Guest

CiscoWorks Resource Manager Essentials

Readme for Resource Manager Essentials 4.0 Service Pack 2 on Solaris

  • Viewing Options

  • PDF (443.1 KB)
  • Feedback
Readme for Resource Manager Essentials 4.0 Service Pack 2 on Solaris

Table Of Contents

Readme for Resource Manager Essentials 4.0 Service Pack 2 on Solaris

Description

Accessing RME 4.0 SP2 Help

New Device Support

Hardware and Software Requirements

Downloading the Application

Downloading From Cisco.com

Downloading From Software Center

Using the Download Updates Option

Using the Select Updates Option

Installing the Application

Pre-requisites for Installing RME 4.0 SP2

Installing RME 4.0 SP2

Verifying the Installation

Backing up and Restoring of Data

Restoring All RME 4.0 SP1 and SP2 Data

Restoring All RME 3.x Data

Restoring NetShow Data

Uninstalling the Application

Re-installing RME 4.0 SP2

RME 4.0 SP2 Related Documentation

Known and Resolved Problems

Known and Resolved Problems in RME 4.0 SP2

Known Problems in RME 4.0 SP1


Readme for Resource Manager Essentials 4.0 Service Pack 2 on Solaris


This Readme is for Resource Manager Essentials 4.0 Service Pack 2 (RME 4.0 SP2), on Solaris.

It contains the following sections:

Description

Accessing RME 4.0 SP2 Help

New Device Support

Hardware and Software Requirements

Downloading the Application

Installing the Application

Backing up and Restoring of Data

Uninstalling the Application

Re-installing RME 4.0 SP2

RME 4.0 SP2 Related Documentation

Known and Resolved Problems

Description

The RME 4.0 Service Pack 2 is a cumulative package. In addition to the devices and applications already supported in RME 4.0 SP1, this package supports new devices and contains fixes to known problems, as well as fixes to newly discovered problems.

Accessing RME 4.0 SP2 Help

The help for RME 4.0 SP2 is available as part of the User Guide for Resource Manager Essentials. See

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

This information is also a part of the Online help that is available when you install RME 4.0 SP2.

To launch and access the Online help see the topic "Context-Sensitive Online Help for Resource Manager Essentials" in the section, "RME 4.0 SP2 Related Documentation".

New Device Support

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

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

Table 1 Devices Supported in RME 4.0 SP2 

Device Type
Devices/
Modules Supported
sysObjectID
Inventory Manager
Config. Mgmt.
Software Mgmt.
Minimum Software

Cisco Aironet AP/BR Series

AP 1130

1.3.6.1.4.1.9.1.618

Yes

Yes

Yes

12.3(2)JA

Cisco Catalyst 6500/7600 Series Supervisor Modules

SUP 720-3BXL

Yes

Yes

Yes

12.2(17a)SXA

Cisco Content Engine Series

CE 511

1.3.6.1.4.1.9.1.595

Yes

Yes

Yes

5.2.1.5

Cisco Gigabit Ethernet Switching Module

CGESM

1.3.6.1.4.1.11.2.3.7.11.33.3.1.1

Yes

Yes

Yes

12.2(25)SE

Cisco MDS 9200 Series Multilayer Fabric Switches

9216A

1.3.6.1.4.1.9.12.3.1.3.442

Yes

Yes

Yes

2.0(2b)

Cisco Small Business Routers

SB 101

1.3.6.1.4.1.9.1.627

Yes

Yes

Yes

12.3(8)YG

SB 106

1.3.6.1.4.1.9.1.628

SB 107

1.3.6.1.4.1.9.1.629

Cisco 1800 Series Routers

1801

1.3.6.1.4.1.9.1.638

Yes

Yes

Yes

12.3(14)YT

1802

1.3.6.1.4.1.9.1.639

1811

1.3.6.1.4.1.9.1.641

Yes

Yes

Yes

12.3(8)YH

1812

1.3.6.1.4.1.9.1.642

Cisco Catalyst 3560 Series Switches

3560-24TS

1.3.6.1.4.1.9.1.633

Yes

Yes

Yes

12.2(20)EX

3560-48TS

1.3.6.1.4.1.9.1.634

Yes

Yes

Yes

Cisco RPM Series Routers

RPM-XF

1.3.6.1.4.1.9.1.440

Yes

Yes

Yes

12.3(11)T5

Cisco Router 800 Series

857

1.3.6.1.4.1.9.1.567

Yes

Yes

Yes

12.3(8)YI1

877

1.3.6.1.4.1.9.1.569

Cisco Router 12000 Series

12010

1.3.6.1.4.1.9.1.348

Yes

Yes

Yes

12.0(27) S1

Cisco Catalyst 3750 Series Switches

3750-24FS

1.3.6.1.4.1.9.1.516

Yes

Yes

Yes

12.2(25)SEC

Cisco 7304 Router Shared Port Adapter (SPA)

spa-2p-ge-7304

Yes1

12.2(25)S3

spa-4p-fe-7304

Cisco Access Server 5400 Series

AS5400 HPX

1.3.6.1.4.1.9.1.274

Yes

Yes

Yes

12.3(3g)

Cisco Catalyst 1900 Series Switches

CPW 1900L (1900i)

1.3.6.1.4.1.9.5.31

Yes

Yes

Yes

8.00.00

1900c (1900 W FX Port)

1.3.6.1.4.1.9.5.28

Cisco Catalyst 2800 Series Switches

2820

1.3.6.1.4.1.9.5.20

Yes

Yes

Yes

8.00.00

Cisco Content Services Switch

CSS11501

1.3.6.1.4.1.9.9.368.4.7

Yes

Yes

Yes

7.4

Cisco Catalyst 2900XL Series Switches

2924C-XL-V

1.3.6.1.4.1.9.1.218

Yes

Yes

Yes

12.0(5)WC11

Cisco Catalyst 6500 Series Satellite Switches

6506

1.3.6.1.4.1.9.1.282

Yes

Yes

Yes

12.0.17.SR

1 Supported through parent device


Hardware and Software Requirements

The hardware and software requirements remain the same as the requirements for Resource Manager Essentials 4.0.

To check the hardware and software requirements for RME 4.0, see the section:

http://www.cisco.com/univercd/cc/td/doc/product/rtrmgmt/cw2000/cw2000e/
e_4_x/4_0/install/sol/install.htm#wp1105005

This section is a part of the Installation and Setup Guide for Resource Manager Essentials 4.0 on Solaris at:

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

Downloading the Application

You can download RME 4.0 SP2 either from Cisco.com, or as a Software Update from Common Services > Software Center > Software Update. See:

Downloading From Cisco.com

Downloading From Software Center

Downloading From Cisco.com

To download RME 4.0 SP2:


Step 1 Go to http://www.cisco.com/cgi-bin/tablebuild.pl/cw2000-rme.

Step 2 Login using your Cisco.com username and password.

Step 3 Locate the file, cwrme4_0_2_sol.zip

Step 4 Download the file into a temporary location on your system.


Downloading From Software Center

In Common Services 3.0, you can use the Software Center feature (CiscoWorks Common Services > Software Center) to download RME 4.0 SP2.

To download RME 4.0 SP2:


Step 1 From the Common Services Home Page, select Common Services > Software Center > Software Update.

The Software Updates page appears.

Step 2 In the Products Installed table, select the check box corresponding to Resource Manager Essentials.

Step 3 Click either:

Download Updates—See Using the Download Updates Option

Or

Select Updates—See Using the Select Updates Option


Using the Download Updates Option

To download RME 4.0 SP2 using the Download Updates option:


Step 1 Click Download Updates in the Software Updates page.

The CCO and Proxy Server Credentials dialog box appears.

Step 2 Enter your CCO username and password.

If you have configured proxy settings under Common Services > Server > Security > Cisco.com Connection Management > Proxy Server Setup, enter the Proxy server username and password.

Step 3 Click Next.

The Destination Location page appears.

Ensure that the destination location is not the location where CiscoWorks is installed.

We recommend that you download device or software updates in a directory other than the one where you have installed CiscoWorks Common Services, or any of its sub-directories.

Step 4 Enter the location, or browse to the location using the Browse tab.

Ensure that the destination location has casuser write-permissions.

Step 5 Click Next.

The Summary page appears, with the summary of your inputs.

Step 6 Click Finish.

RME 4.0 SP2 (cwrme4_0_2_sol.zip) is downloaded to a sub-directory named rme, in the destination location that you had selected in Step 4.


Using the Select Updates Option

To download RME 4.0 SP2 using the Select Updates option:


Step 1 Click Select Updates in the Software Updates page.

The CCO and Proxy Server Credentials dialog box appears.

Step 2 Enter your CCO username and password.

If you have configured proxy settings under Common Services > Server > Security > Cisco.com Connection Management > Proxy Server Setup, enter the Proxy server username and password.

The Available Images page appears:

Step 3 Select cwrme4_0_2_sol.zip

Step 4 Click Next.

The Destination Location page appears.

Ensure that the destination location is not the location where CiscoWorks is installed.

We recommend that you download device or software updates in a directory other than the one where you have installed CiscoWorks Common Services, or any of its sub-directories.

Step 5 Enter the location, or browse to the location using the Browse tab.

Ensure that the destination location has casuser write-permissions.

Step 6 Click Next.

The Summary page appears, with the summary of your inputs.

Step 7 Click Finish.

RME 4.0 SP2 (cwrme4_0_2_sol.zip) is downloaded to a sub-directory named rme, in the destination location that you had selected in Step 5.


Installing the Application

This section has the following topics:

Pre-requisites for Installing RME 4.0 SP2

Installing RME 4.0 SP2

Pre-requisites for Installing RME 4.0 SP2

Before you install RME 4.0 SP2, ensure that you have installed the following applications:

Common Services 3.0

RME 4.0 or RME 4.0 SP1

Common Services 3.0 SP2

For details about installing these application see "RME 4.0 SP2 Related Documentation".


Caution After you install RME 4.0 SP2, you will not be able to uninstall it. You will need to uninstall RME 4.0 to remove RME 4.0 SP2.

Before installing RME 4.0 SP2, we recommend that you back up your RME 4.0 data using Common Services > Server > Admin > Backup.

See the section "Backing up Your Data", in Installation and Setup Guide for Resource Manager Essentials on Solaris: http://www.cisco.com/univercd/cc/td/doc/product/rtrmgmt/cw2000/cw2000e/
e_4_x/4_0/install/sol/install.htm#wp1118037

Installing RME 4.0 SP2

This section provides information on installing RME 4.0 SP2 on Solaris platform.

You can download the installable image either from Cisco.com or from Common Services Software Center. See "Downloading the Application".

See "Pre-requisites for Installing RME 4.0 SP2" before installing RME 4.0 SP2

To install RME 4.0 SP2 on Solaris:


Step 1 Navigate to the location on your system, where you downloaded cwrme4_0_2_sol.zip.

Step 2 Unzip cwrme4_0_2_sol.zip file by entering:

unzip cwrme4_0_2_sol.zip

After unzipping, the cwrme4_0_2_sol.zip file, the setup.sh file is saved in the folder cwrme4_0_2_sol.

Step 3 Run the installation program by entering:

./setup.sh

A welcome message appears:

Welcome to Resource Manager Essentials 4.0 SP2 setup program.

If you have not installed Common Services 3.0 SP2, this message appears:

Install CiscoWorks Common Services 3.0 Service Pack 2, or later, before installing RME 4.0 Service Pack 2.

You can download and install Common Services 3.0 SP2 from this location:

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

For more details see the Readme Document for Common Services 3.0 Service Pack 2 available at that location.

After installing Common Services 3.0 SP 2, resume from Step 3

Since RME 4.0 SP2 cannot be uninstalled alone, a message prompts you to back up the database:

Because the RME 4.0 SP2 cannot be uninstalled, we recommend that you backup the database before proceeding with installation.

Please refer to the RME 4.0 SP2 readme file for details.

Have you backed up the database? (y/n) [n]:y

If you have backed up your database, enter y to proceed with the installation.

If you have not backed up your database, enter n.

If you select n the following warning message appears:

WARNING: Cisco recommends that you back up the database before installing the RME 4.0 SP2.

WARNING: Do you want to proceed without backing up the database? (y/n) [y]:

If you select y the installation proceeds and if select n the installation aborts.

To back up your database, see the section "Backing up and Restoring of Data".

A message appears:

Press ENTER to read/browse the following License Agreement :

Step 4 Press Enter to read the license agreement.

The following message appears at the end of the license agreement:

You must accept this License agreement for the installation to

proceed.

If you enter N/n, the installation will exit.

Do you accept all the terms of the preceding License Agreement ?

(y/n)

Step 5 Either:

Enter y to accept the license and continue with the installation.

Or

Enter n to stop the installation.

If you accepted the license agreement, the installation proceeds.

This message appears after the installation is complete:

To ensure that you retain the latest device support, please install the latest Device Packages from CCO @ http://www.cisco.com/cgi-bin/tablebuild.pl/cw2000-rme.

Please refer to the Installation and Setup Guide for details.

Please install/upgrade all the required apps in the bundle and then run the migration scripts to restore data from older version of RME.

See "Backing up and Restoring of Data" for more information.

The installation program installs RME 4.0 SP2 in the same directory where you have installed RME 4.0.


Verifying the Installation

To check whether RME 4.0 SP2 is installed successfully:


Step 1 Log into CiscoWorks.

Step 2 Go to Common Services > Software Center > Software Update.

The Software Updates page appears.

Step 3 Check the version for Resource Manager Essentials in the Products Installed table.

If RME 4.0 SP2 is installed successfully, it will be listed as 4.0.2.


Backing up and Restoring of Data

You can restore the data backed up from a server that has RME 4.0 SP2, RME 4.0 SP1, RME 4.0, RME 3.5 with or without IDU or RME 3.4 with or without IDU on a server that has RME 4.0 SP2 installed.

You must not restore the data backed up from a RME 4.0 SP2 server, on a server that has RME 4.0 installed.

Based on your installation, select either of these procedures to restore your RME data:

Restoring All RME 4.0 SP1 and SP2 Data

Restoring All RME 3.x Data

Restoring NetShow Data

If you want to restore RME 4.0 data then see the section, "Data Migration from an Earlier Version" in the Installation and Setup Guide for Resource Manager Essentials 4.0 on Solaris:

http://www.cisco.com/univercd/cc/td/doc/product/rtrmgmt/cw2000/cw2000e/
e_4_x/4_0/install/sol/install.htm#wp1117925


Caution Use this procedure only if you are migrating all your data from RME 3.x to RME 4.0 SP2. This migration script cleans up the database. Therefore, all user-created data (for all applications) between RME 4.0 and RME 4.0 SP2 will be lost.

If you want to restore only NetShow data, use the procedure given in the section "Restoring NetShow Data".

Restoring All RME 4.0 SP1 and SP2 Data

You can restore all the RME4.0 SP1/RME4.0 SP2 backup data using restorebackup.pl available at NMSROOT/bin/restorebackup.pl

To restore all RME 4.x data, follow the procedure described in Data Migration From an Earlier Version, in Installation and Setup Guide for Resource Manager Essentials 4.0 on Solaris:

http://www.cisco.com/univercd/cc/td/doc/product/rtrmgmt/cw2000/cw2000e/
e_4_x/4_0/install/sol/install.htm#wp1117925

Restoring All RME 3.x Data

If you are installing RME 4.0 and RME 4.0 SP2 for the first time, and if you want to restore the complete RME 3.x data, follow the procedure described in Data Migration From an Earlier Version, in Installation and Setup Guide for Resource Manager Essentials 4.0 on Solaris: http://www.cisco.com/univercd/cc/td/doc/product/rtrmgmt/cw2000/cw2000e/
e_4_x/4_0/install/sol/install.htm#wp1117925

Restoring NetShow Data

This procedure is applicable if you had previously installed RME 4.0, and restored all other RME data except for NetShow data.

All the RME 3.x User Defined Command Sets and the Commands associated with those command sets are migrated to RME 4.0 SP2. The migrated Command Sets will not have any device type associated with them. You must edit them before using them in jobs.

Follow this procedure to restore only the RME 3.x NetShow data that you had backed up earlier, while upgrading from RME 3.x to RME 4.0:


Step 1 Log in as the local administrator on the system on which you installed RME 4.0 SP2.

Shut down the daemon manager. To do this, enter:  
/etc/init.d/dmgtd stop
Run the command: 
/opt/CSCOpx/bin/perl 
/opt/CSCOpx/MDC/tomcat/webapps/rme/WEB-INF/classes/com/cisco/nm/rmeng/
config/netshow/migration/RestoreNetshowData.pl -d backup location -gen 
version
Example: 
/opt/CSCOpx/bin/perl 
/opt/CSCOpx/MDC/tomcat/webapps/rme/WEB-INF/classes/com/cisco/nm/ 
rmeng/config/netshow/migration/RestoreNetshowData.pl -d 
/ciscoworks/rmebackupdata -gen 0

where:
/opt/CSCOpx—CiscoWorks installation directory.

-d backup location—Location where RME 3.4 or RME 3.5. backup data is available. This is mandatory.

-gen version—Version to be migrated to RME 4.0. This is mandatory.

After the migration is complete you will see this message:

NetShow Data migrated successfully.

Step 2 Start the daemon manager, by entering:

/etc/init.d/dmgtd start

You have migrated NetShow Data into RME 4.0 SP2.


Uninstalling the Application

You cannot uninstall RME 4.0 SP2 alone. To uninstall RME 4.0 SP2, you must uninstall RME 4.0.

To uninstall RME 4.0 see the uninstallation procedure in the Installation and Setup Guide for Resource Manager Essentials 4.0 on Solaris:

http://www.cisco.com/univercd/cc/td/doc/product/rtrmgmt/cw2000/cw2000e/
e_4_x/4_0/install/sol/install.htm#wp1128514

Re-installing RME 4.0 SP2

To reinstall RME 4.0 SP2, follow the instructions in the section, "Installing the Application":


Caution If you re-install RME 4.0 over RME 4.0 SP2, you will lose all RME 4.0 SP2 functionality. You will have to re-install RME 4.0 SP2 over RME 4.0, to regain the RME 4.0 SP2 functionality.

RME 4.0 SP2 Related Documentation

The following product documentation is available:


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.


Documentation for Common Services 3.0

On Cisco.com at http://www.cisco.com/univercd/cc/td/doc/product/rtrmgmt/cw2000/cw2000_d/
comser30/index.htm
.

Documentation for Resource Manager Essentials 4.0

On Cisco.com at: http://www.cisco.com/univercd/cc/td/doc/product/rtrmgmt/cw2000/cw2000e/
e_4_x/4_0/index.htm

Context-Sensitive Online Help for Resource Manager Essentials

To access the Online help select an option from the navigation tree and click Help (extreme right corner of your browser window).

The RME device package support for RME 4.0 is available at install time. You can access the device package help from the Online help.


Step 1 Select an option from RME desktop and click Help.

The Help launches in a separate browser window.

Step 2 Click Main at the extreme right corner of the page.

The Help window is refreshed and you see these nodes in the left navigation pane:

CiscoWorks Common Services

Resource Manager Essentials

Step 3 Expand the Resource Manager Essentials node.

The following leaf and node appear in the left navigation pane:

RME User Guide (leaf)

Device Packages (node)

Step 4 Expand the Device Packages node to view the help for device packages.


Known and Resolved Problems

This section lists the problems known to exist in this release as well the earlier releases. This section also provides information the problems resolved since the last release of RME 4.0

This section has these topics:

Known and Resolved Problems in RME 4.0 SP2

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

Known and Resolved Problems in RME 4.0 SP2

This section lists the known problems in RME 4.0 SP2.

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

Table 2 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 3 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 4 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 5 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 6 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 7 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 8 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 9 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 10 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 11 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 12 Resolved Problems in RME 4.0 SP2 

Bug ID
Summary

CSCsb29026

IfEntry.IfIndex has 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 are shown as `0' if they are in alphanumeric format.


Known Problems in RME 4.0 SP1

This section lists the known problems in RME 4.0 SP1.

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

Table 13 Known Problems in Installation 

Bug ID
Summary
Explanation

CSCsb50498

RME 4.0 SP1 does not back up NetShow jobs when you run a backup.

NetShow jobs are not getting backed up when when backup is run in RME 401.

As a result NetShow jobs could not be restored in Reinstall in RME 401 or Upgrades from RME401'

Workaround:

None

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 14 Known Problems in Server, Browser, and Desktop 

Bug ID
Summary
Additional Information

CSCsa95781

CTMJrmServer goes down after you change to the ACS mode.

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

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

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

The CTMJrmServer process may go down because of authorization failure at startup. This happens because the System Identity user is not configured properly in ACS.

CSCsa95781

(Continued)

CTMJrmServer goes down after changing to ACS mode.

(Continued)

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

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

Or

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

Workaround:

1. Make the ACS-related Securitychanges.

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

3. 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 15 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 RME 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 you cannot select it.

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

You can see the SNMP timeout exceptions 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 16 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 17 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 do not appear 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 earlier are deleted. This may occur when you copy or retry jobs.

Workaround:

Select the task and re-create the instances.

To create instances of tasks, see the User Guide for Resource Manager Essentials or the RME 4.0 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 enable TACACS + authentication.


Table 18 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, there were some 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:

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

These custom commands will be migrated as if they were 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 when you want to remove an adhoc command and do the following:

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. Slect the ad hoc command that you want to delete, from the Selected Commands list and click Remove.

The command moves to the Available Commands list.

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

An error appears:

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

The Adhoc command is not deleted.

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. Again, enter the Edit flow from the Commands Sets page (in the Resource Manager Essentials > Tools > NetShow > Command Sets flow).

3. Select the command set you want to edit and click Edit) and follow the same procedure detailed above.

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

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

CSCsb09234

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 a voluminous output.

Workaround:

Do any of the following:

Use the per-device print option.

Increase the Tomcat heap-size.

Reduce the number of devices in the job.

CSCsa75907

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

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

This occurs in the command set creation flow of NetShow (Resource Manager Essentials > Tools > NetShow > Command Sets).

This occurs when 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 19 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 20 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.

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

CSCsb19581

rcp does not work for Windows 2003 Server

Image transfer using rcp protocol fails in Windows 2003.

This happens when CiscoWorks is installed on Windows 2003.

Workaround:

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

2. Retry the image transfer.

CSCsb19467

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

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

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

Workaround:

None.

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.