Install Cisco LSM PDF

Installing and Migrating to Cisco Prime
LAN Management Solution 4.2
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
Text Part Number: OL-25957-01
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-2014 Cisco Systems, Inc. All rights reserved.
CONTENTS
Notices
xi
OpenSSL/Open SSL Project

License Issues i-xi
Preface
i-xi
xv
Audience
i-xv
Document Conventions
i-xvi
Product Documentation
i-xvii
Related Documentation for CiscoWorks LAN Management Solution 4.0

Obtaining Documentation, Obtaining Support, and Security Guidelines
CHAPTER
Overview of Cisco Prime LAN Management Solution 4.2

Product Overview
i-xix
i-xxi
1-1
1-1
Install and Upgrade Behavior 1-2

Overview of Upgrade and Migration 1-2
Upgrading Master-Slave Server Setup 1-3
New Features and Enhancements in LMS 4.2 1-6
Creating Configuration Templates 1-6
Idle Timeout Settings 1-6
Standard Discovery 1-7
CAAM Features 1-8
Data Synchronization between LMS and CAAM 1-8
Managing Policy Groups 1-8
Managing Policy Profile 1-9
Fixing Profile Violation 1-9
Compliance Data Collection 1-9
CAAM Offline Update 1-9
CAAM Online Update 1-9
Import Contracts 1-9
CAAM Reports 1-9
Hardware Configuration-based MIB Objects Polling 1-10
Poller Management Enhancements 1-11
Troubleshooting Workflow Changes 1-11
Fault Management Generic Device Package Support and Traps Support
Enhancement in Unused POE Report 1-11
1-11

OL-25957-01
iii
Contents
Enhancement in Custom Inventory Report 1-11

Enhancement in TrustSec 1-12
EnergyWise Enhancement 1-13
Report Designer Enhancement 1-13
VLAN Fetch Support for SCP and RCP 1-13
Template Center Enhancement 1-14
Third-Party Software and Tool Changes 1-14
Data Migration Overview
1-14
Supported Network Management Systems

Supported Devices
CHAPTER
Prerequisites
1-15
1-18
2-1
System and Browser Requirements for Server and Client 2-2

Disk Space Requirements 2-2
Operating System Requirements 2-3
Storage Area Network Support 2-5
Link Aggregation Support in Solaris 10 2-5
Server Requirements on Soft Appliance Systems 2-7
Server Requirements on Solaris Systems 2-9
Server Requirements on Windows Systems 2-12
Unified Computing System (UCS) Support 2-16
System Requirements on Client Systems 2-16
Terminal Server Support for Windows Server 2-17
Enabling and Disabling Terminal Services on Windows 2008 Server
Enabling and Disabling FIPS on Windows 2008 Servers 2-19
Solaris Patches 2-19
Required and Recommended Solaris Patches
Cluster Patches 2-21
LMS 4.2 Port Usage
Important URLs
2-19
2-21
2-26
Required Device Credentials for LMS Functionalities
CHAPTER
2-17
2-27
Preparing to Install Cisco Prime LAN Management Solution 4.2

Terms and Definitions Used in LMS Installation Framework
3-1
3-1
Before You Begin Installation 3-2

Installation Notes 3-2
Installation Notes (For Solaris Only) 3-3
Installation Notes (For Windows Only) 3-4
iv
OL-25957-01
Contents
Installation Notes (For Soft Appliance Only)
3-5
Licensing Your Product 3-5

Understanding Product Ordering Options and Product Authorization Key 3-5
License Information 3-5
Available Licenses for LMS 4.2 3-6
Upgrading to a Higher SKU on Soft Appliance Systems 3-6
License File 3-7
Transferring Files to Soft Appliance Server 3-7
Evaluation Mode 3-8
LMS 50 Devices Restricted License 3-9
Guidelines to Avoid Necessary Devices Being Moved to Suspended State
Device States After Backup and Restore in a LMS 50 SKU Server 3-9
NFR (Not For Resale) License 3-10
Installing the License File 3-11
3-9
Application Scaling Numbers 3-12

Concurrent Users Supported 3-15
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
System Requirements for High Availability Implementation
4-4
Setting up LMS High Availability Environment on Windows 4-5

Installing Storage Foundation HA 5.1 on Windows 4-5
Creating Disk Groups and Volumes 4-6
Prerequisites for Configuring Disk Groups and Volumes 4-6
Creating Disk Groups on Primary Server 4-6
Creating Volumes on Primary Server 4-7
Creating Disk Groups and Volumes on Secondary Server 4-9
Installing LMS on Primary and Secondary Servers 4-9
Setting Up Veritas Volume Replication 4-10
Modes of Replication 4-10
Setting Up RDS, RVG and RLINK 4-10
Setting Casuser Permissions on cscopx Volume 4-11
Setting Up Veritas Volume Replication Without Clustering 4-12
Veritas Cluster Server Setup Tasks 4-13
Cluster Configuration for High Availability 4-13
Cluster Configuration for Disaster Recovery 4-18
Setting up LMS High Availability Environment on Solaris
4-21

OL-25957-01
Contents
Installing Storage Foundation HA 5.1 on Solaris 4-21

Creating Disk Groups and Volumes on Solaris Servers 4-22
Prerequisites for Configuring Disk Groups and Volumes on Solaris 4-22
Creating Disk Groups on Primary Solaris Server 4-23
Creating Volumes on Primary Solaris Server 4-23
Creating Disk Groups and Volumes on Secondary Solaris Server 4-25
Installing LMS on Primary and Secondary Servers 4-25
Setting Up Veritas Volume Replication on Solaris Server 4-25
Setting Casuser Permissions on cscopx Volume on Solaris (If Required) 4-26
Setting Up Veritas Volume Replication Without Clustering On Solaris 4-26
Veritas Cluster Server Setup Tasks on Solaris 4-27
Cluster Configuration for High Availability on Solaris 4-27
Cluster Configuration for Disaster Recovery on Solaris 4-32
Moving LMS from non-HA to HA Environment
CHAPTER
4-34
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
Overview of VMware VMotion and Storage VMotion 5-5

VMware vSphere Components for Migration 5-6
Prerequisites for Migration Using VMotion 5-6
Migrating LMS 4.2 Using VMware VMotion 5-7
Migrating a Virtual Machine with VMotion 5-8
Migrating a Virtual Machine with Storage VMotion 5-8
Cloning a Virtual Machine Using VMware 5-9
Advantages of Clones 5-9
Types of Clones 5-9
Supported Methods of Cloning 5-10
Cloning a New Virtual Machine from a Parent Virtual Machine 5-10
Prerequisites 5-10
Cloning a new Virtual Machine 5-10
Setting Up LMS in the Clone Virtual Machine 5-11
Known Problems 5-11
Cloning Parent VM to Template and Deploying Template to New VM 5-12
Cloning Parent VM to Template 5-12
vi
OL-25957-01
Contents
Deploying Template to New VM
CHAPTER
5-12
Performing Installation of Cisco Prime LMS 4.2
6-1
Performing Installation of LMS 4.2 6-1

Downloading from Cisco.com 6-2
Download Instructions for LMS 4.2 software on Soft Appliance - OVA Image 6-2
Important Download Notes for LMS 4.2 Software - OVA Image 6-3
Downloading Multiple Small Files - OVA Image 6-3
Download Instructions for LMS 4.2 software - OVA Image 6-3
Installation Procedure for Cisco Prime LMS 4.2 on Soft Appliance - OVA Image 6-4
Extending File System in Soft Appliance 6-12
Extending in Online Mode 6-16
Extending in Offline Mode 6-17
Changing Server Configuration Details 6-17
Viewing System Details 6-19
Installing LMS 4.2 Soft Appliance - ISO Image 6-31
Installing LMS 4.2 Soft Appliance on VMware 6-31
Installing LMS 4.2 Soft Appliance on NCS and UCS Servers 6-34
Installing LMS 4.2 on Solaris 6-37
Installing LMS 4.2 on Windows 6-40
Installing LMS 4.2 in Silent Mode 6-43
Upgrading to LMS 4.2 6-44
Inline Upgrade to LMS 4.2 on Soft Appliance 6-47
Inline Upgrade to LMS 4.2 on Windows 6-48
Inline Upgrade to LMS 4.2 on Solaris 6-48
Remote Upgrade to LMS 4.2 6-48
Remote Upgrade to LMS 4.2 on Solaris 6-48
Remote Upgrade to LMS 4.2 on Windows 6-49
Verifying the Installation
6-49
Accessing LMS Server 6-51

Clearing Cache and Cookies 6-52
Internet Explorer 8.0 and 9.0 6-52
Mozilla FireFox 8.0 and 9.0 6-52
Enabling Loading of Scripts in Windows 2008
Logging into Cisco Prime LMS Server
6-53
6-53
Uninstalling LMS 4.2 6-54

Before You Begin Uninstallation 6-54
Uninstalling LMS 4.2 on Solaris 6-54
Uninstalling LMS 4.2 on Windows 6-55
OL-25957-01
vii
Contents
Re-installing LMS 4.2
6-56
Downloading and Installing CiscoWorks LMS 4.2 Using Windows 2012 Patch
CHAPTER
Migrating Data to Cisco Prime LAN Management Solution 4.2

Overview of Migration to LMS 4.2
6-56
7-1
7-1
Scope of Data Migration 7-2

Common Services Data Migration Scope 7-3
Network Topology, Layer 2 Services and User Tracking Data Migration Scope 7-5
Inventory, Config and Image Management Data Migration Scope 7-6
Fault Management Data Migration Scope 7-9
IPSLA Performance Management Data Migration Scope 7-10
CiscoView Data Migration Scope 7-11
Device Performance Management Data Migration Scope 7-11
Portal Data Migration Scope 7-13
CiscoWorks Assistant Data Migration Scope 7-13
Remote Migration From LMS 2.6 or 2.6 SP1 7-16
Remote Migration From LMS 3.0 or LMS 3.0 December 2007 Update or LMS 3.1 7-16
Migrating Data From LMS 3.2 SP1, LMS 4.0.1 or LMS 4.1
Migrating Data on Solaris 7-18
Migrating Data on Windows 7-19
Migrating Data on Soft Appliance 7-20
7-18
Guidelines to Post-Upgrade Activities 7-22

Guidelines for Fault Management Post-Upgrade Activities in LMS 4.2 7-23
Configuring SNMP Trap Receiving and Forwarding 7-23
Guidelines for Restoring Inventory, Config Timeout and Retry Settings 7-24
Guidelines for Common Services Post-Upgrade Activities 7-25
LMS 4.2 AAA Methods 7-25
Local Authentication Mode 7-25
Resetting the Login Module 7-26
CHAPTER
Troubleshooting and FAQs
8-1
Checking Processes After Installation
8-1
Viewing and Changing Process Status
8-1
Recovering Admin Password on LMS Virtual Appliance

Contacting Cisco Technical Assistance Center (TAC)
Understanding Installation Error Messages
8-2
8-4
8-4
Troubleshooting Errors in Data Migration 8-15

Common Services Data Migration Errors 8-17
viii
OL-25957-01
Contents
Inventory, Config and Image Management Data Migration Errors 8-18

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
User Inputs for Installation
8-19
8-24
A-1
User Inputs for LMS Installation A-1

User Inputs for New Installation A-1
User Inputs for Reinstallation A-2
Password Information A-3
LMS Login and Database Passwords A-4
Changing LMS Admin Password A-4
Changing casuser Password A-6
Installing VMware Tools
APPENDIX
User Tracking Utility
A-7
B-1
Understanding UTU
B-2
Hardware and Software Requirements for UTU 2.0

Downloading UTU 2.0
B-2
B-3
Installing UTU 2.0 B-3

Installing UTU 2.0 in Silent Mode B-4
Installing UTU 2.0 in Normal Mode B-4
Accessing UTU 2.0
Configuring UTU 2.0
B-5
B-6
Searching for Users, Hosts or IP Phones

Using Search Patterns in UTU 2.0
Uninstalling UTU 2.0
APPENDIX
B-8
B-13
B-14
Upgrading to UTU 2.0
B-14
Re-installing UTU 2.0
B-14
Installing the Remote Syslog Collector
C-1
Verifying Remote Syslog Collector Server Requirement

Installing on Solaris C-4
Installing on Windows C-5
C-2
C-4

OL-25957-01
ix
Contents
Installing on Soft Appliance C-5

Subscribing to a Remote Syslog Collector C-6
Starting the Remote Syslog Collector C-6
Stopping the Remote Syslog Collector C-7
Uninstalling the Remote Syslog Collector C-7
Uninstallation on Windows C-7
Uninstallation on Solaris C-7
Uninstallation on Soft Appliance C-7
Understanding the Syslog Collector Properties File
C-8
D-1
APPENDIX
Supported Server Time Zones and Offset Settings
APPENDIX
Syntax and Usage for Backup Script
E-1
APPENDIX
Syntax and Usage for Restore Script
F-1
INDEX
OL-25957-01
Notices
The following notices pertain to this software license.
OpenSSL/Open SSL Project

This product includes software developed by the OpenSSL Project for use in the OpenSSL Toolkit
(http://www.openssl.org/).
This product includes cryptographic software written by Eric Young (eay@cryptsoft.com).
This product includes software written by Tim Hudson (tjh@cryptsoft.com).
License Issues
The OpenSSL toolkit stays under a dual license, i.e. both the conditions of the OpenSSL License and the
original SSLeay license apply to the toolkit. See below for the actual license texts. Actually both licenses
are BSD-style Open Source licenses. In case of any license issues related to OpenSSL please contact
openssl-core@openssl.org.
OpenSSL License:
Copyright 1998-2007 The OpenSSL Project. All rights reserved.

Redistribution and use in source and binary forms, with or without modification, are permitted provided
that the following conditions are met:
1.
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.
6.
Redistributions of any form whatsoever must retain the following acknowledgment:

OL-25957-01
Notices
This product includes software developed by the OpenSSL Project for use in the OpenSSL Toolkit
(http://www.openssl.org/).
THIS SOFTWARE IS PROVIDED BY THE OpenSSL PROJECT AS IS' AND ANY EXPRESSED OR
IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES
OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN
NO EVENT SHALL THE OpenSSL PROJECT OR ITS CONTRIBUTORS BE LIABLE FOR ANY
DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
(INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER
CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH
DAMAGE.
This product includes cryptographic software written by Eric Young (eay@cryptsoft.com). This product
includes software written by Tim Hudson (tjh@cryptsoft.com).
Original SSLeay License:
Copyright 1995-1998 Eric Young (eay@cryptsoft.com). All rights reserved.

This package is an SSL implementation written by Eric Young (eay@cryptsoft.com).
The implementation was written so as to conform with Netscapes SSL.
This library is free for commercial and non-commercial use as long as the following conditions are
adhered to. The following conditions apply to all code found in this distribution, be it the RC4, RSA,
lhash, DES, etc., code; not just the SSL code. The SSL documentation included with this distribution is
covered by the same copyright terms except that the holder is Tim Hudson (tjh@cryptsoft.com).
Copyright remains Eric Youngs, and as such any Copyright notices in the code are not to be removed.
If this package is used in a product, Eric Young should be given attribution as the author of the parts of
the library used. This can be in the form of a textual message at program startup or in documentation
(online or textual) provided with the package.
Redistribution and use in source and binary forms, with or without modification, are permitted provided
that the following conditions are met:
1.
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).
THIS SOFTWARE IS PROVIDED BY ERIC YOUNG AS IS AND ANY EXPRESS OR IMPLIED

WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF
MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO
EVENT SHALL THE AUTHOR OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT,
INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT
OL-25957-01
Notices
NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE,

DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY
THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
(INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF
THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
The license and distribution terms for any publicly available version or derivative of this code cannot be
changed. i.e. this code cannot simply be copied and put under another distribution license [including the
GNU Public License].

OL-25957-01
Notices
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
Audience
This guide is for anyone who installs, upgrades, configures, verifies, and uses LMS software. Network
administrators or operators should have the following skills:
Basic Windows, Linux or Solaris system administrator skills.
Basic network management skills.

OL-25957-01
15
Preface
Table 1 describes the conventions followed in this guide.
Table 1
Note
Caution
Conventions Used
Item
Convention
Commands and keywords
boldface font
Variables for which you supply values
italic font
Displayed session and system information
screen
Information you enter
boldface screen
Variables you enter
italic screen
Menu items and button names
boldface font
Selecting a menu item in paragraphs
Option > Network Preferences
Selecting a menu item in tables
Option > Network Preferences
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.
16
OL-25957-01
Preface
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
Document Title
Available Formats
Installing and Migrating to Cisco Prime LAN

Management Solution 4.2 (this document)
PDF version part of Cisco Prime LMS 4.2 Product

DVD.
On Cisco.com at:
http://www.cisco.com/en/US/docs/net_mgmt/
ciscoworks_lan_management_solution/4.2/install
/guide/install.html
Context-sensitive online help
Select an option from the navigation tree, then click

Help.
Getting Started with Cisco Prime LAN

Management Solution 4.2

DVD.
On Cisco.com at:
ciscoworks_lan_management_solution/4.2/user/
guide/getting_started/lms42_getstart_guide.html
Configuration Management with Cisco Prime


DVD.
On Cisco.com at:
guide/configuration/config.html
Monitoring and Troubleshooting with Cisco

Prime LAN Management Solution 4.2

DVD.
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
Administration of Cisco Prime LAN


DVD.
On Cisco.com at:
guide/admin/admin.html

OL-25957-01
17
Preface
Table 2
Product Documentation (continued)
Document Title
Technology Work Centers in Cisco Prime
Available Formats

DVD.
On Cisco.com at:
guide/workcenters/wcug.html
Reports Management with Cisco Prime LAN


DVD.
On Cisco.com at:
guide/reports/lms41_reports_guide.html
Inventory Management with Cisco Prime


DVD.
On Cisco.com at:
guide/inventory/inventory.html
Navigation Guide for Cisco Prime LAN


DVD.
On Cisco.com at:
oworks_lan_management_solution/4.2/navigation
/Guide/lms42_nav_guide.html
Open Database Schema Support in Cisco

Prime LAN Management Solution 4.2

DVD.
On Cisco.com at:
oworks_lan_management_solution/4.2/database_
schema/dbviews_42.html
Release Notes for Cisco Prime LAN


DVD.
On Cisco.com at:
ciscoworks_lan_management_solution/4.2/
release/notes/lms41rel.html
18
OL-25957-01
Preface
Table 2
Product Documentation (continued)
Document Title
Available Formats
Supported Devices Table for Cisco Prime


DVD.
On Cisco.com at:
ciscoworks_lan_management_solution/4.2/
device_support/table/lms41sdt.html
Documentation Roadmap for Cisco Prime

Printed document part of Software kit
Related Documentation for CiscoWorks LAN Management

Solution 4.0
Note
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
User Guide for Campus Manager

5.2 (With LMS 3.2)
PDF on:
Product 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
User Guide for Resource Manager

Essentials 4.3 (With LMS 3.2)
PDF on:
Product 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

OL-25957-01
19
Preface
Table 3
Related Documentation (continued)
Document Title
User Guide for Device Fault
Manager 3.2 (With LMS 3.2)
Available Formats
PDF on:
Product DVD
User Guide for Internetwork

Performance Monitor 4.2 (With
LMS 3.2)
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
User Guide for CiscoView 6.1.9
On Cisco.com at:
http://www.cisco.com/en/US/docs/net_mgmt/ciscoworks_int
ernetwork_performance_monitor/4.2/user/guide/IPM4_2ug.
html
PDF on:
Product DVD
User Guide for CiscoWorks LMS

Portal 1.2
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

Assistant 1.2
On Cisco.com at:
http://www.cisco.com/en/US/docs/net_mgmt/ciscoworks_lm
s_portal/1.2/user/guide/LMSPortal_1.2.html
PDF on:
Product DVD
On Cisco.com at:
http://www.cisco.com/en/US/docs/net_mgmt/ciscoworks_as
sistant/1.2/user/guide/cwa12.html
20
OL-25957-01
Preface
Table 3
Related Documentation (continued)
Document Title
User Guide for Health and
Utilization Monitor 1.2
Available Formats
PDF on:
Product DVD

Integration Utility 1.7
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
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
Obtaining Documentation, Obtaining Support, and Security

Guidelines
For information on obtaining documentation, submitting a service request, and gathering additional
information, see the monthly Whats New in Cisco Product Documentation, which also lists all new and
revised Cisco technical documentation, at:
http://www.cisco.com/en/US/docs/general/whatsnew/whatsnew.html
Subscribe to the Whats New in Cisco Product Documentation as a Really Simple Syndication (RSS) feed
and set content to be delivered directly to your desktop using a reader application. The RSS feeds are a free
service and Cisco currently supports RSS version 2.0.

OL-25957-01
21
Preface
22
OL-25957-01
CH A P T E R
Overview of Cisco Prime LAN Management

Solution 4.2
This chapter provides overview of LMS 4.2 and data migration from earlier versions of LMS to LMS 4.2.
This chapter contains:
Product Overview
Install and Upgrade Behavior
New Features and Enhancements in LMS 4.2
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.
Hardware and software requirements.
Detailed installation procedures.
Frequently asked questions.
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.

OL-25957-01
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)
Network Topology, Layer 2 Services and User Tracking
Fault Management
IPSLA Performance Management
Device Performance Management
There are additional licenses available for managing performance collectors.

See System and Browser Requirements for Server and Client and Application Scaling Numbers for more
details.

LMS 4.2 provides a single install experience to you. For complete details on installation, see Performing
Installation of Cisco Prime LMS 4.2
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.
Note
After LMS 4.2.5 installation, we recommend to reboot the server as Linux kernel is upgraded.
This section contains the following topics on Upgrade:
Overview of Upgrade and Migration
Upgrading Master-Slave Server Setup
Overview of Upgrade and Migration

Upgrading is overwriting the existing LMS version with a new LMS version. You have to freshly install
LMS 4.2 and then perform data migration.
You can upgrade using either of these methods:
Local upgradeUpgrading to the newer version of LMS on the same machine.
1-2
OL-25957-01
Chapter 1

Note
LMS 4.2 supports local upgrade or direct inline upgrade only from LMS 4.1 and LMS 4.0.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.
Upgrading Master-Slave Server Setup

Table 1-1 provides you details on Upgrading Master-Slave Server Setup
Table 1-1
Details on Upgrading Master-Slave Server Setup
Behavior Changes After

Remote Upgrade
Remote Migration
Changes
LMS Master
LMS Slave
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
After taking backup from LMS 3.2 SP1, install

LMS 4.2, the DCR mode will be in Standalone
After restoring the LMS 3.2 SP1/4.0.1 backed up

data in LMS 4.2, the DCR mode will be in
Standalone
You should change the mode to Slave
DCR Changes
No Changes
DCR devices will be deleted from Slave or pushed to

Master based on your choice, and data will be
synchronized from Master
Device
Management/Allocation
changes
After remote migration, the device

management allocation policy will be set
as it was before. For Example, if the
allocation policy is set to On in LMS 3.2
SP1/4.0.1/4.1 server, after remote
migration to LMS 4.2 the same settings
will be retained.
Device management allocation policy is set to Off,

and all the devices will be moved to unmanaged state.
This allows you to decide in managing devices in the
Slave
Grouping Services
Changes
User-defined groups in Slave will not be

shared or synchronized with Master in
LMS 4.2
User-defined groups can be created in LMS 4.2 Slave

as against previous releases like LMS 3.2 SP1 and
above. User-defined groups created in Master is
shared in Slave server.
Exporting of groups from Slave and

importing to Master is possible.
Grouping services might not work if
Master or Slave has different versions
of LMS. We recommend you to use
the same LMS version across all
servers in DCR management domain.
Exporting of groups from Master and importing

to Slave is possible
System defined (device type) groups are

separately created in Slave

OL-25957-01
1-3
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
Upgrade and Data Migration Procedure
Current LMS Version
Type of Upgrade
LMS 4.1
Remote migration
Direct inline migration
Procedure
1.
Back up the data in the old machine having LMS 4.1.
2.
Install LMS 4.2.
3.
Migrate your data to LMS 4.2 using the instructions

explained in the section Remote Upgrade to LMS 4.2.
1.
Install LMS 4.2 over LMS 4.1.

The data is automatically migrated during installation.
LMS 4.0.1
Remote migration
1.
Back up the data in the old machine having LMS 4.0.1.
2.
Install LMS 4.2.
3.

1.
Install LMS 4.2 over LMS 4.0.1.

LMS 3.2 SP1
Remote migration
1.
Back up the data in the old machine having LMS 3.2 SP1.
2.
Install LMS 4.2.
3.

1-4
OL-25957-01
Chapter 1

Table 1-2
Current LMS Version
Type of Upgrade
Procedure
LMS 2.6, LMS 2.6 SP1, Remote migration

LMS 3.0, LMS 3.0
Direct inline upgrade to
December 2007 update,
LMS 4.2 is not supported.
LMS 3.1
The suggested upgrade path is:
LMS 2.6/LMS 2.6 SP1/
LMS 3.0/LMS 3.0 December
2007 update/LMS 3.1> LMS
3.2 >LMS 4.0 > LMS 4.01 >
LMS 4.2
LMS 2.2, LMS 2.5,
LMS 2.5.1
1.
Back up the data in the old machine.
2.
Install LMS 4.0.1 in the new machine.
3.
Migrate the data to LMS 4.0.1. For more information, see

http://www.cisco.com/en/US/docs/net_mgmt/ciscoworks_la
n_management_solution/4.0/install/guide/dmg.html
4.
Install LMS 4.2.

From LMS 4.0.1 to LMS 4.2, you can perform direct inline
or remote upgrade, click here for more details.
Remote migration
1.

2.
Upgrade from the earlier versions of LMS to LMS 2.6 and

migrate the data, using the instructions in:
Readme for CiscoWorks LMS 2.6 Update on Solaris
LMS 2.2 / LMS 2.5 /

LMS 2.5.1 > LMS 2.6 >
LMS 4.0 > LMS 4.0.1
>LMS 4.2
Readme for CiscoWorks LMS 2.6 Update on Windows

Data Migration Guide for LAN Management Solution
2.6
3.
4.
Migrate the data to LMS 4.0.1.

5.
Install LMS 4.2.


OL-25957-01
1-5
Chapter 1

This section explains the new features in LMS 4.2.
See the Online help of LMS 4.2 applications for a detailed explanation on new features in LMS 4.2.
This section contains the following:
Note
Creating Configuration Templates
Idle Timeout Settings
Standard Discovery
CAAM Features
Hardware Configuration-based MIB Objects Polling
Poller Management Enhancements
Troubleshooting Workflow Changes
Enhancement in Unused POE Report
Enhancement in Custom Inventory Report
Enhancement in TrustSec
EnergyWise Enhancement
Report Designer Enhancement
VLAN Fetch Support for SCP and RCP
Template Center Enhancement
Third-Party Software and Tool Changes
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.
Creating Configuration Templates

CLI templates are user-defined templates that are created based on your own parameters. CLI templates
allow you to choose the elements in the configurations. LMS provides variables that you replace with
actual values and logic statements.
For more information, see Ceating Configuration Templates in Configuration Management with Cisco
Prime LAN Management Solution 4.2.
Idle Timeout Settings

If UI is kept idle for the set time period then a pop-up redirecting the page to idle page will be displayed.
You can click cancel to avoid redirecting to the idle page.
If you are redirected to the idle page then click click here link to return to your previous page. The
default idle timeout is 120 minutes.
1-6
OL-25957-01
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.
Inputs for seed device can be given as follows:
Using default gateway as seed, this option is chosen by default
Using Seed devices from DCR, it will not show the count of devices in DCR
Providing Seed devices manually in TextArea seperated by space
Inputs for SNMP credentials can be given as follows:
Use Policy Configuration
Custom Policy Configuration
Default set credentials
Provide Credentials Manually
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:
Data Synchronization between LMS and CAAM
Managing Policy Groups
Managing Policy Profile
Fixing Profile Violation
Compliance Data Collection
Import Contracts
CAAM Reports
CAAM Offline Update
CAAM Online Update
Data Synchronization between LMS and CAAM

CAAM database should always be in sync with LMS database. When a new device is added to LMS or
an unmanaged device is managed, and if the CAAMServer process is down, the device will not be added
to CAAM database. When the CAAMServer process comes up, the device will be added to CAAM
database but the device details such as Inventory, Config and Show Commands will not be updated in
CAAM database. You have to manually perform Inventory, Config, and Show Commands collection to
update the CAAM database.
For more information, see Using Compliance and Audit Manager Feature in Configuration Management
with Cisco Prime LAN Management Solution 4.2.

OL-25957-01
1-7
Chapter 1
Managing Policy Groups

Policy Group is a collection of Policies. Policies are defined by a set of rules. LMS 4.2 supports 293
policies. In addition to the system-defined Policy Groups, you can create your own Policy Groups by
selecting a set of system-defined policies. LMS allows you to add, clone, edit, and delete policy groups.
Managing Policy Profile

Policy Profile is a set of Policy Groups where each Policy Groups are mapped with set of devices/device
groups. LMS allows you to add, clone, edit, and delete policy profile. It also allows you to run the
compliance check and view the job history.
Fixing Profile Violation

The Profile Violations Fix Report lists all the devices that do not comply with a defined user profile. A
profile is defined as a policy or a set of policies applied on either a device or a set of devices. LMS
provides configuration commands for fixing the violation.

This feature allows you to schedule the Compliance Data Collection System Job. The Compliance Data
Collection job runs daily by default.
For more information, see Compliance and Audit Settings in Administration of Cisco Prime LAN
Management Solution 4.2.
CAAM Offline Update

This feature allows you to download and install the patches related to CAAM Server manually.
CAAM Online Update

Enables you to download and install the patches related to CAAM Server online.
Import Contracts
This feature enables you to import customer contracts into the CAAM Database.
1-8
OL-25957-01
Chapter 1

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.
Using CAAM, the following reports can be generated and viewed in the reports job browser:
Service Reports
Life Cycle Management Reports
Compliance Reports
For more information, see Compliance and Audit in Reports Management with Cisco Prime LAN
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:
HIPAA Compliance Reports
SOX (COBIT) Compliance Report
ISO/IEC 27002 Compliance Reports
NSA Compliance Reports
PCI DSS Compliance Reports
DHS Checklist Reports
DISA Checklists Report
CIS Benchmarks
Vendor Advisory Reports
Hardware Configuration-based MIB Objects Polling

When LMS server with specific hardware configuration polls MIB objects more than the recommended
number, a warning message is displayed.
For more information, see Hardware Configuration-based MIB Object Polling Support in Monitoring
and Troubleshooting with Cisco Prime LAN Management Solution 4.2.

OL-25957-01
1-9
Chapter 1
Poller Management Enhancements

In this release, Poller Management UI displays the polling preference types namely, Poll All Instances,
Poll by Pattern, and Poll by User Selection. Poll by Pattern is a new polling preference type introduced
in this release.
For more information, see Creating a Poller in Monitoring and Troubleshooting with Cisco Prime LAN
Troubleshooting Workflow Changes

Device Information portlet in the Device Troubleshooting workflow is enhanced and it displays
additional information such as CPU Utilization, Memory Utilization and so on.
For more information, see Device Information in Monitoring and Troubleshooting with Cisco Prime
LAN Management Solution 4.2.

In this release, LMS Fault Management functionality supports unknown devices and non-Cisco devices
with limited functionalities.
Unknown devices here refer to Cisco devices for which device package updates are not installed and
available on LMS server.
Unknown devices and non-Cisco devices together referred as Generic devices in LMS.
For more information, see Understanding the Detailed Device View in Monitoring and Troubleshooting
In this release, Trap support is provided for SNMPv3 configured devices, SNMPv2 configured devices,
unknown devices, and non-Cisco devices.
For more information, see Configuring SNMP Trap Receiving and Forwarding in Monitoring and
Troubleshooting with Cisco Prime LAN Management Solution 4.2.
Enhancement in Unused POE Report

You can view an unused PoE report with detailed information of PoE-enabled devices managed by LMS
along with the information of the ports that are not connected to the end points.
For more information, see Generating an Unused PoE Report in Reports Management with Cisco Prime
Enhancement in Custom Inventory Report

New Inventory Groups are added and few attributes have been added to the existing Inventory Groups.
1-10
OL-25957-01
Chapter 1

Inventory Group
Attribute
Bridge
Base Bridge Address

Number of Ports
Bridge Type
Container
Container Model Name

Container Vendor Type
Description
Manufacturer Name
Physical Entity Name
Interface
interface index
Memory pool
Lowest Free Block (MB)
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

OL-25957-01
1-11
Chapter 1
Secured Group Access Configuration
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
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.
Report Designer Enhancement

Earlier, Syslog and Inventory Custom Report templates were combined as a single workflow. In LMS
4.2, Syslog and Inventory Custom Report are available as two seperate flows.
For more information, see Report Designer in Reports Management with Cisco Prime LAN Management
Solution 4.2.
In the Inventory Custom Report template, Report Attributes and Rules for Attributes are available as two
different sections, where the generated report will display only the attributes selected under Report
Attributes section.
For more information, see Creating Inventory Custom Reports in Reports Management with Cisco Prime
VLAN Fetch Support for SCP and RCP

You can set the protocol order for Configuration Management features such as Archive Management,
Config Editor, and NetConfig jobs to download configurations and to fetch configurations. For NetShow
and VLAN Fetch, you can set the protocol order to download configurations.
For more information, see Configuring Transport Protocols in Administration of Cisco Prime LAN
1-12
OL-25957-01
Chapter 1

Template Center Enhancement

In LMS 4.2, you can create Configuration templates using IF and FOREACH statements.
For more information, see Guidelines for Creating Configuration Templates Using IF and FOREACH
Statements in Configuration Management with Cisco Prime LAN Management Solution 4.2.
Third-Party Software and Tool Changes

The following are the changes in the third-party software and tools in this release:
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
Support for Windows 2012 Standard Edition and Data Center Edition on server and client systems
Note
For Windows 2012 support, install LMS 4.2 using CiscoPrime_LMS_4.2_WIN12.exe file
and then upgrade to LMS 4.2.5 by following the conventional installation steps.
WinPcap upgrade to 4.0.2
Daylight Savings Timezone tool upgrade to 1.3.45-b01
Firefox 8.0 and 9.0 support on client systems
Java Plug-in version 1.6.0_24 or later update versions only
Apache upgrade to 2.2.17
Java Runtime Environment (JRE) 1.6.0_24

You can freshly install LMS 4.2 and then perform remote data migration. LMS 4.2 supports direct inline
upgrade from LMS 4.1, and LMS 4.0.1.
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.
Selective Backup - Process by which only required system configurations and data can be backed up.
The following migration paths are available for the customers.
LMS 4.1
LMS 4.0.1
LMS 3.2 SP1
For the following versions, you must migrate to LMS 3.2 SP1, and then install LMS 4.2:
LMS 3.1
LMS 3.0 Dec 2007 update
LMS 3.0
LMS 2.6 SP1

OL-25957-01
1-13
Chapter 1
Note
LMS 2.6
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.

Table 1-3 lists the Network Management Systems (NMS) supported by Integration Utility 1.11, which
is part of LMS 4.2.
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-14
OL-25957-01
Chapter 1

Table 1-3
Network Management System

HP OpenView 9.1, 9.01, 9.0, 8.13, 8.1
Supported Platforms
Windows
Windows 2008 R2 Standard x 64 Edition
Windows 2008 Server Standard Edition Release 1

with SP1 and SP2
Windows 2008 Enterprise Edition Release 1 with SP1

and SP2
Windows Server 2008 R2 Standard Edition
Windows Server 2008 R2 Enterprise Edition

Note Only 64-bit Operating Systems are
supported on the above versions.
Note
Solaris
Solaris 10
Both local and remote integration are supported for these

platforms.
Soft Appliance
Note
Only remote integration is supported for Soft

Appliance.
For information on integrating HP OpenView- LMS, see

NNMi Deployment Guide on the HP site.

OL-25957-01
1-15
Chapter 1
Table 1-3
Supported Network Management Systems (continued)
Network Management System

HP OpenView 7.53, 7.51, 7.50
Supported Platforms
Windows:
with SP1 and SP2

and SP2

Only 64-bit Operating Systems are supported on
the above versions.
Note
Solaris
NetView 7.1.4, 7.1.5
Solaris 10
Only remote integration is supported for the above

platforms.
Windows:
with SP1 and SP2

and SP2
Note
Only 64-bit Operating Systems are supported on

the above platforms.
Only remote integration is supported for the above

platforms.
1-16
OL-25957-01
Chapter 1

Supported Devices
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/
User Guide for CiscoView 6.1.9

CiscoView manages and configures different types of Cisco devices. You can refer this document
for information on supported devices. This document is available on Cisco.com at this URL:
http://www.cisco.com/en/US/products/sw/cscowork/ps4565/products_user_guide_list.html
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
Select the Software Product Category as Cloud and Systems Management.
Step 3
Select Routing and Switching Management > Cisco Prime LAN Management Solution.
Step 4
Select Cisco Prime LAN Management Solution 4.2.
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
Select a product release version from the Latest Release folder.

The device packages corresponding to the selected product version display at the right of the web page.
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/

OL-25957-01
1-17
Chapter 1
Supported Devices
1-18
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.
System and Browser Requirements for Server and Client
Terminal Server Support for Windows Server
Solaris Patches
LMS 4.2 Port Usage
Important URLs

OL-25957-01
2-1
Chapter 2
Prerequisites

Before you begin to install LMS software, you must check if your system meets the recommended
prerequisites.
The recommended LMS 4.2 server and client requirements on the supported operating systems are based
on the license that you use on a single server or multi-server setup.
This section contains the following:
Disk Space Requirements
Operating System Requirements
Server Requirements on Solaris Systems
Server Requirements on Windows Systems
Server Requirements on Virtualization Systems
System Requirements on Client Systems
Disk Space Requirements

The disk space required to install LMS 4.2 on Solaris and Windows is:
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

The operating system requirements are listed in Table 2-1.
This section contains:
Storage Area Network Support
Link Aggregation Support in Solaris 10

OL-25957-01
2-3
Chapter 2
Prerequisites
Table 2-1
Operating
System
Requirements
Solaris
LMS 4.2 supports the following Solaris 10 releases:
Solaris 10, 10/09 release
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
LMS 4.2 supports the following Windows systems:
Windows 2008 Standard Edition Release 1 with SP1 and SP2
Windows 2008 Enterprise Edition Release 1 with SP1 and SP2
Note
Only 64-bit Operating Systems is supported on the above versions.
Windows Server 2008 R2 Standard Edition with SP1
Windows Server 2008 R2 Enterprise Edition with SP1
Note
Only 64-bit Operating Systems are supported on the above versions.
Windows Server 2012 R2 Standard Edition with SP1
Windows Server 2012 R2 Enterprise Edition with SP1
Note
Only 64-bit Operating Systems are supported on the above versions.
2-4
OL-25957-01
Chapter 2
Prerequisites
LMS 4.2 supports the following Virtualization Systems:
VMware ESX server 3.0.x
VMware ESX Server 3.5.x
VMWare ESX Server 4.0.x
VMWare ESX Server 4.1
VMWare ESXi Server 4.0
VMware ESXi Server 4.1
VMware ESXi Server 5.0
Hyper V Virtualization (As an installable in Windows 2008)
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.
Note
ESXi 5.1 will be supported from LMS 4.2.4 onwards.
Storage Area Network Support

LMS runs on Storage Area Network (SAN) which is connected to the Host server through a Fiber
Channel. The server requirements on SAN environment remains the same as the server requirements on
Windows and Solaris systems. See Server Requirements on Solaris Systems and Server Requirements
on Windows Systems for the recommended server hardware requirements.
Link Aggregation Support in Solaris 10

A link aggregation consists of several interfaces on a system that are configured together as a single,
logical unit. Link aggregation is defined in the IEEE 802.3ad Link Aggregation Standard.
Link Aggregation Standard (IEEE 802.3ad) provides a method to combine the capacity of multiple
full-duplex Ethernet links into a single logical link. This link aggregation group is then treated as a single
link. The server requirements on a link aggregated environment remains the same as the server
requirements on Solaris systems. See Server Requirements on Solaris Systems for the recommended
server hardware requirements.
Configuring Link Aggregation in a Solaris Environment
Verifying the Link Aggregation
Configuring Link Aggregation in a Solaris Environment

This section explains how to configure link aggregation in a Solaris environment. The example in this
procedure aggregates sample interfaces bge0 and bge1.
Step 1
Configure the links (in this example, bge0 and bge1) with two different IP addresses in the same
network.

OL-25957-01
2-5
Chapter 2
Prerequisites
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.
Step 3
Unplumb both the NICs using the command:
Step 4
Ifconfig bge0 unplumb
Ifconfig bge1 unplumb
Create the link aggregation group using the command:
dladm create-aggr d bge0 d bge1 2 key
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.
ifconfig aggr2 plumb
ifconfig aggr2 public IP address subnet mask up
For example, ifconfig aggr 2 10.77.210.210 255.255.255.192 up.

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
Verifying the Link Aggregation

To verify the Link Aggregation:
Step 1
Check the statistics by using the following command in the link aggregated server:
dladm show-aggr
A sample output is:

Key: 2 (0x0002) policy: L4
address
speed
duplex link
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
address: 0:14:4f:90:1e:ba (auto)
Device
state
The state of the links should appear as attached in the output, else, the link aggregated server
will not work when the NIC fails.
Reboot the server by using the following command:

reboot-- -rv
Link aggregation is also supported in an HA environment. To configure link aggregation in HA

environment please refer Setting Up Cisco Prime LMS in High Availability and Disaster Recovery
Environment.
2-6
OL-25957-01
Chapter 2
Prerequisites
Server Requirements on Soft Appliance Systems

To manage 10,000 devices in LMS 4.2, you must set up more than one servers.
The LMS Soft Appliance is available in three different SKUs according to the number of devices that
you want to manage:
Upto 500 devices (Standard)
500 to 1500 devices (Medium)
1500 to 5000 devices (Large)
Table 2-2 lists the Software and Hardware Requirements for LMS Soft Appliance (OVA image).
Table 2-2
Software and Hardware Requirements for Soft Appliance (OVA image)
Component
Virtualization Systems
Hard disk space

Memory and CPU
Requirement
Recommended Memory
Requirement
VMWare ESX server 4.1
VMware vSphere Hypervisor (ESXi server 4.1)
VMware vSphere Hypervisor (ESXi server 5.0)
256 GB
4 GB, 2 virtual CPU (< = 500 devices)
8GB, 4 virtual CPU (< = 1500 devices)
16GB, 8 virtual CPU ( > 1500 devices)
8 GB (< = 500 devices)
12 GB (< = 1500 devices)
Swap space
32 GB
Host CPU Core clock speed
Minimum 2.26 GHz
Minimum Virtual CPU

Reservations
Number of recommended virtual CPUs x 2.26 GHz:
Resource Memory
Configuration
Note
Recommended Requirement
4520 MHz (< = 500 devices)
9040 MHz (< = 1500 devices)
18080 MHz ( > 1500 devices)
4096 MB (< = 500 devices)
8192 MB (< = 1500 devices)
16384 MB ( > 1500 devices)
When you use incremental licenses for the LMS Soft Appliance, you must ensure that you configure the
virtual CPUs mentioned in Table 2-2.

OL-25957-01
2-7
Chapter 2
Prerequisites
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
Processor clock speed
2.4 GHz
Number of processors
Processor model
Intel Xeon E5620
Processor number of cores
Cache
12 MB
Hard disk interface
SAS & SATA
Chassis type
Rack (1U)
Maximum storage capacity
2 TB
The following UCS models are supported for installing ISO image:
Cisco UCS B-series blade servers (B200-M1 or M2 and B250-M1 or M2)
Cisco UCS C-series rack-mount servers (C200-M1 or M2, C210-M1or M2, and C250-M1 or M2 and
Cisco UCS C460).
Cisco Prime Network Control System (NCS) appliance
Table 2-3 explains the hardware requirements for the above-mentioned UCS servers.
2-8
OL-25957-01
Chapter 2
Prerequisites
Server Requirements on Solaris Systems

Table 2-4 lists the server requirements for installing LMS 4.2 software on Solaris systems. Table 2-5
lists the recommended server requirements for installing LMS 4.2 software on Solaris systems for
Incremental Licenses.
Table 2-4
Recommended Server Hardware Requirements on Solaris Systems for Different

Licenses
Component
Recommended Server System Requirement
LMS 50
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
bit OS
Recommended: 8 GB RAM and 16 GB swap space
LMS 100

dual stack OS
LMS 300 (Upgrade from previous version) 1 CPU with dual core or 2 CPU with single core 4 GB
dual stack OS
LMS 500
2 CPUs with dual core or 4 CPU with single core 8 GB

dual stack OS
LMS 750 (Upgrade from previous version) 2 CPUs with dual core or 4 CPU with single core 8 GB
bit OS
LMS 1000

bit OS
LMS 1500 (Upgrade from previous

version)
2 CPUs with quad core or 4 CPU with dual core,16 GB

RAM and 32 GB swap space, 60 GB free disk space,
64-bit OS
LMS 2500

64-bit OS
LMS 5,000
2 CPUs with 8 core or 4 CPU with quad core 16 GB RAM

and 32 GB swap space, 120 GB free disk space, 64 bit OS
Note
You can use one or more servers to

manage upto 5000 devices.

OL-25957-01
2-9
Chapter 2
Prerequisites
Table 2-4
Recommended Server Hardware Requirements on Solaris Systems for Different

Licenses (continued)
Component
LMS 10,000 server:
For LMS Server managing Configuration Functionality

for upto 10,000 devices only:
Configuration Functionality will

support up to 10,000 devices
2 CPUs with 8 core or 4 CPUs with quad core 16 GB

RAM and 32 GB swap space, 64 bit OS
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-10
OL-25957-01
Chapter 2
Prerequisites
Table 2-5
Recommended Server Hardware Requirements on Solaris Systems for Incremental

Licenses
License
Upto LMS 300

bit OS
> LMS4.2 300 to LMS4.21.5K

RAM and 16 GB swap space,64 dual stack OS
> LMS4.21.5K to LMS4.22.5K
2 CPUs with quad core or 4 CPU with dual core 16 GB

> LMS4.22.5K to LMS4.2-5 K

and 32 GB swap space, 64 bit OS
The following processors are supported on a Solaris system:
Note
UltraSPARC IIIi processor
UltraSPARC IV processor
UltraSPARC IV+ processor
UltraSPARC T1 processor
UltraSPARC T2 processor
UltraSPARC T2+ processor
SPARC64 VI processor
SPARC64 VII processor
Minimum processor speed must be 1.35 Ghz or higher

See Solaris Patches for information on required and recommended server patches on Solaris systems.

OL-25957-01
2-11
Chapter 2
Prerequisites
Server Requirements on Windows Systems

Table 2-6 lists the server requirements for installing LMS 4.2 software on Windows systems. Table 2-7
lists the recommended server hardware requirements on windows systems for incremental licenses.
To manage LMS 10,000 devices in LMS 4.2, you must set up more than one servers.
For a list of Windows HotFix patches, see the Q.Which Windows HotFix patches are supported for
LMS 4.2?
Table 2-6
Recommended Server Hardware Requirements on Windows Systems for Different

Licenses
Component
LMS 50

bit OS
LMS 100

dual stack OS
LMS 300 (Upgrade from previous version) 1 CPU with dual core or 2 CPU with single core 4 GB
dual stack OS
LMS 500

dual stack OS
LMS 750 (Upgrade from previous version) 2 CPUs with dual core or 4 CPU with single core 8 GB
bit OS
LMS 1000

bit OS
LMS 1500 (Upgrade from previous

version)

64-bit OS
LMS 2500

64-bit OS
LMS 5,000
Note

You can use one or more servers to and 32 GB swap space, 120 GB free disk space, 64 bit OS
manage upto 5000 devices.
2-12
OL-25957-01
Chapter 2
Prerequisites
Table 2-6
Recommended Server Hardware Requirements on Windows Systems for Different

Licenses (continued)
Component
LMS 10,000 server:
For LMS Server managing Configuration Functionality

for upto 10,000 devices only:
Configuration Functionality will

support up to 10,000 devices
2 CPUs with 8 core or 4 CPUs with quad core 16 GB

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
Recommended Server Hardware Requirements on Windows Systems for Incremental

Licenses
License
LMS 50 to LMS 300

bit OS
> LMS 300 to LMS 1.5K

RAM and 16 GB swap space, 64 dual stack OS
Note
> LMS 1.5K to LMS 2.5K
2 CPUs with quad core or 4 CPU with dual core 16 GB

RAM and 32 GB swap space,64 bit OS
> LMS 2.5K to LMS 5 K

and 32 GB swap space,64 bit OS
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.

OL-25957-01
2-13
Chapter 2
Prerequisites
Table 2-8
Recommended Server Hardware Requirements on Windows Systems with HUM
Component
LMS Bundle Hardware Configuration
HUM 50 + LMS 300
One CPU with 2 GB RAM memory and 4 GB swap

space.
HUM 300 + LMS 1500
2 CPUs with 4 GB RAM memory and 8 GB swap

space.
Standalone Hardware Configuration
HUM 50

space.
HUM 300

space.
HUM 1000
Two CPUs with 4 GB RAM memory and 8 GB swap

space.
2-14
OL-25957-01
Chapter 2
Prerequisites
The following processors are supported on a Windows system:

Intel processors
Intel Xeon processor
Intel Core Duo processor T2600 - T2300
Quad Core Intel Xeon
Intel-VT processors (VMware Optimized hardware)
Intel Xeon processor 5400 series
AMD processors
Note
AMD Opteron Processor
AMD Athlon 64 FX Processor
AMD Athlon 64 X2
AMD -V
Minimum processor speed must be 2.33 Ghz or higher
Dual-Core AMD Opteron Processor
AMD Opteron Processor
AMD Athlon 64 FX Processor
AMD Athlon 64 X2 Dual-Core
Server Requirements on Virtualization Systems
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
AMD-V
IBM X3550 M3
Intel Xeon Processor 5600 series

OL-25957-01
2-15
Chapter 2
Prerequisites
Unified Computing System (UCS) Support

LMS 4.2 is supported on the UCS B-series blade servers (B200-M1 or M2 and B250-M1 or M2) and
C-series rack mount servers (C200-M1 or M2, C210-M1 or M2, C250-M1 or M2, and UCS C460). The
server requirements on UCS blade servers and rack mount servers remains the same as the server
requirements on Windows systems. Please refer Table 2-6 for the recommended server hardware
requirements on windows systems
The supported processor in UCS B-series blade servers is Intel Xeon 5500 or 5600 Series processors.
For more information see
http://www.cisco.com/en/US/prod/collateral/ps10265/ps10280/data_sheet_c78-524797_ps10279_Prod
ucts_Data_Sheet.html
The supported processor in UCS C-series rack amount servers is Intel Xeon 5500 or 5600 Series
processors with their choices mentioned explicitly. For more information see
http://www.cisco.com/en/US/products/ps10493/products_data_sheets_list.html
System Requirements on Client Systems

The following table lists the client system requirements for all platforms:
Table 2-9
Recommended Client Hardware and Software Requirements
Component
Recommended Client System Requirement
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 XP with Service Pack 2 and Service Pack 3
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)
Windows 7 with Service Pack 1
Internet Explorer 8.0, 9.0 Standards Mode (Press F12 and select Standards
Mode)
Firefox 8.0 and 9.0 for Windows
Note
Only 32-bit IE and FF browsers are supported
2-16
OL-25957-01
Chapter 2
Prerequisites
Table 2-9
Recommended Client Hardware and Software Requirements
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.

You can install LMS 4.2 software on a system with Terminal Services enabled in Remote Administration
mode. However, you cannot install Common Services on a system with Terminal Services enabled in
Application mode.
If you have enabled Terminal Server in Application mode, you should disable the Terminal Server,
reboot the system, and start the installation again.
Enabling and Disabling FIPS on Windows 2008 Servers
Table 2-10 summarizes the Terminal Services features in Windows Server.

.
Table 2-10
Terminal Services on Windows Server
Windows 2008 Servers
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.

To enable/ disable Terminal Server, use the Terminal Services Manager tool.
To enable/ disable Remote Desktop:
Step 1
Go to Control Panel > System.
Step 2
Click Remote Settings under Tasks > Remote

OL-25957-01
2-17
Chapter 2
Prerequisites
Step 3
Select the Allow connections from computer running any version if Remote Desktop option.
2-18
OL-25957-01
Chapter 2
Prerequisites
Solaris Patches
Enabling and Disabling FIPS on Windows 2008 Servers

Sometimes, Federal Information Processing Standard (FIPS) compliant encryption algorithms are
enabled for Group security policy on Windows server.
When the FIPS compliance is turned on, the SSL authentication may fail on LMS Server. You should
disable the FIPS compliance for the LMS to work properly.
To enable or disable FIPS on Windows 2008 servers:
Step 1
Go to Start > Settings > Control Panel > Administrative tools > Local Security Policy.
The Local Security Policy window appears.
Step 2
Click Local Polices > Security Options.
Step 3
Select System cryptography: Use FIPS compliant algorithms for encryption, hashing, and signing.
Step 4
Right-click the selected policy and click Properties.
Step 5
Select Enabled or Disabled to enable or disable FIPS compliant algorithms.
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

Table 2-11 lists the required and recommended patches for Solaris 10.
The required patches are mandatory for all LMS features to function properly. Some of the LMS features
may not work if the mandatory patches are not installed on your system.

OL-25957-01
2-19
Chapter 2
Prerequisites
Solaris Patches
For more information, see www.oracle.com.

Table 2-11
Operating
System
Solaris 10
Solaris Patches
Required Server Patches are 122032-05 and 127127-11
Minimum system level must be 11/06 release or higher.

To find out the current operating system level, enter the following command:
# more /etc/release
For example, the system displays the following information:

Solaris 10 11/06 s10s_u2wos_09a SPARC
Copyright 2006 Sun Microsystems, Inc. All Rights Reserved.
Use is subject to license terms.
Assembled 11 November 2006
Use showrev -p command to verify that these patches have been applied.
Note
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
Required Server patches
Error message appears with a prompt to continue or quit the

installation.
This system does not have the following required Server
patches
Installation can proceed without the required Server
patches.However, you must install the required patches
listed above before running LMS.
Do you want to continue the installation? (y/n) [y]:
Required Client patches
Error message appears with a prompt to continue or quit the

installation.
This system does not have the following required Client
patches.
These patches are required if only this system is used
as a LMS client.
We recommend you to download and install the latest required and recommended patches from
www.oracle.com before you run LMS 4.2.
2-20
OL-25957-01
Chapter 2
Prerequisites
LMS 4.2 Port Usage
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]:
LMS 4.2 Port Usage

The table below lists the ports used by the various LMS components.
If you have enabled firewall in your LMS Server, you must open or free up the following ports:
HTTP or HTTPS port
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
TACACS+ and ACS
49
Functionality
Common Services
Configuration and Software

Image Management
Network Topology, Layer 2

Services and User Tracking
Fault Management
TCP
25
Simple Mail Transfer

Protocol (SMTP)
Common Services (PSU)
TCP
22
Secure Shell (SSH)
Common Services,

Inventory, Config and Image

Management
Direction
(of Establishment)
of Connection
Server to ACS
Server to SMTP
Server
Management
Server to Device

OL-25957-01
2-21
Chapter 2
Prerequisites
LMS 4.2 Port Usage
Port
Protocol Number
Service Name
TCP
Telnet
UDP
UDP
23
69
161
Functionality
Common Services


Management
Trivial File Transfer

Protocol (TFTP)
Common Services
Inventory, Config and Image Device to Server

Management
Simple Network
Management Protocol
(SNMP)
Common Services
Server to Device
CiscoView
Device to Server

Management

Fault Management
IPSLA Performance
Management
Device Performance
Management
514
Remote Copy Protocol
Common Services
UDP
162
SNMP Traps (Standard

Port)

Fault Management
Common Services
Inventory, Config & Image

Management
514
Server to Device
TCP
UDP
Direction
(of Establishment)
of Connection
Syslog
Server to Device
Server to Device
Device to Server
Device to Server
UDP
14311
Trap Listener to MAC

Notification Traps

Device to Server
UDP
9000
Trap receiving (if port

162 is occupied)
Fault Management
Device to Server
UDP
162362
UT Host acquisition

End host to Server
TCP
443
LMS HTTP server in

SSL mode
Common Services
Client to Server
Server Internal
2-22
OL-25957-01
Chapter 2
Prerequisites
LMS 4.2 Port Usage
Port
Protocol Number
Service Name
TCP
LMS HTTP Protocol
1741
Functionality
Common Services
CiscoView

Inventory, Config & Image

Management
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
ESS (used for Java

Management
Extensions)
Common Services
Server Internal
TCP
8898
Log Server
Fault Management
Server Internal
TCP
9002
DynamID authentication (DFM Broker)
Fault Management
Server Internal
TCP
9007
Tomcat shutdown
Common Services
Server Internal
TCP
9009
Ajp13 connector used

by Tomcat
Common Services
Server Internal
UDP
9020
Trap Receiving
Fault Management
Server Internal
UDP
14004
Lock port for ANI

Server singlet on check

Server Internal
TCP
15000
Log server
Fault Management
Server Internal
TCP
4005040070
CSTM ports used by CS Common Services

applications, such as
Grouping Services,
Device and Credential
Repository (DCR)
Server Internal
TCP
40401
LicenseServer
Common Services
Server Internal
TCP
43242
ANIServer

Client to Server
TCP
42340
LMS Daemon Manager Common Services

- Tool for Server
Processes
Server Internal
TCP
42344
ANI HTTP Server
Server Internal
Common Services

OL-25957-01
2-23
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
Inventory, Config and

Image Management
Database

Management
Server Internal
TCP
43443
ANIDbEngine

Server Internal
TCP
43445
Fault History Database
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

Management
Server Internal
TCP
49000-49 CSTM Port

040

Management
Server Internal
TCP
50001
SOAPMonitor

Management
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-24
OL-25957-01
Chapter 2
Prerequisites
LMS 4.2 Port Usage
Port
Protocol Number
Service Name
Functionality
Direction
(of Establishment)
of Connection
TCP
8161
ESS
Common Services
Server Internal
TCP
50002
IPMOGSServer
CSTM ports used by IPMOGSServer, such as Grouping and

Filering services
Server Internal
TCP
50003
IPMProcess
CSTM ports used by IPMProcess, such as IPSLA collector

creation, Edit, Delete, and
Polling
Server Internal
TCP
4430044301
UPMProcess
CSTM ports used by UPMPro- Server Internal

cess, such as Poller management
(Creation, Edit, Delete) and
Polling Engine
TCP
14017
EPMServer
Port to open a server socket to

Server Internal
ensure only one running system.
UDP
14004
Network Topology,
Layer 2 Services and
User Tracking
Lock port for ANI Server singlet Server Internal

on check
TCP
5500055020
Network Topology,
User Tracking
CSTM Port for Campus Manager Server Internal
TCP
4444
SyslogCollector
Listens to this port and retrieves Server Internal

the syslog from syslog.log file. It
does the processes of validation,
filtering and forwarding the
syslogs to the local/remote
servers in which they are subscribed
TCP
3333
SyslogAnalyzer
Analyzer listens to this port and Server Internal

collects the syslog from collector. This process would trigger
automated actions for the syslog
and finally inserts to the database
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.

OL-25957-01
2-25
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
IOS image download
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=l
atest#
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=l
atest#
Bug Toolkit
2-26
OL-25957-01
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
Compliance and Audit Management
Download
Contractshttps://apps.cisco.com/CustAdv/ServiceSales/contract/viewContractMgr.do?method=v
iewContractMgr
Download Compliance Policy

Updateshttp://www.cisco.com/cisco/software/release.html?mdfid=284259296&flowid=31102&
softwareid=284270571&release=1.0.0&relind=AVAILABLE&rellifecycle=&reltype=latest

You must configure several important device credentials correctly on every Cisco device that will be
managed and monitored through LMS. You must also enter the correct device credentials in the Device
and Credential Repository (Inventory > Device Administration > Add / Import / Manage Devices).
Table 2-12 lists all the functionalities and the device credentials required.
.
Table 2-12
LMS Functionalities and Device Credentials
Functionalities
Telnet/SSH
Password
Enable Password
SNMP Read Only
SNMP Read /
Write
Common Services
Not required
Not required
Required
Required
Network Topology, Layer 2 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 Required

(Telnet)
Required
Required
Not required
Configuration
Management1 (TFTP) 2
Not required
Not required
Required
Required
NetConfig
Required
Required
Required
Required

OL-25957-01
2-27
Chapter 2
Prerequisites
Table 2-12
LMS Functionalities and Device Credentials (continued)
Functionalities
Telnet/SSH
Password
Enable Password
SNMP Read Only
SNMP Read /
Write
Config Editor
Required
Required
Required
Required
NetShow
Required
Required
Required
Not required
Software Management
Required3
Required3
Required
Required
Port and Module

Configuration
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-28
OL-25957-01
CH A P T E R
Preparing to Install Cisco Prime LAN

This chapter lists the necessary information that prepares you to perform an installation of LMS 4.2 on
Soft Appliance, Windows, and Solaris systems.
Before You Begin Installation
Licensing Your Product
Application Scaling Numbers

This section captures the terms and definitions that are used while installing LMS 4.2.
See Licensing Your Product to understand the licensing terminologies.
For more information on Password rules and descriptions, see Password Information.
LMS Application Database Password
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:
LMS Admin Password

An administrative password used while logging into the LMS server as administrator. Use a
minimum of five characters.
Ensure that you have noted down the password.
You are prompted to enter this password during installation.
Self Signed Certificate

LMS allows you to create security certificates to enable SSL communication between your client
browser and management server.

OL-25957-01
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.

This section contains the following important information that you should read before you begin
installation:
Installation Notes
Installation Notes (For Solaris Only)
Installation Notes (For Windows Only)
Installation Notes
Before you begin the installation, read the following notes:
Close all open or active programs. Do not run other programs during the installation process.
While setting up High Availability (HA) and Disaster Recovery (DR) environment in LMS server,
ensure to set them prior to LMS installation.
By default, SSL is not enabled on LMS Server.
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.
LMS 4.2 is installed in the default directories:

On Solaris and Soft Appliance: /opt/CSCOpx
On Windows, 64 bit: SystemDrive:\Program Files<x86>\CSCOpx
Where, SystemDrive is the Windows operating system installed directory.

If you select another directory during installation, the application is installed in that directory.
The destination folder should not contain the following special characters:
On Solaris and Soft Appliance:
3-2
OL-25957-01
Chapter 3

!@#$%^&*()+|}{":[];'?<>,.`=~
On Windows:
!@#$%^&*()+|}{"[];'/?<>,.`=
If errors occur during installation, check the installation log file:

On Solaris and Soft Appliance, check the installation log file
/var/tmp/Cisco_Prime_install_YYYYMMDD_hhmmss.log for LMS 4.2 installation

Where YYYYMMDD denotes the year, month and date of installation and hhmmss denotes the
hours, minutes and seconds of installation.
For example:
/var/tmp/Cisco_Prime_install_20110721_182205.log
On Windows, check the installation log in the root directory on the drive where the operating
system is installed. Each installation creates a new log file.

For example, for LMS 4.2, the installation log file is:
C:\Cisco_Prime_install_YYYYMMDD_hhmmss.log, where YYYYMMDD denotes the year,
month and date of installation and hhmmss denotes the hours, minutes and seconds of
installation.
For example:
C:\Cisco_Prime_install_20100721_182205.log
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
We recommend that you do not terminate the installation while it is running.
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.
Installation Notes (For Solaris Only)
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.

OL-25957-01
3-3
Chapter 3
To preserve all the attributes including timestamp:

a. Change the present working directory to the directory to which the DVD is mounted using the
command:
cd /cdrom/cdrom0
where cdrom/cdrom0 is the directory to which the DVD is mounted.

b. Create a directory where you want to copy the contents of the disk by entering:
mkdir /opt/copydisk
Make sure that this directory has enough space to hold the entire contents of the disk.
c. Enter:
tar cpf - . | (cd /opt/copydisk && tar -xpf -)
This command preserves all attributes including the timestamp.
Installation Notes (For Windows Only)
You can install LMS 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.
Soft Appliance OVA software can be installed only on VMware environment.
We recommend that you disable the virus scan software on your system.
In VMWare, the resources should not be in shared mode.

The LMS 4.2 product provides features such as software-based product registration and license key
activation technologies. While you are installing LMS, the installer displays the Registration and
Licensing input dialog box.
Understanding Product Ordering Options and Product Authorization Key
License Information
License File
Evaluation Mode
NFR (Not For Resale) License
Installing the License File
Understanding Product Ordering Options and Product Authorization Key

Product Authorization Key (PAK) ID refers to the identification key that you must enter while registering
your product in Cisco.com to receive the product serial license key.
The PAK is normally printed on the software claim certificate that is part of the product DVD kit.
With the new ordering options introduced, you can receive the digital PAK IDs through online delivery
also.
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:
Compliance Profile Execution
Compliance Policy and Groups

OL-25957-01
3-5
Chapter 3
HIPAA Compliance Reports
SOX(COBIT) Compliance Reports
ISO/IEC 27002 Compliance Reports
NSA Compliance Reports
PCI DSS Compliance Reports
Department of Homeland Security (DHS) Checklist Reports
Defense Information Systems Agency (DISA) Checklists
Center for Internet Security (CIS) Benchmarkss
The following Compliance and Audit Reports are supported only by LMS license and do not require
CAAM server license.
Service Reports
Lifecycle Management Reports
Vendor Advisory 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.
Available Licenses for LMS 4.2
Upgrading to a Higher SKU on Soft Appliance Systems
See Application Scaling Numbers for further deployment related information.
Available Licenses for LMS 4.2

For availability, ordering, upgrade, and licensing options refer to www.cisco.com/go/lms.
Upgrading to a Higher SKU on Soft Appliance Systems

Before you upgrade your Soft Appliance system from a lower SKU to a higher SKU, ensure that your
system meets the recommended hardware and software specifications mentioned in Server Requirements
on Solaris Systems.
To upgrade your Soft Appliance system from a lower SKU to a higher SKU:
Step 1
Shut down the VM from the vSphere client.
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
Switch on the VM and update the license.
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.
Transferring Files to Soft Appliance Server

In the LMS Soft Appliance when you specify the location of the License file or some other file, you must
use FTP/SFTP/SCP commands to transfer files to the Soft Appliance server:
To transfer files to or from the Soft Appliance server:
Step 1
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
To log into the shell:
Note
Step 3
a.
Enter the command shell.
b.
Enter the shell password.
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:

OL-25957-01
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
Ensure that the file to be transfered is available in the FTP server.

To transfer the file to the Soft Appliance, use the below command:
ftp>get FILE_NAME
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
Ensure that the file to be transfered is available in the SFTP server.

To transfer the file to the Soft Appliance, use the below command:
sftp>get FILE_NAME
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.
LMS 50 Devices Restricted License

If you apply LMS 50 Devices Restricted license on a LMS server which has an evaluation license or any
other restricted device license types installed, the LMS Server allows you to manage a maximum of 50
devices only. The remaining devices would be moved to suspended state automatically.
In this scenario, there are possibilities that the devices that are supposed to be in the managed state might
be moved to suspended state. On the other hand, some devices that are not required to be managed might
be in managed state.
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.
Guidelines to Avoid Necessary Devices Being Moved to Suspended State

To avoid necessary devices being moved to suspended state, follow any one of the procedure mentioned
below:
Install the appropriate purchase license while installing the product.

Or
Before applying the 50 SKU license, you can select the particular set of 50 devices by configuring
the Group Policy.
To configure the Group Policy, select Inventory > Device Administration > Device Allocation
Policy > Manage By Groups from the LMS menu.
Using the group policy you can move the remaining unnecessary devices to unmanaged state.
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.
Device States After Backup and Restore in a LMS 50 SKU Server

Consider two LMS servers S1 and S2 with S1 managing more than 50 devices and S2 applied with
LMS 50 devices restricted license.
If data is backed up from S1 and restored in S2, then the device states in S2 will be as follows:

OL-25957-01
3-9
Chapter 3
The device count that matches the current license count (LMS 50) will be in the managed state in
UDM.
The remaining devices will move to the suspended state.
To handle this scenario, see Guidelines to Avoid Necessary Devices Being Moved to Suspended State.
NFR (Not For Resale) License

NFR (Not For Resale) License is a default license that is valid for only 365 days. It allows you to manage
up to 100 devices.
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.
SeePerforming 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
Launch LMS 4.2
Step 2
Select Admin > System > License Management.

The License Administration page appears.
Step 3
Click Update.
Step 4
Enter the path to the NFR license file in the License field, or click Browse to locate the NFR license file.
Step 5
Click OK to apply the license.
3-10
OL-25957-01
Chapter 3

Installing the License File

We recommend that before installing the LMS 4.2 product, you register the product and receive a
permanent license.
Figure 3-1 describes the steps that you must follow for licensing your product.
Figure 3-1
Steps to Follow For Licensing LMS
Login to
Cisco.com
Register your PAK

in Cisco.com
Receive the
License file
Provide the
License file during
installation
Example 1: 4XCD##V####
275801
Product Authorization Key (PAK)

(Printed on Software License Claim Certificate)
To license your product and install the license file, you must:
Step 1
Log onto Cisco.com to get your 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. After successful registration, you will receive your license file
information through an e-mail.
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
Install the license file.

If you have obtained the LMS license before installation:
a.
Select the LMS application to install and when prompted:

On Windows, select the first radio button and use the browse window to locate the license file
directory.
On Solaris, select L for License File after you accept the Licensing Agreement and continue
installing the application.

b.
Click Next to install the license file.

OL-25957-01
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.
Select Admin > System > License Management.

The License Administration page appears.
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.

This section presents information on the specific scaling numbers for each of the LMS functionalities in
LMS server:
3-12
OL-25957-01
Chapter 3

The scaling numbers for LMS are as follows:

Functionality
Scalability Limit on LMS Server
Grouping Services
For upto LMS 500 Device licenses, the following are the scaling limits:
30 user-defined groups
15 IPSLA groups
10 Fault groups
15 Port and Module Groups
For LMS 500 to LMS 1000 Device licenses, the following are the scaling
limits:
100 IPSLA groups
50 Fault groups
For LMS 2500 Device licenses, the following are the scaling limits:
200 IPSLA groups
50 Fault groups
For LMS 5000 Device licenses, the following are the scaling limits:
100 IPSLA groups
50 Fault groups
Note

Image Management
The recommended limit for creating user-defined group is 200, but

you are allowed to create upto 600 user-defined groups in LMS.
In a LMS server, when only this functionality is managed, it supports the

following:
10,000 devices
200 Port and Module Configuration (PMC) groups with 90% port
groups and 10% module groups
Maximum of 500,000 ports with an average of 50 ports per device
Maximum of 100,000 ports in a port and Module Configuration group
Maximum of 250,000 ports for each LMS job
In addition to the above, Syslog reports can contain upto 40,000 records

OL-25957-01
3-13
Chapter 3
Functionality
Network Topology, Layer

2 Services and User
Tracking
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
The recommended MIB objects scaling numbers are as follows:
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.
You can manage a maximum of 2000 collectors on enabling all the

device management functions including IPSLA Performance
Management functionality. This collector limit includes:
1500 collectors (hourly polling frequency)
500 collectors (minute polling frequency)
You can manage a maximum of 5000 collectors on disabling other

device management functions and managing the IPSLA Performance
Management functionality only. This collector limit includes:
4500 collectors (hourly polling frequency)
500 collectors (minute polling frequency)
For LMS 5000 device license, you can manage a maximum of 5000
collectors with hourly polling frequency.
If you want to manage 5000 collectors without disabling any of the

device management functions, you can manage:
2000 collectors in a Solution Master server with 5000 device
license
3000 collectors in a Slave server with LMS Monitoring Server
large edition license (add-on license to manage additional

performance collectors). See NoteThe AutoIPSLA generated
collectors are accounted for license. for details on LMS
Monitoring Server licenses.
Note
The IPSLA Monitoring Collector license limit applies only to

historical hourly collectors and not to real-time collectors. However,
you are allowed to create real-time collectors even after the license
limit is reached. There is no limit to the number of real-time collectors
that you could create to manage IPSLA Monitoring functionality.
The AutoIPSLA generated collectors are accounted for license.
Concurrent Users Supported

LMS 4.2 can support:
3 concurrent users for upto 500 devices
5 concurrent users for 500 to 2500 devices
10 concurrent users for 5000 and 10 K devices.

OL-25957-01
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
Setting Up Cisco Prime LMS in High Availability

and Disaster Recovery Environment
This chapter explains setting up LMS in a High Availability (HA) and Disaster Recovery (DR)
environment on Windows and Solaris systems. The High Availability solution is based on Symantecs
Veritas Storage Foundation products.
This section explains:
Setting up LMS High Availability Environment on Windows

High Availability refers to a state where data and applications are available always because software or
hardware has been installed to maintain the continued functioning in spite of computer or processes
failure.
High availability is a configuration of hardware and software that allows you to:
Monitor the services provided by a system
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:
Reduces planned and unplanned downtime.
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.
Consolidates hardware in clusters.

OL-25957-01
4-1
Chapter 4
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:
Local redundancy (dual-node within a single site)

The local redundancy configuration provides an automatic failover solution in the event of software
or hardware failures without the need to reconfigure IP Addresses or DNS entries on the switched
or routed network.
Geographic redundancy (single-node across two sites)

The geographic redundancy configuration provides disaster recovery by replicating application data
between two sites. Switch over between sites (redundant server) can be initiated manually or
performed automatically when there is a network failure or during abnormal conditions.
Replication without clustering

This refers to the replication of data across servers without creating a cluster configuration.
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
Local Redundancy Configuration
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
Figure 4-2 displays geographic redundancy configuration.

Figure 4-2
Geographic Redundancy Configuration
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

The following Symantec Veritas components are used in the LMS high availability solution:
Veritas Storage Foundation

Provides volume management technology, quick recovery, and fault tolerant capabilities to
enterprise computing environments. Veritas Storage provides the foundation for Veritas Cluster
Server and Veritas Volume Replicator.
Veritas Volume Replicator

Provides a foundation for continuous data replication over IP networks, enabling rapid and reliable
recovery of critical applications at remote recovery sites.
Veritas Cluster Server (VCS)

Clustering solution to reduce application downtime. A cluster connects multiple independent
systems to provide fault tolerance and failover capability, thus reducing the downtime. VCS
supports both local and global clusters.
Global Cluster Option (GCO)

OL-25957-01
4-3
Chapter 4
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:
Veritas Enterprise Administrator (VEA) Console

Provides a graphical view of storage and allows you to monitor or manage storage objects such as
disk groups and disk volumes.
Cluster Management Console

Allows you to monitor, manage, and report on multiple VCS clusters from a single web-based
console. This console provides enhanced visualization of the managed clusters, and centralized
control for global applications. It also provides reports on the status of the availability of each
application.
Cluster Manager (Java Console)

Provides complete administration capabilities for clusters and different views to monitor the
clusters, systems, service groups, and resources.
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.

This section explains the Operating system and hardware requirements for Veritas implementation:
Operating Systems
Solaris 10 systems
Windows 2008 64 bit Enterprise Edition
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.
You should configure name resolution for all the nodes.
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
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.

This section explains setting up Veritas implementation on a Windows system.
Installing Storage Foundation HA 5.1 on Windows
Creating Disk Groups and Volumes
Installing LMS on Primary and Secondary Servers
Setting Up Veritas Volume Replication
Setting Up Veritas Volume Replication Without Clustering
Veritas Cluster Server Setup Tasks
Installing Storage Foundation HA 5.1 on Windows

To install the product:
Step 1
Start the Veritas Storage and High Availability Solutions setup.
Step 2
Click Storage Foundation HA 5.1 for Windows.
Step 3
Click Complete/Custom to begin the installation.
Step 4
Review the Welcome message and click Next.
Step 5
Accept the license agreement and click Next.
Step 6
Enter the product license key for Veritas Storage Foundation HA 5.1 for Windows and click Add.
Step 7
Click Next to select the product options.

a.
Ensure that the following products are selected:

Veritas Storage Foundation HA 5.1 for Windows (Server components)
Veritas Storage Foundation HA 5.1 for Windows (Client components)
b.
Ensure that the following product options are selected:

Veritas Volume Replicator Replicates data across multiple sites for disaster recovery.
FlashSnap Allows you to create and maintain persistent snapshot of volumes
VxCacheUses a portion of system memory to improve I/O performance.
Global Cluster OptionEnables you to link clusters to provide wide-area failover and disaster
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.

OL-25957-01
4-5
Chapter 4
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
Review the installation settings information and click Next.

The Installation Status screen displays the status messages and the progress of the installation.
Step 10
Review the installation summary information and click Next after the installation has completed.
Step 11
Click Finish.
Step 12
Click Yes to reboot the local node.
Creating Disk Groups and Volumes

A disk group is a collection of disks that is ported as a single unit. Veritas Storage Foundation uses disk
groups to organize disks for management purposes.
Volumes are logical entities that comprises of portions of one or more physical disks and are accessed
by a drive letter or mount point. Volumes can be configured for performance and high availability.
Prerequisites for Configuring Disk Groups and Volumes
Creating Disk Groups on Primary Server
Creating Volumes on Primary Server
Creating Disk Groups and Volumes on Secondary Server
Prerequisites for Configuring Disk Groups and Volumes

Complete the following tasks before you configure the disk groups and volumes:
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.
Creating Disk Groups on Primary Server

You must create the disk group on the first node where the product instance is being installed. Repeat
the procedure if you want to create additional disk groups.
To create a disk group:
Step 1
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
Step 3
Click Connect to a Host or Domain.
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
Click Next to go to next page in the wizard.
Step 10
Provide the information about the disk group:

a.
Enter a name for the disk group in the Group Name field.
You should enter datadg as group name.
b.
Select the Create Cluster Group checkbox.

While creating datadg disk group, if the system bus error appears, you must run this command:
Vxclus UseSystemBus ON
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 Finish to create the new disk group.
Creating Volumes on Primary Server

This section will guide you through the process of creating a volume on a cluster disk group. Repeat the
procedure below if you want to create the following volumes on the first node of the cluster.
To create a volume:
Step 1
Step 2
Select a profile if prompted.

You can also select the default profile.
Step 3
Step 4

OL-25957-01
4-7
Chapter 4

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
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
Select New Volume from the shortcut context menu.

The New Volume wizard appears with a welcome message.
Step 9
Click Next to go to the next page in the wizard.
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
Specify the parameters of the volume:

a.
Enter a name for the volume in the Volume Name field.

You should enter cscopx as volume name.
b.
Select the volume type as concatenated volume.
c.
Provide a size for the volume.

For example, you can enter as 10 GB. Ensure that the disk has sufficient space before providing a
size for the volume.
d.
Click Next.
The Add Drive Letter and Path dialog box appears.
Step 13
Select Assign a Drive Letter, and choose a drive letter.

We recommend that you do not assign D: for this volume. This is because, the CD-ROM drive when
installed on the system, may be allocated with D: by default.
Step 14
Click Next.
The Create File System dialog box appears.
Step 15
Select the Format this volume checkbox.
Step 16
Select the file system as NTFS.
Step 17
Click Next to review the settings summary.
Step 18
Click Finish to create the new volume.
Step 19
Repeat the above procedure to create a volume in the datadg disk group with the following
characteristics:
Volume Name: data_srl
Volume Type: Concatenated Volume
Volume Size: 30 GB
Assigned Drive Letter: None
4-8
OL-25957-01
Chapter 4
This volume will not be mounted and is used only by Veritas Volume Replicator.
Creating Disk Groups and Volumes on Secondary Server

You should launch the Veritas Enterprise Administration console on the Secondary server.
Create the identical disk group and volume as you have created on Primary server. See Creating Disk
Groups on Primary Server and Creating Volumes on Primary Server for detailed explanation.
You should create the data_srl and cscopx volumes with the same size, type and drive letter.

To make the LMS application highly available, install LMS on newly created cscopx volume on both the
Primary and Secondary servers.
Ensure that :
Note
LMS is installed
Admin password, Database password, and HTTP ports are the same on both the Primary and
Secondary servers.
Name of the LMS volume is the same on both the servers.
Casuser settings configured should be the same on both the 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.
By default the VCSHOME is located at:,
On Windows, C:\Program Files\Veritas\Cluster Server\bin
On Solaris, /var/VRTSvcs/bin
Note
To find out the VCSHOME location, give the echo %vcs_home% command in run prompt or
console.

OL-25957-01
4-9
Chapter 4
Setting Up Veritas Volume Replication

Veritas Volume Replicator is a fully integrated component of Veritas Volume Manager that replicates
data to remote locations over any standard IP network to provide continuous data availability.
Modes of Replication
Setting Up RDS, RVG and RLINK
Setting Casuser Permissions on cscopx Volume
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.

This section explains how to set up an Replication Data Set (RDS), which is the most important step to
get replication started. Data is replicated from a Primary node where the application is running to one or
more Secondary nodes.
An RDS consists of a Replication Volume Group (RVG) on the Primary node, and the corresponding
RVG on the Secondary nodes.
A Replication Link (RLINK) is associated with an RVG and it establishes the link between the Primary
and a Secondary RVG. The RLINKs associated with the Primary RVG control the replication settings.
To create the Replicated Data Set, Replicated Volume Groups and Replication Links:
Step 1
Step 2
Click View > Connection > Replication Network.
Step 3
Click Action > Setup Replicated Data Set to launch the Setup Replicated Data Set wizard.
Step 4
Enter a name for Replicated Data Set name.
Step 5
Enter a name for Replicated Volume Group name.
Step 6
Select a Primary host from the drop-down list box.
Step 7
Click Next.
4-10
OL-25957-01
Chapter 4
Step 8
Select cscopx as the volume to be replicated and click Next.
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
Click Yes to add the Secondary host to the Primary RDS.

The Specify Secondary host for replication page appears.
Step 12
Step 13
Specify the Secondary host details for replication:

a.
Enter the name of the Secondary host.
b.
Click Next.
c.
Enter the credentials (User name and Password) to connect to the Secondary server.
d.
Click OK to edit the replication settings.
Edit the replication settings as required:
Verify the Primary side IP address or edit the IP Address if required.
Verify the Secondary side IP address or edit the IP Address if required.
Select the Replication Mode as Synchronous Override.
Enter a Primary RLINK Name and a Secondary RLINK Name.

If you do not specify any name, Veritas Volume Replicator assigns a default name.
Step 14
Click Next to start Replication with the default settings.

The Secondary server will be in inconsistent state. It takes some time to become consistent depending
on the network bandwidth.
Setting Casuser Permissions on cscopx Volume

To run the protected instance of LMS on Secondary servers, you must add the local casusers groups
permissions to the cscopx volume.
Before you set the casusers permissions on cscopx volume:
Step 1
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.
To add the local casusers group permissions for a Secondary server:

Step 1
Right-click Selected Drive Letter:\Program Files\CSCOpx from the Windows Explorer.
Step 2
Select the Sharing and Storage menu item.

The folder properties dialog box appears.
Step 3
Select the Security tab and click Add.
Step 4
Click the Location button in the Select Users or Groups dialog box, and select the local server from the
selection tree.

OL-25957-01
4-11
Chapter 4
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
Click the Advanced button.
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
Click OK after the propagation is complete.
After the casusers group permissions have been set, unmount the volume and start the
replication.
Note
Setting Up Veritas Volume Replication Without Clustering

To set up volume replication on the Primary server:
Step 1
Stop the Daemon Manager on the LMS server.
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
Verify the Secondary Server name to which data is to be replicated.
Step 6
Click OK.
Do the following tasks on the Secondary Server:

Step 1
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
Run the following perl script from the directory:

NMSRoot\bin\perl NMSRoot\bin\hostnamechange.pl ohost oldhostname -nhost newhostname
-domain DomainName
Here,
oldhostnameHostname of the Primary server.
newhostnameHostname of the Secondary server
DomainDomain name of the LMS Server. Entering domain name is optional.
Step 3
Remove the following files after running the hostnamechange.pl script:
NMSROOT\lib\csorb\NS_Ref
NMSROOT\campus\www\classpath\NS_Ref
4-12
OL-25957-01
Chapter 4
Step 4
NMSROOT\_nsdb_root
Run the following command in the Secondary Server:

NMSROOT/lib/jre/bin/java -classpath NMSROOT/MDC/tomcat/webapps/cwhp/WEB-INF/
classes com.cisco.nm.cmf.backup.util.BackupSchedule NMSROOT
You must run this command only if there are any backup jobs scheduled in the Primary Server.
Step 5
Restart the Daemon Manager.
Step 6
Launch the LMS Server by entering the following on the web browser:
http://Secondary_Server_IP_Address:1741
Veritas Cluster Server Setup Tasks

Clustering is used while monitoring of resources or automatic failover of the resources is required.
This section covers the steps required to setup and configure the Veritas clusters. There are two specific
scenarios described:
Cluster Configuration for High Availability
Cluster Configuration for Disaster Recovery
Cluster Configuration for High Availability

This section specifically covers the setup and configuration of the Veritas cluster for the local
redundancy configuration.
Before you start configuring the clusters, ensure that:
You create a cluster with both the Primary and Secondary servers.
NICs on both the servers are assigned with IP Address.
Virtual IP Address will be assigned to the cluster.
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.
This section covers the following procedures:
Creating the Cluster
Creating the Cluster Service Group
Creating the datadg Service Group (For HA Setup)
Creating the Replication Service Group
Creating the Application Service Group
Creating the Cluster

To create the cluster:
Step 1
Click Start > All Programs > Symantec > Veritas Cluster Server > Configuration Wizards >
Cluster Configuration Wizard.

OL-25957-01
4-13
Chapter 4
Step 2
Select Cluster Operation and click Next.

The domain name is displayed.
By default, the list of systems and the list of users in the domain is enabled. You can edit, if required.
Step 3
Click Next.
Step 4
Include the Primary and Secondary servers that should be part of the cluster.
Step 5
Select Create New Cluster Option and click Next.
Step 6
Create a new cluster using the VCS Configuration wizard, where:
Cluster Name = LMS_HA_Cluster
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
Select the Use VCS User Privileges checkbox.
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.
Creating the Cluster Service Group

You can configure a Cluster Service group to run the following optional components:
Cluster Manager (Web Console)Configure this resource if you want to access the Cluster
Management Console (CMC) through the web browser.
NotificationConfigure this component to receive notifications of events occurring in the cluster

through e-mail.
You can use the VCS Configuration wizard to configure these components.
To configure these components:
Step 1
Launch the VCS Configuration wizard.
Step 2
Click Next.
Step 3
Click Cluster Operations > Domain name.
4-14
OL-25957-01
Chapter 4
Step 4
Select the server to configure the cluster groups.
Step 5
Select Edit existing cluster option and click Next.
Step 6
Select Configure Cluster Service options and configure the notifier and web console options for local
redundancy configuration (HA Setup).
Step 7
Enter the virtual IP Address of the cluster.

You can assign a real IP Address which is not used in the network and is not assigned DHCP, as a virtual
IP Address.
Step 8
Click OK.
Step 9
Start the Cluster Manager using Start > All Programs > Symantec > Veritas Cluster Manager - Java
Console.
Step 10
Click File > New Cluster.
Step 11
Enter the virtual IP Address of the cluster that is configured, in the Hostname field.
Step 12
Click OK.
Creating the datadg Service Group (For HA Setup)

To create the datadg Service Group:
Step 1
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:
Give the name of the service group as App_datadg.
Select the Parallel option.
Select the servers (Primary and Secondary servers) on which the service group can come online.
Step 3
Click OK.
Step 4
Add the VMDg resource with the following configuration:
Resource Name = datadg
Resource Type = VMDg
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.
Creating the Replication Service Group

To create the Replication Service group, do the following on the Primary and Secondary clusters:
Step 1
Console.
Step 2
Login to the cluster using the credentials that you have configured in the VCS Configuration wizard.

OL-25957-01
4-15
Chapter 4
Step 3
Enter the name of the service group as App_Rep.
Select the Failover Option.
Enable the Auto Start option.
Step 4
Click OK.
Step 5
Add the Proxy resource with the following configuration:
Resource Name =VVR_NIC_Proxy
Resource Type = Proxy
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
Add the IP resource with the following configuration:
Resource Name = VVR_IP
Resource Type = IP
Address = Virtual IP address
SubNetMask = subnet mask
MACAddress = MAC Address of the corresponding NIC card
Step 7
Add the VvrRvg resource with the following configuration:
Resource Name = APP_RVG
Resource Type = VvrRvg
RVG = Name of the Replicated Volume Group

For example, LMS_RVG.
VMDg Resource Name = Name of the Resource Configured under the App_Rep Service group
For example, datadg.
IPResName = VVR_IP
Step 8
Add the VMDg resource with the following configuration:
Resource Type = VMDg
This is required only for geographic redundancy setup (DR setup).
4-16
OL-25957-01
Chapter 4
Step 9
Right-click on the respective resources and do the following:
Link VVR_IP as the parent of VVR_NIC_Proxy.
Link APP_RVG as the parent of VVR_IP.
Link APP_RVG as the parent of datadg.

Step 10
Right-click on the App_Rep service group and select Online on Primary Server.
Creating the Application Service Group

To create the Application Service Group:
Step 1
Console.
Step 2
Use the VCS Configuration wizard to see the Cluster Service group that is created.
Step 3
Enter the name of the service group as App_Service_GP.
Select the Failover option.
Step 4
Click OK.
Step 5
Add the RVG Primary resource with the following configuration:
Resource Name = App_RVGPrimary
Resource Type = RVGPrimary
RvgResourceName = Name of the Resource Configured under the App_Rep Service group
For example, App_Rvg.
Step 6
Add the MountV Resource with the following configuration:
Resource Name = APP_MountV
Resource Type = MountV
Mount Path = Selected Drive Letter:\
Volume Name = cscopx
VMDg Resource Name = Name of the Resource Configured under the App_Rep Service group
For example, datadg.

OL-25957-01
4-17
Chapter 4
Step 7
Resource Name =APP_NIC_Proxy
TargetResName = NIC
Step 8
Add the IP resource with the following configuration.
Resource Name = APP_IP
Resource Type = IP
Address = Virtual IP address allocated for this cluster and used by LMS application
MACAddress = MAC Address of the corresponding NIC card.
Step 9
Import the Agent file from the location C:\Program Files\Veritas\cluster server\conf\config, into the
cluster.
Step 10
Add the Agent resource with the following configuration.
Resource Name = LMSAgent
Resource Type = LMS
Step 11
Enter the pathname as NMSROOT.
Step 12
Enter the Virtual IP as EventIPAddress.
Step 13
Enter the Certificate Dir as NMSROOT/MDC/Apache/conf/ssl.
Step 14
Link APP_MountV as the parent of APP_RVGPrimary.
Step 15
Link APP_IP as the parent of APP_NIC_PROXY.
Step 16
Link Agent as the parent of APP_MountV.
Step 17
Link Agent as the parent of APP_IP.
Step 18
Right-click on the App_Service_Gp service group and select Online on Primary Server.
Cluster Configuration for Disaster Recovery

This section specifically covers the setup and configuration of the Veritas cluster for the case of two
clusters geographically separated with a single node in each cluster. It contains:
Creating the Primary and Secondary Clusters
Creating the Cluster Service Group for Disaster Recovery Setup
Disaster Recovery Setup Between Primary and Secondary Clusters
4-18
OL-25957-01
Chapter 4
Creating the Primary and Secondary Clusters

For a Disaster Recovery Cluster setup, you should:
Step 1
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.
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.
Creating the Cluster Service Group for Disaster Recovery Setup

Configure a Cluster Service group in the servers at both sites to run the following optional components:
Management Console (CMC) through web browser.
NotificationConfigure this component if you want to receive notification of events happening in

the cluster through e-mail.
Global Cluster OptionAllows you to manage multiple clusters.
To create a Cluster Service Group:

Step 1
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:
Resource Name = wac
Resource Type = Process
Step 3
Link wac as the parent of VCS_IP.
Step 4
Link VCS_IP as the parent of NIC.
Step 5
Link the other resources as explained in Creating the Cluster Service Group.

OL-25957-01
4-19
Chapter 4
Step 6
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.
Select the App_Service_Gp in the Cluster Administrator Console.
b.
Right-click on the App_Rep service group.
c.
Select the Online Local Firm link option and select the name of the service group to be linked as
App_Rep.
Disaster Recovery Setup Between Primary and Secondary Clusters

Steps to follow on a Primary cluster to establish the Disaster Recovery setup between the clusters:
Step 1
Console.
Step 2
Click Edit > Add/Delete Remote Cluster.

A wizard appears.
Step 3
Click Next.
Step 4
Select the Add Cluster option and click Next.
Step 5
Enter the IP Address of the Secondary cluster.
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
The permissions has to be provided in both Primary and Secondary clusters.

Right-click on App Service Group and select Configure as a Global Option.
The Global Cluster Details window appears.
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
Enter the Cluster IP address, Username and password.
4-20
OL-25957-01
Chapter 4
Step 11
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.
Select the App Service Group.
b.
Click Show All attributes from the properties tab for Administrator.
c.
Click Set Administrators/Operators.

This section explains setting up Veritas implementation on a Solaris system.
Installing Storage Foundation HA 5.1 on Solaris
Creating Disk Groups and Volumes on Solaris Servers
Setting Up Veritas Volume Replication on Solaris Server
Setting Up Veritas Volume Replication Without Clustering On Solaris
Veritas Cluster Server Setup Tasks on Solaris
Installing Storage Foundation HA 5.1 on Solaris

To install the product:
Step 1
Go to Veritas installer location.

For example, /Veritas/VSF_HA_5.1/installer.
Step 2
Run the installer file:

./installer
The Task menu appears.

Step 3
Enter I to install or upgrade Veritas Storage Foundation HA 5.1 package.

The component list appears.
Step 4
Enter 5 to install all Veritas Storage Foundation components and press Enter.
Step 5
The installer prompts for a system name.
Step 6
Enter the system hostnames and press Enter.

OL-25957-01
4-21
Chapter 4
Step 7
Enter the required Veritas Storage Foundation license that includes the following components:
Veritas Storage Foundation High Availability
Veritas Volume Replicator
Veritas Cluster Server with the Global Cluster Option support
Step 8
Enter 2 to install Veritas Storage Foundation and press Enter.
Step 9
Enter Y to configure Storage Foundation.
Step 10
Enter N to configure VCS.
Step 11
Enter N to configure Enclosure based naming schemes.
Step 12
Enter Y to set up the default disk group.
Step 13
Enter the disk group name as datadg.
Step 14
Enter N for all VVR questions.
Step 15
Enter Y for Fully qualified host name confirmation.
Step 16
Enter N to enable the Storage Foundation Management server.
Step 17
Enter Y to start the Veritas Storage Foundation Process.
Step 18
Enter shutdown y i6 g0 to reboot the Solaris server
Step 19
Enter ps ef | grep vx on the command prompt after reboot to verify whether all Veritas processes
are brought up successfully.
Creating Disk Groups and Volumes on Solaris Servers

A disk group is a collection of disks that is ported as a single unit. Veritas Storage Foundation uses disk
groups to organize disks for management purposes.
Volumes are logical entities that are comprised of portions of one or more physical disks and are
accessed by a drive letter or mount point. Volumes can be configured for performance and high
availability.
Prerequisites for Configuring Disk Groups and Volumes on Solaris
Creating Disk Groups on Primary Solaris Server
Creating Volumes on Primary Solaris Server
Creating Disk Groups and Volumes on Secondary Solaris Server
Prerequisites for Configuring Disk Groups and Volumes on Solaris

See Prerequisites for Configuring Disk Groups and Volumes for details.
4-22
OL-25957-01
Chapter 4
Creating Disk Groups on Primary Solaris Server

You must create the disk group on the first node where the product instance is being installed. Repeat
the procedure if you want to create additional disk groups.
To create a disk group:
Step 1
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
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
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
Click Next to go to next page in the wizard.
Step 10
Enter the information about the disk group:

a.
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
Click Finish to create the new disk group.
Creating Volumes on Primary Solaris Server

This section explains how to create a volume on a cluster disk group. Repeat the procedure below if you
want to create the volumes on the first node of the cluster.
To create a volume:
Step 1
Enter /opt/VRTS/bin/vea on the Solaris system command prompt to launch the Veritas Enterprise
Administrator (VEA) console.

OL-25957-01
4-23
Chapter 4
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.
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
Step 7
Locate the StorageAgent tree node and right-click the Volumes icon under the StorageAgent tree node.
Step 8
Select New Volume from the shortcut context menu.

The New Volume wizard appears with the welcome message.
Step 9
Step 10
Click Let volume manager decide what disks to use for this volume.
Step 11
Click Next.
Step 12
Specify the parameters of the volume:

a.
Enter a name for the volume in the Volume Name field.

You should enter cscopx as volume name.
b.
Select the volume type as concatenated volume.
c.
Enter a size for the volume.

For example, you can enter as 10 GB.
d.
Click Next.
The Create File System dialog box appears.

Step 13
Select the file system as vxfs.
Step 14
Mount the cscopx volume using the mount point as /opt/CSCOpx
Step 15
Click Next to review the settings summary.
Step 16
Click Finish to create the new volume.
Step 17
characteristics:
Volume Name: varcscopx
Volume Size: 10 GB
File System: vxfs
This volume will be mounted using the mount point /var/adm/CSCOpx and is used only by LMS
application.
Step 18
characteristics:
4-24
OL-25957-01
Chapter 4
Volume Name: data_srl
Volume Size: 10 GB
This volume will not be mounted and is used only by Veritas Volume Replicator.
Creating Disk Groups and Volumes on Secondary Solaris Server

You should launch the Veritas Enterprise Administration console on the Secondary server.
Create the identical disk group and volume as you have created on Primary server. See Creating Disk
Groups on Primary Solaris Server and Creating Volumes on Primary Solaris Server for detailed
explanation.
You should create the cscopx and varcscopx volume with the same size, type and mount point.

To make the LMS application highly available, install LMS on the newly created cscopx or varcscopx
volumes on both the Primary and Secondary servers.
Ensure that:
Note
LMS is installed
Admin password, Database password, and HTTP ports are same on both the Primary and Secondary
servers.
Name of the LMS volume is same on both the servers.
Casuser settings configured should be same on both the servers.
After installing LMS on Secondary server under cscopxvolume, unmount the cscopx and varcscopx
volumes.
Setting Up Veritas Volume Replication on Solaris Server

Veritas Volume Replicator is a fully integrated component of Veritas Volume Manager that replicates
data to remote locations over any standard IP network to provide continuous data availability.
See the following sections for information:

You must select both the cscopx and varcscopx as the volumes to be replicated.
Setting Casuser Permissions on cscopx Volume on Solaris (If Required)

OL-25957-01
4-25
Chapter 4
Setting Casuser Permissions on cscopx Volume on Solaris (If Required)

You must set the casuser permissions on cscopx volume only if required on a Solaris system. Otherwise,
you can skip this section.
To run the protected instance of LMS on Secondary servers, you must add the local casusers groups
permissions to the cscopx and varcscopx volumes.
Before you set the casusers permissions on cscopx volume:
Step 1
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:
chown -R casuser:casusers /opt/CSCOpx
chown -R casuser:casusers /var/adm/CSCOpx
After the casusers group permissions have been set, unmount the cscopx and varcscopx volumes and start
the replication.

To set up volume replication on the Primary server:
Step 1
Stop the Daemon Manager on LMS server.
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
Verify the Secondary Server name to data is to be replicated.
Step 6
Click OK.
Do the following tasks on the Secondary Server:

Step 1
Mount the cscopx volume with the /opt/CSCOpx directory.
Step 2
Mount the varcscopx volume with the /var/adm/CSCOpx directory.
Step 3
Run the following perl script from the directory.

NMSRoot/bin/perl NMSRoot/bin/hostnamechange.pl ohost oldhostname -nhost newhostname
-domain DomainName
Here,
oldhostnameHostname of the Primary server.
newhostnameHostname of the Secondary server
Domain Domain name of the LMS Server. Entering domain name is optional.
4-26
OL-25957-01
Chapter 4
Step 4
Step 5
Remove the following files after running the hostnamechange.pl script:
NMSROOT/lib/csorb/NS_Ref
NMSROOT/campus/www/classpath/NS_Ref
NMSROOT/_nsdb_root
Run the following command in the Secondary Server:

NMSROOT/lib/jre/bin/java -classpath NMSROOT/MDC/tomcat/webapps/cwhp/WEB-INF/
classes com.cisco.nm.cmf.backup.util.BackupSchedule NMSROOT
You must run this command only if there are any backup jobs scheduled in the Primary Server.
Step 6
Restart the Daemon Manager.
Step 7
Launch the LMS Server by entering the following on the web browser:
http://Secondary_Server_IP_Address:1741
Veritas Cluster Server Setup Tasks on Solaris

Clustering is used while monitoring of resources or automatic failover of the resources is required.
This section covers the steps required to setup and configure the Veritas clusters. There are two specific
scenarios described:
Cluster Configuration for High Availability on Solaris
Cluster Configuration for Disaster Recovery on Solaris
Cluster Configuration for High Availability on Solaris

This section specifically covers the setup and configuration of the Veritas cluster for the case of a single,
local cluster with two nodes in the cluster (Primary and Secondary).
You must do the following tasks before you start configuring the clusters:
Create a cluster with both the Primary and Secondary servers.
NICs on both the servers are assigned with IP Address.
Virtual IP Address will be assigned to the cluster.
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.
This section covers the following procedures:
Creating the Cluster on Solaris
Creating the datadg Service Group on Solaris (For HA Setup)
Creating the Replication Service Group on Solaris
Creating the Application Service Group on Solaris
Creating the Cluster on Solaris

To create the cluster on Solaris:
Step 1
Run the Veritas installer from the VSF_HA_5.1 CD.

OL-25957-01
4-27
Chapter 4
Step 2
Enter c followed by 1 to configure the clusters.

The installer prompts you for a system name.
Step 3
Enter the system hostnames of the Primary and Secondary server.
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
Enter N to configure Symantec Security Services and press Enter.
Step 7
Enter Y to create a new user for that cluster and press Enter.
Step 8
Enter N for Cluster Management configuration.
Step 9
Enter Y for Cluster Management Console configuration and press Enter.
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
Enter the correct netmask and press Enter.
Step 13
Configure the SMTP notification for that server.
Step 14
Start the Cluster Manager by entering /opt/VRTSvcs/bin/hagui on the command prompt.
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.
Set the value of Onlineretrylimit attribute as 0.
Make all the resources including the Notifier Manager and Cluster Management Console online.
Creating the datadg Service Group on Solaris (For HA Setup)

To create the datadg Service Group:
Step 1
Step 2
Give the name of the service group as App_datadg.
Select the Parallel option.
Step 3
Click OK.
Step 4
Add the Disk Group resource with the following configuration:
Resource Type = Disk Group
You must select the Critical and Enabled checkboxes for this resource. You should add this resource only
for local redundancy configuration.
4-28
OL-25957-01
Chapter 4
Now the service group is online on both Primary and Secondary servers.
Creating the Replication Service Group on Solaris

To create the Replication Service group on Solaris, do the following on the Primary and Secondary
clusters:
Step 1
Start the Cluster Manager by entering /opt/VRTSvcs/bin/hagui at the command prompt.
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
Enter the name of the service group as App_Rep.
Select the Failover option.
Step 4
Click OK.
Step 5
Resource Name =App_Rep_NIC
TargetResName = csg_nic
This name should be the same as the name of the resource of resource type NIC.
Step 6
Add the RVG resource with the following configuration:
Resource Name = APP_RVG
Resource Type = RVG
RVG = LMS_DR_RVG
Disk Group= datadg
Step 7
Add the IP resource with the following configuration:
Resource Name = AppRep_IP
Resource Type = IP
Address = Virtual IP address
Device = Public NIC name
Step 8
Add the Disk Group resource with the following configuration:
Resource Type = Disk Group

OL-25957-01
4-29
Chapter 4
Step 9
Right-click on the respective resources and do the following:
Link APPRep_IP as the parent of App_Rep_NIC.
Link APP_RVG as the parent of AppRep_IP.
Link APP_RVG as the parent of datadg.

Step 10
Creating the Application Service Group on Solaris

To create the Application Service group on Solaris:
Step 1
Step 2
You can see the Cluster Service group that is created.
Step 3
Give the name of the service group as App_Service_GP.
Select the Parallel Option.
Select the servers in which the service group to act upon.
Step 4
Click OK.
Step 5
Add the RVG Primary resource with the following configuration:
Resource Name = App_RVGPrimary
Resource Type = RVGPrimary
RvgResourceName = Name of the Resource Configured under the App_Rep Service group
For example, App_Rvg.
Step 6
Resource Name =APP_NIC_Proxy
TargetResName = NIC
Step 7
Add the IP resource with the following configuration.
Resource Name = APP_IP
Resource Type = IP
Address = Virtual IP address allocated for this cluster and used by LMS application
4-30
OL-25957-01
Chapter 4
MACAddress = MAC Address of the corresponding NIC card.
Step 8
Add the Volume resource for cscopx volume with the following configuration.
Resource Name = Volume
Resource Type = cscopx
Disk Group= datadg
Step 9
Add the Volume resource for varcscopx volume with the following configuration.
Resource Name = Volume
Resource Type = varcscopx
Disk Group= datadg
Step 10
Add the Mount resource for cscopx volume with the following configuration:
Resource Name = cscopx_Mount
Resource Type = Mount
Mount Point= Mount_point
Block Device=Exact Path of cscopx volume
FSType=vxfs
Step 11
Add the Mount resource for varcscopx volume with the following configuration:
Resource Name = varcscopx_Mount
Resource Type = Mount
Mount Point= Mount_point
Block Device=Exact Path of cscopx volume
FSType=vxfs
FSskopt=-y
Step 12
Import the Agent file from the location /etc/VRTSvcs/conf/config/LMSTypes.cf, into the cluster.
Step 13
Add the Agent resource with the following configuration.
Resource Name = LMSAgent
Resource Type = LMS
Step 14
Click the LMS Resource Type and do the following:

a.
Select the Show All Attributes option from the pane displayed at the right.
b.
Set the value of OnlineTimeout attribute as 1300.
c.
Set the value of OfflineTimeout attribute as 1000.
Step 15
Enter the Virtual IP as EventIPAddress.
Step 16
Link cscopx_Mount as the parent of cscopx.

OL-25957-01
4-31
Chapter 4
Step 17
Link varcscopx_Mount as the parent of varcscopx.
Step 18
Link cscopx as the parent of App_RVGPrimary.
Step 19
Link varcscopx as the parent of App_RVGPrimary.
Step 20
Link APP_IP as the parent of APP_NIC_PROXY.
Step 21
Link Agent as the parent of cscopx_Mount, varcscopx_Mount and APP_IP.
Cluster Configuration for Disaster Recovery on Solaris

This section specifically covers the setup and configuration of the Veritas cluster for the case of two
clusters geographically separated with a single node in each cluster.
For a Disaster Recovery Cluster setup, you should:
Step 1
Create a Primary cluster with the server in Site 1 and make all the service groups online.
groups.
Step 2
Create a Secondary cluster with the server in Site 2 and make all the service groups online except
Application Service Group.
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.
Creating the Cluster Service Group on Solaris
Disaster Recovery Setup Between Primary and Secondary Clusters on Solaris
Creating the Cluster Service Group on Solaris

Configure a Cluster Service group in the servers at both sites to run the following optional components:
Management Console (CMC) through web browser.
NotificationConfigure this component to receive e-mail notifications about the events occurring
in the cluster.
Global Cluster OptionAllows you to manage multiple clusters.
To create the Cluster Service Group, you must:

Step 1
Perform the steps explained in Creating the Cluster Service Group on both the Primary and Secondary
clusters to create the Cluster Service Group.
4-32
OL-25957-01
Chapter 4
Step 2
In addition to these steps, you must add a wac resource with the following configuration to the Cluster
Service Group:
Resource Name = wac
Resource Type = Process
Step 3
Link wac as the parent of APP_IP.
Step 4
Link APP_IP as the parent of NIC.
Step 5
Configure the Online Local Firm link between the App_Service_Gp and App_Rep service groups. To do
so:
a.
Select the App_Service_Gp in the Cluster Administrator Console.
b.
Right-click on the App_Rep service group.
c.
Select the Online Local Firm link option and select the name of the service group to be linked as
App_Rep.
Disaster Recovery Setup Between Primary and Secondary Clusters on Solaris

To establish the Disaster Recovery setup between the clusters, do the following configuration on a
Primary cluster:
Step 1
Step 2
Click Edit > Add/Delete Remote Cluster.

A wizard appears.
Step 3
Click Next.
Step 4
Select the Add Cluster option and click Next.
Step 5
Enter the IP Address of the Secondary cluster.
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
The permissions has to be provided in both Primary and Secondary clusters.

Right-click on App Service Group and select Configure as a Global Option.
The Global Cluster Details window appears.

OL-25957-01
4-33
Chapter 4
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
Enter the Cluster IP address, Username and password.
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.
Select the App Service Group.
b.
Click Show All attributes from the properties tab for Administrator.
c.
Click Set Administrators/Operators.

You can create the HA or DR deployment environment only for a fresh installation of LMS.
We recommend you to:
1.
Uninstall LMS from the server if you want to migrate from non-HA to HA environment.
2.
Install the Symantec Veritas products.
3.
Install LMS 4.2 after the Veritas Setup is complete.
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.
Install the Symantec Veritas products.
3.
Install LMS 4.2 after the Veritas Setup is complete.
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).
For more information on data migration, see
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-34
OL-25957-01
Chapter 4
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.

OL-25957-01
4-35
Chapter 4
4-36
OL-25957-01
CH A P T E R
Setting Up Cisco Prime LMS for High Availability,

Live Migration, and Storage VMotion Using
VMware
This chapter explains setting up LMS for High Availability (HA), Live migration, and, Storage VMotion
using the VMware vSphere solution.
VMware High Availability (HA) is the solution used for HA, and VMware VMotion is used for live
migration (it includes Storage VMotion).
This chapter explains:
Overview of VMware High Availability
Overview of VMware VMotion and Storage VMotion
Cloning a Virtual Machine Using VMware

VMware High Availability (HA) is a simple and cost-effective solution which ensures high levels of
availability during a planned or unplanned downtime.
With VMware HA, you can:
Provide higher availability independent of hardware, operating system, and applications.
Eliminate planned downtime for common maintenance operations.
Provide automatic restart in cases of failure.
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.

OL-25957-01
5-1
Chapter 5
Setting Up Cisco Prime LMS for High Availability, Live Migration, and Storage VMotion Using VMware
VMware HA protects application availability in two ways:
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.
Prerequisites for Implementing High Availability
Setting up High Availability using VMware HA
Creating a VMware HA Cluster

The following VMware vSphere components are used in the LMS HA solution:
VMware ESX or ESXi

Virtualization layer run on physical servers that abstracts processor, memory, storage, and resources
into multiple virtual machines. Two versions of ESX are available: VMware ESX 4.0, 4.1, and 5.0
and VMware ESXi 4.0, 4.1, and 5.0.
VMware vCenter Server

Central point for configuring, provisioning, and managing virtualized IT environments.
VMware vSphere Client

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. vSphere Client acts as an interface
that allows users to connect remotely to vCenter Server or ESX or ESXi from any Windows PC.
Prerequisites for Implementing High Availability

The prerequisites for implementing HA in LMS 4.2 using VMware HA are grouped into:
VMware ESX servers Requirements
VMware vCenter Server Requirements
VMware HA Cluster Requirements
Shared Storage Requirements
Other Requirements
5-2
OL-25957-01
Chapter 5
VMware ESX servers Requirements
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.
The ESX or ESXi servers must:

Have access to all the networks.
Have compatible CPUs.
VMware vCenter Server Requirements
Ensure that the VMware vCenter Server must:

Be installed on a Windows machine with a proper license.
Have network access to the ESX or ESXi host, vSphere Client, and Internet access.
Meet the vCenter Server hardware requirements.
VMware HA Cluster Requirements
The virtual machine must not be:

Connected to a CD-ROM or floppy drive, that is using an ISO or floppy image, stored on a drive
that is local to the host server.

Bound to any physical CPUs.
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 Requirements
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.
Ensure a successful failover before you install LMS 4.2.
For more details, see the VMware vSphere 4.0 documentation.

OL-25957-01
5-3
Chapter 5
Setting up High Availability using VMware HA

This section lists the steps to set up HA for LMS 4.2 using VMware HA:
1.
Install ESX or ESXi 4.0, 4.1, and 5.0 in two or more servers.
2.
Install vCenter Server 4.0 in any server with a proper license.
3.
Install vSphere Client in client server and connect to vCenter Server.
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.
Create a virtual machine and select a datastore as shared storage disk.
7.
Configure VMware HA settings for the cluster created.
8.
Ensure that sufficient resource is available in the cluster.
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.
Creating a VMware HA Cluster

You must create a cluster, populate it with hosts, and configure VMware HA settings before failover
protection can be established. To create a VMware HA cluster using vSphere Client:
Step 1
Select the Hosts & Clusters view in vSphere Client.
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
Click Finish to close the wizard and create an empty cluster.
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
On the Cluster Features page, select Turn On VMware HA.
Step 8
Configure the VMware HA settings for your cluster.
Step 9
Host Monitoring Status
Admission Control
Virtual Machine Options
VM Monitoring
Click OK to close the cluster's Settings dialog box.

A configured VMware HA cluster, populated with hosts, is created.
5-4
OL-25957-01
Chapter 5
Note
For more details on VMware HA settings, see the VMware vSphere 4.0 documentation.

Migration is the process of moving a virtual machine from one host or storage location to another.
VMware VMotion allows you to dynamically move workloads to different physical servers or to
different underlying storage without service interruption.
VMware Storage VMotion lets you relocate virtual machine disk files between shared storage locations
while maintaining continuous service availability and complete transaction integrity.
Migration with VMotion allows working processes in a virtual machine to continue throughout a
migration. The entire state of the virtual machine is moved to the new host, while the associated virtual
disk remains in the same location on storage that is shared between the two hosts. After the virtual
machine state is migrated to the alternate host, the virtual machine runs on the new host.
When you migrate a virtual machine with VMotion, the new host for the virtual machine must meet
compatibility requirements in order for the migration to proceed.
Migration with VMotion happens in three stages:
1.
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.
The virtual machine resumes its activities on the new host.
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.
VMware vSphere Components for Migration
Prerequisites for Migration Using VMotion
Migrating LMS 4.2 Using VMware VMotion

OL-25957-01
5-5
Chapter 5 Setting Up Cisco Prime LMS for High Availability, Live Migration, and Storage VMotion Using VMware

The following VMware vSphere components are used for live migration of LMS 4.2:
VMware ESX or ESXi

Virtualization layer run on physical servers that abstracts processor, memory, storage, and resources
into multiple virtual machines. Two versions of ESX are available: VMware ESX 4.0, 4.1, and 5.0
and VMware ESXi 4.0, 4.1, and 5.0.
VMware vCenter Server

Central point for configuring, provisioning, and managing virtualized IT environments.
VMware vSphere Client

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. vSphere Client acts as an interface
that allows users to connect remotely to vCenter Server or ESX or ESXi from any Windows PC.
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
Prerequisites for Migration Using VMotion

This section explains the prerequisites for migration using VMware VMotion. The prerequisites are
grouped into:
Ensure that all the hosts and the servers meet the hardware and software requirements.
Each host must:

Be correctly licensed for VMotion
Use one dedicated Ethernet adapter for the service console (on ESX hosts).
Use one dedicated Gigabit Ethernet adapter for VMotion.
The ESX or ESXi server(s) must:

Be connected using a Gigabit Ethernet or a faster network.
Have access to the same physical networks.
Have compatible CPUs
Have access to all the shared storages
Ensure that the VMware vCenter Server must:

Be installed on a Windows machine with a proper license.
Have network access to the ESX or ESXi host, vSphere Client, and Internet access.
Meet the vCenter Server hardware requirements.
The migrating virtual machine must be on storage accessible to both the source and target hosts.
5-6
OL-25957-01
Chapter 5
The virtual machine (VM) must not be:

Connected to a CD-ROM or floppy drive, that is using an ISO or floppy image, stored on a drive
that is local to the host server.

Bound to any physical CPUs.
Clustered with another VM using a cluster service like the Microsoft Cluster Service (MSCS).
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.
Shared storage requirements:

Shared storage is typically on a storage area network (SAN), but can also be implemented using
iSCSI and NAS shared storage.
Note
For more details, see the VMware vSphere 4.0 documentation.
Migrating LMS 4.2 Using VMware VMotion

This section lists the steps to migrate LMS 4.2 using VMware VMotion:
1.
Install ESX or ESXi 4.0, 4.1, and 5.0 in two or more servers.
2.
3.
Install the vSphere Client.
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.
Configure VMotion in vSphere 4.0.
7.
On each host, configure a VMkernel port group for VMotion.
8.
Create a virtual machine and select a datastore as storage disk.
9.
Ensure that migration is successful before installing LMS 4.2.
10.
Ensure that sufficient resource is available on the target ESX or ESXi host.
11.
Install LMS 4.2 in any virtual machine in the cluster.
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.

OL-25957-01
5-7
Chapter 5 Setting Up Cisco Prime LMS for High Availability, Live Migration, and Storage VMotion Using VMware
Migrating a Virtual Machine with VMotion

To migrate a powered-on virtual machine from one host to another using VMotion technology:
Step 1
Display the virtual machine you want to migrate in the inventory.
Step 2
Right-click on the virtual machine, and select Migrate from the pop-up menu.
Step 3
Select Change host and click Next.
Step 4
Select a destination host for the virtual machine.

If there is a compatibility problem it appears in the Compatibility panel. Fix the problem, or select
another host or cluster.
Step 5
Select a resource pool and click Next.
Step 6
Select the migration priority level and click Next.
Step 7
Review the page and click Finish.

A task is created that begins the virtual machine migration process.
Note
The VMware HA and VMotion setup supports Windows and Soft Appliance platforms only.
Migrating a Virtual Machine with Storage VMotion

To migrate a powered-on virtual machine from one storage to another using VMotion technology:
Step 1
Display the virtual machine you want to migrate in the inventory.
Step 2
Right-click on the virtual machine, and select Migrate from the pop-up menu.
Step 3
Select Change Datastore and click Next.
Step 4
Choose the storage to which the virtual machine has to be migrated.

If there is a compatibility problem it appears in the Compatibility panel. Fix the problem and then
proceed with migration.
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
Review the page and click Finish.

A task is created that begins the virtual machine migration process. Once the task is completed, the
virtual machine is migrated to the expected storage. You can confirm by checking the Summary tab of
that the virtual machine using the VMware infrastructure or Vcenter server client.
5-8
OL-25957-01
Chapter 5

A clone is a copy of an existing virtual machine. The existing virtual machine is called the parent of the
clone. When the cloning operation is complete, the clone is a separate virtual machine.
Changes made to a clone do not affect the parent virtual machine.
Changes made to the parent virtual machine do not appear in a clone.
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.

OL-25957-01
5-9
Chapter 5
Supported Methods of Cloning

The following methods of Cloning are supported:
Cloning a New Virtual Machine from a Parent Virtual Machine
Cloning Parent VM to Template and Deploying Template to New VM
Cloning a New Virtual Machine from a Parent Virtual Machine

This section explains how to clone to new Virtual Machine (VM) from a parent VM and contains the
following sections:
Prerequisites
Cloning a new Virtual Machine
Setting Up LMS in the Clone Virtual Machine
Known Problems
Prerequisites
This section explains the prerequisites for cloning to new VM from a parent VM:
Install vSphere Client in client server and connect to vCenter Server.
Install ESX 4.0, 4.1, or 5.0 in a machine.
Create a Datacenter and add the ESX host to it.
Configure the shared storage which is accessible to the host.
Create a virtual machine and select a datastore as shared storage disk.
Install LMS in the virtual machine.
Cloning a new Virtual Machine

This section explains how to clone to new VM from a parent VM:
1.
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.
Select Same format as source option and click Next.
7.
Select Do not customize option and click Next.
8.
Verify the settings and choose to Power on the virtual machine after creation.
9.
Click Finish to start the cloning process.
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
Note
After each step, check the Compatibility panel for any compatibility problem. Fix the problem and then
Setting Up LMS in the Clone Virtual Machine

This section explains how to configure LMS to run in the Clone Virtual Machine:
1.
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:
a. Stop daemons using the command net stop crmdmgtd.

b. Run the command NMSROOT\bin\perl NMSROOT\bin\hostnamechange.pl
The script will prompt you to reboot the server.

5.
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
group_name like '%PMC Groups/Port Groups/Link Ports'))



group_name like '%System Defined Groups'))

group_name like '%System Defined Groups'))

Restart UPMProcess to bring the pollers to Active state
Important Notes
url of dbreader - http://hostname:1741/dbreader/dbreader.html
User Id dba and Database Name upm
Command to stop UPMProcess: pdterm UPMProcess
Command to start UPMProcess: pdexec UPMProcess

OL-25957-01
5-11
Chapter 5
Cloning Parent VM to Template and Deploying Template to New VM

Before you clone a parent VM to template and deploy the template to a new VM, ensure you read the
Prerequisites.
This sections contains:
Cloning Parent VM to Template
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.
Cloning Parent VM to Template

This section explains how to clone the parent VM to a template:
1.
Launch the vSphere client and locate the parent VM.
2.
Right click on the parent VM > Template > Clone to Template.
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.
Verify the settings and click Finish
You can view the progress of template creation process from the Recent Tasks option or from the
Note
To deploy this template to a new VM, see Deploying Template to New VM.

This section explains how to deploy the template, which was cloned from the parent VM, to a new VM:
1.
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
8.
Verify the settings and choose to Power on the virtual machine after creation.
9.
Click Finish to start the cloning process.
You can view the progress of the cloning process can be seen from Recent Tasks option or from the
Note

OL-25957-01
5-13
Chapter 5
5-14
OL-25957-01
CH A P T E R

This chapter describes how to install and uninstall LMS 4.2 on Soft Appliance, Solaris and Windows
systems.
It describes the tasks you have to perform for installing LMS 4.2 on Soft Appliance, Solaris and
Windows systems. It also helps you to verify the installation, uninstall, and reinstall LMS 4.2.
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:
Performing Installation of LMS 4.2
Upgrading to LMS 4.2
Accessing LMS Server
Uninstalling LMS 4.2

This section explains how to install LMS 4.2 on Soft Appliance, Windows and Solaris systems for the
first time. It contains:
Downloading from Cisco.com
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
Extending File System in Soft Appliance
Changing Server Configuration Details
Viewing System Details
Installing LMS 4.2 Soft Appliance - ISO Image

OL-25957-01
6-1
Chapter 6
Installing LMS 4.2 on Solaris
Installing LMS 4.2 on Windows
Installing LMS 4.2 in Silent Mode
The LMS 4.2 installation program takes approximately:
35 minutes to complete on Windows
35 minutes to complete on Solaris
50 minutes to complete on Soft Appliance (OVA image)
75 minutes to complete on Soft Appliance (ISO image)
On a single server with the recommended hardware requirements. See System and Browser
Requirements for Server and Clientt 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 Setting Up Cisco Prime LMS in High Availability
and Disaster Recovery Environment.
Downloading from Cisco.com

To download software from Cisco.com:
Step 1
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
Choose 4.2 from the drop-down list.
Step 4
Download the required software.
Download Instructions for LMS 4.2 software on Soft Appliance - OVA Image
Important Download Notes for LMS 4.2 Software - OVA Image
Downloading Multiple Small Files - OVA Image
Download Instructions for LMS 4.2 software - OVA Image
6-2
OL-25957-01
Chapter 6

Important Download Notes for LMS 4.2 Software - OVA Image

This section contains important information that you should read before you begin downloading:
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 can download the split files in any order.
You must have a minimum of 16 GB of free space on your hard disk to download the LMS 4.2
Software.
Downloading Multiple Small Files - OVA Image

You can download LMS 4.2 Software for Soft Appliance as three split files.
To download these files, on cisco.com navigate to Support > Downloads > Cloud and Systems
Management > Routing and Switching Management > Cisco Prime LAN Management Solution >
Cisco Prime LAN Management Solution 4.2
Download Instructions for LMS 4.2 software - OVA Image

To download the LMS 4.2 Software OVA image from Cisco.com, you must do the following:
Step 1
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
Click LMS Software.
Step 3
Choose Linux platform.
Step 4
Choose 4.2 from the drop-down list.
Step 5
Download the following files one by one depending on your requirement:
For 500 SKU

Cisco_Prime_LMS_4_2_500_OVA.part1
Cisco_Prime_LMS_4_2_OVA_Install.zip
For 1500 SKU

For 5000 SKU

Cisco_Prime_LMS_4_2_Install_User_Guide.zip

OL-25957-01
6-3
Chapter 6
See Changing Server Configuration Details for information.

The End User License Agreement page appears.
Step 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:
For 500 SKU

Cisco_Prime_LMS_4_2_500_OVA.part12389465459 -1149239296
Cisco_Prime_LMS_4_2_OVA_Install.zip2465571057 11581
For 1500 SKU

For 5000 SKU

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
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.
Soft Appliance OVA software can be installed only on VMware environment.
In VMWare, the resources should not be in shared mode.
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

Unzip the downloaded Cisco_Prime_LMS_4_2_OVA_Install.zip file and extract the

Cisco_Prime_LMS_4_2_OVA.bat file and checksum.exe.
Ensure the checksum value of the Cisco_Prime_LMS_4_2_OVA.bat file is 3386523025 4055.
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:
For 500 SKU

Cisco_Prime_LMS_4_2_500.ova2913504062 1312832000
For 1500 SKU

For 5000 SKU

To install the LMS 4.2 Soft Appliance (OVA image):

Step 1
Invoke the VMware vSphere Client.
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
Enter the username and password of the VMware server.
Step 4
Click Login.
Step 5
Select File > Deploy OVF Template.

The Deploy OVF Template - Source window appears, see Figure 6-1.
Figure 6-1
Deploy OVF Template - Source window

OL-25957-01
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
Deploy OVF Template - OVF Template Details window
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
Deploy OVF Template - Name and Location window
Enter the name of the deployed template.
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.

OL-25957-01
6-7
Chapter 6
Figure 6-4
Deploy OVF Template - Datastore window
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
Deploy OVF Template - Disk Format window
Cisco recommends you to choose Thick provisioned format.
Click Next.
The Deploy OVF Template - Ready to Complete window appears. This window displays the deployment
setting details.

OL-25957-01
6-9
Chapter 6
Figure 6-6
Step 15
Note
Step 16
Deploy OVF Template - Ready to Complete window
Click Finish to start the deployment task.
The deployment tasks take approximately 50 minutes to complete.

Select a server which has the deployed template name specified in Step 9, from the servers listed on the
left pane of the vSphere Client window.
Right-click the selected server and select Power > Power On to start the server.
Step 17
Select the Console tab.

The Welcome screen appears.
Step 18
Press Enter in the console window to continue with the next step.
6-10
OL-25957-01
Chapter 6

Step 19
Enter the following configuration details of the server:
Note
Step 20
Hostname - You have to enter the server name and not FQDN.
The hostname should not exceed 19 characters.
Default DNS Domain - You have to enter the domain name of the server. For example cisco.com.
IP Address
IP Netmask
IP Default Gateway
Primary Name Server
Primary NTP Server
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
The following message appears:

For security reasons, passwords are not displayed. Do you want to view all the passwords?
(Y/N) [N]:
Step 21
If you enter Y, the following passwords will be displayed.
admin user account password
system identity user account password
system generated database password
The default option is N.

The DB engine process takes 15 to 20 minutes.
Step 22
The server is automatically rebooted.
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 reboot the Windows, Solaris or VM server, you must do so only after stopping the
daemons. You must not reboot the server while the daemons are running.

OL-25957-01
6-11
Chapter 6
Extending File System in Soft Appliance

This section contains the information required to extend the logical volume in soft appliance after
installation of OVA image.
Note
Before extending the file system, check the storage space on VM.
To check the file size in VMware, go to Configuration -> Storage -> Properties
Table 6-1 shows the VMware version and storage space details
Table 6-1
VMware Version and storage space
Version
Maximum File Size
VMware ESXi 4.1.0
256 GB
VMware ESXi 5.0.0
2 TB
VMware ESXi 5.1.0
2 TB
To check the used memory before adding new disk/new partition use the following command:
fdisk l
Example:
Output of fdisk l command in VMware 4.1.0

Disk /dev/sda: 161.0 GB, 161061273600 bytes
255 heads, 63 sectors/track, 19581 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Device Boot
Start
/dev/sda1 *
/dev/sda2
14
/dev/sda3
19454
End
13
Blocks Id System
104391 83 Linux
19453 156151800 8e Linux LVM

19580
1020127+ 83 Linux
Here /dev/sda partition used 161.0 GB

Hence, We have remaining 89 GB, so we can extend this by creating a new partition
Note
For VMWare 4.1.0, if fdisk shows 256 GB then we cannot extend using this disk as there is no space and
new disk need to be created.
Note
For VMWare 5.0.0 and VMWare 5.1.0, if fdisk shows 2 TB then we cannot extend using this disk as
there is no space and new disk need to be created.
6-12
OL-25957-01
Chapter 6

Note
Add a new hard disk before creating a new partition.
To check the used memory after adding new disk/new partition use the following command:
fdisk -l
Example:

Device Boot
Start
/dev/sda1 *
/dev/sda2
14
/dev/sda3
19454
End
Blocks Id System
13
104391 83 Linux
19453 156151800 8e Linux LVM

19580
1020127+ 83 Linux
Disk /dev/sdb: 21.4 GB, 21474836480 bytes

Device Boot
/dev/sdb1
Start
End
2610
Blocks Id System
20964793+ 8e Linux LVM

OL-25957-01
6-13
Chapter 6
To Initialize a disk or a partition for use by LVM entering the following command:
pvcreate /dev/sdb1
For disk use the command pvcreate /dev/sdb
For partition use the command pvcreate /dev/sdb1
Creating new hard disk
To create a new hard disk, refer the following steps:
Step 1
Power off the VM and Click edit settings.
Step 2
Select the hard disk and Click ADD button to add the hard disk.
6-14
OL-25957-01
Chapter 6

Creating new partition

To create a new partition after creating the new hard disk, enter the following commands:
#fdisk -l
#fdisk /dev/sda
#Type m
#Type n(add a new partition)
#Enter P(primary partition)
#Type p(Print the Partition table)
#Type V(verify the Partition)
#Type W(write table to disk and exit)
# reboot
#fdsik -l
Disk /dev/sdb: 21.4 GB, 21474836480 bytes
#mkfs.ext3 /dev/sdb
#Type m
#Type n(add a new partition)
#Type P(primary partition)
#Type P(Print the Partition table)
#Type V(verify the Partition)
#Type W(write table to disk and exit)
#reboot
#fdsik -l
#mkdir /Data
#mount /dev/sdb /Data

OL-25957-01
6-15
Chapter 6
There are two modes of extending file system in Linux. They are listed below:
Extending in Online Mode
Extending in Offline Mode
Extending in Online Mode

For extending the logical volume in online mode use the following steps:
Step 1
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
Display the attributes of volume groups using the following command:

vgdisplay
Step 4
Enter the following command to add physical volumes to a volume group:

vgextend smosvg /dev/sdb1
Step 5
Display the attributes of volume groups using the following command:

vgdisplay
Step 6
Display the attributes of a logical volume using the following command:

lvdisplay
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
Enter the following command to resize the ext2 file system:

resize2fs /dev/mapper/smosvg-varvol
6-16
OL-25957-01
Chapter 6

Extending in Offline Mode

Note
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:
umount -l /dev/mapper/smosvg-varvol
mount /dev/smosvg/varvol /var
Changing Server Configuration Details

To change the configuration details of the server after installation:
Step 1
Login with Soft Appliance console administrator user account.

This is the sysadmin username that you provided during installation.
Step 2
Enter the password.
Step 3
Enter the command shell.
Step 4
Enter the following command to stop the Daemons:

/etc/init.d/dmgtd stop
Step 5
Enter exit to go to the sysadmin mode.
Step 6
Enter the following command, in sysadmin view:

<HOSTNAME>/sysadmin# config terminal
Enter the configuration commands, one per line. End with CNTL/Z.
In all the examples, sysadmin represents the sysadmin username that you provided during installation.
Step 7
Change the required configuration details of the server.

You can change the hostname, Default DNS Domain, IP Address, IP Netmask, IP Default Gateway,
Primary Name Server, Primary NTP Server, Time Zone, Username or Password. See Table 6-2 for more
details.
Step 8
Enter the command end. The following will be displayed:

<HOSTNAME>/sysadmin#
Step 9
Enter the following command to update the changes:

<HOSTNAME>/sysadmin# write memory
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:

OL-25957-01
6-17
Chapter 6
Hostname
Default DNS Domain
IP Address, IP Netmask
IP Default Gateway
Primary Name Server
Primary NTP Server
Time Zone
The Daemons Manager will start automatically.

Step 11
Enter the following command to run the hostnamechange file:

<HOSTNAME>/sysadmin# shell
Enter shell password:
[<HOSTNAME>/root-ade ~]# /opt/CSCOpx/bin/perl /opt/CSCOpx/bin/hostnamechange.pl
-ohost <OLD_HOST_NAME> -nhost <NEW_HOST_NAME>
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-2 lists the examples of how to change the Soft Appliance server configuration details.
Table 6-2
Soft Appliance Server Configuration Details
Tasks
Configuration Details
Change the HostName
<OLD HOSTNAME>/sysadmin(config)# hostname <NEW HOSTNAME>

Changing the hostname may result in undesired side effects
on any installed application(s).
Are you sure you want to proceed? [y/n] y
LNX-LMS-05/admin(config)#
6-18
OL-25957-01
Chapter 6

Table 6-2
Soft Appliance Server Configuration Details (continued)
Change the Domain,

Gateway and Name server
LNX-LMS-05/sysadmin(config)# ip domain-name <DOMAIN NAME>

Changing the domain name may result in undesired side effects
on any installed application(s).
Are you sure you want to proceed? [y/n] y
LNX-LMS-05/sysadmin(config)# ip default-gateway
<DEFAULT_GATEWAY_ADDRESS>
LNX-LMS-05/sysadmin(config)# ip name-server
<PRIMARY_NAME_SERVER>
Change the NTP Server
LNX-LMS-05/sysadmin(config)# ntp server <PRIMARY_NTP_SERVER>
Change the IP address and

Subnet Mask
LNX-LMS-05/sysadmin(config)# interface GigabitEthernet 0

LNX-LMS-05/sysadmin(config-GigabitEthernet)#
LNX-LMS-05/sysadmin(config-GigabitEthernet)# ip address
<IP_ADDRESS> <MASK_ADDRESS>
Change the TimeZone
LNX-LMS-05/sysadmin(config)# clock timezone

<TIME_ZONE_VALUE>
See Supported Server Time Zones and Offset Settings for more details.
Change the Username/
Password
LNX-LMS-05/sysadmin(config)# username <USERNAME> password

plain <PASSWORD> role admin
LNX-LMS-05/sysadmin(config)# end
Viewing System Details

Table 6-3 lists the show commands that you can use in the Soft Appliance server.
Table 6-3
Show Command List
Show Commands
Description
application
Displays the application(s) information.

To display all the installed applications, enter the following command:
CARS-9/sysadmin# show application
cdp
<name>
<Description>
LMS
Cisco Prime LMS
Displays the CDP interface details.

To display the CDP interface details, enter the following command:
CARS-9/sysadmin# show cdp all
CDP protocol is enabled ...
broadcasting interval is every 60 seconds.
time-to-live of cdp packets is 180 seconds.
CDP is enabled on port GigabitEthernet0.
clock
Displays the clock information.

To display the current date, enter the following command:
CARS-9/sysadmin# show clock
Thu May 12 11:38:56 IST 2011

OL-25957-01
6-19
Chapter 6
Table 6-3
Show Command List (continued)
Show Commands
Description
cpu
Displays the CPU information.

To display the CPU information, enter the following command:
CARS-9/sysadmin# show cpu
processor : 0
model
: Intel(R) Xeon(R) CPU X7560
@ 2.27GHz
speed(MHz): 2261.000
cache size: 24576 KB
processor : 1
model
: Intel(R) Xeon(R) CPU X7560
@ 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
Displays the disk and filesystem information.

To display the disk and file system information, enter the following command:
CARS-9/sysadmin# show disks
temp. space 3% used (36996 of 1491808)
disk: 2% used (149208 of 7935392)
Internal filesystems:
all internal filesystems have sufficient free space
icmp_status
Displays the ICMP echo response configuration information.

To display the ICMP echo response configuration information, enter the following command:
CARS-9/sysadmin# show icmp_status
icmp echo response is turned on
6-20
OL-25957-01
Chapter 6

Table 6-3
Show Commands
Description
interface
Displays the interface information.

To display Configuration of IP details, enter the following command:
CARS-9/sysadmin# show interface
GigabitEthernet 0
Link encap:Ethernet
HWaddr 00:0C:29:E1:94:3F
inet addr:10.77.164.145
Bcast:10.77.164.159
Mask:255.255.255.224
inet6 addr: fe80::20c:29ff:fee1:943f/64 Scope:Link

UP BROADCAST RUNNING MULTICAST
MTU:1500
Metric:1
RX packets:138281 errors:0 dropped:0 overruns:0 frame:0

TX packets:122184 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:23371828 (22.2 MiB)
lo
TX bytes:92448564 (88.1 MiB)
Link encap:Local Loopback

inet addr:127.0.0.1
Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host

UP LOOPBACK RUNNING
MTU:16436
Metric:1

RX bytes:991883755 (945.9 MiB)
sit0
TX bytes:991883755 (945.9 MiB)
Link encap:IPv6-in-IPv4
NOARP
MTU:1480
Metric:1

RX bytes:0 (0.0 b)
TX bytes:0 (0.0 b)

OL-25957-01
6-21
Chapter 6
Table 6-3
Show Commands
Description
inventory
Displays hardware inventory information.

To display the hardware inventory information, enter the following command:
CARS-9/sysadmin# show inventory
NAME: "Cisco-VM chassis", DESCR: "Cisco-VM chassis"
PID: Cisco-VM-SPID
, VID: V01 , SN: FHDKICBCFDJ
Total RAM Memory: 3912720 kB

CPU Core Count: 2
CPU 0: Model Info: Intel(R) Xeon(R) CPU
X7560
@ 2.27GHz
CPU 1: Model Info: Intel(R) Xeon(R) CPU
X7560
@ 2.27GHz
Hard Disk Count(*): 1

Disk 0: Device Name: /dev/sda
Disk 0: Capacity: 64.40 GB
Disk 0: Geometry: 255 heads 63 sectors/track 7832 cylinders
NIC Count: 1
NIC 0: Device Name: eth0
NIC 0: HW Address: 00:0C:29:E1:94:3F
NIC 0: Driver Descr: e1000: eth0: e1000_probe: Intel(R) PRO/1000 Network Connection
(*) Hard Disk Count may be Logical.
logging
Displays the system logging information.

To display the logging information, enter the following command:
CARS-9/sysadmin# show logging
ADEOS Platform log:
----------------May 10 07:54:02 localhost debugd[2317]: [2727]: config:network: main.c[252]
[setup]: Setup is complete
May 10 07:54:43 localhost debugd[2317]: [3402]: application:install cars_install.c[245] [setup]: Install initiated with
bundle - Cisco_Prime_LAN_Management_Solution
ion_4_1.tar.gz, repo - SystemDefaultPkgRepos
May 10 07:54:43 localhost debugd[2317]: [3402]: application:install cars_install.c[259] [setup]: Stage area /storeddata/Installing/.1305039283
May 10 07:54:43 localhost debugd[2317]: [3402]: application:install cars_install.c[263] [setup]: Getting bundle to local
machine
May 10 07:54:43 localhost debugd[2317]: [3402]: transfer: cars_xfer.c[58] [setup]:
local copy in of
CiscoPrime_LAN_Management_Solution_4_1.tar.gz requested
--More--
6-22
OL-25957-01
Chapter 6

Table 6-3
Show Commands
Description
logins
Lists the login history.

To display the state of system logins, enter the following command:
CARS-9/sysadmin# show logins cli
admin
pts/0
10.77.203.146
Thu May 12 11:30
root
pts/0
10.77.203.227
Wed May 11 20:38 - 22:51
still logged in
(02:13)
root
pts/0
10.77.203.243
Wed May 11 14:40 - 16:28
(01:47)
root
pts/0
10.77.203.180
Wed May 11 12:20 - 12:31
(00:11)
admin
tty1
reboot
system boot
setup
tty1
reboot
system boot
Tue May 10 21:03
still logged in
2.6.18-238.1.1.e Tue May 10 21:02
(1+14:45)
Wed May 11 08:51 - down
(-11:-50)
2.6.18-238.1.1.e Wed May 11 08:46
(-11:-45)
wtmp begins Wed May 11 08:46:30 2011
memory
Displays the memory information.

To display the memory usage of all the running processes, enter the following command:
CARS-9/sysadmin# show memory
total memory:
free memory:
cached:
3912720 kB
67080 kB
425184 kB
swap-cached:
ntp
0 kB
Displays the Network Time Protocol (NTP) server details.

To show the status of the NTP server, enter the following command:
CARS-9/sysadmin# show ntp
Primary NTP
: 171.68.10.150
synchronised to NTP server (171.68.10.150) at stratum 3

time correct to within 30 ms
polling server every 1024 s
remote
refid
st t when poll reach
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
Warning: Output results may conflict during periods of changing synchronization.
ports
Displays all processes listening on open ports.

To display information about all the processes listening on the active ports, enter the following
command:
CARS-9/sysadmin# show ports
<display usage of ports>
process
Displays the system processes.

To display information about the active processes, enter the following command:
CARS-9/sysadmin# show process
<running processes are displayed>

OL-25957-01
6-23
Chapter 6
Table 6-3
Show Commands
Description
running-config
Displays the current system operating configuration.

To displays the contents of the current running configuration, enter the following command:
CARS-9/sysadmin# show running-config
Generating configuration...
!
hostname CARS-9
!
ip domain-name cisco.com
!
interface GigabitEthernet 0
ip address 10.77.164.145 255.255.255.224
ipv6 address autoconfig
!
ip name-server 72.163.128.140 64.104.76.247
!
ip default-gateway 10.77.164.129
!
clock timezone Asia/Calcutta
!
ntp server 171.68.10.150
!
username admin password hash $1$MVal9Zcx$VRE0HcIs/YY4/1xYZESJz0 role admin
!
service sshd
!
password-policy
lower-case-required
upper-case-required
digit-required
no-username
disable-cisco-passwords
min-password-length 6
!
logging localhost
logging loglevel 6
!
cdp timer 60
cdp holdtime 180
cdp run GigabitEthernet 0
!
icmp echo on
6-24
OL-25957-01
Chapter 6

Table 6-3
Show Commands
Description
startup-config
Displays the startup system operating configuration.

To display the contents of the startup configuration, enter the following command:
CARS-9/sysadmin# show startup-config
!
hostname CARS-9
!
!
ip address 10.77.164.145 255.255.255.224
!
ip name-server 72.163.128.140 64.104.76.247
!
ip default-gateway 10.77.164.129
!
clock timezone Asia/Calcutta
!
ntp server 171.68.10.150
!
username sysadmin password hash $1$MVal9Zcx$VRE0HcIs/YY4/1xYZESJz0 role admin
!
service sshd
!
password-policy
lower-case-required
upper-case-required
digit-required
no-username
disable-cisco-passwords
min-password-length 6
!
logging localhost
logging loglevel 6
!
!
icmp echo on
!

OL-25957-01
6-25
Chapter 6
Table 6-3
Show Commands
Description
tech-support
Displays the tech output.

To display the tech output, enter the following command:
CARS-9/sysadmin# show tech-support
###################################################
Application Deployment Engine(ADE) - 2.0.1.021
Technical Support Debug Info follows...
###################################################
*****************************************
Displaying startup-config...
*****************************************
!
hostname CARS-9
!
!
ip address 10.77.164.145 255.255.255.224
!
ip name-server 72.163.128.140 64.104.76.247
--More--
terminal
Displays the terminal configuration parameters.

To display the information about the terminal configuration, enter the following command:
CARS-9/sysadmin# show terminal
TTY: /dev/pts/0 Type: "vt100"
Length: 27 lines, Width: 80 columns
Session Timeout: 30 minutes
timezone
Displays the timezone.

To display the time zone as set on the system, enter the following command:
CARS-9/sysadmin# show timezone
Asia/Calcutta
SeeSupported Server Time Zones and Offset Settings for more details.
6-26
OL-25957-01
Chapter 6

Table 6-3
Show Commands
Description
timezones
Displays the timezones.

To obtain a list of time zones, enter the following commands:
CARS-9/sysadmin# show timezones
CST6CDT
Libya
Mexico/General
Mexico/BajaSur
Mexico/BajaNorte
Poland
Mideast/Riyadh89
--More--
udi
Displays the udi information.

To display the information about the systems Unique Device Identifier (UDI), enter the following
command:
CARS-9/sysadmin# show udi
SPID: Cisco-VM-SPID
VPID: V01
Serial: FHDKICBCFDJ
<<<display information about the systems Unique Device Identifier (UDI)>>>
uptime
Displays the system uptime.

To display the system uptime, enter the following command:
CARS-9/sysadmin# show uptime
2 day(s), 17:53:09
users
Displays the logged-in users information.

To display a list of users, enter the following command:
LNX-LMS-05/sysadmin# show users
USERNAM
ROLE
admin
Admin
admi
Admin
HOST
10.77.203.146
TTY
LOGIN DATETIME
tty1
Wed May 11 22:53:22 2011
pts/0
Wed May 11 23:50:10 2011

OL-25957-01
6-27
Chapter 6
Table 6-3
Show Commands
Description
version
Displays the version details.

To display all the installed application versions, enter the following command:
CARS-9/sysadmin# show version
Cisco Application Deployment Engine OS Release: 2.0
ADE-OS Build Version: 2.0.1.043
ADE-OS System Architecture: x86_64
Copyright (c) 2005-2010 by Cisco Systems, Inc.
All rights reserved.
Hostname: CARS-9
Version information of installed applications
--------------------------------------------Cisco Prime LAN Management Solution
----------------------------------Version
: 4.2
Vendor
: Cisco Systems, Inc.
-----------------------------------
application status LMS
Displays the status of LMS applications.

To display the status of LMS application, enter the following command:
CARS-9/sysadmin# show application status LMS
Process
State
Pid
*******
*****
***
ESS
Program started - No mgt msgs received
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
Administrator has shut down this server
FHPurgeTask
Transient terminated
-----More-----
6-28
OL-25957-01
Chapter 6

Table 6-3
Show Commands
Description
application version LMS Displays the version of the LMS application.

To display LMS version, enter the following command:
CARS-9/sysadmin# show application version LMS
Cisco Prime LAN Management Solution
----------------------------------Version
: 4.2
Vendor
: Cisco Systems, Inc.
-----------------------------------
logging application LMS Displays the LMS installation log details.

To display the LMS installation log, enter the following command:
CARS-9/sysadmin# show logging application LMS
LMS Application log:
-------------------======================================================================
Started :
Tue May 10 07:55:25 PDT 2011
======================================================================
================- 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
Displays the system log details.

To display system log, enter the following command:
CARS-9/sysadmin# show logging system
<<<<<<<<<<ADE.log displayed>>>>>>>>>>>>>>
ip route
Displays the system IP interface details.

To display the information about the system IP interfaces, enter the following command:
CARS-9/sysadmin# show ip route
Kernel IP routing table
Destination
Gateway
Genmask
10.77.164.128
0.0.0.0
255.255.255.224 U
Flags Metric Ref

0
0 eth0
0.0.0.0
10.77.164.129
0.0.0.0
0 eth0
UG
Use Iface

OL-25957-01
6-29
Chapter 6
Note
The configuration commands which are not listed in the table are not tested and not supported in Soft
Appliance Server.
Table 6-4 lists the commands that are supported for admin users in Soft Appliance Server.
Table 6-4
Command list
Commands
Description
exit
To exit from the EXEC mode.
nslookup
To enable DNS lookup for an IP address or a

hostname.
ssh
To SSH to a remote IP address.
telnet
To Telnet to a remote IP address.
terminal
To set terminal line parameters.
traceroute
To trace the route to a remote IP address.
ping
To ping a remote IP address.
Table 6-5 lists the commands that are supported for non admin users in Soft Appliance Server.
Table 6-5
Command list
Commands
Description
exit
To exit from the EXEC mode.
nslookup
To enable DNS lookup for an IP address or a

hostname.
ssh
To SSH to a remote IP address.
telnet
To Telnet to a remote IP address.
terminal
To set terminal line parameters.
Table 6-6 lists the commands that are not supported for non admin users in Soft Appliance Server.
Table 6-6
Note
Command list
Commands
Description
traceroute
To trace the route to a remote IP address.
ping
To ping a remote IP address.
Ping6 for IPV6 command is not supported for both admin and non admin users in Soft Appliance Server.
6-30
OL-25957-01
Chapter 6

Note
Include the Syslog information in the /opt/CSCOpx/conf/syslog-entries.txt and run the write mem in
the sysadmin console.
Installing LMS 4.2 Soft Appliance - ISO Image

Read the following points before installing the software:
Note
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.
It takes approximately one hour to install the Soft Appliance.
If the virus scanner is enabled on your system, the installation might take longer time.
Installing LMS 4.2 Soft Appliance on VMware
Installing LMS 4.2 Soft Appliance on NCS and UCS Servers
Installing LMS 4.2 Soft Appliance on VMware

To install the LMS 4.2 Soft Appliance (ISO image):
Step 1
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.
In the boot menu the following options appear:
1.
Removable Devices
2.
Hard Drive

OL-25957-01
6-31
Chapter 6
3.
CD-ROM Drive
4.
Network boot from Intel E1000
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>
The following options appears:
[1] Cisco Prime LAN Management Solution 4.2 Installation

This option allows you to perform installation of LMS 4.2.
[2] Recover administrator password

This option allows you to recover the administration password. Follow Step 3 to Step 17 of
Recovering Admin Password on Soft Appliance Installed on VMware, to recover the administration
password.
<Enter> Boot existing OS from Hard Disk

This allows you to boot up the existing OS available in the hard disk.
Step 11
Enter 1 to continue the installation.

All the applications of CARS and LMS are copied to the server, and the server gets rebooted.
Note
It takes approximately 40 minutes to copy all the applications of CARS and LMS.
Step 12
Type setup in the console to set the configuration.
Step 13
IP Address
Subnetmask
Gateway
DNS Domain - You have to enter the domain name of the server. For example cisco.com.
Primary Server Name
Enter one of the following corresponding to Add/Edit another name server:

Enter Y to enter the secondary server name.
or
Enter N to proceed to NTP server configuration details.
Enter one of the following corresponding to primary NTP server.

Enter Y to enter the secondary NTP server name.
or
Enter N to proceed to the next configuration details.
6-32
OL-25957-01
Chapter 6

System Time Zone
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

Do you want to see the passwords at the end of the installation? (Y/N) [N]:
If you enter Y, the following passwords will be displayed before the server gets rebooted.

Step 15
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

OL-25957-01
6-33
Chapter 6
Installing LMS 4.2 Soft Appliance on NCS and UCS Servers

To install LMS 4.2 Soft Appliance to NCS and UCS servers:
Step 1
Login to a machine where you want to install LMS 4.2 Soft Appliance.
Step 2
Insert Soft Appliance LMS 4.2 DVD into the server.

The following options appear in the console:
Cisco Prime LAN Management Solution 4.2 Installation

This option allows you to perform installation of LMS 4.2.
Recover administrator password

This option allows you to recover the administration password. See Recovering Admin Password on
Soft Appliance Installed on NCS and UCS Server for more details.
Step 3
Enter 1 to continue the installation.

All the applications of CARS and LMS are copied to the server, and the server gets rebooted.
Note
It takes approximately 40 minutes to copy all the applications of CARS and LMS.
Step 4
Type setup in the console to set the configuration.
Step 5
IP Address
Subnetmask
Gateway
DNS Domain - You have to enter the domain name of the server. For example cisco.com.
Primary Server Name
Enter one of the following corresponding to Add/Edit another name server:

Enter Y to enter the secondary server name.
or
Enter N to proceed to NTP server configuration details.
Enter one of the following corresponding to primary NTP server.

Enter Y to enter the secondary NTP server name.
or
Enter N to proceed to the next configuration details.
System Time Zone
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-34
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

Do you want to see the passwords at the end of the installation? (Y/N) [N]:
If you enter Y, the following passwords will be displayed before the server gets rebooted.

Step 7
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

OL-25957-01
6-35
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
Insert Soft Appliance LMS 4.2 DVD into the server.

The following options appears in the console:
Step 3
Enter 2 to proceed with the password recovery process.

The Admin Password Recover window appears.
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
Re-enter the password for confirmation.
Step 7
Enter y to save and reboot the system.

If you enter n, the new password will not be saved and you will be redirected to Step 4 to continue with
password recovery process. The responses of y and n are not case sensitive.
Recovering Admin Password on Soft Appliance Installed on VMware

To recover the administration password on Soft Appliance installed on VMware:
Step 1
Go to
http://software.cisco.com/download/release.html?mdfid=284259296&softwareid=280775102&release
=4.2&os=Linux.
Step 2
Download the Cisco_Prime_LAN_Management_Solution_4_2.iso
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-36
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.
Network boot from Intel E1000
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:
Step 13
Enter 2 to proceed with the password recovery process.

The Admin Password Recover window appears.
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.
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
Re-enter the password for confirmation.
Step 17
Enter y to save and reboot the system.

If you enter n, the new password will not be saved and you will be redirected to Step 14 to continue with
password recovery process. The responses of y and n are not case sensitive.
Installing LMS 4.2 on Solaris

To install LMS 4.2 for the first time on a Solaris system:
Step 1
Log into the machine where you want to install LMS 4.2.
Step 2
Insert the LMS 4.2 DVD.

OL-25957-01
6-37
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
Change the execution mode of permission to setup.sh by entering:

# chmod +x setup.sh
Step 5
Run the installation setup script by entering:

# sh setup.sh
Or
#./setup.sh
A Welcome message appears:

Welcome to Cisco Prime LAN Management Solution 4.2 Applications setup program.
A prompt appears:
Press ENTER to read the following License Agreement, or Press n to proceed with
setup? (y/n) [y]:
If you enter y, you can view the license agreement details.
If you enter n, the following prompt appears:

You must accept this License Agreement to proceed with the installation.
If you enter n, the installation will abort.
Do you accept all the terms of the License Agreement? (y/n) [n]:
Step 6
Enter y to proceed.
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:
L to provide the License file location.
6-38
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.
Q to quit the installation.
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
Enter the LMS Login password and confirm it.

The alert message appears prompting you to use the login password as database password (Y/N)?
If you enter Y, the system uses the login password as database password. If you enter N, the system
generates random password for database.
The system uses Login password for Admin and System Identity Account passwords, and generates a
random password for casuser account.
After entering the password details, the following message appears:
Do you want to see the passwords at the end of installation? (y/n) [n]:
If you enter Y, the following prompt appears:

Passwords will be displayed in an unencrypted form. Ensure security of the passwords.
Enter y to continue
Step 10
Enter Y, all the passwords will be displayed at the end of installation.

If you enter N, the passwords will not be displayed.
Installation now proceeds. The installation completes without displaying more questions and the system
prompt appears.
The following messages appear at the end of the installation:
Software Installation Tool Completed
Possible Warnings/Errors Encountered
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.

OL-25957-01
6-39
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.
Installing LMS 4.2 on Windows

To install LMS 4.2 for the first time on a Windows system:
Step 1
Login as administrator to the machine where you want to install LMS 4.2.
Step 2
Note
Step 3
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
Read the prerequisite details and click OK.

The LMS Setup window appears.
6-40
OL-25957-01
Chapter 6

Step 5
Select I accept the terms of the license agreement checkbox.

To view the license details, click View button.
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
Select one of the following:
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
Enter the Login password.

For more information on passwords, see LMS Login and Database Passwords.
The system uses Login password for Admin and System Identity Account passwords, and generates a
random password for casuser account.

OL-25957-01
6-41
Chapter 6
Step 10
Re-enter the Login password to confirm.
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
Click Install to continue.

The Reboot window appears after the installation is complete.
The Reboot window has view buttons that allow you to view the following details:
Errors and Warnings
Installation Information
Password Details
Health Monitor Report
Errors and Warnings
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
Allows you to view the following LMS Password details:
User Admin Password
User Guest Password
System Identity Account Password
Database Password
Health Monitor Report
The Health Monitor report provides the following Hardware Parameter details:
Step 13
Memory availability
Swap
CPU
DSN
Backup status
Number of MIB objects being polled
Maximum number of MIB objects that can be managed
Syslog database size
Click Reboot button to restart your machine.
6-42
OL-25957-01
Chapter 6

To restart your machine later, click Reboot Later button.
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.
Installing LMS 4.2 in Silent Mode

Silent installation or unattended installation is supported in the LMS single installer. You can perform
only a fresh installation of LMS 4.2 in silent installation mode.
Silent install does not prompt for your inputs. It continues the installation based on your inputs provided
in a file. You should save the installation inputs in a file and store the file in the system. See Creating an
Answer File and Sample Answer Files for more information.
To install LMS 4.2 in silent mode:
Step 1
Note
drive. Ensure that you copy the entire contents from the DVD to the hard drive.
Step 2
Navigate to images/disk1 directory at the command prompt.
Step 3
Enter the following commands to install LMS 4.2 in silent mode:
On Solaris: sh setup.sh -q answer_file_name
On Windows: setup.exe QUIET answerfile=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
Restart your system after the installation is complete.
Creating an Answer File
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
Optional. Allows quiet installation to install into a directory other

than NMSROOT.
If not specified, installation goes into /opt/CSCOpx on Solaris or
c:\Program Files\CSCOpx on Windows.
adminPassword
Specifies the login password for the admin user. This is mandatory.

OL-25957-01
6-43
Chapter 6
secretPassword
Specifies the login password for the secret user.
(Solaris only)
casuser
(Windows Only)
If casuser password does not exist by the time of installation, the

framework generates random password for casuser.
If the random password is successful, then no input is required.
If the random password fails, installation opens a dialog

requesting new password.
In quiet mode, installation attempts to load the casuser password

from the answer file. If no casuser password is specified in the
answer file, installation attempts random password, and might fail
if the random password does not pass the company policy.
systemIdentityAccountPassword Password for the System Identity Account. This is mandatory.
(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.

The following upgrade paths are supported:
6-44
OL-25957-01
Chapter 6

Table 6-7
Current LMS Version
Type of Upgrade
LMS 4.1
Remote migration
Procedure
1.
Back up the data in the old machine having LMS 4.1.
2.
Install LMS 4.2.
3.

1.
Install LMS 4.2 over LMS 4.1.

LMS 4.0.1
Remote migration
1.
Back up the data in the old machine having LMS 4.0.1.
2.
Install LMS 4.2.
3.

1.
Install LMS 4.2 over LMS 4.0.1.

LMS 3.2 SP1
Remote migration
1.
Back up the data in the old machine having LMS 3.2 SP1.
2.
Install LMS 4.2.
3.


OL-25957-01
6-45
Chapter 6
Table 6-7
Upgrade and Data Migration Procedure (continued)
Current LMS Version
Type of Upgrade
LMS 2.6, LMS 2.6 SP1, Remote migration

LMS 3.0, LMS 3.0
December 2007 update,
LMS 3.1
LMS 2.6/LMS 2.6 SP1/
LMS 3.0/LMS 3.0 December
2007 update/LMS 3.1> LMS
3.2 >LMS 4.0 > LMS 4.01 >
LMS 4.2
LMS 2.2, LMS 2.5,
LMS 2.5.1
Procedure
1.
2.
3.
Migrate the data to LMS 4.0.1. For more information, see

4.
Install LMS 4.2.

Remote migration
1.

2.
Upgrade from the earlier versions of LMS to LMS 2.6 and

migrate the data, using the instructions in:
Readme for CiscoWorks LMS 2.6 Update on Solaris
LMS 2.2 / LMS 2.5 /

LMS 2.5.1 > LMS 2.6 >
LMS 4.0 > LMS 4.0.1
>LMS 4.2
Readme for CiscoWorks LMS 2.6 Update on Windows

Data Migration Guide for LAN Management Solution
2.6
3.
4.
Migrate the data to LMS 4.0.1.

5.
Install LMS 4.2.

6-46
OL-25957-01
Chapter 6

Inline Upgrade to LMS 4.2 on Soft Appliance

To upgrade from LMS 4.1 to LMS 4.2:
Step 1
Download the Cisco_Prime_LAN_Management_Solution_4_2_Upgrade.tar.gz file from CCO or DVD.
Step 2
Copy the Cisco_Prime_LAN_Management_Solution_4_2_Upgrade.tar.gz to local disk partition of LMS

4.1 installed server (/localdisk).
Step 3
Login with your credentials to the VM Console through Vsphere client.
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:
Local CD-ROM drive (read only)
disk:
Local storage
ftp:
URL using a FTP server
http:
URL using a HTTP server (read only)
https:
URL using a HTTPS server (read only)
nfs:
URL using a NFS server
sftp:
URL using a SFTP server
tftp:
URL using a TFTP server
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
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
myhost/admin#
You can use the above mentioned steps for other protocols.

OL-25957-01
6-47
Chapter 6
Remote Upgrade to LMS 4.2
Step 6
Run the below command in the admin console in VSphere client.

myhost/admin#application upgrade Cisco_Prime_LAN_Management_Solution_4_2_Upgrade.tar.gz
<<myrepo>>
Save the ADE-OS running configuration?(yes/no) [yes]?
Step 7
Note
Press Enter to continue with LMS 4.2 upgrade.
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.
Inline Upgrade to LMS 4.2 on Windows

The LMS 4.2 inline upgrade procedure for Windows is same as the installation procedure explained in
the section Installing LMS 4.2 on Windows. Specify the backup folder during inline upgrade to LMS 4.2.
Inline Upgrade to LMS 4.2 on Solaris

The LMS 4.2 inline upgrade procedure for Solaris is same as the installation procedure explained in the
section Installing LMS 4.2 on Solaris. Specify the backup folder during inline upgrade to LMS 4.2.
Remote Upgrade to LMS 4.2

This section contains information on:
Remote Upgrade to LMS 4.2 on Solaris
Remote Upgrade to LMS 4.2 on Windows
Remote Upgrade to LMS 4.2 on Solaris

To upgrade from the previous versions of LMS (LMS 3.2 SP1, LMS 4.01 or LMS 4.1) to LMS 4.2 on a
different Solaris machine:
Step 1
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
Take a backup of the LMS data.
Step 3
Login to the machine where LMS 4.2 is to be installed.
Step 4
Follow the install procedure to install LMS 4.2. See Installing LMS 4.2 on Solaris.
Step 5
Migrate the data to LMS 4.2.
6-48
OL-25957-01
Chapter 6

To migrate and restore the LMS data, follow the procedure in Migrating Data to Cisco Prime LAN
Notes for Remote Upgrade
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, seeMigrating Data to Cisco
Note
Remote Upgrade to LMS 4.2 on Windows

To remote upgrade from the previous versions of LMS (LMS 3.2 SP1, LMS 4.01 or LMS 4.1) to LMS
4.2 on a different Windows machine:
Step 1
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
Take a backup of the LMS data.
Step 3
Log into the machine where LMS 4.2 is to be installed.
Step 4
Follow the install procedure to install LMS 4.2. See Installing LMS 4.2 on Windows.
Step 5
Migrate the data to LMS 4.2.

To migrate and restore the LMS data follow the procedure in Migrating Data to Cisco Prime LAN
Notes for Remote Upgrade
When you back up the data from LMS 3.2 SP1 and restore the data on LMS 4.2, a warning message
continue the data restore. For more details on backing up and restoring data, see Migrating Data to Cisco
Note

You can verify LMS 4.2 installation by following either of these procedures.

OL-25957-01
6-49
Chapter 6
Procedure 1
You can verify LMS 4.2 installation using either of these methods:
Enter the command pdshow from NMSROOT/bin.

Where, NMSROOT is the LMS installation directory (by default, SystemDrive:\Program
Files\CSCOpx and SystemDrive is the Windows operating system installed directory and for Solaris
and Soft Appliance it is /opt/CSCOpx).
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,
User Tracking

Image Management
Services/Processes
Apache
EDS-GCF
CmfDbEngine
ESS
CmfDbMonitor
EssMonitor
CMFOGSServer
EventFramework
CSDiscovery
FDRewinder (Only on Solaris)
CSRegistryServer
jrm
DCRServer
LicenseServer
DCRDevicePoll
NameServer
diskWatcher
NameServiceMonitor
EDS
Proxy (Windows only)
CSSCPServer
Tomcat
TomcatMonitor
ANIServer
UTLITE
ANIDbEngine
UTMajorAcquisition
UTManager
MACUHIC
VNMServer
WlseUHIC
ChangeAudit
RMEDbEngine
ConfigMgmtServer
SyslogAnalyzer
ConfigUtilityService
SyslogCollector
CTMJrmServer
PMCOGSServer
EnergyWise
EssentialsDM
ICServer
Compliance and Audit

Manager (CAAM) Server
6-50
OL-25957-01
Chapter 6

Functionalities
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
Fault Management
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
Version With Patch Level
LAN Management Solution
4.2

LMS, by default, uses port number 1741 to access the LMS Server in normal (HTTP) mode and port
number 443 to access the server in secure (HTTPS) mode.
To access the server from a client system, enter any one of these URLs in your web browser:
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.

OL-25957-01
6-51
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
Port Scanning is not recommended in LMS.

When you access the LMS Windows 2008 server using Internet Explorer 8, scripts are not loaded, as
Internet Explorer Enhanced Security Configuration (IE ESC) is turned on in IE 8 browser, for more
information see, Enabling Loading of Scripts in Windows 2008.
Clearing Cache and Cookies

The instructions for clearing the cache and cookies may be different for each browser and version. Here
are the steps for deleting cache and cookies for the supported browsers and versions in LMS:
Internet Explorer 8.0 and 9.0
Mozilla FireFox 8.0 and 9.0
Internet Explorer 8.0 and 9.0

To clear the cache and cookies:
Step 1
Go to Tools menu.
Step 2
Select Delete Browsing History.
Step 3
Select the check box for Temporary Internet Files and Cookies.
Step 4
Click Delete. Once the files have been deleted, click Okay.
Mozilla FireFox 8.0 and 9.0

To clear the cache and cookies:
Step 1
Go to Tools menu.
Step 2
Select Clear Recent History.
6-52
OL-25957-01
Chapter 6

Step 3
Select Everything from the Time Range to Clear drop-down list.
Step 4
Select Details.
Step 5
Select:
Step 6
Cache to clear the browser cache.
Cookies to delete the cookies.
Click Clear Now.
Enabling Loading of Scripts in Windows 2008

When you access the LMS Windows 2008 server using Internet Explorer 8, scripts are not loaded, as
Internet Explorer Enhanced Security Configuration (IE ESC) is turned on in IE 8 browser. IE ESC
reduces the exposure of your server to potential attacks from Web-based content.
To disable the Internet Explorer Enhanced Security Configuration option in IE 8:
Step 1
Select Start > All Programs > Administrator Tools > Server Manager.
The Server Summary page appears.
Step 2
Click Configure IE ISC under Security Information.

The Internet Explorer Enhanced Security Configuration popup appears.
Step 3
Click the Off option for both Administrators and Users.
Step 4
Click OK.
Step 5
Restart the browser.

After you have accessed the LMS server, to login for the first time, do the following:
Step 1
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
Click Login or press Enter.

You are now logged into LMS server.
The LMS Getting Started Introduction page appears.
The new LMS User Interface provides easy access to functions based menus, access to information
portlets, searching objects, fault bar, icons for viewing favorites, viewing legacy navigation, adding
portlets, changing dashboard layout, and more. See Understanding the Cisco Prime LMS in Getting
Started with Cisco Prime LAN Management Solution 4.2 for more information.

OL-25957-01
6-53
Chapter 6

Before You Begin Uninstallation
Uninstalling LMS 4.2 on Solaris
Uninstalling LMS 4.2 on Windows
Before You Begin Uninstallation

The following are some precautionary notes on uninstallation that you must read:
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.
Uninstalling LMS 4.2 on Solaris

To uninstall LMS 4.2 on a Solaris system:
Step 1
Enter the following commands as root to start the uninstall script:

# cd /opt/CSCOpx/bin/
where /opt/CSCOpx is the default installation directory.
Step 2
Note
From the /opt/CSCOpx/bin/ directory, enter the ./uninstall.sh command
We recommend you not to use /opt/CSCOpx/bin/uninstall.sh command to uninstall LMS

The uninstall messages get appended to the /var/tmp/LMS_uninstall_20060623_102035.log.
LMS is currently installed in the server. Delete the configured collectors to remove the
corresponding collector entries from the source routers, and uninstall LMS. 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.'N'
to continue with uninstall without deleting the collectors in the device. Default value
is 'N'.
You should do either one of the following:
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-54
OL-25957-01
Chapter 6

Enter n to continue with uninstall without deleting the collectors in device
The uninstallation proceeds.

After the uninstall is complete, the following messages appear:
All files were deleted successfully.
Possible Warnings/Errors Encountered
The uninstallation program lists the warning and error messages.

Step 3
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.
Uninstalling LMS 4.2 on Windows

To uninstall LMS 4.2 on a Windows system:
Step 1
Go to the Windows desktop and select Start > Programs > Cisco Prime LMS > Uninstall Cisco
Prime LMS.
Uninstallation process begins.
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'.
You should do either one of the following:
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
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
Select Yes, I want to restart my computer now and click Finish.

OL-25957-01
6-55
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.

Re-installation is installing the product over the existing one without performing an uninstallation.
You can re-install LMS 4.2 by running the installation program on the system currently running the
product. LMS 4.2 supports new installation and re-installation of applications at the same time.
Re-installation preserves the settings from the previous installation.
To reinstall LMS 4.2, follow the similar procedure as detailed in Performing Installation of LMS 4.2.
Notes for Re-installation
During re-installation, you can choose to enter new passwords or retain the existing ones. For more
information on passwords, see Password Information.
You will be prompted to provide a backup location.
In Windows, locked files window might appear during re-installation.

The locked files list:
Appears when some dll or exe located in NMSROOT has valid reference handles in the memory
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.
Click Yes and proceed with the installation.
Downloading and Installing CiscoWorks LMS 4.2 Using

Windows 2012 Patch
To install the LMS 4.2 using Windows 2012 patch on Windows 2012 servers for the first time (fresh
installation of LMS 4.2):
Step 1
Go to http://software.cisco.com/download/type.html?mdfid=284259296&flowid=37207
6-56
OL-25957-01
Chapter 6

Step 2
Download the patch for Windows 2012 Server Standard and Data Center to your system.
Step 3
Go to the directory where you have downloaded the patch and double-click
CiscoPrime_LMS_4.2_WIN12.exe.
The following message will pop up:
1) CiscoPrime_LMS_4.2_WIN12.exe is supported only on LMS 4.2 on windows 2012 server
platform
2) You can upgrade to LMS 4.2.5 or later versions using the conventional upgradation steps
3) Upgrading to any patch release till LMS 4.2.4 is not supported
4) Click OK to choose the installable.
A new window opens and you can browse to the location in your local hard drive where the LMS 4.2
image is stored or you can select the installable from the DVD.
If you select an unsupported Windows installable, the following message appears:
You have chosen an incorrect setup file. Select LMS 4.2 setup.exe to continue with
installation.
For more information on performing a new installation of LMS 4.2 see,

http://www.cisco.com/en/US/docs/net_mgmt/ciscoworks_lan_management_solution/4.2/install/guide/i
nstl.html#wp1602146
The installation of LMS 4.2 along with Windows 2012 patch will take approximately the same time as
that of LMS 4.2.
Note
You can reinstall LMS 4.2 using the Windows 2012 patch by following the procedure given above.

OL-25957-01
6-57
Chapter 6
6-58
OL-25957-01
CH A P T E R
Migrating Data to Cisco Prime LAN Management

Solution 4.2
This chapter describes how to migrate data to LMS 4.2, and contains the following sections:
Scope of Data Migration
Guidelines to Post-Upgrade Activities

Migration is the process of carrying over data from an older version of LMS to a newer version of LMS.
Migration involves:
1.
Backing up the older version of LMS data.
2.
Installing the newer version of LMS.
3.
Restoring the backed up data.
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.
Note
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.
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

OL-25957-01
7-1
Chapter 7
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
continue the data restore.

This section lists the data that is migrated for Common Services, Network Topology, Layer 2 Services
and User Tracking, Inventory, Config and Image Management, Fault Management, IPSLA Performance
Management, CiscoView, Device Performance Management and Portal when you upgrade to LMS 4.2.
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:
Common Services Data Migration Scope
Network Topology, Layer 2 Services and User Tracking Data Migration Scope
Inventory, Config and Image Management Data Migration Scope
Fault Management Data Migration Scope
IPSLA Performance Management Data Migration Scope
CiscoWorks Assistant Data Migration Scope
CiscoView Data Migration Scope
Device Performance Management Data Migration Scope
Portal Data Migration Scope
7-2
OL-25957-01
Chapter 7

Common Services Data Migration Scope

The Common Services (CS) data can be backed up using either using the Normal or the Selective mode.
Normal Backup
The following data gets migrated:
LMS User information
Single Sign-on configuration
Device and Credential Repository (DCR) configuration
Peer Certificates and Self Signed Certificates
Peer Server Account information
Login Module settings
Software Center map files
License data
Core Client Registry
System Identity Account configuration
Cisco.com User configuration
Proxy User configuration
Jobs and Resources data, DCR data, Groups data, and other data stored in the database
Discovery settings and Scheduled jobs
Local User Policy Setup
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
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

OL-25957-01
7-3
Chapter 7
Selective Backup
When you run a selective data backup from CLI, all the data mentioned above gets backed up except:
Software Center map files
Once, Immediate, and Completed jobs data for all applications
UDM Device State Change After Migration Based on License Limit
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:
Upgrade the LMS 4.2 license
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.
After Migration UDM Policy is Set as Managed By All devices by Default
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-4
OL-25957-01
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
Settings related to Layer 2 services (User Tracking, VRF-lite)
Data Collection Scheduled Details
User Defined Groups
Config Credentials
Data Purge Settings
Trap Configuration Settings
Custom Reports and Layouts
Topo Map PreferencesThis is applicable only for upgrade
Topology layoutsManually updated topology layouts will not be migrated for upgrade and
backup/restore.
MAC Detection Settings
Device Details
Port and VLAN Details
Campus Jobs and Archives
User Tracking Jobs and Archives
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
Device Details
Port and VLAN Details
Campus Archives, UT Archives and VNM Archives

OL-25957-01
7-5
Chapter 7
Inventory, Config and Image Management Data Migration Scope

Inventory, Config and Image Management data in LMS 4.2 (known as RME in earlier LMS versions)
can be backed up using either the Normal or the Selective mode.
Normal Backup
The following data gets migrated to LMS 4.2:
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-6
OL-25957-01
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
Admin Purge policies
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

OL-25957-01
7-7
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
Appliance.
Port groups
Module groups
Template Center
Template Center jobs
WorkCenters
EnergyWise jobs
Identity jobs
ASP jobs
SI jobs
SI profiles
SI configs
7-8
OL-25957-01
Chapter 7

Selective Backup
SWIM Images
Common Reporting Infrastructure archives
Config editor data
Syslog data
Energywise Reports Archives
SmartInstall Archives
Identity Report Archives
Fault Management Data Migration Scope

Fault Management in LMS 4.2 (known as DFM in earlier LMS versions), can be backed up using either
the Normal or the Selective mode.
Normal Backup
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)
The following notification information:

Mail notification information
Mail recipient information
Mail sender ID
Syslog notification
SMTP addresses
Trap forwarding addresses
Trap notification addresses and ports
Fault groups
Some polling and threshold settings
Device details
Trap forward settings
Notification settings (group, email, trap and syslog settings)
Notification customization changes
Event sets
User defined and customizable groups
JRM Jobs

OL-25957-01
7-9
Chapter 7
Events details
Fault History 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
Appliance.
Selective Backup
Events details
Fault History details
IPSLA Performance Management Data Migration Scope

IPSLA Performance Management in LMS 4.2 (known as IPM in earlier LMS versions), can be backed
up using either the Normal or the Selective mode.
Normal Backup
IPSLA databaseContains information about source devices, target devices, operations, collectors,
and the statistics of data collected.
The settings in ipm.env, ipm.properties, and, base.properties files
Historical and Custom Reports
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-10
OL-25957-01
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.
Settings in IPSLA properties.
Log Settings.
System Reports
Report Jobs and archives.
Exported data (Statistics and Collectors).
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.
CiscoView Data Migration Scope

The CiscoView (CV) data can be backed up using the Normal mode. When you upgrade to LMS 4.2, the
users device preferences are migrated. In LMS 4.2, CiscoView is available at Inventory > Tools >
CiscoView.
Device Performance Management Data Migration Scope

Device Performance Management in LMS 4.2 (known as HUM in earlier LMS versions) can be backed
up using either the Normal or the Selective mode. The following data gets migrated when you restore
LMS 3.2 SP1 (HUM) backup in LMS 4.2.
Normal Backup
Configuration Data
Threshold Violation Scripts
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
data from HUM 1.2.

OL-25957-01
7-11
Chapter 7
TrendWatch Violation data TrendWatch Violation data are migrated only when you restore
data from HUM 1.2 and LMS 4.2.
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
Poller Configurations along with the Polled data (Summarization data).
Template Configurations along with the newly loaded MIBs.
Threshold Configurations along with the Threshold Violation data.
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.
Job Information / Reports (system defined and user defined)

Suspended job instances will be moved to scheduled state.
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
7-12
OL-25957-01
Chapter 7

Selective Backup
Poller Configurations alone. Polled data (Summarization data) will not be migrated.
Template Configurations along with the newly loaded MIBs.
Threshold Configurations alone. Threshold Violation 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.
Job Information / Reports (system defined and user defined)

Periodic report jobs will be migrated. Suspended job instances will be moved to scheduled state.
Completed and Immediate report jobs will not be migrated.
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
Portal Data Migration Scope

The LMS Portal data can be backed up using the Normal mode. The LMS Portal configuration or settings
get migrated when you remote upgrade to LMS 4.1. All the private page customization in the earlier
LMS version (3.2 SP1) will be migrated after remote upgrade.

OL-25957-01
7-13
Chapter 7
CiscoWorks Assistant Data Migration Scope

CiscoWorks Assistant is not part of LMS 4.2.
Figure 7-1 shows the migration of data from LMS 2.6 to LM S 3.2.
Figure 7-1
Migrating Data from LMS 2.6 to LMS 3.2
LMS 2.6
CiscoWorks Common Services 3.0.5

Resource Manager Essentials 4.0.5
Campus Manager 4.0.6
Device Fault Manager 2.0.6
Internetwork Performance Monitor 2.6
CiscoView 6.1.5
CiscoWorks Common Services 3.3

Resource Manager Essentials 4.3
Campus Manager 5.2
Device Fault Manager 3.2
CiscoView 6.1.9
CiscoWorks LMS Portal 1.2
CiscoWorks Assistant 1.2
Health and Utilization Monitor 1.2
Operating System
Solaris 9, Solaris 10
274762
Operating System
LMS 3.2
Figure 7-2 shows the migration of data from LMS 2.6 SP1 to LMS 3.2
Figure 7-2
Migrating Data from 2.6 SP1 to 3.2
LMS 2.6 SP1

Resource Manager Essentials 4.0.6
Campus Manager 4.0.7
CiscoView 6.1.6
Integration Utility 1.6.1

Campus Manager 5.2
CiscoView 6.1.9
Operating System
274763
Operating System
Solaris 8, Solaris9
LMS 3.2
7-14
OL-25957-01
Chapter 7

Remote Migration From LMS 2.6 or 2.6 SP1

Note
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.
Note
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 3.2.
Figure 7-3
LMS 3.0
LMS 3.2

Campus Manager 5.0
CiscoView 6.1.6
Health and Utilization Monitor 1.0 (Add-on
and separately licensed)

Campus Manager 5.2
CiscoView 6.1.9
Operating System
274764
Operating System
Figure 7-4 shows the migration of data from LMS 3.0 December 2007 Update to LMS 3.2.

OL-25957-01
7-15
Chapter 7
Figure 7-4
Migrating Data from LMS 3.0 December 2007 Update to LMS 3.2
LMS 3.2
LMS 3.0 December 2007 Update

Campus Manager 5.0
Internetwork Performance Monitor 4.0.1
CiscoView 6.1.7
CiscoWorks LMS Portal 1.0.1
CiscoWorks Assistant 1.0.1
Integration Utility 1.7.1
Health and Utilization Monitor 1.0/1.0.2 (Add-on
and separately licensed)

Campus Manager 5.2
CiscoView 6.1.9
Operating System
274765
Operating System
Figure 7-5 shows the migration of data from LMS 3.1 to LMS 3.2.
Figure 7-5
LMS 3.2
LMS 3.1

Campus Manager 5.1
CiscoView 6.1.8
Health and Utilization Monitor 1.1/1.1.2

Campus Manager 5.2
CiscoView 6.1.9
Operating System
274766
Operating System
7-16
OL-25957-01
Chapter 7

This section explains how to migrate data from LMS 3.2 SP1, LMS 4.0.1 or LMS 4.1.
Migrating Data on Solaris
Migrating Data on Windows
Migrating Data on Soft Appliance
Migrating Data on Solaris

This section explains the procedure of Migrating Data on Solaris to a remote machine.
In this section, the machine that has LMS 3.2 SP1, LMS 4.0.1 or LMS 4.1 is referred to as Machine A
and the remote machine where you need to install LMS 4.2 and restore the data, is referred to as Machine
B.
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
Log in as root into Machine A.
Step 2
Back up LMS 3.2 SP1, LMS 4.0.1 or LMS 4.1 data.

To do normal backup using CLI, enter the following command:
NMSROOT/bin/perl NMSROOT/bin/backup.pl BKP
where BKP is the backup directory.
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 Syntax and Usage for Backup Script.
Step 3
Log in as root into Machine B.
Step 4
Install LMS 4.2.
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
Stop the daemon manager by entering:

Step 7
Restore the backed up data by entering:

NMSROOT/bin/perl NMSROOT/bin/restorebackup.pl -d BKP [-t temporary_directory]
NMSROOT/bin/perl NMSROOT/bin/restorebackup.pl -d /opt/BKP.
For more details, see Syntax and Usage for Restore Script.
See Notes for Remote Migration.

OL-25957-01
7-17
Chapter 7
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, seeSetting 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.
Migrating Data on Windows

To migrate LMS 3.2 SP1, LMS 4.0.1 and LMS 4.1 data to a remote machine:
Step 1
Log in as administrator into Machine A.
Step 2

To do this using CLI, enter the following command:
NMSROOT\bin\perl NMSROOT\bin\backup.pl BKP
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.
Step 3
Log in as administrator into Machine B.
Step 4
Install LMS 4.2.
Step 5
Copy the backup directory BKP that contains the LMS 3.2 SP1 data from Machine A to any temporary
location.
Step 6

net stop crmdmgtd
Step 7

NMSROOT\bin\perl NMSROOT\bin\restorebackup.pl -d BKP [-t temporary_directory]
7-18
OL-25957-01
Chapter 7

NMSROOT\bin\perl NMSROOT\bin\restorebackup.pl -d C:\BKP.
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.
net start crmdmgtd
You can follow the above procedure to perform same version data migration from Solaris to Solaris.
Migrating Data on Soft Appliance

You can perform cross-platform data migration only from Windows/Solaris to Soft Appliance.
Migrating Data from Solaris/Soft Appliance to Soft Appliance
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
Log in as root into Machine A, which is a Solaris/Soft Appliance server.
Step 2
Back up the data.

To do normal backup using CLI, enter the following command:
NMSROOT/bin/perl NMSROOT/bin/backup.pl BKP

OL-25957-01
7-19
Chapter 7
NMSROOT/bin/perl NMSROOT/bin/backup.pl /opt/BKP.
To do selective backup using CLI, seeSyntax and Usage for Backup Script.
Step 3
Log in as root into Machine B, which is a Soft Appliance server.
Step 4
Install LMS 4.2.
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

For more details, see .
Step 8
Note
Step 9
is migrated.
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
Log in as administrator into Machine A which is a windows server.
Step 2

To do this using CLI, enter the following command:
NMSROOT\bin\perl NMSROOT\bin\backup.pl BKP
7-20
OL-25957-01
Chapter 7

NMSROOT\bin\perl NMSROOT\bin\backup.pl C:\BKP.
Step 3
Log in as root into Machine B, which is a Soft Appliance server.
Step 4
Install LMS 4.2.
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
is migrated.
You can follow the above procedure to perform same version data migration from Windows to Soft
Appliance.

Guidelines for Fault Management Post-Upgrade Activities in LMS 4.2
Guidelines for Restoring Inventory, Config Timeout and Retry Settings
Guidelines for Common Services Post-Upgrade Activities
LMS 4.2 AAA Methods
Resetting the Login Module

OL-25957-01
7-21
Chapter 7
Guidelines for Fault Management Post-Upgrade Activities in LMS 4.2

This section contains the complete basic configuration steps for Configuring SNMP Trap Receiving and
Forwarding.
Configuring SNMP Trap Receiving and Forwarding

To upgrade all remote adapters, see Installing and Data Migration With CiscoWorks LAN Management
Solution 4.0. It is available at:
http://www.cisco.com/en/US/products/sw/cscowork/ps2425/prod_installation_guides_list.html
By default, LMS receives SNMP traps on port 162 (or, if port 162 is occupied, port 9000). If you need
to change the port:
Step 1
Select Admin > Network > Notification and Action Settings > Fault - SNMP trap receiving settings.
The configuration page for SNMP trap receiving is launched.
Step 2
Enter the port number in the Receiving Port entry box.
Step 3
Click Apply.
7-22
OL-25957-01
Chapter 7

If you want LMS to forward traps to a remote NMS:

Step 1
Select Admin > Network > Notification and Action Settings > Fault - SNMP trap forwarding.
The configuration page for SNMP trap forwarding is launched.
Step 2
Enter these for each host:
An IP address or DNS name for the hostname.
A port number on which the host can receive traps.
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
Guidelines for Restoring Inventory, Config Timeout and Retry Settings

To upgrade all remote adapters, see Installing and Data Migration With CiscoWorks LAN Management
Solution 4.0. It is available at:
http://www.cisco.com/en/US/products/sw/cscowork/ps2425/prod_installation_guides_list.html
When you do a back up restore from LMS 3.x/ LMS 4.x to LMS 4.2, the inventory, config timeout, and
retry values will not be restored by default. If you have to restore the values in LMS 4.2:
Step 1
Select Admin > Network > Timeout and Retry Settings.

The Inventory, Config timeout and retry settings page appears.
Step 2
Step 3
Note
Enter the required values for:
Read Delay
Transport Timeout
Login Timeout
Tune Sleep
Delay After Connect
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.

OL-25957-01
7-23
Chapter 7
Guidelines for Common Services Post-Upgrade Activities

This section contains the LMS Authorization, Authentication, and Accounting (AAA) methods.
LMS 4.2 AAA Methods

LMS 4.2 supports only one AAA mode; Local Authentication Mode.
Local Authentication Mode

LMS 4.2 server supports the following Login Modules in Local Authentication Mode mode:
Local Authentication
KerberosLogin
Local NT System (Windows only)
Local Unix System (Solaris only)
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-24
OL-25957-01
Chapter 7

Resetting the Login Module

You can run the following commands to reset the Login Module to Local authentication mode:
Step 1
Stop the LMS system by entering:

Step 2
Run the following script:

NMSROOT/bin/perl NMSROOT/bin/ResetLoginModule.pl
Step 3
Start the LMS system by entering:

On Windows:
Step 1
Stop the LMS system by entering:

net stop crmdmgtd
Step 2
Run the following script:

NMSROOT\bin\perl NMSROOT\bin\ResetLoginModule.pl
Step 3
Start the LMS system by entering:

net start crmdmgtd

OL-25957-01
7-25
Chapter 7
7-26
OL-25957-01
CH A P T E R

This chapter provides troubleshooting information for LMS installation and data migration. It contains:
Troubleshooting Errors in Data Migration

You can run a self test or view process failures from the Server.
To run a self test, select Admin > System > Server Monitoring > Selftest from the menu.
To view process failures, select Reports > System > Status > Process
Processes that are not running are displayed in red.
Run the collect server information to check the package errors, if any.

You can view the status of any process by selecting Admin > System > Server Monitoring > Processes
from the menu.
If you are trying to view and change process status:
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.

OL-25957-01
8-1
Chapter 8
To view or change the process status:

Step 1
Select Admin > System > Server Monitoring > Processes.

The Process Management page appears.
Step 2
You can stop and start the processes:
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:
To stop all processes from the server, enter:

net stop crmdmgtd
To start all processes from the server, enter:

net start crmdmgtd
For Solaris:
To stop all processes from the server, enter:

To start all processes from the server, enter:

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.

To recover the admin password in the virtual appliance:
Step 1
Login to the ESX server which contains LMS virtual appliance.
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
Select SCSI Controller 0 in the hardware tab.
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.
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
Select SCSI Controller 0 in the hardware tab.
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.

OL-25957-01
8-3
Chapter 8

You can contact the Cisco Technical Assistance Center (TAC) if you had problems while installing
Common Services.
Before contacting Cisco TAC, we recommend that you ensure:
The system hardware and software requirements are met.
The disk space is not full.
The DVD drive is not defective.
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

Table 8-1 shows error messages that might occur during installation and describes the reasons for the
errors.
Table 8-1
Installation Error Messages
Error Message
Possible Reasons
User Action
Cisco Prime LMS installation

You are not logged into
Log into Windows with local
cannot proceed because you are Windows with administrator administrator privileges and try
not logged in as an administrator. privileges.
installing again.
The setup program has
discovered HP OpenView
services running. This will lock
some of the Cisco Prime LMS
dlls.
HP Network Node Manager Stop all HP OpenView services and

(HPNNM) or NetView is
continue to install Cisco Prime LMS.
running on the same system.
Stop all HP OpenView services

before installing Cisco Prime
LMS.
Retry the download. If you still have
Decompression failed on file.
When you downloaded
errors, contact your technical support
The error was for error code per Cisco Prime LMS, a
CompressGet.
transmission error occurred representative.
or the installation medium is
damaged.
8-4
OL-25957-01
Chapter 8

Table 8-1
Installation Error Messages (continued)
Error Message
Possible Reasons
When you downloaded

Cisco Prime LMS, a
Please check your target location
transmission error might
and try again. Error number:
have occurred.
error code.
General file transmission error.
Severe: Cannot run the

dependency handler.
User Action
Retry the download. If you still have
errors, contact your technical support
representative.
When you have downloaded Retry the download.

Cisco Prime LMS, a
transmission error might
have occurred.
The directory structure of
installation is not
maintained. This can happen
if you download the zip file
and extract the contents to
install from it.
Cannot write infoFile

or
A file-write operation failed. Run the file system checking utility,

then repeat the installation.
Cannot create infoFile.
1.
Verify that you have write

permission to the destination
directory and windows TEMP
directory.
2.
Repeat the installation.
The environment variable %TEMP%

provides the location on TEMP
directory.
Cannot stop service
servicename.
UseDLL failed for dll.
The installation (or

reinstallation) tried to stop
the service servicename
unsuccessfully.
1.
Select Control Panel > Services

and stop service servicename
manually.
2.
Continue to install or uninstall.
dll should be available at any

time for any process, but
Windows did not load it.
Check permissions on the

system32 directory under
%WINDIR%. If the dll is
secure.dll or r_inst.dll, check
product installation media for
errors.
Or
function failed: DLL function
not found.
dll should be available at any

time for any process, but
Windows did not load it.
Reinstall Windows.
Check permissions on system32

directory under %WINDIR%. If
dll is secure.dll or r_inst.dll,
check product installation media
for errors.
Or
Reinstall Windows.

OL-25957-01
8-5
Chapter 8
Table 8-1
Error Message
Possible Reasons
OpenFile failed: pathname.
A file open operation failed.
User Action
Run the file system checking

utility, then repeat the
installation.
Or
Verify whether you have the read

permission on pathname, then
repeat the installation.
ProtectFile failed: file: error.

WWW admin security may be
incomplete.
Setting file permissions

failed because you may not
be allowed to change them.
Log in as administrator.
Launch of isql script failed.
The existing database file is Contact your technical support

representative.
corrupted or the previous
version of LMS 4.2 is
destroyed.
If you are installing on a FAT file

system, LMS 4.2 cannot provide file
security.
The problem may occur

during reinstallation.
The product should not be
installed in a root directory.
Select a directory other than the root

You tried to install the
directory to install the product.
product in a directory of a
drive (for example, c:\ or d:\)
that is not supported.
The product should not be

installed in a remote directory.
You tried to install the

product in a directory of a
drive that is remotely
mounted or using the UNC
pathname.
Select a directory on a local

hard-drive.
Remove all files from directory or

You tried to install in a
The selected directory is not
empty. Mixing new and existing directory that contains some choose another directory to install
the product.
files can cause severe problems files.
during installation.
The installer requires temporary There is not enough drive
space for temporary
workspace.
installation files.
You have less than 8 MB of free
space on drive. Free up some
space and try again.
You are attempting to install
LMS on a server that is
configured as a Primary Domain
Controller or a Backup Domain
Controller (PDC/BDC).
You are trying to install the

application on a server that
is configured as a Primary
Domain Controller or a
Backup Domain Controller
(PDC/BDC).
Make more drive space available

(%TEMP%), then rerun installation.
Install LMS on another server not

configured as PDC / BDC.
8-6
OL-25957-01
Chapter 8

Table 8-1
Error Message
Possible Reasons

LMS on an unsupported
operating system.

application on an operating
system that does not match
System Requirements for
the product.
The installation will exit when

you close this message.
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.
Upgrade the Operating System

on the Server to a supported
version
Or

application on an operating
system that does not match
System Requirements for
Please run installation again on a
the product
supported platform. Do you want
to proceed?

Cisco Prime LMS on operating
system and service pack.
User Action
Install LMS on another server

running a supported Operating
System.
Run installation again on a supported

platform.
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.
Do you want to proceed?

Click Yes to proceed with this
installation.
Click No to exit installation.
The installation image is being
accessed as
\\servername\sharename.
Installation can run only from a
local or mapped drive.
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.
We recommend that you run the

installation from a local CD or a
local hard drive to avoid errors
that may result from the network
being slow or busy.
Click OK to exit installation.

OL-25957-01
8-7
Chapter 8
Table 8-1
Error Message
Possible Reasons
The default (or selected) drive

drive has a(n) file-system-type
file system.
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 system.
This file system does not support

file security. The cluster size is
cluster size bytes, therefore disk
space requirements can be high.
The file system may not

support security. The cluster
size may be bigger than
4096 bytes.
Choose another directory to

install LMS
Use default or selected

directory to install LMS
The product can be installed only

in a folder that does not have
spaces in its name or can be
converted into 8.3 form. Select
another destination folder.
Cannot determine the local

Administrators group.
Cannot determine the local

Everyone group.
Installation cannot create the

default directory, directory
name.
The destination directory

contains spaces in the
directory name and the
directory name cannot be
converted to a MS-DOS
format.
User Action
Install the product in a directory

whose fully qualified pathname
does not contain any spaces or
has MS-DOS name aliases.
Or
Check the presence of MS-DOS

aliases, using dir /x command in
a command-line window.
The installation program

cannot find one of the
built-in Windows user
groups. This prohibits
LMS 4.2 security setup.
1.
Check the Operating System.
2.
Reinstall Windows if necessary,
3.
Rerun LMS 4.2 installation.

cannot find one of the
built-in Windows user
groups. This prohibits the
setup of LMS 4.2 security.
1.
Check the Operating System.
2.
Reinstall Windows if necessary,
3.
Rerun LMS 4.2 installation.
You may not have

permissions on the
directory.
Select another destination directory.
You may not have permissions

on the default directory or you
have specified a read-only
device.
8-8
OL-25957-01
Chapter 8

Table 8-1
Error Message
Possible Reasons
Could not set file permissions.

cannot set file permissions.
Most likely causes are:
User Action
1.
Correct the problem.
2.
Rerun installation program.
task_name is already running!

One installation subtask is
Wait for it to complete and click still running.
OK.
1.
Wait for installation subtask to

finish running.
2.
Click OK to proceed.
Cannot create/open log file.
1.
Determine why the file could not

be created or opened.
2.
Correct the problem, then rerun

installation.
The account you used to

log in to the system has
insufficient
permissions.
The drive on which you

are installing product
has a FAT file system.

could not create or open the
installation log file.
Common causes are lack of disk

space or write protection on file.
Error creating / modifying
casuser - name.
This error may occur if:
Click Yes if you want to try

again.
Click No if you want the Install
to terminate.
The passwords that you

entered do not match the
policies set by System
Administrators.
3.
Rerun installation.
If you are not authorized to

create users on the system,
contact your System
Administrator.
If you are authorized to create

users on the system:
a.
Click Yes.
Or
User running the

installation does not
have permission to
create new user on the
system.
A screen appears where you can

re-enter the passwords.
b.
Correct the problem as given in

the error message.
Cannot find script to upgrade

database.
Problem with database

upgrade.
Contact your technical support

representative.
Database upgrade failed.

upgrade.

representative.
Database upgrade result

unknown.

upgrade.

representative.
The installer has discovered HP HP OpenView services are

OpenView services running. The running.
installation might take
significantly longer to complete
with these services running.
Stop all HP OpenView services

before installing LMS 4.2.
You do not have to restart the system
after stopping HP OpenView.

OL-25957-01
8-9
Chapter 8
Table 8-1
Error Message
Possible Reasons
ODBC Driver Manager 3.510 or Cisco Prime LMS software

later is required by LMS 4.2.
requires ODBC Driver
Install ODBC 3.510 first.
Manager version 3.510 or
later.
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.
Name lookup failed for

hostName. Please configure the
hostname and and then try
installation.
Your hostname is not

configured properly.
Some of the executables and

These files are currently being
used by another running process. DLLs installed by Cisco
Prime LMS are locked.
You must stop all processes
listed below to proceed
successfully with this
installation.
Configure the hostname and continue

installation.
1.
Stop LMS 4.2.
2.
Close Browsers and make sure

Cisco Prime LMS CLIs are not
used at the moment.
After stopping all the
applications, proceed with the
installation.
Click Next to proceed with the

installation.
Click Cancel to exit.
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.
Try to run command net start

from MSDOS window.
The output should not show any
LMS 4.2 daemon manager
running.
5.
Run the installation again.
8-10
OL-25957-01
Chapter 8

Table 8-1
Error Message
Possible Reasons
User Action
The instruction at location

referenced memory at location.
The memory cannot be read.
You have installed Cisco

Prime LMS Common
Services on a Pentium IV
machine.
Click OK, and ignore the message.

The installation will continue
normally.
Click OK to terminate the

program.
Click Cancel to debug the
program.
java.exe has generated errors and
will be closed by Windows. You
must restart the program. An
error log is being created.
This message appears when Click OK, and ignore the message.
The installation will continue
you install Cisco Prime
LMS Common Services on a normally.
Pentium IV machine.
CreateService - service name The specified service is marked

for deletion.
The registry entries related

to the service are not deleted
during the uninstallation.
1.
Restart the machine
2.
Reinstall LMS 4.2.
If the problem still exists:
One instance of Cisco Prime

LMS Installation is already
running.
Cisco Prime LMS

installation is already
running.
If you are sure that no other

instances are running, remove
the file C\:CMFLOCK.TXT. The
Installation will now terminate.
Backup operation failed.
1.
Uninstall LMS 4.2
2.
Restart the machine,
3.
Start a fresh installation.
Remove the file C:\CMFLOCK.TXT

and retry the installation.
Parallel installations are not
supported.
Make sure that no other instance of
installation is running, while you a
start a new installation.
The backup process failed.
Retry backing up again.
Please look at backup

directory\backup.log for the
reason for failure.
Click Retry to take backup
again.
Click Exit to exit the
installation.
Dependency handler error occurs Cisco Security Agent is
and installation quits
enabled.
Disable the Cisco Security Agent and

then start the install.

OL-25957-01
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
This could be due to the

cmgshieldui.exe. This
blocks the setup.exe /
process to get registered
as a service or to reload
itself in the memory.
This issue could be

reproduced if some
other antivirus
programs are running in
the memory.
User Action
To work around this issue, kill

the cmgshieldUI.exe from the
task manager/ process explorer.
Care must be taken not to kill the
cmgshield svc.exe, as this will
reboot the machine
automatically.
Disable the antivirus.
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"
User should be logged

into the server as the
local administrator (not
the domain admin)
when doing the install.
Login with the administrator

mode.
Change the temp directory path.
Append the following path for 64

bit OS, before starting the install
or try reinstalling the product.
Temp directory is
having long path or is
not proper.
The issue occurs when the

DB values are not getting
system32 is not in the path
registered and throw the
variable.
ERROR:
[IsDaemonManagerOff] cannot
execute
C:\PROGRA~1\CSCOpx\bin\pd
show.cmd
C:\Windows\SysWOW64\wbem
;C:\Windows\SysWOW64;C:\W
INDOWS\system32;C:\WINDO
WS;C:\WINDOWS\System32\
Wbem;
Append the following path for 32

bit OS
"c:\windows;c:\windows\sytem3
2;c:\windows\system32\wbem"
8-12
OL-25957-01
Chapter 8

Table 8-1
Error Message
Possible Reasons
User Action
Install error while configuring

tomcat
Error "OpenService: The

specified service does not
exists as an installed
service" while tomcat
configuration during install
Check if DEP is enabled in the server.

You can check the same here.
Right Click on My Computer and go
to Properties > Advanced > Click the
"Settings" button in the Performance
frame > Data Execution Prevention.
If it is enabled for all the programs
then disable it and try installing
Cisco Prime LMS again.
Error in validating a package in

Solaris install
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
During fresh install, the

installation aborts.
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.
Configure the machine swap

space as 8GB and reboot the
server.
Else go to the following registry

location and change the
ps_syscheck value as 0.
HKEY_LOCAL_MACHINE\S
OFTWARE\Cisco\Resource
Manager\CurrentVersion\Enviro
nment
Daemon Manager down and

process are not up.
The Daemon Manager port

42340 may be occupied by
some other third party
application.
Check the port state by "nestat -na |

grep 42340" command. Please free
the port and restart the Daemon
Manager.
Installation fails in Solaris.
Stale process might be

running in the memory.
Check the stale process by "ps -ef |

grep CSCO" command. And kill it
manually by using the kill -9 pid
then start the install.

OL-25957-01
8-13
Chapter 8
Table 8-1
Error Message
Possible Reasons
User Action
Scheduled periodic backup is

active even after Uninstall the
build in both Solaris and
Windows.
When machine performance

is very slow. Then the OS
itself will quit the Perl
command and the files will
not get remove from task
scheduler.
Run the following command from the

command prompt Once the
performance up.
For Windows:
Logrot:
C:/PROGRA~1/CSCOpx\bin\perl
C:\PROGRA~1\CSCOpx\objects\log
rot\schedulelogrot.pl C:\ 0 0 cancel
Backup:
C:/PROGRA~1/CSCOpx\bin\perl
C:/PROGRA~1/CSCOpx\cgi-bin\db
admin\pdbadmin\schedulebackup.pl
C:/ 0 0 cancel
For Solaris:
logrot schedule will be part of
crontab after uninstallation and it
will not cause any issues. Anyway
during installation auto logrot
schedule will update the schedule
Task. No issues in it.
Backed up license count

would be mismatched with
the current license count
installed in the restore
server.
Need to apply the new license with

higher count once the restore is done.
Backed up LMS license

If the number of managed
count is greater than 5000.
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
You can setup LMS in another server

to enable all the other functions for
the additional devices or Select
Admin > System > Device
Management Functions, from the
LMS menu, to disable the other
functions.
WARNING: Your current license

count is lower than your earlier
license count. If you restore the
data now, devices that exceed the
current license count will be
moved to Suspended state.
8-14
OL-25957-01
Chapter 8


This chapter describes the errors that you might encounter during data migration and guidelines on
troubleshooting those errors.
Common Services Data Migration Errors
Inventory, Config and Image Management Data Migration Errors
Fault Management Data Migration Errors
IPSLA Performance Management Data Migration Errors
Device Performance Management 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
Stop the LMS system by entering,
On Solaris
On Windows
net stop crmdmgtd
Step 2
Run the following commands:
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 action=uninstall dsn=dsn_name
rm -fr
NMSROOT/tempBackupData

OL-25957-01
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 action=uninstall dsn=dsn_name
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
Start the LMS system by entering,
On Solaris
On Windows
net start crmdmgtd
8-16
OL-25957-01
Chapter 8

Common Services Data Migration Errors

If you encounter errors during CS data migration, you can use the following options to troubleshoot the
problems:
CAM (Core Admin Module) debugging:

You can enable CAM debugging by entering:
NMSROOT/MDC/bin/ccraccess -updateLog Core cam DEBUG
You can disable CAM debugging by entering:
NMSROOT/MDC/bin/ccraccess -updateLog Core cam WARN
Daemon Manager restart is necessary.
CAM debug details:

CAM debug details are logged at:
NMSROOT/MDC/log/core-MM-DD-YYYY.log
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.

OL-25957-01
8-17
Chapter 8
Inventory, Config and Image Management Data Migration Errors

If you encounter errors during Inventory, Config and Image Management data migration, do the
following:
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
Minimum JVM heap size
128
VM_MAX_HEAP
Maximum JVM heap size
512
RETRIES
Number of retries for starting the

daemon
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 dsn=rmeng dmprefix=RME opt=Y

Windows:
NMSROOT\bin\perl NMSROOT\bin\dbRestoreOrig.pl dsn=rmeng dmprefix=RME opt=Y
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

If you encounter errors during Network Topology, Layer 2 Services and User Tracking data migration:
Check for the migration logs. The relevant logs are:

Solaris:
/opt/CSCOpx/bgupgrade/CmfUpgrade.log (In case of Upgrade)
Windows:
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

OL-25957-01
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
Check the Database files at the following directory:

Windows:
NMSROOT\databases\ani\ani.db
Solaris:
NMSROOT/databases/ani/ani.db
8-20
OL-25957-01
Chapter 8

Fault Management Data Migration Errors

If you encounter errors during Fault Management data migration:
Check logs. The relevant log files are:

Solaris:
Windows:
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
These files are located at:

Solaris:
NMSROOT/databases/dfmEpm/dfmEpm.db
NMSROOT/databases/dfmInv/dfmInv.db
NMSROOT/databases/dfmFh/dfmFh.db

OL-25957-01
8-21
Chapter 8
Windows:
NMSROOT\databases\dfmEpm\dfmEpm.db
NMSROOT\databases\dfmInv\dfmInv.db
NMSROOT\databases\dfmFh\dfmFh.db
IPSLA Performance Management Data Migration Errors

If you encounter errors during IPSLA Performance Management data migration, please check the
following logs:
restorebackup.log
migration.log
ipmclient.log
ipmserver.log
ipm_base.log
The logs are available at:
Solaris
/var/adm/CSCOpx/log
Windows
NMSROOT\log
You may also encounter the following types of errors while migrating IPSLA Performance Management
data:
If Custom operations are not migrated properly, check whether:

ipm2.x backedup DB contains custom operations.
Predefined or custom SNA Operations are migrated.
Alerts of NMVT type are changed to none.
Alerts of NMVT and SNMP trap are changed to 'snmp trap'.
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.
If Collectors are not moved into running state, check whether:

Devices are SNMP reachable from LMS 3.2.
There is sufficient memory in the router to configure probes. If not, remove some probes on the
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

The following folders must be present in filebackup.tar:

Windows: Jobs folder in NMSROOT/files/ipm/jobs and System Reports in
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
Device Performance Management Data Migration Errors

If you encounter errors during Device Performance Management data migration, please check the
following logs:
restorebackup.log
upm_process.log
The logs are available at:
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.

OL-25957-01
8-23
Chapter 8

This section provides Frequently Asked Questions (FAQs) on LMS 4.2 Installation and Data Migration
and the respective solutions.
This section lists the FAQs:
How do I set or change the shell password?
How do I transfer files to or from the LMS Soft Appliance?
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?
On which operating system is LMS 4.2 supported?
Which Windows HotFix patches are supported for LMS 4.2?
Is LMS 4.2 supported on 64-bit native systems?
Can I install LMS 4.2 with Internet Information Services (IIS) enabled?
Which TCP and UDP ports does LMS 4.2 use?
Does LMS 4.2 support virtual machines, such as VMware and VirtualPC?
Can I install LMS 4.2 with Windows Domain Controller enabled?
Is LMS 4.2 supported on Solaris x86 (on the x86 CPU)?
Is LMS 4.2 supported on multi-homed server?
Can I migrate data from Solaris to Windows and vice versa?
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)?
Q. How do I set or change the shell password?

A. To set or change the shell password, perform the following steps:
Step 1
Log in as a sysadmin user.
Step 2
Enter the command shell_enable.
Step 3
Enter a password.
Step 4
Retype the password to confirm.

To access the shell mode, enter the command shell and enter the password.
8-24
OL-25957-01
Chapter 8

Note
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.
Q. How do I transfer files to or from the LMS Soft Appliance?
A. 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.

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
/var/tmp/Cisco_Prime_install_YYYYMMDD_hhmmss.log and /var/log/ade/ADE.log (CARS and

Soft Appliance).
On Windows, if errors occur during installation, check the installation log in the system directory
on the drive where the operating system is installed. Each installation creates a new log file. For
example, the LMS installation creates
SystemDrive:\Cisco_Prime_install_YYYYMMDD_hhmmss.log.
Q. I have LMS 3.2 applications installed on different servers. Can I migrate data from these multiple
servers to one LMS 4.2 server?

A. No, this option is not supported.
Q. 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?
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
data from the backup.

Q. On which operating system is LMS 4.2 supported?
A. See System and Browser Requirements for Server and Client for details.
Q. Which Windows HotFix patches are supported for LMS 4.2?
A. For LMS 4.2, we have tested all the Windows HotFix patches released up to July 2010 that have an
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.

OL-25957-01
8-25
Chapter 8
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.
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
need to get a new license for LMS 4.2 on Windows?

A. No, you can use the same LMS 4.2 Solaris license on Windows.
8-26
OL-25957-01
Chapter 8

Q. When should I install other Network Management Systems (such as HP OpenView Network Node
Manager, Netview)?
A. You must install other Network Management Systems before installing Cisco Prime LMS 4.2. See
Supported Network Management Systems for more information.

OL-25957-01
8-27
Chapter 8
8-28
OL-25957-01
A P P E N D I X

This appendix provides information on the user inputs during LMS 4.2 installation.
Note
For information on the Installation of LMS 4.2, see Performing Installation of Cisco Prime LMS 4.2.
This appendix contains:
User Inputs for LMS Installation
Password Information

User Inputs for New Installation
User Inputs for Reinstallation
User Inputs for New Installation

Enter the following information while installing for the first time:
Table A-1
User Inputs for a New Installation
Settings
Value
Destination folder
The default location is System drive:\Program Files\CSCOpx.

Select another location if you want to install in a specific location.
We recommend that you specify a short path for the destination folder.
Login Password
(Mandatory)
No default values. Enter the login password. For more information on

passwords, see Password Information.
Database Password
No default values. You can use login password as database password or a

random system generated password is provided.

OL-25957-01
A-1
Appendix A
Important Note for Configuring Port Numbers
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.

Enter the following information during an upgrade installation in Custom mode:
Table A-2
User Inputs for an Upgrade Installation: Custom
Settings
Value
Backup folder
Enter a folder for the backup data. You can also browse and select a folder.
Password for users

admin and guest
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
Password for system No default values.

identity account
Enter the System Identity Account password. For more information on
(Mandatory)
passwords, see Password Information.
If you are upgrading from LMS 2.6 and LMS 2.6.1, you can either retain the
existing password or enter a new password.
Password for the user 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.
casuser
(Optional)
However, this is not applicable for Solaris.
Password for the

Common Services
Database (Optional)
Leave the fields blank to use the existing password.
A-2
OL-25957-01
Appendix A

Table A-2
User Inputs for an Upgrade Installation: Custom (continued)
Settings
Value
Web server settings:
You can choose to keep the existing information.
HTTPS port
Administrators
e-mail address
SMTP server
name
(Optional)
Data for the
Self-signed
Certificate:
You may change the Self-signed Certificate information. By default, the

installation program uses the existing Self-Signed Certificate information.
(Mandatory)
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.
Enter the following information while reinstalling:

Table A-3
Settings
Value
Backup folder
Enter a folder for the backup data. You can also browse and select a folder.
Destination folder
The default location is System drive:\Program Files\CSCOpx.

We recommend that you specify a short path for the destination folder.
Login and Database

Passwords
You may change the login and database passwords. To keep the existing
passwords, leave the fields blank.
LMS Login and Database Passwords
Changing LMS Admin Password
Changing casuser Password

OL-25957-01
A-3
Appendix A

While entering LMS Login and Database passwords:
Use a minimum of five characters and a maximum of 15 characters.
Do not start the password with a number.
Do not insert spaces between characters.
Do not use any special characters.
Changing LMS Admin Password

You can change your LMS Admin password by using either the LMS user password recovery utility or
from the GUI, if you want to change it.
Changing Admin Password Using Password Recovery Utility
Changing Admin Password From GUI
Changing Admin Password Using Password Recovery Utility

You can change the LMS user password using the LMS user password recovery utility.
To change the user password on Solaris:
Step 1
Set the LD_LIBRARY_PATH manually. The path is to be set as follows:

setenv LD_LIBRARY_PATH /opt/CSCOpx/MDC/lib:/opt/CSCOpx/lib
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
Enter NMSROOT/bin/ResetPasswd.pl username at the command prompt.

Here NMSROOT refers to the LMS Installation directory.
A message appears:
Enter new password for username:
Step 3
To change the user password on Windows:

Step 1
Enter NMSROOT\bin\ResetPasswd.pl username at the command prompt.

A message appears:
Step 2
To change the user password on Soft Appliance:

Step 1
Enter NMSROOT/bin/ResetPasswd.pl username at the command prompt.
A-4
OL-25957-01
Appendix A

Here NMSROOT refers to the LMS Installation directory.

A message appears:
Step 2

OL-25957-01
A-5
Appendix A
Changing Admin Password From GUI

To change the LMS admin password from the LMS server:
Step 1
Login as admin user.
Step 2
Select Admin > System > User Management > Local User Setup.
The Local User Setup page appears.
Step 3
Click Modify My Profile.

The My Profile pop-up window appears.
Step 4
Enter the password in the Password field.
Step 5
Re-enter the password in the Verify field.
Step 6
Enter the e-mail ID in the E-mail field.
Step 7
Click OK.
Changing casuser Password

You can change the casuser password using resetCasuser.exe.
To change the casuser password, do the following:
Step 1
At the command prompt, enter:

NMSROOT\setup\support\resetCasuser.exe
Three options are displayed:
Step 2
1.
Randomly generate the password
2.
Enter the password
3.
Exit.
Enter 2, and press Enter.

A message appears, prompting you to enter the password.
Step 3
Confirm the password.

You must know the password policy. If you enter a password that does not match the password policy,
the application exits with an error message.
A-6
OL-25957-01
Appendix A


To install VMware tools in a LMS Virtual Appliance:
Step 1
Ensure that your LMS Virtual Appliance is powered on.
Step 2
Right click on the LMS Virtual Appliance VM, then select Guest > Install/Upgrade VMware Tools
and click OK.
Step 3
Enable the root shell.
Step 4
Create a mount point.

mkdir /mnt/cdrom
Step 5
Mount the CDROM.

mount /dev/cdrom /mnt/cdrom
Step 6
Copy the VMware tools tar ball to a local temporary location.

cp /mnt/cdrom/VMwareTools-<version>.tar.gz /tmp/
where <version> is the VMware tools package version.

Step 7
Go to tmp directory and extract the tar file.

cd /tmp
tar -zxvf VMwareTools-<version>.tar.gz
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
Follow the screen prompts to install the VMware Tools.

Options in square brackets are default choices and can be selected by pressing Enter.
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.
Unmount the CDROM.

umount /mnt/cdrom

OL-25957-01
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
Remove VMware tools installation packages.

cd /tmp
rm /tmp/VMwareTools-<version>.tar.gz
rm -rf /tmp/vmware-tools-distrib
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.
Allows you to shutdown/reboot the guest cleanly.
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.
Better time synchronization between the guest and host.
A-8
OL-25957-01
A P P E N D I X

CiscoWorks User Tracking Utility is a Windows desktop utility that provides quick access to useful
information about users or hosts discovered by LMS.
UTU comprises a server-side component and a client utility.
To use UTU, LMS must be installed and functioning on your machine, and accessible through the
network.
Understanding UTU
Downloading UTU 2.0
Installing UTU 2.0
Accessing UTU 2.0
Configuring UTU 2.0

OL-25957-01
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.

Table B-1 lists the minimum system requirements for UTU.
Table B-1
System Requirements for UTU
Requirement Type Minimum Requirements

System hardware
System software
Memory (RAM)
Additional
required software
IBM PC-compatible computer with Intel Pentium processor.
Windows 2008
Windows XP with SP2 or SP3
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)
Microsoft .Net Runtime 3.5 Service Pack 1

You can download Microsoft .Net Runtime 3.5 Service Pack 1 from
http://www.microsoft.com
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

Downloading UTU 2.0
Downloading UTU 2.0

UTU requires CiscoWorksUserTrackingUtility2.0.exe file to be downloaded and installed.
To download UTU 2.0:
Step 1
Go to the Cisco Download Software page

http://www.cisco.com/cisco/software/release.html?mdfid=282641773&flowid=5141&softwareid=2807
75110&release=2.0.0&relind=AVAILABLE&rellifecycle=&reltype=latest.
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
Select a product release version from the Latest Releases folder and locate the software update to
download.
Step 3
Locate the file CiscoWorksUserTrackingUtility2.0.zip

This zip file contains CiscoWorksUserTrackingUtility2.0.exe and setup.iss file (required for silent
installation).
Step 4
Click the Download Now button to download and save the device package file to any local directory on
Server.
Step 5
Extract the file using any file extractor such as WinZip.
Installing UTU 2.0

You can install UTU 2.0 either in normal installation mode or silent installation mode.
Before you install UTU 2.0, check whether you system meets the requirements mentioned in Hardware
and Software Requirements for UTU 2.0.
Installing UTU 2.0 in Silent Mode
Installing UTU 2.0 in Normal Mode

OL-25957-01
B-3
Appendix B
Installing UTU 2.0
Installing UTU 2.0 in Silent Mode

To install UTU in silent mode, run the following command at the command prompt:
exe-location\CiscoWorksUserTrackingUtility2.0.exe a s f1file-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
Editing Setup.iss File
UTU is installed in the C:\Program Files\CSCOutu2.0 directory, by default.

If you want to install UTU in some other directory, you must edit the content of the setup.iss file. Change
the value of the szDir attribute in the setup.iss file.
For example, if you want to set the installation directory as D:\utu20, change
szDir=C:\Program Files\CSCOutu2.0 to szDir=D:\utu20 in the setup.iss file.
Setup.log File
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.
Installing UTU 2.0 in Normal Mode

To install UTU in normal installation mode:
Step 1
Log into the system with local system administrator privileges.
Step 2
Navigate to the directory that contains CiscoWorksUserTrackingUtility2.0.exe.
Step 3
Double-click CiscoWorksUserTrackingUtility2.0.exe to begin installation.

The User Tracking Utility Welcome screen appears.
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

Accessing UTU 2.0
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
Click Next to install UTU in the default directory.

or
a.
Click Browse to choose a different directory and click OK.
b.
Click Next to continue with the installation.
The installation continues.

Step 8
Click Finish to complete the installation.

User Tracking Utility is installed at the destination location you specified and a shortcut to UTU is
created on the desktop. To access the utility, see Accessing UTU 2.0.
Accessing UTU 2.0

To access UTU, click either:
Start > Programs > CiscoWorks UTU 2.0 > CiscoWorks User Tracking Utility 2.0
Or
UTU 2.0 shortcut available on the desktop
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.

OL-25957-01
B-5
Appendix B
Configuring UTU 2.0
Figure B-1
User Tracking Utility - Search Band
1 - Settings Icon
2 - Minimize icon
3 - Close icon
4 - UTU task bar icon
After a system restart and during the startup, the system launches the UTU automatically.
Configuring UTU 2.0

You must configure UTU to set the Campus Manager (for releases earlier than LMS 4.0), or LMS 4.2
server configurations.
To configure UTU:
Step 1
Click the Settings icon.

Or
a.
Right-click the UTU search band.

A popup menu appears.
b.
Click Settings.
The CiscoWorks Server Settings dialog box appears.

Step 2
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
Enter the port number of the LMS server.

The default HTTP port number is 1741.
You can modify the port number if required.
Step 4
Click Enable SSL for communicating with an SSL enabled server.

The port is changed to 443, which is the default port for SSL. See Figure B-2.
You can modify the port number if required.
B-6
OL-25957-01
Appendix B

Configuring UTU 2.0
Figure B-2
Enabling SSL
You can modify the port number if required. See Figure B-2.
Figure B-3
Step 5
Enabling SSL
Enter a valid CiscoWorks Server user name and password.

This is used to verify the validity of the user when searching for users, hosts, or IP Phones.
Step 6
Confirm the password by re-entering it.
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
Click Apply to save the changes.

OL-25957-01
B-7
Appendix B

You can use UTU Search Band to search for the users, hosts, or IP Phones in your network.
Note
UTU search is case-insensitive.

To search for users, hosts, or IP Phones:
Step 1
Right-click the UTU search band.

A popup menu appears with the default search criterion Host name/IP Address selected.
Step 2
Select a search criterion from the popup menu.

You can search using:
User name
Host name or IP Address
Device name or IP Address
MAC Address
Phone number
The default search criterion is host name or IP Address of the host.

The selected criterion is set for future searches until you change the criterion.
Step 3
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
Click Details to view the certificate details.

You can verify the authenticity and correctness of the SSL server here. See Figure B-5.

OL-25957-01
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 Band displaying the number of matching records
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
Select an entry in the Results window.

UTU displays the search results, which is a list of user names, host names, IP Addresses, or MAC
Addresses, in a Results window.
The Results window has the following options:
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.
Close, which you can use to close the window.
For a selected search result record, the Results window displays the details as described in:
Table B-2 for all search criteria except Phone Number
Table B-3 for search based on Phone Number
See Figure B-7 for IP Phone search results window.

Table B-2
Details for Each Entry in Results Window For a User or Host Search
Entry
Description
User Name
Name of the user logged in to the host.
MAC Address
Media Access Control (MAC) address of network interface card in

end-user node.
Host IP Address
IP Address of the host.
Host Name
Name of the host discovered by User Tracking.
Subnet
Subnet to which the host belongs.
Subnet Mask
Subnet mask of the host
Device name
Name of the switch.
Device IP Address
IP Address of the switch
VLAN
VLAN to which the port of the switch belongs.
Port
Port number to which the host is connected.
Port Description
Description of the port number to which the host is connected.
Port State
State of the port: Static or Dynamic.
Port Speed
Bandwidth of the port of the switch.

OL-25957-01
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
Port Duplex configuration details on the device.
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
Media Access Control (MAC) address of network interface card on the

phone.
Phone IP Address
IP Address of the phone.
CCM Address
IP Address of the Cisco Call Manager
Status
Status of the phone, as known to Cisco Call Manager
Phone Type
Model of the phone. Can be SP30, SP30+, 12S, 12SP, 12SPplus, 30SPplus,
30VIP, SoftPhone, or unknown.
Phone Description
Description of the phone.
Device Name
Name corresponding to IP Address of device.
Device IP Address
IP Address of the device
Port
Port number to which the phone is connected.
Port Description
Description of the port to which the phone is connected.
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
IP Phone Number Search Results Window
The search results for the value you enter in the search field depends on the default search
criteria.

UTU searches for the users, hosts, or IP Phones which match the search criterion. See Searching for
Users, Hosts or IP Phones for more information.
You can search for users, hosts, or IP Phones by entering a search pattern or substring of a search pattern.
For example, entering Cisco displays host names that start with, end with or contain Cisco for a search
on host names.
You do not have to use wildcard character * to match a pattern or substring of the pattern.
To search for a MAC Address, you can use one of the following MAC Address patterns or a substring of
these patterns:
xxxx.xxxx.xxxx
xx:xx:xx:xx:xx:xx
xxxxxxxxxxxx
xx-xx-xx-xx-xx-xx
Here x denotes an hexadecimal number.

OL-25957-01
B-13
Appendix B

Ensure that UTU is not running while uninstalling.
If you try to uninstall UTU when it is running, an error message appears and uninstallation terminates.
To uninstall UTU:
Step 1
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
Click Finish to exit the uninstallation wizard.

You can install UTU 2.0 on the same system where UTU 1.1.1 is installed.
You can choose to install UTU 2.0 on any directory other than the directory where UTU 1.1.1 is installed.
See Installing UTU 2.0 for installation instructions.

Re-installation of UTU 2.0 is supported on the normal mode of installation.
In the normal mode of installation, you are prompted with a confirmation message whether you want to
continue the installation. You must provide your inputs to continue the installation.
See Installing UTU 2.0 for installation instructions.
The user profiles that are created already are not be lost during re-installation.
B-14
OL-25957-01
A P P E N D I X

This appendix provides general information on how to install the Remote Syslog Collector on a remote
Windows or UNIX system to process syslog messages.
The Remote Syslog Collector filters the Syslog messages before forwarding them to the Analyzer
process on the LMS server.
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:
/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\
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.

OL-25957-01
C-1
Appendix C
This section describes how to set up Syslog between RSAC and LMS 4.2. This involves:
Stopping the Remote Syslog Collector
Uninstalling the Remote Syslog Collector

The following section lists the necessary server requirements for Remote Syslog Collector:
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.
Remote Syslog Collector Server Minimum Requirements on Solaris
Requirement Type
Minimum Requirements
Hardware
UltraSPARC CPU
Memory (RAM)
4 GB RAM and 8 GB Swap space.
Operating System
Solaris 10
Browser
(You need a browser only if you download

the RSAC installation files from the
LMS 4.2 server.)
Internet Explorer 8.0 and 9.0 Standards Mode (Press F12 and select
Standards Mode)
Table C-2
Remote Syslog Collector Server Minimum Requirements on Windows
Requirement Type
Hardware
IBM PC-compatible system with 1 GHz or faster Pentium processor, and

1 GB memory.
Memory (RAM)
2 GB RAM memory requirement with a Swap space of 4 GB.
Operating System
Windows 2008 Server Standard Edition (SP1 and SP2)
Windows 2008 Server Enterprise Edition (SP1 and SP2)
Windows 2008 Standard Edition R2 (SP2)
Windows 2008 Enterprise Edition R2 (SP2)
Browser
(You need a browser only if you download the

Remote Syslog Collector installation files
from the LMS 4.2 server.)
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
Remote Syslog Collector Server Minimum Requirements on Soft Appliance
Requirement Type
Virtualization Systems
VMWare ESXi server 4.1
Memory (RAM)
4 GB RAM memory requirement with a Swap space of 8GB.
Hard disk space
80 GB
Operating System
Windows 2008 Server Standard Edition (SP1 and SP2)
Windows 2008 Server Enterprise Edition (SP1 and SP2)
Windows 2008 Standard Edition R2 (SP2)
Windows 2008 Enterprise Edition R2 (SP2)
Browser
(You need a browser only if you download the

Remote Syslog Collector installation files
from the LMS 4.2 server.)
Internet Explorer 8.0, and 9.0 Standards Mode (Press F12 and select
Standards Mode)
Firefox 8.0, and 9.0 for Windows

Only 32-bit IE and FF browsers are supported
Note
The following Virtualization systems are supported:
VMware ESX server 3.0.x
VMware ESX Server 3.5.x
VMWare ESX 4.0.x
VMWare ESX 4.1, 4.1, and 5.0
VMWare ESXi 4.0, 4.1, and 5.0
Hyper V Virtualization
RSAC 5.2 works only with LMS 4.2.

You must uninstall the previous version of RSAC before installing the new RSAC which is provided with
LMS 4.2 DVD. To install RSAC 5.2, see Installing the Remote Syslog Collector.

OL-25957-01
C-3
Appendix C

Perform the following to install the Remote Syslog Collector on both platforms.
Installing on Solaris
Installing on Windows
Installing on Soft Appliance
Prerequisites for installing a Remote Syslog Collector:
LMS 4.2 and RSAC 5.2 should be installed.
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).
This section also contains:
Subscribing to a Remote Syslog Collector
Starting the Remote Syslog Collector
Installing on Solaris
To install the Remote Syslog Collector on a Solaris system:
Step 1
Mount the LMS 4.2 DVD.

The RSAC installables are available in the RSAC directory on LMS 4.2 DVD.
Step 2
Enter the following to start the installation:

# cd RSAC
# ./setup.sh
Step 3
Follow the wizard instructions to install the product.

After the installation of Remote Syslog Collector, select Admin > System > Software Center >
Software Update to verify the installation. Remote Syslog Collector should be listed.
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
Navigate to the RSAC folder on the LMS 4.2 DVD.
Step 2
Double-click the Setup.exe file to start the installation.
Step 3
Follow the wizard instructions to install the product.

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.
Installing on Soft Appliance

To install the Remote Syslog Collector on a LMS Soft Appliance system (OVA file):
Step 1
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.
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.

OL-25957-01
C-5
Appendix C
Subscribing to a Remote Syslog Collector

Step 1
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
Hostname or the IP address of the host on which the Collector is installed.
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
Number of forwarded Syslog messages.
Dropped
Number of unprocessed Syslog messages.
Invalid
Number of invalid Syslog messages.
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
Number of Syslog messages received.
Test Collector
Subscription
Click to test a Syslog collector thats already subscribed or thats going to be

subscribed.
Subscribe
Click to subscribe a Syslog collector.
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.
Starting the Remote Syslog Collector

To start the Remote Syslog Collector, enter pdexec SyslogCollector at the command prompt on the
machine where Syslog Collector is installed. It starts by default.
C-6
OL-25957-01
Appendix C


To stop the Remote Syslog Collector, enter pdterm SyslogCollector at the command prompt on the
machine where Syslog Collector is installed.

Perform the following to uninstall RSAC:
Uninstallation on Windows
Uninstallation on Solaris
Uninstallation on Soft Appliance
Uninstallation on Windows
To uninstall on a Windows system:
Step 1
Select Start > Programs > CiscoWorks > Uninstall CiscoWorks.

The Uninstallation dialog box appears, displaying all of the installed components.
Step 2
Select Remote Syslog Collector.
Step 3
Click Next to begin uninstalling the selected component.
Uninstallation on Solaris
To uninstall on a Solaris system:
Step 1
Enter these commands as root to start the uninstall program:

# cd /
#
Step 2
NMSROOT/bin/uninstall.sh
Follow the prompts from the uninstallation wizard.
Uninstallation on Soft Appliance

Uninstallation of Remote Syslog Collector is not supported in the Soft Appliance.

OL-25957-01
C-7
Appendix C

After installing the Syslog Collector on a remote machine, you need to check the Syslog Collector
Properties file to ensure that the Collector is configured properly.
The Syslog Collector Properties file is available at these locations:
/opt/CSCOpx/MDC/tomcat/webapps/rme/WEB-INF/classes/com/cisco/nm/rmeng/csc/data/
On Windows:
NMSROOT\MDC\tomcat\webapps\rme\WEB-INF\classes\com\cisco\nm\rmeng\csc\data\
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:
rmeng\fcss\data\TimeZone.lst
COUNTRY_CODE
Country code for the Syslog Collector.

We recommend that you set the country code variable with the appropriate
country code, to make sure that the Syslog timestamp conversion works
correctly.
For example, if you are in Singapore, you must set the country code variable
as COUNTRY=SGP.
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.

/var/log/syslog_info
On Windows:
NMSROOT\log\syslog.log
DEBUG_CATEGOR
Y_NAME
Name Syslog Collector uses for printed ERROR or DEBUG messages.

The default category name is SyslogCollector.
We recommend that you do not change the default value.
DEBUG_FILE
Filename and location of the Syslog Collector log file containing debug
information:

/var/adm/CSCOpx/log/CollectorDebug.log
On Windows:
NMSROOT\log\CollectorDebug.log
DEBUG_LEVEL
Debug levels in which you run the Syslog Collector.

We recommend that you retain the default INFO, which reports informational
messages. Setting it to any other value might result in a large number of debug
messages being reported.
If you change the debug level, you must restart the Syslog Collector.
The values for the Debug levels are:
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.

OL-25957-01
C-9
Appendix C
Timezone-Related
Properties
Description
Miscellaneous Properties
READ_INTERVAL_
IN_SECS
The interval at which the Collector polls the syslog file.

The default is set to 1 second.
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.

cisco/nm/rmeng/fcss/data/FormatParsers.lst
On Windows:
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:
cisco/nm/rmeng/csc/data/Subscribers.dat
On Windows:
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_PORT 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

Table D-1 lists the supported server timezones in LMS 4.2:
Table D-1
Supported Server Time Zones
List of Supported Time Zone Time Zone Acronym

Values (Area Covered)
Setting on Device
Definition
Offset from GMT
Brazil / DeNoronha
FNT
Fernando de Noronha Time
-2:00
Brazil / West
BST
British Summer Time
+1:00
Brazil/Acre
AMT
Amazon Time
-4:00
Brazil/East
EST
Eastern Standard Time
-3:00
GMT0
AZOST
Azores Summer Time
-1:00
Iceland
GMT
Greenwich Mean Time
0:00
EET
EET
Eastern European Time
+2:00
United States / Pacific
PST
Pacific Standard Time
-8:00
US/Indiana-Starke
EST
-5:00
US/Samoa
SST
Samoa Standard Time
-11:00
US/Arizona
MST
Mountain Standard Time
-7:00
US/East-Indiana
EDT
Eastern Daylight Time
-5:00
US/Central
CST
Central Standard Time
-6:00
US/Eastern
EST
-5:00
US/Mountain
MST
-7:00
US/Alaska
AST
Alaska Standard Time
-9:00
US/Hawaii
HAST
Hawaii-Aleutian Standard Time
-10:00
US/Aleutian
HAST
-10:00
US/Michigan
EDT
-5:00
MST
MST
-7:00
CET
CET
Central Europian Time
+1:00
Asia/Chungking
CST
China Standard Time
+8:00
Asia/Bangkok
ICT
Indochina Time
+7:00
Asia/Kashgar
CST
+8:00

OL-25957-01
D-1
Appendix D
Table D-1

Setting on Device
Definition
Offset from GMT
Asia/Macao
CST
China Standard Time
+8:00
Asia/Yakutsk
YAKT
Yakutsk Time
+9:00
Asia/Riyadh
AST
Arabia Standard Time
+3:00
Asia/Makassar
WITA
Central Indonesian Time
+8:00
Asia/Shanghai
CCT
China Taiwan Time
+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
China Standard Time
+8:00
Asia/Tel_Aviv
IDT
Israel Daylight Time
+3:00
Asia/Anadyr
MAGST
Magadan Summer Time
+12:00
Asia/Istanbul
EEST
Eastern European Summer Time
+2:00
Asia/Jakarta
WIT
Western Indonesian Time
+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
Armenia Summer Time
+5:00
Asia/Seoul
KST
Korea Standard Time
+9:00
Asia/Taipei
CST
China Standard Time
+8:00
Asia/Bahrain
AST
+3:00
Asia/Jerusalem
IDT
Israel Daylight Time
+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
Gulf Standard Time
+4:00
Asia/Tokyo
JST
Japan Standard Time
+9:00
Asia/Omsk
OMSST
Omsk Summer Time
+7:00
Asia/Calcutta
IST
India Summer Time
+5:30
Asia/Kabul
AFT
Afghanistan Time
+4:30
Asia/Karachi
PKT
Pakistan Standard Time
+5:00
Asia/Damascus
EEST
+2:00
Asia/Singapore
SGT
Singapore Time
+8:00
Asia/Samarkand
UZT
Uzbekistan Time
+5:00
Asia/Dili
TLT
East Timor Time
+9:00
D-2
OL-25957-01
Appendix D
Table D-1

Setting on Device
Definition
Offset from GMT
Asia/Dhaka
BST
Bangladesh Standard Time
+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
Yekaterinburg Summer Time
+6:00
Asia/Kamchatka
PETST
Kamchatka Summer Time
+12:00
Asia/Macau
CST
Chinsa Standard Time
+8:00
Asia/Oral
ORAT
ORAT
+5:00
Asia/Ashgabat
TMT
Turkmenistan Time
+5:00
Asia/Novosibirsk
NOVST
Novosibirsk Summer Time
+7:00
Asia/Thimphu
BTT
Bhutan Time
+6:00
Asia/Ulan_Bator
IRKST
Irkutsk Summer Time
+9:00
Asia/Nicosia
EEST
+2:00
Asia/Phnom_Penh
ICT
Indochina Time
+7:00
Asia/Irkutsk
IRKST
Irkutsk Summer Time
+9:00
Asia/Urumqi
CST
Chinsa Standard Time
+8:00
Asia/Kuching
MYT
Malaysia Time
+8:00
Asia/Kolkata
IST
India Standard Time
+5:30
Asia/Vladivostok
VLAST
Vladivostok Summer Time
+11:00
Asia/Dacca
BST
Bangladesh Standard Time
+6:00
Asia/Baku
AZST
Azerbaijan Summer Time
+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
Hong Kong Time
+8:00
Asia/Magadan
MAGST
Magadan Summer Time
+12:00
Asia/Krasnoyarsk
KRAST
Krasnoyarsk Summer Time
+8:00
Asia/Katmandu
NPT
Nepal Time
+5:45
Asia/Gaza
EEST
+2:00
Asia/Brunei
BNT
Brunei Darussalam Time
+8:00
Asia/Pyongyang
KST
Korea Standard Time
+9:00
Asia/Colombo
IST
India Standard Time
+5:30
Asia/Choibalsan
ULAT
Ulaanbaatar Time
+8:00
Asia/Bishkek
KGT
Kyrgyzstan Time
+6:00

OL-25957-01
D-3
Appendix D
Table D-1

Setting on Device
Definition
Offset from GMT
Asia/Baghdad
AST
+3:00
Asia/Tehran
IRDT
Iran Daylight Time
+4:30
Asia/Chongqing
CST
China Standard Time
+8:00
Asia/Tbilisi
GET
Georgia Standard Time
+4:00
Asia/Amman
EEST
+2:00
Asia/Ujung_Pandang
WITA
Central Indonesian Time
+8:00
Asia/Riyadh
AST
+3:00
Asia/Pontianak
WIB
Western Indonesian Time
+7:00
Asia/Muscat
GST
Gulf Standard Time
+4:00
Asia/Sakhalin
SAST
South Africa Standard Time
+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
Arab Standard Time
+3:00
Asia/Jayapura
WIT
Eastern Indonesian Time
+9:00
PRC
MST
-7:00
Japan
JST
Japan Standard Time
+9:00
Antarctica/DumontDUrvill
e
DDUT
Dumont-d`Urville Time
+10:00
Antarctica/Palmer
NZST
New Zealand Standard Time
+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
Syowa Time Time Zone
+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
Gilbert Island Time
+12:00
Pacific/Gambier
GAMT
Gambier Time
+9:00
Pacific/Port_Moresby
PGT
Papua New Guinea Time
+10:00
Pacific/Kiritimati
LINT
Line Islands Time
+14:00
Pacific/Nauru
NRT
Nauru Time Zone
+12:00
Pacific/Rarotonga
CKT
Cook Island Time
-10:00
D-4
OL-25957-01
Appendix D
Table D-1

Setting on Device
Definition
Offset from GMT
Pacific/Galapagos
GALT
Galapagos Time
-6:00
Pacific/Yap
YAPT
Yap Time
+10:00
Pacific/Wake
WAKT
Wake Iland Time Zone
+12:00
Pacific/Auckland
NZST
+12:00
Pacific/Samoa
SST
Samoa Standard Time
-11:00
Pacific/Apia
WST
West Samoa Time
-11:00
Pacific/Majuro
MHT
Marshall Islands Time
+12:00
Pacific/Efate
VUT
Vanuata Time
+11:00
Pacific/Guam
ChST
Chamorro Standard Time
+10:00
Pacific/Chatham
CHAST
Chatham Island Standard Time
+12:45
Pacific/Honolulu
HAST
-10:00
Pacific/Pago_Pago
SST
Samoa Standard Time
-11:00
Pacific/Kwajalein
MHT
+12:00
Pacific/Wallis
WFT
Wallis and Futuna Time
+12:00
Pacific/Norfolk
NFT
Norfolk Time
+11:30
Pacific/Niue
NUT
Niue Time
-11:00
Pacific/Kosrae
KOST
Kosrae Standard Time
+11:00
Pacific/Pitcairn
PST
Pitcairn Standard Time
-8:00
Pacific/Midway
SST
Samoa Standard Time
-11:00
Pacific/Funafuti
TVT
Tuvalu Time
+12:00
Pacific/Saipan
ChST
Chamorro Standard Time
+10:00
Pacific/Marquesas
MART
Marquesas Time
-9:30
Pacific/Tongatapu
TOST
Tongatapu Standard Time
+13:00
Pacific/Easter
EAST
Easter Island Standard Time
-6:00
Pacific/Noumea
NCT
New Caledonia Time
+11:00
Pacific/Ponape
PONT
Pohnpei Standard Time
+11:00
Pacific/Guadalcanal
SBT
Solomon Island Time
+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
Hawaiian Daylight Time
-9:30
Pacific/Enderbury
PHOT
Phoenix Island Time
+13:00
Pacific/Fiji
FJT
Fiji Time
+12:00
Pacific/Truk
TRUT
Truk Time
+10:00
PST8PDT
PDT
Pacific Daylight Time
-7:00

OL-25957-01
D-5
Appendix D
Table D-1

Setting on Device
Definition
Offset from GMT
Hongkong
HKT
Hong Kong Time
+8:00
EST5EDT
EDT
-4:00
GMT
GMT
Greenwhich Mean Time
+0:00
Mideast/Riyadh88
AST
+3:00
Mideast/Riyadh89
AST
+3:00
Mideast/Riyadh87
AST
+3:00
W-SU
MSD
Mascow Daylight Time
+3:00
Navajo
MDT
Mountain Daylight Time
-7:00
GB
BST
British Summer Time
+1:00
NZ
NZST
+12:00
UCT
UCT
Universal Time
+0:00
CST6CDT
CDT
Central Daylight Time
-6:00
Jamaica
EST
-5:00
Universal
UCT
Universal Time
+0:00
Portugal
WEST
Western European Summer Time
+1:00
Cuba
CDT
Cuba Daylight Time
-5:00
Arctic/Longyearbyen
CEST
Central European Summer Time
+1:00
Turkey
EEST
+2:00
GB-Eire
BST
British Summer Time
+1:00
HST
HAST
-10:00
UTC
Universal
Universal
+0:00
Egypt
EET
+2:00
Singapore
SGT
Singapore Time
+8:00
Eire
IST
Irish Standard Time
+1:00
America/Yellowknife
MDT
-7:00
America/Yakutat
YDT
Yukon Daylight Time
-8:00
America/Belem
BRT
Braslia time
-3:00
America/Eirunepe
ACST
Australian Central Standard Time
+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

Setting on Device
Definition
Offset from GMT
America/Merida
CDT
-6:00
America/Cambridge_Bay
MDT
-7:00
America/Buenos_Aires
ART
Argentina Time
-3:00
America/Aruba
AST
Atlantic Standard Time
-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
America/North_Dakota/New_Salem
PDT
-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
Newfoundland Daylight Time
-3:30
America/Montserrat
AST
-4:00
America/Antigua
AST
-4:00
America/Godthab
WGST
Western Greenland Summer Time
-3:00
America/Nassau
EDT
-5:00
America/Shiprock
MDT
-7:00
America/Indianapolis
EDT
-5:00
America/Cayenne
GFT
French Guiana Time
-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
America/Noronha
FNT
Fernando de Noronha Time
-2:00

OL-25957-01
D-7
Appendix D
Table D-1

Setting on Device
Definition
Offset from GMT
America/St_Vincent
AST
-4:00
America/Juneau
AKDT
Alaska Daylight Time
-9:00
America/Sao_Paulo
BRT
Brasilla Time
-3:00
America/Marigot
AST
-4:00
America/Resolute
CDT
-6:00
America/Caracas
VET
Venezuelan Standard Time
-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
Moutain Daylight Time
-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/Tucuman
ART
Argentina Time
-3:00
America/Argentina/Rio_Gallegos
ART
Argentina Time
-3:00
D-8
OL-25957-01
Appendix D
Table D-1

Setting on Device
Definition
Offset from GMT
America/Argentina/Catamarca
ART
Argentina Time
-3:00
America/Argentina/La_Rioja
ART
Argentina Time
-3:00
America/Argentina/San_- ART
Juan
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
Cuba Daylight Time
-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
Atlantic Daylight Time
-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

OL-25957-01
D-9
Appendix D
Table D-1

Setting on Device
Definition
Offset from GMT
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
Hawaii-Aleutian Daylight Time
-9:00
America/Adak
HADT
Hawaii-Aleutian Daylight Time
-10:00
America/Belize
CST
-6:00
America/Louisville
EDT
-5:00
America/Miquelon
PMDT
Pierre & Miquelon Daylight Time
-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

Setting on Device
Definition
Offset from GMT
America/Kentucky/Louis- EDT
ville
-5:00
America/Monterrey
CDT
-6:00
America/Guatemala
CST
-6:00
America/Chicago
CDT
-6:00
MET
MEST
Middle European Summer Time
+2:00
Factory
GMT
+0:00
Indian/Mahe
IST
India Standard Time
+5:30
Indian/Maldives
MVT
Maldives Time
+5:00
Indian/Mauritius
MUT
Mauritius Time
+4:00
Indian/Chagos
IOT
Indian Chagos Time
+6:00
Indian/Cocos
CCT
Cocos Islands Time
+6:30
Indian/Reunion
RET
Reunion Time
+4:00
Indian/Comoro
EAT
East Africa Time
+3:00
Indian/Antananarivo
EAT
East Africa Time
+3:00
Indian/Christmas
CXT
Christmas Island Time
+7:00
Indian/Kerguelen
TFT
French Southern and Antartic Time
+5:00
Indian/Mayotte
EAT
East Africa Time
+3:00
Canada/Pacific
PDT
-7:00
Canada/East-Saskatchewan
CST
Cenntral Standard Time
-6:00
Canada/Newfoundland
NDT
Newfoundland Daylight Time
-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
Western Standard Time
+8:00

OL-25957-01
D-11
Appendix D
Table D-1

Setting on Device
Definition
Offset from GMT
Australia/Darwin
CST
+9:30
Australia/Yancowinna
CST
+9:30
Australia/Brisbane
EST
+10:30
Australia/Lord_Howe
LHST
Lord Howe Standard Time
+10:30
Australia/Currie
EST
+10:00
Australia/Adelaide
CST
+9:30
Australia/Perth
WST
Western Standard Time
+8:00
Australia/Hobart
EST
+10:00
Australia/ACT
EST
+10:00
Australia/North
CST
+9:30
Australia/Eucla
CWST
Central Western Summer Time
+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
Lord Howe Standard Time
+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
Falkland Islands Summer Time
-3:00
Atlantic/Faroe
WEST
+1:00
Atlantic/Canary
WEST
+1:00
Atlantic/Azores
AZOST
Azores Summer Time
+0:00
Atlantic/South_Georgia
GST
Guam Standard Time
-2:00
Atlantic/St_Helena
GMT
Greenwich Mean Time
+0:00
Atlantic/Cape_Verde
CVT
Current Cape Verde Time
-1:00
Atlantic/Jan_Mayen
CEST
+2:00
Atlantic/Reykjavik
GMT
Greenwich Mean Time
+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

Setting on Device
Definition
Offset from GMT
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
Eastern Greenland Summer Time
+0:00
Kwajalein
MHT
+12:00
Iran/Tehran
IRDT
Iran Daylight Time
+4:30
Iran/Tehran
IRST
Iran Standard Time
+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
Irish Standard Time
+1:00
Europe/Guernsey
BST
British Summer Time
+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

OL-25957-01
D-13
Appendix D
Table D-1

Setting on Device
Definition
Offset from GMT
Europe/Jersey
BST
British Summer Time
+1:00
Europe/Isle_of_Man
BST
British Summer Time
+1:00
Europe/Copenhagen
CEST
+2:00
Europe/Volgograd
MSD
Moscow Daylight Time
+4:00
Europe/Gibraltar
CEST
+2:00
Europe/Vatican
CEST
+2:00
Europe/Belfast
BST
British Summer Time
+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
British Summer Time
+1:00
Europe/Moscow
MSD
+4:00
Europe/Madrid
CET
Central European Time
+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

Setting on Device
Definition
Offset from GMT
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
Greenwich Mean Time
+0:00
Africa/Maseru
SAST
+2:00
Africa/Conakry
GMT
Greenwich Mean Time
+0:00
Africa/Niamey
WAT
West Africa Time
+1:00
Africa/Blantyre
CAT
Central Africa Time
+2:00
Africa/Nouakchott
GMT
Greenwich Mean Time
+0:00
Africa/Johannesburg
SAST
+2:00
Africa/Asmera
EAT
Eastern Africa Time
+3:00
Africa/Windhoek
WAT
West Africa Time
+1:00
Africa/Ndjamena
WAT
West Africa Time
+1:00
Africa/Abidjan
GMT
Greenwich Mean Time
+0:00
Africa/Malabo
WAT
West Africa Time
+1:00
Africa/Maputo
CAT
Central Africa Time
+2:00
Africa/Lome
GMT
Greenwich Mean Time
+0:00
Africa/Khartoum
EAT
Eastern Africa Time
+3:00
Africa/Harare
CAT
Central Africa Time
+2:00
Africa/Bamako
GMT
Greenwich Mean Time
+0:00
Africa/Asmara
GMT
Greenwich Mean Time
+0:00
Africa/Porto-Novo
WAT
West Africa Time
+1:00
Africa/Douala
WAT
West Africa Time
+1:00
Africa/Mbabane
SAST
Eastern Africa Time
+2:00
Africa/Kampala
EAT
Eastern Africa Time
+3:00
Africa/Lusaka
CAT
Central Africa Time
+2:00
Africa/Tunis
CET
+1:00
Africa/Addis_Ababa
EAT
Eastern Africa Time
+3:00
Africa/Lubumbashi
CAT
Central Africa Time
+2:00
Africa/Ceuta
CEST
+2:00
Africa/Freetown
GMT
Greenwich Mean Time
+0:00

OL-25957-01
D-15
Appendix D
Table D-1

Setting on Device
Definition
Offset from GMT
Africa/Mogadishu
EAT
Eastern Africa Time
+3:00
Africa/Banjul
GMT
Greenwich Mean Time
+0:00
Africa/Luanda
WAT
West Africa Time
+1:00
Africa/Bangui
WAT
West Africa Time
+1:00
Africa/Lagos
WAT
West Africa Time
+1:00
Africa/Brazzaville
WAT
West Africa Time
+1:00
Africa/Nairobi
EAT
Eastern Africa Time
+3:00
Africa/Algiers
CET
+2:00
Africa/Dar_es_Salaam
GMT
Greenwich Mean Time
+0:00
Africa/Dakar
GMT
Greenwich Mean Time
+0:00
Africa/Accra
GMT
Greenwich Mean Time
+0:00
Africa/Tripoli
EET
+2:00
Africa/Djibouti
EAT
Eastern Africa Time
+3:00
Africa/Libreville
WAT
West Africa Time
+1:00
Africa/Kinshasa
WAT
West Africa Time
+1:00
Africa/El_Aaiun
GMT
Greenwich Mean Time
+0:00
Africa/Cairo
EET
+2:00
Africa/Timbuktu
GMT
Greenwich Mean Time
+0:00
Africa/Sao_Tome
GMT
Greenwich Mean Time
+0:00
Africa/Monrovia
GMT
Greenwich Mean Time
+0:00
Africa/Bissau
GMT
Greenwich Mean Time
+0:00
Africa/Bujumbura
CAT
Central Africa Time
+2:00
Africa/Gaborone
CAT
Central Africa Time
+2:00
Africa/Kigali
CAT
Central Africa Time
+2:00
Africa/Casablanca
WEST
+2:00
Iran/Tehran
IRDT
Iran Daylight Time
+4:30
Iran/Tehran
IRST
Iran Standard Time
+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
Irish Standard Time
+1:00
Europe/Guernsey
BST
British Summer Time
+1:00
Europe/Riga
EEST
+3:00
Europe/Monaco
CEST
+2:00
D-16
OL-25957-01
Appendix D
Table D-1

Setting on Device
Definition
Offset from GMT
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
British Summer Time
+1:00
Europe/Isle_of_Man
BST
British Summer Time
+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
British Summer Time
+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
British Summer Time
+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

OL-25957-01
D-17
Appendix D
Table D-1

Setting on Device
Definition
Offset from GMT
Europe/Sofia
EEST
+3:00
Europe/Malta
CEST
+2:00
D-18
OL-25957-01
A P P E N D I X

You can take a full manual backup using the following syntax:
LMS 3.2 SP/LMS 4.0.1/4.1/4.2
Syntax
backup.pl
On Solaris and Soft

Appliance
/opt/CSCOpx/bin/perl /opt/CSCOpx/bin/backup.pl BKP [Logfile]

email=comma_separated_email_ids [Num_Generations]
On Windows
NMSROOT\bin\perl NMSROOT\bin\backup.pl BKP [Logfile]

email=[comma_separated_email_ids] [Num_Generations]
You can take selective backup using the following syntax:

LMS 3.2 SP/LMS 4.0.1/LMS 4.1/4.2
Syntax
backup.pl
On Solaris and Soft

Appliance
/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]
The following table lists the explanation for the syntax:

Syntax
Explanation
NMSROOT
LMS installation directory (by default, /opt/CSCOpx for Solaris and

Soft Appliance, and C:\Program Files\CSCOpx for Windows, where
C: is the System Drive)
dir1
Directory where you have extracted backup.pl
BKP
Backup directory where you have backed up data using backup.pl
Logfile
Log file name that contains the details of the backup. The default
location of the backup log file (dbbackup.log) is:
BackupDirectory
NMSROOT\CSCOpx\log\ (On Windows)
/var/adm/CSCOpx/log/ (On Solaris and Soft Appliance)
Directory that you want to be your Backup directory.

OL-25957-01
E-1
Appendix E
Syntax
Explanation
comma_separated_email_ids
Email IDs seperated by comma.
Num_Generations
Maximum backup generations to be kept in the backup directory.
Example 1
To back up LMS 3.2 SP data in the backup directory, enter:
On Solaris:
opt/CSCOpx/bin/perl /opt/CSCOpx/bin/backup.pl /backup email=
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

You can use the restorebackup.pl script to restore the LMS data you have backed up.
For a successful restoration of backed up data, ensure that all services and processes are up and running.
Stop the daemons and then run restorebackup.pl.
Note
Cross platform restore is supported only from Solaris/Window to Soft Appliance.

The syntax for restorebackup.pl is as follows:
Solaris and Soft Appliance

NMSROOT/bin/perl NMSROOT/bin/restorebackup.pl -d BKP [-t temporary_directory] [-h]
[-gen generationNumber]
Windows
NMSROOT\bin\perl NMSROOT\bin\restorebackup.pl -d BKP [-t temporary_directory] [-h]
[-gen generationNumber]
The following table lists the explanation for the syntax:

Syntax
Explanation
NMSROOT(Required)
LMS installation directory (by default, /opt/CSCOpx in

Solaris and Soft Appliance, and C:\Program Files\CSCOpx
in Windows where C: is the System Drive)
-t
temporary_directory(Optional)
-gen generationNumber(Optional)
-d
BKP(Required)
-h(Optional)
This is the directory or folder used by the restore program to

store its temporary files. By default this directory is
NMSROOT/tempBackupData. You can customize this by
specifying your own temporary directory to avoid
overloading NMSROOT
This is the generation number. -gen now is the latest
generation. If generations 1 through 5 exist, then 5 is the
latest.
This is the absolute directory or folder used by the restore
program to store the backup.
Displays help. When used with -d BackupDirectory, show s
correct syntax along with available suites and generations

OL-25957-01
F-1
Appendix F
Examples
To restore...
Enter this command in Solaris and

Soft Appliance
Enter this command in Windows
The latest version

of data
C:\Progra~1\CSCOpx\bin\perl
opt/CSCOpx/bin/perl
opt/CSCOpx/bin/restorebackup.p C:\Progra~1\CSCOpx\bin\
restorebackup.pl -d BKP -gen now
l -d BKP -gen now
The 12th
generation of data
opt/CSCOpx/bin/perl
opt/CSCOpx/bin/restorebackup.p C:\Progra~1\CSCOpx\bin\
l -d BKP -gen 12
restorebackup.pl -d BKP -gen
Data from the

forced auto backup
during the CS
upgrade process
opt/CSCOpx/bin/perl
opt/CSCOpx/bin/restorebackup.p
l
-d DB_BKP1/automaticbackup/c
mfbackup -gen now
12
C:\Progra~1\CSCOpx\bin\
restorebackup.pl -d
DB_BKP\automaticbackup\cmfbackup
-gen now
1. DB_BKP is the backup directory created by the user.
F-2
OL-25957-01
INDEX
device package updates
disabling FIPS
accessing LMS server
2-19
6-51
application scaling numbers
3-12
E
enabling FIPS
2-19
evaluation mode
before installation
1-18
3-8
3-2
F
C
FIPS, enabling/disabling
cautions, significance of
i-xvi
cautions regarding
daemon manager, starting and stopping
8-2
Cisco Prime LMS 4.1
high availability, setting up
install and upgrade behavior
1-2
on Windows
Cisco Prime LMS 4.2

processes
overview
6-50
4-5
4-1
system requirements
product overview
concurrent users
2-19
1-1
Veritas components
4-4
4-3
3-15
configuring SNMP Traps
7-23
I
install, preparing to
3-1
installation
database password rules
A-4
new installations
data migration
password rules for
Inventory, Config and Image Management

normal backup
overview
scope
7-2
1-14
7-2
notes
general
3-2
Solaris
3-3
Windows
selective backup
debugging CAM
8-18
7-2
prerequisites
8-17
device credentials, required
3-4
2-1
terms and definitions

2-27
A-4
3-1
installation terms
OL-25957-01
IN-1
Index
Admin password
3-1
Application database password

Cisco.com user ID and password
Fault Management
3-1
installation terms overview

Self signed certificate
C-1
Migration From 2.6 or 2.6 SP1

Remote
Integration Utility
supported NMS
8-22
Network Topology, Layer 2 Services and User

Tracking 8-19
3-1
installing RSAC (see RSAC)
8-21
3-2
8-23
7-16
Migration From LMS 3.0 or LMS 3.0 December 2007

Update or LMS 3.1
1-16
Remote
7-16
Migration Scope
CiscoWorks Assistant
license file
3-7
migration scope
license file, installing

license information
3-11
CiscoView
3-5
7-11
Common Services
licensing LMS 4.2
7-3
evaluation license
license file
7-13
3-8
Fault Management
3-7
NFR license
7-11
7-9
Inventory, Config and Image Management
3-10
product ordering and PAK
3-5
Portal
7-25
before uninstalling
concurrent users
7-13
6-54
3-15
license information
new installation
7-10
Network Topology, Layer 2 Services and User

Tracking 7-5
LMS
AAA Methods
3-5
6-1
N
new features
prerequisites
2-1
Template Center
reinstallation
6-56
third-party software and tool changes
uninstallation
Solaris
Windows
uninstalling
logging into LMS
7-6
1-14
1-14
new installation
6-54
silent mode
6-55
Solaris
6-54
6-43
6-37
verifying installation
6-53
Windows
NFR license
6-49
6-40
3-10
M
messages, installation
8-4
migration errors, troubleshooting

Common Services
8-17
P
PAK
3-5
password information
IN-2
OL-25957-01
Index
database password
A-4
new installation rules

port usage
A-4
scaling numbers
2-21
post-upgrade activities, CS
scope of data migration
7-25
selftest tool
processors, supported
Solaris
Server
2-11
Windows
3-12
7-2
8-17
2-9, 2-12
Solaris patches
2-15
cluster patches
2-21
required and recommended
stopping RSAC
Recovering Admin Password

required device credentials
System
Common Syslog Collector, subscribing to
uninstalling RSAC
properties file
C-4
C-4
C-9
C-9
FILTER_THREADS
2-12
2-9
terminal server support

about Terminal Services
C-10
C-10
READ_INTERVAL_IN_SECS
SUBSCRIPTION_DATA_FILES
SYSLOG_FILES
C-10
C-10
on Windows 2003
2-17
on Windows 2008
2-17
troubleshooting installation
messages, understanding
C-9
8-4
process status, viewing and changing
C-8
TIMEZONE_FILE
2-17
enabling or disabling Terminal Services
C-10
QUEUE_CAPACITY
8-1
C-8
server requirements, verifying
C-3
2-16
DEBUG_MAX_FILE_SIZE
C-7
2-9
Storage Area Network
C-9
C-9
uninstalling
2-3
on Windows
C-8
DEBUG_MAX_BACKUPS
C-7
operating system
C-9
DEBUG_LEVEL
TIMEZONE
2-16
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
system and browser requirements
C-7
COUNTRY_CODE
1-15
2-16
disk space
Syslog Analyzer Collector
stopping
C-6
C-1
Remote Syslog Collector
1-18
supported Network Management Systems
2-27
RSAC (Remote Syslog Analyzer Collector)

installing
C-7
supported devices
8-2
2-19
C-2
U
UCS support
2-16
uninstalling LMS 4.2

before you begin
6-54

OL-25957-01
IN-3
Index
on Solaris
6-54
on Windows
6-55
uninstalling RSAC
C-7
upgrading LMS
remote upgrade on Solaris
remote upgrade on Windows
upgrading RSAC
6-48
6-49
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
users, hosts or IP phones search
B-6
IN-4
OL-25957-01

Install Cisco LSM PDF

Uploaded by

Document Information

Original Description:

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Install Cisco LSM PDF

Uploaded by

Copyright:

Available Formats

Installing and Migrating to Cisco Prime

LAN Management Solution 4.2

Text Part Number: OL-25957-01

OpenSSL/Open SSL Project

Related Documentation for CiscoWorks LAN Management Solution 4.0

Overview of Cisco Prime LAN Management Solution 4.2

Install and Upgrade Behavior 1-2

Installing and Migrating to Cisco Prime LAN Management Solution 4.2

Enhancement in Custom Inventory Report 1-11

Supported Network Management Systems

System and Browser Requirements for Server and Client 2-2

Required Device Credentials for LMS Functionalities

Preparing to Install Cisco Prime LAN Management Solution 4.2

Before You Begin Installation 3-2

Installing and Migrating to Cisco Prime LAN Management Solution 4.2

Installation Notes (For Soft Appliance Only)

Licensing Your Product 3-5

Application Scaling Numbers 3-12

System Requirements for High Availability Implementation

Setting up LMS High Availability Environment on Windows 4-5

Installing and Migrating to Cisco Prime LAN Management Solution 4.2

Installing Storage Foundation HA 5.1 on Solaris 4-21

Overview of VMware VMotion and Storage VMotion 5-5

Installing and Migrating to Cisco Prime LAN Management Solution 4.2

Deploying Template to New VM

Performing Installation of Cisco Prime LMS 4.2

Performing Installation of LMS 4.2 6-1

Accessing LMS Server 6-51

Uninstalling LMS 4.2 6-54

Re-installing LMS 4.2

Migrating Data to Cisco Prime LAN Management Solution 4.2

Scope of Data Migration 7-2

Guidelines to Post-Upgrade Activities 7-22

Troubleshooting and FAQs

Checking Processes After Installation

Viewing and Changing Process Status

Recovering Admin Password on LMS Virtual Appliance

Troubleshooting Errors in Data Migration 8-15

Installing and Migrating to Cisco Prime LAN Management Solution 4.2

Inventory, Config and Image Management Data Migration Errors 8-18

User Inputs for Installation

User Inputs for LMS Installation A-1

User Tracking Utility

Hardware and Software Requirements for UTU 2.0

Installing UTU 2.0 B-3

Searching for Users, Hosts or IP Phones

Upgrading to UTU 2.0

Re-installing UTU 2.0

Installing the Remote Syslog Collector

Verifying Remote Syslog Collector Server Requirement

Installing and Migrating to Cisco Prime LAN Management Solution 4.2

Installing on Soft Appliance C-5

Supported Server Time Zones and Offset Settings

Syntax and Usage for Backup Script

Syntax and Usage for Restore Script

Installing and Migrating to Cisco Prime LAN Management Solution 4.2

OpenSSL/Open SSL Project

Copyright 1998-2007 The OpenSSL Project. All rights reserved.

Redistributions of any form whatsoever must retain the following acknowledgment:

Installing and Migrating to Cisco Prime LAN Management Solution 4.2

Copyright 1995-1998 Eric Young (eay@cryptsoft.com). All rights reserved.

THIS SOFTWARE IS PROVIDED BY ERIC YOUNG AS IS AND ANY EXPRESS OR IMPLIED