installing cwm server software - · pdf filestep 2 insert the cisco wan ... the user can...

C H A P T E R

3-1Cisco WAN Manager Installation Guide

Release 15.1, Part Number OL-6259-01, Rev. A0, January 25, 2005

3Installing CWM Server Software

This chapter provides a step-by-step procedure to install the CWM Release 15.1 software on a CWM server workstation. The CWM Release 15.1 software installation process uses InstallShield to simplify the process.

Before installing the CWM Release 15.1 software on the CWM workstation, the following software should have been installed (in the following order):

1. Either Solaris 8 or Solaris 9 Operating System

2. Solaris patches (see the release notes for the latest list of patches)

3. HP OpenView 6.2, 6.3, or 7.0 (optional)

4. Netscape 4.7.6 or later for on-line help

See Chapter 2 for instructions on installing these products.

Installing CWM Software Installing the CWM software consist of responding to a series of screens. The screens can be regarded as being grouped into three phases.

• Initial installation phase

• Configuring Informix partitions phase (with or without meta devices)

• Completing the installation phase

Selecting the Installation ModeTo install the CWM Release 15.1 software, perform the following steps:

Step 1 Log in to the CWM workstation as user root.

Note If the CWM server is an Ultra 60 or other desktop system, merely log in from the keyboard. If the CWM server is a Netra 20 or other rackmount system, use another Sun workstation or PC as a console and log in remotely using telnet).

Step 2 Insert the Cisco WAN Manager Release 15.1 CD-ROM Number 1 into the CD-ROM drive of the CWM workstation.



Chapter 3 Installing CWM Server Software Installing CWM Software

Step 3 Enter the following commands:

# cd /cdrom/cdrom0# ls

Step 4 Check for the InstallCWM.sh file.

Step 5 Begin the install process by entering the following command:

# ./InstallCWM.sh

The following message is displayed.

Console Mode Option is recommended when you cannot connect to X Server from current terminal (See if you can open an xterm to check!)

Do you Want to Launch Installer in Console Mode? (Yes / No): [No]:y

Step 6 Respond No to continue the installation using the Installshield GUI.Respond Yes to continue the installation using Console Mode Install.

Note 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. Using Console Mode Install, the user can install CWM using an alpha-numeric terminal or a PC in terminal emulator mode.

Installshield GUI InstallationThe installation classes are loaded; this process takes several minutes.

Initial Installation Phase

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




Figure 3-1 CWM Installation Welcome Window

Step 1 Click Next on the Welcome window to continue.

The README Information window, Figure 3-2, is displayed.




Figure 3-2 License Agreement Window

Step 2 To continue with the installation, you must click on the “I accept” button and click Next.

The Information about the Physical Raw Partition window is displayed as shown in Figure 3-3.




Figure 3-3 Information about the Physical Raw Partition Window

Step 3 Select Yes if the Informix log is to have its own separate raw partition, otherwise select No.

Note This window is displayed only if the machine has more than one raw partition available to Informix.

Step 4 Click Next.

The Select the Raw partition for Physical Log window is displayed, as shown in Figure 3-4.

Note This window is displayed only if you have responded Yes in the previous screen because you want to configure a separate raw partition for the Informix log.




Figure 3-4 Select the Raw partition for Physical Log Window

Step 1 Select a raw partition for the Informix log.

Step 2 Click Next.

The Meta Devices window is displayed, as shown in Figure 3-5.




Figure 3-5 Meta Devices Window

Step 3 At the Meta Devices window, unless you have meta devices to configure, accept the default No. Otherwise, select Yes.

Step 4 Click Next.

Note A meta device is a virtual device created by concatenating or striping disk partitions (this is done usually to improve flexibility or performance). The use of meta devices usually requires volume management software found in Solaris (for example, Solstice Sun Disk Suite) or via third party vendors, such as Veritas.

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

Note If the user has specified one partition for the physical log and the system has only two raw partitions available, the answer to the multiple disk configuration is assumed to be No and the The Multiple Disk Configuration for Informix window is skipped




Figure 3-6 Multiple Disk Configuration for Informix Window

Step 5 At the Multiple Disk Configuration for Informix window, if you have one disk accept the default No. If you have multiple disks, click Yes.

Note In this context, the term disk refers to a disk partition (or slice).

Step 6 Click Next to continue.

Configuring Informix Partitions Phase

Configuring Informix partitions consists of eight different procedures of which only one needs to be performed. Which procedure the user performs depends upon the responses the user has made to the questions in the previous phase.

Select the procedure which corresponds to your previous answers to the following questions.

– Do you want the Informix log to have its own raw partition?

– Do you use disk striping (meta-devices) for database partitions?

– Are you using multiple disks (partitions) for Informix?

Proceed to one of the following procedures that corresponds to your answers.

In each of the procedures, the user is asked to specify details about the allocations of Informix partitions.




Note Informix uses the disk space available to it to construct three database spaces. If the user specifies multiple disks for Informix, the installation procedure requires the user to specify which database space is to be allocated to which partition. Note that the datadbs database space will be the largest and should be allocated accordingly.

The procedures are described in the following sequence.

1. No Meta Devices, No multiple disks, No separate raw log partition

2. No Meta Devices, No multiple disks, Yes separate raw log partition

3. No Meta Devices, Yes multiple disks, No separate raw log partition

4. No Meta Devices, Yes multiple disks, Yes separate raw log partition

5. Yes Meta Devices, No multiple disks, No separate raw log partition

6. Yes Meta Devices, No multiple disks, Yes separate raw log partition

7. Yes Meta Devices, Yes multiple disks, No separate raw log partition

8. Yes Meta Devices, Yes multiple disks, Yes separate raw log partition




1. No Meta Devices, No multiple disks, No separate raw log partition

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

Figure 3-7 Select the Raw Partition for CWM Database Window

This window displays only the raw partitions available to Informix.

Step 1 Select the single raw partition to be used.

Step 2 Click Next to proceed to the Completing the Installation section later in this chapter.




2. No Meta Devices, No multiple disks, Yes separate raw log partition


Note If only one raw partition is available for the databases, this window is skipped.


Step 1 Select the partition that is to be used for the Informix database.

Note The partition for the separate log is not displayed as it is no longer available for the database.





3. No Meta Devices, Yes multiple disks, No separate raw log partition



Step 1 Select the partitions for the rootdbs and datadbs.

Note Select only one partition for rootdbs. Rootdbs and datadbs cannot be assigned the same partitions. If there are enough raw partitions, datadbs can be assigned multiple partitions.





4. No Meta Devices, Yes multiple disks, Yes separate raw log partition


Note If only one raw partition is available for the databases, this window is skipped.


Step 1 Select the partitions for the rootdbs and datadbs.

Note Select one partition for rootdbs. Rootdbs and datadbs cannot be assigned the same partitions.

Step 2 Click Next to proceed to the Completing the Installation later in this chapter.




5. Yes Meta Devices, No multiple disks, No separate raw log partition



Step 1 Enter the path to the meta device and its size.





6. Yes Meta Devices, No multiple disks, Yes separate raw log partition

The Select the Path for CWM Database window is displayed, as shown in Figure 3-12.

Figure 3-12 S.elect the Raw Partition for CWM Database Window

Step 1 Enter the path and size of the meta device.





7. Yes Meta Devices, Yes multiple disks, No separate raw log partition



Step 1 Enter the paths and sizes of the meta devices.





8. Yes Meta Devices, Yes multiple disks, Yes separate raw log partition



Step 1 Enter the paths and sizes of the meta devices.

Step 2 Click Next to proceed to the following Completing the Installation section.




Completing the Installation

When the Configuring Informix Partitions phase has been completed, the CWM FTP Information Window is displayed as shown in Figure 3-15.

Figure 3-15 CWM FTP Information Window

Step 1 At the CWM FTP Information window, enter the user name (the default is “svplus”) and the password of the user on the machine.

Note In this release, the user name of “svplus” must be used and cannot be changed.

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

The CORBA Communications Options window is displayed as shown in Figure 3-17.




Figure 3-16 CORBA Communications Options

This window provides the user with four choices of how the server identifies itself for CORBA (Orbix) communications. These choices are:

• The CWM Server host name including a domain name

• The CWM Server host name without a domain name

• The IP address of the CWM server

• A user specified address

Select the method to use for your CWM network and click Next.

If you select “Host with DNS domain name,” you are asked to specify the domain name as shown in Figure 3-17. If you select “Host without DNS Domain name,” the Forced Delete Feature Selection window, Figure 3-19, is displayed. This screen prompts you to select whether or not you want to use the forced delete feature. For more information on this feature, refer to the Cisco WAN Manager User Guide, Release 15.1. If you select “Use machine IP Address,” the Forced Delete Feature Selection window, Figure 3-19, is displayed. If you select “Use specified IP Address,” you are asked to specify the IP address as shown in Figure 3-18.




Figure 3-17 Enter the Domain Name Window




Figure 3-18 Enter IP Address Window

Enter the Domain Name or IP Address as appropriate and click Next.

This domain name and IP address information allows the CWM client workstations access to the database. Also ensure that the workstation and the domain are reachable. You can enter the ping command to test this.




Figure 3-19 Forced Delete Feature Selection Window

Step 2 To choose the Force Delete option and continue with the installation, you must click on the “Yes” radio button and then click Next.

The Upgrade Procedure window is displayed, as shown in Figure 3-20.




Figure 3-20 Upgrading Procedure Window

Step 3 At the Upgrading Procedure window, accept the default No (because this is an initial installation and not an upgrade).

Note If you are upgrading from an earlier version of CWM and not performing an initial installation, go to the upgrade procedure that is described in Chapter 4.

Step 4 Click Next.

A confirmation screen prior to the actual installation of the files is displayed as shown in Figure 3-21.




Figure 3-21 Installer Confirmation Window

Step 5 If the information in the Confirmation window is correct, click Next. If it is not correct, click Back to the appropriate window and correct the wrong settings. If you click Next, the Installation Progress Window is displayed as shown in Figure 3-22.




Figure 3-22 Installation Progress Indicator

If the CWM system has been installed previously, a message appears telling the user that files already exist and permission is requested to overwrite the files with new files. This message is shown in Figure 3-23.

Figure 3-23 Copy Files Message

Step 6 Click Yes to All.

After the files are copied, an Install Log window is also displayed (see Figure 3-24). This log provides on-the-screen messages indicating events during the installation process.

Installing the CWM server generates the log file cwmexecinstall.Log in the /usr/users/svplus/install directory.




Figure 3-24 Install Log

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

Figure 3-25 Installation Complete Window

Step 7 Click Finished.

The software installation process is completed. The Install Shield window closes.

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 and gracefully shuts down the Solaris operating system.

Step 8 Push the CDROM eject button on the CDROM drive to eject the installation CD-ROM.




Note When CWM is installed, the tasks can be checked by displaying the contents of the cwmexecinstall.Log file under usr/users/svplus/install. This log displays the installation tasks that were completed and lists any errors encountered during the installation.

Console Mode Installation If you enter Yes to run in Console Mode, the following panel is displayed

You've chosen to Launch Installer in Console Mode

Loading the installation classes. This may take a few minutes................................................................................................................................................................................................................................................................................................................................................................................InstallShield Wizard

Initializing InstallShield Wizard...

Searching for Java(tm) Virtual Machine............Running InstallShield Wizard...

After a few seconds the Initial Installation phase starts

Making Selections during Console Mode Upgrade

The Console Mode procedure consists of responding to a series of questions. The user is asked either to select an item from a list or to enter data (for example, a database path or a disk size).

Selecting an Item from a List.

When a list is displayed, each item in the list has an item number. One item in the list is already selected as indicated by an X. For example:

Choose the Raw partition for Informix Physical Log:

[X] 1 - /dev/rdsk/c1t0d0s7 ( 4000 MB) [ ] 2 - /dev/rdsk/c1t1d0s0 ( 2048 MB) [ ] 3 - /dev/rdsk/c1t1d0s1 ( 2048 MB) To select a choice enter its number, or 0 when you are finished [0]:

The above example lists three disk partitions from which the user must select one. These items are numbered as 1, 2, and 3 and the first is already selected as indicated by [X].

The user can accept the already selected item or select another item by typing its number followed by the Enter key (in which case the list is displayed again but with the [X] against the selected item).




When the [X] is shown against the correct item (either in the initial display or after the user has selected another item), the user should press 0 followed by the Enter key. The following message is then displayed.

Press 1 for Next panel, 2 for Previous panel, 3 to Cancel or 4 to Redisplay [1]

The user then press 1, 2, 3, or 4 (as appropriate) followed by the Enter key. Normally this will be the 1 key to progress to next step in the upgrade process.

Entering Data

When requested, enter the data and press the Enter key. If you want to change the entered data, press 1 and the Enter key and then start over. When the enter data are correct, press 0 and the Enter key.

Initial Installation Phase

Step 1 The Welcome message is displayed.

-------------------------------------------------------------------------------

Welcome to the Cisco Wan Manager installation program. Click Cancelat any time to quit the installation. Press Next to continue the installation.

Press 1 for Next panel, 3 to Cancel or 4 to Redisplay [1]

-------------------------------------------------------------------------------

Press 1 then Enter to display the next message

Step 2 The Readme message is displayed.

-------------------------------------------------------------------------------

Cisco Wan Manager 15.1.0 Copyright (c) 2004 Cisco Systems, Inc. Allrights reserved. This software product is copyrighted and all rights arereserved by Cisco Systems, Inc. Cisco Systems, Inc. reserves the right to makeperiodic modifications to this product without obligation to notify any personor entity of such revision. Copying, duplicating, selling, or otherwisedistributing any part of this product without the prior written consent of anauthorized representative of Cisco Systems, Inc. is prohibited. IPX, IGX8400,BPX8600, MGX8220, MGX8850, MGX8950 and FastPacket are registered trademarksand Cisco WAN Manager is a trademark of Cisco Systems, Inc.

Please choose from the following options:

[X] 1 - I accept the terms of the license agreement. [ ] 2 - I do not accept the terms of the license agreement.

To select a choice enter its number, or 0 when you are finished [0]:


-------------------------------------------------------------------------------

a. To accept the license terms, press 0 then Enter.

b. Press 1 then Enter to display the next message.




Step 3 The Upgrading message is displayed.

-------------------------------------------------------------------------------

Are You Upgrading Cisco WAN Manager? [ ] 1 - Yes [X] 2 - No



-------------------------------------------------------------------------------

a. To select a new install (not upgrading), either press 0 (to accept the default) or press 2 and then press 0.

b. Press 1 then Enter to display the next panel.

Step 4 The Physical Log on separate partition panel is displayed.

-------------------------------------------------------------------------------

Please select the partitions where you want Informix Physical Log

[X] 1 - Same Raw Partition [ ] 2 - Separate Raw Partition [ ] 3 - Meta Devices To select a choice enter its number, or 0 when you are finished [0]: Press 1 for Next panel, 2 for Previous panel, 3 to Cancel or 4 toRedisplay [1]

-------------------------------------------------------------------------------

a. To select same raw partition, either press 0 (to accept the default) or press 1 then press Enter.

b. To select a separate raw partition for the Informix Physical Log, press 2 then Enter.

c. To select meta devices, press 3 then Enter.

d. Press 1 then Enter to display the next panel.

Step 5 The Select Partition for Physical Log panel is displayed

-------------------------------------------------------------------------------

Choose the Raw partition for Informix Physical Log:

[X] 1 - /dev/rdsk/c1t0d0s7 ( 4000 MB) [ ] 2 - /dev/rdsk/c1t1d0s0 ( 2048 MB) [ ] 3 - /dev/rdsk/c1t1d0s1 ( 2048 MB) [ ] 4 - /dev/rdsk/c1t1d0s3 ( 2048 MB) To select a choice enter its number, or 0 when you are finished [0]:


-------------------------------------------------------------------------------

This panel displays all the raw partitions that are available for the Informix Physical Log.

a. To select a raw partition, either press 0 (to accept the default) or press a number of the desired partition and then press Enter. If the correct partition is selected, press 0 then Enter.




b. Press 1 then Enter to display the next panel.

Step 6 The Meta Devices panel is displayed.

Note A meta device is a virtual device created by concatenating or striping disk partitions (this is done usually to improve flexibility or performance). The use of meta devices usually requires volume management software found in Solaris (for example, Solstice Sun Disk Suite) or via third party vendors, such as Veritas.

-------------------------------------------------------------------------------

Do you use Disk-stripping (meta-devices) for database Partitions? [ ] 1 - Yes [X] 2 - No



-------------------------------------------------------------------------------

a. To select no meta devices, either press 0 (to accept the default) or press 2 then press Enter. If the correct option is selected, press 0 then Enter.

b. To select the use of meta devices, press 1 then press Enter. If the correct option is selected, press 0 then Enter.

c. Press 1 then Enter to display the next panel.

Step 7 The Multiple Disks panel is displayed.

Note If the user specified a separate partition for the physical log and the system has only two raw partitions available, the answer to the multiple disk configuration is assumed to be No and this panel is skipped

-------------------------------------------------------------------------------

Do you want to use Multiple Disk configuration for Informix database?

[ ] 1 - Yes [X] 2 - No



-------------------------------------------------------------------------------

a. To select no multiple disks, either press 0 (to accept the default) or press 2 then press Enter.

b. To select the use of multiple disks, press 1 then press Enter.

c. When the correct option is selected, press 0 then Enter.




d. Then press 1 then Enter to display the next panel.

Configuring Informix Partitions Phase

Configuring Informix partitions consists of eight different procedures of which only one needs to be performed. Which procedure the user performs depends upon the responses the user has made to the questions in the previous phase.

Select the procedure which corresponds to your previous answers to the following questions.

– Do you want the Informix log to have its own raw partition?

– Do you use disk striping (meta-devices) for database partitions?

– Are you using multiple disks (partitions) for Informix?

Proceed to one of the following procedures that corresponds to your answers.

In each of the procedures, the user is asked to specify details about the allocations of Informix partitions.

Note Informix uses the disk space available to it to construct three database spaces. If the user specifies multiple disks for Informix, the installation procedure requires the user to specify which database space is to be allocated to which partition. Note that the datadbs database space will be the largest and should be allocated accordingly.

The procedures are described in the following sequence.

1. No Meta Devices. No Multiple Disks, No Separate Raw Log Partition

2. No Meta Devices. No Multiple Disks, Yes Separate Raw Log Partition

3. No Meta Devices. Yes Multiple Disks. No Separate Raw log partition

4. No Meta Devices. Yes Multiple Disks. Yes Separate Raw log partition

5. Yes Meta Devices. No Multiple Disks. No Separate Raw Log Partition

6. Yes Meta Devices. No Multiple Disks. Yes Separate Raw Log Partition

7. Yes Meta Devices. Yes Multiple Disks. No Separate Log Partition

8. Yes Meta Devices. Yes Multiple Disks. Yes Separate Log Partition

1. No Meta Devices. No Multiple Disks, No Separate Raw Log Partition

The following panel is displayed.

-------------------------------------------------------------------------------

Choose the Raw Partition(s) for Informix: rootdbs

[X] 1 - /dev/rdsk/c1t1d0s0 ( 2048 MB) [ ] 2 - /dev/rdsk/c1t1d0s1 ( 2048 MB) [ ] 3 - /dev/rdsk/c1t1d0s3 ( 2048 MB)






-------------------------------------------------------------------------------

This window displays only the raw partitions available to Informix.

Step 1 Press the number corresponding to raw partition to be used and then press Enter. If the correct partition is selected, press 0 then Enter.

Step 2 Then press 1 then Enter to proceed to the Completing the Installation section later in this chapter.

2. No Meta Devices. No Multiple Disks, Yes Separate Raw Log Partition

The following panel is displayed.

-------------------------------------------------------------------------------

Choose the Raw Partition(s) for Informix: rootdbs

[X] 1 - /dev/rdsk/c1t1d0s0 ( 2048 MB) [ ] 2 - /dev/rdsk/c1t1d0s1 ( 2048 MB) To select a choice enter its number, or 0 when you are finished [0]:


-------------------------------------------------------------------------------

This window displays only the raw partitions available to Informix. Notice that the separate partition previously selected for the Informix physical log is no longer available and is not displayed.

Step 1 Press the number corresponding to raw partition to be used and then press Enter. If the correct partition is selected, press 0 then Enter.


3. No Meta Devices. Yes Multiple Disks. No Separate Raw log partition

The following panel is displayed

-------------------------------------------------------------------------------

Choose the Raw Partition for Root Dbs

[X] 1 - /dev/rdsk/c1t0d0s7 ( 4000 MB) [ ] 2 - /dev/rdsk/c1t1d0s0 ( 2048 MB) [ ] 3 - /dev/rdsk/c1t1d0s1 ( 2048 MB) To select a choice enter its number, or 0 when you are finished [0]: 5

Step 1 Press the number corresponding to Root Dbs partition to be used and then press Enter. After the correct partition is selected, press 0 then Enter.The following panel is displayed.




[ ] 2 - /dev/rdsk/c1t1d0s0 ( 2048 MB) [ ] 3 - /dev/rdsk/c1t1d0s1 ( 2048 MB) [ ] 4 - /dev/rdsk/c1t1d0s3 ( 2048 MB) [X] 5 - /dev/rdsk/c1t1d0s4 ( 2048 MB) To select a choice enter its number, or 0 when you are finished [0]:

Press 1 for Next panel, 2 for Previous panel, 3 to Cancel or 4 to Redisplay [1] -------------------------------------------------------------------------------

Step 2 Press the number corresponding to Datadb partition to be used and then press Enter. If the correct partition is selected, press 0 then Enter.


4. No Meta Devices. Yes Multiple Disks. Yes Separate Raw log partition

The following panel is displayed:

-------------------------------------------------------------------------------

Choose the Raw Partition for Root Dbs

[X] 1 - /dev/rdsk/c1t0d0s7 ( 4000 MB) [ ] 2 - /dev/rdsk/c1t1d0s0 ( 2048 MB) [ ] 3 - /dev/rdsk/c1t1d0s1 ( 2048 MB) [ ] 4 - /dev/rdsk/c1t1d0s3 ( 2048 MB) [ ] 5 - /dev/rdsk/c1t1d0s4 ( 2048 MB)


Step 1 Press the number corresponding to Root Dbs partition to be used and then press Enter, If the correct partition is selected, press 0 then Enter.

Press 1 then Enter, The following panel is displayed:

-------------------------------------------------------------------------------

Choose the Raw Partition for Data Dbs

[ ] 2 - /dev/rdsk/c1t1d0s0 ( 2048 MB) [ ] 3 - /dev/rdsk/c1t1d0s1 ( 2048 MB) [ ] 4 - /dev/rdsk/c1t1d0s3 ( 2048 MB) [X] 5 - /dev/rdsk/c1t1d0s4 ( 2048 MB) To select a choice enter its number, or 0 when you are finished [0]:

Press 1 for Next panel, 2 for Previous panel, 3 to Cancel or 4 to Redisplay [1] -------------------------------------------------------------------------------

Step 2 Press the number corresponding to Datadb partition to be used then press Enter, If the correct partition is selected, press 0 then Return.





5. Yes Meta Devices. No Multiple Disks. No Separate Raw Log Partition


-------------------------------------------------------------------------------

Enter the Complete path of the meta device for the informix database rootdatabases

[]

Step 1 Enter the path of the meta device and press the Enter key.The following panel is displayed:

Enter the Size in MB

[]


-------------------------------------------------------------------------------

Step 2 Enter the size of the database in megabytes and press the Enter key.


6. Yes Meta Devices. No Multiple Disks. Yes Separate Raw Log Partition


-------------------------------------------------------------------------------

Enter the Complete path of the meta device for the informix database rootdbspace

[]

Step 1 Enter the path of the meta device and press the Enter key.The following panel is displayed:


[]


-------------------------------------------------------------------------------

Step 2 Enter the size of the database in megabytes and press the Enter key.





7. Yes Meta Devices. Yes Multiple Disks. No Separate Log Partition


-------------------------------------------------------------------------------


[]

Step 1 Enter the path of the meta device for the Informix database root and press the Enter key.The following panel is displayed:


[]

Step 2 Enter the size of the Informix database root in megabytes and press the Enter key..

Enter the Complete path of the meta device for the informix database CWMdbspace

[]

Step 3 Enter the path of the meta device for the Informix Logdbs and press the Enter key.The following panel is displayed:


[]

Step 4 Enter the size of the Informix database CWM dbspace in megabytes and press the Enter key.The following panel is displayed:.

[]

Enter the Complete path of the meta device for the informix database logdbs

[]


[]

Step 5 Enter the path of the meta device for the Informix database logdbs and press the Enter key.The following panel is displayed:


[]


Step 6 Enter the size of the Informix database CWM dbspace in megabytes and press the Enter key.





8. Yes Meta Devices. Yes Multiple Disks. Yes Separate Log Partition


-------------------------------------------------------------------------------


[]

Step 1 Enter the path of the meta device for the Informix database root and press the Enter key.The following panel is displayed:


[]

Step 2 Enter the size of the Informix database root in megabytes and press the Enter key..

Enter the Complete path of the meta device for the informix database CWMdbspace

[]

Step 3 Enter the path of the meta device for the Informix database CWM dbspace and press the Enter key.The following panel is displayed:


[]

Step 4 Enter the size of the Informix database CWM dbspace in megabytes and press the Enter key.The following panel is displayed:.

[]

Enter the Complete path of the meta device for the informix database logdbs

[]


[]

Step 5 Enter the path of the meta device for the Informix database logdbs and press the Enter key.The following panel is displayed:


[]

Press 1 for Next panel, 2 for Previous panel, 3 to Cancel or 4 to




Redisplay [1]

-------------------------------------------------------------------------------

Step 6 Enter the size of the Informix Logdbs in megabytes and press the Enter key.

Step 7 Press 1 then Enter to proceed to the Completing the Installation section later in this chapter.

Completing the Installation

When one of the eight Informix partition phase procedures has been completed, the FTP Information panel is displayed automatically.

-------------------------------------------------------------------------------

FTP User name

[svplus]

FTP Password

:ReEnter the Password: Press 1 for Next panel, 2 for Previous panel, 3 to Cancel or 4 to Redisplay [1]

-------------------------------------------------------------------------------

Step 1 Perform the following sub-steps.

a. Leave the FTP User name as the default value of “svplus”.

b. Enter the password to be used for FTP and press the Enter key.

c. Repeat the password and again press the Enter key.

d. Press 1 then Enter to proceed to the next panel.

Step 2 The CORBA Communication Option panel is displayed

-------------------------------------------------------------------------------

Please choose one of the following options for CORBA communication: [X] 1 - Host with DNS domain setup [ ] 2 - Host without DNS domain [ ] 3 - Use machine IP Address [ ] 4 - Use specified IP Address


This window provides the user with four choices of how the server identifies itself for CORBA (Orbix) communications. These choices are:

• The CWM Server host name including a domain name

• The CWM Server host name without a domain name

• The IP address of the CWM server

• A user specified address




Perform the following sub-steps.

a. Select the method in use for your CWM network and press 0 and Return.

b. Press 1 then Enter to proceed to the next panel.

c. If the user selects “Host with DNS domain name,” the user is then asked to specify the domain name.

-------------------------------------------------------------------------------

Enter the Domain Name to be used by Orbix (eg:cisco.com)

[]

Press 1 for Next panel, 2 for Previous panel, 3 to Cancel or 4 to Redisplay [1] 2

-------------------------------------------------------------------------------

Enter the Domain Name and press the Return key, Press 1 for the next panel.

d. If the user selects “Use specified IP Address,” the user is then asked to specify the IP address.

-------------------------------------------------------------------------------

Please enter the IP Address for Orbix communication:

[172.29.52.25]


-------------------------------------------------------------------------------

Enter the IP Address and press the Return key, Press 1 for the next panel.

The Force Delet Option panel is displayed.

-------------------------------------------------------------------------------

Do you want Force Delete option? [X] 1 - Yes [ ] 2 - No To select a choice enter its number, or 0 when you are finished [0]: Press 1 for Next panel, 2 for Previous panel, 3 to Cancel or 4 toRedisplay [1]

------------------------------------------------------------------------------

Perform the following sub-steps.

a. Press 1 then Enter to select the Force Delete option.

b. Press 2 then Enter if you do not want the Force Delete option.

The Installation Preview panel is displayed.

-------------------------------------------------------------------------------

Cisco Wan Manager will be installed in the following location:/usr/users/svpluswith the following features:CWMfor a total size: 1743.9MB




Press 1 for Next panel, 2 for Previous panel, 3 to Cancel or 4 to Redisplay [1]-------------------------------------------------------------------------------

Step 3 Perform the following sub-steps.

a. Check the information. If not correct, use the 2 key to go back to a previous panel so that the correction can be made.

b. When the displayed information is correct, press 1 then Enter to proceed to the next panel.

The Installation Progress panel is displayed.

-------------------------------------------------------------------------------

Running in Console Mode. Do tail -f in a separate window on log file for status.Log file is /usr/users/svplus/install/cwmexecInstall.Log

Installing Cisco Wan Manager ... Please wait.

|-----------|-----------|-----------|------------|0% 25% 50% 75% 100%|||||||||||||||||||||||||||||||||||||||||||||||||Committing changes to the Solaris Product Registry.|.........DONE

Creating uninstaller...

-------------------------------------------------------------------------------

The progress bar indicates the progress of the installation. When the installation is complete, the Installation Complete is displayed.

-------------------------------------------------------------------------------The InstallShield Wizard has successfully installed Cisco Wan Manager. Choose Finish to exit the wizard.

Press 3 to Finish or 4 to Redisplay [3]

-------------------------------------------------------------------------------

Step 4 Press 3 then Enter to complete the installation.



Chapter 3 Installing CWM Server Software Installing RtmProxy

Installing RtmProxyRtmProxy is a software module that allows the user to receive traps from a standalone statistics manager (SSM) machine when there is no Service Agent installed on the CWM Server.

Note Do not install RtmProxy if the CWM Service Agent is installed. If RtmProxy and the Service Agent are both installed in the same CWM Server, the trap function is duplicated by both programs and the system will not function properly.

If RtmProxy is installed in a CWM Server and later you want to install the CWM Service Agent, uninstall RtmProxy first (see Chapter 9 for details).

Selecting the Installation ModeTo install the RtmProxy software, perform the following steps:

Step 1 Log in to the CWM workstation as user root.

Note If the CWM server is an Ultra 60 or other desktop system, merely log in from the keyboard. If the CWM server is a Netra 20 or other rackmount system, use another Sun workstation or PC as a console and log in remotely using telnet).

Step 2 Insert the Cisco WAN Manager Release 15.1 CD-ROM Number 1 into the CD-ROM drive of the CWM workstation.

Step 3 Enter the following commands:

# cd /cdrom/cdrom0# ls

Step 4 Check for the InstallRTMProxy.sh file.

Step 5 Begin the install process by entering the following command:

# ./InstallRTMProxy.sh


Console Mode Option is recommended when you cannot connect to X Server from current terminal (See if you can open an xterm to check!)

Do you Want to Launch Installer in Console Mode? (Yes / No): [No]:y

Step 6 Respond No to continue the installation using the Installshield GUI.Respond Yes to continue the installation using Console Mode Install.




Note 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. Using Console Mode Install, the user can install CWM using an alpha-numeric terminal or a PC in terminal emulator mode.

Installshield GUI InstallationThe installation classes are loaded: this process takes several minutes.

The RtmProxy Installation Welcome window is displayed, as shown in Figure 3-26.

Figure 3-26 RTM Proxy Installation Welcome Window

Step 1 Click Next on the Welcome window to continue.

The License Agreement window, Figure 3-27, is displayed.




Figure 3-27 License Agreement Window

Step 2 To continue with the installation, you must click on the “I accept” button and then click Next.

A confirmation screen prior to the actual installation of the files is displayed as shown in Figure 3-28.

Figure 3-28 Installer Confirmation Window




Step 3 If the information in the Confirmation window is correct, click Next. If it is not correct, click Back to the appropriate window and correct the wrong settings. When Next is clicked, the Installation Progress Window is displayed as shown in Figure 3-29.

Figure 3-29 Installation Progress Indicator

After the files are copied, an Install Log window is also displayed. This log provides on-the-screen messages indicating events during the installation process.

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




Figure 3-30 Installation Complete Window

Step 4 Click Finished.

The software installation process is completed. The Install Shield window closes.

Console Mode Installation If you enter Yes to run in Console Mode, the following panel is displayed

You've chosen to Launch Installer in Console Mode

Loading the installation classes. This may take a few minutes................................................................................................................................................................................................................................................................................................................................................................................InstallShield Wizard

Initializing InstallShield Wizard...

Searching for Java(tm) Virtual Machine............Running InstallShield Wizard...

After a few seconds the Initial Installation phase starts




Making Selections during Console Mode Installation

The Console Mode procedure consists of responding to a series of questions. The user is asked either to select an item from a list or to enter data (for example, a database path or a disk size).

Selecting an Item from a List.

When a list is displayed, each item in the list has an item number. One item in the list is already selected as indicated by an X. For example:

Choose from the following options:


To select a choice enter its number, or 0 when you are finished [0]: 0

The above example lists two options from which the user must select one. These items are numbered as 1 and 2 and the first is already selected as indicated by [X].

The user can accept the already selected item or select another item by typing its number followed by the Enter key (in which case the list is displayed again but with the [X] against the selected item).

When the [X] is shown against the correct item (either in the initial display or after the user has selected another item), the user should press 0 followed by the Enter key. The following message is then displayed.


The user then press 1, 2, 3, or 4 (as appropriate) followed by the Enter key. Normally this will be the 1 key to progress to next step in the upgrade process.

Entering Data

When requested, enter the data and press the Enter key. If you want to change the entered data, press 1 and the Enter key and then start over. When the enter data are correct, press 0 and the Enter key.

Installation Phase

Step 1 The Welcome message is displayed.

-------------------------------------------------------------------------------

Welcome to the RTM Proxy installation program. Click Cancelat any time to quit the installation. Press Next to continue the installation.

Press 1 for Next panel, 3 to Cancel or 4 to Redisplay [1]

-------------------------------------------------------------------------------

Press 1 then Enter to display the next message

Step 2 The License Agreement message is displayed.

-------------------------------------------------------------------------------

Cisco WAN Manager 15.1.0 Copyright (c) 2004 Cisco Systems, Inc. All rightsreserved. This software product is copyrighted and all rights are reserved by




Cisco Systems, Inc. Cisco Systems, Inc. reserves the right to make periodicmodifications to this product without obligation to notify any person orentity of such revision. Copying, duplicating, selling, or otherwisedistributing any part of this product without the prior written consent of anauthorized representative of Cisco Systems, Inc. is prohibited. IPX, IGX8400,BPX8600, MGX8220, MGX8850, MGX8950 and FastPacket are registered trademarksand Cisco WAN Manager is a trademark of Cisco Systems, Inc.

Please choose from the following options:


To select a choice enter its number, or 0 when you are finished [0]: 0


-------------------------------------------------------------------------------

a. To accept the license terms, press 0 then Enter.

b. Press 1 then Enter

Step 3 The installation confirmation message is displayed.

RTM Proxy will be installed in the following location:/usr/users/svplusfor a total size: 7MB


Press 1 to start the installation or, if the information is not correct, press 2 to go back.


Running in Console Mode...Configuration status can be checked by executing 'tail -f /usr/users/svplus/install/RTMexecinstall.Log'

Installing RTM Proxy... Please wait.

|-----------|-----------|-----------|------------|0% 25% 50% 75% 100%|||||||||||||||||||||||||||||||||||||||||||||

The progress bar is updated during the installation. When finished, the following message is displayed.

....DONE

Creating uninstaller...

-------------------------------------------------------------------------------

The InstallShield Wizard has successfully installed RTM Proxy. Choose Finishto exit the wizard.

Press 3 to Finish or 4 to Redisplay [3] 3

Step 4 Press 3 and return to finish the installation.



Chapter 3 Installing CWM Server Software Post Installation Tasks

Post Installation TasksAfter the CWM installation is complete, a number of configuration tasks should be completed.

The following sections list the CWM Server files that should be checked and/or modified. This section also includes a list of reserved port and user IDs that must be avoided by other (non-CWM) programs.

Note If, at this point, you have not ejected the CWM CD-ROM, enter the eject command in the terminal window.

Checking the CWM Server File SystemAt the CWM workstation log in as user root, and examine the following files.

• /etc/hosts

• /etc/netmasks

• /etc/rs2.d/S72inetsvc

• /etc/defaultrouter

• /system

• /etc/system

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

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

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

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

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

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 the following paragraphs).

To view the /etc/hosts file, enter the following command:

host% more /etc/hosts

If the host file needs to be modified, use vi or some other editor to enter items into the file.

MGX Nodes

For each node:

Enter the IP address and its nodename as specified in the node’s ipIfconfig command and option 8 of the node’s cnfndparms command.




Note These nodes can have two IP addresses, namely, an ATM IP address and a LAN port address. The node’s ipifconfig CLI command is used to specify both of these addresses. The command uses an atm0 parameter for the ATM IP address and an lnPci0 parameter for the LAN port IP address. Option 8 in the node’s cnfndparms CLI command is then used to specify which of these two addresses is to be used for CWM and it is this IP address that should be used in the hosts file.

The current setting of option 8 can be displayed using the dspndparms command.

For more details of these commands, see Cisco MGX 8850 (PXM1E/PXM45), Cisco MGX 8950, and Cisco MGX 8830 Command Reference, Release 5.1.

Example host file entry:

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 Hosts File

A hosts file might look like the following example:

# MGX Rel 1, 2.0, up to 2.1.60 nodes172.70.207.9 mgx1192.0.0.9 mgx1-l172.70.207.6 mgx2192.0.0.6 mgx2-l172.70.207.4 mgx3192.0.0.4 mgx3-l##MGX 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

An example of a netmasks entry is:




172.29.52.0 225.225.225.0

This display indicates a network number and a network mask of 225.225.225.0 (a commonly used value).

The network mask is installation dependent (check with your network administrator). Use vi or some other editor to change the value if necessary.

/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 vi or some other 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 and netmask)

/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 or some other 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.

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

Verify that the following line exists in this file:

(set semsys:seminfo_semmsl=30).

If this line does not exist or is incorrect, use a text editor to make the necessary correction.




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

/usr/users/svplus/config/network.conf file

The network.conf file located in the /usr/users/svplus/config/ directory, is used to specify the network(s) to be discovered and managed by CWM. Basically, this file describes the routing protocol, the gateway address to the network, and whether in-band or out-of-band management is to be used.

The format of the file depends upon the type of network of which there are four as follows.

• AutoRoute network

• PNNI network

• Hybrid network (one consisting of AutoRoute and PNNI nodes connected via pnni/xlmi trunks)

• Standalone nodes

To view the /usr/users/svplus/config/network.conf file, enter the following command:

host% more /usr/users/svplus/config/network.conf

Network.conf File for AutoRoute Networks (BPX/IGX)

For AutoRoute BPX and IGX networks using in-band management the file has the following format.

NETWORK:Network1 (a name for CWM to identify the network)GATEWAYS:sj123456(the name or IP address of the gateway to the network)DISCOVERY PROTOCOL:AUTOROUTE (the discovery protocol, in this case always AUTOROUTE)IP REACHABILITY FLAG:NWIP_OFF (specifies in-band or out-of-band management)OPTIONAL:"TIMEOUT = 7, RETRANSMIT = 6, THROTTLE = 0, ACKNOWLEDGE = 30, BLOCKSIZE = 1024"

(the optional field is used to specify parameters if the desired value is different from the default value, see Table 3-2)

Check that the mnemonic of the gateway node is correct. Also, for BPX and IGX, check that the IP Reachability Flag is correct as shown in Table 3-1.




Note Appendix B provides more details about IP Reachability.

Table 3-2 provides a list of the optional parameters in the network.conf file.

Note In Table 3-2, default values must not be changed.

Sample Network 1: Discover an AutoRoute Network

Note Use only one Gateway per network in case of AutoRoute networks

NETWORK:Network1GATEWAYS:nmsbpx12DISCOVERY PROTOCOL:AUTOROUTEIP REACHABILITY FLAG:NWIP_ONOPTIONAL:"TIMEOUT = 7, RETRANSMIT = 6, THROTTLE = 0, ACKNOWLEDGE = 30, BLOCKSIZE = 1024"

Table 3-1 IP Reachability Values

Parameter Value Description

NWIP_ON For in-band management. All the CWM messages are sent to each destination node using the node’s nwip(atm_ip_address).

NWIP_OFF For out-of-band management. All the CWM messages are sent to the Gateway node and then relayed to the destination node through trunks. This case also uses the node’s atm_ip_address for communication.

LANIP For out-of-band management. All the CWM messages are sent to each destination node out-of-band using the node's LAN IP.

Table 3-2 network.conf Optional Parameters

Parameter Name Default Value Description

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

RETRANSMIT 6 Link retry count. The number of times CWM will retransmit a message before it declares the link down.

THROTTLE 0 Download throttling timeout value.

ACKNOWLEDGE 30 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.

BLOCKSIZE 1024 Block size used for an Cisco IGX 8400 or Cisco BPX 8600 configuration upload.




Note Check that BPX nodes can be reached using Telnet and the BPX names (the names should get resolved to their IP addresses).

Note To save your changes while using the vi Editor, remember to press Esc, colon (:), then wq!.

Network.conf File for PNNI Networks (PXM 1E and PXM45 based Nodes)

For PNNI PXM 1E and PXM45 based Nodes the file has the following format.

NETWORK:Network1 (a name for CWM to identify the network)GATEWAYS:sj123456(the name or IP address of the gateway to the network)DISCOVERY PROTOCOL:PNNI (the discovery protocol, in this case always PNNI)

Note PNNI networks do not use the IP REACHABILITY and the OPTIONAL parameters.

Sample Network 2: Discover a PNNI network

NETWORK:Network2GATEWAYS:nmsmgx01,nmsmgx11DISCOVERY PROTOCOL:PNNI

Note Multiple Gateways should be separated by commas.


Network.conf File for Hybrid Networks

For Hybrid (AutoRoute and PNNI) networks the file has the following format.

NETWORK:Network1 (a name for CWM to identify the network)AR-GATEWAYS:sj123456(the name or IP address of the gateway to the Auroroute section of the

network)PNNI-GATEWAYS:sj123456(the name or IP address of the gateway to the PNNI section of the

network)DISCOVERY PROTOCOL:HYBRID (the discovery protocol, in this case always HYBRID)IP REACHABILITY FLAG:NWIP_OFF (specifies in-band or out-of-band management)OPTIONAL:"TIMEOUT = 7, RETRANSMIT = 6, THROTTLE = 0, ACKNOWLEDGE = 30, BLOCKSIZE = 1024"(the optional field is used to specify parameters if the desired value is different from the default value, see Table 3-4)

Note For hybrid networks the IP reachability flags and the optional parameters apply to the AutoRoute part of the network only.

An SES node cannot be specified as a PNNI gateway.

Check that the mnemonic of the gateway node is correct. Also, for AutoRoute nodes, check the IP Reachability Flag is correct as shown in Table 3-3.





Sample Network 1: Discover a Hybrid Network

Note Use only one Gateway per network in case of AutoRoute networks.

NETWORK:Network1AR-GATEWAYS:nmsbpx12PNNI-GATEWAYS:nmsmgx13DISCOVERY PROTOCOL:HYBRIDIP REACHABILITY FLAG:NWIP_ONOPTIONAL:"TIMEOUT = 7, RETRANSMIT = 6, THROTTLE = 0, ACKNOWLEDGE = 30, BLOCKSIZE = 1024"

Note Check that BPX nodes can be reached using Telnet and the BPX names (the names should get resolved to their IP addresses).


Network.conf File for Standalone Nodes

Note Specify this network, if and only if there are no other networks in network.conf

For standalone nodes the file has the following format.

NETWORK:Network1 (a name for CWM to identify the network)GATEWAYS:/dev/null/0(always specified as /dev/null/0)DISCOVERY PROTOCOL:AUTOROUTE (the discovery protocol, in this case always AUTOROUTE)IP REACHABILITY FLAG:NWIP_OFF (specifies in-band or out-of-band management)OPTIONAL:"TIMEOUT = 7, RETRANSMIT = 6, THROTTLE = 0, ACKNOWLEDGE = 30, BLOCKSIZE = 1024"

(the optional field is used to specify parameters if the desired value is different from the default value, see Table 3-5)

Check that the IP Reachability Flag is correct as shown in Table 3-4.



NWIP_ON For in-band management. All the CWM messages are sent to each destination node using the node’s nwip (atm_ip_address).







Table 3-5 provides a list of the optional parameters in the network.conf file.

Note In the table above, the default values must not be changed.

Sample Network 4: Discover a Standalone Node

Note Use only one Gateway per network in case of AutoRoute networks.

NETWORK:Network4GATEWAYS:/dev/null/0DISCOVERY PROTOCOL:AUTOROUTEIP REACHABILITY FLAG:NWIP_ONOPTIONAL:"TIMEOUT = 7, RETRANSMIT = 6, THROTTLE = 0, ACKNOWLEDGE = 30, BLOCKSIZE = 1024"



NWIP_ON For in-band management. All the CWM messages are sent to each destination node using the node's nwip(atm_ip_address).



Table 3-5 network.conf Optional Parameters

Parameter Name Default Value Description

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

RETRANSMIT 6 Link retry count. The number of times CWM will retransmit a message before it declares the link down.

THROTTLE 0 Download throttling timeout value.

ACKNOWLEDGE 30 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.

BLOCKSIZE 1024 Block size used for an Cisco IGX 8400, or Cisco BPX 8600 configuration upload.





CWM Gateway Configuration File

If the CWM workstation is to support 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 sgharatDomainGatewayList CWM1 CWM2 CWM3

In this example, CWM1, CWM2, and CWM3 are the names of the CWM gateways.

Note In Release 15 a new flag, called “DegradeMode”, has been added to the CWMgateway.conf file. This flag should be modified only if there are two or more CWMs in a domain.

The AutoSwitchOver flag must be ON and the DegradeMode flag must be OFF in the CWMGateway.conf to use this feature. The flag is read at the time of start up. Once the core is started, users cannot change this configuration. If users want to change this parameter, they must stop and restart the core. The default value for the flag DegradeMode is ON. The flag AutoSwitchOver is an existing flag that must be ON to trigger SwitchOver of CWM role in certain scenarios. The default value for the AutoSwitchOver flag is ON.

This flag can have 3 possible values, ON, OFF and CONDITIONAL_PRIMARY.If the flag is ON, the CWMGateway will become primary, if it detects connectivity failure with the Primary.

If the flag is OFF, the CWMGateway will be remain in secondary after primary reconnects.

If the flag is CONDITIONAL_PRIMARY, it eliminates the Degraded Mode of CWM operation when there is only one primary and one secondary in the domain. When secondary loses connectivity with primary, secondary switches its role to primary.

SCM Gateway Configuration File

If the CWM workstation has to support multiple SCM gateways, check the SCMGateway.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 SCMGateway.conf

Check the DomainGatewayList portion of this file.




## Default: DomainGatewayList## Usage: DomainGateWayList tmonda dilbag sgharatDomainGatewayList SCM1 SCM2 SCM3

In this example, SCM1, SCM2, and SCM3 are the names of the SCM gateways.

Under RedundantSCMList in the SCMGateway.conf file, list the workstation names of those SSM machines that form a redundant group.

Default: RedundantSCMList#### Usage: RedundantSCMList <hostname_1> <hostname_2> <hostname_3> ...#### Example: if cwm1, cwm2 are the StandAlone SSM's. And CWM0 is a cwm machine## then the Usage is as follows:#### RedundantSCMList cwm1 cwm2

Additional details on how to configure a Standalone Statistics Manager (SSM) using the SCMGateway.conf file are included in Appendix A.

CwmDomainGlobal.conf File

This file is used to enable or disable the connection descriptor feature that permits the user to attach an alphanumeric descriptor to a connection. The user should check the contents of the /usr/users/svplus/config/CwmDomainGlobal.conf file. If necessary, use vi or some other editor to set the flag to the correct value (0 for off, 1 for on).

DESCRIPTOR_FLAG = 00 means off1 means onThe connection descriptor string can contain any alphanumeric character and can be up to 64 characters (including spaces) in length.This flag is disabled by default.

Statsparser.config file

If the CWM server is also used to collect statistics using the Integrated Statistics Collection Manager, the configuration of the statistics parser module is performed through settings in the statsparser.conf file. In this file the user can specify the maximum number of threads, log details, database names, and fragmentation details.

The format of the statsparser.conf file and examples of parameter values are as follows.

################################################################################## statsparser configuration file ## This file lets you modify some of the behavior of the SCM Parser Server. ## ## The format of the commands is kind of flexible: ## <KEYWORD> parameter ## where ## KEYWORD is the property that is being set. ## parameter is the property value. ## Only the parameter must be changed. The KEYWORD MUST NEVER BE CHANGED. ## DO NOT PUT NUMBERS ON THE LINES EXCEPT WHERE THEY ARE REQUIRED. ## The valid ranges of each parameters can be derived from the description and




## value held by each parameter. ## ################################################################################# #MAX THREADS USED BY STATSPARSER # MAX_THREADS 32 # #LOG LEVELS # 1 - ALERT (Highest Priority messages - less no. of messages) # 3 - CRITICAL - Some critical error messages. # 6 - ERR( Shows only Exceptions and Errors) # 7 - Complete log - all messages. # LOG_LEVEL 6 # # Database name for config and meta data # DB_NAME statsdb # # Database name for stats data # DATA_DB_NAME statsdb # # Flag to use statsdb schema or stratacom db schema # 1 for statsdb schema & # 0 for stratacom db schema # Note that this is dependant on the DATA_DB_NAME defined above # USE_NEW_DB 1 # # Tables to be fragmented # FRAGMENTED_TABLES atm_conn_data|axsm_conn_data # # Interval for fragmentation (in hours) # FRAGMENTED_TABLE_INTERVAL 2

Cmgrd.conf File

The cmgrd.conf file is located in the /usr/users/svplus/config directory. This file contains a number of configurable parameters concerned with connection management.

In Release 15, a new configurable flag AUSM_DISCARD_OPTION was added to the cmgrd.conf file. This flag is for setting the handling of discarded AUSM frames. The settings of the flag are DISABLE (the default) or ENABLE.

If enabled, cmgrd sets ingressQDiscardOption for AUSM cards on all platforms to ‘frameDiscard’ if FGCRA is enabled on the card or sets it to ‘clpHysterisis’ if FGCRA is disabled on the card.

If disabled, cmgrd will not set ingressQDiscardOption parameter at all on the switch hence defaulted by switch always to ‘clpHysterisis’.

The format of the cmgrd.conf file is:

## Configuration file for Cmgrd## New parameters take effect if a USR1 signal is sent to cmgrd process## % kill -USR1 <cmgrd_pid>###### This applies only when mapping from Auto route FRSMs and only for non-abr## connections




##ATM_FR_OVERHEAD_FLAG ENABLE###### This configures the number of times to retry if a THROTTLE or## a NODE LOCK error happens##THROTTLE_NODE_LOCK_RETRY 1#### This configures the time to wait between retries## Should be specified in seconds##TIME_BETN_RETRY 3#### This configures the time cmgrd waits for every SNMP SET operation## before it declares a timeout## This only configures AR timeout## The value has to be in microsecondsSET_TIMEOUT 30000000#### This configures the time cmgrd waits for every SNMP SET operation## before it declares a timeout## This only configures PNNI timeout## The value has to be in microsecondsPNNI_SET_TIMEOUT 60000000#### This configures the egress %util and servicerate mapping for AUSM## If set to enable cmgrd will map egress values from other end## If set to disable user can explicitly set these values.EGRESS_AUSM_MAPPING ENABLE#### This configures the pnni per conn %util setting to be enabled or disabled.## If this flag is disabled, CWM will not set %util on any PNNI endpoint,## hence the switch default of 100% will be applied.##PNNI_PER_UTIL_FLAG ENABLE#### This configures the AUSM INGRESS Q DISCARD OPTION to frameDiscard on## all AUSM connections when atmEndPointFGCRA is enabled.## Set the foll. flag to ENABLE to have the above configuration.AUSM_DISCARD_OPTION DISABLE#### This configures the time until which cmgrd will wait before giving up## on a request. The time is specified in seconds.##MAX_REQUEST_TIME 300#### This configures whether cmgrd should do backoff on dbroker DoneAdd time## outs. If this is set to enable, cmgrd will not backoff the segments in## case of a dbroker timeout.## NOTE: This flag will NOT take effect for XPVC Segments.##NO_BACKOFF_ON_DBROKER_TIMEOUT DISABLE




CMSCClient.conf File

The SHOW_TOPO_VIEW flag is now located in the CMSCClient.conf file in the /usr/users/svplus/config directory. The permissible values of this flag are “true” (the default) and “false”. The flag is used by those customers who don't use the topology feature, and who want a faster start-up.

The portion of the CMSCClient.conf file that applies to SHOW_TOPO_VIEW is as follows:# Network Monitor show topo view feature.# if SHOW_TOPO_VIEW is true, graphical view in network monitor# will show up. if SHOW_TOPO_VIEW is false, graphical view# in network monitor will not show.SHOW_TOPO_VIEW true

Reserved Port IDs and User IDs

CWM uses a number of dedicated Unix port and user ids. These must be reserved for CWM and must not used by other programs. For this reason it is recommended that, except for those programs that function within the CWM system, such as HP OpenView, no other applications are installed in CWM workstations.

CWM Reserved Port IDs

CWM 15.1 to Cisco WAN switch (outgoing): ports used in the switch

udp: 161, snmp get/set udp: 69, tftp server tcp: 23, telnet tcp: 13, daytimetcp, udp: 1099

Cisco WAN switch to CWM 15.1 (incoming): ports used in CWM 15.1

udp: 162, snmp trap tcp: 8888, HP OV topology daemon tcp: 9999, HP OV database daemon

Operations Support System (OSS) to CWM 15.1 (incoming): ports used in CWM 15.1

udp: 8161, snmpAgent

This port is configurable. Please refer to the Cisco WAN Manager SNMP Service Agent Guide for configuring this port to other than 8161

CWM15 (Internal) Process to Process Communication ports

CWM processes' ports 9000 to 9011 Web Services (Java Client) 1551Orbix ports 3075,3079,3094

CWM Reserved User IDs

In order for CWM and the SSC and SSM applications to operate correctly, certain user IDs must be available for use by the Informix database. The user IDs listed below should be reserved so that they are not taken by other (non-CWM) applications.




The following user IDs should be reserved for CWM installation:

userids 271, 272

The following user IDs should be reserved for SSM installation:

userids 270, 271, 272

The following user IDs should be reserved for SSC installation:

userids 270, 271

The following user ID should be reserved for WANDEST client:

userid 272

The impact when these userids are taken by other applications is that svplus/wandest/informix users will not get created and subsequent references to those userids will fail.

Ensuring the Creation of the svplus and/or wandest Username and Password

When either the SSM, the SSC, or the WANDEST server or client is installed for the first time on your Solaris workstation, the svplus and/or wandest username and password may not be available. After installing any of these applications, log in as root and set the unix password(s) for the svplus and/or wandest user using either the admintool or using the passwd command on the command line as root(e.g., “passwd svplus”).

Equipment Manager (EM) support for Preferred Route StatusCWM Release 15 introduced a new component called EMEX (process name “emex”). EMEX manages the syncing up of the preferred route status data of managed switches for those nodes that support preferred route. Currently, the supported node types are MGX 8850(PXM1E), MGX8830, MGX 8850(PXM45), and MGX 8950)

EMEX is started as a standalone process and is managed by watchdog after the CWM machine has been cold-started or warm-started.

After EMEX has been started, EMEX queries the “node” DB table for newly discovered nodes and checks the “mode” field from the table. If the “mode” is 2, 3, 4, or 5, a first time resync is started. After the first time resync, periodic resyncs for the same node will be scheduled automatically.

In the config file “emex.conf” which is stored in “/usr/users/svplus/config”, the default resync time is 6 hours. The next resync time is 6 hours after the first time node resync.

The user can cause a resync to start manually and can configure the period between resyncs through a new CLI connRouteResync command performed at the CWM server machine. The syntax for this command is:

connRouteResync command [command-arguments]

There are two forms of this command, namely:

connRouteResync start [command-arguments], starts a preferred route status resync.

connRouteResync config [command-arguments], used to configure preferred route resync parameters.




connRouteResync start command

This command has the following syntax.

connRouteResync start [command-arguments]

where [command-arguments] can be:

-h Display argument options

-a ip where ip is in the format of nnn.nnn.nnn.nnn

-a all where ‘all’ signifies resync of all applicable nodes in network.

-n name where name is the name of the node in network

-n all where ‘all’ signifies resync of all applicable nodes in network.

When this command is executed, a confirmation is displayed on the console. An example of such a message is:

EMEX receives client request: Operation:resync Node:all IP: Resync_Time:0 s

connRouteResync config command

This command has the following syntax.

connRouteResync config [command-arguments]

where [command-arguments] can be:

where [command-arguments] can be

-h Display argument options

-t resync_time where resync_time is in the unit of second

When this command is executed, a confirmation is displayed on the console. An example of such a message is:

EMEX receives client request: Operation:config Node: IP: Resync_Time:3600

installing cwm server software - · pdf filestep 2 insert the cisco wan ... the user can...

Documents