Guest

Cisco WAN Manager

Release Notes for the Cisco WAN Manager, 15.1.50 P2

  • Viewing Options

  • PDF (589.4 KB)
  • Feedback
Release Notes for Cisco WAN Manager Release 15.1.50, Patch 2

Table Of Contents

Release Notes for Cisco WAN Manager Release 15.1.50, Patch 2

Contents

Releases Supported by CWM 15.1.50, Patch 2

System Requirements

CWM Server Requirements

Java Client Requirements

Standalone Statistics Manager Requirements

Solaris Patch Requirements

Before You Begin Installing Patches

Installing the Patches

HP OpenView Requirements

Informix Requirements

CWM 15.1.50 Packaging

Supported Hardware

New Hardware Supported by CWM 15.1.50, Patch 1

Existing Hardware Supported by CWM 15.1.50

Releases Certified for CWM 15.1.50, Patch 2

New Features and Enhancements

Features Introduced in CWM 15.1.50, Patch 2

Features Introduced in CWM 15.1.50, Patch 1

Features Introduced in CWM 15.1.50

CWM Feature Limitations

Features Not Supported

Feature Limitations

Configuration Center Limitations

HP OpenView Limitations

SSM Issues

CWM-to-CWM Communication Limitations

Network Monitor Limitations

CWM Notes and Cautions

Installing and Uninstalling CWM 15.1.50, Patch 2

Before You Start

Installing Patch 2

Backing Up the Existing Database

Installing the CWM Server Patch

Verifying and Restoring Your Saved Database

Installing the SNMP Agent (Service Agent) Patch

Installing the SSC Patch

Installing the SSM Patch

Installing the RTM Proxy Patch

Creating a CWM Auto-Restart Shell Script

Installing WANDEST 2.6.50, Patch 2

Installing the WANDEST Server Patch

Installing the WANDEST Client Patch

Uninstalling Patch 2

SNMP Service Agent Trap Limitation

Caveats

Related Documentation

Obtaining Documentation

Cisco.com

Product Documentation DVD

Ordering Documentation

Documentation Feedback

Cisco Product Security Overview

Reporting Security Problems in Cisco Products

Obtaining Technical Assistance

Cisco Technical Support & Documentation Website

Submitting a Service Request

Definitions of Service Request Severity

Obtaining Additional Publications and Information


Release Notes for Cisco WAN Manager Release 15.1.50, Patch 2


February 2006

Rev. C0

These release notes are for use with the Cisco WAN Manager (CWM) 15.1.50, Patch 2 software release. This document also includes the release note data for the CWM 15.1.50 software.

The first section describes all of the switch releases that CWM 15.1.50, Patch 2 supports.

Contents

Releases Supported by CWM 15.1.50, Patch 2

System Requirements

CWM 15.1.50 Packaging

Supported Hardware

Releases Certified for CWM 15.1.50, Patch 2

New Features and Enhancements

CWM Feature Limitations

Installing and Uninstalling CWM 15.1.50, Patch 2

Creating a CWM Auto-Restart Shell Script

SNMP Service Agent Trap Limitation

Caveats

Related Documentation

Obtaining Documentation

Documentation Feedback

Cisco Product Security Overview

Obtaining Technical Assistance

Obtaining Additional Publications and Information

Releases Supported by CWM 15.1.50, Patch 2

Table 1 shows the switches and releases that the CWM 15.1.50, Patch 2 software supports.

For additional information on supported products, see these sections:

Supported Hardware

Releases Certified for CWM 15.1.50, Patch 2

Table 1 Switches and Releases Supported by CWM 15.1.50, Patch 2

Switch
Supported Software Release

Existing WAN switching products, including the Cisco IGX 8400 series and the Cisco BPX 8600 series

9.2.33-9.2.43
9.3.05-9.3.51
9.4.00-9.4.12

SES PNNI Controller

3.0.10-3.0.25
4.0.00-4.0.15

MGX 8220

4.1.07-4.1.12
5.0.12-5.0.2

MGX 8230, 8250 and 8850 (PXM1)

1.1.40-1.1.42
1.2.00-1.2.13
1.2.20-1.2.21
1.3.00-1.3.12
1.3.14

MGX8830/B (PXM45/C)

5.1.20
5.2.00

MGX 8830 and 8850 (PXM1E)
MGX 8850 (PXM45)

3.0.23-3.0.25
4.0.00-4.0.17
5.0.00-5.0.20
5.1.20
5.2.00

MGX 8880 (PXM45)

5.0.00-5.0.20
5.1.20
5.2.00

MGX 8950 (PXM45)

2.1.76-2.1.81
3.0.23-3.0.25
4.0.00-4.0.17
5.0.00-5.0.20
5.1.20
5.2.00


System Requirements

This section describes the system requirements for using the CWM. See these System Requirements sections:

CWM Server Requirements

Java Client Requirements

Standalone Statistics Manager Requirements

Solaris Patch Requirements

HP OpenView Requirements

Informix Requirements

In addition to the CWM platform requirements listed in the CWM installation guide, also consider the following:

UltraSPARC II, UltraSPARC III, and UltraSPARCIIIi workstations—The CWM is compatible with them. For system requirements, see Tables 2 through 5.

Ultra 60 and Enterprise 450 and 4500—They were certified with earlier CWM releases and can still be used with this release. For the certified system requirements, see the CWM 11.0.10 release notes. Cisco does not provide technical support for Sun configurations or products that Sun Microsystems no longer supports.

Graphics card—A graphics card is required when using the Java Client to access to the CWM.

Video—Video on the CWM server is required only for user access or maintenance. It can be added to Sun servers or workstations. For Ultra and Enterprise, a video adapter is required.

Informix database—The minimum disk size for the Informix raw database is 1.7 GB. However, we strongly recommend you provide more disk space for the statistics collection process. Note that if statistics are collected by using the CWM, multiple partition chunks are required to be added to Informix. For additional information on disk partitioning, refer to the Cisco WAN Manager Installation Guide.

Firewalls—If you are using a firewall between the server and the clients, you must open a range of ports for the CWM servers. For additional information about using firewalls, see the "Using Firewalls" section in the CWM installation guide. You can access all CWM documentation at this website:

http://www.cisco.com/en/US/products/sw/netmgtsw/ps2340/tsd_products_support_series_home.html

CWM Server Requirements

Table 2 lists the system requirements for the CWM server. Note also the following about CWM servers:

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 System Requirement Guidelines in the CWM 11.0.10 release notes.

If you are using an Ultra 60 (low-end platform), it should have at least 2 GB of RAM.

Table 2 CWM Server System Requirements 

CWM
Platform
No.
of CPUs
Min.
CPU Speed (MHz)
Min.
RAM
(GB)
Min.
Swap Space
(GB)
Min. Disk Space
(GB)
Max No. of PVC/SPVC Connections or
Connection Segments for XPVC
Max.
No. of
PC
Clients
Max. No. of Nodes
UltraSPARC III Server Used for Network Scale Testing by Cisco

Low - Medium #1

1

900

2

4

1 x 36

100K

10

100

Netra 20, Sun Fire 280R

Low - Medium #2

1

1000

2

4

2 x 36

100K

10

100

Sun Fire V210

Medium #1

2

900

4

8

1 x 36

200K

20

500

Netra 20, Sun Fire 280R

Medium #2

2

1280

4

8

2 x 72

200K

20

500

Sun Fire V240

High- Carrier Grade

4

900

8

16

2 x 36

1M

40

1000

Sun Fire V880

Carrier Grade

8

900

16

32

2 x 36

2M

100

2000

Sun Fire V880

Carrier Grade 2

8

900

40

88

5 x 68

3M

100

2000

Sun Fire V880


Java Client Requirements

Table 3 lists the Java Client system requirements.

Table 3 Java Client System Requirements 

CWM Java Client
Operating System
Web Browser
No. of CPUs
CPU
Speed (MHz)
RAM (MB)
Swap Space (GB)
Disk
Free
Space
(MB)

PC

Windows 2000
Windows NT 4.0, SP 6a
Windows XP, SP1

IE 6.0
Netscape 4.76
J2SE v1.4.2_02

1: Pentium 3

750

512

N/A

130

SPARC10

Solaris 8

Solaris 9

Netscape 4.76

1: 450 MHz

450

512

1

130


Standalone Statistics Manager Requirements

Table 4 lists the Standalone Statistics Collector (SSC) or Standalone Statistics Manager (SSM) system requirements, which are the same. Note also the following:

The file size is 2 Mbytes (typically holds statistics with peak enabled for 20-KB endpoints).

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

Average Network Transfer Rate is the required TFTP/FTP throughput to collect the maximum number of files (combination of server performance and network bandwidth and traffic).

One SSM can control a maximum of 12 SSCs.

Table 4 SSC or SSM System Requirements 

SSC Platform
No. of CPUs
Min. CPU Speed (MHz)
Average Network Transfer Rate
RAM
Swap Space (GB)
Disk Space (GB)
Max. No. of
Stats Files (15-min.
collection
intervals)
Server Used in Cisco Testing

Low

2

450

170 kBps

512 MB

2

2 x 18

350

U60

Medium #1

2

450

3.5 MB/sec

512 MB

2

2 x 18

700

U60

Medium #2

1

1002

4 MB/sec

1 GB

2

2 x 73

550

Sun Fire 210/240

Medium #3

1

900

1.7 MB/sec

1 GB

2

1 x 36

700

Netra 20 or Sun Fire 280R

High #1

2

900

3.5 MB/sec

4 GB

8

1 x 36

900

Netra 20 or Sun Fire 280R

High #2

2

1200

4 MB/sec

1 GB

2

2 x 73

1200

Sun Fire 240


Table 5 lists additional system requirements for the parser in the CWM Server, SSC, or SSM. If the parser is enabled, add the applicable system requirements in Table 5 to the CWM server requirements listed in Table 2 or to the SSM or SSC requirements listed in Table 4.

Five statistics are collected from each connection segment endpoint in 15-minute file collection intervals. Collecting statistics for 4-million endpoints with five 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.

Table 5 Parser System Requirements for the CWM Server, SSC, or SSM 

SSM Platform
No. of CPUs
Min. CPU Speed (MHz)
RAM (GB)
Swap Space (GB)
Min.
Disk Space
(GB)
Max. No. of Connection Segment Endpoints (Statistics Enabled)
Server Used in Cisco Testing

Low - Medium

2

450

1

2

2 x 18

300 KB

Ultra 60

Low - Medium

1

900

2

4

2 x 36

750 KB

Netra 20, Sun Fire 280R

Medium

2

900

4

8

2 x 36

2 MB

Netra 20, Sun Fire 280R

High - Carrier Grade

4

900

8

16

2 x 36

4 MB

Sun Fire V880


Solaris Patch Requirements

This section shows the Solaris patches that you must install for the CWM and those that we recommend you install. You will install these patches after you install the Solaris 8 or 9 operating system.

Before You Begin Installing Patches

For best results, follow these Sun recommendations before you begin installing the patches:

After installing the Solaris 8 or 9 operating system, you must install the kernel patch that is required for your operating system (see Table 6 for the version numbers):

Solaris 8: Kernel Patch 27 or later

Solaris 9: Kernel Patch 12 or later

After you have installed the patch, you will install the additional patches if they were not already installed as part of the cluster.

Use the single-user mode to install most patches.

Shut down CWM processes before installing the patches.

Avoid installing these patches that cause problems with Informix during startup.

SPARC Platform

Solaris 8 with patches 109147-36 through 109147-39

Solaris 9 with patches 112963-21 through 112963-24

x86 Platform

Solaris 8 with patches 109148-36 through 109148-39

Solaris 9 with patches 113986-17 through 113986-20

Not all Solaris patches or patch clusters require a reboot. If a reboot is not required, you can start the CWM after the patch is installed.

Installing the Patches

Use this procedure and sequence to install the patches.

The procedure assumes that you have installed the Solaris 8 or 9 operating system.


Step 1 Verify which patches are already installed on your CWM workstation. To display the installed patches, use the Solaris showrev -p command.

Step 2 Go to the SunSolve Patch Access website to access the patches:

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

(If you have a SunSpectrum contract, you can also access patches from SunService.)

Step 3 Install one of these kernel patches (that corresponds to your operating system):

Kernel Patch 27 for Solaris 8

Kernel Patch 12 for Solaris 9.

See Table 6 for the correct version number.

Step 4 Install the rest of the required patches if they were not already installed as part of the cluster. Depending on your situation, you may want to enter only first 6 digits of the patch number in the Find Patch field on the Sun Patch Access site and not the version extension to obtain the latest patch version.

Step 5 Install the recommended patches, as needed and desired. (Several of these recommended patches may require a service contract with Sun.)

Table 6 Required and Recommended Solaris Patches 

Patches
Solaris 8
Solaris 9

Required to be installed first

Kernel Patch 27 (108528-27 or higher)

Kernel Patch 12 (112233-12 or higher)

Required

108652-35
109326-05
110670-01
110700-01
110898-03
110945-04
110934-04
111327-05
111626-01

112874-31
(if Solaris patch 112233-11 or higher is installed)
112785-42
112970-07
114716-01
113580-01
114224-02
112998-03
112811-01

Recommended

110951-01
110662-06
110615-03
110286-05
109324-04

115336-02
112964-07
113575-05
112808-06


HP OpenView Requirements

HP OpenView is used only for viewing the event log and is not required for other CWM procedures. CWM 15.1.50 works with HP OpenView 6.3 or 7.0.

HP OpenView is not bundled with the CWM CDs. You must order HP OpenView 6.3 or 7.0 directly from Hewlett-Packard and follow the H-P installation requirements and procedures. (Refer to HP OpenView Network Node Manager Products, Installation Guide, Part No. J1136-90000.)

Informix Requirements

CWM 15.1.50 uses Informix 9.4 for database operations. The Informix software is bundled with CWM included on the CWM Server CD in the CWM CD package. The Informix program is installed automatically when CWM is installed.

CWM 15.1.50 Packaging

This section describes the CWM and associated software and CDs. See Table 7 for software information and CD contents.

The CWM 15.1.50 Software Evaluation CD package includes all CWM CDs and functionality. All of the CWM features are available until the 45-day evaluation period expires. As noted in Table 7, when you order the CWM package, you receive the CWM Server CD and the CWM Documentation CD.

Table 7 CWM 15.1.50 and Associated Software 

Software
CD
Notes

CWM Server
Informix Server
CWM Java Client

CWM Server CD

Part of the CWM package.

CWM documentation (PDF)
Acrobat Reader
gzip

CWM Documentation CD

Part of the CWM package.

Note The gzip utility is used to decompress the gz files. The command is gzip -d.

CWM Service Agent

Service Agent CD

The CD must be ordered separately from the CWM Client/Server package CD set.

Standalone Statistics Collection Manager

Standalone Statistics Collection Manager CD

The CD must be ordered separately from the CWM package CD set.

The Standalone SCM software includes the WANDEST client software and the Informix server software.

RTM Proxy for the SCM application

RTM Proxy for SCM Application CD

This application is included on a separate CD with the Standalone Statistics Collection Manager software only when you have ordered that software. It is meant to be installed only with the Standalone Statistic Manager and not on systems using the Service Agent. If you have already installed the Service Agent software and you attempt to install this application, you will see errors because the ~/config/process.conf file has duplicate entries for the RTM Proxy.

To install the RTM Proxy for SCM application from the CD, refer to the CWM installation guide.

WANDEST

WANDEST Server Software CD

WANDEST Client Software CD

The CD must be ordered separately from the CWM set.

Automated Bulk Provisioning

Automated Bulk Provisioning Software CD

The CD must be ordered separately from the CWM set.

Cisco WAN Modeling Tools

Cisco WAN Modeling Tools Software CD

The CD must be ordered separately from the CWM set.


Supported Hardware

The following subsections list all of the hardware that the CWM 15.1.50, Patch 2, supports. No new hardware was added with Patch 2. The sections show the supported hardware that was added with Patch 1 and the hardware that CWM 15.1.50 supports.

See also these sections:

Releases Supported by CWM 15.1.50, Patch 2

Releases Certified for CWM 15.1.50, Patch 2

New Hardware Supported by CWM 15.1.50, Patch 1

Table 8 lists the new hardware that CWM 15.1.50, Patch 1 supports.

Table 8 New Hardware Supported in CWM 15.1.50, Patch 1 

Platform Series
Front Card
Back Card

MGX 8830/B with PXM45/C
MGX8850 with PXM45
MGX 8850/B with PXM45

(For the 1:N redundancy of the MPSM-16-T1E1, MGX 8830/B supports the RCON-1TO3-8830 back card, and MGX 8850/B supports the RCON-1TO3-8850 and RCON-1TO5-8850 back cards.)

AXSM-8-622-XG

SFP-4-622


Existing Hardware Supported by CWM 15.1.50

The tables on the following pages list the hardware that CWM 15.1.50 supports. Table 9 provides an index of the table numbers that apply to particular platforms.


IGX 8400 Series

For IGX 8400 product details, refer to Table 10 in the release notes at this website:

http://www.cisco.com/univercd/cc/td/doc/product/wanbu/bpx8600/9_4/rnote/9412rn.pdf

Table 10 IGX 8400 

Front Card 
Back Card

IGX-HDM

IGX-NPM

SCM

IGX-NTM

BC-xxxxx-T1/E1/SR/Y1

IGX-UFM-4C
IGX-UFM-8C

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

IGX-UFM-U

BC-UFI-12V35
BC-UFI-12X21
BC-UFI-4HSSI

IGX-URM

BC-2FE2V

IGX-UVM

UVI-2T1EC/2E1EC
UVI-2J1EC

IGX-UXM
IGX-UXME

BC-UAI-4-155-MMF/SMF
BC-UAI-2-155-SMF
BC-UAI-2SMFXLR
BC-UAI-4SMFXLR
BC-UAI-3/6-T3
/E3
BC-UAI-4/8-E1-BNC
BC-UAI-4/8-T1/E1-DB15
BC-UAI-4-STM1E


BPX 8600 Series

For BPX 8600 product details, refer to Table 9 in the release notes at this website:

http://www.cisco.com/univercd/cc/td/doc/product/wanbu/bpx8600/9_4/rnote/9412rn.pdf

Table 11 BPX 8600 

Front Card 
Back Card

ASI-2T3/E3

ASI-155E

ASM-LM

BNI-3-T3/C
BNI-3-E3/C
BNI-155E
BNI-2-155/B

BPX-E3-BC
BPX-MMF/SMF/SMFLR-2-BC

BPX-ASM

BPX-ASM-BC

BPX-BCC

BPX-BCC-BC

BPX-BCC-3

BCC-3BC

BPX-BCC4V

BPX-BCC-4V/B

BPX-BME

BPX-T3/E3-BC

BPX-BME-OC12

BPX-E3-BC
BPX-MMF/SMF/SMFLR-2-BC

BPX-BXM-155-8

BPX-MMF/SMF/SMFLR-8-155

BPX-BXM-155-4
BPX-BXM-E-155

BPX-MMF/SMF/SMFLR-4-155

BPX-BXM-622
BPX-BXM-E-622

BPX-622-2-BC
BPX-SMF/SMFLR-622-BC
BPX-SMF/
SMFLR-622-2-BC

BPX-BXM-T3/E3

BPX-T3/E3-BC

BPX-STM1-EL-4
BPX-T3/E3

BPX-E3-BC
BPX-MMF/SMF/SMFLR-2-BC

BPX-XLR

BPX-E3-BC
BPX-MMF/SMF/SMFLR-2-BC

RDNT-SMF-155
RDNT-LR-155/622
RDNT-SMF-622

BPX-E3-BC
BPX-MMF/SMF/SMFLR-2-BC


MGX 8220 Series

For MGX 8220 product details, refer to Table 8 in the release notes at this website:

http://www.cisco.com/univercd/cc/td/doc/product/wanbu/bpx8600/9_4/rnote/9412rn.pdf

Table 12 MGX 8220 

Front Card
Back Card

ASC

ASC-LM

AUSM-4T1E1
AUSM-8T1E1
AUSM--8T1E1/B

RJ-48-8E1/8T1

BNM-155

155-SMF

T3E3-B/D

T3E3-B/D

CESM-8T1E1

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

FRSM-4T1E1
FRSM-8T1E1

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

FRSM-HS1

HSI-4X21/3HSSI

FRSM-VHS

HS2

IMATM-8T1E1/B

RJ-48-T3T1/E3E11.3.12
SMB-E3E1

SRM

DB-15-T1/E1

LM-3T3

AUSM-4T1E1
AUSM-8T1E1
AUSM-8T1E1/B

8T1/E1


MGX 8230 Series

For MGX 8230 product details, refer to Tables 16 and 17 in the release notes at this website:

http://www.cisco.com/univercd/cc/td/doc/product/wanbu/mgx8230/13/rnotes/rn1312.pdf

Table 13 MGX 8230 (PXM1) 

Front Card
Back Card

AX-CESM

RJ48-8T1/8E1
SMB-8E1

AX-FRSM

RJ48-8T1/8E1
SMB-8E1

MGX-AUSM

8T1/E1

MGX-CESM

MGX-RJ48-8T1
MGX-BNC-2E3/2E3A/2T3

MGX-FRSM-2CT3
MGX-FRSM-2T3E3

MGX-BNC-2E3/2T3/2E3A

MGX-FRSM-HS1/B

MGX-12IN1-4S

MGX-FRSM-HS2

MGX-HSSI

MGX-FRSM-HS2/B

MGX-HSSI
MGX-12IN1-8S

MGX-RPM-128M/B

MGX-RJ45-FE/4E
MGX-MMF-FE
MGX-MMF/SMF-FDDI
MGX-MMF/SMF-FDDI/FD

MGX-RPM-PR

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

MGX-SRME
MGX-SRME/B

MGX-SMFIR-1-155
MGX-STM1-EL1
T3

MGX-VISM-8T1/8E1

AX-SMB-8E1
AX-R-SMB-8E1
AX-RJ-48-8T1/8E1
AX-R-RJ-48-8T1/8E1
MGX-RJ48-8E1

MGX-VISM-PR

AX-SMB-8E1
AX-R-SMB-8E1
AX-RJ48-8T1/8E1
AX-R-RJ48-8T1/8E1
MGX-RJ48-8E1

PXM1

T3/E3/OC-3/OC-12


MGX 8250 Series

For MGX 8250 product details, refer to Tables 15 and 17 in the release notes at this website:

http://www.cisco.com/univercd/cc/td/doc/product/wanbu/mgx8230/13/rnotes/rn1312.pdf

Table 14 MGX 8250 (PXM1) 

Front Card
Back Card

AX-CESM

AX-RJ48-8T1/8E1
AX-SMB-8E1

MGX-RPM-128M/B

MGX-RJ45-FE/4E
MGX-MMF-FE
MGX-MMF/SMF-FDDI
MGX-MMF-FDDI/FD
MGX-SMF-FDDI/FD

MGX-SRME

MGX-SMFIR-1-155
MGX-STM1-EL1

MGX-AUSM

AX-SMB-8E1
AX-R-SMB-8E1
AX-RJ48-8E1/8T1
AX-R-RJ48-8T1/8E1
MGX-RJ48-8E1

MGX-CESM

MGX-BNC-2E3/2E3A/2T3

MGX-FRSM-HS1/B

MGX-12IN1-4S

MGX-FRSM-HS2

MGX-HSSI

MGX-FRSM-HS2/B

MGX-HSSI
MGX-12IN1-8S

MGX-RPM-PR

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

MGX-VISM-8T1
MGX-VISM-8E1

AX-SMB-8E1
AX-R-SMB-8E1
AX-RJ48-8T1/8E1
AX-R-RJ48-8T1/8E1
MGX-RJ48-8E1

MGX-VISM-PR

AX-RJ48-8T1
AX-R-RJ48-8T1

MPSM-8-T1E1

AX-RJ-48-8T1/8E1
AX-R-RJ-48-8T1/8E1
AX-SMB-8E1
AX-R-SMB-8E1

PXM1

T3/E3/OC-3/OC-12

SRM

LM-3T3


MGX 8850 Series

For MGX 8850 product details, refer to Tables 15 and 17 in the release notes at this website:

http://www.cisco.com/univercd/cc/td/doc/product/wanbu/mgx8230/13/rnotes/rn1312.pdf

Table 15 MGX 8850 (PXM1) 

Front Card
Back Card

AX-CESM

AX-RJ48-8E1/8T1
AX-SMB-8E1

AX-FRSM

AX-SMB-8E1
AX-R-SMB-8E1
AX-RJ48-8E1/8T1
AX-R-RJ48-8E1/8T1
MGX-RJ48-8E1

MGX-AUSM

AX-SMB-8E1
AX-R-SMB-8E1
AX-RJ48-8T1/8E1
AX-R-RJ48-8T1/8E1
MGX-RJ48-8E1

MGX-CESM

RJ48-8T1
R-RJ48-8T1
MGX-BNC-2E3/2E3A/2T3

MGX-FRSM-2CT3
MGX-FRSM-2T3E3

MGX-BNC-2T3/2E3
MGX-BNC-2E3A
MGX-BNC-2T3

MGX-FRSM-HS1/B

MGX-12IN1-4S
MGX-SCSI2-2HSSI/B

MGX-FRSM-HS2

MGX-SCSI2-2HSSI/B

MGX-FRSM-HS2/B

MGX-12IN1-8S

MGX-RPM-PR

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

MGX-RPM-128M/B

MGX-MMF-FE
MGX-RJ45-FE
MGX-RJ45-4E
MGX-MMF/SMF-FDDI
MGX-MMF/SMF-FDDI/FD

MGX-SRME

MGX-SMFIR-1-155
MGX-STM1-EL1

MGX-VISM-8T1
MGX-VISM-8E1

AX-SMB-8E1
AX-R-SMB-8E1
AX-RJ-48-8T1/8E1
AX-R-RJ48-8T1/8E1
MGX-RJ48-8E1

MGX-VISM-PR

AX-RJ48-8T1
AX-R-RJ48-8T1

MPSM-8-T1E1

AX-RJ-48-8T1/8E1
AX-R-RJ-48-8T1/8E1
AX-SMB-8E1
AX-R-SMB-8E1

PXM1

T3/E3/OC-3/OC-12

SRM

LM-3T3


PXM1E on MGX 8830, 8830/B, 8850, and 8850/B Series

For product details, refer to Tables 4 through 8 in the release notes at this website:

http://www.cisco.com/univercd/cc/td/doc/product/wanbu/8850px45/relnote/52008xx0.pdf

Table 16 PXM1E on MGX 8830, 8830/B, 8850, and 8850/B 

Front Card
Back Card

AX-FRSM

AX-SMB-8E1
AX-R-SMB-8E1
AX-RJ48-8T1/8E1
AX-R-RJ48-8T1/8E1
MGX-RJ48-8E1

AX-CESM

AX-RJ48-8E1/8T1
AX-SMB-8E1

MGX-AUSM

AX-SMB-8E1
AX-R-SMB-8E1
AX-RJ48-8T1/8E1
AX-R-RJ48-8T1/8E1
MGX-RJ48-8E1

MGX-FRSM-2T3E3
MGX-FRSM-2CT3

MGX-BNC-2T3/2E3
MGX-BNC-2E3A

MGX-FRSM-HS2/B

MGX-12IN1-8S

MGX-RPM-PR

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

MGX-SRME/B

MGX-BNC-3T3-M
MGX-STM1-EL-1

MPSM-8-T1E1

AX-RJ48-8T1/E1
AX-R-RJ48-8T1/8E1
AX-SMB-8E1
AX-R-SMB-8E1

MPSM-16-T1E1

RBBN-16-T1E1-1N
MCC-16-E1-1N
RED-16-T1E1

(For the 1:N redundancy of the MPSM-16-T1E1, MGX 8830/B supports the RCON-1TO3-8830 back card and MGX 8850/B supports the RCON-1TO3-8850 and RCON-1TO5-8850 back cards.)

MPSM-T3E3-155

SFP-2-155
BNC-3-T3E3
SMB-2-155-EL

PXM1E-8-155

MMF-4-155/C
MMF/SMFIR/SMFLR-1-155-SFP
PXM-UI-S3/B

PXM1E-8-T3E3

SMB-8-T3/E3
PXM-UI-S3/B

PXM1E-16-T1E1

MCC-16-E1
RBBN-16-T1E1
PXM-UI-S3/B

PXM1E-T3E3-155
(also referred to as PXM1E-COMBO)

MGX-T3E3-155
MMF/SMFIR/SMFLR-1-155-SFP
PXM-UI-S3/B

MGX-SRME

MGX-SMFIR-1-155
MGX-STM1-EL1

MGX-SRME/B

MGX-SMFIR-1-155

MGX-VISM-PR

AX-SMB-8E1
AX-R-SMB-8E1
AX-RJ48-8T1/8E1
AX-R-RJ48-8T1/8E1


MGX 8830/B (PXM 45/C) Series

For MGX 8830/B product details, refer to Tables 4 through 8 in the release notes at this website:

http://www.cisco.com/univercd/cc/td/doc/product/wanbu/8850px45/relnote/52008xx0.pdf

Table 17 MGX 8830/B (PXM 45/C) 

Front Card
Back Cards

AXSM-2-622-E

SMFIR/SMFLR-1-622/C

AXSM-8-622-XG

SFP-4-622

AXSM-16-T3E3-E

SMB-8-T3/E3

AXSM-16-155-XG

SFP-8-155
MMF/SMFIRSMFLR-1-155-SFP
MCC-8-155

MGX-SRME/B

MGX-BNC-3T3-M
MGX-STM1-EL-1

MPSM-8-T1E1

AX-RJ48-8T1/8E1
AX-R-RJ48-8T1/8E1
AX-SMB-8E1
AX-R-SMB-8E1

MPSM-T3E3-155

SFP-2-155
BNC-3-T3E3
SMB-2-155-EL

MPSM-16-T1E1

RBBN-16-T1E1-1N
MCC-16-E1-1N
RED-16-T1E1
MCC-16-E1
RBBN-16-T1E1

(For the 1:N redundancy of the MPSM-16-T1E1, MGX 8830/B supports the RCON-1TO3-8830 back card.)

VISM-PR

AX-SMB-8E1
AX-R-SMB-8E1
AX-RJ48-8T1/8E1
AX-R-RJ48-8T1/8E1


MGX 8850 and 8850/B (PXM 45) Series

For product details, refer to Tables 4 through 8 in the release notes at this website:

http://www.cisco.com/univercd/cc/td/doc/product/wanbu/8850px45/relnote/52008xx0.pdf

Table 18 PXM45 on MGX 8850 and 8850/B 

Front Card
Back Card

AXSM-1-2488
AXSM-1-2488/B

SMFLR/SMFSR/SMFXLR-1-2488
SMFLR/SMFSR/SMFXLR-1-2488/B

AXSM-2-622-E

SMFIR/SMFLR-1-622/C

AXSM-4-622
AXSM-4-622/B

SMFIR/SMFLR-2-622
SMFIR/SMFLR-2-622/B

AXSM-8-155-E

SMB-4-155
MMF/SMFIR/SMFLR-4-155/C

AXSM-16-155

MMF-8-155-MT
SMFIR/SMFLR-8-155-LC

AXSM-16-T3E3
AXSM-16-T3E3/B

SMB-8-T3/E3

AXSM-16-155/B

MMF-8-155-MT/B
SMFIR/SMFLR-8-155-LC/B

AXSM-16-155-XG

SFP-8-155
MMF/SMFIR/SMFLR-1-155-SFP
MCC-8-155

AXSM-32-T1E1-E

MCC-16-E1
RBBN-16-T1E1

AX-CESM

AX-SMB-8E1
AX-R-SMB-8E1
AX-RJ48-8T1/8E1
AX-R-RJ48-8T1/8E1
MGX-RJ48-8E1

AX-FRSM-8T1/8E1

AX-SMB-8T1/8E1

AX-FRSM-8E1-C

AX-R-SMB-8E1
AX-RJ48-8E1
AX-R-RJ48-8E1
MGX-RJ48-8E1

MGX-CESM

AX-RJ48-8T1
AX-R-RJ48-8T1

MGX-FRSM-2CT3

MGX-BNC-2T3

MGX-FRSM-HS2/B

SCSI2-2HSSI/B
MGX-12IN1-8S

MGX-FRSM-2T3E3

MGX-BNC-2E3
MGX-BNC-2T3

MGX-RPM-PR

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

MGX-RPM-XF

MGX-1GE/2GE
MGX-1OC12POS/2OC-12POS-IR
MGX-XF-UI/-UI/B

MGX-SRME

MGX-SMFIR-1-155
MGX-STM1-EL1

MGX-SRME/B

MGX-BNC-3T3-M
MGX-STM1-EL-1

MGX-VISM-PR

AX-SMB-8E1
AX-R-SMB-8E1
AX-RJ48-8T1/8E1
AX-R-RJ48-8E1/8T1

MGX-VXSM

VXSM-BC-4-155
VXSM-BC-24T1E1

MPSM-8-T1E1

AX-RJ-48-8T1/8E1
AX-R-RJ-48-8T1/8E1
AX-SMB-8E1
AX-R-SMB-8E1

MPSM-16-T1E1

RBBN-16-T1E1-1N
MCC-16-E1-1N
RED-16-T1E1

(For the 1:N redundancy of the MPSM-16-T1E1, MGX 8830/B supports the RCON-1TO3-8830 back card and MGX 8850/B supports the RCON-1TO3-8850 and RCON-1TO5-8850 back cards.)

PXM45/B

PXM-HD
PXM-UI-S3

PXM45/C

PXM-HD
PXM-UI-S3/B


MGX 8880 (PXM45/C) Series

For MGX 8880 product details, refer to Table 3 in the release notes at this website:

http://www.cisco.com/univercd/cc/td/doc/product/wanbu/mgx8880/relnote/528880.pdf

Table 19 MGX 8880 (PXM45/C) 

Front Card
Back Card

AXSM-1-2488/B

SMFLR/SMFSR/SMFXLR-1-2488/B

AXSM-4-622/B

SMFIR/SMFLR-2-622/B

AXSM-32-T1E1-E

MCC-16-E1
RBBN-16-T1E1

PXM45/C

PXM-HD
PXM-UI-S3/B

MGX-RPM-XF-512

MGX-1GE/2GE
MGX-1OC12POS/2OC-12POS-IR
MGX-XF-UI/-UI/B

MGX-SRME/B

MGX-BNC-3T3-M
MGX-STM1-EL-1

MGX-VISM-PR

AX-SMB-8E1
AX-R-SMB-8T1/8E1
AX-RJ48-8T1/8E1
AX-R-RJ48-8E1

MGX-VXSM-155

VXSM-BC-4-155

MGX-VXSM-T1E1

VXSM-BC-24T1E1


MGX 8950 (PXM 45) Series

For MGX 8950 product details, refer to Tables 4 through 8 in the release notes at this website:

http://www.cisco.com/univercd/cc/td/doc/product/wanbu/8850px45/relnote/52008xx0.pdf

Table 20 MGX 8950 (PXM45) 

Front Card
Back Card

AXSM-1-2488/B

SMFLR/SMFSR/SMFXLR-1-2488/B

AXSM-1-9953-XG

SMFIR/SMFLR/SMFSR-1-9953

AXSM-4-622/B

SMFIR/SMFLR-2-622/B

AXSM-4-2488-XG

SMF-4-2488-SFP
SMFSR-1-2488-SFP
SMFLR-1-2488-SFP

AXSM-16-155/B

SMFLR-2-622/B
SMFIR/SMFLR-8-155-LC/B

AXSM-16-155-XG

SFP-8-155
MMF/SMFIR/SMFLR-1-155-SFP
MCC-8-155

AXSM-16-T3E3/B

SMB-8-T3/E3

MGX-RPM-PR

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

MGX-RPM-XF

MGX-1GE/2GE
MGX-1OC12POS/2OC-12POS-IR
MGX-XF-UI/-UI/B

MGX-XM60

PXM45/B
PXM45/C

PXM-HD
PXM-UI-S3
PXM-UI-S3/B


SES PNNI Controller

For product details, refer to Tables 1-1, 1-2, and 1-3 in the release notes at this website:

http://www.cisco.com/univercd/cc/td/doc/product/wanbu/bpx8600/pnni_ses/rel4/relnotes/ses4015.pdf

Table 21 SES PNNI Controller 

Front Card
Back Card

PXM1

PXM-UI
PXM-UI-S3

PXM1-4-155

PXM-UI
PXM-UI-S3
MGX-MMF-4-155/B
MGX-SMFIR-4-155/B
MGX-SMFLR-4-155/B

PXM1-1-622

PXM-UI
PXM-UI-S3
MGX-SMFIR-1-622/B
MGX-SMFLR-1-622/B

PXM1-2-T3E3

PXM-UI
PXM-UI-S3
MGX-BNC-2E3
MGX-BNC-2E3A
MGX-BNC-2T3


Releases Certified for CWM 15.1.50, Patch 2

Table 22 lists the card, shelf, or switch software releases that were used to test the CWM 15.1.50, Patch 2 software. Although CWM 15.1.50, Patch 2 supports other releases, the releases listed in the table are the specific releases that were tested for Patch 2.

See also these sections:

Releases Supported by CWM 15.1.50, Patch 2

Supported Hardware

Table 22 Releases Tested with CWM 15.1.50, Patch 2 

Card, Shelf, or Switch
Tested Software Release

BPX/IGX switch software

9.3.47
9.4.10
9.4.12

BPX SES Shelf

3.0.25
4.0.10
4.0.15

MGX 8220 Shelf

5.0.18
5.0.19
5.0.20

MGX 8230, 8250, and 8850 (PXM1) switches

1.3.12
1.3.14

MGX 8830 and 8850 (PXM1E) switches

MGX 8850 and 8950 (PXM45) switches

5.0.20
5.1.20
5.2.00

MGX 8880 (PXM45) switch

5.0.20
5.1.20
5.2.00

RPM-PR and RPM-XF cards

Cisco IOS 12.3(11)T6
Cisco IOS 12.3(14)T4

VISM-PR cards

3.3.00
3.3.10
3.3.20
3.3.25

VXSM cards

5.0.0.1
5.1.20
5.2.00


New Features and Enhancements

This section describes new features and enhancements for these releases:

Features Introduced in CWM 15.1.50, Patch 2

Features Introduced in CWM 15.1.50, Patch 1

Features Introduced in CWM 15.1.50

Features Introduced in CWM 15.1.50, Patch 2

This section describes the new features introduced in Patch 2:

Support for Voice Interworking Service Module (VISM) 3.3.20 features

These features apply to the PXM45-based MGX 8850 and 8880 nodes and the PXM1-based MGX 8850, 8250, and 8230 nodes:

Enable SSRC per a RTP session—You can enable or disable the switch to support more than one SSRC (Synchronizationsource) per RTP session through the CWM Configuration Center. When enabled (set to true), VISM accepts more than one SSRC per RTP session.When disabled (set to false), VISM accepts one SSRC per session.

Modem Tone (1560/980 Hz) Detection—The modem tone 1560/980Hz is used in special modem calls to carry encrypted data. You can enable or disable this special modem tone detection on the card through the CWM Configuration Center.

V.110 detection on the line—The VISM signaling type must be set to ccs when enabling V.110 detection and the card mode should be either aal2 or voip trunking mode.

Alternate codec strings configuration.

MediaGateway endpoint repetition.

Support for VISM 3.3.25 features

These features apply to the PXM45-based MGX 8850 and 8880 nodes, the PXM1E-based MGX 8850 and 8830 nodes, and the PXM1-based MGX 8850, 8250, and 8230 nodes.

VISM alarm Log Enable & Admin Timer on the line—You can enable the Alarm log and configure the admin timer through the CWM Configuration Center.

FAX De-Jitter mode and Jitter initial delay—These configurable parameters for have been added to the DSP parameters.

You can enable or disable the Continuity Check Cell for all PVCs on the card through the CWM Configuration Center.

History Statistics Enhancements (OAM)—The CWM SCM and Diagnostic Center now support two new PVC OAM loopback timeout statistics and counters.

DS0 Group Repetition option

This feature enables you to perform bulk configurations to enable and disable DS1 paths through the Configuration Center. (It also resolves bug CSCej78562.). Use this procedure to create a DSX0 group:

From the Hierarchical Tree, right-click the node and choose Configuration Center.

Click the Elements tab.

Drag and drop the VXSM DS1 line into the Configuration Center.

Select the DS1 Path tab.

From the menu, choose the appropriate DSX0 group and click Create.

In the DSX0 Grp Index field, enter the DSX0 index.

From the Ds0 Channels drop-down menu, choose the DS0 channels.

From the DSX0 Service Type, choose the service type.

In the DS0 Group Repetition pane, enter the number of group repetitions.

Click Apply.

Trap Resiliency feature

With this feature, the CWM can detect network elements that are responsible for unusually high trap rates and can ignore any or all traps that are overloading the system. After the option is configured, the CWM continues to monitor the total trap rate of individual switches and automatically shuts off all trap processing for switches with an excessive total trap rate. The CWM provides historical trend analysis for the total trap rate of each node so any alarming network trends can be detected to avoid real problems.

The following description provides more detail about this feature.

To make the incoming trap rate more manageable, the CWM has added these specific "trap resiliency" capabilities that are viewed and managed in the Diagnostic Center, Statistics or Excessive Traps windows (go to Diagnostic Center > Manageability > Statistics or Excessive Traps):

Identifying and displaying traps that are exceeding a particular threshold level—These traps are automatically detected and displayed. You can also configure the condition for excessive traps with a sampling interval and trap rate threshold. The maximum, minimum, and average trap rate values (shown in throughput traps per second [tps]) are displayed for the selected network nodes during the specified time period. To view these statistics (along with FTP and SNMP statistics), launch the Diagnostic Center, choose a particular network, and view the data in the Statistics window. In the Excessive Traps window, you can change the time period with the "From Period" and "To Period" settings and click Refresh to view the statistics during this new time period.

Managing excessive trap sources—The CWM can block selected incoming traps based on the node ID from which the trap generated and the particular trap number. (At runtime, you can add or remove this filter as needed.) In the Excessive Traps window, each table entry includes a "Blocking State" check box that indicates if the source is currently blocked, and you can check or uncheck this check box to change the setting. Because excessive traps are time sensitive, only those reported within last hour are presented to users. However, trap sources that are currently blocked are displayed even though they are not recent sources of excessive traps (last 1 hour).

Protecting from the excessive traps: Auto shut-off feature—The above capabilities focus on preventing particular traps from being forwarded from the switch. The Auto shut-off feature allows the CWM to protect itself from overloading and automates protective actions. You can enable or disable this feature from the nts.conf file in the ~svplus/config directory. To enable Auto shut-off, set the HIGH_TRAP_NODE_AUTO_SHUTOFF parameter value to "1".

In addition to detecting excessive traps based on particular trap number from each node, you can define a per-node total trap rate threshold so that the total trap rate of each node can be used to trigger alerts when the rate exceeds the threshold. This trap rate is also configured from the nts.conf file. In the Excessive Traps table, you can view the nodes with a total trap rate exceeding the per-node total trap rate threshold and the nodes with trap processing currently shut off.

In the Excessive Traps window, you can also view the Blocked or UnBlocked trap states and block or unblock node trap processing. Blocking the trap processing for a node means dropping any packets from the node's management IP address after the UDP socket so that the node's traps do not overload the CWM. In addition, the CWM is deregistered from the switch Trap Manager table through SNMP so that the switch does not send traps to the CWM (see the next listed item). The blocking or unblocking of node trap processing does not affect any filtering on particular node trap numbers. Node trap number filtering affects trap forwarding to CWM subsystems, whereas node blocking means shutting off trap processing altogether for the node. When the node is no longer blocked and trap processing resumes, any filtering on the pertinent node trap numbers applies again.

Note that when Auto shut-off is enabled, it goes into effect as soon as the threshold is crossed. At that time, the CWM stops processing traps from that node that are already in the system internal buffers, drop all future traps from it after the UDP socket, and deregisters the CWM from its Trap Manager table.

Deregistering the CWM from the Trap Manager table in the Diagnostic Center—Follow these steps to deregister this CWM machine from the switch Trap Manager table. You can launch the Diagnostic Center for any node. From the Manageability tab, choose Excessive Traps. In the Node Login Information area, enter the Node ID and password and then click Deregister Traps.

Features Introduced in CWM 15.1.50, Patch 1

This section describes the new features introduced in CWM 15.1.50, Patch 1:

Support for these cards:

AXSM-8-622-XG card on MGX 8850, 8850/B, 8950 and 8830/B with PXM45/C.

MGX-RPM-1FE-CP back card for RPM-PR on MGX 8850, 8850/B, 8830, and 8830/B with PXM1E.

Compatibility with MGX-VISM-PR-8T1 and MGX-VISM-PR-8E1 using VISM 3.3.20.

Mobile PNNI node and trunk support. (Mobile trunks are always between mobile and fixed PNNI nodes.) This feature provides for configuring mobile interfaces through the Configuration Center. It displays mobile PNNI switches as purple icons in the physical view of the Network Monitor. Mobile trunks are displayed as dotted and dashed lines.

Suppression of ATM network alarms for a set duration (VXSM AIS suppression feature). This feature provides configuration for AIS suppression and delay time through the Configuration Center and for the AIS suppression count through the Diagnostic Center.

Additional MasterAgent log details on queue-related errors.

Finder application enhancements. This feature provides for viewing multiple Finder windows at the same time. The Windows menu has two options: Cascade (windows displayed side-by-side) or Tile (windows displayed behind one another).

Improved Service Class Template database failure recovery.

Features Introduced in CWM 15.1.50

This section describes the new features introduced in CWM 15.1.50:

Provides sync-up operation for large networks (up to 3-million connections).

Current Routes feature on MGX 8950, 8850, and 8830, Rel. 5.1. This feature provides the current path on which an active master connection is currently routed on in a PNNI network, current route statistical information, such as number of connections in the file that have current route information, and congestion management at the master and slave node to avoid possible congestion associated with this feature.

1:N cold redundancy support for MPSM 16T1E1 cards, which provides the capability for configuration (add and delete) and management of 1:N cold redundancy, graceful and nongraceful switchovers, and upgrading 1:N redundant cards.

To enable MPSM 16T1E1 support, CWM GUIs, such as the Configuration and Diagnostic centers and ChassisView, have been updated with configuration parameters for card, line, connection management, and diagnostic capabilities. This feature supports MLPPP and MPPPMux and these services: NxT1, NxE1 IMA v1.0 v1.1, T1/E1 ATM services, and NxDS1/T1/E1 frame services.

SNMP connection transaction log enhancement to provide measurement of module and system performance, which enables a user to generate performance reports on flow-through connection provisioning.

Support of UltraSPARCIIIi system environment.

Upgrade paths from CWM releases 12 and 15.

New Automated Bulk Provisioning (ABP) module (sold separately). This time-based provisioning system enables users to schedule connection and port provisioning jobs. It is a standalone software that works on top of the CWM. For additional information, refer to the CWM Automated Bulk Provisioning Guide at this website:

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

Updated Cisco WAN Modeling Tools, Rel. 15.1.50 (sold separately).

Support for assigning user profiles permission to change the node name (Node Rename feature).

The maximum Informix raw partition size limitation has increased from 2 GB to 4 TB when the CWM is installed in its entirety on a Solaris 8 or 9 system or when the operating system is upgraded to Solaris 9 and the CWM is also upgraded.

For MGX 8850 and MGX 8830, Rel. 5 (PXM45-based nodes and PXM1E-based nodes), CWM 15.1.50 adds support for the MPSM-T3E3-155 MultiLink Frame Relay (MFR) feature on switches running Rel. 5.0.20 or 5.1.00 software.

For MGX 8880, 8850, and 8830 Rel. 5 nodes (both PXM1E-based and PXM45-based nodes), CWM 15.1.50 adds support for VISM 3.3 and for collecting bulk statistics from the VISM-PR.

For MGX 8850, 8250, and 8230 Rel. 1.3.12 (PXM1-based nodes), support has been added so MGX 8850, 8250, and 8230 (PXM1-based nodes) running Rel.1.3.12 now support both VISM and VISM-PR running VISM 3.3.

CWM Feature Limitations

This section describes features that the CWM does not support or features for which CWM limitations exist. See these sections:

Features Not Supported

Feature Limitations

Configuration Center Limitations

HP OpenView Limitations

SSM Issues

CWM-to-CWM Communication Limitations

Network Monitor Limitations

CWM Notes and Cautions

Features Not Supported

These features are not supported by CWM 15.1.50 and later patches:

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

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

The CWM does not support use of the Korn shell.

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

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

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

These VISM 3.1 features introduced cannot be accessed from the CWM: TGCP, Dynamic Payload, and T.38 Fax Relay.

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

These cards are not supported by CWM 15.1.50 and later patches: the BME card, the FRSM12 service module, and the URM, ARM, FRM, BTM, ALM and CVM service modules. To take advantage of the new CWM 15.1.50 GUI enhancements, you must upgrade to the newer supported service modules; otherwise, you would stay with CWM 12.

These are the Current Route feature limitations:

P2MP calls and SVC/SVP connections are not supported.

Only master-ended (not slave-ended) connections have current route information.

The configuration upload file contains only a snapshot of the current route information at the time the switch receives a CWM configuration upload request.

If a node becomes congested, both of the connTrace messages that the CLI and the Current Route feature send are dropped. The CWM does not distinguish between the messages. This situation is also true for a connTrace ACK message received on a congested node.

When a node ID is changed, follow this procedure on each network node to flush out all existing current route information and start collecting new information. Disable and re-enable the current route feature by using the new cnfndcurrte CLI command. After disabling the feature, wait for at least 9 seconds (the timeout period for a conntrace message) before re-enabling the feature to avoid processing stale conn-trace messages.

Because the path information for a connection traversing more than 20 nodes is not stored in the current route path table, the connection does not have current route information.

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

Feature Limitations

The following are known CWM feature limitations:

Because of a VISM image issue, the CWM cannot update fax_jitt_mode and fax_jitt_initdelay in the vism_card table for a Fax jitter configuration change. This problem will be fixed in the next VISM release.

Even though the VXSM T3 card is compatible with the MGX 8880 and 8850 PXM45 platform releases, the CWM 15.1.50 software does not discover it.

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

When /usr/users becomes completely full, the orbix processes cannot write to the disk and continue operations. To correct the problem, free up disk space in /usr/users and then restart the orbix processes and the CWM as follows: Stop the core and exit out of the CWM prompt, run the stoporbix2000 script, type CWM (you should see "Starting Orbix..." in the ~svplus/log/.startStopOrbix.log file), and start the core.

When SSM 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.

When a shortage of shared memory exists on the workstation, the Informix engine may generate an operating system error, as shown in this example:

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

When this error occurs, the statsparser is not able to perform 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.

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

If an ATM IP interface (also called In-band interface) is being used to manage the switch from the CWM, the CWM cannot receive all node bring-up traps. The ATM connections required for in-band management can take time to get routed on node bring-up and therefore are not available for trap delivery at the initialization time. If this initialization time is an issue, the workaround is to configure the CWM for out-of-band management.

Allow a 2- to 3-minute period between enabling or disabling statistics operations on the same BPX or IGX node. Whenever statistics are enabled or disabled on a BPX or IGX node and the switch is configuring statistics, enabling or disabling statistics a second time fails.

If the Start Collection process on the SCM GUI is taking a long time, investigate whether or not collection was started with an unreachable in-band or out-of-band IP address. Use a reachable IP address to start collection with a reachable IP address, either in band or out of band.

The SSM statistics database can go out of sync with node_ids on the CWM after a coldstart -F is executed on the server. To ensure that the node IDs remain consistent, stop and disable collection before doing a coldstart -F. A CWM-to-CWM gateway must be enabled to ensure uninterrupted statistics collection.

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.

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

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

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

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

When a back card is removed because the front card is not provisioned, the CWM reports a major alarm with the description "Back Card; not present." However, the switch may not show an alarm. If the card is actually not provisioned, manually clear the major alarm after determining the alarm condition is not real.

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.

RPM-PR and RPM 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.

Note the following in regard to receiving SNMP traps:

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, such as FFFFFFFFF10701555, you do not receive trap 25302 and 25303, even though you have registered for that group.

If you deselect a currently undefined group such as Group 28, that is a bit mask of FFFFFFFFEFFFFFFF, you can then add traps 25302 and 25303 by editing the trap_filter.conf file and adding these lines to Group 20 # Network Connectivity Status Change Traps: TRAP 25302 and TRAP 25303.

Changing the line, payload, and medium types of VXSM-4OC3 causes the CWM to perform a whole card resync when you change any of the following: the medium type between SONET and SDH for SONET physical line, the payload type between T1 (VT 1.5 VC 11) and E1(VT 2 VC 12) for the STS or STM (Au) path or between T1 (VT 1.5 VC 11) and DS3 for the STS path, or the tributary path between Au4 and Au3 for the STM path in the SDH medium. (A whole card resync takes several minutes to complete.)

If you remove and then immediately add back the same IGX feeder when the CWM is running, the CWM establishes two LINK 0's with the node. This is treated as a delete, and the node is deleted. In this situation, Cisco recommends you either remove and add the feeder when the CWM is down, or, after adding the feeder, restart the CWM.

Changes made to the node name through the Configuration Center are updated automatically in the Tree and Inspector views. However, the node name in the title bar of the internal frame does not update automatically. To make this change, close and reopen the internal frame. You can also update the attribute values in the internal frame by using the Refresh button of that internal frame.

After the Line Send parameter LineSendCode is modified by using snmpset, the database is not updating it, which shows the parameter as inapplicable (shows the value as -1). For additional information, refer to CSCin50480 online.

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.

Note the following in regard to the managing a PXM45-based MGX node and populating the "peripheral" table: If you are running a release earlier than 4.0.10, CWM 15.0.00 does not populate (update) the peripheral table. If you are running a 4.0.10 or later release, the status field in the peripheral table gets updated only during node resync. (If you are managing a PXM1-based MGX node, the peripheral table status field does not get updated.)

If the log level for the CWM EM module is set too high or set above the production default value and many configurations are changed on the switch during a warm start, the sync-up performance is impacted during the warm start.

SmartLogging is a special feature for CWM debugging available when the log level is set to Level 2. It dumps 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 that triggers a Level 2 log message dumps log messages at all levels immediately before and after this event. Because the feature can impact performance due to excessive log messages. it should be disabled in normal operation and enabled only when needed for monitoring performance.

In regard to the The Forced Deletion feature, note that it does not support XPVC connections. They cannot be force deleted. The feature removes only the unused connection descriptor from the workstation on which it is performed. Other gateway workstations continue to show the descriptor. To clear it completely, you must force delete the unused descriptor at each gateway workstation.

Occasionally, when you move linked nodes around in the Topology screen, the link does not automatically follow the nodes. Then it looks like the link is not connected to the nodes. Either move the affected nodes around within the window or refresh the Topology screen. When the screen refreshes, the link automatically appears connected to the appropriate nodes again.

Using the Group Nodes feature affects only your view of the networks. Other users, even those who log into your workstation, do not see the groups you have made.

After a previously saved configuration file is loaded by using the CWM Config Save & Restore feature, 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. In this case, perform a manual node resync.

When setting up VISM connections, the VPI value in the VPI/VCI Selector window is grayed out with the VISM card slot number. If VISM is sitting in a feeder node, the VPI value in the VPI/VCI selector is grayed out as zero.

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.

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

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

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.

The Loss of Cell Delineation alarm on the AXSME, AXSM-XG, or MPSM-OC3 cards may not get propagated from the switch to the CWM. For the AXSM cards, a line or path alarm is present, but the MPSM-OC-3 card could have an LOCD alarm triggered without any line or path alarm that is present. The line would show in the CWM as clear, while it is actually in alarm.

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

Occasionally, WANDEST fails to install immediately after a CWM 15.1.50 and Service Agent installation on a workstation running Solaris 9. This error message appears: "Informix is not in on-line mode." The workaround is to install WANDEST by using the C shell (csh).

In the Connection Manager, the Service Type field displays some nonapplicable service types for SPVCs; however, the CWM displays an error if you select one of these nonapplicable service types.

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.

If a valid network.conf file is not present, the CWM may not start properly and may cause a topod core dump.

Because of a device limitation, an SCT greater than 255 cannot be associated with SCT manager.

An SSC can be added to only one SSM or CWM at a time.

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), the CWM treats these connections as three segment connections and adds 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 want 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 is provisioned by using telnet because 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 deleting SPVC connections on a PXM1E-based node this error message appears: "can not delete connections. Failed to communicate with databroker." The 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 15.1.50. Use the Network Monitor map instead.

SSM Issues

Note these SSM issues:

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 enables connections statistics only on SCM but does not set the stats-enabled flag to true on the connection, the statistics are not collected for that connection. Because no mechanism or warning to the user exists to have this enabled on the connections, the CWM does 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. No such limitation exists 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.

The CWM does not support statistical alarms for lines on PXM45-based MGX nodes.

The following statistics for SRM and SRM/E T3 lines can be enabled on the switch, but are not supported by SCM: 28 dsx3LCVCurrent, 29 dsx3LESCurrent, 30 dsx3LSESCurrent, 31 dsx3PCVCurrent, 32 dsx3PESCurrent, 33 dsx3PSESCurrent, and 34 dsx3CCVCurrent.

HP OpenView is supported on SSM. SSM processes generate CWM traps.

At least one CWM must be 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 an 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.

Inan 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 the SCM GUI on SSM.

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

Statistics data is stored on in statsdb database.

Statistics parsing is only supported for the statsdb database on the SSM machine and the CWM machine. Statistics parsing is not supported for the stratacom database on the SSM and CWM machine.

Stop statistics collection before upgrading a node image.

CWM-to-CWM Communication Limitations

This section describes CWM-to-CWM communication limitations:

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 CWMs managing the same network must have seed nodes or gateway nodes that have IP addresses within the same network. All of the CWMs should not all point to the same gateway node, but the gateway nodes that they point to should be in 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 is not discovered.

The Configurator can be started on either the primary CWM or the secondary CWMs, but any Add, Modify, or Delete operations can be performed with the Configurator only on the primary CWM.

All of the above CWM-to-CWM communication limitations listed also apply to the 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 by using the primary IP address. The primary IP address is specified by using Option 7 or 8 (depending on chassis type) in the cnfndparms CLI command. Configure the trap IP with the primary IP address. PXM1-based MGX nodes connected to PXM45-based MGX nodes are managed through the atm0 IP. If atm0 is not set, the LAN IP address is used to manage the PXM1-based MGX nodes. Use the cnftrapip command to configure the trap IP accordingly.

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

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

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

In releases earlier than CWM 15.0.00, a flag named TOPO_SHOW_MAP in the /usr/users/svplus/config/CwmGs.conf file was used to configure whether or not nodes and trunks are displayed in the topology display of the Network Monitor application at CWM startup. The TOPO_SHOW_MAP flag is now obsolete. Use the SHOW_TOPO_VIEW flag in the CMSCClient.conf file instead.

CWM 15.1.50 adds these new flags in the CMSCClient.conf file:

SHOW_ROUTING_TRUNK_TREEVIEW True means that the TreeView displays the routing trunk folder in all applications. The routing trunk folder contains all of the routing trunk information. The default is true. If you set the SHOW_ROUTING_TRUNK_TREEVIEW parameter to false, the routing trunk information is not retrieved from the inventory server and the TreeView in all applications does not show the routing trunk folder.

SHOW_SORTED_TREEVIEW True means that the TreeView in all applications shows sorted tree node names. The default is true. If you set the SHOW_SORTED_TREEVIEW parameter to false, the tree node names are 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. 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 is disabled.

CWM Notes and Cautions

Because of the asynchronous behavior of the ILOG client and server interaction, CWM client requests may be sent before the CWM server is ready. In this case, this error message appears:

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

Note If the ILOG timeout situation persists for more than 5 minutes and the CWM is not functioning normally, you should call service.


Parameters that the Network Monitor or Configuration Center displays that do not apply to an element, such as a line or a trunk, often contain the value -1. Consider this the same as Not Applicable.

Installing and Uninstalling CWM 15.1.50, Patch 2

This section describes how to install or upgrade CWM 15.1.50, Patch 2. It also provides important background information about installing or upgrading the CWM server. To install or upgrade the server, refer to the CWM 15.1.50 installation guide at this URL:

http://www.cisco.com/application/pdf/en/us/guest/products/ps6451/c2001/ccmigration_09186a00804c3167.pdf

The installation procedure assumes that you have already installed CWM 15.1.50.

You can upgrade to CWM 15.1.50 from CWM 15.0.00, Patch 4, or CWM 12.0.00, Patch 3. To upgrade from an earlier release, refer to the above-referenced CWM 15.1.50 installation guide and the CWM 15.0 release notes at this URL:

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

See these sections:

Before You Start

Installing Patch 2

Uninstalling Patch 2

Before You Start

This section provides important background information that is provided to help you install the patch successfully.

Naming Managed Nodes

The name of each node that the CWM manages 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.

Core File Management

In the past, core files were created without unique names and then overwritten. Now, for each core dump, a unique directory is created under ~svplus/corefilesdir/ and named as follows: <Core.<processName>.<pid>.mmddHrMinSec. The directories have these contents:

Core file named <processName>.<pid>.mmddHrMinSec.core

Information file with dmesg, onstat -d, pstack, and other details named "<processName>.<pid>.mmddHrMinSec.info"

Corresponding log file(s) named "<processName>.<pid>.log"

Cisco Info Center Version

The CWM integrates with the Cisco Info Center (CIC) by including a tar file that can be installed using the CIC update utility (nco_update):

CIC3.6x-IIU001-CWM15.1.tar

The format of this tar file enables the update utility on the CWMAgent CD-ROM to process the file.

The CWM 15.1.50_SNMPAgent.tar.gz file that contains this CIC tar file includes rule files that are compatible only with CIC 3.6.1 so you must install CIC 3.6.1 to use this file.

If you want to continue using CIC 3.6.0 or 3.5 with CWM 15.1.50, save and then apply the CIC36Pipp000CWM15 tar file that is available in the CWM 15.1.50 SNMP Agent CD.

For more information on CIC, refer to this URL:

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

C-Note/CWM Configuration

CWM 15.1.50 supports C-Note version 3. Before the Orbix cmldomain services for C-Note are started, the CWM core must be started and core processes should be running. Add the IP address of the C-Note workstation to the /opt/ssng/config/CMLLogin/SnmpPublisher.xml file by entering this command:

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

The line you add should look like this, substituting your actual C-Note workstation IP address for one in the example below:

<ipAddress>172.28.140.218</ipAddress>

Numbering for Release 9.4 IGX Feeder Nodes

When an IGX is added as a feeder to a SES/BPX or MGX node, it has a default node number that may not be unique within the network. If it is not unique, it needs to be modified to a unique node number by issuing the rnmnd <x> CLI command, where x is unique with regard to all other auto-route nodes.

To find the other node numbers, use the dspnds +n CLI command. If you fail to do this, 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 and user profiles are stored in the database as user_info and sec_profile tables. All CWM systems in the same domain have the same data in the user_info and sec_profile tables through CWM-to-CWM communication. The user_info and sec_profile tables do not get dropped when the coldstart command is executed during a coldstart. They 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, the user gets authenticated against UNIX. The user's password must match the one defined in the UNIX system.

Beginning with the CWM 15.0.00, Patch 2, permission settings for adding, deleting, or modifying network partitions or subnetworks can be configured by using the Security Manager GUI.

CWM Database

After creating a new database by executing the coldstart script, a database inconsistency will result if the CWM is restarted (stop core and start core) before it is synchronized with the network. In this case, rerun the coldstart script to avoid database inconsistencies. Do not use the SV+CreateDb tool for this purpose.

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

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

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

RPM Management Limitations

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

For both RPM and RPM-PR cards managed by ChassisView in CWM 15.1.50 that are in standby 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. To enable the feature and obtain RPM back card information, edit the emd.conf file before starting the CWM core. Note that when back card support is enabled, back card information is polled from the switch only during a coldstart or a manual resync. After that, any back card configuration or status changes are not updated until you perform another coldstart or a manual resync.

The CWM does not distinguish between the Ethernet back card versions installed with the MGX-RPM-128M/B or RPM-PR. No difference in functionality exists.

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 allowed only 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 back card appears as blank, not with grayed-out ports as in previous releases that used CiscoView for equipment management.

Equipment Management Configuration Notes

In the emd.conf file, the OORequest and OOStart parameters should be customized, depending on network. The OORequest parameter defines the number of configuration files per node that can be requested at one time, with a maximum of 32 configuration files concurrently per node. The range is 1 through 32, and the default is 32. The OOStart parameter defines the number of OOEMC child processes. The range is 1 through 25, and the default is 6.

All of the PNNI nodes that the CWM manages (PXM45-based 8950, 8880, and 8850 nodes; PXM1E- based 8950, 8850, and 8830 nodes; and BPX nodes with SES shelves) are distributed among OOEMC processes.

The number of nodes that a single process manages is computed by dividing the number of PNNI network nodes by the number of processes that OOStart defines. Assume that the number of nodes that one process manages is called MANAGED_NODE_COUNT. Then, MANAGED_NODE_COUNT * OORequest must be less than or equal to 200, which can be achieved by increasing the OOStart or reducing the OORequest. The normal range of OOStart is 5 to 20. If the OOStart value is increased beyond 10, the number of DMD processes has to be increased or the shared memory overflows.

Network Monitor Server Configuration File (NMServer.conf)

Two parameters in the NMServer.conf configuration file—HELLO_EVENT_INTERVAL and EVENT_REDELIVERY_COUNT—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 number as the HELLO_EVENT_INTERVAL value times the EVENT_REDELIVERY_COUNT value. The range for HELLO_EVENT_INTERVAL is 0 through 600, and the default is 60. The range for EVENT_REDELIVERY_COUNT is 0 through 10, and 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.

Installing Patch 2

This section describes how to install the CWM 15.1.50, Patch 2. Refer to these sections:

Backing Up the Existing Database

Installing the CWM Server Patch

Verifying and Restoring Your Saved Database

Installing the SNMP Agent (Service Agent) Patch

Installing the SSC Patch

Installing the SSM Patch

Installing the RTM Proxy Patch

Table 23 lists the contents of the Patch 2.

Table 23 CWM 15.1.50, Patch 2 Contents

Component
File

CWM Server

15.1.50-P2_CWM.tar.gz

SNMP Agent

15.1.50-P2_SNMPAgent.tar.gz

SSC (Standalone Statistics Collector)

15.1.50-P2_SSC.tar.gz

SSM (Standalone Statistics Manager)

15.1.50-P2_SSM.tar.gz

WANDEST Server 2.6.50, Patch 2

wandest2.6.50-P2_wdserver.tar.gz

WANDEST Client 2.6.50, Patch 2

wandest2.6.50-P2_wdclient.tar.gz

RTMProxy

Note Install this on the CWM Server only if you are using SSM, but not using the SNMPAgent. See Installing the RTM Proxy Patch.

15.1.50-P2_RTMProxy.tar.gz


Backing Up the Existing Database

Use this procedure to back up the existing database to preparation for installing the patch. You should back up the database in case a problem exists with Informix.


Step 1 Find a location with enough space and 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> 

For example,

# mkdir /usr/users/svplus/DBExports151

where <dbexport-location> is DBExports151.

Step 2 Use these steps to export the databases:

a. Log in as svplus:

hostname# su -u svplus

The system prompts you for the svplus password.

b. Stop the core.

c. Perform a coldstart (drops all network data so you will export only 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, 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

Use this procedure to install the CWM Server Patch.


Step 1 Stop stats collection and disable stats on the 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 the CWM server to a temporary location; for example, /tmp:

# cp 15.1.50-P2_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.1.50-P2_CWM.tar.gz 

Step 8 Extract the tar file:

tar -xvfp 15.1.50-P2_CWM.tar

Step 9 Enter this command to execute the InstallCWM151Patch2.csh script and begin the install process:

./InstallCWM151Patch2.csh

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


This message appears.

CWMGateway.conf file is backed up as CWMGateway.conf_15.1.50, 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, this 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 To continue the installation using the InstallShield GUI, respond with No.
To continue the installation using Console Mode Install, respond with Yes.

(Console Mode Install is a command line script procedure that is a GUI alternative. It is intended for users who do not have access to an X window device. By using the Console Mode Install, the user can install the CWM with an alphanumeric terminal or a PC in terminal emulator mode.)

Step 11 When prompted, follow the instructions provided by the application. When you finish installing the CWM server software, you can install WANDEST Server 2.6.50, Patch 2.

Step 12 If WANDEST Server Rel. 2.6.50 is installed on this machine, following these steps:

a. Stop the wdclient and exit root.

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

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

d. Change to that local directory and uncompress the gzip file, for example:

# gunzip wandest2.6.50-P2_wdserver.tar.gz

e. Untar the tar file, for example:

# tar -xvfp wandest2.6.50-P2_wdserver.tar

f. Switch to root.

g. Run the installation script to install the patch, for example:

# ./InstallWD26Patch2.csh

Step 13 Exit from root.


Verifying and Restoring Your Saved Database

If Informix did not come online after restarting the CWM, use the following procedure to restore the database you saved before you installed Patch 2.

(The output of onstat -d is in /usr/users/svplus/<dbexport-location>/onstat.out for reference. For example, /usr/users/svplus/DBExports151/ where <dbexport-location> is DBExports151.)


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 Follow these 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 this line:

PHYSDBS  phydbs

to this:

PHYSDBS  rootdbs

c. Change this line:

PHYSFILE  <size>

to this:

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 these commands in the order shown below:

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

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

./AddPhyLog
./RestartInf

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

./dbaddchunk

Step 8 Exit from root.

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

onstat -d

Step 10 If a separate partition exists, execute these commands to import the database. If no separate partition exists for datadbs, go to Step 11:

dbimport stratacom -d datadbs -i <dbexport-location> 
dbimport statsdb -d datadbs -i <dbexport-location>
dbimport scmdb -d datadbs -i <dbexport-location>

Step 11 If no separate partition exists for datadbs, do these:

# dbimport stratacom -i <dbexport-location>
# dbimport statsdb -i <dbexport-location>
# dbimport scmdb -i <dbexport-location>

Step 12 If you had WANDEST server before, execute this command:

# dbimport wandest -i <dbexport-location>

Installing the SNMP Agent (Service Agent) Patch

Use this procedure to install 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.1.50-P2_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.1.50-P2_SNMPAgent.tar.gz 

Step 7 Extract the tar file:

# tar -xvfp 15.1.50-P2_SNMPAgent.tar

Step 8 Execute the installation patch script:

# ./InstallAgent151Patch2.csh 

This 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 To continue the installation using the InstallShield GUI, respond No.
To continue the installation using Console Mode Install, respond Yes.

(Console Mode Install is a command line script procedure that is a GUI alternative. It is intended for users who do not have access to an X window device. By using the Console Mode Install, the user can install the CWM with an alphanumeric terminal or a PC in terminal emulator mode.)

Step 10 When prompted, follow the instructions that the application provides.

Step 11 When you have finished installing the SNMP Agent Patch software, exit from root.


Installing the SSC Patch

Use this procedure to install the SSC Patch only if you are using the SSC machine. The patch must be installed on an SSC machine.


Step 1 Log in to the SSC machine as user root:

# su

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

# cp 15.1.50-P2_SSC.tar.gz /tmp

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

# cd /tmp

Step 4 Remove the disk1 directory if it exists:

# rm -rf disk1

Step 5 Decompress the compressed tar files:

# gunzip 15.1.50-P2_SSC.tar.gz 

Step 6 Extract the tar file:

# tar -xvfp 15.1.50-P2_SSC.tar

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

# ./InstallSSC151Patch2.csh

This 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 To continue the installation using the InstallShield GUI, respond with No.
To continue the installation using Console Mode Install, respond with Yes.

(Console Mode Install is a command line script procedure that is a GUI alternative. It is intended for users who do not have access to an X window device. By using the Console Mode Install, the user can install the CWM with an alphanumeric terminal or a PC in terminal emulator mode.)

Step 9 When prompted, follow the instructions that the application provides.

Step 10 When you have finished installing the SSC Patch software, exit from root.


Installing the SSM Patch

Use this procedure to install the SSM Patch only if you are using the SSM machine. The patch must be installed on a SSM machine.


Step 1 Stop stats collection and disable stats on VXSM.

Step 2 Log in to the SSM machine as user root:

su

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

# cp 15.1.50-P2_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.1.50-P2_SSM.tar.gz

Step 7 Extract the tar file:

# tar -xvfp 15.1.50-P2_SSM.tar

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

# ./InstallSSM151Patch2.csh

Step 9 Exit from root.


Installing the RTM Proxy Patch

Use this procedure to install the RTM Proxy Patch on the CWM machine. Install the patch only on a CWM machine and only on a CWM machine that has no installed SNMP agent and that SSM has used for statistics management.

The purpose of the RTM Proxy Patch tar file is to work only with the SSM. It is not required for configuring a northbound interface. If the service agent is installed, do not install the RTM proxy patch. It is not needed.


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.1.50-P2_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.1.50-P2_RTMProxy.tar.gz

Step 7 Extract the tar file:

# tar -xvfp 15.1.50-P2_RTMProxy.tar

Step 8 Execute the InstallRTM151Patch2.csh script:

# ./InstallRTM151Patch2.csh

This 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 To continue the installation using the InstallShield GUI, respond with No.
To continue the installation using Console Mode Install, respond with Yes.

(Console Mode Install is a command line script procedure that is a GUI alternative. It is intended for users who do not have access to an X window device. By using the Console Mode Install, the user can install the CWM with an alphanumeric terminal or a PC in terminal emulator mode.)

Step 10 When prompted, follow the application instructions.

Step 11 When you have finished installing the RTM Proxy Patch software, exit from root.


Creating a CWM Auto-Restart Shell Script

This section describes how to create and configure 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.

Use this procedure to create a script that uses the vi editor and shell commands to automatically restart the CWM core after the workstation has been rebooted.


Note Several minor errors that existed in the past in the CWM Auto restart shell script have been corrected in the script that follows.



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 this command:

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

Step 4 Create the shell script by entering these lines:

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

#!/bin/sh
# Check if Informix configuration is going on 
  while [ ! -z "`ps -ef | grep S98init_db | grep -v grep`" ]
  do
    echo "Informix initialization in progress...." >> 
/usr/users/svplus/log/.start_stopCWM.log
    sleep 5
  done
# Start Orbix E2A ... as svplus 
  echo "Starting Orbix E2A ..." >> /usr/users/svplus/log/.start_stopCWM.log
  su - svplus -c /usr/users/svplus/scripts/startorbix2000 >> 
/usr/users/svplus/log/.start_stopCWM.log
  sleep 5
# Running Guard process ... as svplus
  echo "Running Guard process" >> /usr/users/svplus/log/.start_stopCWM.log 
  su - svplus -c /usr/users/svplus/scripts/Install/RunGuard &
# Start CWM core process ... as svplus 
  su - svplus -c /usr/users/svplus/scripts/start_SV+ &

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

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


Step 5 Provide execute permissions for /etc/rc3.d/S99init_sv by executing this command:

# chmod 755 S99init_sv 

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


Installing WANDEST 2.6.50, Patch 2

If you have standalone WANDEST Server and Client workstations, use this procedure to install the patches to your standalone workstations. See these sections:

Installing the WANDEST Server Patch

Installing the WANDEST Client Patch

Table 23 lists the contents of WANDEST 2.6.50, Patch 2.

Table 24 WANDEST 2.6.50, Patch 2 Contents

Component
File

WANDEST Server

wandest2.6.50-P2_wdserver.tar.gz

WANDEST Client

wandest2.6.50-P2_wdclient.tar.gz


Installing the WANDEST Server Patch

Use this procedure to install the WANDEST Server patch.

Confirm that the WANDEST Client has been stopped before installing 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.6.50-P2.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.6.50-P2_wdserver.tar.gz 

Step 9 Extract the tar file:

# tar -xvfp wandest2.6.50-P2_wdserver.tar

Step 10 Run the installation script to install the patch:

# ./InstallWDS26Patch2.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

Use this procedure to install 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.6.50-P2_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 this command:

# gunzip wandest2.6.50-P2_wdclient.tar.gz 

Step 6 Untar the tar file:

# tar -xvfp wandest2.6.50-P2_wdclient.tar

Step 7 Run the installation script to install the patch:

# ./InstallWDC26Patch2.csh

Step 8 Exit from root.


Uninstalling Patch 2

The patch installation process installs an uninstall script in the /usr/users/svplus directory for the CWM and in the /usr/users/wandest directory for WANDEST.

When you access the uninstall wizard, you are asked for the backup file location that you provided when you installed the CWM or WANDEST initially.

SNMP Service Agent Trap Limitation

This section describes the SNMP Service Agent trap limitation with the PXM1-based MGX nodes. The type of traps that the CWM collects from adding and modifying connections on Cisco MGX PXM1-based nodes running release 1.3.00 and onward can be configured by using the cnfchantrapenbl and dspchantrapenbl CLI commands:

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 command is set to Default, you can use the cnfchantrapenbl Enable command to change to collecting only trap 50601 when CWM 15.1.50 is running.

However, if you are currently collecting only 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 command, all CWM workstations monitoring the node must be shut down (the core must 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 issues in the CWM 15.1.50 and WANDEST 2.6.50 software:

Known issues in the CWM 15.1.50, Patch 2—Table 25

Issues resolved in the CWM 15.1.50, Patch 2—Table 26

Issues resolved in the CWM 15.1.50, Patch 1—Table 27

Issues resolved in WANDEST 2.6.50, Patch 1—Table 28

Issues resolved in CWM 15.1.50—Table 29

Table 25 Known Issues in CWM 15.1.50, Patch 2 

Bug ID
Description
Details and Workaround

CSCei13908

The LED alarm colors shown on the PXM cards do not match actual LED colors on the switch.

The LED alarm colors shown in ChassisView do not always match what is shown on the actual switch for the Rev1 and Rev2 PXM cards.

No workaround exists.

CSCei36492

The DC GUI does not show the correct set of applicable connection diagnostic features.

No workaround exists.

CSCei53748

The Network Monitor fails to do conn trace animation initiated from the Diagnostic Center. An exception is returned.

The issue occurs when three segment FR connections are routed through the PNNI network.

In addition, the CM server always treats the master end of a connection as local and the slave end as the remote. The DC, in contrast, can show the master and slave ends of the connection flipped because two ways of sorting connections exist in the list for a specified endpoint element. That creates confusion for both the DC GUI and the user.

The workaround is as follows. When getting a list of connections in DC, check the flag "Show Master as Local End." In this case, the trace connection result table comes up correctly, and the Network Monitor correctly animates the route.

CSCej33762

With Stats enabled, the collection information is not getting passed to all the CWM servers that are in the gateway setup during startup and runtime.

No workaround exists.

CSCej46494

If svConnServRateOvrRide is enabled, ConnProxy should not copy frEndPointChanServRate to frEndPointPIR and frEndPointMIR on the MPSM-T3E3-155 card.

On the MPSM-T3E3-155 card, the frEndPointChanServRate MIB object is not supported. So, although the current proxy behavior for all FR cards is to copy frEndPointChanServRate to frEndPointPIR and frEndPointMIR when svConnServRateOvrRide is enabled, this feature is not supported on this card.

It causes a failure to set the user-defined PCR and SCR for the MPSM-T3E3-155 FR card.

CSCej49323

Issues are arising when modifying the ingrUpcFGCRAEnable MIB object for the AUSM cards in the MGX1 chassis.

No workaround exists.

CSCej50845

The unreachability of a node is no longer indicated by updating the "alarm_state" of the node to level 3.

The unreachability is now indicated by changing the management state to level 2. This change is made by setting the "mgmt_state" field in the node table to level 2.

The inspector view in the GUI shows the node as "Unmanaged." The "alarm_state" and the "active" fields in the node table remain unchanged.

No workaround exists.

CSCej82725

The DC server crashes when trying to get a BERT configuration on the MGX1 NB card and an SNMP timeout or other exception conditions supersede the request.

The CWM 15.0.00, Patch 4.1 DC server crashed on the primary server and created a core dump. A request was made to get the BERT configuration on the device. (This happens when you drag and drop a DS1 line under FRSM card. There is no response from the switch to this SNMP request.)

No workaround exists.

CSCek23413

The SNMPSet for the AXSME card fails for the cwmRsrcPartILMIEnable MIB object.

Since the upgrade to Patch 5F, ports cannot be added on AXSME cards. An error message is generated.

No workaround exists.

CSCek24789

A frame relay port alarm severity mismatch exists between the node and the CWM. The CWM NMServer is showing the wrong severity for the Signal Failed port alarm.

When the port alarm should be a Major level severity on the switch, the NMServer GUI is showing the alarm as Critical.

No workaround exists.

CSCek24793

The Tree View color for the self-alarm on a node is incorrect. The self-alarm severity on node is different from the self-alarm severity that CWM shows for the node in the Tree View.

When an alarm on any entity below a node is propagated up, the node alarm severity is also affected, in addition to the aggregate node alarm severity. The self-alarm node severity should not be affected.

No workaround exists.

CSCin84452

In larger network environments and only during snmpwalk (not used in production environments), the svVismTable dumps CardProxy core.

No workaround exists.


Table 26 Issues Resolved in CWM 15.1.50, Patch 2 

Bug ID
Headline

CSCec85772

NTS has to suppress sustained trap storms.

CSCei88659

Customer gets failure messages within CCGUI Elements upon attempts to modify MGX 8220 node timezone to any daylight times listed as selectable.

CSCej07544

The stats ager is not purging the data for stratacom database tables.

CSCej28231

Trap support for 50135.

CSCej32748

Stop core does not clean up RPCs.

CSCej57961

The ICR value is set incorrectly on the BXM (ENNI) trunk, equal to MCR for ABR XPVC connections, which caused low throughput for the entire connection.

CSCej59656

CWM 15.1.50 layout can not be saved after stop/start core.

CSCej61947

CWM: Diagnostic center not showing all stats.

CSCej74094

Report for CID stats from VISM card cannot be retrieved.

CSCej77807

The serial number of the standby SRM card is same as for the active SRM card.

CSCej80889

A vbr3RT VXSM connection cannot be created by using the GUI or Service Agent with CWM 15.1.50, Patch 1.

CSCej86453

In adv mode configuration screen, VXSM conn shows as VISM.

CSCin98040

CC GUI: XML parsing error while creating DSX0 group.

CSCin98049

DB discrepancy for vism_codec and CC failure to retrieve CODECs details.

CSCin98397

VXSM: CWM declares partial syncup for pop2 node with VXSM 2.0 image.


Table 27 Issues Resolved in CWM 15.1.50, Patch 1 

Bug ID
Headline

CSCef40566

SCM collection svr reinitialized.

CSCeg36802

MasterAgent should log more details on queue related errors.

CSCeg46628

The CWM should allow creating and saving of sct wit id > 255 (as of June 30, 2005).

CSCeg48525

The svAtmPortVcCount and cwmPvsRsrcMaxLcns vars on IGX does not return (as of June 30, 2005).

CSCeg62787

CC GUI need to validated for duplicate NE while provisioning PrefRoutes.

CSCeg71532

sctDaemon reinitialized on machines.

CSCeg79121

Group names are saved in preference table more than one time (as of June 30, 2005).

CSCeg80123

DB prepare error (code 1802) in SA 4.0 (as of June 30, 2005).

CSCeg86474

overlay map of topo view is not able to be saved.

CSCeg87543

Configurator App: the option to deactivate a node is disabled (grayed-out).

CSCeh14791

SCM: Stats file contain garbled characters (as of June 30, 2005).

CSCeh15769

Background map is not getting set due to hostname not getting resolved (as of June 30, 2005).

CSCeh52545

Connection Manager Unable To Add Connection Descriptor to CESM Connection (as of June 30, 2005).

CSCeh52580

sct should correct db inconsistency.

CSCeh59770

nts needs to re-register if previous registration fails/times out.

CSCeh86839

MFR port deletion failed in OOEMC.

CSCeh93081

Add support for remote and far end line loopback.

CSCeh95809

After deleting the trunks the port is shown as trunk.

CSCeh96884

Not able to delete Connection if any CrossConnects exist in vism_cid table.

CSCeh97053

Local/Remote End Conn Params are messed up on submitting subsequent conn (as of June 30, 2005).

CSCei00522

SRT GUI throws an error that the SRT server not able to retrieve data for VXSM stats.

CSCei01869

DC GUI; Device to loop Combobox should be grayed out for Remote Loopback.

CSCei14148

In NM GUI; setting the client machine time does not work.

CSCei14185

NMGUI filtered view; adding a node to a group turns group color to blue.

CSCei14317

Alarm notes are lost on the Secondary server after coldstart -F.

CSCei27725

need logs preserved to corefilesdir when sctd reinits.

CSCei28729

DC GUI should not show BERT tab for PXM1E card.

CSCei51177

IMA group incorrectly displayed in alarm.

CSCei51182

SRT not able to retrieve data because of field mismatch.

CSCei51600

DC GUI does not display connection diagnostics panel for RPM.

CSCei61414

Saving of watchdog and ftp logs when emc and ooe.

CSCin91618

Card config not aligned with switch for VXSM after resync/pull out.


Table 28 Issues Resolved in WANDEST 2.6.50, Patch 1 

Bug ID
Description

CSCin94490

The WANDEST server throws script errors.


Table 29 Issues Resolved in CWM 15.1.50 

Bug ID
Headline

CSCeg46628

CWM should allow creating/saving of sct wit id > 255.

CSCeg48525

The svAtmPortVcCount and cwmPvsRsrcMaxLcns variables on IGX do not return.

CSCeg63615

ILMITopoc deadlock (CWM 15.1.00 issue).

CSCeg68367

AR PrefRoute support through Config Center GUI that is missed from COL release (CWM 15.1.00 issue).

CSCeg79121

Group names are saved in prference table more than one time.

CSCeg80123

DB prepare error (code 1802) in SA 4.0.

CSCeh14791

SCM: Stats file contain garbled characters.

CSCeh15769

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

CSCeh52545

Connection Manager unable to add connection descriptor to CESM connection.

CSCeh96884

Not able to delete Connection if any CrossConnects exists in vism_cid table.

CSCeh97053

Local/remote end conn params are messed up on submitting subsequent conn.

CSCin84372

Drag and drop of physical view in finder throwing "operation not supported" error (CWM 15.1.00 issue).

CSCin86521

snmpget on DS1 lineloopback is returning wrong value.snmpwalk works fine (CWM 15.1.00 issue).


Related Documentation

These documents are related to the CWM product and are available on Cisco.com. All Rel. 15.1 or Rel. 15.1.00 documents also apply to Rel. 15.1.50 unless otherwise specified in this document.

Online documentation is sometimes updated after the original publication. To ensure that you are viewing the latest information, you can find CWM documents for this release at this URL:

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

The following technical documents comprise the CWM documentation set. The first five documents are on the CWM Documentation CD and on Cisco.com. See CWM 15.1.50 Packaging.

Cisco WAN Manager Installation Guide, Release 15.1.50

Cisco WAN Manager User's Guide, Release 15.1

Cisco WAN Manager SNMP Service Agent Guide, 15.1

Cisco WAN Manager Database Interface Guide, Release 15.1.50

Cisco WANDEST Installation and Reference, Release 2.6

These documents are available on Cisco.com, as are these release notes for Patch 1.

Release Notes for Cisco WAN Manager, Release 15.1.50

Cisco WAN Modeling Tools User Guide, 15.1.50

Cisco WAN Manager Automated Bulk Provisioning Guide, Release 15.1.50

The CWM Modeling Tools and Automated Bulk Provisioning user guides are also available on their software CDs and ordered separately. See CWM 15.1.50 Packaging.

Obtaining Documentation

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

Cisco.com

You can access the most current Cisco documentation at this URL:

http://www.cisco.com/techsupport

You can access the Cisco website at this URL:

http://www.cisco.com

You can access international Cisco websites at this URL:

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

Product Documentation DVD

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:

http://www.cisco.com/go/marketplace/

Ordering Documentation

Beginning June 30, 2005, registered Cisco.com users may order Cisco documentation at the Product Documentation Store in the Cisco Marketplace at this URL:

http://www.cisco.com/go/marketplace/

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

Documentation Feedback

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

You can 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 this address:

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

We appreciate your comments.

Cisco Product Security Overview

Cisco provides a free online Security Vulnerability Policy portal at this URL:

http://www.cisco.com/en/US/products/products_security_vulnerability_policy.html

From this site, you can perform these tasks:

Report security vulnerabilities in Cisco products.

Obtain assistance with security incidents that involve Cisco products.

Register to receive security information from Cisco.

A current list of security advisories and notices for Cisco products is available at this URL:

http://www.cisco.com/go/psirt

If you prefer to see advisories and notices as they are updated in real time, you can access a Product Security Incident Response Team Really Simple Syndication (PSIRT RSS) feed from this URL:

http://www.cisco.com/en/US/products/products_psirt_rss_feed.html

Reporting Security Problems in Cisco Products

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

Emergencies — security-alert@cisco.com

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

Nonemergencies — psirt@cisco.com

In an emergency, you can also reach PSIRT by telephone:

1 877 228-7302

1 408 525-6532


Tip We encourage you to use Pretty Good Privacy (PGP) or a compatible product 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:

http://www.cisco.com/en/US/products/products_security_vulnerability_policy.html

The link on this page has the current PGP key ID in use.


Obtaining Technical Assistance

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

Cisco Technical Support & Documentation Website

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

http://www.cisco.com/techsupport

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

http://tools.cisco.com/RPF/register/register.do


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


Submitting a Service Request

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

http://www.cisco.com/techsupport/servicerequest

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

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

Asia-Pacific: +61 2 8446 7411 (Australia: 1 800 805 227)
EMEA: +32 2 704 55 55
USA: 1 800 553-2447

For a complete list of Cisco TAC contacts, go to this URL:

http://www.cisco.com/techsupport/contacts

Definitions of Service Request Severity

To ensure that all service requests are reported in a standard format, Cisco has established 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:

http://www.cisco.com/go/marketplace/

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

http://www.ciscopress.com

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

http://www.cisco.com/packet

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

http://www.cisco.com/go/iqmagazine

or view the digital edition at this URL:

http://ciscoiq.texterity.com/ciscoiq/sample/

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

http://www.cisco.com/ipj

Networking products offered by Cisco Systems, as well as customer support services, can be obtained at this URL:

http://www.cisco.com/en/US/products/index.html

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

http://www.cisco.com/discuss/networking

World-class networking training is available from Cisco. You can view current offerings at this URL:

http://www.cisco.com/en/US/learning/index.html