Table Of Contents
LAN Management Solution, Release 1.3 (Maintenance Kit)
SUPPLEMENTAL LICENSE AGREEMENT
LAN Management Solution 1.3 Overview
Server and Client System Requirements
Solaris Patches for LAN Management Solution 1.3
LAN Management Solution Port Usage
Upgrading to LAN Management Solution 1.3
Upgrading CiscoWorks Common Services 2.2
Upgrading CiscoWorks Common Services 2.2 on Solaris
Upgrading CiscoWorks Common Services 2.2 on Windows
Upgrading Resource Manager Essentials 3.5
Upgrading Resource Manager Essentials 3.5 on Solaris
Upgrading Resource Manager Essentials 3.5 on Windows
Upgrading Campus Manager 3.3 on Solaris
Upgrading Campus Manager 3.3 on Windows
Upgrading to nGenius Real-Time Monitor
Upgrading to nGenius Real-Time Monitor 1.4
Upgrading nGenius Real-Time Monitor 1.4 Service Pack 6
Adding or Updating Devices in Inventory
Obtaining Technical Assistance
Obtaining Additional Publications and Information
Quick Start Guide
LAN Management Solution, Release 1.3 (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.
•
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 1.3 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
Device Fault Manager (DFM) is not a part of LMS 1.3. The DFM product CD-ROM provided with this Maintenance Kit is applicable for the LMS 2.2 customers.
To install DFM, you will require a previous licensed copy of DFM. If you do not have a DFM 1.2 (or earlier) CD-the installation cannot proceed. As you are a non DFM customer, you may not have a previous licensed copy of DFM. Contact your Cisco sales representative, if you wish to install DFM. Then follow the DFM installation instructions provided in the Quick Start Guide for LAN Management Solution, Release 2.2 (Maintenance Kit). This document comes in your product package.
LMS Contents
Table 1 describes the contents of the LAN Management Solution, Release 1.3 for Solaris and Windows.
Additional Information Online
Registered Cisco.com users can access the most current Incremental Device Updates, CiscoView Device Package Updates, 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
•
CiscoView Device Package Updates at
http://www.cisco.com/cgi-bin/Software/CiscoView/cvplanner.cgi
•
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 1.3:
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 includes:
•
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 includes:
•
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 10).
•
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 includes:
•
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.
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 1.3 server and client requirements.
•
Table 2 lists the server requirements for upgrading the LAN Management Solution 1.3 components on Solaris systems.
•
Table 3 lists the server requirements for upgrading the LAN Management Solution 1.3 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 1.3.
•
Table 7 lists the ports LAN Management Solution 1.3 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 RequirementHardware
•
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 recommended4
1 A Sun UltraSPARC II running Solaris 2.7 or 2.8 is the minimum recommended hardware configuration. If you plan to manage a network with more than 500 devices, or run other management solutions on the same server, an UltraSPARC III running Solaris 2.8 is strongly recommended.
2 LAN Management Solution 1.3 supports only the US English and Japanese versions of these operating systems. It does not support any other language versions. Set the default locale to US-English for the US-English version and Japanese for the Japanese version.
3 Upgrade Solaris patches, as required, for the Solaris version you are using. See the "Solaris Patches for LAN Management Solution 1.3" section.
4 To verify the file system: Enter df -k at the command prompt.
Table 3 Minimum Server Requirements for Windows Systems
Component Minimum RequirementHardware
•
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
1 LAN Management Solution 1.3 supports only the US English and Japanese versions of these operating systems. It does not support any other language versions. Set the default locale to US-English for the US-English version and Japanese for the Japanese version.
2 To verify the Service Pack version, select Start > Run, then enter winver.
3 This version of LMS does not support Terminal Services on Windows 2000 Advanced Server. Terminal Services must be turned off when you upgrade LMS.
4 Upgrade LMS 1.3 on an NTFS file system. Do not upgrade LMS 1.3 on a FAT file system. To verify the file system, open My Computer on the Windows desktop, right-click the drive and select Properties from the popup menu. The file system field appears in the General tab of the Properties dialog box.
Table 5 Browser Requirements
Browser Java Virtual Machine (JVM1 ) Version PlatformInternet Explorer (IE)
(recommended)5.0.0.3802 or later
IE 6.0 (6.0.26),
IE 6.0 SP1 (6.0.28) with patch Q810847Windows 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
1 To verify JVM, select View > Java Console in Internet Explorer and Communicator > Tools > Server > Java Console in Netscape Navigator. If Java Console is not listed in View, you must enable it. To enable Java Console, in Internet Explorer, select Tools > Internet Options > Advanced. In the JVM section, select the Java Console option. Restart Internet Explorer.
2 For Windows XP Professional, SP1 must be installed. Windows XP professional is not packaged with JVM. JVM is installed after you install Windows XP SP1. Windows XP SP1a should not be installed.
Solaris Patches for LAN Management Solution 1.3
Table 6 lists the Solaris patches for the LAN Management Solution 1.3.
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 www.sunsolve.sun.com.
Table 6 Solaris Patches for LAN Management Solution 1.31
Operating System Required RecommendedSolaris 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
1 Use the showrev -p command to verify that these patches have been applied.
LAN Management Solution Port Usage
This section provides a list of ports used by the various CiscoWorks components.
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 thisLMS 1.2 or 1.1 installed
Upgrade to LMS 1.3 using the instructions in this Quick Start Guide (Maintenance Kit).
CiscoWorks Routed WAN Management Solution (RWAN) Release 1.2 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.RWAN 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 1.3 (LMS) component applications when prior versions of those components are already installed on your system.
Note
For specific upgrading and installation instructions, refer to the installation documentation provided with each of the LMS components (see the "Related Documentation" section).
6 Upgrading to LAN Management Solution 1.3
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 1.3. 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 1.3 application separately. While it is strongly recommended that you follow the "Order of Upgrade" section, you can upgrade the other applications of LMS 1.3 in any order.
Prerequisites
This section describes the factors that you should consider before upgrading LMS 1.3.
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 and Campus 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.
•
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 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.
For more information, see 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.
The nGenius system administrator can create the same users and apply the same privileges from CiscoWorks to the nGenius system. See Supplement and Release Notes for NetScout nGenius Real-Time Monitor Release 1.4 Service Pack 6 for details.
Order of Upgrade
Upgrade each application of LMS 1.3 in the following order:
Step 1
Upgrade CiscoWorks Common Services 2.2. See "Upgrading CiscoWorks Common Services 2.2" section.
Step 2
Upgrade Resource Manager Essentials 3.5. See "Upgrading Resource Manager Essentials 3.5" section.
Step 3
Upgrade Campus Manager 3.3. See "Upgrading Campus Manager 3.3" section.
Step 4
Upgrade nGenius Real-Time Monitor 1.4. See "Upgrading to nGenius Real-Time Monitor" section.
7 Upgrading CiscoWorks Common Services 2.2
Upgrading CiscoWorks Common Services takes approximately 40 minutes.
Before you begin:
•
Verify that the server on which you intend to upgrade CiscoWorks Common Services 2.2 with CiscoView 5.5, meets the requirements listed in the tables in the"Server and Client System Requirements" section.
•
If the server has other Cisco bundled products already installed, which use CD One or CiscoWorks already installed, you must follow the recommended upgrade actions described in the "Upgrade Paths" section.
•
If the server has CD One already installed, you must follow the recommended upgrade actions described in the "Upgrade Options" section.
Upgrading CiscoWorks Common Services 2.2 on Solaris
Step 1
Locate Installation and Setup Guide for CiscoWorks Common Services (Includes CiscoView 5.5) on Solaris. The document is available:
•
On the installation CD-ROM, in Adobe Acrobat PDF form.
From the CD-ROM root directory, look for CD-ROMDrive/Documentation/InstallSetupGuideForComSerCVSol.pdf
•
On Cisco.com, in both HTML and PDF form.
Log into Cisco.com. Select Products and Services > Network Management CiscoWorks. Navigate to CiscoWorks Common Services 2.2, then select Installation and Setup Guide for CiscoWorks Common Services (Includes CiscoView 5.5) on Solaris.
Step 2
In Chapter 2, "Installing CiscoWorks Common Services", read the section "Preparing to Install CiscoWorks Common Services". As explained in that section, be sure you:
•
Have root access to the server on which you plan to upgrade CiscoWorks Common Services.
•
Know the server's IP address.
•
Verify that the TCP ports that CiscoWorks Common Services uses will not create conflicts with existing applications. For details, see Table 7 in this document.
Step 3
Determine the password that you want the CiscoWorks Common Services administrator to use. For rules to follow when forming passwords, see the section "Admin Password" in Appendix C, "Password Information".
Step 4
Follow the steps in the section "Performing an Upgrade Installation", in Chapter 2, "Installing CiscoWorks Common Services". While performing the upgrade:
•
If you are performing a local upgrade: Back up your data.
To perform this task, follow the steps in "Backing Up Your Data" in Chapter 2.
•
If you are performing a remote upgrade: Export your data to a new installation.
To perform this task, follow the steps in "Exporting the Data" in Chapter 2.
•
Select an Express upgrade.
Select a Typical or Custom upgrade only if you want to specify a destination directory other than the default or want to set other CiscoWorks parameters. For details on the parameters you can set, see Appendix D, "User Inputs for the Installation".
If you select a Typical or Custom upgrade, you must upgrade all products. Otherwise, LMS will not function correctly.
Step 5
After you complete the upgrade, prepare to use CiscoWorks Common Services by:
a.
Configuring the CiscoWorks server.
b.
Configuring your client.
c.
Accessing the CiscoWorks navigation tree.
Follow the steps in Chapter 3, "Preparing to Use CiscoWorks".
If you receive error messages during the upgrade, or cannot complete the tasks in this step, see Appendix A, "Troubleshooting the Installation".
Upgrading CiscoWorks Common Services 2.2 on Windows
Before you begin:
•
If you are using Windows, do not use a cloned version of the administrator account.
•
On Windows, when prompted to replace a newer file with an older file, you should always keep the newer file.
•
On Windows, do not select an encrypted directory for upgrade. CiscoWorks Common Services 2.2 does not support directory encryption.
Step 1
Locate Installation and Setup Guide for CiscoWorks Common Services (Includes CiscoView 5.5) on Windows. The document is available:
•
On the installation CD-ROM, in Adobe Acrobat PDF form.
From the CD-ROM root directory, look for CD-ROMDrive\Documentation\InstallSetupGuideForComSerCVWin.pdf
•
On Cisco.com, in both HTML and PDF form.
Log into Cisco.com. Select Products and Services > Network Management CiscoWorks. Navigate to CiscoWorks Common Services 2.2, then select Installation and Setup Guide for CiscoWorks Common Services (Includes CiscoView 5.5) on Windows.
Step 2
In Chapter 2, "Installing CiscoWorks Common Services", read the section "Preparing to Install CiscoWorks Common Services". As explained in that section, be sure you:
•
Verify that the server on which you plan to upgrade CiscoWorks Common Services is not configured as a domain controller, does not use the FAT file system, and does not have Windows XP installed.
•
Have installed all of the required Windows software on the server.
•
Verify that the TCP ports CiscoWorks Common Services uses will not create conflicts with existing applications. For details, see Table 7 in this document.
Step 3
Determine the password that you want the CiscoWorks Common Services administrator to use. For rules to follow when forming passwords, see the section "Admin Password" in Appendix B, "Password Information".
Step 4
Follow the steps in the section "Performing an Upgrade Installation", in Chapter 2, "Installing CiscoWorks Common Services". While performing the upgrade:
•
If you are performing a local upgrade: Back up your data.
To perform this task, follow the steps in "Backing Up Your Data" in Chapter 2.
•
If you are performing a remote upgrade: Export your data to a new installation.
To perform this task, follow the steps in "Exporting the Data" in Chapter 2.
•
Select an Express upgrade.
Select a Typical or Custom upgrade only if you want to specify a destination directory other than the default or want to set other CiscoWorks parameters. For details on the parameters you can set, see Appendix D, "User Inputs for the Installation".
If you select a Typical or Custom upgrade, you must upgrade all products. Otherwise, LMS will not function correctly.
Step 5
After you complete the upgrade, prepare to use CiscoWorks Common Services by:
a.
Configuring CiscoWorks Server.
b.
Accessing the CiscoWorks navigation tree.
Follow the steps in Chapter 3, "Preparing to Use CiscoWorks Common Services".
If you receive error messages during the upgrade, or cannot complete the tasks in this step, see Appendix A, "Troubleshooting the Installation".
8 Upgrading Resource Manager Essentials 3.5
Upgrading Resource Manager Essentials takes approximately 30 minutes.
Upgrading Resource Manager Essentials 3.5 on Solaris
Step 1
Locate Installation and Setup Guide for Resource Manager Essentials on Solaris. The document is available:
•
On the product CD-ROM, in Adobe Acrobat PDF form.
From the CD-ROM root directory, look for CD-ROMDrive/Documentation/InstallSetupGuideForEssentialsSol.pdf
•

