Installing and Migrating to Cisco Prime LAN Management Solution 4.1

Transcription

1 Installing and Migrating to Cisco Prime LAN Management Solution 4.1 Americas Headquarters Cisco Systems, Inc. 170 West Tasman Drive San Jose, CA USA Tel: NETS (6387) Fax: Text Part Number:

2 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 UCB s 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 of Cisco Systems, Inc. and/or its affiliates in the U.S. and other countries. A listing of Cisco's trademarks can be found at 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. (1005R) 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. Copyright Cisco Systems, Inc. All rights reserved.

3 CONTENTS Notices xi OpenSSL/Open SSL Project License Issues i-xi i-xi Preface 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 i-xix i-xxi CHAPTER 1 Overview of Cisco Prime LAN Management Solution Product Overview 1-1 Install and Upgrade Behavior 1-2 Overview of Upgrade and Migration 1-2 Upgrading Master-Slave Server Setup 1-4 New Features and Enhancements in LMS LMS 4.1 Soft Appliance 1-8 Cross Platform Data Migration Support 1-8 MACsec Provisioning 1-8 Medianet Work Center 1-9 Device Profiling using AutoSmartports Provisioning 1-10 Configuration Center 1-10 Smart Interactions 1-11 TAC Service Requests Pane 1-11 Enhancements in Template Center 1-11 Combined UT Reports for all Endhost Types 1-12 LLDP-based Discovery Support 1-12 Search LMS Tasks 1-12 IPSLA Video Operations 1-12 Troubleshooting Workflow Changes 1-13 Enhancements to Default Credential Set Policy Configuration 1-13 Enhancements to Trigger Job Discovery 1-13 Grouping Newly Discovered Devices 1-13 Enhancements to Ping Sweep Module 1-14 iii

4 Contents Faster Discovery Updates to DCR 1-14 Third-Party Software and Tool Changes 1-14 Data Migration Overview 1-14 Supported Network Management Systems 1-15 Supported Devices 1-18 CHAPTER 2 Prerequisites 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-4 Link Aggregation Support in Solaris Server Requirements on Soft Appliance Systems 2-6 Server Requirements on Solaris Systems 2-8 Server Requirements on Windows Systems 2-11 Unified Computing System (UCS) Support 2-14 System Requirements on Client Systems 2-14 Terminal Server Support for Windows Server 2-15 Enabling and Disabling Terminal Services on Windows 2008 Server 2-15 Enabling and Disabling FIPS on Windows 2008 Servers 2-17 Solaris Patches 2-17 Required and Recommended Solaris Patches 2-17 Cluster Patches 2-19 LMS 4.1 Port Usage 2-19 Important URLs 2-24 Required Device Credentials for LMS Functionalities 2-25 CHAPTER 3 Preparing to Install Cisco Prime LAN Management Solution Terms and Definitions Used in LMS Installation Framework 3-1 Before You Begin Installation 3-3 Installation Notes 3-3 Installation Notes (For Solaris Only) 3-5 Installation Notes (For Windows Only) 3-5 Installation Notes (For Soft Appliance Only) 3-6 Licensing Your Product 3-6 Understanding Product Ordering Options and Product Authorization Key 3-6 Ordering Physical LMS 4.1 Product DVD with Printed PAK 3-7 Downloading LMS 4.1 Evaluation Software and Ordering Digital PAK 3-8 iv

5 Contents Ordering Physical LMS 4.1 Base Media Kit and Digital PAK 3-8 License Information 3-8 Available Licenses for LMS Major Upgrade Kit Licenses for LMS Upgrading to a Higher SKU on Soft Appliance Systems 3-12 License File 3-14 Transferring Files to Soft Appliance Server 3-16 Evaluation Mode 3-17 LMS 50 Devices Restricted License 3-17 Guidelines to Avoid Necessary Devices Being Moved to Suspended State 3-18 Device States After Backup and Restore in a LMS 50 SKU Server 3-18 NFR (Not For Resale) License 3-18 Installing the License File 3-19 Application Scaling Numbers 3-21 Concurrent Users Supported 3-24 CHAPTER 4 Setting Up Cisco Prime LMS in High Availability and Disaster Recovery Environment 4-1 High Availability and Disaster Recovery- An Overview 4-1 Veritas Components for Setting Up High Availability 4-4 Licensing Information 4-4 System Requirements for High Availability Implementation 4-5 Setting up LMS High Availability Environment on Windows 4-5 Installing Storage Foundation HA 5.1 on Windows 4-6 Creating Disk Groups and Volumes 4-7 Prerequisites for Configuring Disk Groups and Volumes 4-7 Creating Disk Groups on Primary Server 4-7 Creating Volumes on Primary Server 4-8 Creating Disk Groups and Volumes on Secondary Server 4-9 Installing LMS on Primary and Secondary Servers 4-10 Setting Up Veritas Volume Replication 4-10 Modes of Replication 4-10 Setting Up RDS, RVG and RLINK 4-12 Setting Casuser Permissions on cscopx Volume 4-13 Setting Up Veritas Volume Replication Without Clustering 4-14 Veritas Cluster Server Setup Tasks 4-15 Cluster Configuration for High Availability 4-15 Cluster Configuration for Disaster Recovery 4-20 Setting up LMS High Availability Environment on Solaris 4-23 Installing Storage Foundation HA 5.1 on Solaris 4-24 v

6 Contents Creating Disk Groups and Volumes on Solaris Servers 4-25 Prerequisites for Configuring Disk Groups and Volumes on Solaris 4-25 Creating Disk Groups on Primary Solaris Server 4-25 Creating Volumes on Primary Solaris Server 4-26 Creating Disk Groups and Volumes on Secondary Solaris Server 4-27 Installing LMS on Primary and Secondary Servers 4-28 Setting Up Veritas Volume Replication on Solaris Server 4-28 Setting Casuser Permissions on cscopx Volume on Solaris (If Required) 4-28 Setting Up Veritas Volume Replication Without Clustering On Solaris 4-29 Veritas Cluster Server Setup Tasks on Solaris 4-30 Cluster Configuration for High Availability on Solaris 4-30 Cluster Configuration for Disaster Recovery on Solaris 4-35 Moving LMS from non-ha to HA Environment 4-37 CHAPTER 5 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 5-2 Prerequisites for Implementing High Availability 5-2 Setting up High Availability using VMware HA 5-4 Creating a VMware HA Cluster 5-4 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.1 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-9 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 Deploying Template to New VM 5-12 vi

7 Contents CHAPTER 6 Performing Installation of Cisco Prime LMS Performing Installation of LMS Installing LMS Soft Appliance - OVA Image 6-2 Changing Server Configuration Details 6-12 Viewing System Details 6-15 Installing LMS 4.1 Soft Appliance - ISO Image 6-25 Installing LMS 4.1 Soft Appliance on VMware 6-25 Installing LMS 4.1 Soft Appliance on NCS and UCS Servers 6-28 Installing LMS 4.1 on Solaris 6-32 Installing LMS 4.1 on Solaris(Typical) 6-34 Installing LMS 4.1 on Solaris (Custom) 6-36 Installing LMS 4.1 on Windows 6-39 Installing LMS 4.1 on Windows (Typical) 6-41 Installing LMS 4.1 on Windows New (Custom) 6-42 Installing LMS 4.1 in Silent Mode 6-46 Upgrading to LMS Remote Upgrade to LMS Remote Upgrade to LMS 4.1 on Solaris 6-50 Remote Upgrade to LMS 4.1 on Windows 6-50 Verifying the Installation 6-51 Accessing LMS Server 6-53 Clearing Cache and Cookies 6-53 Internet Explorer Mozilla FireFox 4.0.x and 5.0.x 6-54 Enabling Loading of Scripts in Windows Logging into Cisco Prime LMS Server 6-55 Uninstalling LMS Before You Begin Uninstallation 6-56 Uninstalling LMS 4.1 on Solaris 6-56 Uninstalling LMS 4.1 on Windows 6-57 Re-installing LMS CHAPTER 7 Migrating Data to Cisco Prime LAN Management Solution Overview of Migration to LMS 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 vii

8 Contents 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 SP Migrating Data From LMS 3.2, LMS 3.2 SP1, LMS 4.0, or LMS Remote Migration From LMS 3.0 or LMS 3.0 December 2007 Update or LMS Migrating Data on Solaris 7-18 Migrating Data on Windows 7-19 Migrating Data on Soft Appliance 7-20 Guidelines to Post-Upgrade Activities 7-21 Guidelines for Fault Management Post-Upgrade Activities in LMS Configuring SNMP Trap Receiving and Forwarding 7-21 Guidelines for Common Services Post-Upgrade Activities 7-22 LMS 4.1 AAA Methods 7-22 CiscoWorks Local Mode 7-22 Resetting the Login Module 7-24 CHAPTER 8 Troubleshooting and FAQs 8-1 Checking Processes After Installation 8-1 Viewing and Changing Process Status 8-1 Contacting Cisco Technical Assistance Center (TAC) 8-3 Understanding Installation Error Messages 8-3 Troubleshooting Errors in Data Migration 8-14 Common Services Data Migration Errors 8-16 Inventory, Config and Image Management Data Migration Errors 8-17 Network Topology, Layer 2 Services and User Tracking Data Migration Errors 8-18 Fault Management Data Migration Errors 8-20 IPSLA Performance Management Data Migration Errors 8-21 Device Performance Management Data Migration Errors 8-22 Frequently Asked Questions 8-23 APPENDIX A User Inputs for Installation A-1 User Inputs for Typical Installation A-2 User Inputs for Custom Installation A-2 User Inputs for New Installation (Custom) A-3 viii

9 Contents User Inputs for Reinstallation (Custom) A-4 Password Information A-7 Password Rules for New Installation A-7 Password Rules for Re-installation A-7 Password Descriptions A-7 LMS Admin Password A-8 System Identity Account Password A-8 LMS Guest Password A-8 LMS Application Database Password A-8 Changing LMS Admin Password A-8 Changing casuser Password A-11 APPENDIX B User Tracking Utility B-1 Understanding UTU B-2 Hardware and Software Requirements for UTU 2.0 B-2 Downloading UTU 2.0 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 B-5 Configuring UTU 2.0 B-6 Searching for Users, Hosts or IP Phones B-8 Using Search Patterns in UTU 2.0 B-13 Uninstalling UTU 2.0 B-14 Upgrading to UTU 2.0 B-14 Re-installing UTU 2.0 B-14 APPENDIX C Installing the Remote Syslog Collector C-1 Verifying Remote Syslog Collector Server Requirement C-2 Installing the Remote Syslog Collector C-4 Installing on Solaris C-4 Installing on Windows C-5 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 ix

10 Contents Uninstallation on Solaris C-7 Uninstallation on Soft Appliance C-7 Understanding the Syslog Collector Properties File C-8 APPENDIX D Supported Server Time Zones and Offset Settings D-1 APPENDIX E Syntax and Usage for Backup Script E-1 APPENDIX F Syntax and Usage for Restore Script F-1 I NDEX x

11 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 ( This product includes cryptographic software written by Eric Young This product includes software written by Tim Hudson 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 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 ( 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: xi

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

13 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]. xiii

14 Notices xiv

15 Preface This guide helps you to install the Cisco Prime LAN Management Solution 4.1 software on both Windows, Solaris, and Soft Appliance. This guide also provides information on data migration from earlier versions of LMS to LMS 4.1. In addition, the guide provides troubleshooting suggestions that may be useful while you work on LMS. Note The term Virtual Appliance or Soft Appliance is used throughout LMS documentation, including Online Help. This preface details the product documents available for LMS, and demonstrates the styles and conventions used in this guide. This preface contains: Audience Document Conventions Product Documentation Obtaining Documentation, Obtaining Support, and Security Guidelines 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. xv

16 Document Conventions Preface Document Conventions Table 1 describes the conventions followed in this guide. Table 1 Conventions Used Item Commands and keywords Variables for which you supply values Displayed session and system information Information you enter Variables you enter Menu items and button names Selecting a menu item in paragraphs Selecting a menu item in tables Convention boldface font italic font screen font boldface screen font italic screen font boldface font Option > Network Preferences Option > Network Preferences Note Means reader take note. Notes contain helpful suggestions or references to material not covered in the publication. Caution Means reader be careful. In this situation, you might do something that could result in equipment damage or loss of data. xvi

17 Preface Product Documentation Product Documentation Note We sometimes update the printed and electronic documentation after original publication. Therefore, you should also review the documentation on Cisco.com for the latest updates. Table 2 describes the product documentation that is available. Table 2 Product Documentation Document Title Installing and Migrating to Cisco Prime LAN Management Solution 4.1 (this document) Context-sensitive online help Getting Started with Cisco Prime LAN Management Solution 4.1 Configuration Management with Cisco Prime LAN Management Solution 4.1 Monitoring and Troubleshooting with Cisco Prime LAN Management Solution 4.1 Administration of Cisco Prime LAN Management Solution 4.1 Available Formats PDF version part of Cisco Prime LMS 4.1 Product DVD. On Cisco.com at: oworks_lan_management_solution/4.1/install/gui de/install.html Select an option from the navigation tree, then click Help. PDF version part of Cisco Prime LMS 4.1 Product DVD. On Cisco.com at: oworks_lan_management_solution/4.1/user/guide /getting_started/lms41_getstart_guide.html PDF version part of Cisco Prime LMS 4.1 Product DVD. On Cisco.com at: oworks_lan_management_solution/4.1/user/guide /configuration/config.html PDF version part of Cisco Prime LMS 4.1 Product DVD. On Cisco.com at: oworks_lan_management_solution/4.1/user/guide /monitoring_troubleshooting/mnt_ug.html PDF version part of Cisco Prime LMS 4.1 Product DVD. On Cisco.com at: oworks_lan_management_solution/4.1/user/guide /admin/admin.html xvii

18 Product Documentation Preface Table 2 Product Documentation Document Title Technology Work Centers in Cisco Prime LAN Management Solution 4.1 Reports Management with Cisco Prime LAN Management Solution 4.1 Inventory Management with Cisco Prime LAN Management Solution 4.1 Navigation Guide for Cisco Prime LAN Management Solution 4.1 Open Database Schema Support in Cisco Prime LAN Management Solution 4.1 Release Notes for Cisco Prime LAN Management Solution 4.1 Available Formats PDF version part of Cisco Prime LMS 4.1 Product DVD. On Cisco.com at: oworks_lan_management_solution/4.1/user/guide /workcenters/wcug.html PDF version part of Cisco Prime LMS 4.1 Product DVD. On Cisco.com at: oworks_lan_management_solution/4.1/user/guide /reports/lms41_reports_guide.html PDF version part of Cisco Prime LMS 4.1 Product DVD. On Cisco.com at: oworks_lan_management_solution/4.1/user/guide /inventory/inventory.html PDF version part of Cisco Prime LMS 4.1 Product DVD. On Cisco.com at: oworks_lan_management_solution/4.1/navigatio n/guide/lms41_nav_guide.html PDF version part of Cisco Prime LMS 4.1 Product DVD. On Cisco.com at: oworks_lan_management_solution/4.1/database_ schema/dbviews_41.html PDF version part of Cisco Prime LMS 4.1 Product DVD. On Cisco.com at: oworks_lan_management_solution/4.1/release/no tes/lms41rel.html xviii

19 Preface Related Documentation for CiscoWorks LAN Management Solution 4.0 Table 2 Product Documentation Document Title Supported Devices Table for Cisco Prime LAN Management Solution 4.1 Documentation Roadmap for Cisco Prime LAN Management Solution 4.1 Available Formats PDF version part of Cisco Prime LMS 4.1 Product DVD. On Cisco.com at: oworks_lan_management_solution/4.1/device_su pport/table/lms41sdt.html 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 User Guide for Campus Manager 5.2 (With LMS 3.2) User Guide for Resource Manager Essentials 4.3 (With LMS 3.2) Available Formats PDF on: Product DVD LMS 3.2 Documentation DVD On Cisco.com at: mmon_services_software/3.3/user/guide/cs_33_ug.html PDF on: Product DVD LMS 3.2 Documentation DVD On Cisco.com at: mpus_manager/5.2/user/guide_pb/campushelp.html PDF on: Product DVD LMS 3.2 Documentation DVD On Cisco.com at: source_manager_essentials/4.3/user/guide/rme_ug.html xix

20 Related Documentation for CiscoWorks LAN Management Solution 4.0 Preface Table 3 Related Documentation (continued) Document Title User Guide for Device Fault Manager 3.2 (With LMS 3.2) User Guide for Internetwork Performance Monitor 4.2 (With LMS 3.2) Available Formats PDF on: Product DVD LMS 3.2 Documentation DVD On Cisco.com at: vice_fault_manager/3.2/user/guide/dfm32ug_book.html PDF on: Product DVD LMS 3.2 Documentation DVD On Cisco.com at: ernetwork_performance_monitor/4.2/user/guide/ipm4_2ug. html User Guide for CiscoView PDF on: Product DVD LMS 3.2 Documentation DVD On Cisco.com at: scoview/6.1.9/user/userguide/ugcv_619.html User Guide for CiscoWorks LMS PDF on: Portal 1.2 Product DVD User Guide for CiscoWorks Assistant 1.2 LMS 3.2 Documentation DVD On Cisco.com at: s_portal/1.2/user/guide/lmsportal_1.2.html PDF on: Product DVD LMS 3.2 Documentation DVD On Cisco.com at: sistant/1.2/user/guide/cwa12.html xx

21 Preface Obtaining Documentation, Obtaining Support, and Security Guidelines Table 3 Related Documentation (continued) Document Title User Guide for Health and Utilization Monitor 1.2 User Guide for CiscoWorks Integration Utility 1.7 Available Formats PDF on: Product DVD LMS 3.2 Documentation DVD On Cisco.com at: alth_and_utilization_monitor/1.2/user/guide_12/humug.ht ml PDF on: Product DVD LMS 3.2 Documentation DVD On Cisco.com at: 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 What s New in Cisco Product Documentation, which also lists all new and revised Cisco technical documentation, at: Subscribe to the What s 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. xxi

22 Obtaining Documentation, Obtaining Support, and Security Guidelines Preface xxii

23 CHAPTER 1 Overview of Cisco Prime LAN Management Solution 4.1 This chapter provides overview of LMS 4.1 and describes the composition of LAN Management Solution 4.0 on both Windows and Solaris systemsdata migration from earlier versions of LMS to LMS 4.1 This section contains: Product Overview Install and Upgrade Behavior New Features and Enhancements in LMS 4.1 Data Migration Overview Supported Network Management Systems Supported Devices Product Overview LMS 4.1 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.1. 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.1, see Migrating Data to Cisco Prime LAN Management Solution

24 Install and Upgrade Behavior Chapter 1 Overview of Cisco Prime LAN Management Solution 4.1 The licenses in LMS 4.1 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. Install and Upgrade Behavior LMS 4.1 provides a single install experience to you. It captures all required user inputs and then installs the applications. The evaluation version of HUM 1.2 is packaged with LMS 3.2, and is a part of the single installer. Since HUM has a separate license, during installation, you are prompted to first enter the license information for LMS 3.2 and then for HUM 1.2. For complete details on installation, see Performing Installation of Cisco Prime LMS 4.1. Note We recommend you not to install any other product in LMS server. If LMS and Antivirus softwares like MCAfee, Norton and so on, are installed in the same machine, the Antivirus should be configured to exclude the NMSROOT (LMS installation directory) from scanning. This is required because the third party software such as Sybase, included in LMS do disk intensive operations and spawn child processes based on the load. If the Antivirus is enabled this may not function as expected or may cause degradation in the overall performance of LMS. Note Daemon Manager will start slowly during reboot. This is because the antivirus that starts during reboot will cause delay to initiate Cisco Prime processes. If there are any Daemon Manager issues during reboot, then you should either disable the antivirus or restart the Daemon Manager after reboot. This section contains the following topics on Upgrade: 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.1 and then perform data migration. You can upgrade using either of these methods: Local upgrade Upgrading to the newer version of LMS on the same machine. 1-2

25 Chapter 1 Overview of Cisco Prime LAN Management Solution 4.1 Install and Upgrade Behavior Note LMS 4.1 supports local upgrade or direct inline upgrade only from LMS 4.0 and LMS Remote upgrade Installing LMS on a different machine and then restoring the data on that machine. You can do a remote upgrade to LMS 4.1 from LMS 4.0, LMS 4.0.1, LMS 3.2, and LMS 3.2 SP1. Note For LMS 3.1, LMS 3.0, LMS 3.0 December 2007 Update, LMS 2.6 and LMS 2.6 Service Pack (SP) 1, you have to do a remote upgrade to LMS 4.0 and then install LMS

26 Install and Upgrade Behavior Chapter 1 Overview of Cisco Prime LAN Management Solution 4.1 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 LMS Master LMS Slave Remote Migration Changes After restoring the LMS 3.2/3.2 SP1/4.0/4.0.1 backed up data in LMS 4.1, the DCR mode will be moved from Standalone to Master After taking backup from LMS 3.2/LMS 3.2 SP1, install LMS 4.1, the DCR mode will be in Standalone After restoring the LMS 3.2/3.2 SP/4.0/4.0.1 backed up data in LMS 4.1, 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 Grouping Services 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/3.2 SP1/4.0/4.0.1 server, after remote migration to LMS 4.1 the same settings will be retained. User-defined groups in Slave will not be shared or synchronized with Master in LMS 4.1 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. 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 User-defined groups can be created in LMS 4.1 Slave as against previous releases like LMS 3.2/3.2 SP1 and above. User-defined groups created in Master is shared in Slave server. Exporting of groups from Master and importing to Slave is possible System defined (device type) groups are separately created in Slave 1-4

27 Chapter 1 Overview of Cisco Prime LAN Management Solution 4.1 Install and Upgrade Behavior Table 1-2 describes the recommended sequence to upgrade, and migrate your data from earlier versions of LMS to LMS 4.1. Table 1-2 Upgrade and Data Migration Procedure Current LMS Version Type of Upgrade Procedure LMS 4.0 Remote migration 1. Back up the data in the old machine having LMS Install LMS Migrate your data to LMS 4.1 using the instructions explained in the section Remote Upgrade to LMS 4.1. Direct inline migration 1. Install LMS 4.1 over LMS 4.0. The data is automatically migrated during installation. LMS Remote migration 1. Back up the data in the old machine having LMS Install LMS Migrate your data to LMS 4.1 using the instructions explained in the section Remote Upgrade to LMS 4.1. Direct inline migration 1. Install LMS 4.1 over LMS The data is automatically migrated during installation. LMS 3.2, LMS 3.2 SP Remote migration 1. Back up the data in the old machine having LMS 3.2/3.2 SP. 2. Install LMS Migrate your data to LMS 4.1 using the instructions explained in the section Remote Upgrade to LMS

28 Install and Upgrade Behavior Chapter 1 Overview of Cisco Prime LAN Management Solution 4.1 Table 1-2 Upgrade and Data Migration Procedure Current LMS Version Type of Upgrade Procedure LMS 2.6, LMS 2.6 SP1, LMS 3.0, LMS 3.0 December 2007 update, LMS 3.1 LMS 2.2, LMS 2.5, LMS Remote migration Direct inline upgrade to LMS 4.1 is not supported. 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 4.0 > LMS 4.1 Remote migration Direct inline upgrade to LMS 4.1 is not supported. The suggested upgrade path is: LMS 2.2 / LMS 2.5 / LMS > LMS 2.6 > LMS 4.0 > LMS Back up the data in the old machine. 2. Install LMS 4.0 in the new machine. 3. Migrate the data to LMS 4.0. For more information, see n_management_solution/4.0/install/guide/dmg.html 4. Install LMS 4.1. From LMS 4.0 to LMS 4.1, you can perform direct inline or remote upgrade, click here for more details. 1. Back up the data in the old machine. 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 Readme for CiscoWorks LMS 2.6 Update on Windows Data Migration Guide for LAN Management Solution Install LMS 4.0 in the new machine. 4. Migrate the data to LMS n_management_solution/4.0/install/guide/dmg.html 5. Install LMS 4.1. From LMS 4.0 to LMS 4.1, you can perform direct inline or remote upgrade, click here for more details. 1-6

29 Chapter 1 Overview of Cisco Prime LAN Management Solution 4.1 New Features and Enhancements in LMS 4.1 New Features and Enhancements in LMS 4.1 This section explains the new features in the LMS 4.1. See the Online help of LMS 4.1 applications for a detailed explanation of the new features in LMS 4.1. This section contains the following: LMS 4.1 Soft Appliance Cross Platform Data Migration Support MACsec Provisioning Medianet Work Center Device Profiling using AutoSmartports Provisioning Configuration Center Smart Interactions TAC Service Requests Pane Enhancements in Template Center Combined UT Reports for all Endhost Types LLDP-based Discovery Support Search LMS Tasks IPSLA Video Operations Troubleshooting Workflow Changes Enhancements to Default Credential Set Policy Configuration Enhancements to Trigger Job Discovery Grouping Newly Discovered Devices Enhancements to Ping Sweep Module Faster Discovery Updates to DCR Third-Party Software and Tool Changes Note The supported screen resolution for LMS 4.1 is 1024x768 pixels. We recommend you not to use browser zoom in and zoom out features in LMS

30 New Features and Enhancements in LMS 4.1 Chapter 1 Overview of Cisco Prime LAN Management Solution 4.1 LMS 4.1 Soft Appliance LMS is available for customers on a Linux platform in the form of soft appliance. The soft appliance is built on Cisco standard CARS platform Version 2.0 with Redhat 5.4 (64 bit) as the underlying Linux distribution. Note The term Virtual Appliance or Soft Appliance is used throughout LMS documentation, including Online Help. All the packages are packaged using rpm packaging mechanism. Two new packages other than application packages, which will be created during runtime (build time). The two new packages are support and post process packages. Support package is installed first followed by all other application packages and finally post process package. Note When you use Cisco Prime LMS on a Soft Appliance, use FTP, SFTP, or SCP to transfer files from a client machine to the Soft Appliance or vice-versa. See Transferring Files to Soft Appliance Server for more information. Cross Platform Data Migration Support LMS 4.1 supports cross platform data migration from Solaris to Soft Appliance for the following LMS versions: LMS 3.2 SP1 LMS 4.0 LMS LMS 4.1 For more details on cross platform data migration, see Migrating Data on Soft Appliance. MACsec Provisioning Using the Identity Work Center, you can configure MACsec on supported devices. You can select Work Centers > Identity > Configure > Enable Interfaces and: Enable MACsec on supported devices. Select the policy to be applied for the session after the supplicant passes 802.1x authentication. Specify the MKA policy. For more information see Configuring Identity in Technology Work Centers in Cisco Prime LAN Management Solution 4.1. You can also select Configuration > Tools > Template Center, and enable or disable MACsec using the MACsec template. You can define rules to create port and module groups using MACsec status attribute (Admin > System > Group Management > Port and Module). For more information, see Defining Rule Expression for Port or Module Groups in Admin Online Help. 1-8

31 Chapter 1 Overview of Cisco Prime LAN Management Solution 4.1 New Features and Enhancements in LMS 4.1 Medianet Work Center LMS simplifies the deployment, and allows you to manage day-to-day configuration of the Cisco Medianet 2.2 solution. LMS provides workflows for setting up auto configuration, and for configuring location settings to aid the provisioning and tracking of Medianet endpoints such as digital media players (DMP) and IP video surveillance cameras (IPVSC). The LMS Medianet workflows enable the network operator to prepare the network for deployment and to ensure that appropriate location attributes are configured on the endpoints for tracking and monitoring purposes. The Medianet dashboard provides a quick snapshot of the operational status of Medianet endpoints. You can also view the configuration changes for all the Medianet devices after every inventory or configuration collection, and view faults that have occurred on devices, which have Medianet endpoints connected to them. 1-9

32 New Features and Enhancements in LMS 4.1 Chapter 1 Overview of Cisco Prime LAN Management Solution 4.1 You can also perform the following configurations on the Medianet devices: Auto Smartports Video Conferencing Video Transcoding RSVP PfR QoS Performance Monitoring IPSLA Video Operations Dynamic User Tracking For more information see Configuring Devices with Medianet Endpoints in Technology Work Centers in Cisco Prime LAN Management Solution 4.1. Device Profiling using AutoSmartports Provisioning Device Profiling is a new feature in LMS that provides an easy way for users to create triggers and dynamically configure the switch ports based on the device classification. You can create a specific trigger for a specific type of device. Device Profiling feature provides more granularity in device classification. The Device Profiling module has a rule-based device classification engine that can process attributes from various protocols. The minimum supported IOS version for Device Profiling is 15.01(SE). Configuration Center Configuration Center (Configuration > Configuration Center) is a launch point for all types of device or feature configurations supported in LMS. The links to the device or feature configurations are classified into configuration related to: Technologies and Services Validated Designs Configuration Tools For more information, see Configuration Center in the Configuration Management with Cisco Prime LAN Management Solution 4.1 User Guide. 1-10

33 Chapter 1 Overview of Cisco Prime LAN Management Solution 4.1 New Features and Enhancements in LMS 4.1 Smart Interactions Smart Interactions in LMS provides the following services: TAC Service Request Tool to create online Cisco Technical Assistance Center (TAC) service requests for support issues covered under the terms of your Cisco support contracts TAC Service Request Query Tool view the history and status of your existing or historical service requests and update the status of your open service requests Access to Cisco Search Community forums that lists the links of the cisco forums and posts related to the key words of the device type. TAC Service Requests Pane The TAC Service Requests Pane allows you to create online Cisco Technical Assistance Center (TAC) service requests for support issues covered under the terms of your Cisco support contracts. This tool does not currently provide access to warranty support. The TAC Service Request Query Tool allows you to view the history and status of your existing or historical service requests and update the status of your open service requests. This tool displays service request information for all open service requests, in addition to service requests that have been closed within the last 18 months. Enhancements in Template Center The Template Center in LMS provides you with a list of system-defined templates. These templates contain configuration commands that can be deployed on the devices in your network. These templates are deployed using Deploy Template jobs in LMS. The enhancements in Template Center in LMS 4.1 are: New Templates Many new templates like SBA templates, MACsec, Performance Monitoring and so on have been added in this release. For more information, see Accessing Template Center in the Configuration Management with Cisco Prime LAN Management Solution 4.1 User Guide. Grouping of templates The templates in Template Center are grouped into: Custom Templates Lists all the user-defined templates assigned to the current user. Cisco Best Practises Templates Lists all the system-defined templates Reference for each template You can add a link or specify a file that provides additional information about the template. The files have to be stored in the location NMSROOT\htdocs\config-templates-help. The reference files can have the following extensions: html, txt, csv, pdf, doc, docx, xls, xlsx. Tag templates You can specify tags for your template. These tags can be used as filters for the templates. You can specify multiple tags for a single template, each tag should be comma separated. 1-11

34 New Features and Enhancements in LMS 4.1 Chapter 1 Overview of Cisco Prime LAN Management Solution 4.1 Filter templates Template Center has two types of filters: Quick Filter Advanced Filter These filters provide various options for you to query and filter the required templates. Multi-line Command Support You can enter multi-line commands like, banner and crypto certificate commands, as a part of the templates in Template Center. The multi-line commands must be within the tag <MLTCMD> and </MLTCMD>. The commands within the MLTCMD tags are considered as a single command and will be downloaded as a single command onto the device These tags are case-sensitive and you must enter them only in uppercase. You cannot start this tag with a space. You can have a blank line within a multi-line command. For more information, see Accessing Template Center in the Configuration Management with Cisco Prime LAN Management Solution 4.1 User Guide. Combined UT Reports for all Endhost Types You can select endhost type as All (active, inactive and passive) in User Tracking Reports. You can choose from any of the layouts created for All Endhost type. It will launch the report which contains all endhosts (active, inactive and passive). LLDP-based Discovery Support Link Layer Discovery module uses entphysicaltable MIB to find its neighbor's IP Address. CDP devices are also considered as LLDP seed devices, when LLDP module is selected in discovery. Using LLDP, you can also discover the non-cisco devices in your network. Note LLDP will only support IPv4 devices. Search LMS Tasks LMS tasks can be identified using the search option in the Role Management Setup page (Admin > System > User Management > Role Management Setup). The search uses the task name and the task description to perform a complete search. The search results and All tabs contents are synchronized. Any selections made on search results will reflected in all tabs. IPSLA Video Operations The platform-independent IP SLA software feature in Cisco IOS software is incapable of generating the high data rates, 4 to 16 Mbps, which are typical of video applications. To eliminate the protocol overhead and the process scheduling delays that contribute to the limitations of the earlier IP SLAs software to generate video traffic, the Cisco IP SLAs Video Operation feature makes the traffic generation and transmission routines platform dependent. 1-12

35 Chapter 1 Overview of Cisco Prime LAN Management Solution 4.1 New Features and Enhancements in LMS 4.1 LMS IPSLA device management now supports new operation called Video and helps in analyzing the video traffic in the IP networks. Troubleshooting Workflow Changes The following are the changes in the Troubleshooting workflow in this release: Device Diagnostics and Network Connectivity workflows are renamed to Device Center and End Host Center respectively. More quick links of Tasks, Tools, and Reports are added to Troubleshooting workflows and they are displayed in an alphabetical order. Launching Topology window is now optional. When you launch the workflow, the device tab is launched first for Device Center and the end host tab is launched first for End Host Center. You can now enter all universal format of MAC addresses when you troubleshoot a device using MAC addresses. Enhancements to Default Credential Set Policy Configuration Earlier, the policy configuration of the default credential set policy is displayed as plain text with a delimiter # to split the Policy Type, Expression, and Credential Set. In this release, it is displayed in a tabular format eliminating the delimiter and retaining the other functionalities. Enhancements to Trigger Job Discovery In earlier releases of LMS, you have to trigger the job discovery explicitly. In earlier releases of LMS, you do not have the option to run immediate discovery for a scheduled job. In this release, a Start Discovery button is available in the Schedule Discovery page. You can select any job, edit the discovery settings if required, then click the Start Discovery button. When you click this button, it creates a new job id and runs it as immediate job. On completion of the discovery, the Discovery summary window is displayed to update the device list. Grouping Newly Discovered Devices Earlier, there was no option to add only the newly discovered devices into the specified group. In this release, following two new options are included to enhance this functionality: Devices newly discovered during last run checkbox Delete Devices from Group button If you select the Devices newly discovered during last run checkbox, only the newly discovered devices from the last discovery cycle will be added to the specified group. When you select this option and provide a new group name, if the discovery does not discover any new devices, then the group will not be created. Click Clear Device from Group button to select the list of devices to be deleted from the selected group. On selection of the devices click Delete button to remove it from the group. 1-13

36 Data Migration Overview Chapter 1 Overview of Cisco Prime LAN Management Solution 4.1 Enhancements to Ping Sweep Module In this release, ping sweep module supports both CIDR notation and subnet mask to find the range of IPAddresses. Faster Discovery Updates to DCR Earlier, on completion of the discovery, the entire discovered device list will be added to DCR. In this release, the discovered devices gets added to DCR every 2 mins. This enables faster discovery results to the end user. Device Newly Added to DCR and Device Updated to DCR will be updated on regular intervals, before completion of the entire discovery cycle. 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 WinPcap upgrade to Daylight Savings Timezone tool upgrade to Firefox 4.0.x and 5.0.x support on client systems Java Plug-in version 1.6.0_24 or later update versions only Apache upgrade to Java Runtime Environment (JRE) 1.6.0_24 Data Migration Overview You can freshly install LMS 4.1 and then perform remote data migration. LMS 4.1 supports direct inline upgrade from LMS 4.0 and LMS Data Migration to LMS 4.1 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 LMS 4.0 LMS 3.2 SP1 LMS

37 Chapter 1 Overview of Cisco Prime LAN Management Solution 4.1 Supported Network Management Systems For the following versions, you must migrate to LMS 4.0, and then install LMS 4.1: LMS 3.1 LMS 3.0 Dec 2007 update LMS 3.0 LMS 2.6 SP1 LMS 2.6 Note LMS 3.2 and earlier versions allow you to install partial applications in one server. For example, you can install CS and RME (part of earlier LMS versions) in one server and other LMS applications in another server. In this scenario you can perform data migration only from one server. You can migrate data either from RME server or from another LMS server. If the migration is performed from both the servers, then the last run migration will overwrite the previously migrated data. See Migrating Data to Cisco Prime LAN Management Solution 4.1 for more details on data migration. Supported Network Management Systems Table 1-3 lists the Network Management Systems (NMS) supported by Integration Utility 1.10, which is part of LMS 4.1. Note HPOV or NetView adapters are not supported for the Fault Management functionality in LMS 4.1 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) is shipped with LMS

38 Supported Network Management Systems Chapter 1 Overview of Cisco Prime LAN Management Solution 4.1 See User Guide for Integration Utility 1.10 on Cisco.com for instructions to use the Integration Utility. Table 1-3 Supported Network Management Systems 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 Note Both 32-bit and 64-bit Operating Systems are supported on the above versions. Windows Server 2008 R2 Standard Edition Windows Server 2008 R2 Enterprise Edition Note Only 64-bit Operating Systems are supported on the above versions. 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. 1-16

39 Chapter 1 Overview of Cisco Prime LAN Management Solution 4.1 Supported Network Management Systems Table 1-3 Supported Network Management Systems (continued) Network Management System HP OpenView 7.53, 7.51, 7.50 Supported Platforms Windows: Windows 2008 Server Standard Edition Release 1 with SP1 and SP2 Windows 2008 Enterprise Edition Release 1 with SP1 and SP2 Note Both 32-bit and 64-bit Operating Systems are supported on the above versions. Windows Server 2008 R2 Standard Edition Windows Server 2008 R2 Enterprise Edition Note Only 64-bit Operating Systems are supported on the above versions. NetView 7.1.4, Solaris Solaris 10 Only remote integration is supported for the above platforms. Windows: Windows 2008 Server Standard Edition Release 1 with SP1 and SP2 Windows 2008 Enterprise Edition Release 1 with SP1 and SP2 Note Both 32-bit and 64-bit Operating Systems are supported on the above platforms. Windows Server 2008 R2 Standard Edition Windows Server 2008 R2 Enterprise Edition Note Only 64-bit Operating Systems are supported on the above platforms. Only remote integration is supported for the above platforms. 1-17

40 Supported Devices Chapter 1 Overview of Cisco Prime LAN Management Solution 4.1 Supported Devices As additional device packages become available, you can download the Service Packs (formerly called IDUs) that contain them from Cisco.com. Registered Cisco.com users can access the latest Device Package Updates, and download the latest device updates for CiscoView, Topology Device Package Updates, Fault Management Device Package Updates and Inventory Config And Image Management Device Package Updates from: See the following documentation to know more information about supported devices: Supported Devices Table for CiscoWorks LAN Management Solution pport/table/lms40sdt.html User Guide for CiscoView 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: To see the list of installed application s device packages, select Admin > System > Software Center > Device Update from the LMS menu. To download Device Package Updates: Step 1 Step 2 Step 3 Go to 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. Select the Software Product Category as Network Management and Automation. Select Routing and Switching Management > Network Management Solutions > Ciscoworks LAN Management Solution 4.0 and later. Step 4 Select Cisco Prime LAN Management Solution 4.1. Step 5 Step 6 Step 7 Step 8 Step 9 Select the required feature specific update from the product tree. Select the required device package updates from the product software type. 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. Locate the device package update files which you want to download. 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.1 for more information about supported devices: pport/table/lms41sdt.html 1-18

41 CHAPTER 2 Prerequisites This chapter describes the factors that you must consider before installing LMS 4.1 on Soft Appliance, Windows and Solaris systems. Before you install LMS 4.1, 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. If you have configured Remote Syslog Collector (RSC) on a different server, you must upgrade RSC to RSC 5.1. 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. This chapter contains: System and Browser Requirements for Server and Client Terminal Server Support for Windows Server Solaris Patches LMS 4.1 Port Usage Important URLs Required Device Credentials for LMS Functionalities 2-1

42 System and Browser Requirements for Server and Client Chapter 2 Prerequisites System and Browser Requirements for Server and Client Before you begin to install LMS software, you must check if your system meets the recommended prerequisites. The recommended LMS 4.1 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.1 on Solaris, and Windows is: 60 GB free disk space for LMS 4.1 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.1 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.1 on for the 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.1 software on Solaris systems for different device SKUs. Table 2-5 lists the recommended server requirements for installing LMS 4.1 software on Solaris systems for Incremental Licenses. Table 2-6 lists the server requirements for installing LMS 4.1 on Windows systems for different device SKUs. Table 2-7 lists the recommended server requirements for installing LMS 4.1 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.1 is not supported on Windows 2000, Windows 2003, Solaris 8 and Solaris 9 servers. 2-2

43 Chapter 2 Prerequisites System and Browser Requirements for Server and Client Operating System Requirements The operating system requirements are listed in Table 2-1. This section contains: Storage Area Network Support Link Aggregation Support in Solaris 10 Table 2-1 Operating System Requirements Operating System Solaris Windows Requirements LMS 4.1 supports the following Solaris 10 releases: Solaris 10, 10/09 release Solaris 10, 05/09 release Solaris 10, 10/08 release Solaris 10, 05/08 release Solaris 10, 08/07 release Solaris 10, 11/06 release Solaris 10, 09/10 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.1 is installed on global zone of Solaris 10 Operating System by default. LMS 4.1 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.1 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. LMS 4.1 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 Both 32-bit and 64-bit Operating Systems are supported on the above versions. Windows Server 2008 R2 Standard Edition Windows Server 2008 R2 Enterprise Edition with SP1 Note Only 64-bit Operating Systems are supported on the above versions. 2-3

44 System and Browser Requirements for Server and Client Chapter 2 Prerequisites LMS 4.1 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 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 Devices license, in Windows and Solaris. They are supported in Soft Appliance. 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. This section contains: 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 Step 2 Configure the links (in this example, bge0 and bge1) with two different IP addresses in the same network. Check if both the IP addresses are reachable and you are able to telnet to the IPs. Get one public IP address in the same subnet. 2-4

45 Chapter 2 Prerequisites System and Browser Requirements for Server and Client Step 3 Step 4 Step 5 Step 6 Unplumb both the NICs using the command: 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 up. Add the IP address (Public IP) and hostname in the /etc/host file. If you cannot ping the IP address, you can set aggregation LACP mode active to off. dladm modify-aggr t l 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: 0:14:4f:90:1e:ba (auto) Device address speed duplex link state bge0 0:14:4f:90:1e:ba 1000Mbps full up attached bge1 0:14:4f:90:1e:bb 1000Mbps full up attached Note The state of the links should appear as attached in the output, else, the link aggregated server will not work when the NIC fails. Step 2 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-5

46 System and Browser Requirements for Server and Client Chapter 2 Prerequisites Server Requirements on Soft Appliance Systems To manage LMS 10,000 devices in LMS 4.1, 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 Recommended Requirement Virtualization Systems VMWare ESX server 4.1 VMware vsphere Hypervisor (ESXi server 4.1) Hard disk space 256 GB Memory and CPU 4 GB, 2 virtual CPU (< = 500 devices) Requirement 8GB, 4 virtual CPU (< = 1500 devices) Swap space Host CPU Core clock speed Minimum Virtual CPU Reservations Resource Memory Configuration 16GB, 8 virtual CPU ( > 1500 devices) 32 GB Minimum 2.26 GHz Number of recommended virtual CPUs x 2.26 GHz: 4520 MHz (< = 500 devices) 9040 MHz (< = 1500 devices) MHz ( > 1500 devices) 4096 MB (< = 500 devices) 8192 MB (< = 1500 devices) MB ( > 1500 devices) Note When you use incremental licenses for the LMS Soft Appliance, you must ensure that you configure the virtual CPUs mentioned in Table

47 Chapter 2 Prerequisites System and Browser Requirements for Server and Client Table 2-3 lists the Hardware Requirements of the NCS appliance for Soft Appliance (ISO image) Table 2-3 Hardware Requirements of the NCS appliance for Soft Appliance (ISO image) Component Recommended Requirement Processor clock speed 2.4 GHz Number of processors 2 Processor model Intel Xeon E5620 Processor number of cores 4 Cache 12 MB Hard disk interface SAS & SATA Chassis type Rack (1U) Maximum storage capacity 2 TB 2-7

48 System and Browser Requirements for Server and Client Chapter 2 Prerequisites Server Requirements on Solaris Systems Table 2-4 lists the server requirements for installing LMS 4.1 software on Solaris systems. Table 2-5 lists the recommended server requirements for installing LMS 4.1 software on Solaris systems for Incremental Licenses. Table 2-4 Recommended Server Hardware Requirements on Solaris Systems for Different Licenses Component LMS 50 LMS 100 Recommended Server System Requirement 1 CPU with dual core or 2 CPU with single core 4 GB RAM and 8 GB swap space, 60 GB free disk space, 32 or 64 bit OS 1 CPU with dual core or 2 CPU with single core 4 GB RAM and 8 GB swap space, 60 GB free disk space, 32 or 64 dual stack OS LMS 300 (Upgrade from previous version) 1 CPU with dual core or 2 CPU with single core 4 GB RAM and 8 GB swap space, 60 GB free disk space, 32 or 64 dual stack OS LMS CPUs with dual core or 4 CPU with single core 8 GB RAM and 16 GB swap space, 60 GB free disk space, 32 or 64 dual stack OS LMS 750 (Upgrade from previous version) 2 CPUs with dual core or 4 CPU with single core 8 GB RAM and 16 GB swap space, 60 GB free disk space, 64 bit OS LMS CPUs with dual core or 4 CPU with single core 8 GB RAM and 16 GB swap space, 60 GB free disk space, 64 bit OS LMS 1500 (Upgrade from previous version) LMS 2500 LMS 5,000 Note You can use one or more servers to manage upto 5000 devices. LMS 10,000 server: Configuration Functionality will support up to 10,000 devices 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 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 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 For LMS Server managing Configuration Functionality for upto 10,000 devices only: 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: 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 2-8

49 Chapter 2 Prerequisites System and Browser Requirements for Server and Client Configuration and Image Management Functionalities for upto 10,000 devices in one server. Note You must disable other functionalities in Config Server managing upto 10,000 devices. 2-9

50 System and Browser Requirements for Server and Client Chapter 2 Prerequisites Table 2-5 Recommended Server Hardware Requirements on Solaris Systems for Incremental Licenses License Upto LMS 300 Recommended Server System Requirement 1 CPU with dual core or 2 CPU with single core 4 GB RAM and 8 GB swap space, 60 GB free disk space, 32 or 64 bit OS > LMS to LMS K 2 CPUs with dual core or 4 CPU with single core 8 GB RAM and 16 GB swap space,32/64 dual stack OS > LMS K to LMS K 2 CPUs with quad core or 4 CPU with dual core 16 GB RAM and 32 GB swap space,64 bit OS > LMS K to LMS4.1-5 K 2 CPUs with 8 core or 4 CPU with quad core 16 GB RAM and 32 GB swap space,64 bit OS The following processors are supported on a Solaris system: UltraSPARC IIIi processor UltraSPARC IV processor UltraSPARC IV+ processor UltraSPARC T1 processor UltraSPARC T2 processor UltraSPARC T2+ processor SPARC64 VI processor SPARC64 VII processor Note Minimum processor speed must be 1.35 Ghz or higher See Solaris Patches for information on required and recommended server patches on Solaris systems. 2-10

51 Chapter 2 Prerequisites System and Browser Requirements for Server and Client Server Requirements on Windows Systems Table 2-6 lists the server requirements for installing LMS 4.1 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.1, 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.1? Table 2-6 Recommended Server Hardware Requirements on Windows Systems for Different Licenses Component LMS 50 LMS 100 Recommended Server System Requirement 1 CPU with dual core or 2 CPU with single core 4 GB RAM and 8 GB swap space, 60 GB free disk space, 32 or 64 bit OS 1 CPU with dual core or 2 CPU with single core 4 GB RAM and 8 GB swap space, 60 GB free disk space, 32 or 64 dual stack OS LMS 300 (Upgrade from previous version) 1 CPU with dual core or 2 CPU with single core 4 GB RAM and 8 GB swap space, 60 GB free disk space, 32 or 64 dual stack OS LMS CPUs with dual core or 4 CPU with single core 8 GB RAM and 16 GB swap space, 60 GB free disk space, 32 or 64 dual stack OS LMS 750 (Upgrade from previous version) 2 CPUs with dual core or 4 CPU with single core 8 GB RAM and 16 GB swap space, 60 GB free disk space, 64 bit OS LMS CPUs with dual core or 4 CPU with single core 8 GB RAM and 16 GB swap space, 60 GB free disk space, 64 bit OS LMS 1500 (Upgrade from previous version) LMS 2500 LMS 5,000 Note You can use one or more servers to manage upto 5000 devices. LMS 10,000 server: Configuration Functionality will support up to 10,000 devices 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 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 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 For LMS Server managing Configuration Functionality for upto 10,000 devices only: 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 server to manage up to 10,000 devices for all functionalities in your network. You must manage: 2-11

52 System and Browser Requirements for Server and Client Chapter 2 Prerequisites 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. Note 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 Recommended Server System Requirement 1 CPU with dual core or 2 CPU with single core 4 GB RAM and 8 GB swap space, 60 GB free disk space, 32 or 64 bit OS > LMS4 300 to LMS 1.5K 2 CPUs with dual core or 4 CPU with single core 8 GB RAM and 16 GB swap space,32/64 dual stack OS > 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 2 CPUs with 8 core or 4 CPU with quad core 16 GB RAM and 32 GB swap space,64 bit OS Note If you want to configure swap space in a 32-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. Table 2-8 Recommended Server Hardware Requirements on Windows Systems with HUM Component LMS Bundle Hardware Configuration HUM 50 + LMS 300 HUM LMS 1500 Standalone Hardware Configuration HUM 50 HUM 300 HUM 1000 Recommended Server System Requirement One CPU with 2 GB RAM memory and 4 GB swap space. 2 CPUs with 4 GB RAM memory and 8 GB swap space. One CPU with 2 GB RAM memory and 4 GB swap space. One CPU with 2 GB RAM memory and 4 GB swap space. Two CPUs with 4 GB RAM memory and 8 GB swap space. 2-12

53 Chapter 2 Prerequisites System and Browser Requirements for Server and Client The following processors are supported on a Windows system: Intel processors Intel Xeon processor Intel Core Duo processor T T2300 Quad Core Intel Xeon Intel Itanium Processor (32 bit OS only, 1.7 Ghz or higher CPU) Intel-VT processors (VMware Optimized hardware) Intel Xeon processor 5400 series Intel Xeon processor 5300 series Intel Xeon processor 7300 series Intel Xeon processor 5500 series Intel Xeon processor 5600 series AMD processors AMD Opteron Processor AMD Athlon 64 FX Processor AMD Athlon 64 X2 AMD -V Note 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.1 runs on VMware systems. See Operating System Requirements for a list of virtualization systems supported. The server requirements on VMware servers remains the same as the server requirements on Windows systems. However, the following hardware are optimized to run in virtualized environment: Intel-VT processors Intel vpro processor technology Intel Xeon processor 5000 sequence Intel Xeon processor 7000 sequence Intel Xeon processor 3000 sequence Intel Itanium Processor 9000 sequence (only 32-bit is supported) AMD-V IBM X3550 M3 2-13

54 System and Browser Requirements for Server and Client Chapter 2 Prerequisites Intel Xeon Processor 5600 series Unified Computing System (UCS) Support LMS 4.1 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 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 System Requirements on Client Systems The following table lists the client system requirements for all platforms: Table 2-9 Component Disk space Memory Requirements Hardware and software Browser Requirements Recommended Client Hardware and Software Requirements Recommended Client System Requirement 60 GB and above 2 GB RAM At least single CPU@ 2.4 GHZ or higher with one of the following operating systems: Windows 2003 Standard and Enterprise Editions with Service Pack 2 (32 and 64 bit) Windows 2003 Standard R2 and Enterprise R2 Editions with Service Pack 2 (32 and 64 bit) Windows XP with Service Pack 3 Windows 2008 Standard and Enterprise with Service Pack 1 and Service Pack 2 (32 and 64 bit) Windows 2008 R2 Standard and Enterprise with Service Pack 1 and Service Pack 2 (32 and 64 bit) Windows 7 (32 and 64 bit) Internet Explorer 8.x Standards Mode (Press F12 and select Standards Mode) Firefox 4.0.x and 5.0.x for Windows Note Only 32-bit IE and FF browsers are supported 2-14

55 Chapter 2 Prerequisites Terminal Server Support for Windows Server Table 2-9 Java Runtime Environment (JRE) Requirements Adobe Flash Player 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. 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.1 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. 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. Terminal Server Support for Windows Server. You can install LMS 4.1 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. This section contains: Enabling and Disabling Terminal Services on Windows 2008 Server 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 Terminal Server Remote Desktop Administration Features Remote access and virtual system. Each client has its own virtual OS environment. Remote access only. All clients use the same OS. Enabling and Disabling Terminal Services on Windows 2008 Server To enable/ disable Terminal Server, use the Terminal Services Manager tool. To enable/ disable Remote Desktop: Step 1 Step 2 Go to Control Panel > System. Click Remote Settings under Tasks > Remote 2-15

56 Terminal Server Support for Windows Server Chapter 2 Prerequisites Step 3 Select the Allow connections from computer running any version if Remote Desktop option. 2-16

57 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 Step 2 Step 3 Step 4 Step 5 Step 6 Go to Start > Settings > Control Panel > Administrative tools > Local Security Policy. The Local Security Policy window appears. Click Local Polices > Security Options. Select System cryptography: Use FIPS compliant algorithms for encryption, hashing, and signing. Right-click the selected policy and click Properties. Select Enabled or Disabled to enable or disable FIPS compliant algorithms. Click Apply. You must reboot the server for the changes to take effect. Solaris Patches LMS 4.1 is installed on global zone of Solaris 10 Operating System by default. Installation of LMS 4.1 in whole-root non-global zone in Solaris 10 is supported. The Solaris system requires the following patches to be installed on the server: Required and Recommended Solaris Patches Cluster Patches Required and Recommended Solaris 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. 2-17

58 Solaris Patches Chapter 2 Prerequisites For more information, see Table 2-11 Solaris Patches Operating System Required and Recommended Solaris Patches Solaris 10 Required Server Patches are and 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... Required Server patches Required Client patches Message 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]: 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 download and install the latest required and recommended patches from before you run LMS

59 Chapter 2 Prerequisites LMS 4.1 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 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 WARNING: Otherwise, some features of the LMS applications will not function properly. Do you want to continue the installation? (y/n) [y]: LMS 4.1 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: Protocol Port Number Service Name Functionality TCP 49 TACACS+ and ACS Common Services Configuration and Software Image Management TCP 25 Simple Mail Transfer Protocol (SMTP) Network Topology, Layer 2 Services and User Tracking Fault Management Common Services (PSU) Inventory, Config and Image Management TCP 22 Secure Shell (SSH) Common Services, Network Topology, Layer 2 Services and User Tracking Inventory, Config and Image Management Direction (of Establishment) of Connection Server to ACS Server to SMTP Server Server to Device 2-19

60 LMS 4.1 Port Usage Chapter 2 Prerequisites Port Number Protocol Service Name Functionality TCP 23 Telnet Common Services UDP 69 Trivial File Transfer Protocol (TFTP) UDP 161 Simple Network Management Protocol (SNMP) Network Topology, Layer 2 Services and User Tracking Inventory, Config and Image Management Common Services Inventory, Config and Image Management Common Services CiscoView Inventory, Config and Image Management Network Topology, Layer 2 Services and User Tracking Fault Management IPSLA Performance Management Device Performance Management Server to Device Server to Device Device to Server Server to Device Device to Server TCP 514 Remote Copy Protocol Common Services Server to Device UDP 162 SNMP Traps (Standard Port) Network Topology, Layer 2 Services and User Tracking Fault Management UDP 514 Syslog Common Services UDP Trap Listener to MAC Notification Traps UDP 9000 Trap receiving (if port 162 is occupied) Inventory, Config & Image Management Network Topology, Layer 2 Services and User Tracking Fault Management UDP UT Host acquisition Network Topology, Layer 2 Services and User Tracking TCP 443 LMS HTTP server in Common Services SSL mode Direction (of Establishment) of Connection Device to Server Device to Server Device to Server Device to Server End host to Server Client to Server Server Internal 2-20

61 Chapter 2 Prerequisites LMS 4.1 Port Usage Port Number Protocol Service Name Functionality TCP 1741 LMS HTTP Protocol Common Services CiscoView Network Topology, Layer 2 Services and User Tracking Inventory, Config & Image Management Fault Management IPSLA Performance Management Client to Server TCP OSAGENT Common Services Client to Server TCP 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 Fault Management Server Internal (DFM Broker) TCP 9007 Tomcat shutdown Common Services Server Internal TCP 9009 Ajp13 connector used Common Services Server Internal by Tomcat UDP 9020 Trap Receiving Fault Management Server Internal UDP Lock port for ANI Server singlet on check Network Topology, Layer 2 Services and User Tracking Server Internal TCP Log server Fault Management Server Internal TCP CSTM ports used by CS applications, such as Grouping Services, Device and Credential Repository (DCR) Common Services Direction (of Establishment) of Connection Server Internal TCP LicenseServer Common Services Server Internal TCP ANIServer Network Topology, Layer 2 Client to Server Services and User Tracking TCP LMS Daemon Manager - Tool for Server Processes Common Services Server Internal TCP ANI HTTP Server Common Services Server Internal 2-21

62 LMS 4.1 Port Usage Chapter 2 Prerequisites Port Number Protocol Service Name Functionality UDP Event Services Software (ESS) (Alternate port is 44350/udp) Common Services TCP Event Services Software (ESS) Listening (Alternate port is 44351/tcp) TCP ESS Routing (Alternate port is 44352/tcp) TCP Common Services Database TCP Inventory, Config and Image Management Database Common Services Common Services Common Services Inventory, Config and Image Management Server Internal Server Internal Server Internal Server Internal Server Internal TCP ANIDbEngine Network Topology, Layer 2 Server Internal Services and User Tracking TCP Fault History Database Fault Management Server Internal TCP Inventory Service Database Fault Management Server Internal TCP Device Performance Management Database TCP IPSLA Performance Management Database TCP Event Promulgation Module Database TCP TCP TCP Device Performance Management IPSLA Performance Management Fault Management CSTM Ports Fault Management CSTM Port CSTM Port Device Performance Management Inventory, Config and Image Management Inventory, Config and Image Management TCP SOAPMonitor Inventory, Config and Image Management TCP TCP CSTM Port Network Topology, Layer 2 Services and User Tracking Direction (of Establishment) of Connection Server Internal Server Internal Server Internal Server Internal Server Internal Server Internal Server Internal Server Internal CSTM Port VRF Lite Server Internal 1. Windows Firewall blocks the port 1431 (for SNMP Traps), by default. You should free up this port for the SNMP traps to be allowed to the server from the device. 2-22

63 Chapter 2 Prerequisites Important URLs 2. Windows Firewall blocks the port (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 for more details on administering Windows Firewall and on configuring ICMP settings in Windows Firewall. 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. Important URLs The following URLs are most commonly used in LMS and should be added in the proxy server: General Device update/software update/point Patch update IOS image download Smart Services SASI_SERVER RSR_SERVER CSC_SERVER CCOLOGINURL CCOLOGOUTURL CASE_QUERY_URL do?casetype=ciscoservicerequest LOGIN_REDIRECT_URL com CSC_REDIRECT_URL

64 Required Device Credentials for LMS Functionalities Chapter 2 Prerequisites Required Device Credentials for LMS Functionalities 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 Services and User Tracking CiscoView Not required Not required Required Required Fault Management Not required Not required Required Not required IPSLA Performance Not required Not required Required Required Management Device Performance Not required Not required Required Not required Management Inventory Not required Not required Required Not required Configuration Management Required Required Required Not required (Telnet) Configuration Management 1 (TFTP) 2 Not required Not required Required Required NetConfig Required Required Required Required Config Editor Required Required Required Required NetShow Required Required Required Not required Software Management Required 3 Required 3 Required Required Port and Module Required Required Required Required Configuration 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 Required 4 1. Configuration download also uses TFTP. Hence, SNMP Read/Write credentials are required. 2. The file vlan.dat can be fetched only if the Telnet password and Enable password are supplied. 3. Required in the case of a few devices like PIX devices, Cisco 2950 series switches. 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-24

65 Chapter 2 Prerequisites Required Device Credentials for LMS Functionalities 2-25

66 Required Device Credentials for LMS Functionalities Chapter 2 Prerequisites 2-26

67 CHAPTER 3 Preparing to Install Cisco Prime LAN Management Solution 4.1 This chapter lists the necessary information that prepares you to perform an installation of LMS 4.1 on both Soft Appliance, Windows and Solaris systems. This chapter contains: Terms and Definitions Used in LMS Installation Framework Before You Begin Installation Licensing Your Product Application Scaling Numbers Terms and Definitions Used in LMS Installation Framework This section captures the terms and definitions that are used while installing LMS 4.1 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.1, the LMS Application Database Password is requested during Custom installation. This database password is used internally by the LMS software to communicate with the respective application s 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. Note While installing the software in Custom mode alone you will be prompted to enter the LMS Application database password. In the Typical mode, this password is randomly generated. 3-1

68 Terms and Definitions Used in LMS Installation Framework Chapter 3 Preparing to Install Cisco Prime LAN Management Solution 4.1 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 in both Typical and Custom modes of installation. System Identity Account Password Password that is used in a multi-server environment. Communication among multiple LMS Servers is enabled by a trust model addressed by certificates and shared secrets. System Identity setup helps you to create a trust user among servers that are part of a multi-server setup. This user enables communication among servers that are part of a domain. You must configure all the LMS servers that are part of your multi-server setup with the same system identity account password. While entering the System Identity Account Passwords, use a minimum of five characters. You are prompted to enter this password in both Typical and Custom modes of installation. To change the System Identity Account password, select Admin > Trust Management > Multi Server > System Identity Setup. LMS Guest Password This is used while logging into the LMS server as a guest user. Use a minimum of five characters. You are prompted to enter this password in the Custom mode of installation. In the Typical mode, this password is randomly generated. Self Signed Certificate LMS allows you to create security certificates to enable SSL communication between your client browser and management server. Self Signed Certificates are valid for five years from the date of creation. When the certificate expires, the browser prompts you to install the certificate again from the server where you have installed LMS. For more information on Self Signed Certificates, see User Inputs for Custom Installation. In the Typical mode, this certificate is automatically generated. For more information on passwords, see Password Rules for New Installation SMTP Server System-wide name of the SMTP server used by LMS 4.1 to deliver reports. The default server name is localhost. You are prompted to enter this server detail only in the Custom mode of installation. In the Typical mode, after the installation you can configure SMTP by selecting Admin > System > System Preferences from the LMS 4.1 UI. Port The default http port for the LMS server is You are prompted to configure the port number of the http port during the installation of LMS, if the port is in used state. The default https port for the LMS server is 443. You are prompted to configure the port number of the https port during the installation of LMS, if the port is in used state. 3-2

69 Chapter 3 Preparing to Install Cisco Prime LAN Management Solution 4.1 Before You Begin Installation 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. You can also change the System Identity Account password, select Admin > Trust Management > Multi Server > System Identity Setup. To change the Guest password, select Admin > System > User Management > Local User Setup. To change the Cisco.com credentials, select Admin > System > Cisco.com Settings. Before You Begin Installation This section contains the following important information that you should read before you begin installation: Installation Notes Installation Notes (For Solaris Only) Installation Notes (For Windows Only) Installation Notes (For Soft Appliance 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 Integration Utility You can find this document on Cisco.com, in both HTML and PDF form. Disable any popup blocker utility that is installed on your client system before launching LMS. LMS 4.1 is installed in the default directories: On Solaris and Soft Appliance: /opt/cscopx On Windows, 64 bit: SystemDrive:\Program Files<x86>\CSCOpx On Windows, 32 bit: SystemDrive:\Program Files\CSCOpx Where, SystemDrive is the Windows operating system installed directory. If you select another directory during installation, the application is installed in that directory. 3-3

70 Before You Begin Installation Chapter 3 Preparing to Install Cisco Prime LAN Management Solution 4.1 The destination folder should not contain the following special characters: On Solaris and Soft # $ % ^ & * ( ) + } { " : [ ] ; '? < >,. ` = ~ On # $ % ^ & * ( ) + } { " [ ] ; ' /? < >,. ` = 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.1 installation Where YYYYMMDD denotes the year, month and date of installation and hhmmss denotes the hours, minutes and seconds of installation. For example: /var/tmp/cisco_prime_install_ _ 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.1, 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_ _ 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 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. 3-4

71 Chapter 3 Preparing to Install Cisco Prime LAN Management Solution 4.1 Before You Begin Installation Installation Notes (For Solaris Only) On Solaris, if you select an installation directory other than the default, the /opt/cscopx directory is created as a link to the directory you selected. Warning If you remove this link after installation, the product will malfunction. We recommend that you run the installation from a local 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. 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. You must restart your system after you install LMS 4.1. Installation Notes (For Windows Only) You can install LMS 4.1 on a system with Terminal Services enabled in Remote Administration mode. However, installation of LMS 4.1 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 for HTTPS to avoid this conflict. If you are running any virus scanner while installing LMS 4.1, 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.1. The installer will not copy the database to the appropriate location if you do not disable Windows Defender. 3-5

72 Licensing Your Product Chapter 3 Preparing to Install Cisco Prime LAN Management Solution 4.1 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.1. 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.1 to avoid any system instability on a Windows Operating System. Installation Notes (For Soft Appliance Only) 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. Licensing Your Product The LMS 4.1 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. This section contains: 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. The following are the options available to you to order the LMS 4.1 software and Product Authorization Key (PAK): Ordering Physical LMS 4.1 Product DVD with Printed PAK 3-6

73 Chapter 3 Preparing to Install Cisco Prime LAN Management Solution 4.1 Licensing Your Product Downloading LMS 4.1 Evaluation Software and Ordering Digital PAK Ordering Physical LMS 4.1 Base Media Kit and Digital PAK Ordering Physical LMS 4.1 Product DVD with Printed PAK This is the traditional method of purchasing the product through Cisco Direct and Channel Sales representatives. You will receive a kit with product DVDs and a software claim certificate paper, when you opt to select this delivery method. The software claim certificate paper contains the Product Authorization Key (PAK) printed on it. Note The product DVD kit for LMS 500, LMS 1000, LMS 2500, LMS 5,000 and LMS 10,000 license types, contains a DVD for Windows Operating System, a DVD for Solaris Operating Systems. 3-7

74 Licensing Your Product Chapter 3 Preparing to Install Cisco Prime LAN Management Solution 4.1 Downloading LMS 4.1 Evaluation Software and Ordering Digital PAK To ensure the faster delivery of the product, this option has been introduced. With this option, you can now: Download the LMS 4.1 Evaluation software from The Evaluation software functions for 90 days and will expire after that. The product will not work until you provide a valid license file. See Evaluation Mode for more information. Order a digital PAK ID using the Cisco s edelivery application. You must be a registered Cisco.com user to use the edelivery application. To request a Cisco.com profile go to: After you have ordered the product in edelivery and the electronic fulfillment is complete, you will receive the electronic software claim certificate with the digital PAK. Ordering Physical LMS 4.1 Base Media Kit and Digital PAK A physical LMS base media kit without PAK ID is offered to you in this method of ordering. You can opt to order the LMS base media kit if you need a physical DVD or if you are restricted to download the software from the Evaluation Software Download site. Similar to the Evaluation software, the base media kit, when installed, will function for 90-days. Then the software require the installation of a permanent serial license key to operate beyond that point. You must also order for a digital PAK ID using the Cisco s edelivery application. You must be a registered Cisco.com user to use the edelivery application. To request a Cisco.com profile go to: After you have ordered the product in edelivery and the electronic fulfillment is complete, you will receive the electronic software claim certificate with the digital Product Authorization Key (PAK). License Information The licenses in LMS 4.1 are device based. For 10,000 device licenses, applying a single serial license key to more than one server is supported. Please see the SUPPLEMENTAL LICENSE AGREEMENT section for more details. For IPSLA Performance Management alone, besides the number of devices, the number of collectors you create depends on the license and hardware requirements. This section explains about the various licenses available for LMS 4.1. 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

75 Chapter 3 Preparing to Install Cisco Prime LAN Management Solution 4.1 Licensing Your Product This section contains: Available Licenses for LMS 4.1 Available Licenses for LMS 4.1 Major Upgrade Kit Licenses for LMS 4.1 Upgrading to a Higher SKU on Soft Appliance Systems See Application Scaling Numbers for further deployment related information. This section contains: Licensing SKUs for Traditional Ordering Licensing SKUs for Traditional Ordering Licensing SKUs for Ordering Base Media Kit Without PAKs Licensing SKUs for Ordering Digital PAKs The following are the available licenses (SKUs) for LMS 4.1 users, who have opted to order the physical Product DVD kit (Physical software and Software claim certificate paper with PAK): Available Licenses (SKU) in LMS 4.1 Permitted number of Devices in LMS 4.1 LMS K9 50 devices LMS K9 100 devices LMS K9 500 devices LMS-4.1-1K-K devices LMS K-K9 2,500 devices LMS-4.1-5K-K9 5,000 devices LMS K-K9 10,000 devices Licensing Incremental SKUs Incremental SKUs are introduced in LMS 4.1. You must have the LMS 4.1 base media kit to order the incremental licenses. The following are the available incremental licenses (SKUs) for LMS 4.1 users, who have opted to order the physical Product DVD kit (Physical software and Software claim certificate paper with PAK): Available Licenses (SKU) in LMS 4.1 Permitted number of Devices in LMS 4.1 L-LMS ADD Incremental license for 50 devices L-LMS ADD Incremental license for 100 devices L-LMS ADD Incremental license for 500 devices L-LMS-4.1-1K-ADD Incremental license for 1000 devices L-LMS K-ADD Incremental license for 2,500 devices L-LMS-4.1-5K-ADD Incremental license for 5,000 devices 3-9

76 Licensing Your Product Chapter 3 Preparing to Install Cisco Prime LAN Management Solution 4.1 Licensing SKUs for Ordering Base Media Kit Without PAKs If you want to order for the LMS 4.1 base media kit without any PAK, you must use the following product number: Base Media Kit Product Number Permitted number of Devices LMS 4.1 LMS-4.1-SW-K9 100 devices Note This is the default number of devices allowed to manage in the evaluation version of the product. Licensing SKUs for Ordering Digital PAKs : The following are the available licenses (SKUs) for LMS 4.1 users, who have opted to receive the Digital PAK through edelivery: Available Licenses (SKU) in LMS 4.1 Permitted number of Devices in LMS 4.1 R-LMS K9 50 devices R-LMS K9 100 devices R-LMS K9 500 devices R-LMS-4.1-1K-K devices R-LMS K-K9 2,500 devices R-LMS-4.1-5K-K9 5,000 devices R-LMS K-K9 10,000 devices Major Upgrade Kit Licenses for LMS 4.1 To upgrade from LMS 3.x or LMS 4.0.x, you can order LMS 4.1 through Cisco Sales channels. Read the information in Understanding Product Ordering Options and Product Authorization Key to understand about the various product ordering options for LMS 4.1. This section explains: Licenses SKUs For Traditional Ordering of LMS 4.1 Major Upgrade Kit Licenses SKUs For Ordering LMS 4.1 Major Upgrade Kit Digital PAK Licenses SKUs For Ordering LMS 4.1 Minor Upgrade Kit Licenses SKUs For Ordering LMS 4.1 Minor Upgrade Kit Digital PAK Note If you are an existing LMS 3.x or LMS 4.0.x user and if you want to upgrade to LMS or 2500 device licenses, we recommend you to: 1. Order the LMS 4.1 Major Upgrade kit for the existing LMS 2.x or LMS 3.x SKU that you are using, and upgrade to LMS Order a LMS or 2500 Device-Level Conversion License to convert from your existing device license to LMS 750 or 2500 SKU. 3-10

77 Chapter 3 Preparing to Install Cisco Prime LAN Management Solution 4.1 Licensing Your Product Licenses SKUs For Traditional Ordering of LMS 4.1 Major Upgrade Kit If you have opted to order the physical Product DVD kit (Physical software and Software claim certificate paper with PAK), you must use the following SKUs: Licenses (SKU) to upgrade from LMS 2.x, 3.x LMS UP-K9 LMS UP-K9 LMS41-1.5K-UP-K9 LMS41-5K-UP-K9 LMS41-10K-UP-K9 Permitted Number of Devices LMS Device Restricted Upgrade for LMS 2.x, 3.x users LMS Device Restricted Upgrade for LMS 2.x, 3.x users LMS 4.1 1,500 Device Restricted Upgrade for LMS 2.x, 3.x users LMS 4.1 5,000 Device Restricted Upgrade for LMS 2.x, 3.x users LMS ,000 Device Restricted Upgrade for LMS 2.x, 3.x users Licenses SKUs For Ordering LMS 4.1 Major Upgrade Kit Digital PAK If you have opted to order the physical Base Media Kit or download the evaluation software, you must use the following SKUs to order the Digital PAK through edelivery: Licenses (SKU) to upgrade from LMS 2.x, 3.x R-LMS UP-K9 R-LMS UP-K9 R-LMS41-1.5K-UP-K9 R-LMS41-5K-UP-K9 R-LMS41-10K-UP-K9 Permitted Number of Devices LMS Device Restricted Upgrade for LMS 2.x, 3.x users LMS Device Restricted Upgrade for LMS 2.x, 3.x users LMS 4.1 1,500 Device Restricted Upgrade for LMS 2.x, 3.x users LMS 4.1 5,000 Device Restricted Upgrade for LMS 2.x, 3.x users LMS ,000 Device Restricted Upgrade for LMS 2.x, 3.x users Licenses SKUs For Ordering LMS 4.1 Minor Upgrade Kit If you have opted to order the physical Product DVD kit (Physical software and Software claim certificate paper with PAK), you must use the following SKUs: Licenses (SKU) to upgrade from LMS 4.0 LMS41-50-MR-K9 LMS MR-K9 LMS MR-K9 LMS MR-K9 LMS41-1.5K-MR-K9 LMS41-2.5K-MR-K9 LMS41-5K-MR-K9 LMS41-10K-MR-K9 Permitted Number of Devices LMS Device Upgrade for LMS 4.0 users LMS Device Upgrade for LMS 4.0 users LMS Device Upgrade for LMS 4.0 users LMS Device Upgrade for LMS 4.0 users LMS 4.1 1,500 Device Upgrade for LMS 4.0 users LMS 4.1 2,500 Device Upgrade for LMS 4.0 users LMS Device Upgrade for LMS 4.0 users LMS ,000 Device Upgrade for LMS 4.0 users 3-11

78 Licensing Your Product Chapter 3 Preparing to Install Cisco Prime LAN Management Solution 4.1 Licenses SKUs For Ordering LMS 4.1 Minor Upgrade Kit Digital PAK If you have opted to order the physical Base Media Kit or download the evaluation software, you must use the following SKUs to order the Digital PAK through edelivery: Licenses (SKU) to upgrade from LMS 4.0 R-LMS41-50-MR-K9 R-LMS MR-K9 R-LMS MR-K9 R-LMS MR-K9 R-LMS41-1.5K-MR-K9 R-LMS41-2.5K-MR-K9 R-LMS41-5K-MR-K9 R-LMS41-10K-MR-K9 Permitted Number of Devices LMS Device Upgrade for LMS 4.0 users LMS Device Upgrade for LMS 4.0 users LMS Device Upgrade for LMS 4.0 users LMS Device Upgrade for LMS 4.0 users LMS 4.1 1,500 Device Upgrade for LMS 4.0 users LMS 4.1 2,500 Device Upgrade for LMS 4.0 users LMS Device Upgrade for LMS 4.0 users LMS ,000 Device Upgrade for LMS 4.0 users 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 Step 2 Step 3 Step 4 Step 5 Shut down the VM from the vsphere client. In the vsphere client, select the VM, right click, and select Edit Settings. Select the Hardware tab and change the memory and CPU allocations, as recommended. Select the Resources tab and change the CPU reservation, as recommended. Switch on the VM and update the license. 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. Separate license is required to install CiscoWorks Health and Utilization Monitor (HUM) 1.2, add-on component to CiscoWorks LMS 3.2. Read the information in Understanding Product Ordering Options and Product Authorization Key to understand about the various product ordering options, before you understand about the various licenses about HUM 1.2. Note If you are an existing user of HUM 1.0 or HUM 1.1, you can use the existing serial license key to activate HUM 1.2 features. You need not purchase a license for HUM

79 Chapter 3 Preparing to Install Cisco Prime LAN Management Solution 4.1 Licensing Your Product This section contains: Licensing SKUs for Traditional Ordering of HUM 1.2 Licensing SKUs for Ordering Digital PAK for HUM 1.2 Licensing SKUs for Traditional Ordering of HUM 1.2 HUM 1.2 software is part of LMS 3.2 Product DVD kit. When you opt to use this method of ordering, you will receive only a software claim certificate paper with the PAK ID printed on it. You will not receive a separate DVD for HUM 1.2. The following are the available licenses (SKUs) for HUM 1.2 users, who have opted to order the Physical paper (software) claim certificate with printed PAK: Available Licenses (SKU) in HUM 1.2 Permitted number of Devices in HUM 1.2 CWHUM-1.2-S 50 devices restricted license CWHUM-1.2-M 300 devices restricted license CWHUM-1.2-L 1,000 devices restricted license Device-Level Conversion Licenses (SKU) in HUM 1.2 CWHUM-1.2-S2M Conversion from 50 devices restricted license to 300 devices restricted license CWHUM-1.2-S2L Conversion from 50 devices restricted license to 1,000 devices restricted license CWHUM-1.2-M2L Conversion from 300 devices restricted license to 1,000 devices restricted license Licensing SKUs for Ordering Digital PAK for HUM 1.2 HUM 1.2 software is part of CiscoWorks LMS 3.2 Software Download image and CiscoWorks LMS 3.2 Base Media kit. We recommend you to use this option to receive the PAK ID for serial license keys, if you want to activate HUM 1.2 from LMS 3.2 distribution media. Following are the SKUs available for HUM 1.2 users, who have opted to receive the Digital PAK through edelivery: Available Licenses (SKU) in HUM 1.2 Permitted number of Devices in HUM 1.2 L-CWHUM-1.2-S 50 devices restricted license L-CWHUM-1.2-M 300 devices restricted license L-CWHUM-1.2-M 1,000 devices restricted license Device-Level Conversion Licenses (SKU) in HUM 1.2 L-CWHUM-1.2-S2M Conversion from 50 devices restricted license to 300 devices restricted license L-CWHUM-1.2-S2L Conversion from 50 devices restricted license to 1,000 devices restricted license L-CWHUM-1.2-M2L Conversion from 300 devices restricted license to 1,000 devices restricted license 3-13

80 Licensing Your Product Chapter 3 Preparing to Install Cisco Prime LAN Management Solution 4.1 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: If you are not a registered user of Cisco.com, get your Cisco.com user ID from: Once you have obtained your Cisco.com user ID, log on to 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. 3-14

81 Chapter 3 Preparing to Install Cisco Prime LAN Management Solution 4.1 Licensing Your Product 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.1 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.1. 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.1 product. Figure 3-1 displays the licensing screen for LMS 4.1 on Windows 2008 operating system. Figure 3-1 Licensing Screen for LMS 4.1 Figure 3-2 displays the licensing screen for LMS 4.1 for existing users. Figure 3-2 Licensing Screen for LMS 4.1 During Upgrade The LMS installation program prompts you to select either the license file or select the Evaluation Only option (see Figure 3-1). We recommend that you complete the license registration process at this point. 3-15

82 Licensing Your Product Chapter 3 Preparing to Install Cisco Prime LAN Management Solution 4.1 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 Step 2 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. To log into the shell: a. Enter the command shell. b. Enter the shell password. Note Step 3 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: 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 Note Ensure that you provide the appropriate path to the navigate to the folder where the file is located. 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 3-16

83 Chapter 3 Preparing to Install Cisco Prime LAN Management Solution 4.1 Licensing Your Product 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 Ensure that you provide the appropriate path to the navigate to the folder where the file is located. Step 4 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.1 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 90-day evaluation period. The installation process for an evaluation copy is the same as that of a purchased product, except that you are prompted to select the Evaluation Only option from the Licensing Information page (see Figure 3-1). If you choose to run LMS in the evaluation mode, it is valid for only 90 days and does not support any upgrades and allows support for only 100 devices. It stops functioning after 90 days. The evaluation period cannot be extended. 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.1 Evaluation software from 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. 3-17

84 Licensing Your Product Chapter 3 Preparing to Install Cisco Prime LAN Management Solution 4.1 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: 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.If you have backed up from an earlier version of LMS and restored the data in LMS 4.0 that has less license SKU than the earlier version then the device states will be as follows: 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.1 NFR software from You must be a registered user of Cisco.com to download the software. To install a NFR copy of LMS 4.1, 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.1 during the installation. See Figure

85 Chapter 3 Preparing to Install Cisco Prime LAN Management Solution 4.1 Licensing Your Product Step 2 Step 3 Step 4 See Performing Installation of Cisco Prime LMS 4.1 for detailed instructions on installing the product. Enter the LMS 4.1 NFR license file location, or click Browse to locate the NFR license file. Click Next. 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. See Figure 3-1 and Figure 3-3. After the installation is completed, you should: Step 1 Launch LMS 4.1 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. Installing the License File We recommend that before installing the LMS 4.1 product, you register the product and receive a permanent license. Figure 3-3 describes the steps that you must follow for licensing your product. Figure 3-3 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 Product Authorization Key (PAK) (Printed on Software License Claim Certificate) Example 1: 4XCD##V####

86 Licensing Your Product Chapter 3 Preparing to Install Cisco Prime LAN Management Solution 4.1 To license your product and install the license file, you must: Step 1 Step 2 Step 3 Log onto Cisco.com to get your license file. If you are a registered user of Cisco.com, get your license file from: If you are not a registered user of Cisco.com, get your Cisco.com user ID from: Once you have obtained your Cisco.com user ID, log on to 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 . 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. 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 (see Figure 3-1) and use the browse window to locate the license file directory. On Solaris, select L for License File after you accept the Licensing Agreement and continue installing the application. b. Click Next to install the license file. 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.1, 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. 3-20

87 Chapter 3 Preparing to Install Cisco Prime LAN Management Solution 4.1 Application Scaling Numbers Application Scaling Numbers This section presents information on the specific scaling numbers for each of the LMS functionalities in LMS server: The scaling numbers for LMS are as follows: Functionality Grouping Services Inventory, Config and Image Management Scalability Limit on LMS Server 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: 200 user-defined groups 100 IPSLA groups 50 Fault groups 100 Port and Module Groups For LMS 2500 Device licenses, the following are the scaling limits: 200 user-defined groups 200 IPSLA groups 50 Fault groups 100 Port and Module Groups For LMS 5000 Device licenses, the following are the scaling limits: 200 user-defined groups 100 IPSLA groups 50 Fault groups 100 Port and Module Groups Note 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 3-21

88 Application Scaling Numbers Chapter 3 Preparing to Install Cisco Prime LAN Management Solution 4.1 Functionality Network Topology, Layer 2 Services and User Tracking Fault Management Scalability Limit on LMS Server For upto LMS 500 Device licenses, the scaling limit is Endhosts/IP Phones For LMS 500 and LMS 1000 Device licenses, the scaling limit is Endhosts/IP Phones For LMS 2500 Device licenses, the scaling limit is Endhosts/IP Phones For LMS 5000 Device licenses, the scaling limit is 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 The functionality supports upto 80,000 ports or interfaces (of which upto 15 percent can be in Managed state) to a maximum. 3-22

89 Chapter 3 Preparing to Install Cisco Prime LAN Management Solution 4.1 Application Scaling Numbers Functionality Device Performance Management IPSLA Performance Management Scalability Limit on LMS Server The recommended MIB objects scaling numbers are as follows: 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 For LMS 2500 device licenses the MIB objects scaling limit is For LMS 5000 device license the MIB objects scaling limit is 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. 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. Note The AutoIPSLA generated collectors are accounted for license. 3-23

90 Application Scaling Numbers Chapter 3 Preparing to Install Cisco Prime LAN Management Solution 4.1 Concurrent Users Supported LMS 4.1 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. Multiple number of simultaneous users can affect system performance. The maximum recommended concurrent users depends on the size and configuration of the server. 3-24

91 CHAPTER 4 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 Symantec s Veritas Storage Foundation products. This section explains: High Availability and Disaster Recovery- An Overview Veritas Components for Setting Up High Availability System Requirements for High Availability Implementation Setting up LMS High Availability Environment on Windows Setting up LMS High Availability Environment on Solaris Moving LMS from non-ha to HA Environment High Availability and Disaster Recovery- An Overview 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. 4-1

92 High Availability and Disaster Recovery- An Overview Chapter 4 Setting Up Cisco Prime LMS in High Availability and Disaster Recovery Environment The implementation of Symantec Veritas High Availability solution in LMS Server supports local redundancy (HA), geographic redundancy (DR) and Replication without clustering configurations. The following configurations that are implemented by Symantec Veritas High Availability solution in LMS Server, are supported through the local hard disks only: 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 Replication Link VCS Heartbeat Redundant Server DNS Switch/Router Network Network Devices

93 Chapter 4 Setting Up Cisco Prime LMS in High Availability and Disaster Recovery Environment High Availability and Disaster Recovery- An Overview Figure 4-2 displays geographic redundancy configuration. Figure 4-2 Geographic Redundancy Configuration Application Clients Primary Site (single-node) Primary Application Server Replication Link VCS Heartbeat Secondary Site (single-node) Redundant Server DNS Switch/Router Network Network Devices

94 Veritas Components for Setting Up High Availability Chapter 4 Setting Up Cisco Prime LMS in High Availability and Disaster Recovery Environment Veritas Components for Setting Up High Availability 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) 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. Licensing Information In a high availability or a geographic redundancy option, the LMS is active on only one server at any given point in time. Hence only a single license of LMS needs to be procured to be shared between the two servers (Primary and Secondary servers) running in Active-Standby mode respectively. See SUPPLEMENTAL LICENSE AGREEMENT for more information 4-4

95 Chapter 4 Setting Up Cisco Prime LMS in High Availability and Disaster Recovery Environment System Requirements for High Availability Implementation System Requirements for High Availability Implementation This section explains the Operating system and hardware requirements for Veritas implementation: Operating Systems Solaris 10 systems Windows 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. 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. Setting up LMS High Availability Environment on Windows 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 4-5

96 Chapter 4 Setting up LMS High Availability Environment on Windows Setting Up Cisco Prime LMS in High Availability and Disaster Recovery Environment Installing Storage Foundation HA 5.1 on Windows To install the product: Step 1 Step 2 Step 3 Step 4 Step 5 Step 6 Step 7 Step 8 Step 9 Step 10 Step 11 Step 12 Start the Veritas Storage and High Availability Solutions setup. Click Storage Foundation HA 5.1 for Windows. Click Complete/Custom to begin the installation. Review the Welcome message and click Next. Accept the license agreement and click Next. Enter the product license key for Veritas Storage Foundation HA 5.1 for Windows and click Add. 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 VxCache Uses a portion of system memory to improve I/O performance. Global Cluster Option Enables you to link clusters to provide wide-area failover and disaster recovery. Product Documentation Documentation of Veritas Storage Foundation HA 5.1 for Windows 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. 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. Review the installation settings information and click Next. The Installation Status screen displays the status messages and the progress of the installation. Review the installation summary information and click Next after the installation has completed. Click Finish. Click Yes to reboot the local node. 4-6

97 Chapter 4 Setting Up Cisco Prime LMS in High Availability and Disaster Recovery Environment Setting up LMS High Availability Environment on Windows 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. This section explains: 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 Step 2 Step 3 Step 4 Step 5 Step 6 Step 7 Click Start > All Programs > Symantec > Veritas Storage Foundation > Veritas Enterprise Administrator to launch the Veritas Enterprise Administrator (VEA) console. Select a profile if prompted. You can also select the default profile. Click Connect to a Host or Domain. 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. 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. Expand the tree view under the host node to configure a disk group under the StorageAgent tree node. Locate the StorageAgent tree node and right-click the Disk Groups icon under the StorageAgent tree node. 4-7

98 Chapter 4 Setting up LMS High Availability Environment on Windows Setting Up Cisco Prime LMS in High Availability and Disaster Recovery Environment Step 8 Step 9 Step 10 Step 11 Step 12 Select New Dynamic Disk Group from the shortcut context menu. The New Dynamic Disk Group wizard appears with the welcome page. Click Next to go to next page in the wizard. 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. Click Next to accept the confirmation screen with the selected tasks. 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 Step 3 Step 4 Step 5 Step 6 Step 7 Step 8 Step 9 Click Start > All Programs > Symantec > Veritas Storage Foundation > Veritas Enterprise Administrator to launch the Veritas Enterprise Administrator (VEA) console. Select a profile if prompted. You can also select the default profile. Click Connect to a Host or Domain. 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. 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. Expand the tree view under the host node to configure a disk group under the StorageAgent tree node. See Creating Disk Groups on Primary Server for details on how to create a disk group. Locate the StorageAgent tree node and right-click the Volumes icon under the StorageAgent tree node. Select New Volume from the shortcut context menu. The New Volume wizard appears with a welcome message. Click Next to go to the next page in the wizard. 4-8

99 Chapter 4 Setting Up Cisco Prime LMS in High Availability and Disaster Recovery Environment Setting up LMS High Availability Environment on Windows Step 10 Step 11 Step 12 Step 13 Step 14 Step 15 Step 16 Step 17 Step 18 Step 19 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. Click Next. 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. 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. Click Next. The Create File System dialog box appears. Select the Format this volume checkbox. Select the file system as NTFS. Click Next to review the settings summary. Click Finish to create the new volume. 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 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. 4-9

100 Chapter 4 Setting up LMS High Availability Environment on Windows Setting Up Cisco Prime LMS in High Availability and Disaster Recovery Environment Installing LMS on Primary and Secondary Servers To make the LMS application highly available, install LMS on newly created cscopx volume on both the Primary and Secondary servers. Ensure that: LMS is installed in custom mode 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. Note 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. Setting Up Veritas Volume Replication Modes of 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. This section explains: 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 4-10

101 Chapter 4 Setting Up Cisco Prime LMS in High Availability and Disaster Recovery Environment Setting up LMS High Availability Environment on Windows 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. 4-11

102 Chapter 4 Setting up LMS High Availability Environment on Windows Setting Up Cisco Prime LMS in High Availability and Disaster Recovery Environment Setting Up RDS, RVG and RLINK 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 Step 3 Step 4 Step 5 Step 6 Step 7 Step 8 Step 9 Step 10 Step 11 Step 12 Step 13 Step 14 Click Start > All Programs > Symantec > Veritas Storage Foundation > Veritas Enterprise Administrator to launch the Veritas Enterprise Administrator (VEA) console. Click View > Connection > Replication Network. Click Action > Setup Replicated Data Set to launch the Setup Replicated Data Set wizard. Enter a name for Replicated Data Set name. Enter a name for Replicated Volume Group name. Select a Primary host from the drop-down list box. Click Next. Select cscopx as the volume to be replicated and click Next. Select data_srl as the volume to be used for replicator log and click Next. Review the information on the summary page and click Create Primary RVG to create the RVG. A message appears. Click Yes to add the Secondary host to the Primary RDS. The Specify Secondary host for replication page appears. 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. 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. 4-12

103 Chapter 4 Setting Up Cisco Prime LMS in High Availability and Disaster Recovery Environment Setting up LMS High Availability Environment on Windows 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 Step 2 Stop the Replication Network by right-clicking on the Primary server, in the Replication Network view. 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 Step 2 Step 3 Step 4 Step 5 Step 6 Step 7 Step 8 Step 9 Step 10 Step 11 Right-click Selected Drive Letter:\Program Files\CSCOpx from the Windows Explorer. Select the Sharing and Storage menu item. The folder properties dialog box appears. Select the Security tab and click Add. Click the Location button in the Select Users or Groups dialog box, and select the local server from the selection tree. Enter casusers in the enter object names text box and click Check Names. The text box displays Server Name\casusers. Click OK. Click the Full Control checkbox under Allow to grant the casusers group full control. Click the Advanced button. Select Replace permission entries on all child objects shown here that apply to child objects. Click Apply and wait for the permissions to propagate to all child objects under the CSCOpx directory. Click OK after the propagation is complete. Note After the casusers group permissions have been set, unmount the volume and start the replication. 4-13

104 Chapter 4 Setting up LMS High Availability Environment on Windows Setting Up Cisco Prime LMS in High Availability and Disaster Recovery Environment Setting Up Veritas Volume Replication Without Clustering To set up volume replication on the Primary server: Step 1 Step 2 Step 3 Step 4 Step 5 Step 6 Stop the Daemon Manager on the LMS server. Launch the VEA Console and select View Connection > Replication Network. Right-click on the blue arrow displayed for the volume group to be replicated. For example, LMS_RVG. Click Migrate. Verify the Secondary Server name to which data is to be replicated. Click OK. Do the following tasks on the Secondary Server: Step 1 Step 2 Step 3 Step 4 Step 5 Step 6 Mount the cscopx volume with the drive letter as the same as mount drive that is mentioned for cscopx volume on Primary server drive. Run the following perl script from the directory: NMSRoot\bin\perl NMSRoot\bin\hostnamechange.pl ohost oldhostname -nhost newhostname -domain DomainName Here, oldhostname Hostname of the Primary server. newhostname Hostname of the Secondary server Domain Domain name of the LMS Server. Entering domain name is optional. 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. Restart the Daemon Manager. Launch the LMS Server by entering the following on the web browser:

105 Chapter 4 Setting Up Cisco Prime LMS in High Availability and Disaster Recovery Environment Setting up LMS High Availability Environment on Windows 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 Creating the Cluster 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 To create the cluster: Step 1 Click Start > All Programs > Symantec > Veritas Cluster Server > Configuration Wizards > Cluster Configuration Wizard. Step 2 Step 3 Step 4 Step 5 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. Click Next. Include the Primary and Secondary servers that should be part of the cluster. Select Create New Cluster Option and click Next. 4-15

106 Chapter 4 Setting up LMS High Availability Environment on Windows Setting Up Cisco Prime LMS in High Availability and Disaster Recovery Environment Step 6 Step 7 Step 8 Step 9 Step 10 Step 11 Step 12 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. Click Next to go to the next page in the wizard. 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. Click Ok. Click Next to go to the next page in the wizard. Select the Use VCS User Privileges checkbox. 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. Notification Configure this component to receive notifications of events occurring in the cluster through . You can use the VCS Configuration wizard to configure these components. To configure these components: Step 1 Step 2 Step 3 Step 4 Step 5 Step 6 Step 7 Launch the VCS Configuration wizard. Click Next. Click Cluster Operations > Domain name. Select the server to configure the cluster groups. Select Edit existing cluster option and click Next. Select Configure Cluster Service options and configure the notifier and web console options for local redundancy configuration (HA Setup). 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. 4-16

107 Chapter 4 Setting Up Cisco Prime LMS in High Availability and Disaster Recovery Environment Setting up LMS High Availability Environment on Windows Step 8 Step 9 Step 10 Step 11 Step 12 Click OK. Start the Cluster Manager using Start > All Programs > Symantec > Veritas Cluster Manager - Java Console. Click File > New Cluster. Enter the virtual IP Address of the cluster that is configured, in the Hostname field. Click OK. Creating the datadg Service Group (For HA Setup) To create the datadg Service Group: Step 1 Step 2 Step 3 Step 4 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. 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. Click OK. 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 Step 2 Step 3 Start the Cluster Manager using Start > All Programs > Symantec > Veritas Cluster Manager - Java Console. Login to the cluster using the credentials that you have configured in the VCS Configuration wizard. Use the VCS Configuration wizard to see the Cluster Service group created. Go to Tools > Add/Modify Service Group in the console and do the following: Enter the name of the service group as App_Rep. Select the Failover Option. Select the servers (Primary and Secondary servers) on which the service group can come online. Enable the Auto Start option. 4-17

108 Chapter 4 Setting up LMS High Availability Environment on Windows Setting Up Cisco Prime LMS in High Availability and Disaster Recovery Environment Step 4 Step 5 Click OK. Add the Proxy resource with the following configuration: Resource Name =VVR_NIC_Proxy Resource Type = Proxy Step 6 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. Add the IP resource with the following configuration: Resource Name = VVR_IP Step 7 Resource Type = IP Address = Virtual IP address SubNetMask = subnet mask MACAddress = MAC Address of the corresponding NIC card You must select the Critical and Enabled checkboxes for this resource. 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. Step 8 IPResName = VVR_IP You must select the Critical and Enabled checkboxes for this resource. Add the VMDg resource with the following configuration: Resource Name = datadg Resource Type = VMDg Step 9 Step 10 DiskGroupName = datadg You must select the Critical and Enabled checkboxes for this resource. This is required only for geographic redundancy setup (DR setup). 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. This is required only for geographic redundancy setup (DR setup). Right-click on the App_Rep service group and select Online on Primary Server. 4-18

109 Chapter 4 Setting Up Cisco Prime LMS in High Availability and Disaster Recovery Environment Setting up LMS High Availability Environment on Windows Creating the Application Service Group To create the Application Service Group: Step 1 Step 2 Step 3 Step 4 Step 5 Start the Cluster Manager using Start > All Programs > Symantec > Veritas Cluster Manager - Java Console. Log in to the cluster using the credentials that you have configured in the VCS Configuration wizard. Use the VCS Configuration wizard to see the Cluster Service group that is created. Go to Tools > Add/Modify Service Group in the console and do the following: Enter the name of the service group as App_Service_GP. Select the Failover option. Select the servers (Primary and Secondary servers) on which the service group can come online. Enable the Auto Start option. Click OK. Add the RVG Primary resource with the following configuration: Resource Name = App_RVGPrimary Step 6 Resource Type = RVGPrimary RvgResourceName = Name of the Resource Configured under the App_Rep Service group For example, App_Rvg. You must select the Critical and Enabled checkboxes for this resource. Add the MountV Resource with the following configuration: Resource Name = APP_MountV Resource Type = MountV Mount Path = Selected Drive Letter:\ Step 7 Volume Name = cscopx VMDg Resource Name = Name of the Resource Configured under the App_Rep Service group For example, datadg. You must select the Critical and Enabled checkboxes for this resource. Add the Proxy resource with the following configuration: Resource Name =APP_NIC_Proxy Resource Type = Proxy TargetResName = NIC You must select the Critical and Enabled checkboxes for this resource. 4-19

110 Chapter 4 Setting up LMS High Availability Environment on Windows Setting Up Cisco Prime LMS in High Availability and Disaster Recovery Environment Step 8 Add the IP resource with the following configuration. Resource Name = APP_IP Step 9 Step 10 Resource Type = IP Address = Virtual IP address allocated for this cluster and used by LMS application SubNetMask = subnet mask MACAddress = MAC Address of the corresponding NIC card. You must select the Critical and Enabled checkboxes for this resource. Import the Agent file from the location C:\Program Files\Veritas\cluster server\conf\config, into the cluster. Add the Agent resource with the following configuration. Resource Name = LMSAgent Step 11 Step 12 Step 13 Step 14 Step 15 Step 16 Step 17 Step 18 Resource Type = LMS You must select the Critical and Enabled checkboxes for this resource. Enter the pathname as NMSROOT. Enter the Virtual IP as EventIPAddress. Enter the Certificate Dir as NMSROOT/MDC/Apache/conf/ssl. Link APP_MountV as the parent of APP_RVGPrimary. Link APP_IP as the parent of APP_NIC_PROXY. Link Agent as the parent of APP_MountV. Link Agent as the parent of APP_IP. 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-20

111 Chapter 4 Setting Up Cisco Prime LMS in High Availability and Disaster Recovery Environment Setting up LMS High Availability Environment on Windows Creating the Primary and Secondary Clusters For a Disaster Recovery Cluster setup, you should: Step 1 Step 2 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. Create a Secondary cluster with the server in Site 2 and make all the service groups online except Application Service Group. See Cluster Configuration for High Availability for instructions to configure a cluster and various service groups. Note The names of the service groups, resources and their configuration should be identical on both the Primary cluster at Site 1 and the Secondary cluster at Site 2. 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: Cluster Manager (Web Console) Configure this resource if you want to access the Cluster Management Console (CMC) through web browser. Notification Configure this component if you want to receive notification of events happening in the cluster through . Global Cluster Option Allows you to manage multiple clusters. To create a Cluster Service Group: Step 1 Step 2 Perform the steps explained in Creating the Cluster Service Group on both the Primary and Secondary clusters to create the Cluster Service Group. Add a wac resource with the following configuration to the Cluster Service Group: Resource Name = wac Step 3 Step 4 Step 5 Step 6 Resource Type = Process You must select the Critical and Enabled checkboxes for this resource. Link wac as the parent of VCS_IP. Link VCS_IP as the parent of NIC. Link the other resources as explained in Creating the Cluster Service Group. Right-click on the App_Rep service group and select Online on Primary Server. You should not bring the resources to online in the Secondary cluster. 4-21

112 Chapter 4 Setting up LMS High Availability Environment on Windows Setting Up Cisco Prime LMS in High Availability and Disaster Recovery Environment 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 Step 2 Step 3 Step 4 Step 5 Step 6 Step 7 Start the Cluster Manager using Start > All Programs > Symantec > Veritas Cluster Manager - Java Console. Click Edit > Add/Delete Remote Cluster. A wizard appears. Click Next. Select the Add Cluster option and click Next. Enter the IP Address of the Secondary cluster. Enter the Username and password which is used to log into that cluster. A confirmation message appears stating the cluster has been successfully added. 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 Note Step 8 Step 9 Step 10 Step 11 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. 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. Enter the Cluster IP address, Username and password. 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. 4-22

113 Chapter 4 Setting Up Cisco Prime LMS in High Availability and Disaster Recovery Environment Setting up LMS High Availability Environment on Solaris 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. Setting up LMS High Availability Environment on Solaris 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 Installing LMS on Primary and Secondary 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 4-23

114 Chapter 4 Setting up LMS High Availability Environment on Solaris Setting Up Cisco Prime LMS in High Availability and Disaster Recovery Environment Installing Storage Foundation HA 5.1 on Solaris To install the product: Step 1 Step 2 Step 3 Step 4 Step 5 Step 6 Step 7 Step 8 Step 9 Step 10 Step 11 Step 12 Step 13 Step 14 Step 15 Step 16 Step 17 Step 18 Step 19 Go to Veritas installer location. For example, /Veritas/VSF_HA_5.1/installer. Run the installer file:./installer The Task menu appears. Enter I to install or upgrade Veritas Storage Foundation HA 5.1 package. The component list appears. Enter 5 to install all Veritas Storage Foundation components and press Enter. The installer prompts for a system name. Enter the system hostnames and press Enter. 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 Enter 2 to install Veritas Storage Foundation and press Enter. Enter Y to configure Storage Foundation. Enter N to configure VCS. Enter N to configure Enclosure based naming schemes. Enter Y to set up the default disk group. Enter the disk group name as datadg. Enter N for all VVR questions. Enter Y for Fully qualified host name confirmation. Enter N to enable the Storage Foundation Management server. Enter Y to start the Veritas Storage Foundation Process. Enter shutdown y i6 g0 to reboot the Solaris server Enter ps ef grep vx on the command prompt after reboot to verify whether all Veritas processes are brought up successfully. 4-24

115 Chapter 4 Setting Up Cisco Prime LMS in High Availability and Disaster Recovery Environment Setting up LMS High Availability Environment on Solaris 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. This section explains: 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. 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 Step 2 Step 3 Step 4 Step 5 Step 6 Step 7 Step 8 Step 9 Enter /opt/vrts/bin/vea on the Solaris system command prompt to launch the Veritas Enterprise Administrator (VEA) console. Select a profile if prompted. You can also select the default profile. Click Connect to a Host or Domain. 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. 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. Expand the tree view under the host node to configure a disk group under the StorageAgent tree node. Locate the StorageAgent tree node and right-click the Disk Groups icon under the StorageAgent tree node. Select New Dynamic Disk Group from the shortcut context menu. The New Dynamic Disk Group wizard appears with the welcome message. Click Next to go to next page in the wizard. 4-25

116 Chapter 4 Setting up LMS High Availability Environment on Solaris Setting Up Cisco Prime LMS in High Availability and Disaster Recovery Environment Step 10 Step 11 Step 12 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. Click Next to accept the confirmation screen with the selected tasks. 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 Step 2 Step 3 Step 4 Step 5 Step 6 Step 7 Step 8 Step 9 Step 10 Step 11 Step 12 Enter /opt/vrts/bin/vea on the Solaris system command prompt to launch the Veritas Enterprise Administrator (VEA) console. Select a profile if prompted. You can also select the default profile. Click Connect to a Host or Domain. Enter the host name of the server that you want to connect in the Host Name field or Select a host name from the drop-down list box. To connect to the local system, enter localhost. 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. Expand the tree view under the host node to configure a disk group under the StorageAgent tree node. Locate the StorageAgent tree node and right-click the Volumes icon under the StorageAgent tree node. Select New Volume from the shortcut context menu. The New Volume wizard appears with the welcome message. Click Next to go to the next page in the wizard. Click Let volume manager decide what disks to use for this volume. Click Next. 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. 4-26

117 Chapter 4 Setting Up Cisco Prime LMS in High Availability and Disaster Recovery Environment Setting up LMS High Availability Environment on Solaris Step 13 Step 14 Step 15 Step 16 Step 17 Step 18 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. Select the file system as vxfs. Mount the cscopx volume using the mount point as /opt/cscopx Click Next to review the settings summary. Click Finish to create the new volume. Repeat the above procedure to create a volume in the datadg disk group with the following characteristics: Volume Name: varcscopx Volume Type: Concatenated Volume 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. 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: 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. 4-27

118 Chapter 4 Setting up LMS High Availability Environment on Solaris Setting Up Cisco Prime LMS in High Availability and Disaster Recovery Environment Installing LMS on Primary and Secondary Servers 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: LMS is installed in custom mode 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. Note 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: Modes of Replication Setting Up RDS, RVG and RLINK You must select both the cscopx and varcscopx as the volumes to be replicated. This section explains: Setting Casuser Permissions on cscopx Volume on Solaris (If Required) Setting Up Veritas Volume Replication Without Clustering On Solaris 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 Step 2 Stop the Replication Network by right-clicking on the Primary server, in the Replication Network view. Mount the cscopx and varcscopx volumes with the mount point as the same as in the Primary server. 4-28

119 Chapter 4 Setting Up Cisco Prime LMS in High Availability and Disaster Recovery Environment Setting up LMS High Availability Environment on Solaris 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. Setting Up Veritas Volume Replication Without Clustering On Solaris To set up volume replication on the Primary server: Step 1 Step 2 Step 3 Step 4 Step 5 Step 6 Stop the Daemon Manager on LMS server. Launch the VEA Console and select View Connection > Replication Network. Right-click on the blue arrow displayed for the volume group to be replicated. For example, LMS_RVG. Click Migrate. Verify the Secondary Server name to data is to be replicated. Click OK. Do the following tasks on the Secondary Server: Step 1 Step 2 Step 3 Step 4 Step 5 Step 6 Step 7 Mount the cscopx volume with the /opt/cscopx directory. Mount the varcscopx volume with the /var/adm/cscopx directory. Run the following perl script from the directory. NMSRoot/bin/perl NMSRoot/bin/hostnamechange.pl ohost oldhostname -nhost newhostname -domain DomainName Here, oldhostname Hostname of the Primary server. newhostname Hostname of the Secondary server Domain Domain name of the LMS Server. Entering domain name is optional. 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. Restart the Daemon Manager. Launch the LMS Server by entering the following on the web browser:

120 Chapter 4 Setting up LMS High Availability Environment on Solaris Setting Up Cisco Prime LMS in High Availability and Disaster Recovery Environment 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 Creating the Cluster 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 To create the cluster on Solaris: Step 1 Step 2 Step 3 Step 4 Step 5 Step 6 Step 7 Step 8 Step 9 Step 10 Step 11 Run the Veritas installer from the VSF_HA_5.1 CD. Enter c followed by 1 to configure the clusters. The installer prompts you for a system name. Enter the system hostnames of the Primary and Secondary server. Press Enter after the system resumes back after stopping the VCS process. Enter the name of the cluster when system prompts for the cluster name. Enter N to configure Symantec Security Services and press Enter. Enter Y to create a new user for that cluster and press Enter. Enter N for Cluster Management configuration. Enter Y for Cluster Management Console configuration and press Enter. Select the public NICs among the list of NICs and press Enter. Enter the virtual IP Address assigned for that cluster and press Enter. 4-30

121 Chapter 4 Setting Up Cisco Prime LMS in High Availability and Disaster Recovery Environment Setting up LMS High Availability Environment on Solaris Step 12 Step 13 Step 14 Step 15 Step 16 Step 17 Enter the correct netmask and press Enter. Configure the SMTP notification for that server. Start the Cluster Manager by entering /opt/vrtsvcs/bin/hagui on the command prompt. Log in to the cluster using the credentials that you have configured during the Veritas Cluster Server configuration. Select the Cluster Service group and set the following attributes: 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 Step 3 Step 4 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. 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. Click OK. Add the Disk Group resource with the following configuration: Resource Name = datadg Resource Type = Disk Group 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 on Solaris To create the Replication Service group on Solaris, do the following on the Primary and Secondary clusters: Step 1 Step 2 Start the Cluster Manager by entering /opt/vrtsvcs/bin/hagui at the command prompt. 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. 4-31

122 Chapter 4 Setting up LMS High Availability Environment on Solaris Setting Up Cisco Prime LMS in High Availability and Disaster Recovery Environment Step 3 Step 4 Step 5 Go to Tools > Add/Modify Service Group in the console and do the following: Enter the name of the service group as App_Rep. Select the Failover option. Select the servers (Primary and Secondary servers) on which the service group can come online. Enable the Auto Start option. Click OK. Add the Proxy resource with the following configuration: Resource Name =App_Rep_NIC Resource Type = Proxy Step 6 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. Add the RVG resource with the following configuration: Resource Name = APP_RVG Resource Type = RVG RVG = LMS_DR_RVG Step 7 Disk Group= datadg You must select the Critical and Enabled checkboxes for this resource. Add the IP resource with the following configuration: Resource Name = AppRep_IP Step 8 Resource Type = IP Address = Virtual IP address Device = Public NIC name You must select the Critical and Enabled checkboxes for this resource. Add the Disk Group resource with the following configuration: Resource Name = datadg Resource Type = Disk Group Step 9 Step 10 DiskGroupName = datadg You must select the Critical and Enabled checkboxes for this resource. This is required only for geographic redundancy setup (DR setup). 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. This is required only for geographic redundancy setup (DR setup). Right-click on the App_Rep service group and select Online on Primary Server. 4-32

123 Chapter 4 Setting Up Cisco Prime LMS in High Availability and Disaster Recovery Environment Setting up LMS High Availability Environment on Solaris Creating the Application Service Group on Solaris To create the Application Service group on Solaris: Step 1 Step 2 Step 3 Step 4 Step 5 Start the Cluster Manager by entering /opt/vrtsvcs/bin/hagui at the command prompt. Log in to the cluster using the credentials that you have configured in the VCS Configuration wizard. You can see the Cluster Service group that is created. Go to Tools > Add/Modify Service Group in the console and do the following: 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. Click OK. Add the RVG Primary resource with the following configuration: Resource Name = App_RVGPrimary Step 6 Resource Type = RVGPrimary RvgResourceName = Name of the Resource Configured under the App_Rep Service group For example, App_Rvg. You must select the Critical and Enabled checkboxes for this resource. Add the Proxy resource with the following configuration: Resource Name =APP_NIC_Proxy Resource Type = Proxy Step 7 TargetResName = NIC You must select the Critical and Enabled checkboxes for this resource. Add the IP resource with the following configuration. Resource Name = APP_IP Step 8 Resource Type = IP Address = Virtual IP address allocated for this cluster and used by LMS application SubNetMask = subnet mask MACAddress = MAC Address of the corresponding NIC card. You must select the Critical and Enabled checkboxes for this resource. Add the Volume resource for cscopx volume with the following configuration. Resource Name = Volume Resource Type = cscopx Disk Group= datadg You must select the Critical and Enabled checkboxes for this resource. 4-33

124 Chapter 4 Setting up LMS High Availability Environment on Solaris Setting Up Cisco Prime LMS in High Availability and Disaster Recovery Environment Step 9 Add the Volume resource for varcscopx volume with the following configuration. Resource Name = Volume Resource Type = varcscopx Step 10 Disk Group= datadg You must select the Critical and Enabled checkboxes for this resource. Add the Mount resource for cscopx volume with the following configuration: Resource Name = cscopx_mount Step 11 Resource Type = Mount Mount Point= Mount_point Block Device=Exact Path of cscopx volume FSType=vxfs You must select the Critical and Enabled checkboxes for this resource. Add the Mount resource for varcscopx volume with the following configuration: Resource Name = varcscopx_mount Step 12 Step 13 Resource Type = Mount Mount Point= Mount_point Block Device=Exact Path of cscopx volume FSType=vxfs FSskopt=-y You must select the Critical and Enabled checkboxes for this resource. Import the Agent file from the location /etc/vrtsvcs/conf/config/lmstypes.cf, into the cluster. Add the Agent resource with the following configuration. Resource Name = LMSAgent Step 14 Step 15 Step 16 Step 17 Step 18 Step 19 Step 20 Step 21 Resource Type = LMS You must select the Critical and Enabled checkboxes for this resource. 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 c. Set the value of OfflineTimeout attribute as Enter the Virtual IP as EventIPAddress. Link cscopx_mount as the parent of cscopx. Link varcscopx_mount as the parent of varcscopx. Link cscopx as the parent of App_RVGPrimary. Link varcscopx as the parent of App_RVGPrimary. Link APP_IP as the parent of APP_NIC_PROXY. Link Agent as the parent of cscopx_mount, varcscopx_mount and APP_IP. 4-34

125 Chapter 4 Setting Up Cisco Prime LMS in High Availability and Disaster Recovery Environment Setting up LMS High Availability Environment on Solaris 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 Step 2 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. Create a Secondary cluster with the server in Site 2 and make all the service groups online except Application Service Group. See Cluster Configuration for High Availability for instructions to configure a cluster and various service groups. Note The names of the service groups, resources and their configuration should be identical on both the Primary cluster at Site 1 and the Secondary cluster at Site 2. This section explains: Creating the Cluster Service Group on Solaris Creating the Cluster Service Group on Solaris Disaster Recovery Setup Between Primary and Secondary Clusters on Solaris Configure a Cluster Service group in the servers at both sites to run the following optional components: Cluster Manager (Web Console) Configure this resource if you want to access the Cluster Management Console (CMC) through web browser. Notification Configure this component to receive notifications about the events occurring in the cluster. Global Cluster Option Allows you to manage multiple clusters. To create the Cluster Service Group, you must: Step 1 Step 2 Perform the steps explained in Creating the Cluster Service Group on both the Primary and Secondary clusters to create the Cluster Service Group. 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 You must select the Critical and Enabled checkboxes for this resource. 4-35

126 Chapter 4 Setting up LMS High Availability Environment on Solaris Setting Up Cisco Prime LMS in High Availability and Disaster Recovery Environment Step 3 Step 4 Step 5 Link wac as the parent of APP_IP. Link APP_IP as the parent of NIC. 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 Step 3 Step 4 Step 5 Step 6 Step 7 Start the Cluster Manager by entering /opt/vrtsvcs/bin/hagui at the command prompt. Click Edit > Add/Delete Remote Cluster. A wizard appears. Click Next. Select the Add Cluster option and click Next. Enter the IP Address of the Secondary cluster. Enter the Username and password which is used to log into that cluster. A confirmation message appears stating the cluster has been successfully added. 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 Note Step 8 Step 9 Step 10 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. 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. Enter the Cluster IP address, Username and password. 4-36

127 Chapter 4 Setting Up Cisco Prime LMS in High Availability and Disaster Recovery Environment Moving LMS from non-ha to HA Environment Step 11 Step 12 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. 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. Moving LMS from non-ha to HA Environment You can create the HA or DR deployment environment only for a fresh installation of LMS in the Custom mode. 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.1 after the Veritas Setup is complete. Remote Migration of LMS 3.2, LMS 3.2 SP, LMS 4.0 or LMS Data to Cisco Prime LMS 4.1 Server with HA Setup You can do a remote migration of Cisco Prime LMS 3.2, LMS 3.2 SP, LMS 4.0, or LMS data to the Cisco Prime LMS 4.1 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.1 after the Veritas Setup is complete. 4. Migrate the Cisco Prime LMS 3.2, LMS 3.2 SP, LMS 4.0, or LMS data to the remote LMS 4.1 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.1 for instructions to do a remote migration of data to LMS 4.1. Caution Ensure that the passwords, HTTPS port and SMTP server details are the same in both the servers (LMS 3.2, LMS 3.2 SP, LMS 4.0, or LMS and LMS 4.1 server). This is applicable only for Windows Operating System. 4-37

128 Moving LMS from non-ha to HA Environment Chapter 4 Setting Up Cisco Prime LMS in High Availability and Disaster Recovery Environment 4-38

129 CHAPTER 5 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 section explains: Overview of VMware High Availability Overview of VMware VMotion and Storage VMotion Cloning a Virtual Machine Using VMware Overview of VMware High Availability 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. 5-1

130 Chapter 5 Overview of VMware High Availability 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. This section explains: VMware vsphere Components for Setting Up High Availability Prerequisites for Implementing High Availability Setting up High Availability using VMware HA Creating a VMware HA Cluster VMware vsphere Components for Setting Up High Availability 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 and VMware ESXi 4.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.1 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

131 Chapter 5 Setting Up Cisco Prime LMS for High Availability, Live Migration, and Storage VMotion Using VMware Overview of VMware High Availability VMware ESX servers Requirements Ensure that each ESX or ESXi host meets the minimum hardware requirements supported by ESX or ESXi 4.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 For a successful HA in LMS 4.1, all redundant network connections must be in the same subnet. Ensure a successful failover before you install LMS 4.1. Note For more details, see the VMware vsphere 4.0 documentation. 5-3

132 Chapter 5 Overview of VMware High Availability Setting Up Cisco Prime LMS for High Availability, Live Migration, and Storage VMotion Using VMware Setting up High Availability using VMware HA This section lists the steps to setup HA for LMS 4.1 using VMware HA: 1. Install ESX or ESXi 4.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.1 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 Step 2 Step 3 Step 4 Step 5 Step 6 Step 7 Step 8 Step 9 Select the Hosts & Clusters view in vsphere Client. Right-click the Datacenter in the Inventory tree and click New Cluster. Complete the New Cluster wizard. Do not enable VMware HA (or DRS) at this time. Click Finish to close the wizard and create an empty cluster. Based on your plan for the resources and networking architecture of the cluster, use the vsphere Client to add hosts to the cluster. Right-click the cluster and click Edit Settings to modify the VMware HA (and other) settings for the cluster. On the Cluster Features page, select Turn On VMware HA. Configure the VMware HA settings for your cluster. 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

133 Chapter 5 Setting Up Cisco Prime LMS for High Availability, Live Migration, and Storage VMotion Using VMware Overview of VMware VMotion and Storage VMotion Note For more details on VMware HA settings, see the VMware vsphere 4.0 documentation. Overview of VMware VMotion and Storage VMotion 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. This section explains: VMware vsphere Components for Migration Prerequisites for Migration Using VMotion VMware vsphere Components for Migration Migrating LMS 4.1 Using VMware VMotion 5-5

134 Chapter 5 Setting Up Cisco Prime LMS for High Availability, Live Migration, and Storage VMotion Using VMware Overview of VMware VMotion and Storage VMotion VMware vsphere Components for Migration The following VMware vsphere components are used for live migration of LMS 4.1: 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 and VMware ESXi 4.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

135 Chapter 5 Setting Up Cisco Prime LMS for High Availability, Live Migration, and Storage VMotion Using VMware Overview of VMware VMotion and Storage VMotion 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.1 Using VMware VMotion This section lists the steps to migrate LMS 4.1 using VMware VMotion: 1. Install ESX or ESXi 4.0 in two or more servers. 2. Install vcenter Server 4.0 in any server with a proper license. 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 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 Ensure that sufficient resource is available on the target ESX or ESXi host. 11. Install LMS 4.1 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. 5-7

136 Chapter 5 Setting Up Cisco Prime LMS for High Availability, Live Migration, and Storage VMotion Using VMware Overview of VMware VMotion and Storage VMotion Migrating a Virtual Machine with VMotion To migrate a powered-on virtual machine from one host to another using VMotion technology: Step 1 Step 2 Step 3 Step 4 Step 5 Step 6 Step 7 Display the virtual machine you want to migrate in the inventory. Right-click on the virtual machine, and select Migrate from the pop-up menu. Select Change host and click Next. 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. Select a resource pool and click Next. Select the migration priority level and click Next. Review the page and click Finish. A task is created that begins the virtual machine migration process. Migrating a Virtual Machine with Storage VMotion To migrate a powered-on virtual machine from one storage to another using VMotion technology: Step 1 Step 2 Step 3 Step 4 Step 5 Step 6 Display the virtual machine you want to migrate in the inventory. Right-click on the virtual machine, and select Migrate from the pop-up menu. Select Change Datastore and click Next. 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. 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. 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

137 Chapter 5 Setting Up Cisco Prime LMS for High Availability, Live Migration, and Storage VMotion Using VMware Cloning a Virtual Machine Using VMware Cloning a Virtual Machine Using VMware 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. This section contains: 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. 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 5-9

138 Chapter 5 Cloning a Virtual Machine Using VMware Setting Up Cisco Prime LMS for High Availability, Live Migration, and Storage VMotion Using VMware Cloning a New Virtual Machine from a Parent Virtual Machine Prerequisites 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 This section explains the prerequisites for cloning to new VM from a parent VM: Install vcenter Server 4.0 in any server with a proper license. Install vsphere Client in client server and connect to vcenter Server. Install ESX 4.0 in a machine. Cloning a new Virtual 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. 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. Note After each step, check the Compatibility panel for any compatibility problem. Fix the problem and then proceed with migration. 5-10

139 Chapter 5 Setting Up Cisco Prime LMS for High Availability, Live Migration, and Storage VMotion Using VMware Cloning a Virtual Machine Using VMware 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')) Insert into Poller_Group_Details values (7,(select id from Group_Master_Table where group_name like '%PMC Groups/Port Groups/Link Ports')) Insert into Poller_Group_Details values (8,(select id from Group_Master_Table where group_name like '%PMC Groups/Port Groups/Link Ports')) Insert into Poller_Group_Details values (4,(select id from Group_Master_Table where group_name like '%System Defined Groups')) Insert into Poller_Group_Details values (5,(select id from Group_Master_Table where group_name like '%System Defined Groups')) Restart UPMProcess to bring the pollers to Active state Important Notes url of dbreader - User Id dba and Database Name upm Command to stop UPMProcess: pdterm UPMProcess Command to start UPMProcess: pdexec UPMProcess 5-11

140 Chapter 5 Cloning a Virtual Machine Using VMware Setting Up Cisco Prime LMS for High Availability, Live Migration, and Storage VMotion Using VMware Cloning Parent VM to Template and Deploying Template to New VM Cloning Parent VM to Template 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 Deploying Template to New VM 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. 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. Select Same format as source option and click Next. 7. Select Do not customize option and click Next. 8. Verify the settings and click Finish You can view the progress of template creation process from the Recent Tasks option or from the Tasks & Events tab of the ESX host. Note After each step, check the Compatibility panel for any compatibility problem. Fix the problem and then proceed with migration. To deploy this template to a new VM, see Deploying Template to New VM. 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. Select Same format as source option and click Next. 7. Select Do not customize option and click Next. 5-12

141 Chapter 5 Setting Up Cisco Prime LMS for High Availability, Live Migration, and Storage VMotion Using VMware Cloning a Virtual Machine Using VMware 8. Verify the settings and choose to Power on the virtual machine after creation. 9. 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. Note After each step, check the Compatibility panel for any compatibility problem. Fix the problem and then proceed with migration. 5-13

142 Chapter 5 Cloning a Virtual Machine Using VMware Setting Up Cisco Prime LMS for High Availability, Live Migration, and Storage VMotion Using VMware 5-14

143 CHAPTER 6 Performing Installation of Cisco Prime LMS 4.1 This chapter describes how to install and uninstall LMS 4.1 on Soft Appliance, Solaris and Windows systems. It describes the tasks you have to perform for installing LMS 4.1 on Soft Appliance, Solaris and Windows systems. It also helps you to verify the installation, uninstall, and reinstall LMS 4.1. 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.1 Upgrading to LMS 4.1 Verifying the Installation Accessing LMS Server Logging into Cisco Prime LMS Server Uninstalling LMS 4.1 Re-installing LMS

144 Performing Installation of LMS 4.1 Chapter 6 Performing Installation of Cisco Prime LMS 4.1 Performing Installation of LMS 4.1 This section explains how to install LMS 4.1 on Soft Appliance, Windows and Solaris systems for the first time. It contains: Installing LMS Soft Appliance - OVA Image Installing LMS 4.1 Soft Appliance - ISO Image Installing LMS 4.1 on Solaris Installing LMS 4.1 on Windows Installing LMS 4.1 in Silent Mode The LMS 4.1 installation program takes approximately: 35 minutes to complete on Windows 35 minutes to complete on Solaris 50 minutes on LMS Soft Appliance (OVA image) On a single server with the recommended hardware requirements. See System and Browser Requirements for Server and Client for more information. This can take more than two hours if you perform network management integration while installing. You must disable the Anti Virus enabled in your system before installation of LMS 4.1. 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. Note While setting up HA and DR environment in LMS server, ensure to set them prior to LMS installation. For further information on HA/DR configuration, see Chapter 4, Setting Up Cisco Prime LMS in High Availability and Disaster Recovery Environment. Installing LMS Soft Appliance - OVA Image You can install the LMS Soft Appliance using LMS 4.1 OVA image from the LMS 4.1 DVD. Read the following notes before installing the software: Ensure that your system meets the recommended hardware and software specifications specified in Server Requirements on Soft Appliance Systems. It takes approximately 30 minutes (deployment in local system) and 50 minutes (deployment in network) to install the Soft Appliance on a virtualized environment. 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. 6-2

145 Chapter 6 Performing Installation of Cisco Prime LMS 4.1 Performing Installation of LMS 4.1 Note You need not install any soft appliance image on the Virtual Machine (VM) before installing LMS 4.1, as the LMS 4.1 OVA image has embedded RedHat Enterprise Soft Appliance. 6-3

146 Performing Installation of LMS 4.1 Chapter 6 Performing Installation of Cisco Prime LMS 4.1 To install the LMS 4.1 Soft Appliance (OVA image): Step 1 Step 2 Step 3 Step 4 Step 5 Invoke the VMware vsphere Client. 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. Enter the username and password of the VMware server. Click Login. Select File > Deploy OVF Template. The Deploy OVF Template - Source window appears, see Figure 6-1. Figure 6-1 Deploy OVF Template - Source window Step 6 Step 7 Click Browse to select the source OVF template from your local file system or enter a URL to download the OVF Package from the internet. Click Next. 6-4

147 Chapter 6 Performing Installation of Cisco Prime LMS 4.1 Performing Installation of LMS 4.1 The Deploy OVF Template - OVF Template Details window appears, see Figure 6-2. You can verify the OVF template details. Figure 6-2 Deploy OVF Template - OVF Template Details window Step 8 Click Next. The Deploy OVF Template - Name and Location window appears. 6-5

148 Performing Installation of LMS 4.1 Chapter 6 Performing Installation of Cisco Prime LMS 4.1 Figure 6-3 Deploy OVF Template - Name and Location window Step 9 Enter the name of the deployed template. Note Step 10 Ensure that you provide a unique template name that does not exceed 80 characters. The unique template name refers to the virtual host deployed in the ESX/ESXi server. Click Next. The Deploy OVF Template - Datastore window appears. 6-6

149 Chapter 6 Performing Installation of Cisco Prime LMS 4.1 Performing Installation of LMS 4.1 Figure 6-4 Deploy OVF Template - Datastore window Step 11 Step 12 Select a datastore where you want to store the virtual machine files. Click Next. The Deploy OVF Template - Disk Format window appears. 6-7

150 Performing Installation of LMS 4.1 Chapter 6 Performing Installation of Cisco Prime LMS 4.1 Figure 6-5 Deploy OVF Template - Disk Format window Step 13 You can select either the Thin provisioned format or Thick provisioned format. Note We recommend you to choose Thick provisioned format. If you use the Thin provisioned format, you must ensure that your system meets the recommended hardware and software specifications specified in Server Requirements on Solaris Systems. Step 14 Click Next. The Deploy OVF Template - Ready to Complete window appears. This window displays the deployment setting details. 6-8

151 Chapter 6 Performing Installation of Cisco Prime LMS 4.1 Performing Installation of LMS 4.1 Figure 6-6 Deploy OVF Template - Ready to Complete window Step 15 Click Finish to start the deployment task. Note Step 16 Step 17 Step 18 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. Select the Console tab. The Welcome screen appears. Press Enter in the console window to continue with the next step. 6-9

152 Performing Installation of LMS 4.1 Chapter 6 Performing Installation of Cisco Prime LMS 4.1 Step 19 Enter the following configuration details of the server: Hostname - You have to enter the server name and not FQDN. Note The host name should not exceed 19 characters. IP Address IP Netmask Default Gateway DNS Domain Name - You have to enter the domain name of the server. For example cisco.com. Primary Name Server Secondary Name Server (optional) Primary NTP Server Secondary NTP Server (optional) System 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. 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. Confirm Password You can enter the admin password for confirmation. Step 20 The following message appears: For security reasons, passwords are not displayed. Do you want to view all the passwords? (Y/N) [N]: 6-10

153 Chapter 6 Performing Installation of Cisco Prime LMS 4.1 Performing Installation of LMS 4.1 Step 21 Step 22 Step 23 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. It will take 15 to 20 minutes to process the DB engine. 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 Note If you want to power off the VM server from the ESX server, you must do so only after stopping the daemons. You must not power off the VM server while the daemons are running. 6-11

154 Performing Installation of LMS 4.1 Chapter 6 Performing Installation of Cisco Prime LMS 4.1 Changing Server Configuration Details To change the configuration details of the server after installation: Step 1 Step 2 Step 3 Step 4 Step 5 Step 6 Step 7 Step 8 Step 9 Step 10 Login with Soft Appliance console administrator user account. This is the sysadmin username that you provided during installation. Enter the password. Enter the command shell. Enter the following command to stop the Daemons: /etc/init.d/dmgtd stop Enter exit to go to the sysadmin mode. 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. 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-1 for more details. Enter the command end. The following will be displayed: <HOSTNAME>/sysadmin# Enter the following command to update the changes: <HOSTNAME>/sysadmin# write memory 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: Hostname Default DNS Domain IP Address, IP Netmask IP Default Gateway Primary Name Server Primary NTP Server Time Zone 6-12

155 Chapter 6 Performing Installation of Cisco Prime LMS 4.1 Performing Installation of LMS 4.1 Step 11 The Daemons Manager will start automatically. Enter the following command to run the hostnamechange file: <HOSTNAME>/sysadmin# shell Enter shell password: /etc/init.d/dmgtd stop [<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-1 lists the examples of how to change the Soft Appliance server configuration details. Table 6-1 Soft Appliance Server Configuration Details Tasks Change the HostName Change the Domain, Gateway and Name server Change the NTP Server Change the IP address and Subnet Mask Configuration Details <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)# 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> LNX-LMS-05/sysadmin(config)# ntp server <PRIMARY_NTP_SERVER> 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> 6-13

156 Performing Installation of LMS 4.1 Chapter 6 Performing Installation of Cisco Prime LMS 4.1 Table 6-1 Soft Appliance Server Configuration Details (continued) Change the TimeZone Change the Username/ Password LNX-LMS-05/sysadmin(config)# clock timezone <TIME_ZONE_VALUE> See Supported Server Time Zones and Offset Settings for more details. LNX-LMS-05/sysadmin(config)# username <USERNAME> password plain <PASSWORD> role admin LNX-LMS-05/sysadmin(config)# end 6-14

157 Chapter 6 Performing Installation of Cisco Prime LMS 4.1 Performing Installation of LMS 4.1 Viewing System Details Table 6-2 lists the show commands that you can use in the Soft Appliance server. Table 6-2 Show Command List Show Commands application cdp clock cpu Description Displays the application(s) information. To display all the installed applications, enter the following command: CARS-9/sysadmin# show application <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. 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 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 2.27GHz speed(mhz): cache size: KB processor : 1 model : Intel(R) Xeon(R) CPU 2.27GHz speed(mhz): cache size: KB CARS-9/sysadmin# show cpu statistics user time: kernel time: idle time: i/o wait time: irq time:

158 Performing Installation of LMS 4.1 Chapter 6 Performing Installation of Cisco Prime LMS 4.1 Table 6-2 Show Command List (continued) Show Commands disks icmp_status interface Description 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 ) disk: 2% used ( of ) Internal filesystems: all internal filesystems have sufficient free space 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 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: Bcast: Mask: inet6 addr: fe80::20c:29ff:fee1:943f/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets: errors:0 dropped:0 overruns:0 frame:0 TX packets: errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes: (22.2 MiB) TX bytes: (88.1 MiB) lo Link encap:local Loopback inet addr: Mask: inet6 addr: ::1/128 Scope:Host UP LOOPBACK RUNNING MTU:16436 Metric:1 RX packets: errors:0 dropped:0 overruns:0 frame:0 TX packets: errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes: (945.9 MiB) TX bytes: (945.9 MiB) sit0 Link encap:ipv6-in-ipv4 NOARP MTU:1480 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:0 (0.0 b) TX bytes:0 (0.0 b) 6-16

159 Chapter 6 Performing Installation of Cisco Prime LMS 4.1 Performing Installation of LMS 4.1 Table 6-2 Show Command List (continued) Show Commands inventory logging Description 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: kb CPU Core Count: 2 CPU 0: Model Info: Intel(R) Xeon(R) CPU 2.27GHz CPU 1: Model Info: Intel(R) Xeon(R) CPU 2.27GHz Hard Disk Count(*): 1 Disk 0: Device Name: /dev/sda Disk 0: Capacity: 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. 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/ 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

160 Performing Installation of LMS 4.1 Chapter 6 Performing Installation of Cisco Prime LMS 4.1 Table 6-2 Show Command List (continued) Show Commands logins memory ntp ports process Description Lists the login history. To display the state of system logins, enter the following command: CARS-9/sysadmin# show logins cli admin pts/ Thu May 12 11:30 still logged in root pts/ Wed May 11 20:38-22:51 (02:13) root pts/ Wed May 11 14:40-16:28 (01:47) root pts/ Wed May 11 12:20-12:31 (00:11) admin tty1 Tue May 10 21:03 still logged in reboot system boot e Tue May 10 21:02 (1+14:45) setup tty1 Wed May 11 08:51 - down (-11:-50) reboot system boot e Wed May 11 08:46 (-11:-45) wtmp begins Wed May 11 08:46: 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: kb free memory: kb cached: kb swap-cached: 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 : synchronised to NTP server ( ) at stratum 3 time correct to within 30 ms polling server every 1024 s remote refid st t when poll reach delay offset jitter ============================================================================== LOCL. 10 l * u Warning: Output results may conflict during periods of changing synchronization. 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> Displays the system processes. To display information about the active processes, enter the following command: CARS-9/sysadmin# show process <running processes are displayed> 6-18

161 Chapter 6 Performing Installation of Cisco Prime LMS 4.1 Performing Installation of LMS 4.1 Table 6-2 Show Command List (continued) Show Commands running-config Description 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 ipv6 address autoconfig! ip name-server ! ip default-gateway ! clock timezone Asia/Calcutta! ntp server ! 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-19

162 Performing Installation of LMS 4.1 Chapter 6 Performing Installation of Cisco Prime LMS 4.1 Table 6-2 Show Command List (continued) Show Commands startup-config Description 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 domain-name cisco.com! interface GigabitEthernet 0 ip address ipv6 address autoconfig! ip name-server ! ip default-gateway ! clock timezone Asia/Calcutta! ntp server ! 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! 6-20

163 Chapter 6 Performing Installation of Cisco Prime LMS 4.1 Performing Installation of LMS 4.1 Table 6-2 Show Command List (continued) Show Commands tech-support terminal timezone Description Displays the tech output. To display the tech output, enter the following command: CARS-9/sysadmin# show tech-support ################################################### Application Deployment Engine(ADE) Technical Support Debug Info follows... ################################################### ***************************************** Displaying startup-config... *****************************************! hostname CARS-9! ip domain-name cisco.com! interface GigabitEthernet 0 ip address ipv6 address autoconfig! ip name-server More-- 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 Displays the timezone. To display the time zone as set on the system, enter the following command: CARS-9/sysadmin# show timezone Asia/Calcutta See Supported Server Time Zones and Offset Settings for more details. 6-21

164 Performing Installation of LMS 4.1 Chapter 6 Performing Installation of Cisco Prime LMS 4.1 Table 6-2 Show Command List (continued) Show Commands timezones udi uptime users Description 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-- Displays the udi information. To display the information about the system s 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 system s Unique Device Identifier (UDI)>>> Displays the system uptime. To display the system uptime, enter the following command: CARS-9/sysadmin# show uptime 2 day(s), 17:53:09 Displays the logged-in users information. To display a list of users, enter the following command: LNX-LMS-05/sysadmin# show users USERNAM ROLE HOST TTY LOGIN DATETIME admin Admin tty1 Wed May 11 22:53: admi Admin pts/0 Wed May 11 23:50:

165 Chapter 6 Performing Installation of Cisco Prime LMS 4.1 Performing Installation of LMS 4.1 Table 6-2 Show Command List (continued) Show Commands version application status LMS Description 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: ADE-OS System Architecture: x86_64 Copyright (c) by Cisco Systems, Inc. All rights reserved. Hostname: CARS-9 Version information of installed applications Cisco Prime LAN Management Solution Version : 4.1 Vendor : Cisco Systems, Inc 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 Program started - No mgt msgs received 2669 SyslogCollector Running normally 2670 RMEDbEngine Program started - No mgt msgs received 2671 ANIDbEngine Program started - No mgt msgs received 3072 MACUHIC Running normally 3109 UTLITE Running normally 3110 IpmDbEngine Program started - No mgt msgs received 3111 UPMDbEngine Program started - No mgt msgs received 3342 UPMDbMonitor Running normally 3537 DFMLogServer Program started - No mgt msgs received 3609 DFMCTMStartup Administrator has shut down this server 0 FHPurgeTask Transient terminated More

166 Performing Installation of LMS 4.1 Chapter 6 Performing Installation of Cisco Prime LMS 4.1 Table 6-2 Show Command List (continued) Show Commands application version LMS logging application LMS logging system ip route Description 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.1 Vendor : Cisco Systems, Inc 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.1 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-- Displays the system log details. To display system log, enter the following command: CARS-9/sysadmin# show logging system <<<<<<<<<<ADE.log displayed>>>>>>>>>>>>>> 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 Flags Metric Ref Use Iface U eth UG eth0 6-24

167 Chapter 6 Performing Installation of Cisco Prime LMS 4.1 Performing Installation of LMS 4.1 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.1 Soft Appliance - ISO Image Read the following points before installing the software: Ensure that your system meets the recommended hardware and software specifications specified in Server Requirements on Soft Appliance Systems. Note When there is more than one hard disk while installing LMS 4.1 (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. It takes approximately one hour to install the Soft Appliance. If the virus scanner is enabled on your system, the installation might take little longer time. This section contains: Installing LMS 4.1 Soft Appliance on VMware Installing LMS 4.1 Soft Appliance on NCS and UCS Servers Installing LMS 4.1 Soft Appliance on VMware To install the LMS 4.1 Soft Appliance (ISO image): Step 1 Step 2 Step 3 Step 4 Step 5 Step 6 Step 7 Invoke the VMware vsphere Client. 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. Enter the username and password of the VMware server. Click Login. Create a server or select an existing server from the servers listed on the left pane. You must restart the server before starting the installation. Right click the selected server and select Power > Reset to reboot the server. A confirmation message appears. Click Yes to continue. 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 6-25

168 Performing Installation of LMS 4.1 Chapter 6 Performing Installation of Cisco Prime LMS 4.1 Step 8 Step 9 Step 10 Step Network boot from Intel E1000 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. Navigate to the location where you have downloaded the software image and click Open. 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.1 To boot from hard disk, press <Enter> The following options appears: [1] Cisco Prime LAN Management Solution 4.1 Installation This option allows you to perform installation of LMS 4.1. [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. 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 Step 13 Type setup in the console to set the configuration. Enter the following configuration details of the server: Hostname - You have to enter the server name and not FQDN. IP Address Subnetmask Gateway DNS Domain - You have to enter the domain name of the server. For example cisco.com. 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 6-26

169 Chapter 6 Performing Installation of Cisco Prime LMS 4.1 Performing Installation of LMS 4.1 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. Step 14 Confirm Password Enter the admin password for confirmation. The following message appears: 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. admin user account password system identity user account password system generated database password The default option is N. 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 If you want to power off the VM server from the ESX server, you must do so only after stopping the daemons. You must not power off the VM server while the daemons are running. 6-27

170 Performing Installation of LMS 4.1 Chapter 6 Performing Installation of Cisco Prime LMS 4.1 Installing LMS 4.1 Soft Appliance on NCS and UCS Servers To install LMS 4.1 Soft Appliance to NCS and UCS servers: Step 1 Step 2 Step 3 Login to a machine where you want to install LMS 4.1 Soft Appliance. Insert Soft Appliance LMS 4.1 DVD into the server. The following options appears in the console: Cisco Prime LAN Management Solution 4.1 Installation This option allows you to perform installation of LMS 4.1. 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. 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 Step 5 Type setup in the console to set the configuration. Enter the following configuration details of the server: Hostname - You have to enter the server name and not FQDN. IP Address Subnetmask Gateway DNS Domain - You have to enter the domain name of the server. For example cisco.com. 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. Username 6-28

171 Chapter 6 Performing Installation of Cisco Prime LMS 4.1 Performing Installation of LMS 4.1 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. Step 6 Confirm Password Enter the admin password for confirmation. The following message appears: 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. admin user account password system identity user account password system generated database password The default option is N. 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 If you want to power off the VM server from the ESX server, you must do so only after stopping the daemons. You must not power off the VM server while the daemons are running. 6-29

172 Performing Installation of LMS 4.1 Chapter 6 Performing Installation of Cisco Prime LMS 4.1 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 Step 2 Step 3 Step 4 Login to a machine where you want to install LMS 4.1 Soft Appliance. Insert Soft Appliance LMS 4.1 DVD into the server. The following options appears in the console: [1] Cisco Prime LAN Management Solution 4.1 Installation [2] Recover administrator password Enter 2 to proceed with the password recovery process. The Admin Password Recover window appears. Enter the number corresponding to the admin username for which you want to recover the password. Note Step 5 Step 6 Step 7 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. Re-enter the password for confirmation. 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 Step 2 Step 3 Step 4 Step 5 Step 6 Step 7 Step 8 Go to &os=Linux&release=4.1&relind=AVAILABLE&rellifecycle=&reltype=latest Download the Cisco_Prime_LAN_Management_Solution_4_1.iso Invoke the VMware vsphere Client. Enter the IP address or host name of the host that needs to be directly managed. Enter the username and password of the VMware server. Click Login. Select the LMS server from the servers listed on the left pane for password recovery. Right click the selected server and select Power > Reset to reboot the server. A confirmation message appears. Click Yes to continue. 6-30

173 Chapter 6 Performing Installation of Cisco Prime LMS 4.1 Performing Installation of LMS 4.1 Step 9 Step 10 Step 11 Step 12 Step 13 Step 14 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 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. Navigate to the location where you have downloaded the software image and click Open. Select the option CD-ROM Drive and press Enter to boot the ISO image. The following options appears in the console: [1] Cisco Prime LAN Management Solution 4.1 Installation [2] Recover administrator password Enter 2 to proceed with the password recovery process. The Admin Password Recover window appears. Enter the number corresponding to the admin username for which you want to recover the password. Note Step 15 Step 16 Step 17 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. Re-enter the password for confirmation. 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. 6-31

174 Performing Installation of LMS 4.1 Chapter 6 Performing Installation of Cisco Prime LMS 4.1 Installing LMS 4.1 on Solaris Figure 6-7 helps you understand the Typical and Custom installation flows in LMS 4.1 on Solaris. Figure 6-7 LMS 4.1 Installation on Solaris Insert LMS 4.1 Product DVD Run the setup.sh installation script Welcome message and license prompt appears [y] Installing from Network Drive? No Yes Installing from Network Drive message appears [y] Solaris 10 Cluster patch message appears [y] Instal High Availability for LMS [y]? Yes No Typical/Custom Installation Type prompt appears 1 + Enter Typical Enter the License Information 2 + Enter Custom Enter Location to install RAM SWAP space check Enter the License Information Enter Admin Password Enter Database Password Enter System Identity Account Password Installation proceeds to complete RAM SWAP space check Enter Admin and Guest Password Enter System Identity Account Password Enter SMTP Server Details Installation proceeds to complete

175 Chapter 6 Performing Installation of Cisco Prime LMS 4.1 Performing Installation of LMS 4.1 To install the LMS 4.1 from the DVD on a Solaris system for the first time: Step 1 Log into the machine where you want to install LMS 4.1. Step 2 Insert the LMS 4.1 DVD. Note Step 3 Step 4 Step 5 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) 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.1 setup program. A prompt appears: Press Enter to read/browse the following license agreement: Press Enter to read the license agreement. The following message appears at the end of the license agreement: Do you accept all the terms of the License Agreement? (y/n) [n]: Enter Y to accept the license agreement and proceed with the installation, or enter N to deny and quit the installation. Note Step 6 Error messages or warning messages appear if you do not have the required or recommended Server and Client patches. While installing from the network drive, the Installing from Network Drive message appears. Installation from the network drive will be slower than installing from the local drive depending upon the network speed. Enter Y to proceed or N to exit installation. We recommend you download and install the latest required and recommended patches from before you run LMS. For more information on Solaris patches, see Solaris Patches. 6-33

176 Performing Installation of LMS 4.1 Chapter 6 Performing Installation of Cisco Prime LMS 4.1 The following warning messages appear to ensure you install the Cluster Patches required for Solaris 10: Step 7 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 WARNING: Otherwise, some features of the Cisco Prime applications will not function properly. Do you want to continue the installation? (y/n) [y]: If you enter Y and proceed with the installation, a message appears prompting you to select any one mode to install. Select any one of the appropriate installation mode to proceed: Typical This is the default installation mode. See Installing LMS 4.1 on Solaris(Typical) Custom See Installing LMS 4.1 on Solaris (Custom) Installing LMS 4.1 on Solaris(Typical) To install LMS 4.1 for the first time on a Solaris system using the Typical option: Step 1 At the command prompt, press either: 1 and Enter to proceed with the installation after you select the Typical mode. Or Q to quit the installation. If you press Enter to proceed with the installation, the installation program performs the prerequisites checks The License message appears prompting you to enter the license information for LMS 4.1. Note If you do not have a license you can select the Evaluation Mode. You must obtain a valid License Key within 90 days. Step 2 Enter any of the following to specify the license for LMS 4.1: L and provide the License file location. E to opt 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. The installation program calculates the minimum disk space, RAM and Swap space required for installing the product. If the disk space is sufficient, the following message appears: Sufficient disk space. If the drive does not have enough space, an error message appears and the installation exits. 6-34

177 Chapter 6 Performing Installation of Cisco Prime LMS 4.1 Performing Installation of LMS 4.1 Step 3 Step 4 Enter the Cisco Prime LMS Admin password and confirm it. For more information on passwords, see Password Information. Enter the System Identity Account Password and confirm it. This password will be used on all multi-server machines. A message appears: Do you want to see the passwords that were entered/randomly generated? (y/n) [n] Step 5 Enter y. The following message appears: WARNING: Exiting installation beyond this point might result in system instability. Do you want to continue the installation? (y/n) [y]: Step 6 Enter y. 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. Installation now proceeds. It takes approximately 35 minutes to complete the installation. 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 completed. 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. To prepare the client system for use, see System and Browser Requirements for Server and Client. For troubleshooting information, see Checking Processes After Installationand Understanding Installation Error Messages. 6-35

178 Performing Installation of LMS 4.1 Chapter 6 Performing Installation of Cisco Prime LMS 4.1 Installing LMS 4.1 on Solaris (Custom) To install LMS 4.1 for the first time on a Solaris system using the Custom option: Step 1 Go to the command prompt and select either: 2 and Enter to proceed with the installation after you select the Custom mode. Or Q to quit the installation. If you select Enter to proceed with the installation, the following message appears: Enter the location where the product will be installed. The default location is /opt/cscopx. If you choose another location, installation will create a symbolic link /opt/cscopx to that location. Destination folder should not contain the following # $ % ^ & * ( ) + } { " : [ ] ; '? < >,. ` = ~ 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 2 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. The License message appears prompting you to enter the license information. Note If you do not have a license you can select the Evaluation Mode. You must obtain a valid License Key within 90 days. Step 3 Enter any of the following to specify the license for LMS 4.1: Step 4 L and provide the License file location. 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. After specifying the License file for LMS 4.1, the Database Password prompt appears. Enter the database password. This password will be used internally by the product. It must begin with an alphabet and can have 5 15 characters. For more information on passwords, see Password Information. The installation program calculates the minimum disk space, RAM and Swap space required for installing the product. If the disk space is sufficient, the following message appears: Sufficient disk space. If the drive does not have enough space, an error message appears and the installation exits. 6-36

179 Chapter 6 Performing Installation of Cisco Prime LMS 4.1 Performing Installation of LMS 4.1 Step 5 Step 6 Step 7 Step 8 Step 9 Step 10 Step 11 Enter the LMS Admin password and confirm it. For more information on passwords, see Password Information. Enter the Guest password and confirm it. For more information on passwords, see Password Information. Enter the System Identity Account password and confirm it. In a multi-server environment, you must configure all systems part of your multi-server setup with the same System Identity Account password. For more information on passwords, see Password Information. Enter the SMTP server name. For more information, see License Information. Enter the country code, state, city, company, organization, administrator s address, and Host name/fqdn for HTTPS. Only the Host name/fqdn is mandatory. You can enter the host name or fully-qualified domain name of the server. Other fields are optional. Press Enter to skip other fields. The following message appears: Fault Management uses a data transport protocol that requires authentication for server-to-server communication. Do you wish to retain the default username and password for securing this interface? (y/n) [n]: If you enter Y, the user name and password will be generated automatically. If you enter N, it will prompt for user name and password. Enter N Enter the user name and password The following message appears: Do you want to see the passwords that were entered/randomly generated? If yes, please remember that passwords are security sensitive data and hence make sure they are kept secure.? (y/n) [n]: If you Enter Y, all the passwords will be displayed. The default option is N. Step 12 Enter N. A message appears: Exiting installation beyond this point might result in system instability. Do you want to continue the installation? (y/n) [y] 6-37

180 Performing Installation of LMS 4.1 Chapter 6 Performing Installation of Cisco Prime LMS 4.1 Step 13 Enter Y. 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. Installation now proceeds. The installation completes without displaying more questions and the system prompt appears. It takes approximately 35 minutes to complete the installation. 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 completed. 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. 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. 6-38

181 Chapter 6 Performing Installation of Cisco Prime LMS 4.1 Performing Installation of LMS 4.1 Installing LMS 4.1 on Windows Figure 6-8 helps you understand the Typical and Custom installation flows in LMS 4.1 on Windows. Figure 6-8 LMS 4.1 Installation On Windows 6-39

182 Performing Installation of LMS 4.1 Chapter 6 Performing Installation of Cisco Prime LMS 4.1 To install LMS 4.1 on a Windows system for the first time: Step 1 Login as administrator to the machine where you want to install LMS 4.1. Step 2 Insert the LMS 4.1 DVD. Note Step 3 Step 4 Step 5 Step 6 Step 7 Step 8 We recommend that you run the installation from a local DVD or a local hard drive to avoid errors that may result from the network being slow or busy. Installation from local hard drive will be faster than installation from DVD. If you want to install from a local hard drive, you must copy the contents from the DVD to the local hard drive. Ensure that you copy the entire contents from the DVD to the hard drive. Double-click on the autorun.exe or setup.exe file. The Cisco Prime LAN Management Solution 4.1 window appears. Click Install to continue. While installing from the network drive, the Installing from Network Drive window appears. Installation from the network drive will be slower than installing from the local drive depending upon the network speed. Click Yes to proceed or No to exit installation. The Internet Information Services (IIS) detection message appears. When 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, except 6000, for HTTPS to avoid this conflict. 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 custom installation. Click Yes or No to continue. Installation checks for the Regional Settings. They have to be set either as US English or Japanese. If the Primary settings point to an unsupported locale, installation aborts with the following message appears: You are trying to install Cisco Prime LMS on an unsupported locale. Cisco Prime supports only US English or Japanese languages. Please reinstall your Operating System with a supported locale and change the Regional Settings to either of these languages. The following messages appear: Ensure that you have disabled any anti-virus application.anti-virus applications may cause some problems with the installation of Cisco Prime LAN Management Solution 4.1. You must have local Administrator privileges before beginning the installation. Only a user with local Administrator privileges can install or uninstall the product. The Welcome window appears. Click Next to continue. The Software License Agreement window appears. You must accept this agreement to install Cisco Prime LMS

183 Chapter 6 Performing Installation of Cisco Prime LMS 4.1 Performing Installation of LMS 4.1 Step 9 Step 10 Click Accept to continue. The High Availability Detection dialog box appears if any Symantec Veritas products are installed on the same server. You can select the Install High Availability Agent for LMS checkbox to setup the High Availability environment for LMS. If you do so, the installation will continue in Custom mode only. Otherwise, the Setup Type dialog box appears. Select one of the following: Typical This is the default installation mode. See Installing LMS 4.1 on Windows (Typical) Custom See Installing LMS 4.1 on Windows New (Custom) Installing LMS 4.1 on Windows (Typical) To install LMS 4.1 for the first time on a Windows system using the Typical option: Step 1 Step 2 Step 3 Step 4 Step 5 Step 6 Step 7 Step 8 Click Next to continue after you select the Typical installation mode. The Licensing Information dialog box appears. Specify the License File Location. If you do not have a license you can select the Evaluation Mode, which is the default option. You must obtain a valid License Key within 90 days. Click Next. The System Requirements dialog box appears. The Installation program checks the system configuration and required space. If the swap space is less than 8 GB, an error message appears and the installation exits. Click Next. The Enter the Admin Password box appears. Enter the User Admin password and confirm it. For more information on passwords, see Password Information, page A-7. Click Next to continue installation. The Enter the System Identity Account Password dialog box appears. Enter the System Identity Account password and confirm it. In a multi-server environment, you must configure all systems that are part of your multi-server setup with the same System Identity Account password. For more information on passwords, see Password Information, page A-7. Click Next. The Create casuser information box appears. 6-41

184 Performing Installation of LMS 4.1 Chapter 6 Performing Installation of Cisco Prime LMS 4.1 Step 9 Step 10 Step 11 Step 12 Step 13 Step 14 Step 15 Casuser is the user who administers and maintains Cisco Prime LMS Server, without having administrative privileges. If the available memory is less than the required memory, the performance will be affected and a warning appears. Click Yes to continue with installation or No to abort. The Summary dialog box appears. Click Install. Installation continues. The Installation Indicator box appears. Wait for a few minutes for the installation to complete. The Information window appears. The Information window 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 Click Next. If you perform installation with the evaluation license then the following message appears: INFO: Please obtain a valid License Key from Cisco.com within 90 days. Click OK. 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. If the installation completes with errors, the following error message appears: Installation of Cisco Prime Lan Management Solution 4.1 completed. Some errors occured during installation. See NMSROOT/Cisco_Prime_install_YYYYMMDD_hhmmss.log for details. Click OK. The Restart dialog box appears after the installation is complete. You need to restart your machine after you have installed LMS 4.1. Select Yes, I want to restart my computer now. Click Finish. To prepare the client system for use, see System and Browser Requirements for Server and Client, page 2-2. For troubleshooting information, see Checking Processes After Installation, page 8-1and Understanding Installation Error Messages, page 8-3. Installing LMS 4.1 on Windows New (Custom) To install LMS 4.1 for the first time on a Windows system using the Custom option: Step 1 Click Next to continue after you select the Custom installation mode. The Choose Destination Folder dialog box appears. 6-42

185 Chapter 6 Performing Installation of Cisco Prime LMS 4.1 Performing Installation of LMS 4.1 Step 2 Step 3 Step 4 Step 5 Step 6 Step 7 Step 8 Step 9 Step 10 Step 11 Step 12 Step 13 Step 14 Step 15 Step 16 The default folder is SystemDrive:\Program Files\CSCOpx. You can choose the destination folder where Cisco Prime LMS will be installed. Click Next. The Change Destination Folder dialog box appears if the destination folder location was entered in Step 1. You can either select a new destination folder or confirm the one that you selected earlier. Click Next to proceed. The Licensing Information dialog box appears for LMS 4.1. Specify the License File Location. If you do not have a license you can select the Evaluation Mode, which is the default option. You must obtain a valid License Key within 90 days. Click Next. The System Requirements dialog box appears. The Installation program checks the system configuration and required space. If the swap space is less than 8 GB, an error message appears and the installation exits. Click Next. The Enter the Admin and Guest Password box appears. Enter the User Admin password and Guest password and confirm them. The passwords must be at least 5 characters long. For more information on passwords, see Password Information, page A-7. Click Next to continue installation. The Enter the System Identity Account Password dialog box appears. Enter the System Identity Account password and confirm it. In a multi-server environment, you must configure all systems that are part of your multi-server setup with the same System Identity Account password. For more information on passwords, see Password Information, page A-7. Click Next. The Change casuser Password box appears. Casuser is a user who administers and maintains the server, without having any administrative privileges. Enter a password for the casuser and confirm it. If you do not enter a password, the setup program will generate a random password for you. Click Next to continue installation. Click Yes to continue with installation or No to abort. The Database Password dialog box appears. The password must begin with an alphabet and should not exceed 15 characters. Enter the Database password and confirm it. Click Next. The Mail Settings dialog box appears. Enter the https port, address, and SMTP server. 6-43

186 Performing Installation of LMS 4.1 Chapter 6 Performing Installation of Cisco Prime LMS 4.1 Step 17 Step 18 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 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 custom installation. Click Next. The Self-signed certificate dialog box appears. Enter the details to generate the self-signed certificates. Note Step 19 Step 20 Step 21 Step 22 Step 23 Step 24 Step 25 You must provide the Hostname/FQDN information. Click Yes to continue with installation or No to abort. The Summary dialog box appears. Click Install. Installation continues. The Installation Indicator box appears. Wait for a few minutes for the installation to complete. The Information window appears. The Information window 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. Click Next. If you perform installation with the evaluation license then the following message appears: INFO: Please obtain a valid License Key from Cisco.com within 90 days. Click OK. 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. If the installation completes with errors, the following error message appears: Installation of Cisco Prime Lan Management Solution 4.1 completed. Some errors occured during installation. See NMSROOT/Cisco_Prime_install_YYYYMMDD_hhmmss.log for details. Click OK. The Restart dialog box appears after the installation is complete. You must restart your machine after you have installed LMS 4.1. Select Yes, I want to restart my computer now. Click Finish. 6-44

187 Chapter 6 Performing Installation of Cisco Prime LMS 4.1 Performing Installation of LMS 4.1 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. 6-45

188 Performing Installation of LMS 4.1 Chapter 6 Performing Installation of Cisco Prime LMS 4.1 Installing LMS 4.1 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.1 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.1 in silent mode: Step 1 Insert the LMS 4.1 DVD. Note Step 2 Step 3 Step 4 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. Navigate to images/disk1 directory at the command prompt. Enter the following commands to install LMS 4.1 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. Restart your system after the installation is complete. 6-46

189 Chapter 6 Performing Installation of Cisco Prime LMS 4.1 Performing Installation of LMS 4.1 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 destination adminpassword secretpassword (Solaris only) casuser (Windows Only) systemidentityaccountpassword (Windows only) Description 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. Specifies the login password for the admin user. This is mandatory. Specifies the login password for the secret user. 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. Password for the System Identity Account. This is mandatory. Sample Answer Files On Windows: #--- begin answer file #--- hash sign (#) is allowed to mark comments systemidentityaccountpassword=admin casuser=casuser destination=c:\progra~1\cscopx adminpassword=admin #--- end of answer file On Solaris: #cat /tmp/answer_file ##Sample Answer file adminpassword=admin secretpassword=admin destination=/opt/cscopx The sample answer files are also available in the Software image at the directory disk1/install. 6-47

190 Upgrading to LMS 4.1 Chapter 6 Performing Installation of Cisco Prime LMS 4.1 Upgrading to LMS 4.1 The following upgrade paths are supported: Table 6-3 Upgrade and Data Migration Procedure Current LMS Version Type of Upgrade Procedure LMS 4.0 Remote migration 1. Back up the data in the old machine having LMS Install LMS Migrate your data to LMS 4.1 using the instructions explained in the section Remote Upgrade to LMS 4.1. Direct inline migration 1. Install LMS 4.1 over LMS 4.0. The data is automatically migrated during installation. LMS Remote migration 1. Back up the data in the old machine having LMS Install LMS Migrate your data to LMS 4.1 using the instructions explained in the section Remote Upgrade to LMS 4.1. Direct inline migration 1. Install LMS 4.1 over LMS The data is automatically migrated during installation. LMS 3.2, LMS 3.2 SP Remote migration 1. Back up the data in the old machine having LMS 3.2/3.2 SP. 2. Install LMS Migrate your data to LMS 4.1 using the instructions explained in the section Remote Upgrade to LMS

191 Chapter 6 Performing Installation of Cisco Prime LMS 4.1 Remote Upgrade to LMS 4.1 Table 6-3 Upgrade and Data Migration Procedure Current LMS Version Type of Upgrade Procedure LMS 2.6, LMS 2.6 SP1, LMS 3.0, LMS 3.0 December 2007 update, LMS 3.1 LMS 2.2, LMS 2.5, LMS Remote migration Direct upgrade to LMS 4.1 is not supported. 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 4.0 > LMS 4.1 Remote migration Direct upgrade to LMS 4.1 is not supported. The suggested upgrade path is: LMS 2.2 / LMS 2.5 / LMS > LMS 2.6 > LMS 4.0 > LMS Back up the data in the old machine. 2. Install LMS 4.0 in the new machine. 3. Migrate the data to LMS 4.0. For more information, see n_management_solution/4.0/install/guide/dmg.html 4. Install LMS 4.1. From LMS 4.0 to LMS 4.1, you can perform direct inline or remote upgrade, click here for more details. 1. Back up the data in the old machine. 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 Readme for CiscoWorks LMS 2.6 Update on Windows Data Migration Guide for LAN Management Solution Install LMS 4.0 in the new machine. 4. Migrate the data to LMS n_management_solution/4.0/install/guide/dmg.html 5. Install LMS 4.1. From LMS 4.0 to LMS 4.1, you can perform direct inline or remote upgrade, click here for more details. Remote Upgrade to LMS 4.1 This section contains information on: Remote Upgrade to LMS 4.1 on Solaris Remote Upgrade to LMS 4.1 on Windows 6-49

192 Remote Upgrade to LMS 4.1 Chapter 6 Performing Installation of Cisco Prime LMS 4.1 Remote Upgrade to LMS 4.1 on Solaris To upgrade from the previous versions of LMS to LMS 4.1 on a different Solaris machine: Step 1 Step 2 Step 3 Step 4 Login to the machine where the previous version of LMS is installed. Take a backup of the LMS data. Login to the machine where LMS 4.1 is to be installed. Follow the install procedure using Typical or Custom to install LMS 4.1. See Installing LMS 4.1 on Solaris. Step 5 Migrate the data to LMS 4.1. To migrate and restore the LMS data, follow the procedure in Migrating Data to Cisco Prime LAN Management Solution 4.1. Notes for Remote Upgrade When you back up the data from LMS 3.2/3.2 SP and restore the data on LMS 4.1, a warning message appears stating that there is a mismatch in the applications data. You can ignore this message and continue the data restore. For more details on backing up and restoring data, see Migrating Data to Cisco Prime LAN Management Solution 4.1. Note While setting up HA and DR environment in LMS server, ensure to set them prior to LMS installation. For further information on HA/DR configuration, see Chapter 4, Setting Up Cisco Prime LMS in High Availability and Disaster Recovery Environment Remote Upgrade to LMS 4.1 on Windows To remote upgrade from the previous versions of LMS to LMS 4.1 on a different Windows machine: Step 1 Step 2 Step 3 Step 4 Log into the machine where the previous version of LMS is installed. Take a backup of the LMS data. Log into the machine where LMS 4.1 is to be installed. Follow the install procedure using Typical or Custom to install LMS 4.1. See Installing LMS 4.1 on Windows. Step 5 Migrate the data to LMS 4.1. To migrate and restore the LMS data follow the procedure in Migrating Data to Cisco Prime LAN Management Solution 4.1. Notes for Remote Upgrade When you back up the data from LMS 2.6/3.x and restore the data on LMS 4.1, a warning message appears stating that there is a mismatch in the applications data. You can ignore this message and continue the data restore. For more details on backing up and restoring data, see Migrating Data to Cisco Prime LAN Management Solution

193 Chapter 6 Performing Installation of Cisco Prime LMS 4.1 Verifying the Installation While setting up HA and DR environment in LMS server, ensure to set them prior to LMS installation. For further information on HA/DR configuration, see Chapter 4, Setting Up Cisco Prime LMS in High Availability and Disaster Recovery Environment. Verifying the Installation You can verify LMS 4.1 installation by following either of these procedures. Procedure 1 You can verify LMS 4.1 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.1.: Functionalities Services/Processes Common Services Apache CmfDbEngine CmfDbMonitor CMFOGSServer CSDiscovery CSRegistryServer DCRServer DCRDevicePoll diskwatcher EDS CSSCPServer Network Topology, Layer 2 Services and User Tracking ANIServer ANIDbEngine UTManager VNMServer EDS-GCF ESS EssMonitor EventFramework FDRewinder (Only on Solaris) jrm LicenseServer NameServer NameServiceMonitor Proxy (Windows only) Tomcat TomcatMonitor UTLITE UTMajorAcquisition MACUHIC WlseUHIC 6-51

194 Verifying the Installation Chapter 6 Performing Installation of Cisco Prime LMS 4.1 Functionalities Inventory, Config and Image Management Services/Processes ChangeAudit ConfigMgmtServer ConfigUtilityService CTMJrmServer EnergyWise EssentialsDM ICServer Fault Management AdapterServer IPSLA Performance Management Device Performance Management AdapterServer1 DataPurge DfmServer DfmServer1 DFMLogServer DFMCTMStartup DfmBroker DFMMultiProcLogger DFMOGSServer EPMServer EPMDbEngine IPMProcess IpmDbEngine UPMDbEngine UPMProcess RMEDbEngine SyslogAnalyzer SyslogCollector PMCOGSServer FHPurgeTask FHDbEngine FHServer Interactor Interactor1 InventoryCollector InventoryCollector1 INVDbEngine NOSServer PMServer PTMServer TISServer IPMOGSServer UPMDbMonitor 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

195 Chapter 6 Performing Installation of Cisco Prime LMS 4.1 Accessing LMS Server Accessing LMS Server 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: If SSL is enabled, and if you have installed the LMS on the default port, enter: where server_name is the hostname of the server on which you have installed LMS. The LMS Login page appears. 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.1 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 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 custom 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. 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 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 Mozilla FireFox 4.0.x and 5.0.x 6-53

196 Accessing LMS Server Chapter 6 Performing Installation of Cisco Prime LMS 4.1 Internet Explorer 8 To clear the cache and cookies: Step 1 Step 2 Step 3 Step 4 Go to Tools menu. Select Delete Browsing History. Select the check box for Temporary Internet Files and Cookies. Click Delete. Once the files have been deleted, click Okay. Mozilla FireFox 4.0.x and 5.0.x To clear the cache and cookies: Step 1 Step 2 Step 3 Step 4 Step 5 Step 6 Go to Tools menu. Select Clear Recent History. Select Everything from the Time Range to Clear drop-down list. Select Details. Select: 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 Step 2 Step 3 Step 4 Step 5 Select Start > All Programs > Administrator Tools > Server Manager. The Server Summary page appears. Click Configure IE ISC under Security Information. The Internet Explorer Enhanced Security Configuration popup appears. Click the Off option for both Administrators and Users. Click OK. Restart the browser. 6-54

197 Chapter 6 Performing Installation of Cisco Prime LMS 4.1 Logging into Cisco Prime LMS Server Logging into Cisco Prime LMS Server After you have accessed the LMS server, to login for the first time, do the following: Step 1 Step 2 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. 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.1 for more information. 6-55

198 Uninstalling LMS 4.1 Chapter 6 Performing Installation of Cisco Prime LMS 4.1 Uninstalling LMS 4.1 This section contains: Before You Begin Uninstallation Uninstalling LMS 4.1 on Solaris Uninstalling LMS 4.1 on Windows Before You Begin Uninstallation The following are some precautionary notes on uninstallation that you must read: 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.1. Note 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.1 on Solaris To uninstall LMS 4.1 on a Solaris system: Step 1 Step 2 Enter the following commands as root to start the uninstall script: # cd /opt/cscopx/bin/ where /opt/cscopx is the default installation directory. From the /opt/cscopx/bin/ directory, enter the./uninstall.sh command Note 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_ _ log. If IPSLA Performance Management is installed on the server, the following message appears: LMS is currently installed in the server. Delete the configured collectors to remove the corresponding collector entries from the source routers, and uninstall LMS. 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-56

199 Chapter 6 Performing Installation of Cisco Prime LMS 4.1 Uninstalling LMS 4.1 Step 3 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. 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 the LMS 4.1 have been removed. /etc/inetd.conf Ensure that the LMS TFTP entry is removed. Uninstalling LMS 4.1 on Windows To uninstall LMS 4.1 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. If IPSLA Performance Management is installed on the server, the following message appears: LMS is currently installed in the server. Delete the configured collectors to remove the corresponding collector entries from the source routers, and uninstall LMS. CLick "Cancel" to quit the uninstall and manually delete the collectors using IPSLA Performance Management CLI. Click "Yes" to delete the collectors in the device and continue with the uninstall. Click "No" to continue with uninstall without deleting the collectors in device. Default is 'No'. 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 6-57

200 Re-installing LMS 4.1 Chapter 6 Performing Installation of Cisco Prime LMS 4.1 The uninstallation proceeds and the Uninstallation Complete dialog box appears after uninstallation completes. If the uninstallation completes with errors, the following error message appears: Step 2 Installation of Cisco Prime Lan Management Solution 4.1 completed. Some errors occured during installation. See NMSROOT/Cisco_Prime_uninstall_YYYYMMDD_hhmmss.log for details. Select Yes, I want to restart my computer now and click Finish. 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-installing LMS 4.1 Re-installation is installing the product over the existing one without performing an uninstallation. You can re-install LMS 4.1 by running the installation program on the system currently running the product. LMS 4.1 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.1, follow the similar procedure as detailed in Performing Installation of LMS 4.1. 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: 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. 6-58

201 CHAPTER 7 Migrating Data to Cisco Prime LAN Management Solution 4.1 This chapter describes how to migrate data to LMS 4.1, and contains the following sections: Overview of Migration to LMS 4.1 Scope of Data Migration Migrating Data From LMS 3.2, LMS 3.2 SP1, LMS 4.0, or LMS Guidelines to Post-Upgrade Activities Overview of Migration to LMS 4.1 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.1 and then perform remote data migration. LMS 4.1 does not support direct upgrade from previous versions other than LMS 4.0/ Data Migration to LMS 4.1 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. 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 7-1

202 Scope of Data Migration Chapter 7 Migrating Data to Cisco Prime LAN Management Solution 4.1 Notes for Remote Migration When you back up the data from LMS 3.x and restore the data on LMS 4.1, a warning message appears stating that there is a mismatch in the applications data. You can ignore this message and continue the data restore. Scope of Data Migration 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.1. 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 LMS LMS 4.1 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 Data Migration to LMS 4.1 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. 7-2

203 Chapter 7 Migrating Data to Cisco Prime LAN Management Solution 4.1 Scope of Data Migration 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/3.2 SP1 and LMS 4.0/4.0.1 for Windows and Solaris. For Soft Appliance, they are migrated only when you restore data from LMS 3.2 SP1 and LMS 4.0/4.0.1/4.1. Policy Configuration Policy Configuration are migrated only when you restore data from LMS 3.2/3.2 SP1 and LMS 4.0/4.0.1 for Windows and Solaris. For Soft Appliance, they are migrated only when you restore data from LMS 3.2 SP1 and LMS 4.0/4.0.1/4.1. Logrot Configuration Logrot Configuration are migrated only when you restore data from LMS 3.2/3.2 SP1 and LMS 4.0/4.0.1 for Windows and Solaris. For Soft Appliance, they are migrated only when you restore data from LMS 3.2 SP1 and LMS 4.0/4.0.1/4.1. DCR Exclude list DCR Exclude list are migrated only when you restore data from LMS 3.2/3.2 SP1 and LMS 4.0/4.0.1 for Windows and Solaris. For Soft Appliance, they are migrated only when you restore data from LMS 3.2 SP1 and LMS 4.0/4.0.1/4.1. Unreachable Device Polling Settings Unreachable Device Polling Settings are migrated only when you restore data from LMS 3.2/3.2 SP1 and LMS 4.0/4.0.1 for Windows and Solaris. For Soft Appliance, they are migrated only when you restore data from LMS 3.2 SP1 and LMS 4.0/4.0.1/4.1. LDAP Configuration LDAP Configuration are migrated only when you restore data from LMS 3.2/3.2 SP1 and LMS 4.0/4.0.1 for Windows and Solaris. For Soft Appliance, they are migrated only when you restore data from LMS 3.2 SP1 and LMS 4.0/4.0.1/

204 Scope of Data Migration Chapter 7 Migrating Data to Cisco Prime LAN Management Solution 4.1 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.1 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.1 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.1 server and have been managing some set of the devices then if you migrate the older version LMS data into LMS 4.1 server, after migration the backed up data will be restored in the LMS 4.1 server and the UDM policy will be set as Managed By All devices. 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.1 While restoring ACS backup from LMS 3.2 or LMS 3.2 SP1, the Authentication mode will be changed to Local CiscoWorks Authorization 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.1 Case1: If you have "Group1" in CS, CM and RME (part of LMS versions earlier to LMS 4.0) while backing up data from an earlier version of LMS then after restoring the backed up data in LMS 4.1, "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 an earlier version of LMS then after restoring the backed up data in LMS4.1, "Group1" of both CM and RME will be deleted. 7-4

205 Chapter 7 Migrating Data to Cisco Prime LAN Management Solution 4.1 Scope of Data Migration Network Topology, Layer 2 Services and User Tracking Data Migration Scope Network Topology, Layer 2 Services and User Tracking data in LMS 4.1 (known as CM in earlier LMS versions) can be backed up using either the Normal or the Selective mode. Identity 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.1: 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 Preferences This is applicable only for upgrade Topology layouts Manually 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/3.2 SP1 or LMS 4.0/4.0.1 for Windows and Solaris. For Soft Appliance, they are migrated only when you restore data from LMS 3.2 SP1 and LMS 4.0/4.0.1/4.1. Selective Backup When you run a selective data backup from CLI, all the data mentioned above gets backed up except: Device Details Port and VLAN Details Campus Archives, UT Archives and VNM Archives 7-5

206 Scope of Data Migration Chapter 7 Migrating Data to Cisco Prime LAN Management Solution 4.1 Inventory, Config and Image Management Data Migration Scope Inventory, Config and Image Management data in LMS 4.1 (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.1: 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

207 Chapter 7 Migrating Data to Cisco Prime LAN Management Solution 4.1 Scope of Data Migration 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/3.2 SP1 and LMS 4.0/4.0.1 for Windows and Solaris. For Soft Appliance, they are migrated only when you restore data from LMS 3.2 SP1 and LMS 4.0/4.0.1/4.1. User-defined tasks NetShow: NetShow jobs Output archives Commandsets Software Management View/Edit Preferences Update Upgrade Information Software Management repository images All jobs in a Job Browser System Preferences Application Log Level Settings Job Purge RME Device Attributes RME Secondary Credentials Collection Failure Notification 7-7

208 Scope of Data Migration Chapter 7 Migrating Data to Cisco Prime LAN Management Solution 4.1 Inventory Inventory Change Filter System Job Schedule Cisco.com Fetch Interval Inventory jobs Device details Inventory Collection status DCA jobs Device Management state User -defined groups Syslog details Set Backup Policy Set Purge Policy Force Purge Automated actions Message filters Custom reports Syslog messages for the past 14 days Report jobs and archives Port and Module group administration Port and Module group administration are migrated only when you restore data from LMS 3.2/3.2 SP1 and LMS 4.0/4.0.1 for Windows and Solaris. For Soft Appliance, they are migrated only when you restore data from LMS 3.2 SP1 and LMS 4.0/4.0.1/4.1. Port groups Module groups Template Center Template Center jobs WorkCenters EnergyWise jobs Identity jobs ASP jobs SI jobs SI profiles SI configs 7-8

209 Chapter 7 Migrating Data to Cisco Prime LAN Management Solution 4.1 Scope of Data Migration Selective Backup When you run a selective data backup from CLI, all the data mentioned above gets backed up except: 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.1 (known as DFM in earlier LMS versions), can be backed up using either the Normal or the Selective mode. Normal Backup The following data gets migrated when you upgrade to LMS 4.1: Device list: The migration procedure adds devices to LMS Device and Credentials Repository (DCR). To automatically manage devices from DCR in LMS 4.1, 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, , trap and syslog settings) Notification customization changes Event sets User defined and customizable groups JRM Jobs 7-9

210 Scope of Data Migration Chapter 7 Migrating Data to Cisco Prime LAN Management Solution 4.1 Events details Fault History details SNMP Settings SNMP Settings are migrated only when you restore data from LMS 3.2/3.2 SP1 and LMS 4.0/4.0.1 for Windows and Solaris. For Soft Appliance, they are migrated only when you restore data from LMS 3.2 SP1 and LMS 4.0/4.0.1/4.1. Subject customization settings Subject customization settings are migrated only when you restore data from LMS 3.2/3.2 SP1 and LMS 4.0/4.0.1 for Windows and Solaris. For Soft Appliance, they are migrated only when you restore data from LMS 3.2 SP1 and LMS 4.0/4.0.1/4.1. Selective Backup When you run a selective data backup from CLI, all the data mentioned above gets backed up except: Events details Fault History details IPSLA Performance Management Data Migration Scope IPSLA Performance Management in LMS 4.1 (known as IPM in earlier LMS versions), can be backed up using either the Normal or the Selective mode. Normal Backup The following data gets migrated when you upgrade to LMS 4.1: IPSLA database Contains 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 NMSROOT/MDC/tomcat/webapps/ipm/system_reports /var/adm/cscopx/files/ipm/ and /opt/cscopx/mdc/tomcat/webapps/ipm/archive_charts 7-10

211 Chapter 7 Migrating Data to Cisco Prime LAN Management Solution 4.1 Scope of Data Migration Windows NMSROOT\MDC\tomcat\webapps\ipm\system_reports NMSROOT\CSCOpx\files\ipm\ and NMSROOT\CSCOpx\MDC\tomcat\webapps\ipm\archive_charts When you migrate from LMS 3.0 or LMS3.0 December 2007 Update or LMS 3.1 to LMS 4.0 and then install LMS 4.1, the following data gets migrated: IPSLA database contains 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.1, the user s device preferences are migrated. In LMS 4.1, CiscoView is available at Inventory > Tools > CiscoView. Device Performance Management Data Migration Scope Device Performance Management in LMS 4.1 (known as HUM in earlier LMS versions) can be backed up using either the Normal or the Selective mode.normal Backup The following data gets migrated when you upgrade to LMS 4.1: Configuration Data Threshold Violation Scripts Reports Template Configuration Database Poller Configuration Threshold Configuration Admin Settings Polled data Threshold Violation data Summarization data Job information. 7-11

212 Scope of Data Migration Chapter 7 Migrating Data to Cisco Prime LAN Management Solution 4.1 Trendwatch Configurations Trendwatch Configurations are migrated only when you restore data from HUM 1.2. TrendWatch Violation data TrendWatch Violation data are migrated only when you restore data from HUM 1.2 and LMS 4.1. Trap Receiver Groups Trap Receiver Groups are migrated only when you restore data from HUM 1.2 and LMS 4.1. Syslog Receiver Groups Syslog Receiver Groups are migrated only when you restore data from HUM 1.2 and LMS 4.1. 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. The following data gets migrated when you restore LMS 3.x (HUM) backup in LMS 4.1: 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/3.2 SP1/4.0/4.0.1 backup for Windows and Solaris. For Soft Appliance, they are migrated only when you restore data from LMS 3.2 SP1 and LMS 4.0/4.0.1/4.1. Job Information / Reports (system defined and user defined) Suspended job instances will be moved to scheduled state. 7-12

213 Chapter 7 Migrating Data to Cisco Prime LAN Management Solution 4.1 Scope of Data Migration Admin Settings Data Purge, Job Purge and Poll Settings (SNMP retry / timeout, Failure frequency / notification details) Trap Receiver Groups and Syslog Receiver Groups (this is applicable only if you restore LMS 3.2/3.2 SP1/4.0/4.0.1 backup for Windows and Solaris. For Soft Appliance, they are migrated only when you restore data from LMS 3.2 SP1 and LMS 4.0/4.0.1/4.1). 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/3.2 SP1/4.0/4.0.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 LMS 3.2/3.2 SP1/4.0/4.0.1 backup for Windows and Solaris. For Soft Appliance, they are migrated only when you restore data from LMS 3.2 SP1 and LMS 4.0/4.0.1/4.1). 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.x) will be migrated after remote upgrade. CiscoWorks Assistant Data Migration Scope CiscoWorks Assistant is not part of LMS

214 Scope of Data Migration Chapter 7 Migrating Data to Cisco Prime LAN Management Solution 4.1 Figure 7-1 shows the migration of data from LMS 2.6 to LM S

215 Chapter 7 Migrating Data to Cisco Prime LAN Management Solution 4.1 Scope of Data Migration Figure 7-1 Migrating Data from LMS 2.6 to LMS 3.2 (Old Picture, will be updated in the next draft) LMS 2.6 CiscoWorks Common Services Resource Manager Essentials Campus Manager Device Fault Manager Internetwork Performance Monitor 2.6 CiscoView Integration Utility 1.6 LMS 3.2 CiscoWorks Common Services 3.3 Resource Manager Essentials 4.3 Campus Manager 5.2 Device Fault Manager 3.2 Internetwork Performance Monitor 4.2 CiscoView Integration Utility 1.9 CiscoWorks LMS Portal 1.2 CiscoWorks Assistant 1.2 Health and Utilization Monitor 1.2 Operating System Solaris 8, Solaris 9 Operating System Solaris 9, Solaris Figure 7-2 shows the migration of data from LMS 2.6 SP1 to LMS 4.0 Figure 7-2 Migrating Data from 2.6 SP1 to 3.2 LMS 2.6 SP1 CiscoWorks Common Services Resource Manager Essentials Campus Manager Device Fault Manager Internetwork Performance Monitor 2.6 CiscoView Integration Utility LMS 3.2 CiscoWorks Common Services 3.3 Resource Manager Essentials 4.3 Campus Manager 5.2 Device Fault Manager 3.2 Internetwork Performance Monitor 4.2 CiscoView Integration Utility 1.9 CiscoWorks LMS Portal 1.2 CiscoWorks Assistant 1.2 Health and Utilization Monitor 1.2 Operating System Solaris 8, Solaris 9 Operating System Solaris 9, Solaris

216 Migrating Data From LMS 3.2, LMS 3.2 SP1, LMS 4.0, or LMS Chapter 7 Migrating Data to Cisco Prime LAN Management Solution 4.1 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. \\Reviewers, how will this note change w.r.t to the LMS 4.1? 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. Migrating Data From LMS 3.2, LMS 3.2 SP1, LMS 4.0, or LMS This section explains how to migrate data from LMS 3.2, LMS 3.2 SP1, LMS 4.0, or LMS Figure 7-3 shows the migration of data from LMS 3.0 to LMS 4.1. Figure 7-3 Migrating Data from LMS 3.0 to LMS 4.1 (this figure will be updated) LMS 3.0 CiscoWorks Common Services 3.1 Resource Manager Essentials 4.1 Campus Manager 5.0 Device Fault Manager 3.0 Internetwork Performance Monitor 4.0 CiscoView CiscoWorks LMS Portal 1.0 CiscoWorks Assistant 1.0 Integration Utility 1.7 Health and Utilization Monitor 1.0 (Add-on and separately licensed) Operating System Solaris 9, Solaris 10 LMS 3.2 CiscoWorks Common Services 3.3 Resource Manager Essentials 4.3 Campus Manager 5.2 Device Fault Manager 3.2 Internetwork Performance Monitor 4.2 CiscoView Integration Utility 1.9 CiscoWorks LMS Portal 1.2 CiscoWorks Assistant 1.2 Health and Utilization Monitor 1.2 Operating System Solaris 9, Solaris Figure 7-4 shows the migration of data from LMS 3.0 December 2007 Update to LMS

217 Chapter 7 Migrating Data to Cisco Prime LAN Management Solution 4.1 Migrating Data From LMS 3.2, LMS 3.2 SP1, LMS 4.0, or LMS Figure 7-4 Migrating Data from LMS 3.0 December 2007 Update to LMS 4.1 (this figure will be updated) LMS 3.0 December 2007 Update CiscoWorks Common Services Resource Manager Essentials 4.1 Campus Manager 5.0 Device Fault Manager Internetwork Performance Monitor CiscoView CiscoWorks LMS Portal CiscoWorks Assistant Integration Utility Health and Utilization Monitor 1.0/1.0.2 (Add-on and separately licensed) Operating System Solaris 9, Solaris 10 LMS 3.2 CiscoWorks Common Services 3.3 Resource Manager Essentials 4.3 Campus Manager 5.2 Device Fault Manager 3.2 Internetwork Performance Monitor 4.2 CiscoView Integration Utility 1.9 CiscoWorks LMS Portal 1.2 CiscoWorks Assistant 1.2 Health and Utilization Monitor 1.2 Operating System Solaris 9, Solaris Figure 7-5 shows the migration of data from LMS 3.1 to LMS 3.2. Figure 7-5 Migrating Data from LMS 3.1 to LMS 4.1 (this figure will be updated) LMS 3.1 CiscoWorks Common Services 3.2 Resource Manager Essentials 4.2 Campus Manager 5.1 Device Fault Manager 3.1 Internetwork Performance Monitor 4.1 CiscoView Integration Utility 1.8 CiscoWorks LMS Portal 1.1 CiscoWorks Assistant 1.1 Health and Utilization Monitor 1.1/1.1.2 Operating System Solaris 9, Solaris 10 LMS 3.2 CiscoWorks Common Services 3.3 Resource Manager Essentials 4.3 Campus Manager 5.2 Device Fault Manager 3.2 Internetwork Performance Monitor 4.2 CiscoView Integration Utility 1.9 CiscoWorks LMS Portal 1.2 CiscoWorks Assistant 1.2 Health and Utilization Monitor 1.2 Operating System Solaris 9, Solaris Remote Migration From LMS 3.0 or LMS 3.0 December 2007 Update or LMS 3.1 This section explains the procedure of Migrating Data on Solaris to a remote machine. 7-17

218 Migrating Data From LMS 3.2, LMS 3.2 SP1, LMS 4.0, or LMS Chapter 7 Migrating Data to Cisco Prime LAN Management Solution 4.1 In this section, the machine that has LMS 3.2, LMS 3.2 SP1, LMS 4.0, or LMS is referred to as Machine A and the remote machine where you need to install LMS 4.1 and restore the data, is referred to as Machine B. Note We recommend you to stop the daemon manager, before you take the backup of LMS data. This section contains: Migrating Data on Solaris Migrating Data on Windows Migrating Data on Soft Appliance Migrating Data on Solaris To migrate LMS 3.2, LMS 3.2 SP1, LMS 4.0, or LMS data to a remote machine: Step 1 Log in as root into Machine A. Step 2 Back up LMS 3.2, LMS 3.2 SP1, LMS 4.0, or LMS 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 Step 3 Log in as root into Machine B. Step 4 Install LMS 4.1. Step 5 Step 6 Step 7 Transfer the backup directory BKP that contains the LMS 3.x data as a compressed file (example.tar) from Machine A to any temporary location. Stop the daemon manager by entering: /etc/init.d/dmgtd stop Restore the backed up data by entering: NMSROOT/bin/perl NMSROOT/bin/restorebackup.pl -d BKP [-t temporary_directory] 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/restorebackup.pl -d /opt/bkp. For more details, see Syntax and Usage for Restore Script. See Notes for Remote Migration. You can also restore data from LMS 3.2, LMS 3.2 SP1, LMS 4.0, or LMS to the LMS 4.1 server with Symantec Veritas or VMware HA implementation. 7-18

219 Chapter 7 Migrating Data to Cisco Prime LAN Management Solution 4.1 Migrating Data From LMS 3.2, LMS 3.2 SP1, LMS 4.0, or LMS Step 8 For details on High Availability (HA) implementation using Symantec Veritas, see Setting Up Cisco Prime LMS in High Availability and Disaster Recovery Environment. For details on High Availability (HA) implementation using VMware, see Setting Up Cisco Prime LMS for High Availability, Live Migration, and Storage VMotion Using VMware. Examine the log files in the following location to verify that the data was restored. The files are: /var/adm/cscopx/log/restorebackup.log /var/adm/cscopx/log/migration.log /var/adm/cscopx/log/rme_base.log Note Step 9 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 Migrating Data on Windows To migrate LMS 3.2, LMS 3.2 SP1, LMS 4.0, and LMS data to a remote machine: Step 1 Log in as administrator into Machine A. Step 2 Back up LMS 3.2, LMS 3.2 SP1, LMS 4.0, or LMS data. To do this 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 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.1. Step 5 Step 6 Step 7 Copy the backup directory BKP that contains the LMS 3.x data from Machine A to any temporary location. Stop the daemon manager by entering: net stop crmdmgtd Restore the backed up data by entering: NMSROOT\bin\perl NMSROOT\bin\restorebackup.pl -d BKP [-t temporary_directory] where BKP is the backup directory. You must enter the absolute path for BKP. For example, if BKP is under C:\, enter the path as NMSROOT\bin\perl NMSROOT\bin\restorebackup.pl -d C:\BKP. For more details, see Syntax and Usage for Restore Script. See Notes for Remote Migration. 7-19

220 Migrating Data From LMS 3.2, LMS 3.2 SP1, LMS 4.0, or LMS Chapter 7 Migrating Data to Cisco Prime LAN Management Solution 4.1 You can also restore data from LMS 3.2, LMS 3.2 SP1, LMS 4.0, or LMS to the LMS 4.1 server with Symantec Veritas or VMware HA implementation. 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. Note Ensure that the passwords, HTTPS port and SMTP server details are same in both LMS 3.2, LMS 3.2 SP, LMS 4.0, or LMS server and LMS 4.1 server with Symantec Veritas implementation, while migrating data from non-ha to HA environment. Step 8 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 Note Step 9 The migration.log and rme_base.log will be created only when RME (part of earlier LMS versions) is migrated. Start the daemon manager by entering: net start crmdmgtd Migrating Data on Soft Appliance To migrate the data from Solaris to Soft Appliance: Step 1 Step 2 Step 3 Log in as root into Machine A, which is a Solaris server. Back-up the 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 Appendix E, Syntax and Usage for Backup Script. Log in as root into Machine B, which is a Soft Appliance server. Step 4 Install LMS 4.1. Step 5 Step 6 Step 7 Transfer the backup directory BKP that contains the LMS 3.2 SP1, LMS 4.0 or LMS 4.0.1, 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. Stop the daemon manager by entering: /etc/init.d/dmgtd stop Restore the backed up data by entering: 7-20

221 Chapter 7 Migrating Data to Cisco Prime LAN Management Solution 4.1 Guidelines to Post-Upgrade Activities Step 8 NMSROOT/bin/perl NMSROOT/bin/restorebackup.pl -d BKP [-t temporary_directory] 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/restorebackup.pl -d /opt/bkp. For more details, see Syntax and Usage for Restore Script. See Notes for Remote Migration. 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 Note Step 9 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 Guidelines to Post-Upgrade Activities This section contains: Guidelines for Fault Management Post-Upgrade Activities in LMS 4.1 Guidelines for Common Services Post-Upgrade Activities LMS 4.1 AAA Methods Resetting the Login Module Guidelines for Fault Management Post-Upgrade Activities in LMS 4.1 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: 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. 7-21

222 Guidelines to Post-Upgrade Activities Chapter 7 Migrating Data to Cisco Prime LAN Management Solution 4.1 Step 2 Step 3 Enter the port number in the Receiving Port entry box. Click Apply. 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.1 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. Guidelines for Common Services Post-Upgrade Activities This section contains the LMS Authorization, Authentication, and Accounting (AAA) methods. LMS 4.1 AAA Methods LMS 4.1 supports only one AAA mode; CiscoWorks Local Mode. CiscoWorks Local Mode LMS 4.1 server supports the following Login Modules in CiscoWorks Local Mode mode: CiscoWorks Local KerberosLogin Local NT System (Windows only) Local Unix System (Solaris only) MS Active Directory RADIUS TACACS+ LMS 4.1 uses CiscoWorks server authentication (CiscoWorks Local Mode) to authenticate users and authorize them to access LMS. 7-22

223 Chapter 7 Migrating Data to Cisco Prime LAN Management Solution 4.1 Guidelines to Post-Upgrade Activities However, if you select a Login module other than CiscoWorks Local, you can only perform authentication and not authorization. You can perform authorization only through CiscoWorks Local. 7-23

224 Guidelines to Post-Upgrade Activities Chapter 7 Migrating Data to Cisco Prime LAN Management Solution 4.1 Resetting the Login Module You can run the following commands to reset the Login Module to CiscoWorks local mode: On Solaris and Soft Appliance: Step 1 Step 2 Step 3 Stop the LMS system by entering: /etc/init.d/dmgtd stop Run the following script: NMSROOT/bin/perl NMSROOT/bin/ResetLoginModule.pl Start the LMS system by entering: /etc/init.d/dmgtd start On Windows: Step 1 Step 2 Step 3 Stop the LMS system by entering: net stop crmdmgtd Run the following script: NMSROOT\bin\perl NMSROOT\bin\ResetLoginModule.pl Start the LMS system by entering: net start crmdmgtd 7-24

225 CHAPTER 8 Troubleshooting and FAQs This chapter provides troubleshooting information for LMS installation and data migration. It contains: Checking Processes After Installation Viewing and Changing Process Status Contacting Cisco Technical Assistance Center (TAC) Understanding Installation Error Messages Troubleshooting Errors in Data Migration Frequently Asked Questions Checking Processes After Installation 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. Viewing and Changing Process Status 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. 8-1

226 Viewing and Changing Process Status Chapter 8 Troubleshooting and FAQs To view or change the process status: Step 1 Step 2 Select Admin > System > Server Monitoring > Processes. The Process Management page appears. 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: /etc/init.d/dmgtd stop To start all processes from the server, enter: /etc/init.d/dmgtd start 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. 8-2

227 Chapter 8 Troubleshooting and FAQs Contacting Cisco Technical Assistance Center (TAC) Contacting Cisco Technical Assistance Center (TAC) 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.1. 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 the generated report to Cisco TAC. To generate the report: Select Admin > System > Server Monitoring > Collect Server Information from the menu Understanding Installation Error Messages 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 cannot proceed because you are not logged in as an administrator. The setup program has discovered HP OpenView services running. This will lock some of the Cisco Prime LMS dlls. Stop all HP OpenView services before installing Cisco Prime LMS. Decompression failed on file. The error was for error code per CompressGet. You are not logged into Windows with administrator privileges. HP Network Node Manager (HPNNM) or NetView is running on the same system. When you downloaded Cisco Prime LMS, a transmission error occurred or the installation medium is damaged. Log into Windows with local administrator privileges and try installing again. Stop all HP OpenView services and continue to install Cisco Prime LMS. Retry the download. If you still have errors, contact your technical support representative. 8-3

228 Understanding Installation Error Messages Chapter 8 Troubleshooting and FAQs Table 8-1 Installation Error Messages (continued) Error Message Possible Reasons User Action General file transmission error. When you downloaded Retry the download. If you still have Cisco Prime LMS, a errors, contact your technical support Please check your target location transmission error might representative. and try again. Error number: have occurred. error code. Severe: Cannot run the dependency handler. Cannot write infofile or Cannot create infofile. Cannot stop service servicename. UseDLL failed for dll. function failed: DLL function not found. When you have downloaded 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. Retry the download. A file-write operation failed. Run the file system checking utility, then repeat the installation. The installation (or reinstallation) tried to stop the service servicename unsuccessfully. dll should be available at any time for any process, but Windows did not load it. dll should be available at any time for any process, but Windows did not load it. 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. 1. Select Control Panel > Services and stop service servicename manually. 2. Continue to install or uninstall. 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 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. 8-4

229 Chapter 8 Troubleshooting and FAQs Understanding Installation Error Messages Table 8-1 Installation Error Messages (continued) Error Message Possible Reasons User Action OpenFile failed: pathname. A file open operation failed. 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. Launch of isql script failed. The product should not be installed in a root directory. The product should not be installed in a remote directory. The selected directory is not empty. Mixing new and existing files can cause severe problems during installation. The installer requires temporary workspace. 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). Setting file permissions failed because you may not be allowed to change them. The existing database file is corrupted or the previous version of LMS 4.1 is destroyed. The problem may occur during reinstallation. You tried to install the product in a directory of a drive (for example, c:\ or d:\) that is not supported. You tried to install the product in a directory of a drive that is remotely mounted or using the UNC pathname. You tried to install in a directory that contains some files. There is not enough drive space for temporary installation files. 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). Log in as administrator. If you are installing on a FAT file system, LMS 4.1 cannot provide file security. Contact your technical support representative. Select a directory other than the root directory to install the product. Select a directory on a local hard-drive. Remove all files from directory or choose another directory to install the product. Make more drive space available (%TEMP%), then rerun installation. Install LMS on another server not configured as PDC / BDC. 8-5

230 Understanding Installation Error Messages Chapter 8 Troubleshooting and FAQs Table 8-1 Installation Error Messages (continued) Error Message Possible Reasons User Action You are attempting to install LMS on an unsupported operating system. The installation will exit when you close this message. You are attempting to install Cisco Prime LMS on operating system and service pack. Please run installation again on a supported platform. Do you want to proceed? 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. 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. 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. You are trying to install the application on an operating system that does not match System Requirements for the product. You are trying to install the application on an operating system that does not match System Requirements for the product You are trying to install the product from a copy of the DVD or from the DVD drive of another system in the network. You are trying to install the product from another system in the network. Upgrade the Operating System on the Server to a supported version Or Install LMS on another server running a supported Operating System. Run installation again on a supported platform. Copy the installable image to a local drive or use local DVD drive. Copy the installable image to a local drive or use local CD drive. 8-6

231 Chapter 8 Troubleshooting and FAQs Understanding Installation Error Messages Table 8-1 Installation Error Messages (continued) Error Message Possible Reasons User Action The default (or selected) drive drive has a(n) file-system-type file system. This file system does not support file security. The cluster size is cluster size bytes, therefore disk space requirements can be high. 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. You may not have permissions on the default directory or you have specified a read-only device. You are trying to install onto a drive with a non-ntfs (FAT or FAT32) file system. The file system may not support security. The cluster size may be bigger than 4096 bytes. The destination directory contains spaces in the directory name and the directory name cannot be converted to a MS-DOS format. The installation program cannot find one of the built-in Windows user groups. This prohibits LMS 4.1 security setup. The installation program cannot find one of the built-in Windows user groups. This prohibits the setup of LMS 4.1 security. You may not have permissions on the directory. Click on the directory on which you want to install LMS. 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. 1. Check the Operating System. 2. Reinstall Windows if necessary, 3. Rerun LMS 4.1 installation. 1. Check the Operating System. 2. Reinstall Windows if necessary, 3. Rerun LMS 4.1 installation. Select another destination directory. 8-7

232 Understanding Installation Error Messages Chapter 8 Troubleshooting and FAQs Table 8-1 Installation Error Messages (continued) Error Message Possible Reasons User Action Could not set file permissions. The installation program cannot set file permissions. Most likely causes are: Correct the problem. Rerun installation program. task_name is already running! Wait for it to complete and click OK. Cannot create/open log file. Error creating / modifying casuser - name. Click Yes if you want to try again. Click No if you want the Install to terminate. Cannot find script to upgrade database. Database upgrade failed. Database upgrade result unknown. The installer has discovered HP OpenView services running. The installation might take significantly longer to complete with these services running. 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. One installation subtask is still running. The installation program could not create or open the installation log file. This error may occur if: The passwords that you entered do not match the policies set by System Administrators. Or User running the installation does not have permission to create new user on the system. Problem with database upgrade. Problem with database upgrade. Problem with database upgrade. HP OpenView services are running. 1. Wait for installation subtask to finish running. 2. Click OK to proceed. 1. Determine why the file could not be created or opened. 2. Correct the problem, then rerun installation. Common causes are lack of disk space or write protection on file. 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. A screen appears where you can re-enter the passwords. b. Correct the problem as given in the error message. Contact your technical support representative. Contact your technical support representative. Contact your technical support representative. Stop all HP OpenView services before installing LMS 4.1. You do not have to restart the system after stopping HP OpenView. 8-8

233 Chapter 8 Troubleshooting and FAQs Understanding Installation Error Messages Table 8-1 Installation Error Messages (continued) Error Message Possible Reasons User Action ODBC Driver Manager or later is required by LMS 4.1. Install ODBC first. Name lookup failed for hostname. Please configure the hostname and and then try installation. These files are currently being used by another running process. You must stop all processes listed below to proceed successfully with this installation. Click Next to proceed with the installation. Click Cancel to exit. Do you want to verify that Cisco Prime LMS files are no longer being used by running processes? Click Yes to verify that files are no longer in use and that the installation may proceed. Click No to proceed without verification. Cisco Prime LMS software requires ODBC Driver Manager version or later. Your hostname is not configured properly. Some of the executables and DLLs installed by Cisco Prime LMS are locked. Some of the executables and DLLs installed by Cisco Prime LMS are in use. 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. Configure the hostname and continue installation. 1. Stop LMS Close Browsers and make sure Cisco Prime LMS CLIs are not used at the moment. After stopping all the applications, proceed with the installation. Verify that files are no longer in use. If some files are in use, stop all processes. To do this: 1. Cancel installation. 2. Stop the Cisco Prime LMS and change the startup type from Automatic to Manual. 3. Restart the system. 4. Try to run command net start from MSDOS window. The output should not show any LMS 4.1 daemon manager running. 5. Run the installation again. 8-9

234 Understanding Installation Error Messages Chapter 8 Troubleshooting and FAQs Table 8-1 Installation Error Messages (continued) Error Message Possible Reasons User Action The instruction at location referenced memory at location. The memory cannot be read. 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. CreateService - service name - The specified service is marked for deletion. One instance of 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. 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 and installation quits You have installed Cisco Prime LMS Common Services on a Pentium IV machine. This message appears when you install Cisco Prime LMS Common Services on a Pentium IV machine. The registry entries related to the service are not deleted during the uninstallation. Cisco Prime LMS installation is already running. The backup process failed. Cisco Security Agent is enabled. Click OK, and ignore the message. The installation will continue normally. Click OK, and ignore the message. The installation will continue normally. 1. Restart the machine 2. Reinstall LMS 4.1. If the problem still exists: 1. Uninstall LMS 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. Retry backing up again. Disable the Cisco Security Agent and then start the install. 8-10

235 Chapter 8 Troubleshooting and FAQs Understanding Installation Error Messages Table 8-1 Installation Error Messages (continued) Error Message Possible Reasons User Action Install fails to start after clicking the setup.exe / holds up in post install The self extracting exe fails with the not enough disk space error. Install fails with the message "Cannot load global.properties" DB values are not getting registered and throw the ERROR: [IsDaemonManagerOff] cannot execute C:\PROGRA~1\CSCOpx\bin\pd show.cmd 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. Self extract exe will extract the contents into the temp 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. User should be logged into the server as the local administrator (not the domain admin) when doing the install. Temp directory is having long path or is not proper. The issue occurs when the system32 is not in the path variable. 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. Make minimum of 3 GB free space in the C: or temp present directory and then proceed the installation. 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. 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-11

236 Understanding Installation Error Messages Chapter 8 Troubleshooting and FAQs Table 8-1 Installation Error Messages (continued) Error Message Possible Reasons User Action Install error while configuring tomcat Error in validating a package in Solaris install During fresh install, the installation aborts. Daemon Manager down and process are not up. Installation fails in Solaris. Error "OpenService: The specified service does not exists as an installed service" while tomcat configuration during install ERROR: The following base package image is bad: <package> 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. The Daemon Manager port may be occupied by some other third party application. Stale process might be running in the memory. 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. Check whether the package has been corrupted or not by running the below command. pkgchk -d <product_directory>/disk1/packages <package> where, <product_directory> is the mounted media. Example: pkgchk -d /data/lms30/disk1/packages CSCOjcht 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 Check the port state by "nestat -na grep 42340" command. Please free the port and restart the Daemon Manager. Check the stale process by "ps -ef grep CSCO" command. And kill it manually by using the kill -9 pid then start the install. 8-12

237 Chapter 8 Troubleshooting and FAQs Understanding Installation Error Messages Table 8-1 Installation Error Messages (continued) Error Message Possible Reasons User Action Scheduled periodic backup is active even after Uninstall the build in both Solaris and Windows. 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. 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 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. Backed up license count would be mismatched with the current license count installed in the restore server. Backed up LMS license count is greater than 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. Need to apply the new license with higher count once the restore is done. 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. 8-13

238 Troubleshooting Errors in Data Migration Chapter 8 Troubleshooting and FAQs Troubleshooting Errors in Data Migration This chapter describes the errors that you might encounter during data migration and guidelines on troubleshooting those errors. This chapter contains: Common Services Data Migration Errors Inventory, Config and Image Management Data Migration Errors Network Topology, Layer 2 Services and User Tracking 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.1. 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 /etc/init.d/dmgtd stop On Windows Step 2 net stop crmdmgtd 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 8-14

239 Chapter 8 Troubleshooting and FAQs Troubleshooting Errors in Data Migration 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.1. Functionalities dsn_name dmprefix Common Services cmf Cmf Configuration Management rmeng RME Network Topology, Layer 2 Services and User Tracking ani ANI Fault Management dfmepm EPM dfminv INV dfmfh FH IPSLA Performance Management ipm Ipm Device Performance Management upm UPM Step 3 Start the LMS system by entering, On Solaris /etc/init.d/dmgtd start On Windows net start crmdmgtd 8-15

240 Troubleshooting Errors in Data Migration Chapter 8 Troubleshooting and FAQs 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. 8-16

241 Chapter 8 Troubleshooting and FAQs Troubleshooting Errors in Data Migration 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.1. 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-17

242 Troubleshooting Errors in Data Migration Chapter 8 Troubleshooting and FAQs Network Topology, Layer 2 Services and User Tracking Data Migration Errors If you encounter errors during Network Topology, Layer 2 Services and User Tracking data migration: Check for the migration logs. The relevant logs are: Solaris: /var/adm/cscopx/log/restorebackup.log /opt/cscopx/bgupgrade/cmfupgrade.log (In case of Upgrade) Windows: NMSROOT\log\restorebackup.log NMSROOT\lbgupdrade\CmfUpgrade.log (In case of Upgrade) Check the contents of the backup data file, filebackup.tar. The following is the list of Network Topology, Layer 2 Services and User Tracking related files that are backed up into the specified backup directory. Contents of the following folders are backed up as filebackup.tar under specified backup directory Windows: NMSROOT\campus\etc\cwsi\DeviceDiscovery.properties NMSROOT\campus\etc\cwsi\ANIServer.properties NMSROOT\campus\etc\cwsi\ut.properties NMSROOT\campus\etc\cwsi\discoverysnmp.conf NMSROOT\campus\etc\cwsi\datacollectionsnmp.conf NMSROOT\campus\etc\cwsi\WlseUhic.properties NMSROOT\campus\etc\cwsi\Snmpv3EngineParam.txt NMSROOT\campus\etc\cwsi\UTSnmpv3EngineParam.txt NMSROOT\campus\etc\cwsi\UTDiscoverOnTrunk.properties NMSROOT\campus\etc\cwsi\users NMSROOT\campus\etc\cwsi\archives NMSROOT\campus\etc\users NMSROOT\campus\etc\cwsi\ReportArchives NMSROOT\campus\etc\cwsi\CMReportArchives NMSROOT\campus\etc\cwsi\portsData.xml NMSROOT\campus\etc\cwsi\RouterData.xml NMSROOT\campus\etc\cwsi\vlanData.xml NMSROOT\campus\etc\cwsi\CMHP.properties NMSROOT\campus\etc\cwsi\rmeServerCred.dat NMSROOT\campus\etc\cwsi\MACDetection.properties NMSROOT\campus\etc\cwsi\OUI.properties NMSROOT\htdocs\campus\maps NMSROOT\campus\lib\classpath\com\cisco\nm\cm\ut\uhic\utlite\properties\utliteuhic.properties 8-18

243 Chapter 8 Troubleshooting and FAQs Troubleshooting Errors in Data Migration 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-19

244 Troubleshooting Errors in Data Migration Chapter 8 Troubleshooting and FAQs Fault Management Data Migration Errors If you encounter errors during Fault Management data migration: Check logs. The relevant log files are: Solaris: /var/adm/cscopx/log/restorebackup.log Windows: NMSROOT\log\restorebackup.log Check the contents of the backup data file, filebackup.tar. The following is the list of Fault Management related files or databases that are backed up into the user-defined backup directory. Contents of the following folders are backed up as filebackup.tar under specified backup directory. Solaris: NMSROOT/objects/smarts/conf NMSROOT/objects/smarts/local/repos NMSROOT/objects/smarts/local/logs NMSROOT/objects/smarts/local/conf NMSROOT/objects/dps/config NMSROOT/setup/dfm.info Windows: NMSROOT\objects\smarts\conf NMSROOT\objects\smarts\local\repos NMSROOT\objects\smarts\local\logs NMSROOT\objects\smarts\local\conf NMSROOT\objects\dps\config NMSROOT\setup\dfm.info Note NMSROOT\objects\dps\config will be backed up only when you migrate from LMS 3.0 December 2007 Update. The following database files along with corresponding database transaction log files are backed up: dfmepm.db Contains the data of the Fault Management Event Promulgation Module dfminv.db Contains the data of the Fault Management Inventory dfmfh.db Contains 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 8-20

245 Chapter 8 Troubleshooting and FAQs Troubleshooting Errors in Data Migration 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-21

246 Troubleshooting Errors in Data Migration Chapter 8 Troubleshooting and FAQs 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. 8-22

247 Chapter 8 Troubleshooting and FAQs Frequently Asked Questions Frequently Asked Questions This section provides Frequently Asked Questions (FAQs) on LMS 4.1 Installation and Data Migration and the respective solutions. This section lists the FAQs: In LMS Soft Appliance, how do I change the shell_enable password? How do I transfer files to or from the LMS Soft Appliance? Where can I find the install log files for LMS 4.1? I have LMS 3.2 applications installed on different servers. Can I migrate data from these multiple servers to one LMS 4.1 server? I have LMS 3.2/3.2 SP1 installed on Windows 2003 Server. I want to upgrade the OS to Windows 2008 Server, and also upgrade to LMS 4.1. In what order should I perform these upgrades? I have been running LMS 4.1 for sometime, and have collected a lot of data. I would like to restore an older LMS 3.2/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.1 supported? Which Windows HotFix patches are supported for LMS 4.1? Is LMS 4.1 supported on 64-bit native systems? Can I install LMS 4.1 with Internet Information Services (IIS) enabled? Which TCP and UDP ports does LMS 4.1 use? Does LMS 4.1 support virtual machines, such as VMware and VirtualPC? Can I install LMS 4.1 with Windows Domain Controller enabled? Is LMS 4.1 supported on Solaris x86 (on the x86 CPU)? Is LMS 4.1 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.1 on Solaris. I want to migrate to Windows. Do I need to get a new license for LMS 4.1 on Windows? When should I install other Network Management Systems (such as HP OpenView Network Node Manager, Netview)? Q. In LMS Soft Appliance, how do I change the shell_enable password? A. The steps to change the shell_enable password are: a. Enter the command shell_enable to access the shell. b. Enter the shell password. This will be same as the sysadmin password that you provided during installation. c. Re-enter the shell 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. 8-23

248 Frequently Asked Questions Chapter 8 Troubleshooting and FAQs Q. Where can I find the install log files for LMS 4.1? 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.1 server? A. No, this option is not supported. Q. I have LMS 3.2/3.2 SP1 installed on Windows 2003 Server. I want to upgrade the OS to Windows 2008 Server, and also upgrade to LMS 4.1. 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/3.2 SP to LMS 4.1 on Windows 2008 (SP1 & SP2) R2 Standard & Enterprise edition or Windows 2008 (SP1)Server. Q. I have been running LMS 4.1 for sometime, and have collected a lot of data. I would like to restore an older LMS 3.2/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.1 supported? A. See System and Browser Requirements for Server and Client for details. Q. Which Windows HotFix patches are supported for LMS 4.1? A. For LMS 4.1, we have tested all the Windows HotFix patches released up to July 2010 that have an impact on LMS: Q. Is LMS 4.1 supported on 64-bit native systems? A. Yes, LMS 4.1 is supported on native 64-bit systems. See Operating System Requirements for more information. Q. Can I install LMS 4.1 with Internet Information Services (IIS) enabled? A. Yes, you can install. If you click No you must stop IIS services before installing LMS 4.1. 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.1 use? A. See LMS 4.1 Port Usage for details. Q. Does LMS 4.1 support virtual machines, such as VMware and VirtualPC? 8-24

249 Chapter 8 Troubleshooting and FAQs Frequently Asked Questions A. Yes, LMS 4.1 supports VMware. See Server Requirements on Windows Systems, for more information. Q. Can I install LMS 4.1 with Windows Domain Controller enabled? A. No, you must disable Windows Domain Controller before installing LMS 4.1. Q. Is LMS 4.1 supported on Solaris x86 (on the x86 CPU)? A. No, LMS 4.1 is not supported on Solaris x86. Q. Is LMS 4.1 supported on multi-homed server? A. Yes, LMS 4.1 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.1 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.1? 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.1, 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.1 co-exist with other CiscoWorks applications? A. No, LMS 4.1 cannot co-exist with any other CiscoWorks applications. Q. I am currently using a licensed version of LMS 4.1 on Solaris. I want to migrate to Windows. Do I need to get a new license for LMS 4.1 on Windows? A. No, you can use the same LMS 4.1 Solaris license on Windows. 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.1. See Supported Network Management Systems for more information. 8-25

250 Frequently Asked Questions Chapter 8 Troubleshooting and FAQs 8-26

251 APPENDIXA User Inputs for Installation This appendix provides information on the user inputs during LMS 4.1 installation. Note For information on the Installation of LMS 4.1, see Performing Installation of LMS 4.1. This appendix contains: User Inputs for Typical Installation User Inputs for Custom Installation Password Information A-1

252 User Inputs for Typical Installation Appendix A User Inputs for Installation User Inputs for Typical Installation Enter the following information while installing for the first time in Typical mode: Table A-1 User Inputs for New Installation: Typical Settings Password for admin user (Windows and Solaris) Password for sysadmin user (Soft Appliance) Password for System Identity Account Value No default values. Enter the admin password. For more information on passwords, see Password Information. No default values. Enter the sysadmin password. For more information on passwords, see Password Information. No default values. Enter the System Identity Account password. For more information on passwords, see Password Information. Enter the following information during an upgrade installation in Typical mode: Table A-2 User Inputs for Upgrade Installation: Typical Settings Backup folder Password for system identity account Value Enter a folder for the backup data. You can also browse and select a folder. No default values. Enter the System Identity Account password. For more information on passwords, see Password Information The installation program retains the System Identity Account password if you are upgrading from LMS 2.6 and LMS Enter the following information while reinstalling in Typical mode: Table A-3 Settings Backup folder User Inputs for Reinstallation: Typical Value Enter a folder for the backup data. You can also browse and select a folder. User Inputs for Custom Installation This section contains: User Inputs for New Installation (Custom) User Inputs for Reinstallation (Custom) A-2

253 Appendix A User Inputs for Installation User Inputs for Custom Installation User Inputs for New Installation (Custom) Enter the following information while installing for the first time in Custom mode: Table A-4 User Inputs for a New Installation: Custom Settings Destination folder Password for users admin and guest (Mandatory) Password for System Identity Account (Optional) Password for user casuser This is for Windows only. (Optional) Password for the Common Services database. (Mandatory) Web server settings: (Mandatory) HTTPS port Administrator s address SMTP server name Data for the Self-signed Certificate: (Optional) Country Code State City Organization Name Organization Unit Name Host name Address Value 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. No default values. Enter the admin and guest password. For more information on passwords, see Password Information. No default values. Enter the system identity account password. For more information on passwords, see Password Information. The password is generated randomly if you leave the field blank. Enter the database password. For more information on passwords, see Password Information. The default values are: Port number 443. See Important Note for Configuring Port Numbers for more information. yourusername@example.com localhost By default, the self-signed certificate is generated using the organization that Windows is registered to, and the host name. You must enter the host name. You can leave the other fields blank. A-3

254 User Inputs for Custom Installation Appendix A User Inputs for Installation 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 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. User Inputs for Reinstallation (Custom) Enter the following information during an upgrade installation in Custom mode: Table A-5 User Inputs for an Upgrade Installation: Custom Settings Backup folder Password for users admin and guest (Optional) Password for system identity account (Mandatory) Password for the user casuser (Optional) Password for the Common Services Database (Optional) Value Enter a folder for the backup data. You can also browse and select a folder. You may change the passwords for the admin and guest users. To keep the existing passwords, leave the fields blank. 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 No default values. Enter the System Identity Account password. For more information on 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. 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. However, this is not applicable for Solaris. Leave the fields blank to use the existing password. A-4

255 Appendix A User Inputs for Installation User Inputs for Custom Installation Table A-5 User Inputs for an Upgrade Installation: Custom (continued) Settings Web server settings: HTTPS port Administrator s address SMTP server name (Optional) Data for the Self-signed Certificate: (Mandatory) Country Code State City Organization Organization Unit Name Address Value You can choose to keep the existing information. You may change the Self-signed Certificate information. By default, the installation program uses the existing Self-Signed Certificate information. 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 in Custom mode: Table A-6 User Inputs for Reinstallation: Custom Settings Backup folder Destination folder Password for users admin and guest (Optional) Password for system identity account (Mandatory) Password for user casuser (Optional) Password for the Common Services Database (Optional) Value Enter a folder for the backup data. You can also browse and select a folder. The default location is System drive:\program Files\CSCOpx. We recommend that you specify a short path for the destination folder. You may change the passwords for the admin and guest users. To keep the existing passwords, leave the fields blank. You may change the passwords for the system identity account. To keep the existing passwords, leave the fields blank. 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. Leave the fields blank to retain the existing password. A-5

256 User Inputs for Custom Installation Appendix A User Inputs for Installation Table A-6 User Inputs for Reinstallation: Custom (continued) Settings Web server settings: HTTPS port Administrator s address SMTP server name (Optional) Data for the Self-signed Certificate: (Mandatory) Country Code State City Organization Name Organization Unit Name Hostname Address Value You can choose to keep the existing information. By default, the self-signed certificate is generated using the organization that Windows is registered to, and the host name. You must enter the host name. You can leave the other fields blank. A-6

257 Appendix A User Inputs for Installation Password Information Password Information This appendix provides information on the usage of passwords during installation. It contains: Password Rules for New Installation Password Rules for Re-installation Password Descriptions Password Rules for New Installation The following rules apply for a new installation: In Typical mode, admin and System Identity Account passwords are mandatory. Installation program generates guest, casuser, and database passwords randomly. In Custom mode, admin, guest, System Identity Account, and database passwords are mandatory. You can either enter the casuser password or allow the installation program to randomly generate it. Password Rules for Re-installation The following rules apply for re-installation: In Typical mode, the installation program retains passwords for admin, casuser, guest, and database. In Custom mode, you can chose to enter new admin, guest, system identity account, and database passwords or retain the existing passwords. You can either enter the casuser password or allow the installation program to randomly generate it. Password Descriptions The types of passwords are as follows: LMS Admin Password System Identity Account Password LMS Guest Password LMS Application Database Password Changing LMS Admin Password Changing casuser Password A-7

258 Password Information Appendix A User Inputs for Installation LMS Admin Password While entering the LMS Admin passwords, use a minimum of five characters. System Identity Account Password LMS Guest Password While entering the System Identity Account Passwords, use a minimum of five characters. In a multi-server environment, you must configure all systems part of your multiserver setup with the same System Identity Account password. To add a System Identity user select Admin > Trust Management > Multi Server > System Identity Setup. See the section Setting up System Identity Account in the User Guide for Administration of Cisco Prime LAN Management Solution 4.1 for more details on System Identity Account. While entering LMS Guest passwords, use a minimum of five characters. LMS Application Database Password Changing LMS Admin Password While entering LMS Application 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. 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 A-8

259 Appendix A User Inputs for Installation Password Information 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 Step 2 Step 3 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. 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: Enter the new password. To change the user password on Windows: Step 1 Step 2 Enter NMSROOT\bin\ResetPasswd.pl username at the command prompt. A message appears: Enter new password for username: Enter the new password. To change the user password on Soft Appliance: Step 1 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: Enter the new password. Changing Admin Password From GUI To change the LMS admin password from the LMS server: Step 1 Step 2 Step 3 Login as admin user. Select Admin > System > User Management > Local User Setup. The Local User Setup page appears. Click Modify My Profile. A-9

260 Password Information Appendix A User Inputs for Installation Step 4 Step 5 Step 6 Step 7 The My Profile pop-up window appears. Enter the password in the Password field. Re-enter the password in the Verify field. Enter the ID in the field. Click OK. A-10

261 Appendix A User Inputs for Installation Password Information Changing casuser Password You can change the casuser password using resetcasuser.exe. To change the casuser password, do the following: Step 1 Step 2 Step 3 At the command prompt, enter: NMSROOT\setup\support\resetCasuser.exe Three options are displayed: 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. 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-11

262 Password Information Appendix A User Inputs for Installation A-12

263 APPENDIXB User Tracking Utility 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. This section explains: Understanding UTU Hardware and Software Requirements for UTU 2.0 Downloading UTU 2.0 Installing UTU 2.0 Accessing UTU 2.0 Configuring UTU 2.0 Searching for Users, Hosts or IP Phones Using Search Patterns in UTU 2.0 Uninstalling UTU 2.0 Upgrading to UTU 2.0 Re-installing UTU 2.0 B-1

264 Understanding UTU Appendix B User Tracking Utility 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.1, 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. Hardware and Software Requirements for UTU 2.0 Table B-1 lists the minimum system requirements for UTU. Table B-1 System Requirements for UTU Requirement Type Minimum Requirements System hardware IBM PC-compatible computer with Intel Pentium processor. System software Windows 2008 Windows XP with SP2 or SP3 Windows Vista Memory (RAM) 512 MB Additional required software 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 LMS 4.1 (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 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.1/4.0.1/4.1 (Network Topology, Layer 2 Services and User Tracking) must be running, and accessible through the network B-2

265 Appendix B User Tracking Utility 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 Step 2 Step 3 Step 4 Step 5 Go to the Cisco Download Software page &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. Select a product release version from the Latest Releases folder and locate the software update to download. Locate the file CiscoWorksUserTrackingUtility2.0.zip This zip file contains CiscoWorksUserTrackingUtility2.0.exe and setup.iss file (required for silent installation). Click the Download Now button to download and save the device package file to any local directory on CiscoWorks Server. 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. This section explains: Installing UTU 2.0 in Silent Mode Installing UTU 2.0 in Normal Mode B-3

266 Installing UTU 2.0 Appendix B User Tracking Utility 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 Step 2 Step 3 Step 4 Step 5 Log into the system with local system administrator privileges. Navigate to the directory that contains CiscoWorksUserTrackingUtility2.0.exe. Double-click CiscoWorksUserTrackingUtility2.0.exe to begin installation. The User Tracking Utility Welcome screen appears. 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. Click Next. A confirmation message appears. B-4

267 Appendix B User Tracking Utility 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. Step 7 Step 8 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. 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. 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. B-5

268 Configuring UTU 2.0 Appendix B User Tracking Utility 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.1 server configurations. To configure UTU: Step 1 Step 2 Step 3 Step 4 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. Enter the name or IP Address of the server on which Campus Manager (for releases earlier than LMS 4.0), or LMS 4.1 is installed. Enter the port number of the LMS server. The default HTTP port number is You can modify the port number if required. 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

269 Appendix B User Tracking Utility Configuring UTU 2.0 Figure B-2 Enabling SSL You can modify the port number if required. See Figure B-2. Figure B-3 Enabling SSL Step 5 Step 6 Step 7 Step 8 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. Confirm the password by re-entering it. 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. Click Apply to save the changes. B-7

270 Searching for Users, Hosts or IP Phones Appendix B User Tracking Utility Searching for Users, Hosts or IP Phones 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 Step 2 Step 3 Step 4 Right-click the UTU search band. A popup menu appears with the default search criterion Host name/ip Address selected. 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. 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 in the search field. 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

271 Appendix B User Tracking Utility Searching for Users, Hosts or IP Phones Figure B-4 Certificate Viewer Step 5 Click Details to view the certificate details. You can verify the authenticity and correctness of the SSL server here. See Figure B-5. B-9

272 Searching for Users, Hosts or IP Phones Appendix B User Tracking Utility Figure B-5 Certificate Details Step 6 You can click Summary to go back to the Certificate Viewer dialog box. 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

273 Appendix B User Tracking Utility Searching for Users, Hosts or IP Phones Figure 6 UTU Search Band displaying the number of matching records Step 8 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. 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 User Name MAC Address Host IP Address Host Name Subnet Subnet Mask Device name Device IP Address VLAN Port Port Description Port State Port Speed Description Name of the user logged in to the host. Media Access Control (MAC) address of network interface card in end-user node. IP Address of the host. Name of the host discovered by User Tracking. Subnet to which the host belongs. Subnet mask of the host Name of the switch. IP Address of the switch VLAN to which the port of the switch belongs. Port number to which the host is connected. Description of the port number to which the host is connected. State of the port: Static or Dynamic. Bandwidth of the port of the switch. B-11

274 Searching for Users, Hosts or IP Phones Appendix B User Tracking Utility Table B-2 Details for Each Entry in Results Window For a User or Host Search Entry Port Duplex Last Seen Description Port Duplex configuration details on the device. 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 Phone Number MAC Address Phone IP Address CCM Address Status Phone Type Phone Description Device Name Device IP Address Port Port Description Last Seen Description IP Phone number Media Access Control (MAC) address of network interface card on the phone. IP Address of the phone. IP Address of the Cisco Call Manager Status of the phone, as known to Cisco Call Manager Model of the phone. Can be SP30, SP30+, 12S, 12SP, 12SPplus, 30SPplus, 30VIP, SoftPhone, or unknown. Description of the phone. Name corresponding to IP Address of device. IP Address of the device Port number to which the phone is connected. Description of the port to which the phone is connected. 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

275 Appendix B User Tracking Utility Using Search Patterns in UTU 2.0 Figure B-7 IP Phone Number Search Results Window Note The search results for the value you enter in the search field depends on the default search criteria. Using Search Patterns in UTU 2.0 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. B-13