Table Of Contents
Readme for Resource Manager Essentials 4.0 Service Pack 1
on Windows
Description
New Features of RME 4.0 SP1
NetShow, Contract Connection, and SmartCase Applications
Support for SSHv2
New Device Support
Hardware and Software Requirements
Downloading the Application
Downloading From Cisco.com
Downloading From Software Center
Installing the Application
Pre-requisites for Installing RME 4.0 SP1
Installing RME 4.0 SP1
Verifying the Installation
Backup and Restore of Data
Restoring All RME 3.x Data
Restoring NetShow Data
Uninstalling the Application
Re-installing RME 4.0 SP1
RME 4.0 SP1 Related Documentation
Known and Resolved Problems
Readme for Resource Manager Essentials 4.0 Service Pack 1
on Windows
This Readme is for Resource Manager Essentials 4.0 Service Pack 1 (RME 4.0 SP1), on Windows.
It contains the following sections:
•
Description
• New Features of RME 4.0 SP1
• New Device Support
• Hardware and Software Requirements
• Downloading the Application
• Installing the Application
• Backup and Restore of Data
• Uninstalling the Application
• Re-installing RME 4.0 SP1
• RME 4.0 SP1 Related Documentation
• Known and Resolved Problems
Description
The RME 4.0 SP1 release has these new features/applications:
•NetShow
•Contract Connection
•SmartCase
For more details, see "NetShow, Contract Connection, and SmartCase Applications"
The RME 4.0 SP1 release also provides:
•Support for SSHv2 (see "Support for SSHv2").
•Additional device support (see the section, "New Device Support").
•Bug fixes on RME 4.0 (see Table 9).
For more details, see "New Features of RME 4.0 SP1".
New Features of RME 4.0 SP1
The main new features of RME 4.0 SP1 are:
• NetShow, Contract Connection, and SmartCase Applications
• Support for SSHv2
NetShow, Contract Connection, and SmartCase Applications
These new applications are available in RME 4.0 SP1:
•NetShow—Enables you to define command sets with show commands and run these commands on devices.
•Contract Connection—Enables you to verify the service contracts for your Cisco IOS devices. You can also view the contract details of those devices.
•SmartCase—SmartCase enables to open, query or update a TAC Service request.
For more on these features see the RME 4.0 help. To access help see "Accessing RME 4.0 SP1 Help".
Accessing RME 4.0 SP1 Help
The help for the new features of RME 4.0 SP1 is available as part of the User Guide for Resource Manager Essentials:
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 SP1.
To launch and access the Online help see the topic "Context-Sensitive Online Help for Resource Manager Essentials" in the section, "RME 4.0 SP1 Related Documentation".
For the other new features in this release, see "Description".
This table maps the new applications with the relevant sections in the User Guide or in the Online help:
New Application
|
Section/Chapter of User Guide/ Online Help
|
Description
|
NetShow
|
Using NetShow Commands
Using cwcli Commands
|
This section or chapter describes how to use the NetShow application.
NetShow enables you to define show commands within Command Sets and run these commands. It also enables you to analyze the output of the show commands.
The CLI command cwcli netshow is also available. The CLI command cwcli netshow is also available. The cwcli netshow commands let you use NetShow features from the command line. You can use the cwcli netshow commands to view, browse, create, delete, and cancel NetShow jobs.
|
SmartCase
|
Working With SmartCase
|
This section or chapter describes how to use the SmartCase application.
SmartCase enables you to access Cisco.com from Resource Manager Essentials (RME) to open a TAC service request, or to query and update an existing case.
|
Contract Connection
|
Working With Contract Connection
|
This section or chapter describes how to use the Cisco Contract Connection application.
Contract Connection lets you verify the service contracts for your Cisco IOS devices. You can also view the contract details for those devices.
|
Support for SSHv2
RME 4.0 SP1 supports Secure Shell Version 2 (SSHv2).
When you select the SSH protocol for the RME applications (Configuration Archive, NetConfig, ConfigEditor, NetShow and Software Management) the underlying transport mechanism checks whether the device is running SSHv2.
If so, it tries to connect to the device using SSHv2.
If the device does not run SSHv2 and runs only SSHv1 then it connects to the device through SSHv1.
If the device runs both SSHv2 and SSHv1, then it connects to the device using SSHv2.
If a problem occurs while connecting to the device using SSHv2, then it does not fall back to SSHv1 for the device that is being accessed.
Some useful URLs on configuring SSHv2 are:
•Configuring Secure Shell on Routers and Switches Running Cisco IOS:
http://www.cisco.com/warp/public/707/ssh.shtml
•How to Configure SSH on Catalyst Switches Running Catalyst OS:
http://www.cisco.com/en/US/tech/tk583/tk617/
technologies_tech_note09186a0080094314.shtml
•Configuring the Secure Shell Daemon Protocol on CSS:
http://www.cisco.com/en/US/partner/products/hw/contnetw/ps792/
products_configuration_guide_chapter09186a00801eea45.html#1105358
•Configuration Examples and TechNotes:
– http://www.cisco.com/en/US/tech/tk583/tk617/
tech_configuration_examples_list.html
– http://www.cisco.com/univercd/cc/td/doc/product/software/ios123/
123newft/123t/123t_4/gt_ssh2.htm
New Device Support
To view the supported RME applications and sysObjectIDs for the following devices, see the Supported Devices Table for RME 4.0 at this URL:
http://www.cisco.com/univercd/cc/td/doc/product/rtrmgmt/cw2000/cw2000e/
e_4_x/4_0/sdt/rme40.htm
Table 1 NewSupported Devices List for RME 4.0 SP1
Device Category
|
Device Type
|
Media Servers
|
Cisco Media Convergence Server
|
Cisco Media Convergence Server
|
Cable Devices
|
uBR 900 Series
|
uBR904, uBR905, uBR924
|
Hubs
|
FastHub
|
For the supported hubs' sysObjectIDs, see the Supported Devices Table for RME 4.0 at this URL:
http://www.cisco.com/univercd/cc/td/doc/
product/rtrmgmt/cw2000/cw2000e/e_4_x/4_0/
sdt/rme40.htm
|
Interfaces and Modules
|
Network Analysis Module
|
NAM1, NAM2, Network Analysis Module for Cisco 2600/3600 Series
|
Cisco 3201 Wireless Mobile Interface Card
|
Cisco 3201 Wireless Mobile Interface Card
|
Cisco Communication Media Module
|
WS-SVC-CMM
|
Cisco Systems Intelligent Gigabit Ethernet Switch Module (IGESM) for IBM eServer BladeCenter
|
IGESM
|
Routers
|
Cisco 800 Series Routers
|
811, 813
|
Cisco 1400 Series Routers
|
1401
|
Cisco 1800 Series Integrated Services Routers
|
1841
|
Cisco IAD2400 Series Integrated Access Devices
|
IAD2431-8FXS, IAD2431-16FXS, IAD2431-1T1E1, IAD2432-24FXS
|
Cisco 2800 Series Integrated Services Routers
|
2801, 2811, 2821, 2851
|
Cisco 3800 Series Integrated Services Routers
|
3825, 3845
|
Cisco 4000 Series
|
4000, 4500, Cisco Distributed Director 4700M
|
Cisco 7000 Series Routers
|
OSR7609, 7613 IOS
|
Cisco 12000 Series Routers
|
12000 PRP
|
Switches
|
Cisco ATM Switches
|
LS1010
|
Cisco Catalyst 2900 Series Switches
|
2948G-GE-TX
|
Cisco Catalyst 2900 Series XL Switches
|
2950T-24 LRE, 2950ST-8 LRE, 2955, 2955C-12, 2955T-12
|
Cisco Catalyst 2948G-L3 Switch
|
Cat2948GL3
|
Cisco Catalyst G-L3 Series Switches
|
3750-Stack (IOS 37XX Stack)
|
Cisco Catalyst 3560 Switches
|
Catalyst IOS 3560-24PS-S
Catalyst IOS 3560-48PS
|
Cisco Catalyst 3750 Switches
|
Catalyst 3750ME
|
Cisco Catalyst 4000 Series IOS Switches
|
4510R SUP V, WS-C4507, WS-C4948
|
Cisco Catalyst 6000 Series IOS Switches
|
6500 SSL, MSFC3, X-6380, WS-C6509-NEBA
|
Catalyst 6000 Wireless Blade
|
SwitchProbes
|
For the supported SwitchProbes' sysObjectIDs, see the Supported Devices Table for RME 4.0 at this URL:
http://www.cisco.com/univercd/cc/td/doc/
product/rtrmgmt/cw2000/cw2000e/e_4_x/4_0/
sdt/rme40.htm
|
Voice Gateways
|
Cisco VG200 Series Gateways
|
VG224
|
Wireless LAN Products
|
Cisco Aironet 350 Series
|
AP350 IOS
|
Cisco Aironet 1300 Series
|
AP1300
|
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/win/install.htm#wp1058078
This section is a part of the Installation and Setup Guide for Resource Manager Essentials 4.0 on Windows 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 SP1 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
You can download RME 4.0 SP1 from Cisco.com.
To download RME 4.0 SP1:
Step 1 Go to http://www.cisco.com/pcgi-bin/tablebuild.pl/cw2000-rme.
Step 2 Login using your Cisco.com username and password.
Step 3 Locate the file:
cwrme4_0_1_win.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 SP1.
To download RME 4.0 SP1:
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 SP1 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 your 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 SP1 (cwrme4_0_1_win.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 SP1 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_1_win.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 SP1 (cwrme4_0_1_win.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 SP1
• Installing RME 4.0 SP1
Pre-requisites for Installing RME 4.0 SP1
Before you install RME 4.0 SP1, ensure that you have installed the following applications:
•Common Services 3.0
•RME 4.0
•Common Services 3.0 SP1
For details about installing these application see "RME 4.0 SP1 Related Documentation".
Installing RME 4.0 SP1
This section provides information on installing RME 4.0 SP1 on Windows platform.
You can download the installable image either from Cisco.com or from Common Services Software Center. See "Downloading the Application".
You must install RME 4.0 SP1 on a server that has Common Services 3.0, Resource Manager Essentials 4.0, and Common Services 3.0 SP1 installed. See "Pre-requisites for Installing RME 4.0 SP1".
Caution If you install RME 4.0 SP1 when AAA mode is set to ACS, all the custom roles you have created will be lost. This happens only with Cisco Secure
ACS version 3.3.x.
To preserve the custom roles you have created, you must ensure that the AAA mode is set to CiscoWorks Local before you install RME 4.0 SP1. You will be allowed to continue installation after changing the AAA mode. While changing to ACS mode after installation, ensure that you have
not selected the
Register all installed applications with ACS checkbox.
To install RME 4.0 SP1 on Windows:
Step 1 Navigate to the location on your system, where you downloaded cwrme4_0_1_win.zip.
Step 2 Unzip the cwrme4_0_1_win.zip file.
Step 3 Double-click cwrme4_0_1_win.exe file.
A dialog box appears with this message:
Do you really want to install Resource Manager Essentials 4.0 SP1?
Step 4 Click Yes to continue installation.
If you have not installed Common Services 3.0 SP1 this message appears:
Install CiscoWorks Common Services 3.0.1 before installing RME 4.0.1.
The installation terminates when you click OK.
You can download and install Common Services 3.0 SP1 from this location:
http://www.cisco.com/pcgi-bin/tablebuild.pl/cw2000-cd-one
For more details see the Readme Document for Common Services 3.0 Service Pack 1 available at that location.
After installing Common Services 3.0 SP 1, resume from Step 1.
Since RME 4.0 SP1 cannot be uninstalled alone, a message prompts you to back up the database. You will be prompted to back up the database:
Because the RME 4.0 SP1 cannot be uninstalled, we recommend that you backup the database before proceeding with installation.
Please refer to the RME 4.0 SP1 readme file for details.
Have you backed up the database?
•If you have backed up your database, click Yes to proceed with the installation.
•If you have not backed up your database, click No.
To back up your database, see the section, "Backup and Restore of Data".
•If you have set the AAA mode to ACS, a dialog box appears with this message:
The AAA mode of this CiscoWorks server is currently set to ACS mode. If you proceed with the installation without changing the AAA mode to CiscoWorks Local,all the custom roles you have created will be lost. To change the AAA mode,
run NMSROOT\bin\perl NMSROOT\bin\ResetLoginModule.pl.
If you change the AAA mode to CiscoWorks Local, make sure that you revert the AAA mode to ACS, after completing the installation. To continue with the installation, without changing the AAA mode, click Yes. To abort the installation, click No.
•Click Yes to continue installation without changing the AAA mode. If you continue installation without changing the AAA mode, all the custom roles you have created will be lost. This happens only with Cisco Secure ACS version 3.3.x.
If you want to preserve the custom roles you have created, set the AAA mode to CiscoWorks Local. For this you must stop the installation and reset the login module before you continue the installation.
•Click No to stop the installation.
If you stop the installation, run the following script to run the following script to reset the login module:
NMSROOT\bin\perl NMSROOT\bin\ResetLoginModule.pl
You can change the login mode to ACS after the installation. While changing to ACS mode, ensure that you do not select the Register all installed applications with ACS checkbox.
The Welcome screen appears.
Step 5 Click Next to continue.
The Software License Agreement dialog box appears.
Step 6 Click Accept to accept the license agreement and proceed with the installation.
A message appears:
To ensure that you retain the latest device support, please install the latest Device Packages from CCO @ http://www.cisco.com/pcgi-bin/tablebuild.pl/cw2000-rme.
Please refer to the Installation and Setup Guide for details.
Step 7 Click OK.
A message appears:
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 "Backup and Restore of Data" for more information.
Step 8 Click OK.
The installation program installs RME 4.0 SP1 in the same directory where you have installed RME 4.0.
The Setup Complete dialog box appears.
Step 9 Click Finish to complete the installation and start CiscoWorks.
Verifying the Installation
To check whether RME 4.0 SP1 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.
It should be listed as 4.0.1.
Backup and Restore of Data
You can restore the data backed up from a server that has RME 4.0 SP1, RME 4.0, RME 3.5 or RME 3.4 on a server that has RME 4.0 SP1 installed.
You must not restore the data backed up from a RME 4.0 SP1 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 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 Windows:
http://www.cisco.com/univercd/cc/td/doc/product/rtrmgmt/cw2000/cw2000e/
e_4_x/4_0/install/win/install.htm#wp1117199
Caution Use this procedure only if you are migrating all your data from RME 3.x to RME 4.0 SP1. This migration script cleans up the database. Therefore, all user-created data (for all applications) between RME 4.0 and RME 4.0 SP1 will be lost.
If you want to restore only NetShow data, use the procedure given in the section
"Restoring NetShow Data".
Restoring All RME 3.x Data
If you are installing RME 4.0 and RME 4.0 SP1 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 on Windows: http://www.cisco.com/univercd/cc/td/doc/product/rtrmgmt/cw2000/cw2000e/
e_4_x/4_0/install/win/install.htm#wp1117199
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 SP1. 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 SP1.
Step 2 Shut down the daemon manager by entering:
net stop crmdmgtd
Step 3 Run the command:
NMSROOT\bin\perl NMSROOT\MDC\tomcat\webapps\rme\WEB-INF\classes\com\cisco\nm\rmeng\config\netshow\migration\RestoreNetshowData.pl -d backup location -gen version
Where NMSROOT is the CiscoWorks install directory.
For example:
D:\program files\CSCOpx\bin\perl D:\program files\CSCOpx\MDC\tomcat\webapps\rme\WEB-INF\classes\com\cisco\nm\rmeng\config\netshow\migration\RestoreNetshowData.pl -d D:\ciscoworks\rmebackupdata -gen 0
where,
D:\program files\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 optional. By default, this will restore the latest backup data.
After the migration is complete you will see this message:
NetShow Data migrated successfully.
Step 4 Start the daemon manager, by entering:
net start crmdmgtd
You have migrated NetShow Data into RME 4.0 SP1.
Uninstalling the Application
You cannot uninstall RME 4.0 SP1 alone. To uninstall RME 4.0 SP1, 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 Windows:
http://www.cisco.com/univercd/cc/td/doc/product/rtrmgmt/cw2000/cw2000e/
e_4_x/4_0/install/win/install.htm#wp1090092
Re-installing RME 4.0 SP1
To reinstall RME 4.0 SP1, follow the instructions in the section, "Installing the Application":
Caution If you re-install RME 4.0 over RME 4.0 SP1, you will lose all RME 4.0 SP1 functionality. You will have to re-install RME 4.0 SP1 over RME 4.0, to regain the RME 4.0 SP1 functionality.
RME 4.0 SP1 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
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.
Common Services 3.0 SP1 Readmes
http://www.cisco.com/pcgi-bin/tablebuild.pl/cw2000-cd-one
Known and Resolved Problems
Table 2, Table 3, Table 4, Table 5, Table 6, Table 7, Table 8 describe problems known to exist in this release; Table 9 describes problems resolved since the last release of RME 4.0.
This section has these topics:
• Known Problems in Server, Browser, and Desktop
• Known Problems in Inventory
• Known Problems in Configuration Archive
• Known Problems in NetConfig
• Known Problems in NetShow
• Known Problems in Contract Connection
• Known Problems in Software Management
• Resolved Problems in RME 4.0 SP1
For more information about known problems:
Step 1 Go to http://www.cisco.com
Step 2 Select Technical Support & Documentation > Tools & Resources.
Step 3 Then select the Software sub-section and click Bug Toolkit.
Alternatively, go to: http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl
You will be prompted to log into Cisco.com.
Table 2 Known Problems in Server, Browser, and Desktop
Bug ID
|
Summary
|
Additional Information
|
CSCsa95781
|
CTMJrmServer goes down after changing to the ACS mode.
|
The CTMJrmServer process may go down in any one of these cases with respect to ACS configuration:
•When you change the AAA setup from the CiscoWorks local mode to the ACS mode (thorough Common Services > Server > Security > AAA Mode Setup) and register with ACS by enabling the Register all installed applications with ACS option in the AAA Mode Setup dialog box.
•When you re-register the applications with ACS (by enabling the Register all installed applications with ACS option in the AAA Mode Setup screen) while in the ACS mode.
•When you install RME 4.0 SP1 in the ACS mode. If the CiscoWorks Server is in the ACS mode, the RME 4.0 SP1 installation warns you that you need to change to CiscoWorks Local Mode before continuing with the installation. However, if you continue with the installation in the current ACS mode (by choosing Yes when the warning message appears), this issue may occur.
The CTMJrmServer process may go down because of authorization failure at startup. This happens because the System Identity user is not configured properly in ACS.
|
CSCsa95781
(Continued)
|
CTMJrmServer goes down after changing to ACS mode.
(Continued)
|
The reasons for CTMJrmServer process to go down in the above cases can be:
•System Identity user (in the System Identity Setup dialog box under Common Services > Server > MultiServer Trust Management > System Identity Setup) is not configured in ACS.
Or
•The System identity user configured in ACS does not have the necessary JRM job privileges.
Workaround:
Follow these steps:
1. After making the ACS-related security changes, ensure that the System Identity user is configured properly in ACS with the necessary JRM job privileges. To configure the System Identity user, use the System Identity Setup dialog box under Common Services > Server > MultiServer Trust Management > System Identity Setup.
2. Restart the CTMJrmServer process and the other dependent processes (such as Syslog).
|
| |
Table 3 Known Problems in Inventory
Bug ID
|
Summary
|
Explanation
|
CSCsb00224
|
WS-SVC-NAM-1 is displayed as Generic class in Chassis Summary Graph
|
NAM-1 device chassis type WS-SVC-NAM-1 is classified as Generic in Chassis Summary Graph.
The containment collection for this device is not supported. Therefore, the vendor type is not available to the application to classify the device chassis type appropriately.
Workaround:
None.
|
CSCsa79594
|
Misalignment of fields in Inventory Job Browser
|
The fields, Job ID, Job Type, Status, Description, Owner, Scheduled at, Completed at, Schedule Type, are aligned in the Inventory Job Browser only when there are 10 or less than 10 jobs in the Job Browser.
If there are more than 10 jobs in the Job Browser, the fields are not aligned.
Workaround:
None.
|
CSCsa86823
|
A device in the normal state appears with ? icon and cannot be selected.
|
The Device Selector shows ? as the icon for a normal device for which configuration collection is successful.
Device and Credential Repository (DCR) did not have the device type information while the device was added.
Inventory collection failed because of SNMP time-out.
Workaround:
•Update the device type information in DCR.
•Make sure that the inventory collection succeeds (if required, increase the SNMP time-out value).
Note SNMP timeout exceptions can be seen in IC_server.lnog.
For details on editing device information in DCR, increasing SNMP time-out values, etc., see the User Guide for Resource Manager Essentials or the RME 4.0 SP1 Online help.
|
Table 4 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 5 Known Problems in NetConfig
Bug ID
|
Summary
|
Explanation
|
CSCsa98053
|
Deselecting NetConfig tasks removes the associated task instances
|
In the NetConfig Jobs edit flow (Resource Manager Essentials > Config Mgmt > NetConfig > NetConfig Jobs) in the Devices and Tasks page, if you deselect a task, its instances will not be displayed in the Add Tasks page (next page).
If you return to the Device and Tasks page, re-select the task, and then navigate to the Add tasks page again, the instances that you had created earlier, will not re-appear.
When you deselect a NetConfig task all the instances that were added previously are deleted. This may occurs when you copy or retry jobs.
Workaround:
Select the task and re-create the instances.
To create instances of tasks, see the User Guide for Resource Manager Essentials or the RME 4.0 SP1 Online help.
|
CSCsa78026
|
Adhoc Enable Mode command, sh run fails for some string patterns
|
When you create a NetConfig Job with the Adhoc Enable Mode Command sh run, the job status may be reported as Failed even if the commands have been successfully downloaded.
This may occur when the successfully downloaded command output contains well-known error messages such as ERROR:, %ERROR: etc., (which are ideally a part of the command output during error conditions only).
Workaround:
None.
|
CSCsa88089
|
Job Details page: Edit/Copy/Retry/Stop/Delete buttons missing
|
Edit/Copy/Retry/Stop or Delete buttons are missing from the Job Details page.
Workaround:
Use the buttons in the Job Browser page.
|
CSCsa88829
|
Issue with credentials removal in DCR with NetConfig job, when AAA new-model is enabled
|
When you are disabling credentials using NetConfig, the device may become unreachable from within RME.
However the device remains reachable outside RME.
This may occur when you disable or remove credentials such as Telnet password using a system-defined task in NetConfig.
Workaround:
To enable TACACS authentication, you should use the TACACS+ task and not the Telnet Password task.
To disable one kind of authentication, you should enable another kind of authentication.
For example, if you want to disable Telnet authentication and enable TACACS+ authentication, you can simply enable TACACS + authentication.
|
Table 6 Known Problems in NetShow
Bug ID
|
Summary
|
Explanation
|
CSCsa67327
|
Netshow Admin options appear under Config Mgmt.
|
NetShow Admin settings are provided in the Transport Settings page under Resource Manager Essentials > Admin > Config Mgmt although NetShow is listed under Resource Manager Essentials > Tools.
NetShow uses the APIs provided by ArchiveManagement and ConfigJob. Therefore the Admin settings are listed under Config Management.
Workaround:
None.
|
CSCsa86905
|
Custom commands, that are not assigned to any Command Sets, are not migrated
|
This occurs if:
1. In RME 3.x, in NetShow, you had a few isolated custom commands that were not associated with any command set.
2. You backed up and migrated these custom command sets into RME 4.0 SP1.
These isolated custom commands do not exist in RME 4.0 SP1 NetShow after migration.
Workaround:
You can associate these isolated custom commands with any user-defined command set in RME 3.x, before taking a backup. Then these custom commands will be migrated as if they were a part of a command set.
|
CSCsa73709
|
Cannot remove an Adhoc command from the Available Commands list
|
You may not be able to delete an Adhoc command from the Available Commands list (in the Select Commands page of the Resource Manager Essentials > Tools > NetShow > Command Sets flow) even if it is in only one command set.
This occurs in this following scenario when you want to remove an adhoc command:
1. In the Resource Manager Essentials > Tools > NetShow > Command Sets flow and from the Command Sets page, select the command set you want to edit and click Edit. The Select Device Category Page appears.
2. Click Next.
3. Now select the ad hoc command that you wish to delete, from the Selected Commands list and click Remove.
The command moves to the Available Commands list.
4. Now select the command from the Available Commands list and click Delete Adhoc.
You will see an error:
NS0011 :The command(s) show run are not deleted because they may be system-defined or part of a command set or in the selected commands list.
The Adhoc command is not deleted.
|
CSCsa73709
(Continued)
|
Cannot remove an Adhoc command from the Available Commands list
(Continued)
|
Workaround:
1. In the Edit flow detailed above, after Step 3.click Finish.
2. Once again, enter the Edit flow from the Commands Sets page (in the Resource Manager Essentials > Tools > NetShow > Command Sets flow and from the Command Sets page, select the command set you want to edit and click Edit) and follow the same procedure detailed above.
3. This time when you select the command from the Available Commands list and click Delete Adhoc.
You will see a message that the command is successfully deleted.
|
CSCsb09234
|
OutOfMemoryexception on printing job output
|
A 500 server error appears with an out-of-memory exception when you print NetShow Job Results.
This may occur when the job has more than 1500 devices and has a high number of commands that produce voluminous output.
Workaround:
To overcome this problem you can:
•Use the per-device print option.
•Increase the Tomcat heap-size.
•Reduce the number of devices in the job.
|
CSCsa75907
|
Cannot add Adhoc commands that are device-specific, in the same command set.
|
You cannot add device type-specific Adhoc commands in the same command set. The Adhoc commands that you have added in a specific command set apply to all the device types that you have selected.
This scenario occurs when, in the command set creation flow of NetShow (Resource Manager Essentials > Tools > NetShow > Command Sets), you:
1. Choose device categories
2. Add Adhoc commands.
3. Complete the flow.
These Adhoc commands will be applicable to all the device types that you have selected.
For example, if you choose device types Content Networking and Router and added an Adhoc command, say A, then this command will be applicable to both Content Networking and Router device types.
Workaround:
Create different command sets for different device types.
For details on creating command sets, see User Guide for Resource Manager Essentials, or the RME 4.0 SP1 Online help
|
Table 7 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 8 Known Problems in Software Management
Bug ID
|
Summary
|
Explanation
|
CSCsb02631
|
Image import job fails and displays the error Invalid data dir
|
Sometimes, the restore operation fails because the DCRServer process does not come up.
The Restore operation prompts you to confirm whether to restore the certificate. This problem occurs if you select Y (Yes) for Certificate restore, and the certificate has expired.
Workaround:
1. Restart the daemon manager.
2. From the Common Services desktop, select Common Services > Server > Security> Single-Server Management > Certificate Setup.
3. Click Apply.
4. Stop the daemon manager and trigger the Restore operation.
During the Restore operation you should select N (No), when you are prompted to restore the Certificate.
|
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
|
Sofware 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.
|
After you install RME 4.0 SP1, the following problems from RME 4.0 will be resolved:
Table 9 Resolved Problems in RME 4.0 SP1
Bug ID
|
Summary
|
CSCsa89297
|
Setting a proxy may break other applications
|
CSCsa75824
|
RME Sybase Engine will not start with 4 GB memory on Windows 2003.
|
CSCsa55592
|
NAM: SNMP Traps community string shown in clear text
|
CSCsa55916
|
Enable username not needed in Config Editor jobs
|
CSCSa57860
|
Compare and deploy job—Problem in Job Password.
|
CSCsa58229
|
Job password enabled job fails with Synch archive before job execution policy
|
CSCsa46785
|
Incorrect Inventory Change Report for AUS managed PIX device.
|
CSCsa43295
|
Catalyst 5000—Incorrect Inventory Change Report
|
CSCsa38653
|
LMS 2.5-Problem with Syslog message filter after hostname change.
|
CSCsa89304
|
Setting a proxy may break other applications
|
CSCsa55923
|
Issue in Undo/Retry Jobs
|
CSCsa01751
|
Software Management tool should set switch autologout to a proper value for NAM upgrade.
|
CSCsa57873
|
Software Management: Distribution Jobs do not work for Cat6000 MWAM Device.
|
