Cisco WAN Manager

Table Of Contents

Release Notes for Cisco WAN Manager 12.0.00

Contents

System Requirements

CWM Server

Java Client

Standalone Statistics Manager

Solaris Patch Requirements

CWM Software Packaging

HP OpenView Requirements

INFORMIX Requirements

Wingz Requirements

Supported Hardware

Existing Hardware

New Hardware

Certified Releases

New Features and Enhancements in CWM Release 12

Features Introduced in CWM Release 12.0.00

ConnProvAnalyzer

New Features and Enhancements in WANCV Release 4.19

Features Not Supported in WANCV 4.19

Features Not Supported and Known Feature Limitations in CWM 12.0.00

Limitations

Ensuring the Creation of the svplus and/or wandest Username and Password

Connection Manager Limitations

HP OpenView Limitations

Issues with the CWM 12 Statistics Collection Manager

Limitations for CWM to CWM Communication

Topology Limitations

CWM 12 Notes and Cautions

Issues with Firewalls and CWM 12

Firewall on PC:

Firewall on LAN:

CWM 12.0.00 Server Installation or Upgrade to CWM 12.0.00

Evaluation Copy of CWM 12

Evaluation Copy limitations

Important Configuration Notes

Naming Managed Nodes

Node Numbering for Release 9.4 IGX Feeder Nodes

CWM Dedicated IP Ports

Security Profiles

CWM Database

Connection Manager Configuration

Configuration Parameters for Connection Manager Daemon (cmgrd)

Setting up RPM Cards for Management by CiscoView from the Workstation

Configuring SNMP and SYSLOG

Configuring CiscoView for Large Networks

SNMP Service Agent Release Notes

CWM SNMP Agent Configuration Notes

WANCV 4.19 Notes and Cautions

Performance

Caveats

Known Anomalies in CWM 12.0.00 Software

Anomalies Resolved in CWM 12.0.00 Software

Related Documentation

Obtaining Documentation

Cisco.com

Product Documentation DVD

Ordering Documentation

Documentation Feedback

Cisco Product Security Overview

Obtaining Technical Assistance

Cisco Technical Support & Documentation Website

Submitting a Service Request

Definitions of Service Request Severity

Obtaining Additional Publications and Information

Release Notes for Cisco WAN Manager 12.0.00

---

Rev. C0

May 2006

Cisco WAN Manager 12.0.00 software supports the following Cisco products as of May 2, 2003:

•Cisco MGX 8850 PXM45-based products running software releases 2.1.76 through 2.1.81, 3.0.10 through 3.0.20, or 4.0.00.

•Cisco MGX 8950 PXM45-based products running software releases 2.1.76 through 2.1.81, 3.0.10 through 3.0.20, or 4.0.00.

•Cisco MGX PXM1E-based products (8830 and 8850) running software releases 3.0.10 through 3.0.20, or 4.0.00.

•Cisco MGX PXM1-based products (8230, 8250 and 8850) running software releases 1.1.31 through 1.1.34, 1.1.40 through 1.1.42, 1.2.00 through 1.2.13, or 1.2.20.

•Cisco SES PNNI Controller running software releases 1.1.75 through 1.1.79, 3.0.10 through 3.0.20, or 4.0.00.

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

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

Contents

•System Requirements

•CWM Software Packaging

•Supported Hardware

•New Features and Enhancements in CWM Release 12

•New Features and Enhancements in WANCV Release 4.19

•Features Not Supported in WANCV 4.19

•Features Not Supported and Known Feature Limitations in CWM 12.0.00

•Limitations

•CWM 12 Notes and Cautions

•Important Configuration Notes

•Naming Managed Nodes

•Setting up RPM Cards for Management by CiscoView from the Workstation

•SNMP Service Agent Release Notes

•CWM SNMP Agent Configuration Notes

•WANCV 4.19 Notes and Cautions

•Known Anomalies in CWM 12.0.00 Software

•Anomalies Resolved in CWM 12.0.00 Software

•Related Documentation

•"Obtaining Documentation" section

•"Documentation Feedback" section

•"Cisco Product Security Overview" section

•"Obtaining Technical Assistance" section

•"Obtaining Additional Publications and Information" section

System Requirements

The following are additional notes for CWM platform requirements:

•CWM 12.0 is compatible with UltraSPARC II and UltraSPARC III. The previously certified Ultra 60, Enterprise 450 and Enterprise 4500 can still be used with CWM 12.0. Problems reported by customers who choose a non Cisco-tested configuration may take more time to troubleshoot, etc., thus a longer turnaround time.

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

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

CWM Server

Table 1 System Requirements - CWM Server 

CWM Platform	# CPU	Min CPU Speed MHz	Min. RAM GB	Min. Swap	Min Disk	Max # PVC/SPVC Conections or Connection segments for XPVC	Max. # PC Clients	Max. # Nodes	UltraSPARC III Server used for network scale testing by Cisco
Low - Medium	1	900	2 GB	4 GB	1 x 36 GB	100K	10	100	Netra 20, Sun Fire 280R
Medium	2	900	4 GB	8 GB	1 x 36 GB	200K	20	500	Netra 20, Sun Fire 280R
High - Carrier Grade	4	900	8 GB	16 GB	2 x 36 GB	1M	40	1000	Sun Fire V880
Carrier Grade	8	900	16 GB	32 GB	2 x 36 GB	2M	100	2000	Sun Fire V880

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

•If UltraSPARC II Servers are used, refer to the System Requirement Guidelines in the CWM release notes for Release 11.0.10.

Java Client

Table 2 System Requirements - Java Client 

CWM Java Client	Operating System	Web Browser	CPU	CPU Speed MHz	RAM	Swap	Disk	Monitor
PC	Windows 2000 Windows NT 4.0	Internet Explorer 6.0 Netscape 4.76	1 Pentium 3	750	256 MB	n/a	50 MB Free	y
SPARC10	Solaris 8	Netscape 4.76	1 450 Mhz	450	512 MB	1 GB	50 MB Free	y

Standalone Statistics Manager

Table 3 System Requirements - Standalone Statistics Collector or Manager 

SSC Platform	# CPU	Min CPU Speed MHz	Average Network Transfer Rate (KiloByte/Sec)	RAM	Swap	Disk	Max # of stats files (15 minute collection interval)	Server used in Cisco Testing
Low	2	450	170 KB/sec	512 MB	2 GB	2 x 18 GB	350	U60
Medium #1	2	450	3.5 MB/sec	512 MB	2 GB	2 x 18 GB	700	U60
Medium #2	1	900	1.7 MB/sec	1 GB	2 GB	1 x 36 GB	700	Netra 20 or Sun Fire 280R
High	2	900	3.5 MB/sec	4 GB	8 GB	1 x 36 GB	900	Netra 20 or Sun Fire 280R

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

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

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

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

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

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

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

SSM Platform	# CPU	Min CPU Speed MHz	RAM GB	Swap	Min. Disk	Monitor	Max # of Connection Segment Endpoints with Statistics Enabled	Server used for network scale testing by Cisco
Low	1	450	0.25	2GB	2 x 9 GBy		40K	Ultra 10
Low - Medium	2	450	1 GB	2 GB	2 x 18 GBy		300K	Ultra 60
Low - Medium	1	900	2 GB	4 GB	2 x 36 GB	y	750K	Netra 20, Sun Fire 280R
Medium	2	900	4 GB	8 GB	2 x 36 GB	y	2M	Netra 20, Sun Fire 280R
High - Carrier Grade	4	900	8 GB	16 GB	2 x 36 GB	y	4M	Sun Fire V880

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

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

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

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 12.0.00 release:

When you order the CWM Client/Server package, you receive the following 3 disks:

•CWM Server/Client CD 1 (Disk 1). This CD contains the following:

–CWM Server Software

–INFORMIX Server Software Release 9.21.UC5XAI

–CWM Java Client Software

•CWM Server/Client CD 2 (Disk 2). This CD contains the following:

–CiscoView Engine 5.4.1

–WANCV 4.19

–Netscape Communicator 4.76

•CWM Documentation CD (Disk 3). This CD contains the following:

–Acrobat Reader 4.0

–gzip

–PDF copy of the CWM 12 documentation set

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

•Service Agent CD. This CD contains the following

–CWM Service Agent Software

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

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

–Standalone SCM Software with WANDEST Client Software incorporated

–INFORMIX Server Software Release 9.21.UC5XAI

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

•WANDEST Release 2.4 Server CD

–WANDEST Server Software, Release 2.4

•WANDEST Release 2.4 Client CD

–WANDEST Client Software, Release 2.4

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

•Wingz Release 2.5.1 CD

The Wingz version number is located on the license key (a 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 12.0.00 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 12.0.00 release uses Informix 9.21.UC5XAI 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 12.0.00 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.

Supported Hardware

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

Existing Hardware

Table 5 lists the existing hardware supported prior to CWM 12.0.00.

Table 5 Supported Existing Hardware 

Platform Series	Front Card	Back Card	Supported Release Version
IGX 8400	NPM	SCM	SWSW 9.2.33 through 9.2.43, 9.3.05 through 9.3.45, or 9.4.00
IGX 8400	NTM	BC-T1/E1/SR/Y1	SWSW 9.2.33 through 9.2.43, 9.3.05 through 9.3.45, or 9.4.00
IGX 8400	BTM	AIT-T3/E3/E2/HSS1/E1	SWSW 9.2.33 through 9.2.43, 9.3.05 through 9.3.45, or 9.4.00
IGX 8400	FRM	FRI-T1/E1/V.35/X.21	SWSW 9.2.33 through 9.2.43, 9.3.05 through 9.3.45, or 9.4.00
IGX 8400	FTM	FPC-V35/T1/E1/X.21	SWSW 9.2.33 through 9.2.43, 9.3.05 through 9.3.45, or 9.4.00
IGX 8400	HDM	V.35/RS-449/RS-232C/RS-232D	SWSW 9.2.33 through 9.2.43, 9.3.05 through 9.3.45, or 9.4.00
IGX 8400	LDM	RS-2324/RS-2328/RS-232D	SWSW 9.2.33 through 9.2.43, 9.3.05 through 9.3.45, or 9.4.00
IGX 8400	CVM	BC-T1/E1/J1/Y1/SR	SWSW 9.2.33 through 9.2.43, 9.3.05 through 9.3.45, or 9.4.00
IGX 8400	UVM	UVI-2T1EC/2E1EC	SWSW 9.2.33 through 9.2.43, 9.3.05 through 9.3.45, or 9.4.00
IGX 8400	UFM-C	UFI-8T1/8E1-DB15,UFI-8E1-BNC	SWSW 9.2.33 through 9.2.43, 9.3.05 through 9.3.45, or 9.4.00
IGX 8400	UFM-U	UFI-V35/X21/HSI	SWSW 9.2.33 through 9.2.43, 9.3.05 through 9.3.45, or 9.4.00
IGX 8400	ARM	ARI	SWSW 9.2.33 through 9.2.43, 9.3.05 through 9.3.45, or 9.4.00
IGX 8400	UXM	UAI-4OC3MMF/40C3SMF/2OC3SMF/6T3/6E3/3T3/3E3/8T1-IMA/8E1-IMADB15/8E1-IMABNC	SWSW 9.2.33 through 9.2.43, 9.3.05 through 9.3.45, or 9.4.00
BPX 8600	BCC	BCC-bc/3-bc	SWSW 9.2.33 through 9.2.43, 9.3.05 through 9.3.45, or 9.4.00
BPX 8600	ASM	LM-ASM	SWSW 9.2.33 through 9.2.43, 9.3.05 through 9.3.45, or 9.4.00
BPX 8600	BNI-T3	LM-3T3	SWSW 9.2.33 through 9.2.43, 9.3.05 through 9.3.45, or 9.4.00
BPX 8600	BNI-E3	LM-3E3	SWSW 9.2.33 through 9.2.43, 9.3.05 through 9.3.45, or 9.4.00
BPX 8600	BNI-155	LM-OC3-SMF/SMFLR/MMF	SWSW 9.2.33 through 9.2.43, 9.3.05 through 9.3.45, or 9.4.00
BPX 8600	ASI-1	LM-2T3/2E3	SWSW 9.2.33 through 9.2.43, 9.3.05 through 9.3.45, or 9.4.00
BPX 8600	ASI-155	LM-2OC3-SMF/SMFLR/MMF	SWSW 9.2.33 through 9.2.43, 9.3.05 through 9.3.45, or 9.4.00
BPX 8600	BXM-T3/E3	T3/E3-BC	SWSW 9.2.33 through 9.2.43, 9.3.05 through 9.3.45, or 9.4.00
BPX 8600	BXM-15 5	MMF/SMF/SMFLR-155	SWSW 9.2.33 through 9.2.43, 9.3.05 through 9.3.45, or 9.4.00
BPX 8600	BXM-622	MMF/SMF/SMFLR-622	SWSW 9.2.33 through 9.2.43, 9.3.05 through 9.3.45, or 9.4.00
SES PNNI Controller	SES-PXM	PXM-UIA	1.1.75 through 1.1.79, 3.0.10 through 3.0.20, or 4.0.00
SES PNNI Controller	SES-PXM	PXM-UIA	1.1.75 through 1.1.79, 3.0.10 through 3.0.20, or 4.0.00
SES PNNI Controller	SES-PXM	PXM-UIA	1.1.75 through 1.1.79, 3.0.10 through 3.0.20, or 4.0.00
SES PNNI Controller	SES-PXM	PXM-UIA	1.1.75 through 1.1.79, 3.0.10 through 3.0.20, or 4.0.00
MGX 8220	FRSM-4P	DB-15-4T1/4E1, BNC-4E1	4.1.07 through 4.1.12, or 5.0.12 through 5.0.19
MGX 8220	CESM-4P	DB-15-4T1/4E1, BNC-4E1	4.1.07 through 4.1.12, or 5.0.12 through 5.0.19
MGX 8220	AUSM-4P	DB-15-4T1/4E1, BNC-4E1	4.1.07 through 4.1.12, or 5.0.12 through 5.0.19
MGX 8220	FRSM-8P	RJ48-8T1/8E1, SMB-8E1	4.1.07 through 4.1.12, or 5.0.12 through 5.0.19
MGX 8220	AUSM-8P	RJ48-8E1/8T1	4.1.07 through 4.1.12, or 5.0.12 through 5.0.19
MGX 8220	CESM-8P	RJ48-8T1/8E1, SMB-8E1	4.1.07 through 4.1.12, or 5.0.12 through 5.0.19
MGX 8220	IMATM-B	RJ48-T3T1/E3E1/E3T1/T3E1	4.1.07 through 4.1.12, or 5.0.12 through 5.0.19
MGX 8220	FRSM-HS1	HSI-4X21/3HSSI	4.1.07 through 4.1.12, or 5.0.12 through 5.0.19
MGX 8220	BNM-T3/E3	T3E3-B/D	4.1.07 through 4.1.12, or 5.0.12 through 5.0.19
MGX 8220	BNM-155	155-SMF	4.1.07 through 4.1.12, or 5.0.12 through 5.0.19
MGX 8220	SRM	DB-15-T1/E1, LM-3T3	4.1.07 through 4.1.12, or 5.0.12 through 5.0.19
MGX 8220	ASC	ASC-LM	4.1.07 through 4.1.12, or 5.0.12 through 5.0.19
MGX 8220	FRSM-VHS	HS2	4.1.07 through 4.1.12, or 5.0.12 through 5.0.19
MGX 8220, MGX 8230, MGX 8250, MGX 8850 PXM1	AUSM Model B	8T1/E1	4.1.07 through 4.1.12, or 5.0.12 through 5.0.19, 1.1.31 through 1.1.34, 1.1.40 through 1.1.42, 1.2.00 through 1.2.13, or 1.2.20
MGX 8230, MGX 8250, MGX 8850 PXM1	PXM1	T3/E3/OC3/OC12	1.1.31 through 1.1.36, 1.1.40 through 1.1.42, 1.2.00 through 1.2.13, or 1.2.20
MGX 8230, MGX 8250, MGX 8850 PXM1	FRSM-VHS	HS2/T3/E3/2CT3/HS2B	1.1.40 through 1.1.42, 1.2.00 through 1.2.13, or 1.2.20
MGX 8230, MGX 8250, MGX 8850 PXM1	FRSM-8P	RJ48-8T1/8E1, SMB-8E1	1.1.40 through 1.1.42, 1.2.00 through 1.2.13, or 1.2.20
MGX 8230, MGX 8250, MGX 8850 PXM1	CESM-8P	RJ48-8T1/8E1, SMB-8E1, RJ48-8T1-C/8E1-C, SMB-8E1-C	1.1.40 through 1.1.42, 1.2.00 through 1.2.13, or 1.2.20
MGX 8230, MGX 8250, MGX 8850 PXM1	CESM	T3/E3	1.1.40 through 1.1.42, 1.2.00 through 1.2.13, or 1.2.20
MGX 8230, MGX 8250, MGX 8850 PXM1	SRM	LM-3T3	1.1.40 through 1.1.42, 1.2.00 through 1.2.13, or 1.2.20
MGX 8230, MGX 8250, MGX 8850 PXM1	VISM-8T1	AX-RJ48-8T1 AX-R-RJ48-8T1	1.1.40 through 1.1.42, 1.2.00 through 1.2.13, or 1.2.20
MGX 8230, MGX 8250, MGX 8850 PXM1	VISM-8E1	AX-SMB-8E1 AX-RJ48-8E1 AX-R-SMB-8E1 AX-R-RJ48-8E1	1.1.40 through 1.1.42, 1.2.00 through 1.2.13, or 1.2.20
MGX 8230, MGX 8250, MGX 8850 PXM1	VISM-PR	RJ48-T1/E1 and SMB-E1	1.2.10 through 1.2.13, or 1.2.20
MGX 8950 (PXM45)	AXSM-B	T3/E3	2.1.76 through 2.1.81, 3.0.10 through 3.0.20, or 4.0.00
MGX 8950 (PXM45)	AXSM-B	OC3	2.1.76 through 2.1.81, 3.0.10 through 3.0.20, or 4.0.00
MGX 8950 (PXM45)	AXSM-B	OC12	2.1.76 through 2.1.81, 3.0.10 through 3.0.20, or 4.0.00
MGX 8950 (PXM45)	AXSM-B	OC48	2.1.76 through 2.1.81, 3.0.10 through 3.0.20, or 4.0.00
MGX 8950 (PXM45)	PXM45	PXM-HD, PXM-UI	2.1.76 through 2.1.81, 3.0.10 through 3.0.20, or 4.0.00
MGX 8950 (PXM45)	PXM45B	PXM-HD, PXM-UI	2.1.76 through 2.1.81, 3.0.10 through 3.0.20, or 4.0.00
MGX 8950 (PXM45)	RPM-XF	MGX-1GE and MGX-1OC12POS	3.0.10 through 3.0.20, or 4.0.00
MGX 8850 (PXM45)	AXSM	T3/E3	2.1.76 through 2.1.81, 3.0.10 through 3.0.20, or 4.0.00
MGX 8850 (PXM45)	AXSM	OC3	2.1.76 through 2.1.81, 3.0.10 through 3.0.20, or 4.0.00
MGX 8850 (PXM45)	AXSM	OC12	2.1.76 through 2.1.81, 3.0.10 through 3.0.20, or 4.0.00
MGX 8850 (PXM45)	AXSM	OC48	2.1.76 through 2.1.81, 3.0.10 through 3.0.20, or 4.0.00
MGX 8850 (PXM45)	AXSM-E	T3/E3	2.1.76 through 2.1.81, 3.0.10 through 3.0.20, or 4.0.00
MGX 8850 (PXM45)	AXSM-E	OC3	2.1.76 through 2.1.81, 3.0.10 through 3.0.20, or 4.0.00
MGX 8850 (PXM45)	AXSM-E	OC12	2.1.76 through 2.1.81, 3.0.10 through 3.0.20, or 4.0.00
MGX 8850 (PXM45)	AXSM-E	OC48	2.1.76 through 2.1.81, 3.0.10 through 3.0.20, or 4.0.00
MGX 8850 (PXM45)	PXM45	PXM-HD, PXM-UI	2.1.76 through 2.1.81, 3.0.10 through 3.0.20, or 4.0.00
MGX 8850 (PXM45)	PXM45B	PXM-HD, PXM-UI	2.1.76 through 2.1.81, 3.0.10 through 3.0.20, or 4.0.00
MGX 8850 (PXM45)	RPM-XF	MGX-1GE and MGX-1OC12POS	3.0.10 through 3.0.20, or 4.0.00
MGX 8850 (PXM45)	VISM-PR	RJ48-T1/E1 and SMB-E1	3.0.10 through 3.0.20, or 4.0.00
MGX 8850 (PXM1E)	PXM1E	8 Port 155	3.0.10 through 3.0.20, or 4.0.00
MGX 8850 (PXM1E)	PXM1E	8 Port T3/E3	3.0.10 through 3.0.20, or 4.0.00
MGX 8850 (PXM1E)	RPM-PR	Ethernet, Fast Ethernet	3.0.10 through 3.0.20, or 4.0.00
MGX 8850 (PXM1E)	VISM-PR	RJ48-T1/E1 and SMB-E1	3.0.10 through 3.0.20, or 4.0.00
MGX 8850 (PXM1E)	AUSM Model B	8T1/E1	3.0.10 through 3.0.20, or 4.0.00
MGX 8850 (PXM1E)	FRSM-8P	RJ48-8T1/8E1, SMB-8E1	3.0.10 through 3.0.20, or 4.0.00
MGX 8850 (PXM1E)	CESM-8P	RJ48-8T1/8E1, SMB-8E1, RJ48-8T1-C/8E1-C, SMB-8E1-C	3.0.10 through 3.0.20, or 4.0.00
MGX 8850 (PXM1E)	FRSM-HS2B	8 port 12in1, HSSI	3.0.10 through 3.0.20, or 4.0.00
MGX 8850 (PXM1E)	SRM/E	1 port OC3/STM1 (SMF-IR, SMF-LR, SMF-Electrical)	3.0.10 through 3.0.20, or 4.0.00
MGX 8230, MGX 8250, MGX 8850 (PXM1)	FRSM-HS2B	8 port 12in1, HSSI	1.2.00 through 1.2.13, or 1.2.20
MGX 8230, MGX 8250, MGX 8850 (PXM1)	SRM/E	1 port OC3/STM1 (SMF-IR, SMF-LR, SMF-Electrical)	1.2.00 through 1.2.13, or 1.2.20
MGX 8230, MGX 8250, MGX 8850 (PXM1)	RPM/B	Ethernet, Fast Ethernet	1.2.00 through 1.2.13, or 1.2.20
MGX 8230, MGX 8250, MGX 8850 (PXM1)	RPM-PR	Ethernet, Fast Ethernet	1.2.00 through 1.2.13, or 1.2.20
MGX 8230, MGX 8250, MGX 8850 (PXM1)	VISM-PR	RJ48-T1/E1 and SMB-E1	1.2.00 through 1.2.13, or 1.2.20

New Hardware

Table 6 lists the new hardware supported in CWM 12.0.00.

Table 6 Supported New Hardware 

Platform Series	Front Card	Back Card	Supported Release Version
MGX 8950 (PXM45)	AXSM-XG	OC192	4.0.00
MGX 8950 (PXM45)	AXSM-XG	OC48	4.0.00
MGX 8950 (PXM45)	PXM45/C	PXM-HD, PXM-UI	4.0.00
MGX 8850 (PXM45)	PXM45/C	PXM-HD, PXM-UI	4.0.00
MGX 8850 (PXM45)	FRSM-8P	RJ48-8T1/8E1, SMB-8E1	4.0.00
MGX 8850 (PXM45)	CESM-8P	RJ48-8T1/8E1, SMB-8T1B	4.0.00
MGX 8850 (PXM45)	FRSM-HS2B	8 port 12in1, HSSI	4.0.00
MGX 8850 (PXM45)	FRSM-VHS	2CT3	4.0.00
MGX 8850 (PXM45)	SRM/E	1 port OC3/STM1 (SMF-IR, SMF-LR, SMF-Electrical)	4.0.00
MGX 8830/8850 (PXM1E)	PXM1E	8 port OC3 STM1	4.0.00
MGX 8830/8850 (PXM1E)	FRSM-VHS	2CT3	4.0.00

Certified Releases

The following releases were tested with CWM release 12.0.00:

•BPX Switch Software:

–Switch Software 9.4.00

–Switch Software 9.3.42

–Switch Software 9.3.36

–Switch Software 9.2.43

•MGX 8230/8250/8850 (PXM1) Switch

–MGX 1.2.20

–MGX 1.2.13

–MGX 1.1.42

–MGX 1.1.34

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

–MGX 4.0.00

–MGX 3.0.20

–MGX 2.1.81

•BPX SES Shelf

–SES 4.0.00

–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.10 (PXM1-based switches only)

–VISM 2.2.10

–VISM 1.5.08

New Features and Enhancements in CWM Release 12

Features Introduced in CWM Release 12.0.00

This section describes the new features introduced in the Cisco WAN Manager 12 release.

•MGX 8850, Release 4

–Support for PXM45/C (512MB memory, memory protection feature, and Ethernet Controller)

–Support for Cellbus-based Frame Relay and Circuit Emulation support on PXM45-based switches (CESM-8T1E1, CESM-8T1/B, FRSM-VHS 2CT3, FRSM-8T1E1)

–Support for the IMA UNI Port on the AXSM-E32T1E1 service module

•MGX 8950, Release 4

–Support for PXM45/C (512MB memory, memory protection feature, and Ethernet Controller)

–Support for AXSM-XG 4-Port Channelized OC-48 Service Module (Unchannelized and Channelized to OC-12/STM-4, OC-3/STM1 and T3/E3 logical ATM interfaces) and the AXSM-XG 1-Port OC-192 Service Module

•SES, Release 4

–Support for configuring PCR to burst to line rate on SPVC connections using the Connection Manager GUI

–Support for configuring PCR to burst to line rate on SPVC connections using the CWM Service Agent

•BPX 8600 and IGX 8400, Release 9.4.00 support

–Support for configuring and managing hybrid PNNI connections that allow the use of the IGX as a feeder node to the PNNI network (the IGX UXM can be connected to the BPX-SES, the PXM1E, or the AXSM-E)

•Release 1.2.20 (8850, 8250, 8230 with PXM1)

–Support for Configurable AUSM CAC. You can configure the AUSM card to use either PCR or SCR for CAC. The default is PCR.

•MGX 8850 and 8830 Release 4 (PXM1E-based nodes)

–Support for the provisioning and management of the PXM1E 8-Port OC-3 & STM-1 Service Module with 512M memory backcard

–Support for the provisioning and management of the CESM-8T1E1, CESM-8T1/B, FRSM-VHS 2CT3, FRSM-8T1E1 Service Modules

–Support for the IMA UNI Port on the PXM1E-T1E1

–Support for PXM1E on-line diagnostics traps through the Service Agent

–Support for Virtual Trunk and Virtual UNI on the PXM1E management through the Service Agent

•CWM-specific Enhancements

–Evaluation Copy of CWM 12—The 90-day evaluation copy of CWM gives you the opportunity to try CWM for a 90-day period.

–Enhanced Standalone Statistics Collection Management—The enhanced Standalone Statistics Collection Manager is now totally independent from the CWM server. You can perform maintenance on CWM without affecting the SCM operations and vice versa.

–There are two supported configurations:

1. Standalone Statistics Manager (SSM)—The Standalone Statistics Manager (SSM) consists of the Standalone SCM with Control Server, Collection Server and Statistics Parser installed together on a workstation seperate from the CWM server workstation The WANDEST server software must be installed and configured on the CWM server workstation and the WANDEST client software must be installed on the standalone SCM workstation.
SSM uses the WANDEST client to synchronize the network equipment data (node and card) from the CWM server workstation.

2. Standalone Statistics Collector (SSC)—Standalone SCM can be configured as a Standalone Statistics Collector (SSC) to work with SSM or CWM Server to further distribute the statistics collection function to a second separate workstation (separate from the SSM). In this configuration, the Statistics Collection Controller and, optionally, the Statistics Parser function will still reside on either the SSM or the CWM server.

–Enhanced SSC/SSM redundancy

–Point-to-multipoint SPVC Provisioning

–Single-end SPVC Provisioning

–SNMP Community String configuration using Secure Shell (SSH)

–Enhanced Audit Trail Log
The Audit Trail Logging feature now logs all Read-only and Read-Write operations performed by the Java-based CWM GUI and CiscoView.

–Network Topology now provides primary and secondary status of the ports configured for SONET Automatic Protection Switch.

–PNNI Multi-peer Group configuration via Service Agent

–Enhanced Network Events Monitoring
BPX related 20000 Series and 30000 Series traps are forwarded to port 162 for HP OpenView and to RTM for Service Agent. The Source IP address in the BPX 1000 series Traps reflects the IP address of the associated node instead of the CWM IP address. BPX 1000 series traps are only forwarded to port 162, not to RTM.

–PNNI Persistent Physical Topology
CWM 12 adds support for routing trunk persistency.

–Enhanced PNNI Statistics Collection
CWM Statistics Collection Manager now collects historical PNNI related statistics from PXM45/B, PXM45/C and PXM1E-based nodes.

–Enhanced Scalability for Large-Scale Network Management

–Support for WANDEST 2.4

–Support for AXSM-E Port Statistics

–Support for new PXM1 Port Statistics

–Support for additional AUSM Port Statistics

–Support for additional FRSM Connection and Port Statistics

–XPVC/XPVP Management Enhancement
XPVC connection data no longer needs the manual XPVC grooming tool during upgrade to CWM 12. XPVC connections are now discovered from the network by CWM.

–Preferred Route Provisioning

–Support for Closed User Groups

For information on WANDEST 2.4, refer to the Cisco WANDEST Installation and Reference, Release 2.4, OL-4122-01, available at this URL:

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

ConnProvAnalyzer

This new tool analyzes connection provisioning delay and errors using available conn proxy log files and generates reports and creates a separate log file for errors. The off-line tool is located in ~svplus/tools/ConnProvAnalyzer.

The generated data can be used for plotting in Wingz or Microsoft Excel.

This tool extracts CNPA pattern entry from the ConnProxy log messages and will do analysis for successful requests then writes into .csv & .req files. The .csv data can be used for plotting graphs by using applications like Excel or Wingz.

In the .csv file, column-I indicates the connection & column-II indicates Provisioning time.

Xaxis: represents the Connection

Yaxis: represents the Provisioning Time

Plotting a Graph in Excel:

---

Step 1 Invoke Excel and open the .csv file.

Step 2 Select A, B columns for all rows (or for how many ever connection need to be plotted)

Step 3 Click on "Chart wizard"

Step 4 Select any type of graph and walk-through the steps.

---

Plotting a graph in Wingz:

---

Step 1 Invoke wingz and open the .csv file.

Step 2 Select Text Type "comma delimited".

Step 3 Click OK.

Step 4 Select Columns A,B columns

Step 5 Click on Tools->"graph icon (on the left side)". The cursor now changes to "+"

Step 6 Select the columns A,B (Graph will use only these selected rows to plot)

Step 7 Select Chart->Types->XY

---

New Features and Enhancements in WANCV Release 4.19

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

Changes made in 4.19:

•Displays the correct connector to UAI-4E1-DB15 backcard (IGX)

•Displays the correct orientation for PXM-UI-S3 and MCC-8-OC3 back cards (BPX-SES)

•Cosmetic changes to the PNNI Summary Address dialog window Create button

•Support for MCC-8-OC3 backcard for PXM1E is added.

•Added rsrcPartiVsiBwOverbooking support for Rel 9.4.

•Performance improvement when RPM cards are present without back cards.

•On-Line Help support for PXM1E-based & PXM45-based MGX 8800-series/MGX 8950/VSC packages.

•Supports AXSM-XG with clear channel and channelized on the Cisco MGX 8950.

•Adds SCR based CAC support for AUSM and PXM Cards.

Bugs Fixed in 4.19:

Table 7 Bugs Fixed in 4.19

Bug ID	Description
CSCdz21732	AXSMXG ds3 Channelization:Xtm Clock source is not supported
CSCdz77336	PNNI Interface Configuration menu option missing for SES
CSCdz90328	CV missing mibs in VISM Rsvp dialog
CSCea01506	CV RSVP ip addr & port should be in decimal value
CSCea01530	CV spelling mistake for VISM ds0 config dialog
CSCea16488	CV fails to create PNNI controller on PXM1e-8OC3 card

Features Not Supported in WANCV 4.19

The following features are not supported in WANCV 4.19:

•The security feature is not supported in conjunction with CWM 12.

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

•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 CWM 12.0.00

The following features are not supported in CWM 12.0.00:

•You cannot perform an image download (FW download) from the CWM GUI for the NPM, HDM and NTM cards of the IGX switch. If you try to perform an image download on these cards from the Image Download GUI, you will receive an error message, stating "Image download operation not supported for node with card type 0."

•Co-residency of C-NOTE 3.0 and CWM

•StandAlone Stats Parser and Standalone Stats Collector with Parser are no longer supported in CWM 12. This feature has been replaced by the re-architected Standalone Statistics Manager.

•CWM workstations do not support dual NIC configurations.

•The URM service module is not supported by CWM.

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

–TGCP

–Dynamic Payload

–T.38 Fax Relay.

•The logical Multi-peer Group topology display is not available in this release.

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

•New preferred routes can be created using CLI or CWM Service Agent, but not with the CWM GUI.

•The preferred route indicator of a connection is not available 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 PNNI networks.

Pointing multiple CWM workstations at the same gateway node is not recommended unless Persistent Topology is enabled.

CWM must be started from a CDE environment.

CWM does not support use of the korn shell.

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

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

---

Step 1 Stop core, exit out of the CWM prompt

Step 2 Run stoporbix2000 script

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

Step 4 Start core.

---

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

Exception raised while calling activateLease on 
pseudoServer.IT_ATLI_IOP:CONNECTION_CREATION_TIMEOUT

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

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

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

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

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

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

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

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

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

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

shmat: [22]: operating system error

18:45:49  shmat: [22]: operating system error

18:45:57  Error writing '/tmp/shmem.1fd4555c.0' errno = 4

18:45:57  mt.c, line 10260, thread 7148, proc id 1008, errors occurred during mt_

notifyvp.

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

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

forceload: sys/shmsys

forceload: sys/semsys

set shmsys:shminfo_shmmax=1073741824

set semsys:seminfo_semaem=16384

set semsys:seminfo_semmap=5000

set semsys:seminfo_semmni=8192

set semsys:seminfo_semmns=8192

set semsys:seminfo_semmnu=8192

set semsys:seminfo_semume=256

set semsys:seminfo_semvmx=50000

set shmsys:shminfo_shmmin=256

set shmsys:shminfo_shmmni=32000

set shmsys:shminfo_shmseg=256

set semsys:seminfo_semmsl=100

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

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.

CiscoView behavior after using the browser's refresh button is unpredictable. There is no reason to refresh the window, as CiscoView is refreshed automatically, based on the refresh/polling period.

The refresh/polling period can be set via the Preferences option.

If, after using the browser's refresh button, the browser hangs, close the browser and launch a new session.

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

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

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

When you have the persistent topology feature enabled, to decommission a node in the network and take it out of the topology you must delete the node from the persistent topology data using the switch CLI

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

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

Ensuring the Creation of the svplus and/or wandest Username and Password

When either the SSM or the WANDEST server or client is installed for the first time on your Solaris workstation, the svplus and/or wandest username and password may not be available. After installing either of these applications, log in as root and set the password for the svplus and/or wandest user using either the admintool or the passwd command on the command line.

Connection Manager Limitations

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.

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

RPM on PXM1-based MGX 8850/8230/8250 provisioning is done using telnet since the RPM does not support SNMP SETs. Please refer to the specific RPM switch CLI release notes.

HP OpenView Limitations

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

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

Issues with the CWM 12 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.

Only 15 minute collection buckets are supported for PNNI statistics.

Peak statistics are not supported for PNNI statistics.

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

The PXM45A card does not support PNNI statistics collection.

The BPX-SES does not support PNNI statistics collection.

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

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

Wingz and Summary Reports are not supported on the SSM machine.

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

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

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

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

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

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

Limitations for CWM to CWM Communication

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

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

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

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

Topology Limitations

Newly added PXM45-based MGX 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 PXM45-based MGX network, the PXM45-based MGX nodes 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. PXM1-based MGX nodes connected to PXM45-based MGX nodes are managed through the atm0 IP. If the atm0 is not set, then the LAN IP is used to manage the PXM1-based MGX nodes. Configure the trap IP accordingly.

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 nodes and trunks are displayed in the topology display at CWM startup.

TOPO_SHOW_MAP 1 means when NWTopology opened, users can see nodes and trunks in the topology.

TOPO_SHOW_MAP 0 means when NWTopology opened, users cannot see nodes and trunks in the topology.

CWM 12 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.

Occasionally, when deleting a feeder node, unrelated nodes may also be deleted from the topology due to the order of deletion. Refer to CSCin42863 for more details, including workarounds.

Issues with Firewalls and CWM 12

Firewalls set up on managed networks and PCs used as clients may affect the Desktop GUI. The following sections describe how to resolve these issues.

Firewall on PC:

Problem:

If a PC based firewall like BlackIce is used, the protection settings to enable incoming connections may need to be changed. In CWM 12.0.00, when running a client is running on a remote PC, the server opens new connections when sending node and network updates to the Desktop GUI. If the PC blocks all incoming calls, this will cause the topology map to not appear on the GUI.

Solution:

Lower the protection level for incoming connections. In BlackIce, for example, the Protection Level should be set to "Cautious:block some unsolicited inbound traffic" instead of the more restrictive "Nervous:block most unsolicited inbound traffic". OR

If the firewall software allows, add CWM server machine as a trusted IP address and allow all traffic from the CWM host.

Firewall on LAN:

Problem:

If the network where CWM is located has a firewall configured to restrict traffic from both inside the LAN as well as from an outside PC the topology map will not show up in the Desktop GUI.

Solution:

Use VPN tunneling for the remote PCs to connect to the CWM machines in the network OR

Setup trusted IP addresses in the Firewall. Both CWM machines and the remote PC that are going to use CWM GUI need to be added as trusted IP addresses in the firewall configuration.

CWM 12.0.00 Server Installation or Upgrade to CWM 12.0.00

---

Note CWM software can be upgraded from 10.5.10 Patch 1, 10.5.10 Patch 3, or 11.0.10 patch 1 (either Solaris 7 or Solaris 8)

---

The most current upgrade and installation information is found in the CWM Installation Guide for Solaris 8, Release 12 (OL-3837-01). A PDF copy of this document is on the CWM 12 Documentation CD. The following sections describe installation and upgrade procedures specific to CWM 12.0.00.

Evaluation Copy of CWM 12

The 90-day evaluation copy of CWM gives you the opportunity to try CWM for a 90-day period. It is not possible to upgrade an existing version of CWM with the evaluation version. The evaluation version does not support Multiple Disk Configuration for Informix. The only other difference between the licensed version of CWM 12 and the 90-day evaluation version is the way the software is packaged. Here are the details for the 90-day evaluation package

The 90-day evaluation version of CWM comes with all the other applications like Service Agent, SCMSA, WANDEST Server and WANDEST Client

It is packaged into 4 CDs

•CWM Server on the first CD (no change from the licensed version of CWM 12)

•CWM Server Agent and SCMSA on the second CD (the directories are cdromAgent and cdromScmSa)

•CiscoView, WANDEST Server and WANDEST Client on the third CD (the directories are cdromCV, cdromWDServer, cdromWDClient)

•CWM documentation and Adobe Acrobat software on the fourth CD (no change from the licensed version of CWM 12)

All the packages have to be installed separately, just like the licensed version of CWM 12.

For the applications on the second and third CDs, you must change directory to a particular package directory and then follow the installation instructions for that particular package.

For example, the instructions for installing WANDEST are available in Chapter 5 of the WANDEST Installation and Reference, Release 2.4. Change to the /cdrom/cdromWDserver directory before entering the ./installServer.sh command and then follow the installation instructions in this chapter.

Evaluation Copy limitations

You cannot apply patches downloaded from CCO to the 90-day evaluation copy of CWM.

It is not possible to upgrade an existing version of CWM with the evaluation version.

Important Configuration Notes

This section provides important information about configuration.

Naming Managed Nodes

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

Node Numbering for Release 9.4 IGX Feeder Nodes

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

CWM Dedicated IP Ports

CWM 12 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 12 (incoming): ports used in CWM 12

•udp: 162, snmp trap

•tcp: 8888, HP OV topology daemon

•tcp: 9999, HP OV database daemon

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

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

CWM12 (Internal) Process to Process Communication ports

•CWM processes' ports 9000 to 9011

•Web Services (Java Client) 1551

•CiscoView Web Server 1741

•Orbix ports 3075,3079,3094

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.

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

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

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

Setting up RPM Cards for Management by CiscoView from the Workstation

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 community string

•Router(config) exit

•Router# write memory

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 8 shows SNMP and SYSLOG router configuration commands. In this example, the network management system has an IP address of 10.1.1.1.

Table 8 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 PXM1-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 PXM1-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 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

WANCV 4.19 Notes and Cautions

When there is a card mismatch go to the "card summary" display to see the indicator of "mismatchwithParent".

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 actually represent an "alarm" state for a physical interface.

The VISM Ds0 Config screen 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

---

Caveats

This section lists known and resolved anomalies in the Cisco WAN Manager 12.0.00 software and other associated software. The resolved anomalies include all anomalies resolved in CWM 11.0.10 Patch 2 and below, with the exception of CSCea53665, which is listed in the Known Anomalies section below.

Known Anomalies in CWM 12.0.00 Software

This section lists known anomalies in CWM Release 12.0.00 software as of 05/02/03.

Table 9 Known Anomalies in CWM Release 12.0.00 Software 

Bug ID	Description
CSCdx86279	Symptom: CWM fails to display the appropriate trap when a service affecting alarm is generated on the BPX. Conditions: Create a service affecting condition on the BPX and observe OV event browser or the RtmProxy log. Workaround: None.
CSCdz55698	Symptom: Topology - Display Trunk shows PNNI Protocol instead of Feeder Conditions: Unknown Workaround: Unknown
CSCea20044	Symptom: SCM collection server on the SCMSA coredumped during SSM switchover. Conditions: Primary, Secondary Collection Server configuration. Workaround: No workaround required. Process is re-started by watchdog. Resumes operation normally.
CSCea46440	Symptom: Virtual link is displayed twice: as virtual and physical Conditions: This is a timing issue. This might happen when you have virtual trunk between two PNNI nodes and you have persistent topology enabled. Workaround: Cold Start CWM
CSCea53665	Symptom: Node resync is not clearing out the port Agg status when line is not in alarm Conditions: Always Workaround: None
CSCea59868	Symptom: After clrsrmcnf lines under the card is missing from DB Condition: Always. Workaround: Manual Node Resync
CSCea59886	Symptom: Database gets full because the Ager is not able to keep up with the insertion rate. Conditions: This occurs in 2 cases. First the stats data is being parsed into the stratacomDB. Second case is if statsDB is parsing all of the data into 1 table. (not set up for scaling). This occurs when the number of connection end points that the parser is processing exceeds Workaround: For CWM, the data must be parsed into the statsDB for more than 250,000 endpoints. The parser config file must be set up for scaling to generate multiple stats tables. For CWM 11.0.10 the ager will not be able to keep up with the insertion rate. The maximum number of connection endpoints that the Ager can be supported depends on the class of Sun server. Increasing the DB size or reducing the Ager interval, will reduce the probability of the DB filling up. If the DB is slowly filling up because the Ager can not keep up, and it appears the DB space will fill then reduce the amount of data inserted into the DB. (i.e. reduce the number of endpoints or number of stats ids)
CSCea62404	Symptom: Cannot create a new profile using security manager GUI Conditions: From the SecMgr GUI, if the Reset button is clicked before the Create button, profile will not be created. Workaround: Close and open the SecMgr GUI without clicking on the Reset button
CSCea62496	Symptom: SNMP GET of svAtmPortTable.svAtmPortOperState fails for UXM ports Conditions: In CWM 11.0.10 Patch 1 & CWM 12.0 Any mib-object get for UXM Card. Workaround: None. Further Problem Description: Please see the Description.
CSCea63071	Symptom: OOEMC coredumping multiple times and fills up disk space Conditions: When Alarm files were ftped with wrong permission Workaround: Delete corefiles before disk is full and manual resync the node Further Problem Description: Exact root cause of why files were ftped with wrong permission is still unknown. One possibility is unix file system bug. The problem is not reproducible and very rare (only occurred once).
CSCea64528	Symptom: Unreachable feeder node shown as reachable Conditions: Not known. Workaround: Warm start CWM
CSCea65131	Symptom: SCT declares sync up before some nodes actually synced up with CWM. Hence requests from SCT Manager for those nodes will be rejected since the nodes are not synced up yet. Condition: Happens when some nodes in the networks are very slow to sync up with CWM. Workaround: Do not apply SCT operations on nodes that haven't sync up with CWM yet. From SCT GUI user point of view, the effect of SCT Manager declares sync up decides when can the SCT GUI be launched, i.e. SCT GUI can't not be used if SCT Manager hasn't declare sync up yet. So the effect of SCT Manager declare sync up prematurely is just users may experience error messages when try to apply operations on nodes that haven't sync up yet which is the correct response for nodes haven't sync up with CWM. So, no work around is needed.
CSCea65793	Symptom: User information entered via keyboard is not showing in the window opened from Topology --> select the node --> Admin until the end user hit Enter and get the password prompt. End user should be able to see what he/she has entered. Conditions: Normal mode Workaround: No workaround.
CSCea66889	Symptom: one MGX8850R2 was in mode 4 Condition: The config file was corrupted with EM log. Very rare case (only occurred once). Workaround: Manual node resync.
CSCea72297	Symptom: EMC core dump Conditions: on PLCP processing Workaround: unknown.
CSCea73714	Symptom: svConnTestResult units need to be consistent across networks Conditions: When comparing results from AutoRoute and PNNI networks Workaround: Perform conversion Further Problem Description: AR nodes always returns the testdelay result in milliseconds and PNNI nodes returns the testdelay result in microseconds. svConnTestResult value was the same as that was returned by the switch.
CSCea75459	Symptom: MIBs under ~svplus/mibs/mibdir should be cleaned up Conditions: Packaged with Cisco WAN Mgr 12.0 Workaround: View README at ~svplus/mibs
CSCea77654	Symptom: OOEMC core dump Conditions: If a node resync takes place immediately after a SM switch over or switch back. This is seen with MGX2 node with AXSM cards in redundancy. There is switch over of cards followed by a node resync. Workaround: Not applicable. Further Problem Description: The sequence of events from switch is switch over trap followed by a summary alarm trap. But while the handling the order is reverse causing the core dump. A syncup is in progress with PNNI file in parsing phase. This PNNI file upload causes the traps to be buffered and changes the sequence of traps being handled.
CSCea78724	Symptom: Java core dump Conditions: Java runtime environment has segmentation fault and dies. Workaround: none.
CSCea79990	IGX Feeder Trunk alarm shows as unreachable intermittently Symptom: Feeder Trunk alarm between IGX feeder and MGX routing node shows as unreachable though it is not. Conditions: Network containing MGX routing nodes and IGX feeders connected to them. Workaround: Execute dnlmi on the MGX routing node followed by uplmi on the IGX feeder port.
CSCea80031	Symptom: nodeinfocfg coredump Condition: when the secret string typed in is too long, or contains invalid characters (space, tab) Workaround: Enter valid strings
CSCea80228	Symptom: When XLMI trunk is deleted from both BPX and MGX, the XLMI link on the topology GUI is not getting deleted. Condition: First delete the xlmi in MGX side by dellmi. Then do a 'delport' on BXM card in BPX. Still the topology GUI shows that XLMI link in red color instead of deleting it in the GUI. Workaround: None.
CSCea80549	Symptom: In one occasion ooemc process used-up a lot of swap space. Conditions: Normal CWM operation with large number of nodes and connections Workaround: If necessary, cold start CWM
CSCea80629	Symptom: Trunks are not deleted from the Topology GUI Conditions: This happens when, 1. persistency is enabled for MGX2 nodes and 2. the trunk is deleted from the Gateway node and not from the actual node Workaround: Restart Core Further Problem Description: The trunk should be first deleted from the node and then from the Gateway node. It's not a valid scenario to delete the trunks from the Gateway node without deleting them from the actual nodes.
CSCea82069	Symptom: XLMI link didn't get added on topology. Condition: Delete the XLMI port from the AXSM, and re-add it. Workaround: Disable and enable XLMI on BPX side by using "cnfport" command
CSCea82091	Symptom: System call getserverbyname fails causing tftplib to exit, this caused sccmcollsvr coredump Conditions: tftp issued for Legacy nodes: Axis, BPX, MGX1 Workaround: Collection restarts automatically.
CSCea83896	Symptom: svConnPrefRouteDesc returns unusable string for N/A conn type, change to null Conditions: Using svConnPrefRouteDesc with SPVC Workaround: Should not perform GET on this object for non PVC connections
CSCea84134	Symptom: The physdbs becomes full (onstat -d shows 0 pages left) This will cause the parser to stop parsing data. Conditions: When the SCM Parser is configured for scaling. This means the config files have been setup for multiple stats tables. The stats data is also being put into the physdb space. Workaround: Change the physdbs to logdbs. In the onconfig (in /usr/users/informix/etc) change the definition of PHYDBS to logdbs Change the partition name from phydbs to logdbs. Run the command onspaces (as the DBA) first drop the phydbs (onspaces -d phydbs), then add the logdbs (onspaces -a logdbs)
CSCea85711	Symptom: Newly added PVC connection with VBR subtype and non-default policing is not shown in Connection Manager GUI. Conditions: For a VBR connections, when one of the endpoint is ATM (on BPX) and the policing is configured as anything other than policing1 or policing2 or policing3. Workaround: Change policing from switch CLI to one of the above mentioned values to view or modify the connection
CSCea85749	Symptom: SNMPWALK on cwmPrefRouteCnf and cwmPrefRouteNwElem tables does not return for all entries. Conditions: This problem is noticed if the preferred route tables have entries with sequential RouteIds. Workaround: SNMPGet or query DB for the preferred routes could be a work around. These preferred routes can be checked through CLI also.
CSCea85897	Symptom: Connection descriptor for a connection is not shown on the non-provisioning CWM GUI. Conditions: If the local end of the provisioned connection is a FR or CESM endpoint. Workaround: View the descriptor from the provisioned CWM. A coldstart on the non-provisioning CWM will fix the problem.
CSCea86967	Symptom: ILMITopoc coredumped. Conditions: Unknown Workaround: N/A
CSCea87012	Symptom: nodes remain in mode 4 Conditions: duplicate 0 byte config files were created for some axsm slots. Workaround: re-sync
CSCea87848	Symptom: Preferred route modification request returns bogus error message 'cwmPrefRouteNwElemEntry Mib Object cwmPrefRouteNENode [5] has length = [18867868] Out of Range'. Conditions: Try to add a new NE for a existing preferred route as part of preferred route modification. This error message may be triggered by wrong NE Name in the SNMP request. Workaround: None Further Problem Description: Exact conditions for this problem are not known. This problem is reproducible only when the SNMP requests are sent through customer scripts. Direct SNMP request to the customer CWM machine are went through fine without any bogus error message.
CSCea88408	Symptom: Node remain in mode 2 Conditions: node auto resync was interrupted Workaround: re-sync
CSCea88616	Symptom: RPC error messages after Start Core on CWM machine Conditions: Seen in Console Menu Window with 12.0 FCV Mar28 Build Workaround: Unknown Further Problem Description: This is an intermittent problem and does not appear to impact functionality
CSCin38986	Symptom: Node name change is not getting reflected in database for an MGX 8250 node. Condition: Node added as standalone. Workaround: Delete the standalone node and re-add it using Configurator.
CSCin42863	Symptom: MGX8850R2 node disappeared from topology GUI on MGX8220 node deletion Conditions: Delete MGX8220 node from CLI and check topology GUI. Workaround: coldstart CWM.
CSCin15035	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.

Anomalies Resolved in CWM 12.0.00 Software

All anomalies resolved in CWM Release 11 and CWM Release 10 as of 05/02/03 that were applicable to CWM Release 12.0.00 are included in CWM Release 12.0.00. Table 10 lists externally found anomalies from CWM Release 11 and CWM Release 10 as of 05/02/03 that were only resolved in CWM Release 12.0.00 software.

Table 10 Anomalies Resolved in 12.0.00 

Bug ID	Headline:
CSCdx31087	SCT VC and CosB show wrong vals
CSCdx86816	Stata objectID:3/10:type 11,7&6 not being collected.
CSCdy19807	Wrong alarm on collapsed trunks
CSCdy26355	VSI-SIG paramters mismatch SCT GUI and CLI
CSCdy33589	CLR values displayed for PXM1E does not match with switch default values
CSCdy59622	.rhosts file overwritten during upgrade process
CSCdy62201	webServer did not start on upgraded m/c
CSCdy71243	MGX45 nodes failed to resynch because of snmp timeout (eumlator related)
CSCdy82218	SNMP Module:Nodes failed to resynch
CSCdy83851	DiagServer coredumped on a CWM machine
CSCdy84495	Topology shows trunk as clear after doing down & up lmi/ilmi on downed port
CSCdy84607	few AutoRoute trunks are not shown in Network Browser
CSCdy85868	CWM installation hangs at CV install if cronjob leaves a /tmp/crout* file
CSCdy87250	BPX node discovered as forreignnode and got deleted from database
CSCdz01188	On sunrise install, install does not complete (i
CSCdz04403	Some CiscoView subdirectories are world-writable
CSCdz14857	CWM bug in install script
CSCdz19026	SCT manager Cosb tab screen not clearing setting after changes
CSCdz24906	Gui does not refresh when trunks is deleted
CSCdz68842	CM GUI - usability requirements from customers
CSCdz77588	BXM-T3 card type 250,251 BXME not recognised by SCM
CSCdz84213	trapd logs enhancements for debugging
CSCea16325	EMD deadlock MGX 8850 and 8220 will not sync
CSCea49075	PortProxy error misleading
CSCea49140	corba exceptions after install, start core
CSCea57681	Wandest client doesnt work in ksh environment
CSCea63117	ausm_port missing from DB, proxy query fails
CSCea64393	Overhead factor not applied for PXM1E AXSM-E to FRSM VBR conn
CSCea66013	Unable to add connections where VISM is the remote end. GUI and SA
CSCea68557	Corba ping_server utility on wandest client box
CSCea69561	Wandest install error msg is not proper
CSCea69616	Wandest encrypted pwd generation during install is set to default
CSCea72116	SNMP Get on cwmPrefRouteNECount returns incorrect value
CSCea76611	ooemc did not resync with RPM after missed trap
CSCea80554	swap space problem on machine, creates process reinitialization
CSCin36910	SES 1.1(79.102) returns NO SUCH NAME for mib obj cwaChanOamSegEpEnable

Related Documentation

The following technical documents comprise the CWM 12 documentation set:

•Cisco WAN Manager Installation for Solaris 8, OL-3837-01

•Cisco WAN Manager User's Guide, OL-3838-01

•Cisco WAN Manager SNMP Service Agent, OL-3840-01

•Cisco WAN Manager Database Interface, OL-3839-01

•Cisco WANDEST Installation and Reference, Release 2.4, OL-4122-01

•Release Notes for Cisco WAN Manager for Solaris 8, Release 12.0.00, OL-3188-01

PDF copies of the first four items in the CWM 12 documentation set are provided on the third CWM 12 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.

The Cisco WANDEST Installation and Reference, Release 2.4 and these release notes are not available on the third CWM 12 CD. They are available on-line at the following URL:

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

Obtaining Documentation

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

Cisco.com

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

http://www.cisco.com/techsupport

You can access the Cisco website at this URL:

http://www.cisco.com

You can access international Cisco websites at this URL:

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

Product Documentation DVD

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

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

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

Ordering Documentation

Registered Cisco.com users may order Cisco documentation at the Product Documentation Store in the Cisco Marketplace at this URL:

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

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

Documentation Feedback

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

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

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

We appreciate your comments.

Cisco Product Security Overview

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

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

From this site, you will find information about how to:

•Report security vulnerabilities in Cisco products.

•Obtain assistance with security incidents that involve Cisco products.

•Register to receive security information from Cisco.

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

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

To see security advisories, security notices, and security responses as they are updated in real time, you can subscribe to the Product Security Incident Response Team Really Simple Syndication (PSIRT RSS) feed. Information about how to subscribe to the PSIRT RSS feed is found at this URL:

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

Reporting Security Problems in Cisco Products

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

•For Emergencies only — security-alert@cisco.com

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

•For Nonemergencies — psirt@cisco.com

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

•1 877 228-7302

•1 408 525-6532

---

Tip We encourage you to use Pretty Good Privacy (PGP) or a compatible product (for example, GnuPG) to encrypt any sensitive information that you send to Cisco. PSIRT can work with information that has been encrypted with PGP versions 2.x through 9.x.

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

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

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

If you do not have or use PGP, contact PSIRT at the aforementioned e-mail addresses or phone numbers before sending any sensitive material to find other means of encrypting the data.

---

Obtaining Technical Assistance

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

Cisco Technical Support & Documentation Website

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

http://www.cisco.com/techsupport

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

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

---

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

---

Submitting a Service Request

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

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

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

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

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

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

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

Definitions of Service Request Severity

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

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

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

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

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

Obtaining Additional Publications and Information

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

•The Cisco Product Quick Reference Guide is a handy, compact reference tool that includes brief product overviews, key features, sample part numbers, and abbreviated technical specifications for many Cisco products that are sold through channel partners. It is updated twice a year and includes the latest Cisco offerings. To order and find out more about the Cisco Product Quick Reference Guide, go to this URL:

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

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

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

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

http://www.ciscopress.com

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

http://www.cisco.com/packet

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

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

or view the digital edition at this URL:

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

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

http://www.cisco.com/ipj

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

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

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

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

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

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

Copyright © 2003-2006 Cisco Systems, Inc.
All rights reserved.