Guest

Cisco WAN Manager

Release Notes for Cisco WAN Manager 15.0 Patch 2

  • Viewing Options

  • PDF (1.2 MB)
  • Feedback
Release Notes for Cisco WAN Manager 15.0.00, Patch 2

Table Of Contents

Release Notes for Cisco WAN Manager 15.0.00, Patch 2

Table of Contents

Overview

System Requirements

CWM Server

Java Client

Standalone Statistics Manager

Solaris Patch Requirements

CWM Software Release 15.0.00 Packaging

HP OpenView Requirements

INFORMIX Requirements

Supported Hardware

Existing Hardware

New Hardware

Certified Releases

New Features and Enhancements in CWM Release 15

Features Introduced in CWM Release 15.0.00, Patch 2

Features Introduced in CWM Release 15.0.00

Features Not Supported and Known Feature Limitations in 15.0.00

Limitations

Configuration Center Limitations

HP OpenView Limitations

Issues with the CWM 15 Statistics Collection Manager

Limitations for CWM to CWM Communication

Network Monitor Limitations

CWM 15 Notes and Cautions

CWM 15 Server Installation or Upgrade to CWM 15, Patch 2

CWM 15.0.00 Patch 2 Installation

WANDEST Release 2.5, Patch 2

Uninstalling Patch 2

Important Configuration Notes

Naming Managed Nodes

Using the Forced Delete Feature

Core File Management

Cisco Info Center Version

C-Note/CWM Configuration

Node Numbering for Release 9.4 IGX Feeder Nodes

Security Profiles

CWM Database

RPM Management Limitations

ChassisView Operation After Card and Line Switchovers

Equipment Management Configuration Notes

Network Monitor Server Configuration File (NMServer.conf)

Creating and Configuring a CWM Auto-Restart Shell Script

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

SNMP Service Agent Release Notes

Trap Limitation with PXM1-based MGX Nodes

Caveats

Known Anomalies in CWM 15 Software

Anomalies Resolved in CWM 15.0.00 Patch 2 Software

Anomalies Closed By Other Means in CWM 15.0.00 Patch 2 Software

Related Documentation

Obtaining Documentation

Documentation Feedback

Obtaining Technical Assistance

Cisco.com

Technical Assistance Center

Cisco TAC Web Site

Cisco TAC Escalation Center


Release Notes for Cisco WAN Manager 15.0.00, Patch 2


These release notes are part OL-5354-01 Rev. G0, December 27, 2004

Cisco WAN Manager Release 15.0.00 patch 2 software supports the following Cisco products as of 08/17/04:

Cisco MGX 8850 PXM45-based products running software releases 3.0.23 through 3.0.25, 4.0.00 through 4.0.15, or 5.0.00 through 5.0.10.

Cisco MGX 8880 PXM45-based products running software release 5.0.00 through 5.0.10.

Cisco MGX 8950 PXM45-based products running software releases 3.0.23 through 3.0.25, 4.0.00 through 4.0.15, or 5.0.00 through 5.0.10.

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

Cisco MGX PXM1-based products (8230, 8250 and 8850) running software releases 1.1.31 through 1.1.34, 1.2.20 through 1.2.21, or 1.3.00 through 1.3.10.

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

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

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

Table of Contents

Required Patches      7
Recommended Patches      8
CWM-specific Enhancements      26
WANDEST 2.5-Specific Enhancements      27
Preparing to Install the Patch (Backing Up the Existing Database)      36
Installing the CWM Server Patch      37
Verifying and Restoring Your Saved Database After Installing Patch 2      43
Installing the CWM SNMP Agent (Service Agent) Patch:      44
Installing the SSC (Standalone Statistics Collector) Patch on the Standalone Statistics Collector Machine:      50
Installing the SSM (Standalone Statistics Manager) Patch on the Standalone Statistics Manager Machine:      51
Installing the CWM RTM Proxy Patch on the CWM Machine:      51
Contents of This Patch      56
Installing the WANDEST Server Patch:      56
Installing the WANDEST Client Patch:      57

Overview

This document contains the following sections:

"System Requirements" section

"CWM Software Release 15.0.00 Packaging" section

"Supported Hardware" section

"New Features and Enhancements in CWM Release 15" section

"Features Not Supported and Known Feature Limitations in 15.0.00" section

"Limitations" section

"CWM 15 Notes and Cautions" section

"Important Configuration Notes" section

"Naming Managed Nodes" section

"RPM Management Limitations" section

"SNMP Service Agent Release Notes" section

"Caveats" section

"Known Anomalies in CWM 15 Software" section

"Obtaining Documentation" section

"Obtaining Technical Assistance" section

System Requirements

The following are additional notes for CWM platform requirements:

CWM 15 is compatible with UltraSPARC II and UltraSPARC III. Refer to Tables 1 through 4 for the system requirements for certified platforms. The Ultra 60, Enterprise 450 and Enterprise 4500 can still be used with CWM 15. These were previously certified with earlier releases of CWM. For certified system requirements, refer to the System Requirement Guidelines in the CWM release notes for Release 11.0.10, but the minimum RAM needs to be 2 GB. Problems reported by customers who choose a non Cisco-certified configuration may take more time to troubleshoot, etc., resulting in a longer turnaround time. CWM technical support will not be provided for Sun configurations or products that are no longer supported by Sun Microsystems.

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

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

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

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

CWM Server

Table 1 System Requirements - CWM Server 

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

Low - Medium

1

900

2 GB

4 GB

1 x 36 GB

100K

10

100

Netra 20, Sun Fire 280R

Medium

2

900

4 GB

8 GB

1 x 36 GB

200K

20

500

Netra 20, Sun Fire 280R

High -
Carrier Grade

4

900

8 GB

16 GB

2 x 36 GB

1M

40

1000

Sun Fire V880

Carrier Grade

8

900

16 GB

32 GB

2 x 36 GB

2M

100

2000

Sun Fire V880


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

If UltraSPARC II Servers are used, refer to the System Requirement Guidelines in the CWM release notes for Release 11.0.10. If you are using an Ultra 60 (low end platform), it should have at least 2 GB RAM memory.

Java Client

Table 2 System Requirements - Java Client 

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

PC

Windows 2000

Windows NT 4.0 with Service Pack 6a

Windows XP SP1

Internet Explorer 6.0

Netscape 4.76

J2SE v1.4.2_02

1
Pentium 3

750

512 MB

n/a

130 MB Free

y

SPARC10

Solaris 8

Netscape 4.76

1
450 Mhz

450

512 MB

1 GB

130 MB Free

y


Standalone Statistics Manager

Table 3 System Requirements - Standalone Statistics Collector or Manager 

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

Low

2

450

170 KB/sec

512 MB

2 GB

2 x 18 GB

350

U60

Medium #1

2

450

3.5 MB/sec

512 MB

2 GB

2 x 18 GB

700

U60

Medium #2

1

900

1.7 MB/sec

1 GB

2 GB

1 x 36 GB

700

Netra 20 or Sun Fire 280R

High

2

900

3.5 MB/sec

4 GB

8 GB

1 x 36 GB

900

Netra 20 or Sun Fire 280R


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

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

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

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

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

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

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

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

Low

1

450

0.25

2GB

2 x 9 GB

y

40K

Ultra 10

Low - Medium

2

450

1 GB

2 GB

2 x 18 GB

y

300K

Ultra 60

Low - Medium

1

900

2 GB

4 GB

2 x 36 GB

y

750K

Netra 20, Sun Fire 280R

Medium

2

900

4 GB

8 GB

2 x 36 GB

y

2M

Netra 20, Sun Fire 280R

High - Carrier Grade

4

900

8 GB

16 GB

2 x 36 GB

y

4M

Sun Fire V880


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

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

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

Solaris Patch Requirements

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

Solaris 8 Kernel Patch 27 or higher (108528-27 or higher)

(previously was 108528-13)

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

Required Patches

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

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

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

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

111626-01

111327-02

110945-02

110934-01

110898-02

110700-01

110670-01

109326-05

108652-35

108528-27

Recommended Patches

110951-01

110662-02

110615-01

110286-02

109324-02

111085-02

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

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


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


CWM Software Release 15.0.00 Packaging

Refer to the "CWM 15.0.00 Patch 2 Installation" section for the contents of patch 2. The following is the list of CDs for the CWM 15.0.00 release:

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

CWM Server. This CD contains the following:

CWM Server Software

INFORMIX Server Software Release 9.21.UC7XH

CWM Java Client Software

CWM Documentation CD. This CD contains the following:

Acrobat Reader 4.0

gzip

PDF copy of the CWM 15 documentation set

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

Service Agent CD. This CD contains the following

CWM Service Agent Software

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

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

Standalone SCM Software with WANDEST Client Software incorporated

INFORMIX Server Software Release 9.21.UC7XH

The Standalone Statistics Collection Manager software also includes the RTM Proxy for SCM Application on a separate CD. This CD is included only when you have ordered the Standalone Statistics Collection Manager software.

RTM Proxy for SCM Application CD. This CD contains the following:

RTM Proxy for SCM Application Software


Note Refer to the CWM Installation Guide, Release 15 for instructions on installing the RTM Proxy for SCM application from the CD. The RTM Proxy for SCM application is only meant to be installed with the Standalone Statistic Manager. It is not for systems with the Service Agent. If you already have the Service Agent software installed and you attempt to install this application, you will see errors on the console because the ~/config/process.conf file will have duplicate entries for the RTM Proxy.


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

WANDEST Release 2.5 Server CD

WANDEST Server Software, Release 2.5

WANDEST Release 2.5 Client CD

WANDEST Client Software, Release 2.5

HP OpenView Requirements

The CWM 15 release works with HP OpenView Release 6.2 or 6.3 for Solaris 8. See "Third Party Product Limitations Notes" for HP OpenView patches required by CWM.


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


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

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

INFORMIX Requirements

The CWM 15 release uses Informix release 9.21.UC7XH for database operations. The INFORMIX software is bundled with CWM software on disk 1 of the CWM CD package. The INFORMIX program is automatically installed during CWM installation.

Supported Hardware

This section provides information about the hardware supported by the CWM 15 release.

Existing Hardware

Table 5 lists the existing hardware supported by CWM 15.0.00.

Table 5 Supported Existing Hardware 

Platform Series
Front Card
Back Card
Supported Release Version

IGX 8400

NPM

SCM

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

IGX 8400

NTM

BC-T1/E1/SR/Y1

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

IGX 8400

UVM

UVI-2T1EC/2E1EC

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

IGX 8400

UFM-C

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

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

IGX 8400

UFM-U

UFI-V35/X21/HSI

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

IGX 8400

UXM

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

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

BPX 8600

BCC

BCC-bc/3-bc

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

BPX 8600

ASM

LM-ASM

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

BPX 8600

BNI-T3

LM-3T3

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

BPX 8600

BNI-E3

LM-3E3

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

BPX 8600

BNI-155

LM-OC3-SMF/SMFLR/MMF

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

BPX 8600

ASI-1

LM-2T3/2E3

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

BPX 8600

ASI-155

LM-2OC3-SMF/SMFLR/MMF

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

BPX 8600

BXM-T3/E3

T3/E3-BC

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

BPX 8600

BXM-15 5

MMF/SMF/SMFLR-155

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

BPX 8600

BXM-622

MMF/SMF/SMFLR-622

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

SES PNNI Controller

SES-PXM

T3/E3/OC3/OC12

3.0.10 through 3.0.25, or 4.0.00 through 4.0.15

SES PNNI Controller

SES-PXM

PXM-UIA

3.0.10 through 3.0.25, or 4.0.00 through 4.0.15

MGX 8220

FRSM-8P

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

4.1.07 through 4.1.12, or 5.0.12 through 5.0.20

MGX 8220

AUSM-8P

RJ48-8E1/8T1

4.1.07 through 4.1.12, or 5.0.12 through 5.0.20

MGX 8220

CESM-8P

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

4.1.07 through 4.1.12, or 5.0.12 through 5.0.20

MGX 8220

IMATM-B

RJ48-T3T1/E3E1

SMB-E3E1

4.1.07 through 4.1.12, or 5.0.12 through 5.0.20

MGX 8220

FRSM-HS1

HSI-4X21/3HSSI

4.1.07 through 4.1.12, or 5.0.12 through 5.0.20

MGX 8220

BNM-T3/E3

T3E3-B/D

4.1.07 through 4.1.12, or 5.0.12 through 5.0.20

MGX 8220

BNM-155

155-SMF

4.1.07 through 4.1.12, or 5.0.12 through 5.0.20

MGX 8220

SRM

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

4.1.07 through 4.1.12, or 5.0.12 through 5.0.20

MGX 8220

ASC

ASC-LM

4.1.07 through 4.1.12, or 5.0.12 through 5.0.20

MGX 8220

FRSM-VHS

HS2

4.1.07 through 4.1.12, or 5.0.12 through 5.0.20

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

AUSM Model B

8T1/E1

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

MGX 8230, MGX 8250, MGX 8850 PXM1

PXM1

T3/E3/OC3/OC12

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

MGX 8230, MGX 8250, MGX 8850 PXM1

FRSM-VHS

HS2/T3/E3/2CT3/HS2B

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

MGX 8230, MGX 8250, MGX 8850 PXM1

FRSM-8P

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

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

MGX 8230, MGX 8250, MGX 8850 PXM1

CESM-8P

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

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

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

MGX 8230, MGX 8250, MGX 8850 PXM1

CESM

T3/E3

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

MGX 8230, MGX 8250, MGX 8850 PXM1

SRM

LM-3T3

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

MGX 8230, MGX 8250, MGX 8850 PXM1

VISM-8T1

AX-RJ48-8T1

AX-R-RJ48-8T1

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

MGX 8230, MGX 8250, MGX 8850 PXM1

VISM-8E1

AX-SMB-8E1

AX-RJ48-8E1

AX-R-SMB-8E1

AX-R-RJ48-8E1

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

MGX 8230, MGX 8250, MGX 8850 PXM1

VISM-PR

RJ48-T1/E1 and SMB-E1

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

MGX 8950 (PXM45)

AXSM/B

T3/E3

2.1.76 through 2.1.81, 3.0.23 through 3.0.25, 4.0.00 through 4.0.15, or 5.0.00 through 5.0.10

MGX 8950 (PXM45)

AXSM/B

OC3

2.1.76 through 2.1.81, 3.0.23 through 3.0.25, 4.0.00 through 4.0.15, or 5.0.00 through 5.0.10

MGX 8950 (PXM45)

AXSM/B

OC12

2.1.76 through 2.1.81, 3.0.23 through 3.0.25, 4.0.00 through 4.0.15, or 5.0.00 through 5.0.10

MGX 8950 (PXM45)

AXSM/B

OC48

2.1.76 through 2.1.81, 3.0.23 through 3.0.25, 4.0.00 through 4.0.15, or 5.0.00 through 5.0.10

MGX 8950 (PXM45)

PXM45

PXM-HD, PXM-UI

2.1.76 through 2.1.81, 3.0.23 through 3.0.25, 4.0.00 through 4.0.15, or 5.0.00 through 5.0.10

MGX 8950 (PXM45)

PXM45B

PXM-HD, PXM-UI

2.1.76 through 2.1.81, 3.0.23 through 3.0.25, 4.0.00 through 4.0.15, or 5.0.00 through 5.0.10

MGX 8950 (PXM45)

RPM-PR

Ethernet, Fast Ethernet

3.0.23 through 3.0.25, 4.0.00 through 4.0.15, or 5.0.00 through 5.0.10

MGX 8950 (PXM45)

RPM-XF

MGX-1GE and MGX-1OC12POS

3.0.23 through 3.0.25, 4.0.00 through 4.0.15, or 5.0.00 through 5.0.10

MGX 8850 (PXM45)

AXSM/A

AXSM/B

T3/E3

2.1.76 through 2.1.81, 3.0.23 through 3.0.25, 4.0.00 through 4.0.15, or 5.0.00 through 5.0.10

MGX 8850 (PXM45)

AXSM/A

AXSM/B

OC3

2.1.76 through 2.1.81, 3.0.23 through 3.0.25, 4.0.00 through 4.0.15, or 5.0.00 through 5.0.10

MGX 8850 (PXM45)

AXSM/A

AXSM/B

OC12

2.1.76 through 2.1.81, 3.0.23 through 3.0.25, 4.0.00 through 4.0.15, or 5.0.00 through 5.0.10

MGX 8850 (PXM45)

AXSM/A

AXSM/B

OC48

2.1.76 through 2.1.81, 3.0.23 through 3.0.25, 4.0.00 through 4.0.15, or 5.0.00 through 5.0.10

MGX 8850 (PXM45)

AXSM-E

T3/E3

2.1.76 through 2.1.81, 3.0.23 through 3.0.25, 4.0.00 through 4.0.15, or 5.0.00 through 5.0.10

MGX 8850 (PXM45)

AXSM-E

OC3

2.1.76 through 2.1.81, 3.0.23 through 3.0.25, 4.0.00 through 4.0.15, or 5.0.00 through 5.0.10

MGX 8850 (PXM45)

AXSM-E

OC12

2.1.76 through 2.1.81, 3.0.23 through 3.0.25, 4.0.00 through 4.0.15, or 5.0.00 through 5.0.10

MGX 8850 (PXM45)

AXSM-E

OC48

2.1.76 through 2.1.81, 3.0.23 through 3.0.25, 4.0.00 through 4.0.15, or 5.0.00 through 5.0.10

MGX 8850 (PXM45)

PXM45

PXM-HD, PXM-UI

2.1.76 through 2.1.81, 3.0.23 through 3.0.25, 4.0.00 through 4.0.15, or 5.0.00 through 5.0.10

MGX 8850 (PXM45)

PXM45B

PXM-HD, PXM-UI

2.1.76 through 2.1.81, 3.0.23 through 3.0.25, 4.0.00 through 4.0.15, or 5.0.00 through 5.0.10

MGX 8850 (PXM45)

RPM-XF

MGX-1GE and MGX-1OC12POS

3.0.23 through 3.0.25, 4.0.00 through 4.0.15, or 5.0.00 through 5.0.10

MGX 8850 (PXM45)

RPM-PR

Ethernet, Fast Ethernet

3.0.23 through 3.0.25, 4.0.00 through 4.0.15, or 5.0.00 through 5.0.10

MGX 8850 (PXM45)

VISM-PR

RJ48-T1/E1 and SMB-E1

3.0.23 through 3.0.25, 4.0.00 through 4.0.15, or 5.0.00 through 5.0.10

MGX 8850 (PXM1E)

PXM1E

8 Port 155

3.0.23 through 3.0.25, 4.0.00 through 4.0.15, or 5.0.00 through 5.0.10

MGX 8850 (PXM1E)

PXM1E

8 Port T3/E3

3.0.23 through 3.0.25, 4.0.00 through 4.0.15, or 5.0.00 through 5.0.10

MGX 8850 (PXM1E)

RPM-PR

Ethernet, Fast Ethernet

3.0.23 through 3.0.25, 4.0.00 through 4.0.15, or 5.0.00 through 5.0.10

MGX 8850 (PXM1E)

VISM-PR

RJ48-T1/E1 and SMB-E1

3.0.23 through 3.0.25, 4.0.00 through 4.0.15, or 5.0.00 through 5.0.10

MGX 8850 (PXM1E)

AUSM Model B

8T1/E1

3.0.23 through 3.0.25, 4.0.00 through 4.0.15, or 5.0.00 through 5.0.10

MGX 8850 (PXM1E)

FRSM-8P

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

3.0.23 through 3.0.25, 4.0.00 through 4.0.15, or 5.0.00 through 5.0.10

MGX 8850 (PXM1E)

CESM-8P

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

3.0.23 through 3.0.25, 4.0.00 through 4.0.15, or 5.0.00 through 5.0.10

MGX 8850 (PXM1E)

FRSM-HS2B

8 port 12in1, HSSI

3.0.23 through 3.0.25, 4.0.00 through 4.0.15, or 5.0.00 through 5.0.10

MGX 8850 (PXM1E)

SRM/E

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

3.0.23 through 3.0.25, 4.0.00 through 4.0.15, or 5.0.00 through 5.0.10

MGX 8230, MGX 8250, MGX 8850 (PXM1)

FRSM-HS2B

8 port 12in1, HSSI

1.2.00 through 1.2.13, 1.2.20 through 1.2.21, or 1.3.00 through 1.3.10

MGX 8230, MGX 8250, MGX 8850 (PXM1)

SRM/E

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

1.2.00 through 1.2.13, 1.2.20 through 1.2.21, or 1.3.00 through 1.3.10

MGX 8230, MGX 8250, MGX 8850 (PXM1)

RPM/B

Ethernet, Fast Ethernet

1.2.00 through 1.2.13, 1.2.20 through 1.2.21, or 1.3.00 through 1.3.10

MGX 8230, MGX 8250, MGX 8850 (PXM1)

RPM-PR

Ethernet, Fast Ethernet

1.2.00 through 1.2.13, 1.2.20 through 1.2.21, or 1.3.00 through 1.3.10

MGX 8230, MGX 8250, MGX 8850 (PXM1)

VISM-PR

RJ48-T1/E1 and SMB-E1

1.2.00 through 1.2.13, 1.2.20 through 1.2.21, or 1.3.00 through 1.3.10

MGX 8950 (PXM45)

AXSM-XG

OC192

4.0.00 through 4.0.15, or 5.0.00 through 5.0.10

MGX 8950 (PXM45)

AXSM-XG

OC48

4.0.00 through 4.0.15, or 5.0.00 through 5.0.10

MGX 8950 (PXM45)

PXM45/C

PXM-HD, PXM-UI S3/B

4.0.00 through 4.0.15, or 5.0.00 through 5.0.10

MGX 8850 (PXM45)

PXM45/C

PXM-HD, PXM-UI S3/B

4.0.00 through 4.0.15, or 5.0.00 through 5.0.10

MGX 8850 (PXM45)

FRSM-8P

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

4.0.00 through 4.0.15, or 5.0.00 through 5.0.10

MGX 8850 (PXM45)

FRSM-HS2/B

8 port 12in1, HSSI

4.0.10 through 4.0.15, or 5.0.00 through 5.0.10

MGX 8850 (PXM45)

FRSM-VHS

2T3E3

4.0.10 through 4.0.15, or 5.0.00 through 5.0.10

MGX 8850 (PXM45)

CESM-8P

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

4.0.00 through 4.0.15, or 5.0.00 through 5.0.10

MGX 8850 (PXM45)

FRSM-VHS

2CT3

4.0.00 through 4.0.15, or 5.0.00 through 5.0.10

MGX 8850 (PXM45)

SRM/E

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

4.0.00 through 4.0.15, or 5.0.00 through 5.0.10

MGX 8830/8850 (PXM1E)

PXM1E

8 port OC3 STM1

4.0.00 through 4.0.15, or 5.0.00 through 5.0.10

MGX 8830/8850 (PXM1E)

FRSM-VHS

2CT3

4.0.00 through 4.0.15, or 5.0.00 through 5.0.10

MGX 8950 (PXM45)

AXSM-XG

OC3 16P

5.0.00 through 5.0.10

MGX 8880 (PXM45)

AXSM-XG

OC3 16P

5.0.00 through 5.0.10

MGX 8880 (PXM45)

AXSM-E

OC12

5.0.00 through 5.0.10

MGX 8880 (PXM45)

AXSM/B

OC48

5.0.00 through 5.0.10

MGX 8880 (PXM45)

PXM45B

N/A

5.0.00 through 5.0.10

MGX 8880 (PXM45)

VXSM

RJ48-T1/E1 and SMB-E1

5.0.00 through 5.0.10

MGX 8880 (PXM45)

VISM-PR

RJ48-T1/E1 and SMB-E1

5.0.00 through 5.0.10

MGX 8880 (PXM45)

RPM-XF

MGX-2GE and MGX-2OC12POS

5.0.00 through 5.0.10

MGX 8880 (PXM45)

RPM-PR

MGX-2GE and MGX-2OC12POS

5.0.00 through 5.0.10

MGX 8880 (PXM45)

SRME/B

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

5.0.00 through 5.0.10

MGX 8850 (PXM45)

AXSM-XG

OC3

5.0.00 through 5.0.10

MGX 8850 (PXM45)

RPM-XF

MGX-2GE and MGX-2OC12POS

5.0.00 through 5.0.10

MGX 8850 (PXM45)

RPM-PR

MGX-2GE and MGX-2OC12POS

5.0.00 through 5.0.10

MGX 8850 (PXM45)

VISM-PR

RJ48-T1/E1 and SMB-E1

5.0.00 through 5.0.10

MGX 8850 (PXM45)

SRME/B

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

5.0.00 through 5.0.10

MGX 8850/8830 (PXM1E)

RPM-XF

MGX-2GE and MGX-2OC12POS

5.0.00 through 5.0.10

MGX 8850/8830 (PXM1E)

RPM-PR

MGX-2GE and MGX-2OC12POS

5.0.00 through 5.0.10

MGX 8850/8830 (PXM1E)

VISM-PR

RJ48-T1/E1 and SMB-E1

5.0.00 through 5.0.10

MGX 8850/8250/8230 (PXM1)

SRME/B

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

1.3.00 through 1.3.10

MGX 8850/8250/8230 (PXM1)

RPM-PR

MGX-2GE and MGX-2OC12POS

1.3.00 through 1.3.10

MGX 8850/8250/8230 (PXM1)

VISM-PR

RJ48-T1/E1 and SMB-E1

1.3.00 through 1.3.10


New Hardware

Table 6 lists the new hardware supported in CWM Release 15 patch 2.

Table 6 Supported New Hardware 

Platform Series
Front Card
Back Card
Min. Software Version

MGX 8880 (PXM45)

MPSM-8-T1E1

AX-RJ48-8T1

AX-R-RJ48-8T1

AX-RJ48-8E1

AX-R-RJ48-8E1

AX-SMB-8E1

AX-R-SMB-8E1

5.0.10

MGX 8880 (PXM45)

RPM-XF

MGX-UI/B

5.0.10

MGX 8850 (PXM45)

MPSM-8-T1E1

AX-RJ48-8T1

AX-R-RJ48-8T1

AX-RJ48-8E1

AX-R-RJ48-8E1

AX-SMB-8E1

AX-R-SMB-8E1

5.0.10

MGX 8850 (PXM45)

RPM-XF

MGX-UI/B

5.0.10

MGX 8850/8830 (PXM1E)

MPSM-8-T1E1

AX-RJ48-8T1

AX-R-RJ48-8T1

AX-RJ48-8E1

AX-R-RJ48-8E1

AX-SMB-8E1

AX-R-SMB-8E1

5.0.10

MGX 8850/8830 (PXM1E)

RPM-XF

MGX-UI/B

5.0.10

MGX 8850/8250/8230 (PXM1)

MPSM-8-T1E1

AX-RJ48-8T1

AX-R-RJ48-8T1

AX-RJ48-8E1

AX-R-RJ48-8E1

AX-SMB-8E1

AX-R-SMB-8E1

1.3.10


Certified Releases

The following releases were tested with CWM release 15:

BPX/IGX Switch Software:

Switch Software 9.4.10

Switch Software 9.3.45

Switch Software 9.3.36

MGX 8230/8250/8850 (PXM1) Switch

MGX 1.3.10

MGX 1.2.21

MGX 1.2.13 & 1.1.34

MGX 8950 (PXM45) Switch

MGX 5.0.10

MGX 4.0.15

MGX 8850 (PXM45) Switch

MGX 5.0.10

MGX 4.0.15

MGX 3.0.25

MGX 8880 (PXM45) Switch

MGX 5.0.10

MGX 8850/8830 (PXM1E) Switch

MGX 5.0.10

MGX 4.0.15

MGX 3.0.25

BPX SES Shelf

SES 4.0.15

SES 3.0.25

MGX 8220 Shelf

MGX 8220 5.0.20

MGX 8220 4.1.12

VISM-PR

VISM-PR 3.2.11

VISM-PR 3.1.2

VISM-PR 2.2.1

VISM-PR 1.5.10 (Certified with MGX 1.1.34 only)

VXSM

VXSM 5.0.00

RPM-XF

IOS 12.3(7)T3

IOS 12.3(2)T5

RPM-PR

IOS 12.3(7)T3

IOS 12.2(8)T4

New Features and Enhancements in CWM Release 15

Features Introduced in CWM Release 15.0.00, Patch 2

This section describes the new features introduced in Cisco WAN Manager Release 15.0.00, patch 2.

MGX 8950 Release 5 (PXM45-based nodes)

AXSM-XG 16-Port OC3 service module can link to MGX PXM1-based switches as a feeder

CWM 15.0.00 Patch 2 can discover the configuration where MGX PXM1-based switches are used as a feeder to the AXSM-XG 16-Port OC3 service modules on the MGX 8950 shelf. Connections can be set up between the termination points on these feeders and other connection endpoints on the MGX 8950 or on another feeder shelf.

Support for redesigned RPM-XF back cards

With the release of CWM Release 15.0.00, patch 2, the new RPM-XF back cards that are designed to work with the MGX 8880 are now supported.

Support for the preferred routes feature on RPM-XF

With the release of CWM Release 15.0.00, patch 2, configuration of preferred routes for the RPM-XF for XPVC connections is now supported.

The pref_route_id and direct_route_flag fields have been added to the rpm_connection table. The pref_route_id field indicates the associated preferred route for the particular connection.

The direct_route_flag field indicates whether the connection is directed or not. If this is true then the associated SPVC will be routed only to the preferred route. If the preferred route is not available, the connection is not routed on any alternative route and then is flagged as failed. If direct_route_flag is false then the associated SPVC will also be routed to the preferred route, but if the preferred route is not available, alternative routes will be considered as per PNNI routing policies.

Service agent support is provided by adding RPM-XF support to the cwmConnPrefRouteId (for PNNI XPVC segments only) and cwmConnDirectRoute objects in the cwmConnTable in CWM Release 15.0.00, patch 2.

MGX 8880 Release 5 (PXM45-based nodes)

Support for redesigned RPM-XF back cards

With the release of CWM Release 15.0.00, patch 2, the new RPM-XF back cards that are designed to work with the MGX 8880 are now supported.

Support for the preferred routes feature on RPM-XF

With the release of CWM Release 15.0.00, patch 2, configuration of preferred routes for the RPM-XF for XPVC connections is now supported.

The pref_route_id and direct_route_flag fields have been added to the rpm_connection table. The pref_route_id field indicates the associated preferred route for the particular connection.

The direct_route_flag field indicates whether the connection is directed or not. If this is true then the associated SPVC will be routed only to the preferred route. If the preferred route is not available, the connection is not routed on any alternative route and then is flagged as failed. If direct_route_flag is false then the associated SPVC will also be routed to the preferred route, but if the preferred route is not available, alternative routes will be considered as per PNNI routing policies.

Service agent support is provided by adding RPM-XF support to the cwmConnPrefRouteId (for PNNI XPVC segments only) and cwmConnDirectRoute objects in the cwmConnTable in CWM Release 15.0.00, patch 2.

MGX 8850 Release 5 (PXM45 and PXM1E-based nodes)

Support for redesigned RPM-XF back cards

With the release of CWM Release 15.0.00, patch 2, the new RPM-XF back cards that are designed to work with the MGX 8880 are now supported.

Support for the preferred routes feature on RPM-XF

With the release of CWM Release 15.0.00, patch 2, configuration of preferred routes for the RPM-XF for XPVC connections is now supported.

The pref_route_id and direct_route_flag fields have been added to the rpm_connection table. The pref_route_id field indicates the associated preferred route for the particular connection.

The direct_route_flag field indicates whether the connection is directed or not. If this is true then the associated SPVC will be routed only to the preferred route. If the preferred route is not available, the connection is not routed on any alternative route and then is flagged as failed. If direct_route_flag is false then the associated SPVC will also be routed to the preferred route, but if the preferred route is not available, alternative routes will be considered as per PNNI routing policies.

Service agent support is provided by adding RPM-XF support to the cwmConnPrefRouteId (for PNNI XPVC segments only) and cwmConnDirectRoute objects in the cwmConnTable in CWM Release 15.0.00, patch 2.

Support for the MPSM T3/E3 Service Module (2-Port-OC-3/STM1 back card or 3-Port T3/E3 back card)

Support for the MPSM 8-Port T1/E1 Service Module

The MPSM is a multi-purpose service module which can be configured to support ATM, Frame Relay, or Circuit Emulation services. The MPSM-8-T1E1 card has any service, any card (ASAC) capability, which means that all the ports on a card can be configured to one of the supported services. The different services on this module are enabled by software licenses downloadable to the processor card in the node. CWM manages these enabled services on an MPSM service module the same way it manages existing service modules. Multiple ports can be configured to form an ATM IMA group. CWM Release 15.0.00, patch 2 displays the licenses available in the node.

For more information on license management, refer to Chapter 3, Managing Devices, the Managing Licenses for MPSM section (p. 3-63 to p.3-65) under the Managing Network Elements section in the Cisco WAN Manager User's Guide, Release 15 online.

The URL is: http://www.cisco.com/univercd/cc/td/doc/product/wanbu/svplus/15/ug/devices.htm#wp1128668

AXSM-XG 16-Port OC3 service module can link to MGX PXM1-based switches as a feeder

CWM 15.0.00 Patch 2 can discover the configuration where MGX PXM1-based switches are used as a feeder to the AXSM-XG 16-Port OC3 service modules on MGX PXM45-based nodes. Connections can be set up between the termination points on these feeders and other connection endpoints on the MGX PXM45-based node or on another feeder shelf.

Support for the forced delete feature

CWM Release 15.0.00, patch 2 introduces the Forced Delete feature. For more information, refer to the "Using the Forced Delete Feature" section.

Support for VISM Software 3.2.11 for VISM and VISM-PR

CWM extends the VISM features coverage to include the new features available in VISM software release 3.2.11. This includes configuration, trap monitoring, connection provisioning and diagnostics and real time statistics counter retrieval. Only the VISM-PR can be used on MGX PXM45 and PXM1E-based nodes. The PXM1E or PXM45-based switches managing VISM and VISM-PR require MGX 5.0.10 as well as VISM software 3.2.11.

The following VISM/VISM-PR features are supported by CWM 15.0.00, patch 2:

Programmable CAS idle code generation

G729a Bandwidth Improvement

Companding Law setting for VISM TDM Interfaces

VISM Setting for Preferred Route for AAL2 Trunks

Programmable ABCD CAS Signaling Bits Translation

VISM E1 Trunk Conditioning

ATM AIS Signal Propagation Control to TDM I/F

Bandwidth Utilization Enhancements

Display All Static Configuration

Limitations:

Bulk statistics files are not available from VISM or VISM-PR in release 3.2.11.

The Equipment Manager cannot sync up with a mixture of VISM or VISM-PR running release 3.2.11 and VISM or VISM-PR running release 3.2 or earlier.

MGX 8850, 8250, and 8230 Release 1.3.10 (PXM1-based nodes)

Support for VISM Software 3.2.11 for VISM and VISM-PR

CWM extends the VISM features coverage to include the new features available in VISM software release 3.2.11. This includes configuration, trap monitoring, connection provisioning, diagnostics and real time statistics counter retrieval. The VISM service module can only be used on PXM1-based MGX switches whereas the VISM-PR can be used on PXM1-based MGX switches, as well as PXM1E and PXM45-based MGX switches. PXM1-based switches managing VISM and VISM-PR require MGX 1.3.10 as well as VISM software 3.2.11.

The following VISM/VISM-PR features are supported by CWM 15.0.00, patch 2:

Programmable CAS idle code generation

G729a Bandwidth Improvement

Companding Law setting for VISM TDM Interfaces

VISM Setting for Preferred Route for AAL2 Trunks

Programmable ABCD CAS Signaling Bits Translation

VISM E1 Trunk Conditioning

ATM AIS Signal Propagation Control to TDM I/F

Bandwidth Utilization Enhancements

Display All Static Configuration

Limitations:

Bulk statistics files are not available from VISM or VISM-PR in release 3.2.11.

The Equipment Manager cannot sync up with a mixture of VISM or VISM-PR running release 3.2.11 and VISM or VISM-PR running release 3.2 or earlier.

Support for the MPSM 8-Port T1/E1 Service Module

The MPSM is a multi-purpose service module which can be configured to support ATM, Frame Relay, or Circuit Emulation services. The MPSM-8-T1E1 card has any service, any card (ASAC) capability, which means that all the ports on a card can be configured to one of the supported services. The different services on this module are enabled by software licenses downloadable to the processor card in the node. CWM manages these enabled services on an MPSM service module the same way it manages existing service modules. Multiple ports can be configured to form an ATM IMA group. CWM Release 15.0.00, patch 2 displays the licenses available in the node.

For more information on license management, refer to Chapter 3, Managing Devices, the Managing Licenses for MPSM section (p. 3-63 to p.3-65) under the Managing Network Elements section in the Cisco WAN Manager User's Guide, Release 15 online.

The URL is:

http://www.cisco.com/univercd/cc/td/doc/product/wanbu/svplus/15/ug/devices.htm#wp1128668

IGX 8400 switch family

With the release of CWM Release 15.0.00, patch 2, the NTM, UVM, and HDM service modules are now supported. Management of these service modules requires IGX 9.4 software as well as CWM Release 15.0.00, patch 2.

Limitations:

The URM, ARM, FRM, BTM, ALM and CVM service modules are not supported by CWM Release 15.

If you have these unsupported service modules you can either stay with CWM 12 or upgrade to the newer supported service modules to take advantage of the new CWM 15 GUI enhancements.

CWM-specific Enhancements

CWM support for Network Partitioning

For more information on CWM support for Network Partitioning, refer to Chapter 2, Getting Started with CWM, Configuring for Network Partitioning section (p. 2-44 to p. 2-52) under Configuring CWM User Access section in the Cisco WAN Manager User's Guide, Release 15 online.

Configuring for Network Partitioning section URL:

http://www.cisco.com/univercd/cc/td/doc/product/wanbu/svplus/15/ug/start_up.htm#wp1161665

Creating New Profiles section URL:

http://www.cisco.com/univercd/cc/td/doc/product/wanbu/svplus/15/ug/start_up.htm#wp1082122

CWM Configuration Center support for automatic calculation of Bc/Be values for frame relay connections

Support for column sorting in the Monitoring view of the SCM application.

With the release of CWM Release 15.0.00, patch 2, you can now sort any column in the SCM Monitoring view by clicking on the column header.

Duplicate node name blocking

In prior releases, CWM required a coldstart when a duplicate node name was discovered. When there are two or more nodes bearing the same name, CWM Release 15.0.00, patch 2 now alerts you. You no longer need to perform a coldstart after re-configuring the node names in the network so that each node name is unique.

Limitations:

This feature only applies to connected nodes within PNNI networks.

Improvements to Administration GUI

Forced Log out of Java Client Sessions

CWM Administrative user can initiate a Force Log Out to multiple selected Java Client sessions. This is particularly useful for software maintenance, or for eliminating idle user sessions for security purposes. The selected Java Client sessions are terminated within 15 seconds by default. All opened CWM GUI applications are closed automatically. The Administrative user can configure the notice time up to 60 seconds for added flexibility.

Validation of Java Client Sessions

CWM Administration GUI has a new "Validate Clients" function to verify the current active Java Client sessions to find out which operators are still logging in. This validation function detects and removes the stale sessions that are discontinued perhaps due to LAN connectivity failure or due to Client shutdown abnormally. It gives an accurate view of the Java Client sessions to the CWM Administrative user.

CWM Gateway Switchover Enhancement

CWM Release 15.0.00, patch 2 provides an additional configuration option (the CONDITIONAL_PRIMARY flag) in the cwmgateway.conf file that lets you configure an automatic CWM Server switchover when the primary CWM Server fails and there is only one Secondary CWM Server. Previous CWM releases required a manual procedure to invoke the secondary CWM Server to become the primary CWM Server.

The conditional flag is used to make the secondary a conditional primary in case of connectivity loss between the two CWM gateway servers.

In earlier releases, a condition would occur where there would be two primary servers when the connectivity was restored.

With this enhancement, the conditional primary will become secondary when the connectivity is restored.

For more information, refer to the CWM Gateway Configuration File section in Chapter 3 of the Cisco WAN Manager Installation Guide, Release 15 online.

Enhanced SNMP support for network and node information

With CWM Release 15.0.00, patch 2 you can access the following information using SNMP queries on the service MIB:

CWM version

CWM primary host name

Platform type

State information (alarm_state, mode, mgmt_state, active)

Protocol type

Network name and PNNI ID in the node MIB table (you can determine which region a chosen node is in).

Refer to Appendix C of the Cisco WAN Manager SNMP Service Agent Guide, Release 15 for more information on the individual objects.

Features Introduced in CWM Release 15.0.00

This section describes the new features introduced in Cisco WAN Manager Release 15.0.00.

MGX 8880 Release 5 (PXM45-based nodes)

Support for VXSM-OC3 service module

Support for VXSM-48-T1E1 service module

The Voice Switch Service Module (VXSM) is the carrier class, high density, service module for the MGX88xx voice gateway. CWM is the system for setting up AAL2 connection between voice gateways using VXSM for Voice Trunking solutions. This enables the use of packet network for carrying voice traffic and eliminates the need for point-to-point TDM circuit.

Both VXSM with 4 port OC3/STM1 and VXSM with 48 ports of T1/E1 are supported by this CWM release. These modules can be used on the Cisco MGX 8880 PXM45-based voice gateway with AXSMB and VISM-PR.

CWM 15 supports configuration of the lines, ports and channels on these VXSM cards via the GUI and the SNMP Service Agent.

CWM 15 also provides the ability to provision and diagnose ATM connections between VXSM modules or between VXSM and VISM-PR. Image download, TRAP monitoring for the equipment, 1:1 protection switching, and the ATM connections are handled as in other service modules.

The Statistics Collection Manager collects bulk statistics files from VXSM for ATM connection statistics, SONET/SDH line and path statistics, Megaco gateway and termination statistics, and SCTP and LAPD statistics. Realtime statistics counters for CID level statistics can be queried from the CWM 15 GUI using the Diagnostics Center application.

MGX 8850, Release 5

Support for AXSM-16-155-XG

CWM 15 supports the AXSM-16-155-XG service module, which addresses the need for enhanced traffic management capabilities over a higher OC-3c/STM-1 port density.

The AXSM-16-155-XG service module supports ABR with VS/VD and per-VC/VP shaping on 128K connections and provides a full 2.4 Gbps of usable bandwidth per card. These enhancements help lower the cost of OC-3c/STM-1 ports.

Support for soft rerouting

CWM 15 supports soft rerouting. In previous releases during the grooming process the connection was derouted and rerouted when the connection was on a PNNI routed path. Even when the better/desired route was unavailable the connection was derouted and rerouted using PNNI. The soft reroute feature enables you to move a routed SPVC/P from an incumbent working path to a new path with minimal loss of traffic. The existing connection along the path is not derouted until a connection has been established on a new path. Thus soft route brings higher connection availability. QoS is preserved/improved by soft reroute for the rerouting connection.

With this capability the data loss due to grooming of connections is reduced as the new path is established before breaking the older path of a connection. This increases connection availability.

CWM based provisioning using the SNMP MIB is also supported.

Enhancements to Route Optimization

CWM 15 supports scheduled/on-demand route optimization. The existing commands are also enhanced to support "Orderly Grooming" and allow you to schedule the route optimization based on "day(s) of the week". Trunk utilization factor is introduced to prevent connections from grooming to heavily loaded trunks.

The enhancements to route optimization allow you to administer route optimization of connections from the CWM network management workstation. The route optimization enhancements also include orderly grooming and trunk utilization factor for effectively managing the network.

CWM based provisioning using the SNMP MIB is also supported.

MGX 8950, Release 5

Support for AXSM-16-155-XG

CWM 15 supports the AXSM-16-155-XG service module, which addresses the need for enhanced traffic management capabilities over a higher OC-3c/STM-1 port density.

The AXSM-16-155-XG service module supports ABR with VS/VD and per-VC/VP shaping on 128K connections and provides a full 2.4 Gbps of usable bandwidth per card. These enhancements help lower the cost of OC-3c/STM-1 port.for customers in need of the enhanced traffic management capabilities.

Support for soft rerouting

CWM 15 supports soft rerouting. In previous releases during the grooming process the connection was derouted and rerouted when the connection was on a PNNI routed path. Even when the better/desired route was unavailable the connection was derouted and rerouted using PNNI. The soft reroute feature enables you to move a routed SPVC/P from an incumbent working path to a new path with minimal loss of traffic. The existing connection along the path is not derouted until a connection has been established on a new path. Thus soft route brings higher connection availability. QoS is preserved/improved by soft reroute for the rerouting connection.

With this capability the data loss due to grooming of connections is reduced as the new path is established before breaking the older path of a connection. This increases connection availability.

CWM based provisioning using the SNMP MIB is also supported.

Enhancements to Route Optimization

CWM 15 supports scheduled/on-demand route optimization. The existing commands are also enhanced to support "Orderly Grooming" and allow you to schedule the route optimization based on "day(s) of the week". Trunk utilization factor is introduced to prevent connections from grooming to heavily loaded trunks.

The enhancements to route optimization allow you to administer route optimization of connections from the CWM network management workstation. The route optimization enhancements also include orderly grooming and trunk utilization factor for effectively managing the network.

CWM based provisioning using the SNMP MIB is also supported.

Release 1.3 (MGX 8850, 8250, 8230 with PXM1)

SRME/B Card

CWM 15 supports management of the SRME/B. The SRME/B adds T3/E3 interfaces to the current SRM-E which only supports OC-3 and STM-1 Electrical interfaces. This new SRME/B now supports T3/E3, OC-3 and STM-1 Electrical interfaces with the same front card. Bulk distribution to all 24 slots is now possible for the 8230/8250/8850 PXM1-based platforms.

SNTP Support

This feature allows all PXM1-based nodes to use SNTP or Simple Network Time Protocol to synchronize clocks within an internetwork of PXM1-based nodes. SNTP provides a comprehensive mechanism to access national time sources and adjust each nodes's clock to that time source. CWM support for SNTP on PXM1-based nodes is the same mechanism as supported by CWM on the MGX 8800 PXM45-based switches in prior releases.

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

Support for soft rerouting

CWM 15 supports soft rerouting. In previous releases during the grooming process the connection was derouted and rerouted when the connection was on a PNNI routed path. Even when the better/desired route was unavailable the connection was derouted and rerouted using PNNI. The soft reroute feature enables you to move a routed SPVC/P from an incumbent working path to a new path with minimal loss of traffic. The existing connection along the path is not derouted until a connection has been established on a new path. Thus soft route brings higher connection availability. QoS is preserved/improved by soft reroute for the rerouting connection.

With this capability the data loss due to grooming of connections is reduced as the new path is established before breaking the older path of a connection. This increases connection availability.

CWM based provisioning using the SNMP MIB is also supported.

Enhancements to Route Optimization

CWM 15 supports scheduled/on-demand route optimization. The existing commands are also enhanced to support "Orderly Grooming" and allow you to schedule the route optimization based on "day(s) of the week". Trunk utilization factor is introduced to prevent connections from grooming to heavily loaded trunks.

The enhancements to route optimization allow you to administer route optimization of connections from the CWM network management workstation. The route optimization enhancements also include orderly grooming and trunk utilization factor for effectively managing the network.

CWM based provisioning using the SNMP MIB is also supported.

VISM 3.2

The VISM 3.2 features listed below apply to the PXM45-based MGX 8850 and MGX 8880 nodes, the PXM1E-based MGX 8850 and MGX 8830 nodes running Release 5 and the PXM1-based MGX 8850, MGX 8250, and MGX 8230 nodes running Release 1.3.

Support for the Lossless CODEC

CWM 15 supports the new compression technique (lossless compression CODEC) in the DSP (for VISM-PR Release 3.2), which enables Wireless Service Providers to reduce the number of leased lines needed to backhaul traffic from a cell site (BTS) to the central office (BSC).

Support for Tone Detection

CWM 15 supports the detection of a small subset of commonly used Call Progress tones now that VISM-PR reports these tones to the Call Agent as RFC2833 specified events.

Support for 3-Way Conferencing

CWM 15 supports the 3 way conference capability. The three-way calling service allows an end user already engaged in a two-party call to add a third party to the conversation.

Support for IMA Auto Restart

CWM 15 supports IMA auto restart configuration using the Equipment Manager and service agent. The auto-restart functionality to be configured and displayed through Configuration Center. You can also view the auto-restart attribute using inspector view. IMA auto restart applies to the PXM45-based MGX 8850 nodes with the AXSME-32T1E1 running Release 5 and the PXM1E-based MGX 8850 and MGX 8830 nodes with the PXM1E-16T1E1 running Release 5.

Support for the Preferred Route Indicator

CWM 15 supports the Preferred Route Indicator feature for PXM45-based MGX 8850 and/or MGX 8950 nodes and/or PXM1E-based MGX 8850 and MGX 8830 nodes running Release 5. For more information about configuring and managing preferred routes, refer either to the online help or to the appropriate section in the Cisco WAN Manager User's Guide, Release 15 at the following URL:

http://www.cisco.com/univercd/cc/td/doc/product/wanbu/svplus/15/ug/devices.htm#wp1134735

Support for configurable AUSM cell dropping criteria

CWM 15 allows you to configure the criteria for dropping cells on AUSM cards. Depending upon the configuration Frame Based Discard or CLP threshold can be used for determining the criteria for dropping cells.

Support for Test delay through the SNMP Service Agent

CWM 15 allows you to execute delay tests between given OAM segment endpoints on PXM45-based MGX 8850 nodes and/or PXM1E-based MGX 8850 and MGX 8830 nodes running Release 5.using the SNMP Service Agent.

Support for VPI = 0

CWM 15 now supports the configuration of VPI = 0 for AXSM port resource partitions. For more information about configuring and managing VPI = 0 for AXSM port resource partitions, refer either to the online help or to the appropriate section in the Cisco WAN Manager User's Guide, Release 15 at the following URL:

http://www.cisco.com/univercd/cc/td/doc/product/wanbu/svplus/15/ug/index.html

CWM-specific Enhancements

New Graphical User Interface

CWM 15 introduces a new Graphical User Interface. For an overview of the look and feel of this new interface, refer to the Cisco WAN Manager User's Guide, Release 15 at the following URL:

http://www.cisco.com/univercd/cc/td/doc/product/wanbu/svplus/15/ug/index.html

Here's a list of the changes you'll see:

The following applications are new in CWM 15:

Network Monitor Application (for Inventory and Alarms)

Configuration Center (for provisioning)

Diagnostics Center (for running diagnostics)

Object Finder (for finding objects based on user queries)

Statistics Reporting Tool

ChassisView

On-line Help

The following CWM 12 and earlier applications have been replaced in CWM 15:

Topology: Replaced by Network Monitor.

Network Browser: Replaced by Network Monitor and Configuration Center.

CiscoView: Replaced by Configuration Center, Diagnostics Center and Chassis View.

Connection Manager: Absorbed into Configuration Center.

Wingz: Replaced by Statistics Reporting Tool.

Support for WANDEST 2.5

Support for AXSM-E Port Statistics

Support for AXSM-E Level 3 Statistics

Support for new PXM1 Port Statistics

Support for additional AUSM Port Statistics

Support for additional FRSM Connection and Port Statistics

XPVC/XPVP Management Enhancement

XPVC connection data no longer requires the manual XPVC grooming tool during upgrade to CWM 15. XPVC connections are now discovered from the network by CWM 15.

AXSM-E level 3 Statistics

AIS delay grooming

WANDEST 2.5-Specific Enhancements

Selectable Triggers for Database Tables

Prior to Release 2.5, every table within the stratacom database was accessed by WANDEST, regardless of whether you used the table or not. Now you can select the tables you need. Refer to the WANDEST Installation and Reference, Release 2.5 for more information on setting up this feature.

Features Not Supported and Known Feature Limitations in 15.0.00

The following features are not supported in CWM 15.0.00:

CID level traps are not sent to CWM to prevent potential trap flooding.

CID level statistics are not available in bulk statistics file format from the VXSM modules.

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

Bulk statistics for VISM are not supported

Several screens display fields relating to the MPSM-T3E3-155 Multi-Link Frame Relay (MLFR) feature, which is not currently supported

When managing VISM service modules that are running 3.2.10, CWM only supports the 3.2 features

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

TGCP

Dynamic Payload

T.38 Fax Relay.

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

The following cards are not supported by CWM 15.0.00:

The BME card is not supported.

The FRSM12 service module is not supported.

Limitations

1. Pointing multiple CWM workstations at the same gateway node is not recommended.

2. CWM does not support use of the Korn Shell.

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

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


Step 1 Stop core, exit out of the CWM prompt

Step 2 Run stoporbix2000 script

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

Step 4 Start core.


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

Exception raised while calling activateLease on 
pseudoServer.IT_ATLI_IOP:CONNECTION_CREATION_TIMEOUT

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

12. When you have the persistent topology feature enabled, to decommission a node in the network and take it out of the topology you must delete the node from the persistent topology data using the switch CLI To decommission a node or to delete a trunk from the PNNI network, the entry needs to be deleted from the persistent gateway nodes.

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

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

15. Manual node resync may look like it failed due to the GUI timing out for PXM45/PXM1E-based Cisco MGX nodes with many connections (i.e. 400K dax endpoints).

16. In order to correctly manage feeder nodes after they have been moved, you must first delete all trunks from the old node using the CLI before adding the feeder back onto the system.

17. When a back card is removed when there is no provisioning on the front card the card alarm status reported by CWM will be inconsistent with what the switch reports. CWM reports a major alarm with the description "Back Card; not present" whenever a back card is removed. However, the switch may not show an alarm if there is no provisioning on the front card. Manually clear the major alarm after determining this is not a real alarm condition since there is no provisioning on the card.

18. After executing a clrsmcnf command for AXSM from the switch CLI, ChassisView shows the AXSM front card once the card is active, but no backcard is found. To get ChassisView to recognize the back card again, you need to execute a first level manual node resync.

19. RPM-PR and RPM-XF ports/subinterfaces need to be configured with a number less than 32767. If you have configured any ports or subinterfaces with a number greater than 32767 you must delete them and then re-add them using a number less than 32767.

20. If you register an SNMP Manager with the SNMP Agent without changing the bit-mask (i.e. accept the default of FFFFFFFFFFFFFFFF), you get all SNMP traps, including 25302 and 25303.

If you register the SNMP Manager with a non-default bit-mask because you do not want certain groups (Example: FFFFFFFFF10701555), then you do not get trap 25302 and 25303, even though you have registered for that group.

If you deselect a currently undefined group like group 28, which is a bitmask of FFFFFFFFEFFFFFFF, you can then add traps 25302 and 25303 by editing the trap_filter.conf file and adding the following lines to GROUP 20 # Network Connectivity Status Change Traps:

TRAP 25302

TRAP 25303

21. Preforming a switchcc command on a controller card in an IGX or BPX node forces CWM to resync with the node again.This will cause a delay in receiving status information.

22. Changing the line type/payload type/medium type of VXSM-4OC3 causes CWM to do a whole card resync. This card resync will occur when you do any of the following:

change the medium type between Sonet and SDH for sonet physical line

change the payload type between T1 (VT 1.5 VC 11) and E1(VT 2 VC 12) for STS path or STM (Au) path

change the payload type between T1 (VT 1.5 VC 11) and DS3 for STS path

change the tributary path between Au4 and Au3 for STM path in SDH medium

A whole card resync takes several minutes to complete.

23. If you remove and then immediately add back the same IGX feeder while CWM is running, CWM establishes 2 LINK 0's with the node. This is treated as a delete and the node will be deleted.

In this situation, Cisco recommends you either remove and add the feeder while CWM is down, or, after adding the feeder, restart CWM.

24. Changes to the node name from the Configuration Center are updated automatically in the Tree View and in the Inspector View. However, the node name in the title bar of the internal frame does not update automatically. To change the title bar of the internal frame to reflect a change to the node name, close the internal frame and re-open it

The attribute values in the internal frame can be updated by using the Refresh button of that internal frame.

25. After it is modified using snmpset,.the Line Send parameter LineSendCode is not getting updated by the database, which shows the parameter as inapplicable (shows the value as -1).Refer to CSCin50480 for more information.

26. The "l_network_id" field in the connection segment or port tables may not be populated correctly. To ensure collection of an accurate network ID, use the "netw_id" field from the "node" table.

27. If you are managing a PXM45-based MGX node running any supported release earlier than 4.0.10 CWM 15 will not populate the "peripheral" table.

28. If you are managing a PXM45-based MGX node running 4.0.10 or any supported release later than 4.0.10 the "status" field in the "peripheral" table will only be populated or updated during node resync.

29. If you are managing a PXM1-based MGX node the "status" field in the "peripheral" table will not be populated.

30. If the log level for CWM EM module is set too high or above production default value and there are a lot of configuration changes on the switch during warm start, the sync up performance will be impacted during warm start.

31. SmartLogging is a special feature for CWM debugging available when the log level is set to Level 2. It will dump a configurable number of detailed log messages to log files for each Level 2 log message.

For example, when SmartLogging is enabled, an SNMP failure which triggers a Level 2 log message will cause a dump of log messages at all levels immediately prior to and following this event. The SmartLogging feature may have performance impact, due to excessive log messages. It should be disabled in normal operation and enabled only when needed for special investigation.

32. The Forced Deletion feature does not support XPVC connections. XPVC connections cannot be force deleted.

33. Using the Forced Deletion feature to remove an unused connection descriptor only removes the unused descriptor from the workstation it is performed on. Other gateway workstations will still show the descriptor.

You must force delete the unused descriptor at each gateway workstation to clear it completely.

34. Occasionally, when you move linked nodes around in the Topology screen, the link does not automatically follow the nodes. When this happens, it looks like the link is not connected to the nodes. The workaround is to either move the affected nodes around within the window or refresh the Topology screen Once the screen refreshes, the link will automatically appear connected to the appropriate nodes again.

35. Using the "Group Nodes" feature only affects your view of the networks. Other users (even those who log into your workstation) will not see the groups you have made.

36. After a previously saved configuration file is loaded using the Config Save & Restore feature of CWM, the Tree View continues to show some ports that are not in the restored configuration file. Attempting to configure these ports results in an error. The workaround is to perform a manual node resync.

37. When setting up VISM connections the VPI value in the VPI/VCI Selector window defaults to zero. You must manually enter the VPI value, as zero is invalid. The range for the VPI value for VISM cards is one through the highest available slot number on the node.

38. Ports on PXM45-based nodes which are associated to a trunk display as Trunk Ports, however, ports that are carrying signalling protocol information display as User Ports. Since they are carrying information, you cannot provision connections on these ports. Attempting to do so results in an error being displayed. Choose another port.

39. Virtual Ports on BPX are displayed in the Tree View application under the physical Line section as physicalPort.virtualPort.

40. The PNNI ports on the PXM1 card of an SES node are not displayed in the Tree View application.

41. The administrative state of the PNNI ports is not aggregated into the total administrative state of the port. The InspectorView application shows both the total administrative state of the port and the administrative state of the PNNI ports as two separate items.

42. The Loss of Cell Delineation alarm on AXSME, AXSM-XG, and/or MPSMOC3 cards may not get propagated from the switch to CWM. For the AXSM cards, a line/path alarm will be present, but the MPSMOC3 card could have an LOCD alarm triggered without any line/path alarm present. The line would show in CWM as clear, while actually being in alarm.

43. With MPSM-OC3 cards, after you replace an OC3 back card with a DS3 or vice versa you need to do a coldstart.

Configuration Center Limitations

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

The Connection Management section of the Configuration Center GUI for preferred route displays all available trunks without considering the traffic class. As a result, it is possible to set a preferred route for a CBR connection traversing trunks that do not support CBR traffic.

While adding connections originating and terminating on the same feeder nodes (MGX8220 only), CWM will treat these connections as three segment connections and will add three segments (two on the same feeder node, one on the routing node) to realize this connection.

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

Occasionally, when the databroker is busy, while deleting SPVC connections on a PXM1E-based node the following error message may display:

error "can not delete connections. Failed to communicate with databroker".

This error message can safely be ignored, because the connections are correctly deleted on the switch.

HP OpenView Limitations

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

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

Issues with the CWM 15 Statistics Collection Manager

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

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

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

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

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

Only 15 minute collection buckets are supported for PNNI statistics.

Peak statistics are not supported for PNNI statistics.

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

The BPX-SES does not support PNNI statistics collection.

Statistical Alarms for lines on PXM45-based MGX nodes are not supported in CWM.

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

28 dsx3LCVCurrent

29 dsx3LESCurrent

30 dsx3LSESCurrent

31 dsx3PCVCurrent

32 dsx3PESCurrent

33 dsx3PSESCurrent

34 dsx3CCVCurrent

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

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

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

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

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

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

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

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

Limitations for CWM to CWM Communication

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

All the CWM workstations managing the same network must have seed nodes or gateway nodes that have IP addresses within the same network. All the CWM workstations should not all point to the same gateway node, but the gateway nodes they point to should be on the same network.

If an IP address is entered as gateway in the network.conf file and the DNS entry is missing for the gateway node IP address, the Auto-Route network will not be discovered.

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

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

Network Monitor Limitations

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

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

In CWM 15.0.00 and later, the SHOW_TOPO_VIEW flag in the CMSCClient.conf file is used to configure whether or not nodes and trunks are displayed in the topology display of the Network Monitor application at CWM startup.

TOPO_SHOW_VIEW 1 means when NWTopology opens, users can see nodes and trunks in the topology.

TOPO_SHOW_VIEW 0 means when NWTopology opens, users cannot see nodes and trunks in the topology.

In releases prior to CWM 15.0.00, a flag named TOPO_SHOW_MAP in the /usr/users/svplus/config/CwmGs.conf file was used to configure whether or not nodes and trunks are displayed in the topology display of the Network Monitor application at CWM startup.

The TOPO_SHOW_MAP flag is obsolete. Use the SHOW_TOPO_VIEW flag in the CMSCClient.conf file instead.

CWM 15 Notes and Cautions

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

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


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


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

CWM 15 Server Installation or Upgrade to CWM 15, Patch 2


Note CWM 15.0.00, patch 2 can only be installed on a CWM 15 base. To upgrade from an earlier release, refer to the CWM 15.0.00 release notes and the CWM Installation Guide, Release 15 (OL-4550-01). You can upgrade to CWM 15.0.00 from CWM 12.0.00 Patch 2, or 11.0.10 patch 4.1


The most current upgrade and installation information for CWM 15 is found in the CWM Installation Guide, Release 15 (OL-4550-01). A PDF copy of this document is on the CWM 15 Documentation CD. The following sections describe installation and upgrade procedures specific to CWM 15.0.00 patch 2.


Note The patch installation log file might contain error messages like
can not backup "data/scm/srtfilterlist.unl" No such file or directory
This occurs if the patch installation contains a new file which is not present in the already installed version. This type of messages can be safely ignored.


CWM 15.0.00 Patch 2 Installation

Contents of this patch:

CWM Server

15.0.00-P2_CWM.tar.gz (including Informix 9.21.UC7XO)

CWM SNMP Agent

15.0.00-P2_SNMPAgent.tar.gz

CWM SSC (Standalone Statistics Collector)

15.0.00-P2_SSC.tar.gz

CWM SSM (Standalone Statistics Manager)

15.0.00-P2_SSM.tar.gz

WANDEST Server 2.5 Patch 2

wandest2.5-P2_wdserver.tar.gz

WANDEST Client 2.5 Patch 2

wandest2.5-P2_wdclient.tar.gz

RTM Proxy

15.0.00-P2_RTMProxy.tar.gz


Note The RTM Proxy Patch 2 tar file is for the purpose of working with Standalone Statistic Manager only. Not for northbound interface. If Service agent is installed do not install the RTM proxy patch. It is not needed.


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


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


To do a backup of databases do the following:


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

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

Step 2 Do the following to export the databases

a. Log in as svplus

hostname# su -u svplus

The system prompts you for the svplus password:

password:

b. Stop the core.

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

# coldstart
 

d. Export stratacom database

# dbexport stratacom -o <dbexport-location>

e. Export scmdb database

# dbexport scmdb -o <dbexport-location>

f. Export statsdb database

# dbexport statsdb -o <dbexport-location>

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

# dbexport wandest -o <dbexport-location>

Step 4 Get the output of onstat -d

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


Installing the CWM Server Patch


Step 1 Login to the CWM server as user root



Step 2 Download or copy the compressed tar files for CWM Server to a temporary location, for example, /tmp

# cp 15.0.00-P2_CWM.tar.gz /tmp

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

# cd /tmp

Step 4 Remove the disk1 directory

# rm -rf disk1

Step 5 Decompress the compressed tar files

# gunzip 15.0.00-P2_CWM.tar.gz 

Step 6 Extract the tar file

# tar -xvf 15.0.00-P2_CWM.tar

Step 7 Execute the InstallCWM15Patch2.csh script to begin the install process by entering the following command:

# ./InstallCWM15Patch2.csh


Note The patch install process will install a generic version of the CWMGateway.conf file. Be sure to restore the backup copy after installing the patch. The system will prompt you with a message regarding the name of the backed-up CWMGateway.conf file before installing the patch.


The following message is displayed.

CWMGateway.conf file is backed up as CWMGateway.conf_15.0.00, Please update the new 
CWMGateway.conf file with the changes available in the original file after the Patch 
Installation is completed. Press Enter to continue...

After you press Enter, the following message is displayed.


Console Mode Option is recommended when you cannot connect to X Server 
 from current terminal (See if you can open an xterm to check!) 


 Do you Want to Launch Installer in Console Mode? (Yes / No): [No]:

Step 8 Respond No to continue the installation using the Installshield GUI.
Respond Yes to continue the installation using Console Mode Install.


Note Console Mode Install is a command line script procedure. It is an alternative to the GUI and is intended for users who do not have access to an X window device. Using Console Mode Install, the user can install CWM using an alpha-numeric terminal or a PC in terminal emulator mode.


The following examples assume you answered No to continue the installation using the Installshield GUI.

The following welcome screen displays:

Accept the terms of the License Agreement by selecting the appropriate radio button, then click the Next button.

The next screen prompts you to provide the backup directory location:

The directory you enter here is where the patch install program will copy your existing CWM version before installing the patch. The files in this directory will be needed in the event you want to uninstall the patch.


Caution Do not set this directory to /tmp as all the files in the tmp directory are lost if the workstation is rebooted.

The next screen prompts you to select whether or not you want to use the forced delete feature. For more information on this feature, refer to the "Using the Forced Delete Feature" section:

An example of the screen follows:

Select the appropriate radio button, then click the Next button.

The next screen displays what will be installed (15.0.00 Patch 2), which directory it will be installed in, and how much disk space it will take.

:

Confirm that the information is correct, then click on the Next button. The files begin to install, as shown in the next screen.

Once the install is finished, the finished installing screen displays. Click on the Finish button to exit from the InstallShield program.

Step 9 If WANDEST Server 2.5 is installed on this machine, do the following:

Stop the wdclient

Exit root

Run the /usr/users/svplus/scripts/get_dbschema.ksh shell script

For example,

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

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

Download or copy the wandest2.5-P2_wdserver.tar.gz to the local directory. For example, /tmp

Change to that local directory and uncompress the gzip file

For example, # gunzip wandest2.5-P2_wdserver.tar.gz

Untar the tar file

For example, # tar -xvf wandest2.5-P2_wdserver.tar

Switch to root

Run the installation script to install the patch

For example, # ./InstallWD25Patch2.csh

Step 10 Exit from root


Verifying and Restoring Your Saved Database After Installing Patch 2

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


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



Step 1 Become user root

# su

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

# cd /usr/users/informix92/etc

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

a. open onconfig file

# vi onconfig
 

b. Change the following line

                 PHYSDBS          phydbs

to

                 PHYSDBS          rootdbs

c. Change the following line

                 PHYSFILE        <size>
 

to

                 PHYSFILE        20000

d. Save the onconfig file and exit from the editor

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

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

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

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

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

# ./AddPhyLog
# ./RestartInf

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

# ./dbaddchunk

Step 8 Exit from root

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

# onstat -d

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

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

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

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

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

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

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

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

Step 12 If you had WANDEST server before then execute the following command

# dbimport wandest  -i <dbexport-location>

Installing the CWM SNMP Agent (Service Agent) Patch:


Step 1 Login to the CWM server as user root



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


cp 15.0.00-P2_SNMPagent.tar.gz /tmp

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

# cd /tmp

Step 4 Remove the disk1 directory

# rm -rf disk1

Step 5 Decompress the compressed tar files

# gunzip 15.0.00-P2_SNMPagent.tar.gz 

Step 6 Extract the tar file

# tar -xvf 15.0.00-P2_SNMPagent.tar

Step 7 Execute the InstallSNMPAgent15Patch2.csh script:

# ./InstallSNMPAgent15Patch2.csh 

The following message is displayed.


Console Mode Option is recommended when you cannot connect to X Server 
 from current terminal (See if you can open an xterm to check!) 


 Do you Want to Launch Installer in Console Mode? (Yes / No): [No]:

Step 8 Respond No to continue the installation using the Installshield GUI.
Respond Yes to continue the installation using Console Mode Install.


Note Console Mode Install is a command line script procedure. It is an alternative to the GUI and is intended for users who do not have access to an X window device. Using Console Mode Install, the user can install CWM using an alpha-numeric terminal or a PC in terminal emulator mode.


The following examples assume you answered No to continue the installation using the Installshield GUI.

The following welcome screen displays:

Click on the Next button. The License Agreement screen displays, as shown below:

Accept the terms of the License Agreement by selecting the appropriate radio button, then click the Next button.

The next screen prompts you to provide the backup directory location:

The directory you enter here is where the patch install program will copy your existing CWM version before installing the patch. The files in this directory will be needed in the event you want to uninstall the patch.


Caution Do not set this directory to /tmp as all the files in the tmp directory are lost if the workstation is rebooted.

The next screen displays what will be installed (SNMP Agent Patch 2), which directory it will be installed in, and how much disk space it will take.

Confirm that the information is correct, then click on the Next button. The files begin to install, as shown in the next screen.

Once the install is finished, the following screen displays:

Click on the Finish button to exit from the InstallShield program.

Step 9 Exit from root.


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


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



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

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


cp 15.0.00-P2_SSC.tar.gz /tmp

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

# cd /tmp

Step 4 Remove the disk1 directory

# rm -rf disk1

Step 5 Decompress the compressed tar files

# gunzip 15.0.00-P2_SSC.tar.gz 

Step 6 Extract the tar file

# tar xvf 15.0.00-P2_SSC.tar

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

# ./InstallSSC15Patch2.csh

The following message is displayed.


Console Mode Option is recommended when you cannot connect to X Server 
 from current terminal (See if you can open an xterm to check!) 


 Do you Want to Launch Installer in Console Mode? (Yes / No): [No]:

Step 8 Respond No to continue the installation using the Installshield GUI.
Respond Yes to continue the installation using Console Mode Install.


Note Console Mode Install is a command line script procedure. It is an alternative to the GUI and is intended for users who do not have access to an X window device. Using Console Mode Install, the user can install CWM using an alpha-numeric terminal or a PC in terminal emulator mode.


The following examples assume you answered No to continue the installation using the Installshield GUI.


Step 9 Exit from root.


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


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



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

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


cp 15.0.00-P2_SSM.tar.gz /tmp

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

# cd /tmp

Step 4 Remove the disk1 directory

# rm -rf disk1

Step 5 Decompress the compressed tar files

# gunzip 15.0.00-P2_SSM.tar.gz 

Step 6 Extract the tar file

# tar xvf 15.0.00-P2_SSM.tar

Step 7 Check for the file InstallSCM15Patch2.csh script file and begin the install process by entering the following command:

# ./InstallSSM15Patch2.csh

Step 8 Exit from root.


Installing the CWM RTM Proxy Patch on the CWM Machine:


Note RTM Proxy Patch 2 tar file is for the purpose of working with Standalone Statistics Manager only. Not for northbound interface.
This patch installation is to be performed only on CWM machine which has no SNMP Agent and which is used by SSM for statistics management.



Step 1 Login to the CWM machine as user root

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


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


# cd /tmp

Step 4 Remove the disk1 directory

# rm -rf disk1

Step 5 Decompress the compressed tar files

# gunzip 15.0.00-P2_RTMProxy.tar.gz

Step 6 Extract the tar file

# tar xvf 15.0.00-P2_RTMProxy.tar

Step 7 Execute the InstallRTMProxy15Patch2.csh script:

# ./InstallRTMProxy15Patch2.csh

The following message is displayed.


Console Mode Option is recommended when you cannot connect to X Server 
 from current terminal (See if you can open an xterm to check!) 


 Do you Want to Launch Installer in Console Mode? (Yes / No): [No]:

Step 8 Respond No to continue the installation using the Installshield GUI.
Respond Yes to continue the installation using Console Mode Install.


Note Console Mode Install is a command line script procedure. It is an alternative to the GUI and is intended for users who do not have access to an X window device. Using Console Mode Install, the user can install CWM using an alpha-numeric terminal or a PC in terminal emulator mode.


The following examples assume you answered No to continue the installation using the Installshield GUI.

The following welcome screen displays:

Click on the Next button. The License Agreement screen displays, as shown below:

Accept the terms of the License Agreement by selecting the appropriate radio button, then click the Next button.

The next screen prompts you to provide the backup directory location:

The directory you enter here is where the patch install program will copy your existing CWM version before installing the patch. The files in this directory will be needed in the event you want to uninstall the patch.


Caution Do not set this directory to /tmp as all the files in the tmp directory are lost if the workstation is rebooted.

The next screen displays what will be installed (SNMP Agent Patch 2), which directory it will be installed in, and how much disk space it will take.

Confirm that the information is correct, then click on the Next button. The files begin to install, as shown in the next screen.

Once the install is finished, the finished installing screen displays. Click on the Finish button to exit from the InstallShield program.

Step 9 Exit from root


WANDEST Release 2.5, Patch 2

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

Contents of This Patch

WANDEST Server

wandest2.5-P2_wdserver.tar.gz

WANDEST Client

wandest2.5-P2_wdclient.tar.gz

Installing the WANDEST Server Patch:


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



Step 1 Login to the CWM workstation as user svplus

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


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

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

Step 3 Login to the CWM workstation as user root

Step 4 Download or copy the server tar file to the local directory. for example, /tmp

# cp wandest2.5-P2.wdserver.tar.gz /tmp

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

# cd /tmp

Step 6 Remove the disk1 directory

# rm -rf disk1

Step 7 Decompress the compressed tar files

# gunzip wandest2.5-P2_wdserver.tar.gz 

Step 8 Extract the tar file

# tar xvf wandest2.5-P2_wdserver.tar

Step 9 Run the installation script to install the patch:

# ./InstallWD25ServerPatch2.csh

Step 10 Exit from root.


Installing the WANDEST Client Patch:


Step 1 Login to the Wandest client as user root

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

# cp wandest2.5-P2_wdclient.tar.gz /tmp

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

# cd /tmp

Step 4 Remove the disk1 directory

# rm -rf disk1

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

# gunzip wandest2.5-P2_wdclient.tar.gz 

Step 6 Untar the tar file:

# tar xvfp wandest2.5-P2_wdclient.tar

Step 7 Run the installation script to install the patch:

# ./InstallWD25ClientPatch2.csh

Step 8 Exit from root.


Uninstalling Patch 2

The patch installation process installs an uninstall script in the /usr/users/svplus directory for CWM and in the /usr/users/wandest directory for Wandest. When you bring up the uninstall wizard, it will ask for the backup file location that you provided when you installed patch 2.

Important Configuration Notes

This section provides important information about configuration.

Naming Managed Nodes

Each node name of all the nodes managed by CWM must be unique. Duplicate node names are detected if both node names are found in the PNNI networks. Duplicate node names are not detected if one node is in the AutoRoute network and the other node is in the PNNI network.

Using the Forced Delete Feature

The Release 15 Patch 2 release introduces the Forced Delete feature. This new feature allows you to remove dangling connections and unused connection descriptors from the network.


Note If you are not given permission to perform a force delete operation, the following options are not displayed in the Configuration Center

Force Delete button is not displayed in the Connection Browser

The Edit menu does not display the Show Unused Descriptors option.


Procedure to Force Delete Connections

To remove dangling connections from the network, complete the following procedure:


Step 1 Click the Connection List tab to display the Connection Browser window (see Figure 1).

Step 2 Move the object, for example, node, card, line, or port from the Hierarchical Tree to the Local Endpoint ID or Remote Endpoint ID field.

Step 3 Enter the number of connections you want to retrieve in the Connection Count to be retrieved field. To retrieve all the connections, enter *. By default, * is displayed.

Step 4 Click Get.

Step 5 Select one or more connections from the list of connections (see Figure 1).

Figure 1 Configuration Center—List of Connections (Force Delete Example)

Step 6 Click Force Delete to forcefully delete the connections from the network.

Step 7 Click OK to proceed with the force delete for the selected connections (see Figure 2).

Figure 2 Configuration Center—Force Delete Connections (Confirm) Window

Step 8 If successful, click OK to close the Force Deleting Connections (success) window (see Figure 3).

Figure 3 Configuration Center—Force Deleting Connections (Success) Window

The letter `d' appears in the Add/Del Flag column for the forced delete connection.

If some network segments failed to get deleted, you are prompted with the following error message:

Can't Delete the Connection(s): 
Some segments may be on the network.

Click OK to acknowledge the forced delete error message.


Note You can delete the failed endpoints from the switch command line interface (CLI).



Procedure to Delete Unused Connection Descriptors

Unused connection descriptors are in the CWM database but are not associated with any connection.

To remove the unused connection descriptors, complete the following procedure:


Step 1 Choose Edit > Show Unused Descriptors to display the Unused Descriptor List window (see Figure 4).

Figure 4 Configuration Center—Unused Descriptor List Window

Step 2 Select one or more connection descriptor entries.

Step 3 Click Delete to remove the unused connection descriptors from the CWM database.


Core File Management

Core files used to be created without unique names, and overwritten. Now for each core dump a unique directory is created under ~svplus/corefilesdir/.

Each directory is named <Core.<processName>.<pid>.mmddHrMinSec

Within these directories, the core file will be "<processName>.<pid>.mmddHrMinSec.core the Information file with dmesg, onstat -d, pstack and other details will be named "<processName>.<pid>.mmddHrMinSec.info", and the o corresponding log file(s) will be "<processName>.<pid>.log"

Cisco Info Center Version

The 15.0.00-P2_SNMPAgent.tar.gz file contains the CIC36Pipp001CWM15.tar file, which contains rule files that are only compatible with CIC version 3.6.1. You need to install CIC 3.6.1 to use these rule files.

If you want to continue to use CIC version 3.6.0 or 3.5 with CWM 15 Patch 2, save and then apply the CIC36Pipp000CWM15 tar file that is available in the CWM15.0.00 SNMP Agent CD instead.

For more information on CIC, refer to the following URL:

http://www.cisco.com/univercd/cc/td/doc/product/rtrmgmt/info_ctr/3_6/index.htm

C-Note/CWM Configuration

The C-Note version supported by CWM 15 patch 2 is 3.

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

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

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

The line you add should look like this:

<ipAddress>172.28.140.218</ipAddress>

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

Node Numbering for Release 9.4 IGX Feeder Nodes

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

Security Profiles

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

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

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

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

With the Patch 2 release, the ability to set permissions for adding, deleting or modifying network partitions or subnetworks is configurable using the Security Manager GUI.

CWM Database

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


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


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

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

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

RPM Management Limitations

RPM-PR is not supported on MGX PXM1-based nodes managed by ChassisView in CWM 15. The applicable trap is missing so CWM cannot monitor the back card.

For both RPM and RPM-PR cards managed by ChassisView in CWM 15 that are in stand-by state, the card status displays as blue. For other types of cards, stand-by card status displays as yellow.

For both the RPM and RPM-PR card types hardware and firmware revisions are not populated in the database.

For the RPM-PR card type the front card description displays "RPM" instead of "RPM-PR".

The RPM back card support feature is disabled by default. Customers interested in obtaining the RPM back card information should enable this feature by editing the emd.conf file before starting the CWM core. If this feature is enabled, the back card information is polled from the switch only during a coldstart or a manual resync. After the coldstart or manual resync completes, any changes to the back card configuration or status will not be updated until you execute another coldstart or a manual resync.

CWM does not distinguish between the Ethernet back card versions installed with the MGX-RPM-128M/B or RPM-PR. There is no functionality difference.

ChassisView Operation After Card and Line Switchovers

When two cards are in a redundancy relationship, the primary card (i.e. the logical slot) is used to display the ports and lines for all provisioning and troubleshooting activities, even if the primary slot becomes a standby. The secondary slot does not show any ports and lines under it even after it becomes active. Provisioning is only allowed on the working line of an APS pair, irrespective of whether that line is currently active or not. However, both the working and protection lines are monitored.

In ChassisView, the ports on the card only display if they are available. Ports do not display on the secondary slot, even after it becomes active. The backcard appears as blank, not with greyed out ports as in previous releases that used CiscoView for equipment management.

Equipment Management Configuration Notes

In the emd.conf file, the following two parameters will need to be customized depending on network.

The OORequest parameter defines the number of configuration files per node that can be requested at one time. You can request a maximum of 32 configuration files concurrently per node. The range is 1 through 32, and the default is 32.

The OOStart parameter defines the number of OOEMC child processes. The range is 1 through 25, and the default is 6.

All the PNNI nodes managed by CWM (PXM45-based 8950, 8880, & 8850 nodes, PXM1E- based 8950, 8850, & 8830 nodes, and BPX nodes with SES shelves) are distributed among OOEMC processes.

The number of nodes managed by a single process is computed by dividing the total number of PNNI nodes in the network by the number of processes is defined by OOStart. Let us name this computed number of nodes managed by a single process the MANAGED_NODE_COUNT.

Then, MANAGED_NODE_COUNT * OORequest must be less than or equal to 200.

This can be achieved by either increasing the OOStart or reducing the OORequest. The normal range of OOStart is 5-20.

If the OOStart parameter value is increased beyond 10 then the number of DMD processes has to be increased or a shared memory overflow will occur.

Network Monitor Server Configuration File (NMServer.conf)

There are two parameters (HELLO_EVENT_INTERVALand EVENT_REDELIVERY_COUNT) in the NMServer.conf configuration file.that are tied to the NMSERVER_DISCONNECT_TIMEOUT parameter in the CMSCClient.conf client configuration file.

The NMSERVER_DISCONNECT_TIMEOUT parameter value needs to be set to the same as the HELLO_EVENT_INTERVAL value times the EVENT_REDELIVERY_COUNT value. the range for HELLO_EVENT_INTERVAL is 0 through 60, the default is 60. The range for EVENT_REDELIVERY_COUNT is 0 through 3. The default is 3. The default for the NMSERVER_DISCONNECT_TIMEOUT parameter is 60 times 3 or 180.

If you change any of these parameters they must be adjusted so the HELLO_EVENT_INTERVAL value times the EVENT_REDELIVERY_COUNT value continues to equal the NMSERVER_DISCONNECT_TIMEOUT parameter value.

The Network Monitor Server configuration file (NMServer.conf) also contains the PERIODIC_RESYNC_INTERVAL parameter. This parameter defines the interval in hours between periodic resyncs. The range is 2 through 24, and the default is 8. You can also disable the periodic resync feature by setting the PERIODIC_RESYNC_INTERVAL parameter to 0.

Creating and Configuring a CWM Auto-Restart Shell Script

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

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

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


Step 1 Login to the CWM workstation as user root

$ su 

Step 2 Change to directory /etc/rc3.d

# cd /etc/rc3.d 

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

# vi /etc/rc3.d/S99init_sv 

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

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

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

#!/bin/sh

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

# Start Orbix E2A ... as svplus

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

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


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

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


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


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

# chmod 755 S99init_sv 


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


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


SNMP Service Agent Release Notes

Trap Limitation with PXM1-based MGX Nodes

The type of traps collected by CWM from connection addition and modification on Cisco MGX PXM1-based nodes running release 1.3.00 and onwards can be configured using the following new CLI commands:

cnfchantrapenbl

dspchantrapenbl

Use these commands to select either DEFAULT: the same legacy traps plus trap 50601 to be sent, or ENABLE: only trap 50601 to be sent for every connection addition or modification.

If the dspchantrapenbl CLI command is set to DEFAULT, you can use the cnfchantrapenbl ENABLE CLI command to change to only collecting trap 50601 while CWM 15 is running.

However, if you are currently only collecting trap 50601 (the dspchantrapenbl CLI command is set to ENABLE), and you decide to configure the node to send legacy traps for every connection addition or modification by executing the cnfchantrapenbl DEFAULT CLI command, all CWM workstations monitoring the node must be in shutdown state (the core should be stopped) before you execute the command.

To determine which CWM workstations are managing the node, run the dsptrapmgr command.

Caveats

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

Known Anomalies in CWM 15 Software

This section lists known anomalies in CWM Release 15 software as of 08/18/04

.

Table 7 Known Anomalies in CWM Release 15 Software 

Bug ID
Description

CSCed49023

CWM does not get trap for path LOCD alarm

Symptom:

Path is in alarm on switch, clear in CWM

Condition:

Have an IMA link between 2 ds1 paths and then delete the IMA link from one side. CWM doesn't get the trap for the path alarm.

Workaround:

None.

CSCed86925

Trunks are not connected to the nodes in physical view.

Symptom:

Trunks are not connected to nodes in the graphical view of Network Monitor.

Conditions:

During expanding networks in Network Monitor GUI, nodes and trunks are shown in the graphical view. However, trunks are not connected to nodes. That is to say the two ends of trunk are not attached to the nodes. Thus, it looks like those trunks are floating around the topology map.

Workaround:

Move those nodes in the graphical view, or refresh the graphical view like using scroll bar. Then, those floating trunks will be connected to the nodes.

CSCed88696

Install shield (ISMP) issue: Some files are not copied during installation.

Symptom:

When installing CWM, some files are not copied properly which causes the installation failed.

Conditions:

When installing CWM.

Workaround:

Clean up the partly installed files. Reboot the machine and try installing again.

CSCed91850

Symptom:

xdbroker reinitialized once

Conditions:

Running 12.0.00-P1.1

Workaround:

Process was respawned by watchdog

CSCee12471

Finder server coredump

Symptom:

finder server coredump

Conditions:

Unknown.

Workaround:

Unknown.

CSCee89740

Symptom:

No option for Logical partitioning during Infx raw partition for phys db

Conditions:

Install 15.0.00

Workaround:

Here is an example of adding phydbs.

1. Add the partition

chmod 660 /dev/rdsk/c0t10d0s5

chown informix /dev/rdsk/c0t10d0s5

chgrp informix /dev/rdsk/c0t10d0s5

/usr/users/informix92/bin/onspaces -c -d phydbs -p /dev/rdsk/c0t10d0s5 -o 0 -s 1850000

CSCee90732

provision fails with channel unavailable, dmd cache issue

Symptom:

provision fails with channel unavailable, dmd cache issue

Conditions:

proxy provision with CWM 12.0.00-P1.1

Workaround:

coldstart

CSCef02108

AuditTrailViewer Can not retrieve any Gateway Monitor event and Statistics Rep

Symptom:

Can not retrieve "Statistics Report" and "Gateway Monitor" audit logged events

Conditions:

Any time user wants to view audit logged for "Statistics Report" and "Gateway Monitor" event.

Workaround:

Vi the audit logged file and insert a space between Gateway and Monitor. For the "Statistics Report" audit logged, remove "s" at the end of Statistics.

CSCef10417

Symptom:

suspect msgs in scmsapatchinstall log

Conditions:

Seen on SSC during upgrade to 15.0.00-P2H

Workaround:

N/A.

CSCef10445

Symptom:

wdupdate error in scmsaexecinstall log

Conditions:

Seen on SSM during upgrade to 15.0.00-P2C

Workaround:

N/A.

CSCef15590

Symptom:

chown & chgrp file error mesg during scmsapostpatchinstall

Conditions:

Seen during 15.0.00-P2K SSC install

Workaround:

N/A.

CSCef20358

tree view not showing proper info after config save restored

Conditions:

save configuration,add ports on mpsm-8t1-fr card and restore original config.

Workaround:

use nmContol with option 1 & then enter node id or NMServer Resync in 8hr will fix the issue.

CSCef27549

Initial Gui load on PC Client too slow

Symptom:

Initial GUI load on PC Client too slow

Conditions:

Trying to bring up Config-Center GUI on PC Client, server 15.0.00-P2K

Workaround:

None. Was taking 5-10 min in customer specific network environment

CSCef30811

Symptom:

The ATM connections added via switch CLI will show up in the atm_connection table without complete connection details. I.e. many important values will be still -1s. Also, user_connection table does not show their corresponding entries either.

Provisioning CWM using conn proxy or CM GUI will see the user_connection table populated however the newly added atm connections in atm_connection table will have incomplete connection values until the card is next periodically or manually resynched.

On the non-provisioning CWMs, only atm_connection table will see those connection entries with incomplete values but user_connection table will not have corresponding entries.

Conditions:

When MGX1 switch firmware image level is less than 1.2.20 for PXM and 10.2.20 for AUSM card. For AXIS platform, this problem can always be seen.

Workaround:

Periodical resync can heal the problem by itself. Or if customer desires, a manual node resync can be done to those impacted nodes.

Further Problem Description:

This issue will impact AUSM and PXM atm connection provisioning.

It happens when 50601 trap is not supported by the firmware image. Without 50601 traps, the normal 50920 (add) and 50600 (config change) traps will still be sent by switch. Processing of 50920 trap only helps in adding an incomplete conn entry into atm_connection table, and emc did not send for snmpget request for detailed conn info.

After trap 50920 came the config change trap 50600, emc logic is flawed in not handling it due to earlier logic enhancement done for cutting down excessive CONN msgs to databroker. The problem is observed as having incomplete connection information and missing user_connection entries right after atm connection provisioning for AXIS platform or for PXM card with image level less than 1.2.20 or AUSM card with image level less than 10.2.20.

CSCef31564

Symptom:

ooemc reinitialized once

Conditions:

Running 15.0.00-P2K Bundle 1

Workaround:

Was respawned by watchdog.

CSCef37402

Symptom:

MGX nodes in mode 1, ooemc not running

Conditions:

Running 15.0.00-P2K

Workaround:

Coldstart the CWMs.

CSCef38504

Symptom:

sctd reintialized once, did not respawn

Conditions:

Running 15.0.00-P2K

Workaround:

coldstarted in this instance, since other processes were problematic at same time

CSCef38543

Symptom:

NMServer reinitialized once

Conditions:

Running 15.0.00-P2K

Workaround:

process was respawned


Anomalies Resolved in CWM 15.0.00 Patch 2 Software

This section lists the anomalies resolved in CWM Release 15.0.00 Patch 2 software as of 08/18/04

.

Table 8 Anomalies Resolved in CWM Release 15.0.00 Patch 2 Software 

Bug ID
Description

CSCec08510

connection trap 25117 svConnDescriptor has extra blank space

CSCec30209

prefroute deletion fails if dup prefroute Ids used on diff source nodes

CSCec72209

xdbroker reinitialized a few times

CSCed60653

emsd reports incorrect link1 down msg when link1 is up

CSCed60685

Incorrect IMA link alarm in tree view for IGX IMA links

CSCed60728

IMA feeder trunk from IGX is shown as physical trunk

CSCed60737

Finder - unable to find connections under BXM OC3 line

CSCed81118

Cannot login to slt10, NMserver not registered to orbix

CSCed81593

trap 1006 was not generated after comm failure on BPX

CSCed89661

After warmstart-xpvc connections exist in xpvc table after deletingthem

CSCed92843

Memory leak seen in purified ooemc

CSCed92999

Query return val not properly protected in DBAccess lib

CSCed93385

Incomplete cons at CWM/SEC after adding hybrid cons at CWM/Pri

CSCed94948

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

CSCee00795

card reset trap as Addfeeder trap in ILMITopoc

CSCee02123

sctGUI not coming up

CSCee05044

EMC:RPM Ethernet4E backcard wrong mapping

CSCee06418

NMServer did not declare sync-ok for some nodes

CSCee10383

frEndPointPercUtil modify fails with traffic parameters err, OvrSubOvrRide enabled

CSCef25251

conn mgr vism vpi default value incorrect and not validating

CSCef27545

MPSM-OC3(FR) card does not work for svPhysicalToLogicalMap Table

CSCin71018

PXM1 card on MGX8230 is shown as Unknown in TreeView & InspectorView.

CSCin71138

DnD of DS3 line on Primary standby BNM-T3 card in CC/DC triggers XML error.

CSCin71195

Cannot work on routing/feeder node when added/removed from user group

CSCin71556

Total Xmtd/Rcvd and HEC Error Cell Counters are not seen in DC GUI.

CSCin78292

snmpget on cwmRsrcPartTable fails for pnni partition on MPSM-FR port.

CSCin78333

Secondary standby MPSM card does not show licenses in Tree view.


Anomalies Closed By Other Means in CWM 15.0.00 Patch 2 Software

This section lists the anomalies listed as open in CWM 15.0.00 that were closed by means other than resolved in CWM Release 15.0.00 Patch 2 software as of 08/18/04.

.

Table 9 Anomalies Resolved in CWM Release 15.0.00 Patch 2 Software 

Bug ID
Description

CSCef25039

All CWM processes did not come up after starting core with P2N

This bug was set to U (unreproducible).

CSCef05039

sdbroker coredump

This bug was set to U (unreproducible).

CSCed82182

LSNT: cwmftpd core dumped when core is running

This bug was set to U (unreproducible).

CSCin71251

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

This bug was set to D (Duplicate of CSCed18358, which is in M state).

CSCed93069

LSNT: emc core dumped due to mutex control in liblogger library

This bug was set to U (unreproducible).


Related Documentation

The following technical documents comprise the CWM 15 documentation set:

Cisco WAN Manager Installation, OL-4550-01

Cisco WAN Manager User's Guide, OL-4552-01

Cisco WAN Manager SNMP Service Agent, OL-4551-01

Cisco WAN Manager Database Interface, OL-4587-01

Cisco WANDEST Installation and Reference, Release 2.5, OL-5223-01

Release Notes for Cisco WAN Manager, Release 15.0.00, OL-4151-01

Release Notes for Cisco WAN Manager, Release 15.0.00, Patch 2, OL-5354-01

PDF copies of the first five items in the CWM 15 documentation set are provided on the CWM 15 Documentation CD along with a copy of Adobe Acrobat Reader and Netscape Communicator 4.76 for use in reading the files.

Use the included gzip utility to decompress the .gz files. The command is gzip -d.

These release notes are not available on the CWM 15 Documentation CD. They are available on-line at the following URL:

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

Obtaining Documentation

You can access the most current Cisco documentation on the World Wide Web at this URL:

http://www.cisco.com

Translated documentation is available at this URL:

http://www.cisco.com/public/countries_languages.shtml

Documentation Feedback

You can submit comments electronically on Cisco.com. In the Cisco Documentation home page, click the Fax or Email option in the "Leave Feedback" section at the bottom of the page.

You can e-mail your comments to bug-doc@cisco.com.

You can submit your comments by mail by using the response card behind the front cover of your document or by writing to the following address:

Cisco Systems
Attn: Document Resource Connection
170 West Tasman Drive
San Jose, CA 95134-9883

We appreciate your comments.

Obtaining Technical Assistance

Cisco provides Cisco.com as a starting point for all technical assistance. Customers and partners can obtain online documentation, troubleshooting tips, and sample configurations from online tools by using the Cisco Technical Assistance Center (TAC) Web Site. Cisco.com registered users have complete access to the technical support resources on the Cisco TAC Web Site.

Cisco.com

Cisco.com is the foundation of a suite of interactive, networked services that provides immediate, open access to Cisco information, networking solutions, services, programs, and resources at any time, from anywhere in the world.

Cisco.com is a highly integrated Internet application and a powerful, easy-to-use tool that provides a broad range of features and services to help you with these tasks:

Streamline business processes and improve productivity

Resolve technical issues with online support

Download and test software packages

Order Cisco learning materials and merchandise

Register for online skill assessment, training, and certification programs

If you want to obtain customized information and service, you can self-register on Cisco.com. To access Cisco.com, go to this URL:

http://www.cisco.com

Technical Assistance Center

The Cisco Technical Assistance Center (TAC) is available to all customers who need technical assistance with a Cisco product, technology, or solution. Two levels of support are available: the Cisco TAC Web Site and the Cisco TAC Escalation Center.

Cisco TAC inquiries are categorized according to the urgency of the issue:

Priority level 4 (P4)—You need information or assistance concerning Cisco product capabilities, product installation, or basic product configuration.

Priority level 3 (P3)—Your network performance is degraded. Network functionality is noticeably impaired, but most business operations continue.

Priority level 2 (P2)—Your production network is severely degraded, affecting significant aspects of business operations. No workaround is available.

Priority level 1 (P1)—Your production network is down, and a critical impact to business operations will occur if service is not restored quickly. No workaround is available.

The Cisco TAC resource that you choose is based on the priority of the problem and the conditions of service contracts, when applicable.

Cisco TAC Web Site

You can use the Cisco TAC Web Site to resolve P3 and P4 issues yourself, saving both cost and time. The site provides around-the-clock access to online tools, knowledge bases, and software. To access the Cisco TAC Web Site, go to this URL:

http://www.cisco.com/tac

All customers, partners, and resellers who have a valid Cisco service contract have complete access to the technical support resources on the Cisco TAC Web Site. The Cisco TAC Web Site requires a Cisco.com login ID and password. If you have a valid service contract but do not have a login ID or password, go to this URL to register:

http://www.cisco.com/register/

If you are a Cisco.com registered user, and you cannot resolve your technical issues by using the Cisco TAC Web Site, you can open a case online by using the TAC Case Open tool at this URL:

http://www.cisco.com/tac/caseopen

If you have Internet access, we recommend that you open P3 and P4 cases through the Cisco TAC Web Site.

Cisco TAC Escalation Center

The Cisco TAC Escalation Center addresses priority level 1 or priority level 2 issues. These classifications are assigned when severe network degradation significantly impacts business operations. When you contact the TAC Escalation Center with a P1 or P2 problem, a Cisco TAC engineer automatically opens a case.

To obtain a directory of toll-free Cisco TAC telephone numbers for your country, go to this URL:

http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml

Before calling, please check with your network operations center to determine the level of Cisco support services to which your company is entitled: for example, SMARTnet, SMARTnet Onsite, or Network Supported Accounts (NSA). When you call the center, please have available your service agreement number and your product serial number.