 Feedback
|
Table Of Contents
Readme for CiscoWorks LAN Management Solution 4.0.1
Medianet Endpoints Connected Group
Port and Module Groups for Medianet
Troubleshooting Medianet Endpoints
Troubleshooting Workflow-related Enhancements
Third-Party Software and Tool Changes
Server and Client Requirements
Server Requirements on Solaris Systems
Server Requirements on Windows Systems
Steps to Avoid Denial of Service Attacks
Firewall Updates to Avoid Denial of Service Attacks
Downloading CiscoWorks LAN Management Solution 4.0.1
Downloading From Software Center
Using the Download Updates Option
Using the Select Updates Option
Installing CiscoWorks LAN Management Solution 4.0.1
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
Known Problems of CiscoWorks LAN Management Solution 4.0.1
Obtaining Documentation, Obtaining Support, and Security Guidelines
Readme for CiscoWorks LAN Management Solution 4.0.1
March, 2011, OL-23862-01Contents
This 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:
•
Server and Client Requirements
•
•
•
Introduction
CiscoWorks 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 Release
The following are the new features in LMS 4.0.1:
•
•
•
•
•
Medianet Dashboard
The 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:
•
View a bar chart that displays the operational status of the Medianet endpoints grouped according to specific location attributes.
•
View the faults that have occurred on devices with Medianet endpoints connected to them.
•
View details of the unreachable Medianet Endpoints, which are connected to Medianet devices.
The unreachable Medianet Endpoints include the following endpoints, after every User Tracking collection:
–
–
These endpoints were found in one cycle of User Tracking and were missing in the next cycle.
•
View the configuration changes on all the devices with Medianet endpoints after every inventory or configuration collection.
•
View the following Medianet endpoints, during the last N specified time period:
–
–
For more information, see the Online Help.
Medianet Endpoints Connected Group
This 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 Medianet
Two new system-defined PMC groups have been introduced in LMS 401 for Medianet:
•
•
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 Collection
LMS 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.
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
ASP Template Management
LMS 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:
•
This template contains all the system-defined events and their associated system-defined macros.
•
This template contains only ASP events that are mapped to their corresponding system-defined macros, for DMP and IPVSC.
Location Templates
The 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:
•
•
•
Medianet Reports
LMS 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 Endpoints
To 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:
•
Displays the type of Medianet endpoint. It can be Digital Media Player or IP Video Surveillance Camera.
•
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 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 Enhancements
In LMS 4.0.1, the Troubleshooting Workflows (Monitor > Troubleshooting Tools > Troubleshooting Workflows) has the following enhancements:
Port Status portlet
In LMS 4.0.1, the Port Status portlet provides more information about the port like:
•
Displays the number of discrepancies found associated with the port. If you click on the number it launches, the Discrepancies report.
•
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 Search
In 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:
•
•
•
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.
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:
•
•
•
•
•
Third-Party Software and Tool Changes
The following are the changes in the third-party software and tools in this release:
•
•
•
•
Support for MDF 1.47
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.
LMS 4.0.1 supports the MDF package version 1.47 that contains the new device types. For more information on the devices supported by LMS 4.0 Applications see: http://www.cisco.com/en/US/docs/net_mgmt/ciscoworks_lan_management_solution/4.0/device_support/table/lms40sdt.html
Server and Client Requirements
This section contains:
•
•
•
•
Client System Requirements
The following table lists the client system requirements for all platforms:
Server Requirements on Solaris Systems
Table 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
Server Requirements on Windows Systems
Table 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.
Operating System Requirements
The operating system requirements are listed in the table below:
Table 4 Operating System Requirements
Solaris
LMS 4.0.1 supports the following Solaris 10 releases:
•
•
•
•
•
•
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:
•
•
•
•
•
•
Note
•
•
Note
Note
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.
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:
•
•
•
Firewall Updates to Avoid Denial of Service Attacks
If 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
Step 2
For exceptions, see the following steps:
Step 3
For example, Remote Desktop or File and Print Sharing.
Step 4
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
Step 6
Repeat Step 6 until all ports are entered.
Step 7
Step 8
If you have enabled firewall in your CiscoWorks Server, you must open or free up the following ports:
•
•
Only then, the communication across servers or between the server and client can happen.
Note
•
•
•
•
If you want to disable the UDP listeners completely, you must upgrade to LMS 4.1.
Note
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.
Downloading CiscoWorks LAN Management Solution 4.0.1
You 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
LMS 4.0.1 is available on Cisco.com. To download LMS 4.0.1:
Step 1
Step 2
Step 3
Step 4
Step 5
Downloading From Software Center
You 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
The Software Updates page appears.
Step 2
Step 3
•
Or
•
Using the Download Updates Option
To download LMS 4.0.1 using the Download Updates option:
Step 1
The Cisco.com and Proxy Server Credentials dialog box appears.
Step 2
If you have configured proxy settings under Admin > System > Cisco.com Settings > Proxy Server
Setup, enter the Proxy server username and password.
Step 3
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
The destination location must have casuser write-permissions.
Step 5
The Summary page appears with a summary of your inputs.
Step 6
Using the Select Updates Option
To download LMS 4.0.1 using the Select Updates option:
Step 1
The Cisco.com and Proxy Server Credentials dialog box appears.
Step 2
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
•
•
Step 4
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
The destination location must have casuser write-permissions.
Step 6
The Summary page appears with a summary of your inputs.
Step 7
Installing CiscoWorks LAN Management Solution 4.0.1
This 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.
•
•
Note
hasetup.html
This sections contains:
•
•
•
•
•
Prerequisites for Installing CiscoWorks LMS 4.0.1 Software
Before you install CiscoWorks LMS 4.0.1, LMS 4.0 must be installed on your system.
You must ensure that:
•
•
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.
•
•
While installing CiscoWorks LMS 4.0.1, the installation process checks for the required patches. You must install:
•
•
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
Notes on 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.
Installing LMS 4.0.1 on Solaris
To install the LMS 4.0.1 on a Solaris system for the first time:
Step 1
Step 2
The contents of the zip file are extracted under the cwlms4_0_1_sol_k9 directory.
Step 3
Step 4
# 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
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
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
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
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]:Enter Y to proceed with the installation.
Note
Installing LMS 4.0.1 on Windows
To install LMS 4.0.1 on a Windows system for the first time:
Step 1
Step 2
The contents of the zip file are extracted under the cwlms4_0_1_win_k9 directory.
Step 3
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
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
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
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
Installation checks for the Regional Settings. They have to be set either as US English or Japanese. If the Primary settings point to an unsupported locale, installation aborts with the following message appears:
You are trying to install CiscoWorks on an unsupported locale. CiscoWorks supports only US English or Japanese languages. Please reinstall your Operating System with a supported locale and change the Regional Settings to either of these languages.The Welcome window appears.
Step 8
The Software License Agreement window appears. You must accept this agreement to install CiscoWorks LMS 4.0.1.
Step 9
Note
Installing CiscoWorks LMS 4.0.x Using Windows 2008 R2 Patch
To install the LMS 4.0.x using Windows 2008 R2 patch on Windows 2008 R2 servers for the first time (fresh installation of LMS 4.0.x):
Step 2
Step 3
•
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 applicationIf you have selected Windows installable that is corrupted, the following message appears:
Unable to launch 4.0.x application.•
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:
–
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.
If you have selected unsupported Windows installable, the following message appears:
Unable to extract 4.0.x applicationIf you have selected Windows installable that is corrupted, the following message appears:
Unable to launch 4.0.x applicationOr
–
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
Note
a.
–
Or
–
b.
Re-installing LMS 4.0.1
Re-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.
Note
Upgrading to LMS 4.0.1
The following upgrade paths are supported:
LMS 4.0
Remote migration
1.
2.
3.
Direct migration
1.
The data is automatically migrated during installation.
LMS 3.2, LMS 3.2 SP
Remote migration
1.
2.
3.
4.
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.
2.
3.
4.
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.
2.
–
–
–
3.
4.
5.
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
To upgrade from the previous versions of LMS to LMS 4.0.1 on a different Solaris machine:
Step 1
Step 2
Step 3
Step 4
Step 5
For Solaris:
a.
/etc/init.d/dmgtd stop
b.
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.
d.
/etc/init.d/dmgtd start
For Windows:
a.
net stop crmdmgtd
b.
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.
d.
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.
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.Bugs
This section explains:
•
Using Bug Toolkit
In 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
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
You will be prompted to log into Cisco.com. After you login, the Bug Toolkit page opens.
Step 2
Step 3
To search for all the bugs in a specified release, enter the following search criteria in the Search Bugs tab:
•
•
•
CiscoWorks LAN Management Solution 4.0.1.•
•
–
–
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.
–
–
–
Step 4
Export to Spreadsheet
The Bug ToolKit provides the following options to export bugs to a spreadsheet:
•
•
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).Known Problems of CiscoWorks LAN Management Solution 4.0.1
The 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
CSCtl82624
Sorting does not work for some columns in NAM Configuration page and NAM TOP-N Statistics portlet.
In the NAM Configuration page:
•
•
•
In the NAM TOP-N Statistics portlet:
•
•
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:
•
\mibs (On Windows)•
You need not load the MIB when it has dependent MIBS.
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:
•
•
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.
CSCtn02370
Problems in show events filter of the Event monitor
The show events filter of the Event Monitor (EM) has the following problems:
•
•
•
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.
2.
3.
4.
5.
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
CSCtl10689
Problems in Global Search
The Global Search has the following problems:
•
–
–
•
–
–
•
•
•
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:
•
•
•
•
Workaround:
None.
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.
This problem occurs when different devices have different interfaces with different names.
For example, for both the devices, if we are going to enable or disable on Fa 1/0/1 then the job will be successful. If we enable or disable in Fa 1/0/1 in the first device and Fa 1/1 in the second device then the job will fail.
Workaround:
None
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.
CSCtw51607
Device under NAT environment is not collected in EnergyWise
The device maintained under NAT environment and managed with public IP is shown in all the technology workcenter except EnergyWise. In LMS, EnergyWise needs subnet details of a device, which is done through MIB polling. Hence, if the device is managed with NATed IP address then EnergyWise collection fails.
Workaround:
None.
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.
CSCsk35018
CiscoWorks databases open UDP port 2638 to listen for client broadcasts.
CiscoWorks databases open UDP port 2638 to listen for client broadcasts.
This may result in a server response with information about the database port and engine name.
This occurs with the default database configuration for all CiscoWorks
databases.
Workaround:
Use access-lists or firewalls to restrict client access to the CiscoWorks Server.
In LMS 4.0.1, UDP packets sent by the database server in response to client broadcasts do not contain any sensitive information. The data in these packets is limited to:
•
•
•
•
If you want to disable the UDP listeners completely, you must upgrade to LMS 4.1.
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.
Resolved Problems
Table 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.
Table 8 contains the caveats of different applications in earlier versions of LMS, resolved in LMS 4.0.1.
Product Documentation
Table 9 describes the product documentation that is available.
Table 9 Product Documentation
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
•
Note
Related Documentation
Table 10 describes the product documentation that is available.
Table 10 Product Documentation
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
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.
Notices
The following notices pertain to this software license.
OpenSSL/Open SSL Project
This product includes software developed by the OpenSSL Project for use in the OpenSSL Toolkit (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:
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.
2.
3.
4.
5.
6.
"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:
Copyright © 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.
2.
3.
"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.
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)
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.
