Guest

CiscoWorks Routed WAN Management Solution

Read Me First -- Routed WAN Management Solution 1.2 Update

  • Viewing Options

  • PDF (548.5 KB)
  • Feedback
Routed WAN Management Solution 1.2 Bundle Update

Table Of Contents

Routed WAN Management Solution 1.2 Bundle Update

SUPPLEMENTAL LICENSE AGREEMENT

What the Bundle Contains

New Features

CD One, 5th Edition

Resource Manager Essentials 3.4

Access Control List Manager 1.4

Internetwork Performance Monitor 2.4

nGenius Real-Time Monitor 1.4

Hardware and Software Requirements

Server Requirements

Client Requirements

Installing the Bundle

Installing RTM 1.4

Upgrading CD One

Upgrade Paths

Upgrading on Solaris

Upgrading CD One—Local Upgrade

Upgrading CD One—Remote Upgrade

Upgrading on Windows

Upgrading CD One—Local Upgrade

Upgrading from CD One, 4th Edition—Remote Upgrade

Upgrading Essentials

Upgrade Paths

Upgrading Essentials on Solaris

Backing Up Your Previous Database

Running the Installation Program on Solaris

Backing Up the Converted Database

Upgrading Essentials Data from a Remote system

Upgrading Essentials on Windows

Running the Installation Program on Windows

Upgrading Essentials Data from a Remote system

Upgrading ACL Manager

Upgrading ACL Manager on Windows

Upgrading ACL Manager Data from a Remote Windows Machine

Upgrading ACL Manager on Solaris

Upgrading ACL Manager Data from a Remote Solaris Machine

Upgrading IPM

Upgrading from Previous Releases of IPM

Migration Path for IPM 2.4

Migrating Remote Data on Windows

Migrating Remote Data on Solaris

Installing IPM on Windows

Installing IPM on Solaris

Upgrading CD One and CiscoWorks on an IPM Installation

Upgrading nGenius Real-Time Monitor

Prerequisites

Upgrading to nGenius Real-Time Monitor 1.4

Upgrading from nGenius Real-Time Monitor 1.3

Upgrading from nGenius Real-Time Monitor 1.2

Obtaining Documentation

World Wide Web

Ordering Documentation

Documentation Feedback


Routed WAN Management Solution 1.2 Bundle Update


The Routed WAN Management Solution (RWAN) 1.2 Bundle Update provides updates for the RWAN applications on the Solaris and Windows platforms.

SUPPLEMENTAL LICENSE AGREEMENT

What the Bundle Contains

New Features

Hardware and Software Requirements

Installing the Bundle

Upgrading CD One

Upgrading Essentials

Upgrading ACL Manager

Upgrading IPM

Upgrading nGenius Real-Time Monitor

Obtaining Documentation

SUPPLEMENTAL LICENSE AGREEMENT

SUPPLEMENTAL LICENSE AGREEMENT FOR CISCO SYSTEMS NETWORK MANAGEMENT SOFTWARE: CiscoWorks ROUTED WAN 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.

1. 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:

CiscoView/ CD One (CD One): 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 CD One 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.

Access Control List Manager (ACL Manager): May be installed on one (1) server in Customer's network management environment.

Internetwork Performance Monitor (IPM): 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.

2. DESCRIPTION OF OTHER RIGHTS AND LIMITATIONS.

Please refer to the Cisco Systems, Inc. Software License Agreement.

What the Bundle Contains

The Routed WAN Management Solution 1.2 (RWAN) provides a collection of powerful management applications to configure, administer, monitor, and troubleshoot a routed wide-area network. Products in the bundle include:

CD One, 5th Edition (CD One): The most widely used Cisco graphical device management application is now Web-based, providing WAN managers with browser access to real-time device status, operational and configuration functions. CD One includes CiscoWorks2000 Server, CiscoView, and Integration Utility.

Resource Manager Essentials 3.4 (Essentials): This product provides network inventory and device change management, network configuration, software image management, network availability, and syslog analysis. It also offers powerful integration links to Cisco.com.

Access Control List Manager 1.4 (ACL Manager): This Web-based tool significantly reduces the time required to set up, manage, and optimize Cisco IOS and CatOS software-based IP and Internet Packet Exchange (IPX) traffic filtering and device ACLs.

Internetwork Performance Monitor 2.4 (IPM): This application enables wide-area network (WAN) managers to troubleshoot network response times and availability proactively, using instrumentation inside the devices on the network.

NetScout nGenius Real-Time Monitor 1.4 (RTM)—Web-based system designed to manage and monitor the packets, application and protocol traffic in the network. It 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.


Note In addition to the enclosed paper documents, PDF versions of product documentation are available on the product CDs. See the installation instructions for individual application and print out the relevant documentation before proceeding with the installation. You can also order printed copies of documentation using the sources in the "Obtaining Documentation" section.


New Features

This section highlights updates for each component of this Bundle Update release.

All RWAN applications are now supported on Windows 2000 Server, Windows 2000 Professional, and Solaris 2.7 and 2.8. Note that this version of RWAN does not support Windows 2000 Advanced Server.


Note For more detailed information on the new features and for the latest list of supported devices, see the accompanying release notes.


CD One, 5th Edition

CD One provides these new features:

Secure Socket Layer (SSL) encryption to provide secure access between the client browser and management server, and Secure Shell (SSH) to provide secure access between the management server and devices.

Enhanced installation and runtime system security. To improve the security of the product, you can change your login (Admin or Guest user) and database passwords during install (for Windows 2000 only). Your own casuser password supports Windows 2000 strong enhanced password.

Export/Import user information from one CD One server to another server. You can create users in one server and import them to all the other servers.

Provides link to Cisco Feature Navigator (CFN), a tool available on www.cisco.com/go/fn. It enables you to choose the device images based on the features you want to run on your networks.

Protocol and device list import from Resource Manager Essentials through SSL.

Built-in patch for addressing Java issues used to transfer screens to browsers.

Support for several new Cisco devices, Cisco IOS extended features, and Cisco voice applications.

Device package enhancements for several Cisco products, including AS5350, AS5400, Router 12000, IAD2400, Metro 1500, and URM (1.0).

New five-year certificates used to sign JAR files.

Resource Manager Essentials 3.4

Essentials provides these new features:

Support for downloading and uploading of device configurations via Secure Shell (SSH) protocol.

Secure communication between the client browser and the Resource Manager Essentials server via Secure Socket Layer (SSL) protocol.

Configuration management for devices across Network Address Translation (NAT) boundaries.

Support for Interactive IOS, CatOS and FastSwitch commands in the NetConfig applications.

Up-to-date inventory of all Cisco devices in the network, including support for Cisco Call Manager and VPN Concentrator 3000 (VPN c3000).

Copy command enhancement of Network Show Commands facility.

Ability to isolate and view PIX firewall configuration statements.

Summarizes syslog events by severity or user criteria for PIX firewalls.

New five-year certificates used to sign JAR files.

Support for new devices including the following:

Cisco Router 7400 Series (7401 ASR-BB, 7401 ASR-CP)

Cisco 7600 Series (7603, 7606, 7609)

Cisco Router 7304

PIX Firewall (506, 515, 520, 525, 535, 501, 506E, 515E)

Cisco ONS Series (ONS 15540 ESP)

Cisco 1700 Series (1710, 1760)

Integrated Access Device (IAD 2420)

Catalyst 6000 Series (6513)

Gigabit Switch Router (GSR) 12400 (12404, 12406, 12410, 12416)

Cisco RPM-PR

Cisco Aironet AP Series (340, 350)

Cisco 4000 Series (C4224)

Cisco Content Service Switch 11000 Series (11050, 11080, 11150)

Network Analysis Module (Catalyst 6000 module)

Access Control List Manager 1.4

ACL Manager 1.4 provides these new features:

Creating and editing named and numbered ACLs.

Options for saving configuration files to disk.

Support for optimizing ACL statements to eliminate redundancies.

Support for optimizing ACL statements based on hits count.

Printing of ACLs, ACEs, optimization details, and difference data.

Ability to back up ACL Manager data for disaster recovery using the integrated CiscoWorks Backup tasks.

SSH and SSL support for the ACL Manager client.

Full support for:

IP and IP_EXTENDED

IPX and IPX_EXTENDED

IPX_SAP

IPX_SUMMARY

RATE_LIMIT_MAC

RATE_LIMIT_PRECEDENCE

VACL IP, VACL IPX and VACL MAC ACLs.

Support for VACLs on Private VLANs.

Support for Catalyst OS releases 5.3 CSX through 7.1.

Support for Cisco IOS releases 10.3 through 12.2.

SNMP access to Cisco routers controlled through ACLs. ACLs can control and restrict packet filtering and line access, SNMP server access control, and SNMP access to a device, and can limit TFTP servers used via SNMP.

New device support, including:

Cisco 801, 802, 805

Cisco uBR-904, uBR-905, uBR-924

Cisco 1710, 1750, 1751, 1760

Cisco IAD 2420

Cisco 2650, 2651

Cisco uBR-7246 VXR

Cisco 7507Z, 7507MX, 7513Z, 7513MX

Cisco 7304, 7401, 7603, 7606, 7609 (7603, 7606, 7609 are also supported on hybrid images running CatOS.)

Cisco ESR-10005, ESR-10008

Cisco uBR 10012

Gigabit Switch Router series: 12404, 12406, 12416

Catalyst 2950C-24

Catalyst 3550-12T, 3550-24, 3550-48

Catalyst 4006 Supervisor III

Catalyst 6006, 6009, 6506, 6509, 6513 (all these switches, running CatOS and the native IOS, are supported).

Internetwork Performance Monitor 2.4

IPM provides these new features:

Support for HTTP performance collector (for static URLs as targets of performance operations).

Support for viewing the IPM collector SAAs in the running configuration, by setting the ipm.env file's IPM-NVRAM_ENABLE to 1.

The ability to change the IPM database password and enable the administrative password during installation. It is strongly recommended that you enable the administrative password, to ensure the configuration is secured properly.

Improved graphing, including multi-graphing.

Path usage report, showing distribution paths taken between source and target.

Automatic baselining of collector thresholds.

Global edit of IPM operation applied to all IPM collectors.

Enhanced database export capabilities.

Improved IPM process startup time. The IPM processes are now fine-tuned to start instantly.

Support for a new IPM Collector status: Operation Pending State for the IPM collector in the IPM main window now shows when IPM is in the process of configuring collectors.

Support to add a source or target using IP Address and Host Name. You no longer need to make the devices Reverse Address Resolvable.

Support for terminal server on Windows 2000.

Improved CiscoWorks2000 desktop integration, including launching IPM online help from the desktop.

nGenius Real-Time Monitor 1.4

nGenius Real Time Monitor provides these new features:

Support for Differentiated Services—DSMON allows different classes of traffic to be accorded prioritized Quality of Service (QoS) treatment while flowing through the network. DSMON data is displayed in Traffic Monitor.

Asynchronous Device Configuration—Provides the ability to perform concurrent device processing; for example, adding, deleting, or configuring devices. When you initiate a task, a Task Progress Report provides asynchronous device status feedback such as warnings and errors.

Server Load Detection—nGenius Real-Time Monitor proactively monitors the nGenius Server to prevent poor performance or abnormal shutdowns. If disk space, memory usage, or server overload thresholds are exceeded, an alarm is triggered and the nGenius Server executes a script to notify you by e-mail.

Bulk Device Add — Allows you to add multiple devices using a comma separated values (.csv) file.

Hardware and Software Requirements

Server Requirements

You can install the RWAN 1.2 bundle CDs on:

Solaris

Windows 2000

Table 1 provides the server requirements for installing all of the RWAN bundle CDs on a single server. Dual processor systems are required for hosting multiple management solutions on either software platform.

The requirements listed in Table 1 are based on managing 500 devices with both RWAN and LAN Management Solution (LMS) loaded on a single server. If your RWAN applications are distributed on multiple servers or you have chosen not to install some of them, the minimum requirements may be less than those given in Table 1. If you are managing more than 500 devices or you are running additional Cisco or third-party applications on the servers, the requirements may be higher. See the individual RWAN application installation guides for specific product requirements.

You can install RWAN 1.2 on the same server with other CiscoWorks2000 applications only if all these applications support CD One, 5th Edition. For example: RWAN 1.2 can reside on the same server with LMS 1.2 or 2.1, but not LMS 1.1 or 2.0. CiscoWorks2000 solutions supporting different versions of CD One cannot reside on the same server because they share common resources, such as the Web server, common management desktop, and user security system. Users with large networks will usually find it more desirable to host the applications on separate servers. A table of server sizing recommendations is included in the RWAN and LMS documentation available online on Cisco.com.


Note Installing IPM 2.4 on a separate server is required in order to enable secure SSL/SSH communications among the RWAN components. See the "Installing the Bundle" section. RTM must also be installed on a dedicated server. See the "Installing RTM 1.4" section.


Table 1 RWAN Server Requirements

Requirement Type
Windows 2000
Solaris

Hardware

IBM PC-compatible computer with 550 MHz or faster Pentium III (dual processor required for hosting multiple management solutions)

CD-ROM drive

Sun UltraSPARC 60 MP with 440 MHz or faster processor (dual processor required for hosting multiple management solutions)

Sun UltraSPARCIII (Sun Blade 1000 Workstation or Sun Fire 280R Workgroup Server) (dual processor required for hosting multiple management solutions)

CD-ROM drive

Memory (RAM)

1 GB RAM

1 GB RAM (UltraSPARCIII Workstation or UltraSPARC 60 MP)

2 GB RAM (UltraSPARCIII Server)

8 MB E-Cache (both)

Available disk drive space

9 GB minimum

2 GB virtual memory

9 GB, with 2 GB swap space (UltraSPARC 60 MP)

36 GB internal FC-AL disk drive (UltraSPARCIII Workstation)

Dual 36 GB internal FC-AL disk drives (UltraSPARCIII Server)

Software1

Windows 2000 Server or Professional edition with Service Pack 2. 2

Solaris 2.7 or 2.83

1 CD One supports only the US English and Japanese versions of these operating systems. Set the default locale to US English.

2 Do not install on a FAT file system. This version of RWAN does not support Windows 2000 Advanced Server.

3 Please see the installation documentation for more information on required operating system patches.


Client Requirements

Table 2 provides the client requirements for the RWAN bundle.

Table 2 RWAN Client Requirements

Requirement Type
Minimum Requirement

System software and hardware1

Any one of these systems:

IBM PC-compatible computer with 300 MHz Pentium processor, 256 MB RAM, and 512 MB virtual memory; running Windows NT 4.0 (Workstation or Server) with Service Pack 6a, Windows 98, or Windows 2000 Server or Professional edition with Service Pack 2.

Sun UltraSPARC 10 with 333 MHz processor, 256 MB RAM, and 512 MB swap space; running Solaris 2.7 or 2.8.

IBM RS/6000 workstation with 256 MB RAM and 512 MB swap space, running AIX 4.3.3.

HP9000 series with 256 MB RAM and 512 MB swap space, running HP-UX 11.0. (RTM 1.3 is not yet supported by Cisco Systems on HP-UX clients; future support is planned.)

Color monitor with video card set to 256 colors.

Browser2

One of these browsers:

Solaris: Netscape Navigator 4.76

HPUX and AIX: Netscape Navigator 4.77, 4.78, or 4.79

Windows 98/NT/2000: Netscape Navigator 4.77, 4.78, or 4.79; Microsoft Internet Explorer 5.5 (with Service Pack 2), or 6.0.

1 Please see the installation documentation for individual RWAN applications for detailed information on required operating system patches.

2 Please see the installation documentation for individual RWAN applications for more information on required operating system patches, browser plug-ins, and Java Virtual Machine (JVM) versions.


Installing the Bundle

To install an application, log in as the local administrator (on Windows) or root (on UNIX) on the system on which you want to install an application. Table 3 describes the recommended order in which you should install the RWAN applications, and prerequisites for each installation.

If you want to enable secure communications among the RWAN components, you must install IPM on a server separate from the other RWAN components. Installing IPM on a separate server is recommended, as it not only enables secure communications for other RWAN components, but also helps distribute server load for users with large networks. If you choose to install IPM on a separate server, you must install it with CD One, in the following order:

1. CD One, 5th Edition (CD One)

2. Internetwork Performance Monitor (IPM) 2.4

While it is possible to install IPM on a separate server without CD One, this is not recommended, as it will disable important IPM functions, including the Web reports and data export features.

If you are planning to upgrade an existing IPM installation on Windows, see the "Upgrading CD One and CiscoWorks on an IPM Installation" section.


Note You must install CD One before installing any other applications, except
RTM 1.4. For more information on installing RTM 1.4, see "Upgrading nGenius Real-Time Monitor" section.


Following are additional tips and guidelines to bear in mind while installing the upgraded RWAN applications:

You can enable or disable SSL from the CiscoWorks2000 desktop, if you want to use secure access between the client browser and the management server. For more information, see the User Guide for CiscoWorks2000 Server. You cannot enable SSL if there is a non SSL-compliant application, such as IPM, installed on CiscoWorks2000 server.

If your CiscoWorks2000 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 you enable or disable SSL in the CiscoWorks2000 Server. You must do this to update the application registration in the NMS. For more information, see the "Integrating with Third-Party Vendors" section in the CiscoView online help.

CiscoWorks2000 applications are installed in the default directory /opt/CSCOpx (on Solaris) or c:\Program Files\CSCOpx (on Windows). If you select another directory during installation, the application is installed in that directory. On Solaris, if you select an installation directory different from the default, the /opt/CSCOpx directory is created as link to the directory you selected. If you remove the link after installation, the product might malfunction.

Close all open or active programs before beginning installation. Do not run other programs during the installation process.

Network inconsistencies might cause installation errors while installing from a remote mount point.

You can press Ctrl-C (on Solaris) or click Cancel (on Windows) at any time to end the installation. However, any changes to your system (for example, installation of new files or changes to system files) will not be undone.

If errors occurred during installation, check the installation log file /var/tmp/ciscoinstall.log or c:\cw2000_inNNN.log.

If you are using Windows 2000, 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 choose the newer file.

On Windows, when prompted to do so by an installation, you should always reboot your system.

On Windows, do not select an encrypted directory for installation. CiscoWorks2000 does not support directory encryption.

For troubleshooting information, see the Troubleshooting appendices in the product-specific documentation.

For mounting and unmounting instructions, see the mounting and unmounting appendices in the product-specific documentation.

If you are upgrading from a previous version of Essentials and have integrated Essentials with Netsys, please read the Netsys integration upgrade procedures in Installation and Setup Guide for Resource Manager Essentials on Windows 2000, Chapter 2, "Before Installing CD One."

Table 3 Installation Tasks for RWAN Bundle 

Task, Approximate Time
For Detailed and Custom Installation, See
Prerequisites

1. Install CD One, 5th Edition.

Approx. installation time: 40 minutes

Installation and Setup Guide for CD One, 5th Edition (Solaris or Windows 2000 version)1

Release Notes for CD One, 5th Edition (Solaris or Windows 2000 version)2

All required (or desired) operating system upgrades have been performed, and service packs installed.1

All installed applications support CD One, 5th Edition

2. Install Resource Manager Essentials 3.4.

Approx. installation time: 30 minutes

Installation and Setup for Guide for Resource Manager Essentials (Solaris or Windows2000 version)1

Release Notes for Resource Manager Essentials 3.4 (Solaris or Windows 2000 version)2

All required (or desired) operating system upgrades have been performed and service packs installed.1

CD One, 5th Edition is installed.

All installed applications are supported by CD One, 5th Edition

3. Install Access Control List Manager 1.4.

Approx. installation time: 10 minutes

Installation and Setup Guide for ACL Manager, Software Release 1.41

Release Notes for ACL Manager 1.4 on Solaris and Windows2

4. Install Internetwork Performance Monitor 2.4

Approx. installation time: 15 minutes

Installation Guide for Internetwork Performance Monitor, Software Release 2.41

Release Notes for Internetwork Performance Monitor 2.42

1 See the installation documentation for required and optional operating system upgrades. All installation documentation is available in PDF form on the RWAN CD-ROMs, in the Documentation directory. Viewing the PDFs requires Adobe Acrobat Reader v4.0 or later.

2 See the release notes for any last-minute updates.


Installing RTM 1.4

You must install nGenius Real-Time Monitor 1.4 on a dedicated system. Failing to install nGenius Real-Time Monitor on a dedicated system will severely impact performance.

Table 4 Installation Sequence for RTM 1.4

Task Sequence
For Detailed and Custom Installation, See
Prerequisites

Install nGenius Real-Time
Monitor 1.4.

Approx. installation time: 05-15 minutes

NetScout nGenius Real-Time Monitor 1.4 Installation Guide

Supplement and Release Notes for NetScout nGenius Real-Time Monitor Release 1.4 (Cisco document)1

nGenius Real-Time Monitor 1.4 Release Notes (NetScout Systems document)1.

None

1 See Release Notes for any last-minute updates


Following are additional tips and guidelines to bear in mind while installing the RTM:

Do not install RTM on a Windows system that has the server name nGenius.

Before installing RTM, it is recommended that you have 300 MB of space available in the /tmp or Temp directory.

Upgrading CD One

CD One, 5th edition supports upgrade from only CD One, 4th edition. Upgrade from other CD One releases is not supported. The data is preserved when you perform an upgrade.

You can upgrade to the new version of CD One using either of two methods. You can perform a local upgrade by installing the new version on the system currently running a previous version. To perform a local upgrade, see the "Upgrading CD One—Local Upgrade" section.

As an alternative, you can perform a remote upgrade by installing
CD One, 5th Edition, on a new system, and exporting essential data from the system running the CD One, 4th edition to the new system. To perform a remote upgrade, see the "Upgrading CD One—Remote Upgrade" section.


Note If you plan to upgrade CD One or CiscoWorks2000 on a Windows machine on which IPM was previously installed, see the instructions in the "Upgrading CD One and CiscoWorks on an IPM Installation" section.


Upgrade Paths

Table 5 describes the different local upgrade paths and results. See the product installation guides for detailed installation instructions.

Table 5 Upgrade Paths for CD One

Existing Software
Results

Clean system

CD One, 5th Edition is installed in the specified directory.

CD One, 5th Edition

Reinstallation of CD One, 5th Edition overwrites the previously installed
CD One components. All data is preserved.

CD One, 4th Edition

CD One, 5th Edition overwrites the previously installed CD One components. All data is preserved.


Upgrading on Solaris

Upgrading CD One—Local Upgrade

You can upgrade from CD One, 4th Edition only. Upgrade from other lower versions of CD One is not supported.

To perform a local upgrade:

Back up your data—This is optional. You can save your data to a backup file before you perform the local upgrade. If your installation fails, you can retrieve this saved data. See "Backing Up Your Data".

Install a patch—You must install a patch on the old system before you can begin installing CD One, 5th Edition. This patch suspends all currently scheduled job data. Necessary data can then be exported during upgrade to the new version. See "Installing the Patch".

Run the installation program. See "Running the Installation Program on Solaris".

Backing Up Your Data


Step 1 Access the CiscoWorks2000 desktop and log in. For information, see the User Guide for CiscoWorks2000 Server.

Step 2 Select Server Configuration > Administration > Database Management > Back Up Data Now.

The Back Up Data Now dialog box appears.

Step 3 Enter the path name of the target directory. It is recommended that you use a different directory from the directory where CiscoWorks2000 is located, for example, /cw2000/backups on Solaris and c:\cw2000\backups.

To begin the backup, click Finish.

This process might take some time to complete.


Installing the Patch

To install the patch:


Step 1 As root, mount the CD One CD-ROM using either of the following methods:

Mount the CD-ROM on the CD One server system.

Mount the CD-ROM on a remote Solaris system, then access the
CD-ROM from the CD One server system.

See the product installation guide for detailed mounting instructions.

Step 2 At the command line, enter:

perl patch_1x_20.pl

The patch copies the file DisableJobs.class to the runtime installation directory.

Step 3 Make sure that daemon manager is up and running on the server. Also, make sure that the jrm process is up and running. For information on process management, see the product installation guide.

Step 4 At the command line, enter:

setenv LD_LIBRARY_PATH /opt/CSCOpx/objects/db/lib:/opt/CSCOpx/lib

Step 5 At the command line, enter:

cwjava -cw install_directory com.cisco.nm.cmf.jrm.DisableJobs

where install_directory is the directory where CD One, 4th edition was installed. (/opt/CSCOpx is the default).

The class file suspends all the jobs and creates a list of job IDs for the suspended jobs and other job information in a file called joblist.jrm. The file joblist.jrm is saved in $NMSROOT/setup. Jobs are re-enabled as part of the upgrade process for individual applications.


After the patch is installed, you can install CD One, 5th Edition.

Running the Installation Program on Solaris

To run the installation program:


Step 1 As root, mount the CD One CD-ROM using either of the following methods:

Mount the CD-ROM on the CD One server system.

Mount the CD-ROM on a remote Solaris system, then access the
CD-ROM from the CD One server system.


Caution Network inconsistencies might cause installation errors while installing from a remote mount point.

See the product installation guide for detailed mounting instructions.

Step 2 Run the installation program.

For a local installation, enter:

# cd /cdrom/cdrom0/
# ./setup.sh 

For a remote installation, enter:

# cd remotedir
# ./setup.sh

where remotedir is the remote location where the CD-ROM is mounted.

The following message might appear:

Warning: User casuser already exists, the installation process will 
overwrite its privilege.

This message will not appear if this is the first time CD One is installed on this system.

Press Enter if you receive the casuser message.

The installation program adds the new user casuser and the new group casusers to the system.

Step 3 Select one of the following:


Note If CD One has previously installed on this system, the list of components will be different.


1. NMS Integration Utility to install only the Integration Utility—For information about the Integration Utility and third-party NMS integration, see Using CiscoView.

2. Common Management Foundation (CMF) Base Desktop to install a subset of CMF—Select this option only if the application you'll be installing next requires the CMF Base Desktop and you do not want CiscoView or NMS Integration Utility installed.

3. CiscoView to install CiscoView only.

4. CiscoView, NMS Integration Utility and CMF to install all CD One components. This option is recommended for most systems.


Note If CD One has previously been installed on this system, the product will automatically be installed in the same location at which CD One was previously installed.


Step 4 Enter the number corresponding to the option you have chosen or enter q to quit.

The installation program performs several preinstallation and dependency checks on your system, such as TCP/IP address resolution, TCP/IP port use, disk space, and RAM. These preinstallation checks cause some text to appear on the window.

The Installation program displays:

For security reasons, Cisco recommends that you change the default 
password for Admin user. Do you want to change it now? (y/n)

If you enter Y, the installation program allows you to change the password.

The Installation displays prompts allowing you to change the default passwords for Admin user, Guest user, and the CMF and ANI database.

Step 5 Enter a new password, and confirm it.

The installation program continues and information about the Integration Utility appears.

If your previous version of CiscoWorks2000 is already integrated with a third-party NMS, go to Step 7. If your previous version of CiscoWorks2000 is not already integrated with a third-party NMS, a message appears:

The Integration Utility will be installed now. The Integration Utility 
integrates Cisco device packages and Cisco applications into a 
third-party SNMP management platform. You can choose to integrate with 
a third-party SNMP management platform during this install or later.

Do you want to integrate with the third-party product now (y/n)? [n]


Note For information about the Integration Utility, see Using CiscoView.


Step 6 Select one of the following:

n to integrate with a third-party NMS after installation (this is the recommended choice to complete the installation more quickly, and to avoid installation failure due to errors in the third-party integration).
If you select n, go to Step 7.

y to integrate with a third-party NMS during installation
If you select y, continue with steps a through c

a. Select the adapter from the list of available adapters, or select other to select an adapter that is not listed (you will be prompted to enter the path name of the adapter), or select none to integrate after the installation is complete.
If you select none, go to Step 7.


Note If you are installing only the Integration Utility, enter the CiscoWorks2000 server name, protocol type (HTTP, HTTPS) and port number.


b. Enter the HTTP browser location, or press Enter to accept the default location, /opt/netscape/netscape.

A message appears, asking if you want to enable download options from the Cisco Systems web site (CCO).

c. Select one of the following:

n to disallow future upgrades from the Cisco Systems web site.

y to enable future upgrades from the Cisco Systems web site.
Enter your CCO user ID and password.


Note You must have CCO login privileges. If you do not have a user account and password on CCO, contact your channel partner or enter a request on the standard CCO web site (www.cisco.com).


Step 7 After installation is complete, unmount the CD-ROM. See the product installation guide for details.


Note A warning message is displayed if obsolete Solaris patches are present on your system. Before running CD One, 5th Edition, download and install the latest recommended patches from the Sun web site.


If errors occurred during installation, check the installation log file /var/tmp/ciscoinstall.log. Each installation appends to this file. For troubleshooting information or to verify the directories installed on your system, see the product installation guide.

Step 8 Prepare the client system for use. See the product installation guide.


Upgrading CD One—Remote Upgrade

If you do not want to overwrite your current application you can perform a remote upgrade. During a remote upgrade, you must:

Install CD One, 5th Edition. See "Installing CD One".

Install the patch—Before you upgrade from a previous edition of CD One, data from all jobs must be exported to the new system. To make this possible, you must first install a patch on the old system. The patch is shipped with CD One, 5th edition. See "Installing the Patch".

Export data from the system running the CD One, 4th edition to the new system. See "Exporting the Data".

Installing CD One

To install CD One, 5th edition:


Step 1 Install CD One, 5th edition on the new system. See "Running the Installation Program on Solaris" section.

Step 2 Remove the CD One CD-ROM from the new system.


Installing the Patch

To install the patch:


Step 1 Insert the CD One CD-ROM into the CD-ROM drive of the system running the previous version of CD One.

Step 2 At the command line, enter:

perl patch_1x_20.pl

Step 3 Make sure that daemon manager is up and running on the server. Also, make sure that the jrm process is up and running. For information on process management, see the product installation guide.

Step 4 At the command line, enter:

setenv LD_LIBRARY_PATH /opt/CSCOpx/objects/db/lib:/opt/CSCOpx/lib


Exporting the Data

To export the data:


Step 1 Insert the CD One, 5th edition CD-ROM in the CD-ROM drive of the system running the previous version of CD One.

Step 2 From the root directory, run the script export_cdone.pl.

Step 3 Copy the directories $NMSROOT/rigel/cmf and $NMSROOT/rigel/manifest from the system running the old version of CD One into the corresponding directories on the system running the new version of CD One.

Step 4 On the new system, go to the directory $NMSROOT/rigel/scripts, and run the script import_cdone.pl.

The upgrade is now complete, and all necessary job data from the previous version of CD One has been exported.



Note All passwords will be reset to the corresponding passwords of CD One, 4th edition.


Upgrading on Windows


Note If you plan to upgrade CD One or CiscoWorks2000 on a Windows machine on which IPM was previously installed, see the instructions in the "Upgrading CD One and CiscoWorks on an IPM Installation" section.


Upgrading CD One—Local Upgrade

You can upgrade from CD One, 4th Edition only. Upgrade from other lower versions of CD One is not supported. To perform a local upgrade, you must:

Back up your data — You can save your data to a backup file before you perform the local upgrade. If your installation fails, you can retrieve this saved data. See the "Backing Up Your Data" section.

Install a patch — You must install a patch on the old system before you can begin installing CD One, 5th Edition. This patch suspends all currently scheduled job data. Necessary data can then be exported during upgrade to the new version. See the "Installing the Patch" section.

Run the installation program. See the "Running the Installation Program on Windows" section.

Installing the Patch

To install the patch:


Step 1 Insert the CD One, 5th edition CD-ROM into a CD-ROM drive.

Step 2 At the command line, enter:

perl patch_1x_20.pl

The patch copies the file DisableJobs.class to the runtime installation directory.

Step 3 At the command line, enter:

cwjava -cw install_directory com.cisco.nm.cmf.jrm.DisableJobs

The class file suspends all the jobs and creates a list of job IDs for the suspended jobs and other job information in a file called joblist.jrm. The file joblist.jrm is saved in $NMSROOT/setup. Jobs are re-enabled as part of the upgrade process for individual applications.


After the patch is installed, you can install CD One, 5th Edition.

Running the Installation Program on Windows

To run the installation program:


Step 1 Install the required software as described in the "Hardware and Software Requirements" section.


Caution If you are running Windows 2000, make sure Service Pack 2 is installed. Without the appropriate service pack installed, CD One installer will display a warning to proceed at your own risk.

Step 2 Insert the CD One CD-ROM into a CD-ROM drive.

The Installer window appears.

Step 3 Click Install to continue.

The Welcome window appears.

Step 4 Click Next to continue.

The Setup Type dialog box appears.

Step 5 Select one of the following:

Typical to install all CD One components in the default location
(See the "Local Upgrade from CD One, 4th Edition—Typical" section.)

Custom to select optional components and to specify the location
(See the "Local Upgrade from CD One, 4th edition—Custom" section.)


Local Upgrade from CD One, 4th Edition—Typical

If you select the typical option:


Step 1 Click Next to continue.

The Start Copying Files dialog box appears, verifying current settings.

Step 2 Click Next to continue.

The installation program checks dependencies and system requirements. The Requirements Verification dialog box appears.

Step 3 Click OK.

The installation of CD One progresses.

A message appears:

User casuser already exists. Casuser is the user who administers and 
maintains CW2000 server without having root privileges. Installation 
will reset the password for security reasons.
Do you want to proceed with the installation?

Step 4 Click Yes if you receive the casuser message.

The installation program adds the new user casuser and the new group casusers to the system.

A messages displays:

By default install will select random password for casuser. Do you 
want to change password for casuser?

Step 5 Click Yes to change the password.

The CiscoWorks2000 change password dialog box appears.

Step 6 Enter the password and confirm the password.

The installation program adds the new user casuser and the new group casusers to the system.

The installation program displays:

For security reasons, Cisco recommends that you change the default 
password for Admin user. Do you want to change it now?

Step 7 Click Yes to change the password.

The CiscoWorks2000 change password dialog box appears.

Step 8 Enter the password and confirm the password.

The Installation displays prompts allowing you to change the default passwords for Admin user, Guest user, and the CMF and ANI database.

Step 9 Enter a new password, and confirm it.

The installation script checks dependencies, and the Integration Utility dialog box appears.

Step 10 Select one of the following:

Later to integrate with a third-party NMS after installation. Later is the recommended choice to complete the installation more quickly, and to avoid installation failure due to errors in the third-party integration.
If you select Later, click Next to continue.

Now to integrate with a third-party NMS during installation.
If you select Now, continue with steps a through c.

a. Click Next to continue. The Integration Utility dialog box appears, displaying a list of adapters.

b. Select the adapter from the list of available adapters, select other to select an adapter that is not listed (you will be prompted to enter the path name of the adapter), or select none to integrate after the installation is complete.
If you select none, go to Step 11.

The Integration Utility dialog box appears, asking if you want to enable download options from the Cisco Systems web site (CCO).


Note You must have CCO login privileges. If you do not have a user account and password on CCO, contact your channel partner or enter a request on the standard CCO web site (www.cisco.com).


c. Select one of the following:

No to disallow future upgrades from the Cisco Systems web site.

Yes to enable future upgrades from the Cisco Systems web site.

Enter your CCO user ID and password.


Note A dialog box might display the services that are running. To stop the services and continue the installation, click Yes.


When the installation is complete, the Restart dialog box appears, asking if you want to restart your system.

Step 11 Select Yes, then click Finish.

CD One software is installed in the default directory, C:\Program Files\CSCOpx, or the directory specified.

After the upgrade is complete, all jobs are in a suspended state. Jobs are re-enabled as part of the upgrade process for individual applications.

Step 12 Prepare the client system for use. See the product installation guide.



Caution You must restart your system when installation is complete to restart the processes.


Note If you cannot install CD One, see the product installation guide.


Local Upgrade from CD One, 4th edition—Custom

If you select the custom option:


Step 1 Click Next to continue.

The Select Destination dialog box appears.


Note If CD One has previously been installed on this system, the Select Destination dialog box will not appear and the product will automatically be installed in the same location at which CD One was previously installed.


Step 2 Click Next to accept the default location, or select a different location then click OK, then Next.


Note Do not select an encrypted directory. CiscoWorks2000 does not support directory encryption.


The Select Components dialog box appears.

Step 3 Select one of the following:


Note If CD One has previously been installed on this system, the list of components will be different.


1. NMS Integration Utility to install only the Integration Utility. For information about the Integration Utility and third-party NMS integration, see Using CiscoView.

2. Common Management Foundation (CMF) Base Desktop to install a subset of CMF—Select this option only if the application you'll be installing next requires the CMF Base Desktop and you do not want CiscoView or NMS Integration Utility installed.

3. CiscoView to install CiscoView only.

4. CiscoView, NMS Integration Utility and CMF to install all CD One components. This option is recommended for most systems.

Step 4 Click Next to continue.

The Start Copying Files dialog box appears, verifying current settings and selected components.


Note If you selected the Cisco View or the CMF Base Desktop option, go to Step 7.


Step 5 Click Next to continue.

The Requirements Verification dialog is displayed. The installation checks dependencies, and the Integration Utility dialog box appears.

Step 6 Select one of the following:

Later to integrate with a third-party NMS after installation. Later is the recommended choice to complete the installation more quickly, and to avoid installation failure due to errors in the third-party integration.
If you select Later, go to Step 7.

Now to integrate with a third-party NMS during installation.
If you select Now, continue with steps a through c.

a. Click Next to continue. The Integration Utility dialog box appears, displaying a list of adapters.

b. Select the adapter from the list of available adapters, select other to select an adapter that is not listed (you will be prompted to enter the path name of the adapter), or select none to integrate after the installation is complete.
If you select none, go to Step 7.

The Integration Utility dialog box appears, asking if you want to enable download options from the Cisco Systems web site (CCO).


Note If you are installing only the Integration Utility, enter the CiscoWorks2000 server name, protocol type (HTTP, HTTPS) and port number.


c. Select one of the following:

No to disallow future upgrades from the Cisco Systems web site.

Yes to enable future upgrades from the Cisco Systems web site.
Enter your CCO user ID and password.


Note You must have CCO login privileges. If you do not have a user account and password on CCO, contact your channel partner or enter a request on the standard CCO web site (www.cisco.com).



Note A dialog box might display the services that are running. To stop the services and continue the installation, click Yes.


When the installation is complete, the Restart dialog box appears, asking if you want to restart your system.

Step 7 Select Yes, then click Finish.

CD One software is installed in the default directory, C:\Program Files\CSCOpx, or the directory specified.

After the upgrade is complete, all jobs are in a suspended state. Jobs are re-enabled as part of the upgrade process for individual applications.

Step 8 Prepare the client system for use. See the product installation guide.



Caution You must restart your system when installation is complete to restart the processes.


Note For troubleshooting information, see the product installation guide.


Upgrading from CD One, 4th Edition—Remote Upgrade

If you do not want to overwrite your current application you can perform a remote upgrade. During a remote upgrade, you must:

Install CD One, 5th Edition. See "Installing CD One".

Install the patch—Before starting an upgrade to CD One, 5th Edition, relevant data from all jobs must be exported to the new system. To make this possible, you must first install a patch on the old system. The patch is shipped with CD One, 5th Edition. See the "Installing the Patch" section.

Export data from the system running the CD One, 4th Edition to the new system.See the "Exporting the Data" section.


Caution The database backup and restore options for one version of Essentials are not supported by other versions. When upgrading your server, follow the installation procedures in this section to convert and import your database.

Installing CD One

To install CD One, 5th Edition:


Step 1 Install CD One, 5th Edition on the new system. See the "Running the Installation Program on Windows" section.

Step 2 Remove the CD One CD-ROM from the new system.


Installing the Patch

To install the patch:


Step 1 Insert the CD One CD-ROM into the CD-ROM drive of the system running the previous version of CD One.

Step 2 At the command line, enter:

perl patch_1x_20.pl


After you have installed the patch, you can export the necessary job data from the old system to the new one.

Exporting the Data

To export the data:


Step 1 The CD One CD-ROM should be in the CD-ROM drive of the system running the old version of CD One. Go to the root directory on the CD One CD-ROM.

Step 2 Execute perl export_cdone.pl.

Step 3 Copy the directories $NMSROOT/rigel/cmf and $NMSROOT/rigel/manifest from the system running the old version of CD One into the corresponding directories on the system running the new version of CD One.

Step 4 On the new system, go to the directory $NMSROOT/rigel/scripts, and
execute perl import_cdone.pl.

The upgrade is now complete, and all necessary job data from the previous version of CD One has been exported.



Note All passwords will be reset to the corresponding passwords of CD One, 4th Edition.


Upgrading Essentials

This section describes how to upgrade to Essentials 3.4, if you have Essentials version 3.3 installed on the server.

Upgrade Paths

You can upgrade directly to Essentials 3.4 from Essentials 3.3 and Essentials 3.3 (IDS patch only).

Table 6 describes the different local upgrade paths and results. See the product installation guides for detailed installation instructions.

Table 6 Upgrade Paths for Essentials

Existing Software
Results

CD One exists in clean system

Resource Manager Essentials 3.4 is installed in the specified directory. If you installed CD One on a clean system, follow the installation procedure in the Installation and Setup Guide for Resource Manager Essentials to install Resource Manager Essentials 3.4.

Essentials 3.3

Reinstallation of Resource Manager Essentials disables the previously installed Essentials components. All data is preserved. When you install Essentials 3.4, the installation program converts the preserved database to Essentials 3.4 format.



Caution The database backup and restore options for one version of Essentials are not supported by other versions. When upgrading your server, follow the installation procedures in this section to convert and import your database.

Upgrading Essentials on Solaris

To upgrade your server to Essentials 3.4, you must:

1. Save your data to a backup file before you perform the upgrade; if your installation fails, you can retrieve this saved data. See "Backing Up Your Previous Database".

2. Run the Essentials installation program to install the new version and convert the database to Essentials 3.4 format. See "Running the Installation Program on Solaris" section.

3. Back up the converted database to create a backup compatible with Essentials 3.4. See the "Backing Up the Converted Database" section.

If you have installed Essentials 3.4, and you also have Essentials 3.3 on another server, you must upgrade the existing data to Essentials 3.4. See the "Upgrading Essentials Data from a Remote system" section.

Backing Up Your Previous Database

To back up your database:


Step 1 Access the CiscoWorks2000 desktop and log in. For information, see the Installation and Setup Guide for Resource Manager Essentials.

Step 2 Select Server Configuration > Administration > Database Management > Back Up Data Now.

The Back Up Data Now dialog box appears.

Step 3 Enter the pathname of the target directory. It is recommended that you use a different directory from the directory where Essentials is located, for example, /rme/backups on Solaris and c:\rme\backups in Windows.

Step 4 To begin the backup, click Finish. This process could take some time to complete.


Running the Installation Program on Solaris

The Essentials installation takes approximately 30 minutes.

You can press Ctrl-C at any time to end the installation. However, any changes to your system (for example, installation of new files or changes to system files) will not be undone.

The installation program installs Essentials in the same location as CD One (/opt/CSCOpx by default) and starts CiscoWorks2000.


Step 1 Run a backup database of your old data in case the installation fails.

Step 2 As root, mount the Essentials CD-ROM using either of the following methods:

Mount the CD-ROM on the CD One system.

Mount the CD-ROM on a remote Solaris system, then access the CD-ROM from the CD One server system.

For details on mounting and unmounting the CD-ROM, see the Installation and Setup Guide for Resource Manager Essentials.

Step 3 Start the installation program.

For a local installation, enter:

# cd /cdrom/cdrom0/
# ./setup.sh 

For a remote installation, enter:

# cd remotedir
# ./setup.sh

where remotedir is the remote location where the CD-ROM is mounted.

The installation program checks for required patches and other dependencies and displays:

1) Resource Manager Essentials
2) Resource Manager Essentials Incremental Device Support
3) All of the above
Select one of the items using its number or enter q to quit [q]


Note Option 3 is the most likely choice for an upgrade. If you try to install only one of the components when the others are not present on your system, the installation fails.


Step 4 Enter an option number and press Enter.

The installation program checks dependencies and system requirements.

If there is not enough disk space to install Essentials and Incremental Device Support, the installation program displays an error message and stops.

If the minimum recommended requirements are not met, the installation program displays an error message and continues installing.

The installation proceeds without displaying more questions and the system prompt appears.

Step 5 Unmount the CD-ROM. For instructions, see the Installation and Setup Guide for Resource Manager Essentials.

If errors occurred during installation, check the installation log file /var/tmp/ciscoinstall.log. For other troubleshooting information, see the Installation and Setup Guide for Resource Manager Essentials.

Backing Up the Converted Database

If the Essentials installation was successful, back up your newly converted database. This creates a backup compatible with Essentials 3.4 in case you have a problem and must restore your database. This also prevents overwriting of your database by restoring a database backup from the previous version of Essentials.

For instructions on backing up your newly converted database, see "Backing Up Your Previous Database" section.

Upgrading Essentials Data from a Remote system

If you have installed Essentials 3.4, and you also have Essentials 3.3 on another server, you will have to upgrade the existing data to Essentials 3.4.


Note You must upgrade CD One data before you can upgrade Essentials data.


To upgrade data from a remote system, you must:

Export Essentials data from the server that has Essentials 3.3

Import this data into the server that has Essentials 3.4

Exporting Data

To export Essentials data:


Step 1 Access the server that has Essentials 3.3.

Step 2 Shut down the daemon manager. Enter:

# /etc/init.d/dmgtd stop

Step 3 Mount the Essentials 3.4 CD-ROM.
Enter:

# cd cdrom

Step 4 Enter:

# cd disk1
# ./export_rme.pl

The message "Do you want to export RME jobs (Y/N)?" appears.

Step 5 Enter Y to export jobs or enter N if you do not wish to export jobs.

The NetConfig, Config Editor, and Netshow jobs, if any, will be exported.

The system copies the required files to install_dir/rigel/manifest/rme and install_dir/rigel/rme directories, where install_dir is the directory in which CiscoWorks2000 is installed (/opt/CSCOpx by default).

Step 6 Change to the directory, install_dir/rigel.

Step 7 Copy the contents of this directory to a backup location.

Step 8 Start the daemon manager. Enter:

# /etc/init.d/dmgtd start


Importing Data

To import Essentials data:


Step 1 Access the server that has Essentials 3.4.

Step 2 Copy the exported Essentials data from your backup location into install_dir/rigel, where install_dir is the directory in which CiscoWorks2000 is installed (/opt/CSCOpx by default).

Step 3 Shut down the daemon manager. Enter:

# /etc/init.d/dmgtd stop

Step 4 Change to the directory, install_dir/rigel/scripts.

Step 5 Enter:

# ./import_rme.pl

The message, "Existing RME 3.4 data will be lost and replaced with the imported RME 3.3 data. Are you sure you want to import (Y/N)?" appears.

Step 6 Enter Y.

Step 7 Start the daemon manager. Enter:

# /etc/init.d/dmgtd start


Upgrading Essentials on Windows

To upgrade your server to Essentials 3.4, you must:

1. Save your previous data to a backup file before you perform the upgrade; if your installation fails, then you can retrieve the saved data.See "Backing Up Your Previous Database" section.

2. Run the Essentials installation program to install the new version and convert your previous database to Essentials 3.4 format. See "Running the Installation Program on Windows" section.

3. Back up the converted database to create a backup compatible with Essentials 3.4. See the "Backing Up the Converted Database" section.

If you have installed Essentials 3.4, and you also have Essentials 3.3 on another server, you will have to upgrade the existing data to Essentials 3.4. See the "Upgrading Essentials Data from a Remote system" section.


Caution The database backup and restore options for one version of Essentials are not supported by other versions. When upgrading your server, follow the installation procedures in this section to convert and import your database.

Running the Installation Program on Windows

The Essentials installation takes approximately 30 minutes. You can cancel the installation at any time by clicking Cancel at the bottom of any installation window.


Note Install CD One, 5th Edition before you begin installation of Essentials 3.4


The installation program installs Essentials in the same location as CD One (c:\Program Files\ CSCOpx by default) and starts CiscoWorks2000.


Step 1 Log in as the local administrator on the system on which you installed CD One, 5th Edition.

Step 2 Insert the Essentials 3.4 CD-ROM into a CD-ROM drive.

The Installer window appears.

Step 3 Click Install.

The Welcome window appears.

Step 4 Click Next to continue.

The Setup Type dialog box appears.

Step 5 Select one of the following:

Typical to reinstall both Essentials and Incremental Device Support (IDS).

Custom to select a component to install. The Select Components dialog appears.


Note You must install both Essentials and IDS. If you try to install Essentials only, the installation will fail.


Step 6 Click Next to continue.

The Start Copying Files dialog box appears.

Step 7 Click Next.

The installation program checks dependencies and system requirements.

The Requirements Verification dialog box displays the results of the requirements check and informs you whether the installation can continue. Do one of the following:

If minimum requirements are met, click OK. The Setup window appears, displaying installation progress while files are copied and applications are configured. Then the Setup Complete dialog box appears.

If requirements are not met, click OK. The installation stops. Reconfigure the server and run the installation program again or install on a different server.

Step 8 Click Finish. You have completed the Essentials installation.

Step 9 Remove the CD-ROM from the drive.

Step 10 If you did not restart the computer after installing CiscoWorks2000 CD One, restart it now.


If errors occurred during installation, check the installation log in the root directory on the drive where the operating system is installed. Each installation creates a new log file. For example, the CiscoWorks2000 CD One installation creates c:\cw2000_in001.log. The Essentials installation creates c:\cw2000_in002.log. The Technical Assistance Center (TAC) might ask you to send them the installation log.

For other troubleshooting information, see the Installation and Setup Guide for Resource Manager Essentials.

Upgrading Essentials Data from a Remote system

If you have installed Essentials 3.4, and you also have Essentials 3.3 on another server, you will have to upgrade the existing data to Essentials 3.4.


Note You must export CD One data before you can upgrade Essentials data.


Upgrading data from a remote system consists of:

Exporting RME data from the server that has Essentials 3.3

Importing this data into the server that has Essentials 3.4

Exporting Data

To export Essentials 3.3 data:


Step 1 Access the server that has Essentials 3.3

Step 2 Shut down the daemon manager. Enter:

net stop crmdmgtd

Step 3 Insert the Essentials 3.4 CD-ROM.

Step 4 Change to the directory, disk1.

Step 5 Enter:

install_dir\bin\perl export_rme.pl

where install_dir is the directory in which CiscoWorks2000 is installed (c:\Program Files\CSCOpx by default).

The message "Do you want to export RME jobs (Y/N)?" appears.

Step 6 Enter Y to export jobs or enter N if you do not wish to export jobs.

If you entered N the NetConfig, Config Editor, and Netshow jobs, if any, will be exported. The software management jobs will not be exported.

The system copies the required files to install_dir\rigel\manifest\rme and install_dir\rigel\rme directories, where install_dir is the directory in which CiscoWorks2000 is installed.

Step 7 Change to the directory, install_dir \rigel.

Step 8 Copy the contents of this directory to a backup location.

Step 9 Start the daemon manager. Enter:

net start crmdmgtd


Importing Data

To import Essentials 3.3 data:


Step 1 Access the server that has Essentials 3.4.

Step 2 Copy the exported Essentials data from your backup location into
install_dir \rigel where install_dir is the directory in which CiscoWorks2000 is installed (c:\Program Files\CSCOpx by default).

Step 3 Shut down the daemon manager. Enter:

net stop crmdmgtd

Step 4 Change to the directory, install_dir\rigel.

Step 5 Enter:

install_dir\bin\perl install_dir\rigel\scripts\import_rme.pl

where install_dir is the directory in which CiscoWorks2000 is installed.

The message, "Existing RME 3.4 data will be lost and replaced with the imported RME 3.3 data. Are you sure you want to import (Y/N)?" appears.


Step 6 Enter Y.

Step 7 Start the daemon manager. Enter:

net start crmdmgtd


Upgrading ACL Manager

Upgrading ACL Manager on Windows

Upgrading ACL Manager Data from a Remote Windows Machine

If you have installed ACL Manager 1.4, and you also have ACL Manager 1.3 on another server, you have to upgrade the existing data to ACL Manager 1.4.


Note You must upgrade Essentials and CMF data before you can upgrade
ACL Manager data.


Upgrading data from a remote machine consists of:

1. Exporting ACL Manager data from the server that has ACL Manager 1.3

2. Importing this data into the server that has ACL Manager 1.4

To export ACL Manager data:


Step 1 Access the server that has ACL Manager 1.3.

Step 2 Set the NMSROOT variable to CiscoWorks2000 install directory.

Step 3 To shut down ACL Manager, enter:

%NMSROOT%\bin\pdterm AclmServer

where NMSROOT is the directory in which CiscoWorks2000 is installed (c:\program files\CSCOpx by default).

Step 4 Insert the ACL Manager 1.4 CD-ROM.

Step 5 At the command prompt, corresponding to the drive where the CD-ROM contents can be accessed, enter:

%NMSROOT%\bin\perl.exe export_aclm.pl

Step 6 Enter the backup directory name at the prompt. The aclmdata.tar file will be stored at the specified location.

You can also enter the backup directory name as a command line option:

%NMSROOT%\bin\perl.exe export_aclm.pl backup directory.

Step 7 Copy the aclmdata.tar file to any location on the machine where
ACL Manager 1.4 is installed.

Step 8 Start ACL Manager. Enter:

%NMSROOT%\bin\pdexec AclmServer


Note You must import Essentials data before you can import ACL Manager data.


To import ACL Manager data:


Step 1 Access the server that has ACL Manager 1.4.

Step 2 Shut down ACL Manager. Enter:

%NMSROOT%\bin\pdterm AclmServer

where NMSROOT is the directory in which CiscoWorks2000 is installed (c:\program files\CSCOpx by default).

Step 3 Enter:

cd %NMSROOT%\rigel\scripts
%NMSROOT%\bin\perl.exe import_aclm.pl

Step 4 Enter the location and name of the file (aclmdata.tar) at the prompt. After you enter the backup directory and filename, this message appears on the screen:

Restoring removes all existing data including jobs.
Remove existing data and continue [y/n]?

Step 5 Enter y, and then press Enter.

Step 6 Start ACL Manager. Enter:

%NMSROOT%\bin\pdexec AclmServer


Upgrading ACL Manager on Solaris

Upgrading ACL Manager Data from a Remote Solaris Machine

If you have installed ACL Manager 1.4 on a Solaris machine, and you have
ACL Manager 1.3 on another Solaris machine, you will have to upgrade the existing data to ACL Manager 1.4.


Note You must upgrade Essentials data before you can upgrade
ACL Manager data.


Upgrading data from a remote machine consists of:

Exporting ACL Manager data from the server that has ACL Manager 1.3.

Importing this data into the server that has ACL Manager 1.4

To export ACL Manager data:


Step 1 Access the server that has ACL Manager 1.3.

Step 2 To shut down ACL Manager, enter:

$NMSROOT/bin/pdterm AclmServer

where NMSROOT is the directory in which CiscoWorks2000 is installed (/opt/CSCOpx by default).

Step 3 Mount the ACL Manager 1.4 CD-ROM. Enter:

cd cd cdrom/cdrom0

Step 4 Enter:

./export_aclm.pl

Step 5 Enter the backup directory name at the prompt. The aclmdata.tar file will be stored at the specified location.

You can also enter the backup directory name as a command line option:

./export_aclm.pl backup directory

The aclmdata.tar file will be stored at the specified location.

Step 6 Do an ftp of aclmdata.tar in the binary mode to the machine that has
ACL Manager 1.4.

Step 7 Start ACL Manager. Enter:

$NMSROOT/bin/pdexec AclmServer



Note You must import Essentials data before you can import ACL Manager data.


To import ACL Manager data:


Step 1 Access the server that has ACL Manager 1.4.

Step 2 Shut down ACL Manager. Enter:

$NMSROOT/bin/pdterm AclmServer

where NMSROOT is the directory in which CiscoWorks2000 is installed (/opt/CSCOpx by default).

Step 3 Enter these commands:

cd NMSROOT/rigel/scripts
./import_aclm.pl

Step 4 Enter the location and name of the file (aclmdata.tar) at the prompt. After you enter the backup directory and filename, this message appears on the screen:

Restoring removes all existing data including jobs.
Remove existing data and continue [y/n]?

Step 5 Enter y, and then press Enter.

Step 6 Start ACL Manager. Enter:

$NMSROOT/bin/pdexec AclmServer

Upgrading IPM

This section describes how to upgrade to Internetwork Performance Monitor 2.4 from IPM releases 2.2 and 2.3.


Note You can take a backup of IPMDB.db, IPMDB.log, and ipm.env before you do an upgrade. Make sure that you back up these files after stopping IPM servers.



Caution If there is a failure in the upgrade process or if you terminate the upgrade process, you cannot restore the old database.

If you do not follow these rules when you upgrade, IPM cannot function properly.

Upgrading from Previous Releases of IPM

While installing IPM 2.4, the install process checks for the current version of IPM on your machine. If IPM 2.3 is installed, it is automatically upgraded to IPM version 2.4. The install mode appears as Upgrade rather than Fresh.

The IPM database and seed files from IPM 2.3 are preserved. This data is backed up automatically as part of the installation process and then converted to the format used by IPM 2.4.

Remote upgrade to IPM 2.4 is supported from IPM 2.2 and 2.3.

To upgrade to IPM 2.4 on Windows, see the installation instructions in the "Installing IPM on Windows" section.

To upgrade to IPM 2.4 on Solaris, see the installation instructions in the "Installing IPM on Solaris" section.

If you already have IPM installed on Windows, and plan to upgrade CD One or CiscoWorks2000 on the same machine, see the instructions in the "Upgrading CD One and CiscoWorks on an IPM Installation" section.

Migration Path for IPM 2.4

The migration path for IPM 2.3.x running on Solaris 2.6 and Windows NT 4.0 is as follows:


Step 1 If you are running:

Solaris 2.6, upgrade the OS to Solaris 2.7 or Solaris 2.8.

Windows NT 4.0, upgrade the OS to Windows 2000 Professional or Windows 2000 Server.

Step 2 You can upgrade to IPM 2.4 using inline upgrade or remote upgrade.


The migration path for IPM 2.2 on Solaris and Windows NT 4.0 is as follows:


Step 1 Install IPM on a different machine which is running one of these:

Solaris 2.7 or Solaris 2.8.

Windows 2000 Professional or Windows 2000 Server.

Step 2 Install IPM 2.4

Step 3 Remote upgrade the IPM 2.2 data.


Before you run IPM 2.4, you must install all the required:

OS patches

Service packs

Third party device drivers

for the current operating system.


Caution Make sure that you also upgrade the third party device drivers for the current operating system.

Migrating Remote Data on Windows

When you want to migrate IPM 2.2 or IPM 2.3 data from one machine to IPM 2.4 on another machine on the same network, you need to do a remote upgrade.


Caution When you do an upgrade, existing IPM 2.4 data is overwritten.

To do a remote upgrade:


Step 1 Run RBackup.exe, from the IPM CD-ROM root directory, on the machine on which IPM 2.3 or IPM 2.2 is installed.

This stops all IPM servers that are running and takes a backup of the database, the seed files, and the environment variables.

Step 2 Go to the directory where you have installed IPM 2.3 or IPM 2.2 and change to the backup directory.

Step 3 Copy the entire contents in this directory to the backup directory under the directory where you have installed IPM 2.4.


Note Before copying the files, make sure that IPM 2.4 has been installed on that machine.


Step 4 Go to the bin directory of the IPM server.

Step 5 Run ipm upgrade at the command prompt.

The upgrade from IPM 2.2 or IPM 2.3 to IPM 2.4 is complete.



Caution After remote upgrade, do not run these two versions of IPM simultaneously. There might be synchronization problems with respect to Collectors.

Migrating Remote Data on Solaris

When you want to migrate IPM 2.2 and IPM 2.3 data from one machine to IPM 2.4 on another machine on the same network, you need to do a remote upgrade.


Caution When you do an upgrade, existing IPM 2.4 data is overwritten.

To do a remote upgrade:


Step 1 Mount the CD-ROM on the machine on which IPM 2.2 or IPM 2.3 is installed.


Note For more information, see Chapter 4, "Mounting and Unmounting the CD-ROM Drive on Solaris," in the Installation Guide for Internetwork Performance Monitor.


Step 2 Run RBackup.sh, from the CD-ROM root directory. This stops all running IPM servers and takes a backup of the database, the seed files, the environment variables, and the version information. This data is compressed and ipmBackup.tar file is created in the IPM 2.2 or IPM 2.3 root directory.

Step 3 Copy ipmBackup.tar to the IPM 2.4 root directory.

Before copying the file, make sure that IPM 2.4 has been installed on that machine.

Step 4 Go to the bin directory of the IPM server. Run ipm upgrade at the command prompt. The remote upgrade from IPM 2.2 or IPM 2.3 to IPM 2.4 is complete.


Note This command can only be executed by a user with root privileges.




Caution After a remote upgrade, do not run these two versions of IPM simultaneously. There might be synchronization problems with respect to Collectors.

Installing IPM on Windows

Before beginning this procedure, be sure to see the "Upgrading CD One and CiscoWorks on an IPM Installation" section.

To install IPM on Windows:


Step 1 Log in as the administrator.

Step 2 Insert the IPM CD-ROM in the CD-ROM drive on the workstation.

The IPM program files are automatically extracted from the CD-ROM. When all the files are extracted, the IPM Setup window appears.


Note If the setup window does not appear automatically when you insert the CD-ROM, go to the root directory and run the ipmfull.exe command. If you are having trouble reading the CD-ROM, make sure your CD-ROM drive is compliant with the ISO 9660 standard.


Step 3 Click Next.

The License Agreement window appears.

Step 4 Click Yes.

The Setup Type window appears.

The Setup Type window allows you to specify whether you are installing the IPM server, the IPM client, or both. If you are running Windows 98 or Windows NT, you can install only the IPM client, so the Setup Type window is unnecessary. Instead, the Select Program Folder window appears, and you should
go to Step 7.

Step 5 Specify whether you are installing the IPM server, the IPM client, or both:

To install both, select IPM Client & Server, then click Next.

To install only the IPM client, select IPM Client, then click Next.

To install only the IPM server, select IPM Server, then click Next.

The Choose Destination Location window appears.

Step 6 Accept the default location, or browse to find a location, then click Next.

The Select Program Folder window appears.

Step 7 Accept the default folder, enter a folder name, or browse to find a folder, then click Next. The Select IPM Server Configuration window appears.

Step 8 Complete the fields in the Select IPM Server Configuration window as follows:

In
Enter
Note

DbPort

The port number for the IPM server database. The default port number is 44341/tcp.

This field appears only when you are installing the IPM server or server and client.

ServerHost

The name of the host on which the IPM server software is installed.

This field appears when you are installing the IPM client only.

ServerPort

The IPM server port number.

The default is 44342/udp.

WebPort

The IPM web port number.

The default is 1744/tcp.


Step 9 Click Next.


Note If you have selected to install IPM Server or IPM Server and client, IPM prompts you to enter database and administrative passwords.


The IPM Database Password window appears.

Step 10 Select one of the following:

Yes to enter the new database password. The password is case sensitive, should begin with an alphabetic character, and can contain a maximum of 15 alphanumeric characters.

No to retain the database password. By default, the database password is retained. You can change the Database password after the complete installation, using the command ipm dbpassword.

The IPM Administrative Password window appears.

Step 11 Select one of the following:

Yes to enable the administrative password. Enter the new administrative password. The password is case sensitive, should begin with an alphabetic character, and can contain a maximum of 15 alphanumeric characters.

No to disable the administrative password. You can change the Administrative password after the complete installation, using the command ipm password.


Caution It is strongly recommended that you enable the administrative password, in order to secure the IPM configuration properly. You can enable the administrative password after the installation is complete, using the command ipm password.

Step 12 Click Next. IPM prompts you to confirm your choices, and the Start Copying Files window appears.

Step 13 Click Next. The Setup Status window appears and the files are copied.

Step 14 After all of the files have been copied, the setup program prompts you to enable regular unattended backups of the IPM database. If you want to enable this feature, click Yes.

The InstallShield Wizard Complete window appears. Installation is complete.

Step 15 When installation is complete, the setup program prompts you to read the Readme file. The Readme file contains the latest information about IPM. To view the Readme file, select the Readme checkbox and click Finish.

Step 16 Remove the CD-ROM from the drive.


Note After you have finished using the CD-ROM to install the IPM client in Windows 98, remove the CD-ROM from the workstation's drive. If you leave the CD-ROM in the drive and reboot, or if you remove and then reinsert the CD-ROM, InstallShield setup runs and prompts you to uninstall the IPM client.



Installing IPM on Solaris

To install IPM on Solaris:


Step 1 Before you begin the installation:

Make sure your Solaris system meets the requirements listed in the "Hardware and Software Requirements" section.

Determine the location of the Netscape Communicator executable file. During installation, you are prompted to provide the full path to this file. The default path is /opt/netscape/netscape.

Step 2 Log in as the root user.

Step 3 Insert the IPM CD-ROM into the CD-ROM drive and, if necessary, mount the CD-ROM drive.

Step 4 Start the installation script by entering the following at command prompt:

# ./setup.sh

Step 5 When the installation script menu appears, select one of the following:

To read the latest information about IPM in the Readme file, enter 1 and press Enter. The Readme file contains the latest information about IPM.

To install both the IPM server and client, enter 2 and press Enter.

To install the IPM client only, enter 3 and press Enter.

Step 6 When you select option 2 or 3, the installation script attempts to locate the Netscape Communicator browser. Continue as follows:

If the installation script locates the browser successfully, go to Step 7.

If it cannot locate the browser, the script will prompt you for the path. To accept the default path, press Enter. To specify a path other than the default, type the full path (including filename) where the executable file is located, then press Enter.

Step 7 The installation script determines whether your system meets the requirements for running IPM.

If your system meets the requirements for IPM, the following prompt appears:

Do you want to change the IPM Database Password [y] ->

Note If you have selected to install IPM Server or IPM Server and client, the script prompts you to enter database and administrative passwords.


Step 8 Do one of the following:

Enter y or press Enter to set the new database password. Enter the new database password. The password is case sensitive, should begin with an alphabetic character, and can contain a maximum of 15 alphanumeric characters.

Enter n to retain the database password. By default, the database password is retained.

You can change the database password after the installation is complete, using the command ipm dbpassword.

When you are finished, the installation script displays the following message:

It is strongly recommended that you ENABLE the Administrative 
Password, for securing the IPM configuration.
Do you want to enable the IPM Administrative Password [y] ->

Step 9 Do one of the following:

Enter y or press Enter to enable the administrative password. Enter the new administrative password. The password is case sensitive, should begin with an alphabetic character, and can contain a maximum of 15 alphanumeric characters.

Enter n to disable the administrative password.


Caution It is strongly recommended that you enable the administrative password, in order to secure the IPM configuration properly. You can enable the administrative password after the installation is complete, using the command ipm password.

When you are finished, the installation script displays the following prompt:

Do you want the Express Install (y/n)? [Y]

Step 10 Do one of the following:

Enter y or press Enter to select Express Install, which installs IPM using all default settings.

Enter n to select standard installation, which prompts you for additional information such as port numbers, product path, and filename.

If your system does not meet all the requirements for IPM, the installation script proceeds with the standard installation and prompts you for information such as port numbers and Netscape executable path.

Step 11 Verify that the installation completed successfully by viewing the messages displayed at the end of the installation and by viewing the installation log. The installation log path is specified at the end of the installation script.

After IPM is successfully installed, the following IPM start-up menu appears.

**********************************************************************
*                           Cisco  Systems                           *
*      +          +                                 +          +     *
*      |          |          Internetwork           |          |     *
*     +|+        +|+      Performance Monitor      +|+        +|+    *
*   +|||||+    +|||||+                           +|||||+    +|||||+  *
* ++|||||||++++|||||||++    Startup Options    ++|||||||++++|||||||++*
* Empowering     The        ===============     Internet   Generation*
**********************************************************************
1) Start IPM Server and Client
2) Start IPM Server Only
3) Exit Setup

Please choose an option -> 

Step 12 Start IPM by entering 1 or 2 and pressing Enter.


Upgrading CD One and CiscoWorks on an IPM Installation

If you install IPM on a Windows machine that already has the RWAN bundle installed, re-installation or installation of CD One or any CiscoWorks2000 applications may fail because of a shared library being locked. This problem also occurs when CiscoWorks2000 and IPM installations exist on the same machine and you install or upgrade other CiscoWorks2000 components.

To work around this problem


Step 1 Run ipm stop.

Step 2 Run ipm cw2ksetup uninstall.

Step 3 Re-install or install CD One or the CiscoWorks2000 application.

Step 4 Run ipm cw2ksetup install.

Step 5 Run ipm start.


Note The first two steps remove IPM's dependency on the shared library. The last two steps integrate IPM with CiscoWorks2000.



Upgrading nGenius Real-Time Monitor

You can upgrade to nGenius Real-Time Monitor 1.4 from RTM version 1.2 or 1.3 only. Upgrades from other nGenius products are not supported.

Prerequisites

If you are upgrading, you must comply with the following:

Stop the nGenius Real-Time Monitor Server.

If you have placed your database on other than the default nGenius Real-Time Monitor database directory, it will not be automatically moved to the new default database directory.

To install your database to the new default directory, manually move the stealth.db file to the new database location. For example, move stealth.db from old database location to the nGenius\rtm\database directory.


Note (UNIX only) Ensure that you are logged in as ngenius user before upgrading your database or starting the nGenius Server.


For more details on the prerequisites, see the NetScout nGenius Real-Time Monitor 1.4 Installation Guide.

Upgrading to nGenius Real-Time Monitor 1.4

The nGenius Real-Time Monitor software supports upgrades from nGenius Real-Time Monitor 1.2 or 1.3 only. Upgrades from other nGenius products are not supported.

When you upgrade to nGenius Real-Time Monitor 1.4 from versions 1.2 or 1.3, all existing device configurations and logged data, such as login and password information, are preserved.

The following summarizes the files and settings that the upgrade process automatically moves or copies to the nGenius Real-Time Monitor home directory:

Moves the stealth.db file from nGenius Real-Time Monitor 1.3

Copies the db.properties file

Copies the .license.properties file

Copies the loaduser.sql file

Copies the NS Web Port setting

Upgrading from nGenius Real-Time Monitor 1.3

To upgrade to nGenius Real-Time Monitor 1.4 from version 1.3:


Step 1 Stop the nGenius Real-Time Monitor server. Do not uninstall the nGenius Real-Time Monitor software.

Step 2 Back up your existing database (stealth.db) on a tape or a separate disk partition. See the online Help for specific instructions on how to back up your database.

Step 3 Install the nGenius Real-Time Monitor software on your Windows or UNIX server. See installation instructions provided in the NetScout nGenius Real-Time Monitor 1.4 Installation Guide.

During the upgrade, a message appears indicating that an upgrade will occur and the nGenius Real-Time Monitor installation directory is renamed with a _BAK extension. For example: Windows platform — c:\ProgramFiles\nGenius_BAK and UNIX platform — /opt/nGenius_BAK

A message appears indicating that the previous database password will be assigned automatically. You do not need to enter a new database password. The old database (stealth.db) is moved to the new nGenius Real-Time Monitor installation directory.

Step 4 When the nGenius Real-Time Monitor installation is complete, but before you start the server, upgrade your database.


Caution Ensure you have sufficient disk space before upgrading your database.

(UNIX only) Log in as ngenius user before upgrading your database.

There will be a slight increase (approximately 15 percent) in the size of the database.

Do not interrupt the upgrade process. Doing so might result in database corruption. Expect the upgrade process to take approximately one hour per gigabyte of data.

In the NetScout/rtm/bin directory, execute the following files from the command line:

Windows systems: dbupgrade13_14.bat

UNIX systems: dbupgrade13_14.sh

Step 5 After you complete the upgrade, you can manually delete the old nGenius Real-Time Monitor installation directory to free up disk space.


Caution Do not use the nGenius Real-Time Monitor uninstall program to delete the old nGenius Real-Time Monitor installation directory. Doing so might remove necessary files.


Upgrading from nGenius Real-Time Monitor 1.2

To upgrade to nGenius Real-Time Monitor 1.4 from version 1.2:


Step 1 Stop the nGenius Real-Time Monitor server. Do not uninstall the nGenius Real-Time Monitor software.

Step 2 Back up your existing database (stealth.db) on a tape or a separate disk partition. See the online Help for specific instructions on how to back up your database.

Step 3 Install the nGenius Real-Time Monitor software on your Windows or UNIX server. See installation instructions provided in the NetScout nGenius Real-Time Monitor 1.4 Installation Guide.

During the upgrade, a message appears, indicating that an upgrade will occur and the nGenius Real-Time Monitor installation directory is renamed with a _BAK extension. For example: c:\ProgramFiles\nGenius_BAK (Windows) and /opt/nGenius_BAK (UNIX platforms).

A message appears indicating that the previous database password will be assigned automatically. You do not need to enter a new database password. The old database (stealth.db) is moved to the new nGenius Real-Time Monitor installation directory.

Step 4 When the installation is complete, but before you start the server, upgrade your database.


Caution Ensure you have sufficient disk space before upgrading your database.

(UNIX only) Log in as ngenius user before upgrading your database.

There will be a slight increase (approximately 15 percent) in the size of the database.

Do not interrupt the upgrade process. Doing so might result in database corruption. Expect the upgrade process to take approximately one hour per gigabyte of data.

In the NetScout/rtm/bin directory, execute the following files from the command line:

Windows platforms: dbupgrade12_14.bat

UNIX platforms: dbupgrade12_14.sh

Step 5 After you complete the upgrade, you can manually delete the old nGenius Real-Time Monitor installation directory to free-up disk space.


Caution Do not use the nGenius Real-Time Monitor uninstall program to delete the old nGenius Real-Time Monitor installation directory. Doing so might remove necessary files.


Obtaining Documentation

The following sections explain how to obtain documentation from Cisco Systems.

World Wide Web

You can access the most current Cisco documentation on the World Wide Web at the following URL: http://www.cisco.com

Translated documentation is available at the following URL:

http://www.cisco.com/public/countries_languages.shtml

Ordering Documentation

In addition to individual titles, you can order a complete set of Cisco hardcopy user guides for the products in this version of the Routed WAN Management Solution, using the part number CWDOC-RWAN-LMS, from the following sources:

Registered Cisco Direct Customers can order Cisco Product documentation from the Networking Products MarketPlace: http://www.cisco.com/cgi-bin/order/order_root.pl

Registered Cisco.com users can order the Documentation CD-ROM through the online Subscription Store: http://www.cisco.com/go/subscription

Nonregistered Cisco.com users can order documentation through a local account representative by calling Cisco corporate headquarters (California, USA) at 408 526-7208 or, in North America, by calling 800 553-NETS(6387).

Documentation Feedback

If you are reading Cisco product documentation on Cisco.com, you can submit technical comments electronically. Click Feedback at the top of the Cisco Documentation home page. After you complete the form, print it out and fax it to Cisco at 408 527-0730.

You can e-mail your comments to bug-doc@cisco.com.

To submit your comments by mail, use the response card behind the front cover of your document, or write to the following address:

Cisco Systems
Attn: Document Resource Connection
170 West Tasman Drive
San Jose, CA 95134-9883

We appreciate your comments.

Routed WAN Management Solution 1.2 Bundle Update

Copyright © 2002, Cisco Systems, Inc.

All rights reserved