Home | Skip to Content | Skip to Search | Skip to Navigation | Skip to Footer |
Worldwide [change] |Register |About Cisco
Guest

Hierarchical Navigation

Support

Upgrading CWM Software

Downloads

Table Of Contents

Upgrading CWM Software

Upgrading to the Latest Release of CWM 11 Software from an Earlier 10 Release

Upgrading to the CWM 11 Software from Release 10.4 or 10.5.10 with Multiple CWM Gateways

Initial Conditions before Upgrade

Upgrade Procedure

Post Installation Tasks

First Time Login as User svplus

Checking the CWM Server File System

/etc/hosts

/etc/netmasks

/etc/rc2.d/S72inetsvc

/etc/defaultrouter

usr/users/svplus/.cshrc

svplus/config/network.conf file

Network.conf Examples

CWM Gateway Configuration File

/system

/etc/system

Reboot the Workstation


Upgrading CWM Software

This chapter provides step-by-step procedures to upgrade your CWM server workstation software. The software upgrade process of CWM Release 11 uses InstallShield to simplify the process.

This chapter describes the following two upgrade scenarios:

•Upgrading to the latest release of CWM Release 11 Software from an earlier 10 release.

•Upgrading to the latest release of CWM Release 11 Software from an earlier 10 release with multiple CWM gateways.

Note You can upgrade your software to the CWM Release 11 release only if your workstation is currently running CWM 10.4 with patch 2, or CWM 10.5.10 with patch 1 software.

Caution Service Class Template (SCT) configurations are not preserved during the CWM 10.x to 11 upgrade process.

Upgrading to the Latest Release of CWM 11 Software from an Earlier 10 Release

To upgrade to the CWM Release 11 from releases 10.4, or 10.5 complete the following steps:

Step 1 Ensure that the requisite Solaris 2.7 patches are installed. See Chapter 1 and release notes for details.

Step 2 Log in as user svplus.

Step 3 Stop the CWM core processes.

Step 4 Log in to the CWM workstation as user root

Step 5 Insert the Cisco WAN Manager Release 11 CD#1 into the CDROM drive.

Step 6 Enter the following commands: 

#  cd /cdrom/cdrom0

#  ls

Step 7 Check for the InstallCWM.sh file and begin the install process by entering the following command: 

#  ./InstallCWM.sh

The CWM Installation Welcome window is displayed, as shown in Figure 4-1.

Figure 4-1 CWM Installation Welcome Window

Step 8 Click Next on the welcome window to continue.

The README Information window is displayed (see Figure 4-2).

Figure 4-2 CWM Installation README Information Window

Step 9 After reading the information presented on the README Information window, click Next.

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 10 At the Information About the Upgrade Procedure window, select Yes and click Next.

Figure 4-4 Upgrade Information

Step 11 When the Upgrade Information window is displayed, click OK

The CWM role in the CWM domain for CWM CWM Communication window is displayed, as shown in Figure 4-5. This window is displayed only if upgrading from 10.4 or 10.5.10, otherwise it is skipped.

Figure 4-5 CWM role in the CWM domain for CWM CWM Communication Window

Step 12 Select either Primary or Secondary for the CWM station being upgraded.

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 13 Enter the name of the primary CWM machine.

Step 14 Click Next.

The Auto-Partition Disks window is shown in Figure 4-7.

Figure 4-7 Auto-Partition Disks Window

Step 15 At the Auto-Partition window, accept the default No and click Next.

The Meta Devices window is displayed, as shown in Figure 4-8.

Figure 4-8 Meta Devices Window

Step 16 At the Meta Devices window, accept the default No and click Next.

Note A meta device is a virtual device created by concatenating or striping disk partitions (usually to improve performance).

The Multiple Disk Configuration for Informix window is displayed, as shown in Figure 4-9.

Figure 4-9 Multiple Disk Configuration for Informix Window

Step 17 At the Multiple Disk Configuration for Informix window, accept the default No if you have one disk, click on Yes If you have two disks. Click Next to continue.

The Select the Raw Partition for CWM Database window is displayed, as shown in Figure 4-10.

Figure 4-10 Select the Raw Partition for CWM Database

Step 18 In the Select the Raw Partition for CWM Database window, accept the default name of stratacom, by clicking Next. In this release of CWM, the partition cannot be changed

Note If you have multiple hard disks configured, more partitions may be displayed than those shown in Figure 4-10.

A small window is displayed warning the user that the selected partition must be at least 1 GBytes in size (see Figure 4-11).

Figure 4-11 Minimum Space Warning

Step 19 Check the size of the partition, if the size is not large enough click Cancel, change the partition size and restart the installation process. If the size is large enough, click OK and then click Next in the main window.

When Next has been clicked, the CWM FTP Information window is displayed as shown in Figure 4-12.

Figure 4-12 CWM FTP Information Window

Step 20 At the CWM FTP Information window, enter the user name (default "svplus") and the password of the user on the machine.

After entering the FTP user name and password, click Install.

The Choose Destination Directory window is displayed, as shown in Figure 4-13.

Note This window may or may not be displayed depending upon whether a suitable destination directory already exists.

Figure 4-13 Choose Destination Directory Window

Step 21 If this window is displayed, click Next.

In this release of CWM, the destination directory cannot be changed.

The Install Orbix window is displayed, as shown in Figure 4-14.

Figure 4-14 Install Orbix Window

Orbix is the software component that provides the communication capability between CWM gateways.

Step 22 At the Install Orbix window, accept the default Yes and click Next.

The Enter Domain Name window is displayed as shown in Figure 4-15.

Figure 4-15 Enter the Domain Name Window

Step 23 At the Enter the Domain Name window, enter the domain configured for the workstation.

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 24 After entering the domain name, click Next.

The Install CiscoView window is displayed, as shown in Figure 4-16.

Figure 4-16 Install CiscoView Window

Note The requested patches for CiscoView (106327-05, 106980-10, 107081-11, 107636-03, and 108376-03) should be installed after installing Solaris 2.7.

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 Do not install CiscoView over a previously installed CiscoView, this action will cause two versions of CiscoView to exist and the system will not operate properly.
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-17 Enter CiscoView Home Window

Step 25 At the Enter CiscoView Home window, either click Install to accept the default directory (/opt) or enter a new directory name and click Install.

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

A small log window is also displayed showing entries to the install log as they are entered.

Figure 4-18 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-19. Click Yes to All.

Figure 4-19 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-20.

Figure 4-20 Installation Progress Indicator (database creation)

An Install Log window is also displayed (see Figure 4-21)

Figure 4-21 Install Log

A dialog box displays informing you that the installation is complete, as shown in Figure 4-22.

Figure 4-22 Installation Complete Window

Step 26 Click Finish on the dialog box.

Doing so ends the software installation process is completed. The Install Shield window closes.

Step 27 At this point, you can push the CD-ROM eject button on the CD-ROM drive to eject the installation CD.

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.

When the upgrade is finished, the contents of the scmtemplate table are stored in /usr/users/svplus/SAVE/ under the filename scmtemplate.

Upgrading to the CWM 11 Software from Release 10.4 or 10.5.10 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, 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 network that has three Release 10.5.10 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 Although this example uses a network with three CWM stations, the same procedure can be extended to a network using any number of stations. The same procedure is also used if the three CWM stations are running CWM 10.4

In release 10.4, 10.5, and 11, the first CWM 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 also 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.

As shown in Figure 4-23, 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 CWMC

Figure 4-23 Initial State of CWM Gateways

CWMA 10.5.10
Primary
DomainGatewayList = A,B,C

 

CWMB 10.5.10
Secondary Pri 1
DomainGatewayList = A,B,C

 

CWMC 10.5.10
Secondary Pri 2
DomainGatewayList = A,B,C


Upgrade Procedure

The following steps upgrade the stations, one by one, to Release 11.

Step 1 Stop the CWM core process for CWMA

This action causes CWMB to assume the role of primary and CWMC the role of secondary priority 1.

Step 2 Use InstallCWM.sh to upgrade CWMA to release 11 as described in the previous section. Use the Primary/Secondary select window to select CWMA as primary.

Step 3 Start the CWM core process for CWMA.

CWMA starts as primary but in a different gateway domain.

The new states of the three CWM stations are shown in Figure 4-24.

Figure 4-24 State of CWM Gateways after Step 3

CWMA 11
Primary
DomainGatewayList = A

 

CWMB 10.5.10
Primary
DomainGatewayList = A,B,C

 

CWMC 10.5.10
Secondary Pri 1
DomainGatewayList = A,B,C


Step 4 Stop the CWM core process for CWMB

This action causes CWMC to assume the role of primary.

Step 5 Use InstallCWM.sh to upgrade CWMB to release 11.

When requested, use the Primary/Secondary select window to select CWMB as secondary 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.

The new states of the three CWM stations are shown in Figure 4-25.

Figure 4-25 State of CWM Gateways after Step 6

CWMA 11
Primary
DomainGatewayList = A

 

CWMB 11
Secondary Pri 1
DomainGatewayList = A,B

 

CWMC 10.5.10
Primary
DomainGatewayList = A,B,C


Step 7 Stop the CWM core process for CWMC.

Step 8 Use InstallCWM.sh to upgrade CWMC to release 11.

When requested, use the Primary/Secondary select window to select CWMC as secondary 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.

The new states of the three CWM stations are shown in Figure 4-26.

Figure 4-26 State of CWM Gateways after Step 9

CWMA 11
Primary
DomainGatewayList = A

 

CWMB 11
Secondary Pri 1
DomainGatewayList = A,B

 

CWMC 11
Secondary Pri 2
DomainGatewayList = A,C


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

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 Log in to the workstation as user svplus using the Solaris Login interface.

Step 2 Select CDE.

Step 3 Close the File Manager and Help windows, leaving only the CDE menu bar.

Step 4 Right-click on the blank screen, select Tools, select Terminal.

Move this terminal window to the upper right corner of the screen.

Step 5 Right click on blank screen select Hosts, select Terminal Console.

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 Left-click the CDE icon labeled TTT.

The Style Manager window is displayed.

Step 7 Left click on the Screen, click screen saver on and screen lock off. Click OK.

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 Click on Backdrop and select GrayDk. Click Apply.

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 Click on the CDE icon labeled TTT. Click Startup > Set Home Session > OK.

The next login session will come up using this same screen configuration. Click OK and close the Style Manager.

Step 10 Place the cursor in the terminal window. Enter the vi Editor to edit the network.conf file. 

% cd /usr/users/svplus/config

% vi network.conf

Step 11 Modify the network.conf file depending on your network requirements.

Note When using the vi Editor, remember to write your changes before quitting: press Esc, colon (:), then wq!

Checking the CWM Server File System

At the CWM workstation, log in as user root, and examine the following files.

•/etc/hosts

•/etc/netmasks

•/etc/rs2.d/S72inetsvc

•/etc/defaultrouter

•/usr/users/svplus/.cshrc

•/usr/users/svplus/network.conf

•/usr/users/svplus/config/CWMGateway.conf

•/system

•/etc/system

Note The IP addresses shown are examples. Use addresses relevant to your network.

/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/hosts

Use 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-l

MGX (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	mgx4

BPX Nodes

For each node:

Enter the node's IP address and the node name.

Example: 

192.0.0.8	bpx1

Example Host File

As an example, a hosts file might look like the following example: 

# MGX Rel 1, 2.0, up to 2.1.60 nodes

172.70.207.9	mgx1 
192.0.0.9	mgx1-l

172.70.207.6	mgx2 
192.0.0.6	mgx2-l

172.70.207.4	mgx3 
192.0.0.4	mgx3-l

#

#MGX Rel 2.1.70 and up nodes

172.70.209.9	mgx4

172.70.209.8	mgx5

172.70.209.7	mgx6

172.70.209.6	mgx7

#

#BPX nodes

192.0.0.8	bpx1

192.0.0.9	bpx2

192.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/S72inetsvc

Use the vi Editor to open the S72inetsvc file and find the following line: 

/usr/sbin/route add -interface -netmask "224.0.0.0" "224.0.0.0" "$mcastif"

)&

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 When using the vi editor, remember to write your changes before quitting: press Esc, colon (:), then wq!

/etc/defaultrouter

Examine the /etc/defaultrouter file. To view the /etc/defaultrouter file, enter the following command: 

host% more /etc/defaultrouter

Note If this file does not exist, use the vi Editor to create a new file with the name defaultrouter.

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 To save your changes while using the vi editor, remember to press Esc, colon (:), then wq!.

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:/opt/NSCPcom:$PATH

Add the following lines to the end of the file.

setenv PATH "netscape path":$PATH
setenv MOZILLA_HOME "netscape path"
Exit vi.

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.

•AutoRoute

•PNNI

•Hybrid (consisting of AutoRoute and PNNI segments)

For each network specified in the network.conf file, its entry consists of the following fields.

•NETWORK (this must be the first field)

•NETWORK ID

•GATEWAYS

•DISCOVERY PROTOCOL

•IP REACHABILITY FLAG

•OPTIONS

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 Long network names are truncated to 10 characters and invalid names are ignored.

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 After Network ID is modified, a CWM cold start is needed.

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 If either AR-GATEWAYS or PNNI-GATEWAYS is specified for the network, the other gateway entry (PNNI-GATEWAYS or AR-GATEWAYS as the case may be) can be omitted. However, specifying both types of gateway speeds up the discovery process and is recommended.

.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

•RETRANSMIT

•THROTTLE

•ACKNOWLEDGE

•BLOCKSIZE

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 In this release the default values must not be changed.

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 PNNI networks do not need IP REACHABILITY and OPTIONAL parameter

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/config

host% more CWMGateway.conf

Check the DomainGatewayList portion of this file. 

## Default: DomainGatewayList 
## Usage: DomainGateWayList tmonda dilbag sgharat 
DomainGatewayList CWM1 CWM2 CWM3

In 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/shmsys

forceload: sys/semsys

set semsys:seminfo_semaem=16384

set semsys:seminfo_semmap=66

set semsys:seminfo_semmni=4096

set semsys:seminfo_semmns=4096

set semsys:seminfo_semmnu=4096

set semsys:seminfo_semume=64

set semsys:seminfo_semvmx=32767

set semsys:seminfo_semmsl=30

set shmsys:shminfo_shmmax=268435456

set shmsys:shminfo_shmmin=100

set shmsys:shminfo_shmmni=100

set shmsys:shminfo_shmseg=100

Reboot the Workstation

After completing the configuration, reboot the workstation. 

#  sync ;sync ;reboot