Table Of Contents
LAN Management Solution, Release 2.2 (Maintenance Kit)
SUPPLEMENTAL LICENSE AGREEMENT
LAN Management Solution 2.2 Overview
Prerequisite for Installing DFM for LMS 1.x Users
On Solaris
On Windows
LMS Contents
Additional Information Online
What's New?
Server and Client System Requirements
Solaris Patches for LAN Management Solution
LAN Management Solution Port Usage
Upgrade Paths
Upgrade Options
Upgrading to LAN Management Solution 2.2
Prerequisites
Important Upgrade Notes
Order of Upgrade
Upgrading to CiscoWorks Common Services 2.2
Upgrading to CiscoWorks Common Services 2.2 on Solaris
Upgrading to CiscoWorks Common Services 2.2 on Windows
Upgrading to Resource Manager Essentials 3.5
Upgrading to Resource Manager Essentials 3.5 on Solaris
Upgrading to Resource Manager Essentials 3.5 on Windows
Upgrading to Campus Manager 3.3
Upgrading to Campus Manager 3.3 on Solaris
Upgrading to Campus Manager 3.3 on Windows
Upgrading to Device Fault Manager 1.2 Updated for Common Services Version 2.2
Upgrading to Device Fault Manager 1.2 Updated for Common Services Version 2.2 on Solaris
Upgrading to Device Fault Manager 1.2 Updated for Common Services Version 2.2 on Windows
Upgrading to nGenius Real-Time Monitor
Upgrading to nGenius Real-Time Monitor 1.4
Upgrading to nGenius Real-Time Monitor 1.4 Service Pack 6
Post-Upgrade Tasks
Adding or Updating Devices in Inventory
Upgrading to CiscoWorks LMS 2.2/LMS 1.3 Update 1
Description
Hardware and Software Requirements
General Recommendations on Java Plug-in 1.4.1_02
Prerequisites for CiscoWorks LMS 2.2/LMS 1.3 Update 1
Downloading CiscoWorks LMS 2.2/LMS 1.3 Update 1
Installing CiscoWorks LMS 2.2/LMS 1.3 Update 1
Installing CiscoWorks LMS 2.2/LMS 1.3 Update 1 on Solaris
Installing CiscoWorks LMS 2.2/LMS 1.3 Update 1 on Windows
Installing Real-Time Monitor SP 8
Installing Real-Time Monitor SP 8 on Windows
Known Problems
Device Fault Manager 1.2: Known Problems
Resolved Problems
Where to Go Next
Related Documentation
Obtaining Documentation
Cisco.com
Documentation CD-ROM
Ordering Documentation
Documentation Feedback
Obtaining Technical Assistance
Cisco TAC Website
Opening a TAC Case
TAC Case Priority Definitions
Obtaining Additional Publications and Information
Quick Start Guide
LAN Management Solution, Release 2.2 (Maintenance Kit)
1 SUPPLEMENTAL LICENSE AGREEMENT
SUPPLEMENTAL LICENSE AGREEMENT FOR CISCO SYSTEMS NETWORK MANAGEMENT SOFTWARE: CISCOWORKS LAN MANAGEMENT SOLUTION
IMPORTANT-READ CAREFULLY: This Supplemental License Agreement ("SLA") contains additional limitations on the license to the Software provided to Customer under the Software License Agreement between Customer and Cisco. Capitalized terms used in this SLA and not otherwise defined herein shall have the meanings assigned to them in the Software License Agreement. To the extent that there is a conflict among any of these terms and conditions applicable to the Software, the terms and conditions in this SLA shall take precedence.
By installing, downloading, accessing or otherwise using the Software, Customer agrees to be bound by the terms of this SLA. If Customer does not agree to the terms of this SLA, Customer may not install, download, or otherwise use the Software. When used below, the term "server" refers to central processor unit.
ADDITIONAL LICENSE RESTRICTIONS
Installation and Use
The Software components are provided to Customer solely to install, update, supplement, or replace existing functionality of the applicable Network Management Software product. Customer may install and use following Software components:
•
CiscoWorks Common Services with CiscoView: Contains shared resources used by other components in this bundle. In many cases, all components in this bundle can be installed on a single server. If some components of this bundle are installed on separate servers, a copy of CiscoWorks Common Services can be installed with each component in Customer's network management environment.
•Resource Manager Essentials (Essentials): May be installed on one (1) server in Customer's network management environment.
•Campus Manager (Campus): May be installed on one (1) server in Customer's network management environment.
•Device Fault Manager (DFM): May be installed on one (1) server in Customer's network management environment.
•nGenius Real Time Monitor (RTM): May be installed on one (1) server in Customer's network management environment.
Reproduction and Distribution
Customer may not reproduce nor distribute software.
DESCRIPTION OF OTHER RIGHTS AND LIMITATIONS
Please refer to the Cisco Systems, Inc. Software License Agreement.
2 LAN Management Solution 2.2 Overview
The LAN Management Solution (LMS) software provides applications for configuring, administering, monitoring, and troubleshooting a campus network. It enables network administrators to effectively manage their LAN and campus networks.
You must install LMS on a system that meets specific requirements. You must configure client systems and some applications before use.
In this document you will find:
•LMS contents, including links for accessing online documentation.
•New features added to this release.
•Hardware and software requirements for optimal performance.
•Upgrade paths and pointers to additional documentation that provides detailed procedures for installing each product. If you already have other CiscoWorks bundled products installed on your system, you might not need to install all of the products included in LMS.
•Information about ordering documentation and contacting Cisco Systems for additional assistance.
Note This document contains information for CiscoWorks LMS 2.x and CiscoWorks LMS 1.x Maintenance customers. It also includes the CiscoWorks LMS 2.2/LMS 1.3 Update 1 details.
Prerequisite for Installing DFM for LMS 1.x Users
You may be asked to validate your Device Fault Manager (DFM) image if you are installing DFM using this Maintenance Kit CD (for CiscoWorks LAN Management Solution 2.2). The maintenance kit allows all other previous licensed LMS 1.x components to upgrade (such as CD One, Resource Manager Essentials, Campus Manager and nGenius Real-Time Monitor).
On Solaris
If you are prompted to validate the image, run the setup.sh command from a directory other than /cdrom/cdrom0. You may be requested to eject and reinsert CDs during validation. This cannot be done if you are running setup.sh from the /cdrom/cdrom0 directory.
To validate DFM:
Step 1 You are prompted to accept (and view) the license agreement. Press Enter. The installation program stops CiscoWorks and performs a requirements check.
Step 2 Depending on your configuration, you may be prompted to validate your DFM image as follows:
To validate the upgrade image, insert a Device Fault Manager (DFM) 1.2 or earlier
CD.
Please ensure that the CD is mounted on /cdrom/cdrom0.
Step 3 Insert a DFM 1.2 (or earlier) CD into one of your system drives. (Close the File Manager window that appears.) The installation software starts validating the DFM image.
Step 4 After validation, the following message appears:
Please reinsert the original CD to complete the installation.
Press any key to continue.
Reinsert the original CD (containing DFM 1.2 Updated for Common Services Version 2.2) into the drive (close the File Manager window that appears) and continue the installation.
If the DFM image cannot be validated-that is, if you do not have a DFM 1.2 (or earlier) CD-the installation cannot proceed. Contact your Cisco sales representative.
On Windows
If you are prompted to validate the DFM image, insert a DFM 1.2 (or earlier) CD into one of your system drives. If the DFM product CD is already in the CD-ROM drive and you stopped the installation process to close programs or if Autostart is disabled, click setup.exe to restart the process.
When autoplay is enabled and the DFM product CD is inserted, a new installation window appears. Click Cancel in each new installation window.
If the DFM image cannot be validated-that is, if you do not have a DFM 1.2 (or earlier) CD-the installation cannot proceed. Contact your Cisco sales representative.
LMS Contents
Table 1 describes the contents of the LAN Management Solution, Release 2.2 for Solaris and Windows.
Table 1 LAN Management Solution 2.2 Contents
This product...
|
Allows you to...
|
And includes these components
|
CiscoWorks Common Services 2.2 (Includes CiscoView 5.5)
|
Provide common software and services for all other LMS products. You can deploy, monitor, and troubleshoot devices across your network.
CiscoWorks Common Services 2.2 includes:
•Common Services 2.2-A set of shared application services
•CiscoView 5.5-A graphical device management tool
•Integration Utility 1.5-An integration module that supports third-party Network Management Systems (NMS)
|
•CiscoWorks Common
Services 2.2 with CiscoView 5.5 product CD-ROM
•Release Notes for CiscoWorks Common Services 2.2 (Includes CiscoView 5.5) on Solaris
•Release Notes for CiscoWorks Common Services 2.2 (Includes CiscoView 5.5) on Windows
|
Resource Manager Essentials 3.5 (Essentials)
|
Manage network inventory and device changes, network configuration, and software images. Also allows you to monitor network availability and perform syslog analysis.
|
•Resource Manager
Essentials 3.5 product CD-ROM
•Release Notes for Resource Manager Essentials 3.5 on Solaris
•Release Notes for Resource Manager Essentials 3.5 on Windows
|
Campus Manager 3.3 (Campus)
|
Obtain graphical views of network topology, and end-user information.
|
•Campus Manager 3.3 product CD-ROM
•Release Notes for Campus Manager 3.3 on Solaris
•Release Notes for Campus Manager 3.3 on Windows
|
Device Fault Manager 1.2 Updated for Common Services Version 2.2 (DFM)
|
Monitor faults real-time and determines the cause of Cisco device faults. Provides Cisco device-level fault correlation, and notifies you of critical network conditions by email or pager.
The optional Fault History drop-in lets you store and access historical information about alerts and faults that are detected and processed by DFM. For location details, see "Additional Information Online" section.
|
•Device Fault Manager 1.2 Updated for Common Services Version 2.2 product CD-ROM
•Release Notes for Device Fault Manager 1.2 Updated for Common Services Version 2.2 on Solaris
•Release Notes for Device Fault Manager 1.2 Updated for Common Services Version 2.2 on Windows
|
NetScout nGenius Real-Time Monitor 1.4 (RTM)
|
Manage and monitor packets, and application and protocol traffic on the network. nGenius Real-Time Monitor also provides tools for troubleshooting and monitoring traffic thresholds.
This client-server network management solution is offered to Cisco Systems customers in cooperation with NetScout Systems, Inc.
|
•NetScout nGenius Real-Time Monitor 1.4 product CD-ROM
•NetScout nGenius Real-Time Monitor 1.4 Service Pack 6 CD-ROM
•NetScout nGenius Real-Time Monitor 1.4 Installation Guide
•Supplement and Release Notes for NetScout nGenius Real-Time Monitor Release 1.4 Service Pack 6
•NetScout nGenius Real-Time Monitor 1.4 Release Notes
|
Additional Information Online
Registered Cisco.com users can access the most current Incremental Device Updates, CiscoView Device Package Updates, Fault History, and Latest Adapters at the following locations:
•Incremental Device Updates
–For Resource Manager Essentials at
http://www.cisco.com/cgi-bin/tablebuild.pl/cw2000-rme
–For Campus Manager at
http://www.cisco.com/cgi-bin/tablebuild.pl/cw2000-campus
–For Device Fault Manager at
http://www.cisco.com/cgi-bin/tablebuild.pl/cw2000-dfm
•CiscoView Device Package Updates at
http://www.cisco.com/cgi-bin/Software/CiscoView/cvplanner.cgi
•Fault History at
http://www.cisco.com/cgi-bin/tablebuild.pl/cw-fault-history
•Latest Adapters at
http://www.cisco.com/cgi-bin/tablebuild.pl/cw2000-nnm
What's New?
This section lists the new features added in the LAN Management Solution, Release 2.2:
1. CiscoWorks Common Services 2.2 replaces CD One. It contains the following new features:
•Security/AAA-ACS mode: Used for user authentication and authorization, it meets the secured device view requirements.
•Security/User Session Management: Passes session data back and forth between two different servlet engines, Tomcat and JRunProxyServer.
•Database Password Encryption: Provides confidentiality for database passwords.
•Express, Typical and Custom Installs: Reduces the number of user interactions during the install process. The Express install is faster than the Typical and Custom install.
2. CiscoView 5.5 contains the following new features:
•Support for remote and local upgrades from CD One, 4th and 5th Editions, to Common Services 2.2.
•Support for all Common Services 2.2 compliant browsers and Java Plug-ins.
•Support for the Common Services 2.2 installation framework and packaging mechanism.
•Support of Audit Trail functionality.
•Background Discovery.
3. Resource Manager Essentials 3.5 contains the following new features:
•Support for over 60 new devices. For a list of these devices, see the Supported Devices Table for Resource Manager Essentials 3.5, available on Cisco. com (also see Table 21).
•Significant performance enhancements over the previous version.
•Support during job creation for specification of the username and password for selected devices. This feature is available in ConfigEditor, NetConfig and NetShow.
•A new SWIM workflow that allows users to select an image, the appropriate devices, and then schedule. This new workflow reduces the amount of time it takes to create a job (especially if the image to be deployed is known) by eliminating the Image Recommendation phase.
•A new SWIM workflow that allows users to optimize bandwidth use by storing on a router's flash memory the image they want to deploy, then instructing devices to retrieve the image from the router.
•A new command to extract Detailed Device Inventory information in XML format.
•User-defined fields that are customizable and can hold alphanumeric strings up to 128 characters long.
•Quick config downloads in Configuration Management.
•Archiving of the vlan.dat file for Cat IOS switches.
•Full support for interactive and multiline commands.
•User-specifiable protocol for config fetch and download.
•Multiple job deletion and retry of failed jobs.
•Templates for IPSec and SSH.
•Saving of Syslog messages for 14 days.
4. Campus Manager 3.3 contains the following new features:
•Improved workflow, ease-of-use and intuitiveness in launching tasks from Campus applications.
•Support for administrative view discovery and display, and creating Campus Views per user.
•Support for secure communication between the client browser and Campus applications using Secure Socket Layer (SSL) protocol.
•Support for new devices.
•Fixes to problems that existed in previous releases.
•The following enhancements have been made to individual Campus applications:
–Topology Services
a. Ability to create Topology Groups
b. Options to display device labels
c. Options to prioritize label preference
d. Ability to find in LAN edge view for locating devices in switch-clouds and fabrics
e. Improved device status filter
f. Support for enabling sub filters of LANE components even after a refresh
g. Ability to generate a report to list all unused ports, and an option to print and save
h. Ability to provide uplink information when router boundary map switch clouds are selected to display context between switch cloud (subnet) and joining router
i. Ability to create SPVC (Soft Permanent Virtual Connection) when both ATM end ports are down
–Path Analysis
a. Support for batch job processing and archiving in Path analysis
b. Support for displaying error messages on unsuccessful path analysis for L3 and L2
c. Support for sorting subnet-to-VLAN Mapping table
d. Improved Path Analysis tracing capabilities
e. Support for CCM login
f. Improved GUI: Pull down menu in Path Analysis connected to the source and destination field
–User Tracking
a. Ability to define acquisition based on a subnet range
b. Support for scheduled archive and export feature in User Tracking
c. Support for enhanced troubleshooting support using a new debugger utility
d. Improved GUI: Addition of two new columns to the User Tracking tables (Duplex type and port speed)
–Discrepancy Reports
a. Support for enhanced discrepancy reporting
–Administration
a. Support for administering Topology Groups
b. Ability to configure scheduling of Path Analysis traces, and archiving of User Tracking data
5. Device Fault Manager 1.2 Updated for Common Services Version 2.2 includes:
•Bug fixes listed in the Release Notes for DFM 1.2 Updated for Common Services Version 2.2
•Device Support:
–Cisco Interfaces and Modules: IGX-URM-2FE, IGX-URM-2FE-2V Network Modules
–Cisco Routers:
a. Cisco 1700 Series Access Routers: 1760(V)
b. Cisco 2600 Series: 2610XM, 2610XM-DC, 2610XM-RP5, 2620XM, 2620XM-DC, 2620XM-RP5, 2621XM, 2621XM-DC, 2621XM-RP5, 2650, 2650XM, 2650XM-DC, 2650XM-RP5, 2651, 2651XM, 2651XM-DC, 2651XM-RP5
c. Cisco 3600: 3662Ac, 3662Dc, 3662AcCo, 3662DcCo
d. Cisco 3700: 3725, 3745
e. Cisco 10000 Series Internet Router: 10005 ESR, 10008 ESR
f. Cisco 12000 Series (Gigabit Switch Routers): 12404 GSR, 12406 GSR, 12410 GSR, 12416 GSR
–Cisco Switches:
a. Cisco Catalyst: 2950-12, 2950-24, 2950C-24, 2950G-12, 2950G-24, 2950G-48, 2950G-24-DC, 2950T-24 (running IOS)
b. Cisco Catalyst: 3548XL (running IOS)
c. Cisco Catalyst: 3550-12T, 3550-12G, 3550-24, 3550-24Dc, 3550-24Mmf, 3550-48 (running IOS)
d. Cisco Catalyst 6009 (running IOS)
e. Cisco Catalyst 6509, 6513 (running IOS)
f. Cisco 7600 Series Internet Router 7600 OSR
g. Cisco CSS 11000 Content Services Switches 11050, 11503, 11506, 11150
–Cisco Wireless LAN devices: Cisco Aironet 1200 Series Access Point AP1200
–Cisco Firewalls: Cisco PIX Firewall Series 501, 506, 506E, 515, 515E, 520, 525
–Cisco IP Telephony Devices: Cisco VG248 FXS Port Voice Gateway
6. nGenius Real-Time Monitor includes:
•Bug fixes listed in the Supplement and Release Notes for NetScout nGenius Real-Time Monitor Release 1.4 Service Pack 6
•Support for Service Pack 6.
3 Server and Client System Requirements
This section provides LAN Management Solution 2.2 server and client requirements.
•Table 2 lists the server requirements for upgrading the LAN Management Solution 2.2 components on Solaris systems.
•Table 3 lists the server requirements for upgrading the LAN Management Solution 2.2 components on Windows systems.
•Table 4 lists the client system requirements for all platforms.
•Table 5 lists the browser requirements for all platforms.
•Table 6 lists the Solaris patches required and recommended for LAN Management Solution 2.2.
•Table 7 lists the ports LAN Management Solution 2.2 uses.
The requirements listed are for managing 500 devices, with all applications hosted on a single server.
If you are managing more than 500 devices or if you are running additional Cisco or third-party applications on the servers, the requirements might be higher. See the individual LMS application installation guides for specific product requirements.
Table 2 Minimum Server Requirements for Solaris Systems
Component
|
Minimum Requirement
|
Hardware
|
•One of the following1 :
–Sun UltraSPARC II
–Sun UltraSPARC III (Sun Blade 1000 Workstation or Sun Fire 280R Workgroup Server)
•Dual processor required for hosting multiple management solutions
•CD-ROM drive
•Color monitor with video card capable of 256 colors or more
•10BaseT or faster (10 Mbps or faster network connection)
|
Software2
|
•One of the following3 :
–For UltraSPARC II: Solaris 2.7 or 2.8
–For UltraSPARC III: Solaris 2.8
|
Available memory (RAM)
|
•One of the following:
–For UltraSPARC II: 1 GB RAM minimum
–For UltraSPARC III Workstation: 1 GB RAM minimum
–For UltraSPARC III Server: 2 GB RAM minimum
•8 MB E-cache
|
Available disk space
|
•One of the following:
–For UltraSPARC II: 9 GB, with 2 GB swap space
–For UltraSPARC III Workstation: 40 GB internal FC-AL disk drive
–For UltraSPARC III Server: Dual 40 GB internal FC-AL disk drives
•UNIX file system recommended 4
|
Table 3 Minimum Server Requirements for Windows Systems
Component
|
Minimum Requirement
|
Hardware
|
•IBM PC-compatible computer with 550 MHz or Pentium III processor (dual processor required for hosting multiple management solutions)
•Color monitor with video card capable of 256 colors or more
•CD-ROM drive
•10BaseT or faster (10 Mbps or faster network connection)
|
Software1
|
•One of the following:
–Windows 2000 Professional with Service Pack 32
–Windows 2000 Server with Service Pack 3
–Windows 2000 Advanced Server3 with Service Pack 3
|
Available memory (RAM)
|
•1 GB
|
Available disk space4
|
•40 GB
•2 GB virtual memory
•NTFS file system required
|
Table 4 Minimum Client Hardware and Software Requirements
Component
|
Minimum Requirement
|
Hardware/Software
|
•Any one of these systems:
–IBM PC-compatible computer with 300 MHz Pentium processor, running Windows XP Professional or Windows 2000 (Advanced Server, Server, or Professional) with Service Pack 3
–Sun UltraSPARC 10 with 333 MHz processor, running Solaris 2.7 or 2.8
•Color monitor with video card set to 256 colors
|
Available disk space
|
•One of the following:
–For Solaris: 512 MB swap space
–For Windows: 512 MB virtual memory
|
Available memory (RAM)
|
256 MB RAM
|
Table 5 Browser Requirements
Browser
|
Java Virtual Machine (JVM 1 )
|
Version
|
Platform
|
Internet Explorer (IE)
(recommended)
|
5.0.0.3802 or later
|
IE 6.0 (6.0.26),
IE 6.0 SP1 (6.0.28) with patch Q810847
|
Windows XP Professional2 or Windows 2000
|
Netscape Navigator
|
-
|
4.78 or 4.79
|
Windows XP Professional or Windows 2000
|
Netscape Navigator (Downloaded from Sun site only)
|
-
|
4.76
|
Solaris 2.7 or 2.8
|
Solaris Patches for LAN Management Solution
Table 6 lists the Solaris patches for the LAN Management Solution 2.2.
Note A warning message is displayed if obsolete Solaris patches are present on your system. Before running CiscoWorks Common Services 2.2, download and install the latest recommended patches from http://www.sunsolve.sun.com.
Table 6 Solaris Patches for LAN Management Solution 2.21
Operating System
|
Required
|
Recommended
|
Solaris 2.7
|
106980-10
106327-05
107081-11
107636-03
|
108376-03
112300-01
108301-02
108482-02
|
Solaris 2.8
|
111626-01
111327-02
110945-02
110934-01
110898-02
110700-01
109326-05
108827-30
108652-51
108528-18
108921-14
108940-24
|
110951-01
110662-02
110615-01
110286-02
109324-02
111085-02
108964-06
|
LAN Management Solution Port Usage
This section provides a list of ports used by the various CiscoWorks components.
Table 7 LAN Management Solution Port Usage
Protocol
|
Port Number
|
Service Name
|
Application(s)
|
Direction (of establishment) of connection
|
ICMP
|
-
|
Ping
|
Resource Manager Essentials, Campus Manager, and Device Fault Manager
|
Server to Device
|
TCP
|
22
|
Secure Shell (SSH)
|
CiscoWorks Common Services and Resource Manager Essentials
|
Server to Device
|
TCP
|
23
|
Telnet
|
CiscoWorks Common Services, and Resource Manager Essentials
|
Server to Device
|
TCP
|
25
|
Simple Mail Transfer Protocol (SMTP)
|
Resource Manager Essentials
|
Server Internal
|
TCP
|
80
|
HyperText Transfer Protocol (HTTP)
|
CiscoWorks Common Services, CiscoView, and nGenius Real-Time Monitor
|
Client to Server
|
TCP
|
514
|
Remote Copy Protocol
|
CiscoWorks Common Services
|
Server to Device
|
TCP
|
514
|
rsh Daemon
|
Resource Manager Essentials
|
Server to Device
|
TCP
|
1099
|
Remote Method Invocation (RMI) Registry
|
nGenius Real-Time Monitor
|
Client to Server
|
TCP
|
1683
|
Internet Inter-ORB Protocol (IIOP)
|
CiscoWorks Common Services, and Campus Manager
|
Client to Server
|
TCP
|
1684
|
Internet Inter-ORB Protocol (IIOP)
|
CiscoWorks Common Services, and Campus Manager
|
Server to Client
|
TCP
|
1741
|
CiscoWorks HTTP Protocol
|
CiscoWorks Common Services, CiscoView, and Resource Manager Essentials
|
Client to Server
|
TCP
|
1742
|
SSL (HTTPS)
|
CiscoWorks Common Services, and Resource Manager Essentials
|
Client to Server
|
TCP
|
1961
|
Service Manager for Server
|
nGenius Real-Time Monitor
|
Client to Server
|
TCP
|
1962
|
Service for Server
|
nGenius Real-Time Monitor
|
Client to Server
|
TCP
|
1963
|
Application for Client
|
nGenius Real-Time Monitor
|
Server to Client
|
TCP
|
1964
|
Application Manager for Client
|
nGenius Real-Time Monitor
|
Server to Client
|
TCP
|
1965
|
Monitor
|
nGenius Real-Time Monitor
|
Client to Server
|
TCP
|
2639
|
Sybase database connection
|
nGenius Real-Time Monitor
|
Server Internal
|
TCP
|
8007
|
Ajp12Connector port for Tomcat
|
nGenius Real-Time Monitor
|
Server Internal
|
TCP
|
8009
|
Ajp12Connector port for Tomcat
|
nGenius Real-Time Monitor
|
Server Internal
|
TCP
|
8080
|
Web Server
|
nGenius Real-Time Monitor
|
Client to Server
|
TCP
|
8081
|
HttpConnect port for Tomcat
|
nGenius Real-Time Monitor
|
Client to Server
|
TCP
|
8088
|
HIOP
|
CiscoWorks Common Services
|
Server to Client
Client to Server
|
TCP
|
9002
|
DynamID authentication (DFM Broker)
|
Device Fault Manager
|
Client to Server
|
TCP
|
10033
|
CMF Licensing
|
CiscoWorks Common Services
|
Server Internal
|
TCP
|
42340
|
CiscoWorks Daemon Manager - Tool for Server Processes
|
CiscoWorks Common Services
|
Server Internal
|
TCP
|
42343
|
JRun
|
CiscoWorks Common Services
|
Server Internal
|
TCP
|
42344
|
ANI HTTP Server
|
CiscoWorks Common Services
|
Server Internal
|
TCP
|
42351
|
Event Services Software (ESS) Listening (Alternate port is 44351/tcp)
|
CiscoWorks Common Services
|
Server Internal
|
TCP
|
42352
|
ESS HTTP (Alternate port is 44352/tcp)
|
CiscoWorks Common Services
|
Client to Server
|
TCP
|
42353
|
ESS Routing (Alternate port is 44352/tcp)
|
CiscoWorks Common Services
|
Server Internal
|
TCP
|
43441
|
CMF Database
|
CiscoWorks Common Services
|
Server Internal
|
TCP
|
43442
|
RME Database
|
Resource Manager Essentials
|
Server Internal
|
TCP
|
43443
|
ANIDbEngine
|
Campus Manager
|
Server Internal
|
TCP
|
57860
|
JRun - JRun Server Manager Control Server
|
CiscoWorks Common Services
|
Server Internal
|
UDP
|
69
|
Trivial File Transfer Protocol (TFTP)
|
CiscoWorks Common Services and Resource Manager Essentials
|
Server to Device
Device to Server
|
UDP
|
161
|
Simple Network Management Protocol (SNMP)
|
CiscoWorks Common Services, CiscoView, Resource Manager Essentials, Campus Manager, Device Fault Manager, and nGenius Real-Time Monitor
|
Server to Device
Device to Server
|
UDP
|
162
|
SNMP Traps (Standard Port)
|
CiscoWorks Common Services, Resource Manager Essentials, Device Fault Manager and nGenius Real-Time Monitor
|
Device to Server only (RTM);
Server to Device Device to Server (all others)
|
UDP
|
395
|
NetScout Proprietary Port, Server Monitor
|
nGenius Real-Time Monitor
|
Device to Server
|
UDP
|
514
|
Syslog
|
CiscoWorks Common Services and Resource Manager Essentials
|
Device to Server
|
UDP
|
1971
|
Trap and Alarms Listener
|
nGenius Real-Time Monitor
|
Server Internal
|
UDP
|
1972
|
Trap and Alarms Listener
|
nGenius Real-Time Monitor
|
Server Internal
|
UDP
|
1974
|
Shutdown Listener for RMI Registry
|
nGenius Real-Time Monitor
|
Server Internal
|
UDP
|
1975
|
Shutdown Listener for PM Server
|
nGenius Real-Time Monitor
|
Server Internal
|
UDP
|
1976
|
Shutdown Listener for Watchdog
|
nGenius Real-Time Monitor
|
Server Internal
|
UDP
|
1977
|
Shutdown Listener for nGenius Native
|
nGenius Real-Time Monitor
|
Server Internal
|
UDP
|
9000
|
CSlistener (DFM server if port 162 is occupied)
|
Device Fault Manager
|
Device to Server
|
UDP
|
14004
|
Lock port for ANI Server singlet on check
|
Campus Manager
|
Server Internal
|
UDP
|
16236
|
UT Host acquisition
|
Campus Manager
|
Device to Server
|
UDP
|
42342
|
OSAGENT
|
CiscoWorks Common Services and Resource Manager Essentials
|
Server Internal (Commom Services); RSAC to Server via OSAGENT (RME)
|
UDP
|
42350
|
Event Services Software (ESS) (Alternate port is 44350/udp)
|
CiscoWorks Common Services
|
Server Internal
|
4 Upgrade Paths
You might already have the latest version of another CiscoWorks bundled product installed on your LMS bundled products. Review the information in Table 8 to determine what software is required for the LMS components to function properly.
Table 8 Recommended Upgrade Paths
If you are upgrading CiscoWorks LAN Management Solution (LMS) on a system that has...
|
Then do this
|
LMS 2.0 or 2.1 installed
|
Upgrade to LMS 2.2 using the instructions in this Quick Start Guide (Maintenance Kit).
|
LMS 1.1 or 1.2 installed
|
Upgrade to LMS 2.2 using the instructions in this Quick Start Guide (Maintenance Kit).
Note You may be asked to validate your DFM image if you are installing DFM using this Maintenance Kit CD (for CiscoWorks LAN Management Solution 2.2) during installation. See "Prerequisite for Installing DFM for LMS 1.x Users" section for details.
|
CiscoWorks Routed WAN Management Solution (RWAN) Release 1.2 or 1.1 installed
|
First upgrade to RWAN 1.3. Then install Campus Manager 3.3,
Device Fault Manager 1.2 Updated for Common Services 2.2, nGenius Real-Time Monitor 1.4 and nGenius Real-Time Monitor 1.4 SP6 using the instructions in this Quick Start Guide. See "Upgrade Options" section.
|
5 Upgrade Options
Table 9 describes the recommended sequence for upgrading individual LAN Management Solution 2.2 (LMS) component applications when prior versions of these components are already installed on your system.
Note For specific upgrading and installation instructions, see the installation documentation provided with each of the LMS components (See the "Related Documentation" section for details).
Table 9 Recommended Upgrade Sequence
If the following product is already installed...
|
And one or more of the following products are also already installed...
|
You should upgrade in the following order...
|
CD One, 5th Edition or CD One, 4th Edition
|
-
|
CiscoWorks Common Services 2.2
(Includes CiscoView 5.5)
|
Resource Manager Essentials 3.3
|
•CD One, 4th Edition
|
1. CiscoWorks Common Services 2.2 (Includes CiscoView 5.5)
2. Resource Manager Essentials 3.5
|
Resource Manager Essentials 3.4
|
•CD One, 5th Edition
|
1. CiscoWorks Common Services 2.2 (Includes CiscoView 5.5)
2. Resource Manager Essentials 3.5
|
Campus Manager 3.1
|
•CD One, 4th Edition
•Resource Manager Essentials 3.3
|
1. CiscoWorks Common Services 2.2 (Includes CiscoView 5.5)
2. Resource Manager Essentials 3.5
3. Campus Manager 3.3
|
Campus Manager 3.2
|
•CD One, 5th Edition
•Resource Manager Essentials 3.4
|
1. CiscoWorks Common Services 2.2 (Includes CiscoView 5.5)
2. Resource Manager Essentials 3.5
3. Campus Manager 3.3
|
Device Fault Manager 1.1
|
•CD One, 4th Edition
•Resource Manager Essentials 3.3
|
1. CiscoWorks Common Services 2.2 (Includes CiscoView 5.5)
2. Resource Manager Essentials 3.5
3. Device Fault Manager 1.2 Updated for Common Services 2.2
|
Device Fault Manager 1.2
|
•CD One, 5th Edition
•Resource Manager Essentials 3.4
|
1. CiscoWorks Common Services 2.2 (Includes CiscoView 5.5)
2. Resource Manager Essentials 3.5
3. Device Fault Manager 1.2 Updated for Common Services 2.2
|
nGenius Real-Time Monitor 1.3
|
-
|
1. nGenius Real-Time Monitor 1.4
2. nGenius Real-Time Monitor 1.4 SP6
|
nGenius Real-Time Monitor 1.4
|
-
|
nGenius Real-Time Monitor 1.4 SP6
|
6 Upgrading to LAN Management Solution 2.2
To upgrade an application, log in as root (on Solaris) or local administrator (on Windows) on the system on which you want to upgrade the application.
Before you begin:
•Check the factors to be considered before upgrading LMS 2.2. See "Prerequisites" section.
•Locate the PDF versions of the installation guides for each LMS application. Print them or have them open for viewing while you perform the upgrade. For details on locating the installation guides, see the application upgrade sections of this Quick Start Guide.
•Close all open or active programs. Do not run other programs during the upgrade process.
•Be aware of the following:
–You must upgrade CiscoWorks Common Services 2.2 before upgrading any other applications, except nGenius Real-Time Monitor 1.4 Service Pack 6.
–Once you have upgraded CiscoWorks Common Services 2.2, you must upgrade each LMS 2.2 application separately. While it is strongly recommended that you follow the "Order of Upgrade" section, you can upgrade the other applications of LMS 2.2 in any order.
–You may be asked to validate your DFM image if you are installing DFM using this Maintenance Kit CD (for CiscoWorks LAN Management Solution 2.2) during installation.
Prerequisites
This section describes the factors that you should consider before upgrading LMS 2.2.
Ensure you complete the following tasks before upgrade:
Step 1 Install required operating system upgrades. See "Server and Client System Requirements" section.
Step 2 Install required service packs. See "Server and Client System Requirements" section.
Step 3 Read "Important Upgrade Notes" section.
Important Upgrade Notes
This section contains important information that you should read before you begin upgrade:
•To ensure that you retain the latest device support and bug fixes for Resource Manager Essentials, Campus Manager and Device Fault Manager, you must install the latest Incremental Device Updates (IDU). For download locations, see "Additional Information Online" section.
Install IDU after upgrading the application.
•CiscoWorks applications are installed in the default directories:
–On Solaris: /opt/CSCOpx
–On Windows: SystemDrive:\Program Files\CSCOpx
If you select another directory during upgrade, the application is installed in that directory.
•On Solaris, if you select an upgrade directory different from the default, the /opt/CSCOpx directory is created as a link to the directory you selected. If you remove the link after upgrade, the product might malfunction.
•On Solaris, if errors occur during upgrade, check the upgrade log file /var/tmp/ciscoinstall.log.
On Windows, if errors occur during upgrade, check the upgrade log in the root directory on the drive where the operating system is installed. Each upgrade creates a new log file. For example, the CiscoWorks Common Services upgrade creates SystemDrive:\CiscoWorks_setupxxx.log, where xxx is the log file for the last CiscoWorks application upgraded.
•You can press Ctrl-C (on Solaris) or click Cancel (on Windows) at any time to end the upgrade. However, any changes to your system (for example, installation of new files or changes to system files) will not be undone.
On Solaris, we do not recommend ending the upgrade, using Ctrl-C. You will be required to manually cleanup the installation directories.
•If you want to use secure access between the client browser and the management server, you can enable or disable SSL from the CiscoWorks desktop.
If SSL is enabled:
–The URL begins with https instead of http to indicate a secure connection.
–The port number succeeding the server name is 1742 instead of 1741.
You cannot enable SSL on the CiscoWorks Server if there is an application that is not SSL-compliant installed on the Server.
For help with SSL, consult the User Guide for CiscoWorks Common Services 2.2.
You can find the User Guide for CiscoWorks Common Services 2.2:
–On Cisco.com, in both HTML and PDF form.
Log into Cisco.com. Select Products and Services > Network Management CiscoWorks > CiscoWorks CiscoView > Instructions and Guides > User Guide Books > User Guide for CiscoWorks Common Services 2.2
–On the CiscoWorks Common Services 2.2 (includes CiscoView) CD-ROM, in Adobe Acrobat PDF format.
From the CD-ROM root directory, look for \\Documentation\UserGuideForCommonServices.pdf
•Network inconsistencies might cause installation errors if you are upgrading from a remote mount point.
•Applications not supported by CiscoWorks Common Services 2.2 are disabled during upgrade.
•Device Fault Manager 1.2 Updated for Common Services 2.2 is not SSL compliant. You may be asked to validate your DFM image if you are installing DFM using this Maintenance Kit CD (for CiscoWorks LAN Management Solution 2.2) during installation.
If your CiscoWorks Management Server is integrated with any Network Management Station (NMS) in your network using the integration utility (Network Management Integration Module), you must perform the integration every time when you enable or disable SSL in the CiscoWorks Common Services 2.2 Server. You must do this to update the application registration in the NMS.
For help with NMS integration, consult the section "Integrating with Third-Party Vendors" section in Using CiscoView 5.5. You can find this document:
–On the installation CD-ROM, in Adobe Acrobat PDF form.
From the CD-ROM root directory, look for //Documentation/ug_ciscoview.pdf.
–On Cisco.com, in both HTML and PDF form.
Log into Cisco.com. Select Products and Services > Network Management CiscoWorks > CiscoWorks CiscoView > Versions and Options > CiscoWorks CiscoView 5.5, then select Using CiscoView 5.5.
For nGenius Real-Time Monitor
This section contains important information specific to nGenius Real-Time Monitor that you should read before you begin upgrade.
•nGenius Real-Time Monitor is not SSL compliant.
•nGenius Real-Time Monitor is installed in the default directories:
–On Solaris: /opt/NetScout
–On Windows: SystemDrive:\NetScout
•We recommend that you install nGenius Real-Time Monitor on a separate server for optimal performance. If you install nGenius Real-Time Monitor and Device Fault Manager (DFM) on the same server, it might result in a port conflict.
nGenius Real-Time Monitor uses ports 162 and 395 to listen for traps and events. If you are using nGenius Real-Time Monitor with DFM on the same server, you must configure DFM to forward traps to port 395. nGenius Real-Time Monitor will only accept traps forwarded from DFM.
For more information, see the Installation Guide for Device Fault Manger and the Supplement and Release Notes for NetScout nGenius Real-Time Monitor Release 1.4 Service Pack 6.
•If CiscoWorks and nGenius Real-Time Monitor are installed on different systems, or if nGenius was installed before CiscoWorks, you must manually copy the Cisco Management Connection (CMC) files to the location specified in the CiscoWorks installation.
After the CMC files are in place, you must reboot the system for the changes to take effect. Then, when you select nGenius Server, Traffic Monitor, Packet Analyzer, or Voice Monitor, an nGenius graphic is displayed in the main CiscoWorks window (Management Connection) and the selected application starts.
