Professional Documents
Culture Documents
Americas Headquarters
Cisco Systems, Inc.
170 West Tasman Drive
San Jose, CA 95134-1706
USA
http://www.cisco.com
Tel: 408 526-4000
800 553-NETS (6387)
Fax: 408 527-0883
THE SOFTWARE LICENSE AND LIMITED WARRANTY FOR THE ACCOMPANYING PRODUCT ARE SET FORTH IN THE INFORMATION PACKET THAT
SHIPPED WITH THE PRODUCT AND ARE INCORPORATED HEREIN BY THIS REFERENCE. IF YOU ARE UNABLE TO LOCATE THE SOFTWARE LICENSE
OR LIMITED WARRANTY, CONTACT YOUR CISCO REPRESENTATIVE FOR A COPY.
The Cisco implementation of TCP header compression is an adaptation of a program developed by the University of California, Berkeley (UCB) as part of UCB’s public
domain version of the UNIX operating system. All rights reserved. Copyright © 1981, Regents of the University of California.
NOTWITHSTANDING ANY OTHER WARRANTY HEREIN, ALL DOCUMENT FILES AND SOFTWARE OF THESE SUPPLIERS ARE PROVIDED “AS IS” WITH
ALL FAULTS. CISCO AND THE ABOVE-NAMED SUPPLIERS DISCLAIM ALL WARRANTIES, EXPRESSED OR IMPLIED, INCLUDING, WITHOUT
LIMITATION, THOSE OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT OR ARISING FROM A COURSE OF
DEALING, USAGE, OR TRADE PRACTICE.
IN NO EVENT SHALL CISCO OR ITS SUPPLIERS BE LIABLE FOR ANY INDIRECT, SPECIAL, CONSEQUENTIAL, OR INCIDENTAL DAMAGES, INCLUDING,
WITHOUT LIMITATION, LOST PROFITS OR LOSS OR DAMAGE TO DATA ARISING OUT OF THE USE OR INABILITY TO USE THIS MANUAL, EVEN IF CISCO
OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.
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, RateMUX, ScriptShare, SlideCast, 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. (0704R)
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.
Preface v
Audience v
Conventions vi
Product Documentation vi
INDEX
This document describes the workflows that make up CiscoWorks Assistant. It provides instructions for
configuring, administering, and operating CiscoWorks Assistant.
The CiscoWorks Assistant User Guide is organized as follows:
Chapter Description
Chapter 1, “CiscoWorks Assistant - Gives you an overview of CiscoWorks Assistant.
Overview”
Chapter 2, “Getting Started with Provides you with the list of launch points for the
CiscoWorks Assistant” CiscoWorks Assistant workflows.
You can also review the Privileges that are required for
running CiscoWorks Assistant workflows, using the device
selector, and setting up the debug log level for CiscoWorks
Assistant.
Chapter 3, “Configuring LMS Server Describes how to configure LMS server.
Using CiscoWorks Assistant”
Chapter 4, “Troubleshooting Your Describes how to troubleshoot your network using Device
Network Using CiscoWorks Assistant” Troubleshooting and End Host/IP Phone Down workflows.
Appendix A, “Troubleshooting Describes the troubleshooting tips for all the CiscoWorks
CiscoWorks Assistant” Assistant workflows.
Audience
This document provides descriptions and scenarios for system administrators, network managers, and
other users who might or might not be familiar with CiscoWorks Assistant. Many of the tools described
are accessible to system administrators only.
Conventions
This document uses the following conventions:
Item Convention
Commands and keywords boldface font
Variables for which you supply values italic font
Displayed session and system information screen font
Information you enter boldface screen font
Note Means reader take note. Notes contain helpful suggestions or references to material not covered in the
publication.
Caution Means reader be careful. In this situation, you might do something that could result in equipment
damage or loss of data.
Product Documentation
The following product documentation is available:
Note Although every effort has been made to validate the accuracy of the information in the electronic
documentation, you should also review the CiscoWorks Assistant documentation on Cisco.com for any
updates.
Related Documentation
The CiscoWorks Assistant workflows are dependent on LMS 3.0 applications.
The Installation and Getting Started Guide, Data Migration Guide, User Guide and Release Notes for
the following LMS applications are available in the HTML and PDF formats on Cisco.com at:
http://www.cisco.com/en/US/products/sw/netmgtsw/tsd_products_support_category_home.html
• CiscoWorks LAN Management Solution 3.0
• CiscoWorks Common Services 3.1 (Includes CiscoView 6.1.6)
• Resource Manager Essentials 4.1
• Campus Manager 5.0
• Device Fault Manager 3.0
• Internetwork Performance Monitor 4.0
• LMS Portal 1.0
The following sections provide an overview of CiscoWorks Assistant application and all the
functionalities that are available in CiscoWorks Assistant.
• What is CiscoWorks Assistant?
• What does CiscoWorks Assistant application support?
• What are the dependencies of CiscoWorks Assistant application?
Table 1-1 CiscoWorks Assistant Workflows and the Dependent LMS Applications
Table 1-1 CiscoWorks Assistant Workflows and the Dependent LMS Applications
CiscoWorks Assistant is installed as part of CiscoWorks Common Services. The following topics help
you to work with and understand the CiscoWorks Assistant user interface:
• Launching CiscoWorks Assistant
• Using CiscoWorks Assistant Short-cuts
• User Privileges for CiscoWorks Assistant Workflows
• Settings Debug Level
• CiscoWorks Assistant Process and the Dependency Processes
• Launching Online Help
Step 1 Enter the URL for your CiscoWorks server in your browser.
http://server_name:port_number
Where server_name is the name of the CiscoWorks server and port_number is the TCP port used by the
CiscoWorks server. In normal mode (HTTP), the default TCP port for CiscoWorks server is 1741.
For example:
http://ciscoworksserver:1741
Note If you enter, http://server_name:port_number/login.html in your web browser, the CiscoWorks server
will not launch. Also, do not bookmark the URL with the trailing login.html.
• On Windows, CiscoWorks server always uses the default port numbers (1741 and 443) in secure and
normal modes.
• On Solaris, if the default TCP ports are used by other applications, you can select different ports for
secure and normal modes during CiscoWorks LMS installation.
For more information, see Installing and Getting Started with CiscoWorks LAN Management Solution
3.0
Step 2 Enter admin in the User ID field, and the password for admin in the Password field of the Login Page
Enter the same admin password that you entered while installing CiscoWorks LMS.
Step 3 Click Login or press Enter.
You are now logged into CiscoWorks server.
Logging sessions time out after two hours of inactivity. If you try to do any task after timeout, a message
appears informing you that your session has timed out. You will be prompted to login again.
CiscoWorks LMS Portal is the primary user interface and the launch point for all the applications. After
you log into CiscoWorks, the CiscoWorks LMS Portal home page is displayed.
Step 4 Click the CiscoWorks Assistant link or the Home link under CiscoWorks Assistant portlet on the
CiscoWorks LMS Portal home page.
The CiscoWorks Assistant home page appears in a new window. The CiscoWorks Assistant home page
is an easy way to access frequently used operations. The following links are available.
• Workflows
– Server Setup
– Device Troubleshooting
– End Host/IP Phone Down
• Administration
– Log Level Settings
Table 2-1 Launch Points for CiscoWorks Assistant Workflows from LMS Applications
Table 2-1 Launch Points for CiscoWorks Assistant Workflows from LMS Applications
Task URL1
CiscoWorks Assistant Home http://ServerName:1741/cwa/CWAHome.jsp
Device Troubleshooting Workflow http://ServerName: 1741/cwa/linkDown.do
End Host/IP Phone Down http://ServerName: 1741/cwa/endhostDown.do
Server Setup http://ServerName: 1741/cwa/serverSetup.do
Log Level Settings http://ServerName: 1741/cwa/logLevel.do
1. Where, ServerName is the CiscoWorks LMS server hostname or IP address.
Step 1 Select CiscoWorks Assistant > Administration > Log Level Settings.
The Set CiscoWorks Assistant Logging Level page appears.
Step 2 Select the appropriate log level from the Logging Level drop-down list.
Step 3 Click Reset to apply the default logging levels.
Step 4 Click Apply after you set the log levels.
A message appears, that the log levels have been successfully updated.
The complete User Guide can be viewed in the Adobe Portable Document Format (PDF) from within the
Online Help. To view the PDF, Adobe Acrobat 6.0 or later is required.
The CiscoWorks online Help window contains the following buttons and links:
Button Description
Contents Displays the online help table of content for the launched LMS application.
(Button)
That is, if you have launched Common Services online help, the table of
content for the Common Services application appears.
Index Displays the index entries for the launched LMS application.
(Button)
That is, if you have launched Common Services online help, the index entries
for the Common Services application appears.
Button Description
Search Allows you search any key words within the launched LMS application.
(Button)
That is, if you have launched Common Services online help, you can search
for any keywords within the Common Services online help.
• If you want to search key words in all of the installed LMS application,
you must select All in the application drop-down box (second
drop-down box).
• If you want to search key words in specific LMS application, you must
select the application name in the application drop-down box (second
drop-down box).
That is, if you want to search in CiscoWorks Assistant, select
CiscoWorks Assistant from application drop-down box.
Main This link is available in the top right corner of the CiscoWorks online Help
(Link) window.
Launches the home page of LMS applications online help.
Based on your LMS installed applications, the table of content area lists the
LMS application Online help.
If you have installed all the LMS applications, the table of content lists the
following:
• Campus Manager—Launches the Campus Manager online help.
• CiscoWorks Assistant—Launches the CiscoWorks Assistant online
help.
• CiscoWorks Common Services—Launches the Common Services
online help
• Device Fault Manager—Launches the Device Fault Manager online
help.
• Device Manager—Launches the CiscoView application (Basic) and
CiscoView device packages (ATM Manager, AP1100, Catalyst 4000
IOS, etc.) online help.
• Internetwork Performance Monitor—Launches the Internetwork
Performance Monitor online help.
• Resource Manager Essentials—Launches Resource Manager Essentials
application (RME User Guide) and device packages (Cisco 10000 Series
Routes, Cisco 2600XM Multiservice Router, etc.) online help.
The Server Setup The Server Setup workflow helps you to setup and manage CiscoWorks LAN
management Solution (LMS) servers. It helps you to simplify the deployment and setting up of single or
multiple LMS servers.
The Server Setup workflow assists you in:
• Managing LMS Servers—You can add servers, set up System Identity User accounts, and set up the
device management mode.
• Setting Default Credentials—You can use the default credentials feature to prevent the management
applications from failing if devices added or imported into DCR do not contain all credentials
required to manage them. Default credentials are stored in DCR and are not associated with any
device.
• Adding Devices—You can populate the servers with network devices, either by dynamic discovery,
or bulk import.
• Managing Devices—You can manage devices in each application after adding them into DCR.
• Changing ACS Setup—You can configure the ACS mode and assign device groups.
The Master DCR server refers to the master repository of device list and credential data. There is only
one Master repository for each management domain, and it contains the most up-to-date device list and
credentials. DCR Slaves are slave instances of DCR on other servers and provide transparent access to
applications installed on those servers.
Any change to the repository data occurs first in the Master with the changes being propagated to all the
Slaves. There can be more than one Slave in a management domain but any slave can become a master
at any time.
In Standalone mode, DCR maintains an independent repository of device list and credential data. It does
not participate in a management domain and its data is not shared with any other DCR. It does not
communicate with or contain registration information about any other Master, Slave, or Standalone
DCR.
Devices newly added in DCR can be managed by an application in following ways
• Auto-manage mode —In this mode, applications listen to “Add Device” event and automatically
start managing the device, if the device is relevant to the application.
• Manual-manage mode —In this mode, application keeps track of all newly added devices and shows
the list to the user. User chooses few or all devices from the list for the application to manage. This
mode gives better control on what device to be managed in each application.
The Single Sign-On (SSO) feature helps you to use a single session to navigate to multiple CiscoWorks
servers without having to authenticate to each of them.
For Single Sign On, one of the CiscoWorks servers needs to be set up as the authentication server. The
SSO authentication server is called the Master, and the SSO regular server is called the Slave. If there is
no SSO Master server configured in your setup, the local server is selected as SSO Master.
You must perform the following tasks if the server is either configured as Master or Slave:
• Configure the System Identity User and password in both Master and Slave. The System Identity
User name and password you specify in Master and Slave should be the same.
• Configure Master’s Self Signed Certificate in Slave.
Related Documentation
For more information on Multi-server setups, DCR and SSO, see the latest versions of following
documents on Cisco.com:
• User Guide for CiscoWorks Common Services 3.1
http://www.cisco.com/en/US/products/sw/cscowork/ps3996/products_user_guide_list.html
• White Paper on CiscoWorks L MS Integration with Cisco Secure ACS
http://www.cisco.com/en/US/products/sw/cscowork/ps2425/prod_white_papers_list.html
• LMS application User Guides, wherever applicable.
http://www.cisco.com/en/US/products/sw/netmgtsw/tsd_products_support_category_home.html
After you enter the Server Setup workflow, you can navigate among the available options using the Back,
Skip, and Next buttons.
• Back button
Takes you to the previous screen. When you click Back, the previous step will not be rolled back.
CiscoWorks Assistant does not retain the values you entered previously.
• Skip button
Allows you to skip a task, and get to the next task. For example, if you want to get to the Set Default
Credentials page from the Manage Servers page, without getting into the System Identity User Setup
or Device Management mode page, click Skip.
• Next button
Takes you to the screen that is after the current screen.
CiscoWorks Assistant runs only one instance of Server Setup workflow. You can end an active session
of another user when no operation is running in that session. To end the session, you need to provide the
System Identity User details. If any operation is running, you cannot end the session.
To go to the CiscoWorks Assistant homepage click Home.
Field Description
LMS Server IP Address of the LMS Server or Display Name of the LMS
server.
Reachability Reachability status of the LMS server.
When you click the Expand button of the LMS server, a new pane gets added to the Server Application
List window. The fields in the new pane are described in the following table:
Field Description
Applications Name of the application installed in the server. This can
be any of the following:
• Common Services
• Campus Manager
• Resource Manager Essentials
• Internetwork Performance Monitor
• Device Fault Monitor.
Field Description
Version Version number of the CiscoWorks application.
Version Supported If the version of the application is supported by
CiscoWorks Assistant, a tick mark in green is displayed.
For unsupported applications, a cross in red is displayed.
You cannot perform any tasks using the workflow on
unsupported applications.
Note All the servers you want add to create the Multi-server set up should be DNS resolvable. If not, server
addition will not be successful
Step 1 Select CiscoWorks Assistant > Workflows > Server Setup > Manage Servers from the CiscoWorks
Assistant home page.
The Server Application List table lists the LMS servers.
Step 2 Click Start Setup.
The CiscoWorks server Details table appears with the following details.
• Hostname/IP Address—Hostname or IP Address of the CiscoWorks server.
• Server Display Name—The display name you have set up for the LMS Server.
• Protocol—Protocol of the server. This can be HTTP or HTTPS.
• Port—Port Number of the CiscoWorks server.
• Admin Username—Admin username for the Server.
• DCR—DCR mode of the server. Mode can be DCR Master, Slave, or Standalone.
• SSO—SSO mode of the server. SSO Mode can be Master, Slave, or Standalone.
See the User Guide for CiscoWorks Common Services 3.1 for information on DCR and SSO modes.
Adding a Server
When you add a server, you must:
After you add a server, you can set up the Device Management Mode for all the applications (See Setting
and Editing the Device Management Mode). This determines whether the devices should be managed by
the different applications when they are added to the DCR.
You can view a summary of server addition, after you complete the necessary tasks. See Viewing Server
Addition Summary for details.
Step 1 Select CiscoWorks Assistant > Workflows > Server Setup > Manage Servers.
Step 2 Click Add.
The Add Server dialog box appears.
Step 3 Enter the following server details:
• Hostname/IP Address—Hostname or IP Address of the CiscoWorks server. If the server you add is
in DCR Master mode, or if it is the Salve of another DCR master, it will not allow you to add the
server.
• Administrator Username—Admin username for the Server.
• Administrator Password—Admin username for the Server.
• Protocol—Protocol of the server. Select HTTP or HTTPS from the drop-down list.
• Port—Port Number of the CiscoWorks server.
If the server is in ACS mode, you should enter the Network Device Group (NDG) details.
This should be the NDG to which the DCR Master server is added. CiscoWorks Assistant will convert
the server you add here too into ACS mode, on a successful completion of the Manage Servers workflow.
Step 4 Click Next to continue.
CiscoWorks server is contacted to validate the Device and Credential Repository settings, and to fetch
the Certificate information. See Accepting Certificate Information for details.
Step 1 Enter the SMTP server details in the SMTP Server field.
This is the system-wide name of the SMTP server used by CiscoWorks applications to deliver reports.
The default server name is localhost.
Step 2 Enter the e-mail ID in the CiscoWorks E-mail ID field.
This is the CiscoWorks e-mail ID from which applications send e-mail notifications. There is no default
e-mail ID.
These fields will be already populated if the SMTP server and e-mail ID have been set up in the Common
Services > Server > Admin > System Preferences screen or using the LMS Setup Center.
Step 3 Click OK.
Step 1 Select CiscoWorks Assistant > Workflows > Server Setup > Manage Servers.
Step 2 Select the server by clicking the Host Name/IP Address radio button.
The Edit Server dialog box appears.
This dialog box has pre-populated values in Hostname/IP address, Port and SSO Current Settings fields.
All fields in the Edit Server dialog box can be edited, except the Hostname/IP address and SSO settings
fields
If the server is in SSO Slave mode, you can set is as SSO Master, by selecting the Set as Master check
box.
If the server is in SSO Master Mode, you can change it to Slave mode by selecting the Set as Slave check
box. The Set as Slave check box is not present in the local server.
Step 3 Enter the Server Details and Setup parameters in Edit Server dialog box.
Step 4 Click OK.
The Current System Identity User pop-up appears.
Step 5 Click OK after you enter the System Identity User details.
The New System Identity User pop-up window appears.
Step 6 You can either:
• Enter the new System Identity Username and Password, confirm Password, and click OK
Or
• Click Cancel to proceed, if you do not want to change the current System Identity User.
The Device Management Mode page appears.
Step 7 Click Next, after you modify the Device Management Mode.
See for Setting and Editing the Device Management Mode more information.
If you do not want to change the settings, click Next when you get to this page without making any
modifications to the existing Device Management mode. The Skip button is disabled in this page.
The workflow initiates after you click Next button. The modifications you made are saved when the tasks
are complete.
Deleting a Server
To delete a server from the setup:
Step 1 Select CiscoWorks Assistant > Workflows > Server Setup > Manage Servers
Step 2 Select the server by clicking the Host Name/IP Address radio button.
Step 3 Click Delete.
The Delete Confirmation popup appears.
Step 1 Select the server by clicking the Host Name/IP Address radio button.
Step 2 Click Undelete.
Note The Undelete button appears only if you select a server that is marked for deletion.
If you try to add a server that is marked for deletion back to the set up again using the Add button, the
Undelete Confirmation pop-up is displayed. Click OK to retain the server in the setup.
After the server is deleted from the setup, the deleted server goes into the DCR Standalone and SSO
Standalone modes. The workflow also removes the Trust that is set up from all the deleted servers.
You cannot remove the local server from the setup.
If you remove the SSO Master, you can assign any other server as the SSO Master. If you do not select
another server as the SSO Master, the workflow will assign the local server as the SSO Master. If you
remove the SSO Master, the Multi-server setup is not removed.
Step 1 Select CiscoWorks Assistant > Workflows > Server Setup > Manage Servers.
Step 2 Click Next.
The Current System Identity User Setup dialog box appears
This dialog box appears only when the admin user details are not entered for at least one of the servers.
If the admin user details are entered for all servers, the New System Identity Setup page appears.
Step 3 Enter the current System Identity username and Password in the text field.
Step 4 Click OK to continue.
The New System Identity Setup page appears.
If you want to change the System Identity setup values, enter the new System Identity Username and
Password in the text field, re-enter the password in the confirm password field, and click Next to
complete the System Identity User setup.
CiscoWorks Assistant ensures the new user you create has all the necessary privileges. CiscoWorks
Assistant ensures the new user you create has all privileges.
Otherwise, click Skip.
To set up, or edit the Device Management Mode page, click Next.
Step 1 Click Next, after adding the server or setting up the System Identity User.
The Device Management Mode page appears.
The possible modes are:
• Auto Management— If any new devices are added in DCR, these devices are also added in the
application automatically.
• Manual Allocation—You can use this option to selectively add devices to the application from DCR
or when you have deleted devices in the application and you want to re-add those devices to the
application.
By default, the Device Management Mode shows the current status of device management mode of
applications that have been set up in their respective Device Management Settings pages.
Step 2 Select Manual Allocation or Auto Management from the drop down list for each CiscoWorks server
application.
Step 3 Click Next.
The workflow executes the assigned tasks when you click Next in the Device Management Mode page.
The Manage Servers progress page displays the Server Management status. See Viewing Server
Management Status.
Step 1 Select the Notify me when Manage Servers tasks are complete check box, and click OK.
Step 2 Enter the e-mail ID in the text field.
The e-mail ID will be displayed in the text field if you had entered an e-mail ID in the Manage Servers
flow. Only one e-mail ID is allowed.
The e-mail ID can contain alphabets, numbers, and special characters ($, _, ^, &, #).
For example:
• user_cwa1@cisco.com
• Name_12#@abc.co.in
Step 1 Select CiscoWorks Assistant > Workflows > Server Setup > Set Default Credentials.
The Default Credentials page appears.
You can:
• Set Standard credentials (SeeSetting Standard Credentials)
• Set SNMP credentials (See Setting SNMP Credentials)
• Set HTTP credentials (See Setting HTTP Credentials)
• Set Auto Update Server managed Device Credentials (See Setting Auto Update Server)
• Set Rx Boot Mode credentials (See Setting Rx Boot Mode Credentials)
Click Next to go to the Add Devices step. See Adding Devices for details.
Step 1 Select the Notify me when Set Default Credentials tasks are complete check box, and click OK.
Step 2 Enter the e-mail ID in the text field.
The e-mail ID will be displayed in the text field if you had entered an e-mail ID in the Manage Servers
flow. Only one e-mail ID is allowed.
The e-mail ID can contain alphabets, numbers, and special characters ($, _, ^, &, #).
For example:
• user_cwa1@cisco.com
• Name_12#@abc.co.in
Adding Devices
You can add devices to the Device and Credentials Repository (DCR) using the following methods:
• Bulk Import from File (See Adding Devices Using Bulk Import From File)
• Bulk Import from Network Management Station (NMS) (See Adding Devices Using Bulk Import
From NMS)
• Campus Device Discovery (See Adding Devices Using Campus Device Discovery)
CiscoWorks Assistant allows you to add devices using multiple methods simultaneously. You can add
devices using the Import from File feature, and Campus Device Discovery at the same time.
Campus Device Discovery can be run only if Campus Manager is installed in the CiscoWorks server. It
can be installed either on a local or on a remote server.
You can also:
• View Add Devices Status (See Viewing Add Devices Status)
• Set SNMP Parameters (See Setting SNMP V2 Parameters)
• Delete SNMP Details (See Deleting SNMP V2 Details and Deleting SNMP V3 Details)
To add devices you can either:
• Select CiscoWorks Assistant > Workflows > Server Setup > Add Devices
Or
• Select Manage Servers, and continue in the wizard mode.
Step 1 Select the Import From File check box from the Select Methods pane, and click the Import From File
link.
The File Information pane appears. This is the default.
Step 2 Enter the file name.
Or
a. Click Browse
The Server Side File selector dialog box appears
b. Select the filename
The Server Side File Selector dialog box displays the files from the remote server on which the Server
Setup workflow is running.
Step 3 Select either CSV or XML file formats.
Only CSV 2.0 and CSV 3.0 file formats are supported.
See the User Guide for CiscoWorks Common Services 3.1 for sample CSV and XML files.
Step 4 Select either the Use data from Import source or the Use data from Device and Credential
Repository, to resolve conflicts that may occur if the devices are present both in the import source and
DCR, but differ in their attributes.
• If you select Use data from Import source, the credentials from the import source will be used, and
credentials for the device in DCR will be modified.
• If you select Use data from Device and Credential Repository, the device credentials in DCR will
be used.
Step 5 Select the Use Default Credentials check box to use the default credentials to import the devices.
• If your import source does not have the required device credentials, and if you have opted to use
default credentials, the device information will be imported into DCR with default credentials
values.
• If your import source has the required device credentials and if you have opted to use default
credentials, the device information will be imported into DCR with the values specified in the import
source.
Step 1 Select the Import From NMS check box from the Select Methods pane, and click the Import From NMS
link.
Step 2 Select the Network Management System type from the NMS type drop-down list. HPOV6.x and
Netview7.x are supported.
Step 3 Enter the installation location of Network Management System in the Install Location field.
For example: C:\Program Files\HP OpenView
Step 4 Select either the Use data from Import source or the Use data from Device and Credential Repository, to
resolve conflicts that may occur if the devices are present both in the import source and DCR, but differ
in their attributes.
• If you select Use data from Import source, the credentials from the import source will be used, and
credentials for the device in DCR will be modified.
• If you select Use data from Device and Credential Repository, the device credentials in DCR will
be used.
Step 5 Select the Use Default Credentials check box to use the default credentials to import the devices.
• If your import source does not have the required device credentials, and if you have opted to use
default credentials, the device information will be imported into DCR with the default credentials
values.
• If your import source has the required device credentials and if you have opted to use default
credentials, the device information will be imported into DCR with the values specified in the import
source.
Step 1 Select the Import From NMS check box from the Select Methods pane, and click the Import From NMS
link.
Step 2 Select the Remote NMS check box.
Step 3 Select the Network Management System type from the NMS type drop-down list. HPOV6.x, Netview7.x
and ACS are supported.
Step 4 Select the Operating System type from the OS type drop-down list.
Step 5 Enter the host name, root username, and install location in the corresponding fields.
If you select the NMS type as ACS, enter the root password, port and protocol along with the hostname
and root username in the corresponding fields.
Step 6 Select either the Use data from Import source or the Use data from Device and Credential Repository
radio button, to resolve conflicts that may occur if the devices are present both in the import source and
DCR, but differ in their attributes.
• If you select Use data from Import source, the credentials from the import source will be used, and
credentials for the device in DCR will be modified.
• If you select Use data from Device and Credential Repository, the device credentials in DCR will
be used.
Step 7 Select the Use Default Credentials check box to use the default credentials to import the devices.
• If your import source does not have the required device credentials and if you have opted to use
default credentials, the device information will be imported into DCR with the default credentials
value.
• If your import source has the required device credentials and if you have opted to use default
credentials, the device information will be imported into DCR with the values specified in the import
source.
Step 1 Select the Run Discovery on host_name check box, and click the Run Discovery on host_name link.
This option is available only if Campus Manager is installed on the server.
The Discovery window appears with the following tabs.
• Seed Devices tab
• SNMPV2 tab
• SNMPV3 tab
• Discovery Settings tab
• Configure Range tab
Step 2 Enter the following details to specify the Discovery settings. See the User Guide for Campus Manager
for more information on the Discovery Settings
Seed Devices tab
• IP Address/Host Name
a. Specify the IP Address/Host Name in the text field
b. Click Add to add the device in the device list.
To delete a device, select it, and click Delete.
• Added Device List—Lists the devices that are added to the server.
• Browse—Click Browse to enter seed devices in a file. The file browser displays only the files on the
local server. It does not display any files that are on the remote server.
SNMPV2 tab
• Enable Multiple Community Strings—Select the check box to enable multiple community strings.
You can provide multiple community strings for the same IP address range. Each string is tried for
reachability until the correct string is found.
For example: 10.*.*.* public1 and 10.*.*.* public2
• Encrypt Community Strings —Select the check box to enable encryption of community strings.
Community strings are stored in the system in the encrypted format.
• Target—Target device.
• IP Address/Host Name:
– To add the device to the Added Device IP List enter an IP address or a range of IP addresses to
limit Discovery and click Add.
– To delete a device from the Device IP List, select a device from the Added Device IP List, and
click Delete.
Step 3 Click Next to complete the Add Devices step.
The Add Devices Progress page appears. You can view the device addition status in this page.
See Viewing Add Devices Status for details.
Step 1 Select the Run Discovery on host_name check box, and click the Run Discovery on host_name link.
Step 2 Click the SNMP V2 tab.
Step 3 Click Add to add the SNMP settings.
The SNMP V2 popup appears.
Step 4 Enter the following details in the popup:
• Target—Target device
• Read Community—Read community string.
• Timeouts—Time period after which the query times out.
• Retries—Number of attempts.
• Comments—Remarks, if any.
Step 5 Click either
• OK to save the changes
Or
• Cancel to exit.
Step 6 Select a row, and click Edit to edit the community strings.
The SNMP V2 popup appears with the existing values.
Step 7 Edit the details in the popup and click either:
• OK to save the changes
Or
• Cancel to exit.
Step 8 Select a row, and click Delete to delete the community string.
Step 1 Select the Run Discovery on host_name check box, and click the Run Discovery on host_name link.
Step 2 Click the SNMP V3 tab.
Step 3 Click Add to add the SNMP settings.
The SNMP V3 popup appears.
Step 4 Enter the following details in the popup
• Target—Target device
• Username—Name of the user who has access to the views configured on the device.
• Password—Password of the user.
• Timeouts—Time period after which the query times out.
• Retries—Number of attempts.
• Authentication—Method of authentication. Either SHA-1 or MD5.
• Comments—Remarks, if any.
Step 5 Click either:
• OK to save the changes
Or
• Cancel to exit.
Step 6 Select a row, and click Edit to edit the community strings.
The SNMP V3 popup appears with the existing values.
Step 7 Edit the details in the popup and click either:
• OK to save the changes
Or
• Cancel to exit.
Select a row, and click Delete to delete the community string.
Click Next to go to Manage Devices Tasks. See Managing Devices for details.
Step 1 Select the Notify me when Add Devices tasks are complete check box, and click OK.
Step 2 Enter the e-mail ID in the text field.
The e-mail ID will be displayed in the text field if you had entered an e-mail ID in the Manage Servers
flow. Only one e-mail ID is allowed.
E-mail ID can contain any characters, numbers, and special characters ($, _, ^, &, #).
For example:
• user_cwa1@cisco.com
• Name_12#@abc.co.in
Step 1 Select the Run Discovery on host_name check box, and click the Run Discovery on host_name link.
Step 2 Click the SNMP V2 tab.
Step 3 Select the row to be deleted.
Step 4 Click Delete.
The Delete SNMP V2 Confirmation dialog box appears.
Step 5 Click OK in the Delete SNMP V2 Confirmation dialog box.
Step 1 Select the Run Discovery on host_name check box, and click the Run Discovery on host_name link.
Step 2 Click the SNMP V3 tab.
Step 3 Select the row to be deleted.
Step 4 Click Delete.
The Delete SNMP V3 Confirmation dialog box appears.
Step 5 Click OK in the Delete SNMP V3 Confirmation dialog box.
Managing Devices
This page helps you to allocate devices to be managed by the applications installed in the CiscoWorks
servers. The page lists the CiscoWorks servers and the applications that are present in each server. You
can select devices from the device selector and add it to the application with which you want the device
to be managed.
You can also:
• View device management status (See Viewing Manage Devices Status)
• Use Device Selector to search for devices in DCR (See About Device Selector)
To manage devices:
Step 1 Select CiscoWorks Assistant > Workflows > Server Setup > Manage Devices.
The Manage Devices page appears.
Step 2 Select the applications to which you want to allocate the device
Initially, devices must be added to DCR. After a device is added to DCR, you can add it to the
applications.
Step 3 Click Add Devices to add,
Or
Click Reset to reset the added devices in the application.
The Manage Devices screen displays:
• LMS Server—LMS Server IP Address
• Applications—Applications installed in the LMS Server
• Selected Device(s)—Number of devices selected to add in that application
Step 4 Click Next to complete the Manage Devices tasks.
The Device Management Progress page appears. You can view the Device Management status in this
page. See Viewing Manage Devices Status for details.
Click Next to go to the Change ACS Setup tasks. See Changing ACS Setup for details.
Step 1 Select the Notify me when Manage Devices tasks are complete check box, and click OK.
Step 2 Enter the e-mail ID in the text field.
The e-mail ID will be displayed in the text field if you had entered an e-mail ID in the Manage Servers
flow. Only one e-mail ID is allowed.
The e-mail ID can contain alphabets, numbers, and special characters ($, _, ^, &, #).
For example:
• user_cwa1@cisco.com
• Name_12#@abc.co.in
The following tasks need to be performed to add CiscoWorks server as an AAA client:
Step 1 In the Cisco Secure ACS navigation bar, click Network Configuration.
The Network Configuration page appears.
Step 2 Do either of the following:
• If you are using Network Device Groups (NDGs), click the name of the NDG to which the AAA
client is to be assigned. Then, click Add Entry below the AAA Clients table.
If NDG option is not visible, you can enable Network Device Groups in ACS under Interface
Configuration > Advanced.
Or
• Click Add Entry below the AAA Clients table, to add an AAA client when you have not enabled
NDGs.
The Add AAA Client page appears.
Step 3 In the AAA Client Hostname box, type the name of your CiscoWorks server (up to 32 characters).
Step 4 In the AAA Client IP Address box, enter the IP address of your CiscoWorks server.
Step 5 In the Key box, type the shared secret key that your CiscoWorks server and ACS use to encrypt the data.
Step 6 From the Authenticate Using list, select TACACS + (CiscoIOS) as the network security protocol used
by the AAA client.
Step 7 Click Submit + Restart.
Apart from adding your CiscoWorks server as an AAA client, you also need to add the devices to be
managed by the CiscoWorks server as AAA clients to Cisco Secure ACS. When you are integrating with
Cisco Secure ACS, your devices will not be visible from your CiscoWorks server if you have not added
them as AAA clients in Cisco Secure ACS.
For information on adding network device groups and AAA client configuration, see the Network
Configuration section of the User Guide for CiscoSecure ACS 4.1.
To change ACS settings:
Step 1 Select CiscoWorks Assistant > Workflows > Server Setup > Change ACS Setup.
The Change ACS Setup page appears.
Change ACS Setup page contains these ACS Mode Status details.
• Server—Name or IP Address of the Server.
• Mode—The current mode of the Server. It can be ACS or Non-ACS.
If the mode is ACS, there will be a link. Click the link to view the ACS Connection Status for the server.
Step 2 Select the Change mode to ACS check box in the Login Module pane to change the login mode to ACS.
If the server is in ACS mode, the Change ACS Setup page will contain ACS tasks pane instead of Login
Module pane. ACS tasks pane has these radio buttons
• Update ACS Configuration (See Updating ACS Configuration.)
• Assign Group for missing devices (See Assigning Device Group.)
Step 1 Select CiscoWorks Assistant > Workflows > Server Setup > Change ACS Setup.
The Change ACS Setup page appears.
Step 2 Select the Change Mode to ACS check box and click Next to go the Configure ACS Mode page.
Note Ensure that the local server is an AAA client to ACS server.
Step 3 Click OK on the Notification pop-up window to continue with the ACS Mode change.
Step 4 Enter the required information in the ACS Mode Setup table to change the login mode to ACS.
Field Description
Server Details
Primary IP Address/Hostname Enter the Primary IP Address/Hostname of the ACS server
ACS TACACS+ port Enter the ACS TACACS+ port number.
The default port number is 49. You can change the port based on
the value configured in ACS.
Secondary IP Address/Hostname Enter the Secondary IP Address/Hostname of the ACS server.
ACS TACACS+ port Enter the ACS TACACS+ port number.
The default port number is 49. You can change the port based on
the value configured in ACS.
Tertiary IP Address/Hostname Enter the Tertiary IP Address/Hostname of the ACS server
ACS TACACS+ port Enter the ACS TACACS+ port number.
The default port number is 49. You can change the port based on
the value configured in ACS.
Login
ACS Admin Name Enter the administrator username in ACS
ACS Admin Password Enter the administrator password in ACS
Confirm Password Re-enter the administrator password in ACS
ACS Shared Secret Key Enter the secret key shared between ACS and the CiscoWorks
server.
Confirm Key Re-enter the ACS shared secret key
System Identity
User Name Enter the system identity user name. This user should be already
configured in ACS, with all privileges.
Password Enter the system identity password value
Confirm Password Re-enter the password.
Field Description
Network Device Group Name
Network Device Group Name Enter the Network Device Group Name value. Network Device
Group name should present in the ACS.
This field appears only in a Multi-server set up, when you change
the mode of a Slave. The local server (DCR Master) should be
manually added as an AAA client in ACS, before you change
mode to ACS. The workflow converts the other servers part of the
Multi-server to ACS mode and also add missing devices to the
NDG you specify here.
Step 5 Select the Register all installed applications with ACS check box, if you are registering the applications
for the first time.
In case an application is already registered with ACS, the current registration will overwrite the previous
registration. When you select the Register all installed applications with ACS check box, you are
prompted to confirm whether you want to continue with the settings.
See Common Services Online Help for details.
Step 6 Select the HTTP or HTTPS radio button under Current ACS Administrative Access Protocol.
Step 7 Click Next to complete the Mode change.
The Configure ACS Mode Progress page is displayed. You can view the ACS mode configuration status
in this page. See Viewing the Configure ACS Mode Status for details.
Note Restart Daemon Manager after you create the System Identity User in ACS, and assign the Super Admin
role for the changes to take effect.
The final step in integrating CiscoWorks Common Services Software with Cisco Secure ACS is to
configure the CiscoWorks users within Cisco Secure ACS. Cisco Secure ACS allows you to define access
permissions and policies for the registered CiscoWorks applications on a per user basis or user group
basis.
See the following sections of the Cisco Secure ACS User Guide for more information on managing users
and user groups:
• User Group Management
• User Management
When adding the user, you can configure access policies to define what the user is authorized to do
depending on the role.
See Configuring Users in ACS section in User Guide for CiscoWorks Common Services 3.1 for
information on:
• Assigning Privileges in ACS
• Creating and Modifying Roles in ACS
See also the white paper on CiscoWorks LMS Integration with Cisco Secure ACS, available on cisco.com
Step 1 Select the Notify me when ACS tasks are complete check box, and click OK.
Step 2 Enter the e-mail ID in the text field.
The e-mail ID will be displayed in the text field if you had entered an e-mail ID in the Manage Servers
flow. Only one e-mail ID is allowed.
The e-mail ID can contain alphabets, numbers, and special characters ($, _, ^, &, #).
For example:
• user_cwa1@cisco.com
• Name_12#@abc.co.in
Step 1 Click Next, after the Configure ACS Mode tasks are complete.
The Configure ACS Mode result page appears with the following popup message:
Make sure the configured System Identity User is available in ACS Server.
Restart the LMS Daemon Manager for the ACS Change to take effect.
• On Windows:
Run net stop CRMdmgtd or net stop crmdmgtd
• On Windows:
Run net start CRMdmgtd or net start crmdmgtd
Step 1 Select CiscoWorks Assistant > Workflows > Server Setup > Change ACS Setup
The Change ACS Setup page appears.
Step 2 Select the Update ACS Configuration radio button from the ACS Tasks pane.
The Update ACS Configuration check box appears in the ACS Tasks pane only if the server is in ACS
mode.
Step 3 Click Next.
The following popup message appears:
Please ensure that local server is an AAA client to ACS server.
Step 4 Click OK to continue.
The Configure ACS Mode page appears with the pre-populated values in the ACS Mode Setup.
Step 5 Enter the new details in the ACS Mode Setup window.
You need to provide the current System Identity Username and Password. The NDG should be already
be preset in ACS. You must also provide the Shared Secret key.
Step 6 Click Next to complete updating ACS configuration.
Step 7 Restart Daemon Manager for the changes to take effect.
Step 1 Select CiscoWorks Assistant > Workflows > Server Setup > Change ACS Setup
Step 2 Select the Assign group for missing devices radio button in the ACS Tasks pane.
Step 3 Click Next.
The Assign Device Group page appears.
Step 4 Enter the following information in the Export Devices to ACS table to add the missing devices into ACS:
• Server details—The IP address and port number of the ACS server.
• Login details—The ACS administrator name, password, and the shared secret key.
• Current ACS Administrative Access Protocol—The protocol used to connect to ACS server.
• Network Device Group name—The NDG to which you want to add the missing devices.
Step 5 Click Next to complete assigning device group.
Step 6 Stop daemon manager.
• On Solaris:
Run /etc/init.d/dmgtd stop
• On Windows:
Run net stop CRMdmgtd or net stop crmdmgtd
• On Windows:
Run net start CRMdmgtd or net start crmdmgtd
Session Details
The Session Details table displays the Start Time and the User Name for the current session.
Server Summary
The Server Summary lists all the servers in the setup. The fields in the Server Summary and their
descriptions are given below.
• LMS Server—Host Name or IP Address of the server.
• Protocol—Protocol of the server can be HTTP or HTTPS
• Port—Port Number of the CiscoWorks server.
• DCR—DCR mode of the server. Mode can be DCR Master, Slave, or Standalone.
• SSO—SSO mode of the server. SSO Mode can be Master, Slave, or Standalone.
When you click the Expand button of the CiscoWorks server, it lists the applications installed in that
server.
ACS Summary
The ACS Summary table lists all the servers and their current mode. The mode can be ACS or Non-ACS.
Operation Summary
The Operation Summary tables display the tasks that you performed during the Server Setup workflow.
The fields in the Operation Summary, and their descriptions are given below
• Step—Step Name of the workflow.
• Last run—Date and Time when the step was executed.
• Details—Click the View link to view the Step Summary dialog box.
Click Finish to go to the Server Setup home page and end the current session.
Cisco Works Assistant helps you collect troubleshooting information from all the servers part of the
Multi-server set up and display reports.
For Device Troubleshooting workflow and End Host/IP Phone down workflow to work in a Multi -server
set up, you must have configured Single Sign-on.
You should also have the same System Identity User configured across all servers part of the set up.
The following sections help you understand the Troubleshooting Workflow
• Generating Device Troubleshooting Report
Also see, Understanding the Device Troubleshooting Report
• Generating End Host Down/IP Phone Down Report
Also see,
– Understanding the End Host Down Report
– Understanding the IP Phone Down Report
Note You must install Campus Manager, DFM and RME to view all these details. If these applications are not
installed, some of the reports will not be generated.
Note View Permission Report (Common Services > Server > Reports) to check if you have the required
privileges to perform this task.
E-mail ID This field is enabled only if you have selected the Notify me on Workflow
Completion field.
Enter an E-mail ID. You cannot enter multiple e-mail IDs.
For example:
• john@abc.com
• john_smith@abc.co.in
Device Information
This table contains the device information as available in Device and Credential Repository (DCR):
Connectivity Status
This table contains the device connectivity information.
To know more about device connectivity tools, see the User Guide for Common Services at this location:
http://www.cisco.com/en/US/products/sw/cscowork/ps3996/products_user_guide_list.html
Syslog Messages
This table contains the Syslog messages that are received in the past 24 hours, from the scheduled time
of the report. This information is taken from the RME database. The report shows the latest ten Syslog
messages.
To know more about Syslog Changes, see the User Guide for Resource Manager Essentials at this
location:
http://www.cisco.com/en/US/products/sw/cscowork/ps2073/products_user_guide_list.html
Device Alerts
This table contains the alerts that are received in the past 24 hours, from the scheduled time of the report.
The report shows the latest ten Alerts.
The Alerts provides a consolidated real-time view of the operational status of your network. When a fault
occurs in your network, DFM generates an event. All events occurring on the same device are rolled up
into a single alert.
To know more about device alerts, see the User Guide for Device Fault Manager at this location:
http://www.cisco.com/en/US/products/sw/cscowork/ps2421/products_user_guide_list.html
Field Description
Device Name Display Name of the device as entered in DCR.
Click on the device name to launch the Device Center.
User Name Name of the user who performed the change. This is the name entered when the user logged in. It
can be the name under which the RME application is running, or the name using which the change
was performed on the device.
Field Description
Application Name Name of the RME application involved in the network change.
For example, Archive Mgmt, ConfigEditor, CwConfig, etc.
Host Name Host name of the machine from which the user accessed the device or the host name of the RME
server.
Creation Time Date and time at which the application communicated the network change or when Change Audit
saw the change record.
Connection Mode Connection mode through which the change was made. For example, Telnet, SNMP, or console.
The mode is obtained by querying the device and if the query fails, default or NA is shown.
Message Brief summary of the network change.
Details Application details for a particular device displayed in a separate browser window.
Select the highlighted Details text to view application details in a separate browser window.
Applications that make or detect changes in the network log a change record in Change Audit log
and provide a means for getting to the detailed data.
The following information is displayed when you click on the Details link for:
• Archive Mgmt, ConfigEditor, CwConfig, and NetConfig—The Config Diff Viewer window is
displayed.
• ICServer—The Inventory Change report is displayed.
This window shows the changed values (previous and current value) of different Inventory
entitites such as FlashDevice, FlashPartition, FlashFile.
• Software Management—The Software Modification History report is displayed.
This window shows the changed software image details.
Grouped Records Similar change details grouped by the same job ID and the same function ID (for example:
inventory collection) displayed in a separate summary window.
Select the highlighted More Records text in the Grouped Records column to view similar change
details in a frame below the summary window.
For example, you have completed a software update on five devices. The Change Audit report
shows the Software Management summary information about who performed the job, when, and so
on.
To display all devices affected by this upgrade, click More Records to display the summary
information related to the five devices. From here you can look at details of the individual device
upgrades.
To know more about Change Audit, see the User Guide for Resource Manager Essentials at this location:
http://www.cisco.com/en/US/products/sw/cscowork/ps2073/products_user_guide_list.html
To know more about device discrepancies, see the User Guide for Campus Manager at this location:
http://www.cisco.com/en/US/products/sw/cscowork/ps563/products_user_guide_list.html
Note You must install Campus Manager to generate the End Host Down/IP Phone Down report.
Note View Permission Report (Common Services > Server > Reports) to check if you have the required
privileges to perform this task.
Step 1 Select CiscoWorks Assistant > Workflows > End Host Down/IP Phone Down.
The End Host Down/IP Phone window appears.
Step 2 Enter the following details:
Report from End Host/IP Phone Down Workflow for device (Test Device):
Regards,
CiscoWorks Assistant.
E-mail ID This field is enabled only if you have selected the Notify me on Workflow Completion
field.
Enter an E-mail ID. You cannot enter multiple e-mail IDs.
For example:
• john@abc.com
• john_smith@abc.co.in
Field Description
IP Address IP Address of the End Host.
Device Name Display Name of the device as entered in DCR. This field will be
displayed only if the devices are present in DCR.
Device Type Device Type Information.
For example, Cisco Catalyst 3524 PWR XL Switch, etc.
This field will be displayed only if the devices are present in DCR.
Field Description
Campus Manager IP Address of Campus Manager server.
Switch Address Switch IP Address.
Port Number Port number to which the End Host is connected.
Field Description
Last Seen Date and time when User Tracking last found an entry for this user or host in a
switch. Last Seen is displayed in the format dd mon yyyy hh:mm:ss.
Mac Address Media Access Control (MAC) address of network interface card in end-user
node.
For Ethernet topology the MAC address appears in the format,
xx-xx-xx-xx-xx-xx.
For Token Ring topology the MAC address appears in the format,
xx:xx:xx:xx:xx:xx.
IP Phone Details
This table contains the following details:
Field Description
Name This is displayed only if you have selected IP Address as the Input Type
while generating the IP Phone report.
Phone Number Phone Number of the IP Phone.
This is displayed only if you have selected Phone Number as the Input
Type while generating the IP Phone report.
IP Address IP Address of the IP Phone.
Field Description
Campus Manager IP Address of Campus Manager server.
Switch Address Switch IP Address.
Port Number Port number to which the End Host is connected.
Last Seen Date and time when User Tracking last found an entry for this user or host in a
switch. Last Seen is displayed in the format dd mon yyyy hh:mm:ss.
MAC Address Media Access Control (MAC) address of network interface card in end-user
node.
For Ethernet topology the MAC address appears in the format,
xx-xx-xx-xx-xx-xx.
For Token Ring topology the MAC address appears in the format,
xx:xx:xx:xx:xx:xx.
Cisco Call Manager IP address of the Cisco CallManager.
Field Description
Switch Check Connectivity status of the device
Ping Displays the ping status of the selected device.
Checks whether the device is reachable. A ping tests an ICMP echo message
and its reply.
Trace route Displays the trace route status of the selected device.
Detects routing errors between the network management station and the target
device.
UDP Displays the ping status of the selected device.
Sends an echo request to UDP port 7.
TCP Displays the ping status of the selected device.
Sends an echo request to TCP port 7.
HTTP Displays the ping status of the selected device.
Sends an HTTP request to the HTTP port 80 of the destination device.
TFTP Displays the ping status of the selected device.
Sends a TFTP request to the TFTP port (69) of the destination device.
SNMP Displays the SNMP status (service test, port 161) of the selected device.
Sends an snmp get request to the destination device for an SNMP read test
(SNMPR).
It also sends an snmp set request to the device to test SNMP write (SNMPW).
This protocol is supported for the versions of v1, v2c, and, v3.
Telnet Displays the Telnet status (service test, port 23) of the selected device.
Checks whether Telnet is enabled on the device and if the destination device
responds to a Telnet request. It does not verify that the Telnet password in the
database works.
SSH Displays the SSH status (service test, port 22) of the selected device.
Checks whether SSH is enabled on the device. If the destination device
responds to SSH requests, this also tests whether CiscoWorks server can make
SSH requests to that device. It does not verify the password in the database.
• Report on Recently Down Ports—Campus Manager generates report for the ports, which were
earlier connected to a device or end host, but are not connected when the last User Tracking
Acquisition was completed.
For more information on Switch Port, see the User Guide for Campus Manager:
http://www.cisco.com/en/US/products/sw/cscowork/ps563/products_user_guide_list.html
Rediscover
You can view the rediscovery information of the End Host/IP Phone. This information is available only
if you have selected the Rediscover option while generating the End Host Down/IP Phone Down report.
A P P E N D I X A
Troubleshooting CiscoWorks Assistant
Q. I am not able to view some of information in Device Troubleshooting report. What is the issue?
A. The Device Troubleshooting report depends on the following LMS 3.0 applications. Ensure that you
have installed all of these applications:
– Campus Manager 5.0 (CM 5.0)
– Resource Manager Essentials 4.1(RME 4.1)
– Device Fault Manager 3.0 (DFM 3.0)
Q. I am not able to run the End Host/ IP Phone report. What is the problem?
A. The End Host/IP Phone report depends on Campus Manager 5.0. You must install Campus Manager
application to run this report.
B E TA D R A F T — C I S C O C O N F I D E N T I A L
Error
Message ID Error Message Probable Cause Possible Action
CWA0 Unexpected error — Please contact the CiscoWorks server
occurred. administrator.
CWA026 Error while saving log Could not save the new log Please contact the CiscoWorks server
level. level into the property file. administrator.
CWA100 CWA Internal error. Invalid XML character in Please try again.
Data fetched is in invalid the data.
XML format.
CWA101 Could not get the details CWA engine may not be Check if these processes are running,
from the database. running. OpsxmlDbEngine, OpsXMLRuntime and
ProcSysBus (Common Services > Server > Admin
> Processes) and please try again.
If these processes are not running, restart these
processes.
CWA102 Could not update the CWA engine may not be Check if these processes are running,
database with new values. running. OpsxmlDbEngine, OpsXMLRuntime and
ProcSysBus (Common Services > Server > Admin
> Processes) and please try again.
If these processes are not running, restart these
processes.
CWA104 Could not get the logged Browser session terminated. Please log in again.
in user details.
CWA105 Multiple instance of Server setup workflow was Please contact the CiscoWorks server
Server Setup workflow triggered simultaneously by administrator to end the sessions.
exists. two users.
CWA106 CWA Internal error. Could Invalid XML character in Please try again.
not parse the XML the data.
content.
CWA108 Session timed out. Browser session expired. Please log in again.
CWA109 Could not get the CWA engine is not Restart these processes, OpsxmlDbEngine,
workflow instance details. accessible. OpsXMLRuntime and ProcSysBus (Common
Services > Server > Admin > Processes).
CWA110 Could not fetch the server CWA engine is not Restart these processes, OpsxmlDbEngine,
details. accessible. OpsXMLRuntime and ProcSysBus (Common
Services > Server > Admin > Processes).
CWA111 Session was ended by Another user has ended the Please contact the CiscoWorks server
another user. active session and started a administrator
new session.
CWA112 Operation in progress. Same user with multiple Please try after the operation has completed.
browser session.
B E TA D R A F T — C I S C O C O N F I D E N T I A L
Error
Message ID Error Message Probable Cause Possible Action
CWA113 Could not get the CWA engine is not Restart these processes, OpsxmlDbEngine,
workflow instance details. accessible. OpsXMLRuntime and ProcSysBus (Common
Services > Server > Admin > Processes).
If the problem persists, contact the CiscoWorks
server administrator.
CWA114 Invalid workflow instance Workflow instance of CWA Please contact the CiscoWorks server
state. engine is in consistent state. administrator to end the session.
CWA115 Workflow instance not Workflow instance details Please contact the CiscoWorks server
active. were removed from CWA administrator to end the session.
engine.
CWA116 Invalid page request. — Please try again.
CWA117 Could not get the details Browser session expired. Please log in again.
for the session.
CWA118 ACS server is not ACS server is down or you Enter valid ACS server details and make sure that
reachable. have entered invalid ACS the ACS server is running.
server details.
CWA119 Network Device Group No Network Device Group Create the Network Device group in the ACS
does not exist in ACS specified for ACS server. server.
server.
CWA120 Could not fetch ACS Either the: Make sure that the LMS server is in ACS mode
status. and reachable.
• LMS server is not in
ACS mode. Please try again.
Or
• LMS server is
unreachable.
CWA121 Error while DCRServer or Restart the DCRServer or the DFMOGSServer
communicating with the DFMOGSServer process is process.
DCRServer or the not running in the LMS
(Common Services > Server > Admin >
DFMOGSServer process. server.
Processes).
CWA122 Error while saving log Could not save the new log Please contact the CiscoWorks server
level. level into the property file. administrator.
CWA123 Could not login to remote Either the server is not Please ensure that the server is reachable, Single
server as System Identity reachable or you have not Sign On is configured and try again.
User. configured Single Sign-On.
CWA124 Error while Either the DCR Master is Make sure that DCR Master is reachable.
communicating with not reachable or the
Restart the DCRServer process (Common
DCR. DCRServer process in not
Services > Server > Admin > Processes).
running on the LMS server.
B E TA D R A F T — C I S C O C O N F I D E N T I A L
Error
Message ID Error Message Probable Cause Possible Action
CWA3007 Authentication Failed — When the LMS server is in Make sure the configured System Identity User is
Access denied. ACS mode, the system available in the ACS server.
Identity User should be in If this user is not available, configure the System
the ACS server. Identity User In ACS server.
See User Guide for Common Services to configure
the System Identity User.
CWA4001 LMS server is not LMS server is unreachable. Make sure the LMS server is reachable.
reachable.
CWA4002 Cannot add peer server Certificate is not valid. Please create new certificate.
certificate.
B E TA D R A F T — C I S C O C O N F I D E N T I A L
Error
Message ID Error Message Probable Cause Possible Action
CWA4010 Cannot fetch the Peer Either the host is Make sure the host is reachable from this server
Server certificate from the unreachable or the and the certificate is valid.
host. certificate is invalid.
CWA4011 Could not create a new The user name is invalid. Enter a valid username. It should have at least five
user. characters.
CWA4012 Could not configure You have entered either an Enter a valid hostname, IP address or leave the
SMTP server address. invalid IP address or an SMTP Server field blank.
invalid hostname.
CWA4013 Could not configure Either the username does not Make sure that the user has System Identity User
System Identity User. exist or the user does not privileges.
have the System Identity
User's privilege.
CWA4014 Could not configure the The DCR Master is not Make sure the DCR Master is reachable.
LMS server as DCR reachable.
Slave.
CWA4015 Could not configure the Either System Identity User Make sure System Identity User is configured or
LMS server as Single is not configured or trust establish trust between the servers by adding Peer
Sign-On slave. between the servers is not Server certificate using Common Services >
established by downloading Server > Security > Multi-Server Trust
the certificates. Management > Peer Server Certificate Setup.
CWA4016 Could not configure the Either the ACS server is Make sure the ACS server is reachable.
LMS server to ACS mode. down or the Network Device or
Group does not exist in the
ACS server. Create the Network Device group in the ACS
server.
CWA4500 Invalid file format. Data in the selected file is Please see the online help for the correct file
not in the expected format. format and reselect the file.
CWA4501 File does not exist. You have selected a Select a file with the required permissions.
non-existent file or the
selected file or directory
does not have the required
permissions.
CWA4503 Invalid range found. Invalid IP address. Check the IP Address Range list and enter valid IP
Address.
It must be a number 0 – 255 or valid range
expression [x-y].: xxx.xx.xx.x].
CWA4504 Invalid Seed Devices Invalid IP Address. Check the seed device list and enter a valid IP
found. Address.
CWA4505 Cannot start Device Error occurred while Restart CampusOGSServer process.
Discovery in server since connecting to
(Common Services > Server > Admin >
an error occurred. CampusOGSServer process.
Processes).
B E TA D R A F T — C I S C O C O N F I D E N T I A L
Error
Message ID Error Message Probable Cause Possible Action
CWA4506 Cannot start Device Device Discovery is already Please try after the current Discovery has
Discovery in server, since in progress. completed.
another Discovery is in
progress.
CWA4510 You are not authorized to You can configure Set Please log in as administrator.
perform this task. Default Credentials only if
you have administrator
privileges.
CWA4511 Could not connect to The ANIServer process is Restart the ANIServer process (Common Services
ANIServer. not running. > Server > Admin > Processes).
CWA4512 You do not have the access You do not have the Make sure that you have the privileges to access
to local NMS server. privileges to access the local the NMS server.
NMS server.
CWA4513 You cannot configure the The server you have selected Access the DCR Master to configure the default
default credentials on a for configuring the default credentials.
DCR Slave server. credentials is a DCR Slave.
CWA4514 ANIServer is initializing. ANIServer is still Make sure that ANIServer is started and running
initializing. (Common Services > Server > Admin >
Processes).
CWA4509 Unknown Error - null — —
CWA4520 Could not add devices. — —
CWA4507 Could not import from Invalid Install location. Enter valid install location for NMS application
local NMS.
CWA4508 Import from local NMS NMS daemon may be down. Restart NMS daemon.
failed.
Table A-2 Error Messages for Device Troubleshooting and End Host/IP Phone Workflows
Error
Message ID Error Message Probable Cause Possible Action
CWA001 Cookie is not set. Session is invalid. Please log in and try again.
CWA002 Could not log in to server. No response from server. Check the server connection.
CWA003 Authentication failed. System Identity User is not Check the username and password of the System
set properly. Identity User.
You can set the System Identity User in the
Common Services application (Common Services
> Server > Security > System Identity Setup).
CWA004 Could not log in to Slave Session is invalid. Please log in and try again.
Server.
B E TA D R A F T — C I S C O C O N F I D E N T I A L
Table A-2 Error Messages for Device Troubleshooting and End Host/IP Phone Workflows
Error
Message ID Error Message Probable Cause Possible Action
CWA005 You are not authorized to You do not have the correct Please check the Permission Report (Common
access the page. privileges. Services > Server > Reports) and review the
required permissions.
Contact the CiscoWorks server administrator to
get the required permission.
CWA006 License expired. LMS application license Upgrade your LAN Management Solution license.
expired. See the User Guide for Common Services to
upgrade your license.
http://www.cisco.com/en/US/products/sw/cscowo
rk/ps3996/products_user_guide_list.html
CWA007 License expired. LMS application license Upgrade your LAN Management Solution license.
expired. See the User Guide for Common Services to
upgrade your license.
http://www.cisco.com/en/US/products/sw/cscowo
rk/ps3996/products_user_guide_list.html
CWA008 License expired. LMS application license Upgrade your LAN Management Solution license.
expired. See the User Guide for Common Services to
upgrade your license.
http://www.cisco.com/en/US/products/sw/cscowo
rk/ps3996/products_user_guide_list.html
CWA009 Internal server error. — Restart the daemon manager of the server:
On Windows:
1. Enter net stop crmdmgtd
On Solaris:
1. Enter /etc/init.d/dmgtd stop
CWA010 Error while DCR Server may be down. Start the DCR Server (Common Services > Server
communicating with DCR > Admin > Processes).
Server.
CWA011 Java exception found. — —
CWA012 Application error. — —
CWA014 No HTTP response. Server is down. Check the server connection.
CWA015 Workflow is not • Server discovery • Check the server connection.
supported. workflow could not find
• Install the required application. See
the server information.
“CiscoWorks Assistant Workflows and the
• Required application is Dependent LMS Applications”.
not installed.
• Required application
version is not installed.
B E TA D R A F T — C I S C O C O N F I D E N T I A L
Table A-2 Error Messages for Device Troubleshooting and End Host/IP Phone Workflows
Error
Message ID Error Message Probable Cause Possible Action
CWA016 HTTP parse error. — —
CWA_107 Could not launch the — Restart the daemon manager of the server:
workflow.
On Windows:
1. Enter net stop crmdmgtd
On Solaris:
1. Enter /etc/init.d/dmgtd stop
B E TA D R A F T — C I S C O C O N F I D E N T I A L
Table A-2 Error Messages for Device Troubleshooting and End Host/IP Phone Workflows
Error
Message ID Error Message Probable Cause Possible Action
CWA021 Port number for the Device port connected to the 1. Run Discovery for the device to which the
specified End Host is host is Null. End Host/IP Phone node is connected.
Null. 2. Run UT Acquisition.
See the User Guide for Campus Manager at this
location:
http://www.cisco.com/en/US/products/sw/cscowo
rk/ps563/products_user_guide_list.html
CWA022 VLAN ID for the VLAN ID associated with 1. Run Discovery for the device to which the
specified End Host is port is Null. End Host/IP Phone node is connected.
Null.
2. Run UT Acquisition.
See the User Guide for Campus Manager at this
location:
http://www.cisco.com/en/US/products/sw/cscowo
rk/ps563/products_user_guide_list.html
CWA023 Could not find the Last Date and time when User Run UT Acquisition for the device to which the
Seen information for the Tracking last found an entry End Host/IP Phone node is connected.
specified End Host /IP for End Host /IP Phone in a See the User Guide for Campus Manager at this
Phone. switch is Null. location:
http://www.cisco.com/en/US/products/sw/cscowo
rk/ps563/products_user_guide_list.html
CWA024 Campus Manager is not — —
managing the specified
End Host/IP Phone.
CWA025 Could not launch the — Restart the daemon manager of the server:
workflow.
On Windows:
• Enter net stop crmdmgtd
• Enter net start crmdmgtd
On Solaris:
• Enter /etc/init.d/dmgtd stop
• Enter /etc/init.d/dmgtd start
If the problem persists, contact the CiscoWorks
server administrator.
CWA026 Error while saving the log — Please contact the CiscoWorks server
level. administrator.
B E TA D R A F T — C I S C O C O N F I D E N T I A L
Table A-2 Error Messages for Device Troubleshooting and End Host/IP Phone Workflows
Error
Message ID Error Message Probable Cause Possible Action
CWA028 CiscoWorks Assistant — Upgrade Device Fault Manager to version
does not support the supported by CiscoWorks Assistant.
installed Device Fault See User Guide for CiscoWorks Assistant for the
Manager version. supported Device Fault Manager version.
CWA029 CiscoWorks Assistant — Upgrade Resource Manage Essentials to version
does not support the supported by CiscoWorks Assistant.
installed Resource See User Guide for CiscoWorks Assistant for the
Manager Essentials supported Resource Manager Essentials version.
version.
CWA030 CiscoWorks Assistant — CiscoWorks Assistant does not support the
does not support the installed Internetwork Performance Monitor
installed Internetwork version.
Performance Monitor
version.
CWA031 CiscoWorks Assistant — Upgrade Integration Utility to version supported
does not support the by CiscoWorks Assistant.
installed Integration
See User Guide for CiscoWorks Assistant for the
Utility version.
supported Integration Utility version.
CWA032 CiscoWorks Assistant — Upgrade CiscoView to version supported by
does not support the CiscoWorks Assistant.
installed CiscoView
version.
See User Guide for CiscoWorks Assistant for the
supported CiscoView version.
CWA033 CiscoWorks Assistant — Upgrade Common Services to version supported
does not support the by CiscoWorks Assistant.
installed Common
See User Guide for CiscoWorks Assistant for the
Services version
supported Common Services version
CWA034 Error while Either the DCR Master is Make sure that DCR master is reachable.
communicating with not reachable
Restart the DCRServer process (Common
DCR.
or Services > Server > Admin > Processes).
the DCRServer process is
not running on the LMS
server.
CWA035 Cannot run the The Server Addition process Complete the Server Setup workflow and then
Troubleshooting of the Server Setup re-run the Troubleshooting workflow.
workflow while Server workflow is running.
Addition is in progress.
B E TA D R A F T — C I S C O C O N F I D E N T I A L
Table A-2 Error Messages for Device Troubleshooting and End Host/IP Phone Workflows
Error
Message ID Error Message Probable Cause Possible Action
CWA036 Cannot run the Server The Server Addition process Complete the Server Setup workflow and then
Discovery workflow while of the Server Setup re-run the Trouble shooting workflow.
Server Addition is in workflow is running.
progress.
CWA037 Install Campus Manager Campus Manager is not Install Campus Manager and re-run the End
before running the End installed Host/IP Phone workflow.
Host/IP Phone workflow.
CWA038 The End Host/IP Phone You have installed an Install the correct version of Campus Manager.
workflow does not unsupported version of See User Guide for CiscoWorks Assistant for the
support the installed Campus Manager. supported Campus Manager version.
version of Campus
Manager
B E TA D R A F T — C I S C O C O N F I D E N T I A L
C T
Error messages
Device Troubleshooting, End Host, IP Phone
workflows A-2, A-6
Server Setup workflow A-2
Overview
CiscoWorks Assistant 1-1