Guest

Cisco WAN Manager

Release Notes for the Cisco WAN Manager, 15.3.00 P3

  • Viewing Options

  • PDF (224.5 KB)
  • Feedback
Release Notes for the Cisco WAN Manager, Release 15.3.00, Patch 3

Table Of Contents

Release Notes for the Cisco WAN Manager, Release 15.3.00, Patch 3

Contents

New Features and Enhancements

Supported Releases

Certified Releases

CWM Packaging and Basic Data

Installing the Solaris Patches

Before You Begin Installing Patches

DST Patches

Solaris Patch Installation Procedure

Installing and Uninstalling CWM 15.3.00, Patch 3

Backing Up the CWM Server Database

Installing the CWM Server Patch

Restoring the Saved Database

Installing the SNMP Agent Patch

Installing the SSC Patch

Installing the SSM Patch

Installing the RtmProxy Patch

Uninstalling Patch 3

Installing WANDEST 2.7.00, Patch 3

Installing the WANDEST Server Patch

Installing the WANDEST Client Patch

Caveats

Resolved Issues

Related Documentation

Obtaining Documentation, Support, and Security Guidelines


Release Notes for the Cisco WAN Manager, Release 15.3.00, Patch 3


September 2007

Rev. A0

These release notes are for use with the Cisco WAN Manager (CWM) 15.3.00, Patch 3 software release that supports MGX, BPX, and IGX switches. You can access the switch documentation at this website:

http://www.cisco.com/en/US/products/hw/switches/tsd_products_support_category_home.html

Contents

New Features and Enhancements

Supported Releases

Certified Releases

CWM Packaging and Basic Data

Installing the Solaris Patches

Installing and Uninstalling CWM 15.3.00, Patch 3

Caveats

Related Documentation

Obtaining Documentation, Support, and Security Guidelines

New Features and Enhancements

In CWM 15.3.00, Patch 3, a feature was added to enable an "offline" (nonproduction) CWM to manage switches that the "online" (production) machine cannot manage because excessive traps are being received from them.

With this option, the OSS can continue receiving traps from these switches through the offline CWM. These nodes are part of the offline CWM dummy network and are not managed by the online CWM.

The following are the prerequisites for using the feature:

When you install the online CWM, you must select this option during the installation. You do not need to install the option on the offline CWM.

RtmProxy is expected to be installed on the online and offline CWM machines, and the OSS must be registered with RtmProxy on both machines.

The offline CWM is expected to be running with a dummy network.

Configure the nts.conf and OfflineCWM.conf parameters as follows:

For the online CWM server:

In /usr/users/svplus/config/nts.conf:

HIGH_TRAP_NODE_AUTO_SHUTOFF = 1 (enable)

Offline management is enabled automatically because you chose the option during installation. It is displayed as "CWM_OFFLINE_MGMT 1."

In /usr/users/svplus/config/OfflineCWM.conf:

- Before starting the core, specify "OfflineCwmIP" (and make sure that it can be reached).

- By default, "TrapResilencyMgrPort is set to "3500."

- Set the port number to any unused port.

For the offline CWM server:

In /usr/users/svplus/config/nts.conf, set HIGH_TRAP_NODE_AUTO_SHUTOFF = 0 (disable).

When excessive traps are received from a switch, the online CWM marks these traps as unmanageable by deregistering with the switch and generating the newly defined CWM trap "28502." Because the online CWM stops receiving traps from the deregistered and unmanaged switch, the OSS does not receive traps for that switch.

That switch is added as a standalone node to the offline CWM, which syncs up with the switch and starts managing the node so the OSS will continue receiving traps from the switch.

As soon as the fault on the switch is fixed, the switch can be added to the online CWM using ntsControl and choosing option "ubtn." After adding the node, the online CWM starts sending trap 28502 and deletes the node from the offline CWM. The offline CWM automatically deregisters with switch.

The new trap 28502 has been added to the newly created Group 27 in the trapFilters.conf file. This trap should not be added to any other groups. The CWM forwards this trap to both RtmProxy and port 162.

Supported Releases

Table 1 shows the BPX, IGX, and MGX switch platforms and releases that the CWM 15.3.00, Patch 3 software supports. See also Certified Releases.

(For a list of the hardware that the CWM supports, see the CWM 15.3.00 release notes. No new hardware was added in Rel. 15.3.00.)

Table 1 Switch Platforms and Releases Supported by CWM 15.3.00, Patch 3 

Switch Platform
Supported Software Release

Existing WAN switching products, including the Cisco IGX 8400 series and the Cisco BPX 8600 series

9.2.33-9.2.43
9.3.05-9.3.51
9.4.00-9.4.12

SES PNNI Controller

3.0.10-3.0.25
4.0.00-4.0.15
4.0(15.201)

MGX 8220

4.1.07-4.1.12
5.0.12-5.0.20

MGX 8230, 8250 and 8850 (PXM1)

1.1.40-1.1.42
1.2.00-1.2.13
1.2.20-1.2.22
1.3.00-1.3.12
1.3.14
3.0.10, 3.0.2.0

MGX8830/B (PXM45/C)

5.1.20
5.2.00
5.3.00, 5.3.10, 5.3.20

MGX 8830 and 8850 (PXM1E)
MGX 8850 (PXM45)

3.0.23-3.0.25
4.0.00-4.0.17
5.0.00-5.0.20
5.1.20
5.2.00
5.3.00, 5.3.10, 5.3.20

MGX 8830/B, 8850, 8880, 8950 (PXM45) switches

5.2.00
5.3.00, 5.3.10, 5.3.20

MGX 8880 (PXM45)

5.0.00-5.0.20
5.1.20
5.2.00
5.3.00, 5.3.10, 5.3.20

MGX 8950 (PXM45)

2.1.76-2.1.81
3.0.23-3.0.25
4.0.00-4.0.17
5.0.00-5.0.20
5.1.20
5.2.00
5.3.00 and 5.3.10


Certified Releases

Table 2 lists the certified card, shelf, or switch software releases for CWM 15.3.00, Patch 3 software. Although CWM 15.3.00, Patch 3 supports other releases, the releases listed in the table are the specific releases that were tested for CWM 15.3.00, Patch 3. See Supported Releases.

Table 2 Releases Tested with CWM 15.3.00, Patch 3 

Card, Shelf, or Switch
Tested Software Release

BPX/IGX switch software

9.3.51
9.4.10, 9.4.12

BPX SES Shelf

3.0.25
4.0.15, 4.0(15.201)

MGX 8220 Shelf

4.0.06
4.1.12
5.0.20

MGX 8230, 8250, and 8850 (PXM1) switches

1.2.22
1.3.10, 1.3.12, 1.3.14
3.0.10, 3.0.20

MGX 8830 and 8850 (PXM1E) switches

5.0.20
5.1.00
5.3.00, 5.3.10, 5.3.20

MGX 8830/B, 8850, 8880, 8950 (PXM45) switches

5.2.00
5.3.00, 5.3.10, 5.3.20

RPM-PR and RPM-XF cards

Cisco IOS 12.3(2)T6
Cisco IOS 12.4(4th)
Cisco IOS 12.4(6)T2

VISM-PR cards

3.3.10, 3.3.20, 3.3.25, 3.3.30

VXSM cards

5.0.70
5.2.00, 5.2.50
5.3(0.200), 5.3.10, 5.3.20


CWM Packaging and Basic Data

This section describes the CWM and associated software and CDs. The required software for the CWM system are the CWM Server software, Solaris platform and required patches, CWM Java Client, and a Web browser to launch the online help. See Table 3. All CWM features are available until the 45-day evaluation period expires.

HP OpenView is another optional software package that you can order directly from Hewlett-Packard. It is used with CWM SNMP Service Agent to view the Event Log through the Event Browser. It is not required for any CWM procedures or for an Statistics Collection Manager-Standalone (SCMSA) workstation. This CWM release supports HP OpenView 6.2, 6.3, 7.0, and 7.5. For additional information, see the CWM installation guide.

Refer to the CWM 15.3.00 release notes for the following:

Requirements for the CWM Server, Standalone Statistics Collector (SSC), Standalone Statistics Manager (SSM), and CWM Java Client, HP OpenView, and Informix

Basic requirements for workstations, graphics, video, and firewalls

Note that a minimum of JRE 1.4.2_11 is required for this patch.

When you launch the CWM, you can also access additional information about getting started. In the CWM Client Launcher, you can click the Help tab for this information:

Accessing online help and documentation

Installing Java Web Start

Installing on Solaris and Windows platforms

Configuring Netscape for Using Web Start on Solaris platforms

Table 3 CWM and Associated Software 

Software and
Documentation
CD
Description

CWM Server

Informix 9.4

Orbix

Java Development Kit (JDK)

CWM Server

The CWM Server software is part of the CWM package and required for installation.

As part of the JDK, CWM Java Client is deployed using Java Web Start, which is a deployment tool that uses the Java Network Launching Protocol (JNLP) to manage Java applications from a centralized server. These applications are cached and run locally on Windows 98, NT, 2000, or XP or on a Solaris client.

Java Web Start is bundled with the Java 2 Platform, Standard Edition (J2SE), v1.4.2 and later. To start using Web Start applications, download the latest Java Runtime Environment (JRE) for your operating system from this website:

http://java.sun.com/j2se/1.4.2/download.html

A minimum of JRE 1.4.2_11 is required.

CWM documentation (PDFs)

gzip

CWM Documentation

Part of the CWM package.

The gzip utility is used to decompress the gz files. The command is gzip -d.

CWM SNMP Service Agent

Service Agent

This CD must be ordered separately from the CWM Client/Server package CD set.

Although SNMP Service Agent is not required to run the CWM, it can be used to provide provisioning and fault-management capabilities to the upper layer OSS.

It is not required for an SCMSA workstation.

The SNMP Service Agent CD also contains the tar file for updating the CIC so that it can function with the CWM system.

CWM SCMSA

Standalone Statistics Collection Manager

This CD must be ordered separately from the CWM package CD set.

The SCMSA software includes the Cisco WAN Database Extraction and Synchronization Tool (WANDEST) client software (for communicating with the CWM server) and the Informix server software.

RtmProxy for the SCM application

RtmProxy for SCM Application

This application is included on a separate CD with the Statistics Collection Manager (SCM) software only when you order that software. It is meant to be installed only with the SSM and not on systems using the Service Agent. If you have already installed the Service Agent software and you attempt to install this application, you will see errors because the ~/config/process.conf file has duplicate entries for the RtmProxy.

To install the RtmProxy for SCM application from the CD, refer to the CWM installation guide.

Cisco WANDEST

WANDEST Server

WANDEST Client

This two-CD set must be ordered separately from the CWM set.

The WANDEST software enables the CWM system to communicate with the operational support system (OSS) or other telco applications. The OSS applications use WANDEST to keep their databases synchronized with the CWM (stratacom) database.

Cisco Automated Bulk Provisioning (ABP) Tool

Cisco Automated Bulk Provisioning Tool

This CD must be ordered separately from the CWM set.

The ABP tool is a time-based provisioning system that enables you to schedule connection and port provisioning jobs. It is standalone software that resides on top of the CWM.

Cisco WAN Modeling Tools

Cisco WAN Modeling Tools

This CD must be ordered separately from the CWM set.


Installing the Solaris Patches

This section shows the Solaris patches that you must install on the CWM and the patches that Cisco recommends you install. Install these patches after you install the Solaris operating system.

In the Solaris patch sections that follows, Daylight Savings Time (DST) patch data has been added.

See these subsections:

Before You Begin Installing Patches

DST Patches

Solaris Patch Installation Procedure

Before You Begin Installing Patches

For best results, follow these Sun recommendations before you begin installing 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 4) 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 on the SPARC platform that can cause problems with Informix during startup: patches 112963-21 through 112963-24.

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.

Table 4 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


DST Patches

If you are using U.S. time zones, you must install the appropriate Solaris patches for change in the Daylight Saving Time (DST), which results from DST changes in the U.S. Energy Policy Act of 2005.

As recommended in Sun Microsystems Alert ID 102775, countries not affected by the DST rule changes are still advised to install the latest patches for the DST rule changes. Note that countries may switch to other time zones programmatically to meet an application-specific configuration or computation need. These other time zones may include ones that are affected by the DST changes.

You can review the Sun Microsystems Alert ID 102775 and access the needed patches at this Sun website:

http://sunsolve.sun.com/search/document.do?assetkey=1-26-102775-1

These are the required DST patches for Solaris 9 DST patches for the SPARC platform:
Solaris 9 with time-zone patch 113225-03 or later and libc patch 112874-33 or later

After you install the time-zone and libc patches, reboot the machine, as Sun recommends.

Solaris Patch Installation Procedure

Use this procedure and sequence to install the Solaris patches, which assumes that the Solaris operating system is already installed.


Step 1 Verify the already installed patches. To do this, use the Solaris showrev -p command.

Step 2 Go to the SunSolve Patch Access website to access the patches:

http://sunsolve.Sun.COM/pub-cgi/show.pl?target=patches/patch-access

(If you have a SunSpectrum contract, you can also access patches from SunService.)

Step 3 Install the Kernel Patch 12 for Solaris 9. See Table 4 for the correct version number.

Step 4 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 5 Install the recommended patches, as needed and desired. (Several of these recommended patches may require a service contract with Sun.)


Installing and Uninstalling CWM 15.3.00, Patch 3

This section describes how to install CWM 15.3.00, Patch 3, and provides links to other general installation data.

To install, upgrade, or uninstall the CWM software, review the CWM installation guide. You can access all CWM documentation at this URL:

http://www.cisco.com/en/US/products/sw/netmgtsw/ps2340/tsd_products_support_series_home.html

For information on installation configurations, compatibility, notes, and limitations, refer to the CWM 15.3.00 release notes:

http://www.cisco.com/en/US/products/sw/netmgtsw/ps2340/prod_release_note09186a008068db7e.html

In this section, see these subsections:

Backing Up the CWM Server Database

Installing the CWM Server Patch

Restoring the Saved Database

Installing the SNMP Agent Patch

Installing the SSC Patch

Installing the SSM Patch

Installing the RtmProxy Patch

Uninstalling Patch 3

Installing WANDEST 2.7.00, Patch 3

Table 5 lists the contents of the Patch 3.

Table 5 CWM 15.3.00, Patch 3 Contents

Component
File

CWM

15.3.00-P3_CWM.tar.gz

SNMP Agent

15.3.00-P3_SNMPAgent.tar.gz

SSC

15.3.00-P3_SSC.tar.gz

SSM

15.3.00-P3_SSM.tar.gz

WANDEST Server 2.7.00, Patch 3

wandest2.7.00-P3_wdserver.tar.gz

WANDEST Client 2.7.00, Patch 3

wandest2.7.00-P3_wdclient.tar.gz

RTMProxy

Note Install this on the CWM Server only if you are using SSM, but not using the SNMPAgent.

15.3.00-P3_RTMProxy.tar.gz


Backing Up the CWM Server Database

Use this procedure to back up the existing database to prepare for installing the patch. You should back up the database in case a problem exists with Informix.


Step 1 Log in as svplus:

hostname# su -u svplus 

The system prompts you for the svplus password.

Step 2 If they are not stopped already, stop the core processes.

Step 3 Perform a coldstart (drops all network data so you will export only the user data in each database):

# coldstart 

Step 4 Stop the "Guard" process by executing the script /usr/users/svplus/scripts/cleanGD.

Step 5 Stop the "AuditLogger" process by executing the script /usr/users/svplus/scripts/cleanAL.

Step 6 Create a /usr/users/svplus/tmp/dbexports directory, as shown in the following example. (Please ensure there is at least 2 GB in this directory.)

mkdir /usr/users/svplus/dbexports 

Step 7 Go to this /usr/users/svplus/tmp/dbexports directory, as shown below:

cd /usr/users/svplus/tmp/dbexports 

Step 8 Copy the /usr/users/svplus/etc/svplus.version into the /usr/users/svplus/tmp/dbexports directory, as shown below:

cp /usr/users/svplus/etc/svplus.version /usr/users/svplus/tmp/dbexports/svplus.version 

Step 9 Export the stratacom, statsdb, and scmdb databases. Save a copy of the dbexport.out file if necessary. (To copy dbexport.out, you need to log in as "root.")

dbexport stratacom (stratacom.exp directory is created in the /usr/users/svplus/tmp/dbexports directory. Save a copy of the dbexport.out file if necessary.)

dbexport statsdb (statsdb.exp directory is created in the /usr/users/svplus/tmp/dbexports directory. Save a copy of the dbexport.out file if necessary.)

dbexport scmdb (scmdb.exp directory is created in the /usr/users/svplus/tmp/dbexports directory. Save a copy of the dbexport.out file if necessary.)

Step 10 Capture the output of the onstat -d command and save it to the /usr/users/svplus/<dbexport-location>/onstat.out file for future reference, as shown in the following example:

onstat -d > /usr/users/svplus/dbexports153/onstat.out  

where,

<dbexport-location> = dbexports153

Step 11 Archive the /usr/users/svplus/tmp/dbexports directory, as shown in the following example:

cd /usr/users/svplus/tmp 
tar cvf /tmp/<server name>.tar dbexports/* 

Step 12 Use the FTP facility to copy this tar file to another system for safekeeping.


Installing the CWM Server Patch

Use this procedure to install the CWM Server patch.


Step 1 Stop statistics collection and disable statistics on the VXSM.

Step 2 Log in to the CWM server as user root:

# su 

Step 3 Stop the core.

Step 4 Download or copy the compressed tar files for the CWM server to a temporary location, such as /tmp:

# cp 15.3.00-P3_CWM.tar.gz /tmp 

Step 5 Change to local directory that contains the compressed tar files:

cd /tmp 

Step 6 Remove the disk1 directory if it exists:

rm -rf disk1 

Step 7 Unzip the compressed tar files and untar them:

# gunzip 15.3.00-P3_CWM.tar.gz
# tar xvfp 15.3.00-P3_CWM.tar  

Step 8 Execute the InstallCWM153Patch3.csh script:

# ./InstallCWM153Patch3.csh 

Step 9 Designate if you want to use install the patch using the InstallShield GUI or the console mode and continue the installation.

Step 10 If WANDEST Server Rel. 2.7 is installed on this machine, follow these steps to install WANDEST Server 2.7.00, Patch 3:

a. Stop the wdclient and exit root.

b. Run the /usr/users/svplus/scripts/get_dbschema.ksh shell script, as follows:

cd /usr/users/svplus/scripts
/get_dbschema.ksh 

A wd_dbschema_tmpl file is created in /usr/users/svplus/tmp directory. Edit this file to un-comment any of the tables listed that you want triggers in.

c. Download or copy the wandest2.7.00-P3_wdserver.tar.gz to the local directory, such as /tmp.

d. Change to the local directory, unzip the compressed tar files, and untar them:

# gunzip wandest2.7.00-P3_wdserver.tar.gz 
# tar -xvfp wandest2.7.00-P3_wdserver.tar 

e. Switch to root.

f. Run the installation script to install the patch, as follows:

# ./InstallWD27Patch3.csh 

Step 11 Exit from root.


Restoring the Saved Database

If Informix did not come back online after restarting the CWM, use this procedure to restore the database that you saved before you installed the patch.

(The output of the onstat -d command is located in the /usr/users/svplus/<dbexport-location>/onstat.out file; for example, /usr/users/svplus/dbexports153/onstat.out.)


Step 1 Log in to the workstation as root:

# su 

Step 2 Go to the /usr/users/informix92/etc directory:

# cd /usr/users/informix92/etc 

Step 3 Follow these steps only if you have configured a separate raw partition for the Informix physical log:

a. Open the onconfig file for editing:

# vi onconfig 

b. Change the PHYSDBS <phydbs> line to the following:

PHYSDBS rootdbs

c. Change the PHYSFILE <size> line to the following:

PHYSFILE 20000 

d. Save the onconfig file and exit from the editor.

Step 4 Go the /usr/users/svplus/scripts/Install directory:

# cd /usr/users/svplus/scripts/Install 

Step 5 Run these commands in the order shown below:

./dbmode
./dbinit
./dbonmode
./dbonspace 

Step 6 If you have the file AddPhyLog in /usr/users/svplus/scripts/Install, do these steps:

./AddPhyLog
./RestartInf 

Step 7 If you have the file dbaddchunk in /usr/users/svplus/scripts/Install, do these steps:

./dbaddchunk 

Step 8 Exit from root.

Step 9 Check if you have configured a separate partition for datadbs using the onstat -d command:

onstat -d 

Step 10 If a separate partition exists, execute these commands to import the database. If no separate partition exists for datadbs, go to Step 11:

# dbimport stratacom -d datadbs -i <dbexport-location> 
# dbimport statsdb -d datadbs -i <dbexport-location>
# dbimport scmdb -d datadbs -i <dbexport-location> 

Step 11 If no separate partition exists for datadbs, use these commands to import the stratacom, statsdb, and scmdb databases and the WANDEST database if you had a WANDEST server previously:

# dbimport stratacom -i <dbexport-location>
# dbimport statsdb -i <dbexport-location>
# dbimport scmdb -i <dbexport-location>
# dbimport wandest -i <dbexport-location> 


Installing the SNMP Agent Patch

Use this procedure to install the CWM SNMPAgent (ServiceAgent) patch.


Step 1 Log in to the CWM server as user root:

# su 

Step 2 Stop the core.

Step 3 Download or copy the compressed tar file for ServiceAgent to the local directory, such as /tmp:

# cp 15.3.00-P3_SNMPAgent.tar.gz /tmp  

Step 4 Change to local directory that contains the compressed tar files:

# cd /tmp 

Step 5 Remove the disk1 directory if it exists:

# rm -rf disk1 

Step 6 Unzip the compressed tar file and untar it:

# gunzip 15.3.00-P3_SNMPAgent.tar.gz
# tar xvfp 15.3.00-P3_SNMPAgent.tar  

Step 7 Execute the installation patch script:

# ./InstallAgent153Patch3.csh 

Step 8 Designate if you want to install the patch using the InstallShield GUI or the console mode and continue with the installation.

Step 9 When you have finished installing the SNMP Agent Patch software, exit from root.


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-P3_SSC.tar.gz /tmp  

Step 3 Change to local directory that contains the compressed tar file:

# cd /tmp 

Step 4 Remove the disk1 directory if it exists:

# rm -rf disk1 

Step 5 Unzip the compressed tar file and untar it:

# gunzip 15.3.00-P3_SSC.tar.gz
# tar xvfp 15.3.00-P3_SSC.tar  

Step 6 Execute the InstallSSC153Patch3.csh script:

# ./InstallSSC153Patch3.csh 

You are prompted to choose the installation method.

Step 7 Designate if you want to install the patch using the InstallShield GUI or the console mode and continue the installation.

Step 8 When you have finished installing the SSC patch, exit from root.


Installing the SSM Patch

Use this procedure to install the SSM Patch only if you are using the SSM machine. The patch must be installed on a SSM machine.


Step 1 Stop stats collection and disable stats on VXSM.

Step 2 Log in to the SSM machine as user root:

su 

Step 3 Download or copy the compressed tar file to the local directory, such as /tmp:

# cp 15.3.00-P3_SSM.tar.gz /tmp 

Step 4 Change to local directory that contains the compressed tar files:

# cd /tmp 

Step 5 Remove the disk1 directory if it exists:

# rm -rf disk1 

Step 6 Unzip the compressed tar file and untar it:

# gunzip 15.3.00-P3_SSM.tar.gz 
# tar xvfp 15.3.00-P3_SSM.tar 

Step 7 Execute the InstallSSM153Patch3.csh script:

# ./InstallSSM153Patch3.csh 

Step 8 Exit from root.


Installing the RtmProxy Patch

Use this procedure to install the RtmProxy Patch on the CWM machine.

Install the patch only on a CWM machine and only on a CWM machine that has no installed SNMP agent and that SSM has used for statistics management.

The purpose of the RtmProxy Patch tar file is to work only with the SSM. It is not required for configuring a northbound interface. If the Service Agent is installed, do not install the RtmProxy patch. It is not needed.


Step 1 Log in to the CWM as user root:

# su 

Step 2 Stop the core.

Step 3 Download or copy the compressed tar file to the local directory, for example, /tmp:

# cp 15.3.00-P3_RTMProxy.tar.gz /tmp 

Step 4 Change to local directory that contains the compressed tar files:

# cd /tmp 

Step 5 Remove the disk1 directory:

# rm -rf disk1 

Step 6 Unzip the compressed tar file and untar it:

# gunzip 15.3.00-P3_RTMProxy.tar.gz
# tar xvfp 15.3.00-P3_RTMProxy.tar 

Step 7 Execute the InstallRTM153Patch3.csh script:

# ./InstallRTM153Patch3.csh 

You are prompted to choose the installation method.

Step 8 Designate if you want to install the patch using the InstallShield GUI or the console mode and continue the installation.

Step 9 When you have finished installing the RtmProxy patch, exit from root.


Uninstalling Patch 3

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.

When you access the uninstall wizard, you are asked for the backup file location that you provided when you installed the CWM or WANDEST initially.

Installing WANDEST 2.7.00, Patch 3

If you have standalone WANDEST server and client workstations, follow the procedures in these sections to install and uninstall the patches:

Installing the WANDEST Server Patch

Installing the WANDEST Client Patch

Table 5 lists the contents of WANDEST 2.7.00, Patch 3.

Table 6 WANDEST 2.7.00, Patch 3 Contents

Component
File

WANDEST Server

wandest2.7.00-P3_wdserver.tar.gz

WANDEST Client

wandest2.7.00-P3_wdclient.tar.gz


Installing the WANDEST Server Patch

Use this procedure to install the WANDEST Server patch.

Before installing the patches, ensure that the WANDEST Client has been stopped.


Step 1 Log in to the CWM as an "svplus" user and stop the core.

Step 2 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. Edit this file and un-comment out the tables that you want triggers in it.

Step 3 Switch to root (for example, su):

su 

Step 4 Download or copy the compressed tar file to the local directory, for example, /tmp:

# cp wandest2.7.00-P3.wdserver.tar.gz /tmp 

Step 5 Change to the local directory that contains the compressed tar files:

# cd /tmp

Step 6 Remove the disk1 directory:

# rm -rf disk1 

Step 7 Unzip the compressed tar file and untar it:

# gunzip wandest2.7.00-P3_wdserver.tar.gz 
# tar -xvfp wandest2.7.00-P3_wdserver.tar 

Step 8 Run the installation script to install the patch:

# ./InstallWDS27Patch3.csh 

Step 9 Exit from root and perform a coldstart:

coldstart 

Step 10 Open a new terminal to start the core.


Installing the WANDEST Client Patch

Use this procedure to install the WANDEST Client patch.


Step 1 Log in to the WANDEST client as user root.

Step 2 Download or copy the compressed tar file for WANDEST client to a local directory, such as /tmp:

# cp wandest2.7.00-P3_wdclient.tar.gz /tmp

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 Unzip the compressed tar file and untar it:

# gunzip wandest2.7.00-P3_wdclient.tar.gz
# tar -xvfp wandest2.7.00-P3_wdclient.tar

Step 6 Run the installation script to install the patch:

# ./InstallWDC27Patch3.csh

Step 7 Exit from root.


Caveats

This section lists known and resolved issues in the CWM 15.3.00, Patch 3 and WANDEST 2.7 software:

Known issues in the CWM 15.3.00, Patch 3—Table 7

Issues resolved in CWM 15.3.00, Patch 3—Table 8

Issues resolved in CWM 15.3.00, Patch 2.1—Table 9

Issues resolved in CWM 15.3.00, Patch 2—Table 10

Table 7 Known Issues in CWM 15.3.00, Patch 3

Bug ID
Description
Details and Workaround

CSCek57474

When the customer is using the MGX 8850 with VISM cards running 3.3(25.201), the VISM end points are displayed initially as "active." After the line fails, the status changes as expected to "failed."

However, after the line is restored to active, the Config Center continues to shows the VISM end points as "failed."

The workaround is to initiate a Level 2 resync from the Diagnostics Center for that particular node.


Resolved Issues

Table 8 shows the issues that were resolved in the CWM 15.3.00, Patch 3 software.

Also, an error in the CWM 15.3.00 Database Interface Guide has been corrected in the CWM 15.4.00 guide. The data type for the par_max_cost object in the cesm_connection and connection tables has been changed from "smallint" to "integer."

Table 8 Issues Resolved in CWM 15.3.00, Patch 3 

Bug ID
Bug Headline

CSCek73734

CLI adding, modifying, and deleting of SPVCs are not reflected in CWM.

CSCsi42157

sdbroker coredump.

CSCsi48161

Node resync option in DC is disabled when launching from NM.

CSCsi70504

Chassis View alarm for PXM card is inconsistent.

CSCsi79963

EMEX coredump.

CSCsj07764

Unable to create ABR1 XPVC with AXSM-XG ENNI XLMI trunk.

CSCsj28537

Unable to create ABR XPVC over AXSM-XG ENNI.

CSCsj69937

Throws exception while creating UNIX independent user.

CSCsj70394

Unable to get the logical port using svMapLogicalPort for AXSM-XG card.


Table 9 shows the issues that were resolved in the CWM 15.3.00, Patch 2.1 software.

Table 9 Issues Resolved in CWM 15.3.00, Patch 2.1 

Bug ID
Bug Headline

CSCek56923

Statsreader shows negative and huge values for XG counters.

CSCek61933

Cannot upgrade from AXSM-b/e to AXSM-XG due to custom SCT name.

CSCek64404

AXSM-XG missing connection stats CLP0/1 cells discarded ingress and egress.

CSCek66417

Allow deletion of invalid prefRoutes from ServiceAgent due to MPG reconfig.


Table 10 lists issues resolved in the CWM 15.3.00, Patch 2 software.

Table 10 Issues Resolved in CWM 15.3.00, Patch 2 

Bug ID
Bug Headline

CSCek48635

Custom default value(80) for LoCLP on BPX trunk for abr-fs conn.

CSCek51015

Sct Save as Operation not working properly.

CSCek52079

Unable to get svMapLogicalPort for MPSM-16-T1E1.

CSCek53121

Port alarm severity mismatch between node and CWM.

CSCek53622

Line alarm severity mismatch between node and CWM.

CSCek54440

Usage of minimum available sct id in CWM.

CSCek55520

BERT trap handling.

CSCek56061

The Node Rename does not join user connections.

CSCek56077

In NM GUI - Clicking the Edit menu throws a Java NullPointerException.

CSCek56197

DC Gui:-Paths in loopback not getting updated for MPSM-T3E3-155 card.

CSCek57027

Cannot set loopback on BXM-OC3 line from Diagnostic Center.

CSCek57038

Trap 60566 should have ifName in HPOV trapd log.

CSCek57176

Memory leak in CWM (ILMITopoc/nts sdbroker etc).

CSCek57905

BPX in mode-1 during syncup.

CSCek58147

Image downloader GUI does not show PXM-1E image for 8830/PXM-1E.

CSCek59246

getnext on FRSM returns the same object for svFRPort table.

CSCek59712

DC Server Purify test shows multiple memory usage.

CSCek61715

MGX5320MIB release related change in CC and Agent

CSCek61988

MPSM16 ATM Connection stats - CLP0/1 ingress/egress discard stats missing.

CSCek62092

IfName needs to be included in HPOV trapd report for MPX and IMA Port traps

CSCek62302

MIB CHECK-IN for MGX5320

CSCin80338

SNMPWalk on svFrPortTable fails for MPSM-8T1 on POPEYE1.

CSCin94963

In SCT GUI, associate/download dialog box resizing should be proper.

CSCir00103

For admin user in SecMgrGui some of the permission bits are not given.

CSCir00255

Audit trail not getting updated on download of objects in alarm list.

CSCir00347

DC GUI: Typo in Loopback Confirmation dialog.

CSCir00391

Audit logging is not done while closing Finder & Statistics Report apps.

CSCir00393

SCT should not allow deletion of associated sct files

CSCir00396

ArrayIndexOutOfBoundsException on console when launching multiple SCT GUIs.

CSCir00406

Associate dialog box to be updated with new node entry

CSCir00414

SCT should allow modifying the CoSB MinimumPriority value for AXSMXG cards.

CSCir00415

Clicking on Change SCT Name throws NullPointerException on console.

CSCir00417

In new SCT GUI, Contents submenu is missing under Help menu.

CSCir00462

SCT:-NullPointerException on console while clicking ok in Associate Dialog.

CSCir00663

SCT file entry not getting deleted.

CSCir00733

DC: Inject errors/bitmap button is enabled for Insert; single bit is No error.

CSCir01100

VISM card: Most of the line parameters are updated as -1 in db for pop1.


Related Documentation

These documents comprise the CWM documentation set:

Release Notes for Cisco WAN Manager, 15.3.00, Patch 3

Cisco WAN Manager Installation Guide, 15.3.00

Cisco WAN Manager User Guide, 15.3.00 P1

Cisco WAN Manager Database Interface Guide, 15.3.00

Cisco WAN Manager SNMP Service Agent Guide, 15.3.00

Cisco WANDEST Installation and Reference, 2.7

You can access all CWM documentation at this website:

http://www.cisco.com/en/US/products/sw/netmgtsw/ps2340/tsd_products_support_series_home.html

These documents are also available on Cisco.com:

Release Notes for CWM Automated Bulk Provisioning, 15.3.00

CWM Automated Bulk Provisioning Guide, 15.3.00

Release Notes for the Cisco WAN Modeling Tools, 15.3.00 P2

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. In addition, a Guide to Cisco Multiservice Switch Documentation ships with your product.

You can access the MGX switch documentation at this website. See MGX Switches:

http://www.cisco.com/en/US/products/hw/switches/tsd_products_support_category_home.html

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.

Obtaining Documentation, Support, and Security Guidelines

For information on obtaining documentation and support, providing documentation feedback, security guidelines, recommended aliases, and general Cisco documents, see the monthly What's New in Cisco Product Documentation, which also lists all new and revised Cisco technical documentation, at this URL:

http://www.cisco.com/en/US/docs/general/whatsnew/whatsnew.html