Driver Support Document
| SYSOID Mapping | ||
| SYSOID | MODEL | OS VERSION |
| 1.3.6.1.4.1.9.5.51 | wsc2980gasysID | 5.5(21), 6.4(9), 7.6(12), 8.4(6) |
| 1.3.6.1.4.1.9.5.44 | wsc6509 | 8.3(3) |
| 1.3.6.1.4.1.9.5.45 | wsc6506, wsc6506-E | 8.4(6) |
| 1.3.6.1.4.1.9.5.49 | wsc2980gsysID | 5.5(21), 6.4(9), 7.6(12), 8.4(6) |
CatOS supports access lists in the form of QoS lists and permit lists. Versions 5.x, 6.x, 7.x, 8.x of CatOS only supports permit lists. Permit lists cannot be numbered or named. As a result, permit lists are treated as a single entity by the driver.
Many Cisco devices support a 'show config all' command that includes all default settings in the returned configuration. To retrieve this configuration, set the device access variable "showConfigAll" to "true". Note that transport protocols do not support this argument, only the CLI running configuration will be altered, which may cause a config change when switching between protocols.
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.