Table Of Contents
Release Notes for the Cisco WAN Manager, Release 15.3.00
These release notes are for use with the Cisco WAN Manager (CWM) 15.3 software release that supports MGX, BPX, and IGX switches. You can access the MGX switch documentation at this website. See MGX Switches:
The first section describes all of the switch releases that CWM 15.3.00 supports.
Document Revision History
The Document Revision History table records changes made to this document since its initial release. The table shows the document revision number for the change, the date of the change, and a brief summary of the change.
Revision Date Change Summary
OL-10216-01, Rev. A0
Added bug details for CSCta95976 to the Caveats section.
OL-10216-01, Rev. A0
Releases Supported by CWM 15.3
Table 1 shows the BPX, IGX, and MGX switches and releases that the CWM 15.3 software supports.
For additional information on supported products, see these sections:
This section describes the system requirements for using the CWM. See these System Requirements sections:
In addition to the CWM platform requirements listed in the Cisco WAN Manager Installation Guide, Release 15.3.00, also consider the following:
•The Ultra 60, Enterprise 450, and Enterprise 4500, which were certified with earlier CWM releases, can still be used with CWM 15.3. For these certified system requirements, refer to System Requirement Guidelines in the CWM 11.0.10 release notes; however, the minimum RAM needs to be 2 GB. (See CWM Server Requirements.) Problems reported by customers who choose a noncertified configuration may take more time to troubleshoot, which results in a longer turnaround time. CWM technical support is not provided for Sun configurations or products that Sun Microsystems no longer supports.
•A graphics card is required when using the Java Client access to the CWM. Video on the CWM server is required only for user access or maintenance on the CWM server. Video can be added to Sun servers or workstations. For Ultra and Enterprise, a video adapter is required.
•You can upgrade the standard configuration with more CPU speed, RAM size, and disk space for future expansion.
CWM Server Requirements
Table 2 lists the system requirements for the CWM server. Note also the following about CWM servers:
•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 System Requirement Guidelines in the CWM 11.0.10 release notes.
•If you are using an Ultra 60 (low-end platform), it should have at least 2 GB of RAM.
Java Client Requirements
Table 3 lists the Java Client system requirements.
Standalone Statistics Manager Requirements
Table 4 lists the Standalone Statistics Collector (SSC) or Standalone Statistics Manager (SSM) system requirements, which are the same. Note also the following:
•The file size is 2 MB (typically holds statistics with peak enabled for 20-KB endpoints).
•The number of files does not increase with smaller file size.
•Average Network Transfer Rate is the required TFTP or FTP throughput to collect the maximum number of files (combination of server performance and network bandwidth and traffic).
•One SSM can control a maximum of 12 SSCs.
Table 5 lists additional system requirements for the parser in the CWM server, SSC, or SSM. If the parser is enabled, add the applicable system requirements in Table 5 to the CWM server requirements listed in Table 2 or to the SSM or SSC requirements listed in Table 4.
Five statistics are collected from each connection segment endpoint in 15-minute file collection intervals. Collecting statistics for 4 million endpoints with five 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
This section shows the Solaris patches that you must install for the CWM and those that we recommend you install. You will install these patches after you install the Solaris 9 operating system.
Before You Begin Installing Patches
For best results, follow these Sun recommendations before you begin installing the patches:
•After installing the Solaris 9 operating system, you must install the Solaris 9 Kernel Patch 12 or later. After you have installed the patch, you will install the additional patches (see Table 6) if they were not already installed as part of the cluster.
•Use the single-user mode to install most patches.
•Shut down CWM processes before installing the patches.
•Avoid installing these patches that cause problems with Informix during startup.
Solaris 9 with patches 112963-21 through 112963-24
Solaris 9 with patches 113986-17 through 113986-20
•Not all Solaris patches or patch clusters require a reboot. If a reboot is not required, you can start the CWM after the patch is installed.
Installing the Patches
Use this procedure and sequence to install the patches.
The procedure assumes that you have installed the Solaris 9 operating system.
Step 1 Verify which patches are already installed on your CWM workstation. To display the installed patches, use the Solaris showrev -p command.
Step 2 Go to the SunSolve Patch Access website to access the patches:
(If you have a SunSpectrum contract, you can also access patches from SunService.)
Install the Kernel Patch 12 for Solaris 9. See Table 6 for the correct version number.
Step 3 Install the rest of the required patches if they were not already installed as part of the cluster. Depending on your situation, you may want to enter only the first 6 digits of the patch number in the Find Patch field on the Sun Patch Access site and not the version extension to obtain the latest patch version.
Step 4 Install the recommended patches, as needed and desired. (Several of these recommended patches may require a service contract with Sun.)
HP OpenView Requirements
HP OpenView is used only for viewing the event log and is not required for other CWM procedures. CWM 15.3 works with HP OpenView 6.3 or 7.0.
HP OpenView is not bundled with the CWM CDs. You must order HP OpenView 6.3 or 7.0 directly from Hewlett-Packard and follow the H-P installation requirements and procedures. (Refer to HP OpenView Network Node Manager Products, Installation Guide, Part No. J1136-90000.)
CWM 15.3 uses Informix 9.4 for database operations. The Informix software is bundled with CWM and included on the CWM Server CD in the CWM CD package. The Informix program is installed automatically when CWM is installed.
This section describes the CWM and associated software and CDs. See Table 7 for software information and CD contents.
The CWM Software Evaluation CD package includes all CWM CDs and functionality. All of the CWM features are available until the 45-day evaluation period expires. As noted in Table 7, when you order the CWM package, you receive the CWM Server CD and the CWM Documentation CD.
The following subsections list all of the hardware that CWM 15.3 supports. You can access BPX, IGX, and MGX switch documentation at this website:
See also these sections:
New Hardware Supported by CWM 15.3.00
Table 8 lists the new hardware that CWM 15.3.00 supports.
Existing Hardware Supported by CWM 15.3.00
The tables on the following pages list the hardware that CWM 15.3 supports. Table 9 provides an index of the table numbers that apply to particular platforms.
Table 9 Index of Hardware Tables
Platform Series Table and Page No.
IGX 8400 Series
For IGX 8400 product details, refer to Table 10 in the release notes at this website:
BPX 8600 Series
For BPX 8600 product details, refer to Table 9 in the release notes at this website:
MGX 8220 Series
For MGX 8220 product details, refer to Table 8 in the release notes at this website:
MGX 8230 Series
For MGX 8230 product details, refer to Tables 16 and 17 in the release notes at this website:
MGX 8250 Series
For MGX 8250 product details, refer to Tables 15 and 17 in the release notes at this website:
MGX 8850 Series
For MGX 8850 product details, refer to Tables 15 and 17 in the release notes at this website:
PXM1E on MGX 8830, 8830/B, 8850, and 8850/B Series
For product details, refer to Tables 4 through 8 in the release notes at this website:
MGX 8830/B (PXM 45/C) Series
For MGX 8830/B product details, refer to Tables 4 through 8 in the release notes at this website:
MGX 8850 and 8850/B (PXM 45) Series
For product details, refer to Tables 4 through 8 in the release notes at this website:
MGX 8880 (PXM45/C) Series
For MGX 8880 product details, refer to Table 3 in the release notes at this website:
MGX 8950 (PXM 45) Series
For MGX 8950 product details, refer to Tables 4 through 8 in the release notes at this website:
SES PNNI Controller
For product details, refer to Tables 1-1, 1-2, and 1-3 in the release notes at this website:
Releases Certified for CWM 15.3.00
Table 22 lists the card, shelf, or switch software releases that were used to test the CWM 15.3 software. Although CWM 15.3.00 supports other releases, the releases listed in the table are the specific releases that were tested for CWM 15.3.00.
See also these sections:
New Features and Enhancements
This section describes the new features introduced in CWM 15.3:
•Fractional T/E1 for ATM on the MPSM 16T1E1card:
This feature applies to PXM45-based MGX nodes and PXM1E-based MGX nodes running version 5.3 or later. This feature:
–Provides NxDS0 support for T1/E1 ATM ports.
–Allows only specific consecutive, configurable DS0 timeslots to transmit/receive, enabling you to configure ATM ports while allocating bandwidth that is less than DS1 speed.
AINI and IISP can be set up on a NXDS0 link. NNI trunks are supported on fractional T1/E1 ATM links.
•VXSM 6T3 card support:
CWM 15.3.00 supports the VXSM 6T3 card on PXM45-based MGX 8840 and 8880 nodes (MGX 5.1.10) as follows:
–DSX3 configuration and DS1 line configuration
–Loopback diagnostics operation (from Diagnostics Center)
–AAL2 trunking features of VXSM and statistics related to AAL2 trunking
•MPSM 8 Span Bundle:
Support for an increased number of bundles per card, links per card, and links per DS1 on the MPSM line card is provided.
This feature applies to the MPSM line card running MPSM-PPP 5.3 on the MGX 8850 and 8830 nodes.
•Extended Local Management Interfaces (XLMI) and External Network-to-Network Interfaces (ENNI) on AXSM-XG (OC3 and OC12) service modules on MGX 8850, 8830, and 8950 nodes.
The AXSM-XG cards can be connected to corresponding BXM cards in the AutoRoute (AR) network.
AXSM-8-OC12-XG is an ATM service module that sits on MGX8830/B with a 4-port LM-SMF-4-OC12 back card. This card operates in two modes: channelized and clear channel mode.
•5-Port E/FE/GE auto-sensing back card:
The new 5-port, auto-sensing Ethernet, Fast Ethernet, or Gigabit-Ethernet back card can replace existing back cards in the RPM-PR on PXM45, PXM1, and PXM1E platforms.
This new back card is for use in RPM-PR on MGX 8830, 8850, and 8850/B nodes. This card is supported in upper, lower, or both bays and can be plugged in along with other existing RPM-PR back cards.
Each of the five ports can be of any type of interface: Ethernet, FastEthernet, or GigabitEthernet, based on the speed of the port.
CWM Feature Limitations
This section describes features that the CWM does not support or features for which CWM limitations exist. See these sections:
Features Not Supported
These features are not supported by CWM 15.3 and later patches:
•CID level traps are not sent to the CWM to prevent potential trap flooding.
•CID level statistics are not available in bulk statistics file format from the VXSM modules.
•The CWM does not support use of the Korn shell.
•XPVC support on the FRSM T3E3 in PXM45-based switches has not been tested.
•Several windows display fields that relate to the MPSM-T3E3-155 MultiLink Frame Relay (MLFR) feature, which is not currently supported.
•When managing VISM service modules that are running VISM 3.2.10, the CWM supports only the Rel. 3.2 features.
•These VISM 3.1 features introduced cannot be accessed from the CWM: TGCP, Dynamic Payload, and 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.
•These cards are not supported by CWM 15.3.00 and later patches: the BME card, the FRSM12 service module, and the URM, ARM, FRM, BTM, ALM and CVM service modules. To take advantage of the GUI enhancements that were introduced with CWM 15.3.00, you must upgrade to the newer supported service modules; otherwise, you would stay with CWM 12.
•These are the Current Route feature limitations:
–P2MP calls and SVC/SVP connections are not supported.
–Only master-ended (not slave-ended) connections have current route information.
–The configuration upload file contains only a snapshot of the current route information at the time the switch receives a CWM configuration upload request.
–If a node becomes congested, both of the connTrace messages that the CLI and the Current Route feature send are dropped. The CWM does not distinguish between the messages. This situation is also true for a connTrace ACK message received on a congested node.
–When a node ID is changed, follow this procedure on each network node to flush out all existing current route information and start collecting new information. Disable and re-enable the current route feature by using the cnfndcurrte CLI command. After disabling the feature, wait for at least 9 seconds (the timeout period for a conntrace message) before re-enabling the feature to avoid processing stale conn-trace messages.
–Because the path information for a connection traversing more than 20 nodes is not stored in the current route path table, the connection does not have current route information.
•While the CWM is running, if the remote display is stopped without properly shutting down the CWM desktop, reopening it remotely may not succeed.
The following are known CWM feature limitations:
•For a few of the latest Solaris patches and the Sun Fire E6900 server, the Informix engine may generate a shared memory error as shown in this example:"oninit: Fatal error in shared memory creation <macine name>"
When this error occurs, the Informix engine fails to come up and is not able to perform database related operations.The error can be resolved by changing values in the /etc/system and /usr/users/informix94/etc/onconfig files. The following shows the change to the /etc/system file:forceload: sys/shmsys forceload: sys/semsys set shmsys:shminfo_shmmax=268435456 set semsys:seminfo_semaem=16384 set semsys:seminfo_semmap=64 set semsys:seminfo_semmni=4096 set semsys:seminfo_semmns=4096 set semsys:seminfo_semmnu=4096 set semsys:seminfo_semume=64 set semsys:seminfo_semvmx=32767 set shmsys:shminfo_shmmin=100 set shmsys:shminfo_shmmni=100 set shmsys:shminfo_shmseg=100 set semsys:seminfo_semmsl=100 set rlim_fd_max=1024
After you have made the above changes, edit and configure the "SHMBASE" value in /usr/users/informix94/etc/onconfig as follows and reboot the machine:SHMBASE 0x0A000000L
•Because of a VISM image issue, the CWM cannot update fax_jitt_mode and fax_jitt_initdelay in the vism_card table for a Fax jitter configuration change. This problem will be fixed in the next VISM release.
•Even though the VXSM T3 card is compatible with the MGX 8880 and 8850 PXM45 platform releases, the CWM software does not discover it.
•Cisco does not recommend pointing multiple CWM workstations at the same gateway node.
•When /usr/users becomes completely full, the orbix processes cannot write to the disk and continue operations. To correct the problem, free up disk space in /usr/users and then restart the orbix processes and the CWM as follows: Stop the core and exit out of the CWM prompt, run the stoporbix2000 script, type CWM (you should see "Starting Orbix..." in the ~svplus/log/.startStopOrbix.log file), and start the core.
•When server cannot ping the client, this message is displayed on the CWM workstation: "Exception raised while calling activateLease on pseudoServer.IT_ATLI_IOP:CONNECTION_CREATION
_TIMEOUT." The GUI client initiates the call to activate the lease plug-in that the client uses to detect a server crash. When the server tries to contact the client, it fails, although the DNS is configured so the client can communicate with the server. Make sure that the client can be pinged from the CWM workstation. These are the possible reasons that the server cannot ping the client: A firewall on the client PC may be preventing it from being seen from outside or the network routing from the server to the client is not set up properly.
•When the SSM 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.
•When a shortage of shared memory exists on the workstation, the Informix engine may generate an operating system error, as shown in this example:shmat: : operating system error 18:45:49 shmat: : operating system error 18:45:57 Error writing '/tmp/shmem.1fd4555c.0' errno = 4 18:45:57 mt.c, line 10260, thread 7148, proc id 1008, errors occurred during mt_ notifyvp.
When this error occurs, the statsparser is not able to perform 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.
•When using in-band management, only 50-KB connections are supported on the BPX-SES. To manage 100-KB connections on the BPX-SES, set up the CWM for out-of-band management.
•If an ATM IP interface (also called In-band interface) is being used to manage the switch from the CWM, the CWM cannot receive all node bring-up traps. The ATM connections required for in-band management can take time to get routed on node bring-up and therefore are not available for trap delivery at the initialization time. If this initialization time is an issue, the workaround is to configure the CWM for out-of-band management.
•Allow a 2- to 3-minute period between enabling or disabling statistics operations on the same BPX or IGX node. Whenever statistics are enabled or disabled on a BPX or IGX node and the switch is configuring statistics, enabling or disabling statistics a second time fails.
•If the Start Collection process on the SCM GUI is taking a long time, investigate whether or not collection was started with an unreachable in-band or out-of-band IP address. Use a reachable IP address to start collection with a reachable IP address, either in band or out of band.
•The SSM statistics database can go out of sync with node_ids on the CWM after a coldstart -F is executed on the server. To ensure that the node IDs remain consistent, stop and disable collection before doing a coldstart -F. A CWM-to-CWM gateway must be enabled to ensure uninterrupted statistics collection.
•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.
•To ensure all CWM servers have the same XPVC Preferred data, the CWM-to-CWM gateway must be enabled; otherwise, you must manually propagate the data to all CWM servers.
•On MGX PXM1-based feeders in the BPX network, VISM or VISM-PR terminated XPVCs can connect only to the AUSM service module. No such restriction exists for PXM1E-based or PXM45-based nodes.
•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).
•To correctly manage feeder nodes after they have been moved, you must first delete all trunks from the old node by using the CLI before adding the feeder back onto the system.
•When a back card is removed because the front card is not provisioned, the CWM reports a major alarm with the description "Back Card; not present." However, the switch may not show an alarm. If the card is actually not provisioned, manually clear the major alarm after determining the alarm condition is not real.
•After executing a clrsmcnf command for AXSM from the switch CLI, Chassis View shows the AXSM front card once the card is active, but no back card is found. To ensure that Chassis View recognizes the back card again, you must execute a first level manual node resync.
•RPM-PR and RPM 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.
•Note the following in regard to receiving SNMP traps:
–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, such as FFFFFFFFF10701555, you do not receive trap 25302 and 25303, even though you have registered for that group.
–If you deselect a currently undefined group such as Group 28, that is a bit mask of FFFFFFFFEFFFFFFF, you can then add traps 25302 and 25303 by editing the trap_filter.conf file and adding these lines to Group 20 # Network Connectivity Status Change Traps: TRAP 25302 and TRAP 25303.
•Performing a switchcc command on a controller card in an IGX or BPX node forces the CWM to resync with the node again. This causes a delay in receiving status information.
•Changing the line, payload, and medium types of VXSM-4OC3 causes the CWM to perform a whole card resync when you change any of the following: the medium type between SONET and SDH for SONET physical line, the payload type between T1 (VT 1.5 VC 11) and E1(VT 2 VC 12) for the STS or STM (Au) path or between T1 (VT 1.5 VC 11) and DS3 for the STS path, or the tributary path between Au4 and Au3 for the STM path in the SDH medium. (A whole card resync takes several minutes to complete.)
•If you remove and then immediately add back the same IGX feeder when the CWM is running, the CWM establishes two LINK 0's with the node. This is treated as a delete, and the node is deleted. In this situation, Cisco recommends you either remove and add the feeder when the CWM is down, or, after adding the feeder, restart the CWM.
•Changes made to the node name through the Configuration Center are updated automatically in the Tree and Inspector views. However, the node name in the title bar of the internal frame does not update automatically. To make this change, close and reopen the internal frame. You can also update the attribute values in the internal frame by using the Refresh button of that internal frame.
•After the Line Send parameter LineSendCode is modified by using snmpset, the database is not updating it, which shows the parameter as inapplicable (shows the value as -1). For additional information, refer to CSCin50480 online.
•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.
•Note the following in regard to the managing a PXM45-based MGX node and populating the "peripheral" table: If you are running a release earlier than 4.0.10, CWM 15.0.00 does not populate (update) the peripheral table. If you are running a 4.0.10 or later release, the status field in the peripheral table gets updated only during node resync. (If you are managing a PXM1-based MGX node, the peripheral table status field does not get updated.)
•If the log level for the CWM EM module is set too high or set above the production default value and many configurations are changed on the switch during a warm start, the sync-up performance is impacted during the warm start.
•SmartLogging is a special feature for CWM debugging available when the log level is set to Level 2. It dumps 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 that triggers a Level 2 log message dumps log messages at all levels immediately before and after this event. Because the feature can impact performance due to excessive log messages. it should be disabled in normal operation and enabled only when needed for monitoring performance.
•In regard to the The Forced Deletion feature, note that it does not support XPVC connections. They cannot be force deleted. The feature removes only the unused connection descriptor from the workstation on which it is performed. Other gateway workstations continue to show the descriptor. To clear it completely, you must force delete the unused descriptor at each gateway workstation.
•Occasionally, when you move linked nodes around in the Topology screen, the link does not automatically follow the nodes. Then it looks like the link is not connected to the nodes. Either move the affected nodes around within the window or refresh the Topology screen. When the screen refreshes, the link automatically appears connected to the appropriate nodes again.
•Using the Group Nodes feature affects only your view of the networks. Other users, even those who log into your workstation, do not see the groups you have made.
•After a previously saved configuration file is loaded by using the CWM Config Save & Restore feature, 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. In this case, perform a manual node resync.
•When setting up VISM connections, the VPI value in the VPI/VCI Selector window is grayed out with the VISM card slot number. If VISM is sitting in a feeder node, the VPI value in the VPI/VCI selector is grayed out as zero.
•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.
•Virtual Ports on BPX are displayed in the Tree View application under the physical Line section as physicalPort.virtualPort.
•The PNNI ports on the PXM1 card of an SES node are not displayed in the Tree View.
•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.
•The Loss of Cell Delineation alarm on the AXSME, AXSM-XG, or MPSM-OC3 cards may not get propagated from the switch to the CWM. For the AXSM cards, a line or path alarm is present, but the MPSM-OC-3 card could have an LOCD alarm triggered without any line or path alarm that is present. The line would show in the CWM as clear, while it is actually in alarm.
•With MPSM-OC3 cards, after you replace an OC-3 back card with a DS3 back card or vice versa, you need to do a coldstart.
•Occasionally, WANDEST fails to install immediately after a CWM and Service Agent installation on a workstation running Solaris 9. This error message appears: "Informix is not in on-line mode." The workaround is to install WANDEST by using the C shell (csh).
•In the Connection Manager, the Service Type field displays some nonapplicable service types for SPVCs; however, the CWM displays an error if you select one of these nonapplicable service types.
•If a valid network.conf file is not present, the CWM may not start properly and may cause a topod core dump.
•Because of a device limitation, an SCT greater than 255 cannot be associated with SCT manager.
•An SSC can be added to only one SSM or CWM at a time.
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), the CWM treats these connections as three segment connections and adds 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 want 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 is provisioned by using telnet because 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 deleting SPVC connections on a PXM1E-based node this error message appears: "can not delete connections. Failed to communicate with databroker." The 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 the CWM. Use the Network Monitor map instead.
Note these SSM issues:
•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 enables connections statistics only on SCM but does not set the stats-enabled flag to true on the connection, the statistics are not collected for that connection. Because no mechanism or warning to the user exists to have this enabled on the connections, the CWM does 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. No such limitation exists 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.
•The CWM does not support statistical alarms for lines on PXM45-based MGX nodes.
•The following statistics for SRM and SRM/E T3 lines can be enabled on the switch, but are not supported by SCM: 28 dsx3LCVCurrent, 29 dsx3LESCurrent, 30 dsx3LSESCurrent, 31 dsx3PCVCurrent, 32 dsx3PESCurrent, 33 dsx3PSESCurrent, and 34 dsx3CCVCurrent.
•HP OpenView is supported on the SSM. The SSM processes generate CWM traps.
•At least one CWM must be 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. The SSM gets the node, node_info, card, network, rsc_part, bis_object tables from the CWM server workstation using WANDEST.
•If the statsmaster SWM/CWM is down or unreachable in an 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 or disabling.
•In an SCM Gateway setup with statistics collection in process, the old statistics data is not moved to the new primary CWM/SSM machine after switchover.
•The SSM does not receive traps on Node/Card deletion, so statistics collection must be stopped and disabled before deleting a node or card from the network. Also the SSM does not receive traps on Node/Card Add messages, so the WANDEST upload must be received before the node or card can be seen in the SCM GUI on the SSM.
•In the SSM, statistics collection must be stopped and restarted after changing the node name or changing the node FTP password.
•Statistics data is stored on in statsdb database.
•Statistics parsing is only supported for the statsdb database on the SSM machine and the CWM machine. Statistics parsing is not supported for the stratacom database on the SSM and CWM machine.
•Stop statistics collection before upgrading a node image.
CWM-to-CWM Communication Limitations
This section describes CWM-to-CWM communication limitations:
•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 is not discovered.
•The Configurator can be started on either the primary CWM or the secondary CWMs, but Add, Modify, or Delete operations by using the Configurator can only be performed on the primary CWM.
•The CWM gateway role is undefined or unknown when links between the primary and corresponding secondaries are unstable. When a CWM gateway is in an undefined or unknown role, a core dump sometimes occurs.
All of the above CWM-to-CWM communication limitations listed also apply to the SCM gateway.
Network Monitor Limitations
Network nodes are managed differently depending on the network configuration. See the following configurations:
•In a single routing node PNNI network, the node is managed by using the IP address specified in the network.conf file.
•In the case of a PXM45-based or PXM1E-based MGX network, these PXM45-based or PXM1E-based MGX nodes are managed by using the primary IP address, which is specified by using the cnfndparms CLI command and specifying Option 7 or 8 (depending on chassis type). Configure the trap IP address with the primary IP address.
•PXM1-based MGX nodes connected to PXM45-based MGX nodes are managed through the atm0 IP address. If atm0 is not set, the LAN IP address is used to manage the PXM1-based MGX nodes. Use the cnftrapip command to configure the trap IP address accordingly.
As of the CWM 15.0.00 release and later, the SHOW_TOPO_VIEW flag in the CMSCClient.conf file is used to configure if nodes and trunks are displayed in the topology display of the Network Monitor application at CWM startup. Each flag determines what you see when the NWTopology opens:
•SHOW_TOPO_VIEW 1 = You see nodes and trunks in the topology.
•SHOW_TOPO_VIEW 0 = You cannot see nodes and trunks in the topology.
In releases previous to CWM 15.0.00, a flag named TOPO_SHOW_MAP in the /usr/users/svplus/config/CwmGs.conf file was used to configure if nodes and trunks were displayed in the topology display of the Network Monitor application at CWM startup. Because this flag is now obsolete, you should use the SHOW_TOPO_VIEW flag in the CMSCClient.conf file instead.
Chassis View Operation
This section describes different aspects of the Chassis View operation in the CWM:
Chassis View Card Operation in a Redundant Setup
This section describes how the primary and secondary cards are shown in Chassis View when they are in a redundant setup. The Chassis View behavior is changed based on the CHASSIS_SHOW_PHYSICAL_MAPPING_AND_HIDE_UNMANAGED_ALARMS flag set in the CMSCClient.conf file under the ~svplus/config directory.
When set to false
When two cards are in a redundant relationship, the primary card (also known as the logical slot) displays the ports and lines for all provisioning activities even if the primary slot becomes standby. No ports and lines are shown under the secondary slot even after it becomes active.
In Chassis View, the primary card displays the ports only if they are available in the active card. The secondary slot does not display the ports even if it becomes active.
When set to true
•For the Controller and non-Controller cards:
–When two cards are in a redundant relationship, the active card displays the ports and lines for all provisioning and troubleshooting activities.
–In Chassis View, the active card displays the ports only if they are available in the active card. Chassis View displays the lines and alarms under the active card in a redundant setup.
However, this flag does not affect TreeView and other CWM applications. The logical slot notation in TreeView and other CWM applications and the physical slot notation in Chassis View are maintained whenever an object is selected in one application and launched or dropped in another application.
For example, when the secondary PXM card in slot 8 is active, the line LEDs and alarms are shown on the secondary card in Chassis View. Similarly, when line 1 in slot 8 is selected in Chassis View and another application is launched for that object, the other application is launched for slot 7, line 1.
•For the Controller card only:
–Chassis View does not show unmanaged or unsupported alarms for PXM and RPM cards and unmanaged alarms for MGX nodes, such as the HIST and ACO alarms on the PXM cards.
–Chassis View does show the following in the active controller card: the shelfIntegrated alarm for MGX nodes, physical mapping (alarms and ports or lines) for redundant cards, and alarms that are similar to DCA, DCB, and ENET.
–Chassis View displays an Empty Reserved controller card as a blank card in the front view.
–If no back card or no secondary back card exists, Chassis View displays either card as a blank back card in the rear view.
RPM Card Behavior based on the Chassis View Flag Value
When the CHASSIS_SHOW_PHYSICAL_MAPPING_AND_HIDE_UNMANAGED_ALARMS flag value is set to true in the CMSCClient.conf file, unmanaged alarms, such as the CB_TX and CB_RX alarms on the RPM cards, are not shown in the RPM card in Chassis View.
Chassis View Operation after Card and Line Switchover
For a card switchover in a redundant setup, Chassis View behavior depends on the CHASSIS_SHOW_PHYSICAL_MAPPING_AND_HIDE_UNMANAGED_ALARMS flag value set in the CMSCClient.conf file.
After line switchover, provisioning is allowed only on the working line of an automatic protection switching (APS) pair, whether the line is currently active or not. However, both the working and protection lines are monitored.
CWM Notes and Cautions
Because of the asynchronous behavior of the ILOG client and server interaction, the CWM client requests may be sent before the CWM server is ready. In this case, this error message appears:Ilb Error: Synchronous request to <unidentified actor failed by timeout>.
Note If the ILOG timeout situation persists for more than 5 minutes and the CWM workstation is not functioning normally, you should call service.
Parameters that the Network Monitor or Configuration Center displays that do not apply to an element, such as a line or a trunk, often contain the value -1. Consider this the same as Not Applicable.
Network Configurator displays an authentication failure under the following circumstances:
1. First, your password gets changed when you are logged into the CWM with any of these applications open: Configuration Center, Network Monitor, or Chassis View.
2. Then, you try to launch Network Configurator. The CWM does not prompt you to enter a password. Instead, it displays an authentication failure.
In this situation, you must exit the CWM and relaunch the Configuration Center.
Caution Data will be lost when rebooting if you do not shut down Informix first. To shut down Informix properly before you reboot the machine, execute
/usr/users/svplus/scripts/kill_db as superuser (root).
If persistency is enabled in a PNNI network and you remove a node from the network, you must also delete the node and the corresponding trunks and feeders manually from all the gateway nodes. Otherwise, none of these will be cleared from the CWM.
Installing and Upgrading the CWM
This section describes how to install or upgrade CWM 15.3, or access the installation information. It also provides important background information about installing or upgrading the CWM server.
You can upgrade to CWM 15.3.00 from any of the following:
•CWM 15.0.00 (latest patch) on Solaris 8 to CWM 15.3.00 on Solaris 9
•CWM 15.0.00 (latest patch) on Solaris 9 to CWM 15.3.00 on Solaris 9
•CWM 15.1.50 (latest patch) on Solaris 8 to CWM 15.3.00 on Solaris 9
To upgrade from an earlier CWM release, you must first upgrade to one of the releases listed above. To do so, see the installation guide and the release note for the appropriate CWM version (CWM 15.1.0 or CWM 15.1.50) at this URL:
See these sections:
Before You Start
This section includes the following:
This section provides important background information that is provided to help you install CWM 15.3.00 successfully.
Naming Managed Nodes
The name of each node that the CWM manages 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
In the past, core files were created without unique names and then overwritten. Now, for each core dump, a unique directory is created under ~svplus/corefilesdir/. Each directory is named as follows: <Core.<processName>.<pid>.mmddHrMinSec. These directories have these contents:
•Core file named <processName>.<pid>.mmddHrMinSec.core
•Information file with dmesg, onstat -d, pstack, and other details named "<processName>.<pid>.mmddHrMinSec.info"
•Corresponding log file(s) named "<processName>.<pid>.log"
Cisco Info Version
The CWM supports integration with the Cisco Info Center (CIC) application so the two applications can function together. To facilitate this integration, the CWM includes a tar file that can be installed by using the CIC update utility (nco_update). This tar file is provided in a format that the update utility can process on the CWMAgent CD-ROM.
The 15.3.00_SNMPAgent.tar.gz file contains the CIC36xPatch004CWM151.tar file, which contains rule files that are compatible only with CIC 3.6.1. To use these rule files, you must install CIC 3.6 or 3.6.1.
If you want to continue using CIC 3.6.0 or 3.5 with CWM 15.3.00, save and then apply the CIC36Pipp000CWM15 tar file that is available in the CWM 15.3.00 SNMP Agent CD instead.
For more information on CIC, refer to this URL:
CWM 15.3.00 supports C-Note version 3. Before the Orbix cmldomain services for C-Note are started, the CWM core must be started and core processes should be running. Add the IP address of the C-Note workstation to the /opt/ssng/config/CMLLogin/SnmpPublisher.xml file by entering this command:vi /opt/ssng/config/CMLLogin/SnmpPublisher.xml
The line you add should look like this, substituting your actual C-Note workstation IP address for one in the example below:<ipAddress>172.28.140.218</ipAddress>
Numbering for Release 9.4 IGX Feeder Nodes
When an IGX is added as a feeder to a SES/BPX or MGX node, it has a default node number that may not be unique within the network. If it is not unique, it needs to be modified to a unique node number by issuing the rnmnd <x> CLI command, where x is unique with regard to all other auto-route nodes.
To find the other node numbers, use the dspnds +n CLI command. If you fail to do this, the CWM Databroker may have an incorrectly formed hybrid connection database, and the CWM GUI may show the connection as incomplete.
The security and user profiles are stored in the database as user_info and sec_profile tables. All CWM systems in the same domain have the same data in the user_info and sec_profile tables through CWM-to-CWM communication. The user_info and sec_profile tables do not get dropped when the coldstart command is executed during a coldstart. They 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.
To be added to the database, the CWM user has to be a valid UNIX user because the user is authenticated against UNIX when he or she logs in to the CWM. The user password must match the one that is defined in the UNIX system.
Permission settings for adding, deleting, or modifying network partitions or subnetworks can be configured by using the Security Manager GUI.
After creating a new database by executing the coldstart script, a database inconsistency will result if the CWM is restarted (stop core and start core) before it is synchronized with the network. In this case, rerun the coldstart script to avoid database inconsistencies. Do not use the SV+CreateDb tool for this purpose.
When a gateway node is upgraded or rebuilt before the CWM has synced up with the network, the CWM must be cold-started (create CWM database and restart the CWM) to ensure CWM database consistency.
The user-supplied network name can be up to 10 characters long and should use only alphanumeric characters (no periods).
For the IGX ports, the asi_line table is populated with the 1-based port number and not the 0-based port number.
RPM Management Limitations
RPM-PR is not supported on MGX PXM1-based nodes managed by Chassis View in CWM 15.3.00. The applicable trap is missing so the CWM cannot monitor the back card.
For both RPM and RPM-PR cards managed by Chassis View in CWM 15.3.00 that are in standby 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. To enable the feature and obtain RPM back card information, edit the emd.conf file before starting the CWM core. Note that when back card support is enabled, back card information is polled from the switch only during a coldstart or a manual resync. After that, any back card configuration or status changes are not updated until you perform another coldstart or a manual resync.
The CWM does not distinguish between the Ethernet back card versions installed with the MGX-RPM-128M/B or RPM-PR. No difference in functionality exists.
Equipment Management Configuration Notes
In the emd.conf file, the OORequest and OOStart parameters should be customized, depending on network. The OORequest parameter defines the number of configuration files per node that can be requested at one time, with 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 of the PNNI nodes that the CWM manages (PXM45-based 8950, 8880, and 8850 nodes; PXM1E- based 8950, 8850, and 8830 nodes; and BPX nodes with SES shelves) are distributed among OOEMC processes.
The number of nodes that a single process manages is computed by dividing the number of PNNI network nodes by the number of processes that OOStart defines. Assume that the number of nodes that one process manages is called MANAGED_NODE_COUNT. Then, MANAGED_NODE_COUNT * OORequest must be less than or equal to 200, which can be achieved by increasing the OOStart or reducing the OORequest. The normal range of OOStart is 5 to 20. If the OOStart value is increased beyond 10, the number of DMD processes has to be increased or the shared memory overflows.
Network Monitor Server Configuration File (NMServer.conf)
Two parameters in the NMServer.conf configuration file—HELLO_EVENT_INTERVAL and EVENT_REDELIVERY_COUNT—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 number as the HELLO_EVENT_INTERVAL value times the EVENT_REDELIVERY_COUNT value. The range for HELLO_EVENT_INTERVAL is 0 through 600, and the default is 60. The range for EVENT_REDELIVERY_COUNT is 0 through 10, and 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.
Before installing or upgrading to CWM 15.3.00, you must decide which programs and components to install or upgrade based on the release and parameter you started with and the desired end configuration.
Table 23 summarizes the various installation or upgrade configurations and procedures.
Installation or Upgrade Sequences
This section describes the installation or upgrade sequence of operations for these servers:
Table 24 shows the sequence to follow when installing or upgrading a CWM server.
Table 25 shows the sequence of operations to follow when installing or upgrading a CWM client.
Table 26 shows the sequence of operations to follow when installing or upgrading a Statistics Collection Manager, Standalone (SCMSA)-SSM client. Note that this procedure applies only to the SSM.
Statistics Collection Manager Standalone
Table 27 shows the sequence of operations to follow when installing or upgrading a Statistics Collection Manager, Standalone (SCMSA) installation or upgrade.
Preparing for CWM Installation
All of these products should be installed before you install CWM 15.3.00:
•Solaris Operating System 9 (includes instructions for disk partitioning)
•HP OpenView (Optional)
If you need instructions for installing any of these products, see Cisco WAN Manager Installation Guide, Release 15.3.00. You can access all CWM documentation at this URL:
:Installing the CWM Server Software
By using the CWM 15.3.00 product CD, follow the procedures in the CWM installation guide to install the CWM server software (and RtmProxy if necessary.) See the Cisco WAN Manager Installation Guide, Release 15.3.00 at this URL:
During the installation, you may notice that when you select the partition where you want the Informix Physical Log, you are now given three choices—Same Raw Partition, Separate Raw Partition, and Meta Devices—whereas previously you could choose only Same Raw Partition or Meta Devices.
Upgrading to Solaris 9 and CWM 15.3.00
If you are already running CWM 15.0 or 15.1.50 on Solaris 9, you can begin upgrading the CWM software without having to upgrade from Solaris 8 to Solaris 9. Otherwise, you must upgrade to Solaris 9.
To upgrade from Solaris 8 to Solaris 9 and upgrade the CWM software, see Chapter 4, "Upgrading the CWM from an Earlier Version," in the Cisco WAN Manager Installation Guide, Release 15.3.00 at this URL. You can access all CWM documentation at this URL:
Creating a CWM Auto-Restart Shell Script
This section describes how to create and configure 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.
Use this procedure to create a script that uses the vi editor and shell commands to automatically restart the CWM core after the workstation has been rebooted.
Note Several minor errors that existed in the past in the CWM Auto restart shell script have been corrected in the script that follows.
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 this 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 these lines:******************************************************************#!/bin/sh# Check if Informix configuration is going on while [ ! -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 svplus echo "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.log su - svplus -c /usr/users/svplus/scripts/Install/RunGuard &# Start CWM core process ... as svplus su - svplus -c /usr/users/svplus/scripts/start_SV+ &******************************************************************
Note To save your changes while using the vi editor, press Esc, colon (:), then wq!.
Step 5 Provide execute permissions for
/etc/rc3.d/S99init_svby executing this command:# chmod 755 S99init_sv
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 cannot have the same script number as any other script files in
For more information on configuring this feature, refer to the
SNMP Service Agent Trap Limitation
This section describes the SNMP Service Agent trap limitation with the PXM1-based MGX nodes. The type of traps that the CWM collects from adding and modifying connections on Cisco MGX PXM1-based nodes running release 1.3.00 and onward can be configured by using the cnfchantrapenbl and dspchantrapenbl 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 command is set to Default, you can use the cnfchantrapenbl Enable command to change to collecting only trap 50601 when the CWM is running.
However, if you are currently collecting only 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 command, all CWM workstations monitoring the node must be shut down (the core must 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 issues in the CWM 15.3.00 and WANDEST 2.7 software:
•Known issues in the CWM 15.3.00—Table 28
•Issues resolved in CWM 15.3.00—Table 29
Polling real time stats fails on BPX-SES.
Bugs Resolved in the CWM 15.3.00 Software
All issues resolved in CWM 15.1.50 as of February 14, 2006 that apply to CWM 15.3.00 are included in CWM 15.3.00. Table 29 lists externally found issues from CWM 15.0.00 as of February 14, 2006 that were resolved in CWM 15.3.00 software.
Related CWM and Switch Documentation
A Guide to Cisco Multiservice Switch Documentation ships with your product. This guide contains general information about how to locate Cisco MGX, BPX, SES, and CWM documentation online.
These documents comprise the CWM documentation set. The first five documents are on the CWM Documentation CD and on Cisco.com:
•Cisco WAN Manager Installation Guide, Release 15.3.00
•Cisco WAN Manager User's Guide, Release 15.3.00
•Cisco WAN Manager SNMP Service Agent Guide, 15.3.00
•Cisco WAN Manager Database Interface Guide, Release 15.3.00
•Cisco WANDEST Installation and Reference, Release 2.7
These documents are available on Cisco.com:
•Release Notes for Cisco WAN Manager, Release 15.3.00
•Release Notes for the Cisco WAN Modeling Tools, Release 15.3.00
•Cisco WAN Modeling Tools User Guide, 15.3.00
•Release Notes for CWM Automated Bulk Provisioning, Release 15.3.00
•Cisco WAN Manager Automated Bulk Provisioning Guide, Release 15.3.00
The CWM Modeling Tools and Automated Bulk Provisioning user guides are also available on their software CDs and ordered separately.
Refer to the current CWM release notes for information on all the switch products that CWM supports and that are certified in this release.
You can access all CWM documentation at this website:
These documents support this release of the Cisco Multiservice Switch products and are shipped with the product:
•Regulatory Compliance and Safety Information for Cisco Multiservice Switch Products (MGX, BPX, and SES)—Familiarizes you with safety precautions for your product.
•A Guide to Cisco Multiservice Switch Documentation—Describes how to find the manuals and release notes that support multiservice switches and network management products. These documents are available only online. This guide ships with the product.
•Installation Warning Card—Contains precautions that you should take before you insert a card into a slot. This Warning Card ships with the product.
You can access the MGX switch documentation at this website. See MGX Switches:
Refer to these MGX technical manuals as appropriate:
•For planning information if your network contains MGX and SES products—Cisco PNNI Network Planning Guide for MGX and SES Products
•For information about installing cards and cables in the MGX chassis:
–Cisco MGX 8850 (PXM1E/PXM45), Cisco MGX 8950, and Cisco MGX 8830 Hardware Installation Guide, Releases 2 Through 5 for installing cards and cables in these chassis.
–Cisco MGX 8xxx Edge Concentrator Installation and Configuration Guide for installing cards and cables in the Cisco MGX 8230, Cisco MGX 8250, or Cisco MGX 8850 (PXM1) chassis.
•For configuring your MGX switch and processor cards:
–Cisco MGX 8850 (PXM1E/PXM45), Cisco MGX 8950, and Cisco MGX 8830 Configuration Guide, Release 5 for these chassis.
–Cisco MGX 8xxx Edge Concentrator Installation and Configuration Guide for the Cisco MGX 8230, Cisco MGX 8250, or Cisco MGX 8850 (PXM1) chassis.
You can also use Cisco.com to search for any product and topic by entering a word or phrase in the Search window. For example, you can search for "configuring MGX 8850" or "PXMIE." By using the Advanced Search option, you can search the entire Cisco.com or Technical Support & Documentation.
Cisco documentation and additional literature are available on Cisco.com. Cisco also provides several ways to obtain technical assistance and other technical resources. These sections explain how to obtain technical information from Cisco Systems.
You can access the most current Cisco documentation at this URL:
You can access the Cisco website at this URL:
You can access international Cisco websites at this URL:
Product Documentation DVD
The Product Documentation DVD is a comprehensive library of technical product documentation on a portable medium. The DVD enables you to access multiple versions of installation, configuration, and command guides for Cisco hardware and software products. With the DVD, you have access to the same HTML documentation that is found on the Cisco website without being connected to the Internet. Certain products also have PDF versions of the documentation available.
The Product Documentation DVD is available as a single unit or as a subscription. Registered Cisco.com users (Cisco direct customers) can order a Product Documentation DVD (product number DOC-DOCDVD= or DOC-DOCDVD=SUB) from Cisco Marketplace at this URL:
Registered Cisco.com users may order Cisco documentation at the Product Documentation Store in the Cisco Marketplace at this URL:
Nonregistered Cisco.com users can order technical documentation from 8:00 a.m. to 5:00 p.m. (0800 to 1700) PDT by calling 1 866 463-3487 in the United States and Canada, or elsewhere by calling 011 408 519-5055. You can also order documentation by e-mail at email@example.com or by fax at 1 408 519-5001 in the United States and Canada, or elsewhere at 011 408 519-5001.
You can rate and provide feedback about Cisco technical documents by completing the online feedback form that appears with the technical documents on Cisco.com.
You can submit comments about Cisco documentation by using the response card (if present) behind the front cover of your document or by writing to the following address:
Attn: Customer Document Ordering
170 West Tasman Drive
San Jose, CA 95134-9883
We appreciate your comments.
Cisco Product Security Overview
Cisco provides a free online Security Vulnerability Policy portal at this URL:
From this site, you will find information about how to:
•Report security vulnerabilities in Cisco products.
•Obtain assistance with security incidents that involve Cisco products.
•Register to receive security information from Cisco.
A current list of security advisories, security notices, and security responses for Cisco products is available at this URL:
To see security advisories, security notices, and security responses as they are updated in real time, you can subscribe to the Product Security Incident Response Team Really Simple Syndication (PSIRT RSS) feed. Information about how to subscribe to the PSIRT RSS feed is found at this URL:
Reporting Security Problems in Cisco Products
Cisco is committed to delivering secure products. We test our products internally before we release them, and we strive to correct all vulnerabilities quickly. If you think that you have identified a vulnerability in a Cisco product, contact PSIRT:
•For Emergencies only — firstname.lastname@example.org
An emergency is either a condition in which a system is under active attack or a condition for which a severe and urgent security vulnerability should be reported. All other conditions are considered nonemergencies.
•For Nonemergencies — email@example.com
In an emergency, you can also reach PSIRT by telephone:
•1 877 228-7302
•1 408 525-6532
Tip We encourage you to use Pretty Good Privacy (PGP) or a compatible product (for example, GnuPG) to encrypt any sensitive information that you send to Cisco. PSIRT can work with information that has been encrypted with PGP versions 2.x through 9.x.
Never use a revoked or an expired encryption key. The correct public key to use in your correspondence with PSIRT is the one linked in the Contact Summary section of the Security Vulnerability Policy page at this URL:
The link on this page has the current PGP key ID in use.
If you do not have or use PGP, contact PSIRT at the aforementioned e-mail addresses or phone numbers before sending any sensitive material to find other means of encrypting the data.
Obtaining Technical Assistance
Cisco Technical Support provides 24-hour-a-day award-winning technical assistance. The Cisco Technical Support & Documentation website on Cisco.com features extensive online support resources. In addition, if you have a valid Cisco service contract, Cisco Technical Assistance Center (TAC) engineers provide telephone support. If you do not have a valid Cisco service contract, contact your reseller.
Cisco Technical Support & Documentation Website
The Cisco Technical Support & Documentation website provides online documents and tools for troubleshooting and resolving technical issues with Cisco products and technologies. The website is available 24 hours a day, at this URL:
Access to all tools on the Cisco Technical Support & Documentation website requires a Cisco.com user ID and password. If you have a valid service contract but do not have a user ID or password, you can register at this URL:
Note Use the Cisco Product Identification (CPI) tool to locate your product serial number before submitting a web or phone request for service. You can access the CPI tool from the Cisco Technical Support & Documentation website by clicking the Tools & Resources link under Documentation & Tools. Choose Cisco Product Identification Tool from the Alphabetical Index drop-down list, or click the Cisco Product Identification Tool link under Alerts & RMAs. The CPI tool offers three search options: by product ID or model name; by tree view; or for certain products, by copying and pasting show command output. Search results show an illustration of your product with the serial number label location highlighted. Locate the serial number label on your product and record the information before placing a service call.
Submitting a Service Request
Using the online TAC Service Request Tool is the fastest way to open S3 and S4 service requests. (S3 and S4 service requests are those in which your network is minimally impaired or for which you require product information.) After you describe your situation, the TAC Service Request Tool provides recommended solutions. If your issue is not resolved using the recommended resources, your service request is assigned to a Cisco engineer. The TAC Service Request Tool is located at this URL:
For S1 or S2 service requests, or if you do not have Internet access, contact the Cisco TAC by telephone. (S1 or S2 service requests are those in which your production network is down or severely degraded.) Cisco engineers are assigned immediately to S1 and S2 service requests to help keep your business operations running smoothly.
To open a service request by telephone, use one of the following numbers:
Asia-Pacific: +61 2 8446 7411 (Australia: 1 800 805 227)
EMEA: +32 2 704 55 55
USA: 1 800 553-2447
For a complete list of Cisco TAC contacts, go to this URL:
Definitions of Service Request Severity
To ensure that all service requests are reported in a standard format, Cisco has established severity definitions.
Severity 1 (S1)—An existing network is down, or there is a critical impact to your business operations. You and Cisco will commit all necessary resources around the clock to resolve the situation.
Severity 2 (S2)—Operation of an existing network is severely degraded, or significant aspects of your business operations are negatively affected by inadequate performance of Cisco products. You and Cisco will commit full-time resources during normal business hours to resolve the situation.
Severity 3 (S3)—Operational performance of the network is impaired, while most business operations remain functional. You and Cisco will commit resources during normal business hours to restore service to satisfactory levels.
Severity 4 (S4)—You require information or assistance with Cisco product capabilities, installation, or configuration. There is little or no effect on your business operations.
Obtaining Additional Publications and Information
Information about Cisco products, technologies, and network solutions is available from various online and printed sources.
•The Cisco Product Quick Reference Guide is a handy, compact reference tool that includes brief product overviews, key features, sample part numbers, and abbreviated technical specifications for many Cisco products that are sold through channel partners. It is updated twice a year and includes the latest Cisco offerings. To order and find out more about the Cisco Product Quick Reference Guide, go to this URL:
•Cisco Marketplace provides a variety of Cisco books, reference guides, documentation, and logo merchandise. Visit Cisco Marketplace, the company store, at this URL:
•Cisco Press publishes a wide range of general networking, training and certification titles. Both new and experienced users will benefit from these publications. For current Cisco Press titles and other information, go to Cisco Press at this URL:
•Packet magazine is the Cisco Systems technical user magazine for maximizing Internet and networking investments. Each quarter, Packet delivers coverage of the latest industry trends, technology breakthroughs, and Cisco products and solutions, as well as network deployment and troubleshooting tips, configuration examples, customer case studies, certification and training information, and links to scores of in-depth online resources. You can access Packet magazine at this URL:
•iQ Magazine is the quarterly publication from Cisco Systems designed to help growing companies learn how they can use technology to increase revenue, streamline their business, and expand services. The publication identifies the challenges facing these companies and the technologies to help solve them, using real-world case studies and business strategies to help readers make sound technology investment decisions. You can access iQ Magazine at this URL:
or view the digital edition at this URL:
•Internet Protocol Journal is a quarterly journal published by Cisco Systems for engineering professionals involved in designing, developing, and operating public and private internets and intranets. You can access the Internet Protocol Journal at this URL:
•Networking products offered by Cisco Systems, as well as customer support services, can be obtained at this URL:
•Networking Professionals Connection is an interactive website for networking professionals to share questions, suggestions, and information about networking products and technologies with Cisco experts and other networking professionals. Join a discussion at this URL:
•World-class networking training is available from Cisco. You can view current offerings at this URL:
© 2006-2006 Cisco Systems, Inc. All rights reserved.