Guest

CiscoWorks Resource Manager Essentials

Release Notes for Resource Manager Essentials 4.3 (With LMS 3.2)

  • Viewing Options

  • PDF (730.5 KB)
  • Feedback
Release Notes for Resource Manager Essentials 4.3 (With LMS 3.2)

Table Of Contents

Release Notes for Resource Manager Essentials 4.3 (With LMS 3.2)

New Features

New Device Support

Product Documentation

Additional Information Online

Caveats

Known Problems in RME 4.3

Installation and Upgrade Known Problems

Administrator Known Problems

Device Management Known Problems

Device/Agent Known Problems Impacting ANI Server and RME Functionality

Inventory Known Problems

Archive Management Known Problems

NetConfig Known Problems

Config Editor Known Problems

NetShow Known Problems

Software Management Known Problems

Change Audit Known Problems

Syslog Known Problems

Contract Connection Known Problems

Bug Toolkit Known Problems

Server, Browser, UI, and Desktop Known Problems

Common/Other Known Problems

Resolved Problems in RME 4.3

Obtaining Documentation, Obtaining Support, and Security Guidelines


Release Notes for Resource Manager Essentials 4.3 (With LMS 3.2)


Published: May 22, 2009

Revised: May 07, 2010, OL-19686-01

These release notes are for use with Resource Manager Essentials (RME) 4.3 running on Windows and Solaris platforms. This document contain information about new features. It provides pointers to device support information and also provide information about the known and resolved problems in this release.

This document consists of the following sections:

New Features

Product Documentation

Additional Information Online

Caveats

Known Problems in RME 4.3

Resolved Problems in RME 4.3

Obtaining Documentation, Obtaining Support, and Security Guidelines

New Features

This section discusses the new features in RME 4.3. It also has information on New Device Support.

The new features are:

Port and Module Configuration

End-of-Sale/End-of-Life Report for Software

Virtual Switching System Enhancement

Perform In Service Software Upgrade (ISSU)

Compare Config Enhancement

Search Archive Enhancement

New Technology Support

Smart Call Home Messages link in Device Center

Smart Call Home NetConfig Job Enhancement

NetConfig Task Selector Enhancement

Newly added NetConfig tasks

Newly added Inventory and Syslog Reports

IPv6 Support

Open Database Schema Support

Port and Module Configuration

Apart from the existing Device Groups, RME now allows you to create groups based on ports and modules for a selected set of devices or device groups. You can do this using Port and Module Group Administration.

You can create NetConfig jobs for port and modules by selecting the following tasks:

Port-based tasks

Manage Auto Smartports

Catalyst Integrated Security Features

PoE

Module-based tasks

GOLD Health Monitoring Test

End-of-Sale/End-of-Life Report for Software

You can generate an End-of-Sale (EoS)/End-of-Life (EoL) report for software images based on the information retrieved from Cisco.com at regular intervals. This is apart from the existing EoS/EoL report available for hardware.

You can generate the EoS/EoL Software report to know the end-of-sale, end-of-life, and the end-of-engineering dates for the software image versions running on the devices in your network.

Virtual Switching System Enhancement

During VSS Conversion, the Select Interface list box lists all the VSS capable 10 Gigabit interfaces. RME allows you to select more than two interfaces for each device. The number of interfaces selected must be the same for both devices.

You can also enter the switch priority value for both the switches. A switch with a higher value becomes the Active Switch and the second switch becomes the Standby Switch. The priority value should not be the same for both devices.

Perform In Service Software Upgrade (ISSU)

RME supports In Service Software Upgrade (ISSU) process that allows Cisco IOS software images to be updated without rebooting the device. This increases network availability and reduces downtime caused by planned software upgrades.

Compare Config Enhancement

You can compare the base configuration of a device with the latest configuration version of different devices. The base configuration can be any Running, Startup, or User archives.

Search Archive Enhancement

RME now allows you to search for configuration archives using the following date range types:

As on—Search config archives on or before a specified date and time.

From—Search config archives for the specified period.

Last—Search config archives for the last N number of days. Where N is the value entered for the number of days.

New Technology Support

Apart from the existing technology support, RME also supports configuration and reporting for following technologies:

Catalyst Integrated Security Features (CISF)

Smartports/Auto Smartports

PoE/ePoE

Smart Call Home Messages link in Device Center

You can generate a Call Home History Report for a Smart Call Home (SCH) device that is registered through Cisco.com. You can do this from the Device Center page. The report displays all SCH messages, such as changes to inventory, configuration and Syslog at regular intervals.

Smart Call Home NetConfig Job Enhancement

If a Netconfig job is created for a Smart Call Home task, then the Job Summary page displays a URL for the devices that are pending registration for SCH messages.

You can click the URL to register the devices that are pending to process SCH messages at Cisco.com.

NetConfig Task Selector Enhancement

All NetConfig System-defined tasks are categorized into various task groups in the Tasks Selector. You can select individual tasks by expanding the applicable task group category.

Newly added NetConfig tasks

You can create NetConfig jobs for devices, ports and modules using the following tasks:

Device-based task—Auto Smartports

Port-based tasks

Manage Auto Smartports

Smartports

Catalyst Integrated Security Features

PoE

Module-based task—GOLD Health Monitoring Test

Newly added Inventory and Syslog Reports

Using RME, you can generate the following Inventory and Syslog reports:

Inventory Reports

POE Port Level report

PSE report

EoS/EoL Software report

Syslog Analyzer Reports

Catalyst Integrated Security Features report

PoE Max Power Violation report

IPv6 Support

RME provides IPv6 support for the following tasks:

Assign an IPv6 Address to a Layer 3 device or VLAN

Retrieve software files from a device

Distribute different versions of software to a device

Schedule retrieval of software from a device

Retrieve configuration files from a device

Distribute a new configuration to a device

Distribute a historical configuration file to a device

Schedule distribution of configuration files to a device

Open Database Schema Support

LMS 3.2 supports exposing few database views and definitions.

You can access the created views using the database access methods such as JDBC and ODBC, from a local or remote server. To enable the access to applications database, you must run the dbaccess.pl utility from the command line.

See the Open Database Schema Support for LAN Management Solution 3.2 document for more information on exposed database views and definitions.

New Device Support

For a list of all devices supported in RME 4.3, including devices supported in previous versions of RME, see the Supported Device Table for Resource Manager Essentials 4.3 on Cisco.com:

http://www.cisco.com/en/US/products/sw/cscowork/ps2073/products_device_support_tables_list.html

Product Documentation


Note We sometimes update the printed and electronic documentation after original publication. Therefore, you should also review the documentation on Cisco.com for any updates.


The following documents are provided in PDF on your product Documentation CD:

Installing and Getting Started with CiscoWorks LAN Management Solution 3.2.

User Guide for Resource Manager Essentials 4.3

Adobe Acrobat Reader 6.0 or later is required.

Use these guides to learn how to install and use Resource Manager Essentials 4.3:

Installing and Getting Started with CiscoWorks LAN Management Solution 3.2.

Provides installation instructions, including both server and client system requirements, steps for installing and uninstalling, and installation troubleshooting information for LMS 3.2. This guide also contains installation instructions for RME 4.3.

User Guide for Resource Manager Essentials 4.3

Provides information on using RME 4.3.

User Guide for Common Services 3.3

Provides information about setting up, administering, and accessing CiscoWorks Common Services 3.3.

Resource Manager Essentials Online help

Provides task-oriented and context-sensitive help from every window that contains a Help button.

Also contains all of the information available in User Guide for Resource Manager Essentials 4.3. This ensures you have complete information even if you do not have the manual readily available while using RME.

For more details on the new features in RME 4.3, and the procedures mentioned in this document, see the User Guide for Resource Manager Essentials 4.3.

Additional Information Online

For information about RME supported devices, refer to the following URL:

http://www.cisco.com/en/US/products/sw/cscowork/ps2073/products_device_support_tables_list.html

For the latest technical tips, suggestions for troubleshooting common issues, and frequently asked questions (FAQs) on most RME applications:
Login to Cisco.com and select Products and Services > Network Management > CiscoWorks LAN Management Solution > CiscoWorks Resource Manager Essentials > Product Literature.

Service Pack (SP) for RME is a collection of updated files necessary for RME to support new Cisco devices. In addition to the devices supported, this package also contains fixes to known problems, as well as additional newly discovered problems.

If you are a registered user, you can download the latest version of SP for RME from:

http://www.cisco.com/cgi-bin/tablebuild.pl/cw2000-rme

Caveats

For more information on caveats, see the Installing and Getting Started with CiscoWorks LAN Management Solution 3.2.

Known Problems in RME 4.3

This section contains known problems for RME 4.3:

Installation and Upgrade Known Problems

Administrator Known Problems

Device Management Known Problems

Device/Agent Known Problems Impacting ANI Server and RME Functionality

Inventory Known Problems

Archive Management Known Problems

NetConfig Known Problems

Config Editor Known Problems

NetShow Known Problems

Software Management Known Problems

Change Audit Known Problems

Syslog Known Problems

Contract Connection Known Problems

Bug Toolkit Known Problems

Server, Browser, UI, and Desktop Known Problems

Common/Other Known Problems

Installation and Upgrade Known Problems

Table 1 Installation and Upgrade Known Problems 

Bug ID
Summary
Explanation

CSCsa15596

RME installation quits unexpectedly.

Errors such as:

String variable is not large enough for the String

appear during the installation of Common Services.

This is because NMSROOT (CiscoWorks Install directory) has a very long pathname.

During Common Services installation there is no restriction imposed on the installation directory path length.

Owing to this, Common Services installation might not fail, if the string length is less than 1024.

However, in the case of RME the chances of failures are high because, RME has longer classpaths which are close to 950 characters with NMSROOT length = 39 characters.

Workaround:

Do not use a long pathname for NMSROOT (CiscoWorks Install directory).

CSCsa33360

Device groups migrated for users (Approvers and Network Operators) cannot be edited by users with the same roles in RME 4.0 and above.

Users with Approver and Network Operator roles cannot edit or delete device groups in RME 4.x that were created in RME 3.x by users with the same roles.

This happens when the device groups created in RME 3.x by users with Approver and Network Operator roles, are migrated to RME 4.0 and above.

Workaround:

None.

CSCsa33365

Network Administrator cannot edit or delete device groups in RME 4.x that they created in RME 3.x, after migration.

After migration from RME 3.x to RME 4.x, users who have Network Administrator roles cannot edit or delete the groups in RME 4.x that they created in RME 3.x.

This happens when the device groups created in RME 3.x by a user with a Network Administrator role, are migrated to RME 4.x.

Workaround:

None.

CSCsa34359

Change Audit details are not available for some of the NetConfig records after data migration from RME 3.x to RME 4.x.

The change details cannot be identified for some of the NetConfig records.

This is because you have purged configuration files in the RME 3.x server where the backup was taken for migration.

These purged configuration files are not available in RME 4.x server after data migration. An error appears, Internal Error: Config File information not available.

Workaround:

None.

CSCsa45325

Not able to upgrade from RME 3.4 to RME 4.x when HPOV is running.

This is because during upgrade, some of the dll files are locked in this directory, NMSROOT\objects\smarts\bin

Where NMSROOT, is the CiscoWorks installed directory.

Workaround:

Stop the HPOV process while upgrading to RME 4.x.

CSCsa22623

Data inconsistency while restoring data backed up with jobs in Running state.

After restoring RME 4.x data on a system, the job status is not the same as that of the system where the backup was taken.

When a backup is triggered while a job is running, the Restore command is not aware of the state of the jobs in the backed-up machine.

Additionally, the Backup and Restore commands do not back up or restore the state of the systems. It is only the data that is backed-up and restored.

Workaround:

Ensure that while backing up data, there are no jobs running on the system.

CSCsd41732

RMEDbEngine Process Entries not found after upgrading RME 4.0.3 to RME 4.0.4/ RME 4.0.5/RME 4.1/4.2

When you install RME 4.0.3 and upgrade to RME 4.0.4 /
RME 4.0.5/RME 4.1/RME 4.2, the RMEDbEngine entries do not appear in the registry.

Workaround:

None.

CSCsd66695

Bug Tool Kit summary Report Jobs not shown in Report Archive.

When you back up data from RME 4.0 / 4.0.1 / 4.0.2 and restore it to RME 4.0.3/RME 4.0.4/RME 4.0.5/RME 4.1/RME 4.2, the Bug Tool Kit summary report jobs are not displayed in Reports Archive.

Workaround:

Change the path value of CriArchiveLoc in regdaemon.xml to point to NMSROOT.

CSCsi73325

Error messages logged in restorebackup.log when LMS 2.5.1 backed up data is restored to LMS 3.x using remote migration.

This happens when you:

1. Backup LMS 2.5.1 data.

2. Install LMS 3.x

3. Restore the LMS 2.5.1 backed up data to LMS 3.x using Remote migration

The Restore operation is successful but there are some error messages related to Syslog that get recorded in restorebackup.log. These error messages are also displayed on the CLI screen.

Workaround:

None.

CSCsq26699

Informational message appears as an error message in restorebackup.log after LMS 2.6 data is restored onto LMS 3.1

This happens when you:

1. Back up LMS 2.6 data.

2. Upgrade to LMS 3.1.

3. Restore the backed up LMS 2.6 data onto LMS 3.1.

4. After the restore is complete, check the restorebackup.log file.

The following message appears:

ERROR: Daemon Manager startup in progress. Please wait.

Workaround:

You can ignore this message as it is only an informational message.

CSCsz45971

Software Managemnet repository location is set to the default path when upgrading to RME 4.3

This occurs when you:

1. Install RME 4.1 and change the SWIM repository location to a custom location. For example, c:\cust-Swim

2. Upgrade RME as follows:
RME4.1 > RME4.1.1 > RME4.2 > RME4.3.

3. The RME 4.3 SWIM repository location is set to the following default location: $NMSROOT/files/rme/repository

Where $NMSROOT is the CiscoWorks installed directory.

Workaround:

Change the custom repository location in Admin -> Software Mgmt -> View/Edit Preferences in the RME 4.3 server.

CSCsy23183

Selective backup data includes stale entries.

This occurs when you:

1. Install RME 4.3 and populate Immediate, Once and periodic jobs for all RME modules.

2. Use the Selective backup feature to perform a backup

3. Restore the backed up version on the same server or on a different RME 4.3 server.

After restoring, the user interface of the RME application displays the latest instance of all periodic jobs. However at the backend, the stale entries of Immediate, Once, and all instances of periodic jobs are also available.

Workaround:

None.

CSCsz50487

Reports archives are not restored.

Purge jobs are not backed up.

This problem occurs when you:

Restore a:

Backup that has a customized CRI location.

Backup that is upgraded from an earlier version of RME to RME 4.3.

In this case, the report archives will not be restored.

Backup:

Data that is archived in customized CRI location.

Data that is upgraded to RME 4.3 from an earlier version of RME.

In this case, the purge jobs are not backed up.

Workaround:

None.

CSCtf77796

LMS version is displayed wrongly in the software update page.

This problem occurs when you upgrade RME using standalone build in CSM environment.

Work around:

None

CSCtg14186

Unable to uninstall RME.

This problem occurs when you uninstall RME after:

1. Installing CS 3.3 along with CSM 4.0, RME 4.3, AUS 4.0 and MCP 4.0 applications in windows server.

2. Executing the test cases or performing backup restore.

Work around:

Remove the rme.info.orig file from NMSROOT/setup/ location before uninstalling RME.


Administrator Known Problems

Table 2 Administrator Known Problems 

Bug ID
Summary
Explanation

None

Some of the RME processes are suspended.

If you start RME by entering

net start crmdmgtd

make sure you do not suspend the session with the suspend command.

If you suspend the root session after manually starting RME, other processes, such as Daemon Manager, and ICServer, are also suspended.

Workaround:

Resume the suspended session.


Device Management Known Problems

Table 3 Device Management Known Problems 

Bug ID
Summary
Explanation

CSCsa18790

Device moves from Pending to Normal to Conflicting state

During Device Import, devices may appear as Normal Devices for a very short span of time.

However, later they move to Conflicting or Alias states after Conflict detection or Alias detection, respectively.

This may occur when you add a large number of duplicate or conflicting devices.

Workaround:

Wait for all devices to be processed for management. This may take some time depending on the number of devices added.

CSCsa22830

DLMS fails in SSL mode

This happens when you get or set credentials using DLMS in SSL mode.

Workaround:

SSL support for DLMS is not available in RME 4.x and therefore there is no workaround.

CSCed47422

Device Management State Summary show wrong record count.

A label on the top right of the Device Management State Summary screen shows, for example:

Showing 7 records

This problem occurs because of the default display provided by the underlying UI component (HTML Scrolling table).

Workaround:

This caption should be read as the number of records displayed on that screen — not the number of devices or the number of device states.

CSCsa36278

AUS should not be displayed in the Picker list while adding devices to RME.

Auto Update Servers (AUS) appear in the Add Devices screen.

This happens when you add new devices into RME, and PIX devices managed by Auto Update Servers are also a part of the list of devices to be managed in RME.

Workaround:

If Auto Management option is enabled, delete Auto Update Servers after they are added to the Normal Devices list.

If you select devices from the Add Devices screen, filter out these Auto Update Servers.

CSCsa45574

Alias detection fails for some devices.

Alias detection does not work for devices that are accessed using a virtual management IP address.

This happens when you add devices with virtual management IP address.

Workaround:

Manually resolve aliases by deleting duplicate entries from the Normal Devices dialog box.

See the User Guide for Resource Manager Essentials 4.3 for details.

CSCsa52951

Device Credential Verification does not run when device moves from Conflicting to Normal state.

Device Credential Verification is not triggered when a device moves from Conflicting to Normal state.

This happens when the device type conflict is resolved and the device moves to Normal state.

Workaround:

Manually trigger Device Credential Verification for such devices.

CSCsq43090

High CPU utilization noticed when managing 10K devices in DCR.

This occurs when you import 10K devices into DCR without MDF and SysObjectIDs.

In this case, more than 80% of the CPU is utilized by the RMEDBEngine process, when you add these devices.

Workaround:

None.


Device/Agent Known Problems Impacting ANI Server and RME Functionality

Table 4 Device /Agent Known Problems Impacting ANI Server and RME Functionality 

Bug ID
Summary
Explanation

CSCsa39153

Archive Management tasks fail for Catalyst 4507 device.

Archive Management tasks fail for Catalyst 4507 device, if you have selected TFTP as the transport protocol.

The happens because of incorrect implementation on the device.

Workaround:

Select a different transport protocol using Resource Manager Essentials > Admin > Config Mgmt.

See Supported Device Table for Archive Management Application on Cisco.com for supported transport protocols information for the Archive Management application:

http://www.cisco.com/en/US/products/sw/cscowork/ps2073/products_device_support_tables_list.html

CSCsa19145

SSH connection to the device fails because of SSH disconnection packet.

This problem occurs on a slow network when RME tries to contact device using SSH connection.

This happens because of incorrect implementation of SSH daemon (sshd) on the device.

Workaround:

None.

CSCsa44813

Archive Management tasks on startup configuration using TFTP does not work

Archive Management tasks on startup configuration using TFTP protocol does not work.

This happens because the device supports only OLD-CISCO-CONFIG-MIB for TFTP and this MIB does not support tasks on startup configuration.

Workaround:

Select a different transport protocol using Resource Manager Essentials > Admin > Config Mgmt.

See Supported Device Table for Archive Management Application on Cisco.com for supported transport protocols information for the Archive Management application:

http://www.cisco.com/en/US/products/sw/cscowork/ps2073/products_device_support_tables_list.html

CSCsa40523

Chassis slot incorrect for MDS 9509

MDS device with software version 1.3(4a) renders incorrect values for its chassis number of slots.

This problem is identified in software version 1.3(4a).

Workaround:

Install software version 2.0(1).

CSCed88554

Supervisor software version value is 0

Device does not return Supervisor software version.

This happens when the device is configured with SNMP.

Workaround:

None.

CSCsa07154

Cannot query containment AG for Catalyst 5000 devices.

If the device happens to run with Cisco Catalyst Operating System Software, Version 4.5(13a), it is likely that SNMP query fails for numSlots (SysObjectID > "1.3.6.1.4.1.9.5.1.3.1.1.25").

This happens when the device is configured with SNMP. The problem occurs because support in the Catalyst OS fails for this SysObjectID.

Workaround:

None.

CSCsa36845

Processor Port and Module Port section are missing from DDR for 4506 IOS

The device running IOS,Version 12.1(22)E2 fails for correlation between the port and the interface because ifIndex is rendered Null.

This happens when the device is configured for SNMP.

Workaround:

The problem does not occur with the IOS, Version 12.1(9a). Upgrade the device to this version.

CSCsa28210

cwcli export for CSS 11800 information is missing

Software Identity is missing in cwcli export, in the case of CSS 11800.

This happens when the CSS 11800 device has to be SNMP configured. The device does not return the processor component, while queried using SNMP.

Workaround:

None.


Inventory Known Problems

Table 5 Inventory Known Problems 

Bug ID
Summary
Explanation

CSCsa86823

A device in the normal state appears with ? icon and cannot be selected.

The Device Selector shows ? as the icon for a normal device for which configuration collection is successful.

Device and Credential Repository (DCR) did not have the device type information while the device was added.

Inventory collection failed because of SNMP time-out.

Workaround:

Update the device type information in DCR.

Make sure that the inventory collection succeeds (if required, increase the SNMP time-out value).

SNMP timeout exceptions can be seen in IC_server.log.

For details on editing device information in DCR, increasing SNMP time-out values, etc., see the User Guide for Resource Manager Essentials 4.3 or the RME 4.3 Online help.

None

IP addresses of cable modems ubr904 and ubr924 may change between reboots.

These devices get the IP address of the cable interface using DHCP from head-end cable router. The IP address might change between reboots.

Workaround:

Import cable modems ubr904 and ubr924 using fully qualified pathnames.

None

Cannot manage PIX Firewall device without RME server IP address.

PIX Firewall device cannot be managed in RME without the IP address of the RME server.

Workaround:

1. Configure the PIX Firewall device so that it can be managed.

2. Enter the IP address of the RME server.

None

Check Device Attributes fails for devices that are already managed through the host name.

This happens when the IP address of the device host name is changed on the DNS server or on the local hosts file (/etc/hosts).

Workaround:

Restart the Daemon Manager.

CSCsa36932

The Inventory Job Status page shows deleted device information.

When a device is deleted, the associated change records are deleted, but the device is still a part of the scheduled jobs.

Hence, the job browser shows the status of the job as:

Successful: With Changes

However, when you click View Details, a message appears:

No changes

for a job that has already run. This is because the changes have already been deleted.

Workaround:

None.

CSCsa38526

RAM, NVRAM information duplicated for some multi-processor devices

In the Processor Information section of the Detailed Device Report, Processor details such as RAM and NVRAM information are duplicated for some multi-processor devices.

This happens when the multi-processor devices do not have support for CISCO-ENTITY-EXT-MIB.

Workaround:

None.

CSCsa16772

Cannot create a Private Custom Template with the same name for different users.

If a template with the name ABC, is created by user X, with any access type, then user Y cannot create a template with the same name ABC.

However, user Y cannot see the template named ABC, which user X has created with private access. This may confuse user Y.

Workaround:

Use the following CLI command to view all template names (Private and Public access):

cwcli invreport -u username -p password -listreports.

This will display all the templates defined in the system. Also, avoid template names that are already in use.

CSCsa22899

Device Credential Verification reports no value to test for Enable when Telnet password is blank

If you do not enter the Telnet Username and Password and only enter the Enable Password, Device Credential Verification reports DID NOT TRY for its the Enable Password check.

This problem occurs when both Telnet Username and Password are not entered in Device and Credential Repository.

Workaround:

None.

CSCsd65609

Scheduled Inventory Collection and Polling jobs are not displayed.

Scheduled System Inventory Collection or System Inventory Polling jobs are not shown in the Inventory Job browser or in the RME Job Browser.

Workaround:

View these details from Common Services Job browser or using the RME > Admin > Inventory > System Job Schedule screen.

CSCsd65650

Incorrect device status count when using ACS in RME 4.x Device Manager.

When LMS 2.5.x is integrated with ACS, the count of managed devices under Device Management and Device Selector are not the same.

This is because some devices in Device Credential Repository are not registered as clients of ACS.

Workaround:

None.

CSCse03788

Audit Trail report for deleted devices not proper

The Audit Trail report for deleted devices does not display the identity that you entered when you added the devices. Instead it displays:

Device with Identity UNKNOWN Deleted

in the Description field.

Workaround:

None.

CSCse06499

Inventory MSP report status shows Success for non-MSP capable devices.

When an Inventory Multi-service Port (MSP) report is scheduled for non-MSP capable devices, the job status is displayed as Successful.

Workaround:

None.

CSCse26973

NVRAM and Total RAM information missing in the Hardware report for IGESM device.

The IGESM device does not consist of NVRAM and Total RAM details.

So when you generate a Hardware report for this device, the NVRAM and Total RAM details do not appear in the report.

Workaround:

None.

CSCsd11513

Inventory Reports page, takes a long time to launch.

The output of Detailed Device Report for 10k devices takes a long time to launch. This occurs when you:

1. Go to RME > Reports

2. Select 10k devices and schedule a Detailed Device Report with Schedule Type as Once.

3. Ensure that this job is completed.

4. Go to RME > Reports > Report Jobs.

5. Select the Job ID of the job you scheduled in Step 2 and click Show Output.

The Detailed Device Report output page is not launched.

After 30 minutes, the following error message appears:

The file is damaged and could not be repaired.

Workaround:

None.

CSCsb74173

Job details not shown for Inventory Report jobs migrated from RME 4.0 to RME 4.x

When Inventory Report jobs are migrated from RME 4.0 to RME 4.x, the job output is displayed in the target machine but not the job details.

Instead, the following error message is displayed:

Job not found, Please see the log for more details

Workaround:

None.

CSCsd31552

Device Selector does not list 10k devices if the All Devices node is expanded.

The Device Selector does not list 10k devices when the All Devices node is expanded. This occurs when you:

1. Go to RME > Devices > Device Management.

2. Expand the All Devices node.

When the total number of devices managed is 10k, the Device Selector does not list all devices when you expand the All Devices node.

Instead, the following error message is displayed:

Showing 4992 out of 10037 number of nodes only in Group/RME@rmetest-sf440/All Devices to prevent performance degradation.

To render all nodes, please avoid having multiple groups open.

Workaround:

None.

CSCsm02177

Some Attributes either do not appear or appear as N/A or Inventory not collected in Custom Inventory Reports if they are Null/empty in database.

When attributes have Null/empty values in the database, they are not shown in the reports.

Certain attributes with empty/null values in database are either shown as N/A or Inventory not collected in the generated custom reports.

Workaround:

None

CSCsh60522

Some links do not work in the Failed Job Results page if viewed through Internet Explorer browser.

Sometimes while you view the job results, links such as device link, Go to Next, First, Last page link do not function properly.

These links do not function correctly in the following scenarios:

RME > Devices > Inventory > Inventory Jobs -

If you view any Failed job with 40 or more failed devices.

RME > Config Mgmt > Archive Mgmt Jobs -

If you view any Sync Archive Failed job with 40 or more failed devices.

RME > Job Mgt > RME Jobs -

If you view any CDA Failed job with 40 or more failed devices.

This mainly occurs when you change the number of displayed rows to 30 or 40.

Workaround:

None.

CSCsm36516

Inconsistencies in the formats of some attributes used in Custom Reports and System reports

The time attribute used in a System report such as Detailed Device Report, generates the time in this format:

dd:hh:min:sec

Whereas the following Custom report attributes:

interface:last changed,

system:Updated At

Image:Build Time

generates the time in yy:mm:dd:hh format.

Workaround:

None.

CSCsm67165

Inventory Fetch does not happen after a software image upgrade and subsequent reload of a device.

When there is an image change in a device the following occurs:

1. A Reload Syslog message is sent to the RME server.

2. The server initiates an Inventory Fetch. After a software image upgrade, the device reloads automatically.

3. The Inventory Fetch request does not reach the device while it reloads.

4. The Inventory Fetch request fails and the device information does not get updated in the server database.

Workaround:

Ensure that you create regular Inventory Polling jobs so that the RME database is current.

CSCsy73729

During Inventory collection, high memory utilization is noticed by the RMEDbEngine process.

In a 10K setup, if you create an inventory job for more than 500,000 ports, the RMEDBEngine process utilizes high memory (approx. 1000 MB).

Workaround:

Distribute the inventory collection across multiple jobs at various intervals.


Archive Management Known Problems

Table 6 Archive Management Known Problems 

Bug ID
Summary
Explanation

None

Banner commands containing (") and (^C) characters cause configuration applications to function incorrectly.

If banner values are contained between quotation marks (") in Config Archive and between Ctrl-C (^C) characters in a device, the configuration applications do not function correctly.

Workaround:

Do not add Ctrl-C characters to the banner commands while downloading them to the device.

None

Module configuration is not retrieved even if the module has valid credentials for a CAT switch.

Configurations of IP addressable modules are not retrieved along with Supervisor even if the module has same credentials as the Catalyst switch.

IP addressable modules should be managed as a separate device.

Configurations of non-IP addressable modules are fetched along with Supervisor configuration only if the selected protocols are Telnet or SSH.

This occurs only if the module has same credentials as the Supervisor.

Other protocols are not supported.

Workaround:

None.

CSCsa97886

Config deploy in the Merge-mode download fails in C2970G-24T-E because of Certificate

Configuration deployment in the Merge mode fails for C2970G-24T-E when you try to deploy certificate commands.

This is because:

The configuration that you are trying to deploy has certificate configuration that is fetched from the running configuration.

and

The configuration archived from the running configuration has certificate commands with the private keys missing.

Workaround:

Make sure that the configuration you are deploying has the certificate commands properly configured (including the private keys).

If you want to deploy non-certificate commands from the configuration, remove all certificate-related commands from the configuration.

CSCsa85666

WLAN Module: Sync Archive fails when TFTP is used.

The Sync Archive operation fails for the WLAN module when TFTP is the only transport protocol that is used.

TFTP is not supported since Config-Copy-MIB is not supported by this device.

Workaround:

You can do a Configuration Fetch operation using Telnet and SSH.

Enable these protocols in the Config Transport Settings page (Resource Manager Essentials > Admin > Config Mgmt) and then trigger the configuration collection.

For details, see the User Guide for Resource Manager Essentials 4.3 or the RME 4.3 Online help.

CSCsa55997

Sync Archive Fails for few NAM devices

Sync archive of NAM devices fails.

If the previous deploy job failed with a timeout exception, subsequent Sync Archive jobs for that NAM device will fail.

Workaround:

Either:

Stop and restart the ConfigMgmtServer service at Common Services > Server > Admin > Processes.

Make sure that no other jobs are running. If they are running, perform this task operation after the jobs complete.

Or

For specific device, fetch the startup or running configuration.

To do this use the Startup or Running hyperlinks at Resource Manager Essentials > Config Mgmt > Archive Mgmt > Version Summary.

CSCsa44963

Archival fails in Cisco Content Services Switch 11050.

Configuration archival fails in the Quick Configuration deployment job in the Merge mode for Cisco Content Services Switch 11050.

Workaround:

None.

CSCsa37473

Issue in Config for device CSS 11050

Archived configuration does not contain the complete running configuration.

This occurs when:

The image on the device is Content Switch SW Version 5.02 Build 3 with SNMPv1/v2c Agent.

Configuration fetch is tried with both Telnet and TFTP protocols.

Workaround:

None.

CSCsa35699

VPN configs coloring scheme is incorrect for Compare Configs.

In the Config Diff Viewer, the diffs of modified commands are shown in blue text instead of red.

For VPN 3000 devices, the diff viewer shows the modified commands in blue instead of red, as in other devices.

Workaround:

None.

CSCsa35538

Configuration archival fails for VPN devices.

On Windows, the configuration fetch operation for VPN 3000 devices, fails.

This happens when there are characters such as '<,''>' in the configuration file. For XML parsers these characters are the delimiters.

Workaround:

Remove these characters from the device configuration file.

CSCse34985

TFTP deploy fails for CAT7K device.

While deploying configurations using TFTP protocol for a Cat7K device, the deployment fails.

This failure occurs only on a Windows platform.

Workaround:

None.

CSCsh36359

Write2Start does not work properly for PIX devices.

This occurs, when you:

Download a configuration to the startup configuration of a PIX device.

Workaround:

Use the adhoc template in RME NetConfig to download the command to copy the configuration from external TFTP server to startup configuration for a PIX device.

CSCsl10121

Comparing Configurations also happens for versions that have been purged.

This happens when you:

Compare the versions of a configuration file, where one version has been purged and the other still exists.

The configurations are compared although one of the versions has already been purged.

Moreover, if you select Raw as the mode in Config Viewer, an HTTP-500 error occurs.

Workaround:

None.


NetConfig Known Problems

Table 7 NetConfig Known Problems 

Bug ID
Summary
Explanation

CSCsa78026

Adhoc Enable Mode command, sh run fails for some string patterns

When you create a NetConfig Job with the Adhoc Enable Mode Command sh run, the job status may be reported as Failed even if the commands have been successfully downloaded.

This may occur when the successfully downloaded command output contains well-known error messages such as ERROR:, %ERROR: etc..

These error messages are ideally only a part of the command output during error conditions.

Workaround:

None.

CSCsa88829

Problem with credentials removal in DCR with NetConfig job, when AAA new-model is enabled

When you are disabling credentials using NetConfig, the device may become unreachable from within RME.

However the device remains reachable outside RME.

This may occur when you disable or remove credentials such as Telnet password using a system-defined task in NetConfig.

Workaround:

To enable TACACS authentication, you should use the TACACS+ task and not the Telnet Password task.

To disable one kind of authentication, you should enable another kind of authentication.

For example, if you want to disable Telnet authentication and enable TACACS+ authentication, you can simply enable TACACS + authentication.

CSCsa15482

Network Time Protocol template does not generate proper rollback commands.

When the download command fails on a device, the successfully downloaded commands are rolled back, if the Rollback policy is on.

If the command ntp authentication-key is already present in the device and if you attempt a rollback of the command, it fails.

Workaround:

None.

CSCsa16093

Trap notifications fail for certain image features.

For Cisco IOS devices, if you select certain trap notifications types for the snmp-server host command in the traps template, it might lead to command download failure.

Workaround:

None.

CSCsa19184

Rollback for the SSH key bit configuration command does not restore the original number of key bits.

This happens when you have enabled SSH on a device with a certain number of key bits and then enable or disable the key bits through an SSH template download.

The download of commands other than the key bits command, fails.

Workaround:

None.

CSCsa22697

Rollback for the ntp server command does not restore the original command on the device.

This happens when you have an ntp server command on the device with the key option enabled.

If you change the command on the device through an NTP template download, the download of all other commands fail.

Workaround:

None.

CSCsa24300

Authentication method of non-ip addressable sub-modules is not updated.

When you update the authentication method for the Supervisor module using the TACACS+ template, it does not update the authentication method.

It also does not update the passwords of the non-ip addressable sub-modules.

Workaround:

1. Add a Telnet or Enable password template and apply commands with the same password to the modules.

2. Add a TACACS+ template to update the authentication method for the Supervisor module. Use the same password as above for this template.

CSCsa25755

Rollback of a job changes the password on the device.

This happens when you rollback a job containing two credential templates. When you change the Enable password, it might change the password on the device.

For example, RADIUS and enable or TACACS+ and enable.

Workaround:

Do not use two different templates to change the Enable password credentials in the same job.

CSCsa27946

CSS: NTP: Server IP address alone allowed. Download fails for hostname

While configuring SNTP server, the IP Address of the SNTP server has to be specified. Instead of the IP Address, if SNTP server hostname is specified, the template fails.

This is applicable for all versions from 5.0 onwards.

Workaround:

Specify the IP Address of SNTP server instead of the SNTP server hostname.

CSCsa44983

The commands fails only for Content engine devices running ACNS 5.2 or later versions.

This happens when the commands deployed using Syslog task on Content Engine devices fails for logging priority configuration.

Workaround:

Do not configure logging priority using a Syslog system-defined task on Content Engine devices running ACNS version 5.2 or later.

1. Create a user-defined task for configuring logging priority with commands specific to ACNS 5.2 or later

2. Use this task for deploying on Content Engine devices running ACNS 5.2 or later.

CSCsa44626

IOS-enable TACACS fails when aaa new-model is enabled.

Download of TACACS commands such as login tacacs, tacacs server etc., fail.

This happens when the command, aaa new model is present on the device.

Workaround:

Disable the aaa new model command. To do this use either the TACACS+ or RADIUS template before adding the TACACS template commands.

CSCsa23231

Job Creation wizard loses context when multiple templates are opened.

This problem occurs while creating a NetConfig job, in the second step of the wizard (Add Tasks).

If you open multiple task windows simultaneously and try to add the tasks to the job, there are problems with the wizard.

Workaround:

Open only one window at a time.

CSCsq14383

All profiles created for Call Home get listed under a single profile configlet.

When Call Home profiles are configured in Call Home supported devices, the created profiles (other than Cisco-TAC1) are listed under a single profile configlet. This appears so when you view either the running or the startup configuration in Config Viewer.

Workaround:

None.

CSCta02155

EEM scripts fails to run.

This occurs when you create a NetConfig job by selecting the EEM task to deploy EEM script. The EEM script contains extra line entries appended at the end of the script, which causes the script to fail.

Workaround:

To fix this problem, you must download and install the following RME 4.3 patches from http://www.cisco.com/cgi-bin/tablebuild.pl/cw2000-rme:

rme4.3.0-win-CSCta021550.tar (On Windows)

rme4.3.0-sol-CSCta021550.tar (On Solaris)

 

Netconfig tasks are not displayed in RME application space.

This occurs after installing RME. This is because, database schema changes failed to get updated due to some transient issue (i.e DB tables would be missed).

Work around:

1. Stop the daemons.

2. Run the following script:

NMSROOT\bin\perl.exe -iNMSROOT\objects\perl5\lib NMSROOT\dbupdate\ 
dbupdate.pl NMSROOT\rigel\scripts\rme\dbupgrade\createDb.txt

where NMSROOT, is the CiscoWorks Installation directory.

3. Start the daemons.


Config Editor Known Problems

Table 8 Config Editor Known Problems 

Bug ID
Summary
Explanation

CSCsb78495

Config Editor overwrite job does not work for PIX devices

A Config Editor job in the overwrite mode, does not work for PIX devices. That is, when you are deploying a configuration that you have edited using Config Editor, to a PIX device, in the overwrite mode, the deployment is unsuccessful.

This happens if you:

1. Edit the configuration of a device using Config Editor and save it.

2. Create a job to deploy that configuration to a PIX device, using the Overwrite mode.

The job fails.

However, the job, succeeds in the Merge mode

Workaround:

None.

CSCsa36347

SNMP Authentication/privacy passwords not masked in device response

SNMP security password and Privacy passwords appear in an argument list on the Device Details page.

This happens when Debug is enabled in the device.

Workaround:

Disable Debug on the device.

CSCsa39790

Config Editor updates the Device and Credential Repository with an encrypted string.

If service password-encryption is enabled on the device then credential would be encrypted in show config output of the device.

The Device and Credential Repository is updated with this encrypted password, if you:

1. Create a Config Editor job in Merge mode using Telnet as the transport protocol.

2. Deploy this command using the Config Editor application.

Workaround:

Use the NetConfig application to update the encrypted credential command.

CSCsb82197

The Config Editor deploy job fails when set length length command is downloaded manually in Merge or Overwrite mode.

This problem occurs when you:

1. Go to RME > Config Mgmt > Config Editor

2. Edit a configuration and schedule a Deploy job to deploy that configuration to a device.

3. Manually download set length length command to that device.

Where length is the terminal length.

The Config Editor deploy job fails with the following error message:

Command(s) failed on the device TFTP. Check whether you have provided the correct credentials. If credentials are correct, ensure that the TFTP server is up and running.

Workaround:

Do not manually download the set length length command while deploying a Config Editor job in merge or overwrite mode.

CSCsh65909

Write2Start does not work properly for MDS devices.

This occurs, when you:

Download a configuration to the startup configuration of a MDS device.

The job fails with the following error message:

Transport operation failed, No commands applied on the device.

Workaround:

Use the adhoc template in RME NetConfig to download the command to copy the configuration from external TFTP server to startup configuration for a MDS device.

CSCsi59716

Configurations edited in Processed mode does not support Write2Start.

This problem occurs when you:

1. Go to RME > Config Mgmt > Config Editor

2. Open a configuration and edit it in Processed mode.

3. Schedule a job to write this configuration to the startup configuration of a device.

The job fails.

Workaround:

Edit the configuration in Raw mode and schedule a job to write this configuration to the startup of a device.

CSCsk57507

Exporting of some configuration files after opening in Config Editor results in a HTTP-500 error.

This occurs when you:

Open a baseline template in Config Editor and try to export it.

Edit a private configuration file and try to export it.

Edit a configuration from an external location and try to export it.

All of these scenario results in a HTTP-500 error.

Workaround:

To export a Baseline template:

1. Go to RME > Config Mgmt > Compliance Mgmt > Template Mgmt

2. Select a template and export it.

To export a private configuration file:

1. Go to RME > Config Mgmt > Config Editor

2. Save the private config as a public config and then export it.

You can also use CLI to export the configuration files.

CSCsy76335

Configuration commands are shown as banner.

This occurs when you:

Edit the configuration file using Config Editor.

In the modified config file, if the banner command is either not enclosed or is partially enclosed with a delimiter (" "), then the entire configuration after the banner command is shown as banner.

For example,

banner motd Welcome

banner motd "Welcome

In this case, the configuration commands after Welcome will also be shown as banner.

Workaround:

You must properly enclose the banner with delimiters as shown in the following example:

banner motd "Welcome"


NetShow Known Problems

Bug ID
Summary
Explanation

CSCsa86905

Custom commands, that are not assigned to any Command Sets, are not migrated

This occurs if:

1. In RME 3.x, in NetShow, you had a few isolated custom commands that were not associated with any command set.

2. You backed up and migrated these custom command sets into RME 4.x.

These isolated custom commands do not exist in RME 4.x NetShow after migration.

Workaround:

Associate these isolated custom commands with any user-defined command set in RME 3.x, before taking a backup.

These custom commands will be migrated as if they were part of a command set.

CSCsa73709

Cannot remove an Adhoc command from the Available Commands list

You may not be able to delete an Adhoc command from the Available Commands list (in the Select Commands page of the Resource Manager Essentials > Tools > NetShow > Command Sets flow) even if it is in only one command set.

This occurs when you:

1. Go to the Resource Manager Essentials > Tools > NetShow > Command Sets flow

2. Go to the Command Sets page, select the command set you want to edit and click Edit.

The Select Device Category page appears.

3. Click Next.

4. Select the ad hoc command that you want to delete, from the Selected Commands list and click Remove.

The command moves to the Available Commands list.

5. Select the command from the Available Commands list and click Delete Adhoc.

An error appears:

NS0011:The command(s) show run are not deleted because they may be system-defined or part of a command set or in the selected commands list.

The Adhoc command is not deleted.

6. Select the command from the Available Commands list and click Delete Adhoc.

A message appears that the command is successfully deleted

CSCsa73709

(Continued)

 

Workaround:

1. In the Edit flow detailed above, after Step 3.click Finish.

2. Re-enter the Edit flow from the Commands Sets page (in the Resource Manager Essentials > Tools > NetShow > Command Sets flow

3. From the Command Sets page, select the command set you want to edit and click Edit) and follow the same procedure detailed above.

4. Select the command from the Available Commands list and click Delete Adhoc.

You will see a message that the command is successfully deleted.

CSCsb09234

OutOfMemory exception on printing job output

A 500 server error appears with an out-of-memory exception when you print NetShow Job Results.

This may occur when the job has more than 1500 devices and has a high number of commands that produce voluminous output.

Workaround:

You can do any of the following:

Use the Per-device Print option.

Increase the Tomcat heap-size.

Reduce the number of devices in the job.

CSCsa75907

Cannot add Adhoc commands that are device-specific, in the same command set.

You cannot add device type-specific Adhoc commands in the same command set. The Adhoc commands that you have added in a specific command set apply to all the device types that you have selected.

This scenario occurs when, in the command set creation flow of NetShow (Resource Manager Essentials > Tools > NetShow > Command Sets), you:

1. Choose device categories

2. Add Adhoc commands.

3. Complete the flow.

These Adhoc commands apply to all the device types that you have selected.

For example, if you choose device types Content Networking and Router and add an Adhoc command, this command will be applicable to both Content Networking and Router device types.

Workaround:

Create different command sets for different device types.

For details on creating command sets, see User Guide for Resource Manager Essentials 4.3, or the RME 4.3 Online help


Software Management Known Problems

Table 9 Software Management Known Problems 

Bug ID
Summary
Explanation

CSCsb68458

Software Management fails on Catalyst 5500 with an error

An error, SWIM1035, appears when you try to distribute new software to Catalyst 5500

This occurs:

When RME 4.0 (or later) is installed.

When the device is Catalyst 550x with Supervisor III (WS-X5530)

The content of the error message is:

SWIM1035: Error while performing Recommendation operation.

Runtime error encountered while filtering images caused by a problem with a running image on the device.

See the Troubleshooting section of the RME help.

Workaround:

None.

CSCsb42968

RME 4.x does not distribute images to Cisco Catalyst 6500 series devices running CAT OS.

This problem occurs when the image is being copied to:

bootflash: using TFTP or RCP.

Slot0: using RCP only.

Workaround:

Use Slot0: with TFTP for distribution.

None

Cannot undo image upgrade of tar images for DSBU switches.

After performing an image upgrade of tar images for DSBU switches, you cannot undo the job.

Workaround:

Select the tar image and schedule a new distribution job.

CSCin19501

Software Management includes the bootflash of MSFC as a storage option.

This happens for Cat6000 supervisors running IOS.

Storing the IOS images in the bootflash might bring the device down.

Workaround:

Do not select the bootflash to store the image while upgrading Cat6000 devices running IOS.

Select a different storage location.

CSCsa29037

Image upgrade using Remote Stage fails if the image size exceeds 32 MB.

In the Remote-Stage flow, the only protocol that is supported currently between Remote Stage device and target device, is TFTP.

Here, it uses the TFTP server of IOS on the RS device.

There is a limitation in the Cisco IOS TFTP server for transferring files exceeding 32MB from Remote Stage device to Target device.

Workaround:

Upgrade the IOS image to any of the following versions that have the 32 MB fix:

12.2(18)SXE

12.003(009.008)

12.0(29.03)S

12.2(17d)SXB07

12.2(18)SXD04 12.2(25.04)S

12.3(09.08)T

CSCsa32595

Software Management distribution fails for all devices running Cisco IOS Release 12.3(5x).

This happens because CISCO-FLASH-MIB displays the Flash partition name as Flas instead of Flash.

This problem is found in all devices running Cisco IOS Release 12.3(5x).

Workaround:

None.

CSCsa33864

Add Image or distribution fails in Software Management.

If the tftpboot directory is either a symbolic link or a soft link to a different directory, Software Management add image or distribution operations fails.

Workaround:

None.

CSCsa35853

Software Management Add Image from device and Image Distribution flows fail.

This happens when there are a large number of Cisco Catalyst 2900XL and 3500XL Series Switches selected in the workflow.

These devices will be in pre-deployed state or might have invalid Telnet credentials in the Device Credential Repository.

The application attempts to connect to the device to obtain Flash device and image file information.

Workaround:

We recommend that you do not include a large number of pre-deployed Cisco Catalyst 2900XL and 3500XL Series Switches in the workflow.

CSCsa32962

Device reboot fails when upgraded or downgraded to images with Cisco IOS Release12.2(14)SY*.

The device goes into ROMMMON mode.

This happens when the device is upgraded or downgraded to 12.2(14)SY* versions, that is, 12.2(14)SY4, 12.2(14)SY6.

However, Software Management operations cannot be performed after the upgrade, since the CISCO-Flash-Mib is broken.

Workaround:

If you have 12.2(14)SY* images, upgrade to a higher version available on Cisco.com.

If you have to upgrade or downgrade to these versions, do not select Reboot Immediately in the Software Management Job Options window.

Reboot the device manually.

CSCsa36324

Expert Flow does not work for Cisco Catalyst 3750 Switch.

All Software Management flows except Expert Flow are working for Cisco Catalyst 3750 Switch.

This problem occurs because the image version on this device does not have proper Flash instrumentation.

Workaround:

None.

CSCsa37036

copyFromFlash on Aironet device always returns Success even when there are no files on Flash.

This problem is seen in all Aironet devices. These devices do not have proper Flash instrumentation.

Workaround:

None.

CSCsa47065

7300—Image size verification fails after copy, with running img ver 12.2(18)S

Software upgrade verification fails for a 7300 device if the device is running 12.2(18)S version or any other version in which CISCO-FLASH-MIB does not give ciscoFlashFileName correctly.

In 12.2(18)S, ciscoFlashFileName is returned as disk0 for the image in disk0.

Workaround:

Upgrade the device manually to a different IOS version, in which this problem with ciscoFlashFileName is resolved.

CSCsa22845

Catalyst 5000—Discrepancy in Image Import from Device and Add Image from Network

Image import from the network is not supported for Catalyst 5000.

Workaround:

None.

CSCsa39312

C10700: Distribution fails because of too many boot commands

If there are too many valid boot commands in the device startup-config, the boot command for the new image will not get added to device bootvar.

This happens during device upgrade using Software Management.

If you select the Reboot option because of this problem, the device is rebooted but it does not boot with the new image.

This happens only if many valid boot commands exist on the device before upgrade through Software Management.

Workaround:

Remove some boot commands from startup-config before trying the Software Management job.

CSCin50067

CE: Reboot verification fails when comparing the image version

Reboot verification may fail when images with version prior to 5.1.x, are distributed to Content Engine devices. As a result, Software Management distribution jobs show the status as Failed although the job is successful.

Content Engine devices running ACNS 5.1 or lower, may not return a string that indicates the build number of the software release.

For example, ACNS 5.1.3b17 will be returned in ceAssetSoftwareRevision as 5.1.3.

Workaround:

Manually check the reload.

CSCse08118

Software- distribution.xml shows incorrect IP address on dual home server

During Software Image Distribution, the distribution.xml file shows the secondary IP address as the server address instead of the primary address.

Workaround:

None.

CSCsa08356

Reboot verification is not performed for Standby Supervisor card

This problem occurs because the image version for Standby Supervisor is not available in the MIB. This is because IOS devices do not have dual supervisor support.

Workaround 1:

Manually verify the reboot for Standby Supervisor.

Workaround 2:

1. Make sure the Auto Sync feature is configured on the device.

By default this option is configured on the device. This will synchronize active and standby startup configurations.

2. Schedule a Software Management distribution job to copy the new image to the active supervisor by selecting active supervisor flash device.

The active supervisor flash devices will not have the prefix slave in their display name.

Do not select the Reboot Immediately after Downloading option in Distribution Job

3. Use the same device again to schedule a swim distribution job with the same new image used in Step 2 but selecting the similar standby flash device.

The standby supervisor flash devices will have the prefix slave in their display name.

For instance, if you have selected disk0 as the flash device in step2 then select slave-disk0 as the flash device now.

Select Do not insert new boot commands into configuration file in Distribution Job while scheduling the second job.

4. Reboot the device after the above steps have completed successfully.

Now the active and standby supervisors should be running the new image.

When the cat4500 devices are reloaded, there will be a switch over of the supervisors.

That is, the current active supervisor will become the standby supervisor and vice versa (this behaviour is different in the case of cat6500 IOS devices where the supervisors retain the same state).

This can only be carried out individually for each device, since you need to select Flash devices for manual upgrade.

CSCse74422

Sup3 (SUPERVISOR 3_6000) is not getting renamed to Sup720 (SUPERVISOR720_6000) when RME 4.0.4 is upgraded to RME 4.0.5 or above.

When you upgrade from RME 4.0.4 to RME 4.0.5 or above, the Sup3 of Cat6k devices is not renamed to Sup720. The Sup720 was referred to as Sup3 in RME 4.0.4.

However, it is referred to as Sup720 from RME 4.0.5 release onwards. This is the scenario for Cat6k devices running on Cat OS managed by RME.

While upgrading from RME 4.0.4 to RME 4.0.5 or above, the Sup3 is not changed to Sup720 and so recommendation of software images from the Software Repository does not take place properly.

Workaround:

When you are upgrading from RME 4.0.4 to RME 4.0.5 or later and the Software Repository contains any Sup3 images, you must re-add those images manually to the repository to reflect the latest image type SUPERVISOR720_6000.

When you are upgrading from RME 4.0.4 to RME 4.x, you can export the Sup3 images to any directory and import it again.

This way the images automatically reflect as Sup720 (SUPERVISOR720_6000).

CSCse53270

Undo does not work for successful image distribution jobs for IGESM and 2960G.

When you try to undo a successful image distribution job consisting of tar images for IGESM and 2960G devices, the following error message is displayed:

Internal Error while fetching image information from Cisco.com. This may be caused by a runtime error. Contact Cisco TAC (Technical Assistance Center) with required debug logs.

This error mainly occurs for tar pre-upgrade images. Undoing a successful image distribution job works well for bin pre-upgrade images.

Workaround:

Add the Software tar images that existed prior to the successful image distribution to the Software repository and perform image distribution using Distribute by Device or Distribute by Image flow.

CSCse18070

Verification fails saying that RAM on device is not sufficient to proceed with Software image distribution for IGESM devices.

During software distribution to IGESM devices, the RAM details are shown less than that is available on the devices.

If you use a image whose minimum RAM attribute value is more than the actual RAM space available on the device, then the verification fails.

Workaround:

You can manually edit and downgrade the RAM attribute value for that particular image in the Software repository.

The downgrade value should be less than the RAM available for the device.

This workaround is not applicable for images that are selected directly from Cisco.com for distribution.

The selecting of images directly from Cisco.com for Software distribution is also called a Slamdunk job.

CSCse38083

Incompatible images are recommended during Software distribution for MDS9500 devices.

This problem occurs when you:

1. Add images for MDS9500 devices through Cisco.com to Software repository. To do this, select:

RME > Software Management > Software Repository > Add Images from Cisco.com

The images for Supervisor 1(Vegas) and Supervisor 2 (Isola) are not distinguished and are added to Software Repository.

2. Schedule a Software Distribution job, using either of the following flows:

RME > Software Management > Software Distribution > ByDevice

RME > Software Management > Software Distribution > By image

Both the images are recommended.

3. Continue with the Software Distribution flow.

The distribution fails because the recommended images consisted of incompatible images.

Workaround:

You can select the required compatible images from the list of recommended images before proceeding with Software Distribution.

CSCse54126

Software Distribution and Upgrade Analysis flows show devices twice in the reports.

This problem occurs in either of the following instances:

Scenario 1:

1. Go to RME > Software Distribution

2. Select Distribution By Devices or By Image.

3. Select an image and applicable devices.

4. Click Next

The Device Recommendation page appears with the selected devices appearing twice.

Scenario 2:

1. Go to RME > Software Distribution > Upgrade Analysis.

2. Select Cisco.com or Repository as the upgrade source.

3. Click Go.

The Upgrade Analysis report appears with the selected devices appearing twice.

Workaround:

Since both displayed reports are the same, the duplicate information can be ignored.

CSCse56927

Software Distribution by device fails when the protocol used is RCP for 2960 series devices.

This problem occurs when you:

1. Go to RME > Software Management > Software Distribution > Distribute by devices (basic).

2. The Distribute by devices page appears.

3. Select the required devices.

4. Continue with rest of the instructions to schedule a Software distribution job.

The job fails if the protocol used is RCP.

The job also fails if you use Telnet to connect to the device and try Software image distribution using manual RCP.

Workaround:

You can use the SCP protocol to distribute the images to devices. SCP is a more secure protocol than RCP.

CSCse63584

Software Distribution by device (Advanced) fails when the protocol used is RCP for IGESM series devices.

This problem occurs when you:

1. Go to RME > Software Management > Software Distribution

2. Select any of the distribution methods.

3. Continue with rest of the instructions to schedule a Software distribution job.

The job fails if the protocol used is RCP.

The job also fails if you use Telnet to connect to the device and try Software image distribution using manual RCP.

Workaround:

You can use the SCP protocol to distribute the images to devices. SCP is a more secure protocol than RCP.

CSCsf20973

Incompatible images are recommended during Software distribution for CBS3040 devices.

This problem occurs when you:

1. Add images for CBS3040 device family through Cisco.com to Software repository using RME > Software Management > Software Repository > Add Images from Cisco.com

The images for CBS30x0 device family are added to Software Repository.

2. Schedule a Software Distribution job, using RME > Software Management > Software Distribution > By Device

Instead of recommending images applicable for CBS3040, all CBS30x0 images are recommended.

3. Continue with the Software Distribution flow.

The distribution fails because the recommended images consisted of incompatible images.

Workaround:

You can select the required compatible images from the list of recommended images before proceeding with Software Distribution.

CSCsf22065

Applicable Software images not recommended for CMM devices during Software distribution.

This problem occurs when you schedule a Software Distribution job for CMM devices, using RME > Software Management > Software Distribution > By Device

Software images are not recommended for CMM devices.

Workaround:

You can select the required compatible images from the list of recommended images before proceeding with Software Distribution.

CSCsi53367

Booting of device fails when IOS image upgrade is done through RME Software Management.

This problem occurs when you:

1. Schedule a IOS software image upgrade using RME Software Management.

2. Reload the device which has undergone IOS software image upgrade.

Booting of the device fails.

When devices have more than one location to store IOS images RME does not recognize which partitions can be used for booting an IOS image. This may occur if you have selected a wrong partition.

Workaround:

Choose a suitable partition for the location of the new IOS image.

CSCsi27337

Image filtering not proper for IOS Software Modularity images in Slamdunk and Upgrade analysis flows of RME Software Management

This problem occurs in the following instances:

Scenario 1:

1. Go to RME > Admin > View/Edit Preferences and select Include images higher than running image option.

2. Try a Slamdunk distribution for a Cat6k supervisor720 device.

Slamdunk distribution refers to distribution of software images directly from Cisco.com to devices using RME Software Management.

None of the higher images in Cisco.com are filtered and recommended.

3. Try Upgrade Analysis for a Cat6k supervisor720 device.

None of the higher images in Cisco.com are filtered and recommended.

Scenario 2:

1. Go to RME > Admin > View/Edit Preferences and select Include images higher than running image option.

2. Try a Slamdunk distribution for a Cat6k supervisor720 device.

None of the images in Cisco.com with same image feature subset as running image are recommended.

3. Try Upgrade Analysis for a Cat6k supervisor720 device.

None of the images in Cisco.com with same image feature subset as running image are recommended.

Workaround:

Do not select the filter options in the Admin page, if you expect to get the same version images in later releases with different Technology Identifiers.

CSCsh29914

Inconsistency in the number of devices in Remote Staging and Distribution flow.

This problem occurs when you:

1. Go to RME > Software Mgmt > Software Distribution > Use remote staging

2. Click Go

While selecting a remote stage device, the number of Normal devices consist only of IOS devices according to the filtering.

3. Select a Remote stage device and click Next.

4. Click Back and return to the same device selection screen.

The number of devices displayed under Normal devices is more than the number of Normal devices displayed earlier. Now the Normal devices consists of both IOS and Non IOS devices.

Workaround:

Manually select the devices that support remote staging before continuing with remote staging.

For more information on the unsupported devices for remote staging, see User Guide for Resource Manager Essentials 4.3.

CSCso17225

RME Software Management repository location is set to default path on upgrading to RME 4.2.

This happens when you:

1. Install RME 4.1.

2. Change the Software Management repository location and import some images.

3. Upgrade the server to RME 4.2.

4. Go to RME > Admin > Software Management > View/Edit Preferences and check for the default path.

It reflects the repository location.

However, if you click the images in the repository, the repository location points to the custom path.

Workaround:

Change the repository location to Custom path after upgrade in Admin -> Software Mgmt -> View/Edit Preferences in the RME 4.2 server.

CSCsk42108

RME is unable to copy the image file from the device to the server if the Flash card has been replaced on the device

Currently, RME looks for the full name of the image which is obtained from the sysConfigName. However, if the Flash card is less than or equal to 20 MB, IOS refers to Slot and if it is more than 20MB, it is referred to as Disk.

Hence, if the memory card is replaced from less than or equal to 20 MB to greater than 20 MB in size with the same IOS filename and device is not reloaded, RME inventory still considers the value from sysConfigName as Slot.

When you run a Software Management job to import the IOS image, it fails since Slot does not exists.

Workaround:

Copy the IOS Image manually to the server.

CSCsl16539

RME Software Management job takes a long time to detect that a reboot of the device has not been successful, after downloading a new image.

If a device fails to reboot during a Software management deployment job, it may take a long time for the job to detect this. The time delay depends on the SNMP settings for the device. The higher the timeout and number of retries, the longer the delay.

For example:

SNMP retries = 2 and timeout = 2, the delay is 22 minutes.

SNMP retries = 2 and timeout = 90, the delay is in excess of 12 hours.

Workaround:

Have low settings for SNMP timeout and retries.

CSCsm63267

Image recommendation fails for a software distribution job when some image features are not retrieved from Cisco.com

While creating a software distribution job, some image attributes such as Feature, Version, MINRAM are missing when information is retrieved from Cisco.com.

Software Management uses this information to recommend images. Since these features are not retrieved, the distribution job fails because it cannot recommend images.

Workaround:

None.

CSCso70893

Software upgrade using SSH protocol fails for Catalyst 3750E series devices.

If you use the SSH protocol to upgrade IOS images of Catalyst3750E series devices, running version 12.2(44)SE1 and if you use archive download-sw, upgrade fails. The following message is displayed:

%SCHED-3-THRASHING: Process thrashing on watched message event. -Process= "SSH Process"

Workaround:

Use the Telnet protocol to upgrade images for Catalyst3750E series devices.


Change Audit Known Problems

Table 10 Change Audit Known Problems 

Bug ID
Summary
Explanation

CSCsa33492

ChangeAudit report does not export the grouped records.

Only records shown in the report are exported.

Other grouped records that are visible when you click More Records, are not exported.

Workaround:

None.


Syslog Known Problems

Table 11 Syslog Known Problems 

Bug ID
Summary
Explanation

CSCsa26519

Dateline Standard Time or Greenwich Mean Time is not supported.

When you see the time zone as (GMT-12:00) Eniwetok, Kwajalein, incorrect Syslog times are sent with the Syslog messages.

Workaround:

None.

CSCsa33862

Error while specifying backup location.

You cannot specify a mapped drive as backup location.

This results in an error message that the location does not exist or you do not have permission to access it.

Workaround:

None.


Contract Connection Known Problems

(

Table 12 Contract Connection Known Problems 

Bug ID
Summary
Explanation

CSCdm87814

RME problem with Check Contract Status, for Cat OS-based devices

If you select Resource Manager Essentials > Contract Connection > Check Contract Status, the information is generated only for Cisco IOS devices.

Workaround:

Get information from the Service Contract Center at:

http://www.cisco.com/public/scc/


Bug Toolkit Known Problems

Table 13 Bug Toolkit Known Problems 

Bug ID
Summary
Explanation

CSCsa24273

Bug Toolkit displays different bug counts to different Users logged into Cisco.com.

Data returned from the Bug Toolkit is based on the different security levels of the login IDs, when you use different login IDs to generate the report.

Workaround:

None.

CSCsa47066

For some bugs, the Locate Devices flow does not display correct devices

For some bugs, the Locate Device flow does not display the correct devices that are affected.

This problem can occur at any time.

Workaround:

None.


Server, Browser, UI, and Desktop Known Problems

Table 14 Server, Browser, UI, and Desktop Known Problems 

Bug ID
Summary
Explanation

CSCsa95781

CTMJrmServer goes down after changing to the ACS mode.

The CTMJrmServer process may go down in either of these cases with respect to ACS configuration:

When you change the AAA setup from the CiscoWorks local mode to the ACS mode (Common Services > Server > Security > AAA Mode Setup) and register with ACS by enabling the Register all installed applications with ACS option in the AAA Mode Setup dialog box.

When you re-register the applications with ACS (by enabling the Register all installed applications with ACS option in the AAA Mode Setup screen) while in the ACS mode.

The CTMJrmServer process may go down because of authorization failure at startup.

This happens because the System Identity user is not configured properly in ACS.

CSCsa95781

(Continued)

CTMJrmServer goes down after changing to ACS mode.

The reasons for CTMJrmServer process to go down in the above cases can be:

System Identity user (in the System Identity Setup dialog box under Common Services > Server > MultiServer Trust Management > System Identity Setup) is not configured in ACS.

Or

The System identity user configured in ACS does not have the necessary JRM job privileges.

Workaround:

1. After making the ACS-related security changes, ensure that the System Identity user is configured properly in ACS with the necessary JRM job privileges.

To configure the System Identity user, use the System Identity Setup dialog box under Common Services > Server > MultiServer Trust Management > System Identity Setup.

2. Restart the CTMJrmServer process and the other dependent processes (such as Syslog).

 

CSCin03389

Adhoc template displays Failed for some catalyst devices.

A successful job is displayed as Failed.

Workaround:

Disable debug in the device and run the job.

CSCsf32067

Extra grey spaces appear in few SWIM workflows if number of rows returned is less than 10.

Extra grey spaces appear in following SWIM workflows. This occurs if you:

1. Go to RME > Software Mgmt > Software Repository

a. Click on Add.

The Add Images dialog box appears.

b. Select any one of these options:

Cisco.com

Device

File System

Network

Out of Sync report

2. Go to RME > Software Mgmt > Software Distribution > Upgrade Analysis > Cisco.com

3. Go to RME > Software Mgmt > Software Distribution > By devices (Advanced)

If there are fewer than 10 rows, extra grey space appears.

Workaround:

None.

CSCsg03705

Internet Explorer browser retains last visited screen window size.

When you open a window of any size in Internet Explorer, it remembers the size of the Window previously opened. Any new popup window opened after that, will resize to this previously visited size.

Workaround:

1. Close all instances of Internet Explorer that are currently open, except one.

2. Right click a link on the web page and select Open in the New Window option.

3. Close the first instance of the browser that was originally open by clicking the Close icon at the upper right corner.

4. Resize the existing window by dragging the sides until it is full screen again.

5. Click the Close icon at the upper right corner while holding down the Ctrl key.

The next time you open your Internet Explorer browser, the window will appear as full screen.

CSCsg03697

Internet Explorer popups appear as 10 x 10 screen if the IP address is entered as the server address.

This is a problem with the Internet Explorer browser.

This problem may occur for some of the popup screens. Internet Explorer displays popups as 10 x 10 screen if IP address is provided as server address in the URL.

Workaround:

Invoke the server with host name.

or

Resize the window.


Common/Other Known Problems

Table 15 Common/Other Known Problems 

Bug ID
Summary
Explanation

CSCsa38849

Ctrl+N and Open in New Window result in unexpected behavior in RME.

RME behaves unexpectedly when you open a new window during any of the workflows.

This happens if you press Ctrl+N or select Open in New Window and continue to work on the same flow as the base window.

However, two different workflows that are not under the same tab, do not cause a problem.

Workaround:

None.

CSCsa29250

Cannot filter devices based on user-defined fields

Devices cannot be filtered based on user-defined fields.

Workaround:

Create device groups in Common Services based on user-defined fields and use these in the RME workflows.

See the User Guide for Common Services 3.3 for details on creating Device groups with user-defined fields.

CSCdw48650

(For Inventory)

For ONS Series (ONS 15540 ESP) devices, Inventory Reports might not reflect the latest device information.

Syslog messages are not available after a CPU switchover operation, as a result of which the RME database is not updated automatically.

Workaround:

Run an Immediate Inventory collection job to update Inventory.

See the User Guide for Resource Manager Essentials 4.3 for the procedure.

CSCdw48650

(For Software Management)

For ONS Series (ONS 15540 ESP) devices, Software image recommendation might be based on obsolete information.

Syslog messages are not available after a CPU switchover operation

Owing to this, the RME database is not updated automatically. Software image recommendation is based on data collected by Inventory.

Workaround:

Run an Immediate Inventory Collection job to update Inventory.

See the User Guide for Resource Manager Essentials 4.3 for the procedure.

Software image might be downloaded to a slot for which it was not intended.

If a CPU switchover happens after a software image distribution job is scheduled, Syslog messages are not available for the CPU switchover operation.

As a result of this, the RME database is not updated automatically. Hence, the software image might be downloaded to a slot for which it was not intended.

Workaround:

Avoid scheduling image distribution jobs. Instead perform jobs immediately.

If image distribution jobs are scheduled, ensure that the CPU does not switch over before the job is completed.

CSCsa17529

Special characters such as single quotes, are not supported in a report template name.

When you click on a template name that has unsupported characters (such as single quotes in the link) in the report template table, the following error appears:

Page cannot be displayed.

This happens only if you use a special character such as single quote in the template name while creating the template.

Workaround:

Use only this supported character set:

{A to Z, a to z, 0 to 9, -, _, ., ), (, / and blank space}

CSCsk90535

Help Search results show Unknown help links in upgrade server.

This happens when you use the following upgrade path:

1. LMS 2.5.1 > LMS 3.0 > LMS 3.0.1> LMS 3.1 > LMS 3.2.

2. Search a content in Help with a keyword such as cwcli by selecting ALL groups.

3. Multiple links are listed with same name and some links are displayed with Unknown as the module type.

Workaround:

None.

CSCsx47363

Port and module groups do not work correctly if the parent device group is modified.

This occurs when you:

1. Create a port or module group by selecting the Group Selector.

2. Either:

Modify the parent device group name

Or

Delete the parent device group.

3. Create a netconfig job based on port or module by selecting the created port or module group.

An HTTP 500 error appears in the Add task page of the Netconfig job flow.

Workaround:

None.

CSCtg41231

DCRServer and JRM process down test cases fail in DR mode.

After installing CSM and RME (standalone build) in a windows 2003 server and configuring DR/HA solution, if DCRServer/jrm process goes down in the primary server followed by failing over to the secondary, CS related processes may not be initiated properly on the secondary server.

Workaround:

1. Stop the cluster and replication network.

2. Mount the CSCOpx volume in the server where process is not initiated.

3. Stop the daemons.

4. Clean up all the application databases.

5. Start the daemons.

6. Start the replication network and cluster.


Resolved Problems in RME 4.3

Table 16 describes the problems that were resolved in RME 4.3:

Table 16 Resolved Problems in RME 4.3 

Bug ID
Summary
Additional Information

CSCsm89609

Incorrect error messages were shown for SNMPv3 CDA jobs.

This problem has been resolved.

CSCsu99748

Devices were listed as out of sync, although the Startup and Running configurations were the same.

The Config Diff Viewer page showed that the differences in the configurations were caused by multi-line banner commands (such as banner exec, banner login).

This problem has been resolved.

CSCsh38157

NetConfig job to deploy TACACS+ templates to NAM devices failed.

This problem has been resolved.

CSCsi48034

Config Editor/NetConfig job failed when hostname was changed using Telnet or SSH protocol.

This problem has been resolved.

CSCsd58156

3750 tar images were not transferred while using SCP in RME 4.x Software Management.

This problem has been resolved.

CSCsl44337

RME Software Management Upgrade Analysis report showed HTTP-500 error.

This problem has been resolved.

CSCsg03686

Scroll bars did not appear for some records if the number of records returned were between 16 - 20 in a Version Summary Report.

This problem has been resolved.

CSCsi40639

Software images were not recommended from Cisco.com for 3750 series of devices.

This problem has been resolved.


Obtaining Documentation, Obtaining Support, and Security Guidelines

For information on obtaining documentation, obtaining support, providing documentation feedback, security guidelines, and also recommended aliases and general Cisco documents, see the monthly What's New in Cisco Product Documentation, which also lists all new and revised Cisco technical documentation, at:

http://www.cisco.com/en/US/docs/general/whatsnew/whatsnew.html