Guest

Cisco WAN Manager

Release Notes for Cisco WAN Manager 12.0 Patch 3.0

  • Viewing Options

  • PDF (1.0 MB)
  • Feedback
Release Notes for Cisco WAN Manager 12.0.00, Patch 3

Table Of Contents

Release Notes for Cisco WAN Manager 12.0.00, Patch 3

Contents

System Requirements

CWM Server

Java Client

Standalone Statistics Manager

Solaris Patch Requirements

CWM Software Packaging

HP OpenView Requirements

INFORMIX Requirements

Wingz Requirements

Supported Hardware

Existing Hardware

New Hardware

Certified Releases

New Features and Enhancements in CWM 12.0.00

Features Introduced in CWM 12.0.00, Patch 1.1

LMI AutoSense Feature

Limitations

Features Introduced in CWM 12.0.00

ConnProvAnalyzer

Anomalies Resolved in WANCV 4.22

New Features and Enhancements in WANCV 4.20

Release 4.20 Changes

Release 4.19 Changes

Features Not Supported in WANCV 4.20

WANCV 4.20 Notes and Cautions

Performance

Features Not Supported and Known Feature Limitations in 12.0.00 and All Patches

Limitations

Ensuring the Creation of the svplus and/or wandest Username and Password

Connection Manager Limitations

HP OpenView Limitations

Issues with the CWM 12 Statistics Collection Manager

Limitations for CWM to CWM Communication

Topology Limitations

CWM 12 Notes and Cautions

Issues with Firewalls and CWM 12

Firewall on PC:

Firewall on LAN:

CWM 12.0.00 Server Installation or Upgrade to CWM 12.0.00

CWM 12.0.00, Patch 3 Installation

Installing the Informix 9.21.UC7XL Patch

Installing the Informix Patch

Installing the CWM SNMP Agent (Service Agent) Patch:

Installing the SSC (Standalone Statistics Collector) Patch on the Standalone Statistics Collector Machine:

Installing the SSM (Standalone Statistics Manager) Patch on the Standalone Statistics Manager Machine:

Installing the CWM RTMProxy Patch on the CWM Machine:

CMF Patch 2.1 Installation

WANDEST 2.4, Patch 3

Contents of This Patch

Installing the WANDEST Server Patch:

Installing the WANDEST Client Patch:

Evaluation Copy of CWM 12

Evaluation Copy Limitations

Important Configuration Notes

Naming Managed Nodes

Core File Management

C-Note/CWM Configuration

Node Numbering for Release 9.4 IGX Feeder Nodes

CWM Dedicated IP Ports

CWM Dedicated User IDs

Security Profiles

CWM Database

Connection Manager Configuration

Configuration Parameters for Connection Manager Daemon (cmgrd)

Setting up RPM Cards for Management by CiscoView from the Workstation

Configuring SNMP and SYSLOG

Configuring CiscoView for Large Networks

Creating and Configuring a CWM Auto-Restart Shell Script

Using the vi Editor to Create Your Auto-Restart Shell Script

SNMP Service Agent Release Notes

CWM SNMP Agent Configuration Notes

Error Code Changes with Release 12

Caveats

Anomalies Resolved in the CWM 12.0.00, Patch 3 Software

Known Anomalies in CWM 12.0.00, Patch 3 Software

Anomaly Status Changes in Release 12.0.00 Patch 3

Anomalies Resolved in CWM 12.0.00 Patch 2 Software

Known Anomalies in CWM 12.0.00, Patch 2 Software

Anomaly Status Changes in CWM 12.0.00, Patch 2

Anomalies Resolved in CWM 12.0.00 Patch 1.1 Software

Known Anomalies in CWM 12.0.00 Patch 1.1 Software

Anomalies Resolved in CWM 12.0.00 Software

Anomaly Status Change from Previous Releases

Anomalies Resolved in WANDEST Server 2.4, Patch 3

Anomalies Resolved in WANDEST Client 2.4, Patch 3

Related Documentation

Obtaining Documentation

Cisco.com

Product Documentation DVD

Ordering Documentation

Documentation Feedback

Cisco Product Security Overview

Obtaining Technical Assistance

Cisco Technical Support & Documentation Website

Submitting a Service Request

Definitions of Service Request Severity

Obtaining Additional Publications and Information


Release Notes for Cisco WAN Manager 12.0.00, Patch 3


Rev. D0

May 2006

The Cisco WAN Manager (CWM) 2.0.00, Patch 3 software supports the following Cisco products as of May 17, 2004:

Cisco MGX 8850 PXM45-based products running software releases 2.1.76 through 2.1.81, 3.0.10 through 3.0.25, or 4.0.00 through 4.0.15.

Cisco MGX 8950 PXM45-based products running software releases 2.1.76 through 2.1.81, 3.0.10 through 3.0.23, or 4.0.00 through 4.0.15.

Cisco MGX PXM1E-based products (8830 and 8850) running software releases 3.0.10 through 3.0.25, or 4.0.00 through 4.0.15.

Cisco MGX PXM1-based products (8230, 8250 and 8850) running software releases 1.1.31 through 1.1.34, 1.1.40 through 1.1.42, 1.2.00 through 1.2.13, or 1.2.20 through 1.2.21.

Cisco SES PNNI Controller running software releases 1.1.75 through 1.1.79, 3.0.10 through 3.0.25, or 4.0.00 through 4.0.15.

Existing Cisco WAN switching products (including the Cisco IGX 8400 series and the Cisco BPX 8600 series) running switch software (SWSW) releases 9.2.33 through 9.2.43, 9.3.05 through 9.3.47, or 9.4.00 through 9.4.10.

Existing Cisco MGX 8220 products running software releases 4.1.07 through 4.1.12, or 5.0.12 through 5.0.20.

Contents

System Requirements

CWM Software Packaging

Supported Hardware

New Features and Enhancements in CWM 12.0.00

Anomalies Resolved in WANCV 4.22

New Features and Enhancements in WANCV 4.20

Features Not Supported in WANCV 4.20

WANCV 4.20 Notes and Cautions

Features Not Supported and Known Feature Limitations in 12.0.00 and All Patches

Limitations

CWM 12 Notes and Cautions

CWM 12.0.00 Server Installation or Upgrade to CWM 12.0.00

CWM 12.0.00, Patch 3 Installation

WANDEST 2.4, Patch 3

Important Configuration Notes

Creating and Configuring a CWM Auto-Restart Shell Script

SNMP Service Agent Release Notes

Caveats

Anomaly Status Change from Previous Releases

Obtaining Documentation

Documentation Feedback

Cisco Product Security Overview

Obtaining Technical Assistance

Obtaining Additional Publications and Information

System Requirements

The following are additional notes for CWM platform requirements:

CWM 12.0 is compatible with UltraSPARC II and UltraSPARC III. The Ultra 60, Enterprise 450 and Enterprise 4500 can still be used with CWM 12.0. These were previously certified with CWM 11. Problems reported by customers who choose a non Cisco-tested configuration may take more time to troubleshoot, etc., thus a longer turnaround time.

Video is required when using the Java Client access to CWM. Video on the CWM Server is only required for user access or maintenance on the CWM Server. Video can be added to Sun Servers/Workstations. For Ultra and Enterprise this is via a video adapter.

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

The default disk size for the Informix raw database is 900 MB. However, we strongly recommend you provide 2 GB disk space for the statistics collection process. Note that if statistics collection is done using CWM then multiple 2GB partition chunks are required to be added to Informix Refer to the Cisco WAN Manager Installation for Solaris 8, OL-3837-01 for more information on disk partitioning.

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

CWM Server

Table 1 System Requirements - CWM Server 

CWM
Platform
# CPU
Min. CPU Speed MHz
Min.
RAM GB
Min.
Swap
Min. Disk
Max # PVC/SPVC Connections or
Connection segments for XPVC
Max.
# PC
Clients
Max. # Nodes
UltraSPARC III Server used for network scale testing by Cisco

Low - Medium

1

900

2 GB

4 GB

1 x 36 GB

100K

10

100

Netra 20, Sun Fire 280R

Medium

2

900

4 GB

8 GB

1 x 36 GB

200K

20

500

Netra 20, Sun Fire 280R

High -
Carrier Grade

4

900

8 GB

16 GB

2 x 36 GB

1M

40

1000

Sun Fire V880

Carrier Grade

8

900

16 GB

32 GB

2 x 36 GB

2M

100

2000

Sun Fire V880


Other UltraSPARC III Server models with equal or higher CPU speed and memory capacity can also be used.

If UltraSPARC II Servers are used, refer to the System Requirement Guidelines in the CWM release notes for Release 11.0.10.

Java Client

Table 2 System Requirements - Java Client 

CWM Java Client
Operating System
Web Browser
CPU
CPU Speed MHz
RAM
Swap
Disk
Monitor

PC

Windows 2000

Windows NT 4.0

Internet Explorer 6.0

Netscape 4.76

1
Pentium 3

750

256 MB

n/a

50 MB Free

y

SPARC10

Solaris 8

Netscape 4.76

1
450 Mhz

450

512 MB

1 GB

50 MB Free

y


Standalone Statistics Manager

Table 3 System Requirements - Standalone Statistics Collector or Manager 

SSC Platform
# CPU
Min. CPU Speed MHz
Average Network Transfer Rate (KiloByte/Sec)
RAM
Swap
Disk
Max # of stats files (15 minute collection interval)
Server used in Cisco Testing

Low

2

450

170 KB/sec

512 MB

2 GB

2 x 18 GB

350

U60

Medium #1

2

450

3.5 MB/sec

512 MB

2 GB

2 x 18 GB

700

U60

Medium #2

1

900

1.7 MB/sec

1 GB

2 GB

1 x 36 GB

700

Netra 20 or Sun Fire 280R

High

2

900

3.5 MB/sec

4 GB

8 GB

1 x 36 GB

900

Netra 20 or Sun Fire 280R


File size of 2M bytes (typically holds statistics with peak enabled for 20K endpoints).

The number of files does not increase with smaller file size.

Average Network Xfer Rate is the required TFTP/FTP throughput to collect of the Max #. Of files (combination of Server performance and network bandwidth/traffic).

If you have enabled the Parser, add the Parser System Requirement

The Standalone Statistics Collector (SSC) has the same system requirement (If you have enabled the Parser, add the Parser System Requirement to the SSC system requirements)

A maximum of 12 Standalone Statistics Collectors can be controlled by 1 Standalone Statistics Manager.

Table 4 Additional System Requirements - Parser in CWM Server, Standalone Statistics Collector or Manager 

SSM Platform
# CPU
Min. CPU Speed MHz
RAM GB
Swap
Min.
Disk
Monitor
Max # of Connection Segment Endpoints with Statistics Enabled
Server used for network scale testing by Cisco

Low

1

450

0.25

2GB

2 x 9 GB

y

40K

Ultra 10

Low - Medium

2

450

1 GB

2 GB

2 x 18 GB

y

300K

Ultra 60

Low - Medium

1

900

2 GB

4 GB

2 x 36 GB

y

750K

Netra 20, Sun Fire 280R

Medium

2

900

4 GB

8 GB

2 x 36 GB

y

2M

Netra 20, Sun Fire 280R

High - Carrier Grade

4

900

8 GB

16 GB

2 x 36 GB

y

4M

Sun Fire V880


Five statistics are collected from each connection segment endpoints and 15-minute file collection interval.

This system requirement should be added to the CWM Server requirements if the Parser Function is enabled.

4 Million endpoints with 5 Stats per endpoint requires 80 GB disk space per 24 hour. You'll need at least 3 x 36 GB Disk space.

Solaris Patch Requirements

After installing the Solaris 8 operating system, you must install the following patch cluster:

108528-13 (minimum level)

After you have installed the 108528-13 cluster install the following additional patches if they were not already installed as part of the cluster:

Required Patches

You can display which patches are already installed in the CWM workstation by entering the Solaris showrev -p command.

Patches can be obtained from SunService (if the user has a SunSpectrum contract) or from the SunSolve Recommended and Security Patches web site.

Patches are available to Sun Microsystems customers over the Web at
www.sunsolve.sun.COM/pub-cgi/show.pl?target=home

Use the search facility on the SunSolve site to search for these patches, entering only the six-digit patch ID number (do not include the two-digit patch version number). The version number can be later than the one referenced below.

111626-01

111327-02

110945-02

110934-01

110898-02

110700-01

110670-01

109326-05

108827-19 (-17 is part of 108528-13 cluster, but you need to install -19 or higher)

108652-35

108528-13

Recommended Patches

110951-01

110662-02

110615-01

110286-02

109324-02

111085-02

You can get these patches from Sun Microsystems SunSolve online patch page at the following URL:

http://sunsolve.Sun.COM/pub-cgi/show.pl?target=patches/patch-access


Note Obtaining several of these patches may require that you have a service contract with Sun.


CWM Software Packaging

The following is the list of CDs for CWM 12.0.00.

When you order the CWM package, you receive the following 3 disks:

CWM CD 1 (Disk 1). This CD contains the following:

CWM Server Software

INFORMIX Server Software Release 9.21.UC5XAI

CWM Java Client Software

CWM CD 2 (Disk 2). This CD contains the following:

CiscoView Engine 5.4.1

WANCV 4.20

Netscape Communicator 4.76

CWM Documentation CD (Disk 3). This CD contains the following:

Acrobat Reader 4.0

gzip

PDF copy of the CWM 12 documentation set


Note The documentation for WANDEST 2.4 is not included on the documentation CD. For information on WANDEST 2.4, refer to the Cisco WANDEST Installation and Reference, Release 2.4, OL-4122-01, available at this URL:
http://www.cisco.com/univercd/cc/td/doc/product/wanbu/svplus/12/index.htm.


The Service Agent software is provided on a separate CD. This CD is ordered separately from the CWM 12 release Client/Server package CD set.

Service Agent CD. This CD contains the following

CWM Service Agent Software

The Standalone Statistics Collection Manager software is also on a separate CD. This CD is ordered separately.

Standalone Statistics Collection Manager CD. This CD contains the following:

Standalone SCM Software with WANDEST Client Software incorporated

INFORMIX Server Software 9.21.UC5XAI

The WANDEST 2.4 software is provided on two separate CDs. Each CD is ordered separately.

WANDEST 2.4 Server CD

WANDEST Server Software 2.4

WANDEST 2.4 Client CD

WANDEST Client Software 2.4

The Wingz 2.5.1 software is also on a separate CD. This CD is ordered separately.

Wingz 2.5.1 CD

The Wingz version number is located on the license key (a separate piece of paper) that comes with Wingz. The version number can also be found in the HELP menu. When you click on the About box, the version number displayed is 2.5, however, clicking below the 2.5 line provides the license information followed by 1.1.7, which indicates Wingz version 2.5.1.17.

HP OpenView Requirements

CWM 12.0.00 works with HP OpenView 6.2 or 6.3 for Solaris 8.


Note You must purchase HPOV 6.2 or 6.3 directly from Hewlett Packard.


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

HP OpenView 6.2 or 6.3 is not bundled with CWM CDs. You must order HP OpenView separately. HP OpenView is used for viewing the Event Log. It is not required for any other CWM procedures.

INFORMIX Requirements

CWM 12.0.00 uses Informix9.21.UC5XAI for database operations. The INFORMIX software is bundled with CWM software on disk 1 of the CWM CD package. The INFORMIX program is automatically installed during CWM installation. Patch 3 includes the upgrade to Informix9.21.UC7XL.

Wingz Requirements

The Report Application contained in CWM 12.0.00 uses Wingz 2.5.1. For the Ad-Hoc Report Application to work properly, the Wingz DataLink program must be installed along with Wingz software.

Supported Hardware

This section provides information about the hardware supported by CWM 12.0.00.

Existing Hardware

Table 5 lists the existing hardware supported before CWM 12.0.00, Patch 3.

Table 5 Supported Existing Hardware 

Platform Series
Front Card
Back Card
Supported Release Version

IGX 8400

NPM

SCM

SWSW 9.2.33 through 9.2.43, 9.3.05 through 9.3.47, or 9.4.00 through 9.4.10

IGX 8400

NTM

BC-T1/E1/SR/Y1

SWSW 9.2.33 through 9.2.43, 9.3.05 through 9.3.47, or 9.4.00 through 9.4.10

IGX 8400

BTM

AIT-T3/E3/E2/HSS1/E1

SWSW 9.2.33 through 9.2.43, 9.3.05 through 9.3.47, or 9.4.00 through 9.4.10

IGX 8400

FRM

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

SWSW 9.2.33 through 9.2.43, 9.3.05 through 9.3.47, or 9.4.00 through 9.4.10

IGX 8400

FTM

FPC-V35/T1/E1/X.21

SWSW 9.2.33 through 9.2.43, 9.3.05 through 9.3.47, or 9.4.00 through 9.4.10

IGX 8400

HDM

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

SWSW 9.2.33 through 9.2.43, 9.3.05 through 9.3.47, or 9.4.00 through 9.4.10

IGX 8400

LDM

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

SWSW 9.2.33 through 9.2.43, 9.3.05 through 9.3.47, or 9.4.00 through 9.4.10

IGX 8400

CVM

BC-T1/E1/J1/Y1/SR

SWSW 9.2.33 through 9.2.43, 9.3.05 through 9.3.47, or 9.4.00 through 9.4.10

IGX 8400

UVM

UVI-2T1EC/2E1EC

SWSW 9.2.33 through 9.2.43, 9.3.05 through 9.3.47, or 9.4.00 through 9.4.10

IGX 8400

UFM-C

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

SWSW 9.2.33 through 9.2.43, 9.3.05 through 9.3.47, or 9.4.00 through 9.4.10

IGX 8400

UFM-U

UFI-V35/X21/HSI

SWSW 9.2.33 through 9.2.43, 9.3.05 through 9.3.47, or 9.4.00 through 9.4.10

IGX 8400

ARM

ARI

SWSW 9.2.33 through 9.2.43, 9.3.05 through 9.3.47, or 9.4.00 through 9.4.10

IGX 8400

UXM

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

SWSW 9.2.33 through 9.2.43, 9.3.05 through 9.3.47, or 9.4.00 through 9.4.10

BPX 8600

BCC

BCC-bc/3-bc

SWSW 9.2.33 through 9.2.43, 9.3.05 through 9.3.47, or 9.4.00 through 9.4.10

BPX 8600

ASM

LM-ASM

SWSW 9.2.33 through 9.2.43, 9.3.05 through 9.3.47, or 9.4.00 through 9.4.10

BPX 8600

BNI-T3

LM-3T3

SWSW 9.2.33 through 9.2.43, 9.3.05 through 9.3.47, or 9.4.00 through 9.4.10

BPX 8600

BNI-E3

LM-3E3

SWSW 9.2.33 through 9.2.43, 9.3.05 through 9.3.47, or 9.4.00 through 9.4.10

BPX 8600

BNI-155

LM-OC3-SMF/SMFLR/MMF

SWSW 9.2.33 through 9.2.43, 9.3.05 through 9.3.47, or 9.4.00 through 9.4.10

BPX 8600

ASI-1

LM-2T3/2E3

SWSW 9.2.33 through 9.2.43, 9.3.05 through 9.3.47, or 9.4.00 through 9.4.10

BPX 8600

ASI-155

LM-2OC3-SMF/SMFLR/MMF

SWSW 9.2.33 through 9.2.43, 9.3.05 through 9.3.47, or 9.4.00 through 9.4.10

BPX 8600

BXM-T3/E3

T3/E3-BC

SWSW 9.2.33 through 9.2.43, 9.3.05 through 9.3.47, or 9.4.00 through 9.4.10

BPX 8600

BXM-15 5

MMF/SMF/SMFLR-155

SWSW 9.2.33 through 9.2.43, 9.3.05 through 9.3.47, or 9.4.00 through 9.4.10

BPX 8600

BXM-622

MMF/SMF/SMFLR-622

SWSW 9.2.33 through 9.2.43, 9.3.05 through 9.3.47, or9.4.00 through 9.4.10

SES PNNI Controller

SES-PXM

T3/E3/OC3/OC12

1.1.75 through 1.1.79, 3.0.10 through 3.0.25, or 4.0.00 through 4.0.15

SES PNNI Controller

SES-PXM

PXM-UIA

1.1.75 through 1.1.79, 3.0.10 through 3.0.25, or 4.0.00 through 4.0.15

MGX 8220

FRSM-4P

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

4.1.07 through 4.1.12, or 5.0.12 through 5.0.20

MGX 8220

CESM-4P

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

4.1.07 through 4.1.12, or 5.0.12 through 5.0.20

MGX 8220

AUSM-4P

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

4.1.07 through 4.1.12, or 5.0.12 through 5.0.20

MGX 8220

FRSM-8P

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

4.1.07 through 4.1.12, or 5.0.12 through 5.0.20

MGX 8220

AUSM-8P

RJ48-8E1/8T1

4.1.07 through 4.1.12, or 5.0.12 through 5.0.20

MGX 8220

CESM-8P

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

4.1.07 through 4.1.12, or 5.0.12 through 5.0.20

MGX 8220

IMATM-B

RJ48-T3T1/E3E1

SMB-E3E1

4.1.07 through 4.1.12, or 5.0.12 through 5.0.20

MGX 8220

FRSM-HS1

HSI-4X21/3HSSI

4.1.07 through 4.1.12, or 5.0.12 through 5.0.20

MGX 8220

BNM-T3/E3

T3E3-B/D

4.1.07 through 4.1.12, or 5.0.12 through 5.0.20

MGX 8220

BNM-155

155-SMF

4.1.07 through 4.1.12, or 5.0.12 through 5.0.20

MGX 8220

SRM

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

4.1.07 through 4.1.12, or 5.0.12 through 5.0.20

MGX 8220

ASC

ASC-LM

4.1.07 through 4.1.12, or 5.0.12 through 5.0.20

MGX 8220

FRSM-VHS

HS2

4.1.07 through 4.1.12, or 5.0.12 through 5.0.20

MGX 8220, MGX 8230, MGX 8250, MGX 8850 PXM1

AUSM Model B

8T1/E1

4.1.07 through 4.1.12, or 5.0.12 through 5.0.20, 1.1.31 through 1.1.34, 1.1.40 through 1.1.42, 1.2.00 through 1.2.13, or 1.2.20 through 1.2.21

MGX 8230, MGX 8250, MGX 8850 PXM1

PXM1

T3/E3/OC3/OC12

1.1.31 through 1.1.36, 1.1.40 through 1.1.42, 1.2.00 through 1.2.13, or 1.2.20 through 1.2.21

MGX 8230, MGX 8250, MGX 8850 PXM1

FRSM-VHS

HS2/T3/E3/2CT3/HS2B

1.1.40 through 1.1.42, 1.2.00 through 1.2.13, or 1.2.20 through 1.2.21

MGX 8230, MGX 8250, MGX 8850 PXM1

FRSM-8P

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

1.1.40 through 1.1.42, 1.2.00 through 1.2.13, or 1.2.20 through 1.2.21

MGX 8230, MGX 8250, MGX 8850 PXM1

CESM-8P

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

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

1.1.40 through 1.1.42, 1.2.00 through 1.2.13, or 1.2.20 through 1.2.21

MGX 8230, MGX 8250, MGX 8850 PXM1

CESM

T3/E3

1.1.40 through 1.1.42, 1.2.00 through 1.2.13, or 1.2.20 through 1.2.21

MGX 8230, MGX 8250, MGX 8850 PXM1

SRM

LM-3T3

1.1.40 through 1.1.42, 1.2.00 through 1.2.13, or 1.2.20 through 1.2.21

MGX 8230, MGX 8250, MGX 8850 PXM1

VISM-8T1

AX-RJ48-8T1

AX-R-RJ48-8T1

1.1.40 through 1.1.42, 1.2.00 through 1.2.13, or 1.2.20 through 1.2.21

MGX 8230, MGX 8250, MGX 8850 PXM1

VISM-8E1

AX-SMB-8E1

AX-RJ48-8E1

AX-R-SMB-8E1

AX-R-RJ48-8E1

1.1.40 through 1.1.42, 1.2.00 through 1.2.13, or 1.2.20 through 1.2.21

MGX 8230, MGX 8250, MGX 8850 PXM1

VISM-PR

RJ48-T1/E1 and SMB-E1

1.2.10 through 1.2.13, or 1.2.20 through 1.2.21

MGX 8950 (PXM45)

AXSM/B

T3/E3

2.1.76 through 2.1.81, 3.0.10 through 3.0.23, or 4.0.00 through 4.0.15

MGX 8950 (PXM45)

AXSM/B

OC3

2.1.76 through 2.1.81, 3.0.10 through 3.0.23, or 4.0.00 through 4.0.15

MGX 8950 (PXM45)

AXSM/B

OC12

2.1.76 through 2.1.81, 3.0.10 through 3.0.23, or 4.0.00 through 4.0.15

MGX 8950 (PXM45)

AXSM/B

OC48

2.1.76 through 2.1.81, 3.0.10 through 3.0.23, or 4.0.00 through 4.0.15

MGX 8950 (PXM45)

PXM45

PXM-HD, PXM-UI

2.1.76 through 2.1.81, 3.0.10 through 3.0.23, or 4.0.00 through 4.0.15

MGX 8950 (PXM45)

PXM45B

PXM-HD, PXM-UI

2.1.76 through 2.1.81, 3.0.10 through 3.0.23, or 4.0.00 through 4.0.15

MGX 8950 (PXM45)

RPM-PR

Ethernet, Fast Ethernet

3.0.10 through 3.0.23, or 4.0.00 through 4.0.15

MGX 8950 (PXM45)

RPM-XF

MGX-1GE and MGX-1OC12POS

3.0.10 through 3.0.23, or 4.0.00 through 4.0.15

MGX 8850 (PXM45)

AXSM/A

AXSM/B

T3/E3

2.1.76 through 2.1.81, 3.0.10 through 3.0.25, or 4.0.00 through 4.0.15

MGX 8850 (PXM45)

AXSM/A

AXSM/B

OC3

2.1.76 through 2.1.81, 3.0.10 through 3.0.25, or 4.0.00 through 4.0.15

MGX 8850 (PXM45)

AXSM/A

AXSM/B

OC12

2.1.76 through 2.1.81, 3.0.10 through 3.0.25, or 4.0.00 through 4.0.15

MGX 8850 (PXM45)

AXSM/A

AXSM/B

OC48

2.1.76 through 2.1.81, 3.0.10 through 3.0.25, or 4.0.00 through 4.0.15

MGX 8850 (PXM45)

AXSM-E

T3/E3

2.1.76 through 2.1.81, 3.0.10 through 3.0.25, or 4.0.00 through 4.0.15

MGX 8850 (PXM45)

AXSM-E

OC3

2.1.76 through 2.1.81, 3.0.10 through 3.0.25, or 4.0.00 through 4.0.15

MGX 8850 (PXM45)

AXSM-E

OC12

2.1.76 through 2.1.81, 3.0.10 through 3.0.25, or 4.0.00 through 4.0.15

MGX 8850 (PXM45)

AXSM-E

OC48

2.1.76 through 2.1.81, 3.0.10 through 3.0.25, or 4.0.00 through 4.0.15

MGX 8850 (PXM45)

PXM45

PXM-HD, PXM-UI

2.1.76 through 2.1.81, 3.0.10 through 3.0.25, or 4.0.00 through 4.0.15

MGX 8850 (PXM45)

PXM45B

PXM-HD, PXM-UI

2.1.76 through 2.1.81, 3.0.10 through 3.0.25, or 4.0.00 through 4.0.15

MGX 8850 (PXM45)

RPM-XF

MGX-1GE and MGX-1OC12POS

3.0.10 through 3.0.25, or 4.0.00 through 4.0.15

MGX 8850 (PXM45)

RPM-PR

Ethernet, Fast Ethernet

3.0.10 through 3.0.25, or 4.0.00 through 4.0.15

MGX 8850 (PXM45)

VISM-PR

RJ48-T1/E1 and SMB-E1

3.0.10 through 3.0.25, or 4.0.00 through 4.0.15

MGX 8850 (PXM1E)

PXM1E

8 Port 155

3.0.10 through 3.0.25, or 4.0.00 through 4.0.15

MGX 8850 (PXM1E)

PXM1E

8 Port T3/E3

3.0.10 through 3.0.25, or 4.0.00 through 4.0.15

MGX 8850 (PXM1E)

RPM-PR

Ethernet, Fast Ethernet

3.0.10 through 3.0.25, or 4.0.00 through 4.0.15

MGX 8850 (PXM1E)

VISM-PR

RJ48-T1/E1 and SMB-E1

3.0.10 through 3.0.25, or 4.0.00 through 4.0.15

MGX 8850 (PXM1E)

AUSM Model B

8T1/E1

3.0.10 through 3.0.25, or 4.0.00 through 4.0.15

MGX 8850 (PXM1E)

FRSM-8P

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

3.0.10 through 3.0.25, or 4.0.00 through 4.0.15

MGX 8850 (PXM1E)

CESM-8P

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

3.0.10 through 3.0.25, or 4.0.00 through 4.0.15

MGX 8850 (PXM1E)

FRSM-HS2B

8 port 12in1, HSSI

3.0.10 through 3.0.25, or 4.0.00 through 4.0.15

MGX 8850 (PXM1E)

SRM/E

1 port OC3/STM1 (SMF-IR, SMF-LR, SMF-Electrical)

3.0.10 through 3.0.25, or 4.0.00 through 4.0.15

MGX 8230, MGX 8250, MGX 8850 (PXM1)

FRSM-HS2B

8 port 12in1, HSSI

1.2.00 through 1.2.13, or 1.2.20 through 1.2.21

MGX 8230, MGX 8250, MGX 8850 (PXM1)

SRM/E

1 port OC3/STM1 (SMF-IR, SMF-LR, SMF-Electrical)

1.2.00 through 1.2.13, or 1.2.20 through 1.2.21

MGX 8230, MGX 8250, MGX 8850 (PXM1)

RPM/B

Ethernet, Fast Ethernet

1.2.00 through 1.2.13, or 1.2.20 through 1.2.21

MGX 8230, MGX 8250, MGX 8850 (PXM1)

RPM-PR

Ethernet, Fast Ethernet

1.2.00 through 1.2.13, or 1.2.20 through 1.2.21

MGX 8230, MGX 8250, MGX 8850 (PXM1)

VISM-PR

RJ48-T1/E1 and SMB-E1

1.2.00 through 1.2.13, or 1.2.20 through 1.2.21

MGX 8950 (PXM45)

AXSM-XG

OC192

4.0.00 through 4.0.15

MGX 8950 (PXM45)

AXSM-XG

OC48

4.0.00 through 4.0.15

MGX 8950 (PXM45)

PXM45/C

PXM-HD, PXM-UI S3/B

4.0.00 through 4.0.15

MGX 8850 (PXM45)

PXM45/C

PXM-HD, PXM-UI S3/B

4.0.00 through 4.0.15

MGX 8850 (PXM45)

FRSM-8P

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

4.0.00 through 4.0.15

MGX 8850 (PXM45)

FRSM-HS2/B

8 port 12in1, HSSI

4.0.10 through 4.0.15

MGX 8850 (PXM45)

FRSM-VHS

2T3E3

4.0.10 through 4.0.15

MGX 8850 (PXM45)

CESM-8P

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

4.0.00 through 4.0.15

MGX 8850 (PXM45)

FRSM-VHS

2CT3

4.0.00 through 4.0.15

MGX 8850 (PXM45)

SRM/E

1 port OC3/STM1 (SMF-IR, SMF-LR, SMF-Electrical)

4.0.00 through 4.0.15

MGX 8830/8850 (PXM1E)

PXM1E

8 port OC3 STM1

4.0.00 through 4.0.15

MGX 8830/8850 (PXM1E)

FRSM-VHS

2CT3

4.0.00 through 4.0.15


New Hardware

No new hardware supported in CWM 12.0.00, Patch 3.

Certified Releases

The following releases were tested with CWM 12.0.00, Patch 3:

BPX/IGX Switch Software:

Switch Software 9.4.10

Switch Software 9.3.47

MGX 8230/8250/8850 (PXM1) Switch

MGX 1.2.21

MGX 8850/8950 (PXM45/PXM-1E) Switch

MGX 4.0.15

BPX SES Shelf

SES 4.0.15

MGX 8220 Shelf

MGX 8220 5.0.20

VISM

VISM 3.2.00 (VISM-PR 3.1.2)

New Features and Enhancements in CWM 12.0.00

No new features were introduced in patches 2 and 3 of CWM 12.0.00. See these sections for new features introduced in CWM 12.0.00 and CWM 12.0.00, Patch 1.1:

Features Introduced in CWM 12.0.00, Patch 1.1

Features Introduced in CWM 12.0.00

Features Introduced in CWM 12.0.00, Patch 1.1

This section describes the new features introduced in the CWM 12.0.00, Patch 1.1.

MGX 8850, Release 4

Support for FRSM-2T3E3

Support for FRSM-HS2/B

Support for the LMI AutoSense feature on the FRSM -8T1/E1 and FRSM -VHS cards on PXM1, PXM-45 and PXM-1E-based MGX families of switches.

MGX 8950, Release 4

Support for AXSM/B Feeder Nodes (MGX 8950 to PXM1-based MGX nodes)

Release 1.2.21 (8850, 8250, 8230 with PXM1)

Support for the LMI AutoSense feature on the FRSM -8T1/E1 and FRSM -VHS cards on PXM1, PXM-45 and PXM-1E-based MGX families of switches.

MGX 8850 and 8830 Release 4 (PXM1E-based nodes)

Support for the LMI AutoSense feature on the FRSM -8T1/E1 and FRSM -VHS cards on PXM1, PXM-45 and PXM-1E-based MGX families of switches.

CWM-specific Enhancements

Graphical User Interface Management of Multi Peer Groups
Refer to the Cisco WAN Manager User's Guide for Release 12 for information on the Multi Peer Group Graphical User Interface.

LMI AutoSense Feature

The LMI AutoSense feature on the Frame Relay service modules on MGX switches enables a frame relay port to detect the LMI type supported by frame relay customer premise equipment. This autosensing feature avoids the need to configure the LMI type on each frame relay port.The LMI AutoSense feature is supported on the FRSM-8T1/E1 and FRSM-VHS(2CT3, 2T3, 2E3, 2HS2, 2HS2B) service modules on PXM1/(PXM45A/B)/PXM1E platforms.

The LMI AutoSense feature is supported for Frame Relay and FUNI port types. It is not applicable for Frame Forwarding port types. The detected LMI types will be of the following UNI types:

AnnexD-UNI

AnnexA-UNI

StrataLMI

Limitations

The LMI AutoSense feature is not supported on NNI interfaces.

The LMI AutoSense feature is configurable at a per port level.

The following sections describe the changes incorporated into CWM 12, patch 1.1 to support the LMI AutoSense feature.

Service Agent Component

The new svFrPortLmiCnfType mib object has been added to the svFrPortTable in the PortGroupService.mib.

svFrPortLmiCnfType OBJECT-TYPE 
SYNTAX INTEGER 
{ manual(1),
autosense(2)}
ACCESS read-write
STATUS mandatory
DESCRIPTION
"
          RANGE           : 1,2
          UNIT            : -
          DEFAULT         : 1(manual)
          FORMAT          : -
          APPLICABLE TO   : FRSM-8T1/E1, FRSM-VHS(2CT3, 2T3, 2E3, 2HS2, 2HS2B)
                            on PXM1/(PXM45 A/B)/PXM1E platforms. This object
                            enables/disables the port LMI signalling autosense.
                            Setting this object to 2 puts the port to autosense LMI
                            signalling type.
"
DEFVAL { manual }                  
::= { svFrPortEntry 64 }

The Service Agent supports the following SNMP operations on the svFrPortLmiCnfType MIB object:

1. SNMP SET using the svFrPortLmiCnfType MIB object during addition of FRSM port.

2. SNMP SET using the svFrPortLmiCnfType MIB object during modification of FRSM port.

3. SNMP GET on the svFrPortLmiCnfType MIB object.

The Service Agent will not do any validation of the new svFrPortLmiCnfType MIB object. Multiple SET operations on this object are allowed.

Trap Support

No new traps are sent specific to this feature. A generic Config change trap (trap no 50600 for PXM1-based MGX switches, trap no 50315 for PXM1E or PXM45-based MGX switches) will be generated whenever there is a change in LMI type.

Database Support

In support of the LMI AutoSense feature, the following new field has been added to the FRP table in the Database Schema:

Table 6 New lmi_type Field in the frp Table

Field Name
Data Type

lmi_type

integer


Network Browser Support

The Network Browser displays the lmi_type parameter for FRSM ports. Figure 1 below displays the Network Browser with LMI Type for FRSM ports selected. The settings can be either manual (the default) or autosense.

Figure 1 LMI-AutoSense Feature in the Network Browser

Cisco View GUI

CiscoView supports the LMI AutoSense Feature (displays the new MIB object portLmiCnfType) for the following cards:

:

Table 7 FRSM Cards supporting LMI AutoSense Feature 

Card
shelfFunctionModuleType

FRSM-8T1

frsm-8T1 (35)

FRSM-8E1

frsm-8E1 (36)

FRSM-2CT3

frsm-2ct3 (130)

FRSM-2T3

frsm-2t3 (131)

FRSM-2E3

frsm-2e3 (132)

FRSM-HS2

frsm-hs2 (133)

FRSM-HS2B-HSSI

frsm-hs2b-hssi (136)


The new object will be included as a read-write object in the existing "Ports" dialog category for the above mentioned cards at the Port Level. This object can be set after the creation of the row.

Navigation: Right Click on a Line and Choose "Configure" or Double Click on Line --> Logical Ports

Figure 2 Setting up LMI AutoSense in the Logical Port Configuration Window

Features Introduced in CWM 12.0.00

This section describes the new features introduced in the CWM 12.0.00:

MGX 8850, Release 4

Support for PXM45/C (512MB memory, memory protection feature, and Ethernet Controller)

Support for Cellbus-based Frame Relay and Circuit Emulation support on PXM45-based switches (CESM-8T1E1, CESM-8T1/B, FRSM-VHS 2CT3, FRSM-8T1E1)

Support for the IMA UNI Port on the AXSM-E32T1E1 service module

MGX 8950, Release 4

Support for PXM45/C (512MB memory, memory protection feature, and Ethernet Controller)

Support for AXSM-XG 4-Port Channelized OC-48 Service Module (Unchannelized and Channelized to OC-12/STM-4, OC-3/STM1 and T3/E3 logical ATM interfaces) and the AXSM-XG 1-Port OC-192 Service Module

SES, Release 4

Support for configuring PCR to burst to line rate on SPVC connections using the Connection Manager GUI

Support for configuring PCR to burst to line rate on SPVC connections using the CWM Service Agent

BPX 8600 and IGX 8400, Release 9.4.00 support

Support for configuring and managing hybrid PNNI connections that allow the use of the IGX as a feeder node to the PNNI network (the IGX UXM can be connected to the BPX-SES, the PXM1E, or the AXSM-E)

Release 1.2.20 (8850, 8250, 8230 with PXM1)

Support for Configurable AUSM CAC. You can configure the AUSM card to use either PCR or SCR for CAC. The default is PCR.

MGX 8850 and 8830 Release 4 (PXM1E-based nodes)

Support for the provisioning and management of the PXM1E 8-Port OC-3 & STM-1 Service Module with the MCC - 8 - 155 back card and/or the 512M memory backcard

Support for the provisioning and management of the CESM-8T1E1, CESM-8T1/B, FRSM-VHS 2CT3, FRSM-8T1E1 Service Modules

Support for the IMA UNI Port on the PXM1E-T1E1

Support for PXM1E on-line diagnostics traps through the Service Agent

Support for Virtual Trunk and Virtual UNI on the PXM1E management through the Service Agent

CWM-specific Enhancements

Evaluation Copy of CWM 12
The 90-day evaluation copy of CWM gives you the opportunity to try CWM for a 90-day period.

Enhanced Standalone Statistics Collection Management
The enhanced Standalone Statistics Collection Manager is now totally independent from the CWM server. You can perform maintenance on CWM without affecting the SCM operations and vice versa.
There are 2 supported configurations:
1. Standalone Statistics Manager (SSM)
The Standalone Statistics Manager (SSM) consists of the Standalone SCM with Control Server, Collection Server and Statistics Parser installed together on a workstation separate from the CWM server workstation The WANDEST server software must be installed and configured on the CWM server workstation and the WANDEST client software must be installed on the standalone SCM workstation.
SSM uses the WANDEST client to synchronize the network equipment data (node and card) from the CWM server workstation.
2. Standalone Statistics Collector (SSC)
Standalone SCM can be configured as a Standalone Statistics Collector (SSC) to work with SSM or CWM Server to further distribute the statistics collection function to a second separate workstation (separate from the SSM). In this configuration, the Statistics Collection Controller and, optionally, the Statistics Parser function will still reside on either the SSM or the CWM server.

Enhanced SSC/SSM redundancy

Point-to-multipoint SPVC Provisioning

Single-end SPVC Provisioning

SNMP Community String configuration using Secure Shell (SSH)

Enhanced Audit Trail Log
The Audit Trail Logging feature now logs all Read-only and Read-Write operations performed by the Java-based CWM GUI and CiscoView.

Network Topology now provides primary and secondary status of the ports configured for SONET Automatic Protection Switch.

PNNI Multi-peer Group configuration via Service Agent

Enhanced Network Events Monitoring
BPX related 20000 Series and 30000 Series traps are forwarded to port 162 for HP OpenView and to RTM for Service Agent. The Source IP address in the BPX 1000 series Traps reflects the IP address of the associated node instead of the CWM IP address. BPX 1000 series traps are only forwarded to port 162, not to RTM.

PNNI Persistent Physical Topology
CWM 12 adds support for routing trunk persistency.

Enhanced PNNI Statistics Collection
CWM Statistics Collection Manager now collects historical PNNI related statistics from PXM45/B, PXM45/C and PXM1E-based nodes.

Enhanced Scalability for Large-Scale Network Management

Support for WANDEST 2.4

Support for AXSM-E Port Statistics

Support for new PXM1 Port Statistics

Support for additional AUSM Port Statistics

Support for additional FRSM Connection and Port Statistics

XPVC/XPVP Management Enhancement
XPVC connection data no longer needs the manual XPVC grooming tool during upgrade to CWM 12. XPVC connections are now discovered from the network by CWM.

Preferred Route Provisioning

Support for Closed User Groups

For information on WANDEST 2.4, refer to the Cisco WANDEST Installation and Reference, Release 2.4, OL-4122-01, available at this URL:

http://www.cisco.com/univercd/cc/td/doc/product/wanbu/svplus/12/index.htm.

ConnProvAnalyzer

This new tool analyzes connection provisioning delay and errors using available conn proxy log files and generates reports and creates a separate log file for errors. The off-line tool is located in ~svplus/tools/ConnProvAnalyzer.

The generated data can be used for plotting in Wingz or Microsoft Excel.

This tool extracts CNPA pattern entry from the ConnProxy log messages and will do analysis for successful requests then writes into .csv and .req files. The .csv data can be used for plotting graphs by using applications like Excel or Wingz.

In the .csv file, column-I indicates the connection & column-II indicates Provisioning time.

Xaxis: represents the Connection

Yaxis: represents the Provisioning Time

Plotting a Graph in Excel:


Step 1 Invoke Excel and open the .csv file.

Step 2 Select A, B columns for all rows (or for how many ever connection need to be plotted)

Step 3 Click on "Chart wizard"

Step 4 Select any type of graph and walk-through the steps.


Plotting a graph in Wingz:


Step 1 Invoke wingz and open the .csv file.

Step 2 Select Text Type "comma delimited".

Step 3 Click OK.

Step 4 Select Columns A,B columns

Step 5 Click on Tools->"graph icon (on the left side)". The cursor now changes to "+"

Step 6 Select the columns A,B (Graph will use only these selected rows to plot)

Step 7 Select Chart->Types->XY


Anomalies Resolved in WANCV 4.22

As part of CWM 11, Patch 3, the CiscoView MSSBU device packages (WANCV) were upgraded to Release 4.22 to support CiscoView 5.4.1.

The bugs listed in Table 8 were fixed in WANCV Release 4.22:

Table 8 Bugs Fixed in WANCV Release 4.22 

Bug ID
Description

CSCea22451

CV 5.4 gave failed to refresh error against MGX 8850

CSCdz69325

Refreshed failed errors on view of MGX 8850 on Release 1 chassis


New Features and Enhancements in WANCV 4.20

Release 4.20 Changes

Release 4.20 introduces support for the LMI AutoSense feature. Refer to the "LMI AutoSense Feature" section for more information on this feature.

Release 4.19 Changes

As part of CWSM 12, the CiscoView MSSBU device packages (WANCV) were upgraded to Release 4.19 to support CiscoView 5.4.1.

Displays the correct connector to UAI-4E1-DB15 backcard (IGX)

Displays the correct orientation for PXM-UI-S3 and MCC-8-OC3 back cards (BPX-SES)

Cosmetic changes to the PNNI Summary Address dialog window Create button

Support for MCC-8-OC3 backcard for PXM1E is added.

Added rsrcPartiVsiBwOverbooking support for Rel 9.4.

Performance improvement when RPM cards are present without back cards.

On-Line Help support for PXM1E-based & PXM45-based MGX 8800-series/MGX 8950/VSC packages.

Supports AXSM-XG with clear channel and channelized on the Cisco MGX 8950.

Adds SCR based CAC support for AUSM and PXM Cards.

Table 9 shows the bugs fixed in release 4.19.

Table 9 Bugs Fixed in 4.19 

Bug ID
Description

CSCdz21732

AXSMXG ds3 Channelization: Xtm Clock source is not supported

CSCdz77336

PNNI Interface Configuration menu option missing for SES

CSCdz90328

CV missing mibs in VISM Rsvp dialog

CSCea01506

CV RSVP ip addr & port should be in decimal value

CSCea01530

CV spelling mistake for VISM ds0 config dialog

CSCea16488

CV fails to create PNNI controller on PXM1e-8OC3 card


Features Not Supported in WANCV 4.20

The following features are not supported in WANCV 4.20:

The security feature is not supported in conjunction with CWM 12.

Hot swap polling frequency is 100 seconds and is not user modifiable.

The Telnet button will show an error if a path to "xterm" is not present in the user's PATH environment variable.

The write community string should not be configured to "private" by the user.

The RPM card's community string is not configurable, and has to be set to the default "POPEYE".

The Cisco Support button will not result in Cisco TAC support.

The CCO button will not connect a Web browser to Cisco Connection Online (CCO).

WANCV 4.20 Notes and Cautions

When there is a card mismatch go to the "card summary" display to see the indicator of "mismatchwithParent".

The LEDs displayed in the chassis screen only convey card status for the selected card and not alarm status in the node. The "node alarm status" is shown at the top of a PXM. The "port" LED's red or yellow colors actually represent an "alarm" state for a physical interface.

The VISM Ds0 Config screen shows parameters as configurable that are not applicable for the VISM line type (E1). In the vism Ds0 Config screen under the Line Config. screen, the "Insert Local CAS" and "Local CAS Pattern" parameters are not greyed out. When you have a E1 VISM card you are not allowed to modify the local CAS type (cwmVismDs0InsertLocalCas) or the local CAS bit pattern (cwmVismDs0LocalCasPattern). If you try to change these values the system displays an error.

Performance

The various timers and retry counter should be configured from the Preference menu. For a typical installation, Polling and Monitoring should be about 60 seconds and Timeout should be at least 15 seconds. Faster polling and monitoring values can be configured if conditions permit. One retry is the recommended configuration.


Note Performance is degraded when managing MGX devices with missing or failed service modules, or RPM modules that do not have SNMP enabled. Missing service modules are shown in CiscoView with a red alarm indicator, not as an empty slot.


Features Not Supported and Known Feature Limitations in 12.0.00 and All Patches

The following features are not supported in CWM 12.0.00 and all patches:

You cannot perform an image download (FW download) from the CWM GUI for the NPM, HDM and NTM cards of the IGX switch. If you try to perform an image download on these cards from the Image Download GUI, you will receive an error message, stating "Image download operation not supported for node with card type 0."

XPVC support on the FRSM T3E3 in PXM45-based switches has not been not tested

StandAlone Stats Parser and Standalone Stats Collector with Parser are no longer supported in CWM 12. This feature has been replaced by the re-architected Standalone Statistics Manager.

The URM service module is not supported by CWM.

The following features introduced in VISM 3.1 are not accessible from CWM:

TGCP

Dynamic Payload

T.38 Fax Relay.

The CWM database is not populated with the MPG configuration data. Instead, the Service Agent accesses the configuration directly from the switch.

New preferred routes can be created using CLI or CWM Service Agent, but not with the CWM GUI.

The preferred route indicator of a connection is not available in this release.

Limitations

1. CWM can manage up to 40 different disjoint AutoRoute networks, provided all the network elements have unique network IP addresses and unique names across all the networks managed by CWM. There is no limitation for the number of PNNI networks.

2. Pointing multiple CWM workstations at the same gateway node is not recommended unless Persistent Topology is enabled.

3. CWM must be started from a CDE environment.

4. CWM does not support use of the korn shell.

5. When /usr/users gets 100% full, orbix processes are not able to write to the disk and cannot continue operations.

Correct the problem by first freeing up some disk space in /usr/users, then restarting the orbix processes and CWM using the following procedure:


Step 1 Stop core, exit out of the CWM prompt

Step 2 Run stoporbix2000 script

Step 3 Type CWM, you should see 'Starting Orbix..." in ~svplus/log/.startStopOrbix.log file.

Step 4 Start core.


6. When the client machine cannot be pinged from the server the following message may be seen on the CWM workstation:

Exception raised while calling activateLease on 
pseudoServer.IT_ATLI_IOP:CONNECTION_CREATION_TIMEOUT

The error message is printed when server tries to contact the client, but is not able to. The call is initiated by the GUI client for activating the lease plugin on the client to detect server crash.

The problem is with the client machine DNS setup. The client machine cannot be pinged from the server.

The DNS is setup so that the client can communicate with the server, but when server tries to contact client machine it fails.

The resolution is to make sure the client machine is pingable from the CWM workstation.

Possible reasons for the server not being able to ping the client are:

There may be a firewall on the client PC that prevents it from being seen from outside.

The network routing from the server to the client is not setup properly.

7. When SSM (standalone stats manager) is installed with SCMGateway setup, SCM GUI does not open when the Primary SSM and Secondary SSM are started simultaneously (or within a time gap of 30 seconds to a minute).

Avoid this problem by waiting 2-3 minutes after starting core in the Primary SSM before starting core in the Secondary SSM in Gateway.

8. When there is a shortage of shared memory, the Informix engine may generate an operating system error. The following example from the online.log shows this error:

shmat: [22]: operating system error
18:45:49  shmat: [22]: operating system error
18:45:57  Error writing '/tmp/shmem.1fd4555c.0' errno = 4
18:45:57  mt.c, line 10260, thread 7148, proc id 1008, errors occurred during mt_
notifyvp.

When this error occurs, statsparser is not able to do any database related operation.

The error can be resolved temporarily by changing the /etc/system configuration as follows:

forceload: sys/shmsys
forceload: sys/semsys
set shmsys:shminfo_shmmax=1073741824
set semsys:seminfo_semaem=16384
set semsys:seminfo_semmap=5000
set semsys:seminfo_semmni=8192
set semsys:seminfo_semmns=8192
set semsys:seminfo_semmnu=8192
set semsys:seminfo_semume=256
set semsys:seminfo_semvmx=50000
set shmsys:shminfo_shmmin=256
set shmsys:shminfo_shmmni=32000
set shmsys:shminfo_shmseg=256
set semsys:seminfo_semmsl=100

The long-term solution is to increase the amount of memory to support 2 million connections consistently.

9. When using inband management, only 50 K connections are supported on the BPX-SES. To manage 100 K connections on the BPX-SES, set up CWM for out-of-band management.

10. If an atm IP interface (also called In-band interface) is being used to manage the switch from the NMS, not all node-bringup traps may be received by the NMS. The ATM connections required for in-band management may take time to get routed on node-bringup and are hence not available for trap delivery at this initialization time. If this initialization time is an issue, the workaround is to set up CWM for out-of-band management.

11. CiscoView behavior after using the browser's refresh button is unpredictable. There is no reason to refresh the window, as CiscoView is refreshed automatically, based on the refresh/polling period.

The refresh/polling period can be set via the Preferences option.

If, after using the browser's refresh button, the browser hangs, close the browser and launch a new session.

12. Allow a 2-3 minutes period between enabling or disabling statistics operations on the same BPX or IGX node. Whenever enabling/disabling of statistics is done on a BPX or IGX node, and the switch is in the process of configuring statistics, doing a second enabling/disabling of statistics will fail.

13. If Start Collection on SCM GUI takes a long time, investigate whether collection was started with an IP address that was not reachable. Either in-band or out of band was not reachable. Start collection with a reachable IP address. If the in-band IP address is reachable then start collection with in-band IP address. If out of band is reachable, start collection with out of band.

14. The SSM statistics database can go out of sync with node_ids on CWM after a coldstart -F is executed on the server. Stop collection and disable collection before doing a coldstart -F to ensure that the node ids remain consistent. A Gateway setup is needed to ensure uninterrupted statistics collection.

15. When you have the persistent topology feature enabled, to decommission a node in the network and take it out of the topology you must delete the node from the persistent topology data using the switch CLI

16. To ensure all CWM servers have the same XPVC Preferred data, CWM-to-CWM gateway must be enabled; otherwise, you must manually propagate the data to all CWM servers.

17. On MGX PXM1-based feeders in the BPX network, VISM or VISM-PR terminated XPVC only connect to the AUSM service module. No such restriction exists for PXM1E-based or PXM45-based nodes.

18. Manual node resync may fail due to the GUI timing out for PXM45/PXM1E-based Cisco MGX nodes with too many connections (i.e. 400K dax endpoints).

Ensuring the Creation of the svplus and/or wandest Username and Password

When either the SSM, the SSC, or the WANDEST server or client is installed for the first time on your Solaris workstation, the svplus and/or wandest username and password may not be available. After installing any of these applications, log in as root and set the unix password(s) for the svplus and/or wandest user using either the admintool or the passwd command on the command line. Only the SSM requires resetting the svplus user unix password.

Connection Manager Limitations

The normal behavior of the CWM Connection Manager is that it automatically updates with all events received, however, if there are too many new events (if the event buffer fills up) the refresh button turns yellow. The yellow refresh button indicates that you should refresh the screen. Upon clicking the refresh button, it will pull information directly from the database.

When the connection modify dialog box is already open, another user can delete the connection using the CMGUI delete option.

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

While adding connections originating and terminating on the same feeder nodes (MGX8220 only), CWM 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.

RPM on PXM1-based MGX 8850/8230/8250 provisioning is done using telnet since the RPM does not support SNMP SETs. This should be transparent in daily operation. For more details, please refer to the specific RPM switch CLI release notes.

HP OpenView Limitations

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

The WAN network icon in the network node manager is no longer automatically created when running CWM 12. Use the Network Topology map instead.

Issues with the CWM 12 Statistics Collection Manager

In order to collect connection statistics, statistics should be enabled on individual connections. If the user only enables connections stats on SCM but does not set the stats enabled flag to true on the connection, the stats will not be collected, for that connection. Since there is no mechanism or warning to the user to have this enabled on the connections, CWM will not give appropriate error message.

When enabling statistics by selecting multiple nodes at a time in the SCM, enabling statistics on all the nodes will only work if all of the nodes have the same card types or cards of the same family.

In the PXM45 and PXM1E based MGX 8850 switches Summary Reports are only supported on the AXSM card.

Occasionally, when high connection counts are enabled on the SES, and statistics collection is enabled, the SES node is not getting synced up. The workaround is to disable statistics collection in the SES. Refer to CSCdw32076 for more information.

The statistics collection manager retrieves SPVC connection statistics data from BPX-SES nodes, however, only 15 minute collection buckets are supported on the SES.

The same limitation of only 15 minute collection buckets applies for MGX 8850 PXM45-based nodes with AXSM. There is no such limitation for AXSM-E.

Only 15 minute collection buckets are supported for PNNI statistics.

Peak statistics are not supported for PNNI statistics.

If the PXM45 release is less than 4.0(0.0) PNNI historical statistics can not be enabled.

The PXM45A card does not support PNNI statistics collection.

The BPX-SES does not support PNNI statistics collection.

The following statistics for SRM and SRM/E T3 lines.can be enabled on the switch, but are not supported by SCM:

28 dsx3LCVCurrent

29 dsx3LESCurrent

30 dsx3LSESCurrent

31 dsx3PCVCurrent

32 dsx3PESCurrent

33 dsx3PSESCurrent

34 dsx3CCVCurrent

HP OpenView is supported on StandAlone Statistics Manager (SSM). SSM processes generate CWM traps.

Stats Parsing is only supported for the "statsdb" database on the SSM machine. Stats Parsing is not supported for the "stratacom" database on the SSM machine.

Wingz and Summary Reports are not supported on the SSM machine.

At least one CWM must be up and running, with the nodes synced up, for SSM to work normally. SSM uses the CWM server workstation to get traps while enabling statistics for cellbus-based service modules on MGX 8850 and PNNI statistics on BPX.

The WANDEST server must be up and running on the CWM server workstation. SSM gets the node, node_info, card, network, rsc_part, bis_object tables from the CWM server workstation using WANDEST.

If the statsmaster SSM/CWM is down or unreachable in a SCM Gateway setup, the statsmaster must be changed on the switch to a machine that is up. The statsmaster is needed for SCM statistics enabling/disabling.

In an SCM Gateway setup with statistics collection going on, after switchover the old statistics data is not moved to the new Primary CWM/SSM machine.

SSM does not receive traps on Node/Card Deletion, so statistics collection must be stopped and disabled before deleting a node/card on the network. Also SSM does not receive traps on Node/Card Add messages, so the WANDEST upload must be received before the node/card can be seen in SCM GUI on SSM.

In SSM, statistics collection must be stopped and restarted after changing the node name or changing the node FTP password.

Limitations for CWM to CWM Communication

The Secondary CWMs have to wait for the Primary CWM to finish syncing up with the network. Trap 28075 (svDatabaseInSync) is sent when the Primary CWM has finished syncing up with the network.

All the CWM workstations managing the same network must have seed nodes or gateway nodes that have IP addresses within the same network. All the CWM workstations should not all point to the same gateway node, but the gateway nodes they point to should be on the same network. The exception is that when using the Preferred Route feature, all the CWM workstations must all point to the same gateway node

The Configurator can be started on either the Primary CWM or the Secondary CWMs, but Add, Modify, or Delete operations using the Configurator can only be performed on the Primary CWM.

All the CWM to CWM Communication limitations listed above also apply to SCM Gateway.

Topology Limitations

In a single routing node PNNI network, the node is managed using the IP address specified in the network.conf file.

In the case of a PXM45-based MGX network, the PXM45-based MGX nodes are managed using the primary IP address. The primary IP address is specified using Option 8 in the cnfndparms CLI. Configure the trap IP with the primary IP. PXM1-based MGX nodes connected to PXM45-based MGX nodes are managed through the atm0 IP. If the atm0 is not set, then the LAN IP is used to manage the PXM1-based MGX nodes. Configure the trap IP accordingly.

In the /usr/users/svplus/config/CwmGs.conf file there is a flag named TOPO_SHOW_MAP. You can use this file to set up the flag to configure whether or not nodes and trunks are displayed in the topology display at CWM startup.

TOPO_SHOW_MAP 1 means when NWTopology opened, users can see nodes and trunks in the topology.

TOPO_SHOW_MAP 0 means when NWTopology opened, users cannot see nodes and trunks in the topology.

The CORBA callback functions between the server and GUI are one way asynchronous calls, sent with best-effort, no delivery-guaranteed. There is a possibility of dropping CORBA trunk status messages when the network is extremely busy.

Launching more than five client GUIs tied to the same CWM server managing a large network (seen with an 1800-node network) may result in a data overload condition that shuts down the sockets.between the client machines and the CWM server.

The workaround is to change the QOS parameter for the one way calls between the Topology application running on the CWM server and the client machines. You need to change the value of sync_scope_policy from SYNC_WITH_TRANSPORT to SYNC_WITHSERVER. To do this, BEFORE starting CWM core, while logged in as the "svplus" user, execute the following command:


itadmin variable modify -scope Cwm.Toposerver -type string -value SYNC_WITH_SERVER 
policies:sync_scope_policy

This setting forces the caller to wait until the called resource has read the data, ensuring that the data is sent to the GUI and preventing flooding of the TCP layer.

CWM 12 Notes and Cautions

Due to the nature of asynchronous behavior of ILOG client and server interaction, CWM client requests may be sent before the CWM server is ready. In this case, the following error messages will be displayed on the workstation screen:

Ilb Error: Synchronous request to <unidentified actor failed by timeout>. 


Note If the ILOG timeout situation persists for more than five minutes and the CWM workstation is not functioning normally, then a service call should be made.


Parameters displayed by the Network Browser that are not applicable to an element i.e.: a line or a trunk often contain the value -1. Treat this as the same as Not Applicable.

Issues with Firewalls and CWM 12

Firewalls set up on managed networks and PCs used as clients may affect the Desktop GUI. The following sections describe how to resolve these issues.

Firewall on PC:

Problem:

If a PC based firewall like BlackIce is used, the protection settings to enable incoming connections may need to be changed. In CWM 12.0.00, when running a client is running on a remote PC, the server opens new connections when sending node and network updates to the Desktop GUI. If the PC blocks all incoming calls, this will cause the topology map to not appear on the GUI.

Solutions:

Here are some suggested solutions to the problem. Please use any one of them.

Solution 1

Lower the protection level for incoming connections. In Black Ice, for example, the Protection Level should be set to "Cautious: block some unsolicited inbound traffic" instead of the more restrictive "Nervous: block most unsolicited inbound traffic".

Solution 2

If the firewall software allows, add CWM server machine as a trusted IP address and allow all traffic from the CWM host.

Solution 3

Limit ports used by CWM clients and servers for corba communication and open these ports on the firewall software. The following steps can be executed to set up the ports:


Step 1 Stop CWM core

Step 2 Stop Orbix processes using 'stoporbix2000' script

Step 3 Add the following line at the end of the /usr/users/svplus/orbix_domain/domains/cwm_<cwm-machine-name>_domain.cfg file on the CWM workstation:

policies:iiop:server_address_mode_policy:port_range = "5500:6000";

This will restrict the CWM processes to use ports between 5500 and 6000 for corba communication.

This range is enough for up to 20 clients connecting to the CWM simultaneously. If more than 20 clients will be connected CWM at one time, please increase the upper limit as follows:

30 simultaneous clients - 5500:6100

40 simultaneous clients - 5500:6200

50 simultaneous clients - 5500:6300

Step 4 Start CWM core.

Step 5 Configure the firewall to open the above ports in both directions (from CWM to the clients and vice versa). Other than these ports, the firewall also need to allow 3075 and 3094 ports for communication with the Orbix processes.


Note The above port range can start from any number as required, please note that the number of ports should remain the same as shown above. For example, the port range can be set to 9000:9500 for 20 clients and so on.



Firewall on LAN:

Problem:

If the network where CWM is located has a firewall configured to restrict traffic from both inside the LAN as well as from an outside PC the topology map will not show up in the Desktop GUI.

Solutions:

Here are some suggested solutions to the problem. Please use any one of them.

Solution 1

Use VPN tunneling for the remote PCs to connect to the CWM machines in the lab

Solution 2

Set up trusted IP addresses in the Firewall. Both CWM machines and the remote PC that are going to use CWM GUI need to be added as trusted IP addresses in the firewall configuration.

Solution 3

Limit ports used by CWM clients and servers for Orbix communication and open these ports on the firewall software. The following steps can be executed to setup the ports:


Step 1 Stop CWM core

Step 2 Stop Orbix processes using 'stoporbix2000' script

Step 3 Add the following line at the end of the /usr/users/svplus/orbix_domain/domains/cwm_<cwm-machine-name>_domain.cfg file on the CWM workstation:

policies:iiop:server_address_mode_policy:port_range = "5500:6000";

This will restrict the CWM processes to use ports between 5500 and 6000. This range is enough for up to 20 clients connecting to the CWM simultaneously. If more than 20 clients will be connected CWM at one time, please increase the upper limit as follows:

30 simultaneous clients - 5500:6100

40 simultaneous clients - 5500:6200

50 simultaneous clients - 5500:6300

Step 4 Start CWM core.

Step 5 Configure the firewall to open the above ports in both directions (from CWM to clients and vice versa). Other than these ports, the firewall also need to allow 3075 and 3094 ports for communication with the Orbix processes.


Note The above port range can start from any number as required, please note that the number of ports should remain the same as shown above. For example, the port range can be set to 9000:9500 for 20 clients and so on.



CWM 12.0.00 Server Installation or Upgrade to CWM 12.0.00


Note CWM software can be upgraded from 10.5.10 Patch 1, 10.5.10 Patch 3, 11.0.10 patch 1or 11.0.10 patch 2 (either Solaris 7 or Solaris 8)


The most current upgrade and installation information is found in the CWM Installation Guide for Solaris 8, Release 12 (OL-3837-01). A PDF copy of this document is on the CWM 12 Documentation CD. The following sections describe installation and upgrade procedures specific to CWM 12.0.00, Patch 3.

CWM 12.0.00, Patch 3 Installation

Contents of this patch:

CWM Server

12.0.00-P3a.tar.gz

12.0.00-P3b.tar.gz

InstallCWM12Patch3.csh

Informix 9.21 UC7XL

informix921uc7xl.tar.gz

InstallInformixPatchuc7xl.csh

CWM SNMP Agent

12.0.00-P3.agent.tar.gz

InstallSNMPAgent12Patch3.csh

CWM SSC (Standalone Statistics Collector)

12.0.00-P3.ssc.tar.gz

InstallSSC12Patch3.csh

CWM SSM (Standalone Statistics Manager)

12.0.00-P3.ssm.tar.gz

InstallSSM12Patch3.csh

CMF 2.1 Patch:

cmf2.1-sol-CSCeb834941.tar

WANDEST Server 2.4 Patch 3

wandest2.4-P3.server.tar.gz

InstallWD24Patch3.csh

WANDEST Client 2.4 Patch 3

wandest2.4-P3.client.tar.gz

RTM Proxy

12.0.00-P3.RtmProxy.tar.gz

InstallRTMProxy12Patch3.csh


Note RTM Proxy Patch 3 tar file is for the purpose of working with Standalone Statistic Manager only. Not for northbound interface.


Installing the CWM Server Patch


Step 1 Login to the CWM server as user root

Step 2 Download or copy the compressed tar files for CWM Server and InstallCWM12Patch3.csh, for example, /tmp


Step 3 Change to local directory that contains the compressed tar files



Step 4 Decompress the compressed tar files

# gunzip 12.0.00-P3a.tar.gz 
# gunzip 12.0.00-P3b.tar.gz

Step 5 Execute the InstallCWM12Patch3.csh script with the tar files as arguments to begin the install process by entering the following command:

# ./InstallCWM12Patch3.csh 12.0.00-P3a.tar 12.0.00-P3b.tar

Step 6 If CiscoView 5.4.1 is installed and CMF 2.1 Patch has not been installed on this machine, do the following:

a. Download or copy the cmf2.1-sol-CSCeb834941.tar to a local directory. For example, /tmp

b. Switch to root. For example, su

c. Go to the local directory and untar the tar file
For example,
cd /tmp
tar xvfp cmf2.1-sol-CSCeb834941.tar

d. Go to <local directory>/CSCeb83494-1
For example, cd /tmp/CSCeb83494-1

e. Run the CSCeb83494-1.pl to install the CMF 2.1 patch
For example,
/opt/CSCOpx/bin/perl CSCeb83494-1.pl

Step 7 If WANDEST Server 2.4 is installed on this machine, do the following:

a. Stop the WANDEST Client

b. Exit root

c. Run the /usr/users/svplus/scripts/get_dbschema.ksh
For example,
cd /usr/users/svplus/scripts
./get_dbschema.ksh

A wd_dbschema_tmpl file is created in /usr/users/svplus/tmp directory. Edit this file and un-comment out the tables that you want triggers in.

d. Download or copy the wandest2.4-P3.server.tar.gz and the InstallWD24Patch3.csh files to the local directory. For example, /tmp

e. Change to that local directory and Uncompress the gzip file
For example, # gunzip wandest2.4-P3.server.tar.gz

f. Switch to root

g. Run the installation script to install the patch
For example, # ./InstallWD24Patch3.csh wandest2.4-P3.server.tar


Step 8 Exit from root


Installing the Informix 9.21.UC7XL Patch


Note Informix Patch 921UC7XL should only be applied if the revision level of your Informix installation is lower than 9.21.UC7XL. You can check this by changing to the directory containing the installed Informix binaries and running the command "./onstat -V"


The process for upgrading to Informix Patch 921uc7xl consists of the following three operations:

backing up the existing database

installing the patch

verifying and restoring your saved database after the informix patch installation in case of an Informix problem

Preparing to Install the Informix Patch (Backing Up the Existing Database)


Note It is advisable to do a backup of the database in case there is a problem with informix.


To do a backup of databases do the following:


Step 1 Find a location where there is enough space. Create a directory there called < dbexport-location>

 # mkdir /usr/users/svplus/<dbexport-location> 

Step 2 Do the following to export the databases

a. Log in as svplus

hostname# su -u svplus

The system prompts you for the svplus password:

password:

b. If CWM is runnin stop the core.

c. Perform a coldstart (this will drop all the network data so that you will only be exporting the user data in each database).

# coldstart
 

d. Export stratacom database

# dbexport stratacom -o <dbexport-location>

e. Export scmdb database

# dbexport scmdb -o <dbexport-location>

f. Export statsdb database

# dbexport statsdb -o <dbexport-location>

Step 3 If you have a WANDEST server installed then export the WANDEST database:

# dbexport wandest -o <dbexport-location>

Step 4 Get the output of onstat -d

# onstat -d > <dbexport-location>/onstat.out


Installing the Informix Patch

Contents of the Informix 9.21.UC7XL Patch

InstallInformixPatchuc7xl.csh

informix921uc7xl.tar.gz


Step 1 Log in as svplus

hostname# su -u svplus

The system prompts you for the svplus password:

password:

After you enter the svplus password, the svplus (non-root) prompt displays:

% 

If the CWM core is running, proceed with Step 2. If the core is already stopped, go to Step 5.

Step 2 Enter the CWM Main Menu by typing CWM at the prompt

Step 3 Stop the core by choosing Option 2.

Step 4 Type "X" to exit the CWM Main Menu.

Step 5 Download or copy the tar file and the InstallInformixPatchuc7xl.csh script to a local directory.

For example, /tmp

Step 6 Change to the local directory that contains the tar file.

Step 7 Log in as root

% su

The system prompts you for the root password:

password:

After you enter the password, the root prompt displays:

# 

Step 8 Uncompress the gzip file:

# gunzip informix921uc7xl.tar.gz

Step 9 Execute the InstallInformixPatch.csh script. This script will untar the tar. Do not untar it separately.

# ./InstallInformixPatchuc7xl.csh 

Step 10 Exit from root


Verifying and Restoring Your Saved Database After the Informix Patch Installation

Do the following steps in case Informix did not come up online:


Note The output of onstat -d is in /usr/users/svplus/DBEports120/onstat.out for reference



Step 1 Become user root

# su

Step 2 Go to the /usr/users/informix92/etc directory

# cd /usr/users/informix92/etc

Step 3 Do the following steps only if you have configured a separate raw partition for the Informix physical log

a. open onconfig file

# vi onconfig
 

b. Change the following line

                 PHYSDBS          phydbs

to

                 PHYSDBS          rootdbs

c. Change the following line

                 PHYSFILE        <size>
 

to

                 PHYSFILE        20000

d. Save the onconfig file and exit from the editor

Step 4 Go the /usr/users/svplus/scripts/Install directory

# cd /usr/users/svplus/scripts/Install

Step 5 Run the following commands in the order shown below:

# ./dbmode
# ./dbinit
# ./dbonmode
# ./dbonspace

Step 6 If you have the file AddPhyLog in /usr/users/svplus/scripts/Install then do the following steps:

# ./AddPhyLog
# ./RestartInf

Step 7 If you have the file dbaddchunk in /usr/users/svplus/scripts/Install then do the following steps:

# ./dbaddchunk

Step 8 Exit from root

Step 9 Check if you have configured separate partition for datadbs using onstat -d command

# onstat -d

Step 10 If there is a separate partition then do the following steps to import the database. If there is no separate partition for datadbs then go to step 11

a. # dbimport stratacom -d datadbs -i <dbexport-location>

b. # dbimport statsdb -d datadbs -i <dbexport-location>

c. # dbimport scmdb -d datadbs -i <dbexport-location>

Step 11 If there is no separate partition for datadbs then do the following:

a. # dbimport stratacom -i <dbexport-location>

b. # dbimport statsdb -i <dbexport-location>

c. # dbimport scmdb -i <dbexport-location>

Step 12 If you had WANDEST server before then do the following:

# dbimport wandest  -i <dbexport-location>

Installing the CWM SNMP Agent (Service Agent) Patch:


Step 1 Login to the CWM server as user root

Step 2 Download or copy the compressed tar file and the installation script to the local directory, for example, /tmp


Step 3 Change to local directory that contains the compressed tar file and the installation script


Step 4 Decompress the compressed tar file by entering the following command:

# gunzip 12.0.00-P3.agent.tar.gz 

Step 5 Execute the InstallSNMPAgent12Patch3.csh script with the tar files as arguments:

# ./InstallSNMPAgent12Patch3.csh 12.0.00-P3.agent.tar 

Step 6 Exit from root.


Installing the SSC (Standalone Statistics Collector) Patch on the Standalone Statistics Collector Machine:


Note This patch installation is to be performed only if you are using the Standalone Statistics Collector machine and must be performed on that machine.



Step 1 Login to the SSC (Standalone Statistics Collector) machine as user root

Step 2 Download or copy the compressed tar file and the installation script to the local directory, for example, /tmp


Step 3 Change to local directory that contains the compressed tar file and the installation script


Step 4 Decompress the compressed tar file

# gunzip 12.0.00-P3.ssc.tar.gz 

Step 5 Check for the file InstallSCC12Patch3.csh and begin the install process by entering the following command:

# ./InstallSSC12Patch3.csh 12.0.00-P3.ssc.tar

Step 6 Exit from root.


Installing the SSM (Standalone Statistics Manager) Patch on the Standalone Statistics Manager Machine:


Note This patch installation is to be performed only if you are using the Standalone Statistics Manager machine and must be performed on that machine.



Step 1 Login to the SSM (Standalone Statistics Manager) machine as user root N

Step 2 Download or copy the compressed tar file and the installation script to the local directory, for example, /tmp


Step 3 Change to local directory that contains the compressed tar file and the installation script


Step 4 Decompress the compressed tar file

# gunzip 12.0.00-P3.ssm.tar.gz 

Step 5 Check for the file InstallSCMSA11Patch3.csh and begin the install process by entering the following command:

# ./InstallSSM12Patch3.csh 12.0.00-P3.ssm.tar

Step 6 Exit from root.


Installing the CWM RTMProxy Patch on the CWM Machine:


Note RTM Proxy Patch 3 tar file is for the purpose of working with Standalone Statistics Manager only. Not for northbound interface.


This patch installation is to be performed only on CWM machine which has no SNMP Agent and which is used by SSM for stats


Step 1 Login to the CWM machine as user root

Step 2 Download or copy the compressed tar file and the installation script to the local directory, for example, /tmp


Step 3 Change to local directory that contains the compressed tar file and the installation script


Step 4 Decompress the compressed tar file

# gunzip 12.0.00-P3.RtmProxy.tar.gz 

Step 5 Execute the InstallRTMProxy12Patch3.csh script with the tar file as argument:

# ./InstallRTMProxy12Patch3.csh 12.0.00-P3.RtmProxy.tar

Step 6 Exit from root


CMF Patch 2.1 Installation

To install the CMF patch, perform the following steps:


Step 1 Down load or copy it to a local directory.

Step 2 Switch to root. For example, su

Step 3 Go to that local directory and untar the tar file. For example, tar xvfp cmf2.1-sol-CSCeb834941.tar

Step 4 Go to <local directory>/CSCeb83494-1. For example, cd <local directory>/CSCeb83494-1

Step 5 Run the CSCeb83494-1.pl script For example, /opt/CSCOpx/bin/perl CSCeb83494-1.pl

Step 6 Exit.


Location of Modified Files:

/opt/CSCOpx/objects/web/bin/web_server

Location of Backed-up file details:

/opt/CSCOpx/objects/web/bin/web_server-CSCeb83494-1

Location of Info file

The CSCeb83494-1.info file will be added after installing the patch. This file has brief details about this patch:

/opt/CSCOpx/setup/patch/CSCeb83494-1.info

Steps Required if You Want to Roll Back the Patch


Step 1 Stop Daemon Manager using /etc/init.d/dmgtd stop.

Step 2 Replace /opt/CSCOpx/objects/web/bin/web_server with:

/opt/CSCOpx/objects/web/bin/web_server-CSCeb83494-1

Step 3 Remove the patch info file /opt/CSCOpx/setup/patch/CSCeb83494-1.info

Start Daemon Manager /etc/init.d/dmgtd start.


WANDEST 2.4, Patch 3

If you have standalone WANDEST Server and Client workstations, follow the next sections to install the patches to your standalone workstations.

Contents of This Patch

WANDEST Server

wandest2.4-P3.wdserver.tar.gz

InstallWD24Patch3.csh

WANDEST Client

wandest2.4-P3.wdclient.tar.gz

Installing the WANDEST Server Patch:

To install the WANDEST server patch, perform the following steps:


Note Confirm that the WANDEST Client has been stopped before installing any patches on the WANDEST Server.



Step 1 Login to the CWM workstation as user svplus

Step 2 Run the /usr/users/svplus/scripts/get_dbschema.ksh


# cd /usr/users/svplus/scripts
# ./get_dbschema.ksh

A wd_dbschema_tmpl file is created in /usr/users/svplus/tmp directory. Edit this file and un-comment out the tables that you want triggers in it.



Step 3 Download or copy the server tar file and the installation script to the local directory. for example, /tmp


Step 4 Change to that local directory and Uncompress the gzip file:

# gunzip wandest2.4-P3.wdserver.tar.gz

Step 5 Switch to root


Step 6 Run the installation script to install the patch:

# ./InstallWD24Patch3.csh wandest2.4-P3.wdserver.tar

Step 7 Exit from root.


Installing the WANDEST Client Patch:

To install the WANDEST client patch, perform the following steps:


Step 1 Login to the Wandest client as user root

Step 2 Download or copy the compressed tar file for Wandest client to a local directory. for example, /tmp


Step 3 Change to the local directory that contains the compressed tar file


Step 4 Decompress the compressed tar file by entering the following command:

# gunzip wandest2.4-P3.wdclient.tar.gz 

Step 5 Untar the tar file:

# tar xvfp wandest2.4-P3.wdclient.tar

Step 6 Exit from root.


Evaluation Copy of CWM 12

The 90-day evaluation copy of CWM gives you the opportunity to try CWM for a 90-day period. It is not possible to upgrade an existing version of CWM with the evaluation version. You cannot apply patches downloaded from CCO to the 90-day evaluation copy of CWM. The evaluation version does not support Multiple Disk Configuration for Informix. The only other difference between the licensed version of CWM 12 and the 90-day evaluation version is the way the software is packaged. Here are the details for the 90-day evaluation package

The 90-day evaluation version of CWM comes with all the other applications like Service Agent, SCMSA, WANDEST Server and WANDEST Client

The 90-day evaluation version of CWM is packaged into the following four CDs:

CWM Server on the first CD (no change from the licensed version of CWM 12)

CWM Server Agent and SCMSA on the second CD (the directories are cdromAgent and cdromScmSa)

CiscoView, WANDEST Server and WANDEST Client on the third CD (the directories are cdromCV, cdromWDServer, cdromWDClient)

CWM documentation and Adobe Acrobat software on the fourth CD (no change from the licensed version of CWM 12)

All the packages have to be installed separately, just like the licensed version of CWM 12.

For the applications on the second and third CDs, you must change directory to a particular package directory and then follow the installation instructions for that particular package.

For example, the instructions for installing WANDEST are available in Chapter 5 of the WANDEST Installation and Reference, Release 2.4. The WANDEST Installation and Reference, Release 2.4 is available online at the following URL:

http://www.cisco.com/univercd/cc/td/doc/product/wanbu/svplus/12/wandest/index.htm

In Step 3 of the WANDEST server installation process, change to the /cdrom/cdromWDserver directory before entering the ./installServer.sh command and then follow the remaining installation instructions in this section.

Evaluation Copy Limitations

You cannot apply patches downloaded from CCO to the 90-day evaluation copy of CWM.

It is not possible to upgrade an existing version of CWM with the evaluation version.


Note The 90-day evaluation period begins as soon as the evaluation copy is installed - not after the core is started. You can confirm how much time is left by choosing the About... option under the Help pulldown menu in the Topology GUI.


Important Configuration Notes

This section provides important information about configuration.

Naming Managed Nodes

Each node name of all the nodes managed by CWM must be unique.

Core File Management

Core files used to be created without unique names, and overwritten. Now core files are stored in the /usr/users/svplus/corefilesdir/ directory. Each is given a unique name in the format:

<process name>.<pid>.core.dump

C-Note/CWM Configuration

The CWM core must be started and core processes should be up before the Orbix cmldomain services for C-Note are started.

Add the IP address of the C-Note workstation to the /opt/ssng/config/CMLLogin/SnmpPublisher.xml file by entering the following command:

vi /opt/ssng/config/CMLLogin/SnmpPublisher.xml 

The line you add should look like this:

<ipAddress>172.28.140.218</ipAddress>

You need to substitute the actual IP address of your C-Note workstation for the sample 172.28.140.218 address listed above).

Node Numbering for Release 9.4 IGX Feeder Nodes

When an IGX is added as a feeder to a SES/BPX or MGX node, it will have a default node number, this node number may not be unique within the network. If it is not unique then it needs to be modified to a unique node number by issuing the CLI command "rnmnd <x>" where x should be unique with respect to all other auto-route nodes. To find the other node numbers, use the CLI command "dspnds +n". Failing to do so, the CWM Databroker may have an incorrectly formed hybrid connection database, and the CWM GUI may show the connection as incomplete.

CWM Dedicated IP Ports

CWM 12 to Cisco WAN switch (outgoing): ports used in the switch

udp: 161, snmp get/set

udp: 2500, rtm

udp: 69, tftp server

tcp: 23, telnet

tcp: 13, daytime

Cisco WAN switch to CWM 12 (incoming): ports used in CWM 12

udp: 162, snmp trap

tcp: 8888, HP OV topology daemon

tcp: 9999, HP OV database daemon

Operations Support System (OSS) to CWM 12 (incoming): ports used in CWM 12

udp: 8161, snmpAgent This port is configurable. Please refer to the Cisco WAN Manager SNMP Service Agent Guide for configuring this port to other than 8161

CWM12 (Internal) Process to Process Communication ports

CWM processes' ports 9000 to 9011

Web Services (Java Client) 1551

CiscoView Web Server 1741

Orbix ports 3075,3079,3094

CWM Dedicated User IDs

In order for CWM and the SSC and SSM applications to operate correctly, certain IDs must be available for use by the Informix database. The user IDs listed below should be reserved so that they are not taken by other (non-CWM) applications.

The following user IDs should be reserved for CWM installation:

userids 271, 272

The following user IDs should be reserved for SSM installation:

userids 270, 271, 272

The following user IDs should be reserved for SSC installation:

userids 270, 271

The following user ID should be reserved for WANDEST client:

userid 274

The impact when these userids are taken by other applications is that svplus/wandest/informix users will not get created and subsequent references to those userids will fail.

Security Profiles

The security profile and user profile are stored in the database as user_info and sec_profile tables. All CWM systems in the same domain will have the same data in the user_info and sec_profile table by ways of CWM to CWM communication.

The user_info and sec_profile tables will not get dropped when the coldstart command is executed during a cold start. These tables can only be dropped by executing the coldstart command with the "-F" option.

The Security Manager GUI can be started from NWTopology main window in the primary CWM system.

The CWM user to be added to the database has to be a valid UNIX user, when a user logs in to CWM desktop, user authentication against UNIX gets performed. The CWM user's password needs to match what's defined in the UNIX system.

CWM Database

After performing the creation of a new database by executing the coldstart script, if CWM is restarted (stop core and start core) before it is synchronized with the network, it will result in a database inconsistency. In this case, rerun the coldstart script to avoid database inconsistencies.


Note Do not use the SV+CreateDb tool for the above purpose.


When a Gateway node is upgraded or rebuilt, before CWM has synchronized up with the network, CWM must be cold-started (create CWM database and restart CWM). This is required to ensure CWM database consistency.

The user supplied network name can be up to 10 characters in length and should be alphanumeric characters only (no periods).

The asi_line table is populated with the 1-based port number and not the 0-based port number for IGX ports.

Occasionally, a triggered resync (the automated running of the restoreallcnf command) may result in the CWM connection data being inconsistent with that on the switch. In this case, run a manual node resync to ensure that there are no inconsistencies between CWM connection data and the connection data on the switch.

Connection Manager Configuration

Configuration Parameters for Connection Manager Daemon (cmgrd)

The file used is /usr/users/svplus/config/cmgrd.conf

Any configuration parameter that is changed is in effect only if either the cmgrd process is killed or if not a kill -USR1 signal is sent to it. kill -USR1 signal will make cmgrd re-read the config file, it will not terminate the process and is the recommended way to make the configuration in effect.

The configuration parameters in this file are listed below:

ATM_FR_OVERHEAD_FLAG: This can be set to ENABLE or DISABLE. The default is ENABLE. If Enabled, the frame relay bits per second to atm cells per second conversion will use a overhead factor of 1.44. This flag controls the conversion from frame relay to atm when the frame relay endpoint is one of the FRSM cards on Auto Route Feeder nodes. If enabled, the conversion is cells_ per_second = (bits_per_second +383 / 384) * 1.44.

If disabled, the conversion is cells_per_second = (bits_per_second + 383 / 384). The number 384 comes from 48 bytes in a cell multiplied by 8 bits in a byte.

THROTTLE_NODE_LOCK_RETRY: Default is 1. This number configures the number of times cmgrd will retry in case of a SNMPCOMM Throttle error or a Database Lock error from switches. If no retry is needed this should be changed to 0.

TIME_BETN_RETRY: Default is 3 seconds. This number in seconds is used only if THROTTLE_NODE_LOCK_RETRY is >= 1. This is the time that cmgrd waits internally before issuing the retry.

SET_TIMEOUT: Default is 30000000 microseconds which is 30 seconds. This number in microseconds configures the time that snmpcomm waits for a SET response to a SET request from cmgrd to any Auto Route switch before it declares timeout.

PNNI_SET_TIMEOUT: Default is 60000000 microseconds which is 60 seconds. This number in microseconds configures the time that snmpcomm waits for a SET response to a SET request from cmgrd to any PNNI switch before it declares timeout.

MAX_REQUEST_TIME: Default is 300 seconds. This number in seconds specifies the time that cmgrd internally waits for a provisioning request to complete. If the provisioning request is not completed within that time and the user retries the request, the retried request will go through without giving the error "Outstanding request already exists".

EGRESS_AUSM_MAPPING: This can be set to ENABLE or DISABLE. The default is ENABLE. If enabled, cmgrd will always map the following variables for AUSM on all platforms:

Egress Service Rate from minimum of other end PCR and Local Port speed for non ABR connections; from minimum of other end MCR and Local Port speed for ABR connections.

Egress PercentUtil from other end Percent Util.

If disabled, cmgrd will set the Egress Service Rate for AUSM on all platforms from the user specified value for Egress Service Rate. If the user does not specify it, the mapping as above will be done. Egress Percent Util will also follow the same rules except in case of AUSM on PXM1E-based MGX 8850/8830 where the Egress Percent Util will always be mapped irrespective of the flag value.

PNNI_PER_UTIL_FLAG: This can be set to ENABLE or DISABLE. Default is ENABLE. If enabled, cmgrd will set PercentUtil on all PNNI endpoints as set by user.

If disabled, cmgrd will not set PercentUtil on any PNNI endpoint hence will be defaulted by the switch to 100%.

AUSM_DISCARD_OPTION: This can be set to ENABLE or DISABLE. Default is DISABLE. If enabled, cmgrd will internally set ingressQDiscardOption for AUSM cards on all platforms to `frameDiscard' if FGCRA is enabled on the card and will set it to `clpHysterisis' if FGCRA is disabled on the card.

If disabled, cmgrd will not set ingressQDiscardOption parameter at all on the switch hence defaulted by switch always to `clpHysterisis'.

Setting up RPM Cards for Management by CiscoView from the Workstation

By default, the SNMP agent of an RPM is not enabled. To manage a device that contains an RPM, first ensure that the SNMP agent is enabled.

Useful commands are:

Router# show snmp

Router# config terminal

Router(config) snmp-server community community string

Router(config) exit

Router# write memory

RPM cards must have SNMP configured to enable CiscoView to view configuration parameters, performance statistics, and events.

Configuring SNMP and SYSLOG

Each RPM card to be managed must have SNMP and SYSLOG configured or the management software cannot communicate with the node containing the RPM card.

Table 10 shows SNMP and SYSLOG router configuration commands. In this example, the network management system has an IP address of 10.1.1.1.

Table 10 SNMP and SYSLOG Router Configuration Commands 

RPM Configuration Command Line
Description

logging 10.1.1.1

Enable SYSLOG messages to be sent to the network management system with IP address 10.1.1.1.

snmp-server community public RO

Enable SNMP; allow read-only SNMP access with community string public. On a PXM45/PXM1E-based MGX switch, you can set this string to any value, but it should agree with whatever's set on the PXM45. On a PXM1-based MGX switch, the RPM card's community string is not configurable, and has to be set to the default "POPEYE".

snmp-server community private RW

Allow read-write SNMP access with community string private. On a PXM45/PXM1E-based MGX switch, you can set this string to any value, but it should agree with whatever's set on the PXM45. On a PXM1-based MGX switch, the RPM card's community string is not configurable, and has to be set to the default "POPEYE".

snmp-server trap-source Channel0/2

Configure SNMP traps to be sent from the router with the IP address configured on interface Channel0/2. You should set this configuration parameter to the interface that is used by clients to connect to the RPM. The IP address associated with this interface will be used by the network management system for management.

snmp-server location RTP, NC

Set a textual description of the location of the router. This value is for informational purposes only.

snmp-server contact Network Administrator

Set a textual description of the contact for the router. This value is for informational purposes only.

snmp-server enable traps

Enable all SNMP traps. You can restrict which traps are enabled. See the Cisco IOS command reference for the snmp-server command for a complete list of traps that can be selectively enabled.

snmp-server host 10.1.1.1 public

Specify that all SNMP traps are to be sent to the network management system with IP address 10.1.1.1.



Note The SNMP and SYSLOG configuration process is extensively discussed in the command reference documentation for each release of the Cisco IOS software.


Configuring CiscoView for Large Networks

To improve CiscoView performance in managing large networks, change the value of "session.maxresidents" from 1024 to 3072 in the /opt/CSCOpx/objects/jrun/jsm-cw2000/server/jse/properties/session.properties file and change the value of "MaxClients" from 150 to 200 in the /opt/CSCOpx/objects/web/conf/http.conf file.

Creating and Configuring a CWM Auto-Restart Shell Script

This section describes how to create a shell script that automatically starts the CWM core after a reboot. To create this shell script you need to use a text editor to create a new file containing the commands that you want the script to execute.

Using the vi Editor to Create Your Auto-Restart Shell Script

Follow the steps below to create a script that uses shell commands to automatically restart the CWM core after the workstation has been rebooted.


Step 1 Login to the CWM workstation as user root

$ su 

Step 2 Change to directory /etc/rc3.d

# cd /etc/rc3.d 

Step 3 Create a shell script of the form: Snn<filename>, where nn is the relative sequence number for starting the job under /etc/rc3.d by entering the following command

# vi /etc/rc3.d/S99init_sv 

Since this script does not currently exist, the vi editor will open on a blank line, waiting for you to enter the script commands.

Step 4 Create the shell script by entering the following lines:

******************************************************************

#!/bin/sh

# Check if Informix configuration is going on
  while [ ! -z "`ps -ef | grep S98init_db | grep -v grep`"]
  do
    echo "Informix initialization in progress...." >> 
/usr/users/svplus/log/.start_stopCWM.log
    sleep 5
  done

# Start Orbix E2A ... as svplus

  echo "Starting Orbix E2A ..." >>
  /usr/users/svplus/log/.start_stopCWM.log
  su - svplus -c /usr/users/svplus/scripts/startorbix2000 >> 
/usr/users/svplus/log/.start_stopCWM.log
  sleep 5

# Running Guard process ... as svplus
  echo "Running Guard process" >>
  /usr/users/svplus/log/.start_stopCWM.log
  su - svplus -c /usr/users/svplus/scripts/Install/RunGuard &


# Start CWM core process ... as svplus
  su - svplus -c /usr/users/svplus/scripts/start_SV+ &

******************************************************************


Note To save your changes while using the vi editor, remember to press Esc, colon (:), then wq!.


Step 5 Provide execute permissions for /etc/rc3.d/S99init_sv by executing the following command

# chmod 755 S99init_sv 


Note In order to auto restart informix after reboot, a shell script has been created automatically during the initial CWM installation. This script is called /etc/rc3.d/S98init_db. You need to make sure that the filename of your newly created autorestart shell script has a script number (the second and third characters in the filename) greater than 98. Also, your newly created autorestart shell script can not have the same script number as any other script files in /etc/rc3.d.


For more information on configuring this feature, refer to the /etc/init.d/README file.


SNMP Service Agent Release Notes

This section provides release note information about the SNMP Service Agent.


Caution When you delete a port on the BXM using the port proxy, the BXM line is also deleted.

CWM SNMP Agent Configuration Notes

The snmpd.cnf configuration file for the MasterAgent is located in the /usr/users/svplus/config directory. This file can be viewed or modified only by root.

CWM SNMPV1 module uses community strings for authentication. The CWM SNMP module uses the community strings defined in the snmpd.cnf config file. By default, the snmpget community string is public, and the snmpset community string is configured as private.

The user can modify the community strings by modifying the third column in the following lines from snmpd.cnf config file:

Syntax:

snmpCommunityEntry t0000000 private private localSnmpID - - nonVolatile

snmpCommunityEntry t0000001 public public localSnmpID - - nonVolatile

Modifying the trap_filter.conf file allows the customer to remove the traps they are not interested in. In order to ensure that the trap_filter.conf is recognized correctly, when registering the SNMP Manager with the CWM SNMP Agent, the customer must explicitly set the bit-mask to a value that is NOT the default, but still specifies all the used groups today. Group 28 is unused. Set the bit-mask to FFFFFFFFEFFFFFFF instead of accepting the default.

Error Code Changes with Release 12

A new error table called cwmErrorTable has been introduced in CWM 12.0.00. This table replaces the following CWM 11 error tables:

svCmpaErrorTable

psaErrorTable

cwmLineErrTable

cardPaErrorTable

The Proxy ErrorTable error codes have been changed from CWM 11 to 12. If you have been using are using compiler generated macros, these error code changes do not affect operations. If you have been using hard coded values for error codes, refer to Table 11.

Table 11 Release 11 to 12 Error Code Mapping 

Release 11 Error Codes
Release 12 Error Codes
MIB objects:psaErrorEcode, psaErrorLastEcode
 

{

 

invalid-network(1)

No Change

invalid-node(2)

No Change

invalid-shelf(3)

No Change

invalid-release(4)

No Change

node-timeout(5)

No Change

node-busy(6)

No Change

no-snmpcomm(7)

No Change

snmpcomm-error(8)

No Change

node-error(9)

No Change

bad-value(10)

No Change

port-not-found(11)

No Change

slot-is-full(12)

No Change

no-emd(13)

No Change

emd-error(14)

No Change

rowstatus-missing(100)

(28)

port-exists(101)

(1101)

invalid-slot(102)

(15)

invalid-line(103)

(23)

line-is-full(104)

(1104)

multiple-ports(105)

(1105)

port-reserved(106)

(1106)

na-frsm(107)

(1107)

na-frp(108)

(1108)

no-up-down-frsm(109)

(1109)

invalid-set(110)

(165)

illegal-set(111)

(18)

partial-add(112)

(117)

na-ausm(113)

(1113)

na-iam(114)

(1114)

na-atm(115)

(1115)

na-bxm(116)

(1116)

na-hs1(117)

(1117)

na-cesm(118)

(1118)

invalid-port-index(119)

(1119)

unsupported-card(120)

(25)

lmi-var(121)

(1121)

na-ufm(122)

(1122)

na-frm(123)

(1123)

na-asi(124)

(1124)

na-card(125)

(26)

missing-mandatory(127)

(19)

na-frsm-hs1(128)

(1128)

invalid-line-number(129)

(24)

na-ufmU(130)

(1130)

protocol-group-not-found(131)

(1131)

na-frasm(132)

(1132)

na-uxm(133)

(1133)

link-station-not-found(134)

(1134)

channel-route-not-found(135)

(1135)

channel-not-found(136)

(1136)

card-not-found(137)

(27)

invalid-grp-type-index(138)

(1138)

invalid-grp-number-index(139)

(1139)

invalid-station-addr-index(140)

(1140)

db-access-error(141)

(207)

internal-error(142)

(208)

link-station-exists(143)

(1143)

max-link-station-count-reached(144)

(1144)

na-port-type(145)

(1145)

invalid-channel-dlci-index(146)

(1146)

channel-route-exists(147)

(1147)

max-channel-route-count-reached(148)

(1148)

protocol-group-exists(149)

(1149)

max-protocol-group-count-reached(150)

(1150)

invalid-config-type(151)

(1151)

invalid-card(152)

(1152)

na-bme(153)

(1153)

plcp-not-found(154)

(1154)

port-queue-not-found(155)

(1155)

na-vism(156)

(1156)

mgcres-already-exists (157)

(1157)

mgcres-not-found(158)

(1158)

mgcres-bad-value (159)

(1159)

mgc-already-exists (160)

(1160)

mgc-not-found (161)

(1161)

mgc-not-exist (162)

(1162)

mg-cntlr-not-found(163)

(1163)

mgc-bad-value (164)

(1164)

xgcp-peer-not-found(165)

(1165)

srcp-peer-not-found (166)

(1166)

mgc-protocol-not-found (167)

(1167)

mgcp-not-exist (168)

(1168)

mgcp-already-exists(169)

(1169)

mg-sup-prtcl-not-found (170)

(1170)

mgc-endpt-exists (171)

(1171)

vism-endpt-exists (172)

(1172)

vism-endpt-not-found(173)

(1173)

vism-endpt-not-exist(174)

(1174)

vism-crossconnect-exists (175)

(1175)

vism-lapd-not-found(176)

(1176)

vism-lapd-exists(177)

(1177)

line-not-enabled(178)

(1178)

ds0-already-used(179)

(1179)

rudp-session-not-found(180)

(1180)

pnni-nodeId-not-found(181)

(1185)

no-error-entry(500)

(97)

not-applicable(501)

(98)

invalid-flushall(502)

(99)

invalid-ipaddress(503)

(1181)

invalid-subnetmask(504)

(1182)

}

 
MIB objects:cwmLineErrEcode, cwmLineErrLastErrCode
 

{

 

invalid-network(1)

No Change

invalid-node(2)

No Change

invalid-shelf(3)

No Change

invalid-release(4)

No Change

node-timeout(5)

No Change

node-busy(6)

No Change

no-snmpcomm(7)

No Change

snmpcomm-error(8)

No Change

node-error(9)

No Change

bad-value(10)

No Change

port-not-found(11)

No Change

slot-is-full(12)

No Change

no-emd(13)

No Change

emd-error(14)

No Change

rowstatus-missing(100)

(28)

port-exists(101)

(1101)

invalid-slot(102)

(15)

invalid-line(103)

(23)

line-is-full(104)

(1104)

multiple-ports(105)

(1105)

port-reserved(106)

(1106)

na-frsm(107)

(1107)

na-frp(108)

(1108)

no-up-down-frsm(109)

(1109)

invalid-set(110)

(165)

illegal-set(111)

(18)

partial-add(112)

(117)

na-ausm(113)

(1113)

na-iam(114)

(1114)

na-atm(115)

(1115)

na-bxm(116)

(1116)

na-hs1(117)

(1117)

na-cesm(118)

(1118)

invalid-port-index(119)

(1119)

unsupported-card(120)

(25)

lmi-var(121)

(1121)

na-ufm(122)

(1122)

na-frm(123)

(1123)

na-asi(124)

(1124)

na-card(125)

(26)

missing-mandatory(127)

(19)

na-frsm-hs1(128)

(1128)

invalid-line-number(129)

(24)

na-ufmU(130)

(1130)

protocol-group-not-found(131)

(1131)

na-frasm(132)

(1132)

na-uxm(133)

(1133)

link-station-not-found(134)

(1134)

channel-route-not-found(135)

(1135)

channel-not-found(136)

(1136)

card-not-found(137)

(27)

invalid-grp-type-index(138)

(1138)

invalid-grp-number-index(139)

(1139)

invalid-station-addr-index(140)

(1140)

db-access-error(141)

(207)

internal-error(142)

(208)

link-station-exists(143)

(1143)

max-link-station-count-reached(144)

(1144)

na-port-type(145)

(1145)

invalid-channel-dlci-index(146)

(1146)

channel-route-exists(147)

(1147)

max-channel-route-count-reached(148)

(1148)

protocol-group-exists(149)

(1149)

max-protocol-group-count-reached(150)

(1150)

invalid-config-type(151)

(1151)

invalid-card(152)

(1152)

na-bme(153)

(1153)

plcp-not-found(154)

(1154)

port-queue-not-found(155)

(1155)

na-vism(156)

(1156)

mgcres-already-exists (157)

(1157)

mgcres-not-found(158)

(1158)

mgcres-bad-value (159)

(1159)

mgc-already-exists (160)

(1160)

mgc-not-found (161)

(1161)

mgc-not-exist (162)

(1162)

mg-cntlr-not-found(163)

(1163)

mgc-bad-value (164)

(1164)

xgcp-peer-not-found(165)

(1165)

srcp-peer-not-found (166)

(1166)

mgc-protocol-not-found (167)

(1167)

mgcp-not-exist (168)

(1168)

mgcp-already-exists(169)

(1169)

mg-sup-prtcl-not-found (170)

(1170)

mgc-endpt-exists (171)

(1171)

vism-endpt-exists (172)

(1172)

vism-endpt-not-found(173)

(1173)

vism-endpt-not-exist(174)

(1174)

vism-crossconnect-exists (175)

(1175)

vism-lapd-not-found(176)

(1176)

vism-lapd-exists(177)

(1177)

line-not-enabled(178)

(1178)

ds0-already-used(179)

(1179)

rudp-session-not-found(180)

(1180)

no-error-entry(500)

(97)

not-applicable(501)

(98)

invalid-flushall(502)

(99)

invalid-ipaddress(503)

(1181)

invalid-subnetmask(504)

(1182)

invalid-ima-group(505)

(1183)

invalid-ima-link(506)

(1184)

}

 
MIB objects:cardPaErrorEcode, cardPaErrorLastEcode
 

{

 

invalid-network(1)

No Change

invalid-node(2)

No Change

invalid-shelf(3)

No Change

invalid-release(4)

No Change

node-timeout(5)

No Change

node-busy(6)

No Change

no-snmpcomm(7)

No Change

snmpcomm-error(8)

No Change

node-error(9)

No Change

bad-value(10)

No Change

port-not-found(11)

No Change

slot-is-full(12)

No Change

slot-not-found(13)

(20)

invalid-slot(14)

(15)

no-error-entry(15)

(97)

not-applicable(16)

(98)

invalid-flushall(17)

(99)

illegal-set(18)

No Change

missing-mandatory(19)

No Change

mandatory-param(20)

(164)

db-access-error(21)

(207)

internal-error(22)

(208)

invalid-line(23)

No Change

invalid-line-number(24)

No Change

unsupported-card(25)

No Change

na-card(26)

No Change

card-not-found(27)

No Change

rowstatus-missing(28)

No Change

partial-add(29)

(117)

invalid-set(30)

(165)

na-vism(3001)

(1156)

mgcres-already-exists (3002)

(1157)

mgcres-not-found(3003)

(1158)

mgcres-bad-value (3004)

(1159)

mgc-already-exists (3005)

(1160)

mgc-not-found (3006)

(1161)

mgc-not-exist (3007)

(1162)

mg-cntlr-not-found(3008)

(1163)

mgc-bad-value (3009)

(1164)

xgcp-peer-not-found(3010)

(1165)

srcp-peer-not-found (3011)

(1166)

mgc-protocol-not-found (3012)

(1167)

mgcp-not-exist (3013)

(1168)

mgcp-already-exists(3014)

(1169)

mg-sup-prtcl-not-found (3015)

(1170)

mgc-endpt-exists (3016)

(1171)

vism-endpt-exists (3017)

(1172)

vism-endpt-not-found(3018)

(1173)

vism-endpt-not-exist(3019)

(1174)

vism-crossconnect-exists (3020)

(1175)


Caveats

This section lists known and resolved anomalies in the CWM 12.0.00 software and other associated software. The resolved anomalies include all anomalies resolved in CWM 11.0.10, Patch 4.1 and below.

Anomalies Resolved in the CWM 12.0.00, Patch 3 Software

Table 12 lists internally found Severity 1 through 2 anomalies and externally found Severity 1 through 3 anomalies as of 05/17/04 that were resolved in CWM 12.0.00, Patch 3 software.

Table 12

Bug ID
Description

CSCdx95326

pir is -1 in atm_conn for AXSM abrstd segments

CSCea62022

svplusL1.log file should be cleaned up for error logging

CSCeb03020

ILMITopoc does not resync with the network when NTS restarts

CSCeb03537

file_info table has too many entries so that GUI is slow.

CSCeb03797

port_ques table is not cleaned up at card related DB cleanup

CSCeb12252

emc does not clean up rsc_part table per card after its removed

CSCeb45240

core will not come up if watchdog is in the process table

CSCeb46325

Corba exception error on the console

CSCeb46519

part of the stats GUI is hidden under Task Bar in PC client

CSCeb55958

Stats can not be enabled using SCM Proxy if redundancy is setup

CSCeb64787

7 more stats need to be added to SRM/SRME: SRMEB

CSCeb65351

Incorrect pnport shown in display trunks for a routing node with IGX feeder

CSCeb70294

pnni_nodal_data and pnni_port_data table entries are missing in agerconfig_new

CSCeb77518

"emd emc & ooemc processes did not spawn for 30mins after starting core"

CSCeb77751

Cwm mispopulates varbind for 28102

CSCeb80667

should not resync card when switchover if card not the AXSM with tranid

CSCeb80899

Parser puts incorrect values for 64-bit counters in some cases

CSCeb87700

card synchup fails when redundancy is removed.

CSCec22463

An ABW reported by emc purify

CSCec23612

fc_fw_rev incorrect for vism card following clrsmcnf on pxm1e node

CSCec27052

ooemc coredumped timedEventQueue is removing a timer event

CSCec27217

AUTO: Wrong OID or problem with Varbind

CSCec28933

CD2: PXM1 T3E3 line coding shows differnet in table fromat

CSCec41286

status in ausm_port maps to 15 for upper level down

CSCec42162

egr_srv_rate in atm_connection not updated for trap 50601

CSCec45539

statsparser for xg puts incorrect values for all keys > 256

CSCec46170

EMC failed processing trap 50915

CSCec47932

MGX8850R2/MGX8950 nodes shown as unreachable during periodic/manual resync

CSCec49723

MPSM8-DT: ooemc coredumped; trapQ config in progress for MPSM8T1E1.

CSCec49737

MPSM8-DT: connection alarm inconsistency in DB; portAlrm shown as AIS.

CSCec51151

EMC-HARD resync.C NotifyDatabrokerResync() has performance issue

CSCec52813

11010P4C:NWBrowser shows the APS flag enable after deleting the APS line

CSCec53956

"CMG not supporting FRSM-HS2/B speeds 2.4 4.8 9.6 19.2 38.4Kbs"

CSCec55981

vism endpoint state change didn't send out traps

CSCec56482

db not updating vism line loopback after line disabled

CSCec56561

alarm state remains clear after linelocalloop removed

CSCec66245

"Tree View Inspector View didn't get updated after PXM1E upgrade"

CSCec66295

ooemc coredump due to card redundancy handling and timer

CSCec74855

cant enable stats on MGX 8850 Rel 1 were set/get strings are diff

CSCec74973

ooemc coredump while deleting cons during resync

CSCec76771

11010P4C:Cannot delete incomplete connection from CMGUI

CSCec79995

SCM GUI must use fully qualified host name

CSCec84309

ILMITopoc reintializes relates to admin weight resync

CSCec87848

csridd failing when using NFS mounts

CSCec89541

sdbroker coredump

CSCec89874

Read Trap flag stays ON after RTM trap upload

CSCed01334

scmcollsvr core dumped when stats collection was stoped on SSM

CSCed01993

Informix stops due to shared memory problems

CSCed02607

"MPSM8-DT: emsc process coredumped unknown reason."

CSCed03019

CWM install script remove /system then create a softlink

CSCed04178

AXSME/VXSM: cnfcdmode trap is not being forwarded to EM by NTS

CSCed06198

dummyline and vt port not exist for RPM-XF card caused resync failed

CSCed27387

ilog communication between cwmftpd and scmcollsvr problems

CSCed28408

EMC SetDbAggStatus() is seen to have SQL syntax error

CSCed31344

Failed alarm remain on hybrid conns after recovery from failure state

CSCed32627

vism-pr version is wrong in card table

CSCed37999

CMSC: Missing LMI configuration option from Config Center

CSCed38236

During warmstart emsc does not insert new connections into db

CSCed40218

SNMP getnext cwmPrefRouteNENode returns trailing spaces and embedded null byte

CSCed45446

trapd.conf got overwritten after installing 11.0.10 Patch 4.1

CSCed45619

"EMC-HARD <AddDbPeripheral> SQL insert failed sqlcode = -239"

CSCed46049

CWM connection shows Abit OK when Ingress-AbitFail showed in switch

CSCed47389

incorrect node alarm in tree view due to incorrect msg from EM

CSCed47623

nts failed to generate snmp timeout in time

CSCed49728

CwmGs coredumped while handling the telnet relay

CSCed49841

CWM Web Start Client not able to resolve servers IP/hostname in NAT

CSCed50113

vnni axsmxg ports as failed in db

CSCed50179

MPSM-T3/E3 line length is not changed in DB if its modified w/ val>6400

CSCed50699

Some Stats names are reversed for PXM1E Connection

CSCed50929

Config restore fails

CSCed50999

EMC coredumps if 50002 trap proc timer expires during node resynching

CSCed56044

sctDaemon core dump if stats enable is selected in Connection template

CSCed56923

UVM and HDM cards are not shown in stats conf gui

CSCed57210

EMC-HARD:RemoveConfig is deleting the object in wrong order

CSCed57913

Add/Del Feeder doesn't get updated

CSCed58074

ConnMgr cannot show DAX connection for FR (master)--RPM (slave)

CSCed60373

4000 conns missing from user_connection table

CSCed60892

party alarm file not upload in MGX 8850 PXM1E platform

CSCed60899

"BPX-SES conn alarm trap 60306 and party alarm trap 70403 not handled"

CSCed61817

"Wingz reports 0 but manual queue returned 900 on ATM raw conn stats"

CSCed63769

AR discovery failed as emsd exited without killing its children

CSCed64133

conn became incomplete after warm start because of update counter mismatch

CSCed64979

VBR hybrid connection fails do to incorrect %util mapping

CSCed66238

no backcard shown in chassis view for AXSM after clrsmcnf

CSCed68287

SES nodes stuck in mode 1;emd not handling topod and vnd msg sequence

CSCed74687

CwmGs core file when applying profile to users in Sec. Mgr

CSCed75192

CWM deletes invalid PNNI endpoint during incomplete conn delete (model 136)

CSCed80559

emc can core if .CF not containing port entry at parsing

CSCed80873

Some of the Mib files are not loaded with CWM 12.0

CSCed81484

informix crash creates provisioning and other problems

CSCed81593

trap 1006 was not generated after comm failure on BPX

CSCed81613

CWM has to give up RTM upload on bogus trap contents

CSCed81946

LSNT: emc core dumped when encountered tftp disconnect event

CSCed82379

put api in libftp throws errors sometimes for a large number of requests

CSCed82602

nodal community strings not working for polling svNodeGrp objects

CSCed84487

emc coredump at Dbg() within ClearPendingTrap for 50002 preproc

CSCed87049

CwmGs core dump during CgmServer cleanup

CSCed90489

IGX ATM Top Utilized Connection values show > 100%

CSCed92335

Emc coredump during purify run

CSCed92999

Query return val not properly protected in DBAccess lib

CSCed93708

LSNT:MGX8250 and MGX8220 feeders stuck in mode 1 due to emc deadlock

CSced94286

NWReport coredump when plotting Top Utilization for IGX/BPX

CSCed94948

incorrect source ip for BPX comm fail traps in trapd.log

CSCed95038

LSNT: 6 MGX8220 nodes stuck in mode 1

CSCee01432

Cannot load IANAifType-MIB into HPOV

CSCee02781

"nts udp buffer overflow nodes not syncing up"

CSCee06399

cmsvr reinitialized once

CSCee08788

libtftp throws RECVFROM_FAILED exception when doing intensive upload

CSCee10383

"frEndPointPercUtil modify fails with traffic parameters err OvrSubOvrRide ena"

CSCee13056

libtftp: error number not set when bind fails

CSCee15367

ooemc and emc not populating channel_map of vism_endpt for ds0 31 of VISM E1

CSCee21784

Cannot launch SCT GUI on conditional primary

CSCee21875

nts does not use configured community strings causing unreachable nodes

CSCee34111

Routing Params are not complete for Ce-Ce connection

CSCin45358

Loopback param incorrectly updated in db for FRSM-2T3 on 8850

CSCin45568

Line Coding param shows incorrect value for FRSM-HS1 on 8220

CSCin49960

rt/nrt-vbr2 PVC FR-ATM connections shown as rt/nrt-vbr3 in CM gui.

CSCin50334

NWBrowser: Didn't get updated with newly added AUSM line/port on 8250.

CSCin50747

Party process coredumped on stopping core.

CSCin56162

CESM card re-insertion does not update card table correctly.

CSCin56883

DB not getting updated when a line is added on PXM-1

CSCin58082

Incorrect line type is populated for CESM E3 lines on MGX1 node

CSCin60382

service modules are not shown in MGX8230 after config-restore in cwm - error i

CSCin61233

AUTO: Database is not updating for modification of SRM lines(8250R1)

CSCin61899

line_type updated as DS3 for SONET lines on PXM1 in database.

CSCin62904

NWBrowser shows the connector type as unknown for SRME card

CSCin64272

Add/Remove node to user group not correct when inplace submap is open.

CSCin65282

Cannot set country maps for certain countries in NM gui.

CSCin70994

Line Coding populated wrongly in DB for CESM-T3 card on MGX-8850

CSCin71207

NWBrowser shows local loop as remote and vice versa on AXSM sonet line

CSCin71251

sdbroker coredump while deleting RPM-FR/ATM conns from CMGUI

CSCin71456

Inconsistent signal state shown in NWBrowser for FR port

CSCin71747

Line stat severity for CESM-T1 is populated as NA in NWBrowser

CSCin71913

IMA port grp alarm is not consistent with db/NWBrowser

CSCin72014

Clear Logs (C) option is not clearing any logs under ~svplus/log if many files

CSCin74875

SCT Daemon not registered with CWM after warmstart with some conn.templates ad


Anomalies Resolved in 12.0.00, Patch 3

Known Anomalies in CWM 12.0.00, Patch 3 Software

This section lists known anomalies in CWM 12.0.00, Patch 3 software as of May 17, 2004.

Table 13 Known Anomalies in CWM 12.0.00, Patch 3 Software 

Bug ID
Description

CSCdz55698

Headline:

Topology - Display Trunk shows PNNI Protocol instead of Feeder

Symptom:

In the Network Topology GUI, when you right click on a feeder trunk connected to a PNNI Routing node and choose Display Trunk, the protocol field shows PNNI instead of LMI.

Conditions:

Protocol will always show as PNNI instead of LMI.

Workaround:

Unknown

CSCea62490

Headline:

CWM shows 4294967295 for Max Cost parameter but -1 is on switch

Symptom:

Large number 4294967295 (4 Gig) showed in CMGUI for SPVC ATM-ATM Max Cost but switch CLI shows -1.

Conditions:

When CMGUI is used for viewing connection for SPVC or Hybrid.

Workaround:

Use Connection Proxy.

CSCeb29621

Headline:

Channel Trap Upload sets incorrect Valid Flag for cwaChanSCR for CBR

Symptom:

SNMP GET for atmEndPointSCRZeroPlus1 is 0 for non-applicable conn subtypes

Conditions:

MGX8850 rel 4.0 switches

Workaround:

Unknown

CSCeb68381

Headline:

Upper level alarm in atm-conn table for axsm-xg conns

Symptom:

ok connection shown as failed

Conditions:

upper level alarm is present on one end point in atm_connection table for axsm-xg

Workaround:

resync

CSCeb74413

Headline:

Multiple webserver core dumps

Symptom:

Multiple webserver core dumps

Conditions:

unknown

Workaround:

unknown

CSCeb75495

Headline:

Connections display as ok when card is removed.

Symptom:

Configuration is not being removed from DB when card is pulled out

Conditions:

Card is removed and switchcc or resetsys was done more than once.

Workaround:

None.

CSCed22861

Headline:

user conn traps not expanding Local/Remote strings with node name

Symptom:

user conn traps not formatting local/remote strings correctly

Conditions:

running 12.0.00-P1.1, checking OV trapd.log

Workaround:

Unknown

CSCed24563

Headline:

SSM GUI does not get refresh when ssc status change to reachable

Symptom:

GUI does not get refresh for SSC status on monitor tab

Conditions:

when core was brought up on SSC

Workaround:

either open new GUI or go to all the level up the tree and then down

CSCed91850

Headline:

xdbroker reinitialized

Symptom:

xdbroker reinitialized once

Conditions:

Running 12.0.00-P1.1

Workaround:

Process was respawned by watchdog

CSCee16564

Headline:

l_network_id is stored as -1 in atm_connection during L1 node resync

Symptom:

l_network_id is populated as -1 in atm_connection table during Level 1

manual node resync

Conditions:

Missing atm_connection entries are recovered by Level 1 manual node resync

Workaround:

Use Level 2 manual node resync

CSCee34980

Headline:

statsager core dump 3 times per minutes

Symptom:

Statsager keeps core dump, 3 times per minutes, with console message:

Assertion failed: (RWTime::isValid()) != 0, file ../rwtime.cpp, line 261

Conditions:

In time zone east of Greenwich, England. after DST change.

Workaround:

On the SCM GUI, disable the file purge.

CSCee40999

Headline:

CwmGs core dump after invalid login

Symptom:

CwmGs core dump after invalid login

Conditions:

One time occurence

Workaround:

None needed, CwmGs will restart and all client will reconnect.

CSCee50315

Headline:

PXM1 stuck in mode 5 because emc detects .CF missing bbIf port table

Symptom:

In CWM 12.0 p1.1, selnd indicates that the MGX 8230 PXM1 nodes remain in mode 5.

Conditions:

The emc log includes errors like:

14:12:33 EMERG: PERIPHERAL ALARM PARSE FAILED node cmgx-2

14:12:33 EMERG: Corrupted Config File for node cmgx-2 is saved under /usr/users/svlus/log.

Workaround:

None

CSCee57318

Headline:

scmcollsvr reinitialized twice

Symptom:

scmcollsvr reinitialized

Conditions:

12.0.00-P1.1 SCC

Workaround:

Unknown


Anomaly Status Changes in Release 12.0.00 Patch 3

Table 13 lists the known anomalies that have changed status in CWM 12.0.00, Patch 3 as of May 17, 2004. Changed status means that the anomaly changed from open in CWM 12.0.00, Patch 2 to a state other than resolved. The workaround states the status (closed, junked, duplicate, or unreproducible).

Table 14 Status Change Anomalies in CWM 12.0.00, Patch 3 Software 

Bug ID
Description

CSCeb28467

Headline:

Invalid checking of ADTF value on AUSM of ABR.FS connection

Symptom:

Invalid checking of ADTF value on AUSM of ABR.FS connection

Conditions:

BXM T3 card

AUSM 8E1 card on MGX 8220

Workaround:

n/a

Unreproducible State

CSCeb68663

Headline:

SSM doesn't have primary CWM as host after core is started

Symptom:

CWM host name is not updated on SSM after the core was started on SSM.

Conditions:

CWM Gateway switchover happened on CWM machines during the time when SSM core was down.

Workaround:

Update the host name manually using the command updatescminfo <cwm-host-name>

Closed State

CSCeb81600

Headline:

Connections deleted on one CWM is shown as incomplete in another CWM

Symptom:

Connections deleted on one CWM is shown as incomplete in another CWM.

Condition:

Deleted 524 connections on AXSM-XG-OC48 card in MGX8950 node through proxy

Workaround:

Unknown.

Unreproducible State


Anomalies Resolved in CWM 12.0.00 Patch 2 Software

Table 14 lists internally found Severity 1 through 2 anomalies and externally found Severity 1 through 3 anomalies as of January 2, 2004, that were resolved in CWM 12.0.00, Patch 2 software.

Table 15 Anomalies Resolved in 12.0.00, Patch 2 

Bug ID
Description

CSCdz25721

scm generates badfilelist when node name is changed while collecting

CSCea53665

Node resync need to clear out the port agg status

CSCea80386

Unload failed error while doing Incremental upload

CSCeb28413

Cannot create ABR.FS PVC on UXM-T3 with policing

CSCeb28733

Deletion of CE-CE fails. (Dup of CSCeb85154)

CSCeb29895

Secondary collector take place in delay after lo

CSCeb31451

statistics items for conn were displayed as diff

CSCeb40278

"Stats collection returns success on IN-BAND despite the Atm0 unreachable"

CSCeb45843

CWM Cannot Sync Up with MGX 8220

CSCeb48871

Add/Modify/Deactivate are enabled for inactive node in configurator

CSCeb54554

HCS Error info for service line is displayed as

CSCeb57258

dup node ip addr cause dup node_info entries

CSCeb61691

TFTP Timeouts enabling Stats on BPX/IGX nodes

CSCeb63246

HPOV trap severities need to be in sync with the

CSCeb64098

topod core dumped

CSCeb64139

CESM conn status inconsistent with switch after coldstart

CSCeb66363

statsager use a wrong DB name to access destroynode table

CSCeb67281

updateftpinfo does not update timestamp in cwm_i

CSCeb67920

Traps of size > 512 bytes not forwarded to HPOV

CSCeb69457

SCM GUI grays out when tried to click on a SSC/Ctrlr in monitoring view

CSCeb70993

linktopoc core dump

CSCeb71147

Topology - Truncating Node Names

CSCeb71165

Connection Manager locking up when click on the

CSCeb71268

ooemc core dump after resetcd

CSCeb73034

failed to update status in cesm_connection table for line fail traps

CSCeb73315

Hidden menu entry for users other than svplus

CSCeb75307

scm/ssm versions in GUI help and ~svplus/etc are not updated

CSCeb76329

Some MGX8850R2 nodes are in mode -1 for a long time after starting core

CSCeb77442

remote %util from AR segment not set correctly

CSCeb78848

SNMP requests timeout - PortProxy blocked on a single request

CSCeb79573

Conn -trace is failing from CESM endpoints to other mgx endpoints

CSCeb80050

l_network_id set to -1 in ausm_port and atm_connection table

CSCeb80267

emc reinitializes after port status trap with li

CSCeb81526

ooemc coredump when card removed/inserted multip

CSCeb85064

frsm-atm incomplete conns

CSCeb85154

CE conns added on axis cannot be modified/deleted.

CSCeb85322

process.conf is incorrect on SSC machine

CSCeb85734

Unable to launch 40 clients with a large network

CSCeb87244

Error message is not displayed if more desktops

CSCeb88206

User should not be forced to enter ICR if VSVD i

CSCec00672

problem reading stats file from certain MGX 8850

CSCec01865

CWMAdmin GUI didn't reflect the Admin GUIs opened

CSCec06775

emc process went into hibernation c

CSCec06811

some MGX 8220 and 8850 feeders are not discovered

CSCec08471

NWReport Coredump

CSCec08510

connection trap 25117 svConnDescri

CSCec08732

sdbroker coredump

CSCec09429

NO more vpi/vci error while provisioning when the switch still has available

CSCec13227

EMC needs to cancel prior snmp reqs at del trap

CSCec15885

StatsEnable and CCEnable MOD not reflected via dbkr_temp for FRSM12

CSCec16438

emc coredump

CSCec18559

Adding connection descriptor on an existing connection doesnt get updatedon WD

CSCec20627

sdbroker core dumped when multiple port & connection provisioning going on

CSCec24493

ILMITopoc reintialized

CSCec26911

incorrect slot.port info populated in DB

CSCec30039

wandest server installation should include database table selection

CSCec30209

prefroute deletion fails if dup prefroute Ids us

CSCec30259

cmgrd coredumps when delete is done from 9 Proxi

CSCec31982

"after AXSM upgrades nodes show mode=4 on CWM"

CSCec32494

xdbroker reinitialized

CSCec33348

topod reinitialized during ILOG

CSCec33423

emd reintialized following comm problems with topod

CSCec36613

Summary Reports does not work for Voice Connecti

CSCec38423

MIB files contradictory and compile problems

CSCec39121

Cant get CWM to generate 30000-30120 traps

CSCec40192

emc reinitilized when vism NSAP invalid

CSCec44855

chanTrapMgr.C may not do DB update on a few mib

CSCec46454

Connection deletion issue if feeder segment is deleted for 3 segment

CSCec48501

Need capability to limit users from enable/disable bert tests

CSCec51694

scmcollsvr reinitializes

CSCec54751

logical_slot val in card table incorrect after primary red card is removed

CSCec56073

CwmGs core dumped when trowing unk

CSCec58692

SCM unable to enable statistics on multiple selected nodes

CSCec59524

DMD may go into a loop when finishing syncup

CSCec60636

sdbroker memory leaks

CSCec61379

ooemc reinitialized wrt snmp upload handling

CSCec62432

Stopping stats collection causes scmcollsvr coredump

CSCec63283

linktopoc core dump (when core is running)

CSCec63401

java exception on the console while launching CV from browser

CSCec63717

runconfigurator deletes active nodes

CSCec63782

delete option is greyed out in the Edit menu for deactive node

CSCec64589

LineProxy CwmDs3ConfigTable support for MGX Rel 1 FRSMs

CSCec65396

Audit trail stopped logging events

CSCec65410

MGX8850 manual node resync fails from GUI (homologation?)

CSCec65986

CMGUI operations fail for atm-fr conn w

CSCec66011

Incorrect stdAbrType DefVal applied on CBR1 AUSM

CSCec66307

MPSM8-DT:XPVC non-default params revertedby CCGUI to default;stats/connDesc

CSCec67458

emc deadlock when cancel node event

CSCec67506

"softswitch both the pri and sec cards have wron"

CSCec70660

MPSM8-DT:linktopoc stuck in deadlock; SES stuck in mgmt_state=0.

CSCec70848

trap 60019 not forwarded to trapd.log (Dup of CSCec67920)

CSCec72209

xdbroker reinitialized a few times

CSCec72516

"emc sends -1 for line l_port and logical_port in msg to dbroker"

CSCec75012

scm is missing files of 1 intvl when password changed on node

CSCec76714

Incomplete fr cons on cold

CSCec77814

"provision fails incorrect min_rate used for port_speed"

CSCec80993

Mismatch in connection count between CWM-Switch

CSCec81887

cmgrd should NOT backoff segments if only dbroker comm times out

CSCec84355

need statsreader packaged in SSC standalone config

CSCec85422

Unable to change SNMP community strings for AXIS in Configurator

CSCec87140

Delete SCTs with minor revision # succeeds after association to port

CSCec87785

Scmcollsvr DOWN/UP due to system calls failure

CSCec88664

EMC getting NO SUCH NAME errors from snmp requests to VISM-8T1 card

CSCed01334

scmcollsvr core dumped when stats collection was stoped on SSM

CSCed01922

NTS to provide ability to suppress selected traps to CWM clients

CSCed08325

watchdog reinitialized single time

CSCed12507

cmsvr cores when sdbkr i/f timesout

CSCed14003

wandest upload coredumps

CSCed15070

AutoRoute Frame endpt strings are corrupted in cwmConn mib table(PVC segment)

CSCed21190

"after prefRoute delete query cwmPrefRouteNECount returns values"

CSCed21555

XPVC conn with atm-atm hybrid seg1 fails with err [bad value for one variable]

CSCed25141

"after resync on node with max frsm ports excess traps and DB updates occur"

CSCed26051

disable coredumps when stopping core on SSM/SSC

CSCed28293

EMC was not maintained on UpdDbPeripheral() with group_num new field

CSCed30520

lan ip is shown as atm ip when ip manageability

CSCed32440

Need to have rtmproxy only with ag

CSCin51142

PCR value in CM gui not ok for AXSM-XG-OC192 SPV

CSCin61164

unable to delete the incomplete cesm-8T1 connection with remote-end -1.0.-1.-1

CSCin62283

SCTGUI; red-cards shown twice after modification of sct

CSCin62739

Blnk NwB window gets launched with non-svplus user under certn conditions

CSCin64269

snmp get/walk shows wrong value for some parms in VISM rtpcons

CSCin64653

Nodes are not visible if there are too many trunks displayed


Known Anomalies in CWM 12.0.00, Patch 2 Software

This section lists known anomalies in CWM 12.0.00, Patch 2 software as of January 2, 2004.

Table 16 Known Anomalies in CWM 2.0.00, Patch 2 Software 

Bug ID
Description

CSCdz55698

Headline:

Topology - Display Trunk shows PNNI Protocol instead of Feeder

Symptom:

In the Network Topology GUI, when you right click on a feeder trunk connected to a PNNI Routing node and choose Display Trunk, the protocol field shows PNNI instead of LMI.

Conditions:

Protocol will always show as PNNI instead of LMI.

Workaround:

Unknown

CSCea62490

Headline:

CWM shows 4294967295 for Max Cost parameter but -1 is on switch

Symptom:

Large number 4294967295 (4 Gig) showed in CMGUI for SPVC ATM-ATM Max Cost but switch CLI shows -1.

Conditions:

When CMGUI is used for viewing connection for SPVC or Hybrid.

Workaround:

Use Connection Proxy.

CSCea71339

Headline:

Swap space problem on machine, creates process reinitialization

Symptom:

All swap space and memory is used severely affecting the CWM processes

Conditions:

Less swap space on the machine.

Workaround:

Either add more swap to the machine.

or

Reduce the number of BUFFERS in onconfig for Informix and restart Informix and CWM. This will slow down the database performance but CWM processes will not re initialize.

CSCeb28467

Headline:

Invalid checking of ADTF value on AUSM of ABR.FS connection

Symptom:

Invalid checking of ADTF value on AUSM of ABR.FS connection

Conditions:

BXM T3 card

AUSM 8E1 card on MGX 8220

Workaround:

n/a

CSCeb29621

Headline:

Channel Trap Upload sets incorrect Valid Flag for cwaChanSCR for CBR

Symptom:

SNMP GET for atmEndPointSCRZeroPlus1 is 0 for non-applicable conn subtypes

Conditions:

MGX8850 rel 4.0 switches

Workaround:

Unknown

CSCeb45240

Headline:

Core will not come up if watchdog is in the process table

Symptom:

Core won't come up if watchdog in process table

Conditions:

Any watchdog process activities present prior to starting core on SCM

Workaround:

Kill non-core watchdog processes. Stop or kill all processes tailing/vi'ing/etc anything with watchdog in it.

CSCeb55958

Headline:

Statistics can not be enabled using SCM Proxy if redundancy is setup

Symptom:

Can not enable statistics using SCM Proxy

Conditions:

Enabling statistics using the SCM Proxy while the logical slot is not active if redundancy is setup.

Workaround:

Enable the statistics through the SCM GUI.

CSCeb64787

Headline:

7 more stats id need to be supported for SRME/B

Symptom:

The following 7 Stat Id's are not shown in SCM GUI for SRM card types:

B3ZS Line Code Violations                 28 
Line Errored Seconds                      29 
Line Severely Errored Seconds             30 
P-bit Line Parity Errors                  31 
Errored Seconds - Parity                  32 
Severely Errored Seconds - Parity         33 
C-bit Parity Code Violations              34 

Conditions:

When using SCM for enabling all SRM card type. There are 7 stats IDs missing from the GUI.

Workaround:

Enable the missing 7 stats on the CESM or FRSM. The stats are applied for the DS3 line sub-object across all of the CESM/FRSM and SRM cards in the node. The stat file will contain the 7 stats and the SCM Parser will insert these into the Database.

CSCeb65351

Headline:

Incorrect pnport shown in display trunks for a routing node with IGX feeder

Symptom:

The display trunks dialog box in the NETopology GUI, shows incorrect trunk information for the feeder trunk between an IGX feeder node and an MGX8830 routing node

Conditions:

This might happen if the network has a large number of PNNI nodes and very few auto route nodes and the /usr/users/svplus/config/network.conf file has an auto route gateway specified for this network.

Workaround:

None

CSCeb68381

Headline:

Upper level alarm in atm-conn table for axsm-xg conns

Symptom:

ok connection shown as failed

Conditions:

upper level alarm is present on one end point in atm_connection table for axsm-xg

Workaround:

resync

CSCeb68663

Headline:

SSM doesn't have primary CWM as host after core is started

Symptom:

CWM host name is not updated on SSM after the core was started on SSM.

Conditions:

CWM Gateway switchover happened on CWM machines during the time when SSM core was down.

Workaround:

Update the host name manually using the command updatescminfo <cwm-host-name>

CSCeb74413

Headline:

Multiple webserver core dumps

Symptom:

Multiple webserver core dumps

Conditions:

unknown

Workaround:

unknown

CSCeb75495

Headline:

Connections display as ok when card is removed.

Symptom:

Configuration is not being removed from DB when card is pulled out

Conditions:

Card is removed and switchcc or resetsys was done more than once.

Workaround:

None.

CSCeb77518

Headline:

emd, emc & ooemc processes did not spawn for 30mins after starting core

Symptom:

emd, emc & ooemc processes did not spawn for 30 mins. after starting core

Condition:

start CWM core

Workaround:

Unknown.

CSCeb80899

Headline:

Parser puts incorrect values for 64-bit counters in some cases.

Symptom:

Stat counter values are incorrect for non-zero 64-bit counter values when reading using the statsreader tool or in the database

Conditions:

This is for 64-bit counters (AXSM-XG) and if the counter value exceeds 4 bytes (i.e.) more than half.

Workaround:

None.

CSCeb81600

Headline:

Connections deleted on one CWM is shown as incomplete in another CWM

Symptom:

Connections deleted on one CWM is shown as incomplete in another CWM.

Condition:

Deleted 524 connections on AXSM-XG-OC48 card in MGX8950 node through proxy

Workaround:

Unknown.

CSCed05677

Headline:

Nodes can be select multiple times even though one request is not completed

Symptom:

Stats GUI is very slow for giving status

Conditions:i

f there are 84 nodes in the network

Workaround:

none

CSCed06198

Headline:

dummyline and vt port not exist for RPM-XF card caused resync failed

Symptom:

RPM-XF card resync failed in the card resync file parsing if

the dummyline and vt_port not existed in the card, it make the card resync

failed, and finally cause mode 4.

Conditions:

RPM-XF card redundancy exist in the card resync

Workaround:

n/a


Anomaly Status Changes in CWM 12.0.00, Patch 2

Table 16 lists the known anomalies that have changed status in CWM 12.0.00, Patch 2 as of January 2, 2004. Changed status means that the anomaly changed from open in CWM 12.0.00, Patch 1.1 to a state other than resolved. The workaround states the status (closed, junked, duplicate, or unreproducible).

Table 17 Status Change Anomalies in CWM 12.0.00, Patch 2 Software  

Bug ID
Description

CSCeb28448

Headline:

EFCI value not set properly during creation of ATM PVC on BXM,AUSM.

Symptom:

EFCI value not set properly during creation of ATM PVC on BXM and AUSM

Conditions:

BXM T3 card

AUSM 8E1 card on MGX 8220

Workaround:

n/a

Further Problem Description:

CWM Service MIB is normalized across all platforms. BPX/IGX accepts EFCI Queue size in percentage (atmEndptEfciQSize), whereas AUSM accepts EFCI Queue size as absolute value (ingrQEfciThresh, as well as ingrQDepth). This is the reason cmgrd applies CONVERT_PERCENTAGE_TO_ABS while setting this value to non BPX/IGX switches and EM applies CONVERT_ABS_TO_PERCENTAGE while entering this value in CWM DB.

For e.g, if the user sets values as follows for an AXIS AUSM card, ingrQEfciThresh: 1 ingrQDepth: 1 the absolute value set on the switch will be 0 for ingrQEfciThresh

per - ingrQEfciThresh in percentage value base - ingrQDepth in cells abs - ingrQEfciThresh in absolute units (cells) (as set in switch)

CONVERT_PERCENTAGE_TO_ABS(per, base) (((per * base * 1.0) / 100.0) + 0.5) CONVERT_ABS_TO_PERCENTAGE(abs, base) ((((abs * 1.0) / (base * 1.0)) * 100.0) + 0.5)

Junked State

CSCeb28467

Headline:

Invalid checking of ADTF value on AUSM of ABR.FS connection

Symptom:

Invalid checking of ADTF value on AUSM of ABR.FS connection

Conditions:

BXM T3 card

AUSM 8E1 card on MGX 8220

Workaround:

n/a

Unreproducible State

CSCeb66471

Headline:

Some MGX2 nodes did not syncup after coldstart

Symptom:

Some MGX2 nodes were in mode 4

Condition:

The bandwidth available between CWM station and the network was not enough. This results in large number of errors on the network (collisions etc) and as a result FTPs become extremely slow.

Workaround:

Increase bandwidth between CWM and network. Also manual resync can be done on these nodes to get them in sync.

Junked State

CSCeb68663

Headline:

SSM doesn't have primary CWM as host after core is started

Symptom:

CWM host name is not updated on SSM after the core was started on SSM.

Conditions:

CWM Gateway switchover happened on CWM machines during the time when SSM core was down.

Workaround:

Update the host name manually using the command updatescminfo <cwm-host-name>

Closed State

CSCeb77950

Headline:

2 segment ATM-ATM hybrid connection in ERROR state

Symptom:

2 segment ATM-ATM hybrid connection in "ERROR" state

Conditions:

Immediately after adding connection

Workaround:

Unknown.

Junked State

CSCeb81600

Headline:

Connections deleted on one CWM is shown as incomplete in another CWM

Symptom:

Connections deleted on one CWM is shown as incomplete in another CWM.

Condition:

Deleted 524 connections on AXSM-XG-OC48 card in MGX8950 node through proxy

Workaround:

Unknown.

Unreproducible State


Anomalies Resolved in CWM 12.0.00 Patch 1.1 Software

Table 18 lists internally found Severity 1 through 2 anomalies and externally found Severity 1 through 3 anomalies as of 08/08/03 that were resolved in CWM 12.0.00, Patch 1.1 software.

Table 18 Anomalies Resolved in 12.0.00, Patch 1.1 

Bug ID
Description

CSCdt68502

Nodal community strings not working for svNodeEntry objects

CSCdx86279

Service affecting alarm creation traps not displayed

CSCdy86632

Network Browser GUI does not startup after installing a new patch

CSCdz76898

Node Delete using Configurator PER 7144

CSCea03375

XCNFILMI trap id 50915 is missing from trapd.conf file on MGX 8220

CSCea05999

Connections are ok on the switches failed on CM

CSCea14193

Incorrect display of link info for AXSM-XG in NW Topo

CSCea20044

scmcollection server coredumped - SSC registration to SSM

CSCea26062

dual node entries for mgx 8850

CSCea40817

Incorrect resulting PVC numbers in Summary Report

CSCea45757

CWM needs to set ICR irrespective of VSVD; ICR can be asymmetric for DAX conns

CSCea46616

scmctrlrsvr is restarted by watchdog

CSCea57681

Wandest client doesnt work in ksh environment

CSCea59868

After clrsrmcnf lines are missing from DB, card resync in not happening

CSCea59886

StatsAger is not able to keep up, when DB insertion rate is high

CSCea62404

SecMgr: Reset followed by Create failed when creating new profile

CSCea62496

SNMP GET of scAtmPortTable.svAtmPortOperState fails for UXM ports.

CSCea62611

need process to remove old ~svplus/tmp config files

CSCea63071

ooemc cores filling disk, MGX 8850 fail sync

CSCea63828

MGX 8230 feeders stays in mode -1 after Delete then add feeder again

CSCea64528

unreachable feeder shown as reachable

CSCea65131

SCT declares complete sync up without syncing up with some nodes

CSCea65793

User information not shown until hit Enter with MGX8220

CSCea66889

one MGX8850R2 node is in mode 4- config file got corrupted

CSCea67257

connection is shown as Ok on one machine fail on other and switch

CSCea68557

Corba ping_server utility on wandest client box

CSCea68830

FeederTrunk doesnt reflect alarm when AXSM card is pulled/reset

CSCea70661

SCR for middle-segment not set correctly for foresight conns

CSCea70852

CWMGateway cant connect to other machines in domain

CSCea71081

xdbroker re initializes

CSCea72297

emc core dump on PLCP processing

CSCea73714

CWM should return a consistent unit of measurement for svConnTestResult

CSCea75459

Bundled MIBs should be removed, reviewed

CSCea77654

ooemc cores on machine, ooemc PID taking large CPU time

CSCea78724

java re initializes on CWM machines

CSCea79990

IGX Feeder Trunk alarm shows as unreachable intermittently

CSCea80031

nodeinfocfg coredump

CSCea80228

XLMI link is not getting deleted when delport is done on BPX

CSCea80549

swap space problem on machine, creates process reinitialization

CSCea80629

Bulk deletion and readdition of traps not handled

CSCea80781

Stats files collected with null dimension from MGX and core dumped

CSCea82069

XLMI link is not discovered once it is deleted an re-added on AXSM

CSCea82091

scmcollsvr coredump - getservbyname failure

CSCea83896

Return null string for N/A svConnPrefRouteDesc

CSCea84134

Database error on SSM console

CSCea85646

Unknown Service Type Enum error in CMGUI XPVC mod attempt

CSCea85711

Incorrect connsubtype in userconn table for PVC VBR3NRT Connection

CSCea85749

SNMP walk on cwmPrefRouteSrcNode fails to fetch all pref routes on node

CSCea85897

conn descriptor is not shown if added for non atm as local end point

CSCea86967

ILMITopoc coredumped.

CSCea87005

Cant login after incorrect login

CSCea87012

ooemc created duplicate 0 byte config file

CSCea87848

Pref Route Modification Req produces out of range errors

CSCea88408

ooemc not processing traps

CSCea88616

orbix problems upon start core

CSCea89605

CWM Client not able to resolve to CWM server in a NAT Environment

CSCea90619

Emc doesnt handle fc_type change properly in config file parsing

CSCea91057

ooemc is not handling ima ports

CSCea92900

Stats are not deleted after a feeder node is deleted via runConfigurator

CSCea93846

ooemc core dumped when upgrading MGX8850 PXM45 switches

CSCeb00763

incorrect 50601 trap from FRSM slot

CSCeb00888

FR port addition created a new port entry with wrong port_type

CSCeb01052

FR port added on a failed line does not show proper status in frp entry

CSCeb02227

Trap Lost Trap (60900) Physical Slot to Logical slot change

CSCeb02272

removing the subtrap timer before card resync

CSCeb03364

SNMP Query to svConnSubType returns incorrect value

CSCeb04761

wrong sonet line class design causing pxm.cf file not parsed

CSCeb04804

TFTP failure on PXM slot does not get retried.

CSCeb05160

when card file parsing fails, ooemc process in loop

CSCeb05223

GUI connection was lost: corba disconnected

CSCeb06122

ConnProxy needs to derive end2endtype based on network ids for xpvc

CSCeb07133

SCM stat descs in GUI, doc incorrect and don't match CLI

CSCeb08301

ooemc core dump

CSCeb09131

Newly added XPVC connection in OK state when xpvc_segments show FAIL

CSCeb10544

Memory leaks in OOEMC found in purify reports during em-hardening

CSCeb10772

tftp and error messages on console

CSCeb11480

wrong mapping for 60905

CSCeb11788

SNMP GET on VISM 1.5.08 card objects fail

CSCeb12040

upper level alarm did not set in NotifyDataBrokerResync()

CSCeb12163

emc could lose signal to increment timers ticks

CSCeb13077

grayed out window when three groups were opened in PNNIView

CSCeb13100

multiple statsager coredumps

CSCeb13201

UPD buffer is full and NTS drops the traps

CSCeb13281

Memory leaks in emc found in purify during em-hardening

CSCeb13630

memory leak when inserting to nodal_ig table

CSCeb14163

ooemd coredump - activity unknown

CSCeb14595

ooemc reinitialized on cwm machine

CSCeb14776

when core was stopped watchdog was still up

CSCeb14871

port status wrong for port created on a failed(in alarm) line.

CSCeb14967

New traps in CWM 11.0.10 patch 2 have ipaddress in wrong format

CSCeb18173

Incorrect values for mir,qir and pcr populated in database for abr1 2 seg hybrid conn

CSCeb19056

Del followed by deactivate for SA node doesnt del node from Topo GUI

CSCeb19116

Fully operational trigger for xpvc_segment table is replaced with no-op trigger

CSCeb20269

CWM Admin GUI: GUIs don't disconnect

CSCeb20331

node in mode 2 after auto resync

CSCeb20408

scdDaemon continuously coredumps in gateway setup

CSCeb20943

when secondary become active, pri card should not be updated with sec card

CSCeb21091

Node moved to a different group but drag optimizer stays

CSCeb22787

ILMITopoc continuously coredumps during dynamic addition of PNNI/XLMI links

CSCeb22793

AR discovery can fail if IGX feeders to MGX are unreachable

CSCeb23552

Bringing down oper status of a PGL deletes the peer group from tree view

CSCeb24029

IGX Fdr trk alarm is not updated for resetcd/resetsys on MGX 8850(PXM45)

CSCeb24087

PNNI View does not update aggregation token and new links in few desktops

CSCeb24195

Wandest & StatusView - sequencing issues with connection & desc table uploads

CSCeb24218

nts does not send unregistered notification to its clients

CSCeb24608

cant set PrefRoute for 2seg xpvc, db conn seg missing

CSCeb25345

SES-SES link is not re-discovered and stayed grey

CSCeb25815

Cannot set PCR/SCR to 0 on the ASI side for ATM-ATM conn. between ASI-AUSM

CSCeb26642

Stats data from few tables doesnt get deleted for de-commissioned node

CSCeb26689

CESM connections become incomplete after manual resync

CSCeb26913

failed connections showing as down due to databroker problem

CSCeb27597

CWM database does not show alarm info for MGX1 DAX connection

CSCeb28199

Incorrect processing of 60903 trap for Shelf Generic file on PXM1E

CSCeb28738

ooemc coredumped while removing time event from time event queue

CSCeb29390

persistent topology nodes are not discovered when gateway is enabled

CSCeb29416

Stats for deleted node doesnt get deleted from Secondary CWM

CSCeb29522

scmcollsvr coredumped on SSC and CWM server

CSCeb29718

PNNI nodes stuck in mode 5, UDP buffer is full

CSCeb29804

Toposvr core dumped

CSCeb29907

Peer groups with single unreachable node not deleted after warmstart

CSCeb30096

statsreader gives meaningless obj/subobj

CSCeb30599

Inconsistency in FRSM-VHS connStatus between CLI and CWM database/GUI

CSCeb30719

Sdb shared memory overflow splits routing and feeder msgs

CSCeb30757

SSM does not switch over to New primary CWM, when both were down.

CSCeb30770

Virtual link is shown as unreachable Virtual Link

CSCeb31194

MGX8220 and MGX8850R1 didn't sync up

CSCeb31287

unreachable node in pnni view on two levels

CSCeb31717

svAtmPortAssociatedLines returns incorrect ima port vals

CSCeb31854

Nodes didn't get discovered properly on ent6800 m/c

CSCeb32275

NTS clients cannot digests the traps at the same rate as NTS send it to them

CSCeb32351

mpgd does not send operstatus change message to toposerver

CSCeb32531

frsm_hs2b alarm_state in database don match node CLI after cable remove

CSCeb34474

ooemc core dump

CSCeb34791

enable field in line table is not set when AXSMXG OC48 line is enabled

CSCeb34840

Deleted logical node shown in PNNI View

CSCeb34889

unable to save/restore config

CSCeb36429

snmpget on LocOSpaceCells fails for 2/3 seg PVC connections

CSCeb37664

axsm-xg line changes in stats parser to enable successful parsing

CSCeb37739

Scm Control Server hangs if there is a LAN disconnect with SSC

CSCeb38529

PXM45 node stuck in mode 2.

CSCeb38921

Mod path width (60135,60139) and Up/Dn STS1path (60137) are not defined

CSCeb38925

Cant modify fr-fr XPVC if local fr endpt is at PXM45-8850

CSCeb39200

Numerous hybrid cons in false fail state after script AddConn

CSCeb39365

cwmftpd core dump

CSCeb39752

ILMITopoc re initializes

CSCeb39759

topod re initializes

CSCeb40183

emsc coredump after starting the core

CSCeb40527

ooemc core dump

CSCeb41209

Timeout required for collector to collector CORBA calls

CSCeb41690

no permission config restore returns pass

CSCeb42210

MBS out of range error during XPVC provision

CSCeb42262

path in alarm (LowLayerDn) is shown OperStatus = CLEAR (if not first path)

CSCeb42384

emc coredumped after starting the core

CSCeb42811

Port in alarm (LowLayerDn) is shown CLEAR

CSCeb43982

After processing the TrapTimerEvents, they are not reset properly

CSCeb44789

scmctrlsvr coredumps

CSCeb44798

CWM fails to sync-up with MGX nodes

CSCeb44946

node outside of PG

CSCeb45003

TopoServer coredumped

CSCeb45048

PGL update got delayed

CSCeb45066

pnni 2nd level node is up in cwm, down on the switch

CSCeb45491

snmpcomm core dumped

CSCeb45843

CWM Cannot Sync Up with MGX 8220

CSCeb46122

VPI number for VNNI/VUNI is always set to 0 in DB (AXSMXG)

CSCeb46405

need to handle new 70509 trap with additional varbind

CSCeb46762

cant add VISM-BXM hybrid connection

CSCeb46937

IMA physical trunk showing 255 as suffix on trunk display

CSCeb47540

vism connections have improper nsap address in db

CSCeb47637

incorrect trunk end point in TOPO GUI

CSCeb47671

PNNI view tree not updated in some cases

CSCeb47883

trunk not shown in topo gui/db

CSCeb48024

Secondary Card is not recognized correctly after putting back card

CSCeb48880

Object-finder shows line unreachable when it is in Mod state

CSCeb48987

linktopoc and filetopoc exit after the core is started due to ILOG errors.

CSCeb49466

CWM Gateway communication failure

CSCeb49515

unreachable node as reachable in node table

CSCeb49536

connections in AIS not the same on two CWMs

CSCeb50204

ConnProxy cores, times out on snmpget of primary and secondary XLMI link MIBs

CSCeb51290

ooemc coredumps in svpluscwm1 due to mem allocation

CSCeb51914

ooemc core dump

CSCeb52412

sdbroker coredumps while provisioning with 9 conn proxies

CSCeb53024

xpvc add fails MCR <= ICR <= PCR evaluates False for AR BXM endpts

CSCeb54036

incorrect lslot status for stdby cards

CSCeb54250

P2MPJ:DB not updated after receiving party update traps (add,del,alarm msg)

CSCeb54318

For an MGX1 connected to MGX8950 node, bis_object has -1 as parend nodeid

CSCeb55123

Unable to add connections using Connproxy

CSCeb55127

cmgrd coredump while provisioning with 9 proxies (add/mod/del/trace)

CSCeb55418

node sync up failed, mpgd deadlock

CSCeb56088

sdbroker re initializes

CSCeb56231

FMM memory error while processing PreferredRouteTraps

CSCeb56305

CwmGs coredump

CSCeb58444

multiple ILMITopoc coredumps after starting the core

CSCeb58700

CWMGateway core dumped as soon as core was started

CSCeb59691

linktopoc core dumped and AR discovery did not happen

CSCeb60035

multiple ILMITopoc coredumps after starting core

CSCeb60070

failed to create database, informix not online

CSCeb62275

P2MP: Party on VP con is not being deleted from CWM DB

CSCeb62277

LSNT: Install script did not stop and restart ORBIX

CSCeb62301

sdbroker corrupts cache while reading E3E6 incomplete connection in warmstart

CSCeb62650

mpgd coredumped.

CSCeb63692

emc core dumped after starting core

CSCeb63966

FMM memory corruption in emd while sending messages to children

CSCeb63993

mpgd node resync triggered by -2 trap leads to unknown nodes

CSCeb64139

CESM conn status inconsistent with switch after coldstart

CSCeb66056

feeders stuck in mode=1, need tftpmgr conf changes

CSCeb66470

ILMITopoc coredump caused by mem.corruption

CSCeb66576

wandest uninstall script changes the permission of .cshrc

CSCeb69428

Secondary SSC failed to start collection after LAN cable pulled out in Primary

CSCeb69949

re-applying unmodified %Util not propagated to PNNI nodes

CSCeb70128

Unable to launch 40 desktops using PC Client - GUI grey out. Due to Orbix comm

CSCeb70351

Most POP2 and PXM1 nodes in mode 2 or 5

CSCeb71194

CWM Patch1 installation has failed

CSCeb74259

connection inconsistencies between segment table and user_connection

CSCeb76101

sdbroker cache rebuilds, affect syncup, provisioning

CSCeb76846

Stats enabling takes long time for a large network

CSCin15035

Do not purge Option in stats DB host Configuration Dialog is not working.

CSCin15276

DB wrongly populated for target_line_frm in line distribution table

CSCin33451

SMs on AXIS not shown in CWM after being active after clrallcnf

CSCin35313

Delete Button not enabled after selecting a newly added connection

CSCin36977

FTP username and password tab in Configurator has wrong info for IGX

CSCin38986

Node name change on standalone -8250 is not getting updated.

CSCin40717

Can not launch desktop on disconnected Secondary CWM.

CSCin42863

MGX8850R2 node disappeared from topology on Feeder node deletion.

CSCin43676

IGX Feeder attached to MGX8850R2 not discovered in hybrid-AR discovery

CSCin43976

Deletion of Standalone from Runconfigurator is not working.

CSCin44201

nts coredumps on deletion of node from NW Configurator.

CSCin44489

Topod process coredumped

CSCin44544

Reachable SES shown as Unreachable and mode 1

CSCin44602

Topod coredumped after dellmi & addlmi on AXSM

CSCin44670

Incorrect FRM card details shown for IGX feeders

CSCin44705

ooemc coredumped

CSCin44948

Topology & node table has duplicate entry for same standalone node

CSCin45006

AR Network is not discovered with PNNI-Hybrid Discovery.

CSCin45109

Feeder trunk between IGX & 8850R2 didn't get discovered after warmstart.

CSCin45140

Line Length & OOF criteria params not updated in db for AXSM-T3E3 on 8850

CSCin45178

Medium type param not updated in n/w browser for AXSM-OC3 on 8850

CSCin45356

IMAGE Download fails if node name changed for 8850R2 while downloading.

CSCin45371

Wrong TRAP shown in HPOV for XPVC connection down/failure.

CSCin45504

Complete XPVC connections shown as incomplete after XLMI link addition.

CSCin45564

Gateway BPX node shown unreachable after discovery.

CSCin45860

EMD coredumped while CWM is syncing up.

CSCin46107

Line params not updated in db for PXM1E-T3E3 lines

CSCin46649

PNNI N/W discovery failed with AR-HYBRID Discovery (Has only XLMI bet N/ws)

CSCin46735

Network collapse should not be allowed if pref. route animation is running

CSCin46850

After SCT Daemon restart, can not download SCT templates to nodes.

CSCin47388

Java exception thrown if i click on Paths for AXSM-OC48-CHAN-XG (8950)

CSCin47820

SES nodes are stuck in mode 2 and not synced up with CWM.

CSCin48292

Failed PVCs shown as OK on 8250

CSCin48304

voice_conn table not updated for AUSM-VISM XPVC modification.

CSCin48314

Del. of NW element(!= SRC || DES) fails from proxy

CSCin48330

Pref. route Stop GUI shows incorrect rows

CSCin48395

Cannot modify/delete VISM-<any> PVC/hybrid conn. after VISM card reset.

CSCin48487

WD_SRV_ERROR on START of WANDEST client: Unknown key[]found

CSCin48931

Hybrid Connection on 8420 fdr shown as incomplete in primary CWM

CSCin49093

Cant add CUG on e164 address for uni30-uni40 port from gui if no CUG present

CSCin49112

Nodes with diff name are not removed from db on delete from runconfigurator

CSCin49713

Toposerver coredumped

CSCin49956

SCT-GUI: Show SCT is not working properly.

CSCin50074

Cant delete connections due to snmpcomm not running returned by cmgrd.

CSCin50788

README FILE needs to be updated for Evaluation version

CSCin51032

CwmGs coredumped 5 times on disconnecting-reconnecting LAN cable.

CSCin51119

Cannot add nrt-vbr1 and nrt-vbr2 conn with high PCR between AXSMXG ports.


Known Anomalies in CWM 12.0.00 Patch 1.1 Software

This section lists known anomalies in CWM 12.0.00, Patch 1.1 software as of August 8, 2003.

Table 19 Known Anomalies in CWM 12.0.00, Patch 1.1 Software 

Bug ID
Description

CSCdz55698

Headline:

Topology - Display Trunk shows PNNI Protocol instead of Feeder

Symptom:

In the Network Topology GUI, when you right click on a feeder trunk connected to a PNNI Routing node and choose Display Trunk, the protocol field shows PNNI instead of LMI.

Conditions:

Protocol will always show as PNNI instead of LMI.

Workaround:

Unknown

CSCea53665

Symptom:

Node resync is not clearing out the port aggregate status when line is not in alarm

Conditions:

Always

Workaround:

None

CSCea62490

Headline:

CWM shows 4294967295 for Max Cost parameter but -1 is on switch

Symptom:

Large number 4294967295 (4 Gig) showed in CMGUI for SPVC ATM-ATM Max Cost but switch CLI shows -1.

Conditions:

When CMGUI is used for viewing connection for SPVC or Hybrid.

Workaround:

Use Connection Proxy.

CSCea71339

Headline:

Swap space problem on machine, creates process reinitialization

Symptom:

All swap space and memory is used severely affecting the CWM processes

Conditions:

Less swap space on the machine.

Workaround:

Either add more swap to the machine.

or

Reduce the number of BUFFERS in onconfig for Informix and restart Informix and CWM. This will slow down the database performance but CWM processes will not re initialize.

CSCeb05223

Headline:

GUI connection was lost: corba disconnected

Symptom:

Topo GUI disconnected. The GUI showed the exit confirmation dialog that is normally shown when core is stopped. However, core was not stopped.

Conditions:

The GUI and server have a lease mechanism that is used to determine if there has been a disconnect. This lease mechanism does periodic pings to ensure the other side is still alive. When systems/networks get very busy, this lease mechanism can expire, even though the other side is still alive. To prevent false disconnects, the GUI will retry 5 times, waiting 5 seconds between each try before it gives up and determines the server really is dead. Since there are several corba servers that are monitored with this lease mechanism (CwmGs, cmsvr, scmcontrol, watchdog, toposerver, etc), is likely that lease expired and the client was unable to rebind in 5 retries.

Workaround:

There are no side effects of a GUI exiting this way. The user/application count in Admin GUI will still be correct. The workaround is just to restart the GUI that was exited.

CSCeb28413

Headline:

Cannot use the SNMP agent to create ABR.FS PVC on UXM-T3 with policing on and PCR < 50.

Symptom:

Cannot use the SNMP agent to create ABR.FS PVC on UXM-T3 with Policing ON and PCR < 50

Conditions:

Unknown

Workaround:

Use CM GUI to add the connection

CSCeb28448

Headline:

EFCI value not set properly during creation of ATM PVC on BXM,AUSM.

Symptom:

EFCI value not set properly during creation of ATM PVC on BXM and AUSM

Conditions:

BXM T3 card

AUSM 8E1 card on MGX 8220

Workaround:

n/a

Further Problem Description:

CWM Service MIB is normalized across all platforms. BPX/IGX accepts EFCI Queue size in percentage (atmEndptEfciQSize), whereas AUSM accepts EFCI Queue size as absolute value (ingrQEfciThresh, as well as ingrQDepth). This is the reason cmgrd applies CONVERT_PERCENTAGE_TO_ABS while setting this value to non BPX/IGX switches and EM applies CONVERT_ABS_TO_PERCENTAGE while entering this value in CWM DB.

For e.g, if the user sets values as follows for an AXIS AUSM card, ingrQEfciThresh: 1 ingrQDepth: 1 the absolute value set on the switch will be 0 for ingrQEfciThresh

per - ingrQEfciThresh in percentage value base - ingrQDepth in cells abs - ingrQEfciThresh in absolute units (cells) (as set in switch)

CONVERT_PERCENTAGE_TO_ABS(per, base) (((per * base * 1.0) / 100.0) + 0.5) CONVERT_ABS_TO_PERCENTAGE(abs, base) ((((abs * 1.0) / (base * 1.0)) * 100.0) + 0.5)

CSCeb28467

Headline:

Invalid checking of ADTF value on AUSM of ABR.FS connection

Symptom:

Invalid checking of ADTF value on AUSM of ABR.FS connection

Conditions:

BXM T3 card

AUSM 8E1 card on MGX 8220

Workaround:

n/a

CSCeb28733

Headline:

Deletion of CE-CE fails.

Symptom:

CE-CE connection deletion fails with msg, when CE endpoints are on MGX 8220 node [Wrong cesmChanNum value]

Conditions:

CE-CE Connection deletion on MGX 8220 platform

Workaround:

Delete the connection using switch CLI

Further Problem Description:

l_subchnl_2 and r_subchnl_2 populated in the user_connection table should be the channel numbers of the connection in switch CLI, which is the l_vci value populated in the cesm_connection table. In this case the l_subchnl_2 and r_subchnl_2 are populated incorrectly resulting in connection query from DB to fail and ultimately connection deletion to fail.

CSCeb29621

Headline:

Channel Trap Upload sets incorrect Valid Flag for cwaChanSCR for CBR

Symptom:

SNMP GET for atmEndPointSCRZeroPlus1 is 0 for non-applicable conn subtypes

Conditions:

MGX8850 rel 4.0 switches

Workaround:

Unknown

CSCeb45240

Headline:

Core will not come up if watchdog is in the process table

Symptom:

Core won't come up if watchdog in process table

Conditions:

Any watchdog process activities present prior to starting core on SCM

Workaround:

Kill non-core watchdog processes. Stop or kill all processes tailing/vi'ing/etc anything with watchdog in it.

CSCeb55958

Headline:

Statistics can not be enabled using SCM Proxy if redundancy is setup

Symptom:

Can not enable statistics using SCM Proxy

Conditions:

Enabling statistics using the SCM Proxy while the logical slot is not active if redundancy is setup.

Workaround:

Enable the statistics through the SCM GUI.

CSCeb57258

Headline:

duplicate node ip addresses cause duplicate node_info entries

Symptom:

Nodes with duplicate IP addresses cause duplicate entries in the node_info table and also cause some nodes not to get discovered.

Conditions:

This can happen if the network has nodes with duplicate lan or atm ip addresses.

Workaround:

Configure unique ip addresses for all the nodes in the network. If the lan interface for a node is not used then configure the ip as 0.0.0.0

CSCeb61691

Headline:

TFTP Timeouts enabling statistics on BPX/IGX nodes.

Symptom:

TFTP exception [%TftpException-3-RECVFROM_Failed: <recvfrom>Failed.] caught in [ScmStatEnabler_idl::enableStat] when enabling a large amount of stats on a BPX/IGX node.

Conditions:

When enabling on a node where TFTPing the file manually takes a long time (more than 120 seconds).

Workaround:

None.

CSCeb63246

Headline:

HPOV trap severities need to be in sync with the switch trap severities

Symptom:

For some of the MGX2/MGX1 traps, the severities shown in HPOV event browser are not the same as that sent by the switch.

Conditions:

None

Workaround:

Modify the /usr/users/svplus/OV/conf/C/StrataCom_trapd.conf file to have the desired severity.

CSCeb64098

Headline:

topod core dumped

Symptom:

Topod re initialized.

Conditions:

This may happen when nodes are added/deleted multiple times from the configurator,

Workaround:

None

Further Problem Description:

Topod gets respawned by watchdog. It recovers all the data from the other processes.

CSCeb64787

Headline:

7 more stats id need to be supported for SRME/B

Symptom:

The following 7 Stat Id's are not shown in SCM GUI for SRM card types:

B3ZS Line Code Violations                 28 
Line Errored Seconds                      29 
Line Severely Errored Seconds             30 
P-bit Line Parity Errors                  31 
Errored Seconds - Parity                  32 
Severely Errored Seconds - Parity         33 
C-bit Parity Code Violations              34 

Conditions:

When using SCM for enabling all SRM card type. There are 7 stats IDs missing from the GUI.

Workaround:

Enable the missing 7 stats on the CESM or FRSM. The stats are applied for the DS3 line sub-object across all of the CESM/FRSM and SRM cards in the node. The stat file will contain the 7 stats and the SCM Parser will insert these into the Database.

CSCeb65351

Headline:

Incorrect pnport shown in display trunks for a routing node with IGX feeder

Symptom:

The display trunks dialog box in the NETopology GUI, shows incorrect trunk information for the feeder trunk between an IGX feeder node and an MGX8830 routing node

Conditions:

This might happen if the network has a large number of PNNI nodes and very few auto route nodes and the /usr/users/svplus/config/network.conf file has an auto route gateway specified for this network.

Workaround:

None

CSCeb66471

Headline:

Some MGX2 nodes did not syncup after coldstart

Symptom:

Some MGX2 nodes were in mode 4

Condition:

The bandwidth available between CWM station and the network was not enough. This results in large number of errors on the network (collisions etc) and as a result FTPs become extremely slow.

Workaround:

Increase bandwidth between CWM and network. Also manual resync can be done on these nodes to get them in sync.

CSCeb67281

Headline:

updateftpinfo does not update timestamp in cwm_info table

Symptom:

The updateftpinfo script does not update timestamp in DB cwm_info table

Conditions:

Noticed after running updateftpinfo script after code updates

Workaround:

unknown

CSCeb68381

Headline:

Upper level alarm in atm-conn table for axsm-xg conns

Symptom:

ok connection shown as failed

Conditions:

upper level alarm is present on one end point in atm_connection table for axsm-xg

Workaround:

resync

CSCeb68663

Headline:

SSM doesn't have primary CWM as host after core is started

Symptom:

CWM host name is not updated on SSM after the core was started on SSM.

Conditions:

CWM Gateway switchover happened on CWM machines during the time when SSM core was down.

Workaround:

Update the host name manually using the command updatescminfo <cwm-host-name>

CSCeb69457

Headline:

SCM GUI grays out when tried to click on a SSC/Ctrlr in monitoring view

Symptom:

SCM GUI grays out when tried to click on a SSC/Ctrlr in monitoring view. The GUI shows up after a few minutes (5 to 15 mins).

Conditions:

When LAN cable is pulled out in the other SSC. When one of the SSC LAN connection is pulled and the user clicks on the SCM GUI to perform operations on the other SSCs.

Workaround:

The workaround is to either wait for the GUI to display (5 to 15 mins)

or

Plug the LAN cable back into the SSC that was plugged out.

CSCeb70993

Headline:

linktopoc core dump

Symptom:

linktopoc core dump

Conditions:

This may happen if the network being managed contains 3810/3600 routers connected to BPX/IGX nodes using LMI protocol and SNMP times out with the node(s).

Workaround:

None

CSCeb71268

Headline:

ooemc core dump after resetcd

Symptom:

ooemc core dump

Conditions:

When XM_60 card is removed and inserted back with in 5 minute but card becomes active after 5 minutes of removal.

Workaround:

None

CSCeb73034

Headline:

failed to update status in cesm_connection table for line fail traps

Symptom:

When line failure trap received on CESM card, all the conns still in active state from CWM GUI.

Conditions:

On MGX1 node, and CESM card. When line status changed either from no alarm to alarm, or from alarm to no alarm.

Workaround:

None.

CSCeb74413

Headline:

Multiple webserver core dumps

Symptom:

Multiple webserver core dumps

Conditions:

unknown

Workaround:

unknown

CSCeb75307

Headline:

scm/ssm versions in GUI help and ~svplus/etc are not updated

Symptom:

ssm.version and date files not updated and SCM GUI help brings up CWM version

Conditions:

Running SCM 12.0.00-P1 version.

Workaround:

N/A.

CSCeb75495

Headline:

Connections display as ok when card is removed.

Symptom:

Configuration is not being removed from DB when card is pulled out

Conditions:

Card is removed and switchcc or resetsys was done more than once.

Workaround:

None.

CSCeb76329

Headline:

Some MGX8850R2 nodes are in mode -1 for a long time after starting core

Symptom:

Some MGX8850R2 nodes remain in mode -1

Conditions:

This defect occurs when several frequent SNMP timeouts delay the discovery process in a large network (~30 MGX 8850 routing nodes).

Workaround:

None.

CSCeb77442

Headline:

remote %util from AR segment not set correctly

Symptom:

AR segment %util is not set correctly

Conditions:

Problem seen in user_connection table perc_util after going to 12.0.00-P1. This problem was only seen once and resolved itself after a day.

Workaround:

Unknown.

Further Problem Description:

Coldstart could be used to recover if waiting is unacceptable. Warmstart will have no effect.

CSCeb77518

Headline:

emd, emc & ooemc processes did not spawn for 30mins after starting core

Symptom:

emd, emc & ooemc processes did not spawn for 30 mins. after starting core

Condition:

start CWM core

Workaround:

Unknown.

CSCeb77950

Headline:

2 segment ATM-ATM hybrid connection in ERROR state

Symptom:

2 segment ATM-ATM hybrid connection in "ERROR" state

Conditions:

Immediately after adding connection

Workaround:

Unknown.

CSCeb79573

Headline:

Conn -trace is failing from CESM endpoints to other MGX endpoints

Symptom:

Connection Trace is failing for CESM: MGX 8950 node to other endpoints

Condition:

When the CESM ports are structured ports and there is more than 1 structured port on a line, the Connection Trace will not succeed.

Workaround:

None.

CSCeb80267

Headline:

EMC re initializes after port status trap with line=0

Symptom:

EMC re initializes intermittently

Conditions:

When portstatus traps received from MGX 8220 with line number=0

Workaround:

EMC is respawned by watchdog on CWM

CSCeb80899

Headline:

Parser puts incorrect values for 64-bit counters in some cases.

Symptom:

Stat counter values are incorrect for non-zero 64-bit counter values when reading using the statsreader tool or in the database

Conditions:

This is for 64-bit counters (AXSM-XG) and if the counter value exceeds 4 bytes (i.e.) more than half.

Workaround:

None.

CSCeb81526

Headline:

ooemc coredump when card removed/inserted multiple times

Symptom:

ooemc core dump

Conditions:

When multiple resetcd commands are done on card and it takes more than 5 minutes for the card to become active

Workaround:

None

CSCeb81600

Headline:

Connections deleted on one CWM is shown as incomplete in another CWM

Symptom:

Connections deleted on one CWM is shown as incomplete in another CWM.

Condition:

Deleted 524 connections on AXSM-XG-OC48 card in MGX8950 node through proxy

Workaround:

Unknown.

CSCeb85322

Headline:

process.conf is incorrect on SSC machine

Symptom:

1. If you have SCMGateway setup between 2 SSM machines (SSM1 as P, SSM2 as S), and you have at least 1 SSC machine connected switchover happened between the SSM machines (so now SSM1 is S and SSM2 is P), then forwarding of files does not happen to the new primary (SSM2) but still to the old primary(SSM1)

2. If you have SCMGateway setup between 2 SSM machines (SSM1 as Primary, SSM2 as Secondary), and you are using at least 1 SSC machine started collection with SSM1 as Primary Collector and SSC machine (or machines) as Secondary Collector (and Tertiary Collector), when switchover happened between the SSM machines (so now SSM1 is Secondary and SSM2 is Primary) then you could end up with duplicate collection

Conditions:

Please see the 2 examples in the Symptom description above.

Workaround:

Stop core on the SSC machines and replace the process.conf with the following

snmpcomm    on      off .      snmpcomm -s
cwmftpd     on      on  .      cwmftpd
scmcollsvr  on      on  .      scmcollsvr -s

Further Problem Description:

This is because the process.conf file on the SSC machine is not correct in the patch.

CSCin50334

Headline:

NWBrowser: Didn't get updated with newly added AUSM line/port on 8250.

Symptom:

NWBrowser doesn't show newly added AUSM line and port on 8250.

Conditions:

Added through CLI -> Did Node Resync --> Database got updated properly.

Workaround:

Unknown.

CSCin51142

Headline:

PCR value in CM GUI not ok for AXSM-XG-OC192 SPVC conns with high PCR

Symptom:

PCR value is incorrect for AXSM-XG OC192 SPVC connections with high PCR value.

Condition:

Add SPVC connection between AXSM-XG OC192 ports with 8 digit PCR value, the value in the database as well as what is displayed by the Connection Mgmt. GUI is incorrect.

Workaround:

Unknown.


Anomalies Resolved in CWM 12.0.00 Software

All anomalies resolved in CWM 11 and CWM 10 as of May 2, 2003, that apply to CWM 12.0.00 are included in CWM 12.0.00. Table 20 lists externally found anomalies from CWM  11 and CWM 10 as of May 2, 2003, that were only resolved in CWM 12.0.00 software.

Table 20 Anomalies Resolved in 12.0.00 

Bug ID
Headline:

CSCdx31087

SCT VC and CosB show wrong vals

CSCdx86816

Stata objectID:3/10:type 11,7&6 not being collected.

CSCdy19807

Wrong alarm on collapsed trunks

CSCdy26355

VSI-SIG parameters mismatch SCT GUI and CLI

CSCdy33589

CLR values displayed for PXM1E does not match with switch default values

CSCdy59622

.rhosts file overwritten during upgrade process

CSCdy62201

webServer did not start on upgraded m/c

CSCdy71243

MGX45 nodes failed to resynch because of snmp timeout (emulator related)

CSCdy82218

SNMP Module: Nodes failed to resync

CSCdy83851

DiagServer coredumped on a CWM machine

CSCdy84495

Topology shows trunk as clear after doing down & up lmi/ilmi on downed port

CSCdy84607

few AutoRoute trunks are not shown in Network Browser

CSCdy85868

CWM installation hangs at CV install if cronjob leaves a /tmp/crout* file

CSCdy87250

BPX node discovered as foreign node and got deleted from database

CSCdz01188

On sunrise install, install does not complete (i

CSCdz04403

Some CiscoView subdirectories are world-writable

CSCdz14857

CWM bug in install script

CSCdz19026

SCT manager Cosb tab screen not clearing setting after changes

CSCdz24906

Gui does not refresh when trunks is deleted

CSCdz68842

CM GUI - usability requirements from customers

CSCdz77588

BXM-T3 card type 250,251 BXME not recognized by SCM

CSCdz84213

trapd logs enhancements for debugging

CSCea16325

EMD deadlock MGX 8850 and 8220 will not sync

CSCea49075

PortProxy error misleading

CSCea49140

corba exceptions after install, start core

CSCea57681

Wandest client doesnt work in ksh environment

CSCea63117

ausm_port missing from DB, proxy query fails

CSCea64393

Overhead factor not applied for PXM1E AXSM-E to FRSM VBR conn

CSCea66013

Unable to add connections where VISM is the remote end. GUI and SA

CSCea68557

Corba ping_server utility on wandest client box

CSCea69561

Wandest install error msg is not proper

CSCea69616

Wandest encrypted pwd generation during install is set to default

CSCea72116

SNMP Get on cwmPrefRouteNECount returns incorrect value

CSCea76611

ooemc did not resync with RPM after missed trap

CSCea80554

swap space problem on machine, creates process reinitialization

CSCin36910

SES 1.1(79.102) returns NO SUCH NAME for mib obj cwaChanOamSegEpEnable


Anomaly Status Change from Previous Releases

The following table lists the anomalies that changed status as a result of the CWM 12.0.00, Patch 1.1 release.

Table 21 Anomaly Status Change from Previous Releases 

Bug ID
Description

CSCea46440

Symptom:

Virtual link is displayed twice: as virtual and physical

Conditions:

This is a timing issue. This might happen when you have virtual trunk between two PNNI nodes and you have persistent topology enabled.

Workaround:

Cold Start CWM

Status Change:

This anomaly has been closed out as being unreproducible.


Anomalies Resolved in WANDEST Server 2.4, Patch 3

There are no anomalies resolved in WANDEST Server 2.4, Patch 3

Anomalies Resolved in WANDEST Client 2.4, Patch 3

There are no anomalies resolved in WANDEST Client 2.4, Patch 3

Related Documentation

The following technical documents comprise the CWM 12 documentation set:

Cisco WAN Manager Installation for Solaris 8, OL-3837-01

Cisco WAN Manager User's Guide, OL-3838-01

Cisco WAN Manager SNMP Service Agent, OL-3840-01

Cisco WAN Manager Database Interface, OL-3839-01

Cisco WANDEST Installation and Reference, Release 2.4, OL-4122-01

Release Notes for Cisco WAN Manager for Solaris 8, Release 12.0.00, OL-3188-01

PDF copies of the first four items in the CWM 12 documentation set are provided on the third CWM 12 CD along with a copy of Adobe Acrobat and Netscape Communicator 4.76 for use in reading the files.

Use the included gzip utility to decompress the .gz files. The command is gzip -d.

The Cisco WANDEST Installation and Reference, Release 2.4 and these release notes are not available on the third CWM 12 CD. They are available on-line at the following URL:

http://www.cisco.com/univercd/cc/td/doc/product/wanbu/svplus/12/index.htm

Obtaining Documentation

Cisco documentation and additional literature are available on Cisco.com. Cisco also provides several ways to obtain technical assistance and other technical resources. These sections explain how to obtain technical information from Cisco Systems.

Cisco.com

You can access the most current Cisco documentation at this URL:

http://www.cisco.com/techsupport

You can access the Cisco website at this URL:

http://www.cisco.com

You can access international Cisco websites at this URL:

http://www.cisco.com/public/countries_languages.shtml

Product Documentation DVD

The Product Documentation DVD is a comprehensive library of technical product documentation on a portable medium. The DVD enables you to access multiple versions of installation, configuration, and command guides for Cisco hardware and software products. With the DVD, you have access to the same HTML documentation that is found on the Cisco website without being connected to the Internet. Certain products also have PDF versions of the documentation available.

The Product Documentation DVD is available as a single unit or as a subscription. Registered Cisco.com users (Cisco direct customers) can order a Product Documentation DVD (product number DOC-DOCDVD= or DOC-DOCDVD=SUB) from Cisco Marketplace at this URL:

http://www.cisco.com/go/marketplace/

Ordering Documentation

Registered Cisco.com users may order Cisco documentation at the Product Documentation Store in the Cisco Marketplace at this URL:

http://www.cisco.com/go/marketplace/

Nonregistered Cisco.com users can order technical documentation from 8:00 a.m. to 5:00 p.m. (0800 to 1700) PDT by calling 1 866 463-3487 in the United States and Canada, or elsewhere by calling 011 408 519-5055. You can also order documentation by e-mail at tech-doc-store-mkpl@external.cisco.com or by fax at 1 408 519-5001 in the United States and Canada, or elsewhere at 011 408 519-5001.

Documentation Feedback

You can rate and provide feedback about Cisco technical documents by completing the online feedback form that appears with the technical documents on Cisco.com.

You can submit comments about Cisco documentation by using the response card (if present) behind the front cover of your document or by writing to the following address:

Cisco Systems
Attn: Customer Document Ordering
170 West Tasman Drive
San Jose, CA 95134-9883

We appreciate your comments.

Cisco Product Security Overview

Cisco provides a free online Security Vulnerability Policy portal at this URL:

http://www.cisco.com/en/US/products/products_security_vulnerability_policy.html

From this site, you will find information about how to:

Report security vulnerabilities in Cisco products.

Obtain assistance with security incidents that involve Cisco products.

Register to receive security information from Cisco.

A current list of security advisories, security notices, and security responses for Cisco products is available at this URL:

http://www.cisco.com/go/psirt

To see security advisories, security notices, and security responses as they are updated in real time, you can subscribe to the Product Security Incident Response Team Really Simple Syndication (PSIRT RSS) feed. Information about how to subscribe to the PSIRT RSS feed is found at this URL:

http://www.cisco.com/en/US/products/products_psirt_rss_feed.html

Reporting Security Problems in Cisco Products

Cisco is committed to delivering secure products. We test our products internally before we release them, and we strive to correct all vulnerabilities quickly. If you think that you have identified a vulnerability in a Cisco product, contact PSIRT:

For Emergencies only — security-alert@cisco.com

An emergency is either a condition in which a system is under active attack or a condition for which a severe and urgent security vulnerability should be reported. All other conditions are considered nonemergencies.

For Nonemergencies — psirt@cisco.com

In an emergency, you can also reach PSIRT by telephone:

1 877 228-7302

1 408 525-6532


Tip We encourage you to use Pretty Good Privacy (PGP) or a compatible product (for example, GnuPG) to encrypt any sensitive information that you send to Cisco. PSIRT can work with information that has been encrypted with PGP versions 2.x through 9.x.

Never use a revoked or an expired encryption key. The correct public key to use in your correspondence with PSIRT is the one linked in the Contact Summary section of the Security Vulnerability Policy page at this URL:

http://www.cisco.com/en/US/products/products_security_vulnerability_policy.html

The link on this page has the current PGP key ID in use.

If you do not have or use PGP, contact PSIRT at the aforementioned e-mail addresses or phone numbers before sending any sensitive material to find other means of encrypting the data.


Obtaining Technical Assistance

Cisco Technical Support provides 24-hour-a-day award-winning technical assistance. The Cisco Technical Support & Documentation website on Cisco.com features extensive online support resources. In addition, if you have a valid Cisco service contract, Cisco Technical Assistance Center (TAC) engineers provide telephone support. If you do not have a valid Cisco service contract, contact your reseller.

Cisco Technical Support & Documentation Website

The Cisco Technical Support & Documentation website provides online documents and tools for troubleshooting and resolving technical issues with Cisco products and technologies. The website is available 24 hours a day, at this URL:

http://www.cisco.com/techsupport

Access to all tools on the Cisco Technical Support & Documentation website requires a Cisco.com user ID and password. If you have a valid service contract but do not have a user ID or password, you can register at this URL:

http://tools.cisco.com/RPF/register/register.do


Note Use the Cisco Product Identification (CPI) tool to locate your product serial number before submitting a web or phone request for service. You can access the CPI tool from the Cisco Technical Support & Documentation website by clicking the Tools & Resources link under Documentation & Tools. Choose Cisco Product Identification Tool from the Alphabetical Index drop-down list, or click the Cisco Product Identification Tool link under Alerts & RMAs. The CPI tool offers three search options: by product ID or model name; by tree view; or for certain products, by copying and pasting show command output. Search results show an illustration of your product with the serial number label location highlighted. Locate the serial number label on your product and record the information before placing a service call.


Submitting a Service Request

Using the online TAC Service Request Tool is the fastest way to open S3 and S4 service requests. (S3 and S4 service requests are those in which your network is minimally impaired or for which you require product information.) After you describe your situation, the TAC Service Request Tool provides recommended solutions. If your issue is not resolved using the recommended resources, your service request is assigned to a Cisco engineer. The TAC Service Request Tool is located at this URL:

http://www.cisco.com/techsupport/servicerequest

For S1 or S2 service requests, or if you do not have Internet access, contact the Cisco TAC by telephone. (S1 or S2 service requests are those in which your production network is down or severely degraded.) Cisco engineers are assigned immediately to S1 and S2 service requests to help keep your business operations running smoothly.

To open a service request by telephone, use one of the following numbers:

Asia-Pacific: +61 2 8446 7411 (Australia: 1 800 805 227)
EMEA: +32 2 704 55 55
USA: 1 800 553-2447

For a complete list of Cisco TAC contacts, go to this URL:

http://www.cisco.com/techsupport/contacts

Definitions of Service Request Severity

To ensure that all service requests are reported in a standard format, Cisco has established these severity definitions:

Severity 1 (S1)—An existing network is down, or there is a critical impact to your business operations. You and Cisco will commit all necessary resources around the clock to resolve the situation.

Severity 2 (S2)—Operation of an existing network is severely degraded, or significant aspects of your business operations are negatively affected by inadequate performance of Cisco products. You and Cisco will commit full-time resources during normal business hours to resolve the situation.

Severity 3 (S3)—Operational performance of the network is impaired, while most business operations remain functional. You and Cisco will commit resources during normal business hours to restore service to satisfactory levels.

Severity 4 (S4)—You require information or assistance with Cisco product capabilities, installation, or configuration. There is little or no effect on your business operations.

Obtaining Additional Publications and Information

Information about Cisco products, technologies, and network solutions is available from various online and printed sources.

The Cisco Product Quick Reference Guide is a handy, compact reference tool that includes brief product overviews, key features, sample part numbers, and abbreviated technical specifications for many Cisco products that are sold through channel partners. It is updated twice a year and includes the latest Cisco offerings. To order and find out more about the Cisco Product Quick Reference Guide, go to this URL:

http://www.cisco.com/go/guide

Cisco Marketplace provides a variety of Cisco books, reference guides, documentation, and logo merchandise. Visit Cisco Marketplace, the company store, at this URL:

http://www.cisco.com/go/marketplace/

Cisco Press publishes a wide range of general networking, training and certification titles. Both new and experienced users will benefit from these publications. For current Cisco Press titles and other information, go to Cisco Press at this URL:

http://www.ciscopress.com

Packet magazine is the Cisco Systems technical user magazine for maximizing Internet and networking investments. Each quarter, Packet delivers coverage of the latest industry trends, technology breakthroughs, and Cisco products and solutions, as well as network deployment and troubleshooting tips, configuration examples, customer case studies, certification and training information, and links to scores of in-depth online resources. You can access Packet magazine at this URL:

http://www.cisco.com/packet

iQ Magazine is the quarterly publication from Cisco Systems designed to help growing companies learn how they can use technology to increase revenue, streamline their business, and expand services. The publication identifies the challenges facing these companies and the technologies to help solve them, using real-world case studies and business strategies to help readers make sound technology investment decisions. You can access iQ Magazine at this URL:

http://www.cisco.com/go/iqmagazine

or view the digital edition at this URL:

http://ciscoiq.texterity.com/ciscoiq/sample/

Internet Protocol Journal is a quarterly journal published by Cisco Systems for engineering professionals involved in designing, developing, and operating public and private internets and intranets. You can access the Internet Protocol Journal at this URL:

http://www.cisco.com/ipj

Networking products offered by Cisco Systems, as well as customer support services, can be obtained at this URL:

http://www.cisco.com/en/US/products/index.html

Networking Professionals Connection is an interactive website for networking professionals to share questions, suggestions, and information about networking products and technologies with Cisco experts and other networking professionals. Join a discussion at this URL:

http://www.cisco.com/discuss/networking

World-class networking training is available from Cisco. You can view current offerings at this URL:

http://www.cisco.com/en/US/learning/index.html