Professional Documents
Culture Documents
Americas Headquarters
Cisco Systems, Inc.
170 West Tasman Drive
San Jose, CA 95134-1706
USA
http://www.cisco.com
Tel: 408 526-4000
800 553-NETS (6387)
Fax: 408 527-0883
THE SPECIFICATIONS AND INFORMATION REGARDING THE PRODUCTS IN THIS MANUAL ARE SUBJECT TO CHANGE WITHOUT NOTICE. ALL
STATEMENTS, INFORMATION, AND RECOMMENDATIONS IN THIS MANUAL ARE BELIEVED TO BE ACCURATE BUT ARE PRESENTED WITHOUT
WARRANTY OF ANY KIND, EXPRESS OR IMPLIED. USERS MUST TAKE FULL RESPONSIBILITY FOR THEIR APPLICATION OF ANY PRODUCTS.
THE SOFTWARE LICENSE AND LIMITED WARRANTY FOR THE ACCOMPANYING PRODUCT ARE SET FORTH IN THE INFORMATION PACKET THAT
SHIPPED WITH THE PRODUCT AND ARE INCORPORATED HEREIN BY THIS REFERENCE. IF YOU ARE UNABLE TO LOCATE THE SOFTWARE LICENSE
OR LIMITED WARRANTY, CONTACT YOUR CISCO REPRESENTATIVE FOR A COPY.
The Cisco implementation of TCP header compression is an adaptation of a program developed by the University of California, Berkeley (UCB) as part of UCBs public
domain version of the UNIX operating system. All rights reserved. Copyright 1981, Regents of the University of California.
NOTWITHSTANDING ANY OTHER WARRANTY HEREIN, ALL DOCUMENT FILES AND SOFTWARE OF THESE SUPPLIERS ARE PROVIDED AS IS WITH
ALL FAULTS. CISCO AND THE ABOVE-NAMED SUPPLIERS DISCLAIM ALL WARRANTIES, EXPRESSED OR IMPLIED, INCLUDING, WITHOUT
LIMITATION, THOSE OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT OR ARISING FROM A COURSE OF
DEALING, USAGE, OR TRADE PRACTICE.
IN NO EVENT SHALL CISCO OR ITS SUPPLIERS BE LIABLE FOR ANY INDIRECT, SPECIAL, CONSEQUENTIAL, OR INCIDENTAL DAMAGES, INCLUDING,
WITHOUT LIMITATION, LOST PROFITS OR LOSS OR DAMAGE TO DATA ARISING OUT OF THE USE OR INABILITY TO USE THIS MANUAL, EVEN IF CISCO
OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.
Cisco and the Cisco logo are trademarks or registered trademarks of Cisco and/or its affiliates in the U.S. and other countries. To view a list of Cisco trademarks, go to this
URL: www.cisco.com/go/trademarks. Third-party trademarks mentioned 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. (1110R)
Any Internet Protocol (IP) addresses used in this document are not intended to be actual addresses. Any examples, command display output, and figures included in the
document are shown for illustrative purposes only. Any use of actual IP addresses in illustrative content is unintentional and coincidental.
Installing and Migrating to Cisco Prime LAN Management Solution 4.2
Copyright 1998-2012 Cisco Systems, Inc. All rights reserved.
C O N T E N T S
Notices
xi
i-xi
xv
Audience
i-xv
Document Conventions
i-xvi
Product Documentation
i-xvii
CHAPTER
i-xix
i-xxi
1-1
1-1
1-12
iii
Contents
1-15
CHAPTER
Prerequisites
1-16
1-19
2-1
2-18
2-20
2-25
CHAPTER
2-16
2-26
3-1
3-1
iv
OL-25957-01
Contents
3-5
3-9
CHAPTER
Setting Up Cisco Prime LMS in High Availability and Disaster Recovery Environment
High Availability and Disaster Recovery- An Overview
Veritas Components for Setting Up High Availability
Licensing Information
4-1
4-1
4-3
4-4
4-4
4-22
Contents
CHAPTER
4-35
Setting Up Cisco Prime LMS for High Availability, Live Migration, and Storage VMotion Using
VMware 5-1
Overview of VMware High Availability 5-1
VMware vSphere Components for Setting Up High Availability
Prerequisites for Implementing High Availability 5-2
Setting up High Availability using VMware HA 5-4
Creating a VMware HA Cluster 5-4
5-2
vi
OL-25957-01
Contents
CHAPTER
5-12
6-1
6-45
6-49
6-49
vii
Contents
CHAPTER
6-52
7-1
7-1
7-19
CHAPTER
8-1
8-1
8-1
8-2
8-4
8-4
8-18
viii
OL-25957-01
Contents
Network Topology, Layer 2 Services and User Tracking Data Migration Errors
Fault Management Data Migration Errors 8-21
IPSLA Performance Management Data Migration Errors 8-22
Device Performance Management Data Migration Errors 8-23
Frequently Asked Questions
APPENDIX
8-19
8-24
A-1
APPENDIX
A-7
B-1
Understanding UTU
B-2
B-2
B-3
B-5
B-6
APPENDIX
B-8
B-13
B-14
B-14
B-14
C-1
C-2
C-4
ix
Contents
C-8
D-1
APPENDIX
APPENDIX
E-1
APPENDIX
F-1
INDEX
OL-25957-01
Notices
The following notices pertain to this software license.
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:
Redistributions of source code must retain the copyright notice, this list of conditions and the
following disclaimer.
2.
Redistributions in binary form must reproduce the above copyright notice, this list of conditions,
and the following disclaimer in the documentation and/or other materials provided with the
distribution.
3.
All advertising materials mentioning features or use of this software must display the following
acknowledgment: This product includes software developed by the OpenSSL Project for use in the
OpenSSL Toolkit (http://www.openssl.org/).
4.
The names OpenSSL Toolkit and OpenSSL Project must not be used to endorse or promote
products derived from this software without prior written permission. For written permission, please
contact openssl-core@openssl.org.
5.
Products derived from this software may not be called OpenSSL nor may OpenSSL appear in
their names without prior written permission of the OpenSSL Project.
xi
Notices
6.
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:
Redistributions of source code must retain the copyright notice, this list of conditions and the
following disclaimer.
2.
Redistributions in binary form must reproduce the above copyright notice, this list of conditions and
the following disclaimer in the documentation and/or other materials provided with the distribution.
3.
All advertising materials mentioning features or use of this software must display the following
acknowledgement:
This product includes cryptographic software written by Eric Young (eay@cryptsoft.com).
The word cryptographic can be left out if the routines from the library being used are not
cryptography-related.
4.
If you include any Windows specific code (or a derivative thereof) from the apps directory
(application code) you must include an acknowledgement: This product includes software written
by Tim Hudson (tjh@cryptsoft.com).
xii
OL-25957-01
Notices
xiii
Notices
xiv
OL-25957-01
Preface
This guide helps you to install the Cisco Prime LAN Management Solution 4.2 software on both
Windows, Solaris, and Soft Appliance.
This guide also provides information on data migration from earlier versions of LMS to LMS 4.2. In
addition, the guide provides troubleshooting suggestions that may be useful while you work on LMS.
Note
The term Virtual Appliance or Soft Appliance is used throughout LMS documentation, including Online
Help.
This preface details the product documents available for LMS, and demonstrates the styles and
conventions used in this guide. This preface contains:
Audience
Document Conventions
Product Documentation
Audience
This guide is for anyone who installs, upgrades, configures, verifies, and uses LMS software. Network
administrators or operators should have the following skills:
xv
Preface
Document Conventions
Document Conventions
Table 1 describes the conventions followed in this guide.
Table 1
Note
Caution
Conventions Used
Item
Convention
boldface font
italic font
screen
boldface screen
italic screen
boldface font
font
font
font
Means reader take note. Notes contain helpful suggestions or references to material not covered in the
publication.
Means reader be careful. In this situation, you might do something that could result in equipment
damage or loss of data.
xvi
OL-25957-01
Preface
Product Documentation
Product Documentation
Note
We sometimes update the printed and electronic documentation after original publication. Therefore,
you should also review the documentation on Cisco.com for the latest updates.
Table 2 describes the product documentation that is available.
Table 2
Product Documentation
Document Title
Available Formats
On Cisco.com at:
http://www.cisco.com/en/US/docs/net_mgmt/
ciscoworks_lan_management_solution/4.2/install
/guide/install.html
On Cisco.com at:
http://www.cisco.com/en/US/docs/net_mgmt/
ciscoworks_lan_management_solution/4.2/user/
guide/getting_started/lms42_getstart_guide.html
On Cisco.com at:
http://www.cisco.com/en/US/docs/net_mgmt/
ciscoworks_lan_management_solution/4.2/user/
guide/configuration/config.html
On Cisco.com at:
http://www.cisco.com/en/US/docs/net_mgmt/cisc
oworks_lan_management_solution/4.2/user/guide
/lms_monitor/lms_mnt.html
On Cisco.com at:
http://www.cisco.com/en/US/docs/net_mgmt/
ciscoworks_lan_management_solution/4.2/user/
guide/admin/admin.html
xvii
Preface
Product Documentation
Table 2
Document Title
Technology Work Centers in Cisco Prime
LAN Management Solution 4.2
Available Formats
On Cisco.com at:
http://www.cisco.com/en/US/docs/net_mgmt/
ciscoworks_lan_management_solution/4.2/user/
guide/workcenters/wcug.html
On Cisco.com at:
http://www.cisco.com/en/US/docs/net_mgmt/
ciscoworks_lan_management_solution/4.2/user/
guide/reports/lms41_reports_guide.html
On Cisco.com at:
http://www.cisco.com/en/US/docs/net_mgmt/
ciscoworks_lan_management_solution/4.2/user/
guide/inventory/inventory.html
On Cisco.com at:
http://www.cisco.com/en/US/docs/net_mgmt/cisc
oworks_lan_management_solution/4.2/navigation
/Guide/lms42_nav_guide.html
On Cisco.com at:
http://www.cisco.com/en/US/docs/net_mgmt/cisc
oworks_lan_management_solution/4.2/database_
schema/dbviews_42.html
On Cisco.com at:
http://www.cisco.com/en/US/docs/net_mgmt/
ciscoworks_lan_management_solution/4.2/
release/notes/lms41rel.html
xviii
OL-25957-01
Preface
Related Documentation for CiscoWorks LAN Management Solution 4.0
Table 2
Document Title
Available Formats
On Cisco.com at:
http://www.cisco.com/en/US/docs/net_mgmt/
ciscoworks_lan_management_solution/4.2/
device_support/table/lms41sdt.html
We sometimes update the printed and electronic documentation after original publication. Therefore,
you should also review the documentation on Cisco.com for any updates.
Table 3 describes the additional documentation that is available.
Table 3
Related Documentation
Document Title
User Guide for CiscoWorks
Common Services 3.3
Available Formats
PDF on:
Product DVD
LMS 3.2 Documentation DVD
On Cisco.com at:
http://www.cisco.com/en/US/docs/net_mgmt/ciscoworks_co
mmon_services_software/3.3/user/guide/cs_33_ug.html
PDF on:
Product DVD
LMS 3.2 Documentation DVD
On Cisco.com at:
http://www.cisco.com/en/US/docs/net_mgmt/ciscoworks_ca
mpus_manager/5.2/user/guide_pb/CampusHelp.html
PDF on:
Product DVD
LMS 3.2 Documentation DVD
On Cisco.com at:
http://www.cisco.com/en/US/docs/net_mgmt/ciscoworks_re
source_manager_essentials/4.3/user/guide/rme_ug.html
xix
Preface
Related Documentation for CiscoWorks LAN Management Solution 4.0
Table 3
Document Title
User Guide for Device Fault
Manager 3.2 (With LMS 3.2)
Available Formats
PDF on:
Product DVD
LMS 3.2 Documentation DVD
On Cisco.com at:
http://www.cisco.com/en/US/docs/net_mgmt/ciscoworks_de
vice_fault_manager/3.2/user/guide/dfm32ug_Book.html
PDF on:
Product DVD
LMS 3.2 Documentation DVD
On Cisco.com at:
http://www.cisco.com/en/US/docs/net_mgmt/ciscoworks_in
ternetwork_performance_monitor/4.2/user/guide/IPM4_2ug
.html
PDF on:
Product DVD
LMS 3.2 Documentation DVD
On Cisco.com at:
http://www.cisco.com/en/US/docs/net_mgmt/ciscoworks_ci
scoview/6.1.9/user/userguide/ugcv_619.html
PDF on:
Product DVD
LMS 3.2 Documentation DVD
On Cisco.com at:
http://www.cisco.com/en/US/docs/net_mgmt/ciscoworks_l
ms_portal/1.2/user/guide/LMSPortal_1.2.html
PDF on:
Product DVD
LMS 3.2 Documentation DVD
On Cisco.com at:
http://www.cisco.com/en/US/docs/net_mgmt/ciscoworks_as
sistant/1.2/user/guide/cwa12.html
xx
OL-25957-01
Preface
Obtaining Documentation, Obtaining Support, and Security Guidelines
Table 3
Document Title
User Guide for Health and
Utilization Monitor 1.2
Available Formats
PDF on:
Product DVD
LMS 3.2 Documentation DVD
On Cisco.com at:
http://www.cisco.com/en/US/docs/net_mgmt/ciscoworks_he
alth_and_utilization_monitor/1.2/user/guide_12/HUMug.ht
ml
PDF on:
Product DVD
LMS 3.2 Documentation DVD
On Cisco.com at:
http://www.cisco.com/en/US/docs/net_mgmt/ciscoworks_co
mmon_services_software/3.1/user/nmim/guide/nmimug.htm
l
xxi
Preface
Obtaining Documentation, Obtaining Support, and Security Guidelines
xxii
OL-25957-01
CH A P T E R
Product Overview
Supported Devices
Product Overview
LMS 4.2 provides powerful features that enable you to configure, monitor, troubleshoot, and administer Cisco
networks. It also supports new Cisco technologies such as Identity, EnergyWise, Auto Smartports, Medianet,
and Smart Install.
This document describes procedures for new and upgrade installation of LMS 4.2. It contains:
LMS functionalities.
LMS features.
Information about ordering documentation and contacting Cisco Systems for additional assistance.
If you already have an earlier version of LMS and want to migrate to LMS 4.2, see Migrating Data to
Cisco Prime LAN Management Solution 4.2.
1-1
Chapter 1
The licenses in LMS 4.2 are based on number of devices and you can manage the following
functionalities for the devices:
Configuration Management (This function is enabled by default. You cannot select or unselect this
function)
Fault Management
Note
We recommend you not to install any other product in LMS server. If LMS 4.2 and Antivirus softwares
like MCAfee, Norton and so on, are installed in the same machine, the Antivirus should be configured
to exclude the NMSROOT (LMS installation directory) from scanning. This is required because the third
party software such as Sybase, included in LMS do disk intensive operations and spawn child processes
based on the load. If the Antivirus is enabled this may not function as expected or may cause degradation
in the overall performance of LMS.
Note
Daemon Manager will start slowly during reboot. This is because the antivirus that starts during reboot
will cause delay to initiate Cisco Prime processes. If there are any Daemon Manager issues during
reboot, then you should either disable the antivirus or restart the Daemon Manager after reboot.
This section contains the following topics on Upgrade:
Note
LMS 4.2 supports local upgrade or direct inline upgrade only from LMS 4.1 and LMS 4.0.1.
1-2
OL-25957-01
Chapter 1
Remote upgradeInstalling LMS on a different machine and then restoring the data on that
machine.
You can do a remote upgrade to LMS 4.2 from LMS 4.1, LMS 4.0.1, and LMS 3.2 SP1. For earlier
versions of LMS, refer Table 1-2.
1-3
Chapter 1
Table 1-1
LMS Master
After restoring the LMS 3.2 SP1/4.0.1/4.1
backed up data in LMS 4.2, the DCR
mode will be moved from Standalone to
Master
LMS Slave
DCR Changes
No Changes
Device
Management/Allocation
changes
Grouping Services
Changes
1-4
OL-25957-01
Chapter 1
Table 1-2 describes the recommended sequence to upgrade, and migrate your data from earlier versions
of LMS to LMS 4.2.
Table 1-2
Type of Upgrade
LMS 4.1
Remote migration
Procedure
1.
2.
3.
1.
LMS 4.0.1
Remote migration
1.
2.
3.
1.
Remote migration
1.
Back up the data in the old machine having LMS 3.2 SP1.
2.
3.
1-5
Chapter 1
Table 1-2
Type of Upgrade
Procedure
1.
2.
3.
4.
Remote migration
1.
2.
2.6
3.
4.
5.
1-6
OL-25957-01
Chapter 1
Note
Standard Discovery
CAAM Features
Enhancement in TrustSec
EnergyWise Enhancement
The supported screen resolution for LMS 4.2 is 1024x768 pixels. We recommend you not to use browser
zoom in and zoom out features in LMS 4.2.
1-7
Chapter 1
Standard Discovery
Standard Discovery allows you to discovery devices with minimum settings.
For configuring Standard Discovery, you need to provide the input for Seed Devices and SNMP
Credentials.
1-8
OL-25957-01
Chapter 1
Using Seed devices from DCR, it will not show the count of devices in DCR
For more information, see Inventory Management with Cisco Prime LAN Management Solution 4.2.
CAAM Features
LMS 4.2 supports the following Compliance and Audit Manager (CAAM) features:
Import Contracts
CAAM Reports
1-9
Chapter 1
Import Contracts
This feature enables you to import customer contracts into the CAAM Database.
For more information, see Compliance and Audit Settings in Administration of Cisco Prime LAN
Management Solution 4.2.
CAAM Reports
CAAM reports provide compliance status of the network, lifecycle and contract information about
network devices, security advisory, and service reports based on device and software capabilities, and
the services that are enabled.
1-10
OL-25957-01
Chapter 1
Using CAAM, the following reports can be generated and viewed in the reports job browser:
Service Reports
Compliance Reports
For more information, see Compliance and Audit in Reports Management with Cisco Prime LAN
Management Solution 4.2.
Service Reports
Service reports provide information about the status of all the services on network nodes. These reports
also include a Capability Report section that provides information on what a user needs to do like
upgrading the software or hardware for supporting a given service.
Life Cycle Management Reports
Life Cycle Management Reports provide information about the lifecycle state of the network. This report
includes End of Life and Contract Management Reports.
Compliance Reports
The Compliance Reports provide information about the compliance state of the network for specific
compliance requirements.
Compliance Reports include the following device reports:
CIS Benchmarks
1-11
Chapter 1
1-12
OL-25957-01
Chapter 1
Inventory Group
Attribute
Bridge
Container
Interface
interface index
Memory pool
Module
Slot Number
Port
Port Index
Port Description
Port Vendor Type
System
Management Type
OSI Layer Services
For more information, see Creating an Inventory Custom Report Template in Reports Management with
Cisco Prime LAN Management Solution 4.2.
Enhancement in TrustSec
Till LMS 4.1, Identity was a seperate feature. In LMS 4.2, Identity, which is now called as 802.1x, and
Secured Group Access Configuration (SXP, SGT, and SGACL) are grouped under a common feature
called TrustSec.
TrustSec Version
When you launch the Getting Started/Readiness Assessment page from Work Centers > TrustSec >
Getting Started/Readiness Assessment for the first time, you will be guided to select the TrustSec
version (TrustSec 1.99 and TrustSec 2.0) inorder to list the TrustSec-capable devices. By default
TrustSec 2.0 is selected.
TrustSec Limited Compatibility Devices
In the TrustSec Getting Started/Readiness Assessment page, the pie chart is enhanced with TrustSec
Limited Compatibility Devices. If devices are running with minimum supported image version for the
selected TrustSec version and if the devices are not having the required modules installed then those
devices will be known as TrustSec Limited Compatibility devices.
For more information, see TrustSec Readiness Assessment in Technology Work Centers in Cisco Prime
LAN Management Solution 4.2.
1-13
Chapter 1
Secured Group Access Configuration cross-launches the Template Center page, where you can select the
template and deploy configuration.
This can be done in two ways:
Go to Work Centers > TrustSec > Getting Started or Readiness Assessment, select the devices
from the TrustSec-capable devices pie or TrustSec Limited Compatibility pie and click SXP, SGT,
or SGACL Configure options.
or
Go to Work Centers > TrustSec > Secured Group Access Configuration select the devices and
click SXP, SGT, or SGACL Configure options.
For more information, see Secured Group Access Configuration in Technology Work Centers in Cisco
Prime LAN Management Solution 4.2.
EnergyWise Enhancement
In the EnergyWise Policy Override portlet,Wake the host option is newly added.
In the Current Power Consumption portlet, a new field Category has been added.
In the Work Center > EnergyWise > Configure > Manage Endpoint Groups flow, a new field
Category has been added.
For more information, see Technology Work Centers in Cisco Prime LAN Management Solution 4.2.
1-14
OL-25957-01
Chapter 1
Support for Windows 2008 Standard Edition and Enterprise Edition on server and client systems
Support for Windows 2008 R2 Standard Edition and Enterprise Edition on server and client systems
Normal Backup - Process by which all the configuration files and collected data can be backed up
from application database.
Selective Backup - Process by which only required system configurations and data can be backed up.
LMS 4.1
LMS 4.0.1
For the following versions, you must migrate to LMS 3.2 SP1, and then install LMS 4.2:
LMS 3.1
LMS 3.0
LMS 2.6
1-15
Chapter 1
Note
LMS 3.2 and earlier versions allow you to install partial applications in one server. For example, you can
install CS and RME (part of earlier LMS versions) in one server and other LMS applications in another
server. In this scenario you can perform data migration only from one server. You can migrate data either
from RME server or from another LMS server. If the migration is performed from both the servers, then
the last run migration will overwrite the previously migrated data.
See Migrating Data to Cisco Prime LAN Management Solution 4.2 for more details on data migration.
Note
HPOV or NetView adapters are not supported for the Fault Management functionality in LMS 4.2
See Importing From Remote NMS in the Inventory Management Online Help for information about
importing devices from third party NMS.
Network Management Integration Data Bundle (NMIDB) 1.0.089 is shipped with LMS 4.2.
Note
From HPOV 9.x onwards the integration utility is moved to HPOV software.
For more information about HP NNMi and Cisco Prime LMS Integration,
refer the User Guide for Integration Utility 1.11 on Cisco.com.
1-16
OL-25957-01
Chapter 1
Table 1-3
Supported Platforms
Windows
Windows 2008 R2 Standard x 64 Edition
Note
Solaris
Solaris 10
1-17
Chapter 1
Table 1-3
Supported Platforms
Windows:
Windows 2008 Server Standard Edition Release 1
with SP1 and SP2
Note
Solaris
Solaris 10
Note
1-18
OL-25957-01
Chapter 1
Supported Devices
As additional device packages become available, you can download the Service Packs (formerly called
IDUs) that contain them from Cisco.com.
Registered Cisco.com users can access the latest Device Package Updates, and download the latest
device updates for CiscoView, Topology Device Package Updates, Fault Management Device Package
Updates and Inventory Config And Image Management Device Package Updates from:
http://www.cisco.com/cisco/software/type.html?mdfid=283434800&flowid=19062
See the following documentation to know more information about supported devices:
Supported Devices Table for Cisco Prime LAN Management Solution 4.2
http://www.cisco.com/en/US/docs/net_mgmt/ciscoworks_lan_management_solution/4.2/
device_support/table/lms42sdt.html
To see the list of installed applications device packages, select Admin > System > Software Center >
Device Update from the LMS menu.
To download Device Package Updates:
Step 1
Go to http://www.cisco.com/cisco/software/type.html?mdfid=283434800&flowid=19062
You must be a registered Cisco.com user to access this Software Download site. The site prompts you to
enter your Cisco.com username and password in the login screen, if you have not logged in already.
Step 2
Step 3
Select Routing and Switching Management > Cisco Prime LAN Management Solution.
Step 4
Step 5
Select the required feature specific update from the product tree.
Step 6
Select the required device package updates from the product software type.
Step 7
Step 8
Locate the device package update files which you want to download.
Step 9
Click the Download Now button to download and save the device package file to any local directory on
LMS Server.
See the Supported Devices Tables for LMS 4.2 for more information about supported devices:
http://www.cisco.com/en/US/docs/net_mgmt/ciscoworks_lan_management_solution/4.2/
device_support/table/lms42sdt.html
1-19
Chapter 1
Supported Devices
1-20
OL-25957-01
CH A P T E R
Prerequisites
This chapter describes the factors that you must consider before installing LMS 4.2 on Soft Appliance,
Windows and Solaris systems.
Before you install LMS 4.2, ensure that:
The server and client systems have the recommended hardware and software requirements.
You have disabled Terminal Services on the Windows operating system in the Application mode.
If you have enabled Terminal Server in Application mode, disable the Terminal Server, reboot the
system, and start the installation again.
However, you can enable Terminal Services in remote Administration mode.
You upgrade RSC to RSC 5.2, if you have configured Remote Syslog Collector (RSC) on a different
server. See Installing the Remote Syslog Collector for further information.
You have disabled the virus scanner on your system during the installation.
You have configured the recommended swap space. See System and Browser Requirements for
Server and Client for more information.
For Windows and Solaris, after you uninstall earlier versions of LMS like LMS 3.2, you must
remove the LMS logo manually if it is not removed during uninstallation.
You have local administrator privileges. Only a user with local administrator can install or uninstall
the product.
Solaris Patches
Important URLs
2-1
Chapter 2
Prerequisites
60 GB free disk space for LMS 4.2 application and data, in the LMS installation directory for:
LMS 50 , LMS 100 , LMS 300, LMS 750, LMS 1,500 and LMS 2,500 device license types
120 GB free disk space for LMS 4.2 application and data, in the LMS installation directory for:
LMS 5,000 and LMS 10,000 device license types
The disk space required to install LMS 4.2 on LMS Soft Appliance is 256 GB for all SKUs.
The hardware requirements vary based on the type of device restricted license you use.
Table 2-2 lists the software and hardware requirements for LMS Soft Appliance (OVA image).
Table 2-3 lists the hardware requirements of the NCS appliance for Soft Appliance (ISO image).
Table 2-4 lists the server requirements for installing LMS 4.2 software on Solaris systems for
different device SKUs.
Table 2-5 lists the recommended server requirements for installing LMS 4.2 software on Solaris
systems for Incremental Licenses.
Table 2-6 lists the server requirements for installing LMS 4.2 on Windows systems for different
device SKUs.
Table 2-7 lists the recommended server requirements for installing LMS 4.2 on Windows systems
for Incremental Licenses.
Table 2-9 lists the client system requirements for all platforms.
If you are running additional Cisco or third-party applications on the servers, the requirements might be
higher.
See Licensing Your Product for details on Licensing and the SKU details.
Note
LMS 4.2 is not supported on Windows 2000, Windows 2003, Solaris 8 and Solaris 9 servers.
2-2
OL-25957-01
Chapter 2
Prerequisites
System and Browser Requirements for Server and Client
Operating
System
Requirements
Solaris
Solaris Zones (Supported from Solaris 10) is a virtualization technology from Oracle
(for more details, go to the Oracle website). It allows you to create isolated and secure
environments called zones for running applications.
LMS 4.2 is installed on global zone of Solaris 10 Operating System by default.
LMS 4.2 also supports installing LMS in whole-root non-global zone.
Sparse root zone is not supported.
There is no specific hardware or software requirement for zone support. LMS works in
the same way in non-global zones, as it works on global zone.
LMS 4.2 also supports Logical domains (LDoms) and ZFS file system.
See Solaris Patches for more information on Solaris patches to be installed on these
Operating Systems.
Windows
Note
Note
2-3
Chapter 2
Prerequisites
Note
Virtualization technologies like, VMWare and Hyper V virtualization systems are not supported in LMS
5000, and LMS 10000 Devices license, in Windows. VMWare Systems are supported in LMS 5000, and
LMS 10000 Devices license in Soft Appliance.
Configure the links (in this example, bge0 and bge1) with two different IP addresses in the same
network.
Step 2
Check if both the IP addresses are reachable and you are able to telnet to the IPs. Get one public IP
address in the same subnet.
2-4
OL-25957-01
Chapter 2
Prerequisites
System and Browser Requirements for Server and Client
Step 3
Step 4
Key is the number that identifies the aggregation. The lowest key number is 1. Zeroes are not
allowed as keys. The key can be of any value.
Step 5
Add the IP address (Public IP) and hostname in the /etc/host file.
Step 6
If you cannot ping the IP address, you can set aggregation LACP mode active to off.
dladm modify-aggr t
off 2 key
Check the statistics by using the following command in the link aggregated server:
dladm show-aggr
address
speed
duplex link
state
bge0
0:14:4f:90:1e:ba
1000Mbps
full
up
attached
bge1
0:14:4f:90:1e:bb
1000Mbps
full
up
attached
Note
Step 2
The state of the links should appear as attached in the output, else, the link aggregated server
will not work when the NIC fails.
2-5
Chapter 2
Prerequisites
Table 2-2 lists the Software and Hardware Requirements for LMS Soft Appliance (OVA image).
Table 2-2
Component
Virtualization Systems
Recommended Memory
Requirement
256 GB
Swap space
32 GB
Resource Memory
Configuration
Note
Recommended Requirement
When you use incremental licenses for the LMS Soft Appliance, you must ensure that you configure the
virtual CPUs mentioned in Table 2-2.
2-6
OL-25957-01
Chapter 2
Prerequisites
System and Browser Requirements for Server and Client
Note
You can change the recommended settings of RAM and CPU resources of LMS virtual appliance.
However, you cannot change the default disk size (256 GB) of the virtual appliance after deploying
OVA.
Table 2-3 lists the hardware requirements of the NCS appliance for Soft Appliance (ISO image).
Table 2-3
Note
Hardware Requirements of the NCS appliance for Soft Appliance (ISO image)
Component
Recommended Requirement
2.4 GHz
Number of processors
Processor model
Cache
12 MB
Chassis type
Rack (1U)
2 TB
The following UCS models are supported for installing ISO image:
Cisco UCS C-series rack-mount servers (C200-M1 or M2, C210-M1or M2, and C250-M1 or M2 and
Cisco UCS C460).
Table 2-3 explains the hardware requirements for the above-mentioned UCS servers.
2-7
Chapter 2
Prerequisites
Component
LMS 50
LMS 100
LMS 300 (Upgrade from previous version) 1 CPU with dual core or 2 CPU with single core 4 GB
RAM and 12 GB swap space, 60 GB free disk space, 64
dual stack OS
Recommended: 8 GB RAM and 16 GB swap space
LMS 500
LMS 750 (Upgrade from previous version) 2 CPUs with dual core or 4 CPU with single core 8 GB
RAM and 16 GB swap space, 60 GB free disk space, 64
bit OS
Recommended: 12 GB RAM and 24 GB swap space
LMS 1000
LMS 2500
LMS 5,000
Note
2-8
OL-25957-01
Chapter 2
Prerequisites
System and Browser Requirements for Server and Client
Table 2-4
Component
You need more than one servers to manage up to 10,000 devices for all functionalities in your network.
You must manage:
Note
Network Topology, Layer 2 Services and User Tracking, Fault Management, IPSLA Performance
Management, and Device Performance management Functionalities for upto 5,000 devices in
another server
Configuration and Image Management Functionalities for upto 10,000 devices in one server.
You must disable other functionalities in Config Server managing upto 10,000 devices.
2-9
Chapter 2
Prerequisites
Table 2-5
License
Note
UltraSPARC IV processor
UltraSPARC T1 processor
UltraSPARC T2 processor
SPARC64 VI processor
2-10
OL-25957-01
Chapter 2
Prerequisites
System and Browser Requirements for Server and Client
Component
LMS 50
LMS 100
LMS 300 (Upgrade from previous version) 1 CPU with dual core or 2 CPU with single core 4 GB
RAM and 12 GB swap space, 60 GB free disk space, 64
dual stack OS
Recommended: 8 GB RAM and 16 GB swap space
LMS 500
LMS 750 (Upgrade from previous version) 2 CPUs with dual core or 4 CPU with single core 8 GB
RAM and 16 GB swap space, 60 GB free disk space, 64
bit OS
Recommended: 12 GB RAM and 24 GB swap space
LMS 1000
LMS 2500
LMS 5,000
Note
2-11
Chapter 2
Prerequisites
Table 2-6
Component
You need more than one server to manage up to 10,000 devices for all functionalities in your network.
You must manage:
Note
Network Topology, Layer 2 Services and User Tracking, Fault Management, IPSLA Performance
Management, and Device Performance management Functionalities for upto 5,000 devices in
another server
Configuration and Image Management Functionalities for upto 10,000 devices in one server.
You must disable other functionalities in Config Server managing upto 10,000 devices.
Table 2-7
License
Note
If you want to configure swap space in a 64-bit Windows machine with greater than 4 GB space, create
more than one partition and split the swap space across the drives. For example, to archive 8 GB,
configure 4GB for C:\ and configure another 4GB for D:\
Table 2-8 lists the server requirements for installing the CiscoWorks LAN Management Solution 3.2
components on Windows systems with HUM.
2-12
OL-25957-01
Chapter 2
Prerequisites
System and Browser Requirements for Server and Client
Table 2-8
Component
HUM 50
HUM 300
HUM 1000
2-13
Chapter 2
Prerequisites
AMD processors
Note
AMD Athlon 64 X2
AMD -V
LMS 4.2 runs on VMware systems. See Operating System Requirements for a list of virtualization
systems supported.
The server requirements on VMware servers remains the same as the server requirements on Windows
systems.
However, the following hardware are optimized to run in virtualized environment:
Intel-VT processors
Intel vPro processor technology
Intel Xeon processor 5000 sequence
Intel Xeon processor 7000 sequence
Intel Xeon processor 3000 sequence
AMD-V
IBM X3550 M3
Intel Xeon Processor 5600 series
2-14
OL-25957-01
Chapter 2
Prerequisites
System and Browser Requirements for Server and Client
Component
Disk space
60 GB and above
Memory
Requirements
2 GB RAM
Hardware and
software
At least single CPU@ 2.4 GHZ or higher with one of the following operating
systems:
Browser
Requirements
Windows 2008 Standard and Enterprise with Service Pack 1 and Service Pack
2 (64 bit)
Windows 2008 R2 Standard and Enterprise with Service Pack 1 and Service
Pack 2 (64 bit)
Internet Explorer 8.0, 9.0 Standards Mode (Press F12 and select Standards
Mode)
Note
2-15
Chapter 2
Prerequisites
Table 2-9
To access LMS Topology Services, we recommend that you install Java Plug-in
version 1.6.0_24. If the client machine is installed with the JRE Update version
equal to or higher than the recommended version, then Topology Services will be
launched in the client machine.
Java Runtime
Environment
(JRE) Requirements
If the client machine is installed with more than one JRE Update version equal to or
higher than the recommended JRE version (1.6.0_24), the Topology Services will
be launched with the higher Update JRE version. To view the JRE versions installed,
go to Java Control Panel and click View button under Java tab.
For example, LMS 4.2 requires JRE 1.6.0_24 to launch Topology Services. If the
client machine is installed with an Update version higher than JRE 1.6.0_24, say
1.6.0_25, and user selects JRE 1.6.0_25, then Topology Services is launched with
JRE 1.6.0_25.
Adobe Flash
Player
You need Adobe Flash Player 9 or later to view some portlets and the Getting Started
pages in Work Center.
You can install the flash player from the portlet. You must reload the page after
installing the flash player.
Table 2-10
Features
Terminal Server
Remote access and virtual system. Each client has its own virtual
OS environment.
Remote Desktop Administration Remote access only. All clients use the same OS.
Step 2
2-16
OL-25957-01
Chapter 2
Prerequisites
Terminal Server Support for Windows Server
Step 3
Select the Allow connections from computer running any version if Remote Desktop option.
2-17
Chapter 2
Prerequisites
Solaris Patches
Go to Start > Settings > Control Panel > Administrative tools > Local Security Policy.
The Local Security Policy window appears.
Step 2
Step 3
Select System cryptography: Use FIPS compliant algorithms for encryption, hashing, and signing.
Step 4
Step 5
Step 6
Click Apply.
You must reboot the server for the changes to take effect.
Solaris Patches
LMS 4.2 is installed on global zone of Solaris 10 Operating System by default. Installation of LMS 4.2
in whole-root non-global zone in Solaris 10 is supported.
The Solaris system requires the following patches to be installed on the server:
Cluster Patches
2-18
OL-25957-01
Chapter 2
Prerequisites
Solaris Patches
Operating
System
Solaris 10
Solaris Patches
Use showrev
Note
-p
LMS was tested only with these patches. Later versions of these patches have not been tested since they
were not released when LMS was tested.
The table below lists the messages that appear during installation if you do not have the recommended
and required Solaris patches on the system.
If you do not have...
Message
We recommend you to download and install the latest required and recommended patches from
www.oracle.com before you run LMS 4.2.
2-19
Chapter 2
Prerequisites
Cluster Patches
You should also install the cluster patches recommended by ORACLE on Solaris 10 servers.
You can download the cluster patches from www.oracle.com. See the same website for the installation
instructions of Cluster patches.
The minimum recommended cluster patch levels on Solaris Systems are Solaris 10 Cluster patches
released on Apr/17/07 and Sep/16/09.
If you have not installed the cluster patches on Solaris 10 system, the following warning messages
appear to ensure you install the Cluster Patches required for Solaris 10:
WARNING: Ensure that you have installed the recommended Solaris 10 cluster patches
released on Apr/17/07, in this server.
WARNING: If these cluster patches are not installed, please download and install them
from http://www.sun.com/.
WARNING: Otherwise, some features of the LMS applications will not function properly.
Do you want to continue the installation ? (y/n) [y]:
All ports mentioned in the table have direction of establishment of connection is Client to Server.
Only then, the communication across servers or between the server and client can happen:
Port
Protocol Number
Service Name
TCP
TCP
TCP
49
25
22
Functionality
Common Services
Fault Management
Common Services,
Direction
(of Establishment)
of Connection
Server to ACS
Server to SMTP
Server
Server to Device
2-20
OL-25957-01
Chapter 2
Prerequisites
LMS 4.2 Port Usage
Port
Protocol Number
Service Name
TCP
Telnet
UDP
UDP
23
69
161
Functionality
Common Services
Common Services
Server to Device
Device to Server
Simple Network
Management Protocol
(SNMP)
Common Services
Server to Device
CiscoView
Device to Server
Fault Management
IPSLA Performance
Management
Device Performance
Management
TCP
514
Common Services
UDP
162
Fault Management
Common Services
UDP
514
Direction
(of Establishment)
of Connection
Syslog
Server to Device
Server to Device
Device to Server
Device to Server
UDP
14311
Device to Server
UDP
9000
Fault Management
Device to Server
UDP
162362
UT Host acquisition
TCP
443
Common Services
Client to Server
Server Internal
2-21
Chapter 2
Prerequisites
Port
Protocol Number
Service Name
TCP
1741
Functionality
Common Services
CiscoView
Fault Management
IPSLA Performance
Management
Direction
(of Establishment)
of Connection
Client to Server
TCP
42342
OSAGENT
Common Services
Client to Server
TCP
42352
ESS HTTP
(Alternate port is
44352/tcp)
Common Services
Client to Server
TCP
1099
Common Services
Server Internal
TCP
8898
Log Server
Fault Management
Server Internal
TCP
9002
Fault Management
Server Internal
TCP
9007
Tomcat shutdown
Common Services
Server Internal
TCP
9009
Common Services
Server Internal
UDP
9020
Trap Receiving
Fault Management
Server Internal
UDP
14004
Server Internal
TCP
15000
Log server
Fault Management
Server Internal
TCP
4005040070
Server Internal
TCP
40401
LicenseServer
Common Services
Server Internal
TCP
43242
ANIServer
Client to Server
TCP
42340
Server Internal
TCP
42344
Server Internal
Common Services
2-22
OL-25957-01
Chapter 2
Prerequisites
LMS 4.2 Port Usage
Port
Protocol Number
Service Name
Functionality
Direction
(of Establishment)
of Connection
UDP
42350
Event Services
Software (ESS)
(Alternate port is
44350/udp)
Common Services
Server Internal
TCP
42351
Event Services
Software (ESS)
Listening
(Alternate port is
44351/tcp)
Common Services
Server Internal
TCP
42353
ESS Routing
(Alternate port is
44352/tcp)
Common Services
Server Internal
TCP
43441
Common Services
Database
Common Services
Server Internal
TCP
43455
Server Internal
TCP
43443
ANIDbEngine
Server Internal
TCP
43445
Fault Management
Server Internal
TCP
43446
Inventory Service
Database
Fault Management
Server Internal
TCP
43800
Device Performance
Management Database
Server Internal
TCP
43820
IPSLA Performance
Management Database
Server Internal
TCP
43447
Event Promulgation
Module Database
Fault Management
Server Internal
TCP
4440044420
CSTM Ports
TCP
4701047040
CSTM Port
Server Internal
TCP
Server Internal
TCP
50001
SOAPMonitor
Server Internal
TCP
5500055020
CSTM Port
Server Internal
TCP
5600056040
CSTM Port
VRF Lite
Server Internal
TCP
5001
Tomcat
Common Services
Server Internal
Fault Management
Device Performance
Management
Server Internal
2-23
Chapter 2
Prerequisites
Port
Protocol Number
Service Name
Functionality
Direction
(of Establishment)
of Connection
TCP
8161
ESS
Common Services
Server Internal
TCP
50002
IPMOGSServer
TCP
50003
IPMProcess
TCP
4430044301
UPMProcess
TCP
14017
EPMServer
UDP
14004
Network Topology,
Layer 2 Services and
User Tracking
TCP
5500055020
Network Topology,
Layer 2 Services and
User Tracking
TCP
4444
SyslogCollector
TCP
3333
SyslogAnalyzer
Server Internal
1. Windows Firewall blocks the port 1431 (for SNMP Traps), by default. You should free up this port for the SNMP traps to be
allowed to the server from the device.
2. Windows Firewall blocks the port 16236 (for UTLite Updates), by default. You should free up this port for the UTLite scripts
to run.
Note
In the Windows Firewall, ICMP inbound and outbound needs to be open. If you have ICMP inbound
open and outbound closed, then all the Fault Management devices will stay in questioned state.
While configuring your Windows Firewall, enable the ICMP options to allow ICMP traffic through
Firewall. See http://technet.microsoft.com/en-us/library/cc779521%28WS.10%29.aspx for more details
on administering Windows Firewall and on configuring ICMP settings in Windows Firewall.
2-24
OL-25957-01
Chapter 2
Prerequisites
Important URLs
You need to allow ICMP traffic in any Firewall that is operating between LMS Server and devices to
avoid Fault Management devices staying in questioned state.
Note
Apart from the LMS process listed in the above table, all other LMS processes use port numbers
dynamically depending on the availability of the port number. There is no range for port numbers.
Important URLs
The following URLs are most commonly used in LMS and should be added in the proxy server:
General
http://www.cisco.com
Device update/Software update/Point Patch update
http://tools.cisco.com/software/catalog/swcs/softwaremetadata
http://tools.cisco.com/software/catalog/swcs/image
http://www.cco.cisco.com
http://www.cisco.com/cgi-bin/smarts/swim/crmiosbridge.pl
http://www.cisco.com/techsupport
Smart Services
SASI_SERVERhttps://wsgx.cisco.com
RSR_SERVER https://wsgx.cisco.com
CSC_SERVERhttps://supportforums.cisco.com
CCOLOGINURLhttps://sso.cisco.com/autho/apps/nmtgSSapp/index.html
CCOLOGOUTURL https://sso.cisco.com/autho/logout.html
CASE_QUERY_URLhttps://tools.cisco.com/ServiceRequestTool/query/QueryCaseSearchAction.
do?caseType=ciscoServiceRequest
LOGIN_REDIRECT_URLhttps://fed.cisco.com/idp/startSSO.ping?PartnerSpId=csc.jivesoftware.
com
CSC_REDIRECT_URLhttps://supportforums.cisco.com
PSIRT
EoS/EoL Hardware
Reporthttp://www.cisco.com/cisco/software/release.html?mdfid=282253606&flowid=5144&sof
twareid=280775123&os=Windows&release=4.1.1&relind=AVAILABLE&rellifecycle=&reltype=
latest#
EoS/EoL Software
Reporthttp://www.cisco.com/cisco/software/release.html?mdfid=282253606&flowid=5144&sof
twareid=280775123&os=Windows&release=4.1.1&relind=AVAILABLE&rellifecycle=&reltype=
latest#
Bug Toolkit
2-25
Chapter 2
Prerequisites
http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl
http://tools.cisco.com/Support/BTKNotifications/getBugDetails.do??method=getAllBugs
http://tools.cisco.com/Support/BTKNotifications/getBugDetails.do?method=getAffectedBugdata&b
ugid=
http://tools.cisco.com/Support/BTKNotifications/getBugDetails.do?method=getBugsReport
Contract Connection
http://www.cisco.com/pcgi-bin/front.x/cconx/conx_userinfo.pl
https://www.cisco.com/cgi-bin/front.x/cconx/conx_recv_data.pl
https://www.cisco.com/cgi-bin/front.x/cconx/conx_sortdetail_js.pl
Download
Contractshttps://apps.cisco.com/CustAdv/ServiceSales/contract/viewContractMgr.do?method=v
iewContractMgr
Table 2-12
Functionalities
Telnet/SSH
Password
Enable Password
SNMP Read /
Write
Common Services
Not required
Not required
Required
Required
Not required
Not required
Required
Required
CiscoView
Not required
Not required
Required
Required
Fault Management
Not required
Not required
Required
Not required
IPSLA Performance
Management
Not required
Not required
Required
Required
Device Performance
Management
Not required
Not required
Required
Not required
Inventory
Not required
Not required
Required
Not required
Configuration
Management (Telnet)
Required
Required
Required
Not required
Configuration
Management1 (TFTP) 2
Not required
Not required
Required
Required
2-26
OL-25957-01
Chapter 2
Prerequisites
Required Device Credentials for LMS Functionalities
Table 2-12
Functionalities
Telnet/SSH
Password
Enable Password
SNMP Read /
Write
NetConfig
Required
Required
Required
Required
Config Editor
Required
Required
Required
Required
NetShow
Required
Required
Not required
Required
Required
Required
3
Required
Software Management
Required
Required
Required
Required
Required
EnergyWise
Required
Required
Required
Required
Identity Services
Required
Required
Required
Required
Auto Smartports
Required
Required
Required
Required
Smart Install
Required
Required
Required
Required
Medianet
Required
Required
Required
Required4
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 few devices like PIX devices, Cisco 2950 series switches.
4. To collect location attributes from devices, you must configure SNMPv3 AuthPriv credentials on the devices, and update
these credentials in the Device Management page.
2-27
Chapter 2
Prerequisites
2-28
OL-25957-01
CH A P T E R
In LMS 4.2, the LMS Application Database Password is requested during installation. This database
password is used internally by the LMS software to communicate with the respective applications
database. This password is also used while restoring or troubleshooting the database.
This password should be between 5 and 15 characters and should be alphanumeric. Do not start the
password with a number and do not insert spaces between characters.
While installing, you will come across these terms:
3-1
Chapter 3
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 LMS.
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 LMS Integration Utility.
To change the Cisco.com credentials, select Admin > System > Cisco.com Settings.
Installation Notes
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.
While setting up High Availability (HA) and Disaster Recovery (DR) environment in LMS server,
ensure to set them prior to LMS installation.
While launching LMS, network inconsistencies might cause installation errors if you are installing
from a remote mount point.
If your LMS 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 LMS 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 LMS.
3-2
OL-25957-01
Chapter 3
!@#$%^&*()+|}{":[];'?<>,.`=~
On Windows:
!@#$%^&*()+|}{"[];'/?<>,.`=
On Windows, check the installation log in the root directory on the drive where the operating
You can press Ctrl-C (on Solaris, and not on Soft Appliance) 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
If HP OpenView or NetView 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 LMS you must install the latest
Device Package updates.
For download locations, see Supported Devices.
Warning
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.
If you remove this link after installation, the product will malfunction.
We recommend that you run the installation from a local DVD 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 DVD to the local
hard drive. Ensure that you copy the entire contents from the DVD to the hard drive.
You must preserve the timestamp when you copy the contents from the DVD to the hard drive.
3-3
Chapter 3
command:
cd /cdrom/cdrom0
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 -)
You can install LMS 4.2 on a system with Terminal Services enabled in Remote Administration
mode. However, installation of LMS 4.2 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 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 4.2, 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.
You must disable Windows Defender on servers running Windows 2008 and reboot before installing
LMS 4.2. The installer will not copy the database to the appropriate location if you do not disable
Windows Defender.
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 4.2.
You can set the Active regional settings in Control Panel > Regional and Language Options >
Regional Options.
Ensure that the Cisco Prime Windows Server has either the US English or Japanese version of
Operating System installed. Otherwise, you must re-install the Operating System with one of the
supported versions before you install Cisco Prime LMS.
You must restart your system after you install LMS 4.2 to avoid any system instability on a
Windows Operating System.
In Windows 2008 server, you must disable the firewall before triggering LMS installation.
3-4
OL-25957-01
Chapter 3
Ensure that your system meets the recommended hardware and software specifications specified in
Server Requirements on Soft Appliance Systems.
We recommend that you disable the virus scan software on your system.
License Information
License File
Evaluation Mode
License Information
The licenses in LMS 4.2 are device based. For 10,000 device licenses, applying a single serial license
key to more than one server is supported.
For IPSLA Performance Management alone, besides the number of devices, the number of collectors
you create depends on the license and hardware requirements.
Compliance and Audit Manager (CAAM) Server License
You must have CAAM server license for accessing the following CAAM features in LMS:
3-5
Chapter 3
The following Compliance and Audit Reports are supported only by LMS license and do not require
CAAM server license.
Service Reports
This section explains about the various licenses available for LMS 4.2.
However, you can install the evaluation copy of HUM 1.2, which is packaged along with the CiscoWorks
LMS 3.2 software, from the CiscoWorks LMS 3.2 Product DVD.
Read the information in Understanding Product Ordering Options and Product Authorization Key to
understand about the various product ordering options, before you know about the various licenses of
LMS 4.2.
This section contains:
Step 2
In the vSphere client, select the VM, right-click, and select Edit Settings.
Step 3
Select the Hardware tab and change the memory and CPU allocations, as recommended.
Step 4
Select the Resources tab and change the CPU reservation, as recommended.
Step 5
3-6
OL-25957-01
Chapter 3
License File
When you register your LMS purchase on the product licensing area of Cisco.com, you will 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 provide your PAK ID while you are registering the product. See Understanding Product
Ordering Options and Product Authorization Key for information on PAK ID.
You must also enter the licensing SKU type according to the one you have purchased with the LMS 4.2
product. See License Information to furnish the appropriate license file.
You will receive the license file after the registration is completed.
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 4.2.
You must store the license file that you have received, on your LMS server.
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 4.2 product.
Note
When you want to specify the location of the License file in the Soft Appliance server, you must use
FTP/SFTP/SCP commands to transfer files to the Soft Appliance server. See Transferring Files to Soft
Appliance Server for more information.
Log into the Soft Appliance server through the command line, using a SSH client/console access. To log
into the server, you have to use the sysadmin account that was created at the time of installation.
Step 2
Note
Step 3
a.
b.
By default, the shell will be enabled with sysadmin password. If you want to change the shell password,
use Vsphere console and enter the command shell_enable in sysadmin mode. On using Vsphere
console, you will not have to enter the old password whereas on using other console, you will be
prompted to enter the old password.
Transfer the files using the following FTP, SFTP or SCP commands:
3-7
Chapter 3
FTP command
To log into FTP server use the below command:
ftp -i -n FTP_SERVER_IP_ADDRESS
ftp> user USER_NAME PASSWORD
To transfer a file from the Soft Appliance, use the below command:
ftp>put FILE_NAME
Ensure that you provide the appropriate path to the navigate to the folder where the file is
located.
Note
SFTP command
To log into the SFTP server use the below command:
sftp user@SFTP_IP_ADDRESS:PATH
To transfer a file from the Soft Appliance, use the below command:
sftp>put FILE_NAME
SCP command
Ensure that the file to be transfered is available in the SCP server.
scp [[ user@] from-host :]source-file [[user @]to-host :][destination-file]
Note
Step 4
Ensure that you provide the appropriate path to the navigate to the folder where the file is
located.
Change the owner and group name of the transferred file by using the below command:
chown casuser:casusers FILE_NAME
Evaluation Mode
If the user installing LMS 4.2 is not authorized to obtain the license on behalf of the administrator, the
product can be successfully installed for a period of time using an evaluation license.
If you have received the LMS as an evaluation copy, you need not register the product during the 60-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.
3-8
OL-25957-01
Chapter 3
If you choose to run LMS in the evaluation mode, it is valid for only 60 days and does not support any
upgrades and allows support for only 100 devices. It stops functioning after 60 days. The evaluation
period cannot be extended. The product will not work until you provide a valid license file.
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
License File.
Note
You can download the LMS 4.2 Evaluation software from http://www.cisco.com/go/nmsevals. You
must be a registered user of Cisco.com to download the software.
Note
Devices are moved to suspended state only if you manage more than 50 devices in the LMS Server.
Otherwise there is no change in the device management.
Or
Move the unnecessary devices from managed state to unmanaged state and move same number of
necessary devices from suspended to managed state.
For details on managing device states, see Unified Device Manager in Inventory Online Help.
3-9
Chapter 3
The device count that matches the current license count (LMS 50) will be in the managed state in
UDM.
To handle this scenario, see Guidelines to Avoid Necessary Devices Being Moved to Suspended State.
Note
You can download the LMS 4.2 NFR software from http://www.cisco.com/go/nmsnfr. You must be a
registered user of Cisco.com to download the software.
To install a NFR copy of LMS 4.2, 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 4.2 during the
installation.
See Performing Installation of Cisco Prime LMS 4.2 for detailed instructions on installing the product.
Step 2
Enter the LMS 4.2 NFR license file location, or click Browse to locate the NFR license file.
Step 3
Click Next.
Step 4
Click Next.
The System Requirements dialog box appears.
The installation program calculates the minimum disk space, RAM and Swap space required to install
the product.
To install NFR license of the product, the required RAM space is 4GB and Swap space is 8 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.
After the installation is completed, you should:
Step 1
Step 2
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
3-10
OL-25957-01
Chapter 3
Login to
Cisco.com
Receive the
License file
Provide the
License file during
installation
Example 1: 4XCD##V####
275801
To license your product and install the license file, you must:
Step 1
Step 2
Register the LMS product with Cisco.com using the PAK to get your license file.
See Understanding Product Ordering Options and Product Authorization Key for details. After you have
registered your copy of LMS with Cisco.com, you will receive your license file.
Step 3
directory.
On Solaris, select L for License File after you accept the Licensing Agreement and continue
3-11
Chapter 3
If you want to convert an evaluation copy to a licensed copy or if want to apply the license after the LMS
installation is completed, perform the following:
a.
After you install LMS 4.2, copy this new license file to the LMS server into a directory with read
permissions for the user name casuser in the user group casusers.
b.
c.
Click Update.
A file browser popup dialog box appears.
d.
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.
e.
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 Windows, Solaris, and Soft
Appliance systems.
3-12
OL-25957-01
Chapter 3
Grouping Services
For upto LMS 500 Device licenses, the following are the scaling limits:
30 user-defined groups
15 IPSLA groups
10 Fault groups
For LMS 500 to LMS 1000 Device licenses, the following are the scaling
limits:
50 Fault groups
For LMS 2500 Device licenses, the following are the scaling limits:
50 Fault groups
For LMS 5000 Device licenses, the following are the scaling limits:
50 Fault groups
Note
10,000 devices
200 Port and Module Configuration (PMC) groups with 90% port
groups and 10% module groups
In addition to the above, Syslog reports can contain upto 40,000 records
3-13
Chapter 3
Functionality
For upto LMS 500 Device licenses, the scaling limit is 20000 Endhosts/IP
Phones
For LMS 500 and LMS 1000 Device licenses, the scaling limit is 75000
Endhosts/IP Phones
For LMS 2500 Device licenses, the scaling limit is 150000 Endhosts/IP
Phones
For LMS 5000 Device licenses, the scaling limit is 250000 Endhosts/IP
Phones
Network Topology, Layer 2 Services and User Tracking Data Collection
discovers and tracks a maximum of 250,000 Switch Ports.
VRF-Lite, an add-on to Network Topology, Layer 2 Services and User
Tracking supports 32 VRFs in all LMS device licenses
Fault Management
The functionality supports upto 80,000 ports or interfaces (of which upto
15 percent can be in Managed state) to a maximum.
3-14
OL-25957-01
Chapter 3
Functionality
Device Performance
Management
IPSLA Performance
Management
For upto LMS 500 device licenses the MIB objects scaling limit is
6000
For LMS 500 to LMS 1000 device licenses the MIB objects scaling
limit is 30000
For LMS 2500 device licenses the MIB objects scaling limit is 50000
For LMS 5000 device license the MIB objects scaling limit is 100000.
For LMS 5000 device license, you can manage a maximum of 5000
collectors with hourly polling frequency.
license
3000 collectors in a Slave server with LMS Monitoring Server
Note
3-15
Chapter 3
Multiple number of simultaneous users can affect system performance. The maximum recommended
concurrent users depends on the size and configuration of the server.
3-16
OL-25957-01
CH A P T E R
Transfer of those services to another system when there is a catastrophic system failure
Disaster Recovery refers to the ability to recover from the catastrophic failure of the complete primary
site because of a disaster or disruption. Disaster Recovery configuration involves the duplication of
hardware and software at a remote site, with data replication occurring on a regular basis. Only then, the
remote site can take over the responsibilities of providing the services with little or no loss of data.
The High Availability solution has the following benefits:
Allows you to enable failover between clusters in a local redundancy configuration and between
sites in a geographic redundancy configuration.
Manages applications and allows you to bring the processes online or take them offline.
4-1
Chapter 4
Setting Up Cisco Prime LMS in High Availability and Disaster Recovery Environment
The implementation of Symantec Veritas High Availability solution in LMS Server supports local
redundancy (HA), geographic redundancy (DR) and Replication without clustering configurations.
The following configurations that are implemented by Symantec Veritas High Availability solution in
LMS Server, are supported through the local hard disks only:
Note
The local redundancy (HA), geographic redundancy (DR) and Replication without clustering
configurations are not supported in a Storage Area Network (SAN) environment.
Figure 4-1 displays local redundancy (high availability) configuration.
Figure 4-1
Application Clients
Primary
Application
Server
VCS
Heartbeat
Redundant
Server
Replication Link
DNS
Network Devices
275787
Switch/Router
Network
4-2
OL-25957-01
Chapter 4
Setting Up Cisco Prime LMS in High Availability and Disaster Recovery Environment
Veritas Components for Setting Up High Availability
Primary Site
(single-node)
Application Clients
Primary
Application
Server
Secondary Site
(single-node)
VCS
Heartbeat
Replication
Link
Redundant
Server
DNS
Network Devices
275788
Switch/Router
Network
4-3
Chapter 4
Setting Up Cisco Prime LMS in High Availability and Disaster Recovery Environment
Licensing Information
VCS add-on that allows managing multiple clusters, as in a Disaster Recovery environment.
The following Symantec Veritas GUI applications are used in LMS high availability solution:
Licensing Information
In a high availability or a geographic redundancy option, the LMS is active on only one server at any
given point in time. Hence only a single license of LMS needs to be procured to be shared between the
two servers (Primary and Secondary servers) running in Active-Standby mode respectively.
Solaris 10 systems
Hardware Requirements
Each server should have at least two hard disks for Windows implementation and three hard disks
for Solaris implementation. The additional hard disk should be chosen for disk group and volume
creation.
Each server should have two Network Interface Cards (NICs) assigned to it. One of the IP Addresses
can be assigned with a private IP address on both Primary and Secondary servers and they should
be connected as a direct link.
This requirement is not mandatory for a geographic redundancy configuration.
You should install Storage Foundation on servers under the Domain Controller.
General Requirements
Veritas Volume Replicator requires a static IP for replication. Make sure the system has atleast one
IP address configured which is resolved by DNS.
4-4
OL-25957-01
Chapter 4
Setting Up Cisco Prime LMS in High Availability and Disaster Recovery Environment
Setting up LMS High Availability Environment on Windows
VCS Cluster Manager (Java Console) requires an 8-bit display and a graphics card that can render
2D images.
We recommend that all servers must run the same Operating System, service pack level and system
architecture.
Step 2
Step 3
Step 4
Step 5
Step 6
Enter the product license key for Veritas Storage Foundation HA 5.1 for Windows and click Add.
Step 7
b.
recovery.
Product DocumentationDocumentation of Veritas Storage Foundation HA 5.1 for Windows
Step 8
Select the domain and the computer for the installation, and click Next.
You can select the domain from the auto-populated list. Depending on domain and network size, speed,
and activity, the domain and computer lists can take some time to populate.
4-5
Chapter 4
Setting up LMS High Availability Environment on Windows
Setting Up Cisco Prime LMS in High Availability and Disaster Recovery Environment
You can choose the computer name from the list of servers.
When the domain controller and the computer that runs the installation program are on different subnets,
the installer may not be able to locate the target computers.
You must manually enter the host names or the IP Addresses of the missing computer names.
Step 9
Step 10
Review the installation summary information and click Next after the installation has completed.
Step 11
Click Finish.
Step 12
Determine the configuration of each volume and the total number of disks needed.
Determine the initial size necessary for the volumes. You may increase the volume size at a later
time but you cannot decrease the size.
Verify that the disks you plan to include in the disk groups are available from all nodes.
Verify that the drive letters that will be assigned to the volumes are available on all nodes so that
the volumes can be accessed from any node.
Click Start > All Programs > Symantec > Veritas Storage Foundation > Veritas Enterprise
Administrator to launch the Veritas Enterprise Administrator (VEA) console.
Step 2
Select a profile if prompted. You can also select the default profile.
4-6
OL-25957-01
Chapter 4
Setting Up Cisco Prime LMS in High Availability and Disaster Recovery Environment
Setting up LMS High Availability Environment on Windows
Step 3
Step 4
Enter the host name of the server which you want to connect in the Host Name field or select a host name
from the drop-down list box.
To connect to the local system, enter localhost.
Step 5
Click Connect.
You must provide the user name, password, and domain name if prompted.
You can see the host name of the server added on to the VEA console.
Step 6
Expand the tree view under the host node to configure a disk group under the StorageAgent tree node.
Step 7
Locate the StorageAgent tree node and right-click the Disk Groups icon under the StorageAgent tree
node.
Step 8
Select New Dynamic Disk Group from the shortcut context menu.
The New Dynamic Disk Group wizard appears with the welcome page.
Step 9
Step 10
Enter a name for the disk group in the Group Name field.
You should enter datadg as group name.
b.
c.
Select the appropriate hard disks in the Available disks list, and use the Add button to move them
to the Selected disks list.
You should not select the boot disks from the Available disks list.
d.
Click Next.
Step 11
Click Next to accept the confirmation screen with the selected tasks.
Step 12
Click Start > All Programs > Symantec > Veritas Storage Foundation > Veritas Enterprise
Administrator to launch the Veritas Enterprise Administrator (VEA) console.
Step 2
Step 3
Step 4
Enter the host name of the server which you want to connect in the Host Name field or select a host name
from the drop-down list box.
4-7
Chapter 4
Setting up LMS High Availability Environment on Windows
Setting Up Cisco Prime LMS in High Availability and Disaster Recovery Environment
Click Connect.
You must provide the user name, password, and domain name if prompted. You can see the host name
of the server added on to the VEA console.
Step 6
Expand the tree view under the host node to configure a disk group under the StorageAgent tree node.
See Creating Disk Groups on Primary Server for details on how to create a disk group.
Step 7
Locate the StorageAgent tree node and right-click the Volumes icon under the StorageAgent tree node.
Step 8
Step 9
Step 10
Click Manually select disks and select the available disks (datadg) for the volume.
Ensure that the appropriate disk group name appears in the Group name drop-down list.
Step 11
Click Next.
Step 12
b.
c.
d.
Click Next.
The Add Drive Letter and Path dialog box appears.
Step 13
Step 14
Click Next.
The Create File System dialog box appears.
Step 15
Step 16
Step 17
Step 18
Step 19
Repeat the above procedure to create a volume in the datadg disk group with the following
characteristics:
Volume Size: 30 GB
4-8
OL-25957-01
Chapter 4
Setting Up Cisco Prime LMS in High Availability and Disaster Recovery Environment
Setting up LMS High Availability Environment on Windows
This volume will not be mounted and is used only by Veritas Volume Replicator.
Note
LMS is installed
Admin password, Database password, and HTTP ports are the same on both the Primary and
Secondary servers.
After installing LMS on Secondary server under cscopx volume, unmount the cscopx volume.
If you are using Veritas 5.0 and 5.1 storage foundations for setting up High Availability on a 64-bit
environment and if the set up is not functioning properly, do the following soon after the LMS
installation:
1.
Back up the existing LMS.dll file from the location NMSROOT/HA/LMS and
VCSHOME/bin/LMS to some other location and save it with different names.
2.
Copy VCSdefault.dll /defaultagent50.dll for Veritas 5.0 or 5.1, respectively from VCSHOME
location to NMSROOT/HA/LMS and VCSHOME/bin/LMS, and change the name to LMS.dll.
On Solaris, /var/VRTSvcs/bin
Note
To find out the VCSHOME location, give the echo %vcs_home% command in run prompt or
console.
4-9
Chapter 4
Setting up LMS High Availability Environment on Windows
Setting Up Cisco Prime LMS in High Availability and Disaster Recovery Environment
Modes of Replication
Modes of Replication
The Veritas Volume Replicator replicates data in one of the following modes:
Synchronous
Ensures that an update has been acknowledged by the Secondary host, before completing the update
at the Primary. If there is a network failure, it ensures that the update fails at the Primary server.
Asynchronous
The application updates are immediately reflected at the Primary server and sent to the Secondary
server, later. The updates are stored on the Replicator Log until they are sent to the Secondary
server.
Synchronous Override
In this mode, the replication is synchronous, as long as the network is available. If the network is
unavailable, the replication is continued in the asynchronous mode. The pending updates are sent to
the Secondary server when the network becomes available.
This method is chosen by default for best support.
Click Start > All Programs > Symantec > Veritas Storage Foundation > Veritas Enterprise
Administrator to launch the Veritas Enterprise Administrator (VEA) console.
Step 2
Step 3
Click Action > Setup Replicated Data Set to launch the Setup Replicated Data Set wizard.
Step 4
Step 5
Step 6
4-10
OL-25957-01
Chapter 4
Setting Up Cisco Prime LMS in High Availability and Disaster Recovery Environment
Setting up LMS High Availability Environment on Windows
Step 7
Click Next.
Step 8
Step 9
Select data_srl as the volume to be used for replicator log and click Next.
Step 10
Review the information on the summary page and click Create Primary RVG to create the RVG.
A message appears.
Step 11
Step 12
Step 13
b.
Click Next.
c.
Enter the credentials (User name and Password) to connect to the Secondary server.
d.
Step 14
Stop the Replication Network by right-clicking on the Primary server, in the Replication Network view.
Step 2
Mount the cscopx volume with the drive letter as same as in the Primary server.
Step 2
Step 3
4-11
Chapter 4
Setting up LMS High Availability Environment on Windows
Setting Up Cisco Prime LMS in High Availability and Disaster Recovery Environment
Step 4
Click the Location button in the Select Users or Groups dialog box, and select the local server from the
selection tree.
Step 5
Enter casusers in the enter object names text box and click Check Names.
The text box displays Server Name\casusers.
Step 6
Click OK.
Step 7
Click the Full Control checkbox under Allow to grant the casusers group full control.
Step 8
Step 9
Select Replace permission entries on all child objects shown here that apply to child objects.
Step 10
Click Apply and wait for the permissions to propagate to all child objects under the CSCOpx directory.
Step 11
Note
After the casusers group permissions have been set, unmount the volume and start the
replication.
Step 2
Launch the VEA Console and select View Connection > Replication Network.
Step 3
Right-click on the blue arrow displayed for the volume group to be replicated. For example, LMS_RVG.
Step 4
Click Migrate.
Step 5
Step 6
Click OK.
Mount the cscopx volume with the drive letter as the same as mount drive that is mentioned for cscopx
volume on Primary server drive.
Step 2
4-12
OL-25957-01
Chapter 4
Setting Up Cisco Prime LMS in High Availability and Disaster Recovery Environment
Setting up LMS High Availability Environment on Windows
Step 3
Step 4
NMSROOT\lib\csorb\NS_Ref
NMSROOT\campus\www\classpath\NS_Ref
NMSROOT\_nsdb_root
Step 5
Step 6
Launch the LMS Server by entering the following on the web browser:
http://Secondary_Server_IP_Address:1741
You create a cluster with both the Primary and Secondary servers.
You configure the cluster with the Notifier manager option for mail alerts.
You create service groups to control and administer the cluster such as Cluster service groups,
Replication service group, and Application service group.
4-13
Chapter 4
Setting up LMS High Availability Environment on Windows
Setting Up Cisco Prime LMS in High Availability and Disaster Recovery Environment
Click Start > All Programs > Symantec > Veritas Cluster Server > Configuration Wizards >
Cluster Configuration Wizard.
Step 2
Step 3
Click Next.
Step 4
Include the Primary and Secondary servers that should be part of the cluster.
Step 5
Step 6
Cluster ID = 0
Part of the cluster definition in the wizard is to specify the NICs for the private network. VCS uses a
private network for communications between cluster nodes for cluster maintenance.
You should set the Public NICs with Low Priority on both the servers.
Step 7
Step 8
Select the existing user account and the password for VCS helper service.
The username and password are the credentials with domain name which are used to log into the server.
Step 9
Click Ok.
Step 10
Step 11
Step 12
Enter the VCS User privileges with user name and password.
This is used to log into the cluster.
Note
Step 13
Use the Authentication Broker option instead of VCS user privileges option, if you want the
communication between the Primary and Secondary servers to be more secured.
Review the summary page and click Configure to configure the clusters.
Cluster Manager (Web Console)Configure this resource if you want to access the Cluster
Management Console (CMC) through the web browser.
You can use the VCS Configuration wizard to configure these components.
4-14
OL-25957-01
Chapter 4
Setting Up Cisco Prime LMS in High Availability and Disaster Recovery Environment
Setting up LMS High Availability Environment on Windows
Step 2
Click Next.
Step 3
Step 4
Step 5
Step 6
Select Configure Cluster Service options and configure the notifier and web console options for local
redundancy configuration (HA Setup).
Step 7
Step 8
Click OK.
Step 9
Start the Cluster Manager using Start > All Programs > Symantec > Veritas Cluster Manager - Java
Console.
Step 10
Step 11
Enter the virtual IP Address of the cluster that is configured, in the Hostname field.
Step 12
Click OK.
Log in to the cluster using the credentials that you have configured in the VCS Configuration wizard.
Use the VCS Configuration wizard to see the Cluster Service group created.
Step 2
Go to Tools > Add/Modify Service Group in the console and do the following:
Select the servers (Primary and Secondary servers) on which the service group can come online.
Step 3
Click OK.
Step 4
DiskGroupName = datadg
You must select the Critical and Enabled checkboxes for this resource. You should add this resource
only for local redundancy configuration.
Now the service group is online on both Primary and Secondary servers.
4-15
Chapter 4
Setting up LMS High Availability Environment on Windows
Setting Up Cisco Prime LMS in High Availability and Disaster Recovery Environment
Start the Cluster Manager using Start > All Programs > Symantec > Veritas Cluster Manager - Java
Console.
Step 2
Login to the cluster using the credentials that you have configured in the VCS Configuration wizard.
Use the VCS Configuration wizard to see the Cluster Service group created.
Step 3
Go to Tools > Add/Modify Service Group in the console and do the following:
Select the servers (Primary and Secondary servers) on which the service group can come online.
Step 4
Click OK.
Step 5
TargetResName = csg_nic
This name should be the same as the name of the resource of resource type NIC.
You must select the Critical and Enabled checkboxes for this resource.
Step 6
Resource Type = IP
You must select the Critical and Enabled checkboxes for this resource.
Step 7
VMDg Resource Name = Name of the Resource Configured under the App_Rep Service group
For example, datadg.
IPResName = VVR_IP
You must select the Critical and Enabled checkboxes for this resource.
Step 8
4-16
OL-25957-01
Chapter 4
Setting Up Cisco Prime LMS in High Availability and Disaster Recovery Environment
Setting up LMS High Availability Environment on Windows
DiskGroupName = datadg
You must select the Critical and Enabled checkboxes for this resource.
This is required only for geographic redundancy setup (DR setup).
4-17
Chapter 4
Setting up LMS High Availability Environment on Windows
Step 9
Setting Up Cisco Prime LMS in High Availability and Disaster Recovery Environment
Step 10
Right-click on the App_Rep service group and select Online on Primary Server.
Start the Cluster Manager using Start > All Programs > Symantec > Veritas Cluster Manager - Java
Console.
Step 2
Log in to the cluster using the credentials that you have configured in the VCS Configuration wizard.
Use the VCS Configuration wizard to see the Cluster Service group that is created.
Step 3
Go to Tools > Add/Modify Service Group in the console and do the following:
Select the servers (Primary and Secondary servers) on which the service group can come online.
Step 4
Click OK.
Step 5
RvgResourceName = Name of the Resource Configured under the App_Rep Service group
For example, App_Rvg.
You must select the Critical and Enabled checkboxes for this resource.
Step 6
VMDg Resource Name = Name of the Resource Configured under the App_Rep Service group
For example, datadg.
You must select the Critical and Enabled checkboxes for this resource.
4-18
OL-25957-01
Chapter 4
Setting Up Cisco Prime LMS in High Availability and Disaster Recovery Environment
Setting up LMS High Availability Environment on Windows
Step 7
TargetResName = NIC
You must select the Critical and Enabled checkboxes for this resource.
Step 8
Resource Type = IP
Address = Virtual IP address allocated for this cluster and used by LMS application
You must select the Critical and Enabled checkboxes for this resource.
Step 9
Import the Agent file from the location C:\Program Files\Veritas\cluster server\conf\config, into the
cluster.
Step 10
You must select the Critical and Enabled checkboxes for this resource.
Step 11
Step 12
Step 13
Step 14
Step 15
Step 16
Step 17
Step 18
Right-click on the App_Service_Gp service group and select Online on Primary Server.
4-19
Chapter 4
Setting up LMS High Availability Environment on Windows
Setting Up Cisco Prime LMS in High Availability and Disaster Recovery Environment
Create a Primary cluster with the server in Site 1 and make all the service groups online.
See Cluster Configuration for High Availability for instructions to configure a cluster and various service
groups.
Step 2
Create a Secondary cluster with the server in Site 2 and make all the service groups online except
Application Service Group.
See Cluster Configuration for High Availability for instructions to configure a cluster and various service
groups.
Note
The names of the service groups, resources and their configuration should be identical on both the
Primary cluster at Site 1 and the Secondary cluster at Site 2.
Cluster Manager (Web Console)Configure this resource if you want to access the Cluster
Management Console (CMC) through web browser.
Perform the steps explained in Creating the Cluster Service Group on both the Primary and Secondary
clusters to create the Cluster Service Group.
Step 2
Add a wac resource with the following configuration to the Cluster Service Group:
You must select the Critical and Enabled checkboxes for this resource.
Step 3
Step 4
Step 5
Link the other resources as explained in Creating the Cluster Service Group.
4-20
OL-25957-01
Chapter 4
Setting Up Cisco Prime LMS in High Availability and Disaster Recovery Environment
Setting up LMS High Availability Environment on Windows
Step 6
Right-click on the App_Rep service group and select Online on Primary Server.
You should not bring the resources to online in the Secondary cluster.
Step 7
Configure the Online Local Firm link between the App_Service_Gp and App_Rep service groups. To
do so:
a.
b.
c.
Select the Online Local Firm link option and select the name of the service group to be linked as
App_Rep.
Start the Cluster Manager using Start > All Programs > Symantec > Veritas Cluster Manager - Java
Console.
Step 2
Step 3
Click Next.
Step 4
Step 5
Step 6
Enter the Username and password which is used to log into that cluster.
A confirmation message appears stating the cluster has been successfully added.
Step 7
Note
Step 8
Click File > User Manager option to edit the default user using Java Console and give the following
permissions for App_Rep and App_Service_Gp groups:
Cluster Operator
Group Operator
Group Administrator
Step 9
Select the cluster to be used in remote site from the Global Cluster details window and select the Cluster
failover policy as Auto.
You can select the failover policy as Manual, if you want to bring the App_Service_Gp online in the
remote cluster only after getting the approval from the Cluster Administrator.
Step 10
4-21
Chapter 4
Setting up LMS High Availability Environment on Solaris
Step 11
Setting Up Cisco Prime LMS in High Availability and Disaster Recovery Environment
Click Configure.
A summary page shows that global group has been configured successfully.
The Remote Cluster status of the App service group shows the status of the service group in both the
clusters.
Step 12
Set the attributes for Administrator manually, if they are set already. To do so:
a.
b.
Click Show All attributes from the properties tab for Administrator.
c.
Step 2
Step 4
Enter 5 to install all Veritas Storage Foundation components and press Enter.
Step 5
Step 6
4-22
OL-25957-01
Chapter 4
Setting Up Cisco Prime LMS in High Availability and Disaster Recovery Environment
Setting up LMS High Availability Environment on Solaris
Step 7
Enter the required Veritas Storage Foundation license that includes the following components:
Step 8
Step 9
Step 10
Step 11
Step 12
Step 13
Step 14
Step 15
Step 16
Step 17
Step 18
Enter shutdown
Step 19
Enter ps ef | grep vx on the command prompt after reboot to verify whether all Veritas processes
are brought up successfully.
y i6 g0
4-23
Chapter 4
Setting up LMS High Availability Environment on Solaris
Setting Up Cisco Prime LMS in High Availability and Disaster Recovery Environment
Enter /opt/VRTS/bin/vea on the Solaris system command prompt to launch the Veritas Enterprise
Administrator (VEA) console.
Step 2
Step 3
Step 4
Enter the host name of the server which you want to connect in the Host Name field or select a host name
from the drop-down list box.
To connect to the local system, enter localhost.
Step 5
Click Connect.
You must enter the user name, password, and domain name if prompted. You can see the host name of
the server added on to the VEA console.
Step 6
Expand the tree view under the host node to configure a disk group under the StorageAgent tree node.
Step 7
Locate the StorageAgent tree node and right-click the Disk Groups icon under the StorageAgent tree
node.
Step 8
Select New Dynamic Disk Group from the shortcut context menu.
The New Dynamic Disk Group wizard appears with the welcome message.
Step 9
Step 10
Enter a name for the disk group in the Group Name field.
You should enter datadg as group name.
b.
Select the appropriate hard disks in the Available disks list, and use the Add button to move them
to the Selected disks list.
You should select two hard disks that are not the boot disks, from the Available disks list.
c.
Click Next.
Step 11
Click Next to accept the confirmation screen with the selected tasks.
Step 12
Enter /opt/VRTS/bin/vea on the Solaris system command prompt to launch the Veritas Enterprise
Administrator (VEA) console.
4-24
OL-25957-01
Chapter 4
Setting Up Cisco Prime LMS in High Availability and Disaster Recovery Environment
Setting up LMS High Availability Environment on Solaris
Step 2
Step 3
Step 4
Enter the host name of the server that you want to connect in the Host Name field
or
Select a host name from the drop-down list box.
To connect to the local system, enter localhost.
Step 5
Click Connect.
You must enter the user name, password, and domain name if prompted. You can see the host name of
the server added on to the VEA console.
Step 6
Expand the tree view under the host node to configure a disk group under the StorageAgent tree node.
Step 7
Locate the StorageAgent tree node and right-click the Volumes icon under the StorageAgent tree node.
Step 8
Step 9
Step 10
Click Let volume manager decide what disks to use for this volume.
Step 11
Click Next.
Step 12
b.
c.
d.
Click Next.
Step 14
Step 15
Step 16
Step 17
Repeat the above procedure to create a volume in the datadg disk group with the following
characteristics:
Volume Size: 10 GB
/opt/CSCOpx
This volume will be mounted using the mount point /var/adm/CSCOpx and is used only by LMS
application.
Step 18
Repeat the above procedure to create a volume in the datadg disk group with the following
characteristics:
4-25
Chapter 4
Setting up LMS High Availability Environment on Solaris
Setting Up Cisco Prime LMS in High Availability and Disaster Recovery Environment
Volume Size: 10 GB
This volume will not be mounted and is used only by Veritas Volume Replicator.
Note
LMS is installed
Admin password, Database password, and HTTP ports are same on both the Primary and Secondary
servers.
After installing LMS on Secondary server under cscopxvolume, unmount the cscopx and varcscopx
volumes.
Modes of Replication
4-26
OL-25957-01
Chapter 4
Setting Up Cisco Prime LMS in High Availability and Disaster Recovery Environment
Setting up LMS High Availability Environment on Solaris
Stop the Replication Network by right-clicking on the Primary server, in the Replication Network view.
Step 2
Mount the cscopx and varcscopx volumes with the mount point as the same as in the Primary server.
To add the local casusers group permissions for a Secondary server, run the following commands:
After the casusers group permissions have been set, unmount the cscopx and varcscopx volumes and
start the replication.
Step 2
Launch the VEA Console and select View Connection > Replication Network.
Step 3
Right-click on the blue arrow displayed for the volume group to be replicated. For example, LMS_RVG.
Step 4
Click Migrate.
Step 5
Step 6
Click OK.
Step 2
Step 3
4-27
Chapter 4
Setting up LMS High Availability Environment on Solaris
Step 4
Step 5
Setting Up Cisco Prime LMS in High Availability and Disaster Recovery Environment
NMSROOT/lib/csorb/NS_Ref
NMSROOT/campus/www/classpath/NS_Ref
NMSROOT/_nsdb_root
Step 6
Step 7
Launch the LMS Server by entering the following on the web browser:
http://Secondary_Server_IP_Address:1741
Configure the cluster with Notifier manager option for mail alerts.
Create service groups to control and administer the cluster such as Cluster service groups,
Replication service group, and Application service group.
4-28
OL-25957-01
Chapter 4
Setting Up Cisco Prime LMS in High Availability and Disaster Recovery Environment
Setting up LMS High Availability Environment on Solaris
Step 2
Step 3
Step 4
Press Enter after the system resumes back after stopping the VCS process.
Step 5
Enter the name of the cluster when system prompts for the cluster name.
Step 6
Step 7
Enter Y to create a new user for that cluster and press Enter.
Step 8
Step 9
Step 10
Select the public NICs among the list of NICs and press Enter.
Step 11
Enter the virtual IP Address assigned for that cluster and press Enter.
Step 12
Step 13
Step 14
Step 15
Log in to the cluster using the credentials that you have configured during the Veritas Cluster Server
configuration.
Step 16
Select the Cluster Service group and set the following attributes:
Step 17
a.
Select the Show All Attributes option from the pane displayed at the right.
b.
Make all the resources including the Notifier Manager and Cluster Management Console online.
Log in to the cluster using the credentials that you have configured in the VCS Configuration wizard.
Use the VCS Configuration wizard to see the Cluster Service group created.
Step 2
Go to Tools > Add/Modify Service Group in the console and do the following:
Select the servers (Primary and Secondary servers) on which the service group can come online.
Step 3
Click OK.
Step 4
DiskGroupName = datadg
Group
You must select the Critical and Enabled checkboxes for this resource. You should add this resource
only for local redundancy configuration.
4-29
Chapter 4
Setting up LMS High Availability Environment on Solaris
Setting Up Cisco Prime LMS in High Availability and Disaster Recovery Environment
Now the service group is online on both Primary and Secondary servers.
Step 2
Log in to the cluster using the credentials that you have configured during the Veritas Cluster Server
configuration.
You can see the Cluster Service group that is created during the Veritas Cluster Server configuration.
Step 3
Go to Tools > Add/Modify Service Group in the console and do the following:
Select the servers (Primary and Secondary servers) on which the service group can come online.
Step 4
Click OK.
Step 5
TargetResName = csg_nic
This name should be the same as the name of the resource of resource type NIC.
You must select the Critical and Enabled checkboxes for this resource.
Step 6
RVG = LMS_DR_RVG
Disk Group=
datadg
You must select the Critical and Enabled checkboxes for this resource.
Step 7
Resource Type = IP
You must select the Critical and Enabled checkboxes for this resource.
Step 8
Group
4-30
OL-25957-01
Chapter 4
Setting Up Cisco Prime LMS in High Availability and Disaster Recovery Environment
Setting up LMS High Availability Environment on Solaris
DiskGroupName = datadg
You must select the Critical and Enabled checkboxes for this resource.
This is required only for geographic redundancy setup (DR setup).
Step 9
Step 10
Right-click on the App_Rep service group and select Online on Primary Server.
Step 2
Log in to the cluster using the credentials that you have configured in the VCS Configuration wizard.
You can see the Cluster Service group that is created.
Step 3
Go to Tools > Add/Modify Service Group in the console and do the following:
Step 4
Click OK.
Step 5
RvgResourceName = Name of the Resource Configured under the App_Rep Service group
For example, App_Rvg.
You must select the Critical and Enabled checkboxes for this resource.
Step 6
TargetResName = NIC
You must select the Critical and Enabled checkboxes for this resource.
Step 7
Resource Type = IP
Address = Virtual IP address allocated for this cluster and used by LMS application
4-31
Chapter 4
Setting up LMS High Availability Environment on Solaris
Setting Up Cisco Prime LMS in High Availability and Disaster Recovery Environment
You must select the Critical and Enabled checkboxes for this resource.
Step 8
Add the Volume resource for cscopx volume with the following configuration.
Disk Group=
datadg
You must select the Critical and Enabled checkboxes for this resource.
Step 9
Add the Volume resource for varcscopx volume with the following configuration.
Disk Group=
datadg
You must select the Critical and Enabled checkboxes for this resource.
Step 10
Add the Mount resource for cscopx volume with the following configuration:
FSType=vxfs
You must select the Critical and Enabled checkboxes for this resource.
Step 11
Add the Mount resource for varcscopx volume with the following configuration:
FSType=vxfs
FSskopt=-y
You must select the Critical and Enabled checkboxes for this resource.
Step 12
Import the Agent file from the location /etc/VRTSvcs/conf/config/LMSTypes.cf, into the cluster.
Step 13
You must select the Critical and Enabled checkboxes for this resource.
Step 14
Select the Show All Attributes option from the pane displayed at the right.
b.
c.
Step 15
Step 16
4-32
OL-25957-01
Chapter 4
Setting Up Cisco Prime LMS in High Availability and Disaster Recovery Environment
Setting up LMS High Availability Environment on Solaris
Step 17
Step 18
Step 19
Step 20
Step 21
Create a Primary cluster with the server in Site 1 and make all the service groups online.
See Cluster Configuration for High Availability for instructions to configure a cluster and various service
groups.
Step 2
Create a Secondary cluster with the server in Site 2 and make all the service groups online except
Application Service Group.
See Cluster Configuration for High Availability for instructions to configure a cluster and various service
groups.
Note
The names of the service groups, resources and their configuration should be identical on both the
Primary cluster at Site 1 and the Secondary cluster at Site 2.
Cluster Manager (Web Console)Configure this resource if you want to access the Cluster
Management Console (CMC) through web browser.
NotificationConfigure this component to receive e-mail notifications about the events occurring
in the cluster.
Perform the steps explained in Creating the Cluster Service Group on both the Primary and Secondary
clusters to create the Cluster Service Group.
4-33
Chapter 4
Setting up LMS High Availability Environment on Solaris
Step 2
Setting Up Cisco Prime LMS in High Availability and Disaster Recovery Environment
In addition to these steps, you must add a wac resource with the following configuration to the Cluster
Service Group:
You must select the Critical and Enabled checkboxes for this resource.
Step 3
Step 4
Step 5
Configure the Online Local Firm link between the App_Service_Gp and App_Rep service groups. To
do so:
a.
b.
c.
Select the Online Local Firm link option and select the name of the service group to be linked as
App_Rep.
Step 2
Step 3
Click Next.
Step 4
Step 5
Step 6
Enter the Username and password which is used to log into that cluster.
A confirmation message appears stating the cluster has been successfully added.
Step 7
Note
Step 8
Click File > User Manager option to edit the default user using Java Console and give the following
permissions for App_Rep and App_Service_Gp groups:
Cluster Operator
Group Operator
Group Administrator
4-34
OL-25957-01
Chapter 4
Setting Up Cisco Prime LMS in High Availability and Disaster Recovery Environment
Moving LMS from non-HA to HA Environment
Step 9
Select the cluster to be used in remote site from the Global Cluster details window and select the Cluster
failover policy as Auto.
You can select the failover policy as Manual, if you want to bring the App_Service_Gp online in the
remote cluster only after getting the approval from the Cluster Administrator.
Step 10
Step 11
Click Configure.
A summary page shows that global group has been successfully configured.
The Remote Cluster status of the App service group shows the status of the service group in both the
clusters.
Step 12
Set the attributes for Administrator manually, if they are set already. To do so:
a.
b.
Click Show All attributes from the properties tab for Administrator.
c.
Uninstall LMS from the server if you want to migrate from non-HA to HA environment.
2.
3.
Remote Migration of LMS 3.2 SP1, LMS 4.0.1 or LMS 4.1 Data to Cisco Prime LMS 4.2 Server with HA Setup
You can do a remote migration of Cisco Prime LMS 3.2 SP1, MS 4.0.1 or LMS 4.1 data to the Cisco
Prime LMS 4.2 server with Symantec Veritas implementation.
We recommend you to:
1.
Uninstall LMS from the server if you want migrate from non-HA to HA environment.
2.
3.
4.
Migrate the Cisco Prime LMS 3.2 SP1, LMS 4.0.1, or LMS 4.1 data to the remote LMS 4.2 server
(Remote Migration).
Data Migration Guide for CiscoWorks LAN Management Solution 3.2 for instructions to do a
remote migration of data to LMS 3.2.
Migrating Data to CiscoWorks LAN Management Solution 4.0 in the Installing and Migrating to
CiscoWorks LAN Management Solution 4.0 Guide for instructions to do a remote migration of data
to LMS 4.0.
Migrating Data to Cisco Prime LAN Management Solution 4.2 for instructions to do a remote
migration of data to LMS 4.2.
4-35
Chapter 4
Setting Up Cisco Prime LMS in High Availability and Disaster Recovery Environment
Caution
Ensure that the passwords, HTTPS port and SMTP server details are the same in both the
servers (LMS 3.2 SP1, LMS 4.0.1, or LMS 4.1 and LMS 4.2 server). This is applicable only
for Windows Operating System.
4-36
OL-25957-01
CH A P T E R
VMware HA uses multiple ESX or ESXi hosts configured as a cluster to provide rapid recovery from
outages and high availability for applications running in virtual machines. You must create a cluster,
populate it with hosts, and configure VMware HA settings before failover protection can be established.
After you finish the initial setup of the host, download and install the vSphere Client. The vSphere Client
is a Windows program that you can use to configure the host and to operate its virtual machines. It
enables you to connect to an ESX or ESXi host and to a vCenter Server system. Connect to the host and
add your virtual machine by importing a virtual appliance.
5-1
Chapter 5
Overview of VMware High Availability
Setting Up Cisco Prime LMS for High Availability, Live Migration, and Storage VMotion Using VMware
It protects against a server failure by automatically restarting the virtual machines on other hosts
within the cluster.
It protects against application failure by continuously monitoring a virtual machine and resetting it
in the event that a failure is detected.
Other Requirements
5-2
OL-25957-01
Chapter 5
Setting Up Cisco Prime LMS for High Availability, Live Migration, and Storage VMotion Using VMware
Overview of VMware High Availability
Ensure that each ESX or ESXi host meets the minimum hardware requirements supported by ESX
or ESXi 4.0, 4.1, and 5.0 and vSphere Client.
All virtual machines and their configuration files must reside on shared storage accessible to both
source and target ESX hosts.
The vSphere Client must be installed on a Windows machine that has network access to the ESX or
ESXi host, vCenter Server, and Internet access.
Shared storage is typically on a storage area network (SAN), but can also be implemented using
iSCSI and NAS shared storage.
Other Requirements
Note
For a successful HA in LMS 4.2, all redundant network connections must be in the same subnet.
5-3
Chapter 5
Overview of VMware High Availability
Setting Up Cisco Prime LMS for High Availability, Live Migration, and Storage VMotion Using VMware
Install ESX or ESXi 4.0, 4.1, and 5.0 in two or more servers.
2.
3.
4.
Create a cluster and add ESX or ESXi hosts to it. See Creating a VMware HA Cluster for more
information.
5.
Configure the shared storage which is accessible to all the hosts in the cluster.
6.
7.
8.
9.
Ensure that there are no errors or alert messages (select Cluster > Summary page) in the vSphere
Client.
10.
Install LMS 4.2 in the virtual machine created in the shared storage.
Step 2
Right-click the Datacenter in the Inventory tree and click New Cluster.
Step 3
Complete the New Cluster wizard. Do not enable VMware HA (or DRS) at this time.
Step 4
Step 5
Based on your plan for the resources and networking architecture of the cluster, use the vSphere Client
to add hosts to the cluster.
Step 6
Right-click the cluster and click Edit Settings to modify the VMware HA (and other) settings for the
cluster.
Step 7
Step 8
Step 9
Admission Control
VM Monitoring
5-4
OL-25957-01
Chapter 5
Setting Up Cisco Prime LMS for High Availability, Live Migration, and Storage VMotion Using VMware
Overview of VMware VMotion and Storage VMotion
Note
For more details on VMware HA settings, see the VMware vSphere 4.0 documentation.
When the migration with VMotion is requested, vCenter Server verifies that the existing virtual
machine is in a stable state with its current host.
2.
The virtual machine state information (memory, registers, and network connections) is copied
to the target host.
3.
If any error occurs during migration, the virtual machines revert to their original states and locations.
Migration of a suspended virtual machine and migration with VMotion can be referred to as hot
migration, because they allow migration of a virtual machine without powering it off.
This section explains:
5-5
Chapter 5 Setting Up Cisco Prime LMS for High Availability, Live Migration, and Storage VMotion Using VMware
Overview of VMware VMotion and Storage VMotion
VMware VMotion
VMware VMotion enables the live migration of running virtual machines from one physical server
to another with zero down time, continuous service availability, and complete transaction integrity.
Storage array
Shared storage disks where the migrated disk files will be stored
Ensure that all the hosts and the servers meet the hardware and software requirements.
The migrating virtual machine must be on storage accessible to both the source and target hosts.
5-6
OL-25957-01
Chapter 5
Setting Up Cisco Prime LMS for High Availability, Live Migration, and Storage VMotion Using VMware
Overview of VMware VMotion and Storage VMotion
Ensure that virtual machines have access to the same subnets on source and destination hosts.
Ensure that the network labels used for virtual machine port groups are consistent across hosts.
During a migration with VMotion, vCenter Server assigns virtual machines to port groups based on
matching network labels.
Note
Install ESX or ESXi 4.0, 4.1, and 5.0 in two or more servers.
2.
3.
4.
Create a cluster and add all the ESX or ESXi hosts to it. For Storage VMotion, add the ESX
server to this cluster.
5.
Ensure that shared storage is accessible to both source and target ESX or ESXi hosts.
6.
7.
8.
9.
10.
Ensure that sufficient resource is available on the target ESX or ESXi host.
11.
12.
Migrate the virtual machine from one host to another. See Migrating a Virtual Machine with
VMotion for more information.
13.
Migrate the virtual machine from one storage to another. See Migrating a Virtual Machine with
Storage VMotion for more information.
5-7
Chapter 5 Setting Up Cisco Prime LMS for High Availability, Live Migration, and Storage VMotion Using VMware
Overview of VMware VMotion and Storage VMotion
Step 2
Right-click on the virtual machine, and select Migrate from the pop-up menu.
Step 3
Step 4
Step 5
Step 6
Step 7
Note
The VMware HA and VMotion setup supports Windows and Soft Appliance platforms only.
Step 2
Right-click on the virtual machine, and select Migrate from the pop-up menu.
Step 3
Step 4
Step 5
Choose the format to store the virtual machine after migration. By default, it will use the same format
type using which the virtual machine was created.
Step 6
5-8
OL-25957-01
Chapter 5
Setting Up Cisco Prime LMS for High Availability, Live Migration, and Storage VMotion Using VMware
Cloning a Virtual Machine Using VMware
A clone's MAC address and UUID are different from those of the parent virtual machine.
Advantages of Clones
Types of Clones
Types of Clones
Advantages of Clones
Installing a guest operating system and applications can be time consuming. With clones, you can make
many copies of a virtual machine from a single installation and configuration process. Clones are useful
when you must deploy many identical virtual machines to a group.
Types of Clones
There are two types of clones:
Full Clones
A full clone is an independent copy of a virtual machine that does not share virtual disks with the
parent virtual machine after the cloning operation. It does not access or maintain an ongoing
connection to the parent virtual machine and is separate from the parent virtual machine.
Full clones perform better than linked clones. However, full clones take longer to create than linked
clones.
Linked Clones
A linked clone is a copy of a virtual machine that shares virtual disks with the parent virtual machine
in an ongoing manner. This conserves disk space, and allows multiple virtual machines to use the
same software installation.
A linked clone is made from a snapshot of the parent. All files available on the parent at the moment
of the snapshot continue to remain available to the linked clone. Ongoing changes to the virtual disk
of the parent do not affect the linked clone, and changes to the disk of the linked clone do not affect
the parent. A linked clone must access the parent. Without access to the parent, a linked clone is
disabled.
5-9
Chapter 5
Cloning a Virtual Machine Using VMware
Setting Up Cisco Prime LMS for High Availability, Live Migration, and Storage VMotion Using VMware
Prerequisites
Known Problems
Prerequisites
This section explains the prerequisites for cloning to new VM from a parent VM:
Launch the vSphere client and locate the created virtual machine.
2.
Select the option, Clone to New Virtual Machine in the Summary tab.
3.
Enter a name for the new virtual machine (clone), select the Inventory Location and click Next.
4.
Select the host on which the new VM should run and click Next.
5.
Select the datastore in which the virtual machine files should be stored and click Next.
6.
7.
8.
Verify the settings and choose to Power on the virtual machine after creation.
9.
You can view the progress of the cloning process can be seen from Recent Tasks option or from
the Tasks & Events tab of the ESX host.
5-10
OL-25957-01
Chapter 5
Setting Up Cisco Prime LMS for High Availability, Live Migration, and Storage VMotion Using VMware
Cloning a Virtual Machine Using VMware
Note
After each step, check the Compatibility panel for any compatibility problem. Fix the problem and then
proceed with migration.
Configure the IP address (Control Panel > Network and Sharing Center > Manage Network
Connections > Properties > Internet Protocol Version 4) of the clone.
2.
Change the hostname of the clone VM (Control Panel > System > Advanced System
Settings > Computer Name).
3.
Reboot the server for the new host name to come to effect.
4.
Run the hostnamechange.pl script of LMS so that it uses the new host name:
After you reboot the server, all processes will run in the clone.
Known Problems
System defined pollers will be moved to Instance Not Found state after you run the
hostnamechange.pl script.
As a workaround, launch the dbreader and execute the following queries:
Insert into Poller_Group_Details values (6,(select id from Group_Master_Table where
Important Notes
UPMProcess
UPMProcess
5-11
Chapter 5
Cloning a Virtual Machine Using VMware
Setting Up Cisco Prime LMS for High Availability, Live Migration, and Storage VMotion Using VMware
After you clone a parent VM to a template and deploy the template to a new VM, to setup LMS in the
VM, see Setting Up LMS in the Clone Virtual Machine.
The known problems after you setup LMS in the VM are listed in Known Problems.
2.
3.
Enter a name for the template, select the Inventory Location and click Next.
4.
Select the host in which the template should be stored and click Next.
5.
Select the datastore in which the template files should be stored and click Next.
6.
7.
8.
You can view the progress of template creation process from the Recent Tasks option or from the
Tasks & Events tab of the ESX host.
Note
After each step, check the Compatibility panel for any compatibility problem. Fix the problem and then
proceed with migration.
To deploy this template to a new VM, see Deploying Template to New VM.
Launch the vSphere client and locate the host in which the template is stored.
2.
Right click on the template and select Deploy virtual Machine from this template or select
Deploy to a new Virtual Machine from the Getting Started tab.
3.
Enter a name for the new virtual machine (clone), select the Inventory Location and click Next.
4.
Select the host on which the new VM should run and click Next.
5.
Select the datastore in which the virtual machine files should be stored and click Next.
6.
7.
5-12
OL-25957-01
Chapter 5
Setting Up Cisco Prime LMS for High Availability, Live Migration, and Storage VMotion Using VMware
Cloning a Virtual Machine Using VMware
8.
Verify the settings and choose to Power on the virtual machine after creation.
9.
You can view the progress of the cloning process can be seen from Recent Tasks option or from
the Tasks & Events tab of the ESX host.
Note
After each step, check the Compatibility panel for any compatibility problem. Fix the problem and then
proceed with migration.
5-13
Chapter 5
Cloning a Virtual Machine Using VMware
Setting Up Cisco Prime LMS for High Availability, Live Migration, and Storage VMotion Using VMware
5-14
OL-25957-01
CH A P T E R
Note
The term Virtual Appliance or Soft Appliance is used throughout LMS documentation, including Online
Help.
The installation process is explained in the following sections:
Download Instructions for LMS 4.2 software on Soft Appliance - OVA Image
Installation Procedure for Cisco Prime LMS 4.2 on Soft Appliance - OVA Image
6-1
Chapter 6
On a single server with the recommended hardware requirements. See System and Browser
Requirements for Server and Client for more information.
Note
You must disable the Anti Virus enabled in your system before installation of LMS 4.2.
If HP Openview is running on your system, installation will take a longer time. Disable HP
Openview to run a faster installation.
You must have local Administrator privileges before beginning the installation. Only a user with
local Administrator privileges can install or uninstall the product.
While setting up HA and DR environment in LMS server, ensure to set them prior to LMS installation.
For further information on HA/DR configuration, see Chapter 4, Setting Up Cisco Prime LMS in High
Availability and Disaster Recovery Environment.
Go to Support > Downloads > Cloud and Systems Management > Routing and Switching
Management > Cisco Prime LAN Management Solution > Cisco Prime LAN Management Solution
4.2
Step 2
Based on the preferred operating system, choose one of the following from the software download page:
Linux
Windows
Solaris
Step 3
Step 4
Download Instructions for LMS 4.2 software on Soft Appliance - OVA Image
This section explains:
6-2
OL-25957-01
Chapter 6
The split files of this update are not available in the Cisco Prime Software Updates page (Admin >
Software Center > Software Update).
You must not change the filename of the LMS 4.2 software image files.
You must download all the split files to the same location.
You must have a minimum of 16 GB of free space on your hard disk to download the LMS 4.2
Software.
Go to Support > Downloads > Cloud and Systems Management > Routing and Switching
Management > Cisco Prime LAN Management Solution > Cisco Prime LAN Management Solution
4.2
Step 2
Step 3
Step 4
Step 5
Cisco_Prime_LMS_4_2_Install_User_Guide.zip
6-3
Chapter 6
Click Accept to accept the license agreement and download the software.
The File Download dialog box appears.
If you do not want to accept the license agreement, click Decline.
The License Agreement page appears when you download each file from Cisco.com.
Step 7
Click Save to save the LMS 4.2 software executable file on your system.
After downloading all the files from Cisco.com, ensure that the downloaded files have the following
checksum values:
Cisco_Prime_LMS_4_2_Install_User_Guide.zip1679842211 523481
Installation Procedure for Cisco Prime LMS 4.2 on Soft Appliance - OVA Image
Read the following notes before installing the software:
Note
Ensure that your system meets the recommended hardware and software specifications specified in
Server Requirements on Soft Appliance Systems.
Installing the Soft Appliance on a virtualized environment takes approximately 30 minutes for
deployment in local systems and 50 minutes for deployment in a network.
Ensure that you comment the line var/log/boot.log under syslog.conf, as this may consume more
space in boot.log when the syslog size is huge.
You need not install any soft appliance image on the Virtual Machine (VM) before installing LMS 4.2,
as the LMS 4.2 OVA image has embedded RedHat Enterprise Soft Appliance.
6-4
OL-25957-01
Chapter 6
Double click the Cisco_Prime_LMS_4_2_OVA.bat file to merge the two part files and generate a
single Cisco_Prime_LMS_4_2.ova file.
Ensure the checksum value of the ova files matches the values given below:
Step 2
Enter the IP address or name of the host that needs to be directly managed. To manage multiple hosts,
enter the IP address or name of a VCenter server.
Step 3
Step 4
Click Login.
Step 5
6-5
Chapter 6
Step 6
Click Browse to select the source OVF template from your local file system.
Step 7
Click Next.
The Deploy OVF Template - OVF Template Details window appears, see Figure 6-2. You can verify the
OVF template details.
Figure 6-2
Step 8
Click Next.
The Deploy OVF Template - Name and Location window appears.
6-6
OL-25957-01
Chapter 6
Figure 6-3
Step 9
Note
Step 10
Ensure that you provide a unique template name that does not exceed 80 characters. The unique template
name refers to the virtual host deployed in the ESX/ESXi server.
Click Next.
The Deploy OVF Template - Datastore window appears.
6-7
Chapter 6
Figure 6-4
Step 11
Select a datastore where you want to store the virtual machine files.
Step 12
Click Next.
The Deploy OVF Template - Disk Format window appears.
6-8
OL-25957-01
Chapter 6
Figure 6-5
Step 13
You can select either the Thin provisioned format or Thick provisioned format.
Note
Step 14
Click Next.
The Deploy OVF Template - Ready to Complete window appears. This window displays the deployment
setting details.
6-9
Chapter 6
Figure 6-6
Step 15
Note
Step 16
Step 17
Step 18
Press Enter in the console window to continue with the next step.
6-10
OL-25957-01
Chapter 6
Step 19
Note
Step 20
Hostname - You have to enter the server name and not FQDN.
Default DNS Domain - You have to enter the domain name of the server. For example cisco.com.
IP Address
IP Netmask
IP Default Gateway
Time Zone - You can enter the time zone value. Example Brazil/DeNoronha. See column 1 in
Table D-1 for the list of values supported.
Username - You can enter the username for this device. This user will have the privilege to enable
shell access.
Password
Confirm Password
Step 21
Note
In case of any installation errors, you can check the install error log located at: /var/log/ade/ADE.log and
/var/tmp/Cisco_Prime_Year_Month_Date.log. The installation log contains steps to download and
install the latest Service Packs, Point Patches, Device Package updates, Config Templates or the User
Tracking Utility 2.0 for LMS.
Note
If you want to power off the VM server from the ESX server, you must do so only after stopping the
daemons. You must not power off the VM server while the daemons are running.
6-11
Chapter 6
Display all the partitions of the file system using the following command:
fdisk -l
Step 2
Initialize a disk or a partition for use by LVM by entering the following command:
pvcreate /dev/sdb1
Step 3
Step 4
Step 5
Step 6
Step 7
Display the information about the logical volumes using the following command:
lvs
Step 8
Enter the following command to extend the size of the logical volume by 2GB:
lvextend -L+2G /dev/mapper/smosvg-varvol
Step 9
6-12
OL-25957-01
Chapter 6
Extending file system in Offline mode causes entire data loss, so offline mode is not recommended.
For extending the file system in offline mode using the following commands:
unmount -l /dev/mapper/smosvg-varvol
mount /dev/smosvg/varvol /var
Step 2
Step 3
Step 4
Step 5
Step 6
In all the examples, sysadmin represents the sysadmin username that you provided during installation.
Step 7
Step 8
Step 9
Step 10
Right-click the server and select Power > Reset to start the server.
Or
Enter the following command:
<HOSTNAME>/sysadmin # reload
Save the Current ADE-OS running configuration ?(yes/no)[yes]?yes
Note
You should reboot the server only if you change the following configuration details:
6-13
Chapter 6
Hostname
IP Address, IP Netmask
IP Default Gateway
Time Zone
Note
Step 12
You should execute this command only when you change the hostname. Each time you change the
hostnameof the server, you must perform, steps 1 to 9 to reflect the hostname changes in LMS.
Enter the following command to start the Daemons:
sysadmin#/etc/init.d/dmgtd start
Note
You must restart the Daemon Manager before and after you change the hostname.
Note
You must change the server configuration details only through Soft Appliance admin console.
Table 6-1 lists the examples of how to change the Soft Appliance server configuration details.
Table 6-1
Tasks
Configuration Details
6-14
OL-25957-01
Chapter 6
Table 6-1
See Supported Server Time Zones and Offset Settings for more details.
Change the Username/
Password
Show Commands
Description
application
cdp
<name>
<Description>
LMS
clock
6-15
Chapter 6
Table 6-2
Show Commands
Description
cpu
@ 2.27GHz
speed(MHz): 2261.000
cache size: 24576 KB
processor : 1
model
@ 2.27GHz
speed(MHz): 2261.000
cache size: 24576 KB
CARS-9/ sysadmin# show cpu statistics
user time:
kernel time:
idle time:
i/o wait time:
irq time:
disks
449600
39391
27231962
108498
11058
icmp_status
6-16
OL-25957-01
Chapter 6
Table 6-2
Show Commands
Description
interface
HWaddr 00:0C:29:E1:94:3F
inet addr:10.77.164.145
Bcast:10.77.164.159
Mask:255.255.255.224
MTU:1500
Metric:1
lo
Mask:255.0.0.0
MTU:16436
Metric:1
sit0
Link encap:IPv6-in-IPv4
NOARP
MTU:1480
Metric:1
TX bytes:0 (0.0 b)
6-17
Chapter 6
Table 6-2
Show Commands
Description
inventory
X7560
@ 2.27GHz
X7560
@ 2.27GHz
logging
6-18
OL-25957-01
Chapter 6
Table 6-2
Show Commands
Description
logins
pts/0
10.77.203.146
root
pts/0
10.77.203.227
still logged in
(02:13)
root
pts/0
10.77.203.243
(01:47)
root
pts/0
10.77.203.180
(00:11)
admin
tty1
reboot
system boot
setup
tty1
reboot
system boot
still logged in
(1+14:45)
(-11:-50)
(-11:-45)
memory
3912720 kB
67080 kB
425184 kB
swap-cached:
ntp
0 kB
: 171.68.10.150
refid
delay
offset
jitter
==============================================================================
127.127.1.0
*171.68.10.150
.LOCL.
10 l
10.81.254.202
2 u
64
377
0.000
0.000
0.001
790 1024
56
377
309.187
-2.404
0.558
ports
process
6-19
Chapter 6
Table 6-2
Show Commands
Description
running-config
6-20
OL-25957-01
Chapter 6
Table 6-2
Show Commands
Description
startup-config
6-21
Chapter 6
Table 6-2
Show Commands
Description
tech-support
terminal
timezone
See Supported Server Time Zones and Offset Settings for more details.
6-22
OL-25957-01
Chapter 6
Table 6-2
Show Commands
Description
timezones
udi
uptime
users
ROLE
admin
Admin
admi
Admin
HOST
10.77.203.146
TTY
LOGIN DATETIME
tty1
pts/0
6-23
Chapter 6
Table 6-2
Show Commands
Description
version
: 4.2
Vendor
-----------------------------------
State
Pid
*******
*****
***
ESS
2411
EssMonitor
Running normally
2645
EventFramework
2669
SyslogCollector
Running normally
2670
RMEDbEngine
2671
ANIDbEngine
3072
MACUHIC
Running normally
3109
UTLITE
Running normally
3110
IpmDbEngine
3111
UPMDbEngine
3342
UPMDbMonitor
Running normally
3537
DFMLogServer
3609
DFMCTMStartup
FHPurgeTask
Transient terminated
-----More-----
6-24
OL-25957-01
Chapter 6
Table 6-2
Show Commands
Description
: 4.2
Vendor
-----------------------------------
======================================================================
================- Software Installation Tool Started -================
Welcome to Cisco Prime LAN Management Solution 4.2
setup program.
======================================================================
INFO: Environment variables in this machine
LC_OS=linux
QUIET=true
TOC=disk.toc
OS=LINUX
PATH=/sbin:/bin:/usr/sbin:/usr/bin:/usr/X11R6/bin:/usr/sbin:/usr/bin:/usr/etc:/us
r/ucb:/bin
--More--
logging system
ip route
Gateway
Genmask
10.77.164.128
0.0.0.0
255.255.255.224 U
0 eth0
0.0.0.0
10.77.164.129
0.0.0.0
0 eth0
UG
Use Iface
6-25
Chapter 6
Note
The configuration commands which are not listed in the table are not tested and not supported in Soft
Appliance Server.
Note
Include the Syslog information in the /opt/CSCOpx/conf/syslog-entries.txt and run the write mem in
the sysadmin console.
Note
Ensure that your system meets the recommended hardware and software specifications specified in
Server Requirements on Soft Appliance Systems.
When there is more than one hard disk while installing LMS 4.2 (ISO image) in the UCS server, the
installation will fail. In this scenario, you have to configure logical disk or convert all the disks to a single
virtual disk in the BIOS setup before triggering the installation.
You can install the ISO image of the LMS Soft Appliance only in a NCS and UCS series server.
Refer to Downloading from Cisco.com for instructions on downloading the ISO image.
If the virus scanner is enabled on your system, the installation might take longer time.
Step 2
Enter the IP address or host name of the host that needs to be directly managed.
To manage multiple multiple hosts, enter the IP address or name of a VCenter server.
Step 3
Step 4
Click Login.
Step 5
Create a server with system requirement or select an existing server from the servers listed on the left
pane.
You must restart the server before starting the installation.
Step 6
Right-click the selected server and select Power > Reset to reboot the server.
A confirmation message appears. Click Yes to continue.
Step 7
Click the Console tab from the tabs displayed in the right pane and press Esc key to view the boot menu
in the console.
6-26
OL-25957-01
Chapter 6
Removable Devices
2.
Hard Drive
3.
CD-ROM Drive
4.
Step 8
Click the VMware tools CD icon and select CD/DVD Drive 1 > Connect to ISO image on local disk
to mount the ISO in the VMware server.
Step 9
Navigate to the location where you have downloaded the software image and click Open.
Step 10
Select the option CD-ROM Drive and press Enter to boot the ISO image.
A Welcome message appears:
Welcome to Cisco Prime LAN Management Solution 4.2
To boot from hard disk, press <Enter>
Step 11
Note
It takes approximately 40 minutes to copy all the applications of CARS and LMS.
Step 12
Type
Step 13
setup
Hostname - You have to enter the server name and not FQDN.
IP Address
Subnetmask
Gateway
DNS Domain - You have to enter the domain name of the server. For example cisco.com.
or
Enter N to proceed to NTP server configuration details.
6-27
Chapter 6
or
Enter N to proceed to the next configuration details.
Time Zone
Type h to see the list of supported time zones, and enter the time zone value. For example,
Brazil/DeNoronha. You can check Supported Server Time Zones and Offset Settings for the list of
values supported.
Username
Enter the username to access the LMS appliance console. This user will have the privilege to enable
the shell access. The default username is sysadmin. You cannot use root as the username as it is a
reserved username. You can use only alphanumeric characters for the username.
Password
Enter the sysadmin password. By default, this password will be set as the shell password.
Confirm Password
Enter the sysadmin password for confirmation. Enter Y to view the password.
Admin Password
Enter the password for the admin account to log into LMS using the browser. This password must
contain a minimum of five characters and will also be used for the System Identity account.
Note
This is the password that you must use when you login to Cisco Prime LMS.
Confirm Password
Enter the admin password for confirmation.
Step 14
If you enter Y, the following passwords will be displayed before the server gets rebooted.
LMS installation continues after validating the specified configuration details. It takes approximately 25
minutes to complete the installation.
System gets rebooted on successful installation.
Note
In case of any installation errors, you can check the install error log located at:
/var/log/ade/ADE.log and /var/tmp/ciscoworks_Year_Month_Date.log
6-28
OL-25957-01
Chapter 6
Note
If you want to power off the VM server from the ESX server, you must do so only after stopping the
daemons. You must not power off the VM server while the daemons are running.
6-29
Chapter 6
Login to a machine where you want to install LMS 4.2 Soft Appliance.
Step 2
Step 3
Note
It takes approximately 40 minutes to copy all the applications of CARS and LMS.
Step 4
Type
Step 5
setup
Hostname - You have to enter the server name and not FQDN.
IP Address
Subnetmask
Gateway
DNS Domain - You have to enter the domain name of the server. For example cisco.com.
or
Enter N to proceed to NTP server configuration details.
or
Enter N to proceed to the next configuration details.
Time Zone
Type h to see the list of supported time zones, and enter the time zone value. For example,
Brazil/DeNoronha. You can check Supported Server Time Zones and Offset Settings for the list of
values supported.
6-30
OL-25957-01
Chapter 6
Username
Enter the username to access the LMS appliance console. This user will have the privilege to enable
the shell access. The default username is sysadmin. You cannot use root as the username as it is a
reserved username. You can use only alphanumeric characters for the username.
Password
Enter the sysadmin password. By default, this password will be set as the shell password.
Confirm Password
Enter the sysadmin password for confirmation. Enter Y to view the password.
Admin Password
Enter the password for the admin account to log into LMS using the browser. This password must
contain a minimum of five characters and will also be used for the System Identity account.
Note
This is the password that you must use when you login to Cisco Prime LMS.
Confirm Password
Enter the admin password for confirmation.
Step 6
If you enter Y, the following passwords will be displayed before the server gets rebooted.
LMS installation continues after validating the specified configuration details. It takes approximately 25
minutes to complete the installation.
System gets rebooted on successful installation.
Note
In case of any installation errors, you can check the install error log located at:
/var/log/ade/ADE.log and /var/tmp/ciscoworks_Year_Month_Date.log
Note
If you want to power off the VM server from the ESX server, you must do so only after stopping the
daemons. You must not power off the VM server while the daemons are running.
6-31
Chapter 6
Recovering Admin Password on Soft Appliance Installed on NCS and UCS Server
To recover the administration password on Soft Appliance installed on NCS and UCS Server:
Step 1
Login to a machine where you want to install LMS 4.2 Soft Appliance.
Step 2
Step 3
Step 4
Note
Step 5
Enter the number corresponding to the admin username for which you want to recover the password.
From the available list of admin usernames, you can recover the password only for the first five admin
usernames. Password recovery is limited to the list of admin usernames listed. On specifying a value
apart the listed number will return you an error message.
Enter the new password.
The length of password should be a minimum of six characters. The password should comprise of
minimum of one number, one lowercase and one uppercase character.
Step 6
Step 7
Go to
http://www.cisco.com/cisco/software/release.html?mdfid=283882189&flowid=28661&softwareid=280
775102&os=Linux&release=4.1&relind=AVAILABLE&rellifecycle=&reltype=latest
Step 2
Step 3
Step 4
Enter the IP address or hostname of the host that needs to be directly managed.
Step 5
Step 6
Click Login.
Step 7
Select LMS server from the servers listed on the left pane for password recovery.
6-32
OL-25957-01
Chapter 6
Step 8
Right-click the selected server and select Power > Reset to reboot the server.
A confirmation message appears. Click Yes to continue.
Step 9
Click the Console tab from the tabs displayed in the right pane and press Esc key to view the boot menu
in the console.
In the boot menu, the following options appear:
1.
Removable Devices
2.
Hard Drive
3.
CD-ROM Drive
4.
Step 10
Click the VMware tools CD icon and select CD/DVD Drive 1 > Connect to ISO image on local disk
to mount the ISO in the VMware server.
Step 11
Navigate to the location where you have downloaded the software image and click Open.
Step 12
Select the option CD-ROM Drive and press Enter to boot the ISO image.
The following options appear in the console:
[1] Cisco Prime LAN Management Solution 4.2 Installation
[2] Recover administrator password
Step 13
Step 14
Note
Step 15
Enter the number corresponding to the admin username for which you want to recover the password.
From the available list of admin usernames, you can recover the password only for the first five admin
usernames. Password recovery is limited to the list of admin usernames listed. On specifying a value
apart from those listed will return you an error message.
Enter the new password.
The length of password should be a minimum of six characters. The password should comprise of
minimum of one number, one lowercase, and one uppercase character.
Step 16
Step 17
Log into the machine where you want to install LMS 4.2.
Step 2
6-33
Chapter 6
Note
We recommend that you run the installation from a local DVD or a local hard drive to avoid errors that
may result from the network being slow or busy.
Installation from local hard drive will be faster than installation from DVD.
If you want to install from a local hard drive, you must copy the contents from the DVD to the local hard
drive. Ensure that you copy the entire contents from the DVD to the hard drive. For more information on
copying the contents from the DVD to the hard drive, see Installation Notes (For Solaris Only)
Step 3
Copy the downloaded software image to a directory having minimum of 10 GB free space.
Step 4
Step 5
Or
#./setup.sh
A prompt appears:
Press ENTER to read the following License Agreement, or Press n to proceed with
setup? (y/n) [y]:
Step 6
Enter y to proceed.
The following message appears:
Enter the location where the product will be installed. The default location is
/opt/CSCOpx. If you choose another location, installation will create a symbolic link
/opt/CSCOpx to that location.
Destination folder should not contain the following characters:! @ # $ % ^ & * ( ) + | } { " : [ ] ; ' ? < > , . ` = ~
Enter location or q to quit [/opt/CSCOpx]:
The Custom path or location you specify cannot be the sub-directory of /opt/CSCOpx.
Caution
Step 7
Do not remove the link after installation. LMS will not work without this symbolic link.
Press Enter to accept the default directory for product installation, or enter another directory.
Make sure you have sufficient disk space. For disk space requirements, see System and Browser
Requirements for Server and Client.
Step 8
Enter any of the following to specify the license for LMS 4.2:
6-34
OL-25957-01
Chapter 6
Note
E for an evaluation mode. In this mode, you can provide license information later to fully enable the
product. This is the default option.
If you do not have a license, you can select the Evaluation Mode. You must obtain a valid License Key
within 60 days.
After specifying the License file for LMS 4.2, the Login Password prompt appears.
Step 9
Step 10
The warning and error messages that appear after these messages do not hinder the installation. They
only indicate that you need to take corrective actions after the installation has been completed.
Note
If you have specified LMS 10,000 devices license, the following warning message appears:
If the number of managed devices exceeds 5000, only Inventory, config, and Image
Management functions can remain enabled. Select Admin > System > Device Management
Functions to disable the other functions. However, you can setup LMS in another server
to enable all the other functions for the additional devices.
Note
The installation log contains steps to download and install the latest Service Packs, Point Patches, Device
Package updates, Config Templates or the User Tracking Utility 2.0 for LMS.
Note
If cluster patches are installed for Solaris 10, you must reboot your system after installing LMS.
6-35
Chapter 6
To prepare the client system for use, see System and Browser Requirements for Server and Client.
For troubleshooting information, see Checking Processes After Installation and Understanding
Installation Error Messages.
Login as administrator to the machine where you want to install LMS 4.2.
Step 2
Note
Step 3
We recommend that you run the installation from a local DVD or a local hard drive to avoid errors that
may result from the network being slow or busy.
Installation from local hard drive will be faster than installation from DVD.
If you want to install from a local hard drive, you must copy the contents from the DVD to the local hard
drive. Ensure that you copy the entire contents from the DVD to the hard drive.
Double-click on the autorun.exe or setup.exe file.
The Prerequisites window appears.
Step 4
6-36
OL-25957-01
Chapter 6
Step 5
Step 6
Click Browse button to choose the destination folder where Cisco Prime LMS will be installed.
The Choose Destination Folder dialog box appears.
Destination folder should not contain the following characters:!@#$%^&*()+|}{":[];'?<>,.`=~
The default folder is SystemDrive:\Program Files\CSCOpx.
Step 7
Step 8
Eval - If you do not have a license you can select the Eval, which is the default option and follow
Step 9 . You must obtain a valid License Key within 60 days.
Purchase - If you have purchased a license with the product you can select Purchase.
Click Browse button to specify the License File Location, if you have selected Purchase license
information.
To view the system requirement details, click View button.
If the system requirement is not met, see Server Requirements on Windows Systems.
Step 9
6-37
Chapter 6
Step 10
Step 11
Select Use the above password for the Database checkbox if you want to use the Login password as
your database password.
If you do not select the checkbox, database password will be generated randomly.
Step 12
Installation Information
Password Details
The View button will be enabled only if errors are encountered during installation. You can view the error
details on clicking the View button.
Installation Information
Provides information on how to download and install the latest Service Packs, Point Patches, Device
Package updates, Config Templates, or the User Tracking Utility 2.0. You must obtain a valid license
key from Cisco.com within 60 days. If the number of managed devices exceeds 5000, only Inventory,
config, and Image Management functions can remain enabled. Select Admin > System > Device
Management Functions to disable the other functions. However, you can setup LMS in another server
to enable all the other functions for the additional devices.
Password Details
Database Password
The Health Monitor report provides the following Hardware Parameter details:
Step 13
Memory availability
Swap
CPU
DSN
Backup status
6-38
OL-25957-01
Chapter 6
To prepare the client system for use, see System and Browser Requirements for Server and Client.
For troubleshooting information, see Checking Processes After Installation and Understanding
Installation Error Messages.
Note
We recommend that you run the installation from a local DVD or a local hard drive to avoid errors that
may result from the network being slow or busy.
Installation from local hard drive will be faster than installation from DVD.
If you want to install from a local hard drive, you must copy the contents from the DVD to the local hard
drive. Ensure that you copy the entire contents from the DVD to the hard drive.
Step 2
Step 3
On Solaris: sh
On Windows: setup.exe
setup.sh -q
answer_file_name
where answer_file_name is the full path of the user input file stored on the system.
The installation starts.
Step 4
The answer file is an ASCII file that provides the required inputs for quiet installations.
The answer file contains the following name=value pairs:
Property
Description
destination
adminPassword
Specifies the login password for the admin user. This is mandatory.
6-39
Chapter 6
secretPassword
(Solaris only)
casuser
(Windows Only)
(Windows only)
Sample Answer Files
On Windows:
#--- begin answer file
#--- hash sign (#) is allowed to mark comments
systemIdentityAccountPassword=admin
casuser=casuser
destination=C:\PROGRA~2\CSCOpx
adminPassword=admin
#--- end of answer file
On Solaris:
#cat /tmp/answer_file
##Sample Answer file
adminPassword=admin
secretPassword=admin
destination=/opt/CSCOpx
The sample answer files are also available in the Software image at the directory disk1/install.
6-40
OL-25957-01
Chapter 6
Table 6-3
Type of Upgrade
LMS 4.1
Remote migration
Procedure
1.
2.
3.
1.
LMS 4.0.1
Remote migration
1.
2.
3.
1.
Remote migration
1.
Back up the data in the old machine having LMS 3.2 SP1.
2.
3.
6-41
Chapter 6
Table 6-3
Type of Upgrade
Procedure
1.
2.
3.
4.
Remote migration
1.
2.
2.6
3.
4.
5.
6-42
OL-25957-01
Chapter 6
Step 2
Step 3
Step 4
Create either a local or remote repository. A repository contains URL and credential details
myhost/admin# configure terminal
myhost/admin(config)# repository <<myrepo>>
myhost/admin(config-Repository)# url ?
Step 5
<WORD>
Enter repository URL, including server and path info (Max Size - 80)
cdrom:
disk:
Local storage
ftp:
http:
https:
nfs:
sftp:
tftp:
Combine the URL to the repository that uses a local or remote storage.
a.
The following IOS CLI shows how to combine the URL to a repository that uses a local storage:
Before creating repository copy the downloaded
Cisco_Prime_LAN_Management_Solution_4_2_Upgrade.tar.gz to /localdisk partition of LMS 4.1
installed server.
myhost/admin(config-Repository)# url disk:
myhost/admin(config-Repository)# exit
myhost/admin(config)# exit
myhost/admin# write mem
Generating configuration...
myhost/admin#
b.
The following IOS CLI shows how to combine the URL to a repository that uses an anonymous FTP
server:
myhost/admin(config-Repository)# url ftp://<<ftp_location>>
myhost/admin(config-Repository)# user <<ftp_username>> password plain
<<ftp_password>>
myhost/admin(config-Repository)# exit
myhost/admin(config)# exit
myhost/admin# write mem
Generating configuration...
myhost/admin#
You can use the above mentioned steps for other protocols.
6-43
Chapter 6
Step 6
Step 7
Note
LMS 4.2 upgrade on Soft Appliance takes approximately more than one hour in the local server. You
should use the appliance server only after upgrade process is complete and when the login prompt
appears.
Login to the machine where the previous version of LMS (LMS 3.2 SP1, LMS 4.01 or LMS 4.1) is
installed.
Step 2
Step 3
Step 4
Follow the install procedure to install LMS 4.2. See Installing LMS 4.2 on Solaris.
Step 5
6-44
OL-25957-01
Chapter 6
To migrate and restore the LMS data, follow the procedure in Migrating Data to Cisco Prime LAN
Management Solution 4.2.
When you back up the data from LMS 3.2 SP1 and restore the data on LMS 4.2, a warning message
appears stating that there is a mismatch in the applications data. You can ignore this message and
continue the data restore. For more details on backing up and restoring data, see Migrating Data to Cisco
Prime LAN Management Solution 4.2.
Note
While setting up HA and DR environment in LMS server, ensure to set them prior to LMS installation.
For further information on HA/DR configuration, see Chapter 4, Setting Up Cisco Prime LMS in High
Availability and Disaster Recovery Environment
Log into the machine where the previous version of LMS (LMS 3.2 SP1, LMS 4.01 or LMS 4.1) is
installed.
Step 2
Step 3
Step 4
Follow the install procedure to install LMS 4.2. See Installing LMS 4.2 on Windows.
Step 5
When you back up the data from LMS 3.2 SP1 and restore the data on LMS 4.2, a warning message
appears stating that there is a mismatch in the applications data. You can ignore this message and
continue the data restore. For more details on backing up and restoring data, see Migrating Data to Cisco
Prime LAN Management Solution 4.2.
Note
While setting up HA and DR environment in LMS server, ensure to set them prior to LMS installation.
For further information on HA/DR configuration, see Chapter 4, Setting Up Cisco Prime LMS in High
Availability and Disaster Recovery Environment.
6-45
Chapter 6
Procedure 1
You can verify LMS 4.2 installation using either of these methods:
Select Admin > System > Server Monitoring > Processes from the menu, to see various processes
and their status.
The services that should be appear after installation are listed below. For details on the various
process statuses, refer to the Managing Processes in the Administration of Cisco Prime LAN
Management Solution 4.2.:
Functionalities
Common Services
Network Topology,
Layer 2 Services and
User Tracking
Services/Processes
Apache
EDS-GCF
CmfDbEngine
ESS
CmfDbMonitor
EssMonitor
CMFOGSServer
EventFramework
CSDiscovery
CSRegistryServer
jrm
DCRServer
LicenseServer
DCRDevicePoll
NameServer
diskWatcher
NameServiceMonitor
EDS
CSSCPServer
Tomcat
TomcatMonitor
ANIServer
UTLITE
ANIDbEngine
UTMajorAcquisition
UTManager
MACUHIC
VNMServer
WlseUHIC
ChangeAudit
RMEDbEngine
ConfigMgmtServer
SyslogAnalyzer
ConfigUtilityService
SyslogCollector
CTMJrmServer
PMCOGSServer
EnergyWise
EssentialsDM
ICServer
6-46
OL-25957-01
Chapter 6
Functionalities
Fault Management
Services/Processes
AdapterServer
FHPurgeTask
AdapterServer1
FHDbEngine
DataPurge
FHServer
DfmServer
Interactor
DfmServer1
Interactor1
DFMLogServer
InventoryCollector
DFMCTMStartup
InventoryCollector1
DfmBroker
INVDbEngine
DFMMultiProcLogger
NOSServer
DFMOGSServer
PMServer
EPMServer
PTMServer
EPMDbEngine
TISServer
IPSLA Performance
Management
IPMProcess
IPMOGSServer
IpmDbEngine
Device Performance
Management
UPMDbEngine
UPMDbMonitor
UPMProcess
Procedure 2
You can also verify the installation using Software Center. To verify the installation, Select Admin >
System > Software Center > Software Update and the Software Updates page appears. You can verify
the installation using the Products installed dialog box.
The following entry appears in the Products Installed table.
Product Name
4.2
If SSL is disabled and if you have installed the LMS on the default port, enter:
http://server_name :1741
If SSL is enabled, and if you have installed the LMS on the default port, enter:
https://server_name :443
where server_name is the hostname of the server on which you have installed LMS.
The LMS Login page appears.
6-47
Chapter 6
You can change the default web server port numbers (for HTTP and HTTPS modes) using the changeport
utility. See Administration of Cisco Prime LAN Management Solution 4.2 for more information.
On a Windows system, if you are using HPOV as your third party NMS application, you would require
the IIS service to be enabled for HPOV to install and run. The IIS web server runs on SSL port 443,
which is the default port for the LMS web server when installing LMS. To avoid a conflict, you should
change the SSL port number of the LMS web server from 443 to another port that is available, and that
has a number in the range 1026 to 65535, except 6000.
Port number 6000 is reserved by Firefox, if you enter 6000 as the SSL port number, after installation (for
all the three operating systems), you will not be able to launch LMS using the Firefox browser. You must
ensure that you do not configure port 6000 during installation.
Note
If you have accessed LMS earlier, we recommend you to clear the browser cache and delete cookies
before logging into LMS again. See Clearing Cache and Cookies for more information.
Note
Go to Tools menu.
Step 2
Step 3
Select the check box for Temporary Internet Files and Cookies.
Step 4
Click Delete. Once the files have been deleted, click Okay.
Go to Tools menu.
Step 2
6-48
OL-25957-01
Chapter 6
Step 3
Step 4
Select Details.
Step 5
Select:
Step 6
Select Start > All Programs > Administrator Tools > Server Manager.
The Server Summary page appears.
Step 2
Step 3
Step 4
Click OK.
Step 5
Enter the username in the User ID field, and the password in the Password field of the Login page.
The LMS server administrator can set the passwords for admin and guest users during installation.
Contact the LMS server administrator if you do not know the password.
Step 2
6-49
Chapter 6
Note
The uninstall log file will be generated using time stamp with the YYYYMMDD_hhmmss format,
for example, C:/LMS_uninstall_YYYYMMDD_hhmmss.
The install folder will be removed and the casuser will be removed after uninstallation of LMS 4.2.
If the uninstallation is not performed by an administrator or a user with equivalent privileges, the
uninstallation may not complete successfully.
Use the Uninstall option to remove LMS files and settings. You must be logged in as administrator to
uninstall.
Step 2
Note
Enter c to quit the uninstall and manually delete the collectors using IPSLA Performance
Management CLI.
Enter y to delete the collectors in the device and continue with the uninstall.
6-50
OL-25957-01
Chapter 6
Check the following files after uninstallation and ensure to perform the following:
/etc/syslog.conf
Ensure that the following entry is removed:
local0.emerg;local0.alert;local0.crit;local0.err;local0.warning;local0.notice;local
0.info;local0.debug /var/adm/CSCOpx/log/dmgtd .log .
/etc/services
Ensure that port assignments for LMS 4.2 have been removed.
/etc/inetd.conf
Ensure that the LMS TFTP entry is removed.
Go to the Windows desktop and select Start > Programs > Cisco Prime LMS > Uninstall Cisco
Prime LMS.
Uninstallation process begins.
The following message appears:
LMS is currently installed in the server. Delete the configured collectors to remove the
corresponding collector entries from the source routers, and uninstall LMS. CLick
"Cancel" to quit the uninstall and manually delete the collectors using IPSLA Performance
Management CLI. Click "Yes" to delete the collectors in the device and continue with the
uninstall. Click "No" to continue with uninstall without deleting the collectors in
device. Default is 'No'.
Click Cancel to quit the uninstall and manually delete the collectors using IPSLA Performance
Management CLI.
Click Yes to delete the collectors in the device and continue with the uninstall.
The uninstallation proceeds and the Uninstallation Complete dialog box appears after uninstallation
completes.
If the uninstallation completes with errors, the following error message appears:
Installation of Cisco Prime Lan Management Solution 4.2 completed. Some errors occured
during installation. See NMSROOT /Cisco_Prime_uninstall_YYYYMMDD_hhmmss.log for details.
Step 2
6-51
Chapter 6
Caution
You must restart your system after the uninstallation is complete. The subsequent installation of other
LMS products may fail if you do not restart your system.
During re-installation, you can choose to enter new passwords or retain the existing ones. For more
information on passwords, see Password Information.
during installation.
Appears so that you can stop or kill the file that uses this dll for the installation to proceed, else
the installation will crash due to overwrite of the files loaded in the memory.
You can verify the exe that locks the dll by using the process explorer tool available at the Microsoft
site at: http://technet.microsoft.com/en-us/sysinternals/bb896653.aspx
In Windows, if the WMI service is up and running, the following message appears when installation
starts:
Windows Management Instrumentation (WMI) is running. This locks processes and impedes
installation. To avoid WMI conflicts, this Setup program will stop and immediately
restart the WMI service.
Do you want to proceed?
Click Yes to proceed with this installation. Click No to exit installation.
6-52
OL-25957-01
CH A P T E R
Migrating Data From LMS 3.2 SP1, LMS 4.0.1 or LMS 4.1
2.
3.
You have to freshly install LMS 4.2 and then perform remote data migration from LMS 3.2 SP1, LMS
4.0.1 and LMS 4.1. LMS 4.2 does not support direct upgrade from previous versions other than LMS
4.0.1/4.1.
Data Migration to LMS 4.2 can be done using the following methods:
Note
Normal Backup - Process by which all the configuration files and collected data can be backed up
from application database.
Selective Backup - Process by which only required system configurations and data can be backed
up.
On Solaris machine, the backed up folder must be compressed and transferred. If not, the restore may
fail due to the changes in the file name and checksum, as the file name changes from the upper case to
the lowercase.
7-1
Chapter 7
Note
While copying the backup data from remote Solaris servers, transfer the data in Binary mode. If any FTP
client software is used, ensure that the default transfer mode is set to Binary.
The data migration will not be successful if you transfer the backup data in ASCII or Auto mode
Notes for Remote Migration
When you back up the data from LMS 3.2 SP1and restore the data on LMS 4.2, a warning message
appears stating that there is a mismatch in the applications data. You can ignore this message and
continue the data restore.
On all platforms, migration is supported across different NMSROOT directories, where NMSROOT
is the LMS installation directory. By default, it is:
/opt/CSCOpx for Solaris and Soft Appliance
C:\Program Files\CSCOpx for Windows, where C: is the System Drive
Cross platform data migration from Solaris to Soft Appliance is supported for the following LMS
versions:
LMS 3.2 SP1
LMS 4.0.1
LMS 4.1
LMS 4.2
Normal backup or selective backup can be chosen to restore the data from these versions to the LMS
Soft Appliance server. Ensure that all the prerequisites are addressed. Refer Prerequisites for more
details.
This section contains the following topics:
Network Topology, Layer 2 Services and User Tracking Data Migration Scope
Data Migration to LMS 4.2 can be done using the following methods:
Normal Backup - Process by which all the configuration files and collected data can be backed up
from application database.
7-2
OL-25957-01
Chapter 7
Selective Backup - Process by which only required system configurations and data can be backed
up.
7-3
Chapter 7
License data
Jobs and Resources data, DCR data, Groups data, and other data stored in the database
System Preferences
Multiple Default Credentials Multiple Default Credentials are migrated only when you restore
data from LMS 3.2 SP1 and LMS 4.0.1/4.1/4.2 for Windows, Solaris and Soft Appliance.
Policy Configuration Policy Configuration are migrated only when you restore data from
LMS 3.2 SP1 and LMS 4.0.1/4.1/4.2 for Windows, Solaris and Soft Appliance.
Logrot Configuration Logrot Configuration are migrated only when you restore data from
LMS 3.2 SP1 and LMS 4.0.1/4.1/4.2 for Windows, Solaris and Soft Appliance.
DCR Exclude list DCR Exclude list are migrated only when you restore data from LMS 3.2 SP1
and LMS 4.0.1/4.1/4.2 for Windows, Solaris and Soft Appliance.
Unreachable Device Polling Settings Unreachable Device Polling Settings are migrated only
when you restore data from LMS 3.2 SP1 and LMS 4.0.1/4.1/4.2 for Windows, Solaris and Soft
Appliance.
LDAP Configuration LDAP Configuration are migrated only when you restore data from
LMS 3.2 SP1 and LMS 4.0.1/4.1/4.2 for Windows, Solaris and Soft Appliance.
7-4
OL-25957-01
Chapter 7
Selective Backup
When you run a selective data backup from CLI, all the data mentioned above gets backed up except:
UDM will get the count of managed devices from PIDM table of the backup data (only distinct device
IDs). Based on the LMS 4.2 license count, the respective number of devices will be moved to Managed
state and the remaining devices will be moved to Suspended state. So all the collections will be running
only for the Managed devices in UDM. But for the Suspended devices, the history of the data will be
maintained. If you want to run the collections for Suspended devices, you can either:
Move some of the unnecessary devices from the Managed state to Unmanaged state and move
necessary devices from the Suspended state to the Managed state.
If you have configured UDM policy (Managed By Group) in freshly installed LMS 4.2 server and have
been managing some set of the devices, and if you migrate LMS data from the older version to LMS4.2,
the backed up data will be the backed up data will be restored in LMS 4.2 server and the UDM policy
will be set as Managed By All devices, after the migration. For details on the behavior of device states
see UDM Device State Change After Migration Based on License Limit.
ACS Backup / Restore Behavior in LMS 4.2
While restoring ACS backup from LMS 3.2 SP1, the Authentication mode will be changed to Local
Authentication Mode. No user or groups will be imported from ACS. The authentication and
authorization will be done locally.
Same Name User Defined Groups in Different Applications (backup data) Behavior After Restore in LMS 4.2
Case1: If you have "Group1" in CS, CM and RME (part of LMS versions earlier to LMS 4.0) while
backing up data from LMS 3.2 SP1 then after restoring the backed up data in LMS 4.2, "Group1" of
CS alone will be retained. "Group1" of CM and RME will be deleted.
Case2: If you have "Group1" in CM and RME (part of earlier LMS versions) while backing up data
from LMS 3.2 SP1 then after restoring the backed up data in LMS 4.2, "Group1" of both CM and
RME will be deleted.
7-5
Chapter 7
Network Topology, Layer 2 Services and User Tracking Data Migration Scope
Network Topology, Layer 2 Services and User Tracking data in LMS 4.2 (known as CM in earlier LMS
versions) can be backed up using either the Normal or the Selective mode.
TrustSec related settings available in IDMMonitor.properties will be applicable only for same version
backup and restore.
Following are the conditions for the group settings:
If the groups exist with same name in CS and CM (part of earlier LMS versions), then the CS group
will only exist after restore.
If the groups exist with same name in CM and RME (part of earlier LMS versions), then both the
groups will be dropped.
Normal Backup
The following data gets migrated when you upgrade to LMS 4.2:
SNMP Settings
Config Credentials
Topology layoutsManually updated topology layouts will not be migrated for upgrade and
backup/restore.
Device Details
VNM Settings, Jobs and Archives VNM Settings Jobs and Archives are migrated only when you
restore data from LMS 3.2 SP1 and LMS 4.0.1/4.1/4.2 for Windows, Solaris and Soft Appliance.
Selective Backup
When you run a selective data backup from CLI, all the data mentioned above gets backed up except:
Device Details
7-6
OL-25957-01
Chapter 7
Change Audit
Set Purge Policy
Force Purge
Config Change Filter
Config Management
Transport Settings
Archive Settings
Collection Settings
Purge Settings
Exclude Commands
Fetch Settings
Config Editor
Config Job Policies
Device Management
Device Management Settings
Device Credential Verification Settings
Reports
Archive Settings
PSIRT/EOS/EOL Reports
EnergyWise reports
Config Archive
Shadow directory
ChangeAudit records. This includes Configuration change details
Archived configuration versions
NetConfig
User-defined Templates (UDT)
Default Template Usage
By default, all templates are assigned to Admin on migration. The device-to-task mapping is
not migrated.
7-7
Chapter 7
Configuration groups
Archive Management
All jobs
Label Configs
Custom queries
Baseline templates
Shadow directory
ChangeAudit records. This includes Configuration change details.
Archived configuration versions
Config Editor:
Private Configs
Public Configs
Config Editor jobs
Editing mode in which the files are opened. It is either Raw or Processed.
NetConfig:
Netconfig jobs. This includes Device based jobs, Port based jobs and Module based jobs. Port
and Module based jobs are migrated only when you restore data from LMS 3.2 SP1 and
LMS 4.0.1/4.1/4.2 for Windows, Solaris and Soft Appliance.
User-defined tasks
NetShow:
NetShow jobs
Output archives
Commandsets
Software Management
View/Edit Preferences
Update Upgrade Information
Software Management repository images
All jobs in a Job Browser
System Preferences
Application Log Level Settings
Job Purge
RME Device Attributes
RME Secondary Credentials
Collection Failure Notification
7-8
OL-25957-01
Chapter 7
Inventory
Inventory Change Filter
System Job Schedule
Cisco.com Fetch Interval
Inventory jobs
Device details
Inventory Collection status
DCA jobs
Device Management state
User -defined groups
Syslog details
Set Backup Policy
Set Purge Policy
Force Purge
Automated actions
Message filters
Custom reports
Syslog messages for the past 14 days
Report jobs and archives
Port and Module group administration Port and Module group administration are migrated only
when you restore data from LMS 3.2 SP1 and LMS 4.0.1/4.1/4.2 for Windows, Solaris and Soft
Appliance.
Port groups
Module groups
Template Center
Template Center jobs
WorkCenters
EnergyWise jobs
Identity jobs
ASP jobs
SI jobs
SI profiles
SI configs
7-9
Chapter 7
Selective Backup
When you run a selective data backup from CLI, all the data mentioned above gets backed up except:
SWIM Images
Syslog data
SmartInstall Archives
The following data gets migrated when you upgrade to LMS 4.2:
Device list:
The migration procedure adds devices to LMS Device and Credentials Repository (DCR).
To automatically manage devices from DCR in LMS 4.2, you can configure the Device Management
Policy in Unified Device Manager (UDM) (select Inventory > Device Administration > Device
Allocation Policy), or add them manually (Inventory > Device Administration > Add as
Managed Devices)
Fault groups
Device details
Event sets
JRM Jobs
7-10
OL-25957-01
Chapter 7
Events details
SNMP SettingsSNMP Settings are migrated only when you restore data from LMS 3.2 SP1 and
LMS 4.0.1/4.1/4.2 for Windows, Solaris and Soft Appliance.
Email Subject customization settingsEmail Subject customization settings are migrated only
when you restore data from LMS 3.2 SP1 and LMS 4.0.1/4.1/4.2 for Windows, Solaris and Soft
Appliance.
Selective Backup
When you run a selective data backup from CLI, all the data mentioned above gets backed up except:
Events details
The following data gets migrated when you upgrade to LMS 4.2:
IPSLA databaseContains information about source devices, target devices, operations, collectors,
and the statistics of data collected.
During the same version backup/restore, do not run /NMSROOT/bin/restorebackup.pl script from the
following directories:
Solaris/Soft Appliance
NMSROOT/MDC/tomcat/webapps/ipm/system_reports
/var/adm/CSCOpx/files/ipm/ and
/opt/CSCOpx/MDC/tomcat/webapps/ipm/archive_charts
Windows
NMSROOT\MDC\tomcat\webapps\ipm\system_reports
NMSROOT\CSCOpx\files\ipm\ and
NMSROOT\CSCOpx\MDC\tomcat\webapps\ipm\archive_charts
7-11
Chapter 7
When you migrate from LMS 3.0 or LMS 3.0 December 2007 Update or LMS 3.1 to LMS 4.0.1 and then
install LMS 4.2, the following data gets migrated:
IPSLA databasecontains information about source devices, target devices, operations, collectors,
admin settings and the statistics of data collected.
Log Settings.
System Reports
Selective Backup
When you run a selective data backup from CLI, all the data mentioned above gets backed up except
the statistical table available in database.
The following data gets migrated when you upgrade to LMS 4.2:
Configuration Data
Reports
Template Configuration
Database
Poller Configuration
Threshold Configuration
Admin Settings
Polled data
Threshold Violation data
Summarization data
Job information.
Trendwatch Configurations Trendwatch Configurations are migrated only when you restore
7-12
OL-25957-01
Chapter 7
TrendWatch Violation data TrendWatch Violation data are migrated only when you restore
Trap Receiver Groups Trap Receiver Groups are migrated only when you restore data from
HUM 1.2 and LMS 4.2.
Syslog Receiver Groups Syslog Receiver Groups are migrated only when you restore data from
HUM 1.2 and LMS 4.2.
Selective Backup
When you run a selective data backup from CLI, all the data mentioned above gets backed up except the
Polled data and completed reports.
LMS will not backup old device performance management reports and will backup periodic reports.
Normal Backup
TrendWatch Configurations along with the TrendWatch Violation data - this is applicable only if you
restore LMS 3.2 SP1 and LMS 4.0.1/4.1/4.2 for Windows, Solaris and Soft Appliance.
Admin Settings
Data Purge, Job Purge and Poll Settings (SNMP retry / timeout, Failure frequency / notification
details)
Trap Receiver Groups and Syslog Receiver Groups (this is applicable only if you restore
LMS 3.2 SP1 and LMS 4.0.1/4.1/4.2 for Windows, Solaris and Soft Appliance.
7-13
Chapter 7
Selective Backup
Poller Configurations alone. Polled data (Summarization data) will not be migrated.
TrendWatch Configurations alone. TrendWatch Violation data will not be migrated - this is
applicable only if you restore LMS 3.2 SP1/4.0.1/4.1 backup.
Admin Settings
Data Purge, Job Purge and Poll Settings (SNMP retry / timeout, Failure frequency / notification
details)
Trap Receiver Groups and Syslog Receiver Groups (this is applicable only if you restore
LMS 3.2 SP1 and LMS 4.0.1/4.1/4.2 for Windows, Solaris and Soft Appliance.
7-14
OL-25957-01
Chapter 7
Figure 7-1 shows the migration of data from LMS 2.6 to LM S 4.0.
7-15
Chapter 7
Figure 7-1
Migrating Data from LMS 2.6 to LMS 3.2 (Old Picture , will be updated in the next
draft)
LMS 2.6
LMS 3.2
Operating System
Solaris 8, Solaris 9
274762
Operating System
Solaris 9, Solaris 10
Figure 7-2 shows the migration of data from LMS 2.6 SP1 to LMS 4.0
Figure 7-2
Operating System
Solaris 9, Solaris 10
274763
Operating System
Solaris 8, Solaris9
LMS 3.2
7-16
OL-25957-01
Chapter 7
You must install LMS 3.2 without HUM 1.2. HUM 1.2 installation should be initiated only after LMS
3.2 installation and data restoration are completed. This note is applicable only if HUM 1.2 is a part of
LMS 3.2 installation. \\Reviewers, how will this note change w.r.t to the LMS 4.2?
The application list in the backed up data should exactly match the application list in the machine where
it is restored except for CiscoWorks Assistant and Portal. If there is a difference then the behavior of the
applications after upgrade will be unpredictable.
Remote Migration From LMS 3.0 or LMS 3.0 December 2007 Update or LMS 3.1
Figure 7-3 shows the migration of data from LMS 3.0 to LMS 4.2.
Figure 7-3
Migrating Data from LMS 3.0 to LMS 4.2 (this figure will be updated)
LMS 3.0
LMS 3.2
Operating System
Solaris 9, Solaris 10
Solaris 9, Solaris 10
274764
Operating System
Figure 7-4 shows the migration of data from LMS 3.0 December 2007 Update to LMS 4.2.
7-17
Chapter 7
Figure 7-4
Migrating Data from LMS 3.0 December 2007 Update to LMS 4.2 (this figure will be
updated)
LMS 3.2
Operating System
Solaris 9, Solaris 10
Solaris 9, Solaris 10
274765
Operating System
Figure 7-5 shows the migration of data from LMS 3.1 to LMS 4.2.
Figure 7-5
Migrating Data from LMS 3.1 to LMS 4.2 (this figure will be updated)
LMS 3.2
LMS 3.1
Operating System
Solaris 9, Solaris 10
Solaris 9, Solaris 10
274766
Operating System
7-18
OL-25957-01
Chapter 7
Migrating Data From LMS 3.2 SP1, LMS 4.0.1 or LMS 4.1
This section explains how to migrate data from LMS 3.2 SP1, LMS 4.0.1 or LMS 4.1.
This section contains:
Note
You cannot perform backup on network drives. We recommend you to stop the daemon manager, before
you take the backup of LMS data.
To migrate LMS 3.2 SP1, LMS 4.0.1 or LMS 4.1 data to a remote machine:
Step 1
Step 2
Step 3
Step 4
Step 5
Transfer the backup directory BKP that contains the LMS 3.2 SP1 data as a compressed file (example
.tar) from Machine A to any temporary location.
Step 6
Step 7
7-19
Chapter 7
Migrating Data From LMS 3.2 SP1, LMS 4.0.1 or LMS 4.1
You can also restore data from LMS 3.2 SP1, LMS 4.0.1 or LMS 4.1 to the LMS 4.2 server with
Symantec Veritas or VMware HA implementation.
Step 8
Note
Step 9
For details on High Availability (HA) implementation using Symantec Veritas, see Setting Up Cisco
Prime LMS in High Availability and Disaster Recovery Environment.
For details on High Availability (HA) implementation using VMware, see Setting Up Cisco Prime
LMS for High Availability, Live Migration, and Storage VMotion Using VMware.
Examine the log files in the following location to verify that the data was restored. The files are:
/var/adm/CSCOpx/log/restorebackup.log
/var/adm/CSCOpx/log/migration.log
/var/adm/CSCOpx/log/rme_base.log
The migration.log and the rme_base.log will be created only when RME (part of earlier LMS versions)
is migrated.
Start the daemon manager by entering:
/etc/init.d/dmgtd start
You can follow the above procedure to perform same version data migration from Windows to Windows.
Step 2
Step 3
Step 4
Step 5
Copy the backup directory BKP that contains the LMS 3.2 SP1 data from Machine A to any temporary
location.
Step 6
Step 7
7-20
OL-25957-01
Chapter 7
You must enter the absolute path for BKP. For example, if BKP is under C:\, enter the path as
NMSROOT\bin\perl NMSROOT\bin\restorebackup.pl -d C:\BKP.
For more details, see Syntax and Usage for Restore Script.
See Notes for Remote Migration.
You can also restore data from LMS 3.2 SP1, LMS 4.0.1 or LMS 4.1 to the LMS 4.2 server with
Symantec Veritas or VMware HA implementation.
Note
Step 8
Note
Step 9
For details on High Availability (HA) implementation using Symantec Veritas, see Setting Up Cisco
Prime LMS in High Availability and Disaster Recovery Environment.
For details on High Availability (HA) implementation using VMware, see Setting Up Cisco Prime
LMS for High Availability, Live Migration, and Storage VMotion Using VMware.
Ensure that the passwords, HTTPS port and SMTP server details are same in both LMS 3.2 SP1, LMS
4.0.1 or LMS 4.1 server and LMS 4.2 server with Symantec Veritas implementation, while migrating
data from non-HA to HA environment.
Examine the log files in the following location to verify that the data was restored.The files are:
NMSROOT\log\restorebackup.log
NMSROOT\log\migration.log
NMSROOT\log\rme_base.log
The migration.log and rme_base.log will be created only when RME (part of earlier LMS versions) is
migrated.
Start the daemon manager by entering:
net start crmdmgtd
You can follow the above procedure to perform same version data migration from Solaris to Solaris.
To migrate the data from Solaris (LMS 3.2 SP1, LMS 4.01 or LMS 4.1)/ Soft Appliance (LMS 4.1) to
Soft Appliance (LMS 4.2) in a remote machine:
Step 1
Step 2
7-21
Chapter 7
Migrating Data From LMS 3.2 SP1, LMS 4.0.1 or LMS 4.1
You must enter the absolute path for BKP. For example, if BKP is under /opt, give the path as
NMSROOT/bin/perl NMSROOT/bin/backup.pl /opt/BKP.
To do selective backup using CLI, see Appendix E, Syntax and Usage for Backup Script.
Step 3
Step 4
Step 5
Transfer the backup directory BKP that contains the LMS 3.2 SP1, LMS 4.0.1 or LMS 4.1 data as a
compressed file (example .tar) from Machine A to any temporary location. For more information on
transferring to Soft Appliance, refer Transferring Files to Soft Appliance Server.
Step 6
Step 7
Step 8
Note
Step 9
Examine the log files in the following location to verify that the data was restored. The files are:
/var/adm/CSCOpx/log/restorebackup.log
/var/adm/CSCOpx/log/migration.log
/var/adm/CSCOpx/log/rme_base.log
The migration.log and the rme_base.log will be created only when RME (part of earlier LMS versions)
is migrated.
Start the daemon manager by entering:
/etc/init.d/dmgtd start
You can follow the above procedure to perform same version data migration from Solaris/Soft Appliance
to Soft Appliance.
Migrating Data from Windows to Soft Appliance
To migrate data from Windows (LMS 3.2 SP1, LMS 4.01 or LMS 4.1) to Soft Appliance (LMS 4.2) in
a remote machine:
Step 1
Step 2
7-22
OL-25957-01
Chapter 7
You must enter the absolute path for BKP. For example, if BKP is under C:\, enter the path as
NMSROOT\bin\perl NMSROOT\bin\backup.pl C:\BKP.
To do selective backup using CLI, see Appendix E, Syntax and Usage for Backup Script.
Step 3
Step 4
Step 5
Transfer the backup directory BKP that contains the LMS 3.2 SP1, LMS 4.0.1 or LMS 4.1 data as a
compressed file (example .tar) from Machine A to any temporary location. For more information on
transferring to Soft Appliance, refer Transferring Files to Soft Appliance Server.
Step 6
Step 7
Step 8
Note
Step 9
Examine the log files in the following location to verify that the data was restored. The files are:
/var/adm/CSCOpx/log/restorebackup.log
/var/adm/CSCOpx/log/migration.log
/var/adm/CSCOpx/log/rme_base.log
The migration.log and the rme_base.log will be created only when RME (part of earlier LMS versions)
is migrated.
Start the daemon manager by entering:
/etc/init.d/dmgtd start
You can follow the above procedure to perform same version data migration from Windows to Soft
Appliance.
7-23
Chapter 7
Select Admin > Network > Notification and Action Settings > Fault - SNMP trap receiving settings.
The configuration page for SNMP trap receiving is launched.
Step 2
Step 3
Click Apply.
7-24
OL-25957-01
Chapter 7
Select Admin > Network > Notification and Action Settings > Fault - SNMP trap forwarding.
The configuration page for SNMP trap forwarding is launched.
Step 2
Step 3
Click Apply.
Step 4
Make sure NMS is configured to receive traps at the port you specified in Step 2.
Note
HPOV or NetView adapters are not supported for the Fault Management functionality in LMS 4.2
Step 2
Step 3
Note
Read Delay
Transport Timeout
Login Timeout
Tune Sleep
Click Apply.
Modifying the default timeout values will apply to all the devices and impact the work flows of all
devices. To edit per device level attributes, go to Admin > Collection Settings > Inventory > Edit the
Inventory, Config Timeout, and Retry settings.
To configure remote versions of HP OpenView and NetView to forward SNMP traps to LMS, you must
install the HPOV-NetView adapters on the remote systems.
7-25
Chapter 7
Local Authentication
KerberosLogin
MS Active Directory
RADIUS
TACACS+
LMS 4.2 uses server authentication (Local Authentication Mode) to authenticate users and authorize
them to access LMS.
However, if you select a Login module other than Local Authentication, you can only perform
authentication and not authorization. You can perform authorization only through Local Authentication.
7-26
OL-25957-01
Chapter 7
Step 2
Step 3
On Windows:
Step 1
Step 2
Step 3
7-27
Chapter 7
7-28
OL-25957-01
CH A P T E R
You can start and stop processes from the browser only if you have administrative privileges.
You can start and stop processes from the LMS server only if you have local administrative
privileges.
8-1
Chapter 8
Step 2
Stop:
Select the processes from this page that you want to stop.
Click Stop.
If you select specific processes, the dependent processes also stop.
Start:
Select the processes from this page that you want to start.
Click Start.
Only the selected processes are started. The dependent processes are not started.
For Windows:
For Solaris:
Caution
Do not start the daemon manager immediately after you stop it. The ports used by daemon manager will
be in use for a while even after the daemon manager is stopped. Wait for a few minutes before you restart
the daemon manager.
Step 2
Select the LMS virtual appliance from the servers listed on the left pane.
Step 3
Power off the LMS virtual appliance by right-clicking the appliance and selecting Power > Power off.
Step 4
Right-click the LMS virtual appliance and select the Edit Setting option.
Step 5
8-2
OL-25957-01
Chapter 8
Step 6
Select the Change Type button and the LSI Logic Parallel option to change the SCSI Controller type
and then select OK.
Step 7
Power on the LMS virtual appliance by right-clicking the appliance and selecting Power > Power on.
Step 8
Follow the steps mentioned in the Recovering Admin Password on Soft Appliance Installed on VMware,
page 6-32.
Step 9
Again power off the LMS virtual appliance by right-clicking the appliance and selecting Power > Power
off.
Step 10
Right-click the LMS virtual appliance and select the Edit Setting option.
Step 11
Step 12
Select the Change Type button and the LSI Logic SAS option to change the SCSI Controller type and
then select OK.
Step 13
Power on the virtual appliance and login with your new admin credentials.
8-3
Chapter 8
If the above conditions are met, and you still have problems, contact the Cisco Technical Assistance
Center.
Cisco TAC representatives may ask you to send them the installation log file in the case of LMS 4.2.
This installation log file is C:\LMS_install_YYYYMMDD_hhmmss.log, where YYYYMMDD denotes the
year, month and date of installation and hhmmss denotes the hours, minutes and seconds of installation.
Generate a report and email the generated report to Cisco TAC.
To generate the report:
Select Admin > System > Server Monitoring > Collect Server Information from the menu
Error Message
Possible Reasons
User Action
8-4
OL-25957-01
Chapter 8
Table 8-1
Error Message
Possible Reasons
User Action
Retry the download. If you still have
errors, contact your technical support
representative.
1.
2.
1.
2.
Or
function failed: DLL function
not found.
Reinstall Windows.
Or
Reinstall Windows.
8-5
Chapter 8
Table 8-1
Error Message
Possible Reasons
User Action
Or
Log in as administrator.
8-6
OL-25957-01
Chapter 8
Table 8-1
Error Message
Possible Reasons
Or
User Action
You are trying to install the Copy the installable image to a local
product from a copy of the drive or use local DVD drive.
DVD or from the DVD drive
of another system in the
network.
You are trying to install the Copy the installable image to a local
product from another system drive or use local CD drive.
in the network.
8-7
Chapter 8
Table 8-1
Error Message
Possible Reasons
User Action
You are trying to install onto Click on the directory on which you
want to install LMS .
a drive with a non-NTFS
(FAT or FAT32) file
This file system does not support system.
file security. The cluster size is The file system may not
cluster size bytes, therefore disk support security. The cluster
space requirements can be high. size may be bigger than
4096 bytes.
Choose another directory to
install LMS
The default (or selected) drive
drive has a(n) file-system-type
file system.
Or
1.
2.
3.
1.
2.
3.
8-8
OL-25957-01
Chapter 8
Table 8-1
Error Message
Possible Reasons
User Action
1.
2.
1.
2.
Click OK to proceed.
1.
2.
3.
Rerun installation.
a.
Click Yes.
Or
8-9
Chapter 8
Table 8-1
Error Message
Possible Reasons
User Action
Install Microsoft Data Access
Component (MDAC) 2.1 or higher.
Make sure that all ODBC Core
Components have the same version
number.
See the Microsoft web site for
installation instructions.
ODBC is not available from
Microsoft as a stand-alone
installation but is packaged along
with MDAC.
1.
2.
Do you want to verify that Cisco Some of the executables and Verify that files are no longer in use.
DLLs installed by Cisco
Prime LMS files are no longer
If some files are in use, stop all
Prime LMS are in use.
being used by running
processes. To do this:
processes?
1. Cancel installation.
Click Yes to verify that files are
2. Stop the Cisco Prime LMS and
no longer in use and that the
change the startup type from
installation may proceed.
Automatic to Manual.
Click No to proceed without
3. Restart the system.
verification.
4.
5.
8-10
OL-25957-01
Chapter 8
Table 8-1
Error Message
Possible Reasons
User Action
This message appears when Click OK, and ignore the message.
you install Cisco Prime
The installation will continue
LMS Common Services on a normally.
Pentium IV machine.
1.
2.
1.
2.
3.
8-11
Chapter 8
Table 8-1
Error Message
Install fails to start after clicking
the setup.exe / holds up in post
install
Possible Reasons
User Action
The self extracting exe fails with Self extract exe will extract Make minimum of 3 GB free space in
the C: or temp present directory and
the not enough disk space error. the contents into the temp
then proceed the installation.
directory and precede the
install from temp dir. When
the temp folder present
directory (c:\temp) does not
have the sufficient space to
extract the files then it will
through this error.
Install fails with the message
"Cannot load global.properties"
Temp directory is
having long path or is
not proper.
C:\Windows\SysWOW64\wbem
;C:\Windows\SysWOW64;C:\W
INDOWS\system32;C:\WINDO
WS;C:\WINDOWS\System32\
Wbem;
8-12
OL-25957-01
Chapter 8
Table 8-1
Error Message
Possible Reasons
User Action
ERROR: The following base Check whether the package has been
package image is bad:
corrupted or not by running the
<package>
below command.
pkgchk -d
<product_directory>/disk1/packages
<package>
where, <product_directory> is the
mounted media.
Example:
pkgchk -d
/data/lms30/disk1/packages
CSCOjcht
We recommend a minimum
of 8 GB swap space to install
LMS. If the server has less
than 8 GB swap space, the
installation will exit.
8-13
Chapter 8
Table 8-1
Error Message
Possible Reasons
User Action
8-14
OL-25957-01
Chapter 8
Network Topology, Layer 2 Services and User Tracking Data Migration Errors
You must:
Make sure that the server configuration and OS versions are compatible with LMS 4.2. Also, make
sure the server has enough space to do the DB backup and restore.
Check migration logs. The logs migration.log and restorebackup.log are available under:
Solaris: /var/adm/CSCOpx/log
Windows: NMSROOT\log
Note that time taken to collect inventory is directly proportional to the number of devices and the
network response time
If you encounter problems during the data migration process, do the following to clean up the temporary
files and return to the initial state:
Step 1
On Solaris
/etc/init.d/dmgtd stop
On Windows
net stop crmdmgtd
Step 2
On Solaris
NMSROOT/bin/perl
NMSROOT/objects/db/conf/configureDb.pl
action=unreg
dsn= dsn_name
dmprefix= dmprefix_name
NMSROOT/bin/perl
NMSROOT/objects/db/conf/configureDb.pl
rm -fr
NMSROOT/tempBackupData
8-15
Chapter 8
On Windows
NMSROOT\bin\perl
NMSROOT\objects\db\conf\configureDb.pl
action=unreg
dsn= dsn_name
dmprefix= dmprefix_name
NMSROOT\bin\perl
NMSROOT\objects\db\conf\configureDb.pl
rmdir
NMSROOT/tempBackupData
The following table lists the dsn_names (data source names) and dmprefixes (daemon manager
prefixes) of all functionalities in LMS 4.2.
Functionalities
dsn_name
dmprefix
Common Services
cmf
Cmf
Configuration Management
rmeng
RME
ani
ANI
Fault Management
Step 3
dfmEpm
EPM
dfmInv
INV
dfmFh
FH
ipm
Ipm
upm
UPM
On Solaris
/etc/init.d/dmgtd start
On Windows
net start crmdmgtd
8-16
OL-25957-01
Chapter 8
Server information:
To collect server information, select Admin > System > Server Monitoring > Collect Server
Information from the menu.
This allows you to quickly collect all information about the state of the system. You can send this
information as a report, to TAC for troubleshooting.
This report provides information about System configuration, environment settings, application
configuration details, process status, and product log files.
SelfTest tool:
You can select Admin > System > Server Monitoring > Selftest from the menu to invoke the
SelfTest tool.
The SelfTest tool checks the integrity and health of the system for some of the Common Services
components.
This tool helps to debug issues of corrupted files and issues related to failure of some basic
components. It runs PERL scripts that provide outputs that indicate whether a specific test is
successful.
8-17
Chapter 8
Make sure that the server configuration and OS version are compatible with LMS 4.2. Also, make
sure the server has enough space to back up the database and restore it.
Check migration logs. The logs (migration.log, restorebackup.log, rme_base.log) are available at
Solaris:
/var/adm/CSCOpx/log
Windows:
NMSROOT\log
If you get the OutOfMemoryError message, you can try to increase the available JVM (Java Virtual
Machine) heap size to work around the problem.
The JVM heap size can be configured in:
Solaris:
NMSROOT/MDC/tomcat/webapps/rme/WEB-INF/classes/com/cisco/nm/
rmeng/migration/migration.properties
Windows:
NMSROOT\MDC\tomcat\webapps\rme\WEB-INF\classes\com\cisco\nm\
rmeng\migration\migration.properties
The migration.properties file has the following parameters:
Parameter
Purpose
Default Value
VM_MIN_HEAP
128
VM_MAX_HEAP
512
RETRIES
15
You can increase the JVM heap size as much as possible (up to the available RAM). However, do
not exceed real system memory or your application will stop responding.
Sometimes, Inventory, Config and Image Management Migration may fail and display a message in
the logfile migration.log that DCRServer could not be started.
You can work around this problem by running the following command before performing migration:
Solaris:
NMSROOT/bin/perl NMSROOT/bin/dbRestoreOrig.pl
Windows:
NMSROOT\bin\perl NMSROOT\bin\dbRestoreOrig.pl
Note
For the above commands, stop the daemons before entering the commands. Start the daemons after
entering the commands.
8-18
OL-25957-01
Chapter 8
Network Topology, Layer 2 Services and User Tracking Data Migration Errors
If you encounter errors during Network Topology, Layer 2 Services and User Tracking data migration:
Windows:
NMSROOT\log\restorebackup.log
NMSROOT\lbgupdrade\CmfUpgrade.log (In case of Upgrade)
Check the contents of the backup data file, filebackup.tar. The following is the list of Network
Topology, Layer 2 Services and User Tracking related files that are backed up into the specified
backup directory.
Contents of the following folders are backed up as filebackup.tar under specified backup directory
Windows:
NMSROOT\campus\etc\cwsi\DeviceDiscovery.properties
NMSROOT\campus\etc\cwsi\ANIServer.properties
NMSROOT\campus\etc\cwsi\ut.properties
NMSROOT\campus\etc\cwsi\discoverysnmp.conf
NMSROOT\campus\etc\cwsi\datacollectionsnmp.conf
NMSROOT\campus\etc\cwsi\WlseUhic.properties
NMSROOT\campus\etc\cwsi\Snmpv3EngineParam.txt
NMSROOT\campus\etc\cwsi\UTSnmpv3EngineParam.txt
NMSROOT\campus\etc\cwsi\UTDiscoverOnTrunk.properties
NMSROOT\campus\etc\cwsi\users
NMSROOT\campus\etc\cwsi\archives
NMSROOT\campus\etc\users
NMSROOT\campus\etc\cwsi\ReportArchives
NMSROOT\campus\etc\cwsi\CMReportArchives
NMSROOT\campus\etc\cwsi\portsData.xml
NMSROOT\campus\etc\cwsi\RouterData.xml
NMSROOT\campus\etc\cwsi\vlanData.xml
NMSROOT\campus\etc\cwsi\CMHP.properties
NMSROOT\campus\etc\cwsi\rmeServerCred.dat
NMSROOT\campus\etc\cwsi\MACDetection.properties
NMSROOT\campus\etc\cwsi\OUI.properties
NMSROOT\htdocs\campus\maps
NMSROOT\campus\lib\classpath\com\cisco\nm\cm\ut\uhic\utlite\properties\utliteuhic.properties
8-19
Chapter 8
NMSROOT\campus\lib\classpath\com\cisco\nm\cm\ut\utm\properties\utm.properties
NMSROOT\campus\lib\classpath\com\cisco\nm\cm\ut\uhic\mac\properties\macuhic.properties
Solaris:
NMSROOT/campus/etc/cwsi/DeviceDiscovery.properties
NMSROOT/campus/etc/cwsi/ANIServer.properties
NMSROOT/campus/etc/cwsi/ut.properties
NMSROOT/campus/etc/cwsi/discoverysnmp.conf
NMSROOT/campus/etc/cwsi/datacollectionsnmp.conf
NMSROOT/campus/etc/cwsi/WlseUhic.properties
NMSROOT/campus/etc/cwsi/Snmpv3EngineParam.txt
NMSROOT/campus/etc/cwsi/UTSnmpv3EngineParam.txt
NMSROOT/campus/etc/cwsi/UTDiscoverOnTrunk.properties
NMSROOT/campus/etc/cwsi/users
NMSROOT/campus/etc/cwsi/archives
NMSROOT/campus/etc/users
NMSROOT/campus/etc/cwsi/ReportArchives
NMSROOT/campus/etc/cwsi/CMReportArchives
NMSROOT/campus/etc/cwsi/portsData.xml
NMSROOT/campus/etc/cwsi/RouterData.xml
NMSROOT/campus/etc/cwsi/vlanData.xml
NMSROOT/campus/etc/cwsi/CMHP.properties
NMSROOT/campus/etc/cwsi/rmeServerCred.dat
NMSROOT/campus/etc/cwsi/MACDetection.properties
NMSROOT/campus/etc/cwsi/OUI.properties
NMSROOT/htdocs/campus/maps
NMSROOT/campus/lib/classpath/com/cisco/nm/cm/ut/uhic/utlite/properties/utliteuhic.properties
NMSROOT/campus/lib/classpath/com/cisco/nm/cm/ut/utm/properties/utm.properties
NMSROOT/campus/lib/classpath/com/cisco/nm/cm/ut/uhic/mac/properties/macuhic.properties
Solaris:
NMSROOT/databases/ani/ani.db
8-20
OL-25957-01
Chapter 8
Windows:
NMSROOT\log\restorebackup.log
Check the contents of the backup data file, filebackup.tar. The following is the list of Fault
Management related files or databases that are backed up into the user-defined backup directory.
Contents of the following folders are backed up as filebackup.tar under specified backup directory.
Solaris:
NMSROOT/objects/smarts/conf
NMSROOT/objects/smarts/local/repos
NMSROOT/objects/smarts/local/logs
NMSROOT/objects/smarts/local/conf
NMSROOT/objects/dps/config
NMSROOT/setup/dfm.info
Windows:
NMSROOT\objects\smarts\conf
NMSROOT\objects\smarts\local\repos
NMSROOT\objects\smarts\local\logs
NMSROOT\objects\smarts\local\conf
NMSROOT\objects\dps\config
NMSROOT\setup\dfm.info
Note
NMSROOT\objects\dps\config will be backed up only when you migrate from LMS 3.0 December 2007
Update.
The following database files along with corresponding database transaction log files are backed up:
dfmEpm.dbContains the data of the Fault Management Event Promulgation Module
dfmInv.dbContains the data of the Fault Management Inventory
dfmFh.dbContains the data of the Fault Management Fault History
8-21
Chapter 8
Windows:
NMSROOT\databases\dfmEpm\dfmEpm.db
NMSROOT\databases\dfmInv\dfmInv.db
NMSROOT\databases\dfmFh\dfmFh.db
restorebackup.log
migration.log
ipmclient.log
ipmserver.log
ipm_base.log
Solaris
/var/adm/CSCOpx/log
Windows
NMSROOT\log
You may also encounter the following types of errors while migrating IPSLA Performance Management
data:
If Collectors are not migrated, make sure Source, target devices, and operations are properly
migrated. Also check whether Collectors configured with SNA operations are migrated.
router CLI.
If devices are not migrated, make sure that the IPM2.x backedup database contains source and target
devices.
If the Report Jobs and System Reports are not migrated, check if the job and system reports exist in
filebackup.tar in the backedup folder.
The location of filebackup.tar: backupfolder/0/ipm/filebackup.tar
8-22
OL-25957-01
Chapter 8
NMSROOT/tomcat/webapps/ipm/system_reports
Solaris: Jobs folder in var/adm/CSOCpx/files/ipm/jobs and System Reports
NMSROOT/tomcat/webapps/ipm/system_reports
If the backup directory of IPM2.6 (part of LMS 2.6) does not contain all required files, make sure
it contains the following files:
ipmdb.db
.dbPassword
ipmdb.tmpl
ipm.env
If the backup directory of IPM4.0 (part of LMS 3.0) or IPM4.0.1 (part of LMS 3.0 December 2007
Update) does not contain all required files, make sure it contains the following files:
ipm.db
filebackup.tar
ipm.tmpl
ipmdb.tmpl
restorebackup.log
upm_process.log
Solaris:
/var/adm/CSCOpx/log
Windows:
NMSROOT\log
You may also encounter the following types of errors while migrating Device Performance Management
data:
If pollers, templates, or thresholds are not migrated properly, make sure the Device Performance
Management backedup database contains the related data.
If reports are not migrated, make sure filebackup.tar contains the reports in
NMSROOT/MDC/tomcat/webapps/upm/reports folder.
If threshold scripts are not migrated, make sure filebackup.tar contains the reports in
NMSROOT/hum/thresholdscripts.
If Poller failures are observed, make sure the devices are SNMP reachable from Device Performance
Management server.
8-23
Chapter 8
Where can I find the install log files for LMS 4.2?
I have LMS 3.2 applications installed on different servers. Can I migrate data from these multiple
servers to one LMS 4.2 server?
I have LMS 3.2 SP1 installed on Windows 2003 Server. I want to upgrade the OS to Windows 2008
Server, and also upgrade to LMS 4.2. In what order should I perform these upgrades?
I have been running LMS 4.2 for sometime, and have collected a lot of data. I would like to restore
an older LMS 3.2 SP backup, and merge the data from the current system and the backup. Is this
possible?
Can I install LMS 4.2 with Internet Information Services (IIS) enabled?
Does LMS 4.2 support virtual machines, such as VMware and VirtualPC?
I am currently using a licensed version of LMS 4.2 on Solaris. I want to migrate to Windows. Do I
need to get a new license for LMS 4.2 on Windows?
When should I install other Network Management Systems (such as HP OpenView Network Node
Manager, Netview)?
b.
Enter the shell password. This will be same as the sysadmin password that you provided during
installation.
c.
8-24
OL-25957-01
Chapter 8
Q. Where can I find the install log files for LMS 4.2?
A. On Solaris and Soft Appliance, if errors occur during installation, check the installation log file
Server, and also upgrade to LMS 4.2. In what order should I perform these upgrades?
A. You must:
a.
Upgrade your Operating System to Windows 2008 (SP1 & SP2) R2 Standard & Enterprise edition
or Windows 2008 (SP1)Server.
b.
Upgrade LMS 3.2 SP1 to LMS 4.2 on Windows 2008 (SP1 & SP2) R2 Standard & Enterprise edition
or Windows 2008 (SP1)Server.
Q. I have been running LMS 4.2 for sometime, and have collected a lot of data. I would like to restore
an older LMS 3.2 SP backup, and merge the data from the current system and the backup. Is this
possible?
A. No. After a backup is restored, all data that is currently in the running system is replaced with the
impact on LMS:
http://www.microsoft.com/technet/security/bulletin/MS10-044.mspx
Q. Is LMS 4.2 supported on 64-bit native systems?
A. Yes, LMS 4.2 is supported on native 64-bit systems. See Operating System Requirements for more
information.
Q. Can I install LMS 4.2 with Internet Information Services (IIS) enabled?
A. Yes, you can install. If you click No you must stop IIS services before installing LMS 4.2. If you
click Yes you must change the port from 443 to any other during installation. Also, you must ensure
that no other application or process is utilizing this port.
Q. Which TCP and UDP ports does LMS 4.2 use?
A. See LMS 4.2 Port Usage for details.
8-25
Chapter 8
Q. Does LMS 4.2 support virtual machines, such as VMware and VirtualPC?
A. Yes, LMS 4.2 supports VMware. See Server Requirements on Windows Systems, for more
information.
Q. Can I install LMS 4.2 with Windows Domain Controller enabled?
A. No, you must disable Windows Domain Controller before installing LMS 4.2.
Q. Is LMS 4.2 supported on Solaris x86 (on the x86 CPU)?
A. No, LMS 4.2 is not supported on Solaris x86.
Q. Is LMS 4.2 supported on multi-homed server?
A. Yes, LMS 4.2 is supported on multi-homed server.
A multi-homed machine is a machine that has multiple NIC cards, each configured with different IP
addresses. To run LMS 4.2 on a multi-homed machine, there are two requirements:
All IP addresses must be configured in DNS.
Owing to restrictions with CORBA, only one IP address can be used by the client or browser to
access the server. You must select one IP address as the external address, with which the client
will log into the server.
Q. How do I check the application versions of LMS 4.2?
A. You can check the application versions by selecting Admin > System > Software Center >
Software Update.
If you have installed a licensed version of LMS 4.2, you can check the LMS version in the Products
Installed table (Admin > System > Software Center > Software Update). The LMS version should
be 4.0.
Q. Can I migrate data from Solaris to Windows and vice versa?
A. No, you cannot migrate data between operating systems.
Q. Can LMS 4.2 co-exist with other CiscoWorks applications?
A. No, LMS 4.2 cannot co-exist with any other CiscoWorks applications.
Q. I am currently using a licensed version of LMS 4.2 on Solaris. I want to migrate to Windows. Do I
Manager, Netview)?
A. You must install other Network Management Systems before installing Cisco Prime LMS 4.2. See
8-26
OL-25957-01
A P P E N D I X
Note
For information on the Installation of LMS 4.2, see Performing Installation of LMS 4.2.
This appendix contains:
Password Information
Settings
Value
Destination folder
Login Password
(Mandatory)
Database Password
A-1
Appendix A
On a Windows system, if you are using HPOV as your third party NMS application, you would require
the IIS service to be enabled for HPOV to install and run. The IIS web server runs on SSL port 443,
which is the default port for the LMS web server when installing LMS. To avoid a conflict, you should
change the SSL port number of the LMS web server from 443 to another port that is available, and that
has a number in the range 1026 to 65535, except 6000. Port number 6000 is reserved by Firefox, if you
enter 6000 as the SSL port number, after installation (for all the three operating systems), you will not
be able to launch LMS using the Firefox browser.
Settings
Value
Backup folder
Enter a folder for the backup data. You can also browse and select a folder.
You may change the passwords for the admin and guest users. To keep the
existing passwords, leave the fields blank.
(Optional)
In the upgrade scenario, you cannot enter the Eval license inputs. Only
Purchase license inputs are applicable.
For more information on passwords, see Password Information
If you do not enter a password, the setup program will generate a random
password for you. If casuser does not exist, it will be created.
(Optional)
A-2
OL-25957-01
Appendix A
Table A-2
Settings
Value
HTTPS port
Administrators
e-mail address
SMTP server
name
(Optional)
You may change the Self-signed Certificate information. By default, the
installation program uses the existing Self-Signed Certificate information.
Country Code
State
City
Organization
Organization
Unit Name
E-mail Address
If you want to generate a new certificate, uncheck the Keep Existing Certificate
check box, and enter the country code, state, city, company, organization, and
host name for HTTPS.
You must enter the host name. You can leave the other fields blank.
Settings
Value
Backup folder
Enter a folder for the backup data. You can also browse and select a folder.
Destination folder
You may change the login and database passwords. To keep the existing
passwords, leave the fields blank.
Password Information
This section contains:
A-3
Appendix A
Password Information
This environment variable set is applicable to the current working shell only.
Now, you can change the password using the LMS user password recovery utility.
Step 2
Step 3
Step 2
A-4
OL-25957-01
Appendix A
Step 2
A-5
Appendix A
Password Information
Step 2
Select Admin > System > User Management > Local User Setup.
The Local User Setup page appears.
Step 3
Step 4
Step 5
Step 6
Step 7
Click OK.
resetCasuser.exe.
Step 2
1.
2.
3.
Exit.
Step 3
A-6
OL-25957-01
Appendix A
Step 2
Right click on the LMS Virtual Appliance VM, then select Guest > Install/Upgrade VMware Tools
and click OK.
Step 3
Step 4
Step 5
Step 6
Step 8
Change the directory to vmware-tools-distrib and run the vmware-install.pl PERL script to install
VMware tools.
cd vmware-tools-distrib
./vmware-install.pl
Note
Step 9
It is normal for the console screen to go blank for a short time during the installation when the
display size changes.
Some warnings or errors are normal, when a files does not exist.
Your network service might restart after installation. So the recommendation is to invoke this
command from the console and not remotely.
A-7
Appendix A
Step 10
Manually end the VMware tools installation process. To end the process, click VM in the virtual
machine menu, then click Guest > End VMware Tools Install.
The Install/Upgrade Tools window appears.
Step 11
Note
LMS 4.2 supports only the binary installation of VMware tools in a LMS Virtual Appliance.
Few benefits of installing VMware tools in LMS Virutal Appliance is as follows.
Passes messages from the host operating system to the guest operating system.
Sends a heartbeat to a VMware Server, if you use the virtual machine with VMware server.
A-8
OL-25957-01
A P P E N D I X
Understanding UTU
B-1
Appendix B
Understanding UTU
Understanding UTU
User Tracking Utility (UTU) allows users with Help Desk access to search for users, hosts, or IP Phones
discovered by LMS. UTU comprises a server-side component and a client utility.
UTU is supported on LMS 3.0 (Campus Manager 5.0.6), LMS 3.1 (Campus Manager 5.1.4), and
LMS 3.2 (Campus Manager 5.2.1). To use UTU in LMS 4.2, Network Topology, Layer 2 Services and
User Tracking must be enabled and accessible through the network.
UTU 2.0 supports silent installation mode for easy deployment. It supports communication with LMS
server in Secure Sockets Layer (SSL) mode.
The following are the list of features supported in the CiscoWorks User Tracking Utility 2.0 release:
Windows Vista Support
Earlier, User Tracking Utility did not work on Windows Vista client systems because of library conflicts.
UTU 2.0 is built on Microsoft .Net Framework and Windows Presentation Foundation (WPF). With this,
UTU 2.0 now works on Windows Vista client systems
Support for Phone Number Search
In this release, UTU supports searching phone numbers in addition to existing search criteria.
Memory (RAM)
Additional
required software
Windows 2008
Windows Vista
512 MB
LMS 3.0 (Campus Manager 5.0.6), or LMS 3.1 (Campus Manager 5.1.4), or
LMS 3.2 (Campus Manager 5.2.1), or LMS 4.2 (Network Topology, Layer 2
Services and User Tracking)
Network
Connectivity
LMS 3.0 (Campus Manager 5.0.6) or LMS 3.1 (Campus Manager 5.1.4) or LMS
3.2 (Campus Manager 5.2.1) or LMS4.0/4.0.1/4.1/4.2 (Network Topology, Layer
2 Services and User Tracking) must be running, and accessible through the network
B-2
OL-25957-01
Appendix B
Step 2
Select a product release version from the Latest Releases folder and locate the software update to
download.
Step 3
Step 4
Click the Download Now button to download and save the device package file to any local directory on
Server.
Step 5
B-3
Appendix B
a s f1 file-location \setup.iss
where
exe-location is the directory where you have extracted the
CiscoWorksUserTrackingUtility2.0.exe file
file-location is the directory where you have the setup.iss file.
Do not use space after the -f1 option. Use the complete path for file-location.
For example, if the install directory for UTU is c:\utu, enter the following at the command prompt:
c:\utu\CiscoWorksUserTrackingUtility2.0.exe -a -s -f1c:\utu\setup.iss
The setup.log file is created during the installation in the same directory where you have extracted the
setup.iss file.
You should see the setup.log file to check the installation completion status.
The value of the ResultCode attribute in the setup.log informs you whether the installation has
completed successfully. The value 0 denotes that the UTU installation in silent mode is successful.
When the value of the ResultCode attribute is other than 0, you must install UTU again.
Step 2
Step 3
Step 4
Click Next.
A warning message appears if you have not installed .Net Framework 3.5 SP1.
You can install .Net Framework 3.5 SP1 after terminating the current UTU installation or before
completing the current UTU installation.
Step 5
Click Next.
A confirmation message appears.
B-4
OL-25957-01
Appendix B
Step 6
Click Yes.
The Choose Destination Location dialog box appears. By default, UTU is installed in the directory
C:\Program Files\CSCOutu2.0.
Note
If you have installed .Net Framework 3.5 SP1 already on the system, the installer directs you to
the Choose Destination dialog box, when you click Next in the User Tracking Utility Welcome
screen.
If you click No in the confirmation message, the warning message appears again stating that you have
not installed .Net Framework 3.5 SP1.
You can download and install .Net Framework 3.5 SP1. and then continue with the UTU installation.
Step 7
b.
Start > Programs > CiscoWorks UTU 2.0 > CiscoWorks User Tracking Utility 2.0
Or
The UTU band appears. See Figure B-1for UTU 2.0 band.
You can also find an icon in the task bar. You can use this icon to restore the UTU band when minimized.
B-5
Appendix B
Figure B-1
1 - Settings Icon
2 - Minimize icon
3 - Close icon
After a system restart and during the startup, the system launches the UTU automatically.
b.
Click Settings.
Enter the name or IP Address of the server on which Campus Manager (for releases earlier than LMS
4.0), or LMS 4.2 is installed.
Step 3
Step 4
B-6
OL-25957-01
Appendix B
Figure B-2
Enabling SSL
You can modify the port number if required. See Figure B-2.
Figure B-3
Step 5
Enabling SSL
Step 6
Step 7
Select the Remember me on this computer checkbox if you want the client system to remember your
credentials.
The credentials are preserved only for the current user of Windows system. The credentials are not
available when you log into the Windows system with a different user name.
Step 8
B-7
Appendix B
Note
Step 1
Step 2
User name
MAC Address
Phone number
Enter any value related to user name, host name, device name, IP Address, Phone number or the MAC
Address in the UTU search field.
For example, you can enter 10.77.208 in the search field.
Step 4
Press Enter.
If your server is not SSL enabled, go to Step 7.
When you query for data from an SSL enabled server, the Certificate Viewer dialog box appears. See
Figure B-4.
B-8
OL-25957-01
Appendix B
Figure B-4
Step 5
Certificate Viewer
B-9
Appendix B
Figure B-5
Certificate Details
You can click Summary to go back to the Certificate Viewer dialog box.
Step 6
Click Yes in the Certificate Viewer dialog box or Certificate Details dialog box to accept and store the
certificate.
SSL connection is established with the server.
If you click No, the certificate is not stored and no connection is established with the server.
Note
Step 7
The Certificate Viewer dialog box appears only for the first time configuration. If you had clicked Yes
the first time, you are not prompted to store the certificate during subsequent sessions.
Click the X Record(s) Found button to launch the results window.
X denotes the number of matches found. See Figure 6.
For example, if there 4 matches found, the UTU Search band displays 4 Record(s) Found.
B-10
OL-25957-01
Appendix B
Figure 6
UTU search returns top 500 records only if the number of matches exceed 500. You must refine your
search if you want better and accurate results.
Step 8
Copy to Clipboard, where you can copy the selected search result record.
Copy All to Clipboard, where you can copy all the search result records.
For a selected search result record, the Results window displays the details as described in:
Details for Each Entry in Results Window For a User or Host Search
Entry
Description
User Name
MAC Address
Host IP Address
Host Name
Subnet
Subnet Mask
Device name
Device IP Address
VLAN
Port
Port Description
Port State
Port Speed
B-11
Appendix B
Table B-2
Details for Each Entry in Results Window For a User or Host Search (continued)
Entry
Description
Port Duplex
Last Seen
Date and time when User Tracking last found an entry for this user or host
in a switch. Last Seen is displayed in the format yyyy/mm/dd hh:mm:ss.
Table B-3
Details for Each Entry in Results Window For a Phone Number Search
Entry
Description
Phone Number
IP Phone number
MAC Address
Phone IP Address
CCM Address
Status
Phone Type
Model of the phone. Can be SP30, SP30+, 12S, 12SP, 12SPplus, 30SPplus,
30VIP, SoftPhone, or unknown.
Phone Description
Device Name
Device IP Address
Port
Port Description
Last Seen
Date and time when User Tracking last found an entry. Last Seen is
displayed in the format yyyy/mm/dd hh:mm:ss.
B-12
OL-25957-01
Appendix B
Figure B-7
Note
The search results for the value you enter in the search field depends on the default search
criteria.
xxxx.xxxx.xxxx
xx:xx:xx:xx:xx:xx
xxxxxxxxxxxx
xx-xx-xx-xx-xx-xx
B-13
Appendix B
Select Start > Programs > CiscoWorks UTU 2.0 > Uninstall CiscoWorks User Tracking Utility 2.0
from the windows task bar.
The Uninstallation wizard appears and prompts you to confirm the UTU uninstallation.
Step 2
Click Yes.
The Uninstallation continues.
Step 3
B-14
OL-25957-01
A P P E N D I X
Warning
Do not install Remote Syslog Collector on a system that has LMS 4.2 already installed.
The Remote Syslog Collector and Syslog Analyzer Service on the LMS server uses SSL sockets to
communicate with each other.
It functions as follows:
1.
At startup, the Remote Syslog Collector looks for Syslog Analyzers already subscribed on the LMS
Server and requests for the latest filter definitions.
If the Syslog Analyzer is not reachable when queried, the Remote Syslog Collector logs all emblem
compliant syslogs in the specified downtime file after filtering.
The Syslog Collector Properties file is available at these locations:
On Solaris and Soft Appliance:
/opt/CSCOpx/MDC/tomcat/webapps/rme/WEB-INF/classes/com/cisco/nm/rmeng/csc/data/
Collector.properties
On Windows:
NMSROOT\MDC\tomcat\webapps\rme\WEB-INF\classes\com\cisco\nm\rmeng\csc\data\
Collector.properties
If the Syslog Analyzer responds with the latest filters, the Remote Syslog Collector applies filters
and forwards syslogs to the Syslog Analyzer.
2.
At startup, the Syslog Analyzer tries to connect to all the subscribed Remote Syslog Collectors by
passing the latest filters.
To subscribe or unsubscribe from a Remote Syslog Collector, select Admin > Collection Settings >
Syslog > Syslog Collector Status from the menu.
After the Remote Syslog Collector connects to the LMS 4.2 Server, the Remote Syslog Collector entry
is added to the Collector Status window of the LMS 4.2 Server.
To view the status of the subscribed Syslog Collector, select Admin > Collection Settings > Syslog >
Syslog Collector Status.
C-1
Appendix C
This section describes how to set up Syslog between RSAC and LMS 4.2. This involves:
Table C-1
Table C-1 provides the server requirements for Remote Syslog Collector on Solaris.
Table C-2 provides the server requirements for Remote Syslog Collector on Windows.
Table C-3 provides the server requirements for Remote Syslog Collector on Soft Appliance.
Requirement Type
Minimum Requirements
Hardware
UltraSPARC CPU
Memory (RAM)
Operating System
Solaris 10
Browser
Internet Explorer 8.0 and 9.0 Standards Mode (Press F12 and select
Standards Mode)
Table C-2
Requirement Type
Minimum Requirements
Hardware
Memory (RAM)
Operating System
Browser
Internet Explorer 8.0 and 9.0 Standards Mode (Press F12 and select
Standards Mode)
C-2
OL-25957-01
Appendix C
Table C-3
Requirement Type
Minimum Requirements
Virtualization Systems
Memory (RAM)
80 GB
Operating System
Browser
Internet Explorer 8.0, and 9.0 Standards Mode (Press F12 and select
Standards Mode)
Note
Hyper V Virtualization
C-3
Appendix C
Installing on Solaris
Installing on Windows
If you install LMS Service Pack on the LMS server, you must install the same Service Pack on the
RSAC server.
The LMS Service Pack versions must be same in the LMS Server and RSAC Server.
LMS 4.2 should not be installed on the server where you need to install the Remote Syslog
Collector. (If LMS 4.2 is installed, the Syslog Collector is installed by default).
Installing on Solaris
To install the Remote Syslog Collector on a Solaris system:
Step 1
Step 2
Step 3
After installation, you need to configure the collector.properties file if required. If not, you can use the
defaults. See Understanding the Syslog Collector Properties File.
C-4
OL-25957-01
Appendix C
Installing on Windows
To install the Remote Syslog Collector on a Windows system:
Step 1
Step 2
Step 3
After Installation, you need to configure the collector.properties file if required. If not, you can use the
defaults. See Understanding the Syslog Collector Properties File.
Navigate to the RSAC folder on the LMS 4.2 DVD. Transfer the Remote_syslog_Collector_5_2.ova file
to the VMware server where you want to deploy the OVA image.
Step 2
Follow the installation steps for installing the LMS Soft Appliance OVA file in the section Download
Instructions for LMS 4.2 software - OVA Image.
After the installation of Remote Syslog Collector, select Admin > System > Software Center >
Software Update to verify the installation. Remote Syslog Collector should be listed.
To install the Remote Syslog Collector on a LMS Soft Appliance system (ISO image):
Step 1
Navigate to the RSAC folder on the LMS 4.2 DVD. Transfer the Remote_syslog_Collector_5_2.iso file
to the VMware server where you want to deploy the ISO image.
Step 2
Follow the installation steps for installing the LMS Soft Appliance ISO file in the section Installing LMS
4.2 Soft Appliance on VMware.
After the installation of Remote Syslog Collector, select Admin > System > Software Center >
Software Update to verify the installation. Remote Syslog Collector should be listed.
C-5
Appendix C
Download the Peer certificate from the system where Remote Syslog Collector is running.
Step 2
Upload the Peer certificate to the system where Remote Syslog Collector is running.
Step 3
Select Admin > Collection Settings > Syslog > Syslog Collector Status.
The Collector Status dialog box appears with this information:
Column
Description
Name
Update Time
Date and time of the last update. By default, this dialog box is updated every 5
minutes.
Time and time zone are those of the LMS Server.
Step 4
Uptime
Time duration for which the Syslog Collector has been up.
Forwarded
Dropped
Invalid
Filtered
Number of filtered messages. Filters are defined with the Define Message Filter
option (select Admin > Network > Notification and Action Settings > Syslog
Message Filters from the menu). For details about defining filters, see
Administration of Cisco Prime LAN Management Solution 4.2.
Received
Test Collector
Subscription
Subscribe
Unsubscribe
Select the Syslog collector and click Unsubscribe to unsubscribe the Syslog collector.
Click Subscribe.
The Subscribe Collector dialog box appears.
Step 5
Enter the address of the Common Syslog Collector to which you want to subscribe to.
Step 6
Click OK.
The Syslog Analyzer is subscribed the Syslog Collector that you specified. This can be either the Syslog
Collector on the LMS server, or a remotely installed Syslog Collector.
C-6
OL-25957-01
Appendix C
SyslogCollector
Uninstallation on Windows
Uninstallation on Solaris
Uninstallation on Windows
To uninstall on a Windows system:
Step 1
Step 2
Step 3
Uninstallation on Solaris
To uninstall on a Solaris system:
Step 1
Step 2
NMSROOT/bin/uninstall.sh
C-7
Appendix C
/opt/CSCOpx/MDC/tomcat/webapps/rme/WEB-INF/classes/com/cisco/nm/rmeng/csc/data/
Collector.properties
On Windows:
NMSROOT\MDC\tomcat\webapps\rme\WEB-INF\classes\com\cisco\nm\rmeng\csc\data\
Collector.properties
The following table describes the Syslog Collector Properties file:
Timezone-Related
Properties
TIMEZONE
Description
The timezone of the machine where the Syslog Collector is running. Enter the
correct abbreviation for the timezone. For example, the time zone for India is
IST.
For the correct Timezone abbreviation, see the Timezone file in the following
locations:
/opt/CSCOpx/MDC/tomcat/webapps/rme/WEB-INF/classes/com/cisco/nm/
rmeng/fcss/data/TimeZone.lst
On Windows:
NMSROOT\MDC\tomcat\webapps\rme\WEB-INF\classes\com\cisco\nm\
rmeng\fcss\data\TimeZone.lst
COUNTRY_CODE
TIMEZONE_FILE
The path of the Timezone file. This file contains the offsets for the time zones.
After installing the Syslog Collector, ensure that the offset specified in this file
is as expected. If it is not present or is incorrect, you can add the Timezone
offset according to the convention.
The default paths are:
/opt/CSCOpx/MDC/tomcat/webapps/rme/WEB-INF/classes/com/
cisco/nm/rmeng/fcss/data/TimeZone.lst
On Windows:
NMSROOT\MDC\tomcat\webapps\rme\WEB-INF\classes\com\
cisco\nm\rmeng\fcss\data\TimeZone.lst
C-8
OL-25957-01
Appendix C
Timezone-Related
Properties
Description
General Properties
SYSLOG_FILES
Filename and location of the file from which syslog messages are read.
On Windows:
NMSROOT\log\syslog.log
DEBUG_CATEGOR
Y_NAME
DEBUG_FILE
Filename and location of the Syslog Collector log file containing debug
information:
On Windows:
NMSROOT\log\CollectorDebug.log
DEBUG_LEVEL
Warning
Debug
Error
Information
DEBUG_MAX_FILE The maximum size of the log file containing the debug information.
_SIZE
The default is set to 5 MB.
If the file size exceeds the limit that you have set, Syslog Collector writes to
another file, based on the number of backup files that you have specified for
the DEBUG_MAX_BACKUPS property.
For example, if you have specified the number of backups as 2, besides the
current log file, there will be two backup files, each 5MB in size. When the
current file exceeds the 5 MB limit, Syslog Collector overwrites the oldest of
the two backup files.
DEBUG_MAX_
BACKUPS
The number of backup files that you require. The size of these will be the value
that you have specified for the DEBUG_MAX_FILE_SIZE property.
C-9
Appendix C
Timezone-Related
Properties
Description
Miscellaneous Properties
READ_INTERVAL_
IN_SECS
QUEUE_CAPACITY The size of the internal buffer, for queuing syslog messages.
The default is set to 100000.
PARSER_FILE
The file that contains the list of parsers used while parsing syslog messages.
On Windows:
NMSROOT\MDC\tomcat\webapps\rme\WEB-INF\classes\com\cisco\nm\
rmeng\fcss\data\FormatParsers.lst
SUBSCRIPTION_
DATA_FILE
The Syslog Collector data file that contains the information about the Syslog
Analyzers that are subscribed to the Collector.
On Solaris:
/opt/CSCOpx/MDC/tomcat/webapps/rme/WEB-INF/classes/com/
cisco/nm/rmeng/csc/data/Subscribers.dat
On Windows:
NMSROOT\MDC\tomcat\webapps\rme\WEB-INF\classes\com\cisco\nm\
rmeng\csc\data\Subscribers.dat
FILTER_THREADS
The number of threads that operate at a time for filtering syslog messages. The
default is set to 1.
COLLECTOR_POR
T
The default port of the Syslog Collector. The default is set to 4444.
The port where the collector listens for registration requests from Syslog
Analyzers.
C-10
OL-25957-01
A P P E N D I X
Definition
Brazil / DeNoronha
FNT
-2:00
Brazil / West
BST
+1:00
Brazil/Acre
AMT
Amazon Time
-4:00
Brazil/East
EST
-3:00
GMT0
AZOST
-1:00
Iceland
GMT
0:00
EET
EET
+2:00
PST
-8:00
US/Indiana-Starke
EST
-5:00
US/Samoa
SST
-11:00
US/Arizona
MST
-7:00
US/East-Indiana
EDT
-5:00
US/Central
CST
-6:00
US/Eastern
EST
-5:00
US/Mountain
MST
-7:00
US/Alaska
AST
-9:00
US/Hawaii
HAST
-10:00
US/Aleutian
HAST
-10:00
US/Michigan
EDT
-5:00
MST
MST
-7:00
CET
CET
+1:00
Asia/Chungking
CST
+8:00
Asia/Bangkok
ICT
Indochina Time
+7:00
Asia/Kashgar
CST
+8:00
D-1
Appendix D
Table D-1
Definition
Asia/Macao
CST
+8:00
Asia/Yakutsk
YAKT
Yakutsk Time
+9:00
Asia/Riyadh
AST
+3:00
Asia/Makassar
WITA
+8:00
Asia/Shanghai
CCT
+8:00
Asia/Kuala_Lumpur
MYT
Malaysia Time
+8:00
Asia/Hovd
HOVT
Hovd Time
+7:00
Asia/Qyzylorda
QYZT
Qyzylorda Time
+6:00
Asia/Harbin
CST
+8:00
Asia/Tel_Aviv
IDT
+3:00
Asia/Anadyr
MAGST
+12:00
Asia/Istanbul
EEST
+2:00
Asia/Jakarta
WIT
+7:00
Asia/Aqtobe
AQTT
Aqtobe Time
+5:00
Asia/Aden
AST
+3:00
Asia/Kuwait
AST
+3:00
Asia/Manila
PHT
Philippine Time
+8:00
Asia/Yerevan
AST
+5:00
Asia/Seoul
KST
+9:00
Asia/Taipei
CST
+8:00
Asia/Bahrain
AST
+3:00
Asia/Jerusalem
IDT
+3:00
Asia/Riyadh89
AST
+3:00
Asia/Ho_Chi_Minh
ICT
Indochina Time
+7:00
Asia/Saigon
ICT
Indochina Time
+7:00
Asia/Dubai
GST
+4:00
Asia/Tokyo
JST
+9:00
Asia/Omsk
OMSST
+7:00
Asia/Calcutta
IST
+5:30
Asia/Kabul
AFT
Afghanistan Time
+4:30
Asia/Karachi
PKT
+5:00
Asia/Damascus
EEST
+2:00
Asia/Singapore
SGT
Singapore Time
+8:00
Asia/Samarkand
UZT
Uzbekistan Time
+5:00
Asia/Dili
TLT
+9:00
D-2
OL-25957-01
Appendix D
Table D-1
Definition
Asia/Dhaka
BST
+6:00
Asia/Vientiane
ICT
Indochina Time
+7:00
Asia/Aqtau
AQTT
Aqtobe Time
+5:00
Asia/Thimbu
BTT
Bhutan Time
+6:00
Asia/Ashkhabad
TMT
Turkmenistan Time
+5:00
Asia/Yekaterinburg
YEKST
+6:00
Asia/Kamchatka
PETST
+12:00
Asia/Macau
CST
+8:00
Asia/Oral
ORAT
ORAT
+5:00
Asia/Ashgabat
TMT
Turkmenistan Time
+5:00
Asia/Novosibirsk
NOVST
+7:00
Asia/Thimphu
BTT
Bhutan Time
+6:00
Asia/Ulan_Bator
IRKST
+9:00
Asia/Nicosia
EEST
+2:00
Asia/Phnom_Penh
ICT
Indochina Time
+7:00
Asia/Irkutsk
IRKST
+9:00
Asia/Urumqi
CST
+8:00
Asia/Kuching
MYT
Malaysia Time
+8:00
Asia/Kolkata
IST
+5:30
Asia/Vladivostok
VLAST
+11:00
Asia/Dacca
BST
+6:00
Asia/Baku
AZST
+5:00
Asia/Tashkent
UZT
Uzbekistan Time
+5:00
Asia/Rangoon
MMT
Myanmar Time
+6:30
Asia/Dushanbe
TJT
Tajikistan Time
+5:00
Asia/Hong_Kong
HKT
+8:00
Asia/Magadan
MAGST
+12:00
Asia/Krasnoyarsk
KRAST
+8:00
Asia/Katmandu
NPT
Nepal Time
+5:45
Asia/Gaza
EEST
+2:00
Asia/Brunei
BNT
+8:00
Asia/Pyongyang
KST
+9:00
Asia/Colombo
IST
+5:30
Asia/Choibalsan
ULAT
Ulaanbaatar Time
+8:00
Asia/Bishkek
KGT
Kyrgyzstan Time
+6:00
D-3
Appendix D
Table D-1
Definition
Asia/Baghdad
AST
+3:00
Asia/Tehran
IRDT
+4:30
Asia/Chongqing
CST
+8:00
Asia/Tbilisi
GET
+4:00
Asia/Amman
EEST
+2:00
Asia/Ujung_Pandang
WITA
+8:00
Asia/Riyadh
AST
+3:00
Asia/Pontianak
WIB
+7:00
Asia/Muscat
GST
+4:00
Asia/Sakhalin
SAST
+10:00
Asia/Beirut
EEST
+2:00
Asia/Qatar
AST
+3:00
Asia/Ulaanbaatar
ULAT
Ulaanbaatar Time
+8:00
Asia/Kathmandu
NPT
Nepal Time
+5:45
Asia/Almaty
ALMT
Alma-Ata Time
+6:00
Asia/Riyadh87
AST
+3:00
Asia/Jayapura
WIT
+9:00
PRC
MST
-7:00
Japan
JST
+9:00
Antarctica/DumontDUrvill
e
DDUT
Dumont-d`Urville Time
+10:00
Antarctica/Palmer
NZST
+12:00
Antarctica/Mawson
MAWT
Mawson Time
+5:00
Antarctica/Vostok
VOST
Vostok Time
+6:00
Antarctica/Casey
CAST
Casey Time
+8:00
Antarctica/Syowa
SYOT
+3:00
Antarctica/McMurdo
NZST
+12:00
Antarctica/Rothera
ROTT
Rothera Time
-3:00
Antarctica/Davis
DAVT
Davis Time
+7:00
Antarctica/South_Pole
NZST
+12:00
Pacific/Tarawa
GILT
+12:00
Pacific/Gambier
GAMT
Gambier Time
+9:00
Pacific/Port_Moresby
PGT
+10:00
Pacific/Kiritimati
LINT
+14:00
Pacific/Nauru
NRT
+12:00
Pacific/Rarotonga
CKT
-10:00
D-4
OL-25957-01
Appendix D
Table D-1
Definition
Pacific/Galapagos
GALT
Galapagos Time
-6:00
Pacific/Yap
YAPT
Yap Time
+10:00
Pacific/Wake
WAKT
+12:00
Pacific/Auckland
NZST
+12:00
Pacific/Samoa
SST
-11:00
Pacific/Apia
WST
-11:00
Pacific/Majuro
MHT
+12:00
Pacific/Efate
VUT
Vanuata Time
+11:00
Pacific/Guam
ChST
+10:00
Pacific/Chatham
CHAST
+12:45
Pacific/Honolulu
HAST
-10:00
Pacific/Pago_Pago
SST
-11:00
Pacific/Kwajalein
MHT
+12:00
Pacific/Wallis
WFT
+12:00
Pacific/Norfolk
NFT
Norfolk Time
+11:30
Pacific/Niue
NUT
Niue Time
-11:00
Pacific/Kosrae
KOST
+11:00
Pacific/Pitcairn
PST
-8:00
Pacific/Midway
SST
-11:00
Pacific/Funafuti
TVT
Tuvalu Time
+12:00
Pacific/Saipan
ChST
+10:00
Pacific/Marquesas
MART
Marquesas Time
-9:30
Pacific/Tongatapu
TOST
+13:00
Pacific/Easter
EAST
-6:00
Pacific/Noumea
NCT
+11:00
Pacific/Ponape
PONT
+11:00
Pacific/Guadalcanal
SBT
+11:00
Pacific/Fakaofo
TKT
Tokelau Time
-10:00
Pacific/Tahiti
TAHT
Tahiti Time
-10:00
Pacific/Palau
PWT
Palau Time
+9:00
Pacific/Johnston
HDT
-9:30
Pacific/Enderbury
PHOT
+13:00
Pacific/Fiji
FJT
Fiji Time
+12:00
Pacific/Truk
TRUT
Truk Time
+10:00
PST8PDT
PDT
-7:00
D-5
Appendix D
Table D-1
Definition
Hongkong
HKT
+8:00
EST5EDT
EDT
-4:00
GMT
GMT
+0:00
Mideast/Riyadh88
AST
+3:00
Mideast/Riyadh89
AST
+3:00
Mideast/Riyadh87
AST
+3:00
W-SU
MSD
+3:00
Navajo
MDT
-7:00
GB
BST
+1:00
NZ
NZST
+12:00
UCT
UCT
Universal Time
+0:00
CST6CDT
CDT
-6:00
Jamaica
EST
-5:00
Universal
UCT
Universal Time
+0:00
Portugal
WEST
+1:00
Cuba
CDT
-5:00
Arctic/Longyearbyen
CEST
+1:00
Turkey
EEST
+2:00
GB-Eire
BST
+1:00
HST
HAST
-10:00
UTC
Universal
Universal
+0:00
Egypt
EET
+2:00
Singapore
SGT
Singapore Time
+8:00
Eire
IST
+1:00
America/Yellowknife
MDT
-7:00
America/Yakutat
YDT
-8:00
America/Belem
BRT
Braslia time
-3:00
America/Eirunepe
ACST
+9:30
America/Nipigon
EDT
-4:00
America/Managua
CST
-6:00
America/Rankin_Inlet
CDT
-6:00
America/Fort_Wayne
EDT
-5:00
America/Santiago
ART
Argentina Time
-3:00
America/Port-au-Prince
EST
-5:00
America/Lima
PET
Peru Time
-5:00
D-6
OL-25957-01
Appendix D
Table D-1
Definition
America/Merida
CDT
-6:00
America/Cambridge_Bay
MDT
-7:00
America/Buenos_Aires
ART
Argentina Time
-3:00
America/Aruba
AST
-4:00
America/Ensenada
PDT
-8:00
America/Winnipeg
CDT
-6:00
America/Hermosillo
MST
-7:00
America/Curacao
AST
-4:00
America/Jamaica
EST
-5:00
America/Grand_Turk
MDT
-7:00
America/Rosario
ART
Argentina Time
-3:00
America/North_Dakota/Center
CDT
-6:00
PDT
America/North_Dakota/New_S
alem
-8:00
America/Catamarca
ART
Argentina Time
-3:00
America/Campo_Grande
AMT
Amazon Time
-4:00
America/Toronto
EDT
-5:00
America/Coral_Harbour
EST
-5:00
America/Glace_Bay
CDT
-6:00
America/Montreal
EDT
-5:00
America/St_Johns
NDT
-3:30
America/Montserrat
AST
-4:00
America/Antigua
AST
-4:00
America/Godthab
WGST
-3:00
America/Nassau
EDT
-5:00
America/Shiprock
MDT
-7:00
America/Indianapolis
EDT
-5:00
America/Cayenne
GFT
-3:00
America/Manaus
AMT
Amazon Time
-4:00
America/Dawson
MST
-7:00
America/Panama
EST
-5:00
America/Swift_Current
CDT
-6:00
America/El_Salvador
CST
-6:00
D-7
Appendix D
Table D-1
Definition
America/Noronha
FNT
-2:00
America/St_Vincent
AST
-4:00
America/Juneau
AKDT
-9:00
America/Sao_Paulo
BRT
Brasilla Time
-3:00
America/Marigot
AST
-4:00
America/Resolute
CDT
-6:00
America/Caracas
VET
-4:30
America/Rio_Branco
AMT
Amazon Time
-4:00
America/Los_Angeles
PDT
-8:00
America/Regina
CST
-6:00
America/Porto_Acre
AMT
Amazon Time
-4:00
America/Bogota
COT
Columbia Time
-5:00
America/Anguilla
AST
-4:00
America/Mazatlan
MDT
-7:00
America/Tortola
AST
-4:00
America/Mendoza
ART
Argentina Time
-3:00
America/Atikokan
EST
-500
America/Boise
MDT
-7:00
America/Cayman
EST
-5:00
America/Fortaleza
BRT
Brasilia Time
-3:00
America/Port_of_Spain
AST
-4:00
America/Montevideo
UYT
Uruguay Time
-3:00
America/Mexico_City
CDT
-6:00
America/Argentina/Ushuaia
ART
Argentina Time
-3:00
America/Argentina/Jujuy
ART
Argentina Time
-3:00
America/Argentina/San_Luis
ART
Argentina Time
-3:00
America/Argentina/ComodRivadavia
ART
Argentina Time
-3:00
America/Argentina/Buenos_Aires
ART
Argentina Time
-3:00
America/Argentina/Tucu- ART
man
Argentina Time
-3:00
ART
Argentina Time
-3:00
America/Argentina/Rio_Gallegos
D-8
OL-25957-01
Appendix D
Table D-1
Definition
America/Argentina/Catamarca
ART
Argentina Time
-3:00
America/Argentina/La_Rioja
ART
Argentina Time
-3:00
America/Argentina/San_Juan
ART
Argentina Time
-3:00
America/Argentina/Mendoza
ART
Argentina Time
-3:00
America/Argentina/Salta
ART
Argentina Time
-3:00
America/Argentina/Cordoba
ART
Argentina Time
-3:00
America/Iqaluit
EDT
-5:00
America/Tijuana
PDT
-8:00
America/Cordoba
ART
Argentina Time
-3:00
America/Whitehorse
PDT
-8:00
America/Porto_Velho
AMT
Amazon Time
-4:00
America/Asuncion
PYT
Paraguay Time
-4:00
America/Menominee
CST
-6:00
America/Araguaina
BRT
Brasilia Time
-3:00
America/Dominica
AST
-4:00
America/St_Lucia
AST
-4:00
America/Havana
CDT
-5:00
America/Anchorage
AKDT
-9:00
America/Virgin
EDT
-5:00
America/Paramaribo
SRT
Suriname Time
-3:00
America/Rainy_River
CDT
-5:00
America/Blanc-Sablon
AST
-4:00
America/Thule
ADT
-3:00
America/New_York
EDT
-5:00
America/Tegucigalpa
CST
-6:00
America/St_Thomas
AST
-4:00
America/Indiana/Vevay
EDT
-4:00
America/Indiana/Winamac
EDT
-4:00
America/Indiana/Indianapolis
EDT
-5:00
D-9
Appendix D
Table D-1
Definition
America/Indiana/Marengo EDT
-5:00
America/Indiana/Petersburg
EDT
-5:00
America/Indiana/Knox
CDT
-5:00
America/Indiana/Vincennes
EDT
-4:00
America/Indiana/Tell_City
CDT
-5:00
America/Denver
MDT
-7:00
America/Costa_Rica
CST
-6:00
America/Cuiaba
AMT
Amazon Time
-4:00
America/Boa_Vista
AMT
Amazon Time
-4:00
America/Recife
BRT
Brasilia Time
-3:00
America/Vancouver
PDT
-8:00
America/Dawson_Creek
MST
-7:00
America/Atka
HADT
-9:00
America/Adak
HADT
-10:00
America/Belize
CST
-6:00
America/Louisville
EDT
-5:00
America/Miquelon
PMDT
-3:00
America/Detroit
EDT
-5:00
America/Thunder_Bay
EDT
-5:00
America/Guadeloupe
AST
-4:00
America/Guyana
GYT
Guyana Time
-4:00
America/Martinique
AST
-4:00
America/Nome
AKDT
-9:00
America/Santarem
BRT
Brasilia Time
-3:00
America/Moncton
ADT
-4:00
America/Maceio
BRT
Brasilia Time
-3:00
America/Inuvik
MDT
-7:00
America/Cancun
CDT
-6:00
America/Halifax
ADT
-4:00
America/Edmonton
MDT
-7:00
-4:00
America/Kentucky/Monti- EDT
cello
D-10
OL-25957-01
Appendix D
Table D-1
Definition
America/Kentucky/Louis- EDT
ville
-5:00
America/Monterrey
CDT
-6:00
America/Guatemala
CST
-6:00
America/Chicago
CDT
-6:00
MET
MEST
+2:00
Factory
GMT
+0:00
Indian/Mahe
IST
+5:30
Indian/Maldives
MVT
Maldives Time
+5:00
Indian/Mauritius
MUT
Mauritius Time
+4:00
Indian/Chagos
IOT
+6:00
Indian/Cocos
CCT
+6:30
Indian/Reunion
RET
Reunion Time
+4:00
Indian/Comoro
EAT
+3:00
Indian/Antananarivo
EAT
+3:00
Indian/Christmas
CXT
+7:00
Indian/Kerguelen
TFT
+5:00
Indian/Mayotte
EAT
+3:00
Canada/Pacific
PDT
-7:00
Canada/East-Saskatchewan
CST
-6:00
Canada/Newfoundland
NDT
-2:30
Canada/Central
CDT
-5:00
Canada/Eastern
EDT
-4:00
Canada/Mountain
MDT
-7:00
Canada/Saskatchewan
CST
-6:00
Canada/Atlantic
ADT
-3:00
Canada/Yukon
EDT
-5:00
ROC
CST
+8:00
Greenwich
EDT
-4:00
Zulu
Universal
Universal Time
+0:00
Poland
EDT
-4:00
MST7MDT
MDT
-6:00
Australia/Tasmania
EST
+10:00
Australia/West
WST
+8:00
D-11
Appendix D
Table D-1
Definition
Australia/Darwin
CST
+9:30
Australia/Yancowinna
CST
+9:30
Australia/Brisbane
EST
+10:30
Australia/Lord_Howe
LHST
+10:30
Australia/Currie
EST
+10:00
Australia/Adelaide
CST
+9:30
Australia/Perth
WST
+8:00
Australia/Hobart
EST
+10:00
Australia/ACT
EST
+10:00
Australia/North
CST
+9:30
Australia/Eucla
CWST
+8:45
Australia/NSW
EST
+10:00
Australia/Victoria
EST
+10:00
Australia/South
CST
+9:30
Australia/Canberra
EST
+10:00
Australia/LHI
LHST
+10:30
Australia/Queensland
EST
+10:00
Australia/Melbourne
EST
+10:00
Australia/Sydney
EST
+10:00
Australia/Broken_Hill
CST
+9:30
Atlantic/Stanley
FKST
-3:00
Atlantic/Faroe
WEST
+1:00
Atlantic/Canary
WEST
+1:00
Atlantic/Azores
AZOST
+0:00
Atlantic/South_Georgia
GST
-2:00
Atlantic/St_Helena
GMT
+0:00
Atlantic/Cape_Verde
CVT
-1:00
Atlantic/Jan_Mayen
CEST
+2:00
Atlantic/Reykjavik
GMT
+0:00
Atlantic/Faeroe
WEST
+1:00
Atlantic/Madeira
WEST
+1:00
Atlantic/Bermuda
ADT
-3:00
America/Grenada
AST
-4:00
America/Phoenix
MST
-7:00
America/Chihuahua
MDT
-6:00
D-12
OL-25957-01
Appendix D
Table D-1
Definition
America/Goose_Bay
ADT
-3:00
America/St_Kitts
AST
-4:00
America/La_Paz
BOT
Bolivia Time
-4:00
America/Santo_Domingo
AST
-4:00
America/Guayaquil
ECT
Ecuador Time
-5:00
America/Pangnirtung
EDT
-4:00
America/Barbados
AST
-4:00
America/Jujuy
ART
Argentina Time
-3:00
America/Bahia
BRT
Brasilia Time
-3:00
America/St_Barthelemy
AST
-4:00
America/Puerto_Rico
AST
-4:00
America/Danmarkshavn
GMT
+0:00
America/Knox_IN
CST
-5:00
America/Scoresbysund
EGST
+0:00
Kwajalein
MHT
+12:00
Iran/Tehran
IRDT
+4:30
Iran/Tehran
IRST
+3:30
Europe/Berlin
CEST
+2:00
Europe/Simferopol
EEST
+3:00
Europe/Andorra
CEST
+2:00
Europe/Samara
KUYT
Kuybyshev Time
+4:00
Europe/Dublin
IST
+1:00
Europe/Guernsey
BST
+1:00
Europe/Riga
EEST
+3:00
Europe/Monaco
CEST
+2:00
Europe/Tirana
CEST
+2:00
Europe/San Marino
CEST
+2:00
Europe/Istanbul
EEST
+3:00
Europe/Athens
EEST
+3:00
Europe/Zurich
CEST
+2:00
Europe/Belgrade
CEST
+2:00
Europe/Sarajevo
CEST
+2:00
Europe/Tallinn
EEST
+3:00
Europe/Podgorica
CEST
+2:00
Europe/Bratislava
CEST
+2:00
D-13
Appendix D
Table D-1
Definition
Europe/Jersey
BST
+1:00
Europe/Isle_of_Man
BST
+1:00
Europe/Copenhagen
CEST
+2:00
Europe/Volgograd
MSD
+4:00
Europe/Gibraltar
CEST
+2:00
Europe/Vatican
CEST
+2:00
Europe/Belfast
BST
+1:00
Europe/Brussels
CEST
+2:00
Europe/Amsterdam
CEST
+2:00
Europe/Bucharest
EEST
+3:00
Europe/Helsinki
EEST
+3:00
Europe/London
BST
+1:00
Europe/Moscow
MSD
+4:00
Europe/Madrid
CET
+1:00
Europe/Budapest
CEST
+2:00
Europe/Vaduz
CEST
+2:00
Europe/Prague
CEST
+2:00
Europe/Luxembourg
CEST
+2:00
Europe/Vienna
CEST
+2:00
Europe/Rome
CEST
+2:00
Europe/Mariehamn
EEST
+3:00
Europe/Nicosia
EEST
+3:00
Europe/Lisbon
WEST
+1:00
Europe/Kiev
EEST
+3:00
Europe/Sofia
EEST
+3:00
Europe/Malta
CEST
+2:00
Europe/Chisinau
EEST
+3:00
Europe/Tiraspol
EEST
+3:00
Europe/Paris
CEST
+2:00
Europe/Warsaw
CEST
+2:00
Europe/Oslo
CEST
+2:00
Europe/Stockholm
CEST
+2:00
Europe/Skopje
CEST
+2:00
Europe/Ljubljana
CEST
+2:00
Europe/Zagreb
CEST
+2:00
D-14
OL-25957-01
Appendix D
Table D-1
Definition
Europe/Vilnius
EEST
+3:00
Europe/Zaporozhye
EEST
+3:00
Europe/Uzhgorod
EEST
+3:00
Europe/Minsk
EEST
+3:00
Europe/Kaliningrad
EEST
+3:00
EST
EST
-5:00
Africa/Ouagadougou
GMT
+0:00
Africa/Maseru
SAST
+2:00
Africa/Conakry
GMT
+0:00
Africa/Niamey
WAT
+1:00
Africa/Blantyre
CAT
+2:00
Africa/Nouakchott
GMT
+0:00
Africa/Johannesburg
SAST
+2:00
Africa/Asmera
EAT
+3:00
Africa/Windhoek
WAT
+1:00
Africa/Ndjamena
WAT
+1:00
Africa/Abidjan
GMT
+0:00
Africa/Malabo
WAT
+1:00
Africa/Maputo
CAT
+2:00
Africa/Lome
GMT
+0:00
Africa/Khartoum
EAT
+3:00
Africa/Harare
CAT
+2:00
Africa/Bamako
GMT
+0:00
Africa/Asmara
GMT
+0:00
Africa/Porto-Novo
WAT
+1:00
Africa/Douala
WAT
+1:00
Africa/Mbabane
SAST
+2:00
Africa/Kampala
EAT
+3:00
Africa/Lusaka
CAT
+2:00
Africa/Tunis
CET
+1:00
Africa/Addis_Ababa
EAT
+3:00
Africa/Lubumbashi
CAT
+2:00
Africa/Ceuta
CEST
+2:00
Africa/Freetown
GMT
+0:00
D-15
Appendix D
Table D-1
Definition
Africa/Mogadishu
EAT
+3:00
Africa/Banjul
GMT
+0:00
Africa/Luanda
WAT
+1:00
Africa/Bangui
WAT
+1:00
Africa/Lagos
WAT
+1:00
Africa/Brazzaville
WAT
+1:00
Africa/Nairobi
EAT
+3:00
Africa/Algiers
CET
+2:00
Africa/Dar_es_Salaam
GMT
+0:00
Africa/Dakar
GMT
+0:00
Africa/Accra
GMT
+0:00
Africa/Tripoli
EET
+2:00
Africa/Djibouti
EAT
+3:00
Africa/Libreville
WAT
+1:00
Africa/Kinshasa
WAT
+1:00
Africa/El_Aaiun
GMT
+0:00
Africa/Cairo
EET
+2:00
Africa/Timbuktu
GMT
+0:00
Africa/Sao_Tome
GMT
+0:00
Africa/Monrovia
GMT
+0:00
Africa/Bissau
GMT
+0:00
Africa/Bujumbura
CAT
+2:00
Africa/Gaborone
CAT
+2:00
Africa/Kigali
CAT
+2:00
Africa/Casablanca
WEST
+2:00
Iran/Tehran
IRDT
+4:30
Iran/Tehran
IRST
+3:30
Europe/Berlin
CEST
+2:00
Europe/Simferopol
EEST
+3:00
Europe/Andorra
CEST
+2:00
Europe/Samara
KUYT
Kuybyshev Time
+4:00
Europe/Dublin
IST
+1:00
Europe/Guernsey
BST
+1:00
Europe/Riga
EEST
+3:00
Europe/Monaco
CEST
+2:00
D-16
OL-25957-01
Appendix D
Table D-1
Definition
Europe/Tirana
CEST
+2:00
Europe/San Marino
CEST
+2:00
Europe/Istanbul
EEST
+3:00
Europe/Athens
EEST
+3:00
Europe/Zurich
CEST
+2:00
Europe/Belgrade
CEST
+2:00
Europe/Sarajevo
CEST
+2:00
Europe/Tallinn
EEST
+3:00
Europe/Podgorica
CEST
+2:00
Europe/Bratislava
CEST
+2:00
Europe/Jersey
BST
+1:00
Europe/Isle_of_Man
BST
+1:00
Europe/Copenhagen
CEST
+2:00
Europe/Volgograd
MSD
+4:00
Europe/Gibraltar
CEST
+2:00
Europe/Vatican
CEST
+2:00
Europe/Belfast
BST
+1:00
Europe/Brussels
CEST
+2:00
Europe/Amsterdam
CEST
+2:00
Europe/Bucharest
EEST
+3:00
Europe/Helsinki
EEST
+3:00
Europe/London
BST
+1:00
Europe/Moscow
MSD
+4:00
Europe/Madrid
CET
+1:00
Europe/Budapest
CEST
+2:00
Europe/Vaduz
CEST
+2:00
Europe/Prague
CEST
+2:00
Europe/Luxembourg
CEST
+2:00
Europe/Vienna
CEST
+2:00
Europe/Rome
CEST
+2:00
Europe/Mariehamn
EEST
+3:00
Europe/Nicosia
EEST
+3:00
Europe/Lisbon
WEST
+1:00
Europe/Kiev
EEST
+3:00
D-17
Appendix D
Table D-1
Definition
Europe/Sofia
EEST
+3:00
Europe/Malta
CEST
+2:00
D-18
OL-25957-01
A P P E N D I X
backup.pl
On Windows
backup.pl
/opt/CSCOpx/bin/perl /opt/CSCOpx/bin/backup.pl
-dest=BackupDirectory -system [-log=LogFile]
[-gen=Num_Generations]
On Windows
NMSROOT\bin\perl NMSROOT\bin\backup.pl
-dest=BackupDirectory -system [-log=LogFile]
[-gen=Num_Generations]
Explanation
NMSROOT
dir1
BKP
Logfile
Log file name that contains the details of the backup. The default
location of the backup log file (dbbackup.log) is:
backup.pl
E-1
Appendix E
Syntax
Explanation
BackupDirectory
comma_separated_email_ids
Num_Generations
Example 1
On Solaris:
opt/CSCOpx/bin/perl
On Windows:
C:\Progra~1\CSCOpx\bin\perl C:\Progra~1\CSCOpx\bin\backup.pl C:\backup email=
E-2
OL-25957-01
A P P E N D I X
Note
restorebackup.pl
is as follows:
-d
-d
Windows
NMSROOT\bin\perl NMSROOT\bin\restorebackup.pl
[-gen generationNumber]
Explanation
NMSROOT(Required)
-t
temporary_directory(Optional)
-gen generationNumber(Optional)
-d
BKP(Required)
-h (Optional)
F-1
Appendix F
Examples
To restore...
opt/CSCOpx/bin/perl
C:\Progra~1\CSCOpx\bin\perl
opt/CSCOpx/bin/restorebackup.p C:\Progra~1\CSCOpx\bin\
l -d BKP -gen now
restorebackup.pl -d BKP -gen now
The 12th
generation of data
opt/CSCOpx/bin/perl
C:\Progra~1\CSCOpx\bin\perl
opt/CSCOpx/bin/restorebackup.p C:\Progra~1\CSCOpx\bin\
l -d BKP -gen 12
restorebackup.pl -d BKP -gen
opt/CSCOpx/bin/perl
opt/CSCOpx/bin/restorebackup.p
l
-d DB_BKP1/automaticbackup/c
mfbackup -gen now
12
C:\Progra~1\CSCOpx\bin\perl
C:\Progra~1\CSCOpx\bin\
restorebackup.pl -d
DB_BKP\automaticbackup\cmfbackup
-gen now
F-2
OL-25957-01
I N D EX
disabling FIPS
accessing LMS server
2-18
6-47
3-12
E
enabling FIPS
2-18
evaluation mode
before installation
1-19
3-8
3-2
F
C
FIPS, enabling/disabling
cautions, significance of
cautions regarding
daemon manager, starting and stopping
8-2
1-2
on Windows
overview
6-46
4-5
4-1
system requirements
product overview
concurrent users
2-18
i-xvi
1-1
Veritas components
4-4
4-3
3-15
7-24
I
install, preparing to
3-1
installation
database password rules
A-4
new installations
data migration
7-2
1-15
7-2
notes
general
3-2
Solaris
3-3
Windows
selective backup
debugging CAM
8-18
7-3
prerequisites
8-17
3-4
2-1
A-4
3-1
installation terms
Installing and Migrating to Cisco Prime LAN Management Solution 4.2
OL-25957-01
IN-1
Index
Admin password
3-1
Fault Management
3-1
C-1
Integration Utility
supported NMS
8-22
3-1
8-21
3-2
8-23
7-17
1-17
Remote
7-17
Migration Scope
CiscoWorks Assistant
license file
3-7
migration scope
3-11
CiscoView
3-5
7-12
Common Services
7-4
evaluation license
license file
7-14
3-8
Fault Management
3-7
NFR license
7-12
7-10
3-10
3-5
Portal
7-26
before uninstalling
concurrent users
7-14
6-50
3-15
license information
new installation
7-11
LMS
AAA Methods
3-5
6-1
N
new features
prerequisites
2-1
Template Center
reinstallation
6-52
uninstallation
Solaris
Windows
uninstalling
logging into LMS
7-7
1-15
1-15
new installation
6-50
silent mode
6-51
Solaris
6-50
6-39
6-33
verifying installation
6-49
Windows
NFR license
6-45
6-36
3-10
M
messages, installation
8-4
8-17
P
PAK
3-5
password information
IN-2
OL-25957-01
Index
database password
A-4
A-4
scaling numbers
2-20
post-upgrade activities, CS
7-26
selftest tool
processors, supported
Solaris
Server
2-10
Windows
3-12
7-2
8-17
2-8, 2-11
Solaris patches
2-14
cluster patches
2-20
stopping RSAC
System
uninstalling RSAC
properties file
C-4
C-4
C-9
C-9
FILTER_THREADS
2-11
2-8
C-10
C-10
READ_INTERVAL_IN_SECS
SUBSCRIPTION_DATA_FILES
SYSLOG_FILES
C-10
C-10
on Windows 2003
2-16
on Windows 2008
2-16
troubleshooting installation
messages, understanding
C-9
8-4
C-8
TIMEZONE_FILE
2-16
C-10
QUEUE_CAPACITY
8-1
C-8
C-3
2-15
DEBUG_MAX_FILE_SIZE
C-7
2-8
C-9
C-9
uninstalling
2-3
on Windows
C-8
DEBUG_MAX_BACKUPS
C-7
operating system
C-9
DEBUG_LEVEL
TIMEZONE
2-15
on Virtualization Systems
C-10
DEBUG_CATEGORY_NAME
PARSER_FILE
on client systems
on Solaris
C-8
DEBUG_FILES
2-2
server requirements
COLLECTOR_PORT
upgrading
C-7
COUNTRY_CODE
1-16
2-15
disk space
stopping
C-6
C-1
1-19
2-26
C-7
supported devices
8-2
2-18
C-2
U
UCS support
2-15
6-50
IN-3
Index
on Solaris
6-50
on Windows
6-51
uninstalling RSAC
C-7
upgrading LMS
remote upgrade on Solaris
remote upgrade on Windows
upgrading RSAC
6-44
6-45
C-3
UTU
access
B-5
configure
B-6
download
B-3
install
B-3
requirements
search patterns
uninstall
B-14
upgrade
B-14
B-2
B-13
B-6
IN-4
OL-25957-01