Table Of Contents
Release Notes for Cisco WAN Manager Release 15.1.00
These release notes are part OL-6495-01 Rev. A0, January 25, 2005
Cisco WAN Manager Release 15.1.00 software supports the following Cisco products as of 01/25/05:
•Cisco MGX 8850 PXM45-based products running software Releases 3.0.20 through 3.0.25, 4.0.00 through 4.0.17, 5.0.00 through 5.0.20, or 5.1.00.
•Cisco MGX 8880 PXM45-based products running software Releases 5.0.00 through 5.0.20, or 5.1.00.
•Cisco MGX 8950 PXM45-based products running software Releases 3.0.20 through 3.0.25, 4.0.00 through 4.0.17, 5.0.00 through 5.0.20, or 5.1.00.
•Cisco MGX PXM1E-based products (8830 and 8850) running software Releases 3.0.20 through 3.0.25, 4.0.00 through 4.0.17, 5.0.00 through 5.0.20, or 5.1.00.
•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.21, or 1.3.00 through 1.3.11.
•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.10.
•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 ContentsRequired Patches 7Recommended Patches 8WANDEST 2.6-Specific Enhancements 19
This document contains the following sections:
In addition to the CWM platform requirements listed in the Cisco WAN Manager Installation Guide, Release 15.1, also consider the following:
•CWM 15.1 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.1. 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 2GB partition chunks are required to be added to Informix. Refer to the Cisco WAN Manager Installation, Release 15.1, OL-6259-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.
•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.
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.
Collecting statistics for four million endpoints with 5 statistics per endpoint requires 80 GB 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:
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
Use 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.
To obtain these patches, go to the Sun Microsystems SunSolve online patch page at the following URL:
Note Obtaining several of these patches may require that you have a service contract with Sun.
CWM Software Release 15.1.00 Packaging
The following is the list of CDs for the CWM 15.1.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.4
–CWM Java Client Software
•CWM Documentation CD. This CD contains the following:
–Acrobat Reader 4.0
–PDF copy of the CWM 15.1 documentation set
The Service Agent software is provided on a separate CD. This CD must be ordered separately from the CWM Release 15.1 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.4
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.1 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.6 software is provided on two separate CDs. Each CD is ordered separately.
•WANDEST Release 2.6 Server CD
–WANDEST Server Software, Release 2.6
•WANDEST Release 2.6 Client CD
–WANDEST Client Software, Release 2.6
HP OpenView Requirements
The CWM 15.1.00 release works with HP OpenView Release 6.3, or 7.0.
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.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.
The CWM 15.1.00 release uses Informix release 9.4 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.
This section provides information about the hardware supported by the CWM 15.1.00 release.
Table 5 lists the existing hardware supported by CWM Release 15.1.00.
Table 6 lists the new hardware supported in CWM Release 15.1.00.
The following releases were tested with CWM Release 15.1.00:
•BPX/IGX Switch Software:
–Switch Software 9.4.10
–Switch Software 9.3.47
•MGX 8230/8250/8850 (PXM1) Switch
–MGX 1.2.13 and 1.1.34
•MGX 8950 (PXM45) Switch
•MGX 8850 (PXM45) Switch
•MGX 8880 (PXM45) Switch
•MGX 8850/8830 (PXM1E) Switch
•BPX SES Shelf
•MGX 8220 Shelf
–MGX 8220 5.0.20
–MGX 8220 4.1.12
–VISM-PR 1.5.10 (certified with MGX 1.1.34 only)
–Cisco IOS 12.3(11)T3
–Cisco IOS 12.3(7)T3
–Cisco IOS 12.3(2)T7
–Cisco IOS 12.3(11)T3
–Cisco IOS 12.3(7)T3
–Cisco IOS 12.3(2)T7
New Features and Enhancements in CWM Release 15
Features Introduced in CWM Release 15.1.00
This section describes the new features introduced in Cisco WAN Manager Release 15.1.00.
•MGX 8850 and MGX 8830 Release 5 (PXM45-based nodes and PXM1E-based nodes)
–CWM 15.1.00 adds support for the MPSM-T3E3-155 MultiLink Frame Relay (MLFR) feature on switches running Release 5.0.20 or 5.1.00 software.
•MGX 8880, MGX 8850, and MGX 8830 Release 5 nodes (both PXM1E-based and PXM45-based nodes)
–CWM 15.1.00 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.
WANDEST 2.6-Specific Enhancements
•Selectable Triggers for Database Tables
In the WANDEST releases before Release 2.6, every table within the stratacom database was accessed by WANDEST, regardless of whether you used the table or not. Now you can select the tables you need. Refer to the WANDEST Installation and Reference, Release 2.6 for more information on setting up this feature.
Unsupported Features and Known Feature Limitations in CWM Release 15.1.00
The following features are not supported in CWM Release 15.1.00:
CID level traps are not sent to CWM to prevent potential trap flooding.
CID level statistics are not available in bulk statistics file format from the VXSM modules.
XPVC support on the FRSM T3E3 in PXM45-based switches has not been tested.
Several windows display fields relating to the MPSM-T3E3-155 MultiLink Frame Relay (MLFR) feature, which is not currently supported.
When managing VISM service modules that are running Release 3.2.10, CWM only supports the Release 3.2 features.
The following features introduced in VISM 3.1 are not accessible from CWM:
•T.38 Fax Relay
The CWM database is not populated with the MPG configuration data. Instead, the Service Agent accesses the configuration directly from the switch.
The following cards are not supported by CWM 15.1.00:
•The BME card is not supported.
•The FRSM12 service module is not supported.
•The URM, ARM, FRM, BTM, ALM and CVM service modules are not supported.
If you have these unsupported service modules you can either stay with CWM 12 or upgrade to the newer supported service modules to take advantage of the new CWM 15.1 GUI enhancements.
1. Cisco does not recommend pointing multiple CWM workstations at the same gateway node.
2. CWM does not support use of the Korn Shell.
3. When /usr/users becomes 100 percent full, the orbix processes are not able to write to the disk and thus, cannot continue operations.
Correct the problem by first freeing up some disk space in /usr/users, then restarting the orbix processes and CWM using the following procedure:
Step 1 Stop the core.
Step 2 Exit out of the CWM prompt.
Step 3 Run the stoporbix2000 script.
Step 4 Type CWM.
You should see "Starting Orbix..." in the ~svplus/log/.startStopOrbix.log file.
Step 5 Start the core.
4. When the client machine cannot be pinged from the server the following message may be seen on the CWM workstation:Exception raised while calling activateLease on pseudoServer.IT_ATLI_IOP:CONNECTION_CREATION_TIMEOUT
The error message is printed when the server tries to contact the client, but is not able to. The call is initiated by the GUI client in order to activate the lease plug-in that the client uses to detect a server crash.
The problem is with the client machine DNS setup. The client machine cannot be pinged from the server.
The DNS is configured so that the client can communicate with the server, but when the server tries to contact the client machine it fails.
The resolution is to make sure the client machine is pingable from the CWM workstation.
Possible reasons for the server not being able to ping the client are:
–There may be a firewall on the client PC that prevents it from being seen from outside.
–The network routing from the server to the client is not set up properly.
5. When the SSM (Standalone Statistics Manager) is installed with the SCM Gateway configuration, the SCM GUI does not open when the primary SSM and secondary SSM are started simultaneously (or within a time gap of 30 seconds to 1 minute).
Avoid this problem by waiting 2 to 3 minutes after starting core in the primary SSM before starting core in the secondary SSM in the SCM Gateway configuration.
6. When there is a shortage of shared memory on the workstation, the Informix engine may generate an operating system error. The following example from the online.log shows this error:shmat: : operating system error18:45:49 shmat: : operating system error18:45:57 Error writing '/tmp/shmem.1fd4555c.0' errno = 418:45:57 mt.c, line 10260, thread 7148, proc id 1008, errors occurred during mt_notifyvp.
When this error occurs, the statsparser is not able to perform any database related operations.
The error can be resolved temporarily by changing the /etc/system configuration as follows:forceload: sys/shmsysforceload: sys/semsysset shmsys:shminfo_shmmax=1073741824set semsys:seminfo_semaem=16384set semsys:seminfo_semmap=5000set semsys:seminfo_semmni=8192set semsys:seminfo_semmns=8192set semsys:seminfo_semmnu=8192set semsys:seminfo_semume=256set semsys:seminfo_semvmx=50000set shmsys:shminfo_shmmin=256set shmsys:shminfo_shmmni=32000set shmsys:shminfo_shmseg=256set semsys:seminfo_semmsl=100
The long-term solution is to increase the amount of memory to support 2 million connections consistently.
7. When using in-band management, only 50 K connections are supported on the BPX-SES. To manage 100 K connections on the BPX-SES, set up CWM for out-of-band management.
8. If an ATM IP interface (also called In-band interface) is being used to manage the switch from the CWM, not all node bring-up traps may be received by the CWM. The ATM connections required for in-band management may take time to get routed on node bring-up and are hence not available for trap delivery at this initialization time. If this initialization time is an issue, the workaround is to configure CWM for out-of-band management.
9. Allow a 2 to 3 minute period between enabling or disabling statistics operations on the same BPX or IGX node. Whenever enabling/disabling of statistics is done on a BPX or IGX node, and the switch is in the process of configuring statistics, doing a second enabling/disabling of statistics will fail.
10. If the Start Collection process on the SCM GUI takes a long time, investigate whether collection was started with an IP address that was not reachable. Either in-band or out of band was not reachable. Start collection with a reachable IP address. If the in-band IP address is reachable then start collection with in-band IP address. If out of band is reachable, start collection with out of band.
11. The SSM statistics database can go out of sync with node_ids on CWM after a coldstart -F is executed on the server. Stop collection and disable collection before doing a coldstart -F to ensure that the node IDs remain consistent. A CWM-to-CWM gateway must be enabled to ensure uninterrupted statistics collection.
12. When the persistent topology feature is enabled, to decommission a node in the network and take it out of the topology you must delete the node from the persistent topology data using the switch CLI. To decommission a node or to delete a trunk from the PNNI network, you must delete the entry from the persistent gateway nodes.
13. To ensure all CWM servers have the same XPVC Preferred data, CWM-to-CWM gateway must be enabled; otherwise, you must manually propagate the data to all CWM servers.
14. On MGX PXM1-based feeders in the BPX network, VISM or VISM-PR terminated XPVCs can only connect to the AUSM service module. No such restriction exists for PXM1E-based or PXM45-based nodes.
15. Manual node resync may appear to have failed due to the GUI timing out for PXM45/PXM1E-based Cisco MGX nodes with many connections (for example, 400K DAX endpoints).
16. To correctly manage feeder nodes after they have been moved, you must first delete all trunks from the old node using the CLI before adding the feeder back onto the system.
17. When a back card is removed when there is no provisioning on the front card, the card alarm status reported by CWM will be inconsistent with what the switch reports. CWM reports a major alarm with the description "Back Card; not present" whenever a back card is removed. However, the switch may not show an alarm if there is no provisioning on the front card. If there is no provisioning on the card, manually clear the major alarm after determining this is not a real alarm condition.
18. After executing a clrsmcnf command for AXSM from the switch CLI, ChassisView shows the AXSM front card once the card is active, but no back card is found. To ensure that ChassisView recognizes the back card again, you must execute a first level manual node resync.
19. RPM-PR and RPM-XF ports/subinterfaces must be configured with a number less than 32767. If you have configured any ports or subinterfaces with a number greater than 32767, you must delete them and then re-add them using a number less than 32767.
20. If you register an SNMP Manager with the SNMP Agent without changing the bit-mask (if you accept the default of FFFFFFFFFFFFFFFF), you receive all SNMP traps, including 25302 and 25303.
If you register the SNMP Manager with a non-default bit-mask because you do not want certain groups (Example: FFFFFFFFF10701555), then you do not receive trap 25302 and 25303, even though you have registered for that group.
If you deselect a currently undefined group like group 28, which is a bitmask of FFFFFFFFEFFFFFFF, you can then add traps 25302 and 25303 by editing the trap_filter.conf file and adding the following lines to GROUP 20 # Network Connectivity Status Change Traps:
21. Preforming a switchcc command on a controller card in an IGX or BPX node forces CWM to resync with the node again. This causes a delay in receiving status information.
22. Changing the line type/payload type/medium type of VXSM-4OC3 causes CWM to perform a whole card resync. This card resync will occur when you do any of the following:
–Change the medium type between SONET and SDH for SONET physical line
–Change the payload type between T1 (VT 1.5 VC 11) and E1(VT 2 VC 12) for STS path or STM (Au) path
–Change the payload type between T1 (VT 1.5 VC 11) and DS3 for STS path
–Change the tributary path between Au4 and Au3 for STM path in SDH medium
A whole card resync takes several minutes to complete.
23. If you remove and then immediately add back the same IGX feeder while CWM is running, CWM establishes two LINK 0's with the node. This is treated as a delete and the node will be deleted.
In this situation, Cisco recommends you either remove and add the feeder while CWM is down, or, after adding the feeder, restart CWM.
24. Changes to the node name from the Configuration Center are updated automatically in the Tree View and in the Inspector View. However, the node name in the title bar of the internal frame does not update automatically. To change the title bar of the internal frame to reflect a change to the node name, close the internal frame and re-open it.
You can also update the attribute values in the internal frame by using the Refresh button of that internal frame.
25. After it is modified using snmpset, the Line Send parameter LineSendCode is not getting updated by the database, which shows the parameter as inapplicable (shows the value as -1). Refer to CSCin50480 for more information.
26. The "l_network_id" field in the connection segment or port tables may not be populated correctly. To ensure collection of an accurate network ID, use the "netw_id" field from the "node" table.
27. If you are managing a PXM45-based MGX node running any supported release earlier than 4.0.10 CWM Release 15.0.00 will not populate the "peripheral" table.
28. If you are managing a PXM45-based MGX node running 4.0.10 or any supported release later than 4.0.10 the "status" field in the "peripheral" table will only be populated or updated during node resync.
29. If you are managing a PXM1-based MGX node, the "status" field in the "peripheral" table will not be populated.
30. If the log level for CWM EM module is set too high or above production default value and there are a lot of configuration changes on the switch during warm start, the sync up performance will be impacted during warm start.
31. SmartLogging is a special feature for CWM debugging available when the log level is set to Level 2. It will dump a configurable number of detailed log messages to log files for each Level 2 log message.
For example, when SmartLogging is enabled, an SNMP failure which triggers a Level 2 log message will cause a dump of log messages at all levels immediately prior to and following this event. The SmartLogging feature may have performance impact, due to excessive log messages. It should be disabled in normal operation and enabled only when needed for special investigation.
32. The Forced Deletion feature does not support XPVC connections. XPVC connections cannot be force deleted.
33. Using the Forced Deletion feature to remove an unused connection descriptor only removes the unused descriptor from the workstation it is performed on. Other gateway workstations will still show the descriptor.
You must force delete the unused descriptor at each gateway workstation to clear it completely.
34. Occasionally, when you move linked nodes around in the Topology screen, the link does not automatically follow the nodes. When this happens, it looks like the link is not connected to the nodes. The workaround is to either move the affected nodes around within the window or refresh the Topology screen Once the screen refreshes, the link will automatically appear connected to the appropriate nodes again.
35. Using the "Group Nodes" feature only affects your view of the networks. Other users (even those who log into your workstation) will not see the groups you have made.
36. After a previously saved configuration file is loaded using the Config Save & Restore feature of CWM, the Tree View continues to show some ports that are not in the restored configuration file. Attempting to configure these ports results in an error. The workaround is to perform a manual node resync.
37. When setting up VISM connections the VPI value in the VPI/VCI Selector window defaults to zero. You must manually enter the VPI value, as zero is invalid. The range for the VPI value for VISM cards is one through the highest available slot number on the node.
38. Ports on PXM45-based nodes which are associated to a trunk display as Trunk Ports, however, ports that are carrying signalling protocol information display as User Ports. Because they are carrying information, you cannot provision connections on these ports. Attempting to do so results in an error being displayed. Choose another port.
39. Virtual Ports on BPX are displayed in the Tree View application under the physical Line section as physicalPort.virtualPort.
40. The PNNI ports on the PXM1 card of an SES node are not displayed in the Tree View application.
41. The administrative state of the PNNI ports is not aggregated into the total administrative state of the port. The Inspector View application shows both the total administrative state of the port and the administrative state of the PNNI ports as two separate items.
42. The Loss of Cell Delineation alarm on AXSME, AXSM-XG, and/or MPSM-OC3 cards may not get propagated from the switch to CWM. For the AXSM cards, a line/path alarm will be present, but the MPSM-OC-3 card could have an LOCD alarm triggered without any line/path alarm present. The line would show in CWM as clear, while actually being in alarm.
43. With MPSM-OC3 cards, after you replace an OC-3 back card with a DS3 or vice versa you need to do a coldstart.
44. Occasionally, WANDEST fails installation directly after CWM 15.1 and Service Agent installation on a workstation running Solaris 2.9. The following error message appears:
"Informix is not in on-line mode".
The workaround is to install WANDEST using the C shell (csh).
45. In the Connection Manager, the Service Type field displays some non-applicable service types for SPVCs. CWM will display an error if you select a non-applicable service type.
46. After adding a connection loopback through the Diagnostic Center GUI, there is no indication that the connection is in loopback. You have to use the CLI to verify that the connection is in loopback.
Configuration Center Limitations
When the connection modify dialog box is already open, another user can delete the connection using the CMGUI delete option.
The Connection Management section of the Configuration Center GUI for preferred route displays all available trunks without considering the traffic class. As a result, it is possible to set a preferred route for a CBR connection traversing trunks that do not support CBR traffic.
While adding connections originating and terminating on the same feeder nodes (MGX8220 only), CWM will treat these connections as three segment connections and will add three segments (two on the same feeder node, one on the routing node) to realize this connection. This is because the ASC cannot route traffic. If you wish to pass traffic between two cards in an MGX 8220 chassis, regardless of how connectivity is added, the actual physical connectivity that has to be built is a connection from each endpoint to the ASC and then a looping segment on a BPX.
RPM on PXM1-based MGX 8850/8230/8250 provisioning is done using telnet since the RPM does not support SNMP SETs. This should be transparent in daily operation. For more details, please refer to the specific RPM switch CLI release notes.
Occasionally, when the databroker is busy, while deleting SPVC connections on a PXM1E-based node the following error message may display:
error "can not delete connections. Failed to communicate with databroker".
This error message can safely be ignored, because the connections are correctly deleted on the switch.
HP OpenView Limitations
All event messages are displayed in the HP OpenView Event Browser window. There is a limit of 2000 pending messages on the Event Browser. If there are more than 2000 messages to be processed and displayed by the Event Browser, it may exit.
The WAN network icon in the network node manager is no longer automatically created when running CWM 15. Use the Network Monitor map instead.
Issues with the CWM 15 Statistics Collection Manager
To collect connection statistics, statistics need to be enabled on the individual connections by setting the stats enable flag to true on each connection. If the user only enables connections statistics on SCM but does not set the stats enabled flag to true on the connection, the statistics will not be collected for that connection. Because there is no mechanism or warning to the user to have this enabled on the connections, CWM will not display an appropriate error message.
When enabling statistics by selecting multiple nodes at a time in the SCM, enabling statistics on all the nodes only succeeds when either all of the nodes have the same card types or all of the nodes only contain cards of the same family.
Occasionally, when high connection counts are enabled on the SES, and statistics collection is enabled, the SES node is not getting synced up. The workaround is to disable statistics collection in the SES. Refer to CSCdw32076 for more information.
The statistics collection manager retrieves SPVC connection statistics data from BPX-SES nodes, however, only 15 minute collection buckets are supported on the SES.
The same limitation of only 15 minute collection buckets applies for MGX 8850 PXM45-based nodes with AXSM. There is no such limitation for AXSM-E.
Only 15 minute collection buckets are supported for PNNI statistics.
Peak statistics are not supported for PNNI statistics.
If the PXM45 release is less than 4.0(0.0) PNNI historical statistics can not be enabled.
The BPX-SES does not support PNNI statistics collection.
Statistical Alarms for lines on PXM45-based MGX nodes are not supported in CWM.
The following statistics for SRM and SRM/E T3 lines.can be enabled on the switch, but are not supported by SCM:
HP OpenView is supported on StandAlone Statistics Manager (SSM). SSM processes generate CWM traps.
Stats Parsing is only supported for the "statsdb" database on the SSM machine. Stats Parsing is not supported for the "stratacom" database on the SSM machine.
At least one CWM must be up and running, with the nodes synced up, for SSM to work normally. SSM uses the CWM server workstation to get traps while enabling statistics for cellbus-based service modules on MGX 8850 and PNNI statistics on BPX.
The WANDEST server must be up and running on the CWM server workstation. SSM gets the node, node_info, card, network, rsc_part, bis_object tables from the CWM server workstation using WANDEST.
If the statsmaster SSM/CWM is down or unreachable in a SCM Gateway setup, the statsmaster must be changed on the switch to a machine that is up. The statsmaster is needed for SCM statistics enabling/disabling.
In an SCM Gateway setup with statistics collection going on, after switchover the old statistics data is not moved to the new Primary CWM/SSM machine.
SSM does not receive traps on Node/Card Deletion, so statistics collection must be stopped and disabled before deleting a node/card on the network. Also SSM does not receive traps on Node/Card Add messages, so the WANDEST upload must be received before the node/card can be seen in SCM GUI on SSM.
In SSM, statistics collection must be stopped and restarted after changing the node name or changing the node FTP password.
Limitations for CWM to CWM Communication
The Secondary CWMs have to wait for the Primary CWM to finish syncing up with the network. Trap 28075 (svDatabaseInSync) is sent when the Primary CWM has finished syncing up with the network.
All the CWM workstations managing the same network must have seed nodes or gateway nodes that have IP addresses within the same network. All the CWM workstations should not all point to the same gateway node, but the gateway nodes they point to should be on the same network.
If an IP address is entered as gateway in the network.conf file and the DNS entry is missing for the gateway node IP address, the Auto-Route network will not be discovered.
The Configurator can be started on either the Primary CWM or the Secondary CWMs, but Add, Modify, or Delete operations using the Configurator can only be performed on the Primary CWM.
All the CWM to CWM Communication limitations listed above also apply to SCM Gateway.
Network Monitor Limitations
In a single routing node PNNI network, the node is managed using the IP address specified in the network.conf file.
In the case of a PXM45-based or PXM1E-based MGX network, the PXM45-based or PXM1E-based MGX nodes are managed using the primary IP address. The primary IP address is specified using Option 7 or Option 8 (depending on chassis type) in the cnfndparms CLI command. Configure the trap IP with the primary IP. PXM1-based MGX nodes connected to PXM45-based MGX nodes are managed through the atm0 IP. If the atm0 is not set, then the LAN IP is used to manage the PXM1-based MGX nodes. Configure the trap IP accordingly using the cnftrapip command.
In CWM 15.0.00 and later, the SHOW_TOPO_VIEW flag in the CMSCClient.conf file is used to configure whether or not nodes and trunks are displayed in the topology display of the Network Monitor application at CWM startup.
SHOW_TOPO_VIEW 1 means when NWTopology opens, users can see nodes and trunks in the topology.
SHOW_TOPO_VIEW 0 means when NWTopology opens, users cannot see nodes and trunks in the topology.
In releases earlier than CWM 15.0.00, a flag named TOPO_SHOW_MAP in the /usr/users/svplus/config/CwmGs.conf file was used to configure whether or not nodes and trunks are displayed in the topology display of the Network Monitor application at CWM startup.
The TOPO_SHOW_MAP flag is obsolete. Use the SHOW_TOPO_VIEW flag in the CMSCClient.conf file instead.
CWM Release 15.1.00 adds the following new flags in the CMSCClient.conf file:
•SHOW_ROUTING_TRUNK_TREEVIEW True means that the TreeView will display the routing trunk folder in all applications. The routing trunk folder contains all the routing trunk information. The default is true. If you set the SHOW_ROUTING_TRUNK_TREEVIEW parameter to false, then the routing trunk information is not retrieved from the inventory server and the TreeView in all applications will not show the routing trunk folder.
•SHOW_SORTED_TREEVIEW True means that the TreeView in all applications will show sorted tree node names. The default is true. If you set the SHOW_SORTED_TREEVIEW parameter to false, then the tree node names will not be sorted in the TreeView for all applications.
•ACCESS_TROUBLE_TICKET_SEND_EMAIL True enables the Send button of the Trouble Ticket dialog in the Diagnostics Center application. The default is true. If you set the ACCESS_TROUBLE_TICKET_SEND_EMAIL parameter to false, the Send Button in the Trouble Ticket dialog in the Diagnostics Center application is disabled.
CWM 15 Notes and Cautions
Due to the asynchronous behavior of the ILOG client and server interaction, CWM client requests may be sent before the CWM server is ready. In this case, the following error message appears on the workstation screen:Ilb Error: Synchronous request to <unidentified actor failed by timeout>.
Note If the ILOG timeout situation persists for more than five minutes and the CWM workstation is not functioning normally, then a service call should be made.
Parameters displayed by the Network Monitor or Configuration Center that are not applicable to an element (for example, a line or a trunk) often contain the value -1. Treat this as the same as Not Applicable.
CWM 15.1.00 Server Installation or Upgrade
Note You can upgrade to CWM Release 15.1.00 from CWM Release 15.0.00 patch 3, or CWM Release 12.0.00 patch 3. To upgrade from an earlier release, refer to the CWM 15.1.00 release notes and the CWM Installation Guide, Release 15.1 (OL-6259-01).
The most current upgrade and installation information for CWM 15.1 is found in the CWM Installation Guide, Release 15.1 (OL-6259-01). A PDF copy of this document is on the CWM 15.1 Documentation CD.
Important Configuration Notes
This section provides important information about configuration.
Naming Managed Nodes
Each node name of all the nodes managed by CWM must be unique. Duplicate node names are detected if both node names are found in the PNNI networks. Duplicate node names are not detected if one node is in the AutoRoute network and the other node is in the PNNI network.
Core File Management
Core files used to be created without unique names, and overwritten. Now for each core dump a unique directory is created under ~svplus/corefilesdir/.
Each directory is named <Core.<processName>.<pid>.mmddHrMinSec.
Within these directories, the core file will be "<processName>.<pid>.mmddHrMinSec.core", the Information file with dmesg, onstat -d, pstack and other details will be named "<processName>.<pid>.mmddHrMinSec.info", and the corresponding log file(s) will be "<processName>.<pid>.log".
Cisco Info Center Version
The 15.1.00_SNMPAgent.tar.gz file contains the CIC36Pipp001CWM15.tar file, which contains rule files that are only compatible with CIC version 3.6.1. You need to install CIC 3.6.1 to use these rule files.
If you want to continue to use CIC version 3.6.0 or 3.5 with CWM 15.1.00, save and then apply the CIC36Pipp000CWM15 tar file that is available in the CWM15.1.00 SNMP Agent CD instead.
For more information on CIC, refer to the following URL:
The C-Note version supported by CWM 15.1.00 is 3.
The CWM core must be started and core processes should be up before the Orbix cmldomain services for C-Note are started.
Add the IP address of the C-Note workstation to the /opt/ssng/config/CMLLogin/SnmpPublisher.xml file by entering the following command:vi /opt/ssng/config/CMLLogin/SnmpPublisher.xml
The line you add should look like this:<ipAddress>172.28.140.218</ipAddress>
(You need to substitute the actual IP address of your C-Note workstation for the sample 172.28.140.218 address listed above).
Node Numbering for Release 9.4 IGX Feeder Nodes
When an IGX is added as a feeder to a SES/BPX or MGX node, it will have a default node number. This node number may not be unique within the network. If it is not unique then it needs to be modified to a unique node number by issuing the CLI command "rnmnd <x>" where x should be unique with respect to all other auto-route nodes. To find the other node numbers, use the CLI command "dspnds +n". Failing to do so, the CWM Databroker may have an incorrectly formed hybrid connection database, and the CWM GUI may show the connection as incomplete.
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 means of CWM to CWM communication.
The user_info and sec_profile tables will not get dropped when the coldstart command is executed during a coldstart. These tables can only be dropped by executing the coldstart command with the "-F" option.
The Security Manager GUI can be started from the Network Monitor main window in the primary CWM system.
The CWM user to be added to the database has to be a valid UNIX user, because when a user logs in to the CWM desktop, user authentication against UNIX gets performed. The CWM user's password needs to match the one defined in the UNIX system.
Beginning with the CWM 15.0.00 Patch 2 release, the ability to set permissions for adding, deleting or modifying network partitions or subnetworks is configurable using the Security Manager GUI.
After performing the creation of a new database by executing the coldstart script, if CWM is restarted (stop core and start core) before it is synchronized with the network, it will result in a database inconsistency. In this case, rerun the coldstart script to avoid database inconsistencies.
Note Do not use the SV+CreateDb tool for the above purpose.
When a Gateway node is upgraded or rebuilt, before CWM has synchronized up with the network, CWM must be cold-started (create CWM database and restart CWM). This is required to ensure CWM database consistency.
The user supplied network name can be up to 10 characters in length and should be alphanumeric characters only (no periods).
The asi_line table is populated with the 1-based port number and not the 0-based port number for IGX ports.
RPM Management Limitations
RPM-PR is not supported on MGX PXM1-based nodes managed by ChassisView in CWM 15. The applicable trap is missing so CWM cannot monitor the back card.
For both RPM and RPM-PR cards managed by ChassisView in CWM 15 that are in stand-by state, the card status displays as blue. For other types of cards, stand-by card status displays as yellow.
For both the RPM and RPM-PR card types hardware and firmware revisions are not populated in the database.
The RPM back card support feature is disabled by default. Customers interested in obtaining the RPM back card information should enable this feature by editing the emd.conf file before starting the CWM core. If this feature is enabled, the back card information is polled from the switch only during a coldstart or a manual resync. After the coldstart or manual resync completes, any changes to the back card configuration or status will not be updated until you execute another coldstart or a manual resync.
CWM does not distinguish between the Ethernet back card versions installed with the MGX-RPM-128M/B or RPM-PR. There is no functionality difference.
ChassisView Operation After Card and Line Switchovers
When two cards are in a redundancy relationship, the primary card (i.e. the logical slot) is used to display the ports and lines for all provisioning and troubleshooting activities, even if the primary slot becomes a standby. The secondary slot does not show any ports and lines under it even after it becomes active. Provisioning is only allowed on the working line of an APS pair, irrespective of whether that line is currently active or not. However, both the working and protection lines are monitored.
In ChassisView, the ports on the card only display if they are available. Ports do not display on the secondary slot, even after it becomes active. The backcard appears as blank, not with greyed out ports as in previous releases that used CiscoView for equipment management.
Equipment Management Configuration Notes
In the emd.conf file, the following two parameters will need to be customized depending on network.
The OORequest parameter defines the number of configuration files per node that can be requested at one time. You can request a maximum of 32 configuration files concurrently per node. The range is 1 through 32, and the default is 32.
The OOStart parameter defines the number of OOEMC child processes. The range is 1 through 25, and the default is 6.
All the PNNI nodes managed by CWM (PXM45-based 8950, 8880, and 8850 nodes, PXM1E- based 8950, 8850, & 8830 nodes, and BPX nodes with SES shelves) are distributed among OOEMC processes.
The number of nodes managed by a single process is computed by dividing the total number of PNNI nodes in the network by the number of processes is defined by OOStart. Let us name this computed number of nodes managed by a single process the MANAGED_NODE_COUNT.
Then, MANAGED_NODE_COUNT * OORequest must be less than or equal to 200.
This can be achieved by either increasing the OOStart or reducing the OORequest. The normal range of OOStart is 5-20.
If the OOStart parameter value is increased beyond 10 then the number of DMD processes has to be increased or a shared memory overflow will occur.
Network Monitor Server Configuration File (NMServer.conf)
There are two parameters (HELLO_EVENT_INTERVAL and EVENT_REDELIVERY_COUNT) in the NMServer.conf configuration file that are tied to the NMSERVER_DISCONNECT_TIMEOUT parameter in the CMSCClient.conf client configuration file.
The NMSERVER_DISCONNECT_TIMEOUT parameter value needs to be set to the same as the HELLO_EVENT_INTERVAL value times the EVENT_REDELIVERY_COUNT value. the range for HELLO_EVENT_INTERVAL is 0 through 600, the default is 60. The range for EVENT_REDELIVERY_COUNT is 0 through 10. The default is 3. The default for the NMSERVER_DISCONNECT_TIMEOUT parameter is 60 times 3 or 180.
If you change any of these parameters they must be adjusted so the HELLO_EVENT_INTERVAL value times the EVENT_REDELIVERY_COUNT value continues to equal the NMSERVER_DISCONNECT_TIMEOUT parameter value.
The Network Monitor Server configuration file (NMServer.conf) also contains the PERIODIC_RESYNC_INTERVAL parameter. This parameter defines the interval in hours between periodic resyncs. The range is 2 through 24, and the default is 8. You can also disable the periodic resync feature by setting the PERIODIC_RESYNC_INTERVAL parameter to 0.
Creating and Configuring a CWM Auto-Restart Shell Script
This section describes how to create a shell script that automatically starts the CWM core after a reboot. To create this shell script you need to use a text editor to create a new file containing the commands that you want the script to execute.
Using the vi Editor to Create Your Auto-Restart Shell Script
Follow the steps below to create a script that uses shell commands to automatically restart the CWM core after the workstation has been rebooted.
Step 1 Log in to the CWM workstation as user root$ su
Step 2 Change to directory /etc/rc3.d# cd /etc/rc3.d
Step 3 Create a shell script of the form: Snn<filename>, where nn is the relative sequence number for starting the job under
/etc/rc3.dby entering the following command# vi /etc/rc3.d/S99init_sv
Since this script does not currently exist, the vi editor will open on a blank line, waiting for you to enter the script commands.
Step 4 Create the shell script by entering the following lines:******************************************************************#!/bin/sh# Check if Informix configuration is going onwhile [ ! -z "`ps -ef | grep S98init_db | grep -v grep`"]doecho "Informix initialization in progress...." >> /usr/users/svplus/log/.start_stopCWM.logsleep 5done# Start Orbix E2A ... as svplusecho "Starting Orbix E2A ..." >>/usr/users/svplus/log/.start_stopCWM.logsu - svplus -c /usr/users/svplus/scripts/startorbix2000 >> /usr/users/svplus/log/.start_stopCWM.logsleep 5# Running Guard process ... as svplusecho "Running Guard process" >>/usr/users/svplus/log/.start_stopCWM.logsu - svplus -c /usr/users/svplus/scripts/Install/RunGuard &# Start CWM core process ... as svplussu - svplus -c /usr/users/svplus/scripts/start_SV+ &******************************************************************
Note To save your changes while using the vi editor, remember to press Esc, colon (:), then wq!.
Step 5 Provide execute permissions for
/etc/rc3.d/S99init_svby executing the following command# chmod 755 S99init_sv
Note In order to auto restart Informix after reboot, a shell script has been created automatically during the initial CWM installation. This script is called
/etc/rc3.d/S98init_db. You need to make sure that the filename of your newly created autorestart shell script has a script number (the second and third characters in the filename) greater than 98. Also, your newly created autorestart shell script can not have the same script number as any other script files in
For more information on configuring this feature, refer to the
SNMP Service Agent Release Notes
Trap Limitation with PXM1-based MGX Nodes
The type of traps collected by CWM from connection addition and modification on Cisco MGX PXM1-based nodes running release 1.3.00 and onwards can be configured using the following new CLI commands:
Use these commands to select either DEFAULT: the same legacy traps plus trap 50601 to be sent, or ENABLE: only trap 50601 to be sent for every connection addition or modification.
If the dspchantrapenbl CLI command is set to DEFAULT, you can use the cnfchantrapenbl ENABLE CLI command to change to only collecting trap 50601 while CWM Release 15.1.00 is running.
However, if you are currently only collecting trap 50601 (the dspchantrapenbl CLI command is set to ENABLE), and you decide to configure the node to send legacy traps for every connection addition or modification by executing the cnfchantrapenbl DEFAULT CLI command, all CWM workstations monitoring the node must be in shutdown state (the core should be stopped) before you execute the command.
To determine which CWM workstations are managing the node, run the dsptrapmgr command.
This section lists known and resolved anomalies in the Cisco WAN Manager 15.1.00 software and other associated software.
Known Anomalies in CWM 15.1.00 Software
This section lists known anomalies in CWM Release 15.1.00 software as of 01/25/05.
Anomalies Resolved in CWM 15.1.00 Software
All anomalies resolved in CWM Release 15.0.00 as of 01/25/05 that were applicable to CWM Release 15.1.00 are included in CWM Release 15.1.00. Table 8 lists externally found anomalies from CWM Release 15.0.00 as of 01/25/05 that were only resolved in CWM Release 15.1.00 software.
The following technical documents comprise the CWM 15.1 documentation set:
•Cisco WAN Manager Installation Guide, OL-6259-01
•Cisco WAN Manager User's Guide, OL-6257-01
•Cisco WAN Manager SNMP Service Agent, OL-6260-01
•Cisco WAN Manager Database Interface, OL-6261-01
•Cisco WANDEST Installation and Reference, Release 2.6, OL-6430-01
•Release Notes for Cisco WAN Manager, Release 15.1.00, OL-6495-01
PDF copies of the first five items in the CWM 15.1 documentation set are provided on the CWM 15.1 Documentation CD along with a copy of Adobe Acrobat Reader and Netscape Communicator 4.76 for use in reading the files.
Use the included
gziputility to decompress the .
gzfiles. The command is
These release notes are not available on the CWM 15.1 Documentation CD. They are available on-line at the following URL:
You can access the most current Cisco documentation on the World Wide Web at this URL:
Translated documentation is available at this URL:
You can submit comments electronically on Cisco.com. In the Cisco Documentation home page, click the Fax or Email option in the "Leave Feedback" section at the bottom of the page.
You can e-mail your comments to firstname.lastname@example.org.
You can submit your comments by mail by using the response card behind the front cover of your document or by writing to the following address:
Attn: Document Resource Connection
170 West Tasman Drive
San Jose, CA 95134-9883
We appreciate your comments.
Obtaining Technical Assistance
Cisco provides Cisco.com as a starting point for all technical assistance. Customers and partners can obtain online documentation, troubleshooting tips, and sample configurations from online tools by using the Cisco Technical Assistance Center (TAC) Web Site. Cisco.com registered users have complete access to the technical support resources on the Cisco TAC Web Site.
Cisco.com is the foundation of a suite of interactive, networked services that provides immediate, open access to Cisco information, networking solutions, services, programs, and resources at any time, from anywhere in the world.
Cisco.com is a highly integrated Internet application and a powerful, easy-to-use tool that provides a broad range of features and services to help you with these tasks:
•Streamline business processes and improve productivity
•Resolve technical issues with online support
•Download and test software packages
•Order Cisco learning materials and merchandise
•Register for online skill assessment, training, and certification programs
If you want to obtain customized information and service, you can self-register on Cisco.com. To access Cisco.com, go to this URL:
Technical Assistance Center
The Cisco Technical Assistance Center (TAC) is available to all customers who need technical assistance with a Cisco product, technology, or solution. Two levels of support are available: the Cisco TAC Web Site and the Cisco TAC Escalation Center.
Cisco TAC inquiries are categorized according to the urgency of the issue:
•Priority level 4 (P4)—You need information or assistance concerning Cisco product capabilities, product installation, or basic product configuration.
•Priority level 3 (P3)—Your network performance is degraded. Network functionality is noticeably impaired, but most business operations continue.
•Priority level 2 (P2)—Your production network is severely degraded, affecting significant aspects of business operations. No workaround is available.
•Priority level 1 (P1)—Your production network is down, and a critical impact to business operations will occur if service is not restored quickly. No workaround is available.
The Cisco TAC resource that you choose is based on the priority of the problem and the conditions of service contracts, when applicable.
Cisco TAC Web Site
You can use the Cisco TAC Web Site to resolve P3 and P4 issues yourself, saving both cost and time. The site provides around-the-clock access to online tools, knowledge bases, and software. To access the Cisco TAC Web Site, go to this URL:
All customers, partners, and resellers who have a valid Cisco service contract have complete access to the technical support resources on the Cisco TAC Web Site. The Cisco TAC Web Site requires a Cisco.com login ID and password. If you have a valid service contract but do not have a login ID or password, go to this URL to register:
If you are a Cisco.com registered user, and you cannot resolve your technical issues by using the Cisco TAC Web Site, you can open a case online by using the TAC Case Open tool at this URL:
If you have Internet access, we recommend that you open P3 and P4 cases through the Cisco TAC Web Site.
Cisco TAC Escalation Center
The Cisco TAC Escalation Center addresses priority level 1 or priority level 2 issues. These classifications are assigned when severe network degradation significantly impacts business operations. When you contact the TAC Escalation Center with a P1 or P2 problem, a Cisco TAC engineer automatically opens a case.
To obtain a directory of toll-free Cisco TAC telephone numbers for your country, go to this URL:
Before calling, please check with your network operations center to determine the level of Cisco support services to which your company is entitled: for example, SMARTnet, SMARTnet Onsite, or Network Supported Accounts (NSA). When you call the center, please have available your service agreement number and your product serial number.
CCSP, the Cisco Square Bridge logo, Follow Me Browsing, and StackWise are trademarks of Cisco Systems, Inc.; Changing the Way We Work, Live, Play, and Learn, and iQuick Study are service marks of Cisco Systems, Inc.; and Access Registrar, Aironet, ASIST, BPX, Catalyst, CCDA, CCDP, CCIE, CCIP, CCNA, CCNP, Cisco, the Cisco Certified Internetwork Expert logo, Cisco IOS, Cisco Press, Cisco Systems, Cisco Systems Capital, the Cisco Systems logo, Cisco Unity, Empowering the Internet Generation, Enterprise/Solver, EtherChannel, EtherFast, EtherSwitch, Fast Step, FormShare, GigaDrive, GigaStack, HomeLink, Internet Quotient, IOS, IP/TV, iQ Expertise, the iQ logo, iQ Net Readiness Scorecard, LightStream, Linksys, MeetingPlace, MGX, the Networkers logo, Networking Academy, Network Registrar, Packet, PIX, Post-Routing, Pre-Routing, ProConnect, RateMUX, ScriptShare, SlideCast, SMARTnet, StrataView Plus, SwitchProbe, TeleRouter, The Fastest Way to Increase Your Internet Quotient, TransPath, and VCO are registered trademarks of Cisco Systems, Inc. and/or its affiliates in the United States and certain other countries.
All other trademarks mentioned in this document or Website 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. (0501R)
Copyright © 2005, Cisco Systems, Inc.
All rights reserved.