Cisco WAN Manager Installation Guide, 15.3.00 - 4 - Upgrading the CWM from an Earlier Version [Cisco WAN Manager]

Table Of Contents

Upgrading the CWM from an Earlier Version

Upgrading from Solaris 8 to Solaris 9

Uninstalling the WANDEST Server

Saving Databases

Installing Solaris 9 and OpenView

Upgrading the CWM Software

Before You Start

Selecting the Upgrade Mode

Upgrading with the InstallShield GUI

Upgrading in Console Mode

Creating a CWM Auto-Restart Shell Script

Installing RtmProxy

Upgrading to CWM 15.3.00 from Solaris 8 to Solaris 9 with Multiple CWM Gateways

Initial Conditions before Upgrade

Solaris 8 to 9 Upgrade Procedure

Upgrading to CWM 15.3.00 Solaris 9 from 15.1.50 Solaris 9 with Multiple CWM Gateways

Post-Installation Tasks

Upgrading the CWM from an Earlier Version

This chapter describes how to upgrade to CWM 15.3.00 from an earlier CWM version. You can upgrade to CWM 15.3.00 from any of the following releases:

•CWM 15.1.50 (latest patch) on Solaris 9 to CWM 15.3.00 on Solaris 9

•CWM 15.1.50 (latest patch) on Solaris 8 to CWM 15.3.00 on Solaris 9

•CWM 15.0 (latest patch) on Solaris 8 to CWM 15.3.00 on Solaris 9

To upgrade from an earlier CWM release, you must first upgrade to one of the releases listed above. To do so, see the installation guide and the release note for the appropriate CWM version (CWM 15.1.0 or CWM 15.1.50) at this URL:

http://www.cisco.com/en/US/partner/products/sw/netmgtsw/ps2340/tsd_products_support_series_home.html

Upgrading from Solaris 8 to Solaris 9

Upgrading from one operating system to another requires that you install a completely new Solaris 9 and CWM application. However, the upgrade can be simplified by preserving the CWM database and configuration files throughout the upgrade process.

To upgrade without disrupting the network management functions, the existing Solaris 8 CWM systems should be configured with multiple CWM gateways. The CWM gateways are then upgraded one at a time, which preserves network management throughout the upgrade process. This process is described in Upgrading to CWM 15.3.00 from Solaris 8 to Solaris 9 with Multiple CWM Gateways.

Perform procedures in this order:

•Uninstalling the WANDEST Server

•Saving Databases

•Installing Solaris 9 and OpenView

Uninstalling the WANDEST Server

If the WANDEST server is installed on the CWM, it must be uninstalled before the database is exported.

Saving Databases

The following procedures describe how to save the CWM and SSC databases.

Saving CWM Databases

During the installation of Solaris 9, all the CWM server disk files are erased as the disks are formatted and partitioned. The procedure below ensures that the saved database and other files are stored on a removable device such as a tape or saved temporarily on a separate system so that they can be restored to the CWM machine after Solaris is installed.

To save the CWM database and other needed files, perform the following steps.

Step 1 Stop the CWM core processes if not already stopped.

Step 2 Run uninstall.sh from the /usr/users/wandest/ directory.
host% cd /usr/users/wandest 
host% ./UnInstallWDServer.sh
This command uninstalls the wandest server.

Step 3 Log in as user svplus.

Step 4 Create a directory to hold the saved Informix database.
host% mkdir <save_database_directory>

Caution Do not create the directory under the /usr/user directory. The directory should be on a separate NFS-mounted disk. If an NFS-mounted disk is not available, the directory can be on one of the CWM server disks, but the directory and its contents must be FTPd to another system before Solaris 9 is installed.

Step 5 Change the permissions of the directory:
host% chmod 777 <save_database_directory>

Step 6 Change the current directory to the <save_database_directory> directory:
host% cd <save_database_directory>

Step 7 Verify that enough disk space is available for the Informix OnLine database:
host% onstat -d

Step 8 Enter the dbexport command:
host% dbexport -o <save_database_directory><database_name>

The default name for <database_name> is stratacom and cannot be changed.

Step 9 Repeat Steps 6 and 7 to export the scmdb and statsdb databases using the same <save_database_directory> directory.

Step 10 Copy the svplus.version file (found in the /usr/users/svplus/etc directory) to the same <save_database_directory> directory.

Step 11 Copy any configuration files (such as network.conf) that should be saved to the same <save_database_directory> directory:

•If the <save_database_directory> directory is on a separate NFS-mounted disk, no further steps are necessary.

•If the <save_database_directory> directory is on the CWM machine, it must be transferred to an external location. For example, save it to a tape by using the tar cvf/dev/rmt/0 command or using the FTP facility to copy it to another machine.

If the preceding steps have been performed, the Informix OnLine database is now saved to a safe location.

Saving SSC Workstation Databases

If the upgrade to CWM 15.3.00 also involves upgrading one or more SSC workstations in which the statsdb databases need to be saved, the upgrade of CWM and the upgrade of the SSC workstations must be coordinated.

Upgrading to a SSC is the only configuration upgrade that is supported. Because SSC workstations do not support a local statsdb database, any existing statsdb databases on the standalone systems must be saved (if needed) to the CWM server as part of the upgrade process.

To save statsdb databases, perform the following procedure.

Caution This procedure must be performed before using the CWM 15.3.00 upgrade program.

Step 1 At each SSC workstation, execute the script, statsdbunload.csh, that is located on the SCMSA CD (See Chapter 9 for details). The result is a directory called "statsdbupload" located in usr/users/svplus/tmp on the statistics collection workstation.

Step 2 If the statsdbunload.csh script has been executed on multiple workstations, rename the resulting directories so that each name is unique. Use names such as statsdbupload, statsdbupload1, and statsdbupload2.

Step 3 Save all the statsdbupoad(x) directories.

If the upgrade at the CWM server involves an upgrade from Solaris 8 to Solaris 9, use the FTP facility to copy the directories to the same place that was used for saving (exporting) the CWM databases and files.

If the upgrade does not involve a Solaris upgrade, use the FTP facility to copy the directories to usr/users/svplus/tmp on the CWM server.

Step 4 The installation of Solaris 9 and the upgrade of the CWM server can now proceed. When the CWM upgrade procedure is executed, the saved directories are located and the data is incorporated into the CWM statsdb.

Installing Solaris 9 and OpenView

When the CWM database and other files have been saved, install the following sequence of programs.

1. Solaris 9

2. Solaris 9 patches as specified in these release notes

Note Make sure that the machine is rebooted at this point.

3. HP OpenView (if needed)

http://www.cisco.com/en/US/products/sw/netmgtsw/ps2340/products_installation_guide_book09186a008047b1e4.html

When these programs have been installed, the CWM can be upgraded.

Upgrading the CWM Software

To upgrade the CWM software, first read the Before You Start section and then choose the mode that you want to use to perform the upgrade, by using the InstallShield GUI or in Console Mode:

•Before You Start

•Selecting the Upgrade Mode

•Upgrading with the InstallShield GUI

•Upgrading in Console Mode

The installation procedure (InstallShield GUI or Console Mode) is divided into these three phases:

•Initial Upgrade Phase

Note For the next two steps in the upgrade, refer to the procedure for performing new installations. Any differences pertaining to upgrades are delineated in these sections:

•See Configuring the Informix Partitions

•See Completing the Installation or Upgrade

This section also contains two sections on upgrading with multiple CWM gateways:

•Upgrading to CWM 15.3.00 from Solaris 8 to Solaris 9 with Multiple CWM Gateways

•Upgrading to CWM 15.3.00 Solaris 9 from 15.1.50 Solaris 9 with Multiple CWM Gateways

Before You Start

Ensure that Solaris 9 and the requisite Solaris 9 patches have been installed. Make sure that you reboot the system after Solaris 9 and the patches are installed.

If the CWM upgrade involves upgrading from a Solaris 8 to Solaris 9 platform, ensure that the exported databases and files are accessible to the system:

•If the exported databases are saved to a tape or NFS mounted directory, mount the exported database on the CWM (either tape or NFS mounted directory).

•Alternatively, if the exported databases are using the FTP facility to copy to another system, create a directory on the CWM and use FTP to copy the databases and other files back to that directory.

Whichever method is used, note the path to the location where the databases now reside. You will need this path when you upgrade to the Solaris 9 version of CWM.

Selecting the Upgrade Mode

To begin the upgrade and select the upgrade mode, follow the steps below.

Step 1 Insert the CWM 15.3.00 CD-ROM No. 1 into the CD-ROM drive.

Step 2 Enter the following commands:
#  cd /cdrom/cdrom0
#  ls 
Step 3 Check for the InstallCWM.sh file and enter the following command to begin the installation:
#  ./InstallCWM.sh
After you enter the ./InstallCWM.sh command, this message is displayed.
Console Mode Option is recommended when you cannot connect to X Server 
 from current terminal (See if you can open and xterm to check ! ) 
 
Do you want to Launch Installer in Console Mode  ? (Yes / No ): [No] :y 
The Console Mode Install is a command line script procedure. It is an alternative to the GUI and is intended for users who do not have access to an X window device. By using Console Mode Install, you can install CWM with an alphanumeric terminal or a PC in terminal emulator mode.

Step 4 Designate if you want to use the InstallShield GUI or the Console Mode Install to continue the upgrade procedure:

•To use the Console Mode Install, click Y (for yes) and then click Enter. See Upgrading in Console Mode.

•To use the InstallShield GUI, click N (for no) and then click Enter. See Upgrading with the InstallShield GUI.

Upgrading with the InstallShield GUI

After you choose InstallShield GUI method for performing the upgrade, the installation classes start loading. This process takes several minutes.

Initial Upgrade Phase

To start the initial upgrade phase, the CWM Installation Welcome window in the GUI appears.

Step 1 Click Next. The license agreement window appears.

Step 2 Click I accept and then click Next. The upgrade window appears.

Step 3 Because you are performing an upgrade, click Yes and then click Next. The CWM version window appears.

Step 4 Click the CWM version that you are upgrading from: 15.0 or 15.1.50, and then click Next. The Solaris version window appears.

Step 5 Click the Solaris version from which you are upgrading and then click Next:

•Solaris 8—If you are upgrading from a Solaris 8 to a Solaris 9 platform. If you selected Solaris 8, the Database Path Window appears for you to enter the path for importing the databases. Go to Step 6.

•Solaris 9—If the previous version of CWM is already running on a Solaris 9 platform, the Primary/Secondary window appears. Go to Step 7.

Step 6 Enter the path for importing the database and then click Next. The Primary/Secondary window appears.

Step 7 Click Primary or Secondary for the CWM being upgraded and click Next. Whether you selected Primary or Secondary, the Primary Station window appears.

Step 8 Whether you clicked Primary or Secondary in Step 7, enter the name of the primary CWM and then click Next. The Preserve SCM Gateway window appears.

(If you entered a primary machine that is unreachable, an error message appears.)

Step 9 If you want to set up SCM as part of a gateway, select Yes; otherwise, click No, and then click Next.

•If the CWM has more than one available raw partition, the Log Raw Partition window appears. Go to Step 10.

•If the CWM has only one available partition, go to Step 12.

Step 10 Click Same Raw Partition if the Informix log will have its own separate raw partition; otherwise, click Meta Devices, and then click Next.

•If you clicked Yes to have the Informix log as its own separate raw partition, the Select the Raw Partition window appears. Go to Step 11.

•Otherwise, the Meta Devices window appears. Go to Step 12.

Step 11 Click the desired raw partition for the Informix log and then click Next. The Meta Devices window appears.

Step 12 Accept the default No (stating that you do not use disk striping or meta devices for database partitions) and then click Next. (A meta device is a virtual device created by concatenating or striping disk partitions. This is done usually to improve flexibility or performance.) The Multiple Disk Configuration window appears.

Step 13 If you specified one partition for the physical log and the CWM has only two available raw partitions, click the default No and then click Next.

For the next two steps in the upgrade, refer to the procedure for performing new installations. Any information pertaining specifically to upgrades is delineated in these sections:

•Configuring the Informix Partitions

•Completing the Installation or Upgrade

Upgrading in Console Mode

This section describes how to perform an upgrade in Console Mode. You can follow the same procedure as that used for the initial installation. Any information pertaining specifically to upgrading is designated. See Installing or Upgrading in Console Mode.

Creating a CWM Auto-Restart Shell Script

This section describes how to create and configure a shell script that automatically starts the CWM core after a reboot. To create this shell script, you need to use a text editor to create a new file containing the commands that you want the script to execute.

Use this procedure to create a script that uses the vi editor and shell commands to automatically restart the CWM core after the workstation has been rebooted.

Note Several minor errors that existed in the past in the CWM Auto restart shell script have been corrected in the script that follows.

Step 1 Log in to the CWM as user root:
$ su 
Step 2 Change to directory /etc/rc3.d:
# cd /etc/rc3.d 
Step 3 Create a shell script of the form: Snn <filename>, where nn is the relative sequence number for starting the job under /etc/rc3.d by entering this command:
# vi /etc/rc3.d/S99init_sv 
Since this script does not currently exist, the vi editor will open on a blank line, 
waiting for you to enter the script commands.
Step 4 Create the shell script by entering these lines:
******************************************************************
#!/bin/sh
# Check if Informix configuration is going on 
  while [ ! -z "`ps -ef | grep S98init_db | grep -v grep`" ]
  do
    echo "Informix initialization in progress...." >> 
/usr/users/svplus/log/.start_stopCWM.log
    sleep 5
  done
# Start Orbix E2A ... as svplus 
  echo "Starting Orbix E2A ..." >> /usr/users/svplus/log/.start_stopCWM.log
  su - svplus -c /usr/users/svplus/scripts/startorbix2000 >> 
/usr/users/svplus/log/.start_stopCWM.log
  sleep 5
# Running Guard process ... as svplus
  echo "Running Guard process" >> /usr/users/svplus/log/.start_stopCWM.log 
  su - svplus -c /usr/users/svplus/scripts/Install/RunGuard &
# Start CWM core process ... as svplus 
  su - svplus -c /usr/users/svplus/scripts/start_SV+ &
******************************************************************
Note To save your changes while using the vi editor, press Esc, colon (:), then wq!.

Step 5 Provide execute permissions for /etc/rc3.d/S99init_sv by executing this command:
# chmod 755 S99init_sv 
To auto restart Informix after reboot, a shell script has been created automatically during the initial CWM installation. This script is called /etc/rc3.d/S98init_db. You need to make sure that the filename of your newly created autorestart shell script has a script number (the second and third characters in the filename) greater than 98. Also, your newly created autorestart shell script cannot have the same script number as any other script files in /etc/rc3.d.

For more information on configuring this feature, refer to the /etc/init.d/README file.

Installing RtmProxy

The next step is to install RtmProxy. For the procedures, see Installing RtmProxy.

Upgrading to CWM 15.3.00 from Solaris 8 to Solaris 9 with Multiple CWM Gateways

When upgrading from a network that has multiple CWM gateways, you must follow a certain step sequence to ensure the following:

•Network management functions are not interrupted.

•One and only one primary CWM exists in a CWM domain.

•The integrity of the network configuration and user data files is maintained.

Initial Conditions before Upgrade

This section describes an example network with three gateways to be upgraded that is running on Solaris 8 workstations. The upgrade procedure also applies to networks with different numbers of CWM gateways.

The network has one primary and two secondary CWM 15.0 or 15.1.50 gateways (named CWMA, CWMB, and CWMC) in the same domain. All of these gateways are running and all are synchronized with the network configuration and user data:

•In CWM, the first station to be started automatically is assigned the role of the primary station.

•The second station to be started becomes a secondary workstation with priority 1.

•Subsequent stations become secondary stations with priorities of 2, 3, and so on.

To ensure such a primary/secondary arrangement, the DomainGatewayList field in the CWMGateway.conf file for all three CWMs must list all CWM gateways.

In the Figure 1 example, the CWMA workstation is primary, and workstations CWMB and CWMC are secondary with priorities of 1 and 2, respectively. The CWMGateway.conf field for all three gateways contains the following entry:
DomainGatewayList CWMA CWMB CWMC
Figure 1 Example Initial State of CWM Gateways

Solaris 8 to 9 Upgrade Procedure

The following steps upgrade the workstations.

Step 1 Stop the CWM core process for CWMA. This action causes CWMB to assume the role of the primary gateway and CWMC to assume the role of the secondary gateway with priority 1.

Step 2 On CWMA perform the following steps:

a. Save the database.

b. Install Solaris 9.

c. Install HP OpenView.

d. Upgrade to CWM 15.3.00 (again, with Solaris 9).

Step 3 Start the CWM core process for CWMA. CWMA starts as a primary gateway but in a different gateway domain.

Figure 2 shows the new states of the three CWM workstations.

Figure 2 State of CWM Gateways after Step 3

Step 4 Stop the CWM core process for CWMB. This action causes CWMC to assume the role of the primary gateway.

Step 5 On CWMB, perform the following steps:

a. Save the database.

b. Install Solaris 9.

c. Install HP OpenView.

d. Upgrade to CWM 15.3.00 (with Solaris 9).

When requested, use the Primary/Secondary select window to select CWMB as the secondary gateway and CWMA as primary.

Step 6 Start the CWM core process for CWMB. CWMB starts as secondary priority 1 in the same domain as CWMA.

Figure 3 shows the new states of the three CWM workstations.

Figure 3 State of CWM Gateways after Step 6

Step 7 Stop the CWM core process for CWMC.

Step 8 On CWMC, perform the following steps.

a. Save the database.

b. Install Solaris 9.

c. Install HP OpenView.

d. Upgrade to CWM 15.3.00 (with Solaris 9).

When requested, use the Primary/Secondary select window to select CWMC as the secondary gateway and CWMA as primary.

Step 9 Start the CWM core process for CWMC. CWMC starts as secondary, priority 2 in the same domain as CWMA and CWMB.

Figure 4 shows the new states of the three CWM workstations.

Figure 4 State of CWM Gateways after Step 9

Step 10 At this point, all three gateways are operating in the initial state except that they have all been upgraded to the Solaris 9 platform.

You must now update the DomainGatewayList in the CWMGateway.conf file for all three gateways to include CWMA, CWMB, and CWMC. In this way the gateways will be part of the same gateway domain when their cores are restarted.

Upgrading to CWM 15.3.00 Solaris 9 from 15.1.50 Solaris 9 with Multiple CWM Gateways

To perform these upgrades, use the previous procedure: Upgrading to CWM 15.3.00 from Solaris 8 to Solaris 9 with Multiple CWM Gateways.

You do not need to perform the following tasks in each step that lists them:

a. Save the database.

b. Install Solaris 9.

c. Install HP OpenView.

You only need to upgrade the CWM software.

Post-Installation Tasks

After the CWM installation is complete, you must complete several procedures. For all of the post-installation procedures, see Post-Installation Tasks.

	Cisco WAN Manager Installation Guide, 15.3.00
	4 - Upgrading the CWM from an Earlier Version
Cisco WAN Manager Installation Guide, 15.3.00 Index Preface 1 - Introduction 2 - Preparing to Install 3 - Installing the CWM Software 4 - Upgrading the CWM from an Earlier Version 5 - Installing CWM SNMP Service Agent Software 6 - Installing CWM Client 7 - Installing the SCMSA Software 8 - Upgrading the SCMSA 9 - Uninstalling CWM Components 10 - Router and Node Configuration A - Configuring the SCM B - Configuring IP Reachability	Download this chapter 4 - Upgrading the CWM from an Earlier Version Download the complete book PDF of Entire Guide (PDF - 2 MB) Table Of Contents Upgrading the CWM from an Earlier Version Upgrading from Solaris 8 to Solaris 9 Uninstalling the WANDEST Server Saving Databases Installing Solaris 9 and OpenView Upgrading the CWM Software Before You Start Selecting the Upgrade Mode Upgrading with the InstallShield GUI Upgrading in Console Mode Creating a CWM Auto-Restart Shell Script Installing RtmProxy Upgrading to CWM 15.3.00 from Solaris 8 to Solaris 9 with Multiple CWM Gateways Initial Conditions before Upgrade Solaris 8 to 9 Upgrade Procedure Upgrading to CWM 15.3.00 Solaris 9 from 15.1.50 Solaris 9 with Multiple CWM Gateways Post-Installation Tasks Upgrading the CWM from an Earlier Version This chapter describes how to upgrade to CWM 15.3.00 from an earlier CWM version. You can upgrade to CWM 15.3.00 from any of the following releases: •CWM 15.1.50 (latest patch) on Solaris 9 to CWM 15.3.00 on Solaris 9 •CWM 15.1.50 (latest patch) on Solaris 8 to CWM 15.3.00 on Solaris 9 •CWM 15.0 (latest patch) on Solaris 8 to CWM 15.3.00 on Solaris 9 To upgrade from an earlier CWM release, you must first upgrade to one of the releases listed above. To do so, see the installation guide and the release note for the appropriate CWM version (CWM 15.1.0 or CWM 15.1.50) at this URL: http://www.cisco.com/en/US/partner/products/sw/netmgtsw/ps2340/tsd_products_support_series_home.html Upgrading from Solaris 8 to Solaris 9 Upgrading from one operating system to another requires that you install a completely new Solaris 9 and CWM application. However, the upgrade can be simplified by preserving the CWM database and configuration files throughout the upgrade process. To upgrade without disrupting the network management functions, the existing Solaris 8 CWM systems should be configured with multiple CWM gateways. The CWM gateways are then upgraded one at a time, which preserves network management throughout the upgrade process. This process is described in Upgrading to CWM 15.3.00 from Solaris 8 to Solaris 9 with Multiple CWM Gateways. Perform procedures in this order: •Uninstalling the WANDEST Server •Saving Databases •Installing Solaris 9 and OpenView Uninstalling the WANDEST Server If the WANDEST server is installed on the CWM, it must be uninstalled before the database is exported. Saving Databases The following procedures describe how to save the CWM and SSC databases. Saving CWM Databases During the installation of Solaris 9, all the CWM server disk files are erased as the disks are formatted and partitioned. The procedure below ensures that the saved database and other files are stored on a removable device such as a tape or saved temporarily on a separate system so that they can be restored to the CWM machine after Solaris is installed. To save the CWM database and other needed files, perform the following steps. Step 1 Stop the CWM core processes if not already stopped. Step 2 Run uninstall.sh from the /usr/users/wandest/ directory. host% cd /usr/users/wandest host% ./UnInstallWDServer.sh This command uninstalls the wandest server. Step 3 Log in as user svplus. Step 4 Create a directory to hold the saved Informix database. host% mkdir <save_database_directory> Caution Do not create the directory under the /usr/user directory. The directory should be on a separate NFS-mounted disk. If an NFS-mounted disk is not available, the directory can be on one of the CWM server disks, but the directory and its contents must be FTPd to another system before Solaris 9 is installed. Step 5 Change the permissions of the directory: host% chmod 777 <save_database_directory> Step 6 Change the current directory to the <save_database_directory> directory: host% cd <save_database_directory> Step 7 Verify that enough disk space is available for the Informix OnLine database: host% onstat -d Step 8 Enter the dbexport command: host% dbexport -o <save_database_directory><database_name> The default name for <database_name> is stratacom and cannot be changed. Step 9 Repeat Steps 6 and 7 to export the scmdb and statsdb databases using the same <save_database_directory> directory. Step 10 Copy the svplus.version file (found in the /usr/users/svplus/etc directory) to the same <save_database_directory> directory. Step 11 Copy any configuration files (such as network.conf) that should be saved to the same <save_database_directory> directory: •If the <save_database_directory> directory is on a separate NFS-mounted disk, no further steps are necessary. •If the <save_database_directory> directory is on the CWM machine, it must be transferred to an external location. For example, save it to a tape by using the tar cvf/dev/rmt/0 command or using the FTP facility to copy it to another machine. If the preceding steps have been performed, the Informix OnLine database is now saved to a safe location. Saving SSC Workstation Databases If the upgrade to CWM 15.3.00 also involves upgrading one or more SSC workstations in which the statsdb databases need to be saved, the upgrade of CWM and the upgrade of the SSC workstations must be coordinated. Upgrading to a SSC is the only configuration upgrade that is supported. Because SSC workstations do not support a local statsdb database, any existing statsdb databases on the standalone systems must be saved (if needed) to the CWM server as part of the upgrade process. To save statsdb databases, perform the following procedure. Caution This procedure must be performed before using the CWM 15.3.00 upgrade program. Step 1 At each SSC workstation, execute the script, statsdbunload.csh, that is located on the SCMSA CD (See Chapter 9 for details). The result is a directory called "statsdbupload" located in usr/users/svplus/tmp on the statistics collection workstation. Step 2 If the statsdbunload.csh script has been executed on multiple workstations, rename the resulting directories so that each name is unique. Use names such as statsdbupload, statsdbupload1, and statsdbupload2. Step 3 Save all the statsdbupoad(x) directories. If the upgrade at the CWM server involves an upgrade from Solaris 8 to Solaris 9, use the FTP facility to copy the directories to the same place that was used for saving (exporting) the CWM databases and files. If the upgrade does not involve a Solaris upgrade, use the FTP facility to copy the directories to usr/users/svplus/tmp on the CWM server. Step 4 The installation of Solaris 9 and the upgrade of the CWM server can now proceed. When the CWM upgrade procedure is executed, the saved directories are located and the data is incorporated into the CWM statsdb. Installing Solaris 9 and OpenView When the CWM database and other files have been saved, install the following sequence of programs. 1. Solaris 9 2. Solaris 9 patches as specified in these release notes Note Make sure that the machine is rebooted at this point. 3. HP OpenView (if needed) http://www.cisco.com/en/US/products/sw/netmgtsw/ps2340/products_installation_guide_book09186a008047b1e4.html When these programs have been installed, the CWM can be upgraded. Upgrading the CWM Software To upgrade the CWM software, first read the Before You Start section and then choose the mode that you want to use to perform the upgrade, by using the InstallShield GUI or in Console Mode: •Before You Start •Selecting the Upgrade Mode •Upgrading with the InstallShield GUI •Upgrading in Console Mode The installation procedure (InstallShield GUI or Console Mode) is divided into these three phases: •Initial Upgrade Phase Note For the next two steps in the upgrade, refer to the procedure for performing new installations. Any differences pertaining to upgrades are delineated in these sections: •See Configuring the Informix Partitions •See Completing the Installation or Upgrade This section also contains two sections on upgrading with multiple CWM gateways: •Upgrading to CWM 15.3.00 from Solaris 8 to Solaris 9 with Multiple CWM Gateways •Upgrading to CWM 15.3.00 Solaris 9 from 15.1.50 Solaris 9 with Multiple CWM Gateways Before You Start Ensure that Solaris 9 and the requisite Solaris 9 patches have been installed. Make sure that you reboot the system after Solaris 9 and the patches are installed. If the CWM upgrade involves upgrading from a Solaris 8 to Solaris 9 platform, ensure that the exported databases and files are accessible to the system: •If the exported databases are saved to a tape or NFS mounted directory, mount the exported database on the CWM (either tape or NFS mounted directory). •Alternatively, if the exported databases are using the FTP facility to copy to another system, create a directory on the CWM and use FTP to copy the databases and other files back to that directory. Whichever method is used, note the path to the location where the databases now reside. You will need this path when you upgrade to the Solaris 9 version of CWM. Selecting the Upgrade Mode To begin the upgrade and select the upgrade mode, follow the steps below. Step 1 Insert the CWM 15.3.00 CD-ROM No. 1 into the CD-ROM drive. Step 2 Enter the following commands: # cd /cdrom/cdrom0 # ls Step 3 Check for the InstallCWM.sh file and enter the following command to begin the installation: # ./InstallCWM.sh After you enter the ./InstallCWM.sh command, this message is displayed. Console Mode Option is recommended when you cannot connect to X Server from current terminal (See if you can open and xterm to check ! ) Do you want to Launch Installer in Console Mode ? (Yes / No ): [No] :y The Console Mode Install is a command line script procedure. It is an alternative to the GUI and is intended for users who do not have access to an X window device. By using Console Mode Install, you can install CWM with an alphanumeric terminal or a PC in terminal emulator mode. Step 4 Designate if you want to use the InstallShield GUI or the Console Mode Install to continue the upgrade procedure: •To use the Console Mode Install, click Y (for yes) and then click Enter. See Upgrading in Console Mode. •To use the InstallShield GUI, click N (for no) and then click Enter. See Upgrading with the InstallShield GUI. Upgrading with the InstallShield GUI After you choose InstallShield GUI method for performing the upgrade, the installation classes start loading. This process takes several minutes. Initial Upgrade Phase To start the initial upgrade phase, the CWM Installation Welcome window in the GUI appears. Step 1 Click Next. The license agreement window appears. Step 2 Click I accept and then click Next. The upgrade window appears. Step 3 Because you are performing an upgrade, click Yes and then click Next. The CWM version window appears. Step 4 Click the CWM version that you are upgrading from: 15.0 or 15.1.50, and then click Next. The Solaris version window appears. Step 5 Click the Solaris version from which you are upgrading and then click Next: •Solaris 8—If you are upgrading from a Solaris 8 to a Solaris 9 platform. If you selected Solaris 8, the Database Path Window appears for you to enter the path for importing the databases. Go to Step 6. •Solaris 9—If the previous version of CWM is already running on a Solaris 9 platform, the Primary/Secondary window appears. Go to Step 7. Step 6 Enter the path for importing the database and then click Next. The Primary/Secondary window appears. Step 7 Click Primary or Secondary for the CWM being upgraded and click Next. Whether you selected Primary or Secondary, the Primary Station window appears. Step 8 Whether you clicked Primary or Secondary in Step 7, enter the name of the primary CWM and then click Next. The Preserve SCM Gateway window appears. (If you entered a primary machine that is unreachable, an error message appears.) Step 9 If you want to set up SCM as part of a gateway, select Yes; otherwise, click No, and then click Next. •If the CWM has more than one available raw partition, the Log Raw Partition window appears. Go to Step 10. •If the CWM has only one available partition, go to Step 12. Step 10 Click Same Raw Partition if the Informix log will have its own separate raw partition; otherwise, click Meta Devices, and then click Next. •If you clicked Yes to have the Informix log as its own separate raw partition, the Select the Raw Partition window appears. Go to Step 11. •Otherwise, the Meta Devices window appears. Go to Step 12. Step 11 Click the desired raw partition for the Informix log and then click Next. The Meta Devices window appears. Step 12 Accept the default No (stating that you do not use disk striping or meta devices for database partitions) and then click Next. (A meta device is a virtual device created by concatenating or striping disk partitions. This is done usually to improve flexibility or performance.) The Multiple Disk Configuration window appears. Step 13 If you specified one partition for the physical log and the CWM has only two available raw partitions, click the default No and then click Next. For the next two steps in the upgrade, refer to the procedure for performing new installations. Any information pertaining specifically to upgrades is delineated in these sections: •Configuring the Informix Partitions •Completing the Installation or Upgrade Upgrading in Console Mode This section describes how to perform an upgrade in Console Mode. You can follow the same procedure as that used for the initial installation. Any information pertaining specifically to upgrading is designated. See Installing or Upgrading in Console Mode. Creating a CWM Auto-Restart Shell Script This section describes how to create and configure a shell script that automatically starts the CWM core after a reboot. To create this shell script, you need to use a text editor to create a new file containing the commands that you want the script to execute. Use this procedure to create a script that uses the vi editor and shell commands to automatically restart the CWM core after the workstation has been rebooted. Note Several minor errors that existed in the past in the CWM Auto restart shell script have been corrected in the script that follows. Step 1 Log in to the CWM as user root: $ su Step 2 Change to directory /etc/rc3.d: # cd /etc/rc3.d Step 3 Create a shell script of the form: Snn <filename>, where nn is the relative sequence number for starting the job under /etc/rc3.d by entering this command: # vi /etc/rc3.d/S99init_sv Since this script does not currently exist, the vi editor will open on a blank line, waiting for you to enter the script commands. Step 4 Create the shell script by entering these lines: **************************************************************** #!/bin/sh # Check if Informix configuration is going on while [ ! -z "`ps -ef \| grep S98init_db \| grep -v grep`" ] do echo "Informix initialization in progress...." >> /usr/users/svplus/log/.start_stopCWM.log sleep 5 done # Start Orbix E2A ... as svplus echo "Starting Orbix E2A ..." >> /usr/users/svplus/log/.start_stopCWM.log su - svplus -c /usr/users/svplus/scripts/startorbix2000 >> /usr/users/svplus/log/.start_stopCWM.log sleep 5 # Running Guard process ... as svplus echo "Running Guard process" >> /usr/users/svplus/log/.start_stopCWM.log su - svplus -c /usr/users/svplus/scripts/Install/RunGuard & # Start CWM core process ... as svplus su - svplus -c /usr/users/svplus/scripts/start_SV+ & ************************************************************** Note To save your changes while using the vi editor, press Esc, colon (:), then wq!. Step 5 Provide execute permissions for /etc/rc3.d/S99init_sv by executing this command: # chmod 755 S99init_sv To auto restart Informix after reboot, a shell script has been created automatically during the initial CWM installation. This script is called /etc/rc3.d/S98init_db. You need to make sure that the filename of your newly created autorestart shell script has a script number (the second and third characters in the filename) greater than 98. Also, your newly created autorestart shell script cannot have the same script number as any other script files in /etc/rc3.d. For more information on configuring this feature, refer to the /etc/init.d/README file. Installing RtmProxy The next step is to install RtmProxy. For the procedures, see Installing RtmProxy. Upgrading to CWM 15.3.00 from Solaris 8 to Solaris 9 with Multiple CWM Gateways When upgrading from a network that has multiple CWM gateways, you must follow a certain step sequence to ensure the following: •Network management functions are not interrupted. •One and only one primary CWM exists in a CWM domain. •The integrity of the network configuration and user data files is maintained. Initial Conditions before Upgrade This section describes an example network with three gateways to be upgraded that is running on Solaris 8 workstations. The upgrade procedure also applies to networks with different numbers of CWM gateways. The network has one primary and two secondary CWM 15.0 or 15.1.50 gateways (named CWMA, CWMB, and CWMC) in the same domain. All of these gateways are running and all are synchronized with the network configuration and user data: •In CWM, the first station to be started automatically is assigned the role of the primary station. •The second station to be started becomes a secondary workstation with priority 1. •Subsequent stations become secondary stations with priorities of 2, 3, and so on. To ensure such a primary/secondary arrangement, the DomainGatewayList field in the CWMGateway.conf file for all three CWMs must list all CWM gateways. In the Figure 1 example, the CWMA workstation is primary, and workstations CWMB and CWMC are secondary with priorities of 1 and 2, respectively. The CWMGateway.conf field for all three gateways contains the following entry: DomainGatewayList CWMA CWMB CWMC Figure 1 Example Initial State of CWM Gateways Solaris 8 to 9 Upgrade Procedure The following steps upgrade the workstations. Step 1 Stop the CWM core process for CWMA. This action causes CWMB to assume the role of the primary gateway and CWMC to assume the role of the secondary gateway with priority 1. Step 2 On CWMA perform the following steps: a. Save the database. b. Install Solaris 9. c. Install HP OpenView. d. Upgrade to CWM 15.3.00 (again, with Solaris 9). Step 3 Start the CWM core process for CWMA. CWMA starts as a primary gateway but in a different gateway domain. Figure 2 shows the new states of the three CWM workstations. Figure 2 State of CWM Gateways after Step 3 Step 4 Stop the CWM core process for CWMB. This action causes CWMC to assume the role of the primary gateway. Step 5 On CWMB, perform the following steps: a. Save the database. b. Install Solaris 9. c. Install HP OpenView. d. Upgrade to CWM 15.3.00 (with Solaris 9). When requested, use the Primary/Secondary select window to select CWMB as the secondary gateway and CWMA as primary. Step 6 Start the CWM core process for CWMB. CWMB starts as secondary priority 1 in the same domain as CWMA. Figure 3 shows the new states of the three CWM workstations. Figure 3 State of CWM Gateways after Step 6 Step 7 Stop the CWM core process for CWMC. Step 8 On CWMC, perform the following steps. a. Save the database. b. Install Solaris 9. c. Install HP OpenView. d. Upgrade to CWM 15.3.00 (with Solaris 9). When requested, use the Primary/Secondary select window to select CWMC as the secondary gateway and CWMA as primary. Step 9 Start the CWM core process for CWMC. CWMC starts as secondary, priority 2 in the same domain as CWMA and CWMB. Figure 4 shows the new states of the three CWM workstations. Figure 4 State of CWM Gateways after Step 9 Step 10** At this point, all three gateways are operating in the initial state except that they have all been upgraded to the Solaris 9 platform. You must now update the DomainGatewayList in the CWMGateway.conf file for all three gateways to include CWMA, CWMB, and CWMC. In this way the gateways will be part of the same gateway domain when their cores are restarted. Upgrading to CWM 15.3.00 Solaris 9 from 15.1.50 Solaris 9 with Multiple CWM Gateways To perform these upgrades, use the previous procedure: Upgrading to CWM 15.3.00 from Solaris 8 to Solaris 9 with Multiple CWM Gateways. You do not need to perform the following tasks in each step that lists them: a. Save the database. b. Install Solaris 9. c. Install HP OpenView. You only need to upgrade the CWM software. Post-Installation Tasks After the CWM installation is complete, you must complete several procedures. For all of the post-installation procedures, see Post-Installation Tasks.
	© 1992-2008 Cisco Systems, Inc. All rights reserved. Terms & Conditions \| Privacy Statement \| Cookie Policy \| Trademarks of Cisco Systems, Inc.