Driver Support Document

Cisco switches, Catalyst 1900 series, OS version 9.x.x

Show Tested Devices Grid

SYSOID Mapping
SYSOID MODEL OS VERSION
 1.3.6.1.4.1.9.5.18 wsc1900 9.x.x
 1.3.6.1.4.1.9.5.28 wsc1900c 9.x.x
 1.3.6.1.4.1.9.5.31 wsc1900i 9.x.x
 1.3.6.1.4.1.9.5.175 wsc1900LiteFx 9.x.x

Driver Features Support Grid

Driver FeaturesAccess Methods
(X signifies feature support)CLISNMPTFTPCLI+TFTPSNMP+TFTPFTPCLI+FTPSNMP+FTPCLI+SFTPSCPCLI+SCPSNMP+SCPHTTP/HTTPS
X Driver Discovery   X X                      
X General Access release notes
(CLI protocols: telnet, ssh1, ssh2, console)
X     X                  
Configuration
X Retrieve Running Configuration release notes X     X                  
  Retrieve Startup Configuration                            
  Retrieve Binary Configuration                            
X Device information parsing  
X Enhanced Layer2 Basic IP information parsing  
X Configuration Deployment to Running release notes       X                  
X Configuration Deployment to Startup         X                  
  Binary Configuration Deployment                            
Diagnostics
  Routing Table                            
  OSPF Neighbors                            
X Interfaces   X                        
  Modules and Inventory release notes                          
  Flash Storage Space                            
  File System                            
X Uptime   X X                      
X ICMP Test   X                        
X Topology Parsing   X                        
X Duplex Parsing   X                        
  Enhanced VLAN Parsing release notes
Features
X Software Center release notes
(Auto-reboot device models: 'Catalyst 1900')
      X                  
  Software Image Synchronization release notes                          
X Password Management release notes
(Can modify: limited password, full password, read-only community strings, read/write community strings)
X                        
  Syslog Configuration and Change Detection release notes                            
X Custom Scripts and Diagnostics  
X                        
  ACL Parsing  
  ACL Provisioning release notes                          
  VLAN Provisioning release notes                          
X Configlet Parsing  
X QoS Parsing  
X VRF Parsing  
  Context Management                            

Syslog Configuration and Change Detection

Release Notes

Catalyst 1900: Does not support syslog change detection

The Catalyst 1900 does not send syslog messages.

return to top

General Access

Release Notes

Default IOS prompts expected

The product expects the default prompts for Cisco IOS devices, and cannot discover or otherwise interact with the device if it is unable to recognize these prompts.
Exec: >
Enable: #
Config: )#
If your organization routinely uses non-standard IOS device prompts, contact Customer Support to see whether the product can be reconfigured to match your environment.

Virtual Routing Context for Device Management

Some Cisco devices support named routing contexts. If NA must use the command option "vrf <vrf>" for any device tasks, set the "vrf" custom access variable to contain the context used for device access.

SCP Transfers

Some older versions of Cisco IOS an have problems with SCP transfers; NA only supports a device SCP server for IOS versions 12.3 and later. It is recommended that SCP and TFTP are both enabled so TFTP will be used in the case that SCP fails.

SCPv1.5 unsupported on later NA releases

NA has dropped support for SCP v1.5 due to known security issues. Some device/OS combinations have issues with SCP v2 and will fall back to SCP v1.5. Currently, the WS-C4006 with IOS 12.2(20)EW4 is the only confirmed case. As a result, these devices will fail to transfer files using SCP with current versions of NA.

Workaround:

If SCP issues persist, uncheck the SCP protocol and select TFTP to ensure correct operation.

return to top

Retrieve Running Configuration

Release Notes

VLAN.DAT File Location

Most Cisco models use a file named VLAN.DAT file to store vlan information; where avaiable, this driver attempts to retrieve that file and store it as a binary configuration. To enable the capture of the vlan.dat file, set the access variable "getvlan" to "true".

Because the file's location varies depending on the device model, the show version data is used to attempt to determine its location. The default location is "flash"; to override this, set the "vlanslot" custom variable to set the slot name.

return to top

Software Center

Release Notes

During Software Update task, Delete Files action may not succeed if image filenames are non-standard

During a Software Image Updater task, the product attempts to upload a new software image with the same filename as the existing image. Some IOS versions do not support this action. Choosing the option Delete files from selected slot, then compact memory can support the image update by deleting the existing file before attempting to upload the new image. However, this actions succeeds only if the existing image uses the default filename extension .bin.

If the image file has been renamed using a non-default extension, the product cannot find or delete the file and the new image cannot be uploaded. The Device Software Update task will fail. In these cases use a different image filename.

Alternatively, you can prepare the flash manually or via a custom command script before deploying the software image.

Note: The Delete Files operation deletes only .bin file extensions to prevent any configuration or crash information files in flash memory from being deleted.

SCP Transfers

Some older versions of Cisco IOS can have problems with SCP transfers. It is recommended that SCP and TFTP are both enabled so TFTP will be used in the case that SCP fails.

Update Device Software Task Timeout

The driver supports the deployment of software images contained within TAR archives using the "archive" command. TAR extractions can take a long time to complete. As a result, the Update Device Software task could timeout.

Workaround:

Set the "archive_timeout" access variable to a sufficient number of seconds to complete the task. The default setting is 2,000 seconds.

SWIM Support on older IOS versions

The SWIM component is distributed by Cisco to allow consultation with Cisco.com to recommend IOS images that can be used on Cisco IOS devices. This code requires a certain level of support from the SNMP component of the IOS on the device, and some older versions of IOS are known to not work with the SWIM code, generally limited to IOS 12.1 and lower. Such failures are indistinguishable from simple SNMP timeouts or credential problems. If failures are seen, verify the device's SNMP credentials with other device tasks and check timeout settings.

Command arguments for Archive Download-SW command

The Archive Download-SW command supports several command arguments. "/overwrite" is used by default for image deployments, but the argument "/imageonly" can be added to the command by setting the device access variable "imageOnly" to "true". The argument "/leave-old-sw" can be added by setting the device access variable "leaveOld" to "true". Also, the arguments "/no-version-check /allow-feature-upgrade" can be added if the device access variable "featureUpgrade" is set to "true".

Verify option not possible on TAR software images

Cisco devices support installing TAR files that contain software images. However, the command used by IOS to install the file are atomic - no inspection of the software image's MD5 signature is possible, because the file is extracted and isntalled in one step. Clicking the 'verify' option for software images within a TAR file is not supported and will be ignored.

return to top

Configuration Deployment to Running

Release Notes

SNMP/TFTP Configuration Deployment will not work for deploy to startup and reboot

The ability to reboot a device via SNMP is not available, so deployment to startup with reboot requires CLI access to be successful.

Workaround:

Deploy configurations to running configuration, or enable CLI access.

SNMP/TFTP Configuration Deployment task may time out

Cisco devices with slower processors may time out an SNMP/TFTP Configuration Deployment task.

Workaround:

Deploy configurations via CLI/TFTP only.

ACL remarks will get duplicated on deployment

Cisco devices can maintain multiple lines of "remarks" for access list specifications. The device does not check for duplication of remark lines, so any deployment of a remark back to the running configuration of the device will create another remark line (a duplicate).

Workaround:

Use the system persistent comments for ACL remarks. This capability is handled automatically by using ACL comments in the system.

return to top

Password Management

Release Notes

Use Change Password task only with exec & enable passwords

Cisco devices have several different authentication methods available, including line (exec) passwords, enable, local users, and various AAA servers. The product Change Password task assumes the device is using only exec and enable passwords.

If your device uses local user or AAA passwords the Change Password task usually makes the device unreachable from the product and may make the device unreachable manually. Consider noting the Change Password limitation in the device Description for any Cisco device that uses local user or AAA passwords.

return to top

Modules and Inventory

Release Notes

Parsing extra serial numbers from show inventory raw

Some situations may require parsing inventory information that is not shown in the standard "show inventory" command. To switch this command to "show inventory raw", set the device access variable "raw_inventory" to "true"; parsing will continue based on the same output format, but will include the extra information.

return to top

ACL Parsing

Release Notes

Remark lines are replicated when access list is redeployed

Cisco IOS devices may allow users to enter more than one remark line per access list. When this access list is redeployed, the device replicates each remark line.

To eliminate this problem, use the product commenting feature to create and track configuration comments.

return to top

Enhanced VLAN Parsing

Release Notes

Deleted VLANs Port Associations

Some Cisco devices could retain a VLAN's port associations after the VLAN is deleted from the device. To ensure this does not occur, relocate the ports from a VLAN prior to deleting the VLAN from the device configuration.

return to top