|
|
CiscoWorks Blue SNA View 1.0 Release Note
April 25, 1996
This release note discusses two elements of CiscoWorks Blue SNA View, Software Release 1.0:
Use this document in conjunction with:
This release note is organized as follows:
This section describes the hardware and software requirements for CiscoWorks Blue SNA View on the following components:
CiscoWorks Blue SNA View can run on the following systems:
The network management systems listed here (NetView for AIX, HP OpenView, and SunNet Manager) are optional but recommended.
If the workstation will communicate with the mainframe by LU6.2 instead of TCP, see Table 1 for the requirement corresponding to your operating system.
Table 1 : LU6.2 Stacks Supported by SNA View
on AIX |
on SunOS | on HP-UX | |
|---|---|---|---|
| LU6.2 Stack | IBM AIX SNA Server/6000 version 2.1.1 | not supported | not supported |
All platforms require the following hardware and software:
To verify your workstation's compliance with the requirements in this section, see Table 2.
Table 2 : Hardware and Software Verification Methods
| Verify | on AIX | on SunOS | on HP-UX |
|---|---|---|---|
| Hard Disk Space |
df -I
|
df -a
|
bdf
|
| OS Version |
oslevel
|
uname -a
|
uname -a
|
| NMS Version |
lslpp -L
nv6000.base.obj
|
$SNMHOME/bin/
snm_version
|
/usr/OV/bin/
ovlicense
|
| RAM Size |
lscfg | grep mem
|
dmesg | grep mem
|
/etc/dmesg | grep
Kbytes
|
| Swap Space Size |
lsps -a
|
pstat -s
|
swapinfo
|
| X Window System | Ask your system administrator. | ||
To create a file system, see the mkfs, fsck, mkdir, and mount manual pages.
To be manageable by CiscoWorks Blue SNA View, all routers must be running the appropriate software version:
The mainframe application has the following requirements:
This is a summary of required changes to the mainframe system software.
The information in this section applies to SNA View on AIX, HP-UX, and SunOS workstations.
The following errata have been discovered in the CiscoWorks Blue SNA View Workstation Installation Guide :
See the CiscoWorks Blue SNA View Workstation Installation Guide.
Follow these steps to install and configure SNA View on SunOS and HP-UX. The installation and configuration processes take at least 30 minutes.
If it is necessary to reinstall a CiscoWorks Blue product, deinstall the existing software using procedures in "Deinstalling on SunOS or HP-UX," then reinstall as if it were a new installation.
To stop the SunOS or HP-UX installation or configuration process at any time, press Break or Ctrl-C.
The root .rhosts file on the remote system must contain the host name of your local system and an entry for the user root. Otherwise, you cannot access the remote system to download software from its CD-ROM drive. For more information, refer to the rhosts manual page.
To export a CD-ROM file system from a SunOS, Solaris, or HP-UX system, perform the following steps on the remote system:
To mount a file system that is exported from a remote system, perform the following steps on the local SunOS or HP-UX system:
To prepare the system for installation of software from a local CD-ROM drive, complete the following steps:
After the CD-ROM is mounted, use this procedure to move the software to the host system.
The default for each prompt is the value in brackets. To accept any default value, press Enter. Note that you can press Break or Ctrl-C to stop the installation script at any time.
If it is necessary to deinstall any or all CiscoWorks Blue Maps applications, see "Deinstalling on SunOS or HP-UX."
If it is necessary to deinstall CiscoWorks Blue Maps, such as after a failed installation, follow this procedure. Note that you can press Break or Ctrl-C to stop the deinstallation script at any time.
Perform these steps on a SunOS or HP-UX system when installation of the software in complete.
The default for each prompt is the value in brackets. To accept any default value, press Enter. Note that you can press Break or Ctrl-C to stop the configuration script at any time.
During installation and configuration, messages are recorded in a log file to provide diagnostic information in case a problem arises. Perform these commands on a SunOS or HP-UX system when you are satisfied that configuration of the software is complete.
On SunOS:
On HP-UX:
The installation caveats in this section apply to SNA View on AIX, HP-UX, and SunOS workstations.
Table 3 lists the environment variables applicable to CiscoWorks Blue SNA View on AIX, HP-UX, and SunOS.
Table 3 : CiscoWorks Blue SNA View Environment Variables
You do not have to set the environment variables described in Step 3 of "Installing CiscoWorks Blue SNA View" in the CiscoWorks Blue SNA View Workstation Installation Guide. The System Management Interface Tool (SMIT) installation process performs this step automatically.
Before deinstalling SNA View from any platform, you must set the CWBROOT and NMSROOT environment variables by hand.
The CiscoWorks Blue SNA View Workstation Installation Guide describes installation of the product using SMIT that is part of AIX 3.2.5. In AIX 4.1, the SMIT screens are slightly different.
All parameters is Table 2-2 on page 2-15 and 2-16 of the CiscoWorks Blue SNA View Workstation Installation Guide should have an EV prefix, not SV. During configuration, you see the correct EVxxx parameters in the Domain Configuration window.
The default value of the EVOCMD_OPERATOR parameter (shown in Table 2-2 on page 2-16) is NSPAUTO1.
The evoXconfig utility (found in the $CWBROOT/snaview/bin directory) accepts configuration parameters for each mainframe domain that is managed by SNA View. The utility is invoked by SMIT or the configuration script and can be executed independently if you want to modify parameters without using SMIT or the configuration script. When you are entering data into evoXconfig, read the CiscoWorks Blue SNA View Workstation Installation Guide carefully because the utility does not detect invalid or misspelled input.
To configure LU 6.2 connectivity between an AIX workstation and a mainframe domain, perform these steps.
If you configure TCP connectivity to multiple mainframe domains, you must match the EVOMF_HCI_AGENT_PORT and EVOMF_CMDS_AGENT_PORT parameters of each domain to the TCP Parameter Cards in the mainframe. (TCP Parameter Cards are documented on page 2-13 of the CiscoWorks Blue SNA View Mainframe Installation Guide.) Example:
The TCP Parameter Card in the mainframe for domain north is:
The TCP Parameter Card in the mainframe for domain south is:
The workstation parameters for domain north should be:
The workstation parameters for domain south should be:
This section contains general caveats that apply to CiscoWorks Blue SNA View on all platforms.
The Alert Server described in the CiscoWorks Blue SNA View Workstation Installation Guide is not yet available.
When you launch discovery from the SNA View Task Manager, do not use the Task Manager's Clients> Mainframe Commands feature or the Status Manager until the Task Manager reports that the status of the Discover process is Inactive. Doing so might interfere with discovery and cause incorrect results.
Support of LU6.2 connectivity to the host is not currently available in the SunOS or HP-UX versions of the product. When configuring a mainframe domain in the SunOS or HP-UX workstation application, always select TCP connectivity. LU6.2 connectivity on SunOS or HP-UX will be available in the future.
Hyperlinks in the online help system of SNA View do not work.
After you start start the PU Discover process from the SNA View Task Manager, allow it to complete before running other processes.
This section applies to the CiscoWorks Blue SNA View mainframe application.
If CiscoWorks Blue SNA View will coexist on the workstation with EView/Open from NetTech, Inc., Cisco's NSPOPEN procedure on the mainframe will serve both SNA View and EView/Open on the workstation.
To install SNA View when EView/Open is already installed and configured, follow the instructions in the CiscoWorks Blue SNA View Mainframe Installation Guide. Note the"Mainframe Documentation Caveats" in this release note and the following clarifications to the procedure.
If SNA View is already installed and configured, do not install EView/Open on the mainframe. SNA View's NSPOPEN procedure will serve both the EView/Open and SNA View applications on the workstation. Perform the following steps.
The following errata appear in the CiscoWorks Blue SNA View Mainframe Installation Guide.
If the MVS Message client or the VTAM Message client of the SNA View Task Manager stops receiving messages, enter the following on the MVS host console of a NetView console twice:
If the OUTPUTQ of your TCP task is reported to be non-zero and if it continued to grow between the first report and the second, stop and restart the mainframe application by entering the following commands.
Then start the SNA View Task Manager on the workstation. Access the domain whose message client had failed. Restart the Host Command Interface and Command Server for that domain.
If you turn on the VTAM MSGMOD option at the mainframe for diagnostic purposes, supplemental information appears in messages to the workstation. This information causes errors in the Discover and Status Manager processes on the workstation. If you must activate MSGMOD, shut down SNA View on the workstation first.
Do not filter mainframe IST590I messages. SNA View on the workstation relies on this message.
Many messages issued by NSPOPEN have an EVO prefix. In a future release of the software, all NSPOPEN messages will have a uniform prefix.
Cisco Connection Online (CCO), formerly Cisco Connection Online (CCO), 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, Internet e-mail, and fax download options, 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:
For a copy of CCO's Frequently Asked Questions (FAQ), contact
Copyright 1988-1996 © Cisco Systems Inc.
Exporting a CD-ROM File System from a SunOS or HP-UX System
# mkdir /cdrom
/cdrom -ro
# /etc/nfsd 8 &
#
/usr/etc/rpc.mountd -n
Mount the CD-ROM by entering the following command:
# /etc/mount -r -t hsfs /dev/device_filename /cdrom
# /etc/mount -o ro -t cdfs /dev/device_filename /cdrom
# exportfs -va
# reboot
Mounting a Remotely Exported CD-ROM File System on a Local System
# mkdir /cdrom
hostname# mount
remote_hostname:remote_filesystem local_mount_point
For example, to mount the /cdrom file system from a remote host called faraway on a local directory named /cdrom, enter the following command at the prompt:
hostname#
mount faraway:/cdrom /cdrom
The remote CD-ROM is ready for installation of software on the local system.
Mounting a Local CD-ROM on SunOS or HP-UX
# mkdir /cdrom
# mount -r -t hsfs /dev/device_filename /cdrom
On HP-UX:
# /etc/mount -o ro -t cdfs /dev/device_filename /cdrom
In the SunOS command, the -r option mounts the CD-ROM in read-only mode.
Installing on SunOS and HP-UX
# cd /cdrom
# cwbinstall
In response the the following prompt, enter the source of the software to be installed.
Source Directory :[/cdrom]
On HP-UX, enter the image file in which the software is stored.
Source File:[/cdrom/cwbsnaview.tar]
In response the the following prompt, press Enter. Do not override the default.
Where do you want to install the product :[/usr/cw-blue]
In response to the following prompt, press Enter.
What filesets do you want to install : [CWBLUE-SNAVIEW]
The installation program reviews your responses to the previous questions and asks:
Do you wish to continue? (y/n)[y]:
Press Enter to continue, or type n and press Enter to terminate installation.
# more /usr/cw-blue/log/cwb_install.log
On HP-UX, type:
# more /tmp/update.log
Press Enter to advance the display one screenful at a time.
Deinstalling on SunOS or HP-UX
# export CWBROOT=/usr/cw-blue
# export CWBROOT=/usr/nms
If you are using the C shell or the TC shell, type commands like the following:
# setenv CWBROOT /usr/cw-blue
# setenv CWBROOT /usr/nms
To start the interactive deinstallation script, type the following commands:
# cd /usr/cw-blue/install/bin
# cwbdeinstall
The deinstallation script lists the Maps and SNA View filesets that are installed.
CWBLUE-SNAVIEW
In response to the following prompt, press Enter to begin the deinstallation, or type n and press Enter to terminate deinstallation.
Do you wish to de-install? (y/n)[y]:
When the system prompt returns, examine the deinstallation log file. Unless you see an error message in that file, deinstallation is complete.
# more /tmp/cwb_deinstall.log
On SunOS, there is no deinstallation log file.
# rm /tmp/cwb_deinstall.log
You can now reinstall the software.
Configuring SNA View on SunOS or HP-UX
# cd /usr/cw-blue/install/bin
# cwbconfigure
In response to the following prompt, type snaview to specify that you want to configure the SNA View product.
Which product do you want to configure?: [maps or snaview]
The following prompt appears only if the CWBROOT variable is not already set. Press Enter to accept the default (the same directory in which you placed the software during installation), or type an alternate directory name.
CiscoWorks Blue root directory: [/usr/cwblue]
In response to the following prompt, type the name(s) of the SNA domains from which SNA View will collect information. Separate multiple names with a space.
SNA Domain name(s):
If you are reconfiguring an existing domain, press Enter without typing a name.
Do you wish to continue? (y/n)[y]:
Press Enter to continue, or type n and press Enter to terminate configuration.
# cd /
#
umount /cdrom
Removing Log Files on SunOS or HP-UX
# rm /usr/cw-blue/log/cwb_install.log
# rm /tmp/update.log
rm *.log
to remove the log files because the directory might contain other applications' log files that you do not want to remove.
Workstation Installation and Configuration Caveats
Environment Variables
Variable
Typical Value
CWBROOT
/usr/cw-blue
NMSROOT
/usr/nms
XAPPLRESDIR
$CWBROOT/Xdefaults
HHHOME
$NMSROOT/hyperhelp
HHPATH
$NMSROOT/hyperhelp/bin
You Need Not Set AIX Environment Variables by Hand
You Must Set Environment Variables Before Deinstallation on Any Platform
SMIT Screens in AIX 3.2.5 Are Not the Same As in AIX 4.1
EV and EVO Prefixes are Correct, Not SV Prefixes
Check Your Spelling When Configuring Domains
Configuring LU6.2 Connectivity
# cd /usr/cw-blue/etc
# cp evopen_config_Domain.LU62template /etc/evopen_config_Domain
Domain
is the domain name.
# /usr/cw-blue/snaview/bin/evoXconfig
Typically, set the parameters as follows.
Configuring TCP Connectivity to Multiple Domains
TCP 6116 6117
TCP 6126 6127
EVOMF_HCI_AGENT_PORT 6116
EVOMF_CMDS_AGENT_PORT 6117
EVOMF_HCI_AGENT_PORT 6126
EVOMF_CMDS_AGENT_PORT 6127
Workstation Operational Caveats
Alert Server is Not Implemented
Do Not Interfere with Discovery
HP and Sun Use TCP Connectivity Only
Online Help Hyperlinks Do Not Work
Let the PU Discover Process Finish
Mainframe Information
Coexistence of SNA View and EView/Open from NetTech, Inc.
Installing SNA View When EView/Open Is Already Installed
P EVOPEN
In the NetView procedure steplib, where the EVOPEN load modules were copied, rename the EVOPEN version of DSIEX06 to DSIEX06E, and rename DSIEX11 to DSIEX11E.
6106 TCP EVOPEN
6107 TCP EVOPEN
to
6106 TCP NSPOPEN
6107 TCP NSPOPEN
Also add the port numbers that will be utilized by SNA View, such as:
6116 TCP NSPOPEN
6117 TCP NSPOPEN
In this example, 6116 and 6117 are the ports to configure in the Domain Configuration window of SNA View on the workstation. 6106 and 6107 are the ports that are probably already configured for use by EView/Open on the workstation.
TCP 6106 6107
Add a TCP Parameter Card for each additional domain that will be configured in the SNA View workstation software. The port numbers in the TCP Parameter Card for a given domain must match those defined in the PROFILE.TCPIP for the same domain. The following card matches the ports added in the previous step:
TCP 6116 6117
Per the instructions under "Assembling and Linking NetView Exits" on page 2-16, copy the SNA View NetView modules from prefix.SNAVIEW.NSPLOAD into the NetView steplib. The modules have been assembled using NetView version 2.3, not 2.2 as stated on page 2-16.
S NSPOPEN
Start EView/Open and SNA View on the workstation and verify correct operation.
Installing EView/Open When SNA View Is Already Installed
6106 TCP NSPOPEN
6107 TCP NSPOPEN
Add the port numbers that will be utilized by EView/Open, such as:
6116 TCP NSPOPEN
6117 TCP NSPOPEN
In this example, 6116 and 6117 are the ports to configure in the Domain Configuration window of EView/Open on the workstation.
TCP 6106 6107
Add a TCP Parameter Card for each additional domain that will be configured in the Eview/Open workstation software. The port numbers in the TCP Parameter Card for a given domain must match those defined in the PROFILE.TCPIP for the same domain. The following card matches the ports added in the previous step:
TCP 6116 6117
Start the NSPOPEN procedure on the mainframe to serve both the EView/Open and SNA View applications on the workstation.
S NSPOPEN
Start EView/Open and SNA View on the workstation and verify correct operation.
Mainframe Documentation Caveats
A sample CDRSC definition is available in prefix.SNAVIEW.NSPSAMP(NSPCDRSC).
//NSPOPEN EXEC PGM=EVOPEN,PARM='=TCPIP_PREFIX=TCPIPX'
In the next release of SNA View, the existing example will be correct:
//NSPOPEN EXEC PGM=NSPOPEN,PARM='=TCPIP_PREFIX=TCPIPX'
In release 1.0 of SNA View only, the syntax of the SEC parameter card on page 2-12 should read:
SEC EVRACF
In the next release of SNA View, the existing example will be correct:
SEC NSPRACF
Step 1 on page 2-16 should refer to NSPCLST, not CLIST.
PROC
Description
NSPKDOC
Documentation of procs, how to implement SNA View
NSPKCNM
Documentation on changes to CNMPROC for SNA View
NSPKPPO
Documentation on changes to PPOPROC for SNA View
NSPKPPI
PROC---CNM & PPO message PPI sender
NSPKCMD
PROC---Command PPI receiver (NSPNETV)
NSPKCM1
PROC ---Command issuer and sender
Mainframe Operational Caveats
If the MVS or VTAM Message Client Fails
F NSPOPEN,SHOW FLOW
P NSPOPEN
S NSPOPEN
Beware the VTAM MSGMOD Option
Do Not Filter IST590I Messages
NSPOPEN Issues Messages With EVO Prefix
Cisco Connection Online
http://www.cisco.com.
cco.cisco.com.
ccohelp@cisco.com.
For additional information, contact
ccoteam@cisco.com.
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.
![]()
![]()
![]()
![]()
![]()
![]()
![]()