cc/td/doc/product/rtrmgmt/cwm/10_2
hometocprevnextglossaryfeedbacksearchhelp
PDF

Table of Contents

Release Notes for Cisco WAN Manager 10.3 for Solaris

Release Notes for Cisco WAN Manager 10.3 for Solaris

Cisco WAN Manager 10.3 for Solaris software supports the following Cisco products:

Contents

This document contains the following sections:

Release Numbering

The release numbering scheme for CWM Release 10 has been changed from the Release 9 standard three decimals (for example, 9.2.08) to two decimals (for example, 10.3 or 10.2). The first number represents the Major Release and the second number represents the Minor Release. For example, the current release is numbered as CWM 10.3 with 10 representing the Major Release and .3 representing the Minor Release. The next release will be numbered as 10.4, and so on.

System Requirements

Three types of machines are supported for WAN Manager 10.3 as standard platforms. They are low-end, mid-range, and high-end platforms. Table 1 describes the configuration for each platform.


Table 1: Sun Platform Requirements
Platform Type Machine Type Number of CPUs Size of RAM Hard Disk Drive Swap Space Desktops Supported Connections Supported

Low End

Sun Ultra 10 with SCSI controller

1

512 MB

One 9 GB

1 GB

Less than 5

Less than 5,000

Mid Range option 1

Sun Ultra Enterprise 2 Model 2300 or Ultra 60

2

1 GB

Two 9 GB drives

2 GB

5 - 10

5,000 - 50,000

Mid Range option 2

Sun Ultra Enterprise 2 Model 2300 or Ultra 60

2

2 GB

Two 9 GB drives

2 GB

10-20

50,000 - 100,000

High End

Sun Enterprise 4000 or Enterprise 450

at least 4

4 GB

Two 9 GB drives or disk array

4 GB

More than 20

More than 100,000

Note   The minimum CPU speed requirement for all platforms is 300 MHz. The newer versions of the Sun Ultra 10 have a 450 MHz processor. All platforms require a 24-bit graphics card.

The selection of a proper CWM platform depends on a number of factors, such as the number of CWM desktops, the number of managed connections, and the number of statistics collected and stored. Table 1 lists recommended CWM platforms based on the size of network.

The following are additional notes for CWM platform requirements:

Solaris Patch Requirements

After installing the Solaris 2.7 operating system, you must install the patch 1.1.8_10_patches_sparc_5.7.tar. You can get this patch from Sun Microsystems.

To install the patch, complete the following steps:

Step 1   Untar the patch tar file by entering the following command line: 

    tar -xvf 1.1.8_10_patches_sparc_5.7.tar

Four files are extracted, as listed below:

Step 2   Uncompress and execute tar -xvf for each file.

Four directories will be extracted.

Step 3   Login as root on the destination workstation, and execute the showrev -a command to check to see if these patches have been installed. If installed, the numbers will appear as listed above.

Step 4   If the patches are not installed, install them now by entering the following commands: 

    patchadd ./106980-05
patchadd ./107078-01
patchadd ./107607-01
patchadd ./107636-01

Step 5   All patches should install on the CWM workstation.

Step 6   Execute a showrev -a command to verify that the patches have been installed.

Step 7   Reboot the CWM workstation.

If You Experience Performance Problems

If you use CWM 10.3 on a low-end machine to manage mid-range or large-range networks, the following performance problems might be observed.

CWM Performance Degradation

CWM may take a long time to synchronize with the network. Connection Management and Equipment Management (using either CiscoView or the Equipment Manager GUI) may take long time to come up or perform any user-requested functions. You might not be able to invoke multiple desktops from CWM as certified by Cisco for low-end systems.

Loss of Database Synchronization

CWM may drop traps generated by the network which might put the CWM database out of sync with the network. This would result in the information about nodes, trunks, ports, and PVCs might not match with the status on the network.

CWM Software Packaging

The Service Agent package has been separated from the CWM 10.3 Server CD. The Service Agent package is now on a separate CD. Following is the list of CDs for the CWM 10.3 release:

Note   You must purchase HPOV 6.10 directly from Hewlett Packard.

HP OpenView Requirements

The CWM 10.3 release works with HP OpenView Release 6.10 for Solaris 2.7. See "Third Party Product Limitations Notes" for HP OpenView patches required by CWM.

The default color of the background map can make it difficult to see the color of the nodes and the trunks on the map.

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.10 is not bundled with CWM CDs. You must order HP OpenView separately.

INFORMIX Requirements

The CWM 10.3 release uses Informix 9.2 for database operations. The INFORMIX software is bundled with CWM software on the CWM Server/Client CD. The INFORMIX program is automatically installed during CWM installation.

WingZ Requirements

The Report Application contained in the CWM 10.3 release uses WingZ 2.51. For the Ad-Hoc Report Application to work properly, the WingZ DataLink program must be installed along with WingZ software. WingZ requires a license to install.

Supported Hardware

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

Existing Hardware

Table 2 lists the existing hardware supported in CWM 10.3.


Table 2: Supported Existing Hardware
Platform Series Front Card Back Card Software Version

IGX 8400

NPM

SCM

SWSW 9.1, 9.2, 9.3.00, 9.3.05, or 9.3.10

IGX 8400

NTM

BC-T1/E1/SR/Y1

SWSW 9.1, 9.2, 9.3.00, 9.3.05, or 9.3.10

IGX 8400

BTM

AIT-T3/E3/E2/HSS1/E1

SWSW 9.1, 9.2, 9.3.00, 9.3.05, or 9.3.10

IGX 8400

FRM

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

SWSW 9.1, 9.2, 9.3.00, 9.3.05, or 9.3.10

IGX 8400

FTM

FPC-V35/T1/E1/X.21

SWSW 9.1, 9.2, 9.3.00, 9.3.05, or 9.3.10

IGX 8400

HDM

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

SWSW 9.1, 9.2, 9.3.00, 9.3.05, or 9.3.10

IGX 8400

LDM

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

SWSW 9.1, 9.2, 9.3.00, 9.3.05, or 9.3.10

IGX 8400

CVM

BC-T1/E1/J1/Y1/SR

SWSW 9.1, 9.2, 9.3.00, 9.3.05, or 9.3.10

IGX 8400

UVM

UVI-2T1EC/2E1EC

SWSW 9.1, 9.2, 9.3.00, 9.3.05, or 9.3.10

IGX 8400

UFM-C

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

SWSW 9.1, 9.2, 9.3.00, 9.3.05, or 9.3.10

IGX 8400

UFM-U

UFI-V35/X21/HSI

SWSW 9.1, 9.2, 9.3.00, 9.3.05, or 9.3.10

IGX 8400

ARM

ARI

SWSW 9.1, 9.2, 9.3.00, 9.3.05, or 9.3.10

IGX 8400

UXM

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

SWSW 9.1, 9.2, 9.3.00, 9.3.05, or 9.3.10

BPX 8600

BCC

BCC-bc/3-bc

SWSW 9.1, 9.2, 9.3.00, 9.3.05, or 9.3.10

BPX 8600

ASM

LM-ASM

SWSW 9.1, 9.2, 9.3.00, 9.3.05, or 9.3.10

BPX 8600

BNI-T3

LM-3T3

SWSW 9.1, 9.2, 9.3.00, 9.3.05, or 9.3.10

BPX 8600

BNI-E3

LM-3E3

SWSW 9.1, 9.2, 9.3.00, 9.3.05, or 9.3.10

BPX 8600

BNI-155

LM-OC3-SMF/SMFLR/MMF

SWSW 9.1, 9.2, 9.3.00, 9.3.05, or 9.3.10

BPX 8600

ASI-1

LM-2T3/2E3

SWSW 9.1, 9.2, 9.3.00, 9.3.05, or 9.3.10

BPX 8600

ASI-155

LM-2OC3-SMF/SMFLR/MMF

SWSW 9.1, 9.2, 9.3.00, 9.3.05, or 9.3.10

BPX 8600

BXM-T3/E3

T3/E3-BC

SWSW 9.1, 9.2, 9.3.00, 9.3.05, or 9.3.10

BPX 8600

BXM-15 5

MMF/SMF/SMFLR-155

SWSW 9.1, 9.2, 9.3.00, 9.3.05, or 9.3.10

BPX 8600

BXM-622

MMF/SMF/SMFLR-622

SWSW 9.1, 9.2, 9.3.00, 9.3.05, or 9.3.10

MGX 8220

FRSM-4P

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

4.0.19, 4.1.08, 5.0.14

MGX 8220

CESM-4P

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

4.0.19, 4.1.08, 5.0.14

MGX 8220

AUSM-4P

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

4.0.19, 4.1.08, 5.0.14

MGX 8220

FRSM-8P

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

4.0.19, 4.1.08, 5.0.14

MGX 8220

AUSM-8P

RJ48-8E1/8T1

4.0.19, 4.1.08, 5.0.14

MGX 8220

CESM-8P

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

4.0.19, 4.1.08, 5.0.14

MGX 8220

IMATM-B

RJ48-T3T1/E3E1/E3T1/T3E1

4.0.19, 4.1.08, 5.0.14

MGX 8220

FRSM-HS1

HSI-4X21/3HSSI

4.0.19, 4.1.08, 5.0.14

MGX 8220

BNM-T3/E3

T3E3-B/D

4.0.19, 4.1.08, 5.0.14

MGX 8220

BNM-155

155-SMF

4.0.19, 4.1.08, 5.0.14

MGX 8220

SRM

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

4.0.19, 4.1.08, 5.0.14

MGX 8220

ASC

ASC-LM

4.0.19, 4.1.08, 5.0.14

MGX 8220

FRSM-VHS

HS2

4.0.19, 4.1.08, 5.0.14

MGX 8220, MGX 8230, MGX 8250, MGX 8850 R1

AUSM model B

8T1/E1

4.0.19, 4.1.08, 5.0.14

MGX 8230, MGX 8250, MGX 8850 R1

PXM1

T3/E3/OC3/OC12

1.1.24, 1.1.30

MGX 8230, MGX 8250, MGX 8850 R1

FRSM-VHS

HS2/T3/E3/CT3

1.1.24, 1.1.30

MGX 8230, MGX 8250, MGX 8850 R1

FRSM-8P

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

1.1.24, 1.1.30

MGX 8230, MGX 8250, MGX 8850 R1

CESM-8P

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

1.1.24, 1.1.30

MGX 8230, MGX 8250, MGX 8850 R1

CESM

T3/E3

1.1.24, 1.1.30

MGX 8230, MGX 8250, MGX 8850 R1

RPM

10mbps/100mbps

rpm-js-mz.120-5.XT1

MGX 8230, MGX 8250, MGX 8850 R1

SRM

LM-3T3

1.1.24, 1.1.30

New Hardware

Table 3 lists the new hardware supported in CWM 10.3.


Table 3: Supported New Hardware
Platform Series Front Card Back Card Software Version

BPX 8600

BXM-E

T3/E3

9.3.10

MGX 8850 Release 2

AXSM1

T3/E3

2.0.01, 2.0.02, 2.0.10

MGX 8850 Release 2

AXSM1

OC3

2.0.01, 2.0.02, 2.0.10

MGX 8850 Release 2

AXSM1

OC12

2.0.01, 2.0.02, 2.0.10

MGX 8850 Release 2

AXSM2

OC48

2.0.01, 2.0.02, 2.0.10

MGX 8850 Release 2

PXM45

N/A

2.0.01, 2.0.02, 2.0.10

SES PNNI Controller Release 1

SES-PXM-CNTL-4-155 (with 4 port OC3)

P/N 800-06454-01

PXM-UIA

Rev: 05

MMF-4-155

Rev: 09

1.0.00, 1.0.01, 1.0.02, 1.0.10

SES PNNI Controller Release 1

SES-PXM-CNTL-4-155 (with 4 port OC3)

P/N 800-06454-01

PXM-UIA

Rev: 05

SMFIR-4-155

Rev: 09

1.0.00, 1.0.01, 1.0.02, 1.0.10

SES PNNI Controller Release 1

SES-PXM-CNTL-2T3E3 (with 2 port T3E3)

P/N 800-06699-01

PXM-UIA

Rev: 05

BNC-2T3

Rev: 03

1.0.00, 1.0.01, 1.0.02, 1.0.10

SES PNNI Controller Release 1

SES-PXM-CNTL-2T3E3

(with 2 port T3E3)

P/N 800-06699-01

PXM-UIA

Rev: 05

BNC-2E3

Rev: 03

1.0.00, 1.0.01, 1.0.02, 1.0.10

CWM Software Compatibility

CWM 10.3 operates with BPX 8600 and IGX 8400 series systems running SWSW releases 9.3.10, 9.2, or 9.1. CWM 10.3 operates with MGX 8220 releases 4.0.19, 4.1.07, and 5.0.10 for all supported features. CWM 10.3 operates with MGX 8230 releases 1.0, 1.1.24, and 1.1.30, MGX 8250 releases 1.0, 1.1.24, and 1.1.30, and MGX 8850 releases 1.0, 1.1.24, and 1.1.30 for all supported features. CWM 10.3 operates with MGX 8850 releases 2.0, 2.0.01, 2.0.02, and 2.0.10 for all supported features. CWM 10.3 operates with SES releases 1.0, 1.0.01, 1.0.02, and 1.0.10 for all supported features. CWM 10.3 can operate in mixed networks with SWSW 9.1, SWSW 9.2, and SWSW 9.3.10.

WAN CiscoView Software Compatibility

WANCV 3.30 will operate with BPX/IGX releases 9.3.10, 9.2, and 9.1; releases of MGX 8220 4.0.19 or later, 4.1.02 or later, and 5.0.12 or later; all available releases of MGX 8850 Release 1.0 or later; MGX 8850 Release 2.0 or later, and SES 1.0.00 or later.

CiscoView 5.1

CiscoView Release 5.1 is required for WANCV Release 3.30.

HP OpenView

All event messages are now 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 WANCV 3.30 release works with HP OpenView Release 6.10 for Solaris 2.7.

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

New Features and Enhancements in CWM Release 10.3

This build has the following new features:

    1. Qbin Statistics

  In previous releases of the BPX and IGX, only statistics from Qbins 1-9 were collected on AutoRoute trunks. Starting with Release 9.3.10, the switch allows the collection of additional Qbin statistics. Following is a summary of all Qbin statistics collected by the BPX and IGX. Qbin statistics are Cells Served, Cells Discarded, and Cells Received.
  All other Qbins are unused and the switch does not provide statistics for them.
  Also starting in Release 9.3.10, the switch provides the collection of Qbin Cells Discarded statistics via SNMP for the above mentioned Qbins.

    2. ILMI 4.0 for IGXs

  This feature allows the ILMI 4.0 protocol to be run on the UXM card instead of on an NPM card. The feature can be enabled on a port or virtual trunk basis, but the UXM card requires that the new firmware is loaded to support the new feature.

    3. ILMI/ELMI Neighbor Discovery

  This feature enables the Cisco WAN Manager (CWM) to discover any ATM devices attached to the BXM or UXM ports on the BPX or IGX switches, provided that those neighbor ATM devices also support ILMI Neighbor Discovery. If the BXM or UXM card supports the ILMI Neighbor Discovery feature, the user only needs to configure ILMI and Protocol-By-Card on the port, then the relay of the neighbor's topology information to CWM is automatic. However, in order to authorize the switch to give out its own topology information to the neighboring ATM devices, the user has to use the cnfport command to enable the Neighbor Discovery Enable/Disable parameter. Use the new command dspnebdisc to display neighboring ATM devices' topology information.

    4. ELMI for UFMs

  The ELMI protocol enhancements for the UFM serves the same purpose as the ILMI enhancements for the UXM, and shares similar mechanisms to reach the neighbor discovery purpose.

    5. VSI/MPLS for UXMs

  This feature provides IGX switches with the capabilities for setting up connections based on the PNNI and MPLS protocols, which allows the user to expand their existing network. VSI is a resource management scheme that allocates IGX resources, needed for setting up connections, such as system bandwidth and channel space, to a number of external connection-management entities which manage calls/connections with PNNI, MPLS, or other protocols.
  This feature supports:

    6. Virtual Port

  This feature supports a combination of Virtual Port traffic shaping and connection traffic shaping. The Virtual Port feature allows one or more Virtual Ports per Physical Port interface. Connection- level traffic shaping within Virtual Ports is supported. Although Virtual Ports can connect directly to an ATM edge device or a CPE device, they will generally be used to connect indirectly through an ATM network, because direct connections to an ATM edge device or CPE equipment can be done with currently available Physical Ports. A maximum of 31 Virtual Ports is available per BXM card on the BPX. Each Virtual Port will support all AutoRoute traffic types that are currently supported by Physical Ports. (This is a chargeable feature on the BPX.) CWM 10.3 supports virtual port feature configuration and monitoring.

    7. Support for Integration with Release 3.0 of Cisco Info Center

Cisco Info Center is a service-level monitoring and diagnostics tool that provides network fault and performance monitoring, trouble isolation, and real-time service-level management for large networks. Info Center is designed to help operators focus on important network events, offering a combination of alarm reduction rules, filtering, customizable alarm viewing, and partitioning. Info Center provides a highly configurable client/server application that can consolidate, de-duplicate, filter, and correlate fault information from a wide range of management platforms and technologies.

New Features and Enhancements in WANCV Release 3.30

CiscoView MSSBU device packages (WANCV) are upgraded to release 3.30 to support CiscoView 5.1, IGX/BPX Release 9.3.10, BPX SES, MGX 8220 Release 5.0 enhancements, the MGX 8230, the MGX 8250, and the MGX 8850 Release 1 and Release 2 products. The look and feel of CiscoView 5.1 is slightly different from CiscoView 4.2, but most dialogs will be familiar to experienced CiscoView users. The Front or Rear view selection is done by selecting the outer part of the device with the right mouse button.

Features Not Supported in WANCV Release 3.30

The following features are not supported in WANCV 3.30:

Features Not Supported and Known Feature Limitations in 10.3

The following features are not supported in CWM 10.3:

Supported Connections

This section lists the connections CWM 10.3 supports.

Switch Compatibility

CWM 10.3 can manage connections on the following types of WAN switches or concentrators:

CWM 10.3 supports PVC and SPVC connections. SPVC connections are supported only on the MGX 8850 Release 2 switches and on BPX 8600 switches which are controlled by SES nodes.

Supported Cards

CWM 10.3 supports the following card types for various connections.

Frame Relay

The following Frame Relay (FR) service modules are supported:

CWM 10.3 supports the following FRSM-VHS cards on the MGX 8220 and MGX 8850:

FR and FRSM-VHS cards support the following types of ports:

ATM Service Modules for PVC Connections

CWM 10.3 supports the following types of Service Modules for ATM (Unicast) connections:

Circuit Emulation (CE) Service Modules

CWM 10.3 supports the following types of Service Modules for Circuit Emulation

Voice Service Modules

CWM 10.3 supports the following types of Voice Service Modules:

Note   IPX has been declared `End Of Life' in SWSW 9.1.

Data Service Modules

CWM 10.3 supports the following types of data Service Modules:

Note   IPX has been declared `End Of Life' in SWSW 9.1.

Real Time VBR Feature

Network Support

This feature is supported on network trunks running SWSW 9.2.y or later on the trunk cards BXM, BNI, UXM (only).

ATM Service Module Support

This feature is supported on the BXM, UXM, ASI service modules running SWSW 9.2.2.x. Currently, CWM 9.2 does not support rt-vbr connections involving PXM cards (however PXM-FR nrt-vbr connections are supported).

Frame Relay Service Module Support

This feature is supported only on FRQOS service modules.

PVC Connections Supported by CWM 10.3

Table 4 lists the connection types supported by CWM 10.3.


Table 4: PVC Connections Supported by CWM 10.3
Connection CWM Service Local Endpoint Card Type Remote Endpoint Card Type Comments or Restrictions

FR-FR

none

FR

FR

Choice of FR port types;
choice of ForeSight features;
no QOS support

FR-FR

none

FRQOS

FR,
FRQOS

Choice of FR port types;
ForeSight enabled for QOS types ubr and abr;
Following QOS specified by `ChanServType' attribute on FRSM-VHS SM:

hi_priority, ubr, nrt-vbr, rt-vbr, abr

ATM-FR

nrt-vbr3,abr.fs

ATM

FR

Choice of FR port types;
no QOS support on FR endpoint;
abr.fs not supported with ATM PXM service module

ATM-FR

cbr1,

ubr(1,2),

nrt-vbr(2,3),

abr.fs

ubr(1,2)

ATM

FRQOS

Choice of FR port types;
QOS supported on FR endpoint

ATM-FR

rt-vbr(2,3)

ATM

FRQOS

Choice of FR port types;
QOS supported on FR endpoint;
ForeSight for abr.fs only;
abr.fs not supported with ATM PXM service module

ATM-FR

nrt-vbr3

RPM

FR

Choice of FR port types;
no QOS support on FR endpoint

ATM-FR

nrt-vbr3

RPM

FRQOS

Choice of FR port types;
QOS supported on FR endpoint

ATM-ATM

cbr1,
nrt-vbr(1,2,3),
ubr(1,2),
abr.1,abr.fs

ATM

ATM

No Foresight (except for abr.fs);
rt-vbr available only if both network and service modules support `rt' feature;
no ForeSight supported with cbr and with PXM cards

ATM-ATM

rt-vbr(1,2,3)

ATM

ATM

No Foresight;
real time feature should be supported by the network and the ATM service modules

ATM-ATM

atfst. atfxt, atfttxt

ATM (BXM)

ATM (BXM)

ForeSight supported;
both endpoints should be BXM/BXM-E cards

ATM-ATM

cbr1,
nrt-vbr(1,2,3),
ubr(1,2),
abr.1,abr.fs

ATM-Multicast

ATM-Multicast

No Foresight (except for abr.fs);
multicast connection;
local and remote port combinations: root-root, root-leaf

ATM-ATM

nrt-vbr3

ATM/RPM

ATM/RPM

No Foresight;
one or both endpoint router service modules

CE-CE

cbr

CE

CE

Structured/unstructured;

both endpoints must be either structured or unstructured with matching bandwidth and interface type.

ATM-CE

cbr

CE structured or unstructured;
ATM endpoint bandwidth should be equal to or greater than the CE endpoint bandwidth

Data-Data

none

Data service module

Data service module

Connection routing path cannot include BPX

Voice-Voice

none

Voice service module

Voice service module

Connection routing path cannot include BPX

Table 5 lists the cards that belong to the various endpoint card types. No abr - fs to abr connections supported.


Table 5: Card Types
Card Type Cards
  FR
  FRSM(4T1,4E1,8T1,8E1, HS1b.V35),
FRM,
UFM,
FRP
  FRQOS
  FRSM(2CT3,2E3,2T3,HS2) [FRSM 8T1/8E1 with Release 10.0.20]

ATM

AUSM(4T1,4E1,8T1,8E1),
AUSMB(8T1,8E1),

PXM
ASI, ASI-155,
BXM,
BXM-E,
UXM
(only BXM, BXM-E, AUSM 10.0.11 and UXM support rt-vbr)

Note   CWM will not support 10.0.11 and onward.

ATM-Multicast

BME

CE

CESM(4T1,4E1,8T1,8E1,T3,E3)

RPM

RPM

Voice service module

CVM,
UVM,
CDP

Data service module

CVM,
UVM,
HDM,
LDM,
SDP,
LDP

Note   In this release, Multicast connection is not supported from the Connection Manager GUI.

SPVC Connections Supported by CWM 10.3

Table 6 lists the connection types supported by CWM 10.3.


Table 6: SPVC Connections Supported by CWM 10.3
Connection CWM Service Local Endpoint Card Type Remote Endpoint Card Type Comments or Restrictions

ATM-ATM

cbr1,
nrt-vbr(1,2,3),
ubr(1,2),
abr.1

ATM (AXSM)

ATM (AXSM)

No Foresight;
VSVD always disabled for abr.1

ATM-ATM

cbr1,
nrt-vbr(1,2,3),
ubr(1,2),
abr.1

ATM (BXM)

ATM (BXM)

No Foresight;
no CC enable;
VSVD can be enabled or disabled for abr.1

Table 7 lists the cards that belong to the various endpoint card types.


Table 7: Card Types
Card Type Cards

ATM (AXSM)

AXSM in MGX 8850 Release 2

ATM (BXM)

BXM in BPX

Limitations

CWM can manage up to 40 different disjoint networks running switch software releases 9.1 and 9.2 and 9.3.0, MGX 8220 releases 4.0.19, or later, 4.1.07 or later, 5.0.11 or later, MGX 8230 Release 1 releases 1.1.23 or later, MGX 8250 Release 1 releases 1.1.23 or later, MGX 8850 Release 1 releases 1.1.23 or later, MGX 8850 Release 2, provided all the networks elements have unique network IP addresses and unique names across all the networks managed by CWM. Different networks may run different versions of switch software as long as the releases are those listed above. Disjoint networks containing up to 15 nodes in each network have been tested.

MGX 8850 Release 2 to MGX 8850 Release 2 Communication

This section describes limitations with switch to switch communication via IP Connectivity. It is true that in most cases, where every router in the IP Connectivity system can reach every MGX 8850 Release 2 switch, each switch can reach every other switch using one of the routers as the "go-between." This is not always the case, though, when some of the routers are configured to communicate with only a subset of the MGX 8850 Release 2 switches. This would prevent switch to switch communication.

Also, no functionality exists for a MGX 8850 Release 2 switch to learn the IP addresses of all other MGX 8850 Release 2 switches. Proprietary extensions to PNNI could solve this problem, but these extensions are not proposed.

Limited Number of Routers

Each router AESA that is learned must be maintained in a database and sent to the standby PXM. Each AESA is twenty (20) bytes of information. This limits the number of AESA addresses to ten (10). If this is not a viable number it can be increased or decreased.

IP connectivity for BPX-SES is the same as in MGX 8220, MGX 8230 Release 1, MGX 8250 Release 1, and MGX 8850 Release 1.

Ad-Hoc Reports

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

Topology

It may occasionally take two to three minutes to display new nodes after the addition of virtual trunks. This is due to the time required to setup link0 and link1 subscriptions.

Software or Firmware Image Download

Always use the CWM ImageDownload program to do a SW/FW download. CWM does not make any assumptions on the filename; it requires you to tell the software the filename and the path to download. This helps avoid any inconsistencies resulting from file naming assumptions made by the getfwrev and loadfwrev commands. If the CWM ImageDownload program does not work, there is a problem with the file transfer or the image.

SNMP Traps

All SNMP traps now match with the MIB. In earlier releases, some of the trap enterprise Object Information Descriptors (OID) had different enterprise OIDs. Due to this correction, old traps with incorrect enterprise OIDs from trapd.log file will not be shown in the Event Browser.

After installation, you must run /usr/users/svplus/bin/clearOVDb.s before running ovw because the nodes under the root directory will still be there and may result in CWM database corruption.

The /etc/opt/OV/share/conf/C/trap.conf file will be removed and replaced by the default trap.conf file and will then be merged with the StrataTrapd.conf file. If you have modified the trapd.conf file, those changes will be lost. To save these changes, save the trapd.conf file (perhaps to /tmp), and merge it back.

CWM 10.3 Notes and Cautions

Due to the nature of asynchronous behavior of ILOG client and server interaction, it is likely to have CWM client requests made 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>. However, if the 
ILOG timeout situation persists for more than five minutes and, the CWM station is not 
functioning normally, then a service call should be made.

CWM Upgrade

Note   CWM software can be upgraded from 9.1.10, 9.2.09, 10.1 or 10.2 to 10.3.

When Informix is installed on a disk array (typically the device name is /dev/vx/rdsk/rootdg/vol03) the ownership of the device and the group ownership of the device should be set to informix. The mode of the device should be 770. Otherwise, after rebooting the machine, the "Shared memory is not initialized" error message appears on the console.

The upgrade script has changed in Cisco WAN Manager Release 10.3.

Existing CWM configuration files are unconditionally overwritten with default values during the CWM 10.3 installation process. If you are installing CWM 10.3 over an earlier release of CWM 10.2, 10.1 or 9.2.0x, save these files manually before beginning the installation process.

The following files are affected. These files must be backed up along with the CWM INFORMIX database:

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

If the CWM system has two hard disk drives and you plan to use auto install and intend to partition the disk during auto install, you have two choices for installing the WingZ application:

    1. Install WingZ in /opt/Wingz before installing CWM and then execute IntegrateWingz.

    2. Install WingZ in /usr/users/Wingz after installing CWM and then execute IntegrateWingz.

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

    1. Install WingZ either in /usr/users/Wingz or /opt/Wingz before installing CWM.

    2. Install WingZ either in /usr/users/Wingz or /opt/Wingz after installing CWM and then execute IntegrateWingz.

You install WingZ software from the WingZ tape or CD.

Note   WingZ version 2.51 should be installed for CWM release 10.3. After installing, contact WingZ for a runtime license and blend it with CWM 10.3. Failing to do so results in the "There is a problem with the registration information for this machine. Contact your system administrator" error message when you click on the CWM Report icon.
Note   If the upgrade does not work for CWM 10.3, you must:
Login as root, cd to /usr/users and issue the following commands.
# rm -r svplus
# rm -r inform*
# rm -r corba

Then do an initial CWM 10.3 install.

Installation Notes

This section contains information about late changes to the installation process. This information is also found in the CWM 10.3 Installation Guide for Solaris (78-10308-03).

Note   Changes have been made to the CWM 10.3 Installation Guide for Solaris you received with your software.

Installing Solaris 2.7

When you install the Solaris 2.7 (Solaris 7) operating system software on the CWM workstation, choose to install Entire Distribution.

Disk Partitioning Requirements

Sufficient disk space and proper disk partitioning are essential to achieving the best performance from CWM and your network management workstation.

Note   The minimum disk space requirement for Release 10 of CWM is one 9-GB disk drive.

Partitioning One 9-GB Disk

This section describes how to partition a CWM workstation's single 9-GB disk drive. The following procedure ensures that all but the final partition will be at a set size.

Note   The actual total disk space for a 9-GB disk varies depending on the manufacturer of the disk. One 9-1 GB disk might have 9.05 GB of available space, while another might only have 8.9 GB of space available. Other disk drive flaws also limit disk capacity. Most disks will NOT have a full 9.1 GB, and the slice 2 (s2) total will vary.


Table 0-8: 
Slice

Partition

Space

Comments

 s0


 / 


 1500 MB


 Allocate this partition third


 s1


 swap


 1030 MB


 Allows for memory upgrade to 1 GB; allocate this partition second


 s2


 <overlap>


 8692 MB


 Total amount of space on the disk; do not attempt to modify


 s3


 /opt


 1000 MB


 allocate this partition fourth


 s4


 /var


 1167 MB


 allocate this partition fifth


 s5


 


 


 


 s6


 /usr/users


 2000 MB


 Must be 2000 MB; allocate this partition first


 s7


 


 1995 MB


 Raw partition; might be less that this amount; allocate this partition last
Partitioning a Single 9-GB Disk
Note   To check the running total of what disk space is remaining, just click on the any other partition to update the total free value. When there are 0 free and a rounding error of 0 or 1, click OK.

Partitioning Two 9-GB Disks

This section describes how to partition a CWM workstation that has two 9-GB disk drives. When you install Solaris, partition the first disk drive as shown in Table 0-9. Partition the second disk drive as shown in Table 0-10.


Table 0-9: 
Slice

Partition

Space

Comments

 s0


 / 


 1500 MB


 Allocate this partition third


 s1


 swap


 1030 MB


 Allows for memory upgrade to 1024 MB; allocate this partition second


 s2


 <overlap>


 8692 MB


 Total amount of space on the disk; do not attempt to modify


 s3


 /opt


 3000 MB


 Allocate fourth


 s4


 /var


 1162 MB


 Remainder of disk; allocate this partition last


 s5


 


 


 


 s6


 /usr/users


 2000 MB


 Must be 2500 MB; allocate this partition first


 s7
Partitioning the First 9-GB Disk
Note   The total space should equal the space shown in s2.

Table 0-10: 
Slice

Partition

Space

Comments

 s0


 swap


 1000 MB


 Allocate this first


 s1


 


 


 


 s2


 <overlap>


 8692 MB


 Total amount of space on the disk; do not attempt to modify


 s3


 /spare


 5697 MB


 Allocate this last, This partition can be used for customer use or can be used for multiple 2 GB Informix raw partitions.


 s4


 


 


 


 s5


 


 


 


 s6


 


 


 


 s7


 


 1995 MB


 Allocate this second
Partitioning the Second 9-GB Disk
Note   The total space should equal the space shown in s2.

Resolving Orbix Server Socket Port Conflicts

The five Orbix servers in CWM Release 10 use fixed socket ports because of a GUI reconnect limitation.

The fixed socket ports are:

 Name            Marker  Code    Comms   Port    Launch  PerClient?      OS-pid
 ------------------------------------------------------------------------------
 TopoServer      *       cdr     tcp     5558    manual  ---             5575
 CmServer        *       cdr     tcp     5555    manual  ---             5842
 GenericServer   *       cdr     tcp     5559    manual  ---             5500
 LogServer       *       cdr     tcp     5556    manual  ---             5456
 CWMGateway      *       cdr     tcp     5557    manual  ---             5451

If another program is already using those ports, those server will have problems starting up and the following error message will be displayed when the CWM server comes up:

TCP/IP socket error, address already in use

To resolve this issue choose one of the following two methods:

Shutting down non-CWM Programs

Step 1   Execute the following command at the Unix prompt:

netstat -a

The system will display which program is using which socket port.

Step 2   If there is a non-CWM program using any of socket ports 5555 through 5559, and you feel that you can run CWM without it, stop the program that is using the socket port that's conflicting with the CWM servers.

Step 3   Once the program using the server socket port required by Orbix have been shut down, restart CWM to let the Orbix server begin using the appropriate socket port.

Reassigning Socket Port Numbers

If the non-CWM program using any of socket ports 5555 through 5559 cannot be shut down, you can assign another socket port to the Orbix server (or servers) that have conflicts.

Step 1   Execute the following command at the Unix prompt:

> rmit <servername>

where servername is the name of the CWM server that is in conflict.

This command will remove the socket port assigned to servername.

Step 2   Next, execute the following command at the Unix prompt:

> putit -port <newport number> -persistent <servername>

where newport number is the appropriate socket number to match with servername (the CWM server that is in conflict).

Refer to this table for the appropriate socket port number:


Table 11: Orbix Fixed Socket Port Numbers
Orbix Server Socket Port Number

TopoServer

5558

CmServer

5555

GenericServer

5559

LogServer

5556

CWMGateway

5557

Note   You must assign the corresponding socket port number to the server in conflict.

Repeat Steps 1 and 2 for each Orbix server that is in conflict, assigning the appropriate socket port number.

Step 3   Once all the Orbix server socket port issues have been resolved, restart CWM to let the Orbix server begin using the appropriate socket port.

Important Start Up Note

When the Topology application opens, the Network Topology main window is blank. The system will not begin displaying nodes and trunks until you click on the Network Topology expanded view button. Figure 1 shows the main menu bar of the Network Topology application. The Network Topology Expanded View button (as shown in the callout) must be selected in order to display your network within the Network Topology main window.


Figure 1: Network Topology Main Menu Bar


Figure 2 shows the expanded view of the Network Topology displayed after clicking the Network Topology Expanded View button.


Figure 2: Network Topology Display (After Clicking the Network Topology Expanded View Button)


Important Configuration Notes

This section provides important information about configuration.

Setting Up CWM to HP OpenView Communication

All of the libraries in HP OpenView are shared libraries. In order to get CWM and HP OpenView communicating properly you need to configure the LD_LIBRARY_PATH by following this procedure:

If you are using the Korn shell, enter the following commands as root:

#  LD_LIBRARY_PATH=$LD_LIBRARY_PATH:/opt/OV/lib

#  export LD_LIBRARY_PATH

If you are using the C shell, enter the following command as root:

#  setenv LD_LIBRARY_PATH ${LD_LIBRARY_PATH}:/opt/OV/lib

Naming Managed Nodes

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

Enabling the Connection Descriptor

About the connection descriptor, you can turn the feature on/off by setting a flag in the /usr/users/svplus/config/CwmDoaminGlobal.conf file

DESCRIPTOR_FLAG = 0

0 means off

1 means on

IP Connectivity Through Out-of-Band Management

To use out-of-band management, complete the following configuration.

MGX 8850 Release 2 Nodes

Step 1   Set up both LAN IP addresses and the Network IP (ATM IP) address in each MGX 8850 node.

The LAN IP and the ATM IP addresses should not be the same.

Step 2   Set appropriate subnet mask addresses for each MGX 8850 node.

Step 3   Set the Trap IP address to the Network IP address for each MGX 8850 node.

IP Router

Step 1   Configure the IP router which resides in the same LAN segment as the MGX 8850 Release 2 nodes.

Step 2   Add static routes in the router for all Network IP addresses in the router so it routes them to the respective LAN IP addresses using the iproute command.

Note   Refer to your specific router documentation for more detailed information.

Coldstart Script

CWM 10.3 contains a script called coldstart which allows you to coldstart the system and yet still save user data. An optional -F argument allows you to coldstart the system and remove all data (network and user created).

Entering coldstart -F removes all network data and user created data

Executing the coldstart script without the optional -F argument removes all network data while preserving the existing user data in the following databases:

User Created Data

This section delineates the three types of user-defined data preserved when executing the coldstart script without the optional -F argument. The lists of files are separated into six subsections, user configuration data, user defined meta data, and user collected statistics data, for each of the two databases:

User Configuration Data in the stratacom Database

User Defined Meta Data in the stratacom Database

User Collected Statistics Data in the stratacom Database

User Defined Meta Data in the statsdb Database:

User Collected Statistics Data in the statsdb Database:

Enabling CWM to CWM Communication

In Release 10.3, CWM provides a script to sync up a CWM database with another remote CWM workstation without running the two CWMs in primary-secondary mode.

This script synchronizes the following user-related tables in the stratacom database:

This script also synchronizes the following user-related tables in the statsdb database:

Caution The script will delete whatever existing data is in the tables on the local workstation. Do not expect to retain any existing data in the tables after running the script.

Preliminary Steps

Before running the script, you must ensure that the database on the remote workstation can be opened from the current workstation. This can be verified by confirming in the $INFORMIXDIR /etc/sqlhosts file. This file must have an entry for the remote CWM station being provided as a parameter to usertblDBsync. Otherwise, an entry can be added to this file for the remote workstation. The user may add an entry for the remote station either manually or using a script that is already part of the existing CWM package, such as upd_sqlhosts.

To add an entry to the sqlhosts file using the script, the following steps need to be followed.

The script is called upd_sqlhosts and can be found in the ~svplus/scripts directory.

SYNTAX: upd_sqlhosts <remote_CWM_workstation_name>

Note   The usertblDBsync script will NOT work if the database on the remote workstation can not be opened from the current workstation. This is because the database tables can not be copied over if the system does not permit a connection to the remote database.

Before running the script, you must ensure that the Statistics Collection Manager is installed on both the local machine as well as on the remote machine.

CWM must already be running on the workstation you are pulling the tables from.

This will help the user not having to manually enter the data in these tables on all the workstations that CWM is going to be run on.

This script must be executed on the machine where the database tables need to be synced up BEFORE CWM is started. CWM must already be running on the remote workstation before the script starts.

This script can be found in the ~svplus/scripts directory.

Steps for Executing the usertblDBsync Script

Execute the following steps to copy the remote table information to the database on the local machine using the usertblDBsync script.

Step 1   Execute the upd_sqlhosts script to add an entry in the "sql-hosts" file on the local machine for the remote CWM station.

# upd_sqlhosts <remote_CWM_workstation_name>

Where <remote_CWM_workstation_name> is the name of the remote CWM station.

This step allows the local machine to make a remote database connection.

Note   This step can also be done manually without using the script. You can use the vi editor to append the name of the remote CWM station to the list of hosts within the sqlhosts file in $INFORMIXDIR/etc.

Example:

#     Default sqlhosts file.
#
#**************************************************************************
 
demo_on     onipcshm    on_hostname     on_servername
demo_se     seipcpip    se_hostname     sqlexec
cwmtopo61   ontlitcp    cwmtopo61       informix_istar
CWMTOPO44   ontlitcp    CWMTOPO44       informix_istar

Step 2   Execute the usertblDBsync script 

# usertblDBsync <remote_CWM_workstation_name>

Executing this script copies the following user-related tables in the stratacom database from the remote CWM workstation specified by <remote_CWM_workstation_name> to the local machine:

There are user-related Statistics data in the statsdb database also. The script will prompt you to copy the user-related statistics data in the statsdb database tables from the statsdb database on the remote CWM workstation specified by <remote_CWM_workstation_name> to the local machine.

The prompt will look like the following:

Do you want to copy stats tables from statsdb database?
Enter 0 for No or 1 for Yes: [Default:0]

Step 3   Enter 1 to copy the following tables from the statsdb database:

Ensure that the networks in the network.conf file on the local machine are the same as those specified n the network.conf file on the remote CWM station, where CWM is already synced up. You will see a warning to this effect displayed on the screen after the tables have been successfully loaded.

CWM Out of Band Management for MGX8850 Release 2

In Release 10.3, CWM always communicates with the MGX 8850 Release 2 nodes using the ATM inband address. CWM uses the ATM inband address for topology discovery, trap registration, configuration upload and as well as provisioning. In order to allow CWM to perform out-of-band communication with the switch via the switch's ethernet LAN interface, configure static IP routes on the CWM workstation station (and on any via router if necessary) to forward IP traffic which is destined to ATM inband address to the node's ethernet LAN interface.

Caution You should never configure the same IP address for both ethernet LAN and ATM interface.

Example:


Figure 3: CWM Out of Band Management for MGX 8850 Release 2 Nodes


In the above example, the user is required to configure static routes on both CWM workstations and router as well. Since MGX8850-4 and MGX8850-3 are on the same LAN subnet as CWM station, the user can configure the static routes on unix command prompt as follows:

# route add host x.x.x.3 y.y.y.3 1

# route add host x.x.x.2 y.y.y.100 1

# route add host x.x.x.4 y.y.y.4 1

On the router:

router> config term

router(config)# ip route x.x.x.2 255.255.255.0 z.z.z.2

router(config)# end

router> write mem

ATMARP Protocol

This protocol allows for learning the mapping between SVC endpoint and IP address dynamically. Most routers implement this protocol. It is very useful and saves extra configuration on routers.

Because of the advantages, it was decided that this protocol should be implemented as well by the IPATM interface. The interface will support the functionality of an ATMARP client.

IPATM Configuration

This section describes the configuration of the IPATM interface on the MGX 8850 Release 2 as needing the AESA address of all routers that it needs to establish SVC connections with. It would be nice to not require the MGX 8850 Release 2 user to configure all router AESA.

Two other options have been discussed by where proprietary extensions are added to PNNI that will propagate these AESA between MGX 8850 Release 2 and they will be marked as "important to IPATM."

The first option is to pick one of the reserved AESA addresses to be used by the IP Connectivity functionality of MGX 8850 Release 2. Each router would use these reserved AESA addresses for their endpoints. PNNI knows about this reserved AESA and informs the local IPATM interface when it learns of new endpoints.

Note   This does not require changes to the functionality of PNNI, but requires PNNI to know about special addresses.

The second option is to extend PNNI to support the transfer of the router(s) AESA addresses as part of its node-to-node payload. These addresses, when learned by the remote PNNI are given to their local IPATM interfaces as configuration. This option does require changes to PNNI payload and will not be supported by other vendor PNNI implementations.

With one of these enhancements, no router configuration is needed for the IPATM interface. Via PNNI, the IPATM interface will learn about all the routers in the MGX 8850 Release 2 network.

Note   If the router is NOT running the ILMI protocol, then a static route must be added for the router so that SVC address information on the router can be learned by PNNI.

Using IP Subnet Routing instead of IP-Host Routing

The router must be able to accept packets from the host/workstation and forward them to the appropriate SVC of a MGX 8850 Release 2 IPATM interface. To do this requires an IP route in the router. This section describes the use of IP Subnet routing for this purpose. This means that every MGX 8850 Release 2 IPATM interface is in the same IP network as the router's ATM interface. This allows one route in the router's IP routing table to service all MGX 8850 Release 2 IP addresses.

The functionality of the IP Connectivity described in the chapter does not preclude the use of IP-Host routing. This would allow the MGX 8850 Release 2 IPATM interface to choose any IP address it wants without worrying about which IP network the address was using. This allows flexibility on the configuration of the IPATM interface but at the expense of the configuration on the router. The router will automatically inform host/workstations of the IP Subnet address of the MGX 8850 Release 2 IP Connectivity network using RIP. For the router to do the same for the IP-Host routing configuration, the router must have static routes pre-configured for each MGX 8850 Release 2 IPATM interface.

It is a configuration choice of the user as to which IP network addressing should be used.

Interaction between IPATM Interface and Ethernet Interface

This section describes IP Connectivity using the IPATM interface for communication with hosts/workstations requiring IP data-paths to MGX 8850 Release 2 nodes. Another interface, Ethernet, can also be used for IP Connectivity. Because of the way IP routing is setup on the MGX 8850 Release 2, the node cannot behave as an IP router. All IP communications must be for the MGX 8850 Release 2 receiving the data, or the data will be dropped.

A special hook must be added to the IP Connectivity software on the MGX 8850 Release 2 in order to support both interfaces simultaneously. Remember, the IPATM interface must "remember" the SVC being used for communication with a host/workstation. When both interfaces are in use, the IP layer must "remember" which interface should be used for communication with the host/workstation. To accomplish this, the following steps are taken:

  When a packet is received on the Ethernet interface, it is checked to make sure it is for the local MGX 8850 Release 2. If it is, the source IP address is obtained from the packet and this source IP address is looked up in the IPATM interface's cache. This is the cache that stores the host/workstation IP address to SVC address mapping. If the source IP address is found in the cache it is removed and the associated IP route deleted. From now on communication with the host/workstation associated with the source IP address will be via the ethernet interface.
  As described earlier, any packet received by the IPATM interface causes a local cache entry to be added or updated and an IP route added. Through this mechanism, it can be remembered that the IPATM interface is to be used for any further communication with the host/workstation that originally transmitted the data.

Sample Configurations

The topology shown in Figure 4 will be used to demonstrate two sample configurations for IP Connectivity. In all sample configurations, Cisco IOS-style commands are used. This is to show functionality and not meant to show command formats for all router types. Also, workstation configuration is in a Unix format for the same reasons.


Figure 4: Sample MGX 8850 Release 2 Network Topology


Configuration Sample 1

The following is assumed:

The following is required for configuration:

MGX 8850 R2 #1

Step 1   Configure IP address of IPATM interface.

  ipifconfig atm0 192.0.0.10 arp

Step 2   Configure local AESA.

  svcifconfig atm0 local 47.0091.8100.0000.1010.1010.1010.1010.1010.1010.10

Step 3   Configure router AESA of Router #1.

  svcifconfig atm0 router 47.0091.8100.0000.0101.0101.0101.0101.0101.0101.01 arp llcencap

Step 4   Configure router AESA of Router #2.

  svcifconfig atm0 router 47.0091.8100.0000.0202.0202.0202.0202.0202.0202.02 arp llcencap

MGX 8850 R2 #2

Step 1   Configure IP address of IPATM interface.

  ipifconfig atm0 192.0.0.11 arp

Step 2   Configure local AESA.

  svcifconfig atm0 local 47.0091.8100.0000.1111.1111.1111.1111.1111.1111.11

Step 3   Configure router AESA of Router #1.

  svcifconfig atm0 router 47.0091.8100.0000.0101.0101.0101.0101.0101.0101.01 arp llcencap

Step 4   Configure router AESA of Router #2.

  svcifconfig atm0 router 47.0091.8100.0000.0202.0202.0202.0202.0202.0202.02 arp llcencap

Router #1

Step 1   Configure IP address of ATM interface.

  interface atm 0
  ip address atm0 192.0.0.1 255.255.255.0

Step 2   Configure local AESA.

  atm nsap-address 47.0091.8100.0000.0101.0101.0101.0101.0101.0101.01

Step 3   Configure router to be ATMARP server.

  atm arp-server self

Step 4   Configure the signalling PVC.

  atm pvc 1 0 5 qsaal

Step 5   Configure UNI 3.1.

  atm uni-version 3.1

Step 6   Make sure that IP routing is enabled.

  ip routing

Step 7   Setup RIP protocol to advertise subnet.

  router rip
  network 192.0.0.0

Router #2

Step 1   Configure IP address of ATM interface.

  interface atm 0
  ip address atm0 192.0.0.2 255.255.255.0

Step 2   Configure local AESA.

  atm nsap-address 47.0091.8100.0000.0202.0202.0202.0202.0202.0202.02

Step 3   Configure router to be ATMARP server.

  atm arp-server self

Step 4   Configure the signalling PVC.

  atm pvc 1 0 5 qsaal

Step 5   Configure UNI 3.1.

  atm uni-version 3.1

Step 6   Make sure that IP routing is enabled.

  ip routing

Step 7   Setup RIP protocol to advertise subnet.

  router rip
network 192.0.0.0 Workstation #1
Workstation #2

Configuration Sample 2

The following is assumed:

The following is required for configuration:

MGX 8850 R2 #1

Step 1   Configure IP address of IPATM interface.

  ipifconfig atm0 192.0.0.10 arp

Step 2   Configure local AESA.

  svcifconfig atm0 local 47.0091.8100.0000.1010.1010.1010.1010.1010.1010.10

Step 3   Configure router AESA of Router #1.

  svcifconfig atm0 router 47.0091.8100.0000.0101.0101.0101.0101.0101.0101.01 noarp vcmux

Step 4   Configure router AESA of Router #2.

  svcifconfig atm0 router 47.0091.8100.0000.0202.0202.0202.0202.0202.0202.02 noarp vcmux

Step 5   Configure a static route that specifies the endpoint for Router #1 AESA so that PNNI learns about this endpoint.

MGX 8850 R2 #2

Step 1   Configure IP address of IPATM interface.

ipifconfig atm0 202.0.0.11 arp

Step 2   Configure local AESA.

  svcifconfig atm0 local 47.0091.8100.0000.1111.1111.1111.1111.1111.1111.11

Step 3   Configure router AESA of Router #1.

  svcifconfig atm0 router 47.0091.8100.0000.0101.0101.0101.0101.0101.0101.01 noarp vcmux

Step 4   Configure router AESA of Router #2.

  svcifconfig atm0 router 47.0091.8100.0000.0202.0202.0202.0202.0202.0202.02 noarp vcmux

Step 5   Configure a static route that specifies the endpoint for Router #2 AESA so that PNNI learns about this endpoint.

Router #1

Step 1   Configure IP address of ATM interface.

  interface atm 0
  ip address atm0 132.0.0.1 255.255.0.0

Step 2   Configure local AESA.

  atm nsap-address 47.0091.8100.0000.0101.0101.0101.0101.0101.0101.01

Step 3   Configure the signalling PVC.

  atm pvc 1 0 5 qsaal

Step 4   Configure UNI 3.1.

atm uni-version 3.1

Step 5   Manually configure mapping for MGX 8850 R2 #1 AND MGX 8850 R2 #2.

  map-list atm
  ip 192.0.0.10 atm-nsap 47.0091.8100.0000.1010.1010.1010.1010.1010.1010.10
  ip 202.0.0.11 atm-nsap 47.0091.8100.0000.0202.0202.0202.0202.0202.0202.02

Step 6   Manually setup IP route table entries for Popeye #1 and Popeye #2.

  ip route 192.0.0.10 255.255.255.0 132.0.0.1
  ip route 202.0.0.11 255.255.255.0 132.0.0.1

Step 7   Make sure that IP routing is enabled

  ip routing

Step 8   Setup RIP protocol to broadcast these static routes.

  router rip
  redistribute static

Router #2

Step 1   Configure IP address of ATM interface.

  interface atm 0
  ip address atm0 72.0.0.2 255.0.0.0

Step 2   Configure local AESA.

  atm nsap-address 47.0091.8100.0000.0202.0202.0202.0202.0202.0202.02

Step 3   Configure the signalling PVC.

  atm pvc 1 0 5 qsaal

Step 4   Configure UNI 3.1.

  atm uni-version 3.1

Step 5   Manually configure mapping for MGX 8850 R2 #1 AND MGX 8850 R2 #2.

  map-list atm
  ip 192.0.0.10 atm-nsap 47.0091.8100.0000.1010.1010.1010.1010.1010.1010.10
  ip 202.0.0.11 atm-nsap 47.0091.8100.0000.0202.0202.0202.0202.0202.0202.02

Step 6   Manually setup IP route table entries for Popeye #1 and Popeye #2.

  ip route 192.0.0.10 255.255.255.0 72.0.0.2
  ip route 202.0.0.11 255.255.255.0 72.0.0.2

Step 7   Make sure that IP routing is enabled.

  ip routing

Step 8   Setup RIP protocol to broadcast these static routes.

  router rip
  redistribute static

Workstation #1

Step 1   Add IP address of MGX 8850 R2 #1 to host table.

Step 2   Add IP address of MGX 8850 R2 #2 to host table.

Step 3   Add route to MGX 8850 R2 #1 via Router #1.

  route add host 192.0.0.10 <Router #1 IP address for ethernet interface>

Step 4   Add route to MGX 8850 R2 #2 via Router #1.

  route add host 202.0.0.11 <Router #1 IP address for ethernet interface>

Workstation #2

Step 1   Add IP address of MGX 8850 R2 #1 to host table.

Step 2   Add IP address of MGX 8850 R2 #2 to host table.

Step 3   Add route to MGX 8850 R2 #1 via Router #2.

  route add host 192.0.0.10 <Router #2 IP address for ethernet interface>

Step 4   Add route to MGX 8850 R2 #2 via Router #2.

  route add host 202.0.0.11 <Router #2 IP address for ethernet interface>

CWM Configuration

The default CWM configuration supports most networks. Very large networks with a significant number of PVCs (100,000 or more) require a change to the default CWM configuration for better performance during cold or warm starts of CWM. Please contact CWM Support group for help in this matter.

Modifying the emd.conf File

The /usr/users/svplus/config/emd.conf file provides nineteen configuration parameters that control the operation of the Equipment Manager Switch Daemon (EMD). Each of the nineteen parameters is preceded by a comment statement that describes the parameter. To achieve better cold and warm start performance, complete the following steps:

Step 1   Search for Tftp Timeout, and change the value from 1 hour to 2 hours.

Step 2   Search for Attempt to resynchronize, then change the value from 10 times to
40 times.

Step 3   Change the next parameter, Upload TFTP file, from 4 times to 15 times.

Step 4   Search for next SNMP shelf config request, then change the value from Minimum 600 to Minimum 300 (seconds backoff).

Modifying the tftpmgr.conf File

The /usr/users/svplus/config/tftpmgr.conf file provides configuration parameters about the TFTP Request Manager. To achieve better cold and warm start performance, complete the following steps:

Step 1   Change the NumberOfRetries value to 40 from the default value of 20.

Step 2   Change the MaxTFTPSession value to 72 from the default value of 32.

CWM Dedicated IP Ports

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

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

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

CWM 10.3 to CWM 10.3: Ports used by ORBIX:


Table 12: Orbix Fixed Socket Port Numbers
Orbix Server TCP Socket Port Number

TopoServer

5558

CmServer

5555

GenericServer

5559

LogServer

5556

CWMGateway

5557

Unique Node ID

The Node ID is now stored in the node_info table as opposed to the node table in CWM 9.2. The Node ID is assigned by CWM. To have the same Node ID across the domain, the user must enable the CWM to CWM communication to ensure that the node_info table is in sync across all the CWM systems within a domain.

The CWM 10.3 installation automatically converts the nodes.config file to node_info table during CWM 9.1, CWM 9.2, CWM 10.1, or CWM 10.2 to CWM 10.3 upgrades.

Do not use the SV+CreateDb command to drop the node_info table. It can only be dropped by using the SV+CreateDb -F command.

Security Profiles

The security profile and user profile are no longer in the file format, they 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 SV+CreateDb command is executed during a cold start. These tables can only be dropped by executing the SV+CreateDb command with the "-F" option.

If CWM 10.3 is being upgraded from CWM 9.1 or 9.2 or 10.1 or 10.2, then the old security profile will automatically be converted and loaded into the database during upgrade.

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

Note   You should perform all user or profile Add, Modify, and Delete operations from the primary CWM workstation.

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.

Note   Currently, the Security GUI icon appears as the Admin icon in the Topology GUI.

CWM Database

After performing the creation of a new database by executing the create_db command, if CWM is restarted before it is synchronized with the network, it will result in a database inconsistency. In this case, perform create_db before restarting CWM 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.

Network Configuration

CWM 10.3 supports networks running multiple protocols like Auto Route/PNNI. Earlier versions of CWM needed the configuration in config.sv file to auto discover the networks. The file config.sv has been replaced by a new file called network.conf in the /usr/users/svplus/config directory. The new network.conf file format is totally different from config.sv and is more readable compared to config.sv. The new network.conf file allows you to specify the gateway nodes for Auto Route and PNNI networks.

CWM 10.3 supports discovery of networks running Auto Route and PNNI protocols. Add the following configuration for each network in the network.conf file.

Format of network.conf File

Comments: Any line starting with a `#' is treated as a comment line

Parameter Value Separator: `:' is treated as a separator between parameter and its value

:Specifying Network Name: User needs to specify the name of the network in the format given below

NETWORK: <Network Name>

There is limitation of Maximum 8 characters in Network Name. `:' is treated as a separator

Specifying Gateway Name:

GATEWAYS: <Gateway Name>

In case of PNNI networks user can supply a comma separated list in case there are multiple Gateways to the same network.

Specifying the Discovery Protocol:

DISCOVERY PROTOCOL: <Protocol Name>

Protocol Name has two values. AUTOROUTE or PNNI

AUTOROUTE is used only to discover Auto Route networks

PNNI is used for ILMI or PNNI discovery.

Specifying IP Reachability Method:

This parameter is used only for Auto Route networks.

IP REACHABILITY FLAG:<IP Flag>

IP Flag should be used for AUTOROUTE networks to specify NWIP_ON or NWIP_OFF

Specifying OPTIONAL Parameter:

This parameter is used only for Auto Route networks.

OPTIONAL: "TIMEOUT = 7, RETRANSMIT = 6, THROTTLE = 0, ACKNOWLEDGE = 30, BLOCKSIZE = 1024"

Topology Discovery Configuration for Auto Route Networks

You must enter a configuration for each Auto Route network to be discovered by CWM in /usr/users/svplus/config/network.conf file. Here is the sample configuration for a Auto Route network with gateway nmsbpx02.

    # Sample Network 1 : Discover an AUTO ROUTE Network
# Note : Use only one Gateway per network in case of AUTOROUTE networks
NETWORK:Network1
GATEWAYS:nmsbpx02
DISCOVERY PROTOCOL:AUTOROUTE
IP REACHABILITY FLAG:NWIP_ON
OPTIONAL:"TIMEOUT = 7, RETRANSMIT = 6, THROTTLE = 0, ACKNOWLEDGE = 30, BLOCKSIZE = 1024"
Topology Discovery Configuration for PNNI Networks

You must enter configuration for each PNNI network to be discovered by CWM in /usr/users/svplus/config/network.conf file. Here is the sample configuration for a PNNI network with gateway nmspnni4.

    # Network 9 : Discover a PNNI network
NETWORK:Network9 
GATEWAYS:nmspnni4
DISCOVERY PROTOCOL:PNNI

You also need to specify those nodes through the Network Configurator GUI tool for which the following apply:

Note   Specify the IP Address as "Network IP" and mode as "Connected" for these nodes in the Network Configurator GUI Tool.
Topology Discovery Configuration for StandAlone Nodes

You can configure MGX8850 (Release 1) or MGX8850 (Release 2) nodes as Stand Alone nodes. Follow these steps:

Step 1   Run Network Configurator GUI tool.

Step 2   Choose Edit->Node->Add Dialog.

Step 3   Fill in all the information in Name Tab of Add Dialog.

Step 4   Choose correct Model No and Mode (Stand Alone in this case) and IP Address (Lan Ip Address) in Mode Tab of Add Dialog.

Step 5   Click on the OK button.

Step 6   Save the configured node using File->Save option.

Note   The network.conf file doesn't require any modification for Stand Alone nodes.

Connection Manager

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

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.

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

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

Certain types of connections, such as VBR.1 or CBR, with policing parameters, can't be modified by CWM if the default was changed using the Switch CLI.

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

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

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.

Switch software supports only ATFR and ATFST types of connections for UXM on a feeder node. CWM does not support ATFR or ATFST for ATM to ATM connections (from the Connection Manager GUI select Configure->New ATM-ATM connection->VBR.3), the connection type on the Switch CLI will show as ATFR for all three segments. If you select an ABR.FS connection type for an ATM to ATM connection (from the Connection Manager GUI select Configure->New ATM-TM connection->ABR.FS), the connection type on the Switch CLI will be ATFST for all three segments. For all other limitations of connection types supported for UXM on feeder nodes, refer to the Switch Software Release Notes for release 9.3.10.

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

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


Table 13: PVC ECN Threshold and DE Threshold GUI Defaults and Service Agent
Parameter GUI Default Values Service Agent

Ingress ECN Threshold

10% of Ingress VC Q Depth -> 6554

6553

Ingress DE Threshold

50% of Ingress VC Q Depth -> 32768

32767

Egress ECN Threshold

10% of Egress VC Q Depth -> 6554

6553

Egress DE Threshold

50% of EGress VC Q Depth -> 32768

32767

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

The switch generates the "Failure validating remote endpoint description" error message when the PVC was modified or deleted using CWM. The problem occurs when CWM is managing a mixed release network and the node mastering the PVC has an older release than the remote end, and the remote end point is in a newer card which was introduced after the older release. This is a SWSW limitation. The PVC can be deleted using the Switch CLI.

The Connection Manager ignores the SVC VPI partitioning range in BPX for adding ATM PVC connections with vpi=0 and they are terminated in BXM cards and both SVC Hi VPI and SVC Low VPI are set to 0 on the switch for the same port. However, if you reserve SVC Low VPI to 0 and SVC Hi VPI to nonzero for the SVC range, the Connection Manager will block the PVC provisioning in the reserved SVC VPI range.

ForeSight connections are not supported in PXM UNI ports. In other words, you are not able to create abr.fs service type connections with end points on a PXM UNI port.

RPM

CWM 10.3 supports only ATM connection type and vbr.3 and abr1 service type for end points terminated on the RPM card.

For an RPM VCCON, the only VPI value allowed is 0. To add an RPM VPCON, an asterisk (*) should be specified as the VCI value.

If a VPI, VCI value is used to establish an RPM channel on one subinterface, the SAME VPI, VCI pair cannot be used with another subinterface. This is due to an RPM limitation. If such action is attempted, CWM 10.3 will emit an "Local/Remote end point already exists" error.

CWM 10.3 does not support provisioning of RPM channels for subinterface values over 32767.

For a PVC involving RPM, CWM 10.3 supports ATM Service Type VBR only (VBR.3 for ATM-ATM, ATM-FR for ATM to FR PVCs and ABR.1 for ATM-ATM PVCs). The UBR Service Type is not supported for RPM by CWM 10.3.

CWM 10.3 provisions the RPM end of an "End to End" PVC by using the IOS atm pvc command followed by the addcon command. An RPM end point added using the atm pvc command cannot be modified/deleted using the (newer) pvc command and vice-versa.

To establish a channel on RPM, two IOS commands are required:

If the RPM leg gets deleted (new configuration restored on RPM), CWM 10.3 cannot detect the condition. However, if necessary, CWM 10.3 can be used to delete and re-add the entire channel by reprovisioning the "End to End" PVC.

If the PXM leg gets deleted (for example, clrallcnf on MGX 8850), CWM 10.3 cannot provision the channel until the RPM leg is manually deleted. To do that, you must login to the RPM card and perform the following IOS commands:

The peak and average values for a feeder PVC involving RPM is limited by the bandwidth of the MGX 8850 feeder trunk. As per the strata MIB, the value of average (expressed in cells/second below) is limited for each trunk type as:

  ASI/BNI
  BXM/UXM
  ALM-B(BTM)

The value of peak (express here in cells/second) is limited as for each trunk type as:

   BXM with HEC line formatting

While one CWM 10.3 station is used to provision connections on a specific RPM card, attempts to provision on the same card by another CWM 10.3 station can result in failure in the provisioning of RPM connections.

Provisioning of RPM can take up to 25 seconds on average. On rare occasions, the Connection Manager GUI may time out before IOSMGR returns. The returned IOS messages are eventually updated in the Result pane in the Connection Manager GUI.

The following are the typical causes of the error message "atm pvc missing"message:

The typical cause of the error "add connection to PXM failed" is the resource partition is not configured.

If one of the following error message is encountered:

Complete the following steps:

Step 1   telnet to the MGX 8850 Release 1 node and login to the RPM card (in enable mode).

Step 2   Enter the command show log and hit Return to go to the end.

Note   The log may be wrapped on the RPM card.

For other error messages returned by IOSMGR, complete the following steps:

Step 1   vi ~svplus/log/iosmgr.log

Step 2   Go to the end of the file ($G) and check the command and arguments used for the expect script. Check the tracefile entry as shown at the end of the command.

Step 3   Open the tracefile file and go to the end of the file. Examine the log of the expect session.

The existing RPM connections will not be removed from the CWM database when the RPM card is pulled out of the MGX 8850 shelf.

Note   To manage RPM MGX 8850 nodes, CWM 10.3 must establish telnet sessions to the RPM card and issue IOS commands. Because of this, be cautious using other NMS products to manage the RPM card.

SNMP Service Agent Release Notes

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

CWM SNMP Agent Configuration Notes

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

  Syntax:
TRANSPORT special SNMP
OVER UDP SOCKET
AT PORT 8161

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

  Syntax:
GET_COMMUNITY     public
SET_COMMUNITY     private

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

Statistics Collection Manager Release Notes

This section provides release note information about the Statistics Collection Manager (SCM) application.

Default Configuration Requires Change

Change the default value of AXSM_TRAPWAIT is a parameter in the scmcollsvr.conf file in the /usr/users/svplus/config directory. The current default value of 10 must be changed to 25.

New Features

Cisco WAN Manager 10.3 Statistics Collection Manager provides the following features:

Timed Stats Collection—Using tftp to retrieve statistics data files is available for BPX, IGX, MGX 8850 Release 1, MGX 8230, MGX 8250, and MGX 8220.

Trap Stats Collection—Using ftp to retrieve statistics files, ScmCollSvr waits for a file ready trap message from the switch to start ftp. Trap Stats Collection is used only for MGX 8850 Release 2.

Both Time Stats Collection and Trap Stats Collection are node based. However, the statistics files from AXSM cards in MGX 8850 Release 2 are card based.

Separate SCM Installation—Install the Statistics Collection Manager software after installing CWM software on the same workstation.

Note   Stand Alone SCM is not supported in CWM 10.3.

QBin stats and virtual port stats for BPX have been included.

WingZ provides an adhoc statistics report.

Limitations

We recommend that you use the default number of 100 nodes per SCM collector. Final calculations to determine the maximum number of nodes to supports have not yet been completed.

Note   The total number of nodes supported will be provided at a later date.

If you use too high a number of nodes per SCM, such as 1,000, CWM the workstation might fail on a UNIX select system call, ftp or tftp limitation.

The following limitations also exist:

Additional Information

The SCM supports a maximum of 1,000 nodes for time collectors and 1,000 cards for trap collectors (these values might change). The default setting is 100 nodes. If the workstation manages a large number of node, scmcollsvr.conf should be tuned to achieve maximum performance, especially the buffer size of all file queues and the number of threads for ftp or tftp.

If you perform a create_db operation, the cache/scm files must be manually deleted.

You must adhere to the following rules when you configure peak interval through CWM. Violating these rules will cause tftp error 22 to be displayed in the SCM.

The switch requires processing time to parse the stats.enable file. Depending on the number of statistics and the number of objects, this time can be a long time. Currently, SCM has a finite value (maximum 420 seconds) for time-out to wait for the switch response. There might be cases where SCM will time-out waiting for the switch to finish parsing the stats.enable file. If there are excessive time-outs, try one of the following:

    1. Cut down on the number of statistics enabled and be able to get the status of stats-enabling from SCM.

    2. Use CLI commands such as dspstatparms, dspchstatcnf, dsptrkstatcnf, dspportstatcnf, and dsplnstatcnf to make sure their desired stats are enabled.

    3. Following are the formulae to calculate the time to enable statistics on the switch:

    4. time—Calculated using: 

    		time = (stats / cnt) * delay

Where:

   stats—Calculated using:
(conns * stats_per_con) + (CLNs * stats_per_cln) + (trks * stats_per_trk) +
(ports * stats_per_port)
  cnt—Number of stats configured in one group before giving up CPU; a configurable parameter on the switch
  delay—Delay between enabling of each group of statistics; a configurable parameter on switch.
Note   Occasional time-outs might occur if a node is busy for that period of time. However, this is very intermittent and, if it occurs, should cease once loading of the node stabilizes.

This information is described in more detail in CR CSCdj39737.

Features Not Supported:

Standalone Statistics Collection is not supported in CWM 10.3. You must install and collect statistics on a CWM 10.3 workstation.

WANCV 3.30 Notes and Cautions

For MGX 8220, this CiscoView Package requires MGX 8220 Boot Code version 1.0.00 and MGX 8220 ASC firmware version 4.0.20 or higher. For the new features, MGX 8220 firmware 5.0.10 or later is recommended.

In addition to the installation instructions, please refer to README.txt file.

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.

Control Point Interfaces

Command Line Interface

Use the following command line interface (CLI) commands to configure the IP Connectivity IPATM interface.

Note   Parameters that are within angle brackets ([]) are optional parameters.

ipifconfig—Configure IP address information for an IP interface

  ipifconfig <interface> [<ip_address>] [up | down] [netmask <mask>]
  [broadcast <broad_addr>] [arp | noarp] [svc | nosvc] [pvc | nopvc]
  [default | nodefault] [clrstats]

Where:

  <interface>—atmX, where X is the unit number (currently X is 0)
  <ip_address>—IP address of interface (optional), but must exist if interface not previously configured
  [up | down]—Mark interface up or down (optional)
  [netmask <mask>]—Specify network mask for interface (optional)
  [broadcast <broad_addr>]—specify broadcast IP address for interface (optional)
  [arp | noarp]—Specify whether ARP is enabled or disabled (optional), default is enabled if interface supports ARP
  [svc | nosvc]—Specify whether SVC is enabled or disabled (optional), default is enabled if interface supports SVC
  [pvc | nopvc]—Specify whether PVC is enabled or disabled (optional), default is disabled
  [default | nodefault—Use this interface as the default route or disable this interface as the default route (optional)
  [clrstats]—Clear all interface and SVC/PVC statistics for given interface (optional)

dspipif—Display IP configuration and statistics information for one or all IP interfaces

  dspipif [<interface>]

Where:

  [<interface>]—atmX, where X is the unit number (optional)

svcifconfig—Configure SVC address information for an IP interface

  svcifconfig <interface> router | local <AESA> [arp | noarp] [llcencap | vcmux] [default | nodefault] [reset] [delete] [clrstats]

Where:

  <interface>—atmX, where X is the unit number (currently X is 0)
  router | local <AESA>—Specify whether the given AESA address corresponds to a router or the local PXM. One of the keywords "router" or "local" must be specified. The <AESA> is an NSAP address used by the router or the local PXM.
  [arp | noarp]—Specify whether ATMARP is enabled or disabled on this SVC (optional). Interface must also support ARP for ATMARP to be available (see ipifconfig above).
Note   This parameter is valid for router AESA configuration only.
  [llcsnap | vcmux]—Specify the encapsulation method to be used on the SVC. llcsnap corresponds to LLC Snap encapsulation, while vcmux is for VC Based Multiplexing.
Note   This parameter is valid for router AESA configuration only.
  [default | nodefault]—Use this SVC as the default route on the interface or disable this SVC as the default route (optional)
  [reset]—Force reset on the SVC. SVC call is released, then the call is attempted again (optional)
  [delete]—Delete the specified AESA configuration (optional)
  [clrstats]—Clears all SVC statistics on this interface (optional)

dspsvcif—Display SVC address information for one or all IP interfaces supporting SVC

  dspsvcif [<interface>]

Where:

  [<interface>]—atmX, where X is the unit number (optional)

pvcifconfig—Configure PVC address information for an IP interface

  pvcifconfig <interface> router | feeder <PVC> [arp | noarp] [llcencap | vcmux] [default | nodefault] [up] [reset] [delete] [clrstats]

Where:

  <interface>—atmX, where X is the unit number (currently X is 0)
  router | feeder <PVC>—Specify whether the given PVC address corresponds to a router or a feeder interface. One of the keywords router or feeder must be specified. The <PVC> is a PVC address of the form VPI.VCI used by the router or the feeder interface.
  [arp | noarp]—Specify whether ATMARP is enabled or disabled on this PVC (optional). Interface must also support ARP for ATMARP to be available (see ipifconfig above).
Note   This parameter is valid for router AESA configuration only.
  [llcsnap | vcmux]—Specify the encapsulation method to be used on the PVC.
  llcsnap corresponds to LLC Snap encapsulation, while vcmux is for VC Based Multiplexing.
Note   This parameter is valid for router AESA configuration only.
  [default | nodefault]—Use this PVC as the default route on the interface or disable this PVC as the default route (optional)
  [up]put the PVC into UP state and attempt to bind the lcns associated. PVC must exist (optional)
  [reset]—Force reset on the PVC. PVC is placed back into SETUP state (optional)
  [delete]—Delete the specified PVC configuration (optional)
  [clrstats—Clear all PVC statistics on this interface (optional)

dsppvcif—Display PVC address information for one or all IP interfaces supporting PVC

  dsppvcif [<interface>]

Where:

  [<interface>—atmX, where X is the unit number (optional)

dspipifcache—Display interface cache translation table for one or all interfaces

  dspipifcache [<interface>]

Where:

  <interface>]—atmX, where X is the unit number (optional)

dspipconntask—Display IP Connectivity task information (Debug command)

  dspipconntask

setipconndebug—set debug level for IP Connectivity task (Debug command)

  setipconndebug [debuglevel]

Where:

  [debuglevel]—Value specifying one or more of the following:
NO LOGGING: 0x0
TASK ERRORS: 0x1
TASK DEBUG: 0x2
ATM PROTOCOL: 0x4
TASK STARTUP: 0x8
TASK EVENTS: 0x10
SIGAPI: 0x20
ATMARP PROTOCOL: 0x40
TASK TIMERS: 0x80
INTERFACE CACHE: 0x100
SUBTASK EVENTS: 0x200
DISKDB EVENTS: 0x400
RAMDB EVENTS: 0x800
ALL LOGGING: 0xffffffff

Caveats

This section lists known anomalies in the Cisco WAN Manager 10.3 software and other associated software.

Known Anomalies in CWM 10.3 Software

This section lists known anomalies in CWM software grouped by functional unit.


Table 14: Known Anomalies in CWM 10.3
Bug ID Description

CSCds30458

Internally found severe defect:Open (O) SPVC connections showing incomplete in BPX-SES orion CMGUI shows complete SPVC as incomplete connections.

Description :All the SPVC connections in the network are showing as incomplete on CM-GUI. In fact the spvc connections seem to be not joined to each other in the database (user_connection table). There seem to be two endpoints for the connection in the atm_connection table.The remote end parameters in the table user_connection show as -1 (slot, port etc..)

On adding a connection the status of the connection shows fail on the GUI and user_connection where as the status of both the master and the slave end shows as OK in SES.

CSCds33585

Symptom: CWMGUI fail to add ATM-FR(abr1) connection when one end is in PXM1 card

Conditions: This will happen in new releases of PXM1 where it supports MCR.

Workaround: Can add the same type of connection from ConnProxy. From CMGUI, there is no workaround.

CSCds20299

Symptom: The CMGUI shows the master endpoint as the local endpoint where user has selected the slave endpoint as the local endpoint for viewing the connection list.

Conditions: This problem happens when the user selected starting node (i.e. local node) is not same as the remote node and the master endpoint is same as the remote endpoint.

Workaround: There is no workaround. User needs to traverse both the local endpoint and the remote endpoint to view all the connections terminating on the user selected node.

CSCds33627

Symptom: CWMGUI fails to modify remote endpoint parameters when local end is feeder and the remote end is the AXSM cards.

Conditions: CWMGUI fails to modify remote endpoint parameters when local end is feeder and the remote end is the AXSM cards. This happens for 2 segment hybrid connection.

Workaround: Modify the connection making the AXSM endpoint as the local endpoint and the feeder endpoint as the remote endpoint.

CSCds34696

Symptom: CMGUI shows wrong connection status for SPVC ATM-ATM connections.

Conditions: This happens intermittently. It happens for both AXSM-AXSM and BXM-BXM SPVC connections.

Workaround: No workaround. Making the connection down and up may resolve the problem.

CSCds34711

Symptom: CMGUI shows wrong connection status for SPVC ATM-ATM connections.

Conditions: This happens intermittently. It happens for both AXSM-AXSM and BXM-BXM SPVC connections. In this case, GUI shows incorrect values for status which is in the database.

Workaround: Apply REFRESH button.

CSCds34739

Symptom: CMGUI shows wrong connection status when a hybrid connection is set to DOWN and set to UP.

Conditions: It happens hybrid connections only.

Workaround: Apply REFRESH button.

CSCds29704

Symptom: CMGUI shows wrong multicast endpoint type in the main window when connections are added from different CWM or from the CLI.

Conditions: If the multicast connection is added from the same CWM, this problem does not happen.

Workaround: Apply REFRESH button.

CSCds33738

Symptom: SCM does not collect stats files from the secondary if the primary collector is shut down or not responding.

Conditions: If the Primary collector is operational and reachable but could not collect the stat files from the nodes, Secondary attempt to collect the stats files. However, if Primary collector is down, Secondary will not collect stats files. Same is true for the Tertiary collector.

Workaround: No workaround

CSCds30458

Symptom: CMGUI shows complete SPVC as incomplete connections.

Conditions: This happens intermittently.

Workaround: Do cold start.

Alarm Open Bugs

CSCds33469

Abstract: STG MIB does not contain traps 27551 and 27552

Description:

After installing CWM 10.3V on cwmlab8, the STG MIB stgsyslog.my does not contain the following traps:

  • stgSyslogIPRTLimiWarning # 27551

  • stgSyslogIPRTLimitExceeded #27552

The above traps are included in the 9.2.08 patch 16 stgsyslog.my mib file.

Connection Management Open Bugs

CSCds20299

Abstract: CMGUI shows master end as the local end.

Description:

Before CWM 10, all other CWM releases shows the local ends for the node we have selected. For example, if I select edgetx40 to view all PVCs on slot 1, CWM should show all SPVCs terminated on edgetx40 1.1 as the local ends.

However, CWM release 10 shows the master ends of the PVCs as the local end. It means that if I select edgetx40 1.1, the SPVCs terminated on 1.1 may show up under the local ends or the remote end. This makes searching for an SPVC very difficult.

CSCds28052

Connection status mismatch after the connection reroute.

Description:

Five connections were created using the CMGUI all of them are OK. Connection reroute was done on all the 5 connections. Connection went down for some time in CLI and came back to normal. All the connections are OK in CLI. CMGUI still shows all the connections as FAILED.

CSCds33627

Proxy - Unable to modify remote end parameter of AUSM-AXSM connection

Description:

1. Added AUSM - AXSM CBR1 hybrid connection

2. Tried to modify remote (AXSM side) PCR, it did not modify it. It was able to modify local side PCR.

Workaround:

1. While adding a connection add with values that are needed. (You can always delete and re-add the connection back) if it acceptable to the customer.

2. Instead of adding AUSM (feeder) to AXSM, always put AXSM in the local end and modify will go through fine. This should not affect the traffic etc.

CSCds33680

Connection Details on Failed Connection shows OK through Connection Management GUI

Description:

When connection details is done from Connection Management GUI for Failed connection, the window shows OK Status on Local and Remote end

Workaround:

None

CSCds34696

Databroker shows wrong status for connections in user_connection against switch

Description:

Status in User Connection table of CWM is inconsistent with the status shown for the same connection on CLI.

Workaround:

None. ATM connection Table shows correct State as compared to Switch

CSCds34711

CM GUI doesn't reflect correct status from User Connection in Database

Description:

Connection Manager CM GUI does not reflect correct status as shown in the user connection table.

Example:

Connection State in user connection table is 1 - OK but CM GUI shows the connection as Failed

Workaround:

None.

CSCds34739

Need to do Refresh in CM GUI to get correct status after Up/Dn Hybrid SPVC

Description:

From CM GUI user needs to do refresh after Up Conn/Down on the Hybrid Connection to get Connection Status

Workaround

Always do a refresh after changing a hybrid SPVC. After the refresh is done, the connection status is shown correctly.

CSCds29704

CMGUI displays ATM-ATM connection as ATM-ATM:CBR (-) also as ATM-ATM:ABR1 ( -NRM )

Description:

Add a bunch of connection at a time either using CMGUI or using proxy scripts but do not press apply or refresh button.

CMGUI displays ATM-ATM connection as ATM-ATM:CBR (-) also as ATM-ATM:ABR1 (-NRM)

Workaround:

Currently, any Normal connection should work fine. For Root/Leaf connection, if it is coming as event, user needs to refresh the connection in order to get the correct McType.

CSCds33788

In SCM GUI, the Delete Template doesn't work reliably if the node is in Enabled state

Description:

In SCM GUI (both stand-alone application and web-based), select a node in Enabled state (E) and do one of the following:

    1. Right click on the selected node

or

    2. Open the Options menu

Click on Delete Template and it does nothing. Either it should open the Delete Template Dialog window or the option of Delete Template should be disabled if it is not a design feature for a node in Enabled state.

Workaround:

None

Proxy Related Open Bugs

CSCdr98187

The ciscoMgmt MIB definitions missing in base MIB definition files

Description:

There are MIB definitions in sub-dir ~svplus/mibs/mibdir not included in any base files in ~svplus/mibs. MGX45 RTC definitions is one known example. We need ALL CISCO WAN product MIBs put in one pre-determined place.

Workaround:

None

Statistics Collection Manager (SCM) Related Open Bugs

CSCds33738

SCM Secondary doesn't collect files when Primary is Shut Down

Description:

When the Primary SCM machine is shut down or the connectivity between the Primary SCM and Switch is broken, the Secondary SCM doesn't collect the files.

Workaround:

None

Topology/Network Browser Open Bugs

CSCds34537

Topo Upgrade from 9.2 not opening correctly in CWM 10.3

Description:

When the topology is saved in 9.2 and files are converted using the Converter in ~svplus/java/bin/ in CWM 10.3 Machine, Topology is not opened correctly (as was saved in 9.2)

This happens only when user does upgrades from 9.2 to 10.3 including NWTopology config files. There are two problems:

a). Locations of nodes are not shown as they were when saved

b). Topology map shows nodes with very small icons

(a) is not service affecting. We see all the nodes but at different location

(b) is an existing CTT problem which is also not service affecting.

Workaround:

Remove the NWTopology save file from CWM directory. The user will see all nodes at default locations (as if user did not save locations)

CSCds32828

Two NW topology screens look different for the same CWM workstation

Description:

Two Topology GUIs look different in that one Topology GUI does not show one of the BPX-SES nodes and the trunks associated with it. The other one doesn't show three nodes and the AutoRoute trunks associated with them.

Workaround:

When this situation happens, you need to close and then restart the desktop.

CSCds33673

SNMP request failure causing SCT file association failure.

Symptom:

Proxy requests or SCT file association will be failed and make OOEMC stuck in the SNMP state when another internal SNMP operation happened before the first SNMP response is received and processed.

Conditions:

This proxy request or SCT file association (for a port) will trigger an SNMP operation. This operation will be done in a short period, but if, within this period, a trap is received that triggers another SNMP operation for the same port, then the internal state of this port can not be reset to IDLE. The SNMP request for this port object can not performed after this problem happens.

Workaround:

None

But it will not influence the other objects.

CSCds33586

Topology does not discover routers but the Network Browser shows it

Description:

When launching topology, it does not show any routers attached to the network, but the NWBrowser shows the routers under the feeder nodes.

Workaround:

None

CSCds33654

Deleting and adding node gives warning message

Description:

Testing topology by deleting and re-adding nodes from the network.

When deleting all the trunks that link the node to the gateway node, the node gets removed from the topology.

When the trunks are re-added, the following error message pops up on the console:

(   23558) 02:24:02 WARNING: [ParseTopoNodeMsg] node=devigx04 
netId.nodeId=1.9 LANIP=0xc0000000 NWIP=0xc0000000 status=0 nodeStatus=0 
nodeType=2 release=, model=8420
(   23558) 02:24:02 ERR: [ParseTopoNodeMsg]: topod:WARNING: Node 
'devigx04' not added to topology because of invalid IP 
address(192.0.0.0) or duplicate IP address. Please configure node with a 
valid IP address.
(   23558) 02:10:06 ERR: [ParseTopoNodeMsg]: topod:WARNING: Node 
'devigx05' not added to topology because of invalid IP 
address(192.0.0.0) or duplicate IP address. Please configure node with a 
valid IP address.

Workaround:

None. Despite the above the link 1 to the nodes are established:

 (   23558) 02:10:47 WARNING: <processAudAlm> Link1 to 
devigx05(172.29.57.57) in Network 2 is UP
 (   23558) 02:10:47 WARNING: <processAudAlm> Changed devigx05 node's 
mgmnt state in DB to LinkUP
 (   23558) 02:18:33 WARNING: <processAudAlm> Link1 to 
devigx04(172.29.57.56) in Network 2 is UP
 (   23558) 02:18:33 WARNING: <processAudAlm> Changed devigx04 node's 
mgmnt state in DB to LinkUP

CSCds33796

Draw in Connection Trace not functioning - NWTopology doesn't show a new window

Description:

The Draw button in the CMGUI->Diagnostics->Connection Trace does not function. It should either display the trace or the button needs to be disabled. The NWTopology doesn't show the Connection Trace.

Workaround:

None

Anomalies Resolved in CWM Release 10.3

This section lists anomalies resolved in CWM Release 10.3.


Table 15: Resolved Anomalies in CWM Release 10.3
Bug ID Description

Alarm Fixed Bugs

CSCds15349

GCOE:HPOV event messages are cryptic

Equipment Management Fixed Bugs

CSCdr96511

emsc and emsd core dumps

CSCds08518

Add Port fails on AXSM card on popeye13 because of node release population.

CSCds09574

Connection Reroute does not correctly populate DB with correct state.

CSCdr39402

CMGUI shows EndToEndType as PVC during modify for hybrid connection.

CSCdr79198

EM does not send a nonRoutingNodeStatus msg to topo when axis becomes unreachable

CSCdr90829

CM GUI->Diagnostic->Connection Down: does not reflect the change on the GUI

CSCdr90951
CSCdr45288

EMC needs to forward Service Module %Util information to databroker

CSCdr98333

rsc_part table populated incorrectly

CSCds00778

Delay in receiving traps while addition and deletion of connections (spvc)

CSCds02690

ooemc problems for adding resource partition

CSCds03480

OOEMC sends old request to switch even though proxy sends new request

CSCds09708

EM does not populate the max_svcc_vci correctly in database for popeye2

CSCds10708

CWM deletes router from topo on disabling Neb Disc on the port

CSCdr45288

VISM-ATM Connection per_util in user_connection table saved as 0 while set 100

CSCdr73054

node,card tables fields for BPX-SES needs to be populated more intuitively

CSCdr88250

GCOE: Inconsistency with how VPCs are displayed in Conn Mgr

CSCdr89857

ctrlr_status=-1 and ctrlr_loc=3 in controller table

CSCds05294

GCOE: Version field not updated correctly in Network Browser

CSCdr45741
CSCdr51873

SNMP proxy to add a connection reports success, dspchan shows Connection Down
Fix: Changed the SMIB parameter svConnMaxCost from the DEFVAL of 20000 to 65000.

CSCdr45905

Node sync up problem for redundant PXM cards

CSCdr71331

BXM-T3 card not visible in Equipment Viewer.

CSCdr76216

Port Proxy fails when adding a port.

CSCdr79194

Connection Subtype mismatch for ATMFRABRFS connection in the remote DB

CSCdr92287

EMSC coredump.

CSCdr94228

Manual node resync gave snmp timeout

Fix: Changed the SNMP timeout value.

CSCdr51854

OC48 backcard shows up as other or not at all in network browser. In the Network Browser the OC-48 card Back Card is either shown with nothing or as "Other."

CSCdr61516

When cwmftpd is killed, ooemc has problems in resyncing due to long timeout

CSCdp75072

No response from emd/ooemc after node resync.

CSCdr70382

Cannot delete the existing failed connection from CMGUI

CSCdr75594

apsEnable should not be part of DS3 line mib table for POPEYE 1

CSCdp44283

SV+CreateDb does not check whether dbaccess sessions are up or not.

CSCdp49544

rate_up and rate_down fields have values -1 in card table for AXSM card

CSCdp74694

EMD always sends two responses to sctDaemon for each card association request: one with valid data and the other with invalid (-1) card type. SctDaemon was able to process the valid response successfully, but the invalid response causes sctDaemon to raise exception.

CSCdr45741

SNMP proxy to add a connection reports success, dspchan shows Condn.

Workaround: None.

CSCdr48499

Inconsistencies between primary and secondary connections report in atm_connection table.

Workaround: None.

CSCdr49243

In 10.3E.SOl version of CWM once emsc dies, emsd does not restart emsc.

Workaround: None.

CSCdr50256

ooemc needs to populate icr for spvc in the qir field for spvc conns too.

For BXM PVC ABR.1 connection EM populates the ICR field in the qir column and cmserver picks the icr value from there. EM should populate the same field for icr in case of spvc too to be consistent.

Workaround: None.

CSCdr51541

Database shows -1 as back card type for PXM cards.

Workaround: None.

CSCdr51850

svmg2x05 primary slot is 8, but in REDUNDANTCARD table, db reports svmg2x05 primary slot is 7 instead of 8. There is no pxm card in slot 7.

Workaround: None.

CSCdr51892

When adding VISM-AUSM connection em is sending wrong endpoint type to databroker. The log file name is dbroker.log.chz1

Workaround: None.

CSCdr51958

Internally found severe defect: Assigned (A) after switch cc, cold start cwm, pri_slot in redundantcard still 7 instead 8.

Workaround: None.

CSCdr52321

Internally found severe defect: Assigned (A) rsc_part table: ingr_pctw, egr_pctbw, max_chans & min_chans don not match CLI.

Workaround: None.

CSCdr46624

Emd should send manageController to ooemc after ooemc restarts from crash.

Workaround: After ooemc crashes and restarts, emd sends a manageNode to ooemc which does not know the node id of the BPX node.

CSCds17532

ooemc coredump

CSCds17937

SCT ID association not reflected in the database

CSCds23989

Getting NodeResync coredump on MGX 8850

CSCdr90829

CM GUI->Diagnostic->Connection Down: does not reflect the change on the GUI

CSCds04958

snmp comm giving error while enabling stat

CSCds07880

qir,pir,mir is not converted properly hence their values are zero (atm-fr)

CSCds10708

CWM deletes router from topo on disabling Neb Disc on the port

CSCds10987

SLT: Second VSI controller not discovered by topology when add VSI on BPX

CSCds12842

NoderResync fails for slot 1 for 8230s and Slot 32 (for 8230 no. of slots=14)

CSCds27919

Discrepancy in user_conn counts for 10.3 / 9.2 CWM same network

CSCds19277

Need to change return value from 0 to -1 for FindNodeByName()

CSCds28832

ooemc does not clear all pending traps when it does a card resync

CSCds30703

Config Save not working for SES Controller from NW Topology

CSCds31405

FRSM connection segments from IGX don't show in database

CSCds31730

NW Browser, inconsistency in backcards shown

CSCds31579

For FRSM-HS1-B card Fr-Funi connections have CAC&Rate parm.-->Srv.Rate is -100

Connection Management Fixed Bugs

CSCdr73786

CWM - CMGUI Does not provide option to Add BME Connections.

CSCdr93085

While try to make connection RPM-FRSM2T3,getting error

CSCds06095

Alarm console not showing alarms

CSCds10820

Mismatch in the connection creation/Modification parameters on slave/master

CSCds12449

Error while creating ATM-ATM conn between r8230-1 and r8250-1.

CSCds14973

Databroker core dump during rollback due to invalid alarm updates.

CSCds16887

CWM ftpd Core dumped in Release 2 MGX 8850 SLT Network in B3

CSCdr70782

Range Checking is wrong for CIR, PCR etc in CMGUI

CSCdr81735

CMGUI should check defensively for invalid VPI (for Virtual port)

CSCdr86220

ModConn failed for ATMFR connection.

CSCdr95530

Range of MaxCost is from 0 to 0xffffffff

CSCdr96081

Refresh button does not glow when same conn. is deleted from different GUI

CSCdr96117

Connection addition shown twice in CWM GUI for MGX 1.1.30

CSCdr96320

DRL.dat has incorrect definition of atmEndPointICR/MCR

CSCdr98742

Cmserver/GUI problems for popeye2-popeye1 feeder

CSCdr99451

Cmserver does not show MBS,CDVT,SCR on AXSM side for ATM-RPM hybrid connection

CSCdr99456

Inconsistency in DRL for frEndPointChanServRate

CSCds00146

Modify connection failures for SPVC connections.

CSCds01779

GUI shows the wrong value of Channel for Frame Relay connections.

CSCds02742

Cmserver should send the port speed as PCR in request to cmgrd for CE endpoint

CSCds03547

CMGUI shows blank for ALM card for svigx01(IGX-8420).

CSCds04444

AddConn failed with error Value out of Range

CSCds04689

CM GUI: Unexpected behavior with connection descriptor filter

CSCds04830

Unable to modify RPM-FRSM2T3 connection

CSCds05760

Unable to add connections with default parameters.

CSCds06870

Incorrect Value of Egress Queue-->channel Service type for ATM-FR connection.

CSCdr93103

For ATM-ATM or ATM-FR ABR1 type of connections SCR0+1(cps) parameter is not user modifiable so this text entry box should be grey.

modify-->Edit-->Ingress UPC Parameters: SCR0+1(cps)

CSCds02956

Can't manually change node when attempting to add connection

CSCds09696

CMGUI doesnt have a Keyboard shortcut to open the View menu.

CSCdr70741

Unable to add 3-segment Data connection from CWM

CSCdr73786

CWM - CMGUI Does not provide option to Add BME Connections.

CSCdr82460

When node names are longer than 8 characters, SNMP proxies stop responding after a few hours.

CSCdr92869

Cold start of CWM drops SCT tables

CSCdr47118

Cmserver creates an exception when an ATM-CE/CE-ATM hybrid connection is added

CSCdr51863

Connection status not always accurately reflected in ConnManager.

Workaround:

None.

CSCdr55677

SPVC VP Conn can not be provisioned from CWM

CSCdr58767

ConnGui always displays NA/NA/NA/NA for all AXSM SPVCs (LocalStatus)

CSCdr70764

SNMP provisioning script failed after 507 connections added

CSCdr71011

CONNGUI port popup does not come up for ATM ports after switch yred

CSCdr71174

GCOE: Conn Mgr shows conn parameters defaults differently than on switch

CSCdr55558

sync-up trap 28075 received incorrect time-frame

CSCdr64670

Enable cell routing is wrong for Modify connection and for rt-vbr

CSCdr75557

ConnMgr, error No resource partition found when VpiVci tab is selected

CSCdr84141

Connection Manager allows selection of nodes from different networks.

CSCdr87307

ConnMgr GUI: Get 0 conn in Connection Retrieval window gives 1 connection

CSCdp31522

CMGUI has minor memory leak. If CMGUI is used for longtime for Connection Provisioning, it may used up lots of system memory.

Workaround: If this happens, please terminate CMGUI and restart it.

CSCdr53231

Databroker core dump on both primary and secondary CWM WS.

Workaround: None.

CSCdr42455

connmiss,count etc in tools directory are not then cwm10.0. /usr/users/svplus/tools directory does not have some tools in cwm10.0, which are there in cwm9.2 build.

Workaround: None.

CSCdr49615

ConnGui Modify conn does not bring up actual SCR value. When modifying an existing connection on AXSM, under CAC & Rate Parameters -> MCR(cps) displays default value NOT actual value on connection. Further switch labels this value as SCR not MCR which is confusing. Modifying pvc MCR value modifies SCR value in switch.

Workaround: To display accurate value of SCR in GUI, within 'Modify ATM Connection' it brings up SCT defaults. Best table to seek for BW parms in DB for AXSM spvcs Note Local and Remote SCR values in CLI for AXSM = 3. In atm_connection, there are mir, qir, pir, cir as well as r_pcr and r_mcr columns. For AXSM spvc, in comparison with switch CLI dspchan, it's difficult to see the parameter mappings. Another assumption is r_pcr is derived from PCR and cir = 12 is derived from SCR.

CSCdr50195

ConnMgr Hybrid Modify Failure while restoring the original value.

Workaround: Connection was added successfully through GUI between nmsbpx02.axis245.11.3.255.88 nmsbpx06.2.1.255.89 cbr1 hybrid. Change the PCR value to 51 of both sides. It was modified successfully. Change the value back to 50, and it responds with the error message "Original parameter is same as the modified one."

CSCdr50438

CM GUI refresh Button doesnt change color when Conn is added. When we try to add connection from CLI and verify that Conn in GUI, no response is received in the form of refresh becoming purple. In some cases refresh button becomes Red for Connection addition (It should be red if conn is deleted.) If Apply is selected, user receives the connection addition being populated in CM GUI.

Workaround: None.

CSCdr51527

Secondary CWM WS (qautra60), start CMGUI client, prompt failure dialog.

Workaround: None.

CSCdr51828

In connection manager GUI, when the port is selected, the value of bay is incremented by "1".

Workaround: None.

CSCdr51863

Connection status not always accurately reflected in ConnManager.

Workaround: None.

CSCdr51873

No similar method to specify no max routing cost for an SPVC (Popeye 2). Customer is running 10.1 FCS code with no patches. On popeye 2, a "-1" is used to specify no max routing cost for the connection. This value does not work on CWM. The default in ConnMgr appears to be 20000 which causes problems when 2+ PNNI links need to be traversed.

Workaround: Default value should be made higher or, better, allow a wildcard to specify no max routing cost occurring on the MGX 8850 Rel 2.0 switch.

CSCdr51625

Connection status not always accurately reflected in ConnManager.

Workaround: None.

CSCdr95874

CMGUI missing spvc end-points, incorrect statuses

CSCds10712

Unable to create SCT file from SCT Manager

CSCds12449

Error while creating atm-atm conn between r8230-1 and r8250-1

CSCds14259

Unable to modify AUSM endpoint & Util via GUI

CSCds26898

Cannot add ATM - CESM t3e3 connection

CSCds27387

Get error on attempt to modify FR-ATM ABRFS PVC via GUI

CSCdr70781

CWM not allowing deletion/modification of 3-segment voice connections

CSCdr95475

Line status inconsistent across component GUIs.

CSCds01828

Cancel button should not be there in Deleting Connection Pop up.

CSCds06972

Unable to create FR-FR (STDABR) connection (PCR,MCR,ICR should be >=CIR)

CSCds08749

CAC & Rate parameters->QIR does not change back to default value with default button.

CSCds09375

After successful modification, IBS value doesn't change

CSCds09608

Unable to modify CAC parameters in RPM-FR connection

CSCds10541

GCOE: Conn Mgr does not show accurate local/remote status

CSCds20299

CMGUI shows the master end as the local end

CSCds27890

CMGUI displays NPM cards as NPC for IGX 8420

CSCds27961

Connection trace not working for VP connections

CSCds28449

Conn-mgr does not allow modification of AT-FR conn from BPX-IGX

CSCds28927

Try enabling ECR enable option deactivates it instead of enabling it

CSCds30410

Err Msg Dialog on VISM-ATM states VCI 131-579 and should be 131-510

CSCds09615

Unable to modify std. ABR parameters

CSCds09760

In ABR1 connection of RPM-FRSM,channel service type displayed as VBR3-nrt

CSCds16617

Getting wrong value of burst size in RPM-RPM ABR connection

CSCds18582

Add ATFST connections not supported by CWM

CSCds19885

Connection Manager Network Browser displays IGX ARM card as []

CSCds26318

Test delay fails for downed DAX connection from proxy

CSCds28471

connmgr, modify of CE - CE connection the values mismatch with database

CSCds28847

CMGUI does not allow changes to the UPC enable parameter for PCR 3 segment ATM connections

CSCds29554

MCR value should be read-only for VBR PVC connection in CM GUI

CSCds29697

UPC Enable parameter cannot be disabled for an ABR1 PVC connection

CSCdr67175

CM-GUI, display inconsistent for NRT-VBR3 from NRT-VBR1 & NRT-VBR2

CSCdr70745

CMGUI behavior issue during negative testing

CSCds15570

GCOE: SCT Manager application is incorrectly named in main window

CSCds29637

EFCI Queue size unit not specified in CM GUI

CSCds30458

SPVC connections showing incomplete in BPX-SES

CSCds31225

equip-selector shows NULL FRSM cards

CSCds14259

Unable to modify AUSM endpoint & Util via GUI

CSCds33131

Foresight PIR keeps increasing for every modification of ABRFS PVC

CSCds29499

If the UPC is disabled UPC threshold should be non-editable

Config-Save Fixed Bugs

CSCds08409

Connection Trace for Non DAX Connection Fails.

CSCdr49457

Select any popeye2 node from Config Save dialog. Please note that Node passwd was greyed out. So when I select the Save push button, I get a warning dialog prompt "Node Password Not Specified." It was greyed out. The user can't enter a password.

Workaround: None.

CSCdr87912

GCOE: Save Config process hung up

Database Consistency Fixed Bugs

CSCdr94472

Insertion of Standby PMX card does not show logical slot 0

CSCds04427

bis_object has wrong parent address of feeder node

CSCds06926

Database PACKET_LINE table not populated

CSCds01097

PACKET_LINE table does not have entry for BPX having trunk with another BPX

CSCdr92051

VPI=-2 in Controller table

CSCdr94472

Insertion of Standby PMX card does not show logical slot 0

Download Fixed Bugs

CSCdp99676

SES image filename format is changed which causes the CWM download to fail

Installation Fixed Bugs

CSCds09756

Application cannot launch WingZ when run from menu

CSCdp56031

The Install Shield needs to generate a log file

CSCdr01845

The install script cleans the /tmp directory on the local host

CSCdr82401

GCOE: After installation, CWM 10.3P core will not start

CSCdp82966

The images/ipxbpx directory not created with latest build

CSCdr01845

The install script cleans the /tmp directory on the local host

CSCdr42587

ORBIX is core dumping with 10.3D.SOL for SPVC feeder testing.

Workaround: None.

OpenView Fixed Bugs

CSCdr10406

trap numbers 60371, 60372, and 60373 not received by CWM

CSCdk82706

isCisco and isNode capabilities for StrataCom switches should be true.

CSCdr51853

GCOE: No card insert or removal messages are seen by HPOV event browser

Proxy Fixed Bugs

CSCds03148

Unable to modify ATM-ATM connections through connection proxy.

CSCds06467

Unable to Query AUSM Ports via SNMP

CSCds07225

While adding ATM-FR connection Trunk avoidance type (-1) error is shown (ABR1)

CSCdr08300

Mod Conn fails with IBS/MBS range checking error for ATM-ATM PXM EndPoints

CSCdr71762

Able to add same resource partition multiple times

CSCdr90972

CMGRD needs to set the %Util in the databroker ilog interface correctly

CSCdr93087

CLP Tagging Enable should not be user-modifiable.

CSCdr94230

Checks need to be done for resource partitioning for AXSM in port proxy

CSCds02539

ConnProxy doesn't support RT-VBR for new AUSM cards.

CSCdr69416

Up/down/reroute features not implemented for SPVC, hybrid conns (ConnProxy)

CSCdr80855

ConnProxy - Does not log L3/L4 and no way to enable those

CSCdr86814

cwmRsrcPartTable, is missing the header description

CSCdr91307

ConnProxy doesn't work with VSVD on/no TRM default

CSCds03576

SV+ Service MIB needs to modify description for atmEndPointCDV

CSCds07738

ConnProxy returns frEndPointChanServRate object in 100s of bps.

CSCdr94321

Can't set Q parms on AUSM or BXM ports

CSCdr38335

SV+Service.mib for svCardNodeType = 18 not defined

CSCdr46612

CWM failed to pick up newly added and deleted connections

CSCdr56773

K functions have to be updated in ConnProxy

CSCdr56783

K functions have to be updated in Line Proxy

CSCdr75577

SV+Service.mib not fully updated

CSCdr90972

CMGRD needs to set the %Util in the databroker ilog interface correctly

CSCdr95897

Service MIB shows DEFVAL of 20000 for svConnMaxCost; should be 65535
See also CSCdr45741 and CSCdr51873 under Equipment Manager Fixed Bugs

CSCdr46612

One problem in databroker when deleting incomplete connections is that it always uses master endpoint as local end point. This may not be true for feeder segment. Correct implementation is to use terminated endpoint as local end point for feeder seg incomplete connection.

Workaround: None.

CSCds12453

AUSM port query returns incorrect values

CSCdr58223

SNMP GET of Error Desc fails with error

CSCds15873

CWM MIB names meaningless, No version info, or source control

CSCds16327

Connection shows max cost of -1 when no svConnMaxCost specified

CSCds22496

Creation of ATMlport on BPX/IGX fails

CSCds22504

Creation of ATMLport on AXIS/MGX using multiple SNMP setvalues fails

CSCds22517

Creation of CE-CE, CE-ATM with SNMP fails w/errors CAS parameter is not applicable

CSCds29748

Mod Con failure for UFM endpoint for MAX cases for MIR/PIR/QIR

CSCds30926

CM Proxy should report PIR, MIR, QIR as unmodifiable for non-fs connections

CSCds31294

Verification script fails

Reports Fixed Bugs

CSCdr74861

Network Report of Summary Report throws an error.

CSCdr74876

Port Traffic Summary Report when filtered with Node Name,gives an error

CSCds20494

GCOE: Summary Report does not display nodes in Network Report

Statistics Fixed Bugs

CSCdr90353

SCM Stats enabling/disabling fails if executed during Switchcc Redundancy

CSCds01747

SCM Collection Server Coredump

CSCds08418

SCM Collection Server core dump

CSCdr89779

SCM Default template values are different than those shown in Main SCM Window

CSCds00833

SCM does not enable Cell Rx Port stats

CSCds00955

SCM needs to modify dialog message when closing application.

CSCds06406

After node rebuild, the stats collection from SCM is not resumed

CSCds17377

All nodes failed to enable/disable, start/stop collecting if a node failed

CSCds17393

No Pri/Sec/Ter dropdown list available for editing with Template

CSCds17404

Primary/Secondary/Tertiary server names should be different and primary listed first, secondary listed second, tertiary listed last

CSCdr66229

No SCM Collection server found under SCM Root

CSCdr66728

PXM cards not listed under SCM GUI card family types for Popeye1 nodes

Description:

Under the SCM GUI, after a Popeye1 node was highlighted and then "Edit w/ default parameters" was selected to choose to enable the PXM stats, the card family drop down menu did not have the PXM card listed, only frsm_40 was listed. The node did have a PXM card in it.

CSCdr73710

Stats exception error during statistics enable.

CSCdr74299

SCM doesnt collect statistics and save statistics files to a directory and DB

CSCdr84683
CSCds01747

SCM Collection Server Core Dump

CSCdr89569

SCM GUI hangs indefinitely after cold start

CSCdp95911

In Statistics Collection Manager (SCM) Log window, all the statistics files are not sorted by name. They are sorted by node name. That is, all statistics files under first node are listed first, then the other files from second node and so on.

Workaround: Search for your node ID in the SCM LOg for information on your nodal statistics collection.

CSCdr20875

If multiple SCM GUIs are opened from one CWM, they do not show the same enable status for a node which is stats enabled from one GUI. In this release, the multiple SCM GUI feature should not be used.

Workaround: Do not use the multiple SCM GUI feature.

CSCdr47725

On a secondary workstation, rtm does not forward trap a message to ooemc. Node doesn't sync up on secondary workstation. core dump. If you do a psg ILMITopoc on qaultra60, there is no process for ILMITopoc. Stop CWM core, rtm also core dumps. Both core dump and log files are saved in qault63:/disk1/corefilesdir/cscdr47725.

Workaround: Do not use secondary workstation for statistics collection unless absolutely necessary. Do not stop CWM Core from menu to avoid rtm core dump.

CSCdr51023

Secondary CWM WS, emd did not start by watchdog. ooemc process won't start on secondary CWM WS.

Workaround: None.

CSCdr51045

STG process core dump once on secondary CWM workstation.

Workaround: None.

CSCdr53065

Topo server core dumped.

Workaround: None.

CSCdp66051

When opening the Desktop, it does not indicate on the top of the window which host it is running on. If a user has multiple displays open, it cannot be determined which desktop is from which host.

Workaround: Need to display hostname on top of all GUI windows.

CSCdr32319

Problems reported with starting CWM from client as any other user other than svplus. In sec-mgr log there are various errors (fail to add/save/corba communication failures). Maybe these are related. Also note they use NIS+ so users are not defined on local /etc/passwd file.

Workaround: Single occurence bug with NIS+ users only.

CSCdr50462

Network Browser shows card empty in Slot 8 svbpx04/svbpx03. There is no card in Slot 8, so it should not slot Slot 8, but it is showing Slot 8 (with Blank text); Database shows a card in Slot 8.

Workaround: Ensure all slot(s) indicated as containing a card actually contain card(s).

CSCdr51833

l_line, card_type and pnni_status are -1 in the PACKET_LINE table.

Workaround: Ensure-1 is correct in this field.

CSCdr51848

CWM node alarm status displayed incorrectly. When the node has a Standby PXM, CWM shows a Major alarm for this node. It would appear that CWM is not recognizing the Standby card. CiscoView also shows unknown in the standby card status. This can be proved by pulling the Standby PXM from the node. The node will show a major alarm and indicate there is a missing card, but CWM will go green and show no alarms on the node at all. As soon as the card is reinserted, CWM shows a major alarm and the node shows no alarm at all.

Workaround: Reinsert appropriate card(s) and confirm recognition.

CSCdr51854

OC48 backcard shows up as other or not at all in network browser. In the Network Browser the OC-48 card Back Card is either shown with nothing or as "Other."

Workaround: None.

CSCdr51859

Cosmetically the Network browser is showing numbers for the status of some features of lines on AXSM cards, this is not readable, as there is no indication as to what the numbers mean.

Workaround: None.

CSCdr52267

port, atm_ip_addr, lan_ip_addr and ctrlr_status field is -1 in controller table.

Workaround: None.

CSCds09231

SCM lost template after upgrade to 10.3T

CSCds27974

scmcollsvr dumping core in secondary and tertiary in P/S/T config. for SCM

CSCds29224

SCM Collection Server is core

CSCds06406

After node rebuild, the statistics collection from SCM is not resumed

CSCds09603

SCM control server exception on starting core

CSCds17404

Pri/Sec/Ter server names should be different and primary first, secondary second, tertiary last

CSCds21991

PhyLine should use 11(0,1,2) instead of 1(7,8,9)

CSCds25492

FTP password for statsdb host can not put into process.conf as plain text

CSCds26403

scmcollsvr warmstart info files should encrypt SNMP community string and FTP password

CSCds26820

SCM GUI shows node alarm differently than Topology (which matches switch)

CSCds27038

Error with the install_scm script

CSCds27628

Do not enable SES statistics if connection statistics are not selected

CSCds28652

SCM GUI: Template not reflected on the GUI along with the collection parameter values

CSCds28806

SCM GUI doesn't show Selected Statistic IDs in window even though statistics are enabled

CSCds30282

SCM Template can't save Peak Interval & Default Enable Statistics values

CSCdr76708

SCM GUI gives wrong message in status field (Node not discovered)

CSCds12949

Typo in SCM GUI

CSCds33141

SCM Collection Server Core dumped

Topology Fixed Bugs

CSCdr89156

NWbrowser shows Unknown for card name after reset

CSCdr93840

NWTOPOLOGY- node resync option does not work

CSCdr99292

Topology fails to discover feeder popeye1

CSCdr99360

Topology does not discover feeder on gateway node

CSCdr99485

Topod core dump

CSCds00234

CWM Gateway coredumps

CSCds00519

Topology: cnfname of feeder node shows new node added to parent node

CSCds01056

CWM Gateway coredump

CSCds04608

ILMI Topoc Core Dumped in MGX 8850 Release 2 SLT Network

CSCds07687

ILMITopoc dumped core

CSCds07890

CWM not discovering nodes at all

CSCdr65828

GCOE: Topology Map not updating alarms from the MGX

CSCdr99435

MGX 8850 Release2-MGX 8850 Release 1 feeder network, no rows in packet_line table

CSCds00050

Topology is not showing the feeder trunk deletion

CSCds00063

CWM shows wrong model numbers

CSCds06453

MGX 8850 Release 2 Nodes Not Greyed out in N/W Topology GUI.

CSCdp62255

topod core dump on svplusnw1a

CSCdr47394

CWM machine not syncing completely with PNNI network

Condition:

If the node's mode is -1.

Further Problem Description:

This problem occurred due to a big network. We queue up all the nodes to be discovered if the number of current threads is more than 5 (Configurable parameter). Once the threads are free, we started the discovery of the queued up nodes. At this point, we weren't cleaning up the queue. That is the reason the node was getting discovered continuously and ILMITopoc wasn't able to send the node messages to it's clients like rtm, emd...

CSCdr51868

GCOE: Topology map is not saved after selecting Save from File Menu

CSCdr55481

Failure to open Network Browser from CWM Desktop

Problem Description:

This problem occurred on a CWM workstation managing a BPX/MGX 8220/MGX 8850 Rel. 1 network, as well as on a CWM workstation with basically 8 MGX 8850 Rel. 2 PNNI nodes.

CSCdr63892

Network Topology does not show any trunks either in Integrated or Autoroute View.

CSCdr65344

topod cores occurring on legacy BPX/MGX 8220 network, no SV3 links

CSCdr75659

SNMP timeout for cwsp operation table causing node resync problem.

CSCdr82213

ILMI topoc coredump.

Condition:

CWM workstation running 10.3L Build managing a BPX/AXIS/MGX 8850 Release 1 network. There do not appear to be SV3 links on the BPX nodes

CSCdr89461

ILMITopoc did not receive IP address change trap 60007

Scenario:

1. Changed ip address from 172.29.57.220 to 172.29.57.221

2. Observed trap 60007 in rtm.log and ILMITopoc.log

3. The ipaddress got changed in NWTopology

4. Changed ipaddress again from 172.29.57.221 to 172.29.57.220

5. The trap was not observed in ILMITopoc.log, but it was observed in rtm.log

6. NWTopology did not update to show changed ipaddress

CSCdr91382

Change the implementation of Feeder Discovery

CSCdr99292

Topology fails to discover MGX 8850 Release 1 feeder to a MGX 8850 Release 2 node

Scenario:

1. network.conf has LAN IP of the MGX 8850 Release 2 node (svmg2x03) as gateway

2. NWTopology GUI does not show feeder node

3. but database is populating with feeder node info

Resolution: The MGX 8850 Release 1 feeders weren't displayed if the MGX 8850 Release 1 is connected to the gateway and the LAN IP is specified in gateway.

CSCds00234

CWMgateway coredumps

CSCds00519

Topology: cnfname of feeder node shows new node added to parent node

qault62 - CWM workstation

svmg2x05 - MGX 8850 Release 2 node

popfdr2 - MGX 8850 Release 1 feeder node

Scenario:

1. changed name of MGX 8850 Release 1 feeder node

popfdr2.1.7.PXM.a > cnfname popfdr21

popfdr21.1.7.PXM.a >

2. Topology shows two MGX 8850 Release 1 feeder nodes attached to parent node svmg2x05 (MGX 8850 Release 2 node)

- one named popfdr2

- other with changed name popfdr21 (same ip address)

3. database has new entry for this non-existing MGX 8850 Release 1 feeder node:

node_name

svmg2x04

svmg2x05

svmg2x03

popfdr1

svsp1

popfdr2

popfdr21

CSCdr51842

GCOE: Critical Alarm on node appears as Major Alarm in CWM

CSCdr61541

Feeder not shown on CWM CM and feeder name not updated

Description:

We added an IGX node n8b as feeder to BPX node n5a. The feeder is shown in Network topology using Display Shelf. However, it is not shown in the Start Node window in Connection Management.

However, the other feeder (axis, n2b) to n5a does show up in CM. Also we changed the feeder name from n8b to n8b_fd (using cnfname) and the new name is not updated in CWM. We delete the feeder and then add it back again. This time, there are two entries (the old n8b and the new names n8b_fd) in the DISPLAY SHELF window.

The displays are included below.

The network can be accessed through svplusn2.

n5a TN Cisco BPX 8620 9.3.1J June 8 2000 10:03 PST

TRK Type Current Line Alarm Status Other End

1.2 E3 Clear - OK n4a/1.1

2.2 T3 Clear - OK n4b/1.2

3.1 OC3 Clear - OK n5c/10.1

4.2 OC12 Clear - OK n4b/2.2

6.1 T3 Clear - OK n4b/4.1

6.2 T3 Clear - OK n8b(IGX 8400/AF)

6.3 T3 Clear - OK n2b(AXIS)

10.1 OC3 Clear - OK n3a/4.3

14.6.1 E3 Clear - OK n4b/11.1.1

14.6.2 E3 Clear - OK -

14.6.3 E3 Clear - OK -

14.6.4 E3 Clear - OK -

14.6.5 E3 Clear - OK -

14.6.6 E3 Clear - OK -

This Command: dsptrks

n8b TN Cisco IGX 8420 9.3.1J June 8 2000 10:03 PST

TRK Type Current Line Alarm Status Other End

15.5 T3/636 Clear - OK n5a(BPX 8620)

CSCdr63695

CWM-CWM communication failed to update node_info and user_conn_desc tables

Description:

This problem is produced using three CWM's. After shutting down the primary, one of the secondary nodes became the primary. Add a few nodes and conn descriptors. Restarted another secondary (which was the primary before shutting down). This secondary CWM does not get all the nodes in node_info table and all the records in user_conn_desc table.

CSCdr64893

VSI PArtition from Topology does not show the info of the resources

CSCdr71161

GCOE: Card removal/insertion with SPVC configured does not change topology

Description:

Using CWM 10.1 and MGX 8850 2.0.01 code. After configuring a line, port, partition and an SPVC on a card, remove the card. HPOV sees the card removal and shows a VP/VC failure as a major alarm, but there is NO change in the network topology. It was still showing as green.

CSCdr74238

Trunk Status not updated in Network Topology GUI.

Description:

Down a trunk using dnpnport command through CLI. The RTM receives trap and trunk goes into alarm in the Topology GUI.

Bring up the trunk. The RTM receives link up trap but the Topology GUI does not update status of alarm.

CSCdr74486

IP address change not displayed in Network Topology GUI.

Description:

Change the Network IP address on the switch to a non reachable IP. The new IP address is displayed in the Topology GUI.

Change the IP address back to a valid reachable IP address.

The Topology GUI does not get updated. The node is reachable by selecting the Admin option from the Topology GUI using the valid Network IP address.

CSCdr75512

Feeder nodes shown as clear on NWTopology though they are in major/minor alarm

CSCdr77881

IPX feeder nodes shown as unknown type in Network Topology GUI, IPX routing nodes shown as BPX

Description:

While testing CWM 10.3P (Patch 2) on siyer60 for 9.1/9.2 networks, found that routing IPX nodes are being shown as "BPX", when you do a "Display Shelf" on that node. Also, IPX feeder nodes are shown as "Unknown1" type when you do a "Display Shelf" on its parent routing node.

CSCdr83858

Topod does not send network prefix information to databroker

Description:

Topod does not send the network prefix information to databroker in the new node message.

Resolution:

Linktopoc was sending the node prefix to topod. Topod, while instantiating a new node from the NodeMsg, was not accounting for the node prefix info in the Node Message.

CSCdr84420

Resetting the AXSM card fails to modify Trunk Status in Topology GUI.

Description:

CWM Qault62.

Build: 10.3 P Patch 6, OOEMV Patch 10

Popeye2: svmg2x03.

Image version:

Image Type Shelf Type Card Type Version Built On

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

Runtime MGX PXM45 2.0(228)A1 Jul 7 2000, 04:08:16

Boot MGX PXM45 2.0(210)A1 -

Operation:

Reset AXSM card with trunks configured. The trunk goes into alarm and displays as Red. The card resets and becomes administratively and operationally active. The trunk becomes active again. The Network Topology GUI and the Network Browser do not update the Trunk Status. The trunk is displayed in Red instead of Green.

CSCdr95542

ILMITopoc needs to handle line traps 60101 and 60102

60101 indicates SONET line is activated and 60102 indicates SONET line is inactivated (down).

CSCds00063

CWM shows wrong model numbers

Scenario:

CWM is showing the wrong model numbers

The CWM database is showing the following:

SQL: New Run Modify Use-editor Output Choose Save Info Drop Exit

Run the current SQL statements.

----------------------- stratacom@qault62 ------ Press CTRL-W for Help --------

node_name alarm_state model

svmg2x04 4 8850

svmg2x05 4 8850

svmg2x03 4 8850

popfdr1 2 8230

popfdr2 1 8850

svsp1 1 8230

But the switch shows the nodes as:

popfdr1 8850

popfdr2 8850

svsp1 8230

CSCdr30533

Physical line display options on NWTopology is not implemented in CWM 10.2.

Workaround: None.

CSCdr49493

Network Topo window, Help->On Icon displays nothing

Symptom:

From Network Topology Window. Help->On Icon... displays nothing. It should display a window mapping icons to Cisco switches.

Resolution:

Now when the user clicks on the Help -> On Icon, a dialog box displays all the legend of icons used in CWM Topology.

CSCdr51238

Linktopoc should retry for node prefix in case of SNMP failure

Description:

Linktopoc gets the node prefix for SES nodes (controllers) through a SNMP get operation. This SNMP operation may fail due to various reasons. Linktopoc does not retry for node prefix again in such cases.

CSCdr56625

RTM doesn't handle trap 70009

CSCdr73191

ILMITopoc generates lots of node and trunk messages during initial discovery

Description:

For a network with 5 nodes and 10 trunks, ILMITopoc generates 10 node messages and 40 trunk messages.

Workaround:

None. The message generation has been optimized to make sure that number of redundant messages are minimized. However, a network message may still contain an add as well as a mod message from the same node. This is specially true for the seed nodes. There are no duplicate messages for trunks. The duplicate node messages are present only during initial discovery and there are no redundant messages during resync.

CSCdr76222

Random messages on the screen

CSCdr79140

NWTopology does not receive physicalLineBitmap message

Description:

NWTopology always receives physicalLineBitmap field as 0 from TopoServer in TopologyTrunkMessage, no matter what type of trunk. This has been affected the implementation of displayPhysicalLine feature in NWTopology

CSCdr82942

Topod sends unnecessary messages to snmpcomm

Symptom:

nodeInfo messages were being sent to client based on node alarms.

Workaround: None.This has been suppressed.

CSCdr15406

Need to implement Audible Alarm functions on NWTopology

Workaround: None. Audible Alarm now is implemented in 10.3

CSCdr63475

Cannot bring up CWM 10 after install

Description:

After CWM 10.3L install informix is not running. After re-boot CWM will not come up.

cwmlab400% raw_rg -D stratacom -t

raw_rg: open database error -329

Other informix commands work fine, dbaccess, onstat etc.

Workaround:

None. Fixed in 10.3M.

CSCdr70677

Security rights incorrectly assigned to new user created in Security Manager.

Description:

Create a new user eg: groy using SM GUI.

Assign new user sec. profile with all rights to N/w topology and no other rights. Create a new unix account for user groy in svplus group.

Login to CWM desktop as new user "groy".

The user is allowed access to all applications from "apps" tool bar.

The Icons are however greyed out

Workaround:

None.

CSCdr77572

topod core dumps at the startup for secondary nodes in CWM-CWM gateway

Description:

1. Started core at qault64 (Primary in CWM-CWM gateway)

2. Started core at nmult61 (Secondary priority-1)

3. scmctrlsvr dumps core at the nmult61 i.e the secondary node.

Workaround:

None. Fixed in 10.3R.

CSCdr90661

SCT Manager not in sync with switches

Description:

After changing several SCT parameters and downloading to the switch, a different service type (UBR-1) was changed instead of the intended ABR service type. There appears to be a major disconnect between the CWM SCT and the switch SCT. Output from dspportsct follows. Also issues below with the usage of CWM SCT Manager must be addressed.

I disabled UPC_ENB for ABR, switch shows UBR.1 being disabled.

dspportsct gen 1

+----------------------------------------------------------------------

Service Class Template [3] : General Parameters

+----------------------------------------------------------------------

| SERV-TYPE | COSB_NUM | CAC_TYPE | UPC_ENB | CLP-SELEC | GCRA-1

+----------------------------------------------------------------------

| UBR.1 | 00000006 | LCN_CAC |DISABLED | 000000003 |

DISCARD

| UBR.2 | 00000006 | LCN_CAC |GCRA1-ENB | 000000003 | DSCD/SET-

CLP

| ABR | 00000007 | ECAC- A |GCRA1-ENB | 000000003 | DSCD/SET-

CLP

| CBR.2 | 00000003 | ECAC- A |DISABLED | 000000001 |

DISCARD

| CBR.3 | 00000003 | ECAC- A |DISABLED | 000000001 | DSCD/SET-

CLP

1. CWM SCTs are referred to as INGRESS and EGRESS, switch refers to them as CARD and PORT.

2. CWM SCT defaults[0] do not contain the same information as in SCT-ID 2 and 3 supplied with the switch.

3. CWM SCT only contains samples with policing turned on. There is no SCT with policing turned off as in switch SCT-ID 3.

4. Once a new SCT is created, saved, and downloaded to a switch, the same SCT cannot be changed. A new SCT file must be created. This file also has its ID incremented by one. A minor change created SCT-ID 2. A subsequent change created SCT-ID 3.

5. After creating SCT-ID 2, a download to the switch did not prompt that it was overwriting the current SCT in use.

Workaround:

None. SCT Manager now maps to switch SCT

CSCdr90325

Configurator GUI adds a node with blank IP address field

Description:

When you try to add a node with blank IP address, it will take it for the first time. The second time it gives a error message "Node with IP address already exists"

Workaround:

None. This bug has been fixed by checking at a initial state if the IP address field is blank. If so, a warning is displayed prompting the user to enter a IP address.

CSCdr29839

When a node is deleted and added again via CWM Configurator application, the node shows an error dialog box, but the operation is successful. Ignore this error dialog.

Workaround: None.

CSCdr30533

Physical line display options on NWTopology is not implemented in CWM 10.2.

Workaround: None.

CSCdp58265

The background images setting on JNWTopology is slow when in zoom mode.
Workaround: do not load images when in zoom mode.

CSCds13353

Toposerver core dumped

CSCds15501

TopoServer core dump on svnms 1

CSCds15985

Unable to start desktop

CSCds18353

Handle trunks with loop backs

CSCds22305

CiscoView does not come up from CWM client

Description:

No CiscoView for CWM client SW installed on workstation. Accessing secondary workstation as user svplus or other, same result.

Workaround: None.

CSCds23674

The 'vnd' process has had a core dump on qault62

CSCds25044

Topology shows node svmg2x03 in unreachable state

CSCdp66051

Desktop does not display which host it is running on

CSCdr82203

GCOE: CWM cannot change the SNMP community strings

CSCds20531

GCOE: Topology save does not work, nodes get scrambled

CSCds26707

Upgrade, CWM 10.2 to 10.3 - 10.3 does not discover all the routers as 10.2

CSCds28287

The channel up trap 60308 not handled by RTM

CSCdp13703

Topology map of Italy does not include Sicily and Sardinia

CSCdr77154

No traps for ADD/DEL of trunks/nodes

CSCdr79064

View->Background->Clear Image option not working on the Network Topology GUI

Description:

On the Network Topology GUI, once a background image is selected, the background cannot be cleared by selecting the "Clear Image" option.

However, another image can be selected to replace the existing image.

Fix:

Changes have been made to how images are implemented. These modifications cleared the issue.

CSCds23252

Print to file does not save complete topology

CSCds26012

Showing IP addresses causes nodes to have incorrect size in invisible tabs

CSCds26087

Message Link0 to popeye10.popeye18 in network2 is down

CSCds29555

MAP Image directory not set to default

CSCdp58265

Setting image in background locks the Network Topology window and grays it out

CSCdp62171

Network Topology, background image does not stretch to fit the window size.

CSCdr65748

Topology - View -> Options shows inconsistency

CSCds12691

Improper title in the Network Topology GUI

Description:

Click View -> Overview Window to open the Overview Dialog. The title of the Overview Dialog is presently "Dialog" which should be changed to "Overview Dialog" or something which is less confusing.

Fix:

Correct title now displays.

CSCds16322

CWM 10 Desktop Topology map interface is unusable in customer network

Description:

The CWM GUI interface has been re-designed to bring up a topology map automatically at startup. In 9.2 this was not the case. In larger production networks, the amount of time for the topology to be graphically rendered for each Desktop is indeterminate.

Fixed in 10.3.

CSCds31542

When a wrong table name is specified usertblDbTool uploads all tables

CSCds30548

Node name not displayed in Warning message in Config Save.

CSCds14188

CWM Administration option is always disabled

Documentation Resolved Bugs

CSCdr72431
CSCdr72451
CSCdr72463
CSCdr72472
CSCdr72480

GCOE: CWM 10.1 Installation Documentation Errors

Description:

The following URL contained several errors:

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

CWM Installation, Release 10.1

Workaround:

None. All resolved in 10.3 CWM Installation, which replaces 10.1.

CSCdr72514
CSCdr72530
CSCdr72536
CSCdr72547
CSCdr72556

GCOE: CWM 10.2 Installation Documentation Errors

Description:

The following URL contained several errors:

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

CWM Installation, Release 10.2

Workaround:

None. All resolved in 10.3 CWM Installation, which replaces 10.2.

CSCdp99736

DBSchema doc and NWBrowser change required for mode value 4 in node table

Description:

1. As per DB Schema doc in node table mode can be 0,1,2,3. When axis245 was removed from the n/w and added back to n/w. Mode for it was 4. This is the new value added for "partial" sync states. So DB Schema doc should be updated for it.

2. NWBrowser matched this 4 to UNKNOWN, that should be also changed for it.

Workaround:

None. This bug has been fixed in the 10.3 DB Schema doc.

CSCdr71344

CWM 10.2 User docs do not include Security Manager

Description:

CWM 10.2 user documentation does not include a section on Security Manager.

Workaround:

None. A section on Security Manager has been added in 10.3 CWM User's Guide, which replaces 10.2 CWM User's and Operations manuals.

CSCdr81904

Description:

CWM 10.3p and 2.0.01 code on the MGX 8850 was used. Customer's CWM setup was out-of-band-mgmt.

An entry in the route table was sending 10.0.0.0 addresses to the atm0 interface. This is apparently caused by the fact that the atm0 interface is configured to be the same IP address as the lnPci0 address and that the atm0 interface came up before the ethernet interface. At this time, only the lnPci0 interface is being discovered.

Workaround:

The correct out-of-band-mgmt workaround setup requires two different IP addresses on the atm0 and lnPci0 interface with static routes set up in the CWM workstation. Documented in 10.3 release note.

CSCdr97546

Wrong specification for Refresh button on CMGUI frontend functional spec.

Description:

The functionality of the REFRESH button on the CM GUI mismatches with that written in the functional specification for the CMGUI frontend. The functionality includes the behavior of the REFRESH button at the time of addition or deletion of connections as well as loss of a connection-alarm-status-change.

Workaround:

None. The document has been updated to explain in detail the Refresh Button behavior for various cases

CSCdr52545

Upgrade: missing point in Func. Spec. on commentc restoration.

Description:

Functional Spec. (CWM Upgrade to 10.0) needs to specify the following in the "2.1.4 Backup and restore the commentc field in the various tables of CWM" section:

-Run the UpdateComment.sh scripts right after the Upgrade Installation is done, and before running CWM core process.

Workaround:

None. The document has been updated.

CSCdr49472

Orbix port numbers needs to be release noted and documented

Description:

CWM uses the following 'fixed' port numbers for the server processes and these ports could conflict with something that is already using these tcp port numbers.

The following needs to be documented and release noted:

    1. CWM uses the following port numbers

    2. If a conflict of tcp port numbers is encountered, how to manually assign the CWM server process with a different tcp port number.

Processes and the tcp port number it uses:

 Name     Marker  Code    Comms   Port    Launch  PerClient?      OS-pid
 
------------------------------------------------------------------------
TopoServer *       cdr     tcp    5558    manual  ---             15359
 CmServer   *      cdr     tcp    5555    manual  ---             15599
 GenericServer *   cdr     tcp    5559    manual  ---             15281
 LogServer   *     cdr     tcp    5556    manual  ---             15243
 CWMGateway  *     cdr     tcp    5557    manual  ---             15233

Fix:

Solution added to 10.3 release note

CSCdr78781

GCOE: Security Manager cannot addnewusers (documentation)

Description:

CWM 10.2 user documentation was incorrect on adding new users to Security Manager.

Workaround:

None. The information on adding new users to Security Manager has been corrected in 10.3 CWM User's Guide, which replaces 10.2 CWM User's and Operations manuals.

CSCdr88258

GCOE: Documentation is missing SCT manager info

Description:

CWM 10.2 user documentation does not include a section on SCT Manager.

Workaround:

None. A section on SCT Manager has been added in 10.3 CWM User's Guide, which replaces 10.2 CWM User's and Operations manuals.

CSCds14242

CWM 10.3 topology configurator is not documented

Description:

There is no documentation for CWM10.x topology configurator When configuring IPFR stand alone network. The prior 9.2 documentation cannot be referenced since the CWM configuration GUI has been significantly changed.

Workaround:

None. Fixed in 10.3 CWM User's Guide

CSCds15790

rpm_connection.peak/average are saved in kbps NOT cps as stated in schema

Description:

9.2 and 10.3 DB schema states rpm_connection.average and peak are in cells per second. It is stored as kb per seconds in 9.2 and 10.3.

Workaround:

None. Fixed in 10.3 Database Interface Guide

CSCdr87570

GCOE: Missing Info for Service Class Template GUI

Description:

CWM 10.2 user documentation does not include a section on SCT Manager.

Workaround:

None. A section on SCT Manager has been added in 10.3 CWM User's Guide, which replaces 10.2 CWM User's and Operations manuals.

CSCdr90131

db schema user_connection table doc error

Description:

10.3 DB schema defines following field

user_connection.controller_type

actual field appears to be

user_connection.end_to_end_type

Workaround:

None. Fixed in 10.3 Database Interface Guide

CSCds12224

GCOE:SCM doc errors

Description:

The following statements seem incorrect

Collection Period

Stated default is 60

(Actual is set to 15)

Time-Out Period

Stated default is one minute

(Actual is set to 120)

Bucket Interval

Stated default is 60

(Actual is set to 15)

Number of Retries

Stated default is 1

(Actual is set to 3)

The above was taken from a fresh CWM 10.3T install where these parameters were not modified.

It does not state anywhere in this doc if the Statistics Collection Manager GUI should be opened or not for the CWM to collect statistics. CWM 9.2 required the GUI to be launched to collect statistics.

Workaround:

None. Fixed in 10.3 CWM User's Guide

Upgrade Resolved Bugs

CSCdr70002

Failed to upgrade from 9.1 SV+ to 10.3M CWM

Description:

Installed 10.3M.SOl CWM in upgrade mode from 9.1.10 Patch 14

Install failed with exception.

No nodes.conf and *.sm files under config directory in 9.1.

Workaround:

None. 9.1 did not have a nodes.conf file. The installation has been changed so that the node table is used and not the nodes.conf file to populate the node_info table in the upgraded machine.

CSCdr74759

Upgrade install from 10.1 to 10.3 hangs while create/configure database

Description:

Installed 10.1.SOL image. start core and sync-up database. stop core and install 10.3P.SOL in upgrade mode from 10.x. While creating and configuring database install window hangs.

Workaround:

None.

Please refer to the MGX 8850 Release 2.0.10 release note for a complete listing of all known MGX 8850 Release 2.0.10 anomalies.

Known Anomalies in CWM 10.2 Software

This section lists known anomalies in the 10.2 release of CWM software grouped by functional unit.


Table 16: Known Anomalies in CWM 10.2
Bug ID Description

Equipment Management Open Bugs

CSCdp75072

No response from emd/ooemc after node resync.

CSCdr70382

Cannot delete the existing failed connection from CMGUI

CSCdr75594

apsEnable should not be part of DS3 line mib table for POPEYE 1

CSCdp44283

SV+CreateDb does not check whether dbaccess sessions are up or not.

CSCdp49544

rate_up and rate_down fields have values -1 in card table for AXSM card

CSCdp74694

EMD always sends two responses to sctDaemon for each card association request: one with valid data and the other with invalid (-1) card type. SctDaemon was able to process the valid response successfully, but the invalid response causes sctDaemon to raise exception.

CSCdr45741

SNMP proxy to add a connection reports success, dspchan shows Condn.

Workaround: None.

CSCdr48499

Inconsistencies between primary and secondary connections report in atm_connection table.

Workaround: None.

CSCdr49243

In 10.3E.SOl version of CWM once emsc dies, emsd does not restart emsc.

Workaround: None.

CSCdr50256

ooemc needs to populate icr for spvc in the qir field for spvc conns too.

For BXM PVC ABR.1 connection EM populates the ICR field in the qir column and cmserver picks the icr value from there. EM should populate the same field for icr in case of spvc too to be consistent.

Workaround: None.

CSCdr51541

Database shows -1 as back card type for PXM cards.

Workaround: None.

CSCdr51850

svmg2x05 primary slot is 8, but in REDUNDANTCARD table, db reports svmg2x05 primary slot is 7 instead of 8. There is no pxm card in slot 7.

Workaround: None.

CSCdr51892

When adding VISM-AUSM connection em is sending wrong endpoint type to databroker. The log file name is dbroker.log.chz1

Workaround: None.

CSCdr51958

Internally found severe defect: Assigned (A) after switch cc, cold start cwm, pri_slot in redundantcard still 7 instead 8.

Workaround: None.

CSCdr52321

Internally found severe defect: Assigned (A) rsc_part table: ingr_pctw, egr_pctbw, max_chans & min_chans don not match CLI.

Workaround: None.

CSCdr46624

Emd should send manageController to ooemc after ooemc restarts from crash.

Workaround: After ooemc crashes and restarts, emd sends a manageNode to ooemc which does not know the node id of the BPX node.

Connection Management Open Bugs

CSCdp31522

CMGUI has minor memory leak. If CMGUI is used for longtime for Connection Provisioning, it may used up lots of system memory.

Workaround: If this happens, please terminate CMGUI and restart it.

CSCdr53231

Databroker core dump on both primary and secondary CWM WS.

Workaround: None.

CSCdr42455

connmiss,count etc in tools directory are not then cwm10.0. /usr/users/svplus/tools directory does not have some tools in cwm10.0, which are there in cwm9.2 build.

Workaround: None.

CSCdr49615

ConnGui Modify conn does not bring up actual SCR value. When modifying an existing connection on AXSM, under CAC & Rate Parameters -> MCR(cps) displays default value NOT actual value on connection. Further switch labels this value as SCR not MCR which is confusing. Modifying pvc MCR value modifies SCR value in switch.

Workaround: To display accurate value of SCR in GUI, within 'Modify ATM Connection' it brings up SCT defaults. Best table to seek for BW parms in DB for AXSM spvcs Note Local and Remote SCR values in CLI for AXSM = 3. In atm_connection, there are mir, qir, pir, cir as well as r_pcr and r_mcr columns. For AXSM spvc, in comparison with switch CLI dspchan, it's difficult to see the parameter mappings. Another assumption is r_pcr is derived from PCR and cir = 12 is derived from SCR.

CSCdr50195

ConnMgr Hybrid Modify Failure while restoring the original value.

Workaround: Connection was added successfully through GUI between nmsbpx02.axis245.11.3.255.88 nmsbpx06.2.1.255.89 cbr1 hybrid. Change the PCR value to 51 of both sides. It was modified successfully. Change the value back to 50, and it responds with the error message "Original parameter is same as the modified one."

CSCdr50438

CM GUI refresh Button doesnt change color when Conn is added. When we try to add connection from CLI and verify that Conn in GUI, no response is received in the form of refresh becoming purple. In some cases refresh button becomes Red for Connection addition (It should be red if conn is deleted.) If Apply is selected, user receives the connection addition being populated in CM GUI.

Workaround: None.

CSCdr51527

Secondary CWM WS (qautra60), start CMGUI client, prompt failure dialog.

Workaround: None.

CSCdr51828

In connection manager GUI, when the port is selected, the value of bay is incremented by "1".

Workaround: None.

CSCdr51863

Connection status not always accurately reflected in ConnManager.

Workaround: None.

CSCdr51873

No similar method to specify no max routing cost for an SPVC (Popeye 2). Customer is running 10.1 FCS code with no patches. On popeye 2, a "-1" is used to specify no max routing cost for the connection. This value does not work on CWM. The default in ConnMgr appears to be 20000 which causes problems when 2+ PNNI links need to be traversed.

Workaround: Default value should be made higher or, better, allow a wildcard to specify no max routing cost occurring on the MGX 8850 Rel 2.0 switch.

CSCdr51625

Connection status not always accurately reflected in ConnManager.

Workaround: None.

Config Save/Restore Related Open Bugs

CSCdr49457

Config Save for MGX8850 prompted for password but the node password dialog was greyed out

Description:

Select any popeye2 node from Config Save dialog. Please note that Node passwd was greyed out. So when I select the Save push button, I get a warning dialog prompt "Node Password Not Specified." It was greyed out. The user can't enter a password.

Workaround: None.

Statistics Collection Manager (SCM) Related Open Bugs

CSCdp95911

In Statistics Collection Manager (SCM) Log window, all the statistics files are not sorted by name. They are sorted by node name. That is, all statistics files under first node are listed first, then the other files from second node and so on.

Workaround: Search for your node ID in the SCM LOg for information on your nodal statistics collection.

CSCdr20875

If multiple SCM GUIs are opened from one CWM, they do not show the same enable status for a node which is stats enabled from one GUI. In this release, the multiple SCM GUI feature should not be used.

Workaround: Do not use the multiple SCM GUI feature.

CSCdr47725

On a secondary workstation, rtm does not forward trap a message to ooemc. Node doesn't sync up on secondary workstation. core dump. If you do a psg ILMITopoc on qaultra60, there is no process for ILMITopoc. Stop CWM core, rtm also core dumps. Both core dump and log files are saved in qault63:/disk1/corefilesdir/cscdr47725.

Workaround: Do not use secondary workstation for statistics collection unless absolutely necessary. Do not stop CWM Core from menu to avoid rtm core dump.

CSCdr51023

Secondary CWM WS, emd did not start by watchdog. ooemc process won't start on secondary CWM WS.

Workaround: None.

CSCdr51045

STG process core dump once on secondary CWM workstation.

Workaround: None.

CSCdr53065

Topo server core dumped.

Workaround: None.

CSCdp66051

When opening the Desktop, it does not indicate on the top of the window which host it is running on. If a user has multiple displays open, it cannot be determined which desktop is from which host.

Workaround: Need to display hostname on top of all GUI windows.

CSCdr32319

Problems reported with starting CWM from client as any other user other than svplus. In sec-mgr log there are various errors (fail to add/save/corba communication failures). Maybe these are related. Also note they use NIS+ so users are not defined on local /etc/passwd file.

Workaround: Single occurence bug with NIS+ users only.

CSCdr50462

Network Browser shows card empty in Slot 8 svbpx04/svbpx03. There is no card in Slot 8, so it should not slot Slot 8, but it is showing Slot 8 (with Blank text); Database shows a card in Slot 8.

Workaround: Ensure all slot(s) indicated as containing a card actually contain card(s).

CSCdr51833

l_line, card_type and pnni_status are -1 in the PACKET_LINE table.

Workaround: Ensure-1 is correct in this field.

CSCdr51848

CWM node alarm status displayed incorrectly. When the node has a Standby PXM, CWM shows a Major alarm for this node. It would appear that CWM is not recognizing the Standby card. CiscoView also shows unknown in the standby card status. This can be proved by pulling the Standby PXM from the node. The node will show a major alarm and indicate there is a missing card, but CWM will go green and show no alarms on the node at all. As soon as the card is reinserted, CWM shows a major alarm and the node shows no alarm at all.

Workaround: Reinsert appropriate card(s) and confirm recognition.

CSCdr51854

OC48 backcard shows up as other or not at all in network browser. In the Network Browser the OC-48 card Back Card is either shown with nothing or as "Other."

Workaround: None.

CSCdr51859

Cosmetically the Network browser is showing numbers for the status of some features of lines on AXSM cards, this is not readable, as there is no indication as to what the numbers mean.

Workaround: None.

CSCdr52267

port, atm_ip_addr, lan_ip_addr and ctrlr_status field is -1 in controller table.

Workaround: None.

Topology/Network Browser Open Bugs

CSCdr29839

When a node is deleted and added again via CWM Configurator application, the node shows an error dialog box, but the operation is successful. Ignore this error dialog.

Workaround: None.

CSCdr30533

Physical line display options on NWTopology is not implemented in CWM 10.2.

Workaround: None.

CSCdp58265

The background images setting on JNWTopology is slow when in zoom mode.
Workaround: do not load images when in zoom mode.

Install Open Bugs

CSCdr42587

ORBIX is core dumping with 10.3D.SOL for SPVC feeder testing.

Workaround: None.

Proxy Open Bugs

CSCdr46612

One problem in databroker when deleting incomplete connections is that it always uses master endpoint as local end point. This may not be true for feeder segment. Correct implementation is to use terminated endpoint as local end point for feeder seg incomplete connection.

Workaround: None.

Anomalies Resolved in CWM Release 10.2

This section lists anomalies resolved in CWM Release 10.2.


Table 17: Resolved Anomalies in CWM Release 10.2
Bug ID Description

CSCdr28636

Occasionally the node does not respond to SNMP requests causing SNMP timeouts. This condition might prevent synchronization between CWM and the node.
Workaround: Reset the PXM45 card.

CSCdr31278

Occasionally the node does not respond to ftp requests causing FTP timeouts. This condition might cause CWM to be unable to collect statistics files from the node.
Workaround: Reset the PXM45 card.

CSCdr27681

Occasionally the node does not send statistics file creation traps. If this occurs, CWM will not collect the statistics files from the node.
Workaround: Reset the PXM45 card.

CSCdr28636

Occasionally the node does not send SNMP response or it sends the response after CWM declares a timeout. This is an SAR problem.
Workaround: Reset the PXM45 card.

CSCdr16832

Incomplete PVC or SPVC connection, failed to/from Connection manager GUI or Connection Service Agent.

The values of lot,port,vpi,vci for the remote side of the incomplete segment are the values in the rc column. There was an inconsistency in the cmgrd code wherein in the one segment case it was expecting the client to sedn these values but in the case of 2 or 3 segments it anyway picks up these intermediate end points and sends to databroker. Fix has been made in cmgrd to look for state column in user_connection and populate the intermediate endpts needed by databroker.

Workaround:

Delete the incomplete connection using CLI commands.

CSCdr31131

ABR Channel service type foresight option not correctly displayed in GUI. FCMGUI needs to modify logic for FRSM-VHS cards. New Connections -- FR-FR, Select Service Type "With Foresight".Select VHs cards for remote/local end pts. Press "Next". Now the CMGUI shows Service Type as "Without Foresight". In the parameters "Edit," select ChanServType as "abr," change MIR.PIR/QIR. But the Service Type still shows "Without Foresight." CMGUI should support Foresight for VHS cards for ABR service type. Also Note: Even if ChanServType is "ubr" or "vbr-nrt" the user can still change MIR.PIR/QIR.
Workaround: GUI display error corrected in FRSM-VHS logic.

CSCdr32120

CMGUI does not show connections per filter specified.

Workaround: Press Apply, and all the filtered connections are displayed.

CSCdr27807

NWTopology simultaneous config/save for same node hangs the last node selected. The reason for this was that two configSave applications don't address each other if they are on the same host. The message through gateway is broadcasted to all the other workstations. So what happens here is that both the applications send request to emd and the first saves it. The other waits for the timer to expire or emd to respond.

Workaround: Do not allow more than one configSave for one type of node.

CSCdr33375

Many Port Stats not covered for ausm from Statistics Enable Dialog. Open the Statistics Enable Dialog for Ausm card and find that many of the stats for port is not found in the Port-MGX ATM Port also Line-MGX_ATM does not cover the stats for MGX T1/E1 lines. These are a few stats that are not covered Get Request Rx, Get Request Tx, Get Response, etc.

Workaround: None

CSCdr09117

Wingz not integrated with desktop.

Workaround:WingZ has been integrated with Desktop since SCM 10.1 (April 26, 2000).

CSCdr35396

When core is stopped, security manager is not getting killed.

Opened CWM admin from Topology window, created few users and associated them with user-profiles. Among the users created, selected one of them and tried to change the profile association. The Security Manager (User administration window) gives an error "User unknown". Eventually the application hangs. Normally, to kill the Security Manager and all associated processes, stop the core. After stopping the core, all other processes are killed, but Security Manager is not. This will not allow the desktop to come up because when option 3 is selected from Main menu (after restarting the core), and with valid inputs, the desktop hangs up.

Workaround: None.

CSCdr36792

DeskTop does not connect to CWMgs when CWMgs re-starts.

Workaround: WingZ CwmGs gone, the SecureAdmin object is also gone. When CwmGS re-starts, the SecureAdmin object needs to be re-created.

Please refer to the MGX 8850 Release 2 documentation for a complete listing of all known anomalies.

Related Documentation

The following technical documents comprise the CWM 10.3 documentation set:

Service and Support

Technical Assistance Center

The Cisco Technical Assistance Center (TAC) is available to warranty or maintenance contract customers who need technical assistance with a Cisco product that is under warranty or covered by a maintenance contract.

To display the TAC web site that includes links to technical support information and software upgrades and for requesting TAC support, use www.cisco.com/techsupport.

To contact by e-mail, use one of the following:

Language

E-mail Address

 English


 tac@cisco.com


 Hanzi (Chinese)


 chinese-tac@cisco.com


 Kanji (Japanese)


 japan-tac@cisco.com


 Hangul (Korean)


 korea-tac@cisco.com


 Spanish


 tac@cisco.com


 Thai


 thai-tac@cisco.com

In North America, TAC can be reached at 800 553-2447 or 408 526-7209. For other telephone numbers and TAC e-mail addresses worldwide, consult the following web site: http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml

Obtaining Documentation

World Wide Web

You can access the most current Cisco documentation on the World Wide Web at http://www.cisco.com, http://www-china.cisco.com, or http://www-europe.cisco.com.

Documentation CD-ROM

Cisco documentation and additional literature are available in a CD-ROM package, which ships with your product. The Documentation CD-ROM is updated monthly. Therefore, it is probably more current than printed documentation. The CD-ROM package is available as a single unit or as an annual subscription.

Ordering Documentation

Registered CCO users can order the Documentation CD-ROM and other Cisco Product documentation through our online Subscription Services at http://www.cisco.com/cgi-bin/subcat/kaojump.cgi.

Nonregistered CCO users can order documentation through a local account representative by calling Cisco's corporate headquarters (California, USA) at 408 526-4000 or, in North America, call 800 553-NETS (6387).

Obtaining Technical Assistance

Cisco provides Cisco Connection Online (CCO) as a starting point for all technical assistance. Warranty or maintenance contract customers can use the Technical Assistance Center. All customers can submit technical feedback on Cisco documentation using the web, e-mail, a self-addressed stamped response card included in many printed docs, or by sending mail to Cisco.

Cisco Connection Online

Cisco continues to revolutionize how business is done on the Internet. Cisco Connection Online is the foundation of a suite of interactive, networked services that provides immediate, open access to Cisco information and resources at anytime, from anywhere in the world. This highly integrated Internet application is a powerful, easy-to-use tool for doing business with Cisco.

CCO's broad range of features and services helps customers and partners to streamline business processes and improve productivity. Through CCO, you will find information about Cisco and our networking solutions, services, and programs. In addition, you can resolve technical issues with online support services, download and test software packages, and order Cisco learning materials and merchandise. Valuable online skill assessment, training, and certification programs are also available.

Customers and partners can self-register on CCO to obtain additional personalized information and services. Registered users may order products, check on the status of an order and view benefits specific to their relationships with Cisco.

You can access CCO in the following ways:

You can e-mail questions about using CCO to cco-team@cisco.com.

This document is to be used in conjunction with the documents listed in the "Related Documentation" section.

Access Registrar, AccessPath, Any to Any, AtmDirector, Browse with Me, CCDA, CCDE, CCDP, CCIE, CCNA, CCNP, CCSI, CD-PAC, the Cisco logo, Cisco Certified Internetwork Expert logo, CiscoLink, the Cisco Management Connection logo, the Cisco NetWorks logo, the Cisco Powered Network logo, Cisco Systems Capital, the Cisco Systems Capital logo, Cisco Systems Networking Academy, the Cisco Systems Networking Academy logo, the Cisco Technologies logo, ConnectWay, Fast Step, FireRunner, Follow Me Browsing, FormShare, GigaStack, IGX, Intelligence in the Optical Core, Internet Quotient, IP/VC, Kernel Proxy, MGX, Natural Network Viewer, NetSonar, Network Registrar, the Networkers logo, Packet, PIX, Point and Click Internetworking, Policy Builder, Precept, RateMUX, ScriptShare, Secure Script, ServiceWay, Shop with Me, SlideCast, SMARTnet, SVX, The Cell, TrafficDirector, TransPath, ViewRunner, Virtual Loop Carrier System, Virtual Voice Line, VlanDirector, Voice LAN, Wavelength Router, Workgroup Director, and Workgroup Stack are trademarks; Changing the Way We Work, Live, Play, and Learn, Empowering the Internet Generation, The Internet Economy, and The New Internet Economy are service marks; and Aironet, ASIST, BPX, Catalyst, Cisco, Cisco IOS, the Cisco IOS logo, Cisco Systems, the Cisco Systems logo, the Cisco Systems Cisco Press logo, Enterprise/Solver, EtherChannel, EtherSwitch, FastHub, FastLink, FastPAD, FastSwitch, GeoTel, IOS, IP/TV, IPX, LightStream, LightSwitch, MICA, NetRanger, Post-Routing, Pre-Routing, Registrar, StrataView Plus, Stratm, TeleRouter, and VCO are registered trademarks of Cisco Systems, Inc. or its affiliates in the U.S. and certain other countries. All other trademarks mentioned in this document are the property of their respective owners. The use of the word partner does not imply a partnership relationship between Cisco and any of its resellers. (0004R)

Copyright © 2000, Cisco Systems, Inc.
All rights reserved.


hometocprevnextglossaryfeedbacksearchhelp
Posted: Sun Oct 1 19:44:28 PDT 2000
Copyright 1989-2000©Cisco Systems Inc.