Driver Support Document
| SYSOID Mapping | ||
| SYSOID | MODEL | OS VERSION |
| 1.3.6.1.4.1.18.3 | AN | 14.03, 14.20, 15.4, 15.5, 15.6, 15.7 |
| 1.3.6.1.4.1.18.3 | ARN | 14.03, 14.20, 15.4, 15.5, 15.6, 15.7 |
| 1.3.6.1.4.1.18.3 | ASN | 14.03, 14.20, 15.4, 15.5, 15.6, 15.7 |
| 1.3.6.1.4.1.18.3 | BCN | 14.03, 14.20, 15.4, 15.5, 15.6, 15.7 |
| 1.3.6.1.4.1.18.3 | BLN | 14.03, 14.20, 15.4, 15.5, 15.6, 15.7 |
| 1.3.6.1.4.1.18.3 | BN | 14.03, 14.20, 15.4, 15.5, 15.6, 15.7 |
BayRS routers will deny CLI login attempts if there is not enough memory available to support them. On devices that are low on memory such failures can cause NAS device tasks to fail unexpectedly. If the device is low on memory, you may see error messages like:
Retrieve configuration via CLI (Warning: Timeout in executing script: Failed to get to technician interface mode.)
If messages like this occur frequently in NAS, you may need to reboot your router to clear up memory. Adding memory to the device will prevent the error from occuring frequently.
You can configure BayRS devices to send syslog messages to multiple hosts. However, by default, the device sends messages to only five of the configured hosts. You can use the command maximum-hosts (in bcc) to configure the device to use more or fewer syslog hosts, with an absolute maximum of ten.
You can use the show syslog log-host command (in bcc) to confirm the "operational state" of syslog messaging to the NAS server. If the operational state is down, remove any unnecessary syslog servers from the device's configuration or increase the maximum-hosts value to at least one greater than the number of currently configured syslog hosts. To enable syslog logging to the NAS server that was previously listed as down, save the configuration you modified and reload the device. Alternately you may delete the syslog host entry for the NAS server from the configuration and then use the NAS "Configure Syslog" task to add it back to the device.
Nortel ASN devices may not be discovered through CLI when the NAS system is under heavy load, such as when there is extensive logging by the NAS system and concurrent tasks are running inventory discovery tasks with "store session log" enabled. As a result, ASN devices may not respond to CLI command queries fast enough and the discovery task may fail for some or all of these types of devices. It is recommended that you set up ASN devices for SNMP access by the NAS server, or if this is not feasible, manually assign the driver to the devices exhibiting this behavior.
Due to problems encountered with various OS versions on BayRS devices, discovery of the driver is limited by an explicit list of OS versions. NAS will only discover the BayRS driver for OS versions it supports.
Workaround:
Additional OS versions to support can be added to your system if necessary. Contact Opsware Tech Support for more information.