Release Notes for CiscoWorks 2000 for Mobile Wireless Release 1.0.1

Table Of Contents

Release Notes for CiscoWorks2000 for Mobile Wireless Release 1.0.1

Contents

Introduction

System Requirements

Supported Hardware Platforms in MWFM 2.0.1

GGSN and PDSN Supported Releases

CW4MW TCP/IP Port Assignments

New Enhancements

Notes and Cautions

Limitations

Caveats for CiscoWorks2000 for Mobile Wireless Release 1.0.1

Open Caveats—CiscoWorks2000 for Mobile Wireless

Resolved Caveats

Related Documentation

Obtaining Documentation

World Wide Web

Documentation CD-ROM

Ordering Documentation

Documentation Feedback

Obtaining Technical Assistance

Cisco.com

Technical Assistance Center

Contacting TAC by Using the Cisco TAC Website

Contacting TAC by Telephone

Release Notes for CiscoWorks2000 for Mobile Wireless Release 1.0.1

---

November 21, 2001

78-13318-02

---

Note You can find the most current Cisco documentation on Cisco.com. This set of electronic documents may contain updates and modifications made after the hard-copy documents were printed.

---

These release notes for CiscoWorks2000 for Mobile Wireless describe the features provided in Release 1.0.1. These release notes are updated as needed.

For a list of the software caveats that apply to CiscoWorks2000 for Mobile Wireless, see the "Caveats for CiscoWorks2000 for Mobile Wireless Release 1.0.1" section.

Contents

These release notes include the following topics:

•Introduction

•System Requirements

•Notes and Cautions

•Limitations

•Caveats for CiscoWorks2000 for Mobile Wireless Release 1.0.1

•Related Documentation

•Obtaining Documentation

•Obtaining Technical Assistance

Introduction

CiscoWorks2000 for Mobile Wireless (CW4MW) is a suite of EMS applications that enhances the delivery of new mobile wireless services leveraging Cisco Mobility Platforms.

Table 1 describes the CW4MW components.

Table 1 CW4MW Applications and Functions 

Application	CW4MW Component	Function
LAN Management	CiscoWorks2000 LMS bundle, April refresh Not included in this package.	The LMS Bundle provides operationally focused applications for configuration, fault monitoring, and troubleshooting local networks. A browser interface provides easy-to-use access to topology maps, configuration services, and important system, device, and performance information. Because these applications are browser-accessible, administrators now have the freedom to access network tools anywhere from within the network. Additional detail about the CiscoWorks2000 LMS bundle and the RWAN bundle is provided at the following URL: http://www.cisco.com/warp/public/44/jump/ciscoworks.shtml
Routed WAN Management	CiscoWorks2000 RWAN bundle, April refresh Not included in this package.	The Routed WAN Management Solution Bundle provides a collection of powerful applications to configure, administer, monitor, and troubleshoot routed wide-area networks, thereby dramatically reducing their complexity. This suite of solution applications provides increased visibility into network behavior and quickly identifies performance bottlenecks and long-term performance trends. It also provides sophisticated configuration tools to optimize bandwidth and utilization across expensive and critical WAN links in the network. Additional detail about the CiscoWorks2000 LMS bundle and the RWAN bundle is provided at the following URL: http://www.cisco.com/warp/public/44/jump/ciscoworks.shtml
Access Point Name Management	Cisco Access Point Name Manager 1.1 (For GPRS networks only) Included in this package.	The Cisco APN Manager is a carrier-class provisioning solution that automates the configuration process of APNs within a GPRS network to support centralized GGSN access. The Cisco APN Manager provides flow-through management of APNs within the GPRS Support Node (GSN) complex to support centralized Public Data Network (PDN) access. It provides a CORBA interface to view and configure APN profiles in the GGSN and Domain Name Server (DNS) resource record from Network Management Systems (NMS) and other 3rd party Operations Support Systems (OSS).
Fault Mediation	Cisco Mobile Wireless Fault Mediator (MWFM) 2.0.1: Included in this package.	The Mobile Wireless Fault Mediator provides alarm filtering and correlation to the Gateway GPRS Support Node (GGSN) routers or Packet Data Serving Node (PDSN) routers in CDMA2000 networks and their neighboring Catalyst switches. In addition, it seamlessly integrates with Network and Service-layer Fault OSS to provide a complete network monitoring solution.

System Requirements

Table 2 lists the minimum server requirements for installing and running CiscoWorks2000 for Mobile Wireless.

Table 2 System Configuration Requirements  

Requirement	Solaris Server
Hardware	Sun Ultra 60 workstations
Operating system	Solaris 2.7
Memory (RAM)	2 GB RAM
Available disk drive space	18 GB hard disk
Processor	2 x 450 MHz
Swap space	2 x RAM
Operating environment	CDE

CD-One from either the LMS or RWAN solution must be installed prior to MWFM and/or APN Manager installation.

CNR installation and configuration is also required for APN Manager.

Supported Hardware Platforms in MWFM 2.0.1

MWFM 2.0.1 supports the following Catalyst switches, directly connected to a GGSN or a PDSN:

•Catalyst 55XX family of switches

•Catalyst 6XXX family of L3 switches

•GGSN and PDSN routers (72xx, 75xx)

GGSN and PDSN Supported Releases

Table 3 lists the GGSN and PDSN supported releases.

Table 3 GGSN and PDSN Supported Release Matrix 

	Release	Routers
GGSN	1.4	72xx
PDSN	1.0/1.0.1	75xx
PDSN	1.0.2	72xx

At the time of release, the following PDSN Cisco IOS images are supported by MWFM2.0.1:

•The Cisco IOS Images (PDSN 1.0)

rsp-g5isv-mz.121-3.XS

•The Cisco IOS Images (PDSN 1.0.1)

rsp-g5isv-mz.121-5.XS

rsp-g5isv-mz.121-5.XS1

•The Cisco IOS Images (PDSN 1.0.2)

c7200-g5is-mz.r11.0718

CW4MW TCP/IP Port Assignments

The following TCP/IP ports are used by the applications in CW4MW:

MWFM 2.0.1 Trapmux	tcp/162
MWFM 2.0.1 Trap Monitor	tcp/45000
TIBCO/Rendezvous daemon	tcp/45001
MWFM 2.0.1 Trap Finder	tcp/45002
RTM/TD	udp/395 (when udp/162 is in use)
DFM	udp/9000 (when udp/162 is in use)

New Enhancements

•The user does not need to specify the MWFM Domain Name when he starts MWFM using the start_mwfm script.

•start_mwfm script now automatically extracts the currently configured MWFM Domain from the configuration files.

•The Startup script reports the progress of the MWFM startup.

•change_mwfm_domain script can be used to change the MWFM Domain Name.

•linkFlap is now automatically cleared after 30 minutes.

•Trapmux is automatically launched by riv_ctrl.

•Unknown traps are not forwarded to the SNMP Manager.

Notes and Cautions

MWFM 2.0.1

•MWFM2.0.1 currently supports SNMP version 1 traps.

All the devices should be configured to send traps in v1 format to MWFM2.0.1. Please check the Cisco website for SNMPv1 configuration details:

http://www.cisco.com/univercd/home/home.htm

MWFM2.0.1 currently sends out SNMPv1 traps to SNMP managers and other Fault Management solution.

SNMP managers should be configured to listen to SNMPv1 traps.

•If DFM is installed prior to MWFM:

MWFM will be configured to use port 45000 automatically. It is recommended that the MWFM trapmux be used to forward traps to DFM & MWFM. The user should manually configure the MWFM Trapmux to listen for traps on port 162 and forward traps to MWFM on port 45000 and to DFM on port 9000. DFM should be reconfigured to listen for traps on port 9000.

Please visit the following URL for the configuration steps:

http://www.cisco.com/univercd/cc/td/doc/product/rtrmgmt/cw2000/dfm/dfm1_1/install/sol/solstart.htm#74220

•If RTM is installed prior to installing MWFM:

MWFM when installed will be configured to use port 45000. The trapmux supplied with MWFM must be configured to listen to device traps on port 162, and forward these traps to MWFM and RTM. The user must reconfigure RTM to listen for device traps from the MWFM trapmux.

Please visit the following URL for the configuration steps:

http://www.cisco.com/univercd/cc/td/doc/product/rtrmgmt/cw2000/fam_prod/netscout/7812486.htm#xtocid564724

•If MWFM is installed prior to RTM and DFM is not installed:

The trapmux supplied with MWFM must be configured to listen to device traps on port 162 and forward these traps to MWFM and RTM. Configure DFM & RTM to listen for device traps from the MWFM trapmux.

•AOC Browser documentation:

AOC Browser documentation is available for download from Cisco Connection Online. Please point your favorite web browser at:

http://www.cisco.com/warp/public/cc/pd/wr2k/cw4mw/

•Downloading MWFM 2.0.1 Java SDK

MWFM 2.0.1 Java SDK is available for download from Cisco Connection Online. Please point your web browser at:

http://www.cisco.com/warp/public/cc/pd/wr2k/cw4mw/

•Default MWFM Admin username and password:

Username: root

Password: ciscomwfm

APN Manager

Only the CNR GUI should be installed on the same server as CW4MW. The .CNR server should be installed on a different server.

Limitations

Either CNR Server or CNR Client should be installed before installing APN Manager. Please note that only CNR client can be installed in the same server as CW4MW.

Caveats for CiscoWorks2000 for Mobile Wireless Release 1.0.1

Caveats describe unexpected behavior in Cisco software releases. Severity 1 caveats are the most serious caveats; severity 2 caveats are less serious. Severity 3 caveats are moderate caveats, and only select severity 3 caveats are included in the caveats document.

This section contains only open and resolved caveats for CiscoWorks2000 for Mobile Wireless Release 1.0.1.

---

Note If you have an account with Cisco.com, you can use Bug Navigator II to find caveats of any severity for any release. To reach Bug Navigator II, log in to Cisco.com and click Software Center: Cisco IOS Software: Bug Toolkit: Bug Navigator II. Another option is to go to http://www.cisco.com/support/bugtools/.

---

Open Caveats—CiscoWorks2000 for Mobile Wireless

This section documents possible unexpected behavior by CiscoWorks2000 for Mobile Wireless and describes only severity 1 and 2 caveats and select severity 3 caveats.

•CSCdu32507

There is a known memory resource allocation issue with regard to a large number of events remaining in memory.

Workaround: Manually clear unknown events from database via Java API or OQL. Use the following steps to delete all the unknown traps:

a. Issue the following command:

#riv_oql -domain <INSERT_MWFM_DOMAIN_NAME> -service RivEvents -username root

-latency 6000000

(Please note that the '-' before each attribute is required)

b. Enter MWFM root password

c. Issue the following command to remove all the unknown events in the system:

>delete from mojo.events where EventName=EventTrap;

>send;

•CSCdu76490

riv_agent/Details agent cores during discovery. Occurs when /opt/CSCOpx/objects/mwfm/etc/ServiceData.cfg file gets null values in this file

vi ServiceData.cfg file and check if it contains nulls at the end of this file.

You will see:

"ServiceData.cfg" 9 lines, 474 characters, 2 nulls

Workaround: Retain the following information in the ServiceData.cfg file, delete the rest of the lines

and start a new discovery by running the start_mwfm <Domain_name>.

> vi ServiceData.cfg

-- Server data file - contains info on servers and the general multicast

-- address to use.

SERVICE:RivMulticastService DOMAIN:ANY_RIV_DOMAIN ADDRESS:225.13.13.13 PORT:33000

•CSCdv52289

Symptom: Correlation Rules implemented using the AOC Browser might get lost if Class files gets corrupted.

WorkAround: After modifying the correlation rules using the AOC Browser, copy the Class.Cache.activeClasses.<DOMAIN_NAME>,

Class.Cache.staticClasses.<DOMAIN_NAME> in the mwfm/cache/ directory to some backup directory. Incase the Class files in the cache

directory gets corrupted, then copy the Class files from the backup directory.

•CSCdv56736

Symptom: Sometimes, riv_m_agent for Trap cores during re-discovery.

Workaround: None.

•CSCdv88141

Symptom: In one of the corner cases, when MWFM 2.0 discovery ends before all monitoring agents get fully initialized, new devices may not be monitored. This may happen when only one or two devices are configured in disco config files.

Workaround: To avoid such situation you can modify the CtrlSchema.cfg file so that riv_disco starts only after riv_monitor is completely launched. It is recommended that for riv_disco, the dependsOn field should also include "riv_monitor" as follows:

insert into services.inTray

        ( serviceId, serviceName, domainName, argList, dependsOn, retryCount )

        values

        (

                0,

                "riv_disco",

                "SHARK",

                [ "-domain", "WIRELESS", "-latency", "6000000" ],

                [ "riv_class", "riv_model", "riv_monitor" ],

                0

        );

•CSCdv89061

Symptom: TIBCO Rendezous(rvd) process does not stop

Condition: When stop_mwfm is executed, it will not stop the rvd process

Workaround #1:

ps -ef |grep rvd

root    12     1  0 16:13:13 ?        0:20 rvd -listen tcp:45001

and kill this process by doing the following

pkill rvd

Workaround #2:

Add the following towards the end of stop_mwfm script.

pid=`ps -ef|grep -v grep|grep rvd | awk '{print $2}'`

[ "$pid" != "" ] && ( kill $pid; sleep 3;kill $pid) > /dev/null 2>&1 

Resolved Caveats

•CSCdv20955: Northbound MWFM2.0 trap contain incorrect SNMP version.

•CSCdv20969: Northbound MWFM2.0 trap contain invalid agent address.

•CSCdv27699: Traps from MWFM not seen on HPOV.

•CSCdv36720: riv_ctrl dies when CW2K Daemon Manager is stopped.

•CSCdv47296: The SNMPPollFail is not automatically cleared after 10 minutes.

•CSCdv43642: start_mwfm script incorrectly modifies the CtrlSchema.cfg file.

Related Documentation

The CiscoWorks2000 for Mobile Wireless documentation set is available online at:

http://www.cisco.com/univercd/cc/td/doc/product/rtrmgmt/cw2k4mw/index.htm

•Read Me First—CiscoWorks2000 for Mobile Wireless

•CiscoWorks2000 for Mobile Wireless Release Notes

•Cisco Mobile Wireless Fault Mediator Release 2.0.1; Fault Engine Reference Guide

•Cisco Mobile Wireless Fault Mediator Release 2.0.1; Topology and Platform Modeling
Reference Guide

•Cisco Access Point Name Manager Release 1.1; Application Programming Guide

•Cisco Mobile Wireless Fault Mediator Release 2.0.1; Java API Guide

Obtaining Documentation

The following sections provide sources for obtaining documentation from Cisco Systems.

World Wide Web

The most current Cisco documentation is available on the World Wide Web at http://www.cisco.com. Translated documentation can be accessed at http://www.cisco.com/public/countries_languages.shtml.

Documentation CD-ROM

Cisco documentation and additional literature are available in a CD-ROM package, which ships with your product. The Documentation CD-ROM is updated monthly and may be more current than printed documentation. The CD-ROM package is available as a single unit or as an annual subscription.

Ordering Documentation

Cisco documentation is available in the following ways:

•Registered Cisco Direct Customers can order Cisco product documentation from the Networking Products MarketPlace:

http://www.cisco.com/cgi-bin/order/order_root.pl

•Registered Cisco.com users can order the Documentation CD-ROM through the online Subscription Store:

http://www.cisco.com/go/subscription

•Nonregistered Cisco.com users can order documentation through a local account representative by calling Cisco corporate headquarters (California, USA) at 408 526-7208 or, in North America, by calling 800 553-NETS(6387).

Documentation Feedback

If you are reading Cisco products documentation on the World Wide Web, you can submit technical comments electronically. Click Feedback in the toolbar and select Documentation. After you complete the form, click Submit to send it to Cisco.

You can e-mail your comments to bug-doc@cisco.com.

For your convenience, many documents contain a response card behind the front cover for submitting your comments by mail. Otherwise, you can mail your comments to the following address:

Cisco Systems, Inc.
Document Resource Connection
170 West Tasman Drive
San Jose, CA 95134-9883

We appreciate your comments.

Obtaining Technical Assistance

The following sections provide sources for obtaining technical assistance from Cisco Systems.

Cisco.com

Cisco.com is the foundation of a suite of interactive, networked services that provides immediate, open access to Cisco information and resources at anytime, from anywhere in the world. This highly integrated Internet application is a powerful, easy-to-use tool for doing business with Cisco.

Cisco.com provides a broad range of features and services to help customers and partners streamline business processes and improve productivity. Through Cisco.com, you can find information about Cisco and our networking solutions, services, and programs. In addition, you can resolve technical issues with online technical support, download and test software packages, and order Cisco learning materials and merchandise. Valuable online skill assessment, training, and certification programs are also available.

Customers and partners can self-register on Cisco.com to obtain additional personalized information and services. Registered users can order products, check on the status of an order, access technical support, and view benefits specific to their relationships with Cisco.

To access Cisco.com, go to the following website:

http://www.cisco.com

Technical Assistance Center

The Cisco TAC website is available to all customers who need technical assistance with a Cisco product or technology that is under warranty or covered by a maintenance contract.

Contacting TAC by Using the Cisco TAC Website

If you have a priority level 3 (P3) or priority level 4 (P4) problem, contact TAC by going to the TAC website:

http://www.cisco.com/tac

P3 and P4 level problems are defined as follows:

•P3—Your network performance is degraded. Network functionality is noticeably impaired, but most business operations continue.

•P4—You need information or assistance on Cisco product capabilities, product installation, or basic product configuration.

In each of the above cases, use the Cisco TAC website to quickly find answers to your questions.

To register for Cisco.com, go to the following website:

http://www.cisco.com/register/

Cisco.com registered users who cannot resolve a technical issue by using the TAC online resource can open a case online by using the TAC Case Open tool at the following website:

http://www.cisco.com/tac/caseopen

Contacting TAC by Telephone

If you have a priority level 1(P1) or priority level 2 (P2) problem, contact TAC by telephone and immediately open a case. To obtain a directory of toll-free numbers for your country, go to the following website:

http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml

P1 and P2 level problems are defined as follows:

•P1—Your production network is down, causing a critical impact to business operations if service is not restored quickly. No workaround is available.

•P2—Your production network is severely degraded, affecting significant aspects of your business operations. No workaround is available.