Release Notes for the Cisco WAN Manager, Release 15.3.00 P1 August 2006 Rev. C0 These release notes are for use with the Cisco WAN Manager (CWM) 15.3.00 P1 software release that supports MGX, BPX, and IGX switches. You can access the MGX switch documentation at this website. At the site, see MGX Switches: http://www.cisco.com/en/US/products/hw/switches/tsd_products_support_category_home.html The first section describes all of the switch releases that CWM 15.3.00 P1 supports.
Releases Supported by CWM 15.3.00, Patch 1 Releases Supported by CWM 15.3.00, Patch 1 Table 1 shows the BPX, IGX, and MGX switch platforms and releases that the CWM 15.3.00, Patch 1 software supports. For additional information on supported products, see these sections: • Supported Hardware, page 9 • Releases Certified for CWM 15.3.00 P1, page 22 Table 1 Switch Platforms and Releases Supported by CWM 15.3.
System Requirements System Requirements This section describes the system requirements for using the CWM: • CWM Server Requirements, page 3 • Java Client Requirements, page 4 • Standalone Statistics Manager Requirements, page 4 • Solaris Patch Requirements, page 6 • HP OpenView Requirements, page 7 • Informix Requirements, page 7 In addition to the CWM platform requirements listed in the Cisco WAN Manager Installation and Configuration Guide, Release 15.3.
System Requirements Table 2 CWM Server System Requirements CWM Platform No. of CPUs Min. CPU Speed (MHz) Min. RAM (GB) Min. Swap Space (GB) Max No. of PVC/SPVC Connections Min.
System Requirements Table 4 • 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. SSC or SSM System Requirements RAM Swap Space (GB) Disk Space (GB) Max. No. of Stats Files (15-min. collection Server Used intervals) in Cisco Testing 512 MB 2 2 x 18 350 U60 450 3.
System Requirements 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.
System Requirements Table 6 Required and Recommended Solaris Patches Patches Solaris 9 Required to be installed first Kernel Patch 12 (112233-12 or higher) Required 112874-31 112785-42 112970-07 114716-01 113580-01 114224-02 112998-03 112811-01 Recommended 115336-02 112964-07 113575-05 112808-06 HP OpenView Requirements HP OpenView is used only for viewing the event log and is not required for other CWM procedures. The CWM works with HP OpenView 6.3 or 7.0.
CWM Packaging CWM Packaging 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 and Documentation CDs.
Supported Hardware Table 7 CWM and Associated Software (continued) Software and Documentation CD Notes Automated Bulk Provisioning Automated Bulk Provisioning Software CD This CD must be ordered separately from the CWM set. Cisco WAN Modeling Tools Cisco WAN Modeling Tools Software CD This CD must be ordered separately from the CWM set. Supported Hardware The following subsections list all of the hardware that CWM 15.3.00, Patch 1 supports.
Supported Hardware IGX 8400 Series For IGX 8400 product details, refer to Table 10 in the release notes at this website: http://www.cisco.com/univercd/cc/td/doc/product/wanbu/bpx8600/9_4/rnote/9412rn.
Supported Hardware Table 10 BPX 8600 (continued) Front Card (continued) Back Card BPX-BCC-4V/B — BPX-BME BPX-T3/E3-BC BPX-BME-OC12 BPX-E3-BC BPX-MMF/SMF/SMFLR-2-BC BPX-BXM-155-8 BPX-MMF/SMF/SMFLR-8-155 BPX-BXM-155-4 BPX-BXM-E-155 BPX-MMF/SMF/SMFLR-4-155 BPX-BXM-622 BPX-BXM-E-622 BPX-622-2-BC BPX-SMF/SMFLR-622-BC BPX-SMF/SMFLR-622-2-BC BPX-BXM-T3/E3 BPX-T3/E3-BC BPX-STM1-EL-4 BPX-T3/E3 BPX-E3-BC BPX-MMF/SMF/SMFLR-2-BC BPX-XLR BPX-E3-BC BPX-MMF/SMF/SMFLR-2-BC RDNT-SMF-155 RDNT-LR-155/62
Supported Hardware Table 11 MGX 8220 (continued) Front Card Back Card SRM DB-15-T1/E1 LM-3T3 AUSM-4T1E1 AUSM-8T1E1 AUSM-8T1E1/B 8T1/E1 MGX 8230 Series For MGX 8230 product details, refer to Tables 16 and 17 in the release notes at this website: http://www.cisco.com/univercd/cc/td/doc/product/wanbu/mgx8230/13/rnotes/rn1312.
Supported Hardware Table 12 MGX 8230 (PXM1) (continued) MGX-VISM-PR AX-SMB-8E1 AX-R-SMB-8E1 AX-RJ48-8T1/8E1 AX-R-RJ48-8T1/8E1 MGX-RJ48-8E1 PXM1 T3/E3/OC-3/OC-12 MGX 8250 Series For MGX 8250 product details, refer to Tables 15 and 17 in the release notes at this website: http://www.cisco.com/univercd/cc/td/doc/product/wanbu/mgx8230/13/rnotes/rn1312.
Supported Hardware Table 13 MGX 8250 (PXM1) (continued) Front Card Back Card MPSM-8-T1E1 AX-RJ-48-8T1/8E1 AX-R-RJ-48-8T1/8E1 AX-SMB-8E1 AX-R-SMB-8E1 PXM1 T3/E3/OC-3/OC-12 SRM LM-3T3 MGX 8850 Series For MGX 8850 product details, refer to Tables 15 and 17 in the release notes at this website: http://www.cisco.com/univercd/cc/td/doc/product/wanbu/mgx8230/13/rnotes/rn1312.
Supported Hardware Table 14 MGX 8850 (PXM1) (continued) Front Card Back Card MGX-RPM-128M/B MGX-MMF-FE MGX-RJ45-FE MGX-RJ45-4E MGX-MMF/SMF-FDDI MGX-MMF/SMF-FDDI/FD MGX-SRME MGX-SMFIR-1-155 MGX-STM1-EL1 MGX-VISM-8T1 MGX-VISM-8E1 AX-SMB-8E1 AX-R-SMB-8E1 AX-RJ-48-8T1/8E1 AX-R-RJ48-8T1/8E1 MGX-RJ48-8E1 MGX-VISM-PR AX-RJ48-8T1 AX-R-RJ48-8T1 MGX-VXSM-6T3 VXSM-BC-SMB-3T3E3 MPSM-8-T1E1 AX-RJ-48-8T1/8E1 AX-R-RJ-48-8T1/8E1 AX-SMB-8E1 AX-R-SMB-8E1 PXM1 T3/E3/OC-3/OC-12 SRM LM-3T3 PXM1E on MGX 8830
Supported Hardware Table 15 PXM1E on MGX 8830, 8830/B, 8850, and 8850/B (continued) Front Card Back Card MGX-RPM-PR MGX-MMF-FE MGX-RJ45-4E/B (Ethernet) MGX-RJ45-FE (Fast Ethernet) 5-port auto sensing Fast and Gigabit Ethernet MGX-SRME/B MGX-BNC-3T3-M MGX-STM1-EL-1 MPSM-8-T1E1 AX-RJ48-8T1/E1 AX-R-RJ48-8T1/8E1 AX-SMB-8E1 AX-R-SMB-8E1 MPSM-16-T1E1 RBBN-16-T1E1-1N MCC-16-E1-1N RED-16-T1E1 (For the 1:N redundancy of the MPSM-16-T1E1, MGX 8830/B supports the RCON-1TO3-8830 back card and MGX 8850/B sup
Supported Hardware 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: http://www.cisco.com/univercd/cc/td/doc/product/wanbu/8850px45/relnote/52008xx0.
Supported Hardware MGX 8850 and 8850/B (PXM 45) Series For product details, refer to Tables 4 through 8 in the release notes at this website: http://www.cisco.com/univercd/cc/td/doc/product/wanbu/8850px45/relnote/52008xx0.
Supported Hardware Table 17 PXM45 on MGX 8850 and 8850/B (continued) Front Card Back Card MGX-RPM-PR MGX-MMF-FE MGX-RJ45-4E/B (Ethernet) MGX-RJ45-FE (Fast Ethernet) 5-port auto sensing Fast and Gigabit Ethernet MGX-RPM-XF MGX-1GE/2GE MGX-1OC12POS/2OC-12POS-IR MGX-XF-UI/-UI/B MGX-SRME MGX-SMFIR-1-155 MGX-STM1-EL1 MGX-SRME/B MGX-BNC-3T3-M MGX-STM1-EL-1 MGX-VISM-PR AX-SMB-8E1 AX-R-SMB-8E1 AX-RJ48-8T1/8E1 AX-R-RJ48-8E1/8T1 MGX-VXSM VXSM-BC-4-155 VXSM-BC-24T1E1 MPSM-8-T1E1 AX-RJ-48-8T1/8E1 AX-R
Supported Hardware MGX 8880 (PXM45/C) Series For MGX 8880 product details, refer to Table 3 in the release notes at this website: http://www.cisco.com/univercd/cc/td/doc/product/wanbu/mgx8880/relnote/528880.
Supported Hardware Table 19 MGX 8950 (PXM45) (continued) Front Card Back Card AXSM-16-155-XG SFP-8-155 MMF/SMFIR/SMFLR-1-155-SFP MCC-8-155 AXSM-16-T3E3/B SMB-8-T3/E3 MGX-RPM-PR MGX-MMF-FE MGX-RJ45-4E/B (Ethernet) MGX-RJ45-FE (Fast Ethernet) 5-port auto-sensing Fast and Gigabit Ethernet MGX-RPM-XF MGX-1GE/2GE MGX-1OC12POS/2OC-12POS-IR MGX-XF-UI/-UI/B MGX-XM60 — PXM45/B PXM45/C PXM-HD PXM-UI-S3 PXM-UI-S3/B SES PNNI Controller For product details, refer to Tables 1-1, 1-2, and 1-3 in the rele
Releases Certified for CWM 15.3.00 P1 Releases Certified for CWM 15.3.00 P1 Table 21 lists the card, shelf, or switch software releases that were used to test the CWM 15.3.00 P1 software. Although CWM 15.3.00 P1 supports other releases, the releases listed in the table are the specific releases that were tested for CWM 15.3.00 P1. See also these sections: • Releases Supported by CWM 15.3.00, Patch 1, page 2 • Supported Hardware, page 9 Table 21 Releases Tested with CWM 15.3.
New Features and Enhancements New Features and Enhancements This section describes the new features introduced in CWM 15.3.00 P1: • Multi-Time Zone Support for Object Finder—This feature enables you to specify the local or GMT time zone when viewing and querying historical alarms. In the previous CWM releases, the historical Alarms query from the Object Finder displayed the time only in the client machine timestamp.
CWM Feature Limitations • 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 P1: the BME card and the FRSM12, URM, ARM, FRM, BTM, ALM and CVM service modules.
CWM Feature Limitations 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.
CWM Feature Limitations • 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.
CWM Feature Limitations • 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 nondefault 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.
CWM Feature Limitations • 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.
CWM Feature Limitations 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.
CWM Feature Limitations • 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.
CWM Feature Limitations • The Configurator can be started on either the primary CWM or the secondary CWMs, but devices can be added, modified, or deleted using the Configurator only 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.
CWM Feature Limitations 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.
Installing and Uninstalling CWM 15.3.00 P1 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 . Note If the ILOG timeout persists for more than 5 minutes and the CWM is not functioning normally, you should call service.
Installing and Uninstalling CWM 15.3.00 P1 Before You Start This section provides important background information that is provided to help you install the patch 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.
Installing and Uninstalling CWM 15.3.00 P1 • Security Profiles Before CWM 15.3.00 P1, a CWM user had to have a valid UNIX user because the user was authenticated against UNIX when he or she logged in to the CWM. As of CWM 15.3.00 P1, a new feature has been added to support CWM login without depending on UNIX user accounts. With the new procedure, you add and configure users using the Security Manager.
Installing and Uninstalling CWM 15.3.00 P1 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.
Installing and Uninstalling CWM 15.3.00 P1 Backing Up the Existing Database Use this procedure to back up the existing database to preparation for installing the patch. You should back up the database in case a problem exists with Informix. Step 1 Find a location with enough space and create a directory at this location. In the examples below the directory is called . In each command below, substitute the name you assigned.
Installing and Uninstalling CWM 15.3.00 P1 Step 6 Remove the disk1 directory if it exists: # rm -rf disk1 Step 7 Decompress the compressed tar files and # gunzip 15.3.00-P1_CWM.tar.gz # tar xvfp 15.3.00-P1_CWM.tar Step 8 Execute the InstallCWM153Patch1.csh script: # ./InstallCWM153Patch1.
Installing and Uninstalling CWM 15.3.00 P1 Verifying and Restoring Your Saved Database If Informix did not come back online after restarting the CWM, use this procedure to restore the database you saved before you installed Patch 1. (The output of onstat –d is in /usr/users/svplus//onstat.out for reference. For example, /usr/users/svplus/DBExports153/ where is DBExports153.
Installing and Uninstalling CWM 15.3.
Installing and Uninstalling CWM 15.3.00 P1 Installing the SSC Patch Use this procedure to install the SSC patch only if you are using the SSC machine. The patch must be installed on an SSC machine. Step 1 Log in to the SSC machine as user root: # su Step 2 Download or copy the compressed tar file to the local directory, such as /tmp: # cp 15.3.00-P1_SSC.tar.
Installing and Uninstalling CWM 15.3.00 P1 Step 5 Remove the disk1 directory if it exists: # rm -rf disk1 Step 6 Decompress the compressed tar file and untar the tar file: # gunzip 15.3.00-P1_SSM.tar.gz # tar xvfp 15.3.00-P1_SSM.tar Step 7 Execute the InstallSSM153Patch1.csh script: # ./InstallSSM153Patch1.csh Step 8 Exit from root. Installing the RTM Proxy Patch Use this procedure to install the RTM Proxy Patch on the CWM machine.
Creating a CWM Auto-Restart Shell Script Step 9 When prompted, follow the application instructions. Step 10 When you have finished installing the RTM Proxy Patch software, exit from root. Uninstalling Patch 1 The patch installation process installs an uninstall script in the /usr/users/svplus directory for the CWM and in the /usr/users/wandest directory for WANDEST.
Installing WANDEST 2.7.00, Patch 1 # Running Guard process ... as svplus echo "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 Step 5 To save your changes while using the vi editor, press Esc, colon (:), then wq!. Provide execute permissions for /etc/rc3.
Installing WANDEST 2.7.00, Patch 1 Installing the WANDEST Server Patch Use this procedure to install the WANDEST Server patch. Confirm that the WANDEST Client has been stopped before installing patches on the WANDEST server. Step 1 Log in to the CWM as an “svplus” user. Step 2 Stop the core. Step 3 Run the /usr/users/svplus/scripts/get_dbschema.ksh: # cd /usr/users/svplus/scripts # ./get_dbschema.ksh A wd_dbschema_tmpl file is created in the /usr/users/svplus/tmp directory.
SNMP Service Agent Trap Limitation Step 3 Change to the local directory that contains the compressed tar files: # cd /tmp Step 4 Remove the disk1 directory: # rm -rf disk1 Step 5 Decompress the compressed tar file and untar the tar file: # gunzip wandest2.7.00-P1_wdclient.tar.gz # tar -xvfp wandest2.7.00-P1_wdclient.tar Step 6 Run the installation script to install the patch: # ./InstallWDC27Patch1.csh Step 7 Exit from root.
Caveats Caveats This section lists known and resolved issues in the CWM 15.3.00 P1 and WANDEST 2.7 software: Known issues in the CWM 15.3.00 P1—Table 24 on page 47 Issues resolved in CWM 15.3.00 P1—Table 25 on page 47 Table 24 Known Issues in CWM 15.3.00 P1 Bug ID Description Details and Workaround CSCek45023 Lines in list window are superimposed, The workaround is to use the Web client. which causes a mixed image. CSCek49830 SCTs cannot be deleted from the CWM.
Related Documentation Table 25 Issues Resolved in CWM 15.3.
Obtaining Documentation, Support, and Security Guidelines • CWM Automated Bulk Provisioning Guide, 15.3.00 • Release Notes for the Cisco WAN Modeling Tools, 15.3.00 • Cisco WAN Modeling Tools User Guide, 15.3.00 The Cisco WAN 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 the CWM supports and that are certified in this release.
Obtaining Documentation, Support, and Security Guidelines Release Notes for the Cisco WAN Manager, Release 15.3.00 P1 50 OL-11190-01, Rev.