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

Table of Contents

Release Notes for Cisco StrataView Plus 9.1.10 for Solaris

Release Notes for Cisco StrataView Plus 9.1.10 for Solaris

These release notes provide information about Cisco StrataView Plus 9.1.10 that has changed since the publication of the supporting 9.1 documentation.

Contents

This release note contains the following sections:

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.

Related Documentation

The following documents, along with these release notes, make up the Cisco StrataView Plus 9.1 documentation set:

About the 9.1.10 Cisco StrataView Plus for Solaris Release

The 9.1.10 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 9.1 version of switch software and introduces the following features:

New Features and Enhancements in Release 9.1.10

None, this release provides bug fixes only.

New Features and Enhancements in Release 9.1.09

WANCV has been enhanced to make clock type x21InvertClock selectable.
The MIB definition for this object is:
x21InvertClock OBJECT-TYPE
SYNTAX INTEGER {
normal(1),
invert(2),
normalDontExpectRcvClk(3),
invertDontExpectRcvClk(4)
}
ACCESS read-write
STATUS mandatory
DESCRIPTION
"This object configures two options:
a) Whether you want to invert the clock sent with the TX data
b) Whether you expect to receive a clock from the other side

normal(1) - a)=dont invert, b)=expect rcv clock
invert(2) - a)=invert, b)=expect rcv clock
normalDontExpectRcvClk(3) - a)=dont invert, b)=dont expect rcv clock
invertDontExpectRcvClk(4) - a)=invert, b)=dont expect rcv clock

Default is normal(1)
"
::= { x21CnfGrpEntry 9 }

The two choices normalDontExpectRcvClk(3), invertDontExpectRcvClk(4) are available on FRSM-HS1 and FRSM-HS1B cards with V.35 backcards in AXIS shelves running 4.0.21, 4.1.05 or later releases.
StrataView connection management system (Connection Manager GUI and connection proxy service agent) have been enhanced to support three new service types for ATM-FR and ATM-ATM connections:
Table 1 lists the details for these services for ATM local cards.

Table 1: Services for
Connection Category SV+ Service Type Remote Card
Group Type 		Limits

ATM-FR

atfst

FR

Local end point should be on a routing node. Remote end point should be on a feeder node.

ATM-FR

atftfst

FR

ATM-FR

atfxfst

FR

ATM-ATM

atfst

ATM

Both end points should be on routine nodes.

ATM-ATM

atftfst

ATM

ATM-ATM

atfxfst

ATM

ATM Local Card Groups
Table 2 lists the cards supported in Frame Relay and ATM card group types listed in Table 1.

Table 2:
Card Group Type Cards in the Card Group

FR

FRSM (4T1,4E1,8T1,8E1), FRM, UFM, FRP

ATM

ASI, ASI-155, BXM, UXM

Card Group Types

New Features and Enhancements in Release 9.1.08

StrataView service agent has been enhanced to support svCeEndPointIdleCodeIntgnPeriod parameter for CE connections. Connection Manager GUI doesn't support this parameter.

New Features and Enhancements in Release 9.1.07

StrataView sub-systems such as Cisco View, Conn Proxy, Port Proxy, and Connection Manager GUI have been enhanced to support V.35 back card for FRSM-HS1B front cards on AXIS shelves, as listed in Table 3.

Table 3:
Connection Category Supported Cards Service Type

ATM-FR

BXM-FRSM

AUSM-FRSM

VBR3

ABRFS

ATM-ATM

BXM-BXM

AUSM-BXM

AUSM-AUSM

ABR1, ABRFS, VBR1, VBR2, VBR3, CBR1, VBR1

Supported Cards and Service Types
StrataView SNMP Proxy Agent and Conn Proxy have been enhanced to support the UPC parameters for ATM-ATM PVCs on AUSM cards listed in Table 4:

Table 4:
Service MIB UPC
Parameter Name 		Description

atmEndPointIBS

Initial Burst Size

atmEndPointVcQSize

Maximum VC queue depth

atmEndPointEfciQSize

The threshold setting used by the explicit congestion notification feature for this end-point's transmit queue

atmEndPointHiCLP

CLP (Cell Loss Priority) tagging activation threshold

atmEndPointLoCLP

CLP (Cell Loss Priority) tagging deactivation threshold

supported UPC Parameters for ATM-ATM PVCs on AUSM Cards
Table 5:
Category SV+ Service Type Local End Point Card Group Type Remote End point Card Group Type Restriction/Comments

ATM-ATM

ABR.FS

UXM/BXM/AUSM

UXM/BXM/AUSM

atmEndPointIBS is not applicable

ATM-ATM

ABR.1

UXM/BXM

UXM/BXM

only with VSVD enabled

atmEndPointIBS is not applicable

ATM-ATM

ABR.1

AUSM

AUSM

atmEndPointIBS is not applicable

ATM-ATM

ATFST

UXM/BXM/AUSM

UXM/BXM/AUSM

ATM-FR

ABR.FS

UXM/BXM/AUSM

FRSM/UFM

atmEndPointIBS is not applicable

ATM-FR

ATFST

UXM/BXM/AUSM

FRSM/UFM

ATM-FR

ABR.FS

UXM/BXM/AUSM

FRP/FRM

Connection is not supported

ATM-FR

ATFST

UXM/BXM/AUSM

FRP/FRM

Connection is not supported

Service Types Supporting UPC Parameters
Maps of China, India, Taiwan, Singapore and Canada have been added to StrataView distribution. These maps can be used and viewed from StrataView topology.

Discontinued Features in Release 9.1.07

Support for CO-FRAD (FRASM) card on Axis shelves has been discontinued in StrataView Plus from release 9.1.07 onwards because support for FRASM cards has been discontinued by the AXIS product group.

New Features and Enhancements in Release 9.1.06

StrataView sub-systems have been enhanced to support 8.2.5X release of IGX software. SV+ 9.1 has already been tested with 8.5.0X release of IGX.
StrataView plus 9.1.06 has been enhanced to support upgrade from StrataView Plus 8.2.5X to 9.1.06 or later versions.
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 gets overwritten during the upgrade. This script saves the files listed in /usr/users/svplus/config/files_to_be_saved file. User can edit this files_to_be_saved file to include all the files that need to be saved, before the upgrade.
StrataView installation and desktop and it's applications have been enhanced to support Common Desktop Environment (CDE) on Solaris platform.
StrataView plus 9.1.06 has been enhanced to provide an option to launch either CV or Equipment Manager GUI for Axis shelves running Release 4.0.
SV+ 9.1.06 has been tested and certified for Year 2000 compliance. This has been done by executing and verifying the 29 test cases in the test suite developed by Cisco for Year 2000 compliance.

Table 6:
Software Release Patch Y2K compliance Certified By Remarks

StrataView Plus

9.1.06 or later

N/A

Cisco Systems 29 Test Case suite

HP OpenView

5.01

PSOV-02091

PSOV_02208

HP

WINGZ

2.5

N/A

IISC

Informix

7.2.3.UC4

N/A

Informix

Solaris OS

2.5.1

Solaris 2.5.1 Recommended Patch Cluster

Dated Jan/14/1999 And

Solaris 2.5.1 Y2000 Patch Cluster Dated Jan/04/1999

Sun Microsystems

These patch clusters can be downloaded from http://sunsolve.sun.com/pub-cgi/us/pubpatchpage.pl

Year 200 Compliance Matrix

New Features and Enhancements in Release 9.1.05

Some Cisco WAN device names have been changed since the publication of SV+ 9.1 documentation. SV+ documentation refers 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.
CiscoView has been enhanced to support releases 8.4.x and 8.5.x of BPX/IGX.
StrataView sub-systems have been enhanced to support up to 40 networks.
SV+ Topology has been enhanced to display IGX8450 nodes.
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.
The CAC functionality from SV+ 9.0 has been rolled up to SV+ 9.1.05 Connection Manager GUI, ConnProxy and PortProxy applications.
Two sample files, CAC_calc.txt.sample and CAC_calc.txt.sample2, are distributed along with SV+ package. These files can be found in the /usr/users/svplus/config directory after installing SV+ 9.1.05 or later software.
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.
Connection Manager GUI has been enhanced to automatically update % Utilization field in the new connection and modify connection windows for ATM-ATM connections, as the values for certain fields are being entered. User can always set, such computed % utilization to the desired value.
For VBR connections, the % utilization field will get automatically updated as the values for PCR(0+1), MCR(0+1), MBS(0+1) fields are being entered.
FOR CBR connections, the % utilization field will get automatically updated as the value for PCR(0+1) field is being updated.
Connection Manager GUI has been enhanced to support CE-ATM type connections.
Note ConnProxy does not support this feature in this release.
Two new traps have been implemented in StrataView Plus. The traps svNodeIpUnreachable (25300) and svNodeUnreachable (25301) have been added to the SV+ Network MIB. These traps are sent by SV+ when the node is reachable (SV+ able to send IP packets node) and when the node is unreachable (SV+ not able to send IP packets to the node).
The KEEP_ALIVE time mechanism of StrataView Plus has been made user-configurable. The following are the details of that change:
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.
Reports for most utilized Trunk/Port/PVC have been added.
Auto-installation scripts and documentation has been enhanced to support one more hardware configuration and to become more user friendly.

New Features and Enhancements in Release 9.1.03

Connection Manager and service agent are enhanced to support STM1 and XLR OC3- 12 port and XLR OC12 - 4 port back cards for BXM front card.
The port traps for UFM card shall include the physical port number. The WRAPPER for UFM line number has been enhanced to populate DataBase with the physical line number (line) in the frp table. The line field for FRM cards on IGX and FRP cards on IPX is stored as 1, if WRAPPER is enabled. Otherwise, it is stored as 0.
Trunk/PVC reports have been enhanced for Peak and Average reports. Peak and Average statistical reports have been added for Port statistics.
Both auto-install and manual install procedures have been enhanced to be less interactive. Installation procedure has been added for stand-alone SCM.
Auto-install has been enhanced to find out whether the hard disk is partitioned or not. If it is not partitioned the only option given is to partition the disks. Auto-install has been improved to give error messages about wrong or unsupported disk configurations.
Manual install has been enhanced to work like auto-install, after the disk configuration is done manually.
Note Grouped Connections are no longer supported in switch software version 9.1 in any manner. 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 management of UXM ports and connections.

Network Limits

The network will allow connections of up to 12 SV+ stations. 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.07 can manage up to 40 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

New Hardware Support

CESM-(8T1/8E1): Connection Manager and service agent are enhanced to support CESM ports, structured and unstructured connections and to support 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.

Hardware Support

Table 7 lists the supported legacy hardware supported in SV+ 9.1.10, including platform, front card, back card, firmware version, and software version.


Table 7: Legacy Hardware Support

Platform Front Card Back Card Firmware Version Software Version

IGX 8400

NPM

SCM

CVJ,CWP

9.1.00 to 9.1.10 or later releases of 9.1

IGX 8400

NTM

BC-T1/E1/SR/Y1

9.1.00 to 9.1.10 or later releases of 9.1

IGX 8400

BTM

AIT-T3/E3/E2/HSS1/E1

AJF,BCF,BDK,BDL

9.1.00 to 9.1.10 or later releases of 9.1

IGX 8400

FRM

FRI-T1/E1/V.35/X.21

9.1.00 to 9.1.10 or later releases of 9.1

IGX 8400

FTM

FPC-V35/T1/E1/X.21

9.1.00 to 9.1.10 or later releases of 9.1

IGX 8400

HDM

SDI V.35/RS-449/RS-232C/RS-232D

CEF

9.1.00 to 9.1.10 or later releases of 9.1

IGX 8400

LDM

LDI RS-2324/RS-2328/RS-232D

9.1.00 to 9.1.10 or later releases of 9.1

IGX 8400

CVM

BC-T1/E1/J1/Y1/SR

AFF,AHF,BHC

9.1.00 to 9.1.10 or later releases of 9.1

IGX 8400

UVM

UVI-2T1EC/2E1EC

9.1.00 to 9.1.10 or later releases of 9.1

IGX 8400

UFM-C

UFI-8T1/8E1-DB15,UFI-8E1-BNC

9.1.00 to 9.1.10 or later releases of 9.1

IGX 8400

UFM-U

UFI-V35/X21/HSI

9.1.00 to 9.1.10 or later releases of 9.1

IGX 8400

ALM-A

BC-UAI-1E3/1T3

9.1.00 to 9.1.10 or later releases of 9.1

IGX 8400

ALM-B

BC-UAI-1T3 /1E3

9.1.00 to 9.1.10 or later releases of 9.1

IGX 8400

ARM

ARI

BA

9.1.00 to 9.1.10 or later releases of 9.1

IGX 8400

UXM

UAI-4OC3MMF/40C3SMF/2OC3SMF/6T3/6E3/3T3/3E3/8T1-IMA/8E1-IMADB15/8E1-IMABNC

AAB,ENW,P0512

9.1.00 to 9.1.10 or later releases of 9.1

BPX 8600

BCC

BCC-bc/3-bc

B0406,BKF,BKJ,BMH,BYJ

9.1.00 to 9.1.10 or later releases of 9.1

BPX 8600

ASM

LM-ASM

AAA,ABA,ACA,BC03

9.1.00 to 9.1.10 or later releases of 9.1

BPX 8600

BNI-T3

LM-3T3

CCJ,CEL,CHD,CHF

9.1.00 to 9.1.10 or later releases of 9.1

BPX 8600

BNI-E3

LM-3E3

CFD,CFF,CLF

9.1.00 to 9.1.10 or later releases of 9.1

BPX 8600

BNI-155

LM-OC3-SMF/SMFLR/MMF

9.1.00 to 9.1.10 or later releases of 9.1

BPX 8600

ASI-1

LM-2T3/2E3,

BDK,BFJ,BXJ

9.1.00 to 9.1.10 or later releases of 9.1

BPX 8600

ASI-155

LM-2OC3-SMF/SMFLR/MMF

CB30,HFA

9.1.00 to 9.1.10 or later releases of 9.1

BPX 8600

BXM-T3/E3

BPX-T3/E3-BC

9.1.00 to 9.1.10 or later releases of 9.1

BPX 8600

BXM-15 5

MMF/SMF/SMFLR-155

DC1,DL1

9.1.00 to 9.1.10 or later releases of 9.1

BPX 8600

BXM-622

MMF/SMF/SMFLR-622

9.1.00 to 9.1.10 or later releases of 9.1

MGX 8220

FRSM-4

DB-15-4T1/4E1, BNC-4E1

2.1.16e

4.0.00 to 4.0.20, 4.1.00 to 4.1.04

MGX 8220

CESM-4

DB-15-4T1/4E1, BNC-4E1

3.0.00

4.0.00 to 4.0.20, 4.1.00 to 4.1.04

MGX 8220

AUSM-4

DB-15-4T1/4E1, BNC-4E1

model-A 2.0.01

4.0.00 to 4.0.20, 4.1.00 to 4.1.04

MGX 8220

FRSM-8

RJ48-8T1/8E1, SMB-8E1

4.0.00 to 4.0.20, 4.1.00 to 4.1.04

MGX 8220

AUSM-8

RJ48-8E1/8T1

4.0.00 to 4.0.20, 4.1.00 to 4.1.04

MGX 8220

CESM-8

RJ48-8T1/8E1, SMB-8E1

4.0.00 to 4.0.20, 4.1.00 to 4.1.04

MGX 8220

IMATM-B

RJ48-T3T1/E3E1/E3T1/T3E1

4.0.00 to 4.0.20, 4.1.00 to 4.1.04

MGX 8220

FRSM-HS1

HSI-4X21/3HSSI/V.35

4.0.00 to 4.0.20, 4.1.00 to 4.1.04

MGX 8220

BNM-T3/E3

T3E3-B/D

4.0.00 to 4.0.20, 4.1.00 to 4.1.04

MGX 8220

BNM-155

155-SMF

4.0.00 to 4.0.20, 4.1.00 to 4.1.04

MGX 8220

SRM

DB-15-T1/E1, LM-3T3

4.0.00 to 4.0.20, 4.1.00 to 4.1.03

MGX 8220

ASC

ASC-LM

4.0.00 to 4.0.20, 4.1.00 to 4.1.04

Connection Types Supported

This section lists the connection types supported in Strataview Plus.


Table 8:
Features Supported Feature Requirements Local endpoint Card Group Type Remote endpoint Card Group Type

Choice of ForeSight Feature

No QOS support

FR

FR

ForeSight Enabled for QOS types ubr and abr

Following QOS specified by `ChanServType' attribute on FRSM-VHS SM: hi_priority, ubr,nrt-vbr,rt-vbr, abr

FRQOS

FR, FRQOS

FR-FR Connections for FR and FRASM Port Types
Table 9:
SV+ Service Type Port Types Features Local endpoint Card Group Type Remote endpoint Card Group Type Restrictions

NRT-VBR3

ABR.FS

Choice of FrameRelay and FRASM port types

No QOS support on FR endpoint

ATM

FR

abr.fs not supported with ATM SM - PXM.

CBR,
UBR1
UBR2
NRT-VBR2
NRT-VBR3

ABR.FS

UBR1

UBR2

Choice of FrameRelay port types

QOS supported on FR endpoint

ATM

FRQOS

RT-VBR2

RT-VBR3

Choice of FrameRelay port types

QOS supported on FR end point

ATM

FRQOS

The `real time' feature should be supported by the network and ATM SM. abr.fs not supported with PXM.

ABRFS
VBR3

Choice of FrameRelay port types

No QOS support on FR endpoint

ATM

FR

ABRFS

VBR3

Choice of FrameRelay port types

QOS support on FR endpoint

ATM

FRQOS

ATM-FR Connections
Table 10:
SV+ Service Type ForeSight Features Local endpoint Card Group Type Remote endpoint Card Group Type Restrictions

CBR1, VBR1, VBR2, VBR3, UBR1, UBR2, ABR1, ABR.FS

abr.fs only

ATM

ATM

rt-vbr available only if both network and SMs support `rt' feature.No ForeSight supported with cbr and with PXM cards.

VBR1, VBR2, VBR3

No

ATM

ATM

The `real time' feature should be supported by the network and ATM SMs.

CBR1, VBR1, VBR2, VBR3, UBR1, UBR2, ABR.1, ABR.FS

abr.fs only

Multicast Connection

ATM-Multicast

ATM-Multicast

Local-Remote Port combinations: root-root, root-leaf

NRT-VBR3

No

One or Both endpoints Router Service Modules.

ATM

ATM/RPM

ATM-ATM Connections
Table 11:
Connection Type SV+ Service Classification Local endpoint Card Group Type Remote endpoint Card Group Type Restrictions

CE-CE

CBR

Structure or Unstructured

CE

CE

Both endpoints must be either structured or both unstructured and match bandwidth and interface type.

ATM-CE

CBR

CE Structured or Unstructured

ATM endpoint bandwidth must be equal to or greater than CE endpoint bandwidth

Data-Data

none

Data SM

Data SM

Connection Routing Path cannot include BPX nodes

Voice-Voice

none

Voice SM

Voice SM

Connection Routing Path cannot include BPX nodes

Other Supported Connections

Policing Support

The endpoint Policing Parameter in the strata.mib is atmEndptPolicing. This parameter specifies the traffic policing for the ATM endpoint. The following table provides


Table 12:
Policing Type 1st Bucket 2nd Bucket

vbr.1

CLP(0+1)

CLP(0+1)

vbr.2

CLP(0+1)

CLP(0)

vbr.3

CLP(0+1)

CLP(0) with CLP Tagging

pcrplc

CLP(0+1)

none

none

none

none

ATM endpoint Policing Parameter Restrictions

ATM endpoint policing is applicable only to the following connection types:

The following service types support policing:
Table 13: Service Types Supporting Policing
Category SV+ Service Type Local endpoint Card Group Type Remote endpoint Card Group Type Value of Policing Comments

ATM-ATM

CBR.1

ATM

ATM

pcrplc(4)

ATM-FR

CBR.1

ATM

FR

pcrplc(4)

not in 9.1

ATM-ATM

VBR.1

ATM

ATM

vbr1(1)

ATM-ATM

RTVBR1

ATM

ATM

vbr1(1)

not in 9.1

ATM-ATM

VBR2

ATM

ATM

vbr2(2)

ATM-ATM

RTVBR2

ATM

ATM

vbr2(2)

not there in 9.1

ATM-FR

VBR2

ATM

FR

vbr2(2)

not there in 9.1

ATM-FR

RTVBR2

ATM

FR

vbr2(2)

not there in 9.1

ATM-ATM

VBR3

ATM

ATM

vbr3(3)

ATM-ATM

RTVBR3

ATM

ATM

vbr3(3)

not there in 9.1

ATM-FR

VBR3

ATM

FR

vbr3(3)

ATM-FR

RTVBR3

ATM

FR

vbr3(3)

not there in 9.1

ATM-ATM

ABR.FS

ATM

ATM

vbr3(3)

ATM-FR

ABR.FS

ATM

FR

vbr3(3)

ATM-ATM

ABR.1

ATM

ATM

Can be set to any value between 1 and 5 for ASI family ASI, BXM, BME, UXM

VSVD enabled

ATM-ATM

ABR.1

ATM

ATM

not set

VSVD not enabled

ATM-ATM

ATFST

ATM

ATM

Can be set to any value between 1 and 5 for ASI family

not there in 9.2

ATM-FR

ATFST

ATM

FR

Can be set to any value between 1 and 5 for ASI family

not there in 9.2

ATM-FR

ATFTFST

ATFXFST

ATM

FR

vbr3(3)

not there in 9.2

ATM-ATM

ATFTFST

ATFXFST

ATM

ATM

vbr3(3)

not there in 9.2

UPC Parameters Support

UPC parameters can be specified only through the Proxy, not through Connection Manager GUI. If a connection is added from the Connection Manager GUI, default UPC parameter values are used. If a connection is modified from the Connection Manager GUI, UPC parameters remain unchanged. Table 14 provides the Service MIB UPC parameters and their description.


Table 14:
UPC Parameter Description

atmEndPointIBS

Initial Burst Size

atmEndPointVcQSize

Maximum VC queue depth

atmEndPointEfciQSize

The threshold setting used by the explicit congestion notification feature for this endpoint's transmit queue

atmEndPointHiCLP

CLP (Cell Loss Priority) tagging activation threshold

atmEndPointLoCLP

CLP (Cell Loss Priority) tagging deactivation threshold

ATM UPC Parameters
Table 15: UPC ATM endpoint Parameters
ATM endpoint UPC Parameter Column Used in Table 16

VcQ Depth

1

EfciQSize

2

IBS

3

CLP Hi

4

CLP Lo

5

Oe Vc Depth

6

Oe EfciQSize

7

Oe IBS

8

Oe CLP Hi

9

Oe CLP Lo

10


Table 16: Service Types Supporting UPC Parameters
Category SV+ Service Type Local endpoint
Card Group Type 		Remote endoint
Card Group Type 		1 2 3 4 5 6 7 8 9 1
0

ATM-ATM

ABR.FS

UXM/BXM

UXM/BXM

x

x

x

x

x

x

x

x

ATM-ATM

ABR.FS

AUSM

AUSM

x

x

x

x

x

ATM-ATM

ABR.1 with

VSVD

enabled

UXM/BXM

UXM/BXM

x

x

x

x

x

x

x

x

ATM-ATM

ABR.1 with VSVD disabled

Any ATM

Any ATM

ATM-ATM

ABR.1

AUSM

AUSM

x

x

x

x

x

ATM-ATM

ATFST

UXM/BXM

UXM/BXM

x

x

x

x

x

x

x

x

x

x

ATM-ATM

ATFST

AUSM

AUSM

x

x

x

x

x

ATM-FR

ABR.FS

UXM/BXM

FRSM/UFM

x

x

x

x

x

x

x

x

ATM-FR

ABR.FS

AUSM

FRSM/UFM

x

x

x

x

x

ATM-FR

ATFST

UXM/BXM

FRSM/UFM

x

x

x

x

x

x

x

x

x

x

ATM-FR

ATFST

AUSM

AUSM

x

x

x

x

x

ATM-FR

ABR.FS

UXM/BXM

FRM/FRP (Feeder)

x

x

x

x

x

x

x

x

ATM-FR

ABR.FS

AUSM

FRM/FRP (Feeder)

x

x

x

x

x

ATM-FR

ATFST

UXM/BXM

FRM/FRP (Feeder)

x

x

x

x

x

x

x

x

x

x

ATM-FR

ATFST

AUSM

FRM/FRP (Feeder)

x

x

x

x

x

ATM-FR

ABR.FS

UXM/BXM

FRM/FRP (Routing and NIW)

x

x

x

x

x

x

x

x

x

x

ATM-FR

ATFST

AUSM

FRP/FRM (Routing and NIW)

x

x

x

x

x

ATM-FR

ABR.FS

UXM/BXM/AUSM

FRP/FRM (Routing and SIW)

x

x

x

x

x

ATM-FR

ATFST

UXM/BXM/AUSM

FRP/FRM (Routing and SIW)

New Applications

Reports

This is a new application which displays pre-defined reports in graphical form. A new icon is created in the SV+ Desktop to launch this application. It depends on SCM to collect statistics and populate the Informix database with the required statistics. Please make sure that required statistics are enabled. SV+ Operational Guide gives the details of required statistics.

Ungrouping Grouped Connections Tool

Use this tool to ungroup grouped connections in switch software 8.2.5, 8.4 and 8.5 prior to upgrading to switch software 9.1. Switch software 9.1 does not support grouped connections. All grouped connections need to be ungrouped before doing switch software upgrades to 9.1.

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.07 as standard platforms. They are low-end, mid-range and high-end platforms. The configuration of each platform type is listed in Table 17. Other equivalent platforms running Solaris 2.5.1 are also supported.


Table 17: Sun Platform Requirements

Platform Type Machine Type Number of CPU/MHz processor Amount of RAM Graphics Card Hard Disk Drive Required 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 MB

24 bits

Two 2 GB drives or one 4 GB drive

512 MB

n < 5

m < 5,000

Mid Range option 1

Sun Ultra Enterprise 2 Model 2300 or Ultra 30 model 300

1/300

512 MB

24 bits

Two 4 GB drives

1 GB

5 =< n < 10

5,000 =< m < 25,000

Mid Range option 2

Sun Ultra Enterprise 2 Model 2300 or Ultra 60

2/300

512 MB

24 bits

Two 4 GB drives

1 GB

5 =< n < 10

25,000 =< m < 50,000

Mid Range option 3

Sun Ultra Enterprise 2 Model 2300 or Ultra 60

2/300

1 GB

24 bits

Two 4 GB drives

2 GB

5 =< n < 10

50,000 =< m < 100,000

High End

Sun Enterprise 4000 or Enterprise 450

minimum 4/300

1 GB

24 bits

Two 4 GB drives and disk array

2 GB

n >= 10

m >= 100,000

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

The following are additional notes for SV+ platform requirements:

Note If Low End SV+ system is used for mid/large range networks, following problems may be observed.
SV+ Performance Degradation

StrataView plus may take a long time to sync up with the network. Connection Management and Equipment Management (CiscoView and Equipment Manager GUI) may take a long time to come up or perform any user-requested functions. You may not be able to invoke, multiple number of Desktops from StrataView as certified by Cisco for low end systems.

StrataView plus may drop traps generated by the network, which may put StrataView plus DB out of sync with the network and the information about nodes/trunks/ports/PVCs may not match with the status on the network.

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 18. Other equivalent platforms running Solaris 2.5.1 are also supported.


Table 18: Stand-Alone SCM Platform Requirements

Platform Type Machine Type Number of CPUs Amount 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.07 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

This section lists issues you should be aware of when using Cisco StrataView Plus 9.1.07.

Installation

Make sure at least 750 MB of disk space in /usr/users/svplus area can be allocated for SV+ 9.1.07 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.07 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.

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.07. After installing, contact Wingz for a runtime license and blend it with SV+ 9.1.07. 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. The following upgrades are not supported in this version (9.1.07):

The SV+ 8.2 or 8.4 or SV+ 9.0 to SV+ 9.1 upgrade is 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 synchronize 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 per second units to 100 bits per second units.

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 1and Figure 2, F1, F2 are feeder shelves, and S1 and 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 there in SV+ database. After S1 becomes reachable, configuration changes will be sent to StrataView and StrataView database will be updated with the middle segment details. You can delete the incomplete connection at this time, using StrataView.
However, if F1 (or F2) is Axis shelf and it becomes unreachable after receiving add connection segment request, SV+ doesn't get updated with the end segment details, even if the node becomes reachable. The database update happens whenever the next periodic Node Resync by SV+ happens 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 database, even if the node becomes reachable. The database update happens whenever the next periodic Node Resync by SV+ happens with that shelf.
The above situation occurs only in the second SV+ station when two SV+ stations are used to manage the same network and the first station is used for PVC provisioning. This database inconsistency occurs only during a small window, when the second station discovers the PVC added by first SV+ station by means of node messages or SNMP traps.

Network Configuration

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

Each IPX/BPX/IGX/MGX 8220 node to be managed by StrataView Plus must be configured with an IP Relay IP Address (cnfnwip). The gateway node must be configured with both LAN and IP Relay IP Addresses.

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

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

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 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 PVCs 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 reserve only 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 you perform 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, do the following:

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

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

While SV+ is running, if remote display is killed without properly shutting down the SV+ Desktop, 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

It may occasionally 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+ Image Download 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+ Image Download 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 you are running another Network Manager which uses port number 8161, this UDP port can be configured to some other port number in this file as follows:

Syntax:
TRANSPORT special SNMP
OVER UDP SOCKET
AT PORT 8161

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

Syntax:
GET_COMMUNITY public
SET_COMMUNITY private

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

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 patch is required for HPOV: PSOV_02243. This patch is supplied on the SV+ 9.1.07 CD. If HP OpenView is installed on the system, PSOV_02243 is installed during SV+ 9.1.07 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 axis.mib in SV+ 9.1.08.

Changes from axis.mib release 4.0.18 to 4.0.19.

Changes from axis.mib release 4.0.19 to 4.0.20/4.1.04.

egrQCLPThreshLow, egrQEfciThresh in ausmPortCnfServiceQueGrpTable.

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

Valid range for CESM-8T1 structured port: 25-47
Valid range for CESM-8T1 unstructured port: 33-47
Valid range for CESM-8E1 structured port: 20-47
Valid range for CESM-8E1 unstructured port: 33-47
ICR cannot be set for ASI Card for ABR1.
The minimum for UXM on IGX is 7 and for ASI, BXM, BNI on BPX is 0.
On BPX, if the service type is abr-1 (standard ABR connections), the value range of this object should be (0 to 32768) and the value should be in '2 to the power n'
On BPX, if the service type is abr-fs, the unit is in percentage (1%-100%).
Get Operation
Since this object is not applicable to disabled protocol, (-1) is returned if the network manager attempts to GET this object from a port without protocols.
Set Operation
If the network manager attempts to SET this object of a port without any protocol, an error is reported. Not setable on ports without any protocol.
svAtmPortlcpCellsPeriodicity
svAtmPortTxAvailCellRate
svAtmPortSymmetry
svAtmPortMinNumRxLinks
svAtmPortNeTxClkMode
svAtmPortNumRxCfgLnks,
svAtmPortTestLinkIfIndex
svAtmPortTestPattern
svAtmPortTestProcStatus
svAtmPortIntegrationUpTime
svAtmPortIntegrationDownTime
svAtmPortMinNumTxLinks
svAtmPortnumLinksPresentInImaGroup
svAtmPortimaArbitrationWinner
svAtmPortremoteImaId
svAtmPortlocImaId
svAtmPortimaObsDiffDelay
svAtmPortOversubscribed
svAtmPortRxAvailCellRate
svAtmPortFeState
svAtmPortFailureStatus
svAtmPortFeTxClkMode
svAtmPortTxTimingRefLink
svAtmPortRxTimingRefLink
svAtmPortRxFrameLength
svAtmPortLeastDelayLink
svAtmPortNumRxActLnks
svAtmPortNeState

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

Database Changes

The section provides a summary of changes to the SV+ database defintions with new tables and additions to existing database definition tables.

The following columns were added to the database from 9.1.06 to 9.1.07:


Table 19: AUSM_PORT

Column Name Unique
Identifier Field 		Data
Type 		Description

min_rx_links

no

short

Minimum number of receive links required to be active for IMA group to be in the UP state

min_tx_links

no

short

Mimimum number of transmit links required to be active for IMA group to be in the UP state

ima_symmetry

no

short

Symmetry of IMA Group.

New Database Tables

This section lists tables that were not in the 8,4 and 9.0 releases of Cisco StrataView Plus.

VOICE_CHANNEL describes a new database table that was not in the SV+ 8.4.


Table 20: VOICE_CHANNEL
Column Name Unique Identifier Field Data Type Description

chnl_obj_id

Yes

int

Voice channel Object ID.

l_node_id

Yes

int

Cisco SV+ node ID.

1_slot

short

Slot number.

l_line

short

Port number.

l_chnl

short

Channel number.

per_util

short

Percent utilization (0 - 100).

cos

short

Class of service.

eia

short

EIA rate (0 - 20).

dfm_len

short

DFM length (0, 1, 7, 8, 16).

chnl_info

short

Data channel info:
Bit7-6: spare

Bit5: OCU: 0 = reset, 1 = Set

Bit4: DS0A, UCS: 0 = reset, 1 = Set

Bit3: DTE: 0 = DCE, 1 = DTE

Bit2-1: Clocking: 0 = normal, 1 = split, 2 = looped

Bit0: DFM flag: 0 = Off, 1 = On

input_loss

short

Input loss.

output_loss

short

Output loss.

onhook_ab

short

Onhook AB:
Bit7-5: Onhook A: 0 = 0, 1 = 1, 2 = don't care, 3 = unknown, 4 = not used.

Bit4-2: Onhook B: 0 = 0, 1 = 1, 2 = don't care, 3 = unknown, 4 = not used.

Bit1-0: Dial type: 0 = Inband, 1 = pulse, 2 = User Dial.

onhook_cd

short

Onhook CD:
Bit7-5: Onhook C: 0 = 0, 1 = 1, 2 = don't care, 3 = unknown, 4 = not used.

Bit4-2: Onhook D: 0= 0, 1 = 1, 2 = don't care, 3 = unknown, 4 = not used.

Bit1: Sig Inject.

BIt0: Sig Extract.

chnl_type

short

Channel type.

cndt_crtr_indx

short

Conditioning criterion index.

tx_ab_sgnl

short

Transmit AB signalling:
(This applies to Tx/Rcv XY sig)

Bit7-5: Tx/Rcv X signalling

Bit4-2: Tx/Rcv Y signalling

0=sig. bit is 0, 1= sig. bit is 1, 2=tx sig. bit transparently, 3=don't tx sig. bit, 4=Reverse/Inverse sig. bit.

Bit1=0: Spare

tx_cd_sgnl

short

Transmit CD signalling.

Same as tx_ab_sgnl.

rcv_ab_sgnl

short

Receive AB signalling (same as tx_ab_sgnl).

rcv_cd_sgnl

short

Receive CB signalling (same as tx_ab_sgnl).

sgnl_intgr_time

short

Signalling integration time(ms).

min_wink

int

Minimum wink (ms) (100 - 300).

playout_delay

short

Playout_delay (120 - 200).

iec

short

IEC parms:
Bit7: echo cancel: 0 = Disabled, 1 = Enabled
Bit6: non-linear proc: 0 = Disabled, 1 = Enabled
Bit5: conv.: 0 = Disabled, 1 = Enabled
Bit4: echo return loss: 0 = Low, 1 = High
Bit3: tone disabler: 0 = Disabled, 1 = Enabled
Bit2: bkcd prefer: 0 = Disabled, 1 = Enabled
Bit1: bkgnd filter: 0 = Disabled, 1 = Enabled
Bit0: spare.

DATA_CHANNEL describes a new database table that was not in the SV+ 8.4.


Table 21: DATA_CHANNEL
Column Name Unique Identifier Field Data Type Description

chnl_obj_id

yes

int

Data channel Object ID.

l_node_id

yes

int

Cisco SV+ node ID.

1_slot

short

Slot number.

l_line

short

Line number.

l_channel

short

Channel number.

per_util

short

Percent utilization (0 - 100).

cos

short

Class of service.

eia

short

EIA rate (0 - 20).

dfm_len

short

DFM length (0, 1, 7, 8, 16).

chnl_info

short

Data channel info:
Bit7-6: spare.
Bit5: OCU: 0 = reset, 1 = Set.
Bit4: DS0A, UCS: 0 = reset, 1 = Set.
Bit3: DTE: 0 = DCE, 1 = DTE.
Bit2-1: Clocking: 0 = normal, 1 = split, 2 = looped.
Bit0: DFM flag: 0 = Off, 1 = On.

../../../../../../../../home/home.htm describes a new database table that was in neither SV+ 8.4 nor SV+ 9.0.


Table 22: PROTOCOL_GROUP

Column Name Unique Identifier Field Data Type Description

node_id

Yes

int

Cisco SV+ node ID.

slot

Yes

short

Slot number.

type

Yes

short

Protocol type:
STUN 1
BSTUN 2

group

Yes

short

Group number.

config_type

short

Config type:
sdlc 1
sdlctg 2
bsc 3

local_ack

short

Local ack flag:
disabled 1
enabled 2

state

short

Operational status:
inactive 1
active 2

LINK_STATION describes a new database table that was in neither SV+ 8.4 nor SV+ 9.0.


Table 23: LINK_STATION

Column Name Unique Identifier Field Data Type Description

obj_id

Yes

int

Object ID.

node_id

Yes

int

Cisco SV+ node ID.

slot

short

Slot number.

line

short

Line number.

port

short

Port number.

logical_port

short

Logical port number.

address

short

Address.

mac_address

char (15)

Physical address. It is 6 bytes in hex as format "0000.0000.0000".

max_frame

short

Maximum size of a frame on this station. Value is given in bytes.

xid

int

XID value to be exchanged for this station.

state

short

operational status:
disconnect 1
discpend 2
snrmseen 3
error 4
xidsent 5
xidstop 6
snrmsent 7
connect 8
thembusy 9
usbusy 10
bothbusy 11

CHANNEL_ROUTE describes a new database table that was in neither SV+ 8.4 nor SV+ 9.0.


Table 24: CHANNEL_ROUTE

Column Name Unique Identifier Field Data Type Description

obj_id

Yes

int

Object ID.

node_id

Yes

int

Cisco SV+ node ID.

slot

short

Slot number.

line

short

Line number.

port

short

Port number.

logical_port

short

Logical port number.

dlci

short

DLCI number.

lcn

short

Logical channel number.

address

short

Station address number (for BSTUN, it is CU address. For FRASBAN, it is route ID. For others, it is Link Station address).

type

short

Route type:
STUN 1
BSTUN 2
FRASBNN 3
FRASBAN 4

lsap

short

The LSAP used to differentiate between tunnels on this DLCI (for STUN/BSTUN/FRAS-BNN only).

rsap

short

The RSAP used to differentiate between connections on this DLCI (for FRAS-BNN only).

th_type

short

th_type (for FRASBNN only):

none 1
pfid 2
afid 10
fid4 4

bni

char (15)

The BNI used for this BAN addressing scheme. It is 6 bytes in hex as format "0000.0000.0000" (for FRAS-BAN only).

state

short

operational status:
inactive 1
active 2

STATION_DATA describes a new database table that was in neither SV+ 8.4 nor SV+ 9.0.


Table 25: STATION_DATA

Column Name Unique Identifier Field Data Type Description

timestamp

Yes

integer

Time stamp.

l_node_id

Yes

integer

Node ID.

stn_obj_id

Yes

integer

Station Object ID.

stat_type

Yes

short

Statistics Type.

bucket_type

Yes

short

Bucket interval in minutes.

totald

float

Total count.

peak

float

Peak count.

Database Schema Changes from SV+ 8.4

This section lists new entries in the SV+ 9.1 database tables that were not in the SV+ 8.4 database tables.


Table 26: Database Schema Changes from SV+ 8.4

Table Column Name Unique Identifier Field Data Type Description

PACKET_LINE

l_num_phy_line

short

Local number of physical lines:
-1 for trunks not having physical lines.
(1 for Normal and virtual trunks having physical lines)
2-8 for IMA trunks.
Default value for upgrade to SV+ 9.1 is -1

PACKET_LINE

r_num_phy_line

short

Remote number of physical lines:
-1 for trunks not having physical lines.

1 for normal and virtual trunks having physical lines.

2 to 8 for IMA Trunks.

Default value for upgrade to SV+ 9.1 is -1.

CIRCUIT_LINE

l_port

short

Local-end logical port number.

CIRCUIT_LINE

line_info

short

line info flag:
bit7-3: spare

bit2-Coding: 0=U-law, 1=A-law

bit1-CAS: 0=FALSE, 1=TRUE

bit0-CCS: 0=FALSE, 1=TRUE

FRP

elmi

short

1 = ELMI enabled

-1 = ELMI disabled or this field is not applicable.

This field was earlier used only for Axis nodes.

Beginning with Cisco SV+ version 9.1, it is also used for IGX.

FRP

subrate_speed

short

Port subrate speed (for FRASM only):
1 = speed2400
2 = speed4800
3 = speed9600
4 = speed56000
5 = speed64000

FRP

interface

short

Port interface (for FRASM only): ds0, ds0a or ds0b.

FRP

encoding

short

Port encoding: nrz or nrzi (for FRASM only).

FRP

role

short

Port role: primary, secondary or negotiable (for FRASM only).

FRP

max_frame

short

Maximum number of bits expected in an inbound frame (for FRASM SDLC port only).

FRP

retry_cnt

short

Number of retry attempts (for FRASM SDLC and BSC port only).

FRP

ack_wait_time

int

Number of milliseconds the software waits for an ack before attempting recovery (for FRASM SDLC port only).

FRP

vmac

char (15)

Virtual mac address for BAN group addressing. It is 6 bytes in hex. The format is "0000.0000.0000" (for FRASM SDLC port only).

FRP

poll_cycle

short

Number of 1/10 of a second intervals to wait between the start of a polling cycle (for FRASM BSC port only).

FRP

poll_intv

short

Number of 1/10 second intervals between polls (for FRASM BSC port only).

FRP

group

short

Protocol group number (for FRASM STUN or BSTUN port only).

USER_CONNECTION

l_rate_type

short

Local rate type (for voice/data connections only):
Rate type: (0-13).
Set to -1 for other connection types.

USER_CONNECTION

l_rate_fctr

short

Local rate factor (for data connections only):
Rate factor: (1-8).
Set to -1 for other connection types.

USER_CONNECTION

l_smpl_per_pckt

short

Local sample per packet (for data connections only).
Sample per packet: (1, 2, 4, 5,10).
Set to -1 for other connection types.

USER_CONNECTION

r_rate_type

short

Remote rate type (for voice/data connections only).
Rate type: (0-13).
Set to -1 for other connection types.

USER_CONNECTION

r_rate_fctr

short

Remote rate factor (for data connections only).
Rate factor: (1-8).
Set to -1 for other connection types.

USER_CONNECTION

r_smpl_per_pckt

short

Remote sample per packet (for data connections only).
Sample per packet: (1,2,4,5,10).
Set to -1 for other connection types.

USER_CONNECTION

l_cbr_clock_mode

short

Local end CBR clock mode - CESM.
Values:
synchronous (1)
srts (2)
adaptive (3)

USER_CONNECTION

l_cas

short

Local end signalling pass - CESM.
Values:
basic (1)
e1Cas (2)
ds1SfCas (3)
ds1EsfCas (4)
ccs (5)

USER_CONNECTION

l_partial_fill

short

Local end partial fill - CESM.

Value range: 0-47

USER_CONNECTION

l_idle_detection

short

Local end idle detection - CESM-8.

Values: disable (1) and onhook (2).

USER_CONNECTION

l_onhook_code

short

Local end onhook code - CESM-8.

Values range: 0-15.

USER_CONNECTION

l_idle_suppression

short

Local end idle suppression - CESM-8.
Values: disable (1) and enable (2).

USER_CONNECTION

r_cbr_clock_mode

short

Remote end CBR clock mode - CESM.
Values:
synchronous (1)
srts (2)
adaptive (3)

USER_CONNECTION

r_cas

short

Remote end signalling pass - CESM.

Values:
basic (1)
e1Cas (2)
ds1SfCas (3)
ds1EsfCas (4)
ccs (5)

USER_CONNECTION

r_partial_fill

short

Remote end partial fill - CESM.
Value range: 0-47

USER_CONNECTION

r_idle_detection

short

Remote end idle detection - CESM-8.
Values: disable (1) and onhook (2).

USER_CONNECTION

r_onhook_code

short

Remote end onhook code - CESM-8.
Values Range: 0-15.

USER_CONNECTION

r_idle_suppression

short

Remote end idle suppression - CESM-8.
Values: disable (1) and enable (2).

USER_CONNECTION

l_mc_type

short

Local multicast type flag (for multicast connections). The values are normal (0), root (1) and leaf (2).

USER_CONNECTION

r_mc_type

short

Remote multicast type flog (for multicast connections).
Values are as per local multicast type flag.

USER_CONNECTION

l_end_nni

short

-1: unknown port type.
1: nni port type.
0: non nni port type.

USER_CONNECTION

r_end_nni

short

-1: unknown port type.
1: nni port type.
0: non nni port type.
For incomplete PVC, this field is always -1 (unknown).

CONNECTION

rate_type

short

For voice/data connections only:
Rate type: (0-13)
Set to -1 for other connection types.

CONNECTION

rate_fctr

short

For data connections only:
Rate factor: (1-8)
Set to -1 for other connection types.

CONNECTION

smpl_per_pckt

short

For data connections only:
Sample per packet: (1, 2, 4, 5, 10). Set to -1 for other connection types.

CONNECTION

retry_cnt

short

Number of retry attempts before declaring failure (for FRASM llc port only).

CONNECTION

ack_wait_time

int

Number of millisecond intervals the implementation waits before resending unacknowledged information frames (for FRASM llc port only).

ATM_CONNECTION

mc_type

short

Multicast type:
Normal (0)
Root (1)
Leaf (2)

ASI_LINE

l_trk

short

Logical Trunk number for trunks having physical lines. For non physical lines it is -1. Default value for upgrade to Cisco SV+ 9.1 is -1.

ASI_LINE

l_vtrk

short

When trunks have physical lines and it is a virtual trunk, it contains the virtual trunk number, otherwise it is -1. Default value for upgrade to Cisco SV+ 9.1 is -1.

ASI_LINE

l_line

short

Physical line number. This is unique per card. For example, when physical lines are 2, 3 for one trunk and 6, 7 for another trunk on the same card, this field is 2, 3 for the first trunk and 6, 7 for the second trunk. For non physical lines it is -1. Default value for upgrade to Cisco SV+ 9.1 is -1.

CARD

fc_fab_num

char (21)

Front card FAB number.

AUSM_PORT

ima_symmetry

short

Symmetry of the IMA group; not modifiable after create. Asymmetric Operation and Asymmetric Configuration are not supported. ATM Forum compliant IMA ports only.

AUSM_PORT

min_tx_links

short

Minimum number of transmit links required to be active for the IMA group to be in the Up state.Eventhough the range is 1..8, this value should be <= maximum number of configured links in IMA group. ATM Forum compliant IMA ports only.

AUSM_PORT

min_rx_links

short

Minimum number of receive links required to be active for the IMA group to be in the Up state.At present, since only symmetric configuration is supported, this should be equal to axisImaGroupMinNumTxLinks. ATM Forum compliant IMA ports only.

CESM_CONNECTION

l_line

short

Local line number.

CESM_CONNECTION

r_line

short

Remote line number.

CESM_CONNECTION

cbr_clock_mode

short

Specifies clocking mode of the CBR service:
Values:
synchronous (1)
srts (2)
adaptive (3)

CESM_CONNECTION

cas

short

Specifies when CAS bits are carried by the service.
Values:
basic (1)
e1Cas (2)
ds1SfCas (3)
ds1EsfCas (4)
ccs (5)

CESM_CONNECTION

partial_fill

short

Number of user octets per cell, when partial cell fill is used.
Value range: 0-47

CESM_CONNECTION

idle_detection

short

Idle Detection (CESM-8).
Values: disable (1) and onhook (2).

CESM_CONNECTION

onhook_code

short

Onhook Code (CESM-8).
Value Range: 0-15

CESM_CONNECTION

idle_suppression

short

Idle Suppression (CESM-8).
Values: disable (1) and enable (2).

CESM_CONNECTION

cbr_clock_mode

short

Specifies clocking mode of the CBR service:
Values:
synchronous (1)
srts (2)
adaptive (3)

Database Schema Changes from SV+ 9.0

This section lists new entries in the SV+ 9.1 database tables that were not in the SV+ 9.0 database tables.


Table 27: Database Schema Changes from SV+ 9.0

Table Column Name Unique Identifier Field Data Type Description

PACKET_LINE

l_num_phy_line

short

Local number of physical lines:
-1 for trunks not having physical lines.
(1 for Normal and virtual trunks having physical lines)
2-8 for IMA trunks.
Default value for upgrade to SV+ 9.1 is -1

PACKET_LINE

r_num_phy_line

short

Remote number of physical lines:
-1 for trunks not having physical lines.

1 for normal and virtual trunks having physical lines.

2 to 8 for IMA Trunks.

Default value for upgrade to SV+ 9.1 is -1.

FRP

subrate_speed

short

Port subrate speed (for FRASM only):
1 = speed2400
2 = speed4800
3 = speed9600
4 = speed56000
5 = speed64000

FRP

interface

short

Port interface (for FRASM only): ds0, ds0a or ds0b.

FRP

encoding

short

Port encoding: nrz or nrzi (for FRASM only).

FRP

role

short

Port role: primary, secondary or negotiable (for FRASM only).

FRP

max_frame

short

Maximum number of bits expected in an inbound frame (for FRASM SDLC port only).

FRP

retry_cnt

short

Number of retry attempts (for FRASM SDLC and BSC port only).

FRP

ack_wait_time

int

Number of milliseconds the software waits for an ack before attempting recovery (for FRASM SDLC port only).

FRP

vmac

char (15)

Virtual mac address for BAN group addressing. It is 6 bytes in hex. The format is "0000.0000.0000" (for FRASM SDLC port only).

FRP

poll_cycle

short

Number of 1/10 of a second intervals to wait between the start of a polling cycle (for FRASM BSC port only).

FRP

poll_intv

short

Number of 1/10 second intervals between polls (for FRASM BSC port only).

FRP

group

short

Protocol group number (for FRASM STUN or BSTUN port only).

USER_CONNECTION

l_cbr_clock_mode

short

Local end CBR clock mode - CESM.
Values:
synchronous (1)
srts (2)
adaptive (3)

USER_CONNECTION

l_cas

short

Local end signalling pass - CESM.
Values:
basic (1)
e1Cas (2)
ds1SfCas (3)
ds1EsfCas (4)
ccs (5)

USER_CONNECTION

l_partial_fill

short

Local end partial fill - CESM.

Value range: 0-47

USER_CONNECTION

l_idle_detection

short

Local end idle detection - CESM-8.

Values: disable (1) and onhook (2).

USER_CONNECTION

l_onhook_code

short

Local end onhook code - CESM-8.

Values range: 0-15.

USER_CONNECTION

l_idle_suppression

short

Local end idle suppression - CESM-8.
Values: disable (1) and enable (2).

USER_CONNECTION

r_cbr_clock_mode

short

Remote end CBR clock mode - CESM.
Values:
synchronous (1)
srts (2)
adaptive (3)

USER_CONNECTION

r_cas

short

Remote end signalling pass - CESM.

Values:
basic (1)
e1Cas (2)
ds1SfCas (3)
ds1EsfCas (4)
ccs (5)

USER_CONNECTION

r_partial_fill

short

Remote end partial fill - CESM.
Value range: 0-47

USER_CONNECTION

r_idle_detection

short

Remote end idle detection - CESM-8.
Values: disable (1) and onhook (2).

USER_CONNECTION

r_onhook_code

short

Remote end onhook code - CESM-8.
Values Range: 0-15.

USER_CONNECTION

r_idle_suppression

short

Remote end idle suppression - CESM-8.
Values: disable (1) and enable (2).

USER_CONNECTION

l_mc_type

short

Local multicast type flag (for multicast connections). The values are normal (0), root (1) and leaf (2).

USER_CONNECTION

r_mc_type

short

Remote multicast type flog (for multicast connections).
Values are as per local multicast type flag.

USER_CONNECTION

l_end_nni

short

-1: unknown port type.
1: nni port type.
0: non nni port type.

USER_CONNECTION

r_end_nni

short

-1: unknown port type.
1: nni port type.
0: non nni port type.
For incomplete PVC, this field is always -1 (unknown).

CONNECTION

retry_cnt

short

Number of retry attempts before declaring failure (for FRASM llc port only).

CONNECTION

ack_wait_time

int

Number of millisecond intervals the implementation waits before resending unacknowledged information frames (for FRASM llc port only).

ATM_CONNECTION

mc_type

short

Multicast type:
Normal (0)
Root (1)
Leaf (2)

ASI_LINE

l_trk

short

Logical Trunk number for trunks having physical lines. For non physical lines it is -1. Default value for upgrade to Cisco SV+ 9.1 is -1.

ASI_LINE

l_vtrk

short

When trunks have physical lines and it is a virtual trunk, it contains the virtual trunk number, otherwise it is -1. Default value for upgrade to Cisco SV+ 9.1 is -1.

ASI_LINE

l_line

short

Physical line number. This is unique per card. For example, when physical lines are 2, 3 for one trunk and 6, 7 for another trunk on the same card, this field is 2, 3 for the first trunk and 6, 7 for the second trunk. For non physical lines it is -1. Default value for upgrade to Cisco SV+ 9.1 is -1.

CESM_CONNECTION

cbr_clock_mode

short

Specifies clocking mode of the CBR service:
Values:
synchronous (1)
srts (2)
adaptive (3)

CESM_CONNECTION

cas

short

Specifies when CAS bits are carried by the service.
Values:
basic (1)
e1Cas (2)
ds1SfCas (3)
ds1EsfCas (4)
ccs (5)

CESM_CONNECTION

idle_detection

short

Idle Detection (CESM-8).
Values: disable (1) and onhook (2).

CESM_CONNECTION

onhook_code

short

Onhook Code (CESM-8).
Value Range: 0-15

CESM_CONNECTION

idle_suppression

short

Idle Suppression (CESM-8).
Values: disable (1) and enable (2).

CESM_CONNECTION

cbr_clock_mode

short

Specifies clocking mode of the CBR service:
Values:
synchronous (1)
srts (2)
adaptive (3)

ACCESS_NODE

device_id

short

Device ID


Table 0-1: VOICE_CHANNEL
Column Name Unique Identifier Field Data Type Description

chnl_obj_id

Yes

int

Voice channel Object ID.

l_node_id

Yes

int

Cisco SV+ node ID.

1_slot

short

Slot number.

l_line

short

Port number.

l_chnl

short

Channel number.

per_util

short

Percent utilization (0 - 100).

cos

short

Class of service.

eia

short

EIA rate (0 - 20).

dfm_len

short

DFM length (0, 1, 7, 8, 16).

chnl_info

short

Data channel info:
Bit7-6: spare

Bit5: OCU: 0 = reset, 1 = Set

Bit4: DS0A, UCS: 0 = reset, 1 = Set

Bit3: DTE: 0 = DCE, 1 = DTE

Bit2-1: Clocking: 0 = normal, 1 = split, 2 = looped

Bit0: DFM flag: 0 = Off, 1 = On

input_loss

short

Input loss.

output_loss

short

Output loss.

onhook_ab

short

Onhook AB:
Bit7-5: Onhook A: 0 = 0, 1 = 1, 2 = don't care, 3 = unknown, 4 = not used.

Bit4-2: Onhook B: 0 = 0, 1 = 1, 2 = don't care, 3 = unknown, 4 = not used.

Bit1-0: Dial type: 0 = Inband, 1 = pulse, 2 = User Dial.

onhook_cd

short

Onhook CD:
Bit7-5: Onhook C: 0 = 0, 1 = 1, 2 = don't care, 3 = unknown, 4 = not used.

Bit4-2: Onhook D: 0= 0, 1 = 1, 2 = don't care, 3 = unknown, 4 = not used.

Bit1: Sig Inject.

BIt0: Sig Extract.

chnl_type

short

Channel type.

cndt_crtr_indx

short

Conditioning criterion index.

tx_ab_sgnl

short

Transmit AB signalling:
(This applies to Tx/Rcv XY sig)

Bit7-5: Tx/Rcv X signalling

Bit4-2: Tx/Rcv Y signalling

0=sig. bit is 0, 1= sig. bit is 1, 2=tx sig. bit transparently, 3=don't tx sig. bit, 4=Reverse/Inverse sig. bit.

Bit1=0: Spare

tx_cd_sgnl

short

Transmit CD signalling.

Same as tx_ab_sgnl.

rcv_ab_sgnl

short

Receive AB signalling (same as tx_ab_sgnl).

rcv_cd_sgnl

short

Receive CB signalling (same as tx_ab_sgnl).

sgnl_intgr_time

short

Signalling integration time(ms).

min_wink

int

Minimum wink (ms) (100 - 300).

playout_delay

short

Playout_delay (120 - 200).

iec

short

IEC parms:
Bit7: echo cancel: 0 = Disabled, 1 = Enabled.

Bit6: non-linear proc: 0 = Disabled, 1 = Enabled.

Bit5: conv.: 0 = Disabled, 1 = Enabled.

Bit4: echo return loss: 0 = Low, 1 = High.

Bit3: tone disabler: 0 = Disabled, 1 = Enabled.

Bit2: bkcd prefer: 0 = Disabled, 1 = Enabled.

Bit1: bkgnd filter: 0 = Disabled, 1 = Enabled.

Bit0: spare.

Compatibility Notes

Anomalies in the 9.1.10 Release of StrataView Plus

Known Anomalies

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

Bug ID Descriptions

CSCdk58425

If an IMA group has failed on AXIS shelf, PVCs in another group will be shown in failed state.

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.

CSCdm46717

The connchk script in /usr/users/svplus/tools directory doesn't list all the incomplete connections and shows incorrect status for some of the connections.

CSCdr31980

Number of incomplete user connections increased at one of three CWMs in 9.1.

CSCdp43612

Intermittently, the connection manager does not see ports. The issue was with failure to get shared memory access. In a large network whenever the problem occurred, the "Failed to get shared memory" error message was displayed.

CSCdp90026

Added a CESM to CESM 3 segment T1 structured connection without a loopback on one of the CESMs. Connection manager showed an a-bit alarm for this connection. Placed a loopback on the CESM port and added more structured connections. The new connections were displayed with an OK status but after repeated refreshes, the original connection still showed an a-bit alarm. No alarms were present on AXIS or BPXs. Executed a test delay on the connection and it passed succesfully but connection manager changed the connection status to failed.

CSCdr34196

ConnProxy ABR1 MIN modify failure. A general SNMP failure occurred on the agent.

CSCdr02040

New Reports Traffic Summary reports trunk load > 100 %. A customer is producing reports using the new reports application and the Top Utilization reports displays trunks with Util > 100 %. The reports appear to be inaccurate. The trunk that these stats were collected from is a E3. The problem occurred when collecting statistics and producing the output using New reports. The customers database has been recreated but the problem remained.

CSCdr26425

New reports hangs when you run connection traffic summary report on Voice connection. Customer is running 9.1.07. I reproduced on 171.68.205.131 which is running 9.1.09 patch 7. IGX28 has 3 voice connections. Lab 9.2 CWM was able to graph these same connections successfully.

CSCdm09863

Statsmanager GUI shows many time sync node timeouts. SCM is enhanced to try connecting to time sync host 15 times before giving up and record "failed" error. Previously, when connect to time sync host has an error, SCM recorded incorrectly a "timed out" error.

CSCdr46338

Statistics for "Frame Received with BECN" and "Frame Received with FECN" were enabled on StatsMgr. These items were defined as 44, 45 in StatsMgr. However, 44, 45 were defined as "44 = Unkn Prot Frms Dscd at Egress" and "45 = Cells Received from Port" in IGX.

CSCdr45344

CWM allows a frame relay connection on a UFM-U card with CIR, MIR, PIR, QIR of virtually any speed, even 5000 on a v.35 port of 256kbps. The same, when tried from the CLI of the IGX card, gives an error message saying "MIR exceeds peak". It also allows a PCR value of 5000 cps on the ATM side simultaneously. This is true when modifying the connections too.

CSCdr54592

Some problems happened when executed unGroup command. Please add in unGroup tools: -dncon/upcon about each connection. Please fix for long hop count routes. Customer is using Group Connection and current SWSW Release is 8.4.21. They will soon upgrade to 9.1.xx, but SWSW 9.1 does not support 'Group Connection. They must therefore ungroup for their connection before upgrading.

Customer had executed unGroup command. Then, They had experienced two problems: (1) A-Bit=0 happened about some connections on remote AXIS (by dspchstats), and (2) preferred route had not been set as to the connection that hop count was high.

Anomalies Corrected with the SV+ 9.1.10 Release

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

BugID Description

CSCdr43788

Disabled or an expired time-limited version of XR/table. When customer opens Equipment Manager, the error message This application is built with a XR/table is displayed.

Workaround: An installation and update was performed their 9.1.09 release with the latest patch # 7.

CSCdp62721

Support for Audible Alarms has been reintroduced in release 9.1.09 but audible alarm does not work.

Workaround: Support for Audible Alarms has been reintroduced in release 9.1.09.

CSCdm88329

Unable to add HI_PRIORITY or VBR-RT connections using CMGUI. Added DAX connection between VHS cards (FR-FR connection, same card -2 ports) using CMGUI, only VBR-NRT ,ABR and UBR are highlighted and VBR-rt and HI_PRIORITY are disabled. If VBR-rt or HI_PRIORITY is selected as service type, automatically the sevice type changes to VBR-nrt while adding connections.

Workaround:From CLI, both VBR-rt and Hi_Priority type of connections can be added and same was displayed properly in CMGUI.

CSCdm91369

cmgrd does not understand node release 9.2.3.as realtime connection capable node. Therefore we cannot add real-time VBR,UBR connections on nmsigx38.

Workaround: None.

CSCdm91654

BXM-FRSM ATM_FR atfst connection is shown as ATM-ATM in Conn-Mgr GUI.

Workaround: None.

CSCdp01303

When customer uses Connection Manager to view/modify data/voice connections, SV+ complains of an internal error and does not allow customer to view connection information. Customer is using non-standard (not public/private) community strings.

Workaround. Connection Manager is attempting to contact switches using public community string, even though svplus.conf and watchdog.conf have been modified.

CSCdj93910

Cannot add/mod ATM ABR1 OC3 cons w/MCR=353208 (max) using ConnProxy.

Workaround: Successfully added/modified using CLI.

CSCdm95379

.Some ATM-FR invisible when selecting only ATM-FR. New ATM-FR connection did appear in the list until click apply (Note: This will occur if selecting only ATM-FR.)

Workaround. None.

CSCdr25930

Connection added through GUI shows Fail on CLI (Non-DAX).

Workaround: Use the new default values from the MIB.

CSCdm86541

Frame Relay connection details are not being updated into the StrataView Plus database correctly, some are missing and some are incomplete.

Workaround: After code start on SV+, added a connection to force updates to SV+ from SWSW. SV+ reported that the verification on SWSW data base looks fine.

CSCdr03982

Installation script cannot handle disk partition with name of nine characters.

Workaround: Limit naming to eight characters.

CSCdk36752

.In some circumstances, the SV+ (manual) install script hangs in ilog_cleanup.

Workaround: comment out SV+ Install script to not run ilog_cleanup.

CSCdp16178

Number of Buffers setup for Informix takes up all memory.

Workaround: None.

CSCdp16182

If the Informix directory not removed before upgrade, Informix 72 is not installed properly.

Workaround: None.

CSCdp16184

9.1.09 upgrade from 9.1.06 waits for data when it should not. Also snmp.conf.orig not copied to snmp.conf.

Workaround: None.

CSCdm92999

The traps seen in HPOV are in extended form and not per functional specification.

Workaround: None.

CSCdp72969

SV+ dumped core when adding an ins object into the HPOV map.

Workaround: Reason was user did not have all HPOV patches installed. Install all HPOV patches.

CSCdk89004

ConnProxy CESM 8T1C - CESM 8T1C addition fails.

Workaround: The root cause is that ConnProxy has a bad default value for MaxBufSize for CESM 8T1 structured port.

CSCdp27322

ConnProxy coredumped.

Workaround: The coredump was caused because the makefile in /src/agent/cmpa/src.Patch3 was pointing to old cmgrd/ilog/ but should have been pointing to new cmgrd.patch3/ilog. Mismatch of Ausmparams structure in cmui.h that caused the core dump. Build in /src/agent/cmpa/src.Patch3 by correcting the makefile to point to /cmgrd.patch3/ilog.

CSCdk13201

97r1 compiler warnings.

Workaround: Fixed in 11.3AA build.

CSCm83613

SNMP mods of PVCs thru ServiceMib forces %UTIL to %100.

Workaround: Fixed the Problem in Rel 9.2.x.Files Changed:

1) src/agent/cmpa/src/frTable.c

2) src/agent/cmpa/src/frConnection.

CSCdm92944

Error message display year 2000 in wrong format.

Workaround: Fixed the Problem in ConnProxy for Rel 9.1.x.

CSCdp04800

ConnProxy return CDVT(0+1) out of range incorrectly.

Workaround: Could not reproduce the problem . The Max limit for CDVT0 5000000.

CSCdp90676

Modify connections failed thru proxy when atmEndPointICR was set. The GUI modification went thru fine. Note that in GUI ICR field was not modifiable. GUI took whatever value was set in the PCR field.

Workaround: Do this check on done on the connproxy side, or Service MIB may be modified to say that this field is not modifiable.

CSCdm91232

If Narrowband Trunks were deleted and added, Narrowband Trunk ID changed on SV+ 'Reports' function. To be matched Logical Trunk No. is very difficult with physical Trunk No.

Workaround: New Reports function has displayed correctly.

CSCdp01973

New Reports inaccurate for Top Utilization reports for trunks.

Workaround: None.

CSCdp01986

New Reports graph for trunk traffic summary shows incorrect with E1/32 and SR/16 trunks.

Workaround: None.

CSCdp02074

New Reports complains that start time must be before end time.

Workaround: None.

CSCdm88576

SCM is not sending the correct enablelist to the nodes.

Workaround: Manually tftp the latest enabled stat list of each node to the particular node affected and were able to collect stats. Do not use the GUI's Send Enabed stats button to avoid disabling of the parms.

CSCdp09814

SCM closes intermittantly.

Workaround: Only one instance of SCM can be run at the same machine.

CSCdj81162

NW Topology does not display any Access Devices attached to feeder nodes.

Workaround: Now these features have been implemented on both NWTopology as well as SvOvTopology.

CSCdp09082

NWTopology core dumping.

Workaround: If you remove the config files under the NWTopology directory the system will function correctly.

CSCdp38552

llvTransformer erros when starting topology.

Workaround: This bug was due to resizing the overview window below a certain size. The fix has been put such that user is not allowed to resize the window below a certain size.

CSCdp16956

No trap when AXIS goes unreachable.

Workaround: CWM displays the event log messages received from the SW as they are in the HP OV event browser. When an AXIS node becomes unreachable,CWM gets Comm Failure from the Switch.These messages are converted into SNMP traps & sent to trap process of HPOV,which shows these traps in the event browser.CWM is transparent as far as these event log messages are concerned.

CSCdp75366

unGroup -c does not work with BCC-3-32/BCC-3-64/BCC-4. When using unGroup -c in BCC-3, the following error message is displayed: Ram size out of range: -1. Error getting processor card RAM size from switch.

Workaround: None.

Anomalies Corrected with the SV+ 9.1.09 Release Patch Level 1

The following anomalies have been corrected with the 9.1.09 version patch level 1 of Strata View Plus.

BugID Description

CSCdp09761

BXM - FRM one segment connection other end parameters are not set properly.

Anomalies Corrected with the SV+ 9.1.09 Release Patch Level 2

The following anomalies have been corrected with the 9.1.09 version patch level 2of Strata View Plus.

BugID Description

CSCdp10497

Cannot select the service type of ATFST in the Connection Manager.

CSCdp01303

Connection Mgr uses incorrect community strings when contacting switches.

Anomalies Corrected with the SV+ 9.1.09 Release Patch Level 3

The following anomalies have been corrected with the 9.1.09 version patch level 3 of Strata View Plus.

BugID Description

CSCdm91654

BXM-FRSM ATM_FR atfst connection is shown as ATM-ATM in Conn-Mgr GUI.

CSCdj93910

Cannot add or modify ATM ABR1 OC3 cons w/MCR=353208 (max) using ConnProxy

CSCdm95379

Some ATM-FR connections invisible when selecting only ATM-FR from ConnMgr.

CSCdj93904

ConnProxy should not allow atmEndptCCDV for IPX->BPX atf/atfst connections

CSCdj93905

Inconsistencies for atmEndptCBS between switch,mib,ConnProxy & CMGUI.

CSCdp16178

Number of Buffers setup for INFORMIX hog all memory.

CSCdp16182

When upgrading from 9.0/8.4 informix not installed properly

CSCdp16184

Upgrade to 9.1.09 from 9.1.06 not working (waits for data when it should not).

CSCdk13201

ConnProxy does invalid range checking for MinAdjustPeriod for BXM endpts.

CSCdm83613

SNMP modification of PVCs thru ServiceMib forces %UTIL to %100

CSCdm92944

Error message displays year 2000 in wrong format

CSCdp04800

ConnProxy return CDVT(0+1) out of range incorrectly

CSCdm91232

If executing addtrk and deltrk, Narrowband TRUNK ID will change on SV+ Reports function

CSCdp01973

New Reports inaccurate for Top Utilization reports for trunks

CSCdp01986

New Reports Trunk traffic summary is comparing bytes transmitted to peak byte received

CSCdp02074

New Reports complain that start time must be before end time.

CSCdm88576

SCM is not sending the correct enablelist to the nodes

CSCdp09814

SCM closes intermittantly

CSCdj81162

Network Topology does not display any Access Devices attached to feeder nodes

CSCdp09082

Network Topology core dumping

CSCdm93003

Network Topology, map takes too long to update when Fastpad devices are deleted.

CSCdp16956

Axis shelf went unreachable with no traps captured in the svplus.

CSCdp09761

BXM - FRM one segment connection other end parameters are not set properly.

CSCdp11459

Connection addition between ASI & FRSM fails with error wrong Policing.

CSCdp00125

SV+ NWTopology process causes core dump.

Anomalies Corrected with the SV+ 9.1.09 Release Patch Level 4

The following anomalies have been corrected with the 9.1.09 version patch level 4 of Strata View Plus.

BugID Description

CSCdp38552

llvTransformer errors when starting topology.

Anomalies Corrected with the SV+ 9.1.09 Release Patch Level 5

The following anomalies have been corrected with the 9.1.09 version patch level 5 of Strata View Plus.

BugID Description

CSCdp49596

ECN Threshold shows up as zero in one segment BXM-FRM connection

Anomalies Corrected with the SV+ 9.1.09 Release Patch Level 6

The following anomalies have been corrected with the 9.1.09 version patch level 6 of Strata View Plus.

BugID Description

CSCdp89024

ECN Threshold mapping not correct for one segment BXM-FRM connection.

Anomalies Corrected with the SV+ 9.1.09 Release Patch Level 7

The following anomalies have been corrected with the 9.1.09 version patch level 7 of Strata View Plus.

BugID Description

CSCdp62721

On SV+ 9.1.09 AIX don't support audible alarm for all major alarms as in 8.4.10.

CSCdp31386

Audible alarm does not work.

CSCdm39409

StrataView+ 9.1.06 no longer supports Audible Alarms.

Anomalies Corrected with the SV+ 9.1.09 Release Patch Level 8

The following anomalies have been corrected with the 9.1.09 version patch level 8 of Strata View Plus.

BugID Description

CSCdm76586

network_id field in line table is incorrect.

CSCdp60172

Bad usage of tm_year, inappropriate date in error messages.

CSCdm72969

SV+ dumps core while trying to add a new object of type INS through HP OV.

Anomalies Corrected with the SV+ 9.1.09 Release Patch Level 9

There was no patch level 9 for the 9.1.09 version of Strata View Plus.

Anomalies Corrected with the SV+ 9.1.09 Release Patch Level 10

The following anomalies have been corrected with the 9.1.09 version patch level 10 of Strata View Plus.

BugID Description

CSCdr54592

Some problems happened when executed unGroup command.

Anomalies Corrected with the SV+ 9.1.09 Release Patch Level 11

The following anomalies have been corrected with the 9.1.09 version patch level 11 of Strata View Plus.

BugID Description

CSCdr70644

Some problems happened when executed unGroup Command.

Anomalies Corrected with the SV+ 9.1.09 Release

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

BugID Description

CSCdm43968

Equipment manager message:"Unable to invoke equip. management. CV is not installed or not integrated"

CSCdm50556

All traps received from BPX/IGX shows SV+ station as source rather than BPX name.

CSCdm56837

Some AXIS nodes may not get synced up (when SV+ is brought up) and stay in init state.

Workaround: Warm start SV+

CSCdm59711

After an SV+ warm start, PVCs involving AXIS may show spurious 'ABIT' condition. This affected AUSM/FRM cards.

Workaround: Coldstart SV+.

CSCdm45778

Desktop unable to open the window on local workstation. Msg: X11: connection refused by server.

CSCdm48074

When configuring CE-CE Connection additions, trying to set value for IdleCodeIntegration Period will result in an error. There are lots of Conditions/Constaints required before this variable could be set. Hence the rejection from switch.

Workaround: Use default parameter or dont sent this specific value.

CSCdm65437

Attempts to add onnections fail with subtypes atfst, atftfst and atfxfst.

CSCdm55748

No objects displayed for Connection->FrameRelay or ServiceLines->T1 for stats reports and util_ext: db fetch 0 shows up on the screen.

CSCdm36901

Various L1 errors appear in svplusL1.log

CSCdm55596

asi_line table does not have uxm_lines.

CSCdm56383

SV+ 9.1.07 Connection Manager fails to find AUSM port of AXIS shelf.

CSCdm63914

If the swsw is 8.2.56, the line_load, interface, card_type from packet_line all come back as zero.
Workaround: Upgrade switch software.

CSCdm69328

Link0 and Link1 do not always come up after reboot.

CSCdm57341

Setting UPC parameters for Ausm_BXM or BXM_BXM Connections resulted in Connection Failure.

CSCdm34088

Slow display and update of the "Objects Available" window in Wingz2.5

CSCdm68237

Error message "Invalid Object Type Count in Enable List. 011" is returned when sending stats enable to a BPX node running 9.1.x and enabling some objects available under Service Interfaces --> Physical line T3/E3/OC3 sub-categorie.

Workaround: Disable the Physical Line T3/E3/OC3 objects causin this error before sending stat enable to the BPX node.

CSCdk72512

The following set of actions will cause the dialog box to appear:

    1. Double-click on a trunk icon only

    2. Trunk listing window appears

    3. Do not close this trunk listing window. Click somewhere in the topology window.

    4. Click in a grey area of the trunk listing window (which will be behind the topology window). Do not click on a trunk listing row, just the grey area below it.

In the above situations, a dialog box appears stating "Trunk has been deleted".

CSCdm71424

Upgrade from 9.1.06.SOL to 9.1.09E is dropping the database

CSCdj94046

During upgrade of SV Plus, the following message occours: "ipc.c:606:IPC Connect Failed, Address(9002) PID(862):: Connection refused"

CSCdm82112

Cannot see trunks on submap. This problem occurred intermittently.

CSCdm85965

After Backup ANI connection selected and Add or Delete button becomes sensitive, if another ANI is selected the button remains sensitive.

CSCdm59720

When the % Utilization parameter is changed on an AXIS PVC, SV+ Connection Manager does not update the display.

CSCdm63582

Unable to use the save configuration tool to get the ASC configuration saved. Items being saved are only Service Modules and not the ASC.

CSCdm58376

Install Script says "Welcome to Online help installation of SV+" This is misleading and is removed from the install script.

CSCdm83480

SV+Service.mib is not updated for UPC params. UPC params does not reflect anything for BXM or AUSM-AUSM

CSCdm89055

Cannot Modify BXM-FRSM and BXM-BXM atfst connections

CSCdm88377

cmgrd not setting remote-end upd parameters BXM-BXM atfst connections.

Anomalies in the 9.1.08 Release of StrataView Plus

Anomalies Corrected with the SV+ 9.1.08 Release

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

Bug ID Descriptions

CSCdm03119

If the SV+ Service Mib object atmEndPointMinAdjustPeriod is set to < 20 for a ATM endpoint on BXM/UXM card, SV+ Connection Service Agent considers it as invalid value and rejects the request.

The valid range for this atmEndPointMinAdjustPeriod mib object in SV+ Service Mib is corrected to the following

. ASI/BNI T3/E3: 20-250 msec

. BXM/UXM: 3-255 msec

. ABR.1: 1-100 msec

The range is applicable to ABR.1 and ABR.FS connections when VSVD is enabled.

CSCdm05854

SV+ reports GUI, doesn't show RcvFramesUnknownProtocols stat object. This problem has been fixed in SV+ Wingz interface utility.

CSCdm12801

SV+ Connection Manager GUI doesn't allow the user to set partial fill value for connections on unstructured CESM 8T1/E1 ports. However, it comlains that the partial fill value is not greater than 47. This problem has been fixed in Connection Manger GUI.

CSCdm19166

SV_CreateDB, intermittently shows some error message saying that "/usr/users/svplus/emsc*.msgs: No such file or directory" . This problem has been fixed in SV+CreateDB process.

CSCdm24894

ALM trunks do not appear in the New Reports -> Performance Data -> Trunks -> Trunk Traffic Summary. This has been fixed in NewReports.

CSCdm26653

SV+ INSTALL procedure applies the patches to HP OpenView, without checking whether they are already installed or not. Because of this SV+ would overwirte some of the latest patches of HP OpenView. This problem has been fixed in SV+ install process.

CSCdm29796

SV+ Connection Service Agent doesn't do the valid range checking for ceEndPointMaxBufsize Mib object, while setting up the connections. This problem has been fixed in ConnProxy process.

CSCdm30550

While modifying a CESM 8E1 channelized connection with CDVRxT value 32000 using Connection Manager GUI, the GUI reports an error message "CeMaxBufSize should be between 5120 to 4170". However, the connection modification still fails, even after setting the CeMaxBuffSize to a value within the suggested range. This problem has been fixed in Connection Manager GUI process.

CSCdm33287

An intermittent DB inconsistency problem, which wrongly sets the A-bit status of ATM connections in atm_connection table to FAIL has been fixed.

CSCdm34273

When a user is logs on remotely, to SV+ station as svplus user, an error message 'xrdb: Can't open display' is shown. This problem happens because the environment variable DISPLAY hasn't been set. SV+ environment setup files (.cshrc etc.) have been updated to set the DISPLAY variable to either the SV+ system or to the machine from the user has logged in.

If you do a remote login to launch SV+.The number of remote logins should be restricted to 1.

Secondly, you should set the font size of the DISPLAY using the Style ManagerTool available in CDE. It should have a size of Small(3) or less.

CSCdm35603

When CiscoView is selected from Equipment Manager button of SV+ Desktop to manage BPX/IPX/IGX device running 8.4 or 8.5 release, it aborts with a error message 'selected node runs 8.x. Equipment Manager only supported for 9.1 onwards'. This problem has been fixed in Desktop process.

CSCdm39407

SV+ Connection Manager daemon gives VPI/VCI collision error messages during FR-CE, ATM-CE connection provisioning. The problem has been fixed in databroker process by adding the code to check for presence of colliding VPCONS while adding VCCONS.

CSCdm41998

SV+ Connection Manager doesn't do range checking on the CIR value against portspeed for PVCs on FRSM-8 card. This problem has been fixed in cmgrd process.

CSCdm44647

SV+ New Reports shows 'No Trunks found' when all trunks are selected in trunk traffic summary report. The trunk report is shown properly for each individual trunk if only one trunk is selected.

CSCdm47446

SV+ Connection Proxy fails with the SNMP error "Idle Code Integration Period Cannot be set if idle detection is not Enable_OnHook" error when an attempt is to made to modify a CE-CE connection without supplying CesmIdleCodeIntegrationPeriod. This problem has been fixed in ConnProxy process.

CSCdm47461

SV+ Connection Proxy fails to add CE-CE connection with an error message MaxBufSize is out of range.

CSCdm48173

SV+ Connection Proxy agent gives a general error, when an attempt is made to do snmpwalk on svConnTable in a network with CESM connections. This problem has been fixed in ConnProxy process.

CSCdm89514

While adding connections when AUSM is one end, connection addition fails with an error message from axis: "wrong CLPTagFlag value."

CSCdm91654

BXM-FRSM ATMFRatfst connection shown as ATM-ATM in Connection Manager GUI. .

CSCdm06466

Able to add ce connections on a port in use on axis nodes. Thec onnection is refused by the switch and then backed off by the SV+.

CSCdm85947

NWTopology Core dumped after running for long time.

CSCdm87458

SV+Service.mib needs explanations added. ATFR needs to be defined. All Variables "atmEndpt*" are not there in service mib, they are copied from strata.mib. Proper mapping of all the variables is required. ABR.V and ABR.nV needs some more explanation from SV+Service.mib point of view.

CSCdm84769

SV+ core dumps while trying to add a new object of type INS through HP OV

CSCdm92944

Error message display year 2000 in wrong format

CSCdm89026

SV+Service.mib does not say that VSVD is not modifiable

CSCdm91232

Narrowband Trunk ID is displayed incorrectly in "Object Available" field on SV+ 9.1.xx.

If TRUNKs were deleted and added, TRUNK No. changed on 'Reports' function. 'Logical TRUNK No.' is displayed.

CSCdm88576

SCM is not sending the correct enablelist to the nodes

CSCdm89040

DBSchema document does not explain different values of VSVD.

According to SV+Service.mib, vsvd=1 means enable and vsvd=2 means disable, but when a connection is added from Connection Manager GUI or conn-proxy with vsvd enable, database shows vsvd=2.

CSCdm59074

IMA trunk failures are not highlighted on the SV+ topology map when 'Retained Links' is enabled

CSCdk82202

Printed topology map shows deselected background

CSCdm83466

EMC core dumps when emc gets tftp timeout and tries to send a cancellation request to tftpd.

CSCdm06466

When a connection already exists on a port of an axis node, you can create another connection. This connection is rejected by the switch software. Upon rejection, SV+ backs off the connection from the database.

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.08 release of StrataView Plus.

Bug ID Descriptions

CSCdk931003

SV+ Connection Proxy agent fails to add any FR connection, and goes into a state, where no further operation can be done on the agent. This happens only if INS/DAS software is installed on the SV+ station.This problem has been fixed in ConnProxy process.

Anomalies in the 9.1.07 Release of StrataView Plus

Anomalies Corrected with the SV+ 9.1.07 Release

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

Bug ID Descriptions

CSCdj47891

SV+ Statistics Manager GUI takes lot of time during it's start-up to it's initialization, before giving control to user. This is more evident in large network environments. During start-up SCM does SNMP GET operation synchronously on all the nodes to get their configured statsmaster. This adds up to it takes for the initialization. This problem has been fixed in statsmain process by making these SNMP operation asynchronous.

CSCdj69487

SV+ Connection Proxy agent fails to modify preferred route of a CESM connection. This problem has been fixed in ConnProxy process.

CSCdk53395

SV+ Connection Proxy doesn't use user-specified values to set the parameters HiCLP, LoClp, VCQSize, EfciQSize, IBS for ATM-FR connections on AUSM cards in AXIS shelves.

CSCdk66274

The documentation of MIR, PIR, QIR and IBS objects in SV+ Service MIB has been updated to mention that these object must be set for FR connections with foresight.

CSCdk66993

An intermittent exit problem in Equipment Manager GUI has been fixed. This problem occurs when a DISPLAY SHELF button is clicked, after changing the node selection from the one that is being displayed to a different shelf.

CSCdk68705

An unexpected exit problem in HP OpenView, while filtering events in Event Browser has been fixed by applying patch PSOV_02243 from HP.

CSCdk72506

SV+ Topology sometimes shows grey text on grey background (state of the node). The contrast between the foreground text in dark grey and the background in light grey is low when a row listing an unreachable node is selected in the NodeShelf dialog of SV+ Topology.

The lowered contrast is caused by the fact that by default the color of the cell displaying the alarm is reversed when the row is selected.

This problem has been fixed in NWTopology process by making sure that the color inversion doesn't take place during the row selection. Also, the contrast has been enhanced by displaying text in bold as well using a color which is opposite of the background color. A text color of "white" is used when the background is either dark grey (unreachable alarm) or red (major alarm) and "black" is used when the background is either yellow (minor alarm) or green (no alarm).

CSCdk84820

Inconsistencies between ConnMgr GUI, SV+Service mib, strata mib for minimum values of RateUp/RateDown on ABRFS connections on ASI/BXM/BNI cards in BPX and UXM card in IGX has been fixed. Minimum value for RateDown is 1 on BPX/IGX. For RateUp minimum value is 0, for ASI/BXM/BNI cards on BPX and 7 for UXM cards on IGX.

CSCdk88677

StrataView NewReports show only peformance data if plot duration is selected as TOD. Also the Start Date field have to be left empty, otherwise you get the error "Stop date/time must be later than start date/time".

CSCdk89004

PVC addition using Connection Proxy agent between CESM 8T1 to CESM 8T1 cards fails with the error "Parameter modification for add channel failed". This problem has been fixed in ConnProxy process. This problem happens because EndPortMaxBugSize defaults to value 10000 in ConnProxy.

As a work-around to this one can set value of svCeEndPointBufMaxSize to any value between CDVRxt time 0.7 to 9216 for CESM T1 connections.

CSCdk89368

StrataView may intermittently loose Link 0 /Link 1 access to all the switches in the network, Topology may not get updates for any kind of alarm on the switch. This was observed only one time and that too in a very large network environment, after a network outage due to user error. The problem has been fixed in topod process.

As a work-around to the above problem SV+ can stopped and re-started.

CSCdk89649

StrataView install fails if there multiple entries in the /etc/hosts file with the same host name. It happens even if the entries are commented out.

CSCdk89934

atmEndPointRateDown value description in SV+Service.mib states that range is 0 to 100 for abr-fs.

For abr-fs, range should be 1-100%. SV+Service.mib has been modified accordingly.

CSCdk91186

A database updated problem in emc process, due to which the node table in StrataView DataBase is not updated with the firmware release of AXIS shelves, has been fixed. This problem happens only with AXIS shelves with IP addresses X.0.0.X where X > 0.

CSCdk92485

An intermittent deadlock problem between processes emd and topod has been fixed by throttling number of keep alive messages sent by rtm process to AXIS shelves during one iteration. The deadlock was caused by a blocked by emd process, which was sending axis link status messages to topod. These messages were caused by linkup/down messages sent to emd by rtm.

CSCdk92758

A configured preferred route on a PVC is not removable from Connection Manager GUI. This problem has been fixed Connection Manager GUI. As part of this solution Configure button in Connection Manager GUI is not greyed out, when a Clear Preferred route button is selected.

CSCdk93082

If a connection added through switch CLI is modified using Connection Manager GUI, the connection stops working and the connection type gets changed. This happens intermittently. This has been observed when a FR-ATM connection of ATFXFST type is added on switch and CIR value is modified from Connection Manager GUI. The connection stopped working and the type has been changed to SPFTVBR. This problem has been fixed in databroker process.

This problem is related to some timing issue, depending on the order in which SV+ receives the add conn robust message from the devices. The problem could occur if SV+ receives add conn message from the node on FR end of the connection before it gets the message from ATM side (BPX). As soon as the add fr conn message is received, databroker populates the conn in the DB as a complete connection. Since it does not know the atm endpoint subtype at this point of time, it arbitrarily picks VBR as the subtype of the connection.

The fix is to check the foresight flag on the FR endpoint. If it is ON, populate it as a ABR.FS connection, otherwise VBR connection.

CSCdk93192

SV+ Connection Proxy updates the ICR value while adding or modifying an ATM-ATM ABR1 connection. This behavior is inconsistent with SV+ Connection Manager where ICR field is grayed out while adding/modifying an ATM-ATM ABR1 connection. This problem has been fixed in ConnProxy process.

CSCdm00124

SV+ Network Browser shows that status of 3810 device as unreachable, though 3810 is diplayed as reachable in SV+ Network Topology map. As a fix to this problem the management state of a 3810 will no longer be shown as unreachable in Network Browser. Instead a -- would be shown to indicate that the status is not known.

CSCdm01892

SV+ Connection Manager GUI shows ports on cards, which are removed from the nodes, in PortHelpDialog box. This problem has been fixed Connection Manager GUI.

CSCdm01984

SV+ Connection Manager GUI shows line number as 0 in PortHelpDialog window, for FRP/FRM ports. This problem has been fixed in emsc process.

CSCdm02239

SV+ fails to populate database with collected narrow band trunk statistics. This problem has been fixed in statsparser process. However, while fixing this problem the following details were found out about fixes done for CSCdj71379 and CSCdj68473.

CSCdj68473: SV+ SCM can't collect FRM/CVM T1 line statistics. The fix for this problem only resolves statistics collection on single line service cards. However, the fix doesn't work for multi-line cards like UFM.

CSCdj71379: SV+ SCM fails to parse IPX/IGX trunk statistics. The fix done for this problem only resolves trunk statistics collection on single line trunk cards. The problem still occurs with multi-line trunk cards.

CSCdm03319

SV+ Connection proxy agent fails to modify an existing ATM connection, with atmEndPointMinAdjustPeriod set to a value less than 20. This behavior is inconsistent with SV+ Connection Manager where it allows this value and successfully modifies the connection. This problem has been fixed in ConnProxy process.

CSCdm04691

A problem in watchdog process and some of backend processes which make them terminated or exited in an unexpected manager has been fixed. The problem occurs when control-C is pressed from the same shell script session as the initial SV+ launch. This happens if you press control-C without exiting SV+ menu.

Further Problem Description:

When control-C is pressed, the Unix kernel sends it to all processes in the same process group. SV+ processes inherited the process group ID from the SV+ launch script. However, some SV+ processes treat control-C as termination request. When they voluntarily exit, watchdog try to restart them again. The problem has been fixed now in a way such that SV+ daemon processes no longer inherit the launch script's process group ID.

CSCdm05611

SV+ Connection Proxy agent fails to add AUSM PVCs if UPC parameters are not specified. The connection addition attempt fails with a error message which says "Wrong ingrQCLPHighThresh value". This problem has been fixed in ConnProxy process.

CSCdm06929

If SV+ window (x-term or shell session from which SV+ menu is used) is closed while stop SV+ core processes option is being executed, some of the SV+ processes may not be stopped properly. Because, of this SV+ doesn't come up properly, when it is started next. This problem has been fixed in stop core processes procedure of SV+.

CSCdm07087

SV+ Port Proxy agent fails to add a port on CESM-8E1 card, with the error "svCesmPortTable is not supported for the card: CESM-8" This problem has been fixed in PortProxy process.

CSCdm07324

svPlusL1.log file in /usr/users/svplus/log directory gets the entry "[ConnProxy]GetActiveInsdHostFromFile: fopen[/usr/users/svplus/config/insd.conf, error[2]" added to it very frequently. This happens while ConnProxy process is running. This problem has been fixed in ConnProxy process.

CSCdm09211

SV+ Connection Proxy agent doesn't accept value 0 for atmEndPointRateUP on ATM end point side of ATM-FR ABRFS and ATM-ATM ABRFS connections. This problem has been fixed in ConnProxy process.

CSCdm09292

SV+ imageDonwLoad process fails to download firmware images for FRSM-HS1/B V35 cards in AXIS shelves, from SV+ Topology. This problem has been fixed in imageDownLoad process.

CSCdm09566

SV+ SCM, in integrated environment, fails during startup with the error message "Can't communicate with SV+. Either SV+ is not running or another GUI is already running". This problem was observed in SV+ 9.1.06. The problem has been fixed in SV+ statsmgr process.

CSCdm09844

On SV+ station OpenView reports the error "WARNING!! StrataView Topology submaps are not updating. Either SV+ core process are not running, or there is already an OVW session on this display.", during OpenView processes startup. This problem was observed in SV+ 9.1.06 This happens because of wrong default base port usage during SvOvTopology launch.

As a work-around, change the base port option in /usr/users/svplus/OV/registration/C/SV_registration file.

Application "DAS/DNS Config"

{

Command -Shared -Initial -Restart "/usr/users/svplus/svOvLaunch.s SvOvTopology -b 19500";

-------

-------

-------

}

and restart OpenView.

CSCdm10618

Connection Manager GUI does not reflect correct connection status of AUSM 8. This problem has been fixed in emc.

The Connection Manager shows a "OK/A-Bit Alarm" status on the connections instead of "Fail/A-bit" status or "Failed" status instead of "OK" status, if a loopback is disabled or enabled on the port on which this connection exists. This problem happens if there is a connection exists on a AUSM 8 port card in a AXIS shelf, and if user enables loopback from a disabled state or disables from a enabled state from Equipment Manager GUI.

This problem has been observed in SV+ 8.4.12 managing AXIS 4.0.16 shelf with AUSM 8 cards.

As a work-around, execute a node resync on the AXIS shelf from Equipment Manager GUI.

CSCdm11697

PVC addition using Connection Proxy agent on a AXIS shelf running release 5.0 and above fails with the error message "Invalid release for AXIS". This has been fixed in ConnProxy process.

CSCdm11833

SV+ Connection Proxy agent fails to modify PCR01 value on ATM-ATM or ATM-FR connections, to a smaller value. This problem has been fixed in ConnProxy process.

CSCdm12818

SV+ Connection proxy agent fails to add a PVC with SCR greater than or equal to 14732 CPS, on AUSM IMA ports. This problem has been fixed in ConnProxy process.

CSCdm12903

SV+ Connection Manager GUI and Connection Proxy agent do not allow setup of UPC parameters like atmEndPointEfci, atmEndPointHiCLP, atmEndPointLoCLP, atmEndPointVcQSize, atmEndPointIBS on ATM-ATM connections for Ausm on AXIS shelf. The problem has been fixed in cmgrd process.

Further problem description: The setting of UPC Parameters for Ausm for ATM-ATM connection is not supported in earlier releases of SV+ 9.1. The setting of UPC parameters for Ausm is only supported for ATM-FR connections.

CSCdm15341

After repeatedly opening and closing the SV+ Desktop a time may when it will not be possible to have a working Desktop anymore. The NWTopology process will print the warning:

WARNING: NWTopology - Failed to connect to topod.

Will wait for 60 secs and try again.

NWTopology exits after repeating this warning 5 times at which time Desktop will exit as well.

This problem has been fixed in NWTopology process.

CSCdm17672

An intermittent exit problem in cmgrd process has been fixed. This problem happens intermittently at the time PVC deletion request and it occurs only when the DataBroker process is busy processing connection or alarm messages from the network

CSCdm18580

An intermittent exit problem in emd process has been fixed. This was observed when manual resync operation is done from Equipment Manager GUI with an AXIS shelf.

CSCdm19051

The `Welcome' line in SV+ menu doesn't reflect the correct SV+ version. This problem was observed in SV+ 9.1.06 release.

CSCdm20291

SV+ manual install fails, if groups svplus and informix are not added to the system, prior to adding SV+ CSCOconf package.

As a work-around to the above problem, one can add svplus and informix groups to the system before running SV+ manual install.

CSCdm20301

SV+ install gives the error "Can not open /usr/users/svplus/svplus.conf" file. This problem has been fixed in SV+ INSTALL scripts.

CSCdm20626

SV+ SCM error pane shows the dates on the statsfiles with 2 digit year field. These are error messages only and do not have any direct effect on Y2K compliance. This problem has been fixed in statsmain process.

Anomalies Corrected in SV+ 9.1.07 Patch 1

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

Bug ID Descriptions

CSCdm31948

The attempts get PVC info using SV+ SNMP Agent fail on FR side for ATM-FR connections. This problem has been fixed in ConnProxy process.

CSCdm38892

Intermittently SV+ desktop might not be able to launch Equipment Manager GUI to manage release 4.0.X AXIS shelves. This problem has been fixed in Desktop process.

CSCdm39168

SV+ Connection Manager GUI doesn't show the right A-bit status of the connection when a loop back is removed and added back. Connection Manager GUI shows the A-bit status as failed, though the switch has it in OK/Clear status.

CSCdm41838

SV+ database shows a non-existent connection in the network. This happens even after starting the StrataView process after creating the database using "create_db" utility. This problem happens intermittently and has been fixed in create_db tool.

CSCdm42155

An intermittent exit problem in eventd process has been fixed. Because of this problem, the following error message was continuously displayed on the SV+ console:

"<write_till_finish>: write failed,errno=32,wrote 0 of 2 bytes, ...."

The problem usually happens when a lot of alarm messages are received by SV+ from the switch. This has been observed only in large network environment. The problem has been fixed in eventd process.

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.07 release of StrataView Plus.

Bug ID Descriptions

CSCdm09863

Statistics Collection Manager GUI shows excessive timed out messages to time sync host.This problem has been fixed in statsmain process.

As a fix to the above problem, statsmain has been enhanced to try connecting to time sync host 15 times, whenever it receives "node is busy" or "connection under progress" type of failure cases, before giving up and record "failed" error. For all the other failed cases SCM reports "failed" error and logs the error in its log file.

Anomalies Corrected in the 2.0.00 Release of WANCV

The following anomalies have been corrected with the 2.0.00 release of WANCV which is distributed along with 9.1.07 version of StrataView Plus.

Bug ID Descriptions

CSCdm46308

The backcard display is 15PX and the interface line type is v35 , hence the display donot match

CSCdm38256

For MGX88.pkg versions earlier than 2.02, card information may be displayed incorrectly for SRM modules in slots 31 or 32, if they are in the standby state. The information displayed is for the SRM in the active state, if one is present in adjacent slot.

CSCdk00065

HPOV grapher malfunctions in CiscoView. This problem has been fixed in Cisco View engine as part of fix for anomaly CSCdk76858.

CSCdk05434

Display problems with Port/Channel monitor. Some MIB variables were defined as INTEGER instead of Counter in axis.my. This caused the CiscoView monitoring dialogs to display them as numbers instead of the normal counter display. A large number of variables was redefined as Counter instead of INTEGER in axis.my. This defect has been fixed in AXIS.pkg version 1.03.

CSCdm06256

Cisco View, rear view for IGX shows wrong card layout for UXM card.

CSCdk07747

BNM-155 line color changes do not function in CiscoView. Status monitoring for BNM's has been fixed in AXIS.pkg version 1.03.

CSCdk17076

CSCdk10759

Cisco View reports false error message while deleting a port from FRSM-8E1 card.

CSCdk20837

Intermittently, when changing from rear to front chassis view or vice-versa the chassis view shows up as a mix of the front and rear views.

CSCdk21358

Front view of a BPX in CiscoView don't get refreshed if back cards are removed first. This problem has been fixed in IGX 9.1 switch software.

CSCdk21445

Cisco View retrieves random number of Cards/Ports/Channels from respective table upon query. This problem was observed, when large number pots and channels are configured on FRSM-8 card.

CSCdk51704

CSCdk18768

Reconfiguration attempts of resource partition on CESM-8E1 card fail intermittently. This happens if there are more than 1 service module in the shelf.

CSCdk57700

When using Ciscoview to configure a port on an SRM3T3 card on an AXIS shelf there is no option to configure the line type to dsx3M23.

CSCdk91145

Cisco View front view for BPX doesn't light FAIL LED, even though the card in failed state.

CSCdm14151

The label for frLportPortSpeed was enhanced to clearly show the units of 100's of bits per second.

Anomalies in the 9.1.06 Release of StrataView Plus

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 Conneciton section of Statistics Collection Manager. These statstic types have been added Statsstics 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+ Sevice mib for frEndPointchanType mib oject.

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' and 'LMI with Async Updates. This has been fixed by updating 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. The watchdog.conf file has been updated to not to pass `-k 6000' arguments to rtm process, solving this problem.

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 you specify Log level 5 in /usr/users/svplus/watchdog.conf file. This does not have any implication because 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.

CSCdk81857

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 you needed the packages or not. Now the INSTALL script accepts the user input and if you need to install packages, it does so else 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 continuous trap reception, the agent will then deregister the trap manager 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 you want 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 must be saved, you have 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.

The SV+ Installation process has been upgraded to restore configuration 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 endsegment 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 and 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.

Anomalies Corrected in 9.1.06 Patch 1 and Rolled up from SV+ 8.4

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

Bug ID Descriptions

CSCdj92179

The operation for modification of preferred route only through SV+ connection proxy agent is deemed not efficient. A performance enhancement targeted to this specific operation has been done in ConnProxy and cmgrd processes.

Anomalies Corrected in SV+ 9.1.06 Patch 2

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

Bug ID Descriptions

CSCdk89368

StrataView may loose Link0/Link1 connectivity with the switches, intermittently. The other symptoms of this problem are topology not getting updates for any kind of alarm on switch and traps not getting forwarded to OpenView and other OSS processes registered with RTM.

This problem has been observed only in large networks. This problem has been fixed in topod process. As a work-around one can stop and restart StrataView processes.

Anomalies Corrected in SV+ 9.1.06 Patch 3

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

Bug ID Descriptions

CSCdm02429

SV+ service agent can't set SCR to more than 4670 Cells Per Second on a AUSM-AUSM PVC, even though the maximum value depends on the port speed. This problem has been fixed ConnProxy process.

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 node name is postfixed -bpx. As a result 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 name/ip address displayed in the MIB Browser will be correct.

As a work-around 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.

CSCdm15502

SV+ install script gives the error "/tmp/.saved_sv:No such file or directory." SV+ install script also tries to install older version of WANCV, even if it finds a latest version WANCV files on the system. This problem has been observed in SV+ 9.1.06.

The error message problem has been fixed in INSTALL scripts. WANCV release notes has been updated to caution the user, that while installing if WANCV prompts the user whether to install a older version of WANCV software or not, user is required to decline by typing No.

CSCdm15555

SV+ installation doesn't have an option to upgrade from a previous releases of 9.1 to the current release of 9.1. This problem has been fixed in INSTALL scripts.

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 in the 9.1.05 Release of StrataView Plus

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 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 deiconifed. 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, 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 settings 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 timeslots.

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 you 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, you 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 you are adding or 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 you select 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) and (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 This patch 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

Note This patch is required for the users who have applied SV+ 9.1.05 Patch 3 or later

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, the 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, you will be able to change the timesync host from SCM in NodeConfig parameters.

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

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, execute the following commands as user root:

# 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 DB 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 /usr/users/svplus/tools directory are not functional.

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

Only valid if Line Framing was SET to HEC framing by doing cnftrkcommand. When 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 and 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, you will be able to change the timesync host from SCM in NodeConfig parameters.

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

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 with support contracts.

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
For example, 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>|

For example:

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

For example,

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, you 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 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 you to save and restore configuration from and to IPX/BPX/IGX switches. The configuration saved using StrataView Plus is stored under /usr/users/svplus directory using <saveid>_Cfgdir as directory name. When you need to restore a saved configuration, you must copy this directory under the SCUD home directory.

For example, if SCUD is installed under /usr/SCUD, and the current saved configuration has saveid of 'SV72,' then copy the 'SV72_Cfgdir' directory from /usr/users/svplus/ (or from other directory where files are manually copied) to the /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.

For example,

 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, you will see the Node Administration window on the creen. You can login to the switch and use the 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, you 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, you have 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 you 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 you to easily ungroupPVCs 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 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 of the node's 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 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 you select new stats or different collection intervals, 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 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 you select 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 if you are using multiple SCMs for TFTP Statistics collection. When you configure a node for TFTP collection, the SCM keeps a copy of the node configuration on the LOCAL SCM workstation.This configuration list is used by WingZ to determine what statistics have been 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 you do 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, you can select a node and apply "Show Collect Info" from node selection window.

Cisco Connection Online

Cisco Connection Online (CCO) is Cisco Systems' primary, real-time support channel. Maintenance customers and partners can self-register on CCO to obtain additional information and services.

Available 24 hours a day, 7 days a week, CCO provides a wealth of standard and value-added services to Cisco's customers and business partners. CCO services include product information, product documentation, software updates, release notes, technical tips, the Bug Navigator, configuration notes, brochures, descriptions of service offerings, and download access to public and authorized files.

CCO serves a wide variety of users through two interfaces that are updated and enhanced simultaneously: a character-based version and a multimedia version that resides on the World Wide Web (WWW). The character-based CCO supports Zmodem, Kermit, Xmodem, FTP, and Internet e-mail, and it is excellent for quick access to information over lower bandwidths. The WWW version of CCO provides richly formatted documents with photographs, figures, graphics, and video, as well as hyperlinks to related information.

You can access CCO in the following ways:

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

Note If you are a network administrator and need personal technical assistance with a Cisco product that is under warranty or covered by a maintenance contract, contact Cisco's Technical Assistance Center (TAC) at 800 553-2447, 408 526-7209, or tac@cisco.com. To obtain general information about Cisco Systems, Cisco products, or upgrades, contact 800 553-6387, 408 526-7208, or cs-rep@cisco.com.

Documentation CD-ROM

Cisco documentation and additional literature are available in a CD-ROM package, which ships with your product. The Documentation CD-ROM, a member of the Cisco Connection Family, is updated monthly. Therefore, it might be more current than printed documentation. To order additional copies of the Documentation CD-ROM, contact your local sales representative or call customer service. The CD-ROM package is available as a single package or as an annual subscription. You can also access Cisco documentation on the World Wide Web at http://www.cisco.com, http://www-china.cisco.com, or http://www-europe.cisco.com.

If you are reading Cisco product documentation on the World Wide Web, you can submit comments electronically. Click Feedback in the toolbar and select Documentation. After you complete the form, click Submit to send it to Cisco. We appreciate your comments.





hometocprevnextglossaryfeedbacksearchhelp
Posted: Mon Jun 26 21:39:27 PDT 2000
Copyright 1989 - 2000©Cisco Systems Inc.