Read Me First CiscoWorks2000 for Mobile Wireless, Release 1.0.1

Transcription

1 Read Me First CiscoWorks2000 for Mobile Wireless, Release This purpose of this document is: To introduce the CiscoWorks2000 for Mobile Wireless product. To list and describe the product components that are included in the product package. To list and describe the product components that are not included in the package but that might be prerequisites for installation and use of this product. To provide procedures and guidelines for installing all components of CiscoWorks2000 for Mobile Wireless on a Solaris 2.7 platform. To provide a list of related product documentation and instructions on where to access the documentation. Corporate Headquarters: Cisco Systems, Inc., 170 West Tasman Drive, San Jose, CA USA Copyright Cisco Systems, Inc. All rights reserved.

2 Overview of CiscoWorks2000 for Mobile Wireless Overview of CiscoWorks2000 for Mobile Wireless 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 2001 refresh The LMS Bundle provides operationally focused applications for configuration, fault monitoring, and troubleshooting local Not included in this package. 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: Routed WAN Management Access Point Name Management Fault Mediation CiscoWorks2000 RWAN bundle, April 2001 refresh Not included in this package. Cisco Access Point Name Manager 1.1 For GPRS networks only) Included in this package. Cisco Mobile Wireless Fault Mediator MWFM) 2.0.1: 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: 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). The Mobile Wireless Fault Mediator provides alarm filtering and correlation to the Gateway GPRS Support Node GGSN) routers or Packet Data Serving Node 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. 2

3 What Your Cisco APN Manager and MWFM Product Package Contains What Your Cisco APN Manager and MWFM Product Package Contains Your Cisco APN Manager and MWFM product package contains the following items: Read Me First CiscoWorks2000 for Mobile Wireless This document) Release Notes for CiscoWorks2000 for Mobile Wireless Release Warranty and Software License 2 CDs: The APN Manager CD contains the CSCOapman package. The components for ApnMan are JRE1.2 and Visigenics 4.1 for Java, which are shared from CD-ONE. The process manager of CD-One will control the ApnMan. The Mobile Wireless Fault Mediator CD contains the CSCOmwfm package, which includes the third party components JRE1.2 and Perl5.6 for MWFM Note If you don t have CiscoWorks2000 LMS or RWAN solutions, please contact your local Cisco representative. Related Documentation The CiscoWorks2000 for Mobile Wireless documentation set is available online at: Read Me First CiscoWorks2000 for Mobile Wireless Release Notes for CiscoWorks2000 for Mobile Wireless Release 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 3

4 Installation Prerequisites Installation Prerequisites 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. Table 3 shows the recommended order in which you should install CW4MW and related applications. Table 3 Order of Installation Task 1. Install CiscoWorks2000 CD One, 4th Edition. This typically takes about 40 minutes. 2. Install CW4MW Components a. APN Manager - Installation takes 5 to 15 minutes. b. MWFM Installation takes 5 to 15 minutes. 3. Install Java 2 SDK Standard Edition For Detailed and Custom Installation, Refer To Installing and Setting Up CiscoWorks2000 CD One, 4th Edition. Release Notes for CiscoWorks2000 CD One, 4th Edition for any last-minute updates). This document, Installing CiscoWorks2000 for Mobile Wireless section on page 5. This document, Installing the Java Development Kit section on page 16. 4

5 Installing CiscoWorks2000 for Mobile Wireless This section includes installation procedures for Installing APN Manager, page 5 Installing Mobile Wireless Fault Mediator 2.0.1, page 6 Installing the Java Development Kit, page 16 Installing APN Manager Step 1 Step 2 Step 3 Insert the CD named APN Manager into the Solaris 2.7 machine. From the user prompt, enter the following command to change to the cdrom0 directory: cd /cdrom/cdrom0 Enter the following command to launch the install script:./setup.sh As the installation begins, the screen will display a welcome banner similar to the following and the installation process will scroll on the monitor: ===== Started : Fri Nov 2 10:28:54 EDT 2001 ===== ===============- Software Install Tool Started. -===================== ===- Welcome to the Cisco Works for Mobile Wireless Setup program. ===== INFO: Checking group entry casusers... INFO: Checking user entry casuser... INFO: casuser for installable packages exists. INFO: No user added to the system. INFO: Use admin file /tmp/cscotmp/csco.admin. INFO: Waiting up to 10 minutes) for all our daemons to stop... INFO: OS major is 5 and OS minor is 7 INFO: OS major or minor patch version not set. INFO: Checking for syslog server... INFO: Using syslog facility, local1. INFO: /cdrom/cdrom0/packages/cscoapman/pkginfo INFO: /cdrom/cdrom0/info INFO: /cdrom/cdrom0/info/mwg INFO: Warning - No Any ADVANCED_CHOICE section in TOC-file. INFO: CSCOapman Loading properties from info files, working... Making a list of dependencies, working... INFO: performing prerequisite: CSCOapman: /cdrom/cdrom0/packages/cscoapman/ It is assumed that CNR is installed. Please provide the path where it is located:... Step 4 As shown in the last line of the previous screen sample, the install script prompts for the path where the CNR is installed. Enter the path. 5

6 Step 5 Step 6 Step 7 The installation continues, and the progress is displayed on the screen. When the installation is successfully completed, a message such as the following is displayed: Installation of <CSCOapman> was successful Finished: Fri Nov 2 10:52:06 EDT 2001 ===============- Software Install Tool Completed. -============== Enter the following command to change to the cdrom directory: cd /cdrom Eject the APN Manager CD. Installing Mobile Wireless Fault Mediator Step 1 Step 2 Step 3 Insert the Mobile Wireless Fault Mediator CD into the Solaris 2.7 machine. From the user prompt, enter the following command to change to the cdrom0 directory: cd /cdrom/cdrom0 Enter the following command to launch the install script:./setup.sh As the installation begins, the screen will display a welcome banner similar to the following and the installation process will scroll on the monitor: ===== Started : Fri Nov 2 10:38:14 EDT 2001 ===== ===============- Software Install Tool Started. -===================== ===- Welcome to the Cisco Works for Mobile Wireless Setup program. ===== INFO: Checking group entry casusers... INFO: Checking user entry casuser... INFO: casuser for installable packages exists. INFO: No user added to the system. INFO: Use admin file /tmp/cscotmp/csco.admin. INFO: Waiting up to 10 minutes) for all our daemons to stop... INFO: OS major is 5 and OS minor is 7 INFO: OS major or minor patch version not set. INFO: Checking for syslog server... INFO: Using syslog facility, local1. INFO: /cdrom/cdrom0#1/packages/cscomwfm/pkginfo INFO: /cdrom/cdrom0#1/info INFO: /cdrom/cdrom0#1/info/mwg INFO: Warning - No Any ADVANCED_CHOICE section in TOC-file. INFO: CSCOmwfm Loading properties from info files, working... 6

7 Making a list of dependencies, working... INFO: performing prerequisite: CSCOmwfm: /cdrom/cdrom0#1/packages/cscomwfm/ INFO: PORT NUMBER 162 NOT IN USE Adding property PORT162INUSE false RIV_HOME added DFM IS INSTALLED IN THIS MACHINE RTM IS INSTALLED IN THIS MACHINE CSCOmwfmtrap 45000/udp# TrapListeningPort CSCOmwfmrvd 45001/tcp# RVDProcessMWFM INFO: Sufficient memory RAM). INFO: Sufficient swap space. INFO: A recommended computer model. INFO: Recommended disk space 4 GB. Please refer to the INFO: prerequisites chapter of the install guide. INFO: total size MB) required = 166 COPYOUT_INROOT_MB=0 INFO: Sufficient disk space. Use of uninitialized value at /opt/cscopx/conf/cmf/bin/cmfenable.pl line 96, <PKGPARAM> chunk Use of uninitialized value at /opt/cscopx/conf/cmf/bin/cmfenable.pl line 113, <PKGPARAM> chunk Use of uninitialized value at /opt/cscopx/conf/cmf/bin/cmfenable.pl line 96, <PKGPARAM> chunk Use of uninitialized value at /opt/cscopx/conf/cmf/bin/cmfenable.pl line 96, <PKGPARAM> chunk Use of uninitialized value at /opt/cscopx/conf/cmf/bin/cmfenable.pl line 113, <PKGPARAM> chunk Use of uninitialized value at /opt/cscopx/conf/cmf/bin/cmfenable.pl line 96, <PKGPARAM> chunk Use of uninitialized value at /opt/cscopx/conf/cmf/bin/cmfenable.pl line 108, <PKGPARAM> chunk Use of uninitialized value at /opt/cscopx/conf/cmf/bin/cmfenable.pl line 108, <PKGPARAM> chunk Use of uninitialized value at /opt/cscopx/conf/cmf/bin/cmfenable.pl line 113, <PKGPARAM> chunk Use of uninitialized value at /opt/cscopx/conf/cmf/bin/cmfenable.pl line 113, <PKGPARAM> chunk WARNING: a datasource with the name cmf was already present. It will be replaced INFO: Starting database engine cmfeng to get database file version Attempting to allocate cache of 8200K INFO: Stop database engine cmfeng after testing database version INFO: /opt/cscopx/databases/cmf/cmf.db is in Sybase Adaptive Server format. /opt/cscopx/objects/db/conf/configureapp.pl installing userinfo application. INFO: This appname already exists; it is OK WARNING: a datasource with the name ani was already present. It will be replaced INFO: Starting database engine anieng to get database file version Attempting to allocate cache of 8200K INFO: Stop database engine anieng after testing database version INFO: /opt/cscopx/databases/ani/ani.db is in Sybase Adaptive Server format. INFO: CMFEnable.pl: wantsystem=1; wantnetwork=1 INFO: [EnableAndDisableBundles] will SystemEnable::Enable ProcCall: Start to enable system service... ProcRetn:...Done enabling system service. INFO: [EnableAndDisableBundles] will NetworkEnable::Enable INFO: result of CMF enable is 0 INFO: performing pkgadd -a /tmp/cscotmp/csco.admin -d /cdrom/cdrom0#1/packages CSCOmwfm Processing package instance <CSCOmwfm> from </cdrom/cdrom0#1/packages> 7

8 Mobile Wireless Fault Mediator sparc) Using </opt> as the package base directory. ## Processing package information. ## Processing system information. 2 package pathnames are already properly installed. ## Verifying disk space requirements. ## Checking for setuid/setgid programs. Installing Mobile Wireless Fault Mediator as <CSCOmwfm> ## Installing part 1 of 1. Step 4 Step 5 The installation continues, and the progress is displayed on the screen. When the installation is successfully completed, a message such as the following is displayed: Installation of <CSCOmwfm> was successful. application CSCOmwfm Mobile Wireless Fault Mediator INFO: Configuring JRun properties... syslog service starting. INFO: Testing syslog: sending a msg to local0.debug... INFO: waiting for 12 seconds for syslog to process a test message... Opening /tmp/cscotmp/cmfapppostinstall.log for logging Finished: Fri Nov 2 10:52:06 EDT 2001 ===============- Software Install Tool Completed. -============== The installation continues, and the progress is displayed on the screen. If you have installed RTM, DFM, HPOpenViewHPOV), or Traffic Director TD) on the machine where you install MWFM, you will see a message similar to the following: ===============- Software Install Tool Completed. -============== ===================- Possible Errors Encountered -=================== WARNING: a datasource with the name cmf was already present. It will be replaced WARNING: a datasource with the name ani was already present. It will be replaced WARNING: Installation has detected Cisco DeviceFaultManager in the same machine. There are known SNMP trap reception issues when DFM and MWFM are in the same machine. To resolve this issue, please refer to Read Me First - CW4MW Bundle document. When the installation is successfully completed, a message such as the following is displayed: Installation of <CSCOmwfm> was successful. application CSCOmwfm Mobile Wireless Fault Mediator INFO: Configuring JRun properties... syslog service starting. INFO: Testing syslog: sending a msg to local0.debug... INFO: waiting for 12 seconds for syslog to process a test message... Opening /tmp/cscotmp/cmfapppostinstall.log for logging Finished: Fri Nov 2 10:52:06 EDT 2001 ===============- Software Install Tool Completed. -============== 8

9 Step 6 Step 7 Enter the following command to change to the cdrom directory: cd /cdrom Eject the MWFM2.0.1 CD. Configuring Mobile Wireless Fault Mediator This section describes the tasks that the user needs to perform to configure and start up MWFM Network Information Needed During the Configuration Configuration Example Have the following information available before proceeding with the configuration: Networks/devices that need to be managed SNMP community strings on all the devices Telnet password for the Catalyst Switches IP address of the DNS server Location of Syslog file IP address of the SNMP Manager that will receive MWFM Faults Figure 1 and Table 4 provide sample network information for an MWFM configuration. 9

10 Figure 1 Sample Network for MWFM Configuration MWFM_Server /24 Eth Router_1 Eth /24 Catalyst65xx Eth /24 outer_ /24 HDLC / /24 Eth Router_3 LAN_ /24 Eth LAN_ Table 4 Sample Network Information Networks/devices to be managed SNMP community string public Catalyst Switch information IP address : Password : secret IP address of the DNS server Location of Syslog file /var/adm/messages IP address of the SNMP Manager

11 Configuration Process To Log on to the MWFM server and configure MWFM, perform the following steps: Step 1 Log on to the MWFM server with root privileges and change your directory with the command: cd /opt/cscopx/objects/mwfm Set environment variables as follows: For ksh: #../mwfm.kshrc For csh: # source mwfm.cshrc Step 2 Configure the Discovery Scope Before MWFM can start monitoring the devices, it must discover the devices in the network and retrieve all the information necessary to monitor the devices. The scope of the network is defined in two configuration files: DiscoSchema.cfg and DiscoPingFinderSchema.cfg. Open DiscoSchema.cfg using your favorite text editor. Search for the line insert into scope.zones. Edit the insert statement to match the following: insert into scope.zones m_protocol, m_action, m_zones ) 1, 1, [ { m_subnet=" ", m_netmask=24 }, { m_subnet=" ", m_netmask=24 }, { m_subnet=" ", m_netmask=24 }, { m_subnet=" ", m_netmask=24 } ); ] Save the DiscoSchema.cfg file. 11

12 Note You can use the example statements from the configuration file to build the above configuration. To activate the statements in the configuration file, uncomment the configuration by deleting the leading hyphens --). Open DiscoPingFinderSchema.cfg using your text editor. Search for the line insert into pingfinder.pingrules. Edit the insert statement to match the following: insert into pingfinder.pingrules m_address, m_requesttype, m_netmask ) " ", 2, " " ); insert into pingfinder.pingrules m_address, m_requesttype, m_netmask ) " ", 2, " " ); insert into pingfinder.pingrules m_address, m_requesttype, m_netmask ) " ", 2, " " ); insert into pingfinder.pingrules m_address, m_requesttype, m_netmask ) " ", 2, " " ); Note Step 3 The network scope defined in DiscoSchema.cfg should be the same as the DiscoPingFinderSchema.cfg. Specify the Read Only SNMP community strings. In order to fully enable MWFM to perform complete discovery, you must provide it with the community strings that will be used to access the various devices on the network and, hence, give it the ability to retrieve requested MIB variables from the device. This information is supplied to the MWFM using the RivSnmpStackSchema.cfg configuration file. Note If all the devices in your network have RO community string set to public you may skip this step. Open RivSnmpStackSchema.cfg in a text editor. Search for the line insert into snmpstack.versecuritytable. Edit the insert statement to match the following: insert into snmpstack.versecuritytable m_snmpversion, m_password, m_snmpver3level, m_snmpver3details, m_securityname ) 0, 'public', 2, { m_authpswd="authpassword", m_privpswd="privpassword" }, 'authpriv' ); 12

13 Step 4 Specify the Catalyst switch related info IP address & Password). Open DiscoTelnetHelperSchema.cfg in a text editor. Search for the line insert into telnethelper.deviceconfig. Edit the insert statement to match the following: insert into telnethelper.deviceconfig m_iporsubnet, m_netmaskbits, m_pagelengthcmd, m_pagelength, m_continuemsg, m_continuecmd ) ' ', 32, 'set length', 100, '.*wish to continue.*', 'y^m' ); Note Add the above insert statement for every Catalyst Switch in your network. You must configure the access parameters in order to enable MWFM to gain access to Catalyst Switches on your network. Configuring the access and password in RivTelnetPasswordSchema.cfg accomplishes this. Open RivTelnetPasswordSchema.cfg using your text editor. Search for the line insert into telnetstack.passwords. Edit the insert statement to match the following: Note In the following example, change the Login/Password/Console Prompt based on the configuration of your Catalyst switch. insert into telnetstack.passwords m_iporsubnet, m_netmaskbits, m_password, m_username, m_pwdprompt, m_logprompt, m_conprompt ) ' ', 32, 'secret', 'jdoe', '.*assword:.*', '.*ogin.*', '.*atalyst*' ); 13

14 Step 5 Specify DNS Server IP Address. Skip this step if you are not using a DNS Server for host lookup.) You can configure MWFM to perform DNS lookup for the devices in the network. Open DiscoDNSHelperSchema.cfg using your text editor. Search for the line insert into DNSHelper.methods. Edit the insert statement to match the following: insert into DNSHelper.methods m_methodname, m_methodtype, m_nameserveraddr, m_timeout ) 'DirectDNS', 1, ' ', 1 ); Step 6 Specify the location of the Syslog file. Open MonitorSyslogAgentSchema.cfg using your text editor. Search for the line insert into agentinfo.syslog. Edit the insert statement to match the following: insert into agentinfo.syslog FileNames, RereadFile, FieldNames, RegExps, WhiteSpace, Mappings ) [ "/var/adm/messages","/var/log/syslog_info" ], "false", [ "Date", "CiscoTime", "NodeName", "ExtraInfo", "SysCount", "Sysinfo", "Facility",. Snipped for clarity ); Step 7 Step 8 Specify SNMP Manager IP Address. Open DistSchema.cfg using your text editor. Search for the line RemoteManager. Set the IP address of the SNMP manager as follows: RemoteManager=" ", Configure TrapmuxSchema.cfg file to forward the raw alarms to the SNMP Manager. # vi TrapmuxSchema.cfg -=- insert into trapmux.sinkhosts xxx.xxx.xxx.xxx,162); -=- Where xxx.xxx.xxx.xxx is the IP address of the SNMP Manager Note This step is optional. The user should perform the above step only if he wants MWFM to forward all the raw alarms that are being sent by the network entitles to MWFM. MWFM2.0.1 configuration is complete. 14

15 Starting MWFM To start MWFM enter the following commands: #cd $RIV_HOME #./start_mwfm In the following example WIRELESS is the MWFM DOMAIN. #./start_mwfm WIRELESS The following procedure can be used to change the MWFM Domain: #cd$riv_home #./change_mwfm_domain<new_domain_name> Status of Discovery Issue the following sets of commands to determine the discovery state: #riv_oql -service RivDisco -domain WIRELESS -username root -latency password:<enter the password> The default MWFM superuser password is ciscomwfm. >select * from disco.status; >send; Sample output: m_discoverymode = 0 m_phase = 1 m_blackoutstate = 0 m_cyclecount = 0 m_discoverymode=1 indicates that the discovery has completed. List of devices discovered To get the list of devices discovered by MWFM issue the following commands: #riv_oql -service RivEvents -domain WIRELESS -username root -latency password: >select * from topocache.entitybyname; >send; List of active alarms To get list of MWFM2.0 active alarms issue the following commands: #riv_oql -service RivEvents -domain WIRELESS -username root -latency password: >select * from mojo.events where riveventtype=2; >send; 15

16 Obtaining Documentation Installing the Java Development Kit If you plan to develop Java client applications using the MWFM Java API package, you must install the Java Development Kit. MWFM Java SDK is available for download from Cisco Connection Online. Please point your web browser at: Obtaining Documentation The following sections provide sources for obtaining documentation from Cisco Systems. World Wide Web You can access the most current Cisco documentation on the World Wide Web at the following sites: 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: Registered Cisco.com users can order the Documentation CD-ROM through the online Subscription Store: Nonregistered Cisco.com users can order documentation through a local account representative by calling Cisco corporate headquarters California, USA) at or, in North America, by calling NETS6387). 16

17 Obtaining Technical Assistance Documentation Feedback If you are reading Cisco product 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 your comments to To submit your comments by mail, use the response card behind the front cover of your document, or write to the following address: Attn Document Resource Connection Cisco Systems, Inc. 170 West Tasman Drive San Jose, CA We appreciate your comments. Obtaining 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. For Cisco.com registered users, additional troubleshooting tools are available from the TAC website. 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: 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. 17

18 Obtaining Technical Assistance Contacting TAC by Using the Cisco TAC Website Contacting TAC by Telephone If you have a priority level 3 P3) or priority level 4 P4) problem, contact TAC by going to the TAC website: 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: If you cannot resolve your technical issue by using the TAC online resources, Cisco.com registered users can open a case online by using the TAC Case Open tool at the following website: 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: 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. AccessPath, AtmDirector, Browse with Me, CCIP, CCSI, CD-PAC, CiscoLink, the Cisco Powered Network logo, Cisco Systems Networking Academy, the Cisco Systems Networking Academy logo, Cisco Unity, Fast Step, Follow Me Browsing, FormShare, FrameShare, IGX, Internet Quotient, IP/VC, iq Breakthrough, iq Expertise, iq FastTrack, the iq Logo, iq Net Readiness Scorecard, MGX, the Networkers logo, ScriptBuilder, ScriptShare, SMARTnet, TransPath, Voice LAN, Wavelength Router, and WebViewer are trademarks of Cisco Systems, Inc.; Changing the Way We Work, Live, Play, and Learn, and Discover All That s Possible 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, FastHub, FastSwitch, GigaStack, IOS, IP/TV, LightStream, MICA, Network Registrar, Packet, PIX, Post-Routing, Pre-Routing, RateMUX, Registrar, SlideCast, StrataView Plus, Stratm, SwitchProbe, TeleRouter, and VCO are registered trademarks of Cisco Systems, Inc. and/or its affiliates in the U.S. and certain other countries. All other trademarks mentioned in this document or Web site 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. 0110R) Copyright 2001 Cisco Systems, Inc. All rights reserved. 18