release notes for cisco intelligence engine 2100 series … · release notes for cisco intelligence...

Release Notes for Cisco Intelligence Engine 2100 Series Configuration Registrar 1.2

IntroductionThe Cisco Intelligence Engine 2100 Series (IE2100 Series) Configuration Registrar is a network management device that acts as a configuration service for automating the deployment and management of network devices and services. The IE2100 Series is the hardware platform for the Configuration Registrar.

Each Configuration Registrar manages a group of Cisco IOS devices (routers) and services they deliver, storing their configurations and delivering them as needed. The Configuration Registrar automates initial configurations and configuration updates, dynamically generating the device-specific configuration on-demand, and logs the results.

What’s New in this ReleaseThis section highlights the new features found in this release:

• The IE2100 Series platform has changed. It is now based on the IBM xSeries 330 server platform. Refer to the Cisco Intelligence Engine 2100 Series Installation Guide for information about how to install the hardware platform.

• You can now download a non-interactive Setup script from a remote computer, then run it locally to configure your IE2100 Series system.

• The Intelligent Modular Gateway (IMGW) feature now allows you to use the Configuration Registrar to provision devices that run Cisco IOS versions earlier than 12.2(1) T, or other operating systems that do not include the CNS agents.

• The Directory Administration Tool (DAT) allows you to manage data independent of a particular directory service. You can use this tool to load directory data in bulk mode. You can also use DAT to manage NameSpace Mapper (NSM) data, even when the NSM schema has been extended.

Refer to the Cisco Intelligence Engine 2100 Series Configuration Registrar Administrator’s Guide for more information about these feature.

Corporate Headquarters:

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

Cisco Systems, Inc., 170 West Tasman Drive, San Jose, CA 95134-1706 USA

Related Documentation

Related DocumentationOther documentation related to this product include:

• Cisco Intelligence Engine 2100 Series Configuration Registrar Administrator’s Guide

• Cisco Intelligence Engine 2100 Series Installation Guide

• Release Notes for Cisco Intelligence Engine 2100 Series

• Cisco Intelligence Engine 2100 Series Machine Code License

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

• Cisco Networking Services SDK Programmer’s Guide and API Reference

Installation NotesThe Configuration Registrar 1.2 software is contained on a CD-ROM that is in the accessory kit.

To be able to monitor the installation activity and run the Setup program, you should have a local keyboard-mouse and VGA screen connected to your system (see “Console Access” section on page 3).

To install the software, follow these steps:

Step 1 Verify that the IE2100 Series system is powered down.

Step 2 Insert the Configuration Registrar 1.2 CD-ROM in the CD drive (see Figure 1).

Figure 1 Front View

Step 3 Power on the system.

The software installs automatically.

Power controlbutton

Selectbutton/indicator(green)

System errorlight (amber)

Diskette driveactivity light(green)

Diskette ejectbutton

Power-onlight (green)

Resetbutton

CD activitylight (green)

CD eject button

6649

6

2 OL-1953-01

Console Access

Step 4 When prompted to reboot the system, click OK.

The CD-ROM is automatically ejected.

When the install process completes, you will see a login prompt.

Step 5 Refer to the Cisco Intelligence Engine 2100 Series Configuration Registrar Administrator’s Guide to run the Setup program.

Console AccessNormal terminal login to the box is supported by way of the local keyboard-mouse and VGA screen. It is referred to as the VGA console for ease of reference. The IE2100 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 (see Figure 2).

Figure 2 Rear View

Supporting serial port console on the IE2100 Series requires additional instructions. The complexity comes from the fact that although Linux provides the means of setting up the serial port as a console, Linux does not enter the picture until it starts.

The BIOS messages and the table of function keys (F1, F2, F3, and F4) that are displayed before Linux starts always go to VGA console by default. Normally, access of the function keys (F1 to F4) is not an issue unless you need to run system configuration/setup (F1), Diagnostics (F2), or re-image the IE2100 Series using PXEBOOT (network boot) (F4) remotely using the serial port.

How to Redirect BIOS Messages and Functions Keys to the Serial PortRedirecting BIOS messages and function keys to the serial port requires accessing the IE2100 Series internal service processor menu and enabling remote video. In addition, remote video must be enabled before BIOS outputs its first message.

Select light (green)

USB 1

USB 2

C2T (out) port

Ethernet 2 speedindicator (green)

Ethernet 1 speedindicator (green)

Ethernet 1 linkindicator (green)

Ethernet 2 linkindicator (green)

Advanced systemsmanagement RS-485

Serial port

C2T (in) port

System errorlight (amber)

Power-on light(green)

6649

7

3OL-1953-01

Console Access

While connected to the serial port, you can only access the service processor menu during system restart or machine shutdown, since this is the only moment when the IBM service processor is able to reclaim the serial port. Once Linux starts, the connection to service processor is lost since the Linux OS reclaims control of the serial port.

The serial port is operated under the share mode, between the service processor and the OS. Therefore, restarting the system is not sufficient to access the service processor menu because the time between restart and when the BIOS begins is too short to trigger remote video. Instead, shut down the system (see “Restart and Shutdown” section on page 5).

At the end of a system shutdown, the message Hit ESC to log in appears. This is the greeting login message of the service processor. You can gain access to the menu by entering the predefined login name and password of the system. The complete steps for accessing the service processor are outlined as follows:

Step 1 Connect to the serial port of the IE2100 Series (use baud rate = 9600) and login.

Step 2 Shutdown the system using spoff

A value of 50 seconds works well. For more, see “Restart and Shutdown” section on page 5.

Step 3 Once the machine has shutdown and powered off, hit ESC a few times and you should be prompted to enter userid and password of the service processor menu.

Step 4 Enter USERID as the userID and PASSW0RD as the password.

The 0 in the password is the zero digit instead of the alphabetical letter o.

Step 5 In rapid succession, enter the following sequence:

6 4 2 0 ESC z 0

The 6 4 2 0 sequence powers on the machine.

ESC z 0 brings you out of the power-on menu and starts the remote video.

If you wait too long before entering the ESC z 0 sequence, the BIOS begins and you have missed your opportunity to start the remote video.

Note The system must be in the power-off state before entering the key sequence because the remote video must be triggered before the BIOS starts or else you cannot see the BIOS messages or function keys.

There are four function keys.

• F1 for system configuration/setup

• F2 for Diagnostics

• F3 for booting off the System Partition, for rescue purpose (not currently supported)

• F4 for network boot (PXEBOOT)

As soon as the operating system starts, LILO takes control and reconfigures the serial port for Linux use.

4 OL-1953-01

Restart and Shutdown

Restart and ShutdownWhile in Linux, there are two different commands for system restart and shutdown:

• /sbin/shutdown –r now (or reboot) will restart the system. However, you will not be able to access the function keys due to the short time frame available before BIOS and Linux starts.

• For function key access, use the command spoff to power off the system and start remote video by way of the service processor menu (see “Console Access” section on page 3). The value for must be larger than 30 (spoff 50 works well).

Note The spoff command simply powers off the system after seconds.

• It is the IBM Director component wbem that detects the spoff request and triggers the system shutdown sequence, terminating processes and un-mounting file-systems.

If you don’t see a proper shutdown sequence, use ps –ef | grep wbem to see if wbem is running. wbem started with the installation of IBM Director the first time you run Setup. It can be restarted using /etc/rc.d/init.d/init.wbem start.

Migrating DCL Data and Templates from Release 1.1 to Release 1.2

If you have been running the IE2100 Series Configuration Registrar 1.1 system and want to migrate your DCL directory data and templates to your new IE2100 Series Configuration Registrar 1.2 system, follow these steps:

Step 1 Set up an external server to handle FTP tasks between IE2100 Series systems.

Note You cannot FTP directly from one IE2100 system to another.

Step 2 Log in to the Release 1.2 system as root.

Step 3 FTP the cnsexport.sh script from the Release 1.2 system to your FTP server.

Step 4 FTP the cnsexport.sh script from your FTP server to your Release 1.1 system.

Step 5 Log in to the Release 1.1 system as root.

Step 6 Type chmod +x cnsexport.sh to give execution permission to the cnsexport.sh script on the Configuration Registrar 1.1 system.

Step 7 Change directory (cd) to the one for the cnsexport.sh scrip.

Step 8 Type ./cnsexport.sh and wait until the script finishes.

Step 9 Assuming successful completion, a gzipped tar file called cns_export.tar.gz should be found in the /tmp directory.

Step 10 FTP this cns_export.tar.gz file to your FTP server.

Step 11 FTP the cns_export.tar.gz file from your FTP server to your Release 1.2 system.

Step 12 Log in again to the Release 1.2 system as root.

5OL-1953-01

Migrating DCL Data and Templates from Release 1.1 to Release 1.2

Step 13 Type cd /opt/CSCOcnsie/bin to go to the /opt/CSCOcnsie/bin directory.

Step 14 Type cnsimport.sh to execute the cnsimport.sh script. The variable is the absolute path to the cns_export.tar.gz file.

Step 15 Assuming successful completion, use either administrator’s user interface or the DAT user interface (refer to the Cisco Intelligence Engine 2100 Series Configuration Registrar Administrator’s Guide) to verify that data is ported properly.

Importing Groups and Devices from Release 1.1 to 1.2In IE2100 Series Configuration Registrar 1.1 all devices are stored in the DCL directory in the Internal Directory (Standalone) mode. In this configuration, the only NSM mode supported is default:// mode.

In IE2100 Series Configuration Registrar 1.2, Internal Directory mode, all NSM modes (none://, default://, and http:// algo/non-algo) are supported.

When you import groups from a Release 1.1 system to a Release 1.2 system, and the Release 1.2 system is setup in NSM default:// mode, devices in the default group and imported groups can receive configurations sent to them. However, when the Release 1.2 system is setup in the NSM http:// mode, sending events to the imported groups (non-default groups) fail.

For imported groups to work in Release 1.2 (NSM http:// mode), you must create a reference for the imported group to an application namespace. The reason is, that NSM http:// mode was not available in Release 1.1 Internal Directory (Standalone) mode.

The value for the application namespace is set during Setup with the prompt:

Enter the Event Gateway Application Parameter:

By default value for this parameter is config. You can override this value during Setup with one of your own.

To create the reference to an application namespace (config by default) for an imported group, follow these steps:

Step 1 Log in to your Release 1.2 system user interface.

Refer to the Cisco Intelligence Engine 2100 Series Configuration Registrar Administrator’s Guide.

Step 2 Click on Tools.

Step 3 Click on DAT.

Step 4 Log in to DAT.

Step 5 From DAT main menu, click on Groups.

Step 6 From the Groups Management page, click Update Groups.

Step 7 Select the group to which you want to add the application reference to config.

Note If during Setup, you set a value other than config for the Event Gateway Application Parameter, use this value when setting the application reference.

Step 8 Check the check box for config.

6 OL-1953-01

How to Revert to Factory Setting

Step 9 Click Add.

How to Revert to Factory SettingTo revert to factory settings, follow these steps:

Step 1 Initiate a system backup.

For information about backup, Refer to the Cisco Intelligence Engine 2100 Series Configuration Registrar Administrator’s Guide.

Step 2 Log in as root.

Use your root password.

Step 3 Type reinitialize.

This program clears your system configuration and returns you to Setup.

How to Reconfigure System Network InformationTo reconfigure system network information, follow these steps:

Step 1 Log in as root.

Use your root password.

Step 2 Type relocate.

This program performs the same tasks as reinitialize, except that it backs up all data that you can restore when you run Setup.

Hostname UpdatesIf you want to change the hostname, country code, or location code without destroying the DCL data and templates, use the relocate command. You can use the relocate command in both internal (user-created devices and templates) and external (IMGW data) directory modes.

Router ConfigurationFor a router to pick up its initial configuration from the Configuration Registrar, install the Configuration Registrar before installing a router. Then establish a connection between the router and the Configuration Registrar. Special Cisco IOS images are available for download. Please contact your primary Cisco contact to obtain special Cisco IOS images.

7OL-1953-01

Limitations and Restrictions

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

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

Open Caveats - Release 1.0This section lists known caveats that were open for the IE2100 Series platform (see Table 1) and release 1.0 of the Configuration Registrar software application (see Table 2).

Table 1 IE2100 Series Platform

ID Problem Workaround

CSCdt16330 The setup program does not update the /etc/hosts and /opt/CSCOcnsie/conf/ldaputil.properties files.

Setup is used only at initial configure time. To reuse setup, you must first run the configure or ResetConfig commands. Before you run these commands, export system data, then import it back into the system after setup completes.

CSCdt33902 When recovering from a power-down condition, the system does not boot from flash as it should. The system halts when it reaches a point in the boot sequence where it displays the message: No boot device found.

To recover from this situation, cycle the system power off and on. The system boots from flash as it should.

CSCdt33906 When system power is cycled off and on during the boot process, the system goes into a state of limited command access.

To recover from this situation, cycle the system power off and on. The system boots from flash as it should.

CSCdt33917 When reconfiguring the system after a ResetConfig operation, the system reports numerous SCSI errors.

To recover from this situation, cycle the system power off and on.

CSCdt33930 Setup AdminID has same first and last name in directory.

This is a data display problem and does not affect the operation of the system.

CSCdt34494 Network Time Protocol (NTP) time service is not configured and not running on device.

Date and time values must be set up by the user on site. NTP is just one method of setting date and time values on the system. Please refer to UNIX documentation for information about how to use the NTP service.

CSCdt53937 Ethernet port-0 parameters must be specified in during Setup.

Ethernet port-0 is the primary Ethernet port. Ethernet port-1 has access only to a local subnet.

CSCdt58634 Gateway for second Ethernet card is not functional.

The IE2100 Series Configuration Registrar software supports only LAN and WAN connections on Ethernet port-0. Ethernet port-1 can be used only to access a local subnet. The gateway for the second Ethernet port is not valid.

CSCdt77468 The console port does not reset correctly.

You should set up communication servers to turn off the login prompt to the IE2100 Series. For Cisco communication servers, use the no exec setting on the line that to which the IE2100 Series is attached. Also, set flow control to hardware.

8 OL-1953-01

Open Caveats - Release 1.0

CSCdt89830 Configuration templates are not secure.

The IE2100 Series has no user-level security. Once the user is logged into the system, there is no permission checking. Please restrict login access to the system.

CSCdt93713 The rootenable password can be set only once; the first time you run it.

To change the root password, while logged in as root, run the UNIX passwd command. You should run the rootenable command only when the root account is disabled; for example, following setup on a fresh install.

CSCdu08322 Extraneous error messages when reinstalling IE2100 Series system software.


CSCdu08328 Extraneous error messages when running ResetConfig.


CSCdu08333 Extraneous error messages when rebooting the IE2100 Series. The following error messages can be ignored: Initializing system files [FAILED]Version fork

errorflashed: error reading from

flash […]cat: /etc/issue.sav: No

such file or directory


CSCdu17412 The runtime.properties file needs to be backed up.

If you are extending the schema and are using the OIDs provided by Cisco Systems, keep track of the OIDs used in the runtime.properties file. This file is located in the /opt/CSCOcnsie/conf directory. This file is NOT backed up by means of the current backup script. You should backup this file and restore it when upgrading or reconfiguring the IE2100 Series system software.

Table 2 Configuration Registrar 1.0


CSCds88082 Active tab does not change color on Netscape browser.


CSCds91645 Error message on initial template load.

Because of a timing issue between the applet and JavaScript, the system displays an error message the first time the applet loads. When this message shows, click on the same link again for normal operation.

CSCdt60040 Reload button resends events.Reloading a page that is generated due to a form submission causes the form to be resubmitted. After sending an event, such as Update Device, and reviewing the event on the “Events have been sent” page, if you click the web browser reload button, the event is sent again.

Because the reload function in the browser cannot be controlled programatically, the workaround is to avoid using the reload function. To navigate through the Configuration Registrar, use the links built into the user interface.

Table 1 IE2100 Series Platform (continued)


9OL-1953-01


CSCdt78738 The View Device operation does not update edited group names.

The workaround for this problem is to delete the group that you want to edit, then create a new group with the required updates.

CSCdt93814 JServ intermittently dies during high-volume (~500) partial configuration operations.

Under these circumstances, JServ usually recovers on its own. However, if you get an internal server error message, click Reload for the browser, then click the link again.

CSCdu01134 Button names do not match for Administrator and Operator. On the Change-Password screen for the Administrator, the Edit button performs the same function as the Save button on the Change-Password screen for the Operator.


CSCdu01202 Incorrect message even when no device reference is added or deleted.


CSCdu03717 Invalid time value accepted for Schedule Backup cron job.

The time must be in hh:mm format with valid values for hh of 00-23 and mm of 00-59.

CSCdu04538 Event message window does not handle warning messages.

If a Cisco IOS device sends a warning message, the event window shows the message as [Internal] rather than WARN. If you click detail, the warning message can be read. Event functionality for detecting warnings from devices is functional.

CSCdu05946 Blank template filename is allowed when saving a file.

The template filename parameter value cannot be NULL. You must enter some value in this field.

CSCdu15257 Editing a template file greater than 24Kb causes Netscape on Solaris to crash.

Currently, Solaris 2.6 and 2.7 have a limitation regarding file size. This problem does not pertain to Netscape on the Microsoft Windows platform.

CSCdu17428 Attributes list contains IOSConfigID. The IOSConfigID attribute in the drop-down list in the Edit Template page should not be used in normal operations. It is reserved for future product development.

CSCdu24659 Need to delete device to remove the value in IOShostname, if used.If, when you create a template, you include the IOShostname attribute, then later, you edit this parameter, updates to this device will go unanswered. This is because the device looks for the DeviceID associated with the IOShostname parameter set earlier.

The workaround for this problem is to delete the device in question, then add it back with the updated values.

Table 2 Configuration Registrar 1.0 (continued)


10 OL-1953-01

Resolved Caveats - Release 1.1

Resolved Caveats - Release 1.1This section lists caveats that were resolved for the IE2100 Series platform (see Table 3) and release 1.1 of the Configuration Registrar software application (see Table 4).


ID Description

CSCdt16330 The setup program does not update the /etc/hosts and /opt/CSCOcnsie/conf/ldaputil.properties files.

CSCdt33902 When recovering from a power-down condition, the system does not boot from flash as it should.

CSCdt33906 When system power is cycled off and on during the boot process, the system goes into a state of limited command access.

CSCdt33917 When reconfiguring the system after a ResetConfig operation, the system reports numerous SCSI errors.

CSCdt33930 Setup AdminID has same first and last name in directory.

CSCdt34494 Network Time Protocol (NTP) time service is not configured and not running on device.

CSCdt53937 Ethernet port-0 parameters must be specified in during Setup.

CSCdt58634 Gateway for second Ethernet card is not functional.

CSCdt77468 The console port does not reset correctly.

CSCdt89830 Configuration templates are not secure.

CSCdt93713 The rootenable password can be set only once; the first time you run it.

CSCdu08322 Extraneous error messages when reinstalling IE2100 Series system software.

CSCdu08328 Extraneous error messages when running ResetConfig.

CSCdu08333 Extraneous error messages when rebooting the IE2100 Series.

CSCdu17412 The runtime.properties file needs to be backed up.


ID Description

CSCds88082 Active tab does not change color on Netscape browser.

CSCds91645 Error message on initial template load.

CSCdt60040 Reload button resends events.

CSCdt78738 The View Device operation does not update edited group names.

CSCdu01134 Button names do not match for Administrator and Operator.

CSCdu01202 Incorrect message even when no device reference is added or deleted.

CSCdu03717 Invalid time value accepted for Schedule Backup cron job.

CSCdu04538 Event message window does not handle warning messages.

CSCdu05946 Blank template filename is allowed when saving a file.

CSCdu17428 Attributes list contains IOSConfigID.

11OL-1953-01


Open Caveats - Release 1.1This section lists known caveats that were open for the IE2100 Series platform (see Table 5) and release 1.1 of the Configuration Registrar software application (see Table 6).



CSCdu77514 ldaputil.properties shows groupOfNames as Group object class. In general, groupOfNames is used by LDAP servers as a method of grouping. The Configuration Registrar uses groupOfNames ObjectClass in its grouping mechanism. If it is necessary, you can use your own group object class as long as two multi-value attributes exist in that object class: member (this can be changed as well) and seealso.

Once you decide to use your own object class in Group, you need to modify the ldaputil.properties file by following these steps:

1. Use console access to the IE2100 and login as root.

2. Go to the /opt/CSCOcnsie/conf directory.

3. Edit the ldaputil.properties file.

4. Find the GroupObjectClassName entry:

GroupObjectClassName=groupOfNames

5. Erase groupOfNames and put in . where your new object class name is represented here as to yield:

GroupObjectClassName=

6. Find the MemberAttributeName entry and change it if necessary.

7. Save the changes in ldaputil.properties.

8. Restart the httpd server.

Now, the Configuration Registrar is using your new group object name to search for groups.

Caution The Configuration Registrar fails to operate in standalone mode if you perform mode-switching from Server mode to Standalone mode after performing this procedure.

12 OL-1953-01


CSCdu84805 Downloading a new image times out.

If the IE2100 had been previously configured for Ethernet port-1 and you try to upgrade or reimage your system using BldSetup.sh, the script, which uses Ethernet port-0 information is not able to pass on network information. If Ethernet port-0 is not configured, BldSetup.sh quits with a message asking you to setup your system with Ethernet port-0 first, then run the script.

Workaround One

If your system goes to manual installation of Linux (prompted menu) during the running of BldSetup.sh, you can revert to your previous successful installation by following these steps:

1. Manually restart your system (stop and start).

During initial stages of startup you will see the prompt, LILO: The system waits for about 3-5 seconds here at this prompt.

2. When you see the LILO: prompt press the Tab key.

All the available lilo configurations display separated by spaces in a single line. You should see RM-Install IE-2100.

If you do not see IE-2100 then you did not have a successful installation before you started to run BldSetup.sh script. Go to Workaround Two.

3. If you can see IE-2100 then type IE-2100 at the prompt, then press Enter.

This loads up your previous successful configuration.

4. Now run Setup to configure your system again.

Make sure you give proper values to Ethernet port-0.

5. Run the BldSetup.sh (web server update process).

Workaround Two

Restart you system from flash and use reimage to reimage your system. Do not use it as your first option. Try Workaround One a few times before using this option.

CSCdv09284 Primary and Secondary DNS IP address fields reversed.

It is known that the order of primary DNS and secondary DNS are reversed when they are entered into the /etc/resolv.conf file. As a result, the intended secondary DNS becomes the primary DNS and the intended primary DNS becomes the secondary DNS.

The way to work around this problem is to enter the two DNS IP addresses at the Setup program in reverse order: Enter the secondary DNS address when prompted for primary DNS and vice versa.

Note This workaround is only needed when two DNS are used. If one DNS is used, simply enter your DNS address at the primary DNS prompt.



13OL-1953-01


CSCdv15180 Standalone configuration history lost when reinitialize not run between Setup sessions.

When the Server mode Setup is run multiple times without running reinitialize between sessions, the Standalone mode configuration history is lost and the Configuration Registrar is not able to completely uninitialize the Server mode.

To workaround this problem, follow these steps:

1. Go to the /opt/CSCOcnsie/conf/ldaputil.properties file and set the following values:

Container=ou=IOSConfigsContextRoot=ou=NSMGroupsGroupContainer=ou=AppGroups

2. Run Setup again.




Under these circumstances, JServ usually recovers on its own. However, if you get an internal server error message, click Reload for the browser, then click the link again.

CSCdu15257 Editing template files larger than 24Kb causes Netscape on Solaris to crash.

The Edit Template page currently has a 25Kb size limitation in Solaris 2.6 and 2.7; not on the Microsoft Windows platform. If the file exceeds this limit, Netscape on solaris crashes. This is not a size limitation on configurations for Cisco IOS Devices.

CSCdu24659 You have to delete the device to remove the parameter value in IOShostname, if used. If, when you create a template to remove the value in IOShostname attribute, then later, you edit this parameter, update to this device goes unanswered. This is because the device looks for the DeviceID associated with the IOShostname parameter set earlier.

The workaround for this problem is to delete the device in question, then add it back with the updated value.

CSCdu78255 Error on Edit Schema is persistent. The schema editor keeps the history of all the attributes added during a session. Therefore, any failure operation invalidates the following operations on the Editor.

The workaround is to start a new session by logging out and in again to clear the history.

CSCdu86428 Macros not working correctly in nested templates.

Macros are not supported in this release.

CSCdv02418 DCL limits adding more than 80 references to a group at one time.

If you select 80 devices or less to add to a group, there is no problem. If you want to add more than 80 devices to a group, you can add these devices in two, or more, separate transactions. The only limitation is adding 80 devices per transaction to a group.



14 OL-1953-01


CSCdv03801 Undo last schema update gives error. When undoing a last schema edit or reverting the schema to install state, the schema fails to reload. The following error message displays:

/opt/CSCOcnsie/html/../scripts/restorelastschema:/opt/CSCOcnsie/scripts/dclschemaload.txt: Permission denied.

This message means that the script dclschemaload.txt could not be executed due to insufficient access permission. The schema was undone or reverted successfully but that schema was not reloaded afterwards.

To reload the schema, go to Tools --> Directory Manager --> Reload schema and the schema reloads. To prevent this problem from occurring again, login to the IE2100 Series system as root and grant global execute permission to the following script:chmod +x /opt/CSCOcnsie/scripts/dclschemaload.txt

CSCdv05016 Initial configuration load for 500 devices fails intermittently.

Intermittent failure of an initial configuration download to the router may occur when the configuration file size is greater than 24k. Subsequent retries should be successful. The root cause of this failure is a JServ timeout (see CSCdt93814, page 14).

CSCdv11082 Issue with device update when Template attribute is NULL.

It is a requirement that the value of the template file attribute not be NULL when creating a new device.

CSCdv11084 Issue with device update when the Template attribute is missing.

It is a requirement that there be a value present for the template file attribute when creating a new device.

CSCdv11098 Issue with device update when group is selected.

It is a requirement that there be a value present for the Group attribute when creating a new device.



15OL-1953-01


Resolved Caveats - Release 1.2This section lists caveats that have been resolved for the IE2100 Series platform (see Table 7) and release 1.2 of the Configuration Registrar software application (see Table 8).

.Table 7 IE2100 Series Platform

ID Problem

CSCdu84805 Downloading a new image times out.

If the IE2100 had been previously configured for Ethernet port-1 and you try to upgrade or reimage your system using BldSetup.sh, the script, which uses Ethernet port-0 information is not able to pass on network information. If Ethernet port-0 is not configured, BldSetup.sh quits with a message asking you to setup your system with Ethernet port-0 first, then run the script.

CSCdv09284 Primary and Secondary DNS IP address fields reversed.

It is known that the order of primary DNS and secondary DNS are reversed when they are entered into the /etc/resolv.conf file. As a result, the intended secondary DNS becomes the primary DNS and the intended primary DNS becomes the secondary DNS.

CSCdv15180 Standalone configuration history lost when reinitialize not run between Setup sessions.

When the Server mode Setup is run multiple times without running reinitialize between sessions, the Standalone mode configuration history is lost and the Configuration Registrar is not able to completely uninitialize the Server mode.


ID Problem


CSCdu15257 Editing template files larger than 24Kb causes Netscape on Solaris to crash.

CSCdu24659 You have to delete the device to remove the parameter value in IOShostname, if used. If, when you create a template to remove the value in IOShostname attribute, then later, you edit this parameter, update to this device goes unanswered. This is because the device looks for the DeviceID associated with the IOShostname parameter set earlier.

CSCdu78255 Error on Edit Schema is persistent. The schema editor keeps the history of all the attributes added during a session. Therefore, any failure operation invalidates the following operations on the Editor.

CSCdu86428 Macros not working correctly in nested templates.

CSCdv02418 DCL limits adding more than 80 references to a group at one time.

16 OL-1953-01


CSCdv03801 Undo last schema update gives error. When undoing a last schema edit or reverting the schema to install state, the schema fails to reload. The following error message displays:

/opt/CSCOcnsie/html/../scripts/restorelastschema:/opt/CSCOcnsie/scripts/dclschemaload.txt: Permission denied.

This message means that the script dclschemaload.txt could not be executed due to insufficient access permission. The schema was undone or reverted successfully but that schema was not reloaded afterwards.

CSCdv05016 Initial configuration load for 500 devices fails intermittently.

CSCdv11082 Issue with device update when Template attribute is NULL.

CSCdv11084 Issue with device update when the Template attribute is missing.

CSCdv11098 Issue with device update when group is selected.


ID Problem

17OL-1953-01


Open Caveats - Release 1.2This section lists known caveats that are open for the IE2100 Series platform (see Table 9) and release 1.2 of the Configuration Registrar software application (see Table 10).



CSCdu77514 ldaputil.properties shows groupOfNames as Group object class. In general, groupOfNames is used by LDAP servers as a method of grouping. The Configuration Registrar uses groupOfNames ObjectClass in its grouping mechanism. If it is necessary, you can use your own group object class as long as two multi-value attributes exist in that object class: member (this can be changed as well) and seealso.

Once you decide to use your own object class in Group, you need to modify the ldaputil.properties file by following these steps:

1. Use console access to the IE2100 and login as root.

2. Go to the /opt/CSCOcnsie/conf directory.

3. Edit the ldaputil.properties file.

4. Find the GroupObjectClassName entry:

GroupObjectClassName=groupOfNames

5. Erase groupOfNames and put in . where your new object class name is represented here as to yield:

GroupObjectClassName=

6. Find the MemberAttributeName entry and change it if necessary.

7. Save the changes in ldaputil.properties.

8. Restart the httpd server.

Now, the Configuration Registrar is using your new group object name to search for groups.

Caution The Configuration Registrar fails to operate in standalone mode if you perform mode-switching from Server mode to Standalone mode after performing this procedure.

CSCdv85666 When setting up the IE2100 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.

CSCdv85681 The Setup program accepts invalid value for domain name.

When setting up the IE2100 Series, it is important to enter the domain name properly. No validation is done on the input, so if you find that the domain name was entered incorrectly, it is necessary to run The Setup program again and correct the error.

18 OL-1953-01


CSCdv90816 In the Linux operating system, the two Ethernet interfaces are defined as Ethernet0 and Ethernet1. The user is presented with this nomenclature when configuring and using these two interfaces.

The labelling on the IBM x330 hardware shows the two Ethernet interfaces as Ethernet1 and Ethernet2.

In the IE2100 Series, the hardware is labeled with ports Ethernet 1 and Ethernet 2. The software identifies these ports as Ethernet 0 and Ethernet 1.

Ethernet 1 on the hardware label refers to Ethernet 0 in the software.

Ethernet 2 on the hardware label refers to Ethernet 1 in the software.

CSCdw31205 If the serial port is not connected, reboot or shutdown -r now does not reboot the system.

This condition can also cause problems (hard disk corruption) when powering off the system using spoff 50 because file-system buffers are not flushed.

For reboot:

Issue the command: reboot -f. This bypasses the invocation of shutdown.

Or, connect the serial port before using reboot.

For powering off the system:

Run the following command sequence:

syncsyncspoff 50

Repeating the sync command flushes the file-system buffers forcing changed blocks from memory to disk. Then use spoff 50 to power off the system.

Or, connect the serial port before using spoff 50.

CSCdw37062 Reinitialize is still required when switching over to a different external directory. If you do not run reinitialize and just run the Setup program and point it to another external directory you are not be able to log into the config server.

When reconfiguring the IE2100 Series from using one external directory type to another (such as changing from NDS to iPlanet), the unit does not operate correctly.

The workaround is to backup your data, run reinitialize to reset to factory settings, log in as setup and configure the unit for the new external directory type, and then restore your data.

CSCdw46662 In the Setup program, the prompt Enter the Event Gateway Debug Log does not adequately explain what the Setup program is asking for.

The Setup program means to ask Enable event gateway debugging (y/n)?

Respond with y or n.

CSCdw65776 If you configure the IE2100 Series for External Directory mode and you do not use the sample schema, you will be prompted for the elements of your schema. It is important when setting up your own schema to put the Namespace Mapper group context under the CNS context. No checking is done for this requirement, but if this requirement is not satisfied, you will not be able to view or update any devices in the user interface.

Run the Setup program again and configure a proper Namespace Mapper group context.



19OL-1953-01


CSCdw84222 The command show version was used for displaying the software versions on the system in the previous releases. This command is not yet removed from the system, but it is obsolete. The output should be ignored.

Use the new command showversion.

CSCdw85170 When you change the Admin account, then run relocate or reinitialize, the Admin account is corrupted.

This occurs because of a problem in redefining the Linux administrator account username in Setup.

Run relocate or reinitialize before changing the administrator username.

For example, the administrator username Admin has been created in Setup. To change the administrator username from Admin to Smith, follow these steps:

Step 1Run reinitialize.

This deletes the account for Admin, including the group name.

Warning Use reinitialize with caution. Running reinitialize erases all data files you have created, returning the system back to factory settings.

Step 2Re-run Setup to define the administrator username to Smith.



CSCdu85243 The Search functionality is inconsistent.

On the screens View Device, Edit Device, Delete Device, Update Device, Edit User, Delete User and Order Entry, the search is wildcard-enabled and case-insensitive. Also, the search string is not shown along with the search results.

On the Tools->View Logs->Events Log screen, the search is not wildcard-enabled and is case-sensitive. The search string is shown along with the search results.

CSCdv04599 TibGate getting killed after fetching large number of mappings.

When using the Namespace Mapper feature, there is a limitation of 150 mappings per subject name. If more than 150 mappings are provided, the CNS Event Gateway stops functioning.

Limit the number of mappings per subject name to 150.



20 OL-1953-01


CSCdv05930 Tools->Directory Manager->Edit Schema The Unique ID for this attribute is editable. Any value can be given to this attribute. Since this value is OID for this attribute it should follow the standards used for creating OIDs.

When adding items to the schema of the Cisco Configuration Registrar, it is important that the values for the Unique ID actually be unique. No checking is done to ensure that they really are unique. An attempt to add an item with the same ID as a previous item results in the schema failing to reload from that point forward.

The workaround is to revert to the factory schema and re-do any modifications made since then.

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

CSCdw37706 All users can be deleted using Configuration Registrar user interface.

It is possible to use the delete user functionality in the web-based user interface to remove users with administrator access. If all users with administrative access are removed, it is no longer possible to log into the user interface with administrator privileges.

The workaround is to run reinitialize to revert to factory settings, set up the unit again, and then restore your data from your last backup.

CSCdw58345 When creating, then deleting a DeviceID longer than 64 characters, DCL crashes.

Do not create any user-specified identifier (such as a DeviceID) that is longer than 64 characters. Such identifiers causes internal processes to fail.

CSCdw62131 If the operational mode is changed from Internal Directory mode to External Directory mode, the application container name of ldaputil.properties is not modified to point to the external directory server application container. It remains pointed to the internal directory application container, which is ou=ConfigApp.

When reconfiguring the Configuration Registrar from using Internal Directory mode to External Directory mode, the Directory Administration Tool does not function.

The workaround is to backup your data, run reinitialize to reset to factory settings, run setup to configure for External Directory mode, and then restore your data.

CSCdw67505 java.lang.outofmemory error with Internal Directory mode.

When using the web-based user interface for Configuration Registrar administration for Internal Directory mode, you cannot display 5000 devices simultaneously in the Configuration Server and the Directory Administration windows.

If you want to display devices in both windows simultaneously, the limit on number of devices that display is 4000. 5000 devices can still be supported if only one management window is displaying devices at a time.

Note This does not affect the use of the IE2100 Series as a programmable network element without using the web-based user interface. In that case, 5000 devices are always supported.



21OL-1953-01


CSCdw83530 No warning given to user when reverting back to original schema.

Be careful when choosing to revert the schema back to the original schema. If there are any devices that are actually using new schema elements that were not in the original schema, those devices become unusable if you revert to the original schema.

Therefore, customers who have extended their schema and have actually used new schema elements in device objects should not revert to the original schema.

CSCdw84916 Device update fails when the uniquedeviceid and uniqueconfigid of the device are different.

In External Directory mode, it is important to set the DeviceID of each object to match its ConfigID. This is the default behavior, but it can be changed. If the DeviceID of an object does not match its ConfigID, you are not able to access that device from the Configuration Registrar user interface.

This also means that IOS devices must be careful when they use the cns id command to change their IDs from the default of the device hostname. If they use the cns id command, they must also use the cns id ... event command so the IDs match.

CSCdw89165 DAT allows addition of device with same cn= in different containers.

It is important to make all device IDs in the system unique. It is possible, using the Directory Administration Tool, to create duplicate device IDs if they are in different containers from namesakes that have already been created.

This should not be done, because the software does not operate properly when you try to update the device using the Configuration Registrar.

CSCdw89291 Inconsistent behavior in View and Update screen when template is invalid.

It is important to specify template attributes for device objects with a value ending in .cfgtpl.

If the template value does not end in .cfgtpl, inconsistent behavior (such as being unable to update the device) will result.

CSCdx01553 The TibGate log in /var/log/CNS/TibGateLog uses up the full space allocated to the partition in two days.

The Event Gateway debugging option should only be enabled for short periods of time (less than one day). The reason is that the log will exhaust available disk space within two days of the debugging being turned on.

In addition, after the debugging log has been captured, the debugging log should be turned off (by running setup again), and then the files in /opt/CSCOcnsie/logs should be cleaned up.



22 OL-1953-01

Obtaining Documentation

Obtaining DocumentationThe following sections explain how to obtain documentation from Cisco Systems.

World Wide WebYou can access the most current Cisco documentation on the World Wide Web at the following URL:

http://www.cisco.com

Translated documentation is available at the following URL:

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

Documentation CD-ROMCisco documentation and additional literature are available in a Cisco Documentation CD-ROM package, which is shipped with your product. The Documentation CD-ROM is updated monthly and may be more current than printed documentation. The CD-ROM package is available as a single unit or through an annual subscription.

Ordering DocumentationCisco documentation is available in the following ways:

• Registered Cisco.com users (Cisco direct customers) can order Cisco product documentation from the Networking Products MarketPlace:

http://www.cisco.com/cgi-bin/order/order_root.pl

• Registered Cisco.com users can order the Documentation CD-ROM through the online Subscription Store:

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

• Nonregistered Cisco.com users can order documentation through a local account representative by calling Cisco corporate headquarters (California, USA) at 408 526-7208 or, elsewhere in North America, by calling 800 553-NETS (6387).

Documentation FeedbackIf you are reading Cisco product documentation on Cisco.com, you can submit technical comments electronically. Click the Fax or Email option under the “Leave Feedback” at the bottom of the Cisco Documentation home page.

You can e-mail your comments to [email protected].

23OL-1953-01

http://www.cisco.comhttp://www.cisco.com/public/countries_languages.shtmlhttp://www.cisco.com/cgi-bin/order/order_root.plhttp://www.cisco.com/go/subscription

Obtaining Technical Assistance

To submit your comments by mail, use the response card behind the front cover of your document, or write to the following address:

Cisco SystemsAttn: Document Resource Connection170 West Tasman DriveSan Jose, CA 95134-9883

We appreciate your comments.

Obtaining Technical AssistanceCisco provides Cisco.com as a starting point for all technical assistance. Customers and partners can obtain documentation, troubleshooting tips, and sample configurations from online tools by using the Cisco Technical Assistance Center (TAC) Web Site. Cisco.com registered users have complete access to the technical support resources on the Cisco TAC Web Site.

Cisco.comCisco.com is the foundation of a suite of interactive, networked services that provides immediate, open access to Cisco information, networking solutions, services, programs, and resources at any time, from anywhere in the world.

Cisco.com is a highly integrated Internet application and a powerful, easy-to-use tool that provides a broad range of features and services to help you to

• Streamline business processes and improve productivity

• Resolve technical issues with online support

• Download and test software packages

• Order Cisco learning materials and merchandise

• Register for online skill assessment, training, and certification programs

You can self-register on Cisco.com to obtain customized information and service. To access Cisco.com, go to the following URL:


Technical Assistance CenterThe Cisco TAC is available to all customers who need technical assistance with a Cisco product, technology, or solution. Two types of support are available through the Cisco TAC: the Cisco TAC Web Site and the Cisco TAC Escalation Center.

Inquiries to Cisco TAC are categorized according to the urgency of the issue:

• Priority level 4 (P4)—You need information or assistance concerning Cisco product capabilities, product installation, or basic product configuration.

• Priority level 3 (P3)—Your network performance is degraded. Network functionality is noticeably impaired, but most business operations continue.

24 OL-1953-01



• Priority level 2 (P2)—Your production network is severely degraded, affecting significant aspects of business operations. No workaround is available.

• Priority level 1 (P1)—Your production network is down, and a critical impact to business operations will occur if service is not restored quickly. No workaround is available.

Which Cisco TAC resource you choose is based on the priority of the problem and the conditions of service contracts, when applicable.

Cisco TAC Web Site

The Cisco TAC Web Site allows you to resolve P3 and P4 issues yourself, saving both cost and time. The site provides around-the-clock access to online tools, knowledge bases, and software. To access the Cisco TAC Web Site, go to the following URL:

http://www.cisco.com/tac

All customers, partners, and resellers who have a valid Cisco services contract have complete access to the technical support resources on the Cisco TAC Web Site. The Cisco TAC Web Site requires a Cisco.com login ID and password. If you have a valid service contract but do not have a login ID or password, go to the following URL to register:

http://www.cisco.com/register/

If you cannot resolve your technical issues by using the Cisco TAC Web Site, and you are a Cisco.com registered, you can open a case online by using the TAC Case Open tool at the following URL:

http://www.cisco.com/tac/caseopen

If you have Internet access, it is recommended that you open P3 and P4 cases through the Cisco TAC Web Site.

Cisco TAC Escalation Center

The Cisco TAC Escalation Center addresses issues that are classified as priority level 1 or priority level 2; these classifications are assigned when severe network degradation significantly impacts business operations. When you contact the TAC Escalation Center with a P1 or P2 problem, a Cisco TAC engineer will automatically open a case.

To obtain a directory of toll-free Cisco TAC telephone numbers for your country, go to the following URL:

http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml

Before calling, please check with your network operations center to determine the level of Cisco support services to which your company is entitled; for example, SMARTnet, SMARTnet Onsite, or Network Supported Accounts (NSA). In addition, please have available your service agreement number and your product serial number.

25OL-1953-01

http://www.cisco.com/tachttp://www.cisco.com/register/http://www.cisco.com/tac/caseopenhttp://www.cisco.com/warp/public/687/Directory/DirTAC.shtml


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

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

26 OL-1953-01

Release Notes for Cisco Intelligence Engine 2100 Series Configuration Registrar 1.2IntroductionWhat’s New in this ReleaseRelated DocumentationInstallation NotesConsole AccessHow to Redirect BIOS Messages and Functions Keys to the Serial Port

Restart and ShutdownMigrating DCL Data and Templates from Release 1.1 to Release 1.2Importing Groups and Devices from Release 1.1 to 1.2

How to Revert to Factory SettingHow to Reconfigure System Network InformationHostname UpdatesRouter ConfigurationLimitations and RestrictionsOpen Caveats - Release 1.0Resolved Caveats - Release 1.1Open Caveats - Release 1.1Resolved Caveats - Release 1.2Open Caveats - Release 1.2Obtaining DocumentationWorld Wide WebDocumentation CD-ROMOrdering DocumentationDocumentation Feedback

Obtaining Technical AssistanceCisco.comTechnical Assistance CenterCisco TAC Web SiteCisco TAC Escalation Center

/ColorImageDict > /JPEG2000ColorACSImageDict > /JPEG2000ColorImageDict > /AntiAliasGrayImages false /CropGrayImages true /GrayImageMinResolution 300 /GrayImageMinResolutionPolicy /OK /DownsampleGrayImages true /GrayImageDownsampleType /Bicubic /GrayImageResolution 300 /GrayImageDepth -1 /GrayImageMinDownsampleDepth 2 /GrayImageDownsampleThreshold 1.50000 /EncodeGrayImages true /GrayImageFilter /DCTEncode /AutoFilterGrayImages true /GrayImageAutoFilterStrategy /JPEG /GrayACSImageDict > /GrayImageDict > /JPEG2000GrayACSImageDict > /JPEG2000GrayImageDict > /AntiAliasMonoImages false /CropMonoImages true /MonoImageMinResolution 1200 /MonoImageMinResolutionPolicy /OK /DownsampleMonoImages true /MonoImageDownsampleType /Bicubic /MonoImageResolution 1200 /MonoImageDepth -1 /MonoImageDownsampleThreshold 1.50000 /EncodeMonoImages true /MonoImageFilter /CCITTFaxEncode /MonoImageDict > /AllowPSXObjects false /CheckCompliance [ /None ] /PDFX1aCheck false /PDFX3Check false /PDFXCompliantPDFOnly false /PDFXNoTrimBoxError true /PDFXTrimBoxToMediaBoxOffset [ 0.00000 0.00000 0.00000 0.00000 ] /PDFXSetBleedBoxToMediaBox true /PDFXBleedBoxToTrimBoxOffset [ 0.00000 0.00000 0.00000 0.00000 ] /PDFXOutputIntentProfile () /PDFXOutputConditionIdentifier () /PDFXOutputCondition () /PDFXRegistryName () /PDFXTrapped /False

/Description > /Namespace [ (Adobe) (Common) (1.0) ] /OtherNamespaces [ > /FormElements false /GenerateStructure true /IncludeBookmarks false /IncludeHyperlinks false /IncludeInteractive false /IncludeLayers false /IncludeProfiles true /MultimediaHandling /UseObjectSettings /Namespace [ (Adobe) (CreativeSuite) (2.0) ] /PDFXOutputIntentProfileSelector /NA /PreserveEditing true /UntaggedCMYKHandling /LeaveUntagged /UntaggedRGBHandling /LeaveUntagged /UseDocumentBleed false >> ]>> setdistillerparams> setpagedevice

release notes for cisco intelligence engine 2100 series … · release notes for cisco intelligence...

Documents