Guest

CiscoWorks Resource Manager Essentials

Release Notes for Resource Manager Essentials 4.0 on Solaris.

  • Viewing Options

  • PDF (813.3 KB)
  • Feedback
Release Notes for Resource Manager Essentials 4.0 on Solaris

Table Of Contents

Release Notes for Resource Manager Essentials 4.0 on Solaris

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

Product Documentation

Additional Information Online

Caveats

Known and Resolved Problems in RME 4.0

Server, Browser, and Desktop Known Problems

Bug Toolkit Known Problems

Installation and Upgrade Known Problems

Administrator Known Problems

Device Management Known Problems

Device/Agent Known Problems Impacting ANI Server and RME Functionality

Change Audit Known Problems

Config Editor Known Problems

Archive Management Known Problems

NetConfig Known Problems

cwcli export Known Problems

Inventory Known Problems

Syslog Analyzer Known Problems

Software Management Known Problems

Common/Other Known Problems

Resolved Problems in Resource Manager Essentials 4.0

Known and Resolved Problems in RME 4.0 SP1

Known and Resolved Problems in RME 4.0 SP 2

Obtaining Documentation

Cisco.com

Ordering Documentation

Documentation Feedback

Obtaining Technical Assistance

Cisco Technical Support Website

Submitting a Service Request

Definitions of Service Request Severity

Obtaining Additional Publications and Information


Release Notes for Resource Manager Essentials 4.0 on Solaris


These Release Notes are for use with the CiscoWorks family of products running on a Solaris platform. Supported Solaris versions are 2.8 and 2.9.

For the details, see the Installation and Setup Guide for Resource Manager Essentials 4.0 on Solaris.

These Release Notes provide:

New Features

Product Documentation

Additional Information Online

Caveats

Known and Resolved Problems in RME 4.0

Known and Resolved Problems in RME 4.0 SP1

Known and Resolved Problems in RME 4.0 SP 2

Obtaining Documentation

Documentation Feedback

Obtaining Technical Assistance

Obtaining Additional Publications and Information

New Features

RME 4.0 contains these 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

The Availability module of RME 3.5 is no longer available in 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 is 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 onto 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 the job to send e-mail messages when it starts and when it ends.

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.

Graphical view of configuration versions

You can view all configuration versions of the selected devices as 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.

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

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.

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 option to schedule 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.

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 Solaris

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 Solaris (DOC-7816504=)—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-7816503=)Provides information on using RME 4.0.

User Guide for Common Services 3.0 (DOC-7816571=)—Provides information about setting up, administering, and accessing CiscoWorks Common Services.

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, 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/
dev_sup/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 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 from:

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

Caveats

The following are some caveats:

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 and Resolved Problems in RME 4.0

This section contains the following known problems for RME 4.0.

Server, Browser, and Desktop Known Problems

Bug Toolkit Known Problems

Installation and Upgrade Known Problems

Administrator Known Problems

Device/Agent Known Problems Impacting ANI Server and RME Functionality

Device Management Known Problems

Change Audit Known Problems

Config Editor Known Problems

Archive Management Known Problems

NetConfig Known Problems

cwcli export Known Problems

Inventory Known Problems

Syslog Analyzer Known Problems

Software Management Known Problems

Common/Other Known Problems

Resolved Problems in Resource Manager Essentials 4.0

Server, Browser, and Desktop Known Problems

Table 1 Server, Browser, and Desktop Known Problems 

Bug ID
Summary
Explanation

None

Problems while printing from a browser.

Printing from a browser does not work reliably.

Workaround:

To print an RME window, use the Print Screen or the Capture Screen function on your machine.

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 does not appear.

Workaround:

For Netscape, click Reload.

For Internet Explorer, click Refresh.

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:
/etc/init.d/dmgtd stop

/etc/init.d/dmgtd start

Make sure all process are running before relaunching tasks.

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

CSCds16984

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.


Bug Toolkit Known Problems

Table 2 Bug Toolkit Known Problems 

Bug ID
Summary
Explanation

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 that the login IDs belong to.

Workaround:

None.

CSCsa89297

Setting a proxy may break other applications

Applications such as Campus Manager and Device Center may not work properly.

Device Center may show a blank screen, and Campus Manager applications may report that they cannot connect to ANIServer.

This can happen if a proxy server is configured within CiscoWorks.

Workaround:

Remove the proxy configuration, and restart the CiscoWorks Daemon Manager.

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 of the Bug Summary Report is based on the archived data, whereas the data for the Bug Details page is 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

CSCsa24273

Browse Bugs gives different bug counts for different Cisco.com logins

Bug Toolkit displays varying bug count while logging in to 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.

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


Installation and Upgrade Known Problems

Table 3 Installation and Upgrade Known Problems 

Bug ID
Summary
Explanation

None

ATM image version and image family may be incorrect after upgrade.

After upgrading to RME 3.5, the ATM image version and image family may be incorrect.

Workaround:

1. Delete the ATM images.

2. Reimport the ATM images from the software image library.

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.

CSCsa41910

LMS 2.5—Migration fails as DCRServer is not started.

RME Migration fails with a message that DCRServer could not be started in migration.log

This might happen rarely and can be seen in the migration.log.

Workaround:

Run this command before executing migration:

/opt/CSCOpx/bin/perl /opt/CSCOpx/bin/dbRestoreOrig.pl dsn=cmf dmprefix=Cmf opt=Y

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.

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 4 Administrator Known Problems 

Bug ID
Summary
Explanation

None

Some of the RME processes are suspended.

If you start RME by logging in as root and entering /etc/init.d/dmgtd start, 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 5 Device Management Known Problems 

Bug ID
Summary
Explanation

CSCsa18790

Device moves from Pending to Normal to Conflicting state

During device import, devices may appear as Normal Devices for a very short span of time 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

DCV 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 6 Device /Agent Known Problems Impacting ANI Server and RME Functionality 

Bug ID
Summary
Explanation

CSCdv78969

MSFC2 module in Cat6509 returns zero-length sysConfigName value.

The MSFC2 module in Cat6509 returns zero-length sysConfigName value.

Workaround:

None.

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.

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/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 do not work

Archive Management tasks on startup configuration using TFTP protocol do 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/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 has to be SNMP configured.

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 has to be SNMP configured.

Workaround:

None.

CSCsa07154

Cannot query containment AG for Catalyst 5000 devices.

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

This happens when the device has to be SNMP configured. 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 2.1(9a). Upgrade the device to this version.

CSCsa28210

cwcli export for CSS 11800 information is missing

Software Identity is missing in cwcli export

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

Workaround:

None.


Change Audit Known Problems

Table 7 Change Audit Known Problems 

Bug ID
Summary
Explanation

CSCsa33492

ChangeAudit report does not export the grouped records.

Only records shown in the report are exported. Other grouped records that are visible when you click More Records, are not exported.

Workaround:

None.


Config Editor Known Problems

Table 8 Config Editor Known Problems 

Bug ID
Summary
Explanation

CSCsa14126

Older device credential shown in clear text

This happens 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 is shown 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, the credential is encrypted in the 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.

CSCsa55592

NAM: SNMP Traps community string shown in clear text

If you use Network Analysis Module (NAM) commands, the SNMP trap community strings will not be masked.

Workaround:

None.

CSCsa55916

Enable username not needed in Config Editor jobs

Job creation flow in Config Editor has a field to accept enable username for Job Based Password (JBP). This is found in Config Editor job creation flow when JBP is enabled.

Workaround:

While entering value for JBP do not give a value in the Enable User Name field.

This problem does not have any effect.


Archive Management Known Problems

Table 9 Archive Management Known Problems 

Bug ID
Summary
Explanation

None

TACACS with SecureID not supported.

RME configuration archive does not support TACACS with SecureID. It supports static passwords that are defined when you add or import devices into the RME inventory.

Workaround:

None

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 appears 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 a 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.

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.

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 problem occurs 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 config compare reports may not be the same as in the archived file.

While trying to compare configurations, if you have same commands showing up 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.

CSCSa57860

Compare and deploy job—Problem in Job Password.

Deploying commands does not work on the non-compliant devices.

This occurs:

While scheduling a Compliance job, in the Job Scheduling screen,

When the Compare and Deploy option is checked, and

When the Job Based Password is enabled.

The Deploy operation fails, although you have entered the correct passwords.

Workaround:

While using Job Based Password for deploy operation, schedule Compliance first and then perform Deploy, later on the non-complaint devices.

That is, schedule them as two separate jobs.

CSCSa58267

RME Job fails if local user privilege 0.

Configuration operations on the device fail if privilege level set is 0 for local users.

This happens when RME uses the show privilege command to identify the privilege level. This command does not run if the privilege level is set to 0.

Workaround:

Specify the privilege level as 1 or above for the local user.


NetConfig Known Problems

Table 10 NetConfig Known Problems 

Bug ID
Summary
Explanation

CSCsa15482

Network Time Protocol template does not generate proper rollback commands.

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

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

Workaround:

None.

CSCsa16093

Trap notifications fail for certain image features.

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

Workaround:

None.

CSCsa19184

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

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

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

Workaround:

None.

CSCsa22697

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

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

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

Workaround:

None.

CSCsa24300

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

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

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

Workaround:

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

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

CSCsa25755

Rollback of a job changes the password on the device.

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

For example, Radius and enable or Tacacs+ and enable.

Workaround:

Do not 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 the 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 expires.

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 occurs when the command, aaa new model is present on the device.

Workaround:

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

CSCsa23231

Job Creation wizard loses context when multiple templates are opened.

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

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

Workaround:

Open only one window at a time.

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.

CSCsa58229

Job password enabled job fails with Synch archive before job execution policy

When you create a Netconfig job with:

1. The job password option enabled and

2. The job policy set to Synch archive before job execution,

the job fails with the error:

Pre device download operation failed.

Workaround:

1. Do not select the policy Synch archive before job execution with Job password enabled job, if Telnet/SSH are the only allowed protocols for the config fetch.

2. Specify TFTP as the fallback protocol for the config fetch for Netconfig jobs.


 

cwcli export Known Problems

Table 11 cwcli export Known Problems 

Bug ID
Summary
Explanation

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.

CSCsa47611

Redundant processor appears classified as module.

The inventory of a device shows an abnormal number of Flash Devices in reports or cwcli export extract.

Devices of type R4600 exhibit this behavior as each collection job introduces phantom FlashDevices into the inventory of the device.

Workaround:

Delete the device and add it again.

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.


Inventory Known Problems

Table 12 Inventory Known Problems 

Bug ID
Summary
Explanation

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

PIX Firewall device cannot be managed.

PIX Firewall device cannot be managed in RME.

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

CSCdv64195

Cannot 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 occurs when used memory reaches 4GB. This happens if the device is up for a long time.

The same error is reported in CSCdu09377.

Workaround:

Reload the device to reset the SNMP counters.

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.

CSCdw17735

Single Device Add page displays junk message.

When you select Inventory > Add devices and enter the device name, read write community strings, Telnet and Enable passwords, the Single Device Add page displays the following junk message:

<input type=hidden name="EnPassword" value=

Workaround:

For Netscape, click Reload.

For Internet Explorer, click Refresh.

CSCin07205

Devices with password string containing special characters are not managed.

If you use an apostrophe in these user fields, database query fails.

If you use a comma in the CSV format, import/export file errors may result as the comma would be treated as a separator.

This also applies to Telnet and Enable passwords.

Workaround:

Do not use special characters such as apostrophe (`), quote (") and comma (,) in user fields and password fields.

CSCdm75952

Using special characters in user fields.

Using special characters in user fields might lead to problems.

Workaround:

Do not enter special characters such as semicolons (;) or parentheses in user fields.

CSCin35553

Device does not move to the managed state after importing from file or synching up with ANI.

When a device is in the suspended state, Import from file operation or Synch up with ANI operation do not move that device to the managed state.

Workaround:

Use the Add Device option to move the device to the managed state.

CSCin29373

Reports are not refreshed under some conditions.

This happens:

In Netscape, if you have selected Edit > Preferences > Advanced > Cache > Document in cache is compared to document on network > Never.

In Internet Explorer, if you have selected Tools > Internet Options > Settings > Check for newer versions of stored pages > Never.

Workaround:

In Netscape, select Edit > Preferences > Advanced > Cache > Document in cache is compared to document on network > Every time.

In Internet Explorer, select Tools > Internet Options > Settings > Check for newer versions of stored pages > Every visit to the page.

CSCed92873

Cell values in Reports Job page do not align with headers.

The data in the scrolling table does not align with the headers in the Reports Job page. The table is read-only and cannot be edited.

Workaround:

None.

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

This device is not supported in RME. Hence, the image information is not displayed for the 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.

CSCsa22895

Poller does not utilze the user provided inputs for SNMP timeouts and retries.

Although you specify values for SNMP timeouts and retries, the poller does not utilize these values. Instead, it uses the default values.

Workaround:

None.

CSCsa29425

Poller returns incorrect values for Cisco 7609 router.

The poller returns incorrect values for Cisco 7609 router only in the version of Cisco IOS used by this device.

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.

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 gets executed when you run an inventory report containing user-defined field.

Workaround:

None.

CSCsa33612

Report rendering does not handle special characters.

If some malicious script is configured intentionally or unintentionally, the report display format will get disturbed, and the client side Java script runs.

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.

CSCsa34379

Sometimes Inventory Job Browser Filter fields appear misaligned in certain browsers.

The fields in the Inventory job browser filter sometimes appear misaligned in browsers such as, Netscape and Mozilla.

This is a browser-specific issue.

Workaround:

Refresh the browser window a couple of times for the fields to appear properly.

CSCsa46785

Incorrect Inventory Change Report for AUS managed PIX device.

Inventory Collection for PIX devices report FlashDevice.Size as having changed for every job.

Workaround:

Filter out FlashDevice.Size from being reported as change in the Inventory Change Filter screen.

See the Using Inventory section of User Guide for Resource Manager Essentials.

CSCsa19271

Year drop down appears at the left hand corner of the screen

While scheduling an Inventory job, if you click on the date selector to select a year, the listing of years appears in the left hand corner of the screen.

This happens with Netscape browser on Solaris.

Workaround:

Use Mozilla 1.6 instead of using Netscape.

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.

CSCsa43295

Catalyst 5000—Incorrect Inventory Change Report

Every collection job reports Module::additionalStatus to have changed, for Catalyst 5000 devices.

Workaround:

Disable change detection for Module::additionalStatus from Inventory Change Filter screen.

See the User Guide for Resource Manager Essentials for details.

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 is likely that the FlashAG collection fails at times.

Workaround:

Reboot the device.

CSCsa15342

NS 7.1—Hardware Report: Save in CSV format saves as export.csv.do in Solaris.

When you try to save the Hardware Report in the CSV format, although RME sends the default name export.csv, the Netscape client adds the .do extension.

Workaround.

Edit the name and give.xls or .csv as the extension for the file.

CSCsa23146

Inventory does not collect the Flash information 6015 IPDSL device.

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

This occurs 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 (DCV) reports Telnet as incorrect.

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

Workaround:

None

CSCsa33955

Device Credential Verification (DCV) reports incorrect status for write community string.

When a wrong SNMP Write credential is entered, DCV 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 (DCV) reports the credentials as Failed, if TACACS is configured on the device.

Workaround:

None.

CSCsa22899

Device Credential Verification (DCV) 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 (DCV) 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.


Syslog Analyzer Known Problems

Table 13 Syslog Analyzer Known Problems 

Bug ID
Summary
Explanation

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.

CSCsa20531

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

Device Selector does not recognize wildcard IP addresses which you enter while creating 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 that 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.

CSCdk47488

Changing the default logging facility.

Syslog messages are logged to a file configured to store local7.info messages from routers. However, 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.

CSCsa38653

LMS2.5-Problem with Syslog message filter after hostname change

The Syslog Collector Status shows two entries for the same Syslog Collector — one with the old name of the machine and other with the new name.

This defect occurs when the name of the machine where RME server is running is changed.

In this case, the Syslog Collector Status shows the two entries, and all the earlier filter definitions will be applied based on the new machine name.

Workaround:

Unsubscribe to the Collector before changing the machine name.

CSCsa36158

Unable to unsubscribe Syslog Analyzer from a Collector, when the Collector is uninstalled.

As a user of Syslog Analyzer, you can subscribe to one or more Syslog Collectors. You can also unsubscribe to a subscribed Syslog Collector.

However, if the Syslog Collector is already uninstalled, then the unsubscribe operation fails. You cannot uninstall the Syslog Collector in that condition.

Workaround:

Before uninstalling any Syslog Collector, you must unsubscribe all the subscribed Syslog Analyzers, from this Collector.

If you uninstall the Collector before unsubscribing the Syslog Analyzers that are subscribed to it, a separate row appears in the Syslog Collector Status report for the uninstalled Collector.

There is no other impact on the Syslog Analyzer.

CSCsa15703

MF: Create: UI alignment is lost if subfacility message type is selected

While trying to define message filters by choosing many Syslog message types, the UI alignment of the subfacility field is sometimes lost.

This happens only when many Syslog message types are chosen and a scroll bar appears. After the scroll bar appears, if a message type containing a subfacility string is added, this problem is seen.

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.


Software Management Known Problems

Table 14 Software Management Known Problems 

Bug ID
Summary
Explanation

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.

CSCsa89304

Setting a proxy may break other applications

Applications such as Campus Manager and Device Center may not work properly.

Device Center may show a blank screen, and Campus Manager applications may report that they cannot connect to ANIServer.

This can happen if a proxy server is configured within CiscoWorks.

Workaround:

Remove the proxy configuration, and restart the CiscoWorks Daemon Manager.

CSCin06524

Software management displays error with MC3810 device.

MC3810 devices running IOS version 11.3(1) display errors when accessed from Software Management.

Workaround:

Upgrade the IOS version on the device manually.

CSCdv78969

Baselining, synchronization report, and reboot verification fail for the MSFC2 module in Cat6509.

This is because the MIB required for baselining, synchronization report, and reboot verification is not available.

Workaround:

None.

CSCea14119

The Cisco.com Upgrade Analysis feature of RME recommends the wrong code for 7206 devices.

This happens only on 7206 devices with NSE-1 processors. The router may crash.

Workaround:

Read the Hardware/Software compatibility matrix available at Cisco.com for 7200 devices and select the applicable image.

CSCds33889

Image download to and from device with subdirectory fails.

Distribution jobs fail when images are distributed to devices that have images in a subdirectory.

Images are distributed only to the root directory using Software Management.

Workaround:

None.

CSCdt36628

Baselining, sychronization and backup image fails for 7140-2FE.

This is because the sysConfigName variable is not populated in certain ATA Flash card devices.

Workaround:

Import the image manually from the device.

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.

CSCin12771

The image distribution job on 3550-G12 switches may fail. The message, Flash copy to/from operation failed appears.

This happens if Flash is full on Cisco Catalyst 3550-G12 switches.

Workaround:

Delete or squeeze the files from Flash and retry the job.

CSCds17021

Distribution job's reboot verification fails on dual processor 8540MSR devices.

After image distribution to a dual processor 8540MSR device, the device runs the image of the standby processor.

This causes the distribution job's reboot verification to fail.

Workaround:

Schedule the same image distribution job for the device twice.

After the second distribution, the same image is stored in both Flashes and the device will run that image.

CSCdt82859

Software Management wrongly shows 12.1(5)T5 as an applicable image for a 7500 device with VIP2 blades.

This happens while importing images from Cisco.com and while recommending images for upgrade for a 7500 device with VIP2 blades.

Workaround:

Do not select 12.1(5)T5 image for upgrading a 7500 device with VIP2 blades.

Select a different applicable image.

See the Hardware/Software compatibility matrix for choosing the correct image for such devices.

CSCsa08734

Add Image from device fails for Cisco 7300 Series Routers.

When you select Import from device for Cisco 7300 Series Routers, an error message appears

No images to import

This problem is not seen in devices running later versions of Cisco IOS.

Workaround:

None.

CSCsa12563

CSCsa16902

Add Image from Device does not work for Cisco 1700, 2600, and 3600 Series Routers and the Job Status reported is incorrect.

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 download a new image.

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

None.

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 occurs 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 fail.

Workaround:

None.

CSCsa35853

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

This occurs 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

CSCsa22750

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.

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 work 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 occurs 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.

CSCsa29032

Sol—Copy to and from device fails for files greater than 32MB, using TFTP.

In Solaris, Software Management uses Solaris TFTP server to copy images to and from the device.

This works well if the images are less than or equal to 32MB.

However, there are some recent images for Supervisor 720 series and Andiamo devices, that are more than 32MB.

Workaround:

Use RCP protocol instead of TFTP to transfer images that are greater than 32MB in size.

This workaround applies to all IOS devices. However, for Andiamo devices, upgrade cannot be done using the latest images. This is because they do not support RCP.

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.

CSCsa47331

SCP is not used as copy protocol for telnet/SSH based upgrades

There is no SCP support for devices which are upgraded through Telnet or SSH.

Devices in this category are Catalyst IOS switches such as 29xx,35xx and 800 series routers.

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.

CSCsa55923

Issue in Undo/Retry Jobs

When you Undo a successful distribution job or Retry a failed distribution job, the job options selected as part of the original job are used.

This is not corrected if you clear the selected job options or reset them during Undo or Retry operations.

For example, if in the original distribution job, you had selected Reboot the Device as a job option, during the Undo or Retry operation, the same option continues to be used during the task flow, even if you deselect it.

Workaround:

None.

CSCsa01751

Software Management should set switch autologout to a proper value for NAM upgrade

Software Management relies on the telnet session time of the switch to finish the NAM upgrade job.

Since the upgrade can take a long time (up to 90 minutes) because of HTTP, the session will always time out if it is not configured correctly and upgrade fails.

To avoid this, On CAT-OS swtiches, Software Management sets autologout to 0 (disable) before image transfer starts.

However, at the end of the upgrade, autologout does not revert to the original value that you had configured (if you had configured this value). You should revert the auto-logout value to the original value that you had configured, for security reasons.

Workaround:

Manually configure autologout time to some value instead of 0 (disable) on the switch after NAM upgrade using Software Management.

CSCsa57873

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

MWAM distribution job times out if the MWAM Application Partition (AP) version is 2.0 or higher.

If the MWAM AP version is 2.0 or higher for the AP upgrade, a prompt appears,

Destination filename [filename]? '

This prompt did not appear for the earlier AP versions. Versions 2.0 or higher, cause the Software Management job to timeout and fail.

Workaround:

None.

CSCsa29032

Sol: Copy to and from device fails for files greater than 32 MB, using TFTP.

On Solaris, transfer of files that are greater than 32 MB file using TFTP does not work in both copy from RME server to device and also from device to RME server.

This happens only if image size is greater than 32 MB. This is the problem withe TFTP server that comes with Solaris.

Workaround:

Install tftp server available at ftp://ftp.kernel.org/pub/software/network/tftp/ on Solaris machines and use this for RME operations.


Common/Other Known Problems

Table 15 Common/Other Known Problems 

Bug ID
Summary
Explanation

CSCsa38849

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

RME 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. The bug 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 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, the Archive Management cannot update Config Archive automatically.

Workaround:

Perform a sync archive operation.

See the User Guide for RME 4.0 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 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 for the procedure.

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

If a CPU switchover occurs 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

The Job Browser does not appear automatically after a report is created.

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.

CSCsa18505

Netscape 7 on Solaris Save Report As PDF option displays a 500 Error

This problem occurs when you generate Hardware Report and save it as PDF.

An error appears:

Error: 500

Location: /rme/InventoryReports.do

Internal Servlet Error:

java.lang.NullPointerException

at com.lowagie.text.Document.add(Unknown Source)

at com.cisco.nm.uii.reports.StackOfStackedTablesRequestHelper.doPDFExport(StackOfStackedTablesRequestHelper.java:397)

at com.cisco.nm.rmeng.inventory.reports.ui.action.InventoryReportsAction.perform(InventoryReportsAction.java:199)

at org.apache.struts.action.ActionServlet.processActionPerform(ActionServlet.java:1786

Workaround:

This bug is caused by the Acrobat Plugin and Netscape browser combination.

For details see: http://my.justlinux.com/forum/showthread.php?threadid=127625

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.

CSCsa58650

Cannot set RME ID (NAT ID) to blank or use the option Default Not Defined

Once you modify the RME ID (NAT ID) in Admin > System Preferences > RME Device Attributes, you cannot change it back to the option "Default Not Defined" or Null.

Workaround:

Enter any string that is not an IP address and it will be filtered out by applications.


Resolved Problems in Resource Manager Essentials 4.0

Table 16 Problems Resolved in Resource Manager Essentials 4.0 

CSCin56184

CSCdp74251

CSCdp82755

CSCin35199

CSCdt79815

CSCdx16709

CSCin39767

CSCdx42655

CSCdz66525

CSCea05989

CSCdx95651

CSCin37664

CSCin29580

CSCin32411

CSCdp78299

CSCin06080

CSCin25340

CSCea67346

CSCsa32246

CSCea85674

CSCin06426

CSCdv22599

CSCdt36634

CSCdz61804

CSCin32150

CSCea19533

CSCdz41572

CSCdy43663

CSCea54158

CSCea37907

CSCin39083

CSCea62915

CSCin42853

CSCin07826

CSCin36117

CSCin33389

       

Known and Resolved Problems in RME 4.0 SP1

This section is applicable only if you have installed Resource Manager Essentials 4.0 Service Pack1 (RME 4.0 SP1).

To avail the features and additional device support of RME 4.0 SP1, you must download Resource Manager Essentials 4.0 Service Pack1.

RME 4.0 SP1 is available at this location:

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

The following new features are available in RME 4.0 SP1.

NetShow

Contract Connection

SmartCase

Support for SSHv2

Bug fixes on RME 4.0

For more information, see Readme for Resource Manager Essentials 4.0 Service Pack1 at this location:

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

Table 17, Table 18, Table 19, Table 20, Table 21, Table 22, Table 23, Table 24 describe problems known to exist in this release (RME 4.0 SP1); Table 25 describes problems resolved since the last release of RME 4.0.

This section has these topics:

Known Problems in Installation

Known Problems in Server, Browser, and Desktop

Known Problems in Inventory

Known Problems in Configuration Archive

Known Problems in NetConfig

Known Problems in NetShow

Known Problems in Contract Connection

Known Problems in Software Management

Resolved Problems in RME 4.0 SP1

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.


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

You will be prompted to log into Cisco.com.

Table 17 Known Problems in Installation 

Bug ID
Summary
Explanation

CSCsa93329

Daemon manger dumps core when configjob/DCMA displays OutOfMemory exception

The daemon manager sometimes dumps core but no processes go down.

This sometimes occurs during a Quick Config Deploy operation from Config Management.

Workaround:

1. Stop the daemon manager.

2. Increase the swap space of the system.

3. Restart the daemon manager.


Table 18 Known Problems in Server, Browser, and Desktop 

Bug ID
Summary
Additional Information

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.

When you install RME 4.0 SP1 in the ACS mode. If the CiscoWorks Server is in the ACS mode, the RME 4.0 SP1 installation warns you that you need to change to CiscoWorks Local Mode before continuing with the installation. However, if you continue with the installation in the current ACS mode (by choosing Yes when the warning message appears), this issue may occur.

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

 

CSCsa89512

Difference in log file time-stamp and system time

The time-stamp in the stdout.log file is different from the system time.

This occurs only on some Solaris machines.

Workaround:

None.


Table 19 Known Problems in Inventory 

Bug ID
Summary
Explanation

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.

CSCsa79594

Misalignment of fields in Inventory Job Browser

The fields, Job ID, Job Type, Status, Description, Owner, Scheduled at, Completed at, Schedule Type, are aligned in the Inventory Job Browser only when there are 10 or less than 10 jobs in the Job Browser.

If there are more than 10 jobs in the Job Browser, the fields are not aligned.

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

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 SP1 Online help.


Table 20 Known Problems in Configuration Archive 

Bug ID
Summary
Explanation

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.


Table 21 Known Problems in NetConfig 

Bug ID
Summary
Explanation

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


Table 22 Known Problems in NetShow 

Bug ID
Summary
Explanation

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. Once again, 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:

To overcome this problem you can:

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 SP1 Online help


Table 23 Known Problems in Contract Connection 

Bug ID
Summary
Explanation

CSCdm87814

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

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

Workaround:

Get information from the Service Contract Center at:

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

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.


Table 24 Known Problems in Software Management

Bug ID
Summary
Explanation

CSCsb02631

Image import job fails and displays the error Invalid data dir

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.

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.

CSCsa92049

Software Management-SOL: Edit Admin Preferences displays an error

In Software Management, when you make a change to Admin Preferences, the operation fails with an error
Failed to execute df -k command

This happens when there is not enough swap space on the server to create a new java process.

Workaround:

Increase swap space and then try the operation.


After you install RME 4.0 SP1, the following problems from RME 4.0 will be resolved:

Table 25 Resolved Problems in RME 4.0 SP1 

Bug ID
Summary

CSCsa89297

Setting a proxy may break other applications

CSCsa55592

NAM: SNMP Traps community string shown in clear text

CSCsa55916

Enable username not needed in Config Editor jobs

CSCSa57860

Compare and deploy job—Problem in Job Password.

CSCsa46785

Incorrect Inventory Change Report for AUS managed PIX device.

CSCsa43295

Catalyst 5000—Incorrect Inventory Change Report

CSCsa38653

LMS2.5-Problem with Syslog message filter after hostname change

CSCsa58229

Job password enabled job fails with Synch archive before job execution policy

CSCsa89304

Setting a proxy may break other applications

CSCsa55923

Issue in Undo/Retry Jobs

CSCsa01751

Software Management should set switch autologout to a proper value for NAM upgrade

CSCsa57873

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

CSCsa58650

Cannot set RME ID (NAT ID) to blank or use the option Default Not Defined


Known and Resolved Problems in RME 4.0 SP 2

This section is applicable only if you have installed Resource Manager Essentials 4.0 Service Pack2 (RME 4.0 SP2).

To avail the features and additional device support of RME 4.0 SP2, you must download Resource Manager Essentials 4.0 Service Pack2.

RME 4.0 SP2 is available at this location:

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

Table 26, Table 27, Table 28, Table 29, Table 30, Table 31, Table 32, Table 33, Table 34, Table 35 describe problems known to exist in this release (RME 4.0 SP2); Table 36 describes problems resolved since the last release of RME 4.0.

This section has these topics:

Known Problems in Installation of RME 4.0 SP2

Known Problems in Utils of RME 4.0 SP2

Known Problems in Inventory of RME 4.0 SP2

Known Problems in INVICS of RME 4.0 SP2

Known Problems in Device Selector of RME 4.0 SP2

Known Problems in Data Extract Engine of RME 4.0 SP2

Known Problems in Configuration Archive of RME 4.0 SP2

Known Problems in Netshow of RME 4.0 SP2

Known Problems in Contract Connection of RME 4.0 SP2

Known Problems in Software Management of RME 4.0 SP2

Resolved Problems in RME 4.0 SP2

Table 26 Known Problems in Installation of RME 4.0 SP2 

Bug ID
Summary
Additional Information

CSCsb16108

Installation of RME 4.0 SP1 over RME 4.0 SP2 should not be allowed.

Installation of RME 4.0 SP1 on top of RME 4.0 SP2 is not supported method of installation.

Workaround:

None.

CSCsb51828

Restore operation fails for RME.

During restore operation, only Common Services is restored and not RME.

This problem occurs when Ciscoworks is not installed in the default directory (/opt/CSCOpx).

Workaround:

None


Table 27 Known Problems in Utils of RME 4.0 SP2 

Bug ID
Summary
Explanation

CSCsb15729

Automated actions do not support email addresses with apostrophes

Email addresses that contain apostrophes are not accepted by Syslog automated actions and displays the error

Enter valid e-mail address(es). Insert a comma between e-mail IDs.

This occurs for any email address that contains an apostrophe (''').

Workaround:

Use an email address that does not contain an apostrophe.


Table 28 Known Problems in Inventory of RME 4.0 SP2 

Bug ID
Summary
Explanation

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.


Table 29 Known Problems in INVICS of RME 4.0 SP2 

Bug ID
Summary
Explanation

CSCsb35724

Database is not updated properly after deleting a device.

Syslog reports do not display Syslog messages that came from some managed devices, even if these messages are stored in RME database.

Sometimes, when devices are deleted from RME, the data is not cleaned up properly in the database. So there are several records in the database that refer to the same device.

Workaround:

Reinitilize RME database.


Table 30 Known Problems in Device Selector of RME 4.0 SP2 

Bug ID
Summary
Explanation

CSCsb28200

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

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

All sysObjectIDs in RME are stored with a leading dot.

Workaround:

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

CSCsb29315

The Edit button is disabled and you cannot add or edit user defined groups under Group Admin.

When two users (for example, User1 and User2) have same permissions, the group created by User1 cannot be edited by User2.

In this case, the Edit button is disabled for User 2.

Workaround:

None.


Table 31 Known Problems in Data Extract Engine of RME 4.0 SP2 

Bug ID
Summary
Explanation

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.


Table 32 Known Problems in Configuration Archive of RME 4.0 SP2 

Bug ID
Summary
Explanation

CSCsb27931

Resource Manager Essentials does not fetch configurations from devices using Telnet or SSH.

This problem occurs when it takes more than six seconds for the device to return a prompt after RME logs in.

Workaround:

Use SNMP/TFTP to archive configurations.

CSCsb48293

Cannot to set Config Collection Settings on RME4.0

Even if configuring collection is scheduled correctly, the following message is shown.

New schedule should be later than 
current time

Workaround:

None.

CSCsb48359

You cannot edit the type of device for the baseline template.

After creating a basic baseline template, you cannot edit the type of device for that template.

Workaround:

None.

CSCsb48366

When you view Archive Job status, hyperlink does not work for failed and partial successful devices.

Hyperlink does not work for Failed and Partially successful devices.

Workaround:

1. Open the Succeeded list

2. View the Failed list or Partially Successful list.

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.


Table 33 Known Problems in Netshow of RME 4.0 SP2 

Bug ID
Summary
Explanation

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.

CSCsb26481

You cannot view Netshow job output from the command line.

You cannot view Netshow job output from the command line. The subcommands execcmd and execcmdset (as documented in the cwc-netshow manual page) do not work.

The jobresults cli command was missed for Netshow. So a new CLI command "cwcli netshow jobresults" is introduced. (Explain) This command will fetch job results.

Workaround:

1. Schedule a job from the command line using cwcli netshow

2. View the resulting show command output in the GUI.


Table 34 Known Problems in Contract Connection of RME 4.0 SP2 

Bug ID
Summary
Explanation

CSCsb34626

Contract Connection does not support proxy configurations.

When you run a Contract Connection report in RME the following error message is displayed:

CCX0002 CCO User Credential Invalid

This problem occurs if the CiscoWorks server needs to connect to Cisco.com using a proxy. configuration that does not work properly.

Workaround:

None.


Table 35 Known Problems in Software Management of RME 4.0 SP2 

Bug ID
Summary
Explanation

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.

CSCsb43082

Image import from device fails where ciscoFlashPartitionName=flash0

RME 4.0.1 fails to import images for Cisco Catalyst 3550/3500 series switches. This is caused by the wrong information returned by the switches.

Workaround:

Contact Cisco TAC for a patch to be applied in Resource Manager Essentials 4.0 SP2.

CSCsb30408

SWIM fails when ciscoFlashPartitionName(=flash0) does not exist

RME fails to upgrade the IOS image for the 3550 series switches because of wrong information returned by the switches.

Workaround:

Contact Cisco TAC for a patch to be applied in Resource Manager Essentials 4.0 SP 2.


After you install RME 4.0 SP2, the following problems from RME 4.0.1 will be resolved:

Table 36 Resolved Problems in RME 4.0 SP2 

Bug ID
Summary

CSCsb29026

IfEntry.IfIndex had no correlation with IPAddressTable's 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.


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/univercd/home/home.htm

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

Ordering Documentation

You can find instructions for ordering documentation at this URL:

http://www.cisco.com/univercd/cc/td/doc/es_inpck/pdi.htm

You can order Cisco documentation in these ways:

Registered Cisco.com users (Cisco direct customers) can order Cisco product documentation from the Ordering tool:

http://www.cisco.com/en/US/partner/ordering/index.shtml

Nonregistered Cisco.com users can order documentation through a local account representative by calling Cisco Systems Corporate Headquarters (California, USA) at 408 526-7208 or, elsewhere in North America, by calling 1 800 553-NETS (6387).

Documentation Feedback

You can send comments about technical 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.

Obtaining Technical Assistance

For all customers, partners, resellers, and distributors who hold valid Cisco service contracts, Cisco Technical Support provides 24-hour-a-day, award-winning technical assistance. The Cisco Technical Support Website on Cisco.com features extensive online support resources. In addition, Cisco Technical Assistance Center (TAC) engineers provide telephone support. If you do not hold a valid Cisco service contract, contact your reseller.

Cisco Technical Support Website

The Cisco Technical Support 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, 365 days a year, at this URL:

http://www.cisco.com/techsupport

Access to all tools on the Cisco Technical Support 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 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 TAC 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 TAC 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, and logo merchandise. Visit Cisco Marketplace, the company store, at this URL:

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

The Cisco Product Catalog describes the networking products offered by Cisco Systems, as well as ordering and customer support services. Access the Cisco Product Catalog at this URL:

http://cisco.com/univercd/cc/td/doc/pcat/

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. You can access iQ Magazine at this URL:

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

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

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