Driver Support Document
SYSOID Mapping | ||
SYSOID | MODEL | OS VERSION |
1.3.6.1.4.1.1991.1.3.1.2 | Netiron 400 | v3.x |
1.3.6.1.4.1.1991.1.3.2.1 | ServerIron Switch | v7.x |
1.3.6.1.4.1.1991.1.3.3.1 | ServerIronX/LG | v7.x |
1.3.6.1.4.1.1991.1.3.3.2 | ServerIron 400 | v7.x |
1.3.6.1.4.1.1991.1.3.4.1 | Switch TurboIron 8 | x |
1.3.6.1.4.1.1991.1.3.4.2 | Switch TurboIron 8 | x |
1.3.6.1.4.1.1991.1.3.5.1 | T8Switch | x |
1.3.6.1.4.1.1991.1.3.5.2 | BigIron4000 | 2.x |
1.3.6.1.4.1.1991.1.3.5.3 | BigIron4000 | 2.x |
1.3.6.1.4.1.1991.1.3.5.4 | BigIron4000 | 2.x |
1.3.6.1.4.1.1991.1.3.6.1 | BigIron4000Router | 2.x |
1.3.6.1.4.1.1991.1.3.6.2 | BigIron4000Router | 2.x |
1.3.6.1.4.1.1991.1.3.6.3 | BI4000SI | 2.x |
1.3.6.1.4.1.1991.1.3.7.1 | BI8000Router | v3.x |
1.3.6.1.4.1.1991.1.3.7.2 | BI8000Router | v3.x |
1.3.6.1.4.1.1991.1.3.7.3 | BI8000Router | v3.x |
1.3.6.1.4.1.1991.1.3.8.1 | Fast2Switch | 3.x |
1.3.6.1.4.1.1991.1.3.8.2 | FastIron2Switch | v3.x |
1.3.6.1.4.1.1991.1.3.9.1 | FastIron2PluSwitch | v7.x |
1.3.6.1.4.1.1991.1.3.9.2 | FastIron2PlusRouter | v7.x |
1.3.6.1.4.1.1991.1.3.10.1 | NetIron800 | v7.x |
1.3.6.1.4.1.1991.1.3.11.1 | NetIron800Router | v7.x |
1.3.6.1.4.1.1991.1.3.12.1 | FastIron2GCSwitch | v7.x |
1.3.6.1.4.1.1991.1.3.12.2 | FastIron2PlusGCRouter | v7.x |
1.3.6.1.4.1.1991.1.3.13.1 | FastIronPlusGCSwitch | v7.x |
1.3.6.1.4.1.1991.1.3.13.2 | BigIron15000 | 2.x |
1.3.6.1.4.1.1991.1.3.14.1 | BigIron15000Switch | 2.x |
1.3.6.1.4.1.1991.1.3.14.2 | BI15000Router | 2.x |
1.3.6.1.4.1.1991.1.3.14.3 | BIG15000SI | 2.x |
1.3.6.1.4.1.1991.1.3.15.1 | FastIron3 | v7.x |
1.3.6.1.4.1.1991.1.3.16.1 | FastIron3Switch | v3.x, |
1.3.6.1.4.1.1991.1.3.16.2 | FastIron3Router | v3.x, |
1.3.6.1.4.1.1991.1.3.17.1 | FastIron3GCSwitch | v7.x |
1.3.6.1.4.1.1991.1.3.16.2 | FastIron3router | v3.x |
1.3.6.1.4.1.1991.1.3.17.1 | FastIron3GCSwitch | v7.x |
1.3.6.1.4.1.1991.1.3.17.2 | FastIron3GCRouter | v7.x |
1.3.6.1.4.1.1991.1.3.18.1 | SI400Switch | v7.x |
1.3.6.1.4.1.1991.1.3.18.2 | SI400Router | v7.x |
1.3.6.1.4.1.1991.1.3.19.1 | SI800Switch | v7.x |
1.3.6.1.4.1.1991.1.3.19.2 | SI800Router | v7.x |
1.3.6.1.4.1.1991.1.3.20.1 | SI1500Switch | v7.x |
1.3.6.1.4.1.1991.1.3.20.2 | SI1500Router | v7.x |
1.3.6.1.4.1.1991.1.3.21.1 | 4802Switch | v7.x |
1.3.6.1.4.1.1991.1.3.21.2 | 4802Router | v7.x |
1.3.6.1.4.1.1991.1.3.21.3 | 4802SI | v7.x |
1.3.6.1.4.1.1991.1.3.22.1 | FI400Switch | v3.x |
1.3.6.1.4.1.1991.1.3.22.2 | FI400Router | v3.x |
1.3.6.1.4.1.1991.1.3.23.1 | FI800Switch | v7.x |
1.3.6.1.4.1.1991.1.3.23.2 | FI800Router | v7.x |
1.3.6.1.4.1.1991.1.3.24.1 | FI1500Switch | v7.x |
1.3.6.1.4.1.1991.1.3.24.2 | FI1500Router | v7.x |
1.3.6.1.4.1.1991.1.3.26.1 | FE4802Switch | v3.x |
1.3.6.1.4.1.1991.1.3.26.2 | FES4802Router | v3.x |
1.3.6.1.4.1.1991.1.3.27.1 | FES9604Switch | 4.0.00a |
1.3.6.1.4.1.1991.1.3.27.2 | FES9604Router | 4.0.00a |
1.3.6.1.4.1.1991.1.3.34.1.1.1.2 | FESX424Router | 4.0.01T3e3 |
The Foundry drivers support both SSHv1 and SSHv2. However, some supported devices only support SSHv1 or SSHv2. The correct SSH version for the device should be selected on the Edit Device page in the "Connection Method" field to ensure proper operation.
The Foundry drivers do not support devices with hostnames that contain blank characters. The SNMP sysName field should not contain blanks to ensure correct operation.
Some Foundry devices support usage of SSH without a password. The system does not support this behavior. Devices must be configured to use a password when connecting with SSH. Telnet usage without a password is supported.
You must include the command enable password display in the configuration of Foundry devices to ensure that snapshots and polling work correctly without generating errors.
An attempt to upload software to a Foundry device via TFTP may fail. During a TFTP transfer, the Foundry performs various memory cleanup operations that require additional processing time. The TFTP server times out if the server's timeout property value is set too low. The default value is 3000 milliseconds (3 seconds).
When this error occurs, the message Script - Failed appears in the task details. Although the task shows as failed, the software may bave been successfully uploaded. However, the reboot process fails. You can eliminate this problem by setting the value of the timeout property in the tftpd.properties file to a higher value.
To set the TFTP server timeout property:
- On the Windows server, go to C:\$NA_HOME\server\ext\tftp.
- Using a text editor, such as Notepad, open the tftpd.properties file.
- Edit the TFTP timeout property socketTimeout to a value between 5000 and 10000 (5 to 10 seconds).