Release Notes for Cisco StrataView Plus 9.0.05 Solaris

If you are currently using SV+ 9.0.00 release, install SV+ 9.0.05 and choose the installation New option to initialize the database tables. See next section, Installation Notes for details.

If you are moving from release 8.2, 8.4.xx, 9.0.01, 9.0.02, 9.0.03, 9.0.04 to 9.0.05, it is possible to upgrade the software while keeping data in the Informix database intact. See XREF for more details.

This release note contains the following sections:

New Features in Release 9.0.05

This sections describes the new features in Cisco StrataView Plus Release

WAN Device Name Changes

The following table has the changes to WAN device names. This document references the old names only.

Table 1: WAN Device Name Changes

Old Name New Name

BPX

BPX 8600

IGX

IGX 8400

AXIS

MGX 8220

Old Name	New Name
BPX	BPX 8600
IGX	IGX 8400
AXIS	MGX 8220

TCP/UDP Ports used by StrataView Plus

UDP port 5120 on BPX/IPX/IGX is used by StrataView Plus to communicate with those switches.

TCP and UDP port 9000 is used as base port by StrataView processes for inter process communication.

UDP port 8161 is used by SNMP Proxy agent by default. However, this port is configurable by editing the file SNMPAgent.conf in /usr/users/svplus/config file before starting SNMP Agent processes

Installation

Both auto-install and manual install procedures have been enhanced to be less interactive. Installation procedure has been added for stand-alone SCM.

AutoInstall

Auto-install has been enhanced to find out whether the hard disk is partitioned or not. If it is not partitioned the only option given is to partition the disks. Auto-install has been improved to give error messages about wrong or unsupported disk configuration etc.,

Manual Installation

Manual installation has been enhanced to work like auto-install after the disk configuration has been done manually.

Year 2000 Compliance

SV+ 8.4.13 has been tested and certified for Year 2000 compliance. This has been done by executing and verifying the 29 test cases in the test suite developed by Cisco for Year 2000 compliance.

Software Release Patch Y2K compliance Certified By

StrataView Plus

9.0.05

N/A

Cisco Systems 29 Test Case suite

HP OpenView

4.11

PSOV-02123

PSOV_01782

HP

WINGZ

2.5

N/A

IISC

Informix

5.10

N/A

Informix

Solaris OS

2.5.1

Solaris 2.5.1 Recommended Patch Cluster

Dated Feb/12/1999 And

Solaris 2.5.1 Y2000 Patch Cluster Dated Jan/20/1999

Sun MicroSystems

Software	Release	Patch	Y2K compliance Certified By
StrataView Plus	9.0.05	N/A	Cisco Systems 29 Test Case suite
HP OpenView	4.11	PSOV-02123 PSOV_01782	HP
WINGZ	2.5	N/A	IISC
Informix	5.10	N/A	Informix
Solaris OS	2.5.1	Solaris 2.5.1 Recommended Patch Cluster Dated Feb/12/1999 And Solaris 2.5.1 Y2000 Patch Cluster Dated Jan/20/1999	Sun MicroSystems

Note The Solaris 2.5.1 patch clusters can be downloaded from http://sunsolve.sun.com/pub-cgi/us/pubpatchpage.pl

Connection Manager

SV+ Release 9.0.05 Connection Manager will support management of voice and synchronous data connections on a tiered network architecture, where the switch software is running 8.5 software. Please note that 3 segment voice/data connections with the middle segment terminated in BPX nodes are not supported. Also, you need to preconfigure the remote endpoint channel before setting up 1 segment data connection between two IPX/IGX routing nodes. For more information, please see CSCdk021115 bug description under section 11.

Network Limits

The network will allow up to 12 SV+ stations to be connected into it. There is no change in SV+ software for this feature, the switch software and Axis(4.0.04 onwards) have increased their limits to support this.

SV+ release 9.0.05 will be able to manage different disjointed networks running switch software releases 8.2, 8.4 or 8.5 provided all the networks elements have unique network IP addresses and unique names across all the networks managed by SV+. Different networks may run different versions of switch software as long as the releases are those listed above. SV+ 9.0.05 has been tested to manage up to twenty disjoint networks.

System Requirements

Three types of machines are supported for SV+ 9.0 as standard platforms. They are low-end, mid-range and high-end platforms. The configuration of each platform type is listed in table 1.

Platform Machine Type Number of CPU Total RAM Graphic Card Type Hard Disk Drive Swap Space SV+ Desktops (n) Supported Connections (m) Supported

Low End

Sun Ultra Enterprise 1 Model 170E or Sparc 20 Model 151 or Ultra 10 with SCSI controller

1

256 MB

24 bits

Two 2 GB drives OR one 4 GB drive

512 MB

n < 5

m < 5,000

Mid Range option 1

Sun Ultra 2 with 300 MHz or Ultra 30 model 300 and 1MB cache

1 (300 MHz)

512 MB

24 bits

Two 4 GB drives

1 GB

5 =< n < 10

5,000 =< m < 25,000

Mid Range option 2

Sun Ultra Enterprise 2 Model 2300 or Ultra 60)

2 (300 MHz)

512 MB

24 bits

Two 4 GB drives

1 GB

5 =< n < 10

25,000 =< m < 50,000

Mid Range option 3

Sun Ultra Enterprise 2 Model 2300 or Ultra 60

2 (300 MHz)

1 GB

24 bits

Two 4 GB drives

2 GB

5 =< n < 10

50,000 =< m < 100,000

High End

Sun Enterprise 4000 or Enterprise 450

at least 4

1 GB

24 bits

Two 4 GB drives and disk array

2 GB

n >= 10

m >= 100,000

Platform	Machine Type	Number of CPU	Total RAM	Graphic Card Type	Hard Disk Drive	Swap Space	SV+ Desktops (n) Supported	Connections (m) Supported
Low End	Sun Ultra Enterprise 1 Model 170E or Sparc 20 Model 151 or Ultra 10 with SCSI controller	1	256 MB	24 bits	Two 2 GB drives OR one 4 GB drive	512 MB	n < 5	m < 5,000
Mid Range option 1	Sun Ultra 2 with 300 MHz or Ultra 30 model 300 and 1MB cache	1 (300 MHz)	512 MB	24 bits	Two 4 GB drives	1 GB	5 =< n < 10	5,000 =< m < 25,000
Mid Range option 2	Sun Ultra Enterprise 2 Model 2300 or Ultra 60)	2 (300 MHz)	512 MB	24 bits	Two 4 GB drives	1 GB	5 =< n < 10	25,000 =< m < 50,000
Mid Range option 3	Sun Ultra Enterprise 2 Model 2300 or Ultra 60	2 (300 MHz)	1 GB	24 bits	Two 4 GB drives	2 GB	5 =< n < 10	50,000 =< m < 100,000
High End	Sun Enterprise 4000 or Enterprise 450	at least 4	1 GB	24 bits	Two 4 GB drives and disk array	2 GB	n >= 10	m >= 100,000

The selection of a proper SV+ platform depends on a number of factors, such as number of SV+ desktops, number of managed connections and number of statistics collected and stored. The above table also lists recommended SV+ platforms based on the size of network.

Additional Platform Requirements

For every additional SV+ desktop, you need an additional 8 MB of RAM beyond the standard platform configuration.

You may upgrade the standard configuration such as CPU speed, RAM size and disk space for future expansion.

The default disk size for the Informix database is 800 MB. However, it is highly recommended to size the disk space needed for the statistics collection process.

Stand-Alone SCM Requirements

Stand-alone SCM requires a minimal CPU configuration of 128 MB memory, Solaris 2.5.1, with at least 2 GB total disk space. You should install Solaris and provide at least 300 MB for the /usr/users/svplus partition. This will provide adequate storage for the SCM files and some local stats files. For larger stats file depository, you can add more disks and store the stats files on the larger partition.

HP OpenView Requirements

The SV+ 9.0 release works with HP Openview Release 4.11 for Solaris 2.5.1.

For HP OpenView installation requirements and procedures, refer to "HP OpenView Network Node Manager Products, Installation Guide" (part # J1172-90001 from HP).

Compatibility

SV+ 9.0 will operate with IPX/BPX/IGX releases 8.5, 8.4.0, and 8.2 (8.2.0x, 8.2.3x and 8.2.5x), Axis release 2.x, 3.x (AUSM4, CESM4, FRSM4, ASC and IMATM) and Axis release 4.0.x (CESM4, FRSM4, AUSM4, BNM T3/E3, BNM 155, SRM T1/E1, SRM 3T3, IMATM, FRSM8, AUSM8, FRSM-HS1) for all supported features.

SV+ 9.0 will be backward compatible with AXIS release 3. In the case of IMATM, SV+ 9.0 will fully support IMATM starting on IMATM release 3.0.03 onwards. The support for any previous releases of IMATM is limited to display on Equipment Manager. No other support is available from SV+.

Although SV+ 9.0 Equipment Manager shelf view displays AUSM release 2 cards, you need to enable the line and ports from AUSM CLI. The Equipment Manager line configuration window and port configuration windows will not fully functional for AUSM R2 cards.

SV+ 9.0 Connection Manager does not support AUSM R2 due to the lack of port speed information in the SV+ database. This limitation will not allow the you to specify the PCR(0+1) parameter related to AXIS.

SV+ 9.0 does not support the BERT feature of AXIS/SRM R4. You have to use CLI interface to configure the BERT functions.

Notes, Cautions, and Limitations

Third Party LImitations

All event messages are now displayed in HPOV's Event Browser window. There is a limit of 2000 pending messages on HPOV's Event Browser. If there are more than 2000 messages to be processed and displayed by Event Browser it may exit.

There is a known problem with the malloc() function on Solaris version 2.5.1. Sometimes this problem will cause SV+ applications to core dump in the malloc() function call. The following Solaris patch is required to fix the problem.

Patch-ID# 103640-06 or later

Keywords: SIGSEGV kernel mutex_enter lwplock lm_get_sysid klmmod lm_sysid

Synopsis: SunOS 5.5.1: kernel patch

Date: Mar/13/97

SV+ Database

After creating a new database by executing the SV+CreateDb command, if StrataView Plus is restarted before it is synchronized with the network, it will result in a database inconsistency. In this case, perform create_db before restarting SV+ to avoid database inconsistency.

Note Do NOT use SV+CreateDB tool for the operation described above.

The logical_connection table count for a node in SV+ database may not match the master lcon counts in that node. This will happen if the database contains FastPAD connections, or if the database has slave lcons with no connections.

If Gateway node is upgraded or rebuilt, before SV+ has synchronized with the network, SV+ needs to be cold-started (created SV+ database and restart SV+). This is required to ensure SV+ database consistency.

SV+ database and network may differ by value 1 for parameters PCR(0+1), SCR(0+1), MCR, ICR of some ATM-FR conceitedness. This happens because of the difference (rounding effect) in conversion algorithms used by SV+ and switch to convert values in cells/sec units to 100 bit/sec units.

SV+ CM GUI has text fields for the parameters PCR(0+1), SCR(0+1), MCR and ICR (all in the unit of cell/sec) on the ATM side of the ATM - FR ABR.FS provision window.
The front-end application (CM GUI) passes these values to the back-end process to setup the SNMP request PDU for the switch agent. Following are the MIB variable and the association value from the GUI:

: atmEndptPCR <-- PCR(0+1)
: atmEndptSCR <-- SCR(0+1)
: atmEndptMCR <-- MCR
: atmEndptQIR <-- IC

After the SNMP set request to the switch is done, the values will be deposited in the user_connection table. Following are the database table column names:

: l_pir (100 bit/sec) <-- PCR(0+1)
: l_cir (100 bit/sec) <-- SCR(0+1)
: l_mir (100 bit/sec) <-- MCR
: l_qir (100 bit/sec) <-- ICR

Since the unit for those four columns are in 100 bit/sec, conversion from cell/sec to 100 bit/sec is done.
The conversion algorithm results in 100 bps = ((384 * cps) + 99) / 100 as shown in the following table:

cell/second	100 bit/second
50	192
5760	22119
3259	12515
2834	10883

Note The converted values for 5760, 3259 and 2834 are rounded up to the nearest 100 bit/sec.

The conversion factor used by the switch (in this case BPX 9.1) is different from that used by SV+. Therefore, after the ConnObj Robust Message update, the user_connection table would have different values for those 4 columns. See the following table with example values:

Cell/second	SV+ 100 bit/second	Switch 100 bit/second
5760	22119	22118
3259	12515	12514
2834	10883	10882

The SV+ database may intermittently have incomplete connections for the following reasons. When a multi-segment PVC is being added, if a node receives connection add request, but doesn't respond to SV+, SV+ backs out all the segments from the other nodes which have responded to the add request and deletes those segments from the StrataView database. The node which didn't respond ends up having that segment. Because of this, any further attempt to add that connection, after the node becomes reachable, results in Connection Already Exists error in StrataView Plus. However, this connection segment may or may not appear in the SV+ database, depending on which node was not responsive. Figure 1 and Figure 2 provide examples of these scenarios:

Figure 1: Two Segment Connection

Figure 2: Three Segment Connection

: In Figure 1 and Figure 2, F1, F2 are feeder shelves, and S1, S2 are switch nodes. If S1 becomes unreachable after receiving an add request from SV+, but before sending the response back,'middle segment' will be added on S1, between S1 and S2. However, the connection segment details will not be in the SV+ database. Once S1 becomes reachable, configuration changes will be sent to SV+ and the SV+ database will be updated with the middle segment details. You can delete the incomplete connection at this time using StrataView Plus.
: However, if F1 (or F2) is an Axis shelf and it becomes unreachable after receiving an add connection segment request, SV+ is not updated with the end segment details, even if the node becomes reachable. The database update occurs when the next periodic Node Resync by SV+ occurs with that shelf.

A similar database inconsistency can occur during a delete connection operation. In this case, while a multi-segment PVC is being deleted, if a node receives a connection delete request, but doesn't respond to SV+, SV+ doesn't delete this segment information from the database. This results in a dangling connection segment in the SV+ database which doesn't exist on the node. However, this connection segment will be deleted from the SV+ database eventually. The time taken for this database synch-up (once the node becomes reachable) depends on the type of the node.

: In the above two examples, if S1 becomes unreachable after receiving delete request from SV+, but before sending the response back, 'middle segment' will be deleted on S1, between S1 and S2. However, this connection segment details will not be deleted from SV+ database. Once S1 becomes reachable configuration changes will be sent to StrataView and StrataView database will be updated accordingly.
: However, if F1 (or F2) is Axis shelf and it becomes unreachable after receiving delete connection segment request, SV+ doesn't delete the end segment details from the DB, even if the node becomes reachable. The database update happens whenever the next periodic Node Resync by SV+ happens with that shelf.

Network Configuration

Any node with IP address 192.0.0.0 or 0.0.0.0 will not be displayed or stored in SV+ database. In order to configure right network IP address use cnfnwip command on the switch.

Each IPX/BPX/IGX/Axis node to be managed by SV+ must be configured with IP Relay IP Address (cnfnwip). The gateway node must be configured with both LAN and IP Relay IP Addresses.

The IPX/BPX routing and IPX/AF feeder modes must be configured with read and write SNMP community names. The SNMP community names "public" and "private" are configured in SV+ for GET and SET respectively as defaults.

The directly attached node (Gateway node) must be configured with IP Relay IP address before starting SV+.

Node names, IP Addresses and NWIP addresses of the nodes in a network and across networks in multiple networks scenarios, should be uniquely configured.

Service Agents

For adding a connection the connectionIndex must be 0 (there is no need to do a GET on connAvailIndex). The actual index is internally generated by the connection service agent itself.

For the sake of backward compatibility, the 500 series traps are generated for 8.2 nodes, while the 20000 series traps are generated for 8.4 nodes.

Connection Manager

For DAS connections, deleting an end point from a segment and later adding it to another segment at a very fast rate may result in a database inconsistency.

Test Connection and Test Delay do not work for connections routed through a StrataCom virtual trunk cloud when the connection originates from an Axis or BPX.

Connection Manager GUI for preferred route displays ALL available trunks without considering the traffic class. As a result, it is possible to set a preferred route for a CBR connection traversing trunks that do not support CBR traffic.

SV+ shows the status of a connection based only on the routing segment status.

In the Connection Manager GUI, you must enter both the end points (i.e. node, shelf, slot, port) in the Add Connection window before entering any connection or midpoint parameters.

For an FRSM - ASI PVC connection, the error message "Remote SCR value out of range" generated by the remote BPX, indicates that the CIR value of the Frame Relay side is below the acceptable limit (cell rate) of the trunk between the AXIS shelf and its routing node. To correct the problem, one can increase the value of CIR. E.g., if the trunk between the AXIS shelf and the routing node is a BXM trunk, the CIR value should be at least 19.2 kbps (= 50 cell/sec).

ABR.FS connections cannot be added with default values for ATM-FR SIW connection. The 'ICR TO' value has to be changed.

Certain types of connections, such as VBR.1 or CBR, with policing parameters can't be modified by SV+ if the default was changed using the switch command line interface.

While adding three segment frame relay connections where one routing node is IGX and another is BPX, connections must be mastered on feeders connected to BPX. Attempting to master connections on feeders attached to IGX hub will generate "Internal error" error message, and the connection will not be added.

Three segment voice and data connections can only be added when both routing nodes are IGXs. This is due to a switch software limitation.

While adding connections originating and terminating on same feeder nodes, SV+ will treat these connections as three segment connections and will add three segments (two on the same feeder node, one on the routing node) to realize this connection.

Statistics Collection Manager

When you start a stand-alone SCM, the following message is not an error message: Cannot communicate with SV+, either SV+ is not active or another GUI is running presently.

You should select a routing node for the SCM time sync node.

For a group of selected nodes from which stats files are to be collected by a stand-alone SCM, the collection period should be set to the same value for all nodes.

If stats files are being saved, the SCM does not purge these files even if the disk is full.

The SCM supports 3100 nodes maximum in stand-alone mode.

For "CISCO 3800" node types, the network parameter 'Time-out period' has to be 5 seconds.

Whenever you perform a create_db operation, file statshistory.stats file must be manually deleted.

Prior to SWSW release 8.1, you could specify any time period for a peak interval from SV+. In SWSW 8.5, following rules are used when you configure peak interval through SV+. Violating the rule will cause TFTP error 22 displayed in the SCM.

a) The peak interval cannot be zero.

b) The peak interval must be a multiple of the polling interval

c) The peak interval must be a factor of the bucket interval

d) The peak interval CAN be the same as the bucket interval

The Switch needs some processing time to parse the stats.enable file. Depending on the number of stats and the number of objects this time can be very large. Currently SCM has a finite value for time-out (maximum 420 seconds) to wait for the switch response. Hence there might be cases where SCM will time-out waiting for switch to finish parsing the stats.enable file.If there are excessive time-outs then users should:
(1) cut down on number of stats enabled and be able to get the status of stats-enabling from SCM or
(2) keep the number of stats but losing the status of stats-enabling from the SCM. You can use CLI commands such as dspstatparms, dspchstatcnf, dsptrkstatcnf, dspportstatcnf and dsplnstatcnf to make sure their desired stats are enabled. Note that there can be occasional time-outs if a node is busy for that period of time, but this case at the best is intermittent and should go away once loading on the node stabilizes Following is the formula to calculate the time to enable statistics on the switch:
time = (stats / cnt) * delay
where
stats = (conns * stats_per_con) +
(CLNs * stats_per_cln) +
(trks * stats_per_trk) +
(ports * stats_per_port)

cnt = number of stats configured in one group before giving up CPU, a configurable parameter on the switch.
delay = a delay time between each group of stats get enabled, this is also a configurable parameter on switch.
This is captured in CR CSCdj39737.
Also see item 27 of 8.5 switch software release notes.

Platform

SV+ must not be started from the OpenWindows Cmdtool Window. If SV+ is started from Cmdtool, the Cmdtool may freeze the screen if Cmdtool window's log buffer is full.

While SV+ is running, if the X server crashes for any reason, then SV+ should be stopped and restarted.

While SV+ is running, if remote display is killed without properly shutting down the SV+ Desktop, then reopening it remotely may not succeed.

VNS

A VNS node must not be attached to feeder nodes. A VNS node may be added to a node isolated from the network.

Reports

The Wingz "Add Comment" option is not supported for virtual trunk and ATM connections. Wingz sometimes does not scroll up the list box properly.

Topology

Sometimes it may take 2-3 minutes to display new nodes after addition of virtual trunks. This is due to the time required to setup link0 and link1 subscriptions.

Specific Features Not Supported

ELMI feature on IGX and ALM-A card is not supported from SV+ 9.0.05.

StrataView SNMP Agent Notes

SNMP Agent functionality is unchanged from release 8.4 of SV+. Refer to release 8.4.09 release notes for SNMP Agent Notes. Relevant part of 8.4.09 release notes is reproduced here for completeness.

The basic SNMP Agent functionality is unchanged from release 8.2. ATM-ATM and ATM-FR cross connections are supported through the Connection Service Agent.The Port Service Agent will support a physical port addressing for FRSM and a logical port addressing for the rest of the cards. In the case of CESM and FRP, the logical port addressing is identical to physical port addressing. The structure of the SV+ 8.4 service MIB has been re-organized.

Configuration Notes

The SNMP master agent is configured to use 8161 as a default port id for agent communication. The configuration file SNMPAgent.conf for the master agent is located in /usr/users/svplus/config. If you are running another Network Manager which uses port number 8161, this UDP port can be configured to some other port number in this file as follows:

Syntax:

TRANSPORT special SNMP

OVER UDP SOCKET

AT PORT 8161

The Service MIB (Connection Service MIB and Port Service MIB) uses community strings for authentication. The Connection Service Agent and Port Service Agent processes use /usr/users/svplus/config/SNMPProxy.conf file as a configuration file. The SNMP community name strings can be configured in this file as follows:

Syntax:

GET_COMMUNITY public

SET_COMMUNITY private

The SNMP community names "public" and "private" are configured in this file for GET and SET respectively as defaults.

Installation Notes

The upgrade from SV+ releases 8.2 (SunOS), 8.4.xx (Solaris), 9.0.01 (Solaris), 9.0.02 (Solaris), 9.0.03 (Solaris), 9.0.04 (Solaris) to SV+ release 9.0.05 (Solaris) is supported in this release. Ir you are using SV+ 9.0.00, you should perform a full install, which recreates the database. Thus graceful upgrade from SV+ 9.0.00 is not supported.

Note The SV+ upgrade is not supported across different platforms. For example, you cannot upgrade from AIX-based SV+ release to a Solaris-based SV+ release or vice versa.

The following sections describe procedures to prepare for SV+ 9.0.05 installation and to upgrade from the following releases:

SV+ 8.2 (SUN OS)
SV+ 8.4.xx (Solaris)
SV+ 9.0.00 (Solaris)
SV+ 9.0.01 (Solaris)
SV+ 9.0.02 (Solaris)
SV+ 9.0.03 (Solaris)
SV+ 9.0.04 (Solaris)

Note The installer must have experience in UNIX system administration.

Installation Requirements

You must make sure at least 750 MB of disk space in /usr/users/svplus area can be allocated for SV+ 9.0.05 installation. In the case of upgrade, disk space used by existing SV+ software plus free disk space should be at least 750 MB.

The Solaris Package Check program (pkgchk) works with the SV+ 9.0.05 release. Pkgchk checks the accuracy of installed files or displays information about package files.

You should install Wingz software from the Wingz tape or CD. Note that WingZ version 2.5 should be installed for SV+ release 9.0. Then the customer should contact Wingz for a runtime license and blend it with SV+ 9.0.05. Failing to do so will result in following error messages when you click on the SV+ Report icon: "There is a problem with the registration information for this machine. Contact your system administrator".

If the SV+ station is a Sun Enterprise 4000 and the Informix is installed on a disk array (typically the device name is /dev/vx/rdsk/rootdg/vol03) then the ownership of the device and the group ownership of the device should be set to informix. The mode of the device should be 770. Otherwise, after reboot the machine, following error message will be shown in the console, "Shared memory is not initialized".

If you are installing HP/OV 4.x over an existing version make sure that the /etc/snmpd and /etc/snmpd.conf are removed or re-named before carrying out the upgrade. It is likely that you will see the following message when trying to re-start OV:

object manager name: netmon

behavior: OVs_WELL_BEHAVED

state: NOT_RUNNING

PID: -

last message: Can't talk to snmpd; see /usr/OV/log/netmon.trace for

info

exit status: exit(1)

Information left in these files causes problems for the new version of OpenView.

These files are not removed by the ovremove program.

If smux entry exists in /etc/services file, SV+ SNMPAgent process try to use that port and may have problem opening. For SV+ SNMPAgent processes to function properly this entry in /etc/services should be commented out, if it is not using default tcp port of 199.

Pre-installation Procedures

This section describes steps to prepare for installing SV+ 9.0.05. Since you could have different SV+ releases running, the following covers all these possibilities.

Currently Running SV+ 9.0.01

Step 1 Exit SV+

Step 2 If the existing SV+ was installed through the pkgadd command, remove it. Execute the following command as user root:

# pkgrm CSCOsv

You may use pkginfo and grep for CSCOsv

Step 3 Install SV+ 9.0.05 from the CD package.

See section Installing SV+ 9.0.05 for details.

Currently Running SV+ 8.4.xx or 9.0.00

Step 1 Exit SV+

Step 2 If running 8.4.xx, save a copy of the database. See section Export the Current Database for details. Note: This step is not necessary but it is recommended.

Step 3 Shutdown the current informix database, then execute the following command as user root:

# /usr/users/svplus/kill_db

Step 4 At this point, record the disk partition where the database resides. Use this partition path name for the subsequent SV+ installation prompt for the database raw partition name.

If SV+ 9.0.00 was running, execute the following command as user root:

# grep ROOTPATH /usr/users/informix/etc/onconfig

If SV+ 8.4.xx was running, execute the following command as user root:

# grep ROOTPATH /usr/users/informix/etc/tbconfig

The second column of the output is the disk partition where the database resides, such as /dev/rdsk/c0t1d0s7.

Step 5 Remove the older informix under /usr/users/informix:

If Informix was installed through the pkgadd command, execute the following command as user root:

# pkgrm CSCOinf

You may use pkginfo and grep for CSCOinf.

If Informix was installed through a tar file, execute the following commands as user root:

# rm -r /usr/users/informix

# rm -r /usr/users/informix72

Step 6 If /usr/users/informix72 is present, remove the older informix under /usr/users/informix72:

If Informix was installed through the pkgadd command, execute the following command as user root

# pkgrm CSCOinf

You may use pkginfo and grep for CSCOinf.

If Informix was installed through a tar file, execute the following command as user root:

# rm -r /usr/users/informix72

Step 7 6. If the existing SV+ was installed through the pkgadd command, remove it.

# pkgrm CSCOsv

You may use pkginfo and grep for CSCOsv.

Step 8 Install SV+ 9.0.05 from the CD package.

See section Installing SV+ 9.0.05 for details.

Currently Running SV+ 8.2

Since SV+ 8.2 runs in a SUN OS platform and 9.0.05 in Solaris, it is necessary to perform Informix dbexport on the SUN OS SV+ and then Informix dbimport on a Solaris in the upgrade process. Note: The dbimport step is incorporated in the installation script and will prompt you to enter the path where the database resides. You do not have to explicitly do dbimport.

Step 1 On the SV+ 8.2 machine, dbexport a copy of the database. Then copy the exported database to a separate machine.

See section Export the Current Database for details.

Step 2 Convert the SUN OS machine to a Solaris 2.5.1 platform.

To configure the machine, refer to Chapter 2, First Time Installation of Cisco SV+ Installation Guide for Solaris.

Step 3 Once the configuration is complete, one can proceed to install SV+ 9.0.05.

See section 3.2 Install SV+ 9.0.05 from the CD Package on page 4 for details.

Currently Running SV+ 8.1 or older

For currently running SV+ 8.1 or older release of SV+, install SV+ 9.0.05 as a new install (section 3.2, Install SV+ 9.0.05 from the CD Package, in page 4).

Installing SV+ 9.0.05

The SV+ 9.0.05 CD contains SV+ 9.0.05 software and Informix version 5.10. When you install the software, select the New Installation option.

Step 1 Insert CD in the attached CD driver. After waiting for 10 to 20 seconds execute the df command to see if the CDROM is mounted properly. Make sure Motif window manager mwm is running.

Step 2 First install Informix and SV+ from the /cdrom/cdrom0 by executing the following:

# pkgadd -d /cdrom/cdrom0 CSCOinf

Answer the prompts as follows:

< Informix installation related information displayed>

< ...... >

Do you want this directory created now [y,n,?,q]

Enter "y"

< Informix installation related information displayed>

< ..... >

[ Hit <RETURN> to continue display ]

Enter "<RETURN>"

Do you want to install these as setuid/setgid files [y,n,?,q]

Enter "y"

Do you want to continue with the installation of <CSCOinf> [y,n,?]

Enter "y"

< Informix installation related information displayed>

< ..... >

Wait for the following message.

Installation of <CSCOinf> was successful.

Step 3 Execute the following command:

pkgadd -d /cdrom/cdrom0 CSCOsv

Answer the prompts as follows:

< CSCOsv installation related information displayed>

< ...... >

Do you want this directory created now [y,n,?,q]

Enter "y"

Do you want to continue with the installation of <CSCOsv> [y,n,?]

Enter "y"

Do you want to install these as setuid/setgid files [y,n,?,q]

Enter "y"

Do you want to continue with the installation of <CSCOsv> [y,n,?]

Enter "y"

< Informix installation related information displayed>

< ..... >

(wait for the following message)

Installation of <CSCOsv> was successful.

Step 4 If you logged in as svplus user, logout of the current environment from the SV+ root menu, then login as svplus again.

Step 5 Ensure that WingZ 2.55 is loaded properly.

If an older version of Wingz was installed previously, remove it before installing Wingz 2.55 by executing the following command as user root:

# pkgrm IISCWingz

Step 6 Install SV+ 9.0.05. Execute the following command as user root:

./INSTALL

To install SV+ 9.0.05 new or upgrade from 9.0.00 and to reinitialize all the database tables, refer to section Install SV+ 9.0.05 from SV+ 9.0.00. To upgrade from SV+ 9.0.01, 8.2 or 8.4.xx and to preserve the database content, refer to section Upgrade from SV+ 9.0.01, 8.4.xx or SV+ 8.2.

Install SV+ 9.0.05 from SV+ 9.0.00

This installation procedure is similar to the previous release and will cause all database tables to be initialized. Choose the new installation option at the following prompt.

(1) NEW (Release 9.0 of SV+)

(2) UPGRADE (From previous release of SV+)

Enter number corresponding to installation type of x to exit:

Enter "1"

WARNING: In the following output, the installation script provides users with available partitions. It also picks up the swap partition as available raw partition. DO NOT use swap partition.

Checking existing partition....................... Successful

Available partitions (Solaris):

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

/dev/rdsk/c0t0d0s1

/dev/rdsk/c0t1d0s1

< Could be some more disk partition information displayed>

< ...... >

Checking Hard Disk count.......................... Successful

Disk Configuration Migration to SV+ 9.0

1) Single Raw Database Disk

2) Multiple Raw Database Disk

Enter number corresponding to disk configuration or x to exit:

Enter "1"

If upgrading from 9.0.01, the following prompt will be displayed:

Enter Raw Partition Name for rootdb (default: <same raw partition name as in the previous release>):

Hit return at the prompt to use the same raw partition as in 9.0.01.

If upgrade from releases older than 9.0.01, the following prompt will be displayed:

Enter Raw Partition Name for rootdb (default: not configured):

Enter "<the disk partition where database will reside>"

Note: If upgrading from 8.4.xx or 9.0.00, enter the same raw partition recorded in section Currently Running SV+ 8.4.xx or 9.0.00. Otherwise, you should enter the raw partition configured for the database.

Upgrade from SV+ 9.0.01, 8.4.xx or SV+ 8.2

This upgrade path will allow users to preserve the content of the database from releases 8.2, 8.4.xx, or 9.0.01. The following steps are involved with the upgrade. If upgrade from 8.2, make sure the exported database is in the local machine now, so that one can enter the path of the database at the prompt for importing database.

Answer the following prompts accordingly:

(1) NEW (Release 9.0 of SV+)

(2) UPGRADE (From previous release of SV+)

Enter number corresponding to installation type of x to exit:

Enter "2"

Supported Upgrade Path for SV+ Release 9.0

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

(1) From 8.2 (SUN OS)

(2) From 8.4.xx (Solaris)

(3) From 9.0.xx (Solaris)

Enter number corresponding to upgrade path or x to exit:

Enter "1", if upgrade from 8.2. Enter "2", if upgrade from 8.4.xx. Enter "3", if upgrade from 9.0.xx ( 9.0.01 or later releases)

Note: If 9.0.00 was running, you must exit here and install new.

WARNING: In the following output, the installation script provides uses with available partitions. It also picks up the swap partition as available raw partition. DO NOT use swap partition.

Checking existing partition....................... Successful

Available partitions (Solaris):

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

/dev/rdsk/c0t0d0s1

/dev/rdsk/c0t1d0s1

< Could be some more disk partition information displayed>

< ...... >

Checking Hard Disk count.......................... Successful

Disk Configuration Migration to SV+ 9.0

1) Single Raw Database Disk

2) Multiple Raw Database Disk

Enter number corresponding to disk configuration or x to exit:

Enter "1"

Note: If upgrade from 8.2 is chosen, it will then prompt you to enter the directory where the copy of the database one dbexport and saved.

If upgrade from 9.0.01, the following prompt will be displayed:

Enter Raw Partition Name for rootdb (default: <same raw partition name as in 9.0.01>):

Hit return at the prompt to use the same raw partition as in 9.0.01.

If upgrade from 8.4.xx or 8.2, the following prompt will be displayed:

Enter Raw Partition Name for rootdb (default: not configured):

Enter "<the disk partition where database will reside>

Note: If 8.4.xx was running previously, use the same raw partition as before. Enter the one noted down in Currently Running SV+ 8.4.xx or 9.0.00. Otherwise, you should enter the one configured for the database.

Export the Current Database

This section describes how to save a copy of the current database using Informix dbexport.

Step 1 Stop SV+ core processes

Step 2 As user svplus, make a directory dbdump under /user/users/svplus and change permission.

# mkdir /user/users/svplus/dbdump

# chmod 777 /user/users/svplus/dbdump

Step 3 As user informix, execute the following command:

# dbexport -o /user/users/svplus/dbdump stratacom

To find out disk space requirements, use the command tbstat -d and ensure that at least that much disk space is available.

Step 4 Save the content to a directory outside of /user/users/svplus, that is not easily being overwritten. Make sure that directory has enough space.

# cp -r /user/users/svplus/dbdump some_directory

Or save the database residing in /usr/users/svplus/dbdump onto a tape mounted on the /dev/rmt/0 drive:

# tar cvf /dev/rmt/0 /user/users/svplus/dbdump

Step 5 If SV+ 8.2 is running, one should copy the exported database to a remote machine, so that the database will not be overwritten in some directory of machine B:

# rcp -rp /user/users/svplus/dbdump < machine B>: <some directory>

or to a tape mounted on /dev/rmt/0:

# tar cvf /dev/rmt/0 /user/users/svplus/dbdump

Note Please refer to the Informix user manual for additional information on the db command.

Caveats

SV+ 9.0.05 Known Bugs

Bug ID Description

CSCdk02115

Roll down CSCdj92497, no data continuity for 1 segment data connection.
When you use SV+ to setup 1 segment data connection, though connection add is successful, there is no data continuity. The reason is SV+ presets only the local line/port parameters but not the remote one. For data continuity both sides should have same values for these parameters.

Preconfigure channel for remote endpoint for dfm enable, dfm length and eia update from the remote node's CLI before adding 1 segment data connection.

CSCdj47443

One occurrence of CM GUI core dump if exited in a certain way.
This core dump happens if users are trying to close the CM GUI by using Alt-F4 key AND CM GUI is trying to update the screen at the same time. Under such condition, a core dump is generated. It is possible that users may not be able to invoke CM GUI from Desktop.

There are two precautions.
First, users are recommended to use the File-Exit menu to exit the CM GUI. If this is observed then there is no impact on the functionality and no issues.

If however, users do use Alt-F4 by mistake and if they cannot subsequently restart CM GUI, then the desktop must be exited and restarted by invoking option "3" from SV+ script.

CSCdj47891

SV+ Stats GUI is slow first time after install
When statsmain is brought up first time after the install, by default, it goes to each node to get their statsmaster using SNMP Get and then collect stats using TFTP. Both operations go through IP-relay. The delay could be due to the heavy traffic over the ip-relay network. This delay can be minimized if IP subnets are properly planned and out-of-band management is already in place. Make sure that all the swiches have read snmp community string set to public and write snmp community string set to private.

CSCdj45264

RtmProxy: SV+Network.mib missing card reason, wrong port state for ASI
RtmProxy: SV+Network.mib missing card reason, wrong port state for ASI svPortState MIB object reports down state when it should report inactive state.

CSCdj31976

Test Delay from Conn GUI has misspelled error message
If test delay times out then the error message has few characters wrongly spelled. Known problem as of now, but this message conveys the time-out message. The same is true if test delay is aborted by switch. The messages displayed are as follows.
" ) Test endpoint operation aborte" for aborted operation and
" ) Test delay timed ou " for timed out operation.

CSCdj35196

Preferred route limit of 255 bytes may be inadequate in certain (very unlikely) network configurations
The preferred route limitation of 255 bytes is not enough if a connection routes over all 10 hops and more then 3 of them are over virtual trunks. If this happens and users need to configure preferred route then cli commands must be used. This problem has never been reported from field but was found by engineering while analyzing some other limits.

CSCdj42660

Upgrade Status Window has duplicate entries if nodes have invalid ip addresses
When managing a network where some nwip addresses are not configured correctly following behavior is observed.
a. Until the nwip addresses are configured correctly the nodes do not appear on the topology.
This is correct behavior.
b. However after all the nwip addresses are configured correctly the display upgrade status window still has the invalid ip address nodes appended at the end of the list.

CSCdj44061

: PortProxy: intermittent gen err when walking the svPortNode
Walking the svPortNode Entry using BPX hub as index and then walking the same table using BPX.axis as index will give gen error. But, subsequent walk on the table using BPX.axis as index works correctly.

CSCdj51194

Need to inform user when using incorrect password to restore configuration
Need to inform user when using an incorrect password to restore configuration Instead only a access violation message is displayed.

CSCdj41484

Two garbage lines seen at the end of SV+ Admin Process Log
Some garbage output has been seen on SV+ Admin window on two last lines.

CSCdj74802

Voice ports are shown as port number 0 in the conn
If SV+ 9.0.03 is attached to a swsw 8.4 or earlier, all CDP/CVM cards are being reported as port number 0 in COnnMgr Gui. There is no workaround. However, it should be noted that since voice/data connections on CDP/CVM cards were not supported by SV+ before swsw 8.5, this does not block any functionality. The port 0 in the list can be safely ignored.

CSCdj75650

After runcnf the SV+ does not update the connection database accordingly
After performing "runcnf" for the entire switch, it was found that in some cases there were pending robust messages in the switch either due to one of the nodes becoming unreachable or multiple trunk failure. As a result, SV+ did not get all the connections. Currently, the way to get around the missing connections problem on SV+ is to do a cold start after a "runcnf".

CSCdj75650

cmgrd - Failed to configure preferred route for UVM-CVM connection
This happens when preferred route is applied for a UVM-CVM connection. There is no workaround.

Bug ID	Description
CSCdk02115	Roll down CSCdj92497, no data continuity for 1 segment data connection. When you use SV+ to setup 1 segment data connection, though connection add is successful, there is no data continuity. The reason is SV+ presets only the local line/port parameters but not the remote one. For data continuity both sides should have same values for these parameters. Preconfigure channel for remote endpoint for dfm enable, dfm length and eia update from the remote node's CLI before adding 1 segment data connection.
CSCdj47443	One occurrence of CM GUI core dump if exited in a certain way. This core dump happens if users are trying to close the CM GUI by using Alt-F4 key AND CM GUI is trying to update the screen at the same time. Under such condition, a core dump is generated. It is possible that users may not be able to invoke CM GUI from Desktop. There are two precautions. First, users are recommended to use the File-Exit menu to exit the CM GUI. If this is observed then there is no impact on the functionality and no issues. If however, users do use Alt-F4 by mistake and if they cannot subsequently restart CM GUI, then the desktop must be exited and restarted by invoking option "3" from SV+ script.
CSCdj47891	SV+ Stats GUI is slow first time after install When statsmain is brought up first time after the install, by default, it goes to each node to get their statsmaster using SNMP Get and then collect stats using TFTP. Both operations go through IP-relay. The delay could be due to the heavy traffic over the ip-relay network. This delay can be minimized if IP subnets are properly planned and out-of-band management is already in place. Make sure that all the swiches have read snmp community string set to public and write snmp community string set to private.
CSCdj45264	RtmProxy: SV+Network.mib missing card reason, wrong port state for ASI RtmProxy: SV+Network.mib missing card reason, wrong port state for ASI svPortState MIB object reports down state when it should report inactive state.
CSCdj31976	Test Delay from Conn GUI has misspelled error message If test delay times out then the error message has few characters wrongly spelled. Known problem as of now, but this message conveys the time-out message. The same is true if test delay is aborted by switch. The messages displayed are as follows. " ) Test endpoint operation aborte" for aborted operation and " ) Test delay timed ou " for timed out operation.
CSCdj35196	Preferred route limit of 255 bytes may be inadequate in certain (very unlikely) network configurations The preferred route limitation of 255 bytes is not enough if a connection routes over all 10 hops and more then 3 of them are over virtual trunks. If this happens and users need to configure preferred route then cli commands must be used. This problem has never been reported from field but was found by engineering while analyzing some other limits.
CSCdj42660	Upgrade Status Window has duplicate entries if nodes have invalid ip addresses When managing a network where some nwip addresses are not configured correctly following behavior is observed. a. Until the nwip addresses are configured correctly the nodes do not appear on the topology. This is correct behavior. b. However after all the nwip addresses are configured correctly the display upgrade status window still has the invalid ip address nodes appended at the end of the list.
CSCdj44061	: PortProxy: intermittent gen err when walking the svPortNode Walking the svPortNode Entry using BPX hub as index and then walking the same table using BPX.axis as index will give gen error. But, subsequent walk on the table using BPX.axis as index works correctly.
CSCdj51194	Need to inform user when using incorrect password to restore configuration Need to inform user when using an incorrect password to restore configuration Instead only a access violation message is displayed.
CSCdj41484	Two garbage lines seen at the end of SV+ Admin Process Log Some garbage output has been seen on SV+ Admin window on two last lines.
CSCdj74802	Voice ports are shown as port number 0 in the conn If SV+ 9.0.03 is attached to a swsw 8.4 or earlier, all CDP/CVM cards are being reported as port number 0 in COnnMgr Gui. There is no workaround. However, it should be noted that since voice/data connections on CDP/CVM cards were not supported by SV+ before swsw 8.5, this does not block any functionality. The port 0 in the list can be safely ignored.
CSCdj75650	After runcnf the SV+ does not update the connection database accordingly After performing "runcnf" for the entire switch, it was found that in some cases there were pending robust messages in the switch either due to one of the nodes becoming unreachable or multiple trunk failure. As a result, SV+ did not get all the connections. Currently, the way to get around the missing connections problem on SV+ is to do a cold start after a "runcnf".
CSCdj75650	cmgrd - Failed to configure preferred route for UVM-CVM connection This happens when preferred route is applied for a UVM-CVM connection. There is no workaround.

SV+ 9.0.04 Fixed Bugs

This maintenance release is required if the network has Axis feeders with release 4.0.10 or later.

After SV+ 9.0.04 is installed, run /usr/users/svplus/clearOVDb.s as super user to clean the OV database before starting ovw. This is required for CSCdj59952 fix to take effect.

If the network has Axis shelves running 4.0.13 or later release this version of StrataView is required to manage those shelves. The previous versions of StrataView can't manage 4.0.13 Axis shelves.

Bug ID Description

CSCdj59952

When using the MIB browser in HP OpenView for BPX node in the StrataView map, the nodename is postfixed -bpx. As a result MIB browser doesn't understand if this name is given.

In release SV+ 9.0.04 in the routing level map, all bpx nodes label and selection names are constructed from node names suffixed with "-hub". In the feeder level map, the label and selection name of the core shelf are the same as the node name. You must select the core shelf for the bpx node in the feeder level map to launch Mib Browser. For IPX, IGX and AXIS, you can select the respective node and launch Mib Browser. The name/ip address displayed in the MIB Browser will be correct.

As a work-around for the above problem the core shelf for the bpx node can be selected from the feeder level map. Then from the Misc menu, if SNMP Mib Browser is selected, the name/ip address displayed in the MIB Browser will be correct.

CSCdj81530

Specifying a value more than 255 for atmEndPointVpi for BXM card on a NNI port, as part of the ConnProxy script results in an error. This problem has been fixed in ConnProxy process.

CSCdj89037

statsparser process fails to parse stat files collected from AXIS shelves with the following error message in /usr/users/svplus/statsmgrdir/statsparser.err file.

"Mar 17 17:17:00 ERROR:0 statsparser.c@668: FILE ABORTED: File:/usr/users/svplus/incoming/<axisnodename>.0317981700

Mar 17 17:17:00 ERROR:0 BinaryProcessor.c@258: Parser Template Node Not Found for Binary Statistics File Record Entry"

This problem happens only with release 4.0.09x Axis shelves.

CSCdk09192

A problem in configd process which makes the loadcnf command given from BPX/IPX/IGX CLI abort has been fixed. This could happen if IP network is lossy and is prone to drop packets. When configuration packets going from SV+ to a switch get dropped, the retry (retransmission) mechanism in SV+ does not work & loadcnf aborts.

The work-around for this to use loadcnf command on the switch when the network is less used

CSCdk10837

Equipment Manager GUI shows the secondary slot as empty after the cold start even though the primary card is covered by the secondary card. It should show the secondary as activated. This problem has been fixed in emc process.

When primary and secondary cards are setup and then primary card is removed and secondary is activated while SV+ is running, Equipment Manager GUI shows the secondary card as empty and the primary card as covered slot. If SV+ is stopped and cold started, Equipment Manager GUI still shows the secondary slot as empty.

This happens for secondary FRSM8 cards with no back card only.

Further Problem Description

While investigating this problem, a problem similar to this and applies to all types of cards was found. In this case Equipment Manager GUI shows the primary slot as empty after the cold start even though the primary card is covered by the secondary card. It should show the primary card as covered slot.

This problem can happen in the following scenario. When primary and secondary cards are setup and then primary card is removed while SV+ is running, Equipment Manager GUI shows the secondary card as active and the primary card as covered slot. If SV+ is then stopped and restarted after creating SV+ database, Equipment Manager GUI shows the primary slot as empty.

As a work-around for this the primary card can be inserted back into the slot.

CSCdk12069

Node resync operation in Equipment Manager GUI fails with Axis shelves running release 4.0.13 software. This problem has been fixed in emc process.

CSCdk12201

User connection is not reset back to OK state when connection is re-established. This problem has observed on CESM-CESM connections in SV+ 8.4. This problem has been fixed in Connection Manager GUI process.

CSCdk12929

Connection Manager GUI only allows the range 1..24,000 cells for the parameter MBS of the BXM cards which support the range 1..5,000,000 cells. This has been fixed in ConnMgr process.

CSCdk13002

Equipment Manager GUI doesn't allow to filter on line 4 of FRSM-HS1 card, even it has 4 lines. It comes up with a error message "Field:line number: The filed you entered has a range of 1 to 3. Please re-enter the field".

The FRSM-HS1 supports two different types of back cards. This problem is only applicable to the situation where the back card is X.21(i.e. 4-lines).

CSCdk13155

In a redundancy card setup, when a secondary card takes over in primary card failure situation, no new ports or PVCs can be added to the primary card, if the primary card is pulled out. This problem has been fixed in emc process.

This problem has been observed with SV+ 8.4.11 and prior releases managing release 4.0.12 or later Axis shelves.

CSCdk13162

StrataView node resync with axis shelves fails. This problem happens only when any redundancy action occurred like softswitch, primary card failed or pulled out. In such cases the SV+ database will be out of sync with axis shelves. This has been observed with StrataView 8.4.11 managing Axis 4.0.13 shelves. This problem has been fixed in emc process.

CSCdk16795

An intermittent problem in topod process, because of which some of the AXIS nodes are wrongly shown as unreachable in NWBrowser has been fixed.

This problem occurs when an AXIS node has no alarm or connection problem with its routing node. During SV+ cold start, these nodes are mistakenly reported as alarm status 'clear', but mgmt_state 'unreachable'.

CSCdk21635

Non existing trunk appear intermittently on SV+ Topology and HPOV Topology maps. This problem has been observed in SV+ 8.4 usually after swithcc operation is done on 8.4 SWSW network. The problem has been fixed in topod process.

CSCdk22603

SCM appears to get stuck when it is trying to reach timesync host. This problem could happen in either of these conditions.

1 . Time Sync host is not reachable

2 . Network responds after a period close to the (sync with timesync host) retry time.

This problem has been fixed in statsmain process. With this fix the default retry time to sync with timesync host is 5 minutes and this can be set to anywhere from 4 to 14 minutes by a environment variable TIMESYNCPERIOD.

When the above problem happens one can exit SCM and set this TIMESYNCPERIOD to a value more than network response time for timesync host status and then start SCM. This time if timesync host is not reachable, you will be able to change the timesync host from SCM in NodeConfig parameters.

Further Problem Description

There was a problem in the way the time sync host was contacted by SCM. If the time sync host was unreachable then a particular host may kept on gutting retried.

CSCdk28135

Checksum error is shown in statsmain error log even though the collected stats file is not corrupted. This problem has been fixed in statschild and statsparser processes.

This problem occurs when the collected stats file is of such a size such that the checksum straddles two blocks. Each block is assumed to be of size 4096.

Further Problem Description

The child process on getting the stats file validates it using the checksum at the end of the file. When this checksum straddles two blocks of size 4096, StrataView checksum computation procedure breaks down and flags the file as corrupt.

CSCdk30217

Different SNMP community strings other than the default settings are not supported for VNS. VNS is shown as unreachable on SV+ if the SNMP community strings on VNS are changed from default. This problem has been fixed in rtm process.

When a VPC is created thru ConnProxy it fails with error message

CSCdk30572

"Invalid variable type,length or value". Since the VPC does not have a specific vci, it is stored in the SV+ DB with vci=65537. Hence, this error. This problem can also be seen whenever a SNMP get operation is done on the endpoints of the VPC connection, or when a SNMP netx or SNMP walk kind of operations are done. This problem has been fixed ConnProxy process.

CSCdk35335

SNMP GET on atmEndPointVSVD always returns disable. This has been fixed in ConnProxy process.

CSCdk36034

Unknown line interface is reported by SV+ whenever trap 20001 is received. This trap is received whenever a line cable is pulled out and line alarm is generated. This problem has been fixed in eventd process.

When a line alarm occurs, SWSW sends SV+ robust alarm message. The interface varbind in 20001 trap sent out by SV+ contains a value "Unknown" (1). This is because the message sent to SV+ from SWSW is as below:

1 . T1

2 . E1

CSCdk36049

SV+ database table 'circuit_line' shows wrong information in column 'l_line'; the l_line field has value 255. This problem applies to circuit lines on IPX, IGX and BPX only. This problem has been fixed in emsc process.

Bugs Fixed in SV+ 9.0.03 Patch 2

The following bugs were fixed in release 9.0.03.Patch 2.

Bug ID Description

CSCdj81530

Connection Proxy can't setup ATM connections if the VPI value given is more than 255 for connections involving BXM NNI port. It has been fixed to take the values for atmEndPointVpi in the range of 0 to 4095 for BXM NNI ports.

CSCdk05629

Minimum PCR value shown by Connection Manager GUI for a PVC is different than that is shown on the switch. This has been fixed in Connection Manager GUI and ConnProxy processes.

This problem has been observed in StrataView 9.0.03 when managing switches running 8.4.19 SWSW

CSCdk08930

A problem related to managing more than 9 networks in emd process has been fixed. This problem shows up in the form of the emd process dying and getting restarted multiple times. This in turn makes the SV+ database to be inconsistent with the status and configuration of Axis nodes in the network.

This has been noticed in a multi-network environment where there are more than 8 networks being managed by SV+.

The problem was caused by the fact that topod was busy when emd comes up and tries to register with topod. This has been fixed by making sure that topod doesn't subscribe to the network before all the core clients including emd have registered so that the client will be able to register successfully. Also a retry mechanism has been implemented in emd.

CSCdl13911

An intermittent exit problem in rtm process has been fixed. This problem shows up in the form of the rtm process dying and getting restarted by the watchdog.

This problem seem to show up in multiple-network or large network environment.

The problem was being caused by a bad interprocess connection between rtm and one other process. This has been fixed by setting the secure mode on the connection to make sure that the calling process (rtm) will not die even if the call doesn't go through.

Bug ID	Description
CSCdj81530	Connection Proxy can't setup ATM connections if the VPI value given is more than 255 for connections involving BXM NNI port. It has been fixed to take the values for atmEndPointVpi in the range of 0 to 4095 for BXM NNI ports.
CSCdk05629	Minimum PCR value shown by Connection Manager GUI for a PVC is different than that is shown on the switch. This has been fixed in Connection Manager GUI and ConnProxy processes. This problem has been observed in StrataView 9.0.03 when managing switches running 8.4.19 SWSW
CSCdk08930	A problem related to managing more than 9 networks in emd process has been fixed. This problem shows up in the form of the emd process dying and getting restarted multiple times. This in turn makes the SV+ database to be inconsistent with the status and configuration of Axis nodes in the network. This has been noticed in a multi-network environment where there are more than 8 networks being managed by SV+. The problem was caused by the fact that topod was busy when emd comes up and tries to register with topod. This has been fixed by making sure that topod doesn't subscribe to the network before all the core clients including emd have registered so that the client will be able to register successfully. Also a retry mechanism has been implemented in emd.
CSCdl13911	An intermittent exit problem in rtm process has been fixed. This problem shows up in the form of the rtm process dying and getting restarted by the watchdog. This problem seem to show up in multiple-network or large network environment. The problem was being caused by a bad interprocess connection between rtm and one other process. This has been fixed by setting the secure mode on the connection to make sure that the calling process (rtm) will not die even if the call doesn't go through.

Bugs Fixed in SV+ 9.0.03 Patch 1

The following bugs were fixed in release 9.0.03.Patch1

Bug ID Description

CSCdk08930

SV+ unable to support 9 networks

Symptom: Emd exits when fails to register with the topod process when multiple networks are managed by SV+. As a result, all AXIS nodes cannot be managed from SV+.

Workaround: In ~svplus/config/watchdog.conf file, move the line begining with emsd under the line which begins with cmgrd. Also, move the line begining with statsparser under the line which begins with databroker.

CSCdk04250

Port cac over ride mib checks for incorrect release number.

Symptom: Cannot set BPX ATM port for CAC override. There is no workaround.

Bug ID	Description
CSCdk08930	SV+ unable to support 9 networks Symptom: Emd exits when fails to register with the topod process when multiple networks are managed by SV+. As a result, all AXIS nodes cannot be managed from SV+. Workaround: In ~svplus/config/watchdog.conf file, move the line begining with emsd under the line which begins with cmgrd. Also, move the line begining with statsparser under the line which begins with databroker.
CSCdk04250	Port cac over ride mib checks for incorrect release number. Symptom: Cannot set BPX ATM port for CAC override. There is no workaround.

Bugs Fixed in SV+ 9.0.03

The following bugs were fixed in release 9.0.03:

Bug ID Description

CSCdj84455

emd core dump

Symptom: Emd exits when fails to register with the topod process. This happens when topod is not running.

Workaround: Restart SV+.

CSCdj83361

Roll down CSCdj72384 - statsmain has incorrect node version info in cache

Symptom: If the incorrect node release is lower than the actual one, some stats which are supported for the actual release of node cannot be enabled. This incorrect node version occurs if SCM has connected to a different network from the previous network.

Workaround: Delete stathistory.stats file under /usr/users/svplus/statsmgrdir and restart SCM.

CSCdj84298

Wingz does not display object for selected line statistics

Symptom: No E1 line objects are listed in the Object Available window

Workaround: None

CSCdj85870

EMSC will not update port status for BXM ports

Symptom: Port alarm status for some BXM cards are not updated.

Workaround: None

CSCdj86766

Internal Error: Failed to modify connection: Cannot get selected connection.

Symptom: When a connection is in selected state in the main window, and an event(DBKR_ALARM_EVENT) comes for that connection, you will get the above error message if an attempt is made to modify that connection.

Workaround: Wait for a few seconds and try to modify again.

CSCdj87117

Make pkgchk work for 9.0.03

Symptom: When run "pkgchk" on CSCOsv, CSCOinf and CSCOscm packages, there are error messages on all the files in the package. Thus, it is very difficult to pinpoint which file got modified inadverdently in the file audit process.

Workaround: None

Bug ID	Description
CSCdj84455	emd core dump Symptom: Emd exits when fails to register with the topod process. This happens when topod is not running. Workaround: Restart SV+.
CSCdj83361	Roll down CSCdj72384 - statsmain has incorrect node version info in cache Symptom: If the incorrect node release is lower than the actual one, some stats which are supported for the actual release of node cannot be enabled. This incorrect node version occurs if SCM has connected to a different network from the previous network. Workaround: Delete stathistory.stats file under /usr/users/svplus/statsmgrdir and restart SCM.
CSCdj84298	Wingz does not display object for selected line statistics Symptom: No E1 line objects are listed in the Object Available window Workaround: None
CSCdj85870	EMSC will not update port status for BXM ports Symptom: Port alarm status for some BXM cards are not updated. Workaround: None
CSCdj86766	Internal Error: Failed to modify connection: Cannot get selected connection. Symptom: When a connection is in selected state in the main window, and an event(DBKR_ALARM_EVENT) comes for that connection, you will get the above error message if an attempt is made to modify that connection. Workaround: Wait for a few seconds and try to modify again.
CSCdj87117	Make pkgchk work for 9.0.03 Symptom: When run "pkgchk" on CSCOsv, CSCOinf and CSCOscm packages, there are error messages on all the files in the package. Thus, it is very difficult to pinpoint which file got modified inadverdently in the file audit process. Workaround: None

Bugs Fixed in SV+ 9.0.02

The following bugs were fixed in release 9.0.02.

Bug ID Description

CSCdj35673

Symptom: IGX feeders not seen by CM GUI nor NWTopology after being deleted and re-added

Workaround: Exit the DeskTop application and start it again.

CSCdj63233

Symptom: Wingz: Saving/Retrieving template causes the Raw Data Report to disappear

Workaround: Restart Wingz to use the Raw Data Report

CSCdj65482

Symptom: After SV+ installation, Wingz will not launch from DeskTop

Workaround: Do the following steps:

1 Enter "cd /usr/users/Wingz"

2. Enter "su root"

3. Enter "find . -print | xarg chown svplus"

4. Enter "su svplus"

5. Enter "ln -s DataLink/DBLink DBLink"

CSCdj65804

Symptom: SV+ will not start after installation due to wrong file ownership in svplus.conf

Workaround: Manually change the file ownership:

chown svplus $SVPLUS_ROOT/config/svplus.conf

chmod 644 $SVPLUS_ROOT/config/svplus.conf

CSCdj65837

See descripton of CSCdj65482 and CSCdj63230

CSCdj27687

Symptom: Wingz error message, "Unable to call function", keeps appearing forever when scrolling down

the connection object list while the plot window is open.

Workaround: Close the plot window before scrolling down the connection list from the Raw Data Report window.

CSCdj43801

Symptom: Eventd/RtmProxy: When attached with a 8.2 network, incorrect trunk type in trunk traps

and incorrect connection type in connection traps were sent

Workaround: No workaround

CSCdj56495

Symptom: CMGUI: When attempt to add a data connection via CM GUI and if the SNMP agent returns an error regarding object not found, there is a spelling error in this message, "An error encountered while doing a GET operation prior to doing SET ......"

Workaround: No workaround

CSCdj63230

Symptom: Wingz 2.5: When Wingz is brought up, many unnecessary pop ups and flashing are displayed.

Workaround: Manually close the pop ups and wait until the flashing stops

CSCdj65404

Symptom: Installation: When install SV+ from a CD via "pkgadd "CSCOsv, there is a warning states.

that Wingz is a pre-requisite when Wingz is not a part of the SV+ package.

Workaround: Ignore the warning.

CSCdj65427

Symptom: After SV+ installation, you cannot use "top" and "tracerout" due to incorrect

permissions/ownerships of of these two binary files

Workaround: Manually modify the permissions/ownerships of of these two files as root:

/usr/ucb/chown root.svplus /usr/users/svplus/tools/traceroute

chmod 4555 /usr/users/svplus/tools/traceroute

CSCdj69945

Symptom: when a node is deleted, the associated card, peripheral, voice and data channels entries will be removed from the database.

Workaround: No workaround

CSCdj80628

Symptom: When an abit alarm is originated from the AIT end of a segment, SV+ does not show a-bit failures for 2 segment FR, voice and data connections

Workaround: No workaround

CSCdj74473

Symptom: SV+ shows OK data/voice connections as in OK/A-bit alarm

Workaround: No workaround

CSCdj62532

Symptom: PortProxy does not support UFM port

Workaround: No workaround

CSCdj82123

Symptom: Wingz does not support Add Comment feature

Workaround: No workaround

Bug ID	Description
CSCdj35673	Symptom: IGX feeders not seen by CM GUI nor NWTopology after being deleted and re-added Workaround: Exit the DeskTop application and start it again.
CSCdj63233	Symptom: Wingz: Saving/Retrieving template causes the Raw Data Report to disappear Workaround: Restart Wingz to use the Raw Data Report
CSCdj65482	Symptom: After SV+ installation, Wingz will not launch from DeskTop Workaround: Do the following steps: 1 Enter "cd /usr/users/Wingz" 2. Enter "su root" 3. Enter "find . -print \| xarg chown svplus" 4. Enter "su svplus" 5. Enter "ln -s DataLink/DBLink DBLink"
CSCdj65804	Symptom: SV+ will not start after installation due to wrong file ownership in svplus.conf Workaround: Manually change the file ownership: chown svplus $SVPLUS_ROOT/config/svplus.conf chmod 644 $SVPLUS_ROOT/config/svplus.conf
CSCdj65837	See descripton of CSCdj65482 and CSCdj63230
CSCdj27687	Symptom: Wingz error message, "Unable to call function", keeps appearing forever when scrolling down the connection object list while the plot window is open. Workaround: Close the plot window before scrolling down the connection list from the Raw Data Report window.
CSCdj43801	Symptom: Eventd/RtmProxy: When attached with a 8.2 network, incorrect trunk type in trunk traps and incorrect connection type in connection traps were sent Workaround: No workaround
CSCdj56495	Symptom: CMGUI: When attempt to add a data connection via CM GUI and if the SNMP agent returns an error regarding object not found, there is a spelling error in this message, "An error encountered while doing a GET operation prior to doing SET ......" Workaround: No workaround
CSCdj63230	Symptom: Wingz 2.5: When Wingz is brought up, many unnecessary pop ups and flashing are displayed. Workaround: Manually close the pop ups and wait until the flashing stops
CSCdj65404	Symptom: Installation: When install SV+ from a CD via "pkgadd "CSCOsv, there is a warning states. that Wingz is a pre-requisite when Wingz is not a part of the SV+ package. Workaround: Ignore the warning.
CSCdj65427	Symptom: After SV+ installation, you cannot use "top" and "tracerout" due to incorrect permissions/ownerships of of these two binary files Workaround: Manually modify the permissions/ownerships of of these two files as root: /usr/ucb/chown root.svplus /usr/users/svplus/tools/traceroute chmod 4555 /usr/users/svplus/tools/traceroute
CSCdj69945	Symptom: when a node is deleted, the associated card, peripheral, voice and data channels entries will be removed from the database. Workaround: No workaround
CSCdj80628	Symptom: When an abit alarm is originated from the AIT end of a segment, SV+ does not show a-bit failures for 2 segment FR, voice and data connections Workaround: No workaround
CSCdj74473	Symptom: SV+ shows OK data/voice connections as in OK/A-bit alarm Workaround: No workaround
CSCdj62532	Symptom: PortProxy does not support UFM port Workaround: No workaround
CSCdj82123	Symptom: Wingz does not support Add Comment feature Workaround: No workaround

SV+ 8.4 Bugs Fixed in SV+ 9.0.02

The following bugs were fixed in 8.4 and rolled up into release 9.0.02.

Bug ID Description

CSCdj52243

packet_line table has corrupted entries

CSCdj40746

When a statistic file is found bad, the SCM will not re-get the f

CSCdj41747

RtmProxy return gen err when walking the lineGroup mib for an IPX

CSCdj41775

Specific 500 trap gives svConnType value of 5 which is undefined

CSCdj45001

Comm failure messages in maintlog are not converted to traps

CSCdj47539

Multiple Stats Ager processes in SV+

CSCdj49013

Preferred routes via SNMP off by one on trunk info

CSCdj49468

Connection Mgr Gui crashed after certain input sequence involving

CSCdj49612

cmgrd disconnected from databroker for 2 hours ICORE (ispan976468

CSCdj50252

Modification of PVC with icrto > 8000ms problem via snmp mib

CSCdj50479

tftpchild may store data from previous session to current file

CSCdj51047

EM GUI - cannot configure redundant card for HSSI.

CSCdj52053

Modifying a Fr-ATM connection changes some values to defaults

CSCdj52061

watchdog.conf can get removed when the SNMPAgent/Proxies are kill

CSCdj53960

EMGUI cannot configure SRMs intermittently.

CSCdj54165

Connection manager fails to delete/modify cons.

CSCdj55784

tftpmgr starts one child less, whenever a child is manually kille

CSCdj55790

Enhance RTM to poll INS faster than an AXIS node.

CSCdj57299

AXIS clock source configuration is not displayed accurately in EM

CSCdj59754

snmp error 152 while trying to increase cir on fr-atm com

CSCdj60562

Customer needs informaation about Informix Database tables and Ob

CSCdj63341

After SV warmstart, Shared Mem failure prevents GUI node list pop

CSCdj63377

SV+ became unsubscribed to all AXIS shelves.

CSCdj63440

No ports seen thru ConnManager.

CSCdj63905

EMGUI does not properly display admin/loop status for SRM

CSCdj64646

EMGUI view counters does not reflect input parameters

CSCdj65376

EMGUI view counters does not refect value on switch.

CSCdj24454

Download lcbs not getting freed up.

CSCdj39053

Dbexport illegal stored procedure failure

CSCdj48237

Create a read only Connection Manager GUI

CSCdj49244

SV+ log files and ImagDownLoad program shows 100 for Year 2000

CSCdj49998

ConnProxy: ServiceMib definition of pref Route lacks trunk remote

CSCdj50369

SV+ startup script option 8 is not functioning. INS ANI Configura

CSCdj50377

Scroll bar in NORMAL congui window disappear after coming back fr

CSCdj50752

Configs saved using savecnf do not show BRAM or node ids in the S

CSCdj50938

Changing assign severity twice causes INTERNAL ERROR 639 on HPOV4

CSCdj52643

No HPOV format for trap 20007 sent by RtmProxy

CSCdj52856

Topod doesnt update the debug level passed thru command line

CSCdj53355

tstdelay doesnt work for local connection on ConnMgr

CSCdj54427

emd: dberr 100 and 239 when deleting a link of an IMATM port

CSCdj56246

Makefiles generated for SV+ processes do not include all the flag

CSCdj61406

UMR and UMW problems in emsc as shown by Purify

CSCdj63598

wrong stats if peak interval = bucket interval

CSCdj51831

NWTopology gives warning msg at console when listing multiple tru

Bug ID	Description
CSCdj52243	packet_line table has corrupted entries
CSCdj40746	When a statistic file is found bad, the SCM will not re-get the f
CSCdj41747	RtmProxy return gen err when walking the lineGroup mib for an IPX
CSCdj41775	Specific 500 trap gives svConnType value of 5 which is undefined
CSCdj45001	Comm failure messages in maintlog are not converted to traps
CSCdj47539	Multiple Stats Ager processes in SV+
CSCdj49013	Preferred routes via SNMP off by one on trunk info
CSCdj49468	Connection Mgr Gui crashed after certain input sequence involving
CSCdj49612	cmgrd disconnected from databroker for 2 hours ICORE (ispan976468
CSCdj50252	Modification of PVC with icrto > 8000ms problem via snmp mib
CSCdj50479	tftpchild may store data from previous session to current file
CSCdj51047	EM GUI - cannot configure redundant card for HSSI.
CSCdj52053	Modifying a Fr-ATM connection changes some values to defaults
CSCdj52061	watchdog.conf can get removed when the SNMPAgent/Proxies are kill
CSCdj53960	EMGUI cannot configure SRMs intermittently.
CSCdj54165	Connection manager fails to delete/modify cons.
CSCdj55784	tftpmgr starts one child less, whenever a child is manually kille
CSCdj55790	Enhance RTM to poll INS faster than an AXIS node.
CSCdj57299	AXIS clock source configuration is not displayed accurately in EM
CSCdj59754	snmp error 152 while trying to increase cir on fr-atm com
CSCdj60562	Customer needs informaation about Informix Database tables and Ob
CSCdj63341	After SV warmstart, Shared Mem failure prevents GUI node list pop
CSCdj63377	SV+ became unsubscribed to all AXIS shelves.
CSCdj63440	No ports seen thru ConnManager.
CSCdj63905	EMGUI does not properly display admin/loop status for SRM
CSCdj64646	EMGUI view counters does not reflect input parameters
CSCdj65376	EMGUI view counters does not refect value on switch.
CSCdj24454	Download lcbs not getting freed up.
CSCdj39053	Dbexport illegal stored procedure failure
CSCdj48237	Create a read only Connection Manager GUI
CSCdj49244	SV+ log files and ImagDownLoad program shows 100 for Year 2000
CSCdj49998	ConnProxy: ServiceMib definition of pref Route lacks trunk remote
CSCdj50369	SV+ startup script option 8 is not functioning. INS ANI Configura
CSCdj50377	Scroll bar in NORMAL congui window disappear after coming back fr
CSCdj50752	Configs saved using savecnf do not show BRAM or node ids in the S
CSCdj50938	Changing assign severity twice causes INTERNAL ERROR 639 on HPOV4
CSCdj52643	No HPOV format for trap 20007 sent by RtmProxy
CSCdj52856	Topod doesnt update the debug level passed thru command line
CSCdj53355	tstdelay doesnt work for local connection on ConnMgr
CSCdj54427	emd: dberr 100 and 239 when deleting a link of an IMATM port
CSCdj56246	Makefiles generated for SV+ processes do not include all the flag
CSCdj61406	UMR and UMW problems in emsc as shown by Purify
CSCdj63598	wrong stats if peak interval = bucket interval
CSCdj51831	NWTopology gives warning msg at console when listing multiple tru

Bugs Fixed in SV+ 9.0.01

The following bugs were fixed in release 9.0.01.

Bug ID Description

CSCdj57155

Process emsc may core dump if there are FTM or FTC cards in the network.

CSCdj54776

A-bit alarms seen on 1 segment voice and data conns for IPX to IGX conns only

CSCdj43801

Incorrect trktype in trktrap, incorrect contype in contrap, for swsw 8.2 release

CSCdj54722

SV+ installation script did not inform about minimum version required for WingZ

CSCdj54740

Statistics Collection Period 5 minutes should not offered in the SCM

Bug ID	Description
CSCdj57155	Process emsc may core dump if there are FTM or FTC cards in the network.
CSCdj54776	A-bit alarms seen on 1 segment voice and data conns for IPX to IGX conns only
CSCdj43801	Incorrect trktype in trktrap, incorrect contype in contrap, for swsw 8.2 release
CSCdj54722	SV+ installation script did not inform about minimum version required for WingZ
CSCdj54740	Statistics Collection Period 5 minutes should not offered in the SCM

Cisco Connection Online

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:

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 connection rates up to 28.8 kbps.

For a copy of CCO's Frequently Asked Questions (FAQ), contact cco-help@cisco.com. For additional information, contact cco-team@cisco.com.

Note 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 cs-rep@cisco.com.

Documentation CD-ROM

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.

Table of Contents

Release Notes for Cisco StrataView Plus 9.0.05 Solaris