Driver Support Document
| SYSOID Mapping | ||
| SYSOID | MODEL | OS VERSION |
| 1.3.6.1.4.1.2272.30 | 8610 | 3.2, 3.3, 3.4, 3.5, 3.7, 4.1, 5.1.3.0 |
| 1.3.6.1.4.1.2272.31 | 8606 | 3.2, 3.3, 3.4, 3.5, 3.7, 4.1 |
| 1.3.6.1.4.1.2272.32 | 8110 | 3.2, 3.3, 3.4, 3.5, 3.7 |
| 1.3.6.1.4.1.2272.33 | 8106 | 3.2, 3.3, 3.4, 3.5, 3.7 |
| 1.3.6.1.4.1.2272.34 | 8603 | 3.2, 3.3, 3.4, 3.5, 3.7, 4.1 |
| 1.3.6.1.4.1.2272.35 | 8103 | 3.2, 3.3, 3.4, 3.5, 3.7 |
| 1.3.6.1.4.1.2272.45 | 1624 | 1.1, 1.2.4, 2.1 |
| 1.3.6.1.4.1.2272.47 | 8310 | 3.0 |
SSHv2 is disabled for the Passport devices. SSHv1 has been enabled to work with Passport and Nortel Ethernet Routing Switch (ERS) devices. SSHv2, however, might encounter protocol errors with NAS and is currently not supported.
In order to prevent this scenario from happening, SSH connections are not allowed to the device.
The device supports different types of VLANs depending on the protocol (byport,byipsubnet,byprotocol,bysrcmac,bysvlan,forIDS) used. A port will only be mapped to a VLAN if it is assigned in only one VLAN regardless of the VLAN's protocol. Furthermore, the configuration does not display the protocol used for VLAN1 (the default VLAN) nor the ports assigned to it, therefore, VLAN1 will not contain any ports.
In order to allow any form of community string management in later versions of the Passport OS (those that require snmp-v3 configuration), the driver uses named community strings of "nasro" and "nasrw". The Passport OS masks all community string values, so NAS is unable to read the actual community string value back from the device and thereby relies on the strings entered by the user as part of the device's authentication data.
As a result of this disparity, NAS may report a community string in use that is, in fact, not configured on the device. Once a community string has been configured using NAS password deployment, that community string can continue to be managed as the driver will modify the named community string as described above. Note that any additional community strings configured on the device will not be affected by these changes. Setting the community string to blank in the NAS deploy passwords task will erase the appropriate named community string from the device, but NAS may continue to report a community string configured if the authentication data has one specified. Furthermore, if you are using password rules rather than device-specific passwords, the information populated into the community string values will always match that of the rule.
The name of the community strings managed by NAS on the device can be configured via the device access settings of: _pp_roid for the read-only community string, and _pp_rwid for the read/write community string.
NAS can manage one of the 4 lesser privileged access levels with limitations. The access level that can be managed by NAS is "ro". To initially manage the "ro" account, the device must have that privilege/account in the default state (where the username, password, and access level all match For example, the device must have the ro account enabled with the username and password set to "ro".
Updating software on a Passport 8000 series device involves several steps to ensure a successful update. Before deploying software to this device, please review the Nortel Passport 8000 Series Devices Software Update Guide. This guide describes how to enable updates for Passport 8000 devices in NAS and the steps necessary to ensure succesful software deployments.
The guide is available at:
http://www.opsware.com/customer_support/product_addins/Passport_8000_Software_Update_Guide.pdf