Guest

CiscoWorks LAN Management Solution 3.2 and earlier

Readme for CiscoWorks LAN Management Solution 3.0 December 2007 Update on Windows

  • Viewing Options

  • PDF (891.4 KB)
  • Feedback
Readme for CiscoWorks LMS 3.0 December 2007 Update on Windows

Table Of Contents

Readme for CiscoWorks LMS 3.0 December 2007 Update on Windows

Description

New Features in LMS 3.0 December 2007 Update

New Features and Enhancements in LMS 3.0 December 2007 Solution Update

New Features and Enhancements in Individual LMS Applications

New Features in Common Services 3.1.1

New Features in Campus Manager 5.0.2

New Features in Resource Manager Essentials 4.1.1

New Features in Internetwork Performance Monitor 4.0.1

New Features in Device Fault Manager 3.0.2

New Features in CiscoView 6.1.7

New Features in CiscoWorks LMS Portal 1.0.1

New Features in CiscoWorks Assistant 1.0.1

Hardware and Software Requirements

Supported Network Management Systems

Supported Devices

Cisco Secure ACS Support

Prerequisites for CiscoWorks LMS 3.0 December 2007 Update

Downloading CiscoWorks LMS 3.0 December 2007 Update on Windows

Single Large File

Multiple Small Files

Important Download Notes for LMS 3.0 December 2007 Update

Installing CiscoWorks LMS 3.0 December 2007 Update on Windows

Installing the Update

Installing Evaluation Copy of HUM 1.0 From LMS 3.0 December 2007 Update

Verifying the LMS 3.0 December 2007 Update Installation

Installing CiscoWorks LMS 3.0 December 2007 Update for Missing LMS 3.0 Applications

Reinstalling CiscoWorks LMS 3.0 December 2007 Update

Data Migration Notes

Starting Topology Services From Solaris Client

Known Problems in LMS 3.0 December 2007 Update

Known Problems in Common Services

Known Problems in Campus Manager

Known Problems in Resource Manager Essentials

Known Problems in Internetwork Performance Monitor

Known Problems in Device Fault Manager

Known Problems in CiscoView

Known Problems in CiscoWorks LMS Portal

Known Problems in CiscoWorks Assistant

Resolved Problems in LMS 3.0 December 2007 Update

Resolved Problems in Common Services

Resolved Problems in Campus Manager

Resolved Problems in Resource Manager Essentials

Resolved Problems in Internetwork Performance Monitor

Resolved Problems in Device Fault Manager

Resolved Problems in CiscoView

Resolved Problems in CiscoWorks LMS Portal

Resolved Problems in CiscoWorks Assistant

Related Documentation

Related Documentation of LMS 3.0 December 2007 Update

LMS 3.0 Documentation

Notices

OpenSSL/Open SSL Project

License Issues


Readme for CiscoWorks LMS 3.0 December 2007 Update on Windows


This document provides the information on new features in CiscoWorks LMS 3.0 December 2007 Update, prerequisites, and instructions to install the update on Windows system.

This document contains the following sections:

Description

New Features in LMS 3.0 December 2007 Update

Hardware and Software Requirements

Supported Network Management Systems

Supported Devices

Cisco Secure ACS Support

Prerequisites for CiscoWorks LMS 3.0 December 2007 Update

Downloading CiscoWorks LMS 3.0 December 2007 Update on Windows

Installing CiscoWorks LMS 3.0 December 2007 Update on Windows

Data Migration Notes

Starting Topology Services From Solaris Client

Known Problems in LMS 3.0 December 2007 Update

Resolved Problems in LMS 3.0 December 2007 Update

Related Documentation

Notices

Description

CiscoWorks LAN Management Solution (LMS) 3.0 December 2007 Update is a Solution Update that contains:

Incremental versions to the applications in LMS 3.0 Solution.

CiscoWorks Common Services (CS) 3.1.1 — An incremental release over CS 3.1.

Campus Manager (CM)5.0.2 — An incremental release over Campus Manager 5.0.

Resource Manager Essentials (RME) 4.1.1 — An incremental release over RME 4.1.

Internetwork Performance Monitor (IPM) 4.0.1 — An incremental release over IPM 4.0.

Device Fault Manager (DFM) 3.0.2 — An incremental release over DFM 3.0.

CiscoView 6.1.7 — An incremental release over CiscoView 6.1.6.

CiscoWorks LMS Portal 1.0.1 — An incremental release over LMS Portal 1.0.

CiscoWorks Assistant 1.0.1 — An incremental release over CiscoWorks Assistant 1.0.

Integration Utility 1.7.1 — An incremental release over Integration Utility1.7.

Evaluation version of Health and Utilization Monitor (HUM) 1.0.

CiscoWorks LAN Management Solution 3.0 December 2007 Update is packaged as a single installable software image in LMS 3.0 December 2007 Update Product DVD.

You can also download the software image from Cisco.com Software Download site. See Downloading CiscoWorks LMS 3.0 December 2007 Update on Windows for more information.

New Features in LMS 3.0 December 2007 Update

This section explains:

New Features and Enhancements in LMS 3.0 December 2007 Solution Update

New Features and Enhancements in Individual LMS Applications

New Features and Enhancements in LMS 3.0 December 2007 Solution Update

The following are the new features and enhancements in LMS 3.0 December 2007 Solution Update:

Increased Scalability

SNMPv3 AuthPriv Support

Device Discovery in Common Services

Third Party Tools and Software Changes

VSS Support

Support for HUM Installation From LMS 3.0 December 2007 Update

Process Consolidation

Support for MDF 1.22

Increased Scalability

LMS 3.0 December 2007 Update now supports up to 5,000 devices for all applications (except DFM and HUM) that are installed in a single Solution server.

To manage 5,000 devices for all applications including DFM and HUM, you must setup:

DFM on a Standalone server (with only CS and DFM installed)

HUM on a Standalone server (with only CS and HUM installed)

All other CiscoWorks applications on another server

The system requirements for 5,000 devices in Solution and Standalone servers remain the same as the requirements for LMS 3.0.

See Installing and Getting Started With CiscoWorks LAN Management Solution 3.0 to understand the system requirements for LMS 3.0.

SNMPv3 AuthPriv Support

AuthPriv mode provides the encryption feature in addition to the security features such as message integrity and authentication.

SNMPv3 AuthPriv support provides secure access to devices by authenticating and encrypting packets over the network. This ensures that a packet has not been tampered with in-transit. This also scrambles the contents of a packet to prevent it from being seen by an unauthorized source.

It supports the following Privacy protocols:

DES

3DES

AES-128

AES-192

AES-256

In this release, the following LMS applications provide support to SNMPv3 AuthPriv level of security:

Common Services

Campus Manager

CiscoView

Internetwork Performance Monitor

Resource Manager Essentials

The behavior of handling SNMPv3 credentials is modified in Device Fault Manager. See Importing Devices with SNMPv3 Credentials for information.

Device Discovery in Common Services

In this release, Common Services supports Device Discovery based on many discovery modules.

The Device Discovery based on Cisco Discovery Protocol (CDP) that was earlier supported in Campus Manager, is also supported in Common Services.

The Device Discovery engine integrated with Common Services allows you to start Device Discovery from the Common Services application and update device information in DCR.

The new user interface provided for Device Discovery helps you to:

Set up Device Discovery protocols and discovery options.

Configure seed devices using their IP Address or hostname for the modules selected.

Specify SNMP settings to discover the devices from the network.

Configure Device Discovery filter settings.

Specify global settings that are common across Device Discovery modules.

Common Services 3.1.1 supports Device Discovery operations from CLI also.

The Device Discovery process that was available in the previous versions of Campus Manager is now removed.

Third Party Tools and Software Changes

The following are the third-party tools and software-related changes in this release:

NMIM Integration with HPOV 7.5.1 on Solaris and Windows systems.

HPOV 7.5.1 and NetView 7.1.5. supports integration with DCR Import and Export module.

Support in LMS for Windows Vista Business Operating System in the client systems.

Support in LMS for VMware ESX virtualization servers that have Windows Operating System.

VSS Support

Virtual Switching technology is the process of combining two standalone distribution switches found in the local distribution layer into a single management point.

This Virtual Switching technology is implemented in LAN Management Solution (LMS) by providing a Virtual Switching System Configuration tool under Resource Manager Essentials (RME).

Support for HUM Installation From LMS 3.0 December 2007 Update

In this release, support is provided to install the evaluation version of Health and Utilization Monitor (HUM) 1.0 at the end of Solution Update installation.

HUM 1.0 Evaluation version is packaged in the LMS 3.0 December 2007 Update DVD and in the downloadable Solution Update from Cisco.com.

Process Consolidation

Removing Dbmonitor processes reduces the number of processes at the solution level and results in better and improved process performance.

The CiscoWorks Assistant OPSxmlDbmonitor process and Dbmonitor processes of IPM and DFM are completely removed. RMEDbMonitor and RMECSTMServer have been consolidated into EssentialsDM process.

Some processes such as NCTemplateMgr and NetShowMgr have been consolidated into ConfigMgmtServer process.

Support for MDF 1.22

Meta Data Framework (MDF) Package defines device types in a uniform way across CiscoWorks applications. This package contains new device types, new device type definitions, new device icons, and solutions to some problems in earlier MDF packages.

Common Services 3.1.1 supports the MDF package version 1.22 that contains the following new device types:

Cisco Catalyst 2960-24-S Switch (1.3.6.1.4.1.9.1.929)

Cisco Catalyst 2960-24TC-S Switch (1.3.6.1.4.1.9.1.928)

Cisco Catalyst 2960-48TC-S Switch (1.3.6.1.4.1.9.1.927)

Cisco MDS 9216i Multilayer Fabric Switch (1.3.6.1.4.1.9.12.3.1.3.472)

Cisco 7603 Router (1.3.6.1.4.1.9.1.862)

Cisco SFS 3504 Multifabric Server Switch (1.3.6.1.4.1.6203.16)

Cisco BladeCenterH (1.3.6.1.4.1.6203.15)

Cisco WAE-612 Wide Area Application Engine (1.3.6.1.4.1.9.1.761)

Cisco ME 3400G-2CS-A Switch (1.3.6.1.4.1.9.1.825)

Cisco Catalyst Switch Module 3110G for IBM BladeCenter (1.3.6.1.4.1.9.1.909)

Cisco Virtual Switching System (1.3.6.1.4.1.9.1.896)

Cisco Catalyst 3560E-12D-S Switch (1.3.6.1.4.1.9.1.930)

Cisco Catalyst 3750G-12S Switch (1.3.6.1.4.1.9.1.530)

Cisco Unity Express Network Module(1.3.6.1.4.1.9.1.711,1.3.6.1.4.1.9.1.866)

Cisco Unity Express Advanced Integration Module (1.3.6.1.4.1.9.1.867, 1.3.6.1.4.1.9.1.868)

Cisco 1861 Integrated Services Router(1.3.6.1.4.1.9.1.939, 1.3.6.1.4.1.9.1.940)

Cisco 7609 Router(1.3.6.1.4.1.9.1.835)

Cisco Unified Communications 500 Series for Small Business (1.3.6.1.4.1.9.1.878, 1.3.6.1.4.1.9.1.879, 1.3.6.1.4.1.9.1.880, 1.3.6.1.4.1.9.1.881, 1.3.6.1.4.1.9.1.882, 1.3.6.1.4.1.9.1.883, 1.3.6.1.4.1.9.1.884, 1.3.6.1.4.1.9.1.885, 1.3.6.1.4.1.9.1.886, 1.3.6.1.4.1.9.1.888, 1.3.6.1.4.1.9.1.890, 1.3.6.1.4.1.9.1.892, 1.3.6.1.4.1.9.1.894, 1.3.6.1.4.1.9.1.895)

When you add new device types through MDF Package, it does not guarantee support for these device types in all CiscoWorks applications. Device support has to be provided by individual applications such as DFM, RME and CM. For a list of supported device types, see the relevant product documentation.

New Features and Enhancements in Individual LMS Applications

The following are the new features and enhancements in LMS Applications in this release:

New Features in Common Services 3.1.1

New Features in Campus Manager 5.0.2

New Features in Resource Manager Essentials 4.1.1

New Features in Internetwork Performance Monitor 4.0.1

New Features in Device Fault Manager 3.0.2

New Features in CiscoView 6.1.7

New Features in CiscoWorks LMS Portal 1.0.1

New Features in CiscoWorks Assistant 1.0.1

See the Online help or the User Guides of applications for a detailed explanation of the new features in LMS 3.0 December 2007 Solution Update.

The Related Documentation section lists the Cisco.com URLs of LMS Application User Guides.

New Features in Common Services 3.1.1

The following are the new features and enhancements in Common Services 3.1.1:

SNMPv3 AuthPriv Support and Related Changes

Common Services Device Discovery and Related Changes

Local User Policy Setup

Security Related Changes

SNMPv3 AuthPriv Support and Related Changes

In this release, Common Services extends its support to SNMPv3 AuthPriv level of security.

DCR Administration user interface is now enhanced to allow you to enter SNMPv3 AuthPriv credentials and store them in DCR.

The SNMPSet, SNMPWalk, and Management Station to Device tools now allow you to enter SNMPv3 AuthPriv credentials to troubleshoot and gather information about devices.

Common Services Device Discovery and Related Changes

Common Services 3.1.1 supports Device Discovery that was earlier supported by Campus Manager. The Device Discovery engine integrated with Common Services allows you to start Device Discovery from the Common Services application and update device information in DCR.

The Common Services Logging Configuration user interface is enhanced to allow you to debug the Common Services Device Discovery module.

The Common Services Home and LMS Setup Center are updated with the links to Common Services Device Discovery user interface.

Local User Policy Setup

Common Services 3.1.1 provides a user interface that allows you to select the options to:

Start the local username with a number

Include special characters in the local username

Specify the length of username and passwords of CiscoWorks local users

You can enter local usernames and passwords up to 256 characters.

Security Related Changes

The following are the security related changes in Common Services 3.1.1:

Performance Improvement in ACS Server Response Time

In this release, the responses to authentication and authorization requests from ACS Server is much faster. Instead of sending the requests to Primary, Secondary, and Tertiary ACS Servers, the request is forwarded only to an Active ACS Server. The Active ACS Server is determined and maintained when the user logs into CiscoWorks Server.

Option to provide hostname during ACS Integration

In this release, the option to enter the hostname in the IP Address field in ACS Server is allowed. If the AAA client (network device) added in DCR is resolvable by its DNS, the device is imported in DCR with its display name and IP Address. Otherwise, the device is imported in DCR with its display name and hostname.

Resynchronizing device cache without re-login

Earlier, if you added any device in ACS, you needed to log out and log into CiscoWorks Server for the devices to be visible in device selector.

In this release, the device cache in CiscoWorks Server is updated at every manual refresh and synchronized with the devices in ACS. This eliminates the need to log out and log into CiscoWorks Server.

The Refresh icon provided in the Device Management page and the Devices Not Configured in ACS report helps you to manually refresh the device cache in CiscoWorks Server.

Changes in MS Active Directory Pluggable Authentication Module

Earlier, only one value of usersroot was allowed for Distinguished Name based authentication in
MS Active Directory login module.

Common Services now allows you to enter multiple usersroot for Distinguished Name based authentication in MS Active Directory login module. You can enter multiple values for usersroot separated by semicolons.

New Features in Campus Manager 5.0.2

The following are the new features and enhancements available in Campus Manager 5.0.2:

SNMPv3 AuthPriv Support in Campus Manager

Removal of Device Discovery

Additional Dynamic User Tracking Configuration

New Options in User Tracking Command Line Interface (CLI)

New Best Practice Deviation that can be Fixed through Campus Manager

Enhancements in Discrepancies Report

SNMPv3 AuthPriv Support in Campus Manager

Campus Manager provides support for SNMPv3 AuthPriv mode.

Note that the IOS version running on the device should support the encryption algorithm used in SNMPv3 AuthPriv mode.

With this support:

Data can be collected securely from SNMP devices without the risk of the data being tampered with or corrupted.

Confidential information can be encrypted to prevent its contents from being exposed on the network. For example, SNMPSet command packets that change a router's configuration.

It is supported by all applications in Campus Manager. For Dynamic User Tracking, Campus Manager processes only SNMPv1/SNMPv2 traps even if the device is managed with SNMPv3.

Removal of Device Discovery

The Device Discovery process that was available in the previous versions of Campus Manager is now moved to Common Services.

Since Common Services 3.1.1 supports Device Discovery based on many protocols, the CDP based discovery earlier supported in Campus Manager is now supported in Common Services. This enables you to start Device Discovery from a single screen irrespective of the underlying protocol.

You can start Device Discovery from Common Services > Device and Credentials > Device Discovery.

Additional Dynamic User Tracking Configuration

Campus Manager provides a new GUI screen to configure properties that validate the SNMP traps received. These properties make the server receive traps only from specified devices and with specified community strings.

New Options in User Tracking Command Line Interface (CLI)

The following reports can now be generated from the CLI:

Switch Port Summary report

Generates reports that gives the number of Connected, Free, and Free down ports in each switch.

Wireless Report

Displays detailed information on Wireless clients connected to the network.

New Best Practice Deviation that can be Fixed through Campus Manager

In Switches that run STP, enabling Loop Guard and Port fast features in the same port results in unpredictable behavior. Campus Manager 5.0.2 detects this condition and flags it as a Best Practice Deviation in the name Loop Guard and Port Fast Enabled on Ports.

You can also fix this Best Practice Deviation through Campus Manager.

Enhancements in Discrepancies Report

Discrepancy Report has a new column, Fix

The discrepancies report has a new column named Fix, that indicates if the discrepancy is fixable through Campus Manager. If it is fixable, a link is provided. If you click on the link, it launches the page with Fix commands.

This saves you a few mouse clicks, that was previously required to know whether the discrepancy was fixable. The same enhancement is also available in the Best Practice Deviation Report.

Fix Template is editable

Campus Manager provides the appropriate set of commands to fix a discrepancy. You can now edit and change the commands provided, to suit your network requirements.

The same enhancement is also provided in the Best Practice Deviation report.

New Features in Resource Manager Essentials 4.1.1

The following are the new features and enhancements available in Resource Manager Essentials 4.1.1:

Support for Virtual Switching System

Support for SNMPv3 AuthPriv Security Mode in RME

Device Statistics Report

Hardware Statistics Report

POE Report

Enhanced Expert Distribution using Skip Verification

SME Notes in End of Sale/End of Life Report

New Image Support for 7600 Series Devices

Support for Virtual Switching System

The Virtual Switching technology is the process of combining two standalone distribution switches found in the local distribution layer into a single management point.

This Virtual Switching technology is implemented in LAN Management Solution (LMS) by providing a Virtual Switching System Configuration tool under Resource Manager Essentials (RME).

Support for SNMPv3 AuthPriv Security Mode in RME

RME now supports SNMPv3 AuthPriv security mode to access devices. SNMPv3 AuthPriv commands can be downloaded to the device using Netconfig SNMP Security task.

After a successful download, new credentials will be updated in the DCR by default. SNMP Security task is supported only for IOS, CATOS and CE devices.

Device Statistics Report

A Device Statistics report is a system report. You can use this Inventory system report to view the count of one or more components available for each device for the selected devices. The output tables are categorized based on the devices.

Hardware Statistics Report

A Hardware Statistics report is a system report. You can generate this Inventory system report to view the count of one or more components in the selected devices. The output tables are categorized based on the components.

POE Report

Power over Ethernet (POE) is the ability of the LAN switching infrastructure to provide power over a copper Ethernet cable to an endpoint (Powered device).

You can generate a POE report to display detailed information of POE supported devices managed by RME.

Enhanced Expert Distribution using Skip Verification

To improve the performance, Software Management now uses an enhanced approach to distribute images to devices using the Expert distribution or Distribute by Device (Advanced) method.

This approach allows you to decide whether you want the verification to take place either during the software distribution job scheduling stage or during the job execution stage.

You can select the checkbox available in the Distribute by Device (Advanced) flow if you want to postpone the verification to happen during the job execution stage.

SME Notes in End of Sale/End of Life Report

The End of Sale or End of Life data may not be the same in the End of Sale/End of Life report for some devices. This is because the data source may have multiple End of Sale and End of Life values. So, the SME Notes field has been added to address this.

The SME Notes field gets populated for all such devices that have multiple End of Sale or End of Life values.

New Image Support for 7600 Series Devices

Earlier Cisco IOS Software Modularity images in LMS 3.0 did not support image names starting with c7600sup720 and c7600sup32. This was because of the change in the naming conventions for these images.

Now RME Software Management also provides support for these images having different naming conventions.

New Features in Internetwork Performance Monitor 4.0.1

The following are the new features and enhancements in Internetwork Performance Monitor (IPM) 4.0.1:

Clickable Legends for Graphs

Support for 5,000 Collectors

Clickable Legends for Graphs

When there are many curves in a graph, they tend to overlap each other and it becomes difficult to view a particular curve. Clickable legends have been introduced to help you view a particular graph curve by just clicking on the legends available for each graph curve.

You can click on a legend to view a particular curve, if it is not already visible. You can click on the same legend again to hide that curve.

Support for 5,000 Collectors

IPM now supports 5,000 Collectors. This 5,000 Collectors support is applicable only for:

IPM licenses that support 5,000 devices

IPM Standalone installation that includes installation of Common Services, Portal, CiscoWorks Assistant and IPM

The Collector support for the other LMS 3.0 licenses remains the same.

New Features in Device Fault Manager 3.0.2

DFM 3.0.2 provides the following new features and enhancements:

Importing Devices with SNMPv3 Credentials

Changes in Supported Network Management Systems

Importing Devices with SNMPv3 Credentials

When a device is imported into DCR with SNMPv3 Credentials, DFM reacts to each of the SNMPv3 credentials in the following ways:

SNMPv3 AuthPriv:

When a device with SNMPv3AuthPriv credentials is imported into DFM from DCR, DFM pushes the device to Unknown Devices in Inventory Group with an error message SNMPv3 is not supported.

SNMPv3 NoAuthNoPriv:

When a device with SNMPv3 username is imported into DFM from DCR, DFM pushes the device into All Questioned State Devices in Inventory Group with an error message Missing SNMPv3 Authentication Password.

SNMPv3 AuthNoPriv:

When a device, with SNMPv3 username and password, and its privacy password blank, is imported into DFM from DCR, DFM discovers the device successfully and the device is grouped under All Known Devices in Inventory Group.

Changes in Supported Network Management Systems

DFM supports HPOV 7.5.1 and NetView 7.1.5 in this release.

New Features in CiscoView 6.1.7

The following features are new to CiscoView 6.1.7:

Ability to Launch Health and Utilization Monitor (HUM) Reports

Support for the Cisco Catalyst 6500 Virtual Switching System (VSS) Single/Dual Chassis View

Ability to Launch Health and Utilization Monitor (HUM) Reports

With the CVCrossLaunch device package installed, you can generate and view two HUM reports:

Device Dashboard report

Provides a snapshot of a device, listing information such as its current status, its availability over the past 24 hours, and its memory utilization figures. To launch this report, right-click the chassis view of a device, and then select HUM Device Dashboard from the context menu.

Interface report

Summarizes activity on the selected port during the past hour. To launch this report, right-click the port for which you want to generate a report, and then select HUM Interface Report from the context menu.

Support for the Cisco Catalyst 6500 Virtual Switching System (VSS) Single/Dual Chassis View

Virtual Switch functionality allows you to take two switches and combine them virtually so that they can be managed from one point/IP address.

To enable this feature, you must install the Catalyst 6000 IOS device package (version 29.0 or later).

New Features in CiscoWorks LMS Portal 1.0.1

The following are the new portlets and features in CiscoWorks LMS Portal 1.0.1:

Syslog Collectors Information Portlet in Resource Manager Essentials View

Servers and Applications Portlet in Common Services View

Device Discovery Summary Portlet in Common Services View

Additional Features in Frequently Used Links Portlet

Manual Refresh Icon for Portal Home Page

New Columnar Layout

Row Shading

Syslog Collectors Information Portlet in Resource Manager Essentials View

This portlet displays the list of remote Syslog collectors subscribed to the RME server.

It contains Syslog collector information such as the name of the remote Syslog, analyser name, status, the number of packets received and so on. This portlet will not be added to any view by default. However, it is listed under the RME link and you can add the portlet to any view.

Servers and Applications Portlet in Common Services View

This portlet enables you to launch the DCR Master/Server installed applications home page. If the server is in the Standalone mode, the portlet displays its own installed applications home page.

This portlet will not be added to any view by default. However, it is listed under the CS link and you can add the portlet to any view.

Device Discovery Summary Portlet in Common Services View

This portlet gives the summary of the devices, such as the total number of devices discovered, reachable devices, unreachable devices, devices added to DCR, devices updated to DCR and so on.

This portlet will not be added to any view by default. However, it is listed under the CS link and you can add the portlet to any view.

Additional Features in Frequently Used Links Portlet

This includes features such as the edit, delete, reset button, drag and drop features for the newly added links.

Manual Refresh Icon for Portal Home Page

A new refresh icon is now available at the top right corner of the Portal home page. Insead of getting the cached data,( new feature in Portal 1.0.1) this refresh icon enables you to view the latest data of the portlets in the view. However, the browser refresh (Functional key F5) only refreshes the screen not the data.

New Columnar Layout

A new columnar layout (2:1:2-1) has been introduced in this release and the portlets can be organized in the corresponding format.

Row Shading

To enhance the look and feel and understanding of the portlets, rows and column separators are used.

New Features in CiscoWorks Assistant 1.0.1

The following are the new features in CiscoWorks Assistant 1.0.1:

Changes in CiscoWorks Assistant for SNMPv3 AuthPriv Support

Changes in Device Discovery

Changes in CiscoWorks Assistant for SNMPv3 AuthPriv Support

In this release, Common Services extends its support to SNMPv3 AuthPriv level of security.

The SNMPv3 credentials pages in CiscoWorks Assistant are now modified to include the new fields such as Privacy Algorithm and Privacy Password.

Changes in Device Discovery

Running Device Discovery in CiscoWorks Assistant user interface now points to Common Services.

The CiscoWorks Assistant Server Setup workflow (Add Device page) has been enhanced for the Device Discovery changes.

The new user interface provided for Device Discovery helps you to:

Configure seed devices using their IP Address or hostname for the modules selected.

Specify SNMP settings to discover the devices from the network.

Configure Device Discovery filter settings.

Specify global settings that are common across Device Discovery modules.

CiscoWorks Assistant Server supports running immediate Device Discovery jobs.

Hardware and Software Requirements

In addition to the hardware and software requirements for Servers and Clients described in LMS 3.0, the following additional requirments are supported in LMS 3.0 December 2007 Update:

Supported Server Operating Systems

Supported Client Operating Systems

Supported Processors

Supported Virtualization Systems

To check the hardware and software requirements of LMS 3.0, see the Prerequisites chapter of Installing and Getting Started With CiscoWorks LAN Management Solution 3.0.

This document is available at this location:

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

Supported Server Operating Systems

The following Windows Operating Systems are supported in LMS 3.0 December 2007 Update in addition to the existing Windows 2003 32-bit Operating System support:

Windows Server 2003 Standard Edition 64-bit Operating System

Windows Server 2003 Enterprise Edition 64-bit Operating System

Windows Server 2003 R2 Standard Edition 64-bit Operating System

Windows Server 2003 R2 Enterprise Edition 64-bit Operating System

Supported Client Operating Systems

The Windows client systems of LMS 3.0 December 2007 Update supports Windows Vista Business Edition other than the Operating Systems listed in the Prerequisites chapter of Installing and Getting Started With CiscoWorks LAN Management Solution 3.0.


Note Campus Manager User Tracking Utility (UTU) does not run on Windows Vista client systems.


Supported Processors

The following processors are supported for Windows systems in LMS 3.0 December 2007 Update other than the supported processors listed in the Prerequisites chapter of Installing and Getting Started With CiscoWorks LAN Management Solution 3.0:

Quad-Core Intel Xeon processor 5400 series

Quad-Core Intel Xeon processor 5300 series

Quad-Core Intel Xeon processor 7400 series

Supported Virtualization Systems

In addition to the existing platform support, LMS 3.0 December 2007 Update can be installed and run on systems with VMware ESX 3.0.1, a virtualization software.

Virtualization allows to run multiple virtual machines with same or different Operating Systems independently on the same physical machine.


Note LMS 3.0 December 2007 Update is tested only on VMware ESX 3.0.1 Servers with Windows Operating Systems.


Supported Network Management Systems

Table 1 lists the supported Network Management Systems in LMS 3.0 December 2007 Update on Windows.

Table 1 Supported Network Management Systems on Windows Systems

Network Management Systems
Version
Supported Platforms

HPOV

7.5

Windows 2003 Standard Edition with Service Pack 2

Windows 2003 Enterprise Edition with Service Pack 2

7.51

Windows 2003 Standard Edition with Service Pack 2

Windows 2003 Enterprise Edition with Service Pack 2

Windows 2003 R2 Standard Edition with Service Pack 2

Windows 2003 R2 Enterprise Edition with Service Pack 2

NetView

7.1.4

Windows 2003 Standard Edition with Service Pack 2

Windows 2003 Enterprise Edition with Service Pack 2

7.1.5

Windows 2003 Standard Edition with Service Pack 2

Windows 2003 Enterprise Edition with Service Pack 2

Windows 2003 R2 Standard Edition with Service Pack 2

Windows 2003 R2 Enterprise Edition with Service Pack 2


Supported Devices

See Supported Devices Table for LMS 3.0 December 2007 Update on Cisco.com for new device support details.

This document is available on Cisco.com at:

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

Cisco Secure ACS Support

CiscoWorks LAN Management Solution 3.0 December 2007 Update supports ACS mode of authentication and authorization.

To use this mode, you must have a Cisco Secure ACS (Access Control Server), installed on your network. CiscoWorks LAN Management Solution 3.0 December 2007 Update supports the following versions of Cisco Secure ACS:

Cisco Secure ACS 3.2 for Windows Server

Cisco Secure ACS 3.2.3 for Windows Server

Cisco Secure ACS 3.3.2 for Windows Server

Cisco Secure ACS 3.3.3 for Windows Server

Cisco Secure ACS 3.3.4 for Windows Server

Cisco Secure ACS 4.0.1 for Windows Server

Cisco Secure ACS 4.1 for Windows Server

Cisco Secure ACS 4.1.1 for Windows Server

Cisco Secure ACS 4.1.4 for Windows Server

Cisco Secure ACS 4.2 for Windows Server

Cisco Secure Appliance 3.3.3

Cisco Secure Appliance 3.3.4

Cisco Secure Appliance 4.0.1

Cisco Secure Appliance 4.1

Cisco Secure Appliance 4.1.1

Cisco Secure Appliance 4.1.4

Cisco Secure Appliance 4.2

We recommend that you install the Admin HTTPS PSIRT patch, if you are using ACS 3.2.3.

To install the patch:


Step 1 Go to http://www.cisco.com/pcgi-bin/tablebuild.pl/cs-acs-win

You must enter Cisco.com username and password after you launch this URL.

Step 2 Click the Download CiscoSecure ACS Software (Windows) link.

You can find the link to the Admin HTTPS PSIRT patch, in the table.


Prerequisites for CiscoWorks LMS 3.0 December 2007 Update

Before installing LMS 3.0 December 2007 Update, LMS 3.0 must be installed on your system.

For details, see Installing and Getting Started With LAN Management Solution 3.0 available at:

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

Note the following:

If you do not want to install one or more of the LMS 3.0 applications currently but plan to install them later, you must reinstall LMS 3.0 December 2007 Update after you install the missing applications.

For example, if you install RME 4.1 after installing the LMS 3.0 December 2007 Update, you must reinstall LMS 3.0 December 2007 Update.

However, you must follow a workaround to install any of the missing LMS 3.0 applications later, after installing the LMS 3.0 December 2007 Update. See Installing Missing LMS 3.0 Applications for details.

You cannot select individual application updates. This update automatically detects the installed LMS 3.0 applications and installs the required updates for that specific application.

If you have configured DCR Master-Slave setup, you must install this update in all of the CiscoWorks servers.

The Common Services Service Pack versions must be same in all of the DCR Master-Slave setup machines.

You must have a minimum free space of 800 MB on your hard disk to install this update.

If you do not have any of the applications at the LMS 3.0 level, the installation will terminate with an error message.

Downloading CiscoWorks LMS 3.0 December 2007 Update on Windows

You can download LMS 3.0 December 2007 Update using either of these options:

Single Large File

Multiple Small Files

These files are available on the LMS Software Download page:

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

You must be a registered Cisco.com user to download this update. You must log on to Cisco.com Software Download site with a valid username and password. See Important Download Notes for LMS 3.0 December 2007 Update before you download the software update.

Single Large File

A single LMS 3.0 December 2007 Update file is available if you want to download one large file.

The Single Large File option has these files:

lms30_dec07_update_win_k9.zip

lms30_dec07_update_win_readme.pdf

Multiple Small Files

The Single Large LMS 3.0 December 2007 Update file is split into multiple small files if you want to download small files.

The Multiple Small Files option has these files:

lms30_dec07_update_win_cksum.exe

lms30_dec07_update_win_unzip.exe

lms30_dec07_update_win_installer.bat

lms30_dec07_update_win_k9_1of3.zip

lms30_dec07_update_win_k9_2of3.zip

lms30_dec07_update_win_k9_3of3.zip

lms30_dec07_update_win_readme.pdf

Important Download Notes for LMS 3.0 December 2007 Update

This section contains important information that you should read before you begin downloading:

The Single Large File and Multiple Small Files of this update are not visible through the CiscoWorks Software Updates page (Common Services > Software Center > Software Update).

You must not change the filename of the update files.

You must download all of the Multiple Small Files in the same location.

You can download Multiple Small Files in any order.

You must have minimum free space of 800 MB in your hard disk to download this update.

Installing CiscoWorks LMS 3.0 December 2007 Update on Windows

To install this update, login as local administrator or user with administrator privileges on the system on which you installed the LMS 3.0 applications.

Before you install CiscoWorks LMS 3.0 December 2007 Update, ensure that you have installed all the LMS 3.0 applications.

To install any of the LMS 3.0 applications later, after installing the LMS 3.0 December 2007 Update, you must follow the instructions explained in Installing CiscoWorks LMS 3.0 December 2007 Update for Missing LMS 3.0 Applications.

The LMS 3.0 December 2007 Update is installed in the same directory as LMS 3.0. By default, it is System_Drive\Program Files\CSCOpx, where System_Drive is the Windows operating system installed directory.

See Data Migration Notes for information about local or remote migration of data onto CiscoWorks LMS 3.0 December 2007 Update server.

It takes approximately 1 hour to install the complete update for all LMS applications.

The following sections describe the procedures for:

Installing the Update

Installing Evaluation Copy of HUM 1.0 From LMS 3.0 December 2007 Update

Verifying the LMS 3.0 December 2007 Update Installation

Installing CiscoWorks LMS 3.0 December 2007 Update for Missing LMS 3.0 Applications

Reinstalling CiscoWorks LMS 3.0 December 2007 Update

Installing the Update

To install the LMS 3.0 December 2007 Update:


Step 1 Either:

Navigate to the location on your system, where you downloaded the LMS 3.0 December 2007 Update files.

Or

Insert the LMS 3.0 December 2007 Update DVD if want to install the update from DVD.

If you have downloaded Single Large File Update:

a. Unzip the lms30_dec07_update_win_k9.zip file.

The contents of the zip file are extracted under the lms30_dec07_update_win_k9 directory.

b. Navigate to the lms30_dec07_update_win_k9 folder.

c. Double-click CiscoWorks_LMS_3.0_Dec_2007_Update.exe.

If you have downloaded Multiple Small Files Update, run the Windows batch file at the command prompt:

lms30_dec07_update_win_installer.bat

If you have not downloaded all the Multiple Small Files, an error message appears:

ERROR: You have not downloaded all the above files  
ERROR: Please download all the above files and  
ERROR: then run this script 

Download all the Multiple Small Files. See the Multiple Small Files for the list of files.

If you have downloaded all the Multiple Small Files, a message appears:

INFO: You have downloaded all the necessary files 
INFO: creating the zip file from the downloaded files 

If you are installing the update from DVD, double-click Setup.exe or autorun.exe.

A pop-up appears.

Step 2 Click Yes to continue.

While installing from the network drive, the Installing from Network Drive message appears.

Installation from network drive will be slower when compared to installing from the local drive. If you are installing from a network drive, the installation might take longer to complete.

Step 3 Click Yes to continue with the installation or No to quit the installation.

The following warning message appears.

Automatic data backup do not happen during this installation. 
We recommend you to take a backup of data before starting this installation. 
Do you want to continue the installation? 

Step 4 Click Yes to continue with the installation or No to quit the installation.

The following message appears if Windows Management Instrumentation (WMI) services are running:

The setup program has detected Windows Management Instrumentation (WMI) services running. 
This will lock some CiscoWorks processes and may abort installation abruptly. 
To avoid this, installation will stop and start the WMI services. 
Do you want to proceed? 

Step 5 Click OK to continue.

The IIS detection window appears, if IIS is enabled on the server.

When Internet Information Services (IIS) is detected on your system and if you have continued the installation without 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.

To disable IIS in your machine, right-click the IIS Admin Service icon from Control Panel and click Stop.

IIS is now disabled. You need to go back to your installation screen to resume installation.

Step 6 Click OK to continue.

If LMS 3.0 is not installed on the CiscoWorks Server, the following message is displayed and the installation aborts:

Install LMS 3.0 applications before installing LMS 3.0 Dec 2007 Update. 

The Welcome screen appears.

Step 7 Click Next to continue.

The Software License Agreement window appears. You must accept this agreement to install the CiscoWorks LMS 3.0 Dec 2007 Update.

Step 8 Click Accept to continue.

The Install Updates window appears with the updates that will be installed.

Step 9 Click Next.

If CiscoWorks is in ACS mode, the following message appears:

The application that you are installing requires new tasks to be registered with ACS. If 
you have already registered this application with ACS from another server, you do not need 
to register it again. However if you re-register the application, you will lose any custom 
roles that you had created earlier for this application in ACS.

Step 10 Click:

Yes to register the application with ACS Server.

Or

No to continue the installation without registering the application.


Caution If you click Yes, to register with ACS server, you will lose the custom roles which are defined in the previous version. If you click No, not to register with ACS server, all the custom roles which are defined in Common Services 3.0.5 will be carried forward.

The installation program checks the system configuration and required space.

The System Requirements window displays the system requirements, available space in the disk drive, and CPU speed.

Step 11 Click Next.

The Summary window appears with the updates that will be installed and the settings for the installation.

Step 12 Click Next.

Installation now proceeds.

The following message appears only if you have installed the update for RME:

To ensure that you retain the latest device support for RME, 
please install the latest Device Packages from CCO @
http://www.cisco.com/cgi-bin/tablebuild.pl/cw2000-rme
Please refer to the Installation and Setup Guide for details. 

The following message appears only if you have installed the update for Campus Manager:

To ensure that you retain the latest device support for CM,
please install the latest Device Packages from CCO @
http://www.cisco.com/cgi-bin/tablebuild.pl/cw2000-campus
Please refer to the Installation and Setup Guide for details.

The following message appears only if you have installed the update for DFM:

To ensure that you have up-to-date device support,
install the latest Service Pack (SP) from Cisco.com, at
http://www.cisco.com/cgi-bin/tablebuild.pl/cw2000-dfm.
For installation details, refer to the DFM Installation and Setup Guide.

The following message appears:

If you plan to install any of the LMS 3.0 applications later,
you must reinstall CiscoWorks LMS 3.0 December 2007 Update
after installing these applications. 

Step 13 Click OK.

The following message appears.

Would you like to install Health and Utilization Monitor 1.0 now?: 

Step 14 Either:

Click Yes to install the evaluation copy of Health and Utilization Monitor 1.0 from LMS 3.0 December 2007 Update.

Or

Click No to install the evaluation copy of Health and Utilization Monitor 1.0 later. See Installing Evaluation Copy of HUM 1.0 From LMS 3.0 December 2007 Update for details.

The Setup Complete dialog box appears after installation completes.

Step 15 Click Finish to start CiscoWorks.


Installing Evaluation Copy of HUM 1.0 From LMS 3.0 December 2007 Update

While installing LMS 3.0 December 2007 Update, you can choose to install HUM 1.0 Evaluation copy at a later point of time.

You can install HUM 1.0 Evaluation copy later by any one of the following ways:

From LMS 3.0 December 2007 Update DVD, run Setup.exe available on the location sp\HUM\disk1.

From the downloaded Single Large File Update:

a. Extract CiscoWorks_LMS_3.0_Dec_2007_Update.exe if you have not done earlier.

b. Go to extracted_location\sp\HUM\disk1 and run Setup.exe.

From the downloaded Multiple Small Files Update:

a. Run lms30_dec07_update_win_installer.bat to extract the contents from all the zip files, if you have not done earlier.

b. Extract CiscoWorks_LMS_3.0_Dec_2007_Update.exe.

c. Go to extracted_location\sp\HUM\disk1 and run Setup.exe.

Re-install LMS 3.0 December 2007 Update and click Yes when HUM 1.0 installation is prompted at the end of LMS 3.0 December 2007 Update installation.

See Installation Guide for CiscoWorks Health and Utilization Monitor 1.0 available on Cisco.com for installation instructions.

Verifying the LMS 3.0 December 2007 Update Installation

After you install the CiscoWorks LMS 3.0 December 2007 Update on Windows, you can verify the installation. To do this:


Step 1 Launch CiscoWorks by entering:

http://server_name:port_number

where server_name is the name of the CiscoWorks Server and port_number is the TCP port used by the CiscoWorks Server.

In normal mode (HTTP), the default TCP port for CiscoWorks Server is 1741. When SSL is enabled (HTTPS), the default TCP port for CiscoWorks Server is 443.

Step 2 Select Common Services > Software Center > Software Update.

The Software Updates window appears.

The following entries appear in the Products Installed table for each application that you have installed:

Product Name
Version With Patch Level

CiscoWorks Common Services

3.1.1

Campus Manager

5.0.2

CiscoView

6.1.7

CiscoWorks Assistant

1.0.1

Device Fault Manager

3.0.2

Internetwork Performance Monitor

4.0.1

Integration Utility

1.7.1

LMS Portal

1.0.1

Resource Manager Essentials

4.1.1

Health and Utilization Monitor

1.0.0



Installing CiscoWorks LMS 3.0 December 2007 Update for Missing LMS 3.0 Applications

If you install any of the LMS 3.0 applications after installing the LMS 3.0 December 2007 Update, you must reinstall the LMS 3.0 December 2007 Update once again.

To install this update, login as administrator on the system on which you installed the LMS 3.0 applications. You must have superuser privileges on the system being updated.

This section explains:

Installing Missing LMS 3.0 Applications

Installing the Update for Missing LMS 3.0 Applications

Installing Missing LMS 3.0 Applications

To install any of the missing LMS 3.0 applications later, after installing the LMS 3.0 December 2007 Update:


Step 1 Go to NMSROOT/setup and look for the .info files for the LMS applications that are installed already.

Step 2 Modify the .info files and set the value of PATCHVER in these files to their original value of 0.

Step 3 Install the missing LMS 3.0 applications and wait for the installation to complete.

See Installing and Getting Started With LAN Management Solution 3.0 for installation instructions.

Step 4 Reset the values of PATCHVER as it was earlier after the installation is complete.


Installing the Update for Missing LMS 3.0 Applications

To install the updates for missing LMS 3.0 applications:


Step 1 Either:

Navigate to the location on your system, where you downloaded the LMS 3.0 December 2007 Update files.

Or

Insert the LMS 3.0 December 2007 Update DVD if want to install the update from DVD.

If you have downloaded Single Large File Update:

a. Unzip the lms30_dec07_update_win_k9.zip file.

The contents of the zip file are extracted under the lms30_dec07_update_win_k9 directory.

b. Navigate to the lms30_dec07_update_win_k9 folder.

c. Double-click CiscoWorks_LMS_3.0_Dec_2007_Update.exe.

If you have downloaded Multiple Small Files Update, run the Windows batch file at the command prompt:

lms30_dec07_update_win_installer.bat

If you have not downloaded all the Multiple Small Files, an error message appears:

ERROR: You have not downloaded all the above files 
ERROR: Please download all the above files and 
ERROR: then run this script 

Download all the Multiple Small Files. See the Multiple Small Files for the list of files.

If you have downloaded all the Multiple Small Files, a message appears:

INFO: You have downloaded all the necessary files
INFO: creating the zip file from the downloaded files 

If you are installing the update from DVD, double-click Setup.exe or autorun.exe.

A pop-up appears.

Step 2 Click Yes to continue.

While installing from the network drive, the Installing from Network Drive message appears.

Installation from network drive will be slower when compared to installing from the local drive. If you are installing from a network drive, the installation might take longer to complete.

Step 3 Click Yes to continue with the installation or No to quit the installation.

The following warning message appears.

Automatic data backup do not happen during this installation.
We recommend you to take a backup of data before starting this installation.
Do you want to continue the installation? 

Step 4 Click Yes to continue with the installation or No to quit the installation.

The following message appears if Windows Management Instrumentation (WMI) services are running:

The setup program has detected Windows Management Instrumentation
(WMI) services running.
This will lock some CiscoWorks processes and may abort installation abruptly.
To avoid this, installation will stop and start the WMI services.
Do you want to proceed? 

Step 5 Click Yes to continue.

The IIS detection window appears, if IIS is enabled on the server.

When Internet Information Services (IIS) is detected on your system and if you have continued the installation without 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.

To disable IIS in your machine, right-click the IIS Admin Service icon from Control Panel and click Stop.

IIS is now disabled. You need to go back to your installation screen to resume installation.

Step 6 Click Yes to continue.

If LMS 3.0 is not installed on the CiscoWorks Server, the following message is displayed and the installation aborts:

Install LMS 3.0 applications before installing LMS 3.0 Dec 2007 Update. 

The Welcome screen appears.

Step 7 Click Next to continue.

The Software License Agreement window appears. You must accept this agreement to install the CiscoWorks LMS 3.0 Dec 2007 Update.

Step 8 Click Accept to continue.

The Install Updates window appears with the updates that will be installed and the updates that are already installed.

You can select either of these options:

Install new updates only—To install only the new updates.

Install/reinstall all updates—To install the new updates and also reinstall the updates for the already updated applications.

Step 9 Select one of these options and click Next.

If CiscoWorks is in ACS mode, the following message appears:

The application that you are installing requires new tasks to be registered with ACS. If 
you have already registered this application with ACS from another server, you do not need 
to register it again. However if you re-register the application, you will lose any custom 
roles that you had created earlier for this application in ACS.

Step 10 Click:

Yes to register the application with ACS Server.

Or

No to continue the installation without registering the application.



Caution If you click Yes, to register with ACS server, you will lose the custom roles which are defined in the previous version. If you click No, not to register with ACS server, all the custom roles which are defined in Common Services 3.0.5 will be carried forward.

The installation program checks the system configuration and required space.

The System Requirements window displays the system requirements, available space in the disk drive, and CPU speed.

Step 11 Click Next.

The Summary window appears with the updates that will be installed and the settings for the installation.

Step 12 Click Next.

Installation now proceeds.

The following message appears only if you have installed the update for RME:

To ensure that you retain the latest device support for RME, 
please install the latest Device Packages from CCO @
http://www.cisco.com/cgi-bin/tablebuild.pl/cw2000-rme
Please refer to the Installation and Setup Guide for details. 

The following message appears only if you have installed the update for Campus Manager:

To ensure that you retain the latest device support for CM,
please install the latest Device Packages from CCO @
http://www.cisco.com/cgi-bin/tablebuild.pl/cw2000-campus
Please refer to the Installation and Setup Guide for details.

The following message appears only if you have installed the update for DFM:

To ensure that you have up-to-date device support,
install the latest Service Pack (SP) from Cisco.com, at
http://www.cisco.com/cgi-bin/tablebuild.pl/cw2000-dfm.
For installation details, refer to the DFM Installation and Setup Guide.

The following message appears:

If you plan to install any of the LMS 3.0 applications later,
you must reinstall CiscoWorks LMS 3.0 December 2007 Update
after installing these applications. 

Step 13 Click OK.

The following message appears.

Would you like to install Health and Utilization Monitor 1.0 now?: 

Step 14 Either:

Click Yes to install the evaluation copy of Health and Utilization Monitor 1.0 from LMS 3.0 December 2007 Update.

Or

Click No to install the evaluation copy of Health and Utilization Monitor 1.0 later. See Installing Evaluation Copy of HUM 1.0 From LMS 3.0 December 2007 Update for details.

The Setup Complete dialog box appears after installation completes.

Step 15 Click Finish to start CiscoWorks.


Reinstalling CiscoWorks LMS 3.0 December 2007 Update

To reinstall CiscoWorks LMS 3.0 December 2007 Update, follow the instructions in the section, Installing the Update.

Data Migration Notes

LMS 3.0 December 2007 Update supports the following data migration paths:

Local upgrade from LMS 3.0

Remote upgrade from LMS 2.2, LMS 2.5, LMS 2.5.1, LMS 2.6, LMS 2.6 SP1 or LMS 3.0

The data migration procedure for local and remote upgrade remains as same as LMS 3.0. See Data Migration Guide for CiscoWorks LAN Management Solution 3.0 for more information.

In addition to the data listed in the Scope of Data Migration section in Data Migration Guide for CiscoWorks LAN Management Solution 3.0, the following data gets migrated when you install LMS 3.0 December 2007 Update:

Public portal configuration

Per-user Private portal configuration

Discovery Settings are migrated from Campus Manager of earlier versions to Common Services

IPM Collectors are automatically migrated when you do a local migration of data to LMS 3.0 December 2007 Update

Starting Topology Services From Solaris Client

To start the topology services from a Solaris client system, you must:

Install the Java plug-in.

Associate the Topology_Services.jnlp file with the correct Java application.

See Starting Topology Services in the Installing and Getting Started With CiscoWorks LAN Management Solution 3.0 document available on Cisco.com for instructions.

Known Problems in LMS 3.0 December 2007 Update

This section contains:

Known Problems in Common Services

Known Problems in Campus Manager

Known Problems in Resource Manager Essentials

Known Problems in Internetwork Performance Monitor

Known Problems in Device Fault Manager

Known Problems in CiscoView

Known Problems in CiscoWorks LMS Portal

Known Problems in CiscoWorks Assistant

Known Problems in Common Services

Table 2 lists the known problems in Common Services 3.1.1 version..

Table 2 Known Problems in Common Services 3.1.1

Bug ID
Summary
Explanation

CSCsj94584

Cannot install any CiscoWorks
application after installing LMS followed by an application patch installation.

When LMS is installed and any of the applications are patched, no additional applications can be installed and an error message appears.

This occurs when LMS applications are patched after installation, then a new application is installed.

For example, if Campus Manager and Device Fault Manager are patched to LMS 3.0 December 2007 Update in a CiscoWorks Server, you cannot install Internetwork Performance Monitor 4.0.

Workaround:

1. Modify the .info files for the patched modules under
NMSROOT/setup and set the value of PATCHVER in these files to their original value of 0.

2. Install the new application on CiscoWorks Server.

3. Reset the values of PATCHVER to their patched versions after the installation is complete.

CSCsg97728

Jobs scheduled on March 11 between 12 AM to 1:30 AM are moved to Missed Start state or rescheduled for the next run.

All jobs that are scheduled on March 11 between 12 AM to 1:30 AM are not running.

They are either moved to the Missed Start state or rescheduled for the next run.

This happens when the DST patch is installed on March 11 between 1 PM to 3 PM.

Workaround:

Install the DST Patch available on Cisco.com well before the DST observance.

CSCsj04917

After the port number change in DCR Slave Server, the DCR configuration file is not updated.

In a Multi-Server setup, if you change the port number of DCR Slave Server, this is not updated in the DCR configuration file.

This problem persists although you regenerate the certificate.

Because of this:

CiscoWorks Assistant does not work properly in a Multi-Server setup.

Servers and Applications Portlet does not launch in Standalone or Master-Slave setup. Instead this displays an error message.

Workaround:

None.

CSCsj82286

Devices added in DCR are not displayed in Device Selector although they are added in ACS.

In ACS mode, devices added in DCR are not displayed in Device Selector although they are added in ACS.

This is because you added the devices after restarting ACS services in ACS.

This problem occurs only on ACS 4.0 servers.

Workaround:

Either:

Restart the Daemon Manager in CiscoWorks Server.

Or

Upgrade the ACS 4.0 software to later versions.

CSCsk19197

Correct set of SNMP credentials are not updated in DCR after Device
Discovery.

Correct set of SNMP credentials are not updated in DCR after
successful completion of a Device Discovery cycle.

This happens if you:

1. Configure incorrect SNMP credentials in DCR.

2. Configure correct set of SNMP credentials in the Device Discovery Settings screen.

3. Select the Use DCR As Seed List option for Seed Devices Settings.

Because of the incorrect SNMP credentials in DCR, CiscoWorks applications cannot perform the operations on network devices.

Workaround:

In this release, Common Services Device Discovery does not run if the SNMP credentials configuration in DCR is incorrect.

CSCsk44028

In a Single Sign-On (SSO)
multi-server setup, when you launch a SSO Slave Server, it displays a HTTP Status error.

In a Single Sign-On (SSO) multi-server setup, when you launch a SSO Slave Server, it displays the following error:

HTTP Status 500 Error

This problem occurs when you enter a Fully Qualified Domain Name (FQDN) of the SSO Master during the SSO Slave Server
configuration.

Workaround:

None.

CSCsk84471

Exporting a report to a file of PDF format generates a PDF document with white spaces and blank pages.

When you export a report to a file of PDF format, the PDF document is generated with white spaces and blank pages.

This problem occurs with all types of reports such as Tabular Reports, Stacked Table, and Stack of Stacked Table reports.

Workaround:

None.

CSCsk86433

Scheduled periodic jobs do not run after restarting Daemon Manager.

When a scheduled periodic job is running, if you restart the Daemon Manager, the next instance of the scheduled job does not run.

Workaround:

None.

CSCsk86609

Software Center jobs that are backed up from the earlier versions, do not run after you restore them in Common Services 3.1.1 server.

Software Center jobs that are backed up from earlier versions of Common Services do not run after you restore them.

This problem occurs when data is backed up from earlier version of CiscoWorks installed in a non- default (other than NMSROOT) location.

This is because the Software Center jobs are registered with absolute path in the earlier versions.

Workaround:

None.

CSCsl13291

Some of the SNMP properties are not migrated from Campus Manager Device Discovery to Common Services Device Discovery

The following SNMP properties are not migrated from Campus Manager Device Discovery to Common Services Device Discovery.

snmp.getBulkSize

snmp.threadmin

snmp.threadmax

Workaround:

Common Services Device Discovery already contains these properties and do not depend on Campus Manager for discovery.

Configure the values for these properties for better discovery performance.

CSCsh36085

Tomcat logs are not rotated properly.

The following Tomcat logs are not rotated properly.

stdout.log

stderr.log

Some of the contents of log files are missing after the restart of daemons.

Workaround:

None.

CSCsk15483

Any errors occurring during the
configuration of seed devices are not displayed in the user interface.

Any errors occurring during the configuration of seed devices are not displayed in the user interface.

This problem occurs when you selected the Seed Devices From a File option.

Workaround:

None.

CSCsk46142

The Job Details popup window for DCR jobs displays wrong start time.

In Common Services Job Browser page, when you click a DCR job to view the details, the Job Details popup window does not display the correct start time.

This problems occurs when you schedule DCR jobs before installing the DST patch.

Workaround:

None.

CSCsk55579

Problem occurs in daily job schedules before and after the DST patch installation.

All daily jobs that are scheduled after applying the DST patch are advanced by an hour and the jobs that are scheduled before applying the patch are postponed by an hour.

Workaround:

None.

CSCsk57503

Daily jobs scheduled in the DST timings as the second instance, run as the first instance.

Daily jobs that are scheduled in the DST timings to run as the second instance do not run. Instead they run in the first instance.

Workaround:

None.

CSCsg62980

Backup and Restore operations are unsuccessful when Cygnus mount points exist on the CiscoWorks machine.

Backup and Restore operations are unsuccessful when Cygnus mount points exist on the CiscoWorks machine.

This problem occurs when the following software which ships cygwin DLLs for Windows, is installed on the CiscoWorks server:

Third-party OpenSSH for Windows

Cygwin software

IBM Tivoli Backup Manager

Workaround:

1. Uninstall the third-party OpenSSH, IBM Tivoli Backup Manager, and other third-party software which ships Cygwin DLLs for Windows, reboot, and re-attempt upgrade.

2. Uninstall Cygwin DLLs.

3. Remove the mapping of "/" mount point from the Windows
registry. You must backup the registry before doing this.

CSCsl28279

There is no provision to restrict crossing Router boundaries during Common Services Device Discovery.

There is no provision to restrict crossing Router boundaries during Common Services Device Discovery.

Workaround:

None.


Known Problems in Campus Manager

Table 3 lists the known problems in Campus Manager 5.0.2.

Table 3 Known Problems in Campus Manager 5.0.2

Bug ID
Summary
Explanation

CSCsk65566

UTU 1.1.1 is not supported on Windows Vista software.

UTU 1.1.1 is not supported on Windows Vista software.

Workaround:

None.

CSCsk82957

Schedule Jobs for IP Phone report do not complete as expected.

This problem occurs when:

1. Campus Manager is managing 5,000 devices on a single server.

And

2. Two IP Phone jobs are scheduled to run at the same time.

Workaround:

None.

CSCsl14784

Exporting reports to CSV and PDF does not work in Campus Manager.

This problem occurs on Microsoft Internet Explorer 7.0 browsers.

Workaround:

None.


Known Problems in Resource Manager Essentials

Table 4 explains the known problems in RME 4.1.1

Table 4 Known Problems in RME 4.1.1 

Bug ID
Summary
Explanation

CSCsj83936

Check Device Attributes (CDA) job fails when you schedule it with only SNMP Read Write Community credentials.

This occurs when you schedule a CDA job with DCR credential without providing any value for SNMP Read community but providing a value for SNMP Read Write community.

The job fails with an error message.

Workaround:

None.

CSCse50395

RCP fails on IGESM and AP1231 device.

This occurs when you:

1. Set RCP as the config fetch and deploy protocol for Archive management.

2. Schedule a job to deploy some configurations on IGESM or AP1231 device

The job fails.

RCP manual copy also fails on IGESM or AP1231 device

Workaround:

Use protocols other than RCP.

CSCsk98607

Image name not shown completely in the Image options drop down during Software Image distribution.

This occurs when you:

1. Go to RME ->Software Management-> Software Distribution.

2. Select the Distributes by devices option.

3. Select a device.

4. Click Next.

The Image option drop down lists all the images available in the repository.

If the image name is too long, you can only view the image name partially.

Workaround:

This scenario occurs only in Internet Explorer. The image name is displayed completely if viewed using Firefox.

CSCsk90127

Inventory Custom Report fails when the first and the second conditional parameters in the query expression does not consist of user-defined fields.

This occurs when you:

1. Go to RME > Reports > Report Generator.

2. Schedule an Immediate report job with a custom query expression comprising of Common Services user-defined fields.

The job fails with a following error:

INVREP0026: Could not get data from database. Check the log for more details.

This is observed when the user-defined field is neither the first nor the second conditional parameter in the query expression.

Workaround:

This error does not occur when the query expression consists of user-defined fields in the first and the second conditional parameters.

CSCsl13374

Restore does not happen for CAT 2900 or CAT 3750 non-IOS devices after software image upgrade.

This occurs when you:

1. Backup the configuration for CAT 2900 or CAT 3750 non-IOS devices.

2. Perform image upgrade for this device using RME Software Management.

During upgrade of the image, vlan.dat and config.txt are deleted.

3. After image upgrade, restore the backed up files on to the device.

Restore is successful only for successful distribution jobs and not for failed jobs.

Workaround:

RME Software Management copies the backed up files onto the respective job directory in the RME server. You can restore them manually from that directory.

CSCsl34149

Contract Connection report generation fails sometimes if there are many device types.

Sometimes Contract Connection report generation fails if you have selected many device types.

Workaround:

Either:

Generate multiple reports with less number of device types in batches.

Or

Generate report with less number of device types, using the System-defined Group options.

CSCsk92778

Adhoc template fails for PIX device in the multi-context mode

This occurs when you:

1. Go to NetConfig > NetConfig Jobs

2. Click Create, to create a new NetConfig job.

3. From the Device Selection pane, select a PIX 7.x device, which is in multi-context mode.

4. Select an Adhoc template from the right pane.

5. Click Next

The Add Tasks dialog box appears.

6. Click Add Instance to add an instance

The Adhoc Configuration dialog box appears.

7. Enter the following command in CLI Commands text area.

copy tftp flash<R>10.77.212.123<R>test.txt<R>pdm-test

8. Check the Enable Command mode.

9. Select System as the context.

10. Click Save.

An Instance is added.

11. Click Next.

The Job Schedule and Options dialog box appears.

12. Schedule an Immediate NetConfig job.

The job fails with the following error message:

Command(s) failed on the device Insufficient no. of interactive responses(or timeout) for command: copy tftp flash. Insufficient no. of interactive responses(or timeout) for command: copy tftp flash

Workaround:

None.


.

Known Problems in Internetwork Performance Monitor

This section explains the known problems in IPM 4.0.1:

Table 5 Known Problems in IPM 4.0.1

Bug ID
Summary
Explanation

CSCsi28776

Changing the display name of a target device in DCR does not change the name of the associated Collector.

This happens when you:

1. Access a IPM target device in Device Credential Repository (DCR).

2. Change its Display Name

The name change gets reflected in Device Selector and target HOS. But the change to the target device display name does not reflect in the name of the Collector that was already created.

This is because IPM appends the target display name while naming a Collector.

Workaround:

None.

CSCsk26585

Restore of IPM 2.6 data consisting of statistical data for more than 20 days onto IPM 4.0.1 takes more time.

This happens when you:

1. Backup IPM 2.6 data which consists of statistical data for more than 20 days.

2. Install IPM 4.0

3. Install IPM 4.0.1

4. Restore the IPM 2.6 data into IPM 4.0.1

The Restore operation takes more time.

After sometime a message appears that the Restore was successful.

The Restore operation takes more time typically when the backed up data consists of statistical data of more than 20 days.

Workaround:

None.

CSCsk97954

While migrating data from IPM 2.x to IPM4.0.1, the Licence check is done only for Collectors but not for devices.

With an evaluation licence of IPM 4.0.1, restore a IPM 2.x backup with 1000 collectors and 500 devices.

Only 330 collectors get migrated and 500 devices come in to IPM space instead of the evaluation license limit of 110 devices.

Workaround:

None.

CSCsl00127

Irregular polling occurs when there are more Collectors created in a source, and that source is not in a responding state in a 5,000 Collector setup.

If you have a large number of collectors created in a source and the source is not in a responding state during polling, IPM retries to reach the device for each Collector in that source.

The delay in reaching the unresponsive device affects the polling of collectors created in other sources.

Workaround:

Reduce the default SNMP retries and timeout in IPM space.

CSCsk13949

The source device reflects a Source Not Responding state even when the associated Collectors are running.

These conditions occur when, for instance a device, dev1 is not reachable or responding and:

Collectors are created on dev1 and these Collectors move to Source Not Responding state.

These Collectors remain indefinitely in the Source Not Responding state.

A Collector on dev1 is edited and the device is not reachable or responding.

During that time the Collector moves to Source Not Responding state and gets stuck in that state.

Collectors are reconfigured on dev1 because the process has been restarted and if the device is not reachable or responding.

At this situation, the Collectors move to Source Not Responding state and remain in Source Not Responding state forever.

Stopped Collectors on dev1 (which is not reachable or responding) are started.

Such Collectors move to Source Not Responding state and remain indefinitely in the Source Not Responding state.

Operations are edited.

When Operations are edited, the Collectors on dev1(which is not reachable or responding) are also edited and reconfigured.

Then those Collectors are moved to Source Not Responding state and remain indefinitely in the Source Not Responding state.

Workaround:

Create a Collector for the source device when it is reachable.

This checks all collectors for their failure conditions and move them to appropriate states.

CSCsi42099

Scheduled reports shows as Failed after running dbRestoreOrig.

This happens if the existing reports are not cleaned up after running dbRestoreOrig.

Because of this, the reports and the scheduled jobs move to a Failed status on the Historical Reports and Report Job Browser pages.

Workaround:

After running the dbRestoreOrig, delete all the files and subdirectories from the following archive folder:

$PX_DATA_DIR/ipm/archives

where $PX_DATA_DIR represents NMSROOT/files.

CSCsi85216

Hostname or IP address or Domain name changes do not reflect in the Collector list in some scenarios.

These are the scenarios in which the Hostname, IP address or Domain name changes do not reflect in the Collector list:

Scenario 1:

Change the source hostname into an invalid hostname.

These changes are not reflected in the Collector list.

Scenario 2:

Change the Source IP into Invalid or Not Reachable IP.

These changes are not reflected in the Collector list.

Scenario 3:

Change the hostname into IP address.

These changes are not reflected in the Collector list.

Scenario 4:

Change the IP address into a hostname.

These changes are not reflected in the Collector list.

Scenario 5:

Change the domain name.

These changes are not reflected in the Collector list.

Workaround:

None.

CSCsj73992

Constant rise in memory for
IPMDbEngine process when there are more number of Collectors spread across many source devices.

For example:

There are 2000 Collectors that are spread across 10 source devices, there is constant rise in memory for IPMDbEngine process.

Workaround:

None.

CSCsk96639

Sometimes, two Collectors are shown with same admin index in the server when bulk Collectors are created on a source device.

This problem occurs when you:

1. Create around 200 Collectors on a source device.

The source device shows that 199 Collectors were created but the server shows that there were 200 Collectors created.

2. Run the following query:

select adminindex from Collector where SourceAddress='10.77.209.67' order by adminindex

The output of the query shows that there are two Collectors with same admin index in the server.

Workaround:

None.

CSCsk65557

Search does not work properly for adhoc devices.

IPM Search does not work properly when:

There are more than one asterisk(*) symbols provided in the search criteria

Example:

10.77.*.*

The asterisk symbol is provided in between two numbers in the search criteria

Example:

10.*.203.110

10.*7.203.110

10.77.203*0

The asterisk symbol is provided in between two characters in the search criteria

Example:

bun*pc9,

b*9

Workaround:

None.

CSCsk51878

The dbsrv9 service creates core dump after few days of upgrade from IPM 4.0 to IPM 4.0.1

This problem occurs when you:

1. Install IPM 4.0

2. Create a large number of collectors, say 2000.

3. Upgrade to IPM 4.0.1 after few days.

After few days, dbsrv9 service creates a core dump.

The IPMProcess and IPMDbEngine processes go down due to the core dump creation.

Workaround:

None.

CSCsk96283

Poll period in reports not matching buckets on devices when daemons are restarted.

This problem occurs when you:

1. Configure a collector in a device

2. Ensure the device collects and stores the data in a bucket at time:

1:30 pm

2:30 pm

3:30 pm

4.30 pm and so on.

Also ensure that IPM polls the source device at:

1.30 pm

2:30 pm

3:30 pm

4:30 pm and so on.

3. Restart the daemons at 3:45 pm

The IPM polling time changes to:

1:30 pm

2:30 pm

3:30 pm

4:45 pm

5:45 pm and so on.

This polling time also reflects in the Hourly reports and does not match with device collection and storing time.

Workaround:

None.


Known Problems in Device Fault Manager

This section explains the known problems in Device Fault Manager 3.0.2:

Table 6 Known Problems in Device Fault Manager 3.0.2 

Bug ID
Summary
Explanation

CSCsl11291

DFM may not co-exist with Install Shield 2008 software.

When InstallShield 2008 is installed on a DFM 3.0.2 Server, DfmServer process is up and running. However, it creates an empty DFM.log and the device addition hangs at 10%.

If you uninstall InstallShield 2008, DFM will start functioning normally.

Workaround:

None.

CSCsf16249

Polling and Thresholds View button displays an error message.

Clicking on the View button under polling parameters or Managing thresholds, displays the following message instead of showing the parameters:

The selected group has no devices. Please select a group with devices.

Workaround:

None.

CSCsh50211

Cannot manage Interface with
8 bit character description.

When a managed device has an Interface description using International characters and you open a DDV, an Internal Server Error or an error message is displayed.

Workaround:

Change Interface description to 7 bit character set and rediscover the device.

CSCsi01966

SNMP timeout occurs on rediscovering the learning devices at 40%

During Rediscovery, the devices goes to Questioned state displaying the following message in the Rediscover/Delete page.

Data Collector timeout request

This happens only in a Solution server with 5,000 devices where DFM is installed with other LMS applications. This does not occur in a Standalone DFM system.

Workaround:

None.

CSCsi65339

After Rediscovery, the device status changes from Known to Questioned.

After manual or automatic Rediscovery, two 7206VXR routers are displayed to be in Questioned states although they are in Known state.

Workaround:

Disable automatic DCR synchronization, delete affected devices from DFM, and manually add them again.

CSCsi85221

IPCC Express device gets into Unsupported state in DFM - CUOM.

IPCC Express device getting into Unsupported state in DFM with Qualified Access Address Not Found in CUOM.

The device does not have any IP address in managed state. An EMC Smarts case has been raised for this bug.

Workaround:

None.

CSCsk33199

DFM adds alias devices when an alias has a DNS resolvable IP address.

DFM treats alias device as a different device.

This problem occurs when a device has more logical IP addresses and some of them are DNS resolvable.

When all the IP addresses are added, DFM does not treat them as alias (duplicate) devices.

Workaround:

None.

CSCsk34630

DFM discovers devices with wrong SNMP credentials.

When SNMP credentials of a device are changed in DCR, DFM still discovers the device although they have wrong credentials.

DCR passes the correct credentials but DFM uses the old ones.

Workaround:

None.

CSCsk34741

DFM does not handle SNMP retries properly.

DFM does not handle SNMP retries properly although you have configured the device for default retries (3 times).

This problem occurs when you enter wrong SNMP credentials.

Workaround:

None.

CSCsk38554

DFM does not support managing devices with SNMPv3 NoAuthNoPriv mode.

DFM does not support managing devices with SNMPv3 NoAuthNoPriv mode. It displays a message that the credentials are insufficient.

Workaround:

None.

CSCsl20205

Updated fault history tasks are not available for CiscoWorks roles in ACS.

Updated fault history tasks are not available for CiscoWorks roles in ACS.

Group/Device Filtering and Alert/Event ID Filtering tasks are not included and SearchAlert, SearchDevice, SearchGroup, and SearchEvent tasks are not removed from Fault History.

In Device Management, Device Selector task is not replaced with Device Import, and Device Reports task is not replaced with Device Details.

Workaround:

None.

CSCsk10099

DFM is not able to receive traps in remote integration with Netview7.1.5.

This problem occurs when you:

1. Install Netview 7.1.5 before installing CiscoWorks.

Ensure that Netview and CiscoWorks (Common Services + DFM adapters) are in different locations.

2. Check if all the netview processes are up and running.

3. Configure any device to send traps to 162 port where Netview listens.

4. Check if the configured traps are seen in Netview and DFM.

Traps are seen in Netview, but not in DFM.

Workaround:

None.

CSCsl45641

Wrong message is displayed during restoring the DFM data on a CiscoWorks Server.

When you restore the backed up DFM data on a DFM 3.0.2 Server, the following message is displayed:

Failed to stop Daemon ManageR. Try stopping from Command Line.

Workaround:

Ignore this message and continue. No functionality is affected in DFM after data restore.


Known Problems in CiscoView

Table 7 describes problems known to exist in CiscoView 6.1.7. Table 8 describes problems known to exist in CiscoView Mini-RMON Manager 3.1.

Table 7 Known Problems in CiscoView 6.1.7 

Bug ID
Summary
Explanation

CSCsa30779

Selected port/module is not completely highlighted.

This problem occurs when you:

1. Launch CiscoView in Netscape Navigator and open the chassis view for either a Catalyst 3750 or 6000 device.

2. Click either a module or port to select it.

Only the left side of the selected module/port is highlighted by a yellow border.

This problem does not occur in Internet Explorer.

Workaround:

None.

CSCse83768

Error occurs after launching Stack View for a device on both Windows XP and Windows 2003 clients.

This problem occurs when you:

1. Launch StackMaker (right-click the chassis view for a device and then select StackMaker).

The Stack Management Of device's IP address dialog box appears.

2. Click Stack View.

The following error message appears: Callback is null or not an object.

After clicking OK to close the error message, CiscoView displays the device stack.

Workaround:

None.

CSCsb87420

Error sometimes occurs while configuring a device.

A null point exception error sometimes occurs after making a configuration change to a device within CiscoView.

Workaround:

None.


Table 8 Known Problems in CiscoView Mini-RMON Manager 3.1 

Bug ID
Summary
Explanation

CSCsa94018

Pages and dialog boxes do not display any data after device goes down.

This problem occurs when you:

1. Launch CiscoView Mini-RMON Manager.

2. Select a new application page or refresh the current one.

If the device being monitored goes down before a new page is opened or the current page is refreshed, all subsequent pages and dialog boxes will display no data.

No message appears indicating that the device is down.

To get confirmation that the device is down, close the current session and then open a new one for that device.

Workaround:

None.

CSCsb07793

Sometimes Device Selector does not work as expected.

This problem occurs when you:

1. Launch multiple CiscoView Mini-RMON Manager sessions.

2. Expand a folder in the Device Selector of an open session by clicking the plus sign beside it.

Sometimes, instead of the folder expanding, the Device Selector tree collapses and displays only the main folder.

After you expand the main folder, the expandable folders beneath it display a minus sign instead of a plus sign.

Workaround:

Click the minus sign for an expandable folder. A plus sign is displayed and the Device Selector works as expected.

CSCsb00192

Browser's status bar does not indicate that the creation of a new alarm is complete.

This problem occurs when you:

1. Click the Setup tab.

2. From the Options bar, click Alarms.

3. From the Setup Alarm Thresholds page, click Create.

4. Enter the necessary information and then click OK.

A new alarm is created, but the status bar continues to indicate that the process is still running.

Workaround:

Launch another page or click an action button.

CSCsb05750

Cannot enable statistics collection on some devices.

An error message is displayed when you attempt to enable statistics collection on the following devices:

Catalyst 2970-24TS

Catalyst 3550-24MMF

Catalyst 3750

Catalyst 4948

For more information, see the corresponding SNMP agent problems:

CSCin93032, CSCin93030, CSCin93028, CSCsb05787, and CSCef19988.

Workaround:

Enable statistics collection using the CLI (this does not apply to Catalyst 4948 devices).

CSCsc00802

Statistics collection and History features are not supported by some devices.

The following devices do not support the Statistics collection and History features in CiscoView Mini-RMON Manager 2.0:

Cisco 2800 Series Integrated Services Routers: Cisco 2801, Cisco 2821, Cisco 2851

Cisco 3800 Series Integrated Services Routers: Cisco 3825, Cisco 3845

Cisco 2600 Series Multiservice Routers: Cisco 2610, Cisco 2610XM, Cisco 2611, Cisco 2611XM, Cisco 2612, Cisco 2613, Cisco 2620, Cisco 2620XM, Cisco 2621, Cisco 2621XM, Cisco 2650, Cisco 2650XM, Cisco 2651, Cisco 2651XM

Cisco 3600 Series Multiservice Routers: Cisco 3620, Cisco 3631Co, Cisco 3640, Cisco 3660, Cisco 3662Dc, Cisco 3662Ac, Cisco 3662AcCo, Cisco 3662DcCo, Cisco 3661Ac, Cisco 3661Dc

Cisco 3700 Series Multiservice Access Routers: Cisco 3725, Cisco 3745

Cisco IAD2400 Series Integrated Access Devices: Cisco 2420 IAD, Cisco 2430-24Fxs IAD, Cisco 2431-8Fxs IAD, Cisco 2431-16Fxs IAD, Cisco 2431-1T1E1 IAD, Cisco 2432-24Fxs IAD

Workaround:

None.


Known Problems in CiscoWorks LMS Portal

Table 9 describes the known problem in LMS Portal 1.0.1.

Table 9 Known Problem in CiscoWorks LMS Portal 1.0.1

Bug ID
Summary
Explanation

CSCsk76372

Remote portlet links do not launch the remote server from a Windows Vista client systems.

This is because the domain name for the remote server is not resolved with the client server.

The remote portlet is configured from some intermediate server without any domain name issue. Hence the client browser is not able to connect to the remote server because its domain name is not resolved.

Workaround:

None.

CSCsj72270

In 2:1:2 - 1 Layout, dropping a portlet to third column for the first time does not display the shaded region.

In 2:1:2 - 1 Layout, when you drop a portlet to third column for the first time, shaded region does not appear to indicate the arrow.

This results in difficulty to drop the portlet.

This problem is because of a bug in Liferay engine.

Workaround:

None.


Known Problems in CiscoWorks Assistant

Table 10 describes the known problem in CiscoWorks Assistant 1.0.1

Table 10 Known Problem in CiscoWorks Assistant 1.0.1

Bug ID
Summary
Explanation

CSCsj05479

CiscoWorks Assistant does not work after the port change in DCR Slave server.

In a multi-server setup, if you change the port number of the Slave server, CiscoWorks Assistant does not work properly.

This is because the port change does not get reflected in the DCRMaster.

Workaround:

1. Change DCR mode of the Slave server (after port change) to Standalone.

2. Add the following line in the dcr.ini file of the Slave:

PREVIOUS_DCR_GROUP_ID = Master's DCR_GROUP_ID

where, Master's DCR_GROUP_ID is the value of DCR_GROUP_ID from the dcr.ini file of the Master.

3. Change the DCR mode of the Standalone server back to Slave. This operation might result in data loss.

CSCsj05096

Severe error occurs while installing LMS 3.0.

This problem occurs when you:

1. Uninstall CiscoWorks from the Windows Server.

2. Install LMS 3.0 in the same server in Custom mode in a non-default location (location other than NMSROOT).

The following severe error message appears after 85% completion of installation.

StartService: Operation completed successfully

Workaround:

Use the latest Cleanup script after uninstalling LMS 3.0.

CSCsj17702

GGScript is using 97% CPU on a LMS 5,000 devices server.

On a LMS 5,000 devices server, the task bar displays the following message although no CiscoWorks Assistant specific operations are performed:

GG script ia using 97% CPU

Workaround:

None.

CSCsl11359

Severe error occurs while uninstalling CiscoWorks.

While uninstalling CiscoWorks, the following error appears:

CSCOpx\objects\wfengine\Program\xerces-c_2_2_0.dll Access denied.

This is because many CiscoWorks Assistant processes are running on the server.

Workaround:

Use the latest Cleanup script after uninstalling LMS 3.0

CSCsl00079

While installing LMS 3.0, the Failed to execute the Setup program error occurs.

This problem occurs when you:

1. Uninstall CiscoWorks from the Windows Server.

2. Install LMS 3.0 in the same server.

The following severe error message appears after 85% completion of installation.

Failed to execute the Setup program

Workaround:

Use the latest Cleanup script after uninstalling LMS 3.0 every time.

CSCsl72562

CiscoWorks Assistant Workflows do not launch on a Solution server with 5,000 devices after data restore.

After restoring the data in a Solution server that manages 5,000 devices, CiscoWorks Assistant Workflows do not launch.

This occurs on LMS servers in ACS mode and is because of the problem with Opsxml Engine.

Workaround:

Restart the following Opsxml related processes:

OpsxmlDbEngine

OpsXMLRuntime

ProcSysBus

CSCsq43443

Database communication fails and CiscoWorks Assistant publisher may not run properly.

OpsXML Database communication fails in CiscoWorks Assistant and the CiscoWorks Assistant publisher may not run properly.

This problem occurs because:

The database password may not be updated properly

The database password contains special characters

There is a version mismatch in CiscoWorks Assistant publisher

This problem occurs only on CiscoWorks Assistant 1.0.1 Windows systems.

Workaround:

1. Reset the database password on the server.

To do this, run the following command at the command prompt:

NMSROOT\bin\perl dbpasswd.pl dsn=opsxml npwd=new_password

where:

NMSROOT is your CiscoWorks Installation directory.

new_password denotes the New database password.

2. Wait until all the CiscoWorks Assistant processes are started.

3. Run the CiscoWorks Assistant publisher (CWAPublisher.exe) on the command prompt.

The CiscoWorks publisher is located at NMSROOT\objects\wfengine\Program\TempFiles.

Contact the Cisco Technical Assistance Center (TAC) to know about the CiscoWorks Assistant publisher version.


Resolved Problems in LMS 3.0 December 2007 Update

This section contains:

Resolved Problems in Common Services

Resolved Problems in Campus Manager

Resolved Problems in Resource Manager Essentials

Resolved Problems in Internetwork Performance Monitor

Resolved Problems in Device Fault Manager

Resolved Problems in CiscoView

Resolved Problems in CiscoWorks LMS Portal

Resolved Problems in CiscoWorks Assistant

Resolved Problems in Common Services

Table 11 lists the problems resolved in Common Services 3.1.1.

Table 11 Resolved Problems in Common Services 3.1.1

Problem
Description
Additional Information

CSCsj52471

Incorrect Display Name was displayed when you registered the CiscoWorks applications from a remote server in the local server.

This problem has been resolved.

The local server now displays the correct Display Name of the remote server.

CSCsj58812

Software Center device and package maps were corrupted.

This was because multiple Software Center jobs were started before the completion of the previous jobs.

This problem has been resolved.

CSCsl09643

RME ConfigMgmtServer was stopped when SSH was used an a transport protocol.

This problem has been resolved.

The application process is not stopped now.

CSCsi01380

Support for Western Australia DST Time change was not provided.

This problem has been resolved.

The support for Western Australia DST Time change is now available.

CSCsi86050

Local applications were registered using hostname instead of Fully Qualified Domain Name (FQDN) on CiscoWorks Server.

Because of this, applications did not launch when accessed from a client machine that belonged to a different domain.

This problem has been resolved.

In this release, the local applications were registered using FQDN on CiscoWorks Server.

CSCsj85581

When performing a sync archive against the NAM devices, device prompt could not be learnt.

This problem occurred when Telnet or SSHv2 were used as Transport protocols.

This problem has been resolved.

A time delay is introduced before reading the data from the NAM devices.

CSCsk21026

Security vulnerability with Java Web Start was reported.

This problem has been resolved by applying the JRE 5.0 Update 12 or later releases.

CSCsj21268

The checkaddr.pl Perl script was no longer in use and should have been removed from the NMSROOT/bin location.

This problem has been resolved.

CSCsf99247

Special characters were not allowed in CiscoWorks username.

This problem has been resolved.

You can now include the following special characters in CiscoWorks username:

~ (Tilde)

@ (Commercial At character)

# (Number sign)

_ (Underscore)

' ( Apostrophe)

- (Hyphen)

/ (Solidus or Leading slash)

\ (Trailing slash)

. (Period)

space (Non-breaking space)

CSCsg02531

New devices that were added to a device group after creating a recurring DCR Device Export schedule were not exported.

Only the devices which were present in DCR before creating a schedule were exported from DCR.

This problem has been resolved.

All new devices that are added after the creation of recurring scheduled jobs are now exported from DCR.

CSCsi10451

There was no option to add the hostname of devices in CiscoWorks Server during CiscoWorks—ACS integration.

If you entered the hostname in the IP Address field in ACS, device import in DCR failed.

This problem has been resolved.

In this release, the option to enter the hostname in the IP Address field in ACS Server is allowed.

If the AAA client (network device) added in DCR is resolvable by its DNS, the device is imported in DCR with its display name and IP Address.

Otherwise, the device is imported in DCR with its display name and hostname.

CSCsi35128

The ps -ef command displayed only the running processes. It did not display the process names.

This problem has been resolved.

The ps -ef output now shows process name for all the processes except Tomcat, ESS, Rmegatekeeper which call one more exec function in their script.

CSCsi35153

Could not view the processes of a specific state in the Process Management page.

This problem has been resolved.

The Process Management page now allows you to select a specific process state and view the details of only those processes.

CSCsi59949

CiscoWorks did not allow the login username to start with a number because of security limitations with Active Directory Server.

This problem has been resolved.

Now, you can configure the login username to start with a number in CiscoWorks.


Resolved Problems in Campus Manager

Table 12 lists the problems resolved in Campus Manager 5.0.2.

Table 12 Problems Resolved in Campus Manager 5.0.2

Bug ID
Summary
Additional Information

CSCsi60354

Campus Manager Topology Services did not detect the root bridge of an MST instance.

This problem has been resolved.

CSCsj25061

Campus Manager did not manage Tunnel interfaces.

This problem has been resolved.

CSCsj32292

Campus Manager Topology Maps displayed L2L3 Switch icons for neighbor devices.

This occurred only when there were neighbors connected to MSFC in Cisco Catalyst 6000 series device—MSFC setup in hybrid mode.

This problem has been resolved.

CSCsj42193

Campus Manager User Tracking did not track user names for Windows endhosts.

This problem has been resolved.

CSCsj47107

Path Analysis showed Error Messages, even if the trace between two devices was successful.

This problem has been resolved.

CSCsj87906

STP Visualizer computation failed when MST was configured.

This problem has been resolved.

CSCsj87927

When you tried to perform STP configuration for an MST instance, Campus Manager returned an empty device list.

This problem has been resolved.

CSCsj99740

When you tried to assign ports to a VLAN from a device in client mode, Campus Manager displayed an error message that the device did not support VPA(VLAN Port Assignment) operations.

This problem has been resolved.

CSCsk19211

Campus Manager did not discover routers running Hot Standby Router Protocol (HSRP), if they were unreachable during the Data Collection.

This problem has been resolved.

CSCsk39909

The debug log messages written by the SocketListener class in Dynamic User Tracking was not detailed enough to troubleshoot all problems.

This problem has been resolved.

CSCsk39910

When UTLite debugging was enabled, the status of the UTLITE engine was not printed in the log file, on reception of each packet. It was printed only when UTLITE started.

This problem has been resolved.

CSCsk39913

Certain debugging options for Dynamic User Tracking were not enabled through GUI.

This problem has been resolved.

CSCsk39916

While debugging UTLite, details such as User name, IP address and MAC address received from the incoming packet were not written to the log file. This blocked effective debugging of UTLite.

This problem has been resolved.

CSCsk40066

In Campus Manager 5.0, you could not launch Telnet or SSH for a device from Topology Services.

This problem has been resolved.

CSCsk77535

In Campus Manager 5.0, you could not launch SSH for a device from Topology Services.

This problem has been resolved.


Resolved Problems in Resource Manager Essentials

Table 13 lists the problems resolved in RME 4.1.1.

Table 13 Resolved Problems in RME 4.1.1 

Bug ID
Summary
Additional Information

CSCsi89107

During remote migration, the Restore operation failed when RME 4.0/4.0.x data was restored to RME 4.1 or RME 4.1.1 in a specific scenario.

This happened because the filebackup.tar file was extracted in the RME backup folder in addition to the Common Services extraction in NMSROOT, during the Restore operation.

A space crunch was caused because the size of the extracted data (RME under Backup Folder and Common Services under NMSROOT) exceeds the required space estimated by Common Services (Common Services under NMSROOT) during extraction.

The Restore operation failed because of this space crunch.

This problem has been resolved by removing the RME extraction logic and using the data extracted by Common Services.

CSCsd39567

In Image version, RME Software Management could not parse for FWSM.

This problem has been resolved.

The distribution of FWSM 3.1 images now happens smoothly without any errors.

CSCsd36547

CatOS image import from CCO reported Pass/Fail status as Pass.

When a CatOS image is imported into RME from Cisco.com, the Image Requirements column reported NA but the PASS/FAIL column reports Pass.

Now if the Image Requirements column reports NA, the PASS/FAIL column reports FAIL.

CSCsh89021

RME Software Management could not download multiple images from Cisco.com.

This problem has been resolved.

RME Software Management can now download multiple images from Cisco.com.

CSCsg73121

Contract Connection reports in RME appeared with inconsistencies.

This problem has been resolved.

The Contract Connection reports now appear as intended.

CSCse85024

If you used the Select All option to select 10000 devices in the Search Results tab of RME Device Selector, it took long time.

This problem has been resolved.

Now selecting 10000 devices using Select All option in Device Selector does not take much time.


Resolved Problems in Internetwork Performance Monitor

Table 14 describes the problems resolved since the last release of IPM.

Table 14 Resolved Problems in IPM 4.0.1

Bug ID
Summary
Additional Information

CSCsh59288

IP SLA probes were not deleted when IPM was uninstalled.

After uninstalling IPM, the IP SLA probes are now deleted from both the IPM server as well as the source router.

CSCsg62084

The values in the graphs were not plotted properly if more than one parameter has the same value.

The values in the graphs are now plotting properly even if more than one parameter has the same value.

CSCsi85402

PathEcho collectors took different paths to traverse from source to destination.

This problem has been resolved.

Now these paths are captured accurately in the reports.

CSCsi92859

IPM 2.5 back up folder was not migrated to temporary location.

During migration from IPM 2.5 to IPM 4.0, the ipm.env file settings are also getting migrated now.

CSCsj17761

JOS: Could not specify the End Date while creating new collectors.

In a JOS (Japanese Operating System), you can now specify the End Date while creating new collectors.

This problem occurred only in Internet Explorer and is solved now.


Resolved Problems in Device Fault Manager

Table 15 lists the problems resolved in DFM 3.0.2.

Table 15 Problems Resolved in  Device Fault Manager 3.0.2 

Bug ID
Summary
Additional Information

CSCsg28859

Search in the ACS device selector displayed devices not in ACS.

When the LMS server was integrated with ACS, a search in the DFM hierarchy listed all devices, those configured in ACS and also those not in ACS.

Now in DFM 3.0.2, Simple and Advanced search will result in displaying correct set of devices depending on the ACS mode.

CSCsh65478

An error occurred during a DFMOGSServer IP address range search.

In DFM 3.0, you can search using an IP range. If you specified a range including the third or fourth octet or both, for example 10.77.[0-255].[0-255].[0-255].[0-255], DFM displayed an Out of Memory error.

In DFM 3.0.2, the logic to determine the managed IP Address in the given range has been modified. The search can be completed successfully.

CSCsh87548

FireFox and IE: DDV values were not changed in UI.

If the underlying interface was in unmanaged state, and if you changed the ip from false to true from DDV will not respect the change.

This is resolved in DFM 3.0.2.

CSCsh91353

When an NOS group was edited, the number of devices shown was incorrect.

An incorrect number of devices was shown in the NOS Group window after the group was edited. Double the actual number of devices was displayed. This occurred whenever an edit was made.

Now, when NOS group is edited by selecting all device groups, it shows the correct device count.

CSCsi30667

A CARD description for most devices was not shown in DDV.

It has been resolved and the descriptions are shown for all the devices.

CSCsi35962

ASL ERROR was displayed in the DFM1.log.

No ASL errors are found in the DFM1.log.

CSCsi67159

Change in the certification of AP340 device.

The certification was changed in the device AP340 (SysOID:.1.3.6.1.4.1.9.1.379). Up to DFM 2.0.6, the TYPE in the certification was shown as ROUTER, after DFM 2.0.6, the TYPE in the certification was shown as SWITCH. Because of this change, the health components discovery and monitoring were lost.

It is now corrected and the device type is properly displayed as SWITCH.

CSCsi80384

Although the automatic synchronization was not set and you applied the Filter changes, DFM displayed that the operation (setting filters) was successful.

An incorrect popup message was displayed when you applied the Filter changes.

For example, in the Auto Import Filters screen, when you selected the Device Type Groups without enabling the automatic synchronization check box and clicked Apply, the following message was displayed:

Filter set successfully

Proper error messages are displayed now.

CSCsi81776

The DFM Device portlet displayed unauthorized devices.

The DFM Device Status portlet displayed unauthorized devices.

The logic has been modified. In ACS mode, the authorized devices are displayed.

CSCsi86801

DynAPIerror occurred in the Alerts and Activities Display when the device name of an unidentified trap was clicked.

When the device name of an unidentified trap was clicked in AAD, a DynAPIerror occurred. This was observed after upgrading from DFM 2.0.8 to DFM 3.0.

The passing variable to noddv() was not handled properly and is corrected now.

CSCsj01279

License check was not done for DFM settings in the Setup Center.

DFM specific links appeared in the Setup Center even after the expiry of license.

The class has been modified to include a check for license validity limit. Depending on the validity the links will appear now.

CSCsj20011

Debugging for low-level EPM, Adapter, and Notification operations were not enabled in the GUI.

Instead, individual properties files were edited and then daemons must be restarted.

This problem has been resolved.

Now the property file is getting updated properly for each and every logging level setting.

CSCsa98634

sm_nv_fwd did not run after installing DFM2.0 on a Windows machine with Netview.

This problem has been resolved.

sm_nv_fwd process is up after installing DFM 3.0 and DFM3.0.2, and traps are forwarded from netview to DFM.

CSCsd65361

Trap Recipients entries given after a duplicate entry was deleted.

This problem has been resolved.

In DFM 3.0.2, data after duplicate entry is not lost. It is able to recognize the duplicate host names properly and displays all the host names.

CSCsi52984

Notifications such as traps, syslogs, and e-mails sent from Device Fault Manager to external servers were delayed.

The overall delay varied depending on the number of events and alerts generated.

This occurred because of the delay in resolving the notification destination.

This also occurred when DNS was improperly configured or the notification destination did not an entry in either DNS or the DFM server's local hosts file.

This problem has been resolved.

Now the notifications are sent to external servers without any delay.

CSCsi92010

DFM limits e-mail sender address to only 40 characters during the configuration of E-mail Notification Subscription.

This problem has been resolved.

The e-mail sender address can now contain up to 50 characters.

CSCsk26935

DFM displayed an error when attaching the DFM in the DMCTL.

Cannot connect to DM Broker at dfm-qpm-pc15:9002/dmbroker. No process is connected to the specified location. Cannot connect to DM Broker. Could not attach to DFM.

This problem has been resolved.

In DFM 3.0.2, after changing the host name using the hostname change script, the DMCTL and DFM Broker is getting attached.

You should reboot the machine after running the script.

CSCsb76225

sm_nv_fwd does not run after Remote Netview Adapter installation on a machine where CiscoWorks is not installed.

This problem has been resolved.


Resolved Problems in CiscoView

None.

Resolved Problems in CiscoWorks LMS Portal

Table 16 lists the problems resolved in LMS Portal 1.0.1.

Table 16 Problems Resolved in CiscoWorks LMS Portal 1.0.1

Bug ID
Summary
Additional Information

CSCsj10667

When you clicked the device count in RME Hardware Summary or RME Software Summary portlet, an HTTP 500 Error was displayed.

This happened when the display name of the devices contained spaces.

This problem has been resolved.

Now the error is not displayed although the device display name contains spaces.

CSCsi96540

Some application portlets were missing in the Functional view after a remote migration.

This problem has been resolved.

All the application portlets now appear in the Functional View after a remote migration.

CSCsh59261

RME Hardware summary graph was not shown in Remote portlet.

This problem has been resolved.

You can view both the RME Hardware Summary

details and RME Summary graph when added as a Remote portlet.

CSCsg54946

When you configured any URL in IFrame
portlet and clicked Back, it launched in a full window.

This problem has been resolved.


Resolved Problems in CiscoWorks Assistant

Table 17 lists the problems resolved in CiscoWorks Assistant1.0.1.

Table 17 Problems Resolved in CiscoWorks Assistant 1.0.1

Bug ID
Summary
Additional Information

CSCsj30122

Device credentials were corrupted after configuring Default Credentials in the CiscoWorks Assistant Server Setup Workflow.Because of this, applications did not work properly.

For example, Resource Manager Essentials failed to archive configurations from devices, or deploy software images.

This problem has been resolved.

CSCsi91589

Device Troubleshooting workflow report displayed incomplete information when one of servers in a Multi-server setup was down or not reachable.

CiscoWorks Assistant could not interact with the LMS applications installed in servers that were unreachable or down, and fetched data only from the local server.

This problem has been resolved.

CSCsj12820

CiscoWorks Assistant did not display a warning message when one of the servers in a multi-server setup was not reachable.

This problem has been resolved.

In this release, the following warning message appears when any server in a multi-server setup is not reachable or when the daemon threads of any server is down.

Warning: Either one or more of the LMS servers in the multi-server setup is down or the System Identity credentials and Peer Server certificate are not configured correctly.

CSCsi91287

If you changed the Home page server name, it did not get reflected in CiscoWorks Assistant pages though it was reflected in the application pages and tabs.

This problem has been resolved.

CSCsh68984

The End Host or IP Phone port number was not displayed in Check Status in the
End Host/IP Phone Down report.

This occurred when you generated the report for the End Host or IP Phone that was not connected to any port or if the connected port was down.

This problem has been resolved.

CSCsj21410

CiscoWorks Assistant workflows did not work on Windows Servers running Japanese OS.

This problem has been resolved.

CSCsk19350

CiscoWorks Assistant Device Troubleshooting workflow and Endhost/IP Phone Down WorkFlow did not run after installing Campus Manager Incremental Device Update (IDU) 18 and Device Fault Manager IDU 18.

This problem has been resolved.

CSCsk45213

CiscoWorks Assistant did not support E-mail addresses that contained dashes or single quotes.

This problem has been resolved.

CSCsk98519

The Add Devices page of Server Setup workflow hung when there were duplicate entries for the seed devices in the device list.

This problem has been resolved.

CSCsj08841

The CiscoWorks Assistant did not launch after running the dbRestoreOrig.pl script.

This problem has been resolved.


Related Documentation

This section contains:

Related Documentation of LMS 3.0 December 2007 Update

LMS 3.0 Documentation


Note Although every effort has been made to validate the accuracy of the information in the printed and electronic documentation, you should also review the documentation on Cisco.com for any updates.


Related Documentation of LMS 3.0 December 2007 Update

Table 18 lists the documentation of LMS 3.0 December 2007 Update:

Table 18 LMS 3.0 December 2007 Update Documentation

Document Title
Available Formats
LMS 3.0 December 2007 Update Solution Level Documentation

Readme for CiscoWorks LAN Management Solution 3.0 December 2007 Update on Windows (this document)

On Cisco.com:

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

Readme for CiscoWorks LAN Management Solution 3.0 December 2007 Update on Solaris

On Cisco.com:

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

Supported Devices Table for CiscoWorks LAN Management Solution 3.0 December 2007 Update

On Cisco.com:

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

Common Services

User Guide for CiscoWorks Common Services 3.1.1

On Cisco.com:

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

Campus Manager

User Guide for CiscoWorks Campus Manager 5.0.2

On Cisco.com:

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

Resource Manager Essentials

User Guide for Resource Manager Essentials 4.1.1

On Cisco.com:

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

Internetwork Performance Monitor

User Guide for Internetwork Performance Monitor 4.0.1

On Cisco.com:

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

Device Fault Manager

User Guide for Device Fault Manager 3.0.2

On Cisco.com:

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

CiscoView

User Guide for CiscoView 6.1.7

On Cisco.com:

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

CiscoWorks Assistant

User Guide for CiscoWorks Assistant 1.0.1

On Cisco.com:

http://www.cisco.com/en/US/products/ps7212/products_user_guide_list.html

CiscoWorks LMS Portal

User Guide for CiscoWorks LMS Portal 1.0.1

On Cisco.com:

http://www.cisco.com/en/US/products/ps7198/products_user_guide_list.html


LMS 3.0 Documentation

Table 19 lists the documentation of LMS 3.0.

Table 19 LMS 3.0 Documentation

Document Title
Available Formats
LMS 3.0 Documentation

Installing and Getting Started With CiscoWorks LAN Management Solution 3.0

On Cisco.com:

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

Data Migration Guide for CiscoWorks LAN Management Solution 3.0

On Cisco.com:

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

Supported Devices Table for CiscoWorks LAN Management Solution 3.0

On Cisco.com:

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

Common Services

User Guide for CiscoWorks Common Services 3.1

On Cisco.com:

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

Release Notes for CiscoWorks Common Services 3.1 on Solaris

On Cisco.com:

http://www.cisco.com/en/US/products/sw/cscowork/ps3996/prod_release_notes_list.html

Release Notes for CiscoWorks Common Services 3.1 on Windows

On Cisco.com:

http://www.cisco.com/en/US/products/sw/cscowork/ps3996/prod_release_notes_list.html

Campus Manager

User Guide for CiscoWorks Campus Manager 5.0

On Cisco.com:

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

Release Notes for CiscoWorks Campus Manager 5.0 on Solaris

On Cisco.com:

http://www.cisco.com/en/US/products/sw/cscowork/ps563/prod_release_notes_list.html

Release Notes for CiscoWorks Campus Manager 5.0 on Windows

On Cisco.com:

http://www.cisco.com/en/US/products/sw/cscowork/ps563/prod_release_notes_list.html

Resource Manager Essentials

User Guide for Resource Manager Essentials 4.1

On Cisco.com:

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

Release Notes for CiscoWorks Resource Manager Essentials 4.1 on Solaris

On Cisco.com:

http://www.cisco.com/en/US/products/sw/cscowork/ps2073/prod_release_notes_list.html

Release Notes for CiscoWorks Resource Manager Essentials 4.1 on Windows

On Cisco.com:

http://www.cisco.com/en/US/products/sw/cscowork/ps2073/prod_release_notes_list.html

Internetwork Performance Monitor

User Guide for Internetwork Performance Monitor 4.0

On Cisco.com:

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

Release Notes for CiscoWorks Internetwork Performance Monitor 4.0 on Solaris

On Cisco.com:

http://www.cisco.com/en/US/products/sw/cscowork/ps1008/prod_release_notes_list.html

Release Notes for CiscoWorks Internetwork Performance Monitor 4.0 on Windows

On Cisco.com:

http://www.cisco.com/en/US/products/sw/cscowork/ps1008/prod_release_notes_list.html

Device Fault Manager

User Guide for Device Fault Manager 3.0

On Cisco.com:

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

Release Notes for Device Fault Manager 3.0 on Solaris

On Cisco.com:

http://www.cisco.com/en/US/products/sw/cscowork/ps2421/prod_release_notes_list.html

Release Notes for Device Fault Manager 3.0 on Windows

On Cisco.com:

http://www.cisco.com/en/US/products/sw/cscowork/ps2421/prod_release_notes_list.html

CiscoView

User Guide for CiscoView 6.1.6

On Cisco.com:

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

Release Notes for CiscoView 6.1.6

On Cisco.com:

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

CiscoWorks Assistant

User Guide for CiscoWorks Assistant 1.0

On Cisco.com:

http://www.cisco.com/en/US/products/ps7212/products_user_guide_list.html

Release Notes for CiscoWorks Assistant 1.0

On Cisco.com:

http://www.cisco.com/en/US/products/ps7212/prod_release_notes_list.html

CiscoWorks LMS Portal

User Guide for CiscoWorks LMS Portal 1.0

On Cisco.com:

http://www.cisco.com/en/US/products/ps7198/products_user_guide_list.html

Release Notes for CiscoWorks LMS Portal 1.0 on Solaris

On Cisco.com:

http://www.cisco.com/en/US/products/ps7198/prod_release_notes_list.html

Release Notes for CiscoWorks LMS Portal 1.0 on Windows

On Cisco.com:

http://www.cisco.com/en/US/products/ps7198/prod_release_notes_list.html


Notices

The following acknowledgements pertain to this software license.

OpenSSL/Open SSL Project

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

This product includes cryptographic software written by Eric Young (eay@cryptsoft.com).

This product includes software written by Tim Hudson (tjh@cryptsoft.com).

License Issues

The OpenSSL toolkit stays under a dual license, i.e. both the conditions of the OpenSSL License and the original SSLeay license apply to the toolkit. See below for the actual license texts. Actually both licenses are BSD-style Open Source licenses. In case of any license issues related to OpenSSL please contact openssl-core@openssl.org.

OpenSSL License:

© 1998-1999 The OpenSSL Project. All rights reserved.

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

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

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

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

4. The names "OpenSSL Toolkit" and "OpenSSL Project" must not be used to endorse or promote products derived from this software without prior written permission. For written permission, please contact openssl-core@openssl.org.

5. Products derived from this software may not be called "OpenSSL" nor may "OpenSSL" appear in their names without prior written permission of the OpenSSL Project.

6. Redistributions of any form whatsoever must retain the following acknowledgment:

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

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

This product includes cryptographic software written by Eric Young (eay@cryptsoft.com). This product includes software written by Tim Hudson (tjh@cryptsoft.com).

Original SSLeay License:

© 1995-1998 Eric Young (eay@cryptsoft.com). All rights reserved.

This package is an SSL implementation written by Eric Young (eay@cryptsoft.com).

The implementation was written so as to conform with Netscapes SSL.

This library is free for commercial and non-commercial use as long as the following conditions are adhered to. The following conditions apply to all code found in this distribution, be it the RC4, RSA, lhash, DES, etc., code; not just the SSL code. The SSL documentation included with this distribution is covered by the same copyright terms except that the holder is Tim Hudson (tjh@cryptsoft.com).

Copyright remains Eric Young's, and as such any Copyright notices in the code are not to be removed. If this package is used in a product, Eric Young should be given attribution as the author of the parts of the library used. This can be in the form of a textual message at program startup or in documentation (online or textual) provided with the package.

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

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

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

3. All advertising materials mentioning features or use of this software must display the following acknowledgement:

"This product includes cryptographic software written by Eric Young (eay@cryptsoft.com)".

The word `cryptographic' can be left out if the routines from the library being used are not cryptography-related.

4. If you include any Windows specific code (or a derivative thereof) from the apps directory (application code) you must include an acknowledgement: "This product includes software written by Tim Hudson (tjh@cryptsoft.com)".

THIS SOFTWARE IS PROVIDED BY ERIC YOUNG "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE AUTHOR OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT 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].