Guest

CiscoWorks Resource Manager Essentials

Release Notes for Resource Manager Essentials 3.5 on Solaris

  • Viewing Options

  • PDF (571.3 KB)
  • Feedback
Release Notes for Resource Manager Essentials 3.5 on Solaris

Table Of Contents

Release Notes for Resource Manager Essentials 3.5 on Solaris

New Features

Product Documentation

Additional Information Online

Caveats

Support Information

Known and Resolved Problems

Known Problems

Server, Browser, and Desktop Known Problems

Installation and Upgrade Known Problems

Administrator Known Problems

Device/Agent Known Problems Impacting ANI Server and RME Functionality

Availability Known Problems

Change Audit Known Problems

Config Editor Known Problems

Configuration Management Known Problems

NetConfig Known Problems

NetShow Known Problems

DEE Known Problems

Contract Connection Known Problems

Inventory Known Problems

Software Management Known Problems

Syslog Analysis Known Problems

Resolved Problems

Obtaining Documentation

Cisco.com

Documentation CD-ROM

Ordering Documentation

Documentation Feedback

Obtaining Technical Assistance

Cisco.com

Technical Assistance Center

Cisco TAC Website

Cisco TAC Escalation Center

Obtaining Additional Publications and Information


Release Notes for Resource Manager Essentials 3.5 on Solaris


These release notes are for use with CiscoWorks Resource Manager Essentials (RME) 3.5, running on Solaris. Supported Solaris versions are 2.7 and 2.8.

These release notes provide:

New Features

Product Documentation

Additional Information Online

Caveats

Support Information

Known and Resolved Problems

Obtaining Documentation

Obtaining Technical Assistance

Obtaining Additional Publications and Information

New Features

RME 3.5 contains these new features:

Support for deleting Change Audit records that are older than a specified number of days.

Separate protocol ordering for Configuration Download and Fetch operations.

Quick Configuration Download from Configuration Archive.

Support for interactive and multiline commands in Configuration Management.

Multiple selection of jobs for deletion in Configuration Management.

Job Retry option in NetConfig.

Support for new IOS templates and Cable templates in NetConfig.

Support for system-defined templates to configure IPSec and SSH on devices in NetConfig.

Support for archiving and restoring VLAN Configuration Files.

Job Password Policy for NetConfig, NetShow, and Config Editor Jobs.

Option to specify the Transport Protocol order for NetConfig, Config Editor, and Network Show Jobs.

Data Extracting Engine (DEE), a tool that provides servlet access to inventory and configuration data.

Increase in the length of User Fields to 128 characters in Inventory.

Option to customize the labels for User Fields in Inventory.

New workflow, Distribute by Images, to upgrade an image on multiple devices.

Remote Staging and Distribution option to stage an image temporarily on a managed IOS device and then use the staged image to upgrade similar devices that are connected by LAN to the Remote Stage.

Option to store syslog messages in the database for a maximum of 14 days, including today.

Option to back up the purged syslog messages at the specified location.

The Remote Syslog Analyzer Collector (RSAC) now avoids restart, by sensing the reboot of its specified server.

Additional device support.

Incremental Device Update (IDU) lets you manage new Cisco devices without waiting for a new release of CiscoWorks. You can download the latest version of IDU from Cisco.com.

Product Documentation


Note Although every effort has been made to validate the accuracy of the information in the printed and electronic documentation, you should also review the Resource Manager Essentials 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-7814808=)—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-7814810=)Provides information on using RME 3.5.

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

Resource Manager RME 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.

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.
Select Products and Services > Network Management CiscoWorks > Resource Manager Essentials > Product Literature.


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

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

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.

While checking the service contract status of your Cisco IOS devices, you can select only one contract at a time.

The Vlan configuration is not fetched along with the running configuration after running NetConfig or Config Editor jobs.

If you stop the Change Audit process, you should stop and restart the Daemon Manager.

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.

By default, Configuration Management assumes a non multi-homed machine. If you want to run RME on a multi-homed machine, set the variable MULTI_HOME=true in the $NMSROOT/objects/cmf/data/Transport.ini file and restart the Daemon Manager.

If you apply the Solaris patches 108434-11 (on Solaris 8) or 106327-18 (on Solaris 7), then DIServer, IcServer, and the Availability processes will not run.

Support Information

RME supports only US-English and Japanese versions of Solaris Operating System. It does not support any other language version. Set the default locale to US-English for US-English version and Japanese for Japanese version.

Supported Device prompts:

On IOS, PIX, CE, CSS, FastSwitch devices: > in the login mode and # in the enable mode.

On Catalyst devices: > in the login mode and (enable) in the enable mode

Catalyst 4000, 5000, and 6000 devices: custom prompts are supported in the login mode only.

The RME 3.5 installation program automatically updates the RME 3.3 or RME 3.4 program files and migrates the application data to RME 3.5.

IDU 2.0 is integrated into RME 3.5. Therefore, the installation program automatically applies some of the device updates that were previously released on the Cisco download site as IDU versions.

However, if you had installed IDU version 3.0 or higher, you should reinstall the latest IDU after installing RME 3.5. You can download it from:
http://www.cisco.com/cgi-bin/tablebuild.pl/cw2000-rme

Known and Resolved Problems

This section describes problems known to exist in this release and problems resolved since the last release of RME.


Note To obtain more information about known problems, access the Cisco Software Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/home.pl. (You will be prompted to log into Cisco.com.)


Known Problems

This section contains the following known problems for RME 3.5.

Server, Browser, and Desktop Known Problems

Installation and Upgrade Known Problems

Administrator Known Problems

Device/Agent Known Problems Impacting ANI Server and RME Functionality

Availability Known Problems

Change Audit Known Problems

Config Editor Known Problems

Configuration Management Known Problems

NetConfig Known Problems

NetShow Known Problems

DEE Known Problems

Contract Connection Known Problems

Inventory Known Problems

Software Management Known Problems

Syslog Analysis Known Problems

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.

CSCin56184

Information about ACS user privileges is not updated.

ACS user gains privileges based on the corresponding privileges assigned by CiscoWorks Administrator to the local user.

For example, if the local user corresponding to the ACS user has guest privileges, the ACS user will have access to all command sets which are assigned to that local user.

If you remove the local user corresponding to the ACS user from CiscoWorks, or if there is no corresponding CiscoWorks user for the ACS user, the ACS user will not be able to access Netshow Immediate Execution page in NetShow application.

Also, if CiscoWorks Administrator assigns remote console access to the local user, the ACS user will also gain that privilege.

Workaround:

None.

CSCdp74251

Application performance is very slow with HTTP proxy.

Accessing RME through HTTP proxy might cause significant performance degradation.

Workaround:

Access CiscoWorks Server directly from the client.

CSCin03389

Adhoc template displays Failed for some catalyst devices.

A successful job will be displayed as Unsuccessful.

Workaround:

Disable debug in the device and run the job.

CSCdp08278

Tasks might fail if server is not 100% up.

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

Workaround:

For Netscape, click Reload.

For Internet Explorer, click Refresh.

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.

CSCdp82755

Netscape 4.x: Cannot access CiscoWorks.

After Config Editor Job browser is launched, you cannot access CiscoWorks Desktop or Java console.

Workaround:

Close Config Editor Job browser before trying to access other applications.

CSCin35199

Devices do not appear in the Device Selector.

This happens after importing a set of devices or after running RME for a few days. This happens intermittently for some device views including All Devices.

Workaround:

Restart the daemon manager. Enter:

/etc/init.d/dmgtd stop

/etc/init.d/dmgtd start

CSCds16984

Unable to launch RME from Netscape or Internet Explorer.

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

Workaround:

Restart the RME server.


Installation and Upgrade Known Problems

Table 2 Installation and Upgrade Known Problems 

Bug ID
Summary
Explanation

None

ATM image version and image family might 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.

CSCdp11661

Server error when attempting to open Inventory report.

If you install TrafficDirector after installing RME and use /opt/CSCOpx as the TrafficDirector installation directory (or the directory where RME is installed), TrafficDirector could corrupt RME.

Workaround:

Uninstall both RME and TrafficDirector and reinstall both products. Uninstalling only TrafficDirector, does not resolve the problem.

CSCdk89921

RME screen appears without the login applet.

This happens if the default file ownership and permissions for /var/sadm directory are changed.

Workaround:

Do not change the default file ownership and permissions for /var/sadm directory. If you do, casuser will not be able to read the files in the directory.

CSCdr72068

Command syntax is not clear for restore backup.

Restore backup fails with fresh RME installation, when you use the command:
restorebackup.pl -d database-backup-directory

The output message does not clearly explain the command syntax you need to follow to restore the database backup on a fresh RME installation.

Workaround:

Execute the command

$NMSROOT/bin/perl

$NMSROOT/bin/restorebackup.pl -force -d backup-directory

to restore the backup database after installing RME 3.5.


Administrator Known Problems

Table 3 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, DIServer, and IcServer, are also suspended.

Workaround:

Resume the suspended session.


Device/Agent Known Problems Impacting ANI Server and RME Functionality

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

Bug ID
Summary
Explanation

CSCin04311

Protocol Distribution Graph is not displayed for VPN 3030 devices in RME Availability.

This happens because some of the MIBs are not implemented by this device group.

Workaround:

None.

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.

CSCdv64195

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

The problem occurs in the following scenarios:

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

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

The same error is reported in CSCdu09377.

Workaround

Re-load the device to reset the SNMP counters.

CSCdt79815

Reboot verification fails during the image upgrade of a WSX-4232 card on Catalyst 4000.

If you select the Reboot Immediately option during a WSX-4232 card upgrade, the upgrade fails during the reboot verification phase.

Workaround:

1. Select the Don't Reboot Immediately option during image upgrade.

2. Perform a manual reboot of the WSX-4232 card after the upgrade.

3. Verify that the card is running the new image.


Availability Known Problems

Table 5 Availability Known Problems 

Bug ID
Summary
Explanation

CSCdt10034

Private Views of one user shown to other users.

When you create a private view and add this view to Availability polling, your view will be visible if another user logs in and opens the Reachability dashboard or any other Availability options.

Workaround:

None.

CSCin30567

Interface Status not shown for Cisco 1000 series in Device Center, even though the information is present in the Detailed Device Report.

This happens because the HSE device is not supported by RME.

Workaround:

None.

CSCeg76943

The Reachability Dashboard is not refreshed while using Netscape 4.76.

The Reachability Dashboard window should be refreshed frequently (every few minutes) to display the latest data. However, this window does not refresh while using Netscape 4.76.

Workaround:

Use Netscape 7.0 or Microsoft Internet Explorer 6.0 (version 6.0.2600.0000), or 6.0 with Service Pack 1 (version 6.0.2800.1106).

You should install CiscoWorks Update 1 to avail of the support for Netscape 7.0 on Solaris.

If you are using more than one bundled product (for example, if you use LMS and RWAN), you must install the CiscoWorks Update 1 for each bundled product on all servers where that bundled product or any part of it is installed.

Download CiscoWorks Update 1 installables and Readme documents for:

CiscoWorks LMS 2.2/LMS 1.3 Update 1—Log into Cisco.com and select: Products & Solutions > Network Management > All Network Management Products, and then select CiscoWorks LAN Management Solution Software > Software Center > Download Software Image, or go to

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

CSCeg76943
(Continue)

The Reachability Dashboard is not refreshed while using Netscape 4.76.

Workaround (continue):

You should install CiscoWorks Update 1 to avail of the support for Netscape 7.0 on Solaris.

If you are using more than one bundled product (for example, if you use LMS and RWAN), you must install the CiscoWorks Update 1 for each bundled product on all servers where that bundled product or any part of it is installed.

Download CiscoWorks Update 1 installables and Readme documents for:

CiscoWorks RWAN 1.3 Update 1—Log into Cisco.com and select:

Products & Solutions > Network Management > All Network Management Products, and then select CiscoWorks Routed WAN Management Solution > Software Center > Download Software Image, or go to

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

CiscoWorks VMS 2.2 Update 1—Log into Cisco.com and select:

Products & Solutions > Network Management > All Network Management Products, and then select CiscoWorks VPN/Security Management Solution > Software Center > Download Software Image, or go to

http://www.cisco.com/cgi-bin/tablebuild.pl/vms-3des.


Change Audit Known Problems

Table 6 Change Audit Known Problems 

Bug ID
Summary
Explanation

CSCdw15134

Internal server error occurs in the Exceptions Summary report.

When you define exceptions for all seven days of the week and generate the Exceptions Summary report, an Internal Server error occurs if you selected to view all the seven days.

Workaround:

Select less than seven days.

CSCin22389

Previously defined jobs are not carried forward after a remote upgrade is performed.

This happens when Change Audit jobs are defined and then a remote upgrade is performed.

Workaround:

None

CSCdx16709

The All Changes report in Change Audit takes a long time to generate.

When a large number of change audit records accumulate over a period of time, the All Changes report tries to put all these records into a single HTML page.

Workaround:

Purge the Change Audit records regularly. To do this, select Change Audit > Delete Change History.

CSCin22391

Previously defined user preferences for Trap Destination and Exceptions are not carried forward after a remote upgrade is performed.

This happens when Exceptions and Trap Definitions are defined and then you perform a remote upgrade.

Workaround:

None

CSCin39767

Cannot set the trap destination to a single location. The message, Invalid host name appears.

This happens when you try to set the trap destination to only one location and the second location is blank or invalid.

Workaround:

Provide valid values for both the trap destinations. The values can be either identical or different.


Config Editor Known Problems

Table 7 Config Editor Known Problems 

Bug ID
Summary
Explanation

CSCdp97125

Running Config Editor from Config Viewer or VPN Config Reports leaves an empty browser.

If you run Config Editor from Config Viewer or VPN Config Reports, an empty browser is launched.

Workaround:

Do not close the browser or some features might not function properly.

CSCin29883

The commands to be downloaded to a device are not displayed in the Job Details page or the Work Order page. The system displays ArrayIndexOutOfBounds exception.

This happens when a job containing the commands generated in the Diff mode in RME 3.3 or 3.4, is scheduled to run after the upgrade to RME 3.5.

Workaround:

Edit the job. Choose the Merge mode instead of Diff as the download option.

Or

Delete the job. Select the file and undo the checkout. Check out the file once again and create a new job.

CSCdx42655

Configuration file does not open for editing.

This happens if there is no space on the RME server's hard disk to open the file.

Workaround:

1. Clean up the disk to get free space.

2. Undo the checkout of the file.

To do so, select Tools > List Checked Out File. Select the file and click Undo Checkout.

3. Open the configuration file again.

CSCdz66525

Config Editor does not download the IOS running config correctly.

When you download the IOS running config, using Config Editor, the configuration is not downloaded correctly.

Workaround:

1. Open the archived config in Config Editor in the Raw mode.

2. Place the router isis group of commands before the interface configuration as shown below:

!
router isis
metric-style wide
!
int s0
ip router isis
isis metric 1000
!

3. Save the changes.

4. Download the config file to the device in the Merge mode.

CSCin20789

The Print option does not work if you select it twice, consecutively.

This happens in the Work Order page of the Job Details dialog box.

Workaround:

1. Click on an other page (Download Summary or Device Details).

2. Return to the Work Order page.

3. Select File > Print.

CSCin25754

Config Editor jobs for Catalyst 5000 series contain an incorrect command.

There is an additional command, clear #version7.5, in Config Editor jobs for Catalyst 5000 series. This is incorrect.

Workaround:

None.

CSCea05989

The Config Editor window hangs when the user tries to check out a configuration version of an ONS device.

This happens if an unsupported ONS device was being managed as a GenericSnmp device in the earlier version of RME.

During upgrade, the configurations fetched for such ONS devices are not associated with any slot in the device. This is because the inventory was not updated.

You can verify this by generating a Configuration Summary report of the device. The slot information will be missing in the Device Name column for one of the rows.

Workaround:

Remanage the ONS device. To do so:

1. Select Resource Manger Essentials > Administration > Inventory > Delete Devices.

2. Select the ONS device and click Next.

The system prompts you for confirmation.

3. Click OK.

Wait till the device moves to the Suspended state.

4. Click on Suspended.

A list of devices that are in the Suspended state appears.

5. Select the ONS device and then select Resubmit Devices.

6. Click Finish.

CSCin29974

Error messages and comments are also downloaded in the Merge mode for Catalyst devices with submodules.

When you perform a download in the Merge mode for Catalyst devices with submodules, error messages and comments are also downloaded.

Workaround:

None.

CSCdt12180

ConfigEditor is not launched when invoked by double-clicking for the second time.

When you close ConfigEditor and then try to reopen it by double clicking, it does not open. This occurs only when the plug-in is enabled.

Workaround:

Launch the browser again.


Configuration Management Known Problems

Table 8 Configuration 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 when downloading them to the device.

None

Telnet transport mechanism cannot retrieve or update device configurations if any of the remote devices have nonstandard device prompts.

Standard device prompts are required for Configuration Archive Telnet mechanism.

Workaround:

Use only the standard device prompts.

Accepted, standard device prompts on Cisco IOS devices have strings ending with greater than symbol (>) or the pound symbol (#) at Telnet login and enable mode.

Accepted, standard device prompts on Catalyst devices end with keyword enable at Telnet enable mode.

It is recommended that all managed devices should have passwords.

None

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

Configuration Management will not retrieve the configuration of the modules which have valid Telnet credentials, if a previous module had wrong credentials.

If in a CAT switch, the supervisor and ATM module have the same credentials and RSM has a different one, Configuration Management will retrieve the configurations of Supervisor. It will fail for RSM module and display the following message:

ERROR: Incorrect Telnet passwords

It will also fail for ATM module displaying the same error, even if it has valid credentials.

Workaround:

None

None

TFTP transport mechanism might not work for devices with multiple IP addresses.

This happens when the device is managed by using the hostname in the inventory database.

TFTP uses the SNMP library. This library queries for only one IP address for a given hostname, while resolving the hostname with the corresponding domain name server.

For a device with more than one IP address, the hostname resolution might not return IP address of the interface running the SNMP agent. In such cases, TFTP fails and displays SNMP Time Out Error.

Workaround:

Import devices using IP address in inventory database.

CSCds68827

Syslog messages archived in the Configuration archive

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

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

Workaround:

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

CSCdw48650

Startup and running configuration of the active CPU and startup configuration of the standby CPU will not be fetched automatically after a CPU switchover operation.

Syslog messages are not available after a CPU switchover operation, as a result of which the Configuration Management cannot update Config Archive automatically.

Workaround:

1. Perform a manual Update Inventory operation. To do this, select:
Resource Manager Essentials > Administration > Inventory >
Update Inventory.

2. Perform an Update Archive operation. To do this, select:
Resource Manager Essentials > Configuration Management > Update Archive.

This operation fetches the running configuration of the active CPU.

All configuration related reports might show an incorrect slot as active or standby.

Syslog messages are not available after a CPU switchover operation, as a result of which the RME database is not updated automatically. Hence, all configuration related reports might show an incorrect slot as active or standby.

Workaround:

Before launching Config Reports, perform a manual Update Inventory operation. To do this, select:
Resource Manager Essentials > Administration > Inventory > Update Inventory.

CSCin03327

Slot info not updated for Cisco ONS Series (ONS 15540 ESP) devices after a CPU switchover.

The Cisco ONS Series (ONS 15540 ESP) series devices do not send syslog switchover messages to the RME server, hence the slot information will not be updated in the database.

This also causes Configuration Management not to automatically archive configuration information when there is a switchover on the device.

Workaround:

1. Perform a manual Update Inventory operation. To do this, select:
Resource Manager Essentials > Administration > Inventory > Update Inventory

2. Perform a Configuration Update manually.

CSCdw18195

Telnet access required to retrieve startup configurations from Cisco ONS Series (ONS 15540 ESP) devices.

You can retrieve the startup and running configurations of active CPU from ONS Series (ONS 15540 ESP) devices using TFTP.

However, to retrieve the standby configurations you require telnet credentials.

Workaround:

Provide telnet credentials.

CSCdt24115

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

Catalyst 5000 device displays:

Device is busy with previous operation, Try 
later'

when you perform a Config Fetch operation.

The device going into busy state is a feature of the Catalyst 5000 switches. This is to prevent too many TFTP/Telnet connections within short intervals of time.

Workaround:

Change Transport Order to specify Telnet as the first protocol.

CSCdu69242

Configuration archive causes problems when used on terminal servers with menus.

Workaround:

Use RCP for startup configurations and SNMP or TFTP for running configurations.

CSCdv77153

RME displays an out of sync error after reload for no scheduler allocate.

This happens because after a reload, routers may add the following line:

no scheduler allocate

to the running config. This confuses the RME Startup or Running Out of Sync report.

Workaround:

1. Add the following line:

no scheduler allocate

to the CommandExcludesIos.ini file. You can find the file at the location:

/opt/CSCOpx/objects/cmf/data/

2. Restart the daemon manager. Enter:

/etc/init.d/dmgtd stop 
/etc/init.d/dmgtd start

CSCdk12667

Command-line syntax errors.

When a cwconfig session has multiple syntax errors, only the first detected error is reported. Others remain unlisted.

Workaround:

None

CSCdx95651

ChangeAudit process consumes 95% CPU for more than 20 minutes when the Config Summary report or the Compare Configuration report is executed.

This happens when the device for which the report is run has a huge config (size > 600K).

Workaround:

None


NetConfig Known Problems

Table 9 NetConfig Known Problems 

Bug ID
Summary
Explanation

None

NetConfig job gives intermittent errors about failure in the Pre-Device Download operation on devices.

This happens on devices having large configurations (more than 10000 lines).

Workaround:

None.

CSCin26729

Cannot open multiple NetConfig sessions.

When you have one open session of NetConfig from an RME server, if you try to open another NetConfig session from a different RME server, you get a Permission Denied error. The old session is restored after you click OK.

Workaround:

Close the first NetConfig session before opening a new NetConfig session from a different RME server.

CSCdr50519

Cannot write to startup config after changing telnet password.

It is not possible to enable the 'Write Running Configuration to Startup Configuration' option in a NetConfig job that changes the telnet passwords.

If you do this, the job will fail when trying to write the Running Configuration to Startup.

Workaround:

Add an adhoc template that does a `write mem' instead of using the `Write Running to Startup Configuration' option.

Or

A second job can be created with a harmless change and `Write Running to Startup Configuration' option enabled to run after the first one.

CSCdz65801

NetConfig hangs when you resize the NetConfig window on Japanese OS client desktop.

NetConfig hangs and you cannot perform further operations until you close the browser.

Workaround:

Increase the Java plug-in heap-size. To do this:

1. Go to Java 1.3.1 Plugin Install Directory/bin/ControlPanel.

2. Select the Basic tab.

3. Enter -Xmx256m in Java Runtime Parameters.

4. Select Apply.

5. Relaunch the browser.

Now you can successfully resize the NetConfig window through VNC and X-client applications.


NetShow Known Problems

Table 10 NetShow Known Problems 

Bug ID
Summary
Explanation

CSCdt14631

Stop button not working properly in Immediate Execution.

When you run commands for more than one device, the Stop button might fail, if you press it repeatedly.

Workaround:

Press the Stop button only once to stop the execution of the show commands.

CSCds19913

Batch Reports do not work after you restart JRM.

After you restart JRM, Batch Reports do not work.

Workaround:

Restart the daemon manager. Enter:

/etc/init.d/dmgtd stop

/etc/init.d/dmgtd start

CSCds08146

Allows creation of duplicate command set name, if created from two different clients.

When you create the command set name from two different clients at the same instant, only one command set is created. The error message will not be displayed in the second client from where you attempted to create the command set name.

Workaround:

Select Administration > Configuration Management > Network Show > Define Command Set.

CSCin13899

Netshow displays a No output error.

This happens when you execute the command set, sh switch vlan info on UBR devices.

Workaround:

Create a custom command with a user defined command set that is applicable only to UBR devices.

CSCin12541

Netshow does not execute Catalyst show commands on Catalyst devices running IOS images.

When you select command sets containing show commands that can be executed on catalyst devices and execute them on CatIOS devices, Netshow does not execute them on these devices.

Workaround:

Do the following to assign remote console functionality to the required users:

1. Select Resource Manager Essentials > Administration > Configuration Management > Network Show > Assign Users.

2. Click Enable Remote Console? to allow the user to enter network show commands directly while running command sets.

By default, Enable Remote Console? is not selected. Enabling remote console commands will allow users to run privileged commands such as, Show Running.

To assign specific remote console commands to a user group, create the appropriate command set.

CSCdx71306

The Assign Users option does not work.

This happens when you log in as `admin' using a different combination of upper and lower case letters.

Workaround:

Login using the correct case: admin.

CSCin16615

Stop and Edit buttons are enabled for the jobs in the Missed Start state.

This happens if the scheduled time of execution is earlier than the current time of the RME server.

Workaround:

Make sure that the scheduled time of execution is later than the current time of the RME server.

CSCin20578

When you try to execute a command that ends with `?' on devices, you receive an error message.

This happens because Netshow executes two variations of the command, one ending with `?' and the other without `?'.

Example:

You try to execute the sh interface? command. NetShow executes both the commands, sh interface? and sh interface.

Workaround:

None.

CSCin19715

Netshow does not handle CatIOS-specific commands.

When you try to execute the show vtp command on the cat4503 device, it fails and displays the error, Incomplete command.

Workaround:

Run the show vtp command from a remote console.

CSCin26379

System defined command sets are not automatically assigned to admin after upgrade (remote or direct).

When you create new admin users, all the system defined command sets are assigned to them by default.

However, if you create a new system command set or custom command set when an admin user already exists, the new command sets are not automatically assigned to the existing admin user.

Workaround:

After upgrading, assign the new system command sets to the admin users.

To do so, select:
Resource Manager Essentials > Administration > Configuration Management > Network Show > Assign Users.

CSCdp91314

Net Show error:

java.lang.outOfMemory

Netshow may give a java.lang.outOfMemory error on a device. This problem occurs only with specific types of devices and only if the number of threads (set in properties file) and number of devices supplied to the command are both greater than one.

Workaround:

Run command line interface application on problem device alone, or reduce number of threads to one, and run serially.

CSCds02210

Report details appear empty when you select a report in the View Report Output window.

When you select a report in the View Report Output window of Network Show Batch Reports, the report details such as, Devices and Command Sets are not shown until you select Report Output.

Workaround:

None.

CSCdy20137

Netshow does not work if the CLASSPATH variable is set in the client machine from where RME is launched.

You cannot use Netshow if you have set the CLASSPATH variable in the client machine from where RME is launched.

Workaround:

Remove the CLASSPATH variable set in the client machine.

CSCdy38590

It takes a considerable time to refresh the NetShow window, when you select some of the NetShow commands for immediate execution.

This happens when you select commands that produce voluminous output (such as show tech or show mem) for immediate execution.

Workaround:

1. Select Network Show Commands > Batch Reports.

2. Run these commands during late hours when the RME server is not highly loaded.

CSCin28106

A Net Show job with 3500+ devices is not completed.

This happens because of lack of memory, when the job output exceeds 10MB.

Workaround:

Reschedule the job with less devices and command sets.


DEE Known Problems

Table 11 DEE Known Problems 

Bug ID
Summary
Explanation

CSCin37664

Cannot see card containment under logical section.

This happens only with devices that have card containment (a card inside another card).

Workaround:

None

CSCin29580

SubConfiglet information is missing in the config export output.

This happens when the parent configlet contains both, commands and more than one level of subconfiglets.

Workaround:

None

CSCin34817

While running DEE, 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 for either of these reasons:

1. The EssentialsDBEngine is down.

Or

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

Workaround:

1. Run the pdexec command.

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

CSCin32411

DEE output will not validate against the schema for URM devices.

In the DEE inventory output for URM devices, a square character is shown in the <HardwareVersion> tag under Cisco_Chassis and Cisco_Card. This gives an error in schema validation.

Workaround:

Manually edit the output file by deleting the unwanted binary character in the <HardwareVersion> tag under Cisco_Chassis and Cisco_Card.


Contract Connection Known Problems

Table 12 Contract Connection Known Problems 

Bug ID
Summary
Explanation

CSCdm87814

The Check Contract Status option generates information for IOS devices only.

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

Workaround:

For other devices, obtain information from the Service Contract Center at
http://www.cisco.com/public/scc/


Inventory Known Problems

Table 13 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:

Configure the PIX Firewall device so that it can be managed. 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.

CSCdw48650

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:

Perform a manual Update Inventory operation. Select Resource Manager Essentials > Administration > Inventory > Update Inventory.

CSCin06583

DIServer displays error when trying to import more than 1500 devices.

When RME tries to import data from a file which has more than 1500 devices, in a single attempt, on Windows in SSL mode, the DIServer displays an error, and pdshow hangs.

Workaround:

Import only 1000 devices at a time.

If you have more than 1000 devices to be managed, divide the contents of the file to contain not more than 1000 devices at a time.

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:

Go to the device and configure the modem. Then reacquire the inventory data.

CSCdr02713

Chassis Summary and Software Version Graphs fail.

If you click Chassis Summary Graph or Software Version Graph and select 2000 or more devices, the operation will time out after 5 minutes.

Workaround:

Do not let the maximum number of devices exceed 50.

CSCds73696

IcServer increasing in size.

IcServer shows steady increase in memory size of the process over time.

Workaround:

Restart IcServer daemon periodically.

Enter:

$NMSROOT/bin/pdterm IcServer $NMSROOT/bin/pdexec IcServer


where $NMSROOT is the CiscoWorks install directory.

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 happens to be different, Inventory will not manage the device and the device will go to the Not Responding state.

Workaround:

None

CSCdp61331

Comma included in password will cause device import to fail.

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

If you use a "," character in the password or other fields while adding a device, the CSV file generated after exporting will be invalid. An exported CSV file cannot be used for importing devices.

Workaround:

None

CSCdr81211

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

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

Workaround:

Manually delete the device from the inventory.

CSCdu68457

CSCdv31449

CSCdu68440

CSCin00785

Alias classification fails

Occasionally, a device is listed as part of the managed devices, even if the same device (with different name) is already in the managed state.

Workaround:

1. Delete all the duplicate devices from the managed list of devices.

2. Check if the DIServer debug is set to OxFFFFFFFF in daemons.log

3. To achieve max debug and have aliasing turned On, set max debug to OxFFFEFFFF.

This will provide the same debug info as that obtained by setting it to OxFFFFFFFF with aliasing turned On.

CSCdv64195

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

The problem occurs in the following scenarios:

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

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

The same error is reported in CSCdu09377.

Workaround:

Re-load the device to reset the SNMP counters.

CSCdp78299

Device card names do not appear in Detailed Device Report.

The Detailed Device Report for BPX 8600, IGX 8400, and IPX devices running switch software releases earlier than 9.1 does not show interface information.

Workaround:

None

CSCds48244

Import operations fail for 7100 and 7200 routers due to IOS bug.

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

Workaround:

Select Resource Manager Essentials > Administration > System Configuration and 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 password, 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.

CSCdx06315

Inventory shows wrong device status.

When you try to manage a device running Cisco IOS, it sometimes displays the following error:

Check DB Stats (Running/Stopped)

This occurs when the value of ciscoMemoryPoolUsed crosses 4.2 GB and this value cannot be inserted into the RME database.

Workaround:

Reload the devices to reset the SNMP counters. Then add the device again.

Or

Upgrade Cisco IOS on the devices.

CSCdx13226

Inventory update does not reflect processing of AUS device

Under Resource Manager Essentials > Administration > Inventory > Update Inventory, select an AUS device and submit for processing.

The IcServer status does not show the processing of AUS devices.

This is because AUS devices are not processed by IcServer.

Workaround:

You can check the TimeStamp on the Inventory reports to verify whether update occured.

CSCin07205

Devices with passwrd string containing special characters are not managed.

If an apostrophe is used in these user fields, database query fails. If comma is used 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.

CSCin06080

On a LS1010 with an E1 connection, Detailed Device Report does not show slot number.

As the MIB required for slot number is not available on the LS1010 with an E1 connection, this information is not provided.

Workaround:

None.

CSCin35553

Device not moving to the Managed state after performing Import from File or Synch up with ANI.

When a device is in the Suspended state, then Import from file or Synch up with ANI will 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.

CSCin22387

DIServer takes up a lot of memory

DIServer takes up a lot of memory after importing a huge number of devices (greater than 1000). System performance degrades.

Workaround:

Restart DIServer after importing a huge set of devices. Enter:

$NMSROOT/pdterm DIServer
and
$NMSROOT/pdexec DIServer.

CSCin23419

If syslogs are being pumped at a very high rate (greater than 5 syslogs per second) over a period of time, Inventory Reports may not come up.

This happens because IcServer takes up a lot of memory.

Workaround:

Restart the daemon manager. Enter:

/etc/init.d/dmgtd stop

/etc/init.d/dmgtd start

CSCin25340

When more than 1500 devices are being imported, the import process may hang and display the message, Wait For Db on the Import Status screen.

To avoid this problem, do not select more than 1000 devices while importing.

Check the Import Status to be sure that the batch of 1000 imported devices have passed to the Managed state. Then, start importing the next batch of devices.

Workaround:

If the import process hangs, restart RME. The import process will continue.

CSCea67346

When you add a GSR device to RME, it may appear in the Not Responding state.

This happens only if the processor RAM of the device is greater than or equal to 2 GB.

Workaround:

None.

CSCea85674

DIServer, IcServer, and all the Availability processes fail to start.

This happens after you apply the Solaris patches 108434-11 (on Solaris 8) or 106327-18 (on Solaris 7) and restart the system.

Workaround:

Revert to the previous version of the patch.

Earlier versions of 108434, upto -06 and 106327, upto -12 have been tested and do not cause this problem.


Software Management Known Problems

Table 14 Software Management Known Problems 

Bug ID
Summary
Explanation

None

For DSBU switches, both tar image and bin image of the same version cannot exist together in the image library.

The tar and bin images for DSBU switches cannot exist together in the image library, if they are of the same version.

Workaround:

None

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.

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.

CSCin06426

Reboot verification fails.

When a device runs the c6sup22 image from the sup-bootflash, the device incorrectly reports that it is running the image from bootflash. This causes the Reboot Verification phase of Software Management to fail.

Workaround:

Perform reboot verification manually.

CSCdv22599

Software management distribution errors occur in CSS11000 series devices versions earlier than 5.0. B10.

This is because Unpack of the copied image fails on the device.

Workaround:

Before starting an upgrade job on the device:

a. Enter the following commands at the device enable prompt:

Prompt>llama
Prompt>symbol-table load
Prompt>shell setLongVar 
uDontGarbageCollect 1

b. Reload the device.

c. Keep the telnet connection alive (open) until the upgrade job is completed.

Or

Upgrade to version 5.0 B10 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 CCO 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.

CSCdw48650

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, as a result of which the RME database is not updated automatically. Software image recommendation is based on data collected by Inventory.

Workaround:

Perform a manual Update Inventory operation. Select Resource Manager Essentials > Adminstration > Inventory > Update Inventory.

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.

CSCds66601

Image upgrade is proper but job is reported as error (1900 series).

This occurs while upgrading a 1900 device over a slow network. When the 1900 image upgrade is in progress and exceeds 5 minutes, Software Management assumes that the job has failed as it receives no response from the device.

This results in Software Management marking the job as failed. However, the upgrade is successful.

Workaround:

None

CSCds33889

Image download to and from device with subdirectory fails.

Distribution to a device or an image import job from the device having images in the subdirectory fails.

While importing the images from the device's subdirectory, Software Management considers the images in the subdirectory and continues to schedule the job. However, the job displays an error message.

Workaround:

Copy the images that have to be imported from the device to the root directory on the device.

During distribution, images are copied only to the root directory on the device. Later, you can move the images to the required subdirectory manually.

CSCdr87269

Software Management hangs if inventory contains 5000 or more devices.

If Inventory contains 5000 or more devices, and all the devices are selected in Software Management, Software Management might hang when device specific queries are issued, or may generate an error message.

Workaround:

Select a maximum of 50 devices at a time before issuing the queries.

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.

CSCdt36634

Baselining, synchronization and backup image fails for Catalyst 4232.

This is because the sysConfigName variable is not populated in certain versions of the image.

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 choose the bootflash to store the image while upgrading Cat6000 devices running IOS. Choose a different storage location.

CSCdz61804

Copy from CiscoWorks to 7600 devices fails if the flash name is long.

This happens on devices running native IOS and having flash file systems whose names are more than 16 characters long.

Example: slavesup-bootflash.

Workaround:

Choose a different storage location that has a name not longer than 16 characters.

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 the flashes and the device will run that image.

CSCdt82859

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

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

Workaround:

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

Choose a different applicable image. See the Hardware/Software compatibility matrix for choosing the correct image for such devices.

CSCin35601

Image upgrade on Cisco 800 devices fails due to lack of space.

This happens when there is not enough flash memory and the only way to free up memory is by deleting the Cisco IOS software image the router booted from. However, the Cisco 800 device does not allow users to erase the Cisco IOS software image it booted from.

Workaround:

1. Get into the TinyROM mode by modifying the config-register value followed by reload.

2. Enter the required download parameters and save.

3. Erase the existing Cisco IOS software image.

4. Download the new image using the upload tftp command in the TinyROM mode.

5. Save the file from RAM to flash.

6. Reload the router.

7. Check the image upgrade status.

CSCin32150

and

CSCea19533

Image upgrade fails on devices and the following message appears:
Config update failed because it could not find the new image on the device.

This has been observed on Cat4503, C10000, C10720, LS1010 and some of the 7200, 7300, and 7400 series devices (especially when they have disk0 or disk1 flash devices).

Workaround:

1. Do not choose the Reboot Immediately option.

2. Add the new boot command manually and then reboot the device.

3. Choose a flash partition which does not need to be erased before copying the new image.

Make sure that it has enough free space to copy the new image.

The image distribution job goes into an infinite loop. To stop the job, you have to stop the CiscoWorks daemon manager or reboot the RME server.

This problem occurs when the flash selected to copy the new image is empty. This happens because the flash has been erased before copying the new image.

The OIDs that are used in some of the images for these devices are not defined in the flash-mib that is used in RME.

Workaround:

1. Add the new boot command manually and then reboot the device.

2. Choose a flash partition which does not need to be erased before copying the new image.

Make sure that it has enough free space to copy the new image.

CSCdz41572

Image Upgrade operation fails on 2940gl3 devices.

This happens when the flash partition onto which the image is being copied does not have enough free space.

Software Management requires the files on the partition to be deleted and erased. However, the device does not support this.

Workaround:

Erase the flash partition manually and then perform the image upgrade operation.

CSCdy43663

The file, BTCCOComm.pm sends a long URL to CCO causing an error. The following message appears:

Request-URI Too Large.

This happens when you select a large number of devices for the Bug Report.

Workaround:

List the bugs using the Browse Bugs by Device option.

CSCea54158

The Tftp Fallback option does not work for AS5800 devices.

This happens because of the multiple image headers in the AS5800 images.

Workaround:

Manually copy the running image on the device to a tftp server.

Add a boot command to the device to boot from that tftp server.

CSCea37907

The Tftp Fallback option does not work for GSR devices.

This happens because of the multiple image headers in the GSR images.

Workaround:

Manually copy the running image on the device to a tftp server.

Add a boot command to the device to boot from that tftp server.

CSCin39083

Some of the SWIM operations do not work correctly for AP1100 devices.

This happens because of the inconsistency between the image names returned by the device and the names maintained by CCO.

Workaround:

None.

CSCea62915

Software Management leaves the device in the boot mode if the copy image operation fails.

This happens when upgrading the image on a run-from-flash device such as a 2500 device. Software Management leaves the device in the boot mode if the copy image operation fails.

The image copy operation may fail due to one of these reasons:

Very slow WAN link between the RME server and the device.

Or

Corrupted image copied onto the device.

Workaround:

If there is a slow WAN link between the RME server and the device, perform image upgrades manually on run-from-flash devices.

Make sure that the image to be copied onto the device is downloaded from CCO and is not corrupted.

CSCdz35730

Undo operation not supported for NAM devices.

The workflow for NAM devices does not have the Undo button.

Workaround:

Schedule a distribution job and select the NAM image to which you wish to revert.

CSCin33422

Add Image from Aironet device does not allow image import, if it is of the same version.

If an Aironet image of a particular version is imported from the device to the software library, then Software Management does not allow you to import the same image version from an Aironet device.

Workaround:

Import the image from CCO.

CSCin32665

The message, 500 server error appears.

When the CiscoWorks user name contains special characters, such as, '+', '=' etc., the image distribution workflow displays 500 server error.

Workaround:

Do not use special characters in the CiscoWorks user names.

CSCin42853

The http server does not come up after the image upgrade using the Remote Stage Distribution workflow.

This happens only on DSBU devices.

Workaround:

Add the ip http server command either at the device prompt or by using the NetConfig template.


Syslog Analysis Known Problems

Table 15 Syslog Analysis Known Problems 

Bug ID
Summary
Explanation

CSCin07826

The ip NAT log translation syslog messages are not supported in RME.

This is because NAT log translation syslog messages are not in the standard format.

Workaround:

None.

CSCdk47488

Changing the default logging facility.

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

Workaround:

Set PIX device to facility 23.

CSCdr77668

VPN 3000 series concentrators are not automatically updated in the Syslog triggered inventory update.

When a Syslog triggered inventory update happens, the VPN 3000 series concentrators are not automatically updated.

Workaround:

To update the inventory with the current device status, do one of the following:

Schedule inventory collection on a regular basis (weeks, days, hours).

Set Inventory Poller Schedule to work on a regular basis.

Update Inventory as a one time event for specific devices. Syslog triggered inventory update does not happen for VPN concentrators. Hence, manual update or scheduled inventory updates are the only available means to do the update.

CSCdt32881

Workflow Report custom/private views are not displayed

Your custom/private views will not be shown in the device selector shown in Workflow Reports. This is irrespective of whether the custom/private view has a few devices or only Workflow devices.

Workaround:

Choose the Workflow devices in the MCS Servers system view to see the reports.

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.

CSCin36117

Syslog messages from MCS devices are missing or deleted.

If Syslog messages come from MCS devices, they are stored in Syslog tables. After a scheduled Inventory Collection or Update Inventory is done on an MCS device the syslogs for the MCS device are deleted from the Syslog tables.

Workaround:

None

CSCin33389

When you download the SAenvProperties.ini file from a Solaris server onto a Windows system running RSAC, new line characters are missing.

The file appears scrambled when it is opened in Notepad.

Workaround:

Use WordPad to edit the file.


Resolved Problems

Table 16 Resolved Problems in Resource Manager Essentials 3.5 

Bug ID
Summary
Additional Information

None

cwconfig did not update or change configurations of individual modules in Catalyst 5000 switches

This problem has now been resolved.

CSCdt82319

System View was not present after restoring database from rme.dborig.

Applicable system view for Media Convergence Server and VPN Devices were missing when runtime rme.db was replaced with pre-packaged rme.dborig.

This problem has now been resolved.

CSCds13128

If two users tried to open a configuration for a device simultaneously, the device would occasionally go into a state where it would be shown as locked.

However, neither of the users would be able to unlock the device.

Earlier you had to delete the device from Inventory and add it back again.

You are no longer required to do this.

CSCdp98004

Stopping a job while it was running would cause unpredictable results.

This problem has now been resolved.

CSCin09593

CED job browser was displayed only when scheduled or running jobs were available. Otherwise, it displayed the message, No scheduled jobs found.

Earlier you had to install a patch to solve this problem.

You are no longer required to do this.

CSCin09578

Configfetch was improper in one of the fetching operations in Cisco ONS Series (ONS 15540 ESP) devices.

Earlier you had to install a patch to solve this problem.

You are no longer required to do this.

CSCdp05515

After uninstalling RME, Job Resource Manager did not remove NetConfig jobs.

Earlier you had to reinstall RME to solve this problem.

You are no longer required to do this.

CSCds20036

Launching Copy Job from Job Details window did not work.

This problem has now been resolved.

CSCdz31541

After performing an IOS upgrade on a Cat6500 device, update inventory would fail.

This problem has now been resolved.

CSCdm01805

Adding devices to Essentials would fail.

Earlier, adding devices to RME failed if case-insensitive community strings already existed in the database.

This problem has now been resolved.

CSCdx60224

Retry and Undo features were not available in Software Management.

Earlier you had to install a patch to solve this problem.

You are no longer required to do this.

CSCin00287

Retry and Undo did not work on Cisco ONS Series (ONS 15540 ESP).

This problem has now been resolved.

CSCin07665

Reboot verification used to fail.

Earlier you had to upgrade CatOS to version 5.5(13.14) 7.2(0.89) 7.4(0.2).

You are no longer required to do this.

CSCds46280

Cisco IOS TFTP client could not transfer files larger than 16MB.

This problem has now been resolved.

Solaris TFTP servers did not support TFTP file sizes of more than 16 MB.

Earlier you had to install a patch to solve this problem.

You are no longer required to do this.

CSCdy69953

While scheduling an image upgrade job on routers running Cisco IOS 12.1(11) and 12.2(5x) such as, 12.2(5a), 12.2(5b), 12.2(5c), image verification would fail. You could not schedule the upgrade job.

This happened on routers on which CISCO-FLASH-MIB did not return the partition size. Therefore, Software Management would find no Flash memory to push the image, and did not allow you to schedule the upgrade job.

This was observed on routers running Cisco IOS 12.1 (11) and 12.2(5x) such as, 12.2(5a), 12.2(5b), 12.2(5c).

A fix has been provided in this release which uses OLD-CISCO-FLASH-MIB instead of CISCO-FLASH-MIB to populate the storage details. The limitations of the fix are:

Software Management shows only the `flash' storage device as available for upgrade.

Other storage devices like bootflash, slot0, slot1, even if they exist, are not shown as available for upgrade.

To overcome these limitations:

Partition the 'Flash' storage device to ensure that CISCO-FLASH-MIB returns its correct partition size.

If you are unable to partition the 'Flash' storage device, you have to manually upgrade the device.

Optionally, partition the other storage devices also, if you want to use them for image upgrade.

CSCds71189

Remote Software Image Management upgrade of 2948G router would fail when subnet contained 3COM devices.

This problem has now been resolved.

CSCdt03226

Software Management upgrade for Cat3524 PWR XL would fail.

This problem has now been resolved.

CSCdv44225

Software Management was unable to import images from device.

This problem has now been resolved.

CSCdt19282

Exception error message was displayed when you tried to invoke Syslog Message Reference from Device Center.

This problem has now been resolved.

CSCdt94486

Software Management did not upgrade Catalyst with backup SUP.

Earlier you had to unplug the backup SUP from slot 2 to use the reboot option.

You are no longer required to do this.


Obtaining Documentation

Cisco provides several ways to obtain documentation, 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 on the World Wide Web at this URL:

http://www.cisco.com/univercd/home/home.htm

You can access the Cisco website at this URL:

http://www.cisco.com

International Cisco web sites can be accessed from this URL:

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

Documentation CD-ROM

Cisco documentation and additional literature are available in a Cisco Documentation CD-ROM package, which may have shipped with your product. The Documentation CD-ROM is updated monthly and may be more current than printed documentation. The CD-ROM package is available as a single unit or through an annual subscription.

Registered Cisco.com users can order the Documentation CD-ROM (product number DOC-CONDOCCD=) through the online Subscription Store:

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

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 Networking Products MarketPlace:

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

Registered Cisco.com users can order the Documentation CD-ROM (Customer Order Number DOC-CONDOCCD=) through the online Subscription Store:

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

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

Documentation Feedback

You can submit comments electronically on Cisco.com. On the Cisco Documentation home page, click Feedback at the top of the page.

You can email your comments to bug-doc@cisco.com.

You can submit your comments by mail by using the response card 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

Cisco provides Cisco.com, which includes the Cisco Technical Assistance Center (TAC) Website, as a starting point for all technical assistance. Customers and partners can obtain online documentation, troubleshooting tips, and sample configurations from the Cisco TAC website. Cisco.com registered users have complete access to the technical support resources on the Cisco TAC website, including TAC tools and utilities.

Cisco.com

Cisco.com offers a suite of interactive, networked services that let you access Cisco information, networking solutions, services, programs, and resources at any time, from anywhere in the world.

Cisco.com provides a broad range of features and services to help you with these tasks:

Streamline business processes and improve productivity

Resolve technical issues with online support

Download and test software packages

Order Cisco learning materials and merchandise

Register for online skill assessment, training, and certification programs

To obtain customized information and service, you can self-register on Cisco.com at this URL:

http://www.cisco.com

Technical Assistance Center

The Cisco TAC is available to all customers who need technical assistance with a Cisco product, technology, or solution. Two levels of support are available: the Cisco TAC website and the Cisco TAC Escalation Center. The avenue of support that you choose depends on the priority of the problem and the conditions stated in service contracts, when applicable.

We categorize Cisco TAC inquiries according to urgency:

Priority level 4 (P4)—You need information or assistance concerning Cisco product capabilities, product installation, or basic product configuration.

Priority level 3 (P3)—Your network performance is degraded. Network functionality is noticeably impaired, but most business operations continue.

Priority level 2 (P2)—Your production network is severely degraded, affecting significant aspects of business operations. No workaround is available.

Priority level 1 (P1)—Your production network is down, and a critical impact to business operations will occur if service is not restored quickly. No workaround is available.

Cisco TAC Website

You can use the Cisco TAC website to resolve P3 and P4 issues yourself, saving both cost and time. The site provides around-the-clock access to online tools, knowledge bases, and software. To access the Cisco TAC website, go to this URL:

http://www.cisco.com/tac

All customers, partners, and resellers who have a valid Cisco service contract have complete access to the technical support resources on the Cisco TAC website. Some services on the Cisco TAC website require a Cisco.com login ID and password. If you have a valid service contract but do not have a login ID or password, go to this URL to register:

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

If you are a Cisco.com registered user, and you cannot resolve your technical issues by using the Cisco TAC website, you can open a case online at this URL:

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

If you have Internet access, we recommend that you open P3 and P4 cases through the Cisco TAC website so that you can describe the situation in your own words and attach any necessary files.

Cisco TAC Escalation Center

The Cisco TAC Escalation Center addresses priority level 1 or priority level 2 issues. These classifications are assigned when severe network degradation significantly impacts business operations. When you contact the TAC Escalation Center with a P1 or P2 problem, a Cisco TAC engineer automatically opens a case.

To obtain a directory of toll-free Cisco TAC telephone numbers for your country, go to this URL:

http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml

Before calling, please check with your network operations center to determine the level of Cisco support services to which your company is entitled: for example, SMARTnet, SMARTnet Onsite, or Network Supported Accounts (NSA). When you call the center, please have available your service agreement number and your product serial number.

Obtaining Additional Publications and Information

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

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://www.cisco.com/en/US/products/index.html

Cisco Press publishes a wide range of networking publications. Cisco suggests these titles for new and experienced users: Internetworking Terms and Acronyms Dictionary, Internetworking Technology Handbook, Internetworking Troubleshooting Guide, and the Internetworking Design Guide. For current Cisco Press titles and other information, go to Cisco Press online at this URL:

http://www.ciscopress.com

Packet magazine is the Cisco monthly periodical that provides industry professionals with the latest information about the field of networking. You can access Packet magazine at this URL:

http://www.cisco.com/en/US/about/ac123/ac114/about_cisco_packet_magazine.html

iQ Magazine is the Cisco monthly periodical that provides business leaders and decision makers with the latest information about the networking industry. You can access iQ Magazine at this URL:

http://business.cisco.com/prod/tree.taf%3fasset_id=44699&public_view=true&kbns=1.html

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

http://www.cisco.com/en/US/about/ac123/ac147/about_cisco_the_internet_protocol_journal.html

Training—Cisco offers world-class networking training, with current offerings in network training listed at this URL:

http://www.cisco.com/en/US/learning/le31/learning_recommended_training_list.html