Table Of Contents
Release Notes for CiscoWorks Assistant 1.0
Contents
Introduction
Product Documentation
Related Documentation
Known Problems in CiscoWorks Assistant 1.0
Obtaining Documentation, Obtaining Support, and Security Guidelines
Open Source License Acknowledgements
OpenSSL/Open SSL Project
License Issues
Release Notes for CiscoWorks Assistant 1.0
Revised: June 22, 2007, OL-12177-01
CDC Date June 12, 2007
Contents
This document has the following sections:
•
Introduction
•Product Documentation
•Related Documentation
•Known Problems in CiscoWorks Assistant 1.0
•Obtaining Documentation, Obtaining Support, and Security Guidelines
•Open Source License Acknowledgements
Introduction
CiscoWorks Assistant is a web-based tool that provides workflows to help you to overcome network management and software deployment challenges. CiscoWorks Assistant is available along with CiscoWorks LAN Management Solution (LMS) solution.
A workflow is a compilation of tasks that assist you to deploy LMS servers and troubleshoot your network. The CiscoWorks Assistant Engine, which works in the backend, runs the workflows and allows you to navigate between the various tasks.
CiscoWorks Assistant 1.0 provides the following workflows:
•Device Troubleshooting—Helps you to identify the root cause for device unreachabililty. The generated Device Troubleshooting report contains the following details for the selected device:
–Alerts and Syslog messages
–Last configuration change
–Details of the device topology
–Details on network inconsistencies, and misconfiguration in the network device.
•End Host/IP Phone Down—Helps you to get the information required to troubleshoot as well as analyze the connectivity issues related to end hosts and IP Phones.
•Server Setup—Helps you to setup and manage LMS servers. Simplifies the deployment and setting up of single or multiple LMS servers.
For information on CiscoWorks Assistant installation, see the Installing and Getting Started with CiscoWorks LAN Management Solution 3.0.
For information on using the workflows, see the User Guide for CiscoWorks Assistant or the context sensitive Online help.
Product Documentation
Table 1 describes the product documentation that is available.
Table 1 Product Documentation
Related Documentation
Table 2 describes additional documentation available.
Table 2 Related Documentation
Known Problems in CiscoWorks Assistant 1.0
Table 3 contains the Known Problems found in CiscoWorks Assistant 1.0.
Table 3 Known Problems in CiscoWorks Assistant 1.0
Bug ID
|
Summary
|
Explanation
|
CSCsj30122
|
Device credentials are corrupted after configuring Default Credentials using CiscoWorks Assistant.
|
Device credentials are corrupted after configuring Default Credentials using the CiscoWorks Assistant Server Setup Workflow. Because of this, applications fail to work properly. For example, Resource Manager Essentials fails to archive configurations from devices, or deploy software images.
Workaround:
Configure the Default Credentials from Common Services (Common Services > Device and Credentials > Admin > Default Credentials).
If the devices are already in DCR, then go to Common Services > Device and Credentials > Device Management to change the device credentials.
|
CSCsi61116
|
Device Discovery Poll timeout occurs if there are more devices in Device and Credential Repository (DCR).
|
The Server Set up workflow device discovery displays the following message if there are more than 5000 devices in DCR:
status poll timeout
CiscoWorks Assistant polls for Device Discovery completion for 30 minutes. If the operation is not completed within this time, CiscoWorks Assistant displays the above message.
The e-mail report says that discovery has timed out.
Workaround:
None.
Although UI shows the timeout message, the workflow runs in the backend.
You can go to Campus Manager home page to view the status of the discovery operation.
|
CSCsi80709
|
ACS mode should be changed back to non-ACS mode when ACS configuration fails for any one of the servers part of a Multi-server setup.
|
When you change the ACS mode in a Multi-server setup and it fails for any of the servers, the setup will have mixed AAA modes. This may be caused by a mismatch in the secret key.
We do not recommend a Multi-server setup that has mixed AAA modes.
Workaround:
Change the AAA mode of the Master back to non-ACS mode if the ACS configuration fails for any one of the Slaves in the Multi-server setup.
|
CSCsi91589
|
Troubleshooting workflow report has incomplete data if one of the servers in a Multi-server set up is down.
|
Device Troubleshooting workflow report shows incomplete information if one of servers in a Multi-server setup is down or not reachable. CiscoWorks Assistant cannot interact with the LMS applications installed in servers that are unreachable or down.
CiscoWorks Assistant fetches data only from the local server if any of the servers in a Multi-server setup is unreachable or down.
Workaround:
Ensure that the server:
•Is reachable.
•Is running.
•Has the required LMS applications installed.
|
CSCsi91608
|
Cannot delete an unreachable server.
|
If one of the servers in a Multi-server setup has a hardware failure or is temporarily inaccessible, you cannot perform the Manage Servers and Change ACS Mode tasks in the Server Setup workflow.
Also, you will not be able to delete the unreachable server because you cannot perform the Delete Server task, which is part of the Manage Servers flow.
Workaround:
None.
|
CSCsi92894
|
End Host / IP Phone Down workflow does not get data from all the servers.
|
This occurs when you run the End Host / IP Phone down workflow when the machine does not have Campus Manager installed.
The following message is displayed:
CWA37: End Host / IP Phone workflow requires Campus Manager to be installed.
Workaround:
Run the workflow on a machine that has Campus Manager installed, and ensure that device is managed by Campus Manager.
|
CSCsi91629
|
Device Troubleshooting workflow Device Selector does not always show devices under All Devices.
|
In the Device Troubleshooting workflow page, if you expand the All Devices tab in the Device Selector, it sometimes does not show the devices.
Workaround:
However, the devices appear in the device group trees, and also in Device Center.
Relaunch the browser to populate the devices under the All Devices tab.
|
CSCsj05479
|
CiscoWorks Assistant is not working after the port change in the Slave.
|
In a Multi-server setup, if you change the port number of the Slave server, CiscoWorks Assistant does not work properly. This is because the port change does not get reflected in the Master.
Workaround:
1. Change DCR mode of the Slave server (after port change) to Standalone.
2. Add the following line in the dcr.ini file of the Slave:
PREVIOUS_DCR_GROUP_ID = Master's DCR_GROUP_ID
where, Master's DCR_GROUP_ID is the value of DCR_GROUP_ID from the dcr.ini file of the Master.
3. Change the DCR mode of the Standalone server back to Slave. This operation might result in data loss.
|
CSCsj04973
|
Inconsistent issues with application data in Device Troubleshooting report.
|
The Device Troubleshooting workflow report might have the following issues:
•Does not display CDP neighbors if you specify only hostname in DCR. To display the CDP neighbors, you must enter the IP address.
•Does not show all Syslog messages.
•Shows Emergencies headline but does not list the messages under it.
•DFM Alerts take a long time to load even if there are no alert messages for the device.
•Syslog messages appear in Loading state even after all messages are displayed.
Workaround:
CDP neighbors will be displayed if the hostnames are DNS resolvable.
Other issues do not have workarounds.
|
CSCsj08858
|
Devices managed in the Slave get deleted while creating a Multi-server setup.
|
All devices managed in Slave get deleted while you are creating a Multi-server setup using CiscoWorks Assistant. This happens because devices managed in Slaves are not added to the Master's DCR.
Workaround:
None.
Currently, CiscoWorks Assistant does not provide this feature. However, you can do this using CiscoWorks Common Services. See User Guide for CiscoWorks Common Services 3.1, for details.
|
CSCsj12820
|
CiscoWorks Assistant does not display a warning message when one of the servers is unreachable.
|
If you run Device Troubleshooting workflow when any of the servers in a Multi-server setup is unreachable, the workflow gathers data only from the local server.
CiscoWorks Assistant does not display a warning message about the unreachable server.
Workaround:
None.
|
CSCsi91287
|
Changing Homepage server name does not get reflected in CiscoWorks Assistant.
|
If you change the homepage server name from Common Services (Common Services > Server > Home Page Admin), it gets reflected in all the browser and Application tabs.
However, the change does not get reflected in CiscoWorks Assistant pages.
Workaround:
None.
|
CSCsj08841
|
Cannot launch the workflows after you re-initialize the CiscoWorks Assistant database.
|
This occurs when you:
1. Run dbrestoreorig.pl using the following command:
On Solaris:
–/opt/CSCOpx/bin/perl dbRestoreOrig.pl dsn=opsxml dmprefix=Opsxml
On Windows:
–NMSROOT\bin\perl dbRestoreOrig.pl dsn=opsxml dmprefix=Opsxml
2. Restart Daemon Manager and launch CiscoWorks Assistant workflows.
The following error message is displayed:
CWA0: Could not fetch the error message from the database. CWA database engine may not be running.
Check if the OpsxmlDbEngine (Common Services > Server > Admin > Processes) is running. If the process is not running, restart the process and please try again.
Workaround:
Change the CiscoWorks Assistant database password.
To do this, run dbpasswd.pl.
On Solaris:
–/opt/CSCOpx/bin/perl dbpasswd.pl dsn=opsxml npwd=new password
On Windows:
–NMSROOT\bin\perl dbpasswd.pl dsn=opsxml npwd=new password
|
CSCsi43537
|
Cannot add a new server when one of the Slaves in a Multi-server setup is unreachable.
|
In a Multi-server setup, if one of the slaves is down, you cannot run the Manage Servers and Change ACS Setup steps in Server Setup workflow.
However, you can run all the device related steps such as Setting Default Credentials, Adding Devices, and Managing Devices.
This occurs because changes made during Manage Servers and Change ACS Setup steps have to be uniformly applied across all servers part of the Multi-server setup. The changes cannot be omitted for any servers that are down.
Workaround:
None.
|
CSCsh68984
|
Port number is not displayed in Check Status in the End Host / IP Phone Down report.
|
The End Host / IP Phone port number is not displayed in Check Status in the End Host / IP Phone Down report.
This occurs when you generate the report for the End Host / IP Phone that is not connected to any port or if the connected port is down.
Workaround:
None.
|
CSCsj21410
|
CiscoWorks Assistant workflows fail to work on Windows Servers running Japanese OS.
|
On a Windows Server running Japanese OS, Server Setup workflow fails to start. The page initially displays the following message:
Collecting existing server information. Please wait.
However, it eventually fails and the following Error Message is displayed:
Server Discovery timed out. Please try again later.
The Device Troubleshooting workflow and the End Host/IP Phone Down workflow also fail to run.
Workaround:
None
|
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
This document is to be used in conjunction with the documents listed in the Related Documentation section.
Open Source License Acknowledgements
The following acknowledgements 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:
© 1998-1999 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. Redistributions of source code must retain the copyright notice, this list of conditions and the following disclaimer.
2. Redistributions in binary form must reproduce the above copyright notice, this list of conditions, and the following disclaimer in the documentation and/or other materials provided with the distribution.
3. All advertising materials mentioning features or use of this software must display the following acknowledgment: "This product includes software developed by the OpenSSL Project for use in the OpenSSL Toolkit. (http://www.openssl.org/)"
4. The names "OpenSSL Toolkit" and "OpenSSL Project" must not be used to endorse or promote products derived from this software without prior written permission. For written permission, please contact openssl-core@openssl.org.
5. Products derived from this software may not be called "OpenSSL" nor may "OpenSSL" appear in their names without prior written permission of the OpenSSL Project.
6. Redistributions of any form whatsoever must retain the following acknowledgment:
"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:
© 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. Redistributions of source code must retain the copyright notice, this list of conditions and the following disclaimer.
2. Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution.
3. All advertising materials mentioning features or use of this software must display the following acknowledgement:
"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. If you include any Windows specific code (or a derivative thereof) from the apps directory (application code) you must include an acknowledgement: "This product includes software written by Tim Hudson (tjh@cryptsoft.com)".
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].
CCVP, the Cisco logo, and the Cisco Square Bridge logo are trademarks of Cisco Systems, Inc.; Changing the Way We Work, Live, Play, and Learn is a service mark of Cisco Systems, Inc.; and Access Registrar, Aironet, BPX, Catalyst, CCDA, CCDP, CCIE, CCIP, CCNA, CCNP, CCSP, Cisco, the Cisco Certified Internetwork Expert logo, Cisco IOS, Cisco Press, Cisco Systems, Cisco Systems Capital, the Cisco Systems logo, Cisco Unity, Enterprise/Solver, EtherChannel, EtherFast, EtherSwitch, Fast Step, Follow Me Browsing, FormShare, GigaDrive, HomeLink, Internet Quotient, IOS, iPhone, IP/TV, iQ Expertise, the iQ logo, iQ Net Readiness Scorecard, iQuick Study, LightStream, Linksys, MeetingPlace, MGX, Networking Academy, Network Registrar, Packet, PIX, ProConnect, ScriptShare, SMARTnet, StackWise, The Fastest Way to Increase Your Internet Quotient, and TransPath 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. (0705R)
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.
Release Notes for CiscoWorks Assistant 1.0
© 2007 Cisco Systems, Inc.
All rights reserved.
