Table Of Contents
Release Notes for Cisco Configuration Engine 3.5.4
What's New in Cisco Configuration Engine 3.5.4
Obtaining Documentation and Submitting a Service Request
Release Notes for Cisco Configuration Engine 3.5.4
Revised: December 03, 2013,
OL-21544-06This document describes the new features, system requirements, and caveats for Cisco Configuration Engine 3.5.4. 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:
•What's New in Cisco Configuration Engine 3.5.4
•Obtaining Documentation and Submitting a Service Request
Introduction
Cisco Configuration Engine 3.5.4 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 Linux.The Cisco Configuration Engine is a network management software application that provides a highly scalable, secure, and reliable solution for remote deployment. By taking advantage of intelligent agents inside Cisco IOS Software, the Cisco Configuration Engine enables the call-home architecture, which enables a new device to automatically connect with the Cisco Configuration Engine and obtain the correct configuration.
What's New in Cisco Configuration Engine 3.5.4
Cisco Configuration Engine 3.5.4 supports the RHEL5 (32-bit) and the RHEL6 (64-bit) operating system.
Note The Cisco Configuration Engine runs on a 32-bit mode on a 64-bit Linux operating system.
Executing the Patch Script
If you have custom attributes defined in the Cisco Configuration Engine, and are planning to migrate from Release 3.5.3 or earlier to Cisco Configuration Engine 3.5.4, run the schema patch script. The patch script will be a part of Cisco Configuration Engine Release 3.5.4; the patch script file is available in the RPMS and Patch directory when you untar the Cisco Configuration Engine 3.5.4 tar file. After applying this patch, you can run search queries based on your custom attributes.
To run the patch script, follow these steps:
1. Untar the Cisco Configuration Engine 3.5.4 tar file and go to the patch folder.
2. Run the ./schema_patch.sh script.
Example of Data Export Prompts:
# ./schema_patch.sh--------------------------------------------------CE utility to patch schema of custom defined attributes.--------------------------------------------------Apply this patch if you are migrating from any CE release prior to CE 3.5.3 to CE 3.5.4 or above release.Do you want to apply the patch to update CE schema? (y/n) [n]yApplying patch...Patch SUCCESS!!!Now you can run dataexport script for CE migration.For more information on schema patch script, see the Cisco Configuration Engine Installation and Configuration Guide.
Note If you are using releases prior to Release 3.5.3, execute the schema patch to upgrade to Release 3.5.4. If you are using Release 3.5.3, you do not have to execute this patch.
Cisco IOS Dependencies
Table 1 lists the Cisco IOS versions with the corresponding versions of the Cisco Configuration Engine, including feature limitations associated with each version.
Router Configuration
The Cisco Configuration Engine 3.5.4 software should be installed before configuring a device. The device can obtain its initial configuration from the Cisco Configuration Engine 3.5.4.
Limitations and Restrictions
•If your configuration changes the username, password, enable password, or IP address for a nonagent-enabled device, modify the corresponding Intelligent Modular Gateway hop information for the device in order to update it with the new username, password, enable password, and IP address.
•TFTP
–No new files can be created, and existing files cannot be deleted. However, existing files can be overwritten if they are publicly writable. The permissions for the files placed in the FTP directory can be controlled by the SFTP user managing the 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, TFTP allows only publicly readable files to be accessed.
•Device Name values can only contain period (.), underscore (_), hyphen (-), and alphanumeric characters.
•Group Name values can only contain underscore (_) and alphanumeric characters.
•The configuration entry in /etc/hosts on the server where the Cisco Configuration Engine is installed must comply with the following format:
<server IP> <hostname> <FQDN>
172.27.117.199 imgw-test16 imgw-test16.cisco.com
•The Cisco Networking Services (CNS) Agent should use the same configuration event and image ID when using CE to manage devices.
•If you download a configuration that changes the CNS password, use the Cisco Configuration Engine to resync the device.
•The attribute name must begin with alphabetical characters only when a new attribute is being added through the Directory Manager.
Caveats
The caveats describe unexpected behavior in Cisco Configuration Engine 3.5.4. See the following sections for more information:
Open Caveats
There are no open caveats for this release.
Resolved Caveats
•CSCth25115
Symptom: The Configuration Engine logs increase in size when they are not rotated.
Conditions: This condition occurs on all the existing versions of Cisco Configuration Engine.
Workaround: Create a cron job that runs the logrotate -f /etc/logrotate.d/cnsce/* command.
•CSCtu41529
Symptom: The Cisco Security Manager jobs created for nonconnected devices do not stop and start automatically.
Conditions: This condition occurs when the device name and device identity do not match.
Workaround: Ensure that the device name and device identity have the same value and check if Configuration Engine 3.5.3 patch is upgraded.
•CSCtu46791
Symptom: The ASA/PIX LDAP search fails and displays the status code 34.
Conditions: This condition occurs when the ASA/PIX LDAP storage in unavailable on versions earlier that Release 3.5.0.
Workaround: Use the data export scripts from Cisco Configuration Engine Release 3.5.1 version.
•CSCsc82397
Symptom: Cisco Configuration Engine running on release 3.0.1, crashes periodically.
Conditions: This condition occurs when the Cisco Configuration Engine running on release 3.0.1 runs out of memory.
Workaround: There is no workaround.
Related Documentation
Table 1 describes the documentation available for Cisco Configuration Engine.
Table 2 Cisco Configuration Engine Documentation
Document Title Available FormatsCisco Configuration Engine Installation and Configuration Guide, 3.5.4
This document is available on Cisco.com and can be accessed without an account.
Cisco Configuration Engine Administration Guide 3.5.4
This document is available on Cisco.com and can be accessed without an account.
Cisco Configuration Engine Software Development Kit API Reference and Programmer Guide 3.5.3
This document is available on Cisco.com and can be accessed without an account.
Troubleshooting Guide for Cisco Configuration Engine 3.5.3
This document is available on Cisco.com and can be accessed without an account.
Release Notes for Cisco Configuration Engine 3.5.4
This release note document is available on Cisco.com and can be accessed without an account.
Cisco Configuration Engine 3.5.4 Open Source Documentation
This document is available on Cisco.com and can be accessed without an account.
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 "Cisco IOS Dependencies" section.
Cisco and the Cisco Logo are trademarks of Cisco Systems, Inc. and/or its affiliates in the U.S. and other countries. A listing of Cisco's trademarks can be found at www.cisco.com/go/trademarks. Third party trademarks mentioned 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. (1110R)
This product includes software developed by Eric Rescorla for RTFM, Inc.
© 2013 Cisco Systems, Inc. All rights reserved.