Table Of Contents
Release Notes for Resource Manager Essentials 4.0 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
Product Documentation
Additional Information Online
Caveats
Known and Resolved Problems of RME 4.0
Server, Browser, and Desktop Known Problems
Bug Toolkit Known Problems
Installation and Upgrade Known Problems
Administrator Known Problems
Device Management Known Problems
Device/Agent Known Problems Impacting ANI Server and RME Functionality
Change Audit Known Problems
Config Editor Known Problems
Archive Management Known Problems
NetConfig Known Problems
cwcli export Known Problems
Inventory Known Problems
Syslog Analyzer Known Problems
Software Management Known Problems
Common/Other Known Problems
Resolved Problems in Resource Manager Essentials 4.0
Known and Resolved Problems of RME 4.0 SP1
Known and Resolved Problems in RME 4.0 SP 2
Obtaining Documentation
Cisco.com
Ordering Documentation
Documentation Feedback
Obtaining Technical Assistance
Cisco Technical Support Website
Submitting a Service Request
Definitions of Service Request Severity
Obtaining Additional Publications and Information
Release Notes for Resource Manager Essentials 4.0 on Windows
These Release Notes are for use with the CiscoWorks family of products running on a Windows platform. Supported Windows versions are:
•
Windows 2000 Professional, Server, Advance Server with terminal services (in remote admin mode) or Server with Service Pack 3 and Service Pack 4.
•Windows 2003 Server and Enterprise Edition with terminal services (in remote admin mode).
For the details, see the Installation and Setup Guide for Resource Manager Essentials 4.0 on Windows.
These Release Notes provide:
•New Features
•Product Documentation
•Additional Information Online
•Caveats
•Known and Resolved Problems of RME 4.0
•Known and Resolved Problems of RME 4.0 SP1
•Known and Resolved Problems in RME 4.0 SP 2
•Obtaining Documentation
•Documentation Feedback
•Obtaining Technical Assistance
•Obtaining Additional Publications and Information
New Features
RME 4.0 contains these new features:
•New Features of Inventory
•New Features of Device Management
•New Features of Config Editor
•New Features of NetConfig
•New Features for Job Approval
•New Features of Reports
•New Features of Syslog
•New Features of Change Audit and Audit Trail
•New Features of Software Management
•New Features of Job Management
The Availability module of RME 3.5 is no longer available in RME 4.0.
New Features of Inventory
The Inventory application has the following new features:
•Integration with Device and Credentials Admin (DCA) database.
•All Inventory reports are now schedulable. You can run an immediate report or schedule a report to be run at a specified time.
•You can schedule Inventory Collection and Polling jobs.
•Periodic reports: You can schedule periodic jobs-6-hourly, 12-hourly, daily, weekly, or monthly.
•Export of reports as PDF or in CSV format.
•You can now export devices to a device list, from within a report.
•CLI feature is now available for all system reports (excluding graphs).
New Features of Device Management
The Device Management application has the following new features:
•Import devices from Common Services Device and Credential Repository.
You add devices to RME either manually or automatically. Before adding devices to RME you must add devices into Device and Credential Repository using Common Services > Device and Credentials > Device Management.
You add devices in two ways:
–Adding Devices to RME Manually
–Adding Devices to RME Automatically
By default, the Automatically Manage Devices from Credential Repository option in the Device Management Settings window is enabled.
•Device State Management based on device reach ability.
The device participation in RME application tasks 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 immediate, once or periodic. 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.
•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.
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.
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.
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.
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-7816505=)—Provides installation instructions, including both server and client system requirements, steps for installing and uninstalling, and installation troubleshooting information.
•User Guide for Resource Manager Essentials (DOC-7816503=)—Provides information on using RME 4.0.
•User Guide for Common Services 3.0 (DOC-7816571=)—Provides information about setting up, administering, and accessing CiscoWorks Common Services.
•Resource Manager Essentials Online help—Provides task-oriented and context-sensitive help from every window that contains a Help button.
Also contains all of the information available in User Guide for Resource Manager Essentials. This ensures you have complete information even if you do not have the manual readily available while using RME.
For more details on the new features in RME 4.0, and the procedures mentioned in this document, see the User Guide for Resource Manager Essentials.
Additional Information Online
For information about RME supported devices, refer to the following URL:
http://www.cisco.com/univercd/cc/td/doc/product/rtrmgmt/cw2000/cw2000e/
dev_sup/index.htm
Tip For the latest technical tips, suggestions for troubleshooting common issues, and frequently asked questions (FAQs) on most RME applications, you can:
Login to Cisco.com and select Products and Services > Network Management > CiscoWorks LAN Management Solution > CiscoWorks Resource Manager Essentials > Product Literature.
The Incremental Device Update (IDU) for RME 4.0 is a collection of updated files necessary for RME to support new Cisco devices. In addition to the devices supported, this package also contains fixes to known problems, as well as additional newly discovered problems.
If you are a registered user, you can download the latest version of IDU for RME 4.0 from:
http://www.cisco.com/pcgi-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 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 and Resolved Problems of RME 4.0
This section contains the following known problems for RME 4.0:
•Server, Browser, and Desktop Known Problems
•Bug Toolkit Known Problems
•Installation and Upgrade Known Problems
•Administrator Known Problems
•Device/Agent Known Problems Impacting ANI Server and RME Functionality
•Device Management Known Problems
•Change Audit Known Problems
•Config Editor Known Problems
•Archive Management Known Problems
•NetConfig Known Problems
•cwcli export Known Problems
•Inventory Known Problems
•Syslog Analyzer Known Problems
•Software Management Known Problems
•Common/Other Known Problems
•Resolved Problems in Resource Manager Essentials 4.0
Server, Browser, and Desktop Known Problems
Table 1 Server, Browser, and Desktop Known Problems
Bug ID
|
Summary
|
Explanation
|
None
|
Problems while printing from a browser.
|
Printing from a browser does not work reliably.
Workaround:
To print an RME window, use the Print Screen or the Capture Screen function on your machine.
|
CSCin03389
|
Adhoc template displays Failed for some catalyst devices.
|
A successful job will be displayed as Unsuccessful.
Workaround:
Disable debug in the device and run the job.
|
CSCdp08278
|
Tasks might fail if server is not 100% up.
|
If you try to access CiscoWorks before the server is running fully, Login Manager will not appear.
Workaround:
•For Netscape, click Reload.
•For Internet Explorer, click Refresh.
|
CSCdp08278
(Continued)
|
Tasks might fail if server is not 100% up.
(Continued)
|
At the beginning of CiscoWorks session, if you select a task from the navigation tree before the server is fully operational, the task might fail.
Workaround:
Select the task again. If this does not help, restart the system using one of these methods:
•Using the GUI:
a. Select Server Configuration > Administration > Process Management > Stop Process.
b. Select the System radio button and click Finish.
c. Select Server Configuration > Administration > Process Management > Start Process.
d. Select the System radio button and click Finish.
From command line interface, enter:
On Windows:
net stop crmdmgtd
net start crmdmgtd
•Make sure all process are running before relaunching tasks.
Select Server Configuration >
Administration > Process Status. The State column shows whether processes are running.
|
CSCds16984
|
Cannot launch RME from Netscape or Internet Explorer.
|
This may happen because the JRun Proxy Server process is not running.
Workaround:
Restart the RME server.
|
CSCsa57408
|
JOS: Upgrading from RME 3.5 to RME 4.0 takes over 3 hours.
|
Single server upgrade, that is, RME 3.4 or 3.5 to RME 4.0, in Japanese Windows environment takes over 3 hours.
Workaround:
None.
|
Bug Toolkit Known Problems
Table 2 Bug Toolkit Known Problems
Bug ID
|
Summary
|
Explanation
|
CSCsa89297
|
Setting a proxy may break other applications
|
Applications such as Campus Manager and Device Center may not work properly. Device Center may show a blank screen, and Campus Manager applications may report that they cannot connect to ANIServer.
This can happen if a proxy server is configured within CiscoWorks.
Workaround:
Remove the proxy configuration, and restart the CiscoWorks Daemon Manager.
|
CSCsa24273
|
Bug Toolkit displays different bug count when logging into Cisco.com with different login IDs.
|
Data returned from the Bug Toolkit is based on the different security levels that the login IDs belong to.
Workaround:
None.
|
CSCsa18424
|
The number of bugs shown in the Bug Summary Report and the Bug Details page, do not match.
|
When you schedule a job and check the bug summary report, you get the count for the number of bugs. For the same job, if you check the Bug Details page, you might see more bugs shown, resulting in a discrepancy.
This is because the Bug Summary Report is based on the archived data, whereas the data for the Bug Details page in the latest information, drawn from Cisco.com.
Workaround:
Run the Bug Summary Report again with the same job criteria, but with the Run Type as Immediate.
|
CSCsa24273
|
Browse Bugs gives different bug counts for different Cisco.com logins
|
Bug Toolkit displays varying bug count while logging in to Cisco.com with different login ids.
Data returned from the Bug Toolkit is based on the different security levels of the login IDs, when you use different login IDs to generate the report.
Workaround:
None.
|
CSCsa24369
|
Browse Bugs—Schedule time shows an old date in
Netscape 7.1
|
Invoke the Browse Bugs/Locate Devices report.
A popup appears prompting you to select a username.
If you click OK or Cancel, the current dialog box is retained.
This behaviour is not seen in IE 6.x.
Workaround:
In Netscape there is an option for storing or "remembering" the password. This problem occurs only if you choose the Remember Password option. Therefore do not select the Remember password option of Netscape.
Also, if the popup appears, you can click Cancel and continue to schedule the jobs.
|
CSCsa47066
|
For some bugs, the Locate Devices flow does not display correct devices
|
For some bugs, the Locate Device flow does not display the correct devices that are affected.
This problem can occur at any time.
Workaround:
None.
|
Installation and Upgrade Known Problems
Table 3 Installation and Upgrade Known Problems
Bug ID
|
Summary
|
Explanation
|
CSCsa75824
|
RME Sybase Engine will not start with 4 GB memory on Windows 2003.
|
This problem can happen on a Windows machines with 2 GB RAM or more.
RME features do not work because CiscoWorks Sybase fails to start.
Workaround:
To resolve this issue, you should edit the Windows registry for RMEDbEngine services.
1. Select Start > Run.
2. Enter regedit.
3. Go to HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Services\RMEDbEngine.
4. Select Parameters.
5. Change Parameters Value Data from -ch 50P to -ch 1G (where P is the percentage of total physical RAM in the machine, and G is Gigabyte).
6. Update the *tmpl files at NMSROOT/databases/rmeng/orig directory odbc.tmpl and odbc.tmplorig files by changing the value -ch 50P to -ch 1G.
7. Reboot the CiscoWorks server.
The maximum cache size of the CiscoWorks server should not be more than 1 GB. If it is more than 1 GB you must adjust the -ch parameter value for RMEDbEngine services.
On all machines with physical RAM greater than 2 GB, it is recommended that the maximum cache size is
1 GB. Change the Parameter Value Data to -ch 1G. This hardcodes the cache size to 1 GB.
|
|
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).
|
None
|
ATM image version and image family may be incorrect after upgrade.
|
After upgrading to RME 3.5, the ATM image version and image family may be incorrect.
Workaround:
1. Delete the ATM images.
2. Reimport the ATM images from the software image library.
|
CSCsa33360
|
Device groups migrated for users (Approvers and Network Operators) cannot be edited by users with the same roles in RME 4.0
|
Users with Approver and Network Operator roles cannot edit or delete device groups in RME 4.0 that were created in RME 3.x by users with the same roles.
This happens when the device groups created in RME 3.x by users with Approver and Network Operator roles, are migrated to RME 4.0.
Workaround:
None.
|
CSCsa33365
|
Network Administrator cannot edit or delete device groups in RME 4.0 that they created in RME 3.x, after migration.
|
After migration from RME 3.x to RME 4.0, a user with a Network Administrator role cannot edit/delete groups in RME 4.0 that the user created in RME 3.x.
This happens when the device groups created in RME 3.x by a user with a Network Administrator role, are migrated to RME 4.0.
Workaround:
None.
|
CSCsa41910
|
LMS 2.5—Migration fails as DCRServer is not started.
|
RME Migration fails stating DCRServer could not be started in migration.log
This might happen rarely and can be seen in the migration.log.
Workaround:
Run this command before executing migration:
/opt/CSCOpx/bin/perl /opt/CSCOpx/bin/dbRestoreOrig.pl dsn=cmf dmprefix=Cmf opt=Y
|
CSCsa34359
|
Change Audit details are not available for some of the NetConfig records after data migration from RME 3.x to
RME 4.0.
|
The change details cannot be identified for some of the NetConfig records.
This is because you have purged configuration files in the RME 3.x server where the backup was taken for migration.
These purged configuration files are not available in RME 4.0 server after data migration. An error appears, Internal Error: Config File information not available.
Workaround:
None.
|
CSCsa45325
|
No able to upgrade from
RME 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 4 Administrator Known Problems
Bug ID
|
Summary
|
Explanation
|
None
|
Some of the RME processes are suspended.
|
If you start RME by logging in as root and entering /etc/init.d/dmgtd start, make sure you do not suspend the session with the suspend command.
If you suspend the root session after manually starting RME, other processes, such as Daemon Manager, and IcServer, are also suspended.
Workaround:
Resume the suspended session.
|
Device Management Known Problems
Table 5 Device Management Known Problems
Bug ID
|
Summary
|
Explanation
|
CSCsa18790
|
Device moves from Pending to Normal to Conflicting state
|
During device import, devices may appear as Normal Devices for a very short span of time but later on move to Conflicting or Alias states after Conflict detection or Alias detection, respectively.
This may occur when you add a large number of duplicate or conflicting devices.
Workaround:
Wait for all devices to be processed for management. This may take some time depending on the number of devices added.
|
CSCsa22830
|
DLMS fails in SSL mode
|
This happens when you get or set credentials using DLMS in SSL mode.
Workaround:
SSL support for DLMS is not available in
RME 4.0 and therefore there is no workaround.
|
CSCed47422
|
Device Management State Summary show wrong record count.
|
A label on right top of Device Management State Summary screen shows, for example:
Showing 7 records
This problem occurs because of the default display provided by the underlying UI component (HTML Scrolling table).
Workaround:
This caption should be read as the number of records displayed on that screen — not the number of devices or the number of device states.
|
CSCsa36278
|
AUS should not be displayed in the Picker list while adding devices to RME.
|
Auto Update Servers (AUS) appear in the Add Devices screen.
This happens when you are adding new devices into RME, and PIX devices managed by Auto Update Servers are also a part of the list of devices to be managed in RME.
Workaround:
If Auto Management option is enabled, delete Auto Update Servers after they are added to the Normal Devices list.
If you select devices from the Add Devices screen filter out these Auto Update Servers.
|
CSCsa45574
|
Alias detection fails for some devices.
|
Alias detection does not work for devices that are accessed using a virtual management IP address.
This happens when you add devices with virtual management IP address.
Workaround:
Manually resolve aliases by deleting duplicate entries from the Normal Devices dialog box.
See the User Guide for Resource Manager Essentials for details.
|
CSCsa52951
|
DCV does not run when device moves from conflicting to normal state
|
Device Credential Verification is not triggered when a device moves from Conflicting to Normal state.
This happens when the device type conflict is resolved and the device moves to Normal state.
Workaround:
Manually trigger Device Credential Verification for such devices.
|
Device/Agent Known Problems Impacting ANI Server and RME Functionality
Table 6 Device /Agent Known Problems Impacting ANI Server and RME Functionality
Bug ID
|
Summary
|
Explanation
|
CSCdv78969
|
MSFC2 module in Cat6509 returns zero-length sysConfigName value.
|
The MSFC2 module in Cat6509 returns zero-length sysConfigName value.
Workaround:
None.
|
CSCdv62510
|
Config Fetch using TFTP fails for 800 series devices.
|
This happens on devices running IOS Release versions greater than 12.0.
Workaround:
Use Telnet to fetch or download files.
|
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/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/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
This happens when the device has to be SNMP configured. The device does not return the processor component, while queried using SNMP.
Workaround:
None.
|
Change Audit Known Problems
Table 7 Change Audit Known Problems
Bug ID
|
Summary
|
Explanation
|
CSCsa22116
|
Error when saving the reports in PDF format with default file names. The message The disk you were saving to or the disk used for temporary files is full.Free some space on the disk and try gain or save to a different disk appears.
|
This error is displayed by Windows when files names exceeding 254 characters are used.
Workaround:
Select Save As and enter a new file name which has less than 254 characters.
|
CSCsa33492
|
Change Audit report does not export the grouped records.
|
Only records shown in the report are exported. Other grouped records that are visible when you click More Records, are not exported.
Workaround:
None.
|
Config Editor Known Problems
Table 8 Config Editor Known Problems
Bug ID
|
Summary
|
Explanation
|
CSCsa14126
|
Older device credential shown in clear text
|
This happens for all device credentials when you:
1. Open a configuration file for editing using Config Editor application.
In the Credentials pane (Config Editor dialog box), the masked credentials appear. These credentials are hyperlinked.
2. Click on hyperlinked credentials.
The Modify Credentials dialog box appears.
The old device credential is shown in clear text in the Old Credential text field.
Workaround:
None.
|
CSCsa36347
|
SNMP Authentication/privacy passwords not masked in device response
|
SNMP security password and Privacy passwords appear in an argument list in the Device Details page.
This happens when Debug is enabled in the device.
Workaround:
Disable Debug on the device.
|
CSCsa30243
|
Commands not in proper configlet
|
This happens when you:
1. Create a baseline template in the Advanced mode (Resource Manager Essentials > Config Mgmt > Archive Mgmt >
Baseline Templates > Create).
2. Open the baseline template using Config Editor.
3. Edit and save the baseline template in the Public location.
4. Open the saved baseline config from the Public location in the Processed mode.
Some of the commands are shown in incorrect configlets.
Workaround:
To edit Baseline Template in commandlet format use Resource Manager Essentials > Config
Mgmt > Archive Mgmt > Baseline Templates > Edit.
|
CSCsa39790
|
Config Editor updates the Device and Credential Repository with an encrypted string.
|
If service password-encryption is enabled on the device then credential would be encrypted in show config output of the device.
The Device and Credential Repository is updated with this encrypted password, if you:
1. Create a Config Editor job in merge mode using Telnet as the transport protocol.
2. Deploy this command using the Config Editor application.
Workaround:
Use the NetConfig application to update the encrypted credential command.
|
CSCsa55592
|
NAM: SNMP Traps community string shown in clear text
|
If you use Network Analysis Module (NAM) commands, the SNMP trap community strings will not be masked.
Workaround:
None.
|
CSCsa55916
|
Enable username not needed in Config Editor jobs
|
Job creation flow in Config Editor has a field to accept enable username for Job Based Password (JBP). This is found in Config Editor job creation flow when JBP is enabled.
Workaround:
While entering value for JBP do not give a value in the Enable User Name field.
This problem does not have any effect.
|
Archive Management Known Problems
Table 9 Archive Management Known Problems
Bug ID
|
Summary
|
Explanation
|
None
|
TACACS with SecureID not supported.
|
RME configuration archive does not support TACACS with SecureID. It supports static passwords that are defined when you add or import devices into the RME inventory.
Workaround:
None
|
None
|
Banner commands containing (") and (^C) characters cause configuration applications to function incorrectly.
|
If banner values are contained between quotation marks (") in Config Archive and between Ctrl-C (^C) characters in a device, the configuration applications do not function correctly.
Workaround:
Do not add Ctrl-C characters to the banner commands while downloading them to the device.
|
None
|
Module configuration is not retrieved even if the module has valid credentials for a CAT switch.
|
Configurations of IP addressable modules are not retrieved along with Supervisor even if the module has same credentials as the Catalyst switch.
IP addressable modules should be managed as a separate device.
Configurations of non-IP addressable modules are fetched along with Supervisor configuration only if the selected protocols are Telnet or SSH, provided the module has same credentials with Supervisor. Other protocols are not supported.
Workaround:
None.
|
CSCds68827
|
Syslog messages archived in the Configuration archive
|
Telnet retrieves all the information that is displayed in the telnet session when you try to fetch configuration using Telnet.
If logging is enabled for sessions, Syslog messages displayed on the Telnet session are also archived along with the configuration.
Workaround:
Turn off the display of Syslog messages on the Telnet session before fetching configurations using Telnet.
|
CSCdt24115
|
Catalyst 5000 Devices: Transport FallBack from TFTP to Telnet Fails.
|
Catalyst 5000 device displays:
Device is busy with previous operation, Try
later'
when you perform a Config Fetch operation.
The device going into busy state is a feature of the Catalyst 5000 switches.
This is to prevent too many TFTP/Telnet connections within short intervals of time.
Workaround:
Change Transport Order to specify Telnet as the first protocol.
|
CSCsa44963
|
Archival fails in Cisco Content Services Switch 11050.
|
Configuration archival fails in the Quick Configuration deployment job in the Merge mode for Cisco Content Services Switch 11050.
Workaround:
None.
|
CSCsa16259
|
Configuration download fails for Cisco 3660 Router.
|
Configuration download fails for Cisco 3660 Router with the message:
Transport session to device failed
This failure happens in the Merge mode although the device credentials are correct.
Workaround:
None.
|
CSCsa35538
|
Configuration archival fails for VPN devices.
|
On Windows, the configuration fetch operation for VPN 3000 devices, fails.
This happens when there are characters such as '<,''>' in the configuration file. For XML parsers these characters are the delimiters.
Workaround:
Remove these characters from the configuration file.
|
CSCsa38392
|
Archive Mgmt scheduled jobs retain old display names.
|
The Archive Management Job Details page sometimes shows old names of managed devices.
This happens when the display name of the device changes after the job execution begins.
In the case of periodic jobs, if the device name changes after the job is created, all instances of the job continue to show the old name.
Workaround:
Recreate the job.
|
CSCsa36000
|
Device link for Partially Successful devices is not Enabled
|
Status links in the Job Details page are either disabled or they do not invoke the Details page.
This happens when you:
1. Click the Job ID and the Job Details page is launched.
Partially Successful Devices, Failed devices, Successful devices appear
2. Click the status links in the Partially Successful devices,
No page appears.
Workaround:
1. Click on any one of the status links under Failed or Successful devices
2. Click the partially successful devices again.
The Details page appears.
|
CSCsa17778
|
Configuration archival fails in a mounted file system.
|
Archival of configurations does not occur on the mounted/mapped drives on Windows.
This happens when the default archive location is changed to the mapped network drive on Windows.
Workaround:
Restore it to the default location or change to another location on the local hard disk.
|
CSCsa35699
|
VPN configs coloring scheme is incorrect for Compare Configs.
|
In the Config Diff Viewer, the diffs of modified commands are shown in blue instead of red.
For VPN 3000 devices, the diff viewer shows the modified commands in blue font instead of red, as in other devices.
Workaround:
None.
|
CSCsa37473
|
Issue in Config for device CSS 11050
|
Archived configuration does not contain the complete running configuration.
This occurs happens when the image on the device is Content Switch SW Version 5.02 Build 3 with SNMPv1/v2c Agent.
This happens when configuration fetch is tried with both Telnet and TFTP protocols.
Workaround:
None.
|
CSCsa51073
|
Compare config report with Raw mode shows incorrect data for ACLs.
|
In the Raw mode, the order of commands in the config compare reports may not be the same as in the archived file.
While trying to compare configurations, if you have same commands appearing under different sections in two versions, the order can be different in the Raw mode, with the All option
Workaround:
Ignore the error in the Raw mode diff and use the Processed mode, which is more refined, to view such changes. There is no change in the order in the archived file—this is only an issue in the user interface.
|
CSCsa55997
|
Sync Archive Fails for few NAM devices
|
Sync archive of NAM devices fails.
If the previous deploy job failed with a timeout exception, subsequent sync archive jobs for that NAM device will fail.
Workaround:
Either:
•Stop and restart the ConfigMgmtServer service at Common services > Server > Admin > Processes.
Make sure that no other jobs are running. If they are running, perform this task operation after the jobs complete.
Or
•For the specific device, fetch the startup or running configuration using the Startup or Running hyperlinks respectively at Resource Manager Essentials > Config Mgmt > Archive Mgmt > Version Summary.
|
CSCsa45567
|
DM, Inventory and ConfigArchive applications are out-of-sync with reference to the number of devices managed
|
The number of devices shown in Archive Status screen of Archive Management may be more than the number of devices managed in RME.
This can happen when the devices are deleted while config collection is in progress.
Workaround:
None.
|
CSCsa56349
|
Baseline compare need not be case sensitive.
|
Baseline Compliance flags a configuration as non-compliant although the command is present in the configuration.
This may occur when there is difference in case between the commands in the template and the commands in the configuration file of the device. IOS is case insensitive and hence you may have entered the commands in the template under this assumption.
Workaround:
Ensure that you use the same case in the commands in the template and the configuration on the device.
|
CSCSa57860
|
Compare and deploy job—Problem in Job Password.
|
Deploying commands does not work on the non-compliant devices.
This occurs:
•While scheduling a Compliance job, in the Job Scheduling screen,
•When the Compare and Deploy option is checked, and
•When the Job Based Password is enabled.
The Deploy operation fails, although you have entered the correct passwords.
Workaround:
While using Job Based Password for deploy operation, schedule Compliance first and then perform Deploy, later on the non-complaint devices.
That is, schedule them as two separate jobs.
|
CSCSa58267
|
RME Job fails if local user privilege 0.
|
Configuration operations on the device fail if privilege level set is 0 for local users.
This happens when RME uses the show privilege command to identify the privilege level. This command does not run if the privilege level is set to 0.
Workaround:
Specify the privilege level as 1 or above for the local user.
|
NetConfig Known Problems
Table 10 NetConfig Known Problems
Bug ID
|
Summary
|
Explanation
|
CSCsa15482
|
Network Time Protocol template does not generate proper rollback commands.
|
When the download command fails on a device, the successfully downloaded commands are rolled back, if the Rollback policy is on.
If the command ntp authentication-key is already present in the device and if you attempt a rollback of the command, it fails.
Workaround:
None.
|
CSCsa16093
|
Trap notifications fail for certain image features.
|
For Cisco IOS devices, if you select certain trap notifications types for the snmp-server host command in the traps template, it might lead to command download failure.
Workaround:
None.
|
CSCsa19184
|
Rollback for the SSH key bit configuration command does not restore the original number of key bits.
|
This happens when you have enabled SSH on a device with a certain number of key bits and then enable or disable the key bits through an SSH template download.
The download of commands other than the key bits command, fails.
Workaround:
None.
|
CSCsa22697
|
Rollback for the ntp server command does not restore the original command on the device.
|
This happens when you have an ntp server command on the device with the key option enabled.
If you change the command on the device through an NTP template download, the download of all other command fails.
Workaround:
None.
|
CSCsa24300
|
Authentication method of non-ip addressable sub-modules is not updated.
|
When you update the authentication method for the Supervisor module using the tacacs+ template, it does not update the authentication method.
It also does not update the passwords of the non-ip addressable sub-modules.
Workaround:
1. Add a Telnet or Enable password template and apply commands with the same password to the modules.
2. Add a tacacs+ template to update the authentication method for the Supervisor module. Use the same password as above for this template.
|
CSCsa25755
|
Rollback of a job changes the password on the device.
|
This happens when you rollback a job containing two credential templates. When you change the Enable password, it might change the password on the device.
For example, Radius and enable or Tacacs+ and enable.
Workaround:
Do not have two different templates changing the Enable password credentials in the same job.
|
CSCsa27946
|
CSS: NTP: Server IP address alone allowed. Download fails for hostname
|
While configuring SNTP server, the IP Address of the SNTP server has to be specified. Instead of the IP Address, if SNTP server hostname is specified, the template fails.
This is applicable for all versions from 5.0 onwards.
Workaround:
Specify the IP Address of SNTP server instead of the SNTP server hostname.
|
CSCsa42117
|
Config jobs scheduled to run after RME evaluation license expiry period.
|
This happens when all Configuration jobs fail to run after the license expire.
However, the reason for Job Execution failure is not captured in Archive Management application Job Browser and Job Details windows.
Workaround:
After the license expires, view the Job Status message using Common Services > Server > Admin > Job Browser.
</ |
