Guest

CiscoWorks Resource Manager Essentials

Release Notes for Resource Manager Essentials 4.0.3 on Windows (With LMS 2.5.1)

  • Viewing Options

  • PDF (871.4 KB)
  • Feedback
Release Notes for Resource Manager Essentials 4.0.3 on Windows

Table Of Contents

Release Notes for Resource Manager Essentials 4.0.3 on Windows

New Features

New Features of Inventory

New Features of Device Management

New Features of Archive Management

New Features of Config Editor

New Features of NetConfig

New Features for Job Approval

New Features of Reports

New Features of Syslog

New Features of Change Audit and Audit Trail

New Features of Software Management

New Features of Job Management

NetShow, Contract Connection, and SmartCase Applications

Support for SSHv2

New Device Support

Product Documentation

Additional Information Online

Caveats

Known Problems in RME 4.0.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

cwcli export Known Problems

Contract Connection Known Problems

Bug Toolkit Known Problems

Server, Browser, and Desktop Known Problems

Common/Other Known Problems

Resolved Problems in RME 4.0.3

Customer-found Problems Resolved in RME 4.0.3

Problems Resolved in RME 4.0 SP2, RME 4.0 SP1 and RME 4.0

Obtaining Documentation

Cisco.com

Product Documentation DVD

Ordering Documentation

Documentation Feedback

Cisco Product Security Overview

Reporting Security Problems in Cisco Products

Obtaining Technical Assistance

Cisco Technical Support & Documentation Website

Submitting a Service Request

Definitions of Service Request Severity

Obtaining Additional Publications and Information


Release Notes for Resource Manager Essentials 4.0.3 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.0.3 on Windows.

These Release Notes provide:

New Features

Product Documentation

Additional Information Online

Caveats

Known Problems in RME 4.0.3

Resolved Problems in RME 4.0.3

Obtaining Documentation

Documentation Feedback

Obtaining Technical Assistance

Obtaining Additional Publications and Information

New Features

This section discusses the new features in RME 4.x releases.

RME 4.0.1 (RME 4.0 SP1) and RME 4.0.2 (RME 4.0 SP2), the incremental releases over RME 4.0 have been rolled into RME 4.0.3 (RME 4.0 SP3).

RME 4.0.3 and RME 4.0 Service Packs 1 and 2 provide new device support, and bug fixes over the previous releases.

RME 4.0 provided new features, new device support, and bug fixes over the RME 3.x releases.

When you install RME 4.0.3, you will get all the features discussed in this section:

New Features of Inventory

New Features of Device Management

New Features of Config Editor

New Features of NetConfig

New Features for Job Approval

New Features of Reports

New Features of Syslog

New Features of Change Audit and Audit Trail

New Features of Software Management

New Features of Job Management

NetShow, Contract Connection, and SmartCase Applications

Support for SSHv2

New Device Support

The Availability module of RME 3.5 is no longer available, beginning with
RME 4.0.

New Features of Inventory

The Inventory application has the following new features:

Integration with Device and Credentials Admin (DCA) database.

All Inventory reports are now schedulable. You can run an immediate report or schedule a report to be run at a specified time.

You can schedule Inventory Collection and Polling jobs.

Periodic reports: You can schedule periodic jobs-6-hourly, 12-hourly, daily, weekly, or monthly.

Export of reports as PDF or in CSV format.

You can now export devices to a device list, from within a report.

CLI feature is now available for all system reports (excluding graphs).

New Features of Device Management

The Device Management application has the following new features:

Import devices from Common Services Device and Credential Repository.

You add devices to RME either manually or automatically. Before adding devices to RME you must add devices into Device and Credential Repository using Common Services > Device and Credentials > Device Management.

You add devices in two ways:

Adding Devices to RME Manually

Adding Devices to RME Automatically

By default, the Automatically Manage Devices from Credential Repository option in the Device Management Settings window is enabled.

Device State Management based on device reach ability.

The device participation in RME application tasks will no longer be dependent on the device being in the Managed State as in earlier releases of RME.

Instead it depends upon the actual device information required by the application task. This change allows RME to better and more flexibly, meet requirements for performing tasks on devices that have not yet been deployed on the network.

Add RME specific device attributes such as retry counts, timeouts, etc., at per device level.

You can either set a default device attributes value for all RME devices or set different device attributes value for different RME devices.

The RME device attributes includes Serial Number, SNMP timeout, SNMP retry, Telnet timeout, and RME server ID (NAT ID).

New Features of Archive Management

The Archive Management application has the following new features:

Baseline Template

You can compare the baseline template with the configuration of devices in the archive. You can also generate a non-compliance configuration report and deploy this template on to the devices to make it compliant.

VLAN configuration is archived independently

VLAN configuration is archived as a separate configuration type. That is, the running configuration and the VLAN configuration files are not archived in pairs.

Job based Archive Management tasks

All Archive Management tasks on the device, fetch and deploy are job based. You can specify when you want to run the Archive Management jobs. That is, the job can be run immediately, once or periodically. You can configure to send e-mail messages at the beginning and at the end of the job.

Manual Update of Configuration

You can manually update the configuration archive to check specified devices for changes to the configuration file.

Enhanced Search Archive

You can search the archive for configuration containing text patterns for selected devices. You can specify ten different combinations of patterns/strings as part of search criteria. You can also create custom queries and use them whenever required.

Graphical view of configuration versions

You can view all configuration versions of the selected devices in the form of a graphical display. You can also perform a Configuration Quick Deploy operation for a selected device.

Support for new protocols -SCP, HTTPS.

Check the configuration archival status using the Device Center.

New Features of Config Editor

The Config Editor application has the following new features:

Multiple user editing of configuration files simultaneously.

Baseline configuration creation using baseline templates.

External configuration files editing.

Interface to syntax checker.

Masking credentials.

Enable password option in job based password.

Additional protocol support for Configuration Deploy jobs.

New Features of NetConfig

The NetConfig application has the following new features:

Parameterized User-defined templates

These allow configuration commands in the User Defined Templates to contain user-defined variables. You can enter values for the variables in a text file during the job creation time.

Periodic Netconfig jobs

Netconfig jobs can be scheduled with periodicity of Daily, Weekly, Monthly and Last Day Of Month. Each instance of periodic schedule is maintained and can be accessed from the job browser.

Cisco MetaData Framework (MDF) support for User-defined Templates

User-defined templates can be created with more granularity by mapping them to one or more device types represented through MDF. Thus a job can now include different categories of devices.

Additional protocol support for Configuration Deploy jobs

Netconfig jobs can use any of the protocol supported by Config Management for deploying configuration change jobs.

You can import, or export of user-defined tasks.

The cwcli netconfig CLI supports user-defined tasks.

New Features for Job Approval

The Job Approval application has the following new features:

Separate approval policies for each application.

Instead of assigning approver-list during each job creation flow, now it can be assigned once for each application.

Approver has the option to change the schedule of a job before approving.

Common Services Approvers can be directly synced during the Approver list creation.

New Features of Reports

The Reports application has the following new features:

You can schedule all reports (except Inventory graphs and Audit Trail report.)

You can perform reporting tasks such as:

Generating reports

Managing reports jobs and archived reports

Creating custom report templates

You can purge report jobs and archives purging to manage disk space.

New Features of Syslog

The Syslog application has the following new features:

Many Collectors and many Analyzers

Syslog processing load can be better balanced by subscribing any number of Syslog Servers to any number of Syslog Collectors.

Easy Timezone support

Syslog Analyzer supports any timezone, by enabling you to edit the configuration file.

Drop/Keep filtering

Filtering can be to keep or to drop Syslogs. Filtering now has the capability to consider interfaces also.

Syslog reports can be scheduled.

Automated Actions now provide a template for e-mail.

Import/Export of Automated Actions and Message Filters is possible.

Force Purge capability is available.

Syslog backup new feature enables you to keep older messages.

New Features of Change Audit and Audit Trail

The Change Audit application has the following new features:

Audit Trail

The Audit Trail application tracks and reports changes that the RME administrator makes on the RME server.

Export Change Audit record in XML format

You can export the Change Audit record in XML format using the cwcli export changeaudit command.

Change Audit report

You can schedule to run Change Audit reports periodically.

New Features of Software Management

The Software Management application has the following new features:

Concurrent Image download

You have the provision for scheduling parallel device upgrades in single distribution job.

Distribute by device in Expert mode

Distribute by device (advanced) workflow provides a quick job creation wizard for advanced Network Management users.

Add image from URL

You can download images from a remote HTTP server by providing the URL.

Support for new protocols —SCP, HTTP.

New Features of Job Management

The Job Management application has the following new features:

Separate approval policies for each application.

Instead of assigning approver-list during each job creation flow, now it can be assigned once for each application.

Approver has the option to change the schedule of a job before approving.

NetShow, Contract Connection, and SmartCase Applications

These applications are also available in RME 4.x:

NetShow—Enables you to define command sets with show commands and run these commands on devices.

Contract Connection—Enables you to verify the service contracts for your Cisco IOS devices. You can also view the contract details of those devices.

SmartCase—SmartCase enables to open, query or update a TAC Service request.

Support for SSHv2

RME 4.x supports Secure Shell Version 2 (SSHv2).

When you select the SSH protocol for the RME applications (Configuration Archive, NetConfig, Config Editor, NetShow and Software Management) the underlying transport mechanism checks whether the device is running SSHv2.

If so, it tries to connect to the device using SSHv2.

If the device does not run SSHv2 and runs only SSHv1 then it connects to the device through SSHv1.

If the device runs both SSHv2 and SSHv1, then it connects to the device using SSHv2.

If a problem occurs while connecting to the device using SSHv2, then it does not fall back to SSHv1 for the device that is being accessed.

Some useful URLs on configuring SSHv2 are:

Configuring Secure Shell on Routers and Switches Running Cisco IOS:

http://www.cisco.com/warp/public/707/ssh.shtml

How to Configure SSH on Catalyst Switches Running Catalyst OS:

http://www.cisco.com/en/US/tech/tk583/tk617/
technologies_tech_note09186a0080094314.shtml

Configuring the Secure Shell Daemon Protocol on CSS:

http://www.cisco.com/en/US/partner/products/hw/contnetw/ps792/
products_configuration_guide_chapter09186a00801eea45.html#1105358

Configuration Examples and TechNotes:

http://www.cisco.com/en/US/tech/tk583/tk617/
tech_configuration_examples_list.html

http://www.cisco.com/univercd/cc/td/doc/product/software/ios123/
123newft/123t/123t_4/gt_ssh2.htm

New Device Support

For a list of all devices supported in RME 4.0.3 (RME 4.0 Service Pack 3), including devices supported in previous versions of RME, see the Supported Device Table for Resource Manager Essentials 4.0.3 on Cisco.com:

http://www.cisco.com/univercd/cc/td/doc/product/rtrmgmt/cw2000/cw2000e/
e_4_x/4_0_3/sdt/index.htm

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 CD:

Installation and Setup Guide for Resource Manager Essentials on Windows

User Guide for Resource Manager Essentials


Note Adobe Acrobat Reader 4.0 or later is required.


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

Installation and Set Up Guide for Resource Manager Essentials on Windows (DOC-7817223=)—Provides installation instructions, including both server and client system requirements, steps for installing and uninstalling, and installation troubleshooting information.

User Guide for Resource Manager Essentials (DOC-7817221=)Provides information on using RME 4.0.3.

User Guide for Common Services (DOC-7817182=)—Provides information about setting up, administering, and accessing CiscoWorks Common Services 3.0.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. 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.0.3, and the procedures mentioned in this document, see the User Guide for Resource Manager Essentials.

Additional Information Online

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

http://www.cisco.com/univercd/cc/td/doc/product/rtrmgmt/cw2000/cw2000e/
e_4_x/4_0_3/sdt/index.htm


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


The Incremental Device Update (IDU) for RME 4.0.3 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 IDU for RME 4.0.3 from:

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

Caveats

The following are some caveats:

If the RME Installer window does not appear after you have inserted the
RME 4.0.3 CD-ROM into the CD-ROM drive, do the following:

a. On your desktop, select Start > Run.

The Run dialog box opens.

b. In the Open field, enter drive:\RME\autorun.exe.

where drive is the CD-ROM drive letter.

Before installing RME, ensure that you do not have CWSI Campus 2.x or Cisco Voice Manager on the system.

Before upgrading RME, ensure that all applications are stopped. The upgrade depends on having reasonable interaction time with the database. If this is not possible, the upgrade fails.

Browsers running on remote X servers are not supported in RME.

If you stop the Daemon Manager, you should wait for 5 minutes before restarting it. Wait for 5 more minutes before performing any tasks. This will ensure that the processes are initialized correctly.

Known Problems in RME 4.0.3

RME 4.0.1 (RME 4.0 SP1) and RME 4.0.2 (RME 4.0 SP2), the incremental releases over RME 4.0 have been rolled into RME 4.0.3 (RME 4.0 SP3).

This section contains the following known problems for RME 4.0.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

cwcli export Known Problems

Contract Connection Known Problems

Bug Toolkit Known Problems

Server, Browser, 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 Then select the Software sub-section and click Bug Toolkit.


Installation and Upgrade Known Problems

Table 1 Installation and Upgrade Known Problems 

Bug ID
Summary
Explanation
RME 4.0.3
   

CSCsc19725

Error in RME install log

While installing or upgrading to RME 4.0.3, the following error is appears in the install log:

INFO: System RAM is: >
ERROR: Failed to convert the string to Number
Return value of CheckSystemRam is 0

Workaround:

None.

You can ignore this error.

CSCsc46237

Restore fails even when there is adequate space

RME restore operation fails with an insufficient disk space error.

While restoring, the backup data is extracted in the partition where the backup exists. Therefore, if the partition does not have enough space, the insufficient disk space error appears.

Workaround:

Either increase the partition space or copy the backup to a different partition that has enough space.

RME 4.0 SP2
   

CSCsb36922

RME installation does not proceed if the Task scheduler not enabled.

RME installation waits with the message displayed as:
Please be patient. Installing Device Packages(RME) may take some time.

This problem occurs if the Schedule or Task scheduler on the RME server is not enabled.

Workaround:

1. Copy
NMSROOT\temp\rme_cids_pkgs\*zip to some location folder such as C:\DevicePkgs

To make the installation proceed further, create a blank file, PSUCli.done under NMSROOT\bin\

NMSROOT is the install directory.

2. After the installation is over, stop the daemon manager and follow these steps in command line.

3. Change directory to NMSROOT\bin

4. Run the command
PSUCli.bat -p rme -src c:\DevicePkgs -all -i -noServerRestart

5. After the device packages installation over, start the daemon manger.

RME 4.0
   

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

Users with Approver and Network Operator roles cannot edit or delete device groups in RME 4.0 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.

Workaround:

None.

CSCsa33365

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

After migration from RME 3.x to RME 4.0, a user with a Network Administrator role cannot edit/delete groups in RME 4.0 that the user 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.0.

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

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.0 server after data migration. An error appears, Internal Error: Config File information not available.

Workaround:

None.

CSCsa45325

No able to upgrade fromRME 3.4 to RME 4.0 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.0.

CSCsa22623

Data inconsistency on restoring data backed up with jobs in running state.

After restoring RME 4.0 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/Restore command does not backup/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.


Administrator Known Problems

Table 2 Administrator Known Problems 

Bug ID
Summary
Explanation
RME 4.0
   

None

Some of the RME processes are suspended.

If you start RME 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
RME 4.0.3
   

CSCsc47973

ACS integration with NDG gives devices access

This problem occurs when you use Resource Manager Essentials 4.0 SP2 (or later) and Cisco ACS 3.3.2 software (not the ACS appliance).

If you have the privilege to manage a particular Network Device Group (NDG) in Cisco Secure ACS, you are able to view the same NDG in RME, when RME is integrated with Cisco Secure ACS.

However, if you access the RME Devices option (RME > Devices > Device Management > RME Devices) then you are able to see all devices belonging to other NDGs. You can also add or edit devices from other NDGs.

If you select any option other than RME Devices, for example Normal Devices, you are able to view only those devices belonging to your NDG.

Workaround:

None.

CSCsc12079

GUI of Device Management State Summary is not updated

This problem occurs with Resource Manager Essentials 4.0 SP2 (or later).

The Device Management State Summary page (RME > Devices > Device Management) does not get updated, and displays incorrect information.

The information in the summary page remains incorrect. When you click on a device number, it does not match with number displayed on the device details dialog box.

Workaround:

None.

CSCsc17381

Device Center: Check Device Credentials do not return results.

In the Device Center, if you click Check Device Credentials under Management Tasks, it takes an unusually long time to return results.

In some cases, the results are not displayed and all the fields in the report state: No data yet.

Workaround:

None.

RME 4.0
   

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 but later on 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.0 and therefore there is no workaround.

CSCed47422

Device Management State Summary show wrong record count.

A label on right top of 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 are adding 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 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
RME 4.0
   

CSCdv62510

Config Fetch using TFTP fails for 800 series devices.

This happens on devices running IOS Release versions greater than 12.0.

Workaround:

Use Telnet to fetch or download files.

CSCdv64195

Unable to add Route Switch Modules (RSM) into RME when used memory reaches 4GB.

The problem occurs in the following scenarios:

The datatype used is integer. In this case, Inventory cannot handle a value of 4GB in the database column.

SNMP counter error. In this case, an error happens when used memory reaches 4GB, which happens when the device is up for a long time

The same error is reported in CSCdu09377.

Workaround

Reload the device to reset the SNMP counters.

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/univercd/cc/td/doc/product/rtrmgmt/cw2000/cw2000e/
e_4_x/4_0_3/sdt/index.htm

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/univercd/cc/td/doc/product/rtrmgmt/cw2000/cw2000e/
e_4_x/4_0_3/sdt/index.htm

CSCsa29075

The device boots with, but does not work on Image.ROM Version

ROMSysVersion is not returned by RME 4.0

This happens when the device is configured with SNMP.

Workaround:

None.

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
RME 4.0.3
   

CSCsc37630

System Inventory Collection and Polling jobs fail

The System Inventory Collection and Polling tasks do not scan any devices on the system.

RME flags the job as Successful, but does not scan any devices on the system.This happens when the CiscoWorks server is configured for Cisco Secure ACS.

Workaround:

None.

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.

CSCsc31440

RME detailed device report shows incorrect serial number for Cat2950

RME reports incorrect serial number information in detailed device reports for the Catalyst 2950 switches.

This is because RME polls chassisId in OLD-CISCO-CHASSIS-MIB.

However, the serial number information is available in entPhysicalSerialNum of the ENTITY-MIB which is what RME should use.

Workaround:

Hard code the chassis-id using the CLI on the 2950:

conf t

snmp-server chassis-id the-real-serial-number

where the-real-serial-number is the Serial Number.

CSCsb87660

Changing Inventory job schedule may cause duplicate jobs

Duplicate entries may appear for system RME inventory jobs, when you try to change the job schedule.

Workaround:

Use the job CLI to delete any unwanted jobs.

On Windows replace NMSROOT with the CiscoWorks install directory, for example, C:\Program Files\CSCOpx).

1. Navigate to NMSROOT\bin

2. At the command prompt enter:

cwjava -cw NMSROOT com.cisco.nm.cmf.jrm.jobcli delete unwanted_job_id

(where unwanted_job_id is the ID of the job you want to delete.)

3. Then restart the daemons using these commands:

net stop crmdmgtd
net start crmdmgtd

RME 4.0 SP2
   

CSCsb40088

The Inventory > Hardware Report does not populate RAM, NVRAM, Used NVRAM fields for most CatOS switches RME 4.0.1

Inventory data is collected from StackMib. This does not have NVRamSize, RAM Size and Used NVRAM attributes.

These attributes need to be collected using EntityExtMIB or OCCM. However, the reports code is refers to EntityExtension MIB. Hence, these fields appear blank.

Workaround:

None

CSCsb50677

Device categorization of Router 1801 and 1802 appear incorrectly in Device Credentials Repository.

Cisco 1800 series Integrated Services Routers 1801 and 1802 are mapped under 1811 and 1812, respectively in Device and Credential Repository.

Workaround:

Patch will be posted on to Cisco.com.

RME 4.0 SP1
   

CSCsb00224

WS-SVC-NAM-1 is displayed as Generic class in Chassis Summary Graph

NAM-1 device chassis type WS-SVC-NAM-1 is classified as Generic in Chassis Summary Graph.

The containment collection for this device is not supported. Therefore, the vendor type is not available to the application to classify the device chassis type appropriately.

Workaround:

None.

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

Note 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 or the RME 4.0.3 Online help.

RME 4.0
   

None

Desktop machines appear incorrectly.

Do not import desktop machines unless they are running Cisco Call Manager applications. Otherwise, desktop machines appear incorrectly in the device selector under Call Managers.

Workaround:

None

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:

You must 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.

CSCdk35153

Chassis modem table is not polled correctly.

Inventory reports show only configured modems. An interval exists between modem installation and modem configuration.

During this interval, the Inventory application might detect only one modem. Additionally, log messages might display database integrity violations.

These messages can be ignored.

Workaround:

1. Go to the device and configure the modem.

2. Reacquire the inventory data.

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

CSCdp61331

Comma included in password will cause device import to fail.

In comma separated value (CSV) format, the "," character is used as a delimiter. Therefore, fields in the CSV file should not contain the "," character.

If you use a "," character in the password or other fields while adding a device, the CSV file generated after exporting will be invalid.

An exported CSV file cannot be used for importing devices.

Workaround:

None

CSCdr81211

When a hitherto managed device is disconnected from the network, Scheduler does not report the status as Not Responding.

After a device has been managed using RME, it will not report the status as Unmanaged or Not Responding.

Workaround:

Manually delete the device from the inventory.

CSCds48244

Import operations fail for 7100 and 7200 routers because of an IOS bug.

Import operations may fail for Cisco 7100 and 7200 routers because of SNMP timeout.

Workaround:

1. Select Resource Manager Essentials > Administration > System Configuration

2. Increase Slow SNMP Timeout to a value more than 60 seconds.

CSCsa34114

Sysadmin privileges to generate reports is not restricted.

A user with Approval role, and a sysadmin user are not restricted from generating reports for inventory, Syslog, change audit etc.

Workaround:

None.

CSCsa36663

Location of archived reports cannot be changed.

All reporting application archives are stored at a predefined location and you are not given an option to change it.

After the disk is full with archived files, further jobs fail.

Workaround:

None.

CSCsa17340

Inventory Collection fails for Cisco Catalyst 2926 Device.

The device and the version of Catalyst Operating System (WS-C2926 and CatOS release 3.x) used by this device are no longer supported.

Owing to this, Inventory Collection fails for the device.

Workaround:

None.

CSCsa21492

Software Image information incomplete for Cisco Catalyst 4503 Switch.

The software Image information is incomplete for Cisco Catalyst 4503 switch.

This is because CW_MIN_DRAM, CW_MIN_NVRAM, and CW_MIN_BOOTFLASH are missing in the ciscoImageString for 4503 device.

Workaround:

None.

CSCsa33691

Image information missing for Cisco MGX 8220.

All the images information for Cisco MGX 8220 are not collected.

Workaround:

None.

CSCsa36025

Inventory Collection fails for Cisco 7010 Router.

RME 4.0 does not support Cisco 7010 Router and hence, inventory collection is not performed on the device.

Workaround:

None.

CSCsa41634

Inventory Collection fails for Cisco ONS 15530.

Inventory collection fails for the above device with the error message:

ASA Error - 195 column Physical ElementID 
in table Physical AssetData cannot be NULL

Workaround:

None.

CSCsa29425

Poller returns incorrect values for Cisco 7609 router.

The poller returns incorrect values for Cisco 7609 router when the image version of the device is 12.2(17d)SXB1.

Workaround:

None.

CSCsa33704

In the Change Audit report, Inventory change details do not appear

After migrating from RME 3.4 to RME 4.0, when you click Inventory change details, no details appear.

Workaround:

None.

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.

CSCsa18445

Editing the Value field of custom report template using Netscape is difficult.

In the template creation dialog box for Inventory, when you select Group as UDF, attr as anything, Operator as anything, you will see that Value is set to All by default.

It is very difficult to type in anything that has the letter "A" because it automatically selects All.

Workaround:

Reselect the text you need to change and continue typing.

CSCsa27682

Custom group creation based on numeric attributes does not work for = operator.

This happens when the values are taken from reports which have more than two decimal values.

Workaround:

1. When real numbers comparison is required, use > or < as operators for creating custom groups instead of = operator.

2. You can round the value up to 2 decimal values and use the same for Custom group creation flow.

CSCsa32184

Inventory reports are affected by cross site scripting vulnerability.

If a user-defined field contains a string such as:

<html><body><p>hello</p><script>alert ("You 
have found XSS bug") 
</script></body></html>

instead of a plain text string, a malicious script is executed when you run an inventory report containing user-defined field.

Workaround:

None.

CSCsa33612

Report rendering does not handle special characters.

The report display format gets disturbed when a device attribute is configured with a malicious script (html or java) intentionally or unintentionally.

Workaround:

None.

CSCsa33994

Data extraction for Cisco Catalyst 4006 Switch has incomplete information.

Data extraction for Cisco Catalyst 4006 Switch running IOS has the following improper information:

Software identity has no firmware information.

There is no Cisco Flash device.

There is no Cisco port under the Cisco card.

There are no ports under the Cisco network element.

Workaround:

None.

CSCsa34243

Data extraction for Cisco Catalyst 4507 Switch has incomplete information.

Data extraction for Cisco Catalyst 4006 Switch running IOS has the following improper information:

Software identity has no firmware information.

There is no Cisco Flash device.

There is no Cisco port under the Cisco card.

There are no ports under the Cisco network element.

Workaround:

None.

CSCin15464

Card and Flash details are missing for older version Router 12000

Card and Flash Details do not get exported for 12000 series routers with older IOS versions.

Workaround:

For 12000 series routers, only newer IOS images that support CISCO-ENTITY-EXT-MIB will be supported.

For more details on the IOS images supported by the CISCO-ENTITY-EXT-MIB, go to the URL:

http://tools.cisco.com/ITDIT/MIBS/servlet/index

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.

CSCsa14976

Flash information is not populated for 7304 device

If the IOS version running on the device is Version 12.1(9)EX2, EARLY DEPLOYMENT RELEASE SOFTWARE, it likely that the FlashAG collection fails at times.

Workaround:

Reboot the device.

CSCsa23146

Inventory does not collect the Flash information 6015 IPDSL device.

Device fails FlashAG collection when the device is configured for SNMP.

This happens because the device does not support Old-Cisco-Flash-Mib and Cisco-Flash-Mib.

Workaround:

None.

CSCsa16769

Incomplete rule accepted for custom template creation.

This problem occurs when you are creating a Custom Report Template using the Resource Manager Essentials > Reports > Custom Reports Templates, Create flow.

If the rule you are adding in the Custom Template Rules dialog box is the second rule or thereafter, even without entering any Operator and Value, you can create a rule.

If you:

1. Add only Association, Inventory Group, and Attribute,

2. Click Add, leaving the Operator and Value fields blank.

The rule is added to the template.

Workaround:

No workaround is required to generate the report, because you can see the operator in the Rules List.

Without any rule (operator and value), the rule will be considered as All (for string equals:ALL, for numeric attributes it is considered as =ALL).

1. If you want to modify the template, you can do it using the Edit flow from the Reports > Inventory Custom Templates dialog box:

1. Select the rule that you want to modify.

2. Enter the operator and value.

3. Click Modify.

4. Complete the template edit flow.

See the User Guide for Resource Manager Essentials for procedures.

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.

CSCsa37995

AP1200 Device Credential Verification reports Telnet as incorrect.

Even when you enter the correct Telnet credential and invoke Device Credential Verification for AP1200 device, Device Credential Verification reports this as incorrect.

Workaround:

None

CSCsa33955

Device Credential Verification reports incorrect status for write community string.

When a wrong SNMP Write credential is entered, Device Credential Verification reports the status as Failed instead of Incorrect.

Workaround:

None.

CSCsa23936

Check Device Attributes (CDA) for CDM 4630 reports correct Telnet credentials as Failed.

Even if you have configured the correct Telnet credentials, Device Credential Verification reports the credentials as Failed, if TACACS is configured on the device.

Workaround:

None.

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.

The condition under which this problem occurs is that both Telnet Username and Password are not provided in Device and Credential Repository.

Workaround:

None.


Archive Management Known Problems

Table 6 Archive Management Known Problems 

Bug ID
Summary
Explanation
RME 4.0.3
   

CSCsb68389

Config Export returns Permission Denied

Config Export returns Permission Denied although the corresponding entry for the folder is added in the Property file.

When you click the Browse Button in the Export browser, all entries of the Property DCMACONFIGEXPORT_AllowedFolders appear with the pipe symbol(|).

Workaround:

Manually edit the file name.

CSCsb68389

(Continued)

 

You can change the default export directory by modifying the AllowedFolders.properties file. To modify this file, follow this procedure:

1. Go to the folder NMSROOT\MDC\tomcat\webapps\rme\
WEB-INF\classes\com\cisco\nm\
rmeng\util

Where, NMSROOT is the CiscoWorks Installed directory. By default the installed directory on Windows is
C:\Program Files\CSCOpx.

2. Go to the line that contains the attribute,
DCMACONFIGEXPORT_AllowedFolders.

3. Append the new location at the end of the line by using pipe (|). There should not be any space before or after the pipe (|).

For example: If the new location is, d:\export, append the new location,

DCMACONFIGEXPORT_AllowedFolders : DATADIR/rme/dcma/configexport|d:/export

For the location specified by you, casuser should have Full Control in Windows.

CSCsb86166

Ability to ignore VLAN-PRIMARY lacking in Change Audit

Change Audit reports numerous VLAN-RUNNING entries.

This happens because vlan.dat is a binary file, and therefore Configuration Archive cannot do a comparison.

Each time Configuration Archive does a comparison, it fails, and vlan.dat is archived.

Whenever vlan.dat is archived, a change audit record is created.

Workaround:

None.

CSCsb69323

Change Audit record is not logged when copy running configuration to startup configuration.

A Change Audit record is not created when the running configuration is successfully copied to the startup configuration.

This happens when you:

1. Launch RME > Config Mgmt > Out of Sync Summary.

2. Select a device that has a difference between its running configuration and startup configuration.

3. Click Sync on Device and ensure that the job has completed successfully.

The change in startup configuration is not logged in the Change Audit Report.

A Change Audit record is also not created for a successful cwcli config run2start job.

Workaround:

None.

RME 4.0 SP 2
   

CSCsb23687

TFTP Fetch/Download failed for new MIB in Cisco Content Services Switch.

You cannot fetch or download the configuration using TFTP protocol

This problem will occur when users select the TFTP protocol alone for the Fetch and Download operations.

Workaround:

Use Telnet or SSH protocol for fetch and download operations.

RME 4.0 SP1
   

CSCsa73651

Wrong Job options are displayed in the Work Order page for Retry job

The wrong job options are displayed in the Work Order page for a Retry job under these conditions:

1. You create a NetShow or a NetConfig job with the Job Password option disabled in the Job Schedule Page.

The job fails with a mix of successful and failed devices.

2. You retry the job after enabling the Job Password option in the Job Schedule page.

After the job completes, when you open the Job Details page and check the Work Order page, the Job Password option appears as Disabled.

This occurs because you had disabled the Job Password option when the job was run earlier.

Workaround:

None.

CSCsa73022

WS-C2948G-GE-TX: Configuration Fetch or Deploy operations fail with TFTP.

Configuration Fetch and Deploy operations fail for WC-C2948G-GE-TX when you use TFTP.

This occurs even when you have set the Telnet and SNMP time-out values to the maximum limits and the timeout_for_slow_devices flag is set as true in the regdaemon.xml file.

Workaround:

None.

CSCsb02036

CLI output is not displayed for PIX write2start jobs when you use SSH as the transport protocol.

When you run a write2start job on a PIX device using SSH as the transport protocol, you may not be able to see the CLI output for that job.

Workaround:

None.

CSCsa97147

Config Poller shows success without any value for RO/RW community strings in DCR.

Poller-based configuration Fetch is successful with no values entered for Read-Only (RO) or Read-Write (RW) community strings in Device and Credential Repository (DCR).

This occurs when there are no SNMP strings configured in DCR, and the Config Poller uses these default values (public and private) for SNMP RO and RW.

Workaround:

Ensure that you have configured the correct values for SNMP RO and SNMP RW in the device.

For details see the User Guide for Common Services.

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 or the RME 4.0 SP1 Online help.

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, which 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.

CSCsa68935

? command download is not handled

? command download fails when you run the ? command on Content Engine devices.

Workaround:

None.

CSCsb04066

VPN3080: Put job fails—Deploy is successful, fetch fails

When you download commands which change the policy settings of VPN devices, after a successful download operation, the Sych Archive operation may fail.

This is because the configuration of policy commands closes the VPN session. Also, the and the handshake between the RME server and the device fails.

Therefore the Fetch operation is not initiated.

Workaround:

You can, initiate a manual Synch Archive operation, after a successful download.

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

RME 4.0
   

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, provided the module has same credentials with Supervisor. Other protocols are not supported.

Workaround:

None.

CSCds68827

Syslog messages archived in the Configuration archive

Telnet retrieves all the information that is displayed in the Telnet session when you try to fetch configuration using Telnet.

If logging is enabled for sessions, Syslog messages displayed on the Telnet session are also archived along with the configuration.

Workaround:

Turn off the display of Syslog messages on the Telnet session before fetching configurations using Telnet.

CSCdt24115

Catalyst 5000 Devices: Transport FallBack from TFTP to Telnet Fails.

Catalyst 5000 device displays:

Device is busy with previous operation, Try 
later.

when you perform a Config Fetch operation.

The device going into busy state is a feature of the Catalyst 5000 switches.

This is to prevent too many TFTP/Telnet connections within short intervals of time.

Workaround:

Change Transport Order to specify Telnet as the first protocol.

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.

CSCsa16259

Configuration download fails for Cisco 3660 Router.

Configuration download fails for Cisco 3660 Router with the message:

Transport session to device failed

This failure happens in the Merge mode although the device credentials are correct.

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 configuration file.

CSCsa38392

Archive Mgmt scheduled jobs retain old display names.

The Archive Management Job Details page sometimes shows old names of managed devices.

This happens when the display name of the device changes after the job execution begins.

In the case of periodic jobs, if the device name changes after the job is created, all instances of the job continue to show the old name.

Workaround:

Recreate the job.

CSCsa36000

Device link for Partially Successful devices is not Enabled

Status links in the Job Details page are either disabled or they do not invoke the Details page.

This happens when you:

1. Click the Job ID and the Job Details page is launched.

Partially Successful Devices, Failed devices, Successful devices appear

2. Click the status links in the Partially Successful devices,

No page appears.

Workaround:

1. Click on any one of the status links under Failed or Successful devices

2. Click the partially successful devices again.

The Details page appears.

CSCsa17778

Configuration archival fails in a mounted file system.

Archival of configurations does not occur on the mounted/mapped drives on Windows.

This happens when the default archive location is changed to the mapped network drive on Windows.

Workaround:

Restore it to the default location or change to another location on the local hard disk.

CSCsa35699

VPN configs coloring scheme is incorrect for Compare Configs.

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

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

Workaround:

None.

CSCsa37473

Issue in Config for device CSS 11050

Archived configuration does not contain the complete running configuration.

This occurs happens when the image on the device is Content Switch SW Version 5.02 Build 3 with SNMPv1/v2c Agent.

This happens when configuration fetch is tried with both Telnet and TFTP protocols.

Workaround:

None.

CSCsa51073

Compare config report with Raw mode shows incorrect data for ACLs.

In the Raw mode, the order of commands in the config compare reports may not be the same as in the archived file.

While trying to compare configurations, if you have same commands appearing under different sections in two versions, the order can be different in the Raw mode, with the All option

Workaround:

Ignore the error in the Raw mode diff and use the Processed mode, which is more refined, to view such changes. There is no change in the order in the archived file—this is only an issue in the user interface.

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 using the Startup or Running hyperlinks respectively at Resource Manager Essentials > Config Mgmt > Archive Mgmt > Version Summary.

CSCsa45567

DM, Inventory and ConfigArchive applications are out-of-sync with reference to the number of devices managed

The number of devices shown in Archive Status screen of Archive Management may be more than the number of devices managed in RME.

This can happen when the devices are deleted while config collection is in progress.

Workaround:

None.

CSCsa56349

Baseline compare need not be case sensitive.

Baseline Compliance flags a configuration as non-compliant although the command is present in the configuration.

This may occur when there is difference in case between the commands in the template and the commands in the configuration file of the device. IOS is case insensitive and hence you may have entered the commands in the template under this assumption.

Workaround:

Ensure that you use the same case in the commands in the template and the configuration on the device.


NetConfig Known Problems

Table 7 NetConfig Known Problems 

Bug ID
Summary
Explanation
RME 4.0 SP1
   

CSCsa98053

Deselecting NetConfig tasks removes the associated task instances

In the NetConfig Jobs edit flow (Resource Manager Essentials > Config Mgmt > NetConfig > NetConfig Jobs) in the Devices and Tasks page, if you deselect a task, its instances will not be displayed in the Add Tasks page (next page).

If you return to the Device and Tasks page, re-select the task, and then navigate to the Add tasks page again, the instances that you had created earlier, will not re-appear.

When you deselect a NetConfig task all the instances that were added previously are deleted. This may occur when you copy or retry jobs.

Workaround:

Select the task and re-create the instances.

To create instances of tasks, see the User Guide for Resource Manager Essentials or the RME 4.0.3 Online help.

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., (which are ideally a part of the command output during error conditions only).

Workaround:

None.

CSCsa88089

Job Details page: Edit/Copy/Retry/Stop/Delete buttons missing

Edit/Copy/Retry/Stop or Delete buttons are missing from the Job Details page.

Workaround:

Use the buttons in the Job Browser page.

CSCsa88829

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

RME 4.0
   

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 have two different templates changing 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.

CSCsa42117

Config jobs scheduled to run after RME evaluation license expiry period.

This happens when all Configuration jobs fail to run after the license expire.

However, the reason for Job Execution failure is not captured in Archive Management application Job Browser and Job Details windows.

Workaround:

After the license expires, view the Job Status message using Common Services > Server > Admin > Job Browser.

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

CSCsa26931

Pattern matching does not work for the values that are space-separated.

This happens when any command in the configuration file has a space. Compliance report may flag a non-compliance issue although you have entered a command in the configuration file.

For example, even if you enter + banner motd [msg] in the template and <cmd> banner motd "Good Morning" exists, Compliance reports an error. This is because it assumes that the string after the space is an extra parameter in a command.

Workaround:

Give the exact command and do not use parameter-based commands in such cases.

CSCsa36283

The Edit and Save instance, after adding a new device category, gives incorrect results.

The problem occurs in this scenario:

1. During job creation, select devices belonging to a category.

2. Go to the next step and add the task instances.

3. Return to the Device Selector and select devices belonging to another category.

4. Proceed with job creation.

Here, the newly added devices will not have any commands to download.

This happens when devices belonging to different categories are added.

Workaround:

1. Delete the task instance that you added previously.

2. Add it again.

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.


Config Editor Known Problems

Table 8 Config Editor Known Problems 

Bug ID
Summary
Explanation
RME 4.0.3
   

CSCsc02023

DCR is not updated after executing Config Editor job, in RME 4.0 SP2

When you run the job to change the SNMP community strings, the SNMP strings are changed on the device, however, Device Credentials Repository is not updated.

This occurs if you have installed RME 4.0 Service Pack 2.

Workaround:

None

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.

CSCsa14126

Older device credential shown in clear text

This problem occurs for all device credentials when you:

1. Open a configuration file for editing using Config Editor application.

In the Credentials pane (Config Editor dialog box), the masked credentials appear. These credentials are hyperlinked.

2. Click on hyperlinked credentials.

The Modify Credentials dialog box appears.

The old device credential appears in clear text in the Old Credential text field.

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.

CSCsa30243

Commands not in proper configlet

This happens when you:

1. Create a baseline template in the Advanced mode (Resource Manager Essentials > Config Mgmt > Archive Mgmt >
Baseline Templates > Create).

2. Open the baseline template using Config Editor.

3. Edit and save the baseline template in the Public location.

4. Open the saved baseline config from the Public location in the Processed mode.

Some of the commands are shown in incorrect configlets.

Workaround:

To edit Baseline Template in commandlet format use Resource Manager Essentials > Config
Mgmt > Archive Mgmt > Baseline Templates > Edit.

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.


Netshow Known Problems

Table 9 Netshow Known Problems 

Bug ID
Summary
Explanation
RME 4.0 SP2
   

CSCsb43125

RME database does not update the CommandSet details after migration

RME database does not update the CommandSet details after migration

This is caused by the character '+' in the Command Set name RME3.4+IDU11.0. NetShow in RME 4.0.x UI does not allow this character.

Workaround:

Before taking a backup in RME3.x, make sure that none of the CommandSet names have special characters.

RME 4.0 SP1
   

CSCsa67327

Netshow Admin options appear under Config Mgmt.

NetShow Admin settings are provided in the Transport Settings page under Resource Manager Essentials > Admin > Config Mgmt although NetShow is listed under Resource Manager Essentials > Tools.

NetShow uses the APIs provided by ArchiveManagement and ConfigJob. Therefore the Admin settings are listed under Config Management.

Workaround:

None.

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.0 SP1.

These isolated custom commands do not exist in RME 4.0 SP1 NetShow after migration.

Workaround:

You can associate these isolated custom commands with any user-defined command set in RME 3.x, before taking a backup. Then these custom commands will be migrated as if they were a 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 in this following scenario when you want to remove an adhoc command:

1. 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. The Select Device Category Page appears.

2. Click Next.

3. Now select the ad hoc command that you wish to delete, from the Selected Commands list and click Remove.

The command moves to the Available Commands list.

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

You will see an error:

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.

CSCsa73709

(Continued)

Cannot remove an Adhoc command from the Available Commands list

(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. This time when you select the command from the Available Commands list and click Delete Adhoc.

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

CSCsb09234

OutOfMemoryexception 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:

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 will be applicable to all the device types that you have selected.

For example, if you choose device types Content Networking and Router and added an Adhoc command, say A, then 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, or the RME 4.0.3 Online help


Software Management Known Problems

Table 10 Software Management Known Problems 

Bug ID
Summary
Explanation
RME 4.0.3
   

CSCsc38626

Adding an image from the network using Sync Report takes over 30 minutes.

Out-of- sync report takes over 3 to 4 minutes to load. The time taken to load increases with the number of managed devices increases.

If the number of managed devices is more than 300-400, the sync-report takes around 10 minutes. If it exceeds 1000 devices, the sync report takes around 30 minutes.

Workaround:

Use Add from Network flow without using the Out-of-Sync report option.

CSCsb71888

Software Management fails if ciscoFlashPartitionName is :flash1

Software Management does not upgrade the IOS image for the Catalyst 3560 series switches if the target name is flash1.

This occurs with:

CiscoWorks LMS2.5 / LMS2.5.1 RME4.0 (or later)

Catalyst 3560 series switches

Flash Target: flash1

Workaround:

None

CSCsb59359

Import image from subdirectory is not supported for 3750 stack device

When you use a 3750 stack device and try to import a .bin image from device, the following error appears:

SWIM0014: No images to import. If not a CLI based device, Check DDR if it has the latest information.

If not, update inventory and try the Import operation again.

This is because there are no bin images present directly under the flash directory but are present under their subdirectories.

Workaround:

1. Copy the .bin images from the flash subdirectory directly into flash directory. `

2. Retry the Import from device flow.

CSCsb65363

CiscoWorks should not boot on slave disk 0

CiscoWorks puts code on a slavedisk0 and boots off that disk. The slavedisk0 does not exist until after the device is up and running.

This occurs when you are running RME 3.5 and IDU 7.0

Workaround:

You should manually select a storage location other than the slave partitions.

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:

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 4.0 help.

Workaround:

None.

CSCsb88589

Software Management: Boot commands wrongly updated.

The Software Management job completes successfully. However, in the device configuration, the BOOT path-list is configured incorrectly.

This happens in the following conditions:

RME 4.0 (or later)

Distribution of a tar file to Catalyst 3560 series switches.

Workaround:

Manually update the configuration.

CSCsc45170

Software Management leaves RFF device in boot mode when TACACS is configured

Software Management leaves RFF device in boot mode when TACACS is configured.

This happens when:

For upgrade of RFF devices such as 2500, the device is reloaded into RxBoot mode for flash erase and image copy from the TFTP server.

TACACS is also configured on the device.

The TACACS credentials are used by RME when the device is in normal mode and it works fine.

However, when RME attempts to use the same credentials in RxBoot mode, since TACACS is not supported in RxBoot mode, login fails

Workaround:

Disable TACACS during image upgrade.

Or

Have the same set of TACACS and vty credentials for the device during upgrade process.

CSCsc04541

Import Image from Device fails when flash partition is flash:1

CiscoFlashMib returns flash:1 as the partition name, where none exists on the device. This results in problems while importing images from 2611 and 3660 routers.

Workaround:

None.

CSCsc60383

RME Software Management Distribute by Devices shows duplicate 2950 images

RME Software Management Distribute by Devices shows duplicate 2950 images under
RME > Software Management > Software Distribution

This occurs during the distribution of 2950 images, using Software Management.

Workaround:

To avoid deploying the same image twice:

1. Deselect the checkboxes for duplicate SYSTEM_SW.

2. Proceed with scheduling the job.

CSCsc60288

Distribution hangs for 3550/3750/2900 switches when using SSH and TFTP

Distribution to Catalyst 3550, 2950 and 3750 family devices takes very long time (over 2:30 hours) and fails with the following error in the distribution report:

Device upgrade timed out

This occurs when you select SSH as the connection protocol to the device and select TFTP as the copy protocol.

Workaround:

Select SCP or RCP as the copy protocol instead of TFTP.

Or

Do not select SSH as the connection protocol (in this case, Telnet will be used).

To configure SCP, see:

http://www.cisco.com/en/US/partner/products/
sw/iosswrel/ps1839/products_feature_guide09186a0080087b18.html

To configure RCP, see:

http://www.cisco.com/en/US/partner/products/
sw/cscowork/ps2073/products_user_guide_chapter09186a0080357612.html#wp1328314

RME 4.0 SP2
   

CSCsb27389

You cannot create a distribution job for Cisco Catalyst 6000 Series Dual SUP.

The Create Software Distribution task in RME does not allow you to create a software upgrade job on Cisco Catalyst 6000 Series Dual SUP devices.

An error message appears at the View Verifications stage

An unexpected error has occurred. Contact TAC and attach the swim_debug.log file.'

This problem occurs only on CAT6K Dual SUP devices when you select both the SUPs for an upgrade.

Workaround:

None.

CSCsb42968

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

This problem occurs when the image is being copied to:

1. bootflash: using TFTP or RCP.

2. Slot0: using RCP only.

Workaround:

Use Slot0: with TFTP for distribution.

RME 4.0 SP1
   

CSCsb02631

Image import job fails and displays the error Invalid data dir

The image import operation fails due to the following migration (backup/restore) issue from LMS 2.1 to LSM 2.5 (or higher).

Admin > Software Mgmt >View/Edit Preferences, shows null value for the Repository Image Location.

As default, it should have the directory location as:

NMSROOT/CSCOpx/files/rme/repository/

Sometimes, the restore operation fails because the DCRServer process does not come up.

The Restore operation prompts you to confirm whether to restore the certificate. This problem occurs if you select Y (Yes) for Certificate restore, and the certificate has expired.

Workaround:

1. Restart the daemon manager.

2. From the Common Services desktop, select Common Services > Server > Security> Single-Server Management > Certificate Setup.

3. Click Apply.

4. Stop the daemon manager and trigger the Restore operation.

During the Restore operation you should select N (No), when you are prompted to restore the Certificate.

CSCsb19581

rcp does not work for Windows 2003 Server

Image transfer using rcp protocol fails in Windows 2003.

This happens when CiscoWorks is installed on Windows 2003.

Workaround:

1. Give full permissions for the casusers group to execute cmd.exe.

2. Retry the image transfer.

CSCsb19467

Software Management distribution support missing NM-NAM in 2600/3600 Routers

The NM-NAM module in the Routers 2600 (Cisco 2600 Series Modular Access Routers) and 3600 (Cisco 3600 Series Multiservice Platforms) cannot be upgraded using Software Management.

This applies only to the NM-NAM module in these routers.

Workaround:

None.

RME 4.0
   

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.

CSCsa08734

Add Image from device fails for Cisco 7300 Series Routers.

Add image operation from the device fails for Cisco 7300 Series Routers because of an issue with Cisco-Flash-Mib implementation on the device.

This problem is seen if device runs versions 12.1(19)EX2.

Workaround:

1. Upgrade the device manually to version 12.0(S) which has the fix.

2. Perform inventory update.

3. Retry the import operation.

CSCsa16902

Image distribution to device fails for 3660, 17XX/26xx platforms

Software Image Management fails to erase Flash on Cisco 1700, 2600, and 3600 Series Routers running Cisco IOS Release 12.0(5)T1, prior to distributing the new image.

This causes the job to fail if there is no enough space on Flash and it needs to be erased.

Workaround:

Manually erase Flash before using Software Image Management to distribute a new image to the device.

CSCsa20454

Cisco.com workflows do not prompt for password when launching it through Device Center.

Cisco.com credentials are verified for every session in RME. You are prompted to enter your username and password whenever you select a flow involving Cisco.com.

However, when Cisco.com is launched from Device Center, you are not prompted to enter user name and password.

Workaround:

Configure the credentials for Cisco.com in CMF (Common Management Foundation).

The Cisco.com flows then works properly.

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:

Please upgrade the IOS image to any of the following versions which has 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 returns 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.

CSCsa41495

Suspended job for a device cannot be retried.

In a job where all the devices are suspended devices, retry is not allowed.

This happens when a request is made to Device Management during Job Execution as to whether there are enough permissions to work on the device.

Device Management responds that permission is denied in case the device is either suspended or deleted.

It does not return the exact state, whether it is suspended or deleted.

If the device is deleted, it can be retried only after you re-manage it, and when you re-manage it, the key index, that is, the deviceID gets changed.

Hence if Retry is allowed for this job after re-managing the device, the earlier job data would be invalid and would point to a wrong device ID.

To avoid such conditions, Retry on jobs where all the devices are suspended or deleted is not allowed.

Workaround:

None.

CSCsa14784

Image Import from Device does not work for Cisco 7304 Router.

Importing images from Device option does not work for Cisco 7304 Router running Image: c7300-is-mz.121-9.EX2.bin.

When you select this image and click Select Images, an error message appears.

Detailed Device Report also does not work for this device.

Workaround:

None.

CSCsa14978

CSCsa14980

Flash information not retrieved from memory for Cisco7401 ASR Router.

This happens when Cisco7401 ASR Router runs Cisco IOS Release 12.2(02)DD.

Workaround:

Upgrade the device manually to the next higher version.

Check Cisco.com documentation for higher versions available with the fix.

CSCsa22596

Software Management operations fail for Cisco Catalyst 2926 Switch.

Cisco Catalyst 2926 Switch runs on Cisco Catalyst Release 3.2(7). RME 4.0 does not support this version of Cisco Catalyst.

Workaround:

Upgrade the device manually to the next higher version.

Check Cisco.com documentation for higher versions available with the fix.

CSCsa23007

Squeeze operation fails in the Remote Stage device.

When you do Software Management distribution using remote staging, the job succeeds.

However, when you attempt a Squeeze operation in the remote stage device, it is not successful.

Workaround:

None.

CSCsa23153

Software Management Distribution fails to retrieve Flash information for Cisco MWR 1900 Mobile Wireless Router.

When you try to retrieve Flash information for Cisco MWR 1900 Mobile Wireless Router, the following error message appears:

No Flash Information is Available.

This is because the image version of this device is obsolete and no longer supported.

Workaround:

None.

CSCsa26411

Image distribution performed using Software Management onto a Cisco 7010 fails to reboot the device.

This happens when you have opted to upgrade the Cisco 7010 device with the 11.x version of image, and then rebooted immediately after copying the image.

Workaround:

None.

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, the device is rebooted but it does not boot with the new image.

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

Workaround:

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

CSCsa23990

Image Out-Of-Sync Report does not maintain the history of previous runs.

Image Synchronization Report does not maintain a history of previous runs.

There is only one synchronization job running periodically. On every run, the old report is overwritten with new report.

Therefore at any time, only one instance of the synchronization job, is running.

Workaround:

None.

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.

CSCsl58585

RME deletes NVRAM configuration files from 29/35/37xx switches on executing erase flash command.

The following scenario is noticed in DSBU switches (29xx, 35xx, 37xx):

Before upgrading to a new IOS image, the RME Software Management jobs require the flash in the device to be erased due to insufficient space. For this purpose, an erase flash is performed before pushing out the new IOS image to the device, to ensure enough space is available for the image. This leads to deletion of NVRAM configuration files.

When the device is reloaded to load the new IOS image, few issues are encountered as a result of these missing NVRAM files.

Some of the problems are:

SSH/HTTPS/SNMPv3 accesses are no longer possible.

ifIndex values are changed

Workaround:

Before scheduling the Software distribution job ensure that you free up the space in the disk so that the application does not perform an erase flash due to insufficient space.


Change Audit Known Problems

Table 11 Change Audit Known Problems 

Bug ID
Summary
Explanation

RME 4.0

   

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 12 Syslog Known Problems 

Bug ID
Summary
Explanation
RME 4.0.3
   

CSCsb70782

Syslog: Import does not work for Automated Actions and Message Filters

Import does not work for Automated Actions and Message Filters under a certain condition. This occurs when you:

1. Successfully export an existing automated action or message filter to a location that you have specified.

2. Delete the automated action or message filter.

3. Try to import the automated action or message filter that you had earlier exported.

The automated action or message filter is not imported successfully although a message appears that the automated action or message filter has been successfully imported.

Workaround:

None.

CSCsb87475

Syslogs are not received when the CW Server is inside NAT/Firewall

Syslogs are not received when the CiscoWorks server is inside NAT/Firewall

Workaround:

None.

CSCsa33492

Change Audit 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.

RME 4.0
   

CSCsa13169

CSCsa13170

Device selector lists all devices in Workflow Report.

The device selector in the Workflow Report lists all the system-defined views and all Cisco devices.

This device selector should list only Media Convergence Server (MCS) system-defined and user-defined views, and should list only MCS devices that are available in RME.

Workaround:

None.

CSCsa14816

Syslog Application of RME hogs memory in Windows.

Syslog Analyzer process consumes about 80 MB memory.

Even after you stop sending syslogs and there is no other activity on the RME server, the Syslog process still uses 80 MB memory. This affects the system performance.

Workaround:

None.

CSCsa20531

You cannot enter wildcard IP address in the device selector while creating message filters.

Device Selector does not recognize wildcard IP addresses which you enter during creation of message filters.

Workaround:

None.

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.

CSCsa34401

Migration log grows to 79MB in size while migrating data for a large number of devices.

When you migrate RME 3.5 data into RME 4.0, the log file for migration, migration.log grows to 79MB.

Workaround:

You can delete the file migration.log after the migration is completed successfully. This reclaims the space.

CSCsa35687

Syslog AA does not work in Windows 2003 Server.

An error message is displayed when you invoke Syslog Automation Action (AA) in Windows 2003 Server.

Workaround:

Give causers group the permission to run cmd.exe.

CSCdk47488

Changing the default logging facility.

Syslog messages are logged to a file configured to store local7.info messages from routers, but for PIX devices, the default is not local7.

Workaround:

Set PIX device to facility 23.

CSCin07835

Reload or restart Syslog messages are not sent by 2900XL switches.

During device reload, SYS-5-RESTART messages are not sent from the device.

This causes Update Inventory and automatic Config Fetch operations to fail.

Workaround:

None.

CSCSa57752

Alias device problems in Syslog

These occur after alias resolution happens in a way that the normal device is rejected and the aliased interface is moved to normal.

There are two problems:

1. Syslogs from some normal devices appear as syslogs from unexpected devices.

Workaround:

Restart the Syslog Analyzer.

2. Unable to find Syslogs from some normal devices in the standard or unexpected device reports.

Workaround:

There is no workaround for the second problem. Resolving the alias immediately after adding the devices to RME, largely mitigates the problem.


cwcli export Known Problems

Table 13 cwcli export Known Problems 

Bug ID
Summary
Explanation
RME 4.0 SP 2
   

CSCsb36330

cwcli export config does not export configuration data to standard output.

This happens for multiple device invocations of the cwcli export config command as well as for single device invocations that do not have the -s 1 argument.

Workaround:

1. By exporting the config for a single device at a time,

2. By also specifying the -s 1 command line argument.

The configuration data is written to the standard output stream.

RME 4.0
   

CSCin34817

While running cwcli export, either of these messages may appear:

<cwexport> * Error * Could not create device list. Check if database is up and running.

Or

java.lang.OutOfMemoryError

This may happen because:

1. The EssentialsDBEngine is down.

Or

2. There are no connections available to query the database.

Workaround:

1. Run the pdexec command.

2. Run cwcli export after some time so that connections to the database are available.

CSCsa25378

Cisco Flash device missing in cwcli export extract for 7507 MX.

The device running software version 12.1(24) fails for processor index correlation with FlashAG, and therefore, cwcli export fails.

This happens when the device has to be SNMP configured. The device has only partial support for Old-Cisco-Flash-Mib and Entity-Ext-Mib is not supported for this device.

Therefore, the physical index correlation is not archived and Flash to Processor index correlation fails.

Workaround:

None.

CSCsa28207

cwcli export for MC 3810 V3 has missing information

MC 3810 V3 has partial support for Old-Cisco-Chassis-Mib and no support for Entity-MIB, for software version 12.3(9). ContainmentAG, collection fails.

Hence cwcli export fails.

This happens when the device has to be SNMP configured.

Workaround:

None.


Contract Connection Known Problems

Table 14 Contract Connection Known Problems 

Bug ID
Summary
Explanation
RME 4.0.3
   

CSCsc44556

Contract Connection Summary Report fails with http response code 500

When you launch the Contract Connection Device Type Summary Report, an error appears, and you cannot connect to Cisco.com.

This occurs if your Cisco.com username has a dot character in it, and the contractcon.log has the message Server returned Http response code: 500 for URL.

Workaround:

None.

RME 4.0
   

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/

CSCsa94232

Device Contract Status Details Report is displayed inconsistently

Sometimes, when you launch Device Contract Status Details Report, a page appears with no records.

This occurs when you launch the detailed report page from the Device Type Summary Report, by clicking the Product Family name under Product Family in the Device Type Summary Report.

Workaround:

Press F5 to refresh the page.

Or

Close the window and launch the report again.


Bug Toolkit Known Problems

Table 15 Bug Toolkit Known Problems 

Bug ID
Summary
Explanation
RME 4.0 SP2
   

CSCsb56985

Defect subject link not working properly in Bug Details Report

Clicking on the bug headline link in the bug summary report does not show the bug description.

Workaround:

In the Locate Device Report, click the headline to view the detailed description of the bug.

RME 4.0
   

CSCsa24273

Bug Toolkit displays different bug count when logging into Cisco.com with different login IDs.

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.

CSCsa18424

The number of bugs shown in the Bug Summary Report and the Bug Details page, do not match.

When you schedule a job and check the bug summary report, you get the count for the number of bugs. For the same job, if you check the Bug Details page, you might see more bugs shown, resulting in a discrepancy.

This is because the Bug Summary Report is based on the archived data, whereas the data for the Bug Details page in the latest information, drawn from Cisco.com.

Workaround:

Run the Bug Summary Report again with the same job criteria, but with the Run Type as Immediate.

CSCsa24369

Browse Bugs—Schedule time shows an old date in
Netscape 7.1

Invoke the Browse Bugs/Locate Devices report.

A popup appears prompting you to select a username.

If you click OK or Cancel, the current dialog box is retained.

This behaviour is not seen in IE 6.x.

Workaround:

In Netscape there is an option for storing or "remembering" the password. This problem occurs only if you choose the Remember Password option. Therefore do not select the Remember password option of Netscape.

Also, if the popup appears, you can click Cancel and continue to schedule the jobs.

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, and Desktop Known Problems

Table 16 Server, Browser, and Desktop Known Problems 

Bug ID
Summary
Explanation
RME 4.0.3
   

CSCsb84712

Job Browser Sort by Job ID is incorrect

When there are more than 9 instances of a job, sorting of the Job ID field in the RME Job Browser is incorrect.

This happens when there are more than 9 instances of a job.

For example when there are over 9 instances of the same Job ID, including 1000.10, 1000.11 is the sorting appears like this:

1000.1

1000.10

1000.11

1000.2

1000.3

1000.4

...

1000.9

That is, the sort occurs in the numeric order because the Job ID field has `number' as the datatype.

This is because the Job IDs are incremented in the textual order, whereas the sorting happens in numeric order.

This is because of a limitation in the User Interface.

Workaround:

None.

RME 4.0 SP2
   

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.

RME 4.0 SP1
   

CSCsa95781

CTMJrmServer goes down after changing to the ACS mode.

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

When you change the AAA setup from the CiscoWorks local mode to the ACS mode (thorough 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.

(Continued)

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:

Follow these steps:

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

 
RME 4.0
   

CSCin03389

Adhoc template displays Failed for some catalyst devices.

A successful job will be displayed as Unsuccessful.

Workaround:

Disable debug in the device and run the job.

CSCdp08278

Tasks might fail if server is not 100% up.

If you try to access CiscoWorks before the server is running fully, Login Manager will not appear.

Workaround:

For Netscape, click Reload.

For Internet Explorer, click Refresh.

CSCdp08278

(Continued)

Tasks might fail if server is not 100% up.

(Continued)

At the beginning of CiscoWorks session, if you select a task from the navigation tree before the server is fully operational, the task might fail.

Workaround:

Select the task again. If this does not help, restart the system using one of these methods:

Using the GUI:

a. Select Server Configuration > Administration > Process Management > Stop Process.

b. Select the System radio button and click Finish.

c. Select Server Configuration > Administration > Process Management > Start Process.

d. Select the System radio button and click Finish.

From command line interface, enter:
On Windows:

net stop crmdmgtd 
net start crmdmgtd 

Make sure all process are running before relaunching tasks.

Select Server Configuration >
Administration > Process Status. The State column shows whether processes are running.

CSCds16984

Under certain conditions, you cannot launch RME from Netscape or Internet Explorer.

This may happen because the JRun Proxy Server process is not running.

Workaround:

Restart the RME server to get the process running.

CSCsa57408

JOS: Upgrading from RME 3.5 to RME 4.0 takes over 3 hours.

Single server upgrade, that is, RME 3.4 or 3.5 to RME 4.0, in Japanese Windows environment takes over 3 hours.

Workaround:

None.


Common/Other Known Problems

Table 17 Common/Other Known Problems 

Bug ID
Summary
Explanation
RME 4.0
   

CSCsa38849

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

RME shows unexpected behavior when you open a new window during any of the work flows.

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 (not under the same tab) does not cause a problem.

Workaround:

None.

CSCin17659

RME saves reports as .pl files when using Netscape.

In Netscape, if the file type exported is not pre-configured you may encounter an error. The reports are saved as .pl files instead of .txt files.

Workaround:

Add the file type manually.

To do so, select Edit > Preferences and specify the default application to open the file.

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.0.3 for details on creating Device groups with user-defined fields.

CSCdw48650(For Archive Management)

Startup and running configuration will not be fetched automatically after a CPU switchover operation.

Syslog messages are not available after a CPU switchover operation.

Owing to this, Archive Management cannot update Config Archive automatically.

Workaround:

Perform a sync archive operation. See the User Guide for RME 4.0.3 for the procedure.

This operation fetches the running configuration of the active CPU.

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 RME 4.0.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 RME 4.0.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 switchover 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}

CSCsa20015

An incorrect message appears when you click the Back button.

If you use the Back button to change your report selection, an invalid error message appears:

Select the application first.

For example, if you select the Inventory application and the Detailed Device report from the drop-down list, and then select a Syslog report.

When you click the Back button in the browser, this error message appears.

Workaround:

Select a the required report from the Report Generator drop-down list.

CSCsa15769

Timezone information not available in Report Job Browser.

If you create a new job with a frequency other than Immediate, the reports Job Browser does not appear automatically.

Workaround:

After creating a Report job, click on Report Jobs, to view the newly created job in the Job Browser.

CSCsa22897

Timezone information not available in Report Job Browser.

If the client and server machines are in different timezones, the Scheduled At and Created At times are not clear in the Report Job Browser.

Workaround:

You can find the timezone information in the CiscoWorks homepage, under Server Configuration, and also in the report heading.

CSCSa58546

RME cannot create device groups based on display name attributes

In RME, device groups cannot be created based on the domain name and display name configured in DCR (Device Credential Repository).

In RME, a device group can be created, based on device sysName and domain name obtained from device and stored as inventory data.

However, these are not the same as the display name and the domain name that is configured in DCR.

Therefore, if you create a filter for sysName but if the sysName is not the same as the name of the device in DNS (or the display name), you cannot not see any of your devices that match the filter.

In such a case, even hostnames and DNS names with differing cases do not match.

Workaround:

Create the required device group in Common Services based on DCR's display name domain name. The same groups can be seen in RME flows and can be used.


Resolved Problems in RME 4.0.3

This section has resolved problems from RME 4.0.3, RME 4.0 SP2, RME 4.0 SP1 and RME 4.0:

Customer-found Problems Resolved in RME 4.0.3

Resolved Problems in RME 4.0 SP2, RME 4.0 SP1 and RME 4.0.

Customer-found Problems Resolved in RME 4.0.3

The following are the Customer-found problems that were resolved in RME 4.0.3.

Table 18 Customer-found Problems Resolved in RME 4.0.3 

Bug ID
Component
Summary

CSCsb66955

Configuration Archive

RME 4.0 Config fetch or Config Archive jobs consistently failed.

CSCsb71868

Configuration Archive

Config Archive reported failure when vlan.dat did not exist.

CSCsb92913

Configuration Archive

Baseline template deploy did not take email id as a.b@c.d.

CSCsb92772

Configuration Archive

Inherited default exclude commands needed to be shown in UI.

CSCsb03684

Configuration Archive

LMS 2.5 Device Center View Config displayed the oldest config archived.

CSCsb65048

Configuration Archive

Compare Configurations sometimes failed with a 500 Server Error.

CSCsb63574

Configuration Archive

Archive Management Config Diff Viewer did not export correctly.

CSCsb23710

Configuration Archive

Shadow directory did not contain carriage return.

CSCsb52888

Configuration Archive

Search Archive could not redirect more devices.

CSCsb55918

Configuration Archive

Out of sync report did not consider exclude commands.

CSCsb37561

Configuration Archive

Sync Archive email no longer contained summary information.

CSCsc14404

Configuration Archive

The shadow directory had to be enabled by default.

CSCsc37260

Configuration Archive

Baseline Device selector performance was bad.

CSCsc37263

Configuration Archive

In ACS mode, Device selector screen took 4 minutes and 3 seconds to come up.

CSCsb74192

Configuration Archive

Sybase unexpected DBA lock caused SQLException and failed ChangeAudit data.

CSCsb48366

Configuration Archive

Hyperlink did not work for Failed and Partial successful devices.

CSCsb27931

Configuration Archive

RME may not have archived configs from IOS devices using Telnet or SSH.

CSCsb34647

Contract Connection

Error msg thrown by contract connection was misleading.

CSCin39798

Contract Connection

Contract information was not shown for GSR (12000s) device D683530.

CSCsb34626

Contract Connection

Contract Connection did not support proxy configurations.

CSCsb83569

cwcli export

cwcli export command generated invalid XML.

CSCsb33174

cwcli export

RME 4.0 new cwcli export config doc had missing parameters.

CSCsb36345

DEE

DEE returned invalid XML data.

CSCsc03603

Device Selector

Provision for deleting groups created by other users.

CSCsb29315

Device Selector

Could not add or edit user defined groups under Group Admin.

CSCsa41910

Install

LMS 2.5—Migration failed since DCRServer had not started.

CSCsb32001

Inventory

There was no provision to bulk import device specific NAT ID.

CSCsb61897

Inventory

Device Credentials Verification sometimes failed for cache engines.

CSCsb64870

Inventory

Unparseable date problem now resolved: error does not appear in IC_Server.log.

CSCsa86468

Inventory

Inventory Report to PDF output was unreadable.

CSCsb35724

Inventory

Database was not updated properly after deleting a device.

CSCsa64352

Inventory

Custom-report format had to be more user friendly.

CSCsb48293

Inventory

Was unable to set Config Collection Settings on RME4.0.

CSCsb92768

Syslog

Cat3750 messages were missing in Syslog system-defined messages tree.

CSCsb15729

Syslog

Automated actions did not support email addresses with apostrophes.

CSCsb48447

Job Approval

MakerChecker exception printStackTrace() threw NULLPOINTER exception.

CSCsa97811

NetConfig

NetConfig System-Defined Tasks did not include SNMP security for CatOS.

CSCsb91134

NetConfig

Incorrect Netconfig job result was displayed for failed local password change.

CSCsb74012

NetConfig

NetConfig ran out of database connections.

CSCsc05341

Netshow

There was no No sorting in device picker in certain RME flows.

CSCsb61158

Netshow

System command sets could not be unassigned to users.

CSCsb61170

Netshow

Did not allow system command sets to be selected for deletion.

CSCsb26185

Netshow

RFE - Functionality to export output of Network Show jobs to file added.

CSCsb26481

Netshow

Command output was not shown in netshow cli.

CSCsb75450

Software Management

Software Library Sync job sent one mail as PASS and the other as FAIL.

CSCsb94554

Software Management

In Software Distribution -Define Filter did not work.

CSCsb27396

Software Management

Software Repository > View/Edit Image MIN FLASH did not have 48 MB option.

CSCsb67308

Software Management

RME 4.0.2: SWIM import of 12.2.18SXE images failed

CSCsb91784

Software Management

Image upgrade of similar devices with identical images sometimes failed.

CSCsb88676

Software Management

SWIM support for 12.2.25 SG cat4500 image family was added.

CSCsb30408

Software Management

Software Management failed when ciscoFlashPartitionName(=flash0) was non-existent.

CSCsc27061

Syslog Collector

Rotating the syslog message file sometimes interrupted syslog message processing.

CSCsa36158

Syslog Collector

Could not unsubscribe when collector was uninstalled.

CSCsb14267

Utils

A TFTP Timeout attribute was added to RME.

CSCsb46867

Utils

Replaced log level '-' with 'Select log level'.


Problems Resolved in RME 4.0 SP2, RME 4.0 SP1 and RME 4.0

The following are the problems resolved in RME 4.0 SP2, RME 4.0 SP1 and
RME 4.0:

Table 19 Resolved Problems in RME 4.0 SP2, RME 4.0 SP1 and RME 4.0 

Bug ID
Summary

RME 4.0 SP2

 

CSCsb29026

IfEntry.IfIndex had no correlation with IPAddressTable IfIndex.

CSCsb44164

Supported sysOID for AP1220 was displayed wrongly in device support table.

CSCsb29155

Device support was not documented properly.

CSCsb14251

RME failed to archive CatOS configurations through TFTP.

CSCsb21855

RME did not recognize serial numbers correctly on Cisco 7507 Router.

CSCsb21873

For 3600 series devices, the serial numbers of modules were shown as `0' if they were in alphanumeric format.

CSCsa47331

SCP was not used as copy protocol for Telnet/SSH based upgrades.

RME 4.0 SP1
 

CSCsa89297

Setting a proxy may have broken other applications.

CSCsa75824

RME Sybase Engine did not start with 4 GB memory on Windows 2003.

CSCsa55592

NAM: SNMP Traps community string was shown in clear text.

CSCsa55916

Enable username not needed in Config Editor jobs.

CSCSa57860

Compare and deploy job—There was a problem in Job Password.

CSCsa58229

Job password enabled job failed with Synch archive before job execution policy.

CSCsa46785

Incorrect Inventory Change Report for AUS managed PIX device.

CSCsa43295

Catalyst 5000—Incorrect Inventory Change Report was being displayed.

CSCsa38653

LMS 2.5-There was a problem with Syslog message filter after hostname change.

CSCsa89304

Setting a proxy may have broken other applications.

CSCsa55923

Issue in Undo/Retry Jobs, now resolved.

CSCsa01751

Software Management tool had to be set to switch autologout to a proper value for NAM upgrade.

CSCsa57873

Software Management: Distribution Jobs did not work for Cat6000 MWAM Device.

CSCSa58267

RME Job failed if local user privilege 0.

CSCsa47611

Redundant processor appeared classified as module.

CSCsa58650

Could not set RME ID (NAT ID) to blank or use the option Default Not Defined.

RME 4.0
 

CSCdp82755

Config Editor job browser needed to be non modal.

CSCin35199

List devices did not show managed devices.

CSCdt79815

Device reboot operation failed on WSX-4232.

CSCdx16709

RME 3.3: Change Audit > All changes was very slow.

CSCin39767

Could not set trap for a single location.

CSCdx42655

Config Editor was not handling disk full, on creating job.

CSCdz66525

RME was not downloading IS-IS config correctly.

CSCea05989

RME 3.4+May patch > RME 35:ConfEditor used to hang for ONS config.

CSCdx95651

RME went high CPU handling large config of a router.

CSCin37664

Logical containment data for routers was lost.

CSCin29580

Configlet was not seen for UBR10012.

CSCin32411

Schema validation failed for URM device.

CSCdp78299

RME: MSSBU device card names did not show in pre-9.1 nodes.

CSCin06080

RHINO-MIB did not return index for E1.

CSCin25340

Was unable to import 2900+ devices from file.

CSCea67346

Was unable to add GSR 12416 Series devices to the Inventory.

CSCsa32246

CDA failed for MDS 9509.

CSCin06426

7609: Reboot verification failed for enswosr1, target=sup-bootflash.

CSCdv22599

CSS11K: Software Management distribution problems, now resolved.

CSCdt36634

Baselining, synchronization and backup image failed for WSX-4232.

CSCdz61804

Software Management failed IOS copy because of a long flash name.

CSCin32150

Remote stage failed on Catalyst 4503.

CSCea19533

RME IOS upgrade failed when no files on LS1010 flash disk.

CSCdz41572

Distribution jobs requiring flash erasure failed on 2948.

CSCdy43663

Bug reports URL caused Request-URI Too Large error.

CSCea54158

TFTP fallback option did not work for AS5800 devices.

CSCea37907

TFTP Fallback option did not work for GSR Series devices.

CSCin39083

Some problems with Software Management functionality for AP110, now resolved.

CSCea62915

Software Management left device in boot mode if cksum mismatch on router.

CSCin42853

RS: After the image upgrade, http server was down on DSBU devices.

CSCin07826

IP NAT log translation syslog messages were not EMBLEM compliant.

CSCin36117

Syslogs in log file were missing from database.

CSCin33389

ini file was scrambled after editing.


Obtaining Documentation

Cisco documentation and additional literature are available on Cisco.com. Cisco also provides several ways to obtain technical assistance and other technical resources. These sections explain how to obtain technical information from Cisco Systems.

Cisco.com

You can access the most current Cisco documentation at this URL:

http://www.cisco.com/techsupport

You can access the Cisco website at this URL:

http://www.cisco.com

You can access international Cisco websites at this URL:

http://www.cisco.com/public/countries_languages.shtml

Product Documentation DVD

Cisco documentation and additional literature are available in the Product Documentation DVD package, which may have shipped with your product. The Product Documentation DVD is updated regularly and may be more current than printed documentation.

The Product Documentation DVD is a comprehensive library of technical product documentation on portable media. The DVD enables you to access multiple versions of hardware and software installation, configuration, and command guides for Cisco products and to view technical documentation in HTML. With the DVD, you have access to the same documentation that is found on the Cisco website without being connected to the Internet. Certain products also have .pdf versions of the documentation available.

The Product Documentation DVD is available as a single unit or as a subscription. Registered Cisco.com users (Cisco direct customers) can order a Product Documentation DVD (product number DOC-DOCDVD=) from Cisco Marketplace at this URL:

http://www.cisco.com/go/marketplace/

Ordering Documentation

Beginning June 30, 2005, registered Cisco.com users may order Cisco documentation at the Product Documentation Store in the Cisco Marketplace at this URL:

http://www.cisco.com/go/marketplace/

Nonregistered Cisco.com users can order technical documentation from 8:00 a.m. to 5:00 p.m. (0800 to 1700) PDT by calling 1 866 463-3487 in the United States and Canada, or elsewhere by calling 011 408 519-5055. You can also order documentation by e-mail at tech-doc-store-mkpl@external.cisco.com or by fax at 1 408 519-5001 in the United States and Canada, or elsewhere at 011 408 519-5001.

Documentation Feedback

You can rate and provide feedback about Cisco technical documents by completing the online feedback form that appears with the technical documents on Cisco.com.

You can send comments about Cisco documentation to bug-doc@cisco.com.

You can submit comments by using the response card (if present) behind the front cover of your document or by writing to the following address:

Cisco Systems
Attn: Customer Document Ordering
170 West Tasman Drive
San Jose, CA 95134-9883

We appreciate your comments.

Cisco Product Security Overview

Cisco provides a free online Security Vulnerability Policy portal at this URL:

http://www.cisco.com/en/US/
products/products_security_vulnerability_policy.html

From this site, you can perform these tasks:

Report security vulnerabilities in Cisco products.

Obtain assistance with security incidents that involve Cisco products.

Register to receive security information from Cisco.

A current list of security advisories and notices for Cisco products is available at this URL:

http://www.cisco.com/go/psirt

If you prefer to see advisories and notices as they are updated in real time, you can access a Product Security Incident Response Team Really Simple Syndication (PSIRT RSS) feed from this URL:

http://www.cisco.com/en/US/products/products_psirt_rss_feed.html

Reporting Security Problems in Cisco Products

Cisco is committed to delivering secure products. We test our products internally before we release them, and we strive to correct all vulnerabilities quickly. If you think that you might have identified a vulnerability in a Cisco product, contact PSIRT:

Emergencies — security-alert@cisco.com

An emergency is either a condition in which a system is under active attack or a condition for which a severe and urgent security vulnerability should be reported. All other conditions are considered nonemergencies.

Nonemergencies — psirt@cisco.com

In an emergency, you can also reach PSIRT by telephone:

1 877 228-7302

1 408 525-6532


Tip We encourage you to use Pretty Good Privacy (PGP) or a compatible product to encrypt any sensitive information that you send to Cisco. PSIRT can work from encrypted information that is compatible with PGP versions 2.x through 8.x.

Never use a revoked or an expired encryption key. The correct public key to use in your correspondence with PSIRT is the one linked in the Contact Summary section of the Security Vulnerability Policy page at this URL:

http://www.cisco.com/en/US/products/
products_security_vulnerability_policy.html

The link on this page has the current PGP key ID in use.


Obtaining Technical Assistance

Cisco Technical Support provides 24-hour-a-day award-winning technical assistance. The Cisco Technical Support & Documentation website on Cisco.com features extensive online support resources. In addition, if you have a valid Cisco service contract, Cisco Technical Assistance Center (TAC) engineers provide telephone support. If you do not have a valid Cisco service contract, contact your reseller.

Cisco Technical Support & Documentation Website

The Cisco Technical Support & Documentation website provides online documents and tools for troubleshooting and resolving technical issues with Cisco products and technologies. The website is available 24 hours a day, at this URL:

http://www.cisco.com/techsupport

Access to all tools on the Cisco Technical Support & Documentation website requires a Cisco.com user ID and password. If you have a valid service contract but do not have a user ID or password, you can register at this URL:

http://tools.cisco.com/RPF/register/register.do


Note Use the Cisco Product Identification (CPI) tool to locate your product serial number before submitting a web or phone request for service. You can access the CPI tool from the Cisco Technical Support & Documentation website by clicking the Tools & Resources link under Documentation & Tools. Choose Cisco Product Identification Tool from the Alphabetical Index drop-down list, or click the Cisco Product Identification Tool link under Alerts & RMAs. The CPI tool offers three search options: by product ID or model name; by tree view; or for certain products, by copying and pasting show command output. Search results show an illustration of your product with the serial number label location highlighted. Locate the serial number label on your product and record the information before placing a service call.


Submitting a Service Request

Using the online TAC Service Request Tool is the fastest way to open S3 and S4 service requests. (S3 and S4 service requests are those in which your network is minimally impaired or for which you require product information.) After you describe your situation, the TAC Service Request Tool provides recommended solutions. If your issue is not resolved using the recommended resources, your service request is assigned to a Cisco engineer. The TAC Service Request Tool is located at this URL:

http://www.cisco.com/techsupport/servicerequest

For S1 or S2 service requests or if you do not have Internet access, contact the Cisco TAC by telephone. (S1 or S2 service requests are those in which your production network is down or severely degraded.) Cisco engineers are assigned immediately to S1 and S2 service requests to help keep your business operations running smoothly.

To open a service request by telephone, use one of the following numbers:

Asia-Pacific: +61 2 8446 7411 (Australia: 1 800 805 227)
EMEA: +32 2 704 55 55
USA: 1 800 553-2447

For a complete list of Cisco TAC contacts, go to this URL:

http://www.cisco.com/techsupport/contacts

Definitions of Service Request Severity

To ensure that all service requests are reported in a standard format, Cisco has established severity definitions.

Severity 1 (S1)—Your network is "down," or there is a critical impact to your business operations. You and Cisco will commit all necessary resources around the clock to resolve the situation.

Severity 2 (S2)—Operation of an existing network is severely degraded, or significant aspects of your business operation are negatively affected by inadequate performance of Cisco products. You and Cisco will commit full-time resources during normal business hours to resolve the situation.

Severity 3 (S3)—Operational performance of your network is impaired, but most business operations remain functional. You and Cisco will commit resources during normal business hours to restore service to satisfactory levels.

Severity 4 (S4)—You require information or assistance with Cisco product capabilities, installation, or configuration. There is little or no effect on your business operations.

Obtaining Additional Publications and Information

Information about Cisco products, technologies, and network solutions is available from various online and printed sources.

Cisco Marketplace provides a variety of Cisco books, reference guides, documentation, and logo merchandise. Visit Cisco Marketplace, the company store, at this URL:

http://www.cisco.com/go/marketplace/

Cisco Press publishes a wide range of general networking, training and certification titles. Both new and experienced users will benefit from these publications. For current Cisco Press titles and other information, go to Cisco Press at this URL:

http://www.ciscopress.com

Packet magazine is the Cisco Systems technical user magazine for maximizing Internet and networking investments. Each quarter, Packet delivers coverage of the latest industry trends, technology breakthroughs, and Cisco products and solutions, as well as network deployment and troubleshooting tips, configuration examples, customer case studies, certification and training information, and links to scores of in-depth online resources. You can access Packet magazine at this URL:

http://www.cisco.com/packet

iQ Magazine is the quarterly publication from Cisco Systems designed to help growing companies learn how they can use technology to increase revenue, streamline their business, and expand services. The publication identifies the challenges facing these companies and the technologies to help solve them, using real-world case studies and business strategies to help readers make sound technology investment decisions.

Internet Protocol Journal is a quarterly journal published by Cisco Systems for engineering professionals involved in designing, developing, and operating public and private internets and intranets. You can access the Internet Protocol Journal at this URL:

http://www.cisco.com/ipj

Networking products offered by Cisco Systems, as well as customer support services, can be obtained at this URL:

http://www.cisco.com/en/US/products/index.html

Networking Professionals Connection is an interactive website for networking professionals to share questions, suggestions, and information about networking products and technologies with Cisco experts and other networking professionals. Join a discussion at this URL:

http://www.cisco.com/discuss/networking

World-class networking training is available from Cisco. You can view current offerings at this URL:

http://www.cisco.com/en/US/learning/index.html