Table Of Contents
Preparing to Install CiscoWorks LAN Management Solution 3.1
Terms and Definitions Used in LMS Installation Framework
Before You Begin Installation
License Information
Application Scaling Numbers
Standalone Server
Solution Server
Concurrent Users Supported
Licensing Your Product
Installing the Licensing File
Preparing to Install CiscoWorks LAN Management Solution 3.1
This chapter lists the necessary information that prepares you to perform an installation of CiscoWorks LMS 3.1 on both Windows and Solaris systems.
This chapter contains:
•
Terms and Definitions Used in LMS Installation Framework
•
Before You Begin Installation
•
License Information
•
Application Scaling Numbers
•
Licensing Your Product
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 to understand the licensing terminologies.
LMS Application Database Password
In LMS 3.1, the LMS Application Database Password is requested during Custom installation. This database password is used internally by all the LMS applications to communicate with the respective application's database. This password is also used while restoring or troubleshooting the database.
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.
Note
While installing applications in Custom mode alone you will be prompted to enter the LMS Application database password. In the Typical mode, this password is randomly generated.
While installing, you will come across these terms:
•
CiscoWorks Admin Password
An administrative password used while logging into the CiscoWorks server as administrator. Use a minimum of five characters.
Ensure that you have noted down the password.
You are prompted to enter this password in both Typical and Custom modes of installation.
•
System Identity Account Password
Password that is used in a multi-server environment.
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.
You must configure all the CiscoWorks servers that are part of your multi-server setup with the same system identity account password.
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.
•
CiscoWorks Guest Password
This is used while logging into the CiscoWorks server as a guest user. Use a minimum of five characters.
You are prompted to enter this password in the Custom mode of installation. In the Typical mode, this password is randomly generated.
•
Self Signed Certificate
CiscoWorks allows you to create security certificates to enable SSL communication between your client browser and management server.
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.
For more information on Self Signed Certificates, see User Inputs for Custom Installation.
In the Typical mode, this certificate is automatically generated.
For more information on passwords, see Password Rules for New Installation
•
SMTP Server
System-wide name of the SMTP server used by CiscoWorks applications to deliver reports. The default server name is localhost.
You are prompted to enter this server detail only in the Custom mode of installation. In the Typical mode, after the installation you can configure SMTP by selecting Common Services > Server > Admin > System Preferences from the CiscoWorks home page.
•
Cisco.com
Cisco.com user ID and password. This information is used while performing tasks such as downloading software images, downloading device packages, etc.
You are prompted to enter these credentials only 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).
Before You Begin Installation
This section contains the following important information that you should read before you begin installation:
•
Installation Notes
•
Installation Notes (For Solaris Only)
•
Installation Notes (For Windows Only)
Installation Notes
Before you begin the installation, read the following notes:
•
Close all open or active programs. Do not run other programs during the installation process.
•
By default, SSL is not enabled on CiscoWorks Server.
•
While launching CiscoWorks, network inconsistencies might cause installation errors if you are installing from a remote mount point.
•
If your CiscoWorks Server is integrated with any Network Management System (NMS) in your network using the Integration Utility, you must perform the integration whenever you enable or disable SSL in the CiscoWorks Server. You must do this to update the application registration in the NMS.
For help with NMS integration, see the User Guide for CiscoWorks Integration Utility 1.7. 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
•
Disable any popup blocker utility that is installed on your client system before launching CiscoWorks.
•
CiscoWorks applications are installed in the default directories:
–
On Solaris: /opt/CSCOpx
–
On Windows: SystemDrive:\Program Files\CSCOpx
Where, SystemDrive is the Windows operating system installed directory.
If you select another directory during installation, the application is installed in that directory.
The destination folder should not contain the following special characters:
–
On Solaris:
! @ # $ % ^ & * ( ) + | } { " : [ ] ; ' ? < > , . ` = ~
–
On Windows:
! @ # $ % ^ & * ( ) + | } { " [ ] ; ' / ? < > , . ` =
•
If errors occur during installation, check the installation log file:
–
On Solaris, check the installation log file /var/tmp/Ciscoworks_install_YYYYMMDD_hhmmss.log for LMS 3.1 installation
Where YYYYMMDD denotes the year, month and date of installation and hhmmss denotes the hours, minutes and seconds of installation.
For example:
/var/tmp/Ciscoworks_install_20060721_182205.log
–
On Windows, 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, for LMS 3.1, the installation log file is:
C:\Ciscoworks_install_YYYYMMDD_hhmmss.log, where YYYYMMDD denotes the year, month and date of installation and hhmmss denotes the hours, minutes and seconds of installation.
For example:
C:\Ciscoworks_install_20060721_182205.log
•
You can press Ctrl-C (on Solaris) or click Cancel (on Windows) at any time to end the installation. However, any changes to your system will not be undone.
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
We recommend that you do not terminate the installation while it is running.
•
If HP OpenView is running on your system, installation will take more time. Disable HP OpenView to run a faster installation.
•
To ensure that you have the latest device support and bug fixes for Resource Manager Essentials, Campus Manager, Device Fault Manager, and CiscoView you must install the latest Service Packs.
For download locations, see the Supported Devices.
Installation Notes (For Solaris Only)
•
On Solaris, if you select an installation directory other than the default, the /opt/CSCOpx directory is created as a link to the directory you selected.
Warning
If you remove this link after installation, the product will malfunction.
•
We recommend that you run the installation from a local CD or a local hard drive to avoid errors that may result from the network being slow or busy.
If you want to install from a local hard drive, you must copy the contents from the CD to the local hard drive. Ensure that you copy the entire contents from the CD to the hard drive.
You must preserve the timestamp when you copy the contents from the CD to the hard drive.
To preserve all the attributes including timestamp:
a.
Change the present working directory to the directory to which the CD is mounted using the command:
cd /cdrom/cdrom0
where cdrom/cdrom0 is the directory to which the CD is mounted.
b.
Create a directory where you want to copy the contents of the disk by entering:
mkdir /opt/copydisk
Make sure that this directory has enough space to hold the entire contents of the disk.
c.
Enter:
tar cpf - . | (cd /opt/copydisk && tar -xpf -)
This command preserves all attributes including the timestamp.
Installation Notes (For Windows Only)
•
You can install LMS 3.1 applications on a system with Terminal Services enabled in Remote Administration mode. However, installation of LMS 3.1 applications on a system with Terminal Services enabled in Application mode is not supported.
If you have enabled Terminal Server in Application mode, disable the Terminal Server, reboot the system, and start the installation again. See Terminal Server Support for Windows 2003 Server.
•
If Internet Information Services (IIS) is detected on your system and if you have continued the installation with IIS services, you cannot use the port number 443 for HTTPS. Instead, you must use the port numbers ranging from 1026 to 65535 for HTTPS to avoid this conflict.
•
If you are running any virus scanner while installing LMS applications, the installation might take longer to complete.
We recommend that you disable the virus scan software on your system. You can restart it after all installations are completed.
•
Check the Primary and Active regional settings before installation. They have to be set either as US English or Japanese. Other options are not supported by LMS 3.1.
You can set the Active regional settings in Control Panel > Regional and Language Options > Regional Options.
•
You must restart your system after you install LMS 3.1 to avoid any system instability on a Windows OS.
License Information
The licenses in LMS 3.1 are device based for all applications. For 10000 device licenses, applying a single serial license key to more than one server is supported. Please see the SUPPLEMENTAL LICENSE AGREEMENT section for more details.
For Internetwork Performance Monitor (IPM) alone, besides the number of devices, the number of collectors you create depends on the license.
Available Licenses (SKU) in LMS 3.1
|
Permitted number of Devices and Collectors in LMS 3.1 (RME, Campus, DFM and IPM)
|
CWLMS-3.1-100-K9
|
100 devices and 300 collectors
|
CWLMS-3.1-300-K9
|
300 devices and 1,000 collectors
|
CWLMS-3.1-1.5K-K9
|
1,500 devices and 1,500 collectors
|
CWLMS-3.1-5K-K9
|
5,000 devices and 5,000 collectors
|
CWLMS-3.1-10K-K9
|
10,000 devices and 5,000 collectors
|
Note
The LMS 100 devices license is supported only on Windows systems. This is not supported on Solaris systems.
Add-on Component(s) to LMS
Separate license is required to install CiscoWorks Health and Utilization Monitor (HUM) 1.1, add-on component to LMS 3.1. Following are the SKUs available for HUM 1.1:
Available Licenses (SKU) in HUM 1.1
|
Permitted number of Devices in HUM 1.1
|
CWHUM-1.1-S-K9
|
50 devices restricted license
|
CWHUM-1.1-M-K9
|
300 devices restricted license
|
CWHUM-1.1-L-K9
|
1000 devices restricted license
|
Upgrade Licenses (SKU) in HUM 1.1
|
CWHUM-1.1-S2M-K9
|
Upgrade from 50 devices to 300 devices
|
CWHUM-1.1-S2L-K9
|
Upgrade from 50 devices to 1000 devices
|
CWHUM-1.1-M2L-K9
|
Upgrade from 300 devices to 1000 devices
|
If you have LMS 3.0 license with Software Application Support (SAS) contracts, you can order LMS 3.1 using the Product Upgrade Tool at www.cisco.com/upgrade. The SKUs that need to be used while ordering are:.
Licenses (SKU) to upgrade from LMS 3.0
|
Permitted number of Devices
|
CWLMS-3.1-100SRK9
|
LMS 3.0 100 Device Restricted Upgrade to LMS 3.1
|
CWLMS-3.1-300-SRK9
|
LMS 3.0 300 Device Restricted Upgrade to LMS 3.1
|
CWLMS-3.1-1.5KSRK9
|
LMS 3.0 1500 Device Restricted Upgrade to LMS 3.1
|
CWLMS-3.1-5K-SR-K9
|
LMS 3.0 5000 Device Restricted Upgrade to LMS 3.1
|
CWLMS-3.1-10K-SRK9
|
LMS 3.0 10000 Device Restricted Upgrade to LMS 3.1
|
If you have LMS 3.0 license without Software Application Support (SAS) contracts, you can order LMS 3.1 from www.cisco.com. The SKUs that need to be used while ordering are:.
Licenses (SKU) to upgrade from LMS 3.0
|
Permitted number of Devices
|
CWLMS-3.1-100MR-K9
|
LMS 3.0 100 Device Restricted Upgrade to LMS 3.1
|
CWLMS-3.1-300MR-K9
|
LMS 3.0 300 Device Restricted Upgrade to LMS 3.1
|
CWLMS-3.1-1.5KMRK9
|
LMS 3.0 1500 Device Restricted Upgrade to LMS 3.1
|
CWLMS-3.1-5KMR-K9
|
LMS 3.0 5000 Device Restricted Upgrade to LMS 3.1
|
CWLMS-3.1-10KMR-K9
|
LMS 3.0 10000 Device Restricted Upgrade to LMS 3.1
|
To upgrade from LMS 2.5.x, LMS 2.6, you can order LMS 3.1 through Cisco Sales channels. The SKUs that need to be used while ordering are:
Licenses (SKU) to upgrade from LMS, LMS 2.6
|
Permitted number of Devices
|
CWLMS-3.1-300UPK9
|
LMS 3.1 300 Device Restricted Upgrade for LMS 2.5.x, 2.6
|
CWLMS-3.1-1.5KUPK9
|
LMS 3.1 1500 Device Restricted Upgrade for LMS 2.5.x, 2.6
|
CWLMS-3.1-5KUPK9
|
LMS 3.1 5000 Device Restricted Upgrade for LMS 2.5.x, 2.6
|
CWLMS-3.1-10KUPK9
|
LMS 3.1 10000 Device Restricted Upgrade for LMS 2.5.x, 2.6
|
See Application Scaling Numbers for further deployment related information.
Application Scaling Numbers
This section presents information on the specific scaling numbers for each of the CiscoWorks LMS applications in both Standalone server as well as in a Solution server:
•
Standalone Server
•
Solution Server
•
Concurrent Users Supported
Standalone Server
The application scaling numbers on a Standalone Server are:
•
Common Services Device and Credential Repository (DCR)—Maximum of 50,000 devices and 100 user-defined groups.
•
Resource Manager Essentials (RME)—10,000 devices and 100 user-defined groups.
•
Campus Manager—5,000 devices, 250,000 end hosts and IP Phones, and 100 user-defined groups.
Campus Manager Data Collection discovers and tracks a maximum of 150,000 Switch Ports.
•
Device Fault Manager (DFM)—5,000 devices with a maximum of 80,000 ports or interfaces of which upto 15 percent can be in managed state. It also supports 100 user-defined groups.
•
Internetwork Performance Monitor (IPM)—5,000 devices with a maximum of 5,000 collectors.
•
Health and Utilization Monitor (HUM)
–
50 devices with a maximum of 30,000 MIB objects
–
300 devices with a maximum of 30,000 MIB objects
–
1000 devices with a maximum of 100,000 MIB objects
Solution Server
LMS 3.1 now supports up to 5,000 devices for all applications that are installed in a single Solution server, except HUM. This includes 150,000 end-hosts in Campus Manager and 1,200 collectors in IPM.
To manage 5,000 devices for all applications including HUM, you must set up:
•
HUM on a Standalone server (with only CS, Portal, CiscoWorks Assistant, and HUM installed), which manages 1000 devices.
•
All other CiscoWorks applications on another server
For HUM, the scaling numbers are:
•
All applications installed in a single server with 300 device SKU—15,000 MIB objects.
•
All applications installed in a single server with 1500 device SKU—50,000 MIB objects.
Concurrent Users Supported
LMS 3.1 can support:
•
3 concurrent users for LMS 100 and LMS 300 License types.
•
20 concurrent users for LMS 1,500, LMS 5,000 and LMS 10,000 License types.
Multiple number of simultaneous users can affect system performance. 20 concurrent users is the maximum recommended number. However, this depends on the size and configuration of the server.
Licensing Your Product
The LMS 3.1 product provides features such as software-based product registration and license key activation technologies. While installing CiscoWorks, the installer displays the Registration and Licensing input dialog box.
Understanding Product Authorization Key
The Product Authorization Key (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 3.1.
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.
You must enter the license file according to the one you have purchased with the LMS 3.1 product. See License Information to furnish the appropriate license file.
If you have not purchased a license with the product, and if you have only an Evaluation copy, you can select the Evaluation mode and proceed with using the LMS 3.1 product.
Figure 3-1 displays the licensing screen for LMS Applications on Windows operating system.
Figure 3-1 Licensing Screen for LMS Applications
The LMS installation program prompts you to enter either the license file or select the Evaluation Only option (see Figure 3-1).
Figure 3-2 displays the licensing screen for HUM on Windows operating system.
Figure 3-2 Licensing Screen for HUM
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 3-1).
If you choose to run LMS in the evaluation mode, it is valid for only 90 days and does not support any upgrades and allows support for only 100 devices. It stops functioning after 90 days. The evaluation period cannot be extended.
If you have not purchased the product, the LMS evaluation server can be reactivated by purchasing LMS from your authorized Cisco reseller and you can register the product. For details, see Installing the Licensing File.
The behavior of HUM in evaluation mode will be the same as explained above.
NFR (Not For Resale) License
NFR (Not For Resale) License is a default license that is valid for only 365 days. It allows you to manage up to 100 devices.
To install a NFR copy of CiscoWorks applications, you must apply the NFR license either during the installation or after the installation using the graphical user interface.
To apply the NFR license during the installation, you must:
Step 1
Select the License File location option in the Licensing Information page of LMS 3.1 during the installation. See Figure 3-1.
See Performing Installation of LAN Management Solution 3.1 for detailed instructions on installing the product.
Step 2
Enter the LMS 3.1 NFR license file location, or click Browse to locate the NFR license file.
Step 3
Click OK.
After specifying the NFR License file for LMS 3.1, the Licensing Information dialog box appears for HUM, if you have selected HUM earlier in the list of applications to be installed. See Figure 3-2.
Step 4
Enter the HUM NFR license file location, or click Browse to locate the NFR license file.
Step 5
Click OK.
The System Requirements dialog box appears.
The installation program calculates the minimum disk space, RAM and SWAP space required to install the product.
The required RAM space to install NFR license of the product is 4 GB (4096 MB). The following warning message appears if the RAM space is lesser than 8 GB:
The available RAM is X MB which is lesser than the required RAM of 8192 MB which may affect the performance. Click Yes to proceed or No to abort.
X in the warning message denotes the available RAM space.
You can ignore this warning message and c ontinue the installation if the RAM space on your server is more than 4 GB.
You can also apply NFR license after the installation is completed.
To apply the NFR license after the installation is completed, you must select the Evaluation Only option in the Licensing Information page while the installation is progressing. See Figure 3-1 and Figure 3-2.
After the installation is completed, you should:
Step 1
Launch CiscoWorks.
Step 2
Go to the CiscoWorks home page and select Common Services > Server > Admin > Licensing.
The License Administration page appears.
Step 3
Click Update.
Step 4
Enter the path to the NFR license file in the License field, or click Browse to locate the NFR license file.
Step 5
Click OK to apply the license.
Installing the Licensing File
We recommend that before installing the LMS 3.1 product, you register the product and receive a permanent license.
To license your product, you must:
Step 1
Register the LMS product with Cisco.com using the PAK to get your license file. 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. After successful registration, you will receive your license file information through an email.
Step 2
After you install LMS 3.1, copy this new license file to the CiscoWorks Common Services server into a directory with read permissions for the user name casuser in the user group casusers.
Step 3
Install the license file.
If you have obtained the LMS license before installation:
a.
Select the first LMS applications you wish to install and when prompted:
–
On Windows, select the first radio button (see Figure 3-1) and use the browse window to locate the license file directory.
–
On Solaris, select L for License File after you accept the Licensing Agreement and continue installing the application.
b.
Click Next to install the license file.
After you have completed the LMS install by entering the appropriate license file, if you want to convert an evaluation copy to a licensed copy, perform the following:
a.
Go to the CiscoWorks home page and select Common Services > Server > Admin > Licensing.
The License Administration page appears.
b.
Click Update.
A file browser popup dialog box appears.
c.
Enter the path to the new license file in the License field, or click Browse to locate the license file that you copied to the server in Step 2.
d.
Click OK.
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.
Note
The License file obtained is platform independent and hence can be used in both Windows as well as Solaris operating systems.