Table Of Contents

Overview of LAN Management Solution 3.1

Product Overview

Composition of LAN Management Solution 3.1

Key Features of LMS 3.1

Install and Upgrade Behavior

Support for New Server and Client Operating Environments

Support for New Hardware in LMS 3.1

Removal and Upgrade of Third Party Components

Auto Allocation of Devices to Applications

Enhancements to Report Jobs

Enhancements to Job Settings in Reports

Support for Zone-based Virtualization in Solaris 10

Support for ZFS File System

Support for LDom Virtualization

Supported Network Management Systems

Supported Devices

Overview of LAN Management Solution 3.1

---

This chapter provides a clear overview of CiscoWorks LAN Management Solution 3.1 and describes the composition of LAN Management Solution 3.1 on both Windows and Solaris systems.

This chapter contains:

•Product Overview

•Composition of LAN Management Solution 3.1

•Key Features of LMS 3.1

•Supported Network Management Systems

•Supported Devices

Product Overview

The LAN Management Solution (LMS) 3.1 software provides applications for configuring, administering, monitoring, and troubleshooting a campus network. It enables network administrators to effectively manage their LAN and Campus networks.

This document describes the procedure for a new and upgrade installation of LMS 3.1. It contains:

•LMS product composition, including links for accessing online documentation.

•LMS features.

•Hardware and software requirements.

•Detailed installation procedures for all applications.

•Information on getting started with LMS.

•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 3.1, follow the procedure in the Data Migration Guide for LAN Management Solution 3.1.

You can find this document at this URL:

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

The licenses in LMS 3.1 are device-based for all applications. However, for Internetwork Performance Monitor (IPM) the license is based on the number of devices and the number of collectors.

Based on the requirement, you can select the appropriate license. See License Information for further information.

Composition of LAN Management Solution 3.1

The LAN Management Solution 3.1 software is packaged in a DVD for your use. Figure 1-1 explains the composition of LAN Management Solution 3.1 software.

Figure 1-1 Composition of LAN Management Solution 3.1

The entire list of applications comprised within LAN Management Solution 3.1 has been tabulated below.

You can select to upgrade install any number of applications based on your need and the system prerequisites. However, CiscoWorks Common Services 3.2, CiscoWorks Assistant 1.1 and CiscoWorks LMS Portal 1.1 will be selected and installed by default.

Table 1-1 describes the composition of applications within LAN Management Solution 3.1.

Table 1-1 Composition of Applications within LAN Management Solution 3.1  

This LMS 3.1 Application...	Provides...
CiscoWorks Common Services 3.2 (CS)	Common software and services for LMS applications. Common Services provides a set of shared application services that are used by all LMS applications.
Resource Manager Essentials 4.2 (RME)	The ability to manage: •Device inventory and audit changes. •Configuration files, software images, and syslog analysis. •Network monitoring and fault information for tracking devices that are critical to network uptime.
Campus Manager 5.1 (CM) Campus Manager is sometimes referred to as Campus.	The following functions: •Visualize network topology. •Locate and display data about users and hosts in the network. •Manage VLANs. •Detect network discrepancies and Best Practice Deviations
CiscoView 6.1.8 (CV)	The ability to monitor and troubleshoot devices across your network being a graphical device management tool.
Device Fault Manager 3.1 (DFM)	The following functions: •Monitor device faults in real-time, and determine the root cause by correlating device-level fault conditions. •Monitor fault history. •Configure e-mail, SNMP trap, and syslog notifications.
Internetwork Performance Monitor 4.1 (IPM)	The ability to pro-actively troubleshoot network response time, jitter, and availability.
CiscoWorks LMS Portal 1.1	The ability to: •Customize information, based on the applications installed. •View frequently used information in a common place. With this you do not need to navigate through many pages. •Display application-related information as portlets. •Customize home page to have all information on a single screen from all the installed applications.
CiscoWorks Assistant 1.1	Workflows to: •Set up and manage CiscoWorks LAN Management Solution (LMS) servers. •Collect troubleshooting information.
CiscoWorks Health and Utilization Monitor 1.1	Monitors the device for performance parameters, report violations based on the threshold values configured, and provides extensive reporting.
Integration Utility 1.8 (NMIM)	Support for third-party Network Management Systems (NMS). This is an integration module.

Key Features of LMS 3.1

The following are the key features of LMS 3.1:

•Install and Upgrade Behavior

•Support for New Server and Client Operating Environments

•Support for New Hardware in LMS 3.1

•Removal and Upgrade of Third Party Components

•Auto Allocation of Devices to Applications

•Enhancements to Report Jobs

•Enhancements to Job Settings in Reports

•Support for Zone-based Virtualization in Solaris 10

•Support for ZFS File System

•Support for LDom Virtualization

•Supported Network Management Systems

See the respective application User Guides to know about the key features of all LMS applications.

Install and Upgrade Behavior

LMS 3.1 provides a single install experience to you. It allows you to select and install all applications together or select specific applications.

The complete installation is managed by this single installer. It captures all required user inputs and then installs the applications.

The evaluation version of HUM 1.1 is packaged with LMS3.1, and is a part of the single installer. Since HUM has a separate license, during installation, you are prompted to first enter the license information for LMS3.1 and then for HUM 1.1.

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

This section contains the following topics:

•Upgrade and Migration Overview

•Upgrading Master-Slave Server Setup

Upgrade and Migration Overview

Upgrading is overwriting the existing LMS version with the new LMS version. LMS 3.1 enables you to upgrade from an earlier version of LMS and perform a fresh installation of other applications at the same time.

When you install LMS 3.1, the existing applications of LMS are selected by default for upgrading to the latest version of LMS 3.1.

For example, if you had installed Resource Manager Essentials 4.0.5 (LMS 2.6) previously, and when you now install LMS 3.1 using the DVD, this application will be selected by default for an upgrade installation to Resource Manager Essentials 4.2 (LMS 3.1).

The three default applications namely, CiscoWorks Common Services 3.2, CiscoWorks Assistant 1.1 and CiscoWorks LMS Portal 1.1, will also be selected.

The other applications you want to install can also be simultaneously selected for a fresh installation, using the LMS 3.1 DVD.

You can upgrade using either of these methods:

•Local upgrade—Upgrading to the newer version of LMS on the same machine.

You can locally upgrade to LMS 3.1 from LMS 3.0, LMS 3.0 December 2007 update, LMS 2.6 and LMS 2.6 Service Pack (SP) 1.

•Remote upgrade—Installing LMS on a different machine and then restoring the data on that machine.

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

Upgrading Master-Slave Server Setup

The Master server should be first upgraded to the latest version of LMS. Then the Slave server should be upgraded.

You can upgrade only if the Master server has a higher version of LMS (for example, LMS 3.1) and the Slave server has a lower version of LMS (for example, LMS 3.0.)

You cannot upgrade if the Master server has a lower version of LMS (for example, LMS 3.0 and the Slave server has a higher version of LMS (for example, LMS 3.1).

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

Table 1-2 Upgrade and Data Migration Procedure 

Current LMS Version	Type of Upgrade	Procedure
LMS 3.0, LMS 3.0 December 2007 update, LMS 2.6, LMS 2.6 Service Pack 1.	Local Upgrade	Upgrade to LMS 3.1 using the LMS 3.1 DVD. For details on the upgrade procedures, see the Upgrading to LMS 3.1. Data from the older version of LMS is automatically migrated into LMS 3.1 from LMS 3.0 onwards. For upgrades from LMS 2.6 / LMS 2.6 SP1, all data gets migrated to LMS 3.1 except IPM. To migrate IPM data, follow the instructions in the Data Migration Guide for LAN Management Solution 3.1.
LMS 2.6, LMS 2.6 SP1, LMS 3.0, LMS 3.0 December 2007 update	Remote Upgrade	1. Back up the data in the old machine. 2. Install LMS 3.1 in the new machine. 3. Migrate your data to LMS 3.1 using the instructions in the Data Migration Guide for LAN Management Solution 3.1.
LMS 2.2, LMS 2.5, LMS 2.5.1	Direct upgrade to LMS 3.1 is not supported. The suggested upgrade path is: LMS 2.2 / LMS 2.5 / LMS 2.5.1 > LMS 2.6 > LMS 3.1	1. Back up the data. 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 3. For remote upgrade from LMS 2.6, backup data for all the applications. For local upgrade from LMS 2.6, backup only the IPM data. 4. Upgrade from LMS 2.6 to LMS 3.1. 5. Migrate data using the instructions in the Data Migration Guide for LAN Management Solution 3.1.

Support for New Server and Client Operating Environments

Support for the following has been added in LMS 3.1:

New Server Operating Systems supported in LMS 3.1

Solaris 10, 10/08 release

Solaris 10, 05/08 release

New Virtualization System supported in LMS 3.1

•VMware ESX 3.5.x

•VMware ESXi 3.5 Update 2

•Zone based Virtualization in Solaris 10

•Logical domains (LDoms) in Solaris 10

New Operating Environment supported in LMS 3.1

ZFS file System for Solaris 10 Operating System

---

Note See Prerequisites for detailed information on other supported Server and Client Operating environments in LMS 3.1.

---

Support for New Hardware in LMS 3.1

The new hardware supported in LMS 3.1 is:

•UltraSPARC T2 processor

•UltraSPARC T2+ processor

•SPARC64 VI processor

•VMWare Optimized hardware

–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

–AMD-V

Removal and Upgrade of Third Party Components

The following third party components are removed and replaced with open source components in LMS 3.1:

•Visigenics that was used for CORBA communication is replaced with JACORB.

•Tibco that was used for event services is replaced with ActiveMQ

The following component upgrade is performed in LMS3.1:

•Itools framework (Installation framework) that was scripted using Installshield 5.5 is migrated to Installshield 2008 premier version.

•Sybase ASA version is upgraded to 10.0.1 from 9.x. because 10.x has better performance.

Auto Allocation of Devices to Applications

In the previous versions of LMS, device allocation is done either in the auto or manual mode, except in Campus Manager that has filter support.

The new feature Auto Device Allocation helps you to define rules and policies and automatically allocate the devices based on the rules into various LMS applications.

Groups (System created and User-defined groups) created in Common Services are used for this purpose. Application specific groups are not be used for this.

To set up the Auto Allocation feature:

---

Step 1 Create groups using Common Services Group Administration page using fields like sysLocation, ip-address range etc.

Step 2 Go to each application Auto Allocation settings page and select the appropriate mode.

Step 3 Add devices in DCR via Discovery, Import or Manual addition.

If the devices are already present in DCR, this step is not required.

---

The Auto Allocation feature can be enabled from the following menu paths in these applications:

•Campus Manager > Admin > Data Collection > Mode and Policy Settings

•Resource Manager Essentials > Admin >Device Management >
Device Mgmt Settings

•Device Fault Manager > Device Management > Device Import > Auto allocation settings

•Internetwork Performance Monitor > Admin > Auto Allocation Settings

There are three possible modes in Auto Allocation:

•Manual — Auto allocation is disabled and you must add devices manually into each application.

•Allocate All Devices — Auto allocation is enabled and all the devices in DCR are added into the application. New devices added into DCR after applying the settings, will be dynamically added into applications.

•Allocate By Groups — Auto allocation is enabled and user can select one or more groups from Common Services. The list of devices that are part of the selected groups are added into application.

New devices added into the group after applying the settings, will be dynamically added into applications.

It is possible that each application in the same LMS server can be in different modes.

For example: RME can be in Allocate All Devices mode and DFM can be in Manual mode. You can manually add devices, even if the mode is Allocate all Devices or Allocate by Groups.

For complete details of the above modes, see the User Guide of the relevant application.

This section contains:

•Auto Allocation mode in DCR Master Slave Setup

•Behavior during Fresh Installation of LMS 3.1

•Behavior during Local Upgrade and Remote Upgrade/Restore

•Behavior During Re-installation of LMS 3.1

Auto Allocation mode in DCR Master Slave Setup

If the Master Slave setup is present, then groups from Master Server will be shown in the Group selector. This occurs whether the application is installed in the Master or in the Slave machine. All functionalities will behave as in the normal standalone DCR mode.

The following are the possible DCR mode changes and the corresponding device management mode:

•DCR mode changes from Standalone to Master

Auto Allocation mode is preserved.

•DCR mode changes from Standalone to Slave

All the devices are removed from the application space and device management is set to Manual Mode.

•DCR mode changes from Slave to Standalone

Auto Allocation mode is preserved.

•DCR mode changes from Slave to Master

Auto Allocation mode is preserved.

•DCR mode changes from Master to Slave

All the devices are removed from the application space and device management is set to Manual Mode.

•DCR mode changes from Master to Standalone

Auto Allocation mode is preserved.

Behavior during Fresh Installation of LMS 3.1

The following are the settings for the applications during fresh install:

•CM and RME

Auto Allocation feature is enabled in the Allocate All Devices mode

•DFM and IPM

Auto Allocation is off and device management will be in Manual mode

Behavior during Local Upgrade and Remote Upgrade/Restore

Each application behaves differently during upgrade, based on its previous version settings.

•RME and IPM

–If Auto Allocation was enabled in the previous version of LMS, after upgrading to LMS 3.1, the Auto Allocation feature is enabled in the Allocate All Devices mode.

–If Auto Allocation was disabled in the previous version of LMS, after upgrading to LMS 3.1, Device Management will be in Manual mode.

•DFM

–If Synchronization with DCR option was enabled in previous version of LMS, after upgrading to LMS 3.1, the Auto Allocation feature is enabled in the Allocate All Devices mode.

–If Synchronization with DCR option was disabled in the previous version of LMS, after upgrading to LMS 3.1, Device Management will be in Manual mode.

•CM

–If the filters were not specified in the Data Collection settings in the previous version of LMS, after upgrading to LMS 3.1, Auto Allocation feature is enabled in the Allocate All Devices mode.

–If the filters were specified in the Data Collection setting in the previous version of LMS, after upgrading to LMS 3.1, Auto Allocation feature is enabled in the Allocate by Group mode.

Campus Manager automatically creates a group with the name Migrated_From_CM_Filters, which matches the filter criteria and this group is selected.

Behavior During Re-installation of LMS 3.1

Auto Allocation settings will be preserved during re-install.

Enhancements to Report Jobs

After the completion of report jobs, the entire report is sent as e-mail, so that you can quickly access it.

You can:

•Enable this option in the Common Services Admin page. To access this page select Common Services > Server > Admin > System Preferences.

•Specify the type of attachment

•Specify the maximum size of the attachment

If the attachment is larger than the specified size, the URL to launch the report is included in the e-mail.

The following reports are sent as e-mails:

•Health and Utilization Monitor — All reports

•Resource Manager Essentials

–Inventory Reports

–Syslog Reports

–CDA jobs

–Baseline Jobs Reports

•Campus Manager

–Rogue MAC Report

–New MAC Report

–Dormant MAC report

Enhancements to Job Settings in Reports

While specifying time period for report generation, you can now specify whether the date range is in days, months or years. This makes the date selection much easier.

The following reports have been enhanced with this feature:

•Campus Manager

–Switch Port Reports —Reclaim Unused Up and Reclaim Unused Down

–MAC Reports — Rogue MAC, New MAC and Dormant MAC

–History Reports — History Switch Port Utilization and End Host History

•Device Fault Manager—Fault History report

•Resource Manager Essentials:

–Syslog report

–Change Audit report

Support for Zone-based Virtualization in Solaris 10

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

LMS3.1 will support LMS in whole-root non-global zone. Sparse root zone is not supported.

If the whole-root non-global zone is configured in the server, installing LMS 3.1 in global 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.

Support for ZFS File System

ZFS is a new kind of file system for the Solaris Operating System, based on pooled storage model. LMS 3.1 supports ZFS file system. It is supported in both global and non-global zones.

Support for LDom Virtualization

LDoms (Logical domains) is a virtualization technology from SUN Microsystems For details, see http://www.sun.com/servers/coolthreads/ldoms/index.xml

LDOMs are supported in LMS3.1.

Supported Network Management Systems

Table 1-3 lists the Network Management Systems (NMS) supported by Integration Utility 1.8, which is part of LMS 3.1.

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

Table 1-3 Supported Network Management Systems 

Network Management System	Supported Platforms
HP OpenView 8.13	•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.
HP OpenView 7.51	•Solaris 9 •Solaris 10 •Windows 2003 Standard Edition with Service Pack 1 •Windows 2003 Enterprise Edition with Service Pack 1 •Windows 2003 R2 Standard Edition •Windows 2003 R2 Enterprise Edition
HP OpenView 7.50	•Solaris 9 •Windows 2003 Standard Edition with Service Pack 1 •Windows 2003 Enterprise Edition with Service Pack 1
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

See User Guide for CiscoWorks Common Services 3.2 and the Online help for information about importing devices from third party NMS.

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

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.

Supported Devices

As additional device packages become available, you can download the Service Packs (formerly called IDUs) that contain them from Cisco.com.

Registered Cisco.com users can access the most current Device Package Updates, and download the latest device updates for CV, CM, DFM and RME from the following location:

•For CiscoView at:

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

•For Campus at:

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

•For DFM at:

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

•For RME at:

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

To see the list of installed application's device packages, select Common Services > Software Center and then select the required application name on the CiscoWorks home page.

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

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

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

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