Installing and Configuring CiscoWorks Blue

Note Refer to the Release Notes for CiscoWorks Blue Maps and SNA View Software Release 3.0.1 for cautionary statements about the installation and configuration process. Also review the "Collecting Data for Installation on UNIX" section.

Upgrading to CiscoWorks Blue Release 3.0.1

This section describes how to upgrade to CiscoWorks Blue Maps or SNA View Release 3.0.1 from a previous release.

Creating a Seed File from a Previous Software Release Database

Use the following procedure to create a seed file from your database of a previous release for use with your Release 3.0.1 applications.

Note You can avoid having to discover the network from the network management database by creating a seed file or saving the seed file from the previous release.

Creating a Seed File in a Previous Release

Enter the following command:

: cwb create seed [-s seedfile]

Where -s seedfile specifies the name of the seed file to create. If you omit this parameter, the seed file is named seed.file.

Note When you deinstall CiscoWorks Blue, the following configuration files are saved in the /var/tmp/cwb.save directory: cwbinit, runprocess, CWBlue.conf, Services.conf, and SeedFile.

Upgrading SNA View Configuration Files

If you specify the same domain name during configuration of Release 3.0.1, your mainframe connection configuration file will be upgraded automatically.

Using CiscoWorks Blue Release 3.0.1 Workstation Software with a Previous SNA View Release of Mainframe Software

If you are installing CiscoWorks Blue Release 3.0.1, the mainframe software must be at least Release 2.1 (version 3.0 for LU 6.2 users). Cisco strongly recommends that you upgrade both the mainframe software and CiscoWorks Blue to Release 3.0.1.

Note If you plan to connect a workstation running CiscoWorks Blue Release3.0.1 to a mainframe running a previous release of SNA View using TCP/IP, set MESSAGES OFF in the NSPPARM file on the mainframe to avoid connectivity problems.

Saving the cwbinit File

Before you install CiscoWorks Blue Release 3.0.1, you might want to save the $CWBROOT/etc/cwbinit configuration file from your previous release. Although the previous versions of this file are not suitable for use with Release 3.0.1, you can copy settings from the older release after you install Release 3.0.1.

Deinstalling Maps and SNA View from a Previous Release

Before you install CiscoWorks Blue Maps and SNA View Release 3.0.1, you must deinstall the previous release. Use the deinstall script from the CD-ROM to perform the deinstall function.

Use the instructions in the "Deinstalling CiscoWorks Blue From a Previous Release" section

Installing and Configuring CiscoWorks Blue

You can install and configure CiscoWorks Blue Maps and SNA View from a local or remote CD-ROM drive. In either case, you install both Maps and SNA View at the same time. The license that you purchase from Cisco determines which applications you can use. You must have a license key for each application, one for Maps and one for SNA View.

This section includes the following subsections:

If it is necessary to reinstall a CiscoWorks Blue product, deinstall the existing software using procedures in the "Deinstalling CiscoWorks Blue From a Previous Release" section, and then reinstall as if it were a new installation.

Installing CiscoWorks Blue Maps and SNA View

Use the following procedure to install the software on your system. The default for each prompt is the value in brackets. To accept any default value, press Enter.

Installing from a Remote CD-ROM Drive

If you are installing from a remote CD-ROM drive, insert the CD-ROM into the drive on a remote system and export the CD-ROM file system (make it available to an outside system). If you are installing from a local CD-ROM drive, insert the CD-ROM in the drive on the local system, then mount the CD-ROM file system on the local system. If you do not know how to mount a CD-ROM drive from a local or remote system, see "Mounting a CD-ROM on UNIX Workstations."

Installing from a Remote System

If you are installing from a remote system, you must export your display to that remote system to view the applications that are started at the end of the installation process.

Installing the First CiscoWorks Blue for the First Time

If you are just now installing your first CiscoWorks Blue 3.0.1 product, go to the "Installing the CiscoWorks Blue 3.0.1 Products."

Installing a Second CiscoWorks Blue Product

If you have already installed one of the CiscoWorks Blue 3.0.1 products, either Maps or SNA View, and now want to install the other CiscoWorks Blue 3.0.1 product, do not go through the installation process. Instead, apply the second license key to the license file, as described in the "Applying Licenses after Installation."

I nstalling the CiscoWorks Blue 3.0.1 Products

The default for each prompt is the value shown in brackets. To accept any default value, press Enter.

Step 1 Before you start, collect the necessary information as described in the "Collecting Data for Installation on UNIX" section.

Step 2 If you have any release of CiscoWorks Blue Maps or SNA View installed, deinstall it as described in the "Deinstalling CiscoWorks Blue From a Previous Release" section or the "Modifying Color Schemes for the Maps Motif Applications" section before you begin to install CiscoWorks Blue Maps or SNA View Release 3.0.1.

Note When you deinstall a previous release and then install Release 3.0.1, the following configuration files are saved in the /var/tmp/cwb.save directory for reference: cwbinit, runprocess, CWBlue.conf, Services.conf, and SeedFile.

Step 3 Start the interactive installation script by entering the following command:

: # /cdrom/setup.sh

Step 4 If you have already installed the products and are already licensed for Maps but not for SNA View, you will see the following message.

INFO:Your current CiscoWorks Blue SNA View license key is not valid.

Do you want to enter CiscoWorks Blue SNA View license key[yes|no]? [Y]

Press Enter to install a license for SNA View.

If you enter Y, go to the "Applying the CiscoWorks Blue Licenses" section.
If you enter N, installation stops.

Step 5 If you have installed the products and are already licensed for SNA View and not for Maps, you will see the following message:

INFO:Your current CiscoWorks Blue Maps license key is not valid.

Do you want to enter CiscoWorks Blue Maps license key[yes|no]? [Y]

Press Enter to install a license for Maps.

Step 6 If you have installed the products but you have applied a temporary license key for an evaluation copy of Maps or SNA View, or a license key that is invalid, you might see one of the following messages:

INFO:Your current CiscoWorks Blue Maps license expires on mm/dd/yyy.

Do you want to enter CiscoWorks Blue Maps license key[yes|no]? [Y]

INFO:Your current CiscoWorks Blue SNA View license expires on mm/dd/yyy.

Do you want to enter CiscoWorks Blue SNA View license key[yes|no]? [Y]

INFO:Your current CiscoWorks Blue Maps license key is not valid.

Do you want to enter CiscoWorks Blue Maps license key[yes|no]? [Y]

INFO:Your current CiscoWorks Blue SNA View license key is not valid.

Do you want to enter CiscoWorks Blue SNA View license key[yes|no]? [Y]

Press Enter if you now want to apply a valid, permanent license key for Maps or SNA View.

Step 7 If you have already installed the products but did not apply any license, and then you reran the installation program, you will see the following message:

INFO:Your current CiscoWorks Blue license keys are not valid.

Do you want to enter CiscoWorks Blue license key(s) [yes|no]? [Y]

Press Enter to install a license.

Step 8 The setup program starts and displays the following banner:

**********************************************************************

*                           Cisco  Systems

*      .          .                                 .          .

*      |          |          CiscoWorks             |          |

*     :|:        :|:      Blue Maps and SNA View  :|:        :|:

*   :|||||:    :|||||:                           :|||||:    :|||||:

* .:|||||||:..:|||||||:.    Setup  Program     .:|||||||:..:|||||||:.

*********************************************************************

Note Installation error messages are self-describing and are not described in this manual. If you cannot complete the installation successfully, call the Cisco TAC.

Step 9 On Solaris, if you have more than one network management system (NMS) installed, select which NMS you want to integrate with CiscoWorks Blue. The installation program detects if you have any network management systems installed. If it finds more than one NMS, it asks you to select one to use. In response to the following prompt, type SNM to use the Sun Net Manager, or type HPOV to use HP-OpenView.

INFO: Install program detected SunNet Manager and HP Openview installed on the machine.

Which NMS platform do you want to use to integrate CiscoWorks Blue Product?: [SNM/HPOV]

Step 10 If the installation program cannot find an NMS, either enter the NMS path or specify no NONMS:

On Solaris systems:

In response to the following prompt, specify which NMS is installed:

Install program did not detect either HP OpenView or SunNet Manager

Do you have either HP OpenView or SunNet Manager installed on the system? [HPOV/SNM/NONMS]

Type HPOV if HP OpenView is installed.
Type SNM if SunNet Manager is installed.
Type NONMS if no NMS is installed.

On HP systems:

In response to the following prompt, specify which NMS is installed:

Install program did not detect HP OpenView 

Do you have HP OpenView installed on the system? [HPOV/NONMS]

Type HPOV if HP OpenView is installed.
Type NONMS if no NMS is installed.

On AIX systems:

In response to the following prompt, specify which NMS is installed:

Install program did not detect NetView for AIX

Do you have NetView for AIX installed on the system? [NETV/NONMS]

Type NETV if NetView for AIX is installed.
Type NONMS if no NMS is installed.

Step 11 And, in response to the next prompt, enter the full path name for the NMS:

For SunNet Manager:

Enter the SunNet Manager installation root directory:

For HP OpenView:

Enter the HP OpenView installation root directory:

For NetView for AIX:

Enter the NetView for AIX installation root directory:

Step 12 In response to the following prompt, enter the path and name of your Netscape browser binary file (the executable file):

Note This file should be the Netscape executable, not a shell script that runs Netscape.

Enter fully qualified Netscape browser executable path

Type the full path (including filename) to the Netscape browser binary file; for example:

Enter fully qualified Netscape browser executable path /usr/local/packages/cnetscape/current/Solaris-2.5/netscape.128

If you do not have Netscape installed yet, you can install it later. At that time, add the string Netscape to your path statement and ensure that the Netscape executable name is Netscape.

Step 13 (Optional) If you are installing on a Solaris platform and want to use the path tool for mainframes in HPR/IP session paths, "traceroute" must be included in your current path. If "traceroute" is not in your current path, you will be prompted to supply the path as in this example:

Ener fully qualified traceroute executable path

Type the full path of the traceroute command.

To skip this step, hit the Enter key.

Step 14 In response to the following prompt, press Enter to accept the default or enter a new path for installing the product. Normally the installation program chooses the drive with space available.

Where should the product be installed? [/opt] 

Note The installation program always creates links from /opt/CSCOcb to wherever you choose to install the product. You can always find the CiscoWorks Blue cwb command in /opt/CSCOcb/bin.

Step 15 For AIX systems, if there is insufficient room in the /usr file system, in response to the following prompt, press Enter to expand the /usr file system:

/usr has insufficient space for installation.

Do you want to expand /usr partition [yes|no]? [Y]

Step 16 The program installs the software from the CD-ROM and reports on its progress.

You can use the more command to examine the installation log file for error messages.

more /opt/CSCOcb/install/cwb_install.log

Press the Spacebar to advance the display one screen at a time.

When installation is complete, the cwbinit script is added to the system initialization files to automatically start the CiscoWorks Blue processes when you reboot.

This concludes the installation process. Go to the next section to apply your licenses for CiscoWorks Blue applications.

Applying the CiscoWorks Blue Licenses

During installation, you can apply the license information for the Maps and SNA View applications. If you do not apply the license information now, you can apply it later as described in the "Applying Licenses after Installation" section.

Note If you uninstalled CiscoWorks Blue Release 3.0 from the Release 3.0.1 CD, your licenses will be automatically restored. Depending on which products you had previously licensed, Steps 1 and 2 in this procedure will be skipped.

Step 1 In response to the prompt, enter the Maps license key as found in your license materials. If you are not licensed for Maps, press Enter.

Enter the CiscoWorks Blue Maps license key (example:123456789012) or press enter if not licensed for CiscoWorks Blue Maps

Step 2 In response to the following prompt, enter the SNA View license key as found in your license materials. If you are not licensed for SNA View, press Enter.

Enter the CiscoWorks Blue SNA View license key (example:123456789012) or press enter if not licensed for CiscoWorks Blue SNA View

Step 3 In response to the prompt, press Enter to configure the installed product now and go to the next section. If you enter N, you can configure the product later using the cwb config command.

Would you like to configure CiscoWorks Blue Maps now [yes|no]? [Y]

Go to the next section to configure CiscoWorks Blue applications.

Configuring CiscoWorks Blue

After you install Maps and SNA View, configure the application using the following procedures.

Specify an SNA domain name and protocol for a connection to an SNA mainframe.
Specify the protocols (DLSw, APPN/SNASw, RSRB, and TN3270) to be managed so that the Process Manager sets up the correct processes.
Specify whether to query a domain name server (DNS) for router host names.
Specify the ports to use for CiscoWorks Blue processes.

Note If you do not configure now, you can use the /opt/CSCOcb/bin/cwb config command to configure later.

Using Default Values

In the configuration procedure, the default for each prompt is the value shown in brackets. To accept any default value, press Enter.

The CiscoWorks Blue configuration procedure starts with a set of predefined default values. After you run the CiscoWorks Blue configuration procedure the first time, the choices you make become the default values for the next time you run the program. For example, the first time you run the program, the default for enabling DNS queries is N:

Would you like to enable DNS search [yes|no]? [N]

If you change the N to Y and press Enter to enable DNS queries, the next time you run the configuration procedure, the default changes to Y:

Would you like to enable DNS search [yes|no]? [Y]

Note In the prompts in the following section, the values shown in brackets are the predefined default values used when you first run the configuration program.

Using the Configuration Procedure

The installation script should automatically start the configuration script. If it does not, or if you want to reconfigure the product at any time, you can start the interactive configuration script with the cwb config command as described in the "Configuring CiscoWorks Blue after Installation" section.

Note You must have applied a valid Maps or SNA View license to configure the product.

Use the following information to configure the CiscoWorks Blue:

Step 1 In response to the following prompt, type Y and press Enter to configure the mainframe connection now or type N and press Enter to bypass configuring a mainframe connection. You can use the cwb config command later to configure a mainframe connection.

Would you like to Add/Modify/Delete a SNA host connection [yes|no]? [Y]

Step 2 At the following prompt, enter the name of the mainframe SNA domain in uppercase letters:

SNA Domain name(s) (Use upper case letters only):MVSD

To specify a domain name, enter any 1- to 8-character alphanumeric value. Choose a name that is meaningful in your environment, such as an SSCP name or host PU name. This domain name is added as an extension to all PU and LU names to create the format PUNAME.DOMAIN, which is used in the SNA View database and on the Maps views. You must use all uppercase characters in domain names.

Step 3 To reconfigure an existing domain, specify an existing domain name. The configuration program displays a message informing you of the reconfiguration of the existing file. Type Y and press Enter to modify the selected mainframe connection now or type N and press Enter to bypass modifying the mainframe connection.

Would you like to modify it [yes|no]? [Y] 

You might want to reconfigure an existing domain if you migrated configuration files from a previous release of SNA View.

Step 4 At the following prompt, specify whether the connection to that domain is using LU 6.2 or TCP/IP. Type TCP and press Enter to configure a TCP/IP connection or type LU62 and press Enter to configure an LU 6.2 connection.

Connectivity to mainframe (TCP or LU62): TCP

If you enter TCP, then the Process Manager automatically starts the cwbhcid daemon to start a connection to the mainframe component.

At this point in the configuration process, if your host connection is via LU 6.2, you should configure the host connection as described in the "Configuring the Host Connection" section.

Step 5 At the following prompt, for TCP/IP connections only, enter the TCP/IP address or host name for the SNA mainframe:

Mainframe TCP/IP Name or Address: rtpmvsd

For each SNA domain that you configure, the program builds a configuration file named /etc/svopen_config_DOMAINNAME, where DOMAINNAME is the name of the SNA domain that you specified. To review the SNA parameter values, edit this file as described in the "Configuring Domain-Specific Parameters" section.

Note The configured mainframe ports for /etc/svopen_config_hostname are 6104 and 6105. Ensure that NSPPARM on the mainframe is configured to match. See the CiscoWorks Blue Maps and SNA View Mainframe Installation Guide for more information.

Step 6 When you see the following prompt, type Y and press Enter to configure another host domain or type N and press Enter to stop configuring host domains.

Configure another SNA host connection [yes|no]? [N]

Step 7 In response to the following prompt:

Type Y and press Enter to specify that you manage APPN/SNASw. This action makes cwbsnamapsd dependent on AppnPollerServer in the Process Manager and is used by cwb verify to check for valid configuration.
Type N and press Enter to specify that you do not manage APPN/SNASw.
Press Enter to accept the default.

Configure APPN [yes|no]? [Y]

Step 8 In response to the following prompt:

Type Y and press Enter to specify that you manage DLSw. This action makes cwbdlswpollerd and cwbtrapd (if an NMS is present) start automatically in the Process Manager and is used by cwb verify to check for valid configuration.
Type N and press Enter to specify that you do not manage DLSw.
Press Enter to accept the default.

Configure DLSW [yes|no]? [Y]

Step 9 In response to the following prompt:

Type Y and press Enter to specify that you manage RSRB. This action makes cwbrsrbpollerd and cwbtrapd (if an NMS is present) start automatically in the Process Manager and is used by cwb verify to check for valid configuration.
Type N and press Enter to specify that you do not manage RSRB.
Press Enter to accept the default.

Configure RSRB [yes|no]? [Y]

Step 10 In response to the following prompt:

Type Y and press Enter to specify that you manage TN3270.
Type N and press Enter to specify that you do not manage TN3270.
Press Enter to accept the default.

Configure TN3270 [yes|no]? [Y]

Step 11 In response to the following prompt:

Type Y to specify that you do want a DNS lookup when devices are added to the database. Press Enter.
Type N to specify that you do not want a DNS lookup when devices are added to the database. Press Enter.
Press Enter to accept the default.

Note The option you select here is used to set the doDNSSearch variable in the cwbinit file.

If you select N, then a device can be added only by the name with which the device was discovered. If you select Y, then a DNS lookup will let you enter any other valid names for the device that can be resolved by a DNS. For example, using DNS lookup, a device that was discovered as heritage.cisco.com could also be referred to as heritage.

Devices in the network may be referred to in different ways. For

example a device may be discovered as router1.cisco.com, but a

Maps/SNA View user may refer to the device just as router1. In order

for the application to identify both names as the same device it

must perform a DNS lookup on the device name both when it is discovered and for each client request that can not be identified based upon the device name supplied. Enabling DNS searches can increase the device discovery time and the amount of time it takes to service requests, especially if the DNS searches fail for the devices being discovered.

Would you like to enable DNS search [yes|no]? [N]

Step 12 In response to the following prompt, press Enter to accept the default port for use by the CiscoWorks Blue web server or type in another TCP port above 1023 and press Enter. Initially, the default port is port 80.

Enter 80, 8080 or an unused tcp port above 1023 for Web Server:[80]

The configuration program checks to see whether the selected port is available. If it is unavailable, you will be prompted to select another port for the web server.

Step 13 In response to the following prompt, press Enter to accept the default port for use by the CiscoWorks Blue Open Server Gateway or type in another TCP port above 1023 and press Enter. Initially, the default port is port 44541.

Enter an unused tcp port above 1023 for Open Server Gateway:[44541] 

The configuration program checks to see whether the selected port is available. If it is unavailable, you will be prompted to select another port for the Open Server Gateway.

Step 14 In response to the following prompt, press Enter to accept the default port for use by the CiscoWorks Blue Name server or type in another UDP port above 1023 and press Enter. Initially, the default port is port 44542.

Enter an unused udp port above 1023 for Name Server:[44542]

The configuration program checks to see whether the selected port is available. If it is unavailable, you will be prompted to select another port for the Name server.

Note Ensure that the ports that you select are not used by other applications. During configuration, the /etc/services file and current ports in use are checked, but a service might not be active at the moment. If you need to change this port later, you must reconfigure the product using the cwb config command.

Step 15 If one of the selected ports is reserved in the /etc/services file but does not appear to be in use at this time, you might see the following message. If you want to keep the port reserved and use another port, type N and press Enter.

WARNING: Port port_number/protocol is reserved for application_name service in /etc /services file.

Do you want to use port_number/protocol anyway [yes|no]? [N]

Step 16 In response to the following prompt, type Y and press Enter to stop and restart CiscoWorks Blue processes or type N and press Enter to restart them at a later time. If you make any changes to the CiscoWorks Blue configuration, you must stop and restart all CiscoWorks Blue processes before those changes become active.

You will see this prompt only if you have configured the product already and are now changing that configuration.

CiscoWorks Blue configuration has changed. You must restart
all CiscoWorks Blue processes to make these changes effective.
Do you want to restart CiscoWorks Blue processes [yes|no]? [Y] 

This concludes the configuration process. To start CiscoWorks Blue processes, go to the "Enabling DNS Lookups for Device Queries" section.

Enabling DNS Lookups for Device Queries

When CiscoWorks Blue processes add a device to the database or make device queries, they use the device host names. If a DNS is available, the processes can query the DNS to resolve the host names. If a DNS is not available, the processes must use the exact device names with which the devices were first discovered.

If you do not enable DNS queries, a device can be added only by the name with which the device was discovered. If you enable DNS queries, a DNS lookup will let you enter any other valid names for the device that can be resolved by a DNS. For example, using DNS lookup, a device that was discovered as heritage.cisco.com could also be referred to as heritage.

Use the following sections for information on selecting DNS lookup:

Selecting DNS Lookup During Configuration

During configuration, a prompt asks you to specify whether or not to use a DNS lookup when devices are added to the database.

Selecting DNS Lookup with the doDNSSearch Variable

The doDNSSearch variable in the cwbinit file lets you specify to use DNS lookup to query routers during discovery and polling. In previous releases, you had to enter the exact name of the router by which it was first discovered. You can set this variable so that you can enter a different host name that can be resolved by a DNS lookup. This variable is used when you do the following:

Discover devices with the Maps and SNA View web interface
Use the Administration program to discover, rediscover, and add devices
Use the cwb start cwbdiscover command
Use discovery or add devices in the Maps Motif application

The following new section of the cwbinit file provides the doDNSSearch variable:

# This boolean value is used by both the cwbsnamapsd server process 

# and other processes such as cwbadmin, cwbdiscover, dlsw and rsrb

# that add devices to the database.

#

# When adding a device to the database, this value is used to decide 

# whether to do a DNS lookup on the name of the device being added,

# storing the DNS name in the DNS database table.

#

# cwbsnamapsd uses this value to decide whether to do a DNS lookup on

# a device name supplied in a user's request, if the request could

# not be satisfied with a device name or IP address lookup.

#

# The default value is "false", DNS lookups are not enabled. Set this

# value to "true" to enable DNS lookups.

doDNSSearch = false

Note You can set the doDNSSearch value during configuration.

You can set the doDNSSearch variable in the cwbinit file to true to discover and query routers by any valid name. Now you can enter the discovered name, a valid IP address, or any valid name for the router. For example, you could enter cwb-c5 in the input field for a DLSw focus view even if the router was discovered as cwb-c5.cisco.com. To enable DNS lookup for routers, change the doDNSSearch value to true:

doDNSSearch = true

The DNS lookup is done when the router is added to the database and any time a device cannot be found by the discovered name or IP address. This search might impact performance.

Note After you change the doDNSSearch parameter, you should stop and restart cwbsnamapsd.

Starting the CiscoWorks Blue Processes

This section describes how to start CiscoWorks Blue processes during installation.

Step 1 In response to the following prompt, press Enter to start the CiscoWorks Blue servers. If you enter N, you can start the servers yourself with the cwb start servers command, as described in "Monitoring and Controlling CiscoWorks Blue Applications."

Would you like to start the CiscoWorks Blue Maps processes now [yes|no]? [Y]

Step 2 When the servers are started, the installation program displays the current status of all CiscoWorks Blue servers and processes:

CiscoWorks Blue Naming Server Started.
CiscoWorks Blue Process Manager Started.
Process Manager running with processes:

PROCESS              STATE    PID        Last Message

CWBHTTPAdapter       Ready    45818      Running

CWBOSAMonitor        Ready    25078      Running

cwbhcid_MVSDTCP      Ready    26162      Running

cwbhcmdd_MVSDTCP Ready    17106      Running

cwbhmond_MVSDTCP Ready    18690      Domain Discovered : Mon Aug  2 17:189

CWBPMMonitor         Ready    19262      Running

cwbsnamapsd          Ready    26422      Ready for client requests

cwbtrapd             Ready    15548      Running

CWBMsgLogServer      Ready    40696      Running

AppnPollerServer     Ready    21386      Connection opened with cwbsnamapsd

cwbdlswpollerd       Ready    29058      Running

cwbhci_server_MVSDLU62 Initial

cwbhcmd_server_MVSDLU62 Initial

CWBDBAdapter         Ready    33598      Running

cwbmonitord          Initial

Step 3 The installation program starts the following applications:

The Process Manager client, which lets you monitor, start, and stop CiscoWorks Blue processes
The Message Logger client, which lets you view CiscoWorks Blue messages
The Administration application, which lets you discover network devices and specify DLSw key devices

Note The Administration application, the Process Manager, and Message Logger clients require X Window System support. If you install the product from a remote workstation, you need an X Window System server and you must export your display to that server to use these applications.

Now that all the servers and processes are running, go to the "Finishing Installation" section to finish the installation.

Finishing Installation

After the installation process is complete and the CiscoWorks Blue programs are started, you can create a seed file, discover the network routers, and specify DLSw key routers by using the following procedures;

Creating a Seed File with DLSw Key Routers

This step is optional. A seed file is a file that contains a list of router names or addresses. You can list the routers in either of two formats:

router [ReadCommunityString] [key]

router:[ReadCommunityString]:[key]

Where:

key indicates that this is a DLSw key device. This option does not apply to APPN/SNASw, RSRB, or TN3270 devices. If you omit the word key, the router is not considered a DLSw key device.

For more information on using key devices, see the "Using Key Devices" section.

For information about creating a seed file, see the "Discovering the Network" section and review creating a seed file in the subsections for each protocol (DLSw, RSRB, TN3270, and APPN/SNASw).

Discovering the Routers

You can discover the network devices using the CiscoWorks Blue Administration application, as described in "Using the Administration Application."

Now that all the servers and processes are running, and you have created a seed file and discovered the routers in the network, go to "Monitoring and Controlling CiscoWorks Blue Applications" to learn how to control the applications.

Running the Verification Program

After you finish installing the CiscoWorks Blue products, configuring the products, and discovering routers for the database, use the verification program to ensure that all went successfully. Click Verify on the Administration window or enter the commands shown below:

: cd /opt/CSCOcb/bin
: ./cwb verify

The verification program performs the following tasks:

Summarizes the applications you configured
Checks your configuration files
Scans the CiscoWorks Blue database
Displays a verification report:

======================================================================

                          CiscoWorks Blue Verification

                           Wed Jan 20 14:56:26 1999 

                                   nchand-u5

======================================================================

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

Process Summary

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

     Name       Configured      Ready

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

     APPN/SNASw    Yes           Yes

     Base          Yes           Yes

     DLSw          Yes           Yes

     RSRB          Yes           Yes

		     TN3270        Yes           Yes

     SNA           Yes           Yes

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

Database Summary

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

Total number of devices: 13

    APPN/SNASw:     3

    DLSw:           8

    RSRB:           3

    TN3270:         2

DLSw Key Devices:  6

Physical Units:    7

Logical Units:     7

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

Action Summary

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

The last section of the report suggests changes you might make to improve the CiscoWorks Blue installation.

You must fix all errors before you can proceed.
You can evaluate warnings and take action depending on your needs.
You can suppress warning messages by setting the ShowWarnings parameter in the /opt/CSCOcb/etc/cwbinit file to No.

Configuring the Host Connection

This section describes how to configure the connection between the Maps and SNA View workstation component and the mainframe component. You should configure the host connection before you install and configure the workstation.

This section includes the following subsections:

Creating and Deleting a Domain

To create a new domain or delete an existing domain, use the cwb config command.

Note Do not copy domain files nor edit them to create new domains. Do not delete domain files to delete existing domains.

Configuring Domain-Specific Parameters

This section describes how to configure domain-specific parameters for an SNA domain. For each SNA domain that you configure, the configuration program creates a file named /etc/svopen_config_DOMAINNAME, such as /etc/svopen_config_TEXAS using the domain name and protocol (TCP or LU 6.2) to create a set of default values in the configuration file. You can edit this file directly, if necessary, to change the values. The following is a sample configuration file:

SVMF_AGENT_ADDR rtpmvsd

SVMF_CONNECT TCP

INCLUDE_LUS yes

SVCMD_TIMEOUT 30

SV_KEEPALIVE 30

SV_DISCOVER_DISPLAY TOGGLE

SV_DISCOVER_INTERVAL 10

SV_EVENT_GEN YES

SVPATH /opt/CSCOcb/snahost

SVWORK_AREA /opt/CSCOcb/snahost/tmp

SVCMDS_AGENT_PORT 6100

SVHCI_STATUS_PORT 6101

SVACK_AGENT_PORT 6102

SVHCI_CMD_PORT 6103

SVMF_HCI_AGENT_PORT 6104

SVMF_CMDS_AGENT_PORT 6105

SV_RECONNECT yes

Table 3-1 lists the parameters you must set in the configuration file. Table 3-2 lists additional parameters that you might choose to customize. Table 3-3 lists additional parameters whose defaults you might choose to accept.

See the detailed descriptions of all parameters in the sections that follow the tables.

Table 3-1 Required Configuration Parameters

Parameter	Default Value	Description and Valid Values
SVMF_AGENT_ADDR	mvs_host_name.name.com	Host name or IP address of the mainframe on which the mainframe component is installed.
SVMF_CONNECT	TCP	LU62 or TCP. Set to LU62 if you use an LU 6.2 connection.

Table 3-2 Configuration Parameters You Might Want to Customize

Parameter	Default Value	Description and Valid Values
INCLUDE_LUS	YES	YES—Indicates to include LUs in the database. NO—Indicates to exclude LUs from the database.
SVCMD_TIMEOUT	30	1 to 1800 seconds.
SV_INCLUDE_SRB	YES	YES—Calculates PU-SRB dependencies during host discovery. NO—Does not calculate PU-SRB dependencies during host discovery.
SV_KEEPALIVE	30	1 to 1800 seconds.
SV_DISCOVER_DISPLAY	PERCENT	PERCENT.
SV_DISCOVER_INTERVAL	100	1 to 65535 PUs.
SV_EVENT_GEN	YES	YES—Generates an event notification message. NO—Does not generate an event notification message.
SV_LU62CMD_TP	NSPOPNCS	Any valid APPC TP name.
SV_LU62MSG_TP	NSPOPNMS	Any valid APPC TP name.
SV_RECONNECT	YES	YES—If the TCP connection to the mainframe fails, automatically try to reconnect. NO—If the TCP connection to the mainframe fails, do not automatically try to reconnect.

Table 3-3 Configuration Parameters You Might Want to Accept

Parameter	Default Value	Description and Valid Values
SVPATH	/opt/CSCOcb/snahost	Home directory.
SVWORK_AREA	/opt/CSCOcb/snahost	Any valid directory.
SVCMDS_AGENT_PORT	6100	Any unused port value.
SVHCI_STATUS_PORT	6101	Any unused port value.
SVACK_AGENT_PORT	6102	Any unused port value.
SVHCI_CMD_PORT	6103	Any unused port value.
SVMF_HCI_AGENT_PORT	6104	Any unused port value. Must match ports defined in mainframe PARM member.
SVMF_CMDS_AGENT_PORT	6105	Any unused port value. Must match ports defined in mainframe PARM member.

Configuration Parameter Descriptions

The following sections describe each parameter in detail.

Required Parameters

Set the following parameters, or accept the default values, for each domain:

SVMF_AGENT_ADDR (mainframe agent address parameter)—The host name or IP address of the mainframe where the mainframe component is installed. The value is used (and required) only when the SVMF_CONNECT value is TCP. There is no default value for this parameter.
SVMF_CONNECT (mainframe connectivity parameter)—Specifies the method of connectivity to the mainframe. Ensure that this parameter is set correctly:

TCP specifies that the workstation is connected to the mainframe using TCP/IP.
LU62 specifies that the workstation is connected to the mainframe using LU 6.2.

Parameters You Might Want to Customize

These parameters have preset default values that suit most users. Review the default setting for each parameter and decide whether it meets your requirements. You might want to change some of these parameter values.

INCLUDE_LUS (include logical units parameter)—Specifies whether to add LUs to the network management database if they are sent from the mainframe. (The Maps and SNA View mainframe installer can use the LU_CONTROL parameter card to specify how LUs are handled.) If your SNA network contains a large number of LUs, you might choose not to monitor them, to conserve workstation resources.

YES means the application adds LUs and monitors their status if they are sent from the mainframe.
NO means the application does not add LUs.

SVCMD_TIMEOUT (command time out parameter)—Specifies the number of seconds to wait for a command response from the mainframe before timing out. The default value is 30 seconds.
SV_INCLUDE_SRB—Determines if a host PU with rif data is associated with the discovered routers.

YES means the application calculates the PU-SRB dependencies during host discovery.
NO means the application does not perform the calculations.

SV_KEEPALIVE (Host Connection Interface connection keepalive parameter)—Specifies the number of seconds to wait for each of the following events to occur:

For TCP/IP communications, SV_KEEPALIVE controls how long the workstation waits without receiving anything from the mainframe before it sends a ping.
For TCP/IP and LU6.2 communications, SV_KEEPALIVE controls how long the Host Connection Interface, Host Command Server, and Status Monitor wait to connect to each other before they determine there is a communications problem.

SV_DISCOVER_DISPLAY (discovery status message parameter)—Specifies how the Process Manager client displays the discovery status message. The default value is PERCENT.

PERCENT—The discovery message window displays the percentage complete.

SV_DISCOVER_INTERVAL (PU discovery update parameter)—Specifies the number of PUs (1 - 65535) that can be discovered before the Process Manager client application is notified of the discovered PUs. The default is 100 PUs.
SV_EVENT_GEN (event generation parameter)—Specifies whether the SNA host component generates an event notification message when a VTAM IDBLK/INUM value in the database for one PU is found for a different PU. All event notification messages are described in "Starting the User Applications." This condition might mean that more than one end station is trying to use the same PU.

YES means the SNA host component generates an event notification message.
NO means the SNA host component does not generate an event notification message.

SV_LU62CMD_TP tpname—This parameter card is optional and is required only when a workstation requires multiple host connections using LU6.2. This card allows unique APPC transaction program (TP) names to be specified for each host connection. tpname is the APPC TP name configured for the host connection command program. The default name is NSPOPNCS if this card is not defined.
SV_LU62MSG_TP tpname— This parameter card is optional and is required only when a workstation requires multiple host connections using LU6.2. This card allows unique APPC TP names to be specified for each host connection. tpname is the APPC TP name configured for the host connection message program. The default name is NSPOPNMS if this card is not defined.
SV_RECONNECT— For TCP connections only, this parameter determines whether the workstation will automatically try to reconnect if the connection fails. Since a reconnect will restart PU discovery at the mainframe, you might want to manually control this function to avoid high CPU utilization during critical business hours.

YES means that the application will automatically try to reconnect to the mainframe. This was previously the hardcoded behavior of the product.
No means that the host connection processes (csbhcid, cwbhmond, and cwbhcmd) will be stopped and will not restart automatically. With this function, host resources will no longer be updated until you manually restart the csbhcid process for this domain.

You must also alter the /opt/CSCOcb/etc/CWBlue.conf file by changing the cwbhcid process for the proper domain from R "automatically restart" to Y "start automatically (but no restart)".

For example, if your domain in"MVSD", change the following line:

cwbhcid_MVSD R CWBMsgLogServer,CWBDBAdapter /opt/CSCOcb/etc/runprocess cwbhcid_MVSD,MVSD 30

to

cwbhcid_MVSD YCWBMsgLogServer,CWBDBAdapter /opt/CSCOcb/etc/runprocess cwbhcid_MVSD,MVSD 30

See the "Configuring Process Manager Windows" section for more information on updating the CWBlue.conf file.

Parameters You Might Want to Accept

These parameters have preset default values that suit most users. Review the default setting for each parameter and decide whether it meets your requirements. Depending on how your workstation is configured, you might want to change some of these parameter values.

SVPATH (path parameter)—The home directory of the SNA host component software, which is usually /opt/CSCOcb/snahost.
SVWORK_AREA (work area directory parameter)—Specifies where the SNA host component places temporary work files. The default is /opt/CSCOcb/snahost/tmp, but you can change it to meet your site's requirements.

Port Values:

Port	Default Port Setting
SVCMDS_AGENT_PORT	6100
SVHCI_STATUS_PORT	6101
SVACK_AGENT_PORT	6102
SVHCI_CMD_PORT	6103
SVMF_HCI_AGENT_PORT	6104
SVMF_CMDS_AGENT_PORT	6105

You can change the port values that the SNA host component specifies as default values if any of these ports are already in use at your site. We recommend that the port values be greater than 6000 and not exceed 9999.

When you are managing more than one domain, the Maps and SNA View installation program automatically increments the port values for each specified domain by 20. For example, if a port number in domain ABC is 6100, the SNA host component automatically sets the value for the same configuration parameter in domain DEF to 6120. If the port numbers are already in use, modify them to fit your site's requirements.

Configuring LU 6.2 Connectivity to the Mainframe

This section explains how to configure LU 6.2 connectivity between the SNA host workstation component and the mainframe.

This section includes the following subsections:

Preparing to Configure the SNA Host Component for Maps and SNA View

Before starting the steps to allow the SNA host component on the workstation to communicate with the mainframe, you must first do all the necessary configuration to allow an LU 6.2 session to flow from the workstation to the mainframe. You might need to make changes to both VTAM and the workstation application that supports LU 6.2 sessions. The following workstation LU 6.2 programs are supported:

HP-UX SNAplus2 (including SNAplus2 Link and SNAplus2 API)
IBM eNetwork Communications Server for AIX, Version 5.0 or later
Data Connection SNAP-IX V6.0.6 or later for SPARC Solaris (For more information, see http://www.dataconnection.com)

If the workstation is not directly connected to the mainframe running the SNA host component, but the session instead passes through one or more VTAMs before reaching the destination VTAM, then the correct configuration might require changes to all VTAMs (and possibly NCPs in the path).

Note It is not the intent of this document to identify all the steps necessary to set up the network. See the relevant IBM VTAM and NCP publications for more setup information.

If this LU 6.2 configuration has not yet been done, the installation should be delayed until the LU 6.2 configuration is complete. One way to determine whether there is LU 6.2 connectivity between the workstation and the mainframe is to issue the VTAM command D NET,APING,ID=NETID.RESOURCE. The NETID.RESOURCE should be the fully qualified name of the SNA workstation. Until this command returns a positive response, the mainframe will be unable to connect to the workstation.

After the initial LU 6.2 configuration is complete, you can use the procedures in the following sections to complete the configuration for the SNA host component.

Configuring LU 6.2 Connectivity for the eNetwork Communications Server on AIX

If the AIX workstation is connected to the mainframe using SNA LU 6.2, use this procedure to configure the LU 6.2 operating environment. This procedure creates the sna_tps file for TP profiles for the command server and the message server and a logmode named PARALLEL.

To configure AIX, create a file named sna_tps, and then configure PARALLEL mode processing.

Creating the sna_tps File on AIX

To configure the LU 6.2 transaction programs (TPs) that the SNA host component uses to communicate between an AIX workstation and a mainframe, create the configuration file /etc/sna/sna_tps, as described in the IBM eNetwork Communication Server for AIX publications. Use the sna_tps file to define two TPs named NSPOPNMS and NSPOPNCS. The following example shows a sna_tps file:

[NSPOPNCS]

LUALIAS = ""

DESCRIPTION = ""

USERID = root

GROUP = system

TIMEOUT = 30

TYPE = NON-QUEUED

STYLE = EXTENDED

PATH = /opt/CSCOcb/bin/cwbstarttp

ARGUMENTS = cwbhcmd_server MYDOMAIN

[NSPOPNMS]

LUALIAS = ""

DESCRIPTION = ""

USERID = root

GROUP = system

TIMEOUT = 30

TYPE = NON-QUEUED

STYLE = EXTENDED

PATH = /opt/CSCOcb/bin/cwbstarttp

ARGUMENTS = cwbhci_server MYDOMAIN

This sample sna_tps file defines two TPs:

NSPOPNCS is for the command server.
NSPOPNMS is for the message server.

In the file, each TP name is enclosed in brackets, as shown below:

[NSPOPNCS]

[NSPOPNMS]

For each TP, code the following entries:

USERID—Specifies the username under which the SNA host component launches the two TPs. This username must be root.
GROUP—Specifies the group for these TP programs (code system, as shown in the sample).
TIMEOUT—Specifies the timeout period (code 30, as shown in the sample).
TYPE—Specifies the type NON-QUEUED as shown in the sample.
STYLE—Specifies the style EXTENDED as shown in the sample.

Note When the new eNetwork Communications Server protocol stack is used, you must set the STYLE to EXTENDED.

PATH—Specifies the path to the executable file that handles the transaction programs. Code /opt/CSCOcb/bin/cwbstarttp, as shown in the sample.
ARGUMENTS—Specifies the name of the TP executable file and the name of the SNA domain. Replace MYDOMAIN in the sample file with the name of your SNA domain (use uppercase characters).

Configuring PARALLEL Mode on AIX

After you create the /etc/sna/sna_tps file, create a new LU 6.2 session profile named PARALLEL as described in the eNetwork Communication Server for AIX publications. Use the xsnaadmin command to configure an LU 6.2 PARALLEL logmode. The xsnaadmin command can often be found in the /usr/lpp/X11/bin directory.

Step 1 At the command prompt, enter the xsnaadmin command, as shown below.

: % xsnaadmin

The xsnaadmin window is displayed.

Note Ensure that your DISPLAY environment variable is correctly set. You might also have to set the LANG environment variable to your language.

Step 2 In the xsnaadmin window, select Services > APPC > Modes.

Step 3 If the PARALLEL mode is not in the list of defined modes, select Add. The Add Mode window is displayed.

Step 4 If the PARALLEL mode is already in the list of defined modes, exit the window. If its not in the Add Mode window, enter PARALLEL for the Mode Name, and either accept the defaults or customize the values for your operating environment.

If you need to create a PARALLEL log mode, accept the default parameter values:

Field	Default Value
COS name	#CONNECT
Initial session limit	2
Maximum session limit	32767
Min con. winner sessions	1
Auto-activated sessions	0
Receive pacing window (Initial)	4

Configuring LU 6.2 Connectivity for SNAplus2 on HP-UX

This section describes how to configure SNAplus2 for LU 6.2 support on HP-UX. To configure HP-UX SNAplus2, you first create a file named sna_tps, and then configure PARALLEL mode processing.

Creating the sna_tps File on HP-UX

To configure the LU 6.2 TPs that the SNA host component uses to communicate between an HP-UX workstation and a mainframe, create the configuration file /etc/opt/sna/sna_tps, as described in the SNAplus2 Administration Guide and SNAplus2 Installation Guide. Use the sna_tps file to define two TPs named NSPOPNMS and NSPOPNCS. The following example shows a sna_tps file:

#SNA Host Message Server

["NSPOPNMS"] 

PATH          = /opt/CSCOcb/bin/cwbstarttp 

ARGUMENTS     = cwbhci_server MYDOMAIN 

TYPE          = NON-QUEUED

TIMEOUT       = 30

USERID        = root 

GROUP         = sys 

#SNA Host Command Server

["NSPOPNCS"]

PATH          = /opt/CSCOcb/bin/cwbstarttp

ARGUMENTS     = cwbhcmd_server MYDOMAIN

TYPE          = NON-QUEUED

TIMEOUT       = 30

USERID        = root

GROUP         = sys

This sample sna_tps file defines two TPs:

NSPOPNMS is for the message server.
NSPOPNCS is for the command server.

In the file, each TP name is enclosed in quotation marks and then in brackets, as shown below:

["NSPOPNMS"]

["NSPOPNCS"]

For each TP, code the following entries:

PATH—Specifies the path to the executable file that handles the transaction programs. Code /opt/CSCOcb/bin/cwbstarttp as shown in the sample.
ARGUMENTS—Specifies the name of the TP executable file and the name of the SNA domain. Replace MYDOMAIN in the sample file with the name of your SNA domain (use uppercase characters).
TYPE—Specifies the type NON-QUEUED, as shown in the sample.
TIMEOUT—Specifies the timeout period (code 30, as shown in the sample).
USERID—Specifies the username under which the SNA host component launches the two TPs. This username must be root.
GROUP—Specifies the group for these TP programs (code sys, as shown in the sample).

Configuring PARALLEL Mode on HP-UX

After you create the sna_tps file, use the xsnapadmin command to configure SNAplus2 for PARALLEL processing mode. The xsnapadmin command is often found in the /opt/sna/bin/X11 directory.

Step 1 At the command prompt, enter the xsnapadmin command, as shown below.

: % xsnapadmin

The xsnapadmin window is displayed.

Note Ensure that your DISPLAY environment variable is correctly set. You might also have to set the LANG environment variable to your language.

Step 2 In the xsnapadmin window, select Services > APPC > Modes.

Step 3 If the PARALLEL mode is not in the list of defined modes, select Add. The Add Mode window is displayed.

If you need to create a PARALLEL log mode, accept the default parameter values:

Field	Default Value
Receive pacing window	4
Initial session limit	2
Max session limit	32767
Min con. winner sessions	1
Auto-activated sessions	0

Configuring LU 6.2 Connectivity for SNAP-IX on Solaris

This section describes how to configure SNAP-IX for LU 6.2 support on Solaris. To configure SNAP-IX, you first create the file sna_tps, and then configure PARALLEL mode processing.

Creating the sna_tps File on Solaris

To configure the LU 6.2 TPs that the SNA host component uses to communicate between a Solaris workstation and a mainframe, create a configuration file named /etc/opt/sna/sna_tps as described in the SNAP-IX publications. Use the sna_tps file to define two TPs named NSPOPNCS and NSPOPNMS.

The following example shows a sna_tps file:

[NSPOPNCS]

LUALIAS = ""

DESCRIPTION = ""

USERID = root

GROUP = other

TIMEOUT = 30

TYPE = NON-QUEUED

PATH = /opt/CSCOcb/bin/cwbstarttp

ARGUMENTS = cwbhcmd_server MYDOMAIN

[NSPOPNMS]

LUALIAS = ""

DESCRIPTION = ""

USERID = root

GROUP = other

TIMEOUT = 30

TYPE = NON-QUEUED

PATH = /opt/CSCOcb/bin/cwbstarttp

ARGUMENTS = cwbhci_server MYDOMAIN

This sample sna_tps file defines two TPs:

NSPOPNCS is for the command server.
NSPOPNMS is for the message server.

In the file, each TP name is enclosed in brackets, as shown below:

[NSPOPNCS]

[NSPOPNMS]

For each TP, code the following entries:

PATH—Specifies the path to the executable file that handles the transaction programs. Code /opt/CSCOcb/bin/cwbstarttp as shown in the sample.
ARGUMENTS—Specifies the name of the TP executable file and the name of the SNA domain. Replace MYDOMAIN in the sample file with the name of your SNA domain (use uppercase characters).
TYPE—Specifies the type NON-QUEUED, as shown in the sample.
TIMEOUT—Specifies the timeout period (code 30, as shown in the sample).
USERID—Specifies the username under which the SNA host component launches the two TPs. This username must be root.
GROUP—Specifies the group for these TPs (code other, as shown in the sample).

Configuring PARALLEL Mode on Solaris

After you create the /etc/opt/sna/sna_tps file, create a new LU 6.2 session profile named PARALLEL, as described in the SNAP-IX publications. Use the xsnaadmin command to configure an LU 6.2 PARALLEL logmode. The xsnaadmin command can often be found in the /opt/sna/bin/X11 directory.

Step 1 At the command prompt, enter the xsnaadmin command, as shown below.

: % xsnaadmin

The xsnaadmin window is displayed.

Note Ensure that your DISPLAY environment variable is correctly set. You might also have to set the LANG environment variable to your language.

Step 2 In the xsnaadmin window, select Services > APPC > Modes.

Step 3 If the PARALLEL mode is not in the list of defined modes, select Add. The Add Mode window is displayed.

If you need to create a PARALLEL log mode, accept the default parameter values:

Field	Default Value
Initial session limit	2
Maximum session limit	32767
Min con. winner sessions	1
Auto-activated sessions	0
Receive pacing window (Initial)	4

Configuring LU6.2 Connectivity to Multiple Hosts

This section allows you to define a single workstation to communicate with multiple mainframes using LU6.2. This section describes the configuration requirements for having a single workstation communicate with multiple hosts using LU6.2:

There must be unique pair of APPC TP names defined on the workstation for each host connection. The default TP names are NSPOPNMS and NSPOPNCS. Use the appropriate procedure in the "Configuring LU 6.2 Connectivity to the Mainframe" section to configure APPC TP names and select unique names for each connection.

For example, to have the workstation communicate to both MVS1 and MVS2, configure two sets of APPC TP programs. The pair of TP names for host connection MVS1 could be NSPM1 and NSPC1, while the host connection MVS2 could be NSPM2 and NSPC2.

In the host connection configuration files, you must indicate which APPC TP names are configured using the SV_LU62CMD_TP and SV_LU62MSG_TP cards.

For example, for host connection MVS1, the /etc/svopen_config_MVS1 configuration file should specify the following entries:

SV_LU62MSG_TP NSPM1
SV_LU62CMD_TP NSPC1

Also, for host connection MVS2, the /etc/svopen_config_MVS2 configuration file should specify the following entries:

SV_LU62MSG_TP NSPM2
SV_LU62CMD_TP NSPC2

At each host, ensure the SERVER card definitions in the NSPPARM configuration file match the TP names selected for the host connection.

For example, at host MVS1 a SERVER card must be configured to indicate TP names of NSPM1 and NSPC1. At host MVS2 a SERVER card must be configured to indicate TP names of NSPM2 and NSPC2.

Configuring TCP/IP Connectivity to the Mainframe

This section explains how to configure TCP/IP connectivity between the workstation and the mainframe. It includes the following subsections:

Configuring TCP/IP Port Parameters

If you configure TCP/IP connectivity from the workstation to the mainframe, you must match the SVMF_HCI_AGENT_PORT and SVMF_CMDS_AGENT_PORT parameters of the domain to the TCP Parameter Cards used in the mainframe. (TCP Parameter Cards are documented in the CiscoWorks Blue Maps and SNA View Mainframe Installation Guide.) For example, the workstation parameters for domain "NORTH" should be set as follows in /etc/svopen_config_NORTH:

SVMF_HCI_AGENT_PORT 6104

SVMF_CMDS_AGENT_PORT 6105

The host configuration file should have a TCP card containing the following:

TCP 6104 6105

Sending Nonencrypted Data

The data that is transferred between the mainframe and workstation component is not encrypted. This data transfer is secure if the data is transferred over a private intranet. If the workstation-to-host connection traverses the Internet, or if additional security is desired over the intranet, you can use the "Network Data Encryption with Router Authentication" feature provided with Cisco routers to encrypt the data that flows between the router nearest to the workstation and the router nearest to the host.

For more information on this topic, see the Cisco IOS software Security Configuration Guide.

Configuring Connectivity to Multiple Domains

If you configure TCP/IP connectivity from the same workstation to multiple mainframe domains, each set of SVMF_HCI_AGENT_PORT and SVMF_CMDS_AGENT_PORT parameters for each domain must have corresponding TCP parameter cards in the mainframe. (TCP Parameter Cards are documented in the CiscoWorks Blue Maps and SNA View Mainframe Installation Guide.)

To configure connectivity from the same workstation to multiple mainframe domains, use the following procedure:

For example, the workstation parameters for domain NORTH should be set as follows in /etc/svopen_config_NORTH:

SVMF_HCI_AGENT_PORT 6104

SVMF_CMDS_AGENT_PORT 6105

The workstation parameters for domain SOUTH should be set as follows in
/etc/svopen_config_SOUTH:

SVMF_HCI_AGENT_PORT 6114

SVMF_CMDS_AGENT_PORT 6115

The host configuration file for the SNA Host component at each domain's mainframe should have a TCP cards that contain the following lines:

For domain NORTH:

TCP 6104 6105

For domain SOUTH:

TCP 6114 6115

Applying Licenses after Installation

If you choose not to apply your CiscoWorks Blue license information during installation, or if you later obtain a new license for Maps or SNA View, you can apply a license after installation as described in this section.

You can get one of two licenses for the CiscoWorks Blue applications. You can get a license to run the Maps applications and a license to use the SNA View web pages. The license that you obtain determines which CiscoWorks Blue applications you can run. If you license both Maps and SNA View, you can use all the applications:

The SNA View license enables the SNA View icon on the CiscoWorks Blue web page and TN3270 discovery.
The Maps license enables the DLSw, RSRB, and APPN/SNASw icons on the CiscoWorks Blue web page, and makes the DLSw, RSRB, and APPN/SNASw Motif applications operational.
Either license enables the Process Manager, Message Log Viewer, and Administration program, as well as discovery of DLSw, RSRB, and APPN/SNASw devices.

After installation, use the cwbupgrade.sh command to apply the Maps and SNA View license keys. To enter a license key, use the following procedure:

Step 1 Start the /opt/CSCOcb/install/cwbupgrade.sh program:

: /opt/CSCOcb/installcwbupgrade.sh

Step 2 When you see the following prompt, enter y to enter a license key:

Do you want to enter CiscoWorks Blue Maps license key [yes|no]? Y

Step 3 When you see the following prompt, enter the Maps license key:

Enter the CiscoWorks Blue Maps license key (example 123456789012) or press enter if not licensed for CiscoWorks Blue Maps: 123456789012

Step 4 When you see the following prompt, enter the SNA View license key:

Enter the CiscoWorks Blue SNA View license key (example 123456789012) or press enter if not licensed for CiscoWorks Blue SNA View: 123456789012

Step 5 If you applied a temporary license key for an evaluation copy of Maps or SNA View, or a license key that is invalid, you might see one of the following messages:

INFO:Your current CiscoWorks Blue Maps license expires on mm/dd/yyy.

Do you want to enter CiscoWorks Blue Maps license key[yes|no]? [Y]

INFO:Your current CiscoWorks Blue SNA View license expires on mm/dd/yyy.

Do you want to enter CiscoWorks Blue SNA View license key[yes|no]? [Y]

INFO:Your current CiscoWorks Blue Maps license key is not valid.

Do you want to enter CiscoWorks Blue Maps license key[yes|no]? [Y]

INFO:Your current CiscoWorks Blue SNA View license key is not valid.

Do you want to enter CiscoWorks Blue SNA View license key[yes|no]? [Y]

Press Enter if you now want to apply a valid, permanent license key for Maps or SNA View.

Step 6 If Maps or SNA View is now running, press Enter when you see the following prompt:

INFO: CiscoWorks Blue Servers are currently running. You must restart all CiscoWorks Blue processes to make these changes effective.

Do you want to restart CiscoWorks Blue processes [yes|no]? [Y]

Configuring CiscoWorks Blue after Installation

You can configure the CiscoWorks Blue applications after installation using the cwb config command.

Step 1 Enter the following commands:

: # cd /opt/CSCOcb/bin
: # ./cwb config

Step 2 Make your responses to the configuration prompts as described in the "Configuring CiscoWorks Blue" section.

Deinstalling CiscoWorks Blue

If you have a previous version of CiscoWorks Blue installed, you must deinstall it before installing Release 3.0.1. If you have errors during installation of 3.0.1, you might also need to run uninstall before trying to install it again.

This section describes how to deinstall CiscoWorks Blue Maps and SNA View, and contains the following sections:

Deinstalling CiscoWorks Blue From a Previous Release, describes how to deinstall a previous release of CiscoWorks Blue software before you reinstall the product.

Deinstalling CiscoWorks Blue From a Previous Release

Note When you deinstall the previous release and then install Release 3.0.1, the following configuration files are saved in the /var/tmp/cwb.save directory: cwbinit, runprocess, CWBlue.conf, Services.conf, and SeedFile.

Step 1 Log in as the root user. For details, see the "Becoming the Root User" section.

Step 2 If you are deinstalling Release 3.x, use the following command from the CD to preserve the license keys:

: /cdrom/uninstall.sh

If you are deinstalling Release 2.x, start the interactive deinstallation script by entering the following commands:

: # cd /opt/CSCOcb/install
: # ./uninstall.sh

After you issue the uninstall command, the deinstallation script lists the packages that are installed:

CSCOcwbC is a common package that supports Maps and SNA View.
CSCOcwbXX is the Maps and SNA View package that supports an NMS. The XX identifies the NMS. (For example, package CSCOcwbOV supports HP OpenView.)
CSCOjre102 and CSCOjre110 provide Java Runtime Environment support (for HP workstations only).

Step 3 In reply to the following prompt, enter Y or press Enter to deinstall the packages.

Delete all Cisco Products CiscoWorks Blue packages listed above? [yes]

The deinstall program removes the CiscoWorks Blue products from the system.

Note If the program fails to completely uninstall all CiscoWorks Blue files and directories from the /opt/CSCOcb file structure, run uninstall.sh again.

Modifying Color Schemes for the Maps Motif Applications

After installation, you can modify the color scheme of the Maps Motif applications by copying the Color.schemename file in the /opt/CSCOcb/Xdefaults directory to the file named /opt/CSCOcb/Xdefaults/Color.

Here is an example that shows how to copy the Color.Rembrandt file as Color:

: # cd /opt/CSCOcb/Xdefaults
: # cp Color.Rembrandt Color

Running the Maps Applications with a Sample User

After installation is complete, the installation process creates a sample user with the username cwblue. The username cwblue is created without a password. To start a Maps application from the command line, you can do one of the following:

Create a password for the cwblue username.
Log in as the root user and use the switch username command to become user cwblue:

: # su - cwblue

Then you can start one of the Maps Motif applications using the cwb start command.

Note You must be the root user to start the server processes.

CiscoWorks Blue Maps Environment Variables

This section lists the environment variables that are set automatically by the CiscoWorks Blue Maps script (runprocess). Table 3-4 lists the environment variables, used by each application (for technical reference only).

Table 3-4 Maps and SNA View Environment Variables

Variable	Use and Default Value
CSCO_TVSPATH	CiscoWorks Blue Maps bitmap directory; the default is $CWBROOT/Xbm.
CVIEWROOT	CiscoView installation directory.
CWB-ALIVE-TIMEOUT	Discover-in-progress timeout to detect abnormal termination of discovery process.
CWB-CONNECT-TIMEOUT	Time required for discovery process to initially contact progress indicator window.
CWB_MAPNOT EXIST	Tells Maps application not to read the layout from a saved map file, which forces the application to create a new layout; by default it is not set. This variable is for use when you are instructed to create a new layout by the Cisco TAC to solve a layout problem.
CWBCSROOT	CiscoWorks Blue common code directory.
CWBROOT	CiscoWorks Blue Maps installation directory; set to the directory you specify during installation, usually /opt/CSCOcb.
CWB_DEFAULT_ LAYOUT	Sets the default layout of graphical maps; values can be C (circular), H (hierarchical), or S (symmetrical). The default value is H.
CWB_MIBFILE	Specifies the name of the MIB file; defaults to $CWBROOT/etc/mib.txt.
CWB_PROCESS_ REFRESH	Specifies the refresh interval, in seconds, for the Update Process window.
CWB_SERVER	Identifies the workstation on which the daemons run. The default is hostname.
CWB_UPDATE_ INTERVAL	Defines an interval to control map refresh requests. During this period, map changes are recorded but not displayed. When the interval expires, the map is refreshed. The default value is 10 seconds.
CWB_UPDATE_ SERVER	Identifies the workstation on which the cwbmonitord daemon runs. The default is $CWB_SERVER.
DBNAME	Name of the CiscoWorks Blue database, such as SNA.
DSQUERY	Name of the Sybase database server, such as CW_SYBASE.
HHHOME	HyperHelp installation directory for CiscoWorks Blue Maps help. The default is $CWBROOT/hyperhelp.
INSTALL_SOL_27	Allows installation on Solaris Version 7 when set to TRUE.
INSTALL_SOL_28	Allows installation on Solaris Version 8 when set to TRUE.
INSTALL_AIX_51	Allows installation on AIX Version 5.1 when set to TRUE.
LD_LIBRARY_ PATH	Set runtime library search path for Solaris.
LIB_PATH	Sets the runtime library search path for AIX.
NETMGTSYS	Indicates whether an NMS is integrated with CiscoWorks Blue. NONMS indicates no NMS is integrated.
NMSROOT	CiscoWorks installation directory.
PRINTER	Printer identification. The default is none; if printing maps is desired, set this before starting any Maps application.
SHLIB_PATH	Set runtime library search path for HP-UX.
SQLANY	Directory path to SQLAnywhere, such as /opt/CSCOcwbC/db.
SVHOME	CiscoWorks Blue the SNA Host component installation directory. The default is $CWBROOT/snahost.
SYBASE	Sybase installation directory, such as /opt/CSCOcwbC/db/ctlibs.
TERM	Specifies xterm terminal.
XAPPLRESDIR	CiscoWorks Blue Maps X resource directory. The default is /opt/CSCOcb/Xdefaults.

Table of Contents

Installing and Configuring CiscoWorks Blue

Upgrading to CiscoWorks Blue Release 3.0.1

Creating a Seed File from a Previous Software Release Database

Creating a Seed File in a Previous Release

Upgrading SNA View Configuration Files

Using CiscoWorks Blue Release 3.0.1 Workstation Software with a Previous SNA View Release of Mainframe Software

Saving the cwbinit File

Deinstalling Maps and SNA View from a Previous Release

Installing and Configuring CiscoWorks Blue

Installing CiscoWorks Blue Maps and SNA View

Installing from a Remote CD-ROM Drive

Installing from a Remote System

Installing the First CiscoWorks Blue for the First Time

Installing a Second CiscoWorks Blue Product

Installing the CiscoWorks Blue 3.0.1 Products

Applying the CiscoWorks Blue Licenses

Configuring CiscoWorks Blue

Using Default Values

Using the Configuration Procedure

Enabling DNS Lookups for Device Queries

Selecting DNS Lookup During Configuration

Selecting DNS Lookup with the doDNSSearch Variable

Starting the CiscoWorks Blue Processes

Finishing Installation

Creating a Seed File with DLSw Key Routers

Discovering the Routers

Running the Verification Program

Configuring the Host Connection

Creating and Deleting a Domain

Configuring Domain-Specific Parameters

Configuration Parameter Descriptions

Required Parameters

Parameters You Might Want to Customize

Parameters You Might Want to Accept

Configuring LU 6.2 Connectivity to the Mainframe

Preparing to Configure the SNA Host Component for Maps and SNA View

Configuring LU 6.2 Connectivity for the eNetwork Communications Server on AIX

Creating the sna_tps File on AIX

Configuring PARALLEL Mode on AIX

Configuring LU 6.2 Connectivity for SNAplus2 on HP-UX

Creating the sna_tps File on HP-UX

Configuring PARALLEL Mode on HP-UX

Configuring LU 6.2 Connectivity for SNAP-IX on Solaris

Creating the sna_tps File on Solaris

Configuring PARALLEL Mode on Solaris

Configuring LU6.2 Connectivity to Multiple Hosts

Configuring TCP/IP Connectivity to the Mainframe

Configuring TCP/IP Port Parameters

Sending Nonencrypted Data

Configuring Connectivity to Multiple Domains

Applying Licenses after Installation

Configuring CiscoWorks Blue after Installation

Deinstalling CiscoWorks Blue

Deinstalling CiscoWorks Blue From a Previous Release

Modifying Color Schemes for the Maps Motif Applications

Running the Maps Applications with a Sample User

CiscoWorks Blue Maps Environment Variables

I nstalling the CiscoWorks Blue 3.0.1 Products