Cisco Configuration Engine

Table Of Contents

Release Notes for Cisco Configuration Engine 3.0

Contents

Introduction

What's New in this Release

System Requirements—Solaris

System Requirements—Linux

Related Documentation

SDK Document Available Online and on the SDK CD-ROM

Cisco IOS Dependencies

Router Configuration

Limitations and Restrictions

Caveats

Open Caveats

Resolved Caveats

Obtaining Documentation and Submitting a Service Request

Release Notes for Cisco Configuration Engine 3.0

---

Revised: November 27, 2008

This document describes the new features, system requirements, and caveats for Cisco Configuration Engine, 3.0. Use this document in conjunction with the documents listed in the "Related Documentation" section.

---

Note We sometimes update the documentation after original publication. Therefore, you should also review the documentation on Cisco.com for any updates.

---

Contents

This document includes the following sections:

•Introduction

•What's New in this Release

•Related Documentation

•SDK Document Available Online and on the SDK CD-ROM

•Router Configuration

•Limitations and Restrictions

•Caveats

•Obtaining Documentation and Submitting a Service Request

Introduction

The Cisco Configuration Engine 3.0 is a network management application that acts as a configuration service for automating the deployment and management of network devices and services. The
Cisco Configuration Engine runs on host systems running either Linux or Solaris.

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

What's New in this Release

Cisco Configuration Engine 3.0 supports updated versions of the Solaris and Linux operating systems with increased device connections. For details see System Requirements—Solaris and System Requirements—Linux.

System Requirements—Solaris

With the following system requirements, the device connections can scale up to 30,000 devices:

•Solaris 10

•32 GB RAM

•8 core 1.0-GHz UltraSPARC T1 processor

•70 GB disk space

System Requirements—Linux

With the following system requirements, the device connections can scale up to 20,000 devices:

•Red Hat Enterprise Linux 4 (32-bit SMP, kernel 2.6)

•2 Intel Xeon CPUs 5140 at 2.33 GHz or equivalent or higher

•4 GB RAM

•70 GB disk space

Related Documentation

Table 1 describes the documentation available for Cisco Configuration Engine.

Table 1 Cisco Configuration Engine Documentation 

Document Title	Available Formats
Cisco Configuration Engine Installation & Configuration Guide, 3.0	This guide is available in the following formats: •On the product CD-ROM. •On Cisco.com.
Cisco Configuration Engine Administration Guide	This guide is available in the following formats: •On the product CD-ROM. •On Cisco.com.
Cisco Configuration Engine Software Development Kit API Reference and Programmer Guide	This guide is available in the following formats: •On the SDK CD-ROM. •On Cisco.com. See "SDK Document Available Online and on the SDK CD-ROM" section.
Troubleshooting Guide for Cisco Configuration Engine	On Cisco.com.
Release Notes for Cisco Configuration Engine 3.0	On Cisco.com.
Readme First for Cisco Configuration Engine 3.0	Printed document included with the product.

SDK Document Available Online and on the SDK CD-ROM

The Cisco Configuration Engine Software Development Kit API Reference and Programmer Guide is available online as well as on the SDK CD-ROM. Although the readme first document states that the Cisco Configuration Engine Software Development Kit API Reference and Programmer Guide is available on the SDK CD-ROM only, please note that this document is also available online on Cisco.com.

Cisco IOS Dependencies

Table 2 lists Cisco IOS versions with corresponding versions of Configuration Engine, including feature limitations associated with each version.

Table 2 Cisco Configuration Engine 3.0 and Cisco IOS Dependencies

Cisco IOS	CNS Configuration Engine	Limitations
12.3	1.3.2 or later
12.2(11)T	1.2 or later
12.2(2)T	1.2 or later with no authentication	Applications will be unable to use exec commands or point-to-point messaging.

Router Configuration

For a router to pick up its initial configuration from the Cisco Configuration Engine 3.0, install the
Cisco Configuration Engine 3.0 software before installing the router. Then, establish a connection between the router and the Cisco Configuration Engine 3.0.

For information about Cisco Flow-Through Provisioning, see:

http://www.cisco.com/en/US/docs/ios/12_2t/12_2t8/feature/guide/ftsnap26.html.

Limitations and Restrictions

•If you download a configuration that changes username, password, enable password, or IP address for a non-agent-enabled device, you need to modify the corresponding IMGW hop information for the device to update it with the new username, password, enable password, and IP address.

•SFTP—An SFTP server is permanently enabled which can be used for administrative tasks such as placing images securely into the FTP directory [ /tftp/CSCOcnsis/images/ ] for image download by devices over FTP or TFTP. Any regular system account may log in to SFTP.

•FTP—FTP service is READ-ONLY and the user must be "root".

•TFTP:

–No new files can be created and files cannot be deleted. However, existing files can be overwritten ONLY if they are publicly writable. The permissions of the files placed into the FTP directory can be controlled by the SFTP user managing files in the FTP directory.

–The TFTP service does not require an account or password on the server system. Because of the lack of authentication information, TFTPD allows only publicly readable files (o+r) to be accessed. Files may be written only if they already exist and are publicly writable.

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

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

•When a UDI is used as a device-unique ID, the unique ID string used on CE has to exactly match that which the CNS agent uses on the router.

•The configuration entry in /etc/hosts on the server where CE is installed must comply with the following format:

<server IP> <hostname> <FQDN>

172.27.117.199 imgw-test16 imgw-test16.cisco.com

•CNS Agent should use the same config event and image ID when using CE to manage devices.

•If you download a configuration that changes the CNS password, you need to use CE to resync the device.

•When a UDI is used as an event ID, the device will not be created by device discovery.

•When creating an IMGW device, the device name and the unique ID has to have the same value.

Caveats

The caveats describe unexpected behavior in Cisco Configuration Engine 3.0. See the following sections for more information:

•Open Caveats

•Resolved Caveats

Open Caveats

Table 3 describes the open caveats for Cisco Configuration Engine 3.0.

Table 3 Open Caveats for Cisco Configuration Engine 3.0 

ID	Problem	Workaround
CSCsl64036	Assign a generic CNS password when Authentication is enabled during setup.	After CE setup is complete and Authentication is enabled, you must create a bootstrap password first before you do other operations. If you do not create a bootstrap password, all the devices will have to be synced individually.
CSCsr67550	Config update: banner cannot begin with a hyphen and cannot have ^C as a delimiter. Update Config to non-agent-enabled device does not accept configure banners which have the character hyphen (-) as the first in the line. Multi-line banner does not accept ^C as the start/end delimiter.	•Imgw device supports the following banner's anchors: \(.*)# •Avoid the hyphen (-) as the first character of any line in the banner. •Do not use ^C as a delimiter in banner configurations to non-agent-enabled devices. Example of banner that will not work: banner login < -one -two -three < Example of banner that will work: banner login < one- two-three four
CSCsv78312	Data restore and migration need both CEs to be installed in the same directory.	If on server A, CE is installed in /export/home/ConfigEngine, and on server B, CE is installed in /opt/ConfigEngine: 1. Before running data export or backup on sever A, do the following: ln -s /export/home/ConfigEngine /opt/ConfigEngine, change the following environment as follows: APPLIANCE_HOME=/opt/ConfigEngine/appliance PWD=/var/log/CNSCE/imgw CISCO_CE_HOME=/opt/ConfigEngine/CSCOcnsie CISCO_CE_INSTALL_ROOT=/opt/ConfigEngine 2. Perform data export or backup. 3. Perform data migration or data restore on server B.
CSCsu85086	Not able to edit IMGW device name. IMGW device disappears after editing device name.	Recreate the IMGW device with a new device name. Delete the old device from LDAP.
CSCsv89994	Device name and unique ID has to be the same for IMGW to work.	When creating IMGW device, ensure that the device name and the unique ID are the same, otherwise, the device will not work.

Resolved Caveats

Table 4 describes the resolved caveats for Cisco Configuration Engine 3.0.

Table 4 Resolved Caveats for Cisco Configuration Engine 3.0 

ID	Problem
CSCsm27069	Data migration from CE 1.5 to 2.0 requires intervention in some cases.
CSCsm27179	Backup/restore needs to support transferring data between CE 2.0 hosts.
CSCsj35405	CE setup script clears crontab entries.
CSCsm51204	The image ID should be created automatically like config ID and event ID.
CSCsl38165	OutOfMemory - Tomcat.
CSCsh13210	Template's values are not populated when a new device is created.
CSCsr36946	CNS CE - config update to non-agent device does not accept the dollar sign ($) in password.
CSCso80750	Banner login circumflex (^) does not work with the pound sign (#).
CSCsr23004	Unable to clone subdevice when using template with non-default attribute.
CSCsv53054	Config Update - IMGW device - Banner login * does not work.
CSCsv53109	Config/Image Update - IMGW device - certain banners do not work.
CSCsl06737	CNS and CE implementation does not support the UDI format in the ISRs.

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.

---

CCDE, CCENT, Cisco Eos, Cisco Lumin, Cisco Nexus, Cisco StadiumVision, Cisco TelePresence, Cisco WebEx, the Cisco logo, DCE, and Welcome to the Human Network are trademarks; Changing the Way We Work, Live, Play, and Learn and Cisco Store are service marks; and Access Registrar, Aironet, AsyncOS, Bringing the Meeting To You, Catalyst, CCDA, CCDP, CCIE, CCIP, CCNA, CCNP, CCSP, CCVP, Cisco, the Cisco Certified Internetwork Expert logo, Cisco IOS, Cisco Press, Cisco Systems, Cisco Systems Capital, the Cisco Systems logo, Cisco Unity, Collaboration Without Limitation, EtherFast, EtherSwitch, Event Center, Fast Step, Follow Me Browsing, FormShare, GigaDrive, HomeLink, Internet Quotient, IOS, iPhone, iQuick Study, IronPort, the IronPort logo, LightStream, Linksys, MediaTone, MeetingPlace, MeetingPlace Chime Sound, MGX, Networkers, Networking Academy, Network Registrar, PCNow, PIX, PowerPanels, ProConnect, ScriptShare, SenderBase, SMARTnet, Spectrum Expert, StackWise, The Fastest Way to Increase Your Internet Quotient, TransPath, WebEx, and the WebEx logo are registered trademarks of Cisco Systems, Inc. and/or its affiliates in the United States and certain other countries.

All other trademarks mentioned in this document or website are the property of their respective owners. The use of the word partner does not imply a partnership relationship between Cisco and any other company. (0809R)

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