Cisco WANDEST Installation and Configuration Guide, 2.5 - Installation and Startup [Cisco WAN Manager]

Table Of Contents

Installation and Startup

Installing the WANDEST Server

Platform Requirements

Enabling WANDEST Table Selection

Running the Install Program

Installshield GUI Installation

License Agreement Acceptance

WANDEST Server Installation without Disk-Stripping [Meta-devices] for Database Partitions

WANDEST Server Installation with Disk-Stripping [Meta-devices] for Database Partitions

Selecting the Raw Partitions

Choosing between the rootdbs or the datadbs Databases

Selecting an Alternate Database

Completing the Installation

Running the Uninstall Program

Installing the WANDEST Client

Platform Requirements

Running the WANDEST Client Install Program

Installshield GUI Installation

License Agreement Acceptance

Setting Up Client Communication With the WANDEST Server

Completing the Installation

Running the Uninstall Program

Starting the WANDEST Server

Starting the WANDEST Client

Modifying the Client Password

Installation and Startup

This chapter describes the installation for the WANDEST server and the WANDEST client. The WANDEST Release 2.5 software is provided on two separate CDs. Each CD is ordered separately.

•WANDEST Release 2.5 Server CD

–WANDEST Server Software, Release 2.5

•WANDEST Release 2.5 Client CD

–WANDEST Client Software, Release 2.5

Caution Before beginning your installation, ensure that there is adequate disk space by executing the
/usr/bin/df -k /usr/users command. Examine the Capacity column. If it is 100% full, then you will have to take action to free up some disk space.

Note If an existing WANDEST server is found during a CWM installation, the WANDEST server can be preserved and not need to be re-installed. However, if the stratacom database schema is changed during a CWM upgrade or patching, the WANDEST server must be re-installed on the CWM host. The client does not need to be re-installed, but the control file from the re-installed server must be updated.

Installing the WANDEST Server

This section describes how to install the WANDEST server. It consists of the following prerequisites and procedures:

•Platform Requirements

•Enabling WANDEST Table Selection

•Running the Install Program

•License Agreement Acceptance

•WANDEST Server Installation without Disk-Stripping [Meta-devices] for Database Partitions

•WANDEST Server Installation with Disk-Stripping [Meta-devices] for Database Partitions

•Selecting the Raw Partitions

•Choosing between the rootdbs or the datadbs Databases

•Completing the Installation

Platform Requirements

To successfully install the WANDEST server, the following programs must be loaded and running (unless otherwise noted):

•Solaris 8 (with the 108523-23 patch cluster installed)

•CWM 15—installed but not running

Note If the WANDEST server is installed on a CWM machine where the CWM core has been started, stop the CWM core. After loading all the files, the WANDEST server installation does a coldstart -F of the wandest database. To ensure that the tables in the CWM databases are up-to-date, you may want to coldstart CWM by executing the coldstart command after stopping the CWM core and ensuring that your existing data is backed up as described in the Cisco WAN Manager Database Interface Guide. The CWM core must be completely stopped before installing the WANDEST server.

•Informix 9.21.UC7XH

Enabling WANDEST Table Selection

The default WANDEST installation creates triggers and procedures for every table in the stratacom database. You may not need to have the WANDEST application access all of the tables in the stratacom database. This release of WANDEST has been enhanced to allow you to select only the tables you need.

To enable this feature, run the script /usr/users/svplus/scripts/get_dbschema.ksh before installing the WANDEST server.

Complete the following steps:

Step 1 Stop the wdclient.

Step 2 Exit root

Step 3 Run the /usr/users/svplus/scripts/get_dbschema.ksh script as shown below:
% cd /usr/users/svplus/scripts
% ./get_dbschema.ksh
A wd_dbschema_tmpl file is created in /usr/users/svplus/tmp directory.  Edit this file and 
un-comment out the tables that you want triggers in it.
Step 4 In order to select which tables you want triggers to be planted, enter the vi editor:
% cd /usr/users/svplus/tmp
% vi wd_dbschema_tmpl
The contents of the wd_dbschema_tmpl file displays:
                 # maintlog
                 # sv_system
                 # network
                 # cwm_info
                 # user_info
                 # node_parent
                 # sec_profile
                 # scmcardenable
                 # node
                 # xlmi
                 # packet_line
Step 5 Remove the leading # character from each line that contains a table that needs triggers and procedures.

After you have edited and saved the template file, only those tables you un-commented will have triggers and procedures on the stratacom database.

Note The WANDEST database will create every table present in the stratacom database but after you edit the wd_dbschema_tmpl file triggers and procedures will be planted only on those tables in the database you selected.

Running the Install Program

To install the WANDEST server, complete the following steps.

Step 1 Log in as superuser.
% su
Step 2 Place the WANDEST Server CD into the CD-ROM drive.

Step 3 Change to the /cdrom/cdromwdserver directory.
# cd /cdrom/cdromwdserver
Step 4 At the command line prompt enter the following command:
# ./InstallWDServer.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 5 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, you can install WANDEST using an alpha-numeric terminal or a PC in terminal emulator mode. For a general overview of how to use Console Mode Install, refer to the Console Mode Installation section in the Installing CWM Server Software chapter of the Cisco WAN Manager Installation Guide, Release 15.

Installshield GUI Installation

After responding No to the question in Step 5, above, the installation classes are loaded: this process takes several minutes.

License Agreement Acceptance

Step 1 After the installation classes are loaded the WANDEST Installation Welcome window is displayed, as shown in Figure 5-1.

Figure 5-1 Welcome Window

Step 2 From the Welcome window, click Next to continue the installation

Step 3 The Agreement for Software License window is displayed, as shown in Figure 5-2.

Figure 5-2 License Agreement Window (default)

Step 4 Read and review the license agreement text in Figure 5-2.

Step 5 From the Agreement for Software License window, select your acceptance by clicking the I accept the terms of the license agreement radio button, as shown in Figure 5-3.

Figure 5-3 License Agreement Window (accept terms of the agreement selected)

Step 6 Click Next on the License Agreement window to continue the installation.

The Choose Meta Devices window (Figure 5-4) appears.

Step 7 Continue on to the "WANDEST Server Installation without Disk-Stripping [Meta-devices] for Database Partitions" section.

WANDEST Server Installation without Disk-Stripping [Meta-devices] for Database Partitions

Once you have clicked Next on the License Agreement window (Figure 5-3), the Choose Meta Devices window appears. See Figure 5-4.

Figure 5-4 Meta-Devices Window (default selected)

The default selection is No.

Step 1 If you do not use meta devices, click Next on the Meta-Devices window to continue.

Go to the "Choosing between the rootdbs or the datadbs Databases" section to continue installing the software.

Step 2 If you have decided to use Disk-stripping [Meta-devices] for database partitions, go to the "WANDEST Server Installation with Disk-Stripping [Meta-devices] for Database Partitions" section.

WANDEST Server Installation with Disk-Stripping [Meta-devices] for Database Partitions

Step 1 If you have decided to use Disk-stripping [Meta-devices] for database partitions, select Yes in the Meta-Devices window by clicking the Yes checkbox, as shown in Figure 5-5.

Figure 5-5 Meta Devices Window (Meta Device Use Selected)

Step 2 With the Yes selection highlighted, as shown in Figure 5-5, click Next on the Meta-Devices window to continue.

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 other than that provided in Solaris (for example, Veritas).

Once you have selected Yes (I use Disk-stripping [Meta-devices] for database partitions) and clicked Next on the Meta-Devices window to continue, the Configure the Meta Device Path and the Raw Partition Size for the WANDEST Database window is displayed, as shown in Figure 5-6.

Figure 5-6 Configure the Meta Device Path and the Raw Partition Size for the WANDEST Database Window

Step 3 Enter the path to the meta device in the first field.

Step 4 Enter the size of the meta device in megabytes in the second field.

For an example of the type of information to enter in these fields, refer to the sample Configure the Meta Device Path and the Raw Partition Size window shown in Figure 5-7.

Figure 5-7 Configure the Meta Device Path and the Raw Partition Size (with Path & Size Information)

Step 5 Once you have filled in the appropriate information in the path and size fields, and the screen looks similar to the example in Figure 5-7, click Next on the Meta Device Path and the Raw Partition Size window to continue.

The Select the Raw Partition for WANDEST Database window is displayed, as shown in Figure 5-8.

Step 6 Go to the "Selecting the Raw Partitions" section to continue installing the software.

Selecting the Raw Partitions

This section describes the process for choosing the raw partitions used for the applicable database used by WANDEST.

At the beginning of this process, the Select the Raw Partition for WANDEST Database window is displayed, as shown in Figure 5-8.

Figure 5-8 Select the Raw Partition for WANDEST Database Window (Default Settings Shown)

This window displays only those raw partitions available to Informix.

Step 1 Select the appropriate raw partition to be used by clicking on the radio button. For example, selecting the second radio button causes the second raw partition to be highlighted, as shown in Figure 5-9.

Figure 5-9 Select the Raw Partition for WANDEST Database Window (Second Partition Selected)

Step 2 Click Next to finish the installation.

The Install Location Confirmation window (Figure 5-13) is displayed.

Step 3 Continue to the "Completing the Installation" section to wrap up the installation.

Choosing between the rootdbs or the datadbs Databases

This process is only triggered if you do not use meta devices.

After accepting the default (no meta devices) in the Meta-Devices window and you have clicked Next to continue, the Choosing Which Database to Install WANDEST in window displays, as shown in Figure 5-10.

Figure 5-10 Choosing Which Database to Install WANDEST in Window (default - No, do not choose)

The default selection is No.

Step 4 If you do not want to choose between rootdbs or datadbs, click Next.

The Select the Raw Partition for WANDEST window is displayed, as shown in Figure 5-8.

Step 5 Go to the "Selecting the Raw Partitions" section to continue installing the software.

Selecting an Alternate Database

If you want to choose between rootdbs or datadbs, complete the following procedure.

Step 1 In the Choosing Which Database to Install WANDEST in window, as shown in Figure 5-10, click the radio button next to Yes (See Figure 5-11)

Figure 5-11 Choosing Which Database to Install WANDEST in Window (yes, I want to choose selected)

Step 2 Click Next to continue the process.

The Choosing between rootdbs and datadbs window opens. See Figure 5-12.

Step 3 Click on the appropriate radio button to choose either rootdbs or datadbs. See Figure 5-12.

Figure 5-12 Choosing between rootdbs and datadbs Window (datadbs selected)

Step 4 Click Next to accept your choice.

The Install Location Confirmation window (Figure 5-13) is displayed.

Continue to the "Completing the Installation" section to wrap up the installation.

Completing the Installation

This section describes the steps needed to complete the WANDEST client installation. It consists of the following:

•Confirm the choices made in the previous sections, and possibly go back to change them.

•Begin the installation of files from the WANDEST client CD to the appropriate locations on the client workstation.

•Monitoring the Installation Log file as it configures the database tables.

Step 1 After you have completed all the appropriate configuration tasks in the previous sections, The Install Location Confirmation window (Figure 5-13) is displayed.

Figure 5-13 Install Location Confirmation Window

Step 2 If the information in the Confirmation window is not correct, click Back to the appropriate window and correct the applicable settings.

Step 3 Clicking cancel will abort the installation.

Step 4 If the information in the Confirmation window is correct, and you are ready to load the files from the CD onto your workstation, click Next.

Step 5 When Next is clicked, the Installation Progress Window is displayed as shown in Figure 5-14.

The Installing Progress window (Figure 5-14) shows the progress of the files being extracted, and the progress of the database creation and configuration process.

Figure 5-14 Installing Progress Window

As the installation process begins configuring database tables an Installation Log Window (Figure 5-15) opens.

Figure 5-15 Installation Log Window

Once the database is completely configured, the Installation Log Window (Figure 5-15) and the Installing progress window (Figure 5-14) automatically shut down and the Installation Complete window (Figure 5-16) displays.

Figure 5-16 Installation Complete Window

Step 6 In the Installation Complete window, click Finish.

Step 7 Copy the wdclient.ctrl file from the server onto the client machine.

Warning The WANDEST client does NOT operate without this control file. The WANDEST client
ships with a default control file that matches CWM 15. It is recommended that the control file is transferred via FTP from the WANDEST server machine: /usr/users/wandest/wdclient.ctrl. The file on the server has been generated to match
the CWM database schema on the server.

Running the Uninstall Program

An uninstall program is included in the WANDEST server installation. To uninstall the WANDEST server, complete the following steps.

Step 1 Log in as superuser.

Step 2 Change the directory to /usr/users/wandest.

Step 3 At the prompt enter the following script:
host% ./UnInstallWDServer.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 Uninstaller in Console Mode? (Yes / No): [No]:y
Step 4 Respond No to continue uninstalling WANDEST using the Installshield GUI.
Respond Yes to continue uninstalling WANDEST 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, you can uninstall WANDEST using an alpha-numeric terminal or a PC in terminal emulator mode. To uninstall using Console Mode, follow the instructions as they are displayed on the screen. For a general overview of how to use Console Mode Install, refer to the Console Mode Installation section in the Installing CWM Server Software chapter of the Cisco WAN Manager Installation Guide, Release 15.

Step 5 After responding No to the question in Step 4, the WANDEST Uninstaller window opens.
All the files and directories will be removed without any intervention on your part. Once the process finishes, click the Finish button to exit the Installshield GUI.

Installing the WANDEST Client

This section describes how to install the WANDEST client. It consists of the following prerequisites and procedures:

•Platform Requirements

•Running the Install Program

•License Agreement Acceptance

•Setting Up Client Communication With the WANDEST Server

•Completing the Installation

Platform Requirements

The following requirements are needed on the workstation to successfully install the WANDEST client:

•Solaris 8 (with the 108523-23 patch cluster installed)

Running the WANDEST Client Install Program

Complete the following steps to install the WANDEST client. Multiple clients can be installed on the same workstation. For information on multiple clients, see "WANDEST Client."

Step 1 Log in as superuser.

Step 2 Load the CD-ROM.

Step 3 Change to the /cdrom/cdromWDclient directory.

Step 4 At the command line prompt enter the following command:
host% ./installWDClient.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 5 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, you can install WANDEST using an alpha-numeric terminal or a PC in terminal emulator mode. For a general overview of how to use Console Mode Install, refer to the Console Mode Installation section in the Installing CWM Server Software chapter of the Cisco WAN Manager Installation Guide, Release 15.

Installshield GUI Installation

After responding No to the question in Step 5, above, the installation classes are loaded: this process takes several minutes.

License Agreement Acceptance

Step 1 After the installation classes are loaded the WANDEST Client Installation Welcome window is displayed, as shown in Figure 5-17.

Figure 5-17 Welcome Window

Step 2 From the Welcome window, click Next.

The WANDEST Client License Agreement window is displayed, as shown in Figure 5-18.

Figure 5-18 License Agreement Window

Step 3 From the Agreement for Software License window, click I accept the terms of the license agreement.

Step 4 Click Next.

The WANDEST FTP Information Window is displayed, as shown in Figure 5-19.

Step 5 Continue to the "Setting Up Client Communication With the WANDEST Server" section.

Setting Up Client Communication With the WANDEST Server

After accepting the terms of the license agreement in the previous section, the next step is to set up your FTP User. Configuring passwords for the WANDEST FTP user is accomplished in the WANDEST FTP Information Window, as shown in Figure 5-19.

Figure 5-19 WANDEST FTP Information Window

Step 1 At the WANDEST FTP Information window, enter the password of the user on the machine in the FTP Password field and then reenter the same password to confirm in the ReEnter the Password field.

Note In this release, the user name of "wandest" must be used as the FTP user name and cannot be changed.

Step 2 After entering the FTP password in both fields, click Next.

The Domain Name Used by Orbix window (Figure 5-20) is displayed.

Figure 5-20 Domain Name Used by Orbix

Step 3 In the Domain Name Used by Orbix window (Figure 5-20), enter the domain name to be used by Orbix.

You can also choose to leave the domain name blank.

Step 4 Click Next.

The Choose the Output Directory and the Archive Directory window is displayed, as shown in Figure 5-21.

Figure 5-21 Choose the Output Directory and the Archive Directory Window

Step 5 If the default directory names in the Choose the Output Directory and the Archive Directory window are acceptable to you, click Next.

If you want to change the default directory names, complete the following steps:

Step 6 Enter the path for the output directory in the first field.

Step 7 Enter the path for the archive directory in the second field.

After you click Next to accept the default directories or the ones you entered, the Install Location Confirmation window (Figure 5-22) is displayed. Continue to the "Completing the Installation" section to wrap up the installation.

Completing the Installation

This section describes the steps needed to complete the WANDEST client installation. It consists of the following:

•Confirm the choices made in the previous sections, and possibly go back to change them.

•Begin the installation of files from the WANDEST client CD to the appropriate locations on the client workstation.

•Monitoring the Installation Log file as it configures the database tables.

Figure 5-22 Install Location Confirmation Window

Step 8 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 applicable settings.

Step 9 When Next is clicked, the Installation Progress Window is displayed as shown in Figure 5-23.

The Installing Progress window (Figure 5-23) shows the progress of the files being extracted, and the progress of the database creation and configuration process.

Figure 5-23 Installing Progress Window

As the installation process begins configuring database tables an Installation Log Window (Figure 5-24) opens.

Figure 5-24 Installation Log Window

Once the database is completely configured, the Installation Log Window (Figure 5-24) and the Installing progress window (Figure 5-23) automatically shut down and the Installation Complete window (Figure 5-25) displays.

Figure 5-25 Installation Complete Window

Step 10 In the Installation Complete window, click Finish.

The client installation program creates the client Configuration file, /usr/users/wandest/client/wdconfig.conf, based upon inputs during installation.

Note The installation program supplies a default Control file. The WANDEST client can be started using the default Control file. However, you should use the FTP protocol to copy the control file from the WANDEST server machine /usr/users/wandest/wdclient.ctrl, which has been generated to match the CWM database schema on the server. The Control file for WANDEST can be edited to capture only certain data. See "WANDEST Client."

Ensuring the Creation of the wandest Username and Password

A user with the default ID and password of wandest is created during the client installation.

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

To change an existing password, complete the steps listed in Modifying the Client Password.

Caution The wandest password needs to be set only on the client machine.

Running the Uninstall Program

An uninstall program is included in the WANDEST client installation. To uninstall the WANDEST client, complete the following steps.

Step 1 Log in as superuser.

Step 2 Change to the /usr/users/wandest directory.

Step 3 At the prompt enter the following script:
host% ./UnInstallWDClient
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 Uninstaller in Console Mode? (Yes / No): [No]:y
Step 4 Respond No to continue uninstalling WANDEST using the Installshield GUI.
Respond Yes to continue uninstalling WANDEST 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, you can uninstall WANDEST using an alpha-numeric terminal or a PC in terminal emulator mode. To uninstall using Console Mode, follow the instructions as they are displayed on the screen. For a general overview of how to use Console Mode Install, refer to the Console Mode Installation section in the Installing CWM Server Software chapter of the Cisco WAN Manager Installation Guide, Release 15.

Step 5 After responding No to the question in Step 5, the WANDEST Uninstaller window opens.
All the files and directories will be removed without any intervention on your part. Once the process finishes, click the Finish button to exit the Installshield GUI.

Starting the WANDEST Server

After installation, the WANDEST server becomes part of the CWM startup process. The WANDEST server starts upon execution of the command to start CWM. For information on starting CWM, refer to the Cisco WAN Manager User's Guide, Release 15.

Starting the WANDEST Client

To start the WANDEST client, complete the following steps:

Step 1 Log in as wandest.

Step 2 To start the client, enter the following command:
host% wdclient <serverworkstationname> <socket port number>
The client is not yet connected to the server.

Step 3 From either the OSS application or the Admin Utility, enter the start command to connect the client to the server.

The WANDEST client is now connected to the WANDEST server.

Modifying the Client Password

A user with ID wandest is created during the WANDEST client installation. The default password created by the installation is also wandest. The password is encrypted and stored on the client configuration file. This password is not exported in any WANDEST database or log file.

Caution Each time the client password is changed, the wdupdate utility program must be invoked to update the new password. Otherwise, WANDEST does not function properly.

To change the client password, complete the following steps:

Step 1 Stop any running wdclient or wdadmin program on the client host.

Step 2 To modify the password, use a password management utility. For example:
host% passwd wandest
The password must be 5-20 characters. Only a subset of ASCII characters can be included in the password.

Step 3 At the prompt, enter the new password. Reenter it when prompted.

Step 4 Execute the wdupdate utility program with the new password as input.
host% /usr/users/wandest/bin/wdupdate <new password> <wdconfig.conf file>
The wdupdate utility modifies the following default config file with the encrypted version of the new, input password: /usr/users/wandest/client/config/wdconfig.conf

If a different configuration file is used, the full path and file name of this configuration file needs to be input to the wdupdate program. Otherwise the correct password is not modified, and the WANDEST client/server communication cannot function.

For example, if the new password is <newpwd> and the configuration file is: /usr/users/myname/somewhere/wdconfig.conf, the command line to invoke the wdupdate program is:
host% /usr/users/wandest/bin/wdupdate <newpwd> /usr/users/myname/somewhere/wdconfig.conf

	Cisco WANDEST Installation and Configuration Guide, 2.5
	Installation and Startup
Cisco WANDEST Installation and Configuration Guide, 2.5 About This Guide Introduction WANDEST Server WANDEST Client About the Data Files Installation and Startup Exceptions and Errors Server IDL Interface Definition	Download this chapter Installation and Startup Download the complete book PDF Copy of the Cisco WANDEST Installation & Reference, Release 2.5 (PDF - 2 MB) Table Of Contents Installation and Startup Installing the WANDEST Server Platform Requirements Enabling WANDEST Table Selection Running the Install Program Installshield GUI Installation License Agreement Acceptance WANDEST Server Installation without Disk-Stripping [Meta-devices] for Database Partitions WANDEST Server Installation with Disk-Stripping [Meta-devices] for Database Partitions Selecting the Raw Partitions Choosing between the rootdbs or the datadbs Databases Selecting an Alternate Database Completing the Installation Running the Uninstall Program Installing the WANDEST Client Platform Requirements Running the WANDEST Client Install Program Installshield GUI Installation License Agreement Acceptance Setting Up Client Communication With the WANDEST Server Completing the Installation Running the Uninstall Program Starting the WANDEST Server Starting the WANDEST Client Modifying the Client Password Installation and Startup This chapter describes the installation for the WANDEST server and the WANDEST client. The WANDEST Release 2.5 software is provided on two separate CDs. Each CD is ordered separately. •WANDEST Release 2.5 Server CD –WANDEST Server Software, Release 2.5 •WANDEST Release 2.5 Client CD –WANDEST Client Software, Release 2.5 Caution Before beginning your installation, ensure that there is adequate disk space by executing the /usr/bin/df -k /usr/users command. Examine the Capacity column. If it is 100% full, then you will have to take action to free up some disk space. Note If an existing WANDEST server is found during a CWM installation, the WANDEST server can be preserved and not need to be re-installed. However, if the stratacom database schema is changed during a CWM upgrade or patching, the WANDEST server must be re-installed on the CWM host. The client does not need to be re-installed, but the control file from the re-installed server must be updated. Installing the WANDEST Server This section describes how to install the WANDEST server. It consists of the following prerequisites and procedures: •Platform Requirements •Enabling WANDEST Table Selection •Running the Install Program •License Agreement Acceptance •WANDEST Server Installation without Disk-Stripping [Meta-devices] for Database Partitions •WANDEST Server Installation with Disk-Stripping [Meta-devices] for Database Partitions •Selecting the Raw Partitions •Choosing between the rootdbs or the datadbs Databases •Completing the Installation Platform Requirements To successfully install the WANDEST server, the following programs must be loaded and running (unless otherwise noted): •Solaris 8 (with the 108523-23 patch cluster installed) •CWM 15—installed but not running Note If the WANDEST server is installed on a CWM machine where the CWM core has been started, stop the CWM core. After loading all the files, the WANDEST server installation does a coldstart -F of the wandest database. To ensure that the tables in the CWM databases are up-to-date, you may want to coldstart CWM by executing the coldstart command after stopping the CWM core and ensuring that your existing data is backed up as described in the Cisco WAN Manager Database Interface Guide. The CWM core must be completely stopped before installing the WANDEST server. •Informix 9.21.UC7XH Enabling WANDEST Table Selection The default WANDEST installation creates triggers and procedures for every table in the stratacom database. You may not need to have the WANDEST application access all of the tables in the stratacom database. This release of WANDEST has been enhanced to allow you to select only the tables you need. To enable this feature, run the script /usr/users/svplus/scripts/get_dbschema.ksh before installing the WANDEST server. Complete the following steps: Step 1 Stop the wdclient. Step 2 Exit root Step 3 Run the /usr/users/svplus/scripts/get_dbschema.ksh script as shown below: % cd /usr/users/svplus/scripts % ./get_dbschema.ksh A wd_dbschema_tmpl file is created in /usr/users/svplus/tmp directory. Edit this file and un-comment out the tables that you want triggers in it. Step 4 In order to select which tables you want triggers to be planted, enter the vi editor: % cd /usr/users/svplus/tmp % vi wd_dbschema_tmpl The contents of the wd_dbschema_tmpl file displays: # maintlog # sv_system # network # cwm_info # user_info # node_parent # sec_profile # scmcardenable # node # xlmi # packet_line Step 5 Remove the leading # character from each line that contains a table that needs triggers and procedures. After you have edited and saved the template file, only those tables you un-commented will have triggers and procedures on the stratacom database. Note The WANDEST database will create every table present in the stratacom database but after you edit the wd_dbschema_tmpl file triggers and procedures will be planted only on those tables in the database you selected. Running the Install Program To install the WANDEST server, complete the following steps. Step 1 Log in as superuser. % su Step 2 Place the WANDEST Server CD into the CD-ROM drive. Step 3 Change to the /cdrom/cdromwdserver directory. # cd /cdrom/cdromwdserver Step 4 At the command line prompt enter the following command: # ./InstallWDServer.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 5 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, you can install WANDEST using an alpha-numeric terminal or a PC in terminal emulator mode. For a general overview of how to use Console Mode Install, refer to the Console Mode Installation section in the Installing CWM Server Software chapter of the Cisco WAN Manager Installation Guide, Release 15. Installshield GUI Installation After responding No to the question in Step 5, above, the installation classes are loaded: this process takes several minutes. License Agreement Acceptance Step 1 After the installation classes are loaded the WANDEST Installation Welcome window is displayed, as shown in Figure 5-1. Figure 5-1 Welcome Window Step 2 From the Welcome window, click Next to continue the installation Step 3 The Agreement for Software License window is displayed, as shown in Figure 5-2. Figure 5-2 License Agreement Window (default) Step 4 Read and review the license agreement text in Figure 5-2. Step 5 From the Agreement for Software License window, select your acceptance by clicking the I accept the terms of the license agreement radio button, as shown in Figure 5-3. Figure 5-3 License Agreement Window (accept terms of the agreement selected) Step 6 Click Next on the License Agreement window to continue the installation. The Choose Meta Devices window (Figure 5-4) appears. Step 7 Continue on to the "WANDEST Server Installation without Disk-Stripping [Meta-devices] for Database Partitions" section. WANDEST Server Installation without Disk-Stripping [Meta-devices] for Database Partitions Once you have clicked Next on the License Agreement window (Figure 5-3), the Choose Meta Devices window appears. See Figure 5-4. Figure 5-4 Meta-Devices Window (default selected) The default selection is No. Step 1 If you do not use meta devices, click Next on the Meta-Devices window to continue. Go to the "Choosing between the rootdbs or the datadbs Databases" section to continue installing the software. Step 2 If you have decided to use Disk-stripping [Meta-devices] for database partitions, go to the "WANDEST Server Installation with Disk-Stripping [Meta-devices] for Database Partitions" section. WANDEST Server Installation with Disk-Stripping [Meta-devices] for Database Partitions Step 1 If you have decided to use Disk-stripping [Meta-devices] for database partitions, select Yes in the Meta-Devices window by clicking the Yes checkbox, as shown in Figure 5-5. Figure 5-5 Meta Devices Window (Meta Device Use Selected) Step 2 With the Yes selection highlighted, as shown in Figure 5-5, click Next on the Meta-Devices window to continue. 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 other than that provided in Solaris (for example, Veritas). Once you have selected Yes (I use Disk-stripping [Meta-devices] for database partitions) and clicked Next on the Meta-Devices window to continue, the Configure the Meta Device Path and the Raw Partition Size for the WANDEST Database window is displayed, as shown in Figure 5-6. Figure 5-6 Configure the Meta Device Path and the Raw Partition Size for the WANDEST Database Window Step 3 Enter the path to the meta device in the first field. Step 4 Enter the size of the meta device in megabytes in the second field. For an example of the type of information to enter in these fields, refer to the sample Configure the Meta Device Path and the Raw Partition Size window shown in Figure 5-7. Figure 5-7 Configure the Meta Device Path and the Raw Partition Size (with Path & Size Information) Step 5 Once you have filled in the appropriate information in the path and size fields, and the screen looks similar to the example in Figure 5-7, click Next on the Meta Device Path and the Raw Partition Size window to continue. The Select the Raw Partition for WANDEST Database window is displayed, as shown in Figure 5-8. Step 6 Go to the "Selecting the Raw Partitions" section to continue installing the software. Selecting the Raw Partitions This section describes the process for choosing the raw partitions used for the applicable database used by WANDEST. At the beginning of this process, the Select the Raw Partition for WANDEST Database window is displayed, as shown in Figure 5-8. Figure 5-8 Select the Raw Partition for WANDEST Database Window (Default Settings Shown) This window displays only those raw partitions available to Informix. Step 1 Select the appropriate raw partition to be used by clicking on the radio button. For example, selecting the second radio button causes the second raw partition to be highlighted, as shown in Figure 5-9. Figure 5-9 Select the Raw Partition for WANDEST Database Window (Second Partition Selected) Step 2 Click Next to finish the installation. The Install Location Confirmation window (Figure 5-13) is displayed. Step 3 Continue to the "Completing the Installation" section to wrap up the installation. Choosing between the rootdbs or the datadbs Databases This process is only triggered if you do not use meta devices. After accepting the default (no meta devices) in the Meta-Devices window and you have clicked Next to continue, the Choosing Which Database to Install WANDEST in window displays, as shown in Figure 5-10. Figure 5-10 Choosing Which Database to Install WANDEST in Window (default - No, do not choose) The default selection is No. Step 4 If you do not want to choose between rootdbs or datadbs, click Next. The Select the Raw Partition for WANDEST window is displayed, as shown in Figure 5-8. Step 5 Go to the "Selecting the Raw Partitions" section to continue installing the software. Selecting an Alternate Database If you want to choose between rootdbs or datadbs, complete the following procedure. Step 1 In the Choosing Which Database to Install WANDEST in window, as shown in Figure 5-10, click the radio button next to Yes (See Figure 5-11) Figure 5-11 Choosing Which Database to Install WANDEST in Window (yes, I want to choose selected) Step 2 Click Next to continue the process. The Choosing between rootdbs and datadbs window opens. See Figure 5-12. Step 3 Click on the appropriate radio button to choose either rootdbs or datadbs. See Figure 5-12. Figure 5-12 Choosing between rootdbs and datadbs Window (datadbs selected) Step 4 Click Next to accept your choice. The Install Location Confirmation window (Figure 5-13) is displayed. Continue to the "Completing the Installation" section to wrap up the installation. Completing the Installation This section describes the steps needed to complete the WANDEST client installation. It consists of the following: •Confirm the choices made in the previous sections, and possibly go back to change them. •Begin the installation of files from the WANDEST client CD to the appropriate locations on the client workstation. •Monitoring the Installation Log file as it configures the database tables. Step 1 After you have completed all the appropriate configuration tasks in the previous sections, The Install Location Confirmation window (Figure 5-13) is displayed. Figure 5-13 Install Location Confirmation Window Step 2 If the information in the Confirmation window is not correct, click Back to the appropriate window and correct the applicable settings. Step 3 Clicking cancel will abort the installation. Step 4 If the information in the Confirmation window is correct, and you are ready to load the files from the CD onto your workstation, click Next. Step 5 When Next is clicked, the Installation Progress Window is displayed as shown in Figure 5-14. The Installing Progress window (Figure 5-14) shows the progress of the files being extracted, and the progress of the database creation and configuration process. Figure 5-14 Installing Progress Window As the installation process begins configuring database tables an Installation Log Window (Figure 5-15) opens. Figure 5-15 Installation Log Window Once the database is completely configured, the Installation Log Window (Figure 5-15) and the Installing progress window (Figure 5-14) automatically shut down and the Installation Complete window (Figure 5-16) displays. Figure 5-16 Installation Complete Window Step 6 In the Installation Complete window, click Finish. Step 7 Copy the wdclient.ctrl file from the server onto the client machine. Warning The WANDEST client does NOT operate without this control file. The WANDEST client ships with a default control file that matches CWM 15. It is recommended that the control file is transferred via FTP from the WANDEST server machine: /usr/users/wandest/wdclient.ctrl. The file on the server has been generated to match the CWM database schema on the server. Running the Uninstall Program An uninstall program is included in the WANDEST server installation. To uninstall the WANDEST server, complete the following steps. Step 1 Log in as superuser. Step 2 Change the directory to /usr/users/wandest. Step 3 At the prompt enter the following script: host% ./UnInstallWDServer.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 Uninstaller in Console Mode? (Yes / No): [No]:y Step 4 Respond No to continue uninstalling WANDEST using the Installshield GUI. Respond Yes to continue uninstalling WANDEST 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, you can uninstall WANDEST using an alpha-numeric terminal or a PC in terminal emulator mode. To uninstall using Console Mode, follow the instructions as they are displayed on the screen. For a general overview of how to use Console Mode Install, refer to the Console Mode Installation section in the Installing CWM Server Software chapter of the Cisco WAN Manager Installation Guide, Release 15. Step 5 After responding No to the question in Step 4, the WANDEST Uninstaller window opens. All the files and directories will be removed without any intervention on your part. Once the process finishes, click the Finish button to exit the Installshield GUI. Installing the WANDEST Client This section describes how to install the WANDEST client. It consists of the following prerequisites and procedures: •Platform Requirements •Running the Install Program •License Agreement Acceptance •Setting Up Client Communication With the WANDEST Server •Completing the Installation Platform Requirements The following requirements are needed on the workstation to successfully install the WANDEST client: •Solaris 8 (with the 108523-23 patch cluster installed) Running the WANDEST Client Install Program Complete the following steps to install the WANDEST client. Multiple clients can be installed on the same workstation. For information on multiple clients, see "WANDEST Client." Step 1 Log in as superuser. Step 2 Load the CD-ROM. Step 3 Change to the /cdrom/cdromWDclient directory. Step 4 At the command line prompt enter the following command: host% ./installWDClient.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 5 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, you can install WANDEST using an alpha-numeric terminal or a PC in terminal emulator mode. For a general overview of how to use Console Mode Install, refer to the Console Mode Installation section in the Installing CWM Server Software chapter of the Cisco WAN Manager Installation Guide, Release 15. Installshield GUI Installation After responding No to the question in Step 5, above, the installation classes are loaded: this process takes several minutes. License Agreement Acceptance Step 1 After the installation classes are loaded the WANDEST Client Installation Welcome window is displayed, as shown in Figure 5-17. Figure 5-17 Welcome Window Step 2 From the Welcome window, click Next. The WANDEST Client License Agreement window is displayed, as shown in Figure 5-18. Figure 5-18 License Agreement Window Step 3 From the Agreement for Software License window, click I accept the terms of the license agreement. Step 4 Click Next. The WANDEST FTP Information Window is displayed, as shown in Figure 5-19. Step 5 Continue to the "Setting Up Client Communication With the WANDEST Server" section. Setting Up Client Communication With the WANDEST Server After accepting the terms of the license agreement in the previous section, the next step is to set up your FTP User. Configuring passwords for the WANDEST FTP user is accomplished in the WANDEST FTP Information Window, as shown in Figure 5-19. Figure 5-19 WANDEST FTP Information Window Step 1 At the WANDEST FTP Information window, enter the password of the user on the machine in the FTP Password field and then reenter the same password to confirm in the ReEnter the Password field. Note In this release, the user name of "wandest" must be used as the FTP user name and cannot be changed. Step 2 After entering the FTP password in both fields, click Next. The Domain Name Used by Orbix window (Figure 5-20) is displayed. Figure 5-20 Domain Name Used by Orbix Step 3 In the Domain Name Used by Orbix window (Figure 5-20), enter the domain name to be used by Orbix. You can also choose to leave the domain name blank. Step 4 Click Next. The Choose the Output Directory and the Archive Directory window is displayed, as shown in Figure 5-21. Figure 5-21 Choose the Output Directory and the Archive Directory Window Step 5 If the default directory names in the Choose the Output Directory and the Archive Directory window are acceptable to you, click Next. If you want to change the default directory names, complete the following steps: Step 6 Enter the path for the output directory in the first field. Step 7 Enter the path for the archive directory in the second field. After you click Next to accept the default directories or the ones you entered, the Install Location Confirmation window (Figure 5-22) is displayed. Continue to the "Completing the Installation" section to wrap up the installation. Completing the Installation This section describes the steps needed to complete the WANDEST client installation. It consists of the following: •Confirm the choices made in the previous sections, and possibly go back to change them. •Begin the installation of files from the WANDEST client CD to the appropriate locations on the client workstation. •Monitoring the Installation Log file as it configures the database tables. Figure 5-22 Install Location Confirmation Window Step 8 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 applicable settings. Step 9 When Next is clicked, the Installation Progress Window is displayed as shown in Figure 5-23. The Installing Progress window (Figure 5-23) shows the progress of the files being extracted, and the progress of the database creation and configuration process. Figure 5-23 Installing Progress Window As the installation process begins configuring database tables an Installation Log Window (Figure 5-24) opens. Figure 5-24 Installation Log Window Once the database is completely configured, the Installation Log Window (Figure 5-24) and the Installing progress window (Figure 5-23) automatically shut down and the Installation Complete window (Figure 5-25) displays. Figure 5-25 Installation Complete Window Step 10 In the Installation Complete window, click Finish. The client installation program creates the client Configuration file, /usr/users/wandest/client/wdconfig.conf, based upon inputs during installation. Note The installation program supplies a default Control file. The WANDEST client can be started using the default Control file. However, you should use the FTP protocol to copy the control file from the WANDEST server machine /usr/users/wandest/wdclient.ctrl, which has been generated to match the CWM database schema on the server. The Control file for WANDEST can be edited to capture only certain data. See "WANDEST Client." Ensuring the Creation of the wandest Username and Password A user with the default ID and password of wandest is created during the client installation. When the WANDEST server or client is installed for the first time on your Solaris workstation, the wandest username and password may not be available. After installing the WANDEST server or client, log in as root and set the unix password(s) for the wandest user using either the admintool or using the passwd command on the command line as root (e.g. "passwd svplus") To change an existing password, complete the steps listed in Modifying the Client Password. Caution The wandest password needs to be set only on the client machine. Running the Uninstall Program An uninstall program is included in the WANDEST client installation. To uninstall the WANDEST client, complete the following steps. Step 1 Log in as superuser. Step 2 Change to the /usr/users/wandest directory. Step 3 At the prompt enter the following script: host% ./UnInstallWDClient 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 Uninstaller in Console Mode? (Yes / No): [No]:y Step 4 Respond No to continue uninstalling WANDEST using the Installshield GUI. Respond Yes to continue uninstalling WANDEST 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, you can uninstall WANDEST using an alpha-numeric terminal or a PC in terminal emulator mode. To uninstall using Console Mode, follow the instructions as they are displayed on the screen. For a general overview of how to use Console Mode Install, refer to the Console Mode Installation section in the Installing CWM Server Software chapter of the Cisco WAN Manager Installation Guide, Release 15. Step 5 After responding No to the question in Step 5, the WANDEST Uninstaller window opens. All the files and directories will be removed without any intervention on your part. Once the process finishes, click the Finish button to exit the Installshield GUI. Starting the WANDEST Server After installation, the WANDEST server becomes part of the CWM startup process. The WANDEST server starts upon execution of the command to start CWM. For information on starting CWM, refer to the Cisco WAN Manager User's Guide, Release 15. Starting the WANDEST Client To start the WANDEST client, complete the following steps: Step 1 Log in as wandest. Step 2 To start the client, enter the following command: host% wdclient <serverworkstationname> <socket port number> The client is not yet connected to the server. Step 3 From either the OSS application or the Admin Utility, enter the start command to connect the client to the server. The WANDEST client is now connected to the WANDEST server. Modifying the Client Password A user with ID wandest is created during the WANDEST client installation. The default password created by the installation is also wandest. The password is encrypted and stored on the client configuration file. This password is not exported in any WANDEST database or log file. Caution Each time the client password is changed, the wdupdate utility program must be invoked to update the new password. Otherwise, WANDEST does not function properly. To change the client password, complete the following steps: Step 1 Stop any running wdclient or wdadmin program on the client host. Step 2 To modify the password, use a password management utility. For example: host% passwd wandest The password must be 5-20 characters. Only a subset of ASCII characters can be included in the password. Step 3 At the prompt, enter the new password. Reenter it when prompted. Step 4 Execute the wdupdate utility program with the new password as input. host% /usr/users/wandest/bin/wdupdate <new password> <wdconfig.conf file> The wdupdate utility modifies the following default config file with the encrypted version of the new, input password: /usr/users/wandest/client/config/wdconfig.conf If a different configuration file is used, the full path and file name of this configuration file needs to be input to the wdupdate program. Otherwise the correct password is not modified, and the WANDEST client/server communication cannot function. For example, if the new password is <newpwd> and the configuration file is: /usr/users/myname/somewhere/wdconfig.conf, the command line to invoke the wdupdate program is: host% /usr/users/wandest/bin/wdupdate <newpwd> /usr/users/myname/somewhere/wdconfig.conf
	© 1992-2008 Cisco Systems, Inc. All rights reserved. Terms & Conditions \| Privacy Statement \| Cookie Policy \| Trademarks of Cisco Systems, Inc.