 Feedback
|
Table Of Contents
Quick Start Guide for LAN Management Solution 2.5
SUPPLEMENTAL LICENSE AGREEMENT
LAN Management Solution 2.5 Overview
Server and Client System Requirements
Solaris Patches for LAN Management Solution
LAN Management Solution Port Usage
Installing LAN Management Solution 2.5
Installing CiscoWorks Common Services 3.0
Installing CiscoWorks Common Services 3.0 on Solaris
Installing CiscoWorks Common Services 3.0 on Windows
Installing Resource Manager Essentials 4.0
Installing Resource Manager Essentials 4.0 on Solaris
Installing Resource Manager Essentials 4.0 on Windows
Installing Campus Manager 4.0 on Solaris
Installing Campus Manager 4.0 on Windows
Installing Device Fault Manager 2.0
Installing Device Fault Manager 2.0 on Solaris
Installing Device Fault Manager 2.0 on Windows
Installing Internetwork Performance Monitor 2.6
Installing Internetwork Performance Monitor 2.6 on Solaris
Installing Internetwork Performance Monitor 2.6 on Windows
Invoking the CiscoWorks Homepage
Understanding the CiscoWorks Homepage
CiscoWorks Product Updates Panel
Configuring Device Discovery Using Campus Manager
Adding Devices Using the Device and Credential Admin
Setting Up System Identity User
Configuring Master Self Signed Certificate
Configuring the CiscoWorks Homepage
Using Applications in ACS Mode
Registering Applications to the ACS
Enabling Browser-Server Security From the CiscoWorks Server
Obtaining Technical Assistance
Cisco Technical Support Website
Definitions of Service Request Severity
Obtaining Additional Publications and Information
Quick Start
Quick Start Guide for LAN Management Solution 2.5
1 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:
•
CiscoWorks Common Services with CiscoView: Contains shared resources used by other components in this solution. In many cases, all components in this solution can be installed on a single server. If some components of this solution are installed on separate servers, a copy of CiscoWorks Common Services can be installed with each component in the Customer's network management environment.
•
•
•
•
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.
2 LAN Management Solution 2.5 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 some applications before use.
Caution
You can select any one of the following two versions of LMS 2.5:
•
•
LAN Management Solution 2.5 does not coexist with any other Solution.
In this document you will find:
•
•
•
•
•
•
Licensing
The LMS 2.5 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.
Understanding Licensing Terms
Table 1 describes PAK, PIN, License file and its usage.
Table 1 Understanding PAK, PIN, and License File
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 only a PIN is entered, LMS will run normally, but you will be periodically reminded to complete the license process.
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 product license before installing the LMS 2.5.
If the person 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 automatically remind the administrator to complete the licensing process.
License file
When you register your LMS purchase on the product licensing area of Cisco.com, you will receive a license file. You need to provide 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, use this site to get your license file: http://www.cisco.com/go/license/public
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
As you begin the LMS installation process, you must first install CiscoWorks Common Services 3.0 (see Server and Client System Requirements). You will not be prompted for registration information during this process. After Common Services is installed on your LMS server, you can install LMS applications, such as RME 4.0, Campus 4.0, DFM 2.0 and IPM 2.6.
The first LMS application you install, prompts you to provide the LMS licensing information. (see Figure 1) The LMS installation program prompts you to enter either the license file, or the PIN and PAK. We recommend that you complete the license registration process at this point.
The LMS installer only prompts you once per server for licensing information that is used by all components of the solution. If you provide a valid license or the PIN and PAK while installing the first LMS application on a given server, the other applications installed later on that server will not prompt for a license.
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 same as that of a purchased product; except that you will be prompted by each of the LMS applications to select the Evaluation Only option from the Licensing Information page (see Figure 1.)
If you choose to run any application in evaluation mode, the application will stop functioning after 90 days. The evaluation period can NOT be extended. If you have a purchased 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 and license the product using the PAK and PIN provided with the product. For details see, "Licensing Your Product" section.
Licensing Your Product
We recommend that prior to installing the LMS 2.5 product, that 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, use this site to get your license file: http://www.cisco.com/go/license/public
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 prior to 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.5 Large Enterprise Unrestricted Licensing
Users of LMS 2.5 for Large Enterprises often require individual LMS applications such as DFM or RME to be run on separate servers to support large number of devices or to meet certain performance criteria.
When more than one server is used to host the 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, Release 2.5 for Solaris and Windows.
Additional Information Online
Registered Cisco.com users can access the most current Device Package Updates, and Latest Adapters for 3rd party network management applications at the following locations:
•
–
–
http://www.cisco.com/cgi-bin/tablebuild.pl/cw2000-campus
–
http://www.cisco.com/cgi-bin/tablebuild.pl/cw2000-dfm
–
http://www.cisco.com/cgi-bin/tablebuild.pl/cw2000-rme
•
http://www.cisco.com/cgi-bin/tablebuild.pl/cw2000-nnm
3 Server and Client System Requirements
This section provides LAN Management Solution 2.5 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.5 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.
Table 3 Minimum Server Requirements for Solaris Systems
Hardware
•
•
•
•
Software
For UltraSPARC IIIi: Solaris 2.8 and 2.9
Available memory (RAM)
•
Available disk space
•
•
•
We recommend that you set swap space to twice the size of RAM.
1 To verify the file system: Enter df -k at the command prompt.
Table 4 Minimum Server Requirements for Windows Systems
Hardware
•
•
•
•
Software for Windows
One of the following:
•
•
•
•
Available memory (RAM)
•
•
Available disk space
•
•
•
We recommend that you set virtual memory to twice the size of RAM.
1 To verify the Service Pack version on Windows, select Start > Run, then enter winver.
2 This version of LMS does not support Terminal Services on Windows 2000 Advanced Server. Terminal Services must be turned off when you install LMS.
3 Install LMS2.5 on an NTFS file system. Do not install LMS 2.5 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 6 Browser Requirements
Internet Explorer (recommended)
5.0.0.3802 or later,
and
Java Plug-in version 1.4.2_042
6.0.26 and 6.0.28
Any one of the following:
•
•
6.0 (6.0.3790.0)
Windows Server 20033
Netscape Navigator
—
7.1
Any one of the following:
•
•
Netscape Navigator (Downloaded from Sun site only)
—
7.0
Solaris 2.8 or 2.9
Mozilla
—
1.7.1
Windows
Mozilla
—
1.7
Solaris 2.8 or 2.9
1 Java Virtual Machine. To verify JVM, select View > Java Console in Internet Explorer and Communicator > Tools > Server > Java Console in Netscape Navigator. If Java Console is not listed in View, you must enable it. To enable Java Console, in Internet Explorer, select Tools > Internet Options > Advanced. In the JVM section, select the Java Console option. Restart Internet Explorer.
2 You can upgrade to Java Plug-in version 1.4.2_06 manually. See 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 would best suit your needs and optimize performance.
Below are the tested numbers for each application in standalone mode:
•
•
•
•
•
The supported concurrent users for LMS 2.5 are:
•
•
More number of concurrent 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 the LAN Management Solution 2.5.
Note
Table 7 Solaris Patches for LAN Management Solution 2.51
Solaris 2.8
111327-05
110945-08
110934-16
110898-09
109326-14
108827-40
108528-29
111626-03
108652-81
108921-21
108940-62
110951-01
110662-02
110615-01
110286-02
110951-05
110662-12
110615-11
108964-06
Solaris 2.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
112808-06
1 Use the showrev -p command to verify that these patches have been applied.
LAN Management Solution Port Usage
This section provides a list of ports used by the various CiscoWorks components.
4 Installation Paths
You might already have the previous version of LMS installed. Review the information in Table 9 to determine what software is required for the LMS component applications to function properly.
5 Upgrade Options
Table 10 describes the recommended sequence for upgrading individual LAN Management Solution 2.5 (LMS) component applications when prior versions of these applications are already installed on your system. We recommend that you install CiscoWorks LAN Management Solution 2.5 on a machine that has no other CiscoWorks solution applications installed on it.
Note
6 Installing LAN Management Solution 2.5
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 begin:
•
•
•
•
–
–
Prerequisites
This section describes the factors that you should consider before installing LMS 2.5.
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:
•
Install device IDU after installing the application.
•
Install the device package after installing the application.
•
–
–
If you select another directory during installation, the application is installed in that directory.
•
•
On Windows, if errors occur during installation, check the installation log in the root directory on the drive where the operating system is installed. Each installation creates a new log file. For example, the CiscoWorks Common Services installation creates SystemDrive:\CiscoWorks_setupxxx.log, where xxx is the log file for the last CiscoWorks application installed.
•
On Solaris, we do not recommend ending the installation, using Ctrl-C. You will be required to manually cleanup the installation directories.
•
•
•
•
For help with NMS integration, see the User Guide for CiscoWorks Integration Utility 1.6. You can find this document:
–
http://www.cisco.com/univercd/cc/td/doc/product/rtrmgmt/cw2000/cw2000_d/index.htm
•
Order of Installation
Install each application of LMS 2.5 in the following order:
Step 1
Step 2
Step 3
Step 4
Step 5
7 Installing CiscoWorks Common Services 3.0
Installing CiscoWorks Common Services takes approximately 40 minutes.
Installing CiscoWorks Common Services 3.0 on Solaris
To install CiscoWorks Common Services 3.0 (CWCS) on Solaris:
Step 1
•
From the CD-ROM root directory, look for CD-ROMDrive/Documentation/InstallSetupGuideForComSerCVSol.pdf
•
http://www.cisco.com/univercd/cc/td/doc/product/rtrmgmt/cw2000/cw2000_d/
index.htmStep 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. If you select Custom install, you must install all components or LMS will not function correctly.
Step 5
a.
b.
c.
Follow the steps in Chapter 3, "Preparing to Use CiscoWorks".
Step 6
ESS, EssMonitor, CmfDbEngine, CmfDbMonitor, DCRServer, CMFOGSServer, LicenseServer, Tomcat, Apache, RmeOrb, RmeGatekeeper, EDS, EDS-GCF, EDS-TR, jrm, diskWatcher, CSRegistryServer, TomcatMonitor, FDRewinder.
If you receive error messages during the installation, or cannot complete the tasks in this step, see Appendix A, "Troubleshooting the Installation".
Installing CiscoWorks Common Services 3.0 on Windows
Before you begin:
•
•
•
To install CiscoWorks Common Services 3.0 (CWCS) on Windows:
Step 1
•
From the CD-ROM root directory, look for CD-ROMDrive\Documentation\InstallSetupGuideForComSerCVWin.pdf
•
http://www.cisco.com/univercd/cc/td/doc/product/rtrmgmt/cw2000/cw2000_d/
index.htmStep 2
•
•
•
•
However, you cannot configure ACS as an AAA client, which is required when ACS and CiscoWorks coexists. 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. If you select Custom install, you must install all the LMS applications. Otherwise, LMS will not function correctly.
Step 5
a.
b.
c.
Follow the steps in Chapter 3, "Preparing to Use CiscoWorks Common Services".
Step 6
Tomcat, Apache, TomcatMonitor, RmeOrb, RmeGatekeeper, EDS, EDS-TR, Proxy, LicenseServer, ESS, EssMonitor, diskWatcher, CSRegistryServer, CmfDbEngine, CmfDbMonitor, DCRServer, CMFOGSServer, EDS-GCF, jrm
If you receive error messages during the installation, or cannot complete the tasks in this step, see Appendix A, "Troubleshooting the Installation".
8 Installing Resource Manager Essentials 4.0
Installing Resource Manager Essentials takes approximately 30 minutes.
Installing Resource Manager Essentials 4.0 on Solaris
To install Resource Manager Essentials 4.0 (RME) on Solaris:
Step 1
•
From the CD-ROM root directory, look for CD-ROMDrive/RME/Documentation/InstallSetupGuideForEssentialsSol.pdf
•
http://www.cisco.com/univercd/cc/td/doc/product/rtrmgmt/cw2000/cw2000e/index.htm
Step 2
We recommend that you change the RME database password when prompted to do so.
Step 3
a.
b.
c.
Or
After you complete the installation, verify that the following processes are running using Common Services > Server > Admin > Processes:
RMEDbEngine, RMEDbMonitor, ConfigMgmtServer, NCTemplateMgr, RMEOGSServer, SyslogCollector, EssentialsDM, CTMJrmServer, ChangeAudit, ICServer, and SyslogAnalyzer.
Follow the steps in Chapter 2, "Preparing to Use RME".
If you receive error messages during the installation, or cannot access the home page, see Appendix C, "Troubleshooting the Installation".
Installing Resource Manager Essentials 4.0 on Windows
To install Resource Manager Essentials 4.0 (RME) on Windows:
Step 1
•
From the CD-ROM root directory, look for CD-ROMDrive\Documentation\InstallSetupGuideForEssentialsWin.pdf
•
http://www.cisco.com/univercd/cc/td/doc/product/rtrmgmt/cw2000/cw2000e/index.htm
Step 2
We recommend that you change the RME database password when prompted to do so.
Step 3
a.
b.
c.
Or
After you complete the installation, verify that the following processes are running using Common Services > Server > Admin > Processes:
RMEDbEngine, RMEDbMonitor, ConfigMgmtServer, NCTemplateMgr, RMEOGSServer, SyslogCollector, EssentialsDM, CTMJrmServer, ChangeAudit, ICServer, and SyslogAnalyzer.
Follow the steps in Chapter 2, "Preparing to Use RME".
If you receive error messages during the installation, or cannot access the Homepage, see Appendix C, "Troubleshooting the Installation".
9 Installing Campus Manager 4.0
Installing Campus Manager takes approximately 11 minutes.
Installing Campus Manager 4.0 on Solaris
To install Campus Manager 4.0 (Campus) on Solaris:
Step 1
•
From the CD-ROM root directory, look for CD-ROMDrive/Documentation/InstallSetupGuideForCampusSol.pdf
•
http://www.cisco.com/univercd/cc/td/doc/product/rtrmgmt/cw2000/camp_mgr/
index.htmStep 2
We recommend that you change the ANI database password when prompted to do so.
Step 3
a.
b.
c.
Or
After you complete the installation, verify that Campus was installed correctly by accessing the CiscoWorks Server, logging in as administrator, and selecting Campus Manager > Administration > System Configuration.
Follow the steps in Chapter 3, "Preparing to Use Campus Manager".
If you receive error messages during the installation, or cannot access the server, see Appendix A, "Troubleshooting the Installation".
Installing Campus Manager 4.0 on Windows
To install Campus Manager 4.0 on Windows:
Step 1
•
From the CD-ROM root directory, look for CD-ROMDrive\Documentation\InstallSetupGuideForCampusWin.pdf
•
http://www.cisco.com/univercd/cc/td/doc/product/rtrmgmt/cw2000/camp_mgr/
index.htmStep 2
We recommend that you change the ANI database password when prompted to do so.
Step 3
a.
b.
The Application Registration Status page appears.
c.
Or
After the installation, verify that Campus Manager was correctly installed by accessing the CiscoWorks Server, logging in as administrator, and selecting Campus Manager > Administration > System Configuration.
If your client does not have Java plug-in, you will receive a message asking if you want to install it. Campus Manager requires the plug-in for Topology Services, Path Analysis, Discrepancy Reports and VLAN Port Assignment. The plug-in is not required for User Tracking and Campus Manager Administration.
Follow the steps in Chapter 3, "Preparing to Use Campus Manager".
If you receive error messages during the installation, or cannot access the server, see Appendix A, "Troubleshooting the Installation".
10 Installing Device Fault Manager 2.0
Installing Device Fault Manager (DFM) takes approximately 10 minutes.
Installing Device Fault Manager 2.0 on Solaris
To install Device Fault Manager 2.0 (DFM) on Solaris:
Step 1
•
From the CD-ROM root directory, look for CD-ROMDrive/Documentation/dfm20_solaris_install_and_setup.pdf
•
http://www.cisco.com/univercd/cc/td/doc/product/rtrmgmt/cw2000/dfm/dfm20/install/
index.htmStep 2
We recommend that you change the DFM database password when prompted to do so.
Step 3
a.
b.
The Application Registration Status page appears.
c.
Or
After you complete the installation, verify that Device Fault Manager was installed correctly by verifying that the DfmServer process is running. To verify, log on to the CiscoWorks Homepage as the administrator and select Common Services > Server > Admin > Processes.
If you receive error messages during the installation, or cannot access the server, check the installation log at /var/tmp/ciscoinstall.log.
Installing Device Fault Manager 2.0 on Windows
To install Device Fault Manager 2.0 (DFM) on Windows:
Step 1
•
From the CD-ROM root directory, look for CD-ROMDrive\Documentation\dfm20_windows_install_and_setup.pdf
•
http://www.cisco.com/univercd/cc/td/doc/product/rtrmgmt/cw2000/dfm/dfm20/install/
index.htmStep 2
We recommend that you change the DFM database password when prompted to do so.
Step 3
a.
b.
The Application Registration Status page appears.
c.
Or
After you complete the installation, verify that Device Fault Manager was installed properly by verifying that the DfmServer process is running. To verify, log on to the CiscoWorks Homepage as the administrator and select Common Services > Server > Admin > Processes.
If you receive error messages during the installation, or cannot access the server, check the installation log at System Drive\CiscoWorks_Setupxxx.log.
11 Installing Internetwork Performance Monitor 2.6
Installing Internetwork Performance Monitor (IPM) takes approximately 20 minutes. The installation script installs Internetwork Performance Monitor in the following default locations:
•
•
Installing Internetwork Performance Monitor 2.6 on Solaris
To install Internetwork Performance Monitor 2.6 on Solaris:
Step 1
•
From the CD's root directory, look for /docs/ipm26_install.pdf
•
http://www.cisco.com/univercd/cc/td/doc/product/rtrmgmt/ipmcw2k/cipm26/install/
index.htmStep 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.
Step 4
a.
b.
The Application Registration Status page appears.
c.
Or
After you complete the installation, verify that IPM was installed correctly as explained in the section "Verifying IPM Installation on Solaris" in Chapter 4.
Installing Internetwork Performance Monitor 2.6 on Windows
To install Internetwork Performance Monitor 2.6 (IPM) on Windows:
Step 1
•
From the CD's root directory, look for \\docs\ipm26_install.pdf.
•
http://www.cisco.com/univercd/cc/td/doc/product/rtrmgmt/ipmcw2k/cipm26/install/
index.htmStep 2
•
•
•
•
Step 3
Step 4
a.
b.
The Application Registration Status page appears.
c.
Or
Select Start > Programs > Internetwork Performance Monitor > IPM Server Status. If the IPM server installation is successful, a DOS window opens and the status of the IPM servers is displayed. For more information see "Verifying IPM Installation on Windows" in Chapter 5.
12 Getting Started with LMS
The topics in this section help you to work with and understand the LMS user interface.
Invoking the CiscoWorks Homepage
Enter the URL for your CiscoWorks Server in your browser.
http://server_name:port_numberwhere 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. When SSL is enabled (HTTPS), the default TCP port for CiscoWorks Server is 443.
Note
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 Installation and Setup Guide for CiscoWorks Common Services on Solaris.
Logging In
Step 1
User Name: adminPassword: passwordStep 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.
Resources Panel. See, the "Resources Panel" section.
CiscoWorks Server Name.
CiscoWorks Tool Bar. See, the "Tool Bar Items" section.
Application Panel. See, the "Application Panel" section.
CiscoWorks Product Updates Panel. See, the "CiscoWorks Product Updates 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 telnet a device.
For more information, see the "Using Device Center" chapter in the User Guide for CiscoWorks Common Services 3.0.
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 login. 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 home page. 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.
Resources Panel
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
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. CiscoWorks Homepage provides an Admin UI to accept the proxy settings. 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 top of the right hand side of the CiscoWorks Homepage:
•
•
•
13 Post-Installation Tasks
After you have installed the required applications and verified the installations, you must:
Step 1
Step 2
•
•
•
•
Step 3
The Device Management option in DCA helps you manage the list of devices and their credentials. You can:
•
•
•
•
•
•
•
Figure 3 Common Services Device Management Page
For more information, see Managing Devices Online help or the Managing Devices section in the Managing Device and Credentials chapter of the User Guide for CiscoWorks Common Services 3.0.
By default, DFM automatically synchronizes its managed inventory with the Device and Credential Repository (DCR). For more information, see the "Using Device Management chapter" of the User Guide for Device Fault Manager 2.0. After adding devices to DCR, RME automatically adds the devices in DCR to RME.
Step 4
For more information, see the online help or see Using Inventory Management chapter in the User Guide for Resource Manager Essentials 4.0.
Step 5
For more information, see the online help or see the "Configuring and Administering DFM (Basic)" chapter in User Guide for Device Fault Manager 2.0.
Optional Steps
The following steps are optional:
Step 1
In a multi-server deployment of LMS, enable Single Sign-On to avoid separately signing on to each server. See "Enabling Single Sign-On" section.
Step 2
Step 3
Step 4
Step 5
For Campus
a.
b.
For RME
a.
b.
For DFM
a.
b.
c.
d.
e.
For IPM
a.
The Import from Device and Credential Repository page appears.
b.
The Import from Devices screen appears.
c.
–
–
–
For more information see the online help or "Defining a Collector" section of the User Guide for Internetwork Performance Monitor 2.6.
Uninstalling LMS
You can uninstall LMS using the instructions in the application installation guides. Uninstall each application in the reverse order of upgrade.
You need to uninstall all applications dependent on CiscoWorks before uninstalling CiscoWorks Common Services 3.0.
Configuring Device Discovery Using Campus Manager
To configure Device Discovery:
Step 1
A new Campus Administration page appears.
Figure 4 Campus Manager Administration page
Step 2
The SNMP Settings page appears.
Step 3
Step 4
The Discovery Settings page appears.
Step 5
Step 6
The Configure Seed Devices dialog box appears. Seed devices are devices used to initiate network discovery.
Step 7
The seed devices stored in the file have to be separated by a carriage return. That is, only one seed device can be stored per line in the file.
For example, the seed devices in the file can be entered as:
172.20.5.6172.20.118.13010.77.209.209172.20.99.210.77.210.10110.77.210.103Step 8
The IP Address Range settings screen appears. Specify IP Address Range settings as required.
If IP address range is not specified, Device Discovery will try 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.
Adding Devices Using the Device and Credential Admin
The Device Management option in Device and Credential Admin (DCA) helps you manage the list of devices and their credentials. You can use this feature to add devices, device properties, and device credentials to DCA. You can also add devices to RME, Campus, DFM and IPM.
To add devices to the device list:
Step 1
The Device Management page appears.
Note
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 Adding Devices Online help or "Managing Devices" section of the User Guide for CiscoWorks Common Services 3.0.
To do a bulk import:
Step 1
The Device Management page appears.
Step 2
The Import Devices popup window appears.
Step 3
•
•
•
For more information, see "Importing and Devices and Credentials" section of the User Guide for CiscoWorks Common Services 3.0.
Configuring Data Collection
You must configure Data Collection for Campus Manager to manage devices. You can configure data collection using the Campus Manager Administration module (select Campus Manager > Administration). Data collection configuration involves:
•
•
•
•
For more information, see the Online help or the "Using ANI Data Collection Administration" section in the "Administering Campus Manager" chapter of the User Guide for Campus Manager 4.0.
Enabling Single Sign-On
With Single Sign-On (SSO), you can use your browser session to transparently navigate to multiple CiscoWorks Servers without having to authenticate to each of them. Communication between multiple CiscoWorks Servers is enabled by a trust relationship using self-signed certificates and passwords shared between servers.
You must do the following tasks, initially:
Step 1
Figure 5 Common Services Security Settings Page
Step 2
To verify that the same username is used, for each server, select Common Services > Server > Security > Multi-Server Trust Management > System Identity Setup and verify the System Identity Setup screen.
To ensure that you use the same system identity user and password, while installing Common Services on each server, use the default username for the administrative user and enter the same password. For more information, see "Setting Up System Identity User" Online help.
Step 3
a.
The Peer Server Certificate screen appears.
b.
A popup dialog box appears.
c.
The certificate details of the imported certificate appear in the Peer Server Certificate page. For more information, see "Creating Self Signed Certificates" Online help.
Step 4
a.
The Peer Server Certificate screen appears.
b.
A popup dialog box appears.
c.
The certificate details for the Master should appear in the Peer Server Certificate screen of each Slave.
Step 5
a.
The Single Sign-On Setup page appears.
b.
c.
Step 6
a.
The Single Sign-On Setup screen appears.
b.
c.
d.
If the server is either configured as Master or Slave, you must:
•
•
Setting Up System Identity User
System Identity setup helps you to create a trust user on servers that are part of a Multi-Server setup. This user enables communication between servers part of a Domain. There can only be one System Identity User for each machine. The System Identity User you configure has to be a Peer Server User. In Non-ACS mode, the System Identity User you create has to be a Local User, with System Administrator privileges. In ACS mode, the System Identity user needs to be configured in ACS, with all the privileges the user has on CiscoWorks Server.
In non-ACS mode, the default user admin is also the system identity user. But in ACS mode, you need to add the system identity user to the ACS server. You can configure the admin user as the default System Identity User during the CiscoWorks installation.
Single Sign-On uses System Identity user password as the secret key to provide confidentiality and authenticity between Master and Slave. It is sufficient to have the same System Identity user passwords in Master and Slave, without having the same user name. We recommend that you have the same user name and password across Master and Slave.
To set up System Identity user:
Step 1
Step 2
Step 3
Configuring Master Self Signed Certificate
To configure Master's Self Signed Certificate in the Slave, select Common Services > Server > Security > Peer Server Certificate Setup > Add.
The common name (CN) in the certificate must be identical to the Master server name to be considered a valid certificate.
Configuring the CiscoWorks Homepage
CiscoWorks Homepage is the primary user interface and the launch point for all features. After you log in to Common Services, the default CiscoWorks Homepage appears.
The Application Registration, Link Registration, and Settings links under Homepage help you configure your CiscoWorks Homepage. They help you in:
•
To register your application with CiscoWorks Homepage:
From the CiscoWorks Homepage, select Common Services > Homepage > Application Registration.
Figure 6 Common Services Application Registration Status Page
•
To register your links with CiscoWorks Homepage:
From the CiscoWorks Homepage, select Common Services > Homepage > Link Registration.
•
To set up CiscoWorks Homepage:
From the CiscoWorks Homepage, select Common Services > Homepage > Settings.
For more information on Homepage configuration, see the Online help or Chapter 2, "Interacting with CiscoWorks Homepage", in User Guide for CiscoWorks Common Services 3.0.
Using Applications in ACS Mode
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, using a source of authentication other than the native CiscoWorks Server mechanism (that is, the CiscoWorks Local login module).
CiscoSecure ACS provides authentication, authorization, and accounting services to network devices that function as AAA clients. CiscoSecure ACS uses the TACACS+ and RADIUS protocols to provide AAA services that ensure a secure environment.
In ACS mode, you can create custom roles so that you can customize Common Services client applications to suit your business workflow and needs. That is, you can create a user, and assign the user with a set of privileges, that would suit your needs.
System Identity User in ACS Mode: There can only be one System Identity User per machine. The System Identity User you configure has to be a Peer Server User. In ACS mode, the System Identity user needs to be configured in ACS, with all the privileges the user has in CiscoWorks.
Configuring ACS
Configure ACS after all applications are installed. If you have installed an application after configuring the CiscoWorks Login Module to the TACACS+ mode, then the users of that application are not granted any permissions. However, the application is registered to Cisco Secure ACS.
Multiple instances of same application using the same ACS server will share settings. Any changes will affect all instances of that application.
If an application is configured with ACS and then the application is reinstalled, the application will inherit the old settings.
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 have to create new roles for each of the LMS applications that are running on the CiscoWorks Server.
For example: Assume you have configured 10 CiscoWorks Servers with an ACS server and you have created a role in RME (say, RMESU). This role is shared for the RME application that runs on all 10 CiscoWorks Servers.
Registering Applications to the ACS
To register or re-register all the installed applications to the ACS:
Step 1
The AAA Mode Setup page appears with the AAA Mode Setup dialog box.
Step 2
Step 3
•
•
•
•
The default port is 49. Secondary and Tertiary IP address/hostname details are optional.
The values true and false will not be accepted in the Primary, Secondary, and Tertiary IP Address/Hostname fields.
Step 4
•
•
•
Step 5
Step 6
If an application is already registered with ACS, the current registration will overwrite the previous one.
Step 7
Step 8
On Windows:
a.
b.
On Solaris:
a.
b.
You must enable ACS communication on HTTPS if ACS is in HTTPS mode. To enable ACS communication, select the Connect to ACS in HTTPS mode check box in the Login Module dialog box. For more information, see User Guide for Cisco Secure ACS. You can find the document at http://www.cisco.com/univercd/cc/td/doc/product/access/acs_soft/csacs4nt/acs33/user/index.htm.
Enabling Browser-Server Security From the CiscoWorks Server
To enable Browser-Server Security:
Step 1
The Browser-Server Security Mode Setup dialog box appears.
Step 2
Step 3
Step 4
Step 5
On Windows:
a.
b.
On Solaris:
a.
b.
Step 6
When you restart the CiscoWorks session after enabling SSL, you must enter the URL with the following changes:
•
•
If you do not make the above changes, CiscoWorks Server will automatically redirect you to HTTPS mode with port number 443. The port numbers mentioned above are applicable for CiscoWorks Server running on Windows.
On Solaris, if the default port (1741) is used by another application, you can select a different port during CiscoWorks Server installation. For details, see Installation and Setup Guide for CiscoWorks Common Services 3.0 (Includes CiscoView) on Solaris.
14 Where to Go Next
After you have installed the required applications, you are ready to manage your LAN environment. For more information, see the following User Guides for the LMS component applications:
•
•
•
•
•
•
You can access these documents:
•
•
From Cisco.com:
a.
b.
c.
d.
From the CiscoWorks Online help:
a.
b.
15 Related Documentation
Note
For information about installing, troubleshooting, and using the applications in the LAN Management Solution, see Table 11.
Note
Table 11 Related Documentation
more about...
CD?1
help?The known product bugs (DDTS)
Release Notes for CiscoWorks Common Services 3.0 (Includes CiscoView) on Solaris
Release Notes for CiscoWorks Common Services 3.0 (Includes CiscoView) on Windows
Release Notes for Campus Manager 4.0 on Solaris
Release Notes for Campus Manager 4.0 on Windows
Yes
Yes
Yes
Yes (PDF, HTML)
No
The known product bugs (DDTS)
(continued)
Release Notes for Device Fault Manager 2.0 on Windows
Release Notes for Device Fault Manager 2.0 on Solaris
Release Notes for Internetwork Performance Monitor 2.6
Release Notes for Resource Manager Essentials 4.0 on Solaris
Release Notes for Resource Manager Essentials 4.0 on Windows
Yes
Yes
Yes
Yes (PDF, HTML)
No
Performing a typical or custom installation
Installation and Setup Guide for CiscoWorks Common Services 3.0 (Includes CiscoView) on Solaris (DOC-7815885=)
Installation and Setup Guide for CiscoWorks Common Services 3.0 (Includes CiscoView) on Windows (DOC-7816497=)
Installation and Setup Guide for Resource Manager Essentials 4.0 on Solaris (DOC-7816504=)
Installation and Setup Guide for Resource Manager Essentials 4.0 on Windows (DOC-7816505=)
No
Yes
Yes
Yes (PDF, HTML)
No
Performing a typical or custom installation
(continued)
Installation and Setup Guide for Campus Manager 4.0 on Solaris (DOC-7816400=)
Installation and Setup Guide for Campus Manager 4.0 on Windows (DOC-7816401=)
Installation Guide for Device Fault Manager 2.0 on Solaris (DOC-7816268=)
Installation Guide for Device Fault Manager 2.0 on Windows (DOC-7816267=)
Installation Guide for Internetwork Performance Monitor 2.6 (DOC-7816653=)
No
Yes
Yes
Yes (PDF, HTML)
No
Features, tasks, and troubleshooting
Using CiscoView 6.1 (DOC-7815605=)
User Guide for CiscoWorks Common Services 3.0 (DOC-7816571=)
User Guide for Resource Manager Essentials 4.0 (DOC-7816503=)
User Guide for Campus Manager 4.0 (DOC-7816398=)
No
Yes
Yes2
Yes
Yes
Features, tasks, and troubleshooting
(continued)
User Guide for Internetwork Performance Monitor (DOC-7816652=)
User Guide for Device Fault Manager (DOC-7816266=)
No
Yes
Yes
Yes
Yes
Device Support
Supported Device Table for Resource Manager Essentials 4.03
Supported Device Table for Campus Manager 4.04
Supported Devices Table for Device Fault Manager 2.05
No
No
Yes
No
No
Integration with third party NMS
User Guide for CiscoWorks Integration Utility 1.6
No
No
Yes
No
No
1 Provided as PDF in Documentation folder on the CD-ROM.
2 From the CiscoWorks Homepage, click Help.
3 To view the RME documents on Cisco.com, log on to your Cisco.com home page, then enter the URL: http://www.cisco.com/univercd/cc/td/doc/product/rtrmgmt/cw2000/cw2000e/index.htm
4 To view the Campus documents on Cisco.com, log on to your Cisco.com home page, then enter the URL: http://www.cisco.com/univercd/cc/td/doc/product/rtrmgmt/cw2000/camp_mgr/index.htm
5 To view the DFM documents on Cisco.com, log on to your Cisco.com home page, then enter the URL: http://www.cisco.com/univercd/cc/td/doc/product/rtrmgmt/cw2000/dfm/dev_sup/dfm2_0.htm
16 Obtaining Documentation
Cisco documentation and additional literature are available on Cisco.com. Cisco also provides several ways to obtain technical assistance and other technical resources. These sections explain how to obtain technical information from Cisco Systems.
Cisco.com
You can access the most current Cisco documentation at this URL:
http://www.cisco.com/univercd/home/home.htm
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
Ordering Documentation
You can find instructions for ordering documentation at this URL:
http://www.cisco.com/univercd/cc/td/doc/es_inpck/pdi.htm
You can order Cisco documentation in these ways:
•
http://www.cisco.com/en/US/partner/ordering/index.shtml
•
17 Documentation Feedback
You can send comments about technical documentation to bug-doc@cisco.com.
You can submit comments by using the response card (if present) behind the front cover of your document or by writing to the following address:
Cisco Systems
Attn: Customer Document Ordering
170 West Tasman Drive
San Jose, CA 95134-9883We appreciate your comments.
18 Obtaining Technical Assistance
For all customers, partners, resellers, and distributors who hold valid Cisco service contracts, Cisco Technical Support provides 24-hour-a-day, award-winning technical assistance. The Cisco Technical Support Website on Cisco.com features extensive online support resources. In addition, Cisco Technical Assistance Center (TAC) engineers provide telephone support. If you do not hold a valid Cisco service contract, contact your reseller.
Cisco Technical Support Website
The Cisco Technical Support 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, 365 days a year, at this URL:
http://www.cisco.com/techsupport
Access to all tools on the Cisco Technical Support 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
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 TAC 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 TAC 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)—Your 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 operation 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 your network is impaired, but 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.
19 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://cisco.com/univercd/cc/td/doc/pcat/
•
•
•
http://www.cisco.com/go/iqmagazine
•
•
