Installation and Setup Guide for Resource Manager Essentials 4.0 on Solaris (With LMS 2.5) - Installing Resource Manager Essentials [CiscoWorks Resource Manager Essentials]

Table Of Contents

Installing RME

Product Overview

Installation Overview

Preparing to Install RME

RME Migration Paths

Server Requirements and Recommendations

Minimum Server Requirements

Server Recommendations

Client Requirements

RME Port Usage

Supported Devices

Installing RME

Installation Notes

Performing a New Installation

Running the Installation Program for a New Installation

New Installation—Typical

New Installation—Custom

Data Migration From an Earlier Version

Migrating on the Same Server

Migrating on a Different Server

Running the Migration Script

Validating the Upgrade

Backing Up Your Data

Data Migrated

Data Not Migrated

Reinstalling or Upgrading From the Evaluation Version

Running the Installation Program to Reinstall

Reinstalling RME—Typical

Reinstalling RME—Custom

Post Installation Checklist

Uninstalling RME

Installing RME

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

•Product Overview

•Installation Overview

•Preparing to Install RME

•Installing RME

•Post Installation Checklist

•Uninstalling RME

After installing RME 4.0, if you want to avail these features and additional device support, you must download Resource Manager Essentials 4.0 Service Pack 1 (RME 4.0 SP 1).

•NetShow

•Contract Connection

•SmartCase

•Support for SSHv2

•Bug fixes on RME 4.0

For more information, see Readme for Resource Manager Essentials 4.0 Service Pack 1.

RME 4.0 SP 1 is available at the location:

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

Product Overview

Resource Manager Essentials (RME), one of the major components of CiscoWorks, enables the deployment, monitoring, and configuration of devices across your network.

RME 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 RME CD-ROM contains the Resource Manager Essentials 4.0 installable package.

Installation Overview

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

Table 1-1 Installing RME Task Overview

Task

Steps

References

1. Prepare to install RME.

Verify that server requirements are met.

"RME Migration Paths" section

"Server Requirements and Recommendations" section

2. Install RME.

a. Mount the CD-ROM.

b. Run the installation program.

"Performing a New Installation" section

or

"Data Migration From an Earlier Version" section

and

"Validating the Upgrade" 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 RME applications.

"Preparing to Use RME Applications"

Preparing to Install RME

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

•RME Migration Paths

•Server Requirements and Recommendations

•Client Requirements

•Supported Devices

•RME Port Usage

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

RME Migration Paths

Migration refers to the migration of RME data from an older version of RME to a newer version. Migration from RME 3.4.x or RME 3.5.x is permitted (.x stands for the IDU upgrades). RME 3.4.x or RME 3.5.x backup data is essential for migration.

You can migrate to RME 4.0 from:

RME Releases

Incremental Device Updates (IDU)s / Patches

RME 3.4

You can migrate to RME 4.0 with or without using the following combinations of software releases on RME 3.4:

•All IDU releases on RME 3.4

•All patches released till date on RME 3.4 except point patches

•Data Extracting Engine (DEE) V2

RME 3.5

You can migrate to RME 4.0 with or without using the following combinations of software releases on RME 3.5:

•All the IDU releases on RME 3.5

•All the patches released till date on RME 3.5 except point patches

Caution The migration data also includes Netshow data. If you plan to migrate Netshow data later, you must retain a backup of the RME 3.x data. Netshow will be part of a drop-in release.

For more details see, "Data Migration From an Earlier Version" section.

Server Requirements and Recommendations

This section describes the server requirements and recommendations for CiscoWorks Common Services (Common Services) and RME 4.0.

Minimum Server Requirements

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

Table 1-2 Server System Minimum Requirements

Requirement Type

Minimum Requirements

System hardware

•Sun UltraSPARC IIIi¹

•Color monitor.

•CD-ROM drive

System software

Solaris 2.8 and Solaris 2.9

RME 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 of RME and Japanese for Japanese version of RME.

Memory (RAM)

1 GB

Available drive space

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

•Enough space for storing device software image files³

•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 RME. For installation instructions, see Installation and Setup Guide for Common Services 3.0 (Includes Ciscoview) on Solaris

Additional optional software

•Netscape Navigator 7.0 (if you are using the desktop on the server system) ⁴

•Mozilla 1.7

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

²RME 4.0 is installed in the same directory as Common Services.

³For information about downloaded files, see the "Setting Up Configuration Management" section.

⁴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, you must consider the number of managed devices expected in the Inventory, Configuration Management, and Software Management applications.

These factors affect server performance and user report response time.

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

Table 1-3 Server System Recommendations

Minimum System Configuration

Inventory

Configuration Management

Software Management

UltraSPARC IIIi

Memory: 1 GB
Swap space: 2 GB
Available disk space: 40 GB

0-300 devices

0-300 devices

0-300 devices

Dual Processor UltraSPARC IIIi

Memory: 2 GB
Swap space: 4 GB
Available disk space: 80 GB

Up to 3000 devices

Up to 2000 devices

Up to 1700 devices

Client Requirements

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

Before you access RME from a client system, the system must be properly configured. For more information about configuring clients, see Installation and Setup Guide for Common Services 3.0 (Includes Ciscoview) on Solaris.

Table 1-4 Client System Requirements Summary

Requirement Type

Minimum Requirement

System Software and Hardware

•Client system:

–IBM PC-compatible system with at least a 300 MHz Pentium processor running Windows 2000 (Professional and Server) with Service Pack 3 or Service Pack 4, Windows XP (SP1 and SP2), Windows Server 2003 (Standard and Enterprise Edition).

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

–Sun UltraSPARC IIIi, running Solaris 2.8 or 2.9.

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

Memory (RAM)

512 MB

Browser

One of these browsers:

•On Windows 2000 and Windows XP clients:

–Microsoft Internet Explorer 6.0 (version 6.0.3790.0) in Windows 2003 with SP1

–Microsoft Internet Explorer 6.0.26 and 6.0.28 for Windows 2000 and Windows XP

–Netscape Navigator 7.1

–Mozilla 1.7.1.

•On Solaris clients:

–Netscape Navigator 7.0 ¹ for Solaris 2.8 and 2.9

–Mozilla 1.7 for Solaris 2.8 and 2.9

¹Use Netscape Navigator downloaded only from the Sun site.

RME Port Usage

Table 1-5 lists the ports used by RME:

Table 1-5 RME Port Usage

Protocol

Port Number

Service Name

Direction (of Establishment) of Connection

ICMP

-

Ping

Server to Device

TCP

22

Secure Shell (SSH)

Server to Device

TCP

23

Telnet

Server to Device

TCP

25

Simple Mail Transfer Protocol (SMTP)

Server Internal

TCP

514

rsh Daemon

Server to Device

TCP

1742

SSL (HTTPS)

For SSL, by default, the port is 443.

Client to Server.

TCP

3333

Syslog Collector Service and Syslog Analyzer Service

Server Internal

TCP

43455

RME Database

Server Internal

TCP

4444

Syslog Collector Service and Syslog Analyzer Service

Server Internal

TCP

47000 - 47020

RME CSTM (Common Services Transport Mechanism) Server.

Used for internal application communication.

Server Internal

UDP

69

Trivial File Transfer Protocol (TFTP)

Server to Device

Device to Server

UDP

161

Simple Network Management Protocol (SNMP)

Server to Device

Device to Server

UDP

162

SNMP Traps (Standard Port)

Device to Server only (nGenius Real-Time Monitor);

Server to Device Device to Server (all others)

UDP

514

Syslog

Device to Server

UDP

42342

OSAGENT

Server Internal (Common Services); RSAC to Server via OSAGENT (RME)

Supported Devices

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

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

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

•Downloading device packages.

You can download device packages for RME from:

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

•More information about new device support

To see a list of the device packages installed in the CiscoWorks homepage, select Software Center > Resource Manager Essentials.

Installing RME

This section describes:

•Performing a New Installation

•Data Migration From an Earlier Version

•Reinstalling or Upgrading From the Evaluation Version

While performing RME installation you might be prompted to enter a new RME Database password. For details, see "Troubleshooting the Installation" section.

For more information on creating a new password see the "Password Information" Appendix in Installation and Setup Guide for Common Services 3.0 (Includes Ciscoview) on Solaris.

Installation Notes

Before you begin your installation, note the following:

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

•Install CiscoWorks Common Services 3.0 (Common Services) before installing RME 4.0.

For more information, see the Installation and Setup Guide for Common Services 3.0 (Includes Ciscoview) on Solaris. The install script finds the Common Services directory and installs RME at the same location (/opt/CSCOpx by default). This location is referred to as $NMSROOT in this document.

•You can migrate to RME 4.0 only from RME 3.4 and RME 3.5 with Incremental Device Update (IDU) packages for the respective versions. No other migration paths are supported. RME 3.4 or RME 3.5 backup data is essential for migration. For more information, see RME Migration Paths.

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

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 RME installed, see the "Data Migration From an Earlier Version" section.

Note To import data from a previous version of RME, after installation follow the procedure in the "Data Migration From an Earlier Version" section.

Running the Installation Program for a New Installation

The RME installation takes approximately 30 minutes.

You can press Ctrl-C at any time to cancel 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 RME 4.0 in the same location as Common Services 3.0 (/opt/CSCOpx by default) and starts CiscoWorks.

Step 1 As root, mount the RME 4.0 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)

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

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/
# cd RME
# ./setup.sh 
•For a remote installation, enter:
# cd remotedir
# cd RME
# ./setup.sh
where remotedir is the remote location where the CD-ROM is mounted.

The installation prompts you to press Enter to display the License Agreement.

Step 3 Press Return.

The License Agreement page appears.

Step 4 Press Return to scroll forward one page, or q to quit the License Agreement page. A message appears:
You must accept this License Agreement to proceed with the 
installation.
If you enter N/n, the installation will exit.
Do you accept all the terms of the License Agreement? (y/n) [n]
Step 5 Press y to accept the agreement, or n to quit installation.

A message appears:
To ensure full use of the product features, please select one of the 
following:
(L) If you have a license file for this product,
you will then be prompted for the license file location.
(S) If you know only the serial number and PIN,
but have not obtained the license file.
(E) To evaluate the product only.
You can provide licensing information later if you want to fully 
enable the product.
Step 6 Enter one of these:

•L for License File

•S for Serial number and PIN

•E for Evaluation

•Q to quit.

The installation program checks for required patches and other dependencies and displays:
1) "Typical installation is recommended for all computers."
2) "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]
If you choose the Typical installation mode, the RME database password is randomly generated for you. You can view the password at the end of installation. To proceed with a Typical installation, go to "New Installation—Typical" section.

If you choose the Custom installation mode, you will be prompted to enter the RME database password. To proceed with a Custom installation, go to "New Installation—Custom" section.

New Installation—Typical

To install RME using the Typical option:

Step 1 Enter 1 (for Typical) 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 partition does not have enough space, an error message appears:
There is not enough space in partition drive name.
Select another partition, or free some space on partition drive name.

The installation proceeds without displaying more prompts. This message appears at the end of installation:
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]
•If you enter y, the password appears in clear text on the console.

Note Memorize your password displayed on the console. We recommend you do not write it down.

•If you enter n, the password does not appear.

The installation completes without displaying more prompts and the system prompt appears.

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

New Installation—Custom

To install RME using the Custom option:

Step 1 Enter 2 (for Custom) 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 partition does not have enough space, an error message appears:
There is not enough space in partition drive name.
Select another partition, or free some space on partition drive name.

The installation program displays:
Enter RME database password:
Step 2 Enter a new password. Password should have minimum five characters.

A message appears:
Confirm Password
Step 3 Enter the password again to confirm.

The installation completes without displaying more prompts and 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".

Data Migration From an Earlier Version

Data Migration refers to the migration of RME data from an older version of RME to a newer version. Migration from RME 3.4.x or RME 3.5.x is permitted. RME 3.4.x or RME 3.5.x backup data is essential for migration.

This section describes how to migrate to RME 4.0, if you have RME 3.4.x or RME 3.5.x installed on the server.

•To migrate RME on the same server see, "Migrating on the Same Server" section.

•To migrate RME on a different server see, "Migrating on a Different Server" section on page 1-18. All data available in the RME 3.x backup is not migrated to RME 4.0. For details see, "Data Migrated" section and "Data Not Migrated" section.

If you had installed a version of IDU later than 2.0 on a previous version of RME, and then want to migrate to RME 4.0, you will lose support for new devices.

To retain support for those devices, we recommend that you download and install the latest device packages for RME 4.0 after upgrading to RME 4.0.

Note Data migration across operating systems is not supported.

Migrating on the Same Server

To migrate RME on the same server:

Step 1 Upgrade to Common Services 3.0. For more information, see Installation and Setup Guide for Common Services 3.0 (Includes Ciscoview) on Solaris.

The Common Services 3.0 install script ensures that application data is backed up before migration. During backup, you are prompted to enter the backup directory. For more details see, "Backing Up Your Data" section.

Step 2 Install RME 4.0.

The RME 4.0 install script uninstalls older versions of RME (3.4.x or 3.5.x) along with dependent applications installed in the system.

For example, consider Access Control List Manager (ACLM) and VPN/Security Management as RME dependant applications. During RME 4.0 installation, ACLM, VPN and the older version of RME (3.x) is uninstalled.

For more details, see the "Performing a New Installation" section on page 1-11.

Step 3 Run the migration script to migrate RME 3.4.x or RME 3.5.x data. For more details, see the "Running the Migration Script" section on page 1-19.

Migrating on a Different Server

To migrate RME on a different server:

Step 1 Backup RME 3.4.x or RME 3.5.x data on the system where RME 3.4.x or RME 3.5.x is installed. For more details see, "Backing Up Your Data" section.

Step 2 Install Common Services 3.0 on a clean system. For more information, see Installation and Setup Guide for Common Services 3.0 (Includes Ciscoview) on Solaris.

Step 3 Install RME 4.0 on the system where you just installed Common Services 3.0.

For details see, "Performing a New Installation" section.

Step 4 Transfer the backup data to this server.

Step 5 Run the migration script to migrate RME 3.4.x or RME 3.5.x data. For more details, see the "Running the Migration Script" section on page 1-19.

Running the Migration Script

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

We recommend that you do not cancel migration to avoid errors.

Step 1 As root, login to the system on which you installed RME 4.0.

Step 2 Shut down the daemon manager. To do this, enter:
/etc/init.d/dmgtd stop
Step 3 Run the command:

/opt/CSCOpx/bin/perl /opt/CSCOpx/bin/restorebackup.pl -d backup location -gen version -t tempbackup dir

Example:

/opt/CSCOpx/bin/perl /opt/CSCOpx/bin/restorebackup.pl
-d /ciscoworks/rmebackupdata -gen 2 -t /tmp

where:

•/opt/CSCOpx is the CiscoWorks installation directory.

•-d backup location is the location where RME 3.4 or RME 3.5. backup data is available. This is mandatory.

•-gen version is the version to be migrated to RME 4.0. This is optional. By default, it will restore the latest backup data.

•-t tempbackup dir is used to extract files from the backup into a temporary location. These files are used by the restore backup script. This will be deleted after the data restoration is complete. This is optional. By default, restore backup script uses /opt/CSCOpx/tempbackupdata directory.

The migration script checks the details of the applications installed in the system and applications in the backup archive.

You are prompted to migrate syslog information. A message appears:
Do you want to migrate syslogs [y / n]? Enter y to continue.
If you want to migrate syslog information, choose Y, otherwise choose N.

You are prompted to collect inventory data. A message appears:
Do you want to collect Inventory [y/n]?
If you want to collect inventory information during migration, choose Y, otherwise choose N.

Inventory collection during migration is not recommended. Time taken to complete inventory data collection is considerable.

It depends on number of devices, network speed and device response time. Schedule inventory collection after migration using the user interface. From the CiscoWorks homepage, select RME > Devices > Inventory.

Step 4 Start daemon manager after the migration is completed. To do this, enter:
/etc/init.d/dmgtd start
You have migrated to RME 4.0.

Validating the Upgrade

If you purchased an upgrade license of RME 4.0, you must validate the upgrade on the system where RME 4.0 is installed.

Proof of Purchase (POP) is required to validate an upgrade license of RME 4.0. You are prompted to run a CLI script to validate this upgrade license. This script is available at this location, /opt/CSCOpx/bin/validateupgrade.

•If you plan to use the same machine (that has RME 3.4.x or RME 3.5.x) for RME 4.0 installation, you will not be prompted to run this CLI script.

In this case, Proof of Purchase validation is done automatically.

•If you plan to use a new/different server for RME 4.0 (that has 3.4.x or 3.5.x installed on a different server), a message appears at the end of the RME 4.0 installation to validate the upgrade license.

The product will be in the nag mode until POP is validated. This message appears till you complete the upgrade validation:
This software installation requires reusing a license provided in 
a previous version. If a previous license is not available or 
proof of purchase validation was not performed, you may continue 
to install in NAG mode, while arranging with your Cisco 
representative to return this product and purchase a full licensed 
version.
To validate the upgrade license:

Step 1 Go to C Shell by running the command csh.

Step 2 Set the environment using the command:
setenv LD_LIBRARY_PATH 
/opt/CSCOpx/objects/db/lib:/opt/CSCOpx/lib:/opt/CSCOpx/MDC/lib
Step 3 Change the directory to /opt/CSCOpx/bin using the command:
cd /opt/CSCOpx/bin
Step 4 Run the CLI script:
./validateupgrade
The following prompt appears:
This utility will validate your proof of purchase of the product and 
allow you to obtain an upgrade license.
Please enter the CiscoWorks product for the proof of purchase 
validation (such as LMS, ITEM, VMS):
Step 5 Enter the bundle name and press the Return key.

The following prompt appears:
Please select the source for upgrade validation from the following
1. Validate from a CD (older version of RME).
2. Validate from a remote server (where older version of RME is 
installed).
Please enter 1 to upgrade from a CD; enter 2 to upgrade from a remote 
server  [1 / 2] :
•If you select 1, a prompt appears:
Please insert the previous versions of RME CD into the CDROM drive 
and provide the absolute path to the CD drive:
Enter the CDROM drive path. For example, /cdrom/cdrom0

•If you select 2, a prompt appears:
Please enter the remote CiscoWorks server host name or the IP 
address : 
Please enter the remote CiscoWorks server http or https port 
number :
Please enter the remote CiscoWorks server login name :
Please enter the remote CiscoWorks server login password :
Please be patient. Upgrade validation is in progress from a remote 
server.
Enter the following details of the remote CiscoWorks server:

–Host name or the IP address. For example, ciscoworks-rme

–http or https port number. For example, 1741

–Login name. For example, admin

–Login password.

This message is appears after you enter the above details:
Please be patient. Upgrade validation is in progress from a remote 
server.
After the RME upgrade validation completes, this message is appears:
Validation succeeded.
Backing Up Your Data

To backup your data:

Step 1 Access the CiscoWorks Server and log in.

For information, see Invoking CiscoWorks HomePage and Logging in to Common Services sections in the User Guide for CiscoWorks Common Services.

Step 2 From CiscoWorks Homepage, select Common Services > Server > Admin > Backup.

The Backup page appears.

Step 3 Enter the path name of the target directory in the Set Backup Schedule dialog box.

We recommend that you use a different directory from the directory where CiscoWorks is located, for example, /cw/backups.

Step 4 Check the Immediate radio button in the Set Backup Schedule dialog box.

Step 5 Click Apply to begin the backup.

This process may take some time to complete. For more information, see the Online help.

Backing up Data Using CLI

To backup your data using CLI, run the following command at your command prompt:
NMSROOT/bin/backup.pl BackupDirectory LogFile Num_Generations
BackupDirectory—Directory that you want to be your Backup directory.

LogFile—Log file name

Num_Generations—Maximum backup generations to be kept in the backup directory.

Before starting migration, all currently scheduled jobs must be suspended.

Data Migrated

The data migrated from RME 3.4.x or 3.5.x to RME 4.0:

•Devices and its credentials are updated in the Device Credential Repository (DCR).

•Device configurations collected from devices using Config Archive.

•Change Audit history of all devices. This includes details changes that each application maintains.

•Images in Software Management repository.

•NetConfig user defined templates and Syslog custom filters.

Caution The migration data also includes Netshow data. If you plan to migrate Netshow data later, you must retain a backup of the RME 3.x data. Netshow will be part of a drop-in release.

See the following sections for application specific details on data migrated:

•Device Selector

•Inventory

•Config Archive

•NetConfig

•Config Editor

•Software Management

•Syslog

•Change Audit

Device Selector

Public and Private Static Device Views

For private views, device groups are created with the RME 3.4 or RME 3.5 username. You may use groups if the same username exists in RME 4.0. If the username does not exist in RME 4.0, the group is assigned to NetAdmin.

Inventory

The inventory data migrated from RME 3.4.x or 3.5.x to RME 4.0:

•Change History

•User defined fields and their display names

•Device attributes and credentials

•RME Device Management Application updates

RME Device Management Application updates DCR with the list of devices and appropriate credentials.

Migration Strategy

All devices in the managed state in RME 3.4.x and RME 3.5.x are migrated to RME 4.0. The migration strategy is:

For the list of devices maintained in RME 3.4 or RME 3.5:

1. Device Management Application is supplied with the list of devices migrated from RME 3.4 or RME 3.5.

2. Device Management Application assigns the device ID to the device. The device ID is the same ID the device used in RME 3.4 or RME 3.5. Device Management Application also marks the state of the devices as normal.

3. You are prompted to initiate inventory collection.

If you choose to collect inventory data during migration, inventory collection is triggered towards the end of migration.

We recommend that you do not perform Inventory collection during migration. This is because it takes a long time to complete inventory data collection.It depends on number of devices, network speed and device response time.

Schedule inventory collection after migration using the user interface. To do this select RME > Devices > Inventory. from the CiscoWorks homepage.

For devices in other states in RME 3.4 or RME 3.5 (unreachable, aliased, or suspended):

Credentials are associated. These devices and their associated credentials are migrated to DCR. For details, select Devices > Device Management > RME Devices, from the CiscoWorks homepage

Config Archive

The Config Archive data migrated from RME 3.4.x or 3.5.x to RME 4.0:

•Raw Configuration files

All running, startup and VLAN configurations

•Shadow directory.

•ChangeAudit records. This includes Configuration change details.

•Archived configuration versions

NetConfig

The NetConfig data migrated from RME 3.4.x or 3.5.x to RME 4.0:

•User Defined Templates (UDT)

UDT RouterUDT in RME3.5 is migrated as RouterUDTTask with the UDT template, RouterUDT in RME4.0.

•Default Template Usage

All templates are assigned to Admin on migration by default. If your RME 3.4 or RME 3.5 user exists in RME 4.0, the task mappings are migrated. However, device to task mapping is not migrated.

Config Editor

Editing Mode in which the files are opened. It is either `Raw' or `Processed'.

Software Management

The Software Management data migrated from RME 3.4.x or 3.5.x to RME 4.0 are Image Libraries.

Exceptions

•Images of device types that do not have device support are not migrated. The corresponding device package may not be installed.

•Images are migrated with default attributes. If you made any changes to the image attributes in RME 3.4 or RME 3.5, you must redo the changes after migrating the image to RME 4.0.

Syslog

The Syslog data migrated from RME 3.4.x or 3.5.x to RME 4.0:

•Automated Actions and Filters

Automated Actions and Filters are migrated. However, the scripts associated with the automated actions are not migrated.

Hence, you must manually copy the scripts from RME 3.4 or RME 3.5 installation to the required location in RME 4.0. Ensure that the scripts are operational on the RME 4.0 system for the automated tasks to function properly.

•Syslog messages

Syslog messages are critical. However, the data volume is huge. Hence, you may choose to migrate the Syslog messages during migration.

•RME 4.0 retains data up to 7 days by default. During migration, if you attempt to restore RME 3.4 or RME 3.5 data older than the configured number of days on RME 4.0, messages are purged when the next Syslog purge job is triggered.

•Custom reports

Change Audit

All change records with the details are migrated.

Data Not Migrated

This section lists the data that is not migrated RME 3.4.x or 3.5.x to RME 4.0. It also states the tasks that you need to recreate.

•Scheduled jobs that are yet to be executed.

These jobs must be recreated with required approvals sought anew.

•Application execution logs.

The structure and components of earlier versions of RME in comparison to RME 4.0 are different. Hence, earlier versions of logs are irrelevant.

•Completed jobs.

Completed jobs cannot be edited or used to create new jobs. However, the details of job execution are available. View the Change Audit reports for details about how devices were affected.

•Admin Settings

RME 4.0 default configuration overrides configurations of earlier versions of RME. For the admin settings of your RME 3.x system, see AdminSettings.txt file. The file is usually available in $NMSROOT. You may use this file as a baseline to configure your RME 4.0 system, if required.

See the following sections for application specific details on data not migrated:

•Device Selector

•Inventory

•Config Archive

•NetConfig

•Config Editor

•Software Management

•Syslog

•Change Audit

•Jobs

Device Selector

Dynamic Views

RME 3.4 or RME 3.5 dynamic views are not migrated because of the device classification changes to Meta Data Format (MDF) in RME 4.0.

Inventory

The inventory data not migrated from RME 3.4.x or 3.5.x to RME 4.0:

•Detailed Device Data

Importing a device in RME4.0 fetches device data from the managed device.

•Scan History

This feature is not supported in RME 4.0.

•Collection and Polling Interval

Default system inventory collection and polling job is created.

•Inventory Change Filter

Inventory change filter details are not backed up in RME 3.4 and RME 3.5. This data must be recreated in RME4.0.

•Check device attributes

Check device attribute data is overwritten when invoked.

Config Archive

The Config Archive data not migrated from RME 3.4.x or 3.5.x to RME 4.0:

•Protocol order and archive location

The RME 4.0 settings take precedence.

•Admin settings

Default update schedule, purge policy and syslog policy.

•Label information.

•Custom queries

•Last Configuration change time for devices.

•Running startup out of synchronized data.

NetConfig

The NetConfig data not migrated from RME 3.4.x or 3.5.x to RME 4.0:

•Template to Device Type Assignment

In RME 3.4 or RME 3.5, User Defined Templates are associated with a device category, while in RME 4.0 the categorization is based on MDF type. Hence, the translation from RME 3.4 or RME 3.5 categorization to RME 4.0 is not feasible.

•Jobs and details

•User Preferences and Admin Settings

Config Editor

The Config Editor data not migrated from RME 3.4.x or 3.5.x to RME 4.0:

•Negation rules

In RME 3.4 or RME 3.5, negation rules are maintained in flat files. In RME 4.0, RME device packages handle this task.

•Insertion rules

In RME 4.0, insertion rules are maintained by Config archive.

•User Preferences and Admin Settings

Software Management

The Software Management data not migrated from RME 3.4.x or 3.5.x to RME 4.0 is:

•Admin Settings

Admin settings are stored in a flat file. You may access the file after migration. Refer to your old admin settings from the text file and configure RME 4.0.

•Jobs and details

Syslog

The Syslog data not migrated from RME 3.4.x or 3.5.x to RME 4.0:

•Admin settings

The devices that are not managed in RME 4.0 and are represented using wildcards, are ignored during migration of automated action, message filters and custom reports.

Change Audit

The Change Audit data not migrated from RME 3.4.x or 3.5.x to RME 4.0:

•Admin settings

•Exception periods

Jobs

In RME 3.x, jobs are serialized objects. You could copy the RME job objects from one 3.x version to another. In RME 4.0, the job data structures are not serialized objects. Hence, you cannot migrate jobs.

Reinstalling or Upgrading From the Evaluation Version

This section explains how to reinstall RME 4.0 or upgrade from an evaluation version of RME 4.0.

The installation program is able to detect whether you have already installed RME 4.0. 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 RME installation takes approximately 30 minutes.

You can press Ctrl-C at any time to cancel 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 the "Frequently Asked Questions" section.

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

Step 1 As root, mount the RME 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.

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

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/
# cd RME
# ./setup.sh
•For a remote installation, enter:
# cd remotedir
# cd RME
# ./setup.sh
where remotedir is the remote location where the CD-ROM is mounted.

The installation program displays the License agreement.

Step 3 Select I Agree.

The installation options appear:
Choose the type of Setup you prefer.
1) "Typical installation is recommended for all computers."
2) "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]
•If you choose the Typical installation mode, the password assigned to the previous installation of RME database will be retained.

•If you choose the Custom installation mode, you will be prompted to enter a password for the RME database.

Step 4 Do either of the following:

•To use the Typical reinstallation mode, go to
"Reinstalling RME—Typical" section.

•To use the Custom reinstallation mode, go to
"Reinstalling RME—Custom" section.

Reinstalling RME—Typical

To use the Typical option:

Step 1 Enter 1 (Typical) 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 partition does not have enough space, an error message appears:
There is not enough space in partition drive name.
Select another partition, or free some space on partition drive name.

The installation program checks dependencies and displays the following:
Resource Manager Essentials 4.0 has been detected on your system, are 
you sure you want to reinstall (y/n):
Step 2 Enter y to reinstall, or n to quit.

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

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

Reinstalling RME—Custom

To use the Custom option:

Step 1 Enter 2 (for Custom) 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 partition does not have enough space, an error message appears:
There is not enough space in partition drive name.
Select another partition, or free some space on partition drive name.

The installation program checks dependencies and displays the following:
Resource Manager Essentials 4.0 has been detected on your system. Are 
you sure you want to reinstall this software? (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 installation completes without displaying more prompts and 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-6 lists the common post-installation that are required to be configured after installing RME. For details, see "Preparing to Use RME Applications".

Table 1-6 Post Installation Checklist

Task

How to get there...

Verifying System Settings

RME > Administration > System Preferences

Or

Common Services > Server > Admin > System Preferences

Job Approval

Creating approver list

RME > Administration > Approval > Create/Edit

Enabling job approval

RME > Administration > Approval > Approval Policies

Inventory Management

Add Devices

RME > Devices > Device Management > RME Devices.

Checking Add / Import Summary

RME > Devices > Device Management.

Checking device attributes

RME >Devices > Device Management> Device Credential Verification > Select Devices > View Credential Verification Report

Changing device attributes

RME >Devices > Device Management > Device Credential Verification > Select Devices > Edit Device Credentials

Deleting unwanted devices

RME > Devices > RME Devices > Select Devices > Delete

Scheduling collection

RME >Devices > Inventory > Inventory Jobs > Create

Manually updating inventory

RME >Devices > Inventory > Inventory Jobs > Create> Choose Immediate Job

Configuration Management

Performing general setup tasks

RME > Admin > Config Mgmt

Config Editor Administration

RME > Admin > Config Mgmt > Config Editor

Or

RME > Admin > Config Mgmt > Config Job Policies > ConfigEditor

NetConfig Administration

RME > Admin > Config Mgmt > Config Job Policies > NetConfig

Software Management

Establishing Software Management Preferences

RME > Administration > Software Management > View/Edit Preferences

Importing Baseline of Software Images

RME > Software Management > Software Repository

Scheduling Synchronization Job

RME > Software Management > Software Repository > Software Repository Synchronization

Change Audit

Defining Exception Periods

RME > Tools > Change Audit > Exception Periods

Forwarding Traps

RME > Tools > Change Audit > Automated Actions

Syslog Analyzer

Verifying Storage Options

RME > Admin > Syslog > Set Backup Policy

Defining Message Filters

RME > Tools > Syslog > Message Filter

Defining Automated Actions

RME > Tools > Syslog > Automated Action

Creating Custom Syslog Reports

RME > Reports > Custom Templates

Uninstalling RME

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

Before removing the RME, you must remove any applications that depend on the product. That is, the applications for which installing RME is a prerequisite.

Caution You must use the uninstall program to remove the product. If you try to remove RME manually, CiscoWorks may stop functioning. Uninstalling the product 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.

Note You cannot uninstall Common Services without uninstalling RME.

A message similar to the following appears at command prompt:
1) CiscoView 6.1
2) Integration Utility 1.6
3) CiscoWorks Common Services 3.0
4) Resource Manager Essentials 4.0
5) 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 RME.

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

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

The installation program checks for CiscoWorks packages on the system and the following prompt appears:
Delete the CiscoWorks packages? (y/n) [n]
Step 4 Enter y and press Return to remove packages, or n to quit.

Messages prompting you to remove packages, may appear. You may ignore them since they are only for information. The installation program does not accept input to these questions.

After the uninstallation program completes, this message appears:
All files were deleted successfully.
When you remove Common Services or RME, 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.

To reinstall RME, follow the instructions in the "Reinstalling or Upgrading From the Evaluation Version" section.