Installation and Setup Guide for Resource Manager Essentials 3.5 on Windows (With LMS 2.2/RWAN 1.3)
Installing Essentials
Downloads: This chapterpdf (PDF - 387.0KB) The complete bookPDF (PDF - 1.4MB) | Feedback

Installing Essentials

Table Of Contents

Installing Essentials

Product Overview

Installation Overview

Installation Notes

Preparing to Install Essentials

Server Recommendations

Client Requirements

Additional Client Requirements

Supported NMS Environments for Device Import

Supported Devices

Installing Essentials

Performing a New Installation

Running the Installation Program for a New Installation

Upgrading from a Previous Version

Running the Installation Program for an Upgrade (Direct Upgrade)

Upgrading Essentials Data from a Remote Machine (Remote Upgrade)

Reinstalling or Upgrading from the Evaluation Version

Running the Installation Program to Reinstall

Post Installation Checklist


Installing Essentials


This chapter describes installing Resource Manager Essentials 3.5 on a Windows system. It consists of:

Product Overview

Installation Overview

Preparing to Install Essentials

Installing Essentials

Post Installation Checklist

Essentials application alone Common ServicesEssentialsBefore removing Essentials, you must remove any applications that depend on Essentials. These are the applications for which installing Essentials is a prerequisite.

Product Overview

Resource Manager Essentials (Essentials), one of the major components of CiscoWorks, enables the deployment, configuration, and monitoring of devices across your network. Essentials is a suite of web-based network management tools integrated into a network desktop that includes web-based tools, and web-browser capability. This product is based on a client/server network architecture that connects multiple web-based clients to a network server.

The Essentials CD-ROM contains the Resource Manager Essentials 3.5 installable package.

Installation Overview

Table 1-1 is an overview of the Essentials installation. It contains references to more detailed information about each task.


Installation Notes

Before you begin your installation, note the following:

You must install CiscoWorks Common Services 2.2 (Common Services). Essentials 3.5 can be installed only after you have installed Common Services. For more information, refer to Installation and Setup Guide for Common Services on Windows. The install script will find the Common Services directory and install Essentials at the same location (SystemDrive:\Program Files\CSCOpx by default). This location is referred to as %NMSROOT% in this document.

You can upgrade to Essentials 3.5 only from Essentials 3.3 and Essentials 3.4 with Incremental Device Update (IDU) packages. No other upgrades are supported. For more information, see You can upgrade to Essentials 3.5 from:.

You must restart the system after installing CiscoWorks Common Services and before installing Essentials 3.5. The installation of Essentials might fail if you do not restart your system.

Run the installation from a local CD or a local hard drive to avoid errors due to network inconsistencies.

Close all applications before running installation. Do not run any other programs while installation is in progress.

If you are running virus scanner or mail client while installing Essentials, the installation might take longer to complete.

The Resource Manager Essentials 3.5 installer will automatically update Essentials 3.3 and Essentials 3.4 program files and migrate user-entered data related to Essentials. The Essentials 3.5 installer will also automatically re-apply some device updates previously released on Cisco's download site as Incremental Device Updates (IDU). IDU 1.0 and IDU 2.0 have been incorporated into Essentials 3.5. If you have installed IDU 3.0 or higher for Essentials 3.4, you will need to re-apply that IDU after the Essentials 3.5 installation is complete.

To ensure that you retain the latest device support and bug fixes after installing Essentials you must install the latest Incremental Device Update (IDU) for Resource Manager Essentials 3.5.

For more details, see "Frequently Asked Questions" section.

Preparing to Install Essentials

This section describes prerequisites and other factors you should consider before installing Essentials. This consists of:

You can upgrade to Essentials 3.5 from:

Server Requirements and Recommendations

Client Requirements

Supported NMS Environments for Device Import

Supported Devices


Caution Do not change the system time after installing Essentials. Such changes may affect the working of some time-dependent features. For more information, see "Frequently Asked Questions" section.

You can upgrade to Essentials 3.5 from:

Essentials Releases
Incremental Device Updates (IDUs) / Patches

Essentials 3.3

You can upgrade to Essentials 3.5 with or without using the following combinations of software releases on Essentials 3.3:

All the IDU releases on Essentials 3.3

All the patches released till date on Essentials 3.3

Data Extracting Engine (DEE) V1

Essentials 3.4

You can upgrade to Essentials 3.5 with or without using the following combinations of software releases on Essentials 3.4:

All the IDU releases on Essentials 3.4

All the patches released till date on Essentials 3.4

Data Extracting Engine (DEE) V2


This section describes the server requirements and recommendations for CiscoWorks Common Services 2.2 (Common Services) and Essentials.

a CiscoWorks Server running theTable 1-2

Table 1-2 Server System Minimum Requirements 

Requirement Type
Minimum Requirements

 

IBM PC-compatible computer with 500 MHz Intel Pentium processor

CD-ROM drive

System software

Windows 2000 (Professional or Server) with Service Pack 3 or higher

Windows Advanced Server without enabling terminal services 1

ODBC Driver Manager 3.5.10

Essentials supports only US-English and Japanese versions of Windows Operating System. It does not support any other language version. Set the default locale to US-English for US-English version and Japanese for Japanese version.

 

512 MB

 

Enough space for storing device software image files2

512NTFS file system required for secure operation

16 MB in the Windows temporary directory (%TEMP%)

 

Common Services 2.2 must be installed before installing . See Installation and Setup Guide for Common Services on Windows.

Additional optional software

One of these browsers:

Microsoft Internet Explorer 6.0 (version 6.0.2600.0000), or 6.0 with Service Pack 1 (version 6.0.2800.1106)

Java Virtual Machine (JVM) versions 5.0.0.3802 3 , 4 or later, and

Java Plug-in version 1.3.1

Netscape Navigator 4.78, 4.79

1 Installation will continue with a warning message on a Windows 2000 Advanced Server

2 For information about space needed for these files, see Setting Up Software Management.

3 To verify the JVM version, select View > Java Console.

4 We had tested our products on the following versions of JVM: 5.0.0.3802, 5.0.0.3805 and 5.0.0.3809.


Server Recommendations

To select or configure a server system that best meets your needs, consider:

The number of managed devices to be polled by the Availability application.

The number of managed devices expected in Inventory and Configuration Management.

The number of Syslog messages expected daily.

Availability is an application in Essentials, and it is a primary consideration for server recommendations. After that, you can consider Syslog messages and managed device expectations and determine your needs accordingly. These factors affect server performance and user report response time.

Table 1-3 shows the recommendations for a server running Common Services and . These recommendations produce optimal response time when running user reports.

Table 1-3 Server System Recommendations

Minimum System Configuration
Availability 1
Syslog 2
Configuration Management 3
Inventory 4 and Software Image Management

Pentium III, 450 MHz
Memory: 512 MB
Virtual memory: 1 GB
Available disk space: 40 GB 5

0-100 managed devices

0-50,000 messages per day

0-500 managed devices

0-500 managed devices

Pentium III, 450 MHz
Memory: 1 GB
Virtual memory: 2 GB
Available disk space: 80 GB 5

100-500 managed devices

50,000-150,000 messages per day

500-2,500 managed devices

500-2,500 managed devices

Dual Pentium III, 550 MHz
Memory: 2 GB
Virtual memory: 4 GB 5
Available disk space: 80 GB

500-1,000 managed devices

150,000 messages per day

2,500-5,000 managed devices

2,500-5,000 managed devices

1 Availability function within Essentials helps you track the reachable devices on your network. The number of managed devices in Availability is the main deciding factor.

2 Syslog Analysis lets you centrally log and track messages generated by devices. The figures in this column are number of messages per day.

3 Configuration Management function controls and tracks changes to device configurations in order to minimize errors and assist in troubleshooting problems.

4 Inventory application stores all information on all devices that you wish to manage on a network.

5 Disk space requirements are up to ten times higher if Common Services and Essentials are installed on a FAT file system.


Client Requirements

The minimum client system requirements for Common Services and are shown in Table 1-4.

Before you access from a client system, you must configure the system. For more  information about client system requirements and configuring clients, see Installation and Setup Guide for Common Services on Windows.

Table 1-4 Client System Requirements Summary 

Requirement Type
Minimum Requirement

System Software and Hardware

Client system:

IBM PC-compatible computer with 300 MHz Pentium processor running Windows 2000 (Professional or Server), or Windows XP with Service Pack 1.

Essentials supports only US-English and Japanese versions of Windows OS. Set the default locale to US-English for US-English OS, and Japanese for Japanese OS.

Sun SPARC Ultra 10 running Solaris 2.7, Solaris 2.8

Color monitor with video card set to 24 bits color depth.

Memory (RAM)

128 MB

Browser

One of these browsers:

On Windows 2000 and Windows XP clients:

Microsoft Internet Explorer 6.0 (version 6.0.2600.0000), or 6.0 with Service Pack 1 (version 6.0.2800.1106)

Java Virtual Machine (JVM) versions 5.0.0.3802 1 , 2 or later, and

Java Plug-in version 1.3.1

Netscape Navigator 4.78, 4.79

On Solaris clients:

Netscape Navigator 4.76 3

1 To verify the JVM version, select View > Java Console.

2 We had tested our products on the following versions of JVM: 5.0.0.3802, 5.0.0.3805 and 5.0.0.3809.

3 Use Netscape Navigator downloaded only from the Sun site.


Additional Client Requirements

The Table 1-4 lists minimum client requirements for Essentials. Some memory and processor intensive operations might require higher client requirements. For example, scheduling or viewing NetConfig jobs containing more than 500 devices, we recommend the following additional client requirements:

Requirement Type
Minimum Requirement

System Hardware

IBM PC-compatible computer with at least 450 MHz Pentium processor running Windows 2000 (Professional or Server), or Windows XP.

Memory (RAM)

384 MB

Virtual Memory

1024 MB


To display the NetConfig job details for the jobs containing more than 500 devices, Java Plugin requires more memory. You are required to update a parameter in Java Plugin control panel to allocate more heap-size to JVM.

To do so:


Step 1 Select Start > Settings > Control Panel > Java Plugin 1.3.1.

Step 2 Select Basic.

Step 3 In the Java Runtime Parameters field, enter:

-Xmx256m

Step 4 Click Apply.

Step 5 Restart browser.


Supported NMS Environments for Device Import

The Inventory application can import device information from both local and remote network management systems (NMS).

Table 1-5 and Table 1-6 show the software Essentials supports for importing devices from local and remote systems. You can import devices remotely only from a UNIX system. Essentials does not support remote device imports from Windows system. For more information, see the "Adding or Importing Inventory Data" section or see the online help.

Table 1-5 Supported NMS Software for Local Device Import 

Software
Version

Campus Manager

3.1 (ANI), 3.2 and 3.3

HP OpenView Network Node Manager

6.0, 6.1, 6.2 and 6.3

NetView

6.0, 6.0.1 and 7.1


Table 1-6 Supported NMS Software for Remote Device Import1

Software
Version

Campus Manager

3.1, 3.2 and 3.3

Cisco WAN Manager

9.1, 9.2, 10.4, 10.5

CiscoWorks for Switched Internetworks (CWSI)

2.4

HP OpenView Network Node Manager

5.01, 6.1 and 6.2

NetView

5.1, 6.0, 6.0.1 and 7.1

5.1, 6.0 on AIX

1 You can remotely import devices from UNIX systems only.


Supported Devices

Essentials 3.5 supports the devices supported in previous versions of Essentials as well as new devices. Device adapter packages for all supported devices are installed when you install Essentials. Information about these devices is at:

http://www.cisco.com/univercd/cc/td/doc/product/rtrmgmt/cw2000/cw2000e/index.htm

You can login to Cisco.com as a registered user for:

Downloading Incremental Device Update (IDU). IDUs contain latest device support and bug fixes for Essentials.

You can download IDU for Essentials from:

http://www.cisco.com/cgi-bin/tablebuild.pl/cw2000-rme

More information about new device support

To see a list of the device packages installed on your CiscoWorks server, select Server Configuration > About the Server > Applications and Versions. Then click on the Inventory Manager link to see specific device information.

Installing Essentials

This section describes the following tasks:

Performing a New Installation

Running the Installation Program for a New Installation

Upgrading Essentials Data from a Remote Machine (Remote Upgrade)

Upgrading from a Previous Version

Reinstalling or Upgrading from the Evaluation Version

While performing Essentials installation you might be prompted to enter a new password. For details, refer to "Frequently Asked Questions" section. For more information on creating a new password see the "Password Information" Appendix in Installation and Setup Guide for Common Services on Windows.


Note You must install Common Services 2.2 before you can install . For details, refer to Installation and Setup Guide for Common Services on Windows.


Performing a New Installation

This section describes how to perform a new installation.

If you are upgrading on a system that had a previous version of installed, see the"Upgrading from a Previous Version" section.

If you are reinstalling Essentials 3.5 or upgrading from an evaluation version of Essentials 3.5, see the "Reinstalling or Upgrading from the Evaluation Version" section.


Note If you want to import data from a previous version of Essentials that resides on a different server, follow the procedure in this section to perform a new installation. After installing Essentials, follow the procedure in the "Upgrading Essentials Data from a Remote Machine (Remote Upgrade)" section to import the data.


Running the Installation Program for a New Installation

The installation takes approximately 30 minutes.

You can cancel the installation at any time by clicking Cancel at the bottom of most installation screens.

The installation program installs in the same location as Common Services 2.2 (%NMSROOT% by default) and starts CiscoWorks.


Step 1 Log in as the local administrator on the system on which you installed Common Services.

Step 2 Insert the Essentials 3.5 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 Software License Agreement window appears.

Step 5 Click Yes to continue.

The Setup Type dialog box appears displaying two installation modes, Typical installation and Custom installation.


NoteIf you choose the Typical installation mode, a password for the Essentials database will be randomly generated for you.

If you choose the Custom installation mode, you will be prompted to enter a password for the Essentials database, else a password will be randomly generated for you.


Step 6 Do one of the following:

If you prefer the Typical installation mode, go to New Installation—Typical.

If you prefer the Custom installation mode, go to New Installation—Custom.


New Installation—Typical

If you prefer the Typical option:


Step 1 Select Typical installation.

Step 2 Click Next.

The System Requirements window appears.

Step 3 Click Next.

The Summary window appears.

Step 4 To view all settings including those selected automatically, click Show Details.

A Security Alert dialog appears.

Step 5 Click Yes to view details.


Note The summary details view displays the randomly generated password in clear text.


The Summary window displays installation details.

Step 6 Click Next.

The installation program checks dependencies and system requirements.

The Setup screen appears, displaying installation progress while files are copied and applications are configured.

The following message appears:

To ensure that you retain the latest device support and bug fixes, 
please install the latest Incremental Device Update (IDU) for Resource 
Manager Essentials 3.5. You can download the latest IDU from 
http://www.cisco.com/cgi-bin/tablebuild.pl/cw2000-rme

Please refer to the Installation and Setup Guide for details.


Note For more information about IDUs, see "Frequently Asked Questions" section.


Step 7 Click OK.

The Setup Complete dialog box appears.

Step 8 Click Finish. You have completed the installation.

Step 9 Restart the system.


New Installation—Custom

If you prefer the Custom option:


Step 1 Select Custom installation.

Step 2 Click Next to continue.

The Change Essentials Database Password window appears.

Step 3 Do one of the following:

To define a new password:

Enter a password in the Password field.

Re-enter the password in the Confirm Password field.

To let Essentials generate a random password for you, leave the Password field and the Confirm Password field empty.

You can view your password in clear text in Step 6.

Step 4 Click Next.

The System Requirements window appears.

Step 5 Click Next.

The Summary window appears.

Step 6 To view all settings including those selected automatically, click Show Details. A Security Alert dialog appears.

Step 7 Click Yes to view details.


Note The summary details view displays the password in clear text.


The Summary window displays installation details.

Step 8 Click Next.

The installation program checks dependencies and system requirements.

The Setup screen appears, displaying installation progress while files are copied and applications are configured.

The following message appears:

To ensure that you retain the latest device support and bug fixes, 
please install the latest Incremental Device Update (IDU) for Resource 
Manager Essentials 3.5. You can download the latest IDU from 
http://www.cisco.com/cgi-bin/tablebuild.pl/cw2000-rme

Please refer to the Installation and Setup Guide for details.


Note For more information about IDUs, see "Frequently Asked Questions" section.


Step 9 Click OK.

The Setup Complete dialog box appears.

Step 10 Click Finish. You have completed the installation.

Step 11 Restart the system.


If you had any errors 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 Common Services installation creates SystemDrive:\CiscoWorks_setupxxx.log, where xxx is the log file for the last CiscoWorks application installed. If you request for assistance, the Technical Assistance Center (TAC) might ask you to send them the installation log.

For other troubleshooting information, see "Troubleshooting the Installation"

Upgrading from a Previous Version

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


Note If you had installed a version of IDU later than 2.0 on a previous version of Essentials, and then want to upgrade to Essentials 3.5, you will lose support for new devices.

To retain support for those devices, we recommend that you download and install the latest IDU for Essentials 3.5 after upgrading to Essentials 3.5. For more details, see "Frequently Asked Questions" section.


When you install Common Services on a system that has Essentials 3.3.x or Essentials 3.4.x, the installation program disables the previous version but preserves its database. Only when you install Essentials 3.5, the installation program converts the preserved database to Essentials 3.5 format.

If you installed Common Services on a clean system, follow the installation procedure in the "Performing a New Installation" section.

You can upgrade to Essentials 3.5 from Essentials 3.3.x or Essentials 3.4.x using either of the following methods:

Direct Upgrade—Involves Running the Installation Program for an Upgrade (Direct Upgrade).

Remote Upgrade—Involves a set of two tasks:

a. Exporting and then importing CiscoWorks CD One data. For more information, see Installation and Setup Guide for Common Services on Windows.

b. Exporting and then importing Essentials 3.3.x or Essentials 3.4.x data. For more details, see Upgrading Essentials Data from a Remote Machine (Remote Upgrade).

Running the Installation Program for an Upgrade (Direct Upgrade)

The Essentials installation takes approximately 30 minutes.

You can cancel the installation at any time by clicking Cancel at the bottom of most installation screens.

The installation program installs Essentials in the same location as Common Services (SystemDrive:\Program Files\CSCOpx by default) and starts CiscoWorks.


Step 1 Log in as the local administrator on the system on which you installed Essentials 3.3 or Essentials 3.4.

Step 2 Insert the Essentials 3.5 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 Software License Agreement window appears.

Step 5 Click Yes to continue.

The Setup Type dialog box appears displaying two installation modes, Typical Installation and Custom Installation.


NoteIf you choose the Typical installation mode, the password assigned to the previous installation of Essentials database will be retained.

If you choose the Custom installation mode, you will be prompted to enter a password for the Essentials database, else the password assigned to the previous installation of Essentials database will be retained.


Step 6 Do one of the following:

If you prefer the Typical installation mode, go to Upgrade Installation—Typical.

If you prefer the Custom installation mode, go to Upgrade Installation—Custom.


Upgrade Installation—Typical

If you prefer the Typical option:


Step 1 Select Typical installation.

Step 2 Click Next.

The System Requirements window appears.

Step 3 Click Next.

The Summary window appears.

Step 4 To view all settings including those selected automatically, click Show Details.

A Security Alert dialog appears.

Step 5 Click Yes to view details.

The Summary window displays installation details.

Step 6 Click Next.

The installation program checks dependencies and system requirements.

The Setup screen appears, displaying installation progress while files are copied and applications are configured.

The following message appears:

To ensure that you retain the latest device support and bug fixes, 
please install the latest Incremental Device Update (IDU) for Resource 
Manager Essentials 3.5. You can download the latest IDU from 
http://www.cisco.com/cgi-bin/tablebuild.pl/cw2000-rme
Please refer to the Installation and Setup Guide for details.


Note For more information about IDUs, see "Frequently Asked Questions" section.


Step 7 Click OK.

The Setup Complete dialog box appears.

Step 8 Click Finish. You have completed the installation.

Step 9 Restart the system.


Upgrade Installation—Custom

If you prefer the Custom option:


Step 1 Select Custom installation.

Step 2 Click Next to continue.

The Change Essentials Database Password window appears.

Step 3 Do one of the following:

To define a new your password:

Enter a password in the Password field.

Re-enter the password in the Confirm Password field.

You can view your password in clear text in Step 6.

To retain the password assigned to the previous installation of Essentials, leave the Password field and the Confirm Password field empty.

Step 4 Click Next.

The System Requirements window appears.

Step 5 Click Next.

The Summary window appears.

Step 6 To view all settings including those selected automatically, click Show Details.

A Security Alert dialog box appears.

Step 7 Click Yes to view details.


Note If you chose to define a new password in Step 3 above, the summary details view displays the password in clear text.


The Summary window displays installation details.

Step 8 Click Next.

The installation program checks dependencies and system requirements.

The Setup screen appears, displaying installation progress while files are copied and applications are configured.

The following message appears:

To ensure that you retain the latest device support and bug fixes, 
please install the latest Incremental Device Update (IDU) for Resource 
Manager Essentials 3.5. You can download the latest IDU from 
http://www.cisco.com/cgi-bin/tablebuild.pl/cw2000-rme

Please refer to the Installation and Setup Guide for details.


Note For more information about IDUs, see "Frequently Asked Questions" section.


Step 9 Click OK.

Then the Setup Complete dialog box appears.

Step 10 Click Finish.

You have completed the installation.

Step 11 Restart the system.


If you had any errors 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 Common Services installation creates SystemDrive:\cw2000_inxxx.log, where xxx is the log file for the last CiscoWorks application installed. If you request for assistance, the Technical Assistance Center (TAC) might ask you to send them the installation log.

For other troubleshooting information, see "Troubleshooting the Installation"

Upgrading Essentials Data from a Remote Machine (Remote Upgrade)

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


Note You must upgrade Common Services 2.2 data (export data and then import data) before you can upgrade data. For more information about upgrading Common Services data, see Installation and Setup Guide for Common Services on Windows.


Upgrading data from a remote machine involves:

Exporting Essentials Data—Exporting Essentials data from the server that has Essentials 3.3.x or Essentials 3.4.x to a user specified location.

Importing Essentials Data—Importing this data into the current Essentials 3.5 database.

Exporting Essentials Data

To export data:


Step 1 Access the server that has 3.3.x or Essentials 3.4.x.

Step 2 Shut down the daemon manager. To do this, enter:

net stop crmdmgtd

Step 3 Insert the Essentials 3.5 CD-ROM.

Step 4 Enter # cd cdrom0


Step 5 Enter:%NMSROOT%\bin\perl export_rme.pl


where %NMSROOT% is the directory in which CiscoWorks is installed (SystemDrive:\Program Files\CSCOpx by default).

The following message appears:

Enter the location where you want to export RME data [%NMSROOT%\rigel]

Step 6 Press Enter to accept the default location, or enter a new location.

The system exports the data, and creates the directories manifest\rme and rme at the location specified for backing up the data. For example, if you have chosen D:\export as the back up location, the system creates the directories D:\export\rme and D:\export\manifest\rme to store the exported data

The following message appears:

Do you want to export RME jobs(Y/N)?

Step 7 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 software management jobs will not be exported.

Step 8 Start the daemon manager. To do this, enter:

net start crmdmgtd


Importing Essentials Data


Note You must import Common Services data before you can import  data. For more information about upgrading Common Services data, see Installation and Setup Guide for Common Services on Windows.


To import 3.3.x or Essentials 3.4.x data:


Step 1 Access the server that has Essentials 3.5.

Step 2 Copy the exported data from your backup location into
%NMSROOT%\rigel where %NMSROOT% is the directory in which CiscoWorks is installed (SystemDrive:\Program Files\CSCOpx by default).

Step 3 Shut down the daemon manager. To do this, enter:

net stop crmdmgtd

Step 4 Change to the directory, %NMSROOT%\rigel.

Step 5 Enter:

%NMSROOT%\bin\perl %NMSROOT%\rigel\scripts\import_rme.pl

where %NMSROOT% is the directory in which CiscoWorks is installed.

The following message appears:

Existing RME 3.5 data will be lost and replaced with the imported 
RME 3.x data. Are you sure you want to import (Y/N)?

where 3.x is the version of Essentials data which is being imported.

Step 6 Enter Y to import the data, or N to quit.

Step 7 Start the daemon manager. To do this, enter:

net start crmdmgtd


Reinstalling or Upgrading from the Evaluation Version

This section explains how to reinstall Essentials 3.5 or upgrade from an evaluation version of Essentials 3.5.

The installation program is able to detect whether you have already installed Essentials 3.5. Your existing database is not affected by the reinstallation; however, you should back up the database before installing to prevent any possible loss of data. Your CiscoWorks Server configuration is also preserved.

Running the Installation Program to Reinstall

The Essentials installation takes approximately 30 minutes.

You can cancel the installation at any time by clicking Cancel at the bottom of most installation screens.

The installation program installs Essentials in the same location as Common Services (SystemDrive:\Program Files\CSCOpx by default) and starts CiscoWorks.


Step 1 Log out of CiscoWorks and close the browser.

Step 2 Insert the Essentials 3.5 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 Software License Agreement window appears.

Step 5 Click Yes to continue.

The Setup Type dialog box appears displaying two installation modes, Typical Installation and Custom Installation.


NoteIf you choose Typical installation mode, the password assigned to the previous installation of Essentials database will be retained.

If you choose Custom installation mode, you will be prompted to enter a password for the Essentials database, else the password assigned to the previous installation of Essentials database will be retained.


Step 6 Do one of the following:

If you prefer the Typical installation mode, go to Reinstalling Essentials—Typical.

If you prefer the Custom installation mode, go to Reinstalling Essentials—Custom.


Reinstalling Essentials—Typical

If you prefer the Typical option:


Step 1 Select Typical installation.

Step 2 Click Next.

The System Requirements window appears.

Step 3 Click Next.

The Summary window appears.

Step 4 To view all settings including those selected automatically, click Show Details.

A Security Alert dialog appears.

Step 5 Click Yes to view details.

The Summary window displays installation details.

Step 6 Click Next.

The installation program checks dependencies and system requirements.

The Setup screen appears, displaying installation progress while files are copied and applications are configured.

The following message appears:

To ensure that you retain the latest device support and bug fixes, 
please install the latest Incremental Device Update (IDU) for Resource 
Manager Essentials 3.5. You can download the latest IDU from 
http://www.cisco.com/cgi-bin/tablebuild.pl/cw2000-rme

Please refer to the Installation and Setup Guide for details.


Note For more information about IDUs, see "Frequently Asked Questions" section.


Step 7 Click OK.

The Setup Complete dialog box appears.

Step 8 Click Finish.

You have completed the installation.

Step 9 Restart the system.


Reinstalling Essentials—Custom

If you prefer the Custom option:


Step 1 Select Custom installation.

Step 2 Click Next to continue.

The Change Essentials Database Password window appears.

Step 3 Do one of the following:

To define a new your password:

Enter a password in the Password field.

Re-enter the password in the Confirm Password field.

You can view your password in clear text in Step 6.

To retain the password assigned to the previous installation of Essentials, leave the Password field and the Confirm Password field empty.

Step 4 Click Next.

The System Requirements window appears.

Step 5 Click Next.

The Summary window appears.

Step 6 To view all settings including those selected automatically, click Show Details.

A Security Alert dialog appears.

Step 7 Click Yes to view details.


Note If you chose to define a new password in Step 3 above, the summary details view displays the password in clear text.


The Summary window displays installation details.

Step 8 Click Next.

The installation program checks dependencies and system requirements.

The Setup screen appears, displaying installation progress while files are copied and applications are configured.

The following message appears:

To ensure that you retain the latest device support and bug fixes, 
please install the latest Incremental Device Update (IDU) for Resource 
Manager Essentials 3.5. You can download the latest IDU from 
http://www.cisco.com/cgi-bin/tablebuild.pl/cw2000-rme

Please refer to the Installation and Setup Guide for details.


Note For more information about IDUs, see "Frequently Asked Questions" section.


Step 9 Click OK.

Then the Setup Complete dialog box appears.

Step 10 Click Finish. You have completed the installation.

Step 11 Restart the system.


If you had any errors 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 Common Services installation creates SystemDrive:\cw2000_inxxx.log, where xxx is the log file for the last CiscoWorks application installed. If you request for assistance, the Technical Assistance Center (TAC) might ask you to send them the installation log.

For other troubleshooting information, see"Troubleshooting the Installation".

Post Installation Checklist

Table 1-7 lists the common post-installation that are required to be configured after installing Essentials. For details, see "Preparing to Use Essentials Applications".

Table 1-7 Post Installation Checklist

Task
How to get there...

Verifying System Settings

Resource Manager Essentials > Administration > System Configuration

Job Approval

Creating approver list

Resource Manager Essentials > Administration > Job Approval > Create Approver List

Enabling job approval

Resource Manager Essentials > Administration > Job Approval > Edit Preferences

Inventory Management

Checking Add / Import Summary

Resource Manager Essentials > Administration > Inventory > Import Status

Checking device attributes

Resource Manager Essentials > Administration > Inventory > Check Device Attributes

Changing device attributes

Resource Manager Essentials > Administration > Inventory > Change Device Attributes

Deleting unwanted devices

Resource Manager Essentials > Administration > Inventory > Delete Devices

Scheduling collection

Resource Manager Essentials > Administration > Inventory > Schedule Collection

Verifying Inventory poller configuration

Resource Manager Essentials > Administration > Inventory > Inventory Poller

Manually updating inventory

Resource Manager Essentials > Administration > Inventory > Update Inventory

Configuration Management

Performing general setup tasks

Resource Manager Essentials > Administration > Configuration Management > General Setup

Config Editor Administration

Resource Manager Essentials > Configuration Management > Config Editor

Or

Edit > Set Job Policies

NetConfig Administration

Resource Manager Essentials > Configuration Management > NetConfig

Or

Admin > Set Template Policies

Network Show Commands

Creating Command Sets

Resource Manager Essentials > Administration > Configuration Management > Network Show > Define Command Set

Assigning Users to Command Sets

Resource Manager Essentials > Administration > Configuration Management > Network Show > Assign Users

Defining Network show Batch Commands

Resource Manager Essentials > Configuration Management > Network Show Commands > Batch Reports > Define Reports

Scheduling a Network show Command Batch Report

Resource Manager Essentials > Configuration Management > Network Show Commands > Batch Reports > Schedule Reports

Setting Default Job Properties for Batch Reports

Resource Manager Essentials > Configuration Manager > Network Show Commands > Batch Reports > Set Job Policies

Software Image Management

Establishing Software Management Preferences

Resource Manager Essentials > Administration > Software Management > Edit Preferences

Importing Baseline of Software Images

Resource Manager Essentials > Software Management > Library > Add Images

Scheduling Synchronization Job

Resource Manager Essentials > Administration > Software Management > Schedule Synchronization Job

Schedule Browse Bugs Job

Resource Manager Essentials > Administration > Software Management > Schedule "Browse Bugs" Job

Change Audit

Configuring Inventory Change Filter

Resource Manager Essentials > Administration > Inventory > Inventory Change Filter

Defining Exception Periods

Resource Manager Essentials > Administration > Change Audit > Define Exceptions Summary

Forwarding Traps

Resource Manager Essentials > Administration > Change Audit > Administer Trap Generator

Syslog Analysis

Verifying Storage Options

Resource Manager Essentials > Administration > Syslog Analysis > Change Storage Options

Defining Message Filters

Resource Manager Essentials > Administration > Syslog Analysis > Define Message Filter

Defining Automated Actions

Resource Manager Essentials > Administration > Syslog Analysis > Define Automated Action

Creating Custom Syslog Reports

Resource Manager Essentials > Administration > Syslog Analysis > Define Custom Report

Availability Manager

Establishing Polling Options

Resource Manager Essentials > Administration > Availability > Change Polling Options


Essentials application alone Common ServicesEssentialsBefore removing Essentials, you must remove any applications that depend on Essentials. These are the applications for which installing Essentials is a prerequisite.


Note EssentialsEssentialsEssentialsYou cannot uninstall Common Services without uninstalling Essentials.


A dialog box listing the components selected for uninstallation appears.

Step 12 Click Next.

Messages showing the progress of the uninstallation appear.

The following message appears:

Uninstallation is complete. Click Ok to finish.

Step 13 Click OK.

Step 14 Restart the system.


Note The Software Management application stores images that are not removed by the uninstallation program. To permanently remove Essentials, you must remove these files manually from
%NMSROOT%\files\sw_images,
%NMSROOT%\files\inventory,
%NMSROOT%\files\netconfig



"Reinstalling or Upgrading from the Evaluation Version" section