9.0.04 Version Software Release Notes
Cisco StrataView Plus for Solaris

Enter "1"

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

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

Export the Current Database

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

1. Stop SV+ core processes

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

3. As user informix, do "dbexport -o /user/users/svplus/dbdump stratacom". Hint: In order to find out disk space requirements, use command "tbstat -d" and ensure that at least that much disk space is available.

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.

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

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:

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

Sun Platform Requirements

Three types of machines are supported for StrataView Plus 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 Type	Machine Type	Number of CPU	Size of RAM	Graphic Card Type	Hard Disk Drive	Size of Swap Space
Low End	Sun Ultra 1 Model 170E or Sparc 20 Model 151	1	256 MBytes	24 bits	Two 2 GByte drives	300 MBytes
Mid Range option 1	Sun Ultra 2 with 300 MHz and 1MB cache	1	512 MBytes	24 bits	Two 4 GByte drives	1 GByte
Mid Range option 2	Same as above	2	1 GByte	24 bits	Two 4 GByte drives	2 GByte
High End	Sun Enterprise 4000	at least 4	1 GByte	24 bits	Two 4 GByte drives and disk array	2 GByte

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. Table 2 lists recommended SV+ platforms based on the size of network.

Platform Type	Machine Type	Number of SV+ Desktops (n)	Number of Connections (m)
Low End	Sun Ultra 1 Model 170E or Sparc 20 Model 151	n < 5	m < 5,000
Mid Range option 1	Sun Ultra 2 with 300 MHz and 1MB cache	5 =< n < 10	5,000 =< m < 25,000
Mid Range option 2	Same as above	5 =< n < 10	25,000 =< m < 100,000
High End	Sun Enterprise 4000	n >= 10	m >= 100,000

Following are additional notes for SV+ platform requirements:

• For every additional SV+ desktop, there is a need for additional 8 Mbytes of RAM beyond the standard platform configuration.

• Users 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 MBytes. However, it is highly recommended to size the disk space needed for the statistics collection process.

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, please refer to "HP OpenView Network Node Manager Products, Installation Guide" (part # J1172-90001 from HP).

Notes and Cautions

Installation:

The user needs to make sure at least 750 MBytes of disk space in /usr/users/svplus area can be allocated for SV+ 9.0 installation. In the case of upgrade, disk space used by existing SV+ software plus free disk space should exceed 750 MBytes.

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

Install WingZ software from the WingZ tape or CD. Note that WingZ version 2.5 should be installed for SV+ release 9.0. Contact WingZ for a runtime license and blend it with SV+ 9.0. Failing to do so will result in following error messages when the user clicks 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 the user is installing OpenView 4.x over an existing version make sure that the /etc/snmpd and /etc/snmpd.conf are removed or renamed before carrying out the upgrade. It is likely that the user will see the following message when trying to restart OV:

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

These files are not removed by the ovremove program.

SV+ Upgrade:

The SV+ upgrade is not supported across different platforms, for example the upgrade from a AIX-based SV+ release can't be upgraded to a Solaris based SV+ release or vice versa.

SV+ Database:

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

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 it contains FastPAD connections, or if it has slave lcons with no connections.

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 the correct network ip address use cnfnwip command on the switch.

Each IPX/BPX/IGX/MGX 8220 node to be managed by StrataView Plus must be configured with an 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 StrataView Plus.

Service Agents:

For adding a connection the connectionIndex must be 0(i.e., 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.1 or 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 midpoint.

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, the user 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 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 the user starts 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.

The user 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 a user performs a create_db operation, the statshistory.stats file must be manually deleted.

Prior to SWSW Release 8.1, the user is able to specify any time period for a peak interval from SV+. In SWSW 8.4 and above, the following rules are used when the user configures peak interval through SV+. Violating the rule will cause TFTP error 22 displayed in the SCM.

• The peak interval cannot be zero.

• The peak interval must be a multiple of the polling interval

• The peak interval must be a factor of the polling interval

• 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. Users 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.

Platform:

SV+ must not be started from the OpenWindow's 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 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 is not to 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.

Software/Firmware Image Download:

Always use the SV+ ImageDownload program to do a SW/FW download. Since SV+ does not make any assumptions on the filename, it requires the user to tell the SW the filename and the path to download, avoiding any inconsistencies resulting from the file naming assumptions made by the getfwrev and loadfwrev commands. If the SV+ ImageDownload program does not work, then there is some problem with the file transfer or the image.

Specific Features Not Supported:

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

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 reorganized.

StrataView SNMP Agent 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 user is 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.

Third Party Product Limitations Notes

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

Compatibility Notes

StrataView Plus 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.0x (CESM4, FRSM4, AUSM4, BNM T3/E3, BNM 155, SRM T1/E1, SRM 3T3, IMATM, FRSM8, AUSM8, and FRSM-HS1) for all supported features.

StrataView Plus 9.0 will be backward compatible with AXIS Release 3. In the case of IMATM, StrataView Plus 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 StrataView Plus.

Although the StrataView Plus 9.0 Equipment Manager shelf view displays AUSM Release 2 cards, the user needs to enable the line and ports from the AUSM Command Line Interface. The Equipment Manager line configuration window and port configuration windows will not be fully functional for AUSM Release 2 cards.

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

StrataView Plus 9.0 does not support the BERT feature of AXIS/SRM Release 4. The user has to use the SRM Command Line Interface to configure the BERT functions.

Known Anomalies

The following is the list of known anomalies in this Cisco StrataView Plus software release.

Bug ID	Descriptions
CSCdk02115	Roll down CSCdj92497, no data continuity for 1 segment data connection. When user uses 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. User needs to 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 switches 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 the 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.04 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.

Corrected Anomalies from the 9.0.03 Cisco StrataView Plus Software Release

The following conditions have been corrected with the 9.0.04 version of the software release.

.

Bug ID	Descriptions
CSCdj59952	When using the MIB browser in HP OpenView for BPX node in the StrataView map, the nodename is has the added suffix "-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. User has to select the core shelf for the bpx node in the feeder level map to launch Mib Browser. For IPX, IGX and AXIS, user can select the respective node and launch Mib Browser. The name/ip address displayed in the MIB Browser will be correct. As a workaround 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 workaround 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 workaround 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 reestablished. 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 switchcc 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, user 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.
CSCdk30572	When a VPC is created thru ConnProxy it fails with error message "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.
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 beginning with emsd under the line which begins with cmgrd. Also, move the line beginning with statsparser under the line which begins with databroker. 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.
CSCdk04250	Port cac over ride mib checks for incorrect release number
Symptom	Cannot set BPX ATM port for CAC override.
Workaround	None
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.
Symptom	This problem seem to show up in multiple-network or large network environment.
Workaround	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.
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.
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.

Corrected Anomalies from the 9.0.02 Cisco StrataView Plus Software Release

The following conditions have been corrected with the 9.0.03 version of the software release.

Bug ID	Descriptions
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. When a connection is in selected state in the main window, and an event(DBKR_ALARM_EVENT) comes for that connection, user will get the above error message if an attempt is made to modify that connection. Wait for a few seconds and try to modify again.
Symptom
Workaround
CSCdj87117 Symptom Workaround	Make pkgchk work for 9.0.03 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 inadvertently in the file audit process. None

Corrected Anomalies from the 9.0.01 Cisco StrataView Plus Software Release

The following conditions have been corrected with the 9.0.02 version of the software release.

Bug ID	Description
CSCdj35673	IGX feeder not seen by cmgr nor NWTopology after being deleted and re-added
CSCdj63233	Wingz: Save/Retrieve template does not work
CSCdj65482	SV+ 9.0 Wingz2.5 Wingz will not launch from GUI
CSCdj65804	/usr/users/svplus/config/svplus.conf has wrong ownership, SV+ will not s
CSCdj65837	Problems when running Wingz, multiple error messages
CSCdj27687	Baseline: WingZ error message loops forever
CSCdj43801	Eventd/RtmProxy: incorrect trktype in trktrap, incorrect contype in cont
CSCdj56495	SV+ 9.0 : spelling mistake in data conn error message
CSCdj63230	Wingz: cleanup some of the pop up and flashing of Config.wkz
CSCdj65404	CSCOsv pkg states that CSCO Wingz is a pre-requisite. This is incorrect
CSCdj65427	Incorrect permissions/ownerships of traceroute and top in tools directory
CSCdj69945	Voice and data channels entries will not be removed when node is deleted
CSCdj71987	(Rollup CSCdj68473 from 8.4) cannot parse stats for FRM/CVM T1 circuit line
CSCdj80628	SV+ does not show a-bit failures for 2 segment FR conns
CSCdj74473	Conn mgr shows OK data/voice connections as in OK/A-bit alarm
CSCdj62532	PortProxy does not support UFM port
CSCdj82123	Wingz does not support Add Comment feature

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
CSCdj09378	SV+ : 8.4.0B (AIX) : Unable to add foresight connection
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:	downld 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

Corrected Anomalies from the 9.0.00 Cisco StrataView Plus Software Release

The following conditions have been corrected with the 9.0.01 version of the software release.

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 be offered in the SCM

Corrected Anomalies from the 8.4.06 Cisco StrataView Plus Software Release

The following conditions have been corrected with the 8.4.06 version of the software release. In addition, all corrections applied to previous 8.4 releases are included in this release.

Bug ID	Descriptions
CSCdj01722	SV+ database counts and alarm states were not consistent between two SV+ stations. This problem was found once during stress test in the large network. However, follow up tests could not reproduce similar problems.
CSCdj01109	SV+ statsparser core dumped when reading Unix password file (/etc/passwd). This problem has been reported to Sun Microsystems for investigation. This problem was found once in SIT.
CSCdj21534	The CMGUI takes a long time (about 25 minutes) to show a large number of connections (about 7000 connections) in the connection list.
CSCdj21366	Sometimes SV+ port proxy core dumped on handling a nonexistent IPX X.21 backyard.
CSCdj17225	There is a problem of displaying correct Line trap information (501). The information in slot, idstring, status, severity fields are incorrect.
CSCdj17240	There is a problem of displaying correct Port alarm information (503). The information in status and severity fields are incorrect.
CSCdj17251	There is a problem of displaying correct Trunk trap information (502). The information in status and severity fields are incorrect.
CSCdj15683	The fc_state field is not correct in the SV+ database.
CSCdj15391	The line information is missing from EMGUI for those cards support physical port scheme.
CSCdj15564	Sometimes the remote per_util of a connection is stored as 0 in the user_connection table when it should be non zero.
CSCdj19368	There is problem of displaying correct status field information for 20k series traps.
CSCdj19371	There is problem of displaying correct status and severity fields information for 25k series traps.
CSCdj00196	The user is not able to change the frame relay signalling from Annex DNNI to no signalling through EMGUI.
CSCdj11457	The rate up (RIF) parameter of a ABR foresight connection is not calculated correctly.
CSCdj15678	The nwip_on option for savecnf command does not work with 8.4.01 IPX feeders.
CSCdj20689	Sometimes databroker restarted without sending a trap to the user.
CSCdj19360	Sometimes there is a problem of showing correct PVC status in CMGUI and EMGUI/alarm view. The CMGUI failed to show an A-bit problem.
CSCdj25970	The SNMP object svFrPortSpeed in 8.4 is not matching with 8.1 for set/get results. One uses units of kbps, the other uses 100 bps.
CSCdj19575	The trapCardType for BXM-12T3 is not supported in SV+MIB and schema.
CSCdj20902	Sometimes CMGUI does not show connections of a failed IPX port. (
CSCdj22291	Sometimes incomplete connection not showing on CMGUI. This problem is intermittent.
CSCdj08401	The SV+ Service MIB should be enhanced to support following ATM parameters: CLPHighThresh, CLPLowThresh, EFCIThresh, IBS and VCQ size.
CSCdj29021	Sometime the number of user connections between two SV+ stations managing the same network do not match. This problem observed on a 8.2.50 based network only.
CSCdj33564	Sometime the connection states for AXIS connections are showing up as "OK/Abit failed" when they are actually "FAILED/Abit failed". The line on the AXIS shelf is in alarm state.

Corrected Anomalies from the 8.4.09 Cisco StrataView Plus Software Release

All anomalies corrected between version 8.4.06 and version 8.4.09 are included in this release. Please see the Cisco StrataView Plus Software release notes for version 8.4.09.

Obtaining Service and Support

For service and support for a product purchased from a reseller, contact the reseller. Resellers offer a wide variety of Cisco service and support programs, which are described in the section "Service and Support" in the information packet that shipped with your chassis.

For service and support for a product purchased directly from Cisco, use CCO.

Cisco Connection On-line

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.

Copyright 1989-1998 © Cisco Systems Inc.