Driver Support Document
| SYSOID Mapping | ||
| SYSOID | MODEL | OS VERSION |
| 1.3.6.1.4.1.1872.1.13.3.2.1 | 5412XL (ADC-VX) | 28.1.8.0 |
| 1.3.6.1.4.1.1872.1.13.3.2.2 | 5412XL (vADC) | 28.1.8.0, 29.0.0.0 |
| 1.3.6.1.4.1.1872.1.13.3.5.1 | 5224XL (ADC-VX) | 28.1.8.0, 30.0.3.0 |
| 1.3.6.1.4.1.1872.1.13.3.5.2 | 5224XL (vADC) | 28.1.8.0 |
| 1.3.6.1.4.1.1872.1.13.3.6.1 | 10000 | 28.1.15.0 |
| 1.3.6.1.4.1.1872.1.13.3.9.1 | 6420 | 29.5.1.10 |
| 1.3.6.1.4.1.1872.1.13.3.10.1 | 5208 | 30.0.4.0 |
| 1.3.6.1.4.1.1872.1.13.3.10.2 | 5208 | 30.0.4.0 |
| 1.3.6.1.4.1.1872.1.13.3.12.1 | 6024XL | 30.5.2.100 |
This driver supports management of virtual device contexts, but some vADC setups will login to the device with no reference to the overall device model. In such cases, auto-discovery is not possible by CLI. In general, the main device should be managed by its IP address, and virtual contexts will be discovered automatically by the Module Status diagnostic.
Alteon devices can host configurations that contain the device's private keys. By default, these are collected as part of the configuration. If their inclusion is not desired, set the Device Access variable "include_keys" to "false". The device may require a passphrase to be used to encrypt the keys; in this case the device's login passord will be provided to facilitate the encryption. These keys are are ignored during configuration comparison, since they are subject to change with each snapshot.
Discovery tasks for Javascript drivers handle More prompts by using timeouts, which can cause problems with the third-party SSH client code, which interprets the timeout as a disconnection. There are two options to work around the problem. Setting the RCX option [<option name="Driver/Discovery/UsePollRead">true</option>] in site_options.rcx will effect the workaround for all affected devices. Alternatively, it could be applied to a single device by setting the device access variable "PollRead" to "true".
Discovery tasks for Javascript drivers use wakeup characters are sent during device connection, to ensure that the device is responding. Normally, these characters do not echo to the console, but some devices may echo them. In this case, this causes the prompt detection phase to fail, which in turn can cause More prompts to not be handled properly, and discovery may fail. If these characters are echoed from the device [check the session log to see this], then set the device access variable "skip_ctrl_u" to skip the sending of the wakeup characters. Note that setting this option on a previously working device could cause discovery tasks to fail, but it only affects CLI discovery. SNMP discovery is unaffected.