Table Of Contents
Mobile Wireless Fault Mediator Release 2.2.1 - Patch A - E Software Release Notes
System Configuration Requirements
Cisco Mobile Wireless Fault Mediator 2.2.1 Features
Supported Hardware Platforms in MWFM 2.2.1
Supported Release Matrix for Platforms
MWFM2.2.1 TCP/IP Port Assignments
Caveats for Mobile Wireless Fault Mediator 2.2.1
Open Caveats—Mobile Wireless Fault Mediator 2.2
Closed Caveats in MWFM2.2.1 Patch D
How to use Incremental Discovery
Closed Caveats in MWFM2.2.1 Patch E
Obtaining Technical Assistance
Mobile Wireless Fault Mediator Release 2.2.1 - Patch A - E Software Release Notes
April 20, 2004
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 Mobile Wireless Fault Mediator 2.2.1, which forms a part of CiscoWorks 2000 for Mobile Wireless bundle, describe the features provided in Release 1.2.
For a list of the software caveats that apply to MWFM, see the "Caveats for Mobile Wireless Fault Mediator 2.2.1" section.
Contents
These release notes include the following topics:
•
•
•
About the CW4MW Release 1.2
CiscoWorks2000 for Mobile Wireless (CW4MW) is a suite of EMS applications that enhances the delivery of new mobile wireless services leveraging Cisco Mobility Platforms. It is comprised of:
•
•
•
•
•
LAN Management
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.
Routed WAN Management
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.
Access Point Name Management
For GPRS Networks only, the 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
Mobile Wireless Fault Mediator provides alarm filtering and correlation to the Gateway GPRS Support Node (GGSN) routers, Packet Data Serving Node routers in CDMA2000 networks, Mobile Wireless Routers (MWR1900) in an all IP-RAN network, and their neighboring Catalyst switches. In addition, it seamlessly integrates with Network and Service-layer Fault OSS to provide a complete network.
CiscoView
CiscoView for Cisco Devices is another Web based package for supporting the Wireless devices like GGSN, PDSN and MWR1900. This primarily provides a graphical representation of the device and indicates the state and status of the device's components such as ports, power supplies, etc.
CW4MW release 1.2.1 does not support a standalone version. The user has to install CW2000 solution CDs (either LMS bundle or RWAN bundle) along with CW4MW CDs including MWFM CD and APN manager CD.
For additional information on LMS & RWAN bundle refer to the following website:
http://www.cisco.com/warp/public/44/jump/ciscoworks.shtml
System Configuration Requirements
Table 1 lists the minimum system configuration needed for running CiscoWorks2000 Mobile Wireless Suite.
Note
Cisco Mobile Wireless Fault Mediator 2.2.1 Features
MWFM is a feature-rich device layer solution that provides alarm filtering and correlation of Cisco Wireless Support Nodes (PDSN/GGSN) and their neighboring Catalyst Switches. This release also supports the Mobile Wireless Router (MWR1900) in an all IP-RAN Wireless network. MWFM uses complex mathematics to solve the change monitoring problem allowing network management products such as Fault MoM to support networks that are experiencing the phenomenal growth imposed by the boom in Mobile Internet traffic.
Supported Hardware Platforms in MWFM 2.2.1
MWFM2.2.1 support the following devices:
•
•
•
•
•
Supported Release Matrix for Platforms
Table 3 lists the supported releases.
Table 3 Supported Release Matrix
GGSN
1.4/3.0
72xx
PDSN
1.0/1.0.1
75xx
PDSN
1.0.2/1.1
72xx
HomeAgent
1.0/1.1
72xx
MWR1900
1.0
19xx
At the time of release, the following Cisco IOS images are supported by MWFM2.2.1:
•
rsp-g5isv-mz.121-3.XS
•
rsp-g5isv-mz.121-5.XS
rsp-g5isv-mz.121-5.XS1
rsp-g5is-mz.121-5.XS5
•
c7200-g5is-mz.r11.0718
•
c7200-g5is-mz.122-2.XC
c7200-g5is-mz.122-2.XC1
•
c7200-g5js-mz.122-7.4
•
c7200-g5js-mz.122-4.MX
•
c7200-is-mz.122-2.XC
c7200-is-mz.122-2.XC1
•
mwr1900-i-mz.02182002
•
mwr1900-i-mz.122-8.MC2d
Notes and Cautions
MWFM 2.2.1
•
For Root Cause analysis to report correctly the MWFM Server has to be renamed to fully qualified name (FQN). This shall be of the type <mwfm_server>.<domain_name>.com
•
All the devices should be configured to send traps in v1 format to MWFM2.1. Refer to the Cisco website for SNMPv1 configuration details.
http://www.cisco.com/univercd/home/home.htm
MWFM2.2.1 can send out only SNMPv1 traps to Northbound/Westbound NMS.
Northbound/West Bound NMS should be configured to listen to SNMPv1 traps
•
Note
•
MWFM will be configured to use port 45000 automatically. The user will have to manually configure DFM to forward device traps to MWFM on port 45000.
•
When MWFM is installed, it 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 or HPOV. The user must configure RTM or HPOV to listen for device traps from the MWFM trapmux.
•
When MWFM is installed, it will be configured to use port 162. The trapmux supplied with MWFM must be configured to listen to device traps on port 162, and MWFM needs to be reconfigured to listen on port 45000. Forward these traps to MWFM and RTM or HPOV. Configure RTM or HPOV to listen for device traps from the MWFM trapmux.
•
The user name and password for executing riv_oql queries are 'admin', and '<BLANK>'
•
In the event an ARP table reports the same MAC address for multiple interfaces on the MWFM server, MWFM will not discover the devices properly.
To resolve this problem follow the steps listed below.
Step 1
Step 2
ok> setenv local-mac-address? true
Step 3
ok> reset
•
User can turn on this capability by editing
$RIV_HOME/etc/DistSchema.cfg.
The following steps show what needs to be done.
Step 1
insert into listeners.snoopers values ('TrapEvents1', 'Events', '<domain name>', 'Dist=1 AND EventName<>"EventTrap"','TrapAdapt1', [{ }]);Step 2
insert into listeners.snoopers values('TrapEvents1', 'Events','<domain name>', 'Dist=1', 'TrapAdapt1', [{ }]);The above changes should be redone if a new NMS is added or modified using the configuration GUI.
•
rivExtraInfo field is truncated if it exceeds 256 characters.
•
•
•
•
MWFM2.2.1 TCP/IP Port Assignments
The following TCP/IP ports are used by the applications in CW4MW1.2.1 suite.
MWFM 2.2.1 Trapmux
tcp/162
MWFM 2.2.1 Trap Monitor
tcp/45000
TIBCO/Rendezvous daemon
tcp/45001
MWFM 2.2.1 Trap Finder
tcp/45002
RTM
udp/395 (default udp/162)
DFM
udp/9000 (default udp/162)
Caveats for Mobile Wireless Fault Mediator 2.2.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. 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.2.1.
Note
Open Caveats—Mobile Wireless Fault Mediator 2.2
This section documents possible unexpected behavior by CiscoWorks2000 for Mobile Wireless and describes only severity 1 and 2 caveats and select severity 3 caveats.
Bug ID and Description
•
Symptom—AOC Browser - Fault Rule editor window comes up blank. Conditions: In the AOC Browser window click on the Methods icon under Fault the Fault Rule editor window comes up as a blank window
Workaround—Add the correlation rules by modifying the AOC files directly using a text editor.
•
Symptom—MWFM riv2trap memory utilization too high.
Workaround—There are no known workarounds.
•
Symptom—amos and riv_m_agents get restarted after rediscovery. Incoming events (new alarm/clear) might be lost after rediscovery.
Workaround—none
•
Symptom—MWFM does not clear unknown traps after 24 hours.
Workaround—Unknown traps can be cleared either via Java API or by executing the following OQL :
|mwfm20:1> delete from mojo.events where EventType=0;|mwfm20:2> send;
•
Symptom—CISCO-STP-EXTENSION-MIB related traps are not translated by MWFM.
Condition—When unprocessed traps are enabled.
Workaround—Perform the following steps to resolve this problem:
Step 1
Step 2
Step 3
Step 4
Step 5
Step 6
•
Symptom—MWFM Trap might not be correctly decoded on some NMS.
Condition—rivLocation,rivContact,rivAssignedTo Varbinds missing from MWFM trap.
Workaround—Using text editor, modify RiverSoftTraps.mib (located in/opt/CSCOpx/objects/mwfm/mib directory) as follows:
Step 1
.rivEventTrap TRAP-TYPEENTERPRISE riversoftVARIABLES {rivSequentialID,rivEntityName,rivCreateTime,rivDescription,rivCauseType,rivEventId,rivLocation,rivSeverity,rivExtraInfo,rivClassName,rivEventName,rivEventType,rivContact,rivAssignedTo,rivAcknowledged,rivCorrelatedId,rivEventGroupId,rivActionGlyph,rivOccurred,rivActionType,rivAgentAddress,rivInternalAction
Step 2
•
Symptom—MWFM does not cache Alarms.
Condition—When at the startup time, the user responds with "y" to the following prompt..."Do you want to delete the old MWFM Alarms (y/n):[n]"
Workaround—Do not respond with "y" to the above question. If you already responded with "y", then you can recover out of it by following the procedure described below.
Step 1
Step 2
Step 3
•
Symptom—The MWFM 2.2.1 is not processing direct syslogs from devices. Not all devices support the Syslog traps For example, GGSN do not send syslog traps despite configuring the router with snmp-server enable traps syslog. Homeagent does not support Flash traps not Syslog traps.
Workaround—None
•
Symptom—The import database takes in only one RO community string defined in MWFM IF there are multiple RO community strings defined in MWFM, they are not handled during import and therefore RME will fail to manage those devices.
Workaround—Manually modify the community Strings for the device via RME GUI interface.
Appendix APatch A
New Features/Fixes in MWFM2.2.1 Patch A:
•
•
Install Instructions
Step 1
# gunzip -c MWFM_2.2.1_Patch_A.tar.gz | tar -xvf -Step 2
# cd disk2Step 3
# ./patchadd.shThe MWFM 2.2.1 Patch A will be installed. Make sure that you start MWFM after installing the patch.
Uninstall Instructions
Step 1
# gunzip -c MWFM_2.2.1_Patch_A.tar.gz | tar -xvf -Step 2
# cd disk2Step 3
# ./patchrm.shThe MWFM 2.2.1 Patch A will be removed. Make sure that you start MWFM after un-installing the patch.
Patch B
New Features/Fixes in MWFM2.2.1 Patch B:
•
•
•
This patch also includes contents of MWFM 2.2.1 Patch A:
•
•
Install Instructions
Step 1
# gunzip -c MWFM_2.2.1_Patch_B.tar.gz | tar -xvf -Step 2
# cd disk2Step 3
# ./patchadd.shThe MWFM 2.2.1 Patch B will be installed. Make sure that you start MWFM after installing the patch.
Un-install Instructions
Step 1
# gunzip -c MWFM_2.2.1_Patch_B.tar.gz | tar -xvf -Step 2
# cd disk2Step 3
# ./patchrm.shThe MWFM 2.2.1 Patch B will be removed. Make sure that you start MWFM after un-installing the patch.
Patch C
New Features/Fixes in MWFM2.2.1 Patch C:
•
•
•
The following has been done to resolve CSCea77743:
•
•
–
–
HSRP Monitoring)
Note
–
•
–
Note
This Patch also includes contents of MWFM2.2.1 Patch B:
•
•
•
This Patch also includes contents of MWFM2.2.1 Patch A:
•
•
Latest Patches
For information on the latest MWFM patches, direct your browser to:
http://www.cisco.com/cgi-bin/tablebuild.pl/fault-med
Install Instructions
Step 1
# gunzip -c MWFM_2.2.1_Patch_C_mmddyy.tar.gz | tar -xvf -Step 2
# cd disk2Step 3
# ./patchadd.shThe MWFM 2.2.1 Patch C will be installed. Make sure that you start MWFM after installing the patch.
Uninstall Instructions
Step 1
# gunzip -c MWFM_2.2.1_Patch_C_mmddyy.tar.gz | tar -xvf -Step 2
# cd disk2Step 3
# ./patchrm.shThe MWFM 2.2.1 Patch C will be removed. Make sure that you start MWFM after un-installing the patch.
HSRP Monitoring
Sample mini-rmon commands for HSRP monitoring are listed below.
rmon event 3 log trap public description "Router now active" owner ciscormon event 4 log trap public description "Router now standby" owner ciscormon alarm 2 cHsrpGrpEntry.15.1.1 180 absolute rising-threshold 6 3falling-threshold 5 4 owner ciscormon alarm 3 cHsrpGrpEntry.15.2.2 180 absolute rising-threshold 6 3falling-threshold 5 4 owner ciscoPatch D
New Features in MWFM2.2.1 Patch D:
•
•
•
•
•
•
a.
b.
c.
d.
e.
f.
•
Follow the instructions below to enable the logging.
Step 1
Step 2
Step 3
{rulename = 'UnknownTrapDeleteFromUnknown',... snipped for clarity ...
change_events = [// {// action = {// actionvalues = [// "Description = eval(text,'CAT(`Timed Delete: `,&&Description)')"// ],// filter="EventId=eval(int,'&&EventId')"// },// actionfilter="EventId=eval(int,'&&EventId')"// }... snipped for clarity ...
],}Step 4
{action = {actionvalues = ["Description = eval(text,'CAT(`Timed Delete: `,&&Description)')"],filter="EventId=eval(int,'&&EventId')"},actionfilter="EventId=eval(int,'&&EventId')"}Step 5
# cd /opt/CSCOpx/objects/mwfm/cache# rm *Classes*Step 6
Closed Caveats in MWFM2.2.1 Patch D
•
•
•
•
•
Notes & Cautions
•
•
Follow the instructions below to change the Ping Poll Frequency.
Step 1
Step 2
Step 3
{ // Ping pollPollDefState=0,... snipped for clarity ...
Severity=3,Description="eval(text,'CAT(`Ping fail on device `,this->EntityName)')",Location="",Contact="",EventName="pingFail",Frequency=900,Threshold= "",ThreshFailList={},... snipped for clarity ...
},Step 4
Frequency=60,Step 5
# cd /opt/CSCOpx/objects/mwfm/cache# rm *Classes*Step 6
•
–
–
–
Install Instructions
Step 1
# gunzip -c MWFM_2.2.1_Patch_D_mmddyy.tar.gz | tar -xvf -Step 2
# cd disk2Step 3
# ./patchadd.shThe MWFM 2.2.1 Patch D will be installed. Make sure that you start MWFM after installing the patch.
Uninstall Instructions
Step 1
# gunzip -c MWFM_2.2.1_Patch_D_mmddyy.tar.gz | tar -xvf -Step 2
# cd disk2Step 3
# ./patchrm.shThe MWFM 2.2.1 Patch D will be removed. Make sure that you start MWFM after un-installing the patch.
Patch E
New Features/Fixes in MWFM2.2.1 Patch E:
•
•
•
Incremental Discovery
MWFM supports two ways of discovering devices in a Network.
•
•
MWFM Full discovery is intended for discovering the devices in a Network for the very first time when MWFM is installed. However, there are situations wherein some devices do not get discovered during Full Discovery cycle for various reasons. For example:
•
•
•
•
•
To discover and monitor such kind of devices, MWFM Incremental Discovery can be used.
How to use Incremental Discovery
Primarily three steps are involved in discovering device via MWFM Incremental Discovery.
•
•
•
Step 1
There are two ways to identify these devices by doing the following:
a.
Open the /opt/CSCOpx/objects/mwfm/scripts/list_of_devices.txt using any text editor.
Note
b.
12.12.12.4
12.12.12.7
c.
Open the /opt/CSCOpx/objects/mwfm/scripts/master_device_list.txt file in some text editor.
d.
12.12.12.1
12.12.12.2
12.12.12.3
12.12.12.4
12.12.12.5
12.12.12.6
12.12.12.7
12.12.12.8
12.12.12.9
e.
# cd /opt/CSCOpx/objects/mwfm
# ksh
# . ./mwfm.kshrc
# cd scripts
# cd /opt/CSCOpx/objects/mwfm/scripts
# ./find_undiscovered_devices.sh
This script will compare the devices in master_device_list.txt with the one MWFM is currently monitoring. The devices which are not currently discovered/monitored by MWFM will be written to "list_of_devices.txt"
Step 2
The devices that need to be incrementally discovered have been identified, the user can invoke incremental discovery as follows:
# pwd
/opt/CSCOpx/objects/mwfm/scripts
# ./incremental_disco.sh
The devices in the list_of_device.txt will be submitted to MWFM Incremental Discovery for further processing.
Step 3
Issue the following commands to determine if MWFM Incremental discovery has finished or not.
# cd /opt/CSCOpx/objects/mwfm/logs.WIRELESS
# grep Completed ctrl.log
Phase 0 Completed Fri Apr 9 06:40:59 2004
Phase 1 Completed Fri Apr 9 06:42:33 2004
Phase 2 Completed Fri Apr 9 06:42:33 2004
Last Phase Completed Fri Apr 9 06:42:38 2004
Phase -1 Completed Fri Apr 9 06:44:45 2004
If following string "Phase -1 Completed" is observed towards the end, then that implies that incremental discovery has finished.
Note
MWFM Discovery uses the inband data channel to gather device information. Hence, during high traffic times, it is quite possible that a device may not get discovered if the discovery packets get dropped.
That SNMP being UDP based is sometimes unreliable. MWFM Discovery relies on SNMP to gather Device information. Hence due to the unreliable nature of SNMP/UDP, MWFM may not be able to successfully gather device information and hence may drop the device in the middle of the discovery cycle.
It is quite possible that the device that MWFM is trying to discover is down or there is some kind of mis-configuration due to which MWFM is not able to discover the device. In such situations, it is recommended that configuration of the device be checked. Please also ensure that the device is pingable and that device does respond to SNMP queries.
Install Instructions
Step 1
# gunzip -c MWFM_2.2.1_Patch_E_mmddyy.tar.gz | tar -xvf -Step 2
# cd disk2Step 3
# ./patchadd.shThe MWFM 2.2.1 Patch E will be installed.
Note
Note
Uninstall Instructions
Step 1
# gunzip -c MWFM_2.2.1_Patch_E_mmddyy.tar.gz | tar -xvf -Step 2
# cd disk2Step 3
# ./patchrm.shThe MWFM 2.2.1 Patch E will be removed.
Note
Closed Caveats in MWFM2.2.1 Patch E
•
•
•
•
•
•
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
•
•
•
•
Reference Guide•
•
Obtaining Documentation
The following sections explain how to obtain documentation from Cisco Systems.
World Wide Web
You can access the most current Cisco documentation on the World Wide Web at the following URL:
Translated documentation is available at the following URL:
http://www.cisco.com/public/countries_languages.shtml
Documentation CD-ROM
Cisco documentation and additional literature are available in a Cisco Documentation CD-ROM package, which is shipped 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 through an annual subscription.
Ordering Documentation
Cisco documentation is available in the following ways:
•
http://www.cisco.com/cgi-bin/order/order_root.pl
•
http://www.cisco.com/go/subscription
•
Documentation Feedback
If you are reading Cisco product documentation on Cisco.com, you can submit technical comments electronically. Click Leave Feedback at the bottom of the Cisco Documentation home page. After you complete the form, print it out and fax it to Cisco at 408 527-0730.
You can e-mail your comments to bug-doc@cisco.com.
To submit your comments by mail, use the response card behind the front cover of your document, or write to the following address:
Cisco Systems
Attn: Document Resource Connection
170 West Tasman Drive
San Jose, CA 95134-9883Obtaining Technical Assistance
Cisco provides Cisco.com as a starting point for all technical assistance. Customers and partners can obtain documentation, troubleshooting tips, and sample configurations from online tools by using the Cisco Technical Assistance Center (TAC) Web Site. Cisco.com registered users have complete access to the technical support resources on the Cisco TAC Web Site.
Cisco.com
Cisco.com is the foundation of a suite of interactive, networked services that provides immediate, open access to Cisco information, networking solutions, services, programs, and resources at any time, from anywhere in the world.
Cisco.com is a highly integrated Internet application and a powerful, easy-to-use tool that provides a broad range of features and services to help you to
•
•
•
•
•
You can self-register on Cisco.com to obtain customized information and service. To access Cisco.com, go to the following URL:
Technical Assistance Center
The Cisco TAC is available to all customers who need technical assistance with a Cisco product, technology, or solution. Two types of support are available through the Cisco TAC: the Cisco TAC Web Site and the Cisco TAC Escalation Center.
Inquiries to Cisco TAC are categorized according to the urgency of the issue:
•
•
•
•
Which Cisco TAC resource you choose is based on the priority of the problem and the conditions of service contracts, when applicable.
Cisco TAC Web Site
The Cisco TAC Web Site allows you to resolve P3 and P4 issues yourself, saving both cost and time. The site provides around-the-clock access to online tools, knowledge bases, and software. To access the Cisco TAC Web Site, go to the following URL:
All customers, partners, and resellers who have a valid Cisco services contract have complete access to the technical support resources on the Cisco TAC Web Site. The Cisco TAC Web Site requires a Cisco.com login ID and password. If you have a valid service contract but do not have a login ID or password, go to the following URL to register:
http://www.cisco.com/register/
If you cannot resolve your technical issues by using the Cisco TAC Web Site, and you are a Cisco.com registered user, you can open a case online by using the TAC Case Open tool at the following URL:
http://www.cisco.com/tac/caseopen
If you have Internet access, it is recommended that you open P3 and P4 cases through the Cisco TAC Web Site.
Cisco TAC Escalation Center
The Cisco TAC Escalation Center addresses issues that are classified as priority level 1 or priority level 2; these classifications are assigned when severe network degradation significantly impacts business operations. When you contact the TAC Escalation Center with a P1 or P2 problem, a Cisco TAC engineer will automatically open a case.
To obtain a directory of toll-free Cisco TAC telephone numbers for your country, go to the following URL:
http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml
Before calling, please check with your network operations center to determine the level of Cisco support services to which your company is entitled; for example, SMARTnet, SMARTnet Onsite, or Network Supported Accounts (NSA). In addition, please have available your service agreement number and your product serial number.
This document is to be used in conjunction with the documents listed in the "Related Documentation" section.
CCIP, CCSP, the Cisco Arrow logo, the Cisco Powered Network mark, Cisco Unity, Follow Me Browsing, FormShare, and StackWise are trademarks of Cisco Systems, Inc.; Changing the Way We Work, Live, Play, and Learn, and iQuick Study are service marks of Cisco Systems, Inc.; and Aironet, ASIST, BPX, Catalyst, CCDA, CCDP, CCIE, CCNA, CCNP, Cisco, the Cisco Certified Internetwork Expert logo, Cisco IOS, the Cisco IOS logo, Cisco Press, Cisco Systems, Cisco Systems Capital, the Cisco Systems logo, Empowering the Internet Generation, Enterprise/Solver, EtherChannel, EtherSwitch, Fast Step, GigaStack, Internet Quotient, IOS, IP/TV, iQ Expertise, the iQ logo, iQ Net Readiness Scorecard, LightStream, Linksys, MGX, MICA, the Networkers logo, Networking Academy, Network Registrar, Packet, PIX, Post-Routing, Pre-Routing, RateMUX, Registrar, ScriptShare, SlideCast, SMARTnet, StrataView Plus, Stratm, SwitchProbe, TeleRouter, The Fastest Way to Increase Your Internet Quotient, TransPath, and VCO are registered trademarks of Cisco Systems, Inc. and/or its affiliates in the United States and certain other countries.
All other trademarks mentioned in this document or Website are the property of their respective owners. The use of the word partner does not imply a partnership relationship between Cisco and any other company. (0402R)
Copyright © 2004, Cisco Systems, Inc. All rights reserved
