cc/td/doc/product/wanbu/9_1/nms
hometocprevnextglossaryfeedbacksearchhelp
PDF

Table of Contents

9.1.06 Version Software Release Notes
Cisco StrataView Plus for Solaris

9.1.06 Version Software Release Notes
Cisco StrataView Plus for Solaris

About These Release Notes

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, select Documentation, and click Enter the feedback form. After you complete the form, click Submit to send it to Cisco. We appreciate your comments.

About the 9.1.06 Cisco StrataView Plus for Solaris Release

The 9.1.06 Cisco StrataView Plus for Solaris software release supports the existing Cisco WAN switching products (including the Cisco IGX 8400 series and the Cisco BPX 8600 series) running the Switch software version 9.1 based release, and introduces the following features:

New Features and Enhancements in Release 9.1.06

A new saveConfig script has been provided as part of StrataView Plus distribution. This script can be used to save some of the configuration files like /usr/users/svplus/statsmgrdir/parserconfig.stats, which is overwritten during the upgrade. This script saves the files listed in /usr/users/svplus/config/files_to_be_saved file. You can edit the files_to_be_saved file to include all the files that should be saved before the upgrade.

New Features and Enhancements in Release 9.1.05

Following table has the changes to WAN device names. This document has reference to the old names only.
Old Name New Name

BPX

BPX 8600

IGX

IGX 8400

AXIS

MGX 8220


IGX 8450 chassis includes both IGX8400 and MGX8800 planes. However, SV+ 9.1.05 supports only IGX8400 cards.
Note In StrataView Topology, during initial network discovery phase, the IGX8450 icon will be shown as IGX8400 icon. In few seconds it will be shown as proper IGX8450 icon. However, if the NWIP address on IGX8450 is not configured, the transition from the IGX8400 icon to the IGX8450 icon on SV+ topology will not be done.
Cisco View has been enhanced to manage IGX8450. This release shall manage only the following cards:
The right half of the IGX8450 shelf will be shown empty.
Two sample files, CAC_calc.txt.sample, CAC_calc.txt.sample2 files are distributed along with SV+ package. These files can be found on an installed SV+ 9.1.05 system in the /usr/users/svplus/config directory.
You must copy one of the files as CAC_calc.txt into /usr/users/svplus/config directory, modify, if needed, before starting SV+ to be able to use the CAC functionality.
For VBR connections, the % utilization field will be updated automatically as the values for PCR(0+1), MCR(0+1), MBS(0+1) fields are being entered.
FOR CBR connections, the % utilization field will be updated automatically as the value for PCR(0+1) field is being updated.
Note ConnProxy does not support this feature in this release.
Link0 and link1 keep-alive interval can be configured by environment variables SV_LINK0_TIMEOUT and SV_LINK1_TIMEOUT in seconds. If these environment variables are not set, the default values are:
Variable Time (seconds) Link Number

link0 keep-alive interval

120

if number_of_link0 < 29

180

if 30 < number_of_link0 < 59

240

if 60 < number_of_link0 < 89

300

if 90 < number_of_link0

link1 keep-alive interval

300


If you use the environment variables to set their own link0/link1 keep-alive interval, the above default values will not apply.
Because of the retry mechanism in SV+, in a worst case scenario, the gap time to inform LINK_DOWN is:
keep-alive interval + (2 * number_of_retry * response_time_out)
number_of_retry by default is configured in config.sv as 6 seconds
response_time_out by default is configured in config.sv as 7 seconds
With these retry and response time out values, the maximum time taken by SV+ to report a LINK_DOWN message will be keep-alive interval + 84 seconds.

New Features and Enhancements in Release 9.1.03

Note Grouped Connections are no longer supported in switch software version 9.1. All grouped connections must be deleted prior to starting the upgrade. If these connections are desired, all grouped connections must be ungrouped using a Cisco StrataView Plus based tool called unGroup which will be available at a later date. This tool will be posted on CCO. More details on this tool are given in this release note.

Connection Manager:

The StrataView Plus Release 9.1 Connection Manager supports CESM ports, structured and unstructured connections and supports CESM 8 port cards. Until SV+ 9.0 the addressing scheme used for CESM 4 port cards was logical addressing. In SV+ 9.1 the addressing scheme has been changed to physical addressing.

The StrataView Plus Release 9.1 Connection Manager supports FRASM ports and connections.

The StrataView Plus Release 9.1 Connection Manager supports management of UXM ports and connections.

Network Limits:

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

StrataView Plus Release 9.1.06 will be able to manage different disjoint networks running switch software releases 8.2, 8.4, 8.5 or 9.1 provided all the networks elements have unique network IP addresses and unique names across all the networks managed by StrataView Plus. Different networks may run different versions of switch software as long as the releases are those listed above.

New Features Supported

This section lists the new features provided in the 9.1.06 release of StrataView Plus.

New Hardware Support

New Applications

Enhancements

Features Not Supported

Packaging Changes

SV+ Service Agent is packaged along with StrataView Plus and is not an optional feature. SNMP Agent and Proxy processes are run along with other StrataView Plus core processes. The option to run SNMP agent from the SV+ menu has been removed.

How to Get CiscoView

CiscoView is not on the SV+ 9.1 CD. CiscoView consists of CiscoView engine and device package files. CiscoView engine, device package files and required patches of CiscoView engine are on a separate CD included in SV+ bill of materials. CiscoView device package files are also available on CCO and the AXIS/BPX/IGX device files are also available on SV+ CD.

Sun Platform Requirements

Three types of machines are supported for StrataView Plus 9.1.05 as standard platforms. They are low-end, mid-range and high-end platforms. The configuration of each platform type is listed in Table 1. Other equivalent platforms running Solaris 2.5.1 are also supported.

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

Low End

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

1

256 MBytes

24 bits

Two 2 GByte drives OR one 4 GByte drive

512 MBytes

n < 5

m < 5,000

Mid Range option 1

Sun Ultra Enterprise 2 Model 2300 or Ultra 30 model 300

1

(300 MHz processor)

512 MBytes

24 bits

Two 4 GByte drives

1 GByte

5 =< n < 10

5,000 =< m < 25,000

Mid Range option 2

Sun Ultra Enterprise 2 Model 2300 or Ultra 60

2

(300 MHZ processors)

512 MBytes

24 bits

Two 4 GByte drives

1 GByte

5 =< n < 10

25,000 =< m < 50,000

Mid Range option 3

Sun Ultra Enterprise 2 Model 2300 or Ultra 60

2

(300 MHZ processors)

1 GByte

24 bits

Two 4 GByte drives

2 GByte

5 =< n < 10

50,000 =< m < 100,000

High End

Sun Enterprise 4000 or Enterprise 450

at least 4

1 GByte

24 bits

Two 4 GByte drives and disk array

2 GByte

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

The following are additional notes regarding SV+ platform requirements:

Note If Low End SV+ system is used for mid-size or large networks, the following problems may be observed.

Required Configuration for Stand-alone SCM

Three types of machines are supported for SV+ 9.1 stand-alone SCM as standard platforms. They are low-end, mid-range and high-end platforms. The configuration of each platform type is listed in table 1. Other equivalent platforms running Solaris 2.5.1 are also supported.

Platform Type Machine Type Number of CPU Size of RAM Hard Disk Drive Size of Swap Space

Low End

Sun Ultra Enterprise 1 Model 170 or Sparc 20

1

128 MB

One 2 GB drive

256 MB

Mid Range

Sun Ultra Enterprise 2 Model 2000 or Sun Ultra-30

1

256 MB

One 2 GB drive

512 MB

High End

Sun Ultra 60

2

512 MB

One 2 GB drive

1 GB

HP OpenView Requirements

The SV+ 9.1.05 release works with HP Openview Release 5.01 for Solaris 2.5.1. See "Third Party Product Limitations Notes" for HP OpenView patches required by SV+.

The default color of the background map can make it difficult to see the color of the nodes and the trunks on the map. To change the color of the background map, see See "Default Color of Background Map"

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

Notes and Cautions

Installation:

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

If you have installed SV+ 9.1.00, remove the Informix package from your system and reinstall Informix package from 9.1.05 CD. Make sure Informix processes are not running before removing the informix package. To remove the existing informix package, execute the command as a root user:

# pkgrm CSCOinf

You do not have to remove the Informix package if you had installed Informix from 9.1.01 or later CD.

If you plan to use auto install and intend to partition the disk during auto install you have two choices for installing Wingz:

    1. Install Wingz in /opt/Wingz before installing SV+ and then execute IntegrateWingz.

    2. Install Wingz in /usr/users/Wingz after installing SV+ and then execute IntegrateWingz.

Note Several Wingz configuration files were omitted from the 9.1.05 SV+ for Solaris CD. These files are available in SV_Rel91.05Solaris.Patch3.

If you do not plan to partition the disk during auto install or if you are using manual install you have two choices for installing Wingz:

    1. Install Wingz either in /usr/users/Wingz or /opt/Wingz before installing SV+.

    2. Install Wingz either in /usr/users/Wingz or /opt/Wingz after installing SV+ and run IntegrateWingz.

Install Wingz software from the Wingz tape or CD. Note that WingZ version 2.5 should be installed for SV+ release 9.1.05. After installing, contact Wingz for a runtime license and blend it with SV+ 9.1.05. Failing to do so will result in following error message when clicking on the SV+ Report icon: "There is a problem with the registration information for this machine. Contact your system administrator".

If 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, the following error message will appear in the console, "Shared memory is not initialized".

If you are installing HP/OV 5.01 over an existing version make sure that the /etc/snmpd and /etc/snmpd.conf files are removed or re-named before carrying out the upgrade. If these files are not removed or renamed, 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 OV. These files are not removed by the ovremove program.

SV+ Upgrade:

The SV+ upgrade is not supported across different platforms. For example, an AIX-based SV+ release can't be upgraded to a Solaris-based SV+ release or vice versa. Upgrades from SV+ 9.1.00, 9.1.01, and 9.1.02 are not supported in StrataView Plus 9.1.06. Upgrades from SV+ 8.2, 8.4, 9.0 to SV+ 9.1 upgrade are supported.

SV+ Database:

After performing the creation of 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 above purpose.

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

atmEndptPCR <-- PCR(0+1)
atmEndptSCR <-- SCR(0+1)
atmEndptMCR <-- MCR
atmEndptQIR <-- IC
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
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.
Cell/second SV+
100 bit/second 		Switch
100 bit/second

5760

22119

22118

3259

12515

12514

2834

10883

10882



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.
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. To configure the correct network IP address use the 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.

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(i.e., there is no need to do a GET on connAvailIndex). The actual index is internally generated by the connection service agent itself.

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 Cisco 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, 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 an "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.

Switch software supports only ATFR and ATFST type of connections for UXM on a feeder node. SV+ does not support ATFR or ATFST for ATM to ATM connection (on Connection manager GUI select Configure->New ATM-TM connection->VBR.3) the connection type on switch CLI will show as ATFR for all 3 segments. If you select ABR.FS connection type for ATM to ATM connection (on connection manager GUI select Configure->New ATM-ATM connection->ABR.FS) the connection type on CLI will be ATFST for all 3 segments. For all other limitations of connection type supported for UXM on feeder node please refer to the switch software release notes for release 9.1.

ATM-FR connections with FR endpoint on IGX/IPX running 8.4.x switch software can not be set with channel type SIW (Service InterWorking) transparent or SIW translate. This feature is not supported by IGX/IPX running 8.4.X SWSW. The connections thus set using 9.1 Connection Manager would fail.

The default values provided by the Connection Manager GUI for the Frame Relay end point parameters Ingress/Egress ECN Threshold and DE Threshold are not the same as those provided by the connection service agent.

The Connection Manager GUI uses percentage notation for both the ECN Threshold and DE Threshold. However, the service agent MIB uses the absolute value for those MIB variables. If the defaults were used for GUI and service agent, following values would be setup for the PVC:

Parameter GUI Default Values Service Agent

Ingress ECN Threshold

10% of Ingress VC Q Depth -> 6554

6553

Ingress DE Threshold

50% of Ingress VC Q Depth -> 32768

32767

Egress ECN Threshold

10% of Egress VC Q Depth -> 6554

6553

Egress DE Threshold

50% of EGress VC Q Depth -> 32768

32767

Note The defaults for both Ingress and Egress VC Queue Depth are 65535 bytes.

The switch generates the following error message 

Failure validating remote endpoint description

when the PVC was modified or deleted using SV+. The problem occurs when SV+ is managing a mix release network and the node mastering the PVC has an older release than the remote end, and the remote end point is in a newer card which was introduced after the older release. This is switch software limitation. The PVC can be deleted using the switch CLI.

Connection manager doesn't check for the SVC VPI/VCI partitioning range, if VPI value is ZERO and if SVC Hi VPI and Low VPI are set to ZERO on the switch. Because of this, VPI 0 can be used for provisioning. However, if you only reserve 0 for SVC range, Connection Manager will not block the PVC provisioning.

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

In SWSW 8.5, the following rules are used when you configure peak interval through SV+. Violating these rules will cause TFTP error 22 displayed in the SCM.

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 lose 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 OpenWindows command tool Window. If SV+ is started from command tool, the command tool may freeze the screen when command tool window's log buffer fills.

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.

SV+ must not be started from CDE environment.

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.

If a blue trace is left behind on dragging a node on Network Topology, stop SV+ core processes and restart motif window manager or if possible reboot the system. Restart SV+ and check if blue trace is still left behind on dragging a node on network topology. If the problem does not go away by restarting motif window manager or rebooting the system there could be problem in the graphics card on the system. Stop SV+ core processes and edit /usr/users/svplus/.cshrc file and include the following statement in it:

setenv NWTOPOLOGY_LABEL_SHADOW off

Execute the command: source /usr/users/svplus/.cshrc

Restart SV+ core processes.

This will disable the feature to draw the label as the node icon is being dragged on network topology map. For more detail please refer to bug # CSCdj86512.

Map Status Displays

Both NWTopology and SvOvTopology maps display the status of a routing node or a 3810 cluster node using the concept of compound status where the compounding is done by propagating the most critical status. The routing node icon on a map displays the color representing the worst case status of either the routing node or any of the feeder shelves connected to the routing node. The 3810 cluster icon similarly shows a color representing the worst case status of either the parent IGX node or any of the 3810 connected to the IGX node. The actual status of each node is displayed on the submap brought up by double-clicking on either the routing node icon or the 3810 cluster icon. The SvOvTopology map uses the different mechanism of compounding the node status by default. To display the correct node status on the SvOvTopology (also to be consistent with NWTopology map) the correct compound status propagation mechanism needs to be set. To do this, first bring up the "Map Description" dialog by clicking on Map->Maps->Describe/Modify command. Next, choose the "Propagate Most Critical" item from the selections under the "Compound Status:" label. Finally, select the "OK" button on the dialog. This setup will be saved in the HPOV database when exiting the SvOvTopology map and no further action is required until the HPOV database is cleaned up at which time this configuration must be performed again. There is no API provided by HPOV to do this configuration from the SvOvTopology application.

Default Color of Background Map

The default color of the background map can make it hard to see the color of the nodes and trunks on the map. At times it may be convenient to turn off the background map and have a solid grey background. To do this, first bring up the "Submap Description" window by clicking on the Map->Submap->Describe/Modify command. Now, delete the text from under the "Background Graphics" label and click on the "OK" button. This will replace the background map with a solid grey background. To replace the background map with another map, click on the "Browse" button in the "Submap Description" dialog mentioned above. This brings up a file selection dialog called the "Background Graphics" with a list of available GIF files. Select a GIF file and click on "OK" first in the "Background Graphics" dialog followed by in the "Submap Description" dialog. This will replace the background map. The background map selection will be in effect as long as the HPOV database is not cleared at which point the selection need to made again.

If the nodes are grouped in the topology, a double click on that group shows only the list of nodes in that group. It doesn't give access to any of those nodes. The list doesn't show the status of the node(s) also.

Network Browser

Network Browser will not come up if the color allocation fails during it's start-up, due to other active color intensive applications, like Netscape browser. However, NWBrowser process will be running in the background. So next time when you try to bring up network browser, it will not come up, since already on instance is running.

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 you 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:

Voice connection G729 and G729A are not supported from Connection Manager and Service Agent.

Multicast, voice and data connections are not supported though Service Agent.

There is no support for Equipment manager GUI for Axis 4.1. Cisco View is used for equipment management of Axis 4.1.

StrataView SNMP Agent Notes

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.

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.

The following patches are required for HPOV: PSOV_01688 and PSOV_01863. These patches are supplied on the SV+ 9.1.05 CD. If HP OpenView is installed on the system these patches are installed during SV+ installation.

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

Interface Changes

The following changes were made in SV+ Service MIB in SV+ 9.1.06.

ASI
T3 : 10-96000
E3 : 10-80000
OC3 : 10-353208
BXM
T3 : 50-96000
E3 : 50-80000
OC3 : 50-353208
OC12: 50-1412832
ASI
T3 : 0-96000
E3 : 0-80000
OC3 : 0-353208
BXM/BME/UXM
T3 : 6-96000
E3 : 6-80000
OC3 : 6-353208
OC12: 6-1412832
ASI
T3 : 10-96000
E3 : 10-80000
OC3 : 10-353208
BXM/BME/UXM
T3 : 50-96000
E3 : 50-80000
OC3 : 50-353208
OC12: 50-1412832

The following changes were made in axis.mib in SV+ 9.1.05 (changes from axis.mib release 4.1.00 to 4.1.02).

Compatibility Notes

Anomalies in the 9.1.06 Release of StrataView Plus

This section describes known anomalies in the 9.1.06 version of StrataView Plus.

Known Anomalies

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

Bug ID Descriptions

CSCdk21071

You cannot add Link station with port proxy for FRASM firmware version 4.1.00af. There is no problem with FRASM firmware version 4.1.00aa. The following error message is returned if you add link station using port proxy: "Wrong OID or problem with Varbind". The workaround is to use CLI to add the link station.

CSCdk35905

Intermittently cannot move node icons in SV+ topology map. As a work-around to this user can stop SV+ processes, exit the graphic environment (Open Windows/CDE), restart the window manager and restart SV+.,

CSCdk72506

SV+ Topology sometimes shows grey text on grey background (state of the node). This is difficult to read.

CSCdk82083

Loop timing on CESM lines on AXIS shelf can't be configured using Equipment Manager GUI.

CSCdk81857

Many SV+ core processes disappear unexpectedly. When trying to bring up desktop, SV+ reports errors like:

Error: ilblmap[620756995,1]@anouken not registered.

Error: Failed to request logical mapper

Desktop: NWTopology Program Aborted, Exiting

The problem is only seen when statsmain (SCM) is used along with SV+. When SCM is terminated, occasionally, the problem shows up.

As a work-around to this problem SV+ can be restarted.

Further problem description: SCM and SV+ share the same watchdog.conf for automatic restart of processes by watchdog. When SCM terminates, the watchdog.conf entry is first modified in /tmp and then moved back to /usr/users/svplus/config directory. The Unix command 'mv' on Solaris removes the target file first and then copy over the source file, when source and target files are on different file systems.

Problems may occur in a very small time window when the target watchdog.conf is removed, and yet to be copied in. SV+ process watchdog may be in the process of reading the watchdog.conf file. The non-existence of watchdog.conf leads to killing of all existing SV+ processes.

The ilblmap process is the first process to be removed. Once it is killed by watchdog, subsequent desktop startup fails.

CSCdk83208

Network Browser intermittently shows nodes in sync state, though some of the cards in those node are marked as out of sync in SV+ Database card table.

CSCdk84287

SV+ Topology doesn't update the node status when the nodes become unreachable.

CSCdk88933

SV+ Topology beeps when you double-click on grouped icon or grouped trunk icon. This happens only when the NUMLOCK or CAPLOCK is set on the SV+ station's keyboard.

CSCdk89004

PVC addition using Connection Proxy agent between CESM 8T1 to CESM 8T1 cards fails with the error "Parameter modification for add channel failed".

CSCdk89368

StrataView may intermittently loose Link 0/Link 1 access to all the switches in the network. This was observed on one occasion in a very large network environment after a network outage due to user error.

CSCdk89647

SV+ installation fails if there are multiple entries in /etc/hosts file with the same host name, even though they are commented.

CSCdk90417

Stats Collection Manager cannot collect statistics for ASI connections on BXM card.

CSCdk90900

The UXM card on an IGX goes into alarm and resets if the connection was added using switch CLI and then modified using the Connection Manager GUI.

The work-around is to add connection using the Connection Manager GUI and modify it using the switch CLI.

Anomalies Corrected with the SV+ 9.1.06 Release

The following anomalies have been corrected with the 9.1.06 version of StrataView Plus.

Year 2000-Related Anomalies Fixed in SV+ 9.1.06

Bug ID Descriptions

CSCdk89132

In SV+ New Reports, 2/29/99 (DD/MM/YY) is accepted as a valid date in Performance Data window. This is an error because 1999 is not a leap year.

Other Anomalies Fixed in SV+ 9.1.06

Bug ID Descriptions

CSCdj68372

Stat types "Packets Received" and "Receive Packets Discarded" are missing in Data Connection section of Statistics Collection Manager. These statistic types have been added Statistics Collection Manager and the reports tool.

CSCdj81530:

Connection Proxy and Connection Management GUI can't setup ATM connections if the VPI value given is in the range of 256-4096 for connections involving BXM/ASI NNI port. It has been fixed to take the values for atmEndPointVpi in the range of 0 to 4095 for BXM/ASI NNI port. For UNI port the range is 0-255 .For AUSM NNI VPI range is 0-255.

CSCdk02155

Information traps are not handled properly by SV+. SV+Network.mib (to include info enum value) and emsc proccess have been updated to fix this problem.

CSCdk02834

Frame Forward and FUNI enum are missing from SV+ Service MIB for frEndPointchanType MIB object.

Enumerations frFUNI(4), frForward(5) have been added to this MIB variable.

Defaults for this attribute:

FUNI ports : frFUNI

FF ports : frForward

Other : frNIW

frFUNI is applicable for FUNI ports only.

frForward is applicable for FrameForwarding ports only.

CSCdk04116

Database inconsistency between two SV+ stations managing same network, after the cold start (after creating SV+ DB) has been fixed in SV+CreateDB process.

CSCdk12929

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

CSCdk23119

The default value shown for chanType in Connection Manager GUI is SIW for ATM-FR new connection window. But SIW is not supported for FR cards on switch feeders IPX/IGX. This problem has been fixed in Connection Manager GUI process.

CSCdk25132

SV+ install fails if the target disk/slice has more than one digit. That is, if the disk that the raw-partition is being installed on has tNN, where NN is the target, the install script will fail as in the following example: /dev/dsk/c0t15d0s5. This problem has been fixed in SV+ INSTALL process.

CSCdk34622

Values for the column protocol_type in SV+ database table - frp for certain rows, do not match with the enumerations specified in the SV+ Database Interface Manual. This happens for protocol types - 'none' & 'LMI with Async Updates. This has been fixed by update SV+ Database Interface Manual.'

CSCdk58273

PCR(0+1) value for a connection on BXM card can not be set to more then 353208 using ConnProxy process. This problem has been fixed in ConnProxy and Connection Manager GUI processes. SV+ service MIB has also been updated

CSCdk60151

StrataView looses registration with AXIS shelves. This happened because of increase of keep-alive timeout in rtm process, by passing `-k 6000' arguments to rtm from /usr/users/svplus/config/watchdog.conf file. To fix this watchdog.conf file has been updated to not to pass `-k 6000' arguments to rtm process.

CSCdk60249

An unexpected exit problem in Connection Manager GUI has been fixed. This happens when `.' (dot) is entered as port number in Port # field and when Apply button is pressed. Fix has been put in to flag an error message if there is any illegal character entered in this field.

CSCdk62018

SV+ INSTALL, while installing CiscoView files, displays the error "ERROR: file /usr/users/svplus/wancv/BPX.pkg not found. Exiting". This problem has been fixed in SV+ INSTALL process.

CSCdk63006

Connection Manager GUI, shows incomplete info for data connections. This happens if there are connections with channel number 255 (the permissible range is 2 to 32 ) in the database. If a connection with channel number 255 is added Connection Manager GUI complains that it is out of range, but continues to add the connection. This problem has been fixed in Connection Manager GUI process.

CSCdk63619

A DataBase inconsistency problem has been fixed in emd and emc processes. This happens when a node gets deleted (reachability) and re-added, and if the management of that node is given to a different emc process than the one previously managing it. In this situation there was a race condition where the previous emc process would be deleting the objects of this node, while the new emc process is getting the objects from the node and updating the database.

CSCdk63784

SV+ INSTALL displays the disk size in number of sectors, instead of bytes as part of the error message, when there is not sufficient disk space on the selected partition to install as INFORMIX database partition.

CSCdk64179

RTM process abnormally exits if user specifies Log level 5 in /usr/users/svplus/watchdog.conf file. This does not have any implication for user as log level 5 is not enabled by default. The regular logging level is 2. Higher logging is only required for getting debugging information during development or when there is some problem reported. There is not problem if Log level 4 is enabled for RTM.

CSCdk65319

SV+ Network Browser doesn't come up if color map allocation fails during its startup. This problem has been fixed in NWBrowser process.

CSCdk66461

Whenever Connection Manager GUI is invoked SV+ Admin window shows "/usr/users/svplus/config/insd.conf open failure" error. The problem has been fixed in Connection Manager GUI Process.

CSCdk67145

SV+ Stats Manager will skip sending request to tftp GET the stats file for some nodes in a random pattern, hence missing stats in the database. This problem has been fixed in statsmain process.

CSCdk67623

SV+ doesn't get registered with AXIS shelves for a long time. If the first attempt to get registered with the axis fails due to axis agent timeout or other SNMP error and the short timeout (in seconds) command line option (-s) is set to a high value for rtm process in /usr/users/svplus/config/watchdog.conf file.

Further Problem Description: This problem is fixed by decoupling the use of the short timeout value in the error retry delay scenario. Now, the short timeout value is used only for timeout getting response from snmpcomm. This short timeout can be set to a higher value to avoid too many repeated requests sent to snmpcomm while its busy and end up flooding its message queue. A new command line option "-d" is introduced to set the error retry delay time in seconds. This error retry delay time is used if response is received from snmpcomm but the request was failed. In this case, rtm will retry (resend the request) after the error retry delay time. The default for this retry delay is 60s if its not set.

CSCdk67623

INSTALL takes long time. This problem has been fixed in INSTALL script. INSTALL used to take a long time because it used to uninstall CiscoView packages and then reinstall them again irrespective of whether the workstation requires the packages or not. Now the INSTALL script accepts the user input and if the user needs to install packages it does so, otherwise it skips the installation of the CiscoView package files.

CSCdk70434

Test delay feature from SV+ Connection Manager GUII doesn't function, if the SNMP community strings in /usr/users/svplus/config/svplus.conf files are changed from the default public for GET community and private for SET community before Connection Manager GUI startup.

CSCdk73834

Configuration Restore to BPX/IGX/IPX does not use block size specified in the /usr/users/svplus/config.sv file. As a result of this, the configuration restore process doesn't show any performance improvement, even after increasing the block size in /usr/users/svplus/config.sv file.This problem has been fixed in configd process.

CSCdk75148

StrataView Plus doesn't receive some of the traps intermittently. This problem has been observed with port delete trap. This problem has been fixed in rtm process.

Further problem description: The problem is that rtm process resets KeepAlive Timer (of the src agent) every time when it receives a trap from that agent. If the KeepAlive timer does not get expired, no KeepAlive (SNMPGET ManagerRowStatus) will be sent. So, in a scenario where traps are received continuously from agent by rtm, rtm will delay sending the KeepAlive every time it receives a trap. After 30 minutes of continous trap reception, the agent will then deregister the trapmgr entry since no KeepAlive is received from SV+.

CSCdk75845

SV+ SNMP Proxy agent doesn't filter some of the traps like 50600, 50800, 50018, 50500, 50501, 50502, 50021, 50020, 50131, 50303, 25000, 25001, 25002. This trap filter list is installed in /usr/users/svplus directory as rtmIgnoreTraps file. This problem happened because rtmIgnoreTraps file was not included in SV+ distribution.

CSCdk76234

The existing SV+ configuration files are lost during StrataView Plus upgrade. StrataView Plus INSTALL process has been enhanced to restore user configuration files from previously saved set. User can follow the following procedure:

The files the user wants to save are to be listed in /usr/users/svplus/config/files_to_be_saved with their full path. For example, if /usr/users/svplus/config.sv has to be saved then the user has to add this entire path in the files_to_be_saved file. The names should be one per line. Care should be taken to ensure that the file files_to_be_saved always contains the entry /usr/users/svplus/config/files_to_be_saved

Stop SV+ processes.

Run /usr/users/svplus/install/saveConfig. This will save all the files which are listed in /usr/users/svplus/config/files_to_be_saved in /tmp/.saved.sv.

SV+ installation process has been upgraded to restore config files from this saved set.

CSCdk78372

RtmProxy process is not configured with large timeout value in /usr/users/svplus/config/watchdog.conf file. Because of this any trap manager that is registered with RtmProxy process times out frequently. RtmProxy line /usr/users/svplus/config/watchdog.conf file has been updated to:

RtmProxy on . RtmProxy -k 2147483647

CSCdk78908

socketd process exits in an unexpected manner, if CDE server in whose environment SV+ processes are running, exits abnormally. This problem has been fixed in socketd process.

When the CDE session exit, all process with the TTY associated gets SIGHUP signal. socketd does not have handler for this signal that why it exit. When it exit, it does not kill other processes.

CSCdk84211

SV+ Service MIB has incorrect range and description for atmEndPointVpi MIB object if the ATM end point is on a NNI port. For UNI port, VPI range is 0-255. For NNI port, VPI range is 0-4095.

CSCdk86036

Error "Cmgr: nodeName: 0129/99 11:10:38 from Mgr xx.xx.xx.xx :: SET AtmEndptTable Row 1001343 (MODIFY) Local SCR must not exceed PCR(0+1) (10) Agent:Nodename(xx.xx.xx.xx):Agent reported General Error." is return when adding or modifying ATM-ATM/ATM-FR 2-segment or 3-segment connection.

This problem occur only when there is a BXM card on the routing segment of the connection and CIR is set to < 19.2k or SCR and PCR are set to < 50.

As a fix to this problem cmgrd process has been enhanced to round up the SCR and PCR parameter to 50 for the routing segment if you are adding or modifying the end segment CIR to < 19.2k or SCR < 50. In a 3-segment connection case, the end segments will have the user configured value for CIR or SCR while the middle segment will have SCR=50 and PCR = 50.

CSCdk88603

SV+ service agent doesn't check whether ATM port type is UNI or NNI for VPI range. The ConnProxy process has been fixed the following ranges. For AUSM card: vpi range is 0-255 for UNI & NNI. For ASI/BXM/UXM: vpi range is 0-255 for UNI and 0-4095 for NNI.

CSCdk89167

SV+ ConnProxy reports that CIR,MIR must be greater than or equal to 19200 on remote FR end, if local end is UXM/BXM, while provisioning ATM-FR connections. This problem has been fixed in ConnProxy process. For FRP, FRM, UFM (FR cards on switches) the restriction on CIR, MIR is that both must be greater than or equal to 19,200. This condition is not valid for FRSM cards in AXIS shelves.

CSCdk90547

The display of SV+ GUIs like Connection Manager, Stats Collection Manager, malfunction in CDE environment.

For CDE support a file called ConnMgr in /usr/users/svplus/app-defaults has been added to SV+ distribution, which specifies the font that should be used when the application is started in CDE. The INSTALL process of SV+ makes a soft link to the above file in /usr/lib/X11/app-defaults directory so that the font details for SV+ Connection Manager GUI are known to CDE.

The window sizes for the SV+ GUI processes like Connection Manager, Stats Collection Manager have been modified, as CDE in some cases need a bigger window size to accommodate all the window components.

The font sizes in other related applications have also been modified wherever needed.

CSCdk91581

In a large network (having several hundred nodes), the redundant state changes (redundant messages between SV+ processes) could potentially cause a deadlock between SV+ processes.

Corrected Anomalies Rolled Up From the SV+ 9.0 Release

The following anomalies of the 9.0 release of StrataView Plus have been corrected and rolled into the 9.1.06 release of StrataView Plus.

Bug ID Descriptions

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.

Corrected Anomalies Rolled Up From the SV+ 8.4 Release

The following anomalies of the 8.4 release of StrataView Plus have been corrected and rolled into the 9.1.06 release of StrataView Plus.

Bug ID Descriptions

CSCdj59952

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

In release SV+ 8.4.10 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 nameand 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.

CSCdk11108

SV+ SNMP proxy returns no variable found, when a query is made on MIB variable svMapLogicalPort for non-channelize frsm-8 card. This problem has been fixed in PortProxy process.

CSCdk36749

Equipment Manager GUI shows 'wrong value' error message when a port is added on FRSM-HS1 with X.21 back card. This problem has been fixed in Equipment Manager GUI process. This problem can occur in the following scenario

  • Add a new port on FRSM-HS1/X.21 card with CLLM disabled and LMI signalling protocol set to Annex ANNI.

  • Make sure that the newly added port has "Rcv Status Timer" value other than 1000.

  • Add another new line and new port on that line with signalling enabled and CLLM disabled. Equipment Manager GUI shows 'wrong value' error message now.

CSCdk50180

Equipment Manager GUI, displays "Port configured does not match the current filter" error message, after a port is successfully added. This has been observed when a port is added on FRSM-HS1 card.

CSCdk65341

Equipment Manager GUI, displays "DS0 BitMap is Wrong for E1" error message, when an attempt to up a E1 port on FRSM card with CAS signalling is made.

CSCdk67023

.SV+ does not get registered to the AXIS nodes for a long time. This problem happens if the first attempt to register to the AXIS fails due to AXIS agent time-out or other SNMP error and the short time-out (in seconds) given by command line option (-s) to rtm process is set to a high value.

Further Problem Description: This problem is fixed by de-coupling the use of the short time-out value in the error retry delay scenario. Now, the short time-out value is used only for time-out getting response from snmpcomm. This short time-out can be set to a higher value to avoid too many repeated requests sent to snmpcomm while its busy and end up flooding its message queue. A new command line option "-d" is introduced to set the error retry delay time in seconds.This error retry delay time is used if response is received from snmpcomm but the request was failed. In this case, rtm will retry (resend the request) after the error retry delay time. The default for this retry delay is 60s if its not set.

Anomalies Corrected with the SV+ 9.1.05 Release

The following anomalies have been corrected with the 9.1.05 version of StrataView Plus.

Bug ID Descriptions

CSCdj77506

The currentRoute of a PVC is shown as NULL after test delay operation is done using SV+ SNMP agent. This problem has been fixed in ConnProxy process.

CSCdj88008

The following non-interval IGX statistics for the UXM have been removed from statsenablelist.stats file.

ASI Connection 0 7 300

Average Cell Rx Q Depth 2 51 91

Average Cell Tx Q Depth 2 59 91

Egress VSVD Allowed Cell Rate 2 58 91

Ingress VSVD Allowed Cell Rate 2 57 91

ASI Port 3 1 300

Last known VPI/VCI 2 37 91

CSCdj92150

An unexpected exit problem in SvOvTopology process, while adding a DAS station has been fixed. For this one has to apply HPOV Patch PSOV_02091. This is now being shipped with SV+ 9.1.05 media.

CSCdk04921

Local DLCI field in DB gets populated with -1 values for voice and data connections. This has been fixed in emsc process. l_dlci is not applicable to voice and data connections. Now the new value being set is 1.

CSCdk04123

Error window in SCM has been made scrollable.

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

CSCdk21838

Communication break alarms 20016 and 20017 are not getting generated, instead 20006 and 20007 get generated. The trap numbers were changed in 9.1, the correct trap numbers are 20016 and 20017.

CSCdk24081

If axis is in minor alarm and for any reason a feeder alarm for that axis is generated, there is no corresponding clear feeder alarm getting generated when the feeder alarm is cleared. This bug has been fixed in emsc process.

CSCdk32996

A database inconsistency issue, where ipx_netw_id field in network table is always populated as -1, has been fixed in topod process.

CSCdk35335

SV+ SNMP Agent gets the VSVD as disabled even if VSVD is enabled on a connection. This problem has been fixed in ConnProxy process.

CSCdk37713

SV+ install overrides root users PATH environment variable. This has been fixed in SV+ install procedure.

CSCdk37805

When EMGUI is iconified and EM desktop button is pressed EMGUI does not de-iconified. This problem has been fixed in Equipment Manager GUI process.

CSCdk38099

The switch generated error messages shown on the CM GUI result window sometimes are vague to indicate the true problem.

This occurs when SV+ release 9.1 is used to provision pre 8.5 IPX/IGX frame relay PVC with channel type option as SIW-Translate or SIW-Transparent.

The SIW-Translate and SIW-Transparent channel types are not supported by the IPX/IGX switch until 8.5 release. This is a switch limitation which prohibits the creation of such PVC. No true workaround exists for pre 8.5 switch software. If SIW-Translate or SIW-Transparent feature is needed, upgrading switch software is the only solution.

The enhancement implemented on the SV+ side is to generate a more user friendly message to point out the feature is not supported by the switch running pre 8.5 switch software.

CSCdk38581

SV+ system log shows error message, even the peak value given in SCM wholly divides the collection interval and bucket interval. This has been fixed in statsmain process.

CSCdk39653

A DB inconsistency issue related to voice and data connection in user_connection and connection tables has been fixed. This problem has been fixed in emsc process. Because of this problem, when voice and data connection are added, DB doesn't get properly updated.

CSCdk42137

SV+ Service Agent will fail on adding a new CESM port that spans time slot 16, if the line is configured for CAS. This happens only when a port is added on CESM E1 card, when line is configured for CAS.

As a work-around, user can skip timeslot 17 in the bit map, while using Proxy Agent to do port creation with such configuration.

Further problem description: When adding a new CESM port that spans timeslot 16, the proxy will fail if the line is configured for CAS. This operation is successful when adding the port from the command line. On CESM, when an E1 line is in CAS or CAS_CRC mode timeslot 17 is allocated for signalling and can't be used for port creation. Using CLI to create a port spans timeslot 17, agent will automatically skip the timeslot. This can be verified by the timeslot bitmap in dspport. When using Proxy Agent to do port creation with such configuration, you have to skip timeslot 17 in the bitmap.

CSCdk42244

LMI setting won't change on FRSM-HS1 card in Equipment Manager GUI. When adding a new port on FRSM-HS1 with LMI protocol other than "No signalling", or modifying the LMI setting, Equipment Manager GUI will return back to the original setting when it prompts "Completed".

Further Problem Description:

1. When adding a port on a FRSM-HS1 card, if select protocol type other than "No signalling" in LMI parameter field, the result box will print "Wrong Value", and all setting in LMI parameter field return back to No signalling.

Go back to the port selection window and hit Apply button again shows that the port was added and the LMI parameters were set correctly.

2. When modifying a port on a FRSM-HS1 card, after apply the change the result window shows Completed but the LMI parameter field go back to "No signalling" (the default setting). Re-select the port for modification shows that the port parameters did not get changed.

CSCdk42752

A problem in topod process, where it doesn't populate it's internal node cache with SV+ gateway field has been fixed.

The SV+ gateway field is the key to link0/link1 IP reachability trap generation. Without the clear indication whether a node is SV+ gateway, the current link0/link1 IP reachability capability would generate traps twice for the SV+ gateway node.

CSCdk42768

A functional inconsistency in Network Browser process in reporting state of AXIS nodes and state of routing nodes has been fixed.

CSCdk43249

bc (back card) value is not updated properly in connection table when creating a FR-FR connection using Connection Manager. A wrong value of 65535 is stored always.

CSCdk44179

Slot dialog in Connection Manager shows slot 0 when selecting Voice and Data slots on an IPX node. This problem occurs when using SV+ 9.1 to manage 8.4 IPX node. This problem has been fixed in emsc process.

CSCdk44435

SV+ Connection Manager does not allow the "Signalling pass through" option be changeable during PVC addition on CESM structured port. The problem only occurs when the CESM structured port speed is greater than 64Kbps (more than 1 T1/E1 timeslot).

There is no work-around to this problem, other than changing the option from AXIS CLI.

Further Problem Description: The "Signalling pass through" option is applicable for any CESM structured port no matter the structured port included only one or more than one timeslot.

CSCdk45518

After a FRP port is deleted, it takes sometimes before it can be added back, even though SNMP get on the port confirms that the port is deleted. The wait is usually more than 30 seconds. This has been fixed in ConnProxy process.

Further problem description: This is a timing issue. After the port is deleted, if an attempt to add back that port is done immediately, ConnProxy may not allow user to do so. The reason is ConnProxy goes to the DB to check for port existence. And if it happens that the robust message has not come from the network to update the FRP table, ConnProxy thinks the port still exists and hence reject the add operation. The fix is to remove the DB port existence check, and forward the add request to the switch to let it determine if the port exists or not.

CSCdk45650

PVC Failed trap 25011 sent when AXIS switch to secondary FRSM card and the PVC is shown in failed state. This happens when secondary FRSM-8 card takes over from primary FRSM-8 card in a redundant card setup in AXIS shelf.

Further Problem Description:

When switch from a primary FRSM-8 card to a secondary FRSM-8 card on an AXIS shelf, a PVC failed trap is sent from SV+ and on Connection Manager the connection will be in Failed state and later on back to clear state. In OpenView/NetView trap log, user will see User Connection Failed followed by User Connection Clear traps.

CSCdk46980

The MIB definitions for svConnAlarmLocalEndNNI and svConnAlarmRemoteEndNNI do not correspond to the OID values being sent in the PVC traps.

The MIB defines these variables as:

1.3.6.1.4.1.351.1.101.1.17.1.10

1.3.6.1.4.1.351.1.101.1.17.1.11

The Trap sends:

1.3.6.1.4.1.351.1.101.1.17.1.12

1.3.6.1.4.1.351.1.101.1.17.1.13

This has been fixed in databroker process.

CSCdk47096

SV+ sends trap 20003 instead of trap 20011 for UFM port alarms.

CSCdk47462

SV+ still reports 1000 - 1003 event log traps are reported, instead of 1004 - 1007. With this fix only 1004 - 1007 event log traps will be generated with one less varbind than the original 1000 - 1003 traps.

CSCdk48096

Trap 20009 doesn't have slot number as part of the trap format. The format and definition have been updated in SV+ Network MIB.

CSCdk48105

Trap 20009 doesn't provide line number in UXM IMA set up on IGX nodes. This problem has been fixed in emsc process.

CSCdk48184

Connection Manager GUI has been enhanced to accept 125 msec as the minimum CDVRXT for CESM cards in Axis 4.1.02 release or later.

CSCdk48793

When executing pkgadd -d CSCOsv error message "please create group users9" is shown. For this group'users9' has to be created before running pkgadd command. This problem has been fixed in INSTALL program

CSCdk50227

SCM will not come up again, if X-server of the desktop is shutdown while SCM is running, by invoking from SV+ script, after restarting the X-server. This problem has been fixed in SV+ script.

CSCdk52835

An intermittent DB inconsistency problem, in which an incomplete PVC(ATM-FR) shown as complete, has been fixed. This problem has been fixed in databroker process.

The problem only occurs intermittently during PVC provisioning when the node of the ATM side is not responding and the traps from the AXIS node arrive not in a timely manner.

CSCdk50328

ungroup tool deletes the connection and doesn't add back.

CSCdk52899

Typographical errors for trap reason codes 92 and 4005 have been fixed in Network MIB.

CSCdk53210

SV+ Topology map doesn't reflect the correct status of ESP nodes. This problem has been fixed in topod process.

CSCdk53307

Error message "Other end CIR out of range for this end card;" is returned when adding or modifying ATM-ATM/ATM-FR 2-segment or 3-segment connection.

This problem occur only when there is a BXM card on the routing segment of the connection and CIR is set to < 19.2k or SCR is set to < 50.

Further problem description: SV+ is enhanced to round up the SCR parameter to 50 for the routing segment if user is adding/modifying the end segment CIR to < 19.2k or SCR < 50. In a 3-seg con case, the end segments will have the user-configured value for CIR or SCR while the middle segment will have SCR=50.

CSCdk53677

Percent utilization set for connections modified using ConnMgr GUI is not updated properly in database as well as on switch. This problem happens only for FRP-FR DAX connections or 2 segment FRP DAX connections (defined as a 2 segment connection where the routing segment is a DAX connection, and the user endpoint on the routing segment is FRP).

SV+ ConnMgr GUI allows you to configure the percent utilization on these types of connection. The Modify Connection screen confirms the modified percent utilization parameters. However, the switch CLI display shows the old percent utilization. In fact, the segment entry in the segment table of SV+ database still shows the old percent utilization value.

CSCdk54230

A problem in StrataView subsystems related to synch-up with network has been fixed. This problem occurs usually in large network setup and due to this problem StrataView could take more time to synch-up with the network.

CSCdk54488

Software, Firmware download window doesn't come up from OpenView window, if IGX8450 node is selected.

CSCdk54496

When IGX8450 is configured as the gateway node for SV+, CiscoView is not launched when Equipment Management icon is selected from the Desktop.

CSCdk54751

Connection Manager GUI doesn't list ATM-FR PVCs, when user selects the view from FR end. This problem has been fixed in Connection Manager GUI process.

CSCdk55470

Can not delete a 2 segment ATM-CE connection, if the connection was added with CE as local endpoint.

Workaround:

Add 2-segment with ATM being the local endpoint.

After an add, click on the Apply button to list that newly added connection again. Then delete. The apply button triggers CM GUI to get the connection from user_connection table. The query will result in ATM being the local end.

CSCdk55524

Connection manager GUI shows CE-ATM: Cant get segment info from Data-base for modify/delete kind of operations on ATM-CE PVCS.

CSCdk56367

An intermittent exit problem in emc process has been fixed.

CSCdk56493

A problem in PortProxy process, where add port operation on UFM card fails, has been fixed.

CSCdk56970

PortAlarm trap 20011, has only <slot>.<port> in trapIdString. <line> description is missing.

CSCdk58237

ConfigDevice window in Equipment Manager GUI doesn't recognize IGX8450 node. If IGX8450 node is selected, an error message 'Unknown Node type' is shown.

CSCdk58256

In Equipment Manager, upline and upport features do not function for UXSM card and ALM/A front card with UAI/T3 as back card in IGX8450 node.

CSCdk59072

SV+ forwards trap 20000 in corrupted format. This problem has been fixed in emsc process.

CSCdk60151

A problem in rtm process, where keep alive messages to AXIS shelves are not sent, has been fixed.

CSCdk61676

Trap 20004 returns incorrect trapReason for clear state. The problem has been fixed in SV+ Network MIB file.

CSCdk63619

A problem in emsc process, which could lead to database inconsistencies have been fixed.

CSCdk63847

Installation fails with the message "RESIDENT_VAL: Undefined variable". This problem has been fixed in INSTALL procedure.

Anomalies Corrected in SV+ 9.1.05 Patch 1

The following anomalies have been corrected in Patch 1 of the 9.1.05 release of StrataView Plus.

Bug ID Descriptions

CSCdk57648

In SV+ Topology, once a group has been created by collecting a set of routing nodes, there is no way to access the individual routing nodes without deleting the group. This problem has been fixed in NWTopology process.

To access nodes and trunks in a group, two different dialogs - NodeListDialog and TrunkListDialog - have been implemented. The NodeListDialog provides a list of all the nodes in a group along with information about the nodes. Admin, Display Shelf, and SW/FW Images command are provided on the dialog in the form of buttons. The NodeShelfDialog can be invoked by:

1 .Double clicking on the group

2 .Pressing the right button on the group and then invoking the "Display Node List" command from the popup menu

3 .From the Group->Display Node List pull down menu

Steps (2) & (3) allow you to bring up the TrunkListDialog.

CSCdk57649

Overview map in SV+ topology doesn't get updated, when a layer (background/name/IP address) is turned off/on in the main map. This problem has been fixed in NWTopology process.

CSCdk67145

SCM will skip sending request to tftp GET the stats file for some nodes in a random pattern. This results in missing stats in the database. This problem has been fixed in statsmain process.CSCdk67145: SCM will skip sending request to tftp GET the stats file for some nodes in a random pattern. This results in missing stats in the database. This problem has been fixed in statsmain process.

Anomalies Corrected in SV+ 9.1.05 Patch 2

The following anomalies have been corrected in Patch 2 of the 9.1.05 release of StrataView Plus.

Bug ID Descriptions

CSCdk72509

A selected node or trunk in SV+ Topology is displayed in a different color (purple) than the regular alarm color. Selection of node/trunk is required to execute pull-down menu commands that require either node or trunk as an argument. The normal behavior is a selected node/trunk stay that way (hiding the alarm) until it is deselected or another node/trunk is selected. The problem is when a node/trunk is double-clicked on to bring up a dialog and in the process the node/trunk gets selected although it is not intended. This problem has been fixed in NWTopology process.

The problem has been fixed by making sure that before bringing up a dialog on a node/trunk as a result of a double-click on it, the node/trunk is deselected. However, if a node/trunk is selected and then a pull-down menu command is invoked to bring up a dialog, the node/trunk would continue to be selected even after the dialog has gone away. In this case the node/trunk has to be implicitly deselected.

CSCdk72513

An unexpected exit problem in SV+ Topology, when a group icon is selected and the Component->Node->Display Shelf command is invoked, has been fixed.

CSCdk72519

SV+ Topology main map doesn't show the background map while overview map of topology shows the background map. This problem occurs only SV+ 9.1.05 Patch 1. This has been fixed in NWTopology process.

Further problem description: This problem happens, if the configuration is saved when the background map is turned off. On subsequent restart of NWTopology, the main map gets displayed without the background map but the overview map comes up with the background map. Turning on the background map layer on the main map toggles the display of background map on the overview window.

CSCdk75077

No statistics option appears in Wingz reports menu. This happens because of the missing Wingz worksheet and configuration files from SV+ 9.1 distribution.

Anomalies Corrected in Patch 2 and Rolled up from SV+ 8.4

The following anomaly of SV+ 8.4 has been corrected in Patch 2 of the 9.1.05 release of StrataView Plus.

Bug ID Descriptions

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.

Anomalies Corrected in SV+ 9.1.05 Patch 3

The following anomalies have been corrected in Patch 3 of the 9.1.05 release of StrataView Plus.

Bug ID Descriptions

CSCdk76868

SV+ Connection Proxy fails to add CAS connections on CESM-8E1 port if the value of svCEEndPointCAS object is set to 2 (yes). This problem has been fixed in ConnProxy process

Anomalies Corrected in SV+ 9.1.05 Patch 4

The following anomalies have been corrected in Patch 4 of the 9.1.05 release of StrataView Plus.

Note Patch 4 includes CiscoView 2.0 device packages for BPX, IGX and AXIS devices.

Bug ID Descriptions

CSCdk84925

SV+ Connection Manager GUI does not show the preferred route properly. This problem occurs when the preferred route contains routing node having "-" as part of the node name. This problem has been fixed in Connection Manager GUI process.

Anomalies Corrected in SV+ 9.1.05 Patch 5

Patch 5 is required on all workstations where SV+ 9.1.05 Patch 3 or Patch 4 has been installed.

Bug ID Descriptions

CSCdk86224

AXIS shelves become unreachable, if different SNMP community strings, other than the defaults settings, for non AXIS nodes are given in /usr/users/svplus/config/svplus.conf file. This problem has been fixed in rtm process.

As a work-around to this SV_COMMUNITY string in /usr/users/svplus/config/svplus.conf file can be changed to public and the GET community string on non-AXIS nodes. Set community string can be something other than the default value private.

Corrected Anomalies Rolled Up From the SV+ 9.0 Release

The following anomalies of the 9.0 release of StrataView Plus have been corrected and rolled into the 9.1.05 release of StrataView Plus.

Bug ID Descriptions

CSCdk17392

In Connection Manager GUI, DE to CLP mapping is not available for FR-ATM connections. This problem has been fixed in Connection Manager GUI process by enabling the "Set CLP Zero" and "Set CLP One" for Channel types SIW-Transparent and SIW-Translate.

CSCdk45939

The % util field in ConnManager is not updated when PCR(0+1) value is changed for ATM-ATM connections.

Corrected Anomalies Rolled Up From the SV+ 8.4 Release

The following anomalies of the 8.4 release of StrataView Plus have been corrected and rolled into the 9.1.05 release of StrataView Plus.

Bug ID Descriptions

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 prone to drop packets. When configuration packets going from SV+ to a switch get dropped, the retry (retransmission) mechanism in SV+ does not work and loadcnf aborts.

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

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.

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

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.

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.

CSCdk36752

An intermittent problem in SV+ install where the install process hangs has been fixed. The problem is in ilog_cleanup tool which is used by the install process.

CSCdk45447

A problem in Equipment Manger GUI, where it displays incorrect information if a slot number field on Equipment Manager: Configure Port Dialog is changed, has been fixed.

CSCdk60860

Following BPX stats have been added to SV+ Stats Collection Manager:

  • BIP-8 Errors (stat id 40)

  • BIP-8 Errored Seconds (stat id 41)

  • BIP-8 Severely Err Secs (stat id 42)

Anomalies in the 9.1.03 Release of StrataView Plus

This section describes known anomalies in the 9.1.03 version of StrataView Plus.

Corrected Anomalies with the SV+ 9.1.03 Release

The following conditions in the previous releases of SV+ have been corrected with the 9.1.03 version of StrataView Plus.

Bug ID Descriptions

CSCdj63461

The status for CESM connection gets updated with an undefined value 143. This has been fixed in emc process.

CSCdj64376

An intermittent error log problem in emc process has been fixed. emc logs IMATM card with trunk ports as unknown card type in it's log file /usr/users/svplus/log directory.

CSCdj87578: Wingz data report shows UFM-E1 narrow band trunk category.

CSCdk21052: After SV+ install Wingz reports tool may not work due to some file permission problem. This has been fixed in SV+ install procedure.

As a work-around user can execute the following commands.

# ln -s /usr/users/Wingz/DataLink/DBLink /usr/users/Wingz/DBLink

# chown -R svplus /usr/users/Wingz

# chgrp -R svplus /usr/users/Wingz

CSCdk21512

A problem with database consistency during SV+ warm-start has been fixed in emc process. SV+ DB doesn't get updated properly during warm-start if some FRSM channels are deleted while SV+ is not running and SV+ is warm-started after this deletion.

CSCdk22503

The tbcount, dbcount and svdbcount scripts in the /usr/users/svplus/tools directory are not functional.

CSCdk22563

In some cases modify FRASM BSTUN parameter svFrPortDataEncoding using PortProxy fails with error: "Can not change line or DS0 Bit or speed".

CSCdk23023

ATM-FR connections can't be added using SV+. An attempt to do so fails with the error message from switch Agent:

  • "Interworking ATM-CONS are not allowed" or

  • "Remote card is inappropriate type (AIT)"

This happens when the FR side is an IPX/IGX feeder connected to an IGX hub. This happens because SV+ tries to add the middle segment with subtype=vbr or abr, but it results in error because BTM does not support vbr/abr.

CSCdk25344

Trap 20004 generated after a switchcc on BPX gives undefined values for trapReason (3055) and trapCardStatus (4). This problem has been fixed in emsd process. SV+Network.MIB has also been updated.

CSCdk29857

EMGUI will not show the correct line status if there is any alarm or the alarm is cleared. Also the connection status shown on CMGUI will be incorrect in case of alarm of if the alarm is cleared on FRSM or any other card related to following traps:

dsx1LineNoAlarmTrap (50120)

dsx1LineInAlarmTrap (50121)

dsx1LineLpbkEnableTrap (50122)

dsx1LineLpbkDisableTrap (50123)

As a work-around to this SV+ can be restarted.

CSCdk28176

NWTopology process exits intermittently in an unexpected manner.

CSCdk30796

The create_db process in SV+ doesn't create stored procedures if it is run by user root.

CSCdk33349

Alarm state of lines of SRM card shown on Equipment Manager GUI line configuration are not correct. The problem has been fixed in Equipment Manager GUII process.

CSCdk34194

Traps 25010, 25011, 25012 do not contain correct svConnType if they are generated on ATM-FR connections.

Corrected Anomalies Rolled Up From the SV+ 8.4 Release

The following conditions have been corrected in the 8.4 release of StrataView Plus and rolled into the 9.1.03 version of StrataView Plus.

Bug ID Descriptions

CSCdj52072:

Connection Manager GUI does not allow value=0 for %util parameter on BXM card with serviceType=UBR. The problem exists for connections UBR.1 and UBR.2 service types involving BXM cards.

A work-around for this is to use CLI to modify the %util value to zero.

CSCdj63905:

Equipment Manager GUI does not reflect the correct color for administrative state on SRM3T3 in release 4 AXIS shelves. This problem happens because of improper handling of the related trap by emc process.

The problem has been fixed in both Axis firmware and StrataView Plus releases. Axis fix is in release 4.0.13 or later.

The workaround for this is to do a node resync from Equipment Manager GUI after disabling the line.

CSCdj72753:

The documentation error regarding atmEndPointMinAdjustPeriod object in SV+Service.MIB has been fixed. The range now has been changed to 3 to 255.

CSCdj77436:

SCM may not collect statistics files 12 collection cycles back if the history files are set to >= 12. This problem has been fixed in statsmain process.This problem only occurs if the number of history files to collect is set to >= 12.

CSCdj78846:

Unable to collect the following statistics via TFTP from BXM trunk lines when selected from SV+ stats manager:

T3 Trunk

41) BIP-8 Errors

98) Frame Sync Errors

197) Tx NTS Cells Discarded

198) Tx Hi-Pri Cells Discarded

199) Tx Voice Cells Discarded

200) Tx TS Cells Discarded

201) Tx BData A Cells Discarded

202) Tx BData B Cells Discarded

203) Tx CBR Cells Discarded

204) Tx ABR Cells Discarded

205) Tx VBR Cells Discarded

E3 Trunk

41) BIP-8 Errors

197) Tx NTS Cells Discarded

198) Tx Hi-Pri Cells Discarded

199) Tx Voice Cells Discarded

200) Tx TS Cells Discarded

201) Tx BData A Cells Discarded

202) Tx BData B Cells Discarded

203) Tx CBR Cells Discarded

204) Tx ABR Cells Discarded

205) Tx VBR Cells Discarded

(98) Frame Sync Errors and

(141) FEBE Counts can be configured for a T3 trunk but don't appear for an E3 trunk.

(170) Loss of Cell Delineation can be configured for an E3 trunk but doesn't appear for a T3 trunk.

Further explanation of the problem:

Frame Sync Errors

As of today, On E3 trunks only Direct Map mode OR HEC framing is supported. With this type of Line Framing "Frame Sync Errors" are NOT supported.

Loss of cell delineation

If the Line Framing was SET to HEC framing by doing cnftrk, ONLY then this stat is valid. When it is configured in the PLCP mode, this count is not valid.

FEBE Count

This fix is done in Switch Software.v

The rest of the missing counters are fixed in StrataView Plus SCM.v

CSCdj80624

The status of a trunk in the packet_line table of SV+ DB is inconsistent with the status displayed in the CLI of the switch. The packet_line table is written to by both topod and emsd although to update different sets of attributes. But this may at times create the scenario that when either of them is writing the other also tries to write which fails and as a result the database may not get update with the correct values for some of the attributes (trunk status in this case). This gives rise to database inconsistency. This problem has been fixed in topod and emsd processes by introducing retry mechanism for DB writes

CSCdj83864:

CM GUI differs from SNMP/CLI in configuring CLLM ports. User can't change the cllm enable, and timer when the FR port is configured to LMI or UNI protocol type, in the Equipment Manager GUI.

CSCdj85527:

SV+ install script overwrites the perl executable in /usr/local/bin with the version bundled with StrataView media. This problem has been fixed SV+ INSTALL procedure.

A work-around for this problem is to save the existing copy of perl before the install and restore it back in /usr/local/bin after StrataView installation.

CSCdj88137:

TestConn returns erroneous data in SNMP for FR-ATM PVC. The returned values do not match with the values described in SV+Service.MIB file. This problem has been fixed in ConnProxy process.

The above problem happens if a TestConn is executed for a FR-ATM connection from the ATM end and if the test is successful, the test result returned actually contains the delay, a positive integer value, rather than the expected 0.

As a work-around for this any positive value returned can be considered as success.

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:/usr/users/svplus/incoming/<axisnodename>.0317981700

Mar 17 17:17:00 ERROR:0 BinaryProcessor.c@258:

This problem happens only with release 4.0.09x Axis shelves.

CSCdj89302:

When statistics collection is in progress SCM does not warn you while exiting that statistics collection will be stopped upon exit.

CSCdj89609

Strata View Plus Equipment Manager GUI shows BNM Clock Source as AUM Inband instead of BNM Inband. This problem has been observed with Strata View 8.4.10 manager Axis shelves with release 4 or higher BNM cards.

CSCdj89825

:When a SNMP GET operation is done on the ServiceMib object svPortIfType and svAtmPortIfType for a port on a BXM-12T3 or BXM-8T3 card, the Port Proxy Agent returns the wrong value of 16 which is oc12-smf. The correct value should be 4 for t3. Similar problem happens to BXM-8E3 and BXM-12E3 cards also, for which the correct value is 5 for e3.

CSCdj91893:

OpenView trapd.log file shows some Axis traps in no defined format. This could happen if traps from axis.mib are loaded (using OpenView menu options etc.), prior to StrataView installation. This has been observed in StrataView 8.4.10.

The work-around for the above problem is available only for Axis traps 50120-50123.

Login as root and run following commands from /usr/users/svplus directory:

# /opt/OV/bin/xnmevents -delete dsx1LineNoAlarmTrap dsx1LineInAlarmTrap\ dsx1LineLpbkEnableTr dsx1LineLpbkDisableT

# cd /usr/users/svplus

# ./SV+_HPOV.install

The above problem has two parts

1 .Traps 50120-50123 have some conflicts with axis.mib definition of Trap. The trap names are:

  • dsx1LineNoAlarmTrap
  • dsx1LineInAlarmTrap
  • dsx1LineLpbkEnableTr
  • dsx1LineLpbkDisableT

2 .SV+_HPOV.install was not loading format into trapd.conf for the following traps:

  • coreCardsConfigClear
  • bnmTrunkCellFormatTr
  • trapBERTStart
  • trapBERTEnd
  • trapBERTAbort
  • srmLossOfClockTrap
  • trapImaRcvAisLoam
  • trapImaRcvRdiLoam
  • trapImaFailedOtherRe
  • trapImatmDsx3HecChan
  • trapCardOvrSubscribe
  • trapPortOvrSubscribe
  • trapAusmPortSvcRange
  • trapImaPortSvcRangeC

These missing traps have been added to StrataView's StrataCom_trapd.conf file.

CSCdk01192:

When adding a BXM or ASI port that is already existing, the error message in the error table is incorrect. The error message reported the wrong port with a bogus shelfName, in the format "Port routingNodeName.shelfName.slot.port already exists". The correct error message should not have the shelfName. This problem has been fixed in PortProxy process.

CSCdk07105:

When trap 50045 is received, the HPOV event browser dumps the varbind list instead of trap description string. This trap is generated when secondary card becomes active as the primary card fails.

CSCdk07451:

For userLogoutTrap (55021) from axis, OpenView event browser shows incorrect value in user field.

CSCdk09486:

A database inconsistency problem related to user_connection table has been fixed in emsc process. Because of this problem entries in user_connection table do not match with status on network and atm_connection table. This problem could happen if addition and deletion of connections on the same switch are done at a rapid rate or when SV+ is down.

As a work-around for this problem SV+ database can be re-created and SV+ can be started.

CSCdk10508:

A database inconsistency issue related to logical connections has been fixed in emsc process. SV+ database table logical_conn contains rows that do not correspond to any existing connection. These rows are leftovers from connections that have been deleted. This problem can happen if connection addition & deletion is performed while SV+ is down or if SV+ is up but the network is busy.

As a work-around for this problem SV+ database can be re-created and SV+ can be started.

CSCdk10837:

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.

CSCdk11895:

Equipment Manager GUI displays incorrect values for rcv/xmt AIR counter values for FR-channels, in the view counter screen.

This problem happens if the network has Axis 4 shelves with FRSM-4 cards and SV+ is 8.4.09, 8.4.10 or 8.4.11.

CSCdk13002:

As a work-around to this problem, the line field in Equipment Manager GUI Port configure window can be left out. This results in ports on line 4 displayed along with the other ports.

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+ 9.1.02 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.

CSCdk14193:

As a work-around to this problem, node resync can be opted from Equipment Manger GUI. This will update the GUI with line distribution status.

CSCdk14782:

An intermittent exit problem in Desktop process has been fixed. This problem has been observed when SV+ processes are stopped while Desktop is running.

CSCdk21314:

The equipment management subsystem (emd, emc processes) and DataBase schema have been updated to support the new card state reserved in Axis releases 4.0.16 onwards. Axis send this reserved state if a card is pulled out from its slot. In Equipment Manager GUI a card in this state will be shown as empty slot.

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.

CSCdk24102:

Maintenance logs (event logs) on switches are logged but do not immediately appear in HPOV event browser. Sometimes the delay is very significant, i.e.,in hours. Traps may seem to be bursted into HPOV event browser every 2 to 3 minutes. This has been fixed in eventd process.

The problem occurs when a new switch is added to the network, but not yet added to SV+ workstation(s) local /etc/hosts file or on the DNS server. The problem also occurs whenever the entire network status changes.

As a work-around to this problem an entry with node name "NETWORK" (all capital letters) and a dummy IP address can be added to SV+ workstation(s) local /etc/hosts file (or to SV+ system(s) hosts database if /etc/hosts is not consulted by system running SV+).

Prior to introducing a new switch to the network, the node name and its IP address should be added to the SV+ workstation(s) local /etc/hosts file (or to SV+ system(s) host database if /etc/hosts is not consulted by system running SV+).

If for whatever reason, the symptoms occur, try to "ping" all the nodes and node "NETWORK" from the SV+ workstation(s). If any node is unreachable, add the node name to local /etc/hosts file (or to SV+ system(s) hosts database if /etc/hosts is not consulted by system running SV+).

A work-around to this is to select a IPX/IGX feeder which is connected a BPX hub or connection can be added using CLI.

CSCdk24394

If the softswitch command is executed on CLI to switch primary card to secondary card in redundant card setup, the PVCs on primary card are stayed in failed state on SV+ CMGUI. even though the PVCs on AXIS shelves and switches are in clear state. This problem has been fixed in emc process.

As a work-around for this problem, StrataView can be cold started (clearing the DB and restarting SV+).

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

CSCdk33001:

Statistics collection won't get completed on nodes running 8.4.X SWSW. This problem has been observed when running SCM with SV8.4.11.Patch2 and SCMSA_8.4.11.Patch2 on 8.4.X nodes. This problem has been fixed in statschild process.

Corrected Anomalies Rolled Up From the SV+ 9.0 Release

The following anomaly has been corrected in the 8.4 release of StrataView Plus and rolled into the 9.1.03 version of StrataView Plus.

Bug ID Descriptions

CSCdj84298

Wingz does not display object for selected line statistics for E1 line type.

:

Serial Configuration Upload Download (SCUD)

The Serial Configuration Upload Download (SCUD) product, as the name says, supports IPX/BPX/IGX configuration save and restore functionality over a serial interface.

The current available is 2.0. This tool is used for disaster recovery and is available free of cost to Cisco SV+ users having support contract.

SV+ Development is actively attempting to add this tool to CCO. Once this is done, one should be able to find the links to the SCUD patches at the CCO site.

http://www.cisco.com

SCUD Features

    1. Supports configuration save and restore for a single node network.

    2. SCUD uses serial line interface on 'Control Port' of switch.

    3. Following baud rates are supported:

    4. The "Node Administration" window is used for user logins.No topology map will be shown.

    5. SCUD supports IPX, BPX and IGX switches.

    6. SCUD can be launched by any user and does not need special privileges.

    7. SCUD uses the same directory structure used by SV+ to save/restore configurations.

Hardware Requirements

The SCUD software will run on any Sun workstation running SunOS 4.1.x operating system. It can also be run on Sun workstation running Solaris 2.5 or 2.6 with binary compatibility support. The minimum memory requirement is 64MB. There is no special hardware requirement.

Installation

SCUD software is available on quarter inch tape in UNIX tar format. Following procedure needs to be followed for installation.

Step 1 Login on Sun workstation.

Step 2 Change directory to where you need to install SCUD (SCUD home directory). It is advisable to install SCUD in the /usr/users/svplus directory. For this you have to move any existing SV+ installation in /usr/users/svplus to some other place before installing SCUD.

Step 3 Insert tape in the tape drive.

Step 4 Use tar command as shown below to get software loaded.

$ tar xvf /dev/<driveid>

where <driveid> indicates the tape drive identifier
e.g. rst0, rmt0 etc.

There is no install script to be run. The software is ready for use.

Configuration

SCUD Software Configuration

SCUD software uses two configuration files. Configuration file 'cnfnodes' is used to specify the switch identification. Second file 'config.sv' is similar to one used by SV+ product and contains the serial line configurations.

'cnfnodes' file can have only one line with format shown below:

<nodename>|<switch_node_id>|<switch_net_id>|<SV+_netid>|

e.g.

nmsipx02|2|1|1|

'switch_node_id' is node id of a switch.

'switch_net_id' is network (also called as domain) is of a switch.

'SV+_netid' is SV+ network id (from config.sv file)

'config.sv' can have only one line with following fields and '|' as delimiter:

SV+_netid NO NEED TO CHANGE

networkname NO NEED TO CHANGE

serialport Specify the device file name for the serial port used

Baudrate Set serial port speed, must match speed of control port at the node

autodial Phone # to dial out including any prefix needed, 0 for not dialing

SV_Timeout NOT ALLOWED TO CHANGE

Retransmit NOT ALLOWED TO CHANGE

DL_Thresh_TO NOT ALLOWED TO CHANGE

DL_Ack_TO Set application level time-out value in seconds as appropriate

DL_Blk_Size Set transmission block size in bytes, no greater than 1024

Release Specify switch software release as appropriate

e.g.

1|Network1|/dev/ttya|19200|0|7|3|0|30|256|8.1

Serial Port Configuration On SCUD Workstation

If SCUD is running with SunOS system, no configuration is needed for the serial port. User only need to identify which tty (/dev/ttya or /dev/ttyb) is for SCUD to use.

If SCUD is running with Solaris system, user need to run the system administration tool "admintool" to configure the serial port as "Modem - Dial-Out Only". This tool can only be run by super user (root). The serial port device name to use in the "config.sv" file should be "/dev/cua/a" for ttya and "/dev/cua/b" for ttyb.

Remote Node Control Port Configuration

Configure the control port of the remote node to be connected as follows:

    1. Run "cnftermfunc c 1" command to set control port function as VT100/StrataView.

nmsipx06        TN     StrataCom              IPX 8       8.1.50        Sep. 18 1997 19:16 PST 
 
 
Control port	Auxiliary port
 
1. VT100/StrataView	1. Okidata 182 Printer
2. VT1002. Okidata 18	2 Printer with LOG
	3. VT100
	4. Alarm Message Collector
	5. External Device Window
	6. Autodial Modem
 
 
 
 
 
 
                                                                                                                              
Last Command: cnftermfunc c 1
 
 
Next Command:

    1. Run "cnfterm c 19200 n 8 1 x x y n" command, replacing the port speed parameter (19200) to match the setting in 'config.sv' file, to configure the control port to this settings:

nmsipx06        TN     StrataCom              IPX 8       8.1.50        Sep. 18 1997 19:29 PST 
 
 
Control port		Auxiliary port
 
Baud Rate:	19200	Baud Rate:	9600
 
Parity:	None	Parity:	None
Number of Data Bits:	8	Number of Data Bits:	8
Number of Stop Bits:	1	Number of Stop Bits:	1
Output flow control:	XON/XOFF	Output flow control:	XON/XOFF
Input flow control:	XON/XOFF	Input flow control:	XON/XOFF
CTS flow control:	Yes	CTS flow control:	Yes
Use DTR signal:	No	Use DTR signal:	Yes
 
 
 
                                                                                                                              
Last Command: cnfterm c 19200 n 8 1 x x y n
 
 
Next Command:

Modem Configurations

Modem settings we use in this recommendation is for Motorola Codex 3220+ model. If you are not using this model, use the corresponding commands for your modem to configure same settings.

    1. Modem attached to the remote node:

    2. Modem attached to SCUD workstation:

Copying Existing Configuration Files

SCUD allows user to save and restore configuration from/to IPX/BPX/IGX switches. The configuration saved using StrataView Plus product is stored under /usr/users/svplus directory using <saveid>_Cfgdir as directory name. When user needs to restore the saved configuration he has to copy this directory under SCUD home directory.

e.g.

If SCUD is installed under /usr/SCUD directory and the current saved configuration has saveid of 'SV72' then user will copy the 'SV72_Cfgdir' directory from /usr/users/svplus/ (or from other directory where files are manually copied) to /usr/SCUD directory.

SCUD Configuration File Setup

Change the 'cnfnodes' and 'config.sv' files to the required configurations.

Change directory to where SCUD is installed.

Set DISPLAY environment variable to your workstation display.

e.g.

 B shell --> $ set DISPLAY :0.0
                 $ export DISPLAY (for local display)
             --> $ set DISPLAY mach1:0.0 
                 $ export DISPLAY (for remote machine name mach1)
     C shell --> % setenv  DISPLAY :0.0 (for local display)
             --> % setenv DISPLAY mach1:0.0 (for remote machine name mach1)

Launch SCUD

Make sure the SCUD configuration files, the remote node's control port and the modems on both sides are configured properly before launching SCUD.

Follow these steps to launch or stop SCUD:

Step 1 Type 'SCUD' on command line and hit <RETURN>

Step 2 Select option 1 to launch SCUD or select 2 to stop SCUD.

When SCUD is launched user will see "Node Administration" window on screen. User can login to the switch and use 'loadcnf' command to restore the configuration. The configuration to be restored must have already been copied to the SCUD home directory.

Establish Modem Connection

There are two ways to make the modem connection:

    1. Use SCUD to dial out

    2. Use other communication tools, e.g. tip

Open Bugs

If network id in 'config.sv' does not match with one from 'cnfnodes' SCUD does not detect it.

User Notes For SCUD 2.0

Restriction

SCUD may not be launched if SV+ software is running on the same workstation.

Configuration Save/Restore Protocol

The protocol between SCUD and the remote node during a configuration save or restore session enforced a simple handshaking protocol that the sending side after sending a data packet, will wait for an acknowledgment (ACK) from the remote side before sending the next data packet. An application level time-out is imposed. When time-out on waiting the ACK, the sending side will send an ABORT message to the remote end and the operation is aborted completely. At the application layer, there is no retry capability. However, at the link layer, each packet will retransmit 3 times before giving up. Depending on the modem line quality, it could be so worse that the session keep aborting and never get completed.

In SCUD release 2.0, some enhancements are added to address this issue:

    1. SCUD will perform retry on a configuration restore session (loadcnf). Configuration data is sent from SCUD to the remote node. When SCUD time-out on receiving the ACK, it will re-send the last data packet. By default, SCUD will try totally 3 times on the same packet before it gives up and abort the session. A "-r <num>" command line option can be given to configd in the "start_SCUD" script to specify the number of retries SCUD uses.

    2. The Baudrate (port speed), DL_Ack_TO time-out value and the DL_Blk_Size values in SCUD's configuration file "config.sv" can be tuned to optimize performance and cope with line quality. For example, if the line quality is good, port speed and block size could be set to a higher value. On the other hand, when line quality is not so good, these 2 fields should be set to a smaller value while DL_Ack_TO should be set to a larger value to give sufficient time for link layer retransmission.

Logging and Debugging Capabilities

Log files are stored in the log directory under SCUD home directory. Messages are appended to these log files continuously even when SCUD is restarted. When they grow to certain size, they are moved to *.old and new log files are used. When the new log files are full again, the *.old will be overwritten. In other words, only one backup is kept to prevent using up all disk space.

These log files are there to help debugging in case problems occur. User should saved these files when there is problem. Otherwise, there is no need to backup these files.

There are some debugging capabilities built into SCUD as highlighted here:

    1. Higher levels (L3 and L4) of verbose messages for log/svmain.log can be enabled at SCUD start-up time and toggled on/off during run time. To enable these levels of verbose messages at start-up time, modify the "start_SCUD" script to include "-w" command line option for socketd as follows:

#!/bin/sh
#
#   $RCSfile: start_SCUD,v $ $Revision: 1.1.4.1 $
#
 
#  -f option for topod and configd need to point
#     the same file.
#  If there is a port conflict then change base
#  4000 to some other number.
 
socketd -b 4000 -c config.sv -g 560x342+1+90 -w << !
topod -e topo.err -f cnfnodes
downld 
configd  -C cnfnodes

    2. Verbose mode can also be turned on for configd process which is responsible for the configuration save and restore operation in SCUD. Modify the "start_SCUD" script to give the "-v" command line option to configd:

#!/bin/sh
#
#   $RCSfile: start_SCUD,v $ $Revision: 1.1.4.1 $
#
 
#  -f option for topod and configd need to point
#     the same file.
#  If there is a port conflict then change base
#  4000 to some other number.
 
socketd -b 4000 -c config.sv -g 560x342+1+90 << !
topod -e topo.err -f cnfnodes
downld 
configd  -C cnfnodes -v

Possible Errors

    1. At times, user may see the following messages:

ipc.c:598:IPC Connect Failed, Address(4001) PID(25409):: Connection refused
topod: send_packet_2_IPX failed, retrying ...
ipc.c:598:IPC Connect Failed, Address(4001) PID(25408):: Connection refused
topod: send_packet_2_IPX retry succeeded.

    2. If in the middle of a SCUD session, the phone line dropped or hung, user has to restart SCUD to re-establish the connection.

unGroup Connections Tool

Introduction

This section describes the installation and use of the unGroup script. This script is designed to allow a network administrator to automatically ungroup all grouped PVCs on an IPX, BPX, or IGX node.

Audience

This document is intended for any user who may need to install or use the unGroup script. Such users may be either Cisco personnel or customer/distributor personnel. It is assumed that the reader is familiar with the Cisco WANBU's IPX, BPX, IGX and StrataView Plus products.

Purpose

The purpose of the unGroup script is to support the switch software upgrades to version 9.1. Grouped connections are no longer supported in switch software version 9.1. The primary motivation for the development of this tool is to allow users to easily ungroup PVCs before upgrading, thereby allowing a switch software upgrade to version 9.1 without losing any PVCs.

Feature Overview

This script will check, prior to ungrouping connections, to make sure that the lcon limit for a given switch would not be exceeded while ungrouping the connections (see table in section 5.0). The script will ungroup Frame Relay, ATM, and Service Interworking connections. All parameters for each connection will be saved in a log file for error recovery. Preferred routes will be preserved for each connection.

Operational Overview

The script first uses node, and connection information from the SV+ database to determine, for each node, if the Luton limit would be exceeded by ungrouping all grouped connections on that node. Then for each node, the script using SNMP will get all the groups for that node, and ungroup each group one at a time. For each connection in a group, the connection parameters are retrieved from the node, and the connection is deleted. Using the saved parameters, the connection is then re-added. Once all connections are ungrouped, the empty group is deleted.

Requirements

The following are the requirements for the unGroup script:

Supported Switch Software Releases

Only releases 8.2.5, 8.4, and 8.5 are supported.

Operating Environment

The unGroup script must be installed and run on a workstation which is running Solaris, and which is running StrataView Plus version 8.4 or 9.0 or 9.1. Since the SV+ database is used, SV+ must be running and in sync with the network.

Required Directories

This script is actually one binary, and two SQL scripts - three files in all. They must be installed on a StrataView Plus workstation, in the /usr/users/svplus/tools directory.

Note that all log files generated by the unGroup script are automatically placed in the /usr/users/svplus/log directory. This directory must already exist on the workstation. It will not be created if it does not already exist and the script will not run.

File Ownerships and Modes

The ownership and group of the files should be the user svplus and the group svplus. The script must be run by the user svplus from the directory /usr/users/svplus/tools. Type ./unGroup at the shell prompt to run the tool.

The mode of the files should be 755 or 777.

Accessing the IPX, IGX, and BPX Nodes

In an in-band network management configuration, the IP-Relay addresses of all nodes are obtained from the SV+ database, and used for executing SNMP requests to the nodes. If the IP-Relay addresses are not configured on every node, the unGroup tool cannot communicate with that node.

Notes, Cautions, and Limitations

If the unGroup tool is invoked towards a network with no grouped connections or running SWSW version with no support for grouped connections, the following error message is shown.

"Getting node information from the SV+ database... No input from SV+ database. Exiting Error accessing SV+ Database. Exiting"

Script Operation

To run the unGroup script, make sure you are logged into the directory which contains the files.

host% ls -l
-r-xr-xr-x  1 svplus   1204224 Feb 26 11:33 unGroup                     -r-xr-xr-x  1 svplus       9011 Feb 26 11:33 gconn.sql                   -r-xr-xr-x  1 svplus     1390 Feb 26 11:33 pref.sql                 host%

The unGroup script options: unGroup [-c] [-n nodename] [-t timeout]

The "-c" option will "check" all nodes to see if the lcon limit for that node would be exceeded if all groups on that node were ungrouped. It will produce a report, with a line for each node, and then the script will exit. This option is used to determine if ungrouping is possible.

The "-n nodename" option will only ungroup connections on that node.

The "-t timeout" option is for setting the SNMP timeout value. This can be used if the default value of 30 seconds is not enough. The value of timeout should be in seconds.

With no option, the unGroup script will check all nodes for lcon limits, and print a report as before, then begin prompting you for confirmation on each node to be ungrouped.

To begin execution of the unGroup script to check all nodes, and produce a lcon limit report, simply type:

host% unGroup -c

The script clears the current window, displays an information banner, and then reads the node, and connection information from the SV+ database. The script will then get the active processor card ram size, for each node, check lcon limits, and produce a report: 

      ******************************************************************
      ** unGroup                                                      **
      ** ~~~~~~~                                                      **
      ** This is a tool which can  be used for ungrouping all grouped **
      ** connections for all nodes in the network. The groups are     **
      ** ungrouped by deleting and readding the connections, one at   **
      ** time.                                                        **
      **                                                              **
      ******************************************************************
 
      Log file name: /usr/users/svplus/log/ungconn.log.980204_104834
 
      Getting node information from the SV+ database...
      Checking lcon limits for all nodes...
 
      Node: nmsbpx02   Lcon limit:  7000, VC count:    33 - OK
      Node: nmsipx15   Lcon limit:  1500, VC count:    73 - OK
      Node: nmsbpx06   Lcon limit:  7000, VC count:    73 - OK
 
 
      All nodes have enough lcons for ungrouping.

The following is the contents of the log file for the the example above:

STARTING ungconn  : Time - 10:48:34
Getting node information from the SV+ database...
Checking lcon limits for all nodes...
Node: nmsbpx02 release:8.4.1.1 ram size: 32 lcon_limit:  7000 VC count:    33 - OK
Node: nmsipx15 release:8.4.1.1 ram size: 16 lcon_limit:  1500 VC count:    73 - OK
Node: nmsbpx06 release:8.4.1.1 ram size: 32 lcon_limit:  7000 VC count:    73 - OK
All nodes have enough lcons for ungrouping.
 
CHECKING LCON LIMITS COMPLETE : Time - 10:48:37

If one the the nodes lcon limits was exceeded, the following messages would be printed to the console and log file:

      Node: nmsbpx02   Lcon limit:  7000, VC count:    33 - OK
  --> Node: nmsipx15   Lcon limit:  1500, VC count:  1510 - LIMIT EXCEEDED
      Node: nmsbpx06   Lcon limit:  7000, VC count:    73 - OK
 
      ONE OR MORE NODES WILL EXCEED LCON LIMIT IF CONNECTIONS ARE UNGROUPED.

To begin execution of the unGroup script to ungroup connections for all nodes, simply type:

host% unGroup

The script will as before get information from the database, check lcon limits, and then prompt you for the first node to be ungrouped:

      ******************************************************************
      ** unGroup                                                      **
      ** ~~~~~~~                                                      **
      ** This is a tool which can  be used for ungrouping all grouped **
      ** connections for all nodes in the network. The ungrouping is  **
      ** done by deleting and readding each connection one at a time. **
      **                                                              **
      ******************************************************************
 
      Log file name: /usr/users/svplus/log/ungconn.log.980204_163037
 
      Getting node information from the SV+ database...
      Checking lcon limits for all nodes...
 
 
      Do you want to ungroup connections on nmsbpx02 ? (Y/N):

If you type no or n, the script will skip to the next node. If you type quit or q, the script will exit. If confirmed by typing yes (or y) then the groups for that node are ungrouped: 

      Do you want to ungroup connections on nmsbpx02 ? (Y/N/Q): y
      Determining number of groups...
 
      Starting to ungroup 10 groups on nmsbpx02
      Deleting empty group : D1.nmsipx15.9 successful
      Deleting empty group : D1.nmsipx15.1 successful
      Deleting empty group : D1.nmsipx15.2 successful
      Deleting empty group : D1.nmsipx15.12 successful
      Deleting empty group : D1.nmsipx15.14 successful
      Conn: D1.nmsbpx02.11.2.109.101 - D1.nmsipx15.5.1.118:  successful.
      Conn: D1.nmsbpx02.11.2.109.100 - D1.nmsipx15.5.1.117:  successful.
      Deleting empty group : D1.nmsipx15.7 successful
      Conn: D1.nmsbpx02.11.1.100.409 - D1.nmsbpx06.11.1.100.409:  successful.
      Conn: D1.nmsbpx02.11.1.100.411 - D1.nmsbpx06.11.1.100.411:  successful.
      Conn: D1.nmsbpx02.11.1.100.410 - D1.nmsbpx06.11.1.100.410:  successful.
      Deleting empty group : D1.nmsbpx06.9 successful
      Conn: D1.nmsbpx02.11.2.107.103 - D1.nmsbpx06.11.1.107.103:  successful.
      Conn: D1.nmsbpx02.11.2.107.102 - D1.nmsbpx06.11.1.107.102:  successful.
      Conn: D1.nmsbpx02.11.2.107.101 - D1.nmsbpx06.11.1.107.101:  successful.
      Deleting empty group : D1.nmsbpx06.10 successful
      Conn: D1.nmsbpx02.11.1.111.303 - D1.nmsipx15.5.1.303:  successful.
      Conn: D1.nmsbpx02.11.1.111.302 - D1.nmsipx15.5.1.302:  successful.
      Deleting empty group : D1.nmsipx15.20 successful
      Conn: D1.nmsbpx02.11.1.111.305 - D1.nmsipx15.5.1.305:  successful.
      Conn: D1.nmsbpx02.11.1.111.304 - D1.nmsipx15.5.1.304:  successful.
      Deleting empty group : D1.nmsipx15.21 successful
 
      All 10 groups successfully ungrouped
 
      Do you want to ungroup connections on nmsipx15 ? (Y/N/Q):

This process will continue for all nodes that have groups, and nodes where the lcon limit would not be exceeded.

The following is the log file content for the first PVC ungrouped in the example above:

STARTING ungconn  : Time - 16:30:37
Getting node information from the SV+ database...
Checking lcon limits for all nodes...
Node: nmsbpx02 release:8.4.1.1 ram size: 32 lcon_limit:  7000 VC count:    33 - OK
Node: nmsipx15 release:8.4.1.1 ram size: 16 lcon_limit:  1500 VC count:    73 - OK
Node: nmsbpx06 release:8.4.1.1 ram size: 32 lcon_limit:  7000 VC count:    73 - OK
All nodes have enough lcons for ungrouping.
 
Getting all group id's from the connTable Mib table
Starting to ungroup 10 groups  on nmsbpx02
 
**** DELETING EMPTY GROUPS *************************************
 
Deleting Empty group: group_name = D1.nmsipx15.9
 
Deleting Empty group: group_name = D1.nmsipx15.1
 
Deleting Empty group: group_name = D1.nmsipx15.2
 
Deleting Empty group: group_name = D1.nmsipx15.12
 
Deleting Empty group: group_name = D1.nmsipx15.14
 
##### UNGROUPING GROUP D1.nmsipx15.7 #####
 
****************************************************************
UNGROUPING CONNECTION 1
endPtIndex = 16, connIndex = 0
 
RETRIEVING INFO FROM THE atmEndPt TABLE
atmEndptIndex             = 16
atmEndptDesc              = D1.nmsbpx02.11.2.109.101
atmOtherEndptIndex        = 43
atmOtherEndptDesc         = D1.nmsipx15.5.1.118
atmEndptAdminStatus       = 5
atmEndptOperStatus        = 1
atmNoRouteFoundFailure    = 1
atmBumpFailure            = 1
atmEndPointFailure        = 1
atmTestFailure            = 1
atmConnPtr                = .1.3.6.1.4.1.351.100.4.3.4.1.1.0
atmNextPtr                = .1.3.6.1.4.1.351.100.4.3.8.1.1.1
atmNextOnPortPtr          = .1.3.6.1.4.1.351.100.4.3.8.1.1.1
atmEndptTrkAvoidType      = 1
atmEndptTrkAvoidZCS       = 1
atmEndptSubType           = 1
atmEndptVcQSize           = 1366
atmEndptEfciQSize         = 100
atmEndptQIR               = 10
atmEndptPercUtil          = 100
atmEndptCBS               = 1000
atmEndptIBS               = 1
atmEndptCCDV              = 10000
atmEndptHiCLP             = 100
atmEndptLoCLP             = 90
atmEndptOeVcQSize         = 1366
atmEndptOeEfciQSize       = 100
atmEndptOeQIR             = 10
atmEndptOePercUtil        = 100
atmEndptOeCBS             = 1000
atmEndptOeIBS             = 1
atmEndptOeCCDV            = 10000
atmEndptOeHiCLP           = 100
atmEndptOeLoCLP           = 90
atmEndptCLPTagging        = 1
atmEndptEnableFST         = 2
atmEndptRateUpICA         = 2000
atmEndptRateDnICA         = 87
atmEndptToQIR             = 10000
atmEndptMinAdjustICA      = 100
atmEndptGroupFlag         = 2
atmEndptOamStatus         = 2
atmEndptBCM               = 2
atmEndptFGCRA             = 1
atmEndptLocLpbkState      = 2
atmEndptLpbkStatus        = -1
atmEndptTestType          = 2
atmEndptRtdTestDelay      = 0
atmEndptOeBCM             = 2
atmEndptOeFGCRA           = 1
atmEndptGroupDesc         = D1.nmsipx15.7
atmEndptLocRmtLpbkState   = 2
atmEndptNRM               = 32
atmEndptFRTT              = 0
atmEndptTBE               = 1048320
atmEndptVSVD              = 1
atmEndptPolicing          = 3
atmEndptPCR               = 10
atmEndptOePCR             = 10
atmEndptSCR               = 10
atmEndptOeSCR             = 10
atmEndptMCR               = 10
atmEndptOeMCR             = 10
 
RETRIEVING INFO FROM THE Connection TABLE
connIndex                 = 0
connLclEndptDesc          = D1.nmsipx15.7
connType                  = 2
connOeIndex               = 6
connRmtEndptDesc          = No Remote Connection Descriptor for a Grouped Connection
connMasterFlag            = 2
connClassOfService        = 0
connGroupFlag             = 2
connAdminStatus           = 4
connOperStatus            = 1
connNoRouteFoundFailure   = 1
connBumpFailure           = 1
connFirstEndptPtr         = .1.3.6.1.4.1.351.100.4.3.8.1.1.1
connCurrRouteDesc         = nmsbpx023.1--0.0nmsbpx060.0-- 8nmsipx15
connPrefRouteDesc         = Not Configured
connMstOSpacePkts         = 14620
connMstOSpaceCells        = 78343
connMstOSpaceBdaCmax      = 65534
connMstOSpaceBdbCmax      = 65534
connSlvOSpacePkts         = 2147483647
connSlvOSpaceCells        = 78384
connSlvOSpaceBdaCmax      = 65534
connSlvOSpaceBdbCmax      = 65534
connIcaRTD                = 0
connGroupDesc             = D1.nmsipx15.7
 
SUCCESSFULLY DELETED CONNECTION
endPtIndex = 16, connIndex = 0, D1.nmsbpx02.11.2.109.101 - D1.nmsipx15.5.1.118
 
ADDING CONNECTION
atmEndptDesc             : D1.nmsbpx02.11.2.109.101
atmOtherEndptDesc        : D1.nmsipx15.5.1.118
atmEndptAdminStatus      : 1
atmEndptTrkAvoidType     : 1
atmEndptTrkAvoidZCS      : 1
atmEndptSubType          : 1
atmEndptVcQSize          : 1366
atmEndptEfciQSize        : 100
atmEndptPercUtil         : 100
atmEndptCBS              : 1000
atmEndptIBS              : 1
atmEndptCCDV             : 10000
atmEndptOeVcQSize        : 1366
atmEndptOeEfciQSize      : 100
atmEndptOePercUtil       : 100
atmEndptOeCBS            : 1000
atmEndptOeIBS            : 1
atmEndptOeCCDV           : 10000
atmEndptPolicing         : 3
atmEndptPCR              : 10
atmEndptOePCR            : 10
atmEndptSCR              : 10
atmEndptOeSCR            : 10
 
CONN SUCCESSFULLY UNGROUPED
New EndPtIndex = 16, New connId = 3
All EndPt ConnInfo freed
****************************************************************

Theory of Operation

When the script starts, it first accesses the SV+ database to obtain node and connection information. Specifically it gets the node name, IP address, node type, switch software release, number of VCs, and number of groups. Only nodes which are an IPX, IGX, or a BPX, and are active and reachable, are retrieved from the database. Then for each node a SNMP GET request is made to get the switch to get the amount of RAM on the active processor card. If no processor card is found to be in the active state, an error is printed and this node is skipped. Note that all SNMP requests are made using the IP address from the database.

Next, for each node a check is done to see if the switch lcon limit would be exceeded if all grouped connections were ungrouped on that node. Using the node type, switch software release, and RAM size on the active processor card, the following table is indexed for the lcon limit.

BCC 32 BCC64 NPC 16 NPC 32&64 NPM 32 NPM 64
8.2.5

1000

na

850

1000

1000

1000

8.4

7000

12000

850

1500

1500

1500

8.5

7000

12000

850

1500

2750

3500

The lcon limit is compared with the VC count from the SV+ database. If the limit would be exceeded, this node is marked, so as not to be ungrouped.

Note To check the number of lcons using the switch CLI, use the command: dlcon t. To check the number of PVC's using the switch CLI use the command: dvc t.

Next, for each node which has grouped connections (as determined from the SV+ database), and not marked as "limit exceeded", SNMP GETNEXT commands are used to obtain all the groups for this node. These include all local (master end) and remote empty groups, and all local (master end) nonempty groups. All empty groups are deleted first, then for each nonempty local (master end) group all PVCs are ungrouped.

For each PVC to be ungrouped, SNMP GET commands are used to obtain all of the current configuration parameters pertaining to the PVC. The SNMP responses received are included in the log file.

Next, an SNMP SET is used to delete the PVC. It is necessary to delete the existing PVC before adding the new PVC in order to free the resources at the other end of the PVC.

Finally, SNMP SETs are used to add the new PVC using all the same parameters as the old PVC. These include end point parameters, class of service, and preferred route.

Once this process has completed for all connections in a given group, that empty group is then deleted.

This process continues for all groups on a given node, and for all nodes.

Limitations

The local and remote loopback states of a connection will not be preserved. All connections will not be in loopback after ungrouping.

If any error occurs while the script is running, an error is printed to the console and logged and the script exits. Corrective action can be taken and the script can be restarted.

Only one script should be run at a time, since running two scripts in parallel might cause one script to stop if it tries to delete a connection or group that was already deleted by the other script.

If the unGroup script is aborted while it is in the process of ungrouping connections, it will attempt to finish ungrouping the current connection it is on before exiting.

If an SNMP error or timeout occurs, it is possible for a connection to be deleted but not re-added. If this situation occurs, all of the information needed to manually rebuild the PVC is contained in the log file.

Statistics Collection Management Application Notes

When installing statistics collection management (SCM) over existing 9.1.X SV+, there are two user procedures to follow to get the correct behavior for SCM autoenable and config files.

SCM Autoenable INSTALL Procedure over existing 9.1.X

The SCM has a master file used to autoenable a switch during stats collection.

In the /usr/users/svplus/statsmgr directory, enable.master.81.stats is a binary file that is sent to the switch when autoenable is invoked. It comes initially set to 60 minute collection and 60 minute buckets for stats and a limited set of statistics for Frame Relay.

During normal operation, when a user selects new stats or different collection intervals, this file is reset to whatever values you have selected in your configuration and setup.

If a user installs a new 9.1.X over an existing environment, the enable file will be overwritten to the defaults. To avoid this, move the enable.master.81.stats file to a temporary file then move it back after install. Or you can bring up the SCM GUI, select the stats as desired, send stats enable to the network, and the enable file will automatically be overwritten by your settings.

SCM stats config Procedure over existing 9.1.X

The SCM has a master file used to setup the selected stats in the user interface.

In the /usr/users/svplus/statsmgr dir, statsenablelist.stats is a ASCII file that is used to initialize the listboxes for stats in the GUI. The file is initially set to a limited set of statistics for Frame Relay.

During normal operation, when a user selects new stats, this file is reset to whatever values you have selected in your configuration and setup.

If you install a new 9.1.X over an existing environment, the file will be overwritten to the defaults supplied on the install file. To avoid this, the you can move the file to a temporary file then move it back after install. Or you can bring up the SCM GUI, select the stats as desired and select the OK button in the window. The file will automatically be overwritten by your settings.

Application Note for Multiple SCM Configuration

Collecting Statistics from the Same Nodes Using Multiple SCMs

There are some users who will be doing redundant file collection, and other users who will be using multiple SCMs to collect files to a common SV+ workstation. The restrictions that are discussed here apply to both configurations. Refer to Figure 3 Multiple Statistics Collection Manager Configuration below.


Figure 3: Multiple Statistics Collection Manager Configuration


There are SV+ WingZ and Parser considerations when using multiple SCMs for TFTP Statistics collection. When you configure a node for TFTP collection, the SCM keeps a copy of the node configuration on the LOCAL SCM workstation.This configuration list is used by WingZ to determine what statistics have been enable/disabled on a given node. In order for WingZ to turn on the statistics enable table, these configuration files are opened and parsed by the SV+ statsenable program, and the database "stat_enable" table updated for that node.

It is recommended that you use a single SCM to enable all TFTP statistics for all nodes in the network. The single SCM should be the SCM that runs on the same workstation as WingZ and SV+.

It also important to note, that the Network Parameters window on the SCM that is running stand-alone contains configuration parameters for the statsParser. Since the SCM is running stand-alone where there is no statsParser or SV+, the Parser parameters will have no effect upon other SCMs running on other machines. If you want to change a statsParser parameter, you must go to the machine where SV+ and the parser are running and configure the parameters appropriately for them to take effect

Auto enable feature in SCM 9.1.X

The auto enable feature is only available in SCM which is running along with SV+ core processes. Stand alone SCM does not have auto enable functionality. The function of auto enable is to do TFTP put stats enable to the nodes which are configured to have stats master SCM as this one. This is done when SCM first starts up. If no stats enable file was sent to a node from this SCM, it will send a default enable.master.81.stats file; otherwise, SCM will send the same stats enable file which was sent by this SCM to that node previously.

The important note for this auto enable feature is that there is no provision to turn this feature off. The side effect is that after the installation of SV+ 9.1.X, for the first time when SCM is run, it will put the default enable.master.81.stats file to all the nodes which are configured to have stats master SCM as this one. In this case, if user does not want default stats, he/she has to again select the stats and send to the nodes.

The other important note for SCM in 9.1.X is that the stand alone SCM uses YP page if ypbind is running otherwise it uses local /etc/hosts file to get the nodes name. On the other hand, SCM which is running with SV+ core processes, gets all the node from topology.

SCM 9.1.X does not support local host or any unix work station as time sync node. User has to select one of the routing node for time sync node.

SCM 9.1.Xallows different groups of nodes to have different bucket intervals, collection intervals and time sync nodes. However, the main window in SCM always displays the most recent settings of network parameters. They are valid for those nodes which were enabled and done start collection, after these parameters were set. To see the collection period, bucket interval and time sync node, user can select a node and apply "Show Collect Info" from node selection window.

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.

Note If you purchased your product from a reseller, you can access Cisco Connection On-line (CCO) as a guest. CCO is Cisco Systems' primary, real-time support channel. Your reseller offers programs that include direct access to CCO's services.

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:

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.

hometocprevnextglossaryfeedbacksearchhelp
Posted: Thu Feb 25 15:25:44 PST 1999
Copyright 1989-1999©Cisco Systems Inc.