Table Of Contents
Release Notes for Cisco WAN Manager Release 15.0.00, Patch 5
CWM Software Release 15.0.00 Packaging
New Features and Enhancements in CWM Release 15
Features Introduced in CWM Release 15.0.00, Patch 5
Features Introduced in CWM Release 15.0.00, Patch 4
Features Introduced in CWM Release 15.0.00, Patch 3
Features Introduced in CWM Release 15.0.00, Patch 2
Features Introduced in CWM Release 15.0.00
Unsupported Features and Known Feature Limitations in CWM Release 15.0.00
Configuration Center Limitations
Issues with the CWM Release 15.0.00 Statistics Collection Manager
Limitations for CWM to CWM Communication
CWM Release 15.0.00 Notes and Cautions
CWM Release 15.0.00 Server Installation or Upgrade to CWM Release 15.0.00, Patch 5
CWM Release 15.0.00 Patch 5 Installation
Using the Force Delete Feature
Adding a Desktop Shortcut for the CWM Client Application
Node Numbering for Release 9.4 IGX Feeder Nodes
ChassisView Operation After Card and Line Switchovers
Equipment Management Configuration Notes
Network Monitor Server Configuration File (NMServer.conf)
Creating and Configuring a CWM Auto-Restart Shell Script
Using the vi Editor to Create Your Auto-Restart Shell Script
SNMP Service Agent Release Notes
Trap Limitation with PXM1-based MGX Nodes
Known Anomalies in CWM Release 15.0.00 Software
Anomalies Resolved in WANDEST Release 2.5 Patch 5 Software
Anomalies Resolved in WANDEST Release 2.5 Patch 4 Software
Anomalies Resolved in WANDEST Release 2.5 Patch 3.1 Software
Anomalies Resolved in WANDEST Release 2.5 Patch 3 Software
Anomalies Resolved in CWM Release 15.0.00 Patch 5 Software
Anomalies Resolved in CWM Release 15.0.00 Patch 4 Software
Anomalies Resolved in CWM Release 15.0.00 Patch 3 Software
Anomalies Resolved in CWM Release 15.0.00 Patch 2 Software
Anomalies Closed by Other Means in CWM Release 15.0.00 Patch 3 Software
Anomalies Closed by Other Means in CWM Release 15.0.00 Patch 2 Software
Cisco Product Security Overview
Reporting Security Problems in Cisco Products
Obtaining Technical Assistance
Cisco Technical Support & Documentation Website
Definitions of Service Request Severity
Obtaining Additional Publications and Information
Release Notes for Cisco WAN Manager Release 15.0.00, Patch 5
October 31, 2005
These release notes are part OL-Release 15.0.00, Patch 5 Part Number OL-8487-01 Rev B0
Cisco WAN Manager Release 15.0.00 patch 5 software supports the following Cisco products:
•
Cisco MGX 8850 PXM45-based products running software Releases 3.0.20 and 3.0.23 through 3.0.25, 4.0.00 through 4.0.17, or 5.0.00 through 5.0.20.
•
Cisco MGX 8880 PXM45-based products running software Releases 5.0.00 through 5.0.20.
•
Cisco MGX 8950 PXM45-based products running software Releases 3.0.23 through 3.0.25, 4.0.00 through 4.0.17, or 5.0.00 through 5.0.20.
•
Cisco MGX PXM1E-based products (8830 and 8850) running software Releases 3.0.23 through 3.0.25, 4.0.00 through 4.0.17, or 5.0.00 through 5.0.20.
•
Cisco MGX PXM1-based products (8230, 8250 and 8850) running software Releases 1.1.31 through 1.1.34, 1.2.20 through 1.2.23, or 1.3.00 through 1.3.12.
•
Cisco SES PNNI Controller running software Releases 3.0.10 through 3.0.25 or 4.0.00 through 4.0.15.
•
Existing Cisco WAN switching products (including the Cisco IGX 8400 series and the Cisco BPX 8600 series) running switch software (SWSW) Releases 9.2.33 through 9.2.43, 9.3.05 through 9.3.51, or 9.4.00 through 9.4.12.
•
Existing Cisco MGX 8220 products running software Releases 4.1.07 through 4.1.12, or 5.0.12 through 5.0.20.
Table of Contents
System Requirements
In addition to the CWM platform requirements listed in the Cisco WAN Manager Installation Guide, Release 15, also consider the following:
•
CWM 15 is compatible with UltraSPARC II and UltraSPARC III. Refer to Tables 1 through 4 for the system requirements for certified platforms. The Ultra 60, Enterprise 450 and Enterprise 4500 can still be used with CWM 15. These were previously certified with earlier releases of CWM. For certified system requirements, refer to the System Requirement Guidelines in the CWM release notes for Release 11.0.10, but the minimum RAM needs to be 2 GB. Problems reported by customers who choose a non certified configuration may take more time to troubleshoot, resulting in a longer turnaround time. CWM technical support will not be provided for Sun configurations or products that are no longer supported by Sun Microsystems.
•
Video is required when using the Java Client access to CWM. Video on the CWM server is only required for user access or maintenance on the CWM server. Video can be added to Sun servers/workstations. For Ultra and Enterprise this requires a video adapter.
•
You may upgrade the standard configuration with more CPU speed, RAM size, and disk space for future expansion.
•
The default disk size for the Informix raw database is 1.7 GB. However, we strongly recommend you provide 2 GB disk space for the statistics collection process. Note that if statistics collection is done using CWM then multiple 2 GB partition chunks are required to be added to Informix. Refer to the Cisco WAN Manager Installation, Release 15, OL-4550-01 for more information on disk partitioning.
•
While CWM is running, if the remote display is stopped without properly shutting down the CWM Desktop, then reopening it remotely may not succeed.
CWM Server
•
Other UltraSPARC III Server models with equal or higher CPU speed and memory capacity can also be used.
•
If UltraSPARC II Servers are used, refer to the System Requirement Guidelines in the CWM release notes for Release 11.0.10. If you are using an Ultra 60 (low end platform), it should have at least 2 GB RAM memory.
Java Client
Standalone Statistics Manager
•
File size of 2M bytes (typically holds statistics with peak enabled for 20K endpoints).
•
The number of files does not increase with smaller file size.
•
Average Network Transfer Rate is the required TFTP/FTP throughput to collect of the Max # of files (combination of Server performance and network bandwidth/traffic).
•
If you have enabled the Parser on the CWM Server, add the Parser System Requirement to the requirements listed in Table 1.
•
The Standalone Statistics Collector (SSC) has the same system requirements as the Standalone Statistics Manager. If you have enabled the Parser, add the Parser System Requirement to the system requirements listed in Table 3.
•
A maximum of twelve Standalone Statistics Collectors can be controlled by one Standalone Statistics Manager.
Five statistics are collected from each connection segment endpoints and 15-minute file collection interval.
Add the applicable system requirements in Table 4 to the CWM Server requirements in Table 1 if the Parser Function is enabled.
Collecting statistics for four million endpoints with 5 statistics per endpoint requires 80 GB of disk space per 24 hour period. You will need at least 3 x 36 GB of disk space.
Solaris Patch Requirements
After installing the Solaris 8 operating system, you must install the following patch cluster:
•
Solaris 8 Kernel Patch 27 or later (108528-27 or higher)
(previously was 108528-13)
After you have installed the 108528-27 or later cluster, install the following additional patches if they were not already installed as part of the cluster:
Required Patches
Enter the Solaris showrev -p command to display the patches which are already installed in the CWM workstation.
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=homeUse the search facility on the SunSolve site to search for these patches, entering only the 6-digit patch ID number (do not include the 2-digit patch version number). The version number can be later than the one referenced below.
•
111626-01
•
111327-02
•
110945-02
•
110934-01
•
110898-02
•
110700-01
•
110670-01
•
109326-05
•
109147-37 (needed to resolve CSCej57997)
•
108993-49 (needed to resolve CSCej57997)
•
108652-35
•
108528-27
•
108434-18 (needed to resolve CSCej57997)
Recommended Patches
•
110951-01
•
110662-02
•
110615-01
•
110286-02
•
109324-02
•
111085-02
To obtain these patches, go to the Sun Microsystems SunSolve online patch page at the following URL:
http://sunsolve.Sun.COM/pub-cgi/show.pl?target=patches/patch-access
Note
Obtaining several of these patches may require that you have a service contract with Sun.
CWM Software Release 15.0.00 Packaging
Refer to the "CWM Release 15.0.00 Patch 5 Installation" section for the contents of Patch 5. The following is the list of CDs for the CWM 15.0.00 release:
When you order the CWM package, you receive the following 2 disks:
•
CWM Server. This CD contains the following:
–
CWM Server Software
–
INFORMIX Server Software Release 9.21.UC7XH
–
CWM Java Client Software
•
CWM Documentation CD. This CD contains the following:
–
Acrobat Reader 4.0
–
gzip
–
PDF copy of the CWM 15 documentation set
The Service Agent software is provided on a separate CD. This CD must be ordered separately from the CWM Release 15 Client/Server package CD set.
•
Service Agent CD. This CD contains the following
–
CWM Service Agent Software
The Standalone Statistics Collection Manager software is also on a separate CD. This CD must be ordered separately.
•
Standalone Statistics Collection Manager CD. This CD contains the following:
–
Standalone SCM Software with WANDEST Client Software incorporated
–
Informix Server Software Release 9.21.UC7XH
The Standalone Statistics Collection Manager software also includes the RTM Proxy for SCM Application on a separate CD. This CD is included only when you have ordered the Standalone Statistics Collection Manager software.
•
RTM Proxy for SCM Application CD. This CD contains the following:
–
RTM Proxy for SCM Application Software
Note
Refer to the CWM Installation Guide, Release 15 for instructions on installing the RTM Proxy for SCM application from the CD. The RTM Proxy for SCM application is only meant to be installed with the Standalone Statistic Manager. It is not for systems with the Service Agent. If you already have the Service Agent software installed and you attempt to install this application, you will see errors on the console because the ~/config/process.conf file will have duplicate entries for the RTM Proxy.
The WANDEST Release 2.5 software is provided on two separate CDs. Each CD is ordered separately.
•
WANDEST Release 2.5 Server CD
–
WANDEST Server Software, Release 2.5
•
WANDEST Release 2.5 Client CD
–
WANDEST Client Software, Release 2.5
HP OpenView Requirements
The CWM 15 release works with HP OpenView Release 6.2, 6.3, or 7.0 for Solaris 8.
Note
You must purchase HP OpenView 6.3 or 7.0 directly from Hewlett Packard.
For HP OpenView installation requirements and procedures, please refer to the HP OpenView Network Node Manager Products, Installation Guide (Part Number J1136-90000 from HP).
HP OpenView Release 6.2, 6.3 or 7.0 is not bundled with CWM CDs. You must order HP OpenView separately. HP OpenView is only used for viewing the Event Log. It is not required for any other CWM procedures.
Informix Requirements
The CWM 15.0.00 release uses Informix release 9.21.UC7XH for database operations. The Informix software is bundled with CWM software on disk 1 of the CWM CD package. The Informix program is automatically installed during CWM installation.
Supported Hardware
This section provides information about the hardware supported by the CWM 15.0.00 release.
Existing Hardware
Table 5 lists the existing hardware supported by CWM Release 15.0.00.
Certified Releases
The following releases were tested with CWM Release 15.0.00. Patch 5:
•
BPX/IGX Switch Software:
–
Switch Software 9.4.12
–
Switch Software 9.3.51
–
Switch Software 9.2.47
•
MGX 8230/8250/8850 (PXM1) Switch
–
MGX 1.3.12
–
MGX 1.3.11
–
MGX 1.2.23
–
MGX 1.2.13 and 1.1.34
•
MGX 8950 (PXM45) Switch
–
MGX 5.0.20
–
MGX 4.0.17
•
MGX 8850 (PXM45) Switch
–
MGX 5.0.20
–
MGX 4.0.17
–
MGX 3.0.25
–
MGX 3.0.20
•
MGX 8880 (PXM45) Switch
–
MGX 5.0.70
•
MGX 8850/8830 (PXM1E) Switch
–
MGX 5.0.20
–
MGX 4.0.17
–
MGX 3.0.25
•
BPX SES Shelf
–
SES 4.0.15.20
•
MGX 8220 Shelf
–
MGX 8220 5.0.20
–
MGX 8220 4.1.12
•
VISM-PR
–
VISM-PR 3.3.10
–
VISM-PR 3.2.11
–
VISM-PR 1.5.10 (certified with MGX 1.1.34 only)
•
VXSM
–
VXSM 5.0.20
–
VXSM 5.0.70 (certified with MGX 5.0.20 onlly)
–
VXSM 5.0.00
•
RPM-XF
–
Cisco IOS 12.3(7)T3
–
Cisco IOS 12.3(2)T5
•
RPM-PR
–
Cisco IOS 12.3(7)T3
–
Cisco IOS 12.2(8)T4
New Features and Enhancements in CWM Release 15
Features Introduced in CWM Release 15.0.00, Patch 5
•
Additional queue related details will be logged in snmpd.log. For example, warning messages will appear when 75% or 90% of thread usage is surpassed. Also if usage drops from 75% or 90% to below 75% or 90%, respectively, then a message will be logged.
•
Ability to suppress traps using ntsControl.
Sometimes certain network problems may send out a blast of traps from a set of nodes which may flood CWM causing other nodes not to function properly. It may be useful to suppress these traps from the troubled node and allow proper management of the rest of the network. You can then enable the traps at a later point once the situation is corrected on the troubled nodes.
ntsControl is a client program for NTS which gives certain control APIs for NTS. This would be used to suppress some traps from NTS from flowing to other CWM modules (the traps will still be sent out to HPOV and RTMProxy). To use ntsControl:
> ntsControlpit - Print the list of traps being ignored with NODE ID.it - Ignore a trap for a certain node.dt - Stop Ignoring a trap for a certain node.Ready (? for help) > itAvailable Nodes:1 2 5 7 8 9 10 11 13 14 15 17 19 20 2122 23 24 26 27 28 33 34 36 38 39Enter CWMNodeID for node to suppress traps: 11Enter the trap number to ignore: 60101Ignore trap 60101 for 11...OkIn the above example, NTS will stop forwarding trap number 60101 from nodeid 11 to all CWM modules, except RTMProxy and HPOV. The trap can still be seen in these two modules.
To re-enable the trap so that it is forwarded to other CWM components use the "dt" command for ntsControl.
•
ShelfIntegrated alarms for MGX nodes in the controller card will show in the Chassis View if the flag CHASSIS_SHOW_ORIGINAL_ALARMS is included in the /usr/users/svplus/CMSCClient.conf file.
Features Introduced in CWM Release 15.0.00, Patch 4
This section describes the new features introduced in Cisco WAN Manager Release 15.0.00, patch 4.
•
Support for assigning user profiles permission to change the node name.
Node Rename feature allows users with appropriate authority level to change the node name. If the user has the permission to change the node name and the newly selected node name is already in use, then an error message is displayed and the operation is not allowed. The Node Rename permission is independent of the 'modify' permissions and it applies only to the Configuration Center.
Installation, Security Manager and ConfigurationCenter have been modified as follows:
Installation changes:
–
Node name provisioning option is given to the adminprofile only.
–
New input panel to enable Node Name Provisioning. Profiles are updated with appropriate values that the user designates.
–
Node Name Authority default parameters for adminProf profile is `selected and userProf1 profile is `unselected'.
Security Manager application enhancements:
–
Security Manager profiles are extended with an additional Node Name Authority parameter for Configuration Center.
–
All profiles (both existing and new) will have the Node Name Authority parameter.
–
Node Name Authority parameter is independent of all other profile attributes including the modify attribute.
–
Node Name Authority default parameters for adminProf profile is `selected and userProf1 profile is `unselected'.
When Node Name Authority is 'selected', the profile allows any user bound to it to use Configuration Center to edit the node name.
When Node Name Authority is 'unselected, the profile does not allow any user bound to it to use Configuration Center to edit the node name. The node name in Configuration Center will be disabled (grayed out) and will be a read only attribute.
For any newly created profiles, the Node Name Authority parameter default setting will be set to 'unselected'. However, the Admin user will be able to change the settings.
–
Any user bound to the new profile will be able to edit the node name based on the current 'Node Name Authority' parameter setting in the new profile.
Configuration Center enhancements:
–
Node Name Authority parameter is independent of the 'modify' permission and it applies only to Configuration Center.
–
Configuration Center will use the Node Name Authority parameter setting to enable or disable the editing capabilities of the Node Name UI field in Configuration Center. If the user has permission to edit the node name then the node name UI field is enabled. Otherwise, it is disabled (grayed-out).
–
If the user has the permission to change the node name and the newly selected node name is already in use, then an error message is displayed and the operation is not allowed.
•
Support for 53-byte conversion factor.
Configuration Center allows users to enable the cps to Kpbs conversion (default is cps). For the ATM connections, the conversion factor has been extended to support both the 48 byte as well as 53 byte cells.
Configuration center will use either the 48 byte or the 53 byte conversion based upon the selected conversion-factor in the CMSCClient.conf file.
–
If the USE_53_BYTE_CONVERSION_FACTOR is set to 'false', a conversion factor of 384 (48 bytes; 48 * 8) is used (1 cps = 384 bps).
–
If the USE_53_BYTE_CONVERSION_FACTOR is set to 'true', a conversion factor of 424 (53 bytes; 53 * 8) is used (1 cps = 424 bps).
Note
For existing connections created using a 48 byte conversion factor; if the user changes the conversion factor to 53 byte conversion, a different kbps value other than the original value (which used the 48 factor) will be shown to the user since the connection was originally provisioned with a 48 byte conversion factor.
Note
The 53 byte conversion applies only to the new connections and the modifications of existing connections.
Features Introduced in CWM Release 15.0.00, Patch 3
This section describes the new features introduced in Cisco WAN Manager Release 15.0.00, patch 3.
•
MGX 8850 and MGX 8830 Release 5 (PXM45-based nodes and PXM1E-based nodes)
–
CWM 15.0.00 Patch 3 adds support for the MPSM-T3E3-155 MultiLink Frame Relay (MLFR) feature on switches running Release 5.0.20 software.
•
MGX 8880, MGX 8850, and MGX 8830 Release 5 nodes (both PXM1E-based and PXM45-based nodes)
–
CWM 15.0.00 Patch 3 adds support for collecting bulk statistics from the VISM-PR running Release 3.3 of the VISM software. None of the other new 3.3 features are supported
•
MGX 8850, 8250, and 8230 Release 1.3.10 (PXM1-based nodes)
–
MGX 8850, 8250, and 8230 (PXM1-based nodes) running Release 1.3.10 will recognize both the VISM and VISM-PR running Release 3.3 of the VISM software, but the new 3.3 features are not supported on PXM1-based nodes.
•
Support for VXSM Release 5.0.20
–
CWM 15.0.00 Patch 3 adds support for VXSM Release 5.0.20 on PXM45-based switches running Release 5.0.20 software.
Features Introduced in CWM Release 15.0.00, Patch 2
This section describes the new features introduced in Cisco WAN Manager Release 15.0.00, patch 2.
•
MGX 8950 Release 5 (PXM45-based nodes)
–
AXSM-XG 16-port OC-3 service module can link to MGX PXM1-based switches as a feeder
CWM 15.0.00 Patch 2 can discover the configuration where MGX PXM1-based switches are used as a feeder to the AXSM-XG 16-port OC-3 service modules on the MGX 8950 shelf. Connections can be set up between the termination points on these feeders and other connection endpoints on the MGX 8950 or on another feeder shelf.
–
Support for redesigned RPM-XF back cards
With the release of CWM Release 15.0.00, patch 2, the new RPM-XF back cards that are designed to work with the MGX 8880 are now supported.
–
Support for the preferred routes feature on RPM-XF
With the release of CWM Release 15.0.00, patch 2, configuration of preferred routes for the RPM-XF for XPVC connections is now supported.
The pref_route_id and direct_route_flag fields have been added to the rpm_connection table. The pref_route_id field indicates the associated preferred route for the particular connection.
The direct_route_flag field indicates whether or not the connection is directed. If this flag is set to true, then the associated SPVC will be routed only to the preferred route. If the preferred route is not available, the connection is not routed on any alternative route and then is flagged as failed. If the direct_route_flag parameter is set to false then the associated SPVC will also be routed to the preferred route, but if the preferred route is not available, alternative routes will be considered as per PNNI routing policies.
Service agent support is provided by adding RPM-XF support to the cwmConnPrefRouteId (for PNNI XPVC segments only) and cwmConnDirectRoute objects in the cwmConnTable in CWM Release 15.0.00, patch 2.
•
MGX 8880 Release 5 (PXM45-based nodes)
–

