|
|
This release notes provides information about the 7.2.9 release of Cisco StrataView Plus including system requirements, a list of features, details about Year 2000 Compliance, new and changed information, and a list of known bugs and caveats.
This release note contains the following sections:
This section lists information about the 7.2.9 release including new features, features that have been removed from earlier releases of SV+ 7.2.9, and Year 2000 (Y2K) Compliance information.
Cisco StrataView Plus 7.2.9 has been tested and certified as Year 2000 (Y2K) Compliant. SV+ 7.2.9 has passed Cisco's 29 test-case suite. Table 1 lists details of the Y2K compliance certification including software requirements.
Software | Release | Year 2000 Compliance Certification |
|---|---|---|
StrataView Plus | 7.2.9 or later | Cisco Systems 29 test case suite. |
Wingz | 2.5 | IISC |
Informix | 5.00.UC3 | Informix |
The Y2K requirements for the SunOS are listed in Table 2. Sun Microsystems provided Y2K compliance certification for this software. Patches listed can be downloaded from http://sun-solve/sun.com.
SunOS Release | Recommended Patches |
|---|---|
4.1.3U1vB | 105135-03, 105136-01, 101759-09, 101558-12, 105137-03, 105153-03, 105138-01, 101437-02, 105139-02, 105140-01, 105141-02, 105142-01, 105465-02, 106181-02, 106859-01, 107222-01, 100462-32r, 100523-24, 100544-12, 100638-03, 100728-03 |
4.1.4 | 105143-03, 105144-01, 102544-12, 102545-12, 105145-03, 105146-02, 105147-01, 105148-01, 105149-02, 105150-01, 105151-02, 105152-01, 105466-02, 106182-02, 107223-01, 100462-32, 100523-24, 100544-12, 100638-03, 100728-03 |
Cisco StrataView Plus 7.2.9 supports both high and low performance workstations. Table lists the minimum requirements for a high and low end platform workstation.
Platform Type | Machine Type | Number of CPUs | Memory (RAM) | Hard Disks | Swap Space | Number of Connections |
|---|---|---|---|---|---|---|
Low End | Sun SPARC 20 Model 151 | 1 | 256 MB | Two 2 GB or one 4 GB | 512 MB | Less than 5000 |
High End | Sun Enterprise 2000 | 1 | 256 MB | Two 2 GB or one 4 GB | 512 MB | 50,000 - 100,000 |
SV+ 7.2 will operate with IPX/BPX release 7.2 for all features. It will operate with IPX releases 7.0 and 7.1 for features supported in the respective IPX releases.
The TFTP Statistics collection process is used to collect statistics from IPX with release 7.2. The message-based statistics collection process is still used for BPX release 7.2 and older releases of IPX and BPX. This facility is referred to as the Stats Collection Manager (SCM) or Statistics Agent.
SV+ 7.2.9 requires SunOS 4.1.4 (UNIX) from Sun Microsystems.
SV+ 7.2.9 supports upgrades from versions SV+ 7.0.x and 7.1.x.
This section provides information to help you install 7.2.9 upgrade software. This procedure supports upgrades from releases 7.1.x, 7.1.x, and 7.2.x. There is no need to modify the resident versions of Motif, Informix, and Wingz for the SV+ 7.2.9 upgrade.
During the initial part of the installation, you can choose to save the data from the existing database. The contents of /usr/users/svplus are overwritten during the installation process, including the config.sv file. We recommend that you copy the /usr/users/svplus/config.sv file to /tmp before starting the upgrade process.
The installation script checks for three conditions:
If these conditions are met, the SV+ 7.2.9 software is installed. The following tasks must be completed after the software installation:
To install the SV+ 7.2.9 software, complete the following steps:
Step 1 Login to the SV+ workstation as user svplus, and become user root.
% su
password: <super-user password>
#
Step 2 Enter the following to change to the root directory:
# cd /
Step 3 Insert the SV+ Release 7.2.9 tape into the tape drive and slide the latch to the right.
Step 4 Enter the following command:
# /usr/etc/extract_unbundled
Enter media drive location [local | remote]:
Step 5 Enter l to select a local tape drive.
Enter Device Name (rst0, rmt0, rfd0c): /dev/ (You type st0 for /dev/rst0)
**Please mount the release media if you haven't done so already.**
Press Return when ready.
Step 6 Enter the tape device address and press Return when prompted. If your tape drive's address is /dev/rst0, type st0 and press Enter.
The following product will be installed:
2+0 records in
2+0 records out
StrataView Plus 7.2Step 7 After the copyright banner displays, reply y to the following prompt:
Do you want to continue [y|n]? y
The StrataView Plus Installer (SPI) script begins and checks the basic setup, that user is root, and checks the core script files. After the checks are completed, a message displays asking if you want to perform a manual or automatic installation.
What type of installation do you want? [auto | manual]
Step 8 Enter a to select an automatic installation.
A message displays asking if you want to initialize your statistics or retain your current statistics.
Do you want to initialize the statistics database: [yes | no]
Step 9 Reply n to save the existing statistics database (or reply y to initialize a new statistics database.
The SV+ 7.2.9 software is installed.
Installation was successful!
*** Exiting main driver at Fri May 14 08:03:49 PDT 1999. ***
hostname#
Step 10 Enter the following commands to exit from user root and change directory to /usr/users/svplus:
# exit% cd pwd
% % /usr/users/svplus
%
The Statistics Collection Manager (SCM) files are installed by the installation script after StrataView Plus software has been installed.
To configure an SV+ workstation for statistics collection, complete the following steps:
Step 1 Login to the SV+ workstation as user svplus, and become user root.
% su
password: <super-user password>
#
Step 2 Use cd to change directory to /etc.
# cd /etc
Step 3 For workstations running NIS, edit the /etc/hosts file of the NIS server. Make a list with single-line entries for each node in the network with which the SCM should connect (as shown below), and remake the NIS maps.
alpha 192.187.207.1...
beta 192.187.208.1
fox 192.187.212.1
Step 4 If your workstation is not running NIS, edit the /etc/hosts file of the local SV+ workstation. Make a list with single-line entries for each node in the network with which the SCM should connect (as shown in the example above).
If you saved your workstation's /usr/users/svplus/config.sv file in the /tmp directory as advised earlier, you can restore the file by entering the following:
% cp /tmp/config.sv .
The config.sv file is overwritten with default values during software installation. The default values of the config.sv file is a single line with a serial port selection of /dev/ttya and a baud rate of 9600.
To start SV+, complete the following steps:
Step 1 Login to the SV+ workstation as user svplus.
Step 2 Enter the following command to display the SV+ Main Menu:
% sv+
Step 3 Select option 1 to start SV+.
This section provides information that is new or changed since the most recent documentation was published.
Statistics Aging with all statistics is now performed through the SCM. Aging is applied to all statistics, is performed hourly, and can be in the range from one hour to 8760 hours. You must configure aging through the SCM.
If you install SV+ 7.2.7 (or later) over existing 7.2.x, the aging field will be set to whatever value you had prior to the software upgrade. The default in 7.2.x was "1". If you start SV+ with an aging value of 1, all stats older than one hour will be deleted within the first 15 minutes of running SV+.
To change the aging value prior to running SV+ complete the following steps:
Step 1 At the SV+ Main Menu, select option 8, start the SCM GUI.
Step 2 Set the aging in the Network Parameters Window.
Step 3 Select OK on the Network Parameters Window.
Step 4 Start SV+ by selecting option 1 of the SV+ Main Menu.
SV+ reports Asynchronous Alarms on objects in the network to customer software (AAG clients).
Enhancement add support to report two new alarms:
The following changes are required for SV+ to AAG Client 'Alarm Notification Message' to support the new alarms:
For each type of alarm, two thresholds must be specified, one used by SV+ software for triggering the alarm and another used to generate a clearing of the alarm condition. These four thresholds will be specified in an ASCII file, /usr/users/svplus/statsmgrdir/statsparser.alarm
Following is a sample statsparser.alarm file:
STATSGAIN_PERCENT 25
STATSLOSS_PERCENT 20
DBFULL_PERCENT 85
DBEMPTY_PERCENT 75
If such a file does not exist, no alarms will be generated. If the file exists but has invalid values for parameters, default values will be assumed for generating alarms. The default values will correspond to those in the statsparser.alarms created by SV+ installation.
The alarm state is not maintained by SV+ across sessions (restarts). A database full clear alarm will not be generated unless there has been a database full alarm in the same session of SV+.
A statistics loss clear alarm will be generated on a increase in the amount of connection statistics, even without a corresponding statistics loss alarm.
SV+ reports Asynchronous Alarms & Objects in a Cisco switching network to customer software - AAG clients: Alarm clients & Object clients respectively.
Once a alarm client (or object client) registers with SV+, the former will receive all existing alarms (existing objects for object client) & subsequently any alarms as they occur on the network (additions and updates to objects for object client) from SV+.
This enhancement will add support in SV+ for Incremental AAG clients.
The following changes are required in the AAG Client to SV+ Object Status Request and Object Alarm Status Request messages. The existing message formats will continue to be used and the proposed changes are required to be used only by Incremental AAG clients.
The following sections describe the limitations that have been found when multiple Statistics Collection Managers (SCMs) are deployed in various network configurations.
The TFTP Statistics collection requires special attention to properly configure TFTP file collection when a single SCM is collecting statistics from two separate networks.
A network is defined as a collection of nodes that are connected with a trunk between them. This network will have the same date/time (clock) on all nodes on the network. A network can consist of multiple domains that are inter-connected via trunk lines.
The SCM must be configured to have only one Time Sync Host. In Figure 1, a single SCM is collecting from two separate networks. If the Operations Center sets the network time for Network 1 to a different time than Network 2 and specifies that a node in Network 1 should be used as the Time Sync Host, the SCM might not be able to get the statistics files from Network 2. This occurs because the SCM assumes that Network 2's clock is the same as Network 1's clock.
The Operations Center staff should set the network time on both networks to be the same time. This is accomplished through the cnfdate command on each network.
There are some users who will be doing redundant file collection, and other users who will be using multiple SCMs to collect files to a common SV+ workstation as shown in Figure 2. The restrictions that are discussed here apply to both configurations.
When configuring nodes for TFTP collection, the Collection Period, a critical parameter, defines the interval that the SCM will perform TFTP file GETS from the network to collect statistic files. Collection Period must be identical on all nodes in all networks.Additionally, if multiple SCMs are used to collect statistics from the same node, the same Collection Period must be specified on all the SCMs.Some statistics files may be missed if the multiple SCMs have different collection intervals specified for the same node.
There are additional SV+ WingZ and Parser considerations if you are using multiple SCMs for TFTP Statistics collection. When you configure a node for TFTP collection, the SCM keeps a copy of the node configuration on the local SCM workstation.This configuration list is used by WingZ to determine what statistics have been enabled or disabled on a given node. For WingZ to turn on the statistics enable table, these configuration files are opened and parsed by the SV+ statsenable program, and the database "stat_enable" table updated for that node.
Cisco recommends that you use a single SCM to enable all TFTP statistics for all nodes in the network. The single SCM should be the SCM that runs on the same workstation as WingZ and SV+.
It also important to note that the Network Parameters window on the SCM that is running stand-alone contains configuration parameters for the statsParser. Since the SCM is running stand-alone where there is no statsParser or SV+, the Parser parameters will have no effect upon other SCMs running on other machines. If you want to change a statsParser parameter, you must go to the machine where SV+ and the parser are running and configure the parameters appropriately for them to take effect.
This section lists known and resolved anomalies in the 7.2.9 version of SV+ and known and resolved anomalies in other releases of SV+ 7.2.
The following known anomalies have been fixed in the 7.2.8 release of SV+.
The Stats child process now opens a different UDP port to communication with the nodes for each tftp GETs and PUTs to prevent mixing data from multiple sources.
All patches are inclusive patches, meaning that each patch includes all previous patches. This makes patch installation a single step. You must have previously installed SV+ before applying the patches.
To install a patch, complete the following steps:
Step 1 Get the patch tarfile on to the SV+ machine.
Step 2 Login to the SV+ workstation as user root.
Step 3 If the tar file name does NOT end in "Z", the file is uncompressed. These instructions are for compressed files. If your patch is not compressed, as user root, use the command
compress tarfilename
Step 4 Stop SV+.
Step 5 Enter the following command using the selected patch in place of patchfilename:
zcat patchfilename | tar xvpf -
Step 6 Start SV+.
Cisco Connection Online (CCO) is Cisco Systems' primary, real-time support channel. Maintenance customers and partners can self-register on CCO to obtain additional information 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, product documentation, 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 it 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 cco-help@cisco.com. For additional information, contact cco-team@cisco.com.
Cisco documentation and additional literature are available in a CD-ROM package, which ships with your product. The Documentation CD-ROM, a member of the Cisco Connection Family, is updated monthly. Therefore, it might be more current than printed documentation. To order additional copies of the Documentation CD-ROM, contact your local sales representative or call customer service. The CD-ROM package is available as a single package or as an annual subscription. You can also access Cisco documentation on the World Wide Web at http://www.cisco.com, http://www-china.cisco.com, or http://www-europe.cisco.com.
If you are reading Cisco product documentation on the World Wide Web, you can submit comments electronically. Click Feedback in the toolbar and select Documentation. After you complete the form, click Submit to send it to Cisco. We appreciate your comments.
Posted: Wed May 26 16:44:10 PDT 1999
Copyright 1989-1999©Cisco Systems Inc.