Cisco Configuration Engine

Table Of Contents

Release Notes for Cisco CNS Configuration Engine Maintenance Release 1.3.2

What's New in this Maintenance Release

Related Documentation

Console Access to CNSIE-2110-K9 System

Console Access to CNSIE-2115-K9 System

Serial Connection Settings

Troubleshooting the Serial Port

Cabling an ASM Interconnect Network

Installation Notes

New Setup Prompts

Port Number

TACACS+ Support

NRP2 Support

New Hop Type for NRP2

Limitations and Restrictions

How to Enable IBM Director

Upgrading from Release 1.3.1 to 1.3.2

How to Use the cnsce.linux.v1.3.2.tar File

How to Use the CD-ROM

Migrating Subject Mappings in Provider Mode of NSM

Utility for Automatic Conversion of Subject Mappings

When to Execute the Script

Limitations

New Event Subject Names

Legacy Subject Names

Resolved Caveats - Maintenance Release 1.3.2

Open Caveats - Maintenance Release 1.3.2

Obtaining Documentation and Submitting a Service Request

Release Notes for Cisco CNS Configuration Engine Maintenance Release 1.3.2

---

The scope of this document includes information relevant to Maintenance Release 1.3.2 only. For information about release 1.3 of this product, refer to the "Related Documentation" section.

What's New in this Maintenance Release

•Many caveats present in release 1.3.1 have been resolved for Maintenance Release 1.3.2 (see "Resolved Caveats - Maintenance Release 1.3.2" section).

•This maintenance release of Cisco CNS Configuration Engine supports Cisco IOS 12.3.

•The base element of the CNS event subject namespace has been changed from cisco.cns.* to cisco.mgmt.cns.* in support of Cisco IOS 12.3.

The CNS event subject namespace has been modified in accordance with the new Cisco subject naming conventions. In order to keep up with the new subject naming convention, CNS agents in Cisco IOS have been modified and released with the 12.3 Cisco IOS train. The change affects the subject names that the CNS agents subscribe to and publish on.

For the smooth transition of existing applications from the old subject namespace, the Namespace Mapping service (NSM) has been updated with a new mechanism that maps old subjects to the new ones.

For more information about how to migrate subject mappings in Provider Mode, see "Migrating Subject Mappings in Provider Mode of NSM" section.

There are no code or configuration changes required in applications written using the NSM API since the API interfaces have not been modified. However, upgrading to Cisco CNS SDK 1.5.3 is a required procedure for the transition.

Applications that are written without the use of the Namespace Mapper have to be modified to accommodate the change in CNS event subjects. For example, the subject cisco.cns.config.load has been modified to cisco.mgmt.cns.config.load.

We recommend that all applications use the Namespace Mapper in order to maintain the separation between design-time and deployment-time subjects.

For a complete list of the new event subject names, see "New Event Subject Names" section.

•The none mode under Event Services Setting in the Setup program is not supported from the Cisco CNS Configuration Engine user interface for updates made from the user interface to devices that use the old CNS event subject names. This is because NSM is not invoked in the none mode. NSM has been modified to translate subject names in support of devices not running Cisco IOS 12.3.

Related Documentation

Other documentation related to this product include:

•Cisco CNS Configuration Engine Administrator's Guide

•Documentation Guide for Cisco CNS Configuration Engine, Release 1.3

•Cisco CNS 2100 Series Intelligence Engine Installation Guide

•Release Notes for Cisco CNS 2100 Series Intelligence Engine

•Cisco CNS 2100 Series Intelligence Engine Machine Code License

•Regulatory Compliance and Safety Information for Cisco CNS 2100 Series Intelligence Engine

•Cisco CNS Software Development Kit API Reference and Programmer Guide

Console Access to CNSIE-2110-K9 System

Normal terminal login to the CNSIE-2110-K9 (x330) system is supported by way of the system serial port. The CNS 2100 Series system redirects and supports console login at the serial port.

For more information about console access to the CNSIE-2110-K9 (x330) system, refer to the Release Notes for Cisco CNS 2100 Series Intelligence Engine, Release 1.3.

Console Access to CNSIE-2115-K9 System

Normal terminal login to the CNSIE-2115-K9 (x335) system is supported by way of the system serial port (See Figure 1, item 7).

Figure 1 CNSIE-2115-K9 (x335)Rear Panel

1. Power connector: Connect the power cable here.

2. Ethernet 2 connector: Connect an Ethernet cable here.

3. USB 3 connector: Connect to a Universal Serial Bus here.

4. Ethernet 1 connector: Connect an Ethernet cable here.

5. ISM connector: Connect an ASM link cable from the ASM interconnect module to this connector.

6. C2T OUT connector: Connect the cable from this connector to the input connector of another server.

7. Serial connector: Connect a 9-pin serial device to this connector.

8. C2T IN connector: Connect the cable from the output connector of another server to this connector.

The CNS 2100 Series system redirects and supports console login at the serial port. It is a more desirable feature because you can perform daily or emergency administrative tasks remotely, by way of the serial port.

Serial Connection Settings

The serial connection settings are as follows:

9600 baud
8 data bit
N (No)parity
1 stop bit

Troubleshooting the Serial Port

The serial port is enabled by default. If there is a connection problem, verify that it is enabled by accessing the Remote Console Redirection menu during system start as follows:

---

Step 1 Press F1, then go to: Configuration/Setup Utility (menu) -> Devices and I/O ports (menu) -> Remote Console Redirection (menu)

Step 2 Make sure the Remote Console Active parameter is enabled.

---

Cabling an ASM Interconnect Network

An Advanced System Management (ASM) bus is integrated into the C2T interconnect cables, so by adding one or more Remote Supervisor Adapters to a C2T chain of servers, you can create an Advanced System Management (ASM) interconnect network. For information about using a Remote Supervisor Adapter for remote server management, see the documentation that comes with the adapter.

Before cabling the ASM interconnect network, review the following information:

•The cables in an ASM interconnect network are hot-swappable.

•Make sure that the firmware for the Remote Supervisor Adapter, ASM processor, and integrated system management processor (ISMP) are at the latest level.

•The servers in an ASM interconnect network are referred to by their assigned addresses, not by their positions in the rack.

An ASM interconnect network can have up to 24 RS-485 connections, depending on the configuration. The connections can include Remote Supervisor Adapters, ASM processors, ASM PCI adapters, and ISMPs. Use the following information to determine the number of servers and connections that you can have on your ASM interconnect network:

•Each Remote Supervisor Adapter, ASM processor, ASM PCI adapter, and ISMP in a server that is connected to the network uses one connection. For example, if a server that is connected to the network has a Remote Supervisor Adapter and an integrated ASM processor, the server uses two connections on the network.

•The network must include at least one server with a Remote Supervisor Adapter (either installed as an option or pre-installed in the server).

You can connect up to 23 xSeries 335 servers into an ASM interconnect network using one Remote Supervisor Adapter. However, if you use both xSeries 335 and xSeries 330 servers in the network, the xSeries 330 servers must be the lowest-numbered servers in the chain. Figure 2 shows an ASM interconnect network with three servers.

Figure 2 ASM Interconnect Network of Three Servers

1. IN: Connect the cable from the output connector of another server to this connector.

2. OUT: Connect the cable from this connector to the input connector of another server.

3. ISM: Connect an ASM link cable from the ASM interconnect module to this connector in the first (A) server.

4. ASM link cable: Connect this cable to the ISM connector (3) in the first server.

5. Mouse: Connect a mouse to this connector.

6. Keyboard: Connect a keyboard to this connector.

7. Video: Connect a monitor to this line.

8. ASM interconnect module: Connect this module to the RS-485 connector (9) on the Remote Supervisor Adapter in the first server.

9. RS-485 on Remote Service Adapter: Connect the ASM Interconnect Module to this connector.

You can add up to 23 more servers to the network by installing a Remote Supervisor adapter in the 24th server, creating a second ASM bus. Figure 3 shows an ASM interconnect network with 46 servers.

Figure 3 ASM Interconnect Network of 46 Servers

1. IN: Connect the cable from the output connector of another server to this connector.

2. OUT: Connect the cable from this connector to the input connector of another server.

3. ISM: Connect an ASM link cable from the ASM interconnect module to this connector in the first (A) server.

4. ASM link cable: Connect this cable to the ISM connector (3) in the first server.

5. Mouse: Connect a mouse to this connector.

6. Keyboard: Connect a keyboard to this connector.

7. Video: Connect a monitor to this line.

8. Second ASM bus: Connect servers 24 through 46 on this bus.

9. First ASM bus: Connect servers 1 through 23 on this bus.

To cable an ASM interconnect network, complete the following steps:

---

Step 1 Follow the instructions for cabling a C2T chain.

Step 2 Connect an ASM interconnect module (which comes with the Remote Supervisor Adapter) to the RS-485 connector on the Remote Supervisor Adapter in the first server. If the network contains more than 23 servers, do the same on the 24th server.

---

Connect an ASM link cable (which comes with the Remote Supervisor Adapter) from the ASM interconnect module to the ISM connector in the first server. Insert a terminator into the second connector on the ASM interconnect module. If the network contains more than 23 servers, do the same on the 24th server.

Installation Notes

The Cisco CNS Configuration Engine 1.3.2 software is contained on a CD-ROM.

To be able to monitor the installation activity and run the Setup program, you should be connected to the system serial port.

To install the software, follow these steps:

---

Step 1 Verify that the CNS 2100 Series system is powered down.

Step 2 Power on the system and quickly insert the Cisco CNS Configuration Engine 1.3.2 CD-ROM in the CD drive.

Step 3 Push the Reset button to restart the system from the CD-ROM.

The software installs automatically. When the install sequence completes, the system automatically ejects the CD-ROM and restarts into Linux from the hard drive.

During the Linux startup sequence, by default, the CNS 2100 Series system redirects and supports console login at the serial port.

Step 4 Refer to the Cisco CNS Configuration Engine Administrator's Guide to run the Setup program.

---

New Setup Prompts

For Maintenance Release 1.3.2, new prompts have been added to the Setup script.

Port Number

Enter port number for http web access:[80]

Enter port number for https web access:[443]

Enter Tomcat internal port number for ajp12 protocol:[8007]

Enter Tomcat internal port number for ajp13 protocol:[8009]

Enter CNS Event Bus Service Parameter:[7500]

Enter CNS Event Bus Daemon Parameter:[7500]

Enter http port for Tibco Web Administration GUI:[7580]

Tibco Web Admin port should always be closed unless the Web admin

GUI is needed. Keeping web admin port open is a security risk.

Would you like to open Tibco Web Administration port (y/n)? [n]

TACACS+ Support

You can specify one set of alternative username and password prompts with two new prompts introduced during setup:

Enter Alternative username prompt for device using TACACS/RADIUS:

Enter Alternative password prompt for device using TACACS/RADIUS:

NRP2 Support

Extra steps are required to log on to an NRP blade through NSP:

---

Step 1 Login to C6400 NSP as a normal Cisco IOS device with username and password.

Step 2 Login to NRP2 using the following command with another set of username and password:

nrps <slot-number>

Step 3 Now you can enable and configure the device as a normal Cisco IOS device.

---

New Hop Type for NRP2

To support NRP2, a new hop type IOS_NRP_SLOT is introduced:

Hop_type	IP_address	Port	Username	Password
IOS_LOGIN	X		X	X
IOS_NRP_SLOT		X	X	X
IOS_EN			X	X

Hop_type	IP_address	Port	Username	Password
COMMSERVER_LOGIN	X		X	X
COMMSERVER		X		X
IOS_LOGIN			X	X
IOS_NRP_SLOT		X	X	X
IOS_EN			X	X

Notes

•Enter the NRP slot number as the Port number.

•Use the IOS_EN information to enter the enable mode of NRP card.

•This is not the enable username/password for the NSP.

Limitations and Restrictions

•All password values in Setup must contain alphanumeric characters only. Special characters have different meanings in the UNIX shell and should not be used for passwords.

•A name (Net, Host, Gateway, or Domain name) is a text string up to 24 characters drawn from the alphabet (A-Z), digits (0-9), minus sign (-), and period (.) with the following restrictions:

–Periods are only allowed when they serve to delimit components of domain-style names.

–No blank or space characters are permitted as part of a name.

–No distinction is made between upper and lower case.

–The first character must be an alpha character.

–The last character must not be a minus sign or period.

–Single character names or nicknames are not allowed.

–Device Name values may contain only: period (.), underscore (_), hyphen (-), and alphanumeric characters.

•Group Name values may contain only: underscore (_) and alphanumeric characters.

How to Enable IBM Director

To enable IBM Director, login as root in a terminal window, then type the following UNIX commands:

ln /etc/rc.d/init.d/init.wbem /etc/rc.d/rc3.d/S85init.wbem

ln /etc/rc.d/init.d/init.wbem /etc/rc.d/rc5.d/S85init.wbem

cp /etc/TWGagent/TWGagent.orig /etc/TWGagent/TWGagent

/etc/rc.d/init.d/init.wbem start

/etc/rc.d/init.d/TWGagent start

Upgrading from Release 1.3.1 to 1.3.2

---

Note The CNS Configuration Engine 1.3.2 upgrade must be performed on a CNS 2100 Series system running CNS Configuration Engine 1.3.1. If there is an earlier release installed on your system, please update to 1.3.1 first.

---

The Cisco CNS Configuration Engine 1.3.2 upgrade package can be retrieved from Cisco.com (CCO) or the Cisco CNS Configuration Engine 1.3.2 CD-ROM.

The HTTP URL is:

http://www.cisco.com/public/sw-center/netmgmt/crypto/cns/confeng/

The FTP location is:

ftp.cisco.com/cisco/crypto/3DES/netmgmt/cns/configuration-engine/

On CCO, or the top-level directory of the Cisco CNS Configuration Engine 1.3.2 CD-ROM, you will find the cnsce.linux.v1.3.2.tar file, which you can use for your upgrade. Or, you can simply mount the CD-ROM itself on a system running Cisco CNS Configuration Engine 1.3.1; the upgrade script can be run from the upgrade subdirectory (see "How to Use the CD-ROM" section).

How to Use the cnsce.linux.v1.3.2.tar File

Place the cnsce.linux.v1.3.2.tar file in the /root directory of the CNS 2100 Series system by means of SFTP, then enter the following commands:

mkdir upgrade

cd upgrade

tar xvf /root/cnsce.linux.v1.3.2.tar

./upgrade1-3-2.sh

The following message appears:

This script will upgrade CNS Configuration Engine version 1.3.1 to version 1.3.2.

This program will run the setup program. If you do not wish to change any values then just 
hit return through the questions to accept the default/previous answer.

Hit return to continue or ctrl c to abort

How to Use the CD-ROM

Place the Cisco CNS Configuration Engine 1.3.2 CD-ROM in the CD-ROM drive of the CNS 2100 Series system to be upgraded, then enter the following commands:

mount /mnt/cdrom

cd /mnt/cdrom/upgrade

sh upgrade1-3-2.sh

The following message appears:

This script will upgrade CNS Configuration Engine version 1.3.1 to version 1.3.2.

This program will run the setup program. If you do not wish to change any values then just 
hit return through the questions to accept the default/previous answer.

Hit return to continue or ctrl c to abort

Migrating Subject Mappings in Provider Mode of NSM

Cisco CNS Configuration Engine 1.3.2 requires changes in the subject mapping of CNS subjects in the Provider mode of Namespace Mapper. Since the components of the Cisco CNS Configuration Engine will be publishing and subscribing on the new set of CNS subjects (see "New Event Subject Names" section), the subject mappings in the directory must be updated to include the newly introduced CNS subjects.

The directory must contain objects for all the new subjects corresponding to the old subjects that are already populated.

For example, if the subject cisco.cns.config.load is mapped to a.b.c, then you must create an object for the new subject cisco.mgmt.cns.config.load with a mapping of a.b.c.

All the old subjects that are mapped to themselves must be modified to map to the new CNS subjects.

For example, if the subject cisco.cns.config.load was mapped to itself (for example, cisco.cns.config.load), it must now be modified to map to the corresponding new subject, (for example,cisco.mgmt.cns.config.load).

Utility for Automatic Conversion of Subject Mappings

A utility that automates the modification of subject maps in the directory is shipped along with Cisco CNS Configuration Engine Maintenance Release 1.3.2. This utility, called update_subjects performs two main tasks, as listed below.

•If cisco.cns.X is mapped to itself, map it to cisco.mgmt.cns.X.

•If cisco.cns.X is mapped to something else, say xyz, map cisco.mgmt.cns.X to xyz.

This utility works in both internal and external directory modes.

When to Execute the Script

If you upgrade from 1.3.1 to version 1.3.2 using the upgrade script, the update_subjects utility automatically executes and updates the subject mappings.

If the system is a fresh installation of 1.3.2, and you want to migrate all the data from a previous 1.3.1 installation, you must manually execute the script after running the data migration script by entering the following command at the command line:

/opt/CSCOcnsie/bin/update_subjects

Also, you must execute the utility script once in every mode of the Cisco CNS Configuration Engine. For example, if the system was configured in the Internal Directory Mode when update_subjects was run, it must be executed again if the system is configured to run in the External Directory Mode.

---

Note Executed the script just once in each mode.

---

Limitations

The update_subjects script does not accurately migrate subject mappings under one condition. This is when the old CNS subject is mapped both to itself, and to something else.

Example: If cisco.cns.config.load is mapped to itself, (for example, cisco.cns.config.load) AND to a.b.c, the update_subjects utility does not migrate these mappings accurately to cisco.mgmt.cns.config.load.

New Event Subject Names

This section lists the new event subject names that are associated with Cisco IOS 12.3.

CNS Event Agent

cisco.mgmt.cns.event.boot

cisco.mgmt.cns.event.id-changed

CNS Image Agent

cisco.mgmt.cns.image.* - Events related to the image distribution agent

cisco.mgmt.cns.image.checkServerRequest

cisco.mgmt.cns.image.inventoryRequest

cisco.mgmt.cns.image.upgradeRequest

cisco.mgmt.cns.image.status

CNS Exec Agent

cisco.mgmt.cns.exec.* - Events related to exec command-like functions.

cisco.mgmt.cns.exec.cmd

cisco.mgmt.cns.exec.rsp

cisco.mgmt.cns.exec.reload

cisco.mgmt.cns.reloadNotify

CNS Config Agent

cisco.mgmt.cns.config.complete

cisco.mgmt.cns.config.failure

cisco.mgmt.cns.config.warning

cisco.mgmt.cns.config.sync-status

cisco.mgmt.cns.config.reboot - deprecated. Use cisco.mgmt.cns.exec.reload instead. cisco.mgmt.cns.config.load

cisco.mgmt.cns.config.id-changed

cisco.mgmt.cns.config-changed

cisco.mgmt.cns.config-changed.lost

CNS Inventory Agent

cisco.mgmt.cns.inventory.get

cisco.mgmt.cns.inventory.device-details

cisco.mgmt.cns.inventory.oir

CNS Syslog Agent

cisco.mgmt.cns.log.emerg

cisco.mgmt.cns.log.alert

cisco.mgmt.cns.log.crit

cisco.mgmt.cns.log.err

cisco.mgmt.cns.log.warning

cisco.mgmt.cns.log.notice

cisco.mgmt.cns.log.info

cisco.mgmt.cns.log.debug

CNS MIB Access Agent

cisco.mgmt.cns.mibaccess.request

cisco.mgmt.cns.mibaccess.response

cisco.mgmt.cns.mibaccess.notification

cisco.mgmt.cns.snmp.rqst

cisco.mgmt.cns.snmp.resp

cisco.mgmt.cns.snmp.trap

CNS Event Gateway

cisco.mgmt.cns.device.connect

cisco.mgmt.cns.device.disconnect

Legacy Subject Names

The following is a list of all the subject names in use in Cisco IOS releases prior to 12.3, and CNS Configuration Engine release 1.3.2. Starting with release 12.3 of Cisco IOS and release 1.3.2 of the CNS Configuration Engine, the prefix for all of the subjects listed below will be modified from cisco.cns to cisco.mgmt.cns.

Here is the list of subjects names in use prior to IOS 12.3:

cisco.cns.config.complete

cisco.cns.config.failure

cisco.cns.config.warning

cisco.cns.config.sync-status

cisco.cns.config.reboot

cisco.cns.config.load

cisco.cns.config.id-changed

cisco.cns.exec.cmd

cisco.cns.exec.rsp

cisco.cns.inventory.get

cisco.cns.inventory.device-details

cisco.cns.inventory.oir

cisco.cns.config-changed

cisco.cns.config-changed.lost

cisco.cns.event.boot

cisco.cns.event.id-changed

SYSLOG

cisco.cns.log.emerg

cisco.cns.log.alert

cisco.cns.log.crit

cisco.cns.log.err

cisco.cns.log.warning

cisco.cns.log.notice

cisco.cns.log.info

cisco.cns.log.debug

SAA

cisco.cns.slm

cisco.cns.customtrap

MIB Access

cisco.cns.mibaccess.request

cisco.cns.mibaccess.response

cisco.cns.mibaccess.notification

cisco.cns.snmp.rqst

cisco.cns.snmp.resp

cisco.cns.snmp.trap

CNS Event Gateway

cisco.cns.device.connect

cisco.cns.device.disconnect

Resolved Caveats - Maintenance Release 1.3.2

This section lists caveats that have been resolved in release Maintenance Release 1.3.2 (see Table 1 through Table 3).

Table 1 Security 

ID	Problem
CSCea75440	Disable TRACE and/or TRACK methods in Apache.
CSCeb13752	Keeping the Tibco Web Admin port open all the time, is potential security risk. So, by default the http port of the Tibco Web Admin GUI should be closed and it should be opened only when the user runs an open-tibco-web-admin-port script. After the user completes web admin task by accessing the GUI, the http port of the Tibco Web Admin GUI is closed again by running a close-tibco-web-a dmin-port script. This facility enables the user to open the Tibco Web Admin port, only when it is needed and reduces the security risk.

Table 2 NSM

ID	Problem
CSCea76581	Since Cisco IOS has changed its subject names from cisco.cns.* to cisco.mgmt.cns.*, NSM has to be changed to accommodate backward compatibility for the agents in old Cisco IOS images.

Table 3 General 

ID	Problem
CSCdv04599	TibGate getting killed after fetching large number of mappings.
CSCdw58345	The current version of LDAP directory is unable to handle attributes more than 64 characters, which causes internal processes to fail.
CSCdy48788	When the Bulkupload data contains invalid attributes, DAXMLservelet stops working and logs invalid errors. This is a problem in the current LDAP directory version.
CSCdy83389	When 5000 devices try to post their inventory information and connect to Event Gateway upon receiving their configurations, it may take up to an hour before the last configuration is received.
CSCdz76673	The following prompts added to the Setup program for non-interactive setup: Enter log file rotation timer (minutes, 0 = no rotation): [15] Enter max log file size (Kbytes): [3072] Enter the max versions of log file (0-99): [1]
CSCdz81426	Setup can fail and pause indefinitely when a numeric hostname, such as 2110, is used and entered at the network-parameter prompt. The log file /var/log/appliance-setup.log contains errors similar to the followings: 2003-01-10 21:05:50 rvrd: unable to resolve network specification ('2110') 2003-01-10 21:05:50 rvrd: unable to resolve network specification ('2110') It shows that Tibco fails to resolve the numeric hostname for an IP address.
CSCea08252	CNS 2100 Series system should not hard code port numbers (Apache, Tomcat, Tibco).
CSCea80575	Need TACACS+ support.
CSCea81390	No carriage return on multi-line banner when configuration server sent configuration.
CSCea88624	IMGW expect script does not support 6400 NRP2 connection. [Duplicate of CSCea09168]
CSCea89886	If the relocate script is run, the parent attribute of the device, DemoRouter, is not updated with group information.
CSCea09168	IMGW expect script does not support 6400 NRP2 connection.
CSCea92657	LDAP server listening on non-standard port causes NSM problems.
CSCeb01588	Cache should update when directory is updated by means of external applications.
CSCeb11255	IMGW should use port numbers in all its http requests.
CSCeb16858	Update Cisco IOS packages for security updates.

Open Caveats - Maintenance Release 1.3.2

This section lists known caveats that are open for the CNS 2100 Series third-party software (see Table 4), CNS 2100 Series platform (see Table 5), and Maintenance Release 1.3.2 of the Cisco CNS Configuration Engine software application (see Table 6).

Table 4 CNS 2100 Series Third-Party Software 

ID	Problem	Workaround
CSCdv70366	The directory API does not support special characters in device names, such as < & etc. The API does not accept special characters in username or password fields.	When using the Intelligent Modular Gateway feature of the CNS 2100 Series to configure a device by means of Telnet or SSH, it is not possible to use punctuation characters in the username or password for the target device.

Table 5 CNS 2100 Series Platform 

ID	Problem	Workaround
CSCdv85666	When setting up the CNS 2100 Series with the Setup program, if you enter an invalid IP address for the Ethernet0 interface, you are not re-prompted to enter a correct one. This invalid IP address causes network connectivity problems for the unit.	If you accidentally enter an invalid IP address for the Ethernet0 interface, proceed through the rest of Setup program, but do not commit the changes. Then log in as setup again (if the unit has never been configured before) or run the Setup program (if you are updating a previous configuration) and enter the correct values.

Table 6 Cisco CNS Configuration Engine 1.3.2 

ID	Problem	Workaround
CSCdy15293	The reload button in the web-based user interface might not work properly when reload is pressed number of times.	To clear this problem, close and restart the web browser.
CSCdy68363	Under more stressful load where both Event Gateway and Webserver are contending for directory searches (5000 modular router devices each with 5 subdevices), NSM resolve takes a long time to return. During this time, NO keepalive is sent from the Event Gateway to the affected devices. This is a function of the keepalive value configured on the device, which may cause the device to timeout, terminate the current connection, and retry with a new connection.	Configure the device keepalive interval to a value greater than the delay described to prevent devices from prematurely terminating connections.
CSCdy80613	Currently due to limited resources, it takes a long time for all 5,000 devices to receive configuration updates.	Issue updates in staggered waves of 500 devices per wave.
CSCdz14956	Under stress conditions over a period of weeks it has been noticed that the EventMonitor on the GUI stops logging the events.	To restart the EventMonitor log, restart the CNS 2100 Series system.
CSCdz33665	When SSL is turned on and 5,000 devices post their configurations, then connect to the Event Gateway (TibGate) upon receiving their configurations, all 5,000 successfully connect to the Event Gateway. But, if all 5,000 disconnect from the Event Gateway and reconnect, the CNS 2100 Series system experiences out of memory failures and the number of devices that successfully reconnect to the Event Gateway is reduced. The problem gets worse for each subsequent 5,000 disconnect and reconnect sequence.	The number of devices using SSL, either connecting to Apache configuration server or connecting to the Event Gateway (TibGate), should be limited to 3,000 or less.
CSCdz78340	Memory allocation failure: 293 clients could not establish connection with Event Gateway.	None.
CSCdz83000	When IMGW starts, it generates a debug messages. It displays the debug messages a number of times recursively.	None.
CSCdz90247	Not all required property files are backed up during a backup operation. As a result, a subsequent restore operation could fail if the directory password is changed after a backup, by re-running setup.	Do not change the directory password between backup and restore operations.

Obtaining Documentation and Submitting a Service Request

For information on obtaining documentation, submitting a service request, and gathering additional information, see the monthly What's New in Cisco Product Documentation, which also lists all new and revised Cisco technical documentation, at:

http://www.cisco.com/en/US/docs/general/whatsnew/whatsnew.html

Subscribe to the What's New in Cisco Product Documentation as a Really Simple Syndication (RSS) feed and set content to be delivered directly to your desktop using a reader application. The RSS feeds are a free service and Cisco currently supports RSS version 2.0.

This document is to be used in conjunction with the documents listed in the "Related Documentation" section.

Copyright © 2003, Cisco Systems, Inc.
All rights reserved.