Table Of Contents
Release Notes for Cisco PACE Components, 2.0 and 2.0.1
Cisco PACE Components Features
Known Limitations and Problems
Accessing the Cisco PACE Components Documentation Set
Obtaining Documentation, Obtaining Support, and Security Guidelines
Release Notes for Cisco PACE Components, 2.0 and 2.0.1
Revised: December, 2009, OL-19440-01These release notes include important information regarding Cisco Proactive Automation of Change Execution (PACE) Components, Release 2.0 and 2.0.1.
This document contains the following:
•
Cisco PACE Components Features
•
•
•
Note
Cisco PACE Overview
The Cisco PACE solution combines products that accelerate operational success by helping IT organizations to securely automate and control changes and configuration in their networks. Cisco PACE helps enterprises to meet compliance requirements, ensure business continuity, and increase user productivity.
Cisco PACE 2.0 solution is made up of the following:
•
Cisco PACE Portal provides a launch point and top-level navigation for the frequently used functions in the CiscoWorks NCM application. You can view the important statistics and details of the CiscoWorks NCM applications installed on your CiscoWorks NCM server, in a single window instead of navigating through several windows to view the required data.
•
–
–
–
–
Cisco PACE Components Features
Cisco PACE Components include a suite of value-added capabilities for CiscoWorks NCM users:
•
•
•
•
Caveats
Please read the following before using Cisco PACE Components, 2.0.
CSCsr81881—Syslog server installer can delete Oracle CiscoWorks NCM database
Description: The Syslog Server uses its own database and WILL overwrite the CiscoWorks NCM database if the same db name is specified at installation. The CiscoWorks NCM installer must validate that the Syslog Server database name does not conflict with the CiscoWorks NCM database during install.
Workaround: None at this time.
CSCsu75001—The asterisk character '*' appears at the start and end of each line with console install
Description: The following appears on the Solaris and Linux platforms:
1.
2.
3.
Workaround: Exit the installer and start the installation again.
CSCsz17580—Filters not getting deleted from DB - restart loads deleted filters back
Description: The filters remove command does not delete filters from database even though they are removed from internal memory.
Workaround: Modify the following lines in C_Config->deleteLike() method.
From:
super.delete(C_SITE.SITEID + "=" + C_SITE.getMySiteId() + " AND VER='" + version + "' AND NAME LIKE '" + name + ".%'");
To:
super.delete(C_SITE.SITEID + "=" + C_SITE.getMySiteId() + " AND VER='" + version + "' AND NAME LIKE '" + name + "%'");
The period (.) is removed before the percent sign (%) in the last line.
CSCsz35588—As soon as you create an action it may start taking action
Description: Action is taken for all syslogs received. If you create an action without configuring a filter for that action it might start sending emails for the syslogs currently received until filters are configured. If the action is an email action, then emails are sent for every syslog received. As a result, these emails might flood your mail box.
Workaround: Configure the action specific filters as soon as the action is created.
CSCsz41235—PACE-Syslog Analyzer and CiscoWorks NCM network interface configuration mismatch
Description: When CiscoWorks NCM and Cisco PACE Components are installed on the same server and you add a device with syslog logging checked, configuration changes made on the device are not enabled.
Workaround: Currently the listener socket is bound to the wildcard address, an IP address chosen by the kernel. To use a specified address, manually add a property to the UserInstallDir/addins/cisco/syslog/property/PssCustom.properties file:
srd.udp.address=<ipaddress>
CSCsz41908—CSS will not start because the UDP port 514 is pre-occupied
Description: If you specified using a MySQL database engine during the Cisco PACE Component installation, the hostname you supplied must match the hostname that was supplied during the MySQL installation. If MySQL was installed during the CiscoWorks NCM installation, then you must use the same hostname that was supplied during the CiscoWorks NCM installation.
Workaround: To determine the hostname that was supplied during the CiscoWorks NCM installation, look in the userInstallDir\server\conf\my.ini file or look in the mysqlInstallDir\my.ini file for the bind.address and see what is given there.
If the bind address is bind-address=127.0.0.1, then enter the hostname as localhost. If the bind address is an IP address, then supply this address during installation.
CSCsz73793—Delete and Backspace keys do not work when entering password
Description: The Delete and Backspace keys do not work when entering passwords on Solaris and Linux platforms.
Characters entered in the password field are displayed as asterisks. The password field might display one asterisk even before you enter any characters. If you make a mistake and wants to use the Delete or Backspace keys, the installer starts displaying fields for all entries.
Workaround: Cancel the installation and restart.
CSCsy30368—ERROR: The included VM could not be extracted
Description: Install failed with the following message:
Server# sh install.bin
Preparing to install...
WARNING: /tmp does not have enough disk space! Attempting to use / for install base and tmp dir.
Extracting the JRE from the installer archive...
The included VM could not be extracted. Please try to download the installer again and make sure that you download using 'binary' mode. Please do not attempt to install this currently downloaded copy. server#
Workaround: Clear the /tmp file to make that there is sufficient space for the Cisco PACE Component files. Attempt install again.
CSCta26679—Syslog server should parse all types of Cisco device timestamps
Description: RFC parsers in this release parse standard RFC-3164 syslogs and provide limited support for broken RFC syslogs. If a syslog does not comply with RFC standard, the parsers will parse the PRI part if it exists. The parsers do not parse broken HEAD part, which is what the bug report requests.
Workaround: In order for the Cisco PACE Syslog Analyzer to correctly parse the timestamp, we suggest that you let the device use the default timestamp.
CSCta31536—Cisco PACE Portal and Cisco PACE Components installation order check required
Description: Cisco PACE Components need to be installed before the Cisco PACE Portal to benefit from the automatic registration of syslogs. Currently no check is done while installing the Cisco PACE Portal for the presence of the Cisco PACE Components.
Workaround: Be sure to install the Cisco PACE Components before the Cisco PACE Portal if you want syslogs to automatically be registered.
CSCta45868—Uninstall does not change CiscoWorks NCM syslog port back if user had re-installed
Description: Uninstalling the Cisco PACE Components does not change the CiscoWorks NCM syslog port back to the original port if you installed the Cisco PACE Components on the same box as CiscoWorks NCM.
When you uninstall the Cisco PACE Components, the installer makes a copy of the USER_INSTALL_DIR/jre/adjustable_options.rcx file and names it adjustable_options.rcd.backup for every installation and re-installation. Depending on how many times you reinstall the Cisco PACE Components, there will be multiple backups of the file.
Workaround: The CiscoWorks NCM port is decided by the line:
<option name="syslog/listener_port">1756</option>
Look up this line in the oldest backed up file and copy this line to the adjustable_options.rcx file.
CSCta65239—The Cisco PACE Syslog Analyzer displays jdbc exceptions and does not start
Description: The Cisco PACE Syslog Analyzer server does not up after first time reboot and displays a jdbc exception because the Cisco PACE Syslog Analyzer comes up before MySQL.
Workaround: Manually start The Cisco PACE Syslog Analyzer server after MySQL is up. To check if MySQL is up. enter the following:
/etc/init.d/mysql status start Pace Syslog Analyzer /etc/init.d/paceSyslog start
Known Limitations and Problems
This section contains information about the limitations and problems known to exist in the Cisco PACE Component, Release 2.0.
Cisco PACE Components Can Only Be Installed with MySQL as Localhost
If MySQL was previously installed along with CiscoWorks NCM and localhost was used as the server name, MySQL configures itself to bind with address 127.0.0.1. Therefore, giving DNS hostname or IP address during the Cisco PACE Components installation results in a failure to connect to the database. Only using hostname or the address 127.0.0.1 will work.
Canceling Install does not Start CiscoWorks NCM Services
Canceling the Cisco PACE Components installation does not automatically restart the CiscoWorks NCM services. You will not be prompted to restart the CiscoWorks NCM services. You must manually restart the CiscoWorks NCM services.
NCM Syslog Port was not Restored After Uninstalling PACE Components
The CiscoWorks NCM syslog port was reconfigured to 7514 during Syslog installation. The configuration was properly restored to port 514 after Cisco PACE Components un-installation. However, CiscoWorks NCM still uses port 7514 after un-installation is completed; which causes port conflicts. Manually restarting truecontrol causes CiscoWorks NCM to release port 7514 and reoccupy port 514 as configured.
CSS will not Start
After manually stopping or rebooting the server, you can not start CSS with start-syslog-server.sh script. This issue has been seen on Linux systems with using the MySQL database. Manually restart the Syslog server. If running Cisco PACE Components on a Linux or Solaris platform, use the start_syslog_server.sh command.
Accessing the Cisco PACE Components Documentation Set
You can access the entire Cisco PACE Components documentation set from the following Cisco.com URL:
http://www.cisco.com/en/US/partner/products/ps10519/tsd_products_support_series_home.html
From here you can navigate to any documentation for Cisco PACE Components you will need. The documentation includes:
•
•
•
•
Note
Obtaining Documentation, Obtaining Support, and Security Guidelines
For information on obtaining documentation, obtaining support, providing documentation feedback, security guidelines, and also recommended aliases and general Cisco documents, 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
Notices
The following notices pertain to this software license.
OpenSSL/Open SSL Project
This product includes software developed by the OpenSSL Project for use in the OpenSSL Toolkit (http://www.openssl.org/).
This product includes cryptographic software written by Eric Young (eay@cryptsoft.com).
This product includes software written by Tim Hudson (tjh@cryptsoft.com).
License Issues
The OpenSSL toolkit stays under a dual license, i.e. both the conditions of the OpenSSL License and the original SSLeay license apply to the toolkit. See below for the actual license texts. Actually both licenses are BSD-style Open Source licenses. In case of any license issues related to OpenSSL please contact openssl-core@openssl.org.
OpenSSL License:
Copyright © 1998-2007 The OpenSSL Project. All rights reserved.
Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met:
1.
2.
3.
4.
5.
6.
"This product includes software developed by the OpenSSL Project for use in the OpenSSL Toolkit (http://www.openssl.org/)".
THIS SOFTWARE IS PROVIDED BY THE OpenSSL PROJECT "AS IS"' AND ANY EXPRESSED OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE OpenSSL PROJECT OR ITS CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
This product includes cryptographic software written by Eric Young (eay@cryptsoft.com). This product includes software written by Tim Hudson (tjh@cryptsoft.com).
Original SSLeay License:
Copyright © 1995-1998 Eric Young (eay@cryptsoft.com). All rights reserved.
This package is an SSL implementation written by Eric Young (eay@cryptsoft.com).
The implementation was written so as to conform with Netscapes SSL.
This library is free for commercial and non-commercial use as long as the following conditions are adhered to. The following conditions apply to all code found in this distribution, be it the RC4, RSA, lhash, DES, etc., code; not just the SSL code. The SSL documentation included with this distribution is covered by the same copyright terms except that the holder is Tim Hudson (tjh@cryptsoft.com).
Copyright remains Eric Young's, and as such any Copyright notices in the code are not to be removed. If this package is used in a product, Eric Young should be given attribution as the author of the parts of the library used. This can be in the form of a textual message at program startup or in documentation (online or textual) provided with the package.
Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met:
1.
2.
3.
"This product includes cryptographic software written by Eric Young (eay@cryptsoft.com)".
The word `cryptographic' can be left out if the routines from the library being used are not cryptography-related.
4.
THIS SOFTWARE IS PROVIDED BY ERIC YOUNG "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE AUTHOR OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
The license and distribution terms for any publicly available version or derivative of this code cannot be changed. i.e. this code cannot simply be copied and put under another distribution license [including the GNU Public License].
CCDE, CCENT, CCSI, Cisco Eos, Cisco Explorer, Cisco HealthPresence, Cisco IronPort, the Cisco logo, Cisco Nurse Connect, Cisco Pulse, Cisco SensorBase, Cisco StackPower, Cisco StadiumVision, Cisco TelePresence, Cisco TrustSec, Cisco Unified Computing System, Cisco WebEx, DCE, Flip Channels, Flip for Good, Flip Mino, Flipshare (Design), Flip Ultra, Flip Video, Flip Video (Design), Instant Broadband, and Welcome to the Human Network are trademarks; Changing the Way We Work, Live, Play, and Learn, Cisco Capital, Cisco Capital (Design), Cisco:Financed (Stylized), Cisco Store, Flip Gift Card, and One Million Acts of Green are service marks; and Access Registrar, Aironet, AllTouch, 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 Lumin, Cisco Nexus, Cisco Press, Cisco Systems, Cisco Systems Capital, the Cisco Systems logo, Cisco Unity, Collaboration Without Limitation, Continuum, EtherFast, EtherSwitch, Event Center, Explorer, Follow Me Browsing, GainMaker, iLYNX, IOS, iPhone, IronPort, the IronPort logo, Laser Link, LightStream, Linksys, MeetingPlace, MeetingPlace Chime Sound, MGX, Networkers, Networking Academy, PCNow, PIX, PowerKEY, PowerPanels, PowerTV, PowerTV (Design), PowerVu, Prisma, ProConnect, ROSA, SenderBase, SMARTnet, Spectrum Expert, StackWise, WebEx, and the WebEx logo are registered trademarks of Cisco 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. (1002R)
Any Internet Protocol (IP) addresses used in this document are not intended to be actual addresses. Any examples, command display output, and figures included in the document are shown for illustrative purposes only. Any use of actual IP addresses in illustrative content is unintentional and coincidental.
© 2009 Cisco Systems, Inc. All rights reserved.
