Driver Support Document
| SYSOID Mapping | ||
| SYSOID | MODEL | OS VERSION |
| 1.3.6.1.4.1.45.3.46.1 | BayStack470-48T | 3.1 |
Device seems to report its spanning-tree and QOS information differently via the CLI and TFTP. Differences are also shown between successive snapshots when the lines width exceed 80 characters.
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
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.
The device does not send syslog messages that can reliably indicated configuration changes. Therefore, real-time configuration change detection via syslog is not available.