Table of Contents

System Requirements

In addition to the CWM platform requirements listed in the Cisco WAN Manager Installation Guide, Release 15, also consider the following:

•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 certified configuration may take more time to troubleshoot, 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 requires 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.7 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 2 GB partition chunks are required to be added to Informix. Refer to the Cisco WAN Manager Installation, Release 15, 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

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.

•Average Network Transfer 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 on the CWM Server, add the Parser System Requirement to the requirements listed in Table 1.

•The Standalone Statistics Collector (SSC) has the same system requirements as the Standalone Statistics Manager. If you have enabled the Parser, add the Parser System Requirement to the system requirements listed in Table 3.

•A maximum of twelve Standalone Statistics Collectors can be controlled by one Standalone Statistics Manager.

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

Add the applicable system requirements in Table 4 to the CWM Server requirements in Table 1 if the Parser Function is enabled.

Collecting statistics for four million endpoints with 5 statistics per endpoint requires 80 GB of disk space per 24 hour period. You will 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 later (108528-27 or higher)

(previously was 108528-13)

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

Required Patches

Enter the Solaris showrev -p command to display the patches which are already installed in the CWM workstation.

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 6-digit patch ID number (do not include the 2-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

•109147-37 (needed to resolve CSCej57997)

•108993-49 (needed to resolve CSCej57997)

•108652-35

•108528-27

•108434-18 (needed to resolve CSCej57997)

Recommended Patches

•110951-01

•110662-02

•110615-01

•110286-02

•109324-02

•111085-02

To obtain these patches, go to the 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.

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, 6.3, or 7.0 for Solaris 8.

Note You must purchase HP OpenView 6.3 or 7.0 directly from Hewlett Packard.

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

Informix Requirements

The CWM 15.0.00 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.0.00 release.

SWSW 9.2.33 through 9.2.43, 9.3.05 through 9.3.51, or 9.4.00 through 9.4.12

IGX 8400

UXM-E

UAI-4 SMFXLR, UAI-4-STM1E

SWSW 9.2.33 through 9.2.43, 9.3.05 through 9.3.51, or 9.4.00 through 9.4.12

MGX 8220

ASC

ASC-LM

4.1.07 through 4.1.12, or 5.0.12 through 5.0.20

MGX 8220

AUSM-8P

RJ-48-8E1/8T1

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

BNM-T3/E3

T3E3-B/D

4.1.07 through 4.1.12, or 5.0.12 through 5.0.20

MGX 8220

CESM-8P

RJ-48-8T1/8E1, SMB-8E1

4.1.07 through 4.1.12, or 5.0.12 through 5.0.20

MGX 8220

FRSM-8P

RJ-48-8T1/8E1, SMB-8E1

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

FRSM-VHS

HS2

4.1.07 through 4.1.12, or 5.0.12 through 5.0.20

MGX 8220

IMATM-B

RJ-48-T3T1/E3E1

SMB-E3E1

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, MGX 8230, MGX 8250, MGX 8850 PXM1

AUSM

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, 1.2.20 through 1.2.23, or 1.3.00 through 1.3.12

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, 1.2.20 through 1.2.23, or 1.3.00 through 1.3.12

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.23, or 1.3.00 through 1.3.12

MGX 8230, MGX 8250, MGX 8850 (PXM1)

RPM/B

RJ45-4E/B (Ethernet) MGX-MMF-FE, MGX-RJ45-FE (Fast Ethernet)

1.2.00 through 1.2.13, 1.2.20 through 1.2.23, or 1.3.00 through 1.3.12

MGX 8230, MGX 8250, MGX 8850 (PXM1)

RPM-PR

RJ45-4E/B (Ethernet) MGX-MMF-FE, MGX-RJ45-FE (Fast Ethernet)

1.2.00 through 1.2.13, 1.2.20 through 1.2.23, or 1.3.00 through 1.3.12

MGX 8230, MGX 8250, MGX 8850 (PXM1)

SRM/E

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

1.2.00 through 1.2.13, 1.2.20 through 1.2.23, or 1.3.00 through 1.3.12

MGX 8230, MGX 8250, MGX 8850 (PXM1)

VISM-PR

RJ-48-T1/E1 and SMB-E1

1.2.00 through 1.2.13, 1.2.20 through 1.2.23, or 1.3.00 through 1.3.12

MGX 8230, MGX 8250, MGX 8850 PXM1

AUSM-8P

8T1/E1

1.1.31 through 1.1.34, 1.1.40 through 1.1.42, 1.2.00 through 1.2.13, 1.2.20 through 1.2.23, or 1.3.00 through 1.3.12

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.23, or 1.3.00 through 1.3.12

MGX 8230, MGX 8250, MGX 8850 PXM1

CESM-8P

RJ-48-8T1/8E1, SMB-8E1,

RJ-48-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.23, or 1.3.00 through 1.3.12

MGX 8230, MGX 8250, MGX 8850 PXM1

FRSM-8P

RJ-48-8T1/8E1, SMB-8E1

1.1.40 through 1.1.42, 1.2.00 through 1.2.13, 1.2.20 through 1.2.23, or 1.3.00 through 1.3.12

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.23, or 1.3.00 through 1.3.12

MGX 8230, MGX 8250, MGX 8850 PXM1

MPSM-8-T1E1

AX-RJ-48-8T1

AX-R-RJ-48-8T1

AX-RJ-48-8E1

AX-R-RJ-48-8E1

AX-SMB-8E1

AX-R-SMB-8E1

1.3.00 through 1.3.12

MGX 8230, MGX 8250, MGX 8850 PXM1

PXM1

T3/E3/OC-3/OC-12

1.1.40 through 1.1.42, 1.2.00 through 1.2.13, 1.2.20 through 1.2.23, or 1.3.00 through 1.3.12

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.23, or 1.3.00 through 1.3.12

MGX 8230, MGX 8250, MGX 8850 PXM1

VISM-8E1

AX-SMB-8E1

AX-RJ-48-8E1

AX-R-SMB-8E1

AX-R-RJ-48-8E1

1.1.40 through 1.1.42, 1.2.00 through 1.2.13, 1.2.20 through 1.2.23, or 1.3.00 through 1.3.12

MGX 8230, MGX 8250, MGX 8850 PXM1

VISM-8T1

AX-RJ-48-8T1

AX-R-RJ-48-8T1

1.1.40 through 1.1.42, 1.2.00 through 1.2.13, 1.2.20 through 1.2.23, or 1.3.00 through 1.3.12

MGX 8230, MGX 8250, MGX 8850 PXM1

VISM-PR

RJ-48-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.23, or 1.3.00 through 1.3.12

MGX 8830/8850 (PXM1E)

AUSM Model B

8T1/E1

3.0.23 through 3.0.25, 4.0.00 through 4.0.17, or 5.0.00 through 5.0.20

MGX 8830/8850 (PXM1E)

CESM-8P

RJ-48-8T1/8E1, SMB-8E1, RJ-48-8T1-C/8E1-C, SMB-8E1-C

3.0.23 through 3.0.25, 4.0.00 through 4.0.17, or 5.0.00 through 5.0.20

MGX 8830/8850 (PXM1E)

FRSM-8P

RJ-48-8T1/8E1, SMB-8E1

3.0.23 through 3.0.25, 4.0.00 through 4.0.17, or 5.0.00 through 5.0.20

MGX 8830/8850 (PXM1E)

FRSM-HS2B

8-port 12in1, HSSI

3.0.23 through 3.0.25, 4.0.00 through 4.0.17, or 5.0.00 through 5.0.20

MGX 8830/8850 (PXM1E)

FRSM-VHS

2CT3

4.0.00 through 4.0.17, or 5.0.00 through 5.0.20

MGX 8830/8850 (PXM1E)

MPSM-8-T1E1

AX-RJ-48-8T1

AX-R-RJ-48-8T1

AX-RJ-48-8E1

AX-R-RJ-48-8E1

AX-SMB-8E1

AX-R-SMB-8E1

5.0.20

MGX 8830/8850 (PXM1E)

PXM1E

8-port T3/E3

MGX-T3E3-155

MCC-16-E1

RBBN-16-T1E1

3.0.23 through 3.0.25, 4.0.00 through 4.0.17, or 5.0.00 through 5.0.20

MGX 8830/8850 (PXM1E)

PXM1E

8-port 155

3.0.23 through 3.0.25, 4.0.00 through 4.0.17, or 5.0.00 through 5.0.20

MGX 8830/8850 (PXM1E)

PXM1E

8-port OC-3 STM1

4.0.00 through 4.0.17, or 5.0.00 through 5.0.20

MGX 8830/8850 (PXM1E)

RPM-PR

RJ45-4E/B (Ethernet) MGX-MMF-FE,MGX-RJ45-FE (Fast Ethernet)

3.0.23 through 3.0.25, 4.0.00 through 4.0.17, or 5.0.00 through 5.0.20

MGX 8830/8850 (PXM1E)

SRM/E

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

3.0.23 through 3.0.25, 4.0.00 through 4.0.17, or 5.0.00 through 5.0.20

MGX 8830/8850 (PXM1E)

VISM-PR

RJ-48-T1/E1 and SMB-E1

3.0.23 through 3.0.25, 4.0.00 through 4.0.17, or 5.0.00 through 5.0.20

MGX 8850 (PXM45)

AXSM/A

AXSM/B

OC-12

2.1.76 through 2.1.81, 3.0.20 and 3.0.23 through 3.0.25, 4.0.00 through 4.0.17, or 5.0.00 through 5.0.20

MGX 8850 (PXM45)

AXSM/A

AXSM/B

OC-3

2.1.76 through 2.1.81, 3.0.20 and 3.0.23 through 3.0.25, 4.0.00 through 4.0.17, or 5.0.00 through 5.0.20

MGX 8850 (PXM45)

AXSM/A

AXSM/B

OC-48

2.1.76 through 2.1.81, 3.0.20 and 3.0.23 through 3.0.25, 4.0.00 through 4.0.17, or 5.0.00 through 5.0.20

MGX 8850 (PXM45)

AXSM/A

AXSM/B

T3/E3

2.1.76 through 2.1.81, 3.0.20 and 3.0.23 through 3.0.25, 4.0.00 through 4.0.17, or 5.0.00 through 5.0.20

MGX 8850 (PXM45)

AXSM-32-T1E1-E

MCC-16-E1, RBBN-16-T1E1

4.0.00 through 4.0.17, or 5.0.00 through 5.0.20

MGX 8850 (PXM45)

AXSM-E

OC-12

2.1.76 through 2.1.81, 3.0.20 and 3.0.23 through 3.0.25, 4.0.00 through 4.0.17, or 5.0.00 through 5.0.20

MGX 8850 (PXM45)

AXSM-E

OC-3

2.1.76 through 2.1.81, 3.0.20 and 3.0.23 through 3.0.25, 4.0.00 through 4.0.17, or 5.0.00 through 5.0.20

MGX 8850 (PXM45)

AXSM-E

T3/E3

2.1.76 through 2.1.81, 3.0.20 and 3.0.23 through 3.0.25, 4.0.00 through 4.0.17, or 5.0.00 through 5.0.20

MGX 8850 (PXM45)

AXSM-XG

OC-3

5.0.00 through 5.0.20

MGX 8850 (PXM45)

CESM-8P

RJ-48-8T1/8E1, SMB-8T1B

4.0.00 through 4.0.17, or 5.0.00 through 5.0.20

MGX 8850 (PXM45)

FRSM-8P

RJ-48-8T1/8E1, SMB-8E1

4.0.00 through 4.0.17, or 5.0.00 through 5.0.20

MGX 8850 (PXM45)

FRSM-HS2/B

8-port 12in1, HSSI

4.0.10 through 4.0.17, or 5.0.00 through 5.0.20

MGX 8850 (PXM45)

FRSM-VHS

2CT3

4.0.00 through 4.0.17, or 5.0.00 through 5.0.20

MGX 8850 (PXM45)

FRSM-VHS

2T3E3

4.0.10 through 4.0.17, or 5.0.00 through 5.0.20

MGX 8850 (PXM45)

MPSM-8-T1E1

AX-RJ-48-8T1

AX-R-RJ-48-8T1

AX-RJ-48-8E1

AX-R-RJ-48-8E1

AX-SMB-8E1

AX-R-SMB-8E1

5.0.20

MGX 8850 (PXM45)

PXM45

PXM-HD, PXM-UI S3

2.1.76 through 2.1.81, 3.0.20 and 3.0.23 through 3.0.25, 4.0.00 through 4.0.17, or 5.0.00 through 5.0.20

MGX 8850 (PXM45)

PXM45/C

PXM-HD, PXM-UI S3/B

4.0.00 through 4.0.17, or 5.0.00 through 5.0.20

MGX 8850 (PXM45)

PXM45B

PXM-HD, PXM-UI S3

2.1.76 through 2.1.81, 3.0.20 and 3.0.23 through 3.0.25, 4.0.00 through 4.0.17, or 5.0.00 through 5.0.20

MGX 8850 (PXM45)

RPM-PR

MGX-2GE and MGX-2OC-12POS

5.0.00 through 5.0.20

MGX 8850 (PXM45)

RPM-PR

RJ45-4E/B (Ethernet) MGX-MMF-FE,MGX-RJ45-FE (Fast Ethernet)

3.0.23 through 3.0.25, 4.0.00 through 4.0.17, or 5.0.00 through 5.0.20

MGX 8850 (PXM45)

RPM-XF

MGX-1GE and MGX-1OC12POS

3.0.23 through 3.0.25, 4.0.00 through 4.0.17, or 5.0.00 through 5.0.20

MGX 8850 (PXM45)

RPM-XF

MGX-UI/B

5.0.20

MGX 8850 (PXM45)

SRM/E

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

4.0.00 through 4.0.17, or 5.0.00 through 5.0.20

MGX 8850 (PXM45)

SRME/B

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

T3

5.0.00 through 5.0.20

MGX 8850 (PXM45)

VISM-PR

RJ-48-T1/E1 and SMB-E1

3.0.23 through 3.0.25, 4.0.00 through 4.0.17, or 5.0.00 through 5.0.20

MGX 8850 (PXM45)

VISM-PR

RJ-48-T1/E1 and SMB-E1

5.0.00 through 5.0.20

MGX 8850 (PXM45)

VXSM

RJ-48-T1/E1 and SMB-E1

5.0.00 through 5.0.20

MGX 8850/8250/8230 (PXM1)

MPSM-8-T1E1

AX-RJ-48-8T1

AX-R-RJ-48-8T1

AX-RJ-48-8E1

AX-R-RJ-48-8E1

AX-SMB-8E1

AX-R-SMB-8E1

1.3.00 through 1.3.12

MGX 8850/8250/8230 (PXM1)

RPM-PR

MGX-2GE and MGX-2OC-12POS

1.3.00 through 1.3.12

MGX 8850/8250/8230 (PXM1)

SRME/B

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

T3

1.3.00 through 1.3.12

MGX 8850/8250/8230 (PXM1)

VISM-PR

RJ-48-T1/E1 and SMB-E1

1.3.00 through 1.3.12

MGX 8850/8830 (PXM1E)

MPSM-8-T1E1

AX-RJ-48-8T1

AX-R-RJ-48-8T1

AX-RJ-48-8E1

AX-R-RJ-48-8E1

AX-SMB-8E1

AX-R-SMB-8E1

5.0.20

MGX 8850/8830 (PXM1E)

RPM-PR

MGX-2GE and MGX-2OC-12POS

5.0.00 through 5.0.20

MGX 8850/8830 (PXM1E)

VISM-PR

RJ-48-T1/E1 and SMB-E1

5.0.00 through 5.0.20

MGX 8880 (PXM45)

AXSM/B

OC-48

5.0.00 through 5.0.20

MGX 8880 (PXM45)

AXSM-E

OC-12

5.0.00 through 5.0.20

MGX 8880 (PXM45)

AXSM-XG

OC-3 16P

5.0.00 through 5.0.20

MGX 8880 (PXM45)

PXM45B

PXM-HD, PXM-UI S3

5.0.00 through 5.0.20

MGX 8880 (PXM45)

RPM-PR

MGX-2GE and MGX-2OC-12POS

5.0.00 through 5.0.20

MGX 8880 (PXM45)

RPM-XF

MGX-2GE and MGX-2OC-12POS

5.0.00 through 5.0.20

MGX 8880 (PXM45)

SRME/B

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

T3

5.0.00 through 5.0.20

MGX 8880 (PXM45)

VISM-PR

RJ-48-T1/E1 and SMB-E1

5.0.00 through 5.0.20

MGX 8880 (PXM45)

VXSM

RJ-48-T1/E1 and SMB-E1

5.0.00 through 5.0.20

MGX 8950 (PXM45)

AXSM/B

OC-12

2.1.76 through 2.1.81, 3.0.23 through 3.0.25, 4.0.00 through 4.0.17, or 5.0.00 through 5.0.20

MGX 8950 (PXM45)

AXSM/B

OC-3

2.1.76 through 2.1.81, 3.0.23 through 3.0.25, 4.0.00 through 4.0.17, or 5.0.00 through 5.0.20

MGX 8950 (PXM45)

AXSM/B

OC-48

2.1.76 through 2.1.81, 3.0.23 through 3.0.25, 4.0.00 through 4.0.17, or 5.0.00 through 5.0.20

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.17, or 5.0.00 through 5.0.20

MGX 8950 (PXM45)

AXSM-XG

OC-192

4.0.00 through 4.0.17, or 5.0.00 through 5.0.20

MGX 8950 (PXM45)

AXSM-XG

OC-3 16P

5.0.00 through 5.0.20

MGX 8950 (PXM45)

AXSM-XG

OC-48

4.0.00 through 4.0.17, or 5.0.00 through 5.0.20

MGX 8950 (PXM45)

PXM45

PXM-HD, PXM-UI-S3

2.1.76 through 2.1.81, 3.0.23 through 3.0.25, 4.0.00 through 4.0.17, or 5.0.00 through 5.0.20

MGX 8950 (PXM45)

PXM45/C

PXM-HD, PXM-UI S3/B

4.0.00 through 4.0.17, or 5.0.00 through 5.0.20

MGX 8950 (PXM45)

PXM45B

PXM-HD, PXM-UI-S3

2.1.76 through 2.1.81, 3.0.23 through 3.0.25, 4.0.00 through 4.0.17, or 5.0.00 through 5.0.20

MGX 8950 (PXM45)

RPM-PR

RJ45-4E/B (Ethernet) MGX-MMF-FE, MGX-RJ45-FE (Fast Ethernet)

3.0.23 through 3.0.25, 4.0.00 through 4.0.17, or 5.0.00 through 5.0.20

MGX 8950 (PXM45)

RPM-XF

MGX-1GE and MGX-1OC12POS

3.0.23 through 3.0.25, 4.0.00 through 4.0.17, or 5.0.00 through 5.0.20

SES PNNI Controller

SES-PXM

PXM-UIA

3.0.10 through 3.0.25, or 4.0.00 through 4.0.15

SES PNNI Controller

SES-PXM

T3/E3/OC-3/OC-12

3.0.10 through 3.0.25, or 4.0.00 through 4.0.15

Certified Releases

The following releases were tested with CWM Release 15.0.00. Patch 5:

•BPX/IGX Switch Software:

–Switch Software 9.4.12

–Switch Software 9.3.51

–Switch Software 9.2.47

•MGX 8230/8250/8850 (PXM1) Switch

–MGX 1.3.12

–MGX 1.3.11

–MGX 1.2.23

–MGX 1.2.13 and 1.1.34

•MGX 8950 (PXM45) Switch

–MGX 5.0.20

–MGX 4.0.17

•MGX 8850 (PXM45) Switch

–MGX 5.0.20

–MGX 4.0.17

–MGX 3.0.25

–MGX 3.0.20

•MGX 8880 (PXM45) Switch

–MGX 5.0.70

•MGX 8850/8830 (PXM1E) Switch

–MGX 5.0.20

–MGX 4.0.17

–MGX 3.0.25

•BPX SES Shelf

–SES 4.0.15.20

•MGX 8220 Shelf

–MGX 8220 5.0.20

–MGX 8220 4.1.12

•VISM-PR

–VISM-PR 3.3.10

–VISM-PR 3.2.11

–VISM-PR 1.5.10 (certified with MGX 1.1.34 only)

•VXSM

–VXSM 5.0.20

–VXSM 5.0.70 (certified with MGX 5.0.20 onlly)

–VXSM 5.0.00

•RPM-XF

–Cisco IOS 12.3(7)T3

–Cisco IOS 12.3(2)T5

•RPM-PR

–Cisco IOS 12.3(7)T3

–Cisco IOS 12.2(8)T4

New Features and Enhancements in CWM Release 15

Features Introduced in CWM Release 15.0.00, Patch 5

•Additional queue related details will be logged in snmpd.log. For example, warning messages will appear when 75% or 90% of thread usage is surpassed. Also if usage drops from 75% or 90% to below 75% or 90%, respectively, then a message will be logged.

•Ability to suppress traps using ntsControl.

Sometimes certain network problems may send out a blast of traps from a set of nodes which may flood CWM causing other nodes not to function properly. It may be useful to suppress these traps from the troubled node and allow proper management of the rest of the network. You can then enable the traps at a later point once the situation is corrected on the troubled nodes.

ntsControl is a client program for NTS which gives certain control APIs for NTS. This would be used to suppress some traps from NTS from flowing to other CWM modules (the traps will still be sent out to HPOV and RTMProxy). To use ntsControl:

Features Introduced in CWM Release 15.0.00, Patch 4

Node Rename feature allows users with appropriate authority level to change the node name. If the user has the permission to change the node name and the newly selected node name is already in use, then an error message is displayed and the operation is not allowed. The Node Rename permission is independent of the 'modify' permissions and it applies only to the Configuration Center.

Installation, Security Manager and ConfigurationCenter have been modified as follows:

Installation changes:

–Node name provisioning option is given to the adminprofile only.

–New input panel to enable Node Name Provisioning. Profiles are updated with appropriate values that the user designates.

–Node Name Authority default parameters for adminProf profile is `selected and userProf1 profile is `unselected'.

Security Manager application enhancements:

–Security Manager profiles are extended with an additional Node Name Authority parameter for Configuration Center.

–All profiles (both existing and new) will have the Node Name Authority parameter.

–Node Name Authority parameter is independent of all other profile attributes including the modify attribute.

–Node Name Authority default parameters for adminProf profile is `selected and userProf1 profile is `unselected'.

When Node Name Authority is 'selected', the profile allows any user bound to it to use Configuration Center to edit the node name.

When Node Name Authority is 'unselected, the profile does not allow any user bound to it to use Configuration Center to edit the node name. The node name in Configuration Center will be disabled (grayed out) and will be a read only attribute.

For any newly created profiles, the Node Name Authority parameter default setting will be set to 'unselected'. However, the Admin user will be able to change the settings.

–Any user bound to the new profile will be able to edit the node name based on the current 'Node Name Authority' parameter setting in the new profile.

Configuration Center enhancements:

–Node Name Authority parameter is independent of the 'modify' permission and it applies only to Configuration Center.

–Configuration Center will use the Node Name Authority parameter setting to enable or disable the editing capabilities of the Node Name UI field in Configuration Center. If the user has permission to edit the node name then the node name UI field is enabled. Otherwise, it is disabled (grayed-out).

–If the user has the permission to change the node name and the newly selected node name is already in use, then an error message is displayed and the operation is not allowed.

•Support for 53-byte conversion factor.

Configuration Center allows users to enable the cps to Kpbs conversion (default is cps). For the ATM connections, the conversion factor has been extended to support both the 48 byte as well as 53 byte cells.

Configuration center will use either the 48 byte or the 53 byte conversion based upon the selected conversion-factor in the CMSCClient.conf file.

–If the USE_53_BYTE_CONVERSION_FACTOR is set to 'false', a conversion factor of 384 (48 bytes; 48 * 8) is used (1 cps = 384 bps).

–If the USE_53_BYTE_CONVERSION_FACTOR is set to 'true', a conversion factor of 424 (53 bytes; 53 * 8) is used (1 cps = 424 bps).

Note For existing connections created using a 48 byte conversion factor; if the user changes the conversion factor to 53 byte conversion, a different kbps value other than the original value (which used the 48 factor) will be shown to the user since the connection was originally provisioned with a 48 byte conversion factor.

Note The 53 byte conversion applies only to the new connections and the modifications of existing connections.

Features Introduced in CWM Release 15.0.00, Patch 3

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

–CWM 15.0.00 Patch 3 adds support for collecting bulk statistics from the VISM-PR running Release 3.3 of the VISM software. None of the other new 3.3 features are supported

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

–MGX 8850, 8250, and 8230 (PXM1-based nodes) running Release 1.3.10 will recognize both the VISM and VISM-PR running Release 3.3 of the VISM software, but the new 3.3 features are not supported on PXM1-based nodes.

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 OC-3 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 OC-3 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 or not the connection is directed. If this flag is set to 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 the direct_route_flag parameter is set to 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 or not the connection is directed. If this flag is set to 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 the direct_route_flag parameter is set to 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 or not the connection is directed. If this flag is set to 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 the direct_route_flag parameter is set to 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 multipurpose 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.

–AXSM-XG 16-port OC-3 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 OC-3 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.

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

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

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

When the CONDITIONAL_PRIMARY flag is set to Yes, the secondary CWM Server becomes a conditional primary when it discovers 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 server will automatically revert back to being the secondary server when the connectivity between the two CWM gateway servers is restored.

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-OC-3 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 MGX 8880 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 OC-3/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 using 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 managed 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. You can now use the Diagnostics Center application to query real-time statistics counters for CID level statistics from the CWM 15 GUI.

•MGX 8850, Release 5

–Support for AXSM-16-155-XG

CWM Release 15.0.00 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 Release 15.0.00 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 former path of a connection. This increases connection availability.

CWM based provisioning using the SNMP MIB is also supported.

–Enhancements to Route Optimization

CWM Release 15.0.00 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". The "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.

–Support for VXSM-OC-3 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 MGX 8850 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 OC-3/STM1 and VXSM with 48 ports of T1/E1 are supported by this CWM release. These modules can be used on the Cisco MGX 8850 PXM45-based voice gateway with AXSM-B and VISM-PR.

CWM 15 supports configuration of the lines, ports and channels on these VXSM cards using 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 managed 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. You can now use the Diagnostics Center application to query real-time statistics counters for CID level statistics from the CWM 15 GUI.

•MGX 8950, Release 5

–Support for AXSM-16-155-XG

CWM Release 15.0.00 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 for customers who require these enhanced traffic management capabilities.

–Support for soft rerouting

CWM Release 15.0.00 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 former path of a connection. This increases connection availability.

CWM based provisioning using the SNMP MIB is also supported.

–Enhancements to Route Optimization

CWM Release 15.0.00 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". The "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 Release 15.0.00 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 Release 15.0.00 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 former path of a connection. This increases connection availability.

CWM based provisioning using the SNMP MIB is also supported.

–Enhancements to Route Optimization

CWM Release 15.0.00 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". The "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 Release 15.0.00 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 Release 15.0.00 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 Release 15.0.00 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 Release 15.0.00 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 Release 15.0.00 supports the Preferred Route Indicator feature for PXM45-based MGX 8850 and MGX 8950 nodes and 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 Guide, Release 15 at the following URL:

CWM Release 15.0.00 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.

CWM Release 15.0.00 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 Guide, Release 15 at the following URL:

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

CWM-specific Enhancements

•New Graphical User Interface

CWM Release 15.0.00 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:

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

•AXSM-E level 3 statistics

•AIS delay grooming

WANDEST 2.5-Specific Enhancements

•Selectable Triggers for Database Tables

In the WANDEST releases before 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.

Unsupported Features and Known Feature Limitations in CWM Release 15.0.00

The following features are not supported in CWM Release 15.0.00 Patch 3:

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.

Several windows display fields relating to the MPSM-T3E3-155 MultiLink Frame Relay (MLFR) feature, which is not currently supported.

When managing VISM service modules that are running Release 3.2.11, CWM only supports the Release 3.2 features.

When managing VISM service modules that are running Release 3.3, CWM only supports the Release 3.2.11 features and bulk statistics on PXM45-based and PXM1E-based nodes only.

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

•TGCP

•Dynamic Payload

•T.38 Fax Relay

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

The following cards are not supported by CWM Release 15.0.00:

•The BME card is not supported.

•The FRSM12 service module is not supported.

Limitations

1. Cisco does not recommend pointing multiple CWM workstations at the same gateway node.

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

3. When /usr/users becomes100 percent full, the orbix processes are not able to write to the disk and thus, 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 the core.

Step 2 Exit out of the CWM prompt.

Step 3 Run the stoporbix2000 script.

Step 4 Type CWM.

You should see "Starting Orbix..." in the ~svplus/log/.startStopOrbix.log file.

Step 5 Start the core.

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

The error message is printed when the server tries to contact the client, but is not able to. The call is initiated by the GUI client in order to activate the lease plug-in that the client uses to detect a server crash.

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

The DNS is configured so that the client can communicate with the server, but when the server tries to contact the 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 set up properly.

5. When the SSM (Standalone Statistics Manager) is installed with the SCM Gateway configuration, the SCM GUI does not open when the primary SSM and secondary SSM are started simultaneously (or within a time gap of 30 seconds to 1 minute).

Avoid this problem by waiting 2 to 3 minutes after starting core in the primary SSM before starting core in the secondary SSM in the SCM Gateway configuration.

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

When this error occurs, the statsparser is not able to perform any database related operations.

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 configure CWM for out-of-band management.

9. Allow a 2 to 3 minute 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 the Start Collection process on the 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 CWM-to-CWM gateway must be enabled to ensure uninterrupted statistics collection.

12. When the persistent topology feature is 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, you must delete the entry 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 XPVCs can only connect to the AUSM service module. No such restriction exists for PXM1E-based or PXM45-based nodes.

15. Manual node resync may appear to have failed due to the GUI timing out for PXM45/PXM1E-based Cisco MGX nodes with many connections (for example, 400K dax endpoints).

16. 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. If there is no provisioning on the card, manually clear the major alarm after determining this is not a real alarm condition.

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 back card is found. To ensure that ChassisView recognizes the back card again, you must execute a first level manual node resync.

19. RPM-PR and RPM-XF ports/subinterfaces must 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 (if you accept the default of FFFFFFFFFFFFFFFF), you receive 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 receive 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 causes a delay in receiving status information.

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

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

You can also update the attribute values in the internal frame 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 Release 15.0.00 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. Because 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 Inspector View 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 MPSM-OC3 cards may not get propagated from the switch to CWM. For the AXSM cards, a line/path alarm will be present, but the MPSM-OC-3 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 OC-3 back card with a DS3 or vice versa you need to do a coldstart.

44. In the Connection Manager, the Service Type field displays some non-applicable service types for SPVCs. CWM will display an error if you select a non-applicable service type.

45. After adding a connection loopback through the Diagnostic Center GUI, there is no indication that the connection is in loopback. You have to use the CLI to verify that the connection is in loopback.

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. This is because the ASC cannot route traffic. If you wish to pass traffic between two cards in an MGX 8220 chassis, regardless of how connectivity is added, the actual physical connectivity that has to be built is a connection from each endpoint to the ASC and then a looping segment on a BPX.

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 HP OpenView 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 Release 15.0.00. Use the Network Monitor map instead.

Issues with the CWM Release 15.0.00 Statistics Collection Manager

To collect connection statistics, statistics need to be enabled on the individual connections by setting the stats enable flag to true on each connection. If the user only enables connections statistics on SCM but does not set the stats enabled flag to true on the connection, the statistics will not be collected for that connection. Because there is no mechanism or warning to the user to have this enabled on the connections, CWM will not display an appropriate error message.

When enabling statistics by selecting multiple nodes at a time in the SCM, enabling statistics on all the nodes only succeeds when either all of the nodes have the same card types or all of the nodes only contain 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:

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 either Option 7 or Option 8 (depending on chassis type) 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 Release 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.

SHOW_TOPO_VIEW True means when NWTopology opens, users can see nodes and trunks in the topology.

SHOW_TOPO_VIEW False means when NWTopology opens, users cannot see nodes and trunks in the topology.

In releases earlier than CWM Release 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 Release 15.0.00 Patch 3 adds the following new flags in the CMSCClient.conf file:

•SHOW_ROUTING_TRUNK_TREEVIEW True means that the TreeView will display the routing trunk folder under the network node in all CWM GUI applications. The routing trunk folder contains all the routing trunk information. The default is true. If you set the SHOW_ROUTING_TRUNK_TREEVIEW parameter to false, then the routing trunk information is not retrieved from the inventory server and the TreeView in all CWM GUI applications will not show the routing trunk folder under the network node.

•SHOW_SORTED_TREEVIEW True means that the TreeView in all applications will show sorted tree node names. The default is true. If you set the SHOW_SORTED_TREEVIEW parameter to false, then the tree node names will not be sorted in the TreeView for all applications.

•ACCESS_TROUBLE_TICKET_SEND_EMAIL True enables the Send button of the Trouble Ticket dialog in the Diagnostics Center application. The default is true. If you set the ACCESS_TROUBLE_TICKET_SEND_EMAIL parameter to false, the Send Button in the Trouble Ticket dialog in the Diagnostics Center application is disabled.

CWM Release 15.0.00 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 appears on the workstation screen:

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 (for example, a line or a trunk) often contain the value -1. Treat this as the same as Not Applicable.

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

The most current upgrade and installation information for CWM Release 15.0.00 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 Release 15.0.00 patch 5.

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 Release 15.0.00 Patch 5 Installation

Contents of this patch:

•CWM Server

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

•CWM SNMP Agent

15.0.00-P5_SNMPAgent.tar.gz

•CWM SSC (Standalone Statistics Collector)

15.0.00-P5_SSC.tar.gz

•CWM SSM (Standalone Statistics Manager)

15.0.00-P5_SSM.tar.gz

•WANDEST Server 2.5 Patch 5

wandest2.5-P5_wdserver.tar.gz

•WANDEST Client 2.5 Patch 5

wandest2.5-P5_wdclient.tar.gz

•RTM Proxy

15.0.00-P5_RTMProxy.tar.gz

Note The RTM Proxy Patch 5 tar file is for the purpose of working with Standalone Statistic Manager only. It is not required for setting up a northbound interface. If the 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 perform 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 at this location. In the examples below the directory is called <dbexport-location>. In each command below, substitute the name you assigned.

# 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 drops all the network data so that you will only export the user data in each database).

# coldstart

d. Export the stratacom database

# dbexport stratacom -o <dbexport-location>

e. Export the scmdb database

# dbexport scmdb -o <dbexport-location>

f. Export the 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

Note The screenshots used as examples in the following sections refer to Patch 2. The Patch 5 installation screens are the same, except for the patch number.

Step 1 Stop stats collection and disable stats on VXSM.

Step 2 Log in to the CWM server as user root

# su

Step 3 Stop the core.

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

# cp 15.0.00-P5_CWM.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 15.0.00-P5_CWM.tar.gz

Step 8 Extract the tar file

# tar -xvfp 15.0.00-P5_CWM.tar

Step 9 Execute the patch installationscript to begin the install process by entering the following command:

# ./InstallCWM15Patch5.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 appears.

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

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 10 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 window displays:

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

The next window 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 window displays what will be installed (15.0.00 Patch 5), which directory it will be installed in, and how much disk space it will take.

:

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

After the install program finishes downloading all the files, the finished installing window appears. Click the Finish button to exit the InstallShield program.

The following message appears,

Reconfiguring Orbix is in progress ...

cwm_tballraker19_domain.cfg file is backed up as cwm_tballraker19_domain.cfg_15.0.00. If you have done any manual updates on cwm_tballraker19_domain.cfg before, Please update the new cwm_tballraker19_domain.cfg with the changes available in the original file at /usr/users/svplus/install after the Patch Installation is completed. Press Enter to continue...

Step 11 If WANDEST Server Release 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 to un-comment any of the tables listed that you want triggers in.

Download or copy the wandest2.5-P5_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-P5_wdserver.tar.gz

Untar the tar file

For example, # tar -xvfp wandest2.5-P5_wdserver.tar

Switch to root

Run the installation script to install the patch

For example, # ./InstallWDS25Patch5.csh

Step 12 Exit from root and open a new terminal window to start the core.

Verifying and Restoring Your Saved Database After Installing Patch 5

If Informix did not come up online after restarting CWM, perform the following steps to restore the database you saved before installing Patch 5:

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

Step 1 Log in to the workstation as 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 the onconfig file for editing

# 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 Log in to the CWM server as user root

# su

Step 2 Stop the core.

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

# cp 15.0.00-P5_SNMPAgent.tar.gz /tmp

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

# cd /tmp

Step 5 Remove the disk1 directory if it exists

# rm -rf disk1

Step 6 Decompress the compressed tar files

# gunzip 15.0.00-P5_SNMPAgent.tar.gz

Step 7 Extract the tar file

# tar -xvfp 15.0.00-P5_SNMPAgent.tar

Step 8 Execute the installation script:

# ./InstallAgent15Patch5.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 9 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 window displays:

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

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

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

The directory you enter here is where the patch install program will copy your existing SNMP Agent files 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 window displays what will be installed (SNMP Agent Patch 5), which directory it will be installed in, and how much disk space it will take.

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

After the install is finished, the following window displays:

Click the Finish button to exit from the InstallShield program.

Step 10 Exit from root and open a new terminal window to start the core.

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

# cp 15.0.00-P5_SSC.tar.gz /tmp

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

# cd /tmp

Step 4 Remove the disk1 directory if it exists

# rm -rf disk1

Step 5 Decompress the compressed tar files

# gunzip 15.0.00-P5_SSC.tar.gz

Step 6 Extract the tar file

# tar -xvfp 15.0.00-P5_SSC.tar

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

# ./InstallSSC15Patch5.csh

The following message appears:

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 and open a new terminal window to start the core.

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

# cp 15.0.00-P5_SSM.tar.gz /tmp

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

# cd /tmp

Step 5 Remove the disk1 directory if it exists

# rm -rf disk1

Step 6 Decompress the compressed tar files

# gunzip 15.0.00-P5_SSM.tar.gz

Step 7 Extract the tar file

# tar -xvfp 15.0.00-P5_SSM.tar

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

# ./InstallSSM15Patch5.csh

Step 9 Exit from root and open a new terminal window to start the core.

Installing the CWM RTM Proxy Patch on the CWM Machine:

Note The RTM Proxy Patch 5 tar file is for the purpose of working with Standalone Statistics Manager only. It is not required as part of configuring a 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 Log in to the CWM machine as user root

# su

Step 2 Stop the core.

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

# cp 15.0.00-P5P_RTMProxy.tar.gz /tmp

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

# cd /tmp

Step 5 Remove the disk1 directory

# rm -rf disk1

Step 6 Decompress the compressed tar files

# gunzip 15.0.00-P5_RTMProxy.tar.gz

Step 7 Extract the tar file

# tar -xvfp 15.0.00-P5_RTMProxy.tar

Step 8 Execute the InstallRTM15Patch5.csh script:

# ./InstallRTM15Patch5.csh

The following message appears:

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 9 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 window appears:

Click the Next button. The License Agreement window appears, as shown below:

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

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

The directory you enter here is where the patch install program will copy your existing CWM RTM proxy files 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 window displays what will be installed (RTM Proxy Patch 5), which directory it will be installed in, and how much disk space it will take.

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

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

Step 10 Exit from root and open a new terminal window to start the core.

WANDEST Release 2.5, Patch 5

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-P5_wdserver.tar.gz

•WANDEST Client

–wandest2.5-P5_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 Log in to the CWM workstation as user svplus

Step 2 Stop the core

Step 3 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 4 Switch to root (for example, su)

# su

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

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

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

# cd /tmp

Step 7 Remove the disk1 directory

# rm -rf disk1

Step 8 Decompress the compressed tar files

# gunzip wandest2.5-P5_wdserver.tar.gz

Step 9 Extract the tar file

# tar -xvfp wandest2.5-P5_wdserver.tar

Step 10 Run the installation script to install the patch:

# ./InstallWDS25Patch5.csh

Step 11 Exit from root.

Step 12 Perform a coldstart:

# coldstart

Step 13 Open a new terminal to start the core.

Installing the WANDEST Client Patch:

Step 1 Log in 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-P5_wdclient.tar.gz /tmp

Step 3 Change to the 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-P5_wdclient.tar.gz

Step 6 Untar the tar file:

# tar -xvfp wandest2.5-P5_wdclient.tar

Step 7 Run the installation script to install the patch:

# ./InstallWDC25Patch5.csh

Step 8 Exit from root.

Uninstalling Patch 5

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

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 Force Delete Feature

The CWM 15.0.00 Patch 2 release introduced the Force 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:

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 corresponding log file(s) will be "<processName>.<pid>.log".

Adding a Desktop Shortcut for the CWM Client Application

To add a CWM Client application desktop shortcuts, perform the following steps:

Step 1 Ensure that the web browser is installed and running on the client machine.

Step 2 Connect to the CWM server using its workstation name followed by:1551 (for example, http://cwmhost:1551 or http://cwmhost.company.com:1551).

1551 is the software port number for the CWM Client web page.

Step 3 Drag any of the CWM applications launch points to the desktop.

Cisco Info Center Version

CWM Release 15 supports integration with the Cisco Info Center (v3.5 v3.6 v3.6.1) application so that two applications can function together. To facilitate this integration, CWM Release 15 includes a tar file that can be installed using the Cisco Info Center update utility (nco_update). This tar file is provided in a format that the update utility can process on the CWMAgent CD-ROM.

The 15.0.00-P5_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 Release 15.0.00 Patch 5, save and then apply the CIC36Pipp000CWM15 tar file that is available in the CWM15.0.00 SNMP Agent CD instead.

Note Apply this patch only to CIC v3.5 and v3.6 only. CIC 3.6.1 already has the latest rules for CWM15.x, so there is no need to apply this patch.

The update utility is a tool that is used to install new rules, enhancements, and new lookups necesssary for CIC to function with CWM Release 15.

Install the Cisco Info Center updates for CWM 15.0 on the host that is running the Cisco Info Center RTTrapd Info Mediator.

For additional information on Cisco Info Center documentation, refer to the Documentation Guide for Cisco Info Center, 3.6, which is provided in the Cisco Info Center product box and at the following URL:

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.

Beginning with the CWM 15.0.00 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 Release 15.0.00. The applicable trap is missing so CWM cannot monitor the back card.

For both RPM and RPM-PR cards managed by ChassisView in CWM Release 15.0.00 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.

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.

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_INTERVAL and 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 600, the default is 60. The range for EVENT_REDELIVERY_COUNT is 0 through 10. 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 Log in 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.

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 Release 15.0.00 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 Release 15.0.00 software and other associated software.

Known Anomalies in CWM Release 15.0.00 Software

This section lists known anomalies in CWM Release 15.0.00 software as of 05/05/05.

The svAtmPortVcCount and cwmPvcRsrcMaxLcns MIB variables only return correct data for BPX's. During an SNMP walk on these variables, the data returned for IGX's is the last value returned by a BPX (i.e. data for the last port of the most recent BPX in an alphabetical node listing).

Documentation (Part# 78013569-01 D0) states that svAtmPortVcCount applies to both BPX's and IGX's (pg 3-244), while the cwmPvcRsrcMaxLcns

variable supposedly only applies to BPX's (pg 3-290). Since the documentation suggests that svAtmPortVcCount should work for IGX's, this appears to be a bug.

(Obviously my intention is to get both MIB variables working for both switch types.)

The CWM 15 documentation (part# OL-4551-01 B0) states the same compatibility

information (svAtmPortVcCount for BPX's and IGX's - pg. C-257; cwmPvcRsrcMaxLcns for BPX's only - pg. C-384). I would like to know if I can expect CWM 15 to behave just as CWM 11 does or if upgrading would solve my problem.

Our BPX's and IGX's are running at software rev. 9.3.45.

Workaround:

None.

CSCeh15769

Background map is not getting set due to hostname not getting resolved

Symptom:

CWM server is not reachable from the PC by name, setting the backgound map fails because the hostname is not getting resolved

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. Set to C. The ddts cannot be resolved before CWM 15.1 due to switch dependency.

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. Set to C. The ddts cannot be resolved before CWM 15.1.

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. Set to C.

CSCed91850

Symptom:

xdbroker reinitialized once

Conditions:

Running 12.0.00-P1.1

Workaround:

Process was respawned by watchdog. Set to M.

CSCee12471

Finder server coredump

Symptom:

finder server coredump

Conditions:

Unknown.

Workaround:

Unknown. Set to M.

CSCef10445

Symptom:

wdupdate error in scmsaexecinstall log

Conditions:

Seen on SSM during upgrade to 15.0.00-P2C

Workaround:

N/A. Set to D. This is a duplicate of CSCee61329.

CSCef37402

Symptom:

MGX nodes in mode 1, ooemc not running

Conditions:

Running 15.0.00-P2K

Workaround:

Coldstart the CWMs.

This bug was set to U (unreproducible).

CSCef38504

Symptom:

SCTD reinitialized once, did not respawn

Conditions:

Running 15.0.00-P2K

Workaround:

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

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:

Obtaining Documentation

Cisco documentation and additional literature are available on Cisco.com. Cisco also provides several ways to obtain technical assistance and other technical resources. These sections explain how to obtain technical information from Cisco Systems.

Product Documentation DVD

Cisco documentation and additional literature are available in the Product Documentation DVD package, which may have shipped with your product. The Product Documentation DVD is updated regularly and may be more current than printed documentation.

The Product Documentation DVD is a comprehensive library of technical product documentation on portable media. The DVD enables you to access multiple versions of hardware and software installation, configuration, and command guides for Cisco products and to view technical documentation in HTML. With the DVD, you have access to the same documentation that is found on the Cisco website without being connected to the Internet. Certain products also have .pdf versions of the documentation available.

The Product Documentation DVD is available as a single unit or as a subscription. Registered Cisco.com users (Cisco direct customers) can order a Product Documentation DVD (product number DOC-DOCDVD=) from Cisco Marketplace at this URL:

Ordering Documentation

Nonregistered Cisco.com users can order technical documentation from 8:00 a.m. to 5:00 p.m. (0800 to 1700) PDT by calling 1 866 463-3487 in the United States and Canada, or elsewhere by calling 011 408 519-5055. You can also order documentation by e-mail at tech-doc-store-mkpl@external.cisco.com or by fax at 1 408 519-5001 in the United States and Canada, or elsewhere at 011 408 519-5001.

Documentation Feedback

You can rate and provide feedback about Cisco technical documents by completing the online feedback form that appears with the technical documents on Cisco.com.

You can send comments about Cisco documentation to bug-doc@cisco.com.

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

Reporting Security Problems in Cisco Products

Cisco is committed to delivering secure products. We test our products internally before we release them, and we strive to correct all vulnerabilities quickly. If you think that you might have identified a vulnerability in a Cisco product, contact PSIRT:

An emergency is either a condition in which a system is under active attack or a condition for which a severe and urgent security vulnerability should be reported. All other conditions are considered nonemergencies.

Tip We encourage you to use Pretty Good Privacy (PGP) or a compatible product to encrypt any sensitive information that you send to Cisco. PSIRT can work from encrypted information that is compatible with PGP versions 2.x through 8.x.

Never use a revoked or an expired encryption key. The correct public key to use in your correspondence with PSIRT is the one linked in the Contact Summary section of the Security Vulnerability Policy page at this URL:

Obtaining Technical Assistance

Cisco Technical Support provides 24-hour-a-day award-winning technical assistance. The Cisco Technical Support & Documentation website on Cisco.com features extensive online support resources. In addition, if you have a valid Cisco service contract, Cisco Technical Assistance Center (TAC) engineers provide telephone support. If you do not have a valid Cisco service contract, contact your reseller.

Cisco Technical Support & Documentation Website

The Cisco Technical Support & Documentation website provides online documents and tools for troubleshooting and resolving technical issues with Cisco products and technologies. The website is available 24 hours a day, at this URL:

Access to all tools on the Cisco Technical Support & Documentation website requires a Cisco.com user ID and password. If you have a valid service contract but do not have a user ID or password, you can register at this URL:

Note Use the Cisco Product Identification (CPI) tool to locate your product serial number before submitting a web or phone request for service. You can access the CPI tool from the Cisco Technical Support & Documentation website by clicking the Tools & Resources link under Documentation & Tools.Choose Cisco Product Identification Tool from the Alphabetical Index drop-down list, or click the Cisco Product Identification Tool link under Alerts & RMAs. The CPI tool offers three search options: by product ID or model name; by tree view; or for certain products, by copying and pasting show command output. Search results show an illustration of your product with the serial number label location highlighted. Locate the serial number label on your product and record the information before placing a service call.

Submitting a Service Request

Using the online TAC Service Request Tool is the fastest way to open S3 and S4 service requests. (S3 and S4 service requests are those in which your network is minimally impaired or for which you require product information.) After you describe your situation, the TAC Service Request Tool provides recommended solutions. If your issue is not resolved using the recommended resources, your service request is assigned to a Cisco engineer. The TAC Service Request Tool is located at this URL:

For S1 or S2 service requests or if you do not have Internet access, contact the Cisco TAC by telephone. (S1 or S2 service requests are those in which your production network is down or severely degraded.) Cisco engineers are assigned immediately to S1 and S2 service requests to help keep your business operations running smoothly.

To open a service request by telephone, use one of the following numbers:

Definitions of Service Request Severity

To ensure that all service requests are reported in a standard format, Cisco has established severity definitions.

Severity 1 (S1)—Your network is "down," or there is a critical impact to your business operations. You and Cisco will commit all necessary resources around the clock to resolve the situation.

Severity 2 (S2)—Operation of an existing network is severely degraded, or significant aspects of your business operation are negatively affected by inadequate performance of Cisco products. You and Cisco will commit full-time resources during normal business hours to resolve the situation.

Severity 3 (S3)—Operational performance of your network is impaired, but most business operations remain functional. You and Cisco will commit resources during normal business hours to restore service to satisfactory levels.

Severity 4 (S4)—You require information or assistance with Cisco product capabilities, installation, or configuration. There is little or no effect on your business operations.

Obtaining Additional Publications and Information

Information about Cisco products, technologies, and network solutions is available from various online and printed sources.

•Cisco Marketplace provides a variety of Cisco books, reference guides, documentation, and logo merchandise. Visit Cisco Marketplace, the company store, at this URL:

•Cisco Press publishes a wide range of general networking, training and certification titles. Both new and experienced users will benefit from these publications. For current Cisco Press titles and other information, go to Cisco Press at this URL:

•Packet magazine is the Cisco Systems technical user magazine for maximizing Internet and networking investments. Each quarter, Packet delivers coverage of the latest industry trends, technology breakthroughs, and Cisco products and solutions, as well as network deployment and troubleshooting tips, configuration examples, customer case studies, certification and training information, and links to scores of in-depth online resources. You can access Packet magazine at this URL:

•iQ Magazine is the quarterly publication from Cisco Systems designed to help growing companies learn how they can use technology to increase revenue, streamline their business, and expand services. The publication identifies the challenges facing these companies and the technologies to help solve them, using real-world case studies and business strategies to help readers make sound technology investment decisions. You can access iQ Magazine at this URL:

•Internet Protocol Journal is a quarterly journal published by Cisco Systems for engineering professionals involved in designing, developing, and operating public and private internets and intranets. You can access the Internet Protocol Journal at this URL:

•Networking Professionals Connection is an interactive website for networking professionals to share questions, suggestions, and information about networking products and technologies with Cisco experts and other networking professionals. Join a discussion at this URL: