Driver Support Document
SYSOID Mapping | ||
SYSOID | MODEL | OS VERSION |
1.3.6.1.4.1.9.1.747 | ciscoWsC3750g24ps | 6.0.199.4 |
1.3.6.1.4.1.9.1.818 | ciscoNMWLCE | 7.0.220.0 |
1.3.6.1.4.1.9.1.828 | cisco877M | 5.2.193.0, 6.0.182.0 |
1.3.6.1.4.1.14179.1.1.4.2 | ciscoC2600 | 5.2.x, 6.0.x |
1.3.6.1.4.1.14179.1.1.4.3 | cisco440x | 5.2.x, 6.0.x, 7.0.235.3 |
1.3.6.1.4.1.14179.1.1.4.4 | ciscoWSM | 5.2.x, 6.0.x |
1.3.6.1.4.1.9.1.1069 | ciscoC5508 | 7.0.98.0, 7.4.110.0, 8.x |
1.3.6.1.4.1.9.1.1230 | ciscoNMEAIR | 7.4.121.0 |
1.3.6.1.4.1.9.1.1275 | ciscoWiSM2 | 7.3.113.5 |
1.3.6.1.4.1.9.1.1279 | ciscoC2504 | 7.2.103.0, 7.4.110.0 |
1.3.6.1.4.1.9.1.1293 | ciscoWiSM2 | 7.3.113.5 |
1.3.6.1.4.1.9.1.1295 | AIR-CT7510-K9 | 7.4.100.0 |
1.3.6.1.4.1.9.1.1615 | Flex 8500 WLAN Controller | 7.4.100.0, 8.x |
1.3.6.1.4.1.9.1.1631 | Virtual WLC | 7.6.110.0 |
1.3.6.1.4.1.9.1.2170 | cisco5520 | 8.1.121.0 |
1.3.6.1.4.1.9.1.2171 | cisco8540 | 8.1.102.0 |
1.3.6.1.4.1.9.1.2250 | AIR-AP1852E-E-K9 | 8.3.111.0 |
1.3.6.1.4.1.9.1.2427 | AIR-CT3504-K9 | 8.5.1.150 |
This driver can detect connect Cisco Wireless APs and assign them as "virtual context" devices if they define an independent IP address through which they can be managed. Context detection is normally enabled by default, but it is disabled for this driver. To enable this feature, set the device access variable "disable_context" to "false". Changes will take effect the next time the NA Module Status diagnostic task is run.
Setting the device access variable "use_linux" to "true" will cause the driver to supply the full destination path to the device for SCP transfer operations, rather than the default "." path.
This driver parses connected Access Point devices as modules, to display their serial number information. When large numbers of APs are connected, performance can suffer. To disable parsing of the APs as modules, set the device access variable "skip_ap_modules" to "true".
Cisco WLAN controllers display their configuration in two formats. One is exclusively by TFTP, and the other is available by a CLI command; the former can be deployed back to the device by the driver, but the latter can not. Normally, the driver will collect both and allow the TFTP portion to fail while only generating a warning, to allow for scenarios where TFTP is unavailable. If device recovery is essential, then set the "require_tftp" variable to "true" in the Device Access settings, which will cause NA to fail the task if the TFTP portion of snapshot failed for any reason. To cause the TFTP failure to be completely ignored, set the "require_tftp" variable to "false".
Some (older) Cisco WLAN controllers have a different command set where the output of the commands 'show run-config commands' is a big table of useless information, and the 'show running-config' produces the command configuration instead. To allow for this, the driver enables CLI paging to catch this case of switched commands. However, some older devices can hang when the paging is left on, so it is disabled by default. To enable the paging 'catch' for older devices, set the device access variable "legacy_support" to "true".
WLAN controllers provide two configurations, a deployable format and a command format. Both are collected by default. Since the command format largely duplicates the deployable format in content, its collection can be skipped by setting the "skip_cli" device access variable to "true".
The "Insufficient space" warning message can be ignored when deploying a software image to the device. Cisco Wireless Controllers do not provide commands to find out the size of files. The system warning message can be safely ignored. The task will fail with the appropriate warning message if space is really an issue.
The device allows users to configure two vlans with the same identifier. This feature is not supported by HPNA.
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.