CiscoWorks Resource Manager Essentials

Document ID: 13484

Contents

Introduction
Prerequisites
      Requirements
      Components Used
      Conventions
Procedure for Solaris
      Systems that Run Solaris 2.6 With All CD One-Required Patches Installed
      Systems Running Solaris 2.5.1 or Lacking Patches Required by CD One
Procedure for NT
Cisco Support Community - Featured Conversations
Related Information

Introduction

This document describes how to restore a Resource Manager Essentials (RME) 2.x database to a different server from the one on which RME 2.x is installed. This server also has CiscoWorks, CD One, and RME 3.0, 3.1, 3.2, or 3.3 installed.

Prerequisites

Requirements

There are no specific requirements for this document.

Components Used

The information in this document is based on the Resource Manager Essentials (RME) 2.x database installations on Solaris and Windows. This procedure has not been tested on HP-UX and AIX.

Note: You can use the procedures described here across platforms. It is possible to collect the RME 2.x data in a Solaris server and restore it in RME 3.0, 3.1, 3.2, or 3.3 on an NT platform, and the opposite.

The information in this document was created from the devices in a specific lab environment. All of the devices used in this document started with a cleared (default) configuration. If your network is live, make sure that you understand the potential impact of any command.

Conventions

This document uses the following conventions:

• Old server refers to the system running RME 2.x. This is the server from which you obtain the database.

• New server refers to the system with CD One and RME 3.x installed. This is the server to which you are restoring the database.

For more information on document conventions, refer to the Cisco Technical Tips Conventions.

Procedure for Solaris

Systems that Run Solaris 2.6 With All CD One-Required Patches Installed

For RME 2.x systems that run Solaris 2.6 with all CD One-required patches installed, take these steps to save your data. If your old server runs Solaris 5.2.1, or if it does not have the patches required for CD One installed, take the steps in the next section.

Note: You must first log in as root or super-user.

1. Mount the CD One media and change directory to the installation directory:

   # cd /cdrom/cdrom0 
   

2. Run the setup.sh script, and respond to the prompts:

   Note: This script asks if you wish to continue with the installation and disable RME and CiscoWorks for Switched Internetworks (CWSI). When you get to this part, be sure to answer no.

   # ./setup.sh 
   Setup has detected the following product on the destination server:    
   - Resource Manager Essentials (RME) version 2.0 or higher 
   - CWSI Campus (Campus) version 2.2 or higher 
   - TrafficDirector (TD) version 5.3 or higher 
   
   [ other comments from script are not shown here ] 
   Do you want to proceed? (y/n)? [y] y
   

   Press Enter or type y here.

   Please specify the path of temporary 
   directory where the data from the current products 
   will be archived ? [/opt/CW2000/OldData] 
   Hit "Enter" to use the default /opt/CW2000/OldData 
   (this will be created if it does not exist) 
   or specify an alternate destination directory. 
   Do not specify a directory which contains any other existing data. 
   The script will now save the existing data. 
   The current product's data has been saved. 
   Setup will now uninstall RME/CWSI and TD. 
   Do you want to continue? (y/n)? [y] no
   

   Enter no here.

   Upgrade stopped at user's choice.# 

3. You can now move the saved data to the new server (using tar, ftp, or something similar) or nfsmount the directory where the data is saved. Then use the script, bg2rigel.pl, on the new server.

   If you want to use nfsmount, skip to step 7.

4. To move the data, use tar to create an archive file, which you can then compress.

   # cd /opt/CW2000 
   # tar -cvf /var/tmp/olddata.tar . 
   # cd /var/tmp 
   # compress olddata.tar
   

5. Now use the ftp command (be sure to use binary mode) to transfer the file:

   # ftp 
   username:
   Password:
   bin cd <target directory>
   cd <target directory>
   put olddata.tar.Z
   quit 
   

6. On the new server, you can uncompress and untar the data files:

   # cd <directory containing olddata.tar.Z>
   # uncompress olddata.tar.Z
   # tar -xvf olddata.tar
   

7. Finally, in the new server, run the script that imports the data:

   # cd /opt/CSCOpx/conf/bg2rigel/scripts
   # ./bg2rigel.pl -I <target directory>/OldData rme 
   
   

Systems Running Solaris 2.5.1 or Lacking Patches Required by CD One

If your RME 2.x system runs Solaris 2.5.1, or it lacks patches required by the CD One install, use this alternative procedure:

Note: You must be logged-in as root or super-user.

1. Mount the CD One media and change directory to the installation directory:

   # cd /cdrom/cdrom0 
   
   

2. Enter the Bourne shell:

   # /bin/sh 
   
   

3. Make a temporary setup directory named /tmp/setup:

   # mkdir /tmp/setup 
   
   

4. Define and export these environment variables:

   # SETUPDIR=. ; export SETUPDIR
   # TOC=disk.toc ; export TOC 
   

5. Run the upgradebg.sh script, and respond to the prompts:

   Note: This script asks if you want to continue with the installation, and disable the existing RME and CWSI. When you get to this point, be sure to answer no.

   # /bin/sh ./upgradebg.sh 
   Setup has detected the following product on the destination server: 
   - Resource Manager Essentials (RME) version 2.0 or higher 
   - CWSI Campus    (Campus) version 2.2 or higher 
   - TrafficDirector (TD) version 5.3 or higher    
   - [ other comments from script are not shown here ] 
   Do you want to proceed?    (y/n)? [y] y
   

   Press Enter key or type y here.

   Please specify the path of temporary directory where the data 
   from the current products will be archived ? [/opt/CW2000/OldData] 
   Enter cr to use the default /opt/CW2000/OldData (this will be 
   created if it does not exist) or specify an alternate destination directory. 
   Do not specify a directory which contains any other existing data. 
   The script will now save the existing data. 
   The current product's data has been saved. 
   Setup will now uninstall RME/CWSI and TD. 
   Do you want to continue? (y/n)? [y] no
   

   Enter no here:

   Upgrade stopped at user's choice.      # 
   Remove the 

6. Remove the temporary directory you created in step 3:

   # rm -rf /tmp/setup 
   

7. You can now move the saved data to the new RME 3.0 system (using tar or ftp, for instance) or nfsmount the directory where the data was saved. Then use the script, bg2rigel.pl, on the new system as described in the RME 3.0 installation guide. If you want to use nfsmount, skip to step 11.

8. To move the data, use tar to create an archive file, which you can then compress:

   # cd /opt/CW2000# tar -cvf /var/tmp/olddata.tar# cd /var/tmp# compress olddata.tar
   

9. Now use ftp (be sure to use binary mode) to transfer the file:

   # ftp 
   username: 
   Password: 
   bin cd <target directory>
   cd <target directory>
   put olddata.tar.Z    
   quit
   

10. Now on the new system, you can uncompress and un-tar the data files:

    # cd <directory containing olddata.tar.Z>
    # uncompress olddata.tar.Z # tar -xvf olddata.tar # tar -xvf olddata.tar
    
    

11. Finally, on the new server, run the script that imports the data:

    # cd /opt/CSCOpx/conf/bg2rigel/scripts 
    # ./bg2rigel.pl -I target directory/OldData rme 
    

Procedure for NT

Complete these steps:

1. Insert the CD On installation CD into the CD ROM drive of the PC where you have RME 2.x installed.

2. In order to initiate the CD One installation, click Install.

3. When you see the Previous Versions Found window that notifies you that CiscoWorks is already installed in the PC, click Yes in order to proceed with the installation.

4. You now see a series of messages warning that CiscoWorks is being stopped. If you are prompted at this point to stop the Traffic Director, click OK.

5. After all of the CiscoWorks processes are stopped, this window displays.

   

   Click Next if you want to save the data in the default C:\CiscoWorks\OldData directory. In order to select a different location, click Browse.

   Note: In order to make sure that the OldData directory and any of the non-default directories you select are empty, use Browse.

6. At this point, some files are created under the OldData directory, that contains the relevant information to restore to the new server. It may take some minutes to complete this operation.

7. This window now appears. Answer no.

   

8. Transfer the contents of the OldData directory to the new server. Compress these files and directories. In the new server, restore the contents of the OldData directory exactly as they were in the old server, with the same the directory structure.

9. Go to this directory on the new server: C:\Program Files\CSCOpx\conf\bg2rigel\scripts.

   Note: This line is valid, provided that you have CiscoWorks installed under C:\Program Files\CSCOpx. Otherwise, you need to go under the relative path CSCOpx\conf\bg2rigel\scripts.

10. Execute this command:

    perl bg2rigel.pl -I <target directory>\OldData rme 
    
    
    

    where <target directory> is the directory where you recreated the OldData directory.

Cisco Support Community - Featured Conversations

Related Information

• Technical Support - Cisco Systems