 Feedback
|
Table Of Contents
Quick Start Guide for LAN Management Solution 2.6
SUPPLEMENTAL LICENSE AGREEMENT
LAN Management Solution 2.6 Overview
Server and Client System Requirements
Solaris Patches for LAN Management Solution
LAN Management Solution Port Usage
Required LAN Management Protocols
Installing LAN Management Solution 2.6
Installing CiscoWorks Common Services 3.0.3 on Solaris
Installing Resource Manager Essentials 4.0.3 on Solaris
Installing Campus Manager 4.0.3 on Solaris
Installing Device Fault Manager 2.0.3 on Solaris
Installing Internetwork Performance Monitor 2.6 on Solaris
Installing the LMS 2.6 Update on Solaris
Installing CiscoWorks Common Services 3.0.3 on Windows
Installing Resource Manager Essentials 4.0.3 on Windows
Installing Campus Manager 4.0.3 on Windows
Installing Device Fault Manager 2.0.3 on Windows
Installing Internetwork Performance Monitor 2.6 on Windows
Installing the LMS 2.6 Update on Windows
Getting Started with CiscoWorks LMS
Invoking the CiscoWorks Homepage
Understanding the CiscoWorks Homepage
CiscoWorks Product Updates Panel
Configuring LMS Administration Parameters
Managing Devices in CiscoWorks Server
Adding Devices to DCR Using Campus Manager Device Discovery
Adding Devices to DCR Using Common Services Device and Credential Admin
Using Simple Search and Advanced Search
Performing Maintenance on Your CiscoWorks Server
Launching LMS Applications Online Help
Using Applications in ACS Mode
Integrating and Registering LMS Applications to ACS
Cisco Product Security Overview
Reporting Security Problems in Cisco Products
Product Alerts and Field Notices
Obtaining Technical Assistance
Cisco Technical Support & Documentation Website
Definitions of Service Request Severity
Obtaining Additional Publications and Information
Quick Start Guide for LAN Management Solution 2.6
This document contains information for new users of CiscoWorks LAN Management Solution 2.6. It includes:
•
SUPPLEMENTAL LICENSE AGREEMENT
•
•
•
•
•
•
•
•
SUPPLEMENTAL LICENSE AGREEMENT
SUPPLEMENTAL LICENSE AGREEMENT FOR CISCO SYSTEMS NETWORK MANAGEMENT SOFTWARE: CISCOWORKS LAN MANAGEMENT SOLUTION
IMPORTANT-READ CAREFULLY: This Supplemental License Agreement ("SLA") contains additional limitations on the license to the Software provided to Customer under the Software License Agreement between Customer and Cisco. Capitalized terms used in this SLA and not otherwise defined herein shall have the meanings assigned to them in the Software License Agreement. To the extent that there is a conflict among any of these terms and conditions applicable to the Software, the terms and conditions in this SLA shall take precedence.
By installing, downloading, accessing or otherwise using the Software, Customer agrees to be bound by the terms of this SLA. If Customer does not agree to the terms of this SLA, Customer may not install, download, or otherwise use the Software. When used below, the term "server" refers to central processor unit.
ADDITIONAL LICENSE RESTRICTIONS
Three Hundred Device Restricted Version. Customer may install and run the Software on a single server to manage up to three hundred (300) Cisco devices concurrently across all components provided in this solution. When used anywhere in this SLA, a "device" means any device in the Customer's network environment which has its own IP address. Please refer to the component installation guide for further device definition. Customers whose requirements exceed the restricted version limit of three hundred (300) devices must upgrade to the non-restricted version of the Software. Device restrictions are enforced by license registration.
Non-Restricted Device Version. Customer may install and run the Software on a single server to manage Cisco devices concurrently across all components provided in this solution. Please refer to the component installation guide for further device definition. Device restrictions are enforced by license registration. The deployment of the non-restricted device version is defined by the Installation and Use section in this document.
Installation and Use
The Software components are provided to Customer solely to install, update, supplement, or replace existing functionality of the applicable Network Management Software product. Some license terms, such as device count and proof of preexisting licenses may be electronically enforced. Customer may install and use following Software components:
•
•
•
•
•
Reproduction and Distribution
Customer may not reproduce nor distribute software.
DESCRIPTION OF OTHER RIGHTS AND LIMITATIONS
Please refer to the Cisco Systems, Inc. Software License Agreement.
LAN Management Solution 2.6 Overview
The LAN Management Solution (LMS) software provides applications for configuring, administering, monitoring, and troubleshooting a campus network. It enables network administrators to effectively manage their LAN and campus networks.
You must install LMS on a system that meets specific requirements. You must configure client systems and a few applications, such as browser settings, Solaris patches, and so on. See the "Server and Client System Requirements" section for details.
You can select any one of the following two licenses of LMS 2.6:
•
•
However, the number of devices that can be managed in a single server depends on your server configuration. See the "Application Scaling Numbers" section for details.
This document explains fresh installation of LMS 2.6. In this document you will find:
•
•
•
•
•
•
•
If you already have an earlier version of LMS and want to upgrade to LMS 2.6, follow the procedure as described in these documents:
•
•
You can find these documents at this URL:
http://www.cisco.com/en/US/products/sw/cscowork/ps2425/prod_installation_guides_list.html
Licensing Your Product
The LMS 2.6 product features software-based product registration and license key activation technologies. During the installation process, the installer displays the Registration and Licensing input dialog box. The following table provides information about terminology used in the registration process.
Getting the Licensing File
Table 1 describes PAK, PIN, License file and its usage.
Table 1 Understanding PAK, PIN, and License File
Product Authorization Key (PAK)
The PAK is printed on the software claim certificate. Use the PAK to get your license file from Cisco.com. You may obtain and install your license file at any time while you are working on LMS, not necessarily only at the time you install the product.
We recommend that you complete the LMS license registration and receive the product license before installing LMS 2.6.
If the user installing LMS is not authorized to obtain the license on behalf of the administrator, the product can be successfully installed for a period of time using only the PIN. In this case, the product will remind the administrator to complete the licensing process.
Product Identification Number (PIN)
The PIN is printed on the software claim certificate. The LMS installation program prompts you to enter the PIN during installation.
If an authenticated license cannot be obtained during installation, use the PIN to proceed with the installation. If you enter only a PIN, LMS runs normally, but you will be periodically reminded to complete the license process.
License file
When you register your LMS purchase on the product licensing area of Cisco.com, you will receive a license file. You must enter your PAK to receive a license file.
If you are a registered user of Cisco.com, get your license file from: http://www.cisco.com/go/license
If you are not a registered user of Cisco.com, get your Cisco.com user ID from:
http://tools.cisco.com/RPF/register/register.do. Once you have obtained your Cisco.com user ID, log on to http://www.cisco.com/go/license to get your license file.Logging in allows your Cisco user profile information to auto-populate many of the product registration fields. Login is case sensitive.
Figure 1 displays the licensing screen on Windows operating system.
Figure 1 Licensing Screen
The LMS installation program prompts you to enter either the license file, or the PIN and PAK (see Figure 1). We recommend that you complete the license registration process at this point.
Evaluation Mode
If you have received the LMS as an evaluation copy, you need not register the product during the 90-day evaluation period. The installation process for an evaluation copy is the same as that of a purchased product, except that you are prompted to select the Evaluation Only option from the Licensing Information page (see Figure 1).
If you choose to run LMS in the evaluation mode, it stops functioning after 90 days. The evaluation period cannot be extended. If you have purchased a copy and you decide to install it in evaluation mode, please use your PAK to register the product on the Cisco online licensing site and receive a valid license.
If you have not purchased the product, the LMS evaluation server can be reactivated by purchasing LMS from your authorized Cisco reseller. You can register the product using the PAK and PIN provided with the product. For details, see the "Installing the Licensing File" section.
Note
Installing the Licensing File
We recommend that before installing the LMS 2.6 product, you register the product and receive a permanent license.
To license your product, you must:
Step 1
The PAK is printed on the software claim certificate.
If you are a registered user of Cisco.com, get your license file from: http://www.cisco.com/go/license
If you are not a registered user of Cisco.com, get your Cisco.com user ID from:
http://tools.cisco.com/RPF/register/register.do. Once you have obtained your Cisco.com user ID, log on to http://www.cisco.com/go/license to get your license file.Logging in allows your Cisco user profile information to auto-populate many of the product registration fields. Login is case sensitive.
Step 2
Step 3
If you have obtained the LMS license before installation:
a.
–
–
b.
If you have completed the LMS install by entering the PAK and PIN, or if you want to convert an evaluation copy to a licensed copy:
a.
The License Administration page appears.
b.
A file browser popup dialog box appears.
c.
d.
The system verifies whether the license file is valid, and updates the license.
The updated licensing information appears in the License Information page. If you encounter errors, repeat the steps to license your product.
Additional Information for LMS 2.6 Large Enterprise Unrestricted Licensing
Users of LMS 2.6 for Large Enterprises often require individual LMS applications, such as DFM or RME, to be run on separate servers to support a large number of devices or to meet certain performance criteria.
When more than one server is used to host LMS, each server should have a copy of the license in it. You should copy the license file to the server as described in Step 2, and install the license as described in Step 3. You should not modify the license file.
Legal restriction concerning the distribution of the LMS applications is described in the Supplemental License Agreement. More than one copy of an application (RME, DFM, Campus, or IPM) should not be running in the network unless additional copies of LMS have been purchased and licensed.
LMS Package Contents
Table 2 describes the contents of the LAN Management Solution 2.6 for Solaris and Windows.
Additional Package Information
Registered Cisco.com users can access the most current Device Package Updates, and Latest Adapters for third-party network management applications at the following locations:
•
–
http://www.cisco.com/pcgi-bin/Software/CiscoView/cvplanner.cgi
–
http://www.cisco.com/pcgi-bin/tablebuild.pl/cw2000-campus
–
http://www.cisco.com/pcgi-bin/tablebuild.pl/cw2000-dfm
–
http://www.cisco.com/pcgi-bin/tablebuild.pl/cw2000-rme
•
http://www.cisco.com/pcgi-bin/tablebuild.pl/ipm-sol
•
http://www.cisco.com/kobayashi/sw-center/cw2000/cmc3rd.shtml
•
On Internet Explorer
http://ftp.cisco.com/cisco/netmgmt/ciscoview/5.0/packages/nmidb.X.zip
On Netscape
ftp://userid@ftp.cisco.com/cisco/netmgmt/ciscoview/5.0/packages/nmidb.X.zip
Where, userid is the Cisco.com user ID and X is the latest nmidb version (for example, 1.0.086).
Server and Client System Requirements
This section provides the LAN Management Solution 2.6 server and client requirements.
•
•
•
•
•
•
•
If you are running additional Cisco or third-party applications on the servers, the requirements might be higher. See the individual LMS application installation guides for specific product requirements.
LAN Management Solution 2.6 supports only the US English and Japanese versions of these operating systems. It does not support any other language versions.
Set the default locale to US-English for the US-English version and Japanese for the Japanese version. Installation might proceed in other locales, but there might be problems in the functionality of CiscoWorks.
Note
Table 3 lists the server requirements for upgrading the LAN Management Solution 2.6 components on Solaris systems.
Table 3 Recommended Server Requirements for Solaris Systems
CPU
•
•
•
RAM
•
•
Software
Solaris 8 (Solaris 2.8) and Solaris 9 (Solaris 2.9)
Disk Space
20 GB or more free space for LMS applications and data
Swap Space
•
•
•
We recommend that you set swap space to twice the size of RAM.
1 To verify the amount of available disk space in each of the specified partitions and directories, enter: df -k at the command prompt.
Table 4 lists the server requirements for upgrading the LAN Management Solution 2.6 components on Windows systems. For a list of Windows HotFix patches, see the "Frequently Asked Questions" section.
Table 4 Recommended Server Requirements for Windows Systems
CPU
•
•
RAM
•
•
Any one of the following:
•
•
•
•
•
•
•
•
LAN Management Solution 2.6 supports only the US English and Japanese versions of these operating systems.
Set the default locale to US-English for the US-English version and Japanese for the Japanese version. Installation might proceed in other locales, but there might be problems in the functionality of CiscoWorks.
Disk space
20 GB or more free space for LMS applications and data
Swap space
•
•
•
We recommend that you set virtual memory to twice the size of RAM.
1 Installation of LMS 2.6 on a system with Internet Information Services (IIS) enabled is not supported. IIS Service must be disabled on the server before installing the LMS 2.6 applications.
2 If you are using LMS 2.6 on a Windows 2000 operating system (all versions), disable Hyper-Threading Technology (HTT). See http://www.intel.com/support/processors/sb/CS-017343.htm.
3 Installation of LMS 2.6 applications on a system with Terminal Services enabled in Remote Administration mode is supported. However, installation of LMS 2.6 applications on a system with Terminal Services enabled in Application mode is not supported.
4 To verify the Service Pack version on Windows, select Start > Run, then enter winver.
5 Install LMS 2.6 on an NTFS file system. Do not install LMS 2.6 on a FAT file system. To verify the file system, open My Computer on the Windows desktop, right-click the drive and select Properties from the popup menu. The file system field appears in the General tab of the Properties dialog box.
Table 5 lists the client system requirements for all platforms.
Table 6 lists the browser requirements for all platforms.
Table 6 Browser Requirements
Internet Explorer (recommended)
Java Plug-in version 1.4.2_102
6.0 Service Pack 1
Any one of the following:
•
•
6.0.2900.2180
Windows XP3
Netscape Navigator
Java Plug-in version 1.4.2_102
7.1 and 7.2
Any one of the following:
•
•
Netscape Navigator (Downloaded from Sun site only)
Java Plug-in version 1.4.2_102
7.0
Any one of the following:
•
•
Mozilla
Java Plug-in version 1.4.2_102
1.7.13
Any one of the following:
•
•
•
•
•
1 Java Virtual Machine. To verify JVM, select Tools > Sun Java Console in Internet Explorer and Tools > Web Development > Java Console in Netscape Navigator. If Java Console is not listed in Tools, you must enable it. To enable Java Console in Internet Explorer, select Tools > Internet Options > Advanced. In the Java (Sun) section, select the Java Console option. Restart Internet Explorer.
2 You can upgrade to Java Plug-in version 1.4.2_10 manually. See the Installation Guide for IPM and Campus Manager for more details.
3 Windows XP Professional is not packaged with JVM. JVM is installed after you install Windows XP.
Application Scaling Numbers
This section presents information on the specific scaling numbers for each of the CiscoWorks LMS applications. This helps you decide what server size and distribution will best suit your needs, and optimize your network performance.
Below are the tested numbers for each application in standalone mode:
•
•
•
•
•
The supported concurrent users for LMS 2.6 are:
•
•
The number of "Multiple, simultaneous users" can affect system performance. Depending upon the size of the server, 20 simultaneous users is the maximum recommended.
Solaris Patches for LAN Management Solution
Table 7 lists the Solaris patches for LAN Management Solution 2.6.
A warning message is displayed if obsolete Solaris patches are present on your system. Before running CiscoWorks Common Services 3.0.5, download and install the latest recommended patches from http://www.sunsolve.sun.com.
Caution
Table 7 Solaris Patches for LAN Management Solution 2.61
Solaris 8
111327-05
110945-08
110934-16
110898-09
109326-14
108827-40
108528-29
111626-03
108652-81
108921-21
108940-62
110951-05
110662-12
110615-11
108964-06
110286-11 109324-05
Solaris 9
114224-01
113580-01
112839-04
112233-12
114006-01
112771-14
112661-06
113244-05
113326-01
112998-03
113713-14
112964-07
113575-05
112970-07
112874-31
112808-06
1 Use the showrev -p command to verify that these patches have been applied.
LAN Management Solution Port Usage
Table 8 lists the ports used by the various CiscoWorks components.
Required LAN Management Protocols
You must configure several important device credentials correctly on every Cisco device that will be managed and monitored through LMS. You must also enter the correct device credentials in the Device Credential Repository (Common Services > Device and Credentials > Device Management).
Table 9 lists all the applications and the device credentials required for proper functioning of the applications.
.
Table 9 Applications and Device Credentials
Not required
Not required
Not required
Required
Not required
Not required
Required
Required
Not required
Not required
Required
Required
Not required
Not required
Required
Not required
Not required
Not required
Required
Required
Inventory
Not required
Not required
Required
Not required
Configuration Management (Telnet)
Required
Required
Required
Not required
Not required
Not required
Required
Required
NetConfig
Required
Required
Required
Required
Config Editor
Required
Required
Required
Required
NetShow
Required
Required
Required
Not required
Software Management
Required3
Required3
Required
Required
1 Configuration download also uses TFTP. Hence, SNMP Read/Write credentials are required.
2 The file vlan.dat can be fetched only if the Telnet password and Enable password are supplied.
3 Required in the case of a few devices like PIX devices, Cisco 2950 series switches.
Installing LAN Management Solution 2.6
This section contains information on:
•
•
To install an application, log in as root (on Solaris) or local administrator or user with administrator privileges (on Windows) on the system on which you want to install the application.
Before you install LMS 2.6, note that:
•
Table 10 lists the LMS 2.5.1 applications and their versions.
•
•
LMS 2.6 Update Description
The LMS 2.6 Update is a bundle update that contains incremental versions to more than one component of the LMS 2.5.1 bundle.
It is provided as a single installable CD-ROM and contains:
•
•
•
•
•
There is no change in Internetwork Performance Monitor 2.6.
Recommended Order of Installation
We recommend that you install LMS 2.6 in the following order:
Step 1
Step 2
Step 3
Step 4
Step 5
Step 6
Prerequisites
This section describes the factors that you should consider before installing LMS 2.6. Ensure you complete the following tasks before installation:
Step 1
Step 2
Step 3
Important Installation Notes
This section contains important information that you should read before you begin installation:
•
•
If you have enabled Terminal Server in Application mode, disable the Terminal Server, reboot the system, and start the installation again.
•
•
•
•
•
This also occurs while you are uninstalling the application.
•
–
–
Where, SystemDrive is the Windows operating system installed directory.
If you select another directory during installation, the application is installed in that directory.
•
Warning
•
–
–
Where xxxxxxxx is the date stamp in the format yyyymmdd, and yyyyyy is the time stamp in the format hhmmss.
For example:
/var/tmp/Ciscoworks_install_20060721_182205.logFor IPM, the installation log file is /var/tmp/cisco_ipm_install.log.
•
For example, for LMS 2.5.1, the CiscoWorks Common Services installation creates SystemDrive:\CiscoWorks_setupxxx.log, where xxx is the running number for the last CiscoWorks application installed.
For LMS 2.6, the installation log file is: SystemDrive:\Ciscoworks_install_xxxxxxxx_yyyyyy.log
Where xxxxxxxx is the date stamp in the format yyyymmdd, and yyyyyy is the time stamp in the format hhmmss.
For example:
C:\Ciscoworks_install_20060721_182205.logFor IPM, there is no installation log file on Windows.
•
For example, if any new files were installed or if they were any changes to the system files, you need to manually clean up the installation directories.
Note
•
•
•
For help with NMS integration, see the User Guide for CiscoWorks Integration Utility 1.6. You can find this document on Cisco.com, in both HTML and PDF form.
http://www.cisco.com/en/US/products/sw/cscowork/ps3996/products_user_guide_list.html
•
•
•
Terms and Definitions Used in LMS Installation Framework
This section captures the terms and definitions that are used by LMS applications at the time of installation.
See "Licensing Your Product" section to understand the licensing terminologies.
Common Services:
While installing Common Services, you may come across these terms:
•
Ensure that you have noted down the password.
You are prompted to enter this password in both Typical and Custom modes of installation.
•
Communication among multiple CiscoWorks Servers is enabled by a "trust" model addressed by certificates and shared secrets. System Identity setup helps you to create a "trust" user among servers that are part of a multi-server setup. This user enables communication among servers that are part of a domain.
While entering the System Identity Account Passwords, use a minimum of five characters.
You are prompted to enter this password in both Typical and Custom modes of installation.
•
You are prompted to enter this password in the Custom mode of installation. In the Typical mode, this password is randomly generated.
•
This database password is used internally by the other LMS applications to communicate with the Common Services database. This password is also used while restoring or troubleshooting the Common Services database.
You are prompted to enter this password in the Custom mode of installation. In the Typical mode, this password is randomly generated.
•
Self Signed Certificates are valid for five years from the date of creation. When the certificate expires, the browser prompts you to install the certificate again from the server where you have installed CiscoWorks.
You are prompted to enter the following information to generate the Self Signed Certificate in the Custom mode of installation:
–
–
–
–
–
–
Enter the Host Name with a proper domain name. This is displayed on your certificate (whether self-signed or third party issued). Local host or 127.0.0.1 should not be given.
–
In the Typical mode, this certificate is automatically generated.
•
You are prompted to enter this server detail in the Custom mode of installation. In the Typical mode, after the installation you can configure SMTP by selecting Server > Admin > System Preferences from the CiscoWorks homepage.
•
You are prompted to enter these credentials while installing the CiscoWorks Integration Utility.
You can also change the System Identity Account password, Guest password, and Cisco.com credentials using the Common Services User Interface (Common Services > Server > Security).
Resource Manager Essentials:
While installing RME, you may come across this term:
RME Database Password—Use a minimum of five characters and a maximum of 15 characters. Do not start the password with a number and do not insert spaces between characters.
This password is also used while restoring or troubleshooting the RME database.
You are prompted to enter this password in the Custom mode of installation. In the Typical mode, this password is randomly generated.
Campus Manager:
While installing CM, you may come across this term:
ANI Database Password—Campus Manager accesses the ANI database for critical network information. Use a minimum of five characters and a maximum of 15 characters. Do not start the password with a number and do not insert spaces between characters.
You are prompted to enter this password in the Custom mode of installation. In the Typical mode, this password is randomly generated.
Device Fault Manager:
While installing DFM, you may come across these terms:
•
This password is also used while restoring or troubleshooting the DFM database.
You are prompted to enter this password in the Custom mode of installation. In the Typical mode, this password is randomly generated.
•
You are prompted to enter this password in the Custom mode of installation. In the Typical mode, this password is randomly generated.
Internetwork Performance Monitor:
While installing IPM, you may come across these terms:
•
This password is also used while restoring or troubleshooting the IPM database.
You are prompted to enter this password in both standard installation and Express installation.
•
IPM prompts you to enter this Administrative password to access the client functions, such as opening the seed files, launching the Secure Web clients, using the ipm tshoot troubleshooting command, and downloading the IPM client software from the IPM Server Home Page.
The password is case sensitive and should begin with an alphabet. You can enter only a maximum of 15 characters and you can enter only alphanumeric characters.
You are prompted to enter this password in both Standard installation and Express installation.
Installing LMS 2.6 on Solaris
The following sections capture information on how to install LMS 2.6 on Solaris:
•
•
•
•
•
•
Installing CiscoWorks Common Services 3.0.3 on Solaris
Installing CiscoWorks Common Services takes approximately 25 minutes. To do this:
Step 1
•
From the CD-ROM root directory, look for CD-ROMDrive/Documentation/InstallSetupGuideForComSerCVSol.pdf
•
http://www.cisco.com/en/US/products/sw/cscowork/ps3996/prod_installation_guides_list.html
Step 2
•
•
•
Step 3
Step 4
The default installation option is Typical. Select Custom install option if you want to specify a destination other than /opt/CSCOpx.
Step 5
1.
2.
3.
Step 6
If you receive error messages during the installation, or cannot complete the tasks in this step, see Appendix A, "Troubleshooting the Installation".
Installing Resource Manager Essentials 4.0.3 on Solaris
Installing Resource Manager Essentials takes approximately 30 minutes. To do this:
Step 1
•
From the CD-ROM root directory, look for CD-ROMDrive/RME/Documentation/InstallSetupGuideforRME403Sol.pdf
•
http://www.cisco.com/en/US/products/sw/cscowork/ps2073/prod_installation_guides_list.html
Step 2
We recommend that you change the RME database password when prompted to do so.
Step 3
If you receive error messages during the installation, or cannot access the home page, see Appendix A, "Troubleshooting the Installation".
Installing Campus Manager 4.0.3 on Solaris
Installing Campus Manager takes approximately 30 minutes. To do this:
Step 1
•
From the CD-ROM root directory, look for CD-ROMDrive/Documentation/InstallSetupGuideForCampusSol.pdf
•
Step 2
We recommend that you change the ANI database password when prompted to do so.
Step 3
If you receive error messages during the installation, or cannot access the server, see Appendix A, "Troubleshooting the Installation".
Installing Device Fault Manager 2.0.3 on Solaris
Installing Device Fault Manager (DFM) takes approximately 20 minutes. To do this:
Step 1
•
From the CD-ROM root directory, look for CD-ROMDrive/Documentation/dfm203_solaris_install_and_setup.pdf
•
http://www.cisco.com/en/US/products/sw/cscowork/ps2421/prod_installation_guides_list.html
Step 2
We recommend that you change the DFM database password when prompted to do so.
Installing Internetwork Performance Monitor 2.6 on Solaris
Installing Internetwork Performance Monitor (IPM) takes approximately 20 minutes. The installation script installs Internetwork Performance Monitor in the following default locations:
•
•
•
To do this:
Step 1
•
From the CD's root directory, look for /docs/ipm26_install.pdf
•
Step 2
•
•
•
•
•
Step 3
We recommend that you select an Express install. Select another install option only if you want to specify a destination other than /opt/CSCOipm.
Installing the LMS 2.6 Update on Solaris
It takes approximately 1 hour and 20 minutes to install the complete update for Common Services, RME, Campus Manager, and DFM. To do this:
Step 1
Step 2
# unzip LMS26_sol.zip
The files are extracted under the LMS26_sol directory.
Step 3
# cd LMS26_sol
Step 4
# sh setup.shor
# ./setup.sh
A prompt appears:
Press Enter to read/browse the following license agreement:Step 5
The following message appears at the end of the license agreement:
Do you accept all the terms of the License Agreement? (y/n) [n]:Step 6
Based on your LMS 2.5.1 installation, the new updates are listed.
The following message appears:
LMS 2.6 update
=========================================================
New Updates to be installed :
CiscoWorks Common Services 3.0.5 update
CiscoView 6.1.5 update
Resource Manager Essentials 4.0.5 update
Campus Manager 4.0.6 update
Device Fault Manager 2.0.6 update
Do you want to continue the installation:? (y/n) [y]:Step 7
The following message appears:
Essentials products can be tuned to use system resources effectively to improve
performance. Would you like to apply the new product profiles?The above message appears only if you have installed the update for RME.
Step 8
The following message appears:
WARNING: Exiting installation beyond this point might result in system instability.
Do you want to continue the installation? (y/n) [y]:Step 9
The following messages appear:
WARNING: To ensure that you retain the latest device support for RME,
WARNING: please install the latest Device Packages from CCO @
WARNING: http://www.cisco.com/pcgi-bin/tablebuild.pl/cw2000-rme
WARNING: Please refer to the Installation and Setup Guide for details.The above message appears only if you have installed the update for RME.
WARNING: To ensure that you retain the latest device support for CM,
WARNING: please install the latest Device Packages from CCO @
WARNING: http://www.cisco.com/pcgi-bin/tablebuild.pl/cw2000-campus
WARNING: Please refer to the Installation and Setup Guide for details.The above message appears only if you have installed the update for CM.
WARNING: To ensure that you have up-to-date device support,
WARNING: install the latest Service Pack (SP) from Cisco.com, at
WARNING: http://www.cisco.com/pcgi-bin/tablebuild.pl/cw2000-dfm.
WARNING: For installation details, refer to the DFM Installation and Setup Guide.The above message appears only if you have installed the update for DFM.
WARNING: If you plan to install any of the LMS 2.5.1 applications later,
WARNING: you must reinstall CiscoWorks LMS 2.6 Update
WARNING: after installing these applications.The installation completes without displaying more questions and the system prompt appears.
Installing LMS 2.6 on Windows
The following sections capture information on how to install LMS 2.6 on Windows:
•
•
•
•
•
•
Installing CiscoWorks Common Services 3.0.3 on Windows
Before you begin, note the following:
•
•
•
Installing CiscoWorks Common Services takes approximately 15 minutes. To do this:
Step 1
•
From the CD-ROM root directory, look for CD-ROMDrive\Documentation\InstallSetupGuideForComSerCVWin.pdf
•
Step 2
•
•
•
•
However, you cannot configure ACS as an AAA client, which is required when ACS and CiscoWorks coexist. Hence the configuration required for ACS integration will fail.
Step 3
Step 4
The default installation option is Typical. Select Custom install option if you want to specify a destination other than SystemDrive:\Program Files\CSCOpx.
Step 5
a.
b.
c.
Step 6
If you receive error messages during the installation, or cannot complete the tasks in this step, see Appendix A, "Troubleshooting the Installation".
Installing Resource Manager Essentials 4.0.3 on Windows
Installing Resource Manager Essentials takes approximately 30 minutes. To do this:
Step 1
•
From the CD-ROM root directory, look for CD-ROMDrive\RME\Documentation\InstallSetupGuideforRME403Win.pdf
•
http://www.cisco.com/en/US/products/sw/cscowork/ps2073/prod_installation_guides_list.html
Step 2
We recommend that you change the RME database password when prompted to do so.
Step 3
If you receive error messages during the installation, or cannot access the Homepage, see Appendix C, "Troubleshooting the Installation".
Installing Campus Manager 4.0.3 on Windows
Installing Campus Manager takes approximately 20 minutes. To do this:
Step 1
•
From the CD-ROM root directory, look for CD-ROMDrive\Documentation\InstallSetupGuideForCampusWin.pdf
•
http://www.cisco.com/en/US/products/sw/cscowork/ps563/prod_installation_guides_list.html
Step 2
We recommend that you change the ANI database password when prompted to do so.
Step 3
If you receive error messages during the installation, or cannot access the server, see Appendix A, "Troubleshooting the Installation".
Installing Device Fault Manager 2.0.3 on Windows
Installing Device Fault Manager (DFM) takes approximately 20 minutes. To do this:
Step 1
•
From the CD-ROM root directory, look for CD-ROMDrive\Documentation\dfm203_windows_install_and_setup.pdf
•
http://www.cisco.com/en/US/products/sw/cscowork/ps2421/prod_installation_guides_list.html
Step 2
We recommend that you change the DFM database password when prompted to do so.
Installing Internetwork Performance Monitor 2.6 on Windows
Installing Internetwork Performance Monitor (IPM) takes approximately 20 minutes. The installation script installs Internetwork Performance Monitor in the following default locations:
\\Program Files\Internetwork Performance Monitor
To do this:
Step 1
•
From the CD's root directory, look for \\docs\ipm26_install.pdf.
•
Step 2
•
•
•
•
Step 3
Installing the LMS 2.6 Update on Windows
It takes approximately 1 hour to install the complete update for Common Services, RME, Campus Manager, and DFM. To do this:
Step 1
Step 2
The files are extracted under the lms26_win folder.
Step 3
Step 4
The CiscoWorks LMS 2.6 Update window appears.
Step 5
The following message appears if Windows Management Instrumentation (WMI) services are running:
The setup program has detected Windows Management Instrumentation
(WMI) services running.
This will lock some CiscoWorks processes and may abort installation abruptly.
To avoid this, installation will stop and start the WMI services.
Do you want to proceed?
Click Yes to proceed with this installation.
Click No to exit installation.Step 6
The Welcome screen appears.
Step 7
The Software License Agreement window appears. You must accept this agreement to install CiscoWorks LMS 2.6 Update.
Step 8
The Install Update window appears with the updates that will be installed.
Step 9
The installation program checks dependencies and system requirements. The System Requirements window appears.
The System Requirements window displays the system requirements, available space in the disk drive, available memory and Swap in megabytes, and CPU speed in megahertz.
Step 10
The Summary window appears with the updates that will be installed and the settings for the installation.
Step 11
The following message appears:
Essentials products can be tuned to use system resources effectively to improve
performance. Would you like to apply the new product profiles?The above message appears only if you have installed the update for RME.
Step 12
The Setup screen appears, displaying installation progress while files are copied and applications are configured.
The following message appears only if you have installed the update for RME:
WARNING: To ensure that you retain the latest device support for RME,
WARNING: please install the latest Device Packages from CCO @
WARNING: http://www.cisco.com/pcgi-bin/tablebuild.pl/cw2000-rme
WARNING: Please refer to the Installation and Setup Guide for details.Step 13
The following message appears only if you have installed the update for CM:
WARNING: To ensure that you retain the latest device support for CM,
WARNING: please install the latest Device Packages from CCO @
WARNING: http://www.cisco.com/pcgi-bin/tablebuild.pl/cw2000-campus
WARNING: Please refer to the Installation and Setup Guide for details.Step 14
The following message appears only if you have installed the update for DFM:
WARNING: To ensure that you have up-to-date device support,
WARNING: install the latest Service Pack (SP) from Cisco.com, at
WARNING: http://www.cisco.com/pcgi-bin/tablebuild.pl/cw2000-dfm.
WARNING: For installation details, refer to the DFM Installation and Setup Guide.Step 15
The following message appears:
WARNING: If you plan to install any of the LMS 2.5.1 applications later,
WARNING: you must reinstall CiscoWorks LMS 2.6 Update
WARNING: after installing these applications.Step 16
The Restart dialog box appears after the installation is complete.
Note
Step 17
Step 18
Verifying the Installation
You can verify LMS 2.6 installation by following any one of these procedures.
Procedure 1
You can verify LMS 2.6 installation using either of these methods:
•
Where, NMSROOT is the CiscoWorks installation directory (by default, SystemDrive:\Program Files\CSCOpx and SystemDrive is the Windows operating system installed directory).
•
The following services should be displayed:
Procedure 2
To verify from the CiscoWorks Homepage:
Step 1
The Application Registration Status page appears.
Step 2
If LMS 2.6 is installed successfully, the following application versions must be listed:
•
•
•
•
•
•
•
For Internetwork Performance Monitor 2.6, see the following chapters in the Installation Guide for Internetwork Performance Monitor 2.6.
•
•
Getting Started with CiscoWorks LMS
The topics in this section help you work with and understand the LMS user interface:
•
•
•
•
•
•
•
Before you start using the LMS 2.6 applications, you must ensure that:
•
See Chapter 2, "Setting Up Devices on the Network", in the Cisco LAN Management Solution 2.5 Deployment Guide.
The LMS 2.5 Deployment Guide and other whitepapers are available on Cisco.com at:
http://www.cisco.com/en/US/products/sw/cscowork/ps2425/prod_white_papers_list.html
•
See the "Licensing Your Product" section.
The following sections help you to get started with CiscoWorks LMS only in a single-server mode.
If you have a setup with multiple CiscoWorks servers, you must:
•
•
•
•
To get started in multiple-server mode, see the "Configuring the Server" section in the User Guide for CiscoWorks Common Services 3.0.5.
Invoking the CiscoWorks Homepage
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
You can also use the IP address of the CiscoWorks Server to access the CiscoWorks Homepage. For example:
http://10.77.210.93:1741
On Windows, CiscoWorks Server always uses the default port numbers in secure and normal modes.
On Solaris, if the default TCP ports (1741 and 443) are used by other applications, you can select different ports for secure and normal modes during CiscoWorks Server installation. For more information, see the Installation and Setup Guide for CiscoWorks Common Services on Solaris.
Logging In
To log into the CiscoWorks Homepage:
Step 1
User Name:admin
Password:passwordYou must enter the same admin password that you entered while installing Common Services 3.0.3
Step 2
The CiscoWorks Homepage appears.
Understanding the CiscoWorks Homepage
Figure 2 CiscoWorks Homepage with all the LMS Applications Installed
Common Services Panels. See the "Common Services Panel" section.
CiscoWorks Server Name.
Application Panel. See the "Application Panel" section.
Resources Panel. See the "Resources Panel" section.
CiscoWorks Tool Bar. See the "Tool Bar Items" section.
CiscoWorks Product Updates Panel. See the "CiscoWorks Product Updates Panel" section.
LMS Setup Center Panel. See the "LMS Setup Center Panel" section.
Common Services Panel
The Common Services panel displays all Common Services functions. The Common Services panel appears as a collapsible folder. You can view the first level items when the folder is opened.
Device Troubleshooting Panel
The Device Troubleshooting panel provides a launch point to the Device Center.
Device Center helps you to view device details, launch troubleshooting tools, perform management tasks, and view reports for the selected device. You can also change device credentials, update the inventory, and access a device through Telnet.
For more information, see the "Using Device Center" chapter in the User Guide for CiscoWorks Common Services 3.0.5.
Application Panel
Each Application panel in the CiscoWorks Homepage serves as a top-level launch point for all LMS applications installed on the local or remote server. Applications appear in the CiscoWorks Homepage in three columns.
By default, only the first level items are displayed when you log in. These first level items are in the collapsed mode. Lower level navigations are displayed only if you manually expand a first level item.
The title of each Application panel displays the application name and it serves as a link to the relevant application homepage. Application tasks are displayed in a hierarchical manner. When you select a task from the hierarchy, it launches the application homepage in a new window.
If the corresponding application homepage already exists for some other task, the window for this task is focused, instead of creating a new window.
LMS Setup Center Panel
The LMS Setup Center panel provides a launch point to the LMS Setup Center.
The LMS Setup Center (see Figure 3) helps you complete basic system setup activities, such as select security, proxy, and SMTP settings. You can set up Cisco.com accounts for CS and for each of the applications. You can also configure application-specific settings in a flow.
The configurations are grouped into the following categories: System Settings, Security Settings, Data Collection Settings, Data Collection Schedule, and Data Purge Settings.
Figure 3 LMS Setup Center Page
Resources Panel
The Resources panel is located at the top right corner of the CiscoWorks Homepage. It also serves as a top-level launch point for CiscoWorks resources, Cisco.com resources, third-party application links, and web-based custom tool links. This panel shows the types of resources at the first level and details in the next level.
Note
CiscoWorks Product Updates Panel
The CiscoWorks Product Updates panel is located at the lower right corner of the page. It displays informative messages about CiscoWorks product announcements, and help-related topics. If you click the More Updates link, a popup window appears with all the Cisco Product Update details.
If the Common Services server is behind a firewall, the proxy settings are used to download messages from Cisco.com. The CiscoWorks Homepage provides an Admin UI to accept the proxy settings.
The CiscoWorks Homepage alerts you if any urgent messages are found. By default, the polling interval is one minute. You can change the polling interval.
Tool Bar Items
Three buttons are available on the top right of the CiscoWorks Homepage, above the Resources panel:
•
•
•
Configuring LMS Administration Parameters
After you have installed the required applications and verified the installations, you must perform the following administrative tasks.
Note
Common Services
The administrative tasks for Common Services are:
•
•
Enable or disable SSL depending on the need to use secure access. You can perform this task using Common Services > Server > Security > Browser-Server Security Mode Setup.
•
•
•
See the Online help or the User Guide for CiscoWorks Common Services 3.0.5.
Resource Manager Essentials
The administrative tasks for Resource Manager Essentials are:
•
Network administrators can assign the protocols to be used in RME for Configuration Management and Software Management.
–
The available protocols are Telnet, TFTP, RCP, SSH, SCP, and HTTPS.
–
The supported protocols are: RCP, TFTP, SCP, and HTTP.
•
•
See the Online help or the User Guide for Resource Manager Essentials 4.0.5.
Campus Manager
The administrative tasks for Campus Manager are:
•
You can schedule the day, time, and frequency of data collection.
You can define the periodicity for polling the network. Polling helps you see updated devices and link information without running data collection. Polling is enabled by default. The default poll interval is two hours.
You can perform this task by selecting Campus Manager > Administration. Click Admin and select Campus Data Collection > Schedule Data Collection.
•
You can specify VTP Domains or IP Address ranges for data collection using Campus Data Collection > Data Collection Filters.
•
User Tracking allows you to locate end-user hosts in the network. It collects and presents information gathered by the Asynchronous Network Interface (ANI) Server and held in the ANI database. You can also use User Tracking to find duplicate connections that could indicate potential problems in your network.
To configure this, select Campus Manager > User Tracking and then select Acquisition > Actions.
See the Online help or the User Guide for Campus Manager 4.0.6.
Device Fault Manager
The administrative tasks for Device Fault Manager are:
•
The Common Services system-defined groups include groups, such as Broadband Cable, Routers, Switches and Hubs, and so forth.
These groups have specific polling and threshold settings. The DFM Polling and Threshold function creates its own corresponding groups based on Common Services and DFM groups. These are:
–
–
You can perform this task using Device Fault Manager > Configuration > Polling and Thresholds.
•
In addition to watching network conditions as they change on the Alerts and Activities display, you can use DFM notification services to automatically notify users and other systems when specific changes occur on selected devices.
To do so, you must create subscriptions for e-mail notifications, DFM-generated SNMP trap notifications, or Syslog notifications.
You can also change event names to names that are more meaningful to you, and these names will appear in the DFM displays and notifications.
You can perform this task using Device Fault Manager > Notification Services.
•
The Alerts and Activities display provides a consolidated real-time view of the operational status of your network. When a fault occurs in your network, DFM generates an event (or events). Events are rolled up into alerts, one alert for each device with a fault.
You can perform this task using Configuration > Other Configurations > Alerts and Activities Defaults.
See the Online help or the User Guide for Device Fault Manager 2.0.6.
Managing Devices in CiscoWorks Server
The Device and Credential Repository (DCR) is a common repository of devices, their attributes, and credentials, meant to be used by various network management applications. The Device and Credential Admin (DCA) provides an interface to administer DCR.
DCR helps multiple applications share device lists and credentials using a client-server mechanism, with secured storage and communications. The applications can read or retrieve the information.
The applications can also update the information in DCR so that the updated information could be shared with other applications. DCR:
•
•
•
•
•
•
You must first add devices in Common Services. These devices get added automatically in CM, DFM, and RME. You have to manually add devices to IPM.
These topics describe how to add devices to the CiscoWorks Server:
•
or
Adding Devices to DCR Using Common Services Device and Credential Admin
Figure 4 shows the Common Services Device Management window. From this window, you can:
•
•
•
•
•
•
•
•
Figure 4 Common Services Device Management Page
To learn how to add devices to DCR, see either of these sections:
•
•
Adding Devices to DCR Using Campus Manager Device Discovery
To discover the network, the Device Discovery process needs the SNMP credentials of the devices in the network and the IP address for the seed device. The following are some key facts about Device Discovery:
•
•
•
–
–
–
Device Discovery does not update SNMPv2 write community string.
To configure Device Discovery:
Step 1
A new Campus Administration page appears. (See Figure 5.)
Figure 5 Campus Manager Administration Page
Step 2
The SNMP Settings page appears.
Step 3
Step 4
The Device Discovery Settings page appears.
Step 5
Step 6
The Seed Devices dialog box appears. Seed devices are devices used to initiate network discovery.
Step 7
You must separate the seed devices stored in the file with a carriage return. That is, only one seed device can be stored in each line in the file.
For example, the seed devices in the file can be entered as:
172.20.5.6
172.20.118.130
10.77.209.209
172.20.99.2
10.77.210.101
10.77.210.103To limit discovery by IP addresses in your network, from the Discovery Settings page, click IP Address Range > Configure.
The Configure Range dialog box appears. Specify IP Address Range settings as required.
If IP Address Range is not specified, Device Discovery tries to discover as many devices as it can, based on the community strings and connectivity.
For more information, see Configuring Device Discovery Online help or the "Using Device Discovery Administration" section in the "Administering Campus Manager" chapter of the User Guide for Campus Manager 4.0.6
Adding Devices to DCR Using Common Services Device and Credential Admin
The Device Management option in Device and Credential Admin (DCA) helps you manage the list of devices and their credentials.
To add a device:
Step 1
The Device Management page appears.
The Device Management UI helps you perform operations on Standard Devices, Cluster Managed devices and Auto Update devices. Operations on Auto Update Servers can be performed only at the Auto Update Server Management UI.
The Device Summary window displays the devices and groups in DCA.
Step 2
The Device Properties page appears. The Device Information dialog box provides three device management types:
•
•
•
•
For more information, see the "Adding Devices" Online help or the "Managing Devices" section of the User Guide for CiscoWorks Common Services 3.0.5.
To import bulk of devices:
Step 1
The Device Management page appears.
Step 2
The Import Devices popup window appears.
Step 3
•
•
•
For more information, see the "Importing and Devices and Credentials" Online help or the "Managing Devices" section of the User Guide for CiscoWorks Common Services 3.0.5.
Adding Devices to IPM
You must manually import devices to IPM to manage devices. You can perform this task by selecting Internetwork Performance Monitor > Admin > Import From Device and Credential Repository.
Note
You can import devices as:
•
When you import devices as Sources, IPM contacts the device and adds them only if they are running IOS image with IP SLA feature and if the Read and Write community strings are provided.
•
When devices are imported as Target IP SLA Responders, if the device has a Read community string, IPM verifies whether the IP SLA responder is enabled on the target. If there is no Read community string, the target's IP SLA responder status is not verified.
•
When you import devices as Target IP Devices, IPM adds the device without either contacting the device or making any verification. When you import devices from the Device and Credentials Repository, if the devices already exist in IPM, they are updated.
For more information see the "Defining a Collector" section of the User Guide for Internetwork Performance Monitor 2.6.
Editing Device Credentials
After adding/importing the devices to DCR, you can edit the device credentials such as SNMP RO, SNMP RW, username, password, etc.
You can edit the credentials for a single device or bulk of devices using the Common Services Device Management Window.
To edit the device credentials for a single device:
Step 1
The Device Management page appears.
Step 2
Step 3
The Device Properties dialog box appears.
The Devices column lists all devices selected. From the Devices pane, you should separately select each device that you need to edit.
Step 4
The current attributes are automatically populated in the device information fields.
Step 5
For more information, see the "Editing Device Identity" Online help or the "Managing Devices" section of the User Guide for CiscoWorks Common Services 3.0.5.
Step 6
To edit the device credentials for bulk of devices:
Step 1
The Device Management page appears.
Step 2
Step 3
The Standard Credentials dialog box appears.
Step 4
For more information, see the "Editing Device Credentials" Online help or the "Managing Devices" section of the User Guide for CiscoWorks Common Services 3.0.5.
Step 5
Using Device Selector
Device Selector populates the devices for device selection from Device Center. You can select the device you want to troubleshoot or manage using the Device Selector. The devices are listed in the appropriate groups based on System-defined and User-defined group rules.
Using Simple Search and Advanced Search
You can do a simple search for devices by entering the devices name (Display Name) in the Search Input field in the Device Management window.
The search is based on the Display Name that you view in Device Selector. This Display Name is entered when you add devices to the Device and Credential Repository (Common Services > Device and Credentials > Device Management).
For advanced search, you can use the Advanced Search icon in the Device Management window to specify a set of rules. Advanced search is based on the attributes of the CiscoWorks Grouping Services Server.
In the Advanced Search dialog box, you can create rules to search for devices.
For more information, see the Online help or the User Guide for CiscoWorks Common Services 3.0.5.
Performing Maintenance on Your CiscoWorks Server
As an administrator, you need to perform maintenance to keep your information updated and to get rid of unnecessary or outdated reports and data on the system.
The CiscoWorks server maintenance tasks include:
Performing Regular Backups
You can schedule immediate, daily, weekly, or monthly automatic database backups. You should back up the database regularly so that you have a safe copy of the database.
Common Services uses multiple databases to store client application data. These databases are backed up whenever you perform a backup.
To back up data:
Step 1
The Set Backup Schedule dialog box appears.
Step 2
•
•
•
The Time field is not enabled if you have selected Immediate as the Frequency.
•
–
–
–
–
Step 3
The Schedule Backup message verifies your schedule and provides the location of backup log files.
You can verify backup status by examining the log file at the following location:
On Solaris:
var/adm/CSCopx/log/dbbackup.log
On Windows:
NMSROOT/log/dbbackup.log
Where NMSROOT is the CiscoWorks installed directory.
To restore the backup data, see the "Restoring Data" Online help or the "Configuring the Server" section of the User Guide for CiscoWorks Common Services 3.0.5.
Purging the Data
Every LMS application has its own purge policies. You can define these policies by performing these tasks:
RME
You can purge RME data by performing these tasks:
•
Resource Manager Essentials > Administration > Config Mgmt > Archive Mgmt > Purge Settings.•
Resource Manager Essentials > Administration > Syslog > Set Purge Policy.•
Resource Manager Essentials > Administration > ChangeAudit > Set Purge Policy.•
Resource Manager Essentials > Admin > System Preferences > Job Purge.Campus Manager
You can purge Campus Manager data by performing these tasks:
•
Campus Manager > User Tracking > Admin > Acquisition > Delete Interval.•
Campus Manager > User Tracking > Admin > Reports > User Tracking Purge Policy.Device Fault Manager
To set up a purge schedule for fault history information, select
Device Fault Manager > Configuration > Other Configuration > Daily Purging Schedule.Maintaining the Log Files
The Logrot utility helps you manage the log files in a better fashion. Logrot is a log rotation program that can:
•
•
•
Logrot helps you add new files easily. Logrot should be installed on the same machine where you have installed Common Services.
To configure and run logrot tool, see the "Configuring the Server" section in the User Guide for CiscoWorks Common Services 3.0.5.
Launching LMS Applications Online Help
On the CiscoWorks Homepage, click Help to Launch the CiscoWorks Online help. This Help button is available at the top right corner of your CiscoWorks home page. The CiscoWorks Online help is launched in a separate browser window.
The CiscoWorks Online help window contains the following buttons and links:
Contents
(Button)
Displays the Online help table of content for the launched LMS application.
That is, if you have launched Common Services Online help, the table of content for the Common Services application appears.
Index
(Button)
Displays the index entries for the launched LMS application.
That is, if you have launched Common Services Online help, the index entries for the Common Services application appears.
Search
(Button)
Allows you search any key words within the launched LMS application.
That is, if you have launched Common Services Online help, you can search for any keywords within the Common Services Online help.
•
•
That is, if you want to search in RME, select Resource Manager Essentials from application drop-down box.
Main
(Link)
This link is available in the top right corner of the CiscoWorks Online help window. See Figure 6 for details.
Launches the homepage of LMS applications Online help.
Based on your LMS installed applications, the table of contents area lists the LMS application Online help. See Figure 7 for details.
If you have installed all the LMS applications, the table of contents lists the following:
•
•
•
•
•
•
Figure 6 Launching LMS Application Online Help
Figure 7 Online Help Homepage
Using Applications in ACS Mode
This section contains information on:
•
By default, CiscoWorks Common Services uses CiscoWorks Server authentication (CiscoWorks Local) to authenticate users, and authorize them to access CiscoWorks Common Services applications.
After authentication, your authorization is based on the privileges that have been assigned to you. A privilege is a task or an operation defined within the application. The set of privileges assigned to you defines your role, and dictates the extent and type of system access you have.
You can use the Cisco Secure Access Control Server (ACS) services to add new users, a source of authentication other than the native CiscoWorks Server mechanism (that is, the CiscoWorks Local login module).
Cisco Secure ACS provides authentication, authorization, and accounting services to network devices that function as AAA clients. Cisco Secure ACS uses the TACACS+ and RADIUS protocols to provide AAA services that ensure a secure environment.
With CiscoWorks and CiscoSecure ACS integration, you can provide device level authorization. This device level authorization allows you to authorize only selected users to perform certain tasks, such as configuration updates and software image updates.
When the CiscoWorks server is in the ACS Login mode, a new device group, Secure Views is created. This allows you to perform a task on a device or restrict a set of device.
Secure Views enable filtering of group membership based on the user and the application task context in which a request is made.
Filtering is performed only when operating in ACS Login mode. While operating in non-ACS mode, no filtering is performed and evaluating a group results in all devices that group being returned.
The following are the supported Cisco Secure ACS for Windows versions:
•
•
•
•
•
•
•
•
•
We recommend that you install the Admin HTTPS PSIRT patch, if you are using ACS 3.2.3.
To install the patch:
Step 1
You must enter Cisco.com username and password after you launch this URL.
Step 2
You can find the link to the Admin HTTPS PSIRT patch, in the table.
Configuring ACS
Configure ACS after all applications are installed. If you have installed an application after configuring the CiscoWorks Login Module to the ACS mode, then the users of that application are not granted any permissions.
You have to configure this manually in Cisco Secure ACS server. However, the application except IPM is registered to Cisco Secure ACS.
To register IPM to Cisco Secure ACS, you have to run this command:
•
/opt/CSCOpx/bin/perl /opt/CSCOpx/bin/AcsRegCli.pl -register ipm
•
NMSROOT\bin\perl NMSROOT\bin\AcsRegCli.pl -register ipm
Where, NMSROOT is the CiscoWorks installed directory.
For example:
C:\Program Files\CSCOpx\bin\perl C:\Program Files\CSCOpx\bin\AcsRegCli.pl -register ipm
Multiple instances of same application using the same ACS server will share settings. Any changes in the settings, affect all instances of that application.
The System Identity user needs to be configured in ACS, with all the privileges the user has in CiscoWorks.
You can create new roles using ACS. The role you create is not shared across all the LMS applications. The role is shared across the same application in different CiscoWorks Servers registered to that particular ACS. You must create new roles for each of the LMS applications that are running on the CiscoWorks server.
For example, if you have configured 10 CiscoWorks servers with an ACS server and you have created a role in RME (for instance, RMESU), this role is shared for the RME application that runs on all 10 CiscoWorks servers.
If ACS is in HTTPS mode, you must enable ACS communication on HTTPS. To enable ACS communication, select the Connect to ACS in HTTPS mode check box in the Login Module dialog box.
For more information, see the User Guide for Cisco Secure ACS. You can find the document at:
http://www.cisco.com/en/US/products/sw/secursw/ps2086/prod_installation_guides_list.html
Integrating and Registering LMS Applications to ACS
Follow the steps as described in the Integrating with the ACS Server chapter of the CiscoWorks Common Services 3.0 white paper. This white paper is available at this location:
http://www.cisco.com/en/US/products/sw/cscowork/ps2425/prod_white_papers_list.html
Uninstalling LMS
You can uninstall LMS using the instructions in the application installation guides. Uninstall each application in the reverse order of install.
You need to uninstall all applications dependent on CiscoWorks before uninstalling CiscoWorks Common Services 3.0.5.
Frequently Asked Questions
Q.
A.
Q.
A.
http://www.microsoft.com/technet/security/bulletin/ms08-may.mspx
Q.
A.
Q.
A.
If you have a enabled Terminal Server in Application mode, disable the Terminal Server, reboot the system, and start the installation again.
See the Installation and Setup Guide for CiscoWorks Common Services 3.0.5 on Windows:
http://www.cisco.com/en/US/products/sw/cscowork/ps3996/prod_installation_guides_list.html
Q.
A.
Q.
A.
Q.
A.
Q.
A.
Q.
A.
Q.
A.
A multi-homed machine is a machine that has multiple NIC cards, each configured with different IP addresses. To run CiscoWorks Common Services on a multi-homed machine, there are two requirements.
–
–
See the Release Notes for CiscoWorks Common Services 3.0.5 (Includes CiscoView 6.1.5):
http://www.cisco.com/en/US/products/sw/cscowork/ps3996/prod_release_notes_list.html
Q.
A.
–
–
–
–
–
–
–
If you have installed a licensed version of LMS 2.6, you can check the LMS version in the Bundles Installed table (Common Services > Software Center > Software Update). The LMS version should be 2.6.
Q.
A.
Q.
A.
Q.
A.
Q.
A.
You can generate this report by selecting Common Services > Device and Credentials > Reports. This report is available only after configuring CiscoWorks with Cisco Secure ACS server.
Related Documentation
Note
The CiscoWorks LAN Management Solution 2.6 related documents are available in HTML and PDF formats on Cisco.com at:
http://www.cisco.com/en/US/products/sw/cscowork/ps2425/index.html
Note
Adobe Acrobat 4.0 or later is required.•
–
–
•
–
–
•
–
–
–
•
LAN Management Solution 2.6
The following are the available user documents for LAN Management
Solution 2.6:•
The above document is available in the LMS 2.6 product package and also on Cisco.com at this URL:
http://www.cisco.com/en/US/products/sw/cscowork/ps2425/prod_installation_guides_list.html
•
http://www.cisco.com/en/US/products/sw/cscowork/ps2425/prod_white_papers_list.html
•
http://www.cisco.com/en/US/products/sw/cscowork/ps2425/index.html
Common Services 3.0.5
The following are the available user documents for Common Services 3.0.5:
•
•
•
•
•
•
All these documents are available on Cisco.com at this URL:
http://www.cisco.com/en/US/products/sw/cscowork/ps3996/tsd_products_support_series_home.html
CiscoView 6.1.5
User Guide for CiscoView 6.1.5
This document is available on Cisco.com at this URL:
http://www.cisco.com/en/US/products/sw/cscowork/ps4565/products_user_guide_list.html
Resource Manager Essentials 4.0.5
The following are the available user documents for RME 4.0.5:
•
•
•
•
•
•
All these documents are available on Cisco.com at this URL:
http://cisco.com/en/US/products/sw/cscowork/ps2073/tsd_products_support_series_home.html
The RME Troubleshooting Tips and FAQs is available at this URL:
http://cisco.com/en/US/products/sw/cscowork/ps2073/prod_troubleshooting_guide09186a008036dff2.html
Campus Manager 4.0.6
The following are the available user documents for Campus Manager 4.0.6:
•
•
•
•
•
•
All these documents are available on Cisco.com at this URL:
http://cisco.com/en/US/products/sw/cscowork/ps563/tsd_products_support_series_home.html
Device Fault Manager 2.0.6
The following are the available user documents for DFM 2.0.6:
•
•
•
•
•
•
All these documents are available on Cisco.com at this URL:
http://www.cisco.com/en/US/products/sw/cscowork/ps2421/tsd_products_support_series_home.html
Internetwork Performance Monitor 2.6
The following are the available user documents for IPM 2.6:
•
•
•
All these documents are available on Cisco.com at this URL:
http://www.cisco.com/en/US/products/sw/cscowork/ps1008/tsd_products_support_series_home.html
Obtaining Documentation
Cisco documentation and additional literature are available on Cisco.com. This section explains the product documentation resources that Cisco offers.
Cisco.com
You can access the most current Cisco documentation at this URL:
http://www.cisco.com/techsupport
You can access the Cisco website at this URL:
You can access international Cisco websites at this URL:
http://www.cisco.com/public/countries_languages.shtml
Product Documentation DVD
The Product Documentation DVD is a library of technical product documentation on a portable medium. The DVD enables you to access installation, configuration, and command guides for Cisco hardware and software products. With the DVD, you have access to the HTML documentation and some of the PDF files found on the Cisco website at this URL:
http://www.cisco.com/univercd/home/home.htm
The Product Documentation DVD is created monthly and is released in the middle of the month. DVDs are available singly or by subscription. Registered Cisco.com users can order a Product Documentation DVD (product number DOC-DOCDVD= or DOC-DOCDVD=SUB) from Cisco Marketplace at the Product Documentation Store at this URL:
http://www.cisco.com/go/marketplace/docstore
Ordering Documentation
You must be a registered Cisco.com user to access Cisco Marketplace. Registered users may order Cisco documentation at the Product Documentation Store at this URL:
http://www.cisco.com/go/marketplace/docstore
If you do not have a user ID or password, you can register at this URL:
http://tools.cisco.com/RPF/register/register.do
Documentation Feedback
You can provide feedback about Cisco technical documentation on the Cisco Technical Support & Documentation site area by entering your comments in the feedback form available in every online document.
Cisco Product Security Overview
Cisco provides a free online Security Vulnerability Policy portal at this URL:
http://www.cisco.com/en/US/products/products_security_vulnerability_policy.html
From this site, you will find information about how to do the following:
•
•
•
A current list of security advisories, security notices, and security responses for Cisco products is available at this URL:
To see security advisories, security notices, and security responses as they are updated in real time, you can subscribe to the Product Security Incident Response Team Really Simple Syndication (PSIRT RSS) feed. Information about how to subscribe to the PSIRT RSS feed is found at this URL:
http://www.cisco.com/en/US/products/products_psirt_rss_feed.html
Reporting Security Problems in Cisco Products
Cisco is committed to delivering secure products. We test our products internally before we release them, and we strive to correct all vulnerabilities quickly. If you think that you have identified a vulnerability in a Cisco product, contact PSIRT:
•
An emergency is either a condition in which a system is under active attack or a condition for which a severe and urgent security vulnerability should be reported. All other conditions are considered nonemergencies.
•
In an emergency, you can also reach PSIRT by telephone:
•
•
Tip
Never use a revoked encryption key or an expired encryption key. The correct public key to use in your correspondence with PSIRT is the one linked in the Contact Summary section of the Security Vulnerability Policy page at this URL:
http://www.cisco.com/en/US/products/products_security_vulnerability_policy.html
The link on this page has the current PGP key ID in use.
If you do not have or use PGP, contact PSIRT to find other means of encrypting the data before sending any sensitive material.
Product Alerts and Field Notices
Modifications to or updates about Cisco products are announced in Cisco Product Alerts and Cisco Field Notices. You can receive Cisco Product Alerts and Cisco Field Notices by using the Product Alert Tool on Cisco.com. This tool enables you to create a profile and choose those products for which you want to receive information.
To access the Product Alert Tool, you must be a registered Cisco.com user. (To register as a Cisco.com user, go to this URL: http://tools.cisco.com/RPF/register/register.do) Registered users can access the tool at this URL: http://tools.cisco.com/Support/PAT/do/ViewMyProfiles.do?local=en
Obtaining Technical Assistance
Cisco Technical Support provides 24-hour-a-day award-winning technical assistance. The Cisco Technical Support & Documentation website on Cisco.com features extensive online support resources. In addition, if you have a valid Cisco service contract, Cisco Technical Assistance Center (TAC) engineers provide telephone support. If you do not have a valid Cisco service contract, contact your reseller.
Cisco Technical Support & Documentation Website
The Cisco Technical Support & Documentation website provides online documents and tools for troubleshooting and resolving technical issues with Cisco products and technologies. The website is available 24 hours a day at this URL:
http://www.cisco.com/techsupport
Access to all tools on the Cisco Technical Support & Documentation website requires a Cisco.com user ID and password. If you have a valid service contract but do not have a user ID or password, you can register at this URL:
http://tools.cisco.com/RPF/register/register.do
Note
Tip
If you suspect that the browser is not refreshing a web page, force the browser to update the web page by holding down the Ctrl key while pressing F5.
To find technical information, narrow your search to look in technical documentation, not the entire Cisco.com website. On the Cisco.com home page, click the Advanced Search link under the Search box and then click the Technical Support & Documentation.radio button.
To provide feedback about the Cisco.com website or a particular technical document, click Contacts & Feedback at the top of any Cisco.com web page.
Submitting a Service Request
Using the online TAC Service Request Tool is the fastest way to open S3 and S4 service requests. (S3 and S4 service requests are those in which your network is minimally impaired or for which you require product information.) After you describe your situation, the TAC Service Request Tool provides recommended solutions. If your issue is not resolved using the recommended resources, your service request is assigned to a Cisco engineer. The TAC Service Request Tool is located at this URL:
http://www.cisco.com/techsupport/servicerequest
For S1 or S2 service requests, or if you do not have Internet access, contact the Cisco TAC by telephone. (S1 or S2 service requests are those in which your production network is down or severely degraded.) Cisco engineers are assigned immediately to S1 and S2 service requests to help keep your business operations running smoothly.
To open a service request by telephone, use one of the following numbers:
Asia-Pacific: +61 2 8446 7411
Australia: 1 800 805 227
EMEA: +32 2 704 55 55
USA: 1 800 553 2447For a complete list of Cisco TAC contacts, go to this URL:
http://www.cisco.com/techsupport/contacts
Definitions of Service Request Severity
To ensure that all service requests are reported in a standard format, Cisco has established severity definitions.
Severity 1 (S1)—An existing network is "down" or there is a critical impact to your business operations. You and Cisco will commit all necessary resources around the clock to resolve the situation.
Severity 2 (S2)—Operation of an existing network is severely degraded, or significant aspects of your business operations are negatively affected by inadequate performance of Cisco products. You and Cisco will commit full-time resources during normal business hours to resolve the situation.
Severity 3 (S3)—Operational performance of the network is impaired while most business operations remain functional. You and Cisco will commit resources during normal business hours to restore service to satisfactory levels.
Severity 4 (S4)—You require information or assistance with Cisco product capabilities, installation, or configuration. There is little or no effect on your business operations.
Obtaining Additional Publications and Information
Information about Cisco products, technologies, and network solutions is available from various online and printed sources.
•
•
http://www.cisco.com/go/marketplace/
•
•
•
•
http://www.cisco.com/en/US/products/index.html
•
http://www.cisco.com/discuss/networking
•
http://www.cisco.com/univercd/cc/td/doc/abtunicd/136957.htm
•
http://www.cisco.com/en/US/learning/index.html
Notices
The following notices pertain to this software license.
OpenSSL/Open SSL Project
This product includes software developed by the OpenSSL Project for use in the OpenSSL Toolkit (http://www.openssl.org/).
This product includes cryptographic software written by Eric Young (eay@cryptsoft.com).
This product includes software written by Tim Hudson (tjh@cryptsoft.com).
License Issues
The OpenSSL toolkit stays under a dual license, i.e. both the conditions of the OpenSSL License and the original SSLeay license apply to the toolkit. See below for the actual license texts. Actually both licenses are BSD-style Open Source licenses. In case of any license issues related to OpenSSL please contact openssl-core@openssl.org.
OpenSSL License:
Copyright © 1998-2007 The OpenSSL Project. All rights reserved.
Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met:
1.
2.
3.
4.
5.
6.
"This product includes software developed by the OpenSSL Project for use in the OpenSSL Toolkit (http://www.openssl.org/)".
THIS SOFTWARE IS PROVIDED BY THE OpenSSL PROJECT "AS IS"' AND ANY EXPRESSED OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE OpenSSL PROJECT OR ITS CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
This product includes cryptographic software written by Eric Young (eay@cryptsoft.com). This product includes software written by Tim Hudson (tjh@cryptsoft.com).
Original SSLeay License:
Copyright © 1995-1998 Eric Young (eay@cryptsoft.com). All rights reserved.
This package is an SSL implementation written by Eric Young (eay@cryptsoft.com).
The implementation was written so as to conform with Netscapes SSL.
This library is free for commercial and non-commercial use as long as the following conditions are adhered to. The following conditions apply to all code found in this distribution, be it the RC4, RSA, lhash, DES, etc., code; not just the SSL code. The SSL documentation included with this distribution is covered by the same copyright terms except that the holder is Tim Hudson (tjh@cryptsoft.com).
Copyright remains Eric Young's, and as such any Copyright notices in the code are not to be removed. If this package is used in a product, Eric Young should be given attribution as the author of the parts of the library used. This can be in the form of a textual message at program startup or in documentation (online or textual) provided with the package.
Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met:
1.
2.
3.
"This product includes cryptographic software written by Eric Young (eay@cryptsoft.com)".
The word `cryptographic' can be left out if the routines from the library being used are not cryptography-related.
4.
THIS SOFTWARE IS PROVIDED BY ERIC YOUNG "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE AUTHOR OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
The license and distribution terms for any publicly available version or derivative of this code cannot be changed. i.e. this code cannot simply be copied and put under another distribution license [including the GNU Public License].
CCDE, CCVP, Cisco Eos, Cisco StadiumVision, the Cisco logo, DCE, and Welcome to the Human Network are trademarks; Changing the Way We Work, Live, Play, and Learn is a service mark; and Access Registrar, Aironet, AsyncOS, Bringing the Meeting To You, 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, Collaboration Without Limitation, Enterprise/Solver, EtherChannel, EtherFast, EtherSwitch, Event Center, 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, IronPort, the IronPort logo, LightStream, Linksys, MediaTone, MeetingPlace, MGX, Networkers, Networking Academy, Network Registrar, PCNow, PIX, PowerPanels, ProConnect, ScriptShare, SenderBase, SMARTnet, Spectrum Expert, StackWise, The Fastest Way to Increase Your Internet Quotient, TransPath, WebEx, and the WebEx logo are registered trademarks of Cisco Systems, Inc. and/or its affiliates in the United States and certain other countries.
All other trademarks mentioned in this document or Website are the property of their respective owners. The use of the word partner does not imply a partnership relationship between Cisco and any other company. (0801R)
