cc/td/doc/product/atm/l2020/2020r231
hometocprevnextglossaryfeedbacksearchhelp
PDF

Table Of Contents

StreamView Software Release 2.3(1) for Solaris Installation and Upgrade Procedures

Installing StreamView to Run With HP OpenView

Upgrading StreamView for HP OpenView

Loading StreamView for HP OpenView

Setting Up a User Environment With HP OpenView

Setting Environment Variables for Bourne Shell and Derivatives

Setting Environment Variables for C Shell and Derivatives

Installing StreamView to Run Without HP OpenView

Upgrading StreamView Without HP OpenView

Loading StreamView Without HP OpenView

Setting Up a User Environment Without HP OpenView

Setting Environment Variables for Bourne Shell and Derivatives

Setting Environment Variables for C Shell and Derivatives

StreamView Environment Validation Check

Environment Validation Check

Command Line Options

Cisco Connection Online


StreamView Software Release 2.3(1) for Solaris Installation and Upgrade Procedures

March 25, 1997

Text Part Number: 78-4263-01 Rev. A0

These release notes provide installation and upgrade procedures for StreamView Software Release 2.3(1) for Solaris to be installed on a LightStream 2020 multiservice ATM switch (LS2020 switch).

You will install the StreamView network management software for Solaris onto a UNIX workstation using the 8mm tape provided. The UNIX workstation is used as the network management system (NMS) to configure, monitor, and control an LS2020 switch.

StreamView requires a UNIX workstation running SunOS 4.1.x (Solaris1.1.x) or SunOS 5.4 (Solaris 2.4) with 26MB RAM (additional 3MB RAM for each node in the database) and 90MB swap space.

Note Refer to the LightStream 2020 Site Planning and Cabling Guide for detailed information about the hardware and software requirements for a UNIX workstation.

The StreamView network management software allows you to perform the following tasks:

•Configure an LS2020 switch

•Monitor an LS2020 switch

•Generate a dynamic topological map of your LS2020 network when used with HP OpenView

•Run a remote CLI on an LS2020 switch

•Manage a network of LS2020 switches

•Run the StreamView start-up environmental validation check (only cfg, cfg_a, pvc, vli, and monitor)

With these installation procedures you may install StreamView to run either with or without HP OpenView.

The following table lists the facilities provided by the StreamView network management software and refers you to related LS2020 documents for more detailed information.

For Information aboutє
See theє

Using the configurator

LightStream 2020 Configuration Guide

Using the CLI, and the StreamView monitor and topology map

LightStream 2020 Network Operations Guide

CLI descriptions and command syntax

LightStream 2020 CLI Reference Manual

LynxOS commands

LightStream 2020 NP O/S Reference Manual

LS2020 SNMP management information base (MIB)

LightStream 2020 Network Operations Guide and the LightStream 2020 CLI Reference Manual


Installing StreamView to Run With HP OpenView

Use this procedure to install either a new version or an upgrade of the StreamView network management software onto a UNIX workstation running HP OpenView. You must be running at least Version 3.3 of HP OpenView to run the StreamView network management software. This procedure assumes that HP OpenView is already installed and operating properly on a UNIX workstation.

Upgrading StreamView for HP OpenView

If you installed an earlier version of StreamView with HP OpenView, you need to be running at least Version 3.3 of HP OpenView to run the StreamView network management software with HP OpenView.

The StreamView network management software requires the HP OpenView OVIC utility version 1.4 or later. To verify the version number, execute the following command at the shell prompt on your UNIX workstation:

# cat /usr/OV/install/system/OVIC/ovindex

Release 1.4 is indicated by the line cid: ov1.4 in this file.

Loading StreamView for HP OpenView

The StreamView network management software portion of the LS2020 software includes the following modules: the configurator (cfg, cfg_a, pvc, vli), the monitor, and the topology map. The CLI and the LS2020 enterprise-specific MIB are packaged with these modules.

When installing the StreamView network management software, use the ovinstall command to

•Check the HP OpenView installation utilities version

•Create the /usr/OV/bin/ls_bin directory

•Update several HP OpenView directories with LS2020 registration and bitmap files

•Load the enterprise-specific MIB into the /usr/OV/snmp_mibs directory and install it under HP OpenView

•Create the /usr/OV/databases/ls directory for the MIB database

To load the Streamview network management software, perform the following steps:

Step 1 Log in to the UNIX workstation as root. If logging in as root is disabled, issue the following command to give yourself root privileges:

$ su password:<root password>

Step 2 Create a user account called npadmin, if it does not already exist.

The CLI uses the password for the npadmin account as the password for the CLI protected mode. If no npadmin account has been defined for the workstation, the CLI uses the root password as the CLI protected-mode password.

Step 3 Ensure that the /usr/OV/bin directory is in your path (the installation procedure uses this directory). To display your path, issue the following command at the SunOS prompt:

# echo $PATH

To set your path in a Bourne shell or a bash shell, issue the following command:

# PATH=$PATH:/usr/OV/bin # export PATH

To set your path in a C shell (csh), issue the following command:

# setenv PATH ${PATH}:/usr/OV/bin

Step 4 Insert the 8mm tape containing the StreamView network management software into the UNIX workstation tape drive.

Step 5 Extract the StreamView modules using the ovinstall command. This process takes from 5 to 15 minutes for installation of the modules and their associated files.

Note For an example of StreamView output generated using the HP OpenView commands, refer to the LightStream 2020 Installation Guide, "StreamView Output Samples" appendix.

To extract the StreamView configurator module, enter the following command:

# ovinstall -r -p LS-CONFIGURE - - -d <tape-drive>

Where <tape drive> is /dev/rst0, unless your tape drive has been configured to use a different device (for example, /dev/rst1 or /dev/rst2). The -r switch allows the program to overwrite an existing installation. If you specify an incorrect device in the ovinstall command, the installation process terminates immediately and returns the following message or its equivalent:

"ovinstall: cannot install product definition for LS-CONFIGURE"

Note The ovinstall command creates a log file named /tmp/update.log. If a problem occurs during the installation process, you can examine this file to determine what may have gone wrong. To open this file for inspection, issue the following command: more /tmp/update.log. An example of this file is provided in the LightStream 2020 Installation Guide , "StreamView Output Samples" appendix.

To extract the StreamView monitor module, enter the following command:

# ovinstall -r -p LS-MONITOR - - -d <tape-drive>

To extract the StreamView topology map software, enter the following:

# ovinstall -r -p LS-TOPOMAP -- -d <tape-drive>

Step 6 Update the HP OpenView Fields database with StreamView fields using the following command:

# ovw -fields

Step 7 Verify that the network management software modules have been properly installed using the following command:

# ovw -verify

The verify program takes less than a minute to run and prints the names of the objects that it verifies. If the verification process fails, an error message displays on the screen. In this case, call your Cisco service representative for assistance.

Step 8 Check the status of HP OpenView daemons using the following command:

# ovstatus

If the ovstatus command returns the message ovstatus: ovspnd is not running; use ovstart to start ovspnd, enter the following command from user ID root to start OV daemons:

# ovstart

Step 9 Execute the xnmsnmpconf command at the shell prompt to update variables associated with the SNMP community.

This command displays the SNMP configuration screen. When the screen is displayed, double-click on the default parameters field (which contains default values in text fields). Modify the following field values to read as shown:

Port (remote) 161
Timeout 6.0
Retry 2

The default polling interval is 5 minutes. The polling interval determines how long it will be before the display indicates changes in the network. Setting the polling interval to a value less than 5 minutes causes additional SNMP traffic to be generated and is, therefore, not advised.

By default, LS2020 nodes require the use of the write community for SNMP set operations, as indicated below:

set community: write

However, you may choose to use another name for the community that has read/write privileges, or you may choose to allow SNMP set operations from any community.

To allow such operations, however, you must configure the HP OpenView environment appropriately using the xnmsnmpconf command.

If you do not use the default communities, you must change the files at the LS2020 nodes to conform to the behavior of HP OpenView.

For more information about changing default SNMP community names, refer to the LightStream 2020 Installation Guide , "Set-up Procedures" chapter.

Step 10 Verify that the /etc/services file contains the following lines:

snmp 161/udp snmp-trap 162/udp

If these lines are not present in the /etc/services file, create them. To do so, as user ID root, open the /etc/services file.

Insert the snmp 161/udp and snmp-trap 162/udp lines in the appropriate location(s) in the /etc/services file and close the file.

The installation of the network management software is now complete. The next section describes how to create a user environment for running the StreamView modules with HP OpenView.

Note If the user environment variables are not properly set, the software will not properly find or use the StreamView applications. It may be necessary to close all HP OpenView windows and restart HP OpenView with the correct environment.

Setting Up a User Environment With HP OpenView

This section describes how to set up the user environment to run the StreamView modules with HP OpenView using the Bourne shell and its derivatives (sh and bash) and the C shell (csh). For clarity, the set-up procedures for the Bourne shells and the C shell are discussed under separate headings below. Other shells may differ in details; in the case of another shell, consult the applicable documentation for that shell.

Every user intending to run StreamView with HP OpenView must perform this procedure.

Note Before following this procedure, you should have already installed the StreamView network management software onto a UNIX workstation, as described in the preceding section, " Installing StreamView to Run With HP OpenView."

Before setting up the user environment with HP OpenView, determine the type of shell each user is using.

In a network file system (NFS) environment that uses the network information services (NIS) facility, enter the following command:

# ypmatch <username> passwd

In an environment that does not use the NIS facility, enter the following command:

# egrep <username> /etc/passwd

The shell can be identified from the last field of the password entry, as shown in the following example:

jjones:o@elQMkzZv7o F:10563:312:Jon Jones:/home/jjones:/bin/bash

Setting Environment Variables for Bourne Shell and Derivatives

To set up the network management software to operate under HP OpenView and the Bourne shells, sh and bash, perform the following procedures:

Step 1 From your home directory, edit the .profile file or the .bash_profile file that is read by the shell at login.

Add the following lines to the end of the file:

PATH=$PATH:/usr/OV/bin/ls_bin LSC_DATABASE=/usr/OV/databases/ls/configure.netdb LSC_CFGLOGPATH=/usr/OV/log LSC_CFGTCPPORT=6789 XKEYSYMDB=<pathname>/XKeysymDB NMSROOT=<CiscoView location, if present>
XVTPATH=/usr/OV/bin/ls_bin
export PATH LSC_DATABASE LSC_CFGLOGPATH LSC_CFGTCPPORT XKEYSYMDB NMSROOT XVTPATH

Note To determine the <pathname> for XKEYSYMDB in the second to last line above, consult your system administrator. The file XKeysymDB should be in the subdirectory lib, lib/X11, or /usr/openwin/lib under the directory containing your X Windows executables. You can use the command find / -name XKeysymDB -print to search for the XKeysymDB file. However, the search process may be lengthy and may disclose multiple copies of the file. Also, note the upper- and lower-case characters in the XKeysymDB filename; this case sensitivity is critical. If XKEYSYMDB is incorrectly defined, that is, if no file named XKeySymDB is found where XKEYSYMDB points, error output is directed to the standard error output device (STDERR). A sample of such output is shown in the LightStream 2020 Installation Guide , "StreamView Output Samples" appendix under the heading " Error Output When XKEYSYMDB Is Undefined."

Step 2 Determine whether a UIDPATH variable is already set in your login environment by issuing the following command:

% echo $UIDPATH

Note Some window managers require a UIDPATH entry. For example, Solaris 2.4 with the X11R5 Motif window manager use the path /opt/SUNWmfdm/%U. If this UIDPATH entry is required, ensure that it is present before you proceed.

Step 3 If the system displays a search path in Step 2, add the following line to the end of the .profile file or the .bash_profile file:

UIDPATH=$UIDPATH:/usr/OV/bin/ls_bin/%U export UIDPATH

Otherwise, if the system displays the message "UIDPATH: unbound variable" or displays no message, add the following line to the .profile file or the .bash_profile file:

UIDPATH=/usr/OV/bin/ls_bin/%U export UIDPATH

Step 4 Determine whether an XFILESEARCHPATH variable is already set in your login environment by issuing the following command:

% echo $XFILESEARCHPATH

Step 5 If the system displays a search path in Step 4, add the following line to the end of the .profile file or the .bash_profile file:

XFILESEARCHPATH=$XFILESEARCHPATH:/usr/OV/%T/%N%S export XFILESEARCHPATH

Otherwise, if the system displays the message XFILESEARCHPATH: unbound variable or displays no message, use the following command to check for the existence of the referenced directory.

% ls /usr/openwin/lib/app-defaults/

If this directory exists, add the following lines to the end of the .profile or .bash_profile file:

XFILESEARCHPATH=/usr/openwin/lib/%T/%N%S:/usr/OV/%T/%N%S export XFILESEARCHPATH

Use the following command to check that the referenced directory exists:

% ls /usr/lib/X11/app-defaults/

If the previous directory does not exist, but this directory does exist, add the following lines to the end of the .profile or .bash_profile file:

XFILESEARCHPATH=/usr/lib/X11/%T/%N%S:/usr/OV/%T/%N%S export XFILESEARCHPATH

If both of the above directories exist, add the following lines to the end of the .profile or .bash_profile file:

XFILESEARCHPATH=/usr/openwin/lib/%T/%N%S:/usr/lib/X11/%T/%N%S:/usr/OV/%T/%N%S export XFILESEARCHPATH

If neither of the above directories exists, call your network administrator or Cisco Systems Customer Support for assistance.

Step 6 If this is a new HP OpenView user, check the user's home directory for the existence of the .Xdefaults file (or its equivalent, .Xresources). If this file contains data, proceed with Step 7.

If this file exists but contains no data, append the contents of the /usr/OV/newconfig/xdefaults file to the user's .Xdefaults file by issuing the following command sequence:

% mv .Xdefaults Xdef.sav
% cat Xdef.sav /usr/OV/newconfig/xdefaults > .Xdefaults

This step gives you access to the screen fonts and application colors needed for display purposes.

If you need to revert to the old .Xdefaults file, you can find its contents in the backup file Xdef.sav.

If the .Xdefaults file does not exist in the user's home directory, issue the following command to create it:

% cp /usr/OV/newconfig/xdefaults .Xdefaults

A sample .Xdefaults file is shown in the LightStream 2020 Installation Guide , "StreamView Output Samples" appendix.

Step 7 Issue the following command from the UNIX workstation to start HP OpenView:

% ovw

If, after you issue the ovw command, the message ovw: cannot connect to database is returned, issue the following command:

% ovstatus

This command reports the nature of the problem, as shown below:

ovstatus: ovspnd is not running; use ovstart to start ovspnd

Log in as root and issue the ovstart command as shown below:

# ovstart

As an alternative, if you want to start HP OpenView and run it in background mode while keeping the current window active, issue the following command:

% ovw&

In background mode, the ovw process is fully usable.

Note If LS2020 applications are invoked from within HP OpenView, the applications inherit the environment and privileges of the user account from which the ovw command is issued. When the StreamView configurator is invoked under HP OpenView, the access permissions for the configuration database file created by this module correspond to the privileges of the user issuing the ovw command.

Step 8 If the following error message appears in the parent window from which you started HP OpenView in Step 8, the XFILESEARCHPATH is not set correctly:

ovw: Xt Warning: Cannot convert string "helvr14" to type FontStruct
ovw: Xt Warning: Cannot convert string "helvr12" to type FontStruct
ovw: Xt Warning: Cannot convert string "helvr10" to type FontStruct
ovw: Xt Warning: Cannot convert string "helvr08" to type FontStruct

Shut down HP OpenView, revert to Step 5 above, and add /usr/OV/%T/%N%S to the XFILESEARCHPATH. Continue from that point with Step 9 and Step 7 to restart HP OpenView.

The first time the StreamView configurator tool (cfg) is executed, the database is created automatically with the name specified by LSC_DATABASE, it has the extensions .dir and .pag and the file permissions of the first user.

All users who will create or modify LS2020 node configurations must be in the same UNIX group. If they are not in the same group, such users will be limited to read-only access to the database and, therefore, will not be able to update LS2020 nodes with configuration information from the global database.

For example, if the operations group has read-only access to the global database, user ID root should issue the following commands to ensure that the operations group has required read/write access privileges to the file configure.netdb:

# cd /usr/OV/databases/ls
# chgrp <ops-group> configure.netdb

Where <ops-group> is the value of the group to be used on the system.

Step 9 Any HP OpenView user logged in during the installation process should now log out and log in again to use the new environment variables.

A new feature in Software Release 2.3.1 is the StreamView environment check utility. It checks for correct settings of environment variables in the user's environment. The utility reports status, any warnings, and any fatal errors in a log file. Information about the StreamView environmental check utility can be found later in this document.

Setting Environment Variables for C Shell and Derivatives

To set up network management software to operate under HP OpenView and the C shell, perform the following steps:

Step 1 From your home directory, edit the .cshrc file that is read by the C shell on login. Add the following lines to the end of the file:

setenv PATH ${PATH}:/usr/OV/bin/ls_bin setenv LSC_DATABASE /usr/OV/databases/ls/configure.netdb setenv LSC_CFGLOGPATH /usr/OV/log setenv LSC_CFGTCPPORT 6789 setenv XKEYSYMDB <pathname>/XKeysymDB setenv NMSROOT <CiscoView location, if present> setenv XVTPATH /usr/OV/bin/ls_bin

Note To determine the <pathname> for XKEYSYMDB in the second to last line above, consult your system administrator. The file XKeysymDB should be in the subdirectory lib, lib/X11, or /usr/openwin/lib under the directory containing your X Windows executables. You can use the command find / -name XKeysymDB -print to search for the XKeysymDB file. However, be aware that the search process may be lengthy and may find multiple copies of the file. Also, note the upper- and lower-case conventions in the XKeysymDB file name; this case sensitivity is critical. If XKEYSYMDB is incorrectly defined, that is, no file named XKeySymDB is found where XKEYSYMDB points, error output is directed to the standard error output device (STDERR). A sample of the output is shown in the LightStream 2020 Installation Guide , "StreamView Output Samples" appendix under the heading " Error Output When XKEYSYMDB Is Undefined."

Step 2 Determine whether a UIDPATH variable is already set in your login environment by issuing the following command:

% echo $UIDPATH

Note Some window managers require a UIDPATH entry. For example, Solaris 2.4 with the X11R5 Motif window manager use the path /opt/SUNWmfdm/%U. If this UIDPATH entry is required, ensure that it is present before you proceed.

Step 3 If the system displays a search path in Step 2, add the following line to the end of the .cshrc file:

setenv UIDPATH ${UIDPATH}:/usr/OV/bin/ls_bin/%U

Otherwise, if the system displays the message UIDPATH: Undefined variable or displays no message, add the following line to the end of the .cshrc file:

setenv UIDPATH /usr/OV/bin/ls_bin/%U

Step 4 Determine whether an XFILESEARCHPATH variable is already set in your login environment by issuing the following command:

% echo $XFILESEARCHPATH

Step 5 If the system displays a search path in Step 4, add the following line to the end of the .cshrc file:

setenv XFILESEARCHPATH ${XFILESEARCHPATH}:/usr/OV/%T/%N%S

Otherwise, if the system displays the message XFILESEARCHPATH: undefined variable or displays no message, use the following command to check that the following directory exists:

% ls /usr/openwin/lib/app-defaults/

If this directory exists, add the following line to the end of the .cshrc file:

setenv XFILESEARCHPATH /usr/openwin/lib/%T/%N%S:/usr/OV/%T/%N%S

Use the following commands to check for the existence of the referenced directory:

% ls /usr/lib/X11/app-defaults/

If the first directory does not exist, but this second directory does exist, add the following line to the end of the .cshrc file:

setenv XFILESEARCHPATH /usr/lib/X11/%T/%N%S:/usr/OV/%T/%N%S

If both of the directories exist, add the following line to the end of the .cshrc file:

setenv XFILESEARCHPATH /usr/openwin/lib/%T/%N%S:/usr/lib/X11/%T/%N%S:\ /usr/OV/%T/%N%S

If neither of the directories exists, call your network administrator or Cisco Systems Customer Support for assistance.

Step 6 If this is a new HP OpenView user, check the user's home directory for the existence of the .Xdefaults file (or its equivalent .Xresources). If this file contains data, proceed with Step 7.

If this file exists but contains no data, append the contents of the /usr/OV/newconfig/xdefaults file to the user's .Xdefaults file by issuing the following command sequence:

% mv .Xdefaults Xdef.sav
% cat Xdef.sav /usr/OV/newconfig/xdefaults > .Xdefaults

This step gives you access to the screen fonts and application colors needed for display purposes.

If you need to revert to the old .Xdefaults file, you can find its contents in the backup file Xdef.sav.

If the .Xdefaults file does not exist in the user's home directory, issue the following command to create it:

% cp /usr/OV/newconfig/xdefaults .Xdefaults

A sample .Xdefaults file is shown in the LightStream 2020 Installation Guide , "StreamView Output Samples" appendix.

Step 7 Issue the following command from the UNIX workstation to start HP OpenView:

% ovw

If, after you issue the ovw command, the message ovw: cannot connect to database is returned, issue the following command:

% ovstatus

This command reports the nature of the problem, as shown below:

ovstatus: ovspnd is not running; use ovstart to start ovspnd

Log in as root and issue the ovstart command, as shown below:

# ovstart

As an alternative, if you want to start HP OpenView and run it in background mode while keeping the current window active, issue the following command:

% ovw&

In background mode, the ovw process is fully usable.

Note If you invoke LS2020 applications from within HP OpenView, the applications inherit the environment and privileges of the user account from which the ovw command is issued. When the StreamView configurator is invoked under HP OpenView, the access permissions for the configuration database file created by this module correspond to the privileges of the user issuing the ovw command.

Step 8 If the following error message appears in the parent window from which you started HP OpenView in Step 7, the XFILESEARCHPATH is not set correctly:

ovw: Xt Warning: Cannot convert string "helvr14" to type FontStruct
ovw: Xt Warning: Cannot convert string "helvr12" to type FontStruct
ovw: Xt Warning: Cannot convert string "helvr10" to type FontStruct
ovw: Xt Warning: Cannot convert string "helvr08" to type FontStruct

In this case, shut down HP OpenView, revert to Step 5, and add /usr/OV/%T/%N%S to the XFILESEARCHPATH. Continue from that point with Step 9 and Step 7 to restart HP OpenView.

The first time the StreamView configurator tool (cfg) is executed, the database is created automatically with the name specified by LSC_DATABASE, it has the extensions .dir and .pag and the file permissions of the first user.

All users who will create or modify LS2020 node configurations must be in the same UNIX group. If not, such users will be limited to read-only access to the database and, therefore, will not be able to update LS2020 nodes with configuration information from the global database.

For example, if the operations group has read-only access to the global database, user ID root should issue the following commands to ensure that the operations group has required read-write access privileges to the file configure.netdb:

# cd /usr/OV/databases/ls
# chgrp <ops-group> configure.netdb

Where <ops-group> is the value of the group to be used on the system.

Step 9 Any HP OpenView user logged in during the installation process should now log out and log in again to use the new environment variables.

A new feature in Software Release 2.3.1 is the StreamView environment check utility. It checks for correct settings of environment variables in the user's environment. The utility reports status, any warnings, and any fatal errors in a log file. Information about the StreamView environmental check utility, can be found later in this document.

Installing StreamView to Run Without HP OpenView

Use this procedure to install either a new version or an upgrade of the LS2020 StreamView network management software onto a UNIX workstation that is not running HP OpenView.

Upgrading StreamView Without HP OpenView

If you installed an earlier version of StreamView, verify that you have enough disk space available before upgrading to StreamView for Solaris Software Release 2.3.1.

Loading StreamView Without HP OpenView

When loading StreamView without HP OpenView, the StreamView network management software portion of the LS2020 software includes the following modules: the configurator (cfg, cfg_a, pvc, vli), the monitor, and the topology map. The CLI and the LS2020 enterprise-specific MIB are packaged with all these modules.

To load the StreamView network management software to operate stand-alone without HP OpenView, perform the following steps:

Step 1 Log in to the UNIX workstation as root. If logging in as root is disabled, issue the following command to give yourself root privileges:

$ su password: <root password>

Step 2 Create a user account called npadmin, if one does not already exist.

The CLI uses the password for the npadmin account as the password for the CLI protected mode. If no npadmin account is defined for the UNIX workstation, the CLI uses the root password as the CLI protected mode password.

Step 3 Back up your ovsnmp.conf file if you have customized your existing configuration files and you wish to preserve them for a subsequent installation or upgrade of the network management software.

For example, if you have already installed Software Release 2.3.1 of the StreamView network management software in a non-HP OpenView environment and you need to re-install the software for some reason, you should first back up any configuration files you have customized since the previous installation.

Specifically, if you customize the file /usr/LightStream-2.3.1/templates/ovsnmp.conf, you should save a backup copy of this file and restore it after the installation has been completed (see Step 7).

To back up the ovsnmp.conf file, change to the proper directory and copy the configuration file.

# cd /usr/LightStream-2.3.1/templates # cp ovsnmp.conf ovsnmp.conf.custom

Issue the list (ls) command to display the existing configuration files.

# ls ovsnmp.conf*

This command lists the following configuration files:

ovsnmp.conf
ovsnmp.conf.custom

Step 4 Change to the root directory by issuing the following command:

# cd /

Step 5 Insert the 8mm tape containing the StreamView network management software into the UNIX workstation tape drive.

Step 6 Issue the following commands to rewind and fast forward to the proper location and extract the files from tape:

# mt -f <tape-drive> rew # mt -f <tape-drive> fsf 4 # tar xvpf <tape-drive>

Where <tape-drive> is /dev/nrst0, unless your tape drive has been configured to use a different port, for example, /dev/nrst1, or /dev/nrst2.

Note It is important to include the letter n "no rewind" as the leading character in the tape drive parameter (for example, nrst0 for <tape drive> rst0). If you omit this character, you will not be able to read the tape.

The extraction process, which takes from 10 to 20 minutes to complete, creates the following directory structures:

/usr/LightStream-2.3.1 /usr/LightStream-2.3.1/bin /usr/LightStream-2.3.1/db /usr/LightStream-2.3.1/etc /usr/LightStream-2.3.1/hyperhelp /usr/LightStream-2.3.1/lib /usr/LightStream-2.3.1/log /usr/LightStream-2.3.1/mib /usr/LightStream-2.3.1/templates

Step 7 Restore your ovsnmp.conf file, if necessary.

If you saved a backup copy of your ovsnmp.conf file in Step 3, determine whether differences exist between your backup copy of the ovsnmp.conf.custom file and the new ovsnmp.conf file.

If no differences between these files are reported, the files are identical. On the other hand, if differences are reported, save the distribution copy of the ovsnmp.conf file by issuing the following command:

# mv ovsnmp.conf ovsnmp.conf.orig

Copy your custom configuration file to ovsnmp.conf by issuing the following command:

# cp ovsnmp.conf.custom ovsnmp.conf

Verify your file listing:

# ls ovsnmp.conf* ovsnmp.conf ovsnmp.conf.custom ovsnmp.conf.orig

Step 8 Edit the /etc/services file.Verify that the /etc/services file contains the following entries:

snmp 161/udp snmp-trap 162/udp

If this entry is not present in the /etc/services file, create the entries and close the file.

The installation of the StreamView network management software is now complete. The next section describes how to set up the UNIX workstation environment for using the StreamView network management software in a non-HP OpenView environment.

Setting Up a User Environment Without HP OpenView

This section describes how to set up the StreamView application to run on the UNIX workstation without HP OpenView. Each LS2020 user intending to run StreamView network management software onto the UNIX workstation without HP OpenView must complete the procedures in this section.

It is assumed that you have already installed the StreamView application on a UNIX workstation to operate without HP OpenView, as described in the preceding section, " Installing StreamView to Run Without HP OpenView."

Note Release 2.3.1 is in a new directory structure. Existing users must update their environmental settings.

This section provides instructions for setting up the StreamView user environment for the Bourne shell and its derivatives (sh and bash) and the C shell (csh). For convenience and clarity, the set-up procedures for these shells are described under separate headings below.

Note that other shells may differ in details; in the case of another shell, consult the appropriate shell documentation for additional information.

Determine which type of shell to use:

In an network file system (NFS) environment using the network information services (NIS) facility, enter the following command:

ypmatch <username> passwd

In an environment that does not use the NIS facility, enter the following command:

egrep <username> /etc/passwd

The last field of the output that results from either of the above commands identifies the shell in use, as shown in the following example:

jjones:o@elQMkzZv7oF:10563:312:Jon Jones:/home/jjones:/bin/bash

Setting Environment Variables for Bourne Shell and Derivatives

To set up the StreamView network management software to operate without HP OpenView under the Bourne shells, sh and bash, perform the following procedure:

Step 1 Each StreamView user must define several environment variables. To do so, go to your home directory and edit the .profile file or the .bash_profile file that the Bourne shell reads at the time of login.

Step 2 Determine whether a UIDPATH variable is already set in your login environment by entering the following command:

% echo $UIDPATH

Note Some window managers require a UIDPATH entry. For example, Solaris 2.4 with the X11R5 Motif window manager use the path /opt/SUNWmfdm/%U. If this UIDPATH entry is required, ensure that it is present before you proceed.

Step 3 If the system displays a search path, add the following lines to the end of the .profile file or the .bash_profile file:

PATH=$PATH:/usr/LightStream-2.3.1/bin UIDPATH=$UIDPATH:/usr/LightStream-2.3.1/bin/%U LSC_DATABASE=/usr/LightStream-2.3.1/db/configure.netdb LSC_CFGLOGPATH=/usr/LightStream-2.3.1/log LSC_CFGTCPPORT=6789 OVSNMP_CONF_FILE=/usr/LightStream-2.3.1/templates/ovsnmp.conf XKEYSYMDB=<pathname>/XKeysymDB XVTPATH=/usr/LightStream-2.3.1/bin export PATH UIDPATH LSC_DATABASE LSC_CFGLOGPATH LSC_CFGTCPPORT OVSNMP_CONF_FILE\ XKEYSYMDB XVTPATH

Note To determine the <pathname> for XKEYSYMDB shown in the Bourne shell procedures below, consult your system administrator. The file XKeysymDB should be in the subdirectory lib, lib/X11, or /usr/openwin/lib under the directory containing your X Windows executables. You can use the command find / -name XKeysymDB -print to search for the XKeysymDB file. However, be aware that the search process may be lengthy and may disclose multiple copies of the file. Also, note the upper- and lower-case characters in the XKeysymDB filename; this case sensitivity is critical. If XKEYSYMDB is incorrectly defined, that is, no file named XKeySymDB is found where XKEYSYMDB points, error output is directed to the standard error output device (STDERR). A sample of such output is shown in the LightStream 2020 Installation Guide , "StreamView Output Samples" appendix under the heading " Error Output When XKEYSYMDB Is Undefined."

After adding the data called for in this step to the appropriate file, skip to Step 5.

Step 4 If the system displays UIDPATH: unbound variable or no message in response to the echo $UIDPATH command, add the following lines to the end of the .profile file or the .bash_profile file:

Note Path is order sensitive. If multiple StreamView entries are in the path, the first one will be executed. Operating system and window manager entries must precede StreamView entries.

PATH=$PATH:/usr/LightStream-2.3.1/bin UIDPATH=/usr/LightStream-2.3.1/bin/%U LSC_DATABASE=/usr/LightStream-2.3.1/db/configure.netdb LSC_CFGLOGPATH=/usr/LightStream-2.3.1/log LSC_CFGTCPPORT=6789 OVSNMP_CONF_FILE=/usr/LightStream-2.3.1/templates/ovsnmp.conf XKEYSYMDB=<pathname>/XKeysymDB XVTPATH=/usr/LightStream-2.3.1/bin export PATH UIDPATH LSC_DATABASE LSC_CFGLOGPATH LSC_CFGTCPPORT OVSNMP_CONF_FILE\ XKEYSYMDB XVTPATH

Continue with Step 5.

Step 5 Check the user's home directory for the existence of the .Xdefaults file. If this file is present and contains data, skip to Step 6.

If this file exists but contains no data, append the contents of the /usr/LightStream-2.3.1/templates/xdefaults file to the user's .Xdefaults file by issuing the following commands:

% mv .Xdefaults Xdef.sav
% cat Xdef.sav /usr/LightStream-2.3.1/templates/xdefaults > .Xdefaults

This step gives you access to the screen fonts and application colors needed for display purposes.

If you need to revert to the old .Xdefaults file, you can find its contents in the backup file Xdef.sav.

If the .Xdefaults file does not exist in the user's home directory, issue the following command to create it:

% cp /usr/LightStream-2.3.1/templates/xdefaults .Xdefaults

A sample .Xdefaults file is shown in the LightStream 2020 Installation Guide , "StreamView Output Samples" appendix.

Step 6 By default, LS2020 nodes require the use of the write community for SNMP set operations. You may choose to use another name for your community with read/write access privileges, or you may choose to allow SNMP set operations from any community.

For StreamView to successfully read and write to an LS2020 switch, the StreamView community strings must match the strings defined on the LS2020 itself.

If you change the community name, you must kill the cfg_a process for the changes to take effect. The process will be restarted the next time you download a configuration.

To kill the cfg_a process, perform the following:

a. Log in as root.

b. At the prompt, type

% ps -ax | grep cfg_a

c. Find the PID number for the cfg_a in the resulting display, then type

% kill -9 <pid# of cfg_a>

Note If you change a community name in the ovsnmp.conf file, you must also change the community name on the LS2020 node. For more information about changing community names, refer to the LightStream 2020 Installation Guide , "Set-up Procedures" chapter.

To change the SNMP community names in your UNIX environment:

a. edit the file /usr/LightStream-2.3.1/templates/ovsnmp.conf

b. kill the cfg_a process using the above procedure

c. change the files on each LS2020 node to conform to your workstation's behavior

To configure this snmp communities option in a UNIX workstation environment, edit the file /usr/LightStream-2.3.1/templates/ovsnmp.conf, or change the files at each LS2020 node to conform to your workstation's behavior. Use a text editor such as emacs or vi to modify the file. The file itself contains instructions for formatting each entry.

Step 7 Any user logged in during the installation and configuration process should now log out and log in again to activate the new environment variables.

Note that the first time the StreamView configurator tool (cfg) is executed, the database is created automatically with the name specified by LSC_DATABASE, with the extensions .dir and .pag and the file permissions of the first user.

All users who will create or modify LS2020 node configurations must be in the same UNIX group. If they are not in the same group, users will be limited to read-only access to the database and, therefore, will not be able to update LS2020 nodes with configuration information from the global database.

For example, if the operations group has read-only access to the global database, user ID root should issue the following commands to ensure that the operations group has the required read/write access privileges to the file configure.netdb:

# cd /usr/LightStream-2.3.1/db
# chgrp <ops-group> configure.netdb

Where <ops-group> represents the value of the group to be used on the system.

A new feature in Software Release 2.3.1 is the StreamView environment check utility. It checks for correct settings of environment variables in the user's environment. The utility reports status, any warnings, and any fatal errors in a log file. Information about the StreamView environmental check utility, can be found later in this document.

Setting Environment Variables for C Shell and Derivatives

To set up the network management software applications to operate without HP OpenView under the C shell, perform the following steps:

Step 1 From your home directory, edit the .cshrc file that is read by the C shell on login. Add the following lines to the end of the file:

setenv PATH ${PATH}:/usr/LightStream-2.3.1/bin setenv LSC_DATABASE /usr/LightStream-2.3.1/db/configure.netdb setenv LSC_CFGLOGPATH /usr/LightStream-2.3.1/log setenv LSC_CFGTCPPORT 6789 setenv OVSNMP_CONF_FILE /usr/LightStream-2.3.1/templates/ovsnmp.conf setenv XKEYSYMDB <pathname>/XKeysymDB setenv XVTPATH /usr/LightStream-2.3.1/bin

Note To determine the <pathname> for XKEYSYMDB in the second to last line above, consult your system administrator. The file XKeysymDB should be in the subdirectory lib, lib/X11, or /usr/openwin/lib under the directory containing your X Windows executables. You can use the command find / -name XKeysymDB -print to search for the XKeysymDB file. However, be aware that the search process may be lengthy and may find multiple copies of the file. Also, note the upper- and lower-case conventions in the XKeysymDB file name; this case sensitivity is critical. If XKEYSYMDB is incorrectly defined, that is, no file named XKeySymDB is found where XKEYSYMDB points, error output is directed to the standard error output device (STDERR). A sample of such output is shown in the LightStream 2020 Installation Guide , "StreamView Output Samples" appendix under the heading " Error Output When XKEYSYMDB Is Undefined."

Step 2 Determine whether a UIDPATH variable is already set in your login environment by issuing the following command:

% echo $UIDPATH

Note Some window managers require a UIDPATH entry. For example, Solaris 2.4 with the X11R5 Motif window manager use the path /opt/SUNWmfdm/%U. If this UIDPATH entry is required, ensure that it is present before you proceed.

If the system displays the message UIDPATH: Undefined variable or displays no message, add the following line to the end of the .cshrc file:

setenv UIDPATH /usr/LightStream-2.3.1/bin/%U

Step 3 If the system displays a search path in Step 2, add the following line to the end of the .cshrc file:

setenv UIDPATH ${UIDPATH}:/usr/LightStream-2.3.1/bin/%U

Step 4 Check the user's home directory for the existence of the .Xdefaults file (or its equivalent .Xresources). If this file contains data, proceed with Step 5.

If this file exists but contains no data, append the contents of the /usr/LightStream-2.3.1/templates/xdefaults file to the user's .Xdefaults file by issuing the following command sequence:

% mv .Xdefaults Xdef.sav
% cat Xdef.sav /usr/LightStream-2.3.1/templates/xdefaults > .Xdefaults

This step gives you access to the screen fonts and application colors needed for display purposes.

If you need to revert to the old .Xdefaults file, you can find its contents in the backup file Xdef.sav.

If the .Xdefaults file does not exist in the user's home directory, issue the following command to create it:

% cp /usr/LightStream-2.3.1/templates/xdefaults .Xdefaults

A sample .Xdefaults file is shown in the LightStream 2020 Installation Guide , "StreamView Output Samples" appendix.

Step 5 By default, LS2020 nodes require the use of the write community for SNMP set operations. You may choose to use another name for your community with read/write access privileges, or you may choose to allow SNMP set operations from any community.

If you change the community name, you must kill the cfg_a process for the changes to take effect. The process will be restarted the next time you download a configuration.

To kill the cfg_a process, perform the following:

a. Log in as root.

b. At the prompt, type

% ps -ax|grep cfg_a

c. Find the PID number for the cfg_a in the resulting display, then type

% kill -9 <pid# of cfg_a>

Note If you change a community name in the ovsnmp.conf file, you must also change the community name on the LS2020 node. For more information about changing community names, refer to the LightStream 2020 Installation Guide , "Set-up Procedures" chapter.

To change the SNMP community names in your UNIX environment:

a. edit the file /usr/LightStream-2.3.1/templates/ovsnmp.conf

b. kill the cfg_a process using the above procedure

c. change the files on each LS2020 node to conform to your workstation's behavior

To configure this snmp communities option in a UNIX workstation environment, edit the file /usr/LightStream-2.3.1/templates/ovsnmp.conf, or change the files at each LS2020 node to conform to your workstation's behavior. Use a text editor such as emacs or vi to modify the file. The file itself contains instructions for formatting each entry.

Step 6 Any user logged in during the installation and configuration process should now log out and log in again to use the new environment variables.

The first time the StreamView configurator tool (cfg) is executed, the database is created automatically with the name specified by LSC_DATABASE, it has the extensions .dir and .pag and the file permissions of the first user.

All users who will create or modify LS2020 node configurations must be in the same UNIX group. If they are not, such users will be limited to read-only access to the database and, therefore, will not be able to update LS2020 nodes with configuration information from the global database.

For example, if the operations group has read-only access to the global database, user ID root should issue the following commands to ensure that the operations group has required read/write access privileges to the file configure.netdb:

# cd /usr/LightStream-2.3.1/db
# chgrp <ops-group> configure.netdb

Where <ops-group> represents the value of the group to be used on the system.

A new feature in Software Release 2.3.1 is the StreamView environment check utility. It checks for correct settings of environment variables in the user's environment. The utility reports status, any warnings, and any fatal errors in a log file.

StreamView Environment Validation Check

The StreamView application includes an environmental validation tool that facilitates the installation/upgrade and troubleshooting of the StreamView modules cfg, pvc, vli, cfg_a, and monitor by verifying that a user's login is valid for each environmental component.

Environment Validation Check

Upon startup of each program, the environment validation tool checks the environmental components defined by the login shell. The results of the environmental check are written to a temporary log file in the /tmp directory.

If no errors are found upon completion of the environment check, the temporary log file is deleted. If there are errors found, the temporary log file includes the name of the program and a listing of the errors found. The user must change the login shell so that the environmental components are correct.

The StreamView environment validation check is useful in the following situations:

•Testing a new user login environment

•Performing a new installation of StreamView

•Troubleshooting StreamView

Table 1 shows each StreamView module and the corresponding component descriptions with the variables that are checked upon startup of each module.

Table 1 StreamView Environment Validation Checklist

Description
Variable Name
cfg
pvc
vli
cfg_a
monitor

Program directory

PATH

Y

Y

Y

Y

Y

UIDPATH

UIDPATH

Y

Y

Y

N

Y

GUI Database

LSC_DATABASE

Y

Y

Y

Y

N

GUI Log Directory

LSC_CFGLOGPATH

Y

Y

Y

Y

N

cfg_a server port

LSC_CFGTCPPORT

Y

Y

Y

Y

N

SNMP Configuration Standalone

OVSNMP_CONF_FILE

Y

Y

Y

Y

N

SNMP Configuration
HP OpenView

OVSNMP_CONF_FILE

N

N

N

N

N

<application name>.uid file

None

Y

Y

Y

N

Y

XVTPATH

XVTPATH

N

N

N

N

N

XKeysymDB

XKEYSYMDB

N

N

N

N

N

CiscoView location

NMSROOT

N

N

N

N

N


Note The environment validation check may perform differently when used in a standalone environment compared to an HP OpenView environment.

Command Line Options

The environmental validation tool may be controlled by using the following command line options available for use with the StreamView modules.

Option
Result

-help

Displays this screen, then exits

-h

Displays this screen, then exits

-display_check

Displays the result of the environmental check to the terminal

-no_check

Starts the module, but does not perform an environmental check

-check_only

Performs an environmental check, does not start the StreamView application

-hp_openview

Removes the OVSNMP_CONF_FILE variable, if any, does not check the OV SNMP configuration file

-check_only_no_xvt

Performs an environmental check without starting XVT, does not start the StreamView module


For example, the following command displays the results of the cfg environmental check to the terminal, but does not start the configurator.

cfg -display_check -check_only

Cisco Connection Online

Cisco Connection Online (CCO), formerly Cisco Information Online (CIO), is Cisco Systems' primary, real-time support channel. Maintenance customers and partners can self-register on CCO to obtain additional content and services.

Available 24 hours a day, 7 days a week, CCO provides a wealth of standard and value-added services to Cisco's customers and business partners. CCO services include product information, software updates, release notes, technical tips, the Bug Navigator, configuration notes, brochures, descriptions of service offerings, and download access to public and authorized files.

CCO serves a wide variety of users through two interfaces that are updated and enhanced simultaneously·a character-based version and a multimedia version that resides on the World Wide Web (WWW). The character-based CCO supports Zmodem, Kermit, Xmodem, FTP, and Internet e-mail, and is excellent for quick access to information over lower bandwidths. The WWW version of CCO provides richly formatted documents with photographs, figures, graphics, and video, as well as hyperlinks to related information.

You can access CCO in the following ways:

WWW: http://www.cisco.com.

WWW: http://www-europe.cisco.com.

WWW: http://www-china.cisco.com.

Telnet: cco.cisco.com.

Modem: From North America, 408 526-8070; from Europe, 33 1 64 46 40 82. Use the following terminal settings: VT100 emulation; databits: 8; parity: none; stop bits: 1; and baud rates up to 14.4 kbps.

For a copy of CCO's Frequently Asked Questions (FAQ), contact ccohelp@cisco.com. For additional information, contact ccoteam@cisco.com.

If you are a network administrator and need personal technical assistance with a Cisco product that is under warranty or covered by a maintenance contract, contact Cisco's Technical Assistance Center (TAC) at 800 553-2447, 408 526-7209, or tac@cisco.com. To obtain general information about Cisco Systems, Cisco products, or upgrades, contact 800 553-6387, 408 526-7208, or csrep@cisco.com.

IN NO EVENT SHALL CISCO OR ITS SUPPLIERS BE LIABLE FOR ANY INDIRECT, SPECIAL, CONSEQUENTIAL, OR INCIDENTAL DAMAGES, INCLUDING, WITHOUT LIMITATION, LOST PROFITS OR LOSS OR DAMAGE TO DATA ARISING OUT OF THE USE OR INABILITY TO USE THIS MANUAL, EVEN IF CISCO OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.

AtmDirector, AutoConnect, AutoRoute, AXIS, BPX, Catalyst, CD-PAC, CiscoAdvantage, CiscoFusion, Cisco IOS, the Cisco IOS logo, CiscoLink, CiscoPro, the CiscoPro logo, CiscoRemote, the CiscoRemote logo, CiscoSecure, Cisco Systems, CiscoView, CiscoVision, CiscoWorks, ClickStart, ControlStream, EdgeConnect, EtherChannel, FairShare, FastCell, FastForward, FastManager, FastMate, FastPADlmp, FastPADmicro, FastPADmp, FragmentFree, FrameClass, Fulcrum INS, IGX, Impact, Internet Junction, JumpStart, LAN2LAN Enterprise, LAN2LAN Remote Office, LightSwitch, MICA, NetBeyond, NetFlow, Newport Systems Solutions, Packet, PIX, Point and Click Internetworking, RouteStream, Secure/IP, SMARTnet, StrataSphere, StrataSphere BILLder, StrataSphere Connection Manager, StrataSphere Modeler, StrataSphere Optimizer, Stratm, StrataView Plus, StreamView, SwitchProbe, SwitchVision, SwitchWare, SynchroniCD, The Cell, The FastPacket Company, TokenSwitch, TrafficDirector, Virtual EtherSwitch, VirtualStream, VlanDirector, Web Clusters, WNIC, Workgroup Director, Workgroup Stack, and XCI are trademarks; Access by Cisco, Bringing the Power of Internetworking to Everyone, Enter the Net with MultiNet, and The Network Works. No Excuses. are service marks; and Cisco, the Cisco Systems logo, CollisionFree, Combinet, EtherSwitch, FastHub, FastLink, FastNIC, FastPacket, FastPAD, FastSwitch, ForeSight, Grand, Grand Junction, Grand Junction Networks, the Grand Junction Networks logo, HSSI, IGRP, IPX, Kalpana, the Kalpana logo, LightStream, MultiNet, MultiWare, OptiClass, Personal Ethernet, Phase/IP, RPS, StrataCom, TGV, the TGV logo, and UniverCD are registered trademarks of Cisco Systems, Inc. All other trademarks, service marks, registered trademarks, or registered service marks mentioned in this document are the property of their respective owners.

Copyright © 1997, Cisco Systems, Inc.
All rights reserved. Printed in USA.
9611R

hometocprevnextglossaryfeedbacksearchhelp

Posted: Mon Dec 26 22:28:16 PST 2005
All contents are Copyright © 1992--2005 Cisco Systems, Inc. All rights reserved.
Important Notices and Privacy Statement.