Table Of Contents
Release Notes for Resource Manager Essentials 4.0.3 on Windows
New Features
New Features of Inventory
New Features of Device Management
New Features of Archive Management
New Features of Config Editor
New Features of NetConfig
New Features for Job Approval
New Features of Reports
New Features of Syslog
New Features of Change Audit and Audit Trail
New Features of Software Management
New Features of Job Management
NetShow, Contract Connection, and SmartCase Applications
Support for SSHv2
New Device Support
Product Documentation
Additional Information Online
Caveats
Known Problems in RME 4.0.3
Installation and Upgrade Known Problems
Administrator Known Problems
Device Management Known Problems
Device/Agent Known Problems Impacting ANI Server and RME Functionality
Inventory Known Problems
Archive Management Known Problems
NetConfig Known Problems
Config Editor Known Problems
Netshow Known Problems
Software Management Known Problems
Change Audit Known Problems
Syslog Known Problems
cwcli export Known Problems
Contract Connection Known Problems
Bug Toolkit Known Problems
Server, Browser, and Desktop Known Problems
Common/Other Known Problems
Resolved Problems in RME 4.0.3
Customer-found Problems Resolved in RME 4.0.3
Problems Resolved in RME 4.0 SP2, RME 4.0 SP1 and RME 4.0
Obtaining Documentation
Cisco.com
Product Documentation DVD
Ordering Documentation
Documentation Feedback
Cisco Product Security Overview
Reporting Security Problems in Cisco Products
Obtaining Technical Assistance
Cisco Technical Support & Documentation Website
Submitting a Service Request
Definitions of Service Request Severity
Obtaining Additional Publications and Information
Release Notes for Resource Manager Essentials 4.0.3 on Windows
These Release Notes contain information about new features. They provide pointers to device support information and also provide information about the known and resolved problems in this release.
For the details about the supported Windows versions see the Installation and Setup Guide for Resource Manager Essentials 4.0.3 on Windows.
These Release Notes provide:
•
New Features
•Product Documentation
•Additional Information Online
•Caveats
•Known Problems in RME 4.0.3
•Resolved Problems in RME 4.0.3
•Obtaining Documentation
•Documentation Feedback
•Obtaining Technical Assistance
•Obtaining Additional Publications and Information
New Features
This section discusses the new features in RME 4.x releases.
RME 4.0.1 (RME 4.0 SP1) and RME 4.0.2 (RME 4.0 SP2), the incremental releases over RME 4.0 have been rolled into RME 4.0.3 (RME 4.0 SP3).
RME 4.0.3 and RME 4.0 Service Packs 1 and 2 provide new device support, and bug fixes over the previous releases.
RME 4.0 provided new features, new device support, and bug fixes over the RME 3.x releases.
When you install RME 4.0.3, you will get all the features discussed in this section:
•New Features of Inventory
•New Features of Device Management
•New Features of Config Editor
•New Features of NetConfig
•New Features for Job Approval
•New Features of Reports
•New Features of Syslog
•New Features of Change Audit and Audit Trail
•New Features of Software Management
•New Features of Job Management
•NetShow, Contract Connection, and SmartCase Applications
•Support for SSHv2
•New Device Support
The Availability module of RME 3.5 is no longer available, beginning with
RME 4.0.
New Features of Inventory
The Inventory application has the following new features:
•Integration with Device and Credentials Admin (DCA) database.
•All Inventory reports are now schedulable. You can run an immediate report or schedule a report to be run at a specified time.
•You can schedule Inventory Collection and Polling jobs.
•Periodic reports: You can schedule periodic jobs-6-hourly, 12-hourly, daily, weekly, or monthly.
•Export of reports as PDF or in CSV format.
•You can now export devices to a device list, from within a report.
•CLI feature is now available for all system reports (excluding graphs).
New Features of Device Management
The Device Management application has the following new features:
•Import devices from Common Services Device and Credential Repository.
You add devices to RME either manually or automatically. Before adding devices to RME you must add devices into Device and Credential Repository using Common Services > Device and Credentials > Device Management.
You add devices in two ways:
–Adding Devices to RME Manually
–Adding Devices to RME Automatically
By default, the Automatically Manage Devices from Credential Repository option in the Device Management Settings window is enabled.
•Device State Management based on device reach ability.
The device participation in RME application tasks will no longer be dependent on the device being in the Managed State as in earlier releases of RME.
Instead it depends upon the actual device information required by the application task. This change allows RME to better and more flexibly, meet requirements for performing tasks on devices that have not yet been deployed on the network.
•Add RME specific device attributes such as retry counts, timeouts, etc., at per device level.
You can either set a default device attributes value for all RME devices or set different device attributes value for different RME devices.
The RME device attributes includes Serial Number, SNMP timeout, SNMP retry, Telnet timeout, and RME server ID (NAT ID).
New Features of Archive Management
The Archive Management application has the following new features:
•Baseline Template
You can compare the baseline template with the configuration of devices in the archive. You can also generate a non-compliance configuration report and deploy this template on to the devices to make it compliant.
•VLAN configuration is archived independently
VLAN configuration is archived as a separate configuration type. That is, the running configuration and the VLAN configuration files are not archived in pairs.
•Job based Archive Management tasks
All Archive Management tasks on the device, fetch and deploy are job based. You can specify when you want to run the Archive Management jobs. That is, the job can be run immediately, once or periodically. You can configure to send e-mail messages at the beginning and at the end of the job.
•Manual Update of Configuration
You can manually update the configuration archive to check specified devices for changes to the configuration file.
•Enhanced Search Archive
You can search the archive for configuration containing text patterns for selected devices. You can specify ten different combinations of patterns/strings as part of search criteria. You can also create custom queries and use them whenever required.
•Graphical view of configuration versions
You can view all configuration versions of the selected devices in the form of a graphical display. You can also perform a Configuration Quick Deploy operation for a selected device.
•Support for new protocols -SCP, HTTPS.
•Check the configuration archival status using the Device Center.
New Features of Config Editor
The Config Editor application has the following new features:
•Multiple user editing of configuration files simultaneously.
•Baseline configuration creation using baseline templates.
•External configuration files editing.
•Interface to syntax checker.
•Masking credentials.
•Enable password option in job based password.
•Additional protocol support for Configuration Deploy jobs.
New Features of NetConfig
The NetConfig application has the following new features:
•Parameterized User-defined templates
These allow configuration commands in the User Defined Templates to contain user-defined variables. You can enter values for the variables in a text file during the job creation time.
•Periodic Netconfig jobs
Netconfig jobs can be scheduled with periodicity of Daily, Weekly, Monthly and Last Day Of Month. Each instance of periodic schedule is maintained and can be accessed from the job browser.
•Cisco MetaData Framework (MDF) support for User-defined Templates
User-defined templates can be created with more granularity by mapping them to one or more device types represented through MDF. Thus a job can now include different categories of devices.
•Additional protocol support for Configuration Deploy jobs
Netconfig jobs can use any of the protocol supported by Config Management for deploying configuration change jobs.
•You can import, or export of user-defined tasks.
•The cwcli netconfig CLI supports user-defined tasks.
New Features for Job Approval
The Job Approval application has the following new features:
•Separate approval policies for each application.
•Instead of assigning approver-list during each job creation flow, now it can be assigned once for each application.
•Approver has the option to change the schedule of a job before approving.
•Common Services Approvers can be directly synced during the Approver list creation.
New Features of Reports
The Reports application has the following new features:
•You can schedule all reports (except Inventory graphs and Audit Trail report.)
•You can perform reporting tasks such as:
–Generating reports
•Managing reports jobs and archived reports
–Creating custom report templates
•You can purge report jobs and archives purging to manage disk space.
New Features of Syslog
The Syslog application has the following new features:
•Many Collectors and many Analyzers
Syslog processing load can be better balanced by subscribing any number of Syslog Servers to any number of Syslog Collectors.
•Easy Timezone support
Syslog Analyzer supports any timezone, by enabling you to edit the configuration file.
•Drop/Keep filtering
Filtering can be to keep or to drop Syslogs. Filtering now has the capability to consider interfaces also.
•Syslog reports can be scheduled.
•Automated Actions now provide a template for e-mail.
•Import/Export of Automated Actions and Message Filters is possible.
•Force Purge capability is available.
•Syslog backup new feature enables you to keep older messages.
New Features of Change Audit and Audit Trail
The Change Audit application has the following new features:
•Audit Trail
The Audit Trail application tracks and reports changes that the RME administrator makes on the RME server.
•Export Change Audit record in XML format
You can export the Change Audit record in XML format using the cwcli export changeaudit command.
•Change Audit report
You can schedule to run Change Audit reports periodically.
New Features of Software Management
The Software Management application has the following new features:
•Concurrent Image download
You have the provision for scheduling parallel device upgrades in single distribution job.
•Distribute by device in Expert mode
Distribute by device (advanced) workflow provides a quick job creation wizard for advanced Network Management users.
•Add image from URL
You can download images from a remote HTTP server by providing the URL.
•Support for new protocols —SCP, HTTP.
New Features of Job Management
The Job Management application has the following new features:
•Separate approval policies for each application.
•Instead of assigning approver-list during each job creation flow, now it can be assigned once for each application.
•Approver has the option to change the schedule of a job before approving.
NetShow, Contract Connection, and SmartCase Applications
These applications are also available in RME 4.x:
•NetShow—Enables you to define command sets with show commands and run these commands on devices.
•Contract Connection—Enables you to verify the service contracts for your Cisco IOS devices. You can also view the contract details of those devices.
•SmartCase—SmartCase enables to open, query or update a TAC Service request.
Support for SSHv2
RME 4.x supports Secure Shell Version 2 (SSHv2).
When you select the SSH protocol for the RME applications (Configuration Archive, NetConfig, Config Editor, NetShow and Software Management) the underlying transport mechanism checks whether the device is running SSHv2.
If so, it tries to connect to the device using SSHv2.
If the device does not run SSHv2 and runs only SSHv1 then it connects to the device through SSHv1.
If the device runs both SSHv2 and SSHv1, then it connects to the device using SSHv2.
If a problem occurs while connecting to the device using SSHv2, then it does not fall back to SSHv1 for the device that is being accessed.
Some useful URLs on configuring SSHv2 are:
•Configuring Secure Shell on Routers and Switches Running Cisco IOS:
http://www.cisco.com/warp/public/707/ssh.shtml
•How to Configure SSH on Catalyst Switches Running Catalyst OS:
http://www.cisco.com/en/US/tech/tk583/tk617/
technologies_tech_note09186a0080094314.shtml
•Configuring the Secure Shell Daemon Protocol on CSS:
http://www.cisco.com/en/US/partner/products/hw/contnetw/ps792/
products_configuration_guide_chapter09186a00801eea45.html#1105358
•Configuration Examples and TechNotes:
–http://www.cisco.com/en/US/tech/tk583/tk617/
tech_configuration_examples_list.html
–http://www.cisco.com/univercd/cc/td/doc/product/software/ios123/
123newft/123t/123t_4/gt_ssh2.htm
New Device Support
For a list of all devices supported in RME 4.0.3 (RME 4.0 Service Pack 3), including devices supported in previous versions of RME, see the Supported Device Table for Resource Manager Essentials 4.0.3 on Cisco.com:
http://www.cisco.com/univercd/cc/td/doc/product/rtrmgmt/cw2000/cw2000e/
e_4_x/4_0_3/sdt/index.htm
Product Documentation
Note We sometimes update the printed and electronic documentation after original publication. Therefore, you should also review the documentation on Cisco.com for any updates.
The following documents are provided in PDF on your product CD:
•Installation and Setup Guide for Resource Manager Essentials on Windows
•User Guide for Resource Manager Essentials
Note Adobe Acrobat Reader 4.0 or later is required.
Use these publications to learn how to install and use Resource Manager Essentials:
•Installation and Set Up Guide for Resource Manager Essentials on Windows (DOC-7817223=)—Provides installation instructions, including both server and client system requirements, steps for installing and uninstalling, and installation troubleshooting information.
•User Guide for Resource Manager Essentials (DOC-7817221=)—Provides information on using RME 4.0.3.
•User Guide for Common Services (DOC-7817182=)—Provides information about setting up, administering, and accessing CiscoWorks Common Services 3.0.3
•Resource Manager Essentials Online help—Provides task-oriented and context-sensitive help from every window that contains a Help button.
Also contains all of the information available in User Guide for Resource Manager Essentials. This ensures you have complete information even if you do not have the manual readily available while using RME.
For more details on the new features in RME 4.0.3, and the procedures mentioned in this document, see the User Guide for Resource Manager Essentials.
Additional Information Online
For information about RME supported devices, refer to the following URL:
http://www.cisco.com/univercd/cc/td/doc/product/rtrmgmt/cw2000/cw2000e/
e_4_x/4_0_3/sdt/index.htm
Tip For the latest technical tips, suggestions for troubleshooting common issues, and frequently asked questions (FAQs) on most RME applications, you can:
Login to Cisco.com and select Products and Services > Network Management > CiscoWorks LAN Management Solution > CiscoWorks Resource Manager Essentials > Product Literature.
The Incremental Device Update (IDU) for RME 4.0.3 is a collection of updated files necessary for RME to support new Cisco devices. In addition to the devices supported, this package also contains fixes to known problems, as well as additional newly discovered problems.
If you are a registered user, you can download the latest version of IDU for RME 4.0.3 from:
http://www.cisco.com/cgi-bin/tablebuild.pl/cw2000-rme
Caveats
The following are some caveats:
•If the RME Installer window does not appear after you have inserted the
RME 4.0.3 CD-ROM into the CD-ROM drive, do the following:
a. On your desktop, select Start > Run.
The Run dialog box opens.
b. In the Open field, enter drive:\RME\autorun.exe.
where drive is the CD-ROM drive letter.
•Before installing RME, ensure that you do not have CWSI Campus 2.x or Cisco Voice Manager on the system.
•Before upgrading RME, ensure that all applications are stopped. The upgrade depends on having reasonable interaction time with the database. If this is not possible, the upgrade fails.
•Browsers running on remote X servers are not supported in RME.
•If you stop the Daemon Manager, you should wait for 5 minutes before restarting it. Wait for 5 more minutes before performing any tasks. This will ensure that the processes are initialized correctly.
Known Problems in RME 4.0.3
RME 4.0.1 (RME 4.0 SP1) and RME 4.0.2 (RME 4.0 SP2), the incremental releases over RME 4.0 have been rolled into RME 4.0.3 (RME 4.0 SP3).
This section contains the following known problems for RME 4.0.3:
•Installation and Upgrade Known Problems
•Administrator Known Problems
•Device Management Known Problems
•Device/Agent Known Problems Impacting ANI Server and RME Functionality
•Inventory Known Problems
•Archive Management Known Problems
•NetConfig Known Problems
•Config Editor Known Problems
•Netshow Known Problems
•Software Management Known Problems
•Change Audit Known Problems
•Syslog Known Problems
•cwcli export Known Problems
•Contract Connection Known Problems
•Bug Toolkit Known Problems
•Server, Browser, and Desktop Known Problems
•Common/Other Known Problems
For more information about known problems:
Step 1 Go to http://www.cisco.com
Step 2 Select Technical Support & Documentation > Tools & Resources.
Step 3 Then select the Software sub-section and click Bug Toolkit.
Installation and Upgrade Known Problems
Table 1 Installation and Upgrade Known Problems
Bug ID
|
Summary
|
Explanation
|
RME 4.0.3
|
|
|
CSCsc19725
|
Error in RME install log
|
While installing or upgrading to RME 4.0.3, the following error is appears in the install log:
ERROR: Failed to convert the string to Number
Return value of CheckSystemRam is 0
Workaround:
None.
You can ignore this error.
|
CSCsc46237
|
Restore fails even when there is adequate space
|
RME restore operation fails with an insufficient disk space error.
While restoring, the backup data is extracted in the partition where the backup exists. Therefore, if the partition does not have enough space, the insufficient disk space error appears.
Workaround:
Either increase the partition space or copy the backup to a different partition that has enough space.
|
RME 4.0 SP2
|
|
|
CSCsb36922
|
RME installation does not proceed if the Task scheduler not enabled.
|
RME installation waits with the message displayed as:
Please be patient. Installing Device Packages(RME) may take some time.
This problem occurs if the Schedule or Task scheduler on the RME server is not enabled.
Workaround:
1. Copy
NMSROOT\temp\rme_cids_pkgs\*zip to some location folder such as C:\DevicePkgs
To make the installation proceed further, create a blank file, PSUCli.done under NMSROOT\bin\
NMSROOT is the install directory.
2. After the installation is over, stop the daemon manager and follow these steps in command line.
3. Change directory to NMSROOT\bin
4. Run the command
PSUCli.bat -p rme -src c:\DevicePkgs -all -i -noServerRestart
5. After the device packages installation over, start the daemon manger.
|
RME 4.0
|
|
|
CSCsa15596
|
RME installation quits unexpectedly.
|
Errors such as
String variable is not large enough for the String
appear during the installation of Common Services.
This is because NMSROOT (CiscoWorks Install directory) has a very long pathname.
During Common Services installation there is no restriction imposed on the installation directory path length.
Owing to this, Common Services installation might not fail, if the string length is less than 1024.
However, in the case of RME the chances of failures are high because, RME has longer classpaths which are close to 950 characters with NMSROOT length = 39 characters.
Workaround:
Do not to use a long pathname for NMSROOT (CiscoWorks Install directory).
|
CSCsa33360
|
Device groups migrated for users (Approvers and Network Operators) cannot be edited by users with the same roles in RME 4.0
|
Users with Approver and Network Operator roles cannot edit or delete device groups in RME 4.0 that were created in RME 3.x by users with the same roles.
This happens when the device groups created in RME 3.x by users with Approver and Network Operator roles, are migrated to RME 4.0.
Workaround:
None.
|
CSCsa33365
|
Network Administrator cannot edit or delete device groups in RME 4.0 that they created in RME 3.x, after migration.
|
After migration from RME 3.x to RME 4.0, a user with a Network Administrator role cannot edit/delete groups in RME 4.0 that the user created in RME 3.x.
This happens when the device groups created in RME 3.x by a user with a Network Administrator role, are migrated to RME 4.0.
Workaround:
None.
|
CSCsa34359
|
Change Audit details are not available for some of the NetConfig records after data migration from RME 3.x to
RME 4.0.
|
The change details cannot be identified for some of the NetConfig records.
This is because you have purged configuration files in the RME 3.x server where the backup was taken for migration.
These purged configuration files are not available in RME 4.0 server after data migration. An error appears, Internal Error: Config File information not available.
Workaround:
None.
|
CSCsa45325
|
No able to upgrade fromRME 3.4 to RME 4.0 when HPOV is running.
|
This is because during upgrade some of the dll files are locked in this directory, NMSROOT\objects\smarts\bin
Where NMSROOT, is the CiscoWorks installed directory.
Workaround:
Stop the HPOV process while upgrading to RME 4.0.
|
CSCsa22623
|
Data inconsistency on restoring data backed up with jobs in running state.
|
After restoring RME 4.0 data on a system, the job status is not the same as that of the system where the backup was taken.
When a backup is triggered while a job is running, the Restore command is not aware of the state of the jobs in the backed-up machine.
Additionally, the Backup/Restore command does not backup/restore the state of the systems. It is only the data that is backed-up and restored.
Workaround:
Ensure that while backing up data, there are no jobs running on the system.
|
Administrator Known Problems
Table 2 Administrator Known Problems
Bug ID
|
Summary
|
Explanation
|
RME 4.0
|
|
|
None
|
Some of the RME processes are suspended.
|
If you start RME entering
make sure you do not suspend the session with the suspend command.
If you suspend the root session after manually starting RME, other processes, such as Daemon Manager, and ICServer, are also suspended.
Workaround:
Resume the suspended session.
|
Device Management Known Problems
Table 3 Device Management Known Problems
Bug ID
|
Summary
|
Explanation
|
RME 4.0.3
|
|
|
CSCsc47973
|
ACS integration with NDG gives devices access
|
This problem occurs when you use Resource Manager Essentials 4.0 SP2 (or later) and Cisco ACS 3.3.2 software (not the ACS appliance).
If you have the privilege to manage a particular Network Device Group (NDG) in Cisco Secure ACS, you are able to view the same NDG in RME, when RME is integrated with Cisco Secure ACS.
However, if you access the RME Devices option (RME > Devices > Device Management > RME Devices) then you are able to see all devices belonging to other NDGs. You can also add or edit devices from other NDGs.
If you select any option other than RME Devices, for example Normal Devices, you are able to view only those devices belonging to your NDG.
Workaround:
None.
|
CSCsc12079
|
GUI of Device Management State Summary is not updated
|
This problem occurs with Resource Manager Essentials 4.0 SP2 (or later).
The Device Management State Summary page (RME > Devices > Device Management) does not get updated, and displays incorrect information.
The information in the summary page remains incorrect. When you click on a device number, it does not match with number displayed on the device details dialog box.
Workaround:
None.
|
CSCsc17381
|
Device Center: Check Device Credentials do not return results.
|
In the Device Center, if you click Check Device Credentials under Management Tasks, it takes an unusually long time to return results.
In some cases, the results are not displayed and all the fields in the report state: No data yet.
Workaround:
None.
|
RME 4.0
|
|
|
CSCsa18790
|
Device moves from Pending to Normal to Conflicting state
|
During device import, devices may appear as Normal Devices for a very short span of time but later on move to Conflicting or Alias states after Conflict detection or Alias detection, respectively.
This may occur when you add a large number of duplicate or conflicting devices.
Workaround:
Wait for all devices to be processed for management. This may take some time depending on the number of devices added.
|
CSCsa22830
|
DLMS fails in SSL mode
|
This happens when you get or set credentials using DLMS in SSL mode.
Workaround:
SSL support for DLMS is not available in
RME 4.0 and therefore there is no workaround.
|
CSCed47422
|
Device Management State Summary show wrong record count.
|
A label on right top of Device Management State Summary screen shows, for example:
Showing 7 records
This problem occurs because of the default display provided by the underlying UI component (HTML Scrolling table).
Workaround:
This caption should be read as the number of records displayed on that screen — not the number of devices or the number of device states.
|
CSCsa36278
|
AUS should not be displayed in the Picker list while adding devices to RME.
|
Auto Update Servers (AUS) appear in the Add Devices screen.
This happens when you are adding new devices into RME, and PIX devices managed by Auto Update Servers are also a part of the list of devices to be managed in RME.
Workaround:
If Auto Management option is enabled, delete Auto Update Servers after they are added to the Normal Devices list.
If you select devices from the Add Devices screen filter out these Auto Update Servers.
|
CSCsa45574
|
Alias detection fails for some devices.
|
Alias detection does not work for devices that are accessed using a virtual management IP address.
This happens when you add devices with virtual management IP address.
Workaround:
Manually resolve aliases by deleting duplicate entries from the Normal Devices dialog box.
See the User Guide for Resource Manager Essentials for details.
|
CSCsa52951
|
Device Credential Verification does not run when device moves from conflicting to normal state
|
Device Credential Verification is not triggered when a device moves from Conflicting to Normal state.
This happens when the device type conflict is resolved and the device moves to Normal state.
Workaround:
Manually trigger Device Credential Verification for such devices.
|
Device/Agent Known Problems Impacting ANI Server and RME Functionality
Table 4 Device /Agent Known Problems Impacting ANI Server and RME Functionality
Bug ID
|
Summary
|
Explanation
|
RME 4.0
|
|
|
CSCdv62510
|
Config Fetch using TFTP fails for 800 series devices.
|
This happens on devices running IOS Release versions greater than 12.0.
Workaround:
Use Telnet to fetch or download files.
|
CSCdv64195
|
Unable to add Route Switch Modules (RSM) into RME when used memory reaches 4GB.
|
The problem occurs in the following scenarios:
•The datatype used is integer. In this case, Inventory cannot handle a value of 4GB in the database column.
•SNMP counter error. In this case, an error happens when used memory reaches 4GB, which happens when the device is up for a long time
The same error is reported in CSCdu09377.
Workaround
Reload the device to reset the SNMP counters.
|
CSCsa39153
|
Archive Management tasks fail for Catalyst 4507 device.
|
Archive Management tasks fail for Catalyst 4507 device, if you have selected TFTP as the transport protocol.
The happens because of incorrect implementation on the device.
Workaround:
Select a different transport protocol using Resource Manager Essentials > Admin >
Config Mgmt.
See Supported Device Table for Archive Management Application on Cisco.com for supported transport protocols information for the Archive Management application:
http://www.cisco.com/univercd/cc/td/doc/product/rtrmgmt/cw2000/cw2000e/
e_4_x/4_0_3/sdt/index.htm
|
CSCsa19145
|
SSH connection to the device fails because of SSH disconnection packet.
|
This problem occurs in a slow network when RME tries to contact device using SSH connection.
This happens because of incorrect implementation of SSH daemon (sshd) on the device.
Workaround:
None.
|
CSCsa44813
|
Archive Management tasks on startup configuration using TFTP does not work
|
Archive Management tasks on startup configuration using TFTP protocol does not work.
This happens because the device supports only OLD-CISCO-CONFIG-MIB for TFTP and this MIB does not support tasks on startup configuration.
Workaround:
Select a different transport protocol using Resource Manager Essentials > Admin >
Config Mgmt.
See Supported Device Table for Archive Management Application on Cisco.com for supported transport protocols information for the Archive Management application:
http://www.cisco.com/univercd/cc/td/doc/product/rtrmgmt/cw2000/cw2000e/
e_4_x/4_0_3/sdt/index.htm
|
CSCsa29075
|
The device boots with, but does not work on Image.ROM Version
|
ROMSysVersion is not returned by RME 4.0
This happens when the device is configured with SNMP.
Workaround:
None.
|
CSCsa40523
|
Chassis slot incorrect for MDS 9509
|
MDS device with software version 1.3(4a) renders incorrect values for its chassis number of slots.
This problem is identified in software version 1.3(4a).
Workaround:
Install software version 2.0(1).
|
CSCed88554
|
Supervisor software version value is 0
|
Device does not return Supervisor software version.
This happens when the device is configured with SNMP.
Workaround:
None.
|
CSCsa07154
|
Cannot query containment AG for Catalyst 5000 devices.
|
If the device happens to run with Cisco Catalyst Operating System Software, Version 4.5(13a), then it is likely that SNMP query fails for numSlots (SysObjectID > "1.3.6.1.4.1.9.5.1.3.1.1.25").
This happens when the device is configured with SNMP. The problem occurs because support in the Catalyst OS fails for this SysObjectID.
Workaround:
None.
|
CSCsa36845
|
Processor Port and Module Port section are missing from DDR for 4506 IOS
|
The device running IOS,Version 12.1(22)E2 fails for correlation between the port and the interface because ifIndex is rendered Null.
This happens when the device is configured for SNMP.
Workaround:
The problem does not occur with the IOS, Version 12.1(9a). Upgrade the device to this version.
|
CSCsa28210
|
cwcli export for CSS 11800 information is missing
|
Software Identity is missing in cwcli export, in the case of CSS 11800.
This happens when the CSS 11800 device has to be SNMP configured. The device does not return the processor component, while queried using SNMP.
Workaround:
None.
|
Inventory Known Problems
Table 5 Inventory Known Problems
Bug ID
|
Summary
|
Explanation
|
RME 4.0.3
|
|
|
CSCsc37630
|
System Inventory Collection and Polling jobs fail
|
The System Inventory Collection and Polling tasks do not scan any devices on the system.
RME flags the job as Successful, but does not scan any devices on the system.This happens when the CiscoWorks server is configured for Cisco Secure ACS.
Workaround:
None.
|
CSCsb28200
|
Grouping rules that are built using equality matches on :RME:INVENTORY:Device.System.SystemOID do not find matches.
|
This happens if the sysObjectID on which the match is performed does not begin with a leading dot.
All sysObjectIDs in RME are stored with a leading dot.
Workaround:
Either specify the leading dot in the match value, or change the operator from Equals to EndsWith or Contains.
|
CSCsc31440
|
RME detailed device report shows incorrect serial number for Cat2950
|
RME reports incorrect serial number information in detailed device reports for the Catalyst 2950 switches.
This is because RME polls chassisId in OLD-CISCO-CHASSIS-MIB.
However, the serial number information is available in entPhysicalSerialNum of the ENTITY-MIB which is what RME should use.
Workaround:
Hard code the chassis-id using the CLI on the 2950:
conf t
snmp-server chassis-id the-real-serial-number
where the-real-serial-number is the Serial Number.
|
CSCsb87660
|
Changing Inventory job schedule may cause duplicate jobs
|
Duplicate entries may appear for system RME inventory jobs, when you try to change the job schedule.
Workaround:
Use the job CLI to delete any unwanted jobs.
On Windows replace NMSROOT with the CiscoWorks install directory, for example, C:\Program Files\CSCOpx).
1. Navigate to NMSROOT\bin
2. At the command prompt enter:
cwjava -cw NMSROOT com.cisco.nm.cmf.jrm.jobcli delete unwanted_job_id
(where unwanted_job_id is the ID of the job you want to delete.)
3. Then restart the daemons using these commands:
|
RME 4.0 SP2
|
|
|
CSCsb40088
|
The Inventory > Hardware Report does not populate RAM, NVRAM, Used NVRAM fields for most CatOS switches RME 4.0.1
|
Inventory data is collected from StackMib. This does not have NVRamSize, RAM Size and Used NVRAM attributes.
These attributes need to be collected using EntityExtMIB or OCCM. However, the reports code is refers to EntityExtension MIB. Hence, these fields appear blank.
Workaround:
None
|
CSCsb50677
|
Device categorization of Router 1801 and 1802 appear incorrectly in Device Credentials Repository.
|
Cisco 1800 series Integrated Services Routers 1801 and 1802 are mapped under 1811 and 1812, respectively in Device and Credential Repository.
Workaround:
Patch will be posted on to Cisco.com.
|
RME 4.0 SP1
|
|
|
CSCsb00224
|
WS-SVC-NAM-1 is displayed as Generic class in Chassis Summary Graph
|
NAM-1 device chassis type WS-SVC-NAM-1 is classified as Generic in Chassis Summary Graph.
The containment collection for this device is not supported. Therefore, the vendor type is not available to the application to classify the device chassis type appropriately.
Workaround:
None.
|
CSCsa86823
|
A device in the normal state appears with ? icon and cannot be selected.
|
The Device Selector shows ? as the icon for a normal device for which configuration collection is successful.
Device and Credential Repository (DCR) did not have the device type information while the device was added.
Inventory collection failed because of SNMP time-out.
Workaround:
•Update the device type information in DCR.
•Make sure that the inventory collection succeeds (if required, increase the SNMP time-out value).
Note SNMP timeout exceptions can be seen in IC_server.log.
For details on editing device information in DCR, increasing SNMP time-out values, etc., see the User Guide for Resource Manager Essentials or the RME 4.0.3 Online help.
|
RME 4.0
|
|
|
None
|
Desktop machines appear incorrectly.
|
Do not import desktop machines unless they are running Cisco Call Manager applications. Otherwise, desktop machines appear incorrectly in the device selector under Call Managers.
Workaround:
None
|
None
|
IP addresses of cable modems ubr904 and ubr924 may change between reboots.
|
These devices get the IP address of the cable interface using DHCP from head-end cable router. The IP address might change between reboots.
Workaround:
You must import cable modems ubr904 and ubr924 using fully qualified pathnames.
|
None
|
Cannot manage PIX Firewall device without RME server IP address.
|
PIX Firewall device cannot be managed in RME without the IP address of the RME server.
Workaround:
1. Configure the PIX Firewall device so that it can be managed.
2. Enter the IP address of the RME server.
|
None
|
Check Device Attributes fails for devices that are already managed through the host name.
|
This happens when the IP address of the device host name is changed on the DNS server or on the local hosts file (/etc/hosts).
Workaround:
Restart the Daemon Manager.
|
CSCdk35153
|
Chassis modem table is not polled correctly.
|
Inventory reports show only configured modems. An interval exists between modem installation and modem configuration.
During this interval, the Inventory application might detect only one modem. Additionally, log messages might display database integrity violations.
These messages can be ignored.
Workaround:
1. Go to the device and configure the modem.
2. Reacquire the inventory data.
|
CSCdw68406
|
Inventory does not handle Cisco ONS Series (ONS 15540 ESP) devices with distinct configurations.
|
To perform redundancy operations Cisco ONS Series (ONS 15540 ESP) devices requires that both processors have the same configurations.
If they are:
•Configured with different set of credentials and a forced switch-over is made
And
•The read community string is different, Inventory will not manage the device
The device goes into the Not Responding state.
Workaround:
None
|
CSCdp61331
|
Comma included in password will cause device import to fail.
|
In comma separated value (CSV) format, the "," character is used as a delimiter. Therefore, fields in the CSV file should not contain the "," character.
If you use a "," character in the password or other fields while adding a device, the CSV file generated after exporting will be invalid.
An exported CSV file cannot be used for importing devices.
Workaround:
None
|
CSCdr81211
|
When a hitherto managed device is disconnected from the network, Scheduler does not report the status as Not Responding.
|
After a device has been managed using RME, it will not report the status as Unmanaged or Not Responding.
Workaround:
Manually delete the device from the inventory.
|
CSCds48244
|
Import operations fail for 7100 and 7200 routers because of an IOS bug.
|
Import operations may fail for Cisco 7100 and 7200 routers because of SNMP timeout.
Workaround:
1. Select Resource Manager Essentials > Administration > System Configuration
2. Increase Slow SNMP Timeout to a value more than 60 seconds.
|
CSCsa34114
|
Sysadmin privileges to generate reports is not restricted.
|
A user with Approval role, and a sysadmin user are not restricted from generating reports for inventory, Syslog, change audit etc.
Workaround:
None.
|
CSCsa36663
|
Location of archived reports cannot be changed.
|
All reporting application archives are stored at a predefined location and you are not given an option to change it.
After the disk is full with archived files, further jobs fail.
Workaround:
None.
|
CSCsa17340
|
Inventory Collection fails for Cisco Catalyst 2926 Device.
|
The device and the version of Catalyst Operating System (WS-C2926 and CatOS release 3.x) used by this device are no longer supported.
Owing to this, Inventory Collection fails for the device.
Workaround:
None.
|
CSCsa21492
|
Software Image information incomplete for Cisco Catalyst 4503 Switch.
|
The software Image information is incomplete for Cisco Catalyst 4503 switch.
This is because CW_MIN_DRAM, CW_MIN_NVRAM, and CW_MIN_BOOTFLASH are missing in the ciscoImageString for 4503 device.
Workaround:
None.
|
CSCsa33691
|
Image information missing for Cisco MGX 8220.
|
All the images information for Cisco MGX 8220 are not collected.
Workaround:
None.
|
CSCsa36025
|
Inventory Collection fails for Cisco 7010 Router.
|
RME 4.0 does not support Cisco 7010 Router and hence, inventory collection is not performed on the device.
Workaround:
None.
|
CSCsa41634
|
Inventory Collection fails for Cisco ONS 15530.
|
Inventory collection fails for the above device with the error message:
ASA Error - 195 column Physical ElementID
in table Physical AssetData cannot be NULL
Workaround:
None.
|
CSCsa29425
|
Poller returns incorrect values for Cisco 7609 router.
|
The poller returns incorrect values for Cisco 7609 router when the image version of the device is 12.2(17d)SXB1.
Workaround:
None.
|
CSCsa33704
|
In the Change Audit report, Inventory change details do not appear
|
After migrating from RME 3.4 to RME 4.0, when you click Inventory change details, no details appear.
Workaround:
None.
|
CSCsa36932
|
The Inventory Job Status page shows deleted device information.
|
When a device is deleted, the associated change records are deleted, but the device is still a part of the scheduled jobs.
Hence, the job browser shows the status of the job as:
However, when you click View Details, a message appears:
for a job that has already run. This is because the changes have already been deleted.
Workaround:
None.
|
CSCsa18445
|
Editing the Value field of custom report template using Netscape is difficult.
|
In the template creation dialog box for Inventory, when you select Group as UDF, attr as anything, Operator as anything, you will see that Value is set to All by default.
It is very difficult to type in anything that has the letter "A" because it automatically selects All.
Workaround:
Reselect the text you need to change and continue typing.
|
CSCsa27682
|
Custom group creation based on numeric attributes does not work for = operator.
|
This happens when the values are taken from reports which have more than two decimal values.
Workaround:
1. When real numbers comparison is required, use > or < as operators for creating custom groups instead of = operator.
2. You can round the value up to 2 decimal values and use the same for Custom group creation flow.
|
CSCsa32184
|
Inventory reports are affected by cross site scripting vulnerability.
|
If a user-defined field contains a string such as:
<html><body><p>hello</p><script>alert ("You
have found XSS bug")
</script></body></html>
instead of a plain text string, a malicious script is executed when you run an inventory report containing user-defined field.
Workaround:
None.
|
CSCsa33612
|
Report rendering does not handle special characters.
|
The report display format gets disturbed when a device attribute is configured with a malicious script (html or java) intentionally or unintentionally.
Workaround:
None.
|
CSCsa33994
|
Data extraction for Cisco Catalyst 4006 Switch has incomplete information.
|
Data extraction for Cisco Catalyst 4006 Switch running IOS has the following improper information:
•Software identity has no firmware information.
•There is no Cisco Flash device.
•There is no Cisco port under the Cisco card.
•There are no ports under the Cisco network element.
Workaround:
None.
|
CSCsa34243
|
Data extraction for Cisco Catalyst 4507 Switch has incomplete information.
|
Data extraction for Cisco Catalyst 4006 Switch running IOS has the following improper information:
•Software identity has no firmware information.
•There is no Cisco Flash device.
•There is no Cisco port under the Cisco card.
•There are no ports under the Cisco network element.
Workaround:
None.
|
CSCin15464
|
Card and Flash details are missing for older version Router 12000
|
Card and Flash Details do not get exported for 12000 series routers with older IOS versions.
Workaround:
For 12000 series routers, only newer IOS images that support CISCO-ENTITY-EXT-MIB will be supported.
For more details on the IOS images supported by the CISCO-ENTITY-EXT-MIB, go to the URL:
http://tools.cisco.com/ITDIT/MIBS/servlet/index.
|
CSCsa38526
|
RAM, NVRAM information duplicated for some multi-processor devices
|
In the Processor Information section of the Detailed Device Report, Processor details such as RAM and NVRAM information are duplicated for some multi-processor devices.
This happens when the multi-processor devices do not have support for CISCO-ENTITY-EXT-MIB.
Workaround:
None.
|
CSCsa14976
|
Flash information is not populated for 7304 device
|
If the IOS version running on the device is Version 12.1(9)EX2, EARLY DEPLOYMENT RELEASE SOFTWARE, it likely that the FlashAG collection fails at times.
Workaround:
Reboot the device.
|
CSCsa23146
|
Inventory does not collect the Flash information 6015 IPDSL device.
|
Device fails FlashAG collection when the device is configured for SNMP.
This happens because the device does not support Old-Cisco-Flash-Mib and Cisco-Flash-Mib.
Workaround:
None.
|
CSCsa16769
|
Incomplete rule accepted for custom template creation.
|
This problem occurs when you are creating a Custom Report Template using the Resource Manager Essentials > Reports > Custom Reports Templates, Create flow.
If the rule you are adding in the Custom Template Rules dialog box is the second rule or thereafter, even without entering any Operator and Value, you can create a rule.
If you:
1. Add only Association, Inventory Group, and Attribute,
2. Click Add, leaving the Operator and Value fields blank.
The rule is added to the template.
Workaround:
No workaround is required to generate the report, because you can see the operator in the Rules List.
Without any rule (operator and value), the rule will be considered as All (for string equals:ALL, for numeric attributes it is considered as =ALL).
1. If you want to modify the template, you can do it using the Edit flow from the Reports > Inventory Custom Templates dialog box:
1. Select the rule that you want to modify.
2. Enter the operator and value.
3. Click Modify.
4. Complete t |
