The following information details existing device issues that have been discovered within other releases. In most cases, a resolution is included to address the issue.

ME-C3750-24TE and WS-C3750-24ME - Display Error

  • The ME-C3750-24TE and WS-C3750-24ME do not display identically, depending on SNMP or Terminal pull of SystemProperties using the sysObjectID to get the model.

    Cisco IOS Switches - Missing VLAN Database Command

  • The ME3400 does not return VLAN text, due to lack of support for the vlan database command. This will appear in the scheduler with a message of the form: Dialog getVLANs failed: Warning, can not resolve input value (ConfigFile:vlan text.Content)

    Cisco IOS Switches - VLAN Databases

  • To pull VLAN Databases successfully, the device must be discovered as a Cisco IOS Switch.

  • If it is not discovered as a Cisco IOS switch, you must edit the IOSModels.XML in $VOYENCE_HOME/custompackage /pkgxml, and then re-discover the device.

    Cisco IOS Switches - Missing Hardware Information

  • Issue: Cisco IOS Switches with OS version 12.0 (5.2) XU do not display device OS information correctly in the Device Hardware tab.

  • Resolution: Disable all SNMP Credentials, and then Pull the Hardware using Non-SNMP. Doing this ensures the memory size is pulled correctly, and is then populated using the terminal commands. This must be completed before beginning an OS Upgrade.

    Cisco IOS - Out-of-Sync

  • When a SNMP/TFTP mechanism is used with only a Community String credential, the Running against Startup Configuration Out-of-Sync icon is not displayed. A valid Account and/or Privilege Password credential is needed to pull the Startup configuration on Cisco IOS devices.

    Cisco IOS Upgrade - SNMP Information

  • There is no available OS install target for the 3524 Switch.

    • Issue: SNMP information is not present for this model. The information must be retrieved from the IOS CLI.

    • Resolution: Remove all SNMP community strings from the communication settings of the device, and re-pull the hardware specification. This provides the needed memory information to allow for an OS upgrade.

      Cisco IOS Update

  • Issue: An issue exists where the OS image resided in bootflash, but was not the boot loader image. Additionally, the system image file was not in the show version command. In this case, the application could not free space in the target location. Manual intervention is needed to free space.

    When there is insufficient space in the target location for an OS update on Cisco IOS devices with Class A file systems, the system attempts to free up additional space by deleting and squeezing the system image name displayed in the show version command.

  • For example:

    r2621-vpn uptime is 6 weeks, 5 days, 1 hour, 0 minutes

    System returned to ROM by reload

    System image file is "flash:c2600-ik9o3s3-mz.122-15.T9.bin"

  • Resolution: Manually, complete a delete and squeeze on the filename before beginning the OS update.

    TFTP Pushes May Fail Silently

  • Silent configuration command failures may occur when using any of the TFTP transfer methods (SNMP/TFTP, SSH/TFTP, or Telnet/TFTP). Error status, if any, is being missed from the device following the transfer.

    TACACS+ Implementation

  • Issue: Some versions of IOS have a TACACS+ implementation issue that causes additional characters to be added to the login User Name. When this occurs, it may cause occasional login failures.

  • Resolution: Modify a custom version of the stdlib/stdterm.inc file to issue a backspace character before the username as shown below.

    1. Make a directory named $VOYENCE_HOME/custompackage/stdlib

    2. Copy the file $VOYENCE_HOME/package/stdlib/stdterm.inc to

      $VOYENCE_HOME/custompackage/stdlib/stdterm.inc

    3. Change the termLogin() function in this new file:

      • Search for: send(session,userId+stdEOL,true);

      • Change to: send(session,asc(0x08)+userId+stdEOL,true);

      • After making the change, restart the device server services.

        Cisco IOS Switch — Running Configuration Contents

    4. Run the command:

      chown -R ncm:voyence $VOYENCE_HOME/custompackage/stdlib

  • Running configuration contents of the following form must be removed prior to pushing, or the resulting job will fail based on invalid input messages from the device when the data values following the certificate self-signed line are processed:

    crypto pki certificate chain TP-self-signed-2725887360

    certificate self-signed 01

    3082024C 308201B5 A0030201 02020101 300D0609 2A864886 F70D0101 04050030

    31312F30 2D060355 04031326 494F532D 53656C66 2D536967 6E65642D 43657274