Guest

CiscoWorks Resource Manager Essentials

Release Notes for Resource Manager Essentials 4.0.5 on Solaris

  • Viewing Options

  • PDF (603.7 KB)
  • Feedback
Release Notes for Resource Manager Essentials 4.0.5 on Solaris

Table Of Contents

Release Notes for Resource Manager Essentials 4.0.5 on Solaris

New Features

New Device Support

Product Documentation

Additional Information Online

Caveats

Known Problems in RME 4.0.5

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, UI, and Desktop Known Problems

Common/Other Known Problems

Resolved Problems in RME 4.0.5

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

Open Source License Acknowledgements

OpenSSL/Open SSL Project

License Issues


Release Notes for Resource Manager Essentials 4.0.5 on Solaris


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 Solaris versions, see the Installation and Setup Guide for Resource Manager Essentials 4.0.5 on Solaris.

These Release Notes provide:

New Features

Product Documentation

Additional Information Online

Caveats

Known Problems in RME 4.0.5

Resolved Problems in RME 4.0.5

Obtaining Documentation

Documentation Feedback

Obtaining Technical Assistance

Obtaining Additional Publications and Information

Open Source License Acknowledgements

New Features

This section discusses the new features in RME 4.0.5.

Check Device Attributes: This is now a schedulable job in RME. You can select the credentials that you want to verify, and trigger a job for these credentials. You can access this through the RME Job Browser.

Device Selector: Simple and Advanced Search capabilities are provided in the Enhanced Device Selector.

Functional Homepage: RME now has a new functional homepage from where you can access all reports, carry out frequently used tasks, view status of jobs. You can also view any alert messages.

Performance Tuning Tool (PTT): You can tune system parameters using PTT to improve RME performance.

Reports: Reports have been enhanced to allow group-based selection of devices to generate reports.

Unique Device Identifier UDI: The Detailed Device Report displays Unique Device Identifier as one of the columns for the components available for a particular device.

Each component of a device is identified with a UDI and it is unique. A Unique Device Identifier is a combination of Product ID (PID), Version ID (VID) and Serial Number (SN).

LMS Setup Center: This is a one-stop place that allows you to set basic configuration for the applications.

For more details, see the User Guide for Resource Manager Essentials.

New Device Support

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

http://www.cisco.com/en/US/products/sw/cscowork/ps2073/products_device_support_tables_list.html

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 LMS 2.6 Documentation CD:

Installation and Setup Guide for Resource Manager Essentials on Solaris

User Guide for Resource Manager Essentials


Note Adobe Acrobat Reader 4.0 or later is required.


Use these documents to learn how to install and use Resource Manager Essentials:

Installation and Set Up Guide for Resource Manager Essentials on Solaris — 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 — Provides information on using RME 4.0.5.

User Guide for Common Services — Provides information about setting up, administering, and accessing CiscoWorks Common Services 3.0.5

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.5, 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/en/US/products/sw/cscowork/ps2073/products_device_support_tables_list.html


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.5 is a collection of updated files necessary for RME to support new Cisco devices. In addition to the devices supported, this package also contains fixes to known problems, as well as additional newly discovered problems.

If you are a registered user, you can download the latest version of IDU for RME 4.0.5 from:

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

Caveats

The following are some caveats:

Before installing RME, ensure that you do not have CWSI Campus 2.x or Cisco Voice Manager on the system.

Before upgrading RME, ensure that all applications are stopped. The upgrade depends on having reasonable interaction time with the database. If this is not possible, the upgrade fails.

Browsers running on remote X servers are not supported in RME.

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

This section contains the following known problems for RME 4.0.5.

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, UI, 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 Select the Software sub-section and click Bug Toolkit.


Alternatively, go to: http://www.cisco.com/cgi-bin/Support/Bugtool/home.pl

You will be prompted to log into Cisco.com.

Installation and Upgrade Known Problems

Table 1 Installation and Upgrade Known Problems 

Bug ID
Summary
Explanation

CSCsc46237

Restore fails even when adequate space is available

RME restore operation fails with 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, then the insufficient disk space error appears.

Workaround:

Either increase the partition space or copy the backup to a different partition with enough space.

CSCsc45054

Restoring LMS 2.2 backup on LMS 2.5 fails

Restoring a backup from LMS 2.2 to Solaris server LMS 2.5 SP2 fails.

This occurs when you are running CiscoWorks on Solaris 2.8 and/or 2.9 and the LMS 2.5 (SP2) package is installed.

Workaround:

None.

CSCsa93329

Daemon manger dumps core when configjob/DCMA displays OutOfMemory exception

The daemon manager sometimes dumps core but no processes go down.

This sometimes occurs during a Quick Config Deploy operation from Config Management.

Workaround:

1. Stop the daemon manager.

2. Increase the swap space of the system.

3. Restart the daemon manager.

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.

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

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 3 Device Management Known Problems 

Bug ID
Summary
Explanation
RME 4.0.3
   

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.

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

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.

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/en/US/products/sw/cscowork/ps2073/products_device_support_tables_list.html

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 do not work

Archive Management tasks on startup configuration using TFTP protocol do 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/en/US/products/sw/cscowork/ps2073/products_device_support_tables_list.html

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 has to be SNMP configured.

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), 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 has to be SNMP configured. 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 2.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

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.

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

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.

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 SP1 Online help.

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. Re-acquire 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 causes 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.

CSCdv64195

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

The problem occurs in the following scenarios:

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

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

The same error is reported in CSCdu09377.

Workaround:

Reload the device to reset the SNMP counters.

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.

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:

Successful: With Changes

However, when you click View Details, a message appears:

No changes

for a job that has already run. This is because the changes have already been deleted.

Workaround:

None.

CSCsa19271

Year drop down appears at the left hand corner of the screen

While scheduling an Inventory job, if you click on the date selector to select a year, the listing of years appears in the left hand corner of the screen.

This happens with Netscape browser on Solaris.

Workaround:

Use Mozilla 1.6 instead of using Netscape.

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.

CSCsa15342

NS 7.1—Hardware Report: Save in CSV format saves as export.csv.do in Solaris.

When you try to save the Hardware Report in the CSV format, although RME sends the default name export.csv, the Netscape client adds the .do extension.

Workaround.

Edit the name and give.xls or .csv as the extension for the file.

CSCsa16772

Cannot create a Private Custom Template with the same name for different users.

If a template with the name ABC, is created by user X, with any access type, then user Y cannot create a template with the same name ABC.

However, user Y cannot see the template named ABC, which user X has created with private access. This may confuse user Y.

Workaround:

Use the following CLI command to view all template names (Private and Public access):

cwcli invreport -u username -p password -listreports.

This will display all the templates defined in the system. Also, avoid template names that are already in use.

CSCsa22899

Device Credential Verification reports no value to test for Enable when Telnet password is blank

If you do not enter the Telnet Username and Password and only enter the Enable Password, Device Credential Verification reports DID NOT TRY for its the Enable Password check.

The condition under which this problem occurs is that both Telnet Username and Password are not provided in Device and Credential Repository.

Workaround:

None.

CSCse26973

NVRAM and Total RAM information missing in Hardware Report for IGESM device.

The IGESM device does not consist of NVRAM and Total RAM details. So when you generate a Hardware report for this device, the NVRAM and Total RAM details do not appear in the report.

Workaround:

None.


Archive Management Known Problems

Table 6 Archive Management Known Problems 

Bug ID
Summary
Explanation

CSCsb23687

TFTP Fetch/Download failed for new MIB in Cisco Content Services Switch.

You cannot fetch or download the configuration using TFTP protocol

This problem will occur when users select the TFTP protocol alone for the Fetch and Download operations.

Workaround:

Use Telnet or SSH protocol for fetch and download operations.

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.

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 appears 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 a 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.

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 text 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 problem occurs 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.

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.


NetConfig Known Problems

Table 7 NetConfig Known Problems 

Bug ID
Summary
Explanation

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.

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.

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 commands fail.

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

CSCsa44983

The commands fails only for Content engine devices running ACNS 5.2 or later versions.

This happens when the commands deployed using Syslog task on Content Engine devices fails for logging priority configuration.

Workaround:

Do not configure logging priority using Syslog system defined task on Content Engine devices running ACNS version 5.2 or later.

1. Create a user-defined task for configuring logging priority with commands specific to ACNS 5.2 or later

2. Use that for deploying on Content Engine devices running ACNS 5.2 or later.

CSCsa44626

IOS-enable TACACS fails when aaa new-model is enabled.

Download of TACACS commands such as login tacacs, tacacs server etc., fail.

This occurs when the command, aaa new model is present on the device.

Workaround:

Disable the aaa new model command. To do this use either the TACACS+ or RADIUS template before adding the TACACS template commands.

CSCsa23231

Job Creation wizard loses context when multiple templates are opened.

This problem occurs while creating a NetConfig job, in the second step of the wizard (Add Tasks).

If you open multiple task windows simultaneously and try to add the tasks to the job, there are problems with the wizard.

Workaround:

Open only one window at a time.


 

Config Editor Known Problems

Table 8 Config Editor Known Problems 

Bug ID
Summary
Explanation

CSCsb78495

Config Editor overwrite job does not work for PIX devices

A Config Editor job in the overwrite mode, does not work for PIX devices. That is, when you are deploying a configuration that you have edited using Config Editor, to a PIX device, in the overwrite mode, the deployment is unsuccessful.

This happens if you:

1. Edit the configuration of a device using Config Editor and save it.

2. Create a job to deploy that configuration to a PIX device, using the Overwrite mode.

The job fails.

However, the job, succeeds in the Merge mode.

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.

CSCsa39790

Config Editor updates the Device and Credential Repository with an encrypted string.

If service password-encryption is enabled on the device, the credential is encrypted in the 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.


Netshow Known Problems

Table 9 NetShow Known Problems 

Bug ID
Summary
Explanation

CSCsb43125

RME database does not update the CommandSet details after migration

RME database does not update the CommandSet details after migration

This is caused by the character '+' in the Command Set name RME3.4+IDU11.0. NetShow in RME 4.0.x UI does not allow this character.

Workaround:

Before taking a backup in RME3.x, make sure that none of the CommandSet names have special characters.

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

The command moves to the Available Commands list.

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

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. Re-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. Select the command from the Available Commands list and click Delete Adhoc.

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

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 add an Adhoc command, 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

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:

Use the Per-device Print option.

Increase the Tomcat heap-size.

Reduce the number of devices in the job.


Software Management Known Problems

Table 10 Software Management Known Problems 

Bug ID
Summary
Explanation

CSCsb68458

Software Management fails on Catalyst 5500 with an error

An error, SWIM1035, appears when you try to distribute new software to Catalyst 5500

This occurs:

When RME 4.0 (or later) is installed.

When the device is Catalyst 550x with Supervisor III (WS-X5530)

The content of the error message is :

SWIM1035: Error while performing Recommendation operation.

Runtime error encountered while filtering images caused by a problem with a running image on the device.

See the Troubleshooting section of the RME 4.0 help.

Workaround:

None.

CSCsc04541

Import Image from Device fails when flash partition is flash:1

CiscoFlashMib returns flash:1 as the partition name, where none exists on the device. This results in problems while importing images from 2611 and 3660 routers.

Workaround:

None.

CSCsb42968

RME 4.0 does not distribute images to Cisco Catalyst 6500 series devices running CAT OS.

This problem occurs when the image is being copied to:

1. bootflash: using TFTP or RCP.

2. Slot0: using RCP only.

Workaround:

Use Slot0: with TFTP for distribution.

CSCsa92049

Software Management-SOL: Edit Admin Preferences displays an error

In Software Management, when you make a change to Admin Preferences (Admin > Software Mgmt > View/Edit Preferences) the operation fails with an error
Failed to execute df -k command

This happens when there is not enough swap space on the server to create a new java process.

Workaround:

Increase swap space and retry the operation.

None

Cannot undo image upgrade of tar images for DSBU switches.

After performing an image upgrade of tar images for DSBU switches, you cannot undo the job.

Workaround:

Select the tar image and schedule a new distribution job.

CSCin19501

Software Management includes the bootflash of MSFC as a storage option.

This happens for Cat6000 supervisors running IOS.

Storing the IOS images in the bootflash might bring the device down.

Workaround:

Do not select the bootflash to store the image while upgrading Cat6000 devices running IOS.

Select a different storage location.

CSCsa29037

Image upgrade using Remote Stage fails if the image size exceeds 32 MB.

In the Remote-Stage flow, the only protocol that is supported currently between Remote Stage device and target device, is TFTP.

Here, it uses the TFTP server of IOS on the RS device.

There is a limitation in the Cisco IOS TFTP server for transferring files exceeding 32MB from Remote Stage device to Target device.

Workaround:

Please upgrade the IOS image to any of the following versions which has the 32 MB fix:

12.2(18)SXE

12.003(009.008)

12.0(29.03)S

12.2(17d)SXB07

12.2(18)SXD04 12.2(25.04)S

12.3(09.08)T

CSCsa32595

Software Management distribution fails for all devices running Cisco IOS Release 12.3(5x).

This happens because CISCO-FLASH-MIB returns the Flash partition name as Flas instead of Flash.

This problem occurs in all devices running Cisco IOS Release 12.3(5x).

Workaround:

None.

CSCsa33864

Add Image or distribution fails in Software Management.

If the tftpboot directory is either a symbolic link or a soft link to a different directory, Software Management Add Image or Distribution operations fail.

Workaround:

None.

CSCsa35853

Software Management Add Image from device and Image Distribution flows fail.

This occurs when there are a large number of Cisco Catalyst 2900XL and 3500XL Series Switches selected in the workflow.

These devices will be in pre-deployed state or might have invalid Telnet credentials in the Device Credential Repository.

The application attempts to connect to the device to obtain Flash device and image file information.

Workaround:

We recommend that you do not include a large number of pre-deployed Cisco Catalyst 2900XL and 3500XL Series Switches in the workflow.

CSCsa32962

Device reboot fails when upgraded or downgraded to images with Cisco IOS Release12.2(14)SY*.

The device goes into ROMMMON mode.

This happens when the device is upgraded or downgraded to 12.2(14)SY* versions, that is, 12.2(14)SY4, 12.2(14)SY6.

However, Software Management operations cannot be performed after the upgrade, since the CISCO-Flash-Mib is broken.

Workaround:

If you have 12.2(14)SY* images, upgrade to a higher version available on Cisco.com.

If you have to upgrade or downgrade to these versions, do not select Reboot Immediately in the Software Management Job Options window.

Reboot the device manually.

CSCsa37036

copyFromFlash on Aironet device always returns success even when there are no files on Flash.

This problem occurs in all Aironet devices. These devices do not have proper Flash instrumentation.

Workaround:

None.

CSCsa22845

Catalyst 5000—Discrepancy in Image Import from Device and Add Image from Network

Image import from the network is not supported for Catalyst 5000.

Workaround:

None.

CSCsa39312

C10700: Distribution fails because of too many boot commands.

If there are too many valid boot commands in the device startup-config, the boot command for the new image will not get added to device bootvar.

This happens during device upgrade using Software Management.

If you select the Reboot option because of this, the device is rebooted but it does not boot with the new image.

This happens only if many valid boot commands exists on the device before upgrade through Software Management.

Workaround:

Remove some boot commands from startup-config before trying the Software Management job.

CSCin50067

CE: Reboot verification fails when comparing the image version

Reboot verification may fail when images with version prior to 5.1.x, are distributed to Content Engine devices. As a result, Software Management distribution jobs show the status as Failed although the job is successful.

Content Engine devices running ACNS 5.1 or lower, may not return a string that indicates the build number of the software release.

For example, ACNS 5.1.3b17 will be returned in ceAssetSoftwareRevision as 5.1.3.

Workaround:

Manually check the reload.

CSCsf28724

(continued)

Device selection not properly retained when back button is pressed in SWIM Remote Staging flow.

While performing Remote Staging through SWIM, the devices that are selected are not retained when the Back button is clicked. This occurs in the following flows:

Selection of Different Devices:

a. Select Resource Manager Essentials > Software Mgmt > Software Distribution.

The Distribution Method dialog box appears.

b. Select Use remote staging and click Go.

The Select Remote Stage Device dialog box appears.

c. Select Device A in the Remote Stage Device Selection dialog box.

d. Select the Device B in the Remote Staging and Distribution dialog box.

e. Click Next.

f. Click Back and go to the previous screen and select another device in the Remote Stage Device Selection dialog box.

g. Click Next.

You will find Device A selected instead of Device B in the Remote Staging and Distribution screen.

CSCsf28724

(continued)

 

Selection of same device:

a. Select Resource Manager Essentials > Software Mgmt > Software Distribution.

The Distribution Method dialog box appears.

b. Select Use remote staging and click on Go.

The Select Remote Stage Device dialog box appears.

c. Select Device A in the Remote Stage Device Selection dialog box.

d. Click Next

e. Select Device B in the Remote Staging and Distribution dialog box.

f. Click Next.

g. Click Back and go to the previous screen and select the same device in the Remote Stage Device Selection dialog box.

h. Click Next .You will find Device A selected instead of Device B in the Remote Staging and Distribution dialog box. Also the following error is displayed:

You have selected the Remote Stage device for upgrade. This device cannot be upgraded in the same job. Deselect this device from the devices to be upgraded.

Workaround:

Use Cancel button instead of back button in Device Recommendation dialog box.

or

Deselect the remote stage device and select list of target devices again.

CSCsa08356

(continued)

Reboot verification is not performed for Standby Supervisor card.

This problem occurs because the image version for standby supervisor is not available in the MIB. This is because IOS devices do not have dual supervisor support. Dual supervisor support for IOS devices will be implemented in the LMS 3.0, the next LMS release.

Workaround 1:

Manually verify the reboot for standby supervisor.

Workaround 2:

1. Make sure Auto Sync feature is configured in the device. By default this option is configured in the device. This will synchronize active and standby startup configurations.

2. Schedule a swim distribution job to copy the new image to the active supervisor by selecting active supervisor flash device. The active supervisor flash devices will not have the prefix slave in their display name.

Do not select Reboot immediately after downloading option in the distribution job options.

3. Use the same device again to schedule a swim distribution job with the same new image used in Step 2 but selecting the similar standby flash device. The standby supervisor flash devices will have the prefix slave in their display name.

For instance, if you have selected disk0 as the flash device in step2 then select slave-disk0 as the flash device now.

Check Do not insert new boot commands into configuration file option in the distribution job options while scheduling the second job.

4. On successful completion of the above steps reboot the device using config.

   

Now the active and standby supervisors should be running the new image.


Note On a reload of cat4500 devices there will be a switch over of the supervisors, i.e the current active will become the standby and vice versa(this behaviour is different in the case of cat6500 IOS devices where the supervisors retain the same state).


This can only be carried out per device, since user needs to select flash device for manual upgrade.

CSCsl58585

RME deletes NVRAM configuration files from 29/35/37xx switches on executing erase flash command.

The following scenario is noticed in DSBU switches (29xx, 35xx, 37xx):

Before upgrading to a new IOS image, the RME Software Management jobs require the flash in the device to be erased due to insufficient space. For this purpose, an erase flash is performed before pushing out the new IOS image to the device, to ensure enough space is available for the image. This leads to deletion of NVRAM configuration files.

When the device is reloaded to load the new IOS image, few issues are encountered as a result of these missing NVRAM files.

Some of the problems are:

SSH/HTTPS/SNMPv3 accesses are no longer possible.

ifIndex values are changed

Workaround:

Before scheduling the Software distribution job ensure that you free up the space in the disk so that the application does not perform an erase flash due to insufficient space.


Change Audit Known Problems

Table 11 Change Audit Known Problems 

Bug ID
Summary
Explanation

CSCsa33492

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


Syslog Known Problems

Table 12 Syslog Known Problems 

Bug ID
Summary
Explanation

CSCsb87475

Syslogs are not received when the CW Server is inside NAT/Firewall

Syslogs are not received when the CiscoWorks server is inside NAT/Firewall in Solaris.

Workaround:

None.

CSCsa26519

Dateline Standard Time or Greenwich Mean Time is not supported.

When you see the time zone as (GMT-12:00) Eniwetok, Kwajalein, incorrect Syslog times are sent with the Syslog messages.

Workaround:

None.

CSCsa33862

Error while specifying backup location.

You cannot specify a mapped drive as backup location.

This results in an error message that the location does not exist or that you do not have permission to access it.

Workaround:

None.

CSCdk47488

Changing the default logging facility.

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

Workaround:

Set PIX device to facility 23.

CSCsa15703

MF: Create: UI alignment is lost if subfacility message type is selected

While trying to define message filters by choosing many Syslog message types, the UI alignment of the subfacility field is sometimes lost.

This happens only when many Syslog message types are chosen and a scroll bar appears. After the scroll bar appears, if a message type containing a subfacility string is added, this problem is seen.

Workaround:

None.

CSCSa57752

Alias device problems in Syslog

These occur after alias resolution happens in a way that the normal device is rejected and the aliased interface is moved to normal.

There are two problems:

Syslogs from some normal devices appear as syslogs from unexpected devices.

Workaround:

Restart the Syslog Analyzer.

Cannot find Syslogs from some normal devices in the standard or unexpected device reports.

Workaround:

None. However, resolving the alias immediately after adding the devices to RME, largely mitigates the problem.


cwcli export Known Problems

Table 13 cwcli export Known Problems 

Bug ID
Summary
Explanation

CSCsb36330

cwcli export config does not export configuration data to standard output.

This happens for multiple device invocations of the cwcli export config command as well as for single device invocations that do not have the -s 1 argument.

Workaround:

1. Export the config for one device at a time,

2. Specify the -s 1 command line argument.

The configuration data is written to the standard output stream.


Contract Connection Known Problems

Table 14 Contract Connection Known Problems 

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.

CSCsf12031

Error on getting contract.

This error occurs while generating a Contract Connection Report. To get this error:

1. Go to RME > Reports > Report Generator.

2. Select Contract Connection from the Application drop down list box, .

3. Select Report Based on Contract from the Reports drop down list box,

4. Select the required devices from the Select Devices pane.

5. Select a contract from the Select Contract pane.

6. Specify the job schedule run type as Immediate.

7. Click Finish.

The following error message is displayed:

CCX0004: Problem with posting and getting results from cisco.com. Try again later.

This is a rare scenario.It occurs rarely in one or two servers, when at a time, there are many URL connections open in those servers.

This error is also displayed for scheduled report jobs at the time of the job execution.

Workaround:

None.


Bug Toolkit Known Problems

Table 15 Bug Toolkit Known Problems 

Bug ID
Summary
Explanation

CSCsb56985

Defect subject link not working properly in Bug Details Report

Clicking on the bug headline link in the bug summary report does not show the bug description.

Workaround:

In the Locate Device Report, click the headline to view the detailed description of the bug.

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


Server, Browser, UI, and Desktop Known Problems

Table 16 Server, Browser, UI, and Desktop Known Problems 

Bug ID
Summary
Explanation

CSCsb84712

Job Browser Sort by Job ID is incorrect

When there are more than 9 instances of a job, sorting of the Job ID field in the RME Job Browser is incorrect.

This happens when there are more than 9 instances of a job.

For example when there are over 9 instances of the same Job ID, including 1000.10, 1000.11 is the sorting appears like this:

1000.1

1000.10

1000.11

1000.2

1000.3

1000.4

...

1000.9

That is, the sort occurs in the numeric order as the Job ID field has `number' as the datatype.

This is because the Job IDs are incremented in the textual order, whereas the sorting happens in numeric order.

This is because of a limitation in the User Interface.

Workaround:

None.

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

CTMJrmServer goes down after changing to ACS mode.

(Continued)

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

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

Or

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

Workaround:

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

 

CSCsa89512

Difference in log file time-stamp and system time

The time-stamp in the stdout.log file is different from the system time.

This occurs only on some Solaris machines.

Workaround:

None.

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.

CSCds16984

Under certain conditions, you 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 to get the process running.

CSCdp08278

Tasks might fail if server is not 100% up.

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

Workaround:

For Netscape, click Reload.

For Internet Explorer, click Refresh.

At the beginning of CiscoWorks session, if you select a task from the navigation tree before the server is fully operational, the task might fail.

Workaround:

Select the task again. If this does not help, restart the system using one of these methods:

Using the GUI:

a. Select Server Configuration > Administration > Process Management > Stop Process.

b. Select the System radio button and click Finish.

c. Select Server Configuration > Administration > Process Management > Start Process.

d. Select the System radio button and click Finish.

CSCdp08278 (Continued)

Tasks might fail if server is not 100% up.

From command line interface, enter:

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

Make sure all process are running before relaunching tasks.

Select Server Configuration >
Administration > Process Status. The State column shows whether processes are running.

CSCsf32067 (Continued)

Extra grey spaces appear in few SWIM workflows if number of rows returned is less than 10.

Extra grey spaces appear in following SWIM workflows:

Go to RME > Software Mgmt > Software Repository

a. Click on Add button.

The Add Images dialog box appears.

b. Select any one of the options:

Cisco.com

Device

File System

Network

Out of Sync report

CSCsf32067 (Continued)

 

Go to RME > Software Mgmt > Software Distribution > Upgrade Analysis > Cisco.com

Go to RME > Software Mgmt > Software Distribution > By devices (Advanced)

The resulting rows for the above mentioned flows, if less than 10, appears with extra grey space.

Workaround:

None.

CSCsf32082

The UI for SFS device category under Netconfig templates not consistent with other device category UIs.

When you select Netconfig templates for the SFS device category, the UI for entering SFS parameters is not the same as the UI for other device categories.

This is only a UI inconsistency and does not affect any functionality or flow.

Workaround:

None.

CSCsg03705

Internet Explorer browser retains last visited screen window size.

When you open a window of any size in Internet Explorer, it remembers the size of the Window previously opened. Any new popup window opened after that will resize to this previously visited size.

Workaround:

1. Close all instances of Internet Explorer that are currently open, except for one.

2. Right click a link on the web page and select Open in new window option.

3. Close the first instance of the browser that was originally open by clicking the close icon in the upper right corner.

4. Resize the existing window by dragging the sides until it is full screen again.

5. Click the close icon in the upper right corner while holding down the Ctrl key.

The next time you open your Internet Explorer browser, the window will once again appear full screen.

CSCsg03697

Internet Explorer popups appear as 10 x 10 screen if IP address is provided as server address.

This issue may occur for some of the popup screens. Internet Explorer displays popups as 10 x 10 screen if IP address is provided as server address in the URL. This is an Internet Explorer browser issue.

Workaround:

Invoke the server with host name.

or

Resize the window.

CSCsg03686

Scroll bars do not appear for few records if the number of records returned is between 16 - 20 in a Version Summary Report.

This problem occurs when you generate a Version Summary report by following these steps:

1. Go to RME > Config Management > Archive Management > Version Summary

The Version Summary dialog box appears.

2. Select few devices from the Device Selection pane.

The Version Summary Report is generated.

The scrollbars do not appear for records from 16 - 20.

Workaround:

For reports having record results between 16 to 20, use mouse press and drag to view the end of the report.


Common/Other Known Problems

Table 17 Common/Other Known Problems 

Bug ID
Summary
Explanation

CSCsa38849

Ctrl+N and Open in New Window result in unexpected behavior in RME.

RME shows unexpected behavior when you open a new window during any of the work flows.

This happens if you press Ctrl+N or select Open in New Window and continue to work on the same flow as the base window.

However, two different workflows (not under the same tab) does not cause a problem.

Workaround:

None.

CSCin17659

RME saves reports as .pl files when using Netscape.

In Netscape, if the file type exported is not pre-configured. The bug reports are saved as .pl files instead of .txt files.

Workaround:

Add the file type manually.

To do so, select Edit > Preferences and specify the default application to open the file.

CSCsa29250

Cannot filter devices based on user-defined fields

Devices cannot be filtered based on User-defined fields.

Workaround:

Create device groups in Common Services based on user defined fields and use these in the RME workflows.

See the User Guide for Common Services 3.0.3 for details on creating Device groups with user-defined fields.

CSCdw48650

(For Archive Management)

Startup and running configuration will not be fetched automatically after a CPU switchover operation.

Syslog messages are not available after a CPU switchover operation.

Owing to this, the Archive Management cannot update Config Archive automatically.

Workaround:

Perform a sync archive operation.

See the User Guide for RME 4.0 for the procedure.

This operation fetches the running configuration of the active CPU.

CSCdw48650

(For Inventory)

For ONS Series (ONS 15540 ESP) devices, Inventory Reports might not reflect the latest device information.

Syslog messages are not available after a CPU switchover operation, as a result of which the RME database is not updated automatically.

Workaround:

Run an Immediate Inventory Collection job to update Inventory.

See the User Guide for RME 4.0 for the procedure.

CSCdw48650

(For Software Management)

For ONS Series (ONS 15540 ESP) devices, Software image recommendation might be based on obsolete information.

Syslog messages are not available after a CPU switchover operation

Owing to this, the RME database is not updated automatically. Software image recommendation is based on data collected by Inventory.

Workaround:

Run an Immediate Inventory Collection job to update Inventory.

See the User Guide for RME 4.0.3 for the procedure.

Software image might be downloaded to a slot for which it was not intended.

If a CPU switchover occurs after a software image distribution job is scheduled, Syslog messages are not available for the CPU switchover operation.

As a result of this, the RME database is not updated automatically. Hence, the software image might be downloaded to a slot for which it was not intended.

Workaround:

Avoid scheduling image distribution jobs. Instead perform jobs immediately.

If image distribution jobs are scheduled, ensure that the CPU does not switchover before the job is completed.

CSCsa17529

Special characters such as single quotes, are not supported in a report template name.

When you click on a template name that has unsupported characters (such as single quotes in the link) in the report template table, the following error appears:

Page cannot be displayed.

This happens only if you use a special character such as single quote in the template name while creating the template.

Workaround:

Use only this supported character set:

{A to Z, a to z, 0 to 9, -, _, ., ), (, / and blank space}

CSCsa18505

Netscape 7 on Solaris Save Report As PDF option displays a 500 Error

This problem occurs when you generate Hardware Report and save it as PDF.

An error appears:

Error: 500

Location: /rme/InventoryReports.do

Internal Servlet Error:

java.lang.NullPointerException

at com.lowagie.text.Document.add(Unknown Source)

at com.cisco.nm.uii.reports.StackOfStackedTablesRequestHelper.doPDFExport(StackOfStackedTablesRequestHelper.java:397)

at com.cisco.nm.rmeng.inventory.reports.ui.action.InventoryReportsAction.perform(InventoryReportsAction.java:199)

at org.apache.struts.action.ActionServlet.processActionPerform(ActionServlet.java:1786

Workaround:

This bug is caused by the Acrobat Plugin and Netscape browser combination.

For details see:

http://my.justlinux.com/forum/showthread.php?threadid=127625

CSCSa58546

RME cannot create device groups based on display name attributes

In RME, device groups cannot be created based on the domain name and display name configured in DCR (Device Credential Repository).

In RME, a device group can be created, based on device sysName and domain name obtained from device and stored as inventory data.

However, these are not the same as the display name and the domain name that is configured in DCR.

Therefore, if you create a filter for sysName but if the sysName is not the same as the name of the device in DNS (or the display name), you cannot not see any of your devices that match the filter.

In such a case, even hostnames and DNS names with differing cases do not match.

Workaround:

Create the required device group in Common Services based on DCR's display name domain name. The same groups can be seen in RME flows and can be used.


Resolved Problems in RME 4.0.5

This section has resolved problems from RME 4.0.5.

Table 18 describes the problems that were resolved in RME 4.0.5:

Table 18 Resolved Problems in RME 4.0.5

Bug ID
Component
Summary

CSCsb50677

Device categorization of Routers 1801 and 1802 appeared incorrectly in Device Credentials Repository.

This problem has been resolved.

CSCsb86166

Change Audit could not ignore VLAN-PRIMARY.

This problem has been resolved.

CSCsc02023

DCR did not get updated after running the Config Editor job, in RME 4.0 SP2.

This problem has been resolved.

CSCsb65363

RME 3.5 boots on slave disk 0

This problem has been resolved.

CSCsb27389

Creation of a distribution job for Cisco Catalyst 6000 Series Dual SUP was not allowed.

This problem has been resolved.

CSCsb68389

Config Export returned Permission Denied

This problem has been resolved.

CSCsc38626

Adding an image from the network using Sync Report took over 30 minutes.

This problem has been resolved.

CSCsb71888

Software Management failed if ciscoFlashPartitionName was :flash1

This problem has been resolved.

CSCsb59359

Importing of images from subdirectory was not supported for 3750 stack device.

This problem has been resolved.

CSCsb88589

Boot commands were wrongly updated in Software Management.

This problem has been resolved.

CSCsc45170

Software Management left RFF device in boot mode when TACACS was configured

This problem has been resolved.

CSCsc60288

Distribution hanged for 3550/3750/2900 switches when SSH and TFTP were used.

This problem has been resolved.

CSCsb70782

In Syslog, Import did not work for Automated Actions and Message Filters.

This problem has been resolved.

CSCsb36330

cwcli export config did not export configuration data to standard output.

This problem has been resolved.

CSCsc44556

Contract Connection Summary Report failed with http response code 500.

This problem has been resolved.

CSCsb56985

Defect subject link did not work properly in Bug Details Report.

This problem has been resolved.

CSCsb84712

Job Browser, Sort by Job ID was incorrect.

This problem has been resolved.

CSCsd63541

Netconfig Job result showed Deploy Failed even for successful jobs.

This problem has been resolved.

CSCsd69446

In NetConfig, downloading CSS RADIUS template made the device unreachable.

This problem has been resolved.

CSCsd85901

Save As button was missing in the Config Viewer page in the Raw mode in Config Editor.

This problem has been resolved.

CSCsd46291

Post-upgrade image verification failed for direct image distribution from Cisco.com to the device.

This problem has been resolved.

CSCsc06696

Image distribution failed with an error message, No Inventory Collected.

This problem has been resolved.

CSCsc47973

ACS integration with NDG provided access to devices.

This problem has been resolved.

CSCsc17381

In the Device Center, the Check Device Credentials option under Management Tasks,does not retun results.

This problem has been resolved.

CSCsc37630

System Inventory Collection and Polling jobs failed

This problem has been resolved.

CSCsb87660

Changes to the Inventory job schedule caused duplicate jobs

This problem has been resolved.

CSCsb68389

Config Export returned Permission Denied although the corresponding entry for the specified directory was added to the Property file.

This problem has been resolved.

CSCsf03178

The DCV report erroneously reported that Telnet credentials were incorrect for a device if it took longer than two seconds to get a device prompt after entering the Telnet password.

This problem typically occured in an AAA environment where authentication required more than two seconds.

This problem has been resolved.


Obtaining Documentation

Cisco documentation and additional literature are available on Cisco.com. Cisco also provides several ways to obtain technical assistance and other technical resources. These sections explain how to obtain technical information from Cisco Systems.

Cisco.com

You can access the most current Cisco documentation at this URL:

http://www.cisco.com/techsupport

You can access the Cisco website at this URL:

http://www.cisco.com

You can access international Cisco websites at this URL:

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

Product Documentation DVD

The Product Documentation DVD is a comprehensive library of technical product documentation on a portable medium. The DVD enables you to access multiple versions of installation, configuration, and command guides for Cisco hardware and software products. With the DVD, you have access to the same HTML documentation that is found on the Cisco website without being connected to the Internet. Certain products also have .PDF versions of the documentation available.

The Product Documentation DVD is available as a single unit or as a subscription. Registered Cisco.com users (Cisco direct customers) can order a Product Documentation DVD (product number DOC-DOCDVD= or DOC-DOCDVD=SUB) from Cisco Marketplace at this URL:

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

Ordering Documentation

Registered Cisco.com users may order Cisco documentation at the Product Documentation Store in the Cisco Marketplace at this URL:

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

Nonregistered Cisco.com users can order technical documentation from 8:00 a.m. to 5:00 p.m. (0800 to 1700) PDT by calling 1 866 463-3487 in the United States and Canada, or elsewhere by calling 011 408 519-5055. You can also order documentation by e-mail at tech-doc-store-mkpl@external.cisco.com or by fax at 1 408 519-5001 in the United States and Canada, or elsewhere at 011 408 519-5001.

Documentation Feedback

You can rate and provide feedback about Cisco technical documents by completing the online feedback form that appears with the technical documents on Cisco.com.

You can submit comments about Cisco documentation by using the response card (if present) behind the front cover of your document or by writing to the following address:

Cisco Systems
Attn: Customer Document Ordering
170 West Tasman Drive
San Jose, CA 95134-9883

We appreciate your comments.

Cisco Product Security Overview

Cisco provides a free online Security Vulnerability Policy portal at this URL:

http://www.cisco.com/en/US/products/products_security_vulnerability_policy.html

From this site, you will find information about how to:

Report security vulnerabilities in Cisco products.

Obtain assistance with security incidents that involve Cisco products.

Register to receive security information from Cisco.

A current list of security advisories, security notices, and security responses for Cisco products is available at this URL:

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

To see security advisories, security notices, and security responses as they are updated in real time, you can subscribe to the Product Security Incident Response Team Really Simple Syndication (PSIRT RSS) feed. Information about how to subscribe to the PSIRT RSS feed is found at this URL:

http://www.cisco.com/en/US/products/products_psirt_rss_feed.html

Reporting Security Problems in Cisco Products

Cisco is committed to delivering secure products. We test our products internally before we release them, and we strive to correct all vulnerabilities quickly. If you think that you have identified a vulnerability in a Cisco product, contact PSIRT:

For Emergencies only — security-alert@cisco.com

An emergency is either a condition in which a system is under active attack or a condition for which a severe and urgent security vulnerability should be reported. All other conditions are considered nonemergencies.

For Nonemergencies — psirt@cisco.com

In an emergency, you can also reach PSIRT by telephone:

1 877 228-7302

1 408 525-6532


Tip We encourage you to use Pretty Good Privacy (PGP) or a compatible product (for example, GnuPG) to encrypt any sensitive information that you send to Cisco. PSIRT can work with information that has been encrypted with PGP versions 2.x through 9.x.

Never use a revoked or an expired encryption key. The correct public key to use in your correspondence with PSIRT is the one linked in the Contact Summary section of the Security Vulnerability Policy page at this URL:

http://www.cisco.com/en/US/products/products_security_vulnerability_policy.html

The link on this page has the current PGP key ID in use.

If you do not have or use PGP, contact PSIRT at the aforementioned e-mail addresses or phone numbers before sending any sensitive material to find other means of encrypting the data.


Obtaining Technical Assistance

Cisco Technical Support provides 24-hour-a-day award-winning technical assistance. The Cisco Technical Support & Documentation website on Cisco.com features extensive online support resources. In addition, if you have a valid Cisco service contract, Cisco Technical Assistance Center (TAC) engineers provide telephone support. If you do not have a valid Cisco service contract, contact your reseller.

Cisco Technical Support & Documentation Website

The Cisco Technical Support & Documentation website provides online documents and tools for troubleshooting and resolving technical issues with Cisco products and technologies. The website is available 24 hours a day, at this URL:

http://www.cisco.com/techsupport

Access to all tools on the Cisco Technical Support & Documentation website requires a Cisco.com user ID and password. If you have a valid service contract but do not have a user ID or password, you can register at this URL:

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


Note Use the Cisco Product Identification (CPI) tool to locate your product serial number before submitting a web or phone request for service. You can access the CPI tool from the Cisco Technical Support & Documentation website by clicking the Tools & Resources link under Documentation & Tools. Choose Cisco Product Identification Tool from the Alphabetical Index drop-down list, or click the Cisco Product Identification Tool link under Alerts & RMAs. The CPI tool offers three search options: by product ID or model name; by tree view; or for certain products, by copying and pasting show command output. Search results show an illustration of your product with the serial number label location highlighted. Locate the serial number label on your product and record the information before placing a service call.


Submitting a Service Request

Using the online TAC Service Request Tool is the fastest way to open S3 and S4 service requests. (S3 and S4 service requests are those in which your network is minimally impaired or for which you require product information.) After you describe your situation, the TAC Service Request Tool provides recommended solutions. If your issue is not resolved using the recommended resources, your service request is assigned to a Cisco engineer. The TAC Service Request Tool is located at this URL:

http://www.cisco.com/techsupport/servicerequest

For S1 or S2 service requests, or if you do not have Internet access, contact the Cisco TAC by telephone. (S1 or S2 service requests are those in which your production network is down or severely degraded.) Cisco engineers are assigned immediately to S1 and S2 service requests to help keep your business operations running smoothly.

To open a service request by telephone, use one of the following numbers:

Asia-Pacific: +61 2 8446 7411 (Australia: 1 800 805 227)
EMEA: +32 2 704 55 55
USA: 1 800 553-2447

For a complete list of Cisco TAC contacts, go to this URL:

http://www.cisco.com/techsupport/contacts

Definitions of Service Request Severity

To ensure that all service requests are reported in a standard format, Cisco has established severity definitions.

Severity 1 (S1)—An existing network is down, or there is a critical impact to your business operations. You and Cisco will commit all necessary resources around the clock to resolve the situation.

Severity 2 (S2)—Operation of an existing network is severely degraded, or significant aspects of your business operations are negatively affected by inadequate performance of Cisco products. You and Cisco will commit full-time resources during normal business hours to resolve the situation.

Severity 3 (S3)—Operational performance of the network is impaired, while most business operations remain functional. You and Cisco will commit resources during normal business hours to restore service to satisfactory levels.

Severity 4 (S4)—You require information or assistance with Cisco product capabilities, installation, or configuration. There is little or no effect on your business operations.

Obtaining Additional Publications and Information

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

The Cisco Product Quick Reference Guide is a handy, compact reference tool that includes brief product overviews, key features, sample part numbers, and abbreviated technical specifications for many Cisco products that are sold through channel partners. It is updated twice a year and includes the latest Cisco offerings. To order and find out more about the Cisco Product Quick Reference Guide, go to this URL:

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

Cisco Marketplace provides a variety of Cisco books, reference guides, documentation, and logo merchandise. Visit Cisco Marketplace, the company store, at this URL:

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

Cisco Press publishes a wide range of general networking, training and certification titles. Both new and experienced users will benefit from these publications. For current Cisco Press titles and other information, go to Cisco Press at this URL:

http://www.ciscopress.com

Packet magazine is the Cisco Systems technical user magazine for maximizing Internet and networking investments. Each quarter, Packet delivers coverage of the latest industry trends, technology breakthroughs, and Cisco products and solutions, as well as network deployment and troubleshooting tips, configuration examples, customer case studies, certification and training information, and links to scores of in-depth online resources. You can access Packet magazine at this URL:

http://www.cisco.com/packet

iQ Magazine is the quarterly publication from Cisco Systems designed to help growing companies learn how they can use technology to increase revenue, streamline their business, and expand services. The publication identifies the challenges facing these companies and the technologies to help solve them, using real-world case studies and business strategies to help readers make sound technology investment decisions.

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

http://www.cisco.com/ipj

Networking products offered by Cisco Systems, as well as customer support services, can be obtained at this URL:

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

Networking Professionals Connection is an interactive website for networking professionals to share questions, suggestions, and information about networking products and technologies with Cisco experts and other networking professionals. Join a discussion at this URL:

http://www.cisco.com/discuss/networking

World-class networking training is available from Cisco. You can view current offerings at this URL:

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

Open Source License Acknowledgements

The following acknowledgements pertain to this software license.

OpenSSL/Open SSL Project

This product includes software developed by the OpenSSL Project for use in the OpenSSL Toolkit (http://www.openssl.org/).

This product includes cryptographic software written by Eric Young (eay@cryptsoft.com).

This product includes software written by Tim Hudson (tjh@cryptsoft.com).

License Issues

The OpenSSL toolkit stays under a dual license, i.e. both the conditions of the OpenSSL License and the original SSLeay license apply to the toolkit. See below for the actual license texts. Actually both licenses are BSD-style Open Source licenses. In case of any license issues related to OpenSSL please contact openssl-core@openssl.org.

OpenSSL License:

© 1998-1999 The OpenSSL Project. All rights reserved.

Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met:

1. Redistributions of source code must retain the copyright notice, this list of conditions and the following disclaimer.

2. Redistributions in binary form must reproduce the above copyright notice, this list of conditions, and the following disclaimer in the documentation and/or other materials provided with the distribution.

3. All advertising materials mentioning features or use of this software must display the following acknowledgment: "This product includes software developed by the OpenSSL Project for use in the OpenSSL Toolkit. (http://www.openssl.org/)"

4. The names "OpenSSL Toolkit" and "OpenSSL Project" must not be used to endorse or promote products derived from this software without prior written permission. For written permission, please contact openssl-core@openssl.org.

5. Products derived from this software may not be called "OpenSSL" nor may "OpenSSL" appear in their names without prior written permission of the OpenSSL Project.

6. Redistributions of any form whatsoever must retain the following acknowledgment:

"This product includes software developed by the OpenSSL Project for use in the OpenSSL Toolkit (http://www.openssl.org/)"

THIS SOFTWARE IS PROVIDED BY THE OpenSSL PROJECT "AS IS"' AND ANY EXPRESSED OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE OpenSSL PROJECT OR ITS CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.

This product includes cryptographic software written by Eric Young (eay@cryptsoft.com). This product includes software written by Tim Hudson (tjh@cryptsoft.com).

Original SSLeay License:

© 1995-1998 Eric Young (eay@cryptsoft.com). All rights reserved.

This package is an SSL implementation written by Eric Young (eay@cryptsoft.com).

The implementation was written so as to conform with Netscapes SSL.

This library is free for commercial and non-commercial use as long as the following conditions are adhered to. The following conditions apply to all code found in this distribution, be it the RC4, RSA, lhash, DES, etc., code; not just the SSL code. The SSL documentation included with this distribution is covered by the same copyright terms except that the holder is Tim Hudson (tjh@cryptsoft.com).

Copyright remains Eric Young's, and as such any Copyright notices in the code are not to be removed. If this package is used in a product, Eric Young should be given attribution as the author of the parts of the library used. This can be in the form of a textual message at program startup or in documentation (online or textual) provided with the package.

Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met:

1. Redistributions of source code must retain the copyright notice, this list of conditions and the following disclaimer.

2. Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution.

3. All advertising materials mentioning features or use of this software must display the following acknowledgement:

"This product includes cryptographic software written by Eric Young (eay@cryptsoft.com)".

The word `cryptographic' can be left out if the routines from the library being used are not cryptography-related.

4. If you include any Windows specific code (or a derivative thereof) from the apps directory (application code) you must include an acknowledgement: "This product includes software written by Tim Hudson (tjh@cryptsoft.com)".

THIS SOFTWARE IS PROVIDED BY ERIC YOUNG "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE AUTHOR OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.

The license and distribution terms for any publicly available version or derivative of this code cannot be changed. i.e. this code cannot simply be copied and put under another distribution license [including the GNU Public License].