Driver Support Document
| SYSOID Mapping | ||
| SYSOID | MODEL | OS VERSION |
| 1.3.6.1.4.1.4115.1.9.1 | E6000 | 1.0 |
| 1.3.6.1.4.1.4998.2.1 | Cadant CMTS C4 | 2.0, 4.02, 7.02, 8.00 |
Cadant devices support the reporting of both a "full" and "verbose" configuration, in addition to the regular configuration. When the "full_config" or "verbose_config" access variable is set to 'true', NA will capture the full or verbose configuration by adding the respective keywords to the 'show running config' and 'copy running-config tftp:' commands. If the variable full_verbose_config is set to 'true', then both arguments will be used.
Cadant devices can report their startup configuration in such a way that it can not be correctly compared with the running configuration. Because of this, the startup and running configurations would be seen as out of sync, even after a synchronization task. To avoid this, the comparison script has been altered so that it will always report them to be equal.
Cadant devices (especially in 'verbose' mode) store their interface configurations in a way that is hard to parse, with non-indented configuration sections. Since the devices can contain hundreds or thousands of interfaces, this can impact snapshot completion times. To skip interface parsing, set the device access variable "skip_parsing" to "true".
Banner deployment requires special handling that cannot be automated. As a result, the driver does not support banner deployment when running the "Deploy to running configuration" task through the CLI.
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.