Table of Contents

Contents
System Requirements

If You Experience Performance Problems

CWM Performance Degradation
Loss of Database Synchronization

Required Configuration for Stand-Alone SCM
HP OpenView Requirements
INFORMIX Requirements
WingZ Requirements

Supported Hardware

Legacy Hardware
New Hardware

Software Compatibility

Switch Software
CiscoView 4.2
HP OpenView

New Features and Enhancements in CWM Release 9.2.07

New Connection Provisioning in CWM

New Features and Enhancements in CWM Release 9.2.04
New Features and Enhancements in WANCV Release 2.0
Features Not Supported
Network Limits
CWM 9.2.07 Notes and Cautions

Known Limitations
Installation
CWM Upgrade
CWM Configuration

Modifying the emd.conf File
Modifying the tftpmgr.conf File

CWM Dedicated IP Ports
Unique Node ID
Security Profiles
CWM Database
Network Configuration
Service Agent
Connection Manager
CWM Connection Support
Card Types
Frame Relay Support
ATM Support
Circuit Emulation Support
Voice Connection Support
Data Connection Support
Connection Summaries

FR - FR Connections
ATM - FR Connections
ATM - ATM Connections
Other Supported Connections

Statistics Collection Manager
Platform
Reports
Topology
Software/Firmware Image Download
SNMP Traps
RPM
Cisco WAN Manager SNMP Agent Notes

CWM SNMP Agent Configuration Notes

WANCV 2.06 Notes and Cautions

Installation

Performance
Network Configuration

Interface Changes

SV+Network.mib
SV+Service.mib
AXIPOP.mib

Changes to Database Tables and Definitions

New Database Tables

New Database Definitions

Caveats

Known Anomalies in CWM 9.2.07
Anomalies Corrected in CWM 9.2.07
Anomalies Corrected in the 9.2.04 Release of Cisco WAN Manager
Anomalies Corrected in WANCV 2.07
Anomalies Corrected in WANCV 2.07
Known Anomalies in WANCV 2.06
Anomalies Corrected in WANCV 2.06
Known Anomalies in WANCV 2.04
Anomalies Corrected in the 2.04 Release of WANCV
Anomalies Corrected in the 2.03 Release of WANCV
Anomalies Corrected in the 2.02 Release of WANCV
Anomalies Corrected in the 2.01 Release of WANCV
Anomalies Corrected in the 2.00 Release of WANCV

Related Documentation
Cisco Connection Online
Documentation CD-ROM

9.2.07 Version Software Release Notes
Cisco WAN Manager for HP-UX

Cisco WAN Manager 9.2.07 for HP-UX software supports the following Cisco products:

• New Cisco MGX 8850 products running software release 1

• Existing Cisco WAN switching products (including the Cisco IGX 8400 series and the Cisco BPX® 8600 series) running switch software (SWSW) versions 9.2 or 9.1

• Existing Cisco MGX 8220 products running software versions 4.0, 4.1, or 5.0

Cisco WAN Manager (CWM) is the new name of the former product, Cisco StrataView Plus (SV+). As of CWM release 9.2.00, all references to SV+ were changed to CWM, including the start-up script, the desktop, and icon names.

The CWM 9.2.07 release is fully Year 2000 (Y2K) compliant. Table 7 lists the compliance matrix.

CWM 9.2.07 is bundled with WANCV (WAN switching device packages) for device management.

Contents

This Release Notes document contains the following sections:

• System Requirements

• Supported Hardware

• Software Compatibility

• New Features and Enhancements in CWM Release 9.2.07

• New Features and Enhancements in CWM Release 9.2.04

• New Features and Enhancements in WANCV Release 2.0

• Features Not Supported

• Network Limits

• CWM 9.2.07 Notes and Cautions

• Changes to Database Tables and Definitions

• Caveats

• Related Documentation

• Cisco Connection Online

• Documentation CD-ROM

System Requirements

Three types of machines are supported for WAN Manager 9.2.07 as standard platforms. They are low-end, mid-range (three options), and high-end platforms. The configuration of each platform type is listed in Table 1, "HP Platform Requirements".

If You Experience Performance Problems

If you use CWM 9.2.07 on a low end machine to manage mid-range or large-range networks, the following performance problems might be observed.

CWM Performance Degradation

CWM may take a long time to synchronize with the network. Connection Management and Equipment Management (CiscoView and Equipment Manager GUI) 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.

Loss of Database Synchronization

CWM may drop traps generated by the network which might put the CWM database out of sync with the network. This would result in the information about nodes, trunks, ports, and PVCs might not match with the status on the network.

Required Configuration for Stand-Alone SCM

Three types of machines are supported for CWM 9.2.07 stand-alone SCM as standard platforms. They are low-end, mid-range and high-end platforms. The configuration of each platform type is listed in Table 2, "Platform Requirements for Stand-Alone SCM".

HP OpenView Requirements

The CWM 9.2.07 release works with HP OpenView Release 5.01 for HP-UX 10.20. See "Third Party Product Limitations Notes" for HP OpenView patches required by CWM.

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

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

INFORMIX Requirements

The CWM 9.2.07 release uses Informix 7.23 for database operations.

WingZ Requirements

The CWM 9.2.07 release's Report Application uses WingZ 2.5 or later. For the Report Application to work properly, the DataLink package of wingZ must also be installed along with WingZ package.

Supported Hardware

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

Legacy Hardware

Table 3 lists the legacy hardware supported in CWM 9.2.07.

New Hardware

Table 4, "Supported New Hardware", lists the new hardware supported in CWM 9.2.07.

Software Compatibility

CWM 9.2.07 operates with BPX 8600 and IGX 8400 series systems running SWSW releases 9.2 or 9.1. CWM 9.2.07 operates with MGX 8220 releases 4.0, 4.1, and 5.0 for all supported features. CWM 9.2.07 can operate in mixed networks of 9.1 and 9.2 SWSW.

Switch Software

WANCV 2.01 will operate with BPX/IGX releases 9.2 and 9.1, releases of MGX 8220 later than 4.0.15, and all available releases of MGX 8850. You should use CWM Equipment Manager to manage MGX 8220 release 4.0.15 and earlier releases. When you launch Equipment Manager from the CWM Desktop, the application determines whether to launch WANCV or CWM Equipment Manager.

CiscoView 4.2

Cisco strongly recommends you use CiscoView Release 4.2 with all available Software Module Updates. WANCV device packages are also compatible with CiscoView Release 4.1.

HP OpenView

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

Patch PSOV_02243 is required for HPOV and is supplied on the CWM 9.2.07 CD. If HP OpenView is installed on your CWM station, this patch is installed during CWM 9.2.07 installation.

The WANCV 2.0 release works with HP OpenView Release 5.01 for HP-UX 10.20.

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

New Features and Enhancements in CWM Release 9.2.07

Cisco Wan Manager 9.2.07 has been enhanced to support the following features of switch software release 9.2.30:

• Multiple VSI Partitions

This task allow multiple VSI partitions configured on BPX. In this release, 2 partitions will be supported and will be tested with PNNI and TSC controllers on same BPX.

• Frame Based Traffic Control with Policing on BXM

This feature will allow the configuration of hardware to enable Frame Based Traffic Control with PPD policing for AAL5 traffic. Existing RCMP

• IGX Feeder Node over an UXM IMA Feeder Trunk

This feature allows an IGX to be a feeder node using an UXM IMA trunk. The routing node can be an IGX or a BPX using IMATM. Topology, COM and SCM are impacted, but there is no impact on WANCV. Please refer to ENG-36551 for detailed description.

• FRSM VHS Egress Queue Management

In Cisco MGX 8850 release 1.1.20, FRSM-VHS supports two egress-servicing algorithms. This feature is per board and can be selected by using egrQosFeature object. When it is enabled, four queue algorithms (weighted fair queueing) are used. When disabled, two queue-servicing algorithms are used. Two queue algorithm method is similar to that used in FRSM-8.

The egressQSelect object provides an option for you to assign the high- or low-priority egress queue to a connection. This option is implemented in FRSM-8. FRSM-VHS does not use this object as queues are assigned based upon channel service type. High priority and VBR-RT connections are assigned to high priority queue; and VBR-NRT, ABR, and UBR are assigned to low priority.

Table 5 lists the object mapping between the switch MIB and CWM 9.2.07 Service MIB.

New Connection Provisioning in CWM

CWM 9.2.07 supports the additional connection types listed in Table 6.

New Features and Enhancements in CWM Release 9.2.04

CWM 9.2.04 had the following new features and enhancements.

• AIX and HPUX platform support is added to 9.2.04 version of CWM. A separate Release Note document is available for each platform.

• VP Tunneling on IGX-UXM cards is supported in this release. CWM supports VP-VC connections on UXM cards. The CMGUI (Connection Manager GUI) and Service Agent are enhanced to support VP-VC connections. IGX software release 9.2.20 supports this feature. For earlier versions of IGX software, CMGUI and Service Agent will give appropriate errors.

• BPX software release 9.2.10 supports VSI 2.2 with multiple partitions. The CWM Topology GUI has been enhanced to support a multiple partition consistency check.

• Support for APS Annex B on BPX BXM card in CWM event list and RTM proxy

• Support for 16K terminating connections on BPX BXM card in CWM CMGUI and Connection Service Agent

• This release supports an MGX8850 feeder connection to an MGX8600 (BPX) using SWSW Release 9.2 software. All CWM applications have been tested with this configuration.

• In this release, the PXM card in a MGX 8850 switch supports ATM UNI ports as well as feeder ports. All CWM applications have been tested with this configuration.

• In this release, CWM support of the MGX 8850 switch with the CESM T3/E3 service modules is available.

• In this release, CWM support of the MGX 8850 switch with the FRSM-HS1 model B front card and V.35 back cards is available.

• In this release, some fields were added to the CWM database to support VCC connections with VCI=0. Refer to the "Changes to Database Tables and Definitions" section for detailed information.

• In the CiscoView 2.03 device package (WANCV), improvements in polling efficiency for IGX and BPX products are implemented for larger PDUs which are subject to timeout failures in previous WANCV releases.

• In the CiscoView 2.03 device package, a new object x21InvertClock is introduced for FRSM-hs1 and FRSM-hs1B. This object configures two options:

  • Inverting the clock sent with the TX data

  • Receiving a clock from the other side

• In the CiscoView 2.03 device package, a new feature for FRSM-8T1 and FRSM-8E1 was introduced to configure "RAS OAM Loopback" options.

"OAM Loopback Allowed?" = rasOamlpbkAllowed

This object indicates if the RAS-OAM loopback test is enabled for this card. {rasOamlpbkEnabled(1), rasOamlpbkDisabled(2)}

"OAM Loopback Frequency" = rasOamlpbkFrequency

This object indicates the frequency in minutes (1..10) in which a RAS OAM loopback cell is sent per idle connection.

• In CWM 9.2.03, the maximum buffer size calculation is changed for CESM R5 in MGX 8220 shelves and CESM R10 in MGX8850 shelves. In CWM 9.2.03, the mapping is extended to support CESM R4 in MGX8220 shelves.

• CWM 9.2.03 supports the large network sync-up performance requirement.

• AUSM8-B support with ATM Forum compliant IMA

CWM supports AUSM model B in the MGX 8850 switch. AUSM model B uses a new front card type with either a 8T1 or 8E1 back card. AUSM Model A and Model B support the same set of features, except Model B is compliant with ATM forum IMA and model A is not.

• MGX 8850 Core Redundancy support

CWM fully supports the MGX 8850 PXM Core Redundancy feature from equipment management, connection management, fault management, and service agents' perspective.

• Cisco View Automatic Launching for MGX 8220 device management

CWMautomatically launches the Cisco View GUI for MGX 8220 (AXIS) R4 device management. The EMGUI (Equipment Manager GUI) is no longer supported for MGX 8220 R4 switches.

• CWM supports upgrades from SV+ 9.1 to CWM 9.2.x.

• Alarm Hierarchy

CWM has been enhanced to reduce alarm load on an external SNMP Manager by implementing the alarm hierarchy for line/port/PVC

• The packet_line table in the CWM Database has been modified to include a field to indicate number of PVCs on a given trunk

• CWM has been enhanced to report AIS status. The Connection Manager GUI has been enhanced to show the AIS status field for FRSM8, UXM, BXM, and FRM.

• New traps have been implemented in CWM. The new traps include node reachability traps, configuration change traps, OAM loop back traps for terminated connections on BXM and UXM, AIS alarms for FRSM8, UXM, BXM, and FRM service affecting alarms.

• CWM Health Monitoring---a new process has been developed to monitor CWM station conditions. Traps will be generated for process restart, disk space low, or statistics file parsing errors.

• Trap Filtering---the RTM Proxy has been enhanced to allow you to specify which TRAP group you are interested in. Traps from a selected TRAP group will only be forwarded to registered users.

You can maintain unique node IDs across all CWM databases using the Topology Configurator feature of the CWM Admin application on the CWM Desktop.

• Service Agent Enhancements:

  • ConnProxy Changes:

  VOICE, DATA Connection Provision (IGX)
  

  Multicast View Table support for BME card (BPX)
  

  FRSM-VHS, CESM-8 Connection Provision (MGX 8220)
  

  • PortProxy changes

  VOICE, DATA port provision (IGX)
  

  Multicast (BME) port provision (BPX)
  

  Port Provision for New card types
  

  FRSM-VHS (T3, E3, HS2, 2CT3), CESM-8
  

  ATM AUSM-8 IMA Forum Compliant for MGX 8220
  

  • RTMProxy changes:

  Trap Filtering---allows you to receive traps in the TRAP group desired
  

  RTM mode changes---you no longer need to upload lost traps. The RTM Proxy will resend lost traps to registered managers when requested.
  

  New 25000 series User Connection traps such as, svUserConnComplete, svUserConnIncomplete, svUserConnModified, svUserConnectionCleared, svUserConnectionDown, and svUserConnectionFailed.
  

  • Others:

  CARD MIB group is added for retrieval of card information
  

  CARD ALARM MIB Group is added for retrieval of cards in alarm condition
  

• There is a product name change in CWM 9.2.x. The SV+ start-up script is changed to CWM. The New Reports application is renamed Summary Reports, and SV+ Admin is renamed CWM Admin.

• A new CWM desktop application, Security Manager, has been developed to provide application based access control. Security Manager allows multiple user logins and multiple privilege levels using the UNIX user ID of CWM users.

• Cisco View support---Cisco View MSSBU device packages (WANCV) were upgraded to release 2.0 to support IGX/BPX R92, MGX 8850 and MGX 8220 R5 enhancements. Also, the security feature was supported in conjunction with CWM 92 Security Manager.

• Connection Manager Templates---the Connection Manager GUI has been enhanced to support templates which allows you to use a fixed set of parameters while adding a new PVC. The Connection Manager templates support ATM to ATM, ATM to FR, FR to FR, CE to CE, data, and voice connection types.

• CDE support---CWM installation and desktop and it's applications have been enhanced to support the Common Desktop Environment (CDE) on the HP-UX platform. Open Windows is no longer supported.

• MGX 8220 cards switch back through the CWM SNMP Proxy

• Support idle code suppression in Connection Manager GUI for voice connections

• Support IGX-UXM ATM forum compliant IMA. The multiple physical lines in an UXM IMA trunk can have noncontiguous line numbers.

• Topology Configurator---allows you to modify node related information such as node name, node ID, and model number. You can use this tool to assign unique node IDS across the network. It is an optional tool for tiered networks. However, it is a mandatory tool for standalone nodes.

• CWM 9.2.00 supports connection addition, modification, and deletion for RPM to RPM, RPM to ATM, and RPM to FR service interworking in either single or multiple segment connections.

CWM 9.2.00 supports an MGX 8850 node configured as a standalone switch which does not connect to any Cisco MSSBU switch. In this mode, you must use the Topology Configurator to enter node-related information into the CWM database. The following CWM applications are enhanced to support standalone MGX 8850:

• Topology

• Network Browser

• Image download

• Connection Management including PXM-UNI to ATM, CE, FR, or RPM end points

• Statistics Collection Manager

• Service Agents including Port, Connection, and RTM proxies

• CiscoView

• Fault Management

• TFTP Configuration Upload

• The CWM 9.2.00 Statistics Collection module (SCM) is enhanced to support statistics collection from MGX 8800 Series Standalone Nodes and more efficiently manage the node list and collection parameters when the SCM is in standalone mode. The enhancements are summarized in the following list:

  • MGX 8800 Series Standalone Node Time Synchronization for SCM running in both integrated mode (with CWM core system) and standalone mode

  • Allows you to configure the list of nodes to collect statistics from when SCM is running in standalone mode

  • Performs an SNMP GET operation to retrieve collection parameters from the node when SCM is running in standalone mode.

The first enhancement is required to support statistics collection from MGX 8800 Series Standalone Node only Networks while the last two enhancements are specific for the standalone SCM so it can provide the same full features as the SCM running in integrated mode.

• The NWTopology may at times not allow the selection of the displayed nodes. This is a know problem and the current workaround is to reboot the machine.

• CWM 9.2.00 Connection Management is enhanced to support four different QoS queues for FRSM-VHS including FRSM-2CT3, FRSM-T3/E3, and FRSM-HS2 service modules versus two QoS queues for legacy FRSM service modules. The enhancements include those made in the Connection Manager GUI and Connection Service Agent. Enhancements include FR to FR connection types in CWM 9.2.00.

• CWM 9.2.00 is fully Year 2000 compliant. Table 7 lists the software releases and patches used in CWM 9.2.06 and includes certification information.

New Features and Enhancements in WANCV Release 2.0

CiscoView MSSBU device packages (WANCV) are upgraded to release 2.0 to support IGX/BPX Release 9.2.00, MGX 8220 Release 5.0 enhancements, and the MGX 8800 family of products.

• The security feature is supported in conjunction with CWM 9.2.00.

  Security Manager is an application contained in CWM 9.2.00. A new desktop allows you to create multiple CWM users and assign privilege levels, including read, create, and modify. The access control used by CiscoView is provided at several levels, such as shelf, card, line, and port level privileges.
  

• Q-bin and Resource Partition management is added for BXM (BPX)

• The MGX88 device package is introduced to support the MGX 8850. Features include:

  • Support for PXM cards

  • Broadband Interfaces are supported on PXM

  • Resource Partitions are supported for Broadband Interfaces

  • Resource Partitions are supported for service modules.

• New RAS Disk objects were added for Revision 5.0 ASC cards

• Trunk and Port Management Changes:

  • Virtual Trunks are supported on BNI, BXM, and UXM (BPX and IGX)

  • ATM IMA Trunks are supported on UXM (IGX)

  • Port Provision for new card types: FRSM-VHS (T3, E3, HS2, 2CT3), CESM (MGX)

  • The SRM Line Distribution feature is added {MGX).

Features Not Supported

The following features are not supported in CWM 9.2.05:

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

• There is no support for Equipment Manager GUI for MGX 8220 4.0, 4.1, 5.0, and MGX 8850. CiscoView is used for equipment management of those nodes.

• MGX 8850 configuration save and restore is only supported through the Command Line Interface (CLI). MGX 8850 configuration save and restore is not supported in CWM 9.2.05.

• RPM connection service agent is not supported

• CWM 9.2.05 does not support the BERT feature of the MGX 8220 Release 5. You must use the MGX 8220 Command Line Interface to configure the BERT functions.

• CWM 9.2.05 does not support FRSM-VHS QoS queue selection for FR to ATM connection types.

Network Limits

The SWSW and MGX 8220 (4.04 onwards) have increased their limits to support network connections of up to twelve CWM stations. No changes were required in Cisco WAN Manager Release 9.2.07 software to support this increase.

CWM can manage up to 40 different disjoint networks running switch software releases 9.0 and 9.1, provided all the networks elements have unique network IP addresses and unique names across all the networks managed by CWM. Different networks may run different versions of switch software as long as the releases are those listed above. Disjoint networks containing up to 15 nodes in each network have been tested.

CWM 9.2.07 Notes and Cautions

Known Limitations

RPMs using IOS version 12.0(4) have slot numbers in its ifDescr that are unlike those for IOS version 12.0(5). This invalidates the enhancement for IOS version 12.0(5) in CWM 9.2.07 and WAN CiscoView 2.06, and it makes RPMs using IOS version 12.0(4) unmanageable by CiscoView.

The workaround for this problem is to upgrade RPM using IOS version 12.0(4) to version 12.0(5).

Installation

The upgrade script has changed in Cisco WAN Manager Release 9.2.07.

Existing CWM configuration files are unconditionally overwritten with default values during the CWM 9.2 installation process. If you are installing CWM 9.2.07 over an earlier release of CWM 9.2.0x, save these files manually before beginning the installation process. The following files are affected:

• /usr/users/svplus/config.sv

• /usr/users/svplus/config/userInfo.sm

• /usr/users/svplus/config/profileInfo.sm

• /usr/users/svplus/statsmgrdir/parserconfig.stats

Make sure at least 900 MB of disk space in the /usr/users/svplus area can be allocated for CWM 9.2.07 installation. In the case of an upgrade, the disk space used by the existing CWM software plus free disk space should exceed 900 MB.

If you plan to use auto install and you intend to partition the disk during auto install, you have two choices for installing the WingZ application:

1. Install WingZ in /opt/Wingz before installing CWM and then execute IntegrateWingz.

2. Install WingZ in /usr/users/Wingz after installing CWM and then execute IntegrateWingz.

If you do not plan to partition the disk during auto install or if you are using manual install, you have two choices for installing WingZ:

1. Install WingZ either in /usr/users/Wingz or /opt/Wingz before installing CWM.

2. Install WingZ either in /usr/users/Wingz or /opt/Wingz after installing CWM and then execute IntegrateWingz.

You install WingZ software from the WingZ tape or CD. Note, WingZ version 2.5 should be installed for CWM release 9.2.07. After installing, contact WingZ for a runtime license and blend it with CWM 9.2.07. Failing to do so results in the "There is a problem with the registration information for this machine. Contact your system administrator" error message when you click on the CWM Report icon.

When Informix is installed on a disk array (typically the device name is /dev/vx/rdsk/rootdg/vol03) the ownership of the device and the group ownership of the device should be set to informix. The mode of the device should be 770. Otherwise, after rebooting the machine, the "Shared memory is not initialized" error message appears on the console.

When you are installing HP/OV 5.01 over an existing version, make sure the /etc/snmpd and /etc/snmpd.conf files are removed or re-named before carrying out the upgrade. If these files are not removed or renamed, it is likely you will see the following message when trying to re-start HP/OV:

object manager name: netmon
behavior:            OVs_WELL_BEHAVED
state:               NOT_RUNNING
PID:                 -
last message:        Can't talk to snmpd; see /usr/OV/log/netmon.trace for
info
exit status:         exit(1)
 

Information left in these files causes problems for the new version of HP/OV.

These files are not removed by the ovremove program.

CWM Upgrade

Upgrade of CWM from 9.1.x to 9.2.07 is supported in 9.2.07 release. The incomplete connections in the user_connection table in SV+ 9.1 may not show properly (count) on upgraded CWM 9.2.07. However, a complete user_connection table will be properly propagated to an upgraded CWM workstation.

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.

Modifying the emd.conf File

The /usr/users/svplus/config/emd.conf file provides nineteen configuration parameters that control the operation of the Equipment Manager Switch Daemon (EMSD). Each of the nineteen parameters is preceded by a comment statement that describes the parameter. To achieve better cold and warm start performance, complete the following steps:

Step 1 Search for Tftp Timeout, and change the value from 1 hour to 2 hours.

Step 2 Search for Attempt to resynchronize, then change the value from 10 times to
40 times.

Step 3 Change the next parameter, Upload TFTP file, from 4 times to 15 times.

Step 4 Search for next SNMP shelf config request, then change the value from Minimum 600 to Minimum 300 (seconds backoff).

Modifying the tftpmgr.conf File

The /usr/users/svplus/config/tftpmgr.conf file provides configuration parameters about the TFTP Request Manager. To achieve better cold and warm start performance, complete the following steps:

Step 1 Change the NumberOfRetries value to 40 from the default value of 20.

Step 2 Change the MaxTFTPSession value to 72 from the default value of 32.

CWM Dedicated IP Ports

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

• udp: 162, snmp trap

• udp: 8161, snmpAgent

• tcp: 8888, HP OV topology daemon

• tcp: 9999, HP OV database daemon

Unique Node ID

To provide unique node IDs across all CWM stations, you must copy the nodes.config file to all CWM stations. The CWM upgrade procedure creates the nodes.config file from the existing node table. This file is in the /usr/users/svplus/config directory.

Security Profiles

Default security profiles and those created by your site's system administrator are currently stored on local CWM disks in the /usr/users/svplus/config directory. This is designed to allow you to have different profiles on various CWM stations. If you want all users to have the same security profiles across all CWM stations, you must copy the files listed below to all CWM stations. The following files must be copied manually:

1. configinfo.sm

2. defaultAdmin.sm

3. defconfiginfo.sm

4. profileInfo.sm

5. userInfo.sm

To copy the security profiles from station1 to station2, complete the following steps (as user svplus or as a user with Admin privileges):

Step 1 On station1, change directory to /usr/users/svplus/config.

Step 2 Enter the remote copy command for each file, such as:

rcp configinfo.sm station2:/usr/users/svplus/confg

Step 3 Repeat the above step for all five security profile files previously listed.

CWM Database

After performing the creation of a new database by executing the create_db command, if CWM is restarted before it is synchronized with the network, it will result in a database inconsistency. In this case, perform create_db before restarting CWM to avoid database inconsistencies.

The logical_connection table count for a node in the CWM database may not match the master lcon counts in that node. This happens when the database contains FastPAD connections, or when the database has slave lcons with no connections.

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 CWM database and network may differ by value 1 for parameters PCR(0+1), SCR(0+1), MCR, ICR of some ATM-FR connections. This happens because of the difference (rounding effect) in conversion algorithms used by CWM and the Switch to convert values in cells/second units to 100 bit/second units.

• CWM CM GUI has text fields for the parameters PCR(0+1), SCR(0+1), MCR, and ICR (all in the unit of cell/second) on the ATM side of the ATM - FR ABR.FS provision window.

• The front-end application (CM GUI) passes these values to the back-end process to setup the SNMP request PDU for the Switch Agent. Following are the MIB variables and the associated value from the GUI:

atmEndptPCR <-- PCR(0+1)

atmEndptSCR <-- SCR(0+1)

atmEndptMCR <-- MCR

atmEndptQIR <-- ICR

• After the SNMP set request to the switch is done, the values are deposited in the user_connection table. Following are the database table column names:

l_pir (100 bit/sec) <-- PCR(0+1)

l_cir (100 bit/sec) <-- SCR(0+1)

l_mir (100 bit/sec) <-- MCR

l_qir (100 bit/sec) <-- ICR

• As the unit for the four columns is 100 bits/sec, conversion from cells/sec to 100 bits/sec is done.

• The conversion algorithm results in 100 bps = ((384 * cps) + 99) / 100 as shown in the following table:

cell/second	100 bit/second
50	192
5760	22119
3259	12515
2834	10883

• The conversion factor used by the switch (in this case BPX 9.2) is different from that used by CWM. Therefore, after the ConnObj Robust Message update, the user_connection table has different values for those four columns. See the following table with example values:

Cell/second	CWM 100 bit/second	Switch 100 bit/second
5760	22119	22118
3259	12515	12514
2834	10883	10882

The CWM database may intermittently have incomplete connections for the following reasons. When a multi-segment PVC is being added, if a node receives a connection add request, but doesn't respond to CWM, CWM backs out all of the segments from the other nodes which have responded to the add request and deletes those segments from the CWM DB. The node which didn't respond ends up having that segment. Because of this, any further attempt to add that connection, after the node becomes reachable, results in a "Connection already exists" error in CWM. However, this connection segment may or may not appear in the CWM database, depending upon which node was not responsive. Following are two example scenarios:

In Figure 1 and Figure 2, F1 and F2 are feeder shelves, and S1 and S2 are routing nodes. If S1 becomes unreachable after receiving an add request from CWM, but before sending the response back, Middle segment will be added on S1, between S1 and S2. However, this connection's segment details will not be in the CWM database. Once S1 becomes reachable, configuration changes will be sent to CWM and the CWM database will be updated with the middle segment details. You can delete the incomplete connection at this time, using CWM.

However, if F1 (or F2) is an MGX 8220 shelf and it becomes unreachable after receiving an add connection segment request, CWM does not get updated with the end segment details, even if the node becomes reachable. The database update happens whenever the next periodic Node Resync by CWM happens with that shelf.

• Similar DB inconsistency can happen in the case of deleting a connection operation. In this case, while a multi-segment PVC is being deleted, if a node receives a connection delete request, but doesn't respond to CWM, CWM doesn't delete this segment information from the CWM database. This results in a dangling connection segment in the CWM database, which doesn't exist on the node. However, this connection segment will be deleted from the CWM database eventually. The time taken for this database synchronization, once the node becomes reachable, depends upon the type of the node.

In the above two examples, if S1 becomes unreachable after receiving a delete request from CWM, but before sending the response back, Middle segment will be deleted on S1, between S1 and S2. However, this connection's segment details will not be deleted from the CWM database. Once S1 becomes reachable, configuration changes will be sent to CWM and the CWM database will be updated accordingly.

However, if F1 (or F2) is an MGX 8220 shelf and it becomes unreachable after receiving a delete connection segment request, CWM does not delete the end segment details from the CWM database, even if the node becomes reachable. The database update happens whenever the next periodic Node Resync by CWM happens with that shelf.

Network Configuration

Any node with IP address 192.0.0.0 or 0.0.0.0 will not be displayed or stored in CWM database. In order to configure the correct network IP address, use the cnfnwip command on the switch.

Each IPX/BPX/IGX/MGX 8220/MGX 8800 node to be managed by WAN Manager must be configured with an IP Relay IP Address (cnfnwip). The gateway node must be configured with both LAN and IP Relay IP Addresses.

The IPX/BPX routing and IPX/AF feeder nodes must be configured with read and write SNMP community names. The SNMP community names "public" and "private" are configured in CWM for GET and SET, respectively, as defaults.

The directly attached node (Gateway node) must be configured with an IP Relay IP address before starting CWM.

Node names, IP Addresses, and NWIP addresses of the nodes in a network, and across networks in multiple networks scenarios, should be uniquely configured.

Robust message updates must be enabled.

The Gateway node name must be the same as the node name specified in the config.sv file.

The maximum number of nodes that can be added through the Network Configurator is 2000. Currently, there is no error message to alert you to this situation. This is a limitation of the CWM 9.2.07 back end processes.

In the case of managing standalone MGX 8850 nodes and a tiered AutoRoute network with Automatic Discovery enabled, the addition of standalone nodes using the Network Configurator can't take place while the CWM is synchronizing with the network.

A trap will be generated when the network synchronization is done. You can activate the standalone Network Configurator by running the tool: /usr/users/svplus/bin/configurator.

Service Agent

For adding a connection, the connectionIndex must be 0 (for example, there is no need to do a GET on connAvailIndex). The actual index is internally generated by the Connection Service Agent itself.

Connection Manager

In CWM 9.2.07, the Connection Template (another set of user data) is not getting propagated to other CWM workstations.

CWM 9.2.07 does not use the Service Rate parameter applicable to FRSM channels, while adding FRSM channels, using the CIR instead. If you add FRSM PVCs through the Switch CLI using Service Rate, you will be unable to display all parameters of the PVC and unable to modify the PVC.

For DAS connections, deleting an end point from a segment, and later adding it to another segment at a very fast rate, may result in a CWM database inconsistency.

Test Connection and Test Delay do not work for connections routed through a Cisco virtual trunk cloud when the connection originates from an MGX 8220 or BPX midpoint.

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.

In the Connection Manager GUI, you must enter both the end points (node, shelf, slot, port) in the Add Connection window before entering any connection or midpoint parameters.

For an FRSM - ASI PVC connection, the error message "Remote SCR value out of range", generated by the remote BPX, indicates the CIR value of the Frame Relay side is below the acceptable limit (cell rate) of the trunk, between the MGX 8220 shelf and its routing node. To correct this problem, you can increase the value of CIR. For example, if the trunk between the MGX 8220 shelf and the routing node is a BXM trunk, the CIR value should be at least 19.2 kbps (50 cell/sec).

ABR.FS connections cannot be added with default values for an ATM-FR SIW connection. The
ICR TO value must be changed.

Certain types of connections, such as VBR.1 or CBR, with policing parameters, can't be modified by CWM if the default was changed using the Switch CLI.

While adding three segment Frame Relay connections, where one routing node is IGX and another is BPX, connections must be mastered on feeders connected to BPX. Attempting to master connections on feeders attached to an IGX hub will generate an "Internal error" error message, and the connection will not be added.

Three segment voice and data connections can only be added when both routing nodes are IGXs. This is due to a switch software limitation.

While adding connections originating and terminating on the same feeder nodes, 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.

Switch software supports only ATFR and ATFST types of connections for UXM on a feeder node. CWM does not support ATFR or ATFST for ATM to ATM connections (from the Connection Manager GUI select Configure->New ATM-ATM connection->VBR.3), the connection type on the Switch CLI will show as ATFR for all three segments. If you select an ABR.FS connection type for an ATM to ATM connection (from the Connection Manager GUI select Configure->New ATM-TM connection->ABR.FS), the connection type on the Switch CLI will be ATFST for all three segments. For all other limitations of connection types supported for UXM on feeder nodes, refer to the Switch Software Release Notes for release 9.2.03.

ATM-FR connections with a FR end point on an IGX/IPX running 8.4.x SWSW can not be set with channel type SIW (Service InterWorking) transparent or SIW translate. This feature is not supported by IGX/IPX running 8.4.X SWSW. The connections set using the 9.2.07 Connection Manager would fail.

The default values provided by the Connection Manager GUI for the Frame Relay end point parameters Ingress/Egress ECN Threshold and DE Threshold are not the same as those provided by the Connection Service Agent.

The Connection Manager GUI uses percentage notation for both the ECN Threshold and DE Threshold. However, the Service Agent MIB uses the absolute value for those MIB variables. If the defaults were used by the GUI and Service Agent, the following values would be setup for the PVC:

Parameter	GUI Default Values	Service Agent
Ingress ECN Threshold	10% of Ingress VC Q Depth -> 6554	6553
Ingress DE Threshold	50% of Ingress VC Q Depth -> 32768	32767
Egress ECN Threshold	10% of Egress VC Q Depth -> 6554	6553
Egress DE Threshold	50% of EGress VC Q Depth -> 32768	32767

The switch generates the "Failure validating remote endpoint description" error message when the PVC was modified or deleted using CWM. The problem occurs when CWM is managing a mixed release network and the node mastering the PVC has an older release than the remote end, and the remote end point is in a newer card which was introduced after the older release. This is a SWSW limitation. The PVC can be deleted using the Switch CLI.

The Connection Manager doesn't check for the SVC VPI/VCI partitioning range, if the VPI value is 0 and if SVC Hi VPI and Low VPI are set to 0 on the switch. Because of this, VPI 0 can be used for provisioning. However, if you reserve only 0 for the SVC range, the Connection Manager will not block the PVC provisioning.

In CWM 9.2.07, the FRSM-VHS card supports four separate QoS queues (versus two for legacy FRSM). The selection of a QoS queue (or channel service type) on the FRSM-VHS channel has restrictions on the service type of the ATM routing segment. For a High Priority class of connection (High Priority Queue, Q1), CWM 9.2.07 will select the CBR service type for the routing segment. For VBR-rt (real-time VBR, Q2), the VBR service type is selected. For VBR-nrt (non-real time VBR, Q3), the ATFR service type is selected. For ABR-FS (Available Bit Rate, Q4) or UBR (Unspecified Bit Rate, Q4), the ATFS service type is selected.

ForeSight connections are not supported in PXM UNI ports. In other words, you are not able to create abr.fs service type connections with end points on a PXM UNI port.

CWM Connection Support

Cisco WAN Manager 9.2 supports connections for Frame Relay (FR), Asynchronous Transfer Mode (ATM) both Unicast and ATM-Multicast, Circuit Emulation (CE), Voice, and Data service modules. The following connection types are supported:

• FR - FR

• FR - ATM

• ATM - ATM

• ATM - CE

• CE - CE

• Data - Data

• Voice - Voice

Card Types

Table 8 lists the types of cards supported in CWM 9.2 and the different cards in each card type.

Frame Relay Support

This section lists the Frame Relay service modules, cards, and ports supported in CWM 9.2.

Frame Relay Service Modules

• FRSM (4T1,4E1,8T1,8E1), FRSM-HS1b.V35 cards for MGX 8800 and MGX 8850

• UFM, FRM cards in IGX

• FRP cards in IPX (IPX has been declared `End Of Life' in SWSW 9.1)

Frame Relay Quality of Service Parameters

The following FRSM-VHS cards are supported on the MGX platforms:

• FRSM-2CT3

• FRSM-2T3

• FRSM-2E3

• FRSM-2HS2.

Frame Relay and FRSM-VHS Cards

Frame Relay and FRSM-SVH cards support the following types of ports:

• FrameRelay

• FUNI

• FrameForwarding

FRASM Service Modules

• FRASM in MGX 8220

• FRASM cards support the following port types:

  • STUN

  • BSTUN

  • FRASM

ATM Support

This section lists the ATM service modules, cards, and ports supported in CWM 9.2.

ATM (Unicast) Service Modules

The following service modules support MGX 8220 and MGX 8850:

• AUSM

  • 4T1

  • 4E1

  • 8T1

  • 8E1

• AUSM-B

  • 8T1

  • 8E1

Cards Supporting ATM and IM-ATM Ports

The following cards support ATM and IM-ATM ports:

• PXM card in MGX 8850

• ASI, ASI-155, BXM cards in BPX 8600

• UXM cards in IGX.

ATM Multicast (ATM-MultiCast) Connections

The BME card in BPX 8600 is the only card supporting multicast connections.

RPM Service Modules (Unicast Connections)

The RPM card is supported in MGX 8850.

Circuit Emulation Support

This section lists the CE service modules, cards, and ports supported in CWM 9.2.

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

• CESM-8T1,CESM-8E1: MGX 8850 and MGX 8220

• CESM-T3, CESM-E3: MGX 8850 and MGX 8220

Voice Connection Support

This section lists the voice service modules supported in CWM 9.2.

• CVM, UVM: IGX 8400

• CDP: IPX (IPX has been declared `End Of Life' in SWSW 9.1)

Data Connection Support

This section lists the data service modules supported in CWM 9.2.

• HDM, LDM, UVM, CVM: IGX 8400

• SDP, LDP: IPX (IPX has been declared `End Of Life' in SWSW 9.1)

Connection Summaries

This section provides a summary of supported connections in CWM 9.2

FR - FR Connections

Table 9 lists the supported FR - FR connections. These connections offer a choice of either FR or FRASM port types.

ATM - FR Connections

Table 10 lists the supported ATM - FR connections, including card types, for local end points (LEP) and remote end points (REP).

ATM - ATM Connections

Table 11 lists the supported ATM-ATM connections, including card types, for local end points (LEP) and remote end points (REP).

Other Supported Connections

Table 12 lists the remaining supported connections in CWM 9.2, including card types, for local end points (LEP) and remote end points (REP).

Statistics Collection Manager

Cisco recommends you use the default number of three SCM children specified by CWM 9.2.07.

When you start a stand-alone SCM, the "Cannot communicate with CWM" message is not an error message; either CWM is not active or another GUI is presently running.

You should select a routing node for the SCM time sync node.

For a group of selected nodes from which statistics files are to be collected by a stand-alone SCM, the collection period should be set to the same value for all nodes.

If statistics files are being saved, the SCM does not purge these files, even if the disk is full.

The SCM supports a maximum of 3100 nodes in stand-alone mode.

Whenever you perform a create_db operation, the statshistory.stats file must be manually deleted.

The following rules are used 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 polling interval

• The peak interval must be a factor of the polling interval

• The peak interval can be the same as the bucket interval.

The switch needs some processing time to parse the stats.enable file. Depending on the number of statistics and the number of objects, this time can be very large. Currently, SCM has a finite value for time-out (maximum 420 seconds) to wait for the switch response. Hence, 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. Keep the number of statistics, however, lose the status of stats-enabling from the SCM.

You can use CLI commands such as dspstatparms, dspchstatcnf, dsptrkstatcnf, dspportstatcnf, and dsplnstatcnf to make sure their desired stats are enabled. Note, there can be occasional time-outs if a node is busy for that period of time, however, this case, at best, is intermittent and should go away once loading on the node stabilizes. Following is the formula to calculate the time to enable statistics on the switch:

time = (stats / cnt) * delay
where
stats = (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 = a delay time between each group of stats get enabled, this is also a configurable parameter on switch.

This information is described in CR CSCdj39737.

Platform

While CWM is running, if the X server crashes for any reason, CWM should be stopped and restarted.

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

CWM must be started from a CDE environment.

Reports

The WingZ "Add Comment" option is not supported for virtual trunk and ATM connections. WingZ occasionally does not scroll up the list box properly.

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.

Software/Firmware Image Download

Always use the CWM ImageDownload program to do a SW/FW download. As CWM does not make any assumptions on the filename, it requires you to tell the SW the filename and the path to download, avoiding any inconsistencies resulting from the file naming assumptions made by the getfwrev and loadfwrev commands. If the CWM ImageDownload program does not work, there is a problem with the file transfer or the image.

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 in previous releases. Due to this correction, old traps with incorrect enterprise OIDs from trapd.log file will not be shown in the Event Browser.

• All the CWM traps will go to the CWM Events category instead of StrataView Events.

• All the nodes in the OVW topology map will appear under CWM root instead of StrataView root.

• After installation, you must run /usr/users/svplus/bin/clearOVDb.s before running ovw because the nodes under the StrataView root directory will still be there and may result in CWM database corruption.

• The /etc/opt/OV/share/conf/C/trap.conf file will be removed and replaced by the default trap.conf file and will then be merged with the StrataTrapd.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.

RPM

CWM 9.2.07 supports only ATM connection type and vbr.3 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 9.2.07 will emit an "Local/Remote end point already exists" error.

CWM 9.2.07 does not support provisioning of RPM channels for subinterface values over 32767.

For a PVC involving RPM, CWM 9.2.07 supports ATM Service Type VBR only (VBR.3 for ATM-ATM and ATM-FR for ATM to FR PVCs). The UBR Service Type is not supported for RPM by CWM 9.2.07.

CWM 9.2.07 provisions the RPM end of an "End to End" PVC by using the 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 add command and vice-versa.

To establish a channel on RPM, two IOS commands are required:

1. atm pvc---to add the RPM "leg" of the channel.

2. addcon---to add the PXM "leg" of the channel.

If the RPM leg gets deleted (new configuration restored on RPM), CWM 9.2.07 cannot detect the condition. However, if necessary, CWM 9.2.07 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, clrallcn on MGX 8850), CWM 9.2.07 cannot provision the channel until the RPM leg is manually deleted. To do that, you must login to the RPM card and perform the following IOS commands:

1. no atm pvc---to delete the RPM "leg" of the channel.

2. 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 9.2.07 station is used to provision connections on a specific RPM card, attempts to provision on the same card by another CWM 9.2.07 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 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":

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

Complete the following steps:

Step 1 telnet to the MGX 8850 and login to the RPM card (in enable mode).

Step 2 Enter the command show log and hit Return to go to the end.

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.

Cisco WAN Manager SNMP Agent Notes

CWM SNMP Agent Configuration Notes

The SNMP master agent is configured to use 8161 as a default port ID for agent communication. The SNMPAgent.conf configuration file for the master agent is located in the /usr/users/svplus/config directory. If you are running another Network Manager which uses port number 8161, this UDP port can be configured to some other port number in the SNMPAgent.conf file as follows:

Syntax:

TRANSPORT special SNMP

OVER UDP SOCKET

AT PORT 8161

The Service MIB (Connection Service MIB and Port Service MIB) uses community strings for authentication. The Connection Service Agent and Port Service Agent processes use the /usr/users/svplus/config/SNMPProxy.conf file as a configuration file. The SNMP community name strings can be configured in this file as follows:

Syntax:

GET_COMMUNITY     public

SET_COMMUNITY     private

The SNMP community names public and private are configured in this file for GET and SET respectively, as defaults.

WANCV 2.06 Notes and Cautions

Installation

You must install the CiscoView engine CD first, then install the CWM 9.2.07 CD. In the CWM 9.2.07 installation process, the WANCV 2.06 device packages will be installed automatically.

If CiscoView is already installed, you may install additional device packages or upgrade them with the /opt/CSCOcv/bin/cvinstall command. When upgrading packages, an old package may need to be removed with the uninstallpkg command before installing the new one. A good practice is to use the same revision of all WANCV device packages, and to uninstall all the previous revisions first. The installation of CWM 9.2.07 will do this automatically if CiscoView is installed before CWM.

Following are examples to install WANCV device packages:

• /opt/CSCOcv/bin/cvinstall ~svplus/wancv/AXIS.pkg

• /opt/CSCOcv/bin/cvinstall ~svplus/wancv/MGX88.pkg

• /opt/CSCOcv/bin/cvinstall ~svplus/wancv/BPX.pkg

• /opt/CSCOcv/bin/cvinstall ~svplus/wancv/IGX.pkg

Following are examples to de-install WANCV device packages:

• /opt/CSCOcv/bin/uninstallpkg AXIS

• /opt/CSCOcv/bin/uninstallpkg MGX88

• /opt/CSCOcv/bin/uninstallpkg BPX

• /opt/CSCOcv/bin/uninstallpkg IGX

For general CiscoView information including installation, see:

http://www.cisco.com/univ-src/ccden/data/doc/cview.htm

Caution A "timeout" or "too big" error response for an SNMP get-request may produce undesired results with CiscoView 4.1 or the initial release of CiscoView 4.2.

Use of CiscoView 4.2 with Software Module Updates (SMU) available from CCO is recommended.

Following is a typical SMU installation example (CiscoView on HP-UX, using C shell):

host% su root

host# cd /var/tmp

host# mkdir nmpath; cd nmpath

host# ftp 192.31.7.130

host# uncompress cview-01-sol-hpov-cv42.tar.Z

host# tar -xvf cview-01-sol-hpov-cv42.tar

host# source $NMSROOT/etc/install.cshrc

host# ./install-smu

Performance

The various timers and retry counter should be configured from the Options->Properties 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.

Network Configuration

Each BPX 8600, IGX 8400, MGX 8220, or MGX 8800 node to be managed by Cisco WAN Manager must be configured with an IP Relay IP address (cnfnwip). The Gateway node must be configured with both LAN and IP Relay IP addresses.

The BPX routing and AF feeder nodes must be configured with read and write SNMP community names. The SNMP community names public and private are configured in CWM for GET and SET respectively, as defaults.

The directly attached node (Gateway node) must be configured with an IP Relay IP address before starting CWM.

Node names, IP addresses, and NWIP addresses of the nodes in a network, and across networks in multiple networks scenarios, should be uniquely configured.

Interface Changes

The following interface changes are new in CWM 9.2.07.

SV+Network.mib

A new enumeration ima-feeder-trunk has been added to the trapTrunkType object.

SV+Service.mib

The following new objects were added:

• svConnServRateOvrRide

• frEndPointChanServRate

• svCardEgrQOSFeature

Enumeration changes:

• added ppp to the rpmEndPointEncapType object

• added oc3-2-xlr to the svPortIfType object

• deleted oc3-4-mmf from the svAtmPortIfType object

• added oc3-4-xlr to the svAtmPortIfType object

• added oc3-2-xlr to the svAtmPortIfType object

• added svCardEgrQOSFeature to the svCardEntry object

• added uai-2oc3-xlr to the svCardBackType object

Descriptions were updated for the following objects:

• frEndPointEgressQSelect

• rpmEndPointEncapType

• svPortIfType

• svAtmPortIfType

Miscellaneous:

A new sequence entry frEndPointChanServRate was added to the frEndPointEntry object.

AXIPOP.mib

The following objects were added:

• shelfCBClkRateTable

• shelfCBClkRateEntry

• cBNum

• clkRate

• shelfPowerSupplyVoltage

• chanServiceRateOverride

• chanServiceRate

• egrQosFeature

Enumeration changes:

• added critical, error, warning, notice, and info to the moduleTrapAlarmSeverity object

• added lm-HS1-4V35 to the secLineModuleType object

• added cleanupPending to the bertResourceStatus object

• added larsCom, dsuAlgorithm<x> (where <x> ranges from 4-8) to the dsx3DsuSelect object

• removed dteSt from the x21LineType object

• added dteST to the x21LineType object

The following range changes were made:

• from 5..14 to 1..30 for bertSlotNumber

• range removed from bertPort

• range removed from bertLine

• range changed from 5..14 to 1..30 for bertSupportedTestsTableIndex

• changed from 0..3 to 0..15 for chanPacketNumber

• changed from 0..511 to 0..1023 for x21LineAlarmState

Descriptions were updated for the following objects:

• moduleTrapAlarmSeverity

• bertSlotNumber

• bertStartDate

• bertSupportedTestsTableIndex

• dsx3DsuSelect

• x21LineAlarmState

Miscellaneous:

• New TRAP-TYPE shelfPowerOverLoadTrap has been added

• DisplayString size changed from 8 to 10 in bertStartDate

• New sequence entry vbrrt was added to FrChanCnfGrpEntry.

Changes to Database Tables and Definitions

This section provides information about changes in the CWM database for the 9.2.07 release of CWM from the 9.1 release.

Table 13 lists changes to the CWM database definitions from 9.2.03 to 9.2.04. The CWM 9.2.07 upgrade script and CreateDB script were updated to support these changes.

Table 14 lists changes to the CWM database definitions from 9.2.03 to 9.2.04. The CWM 9.2.04 upgrade script and CreateDB script were updated to support these changes.

New Database Tables

Table 15 lists new tables in the CWM 9.2.05 database that were not in releases prior to CWM 9.2.0.

New Database Definitions

Table 16 lists new fields in the CWM 9.2.05 database (and some recent versions of StrataView Plus) that were not in releases prior to CWM 9.2.0.

Caveats

This section provides information about known anomalies and those corrected in the 9.2.07 release of CWM. This section also provides information about anomalies known and corrected in current releases of WANCV.

Known Anomalies in CWM 9.2.07

Bug ID	Description
CSCdp38307	If shelf is unreachable during a cold start, CWM does not register upon recovery. Workaround: None.
CSCdp22795	Lines switched Trap 20105 is not received for all events. Workaround: None.
CSCdp41488	Trap 50037, secLineModuleMismatchTrap, is not generated. Workaround: None.
CSCdp41501	Trap 50993, trapBbChanFailed, is not generated when channel fails. Workaround: None.
CSCdp42659	No trap definition in trapd.conf for trap 50052: atmLineCellFormatTrap. Workaround: None.
CSCdp06240	Cannot modify PVCs through GUI on AUSM-AUSM connections. Workaround: Modify PVC through connecetion proxy.
CSCdp41835	RPM to PXM conn missing and meaningless values in atm_connection table. Workaround: Cold start CWM station.
CSCdp35428	Database not in sync - shelf table missing shelves. Workaround: Cold start CWM station.
CSCdp41330	conn_type in atm_connection table showed as frame relay. Workaround: None.
CSCdp42401	Statistics file on CWM does not match that of the Switch 9.2.21. Workaround: None.
CSCdp28154	rpm-pxm pvc deletion is intermittent. Workaround: None.
CSCdp38188	Unable to compile mibs using mosy. Workaround: None.
CSCdp41288	Failure to enable stat 58: Total Cells Rx from Line on BPX. Workaround: None.
CSCdp41375	New enabled stats in statsenablelist.stats not listed on SCM GUI. Workaround: None.
CSCdp41396	PXM stats names mismatch between SCM and MGX. Workaround: None.
CSCdp38470	Deleted PVC (PXM-RPM) but still show in Database. Workaround: Cold satrt CWM station.
CSCdp28984	/usr/users file system on cwm machine full. Workaround: Delete files manually.
CSCdp39710	ILB error causes core startup to fail/hang. Workaround: restart CWM startion.
CSCdp14071	Cannot Create Connections from Connection Manager GUI on svplus. Workaround: Cold start CWM
CSCdm64116	When re-homing ATMFR PVC, delete successful then add fails with dangler error. Workaround: retry PVC provision
CSCdm89230	3810 state not reported correctly in the Network Topology GUI. Workaround: cold start CWM
CSCdp02365	Cannot do tstcon/testdelay in SNMP for AUSM-BXM PVCs; always returns -2. Workaround: None
CSCdp05802	Node is in Minor alarm while color is grey. Workaround: cold start CWM
CSCdp06240	Cannot modify PVCs through GUI on AUSM-AUSM connections. Workaround: None
CSCdp10900	VP tunneling ADD for AUSM.E1 to BXM.OC3. Workaround: None
CSCdp12714	Network Browser does not shows lines and ports on UXM card. Workaround: None
CSCdp12999	Receiving physical line status clear trap when trunk is in Major-LOS. Workaround: None
CSCdp13002	Trap 1006 dumps all varbinds fro ds3StatsErrors. Workaround: None
CSCdp13370	addnewuser is using inappropriate option for id Workaround: None
CSCdp14310	Starting CWM Core returns a watchdog error for STG process Workaround: Restart CWM core
CSCdm04988	CWM shutdown prints an error message on kill command. Workaround: None
CSCdm25333	Connection manager does not support for MBS and SCR parameters for ABR connection on pxm. Workaround: None
CSCdm94347	Network Topology, Feeder trunks show in major alarm when added dynamically. Workaround: None
CSCdp00795	ADD FR-FR connections failed with err frEbdPtChanServType not modifiable. Workaround: None
CSCdp01954	Service MIB incorrectly defines how to build VPCs. Workaround: None
CSCdm50265	SNMP addition of PVC gives timeout and channel oversubscribe on MGX 8850.
CSCdm55926	Databroker dies on CWM workstation after warm-start. Workaround: Restart CWM.
CSCdm56837	SV+ machines will not synchronize with the network. This problem is intermittent and only occurs on a very large network. Workaround: Restart CWM.
CSCdm33677	No MIB variable defined for MCR for PXM UNI ports. No work around exists.
CSCdm40692	Wrong severity is received by HPOV and NetView when clearing alarm on IGX 8400. No work around exists.
CSCdm47444	Databroker: Inefficient logic to flag nodes with incomplete (uncommitted) segments. No work around exists.
CSCdm50254	Query for total connections in a given switch in Connection Manager GUI is taking too long. No work around exists.
CSCdm54197	CDVT0+1 allowed range different in GUI from proxy and switch. No work around exists.
CSCdm54366	Connection Manager shows wrong alarm status for FRSM-HS1 to FRSM-HS1 DAX connection. No work around exists.
CSCdm54875	CWM does not properly see the MGX 8850. No work around exists.
CSCdm37703	Could not add CE-CE connections or ATM-CE connections due to "fail to update" disk errors. No work around exists.
CSCdm58248	Syntax error in the INSTALL script during CWM installation. No work around exists.
CSCdm17657	Connection Manager and Databroker - PVC modify: Do not detect ILOG (synchronous) timeout. No work around exists.
CSCdm25333	Connection Manager does not support for MBS and SCR parameters for ABR connection on PXM. No work around exists.
CSCdm27641	AIS/OAM status are shown as OK in upgraded while new 9.2 shows as --. No work around exists.
CSCdm49488	All Platforms: When starting, NWBrowser complains about requiring a "--w." No work around exists.
CSCdm55231	Ilb Error message consistently showing in CWM window. No work around exists.
CSCdm55889	SCM GUI Error Log does not show write permissions denied errors. No work around exists.
CSCdm62433	Incomplete PVC traps after deletion. No workaround exists
CSCdm63698	PVC clear traps are missing in trapd.log. No work around exists.
CSCdm65832	Patch releases do not include version identifier. No workaround exists.
CSCdm64116	When rehoming ATMFR PVC, delete successful, then add fails with dangler error. No workaround exists.
CSCdm66147	The number of SCM children in 9.2.04 is limited to 3 due to the ILOG interface. No workaround exists.
CSCdm68531	Failure to add time sync node that is not in the selected nodes list. No workaround exists.
CSCdm64435	CWM machine not recovering from IP connection problem. No workaround exists.
CSCdm68287	Upgraded CWM and newly installed CWM differs. No workaround exists.

Anomalies Corrected in CWM 9.2.07

Bug ID	Description
CSCdp24005	CWM not able to sync up with very large 9.2.05 network -- some feeder shelves are missing.
CSCdp26561	CWM 9.2.05 not registered with 19 out of 24 AXIS nodes after sync-up.
CSCdp29327	APS data not defined in dbschema.
CSCdp30561	packet_line.aps_flag not set.
CSCdp30615	Frame PVC add hangs on cwm machine.
CSCdp36130	Cannot modify CIR for RPM to PXM connections. Workaround: None
CSCdm90761	EMSC core dumps every 1 second repeatedly.
CSCdp01954	Service mib incorrectly defines how to build VPCs
CSCdp00098	chkcore hits 99% CPU time when a core exists without appropriate permissions.
CSCdp00315	Connection Manager GUI does not show all connections with filters specified.
CSCdp03929	Missing mib valuues for asynchronousUpdate MIB object
CSCdp06259	Create CBR connections as disabled oversubscription override, displays enabled in CWM connection proxy
CSCdp12997	STG trap 26101 stgState value defined as integer in mib, transmitted as octet.
CSCdp15357	STG does not create traps if a 3810 router if no entry in CWM /etc/host file
CSCdp19352	Default policing parameters bbChanGcra1Action and bbChanGcra2Action are not set correctly
CSCdp21203	CWM 9.2.05 will not start, no data from network
CSCdp22665	Unknown SubType deen in CWM Node Table
CSCdp22829	APS disabled on the line, however, trap 20102 is not received
CSCdp28222	No Trap received for User connection modification
CSCdp30214	STG is not creating/sending trap for TRAP 26142, 26004
CSCdp32636	Cannot provision PVC on MGX/RPM
CSCdp36756	Any frame pvc snmp failure on popeye returns incorrect error messages
CSCdm38338	Unable to add RPM-PXMUNI (3 segment) connections using the Connection Manager GUI.
CSCdm68386	Cannot create or configure FR-FR connections using the Connection Manager GUI.
CSCdm72081	Addition of 3-segment RPM connection fails with an error indicating MBS out of memory.
CSCdm73718	Walking MIB svPortAlarmPortType of CWM hangs the system for two minutes.
CSCdm76242	Statistics Collection Manager (SCM) is not performing Time Sync with stand-alone MGX 8850 nodes.
CSCdm76364	TFTP child cannot connect to TFTP manager (workaround would be reduce the number of TFTP childs to 10 by modifying the /usr/users/svplus/config/tftpmgr.config).
CSCdm771129	CNMS MIB walk via Conn Proxy slows when RtmProxy is forced to RTM mode.
CSCdm78283	Unable to add 3-segment FR-FR connections using the Connection Manager GUI.
CSCdm79138	CWM does not correctly add 3-segment FR-FR connections to MGX 8830.
CSCdm79474	Cannot update fields using Connection Manager GUI.
CSCdm80751	CWM does not recognize FRSM-HS1/B ports.
CSCdm81353	Cannot walk MIB svPortAlarmPortType due to incomplete node data.
CSCdm82212	Cannot add 3-segment FRSM-2T3 connections due to VBR-RT failure.
CSCdm82423	uninstall does not remove autostart files.
CSCdm82917	Cannot modify ATM-FR VBR3 connections.
CSCdm84499	Connection Manager GUI displays the error dialog for an invalid port ID.
CSCdm85436	smain core dumps occurred when start core on MGX 8850 devices.
CSCdm85450	eventd core dumped when starting core
CSCdm85476	Connection Manager GUI core dumps when bringing up slot or port list for MGX 8830 PDT.
CSCdm85477	Cannot add abr.fs connections with ForeSight PCR set.
CSCdm85490	Cannot add abr.fs connections with ForeSight PCR set.
CSCdm85526	atmEndPointforesightPCR continues to take values from the old PCR01.
CSCdm86288	Cannot create ATM-FR, VBR3 or ATM-FR, BRFS connections with Conn Proxy.
CSCdm86685	Conn Proxy with patch 3 software fails to modify AUSM end connections.
CSCdm87312	Addition of ATM-FR connections fail for subtypes UBR1 and UBR2 for FUNI ports.
CSCdm87655	Network Topology care dumps when ILMI configuration is changed on AUSM port.
CSCdm87709	Network Topology core dumps when trunk state changes in Level III map.
CSCdm88876	SCM failed to send enable.statistics to all nodes in CWM 9.2.05 patch 3.
CSCdm89925	You must perform ilog_cleanUp as user root.
CSCdm90590	Unable to set rpmEndPointPeak
CSCdm90646	syslog trap generator (STG) core dumps at start of core.
CSCdm90783	Con proxy fails to modify connections with one AUSM 91044end point because of ForeSight set.
CSCdm91044	Attempts to modify AUSM end point connections fail with error of wrong service rate value.
CSCdm92282	In a lab environment, svAtmPortSpeed MIB walk returns invalid address values.
CSCdm92403	Errors while starting up CWM, may be because of 3810 project additions
CSCdm92703	ConnProxy can not modify/delete CESM end point connections
CSCdm94215	ConnProxy transaction timeouts experienced by provisioning engine
CSCdm94289	SNMP request getting timeouts on CWM running 9.2.05 patch #3.
CSCdp00805	MOD RPM test cases failing with error Agent returned NO SUCH NAME
CSCdp02664	9.2.06L emc does not populate line table at all
CSCdp02671	emc dumped core
CSCdp02688	HPOV install patch failed with errors
CSCdp04175	Cannot set statistics enable for 8830 on CWM_SCMSA
CSCdp05302	PXM OC3 Port data being stored in AUSM_Port table.
CSCdp05809	vism_mgcp table is not getting populated in the data base
CSCdp05880	Database SQL logic error introduced by code generator
CSCdp06148	Database inconsistency between switch and SV+ leading to failure in conn.pro
CSCdp06228	Cannot perform test-delay on any connection using Service MIB in 9.2(5
CSCdp06505	Database does not get populated
CSCdp07083	The pollerd process in PFM NMS is shutting down sometimes
CSCdp07535	Modify of all FRSM end connections fail with an error internal error
CSCdp08066	rtm core dumps in 9.2.06M
CSCdp08392	PFM NMS does not move PVC to different node when there is a node power
CSCdp09097	Controller table missing from db
CSCdp09486	ConnProxy, fails to create abr-fs connection for AUSM-BXM endpoints
CSCdp09554	In presence of unreachable nodes in network, pollerd process cannot start
CSCdp09750	Line table inconsistent
CSCdp10354	xgcp_peer port number does not get updated in the DB
CSCdp10642	Unable to set xgcp_peer port through emd
CSCdp11898	Statistics reports (WINGZ) does not have option of displaying MGX ports
CSCdp12642	The MIB files for the 3810 and STG (syslog trap generator) not in release.
CSCdk84906	In Connection Manager the GUI shows a wrong value for MCR (rpm) in ATM-ATM connections.
CSCdm50410	HPOV/trapd.log shows svplus as source for all BPX events
CSCdm50451	Not able to add DAX Connection between CESM E3s on MGX 8850 through Conn Poxy.r
CSCdm63768	Lots of Alarm states for line and ports are displayed Unknown(-1) in N
CSCdm65832	patch releases do not include version identifier file
CSCdm68531	Failure to add a Time Sync node not on selected node list
CSCdm70029	Connection Manager Alarm Suppression is not working properly
CSCdm71563	SA SCM: Node Name field has no restrictions
CSCdm73552	Cannot query IMA port via SNMP
CSCdm74325	Network Browser shows down lines status as Clear or Unknown(-1)
CSCdm74763	CiscoView displays green (enabled) for disable line 2 of FRSM-2T3E3
CSCdm75405	SA SCM Configurator: No confirmation dialog is displayed when removing
CSCdm75767	Non integer VPI.VCI combination interpreted as 0.0 by Connection Manager GUI
CSCdm76459	ConnProxy.log dumps too much garbage while running svConnAlarmConnType
CSCdm76649	ATM-FR connections added through CLI appear as FR-FR on GUI
CSCdm76957	CWM Connection Manager displays wrong value for service rate incase of 0 CIR c
CSCdm77605	CiscoView 8830 node display should be different than SES-IGX node display.
CSCdm78167	Failure to make UBR connections using CWM GUI for FRSM-VHS service mod
CSCdm79516	Network Browser issues
CSCdm81379	Update: WANDEST does not install in csh or borne shell
CSCdm83430	ConnProxy core dumps 9.2.04 patch 9CSCdm83696 ATM Cell header HEC Errors stat is not supported in release 9.2
CSCdm84930	Standalone MGX8830 fail resync: Configurator needs Model MGX8830 not M
CSCdm87140	Inconsistency in trap#50312 bet. AXIS shelf and HPOV
CSCdm87794	Network Topology, trunk status unknown when Trunk recovers from alarm
CSCdm89141	Network Topology, Alarm status not seen on Level 11 & III submaps
CSCdm89449	Release field in IlogTopodNodeMsg_s struct is null
CSCdm91758	STG, syslog messages being logged to sys.old.log instead of sys.log file.
CSCdm92155	CWM autostart does not work.
CSCdm92435	ConnProxy should bloc connection addition with wrong SubType.
CSCdm92999	STG, traps are not send in user readable format to Rtmproxy
CSCdm93201	Proxy adds a CBR1 ATM-FR connection as nrtVBR not as HI priority
CSCdm93853	Network Topology IMA Feeder Trunk Memory Leaks
CSCdm94048	Trap 50135 dumps all varbinds in trapd.log
CSCdm95230	CWM 9.1.06 could not be upgraded to 9.2.04 as defined in upgrade procedure.
CSCdp00794	MOD CESM 4T1 connections failed with error Wrong MaxBufSize
CSCdp00811	Connection Manager GUI: RPM MODIFY
CSCdp02812	WANDEST client displays files in the PST time instead of GMT.
CSCdp04327	Unable to create FR-FR multi-segment connection on MGX 8850 nodes via Connection Manager.
CSCdp06259	Create cbr connection as disable oversubscription override, displays enabled
CSCdp06983	Modify problems in Connection Manager GUI for ATMFRCBR1 cases
CSCdp07746	svMGAdminstate parameter set fails with wrong oid message
CSCdp08909	PER 71, conversion error for SNMP get request for atmendpointForesight
CSCdp09896	conn-proxy is returning in-coherent error message in svCmpaErrorLastDes
CSCdp09990	Wrong varbind for rpmPort subinterface in trapd.log.
CSCdp10675	atmQbinHiClp not displayed in qbin table
CSCdp11903	Statistics reports (WINGZ) does not display objects of Axis Sonet types
CSCdm66959	Nodes does not show in topology if database name is not stratacom
CSCdm67152	MIB should specify the card type if one or more cards have same parameter
CSCdm71558	SA SCM: No help available on Node Configuration in SCM Configurator
CSCdm77121	BPXs do not show up in Statistics collection Manager.
CSCdm79966	Need to narrow FW version support down to for FRSM-8 and RSM-VHS on PO
CSCdm81862	Connection Manager GUI 0-CIR failed on UBR
CSCdm84870	Alarm Status on Network Topology GUI does not refresh after failure
CSCdm84969	Modification of Service Rate MIB does not give error message in Conn Proxy
CSCdm87320	FUNI connection on ATM-FR cbr1 does not choose default parameters automatically.
CSCdm88356	Network Topology, select Singapore background distorts map layout
CSCdm88431	The node name sent by topod is router.cisc^A for a node named router.c
CSCdm88824	Modification failed for connection with 0 CIR on a BXM-FRSM 2E3 connection.
CSCdm89222	Network Topology, Request for trunk alarm propagation for clusters
CSCdm89378	Mod Service Rate always not required
CSCdm90373	Errors in stratacom_tarpd.conf file
CSCdm90374	Configurator exits if DISPLAY verifiable is not set (with out any errors).
CSCdm90618	CWM network browser lists PXMs and SRMs with invalid slot numbers
CSCdm90858	Launching IP Manager through Network Topology GUI is unable to pick the correct DISPLA
CSCdm91706	Network Topology, Level II map does not dynamically detect name/ip changes
CSCdm91708	Network Topology, Adding nodes for Level II and III maps not updated dynamic
CSCdm93946	Conn Proxy adds an ATM-FR connection with default channel type as NIW.
CSCdm94588	Network Topology, ghosting effect when 3810 added to routing node
CSCdm91999	Statistics are not showing up properly in Wingz.
CSCdp0449	ConnProxy did not reject attempt to modify frEndPointchanType of activity.
CSCdp00561	Display error in pollerd.log in LDM/HDM Port Fail over NMS
CSCdp03478	VISM card in the database has two fields missing.
CSCdp03900	ConnProxy fails to reject an improper PVC modify operation
CSCdp04124	Message logged by NMS log for non-DTR leads is not clear
CSCdp04840	PFM NMS is wrongly interpreting all kinds of traps as heartbeat traps
CSCdp09450	SCM statsenablelist.statistics has duplicate statid for different statistic name
CSCdp10282	ConnProxy, PER 71 AUSM-BXM & AUSM-UXM abr-fs connection MIB value incorrect
CSCdp18888	Query to port Speed returns -1
CSCdp19024	INCs to INCs data PVC creation fails
CSCdp19072	Adding BXM-FRSM PVC fails.
CSCdp05302	PXM OC3 Port data is being stored in AUSM_Port.
CSCdp12985	Need to add ethernet port failure in facility.
CSCdp12972	OBJECT-TYPE stgState (administratively up).
CSCdp12997	STG trap 26101 stgState value defined as integer.
CSCdp09092	Conn-proxy returns incoherent error message.
CSCdp09950	Bad varbind for line numbers for traps trap 50132,50133, and others.
CSCdp18611	Difference in Schema for upgrade from 9.1.06 to 9.2.06.
CSCdp17277	DB schema difference during upgrade.
CSCdp13167	Port_type for PXM ports should not be -1.
CSCdp19013	CWM does not return correct logical port.
CSCdp09051	Error message when Ciscoview is installed.
CSCdp14071	Cannot Create Connections from Connection Manager GUI.
CSCdp26561	CWM not registered with 19 out of 24 AXIS nodes after synchronization.
CSCdp24005	CWM not able to synchronize with large 9.2 network -- some feeder shelves missing
CSCdp29286	New image pxm1.1.12KK is not recognized as PXM 1.3 image by emc in 9.2.06 & 07
CSCdp35428	Database not in sync - shelf table missing shelves.
CSCdm18381	CMGUI can not see the ports on a primary BXM card after the Y-red switchover.
CSCdm40244	CWM Console Message: watchdog error: Process iosmgr, pid = <xxx> no longer restarted.
CSCdm51117	snmpget on last sequence number fails and can not GET from host other than registered manager.
CSCdm58835	While setting the RPM-RPM connections, the option to set ciscooppp for encapsulation from ConnProxy will result in connection failure. Workaround: Use CMGUI for adding RPM-RPM connections with ciscooppp as the encapsulation type.
CSCdm60138	ConnProxy: RPM-FR connection fails.
CSCdm63275	Stats enable was only being sent to first node selected in the node list. Workaround: Select nodes one by one.
CSCdm65490	GetEndParam stored procedure is not created from the file GetEndParam.sql during installation.
CSCdm66492	Card data are not populated completely in the CWM database.
CSCdm54209	While modifying an RPM-FRSM connection with maximum values, popeye7 returns a "Fore sight not enabled" error.
CSCdm62240	For FR-ATM PVCs, wrong end points were given in User Connection, Traps #25016 and #25017.
CSCdm62259	When an End to End PVC is deleted from the CMGUI, a User Connection Incomplete Trap (#25014) is sent to CMGUI and HP/OV (as expected). At the same time, however, an unexpected User Connection Clear Trap (#25016) is also sent to HP/OV.
CSCdm63596	socketd dies after killing svmain (due to incorrect ILOG license)
CSCdm66978	SV+ generates a CommBreak trap with wrong varbinds which do not match with the SV+ Network MIB.
CSCdm58562	Opening a 6th session of CiscoView through the Equipment Manager for an Axis shelf, displays the "Already running 5 Ciscoview sessions" error message and also pops up another window saying "Ciscoview - Work in progress." This occurs only while bringing up the 6th session for an Axis shelf, but works properly for other shelves. Also, the pop up window remains displayed and does not go away.
CSCdm59869	When adding a slave end point of a connection, CWM duplicates the remote NSAP/VPI/VCI with the local NSAP/VPI/VCI.
CSCdm48725	When the Topology window is clicked the second time, the window does not come up. If it is iconified, it stays iconified.

Anomalies Corrected in the 9.2.04 Release of Cisco WAN Manager

This section describes anomalies corrected in the 9.2.04 version of Cisco WAN Manager.

Bug ID	Description
CSCdm46772	Cannot set svAtmPortQueue parameters on AUSM port until five minutes after creating the port.
CSCdm47154	HP/OV will not start after the CWM install.
CSCdm47458	When deleting incomplete PVCs, the ConnProxy dies.
CSCdm48712	Trap loading issues and error log on hpov_ins.
CSCdm48731	Connection Manager GUI core dumped when a BPX 8600 node was selected.
CSCdm51715	Extremely slow 9.2 RTM performance on the CWM machine.
CSCdm52063	emsc core dumps after loading the 9.2.04A build.
CSCdm52274	Multiple Connection Manager GUI core dumps while running ConnProxy test automation.
CSCdm55565	Trap is not generated after warmstart of CWM.
CSCdm55825	SNMPAgent.conf file missing and causing all Proxies to die while starting CWM.
CSCdm57221	ConnProxy adds a VP connection when given a VCI value 0.
CSCdm57445	SNMP query of frEndPointPercUtil always returns 100 percent.
CSCdm57504	Problem with parsing RTM trap in GET response.
CSCdm03156	SCM stats enable for Broadband interfaces chops the selected stats window.
CSCdm14322	After switchcc, the logical slot was incorrect in card table.
CSCdm26812	Connection Manager GUI not accepting VCI value 0.
CSCdm44609	SA_SCM on workstation does not function.
CSCdm45189	emsd and databroker processes die the fifth time after restarting the CWM process.
CSCdm46326	portSpeed mismatches in CLI and CWM for FRSM_HS1B.V35 card.
CSCdm47827	Cannot delete incomplete middle segment using the Connection Service Agent.
CSCdm48333	CWM needs to support UXM XLR SONET mode.
CSCdm48467	Alarm Hierarchy is missing from emsd.conf in the 9.2.03 build.
CSCdm48516	Desktop will not start for non-svplus user.
CSCdm48725	Topology button does not work the second time after exiting.
CSCdm50410	HPOV/trapd.log shows svplus as source for all BPX events.
CSCdm50420	HPOV/trapd.log shows incomplete messages after deleting FR-ATM PVCs.
CSCdm50451	Not able to add DAX connection between CESM E3s on MGX 8850 through the Conn proxy.
CSCdm50477	Port speed mismatch on CESM T3.
CSCdm50802	RPM user connection traps are identified as ATM instead.
CSCdm51905	Connection Manager failed because of version checking.
CSCdm53123	CWM does not allow adding VP Tunnel connection through CMGUI.
CSCdm54847	Parameter settings in 9.2.03 required.
CSCdm55958	Incorrect sequence number for the first trap.
CSCdm15107	Need to remove StrataView reference in SvOvTopology.
CSCdm38454	Undefined variable in INSTALL.
CSCdm47635	After clicking on NWBrowser, an error message stating this option requires an argument --w.
CSCdm56865	CWM does not see incomplete MGX 8800 segments.

Anomalies Corrected in WANCV 2.07

Bug ID	Description
CSCdk86469	CiscoView is not lighting port lights (BPX front view).
CSCdp42553	CiscoView IGX package does not highlight SR-BC ports.

Anomalies Corrected in WANCV 2.07

Bug ID	Description
CSCdp21852	CiscoView does not discover RPM backcard MMF
CSCdp16004	VISM1.5: Values in Packetization Period
CSCdp26279	VISM1.5: Domain Name and IP Address parameter
CSCdp26290	VISM1.5: Row Status parameter in Internal Name
CSCdp26311	VISM1.5: Controller Domain Name should be read-only
CSCdp26319	VISM1.5: Cannot configure Shutdown Grace Timer
CSCdp26323	VISM1.5: Default Package Name cannot be configured