Guest

Cisco WAN Manager

Release Notes for Cisco WAN Manager 11.0.10 Patch 2.0 for Solaris 8

  • Viewing Options

  • PDF (1.3 MB)
  • Feedback
Release Notes for Cisco WAN Manager for Solaris 8, Release 11.0.10, Patch 2

Table Of Contents

Release Notes for Cisco WAN Manager for Solaris 8, Release 11.0.10, Patch 2

Table of Contents

Overview

System Requirements

Server

Client

Stand Alone SCM

Solaris Patch Requirements

Required Patches

Recommended Patches

CWM Software Packaging

HP OpenView Requirements

INFORMIX Requirements

Wingz Requirements

Supported Hardware

Existing Hardware

New Hardware

Certified Releases

WANDEST Certification Matrix

New Features and Enhancements in CWM Release 11.0

Features Introduced in CWM Release 11.0.10, Patch 2

Features Introduced in CWM Release 11.0.10, Patch 1

FRSM Statistics

AUSM Statistics

PXM1 Statistics

Network Interface Events

CWM Internal Events

cwmfrWatchdogError (trap#28201)

cwmfrGatewayStatus (trap#28202)

cwmfrCwmInternalError (trap#28203)

cwmfrCwmDatabaseError(trap#28204)

System Events (cwmfrCwmSystemError trap#28301)

User Guidelines

Network Interface Events

CWM Internal Events

System Events

Features Introduced in CWM Release 11.0.10

New Features and Enhancements from CWM Release 10.4.10 Patch 4 Incorporated into CWM 11.0.10 Patch 1

Configuring Auto-Restart

New Features and Enhancements from CWM Release 10.5.10 Patch 3 Incorporated into CWM 11.0.10

Conversion of KBPS to CPS in Connection Manager

New Features and Enhancements from CWM Release 10.5.10 Patch 2 Incorporated into CWM 11.0.10

Connection Segment Loopback Test and Connection Loopback Test for PVC

Egress Queue Selection for FRSM-8

Displaying Master Endpoint as Local Endpoint in Connection Manager GUI

Access Control Privilege for Deleting Multiple Connections

Enhanced Node Reachability Monitoring

Setting Default Values for Filters in Connection Manager GUI

AUSM Egress Counters

New Features and Enhancements in WANCV Release 4.11

Features Not Supported in WANCV Release 4.11

Features Not Supported and Known Feature Limitations in 11.0.10

Supported Connections

Supported Cards

Frame Relay

ATM Service Modules

Circuit Emulation (CE) Service Modules

Voice Service Modules

Data Service Modules

PVC Connections Supported by CWM 11

SPVC Connections Supported by CWM 11

HYBRID Connections Supported by CWM 11

XPVC Connections Supported by CWM 11

Limitations

Notes

Limitations to Upgrading the Stand-alone SCM

Issue with CWM 11 Security Manager

HP OpenView

Issues with CWM 11 Statistics Collection Manager

Limited Number of Routers

Ad-Hoc Reports

Limitations for WANDEST

Limitations for CWM-to-CWM Communication

Topology

SNMP Traps

CWM 11 Notes and Cautions

CWM 11.0.10 Server Installation or Upgrade to CWM 11.0.10 from CWM 10.5 and Earlier

Issue with Upgrading or Installing CWM 11.0.10 on Systems that Use or Will Be Using Meta Devices or Multiple Disks for Informix

Fixing Issue before Rebooting

Downloading the 11_0_10_S97firsttime.tar File from CCO

Editing the Existing /etc/rc3.d/S97firsttime File Manually

Remedy if You Have Already Rebooted the Workstation

Replace or Edit the S97firsttime File (Requires a Reboot)

Downloading the 11_0_10_S97firsttime.tar File from CCO

Editing Existing /etc/rc3.d/S97firsttime File Manually

Cleaning Up TEE Process (Does Not Require Reboot)

Remedy if You Have Already Rebooted Workstation and Entered CWM as svplus

Replace or Edit S97firsttime File (Requires Reboot)

Downloading 11_0_10_S97firsttime.tar File from CCO

Editing Existing /etc/rc3.d/S97firsttime File Manually

Remedy if You Have Already Rebooted Workstation and Started Core Processes

Issue with .rhosts File During Upgrade

Saving User-created Statistics Collection Manager Templates before Upgrading

CWM 11.0.10 Patch 2 Installation

Solaris 8

CWM Server Patch and Informix 9.21 UC7

CWM Client Patch Installation

CWM SNMPAgent (ServiceAgent) Patch Installation

CWM SCMSA Patch Installation

WANDEST Server Patch Installation

WANDEST Client Patch Installation

CWM 11.0.10 non-Java-based Client Installation

Installing Solaris 8

Configuring Workstation Display

Installing InstallShield non-Java based CWM Client Software

Rebooting the Workstation

Installing Netscape Communicator

Preparing CWM 11.0.10 Server Workstation to Launch CiscoView from Client Topology Window

Preparing CWM 11.0.10 Client Workstation to Launch CiscoView from Client Topology Window

Important Configuration Notes

Orbix Registration

Setting Up CWM-to-HP OpenView Communication

Naming Managed Nodes

Enabling Connection Descriptor

CWM Configuration

CWM Dedicated IP Ports

Unique Node ID

Security Profiles

CWM Database

Topology Discovery Configuration for AutoRoute Networks

Topology Discovery Configuration for PNNI Networks

Topology Discovery Configuration for Hybrid (AutoRoute and PNNI) Networks

Topology Discovery Configuration for StandAlone Nodes

Connection Manager Configuration

Configuration Parameters for Connection Manager Daemon (cmgrd)

RPM

Setting up CiscoView to Manage RPM Cards from Workstation

Configuring SNMP and SYSLOG

Configuring CiscoView for Large Networks

SNMP Service Agent Release Notes

CWM SNMP Agent Configuration Notes

SNMP Stack Parameters for CWM 11

MAX_THREADS

MAX_PDU_TIME

MAX_OUTPUT_WAITING

OSS Timeout and Retry

Statistics Collection Manager Release Notes

New Features

Limitations

Additional Information

WANCV 4.11 Notes and Cautions

Performance

Control Point Interfaces

Command Line Interface

Caveats

Anomalies Resolved in CWM Release 11.0.10 Patch 2

Known Anomalies in CWM 11.0.10 Patch 2 Software

Anomaly Status Changes in Release 11.0.10 Patch 2

Anomalies Resolved in CWM 11.0.10 Patch 1

Anomaly Status Changes in Release 11.0.10 Patch 1

WANDEST Server Release 2.3 Patch 2.1

Anomalies Resolved in WANDEST Server Release 2.3 Patch 2

Anomalies Resolved in WANDEST Server Release2.3 Patch 1

Anomalies Resolved in WANDEST Client Release 2.3 Patch 2.1

Anomalies Resolved in WANDEST Client Release 2.3 Patch 2

Related Documentation

Obtaining Documentation

World Wide Web

Documentation CD-ROM

Ordering Documentation

Documentation Feedback

Obtaining Technical Assistance

Cisco.com

Technical Assistance Center

Cisco TAC Web Site

Cisco TAC Escalation Center


Release Notes for Cisco WAN Manager for Solaris 8, Release 11.0.10, Patch 2


Cisco WAN Manager Release 11.0.10 for Solaris 8 supports the following Cisco products:

Cisco MGX 8850 PXM45-based products running minimum software releases 2.0.15, 2.1.70, or 3.0.10.

Cisco MGX 8950 PXM45-based products running minimum software releases 2.1.76, or 3.0.10.

Cisco MGX PXM1E-based products (8830 and 8850) running minimum software release 3.0.10.

Cisco MGX PXM1-based products (8230, 8250 and 8850) running minimum software releases 1.1.34, 1.1.40, or 1.2.00.

Cisco SES PNNI Controller running minimum software releases 1.0.16, 1.1.75, or 3.0.10.

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

Existing Cisco MGX 8220 products running minimum software releases 4.1.07, or 5.0.12.


Caution If you will be setting up multiple partitions (answering "Yes" to the "Do you want multiple Disk configuration for informix database?" prompt) or setting up meta devices (answering "Yes" to the "Do you use disk striping (meta devices) for database partitions?") during your installation of CWM, BEFORE rebooting the workstation (the last step of the installation), you MUST follow the instructions in the "Issue with Upgrading or Installing CWM 11.0.10 on Systems that Use or Will Be Using Meta Devices or Multiple Disks for Informix" section. Refer to this section before installing release 11.0.10 or upgrading your CWM workstation. to CWM release 11.0.10. Upgrading from CWM Release 11.0.10 to CWM Release 11.0.10, Patch 2 is not affected.

Table of Contents

Connection Statistics      20
Port Statistics      20
Port Statistics      21
Port Statistics      21
cwmfrNetworkCommFailure Events (trap# 28101)      23
cwmfrNetworkProcessingFailure Events (trap# 28102)      23
cwmfrNetworkTimeoutError Events (trap# 28103)      25
cwmfrNetworkConfigurationError Events (trap# 28104)      25

Overview

This document contains the following sections:

"System Requirements" section

"CWM Software Packaging" section

"Supported Hardware" section

"New Features and Enhancements in CWM Release 11.0" section

"Features Introduced in CWM Release 11.0.10, Patch 1" section

"Features Introduced in CWM Release 11.0.10" section

"Java GUIs for Config/Save/Restore and Image Download" section

"New Features and Enhancements in WANCV Release 4.11" section

"Features Not Supported in WANCV Release 4.11" section

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

"Supported Connections" section

"Limitations" section

"CWM 11 Notes and Cautions" section

"Issue with Upgrading or Installing CWM 11.0.10 on Systems that Use or Will Be Using Meta Devices or Multiple Disks for Informix" section

"Issue with .rhosts File During Upgrade" section

"Saving User-created Statistics Collection Manager Templates before Upgrading" section

"Installing InstallShield non-Java based CWM Client Software" section

"Preparing CWM 11.0.10 Server Workstation to Launch CiscoView from Client Topology Window" section

"Preparing CWM 11.0.10 Client Workstation to Launch CiscoView from Client Topology Window" section

"Important Configuration Notes" section

"Setting Up CWM-to-HP OpenView Communication" section

"Setting up CiscoView to Manage RPM Cards from Workstation" section

"SNMP Service Agent Release Notes" section

"CWM SNMP Agent Configuration Notes" section

"Statistics Collection Manager Release Notes" section

"WANCV 4.11 Notes and Cautions" section

"Control Point Interfaces" section

"Caveats" section

"Anomalies Resolved in WANDEST Server Release2.3 Patch 1" section

"Obtaining Documentation" section

"Obtaining Technical Assistance" section

System Requirements

Server

Five types of machines are supported for Cisco WAN Manager 11 as standard server platforms. They are one low-end, two mid-range (Medium Level 1 and Solaris 8), one high-end, and one carrier grade platform. Table 1 describes the configuration for each platform.

Table 1 Sun Server Platform Requirements 

CWM Platform
Model
CPU
RAM
SWAP
DISK
Video
# Connections
# Clients
# Nodes
# SSC Collectors

Low End

Ultra 60

1

1 GB

4 GB

2x9 GB
or
1 x 18 GB

19 inch Color monitor, 24 bit graphics card

5,000

5

20

1

Medium Level 1

Ultra 60

2

2 GB

8 GB

2x9 GB
or
1 x 18 GB

19 inch Color monitor, 24 bit graphics card

50,000

10

100

1

Medium Level (Solaris 8)

Netra 20

2

2 GB

8 GB

2x9 GB
or
1 x 18 GB

19 inch Serial Port Terminal

100,000

10

200

1

High End

E450

4

4 GB

16 GB

4x9 GB
or
1 x 36 GB

19 inch Color monitor, 24 bit graphics card

200,000

20

1,000

4

Carrier Grade

E4500

14

8 GB

16 GB

4x9 GB
or
1 x 36 GB

19 inch Color monitor, 24 bit graphics card

1,000,000

100

2,000

8


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

The following are additional notes for CWM platform requirements:

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

Only Solaris 2.8 is available on the Netra 20 Server. Also, Solaris 2.7 and Solaris 2.8 versions of CWM are shipped on separate CD media and have unique part numbers.

The Number of Clients field assumes one application per client. The aggregate number of applications running should not exceed the number in the Number of Clients field and the number of CWM clients you install should be adjusted accordingly.

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

The default disk size for the Informix raw database is 900 MB. However, we strongly recommend you provide 2 GB disk space for the statistics collection process.

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

RPM cards that are unconfigured slow down the launch of CiscoView. Use Cisco IOS to configure the RPM card for management through SNMP before launching CiscoView. Refer to the "Setting up CiscoView to Manage RPM Cards from Workstation" section and the "Configuring SNMP and SYSLOG" section for instructions.

The following are the recommended values to set for SNMP Preferences in CiscoView for Polling, Timeout, Monitor, and Retry values:

The recommended Polling Frequency is at least 60 sec.

The recommended Timeout value is 15 seconds.

The recommended Monitor frequency is 60 seconds.

The recommended Retry count is 1.

Set the SNMP Preferences in CiscoView the first time you start CiscoView.

Client

Table 2 describes the configuration for the two minimum types of machine supported for Cisco WAN Manager 11 as a standard client platform.

Table 2 Sun Client Platform Requirements 

Machine Type
Number of CPUs
Size of RAM
Hard Disk Drive
Swap Space
Desktops Supported
Video

Windows 2000 or Windows NT 4.0 based PC (Pentium 3)

1

256 MB

Requires 50 MB of disk space

N/A

Less than 5

21 inch Color monitor, SVGA graphics card

Sun Ultra 10 with SCSI controller

1

512 MB

Requires 50 MB of disk space

1 GB

Less than 5

19 inch Color monitor, 24 bit graphics card



Note The minimum Sun CPU speed requirement is 300 MHz. Most versions of the Sun Ultra 10 have a 450 MHz processor. Each Sun client requires a 24-bit graphics card.


Stand Alone SCM

Five types of machines are supported for CWM Release 11 Statistics Collection Manager software as standalone platforms. They are one low-end, two mid-range (Solaris 7 and Solaris 8), one high-end, and one carrier grade platform. Table 3 describes the configuration for each platform.

Table 3 Stand Alone Statistics Collection Manager Platform Requirements 

SSC Platform
Model
# CPU
RAM
SWAP
DISK
Video
Number of Connections
Number of Nodes
Number of Collectors

Low End

Ultra 10

1

512 MB

1 GB

2x9 GB
or
1 x 18 GB

N/A

N/A

20

1

Medium Level (Solaris 7)

Ultra 60

2

1 GB

1 GB

2x9 GB
or
1 x 18 GB

N/A

50,000

100

1

Medium Level (Solaris 8)

Netra 20

1

1 GB

1 GB

2x9 GB
or
1 x 18 GB

N/A

100,000

100

1

High End

E 450

4

2 GB

4 GB

2x9 GB
or
1 x 18 GB

N/A

200,000

250

4

Carrier Grade

E 450

4

2 GB

4 GB

2x9 GB
or
1 x 18 GB

N/A

1,000,000

250

8


Solaris Patch Requirements

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

108528-13

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

Required Patches

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

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

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

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

111626-01

111327-02

110945-02

110934-01

110898-02

110700-01

110670-01

109326-05

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

108652-35

108528-13

Recommended Patches

110951-01

110662-02

110615-01

110286-02

109324-02

111085-02

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

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


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


CWM Software Packaging

Following is the list of CDs for the CWM 11.0.10 release:

CWM Server/Client CDROM 1. This CD contains the following:

CWM Server Software

INFORMIX Server Software Release 9.2

WANCV 4.11

CiscoView Engine 5.4.1

Integrated SCM Software

CWM Server/Client CDROM 2. This CD contains the following:

CWM Client Software

Netscape Communicator 4.76

Acrobat Reader 4.0

gzip

JRE plugin 1.3.1

PDF copies of the CWM 11 documentation set

The Service Agent software is provided on a separate CD. This CD is ordered separately from the CWM 11 release CD set.

Service Agent CD. This CD contains the following

CWM Service Agent Software

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

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

Standalone SCM Software

The Wingz Release 2.5.1 software is also on a separate CD.

Wingz Release 2.5.1 CD

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

HP OpenView Requirements

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


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


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

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

INFORMIX Requirements

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

Wingz Requirements

The Report Application contained in the CWM 11.0.10 Patch 2 release uses Wingz 2.5.1. For the Ad-Hoc Report Application to work properly, the Wingz DataLink program must be installed along with Wingz software. Note that with CWM 11.0.10, the Report Application can be launched from a command line prompt.

Wingz and Summary Reports are no longer available within either the client or the server and can no longer be launched from the Network Topology application as a pull down with either the client or the server.

Wingz and Summary Reports are no longer available within either the client or the server and can no longer be launched from the Network Topology application as a pull down with either the client or the server.

To launch Wingz reports, complete the following procedure:


Step 1 Open a terminal window.

Step 2 Enter wingz at the prompt.


Note If you enter an uppercase w, for example, Wingz, the Statistics button will not be displayed on the Wingz toolbar.



To launch summary reports, complete the following procedure:


Step 1 Open a terminal window.

Step 2 Enter NWReport at the prompt.


Supported Hardware

This section provides information about the hardware supported by CWM 11.0.10 Patch 2.

Existing Hardware

Table 4 lists the existing hardware supported prior to CWM 11.0.10 Patch 2.

Table 4 Supported Existing Hardware 

Platform Series
Front Card
Back Card
Min. Software Version

IGX 8400

NPM

SCM

SWSW 9.2.33, SWSW 9.3.05

IGX 8400

NTM

BC-T1/E1/SR/Y1

SWSW 9.2.33, SWSW 9.3.05

IGX 8400

BTM

AIT-T3/E3/E2/HSS1/E1

SWSW 9.2.33, SWSW 9.3.05

IGX 8400

FRM

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

SWSW 9.2.33, SWSW 9.3.05

IGX 8400

FTM

FPC-V35/T1/E1/X.21

SWSW 9.2.33, SWSW 9.3.05

IGX 8400

HDM

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

SWSW 9.2.33, SWSW 9.3.05

IGX 8400

LDM

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

SWSW 9.2.33, SWSW 9.3.05

IGX 8400

CVM

BC-T1/E1/J1/Y1/SR

SWSW 9.2.33, SWSW 9.3.05

IGX 8400

UVM

UVI-2T1EC/2E1EC

SWSW 9.2.33, SWSW 9.3.05

IGX 8400

UFM-C

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

SWSW 9.2.33, SWSW 9.3.05

IGX 8400

UFM-U

UFI-V35/X21/HSI

SWSW 9.2.33, SWSW 9.3.05

IGX 8400

ARM

ARI

SWSW 9.2.33, SWSW 9.3.05

IGX 8400

UXM

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

SWSW 9.2.33, SWSW 9.3.05

BPX 8600

BCC

BCC-bc/3-bc

SWSW 9.2.33, SWSW 9.3.05

BPX 8600

ASM

LM-ASM

SWSW 9.2.33, SWSW 9.3.05

BPX 8600

BNI-T3

LM-3T3

SWSW 9.2.33, SWSW 9.3.05

BPX 8600

BNI-E3

LM-3E3

SWSW 9.2.33, SWSW 9.3.05

BPX 8600

BNI-155

LM-OC3-SMF/SMFLR/MMF

SWSW 9.2.33, SWSW 9.3.05

BPX 8600

ASI-1

LM-2T3/2E3

SWSW 9.2.33, SWSW 9.3.05

BPX 8600

ASI-155

LM-2OC3-SMF/SMFLR/MMF

SWSW 9.2.33, SWSW 9.3.05

BPX 8600

BXM-T3/E3

T3/E3-BC

SWSW 9.2.33, SWSW 9.3.05

BPX 8600

BXM-15 5

MMF/SMF/SMFLR-155

SWSW 9.2.33, SWSW 9.3.05

BPX 8600

BXM-622

MMF/SMF/SMFLR-622

SWSW 9.2.33, SWSW 9.3.05

MGX 8220

FRSM-4P

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

4.1.07, 5.0.12

MGX 8220

CESM-4P

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

4.1.07, 5.0.12

MGX 8220

AUSM-4P

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

4.1.07, 5.0.12

MGX 8220

FRSM-8P

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

4.1.07, 5.0.12

MGX 8220

AUSM-8P

RJ48-8E1/8T1

4.1.07, 5.0.12

MGX 8220

CESM-8P

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

4.1.07, 5.0.12

MGX 8220

IMATM-B

RJ48-T3T1/E3E1/E3T1/T3E1

4.1.07, 5.0.12

MGX 8220

FRSM-HS1

HSI-4X21/3HSSI

4.1.07, 5.0.12

MGX 8220

BNM-T3/E3

T3E3-B/D

4.1.07, 5.0.12

MGX 8220

BNM-155

155-SMF

4.1.07, 5.0.12

MGX 8220

SRM

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

4.1.07, 5.0.12

MGX 8220

ASC

ASC-LM

4.1.07, 5.0.12

MGX 8220

FRSM-VHS

HS2

4.1.07, 5.0.12

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

AUSM Model B

8T1/E1

4.1.07, 5.0.12, 1.1.34, 1.1.40, 1.2.00

MGX 8230, MGX 8250, MGX 8850 R1

PXM1

T3/E3/OC3/OC12

1.1.40, 1.2.00

MGX 8230, MGX 8250, MGX 8850 R1

FRSM-VHS

HS2/T3/E3/CT3

1.1.40, 1.2.00

MGX 8230, MGX 8250, MGX 8850 R1

FRSM-8P

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

1.1.40, 1.2.00

MGX 8230, MGX 8250, MGX 8850 R1

CESM-8P

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

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

1.1.40, 1.2.00

MGX 8230, MGX 8250, MGX 8850 R1

CESM

T3/E3

1.1.40, 1.2.00

MGX 8230, MGX 8250, MGX 8850 R1

RPM

10mbps/100mbps

rpm-js-mz.120-5.XT1

MGX 8230, MGX 8250, MGX 8850 R1

SRM

LM-3T3

1.1.40, 1.2.00

MGX 8230, MGX 8250, MGX 8850 R1

VISM-8T1

AX-RJ48-8T1

AX-R-RJ48-8T1

2.1.1, 2.2.00, 3.0.00, 3.1.00

MGX 8230, MGX 8250, MGX 8850 R1

VISM-8E1

AX-SMB-8E1

AX-RJ48-8E1

AX-R-SMB-8E1

AX-R-RJ48-8E1

2.1.1, 2.2.00, 3.0.00, 3.1.00


New Hardware

Table 5 lists the new hardware supported in CWM 11.0.10 Patch 2.

Table 5 Supported New Hardware 

Platform Series
Front Card
Back Card
Min. Software Version

MGX 8950 (PXM45)

AXSM

T3/E3

2.1.70, 3.0.10

MGX 8950 (PXM45)

AXSM

OC3

2.1.70, 3.0.10

MGX 8950 (PXM45)

AXSM

OC12

2.1.70, 3.0.10

MGX 8950 (PXM45)

AXSM

OC48

2.1.70, 3.0.10

MGX 8950 (PXM45)

PXM45

N/A

2.1.70, 3.0.10

MGX 8950 (PXM45)

PXM45B

N/A

2.1.70, 3.0.10

MGX 8850 (PXM45)

AXSM-E

T3/E3

2.0.15, 2.1.70, 3.0.10

MGX 8850 (PXM45)

AXSM-E

OC3

2.0.15, 2.1.70, 3.0.10

MGX 8850 (PXM45)

AXSM-E

OC12

2.0.15, 2.1.70, 3.0.10

MGX 8850 (PXM45)

AXSM-E

OC48

2.0.15, 2.1.70, 3.0.10

MGX 8850 (PXM45)

PXM45

N/A

2.0.15, 2.1.70, 3.0.10

MGX 8850 (PXM45)

PXM45B

N/A

2.0.15, 2.1.70, 3.0.10

MGX 8850 (PXM45)

VISM-PR

RJ48-T1/E1 and SMB-E1

3.0.00, 3.1.00

MGX 8850 (PXM1E)

PXM1E

8 Port 155

3.0.10

MGX 8850 (PXM1E)

PXM1E

8 Port T3/E3

3.0.10

MGX 8850 (PXM1E)

RPM-PR

Ethernet, Fast Ethernet

3.0.10

MGX 8850 (PXM1E)

VISM-PR

RJ48-T1/E1 and SMB-E1

3.0.10

MGX 8850 (PXM1E)

AUSM Model B

8T1/E1

3.0.10

MGX 8850 (PXM1E)

FRSM-8P

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

3.0.10

MGX 8850 (PXM1E)

CESM-8P

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

3.0.10

MGX 8850 (PXM1E)

FRSM-HS2B

8 port 12in1, HSSI

3.0.10

MGX 8850 (PXM1E)

SRM/E

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

3.0.10

MGX 8850 (PXM1)

FRSM-HS2B

8 port 12in1, HSSI

1.2.00

MGX 8850 (PXM1)

SRM/E

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

1.2.00

MGX 8850 (PXM1)

RPM/B

Ethernet, Fast Ethernet

1.2.00

MGX 8850 (PXM1)

RPM-PR

Ethernet, Fast Ethernet

1.2.00

MGX 8850 (PXM1)

VISM-PR

RJ48-T1/E1 and SMB-E1

1.2.00

SES PNNI Controller

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

P/N 800-06454-01

PXM-UIA

Rev: 05

MMF-4-155

Rev: 09

1.0.16, 1.1.75, 3.0.10

SES PNNI Controller

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

P/N 800-06454-01

PXM-UIA

Rev: 05

SMFIR-4-155

Rev: 09

1.0.16, 1.1.75, 3.0.10

SES PNNI Controller

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

P/N 800-06699-01

PXM-UIA

Rev: 05

BNC-2T3

Rev: 03

1.0.16, 1.1.75, 3.0.10

SES PNNI Controller

SES-PXM-CNTL-2T3E3

(with 2 port T3E3)

P/N 800-06699-01

PXM-UIA

Rev: 05

BNC-2E3

Rev: 03

1.0.16, 1.1.75, 3.0.10


Certified Releases

The following releases were tested with CWM release 11.0.10 Patch 2:

BPX Switch Software:

Switch Software 9.3.45

Switch Software 9.3.36

Switch Software 9.2.41

MGX 8230/8250/8850 (PXM1) Switch

MGX 1.2.13

MGX 1.2.02

MGX 1.1.34

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

MGX 3.0.20

MGX 2.1.80

BPX SES Shelf

SES 3.0.20

SES 1.1.79

MGX 8220 Shelf

MGX 8220 5.0.19

MGX 8220 4.1.12

VISM

VISM 3.1.00

VISM 2.2.00

WANDEST Certification Matrix

CWM version
11.0.10
11.0.10 P1
11.0.10 P2
11.0.10 P2

Wandest 2.3 Version

2.3

2.3 Patch 1

2.3 Patch 2

2.3 Patch 2.1


The following version of CWM was certified with WANDEST:

WANDEST 2.3 Patch 1, 2, and 2.1 are bug-fix only releases and have the same feature content as WANDEST 2.3 that was introduced with Release 11.0.10. All Patches contain cumlative fixes and features from the prior patch release.

Refer to "Caveats" section for the list of resolved anomalies.

New Features and Enhancements in CWM Release 11.0

Features Introduced in CWM Release 11.0.10, Patch 2

The following new feature and enhancement has been introduced in CWM 11.0.10 Patch 2:

Enhanced Network Configurator to have the added capability to delete a decommissioned

node from CWM.

Features Introduced in CWM Release 11.0.10, Patch 1

The following new features and enhancements have been introduced in CWM 11.0.10 Patch 1:

Node Resync

The Node Resync feature is extended with following functionalities for SPVCs:

There are now three types of node resync. The Level 1 Update and Level 2 Update are available through the node resync menu item under the CWM Topology GUI. The Memory Database Resync is available using a script. More details are provided below:

a. Level 1 Update: This types of node resync resolves inconsistencies between the switch and the Equipment Manager, as well as inconsistencies between the Equipment Manager and the segment tables in the database. It also sends all the connection notifications to databroker so as to ensure consistency between the Equipment Manager view and Databroker view of the network. It should only be used when the number of inconsistencies is small. CWM will first compare its database with the switch and flags all the connections that exist on one side but not the other. CWM then issues SNMP GET requests for each such connection to the switch to resolve the inconsistencies. The process can be very slow if the number of inconsistencies is large.

b. Level 2 Update: This type of node resync gets the full connection file from the switch and resolves inconsistencies between the switch and the Equipment Manager caches, as well as inconsistencies between the Equipment Manager caches and the databroker cache. Like Level 1, Level 2 also resolves inconsistencies between the Equipment Manager and the segment tables in the database. This option should be used if the number of inconsistencies is large. The amount of time that this resync process will take depends on the number of connections on the node, (for example, the process can take up to 45 - 50 minutes for 100 thousand endpoints). This is a complete resync. Afterwards, the Equipment Manager caches and the databroker caches, as well as the segment tables in the database should be completely in sync (including alarms and connection parameters) with switch.

c. Memory/Database resync for Databroker: The Memory/Database resync resolves any inconsistencies that might exist between the Databroker cache and the user_connection table. This must be used as the last option only if the inconsistencies are not resolved even after doing the previous Level 1 or Level 2 resync operations. Start this resync by executing the following CLI interface/tool:

> /usr/users/svplus/tools/CacheResync
     It should take 869 seconds to sync the database
     using an ultra 60
     Do you want to proceed (y/n) y
     Cache-Database Resync took 754 sec 

The Memory/Database resync process blocks provisioning, clears the user_connection table and re-flushes all the connections from its cache to the user_connection table. The time it takes to complete these operations is dependent upon the number of connections and the type of machine the CWM is running on.


Note The log debug level affects the length of time it takes to complete the total resync. For example, for CWM on an ultra60 managing a network with 12,000 connections with the debug level set to `4' (ERROR), the execution time is about 2 seconds. If the debug level is set to `7' (DEBUG) the execution time is about 15 minutes.


New Statistics Types for AUSM/FRSM/PXM1 cards

Statistics Collection Manager (SCM) now includes new statistics types for FRSM PVC connections and ports: one new statistics type for AUSM ports and one new statistics type for the PXM1 card. This support has been added only on the PXM1-based MGX platform.

The added statistics are:

FRSM Statistics

Connection Statistics

Statistic Type
Description

xmtBytesDEDiscard

Number of bytes in the egress direction on the channel with DE bit set to 1

rcvBytesDEDiscard

Number of bytes discarded in the ingress direction on the channel with DE bit set to 1

XmtBytesDE

Total Number of Bytes with DE=1 transmitted to the Port side

XmtFramesDiscXceedDEThresh

Total CLP1 cells / DE Frames discarded due to congestion (DE Threshold exceeded)


Port Statistics

Statistic Type
Description

RcvPortFramesDiscard

Number of frames discarded in the ingress direction by the port

xmtPortFramesDE

Number of frames transmitted in the egress direction by the port with DE bit set to 1

xmtPortBytesDE

Number of bytes transmitted in the egress direction by the port with DE bit set to 1

rcvPortBytesDE

Number of bytes received in the ingress direction by the port with DE bit set to 1

xmtPortFramesDiscXceedDEThresh

Number of frames discarded in the egress direction by the port with DE bit set to 1

xmtPortBytesDiscXceedDEThresh

Number of bytes discarded in the egress direction by the port with DE bit set to 1

rcvPortBytesDiscXceedDEThresh

Number of bytes discarded in the ingress direction by the port with DE bit set to 1


AUSM Statistics

Port Statistics

Statistic Type
Description

totalIngrClpSetRcvCells

The number of CLP set cells received in Ingress direction on the port


PXM1 Statistics

Port Statistics

Statistic Type
Description

RcvErroredCells

Total cells with invalid VPI VCI and invalid PTI field.


Health Monitor

Health Monitor is a new feature supported in CWM 11.0.10 Patch 1. It allows CWM to collect network management health related data (network-related events, CWM internal events, and system events) and to record them into /usr/users/svplus/log/cwmErrors.log and generated SNMP traps in HPOV. To enable Health Monitor, change "HEALTH_MONITOR" flag in svplus.conf to ON before starting CWM.

The following three types of network management health information are monitored:

Switch network management interfaces,

CWM components, and

Underlying systems such as Unix, Informix, Orbix, etc.

Events are grouped into following three categories:

Network-related events that CWM has no or little control over such as IP unreachable, FTP timeouts, etc.

CWM Internal events that CWM has the capability to resolve such as process crashes, IPC link failures, etc.

System events that may cause problems in CWM and require operator intervention such as disk full, low on swap space, etc.

Events are classified as belonging to one of the following three severity levels:

Critical: Critical Events require intervention as they indicate that either one or more CWM components to be out of sync with underlying network, or that an event has occurred that prevents CWM from performing required configuration/provisioning functions.

Warning: Warning Events may cause one or more CWM components to be out of sync with underlying network, or prevent CWM from performing required configuration/provisioning functions immediately or in near future.

Information: Information Events are those events that aid the operator in understanding overall network management conditions. These events are not causing CWM components to be out of sync with the underlying network, and/or do not prevent CWM from performing any required configuration/provisioning functions.

Two different actions will be taken in response to the events:

Logging only: For events interesting to customers and CWM support engineers but do not require immediate attention. The events will be stored in a central log file.

Logging & SNMP traps: For events that require immediate attention. In addition to storing the events in the log file, SNMP traps are generated and forwarded to RTMProxy and to HPOV (if available).

The network events are grouped into 4 broad categories:

NetworkCommunicationError(Trap#28101): Generated when CWM processes detect network communication failures such as session failure, reachability etc. This trap reports the node id or ip that has the problem along with a detailed description of the failure.

NetworkProcessingError(Trap#28102): Generated when CWM processes they encounter protocol errors or when they are unable to process network messages even after the max retries is reached. This category also includes errors which are reported when the CWM processes expect a certain set of events from network but they do not receive. This trap reports the node id or ip that has the problem along with a detailed description of the failure.

NetworkTimeoutError(Trap#28103): Generated when CWM processes timeout on some network operation. This trap reports the node id or ip that has the problem along with a detailed description of the failure.

NetworkConfigurationError(Trap#28104): Generated when CWM detects network configuration errors like duplicate trunks etc.

The internal events are grouped into 2 different categories:

InternalError (Trap # 28203): Generated when CWM processes detect inter-process communication errors or unexpected errors.

DatabaseError (Trap# 28204): Generated when CWM processes detect database operation failures which could be critical.

The system errors (Trap # 28301) are reported when CWM detects low disk, swap or db space.

Network Interface Events

cwmfrNetworkCommFailure Events (trap# 28101)

Error Code
Severity
Reported By
Parameters
Description

ftp-session-fail

info

cwmftpd

node_ip

 

ftp-transfer-fail

info

cwmftpd

node_ip

 

net-link0-down

critical

emsd

node_id

Communication failure between the Gateway node in the auto route network. This may be due to the temporary unreachability of the Gateway node LAN ip address.

net-link1-down

critical

emsd

node_id

Communication failure between the node in the auto route network. This may be due to the temporary unreachability of the node network IP address.

ntsmgr-net-fail

critical

rtm

node_id/node_ip

 

nts-trap-loss

info

rtm

node_id/node_ip

 

cwmfrNetworkProcessingFailure Events (trap# 28102)

Reported when CWM encounters error while processing information from network or max retries have been attempted during the processing. All protocol errors are also reported under this category.

Error Code
Severity
Reported By
Parameters
Description

no-nw-partition

warning

emsd

network_id

There is no Gateway specified in the network.conf file in /usr/users/svplus/config directory

no-node-revision

info

emsd

node_ip, sequence no

To start sync up with IGX/BPX switches the revision message is one of the most important messages. If for some reason it is lost, the sync up time will be increased.

no-node-subscription

info

emsd

node_id, sequence no

To start sync up with IGX/BPX switches the subscription message is one of the important message. For some reason if it is lost, the sync up time will be increased.

incorrect-msg

info

emsd

node_id, sequence no

While sync up is going on between IGX/BPX switches, since the protocol use UDP there may be a chance to loose the message. Once the message send from Switch, switch expect the ack from CWM. If it is lost then Switch sends the same message again. But CWM expect the next. So CWM will send a negative ack (NACK) to the Switch. Then switch will reset and send the correct message.

ftp-file-size-mismatch

info

cwmftpd

node_ip

FTP Remote and local file size mismatch

tftp-transfer-fail

info

tftpd

node_ip

 

upload-file-error

critical

ooemc/emc

node_id

A file has errors in the data contents. This error could be checksum error, file open error.

minus2-trap

warning

ooemc/emc

node_id

-2 trap received will trigger node resync of the node which reported in the -2 trap

card-lost-trap

warning

ooemc

node_id, slot

60900 trap means controller module or service module lost trap, and it will trigger the card resync of the service module, or node resync of the controller module.

snmp-retry-exceeded

critical

ooemc/emc

node_id

snmp operation retry exceeded the max retry number will cause the operation failed. If the snmp operation is for config upload, then it would cause the node resync failed or partial completed

ftp-retry-exceeded

critical

ooemc/emc

node_id

ftp/tftp operation is for config upload. If ftp/trtp retry exceeded the maximum retry number, the config upload file will not be available to EM. This could cause the resync to fail or cause the resync to only partially complete.

syncup-failed

warning

ooemc/emc

node_id

Reported when ooemc/emc fails to syncup with a card or node.

stats-file-error

critical

statsparser

node_id

The statistics file has errors in the data contents. This error could be checksum error, file open error, file format error.

stats-file-transfer-error

critical

statscollsvr

node_id

Stats file that cannot be collection from switch due to reasons like reachability, timeout, timesync, etc

snmp-throttle-error

info

snmpcomm

node_ip

Reported when throttling limits (for GET/SET requests) for a node is reached

backoff-failed

warning

cmgrd

node_ip

Backoff failed for end points


cwmfrNetworkTimeoutError Events (trap# 28103)

Error Code
Severity
Reported By
Parameters
Description

ftp-session-timeout

info

cwmftpd

node_ip

 

ftp-transfer-timeout

info

cwmftpd

node_ip

 

tftp-transfer-timeout

info

tftpmgr

node_ip

Reported when a tftp operation times out

snmp-timeout

info

snmpcomm

node_ip

Reported when a node times out on a SNMP request


cwmfrNetworkConfigurationError Events (trap# 28104)

Error Code
Severity
Reported By
Parameters
Description

invalid-network-conf

critical

topod

   

duplicate-node-name

critical

topod

node_id, node_ip

 

duplicate-ip-addr

critical

topod

node_id, node_ip

 

duplicate-trunks

warning

topod

node_id, node_ip

 

invalid

warning

topod

node_id

 

CWM Internal Events

cwmfrWatchdogError (trap#28201)

Error Code
Severity
 
Parameters
Description

process-restarting

critical

 

process name

Reported when watchdog has to restart a process which may have exited

giveup-process-restart

critical

 

process name

Reported when watchdog cannot successfully start a process even after the configurable number of retries(default:5)


cwmfrGatewayStatus (trap#28202)

Status Code
Severity
 
Parameters
Description

primary-disconnected

info

 

CWM station name

Reported when a secondary CWM detects a disconnect from the primary CWM

secondary-disconnected

info

 

CWM station name

Reported when a primary CWM detects a disconnect from one of its secondary CWMs

primary-reconnected

info

 

CWM station name

Reported when secondary CWM is able to successfully communicate with primary CWM

secondary-reconnected

info

 

CWM station name

Reported when primary CWM is able to successfully communicate with secondary CWMs


cwmfrCwmInternalError (trap#28203)

Error Code
Severity
Reported By
Parameters
Description

unknown-error

critical

-

process name, description

The process has critical internal error which will cause the logic of the resync

initialization-error

critical

all processes

process name, description

Reported when the process is unable to initialize itself or one of its subsystems.

spawn-child-error

critical

emd/emsd

process name, description

Reported when a daemon process is unable to spawn a child.

configuration-error

critical

all processes

process name, description

Reported when a process detects configuration error.

communication-error-ilog

critical

emc/ooemc

process name, description

Ilog communication fails.

communication-error-shared-mem

critical

emc/ooemc/emsc

process name, description

Shared memory write/read error.

communication-error-corba

critical

-

process name, description

 

tftpmgr-queue-full

info

tftpmgr

process name, description

Reported by tftpmgr process to indicate that maximum number of tftp sessions are in progress and it can not take any more requests for now, as its internal queue is full.


cwmfrCwmDatabaseError(trap#28204)

Error Code
Severity
Reported By
Parameters
Description

unknown

critical

-

process name, sql statement

all other db errors.

initialization-error

critical

-

process name, sql statement

when db connect fails.

insert

critical

-

process name, sql statement

 

update

critical

-

process name, sql statement

 

delete

critical

-

process name, sql statement

 

select

critical

-

process name, sql statement

 

System Events (cwmfrCwmSystemError trap#28301)

#
Event Code
Severity
Reported by
Parameters
Description
(as in the trap & log)

1

disk-space-low / disk-space-normal

warning/info

svmond

utilization%

Reported when the disk space (under /usr/users/) has reached threshold limits (default is 85%)

( 583) 22:19:56 : [svmond] <WARNING> disk space low, utilization is 78, free Mbyte 650

( 583) 22:21:26 : [svmond] <INFO> disk space normal, utilization is 27, free Mbyte 2197

2

db-space-low / db-space-normal

warning/info

svmond

free%

Reported when informix db space (as reported by onstat -d ) has reached threshold limits (default is 85%)

( 583) 22:19:56 : [svmond] <WARNING> DB space low, free percent 68

( 583) 22:21:26 : [svmond] <INFO> DB space normal, free percent 32

3

swap-space-low / swap-space-normal

warning/info

svmond

utilization%

Reported when the swap space usage in the system (RAM+swap) has reached threshold limits (default is 85%)

( 583) 22:19:56 : [svmond] <WARNING> swap space low, utilization is 62, (in Kb) RAM Total:524288, Free:134712, Swap Total:2445728, Free:1773000

( 583) 22:21:26 : [svmond] <INFO> swap space normal, utilization is 35, (in Kb) RAM Total:524288, Free:287312, Swap Total:2445728, Free:1996470


User Guidelines

This subsection describes guidelines of user actions in response to the events.

Network Interface Events

#
Event
Guideline

1

snmp-throttle-error

A throttle error means that CWM is generating too many SNMP requests for that particular node. Make sure that there are not too many provisioning requests for this node. Also make sure that the node is not generating too many alarms

2

snmp-timeout

A SNMP request to this node is timing out. This could happen if the switch is busy or there are too many SNMP requests to the same node (from multiple CWMs). Make sure that there are not too many provisioning requests for this node. Also make sure that the node is not generating too many alarms.

3

tftp-transfer-timeout

In case of TFTP operation time out, it is recommended to try out tftp PUT/GET from command line on CWM workstation and see if it times out. If yes then there could be some network latency issues. If it does not time out from command line then try tuning the value of PerPacketTimePeriod in tftpmgr.config

15

backoff-failed

Please check the health of the node identified in the error message and remove the reported dangling incomplete segments resulted from the backoff failure

16

sa-timeout

Please check the health of the node reported in the error message

17

upload-file-error

please check the health of the node or the switch platform software for the cause of file corruption. One possible case is that the file has checksum error.

18

minus2-trap

please check the health of the node, node resync will be scheduled to make the data in DB synchronize with the switch again.

19

card-loss-trap

please check the health of the node, The service module lose traps, a card resync will be scheduled to make the data in DB synchronize with that card again.

20

snmp-retry-exceeded

The snmp retry failed after the maximum retry number.

case 1: If the snmp operation related to config upload mechanism, please check the mode of the node table to find out any node is in mode 4 or mode 5. Basically, the health of the node should be investigated in terms of the snmp traffic. To recover from this problem, please do nodeResync for the node in mode 5 or mode 4.

case 2: If this snmp operation is only to handle traps, the failure of snmp upload will cause the data in DB not consistent with the switch. THe periodic resync will correct this problem automatically. However, if users need this data be corrected at once, nodeResync can make this happen for you.

21

ft-retry-exceeded

The FTP/TFTP file upload retry failed after the maximum retry number.

The FTP/TFTP related to config upload mechanism, please check the mode of the node table to find out any node is in mode 4 or mode 5. Basically, the health of the node should be investigated in terms of the FTP/TFTP traffic. To recover from this problem, please do nodeResync for the node in mode 5 or mode 4.

22

net-link0-down

Make sure that the LAN ip address of the node is reachable from CWM Work station

23

net-link1-down

Make sure that the network ip address of the node is reachable from CWM Work station

24

no-net-partition

Stop the core specify the Gateway node in the network.conf file. Restart the core

25

no-net-revision

None. CWM will automatically recover, however syncup time might be delayed.

26

no-node-subscription

None. CWM will automatically recover, however syncup time might be delayed.

27

incorrect-message

None. CWM will automatically recover, however syncup time might be delayed.

28

file-parsing-error

Stats Parser sends this message if it is unable to parse Stats File obtained from the switch. Failure to parse can be check sum error, file opening error, file format error.

29

file-collection-error

Scm Control Server sends this message if file collection fails from switch.


CWM Internal Events

#
Event
Guideline

1

communication-error*

The CWM processes have communication problem. This will most likely be because of protocol mismatch or shared memory sizes. Coldstarting CWM could correct this error.

2

unknown-error

If this error happens, the node syncup could be failed or partial completed. Periodic resync could recover from this problem.But if users don't want to wait, do nodeResync can also correct his problem.

3

syncup-failed

The syncup of the node is either failed or partial completed. Periodic resync could recover from this problem.But if users don't want to wait, do nodeResync can also correct his problem.

4

spawn-child-error

Check system resources of the CWM workstation and whether the installation is completed.

5

initialization-error

Check system resources of the CWM workstation and whether the installation is completed.

7

database errors

Check for DB space and try executing the SQL from the command line.

9

tftpmgr-queue-full

This is not a cause of major concern, Application will retry.

10

restarting-process

Watchdog is restarting a failed CWM process. CWM may not function properly during the failure of the process.

11

giveup-process-restart

Watchdog no longer tries to restart a process due to repeated failed attempts. CWM will not function properly with missing processes.

12

primary-disconnected

If there are more than 2 CWMs in operation, the SP1 will automatically switchover to be the new Primary. If there are only 2 CWM in operation, then the user needs to do ForceSwitchOverOnSecondary if the user wants to continue doing user-data provisioning from the Secondary.

13

secondary-disconnected

If there are more than 2 CWMs in operation the Primary has disconnected with ALL Secondaries, the Primary will demote itself to a Secondary, assuming the SP1 will automatically switch over to the new Primary.

14

primary-reconnected

The connectivity to the disconnected Primary is resumed.

15

secondary-reconnected

The connectivity to the disconnected Secondary is resumed.


System Events

#
Event
Guideline

1

disk-space-low

Cleanup old log files (under /usr/users/svplus/log/) to recover disk space. This is critical since CWM may not log after the /usr/users disk space becomes full.

2

db-space-low

run onmode -F. If it still does not help, stop CWM, add raw partition and restart system.

3

swap-space-low

Add more swap space (at least another 1GB) under a file system other than /usr/users


Channelized CESM-8T1 and CESM-8E1 End Point Support

This feature adds support for adding, modifying, and/or deleting connections between channelized CESM-8T1 and CESM-8E1 end points using either the Connection Manager GUI or the SNMP Service Agent. When using this feature the port speeds and number of DS0 available will be the same on the ports on both ends.

Client Primary to Secondary Switch Over Notification

CWM 11.0.10 patch 1 provides notification to clients (in the form of a pop-up window) when a primary to secondary switch over has occurred.

Client Logged-in Server Description Support

The client window description bar now includes a description of which CWM server the client is logged into.

Addition of CiscoView to the Security Manager module

The Security Manager provides controlled access to multiple users of Cisco WAN Manager (CWM), based on the user's UNIX User ID and password. CWM 11.0.10 patch 1 adds support for controlled access to CiscoView operations through the Security Manager. Refer to Chapter 6 of the Cisco WAN Manager User Guide for general instructions on how to configure and use the Security Manager.

Addition of Support for PXM-UI-S3 Secondary BITS Clocking

The PXM-UI-S3 back card, which provides Stratum level 3 clock source inputs, has been enhanced to accept two external BITS clock inputs. A new interface, 7.36, has been added to support one more external clock input. CWM now recognizes and supports interface 7.36 (the second BITS clock input of the PXM-UI-S3 back card). The properties and use of this newly added interface is exactly the same as that of interface 7.35, which refers to the first BITS clock input of the PXM-UI-S3 back card. The second BITS clock source can be added as primary, secondary or tertiary clock source, which is the same for any other clock interface.

Features Introduced in CWM Release 11.0.10

The following new features and enhancements have been introduced in CWM 11.0.10:

Improvement to Percent Utilization settings for PXM45-based MGX switches

CWM 11.0.10 adds a configuration parameter in /usr/users/svplus/cmgrd.conf called PNNI_PER_UTIL_FLAG. If this flag is set to DISABLE, then CWM will not set %util on all PNNI endpoints, hence defaulting them to 100%. Also whenever %util is to be mapped from a PNNI endpoint for a hybrid or XPVC connection, the %util from the PNNI endpoint will be ignored and the %util will be taken from the other end of the connection. If the flag is ENABLE, then CWM behavior will be to set the %util as it is doing today and also map the %util from the PNNI end wherever applicable. The default is ENABLE.

Improvements to the Robust Trap Manager (RTM)

A ping mechanism has been added to RTM. The PingEnable flag in the /usr/users/svplus/conf/rtm.conf file must to be set to 1 before using the ping mechanism in RTM.

New Java Client Software, using Java Network Launching Protocol (JNLP)

It is no longer necessary to install the CWM client software from the distribution CD. CWM 12.0.00 client software can be deployed directly from the CWM server. Refer to the CWM Installation Guide for Solaris 8, Release 12 (78-14974-01) for more details.

Security Banner Feature

CWM 11.0.10 adds a blank, customizable field in the CWM login screen that allows you to set up a customized security message that displays upon first logging in to Cisco WAN Manager.

The Banner Field is editable with administrator privileges.

The Banner Field window displays a fixed 4 lines of text. If the text exceeds 4 lines, a field scroll bar appears.

The Banner Field text is stored in a securitybanner.conf file and only the administrator has write privileges.

CiscoView 5.4.1

CWM 11.0.10 uses CiscoView 5.4.1. CWM 11.0.00 used CiscoView 5.3. CV 5.4.1 is the latest release of CiscoView and delivers significant performance improvements with faster GUI response and more efficient SNMP handling.

Java Client

CWM 11.0.10 includes a Client application designed to run on a Windows 2000 PC. CWM Java Client will install from the CWM Workstation and will run as a java applet. It will operate all of the CWM functionality with the exception of Motif applications. Wingz and Summary Reports remain as Motif applications and are not available from the Client. To run Wingz or Summary Reports either telnet to the CWM Workstation or run directly from CWM.

CWM Support for Connection Trace

In CWM 11.0.00, Connection Trace was not supported for MGX 8850 routing nodes. In CWM 11.0.10, Connection Trace is supported for all service modules on routing nodes including:

AUSM-8 (PXM1-E only)

FRSM-8 (PXM1-E only)

CESM-8 (PXM1-E only)

RPM-PR (both PXM1-E and PXM45)

VISM-PR (both PXM1-E and PXM45)

FRSM-12-T3E3 (PXM 45 only)

Connection trace should always be done on the Master end of the connection.

CWM Support for MGX 8950

In addition to previous MGX 8950 support, CWM 11.0.10 supports the RPM-XF high-density routing module.

PXM1-E and AXSM-E: T1E1 IMA trunking

CWM 11.0.10 supports the PXM1-E and AXSM-E T1/E1 IMA introduced in MGX 3.0.10. CWM support includes:

Trunks between all PNNI routing nodes (PXM1-E, PXM 45, BPX-SES)

CiscoView IMA Link and IMA Group Provisioning

Event Management and RTM support

Topology/Network Browser View

IMA Trunk Statistics

SRM-E APS

CWM 11.0.10 provides CiscoView configuration for SRM-E APS. CWM recognizes APS traps and flows-through RTM to Service Agent.

SRM-E APS support is in the MGX 8850 with PXM 45.

AXSM-E Double Density

CWM 11.0.10 supports the AXSM-E card with a second backcard. Prior to CWM 11.0.10, only one back card was recognized.

Persistent Topology for MGX 8230/8250/8850 Feeder Nodes

In prior releases, when a MGX feeder node became unreachable and CWM was restarted, the unreachable MGX did not appear in CWM Topology. In CWM 11.0.00, node persistency was added for MGX 8850 routing nodes and in CWM 11.0.10 this capability is extended to include MGX feeder nodes. When CWM is restarted, the unreachable feeder node remains in the network topology and is indicated in CWM Topology as an unreachable, grey state. The Node Persistency feature provides increased reliability in the event of double failures of a MGX 8230/8250/8850 feeder nodes and applies to MGX 8230/8250/8850 feeder nodes. In CWM 11.0.10 there is no support for persistency of links.

Support for Read-Only Operations in the Audit Trail Application

Audit Trail support for the Connection Manager and Config Save/Restore modules is extended to include Read-Only operations in CWM 11.0.10. The Audit Trail application monitors CWM user activity and logs to a file all read, create, modify and delete activity in CMGUI and Config Save/Restore modules. The log includes user, action and time and date. Also includes file archival and retrieval features. CWM Audit Trail improves operations accessibility and scalability through improved security of the management network. Audit Trail applies to CMGUI and Config Save/Restore modules, but Audit Trail does not log for any other CWM modules, add-on modules or CiscoView.

WANDEST 2.3

WANDEST version 2.3 introduces an automation feature that provides the ability to configure and activate automated upload requests from the WANDEST client that will occur at a configurable upload interval.

The new Automation feature allows a WANDEST client to issue upload requests to the WANDEST server, automatically at a set interval. The setup of the automated upload requests, including the configuration of the upload interval, are configured using the AUTO command, issued from the WDADMIN program.

Syntax:

AUTO grp<m>int <n> SEQ1<n> SEQ2<n>

Descriptions of each parameter follow:

GROUP - Same definition as in the FULL or INCR command.

INTERVAL - The time interval between the two consecutive automatic uploads, in seconds.

SEQ1 - The sequence number has the same definition as in the FULL or INCR command. SEQ1 and SEQ2 provides 2 alternating sequence number for the automatic uploads.

SEQ2 - The sequence number has the same definition as in the FULL or INCR command.


Note Because there are 2 alternating sequence numbers, only the 2 latest uploads are kept and any previous uploads will be overwritten.


To stop the automation feature, exit the WANDEST WDADMIN utility by executing the quit command. Refer to the WANDEST Installation and Reference, Part number DOC-7814109=.

Support for Filtered Alarms

In previous CWM releases, the node alarm that displayed on CWM Network Topology GUI (the node shelf integration alarm) was comprised of the aggregated alarm of all slot/line/port/connection alarms in that node. However, some customers prefer to see a "filtered" integrated shelf alarm which ignores all lines, ports, connections and feeder alarms so that the highest level of alarm could not be triggered by a line.

The Filtered Alarm feature also provides the ability to have the feeder trunks' alarm reported as part of their parent routing nodes' aggregated alarm.

Also, when a few routing nodes are grouped into a group, the Filtered Alarm feature also provides the ability to have the alarm of the routing trunks which connect the grouped nodes reported as part of group aggregation alarm.

Java GUIs for Config/Save/Restore and Image Download

Within the Select a file to Download or Restore windows there is a field for User ID and Password. The Save and Restore buttons will remain greyed out (unselectable) until a User ID and Password is entered. The PXM1-based switches (MGX 8230, MGX 8250, and PXM1-based MGX 8850) use tftp for uploading and downloading configurations. You can enter any username or password in these fields and the Save and Restore buttons will be active.

When you are using the Config/Save/Restore GUI to manage configuration files for any non-PXM1-based switches, you will be required to enter a valid User ID and Password.

Persistent Topology

In CWM 11, MGX nodes are stored persistently in the CWM database and network gateway node. Therefore, when CWM is restarted, the unreachable node remains in the network topology and is indicated in CWM Topology as an unreachable, grey state.

Support for 100K SPVC per node

Audit Trail

Monitors CWM user activity and logs to a file all create, modify and delete activity in the Connection Manager and Config Save/Restore modules. The log includes user, action and time and date.

An administrator uses security manager to select "Read-Audit" and/or "Write-Audit" in the user profile. The next time a user assigned to that profile logs in, an audit log will be created. This is fixed in the Release 12 User's Guide.

Connection Management GUI support for XPVCs

Configurable Service Class Templates

This feature provides the ability to modify a Service Class Template and reuse the SCT ID number. Configurable SCTs apply to the AXSM, AXSM/B, AXSM-E, FRSM12-T3E3 and PXM1-E cards. Configurable SCTs are available for MGX 8850 and MGX 8950, but not for AXSM-E on the MGX 8950.

Support for Release 3 of the MGX 8950

CWM 11 provides GUI, Service Agent and Statistics support for Release 3 of the PXM45-based MGX 8950 platform in much the same way as Release 3 of the PXM45-based MGX 8850.

Support for Release 3 of the PXM45-based MGX 8850

With Release 3 of the PXM45-based MGX 8850, CWM 11 supports the following new broadband service modules:

FRSM12-T3E3 high-speed frame relay

RPM-XF high density routing module

AXSM-E

Support for the PXM 1E

Support for V.35 and X.21 on HS2/B for MGX PXM1 and PXM1E

Support for 2-T3E3/B backcard for HS2/B

Support for SRM-E

Support for all cell bus cards on PXM1E: AUSM, FRSM, RPM, VHS, (SPVC Only)

GUI, Service Agent and Statistics support for BPX 8600 and IGX 8400 9.3.40 policing enhancements.

New Features and Enhancements from CWM Release 10.4.10 Patch 4 Incorporated into CWM 11.0.10 Patch 1

The following enhancement has been added in the 10.4.10 Patch 4 Release of CWM:

CWM Auto-Restart

This option automatically starts the CWM core after a reboot.

Configuring Auto-Restart


Step 1 Login to the CWM workstation as user root

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 with the following 2 lines:

#!/bin/csh 
su - svplus -c /usr/users/svplus/scripts/start_SV+ & 

For example: Script name - S99init_sv

Step 4 Provide execute permissions for /etc/rc3.d/Snn<fil ename>:

# chmod 755 S99init_sv 


Note As part of CWM installation, to auto restart informix after reboot, similar script is created /etc/rc3.d/S98init_db. You need to make sure that, for the above script - Snn<filename>, 'nn' should be greater than 98 and should not have the same number as other files in /etc/rc3.d.


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


New Features and Enhancements from CWM Release 10.5.10 Patch 3 Incorporated into CWM 11.0.10

The following new features and enhancements have been added in CWM 11.0.10 with the incorporation of CWM Release 10.5.10 Patch 3 features:

Conversion of KBPS to CPS in Connection Manager

To resolve issue CSCdx29985, Patch 3 of CWM 10.5.10 adds a toggle checkbox to the Options pulldown in the Connection Manager that is used for converting CPS values to KBPS value or vice versa. The default is unchecked (display as CPS). Any changes in the "Show CPS parameters in Kbps" checkbox will be reflected in all the Connection Manager GUI sessions opened after changing the toggle. Any connection addition/modification screens opened prior to changing the toggle must be closed and reopened to reflect the change in units calculation. This feature is useful especially when the traffic parameters in the Connection Manager GUI are shown in different units for local and remote endpoints. An example would be an ATM-FR connection, wherein the ATM traffic parameters are displayed in units of CPS (cells per second) and the frame relay parameters are displayed in KBPS (or BPS).

New Features and Enhancements from CWM Release 10.5.10 Patch 2 Incorporated into CWM 11.0.10

The following new features and enhancements have been added in CWM 11.0.10 with the incorporation of CWM Release 10.5.10 Patch 2 features:

Connection Segment Loopback Test and Connection Loopback Test for PVC

BPX already uses the CLI to initiate a Connection Loopback Test using the testpingoam command. This test can be initiated at the egress endpoint of a connection in a BPX network. The assumption is that the egress endpoint is connected finally to a remote end CPE. In CWM 10.5.10 patch 2, the CWM Service Agent and Connection Management GUI now provide the support for this testpingoam option. When this test is applied to the connection endpoint on a BXM service module, it initiates an end-to-end ATM loopback cell that traverses through the intermediate switches to reach the CPE endpoint and send back to the originating BXM port.

In addition, CWM 10.5.10 patch 2 also supports the enhanced Connection Segment Loopback test (tstconseg) on BPX. This test uses segment loopback cell which is returned by the first segment end point in the connection. This is useful for isolating the fault in case the end-to-end Loopback test fails. With enhancement in BXM firmware MFN and BPX 9.3.30 or newer version, the successful Connection Segment Loopback test result will also include the round trip delay measurement.

Limitation: The CPE is assumed to be able to recognize and return the end-to-end loopback cell back into the network.

Egress Queue Selection for FRSM-8

The Connection Management GUI provides an Egress Queue Parameter option under the Edit menu to allow the user to override the selection of egress queue. By default, the egress queue is set to high priority for cbr, vbr2-rt and vbr3-rt service types, and low priority for abr, ubr, abrstd, vbr2-nrt and vbr3-nrt. This egress queue user selection can be applied to FR-FR, FR-ATM and FR-RPM connection type.

Limitation: The FRSM-8 firmware must be at version 10.0.20 or newer.

Displaying Master Endpoint as Local Endpoint in Connection Manager GUI

In the Connection Manager GUI, after selecting a node or a port, the user is given a set of options to decide what connections are retrieved and displayed in a table. 10.5.10 patch 2 provides an additional option called "Set Master as Local" to toggle between listing the connection master end points or the endpoints of the selected port as the endpoints in Local Endpoint Column. Once this selection is made, it stays in memory until the user changes it again or until the Connection Manager GUI is closed and reopened.

Access Control Privilege for Deleting Multiple Connections

The Security Manager provides a finer granularity of access control to connection deletion. The User Security Administrator can configure a CWM user to have the privilege of deleting a single connection at a time only or the privilege to delete a single or multiple connections in one operation.

Enhanced Node Reachability Monitoring

Instead of using just a repeated SNMP timeout, CWM is enhanced to use also the lower level IP ping to detect any Node Un-reachability condition. By doing this, the Network Topology GUI reflects such condition in about 30 seconds if a failure of the IP connectivity to the node is concluded. The number of retries and the periodic ping cycle time are configurable using configuration data file.

Limitation: The SNMP timeout is the only way to detect SNMP application layer failure. Such failures are reported within 9 minutes as before.

Setting Default Values for Filters in Connection Manager GUI

The Filter Settings in the Connection Manager GUI (invoked via Edit->Filters) now includes a "Defaults" button to reset the default values of all check boxes. The default Filter Settings value is all check boxes selected and the descriptor field cleared. This provides an alternative to the "Reset All" button which resets to the previously saved settings.

AUSM Egress Counters

Support has been added for the following AUSM Egress Counters:

Total Cells Tx to Line

Total Cells Tx to Line w/CLP set

Discard Qfull Tx Port

Discard CLPth Tx Port

Total No. of Cells Tx to N/W

Total No. of Cells Tx to N/W with CLP set

Discard Qfull Rx Port

Discard CLPth Rx Port

Total Cells Rx from Network

New Features and Enhancements in WANCV Release 4.11

As part of Cisco WAN Manager Release 11, the CiscoView MSSBU device packages (WANCV) were upgraded to Release 4.11 to support CiscoView 5.4.1.

The following features were introduced with Release 4.11:

Improved error handling for MGX 8850 devices

performance improvements

Features Not Supported in WANCV Release 4.11

The following features are not supported in WANCV 4.11:

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

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

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

No on-line help text is available at this time.

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

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

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

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

Features Not Supported and Known Feature Limitations in 11.0.10

The following features are not supported in CWM 11:

XPVC Connections for VISM/VISM-PR are not supported

Support of MGX 8850 2.1.60 and SES 1.1.60 PNNI Multi-peer group configuration

MGX 8850 Release 2.1.60 and SES Release 1.1.60 supports UNI 4.0 ATM interface, PNNI Multi-peer group, and AINI as an alternative to Multi-peer group. CWM 11 supports the configuration of the UNI 4.0 ATM interface and AINI, however, the configuration of PNNI Multi-peer group is supported only through the Switch Software CLI.

Support of BPX 9.3.30 Switch Software features other than Enhanced NNI and XPVC/XPVP provisioning

BPX 9.3.30 Switch Software is required for the Enhanced NNI and XPVC/XPVP Provisioning features. Other new features added to BPX 9.3.30 Switch Software are supported only at the Switch CLI.

CWM does not support the URM card on the IGX.

CWM does not support 800 part numbers

Voice connections using G729 and G729A are not supported from the Connection Manager and the Service Agent.

Co-Existence with CiscoWorks 2000 has not been tested.

Standalone MGX 8850 PXM1-based and PXM45-based nodes must be configured as MGX 8850 within the network configurator, and standalone MGX 8250 nodes must be configured as MGX 8250. If you mix up the node type (i.e., configure a standalone MGX 8850 PXM45-based node as MGX 8250), your standalone node will not appear on the Topology map.

The files in the log are not sorted by name in the SCM main window.

Alarm status may be inconsistent in the Connection Manager.

This limitation refers to DAX connections on MGX 1 nodes. When a DAX connection on an MGX 1 node goes to failed state the abit status displayed on the connection manager for this particular connection always stays "ok"

BXM to AXSM connections (on a BPX without SES) are not supported in the Connection Manager. BXM on the BPX SES to AXSM connections are supported in the Connection Manager.

You should not start provisioning ports or connections prior to CWM synchronization with the network.

If your CWM will be managing a network of MGX 8850 PXM1-based nodes with a large number of connections, you must edit the /usr/users/svplus/config/tftpmgr.config file to set the TimeoutPeriod to 120 (the default is 40). This is necessary for syncing up with the MGX 8850 PXM1-based nodes with a large number of connections. An example of the type of node this applies to would be any node containing FRSM2CT3 cards with 4000 connection end points on three to four slots. If you have > 2000 connections on a card on an MGX (PXM1) shelf, then the tftpmgr.conf parameter needs to be tuned.

The config file format for the NWTopology save feature has changed from prior releases. So, if the /usr/users/svplus/data/NWTopology/ directory already has an old format configuration file (which the new parser will be unable to read), the first time you start NWTopology, a message box will pop up saying that "Config File corrupted, continue..." This is the normal case, ignore this message. Once you save the configuration using the "save" before closing the current NWTopology GUI, the next time you start the GUI, the error message box will not appear.

SCM auto-enable feature is not supported. Statistics must be manually enabled and collection must be manually configured. Please refer to the SCM User Guide for details on enabling and collection procedures.

SCM templates for PXM1E and PXM45-based nodes are not supported during the upgrade to 11 from 10.4.10 and 10.5.10. Refer to the "Saving User-created Statistics Collection Manager Templates before Upgrading" section for more details.

SCM auto-collection feature is not supported. You need to enable statistics first.

SCT only downloads template files from PXM1E and PXM45-based MGX 8850 nodes and supports downloading template files from the following cards: AXSM, AXSME, PXM1E and FRSM12.

SCT does not support template file uploads to BPX-SES nodes.

SCT files cannot be associated if ports have resource partitions enabled, and any ports need to be downed before associating SCT files.

There can only be no more than 255 distinct SCT files in the network. The highest allowable SCT ID is 255. (SCT ID 0 is excluded because its the default SCT).

Occasionally, ILB Warning Messages persist on console screen even after sync up is complete.These are internal communication messages between processes and should be ignored. There is no way to turn this off.

There is potentially some corruption of files created by the FTP process during sync-up. The workaround is to do a manual resync. For more information, refer to CSCdv46195.

There is a possibility of a coredump occurring during FTP sessions when too many files are open. The workaround is to do a manual node resync.

The .rhosts file is overwritten during upgrade process. The installation script that comes with release 11.0.10 CWM has a .rhosts file that replaces the one on the server being upgraded and it only has the (+) sign in it. Save a copy of the file before the start of the upgrade and reload it right after the upgrade is done.

The following error messages may display on the console intermittently after starting the CWM core.

Error:Receives distant call to unknown function. 
Error:Receives distant call to unknown function... 

These messages have no effect on system operation. The same messages are logged in the ilberrors* log files.

Supported Connections

This section lists the connections CWM 11 supports.

Supported Cards

CWM 11 supports the following card types for various connections.

Frame Relay

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

FRSM (4T1,4E1,8T1,8E1), FRSM-HS1b.V35 cards for MGX 8220, and Release 1 of the MGX 8850 (PXM1-based)

FRSM (8T1,8E1) and FRSM-HS2b.V35 and High Speed SCSI cards for Release 3 of the MGX 8850 and MGX 8830 (PXM1E-based)

FRSM12-T3E3 cards for Release 3 of the MGX 8850 (PXM45-based)

UFM, FRM, FRP cards in IGX

CWM 11 supports the following FRSM-VHS cards in Release 1 of the MGX 8850 (PXM1-based) platform:

FRSM-2CT3

FRSM-2T3

FRSM-2E3

FRSM-2HS2

ATM Service Modules

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

AUSM (4T1, 4E1) in MGX8220

AUSM (8T1, 8E1) in MGX 8220 and Release 1 of the MGX 8850 (PXM1-based).

These cards support both ATM as well as IM-ATM ports.

AUSM (8T1, 8E1) in Release 3 of MGX 8830, MGX8850 (PXM1E-based)

PXM card in MGX 8850, Release 1.

AXSM card in MGX 8850, Release 3.

ASI, ASI-155, BXM, BXM-E cards in BPX.

UXM cards in IGX.

BME cards in BPX (only card supporting ATM Multicast connections)

RPM-B service module card in Release 1 of the MGX 8850 (unicast connections)

RPM-PR service module card in Release 1 of the PXM1-based MGX family (8230, 8250, 8850), Release 3 of the PXM1E-based MGX family (8830, 8850), and Release 3 of the PXM45-based MGX 8850 RPM-XF in Release 3 of MGX 8850 and MGX 8950

Circuit Emulation (CE) Service Modules

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

CESM-4T1, CESM-4E1: MGX 8220 only

CESM-8T1, CESM-8E1: Release 1 of the PXM1-based MGX family (8230, 8250, 8850), Release 3 of the PXM1E-based MGX family (8830, 8850), and the MGX 8220

CESM-T3, CESM-E3: Release 1 of the PXM1-based MGX family (8230, 8250, 8850) and Release 3 of the PXM1E-based MGX family (8830, 8850)

Voice Service Modules

CWM 11 supports the following types of Voice Service Modules:

VISM 2.1 and 2.2: Release 1 of the PXM1-based MGX family (8230, 8250, 8850) (PRI- Backhaul, VISM - AUSM Connection Management)

VISM-PR 3.1: Release 1 of the PXM1-based MGX family (8230, 8250, 8850), Release 3 of the PXM1E-based MGX family (8830, 8850), and Release 3 of the PXM45-based MGX 8850

CVM, UVM: IGX

Data Service Modules

CWM 11 supports the following types of Data Service Modules:

HDM, LDM, UVM, CVM: IGX

PVC Connections Supported by CWM 11

The following table lists the connection types support for PVC connections. The table gives the connection type followed by Local and Remote EndPoint Card Type. The Local and Remote Endpoints can be reversed and the same rules and restrictions apply. All these cards should be on a Auto Route Platform namely BPX, IGX, MGX 8220, MGX 8850/8250/8230 Release 1

Table 6 lists the PVC connection types supported by CWM 11.

Table 6 PVC Connections Supported by CWM 11 

Connection
CWM Service
Local Endpoint
Card Type
Remote Endpoint Card Type
Comments or Restrictions

FR-FR

with Foresight

FR

FR

no QOS support

FR-FR

with Foresight

FRQOS

FR, FRQOS

QOS can be specified by ChanServType and it has to be abr (4).

FR-FR

without Foresight

FR

FR

no QOS support

FR-FR

without Foresight

FRQOS

FR,
FRQOS

Following QOS specified by `ChanServType' attribute

hi_priority, ubr, nrt-vbr, rt-vbr, stdabr

ATM-FR

nrt-vbr3,abr.fs

ATM

FR

no QOS support on FR endpoint;

ATM-FR

cbr1,

ubr(1,2),

nrt-vbr(2,3),

rt-vbr(2,3)

abr.fs,

abr.1

ubr(1,2)

ATM

FRQOS

QOS supported on FR endpoint, QOS chosen by CWM automatically based on Service.

Some ATM endpoints may not support all service types. Look below in Table 7 for the Service type restrictions on ATM endpoints

RPM-FR

nrt-vbr3

RPM

FR

no QOS support on FR endpoint

RPM-FR

nrt-vbr3, ubr1, abr1

RPM

FRQOS

QOS supported on FR endpoint; QOS chosen by CWM automatically based on Service.

ATM-ATM

cbr1,
nrt-vbr(1,2,3),

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

ATM

ATM

Both ATM endpoints must support the Service. Look below in Table 7 for the Service type restrictions on ATM endpoints

RPM-RPM

nrt-vbr3,

abr1,

ubr1

RPM

RPM

 

ATM-RPM

nrt-vbr3,

abr1,

ubr1

ATM

RPM

 

ATM-ATM

atfst

BXM/BXM-E/UXM

BXM/BXM-E/UXM

 

ATM-FR

atfst

BXM/BXM-E/UXM

FR, FRQOS

 

ATM-FR

atftfst, atfxfst

BXM/BXM-E/UXM

UFM

UFM card must be on a routing IGX node.

ATM-ATM

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

ATM-Multicast

ATM-Multicast

multicast connection;
local and remote port combinations: root-leaf

CE-CE

cbr1

CE

CE

Structured/unstructured;

both endpoints must be either structured or unstructured with matching bandwidth

ATM-CE

cbr1

ATM

CE

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

Data-Data

data

DATA

DATA

The data service modules are listed in section above

Voice-Voice

voice

VOICE

VOICE

All voice service modules listed in above section except VISM are supported for this connection type.

ATM-VISM

cbr1,
nrt-vbr(1,2,3),

rt-vbr(1,2,3)

ATM

VISM

Some VISM and ATM endpoints may not support all Service types. Look below in Table 7 for the Service type restrictions on ATM and VISM endpoints

VISM-VISM

cbr1,
nrt-vbr(1,2,3),

rt-vbr(1,2,3)

VISM

VISM

Some VISM endpoints do not support all Service Types. Look below in Table 7 for service type restrictions on VISM

VISM-RPM

nrt-vbr3

VISM

VISM

Some VISM endpoints do not support all Service Types. Look below in Table 7 for service type restrictions on VISM


Table 7 lists the cards that belong to the various groups like ATM, FRQOS etc that are referred in Table 6.

Table 7 Card Types 

Card Group
Cards on Auto Route Platform

FR

FRSM(4T1,4E1, HS1b.V35), FRSM 8T1/E1 with Release < 10.0.20
FRM, UFM, FRP

FRQOS

FRSM(2CT3,2E3,2T3,HS2), FRSM 8T1/8E1 with Release >=10.0.20

Channel Service Type Restrictions:

. stdabr is supported on FRSM-VHS (2CT3, 2E3, T3, HS2) cards only from version 10.2.01

ATM

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

PXM1
ASI, ASI-155,
BXM,
BXM-E,
UXM

Service Type Restrictions:

rt-vbr support is present only in AUSM-8T1/E1 from version 10.0.20, no other AUSM card supports it.

abr.fs is not supported on PXM1 card

rt-vbr is not supported on ASI, ASI-155 cards

abr-fs from ASI family (ASI,BXM,UXM) to FRP family (FRP.FRM.UFM) will map to atfst service type.

ATM-Multicast

BME

CE

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

RPM

RPMB, RPM-PR

VISM

VISM, VISM-PR

Service Type Restrictions:

. rt-vbr2, rt-vbr3, nrt-vbr2, nrt-vbr3 service types are not supported for VISM cards less than 3.0 version

VOICE

CVM, UVM, CDP

DATA

CVM,
UVM,
HDM,
LDM,
SDP,
LDP


SPVC Connections Supported by CWM 11

The following table lists the connection types support for SPVC connections. The table gives the connection type followed by Local and Remote EndPoint Card Type.The Local and Remote Endpoints can be reversed and the same rules and restrictions apply. All these cards should be on a PNNI Platform namely BPX with SES, MGX 8850 Release 2 and 3, MGX 8950, MGX 8830 Release 3

Table 8 lists the connection types for SPVC supported by CWM 11

Table 8 SPVC Connections Supported by CWM 11 

Connection
CWM Service
Local Endpoint
Card Type
Remote Endpoint Card Type
Comments or Restrictions

FR-FR

Without Foresight

FR

FR

No foresight support on PNNI;

chanServType on FR end can be chosen to be one of

high_priority, nrt-vbr, rt-vbr, ubr and stdabr

ATM-FR

cbr1,
nrt-vbr(2,3),

rt-vbr(2,3)
ubr(1,2),
abr.1

ATM

FR

Look below in Table 9 for restrictions on service types for FR endpoints and Internal and External VSVD on ATM endpoints

RPM-FR

nrt-vbr3,

rt-vbr3

ubr1,

abr1

RPM

FR

Some RPM endpoints may not support all of these Service Types. Look in Table 9 for Service Type restrictions on RPM endpoints.

ATM-ATM

cbr1,
nrt-vbr(1,2,3),

rt-vbr(1,2,3)
ubr(1,2),
abr.1

ATM

ATM

Look below in Table 9 for restrictions on Internal and External VSVD on ATM AXSM endpoints

ATM-RPM

nrt-vbr3,

rt-vbr3,

abr-1,

ubr-1

ATM

RPM

Some RPM endpoints may not support all of these Service Types. Look in Table 9 for Service Type restrictions on RPM endpoints.

RPM-RPM

nrt-vbr3,

rt-vbr3,

abr1,

ubr1

RPM

RPM

Some RPM endpoints may not support all of these Service Types. Look in Table 9 for Service Type restrictions on RPM endpoints

CE-CE

cbr1

CE

CE

Structured/unstructured;

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

ATM-CE

cbr1

ATM

CE

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

ATM-VISM

cbr1,

nrt-vbr(1,2,3),

rt-vbr(1,2,3)

ATM

VISM

 

VISM-VISM

cbr1,
nrt-vbr(1,2,3),

rt-vbr(1,2,3)

VISM

VISM

 

VISM-RPM

nrt-vbr3,

rt-vbr3

VISM

RPM

Some RPM endpoints may not support all of these Service Types. Look in Table 9 for Service Type restrictions on RPM endpoints.


Table 9 lists the cards that belong to the various card groups that are used in Table 8.

Table 9 Card Types

Card Groups
Cards

ATM

AUSM in PXM1E-based MGX 8850/MGX 8830 switches

AXSM,

AXSM-E,

PXM1E

Service Type Restrictions:

. Internal and External VSVD can be set to enable only on AXSM-E cards for ABR.1 service type

FR

FRSM-12,

FRSM cards on PXM1-E based MGX 8850/MGX 8830

Service Type Restrictions:

. rt-vbr2, nrt-vbr2, ubr2 service types are not supported for FRSM-12 cards

CE

CESM cards on PXM1-E based MGX 8850/MGX8830

RPM

RPM-PR, RPM-XF in MGX 8850 Release 2 and 3 and MGX8830 Release 3 switches

Service Type Restrictions:

. abr-1 is not supported for RPM-XF card.

. vbr3-rt is not supported for RPM-PR card

VISM

VISM, VISM-PR in MGX 8850 Release 3 and MGX 8830 Release 3 switches


HYBRID Connections Supported by CWM 11

The following Hybrid platform combinations are supported (The Local and Remote endpoint of the connection must be within the same network):

Auto Route Feeder on PNNI -> PNNI or

PNNI --> Auto Route Feeder on PNNI

Auto Route Feeder on PNNI --> PNNI ---> Auto Route Feeder on PNNI

An intersection of all connection types supported in PVC Table 6 and SPVC Table 8 are supported. The following rules/restrictions apply:

Both endpoints of the Hybrid connection must support the service type. For Auto route endpoints refer to the PVC Table 6 and for PNNI endpoints refer to the SPVC Table 8 for the restrictions.

Since PNNI platform does not support foresight, no foresight service types are supported for two segment Hybrid connections.

XPVC Connections Supported by CWM 11

The following XPVC platform combinations are supported (The Local and Remote Endpoint of the connection must be in different networks separated by at least one XLMI link):

Auto Route --> PNNI ---> Auto Route

Auto Route --> PNNI or

PNNI ---> Auto Route

Auto Route --> Auto Route Feeder on PNNI or

Auto Route Feeder on PNNI --> Auto Route

The Auto Route endpoints can be on a Routing or a Feeder node. An intersection of the connection types supported in PVC Table 6 and SPVC Table 8 are supported. The following additional rules/restrictions apply:

Both endpoints of the XPVC connection must support the service type. For Auto route endpoints refer to the PVC Table 6 and for PNNI endpoints refer to the SPVC Table 8 for the restrictions.

XPVC supports abr.fs connection service types between PNNI endpoints and Auto Route endpoints provided the foresight supported end is in the Auto Route network. This is called a Foresight - ABR interworking connection where there is one congestion control loop which is a foresight loop in the Auto Route network and another congestion control loop which is a ABR loop in the PNNI network. The PNNI network will have the service type configured as ABRSTD with InternalVSVD enabled if applicable.

All cards on IGX and all CESM cards are not supported as XPVC endpoints in this release.

Limitations

CWM can manage up to 40 different disjoint AutoRoute networks, provided all the network elements have unique network IP addresses and unique names across all the networks managed by CWM. There is no such limitation for PXM45 based MGX networks.

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

CWM must be started from a CDE environment.

CWM does not support use of the korn shell.

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

If you use CWM 11.0.10 on a low-end machine to manage mid-range or large-range networks, CWM may take a long time to synchronize with networks that have more than 100K connections. Connection Management and Equipment Management (using CiscoView) may take long time to come up or perform any user-requested functions. You might not be able to invoke multiple desktops from CWM as certified by Cisco for low-end systems with networks that have more than 100K connections.

If you use CWM 11.0.10 on a low-end machine to manage mid-range or large-range networks, CWM may not be able to receive traps generated by the network which might put the CWM database out of sync with the network. The result would be that the information about nodes, trunks, ports, and PVCs may not match with the status on the network.

Notes

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

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

The Connection Manager GUI for preferred route displays all available trunks without considering the traffic class. As a result, it is possible to set a preferred route for a CBR connection traversing trunks that do not support CBR traffic. Even if you set this preferred route through CWM it will be rejected by the switch.

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

RPM on PXM1-based MGX8850/8230/88250 provisioning is done using telnet operation since it does not support SNMP SETs. Please refer to previous release notes for RPM switch CLI notes.

Limitations to Upgrading the Stand-alone SCM

The following six upgrade options are supported for StandAlone SCM:

1. Collection Server to Collection Server

2. Collection Server to Collection Server and Stats Parser

3. StatsParser to StatsParser (preserving the stats data in statsdb is not supported. This database is not used by any application. Please refer to DDTS CSCdx52301 for more details).

4. Collection Server + StatsParser to Collection Server + StatsParser

Issue with CWM 11 Security Manager

Too many concurrent Security Manager GUIs (>15) may have some problems in CWM. In case this problem appears, warm start the core.

HP OpenView

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

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

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

Issues with CWM 11 Statistics Collection Manager

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

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

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

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

Limited Number of Routers

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

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

Ad-Hoc Reports

Wingz occasionally is slow in scrolling. This is due to the amount of process required for the ad-hoc request. There is no loss in data or incorrect data.

These reports can no longer be launched from the Network Topology application. To launch summary reports, complete the following procedure:


Step 1 Open a terminal window.

Step 2 Enter NWReport at the prompt.


Limitations for WANDEST

When a coldstart is done on a CWM machine with the WANDEST server installed and there is dbaccess session on user_connection table before sync-up is done, the databroker may not be able to create the trigger to the table. This will result in the WANDEST incremental upload process not being able to retrieve the update data from the user_connection table.

In this scenario, the following message will appear on the Console during sync-up:

242:Could not open database table (svplus.user_connection)
106:ISAM error :non-exclusive access
Error in line 1
Near character position 1

There is no workaround to this problem. If the triggers could not be planted at the time of coldstart, then they will not be planted during/after CWM sync up. The only solution is for the user to do a coldstatrt again.

It is recommended that the user not do any manual database queries on the user_connection table during CWM sync up.

Limitations for CWM-to-CWM Communication

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

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

The Configurator can only be run on the Primary CWM.

Topology

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

Newly added MGX2 nodes may not be discovered on a CWM which is already running. The node may not be discovered because the IP address of the node may be unreachable when the node was added to the network. The workaround for this is to perform a dnpnport and uppnport on the newly added trunk in the network.

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

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

TOPO_SHOW_MAP 1 means when NWTopology opened, users can see topology maps.

TOPO_SHOW_MAP 0 means when NWTopology opened, users cannot see topology maps.

SNMP Traps

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

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

The removal and replacement of a controller card in the BPX may result in traps being dropped during sync-up. The following seven steps generate the problem.


Step 1 CWM is cold started with test network

Step 2 CWM sync-up is done. [All nodes in mode 3]

Step 3 The controller card in BPX A is pulled out.

Step 4 Immediately BPX A becomes unreachable [Still the mode for BPX A is 3]. It remains in this state for some time.

Step 5 BPX A becomes reachable

Step 6 CWM receives update node message from BPX A and starts the handshake protocol [The mode for BPX A is changed to mode 2]

Step 7 The BPX A sync-up is done. [Now the mode for BPX A turns to mode=3]


If you perform an operation on ports/lines/[any entity] between steps 5 and 6, then the BPX will not send robust messages about those operations to CWM.

If you perform an operation between steps 6 & 7, then the BPX sends messages to CWM.The time difference between steps 5 & 6 might be a few seconds.

If you do any operation during that short interval between steps 5 & 6 CWM will not receive any generated traps about those operations.

CWM 11 Notes and Cautions

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

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


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


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

CWM 11.0.10 Server Installation or Upgrade to CWM 11.0.10 from CWM 10.5 and Earlier


Note CWM software can be upgraded from 10.4.10 patch 3, 10.5.10 Patch 2, 10.5.10 Patch 3, or 11.0.00 (with or without patch 1)


The most current upgrade and installation information is found in the CWM Installation Guide for Solaris 8, Release 11 (78-14230-01). A PDF copy of this document is on the second CWM 11 Server/Client CD.The following sections describe installation and upgrade procedures specific to CWM 11.0.10.

Issue with Upgrading or Installing CWM 11.0.10 on Systems that Use or Will Be Using Meta Devices or Multiple Disks for Informix

There is an issue with database access with Solaris 8 CWM 11.0.10 systems using Meta Devices or Multiple Disks for Informix. All of the databases are being put into the first (rootdbs) partition.There are two issues with this:

If the first partition is small, then the databases will fill up faster than expected, causing unknown CWM failures.

Some users separate the databases for performance reasons, so any expected performance gains will not be realized.

This issue affects you if you are installing CWM for the first time on a Sun workstation or are upgrading your operating system and installing CWM for the first time. The installation of Informix for the first time changes the Solaris kernel parameters and requires a reboot.


Note The following workaround also applies if you are installing Statistics Collection Manager Standalone (SCMSA).


Fixing Issue before Rebooting

If you will be setting up multiple partitions (answering "Yes" to the "Do you want multiple Disk configuration for informix database?" prompt) or setting up meta devices (answering "Yes" to the "Do you use disk striping (meta devices) for database partitions?") during your installation of CWM, BEFORE rebooting the workstation (the last step of the installation),

At the end of the install when you are prompted with the following, "Kernel has been modified. The system must be rebooted to complete the installation. Reboot System now? ", choose "No". DO NOT REBOOT THE WORKSTATION.


Note If you are not prompted, then you do not have to do any of the following procedures.


The workaround to fix this problem is to remove the phrase
| tee -a /usr/users/svplus/install/upgrade/S97.log 2>&1 from several lines in the /etc/rc3.d/S97firsttime file.

To accomplish this, you MUST do one of the following procedures:

Download the 11_0_10_S97firsttime.tar file from CCO at http://www.cisco.com/cgi-bin/tablebuild.pl/strataview. This tar file contains an edited version of the /etc/rc3.d/S97firsttime file.

Edit the existing /etc/rc3.d/S97firsttime file manually

Refer to the following two sections for instructions.

Downloading the 11_0_10_S97firsttime.tar File from CCO

A tar file containing an edited version of the /etc/rc3.d/S97firsttime file is available on CCO. Complete the following steps to download and untar this file.


Step 1 Download the 11_0_10_S97firsttime.tar file from CCO at http://www.cisco.com/cgi-bin/tablebuild.pl/strataview.

Step 2 Log in to the workstation as root

# su

Step 3 Untar the 11_0_10_S97firsttime.tar file by executing the following command:

# tar xvf <path-of-download-dir>/11_0_10_S97firsttime.tar

The edited /etc/rc3.d/S97firsttime file will be installed in the appropriate location.

Step 4 Reboot the workstation.

Step 5 Start the CWM configuration process as described in the CWM Installation Guide for Solaris 8, Release 11 (78-14230-01).


Editing the Existing /etc/rc3.d/S97firsttime File Manually

If you didn't download the 11_0_10_S97firsttime.tar file from CCO, you will need to complete the following steps to edit the existing /etc/rc3.d/S97firsttime file to remove the phrase
| tee -a /usr/users/svplus/install/upgrade/S97.log 2>&1 from the six lines where it appears.


Step 1 Log in to the workstation as root

# su

Step 2 Open the /etc/rc3.d/S97firsttime file for editing with the vi Editor:

# vi /etc/rc3.d/S97firsttime

Step 3 Change the second line in the file from this:

/usr/users/svplus/tmp/chmodFile | tee -a /usr/users/svplus/install/upgrade/S97.log 2>&1

to this:

/usr/users/svplus/tmp/chmodFile

Step 4 Change the third line in the file from this:

/usr/users/svplus/tmp/dbmode | tee -a /usr/users/svplus/install/upgrade/S97.log 2>&1

to this:

/usr/users/svplus/tmp/dbmode

Step 5 Change the fourth line in the file from this:

/usr/users/svplus/tmp/dbfirstinit | tee -a /usr/users/svplus/install/upgrade/S97.log 2>&1

to this:

/usr/users/svplus/tmp/dbfirstinit

Step 6 Change the sixth line in the file from this:

/usr/users/svplus/tmp/dbonmode | tee -a /usr/users/svplus/install/upgrade/S97.log 2>&1

to this:

/usr/users/svplus/tmp/dbonmode

Step 7 Change the seventh line in the file from this:

/usr/users/svplus/tmp/dbonspace | tee -a /usr/users/svplus/install/upgrade/S97.log 2>&1

to this:

/usr/users/svplus/tmp/dbonspace

Step 8 Change the ninth line in the file from this:

rm /etc/rc3.d/S97firsttime | tee -a /usr/users/svplus/install/upgrade/S97.log 2>&1

to this:

rm /etc/rc3.d/S97firsttime

Step 9 Save your changes and exit from the editor by entering the following command:

:wq!

Step 10 Confirm that your edits are saved by viewing the edited file.

The newly edited /etc/rc3.d/S97firsttime file should look like this:

#!/bin/sh
/usr/users/svplus/tmp/chmodFile
/usr/users/svplus/tmp/dbmode
/usr/users/svplus/tmp/dbfirstinit
sleep 5
/usr/users/svplus/tmp/dbonmode
/usr/users/svplus/tmp/dbonspace
sleep 3
/bin/rm /etc/rc3.d/S97firsttime

Step 11 Change the permissions of the /etc/rc3.d/S97firsttime file by entering the following command:

# /bin/chmod 744 /etc/rc3.d/S97firsttime

Step 12 Reboot the workstation.

Step 13 Start the CWM configuration process as described in the CWM Installation Guide for Solaris 8, Release 11 (78-14230-01).


Remedy if You Have Already Rebooted the Workstation

If you've already rebooted your workstation after installing or upgrading to CWM, and you need to support disk partitioning or meta devices on your workstation, after your workstation comes back up, wait for at least 10 minutes before going on.

There are two methods to fix this issue. The first method requires a reboot, and is described in the next section.

Replace or Edit the S97firsttime File (Requires a Reboot)

If you've already rebooted your workstation after installing or upgrading to CWM, and you don't have an issue with rebooting your workstation, complete one of the following procedures:

Download the 11_0_10_S97firsttime.tar file from CCO at http://www.cisco.com/cgi-bin/tablebuild.pl/strataview. This tar file contains an edited version of the /etc/rc3.d/S97firsttime file.

Edit the existing /etc/rc3.d/S97firsttime file manually

Refer to the following two sections for instructions.

Downloading the 11_0_10_S97firsttime.tar File from CCO

A tar file containing an edited version of the /etc/rc3.d/S97firsttime file is available on CCO. Complete the following steps to download and untar this file.


Step 1 Download the 11_0_10_S97firsttime.tar file from CCO at http://www.cisco.com/cgi-bin/tablebuild.pl/strataview.

Step 2 Log in to the workstation as root.

# su

Step 3 Untar the 11_0_10_S97firsttime.tar file by executing the following command:

# tar xvf <path-of-download-dir>/11_0_10_S97firsttime.tar

The edited /etc/rc3.d/S97firsttime file will be installed in the appropriate location.

Step 4 Reboot the workstation.

Step 5 Start the CWM configuration process as described in the CWM Installation Guide for Solaris 8, Release 11 (78-14230-01).


Editing Existing /etc/rc3.d/S97firsttime File Manually

If you didn't download the 11_0_10_S97firsttime.tar file from CCO, you will need to complete the following steps to edit the existing /etc/rc3.d/S97firsttime file to remove the phrase
| tee -a /usr/users/svplus/install/upgrade/S97.log 2>&1 from the six lines where it appears.


Step 1 Log in to the workstation as root

# su

Step 2 Open the /etc/rc3.d/S97firsttime file for editing with the vi Editor:

# vi /etc/rc3.d/S97firsttime

Step 3 Change the second line in the file from this:

/usr/users/svplus/tmp/chmodFile | tee -a /usr/users/svplus/install/upgrade/S97.log 2>&1

to this:

/usr/users/svplus/tmp/chmodFile

Step 4 Change the third line in the file from this:

/usr/users/svplus/tmp/dbmode | tee -a /usr/users/svplus/install/upgrade/S97.log 2>&1

to this:

/usr/users/svplus/tmp/dbmode

Step 5 Change the fourth line in the file from this:

/usr/users/svplus/tmp/dbfirstinit | tee -a /usr/users/svplus/install/upgrade/S97.log 2>&1

to this:

/usr/users/svplus/tmp/dbfirstinit

Step 6 Change the sixth line in the file from this:

/usr/users/svplus/tmp/dbonmode | tee -a /usr/users/svplus/install/upgrade/S97.log 2>&1

to this:

/usr/users/svplus/tmp/dbonmode

Step 7 Change the seventh line in the file from this:

/usr/users/svplus/tmp/dbonspace | tee -a /usr/users/svplus/install/upgrade/S97.log 2>&1

to this:

/usr/users/svplus/tmp/dbonspace

Step 8 Change the ninth line in the file from this:

rm /etc/rc3.d/S97firsttime | tee -a /usr/users/svplus/install/upgrade/S97.log 2>&1

to this:

rm /etc/rc3.d/S97firsttime

Step 9 Save your changes and exit from the editor by entering the following command:

:wq!

Step 10 Confirm that your edits are saved by viewing the edited file.

The newly edited /etc/rc3.d/S97firsttime file should look like this:

#!/bin/sh
/usr/users/svplus/tmp/chmodFile
/usr/users/svplus/tmp/dbmode
/usr/users/svplus/tmp/dbfirstinit
sleep 5
/usr/users/svplus/tmp/dbonmode
/usr/users/svplus/tmp/dbonspace
sleep 3
/bin/rm /etc/rc3.d/S97firsttime

Step 11 Change the permissions of the /etc/rc3.d/S97firsttime file by entering the following command:

# /bin/chmod 744 /etc/rc3.d/S97firsttime

Step 12 Reboot the workstation.

Step 13 Start the CWM configuration process as described in the CWM Installation Guide for Solaris 8, Release 11 (78-14230-01).


Cleaning Up TEE Process (Does Not Require Reboot)

If you rebooted after installing or upgrading to CWM, and you want to fix the issue without rebooting your workstation, complete the following procedure:


Step 1 Log in to the machine as root

# su

Step 2 At the root prompt, check to see if there are any tee processes running by entering the following command:

# /usr/bin/ps -aef | grep "tee -a /usr/users/svplus/install/upgrade/S97.log" | grep -v 
grep 

The following is an example of what displays:

root   295   258  0 19:37:14 ?        0:00 tee -a /usr/users/svplus/install/upgrade/S97.log 

The process corresponding to pid 295 is "tee -a /usr/users/svplus/install/upgrade/S97.log"

Step 3 Issue a kill signal to end the process by entering the following:

# kill -9 295 

Step 4 Repeat Steps 2 and 3 until you do not see any more tee processes.

Step 5 After about 5 minutes, check to make sure that the S97firsttime process finishes. Enter the following command:

# /usr/bin/ps -aef | grep S97firsttime 

There is no need to reboot after this step.

Step 6 Start the CWM configuration process as described in the CWM Installation Guide for Solaris 8, Release 11 (78-14230-01).


Remedy if You Have Already Rebooted Workstation and Entered CWM as svplus

If you rebooted after installing or upgrading to CWM, logged in as user svplus, and typed CWM to get to the opening menu, DO NOT START THE CORE. Type "X" to exit the opening menu and complete the following steps:


Step 1 Log in to the machine as root

# su

Step 2 At the root prompt, enter the following command:

# /bin/mv /usr/users/svplus/install/upgrade/createDB /usr/users/svplus/tmp 


The only method to fix this issue requires a reboot, and is described in the next section.

Replace or Edit S97firsttime File (Requires Reboot)

If you've already rebooted your workstation after installing or upgrading to CWM, and you don't have an issue with rebooting your workstation, complete one of the following procedures:

Download the 11_0_10_S97firsttime.tar file from CCO at http://www.cisco.com/cgi-bin/tablebuild.pl/strataview. This tar file contains an edited version of the /etc/rc3.d/S97firsttime file.

Edit the existing /etc/rc3.d/S97firsttime file manually

Refer to the following two sections for instructions.

Downloading 11_0_10_S97firsttime.tar File from CCO

A tar file containing an edited version of the /etc/rc3.d/S97firsttime file is available on CCO. Complete the following steps to download and untar this file.


Step 1 Download the 11_0_10_S97firsttime.tar file from CCO at http://www.cisco.com/cgi-bin/tablebuild.pl/strataview.

Step 2 Log in to the workstation as root

# su

Step 3 Untar the 11_0_10_S97firsttime.tar file by executing the following command:

# tar xvf <path-of-download-dir>/11_0_10_S97firsttime.tar

The edited /etc/rc3.d/S97firsttime file will be installed in the appropriate location.

Step 4 Reboot the workstation.

Step 5 Start the CWM configuration process as described in the CWM Installation Guide for Solaris 8, Release 11 (78-14230-01).


Editing Existing /etc/rc3.d/S97firsttime File Manually

If you didn't download the 11_0_10_S97firsttime.tar file from CCO, you will need to complete the following steps to edit the existing /etc/rc3.d/S97firsttime file to remove the phrase
| tee -a /usr/users/svplus/install/upgrade/S97.log from the six lines where it appears.


Step 1 Log in to the workstation as root

# su

Step 2 Open the /etc/rc3.d/S97firsttime file for editing with the vi Editor:

# vi /etc/rc3.d/S97firsttime

Step 3 Change the second line in the file from this:

/usr/users/svplus/tmp/chmodFile | tee -a /usr/users/svplus/install/upgrade/S97.log

to this:

/usr/users/svplus/tmp/chmodFile

Step 4 Change the third line in the file from this:

/usr/users/svplus/tmp/dbmode | tee -a /usr/users/svplus/install/upgrade/S97.log

to this:

/usr/users/svplus/tmp/dbmode

Step 5 Change the fourth line in the file from this:

/usr/users/svplus/tmp/dbfirstinit | tee -a /usr/users/svplus/install/upgrade/S97.log

to this:

/usr/users/svplus/tmp/dbfirstinit

Step 6 Change the sixth line in the file from this:

/usr/users/svplus/tmp/dbonmode | tee -a /usr/users/svplus/install/upgrade/S97.log

to this:

/usr/users/svplus/tmp/dbonmode

Step 7 Change the seventh line in the file from this:

/usr/users/svplus/tmp/dbonspace | tee -a /usr/users/svplus/install/upgrade/S97.log

to this:

/usr/users/svplus/tmp/dbonspace

Step 8 Change the ninth line in the file from this:

rm /etc/rc3.d/S97firsttime | tee -a /usr/users/svplus/install/upgrade/S97.log

to this:

rm /etc/rc3.d/S97firsttime

Step 9 Save your changes and exit from the editor by entering the following command:

:wq!

Step 10 Confirm that your edits are saved by viewing the edited file.

The newly edited /etc/rc3.d/S97firsttime file should look like this:

#!/bin/sh
/usr/users/svplus/tmp/chmodFile
/usr/users/svplus/tmp/dbmode
/usr/users/svplus/tmp/dbfirstinit
sleep 5
/usr/users/svplus/tmp/dbonmode
/usr/users/svplus/tmp/dbonspace
sleep 3
/bin/rm /etc/rc3.d/S97firsttime

Step 11 Change the permissions of the /etc/rc3.d/S97firsttime file by entering the following command:

# /bin/chmod 744 /etc/rc3.d/S97firsttime

Step 12 Reboot the workstation.

Step 13 Start the CWM configuration process as described in the CWM Installation Guide for Solaris 8, Release 11 (78-14230-01).


Remedy if You Have Already Rebooted Workstation and Started Core Processes

If you rebooted after installing or upgrading to CWM and started the core, CWM will be functioning normally but the Informix multiple raw partition is not used to its fullest extent. If you would like to use multiple raw partitions with the CWM database residing in its own dbspace (datadbs) instead of rootdbs, you will need to complete the following procedure:


Note This procedure requires both a reboot and a coldstart. Please note that this procedure should only be attempted if you have some Informix expertise. Contact the TAC before attempting this if you've any questions.



Step 1 Log in as svplus

hostname# su -u svplus

The system prompts you for the svplus password:

password:

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

% 

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

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

Step 3 Stop the core by choosing Option 2.

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

Step 5 Export all the CWM databases to a directory containing enough disk space to store the three databases. Substitute <path to dbbackup directory> with the actual path name, for example, /nfs/cwmbackup

% dbexport stratacom -o <path to dbbackup directory> 
% dbexport statsdb -o <path to dbbackup directory> 
% dbexport scmdb -o <path to dbbackup directory> 

Step 6 Reboot the system.

Step 7 Log in as root

% su

The system prompts you for the root password:

password:

After you enter the password, the root prompt displays:

# 

Step 8 Change shell to the csh by executing the following command:

# csh

After you change to the csh, the csh prompt displays:

hostname# 

Step 9 Set up permissions and ownership for the raw partitions you wish to use for datadbs and logdbs

hostname# chown -R informix <path-to-datadbs> <path-to-logdbs> 
hostname# chgrp -R informix <path-to-datadbs> <path-to-logdbs> 

Step 10 Shut down informix by executing the following commands:

hostname# source /usr/users/svplus/.cshrc 
hostname# onmode -ky 
hostname# pkill -9 oninit 

Step 11 Confirm that the oninit process is not running by executing the following command:

hostname# ps -aef | grep oninit

Step 12 Restart informix by executing the following command:

hostname# oninit -iy 

Step 13 Bring informix into multi-user mode by executing the following command:

hostname# onmode -m 

Step 14 Add datadbs and logdbs by executing the following commands:

hostname# /usr/users/informix92/bin/onspaces -c -d datadbs -p <path-to-datadbs> -o 0 -s <size-in-bytes> 
hostname# /usr/users/informix92/bin/onspaces -c -d logdbs -p <path-to-logdbs> -o 0 -s <size-in-bytes> 

Step 15 Bring informix into single-user mode by executing the following command:

hostname# /usr/users/informix92/bin/onmode -uy 

Step 16 Add a logical log for logdbs by executing the following command:

hostname# /usr/users/informix92/bin/onparams -a -d logdbs > /dev/null 

Step 17 Bring informix into multi-user mode by executing the following command:

hostname# /usr/users/informix92/bin/onmode -m 

Step 18 Log in as svplus

hostname# su -u svplus

The system prompts you for the svplus password:

password:

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

% 

Step 19 Import the databases by executing the following three commands:

% dbimport stratacom -d datadbs -i <path to dbbackup directory> 
% dbimport statsdb -d datadbs -i <path to dbbackup directory> 
% dbimport scmdb -d datadbs -i <path to dbbackup directory> 

Step 20 Drop the network data by executing the following command:

% coldstartCWM

Now you can start the core.


Issue with .rhosts File During Upgrade

The .rhosts file is overwritten during the upgrade process.

The installation script that comes with release 11.0.10 CWM has a .rhosts file that replaces the one on the server being upgraded. This .rhosts file only has the (+) sign in it.

Save a copy of the file before the start of the upgrade and reload it right after the upgrade is done.

Saving User-created Statistics Collection Manager Templates before Upgrading

If you have created your own SCM (statistics) templates and if those user created templates are used as the default template for that platform, your user-created templates need to be set to non-default (the "use as default" field needs to be set to "No") in the SCM GUI BEFORE you upgrade to 11.0.10. The node templates are saved in /usr/users/svplus/SAVE/scmtemplate.

Complete the following steps before upgrading to 11.0.10:


Step 1 Edit the template in SCM GUI, and change the "use as default" to "No" before doing "save" or "save as" for the template.

Step 2 Perform the upgrade to 11.0.10

Step 3 After the CWM is up and running, open SCM GUI, select edit template for any platform/enabling method and change the "use as default" flag to "Yes" for the required user created template.


Note Only the templates for the following platforms/cards are supported during upgrade from 10.4.10 Patch 3 and/or 10.5.10 Patch 2 or Patch 3:
BPX, IGX, PXM1-based MGX Feeders

The following platforms are not supported during upgrade from 10.4.10 Patch 3 and/or 10.5.10 Patch 2 or Patch 3:
PXM1E-based MGX 8830 and MGX 8850 switches
PXM45-based MGX 8850 switches
PXM45-based MGX 8950 switches.




Note Before upgrading to 11.0.10 from the 10.4.10 Patch 3 release of CWM, download or copy the PreUpg104.csh script into the /usr/users/svplus/scripts directory and run it before installing 11.0.10.


CWM 11.0.10 Patch 2 Installation

Solaris 8

This patch includes the following components:

CWM Server

11.0.10.SOL28.Patch2P2.tar.gz

InstallCWM11Patch2.csh

Informix 9.21 UC7 (this upgrade is not necessary if done with Patch 1 upgrade).

informix921uc7.tar

InstallInformixPatch.csh

CWM Client

11.0.10.SOL28.client.Patch2P2.tar.gz

InstallClient11Patch2.csh

CWM SNMPAgent

11.0.10.SOL28.agent.Patch2P2.tar.gz

InstallSNMPAgent11Patch2.csh

CWM SCMSA

11.0.10.SOL28.scmsa.Patch2P2.tar.gz

InstallSCMSA11Patch2.csh

WANDEST 2.3 Patch 2.1

wandest2.3.SOL28.client.Patch2.1.tar

wandest2.3.SOL28.server.Patch2.1.tar

InstallWD23Patch2.1.csh


CWM Server Patch and Informix 9.21 UC7

To install the CWM Server Patch and Informix 9.21 UC7, perform the following steps:


Step 1 Login to the CWM workstation as user root.

Step 2 Save a copy of the /usr/users/svplus/network.conf.

% cp -p network.conf network.conf.save

Step 3 Download or copy the compressed tar files and the installation scripts to the same local directory (for example, /tmp).

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

Step 5 Decompress the compressed tar files:

# gunzip 11.0.10.SOL28.Patch2P2.tar.gz 
# gunzip informix921uc7.tar

Step 6 Check for the file InstallCWM11Patch2.csh and InstallInformixPatch.csh, and begin the install process by entering the following command:

# ./InstallInformixPatch.csh
# ./InstallCWM11Patch2.csh 11.0.10.SOL28.Patch2P2.tar

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

a. Stop the wdclient.

b. Download or copy the 11.0.10.SOL28.wd23.P2.tar file to the local directory (for example, /tmp).

c. Untar the 11.0.10.SOL28.wd23.P2.tar file

# tar xvfp 11.0.10.SOL28.wd23.P2.tar

d. Change the permission of wdserver in the /usr/users/wandest directory.

# chmod 4711 /usr/users/wandest/bin/wdserver

Step 8 Exit from root.

Step 9 Enable the Network Health Monitoring feature by setting "HEALTH_MONITOR=ON" in /usr/users/svplus/config/svplus.conf file if you want to use this feature.

Step 10 Change to /usr/users/svplus/config:

% cd /usr/users/svplus/config

Step 11 Incorporate the network information from network.conf.save into the new network.conf.

Step 12 Source.


CWM Client Patch Installation

To install the CWM Client Patch, perform the following steps:


Step 1 Login to the CWM workstation with the same username used to install the Client.

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

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

Step 4 Decompress the compressed tar file:

# gunzip 11.0.10.SOL28.client.Patch2P2.tar.gz

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

# ./InstallClient11Patch2.csh 11.0.10.SOL28.client.Patch2P2.tar

Step 6 Exit from root.


CWM SNMPAgent (ServiceAgent) Patch Installation

To install the CWM SNMPAgent (ServiceAgent) Patch, perform the following steps:


Step 1 Login to the CWM workstation as user root.

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

Step 3 Change to the local directory containing the compressed tar file and the installation script.

Step 4 Decompress the compressed tar file:

# gunzip 11.0.10.SOL28.agent.Patch2P2.tar.gz

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

# ./InstallSNMPAgent11Patch2.csh 11.0.10.SOL28.agent.Patch2P2.tar

Step 6 Exit from root.


CWM SCMSA Patch Installation

To install the CWM SCMSA Patch, perform the following steps:


Step 1 Login to the SCMSA workstation as user root.

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

Step 3 Change to the local directory containing the compressed tar file and the installation script.

Step 4 Decompress the compressed tar file:

# gunzip 11.0.10.SOL28.scmsa.Patch2P2.tar.gz

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

# ./InstallSCMSA11Patch2.csh 11.0.10.SOL28.scmsa.Patch2P2.tar

Step 6 Exit from root.


WANDEST Server Patch Installation

To install the WANDEST Server Patch, perform the following steps:


Note Note: WANDEST Client has been stopped before installing WANDEST Server



Step 1 Login to the CWM workstation as user root.

Step 2 Download or copy the tar file corresponding to the Solaris version and the installation script to the local directory (for example, /tmp).

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

Step 4 Run the installation script to install the patch

For example, # ./InstallWD23Patch2.1.csh wandest2.3.SOL28.server.Patch2.1.tar

Step 5 Exit from root


WANDEST Client Patch Installation

To install the WANDEST Client Patch, perform the following steps:


Step 1 Login to the WANDEST Client workstation as wandest.

Step 2 Stop the wdclient.

Step 3 Download or copy the tar file wandest2.3.SOL28.client.Patch2.1.tar to the local directory (for example, /tmp).

Step 4 Untar the wandest2.3.SOL28.client.Patch2.1.tar file

For example, # tar xvfp wandest2.3.SOL28.client.Patch2.1.tar

Step 5 ftp the wdclient.ctrl file from the WANDEST 2.3 Patch 2.1 Server /usr/users/wandest/wandest.ctrl over into /usr/users/wandest/client/ctrl directory


CWM 11.0.10 non-Java-based Client Installation


Note The instructions in the CWM Installation Guide for Solaris 8, Release 11 (78-14230-01) reflect the Java-based client, available with CWM 11.0.10. CWM 11.0.10 also uses the non-Java-based client. The instructions for installing the non-Java-based client are below.


This section provides step-by-step procedures to install the CWM Release 11.0.10 client software on a client workstation.

Table 10 describes the configuration for the minimum type of machine supported for CWM Release 11.0.10 as a standard non-Java-based client workstation platform.

Table 10 Sun Client Platform Requirements 

Machine Type
Number of CPUs
Size of RAM
Hard Disk Drive
Swap Space
Desktops Supported

Sun Ultra 10 with SCSI controller

1

512 MB

Requires 80 MB of disk space

1 GB

Less than 5



Note The minimum CPU speed requirement is 300 MHz. Most versions of the Sun Ultra 10 have a 450 MHz processor. Each client requires a 24-bit graphics card.


Installing Solaris 8

Before installing the CWM Release 11.0.10 non-Java-based client software on the CWM workstation, the following software should already be installed:

Solaris 8 Operating System

Solaris 8 patches as specified in the CWM 11.0.10 release notes.

Install Solaris 8 according to the automated procedure. The Solaris installation program is a menu-driven, interactive step-by-step guide to installing the Solaris operating environment. It also provides online help to answer your questions.

Configuring Workstation Display

After installing the Sun Solaris 8 operating system, perform the following steps:


Step 1 Log in to the workstation as user root. using the Solaris Login interface and select CDE.

Step 2 Close the File Manager and Help windows, leaving only the CDE menu bar.

Step 3 Right click on blank screen, highlight Tools, then Terminal.

Move this terminal window to the upper right corner of the screen.

Step 4 Right click on blank screen highlight Hosts, then Terminal Console.

Lower the height to display four lines and move this window so that it rests above the CDE menu bar. This window provides a display of workstation system messages.

Step 5 Left click the CDE icon labeled TTT.

The Style Manager window is displayed.

Step 6 Left click on Screen, click screen saver on and screen lock off, then click OK.

If you prefer to use the screen saver, highlight choice(s) and start the screen saver at 29 minutes. Start the screen lock at 30 minutes, click OK.

Step 7 Click on Backdrop and select GrayDk, then click Apply.

Do the same to all four screens, labeled One, Two, Three and Four in the CDE icon bar. In Four click OK and return to screen One. This helps to conserve workstation resources.

Step 8 Click the CDE icon labeled TTT, then click on Startup in the Style Manager. Click on Set Home Session and click OK.

The next login session will come up using this same screen configuration. Click OK and close the Style Manager.

Step 9 Type eject in the Terminal Window to remove the Solaris 8 CD, if necessary.


Installing InstallShield non-Java based CWM Client Software

This section describes how to install the non-java based CWM client software provided on the second CWM distribution CD. It is no longer necessary to install the CWM client software from this distribution CD. The new Java CWM 11.0.10 client software can be deployed directly from the CWM server. Refer to the CWM Installation Guide for Solaris 8, Release 11 (78-14230-01) for more details.

The CWM Release 11.0.10 non-java based client software installation uses InstallShield. To install the CWM Release 11.0.10 client software, complete the following steps:


Step 1 Log in to the CWM workstation as a standard user (not as root), and insert the CWM Release 11.0.10 CD-ROM#2 into the CDROM drive.

Step 2 Enter the following commands:

host% cd /cdrom/cdrom0
host% ls 

Step 3 Check for the file InstallClient.sh and begin the install process by entering the following command:

host% ./InstallClient.sh

The CWM Client Package Installation Welcome screen is displayed, as shown in Figure 1.

Figure 1 CWM Client Welcome Screen

Step 4 Click Next on the Welcome screen to continue.

The Choose Destination Directory screen, Figure 2, is displayed.

Figure 2 Choose CWM Client Destination Directory Screen

The displayed default for the application-based client is /usr/users/svclient.

Use the Browse... button to go to your home directory, and type in the name of a directory under your home directory into which to install the client files.

If the primary Destination directory you provide doesn't currently exist, the Destination Directory Confirmation Screen displays, as shown in Figure 3.

Figure 3 Destination Directory Confirmation Screen

If the directory is correct, click on the Yes button.

The software installation process begins. This process will take about 5 to 10 minutes depending on the speed and resources of the CWM workstation. The installation screen shows a dynamic indicator bar, which moves across the screen, indicating the progress of the installation process, as shown in Figure 4.

Figure 4 CWM Client Installation Progress Indicator

When completed, a final window displays indicating that the installation has completed. This window is shown in Figure 5.

Figure 5 CWM Client Installation Complete Screen

Step 5 Click Finish to end the installation.

Doing so ends the software installation process, and the Install Shield screen closes.

The system needs to be rebooted at this point.


Rebooting the Workstation

At the root prompt, enter the following command to reboot the workstation.

#  sync ;sync ;reboot
 

The reboot sequence aligns the cylinders of your hard disks and gracefully shuts down the Solaris operating system.

The OK prompt is displayed.

At this point, you can push the CDROM eject button on the CDROM drive to eject the installation disk.

Installing Netscape Communicator

The Sun Microsystems Netscape Communicator for Solaris package (version 4.76) is included on the Cisco-provided CWM CD-ROM#2 under the filename of NSCPcom.sparc.tar.gz

Netscape Communicator must be installed before CiscoView 5.4.1 can be launched. Netscape Communicator requires that the basic Solaris software end-user cluster (SUNWCuser) be installed. After installation, Netscape Communicator requires 20Mbytes of free disk space.

Install Netscape Communicator using the following steps.


Step 1 Log in to the CWM workstation as user root, and insert the Cisco WAN Manager Release 11 CD-ROM # 2 into the CD-ROM drive.

Step 2 The NSCPcom.sparc.tar.gz file is located on the CD-ROM in the 110tools directory. You can check that it is present by changing to the tools directory and listing the files as in the following commands.

# cd /cdrom/cdrom0/110tools
# ls 

Note The 110tools directory on the CD#2 also contains a copy of Adobe Acrobat Reader under the filename of sunsparc-rs-405.tar.gz. This can be used for viewing documentation in the PDF format.


Step 3 Copy the Netscape file to the workstation hard drive.

cp -p /cdrom/cdrom0/110tools/NSCPcom.sparc.tar.gz /tmp

Step 4 Copy the gzip utility to the workstation hard drive.

cp -p /cdrom/cdrom0/110tools/gzip /tmp

Step 5 Change to the tmp directory.

cd /tmp

Step 6 Change the permission of the copied gzip file so that it can be executed.

chmod 555 /tmp gzip

Step 7 Unzip the file the Netscape Communicator file.

./gzip -d /tmp/NSCPcom.sparc.tar.gz


Note The gzip utility is a compression software tool that compresses files and assigns them the.gz suffix. Use gzip -d to decompress .gz files. In addition to being provided on CD#2, installing CWM automatically installs gzip in the usr/users/svplus/tools folder and its path is defined in the users account.


Step 8 Untar the file.

tar xvf -p /tmp/NSCPcom.sparc.tar

Step 9 If not already logged in as root, log in now.

myhhost% su
Password:
#

Step 10 Install Netscape Communicator

pkgadd -d /tmp NSCPcom

This command installs the Netscape Communicator package in the /opt/NSCPcom directory.

Step 11 Add the /opt/NSCPcom directory to the PATH variable in the ./CWM file.

setenv PATH /opt/NSCPcom:$ {PATH}

Preparing CWM 11.0.10 Server Workstation to Launch CiscoView from Client Topology Window

Running CiscoView 5.4.1 from Netscape Communicator requires that a Java 1.3.1 plug-in be installed.

The plug-in is included in CDROM #2 and should be installed using the following procedure.


Step 1 Log in to the CWM workstation as user root, and insert the Cisco WAN Manager Release 11 CD-ROM # 2 into the CD-ROM drive.

Step 2 The j2re-1_3_1-solsparc.sh file is a script for installing the plug-in and is located on the CD-ROM in the 110tools directory. You can check that it is present by changing to the 110tools directory and listing the files as in the following commands.

# cd /cdrom/cdrom0/110tools
# ls 

Step 3 Copy the script file to a directory on the workstation hard drive (for example, /usr/users).

cp -p /cdrom/cdrom0/110tools/j2re-1_3_1-solsparc.sh /usr/users

Step 4 Change to the directory containing the script file (for example, /usr/users).

cd /usr/users

Step 5 Run the script

sh j2re-1_3_1-solsparc.sh

Running the script creates a directory named j2re-1_3_1 that contains the plug-in modules. This directory is created beneath the directory that you selected in Step 3.

Step 6 Start the vi editor to open the .cshrc file in the /usr/users/svplus directory.

Step 7 Add the following line to the end of the .cshrc file (this example assumes installation in /usr/users. If in Step 3 you installed the script in a directory other than /usr/users, use the directory selected in Step 3).

setenv NPX_PLUGIN_PATH /usr/users/j2re1_3_1/plugin/sparc/ns4

Step 8 Close vi, saving the changes.



Note You have to either source the .cshrc file or re-log in for the changes you've just made to the .cshrc file to take effect.



Note If you upgrade / downgrade your Java plug-in, you should delete the following files before starting Netscape:

$HOME/.netscape/cert7.db ($HOME here is /usr/users/svplus)
$HOME/.netscape/key3.db ($HOME here is /usr/users/svplus)


Preparing CWM 11.0.10 Client Workstation to Launch CiscoView from Client Topology Window

Before launching CiscoView from the client, perform the following steps:


Step 1 Edit the CWM script to add the path for the Netscape executable.

a. On the server side, you must add the following lines to the .cshrc file.

setenv PATH "netscape path":${PATH}
setenv NPX_PLUGIN_PATH /usr/users/j2re1_3_1/plugin/sparc/ns4


Note The variable "netscape path" must be /opt/NSCPcom.


b. On the client CWM workstation, add the following line to the ./CWM script instead of the .cshrc file:

setenv PATH "netscape path":${PATH}


Note The variable "netscape path" must be /opt/NSCPcom.


c. Next, after the java plug-in for Netscape has been downloaded and installed, add the following line to the ./CWM script before the runDesktop $DISPLAY line

setenv NPX_PLUGIN_PATH /usr/users/j2re1_3_1/plugin/sparc/ns4


Note The runDesktop $DISPLAY command must be the last line in the ./CWM script, otherwise, the CWM Client will not be able to launch CiscoView from the Client Topology window.


The last three lines of the ./CWM script should look like this:

setenv PATH /opt/NSCPcom:/${PATH}
setenv NPX_PLUGIN_PATH /usr/users/j2re1_3_1/plugin/sparc/ns4
runDesktop $DISPLAY


Note Before you attempt to start CiscoView from the client after installation, enter the following: setenv DISPLAY machine_name:0.0, where machine_name is set to the name of the client system where you're launching CiscoView. Otherwise, the error message "Environment Variable DISPLAY not set" will be displayed when you attempt to start CiscoView from the Client Topology window.




Important Configuration Notes

This section provides important information about configuration.

Orbix Registration

As noted in the CWM Installation Guide, use the ping command to confirm that the hostname.domainname you provide for Orbix registration is reachable before completing the installation. Refer to CSCdx87212 for more information about workarounds in the event that the hostname.domainname become unreachable.

Setting Up CWM-to-HP OpenView Communication

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

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

Naming Managed Nodes

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

Enabling Connection Descriptor

The connection descriptor field will not permit you to enter data until you turn the feature on by setting a flag in the /usr/users/svplus/config/CwmDomainGlobal.conf file

DESCRIPTOR_FLAG = 0

0 means off

1 means on

The connection descriptor string can contain any alphanumeric character and can be up to 64 characters (including spaces) in length.

This flag is disabled by default.

CWM Configuration

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

CWM Dedicated IP Ports

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

udp: 161, snmp get/set

udp: 2500, rtm

udp: 69, tftp server

tcp: 23, telnet

tcp: 13, daytime

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

udp: 162, snmp trap

tcp: 8888, HP OV topology daemon

tcp: 9999, HP OV database daemon

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

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

CWM 11 to CWM 11: Ports used by ORBIX:

Table 11 Orbix Fixed Socket Port Numbers 

Orbix Server
TCP Socket Port Number

TopoServer

5558

CmServer

5555

GenericServer

5559

LogServer

5556

CWMGateway

5557

ScmCollSvr

5561

ScmCtrlSvr

5560

StatsParserWD

5562

CWM Audit Logger

5563

CSRID Server

5564

Relay

23

Web Services

1551

CiscoView Web Server

1741


Unique Node ID

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

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

Security Profiles

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

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

If you are upgrading to CWM 11 from CWM 10.4.10, then the old security profile will automatically be converted and loaded into the database during upgrade. If you are upgrading from 10.5.10, no conversion is necessary.

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

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

CWM Database

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


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


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

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

Topology Discovery Configuration for AutoRoute Networks

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

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

Examine the /etc/hosts file and check that the file contains a nodename and IP address for all gateway nodes. The IP address should match the gateway node's (the one that CWM can use for AutoRoute network discovery). Enter the correct nodenames and addresses for any missing gateway nodes.

To view the /etc/hosts file, enter the following command:

host% more /etc/hosts

Use the vi editor to enter items into the file.

For each node:

Enter the BPX gateway node's IP address and the node name.

Example:

192.0.0.8 nmsbpx02

Note Use only one Gateway per network in case of AutoRoute networks


Topology Discovery Configuration for PNNI Networks

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

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

You also need to specify any PNNI nodes through the Network Configurator GUI tool if:

The SNMP community string for GET operation is not set to "public" and/or the SNMP community string for SET operation is not set to "private"

The FTP UserId and Password are not set to the default ("superuser")


Note Specify the IP Address as "Network IP" and mode as "Connected" for these nodes in the Network Configurator GUI Tool.


Topology Discovery Configuration for Hybrid (AutoRoute and PNNI) Networks

You must enter configuration for each Hybrid (AutoRoute and PNNI) network to be discovered by CWM in /usr/users/svplus/config/network.conf file.

To configure CWM for Hybrid (AutoRoute and PNNI) networks, the file has the following format.

NETWORK:Network1 	(a name for CWM to identify the network)
AR-GATEWAYS:sj123456	(the name or IP address of the gateway to the Autoroute section of the 
network)
PNNI-GATEWAYS:sj123456	(the name or IP address of the gateway to the PNNI section of the 
network)
DISCOVERY PROTOCOL:HYBRID 	(the discovery protocol, in this case always HYBRID)
IP REACHABILITY FLAG:NWIP_OFF (specifies in-band or out-of-band management)
OPTIONAL:"TIMEOUT = 7, RETRANSMIT = 6, THROTTLE = 0, ACKNOWLEDGE = 30, BLOCKSIZE = 1024" 
(the optional field is used to specify parameters if the 
desired value is different from the default value, 

With a hybrid network, the XPVC Preferred Table Configurator GUI in Topology GUI can no longer decide which are the closest set of XLMI links for the selected node. You must use the topology map in conjunction with the XPVC Preferred Table Configurator GUI to choose the correct closest link to the selected BPX.


Caution When your networks being managed include a PNNI network, an AutoRoute network, and a hybrid network ensure that both the PNNI-GATEWAYS and the AR-GATEWAYS are specified in the /usr/users/svplus/config/network.conf file. Without the appropriate gateway, the nodes will be discovered, but will not sync up. CWM effectively will not be able to manage these nodes

Examine the /etc/hosts file and check that the file contains a nodename and IP address for all gateway nodes. The IP address should match the gateway node's (the one that CWM can use for AutoRoute network discovery). Enter the correct nodenames and addresses for any missing gateway nodes.

To view the /etc/hosts file, enter the following command:

host% more /etc/hosts

Use the vi editor to enter items into the file.

For each node:

Enter the BPX gateway node's IP address and the node name.

Example:

192.0.0.5 sj123456

Note Use only one Gateway per network in case of AutoRoute networks


Topology Discovery Configuration for StandAlone Nodes

You can configure PXM1-based MGX nodes or PXM1E/PXM45-based MGX nodes as StandAlone nodes. Follow these steps:


Step 1 Run Network Configurator GUI tool.

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

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

Step 4 Choose correct Model No. [8250 or 8850 standalone, (check chassis type by running the dspcds command. The chassis type is the last line in the display)] and Mode (Stand Alone in this case), FTP username & password, and IP Address (Lan Ip Address) in Mode Tab of Add Dialog.

Step 5 Click on the OK button.

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


Note If you have an Automatic Routing Management or PNNI network configured, the network.conf file doesn't require any modification for Stand Alone nodes. If you have only Stand Alone nodes (no Automatic Routing Management or PNNI network configured), enter a dummy gateway node name in the GATEWAYS field in the Network 1 Automatic Routing Management portion of the network.conf file and remark out (#) all lines in the Network2 PNNI portion of the network.conf file


The following is an example of a dummy network:

NETWORK:Network1
GATEWAYS:/dev/null/0
DISCOVERY PROTOCOL:AUTOROUTE
IP REACHABILITY FLAG:NWIP_ON
OPTIONAL:"TIMEOUT = 7, RETRANSMIT = 6, THROTTLE = 0, ACKNOWLEDGE = 30,
BLOCKSIZE = 1024"

Connection Manager Configuration

Configuration Parameters for Connection Manager Daemon (cmgrd)

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

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

The configuration parameters in this file are listed below:

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

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

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

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

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

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

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

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

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

Egress PercentUtil from other end Percent Util.

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

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

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

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

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

RPM

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

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

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

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

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

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

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

atm pvc (for VBR.3) —to add the RPM "leg" of the channel or pvc for ABR.1

addcon—to add the PXM "leg" of the channel.

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

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

no atm pvc (for VBR.3) —to delete the RPM "leg" of the channel or no pvc (for ABR.1)

no addcon—to delete the PXM "leg" of the channel.

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

ASI/BNI

T3: 0-96000

E3: 0-80000

OC3: 0-353208

BXM/UXM

T3: 6-96000

E3: 6-80000

OC3: 6-353208

OC12: 6-1412832

ALM-B(BTM)

T3/E3: 10-24000

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

T3: average-96000

E3: average-80000

OC3: average-353208

OC12: average-1412832

BXM with HEC line formatting

T3_HEC: average-104268

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

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

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

A PVC already exists on a point-to-point subinterface

A PVC with same VPI/VCI already exists on a different subinterface.

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

If one of the following error message is encountered:

"atm pvc missing"

"add connection to PXM failed"


Note The following procedure is only for seeing the log. They do not resolve the problem


Complete the following steps:


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

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


Note The log may be wrapped on the RPM card.


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


Step 1 vi ~svplus/log/iosmgr.log

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

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

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


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


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

Useful commands are:

Router# show snmp

Router# config terminal

Router(config) snmp-server community POPEYE RW

Router(config) exit

Router# write memory


Setting up CiscoView to Manage RPM Cards from Workstation

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

Configuring SNMP and SYSLOG

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

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

Table 12 SNMP and SYSLOG Router Configuration Commands 

RPM Configuration Command Line
Description

logging 10.1.1.1

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

snmp-server community public RO

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

snmp-server community private RW

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

snmp-server trap-source Channel0/2

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

snmp-server location RTP, NC

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

snmp-server contact Network Administrator

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

snmp-server enable traps

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

snmp-server host 10.1.1.1 public

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



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


Configuring CiscoView for Large Networks

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

SNMP Service Agent Release Notes

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


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

CWM SNMP Agent Configuration Notes

The CWM SNMP MasterAgent is configured to use UDP port 816 as the default port for CWM SNMP communication. If the 8161 UDP port is used by other processes in the customer scenario, the user can configure the CWM MasterAgent to use a different UDP port by modifying the /usr/users/svplus/scripts/start_SV+ script as given below.

The following line needs to be edited to change the port:

SR_SNMP_TEST_PORT=8161

In the line mentioned above, replace 8161 by any other valid UDP port to match the user system requirements.

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

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

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

Syntax:

snmpCommunityEntry t0000000 private private localSnmpID - - nonVolatile

snmpCommunityEntry t0000001 public public localSnmpID - - nonVolatile

SNMP Stack Parameters for CWM 11

The user can configure the CWM SNMP stack parameters by modifying the snmpd.cnf config file located in /usr/users/svplus/config directory.

MAX_THREADS

The value of this variable should be set to the maximum number of concurrent (plus 1 for the maintenance thread) SNMP requests the user would expect in their environment at any given time. For example, if the user expects a maximum of not more than 10 requests at any given time, the value of this parameter should be set as 11. The value of this variable gives the maximum number of requests the CWM SNMP stack will queue and process at any given instance. By default, the CWMSNMP Agent module is configured to handle a maximum of 25 concurrent SNMP requests at a given time.

MAX_PDU_TIME

This value of this variable should be set to (MAX_THREADS * 60 seconds) * 100. The assumption here is that the maximum turnaround time for a provisioning request (for example, an RPM MGX 8850 Release 1 node connection provisioning) might take around 60 seconds. A multiplication factor of 100 is applied since this value is given in centiseconds(1/100th of a second). For example, if the MAX_THREADS value is 5, this value would be 30000 centiseconds, i.e., 300 seconds or 5 minutes. But since all the provisioning requests will not take 60 seconds, the default value of 30000 centiseconds or 300 seconds should suffice most of the customer scenario.

MAX_OUTPUT_WAITING

This should be set to (MAX_THREADS * 4096). This is the amount of space the stack requires to buffer/queue the incoming requests and outgoing responses. OSS/Client/Manager Timeout should be set to MAX_PDU_TIME

OSS Timeout and Retry

The OSS SNMP operation timeout value must be configured to a value greater than or equal to MAX_PDU_TIME configured in snmpd.cnf config file (300 seconds by default). This will ensure that the OSS waits for a sufficient turnaround time for CWM SNMP Agent status.

Configuring the OSS timeout to a value less than the MAX_PDU_TIME(CWM SNMP Agent turnaround time) will result in duplicate requests for the same SNMP operation to be forwarded to the CWM SNMP Agent. OSS might send one more request for the same operation currently in progress, which might result in an SNMP error being returned to OSS.

Statistics Collection Manager Release Notes

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

New Features

CWM 11 adds statistics collection support for the PXM1E, the FRSM-HS2/B, and the FRSM-12

Limitations

We recommend that you use the default number of 100 nodes per SCM collector. If you use too high a number of nodes per SCM, the workstation might fail on a UNIX select system call, ftp or tftp limitation.

The following limitation also exists:

PXM45 switchover may lose synchronization of enabling/disabling status.

Additional Information

The SCM supports a maximum of 400 ports for collectors. The default setting is 100 nodes. If the workstation manages a large number of nodes, scmcollsvr.conf should be tuned to achieve maximum performance, especially the buffer size of all file queues and the number of threads for ftp or tftp.

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

The peak interval cannot be zero

The peak interval must be a multiple of the collection interval

The peak interval must be a factor of the collection interval

The peak interval can be the same as the bucket interval

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

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

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

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

time—Calculated using:

		time = (stats / cnt) * delay

Where:

stats—Calculated using:

(conns * stats_per_con) + (CLNs * stats_per_cln) + (trks * stats_per_trk) +
(
ports * stats_per_port)

cnt—Number of stats configured in one group before giving up CPU; a configurable parameter on the switch

delay—Delay between enabling of each group of statistics; a configurable parameter on switch.

WANCV 4.11 Notes and Cautions

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

The LEDs displayed in the chassis screen still display as green on the front card while there is a card mismatch. You must currently go to the "card summary" display to see the indicator of "mismatchwithParent".

With CWM 11.0.10, CiscoView shows an incorrect LED state for the standby VISM PR E1 card in a redundant VISM PR E1 card set undergoing "softswitch" Instead of reverting to Standby state, the slot reverted to standby displays as failed. The "RedundancyInfo" table under shelf configuration correctly indicates that the card is in standby mode.

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

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

Performance

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


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


Control Point Interfaces

Command Line Interface

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


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


ipifconfig—Configure IP address information for an IP interface

ipifconfig <interface> [<ip_address>] [up | down] [netmask <mask>]

[broadcast <broad_addr>] [arp | noarp] [svc | nosvc] [pvc | nopvc]

[default | nodefault] [clrstats]

Where:

<interface>—atmX, where X is the unit number (currently X is 0)

<ip_address>—IP address of interface (optional), but must exist if interface not previously configured

[up | down]—Mark interface up or down (optional)

[netmask <mask>]—Specify network mask for interface (optional)

[broadcast <broad_addr>]—specify broadcast IP address for interface (optional)

[arp | noarp]—Specify whether ARP is enabled or disabled (optional), default is enabled if interface supports ARP

[svc | nosvc]—Specify whether SVC is enabled or disabled (optional), default is enabled if interface supports SVC

[pvc | nopvc]—Specify whether PVC is enabled or disabled (optional), default is disabled

[default | nodefault—Use this interface as the default route or disable this interface as the default route (optional)

[clrstats]—Clear all interface and SVC/PVC statistics for given interface (optional)

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

dspipif [<interface>]

Where:

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

svcifconfig—Configure SVC address information for an IP interface

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

Where:

<interface>—atmX, where X is the unit number (currently X is 0)

router | local <AESA>—Specify whether the given AESA address corresponds to a router or the local PXM. One of the keywords "router" or "local" must be specified. The <AESA> is an NSAP address used by the router or the local PXM.

[arp | noarp]—Specify whether ATMARP is enabled or disabled on this SVC (optional). Interface must also support ARP for ATMARP to be available (see ipifconfig above).


Note This parameter is valid for router AESA configuration only.


[llcsnap | vcmux]—Specify the encapsulation method to be used on the SVC. llcsnap corresponds to LLC Snap encapsulation, while vcmux is for VC Based Multiplexing.


Note This parameter is valid for router AESA configuration only.


[default | nodefault]—Use this SVC as the default route on the interface or disable this SVC as the default route (optional)

[reset]—Force reset on the SVC. SVC call is released, then the call is attempted again (optional)

[delete]—Delete the specified AESA configuration (optional)

[clrstats]—Clears all SVC statistics on this interface (optional)

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

dspsvcif [<interface>]

Where:

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

pvcifconfig—Configure PVC address information for an IP interface

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

Where:

<interface>—atmX, where X is the unit number (currently X is 0)

router | feeder <PVC>—Specify whether the given PVC address corresponds to a router or a feeder interface. One of the keywords router or feeder must be specified. The <PVC> is a PVC address of the form VPI.VCI used by the router or the feeder interface.

[arp | noarp]—Specify whether ATMARP is enabled or disabled on this PVC (optional). Interface must also support ARP for ATMARP to be available (see ipifconfig above).


Note This parameter is valid for router AESA configuration only.


[llcsnap | vcmux]—Specify the encapsulation method to be used on the PVC.

llcsnap corresponds to LLC Snap encapsulation, while vcmux is for VC Based Multiplexing.


Note This parameter is valid for router AESA configuration only.


[default | nodefault]—Use this PVC as the default route on the interface or disable this PVC as the default route (optional)

[up]put the PVC into UP state and attempt to bind the lcns associated. PVC must exist (optional)

[reset]—Force reset on the PVC. PVC is placed back into SETUP state (optional)

[delete]—Delete the specified PVC configuration (optional)

[clrstats—Clear all PVC statistics on this interface (optional)

dsppvcifDisplay PVC address information for one or all IP interfaces supporting PVC

dsppvcif [<interface>]

Where:

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

dspipifcacheDisplay interface cache translation table for one or all interfaces

dspipifcache [<interface>]

Where:

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

dspipconntask—Display IP Connectivity task information (Debug command)

dspipconntask

setipconndebugset debug level for IP Connectivity task (Debug command)

setipconndebug [debuglevel]

Where:

[debuglevel]—Value specifying one or more of the following:

NO LOGGING:      0x0
TASK ERRORS:     0x1
TASK DEBUG:      0x2
ATM PROTOCOL:    0x4
TASK STARTUP:    0x8
TASK EVENTS:     0x10
SIGAPI:          0x20
ATMARP PROTOCOL: 0x40
TASK TIMERS:     0x80
INTERFACE CACHE: 0x100
SUBTASK EVENTS: 0x200
DISKDB EVENTS:   0x400
RAMDB EVENTS:    0x800
ALL LOGGING:     0xffffffff

Caveats

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

Anomalies Resolved in CWM Release 11.0.10 Patch 2

Table 13 lists the anomalies resolved in CWM Release 11.0.10 Patch 2 as of 4/5/03.

Table 13 Anomalies Resolved in CWM Release 11.0.10 Patch 2 

Bug Id
Description

CSCdz90255

CWM: Only 19 of 50 nodes shows up in the SCM.

CSCdz48752

ooemc add msg is sent with msgType=2

CSCin33420

Connection retrieval using PC client does not re

CSCea17654

LineProxy core dump on CWM 11.0.10 P1 bundle3

CSCea17427

CWMGateway core dump on 11.0.10 P1 bundle3

CSCea17618

xcmgrd core dump on cwm 11.0.10 P1 bundle3

CSCin34455

Informix process stops

CSCin25866

TB+MR: PXM-OC3 port speed shows as 353208 bits/s

CSCdz56529

scmcollsvr coredumps when stop coll on same nodeid/slot is done twice

CSCdz68735

Cannot modify cwmVismEndPointPCR on VISM-PR end

CSCdz17262

emc coredumps on CWM release 11.0.10SOL28 (binar

CSCdz67873

Cancel timer before ProcessTimers causes timer

CSCdz01346

Summary report gives over 100% for the port util

CSCdz49996

On standalone parser, one of the statsparsers is

CSCin26569

TB+MR: NWBrowser does not show newly added port

CSCdz85028

FRSM12 port create fails, Set on Illegal object

CSCdz61652

xpvc parm mods fail, Proxy error returned

CSCin26058

TB+MR:SCT:Deletion of sctfile from secondary is

CSCin27121

TB+MR:node_info table not getting updated after

CSCea00921

Proxy blocks setting of frEndPointPIR greater th

CSCea03534

GET on svFrPortSigProt returns incorrect val aft

CSCea03854

Conntrace should not be blocked by CWM for faile

CSCdz17729

Config restore fails if underscore used in node

CSCea07782

RowStatus needs to be SET on PNNI version less t

CSCin33368

Unable to add UVM-UVM connection via CMGUI

CSCdz28135

feeder trunk shows green (no alarm) when AXSM is

CSCdz54777

frEndPointEgressQSelect mod fails from proxy [eg

CSCdz78060

Virtual ports on MGX88x0 nodes are automatically

CSCdz83475

Proxy Conn add fails if PXM 8 is active and no P

CSCdz87202

ConnProxy coredump while doing snmp walk on svCo

CSCdz56506

statsparser is not getting complete list of scmc

CSCdz88836

SCM GUI shows card as E even though collection i

CSCea10274

SNMP Get svCardEgrQOSFeature for PXM1E/FRSM-VHSH

CSCin21587

SCM: Disable stats status not reflected correctl

CSCin26564

cnfds3ln on FRSM 2CT3 line adds new ds1 line in

CSCdz28779

Addcon failed, FRM-UXM on IGX Feeder node

CSCdz69421

Statistic Parser Error SCMSA

CSCea02653

ooemc race loop condition problem

CSCea18417

Links not deleted during topo resync after clrsm

CSCdz87499

statsparser slow, many ftp files backing up in

CSCea16767

Option #4 on CWM Main Menu provides no added val

CSCea17903

Cmsvr causes informix access problem with wdserv

CSCin11233

portproxy: unable to add BXM-STM-OC3 port

CSCin35561

Can not add std-abr connection on FRSM-2CT3 on 8

CSCea20633

CWM GUI restricts setting to the same FGCRA valu

CSCdy88372

CWM: No statistics are collected for an alm card

CSCdz46683

WingZ is unable to report physical line (FR out

CSCdz25721

scm generates badfilelist when node name is chan

CSCea11169

ConnTrace maximum length can exceed 255

CSCea36113

config save needs to check for inconsistent outp

CSCdz70141

SCM stat files are received 1 hour delayed from

CSCea09677

FTP exception error logged on svpluscwm1 console

CSCea10469

Java exception after launching Image downloader

CSCea21831

xdbroker timeouts affect provisioning

CSCea25547

SCM java exception when modifying stats collecti

CSCea27330

Setting the IP_TOS flags for FTP sockets can cau

CSCea30069

SCM stat files delayed over time (cwmftpd)

CSCin16127

TB+SOL2.7: Logical slot for a secondary card(sta

CSCin25836

pvc connections remain on GUI after card is pull

CSCin36352

Card and port not shown in SCT gui after associa

CSCea44102

cmsvr coredump on Diag Center line loopback

CSCea01605

AXSME Stats File has wrong SubObjectId for Port

CSCea17584

scmcardfamilystat not getting uploaded during th

CSCea41069

SCT Daemon sync up takes long time

CSCea42489

adding runwingz softlink and removing Wingz from

CSCea43091

Forced resync causes trk port to be seen by EMC

CSCdz20797

vism card table not updated on IP address change

CSCin24735

TB+MR:AXSM-16OC3 bc_type is populated as Missing

CSCdz44767

multiple statsparser processes are launched

CSCdy86173

SCM collection server takes too long to start/st

CSCdz67109

Node resync queue is corrupted in emc

CSCdz67911

Array out-of-bound write may happen in BuildVarB

CSCdz76898

Node Delete using Configurator PER 7144

CSCdz16818

Trapd.conf file missing FRSM SAR overflow trap f

CSCdx37888

SV+Service.mib svCeEndPointBufMaxSize descriptio

CSCdz69875

Inconsistency between SV+Service.mib and Proxy e

CSCdz75934

atmEndPointHiCLP set to 0 for AUSM(MGX8250) abr-

CSCin26628

Inconsistent Display of CESM Card info acr

CSCdz29139

CWM: network broswer showed 2 extra DS1 line for

CSCin30788

CMGUI, MOD: Default channel type not visible for

CSCdy63369

ftp exceptions thrown on console when database h

CSCdz56554

SCM script needs to be modified to invoke runorb

CSCdz44082

Resource Capacity reports dont include IGX ATM p

CSCea28338

Wingz doesnt extract virtual asi port stats

CSCdz42258

CWM-display CES port level should be viewed in b

CSCea19403

CESM incomplete connection subtypes changes from

CSCdz52358

3 segs fr-fr(pvc) fail/clr trap on hpov , wrong

CSCdz79423

cmgrd throws wrong error when tried to add conn

CSCea33268

Diag Center: Object Finder doesnt get conns for

CSCdy31682

Raw Data report cannot produce stats for PXM-1 T

CSCea20292

svFrPortIfType should be updated for bc val 62 &

CSCea32205

Workaround needed in CWM for MGX bug CSCea31928

CSCea42496

Adding health monitor messages for each ftp/tftp

CSCdx61219

Patch2:SNMPwalk returns wrong TestType for atmEn

CSCin31053

Proxy not allowed to modify the Frame scrambling

CSCin26150

Event log message on HPOV alarms browser for tra

CSCea53665

Node resync need to clear out the port agg status

CSCea55153

Clean-up REVERT operation


Known Anomalies in CWM 11.0.10 Patch 2 Software

Table 14 lists the known anomalies in CWM Release 11.0.10 Patch 2 software.

Table 14 Known Anomalies in CWM Release 11.0.10 Patch 2 Software 

Bug ID
Description

CSCin36910

SES 1.1(79.102) returns NO SUCH NAME for mib object cwaChanOamSegEpEnable

Symptom:Added RPM-XF:AUSM connection in one CWM shown as incomplete in other CWM looking in the same network.

Conditions: Add RPM-XF:AUSM connection in one CWM and check in other CWM.

Workaround: None

CSCdx72708

Improve EMC log messages

Symptom:

1. When missing trap, log did not display node id.

2. The conn trap messages split to several lines. hard to grep meaningful data from one shot.

Conditions:

None

Workaround:

None

CSCdx76945

Need new value for mode field in node table for resync failure

Symptom:

When node/card resync is failed, the mode field in node table will change to "4" or "5", even if the node/card has been successfully resync'd before. Should have another value in the field to tell the node has been synced up before. A field in node/card table may be added to record the last time at which the node/card was synced up.

Condition:

None

Workaround:

Unknown.

CSCdy19807

Wrong alarm on collapsed trunks

Symptom:

Trunks with false alarm only when collapsed.

Conditions:

Not clear.

Workaround:

Refresh. Expanded view of trunks shows correct alarm.

CSCdy31692

We can't change UPC Threshold for vbr3-nrt connection on Connection Manager

Symptom:

Modified values doesn't reflect on CMGUI for UPC Threshold parameters on vbr3_nrt ATM-ATM PVC

Conditions:

When modifying UPC Threshold parameters on vbr3_nrt ATM-ATM PVC on BXM side in BPX SW image 9.2.x

Workaround:

None

CSCdy33589

CLR values displayed for PXM1E does not match with switch default values

Symptom:

CWM GUI shows diff default values for COSB SCT for PXM1E then what is displayed by switch

Conditions:

Do dspportsct cosb <portNum> on switch Compare with COSB tab display for CLR

Workaround:

None. This is not service affecting. The default values displayed on CWM are incorrect. Switch values should be considered correct.

CSCea43091

Unknown exception message for launching CM application from desktop.

Symptom:

sdatabroker stuck in loop and cannot add conns. from the MGX8250 node.

Conditions:

Forced resync was done on the MGX8250 node.

Workaround:

None

CSCea65793

User information not shown until hit Enter with MGX8220

Symptom:

End user should be able to see what he/she has entered.

Conditions:

Normal mode

Workaround:

No workaround

CSCdy71243

POP2 nodes failed to resync because of timeout (LSNT emulator related)

Symptom:

POP2 nodes failed to resync on ent4500 machine

Conditions:

Soak test the CWM for a day

Workaround:

Manually resync the nodes

CSCea07963

rtm core dump

Symptom:

rtm core dump

Conditions:

CWM 11.0.10 P1(Bin_Bundle 1)

Workaround:

unknown

CSCdy82218

Dup of CSCdy71243

SNMP Module: Nodes failed to resync

Symptom:

CWM failed to resync pop2 nodes after first sync. All the pop2 nodes went to mode 5 and never synced up again.

Conditions:

Soak test the CWM for a day.

Workaround:

Manually resync'd the nodes.

Current Status:

DE assigned. This scenario occurs because of the timing of the SNMP responses coming from the emulated nodes in the LSNT Network.

CSCdz55698

Topology - Display Trunk shows PNNI Protocol instead of Feeder

Symptom:

Topology - Display Trunk shows PNNI Protocol instead of Feeder

Conditions:

None.

Workaround:

None.

CSCdy83851

DiagServer coredumped on a CWM machine

Symptom:

DiagServer coredumped on one machine

Conditions:

Occurred during CWM core shutdown

Workaround:

None.

CSCdy84495

Topology shows trunk as clear after doing down & up LMI/ILMI on downed port

Symptom:

CWM shows feeder trunk as clear when the feeder trunk is down.

Conditions:

This happens when the below operations are performed.

1. Down the port using dnport at the MGX2 side.

2. Enable LMI using uplmi.

Workaround:

Enable/Disable LMI with the Port Admin status as UP.

CSCdy84607

A few AutoRoute trunks are not shown in Network Browser

Symptom:

Few AR trunks are missing from Network Browser

Conditions:

Network has BPX and MGX2 with XLMI and/or PNNI trunks

Network.conf is configured as Hybrid and have a BPX node as AR gateway

SNMP queries on the BPX fail intermittently.

Workaround:

Warmstart and make sure that snmp query for IP Address succeeds always

CSCdy85868

CWM installation hangs at CV install if cronjob leaves a /tmp/crout* file

Symptom:

Installation of CWM + CV hangs

Conditions:

When cronjob creates a /tmp/crontab* file after starting CWM installation and before CV installation starts

Workaround:

Remove all files /tmp/crontab* just before CV portion of the install starts

CSCdy87250

BPX node discovered as foreign node and got deleted from database

Symptom:

BPX node discovered as foreign node & got deleted from database

Conditions:

This is an intermittent problem seen on coldstarts.

Workaround:

Warmstart/Coldstart CWM.

CSCdz01188

On sunrise install, install does not complete

Symptom:

The webServer is not running

Conditions:

When CWM is installed for the first time on a new OS (either a regular install or using the upgrade option)

Workaround:

Follow these procedures in the "Issue with Upgrading or Installing CWM 11.0.10 on Systems that Use or Will Be Using Meta Devices or Multiple Disks for Informix" section of this release note.

CSCdz24906

GUI does not refresh when trunks is deleted

CSCin15035

Do not Save option in stats DB host config dialog is not working

Symptom:

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

Condition:

It happens when the "Do not Purge" option is chosen.

Workaround:

To manually delete the files from the purge directory once in every three days.


Anomaly Status Changes in Release 11.0.10 Patch 2

Table 15 lists the anomalies that have changed status in Release 11.0.10 Patch 2 as of 4/5/03. Changed status means that it changed from open in release 11.0.10 Patch 1 to a state other than resolved. The workaround states the status (closed, junked, duplicate, or unreproducible).

Table 15 Known Anomaly Status Changes in CWM Release 11.0.10 Software 

Bug ID
Description

CSCdy43172

Unknown exception message for launching CM application from desktop

Symptom:

Unknown exception

Conditions:

When launching CM application from topo desktop

Workaround:

Try once again to launch the application.

Resolved state

CSCdy46986

Onstat coredump occurred.

Symptom:

Onstat core dumped

Conditions:

Unknown

Workaround:

Unknown

Further Problem Description:

Onstat is used to get informix related parameters on the system.

This is never executed by any process as such.

Resolved state

CSCdy77648

Informix database got frozen

Symptom:

Unable to execute selnd command

Conditions:

On LSNT environment have CWM up and running for a day or two.

Workaround:

Stop core, coldstart -F and restart informix.

Resolved state

CSCdy82595

Conns ok in cwm after the node was powered down

Symptom:

270 out of ~12k Connections between Janus and Pop-2 were in ok state after the Janus node was powered down.

Conditions:

It seems that traps were sent from the switch and received in ooemc, but that the processing took some time. After more than one hour the status was updated.

Workaround:

node resync

Unreproducible state

CSCdy82895

Change in ATM IP of BPX loses feeder info from other GUIs except topo

Symptom:

Change in ATM IP of BPX loses feeder info from other GUIs except Topo

Conditions:

1. ATM IP of a BPX node is changed.

2. The BPX has feeders attached to it.

Workaround:

Unknown

Postponed state

CSCdz17729

Config restore fails if underscore used in node name

Symptom:

The Config Restore feature of CWM may fail depending on how the node is named.

Conditions:

The Config Restore feature of CWM does not work if the MGX node name contains an underscore.

Workaround:

Do not use an "_" in the MGX node name, or manually edit the file name on the MGX to match what CWM is looking for.

Resolved state

CSCin16127

Logical slot for a secondary card (standby) displays physicalslotnum

Symptom:

Logical slot for a secondary card (standby) displays physicalslotnum

Condition:

Add a redundancy on FRSM-2E3 card, pull out standby card and re-insert it after sometime.

Workaround:

Node Resync

Resolved state


Anomalies Resolved in CWM 11.0.10 Patch 1

Table 16 lists the anomalies resolved in CWM Release 11.0.10 Patch 1 as of 12/12/02.

Table 16 Anomalies Resolved in CWM Release 11.0.10 Patch 1 

Bug Id
Description

CSCdw83470

some nodes showing mgmt_state=0 even after synch up for a long time.

CSCdx34242

mvTrunk script -l option does not work at all

CSCdx37071

getting error during connection deletion when not reqd. external parameter is passed to script

CSCdx69213

Incomplete Connections that show up in CM but do not on the switch

CSCdx88531

local Abit alarm shows fail on CWM while okay on

CSCdy02369

when some sct popup dialog open, all apps gui ge

CSCdy04402

Description of Integrated Alarm in emd.conf is w

CSCdy07149

Wingz cannot produce stats for conn/port pxm

CSCdy10349

AddConn: FST not available on a non ABR connecti

CSCdy11559

pref_route, curr_route empty in logical_conn table, specific bins

CSCdy12747

BXM ports without vsi partition shouldnt show wh

CSCdy21986

Backcard desc fpr CHAMP not populated correctly

CSCdy22364

Not able to see the ports on CESM and AUSM from

CSCdy22457

same serial number for active/standby PXM cards

CSCdy28732

databroker should nt wait for last node sync up

CSCdy34740

svAtmPortSignallingProtocol cant be set for AXSM

CSCdy39184

LineProxy doesnt add intercard APS Line & send success to upper layer

CSCdy39198

Line Proxy doesnt configure any parameter other

CSCdy44803

Timeout period shown in minutes instead of secon

CSCdy48900

BXM-E trunks between BPXs not showing up in summ

CSCdy49182

GUI Should return objlist for containerType All

CSCdy50678

sdbroker coredump 11.0.10SOL28Aug15 P3

CSCdy53451

NWBrowser didnt show line# for AXSME-OC3/AXSME-T

CSCdy53847

XPVC batch grooming fails

CSCdy55251

CMGUI doesnt handle 64 character limit of Conn D

CSCdy58694

error message on the pc client java console for

CSCdy63705

Cannot create or edit old scm_template after 10510P2 to 11010 upgrade

CSCdy63910

descriptor is not shown on the table for standal

CSCdy65944

java exception on the console after doing click

CSCdy66934

XLMI link in alarm in the GUI

CSCdy68060

Security Manager does not show username which ha

CSCdy68077

SecMgr status bar shows 1st added profile/user i

CSCdy68551

rsc_part table upload fails after warmstart as d

CSCdy69893

databroker deletes connections for feeders during resync

CSCdy71294

Mode remains in 4 when both cards in redundancy

CSCdy73855

Network.conf file does fit neatly in to default 80x24 window (wraps)

CSCdy74480

Incomplete connection with CESM endpoint

CSCdy76296

Incorrect trap description for trap 60005

CSCdy76343

Sec mgr pop-up windows do not get closed after e

CSCdy76584

Standalone n/w active field sets to 0 on secondary after warmstart

CSCdy77191

CWMGateway on secondary CWM exits in an unexpect

CSCdy78416

Unblock provision between CESM T1 to E1 : Feature track

CSCdy78784

connections on IGX-HDM card are not populated in

CSCdy79995

sdbroker coredumped on upgrading a POP2 node with a feeder

CSCdy81083

ooemc coredumpd on cwmlab

CSCdy81115

Grooming feature does not groom all the XPVCs

CSCdy81481

Full upload got failed once because of table locking

CSCdy82072

scmcollsvr core dump is received on lscm9

CSCdy83911

Image downloader image sorting doesnt work prope

CSCdy83932

Java exception on java web start console for ope

CSCdy84477

RPM-PR images are not shown for PXM1E platform

CSCdy84487

All 4 ports card not supported on POP1/Pxm1 E bu

CSCdy84496

SES is showing all the images available under mg

CSCdy85958

IOSMGR is failing for config save for 8830 PXM1E

CSCdy86634

ConnProxy copies CIR to MIR, PIR & QIR for FRSM-12T3E3 STDABR connections

CSCdy86925

SCM Platform collection and parsing failure - sw

CSCdy87642

Upgrade support of card based SCM templates for

CSCdy87672

Connection count discrepancies on two CWMs at SLT/nw1

CSCdz00814

connection down status for and FR-FR SPVC (NBSM

CSCdz03737

PLCP support for axis node is missing

CSCdz04430

atmEndPointFGCRA does not return correct value f

CSCdz05033

unable to add rt-vbr spvc conns. betwn. POP2 and

CSCdz06329

mgx8220 nodes stuck in mode 5

CSCdz07580

Non-Default Comm. String snmpcomm expects SES Node Id.

CSCdz09817

Informix Crash on CWM, due to Informix bug

CSCdz13258

ooemc pauses for a long time when processing som

CSCdz13831

CMGUI after refresh showed wrong conn status for hybrid conn

CSCdz14449

Set frEndPointChanEgrSrvRate on FRSM 2ct3 card fails

CSCdz15821

AUSM atmEndPointEgressSrvRate implementation is

CSCdz17437

emsc log file have unnecessary info in log level

CSCdz19386

CosB drop down menu boxes not closing after sele

CSCdz20128

atmEndPointNRM=1 cannot be set on ATM-ATM PVC on

CSCdz20464

Wrong link status (major) shown in physical line

CSCdz20481

FR port added does not show up after a long time

CSCdz22257

atmEndPointClpTagging cannot be set with ATM-ATM

CSCdz22541

PER-3837: Add CiscoView to Security Mgr, problem

CSCdz23133

SCMSA not generating stats files after starting

CSCdz23501

Unqalified hostname problem with NWBrowser/Confi

CSCdz25203

CWM to set ausmIngrDiscardOpt to frameDisc when

CSCdz26392

Cannot create CBR.1 conn. on BXM-E3 w/Policing O

CSCdz27053

traps not received after injecting Mastership er

CSCdz29176

emsc fails to forward some connections msgs to d

CSCdz29206

scmcollsvr lost correct ftp passwd after abnorma

CSCdz29531

RPM POP1 conn add fails with err msg RPMPasswd n

CSCdz30101

frEndPointCIR range for FRSM HS1 cards wrong(0..

CSCdz30157

Stats DB Host Configuration empty after several

CSCdz30676

LDM card in standby state didnt get displayed in

CSCdz31335

Some workstations don't discover the BPX nodes in the network

CSCdz32678

CWM doesnot syncup the POP1 nodes when they are

CSCdz33059

Bogus error while adding FRSM port on HS2B with

CSCdz33234

A major alarm from MGX8850 is ahown as warning o

CSCdz36325

SCT manager Cosb tab VC threshold not clear sett

CSCdz36737

Upgrade from 10.4.10 to 11.0.10 scmsa

CSCdz37001

LportMaxBw, LPortMinVpi, LPortMaxVpi get returns

CSCdz37492

AuditLog permissions reset to all

CSCdz40490

Pop1 standalone enter via runconfigurator remain

CSCdz43709

cesm_connection on the non provison cwm l_port i

CSCdz44073

CMGUI-Cancel button in filter settings doesnt wo

CSCdz44226

emc fails to recover from port state change and conn status change fails

CSCdz44434

statistics .done file is not getting removed in

CSCdz44808

MGXRel2.x nodes get in mode 5 after a pas

CSCdz45003

XLMI link displayed incorrectly in topology.

CSCdz46059

cmgrd has to have a internal timeout for a reque

CSCdz48979

xcmgrd secondary gateway does not handle primary

CSCdz49071

HPOV patch install removes everything from ~/tmp

CSCin10666

Unable to add LDM to LDM connection on IGX via CCMGUI

CSCin13050

CMGUI: atmEndPointTBE & atmEndPointFRTT incorrec

CSCin15663

SCR range incorrect for BPX-ASI card in CMGUI, S


Anomaly Status Changes in Release 11.0.10 Patch 1

Table 17 lists the anomalies that have changed status in Release 11.0.10 Patch 1 as of 12/19/02. Changed status means that it changed from open in release 11.0.10 to a state other than resolved. The workaround states the status (closed, junked, duplicate, or unreproducible).

Table 17 Anomalies that have Changed Status in CWM Release 11.0.10 Patch 1 

Bug ID
Description

CSCdx76921

No error checking on shared memory transfers between em/emsc and dbroker

Symptom:

No error checking on shared memory calls when em/emsc sends notifications to databroker. No notification is sent for error, therefore.

Condition:

This happens all of the time.

Workaround:

None. Set to Closed.

CSCdy74732

Inconsistent alarm status on conns

Symptom:

3 connections in connection table out of ~6k had incorrect alarm status in the db of two CWMs. It is not reproducible at will.

Conditions:

On both workstations the core was running for 3 days prior to this error. There was no any specific activity on this node at the time when inconsistency was observed.

Workaround:

Node resync. Set to Unreproducible.

CSCdy76534

Alarm inconsistency on three segment connection

Symptom:

One connection was in alarm on one CWM, and was clear on the switch and other. CWM's were in sync for a few days.

Conditions:

There was no testing for that node at the time when this inconsistency was observed. The node was in mode 3 on all workstations.

Workaround:

Node resync. Set to Unreproducible.

CSCdy82595

Conns ok in cwm after the node was powered down

Symptom:

270 out of ~12k Connections between pxm1e and other non-pxm1e PNNI switch were in ok state after the pxm1e node was powered down.

Conditions:

It seems that traps were sent from the switch and received in ooemc, but that the processing took some time. After more than one hour the status was updated.

Workaround:

Node resync. Set to Unreproducible.


WANDEST Server Release 2.3 Patch 2.1

Table 18 lists the anomalies resolved in WANDEST Server Release 2.3 Patch 2.1.

Table 18 Anomalies Resolved in WANDEST Server Release 2.3 Patch 2.1 

Bug Id
Description
CSCea16996
Informix-stored procedure and id change
CSCea37764
wdserver get confuse on the last synch time calculation
CSCea55153
Clean-up REVERT operation

Anomalies Resolved in WANDEST Server Release 2.3 Patch 2

Table 19 lists the anomalies resolved in WANDEST Server Release 2.3 Patch 2.

Table 19 Anomalies Resolved in WANDEST Server Release 2.3 Patch 2

Bug Id
Description
CSCdz84941
warmstart secondary causes wdclient registration fail
CSCin28948
Core dump observed in Wandest Server while being restarted by watchdog
CSCdz68372
Wandest Server Dies periodically when used with StatusView

Anomalies Resolved in WANDEST Server Release2.3 Patch 1

Table 20 lists the anomalies resolved in WANDEST Server Release 2.3 Patch 1.

Table 20 Anomalies Resolved in WANDEST Server Release 2.3 Patch 1

Bug Id
Description
CSCdz22786
Wandest Client Registration to Server fails on secondary CWMs

Anomalies Resolved in WANDEST Client Release 2.3 Patch 2.1

Table 21 lists the anomalies resolved in WANDEST Client Release 2.3 Patch 2.1.

Table 21 Anomalies Resolved in WANDEST Client Release 2.3 Patch 2.1

Bug Id
Description
CSCea17584
scmcardfamilystat not getting uploaded during the incremental upload

Anomalies Resolved in WANDEST Client Release 2.3 Patch 2

Table 22 lists the anomalies resolved in WANDEST Client Release 2.3 Patch 2.

Table 22 Anamolies Resolved in WANDEST Client Release 2.3 Patch 2

Bug Id
Description
CSCea30195
wdclient coredump

Related Documentation

The following technical documents comprise the CWM 11 documentation set:

Cisco WAN Manager Installation for Solaris 7, 78-13567-01

Cisco WAN Manager Installation for Solaris 8, 78-14230-01

Cisco WAN Manager User's Guide, 78-13568-01

Cisco WAN Manager SNMP Service Agent, 78-13569-01

Cisco WAN Manager Database Interface, 78-13542-01

Release Notes for Cisco WAN Manager for Solaris 7, Release 11.0.10, OL-2910-01

Release Notes for Cisco WAN Manager for Solaris 8, Release 11.0.10, OL-2909-01

PDF copies of the CWM 11 documentation set are provided on the second CWM 11 CD along with a copy of Adobe Acrobat and Netscape Communicator 4.76 for use in reading the files.

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

Obtaining Documentation

These sections explain how to obtain documentation from Cisco Systems.

World Wide Web

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

http://www.cisco.com

Translated documentation is available at this URL:

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

Documentation CD-ROM

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

Ordering Documentation

You can order Cisco documentation in these ways:

Registered Cisco.com users (Cisco direct customers) can order Cisco product documentation from the Networking Products MarketPlace:

http://www.cisco.com/cgi-bin/order/order_root.pl

Registered Cisco.com users can order the Documentation CD-ROM through the online Subscription Store:

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

Nonregistered Cisco.com users can order documentation through a local account representative by calling Cisco Systems Corporate Headquarters (California, U.S.A.) at 408 526-7208 or, elsewhere in North America, by calling 800 553-NETS (6387).

Documentation Feedback

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

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

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

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

We appreciate your comments.

Obtaining Technical Assistance

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

Cisco.com

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

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

Streamline business processes and improve productivity

Resolve technical issues with online support

Download and test software packages

Order Cisco learning materials and merchandise

Register for online skill assessment, training, and certification programs

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

http://www.cisco.com

Technical Assistance Center

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

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

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

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

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

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

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

Cisco TAC Web Site

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

http://www.cisco.com/tac

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

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

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

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

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

Cisco TAC Escalation Center

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

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

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

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