Home | Skip to Content | Skip to Search | Skip to Navigation | Skip to Footer |
Worldwide [change] |Register |About Cisco
Guest

Hierarchical Navigation

CiscoWorks Resource Manager Essentials

Release Notes for Resource Manager Essentials 4.1 on Windows

Downloads

Table Of Contents

Release Notes for Resource Manager Essentials 4.1 on Windows

New Features

New Device Support

Product Documentation

Additional Information Online

Caveats

Known Problems in RME 4.1

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.1

Obtaining Documentation, Obtaining Support, and Security Guidelines

Open Source License Acknowledgements

OpenSSL/Open SSL Project

License Issues


Release Notes for Resource Manager Essentials 4.1 on Windows

These Release Notes contain information about new features. They provide pointers to device support information and also provide information about the known and resolved problems in this release.

For the details about the supported Windows versions see the Installation and Setup Guide for Resource Manager Essentials 4.1 on Windows.

These Release Notes provide:

•New Features

•Product Documentation

•Additional Information Online

•Caveats

•Known Problems in RME 4.1

•Resolved Problems in RME 4.1

•Obtaining Documentation, Obtaining Support, and Security Guidelines

•Open Source License Acknowledgements

New Features

This section discusses the new features in RME 4.1.

Support for 10k Devices

The managing capacity of RME is enhanced to support 10k devices with the minimum requirement of Dual CPU and 4GB RAM. A single server with CS 3.1 and RME 4.1 installed in it is equipped with the capacity of managing 10k devices thus optimizing performance and meeting the scalability prerequisite.

The support for 10k devices for RME is applicable only for CW-LMS-3.0-10K-K9 license of LMS 3.0.

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

Support for IOS Software Modularity Images

Cisco IOS Software Modularity images allow you to apply Maintenance Packs to overcome critical security issues without upgrading to a new software release.

The RME Software Management component allows for distribution of Cisco IOS Software Modularity images as well as Maintenance Packs.

Software Modularity images can be downloaded from Cisco.com to the Software Repository.

For detailed hardware support of Software Modularity images, see the 12.2SX Release Notes.

PSIRT Summary Report

You can use the PSIRT Summary Report to ascertain security vulnerabilities that could affect the devices running IOS in your network. You can generate this Inventory report by selecting this option from the Report Generator dialog box under RME Reports.

The Cisco.com Fetch Interval option helps you to set the frequency of retrieving PSIRT information from Cisco.com and store it in the RME database.

The Report Generator, retrieves information from this database. It also queries the RME Inventory to retrieve information about the impacted devices and generates the PSIRT Summary Report.

End of Sale/End of Life Report

You can use the End of Sale/End of Life Report to ascertain the End of Sale or End of Life details that impact the devices and modules in your network. You can generate this Inventory report by selecting the End of Sale/End of Life option from the Report Generator dialog box under RME Reports.

The Cisco.com Fetch Interval option helps you to set the frequency of retrieving End of Sale/End of Life information from Cisco.com and store it in the RME database.

The Report Generator, retrieves information from this database. It also queries the RME Inventory to retrieve information about the impacted devices and modules and generates the End of Sale/End of Life Report.

Performance Tuning Tool

You can tune system parameters using PTT to improve RME performance. Now you can use PTT to tune Sync Archive, NetConfig, Syslog, Device Management, Check Device Attributes (CDA) and Inventory Collection sub systems of the RME application.

External TFTP Server Support

The Remote Staging and Distribution now allows you to use an external TFTP server as the staging server, to distribute images to all the devices available in RME.

First the image to be distributed is staged to the external TFTP server manually. Then the staged image is upgraded on all the selected devices.

Device Manageability Status

You can use this new reporting option to ascertain possible Inventory or Configuration Collection Failure and take timely actions. You can select the required devices and generate an immediate report. This Device Manageability Status report displays the status of Inventory and Configuration Collection.

Dual Supervisor Support

RME Software Image Management now supports upgrading both active and standby supervisor engines or route processors for the following devices:
Catalyst 4500, Catalyst 6500 (running Cisco IOS/Cisco IOS Software Modularity), Cisco 7600 Routers, Cisco 10000 Routers.

Secondary Credentials Fallback

The Secondary Credentials page available under System Preferences tab of RME Admin allows you to enable or disable fallback to secondary credentials when authentication through Primary Credentials is not successful.

Notification on Inventory / Configuration Failure

You can use the Collection Failure Notification window to configure the receipt of Trap messages on Inventory Collection or Configuration Fetch failure. This Trap is sent for each device from the RME server whenever the collection does not happen.

Other network management stations can use this Trap to know about RME Inventory or Configuration collection failure status. You can configure the destination IP address to which the traps are sent in the env.properties file.

Any third party Trap receivers in the hosts mentioned in the env.properties can receive the Trap messages on Config collection/Inventory collection failure.

Netconfig Reload Task

You can use the Reload Task available under RME NetConfig to reload selected devices in one step. This feature can be accessed from both GUI and CLI.

You can use the NetConfig Reload task in conjunction with SWIM. During Software Distribution using SWIM, the images are distributed to the selected devices.

You can use the Reload task to reload the devices for which, you have not selected Reboot Immediately After Download while scheduling the distribution of the images.

Syslog Support for CSS Devices

From this release, the CSS Syslog messages are also supported.

Software Management Command Line Interface

You can use the new Software Management CLI utility to list software images available in the Software Management Repository as well as export images from the Software Management Repository.

CWCLI Support for CDA Jobs

The CDA jobs are now provided CWCLI support. Apart from using the GUIs for CDA jobs, you can use CWCLI to create, list, stop, cancel, delete CDA jobs as well as verify the CDA job status.

GUI Based Write2Start Option

The Write2Start option can now be run from both CLI and GUI.

Enhanced Severity Level Summary Report

This report has been enhanced to provide more comprehensive details about the Syslogs for each severity for each device. The Syslogs are categorized based on severities as Emergencies, Alerts, Criticality, Errors, Warnings, Notifications, Informational messages and Debug messages.

For each device, count of syslogs is provided for each severity. Clicking on any severity count link corresponding to a device, in the report provides detailed information about the messages for that severity.

GUI Based Option to Export Images from Software Repository

Now you can export software images from Software Repository using the GUI based Export button.

SysUpTime Attribute for Inventory Custom Reports

SysUpTime is a new attribute added for Inventory Custom Reports.

New Device Support

For a list of all devices supported in RME 4.1, including devices supported in previous versions of RME, see the Supported Device Table for Resource Manager Essentials 4.1 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.0.

•User Guide for Resource Manager Essentials 4.1

Adobe Acrobat Reader 6.0 or later is required.

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

•Installing and Getting Started with CiscoWorks LAN Management Solution 3.0.

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

•User Guide for Resource Manager Essentials 4.1

Provides information on using RME 4.1.

•User Guide for Common Services 3.1

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

•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.1. 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.1, and the procedures mentioned in this document, see the User Guide for Resource Manager Essentials 4.1.

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 4.1 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 4.1 from:

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

Caveats

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

Known Problems in RME 4.1

This section contains known problems for RME 4.1:

•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

For more information about known problems:

Step 1 Go to http://www.cisco.com

Step 2 Select Technical Support & Documentation > Tools & Resources.

Step 3 Select the Software sub-section and click Bug Toolkit.

Alternatively, go to: http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl

You will be prompted to log into Cisco.com.

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 to 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 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

No 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 on 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

When you install RME 4.0.3 and upgrade to RME 4.0.4 /
RME 4.0.5/RME 4.1, 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, 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.

CSCsi89107

Restore operation fails when LMS 2.2/2.5/2.5.1/2.6 data is restored to LMS 3.0

This happens when you:

1. Backup the LMS 2.2/2.5/2.5.1/2.6 data

2. Perform a Remote migration from LMS 2.2/2.5/2.5.1/2.6 to LMS 3.0

The space check is done in RME to confirm if two times free space than the backup size is available for a smooth restore.

3. Restore the backed up data.

The data restore happens under NMSROOT as well as RME backup folder.

The filebackup.tar file is extracted in the RME backup folder.

A space crunch arises as the size of the extracted backup file exceeds twice its size. Twice the size of the backup amounts to the available space. The restore operation fails. The error messsages are recorded in the restorebackup.log file.

Workaround 1:

Ensure that the backup is available in the same drive in which the product is installed. If this is ensured, this drive will contain five times free space than that of the backup resulting in a successful restore.

Example:

If the backup size is 5GB then the free space should be minimum 25GB.

Workaround 2:

If the backup data is in a drive other than the drive in which the product is installed, ensure that the drive (in which the product is installed) consists of three times free space than the size of the backup. This will result in a successful restore.

Example:

If the backup size is 5GB then the free space should be minimum 15GB.

CSCsi73325

Error messages logged in restorebackup.log when LMS 2.5.1 backedup data is restored to LMS 3.0 using remote migration.

This happens when you:

1. Backup LMS 2.5.1 data.

2. Install LMS 3.0

3. Restore the LMS 2.5.1 backed up data to LMS 3.0 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 in the CLI screen.

Workaround:

None.


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.1 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.


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 in 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), then 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

CSCsb28200

Grouping rules that are built using equality matches on:RME:INVENTORY:Device.System.SystemOID do not find matches.

This happens if the sysObjectID on which the match is performed does not begin with a leading dot.

All sysObjectIDs in RME are stored with a leading dot.

Workaround:

Either specify the leading dot in the match value, or change the operator from Equals to EndsWith or Contains.

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.1or the RME 4.1 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.

CSCsc22924

CDA fails for a device configured with TACACS prompt.

This problem occurs when the Telnet credentials are incorrect. CDA fails although you have entered the correct credentials and Sync Archive applications are successful.

Workaround:

None.

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.

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 more 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.1

When Inventory report jobs are migrated from RME 4.0 to RME 4.1, 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 not listing 10k devices if the All Devices node is expanded.

The Device Selector is not listing 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 the devices on expanding 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.

CSCdw68406

Inventory does not handle Cisco ONS Series (ONS 15540 ESP) devices with distinct configurations.

To perform redundancy operations Cisco ONS Series (ONS 15540 ESP) devices requires that both processors have the same configurations.

If they are:

•Configured with different set of credentials and a forced switch-over is made

And

•The read community string is different, Inventory will not manage the device

The device goes into the Not Responding state.

Workaround:

None


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 with 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.1 or the RME 4.1 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 the 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.

CSCse88215

Change Audit Purge job does not remove diff files

Change Audit Purge job does not remove diff files even after the corresponding config versions are removed.

Diff files are files that are created as Change Audit reference records during the Archive Purge.

Workaround:

Manually remove the content from the difffiles directory:

NMSROOT\files\rme\dcma\difffiles

Deleting the contents of the difffiles directory does not affect any functionality.

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.


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 command fails.

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.

CSCsh38157

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

This problem happens when you:

1. Go to RME > Config Mgmt > NetConfig

2. Schedule a NetConfig job with TACACS+ template to NAM devices.

3. Try to update DCRusing:

ip http tacacs+ enable 5.3.6.3 <R>**<R>**

The interactive commands are not handled properly and the job fails with the following error message:

Command(s) failed on device.

Workaround:

None.


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 in 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.

CSCsi48034

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

This problem occurs when you:

1. Go to RME > Config Mgmt > Config Editor

2. Select a configuration and change the hostname using Config Editor.

3. Schedule a job to deploy the changed configuration.

4. Set the protocol as Telnet for this job.

The job fails with the message:

Deploy succeeded, Synchronization of RME archive wth Device Config failed.

The same problem occurs when you set SSH as the protocol.When you:

1. Go to RME > Config Mgmt > Netconfig

2. Schedule a job to use an Adhoc task in Netconfig to change the hostname.

3. Set the protocol as Telnet for this job.

The job fails with the message:

Deploy succeeded, Synchronization of RME archive with Device Config failed

Workaround:

After the Netconfig job is completed and the error message appears, you can run a Sync archive job for that particular device to archive the latest configuration.

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.


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.1.

These isolated custom commands do not exist in RME 4.1 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 and from the Command Sets page, select the command set you want to edit and click Edit) and follow the same procedure detailed above.

3. 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.