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

Installing Essentials

Table Of Contents

Installing Essentials

Product Overview

Installation Overview

Installation Notes

Preparing to Install Essentials

Essentials Upgrade Paths

Server Requirements and Recommendations

Minimum Server Requirements

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

Uninstalling Essentials


Installing Essentials


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

Product Overview

Installation Overview

Preparing to Install Essentials

Installing Essentials

Post Installation Checklist

Uninstalling Essentials

Product Overview

Resource Manager Essentials (Essentials), one of the major components of CiscoWorks, enables the deployment, monitoring, and configuration 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.

Table 1-1 Installing Essentials Overview 

Task
Steps
References

1. Prepare to install Essentials.

Verify that requirements are met.

"Essentials Upgrade Paths" section

"Server Requirements and Recommendations" section

"Client Requirements" section

"Supported NMS Environments for Device Import" section

"Supported Devices" section

2. Install Essentials.

a. Mount the CD-ROM.

b. Run the installation program.

"Performing a New Installation" section

or

"Upgrading from a Previous Version" section

or

"Reinstalling or Upgrading from the Evaluation Version" section

3. Troubleshoot the installation.

Analyze installation error messages.

"Troubleshooting the Installation"

4. Perform post-installation tasks.

Configure the system and set up Essentials applications.

"Preparing to Use Essentials Applications"


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, see the Installation and Setup Guide for Common Services on Solaris. The install script will find the Common Services directory and install Essentials at the same location (opt\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 or Essentials 3.4 with Incremental Device Update (IDU) packages. No other upgrades are supported. For more information, see Essentials Upgrade Paths.

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

For information on different installation options, see What are the various installation switches supported?.

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:

Essentials Upgrade Paths

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.

Essentials Upgrade Paths

You can upgrade to Essentials 3.5 from:

Essentials Releases
Incremental Device Updates (IDU)s / 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


Server Requirements and Recommendations

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

Minimum Server Requirements

The minimum system requirements for a CiscoWorks Server running the Common Services 2.2 and Resource Manager Essentials 3.5 software are shown in Table 1-2.

Table 1-2 Server System Minimum Requirements  

Requirement Type
Minimum Requirements

System hardware

Sun Sparc Ultra 101

CD-ROM drive

System software

Solaris 2.7 and Solaris 2.8

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

Memory (RAM)

512 MB

Available drive space

4 GB on the partition on which you install the product
(the default is /opt) 2

Enough space for storing device software image files3

Swap space must be double the amount of memory (RAM). For example, if your system has 512 MB of RAM, you need 1024 MB of swap space

Additional required software

Common Services must be installed before you install Essentials. Refer to Installation and Setup Guide for Common Services on Solaris

Additional optional software

Netscape Navigator 4.76 (if you are using the desktop on the server system) 4

1 Common Services supports Ultra SPARC III machines such as Sun-Fire-280R, Netra-T4, Sun Blade 1000.

2 Essentials 3.5 is is installed in the same directory as Common Services .

3 For information about downloaded files, see the "Setting Up Software Management" section.

4 Use Netscape Navigator downloaded only from the Sun site.


To verify the amount of available disk space in each of the specified partitions and directories, enter:

# df -k directory

where directory is the partition or directory for which you want to check the available disk space.

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 the Inventory and Configuration Management applications.

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 Essentials. 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

Ultra 10
Memory: 512 MB
Swap space: 1 GB
Available disk space: 40 GB

0-100 managed devices

0-50,000 messages per day

0-500 managed devices

0-1000 managed devices

Ultra 10
Memory: 2 GB
Swap space: 2 GB
Available disk space: 80 GB

100-500 managed devices

50,000-150,000 messages per day

500-2,500 managed devices

1000-2500 managed devices

Ultra 60 (dual processor)
Memory: 2 GB
Swap space: 4 GB
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.


Client Requirements

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

Before you can access Essentials from a client system, the system must be properly configured. For more information about configuring clients, see Installation and Setup Guide for Common Services on Solaris.

Table 1-4 Client System Requirements Summary 

Requirement Type
Minimum Requirement

System Software and Hardware

Client system:

Sun SPARC Ultra 10 running Solaris 2.7, Solaris 2.8

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.

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

Memory (RAM)

256 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, for scheduling or viewing NetConfig jobs that contain more than 500 devices, we recommend the following additional client requirements:

Requirement Type
Minimum Requirement

System Hardware

IBM PC-compatible computer with 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 that contain more than 500 devices, Java Plugin requires more memory. You must update a parameter in Java Plugin control panel to allocate more heap-size to JVM.

To update this parameter:


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 Essentials Inventory application can import device information from both local and remote network management systems (NMS).

Table 1-5 and Table 1-6 show the NMSs supported for importing device information into the Essentials inventory. You can import devices remotely from a UNIX system only.

Table 1-5 Supported NMS Software for Local Device Import 

Software
Version

Campus Manager

3.1 (ANI), 3.2 and 3.3

Cisco WAN Manager

10.4 and 10.5

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 (ANI), and 3.3

Cisco WAN Manager

9.1, 9.2, 10.4 and 10.5

CiscoWorks for Switched Internetworks (CWSI)

2.4

HP OpenView Network Node Manager

5.01, 6.0, 6.1, 6.2

NetView

5.1, 6.0, 6.0.1 and 7.1

5.1, 6.0 on AIX

1 You can remotely import device information from UNIX systems only.


For more information, see the "Adding or Importing Inventory Data" section or see the online help.

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, see "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 Solaris.


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


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 Essentials 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 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.

Hence, we do not recommend ending the installation, using Ctrl-C. You will be required to manually cleanup the installation directories. For more information, see "Frequently Asked Questions" section.

The installation program installs Essentials 3.5 in the same location as Common Services 2.2 (/opt/CSCOpx by default) and starts CiscoWorks.


Step 1 As root, mount the Essentials 3.5 CD-ROM. You can either:

Mount the CD-ROM on the CiscoWorks Server system. (Direct installation)

or

Mount the CD-ROM on a remote Solaris system, then access the CD-ROM from the CiscoWorks Server system. (Remote installation)

See "Mounting and Unmounting the CD-ROM," for detailed mounting instructions.

Step 2 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 License Agreement page is displayed.

Step 3 Press Return to scroll forward one page, or q to quit the License Agreement page. The following message appears:

You must accept this License agreement for the installation to 
proceed.
If you enter N/n, the installation will exit.
Do you accept all the terms of the preceding License agreement? (y/n) 
[y]

Step 4 Press y to accept the agreement, or n to quit installation.

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

1) Typical ("Typical installation is recommended for all computers.")
2) Custom ("Custom installation can be selected if you want to 
customize the setup options.")

Select one of the installation modes using its number or enter q to 
quit [1]


NoteIf you choose the Typical installation mode, the Essentials database password will be randomly generated for you. You can view the password at the end of installation.

If you choose the Custom installation mode, you will be prompted to enter the Essentials database password.


Step 5 Do one of the following:

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

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


New Installation—Typical

If you prefer the Typical option:


Step 1 Enter 1 and press Return.

The installation program checks dependencies and system requirements: For details, see "Server Requirements and Recommendations" section.

If your system does not meet the requirements a warning appears:

System memory is less than the minimum requirement, which may 
affect performance.

If the drive does not have enough space, an error message appears:

There is not enough space in drive drive name.

Select another drive, or free some space on drive drive name.

The installation proceeds without displaying more questions. The following message appears:

Do you want to see the passwords that were entered/randomly 
generated ? If yes, please remember that passwords are security 
sensitive data and hence make sure they are kept secure. [y/n]

Step 2 If you enter y, the password will appear in clear text on the console. If you enter n, the password will not appear.

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.


The installation completes without displaying more questions.

The system prompt appears.

Step 3 Unmount and eject the CD-ROM. For details, see "Mounting and Unmounting the CD-ROM".


New Installation—Custom

If you prefer the Custom option:


Step 1 Enter 2 and press Return.

The installation program checks dependencies and system requirements: (For details, see "Server Requirements and Recommendations" section)

If your system does not meet the requirements a warning appears:

System memory is less than the minimum requirement, which may 
affect performance.

If the drive does not have enough space, an error message appears:

There is not enough space in drive drive name.

Select another drive, or free some space on drive drive name.

The installation program displays:

Enter RME database password :

Step 2 Enter a new password.

The following message appears:

Confirm Password

Step 3 Enter the password again to confirm.

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.


The installation completes without displaying more questions.

The system prompt appears.

Step 4 Unmount and eject the CD-ROM. For details, see "Mounting and Unmounting the CD-ROM"


If the system returned any errors, check the installation log file /var/tmp/ciscoinstall.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 some 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 will convert 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 Solaris.

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 upgrade 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. Hence, we do not recommend ending installation using Ctrl-C. You will be required to manually cleanup the installation directories. For more information, see "Frequently Asked Questions" section.

The installation program installs Essentials 3.5 in the same location as Common Services (/opt/CSCOpx by default) and starts CiscoWorks.


Step 1 As root, mount the Essentials CD-ROM. You can either:

Mount the CD-ROM on the local CiscoWorks Server system.

or

Mount the CD-ROM on a remote Solaris system, then access the CD-ROM from the CiscoWorks Server system.

See "Mounting and Unmounting the CD-ROM"for instructions.

Step 2 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 License agreement page appears.

Step 3 Press Return to scroll forward one page, and q to quit the License agreement page. The following message appears:

You must accept this License agreement for the installation to 
proceed.
If you enter N/n, the installation will exit.
Do you accept all the terms of the preceding License agreement? (y/n) 
[y]

Step 4 Press y to accept the agreement, or n to quit.

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

1) Typical ("Typical installation is recommended for all computers.")
2) Custom ("Custom installation can be selected if you want to 
customize the setup options.")

Select one of the installation modes using its number or enter q to 
quit [1]


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.


Step 5 Do one of the following:

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

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


Upgrade Installation—Typical

If you prefer the Typical option:


Step 1 Enter 1 and press Return.

The installation program checks dependencies and system requirements: (For details, see "Server Requirements and Recommendations" section).

If your system does not meet the requirements a warning appears:

System memory is less than the minimum requirement, which may 
affect performance.

If the drive does not have enough space, an error message appears:

There is not enough space in drive drive name.

Select another drive, or free some space on drive drive name.

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.


The installation completes without displaying more questions.

The system prompt appears.

Step 2 Unmount and eject the CD-ROM. For details, see "Mounting and Unmounting the CD-ROM".


Upgrade Installation—Custom

If you prefer the Custom option:


Step 1 Enter 2 and press Return.

The installation program checks dependencies and system requirements: (For details, see "Server Requirements and Recommendations" section)

If your system does not meet the requirements a warning appears:

System memory is less than the minimum requirement, which may 
affect performance.

If the drive does not have enough space, an error message appears:

There is not enough space in drive drive name.

Please select another drive, or free some space on drive drive name.

The installation program displays:

Enter RME database password :

Step 2 Enter a new password.

The following message appears:

Confirm Password

Step 3 Enter the password again to confirm.

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.


The installation completes without displaying more questions.

The system prompt appears.

Step 4 Unmount and eject the CD-ROM. For details, see "Mounting and Unmounting the CD-ROM"


If the system returned any errors, check the installation log file /var/tmp/ciscoinstall.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 Essentials 3.5 data. For more information about upgrading Common Services data, see Installation and Setup Guide for Common Services on Solaris.


Upgrading Essentials 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 Essentials data:


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

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

# /etc/init.d/dmgtd stop

Step 3 Mount the Essentials 3.5 CD-ROM. (For details on mounting the CD-ROM, see "Mounting and Unmounting the CD-ROM") and enter:

# cd cdrom

Step 4 Enter:

# cd cdrom0
# ./export_rme.pl

The following message appears:

Enter the location where you want to export RME data 
[/opt/CSCOpx/rigel]

Step 5 Press Return 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 /opt/export as the backup location, the system creates the directories /opt/export/rme and /opt/export/manifest/rme to store the exported data.

The following message appears:

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

Step 6 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 7 Start the daemon manager. To do this, enter:

# /etc/init.d/dmgtd start


Importing Essentials Data


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


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


Step 1 Access the server that has Essentials 3.5.

Step 2 Copy the exported Essentials 3.3.x or Essentials 3.4.x data from your backup location into $NMSROOT/rigel, where $NMSROOT is the directory in which CiscoWorks is installed (/opt/CSCOpx by default)

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

# /etc/init.d/dmgtd stop

Step 4 Change to the directory, $NMSROOT/rigel/scripts.

Step 5 Enter:

# ./import_rme.pl

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:

# /etc/init.d/dmgtd start


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 system configuration is also preserved.

Running the Installation Program to Reinstall

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.

Hence, we do not recommend aborting installation using Ctrl-C. You will be required to manually cleanup the installation directories. For more information, see "Frequently Asked Questions" section.

The installation program installs Essentials in the same location as Common Services (/opt/CSCOpx by default) and starts CiscoWorks.


Step 1 As root, mount the Essentials CD-ROM. You can either:

Mount the CD-ROM on the CiscoWorks Server system.

or

Mount the CD-ROM on a remote Solaris system, then access the CD-ROM from the CiscoWorks Server system.

See Mounting a Local CD-ROM Drive for detailed mounting instructions.

Step 2 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 displays:

1) Typical ("Typical installation is recommended for all computers.")
2) Custom ("Custom installation can be selected if you want to 
customize the setup options.")

Select one of the installation modes using its number or enter q to 
quit [1]


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

If you choose the Custom reinstallation mode, you will be prompted to enter a password for the Essentials database.


Step 3 Do one of the following:

If you prefer the Typical reinstallation mode, go to
"Reinstalling Essentials—Typical" section.

If you prefer the Custom reinstallation mode, go to
"Reinstalling Essentials—Custom" section.


Reinstalling Essentials—Typical

If you prefer the Typical option:


Step 1 Enter 1 and press Return.

The installation program checks dependencies and system requirements (For details, see "Server Requirements and Recommendations" section)

If your system does not meet the requirements a warning appears:

System memory is less than the minimum requirement, which may 
affect performance.

If the drive does not have enough space, an error message appears:

There is not enough space in drive drive name.

Please select another drive, or free some space on drive drive name.

The installation program checks dependencies and displays the following:

Resource Manager Essentials 3.5 has been detected on your system. If 
you are running an evaluation version of Resource Manager 
Essentials 3.5 and you choose to reinstall the product, you will 
automatically upgrade to a licensed version. Are you sure you want to 
reinstall this software and any required patches? (y/n) [n]

Step 2 Enter y to reinstall, or n to quit.

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.


The installation completes without displaying more questions.

The system prompt appears.

Step 3 Unmount and eject the CD-ROM. For details, see "Mounting and Unmounting the CD-ROM".


Reinstalling Essentials—Custom

If you prefer the Custom option:


Step 1 Enter 2 and press Return.

Step 2 The installation program checks dependencies and system requirements: (For details, see "Server Requirements and Recommendations" section)

If your system does not meet the requirements a warning appears:

System memory is less than the minimum requirement, which may 
affect performance.

If the drive does not have enough space, an error message appears:

There is not enough space in drive drive name.

Please select another drive, or free some space on drive drive name.

The installation program checks dependencies and displays the following:

Resource Manager Essentials 3.5 has been detected on your system. If 
you are running an evaluation version of Resource Manager 
Essentials 3.5 and you choose to reinstall the product, you will 
automatically upgrade to a licensed version. Are you sure you want to 
reinstall this software and any required patches? (y/n) [n]

Step 3 Enter y to reinstall, or n to quit.

The installation program displays:

Enter RME database password :

Step 4 Enter a new password.

The following message appears:

Confirm Password

Step 5 Enter the password again to confirm.

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.


The installation completes without displaying more questions.

The system prompt appears.

Step 6 Unmount and eject the CD-ROM. For details, see "Mounting and Unmounting the CD-ROM"


If the system returned any errors, check the installation log file /var/tmp/ciscoinstall.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


Uninstalling Essentials

The uninstallation program removes files and settings. Uninstallation allows you to remove Essentials application alone or remove Common Services as well. To remove Common Services, you must first remove Essentials.

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


Caution You must use the Essentials uninstall program to remove the product. If you try to remove Essentials manually, you can damage your system. Uninstalling the Essentials software removes the database as well.

Uninstallation takes about 30 minutes.


Step 1 Enter these commands as root to start the uninstall program:

# cd /
# /opt/CSCOpx/bin/uninstall.sh

where /opt/CSCOpx is the default installation directory. If you specified a different directory when you installed Common Services, use the name of that directory.

A message similar to the following appears at command prompt:

1) CiscoWorks Common Services
2) Resource Manager Essentials
3) All of the above
Select one or more of the items using its number separated by comma or 
enter q to quit [q]


Note You cannot uninstall Common Services without uninstalling Essentials.


Step 2 Enter 1, 2 or 3 and press Return. The following prompt similar to the following appears:

Are you sure you want to uninstall: CiscoWorks Common Services, 
Resource Manager Essentials? (y/n) [n]

Step 3 Enter y and press Return to remove the applications you selected, or n to quit the uninstallation.

Step 4 The installation program checks for CiscoWorks packages on the system.

The following prompt appears:

Delete the CiscoWorks packages? (y/n) [n]

Step 5 Enter y and press Return to remove packages, or n to quit.

Ignore all messages that ask if you want to remove packages. These messages are for user information only. The installation program does not accept input to these questions.

When the uninstallation program completes, this message appears:

All files were deleted successfully.

When you remove Common Services or Essentials, the uninstallation program removes changes made to the /etc/services file. The /etc directory still contains all system file changes. The uninstallation messages are written to the /var/tmp/ciscouninstall.log file.


Note The Software Management application stores images that are not removed by the Essentials uninstallation procedure. If you want to permanently remove Essentials, you must manually remove these files from /var/adm/CSCOpx/files/sw_images or the location you specified for storing device software files.



To reinstall Essentials, follow the instructions in the "Reinstalling or Upgrading from the Evaluation Version" section.