Feedback
Table Of Contents
Upgrading CWM from Solaris 7 to Solaris 8
Installing Solaris 8, OpenView, and Wingz
Upgrading CWM 11 Software from Solaris 7 to Solaris 8
Upgrading CWM 11 Software from Solaris 7 to Solaris 8 with Multiple CWM Gateways
Initial Conditions before Upgrade
First Time Login as User svplus
Checking the CWM Server File System
svplus/config/network.conf file
CWM Gateway Configuration File
Upgrading CWM from Solaris 7 to Solaris 8
This chapter provides step-by-step procedures to upgrade your CWM server workstation from a
Solaris 7 platform to a Solaris 8 platform.There is no automatic upgrade procedure such as that used to upgrade from CWM 10.x to CWM 11 on the Solaris 7 platform. Moving from one operating system to another requires that a completely new Solaris 8 CWM installation must be performed. However, the upgrade can be simplified by preserving the CWM database and configuration files throughout the upgrade process. In this way, the user is not faced with reconstructing these files on the new Solaris 8 platform.
To upgrade without a disruption of the network management functions, the existing Solaris 7 CWM system should be configured with multiple CWM gateways. The CWM gateways are then upgraded one at a time thus preserving network management throughout the upgrade process. This process is described in detail later in this chapter.
The upgrade process for a CWM server consists of the following steps.
Step 1
Save the existing CWM database, configuration files, and any other files that need to be preserved to an external safe place (for example, a separate NFS mounted directory, a tape, or FTP'd to another machine). This step must be performed first.
Step 2
Step 3
Step 4
Step 5
Step 6
Step 7
Saving the CWM Database
This section describes how to save a copy of the current database using the Informix OnLine dbexport command. Refer to Informix OnLine documentation for information about the dbexport command.
During the installation of Solaris 8, all the CWM server's 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
Step 2
Step 3
host% mkdir <save_database_directory>
Caution
Step 4
host% chmod 777 <save_database_directory>Step 5
host% cd <save_database_directory>Step 6
host% onstat -dStep 7
host% dbexport -o <save_database_directory> <database_name>Use the name assigned to the database during the CWM installation as the <database_name> name. The default name was `stratacom'.
Step 8
Step 9
Step 10
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, saved to a tape using the tar cvf/dev/rmt/0 command or FTPd to another machine.
The Informix OnLine database is now saved to a safe location.
Installing Solaris 8, OpenView, and Wingz
When the CWM database and other files have been saved, perform the procedures described in
Chapter 2 to install the following sequence of programs.Solaris 8
Solaris 8 patches as specified in the most current release notes.
Note
HP OpenView
Informix Wingz
When these programs have been installed, the databases can be restored.
Restoring the CWM Database
When Solaris 8 and the other programs have been installed, restore the databases and other files using the following procedure.
Step 1
Step 2
Alternatively, if the exported databases have been FTPd to another system, create a directory on the CWM workstation and FTP the databases and other files back to that directory.
Step 3
Upgrading CWM 11 Software from Solaris 7 to Solaris 8
To upgrade to the Solaris 8 version of CWM Release 11 from CWM releases 10.4, 10.5 or 11.0 (Solaris 7 version) complete the following steps:
Step 1
Step 2
Step 3
# cd /cdrom/cdrom0# lsStep 4
# ./InstallCWM.shThe CWM Installation Welcome window is displayed, as shown in Figure 4-1.
Figure 4-1 CWM Installation Welcome Window
Step 5
The README Information window is displayed (see Figure 4-2).
Figure 4-2 CWM Installation README Information Window
Step 6
The Information About the Upgrading Procedure window is displayed, as shown in Figure 4-3.
Figure 4-3 Information About the Upgrading Procedure Window
Step 7
The Upgrade Path window is displayed.
Figure 4-4 Upgrade Path
Step 8
The CWM role in the CWM domain for CWM CWM Communication window is displayed, as shown in Figure 4-5.
Figure 4-5 CWM role in the CWM domain for CWM CWM Communication Window
Step 9
If Secondary is selected, the window is refreshed and the user is requested to enter the name of the Primary station as shown in Figure 4-6. This window is displayed only if upgrading from 10.4, otherwise it is skipped.
Figure 4-6 CWM role in the CWM domain for CWM CWM Communication Window 2
Step 10
Step 11
The Meta Devices window is displayed, as shown in Figure 4-7.
Figure 4-7 Meta Devices Window
Step 12
Note
The Multiple Disk Configuration for Informix window is displayed, as shown in Figure 4-8.
Figure 4-8 Multiple Disk Configuration for Informix Window
Step 13
The Select the Raw Partition for CWM Database window is displayed, as shown in Figure 4-9.
Figure 4-9 Select the Raw Partition for CWM Database
Step 14
Note
A small window is displayed warning the user that the selected partition must be at least 1 GBytes in size (see Figure 4-10).
Figure 4-10 Minimum Space Warning
Step 15
When Next has been clicked, the CWM FTP Information window is displayed as shown in Figure 4-11.
Figure 4-11 CWM FTP Information Window
Step 16
After entering the FTP user name and password, click Install.
The Choose Destination Directory window is displayed, as shown in Figure 4-12.
Note
Figure 4-12 Choose Destination Directory Window
Step 17
In this release of CWM, the destination directory cannot be changed.
The Install Orbix window is displayed, as shown in Figure 4-13.Figure 4-13 Install Orbix Window
Orbix is the software component that provides the communication capability between CWM gateways.
Step 18
The Enter Domain Name window is displayed as shown in Figure 4-14.
Figure 4-14 Enter the Domain Name Window
Step 19
This information allows the CWM client workstations access to the database. Also ensure that the workstation and the domain is reachable. You can enter the ping command to test this.
The only reason to leave the Domain Name field empty (or blank) would be for a standalone CWM server that would never have client workstations.
Step 20
The Install CiscoView window is displayed, as shown in Figure 4-15.
Figure 4-15 Install CiscoView Window
Note
Patches are available to Sun Microsystems customers over the World Wide Web at this URL.
www.sunsolve.sun.com.
You can display which patches are already installed in the CWM workstation by entering the Solaris showrev -p command.Either select Yes to install CiscoView or No if CiscoView is not to be installed, and then click Next.
If Yes is selected, the CiscoView home window is displayed as shown in Figure 3-14.
Caution
If CiscoView is installed (from a previous installation) either select No and Continue or go back, uninstall CiscoView, restart the install process, and select Yes at the CiscoView window.
Figure 4-16 Enter CiscoView Home Window
Step 21
The software installation process begins. This process takes from 30 to 60 minutes depending on the speed and resources of the CWM workstation. The installation window shows a dynamic indicator bar, which moves across the window, indicating the progress of the installation process, as shown in Figure 4-17.
A small log window is also displayed showing entries to the install log as they are entered.
Figure 4-17 Installation Progress Indicator (extracting files)
If the CWM system was installed previously, a message appears telling the user that files already exist and requesting permission to overwrite the files with new files. This message is shown in Figure 4-18. Click Yes to All.
Figure 4-18 Copy Files Message
After extracting the necessary CWM program files, the window refreshes, and the installation process begins creating and configuring the database. The installation window shows a dynamic indicator bar, which moves across the window, indicating the progress of the database creation process, as shown in Figure 4-19.
Figure 4-19 Installation Progress Indicator (database creation)
An Install Log window is also displayed (see Figure 4-20)
Figure 4-20 Install Log
A dialog box displays informing you that the installation is complete, as shown in Figure 4-21.
Figure 4-21 Installation Complete Window
Step 22
Doing so ends the software installation process is completed. The Install Shield window closes.
Step 23
The first time (and only the first) that CWM is installed, the system will display a message stating that the kernel has been changed. Click OK to reboot the system
The reboot sequence aligns the cylinders of your hard disks, gracefully shuts down, and restarts the Solaris operating system.
Note
Upgrading CWM 11 Software from Solaris 7 to Solaris 8 with Multiple CWM Gateways
When upgrading from a network in which there are multiple CWM gateways, a special sequence of steps needs to be followed. This procedure ensures that, at all times, the network management functions are not interrupted, there is one and only one master CWM in a CWM domain, and that the integrity of the network configuration and user data files is maintained.
Initial Conditions before Upgrade
Consider an example CWM network system running on Solaris 7 workstations. The network has three Release 10.x or 11 CWM gateways (named A, B, and C), all in the same domain. The gateways consist of one master and two secondaries. All gateways are up and running, all are synced with the network configuration and user data.
Note
In CWM the first station to be started is automatically assigned the role of primary station. The second station to be started becomes a secondary station 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 CWM stations must list all CWM gateways.
In the example shown in Figure 4-22, CWMA station is primary and stations 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 CWMCFigure 4-22 Initial State of CWM Gateways
CWMA-Sol 7
Primary
DomainGatewayList = A,B,CCWMB-Sol 7
Secondary Pri 1
DomainGatewayList = A,B,CCWMC-Sol 7
Secondary Pri 2
DomainGatewayList = A,B,C
Upgrade Procedure
The following steps upgrade the stations, one by one, to Release 11.
Step 1
This action causes CWMB to assume the role of primary and CWMC the role of secondary priority 1.
Step 2
a.
b.
c.
d.
e.
f.
Step 3
CWMA starts as primary but in a different gateway domain.
The new states of the three CWM stations are shown in Figure 4-23.
Figure 4-23 State of CWM Gateways after Step 3
CWMA-Sol 8
Primary
DomainGatewayList = ACWMB- Sol 7
Primary
DomainGatewayList = A,B,CCWMC-Sol 7
Secondary Pri 1
DomainGatewayList = A,B,C
Step 4
This action causes CWMC to assume the role of primary.
Step 5
a.
b.
c.
d.
e.
f.
When requested, use the Primary/Secondary select window to select CWMB as secondary and CWMA as primary.
Step 6
CWMB starts as secondary priority 1 in the same domain as CWMA.
The new states of the three CWM stations are shown in Figure 4-24.
Figure 4-24 State of CWM Gateways after Step 6
CWMA-Sol 8
Primary
DomainGatewayList = ACWMB-Sol 8
Secondary Pri 1
DomainGatewayList = A,BCWMC-Sol 7
Primary
DomainGatewayList = A,B,C
Step 7
Step 8
a.
b.
c.
d.
e.
f.
When requested, use the Primary/Secondary select window to select CWMC as secondary and CWMA as primary.
Step 9
CWMC starts as secondary priority 2 in the same domain as CWMA and CWMB.
The new states of the three CWM stations are shown in Figure 4-25.
Figure 4-25 State of CWM Gateways after Step 9
CWMA 11-Sol 8
Primary
DomainGatewayList = ACWMB 11-Sol 8
Secondary Pri 1
DomainGatewayList = A,BCWMC 11-Sol 8
Secondary Pri 2
DomainGatewayList = A,C
Step 10
The user 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 next restarted.
Post Installation Tasks
After the CWM installation is complete the following configuration tasks should be completed.
If you haven't already done so, eject the CWM CD-ROM by entering the eject command in the terminal window.
First Time Login as User svplus
After completing the CWM Release 11 software installation, perform the following steps when you log in to CWM as user svplus.
Step 1
Step 2
Step 3
Step 4
Move this terminal window to the upper right corner of the screen.
Step 5
Lower the height to display four lines and move this window so that it rests above the CDE menu bar. This window provides a display of workstation system messages.
Step 6
The Style Manager window is displayed.
Step 7
If you prefer to use the screen saver, highlight choice(s) and start the screen saver at 29 minutes. Start the screen lock at 30 minutes, click OK.
Step 8
Do the same to all four screens. They are labeled One, Two, Three and Four in the CDE icon bar. In Four click OK and return to screen One. This action helps to conserve workstation resources.
Step 9
The next login session will come up using this same screen configuration. Click OK and close the Style Manager.
Step 10
% cd /usr/users/svplus/config% vi network.confStep 11
Note
Checking the CWM Server File System
At the CWM workstation, log in as user root, and examine the following files.
•
•
•
•
•
•
•
•
•
Note
/etc/hosts
Examine the /etc/hosts file and check that the file contains a nodename and IP address for all nodes. The IP address should be one that CWM can use for network discovery (see following paragraphs). Enter the correct nodenames and addresses for any missing nodes.
To view the /etc/hosts file, enter the following command:
host% more /etc/hostsUse vi Editor to enter items into the file.
IPX and MGX (Rel 1.x, 2.0 and up to 2.1.60) Nodes
For each node:
Enter the ATM0 or NWIP address and the node name.
Enter the LnPci0 or LANIP address and the nodename followed by an identifier such as -l, or -lan).
Example:
172.70.207.9 mgx1 192.0.0.9 mgx1-lMGX (Rel 2.1.70 and above) Nodes
For each node:
Enter the IP address used in option 8 of the cnfndparms command. This address can be displayed at the node by entering the dspndparms command.
Example:
172.70.209.9 mgx4BPX Nodes
For each node:
Enter the node's IP address and the node name.
Example:
192.0.0.8 bpx1Example Host File
As an example, a hosts file might look like the following example:
# MGX Rel 1, 2.0, up to 2.1.60 nodes172.70.207.9 mgx1 192.0.0.9 mgx1-l172.70.207.6 mgx2 192.0.0.6 mgx2-l172.70.207.4 mgx3 192.0.0.4 mgx3-l##MGX Rel 2.1.70 and up nodes172.70.209.9 mgx4172.70.209.8 mgx5172.70.209.7 mgx6172.70.209.6 mgx7##BPX nodes192.0.0.8 bpx1192.0.0.9 bpx2192.0.0.10 bpx3/etc/netmasks
Examine the /etc/netmasks file for all subnet and netmask entries. To view the /etc/netmasks file, enter the following command:
host% more /etc/netmasks/etc/rc2.d/S72inetsvc
Examine the /etc/rc2.d/S72inetsvc file to ensure that the IP relay address points to the gateway node. To view the /etc/rc2.d/S72inetsvc file, enter the following command:
host% more /etc/rc2.d/S72inetsvcUse the vi Editor to open the S72inetsvc file and find the following line:
/usr/sbin/route -n add -interface "224.0/4" "$mcastif" >/dev/null)&Add the following line directly below that line
/usr/sbin/route add net 10.10.10.0 209.165.200.225 1 (use your site's valid IP addresses)
Note
/etc/defaultrouter
Examine the /etc/defaultrouter file. To view the /etc/defaultrouter file, enter the following command:
host% more /etc/defaultrouter
Note
If the router IP address is not currently in the file, use the vi Editor to add a line containing the IP address of the default router to which the CWM workstation is attached.
Note
usr/users/svplus/.cshrc
Use the vi editor to modify .cshrc as follows:
vi usr/users/svplus/.cshrc
Change the line:
setenv PATH$ORBIXROOT/bin:$PATH
to
setenv PATH$ORBIXROOT/bin:/<Netscape Communicator Path>:$PATHAdd the following lines to the end of the file.
setenv PATH /opt/<Netscape Communicator Path>:$PATH
setenv MOZILLA_HOME /<Netscape Communicator Path>
Exit vi.The value of <Netscape Communicator Path> should be the actual path to Netscape Communicator. For example, if Netscape Communicator is located in /opt/NSCPcom, the changes would be:
Change the line:
setenv PATH$ORBIXROOT/bin:$PATH
to
setenv PATH$ORBIXROOT/bin:/opt/NSCPcom:$PATHAdd the following lines to the end of the file.
setenv PATH /opt/NSCPcom:$PATH
setenv MOZILLA_HOME /opt/NSCPcom
svplus/config/network.conf file
The network.conf file is located in the /usr/users/svplus/config directory.
The user should modify this file to specify networks parameters for each network to be discovered and managed.This file can describe multiple networks where each network can be any one of the following types.
•
•
•
For each network specified in the network.conf file, its entry consists of the following fields.
•
•
•
•
•
•
NETWORK
The NETWORK field has the following format.
NETWORK: <Network Name>
When describing a network's parameters, NETWORK must be the first parameter.
The Network name cannot have more than 10 characters and cannot contain a space.
Note
NETWORK ID
The NETWORK ID field has the following format.
NETWORK_ID: <Network ID>
Network ID is optional. If it is specified, the Network ID must be a unique numeric value in the range in [1, 32000].
Note
GATEWAYS
The GATEWAYS field has the following formats.
GATEWAYS: <Gateway Name(s)> (used for AutoRoute and PNNI).
AR-GATEWAYS: <Gateway Name> (used for AutoRoute segments in a Hybrid network type).
PNNI-GATEWAYS: <Gateway Name(s)> (used for PNNI segments in a Hybrid network type).
The user should enter the name(s) of any gateways that CWM is to use for network discovery.
The rules for gateways parameters depend upon the network type.
AutoRoute
Use the GATEWAYS: <Gateway Name> format and specify one (and only one) network node to be used as the AutoRoute gateway.
PNNI
Use the GATEWAYS: <Gateway Name> format and specify one or more network nodes to be used as PNNI gateways. If more than one gateway is specified for the network, the names should be separated by commas.
Hybrid
This field is used to specify which gateways should be used for the AutoRoute and PNNI segments of the network.
Use the PNNI-GATEWAYS: <Gateway Names> format to specify one or more network nodes to be used as PNNI gateways. If more than one gateway is specified for the PNNI segment, the names should be separated by commas.
Use the AR-GATEWAYS: <Gateway Names> format and specify one (and only one) network node to be used as an AutoRoute gateway.
Note
.DISCOVERY PROTOCOL
This field is used to specify the network type and has the following format.
DISCOVERY PROTOCOL: <Protocol Name>
The Protocol Name can be either AUTOROUTE or PNNI or HYBRID.
AUTOROUTE is used to discover Auto Route networks .
PNNI is used for ILMI or PNNI discovery of PNNI networks.
HYBRID is used to discover networks that contain both AutoRoute and PNNI segments.
IP REACHABILITY FLAG
The IP REACHABILITY FLAG field is used to specify which IP address method is to be used for managing network nodes. This field is used for AutoRoute networks and Hybrid AutoRoute segments only. It is ignored for PNNI networks or segments.The IP REACHABILITY FLAG field has the following format.
IP REACHABILITY FLAG:<Ip Flag>
IP Flag can be set to NWIP_ON or NWIP_OFF or LANIP.
NWIP_ON — All the routing nodes in the network are managed using their nw ip addresses.
NWIP_OFF — All the routing nodes in the network are managed through the Gateway. The Gateway then routes packets to the individual routing nodes on the corresponding routing trunks.
LANIP — All the nodes in the network are managed using Lan IP. The AUTOROUTE Gateway node is always managed using the LAN IP. By specifying "LANIP", all management traffic (including link0/link1, snmp and tftp) is sent to each node (routing node or feeders) using their Lan IP addresses.
If NWIP is set to ON or OFF, management messages use the managed network for delivery and are therefore considered to be in-band. A setting of LAN IP, on the other hand, uses a separate LAN (or LAN emulation) network for message delivery and is therefore considered to be out-of-band.
OPTIONAL
The OPTIONAL field is used to specify a number of options associated with the IP REACHABILITY FLAG and has the following format.
OPTIONAL: "List of Parameters for Auto Route Networks"
This field is mandatory for AutoRoute networks and AutoRoute segments in Hybrid networks. If this field is not specified, Auto Route networks and segments WILL NOT be discovered
OPTIONAL does not apply for PNNI networks and is ignored.
The OPTIONAL field has five sub-fields (options) as follows:
•
•
•
•
•
TIMEOUT
Link timeout value. The amount of time to wait before resending a message to an Cisco IGX 8400 and Cisco BPX 8600 when a response is not received. Default value is 7.
RETRANSMIT
Link retry count. The number of times CWM will retransmit a message before it declares the link down. Default value is 6.
THROTTLE
Download throttling timeout value. Default value is 0
ACKNOWLEDGE
ACK timeout value used during the download process. When an acknowledgment to a configuration message sent to an Cisco IGX 8400, or Cisco BPX 8600 is not received within this time period, the message is sent again. Default value is 30.
BLOCKSIZE
Block size used for an Cisco IGX 8400, or Cisco BPX 8600 configuration upload. Default value is 1024.
Note
Network.conf Examples
1. Discover an AutoRoute Network
NETWORK:Network1
GATEWAYS:B8650_SJ
DISCOVERY PROTOCOL:AUTOROUTE
IP REACHABILITY FLAG:NWIP_ON
OPTIONAL:"TIMEOUT = 7, RETRANSMIT = 6, THROTTLE = 0, ACKNOWLEDGE = 30, BLOCKSIZE = 1024"
2. Discover a PNNI network
NETWORK:Network2
GATEWAYS:M8850_LA
DISCOVERY PROTOCOL:PNNI
Note
3. Discover a HYBRID Network
#NETWORK:Network3
#PNNI-GATEWAYS:M8850_LA, M8850_CH
#AR-GATEWAYS:B8650_LA
#DISCOVERY PROTOCOL:HYBRID
#IP REACHABILITY FLAG:NWIP_ON
#OPTIONAL:"TIMEOUT = 7, RETRANSMIT = 6, THROTTLE = 0, ACKNOWLEDGE = 30, BLOCKSIZE = 1024"
CWM Gateway Configuration File
If the upgraded CWM workstation is part of a multiple CWM gateway configuration, check the CWMGateway.conf file and ensure that the DomainGatewayList contains all the stations in the Gateway domain.
For example:
host% cd usr/users/svplus/confighost% more CWMGateway.confCheck the DomainGatewayList portion of this file.
## Default: DomainGatewayList ## Usage: DomainGateWayList tmonda dilbag sgharat DomainGatewayList CWM1 CWM2 CWM3In this example, CWM1, CWM2, and CWM3 are the names of the CWM gateways.
/system
Change directory to /system and enter the ls command. Check to see that all required HPOV PSOV_XXXXX patches have been installed.
# cd /system# ls/etc/system
Check to see that the CWM installation process added the semaphores required for Solaris and HP OpenView operability
(set semsys:seminfo_semmsl=30).forceload: sys/shmsysforceload: sys/semsysset semsys:seminfo_semaem=16384set semsys:seminfo_semmap=66set semsys:seminfo_semmni=4096set semsys:seminfo_semmns=4096set semsys:seminfo_semmnu=4096set semsys:seminfo_semume=64set semsys:seminfo_semvmx=32767set semsys:seminfo_semmsl=30set shmsys:shminfo_shmmax=268435456set shmsys:shminfo_shmmin=100set shmsys:shminfo_shmmni=100set shmsys:shminfo_shmseg=100Reboot the Workstation
After completing the configuration, reboot the workstation.
# sync ;sync ;reboot
