 Feedback
|
Table Of Contents
Release Notes for Cisco WAN Manager for Solaris 7, Release 11.0.10, Patch 3
New Features and Enhancements in CWM Release 11
Features Introduced in CWM Release 11.0.10, Patch 3
Features Introduced in CWM Release 11.0.10, Patch 2
Features Introduced in CWM Release 11.0.10, Patch 1
New Statistics Types for FRSM/AUSM/PXM1 Cards
Channelized CESM-8T1 and CESM-8E1 End Point Support
Client Primary to Secondary Switchover Notification
Client Logged-in Server Description Support
Addition of CiscoView to Security Manager Module
Addition of Support for PXM-UI-S3 Secondary BITS Clocking
Features Introduced in CWM Release 11.0.10
Improvement to Percent Utilization settings for PXM45-based MGX switches
Improvements to the Robust Trap Manager (RTM)
New Java Client Software, using Java Network Launching Protocol (JNLP)
CWM Support for Connection Trace
PXM1-E and AXSM-E: T1E1 IMA Trunking
Persistent Topology for MGX 8230/8250/8850 Feeder Nodes
Support for Read-Only Operations in Audit Trail Application
Features Introduced in CWM Release 11.0.00
Java GUIs for Config/Save/Restore and Image Download
Support for 100K SPVC per node
Connection Management GUI Support for XPVCs
Support for Release 3 of MGX 8950
Support for Release 3 of PXM45-based MGX 8850
Improvement to Statistics Enabling
New Features and Enhancements from CWM Release 10.4.10 Patch 4 Incorporated into CWM 11.0.10 Patch 1
New Features and Enhancements from CWM Release 10.5.10 Patch 3 Incorporated into CWM 11.0.10
Conversion of KBPS to CPS in Connection Manager
New Features and Enhancements from CWM Release 10.5.10 Patch 2 Incorporated into CWM 11.0.10
Connection Segment Loopback Test and Connection Loopback Test for PVC
Egress Queue Selection for FRSM-8
Displaying Master Endpoint as Local Endpoint in Connection Manager GUI
Access Control Privilege for Deleting Multiple Connections
Enhanced Node Reachability Monitoring
Setting Default Values for Filters in Connection Manager GUI
Anomalies Resolved in WANCV Release 4.22
New Features and Enhancements in WANCV Release 4.19
New Features and Enhancements in WANCV Release 4.11
Features Not Supported in WANCV Release 4.11
Features Not Supported and Known Feature Limitations in 11.0.10
Circuit Emulation (CE) Service Modules
PVC Connections Supported by CWM 11
SPVC Connections Supported by CWM 11
HYBRID Connections Supported by CWM 11
XPVC Connections Supported by CWM 11
Issue with CWM 11 Security Manager
Issues with the CWM 11 Statistics Collection Manager
Ad-Hoc Reports/Summary Reports
Limitations for CWM-to-CWM Communication
CWM 11.0.10 Server Installation or Upgrade to CWM 11.0.10 from CWM 10.5 and Earlier
Fixing the Issue before Rebooting
Downloading the 11_0_10_S97firsttime.tar File From CCO
Editing the Existing /etc/rc3.d/S97firsttime File Manually
Remedy if You Have Already Rebooted the Workstation
Replace or Edit the S97firsttime File (Requires Reboot)
Cleaning Up TEE Process (Does not Require Reboot)
Remedy if You Have Already Rebooted Workstation and Entered CWM as svplus
Replace or Edit S97firsttime File (Requires Reboot)
Remedy if You Have Already Rebooted the Workstation and Started the Core Processes
Issue with .rhosts File During Upgrade
Saving User-created Statistics Collection Manager Templates Before Upgrading
CWM 11.0.10 Patch 3 Installation
CWM Server Patch and Informix 9.21 UC7XH Installation
CWM SNMP Agent (ServiceAgent) Patch Installation
WANDEST Server Patch 3 Installation
WANDEST Client Patch 3 Installation
CWM 11.0.10 non-Java-based Client Installation
Configuring the Workstation Display
Installing InstallShield non-Java based CWM Client Software
Installing Netscape Communicator
Preparing CWM 11.0.10 Server Workstation to Launch CiscoView from Client Topology Window
Preparing CWM 11.0.10 Client Workstation to Launch CiscoView from Client Topology Window
Setting Up CWM-to-HP OpenView Communication
Enabling Connection Descriptor
Topology Discovery Configuration for AutoRoute Networks
Topology Discovery Configuration for PNNI Networks
Topology Discovery Configuration for Hybrid Networks
Topology Discovery Configuration for Stand-Alone Nodes
Connection Manager Configuration
Configuration Parameters for Connection Manager Daemon (cmgrd)
Setting Up CiscoView to Manage RPM Cards from Workstation
Configuring CiscoView for Large Networks
SNMP Service Agent Release Notes
CWM SNMP Agent Configuration Notes
SNMP Stack Parameters for CWM 11
Statistics Collection Manager Release Notes
Anomalies Resolved in CWM 11.0.10 Patch 3
Known Anomalies in CWM Release 11.0.10 Patch 3
Anomaly Status Changes in Release 11.0.10 Patch 3
Anomalies Resolved in CWM 11.0.10 Patch 2
Known Anomalies in CWM Release 11.0.10 Patch 2
Anomaly Status Changes in Release 11.0.10 Patch 2
Known Anomalies in CWM 11.0.10 Patch 1
Anomalies Resolved in CWM Release 11.0.10 Patch 1
Anomalies Resolved in WANDEST Server Release 2.3 Patch 3
Anomalies Resolved in WANDEST Server Release 2.3 Patch 2.1
Anomalies Resolved in WANDEST Server Release 2.3 Patch 2
Anomalies Resolved in WANDEST Release Server 2.3 Patch 1
Anomalies Resolved in WANDEST Client Release 2.3 Patch 2.1
Anomalies Resolved in WANDEST Client Release 2.3 Patch 2
Anomalies Resolved in CWM Release 11.0.10
Anomaly Status Changes in Release 11.0.10 Patch 1
Anomaly Status Changes in Release 11.0.10
Anomalies Resolved in CWM 11.0.00 Patch 1
Anomalies Resolved in CMF 2.1 Patch
Obtaining Technical Assistance
Obtaining Additional Publications and Information
Release Notes for Cisco WAN Manager for Solaris 7, Release 11.0.10, Patch 3
These release notes are part OL-4880-01 Rev. F0, November 17, 2003
Cisco WAN Manager for Solaris 7, Release 11.0.10 Patch 3, supports the following Cisco products:
•
Cisco MGX 8850 PXM45-based products running minimum software releases 2.0.15, 2.1.70, or 3.0.10 through 3.0.23.
•
•
•
•
•
•
Caution
Contents
FRSM Statistics 21AUSM Statistics 22PXM1 Statistics 22Network Interface Events 24CWM Internal Events 26System Events 28User Guidelines 28Overview
This document contains the following sections:
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
System Requirements
Server
Five types of machines are supported for Cisco WAN Manager 11 as standard server platforms. They are one low-end, two mid-range (Medium Level 1 and Solaris 8), one high-end, and one carrier grade platforms. Table 1 describes the configuration for each platform.
The selection of a proper CWM platform depends on a number of factors, such as the number of managed connections and the number of statistics collected and stored. Table 1 lists recommended CWM platforms based on the size of network.
The following are additional notes for CWM platform requirements:
•
•
•
•
•
•
•
•
–
–
–
–
Set the SNMP Preferences in CiscoView the first time you start CiscoView.
Client
Table 2 describes the configuration for the two minimum types of machines supported for Cisco WAN Manager 11 as a standard client platform.
Note
Stand-Alone SCM
Five types of machines are supported for CWM Release 11 Statistics Collection Manager software as stand-alone platforms. They are one low-end, two mid-range (Solaris 7 and Solaris 8), one high-end, and one carrier grade platform. Table 3 describes the configuration for each platform.
Solaris Patch Requirements
This section lists the patches required on Solaris 7 in support of CWM 11.0.10. Use the search facility on the SunSolve site to search for the 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.
After installing the Solaris 7 operating system, you must install the following patches:
•
•
•
•
•
•
•
•
•
•
•
•
•
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
To install the patches, complete the following steps:
Step 1
When you use the search facility on the SunSolve site, search for the six-digit patch ID number and do not include the two-digit patch version number. The version can be later than the one referenced above.
Step 2
Step 3
patchadd ./106300-09patchadd ./106327-05patchadd ./106541-21patchadd ./106950-09patchadd ./106980-10patchadd ./107081-11patchadd ./107153-01patchadd ./107544-03patchadd ./107636-03patchadd ./108376-03patchadd ./110881-01patchadd ./111980-01patchadd ./112300-01Step 4
Step 5
Step 6
Patches are available to Sun Microsystems customers over the Web at www.sunsolve.sun.com. You can display which patches are already installed in the CWM workstation by entering the Solaris showrev -p command.
The default partition for CV is /opt/CSCOpx, but can be user specified at installation. In any case, the partition should have 500 Mbytes of space.
CWM Software Packaging
Following is the list of CDs for the CWM 11.0.10 release:
•
–
–
–
–
–
•
–
–
–
–
–
–
The Service Agent software is provided on a separate CD. This CD is ordered separately from the CWM 11 release CD set.
•
–
The Standalone Statistics Collection Manager software is also on a separate CD. This CD is ordered separately.
•
–
The Wingz Release 2.5.1 software is also on a separate CD.
•
The Wingz version number is located on the license key (separate piece of paper) that comes with Wingz. The version number can also be found in the HELP menu. When you click on the About box, the version number displayed is 2.5, however, clicking below the 2.5 line provides the license information followed by 1.1.7, which indicates Wingz version 2.5.1.17.
HP OpenView Requirements
The CWM 11.0.10 release works with HP OpenView Release 6.2 or 6.3 for Solaris 7. See "Third Party Product Limitations Notes" for HP OpenView patches required by CWM.
Note
For HP OpenView installation requirements and procedures, please refer to "HP OpenView Network Node Manager Products, Installation Guide" (part # J1136-90000 from HP).
HP OpenView 6.2 or 6.3 is not bundled with CWM CDs. You must order HP OpenView separately. HP OpenView is used for viewing the Event Log. It is not required for any other CWM procedures.
INFORMIX Requirements
The CWM 11.0.10 release uses Informix 9.2 for database operations. The INFORMIX software is bundled with CWM software on the CWM Server/Client CD. The INFORMIX program is automatically installed during CWM installation.
Wingz Requirements
The Report Application contained in the CWM 11.0.10 release uses Wingz 2.5.1. For the Ad-Hoc Report Application to work properly, the Wingz DataLink program must be installed along with Wingz software. Note that with CWM 11.0.10, the Report Application can be launched from a command line prompt.
Wingz and Summary Reports are no longer available within either the client or the server and can no longer be launched from the Network Topology application as a pull down with either the client or the server.
To launch Wingz reports, complete the following procedure:
Step 1
Step 2
Note
To launch summary reports, complete the following procedure:
Step 1
Step 2
Supported Hardware
This section provides information about the hardware supported by CWM Release 11.0.10 Patch 3.
Existing Hardware
Table 4 lists the existing hardware supported prior to CWM Release 11.0.10 Patch 3.
Supported Release Hardware
Table 5 lists the supported release hardware for CWM Release 11.0.10 Patch 3.
Certified Releases
The following releases were tested with CWM Release 11.0.10 Patch 3:
•
–
–
–
•
–
–
–
•
–
–
•
–
–
•
–
–
•
–
–
WANDEST Certification Matrix
Wandest 2.3 Version
2.3
2.3 Patch 1
2.3 Patch 2
2.3 Patch 2.1
2.3 Patch 3
The following version of CWM was certified with WANDEST.
WANDEST 2.3 Patch 1, 2, and 2.1 are bug-fix only releases and have the same feature content as WANDEST 2.3 introduced with 11.0.10. All Patches contain cumulative fixes and features from the prior patch release.
Refer to "Caveats" section for the list of resolved anomalies.
New Features and Enhancements in CWM Release 11
Features Introduced in CWM Release 11.0.10, Patch 3
This is a bug fix only release. Please see the section entitled Anomalies Resolved in CWM 11.0.10 Patch 3 for a list of fixes in this release.
Features Introduced in CWM Release 11.0.10, Patch 2
The following new feature and enhancement have been introduced in CWM Release 11.0.10 Patch 2:
Enhanced Network Configurator
•
Features Introduced in CWM Release 11.0.10, Patch 1
The following new features and enhancements have been introduced in CWM 11.0.10 Patch 1:
Node Resync
The Node Resync feature is extended with the following functionality for SPVCs:
There are now three types of node resync. The Level 1 Update and Level 2 Update are available through the node resync menu item under the CWM Topology GUI. The Memory Database Resync is available using a script. More details are provided below:
a.
b.
c.
> /usr/users/svplus/tools/CacheResyncIt should take 869 seconds to sync the databaseusing an ultra 60Do you want to proceed (y/n) yCache-Database Resync took 754 secThe Memory/Database resync process blocks provisioning, clears the user_connection table and re-flushes all the connections from its cache to the user_connection table. The time it takes to complete these operations is dependent upon the number of connections and the type of machine the CWM is running on.
Note
New Statistics Types for FRSM/AUSM/PXM1 Cards
The Statistics Collection Manager (SCM) now includes the following new statistics types for FRSM PVC connections and ports: one new statistics type for AUSM ports and one new statistics type for the PXM1 card. This support has been added only on the PXM1-based MGX platform.
FRSM Statistics
Connection Statistics
Port Statistics
AUSM Statistics
Port Statistics
totalIngrClpSetRcvCells
The number of CLP set cells received in Ingress direction on the port
PXM1 Statistics
Port Statistics
Health Monitor
Health Monitor is a new feature supported in CWM 11.0.10 Patch 1. It allows CWM to collect network management health related data (network-related events, CWM internal events, and system events) and to record them into /usr/users/svplus/log/cwmErrors.log and generated SNMP traps in HPOV. To enable Health Monitor, change "HEALTH_MONITOR" flag in svplus.conf to ON before starting CWM.
The following three types of network management health information are monitored:
•
•
•
Events are grouped into following three categories:
•
•
•
Events are classified as belonging to one of the following three severity levels (only on Health Monitor):
•
•
•
Two different actions will be taken in response to the events:
•
•
The network events are grouped into 4 broad categories:
•
•
•
•
The internal events are grouped into 2 different categories:
•
•
The system errors (Trap # 28301) are reported when CWM detects low disk, swap or db space.
Network Interface Events
cwmfrNetworkCommFailure Events (trap# 28101)
cwmfrNetworkProcessingFailure Events (trap# 28102)
Reported when CWM encounters error while processing information from network or max retries have been attempted during the processing. All protocol errors are also reported under this category.
cwmfrNetworkTimeoutError Events (trap# 28103)
cwmfrNetworkConfigurationError Events (trap# 28104)
CWM Internal Events
cwmfrWatchdogError (trap#28201)
cwmfrGatewayStatus (trap#28202)
cwmfrCwmInternalError (trap#28203)
cwmfrCwmDatabaseError(trap#28204)
System Events
(cwmfrCwmSystemError trap#28301)
User Guidelines
This section presents guidelines for user actions in response to certain events.
Network Interface Events
CWM Internal Events
System Events
Channelized CESM-8T1 and CESM-8E1 End Point Support
This feature adds support for adding, modifying, and/or deleting connections between channelized CESM-8T1 and CESM-8E1 end points using either the Connection Manager GUI or the SNMP Service Agent. When using this feature the port speeds and number of DS0 available will be the same on the ports on both ends.
Client Primary to Secondary Switchover Notification
CWM 11.0.10 patch 1 provides notification to clients (in the form of a pop-up window) when a primary to secondary switch over has occurred.
Client Logged-in Server Description Support
The client window description bar now includes a description of which CWM server the client is logged into.
Addition of CiscoView to Security Manager Module
The Security Manager provides controlled access to multiple users of Cisco WAN Manager (CWM), based on the user's UNIX User ID and password. CWM 11.0.10 patch 1 adds support for controlled access to CiscoView operations through the Security Manager. Refer to Chapter 6 of the Cisco WAN Manager User Guide for general instructions on how to configure and use the Security Manager.
Addition of Support for PXM-UI-S3 Secondary BITS Clocking
The PXM-UI-S3 back card, which provides Stratum level 3 clock source inputs, has been enhanced to accept two external BITS clock inputs. A new interface, 7.36, has been added to support one more external clock input. CWM now recognizes and supports interface 7.36 (the second BITS clock input of the PXM-UI-S3 back card). The properties and use of this newly added interface is exactly the same as that of interface 7.35, which refers to the first BITS clock input of the PXM-UI-S3 back card. The second BITS clock source can be added as primary, secondary or tertiary clock source, which is the same for any other clock interface.
Features Introduced in CWM Release 11.0.10
The following new features and enhancements have been introduced in CWM 11.0.10:
Improvement to Percent Utilization settings for PXM45-based MGX switches
CWM 11.0.10 adds a configuration parameter in /usr/users/svplus/cmgrd.conf called PNNI_PER_UTIL_FLAG. If this flag is set to DISABLE, then CWM will not set %util on all PNNI endpoints, hence defaulting them to 100%. Also whenever %util is to be mapped from a PNNI endpoint for a hybrid or XPVC connection, the %util from the PNNI endpoint will be ignored and the %util will be taken from the other end of the connection. If the flag is ENABLE, then CWM behavior will be to set the %util as it is doing today and also map the %util from the PNNI end wherever applicable. The default is ENABLE.
Improvements to the Robust Trap Manager (RTM)
A ping mechanism has been added to RTM. Supporting this ping mechanism requires that the Solaris 2.7 workstations have the following patch:
–
The path at the SunSolve site to get 106541-21 for download is:
http://sunsolve.sun.com/pub-cgi/retrieve.pl?doc=fpatches%2F106541&zone_32=106541-21
To install this patch, perform the following steps:
Step 1
Step 2
Note
Note
New Java Client Software, using Java Network Launching Protocol (JNLP)
It is no longer necessary to install the CWM client software from the distribution CD. CWM 11.0.10 client software can be deployed directly from the CWM server. Refer to the CWM Installation Guide for Solaris 8, Release 11 (78-14230-01) for more details.
Security Banner Feature
CWM 11.0.10 adds a blank, customizable field in the CWM login screen that allows you to set up a customized security message that displays upon first logging in to Cisco WAN Manager.
The Banner Field is editable with administrator privileges.
The Banner Field is fixed to 4 lines of text. If text exceeds 4 lines, a field scroll bar will appear.
The Banner Field text is stored in a securitybanner.conf file and only the administrator has write privileges.
CiscoView 5.4.1
CWM 11.0.10 uses CiscoView 5.4.1. CWM 11.0.00 used CiscoView 5.3. CV 5.4.1 is the latest release of CiscoView and delivers significant performance improvements with faster GUI response and more efficient SNMP handling.
CiscoView 5.4.1 patches for Solaris 2.7:
106980-10
106327-05
107081-11
107636-03
108376-03
112300-01
Java Client
CWM 11.0.10 includes a Client application designed to run on a Windows 2000 PC. CWM Java Client will install from the CWM Workstation and will run as a java applet. It will operate all of the CWM functionality with the exception of Motif applications. Wingz and Summary Reports remain as Motif applications and are not available from the Client. To run Wingz or Summary Reports either telnet to the CWM Workstation or run directly from CWM.
CWM Support for Connection Trace
In CWM 11.0.00, Connection Trace was not supported for MGX 8850 routing nodes. In CWM 11.0.10, Connection Trace is supported for all service modules on routing nodes including:
–
–
–
–
–
–
Connection trace should always be done on the Master end of the connection.
CWM Support for MGX 8950
In addition to previous MGX 8950 support, CWM 11.0.10 also supports the RPM-XF high-density routing module.
PXM1-E and AXSM-E: T1E1 IMA Trunking
CWM 11.0.10 supports the PXM1-E and AXSM-E T1/E1 IMA feature introduced in MGX 3.0.10. CWM support includes:
–
–
–
–
–
SRM-E APS
CWM 11.0.10 provides CiscoView configuration for SRM-E APS. CWM recognizes APS traps and flows-through RTM to Service Agent.
SRM-E APS support is in the MGX 8850 with PXM 45.
AXSM-E Double Density
CWM 11.0.10 supports the AXSM-E card with a second backcard. Prior to CWM 11.0.10, only one back card was recognized.
Persistent Topology for MGX 8230/8250/8850 Feeder Nodes
In prior releases, when a MGX feeder node became unreachable and CWM was restarted, the unreachable MGX did not appear in CWM Topology. In CWM 11.0.00, node persistency was added for MGX 8850 routing nodes and in CWM 11.0.10 this capability is extended to include MGX feeder nodes. When CWM is restarted, the unreachable feeder node remains in the network topology and is indicated in CWM Topology as an unreachable, grey state. The Node Persistency feature provides increased reliability in the event of double failures of a MGX 8230/8250/8850 feeder nodes and applies to MGX 8230/8250/8850 feeder nodes. In CWM 11.0.10 there is no support for persistency of links.
Support for Read-Only Operations in Audit Trail Application
Audit trail support for CMGUI and Config Save/Restore operations is extended to include Read-Only operations in CWM 11.0.10. Monitors CWM user activity and logs to a file all read, create, modify and delete activity in CMGUI and Config Save/Restore modules. The log includes user, action and time and date. Also includes file archival and retrieval features. CWM Audit Trail improves operations accessibility and scalability through improved security of the management network. Audit Trail applies to CMGUI and Config Save/Restore modules, but Audit Trail does not log for any other CWM modules, add-on modules or CiscoView.
WANDEST 2.3
WANDEST version 2.3 introduces an automation feature that provides the ability to configure and activate automated upload requests from the WANDEST client that will occur at a configurable upload interval.
The new Automation feature allows a WANDEST client to issue upload requests to the WANDEST server, automatically at a set interval. The setup of the automated upload requests, including the configuration of the upload interval, are configured using the AUTO command, issued from the WDADMIN program.
Descriptions of each parameter follow:
–
–
–
–
Note
To stop the automation feature, exit the WANDEST WDADMIN utility by executing the quit command. Refer to the WANDEST Installation and Reference, Part number DOC-7814109=.
Support for Filtered Alarms
In previous CWM releases, the node alarm that displayed on CWM Network Topology GUI (the node shelf integration alarm) was comprised of the aggregated alarm of all slot/line/port/connection alarms in that node. However, some customers prefer to see a "filtered" integrated shelf alarm which ignores all lines, ports, connections and feeder alarms so that the highest level of alarm could not be triggered by a line.
The Filtered Alarm feature also provides the ability to have the feeder trunks' alarm reported as part of their parent routing nodes' aggregated alarm.
Also, when a few routing nodes are grouped into a group, the Filtered Alarm feature also provides the ability to have the alarm of the routing trunks which connect the grouped nodes reported as part of group aggregation alarm.
Features Introduced in CWM Release 11.0.00
The following new features and enhancements have been introduced in CWM 11.0.00:
Java GUIs for Config/Save/Restore and Image Download
Within the Select a file to Download or Restore windows there is a field for User ID and Password. The Save and Restore buttons will remain greyed out (unselectable) until a User ID and Password is entered. The PXM1-based switches (MGX 8230, MGX 8250, and PXM1-based MGX 8850) use tftp for uploading and downloading configurations. You can enter any username or password in these fields and the Save and Restore buttons will be active.
Persistent Topology
In CWM 11, MGX nodes are stored persistently in the CWM database and network gateway node. Therefore, when CWM is restarted, the unreachable node remains in the network topology and is indicated in CWM Topology as an unreachable, grey state.
Support for 100K SPVC per node
Audit Trail
Monitors CWM user activity and logs to a file all create, modify and delete activity in the Connection Manager and Config Save/Restore modules. The log includes user, action and time and date.
Connection Management GUI Support for XPVCs
Configurable Service Class Templates
This feature provides the ability to modify a Service Class Template and reuse the SCT ID number. Configurable SCTs apply to the AXSM, AXSM/B, AXSM-E, FRSM12-T3E3 and PXM1-E cards. Configurable SCTs are available for MGX 8850 and MGX 8950, but not for AXSM-E on the MGX 8950.
Support for Release 3 of MGX 8950
CWM 11 provides GUI, Service Agent and Statistics support for Release 3 of the PXM45-based MGX 8950 platform in much the same way as Release 3 of the PXM45-based MGX 8850, except that CWM 11 does not support the RPM-XF high-density routing module on the MGX 8950.
Support for Release 3 of PXM45-based MGX 8850
With Release 3 of the PXM45-based MGX 8850, CWM 11 supports the following two new broadband service modules:
–
–
–
Support for PXM 1E
The following lists the support for the PXM1E card:
–
–
–
–
Improvement to Statistics Enabling
When enabling statistics by selecting multiple nodes at a time in the SCM, enabling statistics on all the nodes will only work if all of the nodes have the same card types or cards of the same family.
New Features and Enhancements from CWM Release 10.4.10 Patch 4 Incorporated into CWM 11.0.10 Patch 1
The following enhancement has been added in the 10.4.10 Patch 4 Release of CWM:
CWM Auto-Restart
This option automatically starts the CWM core after a reboot.
Configuring Auto-Restart
Step 1
Step 2
#cd /etc/rc3.dStep 3
#!/bin/cshsu - svplus -c /usr/users/svplus/scripts/start_SV+ &For example: Script name - S99init_sv
Step 4
#chmod 755 S99init_sv
Note
For more information on configuring this feature, refer to the /etc/init.d/README file.
New Features and Enhancements from CWM Release 10.5.10 Patch 3 Incorporated into CWM 11.0.10
The following new features and enhancements have been added in CWM 11.0.10 with the incorporation of CWM Release 10.5.10 Patch 3 features:
Conversion of KBPS to CPS in Connection Manager
To resolve issue CSCdx29985, Patch 3 of CWM 10.5.10 adds a toggle checkbox to the Options pulldown in the Connection Manager that is used for converting CPS values to KBPS value or vice versa. The default is unchecked (display as CPS). Any changes in the "Show CPS parameters in Kbps" checkbox will be reflected in all the Connection Manager GUI sessions opened after changing the toggle. Any connection addition/modification screens opened prior to changing the toggle must be closed and reopened to reflect the change in units calculation. This feature is useful especially when the traffic parameters in the Connection Manager GUI are shown in different units for local and remote endpoints. An example would be an ATM-FR connection, wherein the ATM traffic parameters are displayed in units of CPS (cells per second) and the frame relay parameters are displayed in KBPS (or BPS).
New Features and Enhancements from CWM Release 10.5.10 Patch 2 Incorporated into CWM 11.0.10
The following new features and enhancements have been added in CWM 11.0.10 with the incorporation of CWM Release 10.5.10 Patch 2 features:
Connection Segment Loopback Test and Connection Loopback Test for PVC
BPX already uses the CLI to initiate a Connection Loopback Test using the testpingoam command. This test can be initiated at the egress endpoint of a connection in a BPX network. The assumption is that the egress endpoint is connected finally to a remote end CPE. In CWM 10.5.10 patch 2, the CWM Service Agent and Connection Management GUI now provide the support for this testpingoam option. When this test is applied to the connection endpoint on a BXM service module, it initiates an end-to-end ATM loopback cell that traverses through the intermediate switches to reach the CPE endpoint and send back to the originating BXM port.
In addition, CWM 10.5.10 patch 2 also supports the enhanced Connection Segment Loopback test (tstconseg) on BPX. This test uses segment loopback cell which is returned by the first segment end point in the connection. This is useful for isolating the fault in case the end-to-end Loopback test fails. With enhancement in BXM firmware MFN and BPX 9.3.30 or newer version, the successful Connection Segment Loopback test result will also include the round trip delay measurement.
Limitation: The CPE is assumed to be able to recognize and return the end-to-end loopback cell back into the network.
Egress Queue Selection for FRSM-8
The Connection Management GUI provides an Egress Queue Parameter option under the Edit menu to allow the user to override the selection of egress queue. By default, the egress queue is set to high priority for cbr, vbr2-rt and vbr3-rt service types, and low priority for abr, ubr, abrstd, vbr2-nrt and vbr3-nrt. This egress queue user selection can be applied to FR-FR, FR-ATM and FR-RPM connection type.
Limitation: The FRSM-8 firmware must be at version 10.0.20 or newer.
Displaying Master Endpoint as Local Endpoint in Connection Manager GUI
In the Connection Manager GUI, after selecting a node or a port, the user is given a set of options to decide what connections are retrieved and displayed in a table. 10.5.10 patch 2 provides an additional option called "Set Master as Local" to toggle between listing the connection master end points or the endpoints of the selected port as the endpoints in Local Endpoint Column. Once this selection is made, it stays in memory until the user changes it again or until the Connection Manager GUI is closed and reopened.
Access Control Privilege for Deleting Multiple Connections
The Security Manager provides a finer granularity of access control to connection deletion. The User Security Administrator can configure a CWM user to have the privilege of deleting a single connection at a time only or the privilege to delete a single or multiple connections in one operation.
Enhanced Node Reachability Monitoring
Instead of using just a repeated SNMP timeout, CWM is enhanced to use also the lower level IP ping to detect any Node Un-reachability condition. By doing this, the Network Topology GUI reflects such condition in about 30 seconds if a failure of the IP connectivity to the node is concluded. The number of retries and the periodic ping cycle time are configurable using configuration data file.
Limitation: The SNMP timeout is the only way to detect SNMP application layer failure. Such failures are reported within 9 minutes as before.
Setting Default Values for Filters in Connection Manager GUI
The Filter Settings in the Connection Manager GUI (invoked via Edit->Filters) now includes a "Defaults" button to reset the default values of all check boxes. The default Filter Settings value is all check boxes selected and the descriptor field cleared. This provides an alternative to the "Reset All" button which resets to the previously saved settings.
AUSM Egress Counters
Support has been added for the following AUSM Egress Counters:
•
•
•
•
•
•
•
•
•
Anomalies Resolved in WANCV Release 4.22
As part of Cisco WAN Manager Release 11.0.10 Patch 3, the CiscoView MSSBU device packages (WANCV) were upgraded to Release 4.22 to support CiscoView 5.4.1.
The bugs listed in Table 6 were fixed in WANCV Release 4.22:
Table 6 Bugs Fixed in WANCV Release 4.22
CSCea22451
CV 5.4 gave failed to refresh error against MGX 8850
CSCdz69325
Refreshed failed errors on view of MGX 8850 on Release 1 chassis
New Features and Enhancements in WANCV Release 4.19
As part of Cisco WAN Manager Release 11, the CiscoView MSSBU device packages (WANCV) were upgraded to Release 4.19 to support CiscoView 5.4.1.
Changes Made in WANCV Release 4.19
•
•
•
•
•
•
•
•
•
Bugs Fixed in WANCV Release 4.19 (see Table 7)
New Features and Enhancements in WANCV Release 4.11
As part of Cisco WAN Manager Release 11, the CiscoView MSSBU device packages (WANCV) were upgraded to Release 4.11 to support CiscoView 5.4.1.
The following features were introduced with Release 4.11:
•
Features Not Supported in WANCV Release 4.11
The following features are not supported in WANCV 4.11:
•
•
•
•
•
•
•
•
Features Not Supported and Known Feature Limitations in 11.0.10
The following features are not supported in CWM 11:
•
•
MGX 8850 Release 2.1.60 and SES Release 1.1.60 supports UNI 4.0 ATM interface, PNNI Multi-peer group, and AINI as an alternative to Multi-peer group. CWM 11 supports the configuration of the UNI 4.0 ATM interface and AINI, however, the configuration of PNNI Multi-peer group is supported only through the Switch Software CLI.
•
BPX 9.3.30 Switch Software is required for the Enhanced NNI and XPVC/XPVP Provisioning features. Other new features added to BPX 9.3.30 Switch Software are supported only at the Switch CLI.
CWM does not support the URM card on the IGX.
CWM does not support 800 part numbers
•
•
•
•
•
This limitation refers to DAX connections on MGX 1 nodes. When a DAX connection on an MGX 1 node goes to failed state the abit status displayed on the connection manager for this particular connection always stays "ok"
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
Error:Receives distant call to unknown function.Error:Receives distant call to unknown function...These messages have no effect on system operation. The same messages are logged in the ilberrors* log files.
Supported Connections
This section lists the connections that CWM 11 supports.
Supported Cards
CWM 11 supports the following card types for various connections.
Frame Relay
The following Frame Relay (FR) service modules are supported:
•
•
•
•
CWM 11 supports the following FRSM-VHS cards in Release 1 of the MGX 8850 (PXM1-based) platform:
•
•
•
•
ATM Service Modules
CWM 11 supports the following types of Service Modules for ATM (Unicast) connections:
•
•
•
•
•
•
•
•
•
•
Circuit Emulation (CE) Service Modules
CWM 11 supports the following types of Service Modules for Circuit Emulation
•
•
•
Voice Service Modules
CWM 11 supports the following types of Voice Service Modules:
•
•
•
Data Service Modules
CWM 11 supports the following types of Data Service Modules:
•
•
•
•
PVC Connections Supported by CWM 11
The following table lists the connection types support for PVC connections. The table gives the connection type followed by Local and Remote EndPoint Card Type. The Local and Remote Endpoints can be reversed and the same rules and restrictions apply. All these cards should be on a Auto Route Platform namely BPX, IGX, MGX 8220, MGX 8850/8250/8230 Release 1
Table 8 lists the PVC connection types supported by CWM 11.
Table 8 PVC Connections Supported by CWM 11
FR-FR
with Foresight
FR
FR
no QOS support
FR-FR
with Foresight
FRQOS
FR, FRQOS
QOS can be specified by ChanServType and it has to be abr (4).
FR-FR
without Foresight
FR
FR
no QOS support
FR-FR
without Foresight
FRQOS
FR,
FRQOSFollowing QOS specified by `ChanServType' attribute
hi_priority, ubr, nrt-vbr, rt-vbr, stdabr
ATM-FR
nrt-vbr3,abr.fs
ATM
FR
no QOS support on FR endpoint;
ATM-FR
cbr1,
ubr(1,2),
nrt-vbr(2,3),
rt-vbr(2,3)
abr.fs,
abr.1
ubr(1,2)
ATM
FRQOS
QOS supported on FR endpoint, QOS chosen by CWM automatically based on Service.
Some ATM endpoints may not support all service types. Look below in Table 9 for the Service type restrictions on ATM endpoints
RPM-FR
nrt-vbr3
RPM
FR
no QOS support on FR endpoint
RPM-FR
nrt-vbr3, ubr1, abr1
RPM
FRQOS
QOS supported on FR endpoint; QOS chosen by CWM automatically based on Service.
ATM-ATM
cbr1,
nrt-vbr(1,2,3),rt-vbr(1,2,3)
ubr(1,2),
abr.1,abr.fsATM
ATM
Both ATM endpoints must support the Service. Look below in Table 9 for the Service type restrictions on ATM endpoints
RPM-RPM
nrt-vbr3,
abr1,
ubr1
RPM
RPM
ATM-RPM
nrt-vbr3,
abr1,
ubr1
ATM
RPM
ATM-ATM
atfst
BXM/BXM-E/UXM
BXM/BXM-E/UXM
ATM-FR
atfst
BXM/BXM-E/UXM
FR, FRQOS
ATM-FR
atftfst, atfxfst
BXM/BXM-E/UXM
UFM
UFM card must be on a routing IGX node.
ATM-ATM
cbr1,
nrt-vbr(1,2,3),
ubr(1,2),
abr.1,abr.fsATM-Multicast
ATM-Multicast
multicast connection;
local and remote port combinations: root-leafCE-CE
cbr1
CE
CE
Structured/unstructured; both endpoints must be either structured or unstructured with matching bandwidth
ATM-CE
cbr1
ATM
CE
CE structured or unstructured;
ATM endpoint bandwidth should be equal to or greater than the CE endpoint bandwidthData-Data
data
DATA
DATA
The data service modules are listed in section above
Voice-Voice
voice
VOICE
VOICE
All voice service modules listed in above section except VISM are supported for this connection type.
ATM-VISM
cbr1,
nrt-vbr(1,2,3),rt-vbr(1,2,3)
ATM
VISM
Some VISM and ATM endpoints may not support all Service types. Look below in Table 9 for the Service type restrictions on ATM and VISM endpoints
VISM-VISM
cbr1,
nrt-vbr(1,2,3),rt-vbr(1,2,3)
VISM
VISM
Some VISM endpoints do not support all Service Types. Look below in Table 9 for service type restrictions on VISM
VISM-RPM
nrt-vbr3
VISM
VISM
Some VISM endpoints do not support all Service Types. Look below in Table 9 for service type restrictions on VISM
Table 9 lists the cards that belong to the various groups, such as ATM, FRQOS, and so forth, that are referred to in Table 8.
SPVC Connections Supported by CWM 11
The following table lists the connection types support for SPVC connections. The table gives the connection type followed by Local and Remote EndPoint Card Type.The Local and Remote Endpoints can be reversed and the same rules and restrictions apply. All these cards should be on a PNNI Platform namely BPX with SES, MGX 8850 Release 2 and 3, MGX 8950, MGX 8830 Release 3
Table 10 lists the connection types for SPVCs supported by CWM 11.
Table 10 SPVC Connections Supported by CWM 11
FR-FR
Without Foresight
FR
FR
No foresight support on PNNI;
chanServType on FR end can be one of the following:
high_priority, nrt-vbr, rt-vbr, ubr, or stdabr
ATM-FR
cbr1,
nrt-vbr(2,3),rt-vbr(2,3)
ubr(1,2),
abr.1ATM
FR
Look below in Table 9 for restrictions on service types for FR endpoints and Internal and External VSVD on ATM endpoints.
RPM-FR
nrt-vbr3,
rt-vbr3
ubr1,
abr1
RPM
FR
Some RPM endpoints may not support all of these Service Types. Look in Table 9 for Service Type restrictions on RPM endpoints.
ATM-ATM
cbr1,
nrt-vbr(1,2,3),rt-vbr(1,2,3)
ubr(1,2),
abr.1ATM
ATM
Look below in Table 9 for restrictions on Internal and External VSVD on ATM AXSM endpoints.
ATM-RPM
nrt-vbr3,
rt-vbr3,
abr-1,
ubr-1
ATM
RPM
Some RPM endpoints may not support all of these Service Types. Look in Table 9 for Service Type restrictions on RPM endpoints.
RPM-RPM
nrt-vbr3,
rt-vbr3,
abr1,
ubr1
RPM
RPM
Some RPM endpoints may not support all of these Service Types. Look in Table 9 for Service Type restrictions on RPM endpoints
CE-CE
cbr1
CE
CE
Structured/unstructured;
both endpoints must be either structured or unstructured with matching bandwidth.
ATM-CE
cbr1
ATM
CE
CE structured or unstructured;
ATM endpoint bandwidth should be equal to or greater than the CE endpoint bandwidth.ATM-VISM
cbr1,
nrt-vbr(1,2,3),
rt-vbr(1,2,3)
ATM
VISM
VISM-VISM
cbr1,
nrt-vbr(1,2,3),rt-vbr(1,2,3)
VISM
VISM
VISM-RPM
nrt-vbr3,
rt-vbr3
VISM
RPM
Some RPM endpoints may not support all of these Service Types. Look in Table 9 for Service Type restrictions on RPM endpoints.
Table 11 lists the cards that belong to the various card groups that are used in Table 10.
HYBRID Connections Supported by CWM 11
The following Hybrid platform combinations are supported (The Local and Remote endpoint of the connection must be within the same network):
•
•
An intersection of all connection types supported in PVC Table 8 and SPVC Table 10 are supported. The following rules/restrictions apply:
•
•
XPVC Connections Supported by CWM 11
The following XPVC platform combinations are supported (The Local and Remote Endpoint of the connection must be in different networks separated by at least one XLMI link):
•
•
PNNI ---> Auto Route
•
Auto Route Feeder on PNNI --> Auto Route
The Auto Route endpoints can be on a Routing or a Feeder node. An intersection of the connection types supported in PVC Table 8 and SPVC Table 10 are supported. The following additional rules/restrictions apply:
•
•
•
Limitations
CWM can manage up to 40 different disjoint AutoRoute networks, provided all the network elements have unique network IP addresses and unique names across all the networks managed by CWM. There is no such limitation for PXM45 based MGX networks.
Pointing multiple CWM workstations at the same gateway node is not recommended.
CWM must be started from a CDE environment.
CWM does not support use of the korn shell.
If you use CWM 11.0.10 on a low-end machine to manage mid-range or large-range networks, CWM may take a long time to synchronize with networks that have more than 100K connections. Connection Management and Equipment Management (using CiscoView) may take long time to come up or perform any user-requested functions. You might not be able to invoke multiple desktops from CWM as certified by Cisco for low-end systems with networks that have more than 100K connections.
If you use CWM 11.0.10 on a low-end machine to manage mid-range or large-range networks, CWM may not be able to receive traps generated by the network which might put the CWM database out of sync with the network. The result would be that the information about nodes, trunks, ports, and PVCs may not match with the status on the network.
Connection Manager Notes
The normal behavior of the CWM Connection Manager is that it automatically updates with all events received, however, if there are too many new events (if the event buffer fills up) the refresh button turns yellow. The yellow refresh button indicates that you should refresh the screen. Upon clicking the refresh button, it will pull information directly from the database.
When the connection modify dialog box is already open, another user can delete the connection using the CMGUI delete option.
The Connection Manager GUI for preferred route displays all available trunks without considering the traffic class. As a result, it is possible to set a preferred route for a CBR connection traversing trunks that do not support CBR traffic. Even if you set this preferred route through CWM it will be rejected by the switch.
While adding connections originating and terminating on the same feeder nodes (MGX8220 only), CWM will treat these connections as three segment connections and will add three segments (two on the same feeder node, one on the routing node) to realize this connection.
RPM on PXM1-based MGX8850/8230/88250 provisioning is done using telnet operation since it does not support SNMP SETs. Please refer to previous release notes for RPM switch CLI notes.
Issue with CWM 11 Security Manager
Too many concurrent Security Manager GUIs (>15) may have some problems in CWM. In case this problem appears, warm start the core.
HP OpenView
All event messages are displayed in the HPOV Event Browser window. There is a limit of 2000 pending messages on the Event Browser. If there are more than 2000 messages to be processed and displayed by the Event Browser, it may exit.
The default color of the background map can make it difficult to see the color of the nodes and the trunks on the map.
The WAN network icon in the network node manager is no longer automatically created when running CWM 11. Use the Network Topology map instead.
Issues with the CWM 11 Statistics Collection Manager
In order to collect connection statistics, statistics should be enabled on individual connections. If the user only enables connections stats on SCM but does set the stats enabled flag to true on the connection, the stats will not be collected, for that connection. Since there is no mechanism or warning to the user to have this enabled on the connections, CWM will not give appropriate error message.
Occasionally, when high connection counts are enabled on the SES, and statistics collection is enabled, the SES node is not getting synced up. The workaround is to disable statistics collection in the SES. Refer to CSCdw32076 for more information.
The statistics collection manager retrieves SPVC connection statistics data from BPX-SES nodes, however, only 15 minute collection buckets are supported on the SES.
The same limitation of only 15 minute collection buckets applies for MGX 8850 PXM45-based nodes with AXSM. There is no such limitation for AXSM-E.
When enabling statistics by selecting multiple nodes at a time in the SCM, enabling statistics on all the nodes will work only if all the nodes have the same card types or cards of the same family.
In the PXM45 and PXM1E based MGX 8850 switches Summary Reports are only supported on the AXSM card.
Limited Number of Routers
Each router AESA that is learned must be maintained in a database and sent to the standby PXM. Each AESA is twenty (20) bytes of information. This limits the number of AESA addresses to ten (10). If this is not a viable number it can be increased or decreased.
IP connectivity for BPX-SES is the same as in MGX 8220, MGX 8230 Release 1, MGX 8250
Release 1, and MGX 8850 Release 1.Ad-Hoc Reports/Summary Reports
Wingz occasionally is slow in scrolling. This is due to the amount of process required for the ad-hoc request. There is no loss in data or incorrect data.
These reports can no longer be launched from the Network Topology application.
To launch summary reports, complete the following procedure:
Step 1
Step 2
WANDEST Limitations
When a coldstart is done on a CWM machine with the WANDEST server installed and there is dbaccess session on user_connection table before sync-up is done, the databroker may not be able to create the trigger to the table. This will result in the WANDEST incremental upload process not being able to retrieve the update data from the user_connection table.
In this scenario, the following message will appear on the Console during sync-up:
242:Could not open database table (svplus.user_connection)106:ISAM error :non-exclusive accessError in line 1Near character position 1There is no workaround to this problem. If the triggers could not be planted at the time of coldstart, then they will not be planted during/after CWM sync up. The only solution is for the user to do a coldstatrt again.
It is recommended that the user not do any manual database queries on the user_connection table during CWM sync up.
Limitations for CWM-to-CWM Communication
The Secondary CWMs have to wait for the Primary CWM to finish syncing up with the network. Trap 28075 (svDatabaseInSync) is sent when the Primary CWM has finished syncing up with the network.
All the CWM workstations managing the same network must have seed nodes or gateway nodes that have IP addresses within the same network. All the CWM workstations should not all point to the same gateway node, but the gateway nodes they point to should be on the same network.
The Configurator can only be run on the Primary CWM.
Topology Limitations
It may occasionally take two to three minutes to display new nodes after the addition of virtual trunks. This is due to the time required to setup link0 and link1 subscriptions.
Newly added MGX2 nodes may not be discovered on a CWM which is already running. The node may not be discovered because the IP address of the node may be unreachable when the node was added to the network. The workaround for this is to perform a dnpnport and uppnport on the newly added trunk in the network.
In the case of a MGX2 network, the MGX2s are managed using the primary IP address. The primary IP address is specified using Option 8 in the cnfndparms CLI. Configure the trap IP with the primary IP. MGX1s connected to MGX2s are managed through the atm0 IP. If the atm0 is not set, then the LAN IP is used to manage the MGX1s. Configure the trap IP accordingly.
In the /usr/users/svplus/config/CwmGs.conf file there is a flag named TOPO_SHOW_MAP. You can use this file to set up the flag to configure whether or not background maps are displayed at CWM startup.
TOPO_SHOW_MAP 1 means when NWTopology opened, users can see topology maps.
TOPO_SHOW_MAP 0 means when NWTopology opened, users cannot see topology maps.
SNMP Traps
All SNMP traps now match with the MIB. In earlier releases, some of the trap enterprise Object Information Descriptors (OID) had different enterprise OIDs. Due to this correction, old traps with incorrect enterprise OIDs from trapd.log file will not be shown in the Event Browser.
The /etc/opt/OV/share/conf/C/trapd.conf file will be removed and replaced by the default trapd.conf file and will then be merged with the StrataCom_trapd.conf file. If you have modified the trapd.conf file, those changes will be lost. To save these changes, save the trapd.conf file (perhaps to /tmp), and merge it back.
The removal and replacement of a controller card in the BPX may result in traps being dropped during sync-up. The following seven steps generate the problem.
Step 1
Step 2
Step 3
Step 4
Step 5
Step 6
Step 7
If you perform an operation on ports/lines/[any entity] between steps 5 and 6, then the BPX will not send robust messages about those operations to CWM.
If you perform an operation between steps 6 & 7, then the BPX sends messages to CWM.The time difference between steps 5 & 6 might be in few seconds.
If you do any operation during that short interval between steps 5 & 6 CWM will not receive any generated traps about those operations.
CWM 11 Notes and Cautions
Due to the nature of asynchronous behavior of ILOG client and server interaction, CWM client requests may be sent before the CWM server is ready. In this case, the following error messages will be displayed on the workstation screen:
Ilb Error: Synchronous request to <unidentified actor failed by timeout>.
Note
Parameters displayed by the Network Browser that are not applicable to an element i.e: a line or a trunk often contain the value -1. Treat this as the same as Not Applicable.
CWM Upgrade
Note
The most current upgrade and installation information is found in the CWM Installation Guide for Solaris 7, Release 11 (78-12948-01). The following sections describe installation and upgrade procedures specific to CWM 11.0.10.
CWM 11.0.10 Server Installation or Upgrade to CWM 11.0.10 from CWM 10.5 and Earlier
To install or upgrade the CWM Server workstation to CWM 11, follow the upgrade and/or installation information as found in the CWM Installation Guide for Solaris 7, Release 11 (78-12948-01). A PDF copy of this document is on the second CWM 11 Server/Client CD.
Issue with Upgrading or Installing CWM 11.0.10 on Systems That Use or Will Be Using Meta Devices or Multiple Disks for Informix
There is an issue with database access with Solaris 7 CWM 11.0.10 systems using Meta Devices or Multiple Disks for Informix. All of the databases are being put into the first (rootdbs) partition.There are two issues with this:
•
•
This issue affects you if you are installing CWM for the first time on a Sun workstation or are upgrading your operating system and installing CWM for the first time. The installation of Informix for the first time changes the Solaris kernel parameters and requires a reboot.
Note
Fixing the Issue before Rebooting
If you will be setting up multiple partitions (answering "Yes" to the "Do you want multiple Disk configuration for informix database?" prompt) or setting up meta devices (answering "Yes" to the "Do you use disk striping (meta devices) for database partitions?") during your installation of CWM, BEFORE rebooting the workstation (the last step of the installation),
At the end of the install when you are prompted with the following, "Kernel has been modified. The system must be rebooted to complete the installation. Reboot System now? ", choose "No". DO NOT REBOOT THE WORKSTATION.
Note
The workaround to fix this problem is to remove the phrase
| tee -a /usr/users/svplus/install/upgrade/S97.log 2>&1 from several lines in the /etc/rc3.d/S97firsttime file.To accomplish this, you MUST do one of the following procedures:
•
•
Refer to the following two sections for instructions.
Downloading the 11_0_10_S97firsttime.tar File From CCO
A tar file containing an edited version of the /etc/rc3.d/S97firsttime file is available on CCO. Complete the following steps to download and untar this file.
Step 1
Step 2
# suStep 3
# tar xvf <path-of-download-dir>/11_0_10_S97firsttime.tarThe edited /etc/rc3.d/S97firsttime file will be installed in the appropriate location.
Step 4
Step 5
Editing the Existing /etc/rc3.d/S97firsttime File Manually
If you didn't download the 11_0_10_S97firsttime.tar file from CCO, you will need to complete the following steps to edit the existing /etc/rc3.d/S97firsttime file to remove the phrase
| tee -a /usr/users/svplus/install/upgrade/S97.log 2>&1 from the six lines where it appears.
Step 1
# suStep 2
# vi /etc/rc3.d/S97firsttimeStep 3
/usr/users/svplus/tmp/chmodFile | tee -a /usr/users/svplus/install/upgrade/S97.log 2>&1
to this:
/usr/users/svplus/tmp/chmodFileStep 4
/usr/users/svplus/tmp/dbmode | tee -a /usr/users/svplus/install/upgrade/S97.log 2>&1
to this:
/usr/users/svplus/tmp/dbmodeStep 5
/usr/users/svplus/tmp/dbfirstinit | tee -a /usr/users/svplus/install/upgrade/S97.log 2>&1
to this:
/usr/users/svplus/tmp/dbfirstinit
Step 6
/usr/users/svplus/tmp/dbonmode | tee -a /usr/users/svplus/install/upgrade/S97.log 2>&1
to this:
/usr/users/svplus/tmp/dbonmode
Step 7
/usr/users/svplus/tmp/dbonspace | tee -a /usr/users/svplus/install/upgrade/S97.log 2>&1
to this:
/usr/users/svplus/tmp/dbonspace
Step 8
rm /etc/rc3.d/S97firsttime | tee -a /usr/users/svplus/install/upgrade/S97.log 2>&1
to this:
rm /etc/rc3.d/S97firsttime
Step 9
:wq!Step 10
The newly edited /etc/rc3.d/S97firsttime file should look like this:
#!/bin/sh/usr/users/svplus/tmp/chmodFile/usr/users/svplus/tmp/dbmode/usr/users/svplus/tmp/dbfirstinitsleep 5/usr/users/svplus/tmp/dbonmode/usr/users/svplus/tmp/dbonspacesleep 3/bin/rm /etc/rc3.d/S97firsttimeStep 11
# /bin/chmod 744 /etc/rc3.d/S97firsttimeStep 12
Step 13
Remedy if You Have Already Rebooted the Workstation
If you've already rebooted your workstation after installing or upgrading to CWM, and you need to support disk partitioning or meta devices on your workstation, after your workstation comes back up, wait for at least 10 minutes before going on.
There are two methods to fix this issue. The first method requires a reboot, and is described in the next section.
Replace or Edit the S97firsttime File (Requires Reboot)
If you've already rebooted your workstation after installing or upgrading to CWM, and you don't have an issue with rebooting your workstation, complete one of the following procedures:
•
•
Refer to the following two sections for instructions.
Downloading 11_0_10_S97firsttime.tar File From CCO
A tar file containing an edited version of the /etc/rc3.d/S97firsttime file is available on CCO. Complete the following steps to download and untar this file.
Step 1
Step 2
# suStep 3
# tar xvf <path-of-download-dir>/11_0_10_S97firsttime.tarThe edited /etc/rc3.d/S97firsttime file will be installed in the appropriate location.
Step 4
Step 5
Editing Existing /etc/rc3.d/S97firsttime File Manually
If you didn't download the 11_0_10_S97firsttime.tar file from CCO, you will need to complete the following steps to edit the existing /etc/rc3.d/S97firsttime file to remove the phrase
| tee -a /usr/users/svplus/install/upgrade/S97.log 2>&1 from the six lines where it appears.
Step 1
# suStep 2
# vi /etc/rc3.d/S97firsttimeStep 3
/usr/users/svplus/tmp/chmodFile | tee -a /usr/users/svplus/install/upgrade/S97.log 2>&1
to this:
/usr/users/svplus/tmp/chmodFileStep 4
/usr/users/svplus/tmp/dbmode | tee -a /usr/users/svplus/install/upgrade/S97.log 2>&1
to this:
/usr/users/svplus/tmp/dbmodeStep 5
/usr/users/svplus/tmp/dbfirstinit | tee -a /usr/users/svplus/install/upgrade/S97.log 2>&1
to this:
/usr/users/svplus/tmp/dbfirstinit
Step 6
/usr/users/svplus/tmp/dbonmode | tee -a /usr/users/svplus/install/upgrade/S97.log 2>&1
to this:
/usr/users/svplus/tmp/dbonmode
Step 7
/usr/users/svplus/tmp/dbonspace | tee -a /usr/users/svplus/install/upgrade/S97.log 2>&1
to this:
/usr/users/svplus/tmp/dbonspace
Step 8
rm /etc/rc3.d/S97firsttime | tee -a /usr/users/svplus/install/upgrade/S97.log 2>&1
to this:
rm /etc/rc3.d/S97firsttime
Step 9
:wq!Step 10
The newly edited /etc/rc3.d/S97firsttime file should look like this:
#!/bin/sh/usr/users/svplus/tmp/chmodFile/usr/users/svplus/tmp/dbmode/usr/users/svplus/tmp/dbfirstinitsleep 5/usr/users/svplus/tmp/dbonmode/usr/users/svplus/tmp/dbonspacesleep 3/bin/rm /etc/rc3.d/S97firsttimeStep 11
# /bin/chmod 744 /etc/rc3.d/S97firsttimeStep 12
Step 13
Cleaning Up TEE Process (Does not Require Reboot)
If you rebooted after installing or upgrading to CWM, and you want to fix the issue without rebooting your workstation, complete the following steps:
Step 1
# suStep 2
# /usr/bin/ps -aef | grep "tee -a /usr/users/svplus/install/upgrade/S97.log" | grep -v grepThe following is an example of what displays:
root 295 258 0 19:37:14 ? 0:00 tee -a /usr/users/svplus/install/ upgrade/S97.logThe process corresponding to pid 295 is "tee -a /usr/users/svplus/install/upgrade/S97.log"
Step 3
# kill -9 295Step 4
Step 5
# /usr/bin/ps -aef | grep S97firsttimeThere is no need to reboot after this step.
Step 6
Remedy if You Have Already Rebooted Workstation and Entered CWM as svplus
If you rebooted after installing or upgrading to CWM, logged in as user svplus, and typed CWM to get to the opening menu, DO NOT START THE CORE. Type "X" to exit the opening menu and complete the following steps:
Step 1
# suStep 2
# /bin/mv /usr/users/svplus/install/upgrade/createDB /usr/users/svplus/tmpThe only method to fix this issue requires a reboot, and is described in the next section.
Replace or Edit S97firsttime File (Requires Reboot)
If you've already rebooted your workstation after installing or upgrading to CWM, and you don't have an issue with rebooting your workstation, complete one of the following procedures:
•
•
Refer to the following two sections for instructions.
Downloading 11_0_10_S97firsttime.tar File from CCO
A tar file containing an edited version of the /etc/rc3.d/S97firsttime file is available on CCO. Complete the following steps to download and untar this file.
Step 1
Step 2
# suStep 3
# tar xvf <path-of-download-dir>/11_0_10_S97firsttime.tarThe edited /etc/rc3.d/S97firsttime file will be installed in the appropriate location.
Step 4
Step 5
Editing Existing /etc/rc3.d/S97firsttime FIle Manually
If you didn't download the 11_0_10_S97firsttime.tar file from CCO, you will need to complete the following steps to edit the existing /etc/rc3.d/S97firsttime file to remove the phrase
| tee -a /usr/users/svplus/install/upgrade/S97.log from the six lines where it appears.
Step 1
# suStep 2
# vi /etc/rc3.d/S97firsttimeStep 3
/usr/users/svplus/tmp/chmodFile | tee -a /usr/users/svplus/install/upgrade/S97.log
to this:
/usr/users/svplus/tmp/chmodFileStep 4
/usr/users/svplus/tmp/dbmode | tee -a /usr/users/svplus/install/upgrade/S97.log
to this:
/usr/users/svplus/tmp/dbmodeStep 5
/usr/users/svplus/tmp/dbfirstinit | tee -a /usr/users/svplus/install/upgrade/S97.log
to this:
/usr/users/svplus/tmp/dbfirstinit
Step 6
/usr/users/svplus/tmp/dbonmode | tee -a /usr/users/svplus/install/upgrade/S97.log
to this:
/usr/users/svplus/tmp/dbonmode
Step 7
/usr/users/svplus/tmp/dbonspace | tee -a /usr/users/svplus/install/upgrade/S97.log
to this:
/usr/users/svplus/tmp/dbonspace
Step 8
rm /etc/rc3.d/S97firsttime | tee -a /usr/users/svplus/install/upgrade/S97.log
to this:
rm /etc/rc3.d/S97firsttime
Step 9
:wq!Step 10
The newly edited /etc/rc3.d/S97firsttime file should look like this:
#!/bin/sh/usr/users/svplus/tmp/chmodFile/usr/users/svplus/tmp/dbmode/usr/users/svplus/tmp/dbfirstinitsleep 5/usr/users/svplus/tmp/dbonmode/usr/users/svplus/tmp/dbonspacesleep 3/bin/rm /etc/rc3.d/S97firsttimeStep 11
# /bin/chmod 744 /etc/rc3.d/S97firsttimeStep 12
Step 13
Remedy if You Have Already Rebooted the Workstation and Started the Core Processes
If you rebooted after installing or upgrading to CWM and started the core, CWM will be functioning normally but the Informix multiple raw partition is not used to its fullest extent. If you would like to use multiple raw partitions with the CWM database residing in its own dbspace (datadbs) instead of rootdbs, you will need to complete the following procedure:
Note
Step 1
hostname# su -u svplusThe system prompts you for the svplus password:
password:After you enter the svplus password, the svplus (non-root) prompt displays:
%If the CWM core is running, proceed with Step 2. If the core is already stopped, go to Step 5.
Step 2
Step 3
Step 4
Step 5
% dbexport stratacom -o <path to dbbackup directory>% dbexport statsdb -o <path to dbbackup directory>% dbexport scmdb -o <path to dbbackup directory>Step 6
Step 7
% suThe system prompts you for the root password:
password:After you enter the password, the root prompt displays:
#Step 8
# cshAfter you change to the csh, the csh prompt displays:
hostname#Step 9
hostname# chown -R informix <path-to-datadbs> <path-to-logdbs>hostname# chgrp -R informix <path-to-datadbs> <path-to-logdbs>Step 10
hostname# source /usr/users/svplus/.cshrchostname# onmode -kyhostname# pkill -9 oninitStep 11
hostname# ps -aef | grep oninitStep 12
hostname# oninit -iyStep 13
hostname# onmode -mStep 14
hostname# /usr/users/informix92/bin/onspaces -c -d datadbs -p <path-to-datadbs> -o 0 -s <size-in-bytes>hostname# /usr/users/informix92/bin/onspaces -c -d logdbs -p <path-to-logdbs> -o 0 -s <size-in-bytes>Step 15
hostname# /usr/users/informix92/bin/onmode -uyStep 16
hostname# /usr/users/informix92/bin/onparams -a -d logdbs > /dev/nullStep 17
hostname# /usr/users/informix92/bin/onmode -mStep 18
hostname# su -u svplusThe system prompts you for the svplus password:
password:After you enter the svplus password, the svplus (non-root) prompt displays:
%Step 19
% dbimport stratacom -d datadbs -i <path to dbbackup directory>% dbimport statsdb -d datadbs -i <path to dbbackup directory>% dbimport scmdb -d datadbs -i <path to dbbackup directory>Step 20
% coldstartCWMNow you can start the core.
Issue with .rhosts File During Upgrade
The .rhosts file is overwritten during the upgrade process.
The installation script that comes with release 11.0.10 CWM has a .rhosts file that replaces the one on the server being upgraded. This .rhosts file only has the (+) sign in it.
Save a copy of the file before the start of the upgrade and reload it right after the upgrade is done.
Saving User-created Statistics Collection Manager Templates Before Upgrading
If you have created your own SCM (statistics) templates and if those user created templates are used as the default template for that platform, your user-created templates need to be set to non-default (the "use as default" field needs to be set to "No") in the SCM GUI BEFORE you upgrade to 11.0.10. The node templates are saved in /usr/users/svplus/SAVE/scmtemplate.
Note
Complete the following steps before upgrading to 11.0.10:
Step 1
Step 2
Step 3
Note
BPX, IGX, PXM1-based MGX Feeders
The following platforms are not supported during upgrade from 10.4.10 Patch 3 and/or 10.5.10 Patch 2 or Patch 3:
PXM1E-based MGX 8830 and MGX 8850 switches
PXM45-based MGX 8850 switches
PXM45-based MGX 8950 switches.
Note
CWM 11.0.10 Patch 3 Installation
Solaris 7
Contents of this patch include the following:
•
–
–
•
–
–
•
–
–
•
–
–
•
–
–
•
–
–
–
•
–
CWM Server Patch and Informix 9.21 UC7XH Installation
To install CWM Server Patch and Informix 9.21 UC7XH, perform the following steps:
Step 1
Step 2
% cp -p network.conf network.conf.saveStep 3
For example, /tmp
Step 4
Step 5
# gunzip 11.0.10.SOL27.Patch3P3.tar.gz# gunzip informix921uc7xh.tar.gzStep 6
# ./InstallInformixPatchuc7xh.csh informix921uc7xh.tar# ./InstallCWM11Patch3.csh 11.0.10.SOL27.Patch3P3.tarStep 7
a.
b.
suc.
cd /tmptar xvfp cmf2.1-sol-CSCeb834941.tard.
cd /tmp/CSCeb83494-1e.
/opt/CSCOpx/bin/perl/CSCeb83494-1.plf.
Step 8
a.
b.
c.
# gunzip wandest2.3.SOL27.server.3P3.tar.gzd.
# ./InstallWD23Patch3.csh wandest2.3.SOL27.server.3P3.tarStep 9
Step 10
Step 11
% cd /usr/users/svplus/configStep 12
CWM Client Patch Installation
To install the CWM Client Patch, perform the following steps:
Step 1
Step 2
Step 3
Step 4
# gunzip 11.0.10.SOL27.client.Patch3P3.tar.gzStep 5
# ./InstallClient11Patch3.csh 11.0.10.SOL27.client.Patch3P3.tarStep 6
CWM SNMP Agent (ServiceAgent) Patch Installation
To install the CWM SNMP Agent (ServiceAgent) Patch, perform the following steps:
Step 1
Step 2
Step 3
Step 4
# gunzip 11.0.10.SOL27.agent.Patch3P3.tar.gzStep 5
# ./InstallSNMPAgent11Patch3.csh 11.0.10.SOL27.agent.Patch3P3.tarStep 6
CWM SCMSA Patch Installation
To install the CWM SCMSA Patch, perform the following steps:
Step 1
Step 2
Step 3
Step 4
# gunzip 11.0.10.SOL27.scmsa.Patch3P3.tar.gzStep 5
# ./InstallSCMSA11Patch3.csh 11.0.10.SOL27.scmsa.Patch3P3.tarStep 6
WANDEST Server Patch 3 Installation
To install the WANDEST Server Patch, perform the following steps:
Note
Step 1
Step 2
Step 3
Step 4
# gunzip wandest2.3.SOL28.server.3P3.tar.gzStep 5
# ./InstallWD23Patch3.csh wandest2.3.SOL27.server.3P3.tarStep 6
Step 7
WANDEST Client Patch 3 Installation
To install the WANDEST Client Patch, perform the following steps:
Step 1
Step 2
Step 3
Step 4
# gunzip wandest2.3.SOL27.client.3P3.tar.gz
# tar xvfp wandest2.3.SOL27.client.3P3.tar
Step 5
/usr/users/wandest/wandest.ctrl (over into)/usr/users/wandest/client/ctrl (directory)
CMF Patch 2.1 Installation
To install the CMF Patch, perform the following steps:
Step 1
Step 2
Step 3
tar xvfp cmf2.1-sol-CSCeb834941.tarStep 4
cd <local directory>/CSCeb83494-1Step 5
/opt/CSCOpx/bin/perl CSCeb83494-1.plStep 6
Modify Files:
•
Backed-up File Details:
•
•
Steps Required if You Want to Roll Back the Patch
Step 1
Step 2
Step 3
Step 4
/etc/init.d/dmgtd start
CWM 11.0.10 non-Java-based Client Installation
Note
This section provides step-by-step procedures to install the CWM Release 11.0.10 non-Java-based client software on a client workstation.
Table 12 describes the configuration for the minimum type of machine supported for CWM Release 11.0.10 as a standard non-Java-based client workstation platform.
Note
Installing Solaris 7
Before installing the CWM Release 11.0.10 non-Java-based client software on the CWM workstation, the following software should already be installed:
•
•
Install Solaris 7 according to the automated procedure. The Solaris installation program is a menu-driven, interactive step-by-step guide to installing the Solaris operating environment. It also provides online help to answer your questions.
Installing Solaris 7 Patches
Solaris patches 106950-18, 106980-18, 110881-01, 111980-01, and 106541-21 must be installed before CWM 11 can be launched.
Solaris patches 106327-12, 107081-11, 107636-03, 112300-01, and 108376-03 must be installed before CiscoView can be launched.
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=homeIf the search facility on the SunSolve site is used, search for the search ID number and do not include the two-digit patch version number.
Note
Step 1
Step 2
for example 7 (48.9M)Step 3
Step 4
Step 5
Configuring the Workstation Display
After installing the Sun Solaris 7 operating system, perform the following steps:
Step 1
Step 2
Step 3
Move this terminal window to the upper right corner of the screen.
Step 4
Lower the height to display four lines and move this window so that it rests above the CDE menu bar. This window provides a display of workstation system messages.
Step 5
The Style Manager window is displayed.
Step 6
If you prefer to use the screen saver, highlight choice(s) and start the screen saver at 29 minutes. Start the screen lock at 30 minutes, click OK.
Step 7
Do the same to all four screens, labeled One, Two, Three and Four in the CDE icon bar. In Four click OK and return to screen One. This helps to conserve workstation resources.
Step 8
The next login session will come up using this same screen configuration. Click OK and close the Style Manager.
Step 9
Installing InstallShield non-Java based CWM Client Software
This section describes how to install the non-java based CWM client software provided on the second CWM distribution CD. It is no longer necessary to install the CWM client software from this distribution CD. The new Java CWM 11.0.10 client software can be deployed directly from the CWM server. Refer to the CWM Installation Guide for Solaris 7, Release 11 (78-13567-01) for more details.
The CWM Release 11.0.10 non-java based client software installation uses InstallShield. To install the CWM Release 11.0.10 client software, complete the following steps:
Step 1
Step 2
host% cd /cdrom/cdrom0host% lsStep 3
host% ./InstallClient.shThe CWM Client Package Installation Welcome screen is displayed, as shown in Figure 1.
Figure 1 CWM Client Welcome Screen
Step 4
The Choose Destination Directory screen, Figure 2, is displayed.
Figure 2 Choose CWM Client Destination Directory Screen
The displayed default for the application-based client is /usr/users/svplus.
Use the Browse... button to go to your home directory, and type in the name of a directory under your home directory into which to install the client files.
If the primary Destination directory you provide doesn't currently exist, the Destination Directory Confirmation Screen displays, as shown in Figure 3.
Figure 3 Destination Directory Confirmation Screen
If the directory is correct, click on the Yes button.
The software installation process begins. This process will take about 5 to 10 minutes depending on the speed and resources of the CWM workstation. The installation screen shows a dynamic indicator bar, which moves across the screen, indicating the progress of the installation process, as shown in Figure 4.
Figure 4 CWM Client Installation Progress Indicator
When completed, a final window displays indicating that the installation has completed. This window is shown in Figure 5.
Figure 5 CWM Client Installation Complete Screen
Step 5
Doing so ends the software installation process, and the Install Shield screen closes.
The system needs to be rebooted at this point.
Rebooting the Workstation
At the root prompt, enter the following command to reboot the workstation.
# sync ;sync ;rebootThe reboot sequence aligns the cylinders of your hard disks and gracefully shuts down the Solaris operating system.
The OK prompt is displayed.
At this point, you can push the CDROM eject button on the CDROM drive to eject the installation disk.
Installing Netscape Communicator
The Sun Microsystems Netscape Communicator for Solaris package (version 4.76) is included on the Cisco-provided CWM CD-ROM#2 under the filename of NSCPcom.sparc.tar.gz
Netscape Communicator must be installed before CiscoView 5.4.1 can be launched. Netscape Communicator requires that the basic Solaris software end-user cluster (SUNWCuser) be installed. After installation, Netscape Communicator requires 20Mbytes of free disk space.
Install Netscape Communicator using the following steps.
Step 1
Step 2
# cd /cdrom/cdrom0/110tools# ls
Note
Step 3
cp -p /cdrom/cdrom0/110tools/NSCPcom.sparc.tar.gz /tmpStep 4
cp -p /cdrom/cdrom0/110tools/gzip /tmpStep 5
cd /tmpStep 6
chmod 555 /tmp gzipStep 7
./gzip -d /tmp/NSCPcom.sparc.tar.gz
Note
Step 8
tar xvf -p /tmp/NSCPcom.sparc.tarStep 9
myhhost% suPassword:#Step 10
pkgadd -d /tmp NSCPcomThis command installs the Netscape Communicator package in the /opt/NSCPcom directory.
Step 11
setenv PATH /opt/NSCPcom:$ {PATH}
Preparing CWM 11.0.10 Server Workstation to Launch CiscoView from Client Topology Window
Running CiscoView 5.4.1 from Netscape Communicator requires that a Java 1.3.1 plug-in be installed.
The plug-in is included in CDROM #2 and should be installed using the following procedure.
Step 1
Step 2
# cd /cdrom/cdrom0/110tools# lsStep 3
cp -p /cdrom/cdrom0/110tools/j2re-1_3_1-solsparc.sh /usr/usersStep 4
cd /usr/usersStep 5
sh j2re-1_3_1-solsparc.shRunning the script creates a directory named j2re-1_3_1 that contains the plug-in modules. This directory is created beneath the directory that you selected in Step 3.
Step 6
Step 7
setenv NPX_PLUGIN_PATH /usr/users/j2re1_3_1/plugin/sparc/ns4Step 8
Note
Note
$HOME/.netscape/cert7.db ($HOME here is /usr/users/svplus)
$HOME/.netscape/key3.db ($HOME here is /usr/users/svplus)
Preparing CWM 11.0.10 Client Workstation to Launch CiscoView from Client Topology Window
Before launching CiscoView from the client, perform the following steps:
Step 1
a.
setenv PATH "netscape path":${PATH}setenv NPX_PLUGIN_PATH /usr/users/j2re1_3_1_03/plugin/sparc/ns4
Note
b.
setenv PATH "netscape path":${PATH}
Note
c.
setenv NPX_PLUGIN_PATH /usr/users/j2re1_3_1/plugin/sparc/ns4
Note
The last three lines of the ./CWM script should look like this:
setenv PATH /opt/NSCPcom:/${PATH}setenv NPX_PLUGIN_PATH /usr/users/j2re1_3_1/plugin/sparc/ns4runDesktop $DISPLAY
Note
Important Configuration Notes
This section provides important configuration information.
Orbix Registration
As noted in the CWM Installation Guide, use the ping command to confirm that the hostname.domainname you provide for Orbix registration is reachable before completing the installation. Refer to CSCdx87212 for more information about workarounds in the event that the hostname.domainname become unreachable.
Setting Up CWM-to-HP OpenView Communication
All of the libraries in HP OpenView are shared libraries. In order to get CWM and HP OpenView communicating properly you need to configure the LD_LIBRARY_PATH by entering the following command as root:
# setenv LD_LIBRARY_PATH ${LD_LIBRARY_PATH}:/opt/OV/libNaming Managed Nodes
Each node name of all the nodes managed by CWM must be unique.
Enabling Connection Descriptor
The connection descriptor field will not permit you to enter data until you turn the feature on by setting a flag in the /usr/users/svplus/config/CwmDomainGlobal.conf file
DESCRIPTOR_FLAG = 0
0 means off
1 means on
The connection descriptor string can contain any alphanumeric character and can be up to 64 characters (including spaces) in length.
This flag is disabled by default.
CWM Configuration
The default CWM configuration supports most networks. Very large networks with a significant number of PVCs (100,000 or more) require a change to the default CWM configuration for better performance during cold or warm starts of CWM. Please contact CWM Support group for help in this matter.
CWM Dedicated IP Ports
CWM 11 to Cisco WAN switch (outgoing): ports used in the switch
•
•
•
•
•
Cisco WAN switch to CWM 11 (incoming): ports used in CWM 11
•
•
•
Operations Support System (OSS) to CWM 11 (incoming): ports used in CWM 11
•
Table 13 lists the CWM 11 ports used by ORBIX:
Unique Node ID
The Node ID is now stored in the node_info table as opposed to the node table in CWM 9.2. The Node ID is assigned by CWM. To have the same Node ID across the domain, the user must enable the CWM to CWM communication to ensure that the node_info table is in sync across all the CWM systems within a domain.
Do not use the SV+CreateDb command to drop the node_info table. It can only be dropped by using the coldstart command with the "-F" option.
The ftp_user_passwd field in the node_info table across CWM-CWM in the same domain will not be the same because of encrypted password.
Security Profiles
The security profile and user profile are stored in the database as user_info and sec_profile tables. All CWM systems in the same domain will have the same data in the user_info and sec_profile table by ways of CWM to CWM communication.
The user_info and sec_profile tables will not get dropped when the coldstart command is executed during a cold start. These tables can only be dropped by executing the coldstart command with the "-F" option.
If you are upgrading to CWM 11 from CWM 10.4.10, then the old security profile will automatically be converted and loaded into the database during upgrade. If you are upgrading from 10.5.10, no conversion is necessary.
The Security Manager GUI can be started from NWTopology main window in the primary CWM system.
The CWM user to be added to the database has to be a valid UNIX user, when a user logs in to CWM desktop, user authentication against UNIX gets performed. The CWM user's password needs to match what's defined in the UNIX system.
CWM Database
After performing the creation of a new database by executing the coldstart script, if CWM is restarted (stop core and start core) before it is synchronized with the network, it will result in a database inconsistency. In this case, rerun the coldstart script to avoid database inconsistencies.
Note
When a Gateway node is upgraded or rebuilt, before CWM has synchronized up with the network, CWM must be cold-started (create CWM database and restart CWM). This is required to ensure CWM database consistency.
The user supplied network name can be up to 10 characters in length and should be alphanumeric characters only (no periods).
Topology Discovery Configuration for AutoRoute Networks
You must enter a configuration for each AutoRoute network to be discovered by CWM in /usr/users/svplus/config/network.conf file. Following is a sample configuration for an AutoRoute network with gateway nmsbpx02:
# Sample Network 1 : Discover an AUTO ROUTE Network# Note : Use only one Gateway per network in case of AUTOROUTE networksNETWORK:Network1GATEWAYS:nmsbpx02DISCOVERY PROTOCOL:AUTOROUTEIP REACHABILITY FLAG:NWIP_ONOPTIONAL:"TIMEOUT = 7, RETRANSMIT = 6, THROTTLE = 0, ACKNOWLEDGE = 30, BLOCKSIZE = 1024"Examine the /etc/hosts file and check that the file contains a nodename and IP address for all gateway nodes. The IP address should match the gateway node's (the one that CWM can use for AutoRoute network discovery). Enter the correct nodenames and addresses for any missing gateway nodes.
To view the /etc/hosts file, enter the following command:
host% more /etc/hostsUse the vi editor to enter items into the file.
For each node:
Enter the BPX gateway node's IP address and the node name.
Example:
192.0.0.8 nmsbpx02
Note
Topology Discovery Configuration for PNNI Networks
You must enter configuration for each PNNI network to be discovered by CWM in /usr/users/svplus/config/network.conf file. A sample configuration for a PNNI network with gateway nmspnni4 follows:
# Network 9 : Discover a PNNI networkNETWORK:Network9GATEWAYS:nmspnni4DISCOVERY PROTOCOL:PNNIYou also need to specify any PNNI nodes through the Network Configurator GUI tool if:
•
•
Note
Topology Discovery Configuration for Hybrid Networks
You must enter configuration for each Hybrid (AutoRoute and PNNI) network to be discovered by CWM in /usr/users/svplus/config/network.conf file.
To configure CWM for Hybrid (AutoRoute and PNNI) networks, the file has the following format.
NETWORK:Network1 (a name for CWM to identify the network)AR-GATEWAYS:sj123456 (the name or IP address of the gateway to the Autoroute section of the network)PNNI-GATEWAYS:sj123456 (the name or IP address of the gateway to the PNNI section of the network)DISCOVERY PROTOCOL:HYBRID (the discovery protocol, in this case always HYBRID)IP REACHABILITY FLAG:NWIP_OFF (specifies in-band or out-of-band management)OPTIONAL:"TIMEOUT = 7, RETRANSMIT = 6, THROTTLE = 0, ACKNOWLEDGE = 30, BLOCKSIZE = 1024" (the optional field is used to specify parameters if the desired value is different from the default value,With a hybrid network, the XPVC Preferred Table Configurator GUI in Topology GUI can no longer decide which are the closest set of XLMI links for the selected node. You must use the topology map in conjunction with the XPVC Preferred Table Configurator GUI to choose the correct closest link to the selected BPX.
Caution
Examine the /etc/hosts file and check that the file contains a nodename and IP address for all gateway nodes. The IP address should match the gateway node's (the one that CWM can use for AutoRoute network discovery). Enter the correct nodenames and addresses for any missing gateway nodes.
To view the /etc/hosts file, enter the following command:
host% more /etc/hostsUse the vi editor to enter items into the file.
For each node:
Enter the BPX gateway node's IP address and the node name.
Example:
192.0.0.5 sj123456
Note
Topology Discovery Configuration for Stand-Alone Nodes
You can configure PXM1-based MGX nodes or PXM1E/PXM45-based MGX nodes as Stand-Alone nodes. Follow these steps:
Step 1
Step 2
Step 3
Step 4
Step 5
Step 6
Note
The following is an example of a dummy network:
NETWORK:Network1GATEWAYS:/dev/null/0DISCOVERY PROTOCOL:AUTOROUTEIP REACHABILITY FLAG:NWIP_ONOPTIONAL:"TIMEOUT = 7, RETRANSMIT = 6, THROTTLE = 0, ACKNOWLEDGE = 30,BLOCKSIZE = 1024"
Connection Manager Configuration
Configuration Parameters for Connection Manager Daemon (cmgrd)
•
•
The configuration parameters in this file are listed below:
•
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.
•
•
•
•
•
•
–
–
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.
•
If disabled, cmgrd will not set PercentUtil on any PNNI endpoint hence will be defaulted by the switch to 100%.
•
If disabled, cmgrd will not set ingressQDiscardOption parameter at all on the switch hence defaulted by switch always to `clpHysterisis'.
RPM Support
CWM 11 supports only the ATM connection type and vbr.3 and abr1 service types for endpoints terminated on the RPM card.
For an RPM VCCON, the only VPI value allowed is 0. To add an RPM VPCON, an asterisk (*) should be specified as the VCI value.
If a VPI, VCI value is used to establish an RPM channel on one subinterface, the SAME VPI, VCI pair cannot be used with another subinterface. This is due to an RPM limitation. If such action is attempted, CWM 11 will display an "Local/Remote end point already exists" error.
CWM 11 does not support provisioning of RPM channels for subinterface values over 32767.
For a PVC involving RPM, CWM 11 supports ATM Service Type VBR only (VBR.3 for ATM-ATM, ATM-FR for ATM to FR PVCs and ABR.1 for ATM-ATM PVCs). The UBR Service Type is not supported for RPM by CWM 11.
CWM 11 provisions the RPM end of an "End to End" PVC by using the Cisco IOS atm pvc command followed by the addcon command. An RPM end point added using the atm pvc command cannot be modified/deleted using the (newer) pvc command and vice-versa.
To establish a channel on RPM, two Cisco IOS commands are required:
•
•
If the RPM leg gets deleted (new configuration restored on RPM), CWM 11 cannot detect the condition. However, if necessary, CWM 11 can be used to delete and re-add the entire channel by reprovisioning the "End to End" PVC.
If the PXM leg gets deleted (for example, clrallcnf on MGX 8850), CWM 11 cannot provision the channel until the RPM leg is manually deleted. To do that, you must log in to the RPM card and perform the following Cisco IOS commands:
•
•
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
–
–
–
BXM/UXM
–
–
–
–
–
The value of peak (express here in cells/second) is limited as for each trunk type as:
–
–
–
–
–
While one CWM 11 station is used to provision connections on a specific RPM card, attempts to provision on the same card by another CWM 11 station can result in failure in the provisioning of RPM connections.
Provisioning of RPM can take up to 25 seconds on average. On rare occasions, the Connection Manager GUI may time out before IOSMGR returns. The returned Cisco IOS messages are eventually updated in the Result pane in the Connection Manager GUI.
The following are the typical causes of the error message "atm pvc missing"message:
•
•
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:
•
•
Note
Complete the following steps:
Step 1
Step 2
Note
For other error messages returned by IOSMGR, complete the following steps:
Step 1
Step 2
Step 3
The existing RPM connections will not be removed from the CWM database when the RPM card is pulled out of the MGX 8850 shelf.
Note
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:
•
•
•
•
•
Setting Up CiscoView to Manage RPM Cards from Workstation
RPM cards must have SNMP configured to enable CiscoView to view configuration parameters, performance statistics, and events.
Configuring SNMP and SYSLOG
Each RPM card to be managed must have SNMP and SYSLOG configured or the management software cannot communicate with the node containing the RPM card.
Table 14 shows SNMP and SYSLOG router configuration commands. In this example, the network management system has an IP address of 10.1.1.1.
Note
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
CWM SNMP Agent Configuration Notes
The CWM SNMP MasterAgent is configured to use UDP port 8161 as the default port for CWM SNMP communication. If the 8161 UDP port is used by other processes in the customer scenario, the user can configure the CWM MasterAgent to use a different UDP port by modifying the /usr/users/svplus/scripts/start_SV+ script as given below.
The following line needs to be edited to change the port:
SR_SNMP_TEST_PORT=8161
In the line mentioned above, replace 8161 by any other valid UDP port to match the user system requirements.
The snmpd.cnf configuration file for the MasterAgent is located in the /usr/users/svplus/config directory. This file can be viewed or modified only by root.
CWM SNMPV1 module uses community strings for authentication. The CWM SNMP module uses the community strings defined in the snmpd.cnf config file. By default, the snmpget community string is public, and the snmpset community string is configured as private.
The user can modify the community strings by modifying the third column in the following lines from snmpd.cnf config file:
Syntax:
snmpCommunityEntry t0000000 private private localSnmpID - - nonVolatilesnmpCommunityEntry t0000001 public public localSnmpID - - nonVolatileModifying the trap_filter.conf file allows the customer to remove the traps they are not interested in. In order to ensure that the trap_filter.conf is recognized correctly, when registering the SNMP Manager with the CWM SNMP Agent, the customer must explicitly set the bit-mask to a value that is NOT the default, but still specifies all the used groups today. Group 28 is unused. Set the bit-mask to FFFFFFFFEFFFFFFF instead of accepting the default.
SNMP Stack Parameters for CWM 11
MAX_THREADS
The value of this variable should be set to the maximum number of concurrent (plus 1 for the maintenance thread) SNMP requests the user would expect in their environment at any given time. For example, if the user expects a maximum of not more than 10 requests at any given time, the value of this parameter should be set as 11. The value of this variable gives the maximum number of requests the CWM SNMP stack will queue and process at any given instance. By default, the CWMSNMP Agent module is configured to handle a maximum of 25 concurrent SNMP requests at a given time.
MAX_PDU_TIME
This value of this variable should be set to, (MAX_THREADS * 60 seconds) * 100. The assumption here is that the maximum turnaround time for a provisioning request (for example, an RPM MGX 8850 Release 1 node connection provisioning) might take around 60 seconds. A multiplication factor of 100 is applied since this value is given in centiseconds(1/100th of a second). For example, if the MAX_THREADS value is 5, this value would be 30000 centiseconds, i.e., 300 seconds or 5 minutes. But since all the provisioning requests will not take 60 seconds, the default value of 30000 centiseconds or 300 seconds should suffice most of the customer scenario.
MAX_OUTPUT_WAITING
This should be set to (MAX_THREADS * 4096). This is the amount of space the stack requires to buffer/queue the incoming requests and outgoing responses. OSS/Client/Manager Timeout should be set to MAX_PDU_TIME
OSS Timeout and Retry
The OSS SNMP operation timeout value must be configured to a value greater than or equal to MAX_PDU_TIME configured in snmpd.cnf config file (300 seconds by default). This will ensure that the OSS waits for a sufficient turnaround time for CWM SNMP Agent status.
Configuring the OSS timeout to a value less than the MAX_PDU_TIME(CWM SNMP Agent turnaround time) will result in duplicate requests for the same SNMP operation to be forwarded to the CWM SNMP Agent. OSS might send one more request for the same operation currently in progress, which might result in an SNMP error being returned to OSS.
Statistics Collection Manager Release Notes
This section provides release note information about the Statistics Collection Manager (SCM) application.
New Features
CWM 11 adds statistics collection support for the PXM1E, the FRSM-HS2/B, and the FRSM-12
Limitations
We recommend that you use the default number of 100 nodes per SCM collector. If you use too high a number of nodes per SCM, the workstation might fail on a UNIX select system call, ftp or tftp limitation.
The following limitation also exists:
•
Additional Information
The SCM supports a maximum of 400 ports for collectors. The default setting is 100 nodes. If the workstation manages a large number of nodes, scmcollsvr.conf should be tuned to achieve maximum performance, especially the buffer size of all file queues and the number of threads for ftp or tftp.
You must adhere to the following rules when you configure peak interval through CWM. Violating these rules will cause tftp error 22 to be displayed in the SCM.
•
•
•
•
The switch requires processing time to parse the stats.enable file. Depending on the number of statistics and the number of objects, this time can be a long time. Currently, SCM has a finite value (maximum 420 seconds) for time-out to wait for the switch response. There might be cases where SCM will time-out waiting for the switch to finish parsing the stats.enable file. If there are excessive time-outs, try one of the following:
1.
2.
3.
time—Calculated using:
time = (stats / cnt) * delayWhere:
stats—Calculated using:
(conns * stats_per_con) + (CLNs * stats_per_cln) + (trks * stats_per_trk) +
(ports * stats_per_port)cnt—Number of stats configured in one group before giving up CPU; a configurable parameter on the switch
delay—Delay between enabling of each group of statistics; a configurable parameter on switch.
WANCV 4.11 Notes and Cautions
For MGX 8220, this CiscoView package requires MGX 8220 Boot Code version 1.0.00 and MGX 8220 ASC firmware version 4.0.20 or higher. For the new features, MGX 8220 firmware 5.0.10 or later is recommended.
The LEDs displayed in the chassis screen still display as green on the front card while there is a card mismatch. You must currently go to the "card summary" display to see the indicator of "mismatchwithParent".
With CWM 11.0.10, CiscoView shows an incorrect LED state for the standby VISM PR E1 card in a redundant VISM PR E1 card set undergoing "softswitch" Instead of reverting to Standby state, the slot reverted to standby displays as failed. The "RedundancyInfo" table under shelf configuration correctly indicates that the card is in standby mode.
The LEDs displayed in the chassis screen only convey card status for the selected card and not alarm status in the node. The "node alarm status" is shown at the top of a PXM. The "port" LED's red or yellow colors do represent an "alarm" state for a physical interface.
With CWM 11.0.10, CiscoView shows parameters as configurable that are not applicable for the VISM line type (E1). In the vism Ds0 Config screen under the Line Config. screen, the "Insert Local CAS" and "Local CAS Pattern" parameters are not greyed out. When you have a E1 VISM card you are not allowed to modify the local CAS type (cwmVismDs0InsertLocalCas) or the local CAS bit pattern (cwmVismDs0LocalCasPattern). If you try to change these values the system displays an error.
Performance
The various timers and retry counter should be configured from the Preference menu. For a typical installation, Polling and Monitoring should be about 60 seconds and Timeout should be at least 15 seconds. Faster polling and monitoring values can be configured if conditions permit. One retry is the recommended configuration.
Note
Control Point Interfaces
Command Line Interface
Use the following command line interface (CLI) commands to configure the IP Connectivity IPATM interface.
Note
ipifconfig—Configure IP address information for an IP interface
ipifconfig <interface> [<ip_address>] [up | down] [netmask <mask>]
[broadcast <broad_addr>] [arp | noarp] [svc | nosvc] [pvc | nopvc]
[default | nodefault] [clrstats]
Where:
<interface>—atmX, where X is the unit number (currently X is 0)
<ip_address>—IP address of interface (optional), but must exist if interface not previously configured
[up | down]—Mark interface up or down (optional)
[netmask <mask>]—Specify network mask for interface (optional)
[broadcast <broad_addr>]—specify broadcast IP address for interface (optional)
[arp | noarp]—Specify whether ARP is enabled or disabled (optional), default is enabled if interface supports ARP
[svc | nosvc]—Specify whether SVC is enabled or disabled (optional), default is enabled if interface supports SVC
[pvc | nopvc]—Specify whether PVC is enabled or disabled (optional), default is disabled
[default | nodefault—Use this interface as the default route or disable this interface as the default route (optional)
[clrstats]—Clear all interface and SVC/PVC statistics for given interface (optional)
dspipif—Display IP configuration and statistics information for one or all IP interfaces
dspipif [<interface>]
Where:
[<interface>]—atmX, where X is the unit number (optional)
svcifconfig—Configure SVC address information for an IP interface
svcifconfig <interface> router | local <AESA> [arp | noarp] [llcencap | vcmux] [default | nodefault] [reset] [delete] [clrstats]
Where:
<interface>—atmX, where X is the unit number (currently X is 0)
router | local <AESA>—Specify whether the given AESA address corresponds to a router or the local PXM. One of the keywords "router" or "local" must be specified. The <AESA> is an NSAP address used by the router or the local PXM.
[arp | noarp]—Specify whether ATMARP is enabled or disabled on this SVC (optional). Interface must also support ARP for ATMARP to be available (see ipifconfig above).
Note
[llcsnap | vcmux]—Specify the encapsulation method to be used on the SVC. llcsnap corresponds to LLC Snap encapsulation, while vcmux is for VC Based Multiplexing.
Note
[default | nodefault]—Use this SVC as the default route on the interface or disable this SVC as the default route (optional)
[reset]—Force reset on the SVC. SVC call is released, then the call is attempted again (optional)
[delete]—Delete the specified AESA configuration (optional)
[clrstats]—Clears all SVC statistics on this interface (optional)
dspsvcif—Display SVC address information for one or all IP interfaces supporting SVC
dspsvcif [<interface>]
Where:
[<interface>]—atmX, where X is the unit number (optional)
pvcifconfig—Configure PVC address information for an IP interface
pvcifconfig <interface> router | feeder <PVC> [arp | noarp] [llcencap | vcmux] [default | nodefault] [up] [reset] [delete] [clrstats]
Where:
<interface>—atmX, where X is the unit number (currently X is 0)
router | feeder <PVC>—Specify whether the given PVC address corresponds to a router or a feeder interface. One of the keywords router or feeder must be specified. The <PVC> is a PVC address of the form VPI.VCI used by the router or the feeder interface.
[arp | noarp]—Specify whether ATMARP is enabled or disabled on this PVC (optional). Interface must also support ARP for ATMARP to be available (see ipifconfig above).
Note
[llcsnap | vcmux]—Specify the encapsulation method to be used on the PVC.
llcsnap corresponds to LLC Snap encapsulation, while vcmux is for VC Based Multiplexing.
Note
[default | nodefault]—Use this PVC as the default route on the interface or disable this PVC as the default route (optional)
[up]put the PVC into UP state and attempt to bind the lcns associated. PVC must exist (optional)
[reset]—Force reset on the PVC. PVC is placed back into SETUP state (optional)
[delete]—Delete the specified PVC configuration (optional)
[clrstats—Clear all PVC statistics on this interface (optional)
dsppvcif—Display PVC address information for one or all IP interfaces supporting PVC
dsppvcif [<interface>]
Where:
[<interface>—atmX, where X is the unit number (optional)
dspipifcache—Display interface cache translation table for one or all interfaces
dspipifcache [<interface>]
Where:
<interface>]—atmX, where X is the unit number (optional)
dspipconntask—Display IP Connectivity task information (Debug command)
dspipconntask
setipconndebug—set debug level for IP Connectivity task (Debug command)
setipconndebug [debuglevel]
Where:
[debuglevel]—Value specifying one or more of the following:
NO LOGGING: 0x0TASK ERRORS: 0x1TASK DEBUG: 0x2ATM PROTOCOL: 0x4TASK STARTUP: 0x8TASK EVENTS: 0x10SIGAPI: 0x20ATMARP PROTOCOL: 0x40TASK TIMERS: 0x80INTERFACE CACHE: 0x100SUBTASK EVENTS: 0x200DISKDB EVENTS: 0x400RAMDB EVENTS: 0x800ALL LOGGING: 0xffffffffCaveats
This section lists the known anomalies in the Cisco WAN Manager Release 11.0.10 software and other associated software.
Anomalies Resolved in CWM 11.0.10 Patch 3
Table 15 lists the anomalies resolved in CWM Release 11.0.10 Patch 3 as of 8/22/03.
Known Anomalies in CWM Release 11.0.10 Patch 3
Table 16 lists the known anomalies in CWM Release 11.0.10 Patch 3 software.
Table 16 Known Anomalies in CWM Release 11.0.10 Patch 3 Software
CSCdx72708
Improve EMC log messages
Symptom:
1.
2.
Conditions:
None
Workaround:
None
CSCdx76945
Need new value for mode field in node table for resync failure
Symptom:
When node/card resync fails, the mode field in node table will change to "4" or "5," even if the node/card has been successfully resync'd before. Should have another value in the field to tell the node has been synced up before. A field in node/card table may be added to record the last time the node/card was synced up.
Condition:
None
Workaround:
Unknown.
CSCdy19807
Wrong alarm on collapsed trunks
Symptom:
Trunks with false alarm only when collapsed.
Conditions:
Not clear.
Workaround:
Refresh. Expanded view of trunks shows correct alarm.
CSCdy33589
CLR values displayed for PXM1E does not match with switch default values
Symptom:
CWM GUI shows diff default values for COSB SCT for PXM1E then what is displayed by switch.
Conditions:
Do dspportsct cosb <portNum> on switch Compare with COSB tab display for CLR.
Workaround:
None. This is not service affecting. The default values displayed on CWM are incorrect. Switch values should be considered correct.
CSCdy83851
DiagServer coredumped on a CWM machine
Symptom:
DiagServer coredumped on one machine.
Conditions:
Occurred during CWM core shutdown.
Workaround:
None
CSCdy84495
Topology shows trunk as clear after doing down and up LMI/ILMI on downed port
Symptom:
CWM shows feeder trunk as clear when the feeder trunk is down.
Conditions:
This happens when the below operations are performed.
1. Down the port using dnport at the MGX2 side.
2. Enable LMI using uplmi.
Workaround:
1. Enable/Disable LMI with the Port Admin status as UP.
CSCdy84607
A few AutoRoute trunks are not shown in Network Browser
Symptom:
Few AR trunks are missing from Network Browser
Conditions:
Network has BPX and MGX2 with XLMI and/or PNNI trunks
Network.conf is configured as Hybrid and have a BPX node as AR gateway
SNMP queries on the BPX fail intermittently.
Workaround:
Warmstart and make sure that snmp query for IP Address succeeds always
CSCdy85868
CWM installation hangs at CV install if cronjob leaves a /tmp/crout* file
Symptom:
Installation of CWM + CV hangs
Conditions:
When cronjob creates a /tmp/crontab* file after starting CWM installation and before CV installation starts
Workaround:
Remove all files /tmp/crontab* just before CV portion of the install starts
CSCdy87250
BPX node discovered as foreign node and got deleted from database
Symptom:
BPX node discovered as foreign node and got deleted from database
Conditions:
This is an intermittent problem seen on coldstarts.
Workaround:
Warmstart/Coldstart CWM.
CSCdz01188
On sunrise install, install does not complete
Symptom:
The webServer is not running
Conditions:
When CWM is installed for the first time on a new OS (either a regular install or using the upgrade option)
Workaround:
Follow the procedures in the "Issue with Upgrading or Installing CWM 11.0.10 on Systems That Use or Will Be Using Meta Devices or Multiple Disks for Informix" section of this release note.
CSCea43091
Forced resynch causes trk port to be seen by EMC as NON-NNI, blocks sdbrocker
Symptom:
sdatabroker stuck in loop and cannot add conns. from the MGX8250 node.
Conditions:
Forced resync was done on the MGX8250 node.
Workaround:
none
CSCea58685
scmcollsvr is not cleaning up after start coll fails
Symptom:
Stats Collection fails
Conditions:
If an unreachable address (one of inband or out-of-band) was used for starting collection, the collection fails. After that, if a reachable address (out-of-band or inband) is used, SCMGUI does not generate an error, but the statistics collection process fails because it still uses the old ip address.
Workaround:
Remove entry in node_info for that nodeid in scmdb database and restart scmcollsvr process.
CSCea71339
swap space problem on machine, creates process reinitialization
Symptom:
All swap space and memory is used severly affecting the CWM processes
Conditions:
Less swap space on the machine
Workaround:
Either add more swap to the machine.
or
Reduce the number of BUFFERS in onconfig for Informix and restart Informix and CWM
This will slow down the database performance but CWM processes will not reinitialize
CSCea91637
Need alarms when cards with no conns are pulled for CESM and SRM cards
Symptom:
When CESM, SRM is removed from the node there is no Trap seen in CIC, it needs
to be verified that no trap is generated when these modules are removed and if
so create one. When a service module is removed that has no connections on it no
trap is seen
in CIC, it needs to be verified that no trap is generated, and if so create one
Conditions:
CUstomer is running CWM 11.0.10 Patch 1
CIC 3.4
R1 version 1.2.13
R2 version 3.0.20
Workaround:
unknown
CSCeb02542
T3E3 FR/CE Stats are not shown in Wingz
Symptoms:
T3/E3 lines for FRSM/CESM cards on PXM1-, PXM45-, PXM1E-based shelves are not provided in wingz. Therefore, T3/E3 line statistics for FRSM/CESM card can not be plotted using wingz.
Conditions:
The T3/E3 line statistics on FRSM/CESM card are being collected, and wingz reporting tool is beingused to report data.
Workaround:
None
CSCeb04024
Some statistics are not applicable for NBSM cards
Symptom:
The following statistics are not collected by SCM for FRSM card on PXM1, PXM45, PMX1E:
•
•
•
•
The following statistics are not supported by SCM, even though it is supported by the switch:
FRSM Connection:
•
The following statistics names do not match with CLI for FRSM card connections:
•
•
Conditions:
If the user is looking for FRSM connection statistics - Tx Frame Tagged DE, Rx Bytes Tagged DE and FRSM Port Stats - Transmit Status Enquiries in scm stat files.
Workaround:
For frames Rx in Excess of CIR stat, intrepret it as Rx Frames Tagged DE and for frames Tx in Excess of CIR stat, intrepret it as Tx Frames Tagged DE.
For other statistics mentioned in the symptom, there is no workaround.
CSCeb03364
SNMP Query to svConnSubType returns incorrect value
Symptom:
SNMP GET on svConnSubType returns incorrect value
Conditions:
svConnSubType set to fr-fs, GET returns fr for a XPVC connection.
Workaround:
None.
CSCeb14967
New traps in CWM 11.0.10 patch 2 have ipaddress in wrong format
Symptom:
Some of the new CWM 11.0.10 traps have wrong ipaddress.
The ipaddress in being built as an integer instead of string
Condition:
Generate any of the traps 28101, 28102, 28103 series traps
Workaround:
None
CSCeb20233
ILMITopoc reinitializes
Symptom:
ILMITopoc reinitializations on CWM
Conditions:
Relate to improper switch configuration with trunks
Workaround:
None
CSCeb25978
AXSM B Cards not shown in Wingz
Symptom:
AXSM-B Connections, Lines, Ports are not shown in Wingz
Conditions:
If wingz is reporting statistics collected by SCM.
Workaround:
None
CSCeb29370
Cisco View Telnet button not using the same telnet relay as CWM
Symptom:
Customer is not able to use the telnet button on Cisco View to telnet to a node.
They are able to use the admin function from Topology to telnet to the node.
They would like to have Cisco View telnet function use the same mechanism as the
admin function in Topology to telnet into the node
Conditions:
Customer is running CWM 11.0.10Patch 1. They are running CV 5.4. There is a firewall
between the PC client and the CWM Machine. The network is on the same side as the CWM
Workaround:
Customer can use the admin function from the Topology to telnet to the node
CSCeb31717
svAtmPortAssociatedLines returns incorrect ima port vals
Symptom:
SNMPGET vals returned for svAtmPortAssociatedLines are incorrect
Conditions:
IMA port
Workaround:
Check DB or CLI
CSCeb44087
LogServer reinitialized
Symptom:
LogServer Reinitialized
Conditions:
The NETopology GUI was opened and then closed
Workaround:
None
CSCeb45924
not able to open runSctGuI from workstation
Symptom: not able to open runSctGuI from cwm workstation.
Condition: runSctGui from cwm workstation.
Workaround : runSctGui from cwm desktop ( TOPOGUI->APPS->Service class template)
Note, this script for running SctGui directly from the OS prompt is not supported in Release 11.0.10 like it was in Release 10.5.10. In Release 11.0.10, it is assumed we are using one JRE (java runtime environment) for all the java apps that communicate with Corba servers. NWBrowser and Configurator are exceptions because they can be run without corba servers.
Because of the way the clients are notified if a Corba server goes down, the clients need to be launched from NWTopology. This is the reason we have removed all the other launch points (CM/SCT/SCM) from the webstart launch page. Each client is an observer to NWTopology for corba disconnect callbacks. Therefore, it is only NWTopology GUI that needs register for callbacks.
The reason this design change was made in Release 11.0.10 was to fix a bug with only getting one callback when a server dies. In a situation in which multiple clients share the same servers (Ex. CMGui and DiagCenter, both use CmServer, All GUIs use CwmGs).
In the old design, only the last GUI client that registered for the callback, would get the callback. So if CMGUI was launched, then DiagCenter, if cmsvr dies and came back up, CMGUI would never know, resulting in a stale CMGui client.
The fix as mentioned above, was to have NWTopology be the only client to register for Corba disconnect callbacks. All other clients would basically register (as an observer) to NWTopology for disconnect callback information. So if cmsvr died, NWTopology would get the callback and it would notify its observers, and DiagCenter and CMGui would behave correctly.
Since the disconnect callback code was moved to NWTopology in 11.0.10, All GUI clients should be launched from NWTopology (such as SCT), or they will not be notified if a corba server restarts.
CSCeb49978
error due to not enough fd for eventd when health mon enabled
Symptom:
The following error message was observed on the console
"IPC: accept failed: Too many open files"
Conditions:
Health Monitoring parameter was enabled in svplus.conf and the number of child processes to be spawned was increased as the network was large.
Workaround:
None
CSCeb69949
Reapplying unmodified %Util not propagated to PNNI nodes
Symptom:
Reapply %Util vals via SNMP does not propagate to PNNI segment
Conditions:
Using CWM 12.0.00-P1M ConnProxy, cmgrd for XPVC %Util mod.
PNNI_PER_UTIL_FLAG in cmgrd.conf is set to ENABLE.
Workaround:
Change to value other than current value and then change it back to current value
CSCeb79573
Conn -trace is failing from CESM endpoints to other mgx endpoints
Symptom:
Connection Trace is failing for CESM mgx8950 node to other endpoints.
Condition:
When the CESM ports are structured ports and there is more than one structured port on a line, the Connection Trace will not succeed.
Workaround:
N/A
CSCeb80864
telnet through Cisco View is not connecting to node
Symptom:
Node could not be telneted through telnet button in CV
Condition:
CiscoView launched through Client and svpluscwm3 running CWM 11.0.10 p3j
Workaround:
N/A
CSCec06751
Stale clients still seen in Admin Gui
Symptom:
A PC client when disconnected (lan disconnect or sudden power down) leaves the user client Count of CWM unaffected. Thereby reaching the client Count limit erroneously even when the limit is not reached.
Conditions:
Every time a PC client is powered down suddenly or LAN cable is pulled out.
Workaround:
Killing CwmGs on the Server.
CSCec11228
BadFileList is showing in purge directory for some nodes
Symptom:
BadFileList is showing in purge directory, but the data is parsed properly in DB.
Conditions:
Stats collection using Primary and secondary
Workaround:
The following procedure can be used to check if the data for a particular file has been parsed into DB already or not. (Apply to 11.0.10 ONLY)
Step 1: Use statsreader to parse the statsfile, this will get the Node Obj ID / SubObject ID / Stats Type list.
Step 2: run the following query against statsdb for corresponding CWM Obj ID / SubObject ID / Stats Type list:
select cwm_objtype, cwm_subtype, cwm_stattype from scmnodestat where node_objtype = ? AND node_subtype = ? AND node_stattype = ?
replacing ? with the numbers from Step 1.
If this query returns 0 row, it means the CWM obj id is equal to Node obj id.
Step 3: Check parserconfig.stats, if "-d 0" (stratacom), go to Step 4A, if "-d 1" (statsdb) , go to Step 4B.
Step 4A: Run the following query against statsdb to get the data table name in stratacom:
a.
b.
Step 4B: Run the following query against statsdb to get the data table name in statsdb:
a.
b.
Step 5: Run gettimestamp script to get the timestamp for this particular file:
/gettimestamp [-u] <MM/DD/YYYY> <hour:minute:second>in which, "<MM/DD/YYYY> <hour:minute:second>" can be observed from the filename.
Step 6: Check the data table to see if the data was correctly parsed.
a.
b.
CSCin15035
Do not Save option in stats DB host config dialog is not working
Symptom:
"Do not Purge" Option in stats DB host Configuration Dialog is not working.
Condition:
It happens when the "Do not Purge" option is chosen.
Workaround:
To manually delete the files from the purge directory once in every three days.
CSCin48200
Unable to Modify BXME-FRM connection from CMGUI
Symptom:
Unable to Modify ATM-FRM connection from CMGUI
Condition:
Policing Model cannot be modified for BXME-FRM connection
Workaround:
Able to modify the same from Proxy
CSCin48911
Topo GUI & DB doesnt reflect changed node name on standalone-MGX 8250
Symptom:
TopoGUI and DB are not reflecting the changed node name
Condition:
On changing node name of standalone node (MGX 8250)
Workaround:
None
Anomaly Status Changes in Release 11.0.10 Patch 3
Table 17 lists the known anomalies that have changed status in Release 11.0.10 Patch 3 as of 8/22/03.
Changed status means that the anomaly changed from open in Release 11.0.10 Patch 2 to a state other than resolved. The workaround states the status (closed, junked, duplicate, or unreproducible).
Anomalies Resolved in CWM 11.0.10 Patch 2
Table 18 lists the anomalies resolved in CWM Release 11.0.10 Patch 2 as of 4/5/03.
Known Anomalies in CWM Release 11.0.10 Patch 2
Table 19 lists the known anomalies in CWM Release 11.0.10 Patch 2 software.
Table 19 Known Anomalies in CWM Release 11.0.10 Patch 2 Software
CSCin36910
SES 1.1(79.102) returns NO SUCH NAME for mib object cwaChanOamSegEpEnable
Symptom:
Added RPM-XF:AUSM connection in one CWM shown as incomplete in other CWM looking in the same network.
Conditions:
Add RPM-XF:AUSM connection in one CWM and check in other CWM.
Workaround:
None
CSCdx72708
Improve EMC log messages
Symptom:
1.
2.
Conditions:
None
Workaround:
None
CSCdx76945
Need new value for mode field in node table for resync failure
Symptom:
When node/card resync fails, the mode field in node table will change to "4" or "5," even if the node/card has been successfully resync'd before. Should have another value in the field to tell the node has been synced up before. A field in node/card table may be added to record the last time the node/card was synced up.
Condition:
None
Workaround:
Unknown.
CSCdy19807
Wrong alarm on collapsed trunks
Symptom:
Trunks with false alarm only when collapsed.
Conditions:
Not clear.
Workaround:
Refresh. Expanded view of trunks shows correct alarm.
CSCdy31692
Cannot change UPC Threshold for vbr3-nrt connection on Connection Manager
Symptom:
Modified values do not reflect on CMGUI for UPC Threshold parameters on vbr3_nrt ATM-ATM PVC.
Conditions:
When modifying UPC Threshold parameters on vbr3_nrt ATM-ATM PVC on BXM side in BPX SW image 9.2.x.
Workaround:
None
CSCdy33589
CLR values displayed for PXM1E does not match with switch default values
Symptom:
CWM GUI shows diff default values for COSB SCT for PXM1E then what is displayed by switch.
Conditions:
Do dspportsct cosb <portNum> on switch Compare with COSB tab display for CLR.
Workaround:
None. This is not service affecting. The default values displayed on CWM are incorrect. Switch values should be considered correct.
CSCea43091
Unknown exception message for launching CM application from desktop
Symptom:
sdatabroker stuck in loop and cannot add conns. from the MGX8250 node.
Conditions:
Forced resync was done on the MGX8250 node.
Workaround:
none
CSCea65793
User information not shown until you press Enter with MGX8220
Symptom:
End user should be able to see what he/she has entered.
Conditions:
Normal mode
Workaround:
None
CSCdy71243
POP2 nodes failed to resync because of timeout (LSNT emulator related)
Symptom:
POP2 nodes failed to resync on ent4500 machine
Conditions:
Soak test the CWM for a day
Workaround:
Manually resync the nodes
CSCea07963
rtm core dump
Symptom:
rtm core dump
Conditions:
CWM 11.0.10 P1(Bin_Bundle 1)
Workaround:
unknown
CSCdy82218
SNMP Module: Nodes failed to resync
Symptom:
CWM failed to resync pop2 nodes after first sync. All the pop2 nodes went to mode 5 and never synced up again.
Conditions:
Soak test the CWM for a day.
Workaround:
Manually resync'd the nodes.
Current Status:
DE assigned. This scenario occurs because of the timing of the SNMP responses coming from the emulated nodes in the LSNT Network.
CSCdz55698
Topology - Display Trunk shows PNNI Protocol instead of Feeder
Symptom:
Topology - Display Trunk shows PNNI Protocol instead of Feeder
Conditions:
None.
Workaround:
None.
CSCdy83851
DiagServer coredumped on a CWM machine
Symptom:
DiagServer coredumped on one machine.
Conditions:
Occurred during CWM core shutdown.
Workaround:
None
CSCdy84495
Topology shows trunk as clear after doing down and up LMI/ILMI on downed port
Symptom:
CWM shows feeder trunk as clear when the feeder trunk is down.
Conditions:
This happens when the below operations are performed.
1. Down the port using dnport at the MGX2 side.
2. Enable LMI using uplmi.
Workaround:
1. Enable/Disable LMI with the Port Admin status as UP.
CSCdy84607
A few AutoRoute trunks are not shown in Network Browser
Symptom:
Few AR trunks are missing from Network Browser
Conditions:
Network has BPX and MGX2 with XLMI and/or PNNI trunks
Network.conf is configured as Hybrid and have a BPX node as AR gateway
SNMP queries on the BPX fail intermittently.
Workaround:
Warmstart and make sure that snmp query for IP Address succeeds always
CSCdy85868
CWM installation hangs at CV install if cronjob leaves a /tmp/crout* file
Symptom:
Installation of CWM + CV hangs
Conditions:
When cronjob creates a /tmp/crontab* file after starting CWM installation and before CV installation starts
Workaround:
Remove all files /tmp/crontab* just before CV portion of the install starts
CSCdy87250
BPX node discovered as foreign node and got deleted from database
Symptom:
BPX node discovered as foreign node and got deleted from database
Conditions:
This is an intermittent problem seen on coldstarts.
Workaround:
Warmstart/Coldstart CWM.
CSCdz01188
On sunrise install, install does not complete
Symptom:
The webServer is not running
Conditions:
When CWM is installed for the first time on a new OS (either a regular install or using the upgrade option)
Workaround:
Follow the procedures in the "Issue with Upgrading or Installing CWM 11.0.10 on Systems That Use or Will Be Using Meta Devices or Multiple Disks for Informix" section of this release note.
CSCdz24906
GUI does not refresh when trunks is deleted
CSCin15035
Do not Save option in stats DB host config dialog is not working
Symptom:
"Do not Purge" Option in stats DB host Configuration Dialog is not working.
Condition:
It happens when the "Do not Purge" option is chosen.
Workaround:
To manually delete the files from the purge directory once in every three days.
Anomaly Status Changes in Release 11.0.10 Patch 2
Table 20 lists the known anomalies that have changed status in Release 11.0.10 Patch 2 as of 4/5/03. Changed status means that the anomaly changed from open in Release 11.0.10 Patch 1 to a state other than resolved. The workaround states the status (closed, junked, duplicate, or unreproducible).
Known Anomalies in CWM 11.0.10 Patch 1
Table 21 lists the known anomalies in CWM Release 11.0.10 Patch 1 software as of 12/16/02.
Table 21 Known Anomalies in CWM Release 11.0.10 Patch 1 Software
CSCdx63722
Can not modify PXM to FRSM-AXIS hybrid connections
Symptom:
Can't modify the PCR for hybrid cons between PXM and FRSM on MGX 8220.
Conditions:
Running CWM 10.5.10 Patch 2
Workaround:
none
CSCdx72708
Improve EMC log messages
Symptom:
1.
2.
Conditions:
None
Workaround:
None
CSCdx76945
Need new value for mode field in node table for resync failure
Symptom:
When node/card resync is failed, the mode field in node table will change to "4" or "5", even if the node/card has been successfully resync'd before. Should have another value in the field to tell the node has been synced up before. A field in node/card table may be added to record the last time at which the node/card was synced up.
Condition:
None
Workaround:
Unknown.
CSCdy19807
Wrong alarm on collapsed trunks
Symptom:
Trunks with false alarm only when collapsed.
Conditions:
Not clear.
Workaround:
Refresh. Expanded view of trunks shows correct alarm.
CSCdy31692
Cannot change the UPC Threshold for vbr3-nrt connection on Connection Manager
Symptom:
Modified values do not reflect on CMGUI for UPC Threshold parameters on vbr3_nrt ATM-ATM PVC
Conditions:
When modifying UPC Threshold parameters on vbr3_nrt ATM-ATM PVC on BXM side in BPX SW image 9.2.x
Workaround:
None
CSCdy33589
CLR values displayed for PXM1E does not match with switch default values
Symptom:
CWM GUI shows diff default values for COSB SCT for PXM1E then what is displayed by switch
Conditions:
Do dspportsct cosb <portNum> on switch Compare with COSB tab display for CLR
Workaround:
None. This is not service affecting. The default values displayed on CWM are incorrect. Switch values should be considered correct.
CSCdy43172
Unknown exception message for launching CM application from desktop
Symptom:
Unknown exception
Conditions:
When launching CM application from topo desktop
Workaround:
1. Try once again to launch the application
CSCdy46986
Onstat coredump occurred
Symptom:
Onstat core dumped
Conditions:
Unknown
Workaround:
Unknown
Further Problem Description:
Onstat is used to get informix related parameters on the system.
This is never executed by any process as such.
CSCdy71243
POP2 nodes failed to resync because of timeout (LSNT emulator related)
Symptom:
POP2 nodes failed to resync on ent4500 machine
Conditions:
Soak test the CWM for a day
Workaround:
Manually resync the nodes
CSCdy77648
Informix database got frozen
Symptom:
Unable to execute selnd command
Conditions:
On LSNT environment have CWM up and running for a day or two.
Workaround:
Stop core, coldstart -F and restart informix.
CSCdy82218
SNMP Module: Nodes failed to resync
Symptom:
CWM failed to resync pop2 nodes after first sync. All the pop2 nodes went to mode 5 and never synced up again.
Conditions:
Soak test the CWM for a day.
Workaround:
Manually resync'd the nodes.
Current Status:
DE assigned. This scenario occurs because of the timing of the SNMP responses coming from the emulated nodes in the LSNT Network.
CSCdy82595
Conns ok in CWM after the node was powered down
Symptom:
270 out of ~12k Connections between Janus and Pop-2 were in ok state after the Janus node was powered down.
Conditions:
It seems that traps were sent from the switch and received in ooemc, but that the processing took some time. After more than one hour the status was updated.
Workaround:
node resync
CSCdy82895
Change in ATM IP of BPX loses feeder info from other GUIs except topo
Symptom:
Change in ATM IP of BPX loses feeder info from other GUIs except Topo
Conditions:
1. ATM IP of a BPX node is changed.
2. The BPX has feeders attached to it.
Workaround:
Unknown
CSCdy83851
DiagServer coredumped on a CWM machine
Symptom:
DiagServer coredumped on one machine
Conditions:
Occurred during CWM core shutdown
Workaround:
None.
CSCdy84495
Topology shows trunk as clear after doing down & up LMI/ILMI on downed port
Symptom:
CWM shows feeder trunk as clear when the feeder trunk is down.
Conditions:
This happens when the below operations are performed.
1. Down the port using the dnport command at the MGX2 side.
2. Enable LMI using uplmi.
Workaround:
1. Enable/Disable LMI with the Port Admin status as UP.
CSCdy84607
A few AutoRoute trunks are not shown in Network Browser
Symptom:
Few AR trunks are missing from Network Browser
Conditions:
Network has BPX and MGX2 with XLMI and/or PNNI trunks
Network.conf is configured as Hybrid and have a BPX node as AR gateway
SNMP queries on the BPX fail intermittently.
Workaround:
Warmstart and make sure that snmp query for IP Address succeeds always
CSCdy85868
CWM installation hangs at CV install if cronjob leaves a /tmp/crout* file
Symptom:
Installation of CWM + CV hangs
Conditions:
When cronjob creates a /tmp/crontab* file after starting CWM installation and before CV installation starts
Workaround:
Remove all files /tmp/crontab* just before CV portion of the install starts
CSCdy87250
BPX node discovered as foreign node and got deleted from database
Symptom:
BPX node discovered as foreign node & got deleted from database
Conditions:
After coldstart -F. This is an intermittent problem seen on coldstarts.
Workaround:
Warmstart/Coldstart CWM.
CSCdz01188
On sunrise install, install does not complete
Symptom:
The webServer is not running
Conditions:
When CWM is installed for the first time on a new OS (either a regular install or using the upgrade option)
Workaround:
Follow the procedures in the "Issue with Upgrading or Installing CWM 11.0.10 on Systems That Use or Will Be Using Meta Devices or Multiple Disks for Informix" section of this release note.
CSCdz17729
Config restore fails if underscore used in node name
Symptom:
The Config Restore feature of CWM may fail depending on how the node is named.
Conditions:
The Config Restore feature of CWM does not work if the MGX node name contains an underscore.
Workaround:
Do not use an "_" in the MGX node name, or manually edit the file name on the MGX to match what CWM is looking for.
CSCdz24906
GUI does not refresh when trunks is deleted
CSCin15035
TB+SOL2.7:SCM:Do not Save option in stats DB host config dialog is not working
Symptom:
"Do not Purge" Option in stats DB host Configuration Dialog is not working.
Condition:
It happens when the "Do not Purge" option is chosen.
Workaround:
To manually delete the files from the purge directory once in every three days.
CSCin16127
TB+SOL2.7: Logical slot for a secondary card (standby) displays physicalslotnum
Symptom:
Logical slot for a secondary card (standby) displays physicalslotnum
Condition:
Add a redundancy on FRSM-2E3 card, pull out standby card and re-insert it after sometime.
Workaround:
Node Resync
Anomalies Resolved in CWM Release 11.0.10 Patch 1
Table 22 lists the anomalies resolved in CWM Release 11.0.10 Patch 1 software as of 12/12/02.
Anomalies Resolved in WANDEST Server Release 2.3 Patch 3
Table 24 lists the anomalies resolved in WANDEST Server Release 2.3 Patch 3.
Anomalies Resolved in WANDEST Server Release 2.3 Patch 2.1
Table 24 lists the anomalies resolved in WANDEST Server Release 2.3 Patch 2.1.
Anomalies Resolved in WANDEST Server Release 2.3 Patch 2
Table 25 lists the anomalies resolved in WANDEST Server Release 2.3 Patch 2.
Anomalies Resolved in WANDEST Release Server 2.3 Patch 1
Table 26 lists the anomalies resolved in the WANDEST Server Release 2.3 Patch 1.
Table 26 Anomalies Resolved in WANDEST Server Release 2.3 Patch 1
CSCdz22786
Wandest Client Registration to Server fails on secondary CWMs
Anomalies Resolved in WANDEST Client Release 2.3 Patch 2.1
Table 27 lists the anomalies resolved in WANDEST Client Release 2.3 Patch 2.1.
Table 27 Anomalies Resolved in WANDEST Client Release 2.3 Patch 2.1
CSCea17584
scmcardfamilystat not getting uploaded during the incremental upload
Anomalies Resolved in WANDEST Client Release 2.3 Patch 2
Table 28 lists the anomalies resolved in WANDEST Client Release 2.3 Patch 2.
Table 28 Anomalies Resolved in WANDEST Client Release 2.3 Patch 2
CSCea30195
wdclient coredump
Anomalies Resolved in CWM Release 11.0.10
Table 29 lists anomalies resolved with CWM Release 11.0.10 as of 10/09/02.
Note
Anomaly Status Changes in Release 11.0.10 Patch 1
Table 30 lists anomalies that have changed status in Release 11.0.10 Patch 1 as of 12/19/02. Changed status means that it went from open in release 11.0.10 to a state other than resolved. The workaround states the status (closed, junked, duplicate, or unreproducible).
Anomaly Status Changes in Release 11.0.10
Table 31 lists anomalies that have changed status in Release 11.0.10 as of 10/09/02. Changed status means that it went from open in Release 11.0.00 to a state other than resolved. The workaround states the status (closed, junked, duplicate, or unreproducible).
Anomalies Resolved in CWM 11.0.00 Patch 1
Table 32 lists the anomalies resolved in CWM Release 11.0.00 Patch 1 as of 06/18/02.
Anomalies Resolved in CMF 2.1 Patch
Table 33 lists the anomalies resolved in CMF 2.1 Patch.
Table 33 Anomalies Resolved in CMF 2.1 Patch
Related Documentation
The following technical documents comprise the CWM 11 documentation set:
•
•
•
•
•
•
•
Obtaining Documentation
Cisco provides several ways to obtain documentation, 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 on the World Wide Web at this URL:
http://www.cisco.com/univercd/home/home.htm
You can access the Cisco website at this URL:
International Cisco websites can be accessed from this URL:
http://www.cisco.com/public/countries_languages.shtml
Documentation CD-ROM
Cisco documentation and additional literature are available in a Cisco Documentation CD-ROM package, which may have shipped with your product. The Documentation CD-ROM is updated regularly and may be more current than printed documentation. The CD-ROM package is available as a single unit or through an annual or quarterly subscription.
Registered Cisco.com users can order a single Documentation CD-ROM (product number DOC-CONDOCCD=) through the Cisco Ordering tool:
http://www.cisco.com/en/US/partner/ordering/ordering_place_order_ordering_tool_launch.html
All users can order monthly or quarterly subscriptions through the online Subscription Store:
http://www.cisco.com/go/subscription
Ordering Documentation
You can find instructions for ordering documentation at this URL:
http://www.cisco.com/univercd/cc/td/doc/es_inpck/pdi.htm
You can order Cisco documentation in these ways:
•
http://www.cisco.com/en/US/partner/ordering/index.shtml
•
Documentation Feedback
You can submit comments electronically on Cisco.com. On the Cisco Documentation home page, click Feedback at the top of the page.
You can e-mail your comments to bug-doc@cisco.com.
You can submit comments by using the response card (if present) behind the front cover of your document or by writing to the following address:
Cisco Systems
Attn: Customer Document Ordering
170 West Tasman Drive
San Jose, CA 95134-9883We appreciate your comments.
Obtaining Technical Assistance
Cisco provides Cisco.com, which includes the Cisco Technical Assistance Center (TAC) website, as a starting point for all technical assistance. Customers and partners can obtain online documentation, troubleshooting tips, and sample configurations from the Cisco TAC website. Cisco.com registered users have complete access to the technical support resources on the Cisco TAC website, including TAC tools and utilities.
Cisco.com
Cisco.com offers a suite of interactive, networked services that let you access Cisco information, networking solutions, services, programs, and resources at any time, from anywhere in the world.
Cisco.com provides a broad range of features and services to help you with these tasks:
•
•
•
•
•
To obtain customized information and service, you can self-register on Cisco.com at this URL:
http://tools.cisco.com/RPF/register/register.do
Technical Assistance Center
The Cisco TAC is available to all customers who need technical assistance with a Cisco product, technology, or solution. Two types of support are available: the Cisco TAC website and the Cisco TAC Escalation Center. The type of support that you choose depends on the priority of the problem and the conditions stated in service contracts, when applicable.
We categorize Cisco TAC inquiries according to urgency:
•
•
•
•
Cisco TAC Website
The Cisco TAC website provides online documents and tools to help troubleshoot and resolve technical issues with Cisco products and technologies. To access the Cisco TAC website, go to this URL:
All customers, partners, and resellers who have a valid Cisco service contract have complete access to the technical support resources on the Cisco TAC website. Some services on the Cisco TAC website require a Cisco.com login ID and password. If you have a valid service contract but do not have a login ID or password, go to this URL to register:
http://tools.cisco.com/RPF/register/register.do
If you are a Cisco.com registered user, and you cannot resolve your technical issues by using the Cisco TAC website, you can open a case online at this URL:
http://www.cisco.com/tac/caseopen
If you have Internet access, we recommend that you open P3 and P4 cases online so that you can fully describe the situation and attach any necessary files.
Cisco TAC Escalation Center
The Cisco TAC Escalation Center addresses priority level 1 or priority level 2 issues. These classifications are assigned when severe network degradation significantly impacts business operations. When you contact the TAC Escalation Center with a P1 or P2 problem, a Cisco TAC engineer automatically opens a case.
To obtain a directory of toll-free Cisco TAC telephone numbers for your country, go to this URL:
http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml
Before calling, please check with your network operations center to determine the Cisco support services to which your company is entitled: for example, SMARTnet, SMARTnet Onsite, or Network Supported Accounts (NSA). When you call the center, please have available your service agreement number and your product serial number.
Obtaining Additional Publications and Information
Information about Cisco products, technologies, and network solutions is available from various online and printed sources.
•
http://www.cisco.com/en/US/products/products_catalog_links_launch.html
•
•
http://www.cisco.com/go/packet
•
http://www.cisco.com/go/iqmagazine
•
http://www.cisco.com/en/US/about/ac123/ac147/about_cisco_the_internet_protocol_journal.html
•
http://www.cisco.com/en/US/learning/le31/learning_recommended_training_list.html
CCIP, the Cisco Arrow logo, the Cisco Powered Network mark, the Cisco Systems Verified logo, Cisco Unity, Follow Me Browsing, FormShare, iQ Breakthrough, iQ Expertise, iQ FastTrack, the iQ Logo, iQ Net Readiness Scorecard, Networking Academy, ScriptShare, SMARTnet, TransPath, and Voice LAN are trademarks of Cisco Systems, Inc.; Changing the Way We Work, Live, Play, and Learn, Discover All That's Possible, The Fastest Way to Increase Your Internet Quotient, and iQuick Study are service marks of Cisco Systems, Inc.; and Aironet, ASIST, BPX, Catalyst, CCDA, CCDP, CCIE, CCNA, CCNP, Cisco, the Cisco Certified Internetwork Expert logo, Cisco IOS, the Cisco IOS logo, Cisco Press, Cisco Systems, Cisco Systems Capital, the Cisco Systems logo, Empowering the Internet Generation, Enterprise/Solver, EtherChannel, EtherSwitch, Fast Step, GigaStack, Internet Quotient, IOS, IP/TV, LightStream, MGX, MICA, the Networkers logo, Network Registrar, Packet, PIX, Post-Routing, Pre-Routing, RateMUX, Registrar, SlideCast, StrataView Plus, Stratm, SwitchProbe, TeleRouter, and VCO are registered trademarks of Cisco Systems, Inc. and/or its affiliates in the U.S. and certain other countries.
All other trademarks mentioned in this document or Web site are the property of their respective owners. The use of the word partner does not imply a partnership relationship between Cisco and any other company. (0208R)
