Readme for CiscoWorks LAN Management Solution 4.0€¦ · 4 Readme for CiscoWorks LAN Management Solution 4.0.1 OL-23862-01 What’s New in This Release Select Yes and click Apply

Readme for CiscoWorks LAN Management Solution 4.0.1

March, 2011, OL-23862-01

ContentsThis document provides instructions for downloading and installing CiscoWorks LAN Management Solution (LMS) 4.0.1. The document also provides information on the new features supported in LMS 4.0.1 and points you to the known problems in LMS 4.0.1.

This document has the following sections:

• Introduction

• What’s New in This Release

• Server and Client Requirements

• Installing CiscoWorks LAN Management Solution 4.0.1

• Upgrading to LMS 4.0.1

• Bugs

• Product Documentation

• Related Documentation

• Obtaining Documentation, Obtaining Support, and Security Guidelines

• Notices

Americas Headquarters:Cisco Systems, Inc., 170 West Tasman Drive, San Jose, CA 95134-1706 USA

Introduction

IntroductionCiscoWorks LAN Management Solution (LMS) provides powerful features that enable you to configure, monitor, troubleshoot, and administer Cisco networks. It also supports new Cisco technologies such as Identity, EnergyWise, Auto Smartports, and Smart Install.

LMS 4.0.1 simplifies the deployment, and manages the day-to-day configuration of the Cisco Medianet 2.1 solution. LMS provides workflows for setting up auto configuration, and for configuring location settings to aid the provisioning and tracking of Medianet endpoints such as digital media players (DMP) and IP video surveillance cameras (IPVSC).

What’s New in This ReleaseThe following are the new features in LMS 4.0.1:

• Medianet Dashboard

• Medianet Endpoints Connected Group

• Port and Module Groups for Medianet

• Location Collection

• ASP Template Management

• Location Templates

• Medianet Reports

• Troubleshooting Medianet Endpoints

• Troubleshooting Workflow-related Enhancements

• Enhanced Search

• Third-Party Software and Tool Changes

Medianet DashboardThe Medianet dashboard provides a quick snapshot of the operational status of Medianet endpoints, and also the faults and configuration changes of Medianet devices that have Medianet endpoints connected to them. You can access the Medianet dashboard using My Menu > Default Dashboards > Medianet.

Using the Medianet dashboard, you can view the following portlets:

• Medianet Endpoint Status Across Locations

View a bar chart that displays the operational status of the Medianet endpoints grouped according to specific location attributes.

• Faults on Devices with Medianet Endpoints

View the faults that have occurred on devices with Medianet endpoints connected to them.

• Unreachable Medianet Endpoints

View details of the unreachable Medianet Endpoints, which are connected to Medianet devices.

2Readme for CiscoWorks LAN Management Solution 4.0.1

OL-23862-01

What’s New in This Release

The unreachable Medianet Endpoints include the following endpoints, after every User Tracking collection:

– Endpoints connected to the interfaces of the switch that are down.

– Endpoints missing on the interfaces of the switch that are up.

These endpoints were found in one cycle of User Tracking and were missing in the next cycle.

• Last N Config Changes on Devices with Medianet Endpoints

View the configuration changes on all the devices with Medianet endpoints after every inventory or configuration collection.

• Last N Connected Medianet Endpoints Portlet

View the following Medianet endpoints, during the last N specified time period:

– Endpoints connected to a switch or switch module.

– Endpoints that were down in the previous UT collection and up in the current collection.

For more information, see the Online Help.

Medianet Endpoints Connected GroupThis is a new system-defined device group to group all the devices connected with Medianet Endpoints (DMP and IPVSC).

To generate a Medianet Endpoint Inventory Report, select Reports > Technology > Medianet.

To deploy location attributes on ports, select Configuration > Tools > Template Center > Deploy.

Port and Module Groups for MedianetTwo new system-defined PMC groups have been introduced in LMS 401 for Medianet:

• DMP Ports —Contains all ports connected to DMP endpoints.

• IPVSC Ports—Contains all ports connected to IPVSC endpoints.

LMS 4.0.1 also allows you to define rules to create port and module groups using location attributes (Admin > System > Group Management > Port and Module). Some of the location attributes are Location.Floor, Location.House, Location.Place, and Location.City. For more information, see Defining Rule Expression for Port or Module Groups in Admin Online Help.

Location CollectionLMS can collect the location attributes configured on access layer ports to which Medianet endpoints are connected. You must enable the collection settings for location attributes to view details of the location attributes in the Medianet endpoint inventory reports.

By default the location collection settings are disabled, and you must enable the collection settings to be able to view details of the latest location attributes in the Medianet endpoint inventory reports.

To enable LMS to collect location attributes from the devices, select Admin > Collection Settings > Inventory > Location Collection Settings.


OL-23862-01


Select Yes and click Apply to enable the collection settings for location attributes.

Select No and click Apply to disable the collection settings for location attributes.

When you disable the Location Collection Settings, location attributes continue to be displayed in the Medianet inventory report. These attributes are based on the location settings collected earlier. However, you must enable Location collection to view the latest location attributes.

Note For the location collection of the Medianet devices, configure SNMPv3 AuthPriv credentials on the devices, and update these credentials in the Device Management page (Inventory > Device Administration > Add / Import / Manage Devices).

ASP Template ManagementLMS 4.0.1 provides Auto Smartports templates that allow you to group multiple Auto Smartports events and their associated macros. You can also define user-defined templates.

To manage ASP templates, select Work Centers > Auto Smartports > Manage Templates. You can select a template and deploy it on devices using Work Center > Auto Smartports > Configure > Auto Smartports. Using this workflow, you can auto configure the interface to which the Medianet endpoints are connected.

You can use ASP Management to edit the configuration for CDP-based events that are fetched from the device. To deploy MAC-based events or CDP-based events configuration, you can use Configure ASP flow (Work Center > Auto Smartports > Configure > Auto Smartports).

LMS 4.0.1 supports two types of system-defined templates:

• Cisco Standard Events

This template contains all the system-defined events and their associated system-defined macros.

• Cisco Medianet Template

This template contains only ASP events that are mapped to their corresponding system-defined macros, for DMP and IPVSC.

Location TemplatesThe Template Center (Configuration > Tools > Template Center) in LMS 4.0.1 provides both system-defined and user-defined location templates. Three new templates are available to facilitate configuration of location attributes on the Medianet-connected devices in your network.

You can also filter the templates based on the feature that they support.

You can export the system-defined template, modify it, import it and save it as a user-defined location template. The system-defined location templates that are available in LMS are:

• DMP Location Configuration—Configures location information on access ports that are connected to the Digital Media Player. This template is port-based.

• IPVSC Location Configuration—Configures location information on access ports that are connected to the IP Video Surveillance Camera. This template is port-based.

• Location Configuration—Configures location information on access ports that are connected to any endpoint. This template is port-based.


OL-23862-01


Medianet ReportsLMS 4.0.1 allows you to generate a Medianet Endpoint Inventory Report. To generate this report, select Reports > Technology > Medianet. This report provides information about the Medianet endpoints such as the subnets on which LMS has detected the endpoints, any state changes, and the number of discrepancies found associated with the port.

You can customize the Medianet endpoint inventory report with different layouts using Reports > Report Designer > Medianet Custom Layouts.

In LMS 4.0.1, you can use the new Inventory Group, CivicAddressLocation, to create a custom report template for Inventory. This Inventory Group contains various location attributes like City, Building, and Floor. To create a custom report template, select Reports > Report Designer > Syslog and Inventory Report Designer > Custom Report Templates.

Troubleshooting Medianet EndpointsTo troubleshoot Medianet endpoints, you can view the following details in the User Tracking portlet of the End Host troubleshooting workflow, along with the existing details:

• Type

Displays the type of Medianet endpoint. It can be Digital Media Player or IP Video Surveillance Camera.

• Location

Displays all the location attributes configured on the Medianet endpoints. You can customize the display of the location attributes using the medianet.properties file located at:

– For Windows-NMSROOT/lib/classpath

– For Solaris-NMSROOT\lib\classpath

For more details see, Customizing the Display of Location Attributes in the Work Centers Online Help.

For details on the enhancements in the Troubleshooting Workflow, see Troubleshooting Workflow-related Enhancements.

Troubleshooting Workflow-related EnhancementsIn LMS 4.0.1, the Troubleshooting Workflows (Monitor > Troubleshooting Tools > Troubleshooting Workflows) has the following enhancements:

• Port Status portlet

• Port Configlets

Port Status portlet

In LMS 4.0.1, the Port Status portlet provides more information about the port like:

• Discrepancies Found

Displays the number of discrepancies found associated with the port. If you click on the number it launches, the Discrepancies report.


OL-23862-01


• Best Practice Deviations Found

Displays the number of best practice deviations found associated with the port. If you click on the value it launches, the Best Practice Deviations report.

In the Port Status portlet, you can also use the Reset Port link to shutdown the port and then enable it. You can monitor the changes in the Change Audit report (Reports > Change Audit), if syslogs are enabled in the device. When you click the Reset Port link, the Inventory is triggered for the device, and the status is updated from MIB. Click the refresh icon in the portlet to get the data from database after a successful inventory collection.

Port Configlets

LMS 4.0.1 also provides new configlets to view the configurations on link ports. Each port has a separate configlet, which shows the CLI commands for particular services and features.

Enhanced SearchIn LMS 4.0.1, you can perform an attribute-based search for Device, Endhost and Job search types.

Here are the search patterns and their examples:

• <device attribute>=<value>. For example, managementip=10.77.108.21

• <job attribute>=<value>. For example, Jobid=1026

• <end host attribute>=<value>. For example, city=Chicago, or macaddress=01-36-6a-d7-02-05

There should be no blank space between the attribute type and the delimiter in the LMS Search text box

LMS also supports a number of search attributes for each search type.

Search Type Search Attribute

Device • displayname

• managementip

• deviceid

Note For the deviceid search attribute, you must give the exact value and search results will appear for the exact match.

• sysobjectid

• category

• series

• model

• hostname

Jobs • jobid

• description

• jobtype

• owner


OL-23862-01


End Hosts • macaddress

• ipaddress

• hostname

• username

• devicename

• vlanid

• device

30 location attributes are supported:

• state

• county

• city

• citydivision

• neighborhood

• streetgroup

• leadingstreetdirection

• trailingstreetdirection

• streetsuffix

• house

• streetnumber

• landmark

• additionalloc

• name

• zipcode

• building

• unit

• floor



OL-23862-01


You can also perform simple keyword and the results are displayed in a pop-up window as in LMS 4.0. You can do the following:

• Search for devices by entering the display name, IP address, or host name of the device as the search input.

• Search for jobs by entering the Job ID or Job description as the search input.

• Search for end hosts by entering MAC address, IP address, host name, or user name as the search input.

• Search for help topics by entering the help text as the search input.

• Search for a task by entering the task name as the search input.

End Hosts (contd.) • room

• place

• postalcommunityname

• postofficebox

• additionalcode

• seat

• primaryroad

• roadsection

• roadbranch

• roadsubbranch

• countrycode

• streetnamepremod

• streetnamepostmod

For more details, see Understanding the Search Bar section of the Getting Started Online Help.



OL-23862-01

Server and Client Requirements

Third-Party Software and Tool ChangesThe following are the changes in the third-party software and tools in this release:

• Support for Windows 2008 Standard Edition and Enterprise Edition Release 2

• Java Plug-in upgrade to 1.6.0_22

• Apache upgrade to 2.2.17

• Java Runtime Environment (JRE) 1.6.0_22

Server and Client RequirementsThis section contains:

• Client System Requirements

• Server Requirements on Solaris Systems

• Server Requirements on Windows Systems

• Operating System Requirements

• Firewall Updates to Avoid Denial of Service Attacks


OL-23862-01


Client System RequirementsThe following table lists the client system requirements for all platforms:

Table 1 Recommended Client Hardware and Software Requirements

Component Recommended Client System Requirement

Disk space Windows: 4 GB

Memory Requirements

1 GB RAM

Operating System

• Windows 2003 Standard and Enterprise Editions with SP 2 (32 and 64 Bit)

• Windows Server 2003 R2 Standard Edition with SP 2 (32 and 64 Bit)

• Windows Server 2003 R2 Enterprise Edition with SP 2 (32 and 64 Bit)

• Windows Server 2008 Standard Edition with SP1 and SP 2 (32 and 64 bit)

• Windows 2008 Server Standard Editions Release 2 (64 Bit)

• Windows 2008 Server Enterprise Edition Release 2 (64 Bit)

• Windows XP with Service Pack 3

• Windows 7 (32 and 64 bit)

Browser Requirements

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

• Internet Explorer 8.x

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

• Firefox 3.6.x for Windows

Note Only 32-bit IE and FF browsers are supported

Java Virtual Machine (JVM) Requirements

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


OL-23862-01


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

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

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

Table 2 Recommended Server Hardware Requirements on Solaris Systems

Component Recommended Server System Requirement

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

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

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

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

LMS 5,000

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

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

LMS 10,000

You need more than one servers to manage up to 10,000 devices,with all functions, in your network.

You must manage:

• Network Topology, Layer 2 Services and User Tracking, Fault Management, IPSLA Performance Management, and Device Performance management functions for upto 5,000 devices in another server

• Configuration and Image Management functions for upto 10,000 devices in one server.

Note You must disable other functions in the Config Server that is managing up to 10,000 devices.

For LMS Server managing Configuration functions for upto 10,000 devices only:

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

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

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


OL-23862-01


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

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

Table 3 Recommended Server Hardware Requirements on Windows Systems

Component Recommended Server System Requirement

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



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

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

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

LMS 5,000

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

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

LMS 10,000

You need more than one servers to manage up to 10,000 devices,with all functions, in your network.

You must manage:

• Network Topology, Layer 2 Services and User Tracking, Fault Management, IPSLA Performance Management, and Device Performance management functions for upto 5,000 devices in another server

• Configuration and Image Management functions for upto 10,000 devices in one server.

Note You must disable other functions in the Config Server that is managing up to 10,000 devices.

• For LMS Server managing Configuration functions for upto 10,000 devices only:

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

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

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


OL-23862-01


Operating System RequirementsThe operating system requirements are listed in the table below:

Table 4 Operating System Requirements

OperatingSystem Requirements

Solaris LMS 4.0.1 supports the following Solaris 10 releases:

• Solaris 10, 10/09 release






See Solaris Patches at:

http://www.cisco.com/en/US/docs/net_mgmt/ciscoworks_lan_management_solution/4.0/install/guide/prereq.html#wp1130208, for more information on Solaris patches to be installed on these Operating Systems.

For details on Solaris Zones, see Solaris Zones.

Windows LMS 4.0.1 supports the following Windows systems:

• Windows 2003 Standard Edition (SP2)

• Windows 2003 Enterprise Edition (SP2)

• Windows 2003 Standard Edition R2 (SP2)

• Windows 2003 Enterprise Edition R2 (SP2)

• Windows 2008 Server Standard Edition Release 1 with SP1 and SP2

• Windows 2008 Enterprise Edition Release 1 with SP1 and SP2

Note Both 32-bit and 64-bit Operating Systems are supported on the above versions.

• Windows Server 2008 R2 Standard Edition

• Windows Server 2008 R2 Enterprise Edition

Note Only 64-bit Operating Systems are supported on the above versions.

Note For installing LMS 4.0.x on Windows Server 2008 R2, you have to download and install the Windows 2008 R2 patch from: http://www.cisco.com/cisco/software/release.html?mdfid=283434800&flowid=19062&os=Windows&softwareid=280775103&release=4.0&rellifecycle=&relind=AVAILABLE&reltype=all.

See Installing CiscoWorks LMS 4.0.x Using Windows 2008 R2 Patch for more information.

To avoid Denial of Serice attacks, you must follow the steps in Steps to Avoid Denial of Service Attacks.


OL-23862-01

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


http://www.cisco.com/cisco/software/release.html?mdfid=283434800&flowid=19062&os=Windows&softwareid=280775103&release=4.0&rellifecycle=&relind=AVAILABLE&reltype=all



Solaris Zones

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

LMS 4.0.1 is installed on the global zone of Solaris 10 Operating System, by default. You can also install LMS in a whole-root non-global zone. Sparse root zone is not supported.

There is no specific hardware or software requirement for zone support. LMS works in the same way in non-global zones, as it works on the global zone.

Steps to Avoid Denial of Service Attacks

Immediately following installation, the TCP/IP stack should be hardened to avoid denial of service attacks. Ensure these steps are taken before using the product:

• Apply Windows security patches. See Microsoft Security Updates for Denial of Service Attacks for details. The system that you use for your LMS server should meet all security guidelines that Microsoft recommends for Windows 2003 or 2008 Server. See the NSA website for security guidance: http://www.nsa.gov.

• Specifically, the TCP/IP stack should be hardened to avoid denial of service attacks. Search for “Security Consideration for Network Attacks”, in “The Windows Server 2003 - Security Guide, v2.1” for download from this NSA URL. (This website is Copyright © 2011, Microsoft Corporation.)

• On the Windows Server 2003 Enterprise Edition or 2008 Standard or Enterprise Edition server, block remote access to all TCP/UDP ports except for those ports used by LMS for external access. See Firewall Updates to Avoid Denial of Service Attacks.

Firewall Updates to Avoid Denial of Service AttacksIf you have Windows Server 2003 or Windows Server 2008, use the following procedure to block remote access to all TCP/UDP ports, except for those required for external access by LMS.

Table 5 lists the ports used by the various LMS components.

Step 1 Open Control Panel for Windows Firewall.

Step 2 Select On to block all outside sources from connecting to this computer.

For exceptions, see the following steps:

Step 3 Select the Exceptions tab and select any services you may want to open for remote access.

For example, Remote Desktop or File and Print Sharing.

Step 4 Select the Advanced tab.

To add exceptions for an individual connection, select the network connection that is used for connecting external clients to this server and then click Settings.

Step 5 Click Add in the Advanced Settings window to enter your port exceptions.


OL-23862-01

http://www.nsa.gov


Step 6 In the Service Settings dialog, enter each of the ports used by the various LMS components (see Table 5) and click OK.

Repeat Step 6 until all ports are entered.

Step 7 Click OK in the Windows Firewall window to close it.

Step 8 Restart the server for the firewall settings to take effect, if required.

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

• HTTP or HTTPS port

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

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

Table 5 LMS 4.0.1 Port Usage

Protocol

Port Num-ber Service Name Functionality

Direction (of Establishment) of Connection

TCP 49 TACACS+ and ACS • Common Services

• Configuration and Software Image Management

• Network Topology, Layer 2 Services and User Tracking

• Fault Management

Server to ACS

TCP 25 Simple Mail Transfer Protocol (SMTP)

• Common Services (PSU)

• Inventory, Config and Image Management

Server to SMTP Server

TCP 22 Secure Shell (SSH) • Common Services,



Server to Device

TCP 23 Telnet • Common Services



Server to Device

UDP 69 Trivial File Transfer Protocol (TFTP)

• Common Services


Server to Device

Device to Server


OL-23862-01


UDP 161 Simple Network Management Protocol (SNMP)

• Common Services

• CiscoView




• IPSLA Performance Management

• Device Performance Management

Server to Device

Device to Server

TCP 514 Remote Copy Protocol Common Services Server to Device

UDP 162 SNMP Traps (Standard Port)



Device to Server

UDP 514 Syslog • Common Services

• Inventory, Config & Image Management

Device to Server

UDP 1431 Trap Listener to MAC Notification Traps

Network Topology, Layer 2 Services and User Tracking

Device to Server

UDP 9000 Trap receiving (if port 162 is occupied)

Fault Management Device to Server

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

End host to Server

TCP 443 CiscoWorks HTTP server in SSL mode

Common Services Client to Server

Server Internal

TCP 1741 CiscoWorks HTTP Protocol

• Common Services

• CiscoView


• Inventory, Config & Image Management


• IPSLA Performance Management

Client to Server

TCP 42342 OSAGENT Common Services Client to Server

Table 5 LMS 4.0.1 Port Usage (continued)

Protocol




OL-23862-01


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

Common Services Client to Server

TCP 1099 ESS (used for Java Management Extensions)

Common Services Server Internal

TCP 8898 Log Server Fault Management Server Internal

TCP 9002 DynamID authentica-tion (DFM Broker)

Fault Management Server Internal

TCP 9007 Tomcat shutdown Common Services Server Internal

TCP 9009 Ajp13 connector used by Tomcat


UDP 9020 Trap Receiving Fault Management Server Internal

UDP 14004 Lock port for ANI Server singlet on check

Network Topology, Layer 2 Services and User Tracking

Server Internal

TCP 15000 Log server Fault Management Server Internal

TCP 40050- 40070

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


TCP 40401 LicenseServer Common Services Server Internal

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

Client to Server

TCP 42340 CiscoWorks Daemon Manager - Tool for Server Processes


TCP 42344 ANI HTTP Server Common Services Server Internal

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


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


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



Protocol




OL-23862-01


Note In the Windows Firewall, ICMP inbound and outbound needs to be open. If you have ICMP inbound open and outbound closed then all the Fault Management devices will stay in questioned state. While configuring your Windows Firewall, enable the ICMP options to allow ICMP traffic through Firewall. See http://technet.microsoft.com/en-us/library/cc779521%28WS.10%29.aspx for more details on administering Windows Firewall and on configuring ICMP settings in Windows Firewall. You need to allow ICMP traffic in any Firewall that is operating between CiscoWorks Server and devices to avoid Fault Management devices staying in questioned state.

TCP 43441 Common Services Database


TCP 43455 Inventory, Config and Image Management Database

Inventory, Config and Image Management

Server Internal

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

Server Internal

TCP 43445 Fault History Database Fault Management Server Internal

TCP 43446 Inventory Service Database


TCP 43800 Device Performance Management Database

Device Performance Manage-ment

Server Internal

TCP 43820 IPSLA Performance Management Database

IPSLA Performance Manage-ment

Server Internal

TCP 43447 Event Promulgation Module Database


TCP 44400- 44420

CSTM Ports • Fault Management

• Device Performance Management

Server Internal

TCP 47010- 47040

CSTM Port Inventory, Config and Image Management

Server Internal

TCP 49000-49040

CSTM Port Inventory, Config and Image Management

Server Internal

TCP 50001 SOAPMonitor Inventory, Config and Image Management

Server Internal

TCP 55000- 55020

CSTM Port Network Topology, Layer 2 Services and User Tracking

Server Internal

TCP 56000- 56040

CSTM Port VRF Lite Server Internal


Protocol




OL-23862-01

http://technet.microsoft.com/en-us/library/cc779521%28WS.10%29.aspx

Downloading CiscoWorks LAN Management Solution 4.0.1

Downloading CiscoWorks LAN Management Solution 4.0.1You can download LMS 4.0.1 either from Cisco.com or as a Software Update from:

Admin > System > Software Center > Software Update

This section contains:

• Downloading From Cisco.com

• Downloading From Software Center

Downloading From Cisco.comLMS 4.0.1 is available on Cisco.com. To download LMS 4.0.1:

Step 1 Go to the Download Software page http://www.cisco.com/cisco/software/navigator.html.

Step 2 Select Network Management and Automation from the Software Product Category list.

Step 3 Select Routing and Switching Management > CiscoWorks LAN Management Solution Products > CiscoWorks LAN Management Solution 4.0 and later > CiscoWorks LAN Management Solution 4.0 > CiscoWorks LMS Software.

Step 4 Click Solaris or Windows.

Step 5 Download the file into a temporary directory on your system.

Downloading From Software CenterYou can use the Software Update function in LMS Software Center to download LMS 4.0.1.

To download LMS 4.0.1 from Software Center:

Step 1 Go to the CiscoWorks home page and select Admin > System > Software Center > Software Update.

The Software Updates page appears.

Step 2 In the Products Installed table, select the check box corresponding to CiscoWorks LAN Management Solution.

Step 3 Click either:

• Download Updates. See Using the Download Updates Option.

Or

• Select Updates. See Using the Select Updates Option.


OL-23862-01

http://www.cisco.com/cisco/software/navigator.html

Downloading CiscoWorks LAN Management Solution 4.0.1

Using the Download Updates Option

To download LMS 4.0.1 using the Download Updates option:

Step 1 Click Download Updates on the Software Updates page.

The Cisco.com and Proxy Server Credentials dialog box appears.

Step 2 Enter your Cisco.com username and password. Both are mandatory.

If you have configured proxy settings under Admin > System > Cisco.com Settings > Proxy Server

Setup, enter the Proxy server username and password.

Step 3 Click Next.

The Destination Location page appears. The destination location should not be the location where CiscoWorks is installed.

The default download directory is:

/opt/psu_download—On Solaris

System Drive:\psu_download—On Windows

Software Center does not support downloading software or device updates into the same directory where you have installed CiscoWorks LAN Management Solution, or any of its sub- directories. Also, you cannot download software or device updates under System directories.

Step 4 Enter the location, or browse to the location using the Browse tab.

The destination location must have casuser write-permissions.

Step 5 Click Next.

The Summary page appears with a summary of your inputs.

Step 6 Click Finish to confirm the download operation.

Using the Select Updates Option

To download LMS 4.0.1 using the Select Updates option:

Step 1 Click Select Updates in the Software Updates page.

The Cisco.com and Proxy Server Credentials dialog box appears.

Step 2 Enter your Cisco.com username and password. Both are mandatory.

If you have configured proxy settings under Admin > System > Cisco.com Settings > Proxy Server

Setup, enter the Proxy server username and password.

The Available Images page appears.

Step 3 Either:

• Select the cwlms4_0_1_sol_k9.zip file, for Soalris.

• Select the cwlms4_0_1_win_k9.zip, for Windows.


OL-23862-01

Installing CiscoWorks LAN Management Solution 4.0.1

Step 4 Click Next.

The Destination Location page appears. The destination location should not be the location where CiscoWorks is installed.

The default download directory is:

/opt/psu_download—On Solaris

System Drive:\psu_download—On Windows

Software Center does not support downloading software or device updates into the same directory where you have installed CiscoWorks LAN Management Solution, or any of its sub- directories. Also, you cannot download software or device updates under System directories.

Step 5 Enter the location, or browse to the location using the Browse tab.

The destination location must have casuser write-permissions.

Step 6 Click Next.

The Summary page appears with a summary of your inputs.

Step 7 Click Finish to confirm the download operation.

Installing CiscoWorks LAN Management Solution 4.0.1This section describes how you can install CiscoWorks LMS 4.0.1 on Solaris and Windows systems.

The LMS 4.0.1 installation program takes approximately 35 minutes to complete on Windows and Solaris, on a single server with the recommended hardware requirements.

This can take more than two hours if you perform network management integration while installing.

• If Virus Check is enabled in your system, then installation of LMS 4.0.1 will take a longer time.

• If HP Openview or Netview is running on your system, installation will take a longer time. Stop HP Openview or Netview services to run a faster installation.

Note While setting up HA and DR environment in LMS server, ensure to set them prior to LMS installation. For further information on HA/DR configuration, see http://www.cisco.com/en/US/docs/net_mgmt/ciscoworks_lan_management_solution/4.0/install/guide/ hasetup.html

This sections contains:

• Prerequisites for Installing CiscoWorks LMS 4.0.1 Software

• Installing LMS 4.0.1 on Solaris

• Installing LMS 4.0.1 on Windows

• Installing CiscoWorks LMS 4.0.x Using Windows 2008 R2 Patch

• Re-installing LMS 4.0.1

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


OL-23862-01

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


Prerequisites for Installing CiscoWorks LMS 4.0.1 SoftwareBefore you install CiscoWorks LMS 4.0.1, LMS 4.0 must be installed on your system.

You must ensure that:

• The server and client system have the recommended hardware and software requirements.

• You have disabled Terminal Services on the Windows operating system in the Application mode.

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

However, you can enable Terminal Services in remote Administration mode.

• If you have configured Remote Syslog Collector (RSC) on a different server, you must upgrade RSC to RSC 5.0. There are no changes in RSC in LMS 4.0.1.

• After you uninstall earlier versions of LMS like LMS 3.2, you must remove the CiscoWorks logo manually if it is not removed during uninstallation.

While installing CiscoWorks LMS 4.0.1, the installation process checks for the required patches. You must install:

• All the required patches, recommended patches, and cluster patches on Solaris systems.

• All the required service packs on Windows systems

Local administrators group and casusers group must have full access.

If the permissions are incorrect, stop the Daemon Manager, change the permissions, and start the Daemon Manager again.

Note If CiscoWorks LMS is running without the required service packs or patches, it will not function properly.

Notes on OS Upgrade:

• If you want to install LMS 4.0.1 in a Windows 2003 or Windows 2008 server, and upgrade to Windows 2008 R2 server, you must install the Windows 2008 R2 Patch after the OS upgrade.

• If you have LMS 4.0 in a Windows 2003 or Windows 2008 server, and upgrade to Windows 2008 R2 server, you can install LMS 4.0.1 using the Windows 2008 R2 Patch after the OS upgrade.

You can download the Windows 2008 R2 Patch from:


For more information, see Installing CiscoWorks LMS 4.0.x Using Windows 2008 R2 Patch.


OL-23862-01




Installing LMS 4.0.1 on SolarisTo install the LMS 4.0.1 on a Solaris system for the first time:

Step 1 Navigate to the location on your system, where you have downloaded the cwlms4_0_1_sol_k9.zip.

Step 2 Unzip the cwlms4_0_1_sol_k9.zip file.

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

Step 3 Navigate to the cwlms4_0_1_sol_k9 folder.

Step 4 Run the installation setup script by entering:

# sh setup.sh

or

# ./setup.sh

A Welcome message appears:

Welcome to CiscoWorks LAN Management Solution 4.0.1 setup program.

A prompt appears:

Press Enter to read/browse the following license agreement:

Step 5 Press Enter to read the license agreement.

The following message appears at the end of the license agreement:

Do you accept all the terms of the License Agreement? (y/n) [n]:

Step 6 Enter Y to accept the license agreement and proceed with the installation, or enter N to deny and quit the installation.

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

Installation from the network drive will be slower than installing from the local drive.

If you are installing from a network drive, the installation might take longer to complete. This happens especially for CiscoView device packages.

Step 7 Enter Y to proceed or N to exit installation.

A Warning message appears:

WARNING: Automatic data backup does not happen during this installation. We recommend you to take a backup of data before starting this installation.

Step 8 Enter Y to proceed or N to exit installation.

We recommend you download and install the latest required and recommended patches from http://www.oracle.com/us/sun/index.html, before you run LMS.

For more information on Solaris patches, see Solaris Patches in the LMS 4.0 Installation Guide http://www.cisco.com/en/US/docs/net_mgmt/ciscoworks_lan_management_solution/4.0/install/guide/prereq.html#wp1130208.

The following warning messages appear to ensure you install the Cluster Patches required for Solaris 10:

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

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

WARNING: Otherwise, some features of the CiscoWorks applications will not function properly.

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


OL-23862-01


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


Enter Y to proceed with the installation.

Note LMS 4.0.1 installation automatically use the installation mode that you selected while installing LMS 4.0. You cannot change the LMS 4.0.1 installation mode.

Installing LMS 4.0.1 on WindowsTo install LMS 4.0.1 on a Windows system for the first time:

Step 1 Navigate to the location on your system, where you have downloaded the cwlms4_0_1_win_k9.zip file.

Step 2 Unzip the cwlms4_0_1_win_k9.zip file.

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

Step 3 Navigate to the cwlms4_0_1_win_k9 folder and double-click cwlms4_0_1_win.exe.

While installing from the network drive, the Installing from Network Drive window appears. Installation from the network drive will be slower than installing from the local drive depending upon the network speed.

Step 4 Click Yes to proceed or No to exit installation.

A Warning message appears:

WARNING: Automatic data backup does not happen during this installation. We recommend you to take a backup of data before starting this installation.

The CiscoWorks LAN Management Solution 4.0.1 window appears.

Step 5 Click Yes to proceed or No to exit installation.

If the WMI service is up and running, the following message appears when installation starts:

Windows Management Instrumentation (WMI) is running. This locks processes and impedes

installation. To avoid WMI conflicts, this Setup program will stop and immediately restart

the WMI service.

Step 6 Click OK to proceed.

The Internet Information Services (IIS) detection message appears.

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

Step 7 Click Yes or No to continue.

Installation checks for the Regional Settings. They have to be set either as US English or Japanese. If the Primary settings point to an unsupported locale, installation aborts with the following message appears:

You are trying to install CiscoWorks on an unsupported locale. CiscoWorks supports only US English or Japanese languages. Please reinstall your Operating System with a supported locale and change the Regional Settings to either of these languages.

The Welcome window appears.


OL-23862-01


Step 8 Click Next to continue.

The Software License Agreement window appears. You must accept this agreement to install CiscoWorks LMS 4.0.1.

Step 9 Click Accept to continue.

Note LMS 4.0.1 installation will automatically use the installation mode that you selected while installing LMS 4.0. You cannot change the LMS 4.0.1 installation mode.


OL-23862-01


Installing CiscoWorks LMS 4.0.x Using Windows 2008 R2 PatchTo install the LMS 4.0.x using Windows 2008 R2 patch on Windows 2008 R2 servers for the first time (fresh installation of LMS 4.0.x):

Step 1 Go to http://www.cisco.com/cisco/software/release.html?mdfid=283434800&flowid=19062&os=Windows&softwareid=280775103&release=4.0&rellifecycle=&relind=AVAILABLE&reltype=all

Step 2 Download the patch for Windows 2008 Server Standard and Enterprise Editions Release 2 to your system.

Step 3 Go to the directory where you have downloaded the patch and double-click CiscoWorks_LMS_4.0.x_WIN2K8_R2.exe.

• If LMS 4.0.x is not installed on R2 server already, a dialog box appears prompting you to select the location of LMS 4.0.x installable.

Select LMS 4.0.x installable from the local hard drive where you have stored the software images, to proceed with a new installation of LMS 4.0.x along with R2 patch.

If you have selected unsupported Windows installable, the following message appears:

Unable to extract 4.0.x application

If you have selected Windows installable that is corrupted, the following message appears:

Unable to launch 4.0.x application.

• If LMS 4.0.x is installed on R2 server already, the following confirmation message appears:

Click Yes to reinstall LMS 4.0.x along with the Windows 2008 R2 patch. Click No to

install the Windows 2008 R2 patch alone.

Either:

– Click Yes to reinstall LMS 4.0.x along with the Windows 2008 R2 patch.

A dialog box appears prompting you to select the location of LMS 4.0.x installable

Select LMS 4.0.x installable from the local hard drive where you have stored the software images, to proceed with re-installation of LMS 4.0.x along with R2 patch.




Unable to launch 4.0.x application

Or

– Click No to install the Windows 2008 R2 patch alone.

The confirmation message appears:

CiscoWorks daemons need to be stopped to proceed with the installation. Click Yes

to stop the daemons. Click No to abort the installation.

The installation of the Windows 2008 R2 patch alone takes 15 minutes.

Note You have to configure the swap space before running the installation.


OL-23862-01



Note After the installation of R2 patch alone, if you run the LMS 4.0.x Windows 2008 R2 patch installable again, you have to re-install LMS 4.0.x along with the Windows 2008 R2 patch. You do not have the option to choose R2 patch installation alone during the subsequent re-installations.

a. Either:

– Click Yes to stop the daemons and continue with the installation.

Or

– Click No to abort the installation.

b. Click Finish.

Re-installing LMS 4.0.1Re-installation is installing the product over the existing one without performing an uninstallation.

You can re-install LMS 4.0.1 by running the installation program on the system currently running the product. LMS 4.0.1 supports new installation and re-installation of applications at the same time.

Re-installation preserves the settings from the previous installation.

LMS applications will automatically be installed in the same location, where the previous version was installed.

To reinstall LMS 4.0.1, follow the similar procedure as detailed in Installing CiscoWorks LAN Management Solution 4.0.1.

Note for Re-installation

In Windows, if the WMI service is up and running, the following message appears when installation starts:

Windows Management Instrumentation (WMI) is running. This locks processes and impedes installation. To avoid WMI conflicts, this Setup program will stop and immediately restart the WMI service.

Do you want to proceed?

Click Yes to proceed with this installation. Click No to exit installation.

Click Yes and proceed with the installation.


OL-23862-01


Re-installing LMS 4.0.x Using Windows 2008 R2 PatchTo reinstall LMS 4.0.x using LMS 4.0.x Windows 2008 R2 patch:

Step 1 Go to the directory where you have downloaded the patch and double-click CiscoWorks_LMS_4.0.x_WIN2K8_R2.exe.

If LMS 4.0.x is installed on R2 server already, the following confirmation message appears:

Click Yes to reinstall LMS 4.0.x along with the Windows 2008 R2 patch. Click No to install the Windows 2008 R2 patch alone.

Step 2 Either:

• Click Yes to reinstall LMS 4.0.x along with the Windows 2008 R2 patch.

A dialog box appears prompting you to select the location of LMS 4.0.x installable

Select LMS 4.0.x installable from the local hard drive where you have stored the software images, to proceed with re-installation of LMS 4.0 along with R2 patch.




Unable to launch 4.0.x application

Or

• Click No to install the Windows 2008 R2 patch alone.

The confirmation message appears:

CiscoWorks daemons need to be stopped to proceed with the installation. Click Yes to stop

the daemons. Click No to abort the installation.

The installation of the Windows 2008 R2 patch alone takes 15 minutes.

Note You have to configure the swap space before running the installation.

Note After the installation of R2 patch alone, if you run the LMS 4.0.x Windows 2008 R2 patch installable again, you have to re-install LMS 4.0.x along with the Windows 2008 R2 patch. You do not have the option to choose R2 patch installation alone during the subsequent re-installations.

Step 3 Either:

• Click Yes to stop the daemons and continue with the installation.

Or

• Click No to abort the installation.

Step 4 Click Finish.

Note If any file of LMS 4.0 gets corrupted, you must re-install LMS 4.0 and then re-install LMS 4.0.1.


OL-23862-01

Upgrading to LMS 4.0.1

Upgrading to LMS 4.0.1The following upgrade paths are supported:

Remote migration is supported for LMS 4.0.1, and is similar to the Remote migration to LMS 4.0.

This section contains:

• Remote Upgrade to LMS 4.0.1

Current LMS Version Type of Upgrade Procedure

LMS 4.0 Remote migration 1. Install LMS 4.0

2. Install LMS 4.0.1.

3. Migrate your data to LMS 4.0.1 using the instructions explained in the section Remote Upgrade to LMS 4.0.1.

Direct migration 1. Install LMS 4.0.1 over LMS 4.0.

The data is automatically migrated during installation.

LMS 3.2, LMS 3.2 SP Remote migration 1. Back up the data in the old machine.

2. Install LMS 4.0 in the new machine.


4. Migrate your data to LMS 4.0.1 using the instructions explained in the section Remote Upgrade to LMS 4.0.1.

LMS 2.6, LMS 2.6 SP1, LMS 3.0, LMS 3.0 December 2007 update, LMS 3.1

Remote migration

Direct upgrade to LMS 4.0.1 is not supported.

The suggested upgrade path is:

LMS 2.6/LMS 2.6 SP1/ LMS 3.0/LMS 3.0 December 2007 update/LMS 3.1> LMS 4.0 > LMS 4.0.1

1. Back up the data in the old machine.


3. Migrate the data to LMS 4.0. For more information, see

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


LMS 2.2, LMS 2.5, LMS 2.5.1

Remote migration

Direct upgrade to LMS 4.0.1 is not supported.

The suggested upgrade path is:

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

1. Back up the data in the old machine.

2. Upgrade from the earlier versions of LMS to LMS 2.6 and migrate the data, using the instructions in:

– Readme for CiscoWorks LMS 2.6 Update on Solaris

– Readme for CiscoWorks LMS 2.6 Update on Windows

– Data Migration Guide for LAN Management Solution 2.6


4. Migrate the data to LMS 4.0.




OL-23862-01



Upgrading to LMS 4.0.1

Remote Upgrade to LMS 4.0.1To upgrade from the previous versions of LMS to LMS 4.0.1 on a different Solaris machine:

Step 1 Login to the machine where the previous version of LMS is installed.

Step 2 Take a backup of the LMS data.

Step 3 Login to the machine where LMS 4.0.1 is to be installed.

Step 4 Follow the install procedure to install LMS 4.0. See Installing CiscoWorks LAN Management Solution 4.0.1.

Step 5 Migrate the data to LMS 4.0.1:

For Solaris:

a. Stop the daemon manager by entering:

/etc/init.d/dmgtd stop

b. Restore the backed up data by entering:

NMSROOT/bin/perl NMSROOT/bin/restorebackup.pl -d BKP [-t temporary_directory]

where BKP is the backup directory.

You must give the absolute path for BKP. For example, if BKP is under /opt, give the path as NMSROOT/bin/perl NMSROOT/bin/restorebackup.pl -d /opt/BKP.

c. Examine the log files

d. Start the daemon manager by entering:

/etc/init.d/dmgtd start

For Windows:

a. Stop the daemon manager by entering:

net stop crmdmgtd

b. Restore the backed up data by entering:

NMSROOT\bin\perl NMSROOT\bin\restorebackup.pl -d BKP [-t temporary_directory]

where BKP is the backup directory.

You must enter the absolute path for BKP. For example, if BKP is under C:\, enter the path as NMSROOT\bin\perl NMSROOT\bin\restorebackup.pl -d C:\BKP.

c. Examine the log files

d. Start the daemon manager by entering:

net start crmdmgtd

For the detailed procedure of migrating and restoring the LMS data, follow the procedure in Migrating Data to CiscoWorks LAN Management Solution 4.0 at http://www.cisco.com/en/US/docs/net_mgmt/ciscoworks_lan_management_solution/4.0/install/guide/dmg.html.


OL-23862-01



Bugs

Notes for Remote Upgrade

When you back up the data from LMS 2.6, LMS 2.6 SP1, or LMS 3.x and restore the data on LMS 4.0.1, a warning message appears stating that there is a mismatch in the applications data. You can ignore this message and continue the data restore. For more details on backing up and restoring data, see Migrating Data to CiscoWorks LAN Management Solution 4.0 at http://www.cisco.com/en/US/docs/net_mgmt/ciscoworks_lan_management_solution/4.0/install/guide/dmg.html.

While setting up HA and DR environment in LMS server, ensure to set them prior to LMS installation. For further information on HA/DR configuration, see Setting Up CiscoWorks LMS in High Availability and Disaster Recovery Environment at http://www.cisco.com/en/US/docs/net_mgmt/ciscoworks_lan_management_solution/4.0/install/guide /hasetup.html.

BugsThis section explains:

• Using Bug Toolkit

• Known Problems of CiscoWorks LAN Management Solution 4.0.1

• Resolved Problems

Using Bug ToolkitIn CiscoWorks LMS 4.0.1and later, use the Bug ToolKit to view the list of outstanding and resolved bugs in a release. This section explains how to use the Bug ToolKit through the following subsections:

• Search Bugs

• Export to Spreadsheet

Search Bugs

This section explains how to use the Bug ToolKit to search for a specific bug or to search for all the bugs in a specified release.

Step 1 Go to http://tools.cisco.com/Support/BugToolKit/action.do?hdnAction=searchBugs.

You will be prompted to log into Cisco.com. After you login, the Bug Toolkit page opens.

Step 2 Click Launch Bug Toolkit.

Step 3 To search for a specific bug, enter the bug ID in the Search for Bug ID field and click Go in the Search Bugs tab.

To search for all the bugs in a specified release, enter the following search criteria in the Search Bugs tab:

• Select Product Category—Select Network Management and Automation.

• Select Products—Select CiscoWorks LAN Management Solution from the list.

• Software Version—Select 4.0.1 to view the list of outstanding and resolved bugs in CiscoWorks LAN Management Solution 4.0.1.


OL-23862-01



http://tools.cisco.com/Support/BugToolKit/action.do?hdnAction=searchBugs



Bugs

• Search for Keyword(s)—Separate search phrases with boolean expressions (AND, NOT, OR) to search within the bug title and details.

• Advanced Options—You can either perform a search using the default search criteria or define custom criteria for an advanced search. To customize the advanced search, select Use custom settings for severity, status, and others and provide the following information:

– Severity—Select the severity level.

– Status—Select Open, Fixed, or Terminated.

Select Open to view all the open bugs. To filter the open bugs, clear the Open check box and select the appropriate sub-options that appear below the Open check box. The sub-options are New, Held, More, Open, Waiting, Assigned, Forwarded, Postponed, Submitted, and Information Required. For example, if you want to view only new bugs in CiscoWorks LAN Management Solution 4.0.1, only select New.

Select Fixed to view fixed bugs. To filter fixed bugs, clear the Fixed check box and select the appropriate sub-options that appear below the fixed check box. The sub-options are Resolved or Verified.

Select Terminated to view terminated bugs. To filter terminated bugs, clear the Terminated check box and select the appropriate sub-options that appear below the terminated check box. The sub-options are Closed, Junked, and Unreproducible. Select multiple options as required.

– Advanced—Select the Show only bugs containing bug details check box to view only those bugs that contain detailed information, such as symptoms and workarounds.

– Modified Date—Select this option if you want filter bugs based on the date on which the bugs were last modified.

– Results Displayed Per Page—Select the appropriate option from the list to restrict the number of results that appear per page.

Step 4 Click Search. The Bug Toolkit displays the list of bugs based on the specified search criteria.

Export to Spreadsheet

The Bug ToolKit provides the following options to export bugs to a spreadsheet:

• Click Export All to Spreadsheet link in the Search Results page under the Search Bugs tab. Specify file name and folder name to save the spreadsheet. All the bugs retrieved by the search will be exported.

• Click Export All to Spreadsheet link in the My Notifications tab. Specify file name and folder name to save the spreadsheet. All the saved bugs in all the groups will be exported.

If you are unable to export the spreadsheet, log into the Technical Support Website at http://www.cisco.com/cisco/web/support/index.html for more information or call Cisco TAC (1-800-553-2447).


OL-23862-01

http://www.cisco.com/cisco/web/support/index.html

Bugs

Known Problems of CiscoWorks LAN Management Solution 4.0.1The bugs listed below in the table describe possible unexpected behavior in CiscoWorks LAN Management Solution 4.0.1. These bugs may also be open in previous releases.

Refer Using Bug Toolkit for querying and searching bug details.

Table 6 Known Problems of CiscoWorks LAN Management Solution 4.0.1

Bug ID Summary Explanation

Monitoring and Troubleshooting

CSCtl82624 Sorting does not work for some columns in NAM Configuration page and NAM TOP-N Statistics portlet.

In the NAM Configuration page:

• Sorting does not work for the Port column.

• When the UPMDbEngine process moves to the Running state from the Down state, refresh does not work after you reload the page.

• The radio button does not get highlighted when you use tab to move the control.

In the NAM TOP-N Statistics portlet:

• Sorting does not work for the details listed in the Datasource drop-down list.

• The page takes a long time to load after you configure the portlet. This problem occurs when you do not have Adobe flash player to display the portlet data.

Workaround:

None

CSCtl93304 Unable to load SNMPv2-TC-v1 MIB

When you load the SNMPv2-TC-v1 MIB, the following error appears, Invalid MIB file, or required dependent MIBs are not available.

This error appears even when the dependent SNMPv2-SMI MIB is successfully loaded.

Workaround:

Copy the SNMPv2-TC-v1 MIB file to:

• \NMSRoot\hum\mibmanager\mibcompiler \mibs (On Windows)

• /opt/CSCOpx/hum/mibmanager/mibcompiler/mibs (On Solaris)

You need not load the MIB when it has dependent MIBS.


OL-23862-01

Bugs

CSCtl99901 Devices that do not have a template associated with a poller appear in the Device Type Groups of the Device Selector.

Devices that do not have a template associated with a poller do not appear under All Devices, but appear under Device Type Groups of the Device Selector in Device Performance Management reports.

Workaround:

None.

CSCtl99511 Data does not appear properly when you troubleshoot IP phone using MAC address or IP address.

Data does not appear properly when you troubleshoot an IP phone in the following scenarios:

• Enter the MAC address or IP address of the IP phone in the Troubleshooting page (Monitor > Troubleshooting Tools > Troubleshooting Workflow) and troubleshoot it.

• Launch the IP phone report and click the hyperlink of the IP address or MAC address to troubleshoot the IP phone.

This problem occurs when the associated router of the IP Phone connected switch is not managed.

Workaround:

None.

CSCti95995 Hourly data collection does not happen for some PathEcho Collectors

When a device has image IOS (tm) s72033_rp Software (s72033_rp-ENTSERVICESK9_WAN-M), Version 12.2(18)SXF5, RELEASE SOFTWARE (fc3), proper data collection does not happen for operations like PathEcho, HTTP, tcpConnect, and dlsw.

This problem occurs only when the image is IOS Version 12.2(18)SXF5.

Workaround:

Upgrade the IOS Version.




OL-23862-01

Bugs

CSCtn02370 Problems in show events filter of the Event monitor

The show events filter of the Event Monitor (EM) has the following problems:

• When you click an event in the Device Details popup of the Monitoring dashboard, EM appears with events of the selected device. If you toggle between the options in the Show Event filter, EM does not respond to the Show All option.

• Launch EM from the Fault Monitor page, select a device from the device selector, and toggle between the options in the Show Event filter. EM does not respond to the Show All option.

• Launch EM, by default events are listed based on the last updated time. If there are events generated on the 31’st of a month and first of the next month, then EM displays the events generated on the 31’st as the latest updated events.

Workaround:

None.

CSCtn46604 The steps to download the User Tracking Utility are wrong, in the LMS UI and in the installation.

During UTU installation, and in the LMS UI (Inventory > User Tracking Settings > Acquisition Summary), the steps to download the User Tracking Utility are wrong.

Workaround:

The correct steps are:

1. Go to the Download Software page (http://www.cisco.com/cisco/software/navigator.html)

2. Select Network Management and Automation from the Software Product Category list.

3. Select Routing and Switching Management > CiscoWorks LAN Management Solution Products > CiscoWorks Campus Manager from the product tree.

4. Select an appropriate product version and the product software type.

5. Select a product release version from the Latest Releases folder and locate the software update to download.




OL-23862-01



Bugs

CSCtn42049 Deleted user-defined groups do not get deleted from Topology Services.

Create a user-defined group, delete it, and create a new user-defined group. Launch Topology Services, you can view the deleted user-defined group in the Topology cloud.

Workaround:

None

Delete a user-defined group, create it again, the Topology cloud does not become red if any device in this group goes down. Also, if this device is unmanaged in UDM, the Topology cloud does not become green.

Workaround:

None

CSCtl96069 Cloud color is not updated when Topology recieves an add event.

When you add a device to LMS either using Device Management (DCR) or using groups, the corresponding user-defined groups do not appear in Topology. The color of the group is also incorrect.

Workaround:

Restart Topology, the color of the cloud will be correct.

CSCtk97948 Last N connected Medianet Portlet goes on loading.

When you launch the Last N Connected Medianet Portlet through the Remote Portlet, the Last N Connected Medianet Portlet goes on Loading.

Workaround:

None

CSCtn32077 Devices do not appear under Medianet Endpoint Connected Devices group in Topology.

In Topology Services, no devices appear under Medianet Endpoint Connected Devices groups.

Workaround:

None




OL-23862-01

Bugs

Search

CSCtl10689 Problems in Global Search The Global Search has the following problems:

• The Search result appears blank in the following Fault Management pages:

– Monitor > Fault Settings > Setup > Fault Device Details

– Admin > Collection Settings > Fault > Fault Monitoring Device Administration

• You cannot use the Global search in the following Fault Management pages:

– Configuration > Job Browsers > Software Image Management, text is not taken.

– Configuration > Tools > Software Image Management > Jobs

• Search results takes a long time to appear in the EnergyWise Manage Devices page

• Unable to search for any task under My Menu

• Wrong error message appears when there are more than 20 records in the Search Results popup.

Workaround:

None.

CSCtl08282 Problems in Global Search Results for Jobs Search

In the Job Details popup that appears when you mouse over the Job ID of the Global Search Results for Jobs Search, the following problems occur:

• When a job is in Scheduled state, the value of Last Run Time is wrong

• For Immediate jobs, the value of Scheduled Next is always Enabled

• The format of the time is different from that of the server

• The Job Details popup does not appear for SystemPsirtJob jobs.

Workaround:

None.




OL-23862-01

Bugs

Configuration and Work Centers

CSCtn22066 In Template Center, unique parameters do not get deployed in some instances.

If you do not click Preview CLI and deploy templates, the unique parameters will not get deployed, and the job will fail.

Workaround

When there are unique parameters present in a template you must click Preview CLI and then deploy the template.

CSCtl51982 Identifiers are created for all the interfaces grouped to a port.

For port-based templates in Template Center, identifiers are created for all interfaces present in the CSV file even when there is no input for attributes of each interface.

When you delete an interface in the CSV file and import the file, identifiers are generated for the deleted interface.

This problem occurs only when you select port-based templates and deploy them.

Workaround:

Validate the CSV file before you import it.

CSCtl20142 In LMS 10,000, the Template Center and Auto Smartports job creation takes a long time.

Deploy jobs of Template Center and Auto Smartports are very slow.

Workaround:

None

CSCtl44985 Unable to configure IPv6 devices in the Auto Smartports Interface Configuration page.

An error message appears in the Review Port Groups pane when you select an IPv6 device.

Workaround:

You can manage the device if it has an IPv4 address in the Device Management page (DCR).

CSCtl22183 In the Auto Smartports Interface Configuration page, wrong interfaces are selected for deployment when you select more than one device.

In the Auto Smartports Interface flow, job fails when you select more than one device and a port group. Here, if you select 2 devices, the Enable or Disable command gets deployed in interfaces of the first device only. For the second device, it tries to deploy the commands in the port that was selected for the first device and the job fails.

Workaround:

None




OL-23862-01

Bugs

CSCtl76231 Devices that are not Identity-capable appear in the device selector when you choose IPV6 device for provisioning.

When you select IPV6 device in Enable Interfaces for Identity page and proceed, you can view all the devices which are not capable of Identity technology in the device selector.

Workaround:

Select IPV4 device in Enable Interfaces for Identity page and deploy.

Administration

CSCtl71375 Unable to download all the zip files for some device packages from Device Update page.

When you select the Rtr800 package from the Device Update page and download it using the immediate job, two zip files are downloaded: NGMARShare.zip and Rtr800.zip

When you download the same package using the schedule job, only Rtr800.zip is downloaded.

The order of applications in the Device Update page differs in Windows and Solaris.

Workaround:

You can download the device package using the schedule PSU job.

CSCtl71426 Wrong option appears for the pdcmd command

CLI shows -v as the option of the pdcmd command to see the version number. This is incorrect.

Workaround:

Use pdcmd -version to see the version number.

CSCtl79509 tmpDeviceLicense is not deleted after a selective backup and restore.

An error appears in the restore backup.log when you restore a selective backup of LMS 4.0 over LMS 4.0.1.

Workaround:

Delete the tmpDeviceLicense table from the LMS database.

CSCtl82703 Password policy non-compliance error appears when you edit a user.

When you edit a user after you set the password policy, a non-compliance error appears even though there is no non-compliance.

Workaround:

Disable all the password policies when you edit a user.




OL-23862-01

Bugs

Resolved ProblemsTable 7 contains the bugs of LMS 4.0 resolved in LMS 4.0.1.

Table 8 contains the bugs of earlier versions of LMS resolved in LMS 4.0.1.

Help

CSCtl92914 The version of LMS is 4.0 instead of LMS 4.0.1 in some help pages.

The version of LMS is 4.0 instead of LMS 4.0.1 in some help pages.

CSCtl92939 Wrong copyright appears in some help pages

The copyright of some of the help pages is Copyright © 1998-2010 instead of Copyright © 1998-2011.



Table 7 Bugs of LMS 4.0 resolved in LMS 4.0.1

Identifier Headline

CSCti77576 In Identity, after you sort ports, the enable Identity commands are deployed on the wrong ports.

CSCti39064 Unable to create device groups using the attributes such as System.ASP_capability, System.Identity_Capability and System.Smart_Install_Directors

CSCti83166 After restoration of a selective backup, templates in Template Center do not appear.

CSCti80845 Null pointer exception occurs when you modify My Profile in Getting Started with a different authentication mode

CSCtj58054 Unable to add NAM with https enabled.

CSCtj83804 When you add a device in DCR without the IP address, LMS is unable to configure the director in the Smart Install configure work flow.

CSCtk14142 Help does not mention that the Cisco Call Manager (CCM) to which the IP phone is registered has to be managed in DCR.

CSCtk11127 Baseline compliance does not check negative prerequisites

CSCtk63285 IPSLA cannot create collectors or obtain IPSLA attributes from devices with SNMPv3 credentials.

CSCtk15900 Advanced Search using any search parameters other than Display Name and Hostname returns no match

CSCtl06350 Baseline compliance prerequisite matching does not work properly.

CSCtk75842 Baseline Templates does not show any removal commands for deploy jobs

CSCtl12556 Role Management shows unauthorized device

CSCtn25075 SNMPv3 config documentation missing from online help

CSCtg91006 SI capable switches have been renamed to SI capable devices


OL-23862-01

Bugs

Table 8 contains the caveats of different applications in earlier versions of LMS, resolved in LMS 4.0.1.

CSCtj14080 In the Configuration Help, the steps for generating the parameter file are not available.

CSCtn07896 In the deploy flow of the Template Center, the User Interface for importing and exporting Unique device attributes CSV file is not intuitive.

CSCtj78447 In Identity, the pre-defined Associated ACL is not generated and downloaded to switch.

CSCtj65219 The command to specify the RADIUS server host is not generated in the Configure RADIUS page.

CSCtk95591 Unable to encrypt password in EnergyWise.

CSCtk47903 Error appears when you click Help of the Clone and Edit pages of Template Center.

CSCtk96179 When there is no keyword configured, current power consumption portlet lists empty items in the drop-down list.

CSCtk57181 Periodic Job scheduled on eighth and ninth of a month takes future date by default.

CSCtj81598 Help does not mention the Solaris path to which the configurations are exported from Config Editor.

CSCtj81597 Hyphen is not a valid hostname prefix character.

CSCtk54707 Static ISR EnergyWise device collection fails on subnet validation.

CSCtk54613 EnergyWise Endpoint collection fails for devices managed with hostname

CSCtk47844 Energywise process goes down due to secret mismatch in endpoint collection

CSCth21498 EnergyWise command generation is incomplete in Manage EnergyWise Devices.

CSCtk00362 In a group of more than 2 devices, when you remove the domain of one device, LMS does not remove the EnergyWise domain from the device.

CSCtl10789 Configuration API for event forensics and troubleshooting includes data for sub interfaces.

CSCtl10918 Syslog automated action does not support NEXUS and ACE devices

Table 7 Bugs of LMS 4.0 resolved in LMS 4.0.1

Identifier Headline

Table 8 Bugs of different applications in earlier versions of LMS, resolved in LMS 4.0.1

Identifier Headline

Campus Manager

CSCsx08917 Color of Topology cloud does not get updated

CSCso03691 Channel Ports do not appear in User Tracking

CSCtj58162 Campus Manager assigns incorrect names to VLANs

CSCtl01484 Duplicate sysname appears when an interface is assigned a dynamic IP

CSCsu00368 UT dynamic updates do not work for more than one change

CSCte21983 Topology Services does not reveal native switch ports for some VLANs


OL-23862-01

Bugs

CSCtl10414 Nexus 7K is not supported for User Tracking in Campus Manager

Common Services

CSCtk65217 Discovery does not recognize some Cisco devices

CSCtj80598 Error appears if a device is not added with IP address and any rule is configured with the attribute ManagementIpAddress.

CSCti98766 Cross-site scripting vulnerability when you login to CiscoWorks LMS server.

CSCti58547 In discovery settings, you cannot edit SNMP string if it has quotes

CSCtj20850 URL for Download package for CiscoView has changed in Cisco.com

CSCtl22244 Emails generated for Software and Device Update jobs have only the short hostname of the LMS and not the Fully Qualified Domain Name (FQDN)

Resource Manager Essentials

CSCth43286 When a device is deleted from DCR, the username in the Audit log is Admin.

CSCtc82155 EnergyWise readiness report fails to run

CSCti42219 RME compliance fails for ATM sub interfaces

CSCti46336 Multi-service port report of 6500 VSS shows 3 of 4 power supplies

CSCtj36374 RME offers weak or no SSL encryption

CSCtj29174 For all announcements EOL reports show dates in red

CSCtj74694 Device Credential report shows incorrect error message

CSCtj70524 Config Editor fails to deploy config change to ACE

CSCtj79140 Unable to remove RME Natted IP address

CSCtj89261 ACE module appears in Startup and Running Out-of-Sync summary when there are no differences in the selected configurations

CSCtk14661 Unable to view job details in compliance management job browser

CSCsz83555 RME fails to upgrade PIX and ASA devices

CSCtd67173 SNMPv3 credential verification fails when you upgrade ASA 5520 to 8.2(1)

CSCtd49464 Software Image Management proceeds after delete error is detected on Cisco 1800 and 2800 routers

Device Fault Manager

CSCsz77669 New devices do not appear in DFM Notification Groups.

CSCtk05950 Discovery fails when the engineID of an SNMPv3 device has colon

Health and Utilization Monitor

CSCtj72221 Unable to load RIPv2-MIB

CSCti77773 CPU Utilization template instances are null for Cisco7609

CSCsv88040 If multiple interfaces have the same interface name then HUM is unable to graph the interface stats.

CSCta46821 Unable to launch the Live Graph and Histo Graph for an instance with a 'comma' in its name.

CSCte41577 CSS (Cisco Content Switches) are not supported in HUM


Identifier Headline


OL-23862-01

Product Documentation

Product DocumentationTable 9 describes the product documentation that is available.

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

CSCtl24648 HUM poller cannot poll instances that are more than 100 characters in length.

Internetwork Performance Monitor

CSCti77722 Date is not sorted properly for System report.

CSCth21594 Hourly data collection is not available for some Echo-based Collectors

CSCti65644 Error appears in the Real time graph when you create a collector with an ampersand in the Collector name.


Identifier Headline

Table 9 Product Documentation

Document Title Available Formats

Readme for CiscoWorks LAN Management Solution 4.0.1 (this document)

On Cisco.com at http://www.cisco.com/en/US/docs/net_mgmt/ciscoworks_lan_management_solution/4.0.1/readme/readme.html

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

Technology Work Centers in CiscoWorks LAN Management Solution 4.0.1

• On Cisco.com at http://www.cisco.com/en/US/docs/net_mgmt/ciscoworks_lan_management_solution/4.0.1/user/guide/workcenters/wcug.html


OL-23862-01

http://www.cisco.com/en/US/docs/net_mgmt/ciscoworks_lan_management_solution/4.0.1/readme/readme.html

http://www.cisco.com/en/US/docs/net_mgmt/ciscoworks_lan_management_solution/4.0.1/user/guide/workcenters/wcug.html

http://www.cisco.com/en/US/docs/net_mgmt/ciscoworks_lan_management_solution/4.0.1/user/guide/workcenters/wcug.html

Related Documentation

Related DocumentationTable 10 describes the product documentation that is available.

Obtaining Documentation, Obtaining Support, and Security Guidelines

For information on obtaining documentation, submitting a service request, and gathering additional information, see the monthly What’s New in Cisco Product Documentation, which also lists all new and revised Cisco technical documentation, at:

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

Subscribe to the What’s New in Cisco Product Documentation as a RSS feed and set content to be delivered directly to your desktop using a reader application. The RSS feeds are a free service and Cisco currently supports RSS version 2.0.

NoticesThe following notices pertain to this software license.

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

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

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

Table 10 Product Documentation

Document Title Available Formats

Installing and Migrating to CiscoWorks LAN Management Solution 4.0

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

Release Notes for CiscoWorks LAN Management Solution 4.0 On Cisco.com at http://www.cisco.com/en/US/docs/net_mgmt/ciscoworks_lan_management_solution/4.0/release/notes/lms40rel.html

LMS 4.0 User Guides On Cisco.com at

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


OL-23862-01

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

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

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

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

http://www.openssl.org/

Notices

License Issues

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

OpenSSL License:

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

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

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

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

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

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

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

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

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

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

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

Original SSLeay License:

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

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

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


OL-23862-01



Notices

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

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

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

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

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

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

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

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

4. If you include any Windows specific code (or a derivative thereof) from the apps directory (application code) you must include an acknowledgement: “This product includes software written by Tim Hudson ([email protected])”.

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

CCDE, CCSI, CCENT, Cisco Eos, Cisco HealthPresence, the Cisco logo, Cisco Lumin, Cisco Nexus, Cisco Nurse Connect, Cisco Stackpower, Cisco StadiumVision, Cisco TelePresence, Cisco WebEx, DCE, and Welcome to the Human Network are trademarks; Changing the Way We Work, Live, Play, and Learn and Cisco Store are service marks; and Access Registrar, Aironet, AsyncOS, Bringing the Meeting To You, Catalyst, CCDA, CCDP, CCIE, CCIP, CCNA, CCNP, CCSP, CCVP, Cisco, the Cisco Certified Internetwork Expert logo, Cisco IOS, Cisco Press, Cisco Systems, Cisco Systems Capital, the Cisco Systems logo, Cisco Unity, Collaboration Without Limitation, EtherFast, EtherSwitch, Event Center, Fast Step, Follow Me Browsing, FormShare, GigaDrive, HomeLink, Internet Quotient, IOS, iPhone, iQuick Study, IronPort, the IronPort logo, LightStream, Linksys, MediaTone, MeetingPlace, MeetingPlace Chime Sound, MGX, Networkers, Networking Academy, Network Registrar, PCNow, PIX, PowerPanels, ProConnect, ScriptShare, SenderBase, SMARTnet, Spectrum Expert, StackWise, The Fastest Way to Increase Your Internet Quotient, TransPath, WebEx, and the WebEx logo are registered trademarks of Cisco Systems, Inc. and/or its affiliates in the United States and certain other countries.

Cisco and the Cisco Logo are trademarks of Cisco Systems, Inc. and/or its affiliates in the U.S. and other countries. A listing of Cisco's trademarks can be found at www.cisco.com/go/trademarks. Third party trademarks mentioned are the property of their respective owners. The use of the word partner does not imply a partnership relationship between Cisco and any other company. (1005R)


OL-23862-01

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

Notices

Any Internet Protocol (IP) addresses used in this document are not intended to be actual addresses. Any examples, command display output, and figures included in the document are shown for illustrative purposes only. Any use of actual IP addresses in illustrative content is unintentional and coincidental.

Readme for CiscoWorks LAN Management Solution 4.0.1 Copyright ©1998-2011, Cisco Systems, Inc. All rights reserved.


OL-23862-01

Documents

Readme for CiscoWorks LAN Management Solution 4.0€¦ · 4 Readme for CiscoWorks LAN Management Solution 4.0.1 OL-23862-01 What’s New in This Release Select Yes and click Apply