lmsig40

Americas HeadquartersCisco Systems, Inc.170 West Tasman DriveSan Jose, CA 95134-1706 USAhttp://www.cisco.comTel: 408 526-4000

800 553-NETS (6387)Fax: 408 527-0883

Installing and Migrating to CiscoWorks LAN Management Solution 4.0

Text Part Number: OL-20722-01

http://www.cisco.com

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 www.cisco.com/go/trademarks. Third party trademarks mentioned are the property of their respective owners. The use of the word partner does not imply a partnership relationship between Cisco and any other company. (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.

Installing and Migrating to CiscoWorks LAN Management Solution 4.0Copyright © 1998-2010 Cisco Systems, Inc. All rights reserved.

http://www.cisco.com/go/trademarks

OL-20722-01

C O N T E N T S

SUPPLEMENTAL LICENSE AGREEMENT xi

Notices xiii

OpenSSL/Open SSL Project i-xiii

License Issues i-xiii

Preface xvii

Audience i-xvii

Document Conventions i-xviii

Product Documentation i-xix

Obtaining Documentation, Obtaining Support, and Security Guidelines i-xxi

C H A P T E R 1 Overview of CiscoWorks LAN Management Solution 4.0 1-1

Product Overview 1-1

Install and Upgrade Behavior 1-2

Upgrade and Migration Overview 1-2

Upgrading Master-Slave Server Setup 1-3

New Features in LMS 4.0 1-5

Getting Started Workflow 1-6

Navigating Menus 1-6

Work Centers 1-7

Dashboards 1-7

Search and Fault Bar 1-8

Template Center 1-8

CiscoWorks Local Role-based Access Control 1-8

Unified Grouping Services 1-9

Unified Device Manager 1-9

EnergyWise 1-10

Identity 1-11

Auto Smartports 1-11

Smart Install 1-12

Fault Monitor 1-12

Event Monitor 1-13

Troubleshooting Workflow 1-13

Report Center 1-13

iiiInstalling and Migrating to CiscoWorks LAN Management Solution 4.0

Contents

VRF-lite Support for Catalyst 3000 and Catalyst 4000 Devices 1-14

Third-Party Software and Tool Changes 1-14

Data Migration Overview 1-14

Supported Network Management Systems 1-15

Supported Devices 1-17

C H A P T E R 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-5

Link Aggregation Support in Solaris 10 2-5

Server Requirements on Solaris Systems 2-7

Server Requirements on Windows Systems 2-8

Unified Computing System (UCS) Support 2-10

Server Requirements on Virtualization Systems 2-10

System Requirements on Client Systems 2-11

Terminal Server Support for Windows Server 2-11

Solaris Patches 2-13

Required and Recommended Solaris Patches 2-13

Cluster Patches 2-14

LMS 4.0 Port Usage 2-15

Required Device Credentials for LMS Functionalities 2-19

C H A P T E R 3 Preparing to Install CiscoWorks LAN Management Solution 4.0 3-1

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

Installation Notes (For Windows Only) 3-5

Licensing Your Product 3-6

Understanding Product Ordering Options and Product Authorization Key 3-6

Ordering Physical CiscoWorks LMS 4.0 Product DVD with Printed PAK 3-6

Downloading CiscoWorks LMS 4.0 Evaluation Software and Ordering Digital PAK 3-7

Ordering Physical CiscoWorks LMS 4.0 Base Media Kit and Digital PAK 3-7

License Information 3-7

Available Licenses for LMS 4.0 3-8

Major Upgrade Kit Licenses for LMS 4.0 3-9

ivInstalling and Migrating to CiscoWorks LAN Management Solution 4.0

OL-20722-01

Contents

Licenses for Device-Level Conversion in CiscoWorks LMS 3-10

Licenses for Add-on Components to CiscoWorks LMS 4.0 3-11

License File 3-11

Evaluation Mode 3-12

LMS 50 Devices Restricted License 3-13

Add-on Licenses to Manage Additional Performance Collectors 3-13

NFR (Not For Resale) License 3-15

Installing the Licensing File 3-16

Application Scaling Numbers 3-18

Concurrent Users Supported 3-21

C H A P T E R 4 Setting Up CiscoWorks 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-11

Setting Casuser Permissions on cscopx Volume 4-12

Setting Up Veritas Volume Replication Without Clustering 4-13

Veritas Cluster Server Setup Tasks 4-14

Cluster Configuration for High Availability 4-14

Cluster Configuration for Disaster Recovery 4-19

Setting up LMS High Availability Environment on Solaris 4-22

Installing Storage Foundation HA 5.1 on Solaris 4-23

Creating Disk Groups and Volumes on Solaris Servers 4-24

Prerequisites for Configuring Disk Groups and Volumes on Solaris 4-24

Creating Disk Groups on Primary Solaris Server 4-24

Creating Volumes on Primary Solaris Server 4-25

Creating Disk Groups and Volumes on Secondary Solaris Server 4-26

vInstalling and Migrating to CiscoWorks LAN Management Solution 4.0

OL-20722-01

Contents

Installing LMS on Primary and Secondary Servers 4-27

Setting Up Veritas Volume Replication on Solaris Server 4-27

Setting Casuser Permissions on cscopx Volume on Solaris (If Required) 4-27

Setting Up Veritas Volume Replication Without Clustering On Solaris 4-28

Veritas Cluster Server Setup Tasks on Solaris 4-29

Cluster Configuration for High Availability on Solaris 4-29

Cluster Configuration for Disaster Recovery on Solaris 4-34

Moving LMS from non-HA to HA Environment 4-36

C H A P T E R 5 Setting Up CiscoWorks 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.0 Using VMware VMotion 5-7

Migrating a Virtual Machine with VMotion 5-8

Migrating a Virtual Machine with Storage VMotion 5-8

C H A P T E R 6 Performing Installation of CiscoWorks LAN Management Solution 4.0 6-1

Performing New Installation of LMS 4.0 6-2

Installing LMS 4.0 on Solaris - New 6-3

Installing LMS 4.0 on Solaris —New (Typical) 6-5

Installing LMS 4.0 on Solaris — New (Custom) 6-7

Installing LMS 4.0 on Windows - New 6-10

Installing LMS 4.0 on Windows — New (Typical) 6-12

Installing LMS 4.0 on Windows —New (Custom) 6-13

Installing LMS 4.0 in Silent Mode 6-15

Upgrading to LMS 4.0 6-17

Remote Upgrade to LMS 4.0 on Solaris 6-17

.Remote Upgrade to LMS 4.0 on Windows 6-18

Verifying the Installation 6-18

Accessing CiscoWorks Server 6-20

Clearing Cache and Cookies 6-21

Internet Explorer 8 6-21

viInstalling and Migrating to CiscoWorks LAN Management Solution 4.0

OL-20722-01

Contents

Internet Explorer 7 6-21

Mozilla FireFox 3.6 6-22

Logging into CiscoWorks Server 6-22

Uninstalling LMS 4.0 6-23

Before You Begin Uninstallation 6-23

Uninstalling LMS 4.0 on Solaris 6-23

Uninstalling LMS 4.0 on Windows 6-24

Re-installing LMS 4.0 6-25

Installing CiscoWorks LMS 4.0.x Using Windows 2008 R2 Patch 6-25

Downloading and Installing CiscoWorks LMS 4.0.x Using Windows 2008 R2 Patch 6-25

Re-installing LMS 4.0.x Using Windows 2008 R2 Patch 6-27

Verifying the LMS 4.0.x R2 Installation 6-28

C H A P T E R 7 Migrating Data to CiscoWorks LAN Management Solution 4.0 7-1

Overview of Migration to LMS 4.0 7-1

Scope of Data Migration 7-2

Common Services Data Migration Scope 7-3

Network Topology, Layer 2 Services and User Tracking Data Migration Scope 7-5

Inventory, Config and Image Management Data Migration Scope 7-6

Fault Management Data Migration Scope 7-9

IPSLA Performance Management Data Migration Scope 7-10

CiscoView Data Migration Scope 7-11

Device Performance Management Data Migration Scope 7-11

Portal Data Migration Scope 7-12

Migrating Data From LMS 2.6 or 2.6 SP1 7-13

Migrating Data on Solaris 7-13

Migrating Data on Windows 7-14

Migrating Data From LMS 3.0 or LMS 3.0 December 2007 Update or LMS 3.1 or LMS 3.2 7-16

Migrating Data on Solaris 7-16

Migrating Data on Windows 7-17

Guidelines to Post-Upgrade Activities 7-19

Guidelines for Fault Management Post-Upgrade Activities in LMS 4.0 7-19

Configuring SNMP Trap Receiving and Forwarding 7-19

Guidelines for Common Services Post-Upgrade Activities 7-20

LMS 4.0 AAA Methods 7-20

CiscoWorks Local Mode 7-20

Resetting the Login Module 7-21

viiInstalling and Migrating to CiscoWorks LAN Management Solution 4.0

OL-20722-01

Contents

C H A P T E R 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

A P P E N D I X A User Inputs for Installation A-1

User Inputs for Typical Installation A-2

User Inputs for Custom Installation A-2

Password Information A-5

Password Rules for New Installation A-5

Password Rules for Re-installation A-5

Password Descriptions A-5

CiscoWorks Admin Password A-6

System Identity Account Password A-6

CiscoWorks Guest Password A-6

LMS Application Database Password A-6

Changing CiscoWorks Admin Password A-6

Changing casuser Password A-8

A P P E N D I X 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

viiiInstalling and Migrating to CiscoWorks LAN Management Solution 4.0

OL-20722-01

Contents

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

A P P E N D I X C Installing the Remote Syslog Collector C-1

Verifying Remote Syslog Collector Server Requirement C-2

Installing the Remote Syslog Collector C-3

Installing on Solaris C-4

Installing on Windows C-4

Subscribing to a Remote Syslog Collector C-5

Starting the Remote Syslog Collector C-6

Stopping the Remote Syslog Collector C-6

Uninstalling the Remote Syslog Collector C-6

Uninstallation on Windows C-6

Uninstallation on Solaris C-7

Understanding the Syslog Collector Properties File C-7

A P P E N D I X D Syntax and Usage for Backup Script D-1

A P P E N D I X E Syntax and Usage for Restore Script E-1

IN D E X

ixInstalling and Migrating to CiscoWorks LAN Management Solution 4.0

OL-20722-01

Contents

xInstalling and Migrating to CiscoWorks LAN Management Solution 4.0

OL-20722-01

SUPPLEMENTAL LICENSE AGREEMENT

SUPPLEMENTAL LICENSE AGREEMENT FOR CISCO SYSTEMS NETWORK MANAGEMENT SOFTWARE: CISCOWORKS LAN MANAGEMENT SOLUTION

IMPORTANT-READ CAREFULLY: This Supplemental License Agreement ("SLA") contains additional limitations on the license to the Software provided to Customer under the Software License Agreement between Customer and Cisco. Capitalized terms used in this SLA and not otherwise defined herein shall have the meanings assigned to them in the Software License Agreement. To the extent that there is a conflict among any of these terms and conditions applicable to the Software, the terms and conditions in this SLA shall take precedence.

By installing, downloading, accessing or otherwise using the Software, Customer agrees to be bound by the terms of this SLA. If Customer does not agree to the terms of this SLA, Customer may not install, download, or otherwise use the Software. When used below, the term "server" refers to central processor unit.

ADDITIONAL LICENSE RESTRICTIONS

Device Restricted Versions. Customer may install and run the Software on a single server to manage up to the device count specified in the Right-To-Use statement located on the Claim Certificate received as part of the software package. When used anywhere in this SLA, a "device" means any device in the Customer's network environment which has its own IP address. Please refer to this guide for further device definition.

Customers whose requirements exceed the restricted version limit of devices must purchase another license or upgrade to a higher device support version of the Software. Device restrictions are enforced by license registration and through serial key installation.

Limitations associated with the maximum number of devices an application can support per server is specified below. Please refer to this guide for further device definition. Device restrictions are enforced by license registration and through serial key installation. The licensed device limit will always override the maximum number of devices supported per server unless the customer has purchased and registered the 5,000 or the 10,000 device license offering.

Installation and Use

The Software components are provided to Customer solely to install, update, supplement, or replace existing functionality of the applicable Network Management Software product. Some license terms, such as device count and proof of preexisting licenses may be electronically enforced. Customer may install and use the following Software components:

CiscoWorks LAN Management Solution (CiscoWorks LMS): May be installed on one (1) server in Customer's network management environment. Installing the Software and applying a single serial license key to more than two (2) servers is supported in the 5000 and 10,000 device restricted version, but the cumulative total number of devices supports cannot exceed 5000 and 10,000 respectively per serial license key. Additionally, customers who purchased and registered CiscoWorks LMS Remote Data

xiInstalling and Migrating to CiscoWorks LAN Management Solution 4.0

OL-20722-01

SUPPLEMENTAL LICENSE AGREEMENT

Collector license may only apply this license to LMS servers operating in SLAVE mode, and managing the same set of devices as the MASTER LMS server. This license is only intended for customers to run additional user defined pollers and IPSLA collectors or offload performance management functions to the second server for better server performance.

Additional Information for 5,000 Device Restricted Version for LMS 4.0

Users of CiscoWorks LMS 4.0 with 5,000 device restricted licensing may require CiscoWorks LMS to be run on separate servers in order to support a large number of devices or to meet certain performance criteria.

More than one copy of CiscoWorks LMS may be installed on secondary servers provided the customer has purchased and registered the 5,000 device restricted version of the CiscoWorks LMS software. When installed on secondary server, the cumulative total number of devices supported cannot exceed 5,000 per serial license key. Device support beyond 5,000 unique cumulative devices will require additional licenses and copies of CiscoWorks LMS to be purchased.

When more than one server is used to host CiscoWorks LMS, each server should have a copy of the original license key installed on it. Customers should not modify the license file.

Legal restriction concerning the distribution of the CiscoWorks LMS applications is described in the Supplemental License Agreement.

Additional Information for 10,000 Device Restricted Version for LMS 4.0

Users of CiscoWorks LMS 4.0 with 10,000 device restricted licensing often require CiscoWorks LMS to be run on separate servers in order to support a large number of devices or to meet certain performance criteria.

More than one copy of CiscoWorks LMS may be installed on a secondary servers provided the customer has purchased and registered the 10,000 device restricted version of the CiscoWorks LMS software. When installed on secondary server, the cumulative total number of devices supported cannot exceed 10,000 per serial license key. Device support beyond 10,000 unique cumulative devices will require additional licenses and copies of CiscoWorks LMS to be purchased.

When more than one server is used to host CiscoWorks LMS, each server should have a copy of the original license key installed on it. You should not modify the license file.

Legal restriction concerning the distribution of the CiscoWorks LMS applications is described in the Supplemental License Agreement.

Additional Information for High Availability (HA) and Geographic Redundancy (DR) Option

CiscoWorks LMS 4.0 supports the High Availability (HA) or Geographic Redundancy option, interchangeably referred to as Disaster Recovery (DR) option. Either of these options are supported as documented in the Installing and Getting Started With CiscoWorks LAN Management Solution 4.0 guide.

In a high availability or a geographic redundancy option, two servers are running in Active-Standby mode. The CiscoWorks LMS software and single license key are installed on both servers but active on only one of these servers at any given point in time. This software licensing provision allows the customer to purchase a single copy and license of LMS software and install it on both servers as needed to support this option.

Reproduction and Distribution

Customer may not reproduce nor distribute software.

DESCRIPTION OF OTHER RIGHTS AND LIMITATIONS

Please refer to the Cisco Systems, Inc. Software License Agreement.

xiiInstalling and Migrating to CiscoWorks LAN Management Solution 4.0

OL-20722-01

Notices

The following notices pertain to this software license.

OpenSSL/Open SSL ProjectThis product includes software developed by the OpenSSL Project for use in the OpenSSL Toolkit (http://www.openssl.org/).

This product includes cryptographic software written by Eric Young ([email protected]).

This product includes software written by Tim Hudson ([email protected]).

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 [email protected].

OpenSSL License:

Copyright © 1998-2007 The OpenSSL Project. All rights reserved.

Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met:

1. Redistributions of source code must retain the copyright notice, this list of conditions and the following disclaimer.

2. Redistributions in binary form must reproduce the above copyright notice, this list of conditions, and the following disclaimer in the documentation and/or other materials provided with the distribution.

3. All advertising materials mentioning features or use of this software must display the following acknowledgment: “This product includes software developed by the OpenSSL Project for use in the OpenSSL Toolkit (http://www.openssl.org/)”.

4. The names “OpenSSL Toolkit” and “OpenSSL Project” must not be used to endorse or promote products derived from this software without prior written permission. For written permission, please contact [email protected].

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:

xiiiInstalling and Migrating to CiscoWorks LAN Management Solution 4.0

OL-20722-01

http://www.openssl.org/


Notices

“This product includes software developed by the OpenSSL Project for use in the OpenSSL Toolkit (http://www.openssl.org/)”.

THIS SOFTWARE IS PROVIDED BY THE OpenSSL PROJECT “AS IS”' AND ANY EXPRESSED OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE OpenSSL PROJECT OR ITS CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.

This product includes cryptographic software written by Eric Young ([email protected]). This product includes software written by Tim Hudson ([email protected]).

Original SSLeay License:

Copyright © 1995-1998 Eric Young ([email protected]). All rights reserved.

This package is an SSL implementation written by Eric Young ([email protected]).

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 ([email protected]).

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 ([email protected])”.

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 ([email protected])”.

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

xivInstalling and Migrating to CiscoWorks LAN Management Solution 4.0

OL-20722-01


Notices

NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.

The license and distribution terms for any publicly available version or derivative of this code cannot be changed. i.e. this code cannot simply be copied and put under another distribution license [including the GNU Public License].

xvInstalling and Migrating to CiscoWorks LAN Management Solution 4.0

OL-20722-01

Notices

xviInstalling and Migrating to CiscoWorks LAN Management Solution 4.0

OL-20722-01

Preface

This guide helps you to install the CiscoWorks LAN Management Solution 4.0 software on both Windows and Solaris.

This guide also provides information on data migration from earlier versions of LMS to LMS 4.0. In addition, the guide provides troubleshooting suggestions that may be useful while you work on LMS.

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

AudienceThis guide is for anyone who installs, upgrades, configures, verifies, and uses LMS software. Network administrators or operators should have the following skills:

• Basic Windows or Solaris system administrator skills.

• Basic network management skills.

xviiInstalling and Migrating to CiscoWorks LAN Management Solution 4.0

OL-20722-01

PrefaceDocument Conventions

Document ConventionsTable 1 describes the conventions followed in this guide.

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.

Table 1 Conventions Used

Item Convention

Commands and keywords boldface font

Variables for which you supply values italic font

Displayed session and system information screen font

Information you enter boldface screen font

Variables you enter italic screen font

Menu items and button names boldface font

Selecting a menu item in paragraphs Option > Network Preferences

Selecting a menu item in tables Option > Network Preferences

xviiiInstalling and Migrating to CiscoWorks LAN Management Solution 4.0

OL-20722-01

PrefaceProduct Documentation

Product Documentation

Note We sometimes update the printed and electronic documentation after original publication. Therefore, you should also review the documentation on Cisco.com for the latest updates.

Table 2 describes the product documentation that is available.

Table 2 Product Documentation

Document Title Available Formats

Installing and Migrating to CiscoWorks LAN Management Solution 4.0 (this document)

• On Cisco.com at http://www.cisco.com/en/US/docs/net_mgmt/ciscoworks_lan_management_solution/4.0/install/guide/install.html

• PDF version part of CiscoWorks LMS 4.0 Product DVD.

Context-sensitive online help Select an option from the navigation tree, then click Help.

Getting Started with CiscoWorks LAN Management Solution 4.0

• On Cisco.com at http://www.cisco.com/en/US/docs/net_mgmt/ciscoworks_lan_management_solution/4.0/user/guide/getting_started/gsug.html


Configuration Management with CiscoWorks LAN Management Solution 4.0

• On Cisco.com at http://www.cisco.com/en/US/docs/net_mgmt/ciscoworks_lan_management_solution/4.0/user/guide/configuration_management/cmug.html


Monitoring and Troubleshooting with CiscoWorks LAN Management Solution 4.0

• On Cisco.com at http://www.cisco.com/en/US/docs/net_mgmt/ciscoworks_lan_management_solution/4.0/user/guide/monitoring_troubleshooting/mntug.html


Administration of CiscoWorks LAN Management Solution 4.0

• On Cisco.com at http://www.cisco.com/en/US/docs/net_mgmt/ciscoworks_lan_management_solution/4.0/user/guide/admin/admin.html


xixInstalling and Migrating to CiscoWorks LAN Management Solution 4.0

OL-20722-01

http://www.cisco.com/en/US/docs/net_mgmt/ciscoworks_lan_management_solution/4.0/install/guide/install.html

http://www.cisco.com/en/US/docs/net_mgmt/ciscoworks_lan_management_solution/4.0/user/guide/getting_started/gsug.html

http://www.cisco.com/en/US/docs/net_mgmt/ciscoworks_lan_management_solution/4.0/user/guide/configuration_management/cmug.html

http://www.cisco.com/en/US/docs/net_mgmt/ciscoworks_lan_management_solution/4.0/user/guide/monitoring_troubleshooting/mntug.html

http://www.cisco.com/en/US/docs/net_mgmt/ciscoworks_lan_management_solution/4.0/user/guide/admin/admin.html

PrefaceProduct Documentation

Technology Work Centers in CiscoWorks LAN Management Solution 4.0

• On Cisco.com at http://www.cisco.com/en/US/docs/net_mgmt/ciscoworks_lan_management_solution/4.0/user/guide/work_centers/wc.html


Reports Management with CiscoWorks LAN Management Solution 4.0

• On Cisco.com at http://www.cisco.com/en/US/docs/net_mgmt/ciscoworks_lan_management_solution/4.0/user/guide/Reports/rptmgt_ug.html


Inventory Management with CiscoWorks LAN Management Solution 4.0

• On Cisco.com at http://www.cisco.com/en/US/docs/net_mgmt/ciscoworks_lan_management_solution/4.0/user/guide/inventory_mgmt/inventory.html


Navigation Guide for CiscoWorks LAN Management Solution 4.0

• On Cisco.com at http://www.cisco.com/en/US/docs/net_mgmt/ciscoworks_lan_management_solution/4.0/navigation/guide/nav_guide.html


Open Database Schema Support in CiscoWorks LAN Management Solution 4.0

• On Cisco.com at http://www.cisco.com/en/US/docs/net_mgmt/ciscoworks_lan_management_solution/4.0/database_schema4.0/guide/dbviews.html


Release Notes for CiscoWorks LAN Management Solution 4.0

• On Cisco.com at http://www.cisco.com/en/US/docs/net_mgmt/ciscoworks_lan_management_solution/4.0/release/notes/lms40rel.html


Supported Devices Table for CiscoWorks LAN Management Solution 4.0

• On Cisco.com at http://www.cisco.com/en/US/docs/net_mgmt/ciscoworks_lan_management_solution/4.0/device_support/table/lms40sdt.html


Documentation Roadmap for CiscoWorks LAN Management Solution 4.0

• Printed document part of Software kit

Table 2 Product Documentation

Document Title Available Formats

xxInstalling and Migrating to CiscoWorks LAN Management Solution 4.0

OL-20722-01

http://www.cisco.com/en/US/docs/net_mgmt/ciscoworks_lan_management_solution/4.0/user/guide/work_centers/wc.html

http://www.cisco.com/en/US/docs/net_mgmt/ciscoworks_lan_management_solution/4.0/user/guide/Reports/rptmgt_ug.html

http://www.cisco.com/en/US/docs/net_mgmt/ciscoworks_lan_management_solution/4.0/user/guide/inventory_mgmt/inventory.html

http://www.cisco.com/en/US/docs/net_mgmt/ciscoworks_lan_management_solution/4.0/navigation/guide/nav_guide.html

http://www.cisco.com/en/US/docs/net_mgmt/ciscoworks_lan_management_solution/4.0/database_schema4.0/guide/dbviews.html

http://www.cisco.com/en/US/docs/net_mgmt/ciscoworks_lan_management_solution/4.0/release/notes/lms40rel.html

http://www.cisco.com/en/US/docs/net_mgmt/ciscoworks_lan_management_solution/4.0/device_support/table/lms40sdt.html

PrefaceObtaining Documentation, Obtaining Support, and Security Guidelines

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:

http://www.cisco.com/en/US/docs/general/whatsnew/whatsnew.html

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.

xxiInstalling and Migrating to CiscoWorks LAN Management Solution 4.0

OL-20722-01

http://www.cisco.com/en/US/docs/general/whatsnew/whatsnew.html

PrefaceObtaining Documentation, Obtaining Support, and Security Guidelines

xxiiInstalling and Migrating to CiscoWorks LAN Management Solution 4.0

OL-20722-01

Installing and MigrOL-20722-01

C H A P T E R 1
Overview of CiscoWorks LAN Management Solution 4.0
This chapter provides overview of LMS 4.0 and data migration from earlier versions of LMS to LMS 4.0

This chapter contains:

• Product Overview

• Install and Upgrade Behavior

• New Features in LMS 4.0

• Data Migration Overview

• Supported Network Management Systems

• Supported Devices

Product OverviewLMS 4.0 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, and Smart Install.

This document describes procedures for new and upgrade installation of LMS 4.0. 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.0, see Migrating Data to CiscoWorks LAN Management Solution 4.0.

1-1ating to CiscoWorks LAN Management Solution 4.0

Chapter 1 Overview of CiscoWorks LAN Management Solution 4.0Install and Upgrade Behavior

The licenses in LMS 4.0 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 BehaviorLMS 4.0 provides a single install experience to you.

For complete details on installation, see Performing Installation of CiscoWorks LAN Management Solution 4.0.

This section contains the following topics:

• Upgrade and Migration Overview

• Upgrading Master-Slave Server Setup

Upgrade and Migration OverviewUpgrading is overwriting the existing LMS version with the new LMS version. You have to freshly install LMS 4.0 and then perform remote data migration.

Remote upgrade refers to Installing LMS on a different machine and then restoring the data on that machine.

You can do a remote upgrade to LMS 4.0 from LMS 3.2, LMS 3.1, LMS 3.0, LMS 3.0 December 2007 Update, LMS 2.6 and LMS 2.6 Service Pack (SP) 1.

Note LMS 4.0 does not support direct inline upgrade from previous versions.

1-2Installing and Migrating to CiscoWorks LAN Management Solution 4.0

OL-20722-01


Upgrading Master-Slave Server SetupTable 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 taking backup from LMS 2.6/2.6 SP1/3.x and installed LMS 4.0, the DCR mode will be in Standalone

• After restoring the LMS 2.6/2.6 SP1/3.x backed up data in LMS 4.0, the DCR mode will be moved from Standalone to Master

• After restoring LMS 2.6/2.6 SP1/3.x standalone server backup data in LMS 4.0 Master, the DCR mode will be changed to Standalone

• After taking backup from LMS 2.6/2.6 SP1/3.x and Installed LMS 4.0, the DCR mode will be in Standalone

• After restoring the LMS 2.6/2.6 SP1/3.x backed up data in LMS 4.0, the DCR mode will be in Standalone

• You should change the mode to Slave

DCR Changes No Changes DCR devices will be deleted from Slave or pushed to Master based on your choice, and data will be synchronized from Master

Device Management/Allocation changes

After remote migration, the device management allocation policy will be set as it was before. For Example, if the allocation policy is set to On in LMS 2.6/2.6 SP1/3.x server, after remote migration to LMS 4.0 the same settings will be retained.

Device management allocation policy is set to Off, and all the devices will be moved to unmanaged state. This allows you to decide in managing devices in the Slave

Grouping Services Changes

User-defined groups in Slave will not be shared or synchronized with Master in LMS 4.0

• 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.

User-defined groups can be created in LMS 4.0 Slave as against previous releases. 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


OL-20722-01


Table 1-2 describes the recommended sequence to upgrade, and migrate your data from earlier versions of LMS to LMS 4.0.

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 3.2

Remote Upgrade 1. Back up the data in the old machine.

2. Install LMS 4.0 in the new machine.

3. Migrate your data to LMS 4.0 using the instructions explained in the section Migrating Data to CiscoWorks LAN Management Solution 4.0.

LMS 2.2, LMS 2.5, LMS 2.5.1

Remote Upgrade

Direct upgrade to LMS 4.0 is not supported. The suggested upgrade path is:

LMS 2.2 / LMS 2.5 / LMS 2.5.1 > LMS 2.6 > LMS 4.0

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 2.6


4. Migrate your data to LMS 4.0 using the instructions explained in the section Migrating Data to CiscoWorks LAN Management Solution 4.0


OL-20722-01

Chapter 1 Overview of CiscoWorks LAN Management Solution 4.0New Features in LMS 4.0

New Features in LMS 4.0This section explains the new features in LMS 4.0.

Click the help link for a detailed explanation of the new features.

This section contains the following:

• Getting Started Workflow

• Navigating Menus

• Work Centers

• Dashboards

• Search and Fault Bar

• Template Center

• CiscoWorks Local Role-based Access Control

• Unified Grouping Services

• Unified Device Manager

• EnergyWise

• Identity

• Auto Smartports

• Smart Install

• Fault Monitor

• Event Monitor

• Troubleshooting Workflow

• Report Center

• VRF-lite Support for Catalyst 3000 and Catalyst 4000 Devices

• Third-Party Software and Tool Changes

Note The supported screen resolution for LMS 4.0 is 1024x768 pixels. We recommend you not to use browser zoom in and zoom out features in LMS 4.0.


OL-20722-01


Getting Started WorkflowThe LMS Getting Started workflow assists you in performing the tasks required to get your LMS ready and to manage your Cisco networks.

When you login to LMS Server as a user with Super Admin and Network Administrator roles, the Getting Started page appears. When you login as a user with roles other than Super Admin and Network Administrator, the Default Dashboard appears.

The Introduction page lists the new features added in LMS 4.0. The steps for performing the following tasks are provided in the Getting Started workflow:

• Configure e-mail, cisco.com and proxy settings

• Update software and device packages

• Migrate data

• Configure RCP and SCP Credentials, security, backup and authentication settings

• Manage devices and credentials

• Manage user roles and users

• Access links to advanced functionalities and settings

You can perform these tasks step-by-step using the Getting Started workflow. You can also execute these tasks independently by selecting the task from the Getting Started assistant pane.

Navigating MenusThe LMS 4.0 menus are organized as follows:

Table 1-3 Menus in LMS 4.0

Menu Description

My Menu My Menu helps you to consolidate information specific to particular functions as dashboards. My Menu also enables you to group data from different functions into a single page. You can add, view and manage dashboards using the following options in My Menu:

• My Dashboards

• Public Dashboards

• Default Dashboards

Monitor You can use the Monitor menu for monitoring and troubleshooting your network in LMS. The menu also offers performance and fault management tasks, threshold settings and diagnostic tools.

Inventory You can use the Inventory menu for discovering network devices, managing device credentials, using Inventory tools, and managing inventory dashboards.

Configuration You can use the Configuration menu for deploying configurations on devices, updating software images, archiving and comparing device configurations, configuring VLANs, configuring technologies, converting standalone switches to a virtual switching system. Configuration menu also offers compliance tasks and you can generate configuration compliance reports.


OL-20722-01


Legacy: You can use the Legacy menu to perform LMS functions by using the legacy LMS 3.x navigation menus.

Work CentersLMS 4.0 provides complete lifecycle management of:

• Cisco solutions such as:

– Identity

– EnergyWise

• Network features such as:

– Auto Smartports

– Smart Install

Work Centers in LMS provides complete lifecycle management of Identity, EnergyWise, Auto Smartports, and Smart Install from Day 1 to Day N operations in a workflow-oriented approach. This includes readiness assessment, configuration, monitoring, and reporting capabilities.

DashboardsDashboards provide you with a quick snapshot of specific information on Fault, Configuration, Accounting, Performance, Security (FCAPS) functionality. The following functional dashboards are available in LMS:

• Monitoring Dashboard

• Identity Dashboard

• EnergyWise Dashboard

• Inventory Dashboard

• Configuration Dashboard

• Device Status Dashboard

• System Dashboard

Reports You can use the Reports menu to view and generate reports such as device reports, fault and event reports, audit reports, inventory reports, performance reports, cisco.com reports, and system reports.

Admin You can use the Admin menu for performing all the network and system admin-istration activities such as Device Credential Repository settings, collection settings, tools settings, purge settings, report settings, group management, server administration, software center.

Work Centers You can use the WorkCenter menu for configuring Cisco technologies such as Identity, EnergyWise, Smart Install, and Auto Smartports on devices using LMS.

Table 1-3 Menus in LMS 4.0

Menu Description


OL-20722-01


Search and Fault BarThis section explains:

• Search Bar

• Fault Bar

Search Bar

LMS comes with a new search bar that can be accessed from across all pages. Using the new improved search, you can perform keyword and object-based search on the following topics:

• Devices

• End Hosts

• Tasks

• Jobs

• Help

Fault Bar

LMS has a new fault bar that floats across all pages. Using the fault bar, you can view the real-time summary of Critical, Warning and Info faults.

Template CenterThe 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.

You can modify system-defined templates and save them as user-defined templates. You can also import templates from a client machine and these templates are stored as user-defined templates in LMS.

You can perform the following tasks:

• Deploying templates

• Managing templates

• Importing templates

• Assigning templates to users

CiscoWorks Local Role-based Access ControlFrom LMS 4.0, CiscoWorks Local Role-based Access Control is available for authorization. Your authorization is based on the privileges that have been assigned to you.

Using Local Role-based Access Control you can:

• Create user-defined roles

• Customize existing custom roles

• Import and export roles and users

• Assign one or more roles to LMS users

• Set a default role.


OL-20722-01


You can enable:

• Full authorization

• Task authorization

• Device group authorization

Unified Grouping ServicesLMS 4.0 combines the device grouping for Common Services, Inventory and Configuration Management, and Network Topology, Layer 2 Services and User Tracking with a consolidated attribute list. The Unified Grouping Services can support 600 groups.

The other grouping services that are available are:

• Fault Group

• IPSLA Collector Group

• Port and Module Group

Each of the above groups can support 200 groups.

Unified Device ManagerIn LMS 4.0, Unified Device Manager (UDM) provides centralized device management using a centralized policy configuration. UDM identifies managed devices after verifying the configured policy and the license count.

The different device states in LMS 4.0 are:

Managed State

Devices that match the license count and the configured policy will be in this state. These devices will appear in the appropriate system defined and user defined groups, if the data necessary to resolve group membership is available. You can initiate various tasks and jobs using devices in this state.

You can perform LMS functionalities like Inventory Collection, and Configuration Management only on managed devices. You can move managed devices to suspended or unmanaged state.

Suspended State

If you have some devices under maintenance, they cannot be managed during that period. You can select these devices from the managed device list and suspend them. After the maintenance period, you can move these devices back to the managed state.

Suspended devices do not appear in the managed device list device selector. Syslogs from these devices do not cause any automated actions to happen. However, syslogs from devices in this state are collected and reported, and all the history data will be maintained in the system.These devices will be considered for license count in LMS. Traps are not collected from these devices. Collection and other management activities will not happen. You can move suspended devices to unmanaged or managed state.


OL-20722-01


Unmanaged State

Devices which fail to match the configured policy and license count will be in this state. You can also select some devices from the managed list and make them unmanaged devices.

These devices will be available in UDM and DCR. The corresponding events will be sent to the management components like collectors which will remove the history information from their date base. You can move the unmanaged device to only the managed state.

Managed Devices Not Matching the Policy State

Managed devices that fail to match the current configured policy will be in this state. After a fresh installation, the number of Managed Devices not matching the Policy will be zero. Devices will move to this state only after you configure a device management policy, and if there are some managed devices that do not match the policy.

EnergyWiseCisco EnergyWise is a comprehensive program for power management in your network. Cisco EnergyWise enables companies to save costs by measuring, managing, and reducing the power consumption of network infrastructure, and of devices attached to the network.

EnergyWise in LMS provides a set of management functions to simplify and automate the energy management lifecycle of network infrastructure, and of devices attached to the network. EnergyWise reduces the time and effort required to transform business energy policy to real energy savings.

The EnergyWise dashboard organizes all the EnergyWise functions into a single portal for quick navigation and real-time energy updates.

Using EnergyWise in LMS you can:

• Assess the EnergyWise readiness of your network

• Discover and enable EnergyWise on devices

• Configure and implement energy management policies

• Monitor power consumption using EnergyWise dashboard

• Generate and view energy and cost savings graphs reports

• Generates syslogs and traps on energy violations

EnergyWise Reports quantify the energy used and saved by the network.

The types of EnergyWise reports are:

• EnergyWise Device Power Usage Quick Report

• EnergyWise Port Power Usage Report

• EnergyWise Power Usage Report

• EnergyWise Cost Saving Report

For more information on EnergyWise refer to Technology Work Centers in CiscoWorks LAN Management Solution 4.0.


OL-20722-01


IdentityCisco TrustSec Identity, earlier known as Cisco Identity-based Networking Services (IBNS), a part of the Cisco Trust and Identity Management Solution, is the foundation for providing access control to corporate networks. The Cisco TrustSec Identity solution is a set of Cisco IOS Software services designed to enable secure user and host access to enterprise networks powered by Cisco Catalyst switches and Wireless LANs (WLANs).

Using Identity in LMS you can:

• Assess the Identity readiness of your network

• Discover and enable Identity on devices

• Enable phased deployment of Cisco Identity-based Networking Services (IBNS) using various security modes with minimal impact to your network

• Strengthen the security of your network

• Provide differentiated services to your end users

• Assign resources dynamically to the correct VLAN

• Automate security policy enforcement

• Monitor authentication and authorization trends through charts and graphs

• Generate energy and cost savings graphs reports

• Quickly isolate and troubleshoot Identity related issues through the Identity dashboard

Identity reports display information on the various users of the LMS network.

The types of Identity Reports are:

• Authenticated Users Report

• Authentication Failure Report

• Authorization Failure Report

• User Specific Report

• Authorized User Reports

For more information on Identity refer to Technology Work Centers in CiscoWorks LAN Management Solution 4.0.

Auto SmartportsAuto Smartports macros dynamically configure ports based on the device type detected on the port. When the switch detects a new device on a port it applies the appropriate Auto Smartports macro to the port.

For example, when you connect a Cisco IP phone to a port, Auto Smartports automatically applies the IP phone macro to the port. The IP phone macro ensures quality of service (QoS), security features, and a dedicated voice VLAN to ensure proper handling of delay-sensitive voice traffic.

Auto Smartports uses event triggers to map devices to macros. The most common event triggers are based on Cisco Discovery Protocol (CDP) messages received from connected devices. The detection of a device invokes a CDP event trigger: Cisco IP phone, Cisco wireless access point, Cisco switch, or Cisco router. Other event triggers use MAC authentication bypass (MAB) and 802.1x authentication messages.


OL-20722-01


The Auto Smartports macros embedded in the switch software are groups of CLI commands. For example, the CISCO_PHONE event detected on a port triggers the switch to apply the commands in the CISCO_PHONE_AUTO_SMARTPORT macro.

Using Auto Smartports in LMS you can:

• Assess the readiness of your network for Auto Smartports

• Discover Auto Smartports capable devices, and enable Auto Smartports on them

• Dynamically configure Auto Smartports macros on ports, based on the device type detected on the port

• Dynamically enable quality of service (QoS), security features, and a dedicated VLAN using Auto Smartports macros

• Monitor Auto Smartports through the Auto Smartports report

For more information on Auto Smartports refer to Technology Work Centers in CiscoWorks LAN Management Solution 4.0.

Smart InstallSmart Install (SI) is a plug-and-play configuration and image management feature that provides zero-touch deployment for new switches.

You can configure SI on a switch which will then be the SI director. Customer can ship switches to a location, place them in the network, and power them on with no configuration or image required on the switches. The configuration will be performed by the SI director.

Using Smart Install in LMS you can:

• Assess the readiness of your network for Smart Install capable switches and directors

• Discover and enable Smart Install on Smart Install capable devices

• Manage configuration files and images of clients in the Smart Install director

• Configure DHCP settings for Smart Install

• Monitor Smart Install through the Smart Install report

For more information on Smart Install refer to Technology Work Centers in CiscoWorks LAN Management Solution 4.0.

Fault MonitorLMS Fault Monitor is a centralized browser where you can view the information on faults of devices in a single place.

Fault Monitor collects information on faults and events from all devices in real-time and displays the information for a selected group of devices. Fault Monitor allows you to own the faults or clear them. We can annotate faults or we can send notifications as well.


OL-20722-01


Event MonitorEvent Monitor is a centralized page where you can view the event details of all devices in the network. Event Monitor displays the fault history, syslog, and system events that were generated by the network in the:

• Last one hour

• Last two hours

• Last four hours

• Last eight hours

• Last one day

Troubleshooting WorkflowTroubleshooting workflow in LMS collects information across devices in the network and helps you to overcome network management challenges.

You can troubleshoot the following problems using this workflow:

• Network connectivity problems

• Device diagnostics

Report CenterReports Center provides a single launch point where all reports can be generated, and viewed from a common report management area.

Using Report Center in LMS you can:

• Generate reports which are grouped as:

– Device

– Inventory

– MAC Tracking

– Switch Port

– Technology

– Change Audit

– Fault and Event

– Performance

– Generic Online Diagnostics

– Embedded Event Manager

– cisco.com

– System

– Audit


OL-20722-01

Chapter 1 Overview of CiscoWorks LAN Management Solution 4.0Data Migration Overview

• View Report Archives

You can view the report output that is created from a scheduled report is stored in the reports archive. The archive displays the list for completed report jobs and you can view or delete them.

• Configure system preferences for managing reports.

VRF-lite Support for Catalyst 3000 and Catalyst 4000 DevicesLMS 4.0 supports VRF-lite technology in catalyst 3000 and catalyst 4000 devices.

Third-Party Software and Tool ChangesThe 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

• Firefox 3.6.x support on client systems

• Java Plug-in version 1.6.0_19 or later update versions only

• Apache upgrade to 2.2.10

• Java Runtime Environment (JRE) 1.6.0_19

Data Migration OverviewYou have to freshly install LMS 4.0 and then perform remote data migration. LMS 4.0 does not support direct upgrade from previous versions.

Data Migration to LMS 4.0 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 3.2

• 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 CiscoWorks LAN Management Solution 4.0 for more details on data migration.


OL-20722-01

Chapter 1 Overview of CiscoWorks LAN Management Solution 4.0Supported Network Management Systems

Supported Network Management SystemsTable 1-4 lists the Network Management Systems (NMS) supported by Integration Utility 1.10, which is part of LMS 4.0.

See User Guide for Integration Utility 1.7 on Cisco.com for instructions to use the Integration Utility.

Table 1-4 Supported Network Management Systems

Network Management System Supported Platforms

HP OpenView 9.0 • Solaris 10

• Windows Server 2003 x64 with Service Pack 2

• Windows Server 2003 x64 R2 with Service Pack 2

For information on integrating HP OpenView-CiscoWorks LMS, see NNMi Deployment Guide on www.hp.com.


• Windows Server 2003 x64 with Service Pack 2

• Windows Server 2003 x64 R2 with Service Pack 2

For information on integrating HP OpenView-CiscoWorks LMS, see NNMi Deployment Guide on www.hp.com.


• Solaris 10

• Windows 2003 Standard Edition with Service Pack 2

• Windows 2003 Enterprise Edition with Service Pack 2

• Windows 2003 R2 Standard Edition

• Windows 2003 R2 Enterprise Edition


• Solaris 10



• Windows 2003 R2 Standard Edition

• Windows 2003 R2 Enterprise Edition





OL-20722-01

www.hp.com

http://www.cisco.com/en/US/docs/net_mgmt/ciscoworks_common_services_software/3.1/user/nmim/guide/nmimug.html

www.hp.com

Chapter 1 Overview of CiscoWorks LAN Management Solution 4.0Supported Network Management Systems

Note HPOV or NetView adapters are not supported for the Fault Management functionality in LMS 4.0

See Importing From Remote NMS in the Inventory Management Online Help for information about importing devices from third party NMS.

Network Management Integration Data Bundle (NMIDB) 1.0.089 is shipped with LMS 4.0.

You can download the latest adapters for third-party network management applications and the Network Management Integration Data Bundle (NMIDB) from the following locations:

• Latest Adapters at:

http://www.cisco.com/kobayashi/sw-center/cw2000/cmc3rd.shtml

To access the above page, you must be a registered user of Cisco.com.

• NMIDB at:

http://download-sj.cisco.com/cisco/netmgmt/ciscoview/5.0/packages/nmidb.X.zip (On Internet Explorer and Firefox browsers)

Where X is the version of NMIDB.

Note Remote NMS support is available from 8.X. For lower versions only local integration is supported.

NetView 7.1.5 • Solaris 9

• Solaris 10

• Windows 2003 Standard Edition

• Windows 2003 Enterprise Edition

• Windows 2003 R2 Standard x64 Edition

• Windows 2003 R2 Enterprise x64 Edition

NetView 7.1.4 • Solaris 9

• Windows 2003 Standard Edition

• Windows 2003 Enterprise Edition

Table 1-4 Supported Network Management Systems (continued)

Network Management System Supported Platforms


OL-20722-01

http://www.cisco.com/kobayashi/sw-center/cw2000/cmc3rd.shtml

http://download-sj.cisco.com/cisco/netmgmt/ciscoview/5.0/packages/nmidb.X.zip

Chapter 1 Overview of CiscoWorks LAN Management Solution 4.0Supported Devices

Supported DevicesAs 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 Device Package Updates upto LMS 3.x, and download the latest device updates for CV, CM, DFM and RME (part of LMS 3.2) from the following location:

• For CiscoView at:

http://www.cisco.com/cgi-bin/Software/CiscoView/cvplanner.cgi

• For Campus at:

http://www.cisco.com/cgi-bin/tablebuild.pl/cw2000-campus

• For DFM at:

http://www.cisco.com/cgi-bin/tablebuild.pl/cw2000-dfm

• For RME at:

http://www.cisco.com/cgi-bin/tablebuild.pl/cw2000-rme

See the following documentation to know more information about supported devices:

• Supported Devices Tables of RME, CM, CV, and DFM (part of LMS 3.2)

This document is available on Cisco.com at the following URLs:

http://www.cisco.com/en/US/products/sw/cscowork/ps2425/prod_installation_guides_list.html

http://www.cisco.com/en/US/products/sw/cscowork/ps2425/products_device_support_tables_list.html

• User Guide for CiscoView 6.1.9

CiscoView manages and configures different types of Cisco devices. You can refer this document for information on supported devices. This document is available on Cisco.com at this URL:

http://www.cisco.com/en/US/products/sw/cscowork/ps4565/products_user_guide_list.html

To see the list of installed application’s device packages, select Admin > System > Software Center > Device Update from the LMS menu.

Registered Cisco.com users can access the Device Package Updates for LMS at the following location:

http://www.cisco.com/public/sw-center/index.shtml


OL-20722-01

http://www.cisco.com/cgi-bin/Software/CiscoView/cvplanner.cgi

http://www.cisco.com/cgi-bin/tablebuild.pl/cw2000-campus

http://www.cisco.com/cgi-bin/tablebuild.pl/cw2000-dfm

http://www.cisco.com/cgi-bin/tablebuild.pl/cw2000-rme


http://www.cisco.com/en/US/products/sw/cscowork/ps2425/prod_installation_guides_list.html

http://www.cisco.com/en/US/products/sw/cscowork/ps2425/products_device_support_tables_list.html


Chapter 1 Overview of CiscoWorks LAN Management Solution 4.0Supported Devices

To download Device Package Updates:

Step 1 Go to http://www.cisco.com/public/sw-center/index.shtml

You must be a registered Cisco.com user to access this Software Download site. The site prompts you to enter your Cisco.com username and password in the login screen, if you have not logged in already.

Step 2 Select the Software Product Category as Network Management.

Step 3 Select Routing and Switching Management > Ciscoworks LAN Management Solution Products > Ciscoworks LAN Management Solution

Step 4 Select CiscoWorks LAN Management Solution 4.0

Step 5 Select the required feature specific update from the product tree.

Step 6 Select the required device package updates from the product software type.

Step 7 Select a product release version from the Latest Release folder.

The device packages corresponding to the selected product version display at the right of the web page.

Step 8 Locate the device package update files which you want to download.

Step 9 Click the Download Now button to download and save the device package file to any local directory on CiscoWorks Server.

See the following documentation to know more information about supported devices:

• Supported Devices Tables for LMS 4.0

This document is available on Cisco.com at the following URL:



OL-20722-01





C H A P T E R 2
Prerequisites
This chapter describes the factors that you must consider before installing LMS 4.0 on both Windows and Solaris systems.

LMS 4.0 software can be installed independently and does not depend on the earlier versions of LMS for installation.

Before you install LMS 4.0, 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.0. 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.

Caution If you want to upgrade the operating system from Windows 2003 or Windows 2008 to Windows 2008 R2, you must first complete upgrading the operating system, and then install the LMS 4.0.x Windows 2008 R2 patch.

Note • You can install the LMS 4.0.x Windows 2008 R2 patch only on LMS 4.0.x and not on the lower version of LMS.

• You cannot install Integration Utility and HP Open View 7.x or 8.x on Windows 2008 or Windows 2008 R2 servers.


• System and Browser Requirements for Server and Client

• Terminal Server Support for Windows Server

• Solaris Patches

• LMS 4.0 Port Usage


Chapter 2 PrerequisitesSystem and Browser Requirements for Server and Client

• Required Device Credentials for LMS Functionalities

System and Browser Requirements for Server and ClientBefore you begin to install LMS software, you must check if your system meets the recommended prerequisites.

The recommended LMS 4.0 server and client requirements on both the 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 requirementsThe disk space required to install LMS 4.0 on both Solaris and Windows is:

• 60 GB free disk space for LMS 4.0 application and data, in the CiscoWorks installation directory—For LMS 50 (Windows only), LMS 100 (Windows only), LMS 300, LMS 750, LMS 1,500 and LMS 2,500 device license types

• 120 GB free disk space for LMS 4.0 application and data, in the CiscoWorks installation directory—For LMS 5,000 and LMS 10,000 device license types

The hardware requirements vary based on the type of device restricted license you use.

• Table 2-2 lists the server hardware requirements for installing the LMS 4,0 on Solaris systems.

• Table 2-3 lists the server hardware requirements for installing the LMS 4.0 on Windows systems.

• Table 2-4 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.

Note LMS 4.0 is not supported on Windows 2000, Solaris 8 and Solaris 9 servers.


OL-20722-01


Operating System RequirementsThe 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 Requirements


OL-20722-01


Solaris LMS 4.0 supports the following Solaris 10 releases:

• Solaris 10, 10/09 release






Solaris Zones (Supported from Solaris 10) is a virtualization technology from ORACLE (www.oracle.com). It allows you to create isolated and secure environments called zones for running applications.

LMS 4.0 is installed on global zone of Solaris 10 Operating System by default.

LMS 4.0 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.0 also supports Logical domains (LDoms) and ZFS file system.

See Solaris Patches for more information on Solaris patches to be installed on these Operating Systems.

Windows LMS 4.0 supports the following Windows systems:

• Windows 2003 Standard Edition (SP2)

• Windows 2003 Enterprise Edition (SP2)

• Windows 2003 Standard Edition R2 (SP2)

• Windows 2003 Enterprise Edition R2 (SP2)

• 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.

Note For installing LMS 4.0.x on Windows Server 2008 R2, you have to download and install the Windows 2008 R2 patch also. See Downloading and Installing CiscoWorks LMS 4.0.x Using Windows 2008 R2 Patch for more information.


OL-20722-01

http://www.oracle.com/index.html


LMS 4.0 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

Note VMWare and Hyper V virtualization systems are not supported for LMS 10000 Devices license.

Storage Area Network Support

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

Link Aggregation Support in Solaris 10

A link aggregation consists of several interfaces on a system that are configured together as a single, logical unit. Link aggregation is defined in the IEEE 802.3ad Link Aggregation Standard.

Link Aggregation Standard (IEEE 802.3ad) provides a method to combine the capacity of multiple full-duplex Ethernet links into a single logical link. This link aggregation group is then treated as a single link. The server requirements on a link aggregated environment remains the same as the server requirements on Solaris systems. See Server Requirements on Solaris Systems for the recommended server hardware requirements.


• Configuring Link Aggregation in a Solaris Environment

• Verifying the Link Aggregation

Configuring Link Aggregation in a Solaris Environment

This section explains how to configure link aggregation in a Solaris environment. The example in this procedure aggregates sample interfaces bge0 and bge1.

Step 1 Configure the links (in this example, bge0 and bge1) with two different IP addresses in the same network.

Step 2 Check if both the IP addresses are reachable and you are able to telnet to the IPs. Get one public IP address in the same subnet.

Step 3 Unplumb both the NICs using the command:

• Ifconfig bge0 unplumb

• Ifconfig bge1 unplumb


OL-20722-01


Step 4 Create the link aggregation group using the command:

• dladm create-aggr –d bge0 –d bge1 2 key

Key is the number that identifies the aggregation. The lowest key number is 1. Zeroes are not allowed as keys. The key can be of any value.

• ifconfig aggr2 plumb

• ifconfig aggr2 public IP address subnet mask up

For example, ifconfig aggr 2 10.77.210.210 255.255.255.192 up.

Step 5 Add the IP address (Public IP) and hostname in the /etc/host file.

Step 6 If you cannot ping the IP address, you can set aggregation LACP mode active to off.

dladm modify-aggr –t –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 CiscoWorks LMS in High Availability and Disaster Recovery Environment.


OL-20722-01


Server Requirements on Solaris SystemsTable 2-2 lists the server requirements for installing LMS 4.0 software on Solaris systems.

To manage LMS 10,000 devices in LMS 4.0, you must set up more than one servers.

Note LMS 50 and LMS 100 devices restricted license types are not supported on Solaris systems.

Table 2-2 Recommended Server Hardware Requirements on Solaris Systems

Component Recommended Server System Requirement

LMS 300 1 CPU with dual core or 2 CPUs with single core 4 GB RAM and 8 GB swap space, 32/64 dual stack OS

LMS 750 2 CPUs with dual core or 4 CPUs with single core 8 GB RAM and 16 GB swap space, 32/64 dual stack OS

LMS 1,500 2 CPUs with dual core or 4 CPUs with single core 8 GB RAM and 16 GB swap space, 32 / 64 dual stack OS

LMS 2,500 2 CPUs with quad core or 4 CPUs with dual core 16 GB RAM and 32 GB swap space, 32 / 64 dual stack OS

LMS 5,000

Note You can use one or more servers to manage upto 5000 devices.

2 CPUs with 8 core or 4 CPUs with quad core 16 GB RAM and 32 GB swap space, 32 / 64 dual stack OS

LMS 10,000

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

• 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.

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, 32 / 64 dual stack OS

For LMS Server managing the rest of Functionalities (Network Topology, Layer 2 Services and User Tracking, Fault Management, IPSLA Performance Management, and Device Performance management Functionalities) for upto 5,000 devices:

• 2 CPUs with 8 core or 4 CPUs with quad core 16 GB RAM and 32 GB swap space, 32 / 64 dual stack OS


OL-20722-01


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.

Server Requirements on Windows SystemsTable 2-3 lists the server requirements for installing LMS 4.0 software on Windows systems.

To manage LMS 10,000 devices in LMS 4.0, 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.0?

Table 2-3 Recommended Server Hardware Requirements on Windows Systems


LMS 50 1 CPU with dual core or 2 CPUs with single core 4 GB RAM and 8 GB swap space, 32 or 64 bit OS



LMS 750 2 CPUs with dual core or 4 CPUs with single core, 8 GB RAM and 16 GB swap space, 32 or 64 bit OS

LMS 1,500 2 CPUs with dual core or 4 CPUs with single core, 8 GB RAM and 16 GB swap space, 64 bit OS

LMS 2500 2 CPUs with quad core or 4 CPUs with dual core,16 GB RAM and 32 GB swap space, 64-bit OS

LMS 5,000

Note You can use one or more servers to manage upto 5000 devices.

2 CPUs with 8 core or 4 CPUs with quad core 16 GB RAM and 32 GB swap space, 64 bit OS


OL-20722-01


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:\

The following processors are supported on a Windows system:

Intel processors

• Intel Xeon processor

• Intel Core Duo processor T2600 - T2300

• Intel Itanium Processor (32 bit OS only, 1.7 Ghz or higher CPU)

• Intel-VT processors (VMware Optimized hardware)

• Intel Xeon processor 5400 series





LMS 10,000

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

• 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.

• 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

• For LMS Server managing the rest of Functionalities for upto 5,000 devices:

– 2 CPUs with 8 core or 4 CPUs with quad core 16 GB RAM and 32 GB swap space, 64 bit OS

Table 2-3 Recommended Server Hardware Requirements on Windows Systems



OL-20722-01


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

Unified Computing System (UCS) Support

LMS 4.0 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-M1or M2 and C250-M1 or M2). 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-3 for the recommended server hardware requirements on windows systems

The supported processor in UCS B-series blade servers is Intel Xeon 5500 or 5600 Series processors. For more information see http://www.cisco.com/en/US/prod/collateral/ps10265/ps10280/data_sheet_c78-524797_ps10279_Products_Data_Sheet.html

The supported processor in UCS C-series rack amount servers is Intel Xeon 5500 or 5600 Series processors with their choices mentioned explicitly. For more information see

http://www.cisco.com/en/US/products/ps10493/products_data_sheets_list.html

Server Requirements on Virtualization SystemsLMS 4.0 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


OL-20722-01

http://www.cisco.com/en/US/prod/collateral/ps10265/ps10280/data_sheet_c78-524797_ps10279_Products_Data_Sheet.html

http://www.cisco.com/en/US/products/ps10493/products_data_sheets_list.html

Chapter 2 PrerequisitesTerminal Server Support for Windows Server

System Requirements on Client SystemsThe following table lists the client system requirements for all platforms:

Terminal Server Support for Windows ServerYou can install LMS 4.0 software on a system with Terminal Services enabled in Remote Administration mode. However, you cannot install 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.

Table 2-5 summarizes the Terminal Services features in Windows Server.

Table 2-4 Recommended Client Hardware and Software Requirements

Component Recommended Client System Requirement

Disk space Windows: 4 GB virtual memory

Memory Requirements

2 GB RAM

Hardware and software

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 7 (32 and 64 bit)

Browser Requirements

• Internet Explorer 7.x (except on Windows 7)

• Internet Explorer 8.x

Note LMS 4.0 supports only the IE 8.x Quirks mode and not the IE8 Standards mode.

• Firefox 3.6.x for Windows

Note Only 32-bit IE and FF browsers are supported

Java Virtual Machine (JVM) Requirements

Java Plug-in version 1.6.0_19 or later update versions only


OL-20722-01

Chapter 2 PrerequisitesTerminal Server Support for Windows Server

.

Enabling and Disabling Terminal Services on Windows 2003 Server

To enable/ disable Terminal Server, go to Manage Your Server > Add or Remove a Role > Terminal Server.

To enable/ disable Remote Desktop, go to Control Panel > System > Remote.

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 Go to Control Panel > System.

Step 2 Click Remote Settings under Tasks > Remote

Step 3 Select the Allow connections from computer running any version if Remote Desktop option.

Enabling and Disabling FIPS on Windows 2003 and 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 CiscoWorks Server. You should disable the FIPS compliance for the CiscoWorks to work properly.

To enable/disable FIPS on Windows 2003 and Windows 2008 servers:

Step 1 Go to Start > Settings > Control Panel > Administrative tools > Local Security Policy.

The Local Security Policy window appears.

Step 2 Click Local Polices > Security Options.

Step 3 Select System cryptography: Use FIPS compliant algorithms for encryption, hashing, and signing.

Step 4 Right-click the selected policy and click Properties.

Step 5 Select Enabled or Disabled to enable or disable FIPS compliant algorithms.

Step 6 Click Apply.

You must reboot the server for the changes to take effect.

Table 2-5 Terminal Services on Windows Server

Windows 2003 and 2008 Servers Features

Terminal Server Remote access and virtual system. Each client has its own virtual OS environment.

Remote Desktop Administration Remote access only. All clients use the same (and the only) OS.


OL-20722-01

Chapter 2 PrerequisitesSolaris Patches

Solaris PatchesLMS 4.0 is installed on global zone of Solaris 10 Operating System by default. Installation of LMS 4.0 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 PatchesTable 2-6 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.

For more information, see www.oracle.com.

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.

Table 2-6 Solaris Patches

Operating System Required and Recommended Solaris Patches

Solaris 10 • Required Server Patches are 122032-05 and 127127-11

• Minimum system level must be 11/06 release or higher.

To find out the current operating system level, enter the following command:

# more /etc/release

For example, the system displays the following information:

Solaris 10 11/06 s10s_u2wos_09a SPARC

Copyright 2006 Sun Microsystems, Inc. All Rights Reserved.

Use is subject to license terms.

Assembled 11 November 2006


OL-20722-01


Chapter 2 PrerequisitesSolaris Patches

The table below lists the messages that appear during installation if you do not have the recommended and required Solaris patches on the system.

We recommend you download and install the latest required and recommended patches from www.oracle.com before you run LMS 4.0.

Cluster PatchesYou should also install the cluster patches recommended by ORACLE on Solaris 10 servers.

You can download the cluster patches from www.oracle.com. See the same website for the installation instructions of Cluster patches.

The minimum recommended cluster patch levels on Solaris Systems are Solaris 10 — Cluster patches released on Apr/17/07 and Sep/16/09.

If you have not installed the cluster patches on Solaris 10 system, the following warning messages appear to ensure you install the Cluster Patches required for Solaris 10:

WARNING: Ensure that you have installed the recommended Solaris 10 cluster patches released on Apr/17/07, in this server.

WARNING: If these cluster patches are not installed, please download and install them from http://www.sun.com/.

WARNING: Otherwise, some features of the CiscoWorks applications will not function properly.Do you want to continue the installation ? (y/n) [y]:

If you do not have... Message

Required Server patches Error message appears with a prompt to continue or quit the installation.

This system does not have the following required Server patches

Installation can proceed without the required Server patches.However, you must install the required patches listed above before running CiscoWorks.

Do you want to continue the installation? (y/n) [y]:

Required Client patches Error message appears with a prompt to continue or quit the installation.

This system does not have the following required Client patches.

These patches are required if only this system is used as a CiscoWorks client.


OL-20722-01



Chapter 2 PrerequisitesLMS 4.0 Port Usage

LMS 4.0 Port UsageTable 2-7 lists the ports used by the various LMS components.

If you have enabled firewall in your CiscoWorks Server, you must open or free up the following ports:

• HTTP or HTTPS port

• All ports mentioned in Table 2-7 whose direction of establishment of connection is Client to Server.

Only then, the communication across servers or between the server and client can happen:

Table 2-7 LMS 4.0 Port Usage

Protocol

Port Num-ber Service Name Functionality

Direction (of Establishment) of Connection

TCP 49 TACACS+ and ACS • Common Services

• Configuration and Software Image Management



Server to ACS

TCP 25 Simple Mail Transfer Protocol (SMTP)

• Common Services (PSU)

• Inventory, Config and Image Management

Server to SMTP Server

TCP 22 Secure Shell (SSH) • Common Services,



Server to Device

TCP 23 Telnet • Common Services



Server to Device

UDP 69 Trivial File Transfer Protocol (TFTP)

• Common Services


Server to Device

Device to Server


OL-20722-01


UDP 161 Simple Network Management Protocol (SNMP)

• Common Services

• CiscoView






Server to Device

Device to Server

TCP 514 Remote Copy Protocol Common Services Server to Device

UDP 162 SNMP Traps (Standard Port)



Device to Server

UDP 514 Syslog • Common Services

• Inventory, Config & Image Management

Device to Server

UDP 1431 Trap Listener to MAC Notification Traps

Network Topology, Layer 2 Services and User Tracking

Device to Server

UDP 9000 Trap receiving (if port 162 is occupied)

Fault Management Device to Server

UDP 16236 UT Host acquisition Network Topology, Layer 2 Services and User Tracking

End host to Server

TCP 443 CiscoWorks HTTP server in SSL mode

Common Services Client to Server

Server Internal

TCP 1741 CiscoWorks HTTP Protocol

• Common Services

• CiscoView


• Inventory, Config & Image Management



Client to Server

TCP 42342 OSAGENT Common Services Client to Server

Table 2-7 LMS 4.0 Port Usage (continued)

Protocol




OL-20722-01


TCP 42352 ESS HTTP (Alternate port is 44352/tcp)

Common Services Client to Server

TCP 1099 ESS (used for Java Management Extensions)

Common Services Server Internal

TCP 8898 Log Server Fault Management Server Internal

TCP 9002 DynamID authentica-tion (DFM Broker)

Fault Management Server Internal

TCP 9007 Tomcat shutdown Common Services Server Internal

TCP 9009 Ajp13 connector used by Tomcat


UDP 9020 Trap Receiving Fault Management Server Internal

UDP 14004 Lock port for ANI Server singlet on check


Server Internal

TCP 15000 Log server Fault Management Server Internal

TCP 40050-40070

CSTM ports used by CS applications, such as Grouping Services, Device and Credential Repository (DCR)


TCP 40401 LicenseServer Common Services Server Internal

TCP 43242 ANIServer Network Topology, Layer 2 Services and User Tracking

Client to Server

TCP 42340 CiscoWorks Daemon Manager - Tool for Server Processes


TCP 42344 ANI HTTP Server Common Services Server Internal

UDP 42350 Event Services Software (ESS) (Alternate port is 44350/udp)


TCP 42351 Event Services Software (ESS) Listening (Alternate port is 44351/tcp)


TCP 42353 ESS Routing (Alternate port is 44352/tcp)



Protocol




OL-20722-01


TCP 43441 Common Services Database


TCP 43455 Inventory, Config and Image Management Database

Inventory, Config and Image Management

Server Internal

TCP 43443 ANIDbEngine Network Topology, Layer 2 Services and User Tracking

Server Internal

TCP 43445 Fault History Database Fault Management Server Internal

TCP 43446 Inventory Service Database


TCP 43800 Device Performance Management Database

Device Performance Manage-ment

Server Internal

TCP 43820 IPSLA Performance Management Database

IPSLA Performance Manage-ment

Server Internal

TCP 43447 Event Promulgation Module Database


TCP 44400- 44420

CSTM Ports • Fault Management


Server Internal

TCP 47010-47040

CSTM Port Inventory, Config and Image Management

Server Internal

TCP 49000-49040

CSTM Port Inventory, Config and Image Management

Server Internal

TCP 50001 SOAPMonitor Inventory, Config and Image Management

Server Internal

TCP 55000- 55020

CSTM Port Network Topology, Layer 2 Services and User Tracking

Server Internal

TCP 56000- 56040

CSTM Port VRF Lite Server Internal


Protocol




OL-20722-01

Chapter 2 PrerequisitesRequired Device Credentials for LMS Functionalities

Required Device Credentials for LMS FunctionalitiesYou 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-8 lists all the functionalities and the device credentials required.

.Table 2-8 LMS Functionalities and Device Credentials

FunctionalitiesTelnet/SSH Password Enable Password SNMP Read Only

SNMP Read / Write

Common Services Not required Not required Required Required


Not required Not required Required Required

CiscoView Not required Not required Required Required

Fault Management Not required Not required Required Not required

IPSLA Performance Management


Device Performance Management

Not required Not required Required Not required

Inventory Not required Not required Required Not required

Configuration Management (Telnet)

Required Required Required Not required

Configuration Management1 (TFTP) 2

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.


NetConfig Required Required Required Required

Config Editor Required Required Required Required

NetShow Required Required Required Not required

Software Management Required3

3. Required in the case of a few devices like PIX devices, Cisco 2950 series switches.

Required3 Required Required

Port and Module Configuration

Required Required Required Required

EnergyWise Required Required Required Required

Identity Services Required Required Required Required

Auto Smartports Required Required Required Required

Smart Install Required Required Required Required


OL-20722-01

Chapter 2 PrerequisitesRequired Device Credentials for LMS Functionalities


OL-20722-01


C H A P T E R 3
Preparing to Install CiscoWorks LAN Management Solution 4.0
This chapter lists the necessary information that prepares you to perform an installation of LMS 4.0 on both Windows and Solaris systems.


• 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 FrameworkThis section captures the terms and definitions that are used while installing LMS 4.0

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.0, 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.


Chapter 3 Preparing to Install CiscoWorks LAN Management Solution 4.0Terms and Definitions Used in LMS Installation Framework

While installing, you will come across these terms:

• CiscoWorks Admin Password

An administrative password used while logging into the CiscoWorks server as administrator. Use a minimum of five characters.

Ensure that you have noted down the password.

You are prompted to enter this password in both Typical and Custom modes of installation.

• System Identity Account Password

Password that is used in a multi-server environment.

Communication among multiple CiscoWorks Servers is enabled by a “trust” model addressed by certificates and shared secrets. System Identity setup helps you to create a “trust” user among servers that are part of a multi-server setup. This user enables communication among servers that are part of a domain.

You must configure all the CiscoWorks servers that are part of your multi-server setup with the same system identity account password.

While entering the System Identity Account Passwords, use a minimum of five characters.

You are prompted to enter this password in both Typical and Custom modes of installation.

• CiscoWorks Guest Password

This is used while logging into the CiscoWorks server as a guest user. Use a minimum of five characters.

You are prompted to enter this password in the Custom mode of installation. In the Typical mode, this password is randomly generated.

• Self Signed Certificate

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

Self Signed Certificates are valid for five years from the date of creation. When the certificate expires, the browser prompts you to install the certificate again from the server where you have installed CiscoWorks.

For more information on Self Signed Certificates, see User Inputs for Custom Installation.

In the Typical mode, this certificate is automatically generated.

For more information on passwords, see Password Rules for New Installation

• SMTP Server

System-wide name of the SMTP server used by LMS 4.0 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.0 menu.

• Cisco.com

Cisco.com user ID and password. This information is used while performing tasks such as downloading software images, downloading device packages, etc.

You are prompted to enter these credentials only while installing the CiscoWorks Integration Utility.

You can also change the System Identity Account password, Guest password, and Cisco.com credentials using the LMS 4.0 user interface (Admin > System > Cisco.com Settings).


OL-20722-01

Chapter 3 Preparing to Install CiscoWorks LAN Management Solution 4.0Before You Begin Installation

Before You Begin InstallationThis 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 NotesBefore 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 CiscoWorks Server.

• While launching CiscoWorks, network inconsistencies might cause installation errors if you are installing from a remote mount point.

• If your CiscoWorks Server is integrated with any Network Management System (NMS) in your network using the Integration Utility, you must perform the integration whenever you enable or disable SSL in the CiscoWorks Server. You must do this to update the application registration in the NMS.

For help with NMS integration, see the User Guide for CiscoWorks Integration Utility 1.7. You can find this document on Cisco.com, in both HTML and PDF form.


• Disable any popup blocker utility that is installed on your client system before launching CiscoWorks.

• LMS 4.0 is installed in the default directories:

– On Solaris: /opt/CSCOpx

– On Windows: SystemDrive:\Program Files\CSCOpx

Where, SystemDrive is the Windows operating system installed directory.

If you select another directory during installation, the application is installed in that directory.

The destination folder should not contain the following special characters:

– On Solaris:

! @ # $ % ^ & * ( ) + | } { " : [ ] ; ' ? < > , . ` = ~

– On Windows:

! @ # $ % ^ & * ( ) + | } { " [ ] ; ' / ? < > , . ` =


OL-20722-01



• If errors occur during installation, check the installation log file:

– On Solaris, check the installation log file /var/tmp/Ciscoworks_install_YYYYMMDD_hhmmss.log for LMS 4.0 installation

Where YYYYMMDD denotes the year, month and date of installation and hhmmss denotes the hours, minutes and seconds of installation.

For example:

/var/tmp/Ciscoworks_install_20100721_182205.log

– On Windows, check the installation log in the root directory on the drive where the operating system is installed. Each installation creates a new log file.

For example, for LMS 4.0, the installation log file is:

C:\Ciscoworks_install_YYYYMMDD_hhmmss.log, where YYYYMMDD denotes the year, month and date of installation and hhmmss denotes the hours, minutes and seconds of installation.

For example:

C:\Ciscoworks_install_20100721_182205.log

• You can press Ctrl-C (on Solaris) or click Cancel (on Windows) at any time to end the installation. However, any changes to your system will not be undone.

For example, if any new files were installed or if they were any changes to the system files, you need to manually clean up the installation directories.

Note We recommend that you do not terminate the installation while it is running.

• If HP OpenView is running on your system, installation will take more time. Disable HP OpenView to run a faster installation.

• To ensure that you have the latest device support and bug fixes for LMS you must install the latest Device Package updates.

For download locations, see Supported Devices.

Installation Notes (For Solaris Only)• On Solaris, if you select an installation directory other than the default, the /opt/CSCOpx directory

is created as a link to the directory you selected.

Warning If you remove this link after installation, the product will malfunction.

• We recommend that you run the installation from a local DVD or a local hard drive to avoid errors that may result from the network being slow or busy.

If you want to install from a local hard drive, you must copy the contents from the DVD to the local hard drive. Ensure that you copy the entire contents from the DVD to the hard drive.

You must preserve the timestamp when you copy the contents from the DVD to the hard drive.


OL-20722-01


To preserve all the attributes including timestamp:

a. Change the present working directory to the directory to which the DVD is mounted using the command:

cd /cdrom/cdrom0

where cdrom/cdrom0 is the directory to which the DVD is mounted.

b. Create a directory where you want to copy the contents of the disk by entering:

mkdir /opt/copydisk

Make sure that this directory has enough space to hold the entire contents of the disk.

c. Enter:

tar cpf - . | (cd /opt/copydisk && tar -xpf -)

This command preserves all attributes including the timestamp.

Installation Notes (For Windows Only)• You can install LMS 4.0 on a system with Terminal Services enabled in Remote Administration

mode. However, installation of LMS 4.0 on a system with Terminal Services enabled in Application mode is not supported.

If you have enabled Terminal Server in Application mode, disable the Terminal Server, reboot the system, and start the installation again. See Terminal Server Support for Windows Server.

• If Internet Information Services (IIS) is detected on your system and if you have continued the installation with IIS services, you cannot use the port number 443 for HTTPS. Instead, you must use the port numbers ranging from 1026 to 65535 for HTTPS to avoid this conflict.

• If you are running any virus scanner while installing LMS 4.0, 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.0. The installer will not copy the database to the appropriate location if you do not disable Windows Defender.

• Check the Primary and Active regional settings before installation. They have to be set either as US English or Japanese. Other options are not supported by LMS 4.0.

You can set the Active regional settings in Control Panel > Regional and Language Options > Regional Options.

• You must restart your system after you install LMS 4.0 to avoid any system instability on a Windows Operating System.


OL-20722-01

Chapter 3 Preparing to Install CiscoWorks LAN Management Solution 4.0Licensing Your Product

Licensing Your ProductThe LMS 4.0 product provides features such as software-based product registration and license key activation technologies. While you are installing LMS, the installer displays the Registration and Licensing input dialog box.


• Understanding Product Ordering Options and Product Authorization Key

• License Information

• License File

• Evaluation Mode

• NFR (Not For Resale) License

• Installing the Licensing 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 CiscoWorks LMS 4.0 software and Product Authorization Key (PAK):

• Ordering Physical CiscoWorks LMS 4.0 Product DVD with Printed PAK

• Downloading CiscoWorks LMS 4.0 Evaluation Software and Ordering Digital PAK

• Ordering Physical CiscoWorks LMS 4.0 Base Media Kit and Digital PAK

Ordering Physical CiscoWorks LMS 4.0 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 300, LMS 750, LMS 1,500, LMS 2500, LMS 5,000 and LMS 10,000 license types, contains a DVD for Windows Operating System, and another DVD for Solaris Operating Systems.


OL-20722-01


Downloading CiscoWorks LMS 4.0 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 CiscoWorks LMS 4.0 Evaluation software from http://www.cisco.com/go/nmsevals.

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: https://tools.cisco.com/RPF/register/register.do.

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 CiscoWorks LMS 4.0 Base Media Kit and Digital PAK

A physical CiscoWorks LMS base media kit without PAK ID is offered to you in this method of ordering.

You can opt to order the CiscoWorks 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: https://tools.cisco.com/RPF/register/register.do

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 InformationThe licenses in LMS 4.0 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.0.

Read the information in Understanding Product Ordering Options and Product Authorization Key to understand about the various product ordering options, before you know about the various licenses of LMS 4.0.


OL-20722-01

http://www.cisco.com/go/nmsevals

https://tools.cisco.com/RPF/register/register.do

https://tools.cisco.com/RPF/register/register.do



• Available Licenses for LMS 4.0

• Major Upgrade Kit Licenses for LMS 4.0

• Licenses for Device-Level Conversion in CiscoWorks LMS

• Licenses for Add-on Components to CiscoWorks LMS 4.0

See Application Scaling Numbers for further deployment related information.

Available Licenses for LMS 4.0


• Licensing SKUs for Traditional Ordering

• Licensing SKUs for Ordering Base Media Kit Without PAKs

• Licensing SKUs for Ordering Digital PAKs

Licensing SKUs for Traditional Ordering

The following are the available licenses (SKUs) for LMS 4.0 users, who have opted to order the physical Product DVD kit (Physical software and Software claim certificate paper with PAK):

Licensing SKUs for Ordering Base Media Kit Without PAKs

If you want to order for the LMS 4.0 base media kit without any PAK, you must use the following product number:

Available Licenses (SKU) in LMS 4.0 Permitted number of Devices in LMS 4.0

CWLMS-4.0-SBE-K9 (only for Windows) 50 devices

CWLMS-4.0-100-K9 (only for Windows) 100 devices

CWLMS-4.0-300-K9 300 devices

CWLMS-4.0-750-K9 750 devices

CWLMS-4.0-1.5K-K9 1,500 devices

CWLMS-4.0-2.5K-K9 2,500 devices

CWLMS-4.0-5K-K9 5,000 devices

CWLMS-4.0-10K-K9 10,000 devices

Base Media Kit Product Number Permitted number of Devices LMS 4.0

CWLMS-4.0-SW-K9 100 devices

Note This is the default number of devices allowed to manage in the evaluation version of the product.


OL-20722-01


Licensing SKUs for Ordering Digital PAKs

The following are the available licenses (SKUs) for LMS 4.0 users, who have opted to receive the Digital PAK through eDelivery:

Major Upgrade Kit Licenses for LMS 4.0

To upgrade from LMS 3.x, you can order LMS 4.0 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.0.

This section explains:

• Licenses SKUs For Traditional Ordering of LMS 4.0 Major Upgrade Kit

• Licenses SKUs For Ordering LMS 4.0 Major Upgrade Kit Digital PAK

Note If you are an existing LMS 2.x or LMS 3.x user and if you want to upgrade to LMS 4.0 750 or 2500 device licenses, we recommend you to:

1. Order the LMS 4.0 Major Upgrade kit for the existing LMS 2.x or LMS 3.x SKU that you are using, and upgrade to LMS 4.0

2. Order a LMS 4.0 750 or 2500 Device-Level Conversion License to convert from your existing device license to LMS 750 or 2500 SKU

Licenses SKUs For Traditional Ordering of LMS 4.0 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:

Available Licenses (SKU) in LMS 4.0 Permitted number of Devices in LMS 4.0

L-CWLMS-4.0-SBE (Only for Windows) 50 devices

L-CWLMS-4.0-100 (Only for Windows) 100 devices

L-CWLMS-4.0-300 300 devices

L-CWLMS-4.0-750 750 devices

L-CWLMS-4.0-1.5K 1,500 devices

L-CWLMS-4.0-2.5K 2,500 devices

L-CWLMS-4.0-5K 5,000 devices

L-CWLMS-4.0-10K 10,000 devices

Licenses (SKU) to upgrade from LMS 2.x, 3.x Permitted Number of Devices

CWLMS-4.0-100UPK9 LMS 4.0 100 Device Restricted Upgrade for LMS 2.x, 3.x users

CWLMS-4.0-300UPK9 LMS 4.0 300 Device Restricted Upgrade for LMS 2.x, 3.x users

CWLMS-4.0-1.5KUPK9 LMS 4.0 1,500 Device Restricted Upgrade for LMS 2.x, 3.x users

CWLMS-4.0-5KUPK9 LMS 4.0 5,000 Device Restricted Upgrade for LMS 2.x, 3.x users

CWLMS-4.0-10KUPK9 LMS 4.0 10,000 Device Restricted Upgrade for LMS 2.x, 3.x users


OL-20722-01


Licenses SKUs For Ordering LMS 4.0 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 for Device-Level Conversion in CiscoWorks LMS

You can convert a LMS 4.0 restricted device license type to the next level restricted device license type. You can order for LMS 4.0 device-level conversion licenses through eDelivery digital PAK ordering only.

Note You cannot order LMS 4.0 device-level conversion through Traditional Ordering method.

This section contains information about Digital PAK Ordering For Device-Level Conversion Licenses

Digital PAK Ordering For Device-Level Conversion Licenses

The SKUs that need to be used for ordering Digital PAKs for LMS 3.x device-level to next device-level Conversion are:

Licenses (SKU) to upgrade from LMS 2.x, 3.x Permitted number of Devices

L-CWLMS-4.0-100UP LMS 4.0 100 Device Restricted Upgrade for LMS 2.x, 3.x users

L-CWLMS-4.0-300UP LMS 4.0 300 Device Restricted Upgrade for LMS 2.x, 3.x users

L-CWLMS-4.0-1.5KUP LMS 4.0 1,500 Device Restricted Upgrade for LMS 2.x, 3.x users

L-CWLMS-4.0-5KUP LMS 4.0 5,000 Device Restricted Upgrade for LMS 2.x, 3.x users

L-CWLMS-4.0-10KUP LMS 4.0 10,000 Device Restricted Upgrade for LMS 2.x, 3.x users

Licenses for LMS 3.x Device-Level Conversions Description

L-CWLMSCONVSBE-100 (for Windows only)

Conversion from 50 devices restricted license to 100 devices restricted license

L-CWLMS4CON100-300 (for Windows only)

Conversion from 100 devices restricted license to 300 devices restricted license

L-CWLMSCONV300-750 Conversion from 300 devices restricted license to 750 devices restricted license

L-CWLMSCONV750-1.5k Conversion from 750 devices restricted license to 1,500 devices restricted license

L-CWLMS4CON1.5-2.5 Conversion from 1,500 devices restricted license to 2,500 devices restricted license

L-CWLMSCONV2.5K-5K Conversion from 2,500 devices restricted license to 5,000 devices restricted license

L-CWLMS4CON-5-10K Conversion from 5,000 devices restricted license to 10,000 devices restricted license


OL-20722-01


Licenses for Add-on Components to CiscoWorks LMS 4.0

LMS 4.0 provides add-on licenses to manage additional performance collectors.

The licences for add-on components for LMS 4.0 are:

License File When you register your LMS purchase on the product licensing area of Cisco.com, you will receive a license file.

If you are a registered user of Cisco.com, get your license file from: http://www.cisco.com/go/license.

If you are not a registered user of Cisco.com, get your Cisco.com user ID from: http://tools.cisco.com/RPF/register/register.do. Once you have obtained your Cisco.com user ID, log on to http://www.cisco.com/go/license to get your license file.

Logging in allows your Cisco user profile information to auto-populate many of the product registration fields. Login is case sensitive.

You must provide your PAK ID while you are registering the product. See Understanding Product Ordering Options and Product Authorization Key for information on PAK ID.

You must also enter the licensing SKU type according to the one you have purchased with the LMS 4.0 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.0.

You must store the license file that you have received, on your CiscoWorks server.

Licenses for Add-on Components to LMS 4.0 Description

L-CWLMS-4.0-COL-S Additional performance collectors and MIB objects support for LMS 750 devices

Maximum number of collectors that can be managed using this license is 1250.

The recommended number of MIB objects that can be polled using this license is 15,000

L-CWLMS-4.0-COL-M Additional performance collectors support for LMS 1500 devices


The recommended number of MIB objects that can be polled using this license is 30,000.

L-CWLMS-4.0-COL-L Additional performance collectors support for LMS 2500 devices


The recommended number of MIB objects that can be polled using this license is 50,000


OL-20722-01

http://www.cisco.com/go/license

http://tools.cisco.com/RPF/register/register.do



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.0 product.

Figure 3-1 displays the licensing screen for LMS 4.0 on Windows 2003 operating system.

Figure 3-1 Licensing Screen for LMS 4.0

The LMS installation program prompts you to enter 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.

Evaluation ModeIf the user installing LMS 4.0 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 Licensing File.

Note You can download the CiscoWorks LMS 4.0 Evaluation software from http://www.cisco.com/go/nmsevals. You must be a registered user of Cisco.com to download the software.


OL-20722-01

http://www.cisco.com/go/nmsevals


LMS 50 Devices Restricted LicenseIf 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 which are supposed to be in the managed state might be moved to suspended state. On the other hand, some devices that are not required to be managed might be in managed state.

Note Devices are moved to suspended state only if you manage more than 50 devices in the LMS Server. Otherwise there is no change in the device management.

Guidelines to Avoid Necessary Devices Being Moved to Suspended State

To avoid necessary devices being moved to suspended state, follow any one of the procedure mentioned below:

• Install the appropriate purchase license while installing the product.

Or

Before applying the 50 SKU license, you can select the particular set of 50 devices by configuring the Group Policy.

To configure the Group Policy, select Inventory > Device Administration > Device Allocation Policy > Manage By Groups from the LMS menu.

Using the group policy you can move the remaining unnecessary devices to unmanaged state.

Or

• Move the unnecessary devices from managed state to unmanaged state and move same number of necessary devices from suspended to managed state.

For details on managing device states, see Unified Device Manager.

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.

Add-on Licenses to Manage Additional Performance CollectorsThe following will be the Monitor server behavior in LMS 4.0:

• To monitor 100K objects in Performance management application, it is recommended to go for separate server with a LMS-Monitor license and the server should be in the slave mode.


OL-20722-01


• We can apply the M&T license on a standalone and later convert that to Slave. A nagging message will be shown to the user to convert the server to slave mode. It is strongly recommended to set DCR mode to slave and apply LMS-Monitor license.


OL-20722-01


• Various Performance variables polled (Auto monitoring pollers) are below:

– Link Ports_Interface Utilization

– Link Ports_Interface Errors

– Link Ports_Interface Availability

– All Devices_Device Availability

– All Devices_CPU Utilization

• In case of managing a subset of devices in M&T slave server and the remaining in Master for Monitoring functionality, we can set up the servers for additional polling functionality. Disabling auto monitoring feature, you can use device or port group available as part user defined Performance pollers.

Assume that there are two user defined groups Sj and Ind. You can select SJ grp and create a poller in master server and Ind device grp in slave server.

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 CiscoWorks LMS 4.0 NFR software from http://www.cisco.com/go/nmsnfr. You must be a registered user of Cisco.com to download the software.

To install a NFR copy of LMS 4.0, 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.0 during the installation. See Figure 3-1.

See Performing Installation of CiscoWorks LAN Management Solution 4.0 for detailed instructions on installing the product.

Step 2 Enter the LMS 4.0 NFR license file location, or click Browse to locate the NFR license file.

Step 3 Click Next.

Step 4 Click Next.

The System Requirements dialog box appears.

The installation program calculates the minimum disk space, RAM and Swap space required to install the product.

To install NFR license of the product, the required RAM space is 4GB and Swap space is 8 GB.


OL-20722-01

http://www.cisco.com/go/nmsnfr


You can also apply NFR license after the installation is completed.

To apply the NFR license after the installation is completed, you must select the Evaluation Only option in the Licensing Information page while the installation is progressing. See Figure 3-1 and Figure 3-2.

After the installation is completed, you should:

Step 1 Launch LMS 4.0

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 Licensing FileWe recommend that before installing the LMS 4.0 product, you register the product and receive a permanent license.

Figure 3-2 describes the steps that you must follow for licensing your product.

Figure 3-2 Steps to Follow For Licensing LMS

To license your product and install the license file, you must:

Step 1 Log onto Cisco.com to get your license file.

If you are a registered user of Cisco.com, get your license file from: http://www.cisco.com/go/license

If you are not a registered user of Cisco.com, get your Cisco.com user ID from:http://tools.cisco.com/RPF/register/register.do. Once you have obtained your Cisco.com user ID, log on to http://www.cisco.com/go/license to get your license file.

Logging in allows your Cisco user profile information to auto-populate many of the product registration fields. Login is case sensitive. After successful registration, you will receive your license file information through an e-mail.

2758

01

Product Authorization Key (PAK)(Printed on Software License Claim Certificate)

Example 1: 4XCD##V####

Provide theLicense file duringinstallation

Receive theLicense file

Register your PAKin Cisco.com

Login toCisco.com


OL-20722-01


http://tools.cisco.com/RPF/register/register.do



Step 2 Register the LMS product with Cisco.com using the PAK to get your license file.

See Understanding Product Ordering Options and Product Authorization Key for details.After you have registered your copy of LMS with Cisco.com, you will receive your license file.

Step 3 Install the license file.

If you have obtained the LMS license before installation:

a. Select the LMS application to install and when prompted:

– On Windows, select the first radio button (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.0, copy this new license file to the Common Services 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 both Windows as well as Solaris operating systems.


OL-20722-01

Chapter 3 Preparing to Install CiscoWorks LAN Management Solution 4.0Application Scaling Numbers

Application Scaling NumbersThis 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 Scalability Limit on LMS Server

Grouping Services For upto LMS 300 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 750 and LMS 1500 Device licenses, the following are the scaling limits:


• 100 IPSLA groups

• 50 Fault groups


For LMS 2500 Device licenses, the following are the scaling limits:



• 50 Fault groups


For LMS 5000 Device licenses, the following are the scaling limits:



• 50 Fault groups



In a LMS server, when only this functionality is managed, it supports the following:

• 10,000 devices

• 200 Port and Module Configuration (PMC) groups with 90% port groups and 10% module groups

• Maximum of 500,000 ports with an average of 50 ports per device

• Maximum of 100,000 ports in a port and Module Configuration group

• Maximum of 250,000 ports for each LMS job

In addition to the above, Syslog reports can contain upto 40,000 records


OL-20722-01



For upto LMS 300 Device licenses, the scaling limit is 20000 Endhosts/IP Phones

For LMS 750 and LMS 1500 Device licenses, the scaling limit is 75000 Endhosts/IP Phones

For LMS 2500 Device licenses, the scaling limit is 150000 Endhosts/IP Phones

For LMS 5000 Device licenses, the scaling limit is 250000 Endhosts/IP Phones

Network Topology, Layer 2 Services and User Tracking Data Collection discovers and tracks a maximum of 250,000 Switch Ports.

VRF-Lite, an add-on to Network Topology, Layer 2 Services and User Tracking supports 32 VRFs in all LMS device licenses

Fault Management The functionality supports upto 80,000 ports or interfaces (of which upto 15 percent can be in Managed state) to a maximum



OL-20722-01



• 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)

• 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 Add-on Licenses to Manage Additional Performance Collectors 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.

Add-on Licenses to Manage Additional Performance Collectors

You can apply the LMS add-on licenses to manage additional performance collectors in a LMS server. The scalability limits of add-on licenses are:

• For LMS 750 Monitoring server license the IPSLA collector limit is 1250





OL-20722-01


Concurrent Users SupportedLMS 4.0 can support 20 concurrent users.

Multiple number of simultaneous users can affect system performance.

20 concurrent users is the maximum recommended number. However, this depends on the size and configuration of the server.


The recommended MIB objects scaling numbers are as follows:

• For upto LMS 300 device licenses the MIB objects scaling limit is 6000

• For LMS 750 and LMS 1500 device licenses the MIB objects scaling limit is 30000

• For LMS 2500 device licenses the MIB objects scaling limit is 50000

• For LMS 5000 device license the MIB objects scaling limit is 100000

The recommended number of scaling numbers for MIB objects in LMS Monitoring slave server is as follows:

• L-CWLMS-4.0-COL-S (Small Edition Additional Performance Collectors license) - 15000 MIB objects

• L-CWLMS-4.0-COL-M (Medium Edition Additional Performance Collectors) - 30000 MIB objects

• L-CWLMS-4.0-COL-L (Large Edition Additional Performance Collectors) - 50000 MIB objects



OL-20722-01



OL-20722-01


C H A P T E R 4
Setting Up CiscoWorks LMS in High Availability and Disaster Recovery Environment
This chapter explains setting up CiscoWorks 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.


• 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 OverviewHigh 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.


Chapter 4 Setting Up CiscoWorks LMS in High Availability and Disaster Recovery EnvironmentHigh Availability and Disaster Recovery- An Overview

The implementation of Symantec Veritas High Availability solution in CiscoWorks 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 CiscoWorks 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

Switch/RouterNetwork

PrimaryApplication

Server

RedundantServer

DNS

VCS Heartbeat

Replication Link

Network Devices

2757

87


OL-20722-01

Chapter 4 Setting Up CiscoWorks LMS in High Availability and Disaster Recovery EnvironmentHigh Availability and Disaster Recovery- An Overview

Figure 4-2 displays geographic redundancy configuration.

Figure 4-2 Geographic Redundancy Configuration

ReplicationLink

Application Clients

Switch/RouterNetwork

PrimaryApplication

Server

RedundantServer

DNS

VCS Heartbeat

Network Devices

2757

88

Primary Site(single-node)

Secondary Site(single-node)


OL-20722-01

Chapter 4 Setting Up CiscoWorks LMS in High Availability and Disaster Recovery EnvironmentVeritas Components for Setting Up High Availability

Veritas Components for Setting Up High AvailabilityThe 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 InformationIn a high availability or a geographic redundancy option, the CiscoWorks 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


OL-20722-01

Chapter 4 Setting Up CiscoWorks LMS in High Availability and Disaster Recovery EnvironmentSystem Requirements for High Availability Implementation

System Requirements for High Availability ImplementationThis section explains the Operating system and hardware requirements for Veritas implementation:

Operating Systems

• Solaris 10 systems

• Windows 2008 64 bit Enterprise Edition

Hardware Requirements

• Each server should have at least two hard disks for Windows implementation and three hard disks for Solaris implementation. The additional hard disk should be chosen for disk group and volume creation.

• Each server should have two Network Interface Cards (NICs) assigned to it. One of the IP Addresses can be assigned with a private IP address on both Primary and Secondary servers and they should be connected as a direct link.

This requirement is not mandatory for a geographic redundancy configuration.

• You should install Storage Foundation on servers under the Domain Controller.

• You should configure name resolution for all the nodes.

General Requirements

• Veritas Volume Replicator requires a static IP for replication. Make sure the system has atleast one IP address configured which is resolved by DNS.

• 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 WindowsThis 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


OL-20722-01

Chapter 4 Setting Up CiscoWorks LMS in High Availability and Disaster Recovery EnvironmentSetting up LMS High Availability Environment on Windows

Installing Storage Foundation HA 5.1 on WindowsTo install the product:

Step 1 Start the Veritas Storage and High Availability Solutions setup.

Step 2 Click Storage Foundation HA 5.1 for Windows.

Step 3 Click Complete/Custom to begin the installation.

Step 4 Review the Welcome message and click Next.

Step 5 Accept the license agreement and click Next.

Step 6 Enter the product license key for Veritas Storage Foundation HA 5.1 for Windows and click Add.

Step 7 Click Next to select the product options.

a. Ensure that the following products are selected:

– Veritas Storage Foundation HA 5.1 for Windows (Server components)

– Veritas Storage Foundation HA 5.1 for Windows (Client components)

b. Ensure that the following product options are selected:

– Veritas Volume Replicator— Replicates data across multiple sites for disaster recovery.

– FlashSnap— Allows you to create and maintain persistent snapshot of volumes

– 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

Step 8 Select the domain and the computer for the installation, and click Next.

You can select the domain from the auto-populated list. Depending on domain and network size, speed, and activity, the domain and computer lists can take some time to populate.

You can choose the computer name from the list of servers.

When the domain controller and the computer that runs the installation program are on different subnets, the installer may not be able to locate the target computers.

You must manually enter the host names or the IP Addresses of the missing computer names.

Step 9 Review the installation settings information and click Next.

The Installation Status screen displays the status messages and the progress of the installation.

Step 10 Review the installation summary information and click Next after the installation has completed.

Step 11 Click Finish.

Step 12 Click Yes to reboot the local node.


OL-20722-01


Creating Disk Groups and Volumes A disk group is a collection of disks that is ported as a single unit. Veritas Storage Foundation uses disk groups to organize disks for management purposes.

Volumes are logical entities that comprises of portions of one or more physical disks and are accessed by a drive letter or mount point. Volumes can be configured for performance and high availability.


• Prerequisites for Configuring Disk Groups and Volumes

• Creating Disk Groups on Primary Server

• Creating Volumes on Primary Server

• Creating Disk Groups and Volumes on Secondary Server

Prerequisites for Configuring Disk Groups and Volumes

Complete the following tasks before you configure the disk groups and volumes:

• Determine the configuration of each volume and the total number of disks needed.

• Determine the initial size necessary for the volumes. You may increase the volume size at a later time but you cannot decrease the size.

• Verify that the disks you plan to include in the disk groups are available from all nodes.

• Verify that the drive letters that will be assigned to the volumes are available on all nodes so that the volumes can be accessed from any node.

Creating Disk Groups on Primary Server

You must create the disk group on the first node where the product instance is being installed. Repeat the procedure if you want to create additional disk groups.

To create a disk group:

Step 1 Click Start > All Programs > Symantec > Veritas Storage Foundation > Veritas Enterprise Administrator to launch the Veritas Enterprise Administrator (VEA) console.

Step 2 Select a profile if prompted. You can also select the default profile.

Step 3 Click Connect to a Host or Domain.

Step 4 Enter the host name of the server which you want to connect in the Host Name field or select a host name from the drop-down list box.

To connect to the local system, enter localhost.

Step 5 Click Connect.

You must provide the user name, password, and domain name if prompted.

You can see the host name of the server added on to the VEA console.

Step 6 Expand the tree view under the host node to configure a disk group under the StorageAgent tree node.

Step 7 Locate the StorageAgent tree node and right-click the Disk Groups icon under the StorageAgent tree node.


OL-20722-01


Step 8 Select New Dynamic Disk Group from the shortcut context menu.

The New Dynamic Disk Group wizard appears with the welcome page.

Step 9 Click Next to go to next page in the wizard.

Step 10 Provide the information about the disk group:

a. Enter a name for the disk group in the Group Name field.

You should enter datadg as group name.

b. Select the Create Cluster Group checkbox.

While creating datadg disk group, if the system bus error appears, you must run this command:

Vxclus UseSystemBus ON

c. Select the appropriate hard disks in the Available disks list, and use the Add button to move them to the Selected disks list.

You should not select the boot disks from the Available disks list.

d. Click Next.

Step 11 Click Next to accept the confirmation screen with the selected tasks.

Step 12 Click Finish to create the new disk group.

Creating Volumes on Primary Server

This section will guide you through the process of creating a volume on a cluster disk group. Repeat the procedure below if you want to create the following volumes on the first node of the cluster.

To create a volume:


Step 2 Select a profile if prompted.

You can also select the default profile.





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.


See Creating Disk Groups on Primary Server for details on how to create a disk group.

Step 7 Locate the StorageAgent tree node and right-click the Volumes icon under the StorageAgent tree node.

Step 8 Select New Volume from the shortcut context menu.

The New Volume wizard appears with a welcome message.

Step 9 Click Next to go to the next page in the wizard.


OL-20722-01


Step 10 Click Manually select disks and select the available disks (datadg) for the volume.

Ensure that the appropriate disk group name appears in the Group name drop-down list.

Step 11 Click Next.

Step 12 Specify the parameters of the volume:

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

You should enter cscopx as volume name.

b. Select the volume type as concatenated volume.

c. Provide a size for the volume.

For example, you can enter as 10 GB. Ensure that the disk has sufficient space before providing a size for the volume.

d. Click Next.

The Add Drive Letter and Path dialog box appears.

Step 13 Select Assign a Drive Letter, and choose a drive letter.

We recommend that you do not assign D: for this volume. This is because, the CD-ROM drive when installed on the system, may be allocated with D: by default.

Step 14 Click Next.

The Create File System dialog box appears.

Step 15 Select the Format this volume checkbox.

Step 16 Select the file system as NTFS.

Step 17 Click Next to review the settings summary.

Step 18 Click Finish to create the new volume.

Step 19 Repeat the above procedure to create a volume in the datadg disk group with the following characteristics:

• Volume Name: data_srl

• Volume Type: Concatenated Volume

• Volume Size: 30 GB

• Assigned Drive Letter: None

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.


OL-20722-01


Installing LMS on Primary and Secondary ServersTo 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.

Setting Up Veritas Volume ReplicationVeritas Volume Replicator is a fully integrated component of Veritas Volume Manager that replicates data to remote locations over any standard IP network to provide continuous data availability.


• Modes of Replication

• Setting Up RDS, RVG and RLINK

• Setting Casuser Permissions on cscopx Volume

Modes of Replication

The Veritas Volume Replicator replicates data in one of the following modes:

• Synchronous

Ensures that an update has been acknowledged by the Secondary host, before completing the update at the Primary. If there is a network failure, it ensures that the update fails at the Primary server.

• Asynchronous

The application updates are immediately reflected at the Primary server and sent to the Secondary server, later. The updates are stored on the Replicator Log until they are sent to the Secondary server.

• Synchronous Override

In this mode, the replication is synchronous, as long as the network is available. If the network is unavailable, the replication is continued in the asynchronous mode. The pending updates are sent to the Secondary server when the network becomes available.

This method is chosen by default for best support.


OL-20722-01


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 2 Click View > Connection > Replication Network.

Step 3 Click Action > Setup Replicated Data Set to launch the Setup Replicated Data Set wizard.

Step 4 Enter a name for Replicated Data Set name.

Step 5 Enter a name for Replicated Volume Group name.

Step 6 Select a Primary host from the drop-down list box.

Step 7 Click Next.

Step 8 Select cscopx as the volume to be replicated and click Next.

Step 9 Select data_srl as the volume to be used for replicator log and click Next.

Step 10 Review the information on the summary page and click Create Primary RVG to create the RVG.

A message appears.

Step 11 Click Yes to add the Secondary host to the Primary RDS.

The Specify Secondary host for replication page appears.

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

Step 13 Edit the replication settings as required:

• Verify the Primary side IP address or edit the IP Address if required.

• Verify the Secondary side IP address or edit the IP Address if required.

• Select the Replication Mode as Synchronous Override.

• Enter a Primary RLINK Name and a Secondary RLINK Name.

If you do not specify any name, Veritas Volume Replicator assigns a default name.

Step 14 Click Next to start Replication with the default settings.

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


OL-20722-01


Setting Casuser Permissions on cscopx Volume

To run the protected instance of LMS on Secondary servers, you must add the local casusers groups permissions to the cscopx volume.

Before you set the casusers permissions on cscopx volume:

Step 1 Stop the Replication Network by right-clicking on the Primary server, in the Replication Network view.

Step 2 Mount the cscopx volume with the drive letter as same as in the Primary server.

To add the local casusers group permissions for a Secondary server:

Step 1 Right-click Selected Drive Letter:\Program Files\CSCOpx from the Windows Explorer.

Step 2 Select the Sharing and Storage menu item.

The folder properties dialog box appears.

Step 3 Select the Security tab and click Add.

Step 4 Click the Location button in the Select Users or Groups dialog box, and select the local server from the selection tree.

Step 5 Enter casusers in the enter object names text box and click Check Names.

The text box displays Server Name\casusers.

Step 6 Click OK.

Step 7 Click the Full Control checkbox under Allow to grant the casusers group full control.

Step 8 Click the Advanced button.

Step 9 Select Replace permission entries on all child objects shown here that apply to child objects.

Step 10 Click Apply and wait for the permissions to propagate to all child objects under the CSCOpx directory.

Step 11 Click OK after the propagation is complete.

Note After the casusers group permissions have been set, unmount the volume and start the replication.


OL-20722-01


Setting Up Veritas Volume Replication Without ClusteringTo set up volume replication on the Primary server:

Step 1 Stop the Daemon Manager on the LMS server.

Step 2 Launch the VEA Console and select View Connection > Replication Network.

Step 3 Right-click on the blue arrow displayed for the volume group to be replicated. For example, LMS_RVG.

Step 4 Click Migrate.

Step 5 Verify the Secondary Server name to which data is to be replicated.

Step 6 Click OK.

Do the following tasks on the Secondary Server:

Step 1 Mount the cscopx volume with the drive letter as the same as mount drive that is mentioned for cscopx volume on Primary server drive.

Step 2 Run the following perl script from the directory:

NMSRoot\bin\perl NMSRoot\bin\hostnamechange.pl –ohost oldhostname -nhost newhostname -domain DomainName

Here,

oldhostname—Hostname of the Primary server.

newhostname—Hostname of the Secondary server

Domain—Domain name of the CiscoWorks Server. Entering domain name is optional.

Step 3 Remove the following files after running the hostnamechange.pl script:

• NMSROOT\lib\csorb\NS_Ref

• NMSROOT\campus\www\classpath\NS_Ref

• NMSROOT\_nsdb_root

Step 4 Run the following command in the Secondary Server:

NMSROOT/lib/jre/bin/java -classpath NMSROOT/MDC/tomcat/webapps/cwhp/WEB-INF/classes com.cisco.nm.cmf.backup.util.BackupSchedule NMSROOT

You must run this command only if there are any backup jobs scheduled in the Primary Server.

Step 5 Restart the Daemon Manager.

Step 6 Launch the LMS Server by entering the following on the web browser:

http://Secondary_Server_IP_Address:1741


OL-20722-01


Veritas Cluster Server Setup TasksClustering is used while monitoring of resources or automatic failover of the resources is required.

This section covers the steps required to setup and configure the Veritas clusters. There are two specific scenarios described:

• Cluster Configuration for High Availability

• Cluster Configuration for Disaster Recovery

Cluster Configuration for High Availability

This section specifically covers the setup and configuration of the Veritas cluster for the local redundancy configuration.

Before you start configuring the clusters, ensure that:

• You create a cluster with both the Primary and Secondary servers.

• NICs on both the servers are assigned with IP Address.

• Virtual IP Address will be assigned to the cluster.

• You configure the cluster with the Notifier manager option for mail alerts.

• You create service groups to control and administer the cluster such as Cluster service groups, Replication service group, and Application service group.

This section covers the following procedures:

• Creating the Cluster

• Creating the Cluster Service Group

• Creating the datadg Service Group (For HA Setup)

• Creating the Replication Service Group

• Creating the Application Service Group

Creating the Cluster

To create the cluster:

Step 1 Click Start > All Programs > Symantec > Veritas Cluster Server > Configuration Wizards > Cluster Configuration Wizard.

Step 2 Select Cluster Operation and click Next.

The domain name is displayed.

By default, the list of systems and the list of users in the domain is enabled. You can edit, if required.

Step 3 Click Next.

Step 4 Include the Primary and Secondary servers that should be part of the cluster.

Step 5 Select Create New Cluster Option and click Next.


OL-20722-01


Step 6 Create a new cluster using the VCS Configuration wizard, where:

• Cluster Name = LMS_HA_Cluster

• Cluster ID = 0

Part of the cluster definition in the wizard is to specify the NICs for the private network. VCS uses a private network for communications between cluster nodes for cluster maintenance.

You should set the Public NICs with Low Priority on both the servers.


Step 8 Select the existing user account and the password for VCS helper service.

The username and password are the credentials with domain name which are used to log into the server.

Step 9 Click Ok.


Step 11 Select the Use VCS User Privileges checkbox.

Step 12 Enter the VCS User privileges with user name and password.

This is used to log into the cluster.

Note 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.

Step 13 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 e-mail.

You can use the VCS Configuration wizard to configure these components.

To configure these components:

Step 1 Launch the VCS Configuration wizard.

Step 2 Click Next.

Step 3 Click Cluster Operations > Domain name.

Step 4 Select the server to configure the cluster groups.

Step 5 Select Edit existing cluster option and click Next.

Step 6 Select Configure Cluster Service options and configure the notifier and web console options for local redundancy configuration (HA Setup).

Step 7 Enter the virtual IP Address of the cluster.

You can assign a real IP Address which is not used in the network and is not assigned DHCP, as a virtual IP Address.


OL-20722-01


Step 8 Click OK.

Step 9 Start the Cluster Manager using Start > All Programs > Symantec > Veritas Cluster Manager - Java Console.

Step 10 Click File > New Cluster.

Step 11 Enter the virtual IP Address of the cluster that is configured, in the Hostname field.

Step 12 Click OK.

Creating the datadg Service Group (For HA Setup)

To create the datadg Service Group:

Step 1 Log in to the cluster using the credentials that you have configured in the VCS Configuration wizard.

Use the VCS Configuration wizard to see the Cluster Service group created.

Step 2 Go to Tools > Add/Modify Service Group in the console and do the following:

• Give the name of the service group as App_datadg.

• Select the Parallel option.

• Select the servers (Primary and Secondary servers) on which the service group can come online.

Step 3 Click OK.

Step 4 Add the VMDg resource with the following configuration:

• Resource Name = datadg

• Resource Type = VMDg

• DiskGroupName = datadg

You must select the Critical and Enabled checkboxes for this resource. You should add this resource only for local redundancy configuration.

Now the service group is online on both Primary and Secondary servers.

Creating the Replication Service Group

To create the Replication Service group, do the following on the Primary and Secondary clusters:


Step 2 Login to the cluster using the credentials that you have configured in the VCS Configuration wizard.



• Enter the name of the service group as App_Rep.

• Select the Failover Option.


• Enable the Auto Start option.


OL-20722-01


Step 4 Click OK.

Step 5 Add the Proxy resource with the following configuration:

• Resource Name =VVR_NIC_Proxy

• Resource Type = Proxy

• TargetResName = csg_nic

This name should be the same as the name of the resource of resource type NIC.

You must select the Critical and Enabled checkboxes for this resource.

Step 6 Add the IP resource with the following configuration:

• Resource Name = VVR_IP

• Resource Type = IP

• Address = Virtual IP address

• SubNetMask = subnet mask

• MACAddress = MAC Address of the corresponding NIC card


Step 7 Add the VvrRvg resource with the following configuration:

• Resource Name = APP_RVG

• Resource Type = VvrRvg

• RVG = Name of the Replicated Volume Group

For example, LMS_RVG.

• VMDg Resource Name = Name of the Resource Configured under the App_Rep Service group

For example, datadg.

• IPResName = VVR_IP


Step 8 Add the VMDg resource with the following configuration:


• Resource Type = VMDg



This is required only for geographic redundancy setup (DR setup).

Step 9 Right-click on the respective resources and do the following:

• Link VVR_IP as the parent of VVR_NIC_Proxy.

• Link APP_RVG as the parent of VVR_IP.

• Link APP_RVG as the parent of datadg.


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


OL-20722-01


Creating the Application Service Group

To create the Application Service Group:



Use the VCS Configuration wizard to see the Cluster Service group that is created.


• Enter the name of the service group as App_Service_GP.

• Select the Failover option.



Step 4 Click OK.

Step 5 Add the RVG Primary resource with the following configuration:

• Resource Name = App_RVGPrimary

• Resource Type = RVGPrimary

• RvgResourceName = Name of the Resource Configured under the App_Rep Service group

For example, App_Rvg.


Step 6 Add the MountV Resource with the following configuration:

• Resource Name = APP_MountV

• Resource Type = MountV

• Mount Path = Selected Drive Letter:\

• Volume Name = cscopx

• VMDg Resource Name = Name of the Resource Configured under the App_Rep Service group

For example, datadg.



• Resource Name =APP_NIC_Proxy


• TargetResName = NIC



OL-20722-01


Step 8 Add the IP resource with the following configuration.

• Resource Name = APP_IP


• Address = Virtual IP address allocated for this cluster and used by LMS application


• MACAddress = MAC Address of the corresponding NIC card.


Step 9 Import the Agent file from the location C:\Program Files\Veritas\cluster server\conf\config, into the cluster.

Step 10 Add the Agent resource with the following configuration.

• Resource Name = LMSAgent

• Resource Type = LMS


Step 11 Enter the pathname as NMSROOT.

Step 12 Enter the Virtual IP as EventIPAddress.

Step 13 Enter the Certificate Dir as NMSROOT/MDC/Apache/conf/ssl.

Step 14 Link APP_MountV as the parent of APP_RVGPrimary.

Step 15 Link APP_IP as the parent of APP_NIC_PROXY.

Step 16 Link Agent as the parent of APP_MountV.

Step 17 Link Agent as the parent of APP_IP.

Step 18 Right-click on the App_Service_Gp service group and select Online on Primary Server.

Cluster Configuration for Disaster Recovery

This section specifically covers the setup and configuration of the Veritas cluster for the case of two clusters geographically separated with a single node in each cluster. It contains:

• Creating the Primary and Secondary Clusters

• Creating the Cluster Service Group for Disaster Recovery Setup

• Disaster Recovery Setup Between Primary and Secondary Clusters


OL-20722-01


Creating the Primary and Secondary Clusters

For a Disaster Recovery Cluster setup, you should:

Step 1 Create a Primary cluster with the server in Site 1 and make all the service groups online.

See Cluster Configuration for High Availability for instructions to configure a cluster and various service groups.

Step 2 Create a Secondary cluster with the server in Site 2 and make all the service groups online except Application Service Group.


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 e-mail.

• Global Cluster Option—Allows you to manage multiple clusters.

To create a Cluster Service Group:

Step 1 Perform the steps explained in Creating the Cluster Service Group on both the Primary and Secondary clusters to create the Cluster Service Group.

Step 2 Add a wac resource with the following configuration to the Cluster Service Group:

• Resource Name = wac

• Resource Type = Process


Step 3 Link wac as the parent of VCS_IP.

Step 4 Link VCS_IP as the parent of NIC.

Step 5 Link the other resources as explained in Creating the Cluster Service Group.


You should not bring the resources to online in the Secondary cluster.


OL-20722-01


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 2 Click Edit > Add/Delete Remote Cluster.

A wizard appears.

Step 3 Click Next.

Step 4 Select the Add Cluster option and click Next.

Step 5 Enter the IP Address of the Secondary cluster.

Step 6 Enter the Username and password which is used to log into that cluster.

A confirmation message appears stating the cluster has been successfully added.

Step 7 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 The permissions has to be provided in both Primary and Secondary clusters.

Step 8 Right-click on App Service Group and select Configure as a Global Option.

The Global Cluster Details window appears.

Step 9 Select the cluster to be used in remote site from the Global Cluster details window and select the Cluster failover policy as Auto.

You can select the failover policy as Manual, if you want to bring the App_Service_Gp online in the remote cluster only after getting the approval from the Cluster Administrator.

Step 10 Enter the Cluster IP address, Username and password.

Step 11 Click Configure.

A summary page shows that global group has been configured successfully.

The Remote Cluster status of the App service group shows the status of the service group in both the clusters.


OL-20722-01

Chapter 4 Setting Up CiscoWorks LMS in High Availability and Disaster Recovery EnvironmentSetting 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 SolarisThis 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


OL-20722-01


Installing Storage Foundation HA 5.1 on SolarisTo install the product:

Step 1 Go to Veritas installer location.

For example, /Veritas/VSF_HA_5.1/installer.

Step 2 Run the installer file:

./installer

The Task menu appears.

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

The component list appears.

Step 4 Enter 5 to install all Veritas Storage Foundation components and press Enter.

Step 5 The installer prompts for a system name.

Step 6 Enter the system hostnames and press Enter.

Step 7 Enter the required Veritas Storage Foundation license that includes the following components:

• Veritas Storage Foundation High Availability

• Veritas Volume Replicator

• Veritas Cluster Server with the Global Cluster Option support

Step 8 Enter 2 to install Veritas Storage Foundation and press Enter.

Step 9 Enter Y to configure Storage Foundation.

Step 10 Enter N to configure VCS.

Step 11 Enter N to configure Enclosure based naming schemes.

Step 12 Enter Y to set up the default disk group.

Step 13 Enter the disk group name as datadg.

Step 14 Enter N for all VVR questions.

Step 15 Enter Y for Fully qualified host name confirmation.

Step 16 Enter N to enable the Storage Foundation Management server.

Step 17 Enter Y to start the Veritas Storage Foundation Process.

Step 18 Enter shutdown –y –i6 –g0 to reboot the Solaris server

Step 19 Enter ps –ef | grep vx on the command prompt after reboot to verify whether all Veritas processes are brought up successfully.


OL-20722-01


Creating Disk Groups and Volumes on Solaris ServersA disk group is a collection of disks that is ported as a single unit. Veritas Storage Foundation uses disk groups to organize disks for management purposes.

Volumes are logical entities that are comprised of portions of one or more physical disks and are accessed by a drive letter or mount point. Volumes can be configured for performance and high availability.


• Prerequisites for Configuring Disk Groups and Volumes on Solaris

• Creating Disk Groups on Primary Solaris Server

• Creating Volumes on Primary Solaris Server

• Creating Disk Groups and Volumes on Secondary Solaris Server

Prerequisites for Configuring Disk Groups and Volumes on Solaris

See Prerequisites for Configuring Disk Groups and Volumes for details.

Creating Disk Groups on Primary Solaris Server

You must create the disk group on the first node where the product instance is being installed. Repeat the procedure if you want to create additional disk groups.

To create a disk group:

Step 1 Enter /opt/VRTS/bin/vea on the Solaris system command prompt to launch the Veritas Enterprise Administrator (VEA) console.







You must enter the user name, password, and domain name if prompted. You can see the host name of the server added on to the VEA console.


Step 7 Locate the StorageAgent tree node and right-click the Disk Groups icon under the StorageAgent tree node.

Step 8 Select New Dynamic Disk Group from the shortcut context menu.

The New Dynamic Disk Group wizard appears with the welcome message.

Step 9 Click Next to go to next page in the wizard.


OL-20722-01


Step 10 Enter the information about the disk group:

a. Enter a name for the disk group in the Group Name field.

You should enter datadg as group name.

b. Select the appropriate hard disks in the Available disks list, and use the Add button to move them to the Selected disks list.

You should select two hard disks that are not the boot disks, from the Available disks list.

c. Click Next.

Step 11 Click Next to accept the confirmation screen with the selected tasks.

Step 12 Click Finish to create the new disk group.

Creating Volumes on Primary Solaris Server

This section explains how to create a volume on a cluster disk group. Repeat the procedure below if you want to create the volumes on the first node of the cluster.

To create a volume:

Step 1 Enter /opt/VRTS/bin/vea on the Solaris system command prompt to launch the Veritas Enterprise Administrator (VEA) console.




Step 4 Enter the host name of the server that you want to connect in the Host Name field

or

Select a host name from the drop-down list box.



You must enter the user name, password, and domain name if prompted. You can see the host name of the server added on to the VEA console.


Step 7 Locate the StorageAgent tree node and right-click the Volumes icon under the StorageAgent tree node.

Step 8 Select New Volume from the shortcut context menu.

The New Volume wizard appears with the welcome message.


Step 10 Click Let volume manager decide what disks to use for this volume.

Step 11 Click Next.

Step 12 Specify the parameters of the volume:

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

You should enter cscopx as volume name.

b. Select the volume type as concatenated volume.


OL-20722-01


c. Enter a size for the volume.

For example, you can enter as 10 GB.

d. Click Next.

The Create File System dialog box appears.

Step 13 Select the file system as vxfs.

Step 14 Mount the cscopx volume using the mount point as /opt/CSCOpx

Step 15 Click Next to review the settings summary.

Step 16 Click Finish to create the new volume.


• Volume Name: varcscopx



• File System: vxfs

This volume will be mounted using the mount point /var/adm/CSCOpx and is used only by LMS application.


• Volume Name: data_srl



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.


OL-20722-01


Installing LMS on Primary and Secondary ServersTo 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 ServerVeritas 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.


• 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 Stop the Replication Network by right-clicking on the Primary server, in the Replication Network view.

Step 2 Mount the cscopx and varcscopx volumes with the mount point as the same as in the Primary server.


OL-20722-01


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 SolarisTo set up volume replication on the Primary server:

Step 1 Stop the Daemon Manager on LMS server.

Step 2 Launch the VEA Console and select View Connection > Replication Network.

Step 3 Right-click on the blue arrow displayed for the volume group to be replicated. For example, LMS_RVG.

Step 4 Click Migrate.

Step 5 Verify the Secondary Server name to data is to be replicated.

Step 6 Click OK.

Do the following tasks on the Secondary Server:

Step 1 Mount the cscopx volume with the /opt/CSCOpx directory.

Step 2 Mount the varcscopx volume with the /var/adm/CSCOpx directory.

Step 3 Run the following perl script from the directory.

NMSRoot/bin/perl NMSRoot/bin/hostnamechange.pl –ohost oldhostname -nhost newhostname -domain DomainName

Here,

oldhostname—Hostname of the Primary server.

newhostname—Hostname of the Secondary server

Domain —Domain name of the CiscoWorks Server. Entering domain name is optional.

Step 4 Remove the following files after running the hostnamechange.pl script:

• NMSROOT/lib/csorb/NS_Ref

• NMSROOT/campus/www/classpath/NS_Ref

• NMSROOT/_nsdb_root

Step 5 Run the following command in the Secondary Server:

NMSROOT/lib/jre/bin/java -classpath NMSROOT/MDC/tomcat/webapps/cwhp/WEB-INF/classes com.cisco.nm.cmf.backup.util.BackupSchedule NMSROOT

You must run this command only if there are any backup jobs scheduled in the Primary Server.

Step 6 Restart the Daemon Manager.

Step 7 Launch the LMS Server by entering the following on the web browser:

http://Secondary_Server_IP_Address:1741


OL-20722-01


Veritas Cluster Server Setup Tasks on SolarisClustering is used while monitoring of resources or automatic failover of the resources is required.

This section covers the steps required to setup and configure the Veritas clusters. There are two specific scenarios described:

• Cluster Configuration for High Availability on Solaris

• Cluster Configuration for Disaster Recovery on Solaris

Cluster Configuration for High Availability on Solaris

This section specifically covers the setup and configuration of the Veritas cluster for the case of a single, local cluster with two nodes in the cluster (Primary and Secondary).

You must do the following tasks before you start configuring the clusters:

• Create a cluster with both the Primary and Secondary servers.

• NICs on both the servers are assigned with IP Address.

• Virtual IP Address will be assigned to the cluster.

• Configure the cluster with Notifier manager option for mail alerts.

• Create service groups to control and administer the cluster such as Cluster service groups, Replication service group, and Application service group.

This section covers the following procedures:

• Creating the Cluster on Solaris

• Creating the datadg Service Group on Solaris (For HA Setup)

• Creating the Replication Service Group on Solaris

• Creating the Application Service Group on Solaris

Creating the Cluster on Solaris

To create the cluster on Solaris:

Step 1 Run the Veritas installer from the VSF_HA_5.1 CD.

Step 2 Enter c followed by 1 to configure the clusters.

The installer prompts you for a system name.

Step 3 Enter the system hostnames of the Primary and Secondary server.

Step 4 Press Enter after the system resumes back after stopping the VCS process.

Step 5 Enter the name of the cluster when system prompts for the cluster name.

Step 6 Enter N to configure Symantec Security Services and press Enter.

Step 7 Enter Y to create a new user for that cluster and press Enter.

Step 8 Enter N for Cluster Management configuration.

Step 9 Enter Y for Cluster Management Console configuration and press Enter.

Step 10 Select the public NICs among the list of NICs and press Enter.

Step 11 Enter the virtual IP Address assigned for that cluster and press Enter.


OL-20722-01


Step 12 Enter the correct netmask and press Enter.

Step 13 Configure the SMTP notification for that server.

Step 14 Start the Cluster Manager by entering /opt/VRTSvcs/bin/hagui on the command prompt.

Step 15 Log in to the cluster using the credentials that you have configured during the Veritas Cluster Server configuration.

Step 16 Select the Cluster Service group and set the following attributes:

a. Select the Show All Attributes option from the pane displayed at the right.

b. Set the value of Onlineretrylimit attribute as 0.

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




• Give the name of the service group as App_datadg.

• Select the Parallel option.


Step 3 Click OK.

Step 4 Add the Disk Group resource with the following configuration:


• Resource Type = Disk Group


You must select the Critical and Enabled checkboxes for this resource. You should add this resource only for local redundancy configuration.

Now the service group is online on both Primary and Secondary servers.

Creating the Replication Service Group on Solaris

To create the Replication Service group on Solaris, do the following on the Primary and Secondary clusters:

Step 1 Start the Cluster Manager by entering /opt/VRTSvcs/bin/hagui at the command prompt.

Step 2 Log in to the cluster using the credentials that you have configured during the Veritas Cluster Server configuration.

You can see the Cluster Service group that is created during the Veritas Cluster Server configuration.


OL-20722-01



• Enter the name of the service group as App_Rep.

• Select the Failover option.



Step 4 Click OK.


• Resource Name =App_Rep_NIC


• TargetResName = csg_nic

This name should be the same as the name of the resource of resource type NIC.


Step 6 Add the RVG resource with the following configuration:

• Resource Name = APP_RVG

• Resource Type = RVG

• RVG = LMS_DR_RVG

• Disk Group= datadg


Step 7 Add the IP resource with the following configuration:

• Resource Name = AppRep_IP


• Address = Virtual IP address

• Device = Public NIC name


Step 8 Add the Disk Group resource with the following configuration:


• Resource Type = Disk Group




Step 9 Right-click on the respective resources and do the following:

• Link APPRep_IP as the parent of App_Rep_NIC.

• Link APP_RVG as the parent of AppRep_IP.

• Link APP_RVG as the parent of datadg.




OL-20722-01


Creating the Application Service Group on Solaris

To create the Application Service group on Solaris:



You can see the Cluster Service group that is created.


• Give the name of the service group as App_Service_GP.

• Select the Parallel Option.

• Select the servers in which the service group to act upon.

Step 4 Click OK.

Step 5 Add the RVG Primary resource with the following configuration:

• Resource Name = App_RVGPrimary

• Resource Type = RVGPrimary

• RvgResourceName = Name of the Resource Configured under the App_Rep Service group

For example, App_Rvg.



• Resource Name =APP_NIC_Proxy


• TargetResName = NIC


Step 7 Add the IP resource with the following configuration.

• Resource Name = APP_IP


• Address = Virtual IP address allocated for this cluster and used by LMS application


• MACAddress = MAC Address of the corresponding NIC card.


Step 8 Add the Volume resource for cscopx volume with the following configuration.

• Resource Name = Volume

• Resource Type = cscopx




OL-20722-01


Step 9 Add the Volume resource for varcscopx volume with the following configuration.

• Resource Name = Volume

• Resource Type = varcscopx



Step 10 Add the Mount resource for cscopx volume with the following configuration:

• Resource Name = cscopx_Mount

• Resource Type = Mount

• Mount Point= Mount_point

• Block Device=Exact Path of cscopx volume

• FSType=vxfs


Step 11 Add the Mount resource for varcscopx volume with the following configuration:

• Resource Name = varcscopx_Mount

• Resource Type = Mount

• Mount Point= Mount_point

• Block Device=Exact Path of cscopx volume

• FSType=vxfs

• FSskopt=-y


Step 12 Import the Agent file from the location /etc/VRTSvcs/conf/config/LMSTypes.cf, into the cluster.

Step 13 Add the Agent resource with the following configuration.

• Resource Name = LMSAgent

• Resource Type = LMS


Step 14 Click the LMS Resource Type and do the following:

a. Select the Show All Attributes option from the pane displayed at the right.

b. Set the value of OnlineTimeout attribute as 1300.

c. Set the value of OfflineTimeout attribute as 1000.

Step 15 Enter the Virtual IP as EventIPAddress.

Step 16 Link cscopx_Mount as the parent of cscopx.

Step 17 Link varcscopx_Mount as the parent of varcscopx.

Step 18 Link cscopx as the parent of App_RVGPrimary.

Step 19 Link varcscopx as the parent of App_RVGPrimary.

Step 20 Link APP_IP as the parent of APP_NIC_PROXY.

Step 21 Link Agent as the parent of cscopx_Mount, varcscopx_Mount and APP_IP.


OL-20722-01


Cluster Configuration for Disaster Recovery on Solaris

This section specifically covers the setup and configuration of the Veritas cluster for the case of two clusters geographically separated with a single node in each cluster.

For a Disaster Recovery Cluster setup, you should:

Step 1 Create a Primary cluster with the server in Site 1 and make all the service groups online.


Step 2 Create a Secondary cluster with the server in Site 2 and make all the service groups online except Application Service Group.


Note The names of the service groups, resources and their configuration should be identical on both the Primary cluster at Site 1 and the Secondary cluster at Site 2.


• Creating the Cluster Service Group on Solaris

• Disaster Recovery Setup Between Primary and Secondary Clusters on Solaris

Creating the Cluster Service Group on Solaris

Configure a Cluster Service group in the servers at both sites to run the following optional components:

• 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 e-mail 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 Perform the steps explained in Creating the Cluster Service Group on both the Primary and Secondary clusters to create the Cluster Service Group.

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



OL-20722-01


Step 3 Link wac as the parent of APP_IP.

Step 4 Link APP_IP as the parent of NIC.

Step 5 Configure the Online Local Firm link between the App_Service_Gp and App_Rep service groups. To do so:

a. Select the App_Service_Gp in the Cluster Administrator Console.

b. Right-click on the App_Rep service group.

c. Select the Online Local Firm link option and select the name of the service group to be linked as App_Rep.

Disaster Recovery Setup Between Primary and Secondary Clusters on Solaris

To establish the Disaster Recovery setup between the clusters, do the following configuration on a Primary cluster:


Step 2 Click Edit > Add/Delete Remote Cluster.

A wizard appears.

Step 3 Click Next.

Step 4 Select the Add Cluster option and click Next.

Step 5 Enter the IP Address of the Secondary cluster.

Step 6 Enter the Username and password which is used to log into that cluster.

A confirmation message appears stating the cluster has been successfully added.

Step 7 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 The permissions has to be provided in both Primary and Secondary clusters.

Step 8 Right-click on App Service Group and select Configure as a Global Option.

The Global Cluster Details window appears.

Step 9 Select the cluster to be used in remote site from the Global Cluster details window and select the Cluster failover policy as Auto.

You can select the failover policy as Manual, if you want to bring the App_Service_Gp online in the remote cluster only after getting the approval from the Cluster Administrator.

Step 10 Enter the Cluster IP address, Username and password.


OL-20722-01

Chapter 4 Setting Up CiscoWorks LMS in High Availability and Disaster Recovery EnvironmentMoving LMS from non-HA to HA Environment

Step 11 Click Configure.

A summary page shows that global group has been successfully configured.

The Remote Cluster status of the App service group shows the status of the service group in both the clusters.

Step 12 Set the attributes for Administrator manually, if they are set already. To do so:

a. Select the App Service Group.

b. Click Show All attributes from the properties tab for Administrator.

c. Click Set Administrators/Operators.

Moving LMS from non-HA to HA EnvironmentYou 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 CiscoWorks LMS 4.0 after the Veritas Setup is complete.

Remote Migration of CiscoWorks LMS 3.1 or LMS 3.2 Data to CiscoWorks LMS 4.0 Server with HA Setup

You can do a remote migration of CiscoWorks LMS 3.1 or LMS 3.2 data to the CiscoWorks LMS 4.0 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 CiscoWorks LMS 4.0 after the Veritas Setup is complete.

4. Migrate the CiscoWorks LMS 3.1 or LMS 3.2 data to the remote CiscoWorks LMS 4.0 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 for instructions to do a remote migration of data to LMS 4.0.

Caution Ensure that the passwords, HTTPS port and SMTP server details are the same in both the servers (LMS 3.1, LMS 3.2 and LMS 4.0 server). This is applicable only for Windows Operating System.


OL-20722-01


C H A P T E R 5
Setting Up CiscoWorks LMS for High Availability, Live Migration, and Storage VMotion Using VMware
This chapter explains setting up CiscoWorks 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).


• Overview of VMware High Availability

• Overview of VMware VMotion and Storage VMotion

Overview of VMware High AvailabilityVMware 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.

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.


Chapter 5 Setting Up CiscoWorks LMS for High Availability, Live Migration, and Storage VMotion Using VMware Overview of VMware High Availability


• 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 AvailabilityThe 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 AvailabilityThe prerequisites for implementing HA in LMS 4.0 using VMware HA are grouped into:

• VMware ESX servers Requirements

• VMware vCenter Server Requirements

• VMware HA Cluster Requirements

• Shared Storage Requirements

• Other Requirements


OL-20722-01


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 successfull HA in LMS 4.0, all redundant network connections must be in the same subnet.

• Ensure a successfull failover before you install LMS 4.0.

Note For more details, see the VMware vSphere 4.0 documentation.


OL-20722-01


Setting up High Availability using VMware HAThis section lists the steps to setup HA for LMS 4.0 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.0 in the virtual machine created in the shared storage.

Creating a VMware HA ClusterYou must create a cluster, populate it with hosts, and configure VMware HA settings before failover protection can be established. To create a VMware HA cluster using vSphere Client:

Step 1 Select the Hosts & Clusters view in vSphere Client.

Step 2 Right-click the Datacenter in the Inventory tree and click New Cluster.

Step 3 Complete the New Cluster wizard.

Do not enable VMware HA (or DRS) at this time.

Step 4 Click Finish to close the wizard and create an empty cluster.

Step 5 Based on your plan for the resources and networking architecture of the cluster, use the vSphere Client

to add hosts to the cluster.

Step 6 Right-click the cluster and click Edit Settings to modify the VMware HA (and other) settings for the cluster.

Step 7 On the Cluster Features page, select Turn On VMware HA.

Step 8 Configure the VMware HA settings for your cluster.

• Host Monitoring Status

• Admission Control

• Virtual Machine Options

• VM Monitoring

Step 9 Click OK to close the cluster's Settings dialog box.

A configured VMware HA cluster, populated with hosts, is created.


OL-20722-01

Chapter 5 Setting Up CiscoWorks 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 VMotionMigration is the process of moving a virtual machine from one host or storage location to another. VMware VMotion allows you to dynamically move workloads to different physical servers or to different underlying storage without service interruption.

VMware Storage VMotion lets you relocate virtual machine disk files between shared storage locations while maintaining continuous service availability and complete transaction integrity.

Migration with VMotion allows working processes in a virtual machine to continue throughout a migration. The entire state of the virtual machine is moved to the new host, while the associated virtual disk remains in the same location on storage that is shared between the two hosts. After the virtual machine state is migrated to the alternate host, the virtual machine runs on the new host.

When you migrate a virtual machine with VMotion, the new host for the virtual machine must meet compatibility requirements in order for the migration to proceed.

Migration with VMotion happens in three stages:

1. When the migration with VMotion is requested, vCenter Server verifies that the existing virtual machine is in a stable state with its current host.

2. The virtual machine state information (memory, registers, and network connections) is copied to the target host.

3. The virtual machine resumes its activities on the new host.

If any error occurs during migration, the virtual machines revert to their original states and locations.

Migration of a suspended virtual machine and migration with VMotion can be referred to as hot migration, because they allow migration of a virtual machine without powering it off.


• VMware vSphere Components for Migration

• Prerequisites for Migration Using VMotion

• VMware vSphere Components for Migration

• Migrating LMS 4.0 Using VMware VMotion


OL-20722-01


VMware vSphere Components for MigrationThe following VMware vSphere components are used for live migration of LMS 4.0:

• 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 VMotionThis 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.


OL-20722-01


• 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.0 Using VMware VMotionThis section lists the steps to migrate LMS 4.0 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 4.0.

7. On each host, configure a VMkernel port group for VMotion.

8. Create a virtual machine and select a datastore as storage disk.

9. Ensure that migration is successful before installing LMS 4.0.

10. Ensure that sufficient resource is available on the target ESX or ESXi host.

11. Install LMS 4.0 in any virtual machine in the cluster.

12. Migrate the virtual machine from one host to another. See Migrating a Virtual Machine with VMotion for more information.

13. Migrate the virtual machine from one storage to another. See Migrating a Virtual Machine with Storage VMotion for more information.


OL-20722-01


Migrating a Virtual Machine with VMotionTo migrate a powered-on virtual machine from one host to another using VMotion technology:

Step 1 Display the virtual machine you want to migrate in the inventory.

Step 2 Right-click on the virtual machine, and select Migrate from the pop-up menu.

Step 3 Select Change host and click Next.

Step 4 Select a destination host for the virtual machine.

If there is a compatibility problem it appears in the Compatibility panel. Fix the problem, or select another host or cluster.

Step 5 Select a resource pool and click Next.

Step 6 Select the migration priority level and click Next.

Step 7 Review the page and click Finish.

A task is created that begins the virtual machine migration process.

Migrating a Virtual Machine with Storage VMotionTo migrate a powered-on virtual machine from one storage to another using VMotion technology:

Step 1 Display the virtual machine you want to migrate in the inventory.

Step 2 Right-click on the virtual machine, and select Migrate from the pop-up menu.

Step 3 Select Change Datastore and click Next.

Step 4 Choose the storage to which the virtual machine has to be migrated.

If there is a compatibility problem it appears in the Compatibility panel. Fix the problem and then proceed with migration.

Step 5 Choose the format to store the virtual machine after migration. By default, it will use the same format type using which the virtual machine was created.

Step 6 Review the page and click Finish.

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


OL-20722-01


C H A P T E R 6
Performing Installation of CiscoWorks LAN Management Solution 4.0
This chapter describes how to install and uninstall LMS 4.0 on Solaris and Windows systems.

It describes the tasks you have to perform for installing LMS 4.0 on both Solaris and Windows systems. It also helps you to verify the installation, uninstall, and reinstall LMS 4.0.

The installation process is explained in the following sections:

• Performing New Installation of LMS 4.0

• Upgrading to LMS 4.0

• Verifying the Installation

• Accessing CiscoWorks Server

• Logging into CiscoWorks Server

• Uninstalling LMS 4.0

• Re-installing LMS 4.0

• Installing CiscoWorks LMS 4.0.x Using Windows 2008 R2 Patch


Chapter 6 Performing Installation of CiscoWorks LAN Management Solution 4.0Performing New Installation of LMS 4.0

Performing New Installation of LMS 4.0This section explains how to install LMS 4.0 on Windows and Solaris systems for the first time. It contains:

• Installing LMS 4.0 on Solaris - New

• Installing LMS 4.0 on Windows - New

• Installing LMS 4.0 in Silent Mode

The LMS 4.0 installation program takes approximately 35 minutes to complete on Windows and approximately 35 minutes to complete on Solaris, on a single server with the recommended hardware requirements.

This can take more than two hours if you perform network management integration while installing.

• If Virus Check is enabled in your system, then installation of LMS 4.0 will take a longer time.

• If HP Openview is running on your system, installation will take a longer time. Disable HP Openview to run a faster installation.

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 CiscoWorks LMS in High Availability and Disaster Recovery Environment”.


OL-20722-01


Installing LMS 4.0 on Solaris - NewFigure 6-1 helps you understand the Typical and Custom installation flows in LMS 4.0 on Solaris.

Figure 6-1 LMS 4.0 Installation on Solaris

2797

79

1 + Enter Typical

Insert the 4.0 Product DVD

Welcome message and license prompt appears [y]

Run the setup.sh installation script

Installing fromNetwork Drive?

Solaris 10 Cluster patch message appears [y]

InstalHigh Availability

for LMS [y]?

2 + Enter Custom

Enter Location to install

Enter Database Password

Enter Admin and Guest Password

Installation proceeds to complete

Enter the License Information

RAM SWAP space check

Enter System Identity Account Password

Enter SMTP Server Details

Installing from Network Drivemessage appears [y]

Typical/Custom Installation Type prompt appears

Enter the License Information

RAM SWAP space check

Enter Admin Password

Enter System Identity Account Password

Installation proceeds to complete

Yes

Yes

No

No


OL-20722-01


To install the LMS 4.0 from the DVD on a Solaris system for the first time:

Step 1 Log into the machine where you want to install LMS 4.0.

Step 2 Insert the LMS 4.0 DVD.

Note We recommend that you run the installation from a local DVD or a local hard drive to avoid errors that may result from the network being slow or busy.Installation from local hard drive will be faster than installation from DVD.If you want to install from a local hard drive, you must copy the contents from the DVD to the local hard drive. Ensure that you copy the entire contents from the DVD to the hard drive. For more information on copying the contents from the DVD to the hard drive, see Installation Notes (For Solaris Only)

Step 3 Run the installation setup script by entering:

# sh setup.sh

or

# ./setup.sh

A Welcome message appears:

Welcome to CiscoWorks LAN Management Solution 4.0 setup program.

A prompt appears:

Press Enter to read/browse the following license agreement:

Step 4 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]:

Step 5 Enter Y to accept the license agreement and proceed with the installation, or enter N to deny and quit the installation.

Note 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.

Step 6 Enter Y to proceed or N to exit installation.

We recommend you download and install the latest required and recommended patches from www.oracle.com, before you run LMS. For more information on Solaris patches, see Solaris Patches.


OL-20722-01



The following warning messages appear to ensure you install the Cluster Patches required for Solaris 10:

WARNING: Ensure that you have installed the recommended Solaris 10 cluster patches released on Apr/17/07, in this server.

WARNING: If these cluster patches are not installed, please download and install them from http://www.sun.com/.

WARNING: Otherwise, some features of the CiscoWorks applications will not function properly.


If you enter Y and proceed with the installation, a message appears prompting you to select any one mode to install.

Step 7 Select any one of the appropriate installation mode to proceed:

• Typical

This is the default installation mode. See Installing LMS 4.0 on Solaris —New (Typical)

• Custom

See Installing LMS 4.0 on Solaris — New (Custom)

Installing LMS 4.0 on Solaris —New (Typical)

To install LMS 4.0 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.0.

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.0:

• 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.


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.


OL-20722-01


Step 3 Enter the CiscoWorks Admin password and confirm it.

For more information on passwords, see Password Information.

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


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.


OL-20722-01


Installing LMS 4.0 on Solaris — New (Custom)

To install LMS 4.0 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


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 characters:

! @ # $ % ^ & * ( ) + | } { " : [ ] ; ' ? < > , . ` = ~

Enter location or q to quit [/opt/CSCOpx]:

The Custom path or location you specify cannot be the sub-directory of /opt/CSCOpx.

Caution Do not remove the link after installation. LMS will not work without this symbolic link.

Step 2 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.0:

• 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.


After specifying the License file for LMS 4.0, the Database Password prompt appears.


OL-20722-01


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


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.

Step 5 Enter the CiscoWorks Admin password and confirm it.


Step 6 Enter the Guest password and confirm it.


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


Step 8 Enter the SMTP server name. For more information, see License Information.

Step 9 Enter the country code, state, city, company, organization, administrator’s e-mail 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.


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.

Step 10 Enter N

Step 11 Enter the user name and password


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]


OL-20722-01


Step 13 Enter Y.

If you have specified LMS 10,000 devices license, the following warning message appears.


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


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.


For troubleshooting information, see Checking Processes After Installation and Understanding Installation Error Messages.


OL-20722-01


Installing LMS 4.0 on Windows - NewFigure 6-2 helps you understand the Typical and Custom installation flows in LMS 4.0 on Windows.

Figure 6-2 LMS 4.0 Installation On Windows


OL-20722-01


To install LMS 4.0 on a Windows system for the first time:

Step 1 Login as administrator to the machine where you want to install LMS 4.0.


Note We recommend that you run the installation from a local DVD or a local hard drive to avoid errors that may result from the network being slow or busy.Installation from local hard drive will be faster than installation from DVD.If you want to install from a local hard drive, you must copy the contents from the DVD to the local hard drive. Ensure that you copy the entire contents from the DVD to the hard drive.

Step 3 Double-click on the autorun.exe or setup.exe file.

The CiscoWorks LAN Management Solution 4.0 window appears.

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

Step 5 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 for HTTPS to avoid this conflict.

Step 6 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 CiscoWorks on an unsupported locale. CiscoWorks 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 Welcome window appears.

Step 7 Click Next to continue.

The Software License Agreement window appears. You must accept this agreement to install CiscoWorks LMS 4.0.

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


OL-20722-01


Step 9 Select one of the following:

• Typical

This is the default installation mode. See Installing LMS 4.0 on Windows — New (Typical)

• Custom

See Installing LMS 4.0 on Windows —New (Custom)

Installing LMS 4.0 on Windows — New (Typical)

To install LMS 4.0 for the first time on a Windows system using the Typical option:

Step 1 Click Next to continue after you select the Typical installation mode.

The Licensing Information dialog box appears.

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

Step 3 Click Next.


The Installation program checks the system configuration and required space.

Step 4 Click Next.

The Enter the Admin Password box appears.

Step 5 Enter the User Admin password and confirm it.

For more information on passwords, see Password Information, page A-5.

Step 6 Click Next to continue installation.

The Enter the System Identity Account Password dialog box appears.


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.


Step 8 Click Next.

The Create casuser information box appears.

Casuser is the user who administers and maintains CiscoWorks Server, without having administrative privileges.

Step 9 Click Yes to continue with installation or No to abort.

The Summary dialog box appears.


OL-20722-01


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

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

Step 12 Click OK.

The following warning message appears.


Step 13 Click OK.

The Restart dialog box appears after the installation is complete.

You need to restart your machine after you have installed LMS 4.0.

Step 14 Select Yes, I want to restart my computer now.


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.0 on Windows —New (Custom)

To install LMS 4.0 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.

The default folder is SystemDrive:\Program Files\CSCOpx. You can choose the destination folder where CiscoWorks will be installed.

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

Step 3 Click Next to proceed.

The Licensing Information dialog box appears for LMS 4.0.


OL-20722-01


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

Step 5 Click Next.


The Installation program checks the system configuration and required space.

Step 6 Click Next.

The Enter the Admin Password box appears.

Step 7 Enter the User Admin password and confirm it.


Step 8 Click Next to continue installation.

The Enter the System Identity Account Password dialog box appears.


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.


Step 10 Click Next.

The Create casuser information box appears.

Casuser is the user who administers and maintains CiscoWorks Server, without having administrative privileges.

Step 11 Click Yes to continue with installation or No to abort.

The Summary dialog box appears.

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

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

Step 14 Click OK.

The following warning message appears.


Step 15 Click OK.

The Restart dialog box appears after the installation is complete.

You must restart your machine after you have installed LMS 4.0.


OL-20722-01


Step 16 Select Yes, I want to restart my computer now.



For troubleshooting information, see Checking Processes After Installation and Understanding Installation Error Messages.

Installing LMS 4.0 in Silent ModeSilent installation or unattended installation is supported in the LMS single installer. You can perform only a fresh installation of LMS 4.0 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.0 in silent mode:


Note We recommend that you run the installation from a local DVD or a local hard drive to avoid errors that may result from the network being slow or busy.Installation from local hard drive will be faster than installation from DVD.If you want to install from a local hard drive, you must copy the contents from the DVD to the local hard drive. Ensure that you copy the entire contents from the DVD to the hard drive.

Step 2 Navigate to images/disk1 directory at the command prompt.

Step 3 Enter the following commands to install LMS 4.0 in silent mode:

• On Solaris: sh setup.sh -q answer_file_name

• On Windows: setup.exe QUIET answerfile=answer_file_name

where answer_file_name is the full path of the user input file stored on the system.

The installation starts.

Step 4 Restart your system after the installation is complete.


OL-20722-01


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:

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.

Property Description

destination Optional. Allows quiet installation to install into a directory other than NMSROOT.

If not specified, installation goes into /opt/CSCOpx on Solaris or c:\Program Files\CSCOpx on Windows.

adminPassword Specifies the login password for the admin user. This is mandatory.

secretPassword

(Solaris only)

Specifies the login password for the secret user.

casuser

(Windows Only)

If casuser password does not exist by the time of installation, the framework generates random password for casuser.

• If the random password is successful, then no input is required.

• If the random password fails, installation opens a dialog requesting new password.

In quiet mode, installation attempts to load the casuser password from the answer file. If no casuser password is specified in the answer file, installation attempts random password, and might fail if the random password does not pass the company policy.

systemIdentityAccountPassword

(Windows only)

Password for the System Identity Account. This is mandatory.


OL-20722-01

Chapter 6 Performing Installation of CiscoWorks LAN Management Solution 4.0Upgrading to LMS 4.0

Upgrading to LMS 4.0The following upgrade paths are supported:

This section contains information on:

• Remote Upgrade to LMS 4.0 on Solaris

• .Remote Upgrade to LMS 4.0 on Windows

Remote Upgrade to LMS 4.0 on SolarisTo upgrade from the previous versions of LMS to LMS 4.0 on a different Solaris machine:

Step 1 Login to the machine where the previous version of LMS is installed.

Step 2 Take a backup of the LMS data.

Step 3 Login to the machine where LMS 4.0 is to be installed.

Step 4 Follow the install procedure using Typical or Custom to install LMS 4.0. See Installing LMS 4.0 on Solaris - New.

Step 5 Migrate the data to LMS 4.0.

To migrate and restore the LMS data, follow the procedure in Migrating Data to CiscoWorks LAN Management Solution 4.0.

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 3.2

Remote Upgrade 1. Back up the data in the old machine.


3. Migrate your data to LMS 4.0 using the instructions explained in the section Migrating Data to CiscoWorks LAN Management Solution 4.0.

LMS 2.2, LMS 2.5, LMS 2.5.1

Remote Upgrade

Direct upgrade to LMS 4.0 is not supported. The suggested upgrade path is:

LMS 2.2 / LMS 2.5 / LMS 2.5.1 > LMS 2.6 > LMS 4.0

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 2.6


4. Migrate your data to LMS 4.0 using the instructions explained in the section Migrating Data to CiscoWorks LAN Management Solution 4.0


OL-20722-01

Chapter 6 Performing Installation of CiscoWorks LAN Management Solution 4.0Verifying the Installation

Notes for Remote Upgrade

When you back up the data from LMS 2.6/3.x and restore the data on LMS 4.0, 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 CiscoWorks LAN Management Solution 4.0.

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 CiscoWorks LMS in High Availability and Disaster Recovery Environment”

.Remote Upgrade to LMS 4.0 on WindowsTo remote upgrade from the previous versions of LMS to LMS 4.0 on a different Windows machine:

Step 1 Log into the machine where the previous version of LMS is installed.

Step 2 Take a backup of the LMS data.

Step 3 Log into the machine where LMS 4.0 is to be installed.

Step 4 Follow the install procedure using Typical or Custom to install LMS 4.0. See Installing LMS 4.0 on Windows - New.

Step 5 Migrate the data to LMS 4.0.

To migrate and restore the LMS data follow the procedure in Migrating Data to CiscoWorks LAN Management Solution 4.0.

Notes for Remote Upgrade

When you back up the data from LMS 2.6/3.x and restore the data on LMS 4.0, 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 CiscoWorks LAN Management Solution 4.0.

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 CiscoWorks LMS in High Availability and Disaster Recovery Environment”.

Verifying the InstallationYou can verify LMS 4.0 installation by following either of these procedures.

Procedure 1

You can verify LMS 4.0 installation using either of these methods:

• Enter the command pdshow from NMSROOT/bin.

Where, NMSROOT is the CiscoWorks installation directory (by default, SystemDrive:\Program Files\CSCOpx and SystemDrive is the Windows operating system installed directory and for Solaris it is /opt/CSCOpx).


OL-20722-01

Chapter 6 Performing Installation of CiscoWorks LAN Management Solution 4.0Verifying the Installation

• Select Admin > System > Server Monitoring > Processes from the menu, to see various processes and their status.

The services that should be displayed after installation are listed below. For details on the various process statuses, refer to the Managing Processes in the Administration of CiscoWorks LAN Management Solution 4.0.:

Functionalities Services/Processes

Common Services • Apache

• CmfDbEngine

• CmfDbMonitor

• CMFOGSServer

• CSDiscovery

• CSRegistryServer

• DCRServer

• DCRDevicePoll

• diskWatcher

• EDS

• CSSCPServer

• EDS-GCF

• ESS

• EssMonitor

• EventFramework

• FDRewinder (Only on Solaris)

• jrm

• LicenseServer

• NameServer

• NameServiceMonitor

• Proxy (Windows only)

• Tomcat

• TomcatMonitor


• ANIServer

• ANIDbEngine

• UTManager

• VNMServer

• UTLITE

• UTMajorAcquisition

• MACUHIC

• WlseUHIC


• ChangeAudit

• ConfigMgmtServer

• ConfigUtilityService

• CTMJrmServer

• EnergyWise

• EssentialsDM

• ICServer

• RMEDbEngine

• SyslogAnalyzer

• SyslogCollector

• PMCOGSServer


OL-20722-01

Chapter 6 Performing Installation of CiscoWorks LAN Management Solution 4.0Accessing CiscoWorks Server

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.

Accessing CiscoWorks ServerLMS, by default, uses port number 1741 to access the CiscoWorks Server in normal (HTTP) mode and port number 443 to access the server in secure (HTTPS) mode.

To access the server from a client system, enter any one of these URLs in your web browser:

• If SSL is disabled and if you have installed the LMS on the default port, enter:

http://server_name:1741

• If SSL is enabled, and if you have installed the LMS on the default port, enter:

https://server_name:443

where server_name is the hostname of the server on which you have installed LMS.

The CiscoWorks Login page appears.

You can change the default web server port numbers (for HTTP and HTTPS modes) using the changeport utility. See Administration of CiscoWorks LAN Management Solution 4.0 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 CiscoWorks LMS.

Fault Management • AdapterServer

• AdapterServer1

• DataPurge

• DfmServer

• DfmServer1

• DFMLogServer

• DFMCTMStartup

• DfmBroker

• DFMMultiProcLogger

• DFMOGSServer

• EPMServer

• EPMDbEngine

• FHPurgeTask

• FHDbEngine

• FHServer

• Interactor

• Interactor1

• InventoryCollector

• InventoryCollector1

• INVDbEngine

• NOSServer

• PMServer

• PTMServer

• TISServer


• IPMProcess

• IpmDbEngine

• IPMOGSServer


• UPMDbEngine

• UPMProcess

• UPMDbMonitor

Functionalities Services/Processes


OL-20722-01

Chapter 6 Performing Installation of CiscoWorks LAN Management Solution 4.0Accessing CiscoWorks Server

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.

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.

Clearing Cache and CookiesThe 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

• Internet Explorer 7

• Mozilla FireFox 3.6

Internet Explorer 8

To clear the cache and cookies:

Step 1 Go to Tools menu.

Step 2 Select Delete Browsing History.

Step 3 Select the check box for Temporary Internet Files and Cookies.

Step 4 Click Delete.

Step 5 Once the files have been deleted, click Okay.

Internet Explorer 7



Step 2 Select Delete Browsing History.

Step 3 Click:

• Delete files to delete Temporary Internet files

• Delete Cookies to delete cookies.

Step 4 Click Yes in the confirmation window.

Step 5 Click Close.


OL-20722-01

Chapter 6 Performing Installation of CiscoWorks LAN Management Solution 4.0Logging into CiscoWorks Server

Mozilla FireFox 3.6



Step 2 Select Clear Recent History.

Step 3 Select Everything from the Time Range to Clear drop-down list.

Step 4 Select Details.

Step 5 Select:

• Cache to clear the browser cache.

• Cookies to delete the cookies.

Step 6 Click Clear Now.

Logging into CiscoWorks ServerAfter you have accessed the CiscoWorks server, to login for the first time, do the following:

Step 1 Enter the username in the User ID field, and the password in the Password field of the Login page.

The CiscoWorks server administrator can set the passwords for admin and guest users during installation. Contact the CiscoWorks server administrator if you do not know the password.

Step 2 Click Login or press Enter.

You are now logged into CiscoWorks server.

The CiscoWorks Getting Started Introduction page appears.

The new CiscoWorks 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 CiscoWorks LMS in Getting Started with CiscoWorks LAN Management Solution 4.0 for more information.


OL-20722-01

Chapter 6 Performing Installation of CiscoWorks LAN Management Solution 4.0Uninstalling LMS 4.0

Uninstalling LMS 4.0This section contains:

• Before You Begin Uninstallation

• Uninstalling LMS 4.0 on Solaris

• Uninstalling LMS 4.0 on Windows

Before You Begin UninstallationThe 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:/CiscoWorks_uninstall_YYYYMMDD_hhmmss.

• The install folder will be removed and the casuser will be removed after uninstallation of LMS 4.0.

Use the Uninstall option to remove LMS files and settings. You must be logged in as administrator to uninstall.

Uninstalling LMS 4.0 on SolarisTo uninstall LMS 4.0 on a Solaris system:

Step 1 Enter the following commands as root to start the uninstall script:

# cd /opt/CSCOpx/bin/

where /opt/CSCOpx is the default installation directory.

Step 2 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/Ciscoworks_uninstall_20060623_102035.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.

• Enter n to continue with uninstall without deleting the collectors in device

The uninstallation proceeds.

After the uninstall is complete, the following messages appear:


OL-20722-01

Chapter 6 Performing Installation of CiscoWorks LAN Management Solution 4.0Uninstalling LMS 4.0

All files were deleted successfully.


The uninstallation program lists the warning and error messages.

Step 3 Check the following files after uninstallation and ensure to perform the following:

• /etc/syslog.conf

Ensure that the following entry is removed: local0.emerg;local0.alert;local0.crit;local0.err;local0.warning;local0.notice;local

0.info;local0.debug /var/adm/CSCOpx/log/dmgtd .log.

• /etc/services

Ensure that port assignments for the LMS 4.0 have been removed.

• /etc/inetd.conf

Ensure that the CiscoWorks TFTP entry is removed.

Uninstalling LMS 4.0 on Windows To uninstall LMS 4.0 on a Windows system:

Step 1 Go to the Windows desktop and select Start > Programs > CiscoWorks > Uninstall CiscoWorks.

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

The uninstallation proceeds and the Uninstallation Complete dialog box appears after uninstallation completes.

Step 2 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 CiscoWorks products may fail if you do not restart your system.


OL-20722-01

Chapter 6 Performing Installation of CiscoWorks LAN Management Solution 4.0Re-installing LMS 4.0

Re-installing LMS 4.0Re-installation is installing the product over the existing one without performing an uninstallation.

You can re-install LMS 4.0 by running the installation program on the system currently running the product. LMS 4.0 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.0, follow the similar procedure as detailed in Performing New Installation of LMS 4.0.

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, 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.

Installing CiscoWorks LMS 4.0.x Using Windows 2008 R2 PatchThis section contains the following:

• Downloading and Installing CiscoWorks LMS 4.0.x Using Windows 2008 R2 Patch

• Re-installing LMS 4.0.x Using Windows 2008 R2 Patch

• Verifying the LMS 4.0.x R2 Installation

Downloading and Installing CiscoWorks LMS 4.0.x Using Windows 2008 R2 Patch

To install the LMS 4.0.x using Windows 2008 R2 patch on Windows 2008 R2 servers for the first time (fresh installation of LMS 4.0.x):

Step 1 Go to http://www.cisco.com/cisco/software/release.html?mdfid=283434800&flowid=19062&os=Windows&softwareid=280775103&release=4.0&rellifecycle=&relind=AVAILABLE&reltype=all

Step 2 Download the patch for Windows 2008 Server Standard and Enterprise Editions Release 2 to your system.

Step 3 Go to the directory where you have downloaded the patch and double-click CiscoWorks_LMS_4.0.x_WIN2K8_R2.exe.


OL-20722-01

http://www.cisco.com/cisco/software/release.html?mdfid=283434800&flowid=19062&os=Windows&softwareid=280775103&release=4.0&rellifecycle=&relind=AVAILABLE&reltype=all

Chapter 6 Performing Installation of CiscoWorks LAN Management Solution 4.0Installing CiscoWorks LMS 4.0.x Using Windows 2008 R2 Patch

If LMS 4.0.x is not installed on R2 server already, a dialog box appears prompting you to select the location of LMS 4.0.x installable.

Step 4 Select LMS 4.0.x installable from DVD or from the local hard drive where you have stored the software images, to proceed with a new installation of LMS 4.0.x along with R2 patch.

If you have selected unsupported Windows installable, the following message appears:

Unable to extract 4.0.x application

If you have selected Windows installable that is corrupted, the following message appears:

Unable to launch 4.0.x application

For more information on performing a new installation of LMS 4.0 see http://www.cisco.com/en/US/docs/net_mgmt/ciscoworks_lan_management_solution/4.0/install/guide/instl.html#wp1580069

The installation of LMS 4.0 along with Windows 2008 R2 patch will take approximately the same time as that of LMS 4.0.


OL-20722-01

http://www.cisco.com/en/US/docs/net_mgmt/ciscoworks_lan_management_solution/4.0/install/guide/instl.html#wp1580069


Re-installing LMS 4.0.x Using Windows 2008 R2 PatchTo reinstall LMS 4.0.x using LMS 4.0.x Windows 2008 R2 patch:

Step 1 Go to the directory where you have downloaded the patch and double-click CiscoWorks_LMS_4.0.x_WIN2K8_R2.exe.

If LMS 4.0.x is installed on R2 server already, the following confirmation message appears:

Click Yes to reinstall LMS 4.0.x along with the Windows 2008 R2 patch. Click No to install

the Windows 2008 R2 patch alone.

Step 2 Either:

• Click Yes to reinstall LMS 4.0.x along with the Windows 2008 R2 patch.

A dialog box appears prompting you to select the location of LMS 4.0.x installable

a. Select LMS 4.0.x installable from DVD or from the local hard drive where you have stored the software images, to proceed with re-installation of LMS 4.0 along with R2 patch.

For more information on re-installing LMS 4.0 see http://www.cisco.com/en/US/docs/net_mgmt/ciscoworks_lan_management_solution/4.0/install/guide/instl.html#wp1387755

If you have selected unsupported Windows installable, the following message appears:

Unable to extract 4.0.x application

If you have selected Windows installable that is corrupted, the following message appears:

Unable to launch 4.0.x application

Or

• Click No to install the Windows 2008 R2 patch alone.

The confirmation message appears:

CiscoWorks daemons need to be stopped to proceed with the installation. Click Yes to stop

the daemons. Click No to abort the installation.

The installation of the Windows 2008 R2 patch alone takes 15 minutes.

Note You have to configure the swap space before running the installation.

Note After the re-installation of R2 patch alone, if you run the LMS 4.0.x Windows 2008 R2 patch installable again, you have to re-install LMS 4.0.x along with the Windows 2008 R2 patch. You do not have the option to choose R2 patch installation alone during the subsequent re-installations.

Step 3 Either:

• Click Yes to stop the daemons and continue with the installation.

Or

• Click No to abort the installation.



OL-20722-01

http://www.cisco.com/en/US/docs/net_mgmt/ciscoworks_lan_management_solution/4.0/install/guide/instl.html#wp1387755


Verifying the LMS 4.0.x R2 InstallationAfter you install the CiscoWorks LMS 4.0.x on Windows, you must verify the installation.

For more information on verifying the installation and accessing Cisco Works Server see Verifying the Installation and Accessing CiscoWorks Server.


OL-20722-01


C H A P T E R 7
Migrating Data to CiscoWorks LAN Management Solution 4.0
This chapter describes how to migrate data to LMS 4.0.

This chapter has the following sections:

• Overview of Migration to LMS 4.0

• Scope of Data Migration

• Migrating Data From LMS 2.6 or 2.6 SP1

• Migrating Data From LMS 3.0 or LMS 3.0 December 2007 Update or LMS 3.1 or LMS 3.2

• Guidelines to Post-Upgrade Activities

Overview of Migration to LMS 4.0Migration 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.0 and then perform remote data migration. LMS 4.0 does not support direct upgrade from previous versions.




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.


Chapter 7 Migrating Data to CiscoWorks LAN Management Solution 4.0Scope of Data Migration

Note While copying the backup data from remote Solaris servers, transfer the data in Binary mode. If any FTP client software is used, ensure that the default transfer mode is set to Binary. The data migration will not be successful if you transfer the backup data in ASCII or Auto mode

.Notes for Remote Migration

When you back up the data from LMS 2.6/3.x and restore the data on LMS 4.0, 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 MigrationThis 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.0.

• On both platforms, migration is supported across different NMSROOT directories, where NMSROOT is the CiscoWorks installation directory. By default, it is:

– /opt/CSCOpx for Solaris

– C:\Program Files\CSCOpx for Windows, where C: is the System Drive

• Cross platform data migration is not supported.

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

• CiscoView Data Migration Scope

• Device Performance Management Data Migration Scope

• Portal Data Migration Scope





OL-20722-01


Common Services Data Migration ScopeThe Common Services (CS) data can be backed up using either using the Normal or the Selective mode.

Normal Backup

The following data gets migrated:

• CiscoWorks 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

• ACS Credentials

• Local User Policy Setup

• System Preferences

• Multiple Default Credentials— Multiple Default Credentials are migrated only when you restore data from LMS 3.2 and LMS 4.0.

• Policy Configuration— Policy Configuration are migrated only when you restore data from LMS 3.2 and LMS 4.0.

• Logrot Configuration— Logrot Configuration are migrated only when you restore data from LMS 3.2 and LMS 4.0.

• DCR Exclude list— DCR Exclude list are migrated only when you restore data from LMS 3.2 and LMS 4.0.

• Unreachable Device Polling Settings— Unreachable Device Polling Settings are migrated only when you restore data from LMS 3.2 and LMS 4.0.

• LDAP Configuration— LDAP Configuration are migrated only when you restore data from LMS 3.2 and LMS 4.0.

Note CS Discovery configuration data and Discovery jobs will be migrated only from LMS 3.0 December 2007 Update and LMS 3.1.


OL-20722-01


Selective Backup

When you run a selective data backup from CLI, all the data mentioned above gets backed up except:

• Software Center map files

• Completed jobs data

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.0 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.0 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.0 server and have been managing some set of the devices then if you migrate the older version LMS data into LMS 4.0 server, after migration the backed up data will be restored in the LMS 4.0 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.0

While restoring ACS backup, the Authentication mode will be changed to CiscoWorks local. 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.0

• Case1: If you have "Group1" in CS, 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 LMS 4.0, "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.0, "Group1" of both CM and RME will be deleted.


OL-20722-01


Network Topology, Layer 2 Services and User Tracking Data Migration ScopeNetwork Topology, Layer 2 Services and User Tracking data in LMS 4.0 (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 b/r.

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.0:

• 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 References— This is applicable only for upgrade.

• 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 and LMS 4.0.

Selective Backup


• Device Details

• Port and VLAN Details

• Campus Archives, UT Archives and VNM Archives

Note Discovery settings will be migrated for LMS 3.0 or lower versions.


OL-20722-01


Inventory, Config and Image Management Data Migration ScopeInventory, Config and Image Management data in LMS 4.0 (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.0:

• 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.


OL-20722-01


• 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 and LMS 4.0.

– User-defined tasks

• NetShow:

– NetShow jobs

– Output archives

– Commandsets

• Software Management

– View/Edit Preferences

– Update Upgrade Information

– Software Management repository images

– All jobs in a Job Browser

• System Preferences

– Application Log Level Settings

– Job Purge

– RME Device Attributes

– RME Secondary Credentials

– Collection Failure Notification


OL-20722-01


• 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 and LMS 4.0.

– Port groups

– Module groups

• Template Center

– Template Center jobs

• WorkCenters

– EnergyWise jobs

– Identity jobs

– ASP jobs

– SI jobs

– SI profiles

– SI configs

Note While restoring data from RME 4.2 to LMS 4.0, all jobs, data and admin settings will be migrated.


OL-20722-01


Selective Backup


• SWIM Images

• Common Reporting Infrastructure archives

• Config editor data

• Syslog data

• Energywise Reports Archives

• SmartInstall Archives

• Identity Report Archives

Fault Management Data Migration ScopeFault Management in LMS 4.0 (known as DFM in earlier LMS versions), can be backed up using either the Normal or the Selective mode.

Normal Backup


• Device list:

The migration procedure adds devices to Common Services Device and Credentials Repository (DCR).

To automatically manage devices from DCR in LMS 4.0, 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

• Data Purge settings— Data Purge settings are migrated only when you restore data from LMS 3.0 December 2007 Update or LMS 3.1.

• Some polling and threshold settings

• Device details

• Trap forward settings

• Notification settings (group, email, trap and syslog settings)

• Notification customization changes


OL-20722-01


• Event sets

• User defined and customizable groups

• JRM Jobs

• Events details

• Fault History details

• SNMP Settings—SNMP Settings are migrated only when you restore data from LMS 3.2 and LMS 4.0.

• Email Subject customization settings—Email Subject customization settings are migrated only when you restore data from LMS 3.2 and LMS 4.0.

Selective Backup


• Events details

• Fault History details

IPSLA Performance Management Data Migration ScopeIPSLA Performance Management in LMS 4.0 (known as IPM in earlier LMS versions), can be backed up using either the Normal or the Selective mode.

Normal Backup


• IPSLA Collectors

• IPSLA database—Contains information about source devices, target devices, operations, collectors, and the statistics of data collected.

• The settings in ipm.env file

Note HTML reports available in IPM 2.6 is backed-up but not restored by running restorebackup.pl.

You can generate consolidated System Reports for data migrated from IPM 2.6 to LMS 4.0. However, the time taken to generate the reports depends on the length of the period for which you are querying.

For example, generating reports for a period of 6 months may take a longer time, than generating reports for a period of 10 days.

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

NMSROOT/CSCOpx/MDC/tomcat/webapps/ipm/archive_charts


OL-20722-01


• Windows

NMSROOT\MDC\tomcat\webapps\ipm\system_reports

NMSROOT\CSCOpx\files\ipm\ and

NMSROOT\CSCOpx\MDC\tomcat\webapps\ipm\archive_charts

When you install IPM 4.2, and migrate from LMS 3.0 or LMS3.0 December 2007 Update or LMS 3.1to LMS 3.2 and LMS 4.0, 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 ScopeThe CiscoView (CV) data can be backed up using the Normal mode. When you upgrade to LMS 4.0, the user’s device preferences are migrated. In LMS 4.0, CiscoView is available at Inventory > Tools > CiscoView.

Device Performance Management Data Migration ScopeDevice Performance Management in LMS 4.0 (known as HUM in earlier LMS versions) can be backed up using either the Normal or the Selective mode.The following data gets migrated when you restore LMS 3.X (HUM) backup in LMS 4.0:

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 / HUM 1.2 backup.

• Job Information / Reports (system defined and user defined)

– Suspended job instances will be moved to scheduled state.


OL-20722-01


• 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 / HUM 1.2 backup).

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 / HUM 1.2 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 / HUM 1.2 backup).

Portal Data Migration ScopeThe LMS Portal data can be backed up using the Normal mode. The CiscoWorks Portal configuration or settings get migrated when you remote upgrade to Portal 2.0. All the private page customization in the earlier LMS version (3.x) will be migrated after remote upgrade.


OL-20722-01

Chapter 7 Migrating Data to CiscoWorks LAN Management Solution 4.0Migrating Data From LMS 2.6 or 2.6 SP1

Migrating Data From LMS 2.6 or 2.6 SP1 This section explains how to migrate data from LMS 2.6 or 2.6 SP1 to LMS 4.0.

It also explains the procedure of Migrating Data for Common Services, Inventory, Config and Image Management, Network Topology, Layer 2 Services and User Tracking, Fault Management, IPSLA Performance Management and CiscoView to a remote machine.

In this section, the machine that has LMS 2.6 or 2.6 SP1 data is referred to as Machine A and the remote machine where you need to install LMS 4.0 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.


• Migrating Data on Solaris

• Migrating Data on Windows

Migrating Data on SolarisTo migrate LMS 2.6 or 2.6 SP1 data to a remote machine:

Step 1 Log in as root into Machine A.

Step 2 From the LMS 4.0 DVD, locate the SolarisLMSBackup.tar file under disk1/install directory.

Step 3 Copy the file (SolarisLMSBackup.tar) to a directory (dir1) in the local server.

The tar file contains wrapper.pl and other required files.

Step 4 Untar the file to get wrapper.pl

Note If you need to backup DFM 2.0.10, install DFM 2.0.11 before taking the backup. If not, the backup will fail.

Step 5 Back up LMS 2.6 data.

To do this using CLI, go to the location of wrapper.pl and enter the following command:

NMSROOT/bin/perl wrapper.pl BKP

where BKP is the backup directory.

For example, if BKP is under /opt, enter the path as NMSROOT/bin/perl wrapper.pl /opt/BKP

Step 6 Log in as root into Machine B.

Step 7 Install LMS 4.0.

Step 8 Copy the backup directory BKP that contains the LMS 2.6 data from Machine A to any temporary location.

Note You can preserve the time stamp of the files by entering the option -p with the copy command: cp -rp source destination.


OL-20722-01


Step 9 Stop the daemon manager by entering:

/etc/init.d/dmgtd stop

Step 10 Restore the backed up data by entering:

NMSROOT/bin/perl NMSROOT/bin/restorebackup.pl -d BKP [-t temporary_directory]


You must give 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.

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

• /var/adm/CSCOpx/log/ipm_base.log

Note The migration.log will be created only when either RME or IPM (part of LMS 2.6 or 2.6 SP1) is migrated. However, the rme_base.log and ipm_base.log are created only when RME and IPM are migrated.

Step 12 Start the daemon manager by entering:

/etc/init.d/dmgtd start

Migrating Data on WindowsTo migrate LMS 2.6 or 2.6 SP1 data to a remote machine:

Step 1 Log in as administrator into Machine A.

Step 2 From LMS 4.0 DVD, locate the WindowsLMSBackup.tar file under disk 1/install directory.

For the LMS 4.0 evaluation image downloaded from Cisco.com, the WindowsLMSBackup.tar file is available in a directory under the %temp% directory. The name of the %temp% directory will vary as it is randomly created for every installation.

For example, the randomly created directory name can be C:\DOCUME~1\pdandapa\LOCALS~1\Temp\{58D59C97-B4FA-4022-AA54-5191C2642C66.

To view the temp directory:

a. From the Taskbar, choose Start > Run and enter %temp%.

b. Click OK button.

c. Search for the WindowsLMSBackup.tar file in the above temp directory.

Step 3 Copy the file (WindowsLMSBackup.tar) to a directory (dir1) in the local server.

The tar file contains wrapper.pl and other required files.


OL-20722-01


Step 4 Untar the file to get wrapper.pl

Note If you are about to backup DFM 2.0.10, install DFM 2.0.11 before taking the backup. If not, the backup will fail.

Step 5 Back up LMS 2.6 data.

To do this using CLI, go to the location of wrapper.pl and enter the following command:

NMSROOT\bin\perl wrapper.pl BKP


For example, if BKP is under C:\, enter the path as NMSROOT\bin\perl wrapper.pl C:\BKP.

Step 6 Log in as administrator into Machine B.


Step 8 Copy the backup directory BKP that contains the Common Services, Inventory, Config and Image Management, Network Topology, Layer 2 Services and User Tracking, IPSLA Performance Management, CiscoView and Fault Management data from Machine A to any temporary location.


net stop crmdmgtd


NMSROOT\bin\perl NMSROOT\bin\restorebackup.pl -d BKP [-t temporary_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.



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

NMSROOT\log\ipm_base.log

Note The migration.log will be created only when either RME or IPM (part of LMS 2.6 or 2.6 SP1) is migrated. However, the rme_base.log and ipm_base.log are created only when RME and IPM are migrated.


net start crmdmgtd


OL-20722-01

Chapter 7 Migrating Data to CiscoWorks LAN Management Solution 4.0Migrating Data From LMS 3.0 or LMS 3.0 December 2007 Update or LMS 3.1 or LMS 3.2

Migrating Data From LMS 3.0 or LMS 3.0 December 2007 Update or LMS 3.1 or LMS 3.2

This section explains how to migrate data from LMS 3.0 or LMS 3.0 December 2007 Update or LMS 3.1 or LMS 3.2

This section explains the procedure of Migrating Data on Solaris to a remote machine. HUM is a add-on application and it is optional.

In this section, the machine that has LMS 3.0 or LMS 3.0 December 2007 Update or LMS 3.1 or LMS 3.2 is referred to as Machine A and the remote machine where you need to install LMS 4.0 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.


• Migrating Data on Solaris

• Migrating Data on Windows

Migrating Data on SolarisTo migrate LMS 3.x data to a remote machine:

Step 1 Log in as root into Machine A.

Step 2 Back up LMS 3.x data.

To do this using CLI, enter the following command:

NMSROOT/bin/perl NMSROOT/bin/backup.pl BKP


You must enter the absolute path for BKP. For example, if BKP is under /opt, give the path as NMSROOT/bin/perl NMSROOT/bin/backup.pl /opt/BKP

Step 3 Log in as root into Machine B.


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




NMSROOT/bin/perl NMSROOT/bin/restorebackup.pl -d BKP [-t temporary_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.


OL-20722-01




You can also restore data from CiscoWorks LMS 3.2 to the CiscoWorks LMS 4.0 server with Symantec Veritas or VMware HA implementation.

• For details on High Availability (HA) implementation using Symantec Veritas, see Setting Up CiscoWorks LMS in High Availability and Disaster Recovery Environment.

• For details on High Availability (HA) implementation using VMware, see Setting Up CiscoWorks LMS for High Availability, Live Migration, and Storage VMotion Using VMware.

Step 8 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 The migration.log and the rme_base.log will be created only when RME (part of earlier LMS versions) is migrated.



Migrating Data on WindowsTo migrate LMS 3.x data to a remote machine:

Step 1 Log in as administrator into Machine A.

Step 2 Back up LMS 3.x data.

To do this using CLI, enter the following command:

NMSROOT\bin\perl NMSROOT\bin\backup.pl BKP


You must enter the absolute path for BKP. For example, if BKP is under C:\, enter the path as NMSROOT\bin\perl NMSROOT\bin\backup.pl C:\BKP.

Step 3 Log in as administrator into Machine B.


Step 5 Copy the backup directory BKP that contains the LMS 3.x data from Machine A to any temporary location.


net stop crmdmgtd


NMSROOT\bin\perl NMSROOT\bin\restorebackup.pl -d BKP [-t temporary_directory]



OL-20722-01


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.



You can also restore data from CiscoWorks LMS 3.2 to the CiscoWorks LMS 4.0 server with Symantec Veritas or VMware HA implementation.

• For details on High Availability (HA) implementation using Symantec Veritas, see Setting Up CiscoWorks LMS in High Availability and Disaster Recovery Environment.

• For details on High Availability (HA) implementation using VMware, see Setting Up CiscoWorks 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 server and LMS 4.0 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 The migration.log and rme_base.log will be created only when RME (part of earlier LMS versions) is migrated.


net start crmdmgtd


OL-20722-01

Chapter 7 Migrating Data to CiscoWorks LAN Management Solution 4.0Guidelines to Post-Upgrade Activities

Guidelines to Post-Upgrade ActivitiesThis section contains:

• Guidelines for Fault Management Post-Upgrade Activities in LMS 4.0

• Guidelines for Common Services Post-Upgrade Activities

• LMS 4.0 AAA Methods

• Resetting the Login Module

Guidelines for Fault Management Post-Upgrade Activities in LMS 4.0This section contains the complete basic configuration steps for Configuring SNMP Trap Receiving and Forwarding.

Configuring SNMP Trap Receiving and Forwarding

By default, LMS receives SNMP traps on port 162 (or, if port 162 is occupied, port 9000). If you need to change the port:

Step 1 Select Admin > Network > Notification and Action Settings > Fault - SNMP trap receiving settings.

The configuration page for SNMP trap receiving is launched.

Step 2 Enter the port number in the Receiving Port entry box.

Step 3 Click Apply.

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.0


OL-20722-01


Guidelines for Common Services Post-Upgrade ActivitiesThis section contains the CS Authorization, Authentication, and Accounting (AAA) methods.

LMS 4.0 AAA MethodsLMS 4.0 supports only one AAA mode; CiscoWorks Local Mode.

CiscoWorks Local Mode

LMS 4.0 server supports the following Login Modules in CiscoWorks Local Mode mode:

• CiscoWorks Local

• IBM SecureWay Directory

• KerberosLogin

• Local NT System (Windows only)

• Local Unix System (Solaris only)

• MS Active Directory

• Netscape Directory

• RADIUS

• TACACS+

LMS 4.0 uses CiscoWorks server authentication (CiscoWorks Local Mode) to authenticate users and authorize them to access LMS.

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.


OL-20722-01


Resetting the Login ModuleYou can run the following commands to reset the Login Module to CiscoWorks local mode:

On Solaris:

Step 1 Stop the LMS system by entering:


Step 2 Run the following script:

NMSROOT/bin/perl NMSROOT/bin/ResetLoginModule.pl

Step 3 Start the LMS system by entering:


On Windows:

Step 1 Stop the LMS system by entering:

net stop crmdmgtd

Step 2 Run the following script:

NMSROOT\bin\perl NMSROOT\bin\ResetLoginModule.pl

Step 3 Start the LMS system by entering:

net start crmdmgtd


OL-20722-01



OL-20722-01


C H A P T E R 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 InstallationYou can run a self test or view process failures from the CiscoWorks 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 StatusYou 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 CiscoWorks server only if you have local administrative privileges.


Chapter 8 Troubleshooting and FAQsViewing and Changing Process Status

To view or change the process status:

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

The Process Management page appears.

Step 2 You can stop and start the processes:

• Stop:

• Select the processes from this page that you want to stop.

• Click Stop.

If you select specific processes, the dependent processes also stop.

• Start:

• Select the processes from this page that you want to start.

• Click Start.

Only the selected processes are started. The dependent processes are not started.

For Windows:

• To stop all processes from the server, enter:

net stop crmdmgtd

• To start all processes from the server, enter:

net start crmdmgtd

For Solaris:

• To stop all processes from the server, enter:


• To start all processes from the server, enter:


Caution Do not start the daemon manager immediately after you stop it. The ports used by daemon manager will be in use for a while even after the daemon manager is stopped. Wait for a few minutes before you restart the daemon manager.


OL-20722-01

Chapter 8 Troubleshooting and FAQsContacting 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.0.

This installation log file is C:\Ciscoworks_install_YYYYMMDD_hhmmss.log, where YYYYMMDD denotes the year, month and date of installation and hhmmss denotes the hours, minutes and seconds of installation.

Generate a report and email the generated report to Cisco TAC.

To generate the report:

Select Admin > System > Server Monitoring > Collect Server Information from the menu

Understanding Installation Error MessagesTable 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

CiscoWorks LMS installation cannot proceed because you are not logged in as an administrator.

You are not logged into Windows with administrator privileges.

Log into Windows with local administrator privileges and try installing again.

The setup program has discovered HP OpenView services running. This will lock some of the CiscoWorks dlls.

Stop all HP OpenView services before installing CiscoWorks.

HP Network Node Manager (HPNNM) or NetView is running on the same system.

Stop all HP OpenView services and continue to install CiscoWorks.

Decompression failed on file. The error was for error code per CompressGet.

When you downloaded CiscoWorks, a transmission error occurred or the installation medium is damaged.

Retry the download. If you still have errors, contact your technical support representative.

General file transmission error.

Please check your target location and try again. Error number: error code.

When you downloaded CiscoWorks, a transmission error might have occurred.

Retry the download. If you still have errors, contact your technical support representative.


OL-20722-01

Chapter 8 Troubleshooting and FAQsUnderstanding Installation Error Messages

Severe: Cannot run the dependency handler.

When you have downloaded CiscoWorks, 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.

Cannot write infoFile

or

Cannot create infoFile.

A file-write operation failed. Run the file system checking utility, then repeat the installation.

1. Verify that you have write permission to the destination directory and windows TEMP directory.

2. Repeat the installation.

The environment variable %TEMP% provides the location on TEMP directory.

Cannot stop service servicename.

The installation (or reinstallation) tried to stop the service servicename unsuccessfully.

1. Select Control Panel > Services and stop service servicename manually.

2. Continue to install or uninstall.

UseDLL failed for dll. dll should be available at any time for any process, but Windows did not load it.

• Check permissions on the system32 directory under %WINDIR%. If the dll is secure.dll or r_inst.dll, check product installation media for errors.

Or

• Reinstall Windows.

function failed: DLL function not found.

dll should be available at any time for any process, but Windows did not load it.

• 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.

Table 8-1 Installation Error Messages (continued)



OL-20722-01


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.

Setting file permissions failed because you may not be allowed to change them.

Log in as administrator.

If you are installing on a FAT file system, LMS 4.0 cannot provide file security.

Launch of isql script failed. The existing database file is corrupted or the previous version of LMS 4.0 is destroyed.

The problem may occur during reinstallation.

Contact your technical support representative.

The product should not be installed in a root directory.

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

Select a directory other than the root directory to install the product.

The product should not be installed in a remote directory.

You tried to install the product in a directory of a drive that is remotely mounted or using the UNC pathname.

Select a directory on a local hard-drive.

The selected directory is not empty. Mixing new and existing files can cause severe problems during installation.

You tried to install in a directory that contains some files.

Remove all files from directory or choose another directory to install the product.

The installer requires temporary workspace.

You have less than 8 MB of free space on drive. Free up some space and try again.

There is not enough drive space for temporary installation files.

Make more drive space available (%TEMP%), then rerun installation.

You are attempting to install LMS on a server that is configured as a Primary Domain Controller or a Backup Domain Controller (PDC/BDC).

You are trying to install the application on a server that is configured as a Primary Domain Controller or a Backup Domain Controller (PDC/BDC).

Install LMS on another server not configured as PDC / BDC.




OL-20722-01


You are attempting to install LMS on an unsupported operating system.

The installation will exit when you close this message.

You are trying to install the application on an operating system that does not match System Requirements for the product.

• Upgrade the Operating System on the Server to a supported version

Or

• Install LMS on another server running a supported Operating System.

You are attempting to install CiscoWorks on operating system and service pack.

Please run installation again on a supported platform. Do you want to proceed?

You are trying to install the application on an operating system that does not match System Requirements for the product

Run installation again on a supported platform.

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.

You are trying to install the product from a copy of the DVD or from the DVD drive of another system in the network.

Copy the installable image to a local drive or use local DVD drive.

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 product from another system in the network.

Copy the installable image to a local drive or use local CD drive.




OL-20722-01


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

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.

Click on the directory on which you want 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.

The destination directory contains spaces in the directory name and the directory name cannot be converted to a MS-DOS format.

• 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.

Cannot determine the local Administrators group.

The installation program cannot find one of the built-in Windows user groups. This prohibits LMS 4.0 security setup.

1. Check the Operating System.

2. Reinstall Windows if necessary,

3. Rerun LMS 4.0 installation.

Cannot determine the local Everyone group.

The installation program cannot find one of the built-in Windows user groups. This prohibits the setup of LMS 4.0 security.

1. Check the Operating System.

2. Reinstall Windows if necessary,

3. Rerun LMS 4.0 installation.

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 may not have permissions on the directory.

Select another destination directory.




OL-20722-01


Could not set file permissions. The installation program cannot set file permissions. Most likely causes are:

• 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.

1. Correct the problem.

2. Rerun installation program.

task_name is already running! Wait for it to complete and click OK.

One installation subtask is still running.

1. Wait for installation subtask to finish running.

2. Click OK to proceed.

Cannot create/open log file. The installation program could not create or open the installation log file.

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.

Error creating / modifying casuser - name.

Click Yes if you want to try again.

Click No if you want the Install to terminate.

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.

• 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.

Cannot find script to upgrade database.

Problem with database upgrade.


Database upgrade failed. Problem with database upgrade.


Database upgrade result unknown.

Problem with database upgrade.


The installer has discovered HP OpenView services running. The installation might take significantly longer to complete with these services running.

HP OpenView services are running.

Stop all HP OpenView services before installing LMS 4.0.

You do not have to restart the system after stopping HP OpenView.




OL-20722-01


ODBC Driver Manager 3.510 or later is required by LMS 4.0. Install ODBC 3.510 first.

CiscoWorks Common Services software requires ODBC Driver Manager version 3.510 or later.

Install Microsoft Data Access Component (MDAC) 2.1 or higher.

Make sure that all ODBC Core Components have the same version number.

See the Microsoft web site for installation instructions.

ODBC is not available from Microsoft as a stand-alone installation but is packaged along with MDAC.

Name lookup failed for hostName. Please configure the hostname and and then try installation.

Your hostname is not configured properly.

Configure the hostname and continue 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.

Some of the executables and DLLs installed by CiscoWorks are locked.

1. Stop LMS 4.0.

2. Close Browsers and make sure CiscoWorks CLIs are not used at the moment.

After stopping all the applications, proceed with the installation.

3. Stop the ACS service if it is installed.

Do you want to verify that CiscoWorks 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.

Some of the executables and DLLs installed by CiscoWorks are in use.

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 CiscoWorks 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.0 daemon manager running.

5. Run the installation again.




OL-20722-01


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.

You have installed CiscoWorks Common Services on a Pentium IV machine.

Click OK, and ignore the message. The installation will continue normally.

java.exe has generated errors and will be closed by Windows. You must restart the program. An error log is being created.

This message appears when you install CiscoWorks Common Services on a Pentium IV machine.

Click OK, and ignore the message. The installation will continue normally.

CreateService - service name - The specified service is marked for deletion.

The registry entries related to the service are not deleted during the uninstallation.

1. Restart the machine

2. Reinstall LMS 4.0.

If the problem still exists:

1. Uninstall LMS 4.0

2. Restart the machine,

3. Start a fresh installation.

One instance of CiscoWorks 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.

CiscoWorks installation is already running.

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.

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.

The backup process failed. Retry backing up again.

Dependency handler error occurs and installation quits

Cisco Security Agent is enabled.

Disable the Cisco Security Agent and then start the install.




OL-20722-01


Install fails to start after clicking the setup.exe / holds up in post install

• 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.

• To work around this issue, kill the cmgshieldUI.exe from the task manager/ process explorer. Care must be taken not to kill the cmgshield svc.exe, as this will reboot the machine automatically.

• Disable the antivirus.

The self extracting exe fails with the not enough disk space error.

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.

Make minimum of 2 GB free space in the C: or temp present directory and then proceed the installation.

Install fails with the message "Cannot load global.properties"

• User should be logged into the server as the local administrator (not the domain admin) when doing the install.

• Temp directory is having long path or is not proper.

• Login with the administrator mode.

• Change the temp directory path.

DB values are not getting registered and throw the ERROR: [IsDaemonManagerOff] cannot execute C:\PROGRA~1\CSCOpx\bin\pdshow.cmd

The issue occurs when the system32 is not in the path variable.

• 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:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;

• Append the following path for 32 bit OS

"c:\windows;c:\windows\sytem32;c:\windows\system32\wbem"




OL-20722-01


Install error while configuring tomcat

Error "OpenService: The specified service does not exists as an installed service" while tomcat configuration during install

Check if DEP is enabled in the server. You can check the same here. Right Click on My Computer and go to Properties > Advanced > Click the "Settings" button in the Performance frame > Data Execution Prevention. If it is enabled for all the programs then disable it and try installing CiscoWorks again.

Error in validating a package in Solaris install

ERROR: The following base package image is bad: <package>

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

After fresh install of LMS, the page is not displayed and the daemon Manager wont be up and throw the swap Error.

We recommend minimum 8 GB swap space to up the LMS process. If the server has less than that daemon will not come up.

• 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\SOFTWARE\Cisco\Resource Manager\CurrentVersion\Environment

Daemon Manager down and process are not up.

The Daemon Manager port 42340 may be occupied by some other third party application.

Check the port state by "nestat -na | grep 42340" command. Please free the port and restart the Daemon Manager.

Installation fails in Solaris. Stale process might be running in the memory.

Check the stale process by "ps -ef | grep CSCO" command. And kill it manually by using the “kill -9 pid” then start the install.




OL-20722-01


Scheduled periodic backup is active even after Uninstall the build in both Solaris and Windows.

When machine performance is very slow. Then the OS itself will quit the Perl command and the files will not get remove from task scheduler.

Run the following command from the command prompt Once the performance up.

For Windows:

Logrot: C:/PROGRA~1/CSCOpx\bin\perl C:\PROGRA~1\CSCOpx\objects\logrot\schedulelogrot.pl C:\ 0 0 cancel

Backup: C:/PROGRA~1/CSCOpx\bin\perl C:/PROGRA~1/CSCOpx\cgi-bin\dbadmin\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.

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.

Backed up license count would be mismatched with the current license count installed in the restore server.

Need to apply the new license with higher count once the restore is done.

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

Backed up LMS license count is greater than 5000.

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.




OL-20722-01

Chapter 8 Troubleshooting and FAQsTroubleshooting Errors in Data Migration

Troubleshooting Errors in Data MigrationThis chapter describes the errors that you might encounter during data migration and guidelines on troubleshooting those errors.


• Common Services Data Migration Errors

• Inventory, Config and Image Management Data Migration Errors

• 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.0. Also, make sure the server has enough space to do the DB backup and restore.

• Check migration logs. The logs migration.log and restorebackup.log are available under:

– Solaris: /var/adm/CSCOpx/log

– Windows: NMSROOT\log

• Note that time taken to collect inventory is directly proportional to the number of devices and the network response time

If you encounter problems during the data migration process, do the following to clean up the temporary files and return to the initial state:

Step 1 Stop the LMS system by entering,

• On Solaris


• On Windows

net stop crmdmgtd

Step 2 Run the following commands:

• On Solaris

NMSROOT/bin/perlNMSROOT/objects/db/conf/configureDb.pl action=unreg dsn=dsn_name dmprefix=dmprefix_name

NMSROOT/bin/perlNMSROOT/objects/db/conf/configureDb.pl action=uninstall dsn=dsn_name

rm -fr NMSROOT/tempBackupData


OL-20722-01


• On Windows

NMSROOT\bin\perlNMSROOT\objects\db\conf\configureDb.pl action=unreg dsn=dsn_name dmprefix=dmprefix_name

NMSROOT\bin\perlNMSROOT\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.0.

Step 3 Start the LMS system by entering,

• On Solaris


• On Windows

net start crmdmgtd

Functionalities dsn_name dmprefix

Common Services cmf Cmf

Configuration Management rmeng RME


ani ANI

Fault Management • dfmEpm

• dfmInv

• dfmFh

• EPM

• INV

• FH

IPSLA Performance Management ipm Ipm

Device Performance Management upm UPM


OL-20722-01


Common Services Data Migration ErrorsIf you encounter errors during CS data migration, you can use the following options to troubleshoot the problems:

• CAM (Core Admin Module) debugging:

You can enable CAM debugging by entering:

NMSROOT/MDC/bin/ccraccess -updateLog Core cam DEBUG

You can disable CAM debugging by entering:

NMSROOT/MDC/bin/ccraccess -updateLog Core cam WARN

Daemon Manager restart is necessary.

• CAM debug details:

CAM debug details are logged at:

NMSROOT/MDC/log/core-MM-DD-YYYY.log

• Server information:

To collect server information, select Admin > System > Server Monitoring > Collect Server Information from the menu.

This allows you to quickly collect all information about the state of the system. You can send this information as a report, to TAC for troubleshooting.

This report provides information about System configuration, environment settings, application configuration details, process status, and product log files.

• SelfTest tool:

You can select Admin > System > Server Monitoring > Selftest from the menu to invoke the SelfTest tool.

The SelfTest tool checks the integrity and health of the system for some of the Common Services components.

This tool helps to debug issues of corrupted files and issues related to failure of some basic components. It runs PERL scripts that provide outputs that indicate whether a specific test is successful.


OL-20722-01


Inventory, Config and Image Management Data Migration ErrorsIf 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.0. 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:

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.

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


OL-20722-01


Network Topology, Layer 2 Services and User Tracking Data Migration ErrorsIf 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


OL-20722-01


– 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


OL-20722-01


Fault Management Data Migration ErrorsIf 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


OL-20722-01


Windows:

– NMSROOT\databases\dfmEpm\dfmEpm.db

– NMSROOT\databases\dfmInv\dfmInv.db

– NMSROOT\databases\dfmFh\dfmFh.db

IPSLA Performance Management Data Migration ErrorsIf 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


OL-20722-01


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 ErrorsIf you encounter errors during Device Performance Management data migration, please check the following logs:

• restorebackup.log

• upm_process.log

The logs are available at:

• Solaris:

/var/adm/CSCOpx/log

• Windows:

NMSROOT\log

You may also encounter the following types of errors while migrating Device Performance Management data:

• If pollers, templates, or thresholds are not migrated properly, make sure the Device Performance Management backedup database contains the related data.

• If reports are not migrated, make sure filebackup.tar contains the reports in NMSROOT/MDC/tomcat/webapps/upm/reports folder.

• If threshold scripts are not migrated, make sure filebackup.tar contains the reports in NMSROOT/hum/thresholdscripts.

• If Poller failures are observed, make sure the devices are SNMP reachable from Device Performance Management server.


OL-20722-01

Chapter 8 Troubleshooting and FAQsFrequently Asked Questions

Frequently Asked QuestionsThis section provides Frequently Asked Questions (FAQs) on LMS 4.0 Installation and Data Migration and the respective solutions.

This section lists the FAQs:

• Where can I find the install logfiles for LMS 4.0?

• I have LMS 2.6 applications installed on different servers. Can I migrate data from these multiple servers to one LMS 4.0 server?

• I have LMS 2.6 installed on Windows 2000 Server. I want to upgrade the OS to Windows 2003 Server, and also upgrade to LMS 4.0. In what order should I perform these upgrades?

• I have been running LMS 4.0 for sometime, and have collected a lot of data. I would like to restore an older LMS 2.6 SP1 backup, and merge the data from the current system and the backup. Is this possible?

• I have LMS 3.1 installed on Windows 2003 Server. I would like to upgrade the Operating System to Windows 2008 Server, and also upgrade to LMS 4.0. In what order should I perform these upgrades?

• On which operating system is LMS 4.0 supported?

• Which Windows HotFix patches are supported for LMS 4.0?

• Is LMS 4.0 supported on 64-bit native systems?

• Can I install LMS 4.0 with Internet Information Services (IIS) enabled?

• Which TCP and UDP ports does CiscoWorks LMS 4.0 use?

• Does LMS 4.0 support virtual machines, such as VMware and VirtualPC?

• Can I install LMS 4.0 with Windows Domain Controller enabled?

• Is LMS 4.0 supported on Solaris x86 (on the x86 CPU)?

• Is LMS 4.0 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.0 on Solaris. I want to migrate to Windows. Do I need to get a new license for LMS 4.0 on Windows?

• When should I install other Network Management Systems (such as HP OpenView Network Node Manager, Netview)?


OL-20722-01


Q. Where can I find the install logfiles for LMS 4.0?

A. On Solaris, if errors occur during installation, check the installation log file /var/tmp/Ciscoworks_install_yyyymmdd_hhMMss.log. 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 Common Services installation creates SystemDrive:\Ciscoworks_install_yyyymmdd_hhMMss.log.

Q. I have LMS 2.6 applications installed on different servers. Can I migrate data from these multiple servers to one LMS 4.0 server?

A. No, this option is not supported.

Q. I have LMS 2.6 installed on Windows 2000 Server. I want to upgrade the OS to Windows 2003 Server, and also upgrade to LMS 4.0. In what order should I perform these upgrades?

A. You must:

a. Upgrade your Operating System to Windows 2003 (SP1 & SP2) R2 Standard & Enterprise edition or Windows 2008 (SP1)Server.

b. Upgrade LMS 2.6 to LMS 4.0 on Windows 2003 (SP1 & SP2) R2 Standard & Enterprise edition or Windows 2008 (SP1)Server.

Q. I have been running LMS 4.0 for sometime, and have collected a lot of data. I would like to restore an older LMS 2.6 SP1 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. I have LMS 3.1 installed on Windows 2003 Server. I would like to upgrade the Operating System to Windows 2008 Server, and also upgrade to LMS 4.0. In what order should I perform these upgrades?

A. You must:

a. Upgrade LMS 3.1 to LMS 4.0 on Windows 2003 Server.

b. Upgrade your Operating System to Windows 2008 Server.

Q. On which operating system is LMS 4.0 supported?

A. See System and Browser Requirements for Server and Client for details.

Q. Which Windows HotFix patches are supported for LMS 4.0?

A. For LMS 4.0, we have tested all the Windows HotFix patches released up to July 2010 that have an impact on LMS:

http://www.microsoft.com/technet/security/bulletin/MS10-044.mspx

Q. Is LMS 4.0 supported on 64-bit native systems?

A. Yes, LMS 4.0 is supported on native 64-bit systems. See Operating System Requirements for more information.

Q. Can I install LMS 4.0 with Internet Information Services (IIS) enabled?

A. Yes, you can install. If you click No you must stop IIS services before installing LMS 4.0. 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.


OL-20722-01

http://www.microsoft.com/technet/security/bulletin/MS10-044.mspx


Q. Which TCP and UDP ports does CiscoWorks LMS 4.0 use?

A. See LMS 4.0 Port Usage for details.

Q. Does LMS 4.0 support virtual machines, such as VMware and VirtualPC?

A. Yes, LMS 4.0 supports VMware. See Server Requirements on Windows Systems, for more information.

Q. Can I install LMS 4.0 with Windows Domain Controller enabled?

A. No, you must disable Windows Domain Controller before installing LMS 4.0.

Q. Is LMS 4.0 supported on Solaris x86 (on the x86 CPU)?

A. No, LMS 4.0 is not supported on Solaris x86.

Q. Is LMS 4.0 supported on multi-homed server?

A. Yes, LMS 4.0 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 CiscoWorks LMS 4.0 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 CiscoWorks server.

Q. Can I migrate data from Solaris to Windows and vice versa?

A. No, you cannot migrate data between operating systems.

Q. I am currently using a licensed version of LMS 4.0 on Solaris. I want to migrate to Windows. Do I need to get a new license for LMS 4.0 on Windows?

A. No, you can use the same LMS 4.0 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 CiscoWorks LMS 4.0.


OL-20722-01



OL-20722-01

Installing and Migrating tOL-20722-01

A
P P E N D I X A User Inputs for Installation
This appendix provides information on the user inputs during LMS 4.0 installation.

Note For information on the Installation of LMS 4.0, see Performing New Installation of LMS 4.0.

This appendix contains:

• User Inputs for Typical Installation

• User Inputs for Custom Installation

• Password Information

A-1o CiscoWorks LAN Management Solution 4.0

Appendix A User Inputs for InstallationUser Inputs for Typical Installation

User Inputs for Typical InstallationEnter the following information while installing for the first time in Typical mode:

Enter the following information while reinstalling in Typical mode:

User Inputs for Custom InstallationEnter the following information while installing for the first time in Custom mode:

Table A-1 User Inputs for New Installation: Typical

Settings Value

Password for admin user No default values.

Enter the admin password. For more information on passwords, see Password Information.

Password for System Identity Account

No default values.

Enter the System Identity Account password. For more information on passwords, see Password Information.

Table A-2 User Inputs for Reinstallation: Typical

Settings Value

Backup folder Enter a folder for the backup data. You can also browse and select a folder.

Table A-3 User Inputs for a New Installation: Custom

Settings Value

Destination folder The default location is System drive:\Program Files\CSCOpx.

Select another location if you want to install in a specific location.

We recommend that you specify a short path for the destination folder.

Password for users admin and guest (Mandatory)

No default values. Enter the admin and guest password. For more information on passwords, see Password Information.

Password for System Identity Account (Mandatory)

No default values.

Enter the system identity account password. For more information on passwords, see Password Information.

Password for user casuser—This is for Windows only.

(Optional)

The password is generated randomly if you leave the field blank.

Password for the Common Services database. (Mandatory)

Enter the database password. For more information on passwords, see Password Information.

A-2Installing and Migrating to CiscoWorks LAN Management Solution 4.0

OL-20722-01

Appendix A User Inputs for InstallationUser Inputs for Custom Installation

Enter the following information while reinstalling in Custom mode:

Web server settings: (Mandatory)

• HTTPS port

• Administrator’s e-mail address

• SMTP server name

The default values are:

• Port number 443

• [email protected]

• localhost

Data for the Self-signed Certificate: (Mandatory)

• Country Code

• State

• City

• Organization Name

• Organization Unit Name

• Host name

• E-mail Address

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.

Table A-3 User Inputs for a New Installation: Custom (continued)

Settings Value

Table A-4 User Inputs for Reinstallation: Custom

Settings Value

Backup folder Enter a folder for the backup data. You can also browse and select a folder.

Destination folder The default location is System drive:\Program Files\CSCOpx.

We recommend that you specify a short path for the destination folder.

Password for users admin and guest

(Optional)

You may change the passwords for the admin and guest users. To keep the existing passwords, leave the fields blank.

Password for system identity account (Mandatory)

You may change the passwords for the system identity account. To keep the existing passwords, leave the fields blank.

Password for user casuser

(Optional)

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.


OL-20722-01

Appendix A User Inputs for InstallationUser Inputs for Custom Installation

Password for the Common Services Database

(Optional)

Leave the fields blank to retain the existing password.

Web server settings:

• HTTPS port

• Administrator’s e-mail address

• SMTP server name

(Optional)

You can choose to keep the existing information.

Data for the Self-signed Certificate: (Mandatory)

• Country Code

• State

• City

• Organization Name

• Organization Unit Name

• Hostname

• E-mail Address

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.

Table A-4 User Inputs for Reinstallation: Custom (continued)

Settings Value


OL-20722-01

Appendix A User Inputs for InstallationPassword Information

Password InformationThis 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 InstallationThe 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-installationThe 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:

• CiscoWorks Admin Password

• System Identity Account Password

• CiscoWorks Guest Password

• LMS Application Database Password

• Changing CiscoWorks Admin Password

• Changing casuser Password


OL-20722-01


CiscoWorks Admin Password

While entering the CiscoWorks Admin passwords, use a minimum of five characters.

System Identity Account 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 CiscoWorks LAN Management Solution 4.0 for more details on System Identity Account.

CiscoWorks Guest Password

While entering CiscoWorks Guest passwords, use a minimum of five characters.

LMS Application Database 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.

Changing CiscoWorks Admin Password

You can change your CiscoWorks Admin password by using either the CiscoWorks 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


OL-20722-01


Changing Admin Password Using Password Recovery Utility

You can change the CiscoWorks user password using the CiscoWorks user password recovery utility.

To change the user password on Solaris:

Step 1 Set the LD_LIBRARY_PATH manually. The path is to be set as follows:

setenv LD_LIBRARY_PATH /opt/CSCOpx/MDC/lib:/opt/CSCOpx/lib

This environment variable set is applicable to the current working shell only.

Now, you can change the password using the CiscoWorks user password recovery utility.

Step 2 Enter NMSROOT/bin/resetpasswd.pl username at the command prompt.

Here NMSROOT refers to the CiscoWorks Installation directory.

A message appears:

Enter new password for username:

Step 3 Enter the new password.

Step 4 Enter /etc/init.d/dmgtd start to start the Daemon Manager.

To change the user password on Windows:

Step 1 Enter NMSROOT\bin\resetpasswd.pl username at the command prompt.

A message appears:

Enter new password for username:

Step 2 Enter the new password.

Step 3 Enter net start crmdmgtd to start the Daemon Manager.

Changing Admin Password From GUI

To change the CiscoWorks admin password from the CiscoWorks server:

Step 1 Login as admin user.

Step 2 Select Admin > System > User Management > Local User Setup.

The Local User Setup page appears.

Step 3 Click Modify My Profile.

The My Profile pop-up window appears.

Step 4 Enter the password in the Password field.

Step 5 Re-enter the password in the Verify field.

Step 6 Enter the e-mail ID in the E-mail field.

Step 7 Click OK.


OL-20722-01


Changing casuser Password

You can change the casuser password using resetCasuser.exe.

To change the casuser password, do the following:

Step 1 At the command prompt, enter:

NMSROOT\setup\support\resetCasuser.exe

Three options are displayed:

1. Randomly generate the password

2. Enter the password

3. Exit.

Step 2 Enter 2, and press Enter.

A message appears, prompting you to enter the password.

Step 3 Confirm the password.

You must know the password policy. If you enter a password that does not match the password policy, the application exits with an error message.


OL-20722-01


A
P P E N D I X B 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.


• 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-1o CiscoWorks LAN Management Solution 4.0

Appendix B User Tracking UtilityUnderstanding UTU

Understanding UTUUser 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.0, 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.0Table 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 2003

• Windows 2008

• Windows XP with SP2 or SP3

• Windows Vista

Memory (RAM) 512 MB

Additional required software

• 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.0 (Network Topology, Layer 2 Services and User Tracking)

• Microsoft .Net Runtime 3.5 Service Pack 1

You can download Microsoft .Net Runtime 3.5 Service Pack 1 from http://www.microsoft.com

Network Connectivity

LMS 3.0 (Campus Manager 5.0.6) or LMS 3.1 (Campus Manager 5.1.4) or LMS 3.2 (Campus Manager 5.2.1) or LMS 4.0 (Network Topology, Layer 2 Services and User Tracking) must be running, and accessible through the network

B-2Installing and Migrating to CiscoWorks LAN Management Solution 4.0

OL-20722-01

http://www.microsoft.com

Appendix B User Tracking UtilityDownloading UTU 2.0

Downloading UTU 2.0UTU requires CiscoWorksUserTrackingUtility2.0.exe file to be downloaded and installed.

To download UTU 2.0:

Step 1 Click http://www.cisco.com/public/sw-center/index.shtml.

You must be a registered Cisco.com user to access this Software Download site. The site prompts you to enter your Cisco.com username and password in the login screen, if you have not logged in already.

Step 2 Select the Software Product Category as Network Management.

Step 3 Select Routing and Switching Management > CiscoWorks LAN Management Solution Products > CiscoWorks LAN Management Solution from the product tree.

Step 4 Select CiscoWorks LAN Management Solution 4.0.

Step 5 Select the appropriate product software type.

Step 6 Select a product release version from the Latest Releases folder and locate the software update to download.

Step 7 Locate the file CiscoWorksUserTrackingUtility2.0.zip

This zip file contains CiscoWorksUserTrackingUtility2.0.exe and setup.iss file (required for silent installation).

Step 8 Click the Download Now button to download and save the device package file to any local directory on CiscoWorks Server.

Step 9 Extract the file using any file extractor such as WinZip.

Installing UTU 2.0You can install UTU 2.0 either in normal installation mode or silent installation mode.

Before you install UTU 2.0, check whether you system meets the requirements mentioned in Hardware and Software Requirements for UTU 2.0.


• Installing UTU 2.0 in Silent Mode

• Installing UTU 2.0 in Normal Mode


OL-20722-01


Appendix B User Tracking UtilityInstalling UTU 2.0

Installing UTU 2.0 in Silent ModeTo 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 ModeTo install UTU in normal installation mode:

Step 1 Log into the system with local system administrator privileges.

Step 2 Navigate to the directory that contains CiscoWorksUserTrackingUtility2.0.exe.

Step 3 Double-click CiscoWorksUserTrackingUtility2.0.exe to begin installation.

The User Tracking Utility Welcome screen appears.

Step 4 Click Next.

A warning message appears if you have not installed .Net Framework 3.5 SP1.

You can install .Net Framework 3.5 SP1 after terminating the current UTU installation or before completing the current UTU installation.

Step 5 Click Next.

A confirmation message appears.


OL-20722-01

Appendix B User Tracking UtilityAccessing UTU 2.0

Step 6 Click Yes.

The Choose Destination Location dialog box appears. By default, UTU is installed in the directory C:\Program Files\CSCOutu2.0.

Note If you have installed .Net Framework 3.5 SP1 already on the system, the installer directs you to the Choose Destination dialog box, when you click Next in the User Tracking Utility Welcome screen.

If you click No in the confirmation message, the warning message appears again stating that you have not installed .Net Framework 3.5 SP1.

You can download and install .Net Framework 3.5 SP1. and then continue with the UTU installation.

Step 7 Click Next to install UTU in the default directory.

or

a. Click Browse to choose a different directory and click OK.

b. Click Next to continue with the installation.

The installation continues.

Step 8 Click Finish to complete the installation.

User Tracking Utility is installed at the destination location you specified and a shortcut to UTU is created on the desktop. To access the utility, see Accessing UTU 2.0.

Accessing UTU 2.0To access UTU, click either:

• Start > Programs > CiscoWorks UTU 2.0 > CiscoWorks User Tracking Utility 2.0

Or

• UTU 2.0 shortcut available on the desktop

The UTU band appears. See Figure B-1for UTU 2.0 band.

You can also find an icon in the task bar. You can use this icon to restore the UTU band when minimized.


OL-20722-01

Appendix B User Tracking UtilityConfiguring UTU 2.0

Figure B-1 User Tracking Utility - Search Band

1 - Settings Icon 2 - Minimize icon

3 - Close icon 4 - UTU task bar icon

After a system restart and during the startup, the system launches the UTU automatically.

Configuring UTU 2.0You must configure UTU to set the Campus Manager (for releases earlier than LMS 4.0), or LMS 4.0 server configurations.

To configure UTU:

Step 1 Click the Settings icon.

Or

a. Right-click the UTU search band.

A popup menu appears.

b. Click Settings.

The CiscoWorks Server Settings dialog box appears.

Step 2 Enter the name or IP Address of the server on which Campus Manager (for releases earlier than LMS 4.0), or LMS 4.0 is installed.

Step 3 Enter the port number of the CiscoWorks server.

The default HTTP port number is 1741.

You can modify the port number if required.

Step 4 Click Enable SSL for communicating with an SSL enabled server.

The port is changed to 443, which is the default port for SSL. See Figure B-2.

You can modify the port number if required.


OL-20722-01

Appendix B User Tracking UtilityConfiguring UTU 2.0

Figure B-2 Enabling SSL

Step 5 You can modify the port number if required. Enter a valid CiscoWorks Server user name and password.

This is used to verify the validity of the user when searching for users, hosts, or IP Phones.

Step 6 Confirm the password by re-entering it.

Step 7 Select the Remember me on this computer checkbox if you want the client system to remember your credentials.

The credentials are preserved only for the current user of Windows system. The credentials are not available when you log into the Windows system with a different user name.

Step 8 Click Apply to save the changes.


OL-20722-01

Appendix B User Tracking UtilitySearching for Users, Hosts or IP Phones

Searching for Users, Hosts or IP PhonesYou can use UTU Search Band to search for the users, hosts, or IP Phones in your network.

Note UTU search is case-insensitive.

To search for users, hosts, or IP Phones:

Step 1 Right-click the UTU search band.

A popup menu appears with the default search criterion Host name/IP Address selected.

Step 2 Select a search criterion from the popup menu.

You can search using:

• User name

• Host name or IP Address

• Device name or IP Address

• MAC Address

• Phone number

The default search criterion is host name or IP Address of the host.

The selected criterion is set for future searches until you change the criterion.

Step 3 Enter any value related to user name, host name, device name, IP Address, Phone number or the MAC Address in the UTU search field.

For example, you can enter 10.77.208 in the search field.

Step 4 Press Enter.

If your server is not SSL enabled, go to Step 7.

When you query for data from an SSL enabled server, the Certificate Viewer dialog box appears. See Figure B-3.


OL-20722-01


Figure B-3 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-4.


OL-20722-01


Figure B-4 Certificate Details

You can click Summary to go back to the Certificate Viewer dialog box.

Step 6 Click Yes in the Certificate Viewer dialog box or Certificate Details dialog box to accept and store the certificate.

SSL connection is established with the server.

If you click No, the certificate is not stored and no connection is established with the server.

Note 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.

Step 7 Click the X Record(s) Found button to launch the results window.

X denotes the number of matches found. See Figure 5.

For example, if there 4 matches found, the UTU Search band displays 4 Record(s) Found.


OL-20722-01


Figure 5 UTU Search Band displaying the number of matching records

UTU search returns top 500 records only if the number of matches exceed 500. You must refine your search if you want better and accurate results.

Step 8 Select an entry in the Results window.

UTU displays the search results, which is a list of user names, host names, IP Addresses, or MAC Addresses, in a Results window.

The Results window has the following options:

• Copy to Clipboard, where you can copy the selected search result record.

• Copy All to Clipboard, where you can copy all the search result records.

• Close, which you can use to close the window.

For a selected search result record, the Results window displays the details as described in:

• Table B-2 for all search criteria except Phone Number

• Table B-3 for search based on Phone Number

See Figure B-6 for IP Phone search results window.

Table B-2 Details for Each Entry in Results Window For a User or Host Search

Entry Description

User Name Name of the user logged in to the host.

MAC Address Media Access Control (MAC) address of network interface card in end-user node.

Host IP Address IP Address of the host.

Host Name Name of the host discovered by User Tracking.

Subnet Subnet to which the host belongs.

Subnet Mask Subnet mask of the host

Device name Name of the switch.

Device IP Address IP Address of the switch

VLAN VLAN to which the port of the switch belongs.

Port Port number to which the host is connected.

Port Description Description of the port number to which the host is connected.

Port State State of the port: Static or Dynamic.

Port Speed Bandwidth of the port of the switch.


OL-20722-01


Port Duplex Port Duplex configuration details on the device.

Last Seen Date and time when User Tracking last found an entry for this user or host in a switch. Last Seen is displayed in the format yyyy/mm/dd hh:mm:ss.

Table B-2 Details for Each Entry in Results Window For a User or Host Search

Entry Description

Table B-3 Details for Each Entry in Results Window For a Phone Number Search

Entry Description

Phone Number IP Phone number

MAC Address Media Access Control (MAC) address of network interface card on the phone.

Phone IP Address IP Address of the phone.

CCM Address IP Address of the Cisco Call Manager

Status Status of the phone, as known to Cisco Call Manager

Phone Type Model of the phone. Can be SP30, SP30+, 12S, 12SP, 12SPplus, 30SPplus, 30VIP, SoftPhone, or unknown.

Phone Description Description of the phone.

Device Name Name corresponding to IP Address of device.

Device IP Address IP Address of the device

Port Port number to which the phone is connected.

Port Description Description of the port to which the phone is connected.

Last Seen Date and time when User Tracking last found an entry. Last Seen is displayed in the format yyyy/mm/dd hh:mm:ss.


OL-20722-01

Appendix B User Tracking UtilityUsing Search Patterns in UTU 2.0

Figure B-6 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.0UTU searches for the users, hosts, or IP Phones which match the search criterion. See Searching for Users, Hosts or IP Phones for more information.

You can search for users, hosts, or IP Phones by entering a search pattern or substring of a search pattern.

For example, entering Cisco displays host names that start with, end with or contain Cisco for a search on host names.

You do not have to use wildcard character * to match a pattern or substring of the pattern.

To search for a MAC Address, you can use one of the following MAC Address patterns or a substring of these patterns:

• xxxx.xxxx.xxxx

• xx:xx:xx:xx:xx:xx

• xxxxxxxxxxxx

• xx-xx-xx-xx-xx-xx

Here x denotes an hexadecimal number.


OL-20722-01

Appendix B User Tracking UtilityUninstalling UTU 2.0

Uninstalling UTU 2.0Ensure that UTU is not running while uninstalling.

If you try to uninstall UTU when it is running, an error message appears and uninstallation terminates.

To uninstall UTU:

Step 1 Select Start > Programs > CiscoWorks UTU 2.0 > Uninstall CiscoWorks User Tracking Utility 2.0 from the windows task bar.

The Uninstallation wizard appears and prompts you to confirm the UTU uninstallation.

Step 2 Click Yes.

The Uninstallation continues.

Step 3 Click Finish to exit the uninstallation wizard.

Upgrading to UTU 2.0You can install UTU 2.0 on the same system where UTU 1.1.1 is installed.

You can choose to install UTU 2.0 on any directory other than the directory where UTU 1.1.1 is installed.

See Installing UTU 2.0 for installation instructions.

Re-installing UTU 2.0Re-installation of UTU 2.0 is supported on the normal mode of installation.

In the normal mode of installation, you are prompted with a confirmation message whether you want to continue the installation. You must provide your inputs to continue the installation.

See Installing UTU 2.0 for installation instructions.

The user profiles that are created already are not be lost during re-installation.


OL-20722-01


A
P P E N D I X C Installing the Remote Syslog Collector
This appendix provides general information on how to install the Remote Syslog Collector on a remote Windows or UNIX system to process syslog messages.

The Remote Syslog Collector filters the Syslog messages before forwarding them to the Analyzer process on the LMS server.

Warning Do not install Remote Syslog Collector on a system that has LMS 4.0 already installed.

The Remote Syslog Collector and Syslog Analyzer Service on the LMS server uses SSL sockets to communicate with each other.

It functions as follows:

1. At startup, the Remote Syslog Collector looks for Syslog Analyzers already subscribed on the LMS Server and requests for the latest filter definitions.

• If the Syslog Analyzer is not reachable when queried, the Remote Syslog Collector logs all emblem compliant syslogs in the specified downtime file after filtering.

The Syslog Collector Properties file is available at these locations:

– On Solaris:

NMSROOT/MDC/tomcat/webapps/rme/WEB-INF/classes/com/cisco/nm/rmeng/csc/data/Collector.properties

– On Windows:

NMSROOT\MDC\tomcat\webapps\rme\WEB-INF\classes\com\cisco\nm\rmeng\csc\data\Collector.properties

• If the Syslog Analyzer responds with the latest filters, the Remote Syslog Collector applies filters and forwards syslogs to the Syslog Analyzer.

2. At startup, the Syslog Analyzer tries to connect to all the subscribed Remote Syslog Collectors by passing the latest filters.

To subscribe or unsubscribe from a Remote Syslog Collector, select Admin > Collection Settings > Syslog > Syslog Collector Status from the menu.

After the Remote Syslog Collector connects to the LMS 4.0 Server, the Remote Syslog Collector entry is added to the Collector Status window of the LMS 4.0 Server.

To view the status of the subscribed Syslog Collector, select Admin > Collection Settings > Syslog > Syslog Collector Status.

C-1o CiscoWorks LAN Management Solution 4.0

Appendix C Installing the Remote Syslog CollectorVerifying Remote Syslog Collector Server Requirement

This section describes how to set up Syslog between RSAC and LMS 4.0. This involves:

• Verifying Remote Syslog Collector Server Requirement

• Installing the Remote Syslog Collector

• Stopping the Remote Syslog Collector

• Uninstalling the Remote Syslog Collector

Verifying Remote Syslog Collector Server RequirementThe following section lists the necessary server requirements for Remote Syslog Collector:

• Table C-1 provides the server requirements for Remote Syslog Collector on Solaris.

• Table C-2 provides the server requirements for Remote Syslog Collector on Windows.

Table C-1 Remote Syslog Collector Server Minimum Requirements on Solaris


Hardware UltraSPARC CPU

Memory (RAM) • 4 GB RAM and 8 GB Swap space.

Operating System • Solaris 10

Browser

(You need a browser only if you download the RSAC installation files from the LMS 4.0 server.)

Not Supported

Table C-2 Remote Syslog Collector Server Minimum Requirements on Windows


Hardware IBM PC-compatible system with 1 GHz or faster Pentium processor, and 1 GB memory.

Memory (RAM) 2 GB RAM memory requirement with a Swap space of 4 GB.

Operating System LMS 4.0 supports the following Windows systems:

• Windows 2003 Standard Edition (SP2)

• Windows 2003 Enterprise Edition (SP2)

• Windows 2003 Standard Edition R2 (SP2)

• Windows 2003 Enterprise Edition R2 (SP2)

• Windows 2008 Server Standard and Enterprise Editions with Service Pack 1 and 2

Browser

(You need a browser only if you download the Remote Syslog Collector installation files from the LMS 4.0 server.)

• Internet Explorer 7.x (except on Windows 7)

• Internet Explorer 8.x

• Firefox 3.6.x for Windows

C-2Installing and Migrating to CiscoWorks LAN Management Solution 4.0

OL-20722-01

Appendix C Installing the Remote Syslog CollectorInstalling the Remote Syslog Collector

The following Virtualization systems are supported:

• VMware ESX server 3.0.x

• VMware ESX Server 3.5.x

• VMWare ESX 4.0.x

• VMWare ESX 4.1

• VMWare ESXi 4.0

• Hyper V Virtualization

RSAC 5.0 works only with LMS 4.0.

You must uninstall the previous version of RSAC before installing the new RSAC which is provided with LMS 4.0 DVD. To install RSAC 4.4, see Installing the Remote Syslog Collector.

Installing the Remote Syslog CollectorPerform the following to install the Remote Syslog Collector on both platforms.

• Installing on Solaris

• Installing on Windows

Prerequisites for installing a Remote Syslog Collector:

• LMS 4.0 and RSAC 5.0 should be installed.

• If you install Common Services Service Pack on the CiscoWorks server, you must install the same Service Pack on the RSAC server.

The Common Services Service Pack versions must be same in the CiscoWorks Server and RSAC Server.

• LMS 4.0 should not be installed on the server where you need to install the Remote Syslog Collector. (If LMS 4.0 is installed, the Syslog Collector is installed by default).

This section also contains:

• Subscribing to a Remote Syslog Collector

• Starting the Remote Syslog Collector

• Stopping the Remote Syslog Collector

• Uninstalling the Remote Syslog Collector


OL-20722-01


Installing on SolarisTo install the Remote Syslog Collector on a Solaris system:

Step 1 Mount the LMS 4.0 DVD.

The RSAC installables are available in the RSAC directory on LMS 4.0 DVD.

Step 2 Enter the following to start the installation:

# cd RSAC

# ./setup.sh

Step 3 Follow the wizard instructions to install the product.

After the installation of Remote Syslog Collector, select Admin > System > Software Center > Software Update to verify the installation. Remote Syslog Collector should be listed.

After Installation, you need to configure the collector.properties file if required. If not, you can use the defaults. See Understanding the Syslog Collector Properties File.

Installing on Windows To install the Remote Syslog Collector on a Windows system:

Step 1 Navigate to the RSAC folder on the LMS 4.0 DVD.

Step 2 Double-click the Setup.exe file to start the installation.

Step 3 Follow the wizard instructions to install the product.

After the installation of Remote Syslog Collector, select Admin > System > Software Center > Software Update to verify the installation. Remote Syslog Collector should be listed.

After Installation, you need to configure the collector.properties file if required. If not, you can use the defaults. See Understanding the Syslog Collector Properties File.


OL-20722-01


Subscribing to a Remote Syslog Collector

Step 1 Download the Peer certificate from the system where Remote Syslog Collector is running.

Step 2 Upload the Peer certificate to the system where Remote Syslog Collector is running.

Step 3 Select Admin > Collection Settings > Syslog > Syslog Collector Status.

The Collector Status dialog box appears with this information:

Step 4 Click Subscribe.

The Subscribe Collector dialog box appears.

Step 5 Enter the address of the Common Syslog Collector to which you want to subscribe to.

Step 6 Click OK.

The Syslog Analyzer is subscribed the Syslog Collector that you specified. This can be either the Syslog Collector on the LMS server, or a remotely installed Syslog Collector.

Column Description

Name Hostname or the IP address of the host on which the Collector is installed.

Update Time Date and time of the last update. By default, this dialog box is updated every 5 minutes.

Time and time zone are those of the CiscoWorks Server.

Uptime Time duration for which the Syslog Collector has been up.

Forwarded Number of forwarded Syslog messages.

Dropped Number of unprocessed Syslog messages.

Invalid Number of invalid Syslog messages.

Filtered Number of filtered messages. Filters are defined with the Define Message Filter option (select Admin > Network > Notification and Action Settings > Syslog Message Filters from the menu). For details about defining filters, see Administration of CiscoWorks LAN Management Solution 4.0.

Received Number of Syslog messages received.

Test Collector Subscription

Click to test a Syslog collector that’s already subscribed or that’s going to be subscribed.

Subscribe Click to subscribe a Syslog collector.

Unsubscribe Select the Syslog collector and click Unsubscribe to unsubscribe the Syslog collector.


OL-20722-01


Starting the Remote Syslog CollectorTo start the Remote Syslog Collector, enter pdexec SyslogCollector at the command prompt on the machine where Syslog Collector is installed. It starts by default.

Stopping the Remote Syslog CollectorTo stop the Remote Syslog Collector, enter pdterm SyslogCollector at the command prompt on the machine where Syslog Collector is installed.

Uninstalling the Remote Syslog CollectorPerform the following to uninstall RSAC:

• Uninstallation on Windows

• Uninstallation on Solaris

Uninstallation on Windows

To uninstall on a Windows system:

Step 1 Select Start > Programs > CiscoWorks > Uninstall CiscoWorks.

The Uninstallation dialog box appears, displaying all of the installed components.

Step 2 Select Remote Syslog Collector.

Step 3 Click Next to begin uninstalling the selected component.


OL-20722-01

Appendix C Installing the Remote Syslog CollectorUnderstanding the Syslog Collector Properties File

Uninstallation on Solaris

To uninstall on a Solaris system:

Step 1 Enter these commands as root to start the uninstall program:

# cd /

# NMSROOT/bin/uninstall.sh

A message similar to the following appears at command prompt:

1) CiscoView 6.1.9

2) Integration Utility 1.9

3) CiscoWorks Common Services 3.3

4) Remote Syslog Collector 4.3

5) All of the above

Select one or more of the items using its number separated by comma or enter q to quit [q]

Step 2 Enter 4 and press Return.

Step 3 Follow the prompts from the uninstallation wizard.

Understanding the Syslog Collector Properties FileAfter installing the Syslog Collector on a remote machine, you need to check the Syslog Collector Properties file to ensure that the Collector is configured properly.

The Syslog Collector Properties file is available at these locations:

• On Solaris:

NMSROOT/MDC/tomcat/webapps/rme/WEB-INF/classes/com/cisco/nm/rmeng/csc/data/Collector.properties

• On Windows:

NMSROOT\MDC\tomcat\webapps\rme\WEB-INF\classes\com\cisco\nm\rmeng\csc\data\Collector.properties


OL-20722-01


The following table describes the Syslog Collector Properties file:

Timezone-Related Properties Description

TIMEZONE The timezone of the machine where the Syslog Collector is running. Enter the correct abbreviation for the timezone. For example, the time zone for India is IST.

For the correct Timezone abbreviation, see the Timezone file in the following locations:

• On Solaris:

/opt/CSCOpx/MDC/tomcat/webapps/rme/WEB-INF/classes/com/cisco/nm/rmeng/fcss/data/TimeZone.lst

• On Windows:

NMSROOT\MDC\tomcat\webapps\rme\WEB-INF\classes\com\cisco\nm\rmeng\fcss\data\TimeZone.lst

COUNTRY_CODE Country code for the Syslog Collector.

We recommend that you set the country code variable with the appropriate country code, to make sure that the Syslog timestamp conversion works correctly.

For example, if you are in Singapore, you must set the country code variable as COUNTRY=SGP.

TIMEZONE_FILE The path of the Timezone file. This file contains the offsets for the time zones.

After installing the Syslog Collector, ensure that the offset specified in this file is as expected. If it is not present or is incorrect, you can add the Timezone offset according to the convention.

The default paths are:

• On Solaris:

opt/CSCOpx/MDC/tomcat/webapps/rme/WEB-INF/classes/com/cisco/nm/rmeng/fcss/data/TimeZone.lst

• On Windows:

NMSROOT\MDC\tomcat\webapps\rme\WEB-INF\classes\com\cisco\nm\rmeng\fcss\data\TimeZone.lst


OL-20722-01


General Properties

SYSLOG_FILES Filename and location of the file from which syslog messages are read.

• On Solaris:

/var/log/syslog_info

• On Windows:

NMSROOT\log\syslog.log

DEBUG_CATEGORY_NAME

Name Syslog Collector uses for printed ERROR or DEBUG messages.

The default category name is SyslogCollector.

We recommend that you do not change the default value.

DEBUG_FILE Filename and location of the Syslog Collector log file containing debug information:

• On Solaris:

/var/adm/CSCOpx/log/CollectorDebug.log

• On Windows:

NMSROOT\log\CollectorDebug.log

DEBUG_LEVEL Debug levels in which you run the Syslog Collector.

We recommend that you retain the default INFO, which reports informational messages. Setting it to any other value might result in a large number of debug messages being reported.

If you change the debug level, you must restart the Syslog Collector.

The values for the Debug levels are:

• Warning

• Debug

• Error

• Information

DEBUG_MAX_FILE_SIZE

The maximum size of the log file containing the debug information.

The default is set to 5 MB.

If the file size exceeds the limit that you have set, Syslog Collector writes to another file, based on the number of backup files that you have specified for the DEBUG_MAX_BACKUPS property.

For example, if you have specified the number of backups as 2, besides the current log file, there will be two backup files, each 5MB in size. When the current file exceeds the 5 MB limit, Syslog Collector overwrites the oldest of the two backup files.

DEBUG_MAX_BACKUPS

The number of backup files that you require. The size of these will be the value that you have specified for the DEBUG_MAX_FILE_SIZE property.



OL-20722-01


Miscellaneous Properties

READ_INTERVAL_IN_SECS

The interval at which the Collector polls the syslog file.

The default is set to 1 second.

QUEUE_CAPACITY The size of the internal buffer, for queuing syslog messages.

The default is set to 100000.

PARSER_FILE The file that contains the list of parsers used while parsing syslog messages.

• On Solaris:

opt/CSCOpx/MDC/tomcat/webapps/rme/WEB-INF/classes/com/cisco/nm/rmeng/fcss/data/FormatParsers.lst

• On Windows:

NMSROOT\MDC\tomcat\webapps\rme\WEB-INF\classes\com\cisco\nm\rmeng\fcss\data\FormatParsers.lst

SUBSCRIPTION_DATA_FILE

The Syslog Collector data file that contains the information about the Syslog Analyzers that are subscribed to the Collector.

• On Solaris:

opt/CSCOpx/MDC/tomcat/webapps/rme/WEB-INF/classes/com/cisco/nm/rmeng/csc/data/Subscribers.dat

• On Windows:

NMSROOT\MDC\tomcat\webapps\rme\WEB-INF\classes\com\cisco\nm\rmeng\csc\data\Subscribers.dat

FILTER_THREADS The number of threads that operate at a time for filtering syslog messages. The default is set to 1.

COLLECTOR_PORT The default port of the Syslog Collector. The default is set to 4444.

The port where the collector listens for registration requests from Syslog Analyzers.



OL-20722-01


A
P P E N D I X D Syntax and Usage for Backup Script
You can take a manual backup using the following syntax:

You can take selective backup using the following syntax:

The following table lists the explanation for the syntax:

LMS 2.6/LMS 2.6 SP 1LMS 3.0/LMS 3.0 December 2007 Update/LMS 3.1/LMS 3.2

Syntax wrapper.pl backup.pl

On Solaris

NMSROOT/bin/perl dir1/wrapper.pl BKP Logfile

NMSROOT/bin/perl NMSROOT/bin/backup.pl BKP [Logfile] [Num_Generations]

On Windows

NMSROOT\bin\perl dir1\wrapper.pl BKP Logfile

NMSROOT\bin\perl NMSROOT\bin\backup.pl BKP [Logfile] [Num_Generations]

LMS 4.0

Syntax backup.pl

On Solaris/opt/CSCOpx/bin/perl /opt/CSCOpx/bin/backup.pl -dest=BackupDirectory -system [-log=LogFile] [-gen=Num_Generations]

On WindowsNMSROOT\bin\perl NMSROOT\bin\backup.pl -dest=BackupDirectory -system [-log=LogFile] [-gen=Num_Generations]

Syntax Explanation

NMSROOT Common Services installation directory (by default, /opt/CSCOpx for Solaris, and C:\Program Files\CSCOpx for Windows, where C: is the System Drive)

dir1 Directory where you have extracted wrapper.pl

BKP Backup directory where you have backed up data using wrapper.pl or backup.pl

D-1o CiscoWorks LAN Management Solution 4.0

Appendix D Syntax and Usage for Backup Script

Example 1

To back up LMS 2.6 or LMS 2.6 SP1 data in the backup directory, enter:

• On Solaris:

opt/CSCOpx/bin/perl /wrapper/wrapper.pl /backup

• On Windows:

C:\Progra~1\CSCOpx\bin\perl C:\wrapper\wrapper.pl C:\backup

Example 2

To back up LMS 3.0 or LMS 3.0 December 2007 Update data in the backup directory, enter:

• On Solaris:

opt/CSCOpx/bin/perl /opt/CSCOpx/bin/backup.pl /backup

• On Windows:

C:\Progra~1\CSCOpx\bin\perl C:\Progra~1\CSCOpx\bin\backup.pl C:\backup

Example 3

To specify a different location for the log file during a manual backup of LMS 2.6 or LMS 2.6 SP1, enter:

• On Solaris:

NMSROOT/bin/perl dir1/wrapper.pl BKP backup/log/dbbackup.log

• On Windows:

NMSROOT\bin\perl dir1\wrapper.pl BKP C:\backup\log\dbbackup.log

Logfile Log file name that contains the details of the backup. The default location of the backup log file (dbbackup.log) is:

• NMSROOT\CSCOpx\log\ (On Windows)

• /var/adm/CSCOpx/log/ (On Solaris)

BackupDirectory Directory that you want to be your Backup directory.

Num_Generations Maximum backup generations to be kept in the backup directory.

Syntax Explanation

D-2Installing and Migrating to CiscoWorks LAN Management Solution 4.0

OL-20722-01


A
P P E N D I X E Syntax and Usage for Restore Script
You can use the restorebackup.pl script to restore the LMS data you have backed up.

For a successful restoration of backed up data, ensure that all services and processes are up and running. Stop the daemons and then run restorebackup.pl.

Note Cross platform restore is not supported. That is, you cannot restore data from a Solaris installation of LMS to a Windows installation and vice-versa.

The syntax for restorebackup.pl is as follows:

• Solaris

NMSROOT/bin/perl NMSROOT/bin/restorebackup.pl -d BKP [-t temporary_directory] [-h] [-gen generationNumber]

• Windows

NMSROOT\bin\perl NMSROOT\bin\restorebackup.pl -d BKP [-t temporary_directory] [-h] [-gen generationNumber]

The following table lists the explanation for the syntax:

Syntax Explanation

NMSROOT—(Required) Common Services installation directory (by default, /opt/CSCOpx in Solaris, and C:\Program Files\CSCOpx in Windows where C: is the System Drive)

-t temporary_directory—(Optional) This is the directory or folder used by the restore program to store its temporary files. By default this directory is NMSROOT/tempBackupData. You can customize this by specifying your own temporary directory to avoid overloading NMSROOT

-gen generationNumber—(Optional) This is the generation number. -gen now is the latest generation. If generations 1 through 5 exist, then 5 is the latest.

-d BKP—(Required) This is the absolute directory or folder used by the restore program to store the backup.

-h—(Optional) Displays help. When used with -d BackupDirectory, show s correct syntax along with available suites and generations

E-1o CiscoWorks LAN Management Solution 4.0

Appendix E Syntax and Usage for Restore Script

Examples

To restore... Enter this command in Solaris Enter this command in Windows

The latest version of data

opt/CSCOpx/bin/perl opt/CSCOpx/bin/restorebackup.pl -d BKP -gen now

C:\Progra~1\CSCOpx\bin\perl C:\Progra~1\CSCOpx\bin\restorebackup.pl -d BKP -gen now

The 12th generation of data

opt/CSCOpx/bin/perl opt/CSCOpx/bin/restorebackup.pl -d BKP -gen 12

C:\Progra~1\CSCOpx\bin\perl C:\Progra~1\CSCOpx\bin\restorebackup.pl -d BKP -gen 12

Data from the forced auto backup during the CS upgrade process

opt/CSCOpx/bin/perl opt/CSCOpx/bin/restorebackup.pl -d DB_BKP1/automaticbackup/cmfbackup -gen now

1. DB_BKP is the backup directory created by the user.

C:\Progra~1\CSCOpx\bin\perl C:\Progra~1\CSCOpx\bin\restorebackup.pl -d DB_BKP\automaticbackup\cmfbackup -gen now

E-2Installing and Migrating to CiscoWorks LAN Management Solution 4.0

OL-20722-01


I N D E X

A

accessing LMS server 6-20

application scaling numbers 3-18

B

before installation 3-3

C

cautions, significance of i-xviii

cautions regarding

daemon manager, starting and stopping 8-2

link to installation directory, removing 6-7

CiscoWorks LMS 4.0

install and upgrade behavior 1-2

processes 6-19

product overview 1-1

concurrent users 3-21

configuring SNMP Traps 7-19

D

database password rules A-6

data migration

Inventory, Config and Image Management 8-17

normal backup 7-2

overview 1-14

scope 7-2

selective backup 7-2

debugging CAM 8-16

device credentials, required 2-19

device package updates 1-18

device states 1-9

disabling FIPS 2-12

E

enabling FIPS 2-12

evaluation mode 3-12

F

FIPS, enabling/disabling 2-12

G

guest password rules A-6

H

high availability, setting up

on Windows 4-5

overview 4-1

system requirements 4-5

Veritas components 4-4

I

install, preparing to 3-1

install and upgrade

master-slave server setup, upgrading 1-3

upgrade and migration 1-4

installation

new installations

IN-1ating to CiscoWorks LAN Management Solution 4.0

Index

password rules for A-6

notes

general 3-3

Solaris 3-4

Windows 3-5

prerequisites 2-1

reinstallations

password rules for A-5

terms and definitions 3-1

user inputs for

custom installations A-2

typical installations A-2

installation terms

Admin password 3-2

Application database password 3-1

Cisco.com user ID and password 3-2

Guest password 3-2

installation terms overview

Self signed certificate 3-2

SMTP Server 3-2

System Identity Account password 3-2

installing RSAC (see RSAC) C-1

Integration Utility

supported NMS 1-15

L

license file 3-11

license file, installing 3-16

license information 3-7

licensing LMS 4.0

evaluation license 3-12

license file 3-11

NFR license 3-15

product ordering and PAK 3-6

LMS

AAA Methods 7-20

before uninstalling 6-23

concurrent users 3-21

IN-2Installing and Migrating to CiscoWorks LAN Management Solution

license information 3-7

new installation 6-2

prerequisites 2-1

reinstallation 6-25

uninstallation

Solaris 6-23

Windows 6-24

uninstalling 6-23

log files 7-14

logging into LMS 6-22

M

messages, installation 8-3

migration errors, troubleshooting

Common Services 8-16

Device Performance Management 8-22

Fault Management 8-20

IPSLA Performance Management 8-21

Network Topology, Layer 2 Services and User Tracking 8-18

migration scope

CiscoView 7-11

Common Services 7-3

Device Performance Management 7-11

Fault Management 7-9

Inventory, Config and Image Management 7-6

IPSLA Performance Management 7-10

Network Topology, Layer 2 Services and User Tracking 7-5

Portal 7-12

N

new features

Auto Smartports 1-11

Dashboards 1-7

EnergyWise 1-10

Event Monitor 1-13

4.0OL-20722-01

Index

Fault Monitor 1-12

Getting Started 1-6

Identity 1-11

Local Role-based Access Control 1-8

navigating menus 1-6

Report Center 1-13

Search and Fault Bar 1-8

Smart Install 1-12

Template Center 1-8

third-party software and tool changes 1-14

troubleshooting workflow 1-13

Unified Device Manager 1-9

Unified Grouping Services 1-9

VRF-Lite support for Catalyst 3000 and 4000 1-14

Work Centers 1-7

new installation

silent mode 6-15

Solaris 6-3

custom 6-7

typical 6-5

verifying installation 6-18

Windows 6-10

custom 6-13

typical 6-12

NFR license 3-15

O

ordering product

Base Media Kit and Digital PAK 3-7

Digital PAK for Eval Software 3-7

Product DVD with Printed PAK 3-6

P

PAK 3-6

password information

admin password A-6

Installing OL-20722-01

database password A-6

Guest password rules A-6

new installation rules A-6

upgrade and reinstallation rules A-5

port usage 2-15

post-upgrade activities, CS 7-20

processors, supported

Solaris 2-8

Windows 2-9

R

required device credentials 2-19

RSAC (Remote Syslog Analyzer Collector)

Common Syslog Collector, subscribing to C-5

installing C-1

Remote Syslog Collector C-3

Syslog Analyzer Collector C-3

uninstalling RSAC C-6

properties file C-7

COLLECTOR_PORT C-10

COUNTRY_CODE C-8

DEBUG_CATEGORY_NAME C-9

DEBUG_FILES C-9

DEBUG_LEVEL C-9

DEBUG_MAX_BACKUPS C-9

DEBUG_MAX_FILE_SIZE C-9

FILTER_THREADS C-10

PARSER_FILE C-10

QUEUE_CAPACITY C-10

READ_INTERVAL_IN_SECS C-10

SUBSCRIPTION_DATA_FILES C-10

SYSLOG_FILES C-9

TIMEZONE C-8

TIMEZONE_FILE C-8

server requirements, verifying C-2

stopping C-6

uninstalling C-6

upgrading C-3

IN-3and Migrating to CiscoWorks LAN Management Solution 4.0

Index

S

scaling numbers 3-18

scope of data migration 7-2

selftest tool 8-16

Server 2-7, 2-8, 2-10

Solaris patches

cluster patches 2-14

required and recommended 2-13

stopping RSAC C-6

supported devices 1-17

supported Network Management Systems 1-15

system and browser requirements

disk space 2-2

on client systems 2-11

operating system 2-3

server requirements

on Solaris 2-7

on Virtualization Systems 2-10

on Windows 2-8

Storage Area Network 2-7

T

terminal server support

about Terminal Services 2-11

enabling or disabling Terminal Services

on Windows 2003 2-12

on Windows 2008 2-12

troubleshooting installation

messages, understanding 8-3

process status, viewing and changing 8-1

U

UCS support 2-10

uninstalling LMS 4.0

before you begin 6-23

on Solaris 6-23

IN-4Installing and Migrating to CiscoWorks LAN Management Solution

on Windows 6-24

uninstalling RSAC C-6

upgrading LMS

remote upgrade on Solaris 6-17

remote upgrade on Windows 6-18

upgrading RSAC C-3

UTU

access B-5

configure B-6

download B-3

install B-3

requirements B-2

search patterns B-13

uninstall B-14

upgrade B-14

users, hosts or IP phones search B-6

4.0OL-20722-01

lmsig40

Documents

Transcript of lmsig40