Driver Support Document
| SYSOID Mapping | ||
| SYSOID | MODEL | OS VERSION |
| 1.3.6.1.4.1.45.3.46.1 | BayStack470-48T | 3.0, 2.2.x |
| 1.3.6.1.4.1.45.3.40.1 | BPS2000-24T | 3.0 |
| 1.3.6.1.4.1.45.3.49.1 | BayStack460-24T-PWR | 3.0, 2.0.5.20 |
| 1.3.6.1.4.1.45.3.43.1 | BayStack420-24T | 3.0 |
| 1.3.6.1.4.1.45.3.57.1 | BayStack425-48T | 3.0 |
| 1.3.6.1.4.1.45.3.57.2 | BayStack425-24T | 3.0 |
| 1.3.6.1.4.1.45.3.51.1 | BayStack380-24F | 3.0 |
| 1.3.6.1.4.1.45.3.61.2 | BayStack325-24G | 3.0 |
| 1.3.6.1.4.1.45.3.45.1 | BayStack380-24T | 3.0 |
| 1.3.6.1.4.1.45.3.64.1 | BayStack470-48T | 3.7.3.13 |
Occasionally, if the device is not accessed regularly it will fail to respond to telnet sessions. If this behavior manifests itself, we recommend creating a simple command script to "wake up" the device on a regular basis.
Create a new command script that sends an arbitrary command to the device. In the event of a snapshot failure you can run this command script a few times to "wake up" the device, or you can set up the script to run on a regular basis to limit occurances of this device failure. If you schedule it to run on a recurring basis, it should be set up to run as often as you poll devices on your network.
The command script to create for this purpose should have the following information defined:
Name: Wake Up BayStack
Description: Script to wake up BayStack device(s)
Mode: Baystack initialization
Driver: {select either the BayStack 470 driver or "All applicable drivers"}
Script: show banner
The device stores its configuration in a binary format that cannot be decoded. The system captures this configuration and then captures the output of a number of device diagnostics to provide a textual representation of the device's current configuration.
The device will produce a different binary configuration on every snapshot, even if no actual configuration information on the device has changed. As a result of this, the system ignores changes in the binary configuration and uses the captured device diagnostic text to determine if any significant configuration change has occured since the last snapshot that requires a new configuration to be saved.
It is possible that this diagnostic data will not completely represent all configuration options on the device, so we recommend that you set up a regular "checkpoint" snapshot of the device once a week to ensure that any extra configuration information is being collected.
Nortel BayStack 5520 devices running software version 4.3 will at times reboot after driver discovery and snapshot operations.
Workaround:
Upgrade (or downgrade) your Nortel BayStack 5520 devices to a different software version (e.g., 5.06 or 4.2). Alternatively, you can deactivate the devices or remove them from the system.
During an Update Device Software task on a Baystack device, there are times when the task takes longer than usual. As a result, the system goes on to perform other tasks. This causes the Baystack device to stop the software update process before it has completed. However, the system reports that the Update Device Software task was successful, even though the Baystack device is still running the original software.
A "switch_sleep" variable has been added that enables the Update Device Software task additional time to complete before the system performs anything on the device. This variable is set to 0 by default. You can modify the variable to a positive value, thereby giving the Update Device Software task an additional number of seconds to complete before another task is started.
A configuration deployment to a BayStack 470 resets the full-access login password to the hard-coded default password ("secure"). The system configuration deployment script takes this into account by changing the authentication information in the database to match the hard-coded default. However, if the BayStack 470 is configured for radius authentication, the full-access login password is hidden, and the BayStack 470 continues to use radius authentication. Note that in the case of radius authentication, the system changes the database authentication information and relies on password fallback to access the device if there is a radius authentication challenge.
Nortel has indicated that when doing a configuration deployment to the BayStack 470, the IP address settings remain unchanged (i.e., the deployed configuration's settings are ignored). Although these are the only settings explicitly cited by Nortel to be ignored, it is possible the BayStack 470 could ignore other settings in your deployed configuration.
The device does not send syslog messages that can reliably indicated configuration changes. Therefore, real-time configuration change detection via syslog is not available.