Driver Support Document
SYSOID Mapping | ||
SYSOID | MODEL | OS VERSION |
1.3.6.1.4.1.9.1.436 | cisco3745 | IOS 12.4(13r)T |
1.3.6.1.4.1.9.1.544 | cisco3845 | IOS 12.4(13r)T |
1.3.6.1.4.1.9.1.576 | cisco2811 | IOS 12.3(14)T7, 12.4(3a), 12.4(3f), 12.4(3g), 12.4(6)T2, 12.4(10a), 12.4(13r)T, 12.4(15)T5, 12.4(15)T10, 12.4(15)T13, 12.4(15)T14, 12.4(18), 12.4(20)T1, 12.4(22)T5, 12.4(23), 12.4(23b), 12.4(24)T1, 12.4(24)T7, 12.4(25d) |
1.3.6.1.4.1.9.1.1044 | cisco2921 | IOS 12.4(13r)T |
The access to CUE is through a router tty line, if this line requires authentication, its login credentials must be the same as router exec login credentials.
Only one session is allowed at a time. If access to the CUE module fails, please be sure no other user occupies the session, and the that CUE is in a ready and steady state to accept access from router.
This driver was built to support a CUE module context within a Cisco switch. Since the CUE module is not typically IP-addressible, there is no mechanism to distinguish the management of a CUE module from the chassis itself. Discovery for this driver has been disabled to allow normal management of the chassis.
Recent NA versions now features a mechanism for context management, allowing management of the CUE context alongside the chassis via a parent-child relationship using separate NA inventory items, and work is in progress to rewrite this driver to work under that framework.
This driver uses SCP to deploy router configuration and, after router configuration deployment, the CUE configuration is deployed through TFTP only. Deployment to running is a configuration merge while to startup and reload is a configuration replace.
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.