Guest

Cisco ONS 15200 Series DWDM Systems

Release Notes for ONS 15216 EDFA2 Release 2.1.0

 Feedback

Table Of Contents

Release Notes for ONS 15216 EDFA2 Release 2.1.0

What's New in Release 2.1.0

Closed Caveats—ONS 15216 EDFA2 Release 2.1.0

Open Caveats—ONS 15216 EDFA2 Release 2.1.0

Special Instructions

ONS 15216 EDFA2 Software Upgrade

ONS 15216 EDFA2 Firmware Upgrade

ONS 15216 EDFA2 Software Uninstall

Obtaining Documentation

World Wide Web

Documentation Feedback

Obtaining Technical Assistance

Cisco.com

Technical Assistance Center


Release Notes for ONS 15216 EDFA2 Release 2.1.0


This release note supports the 2.1.0 product release of the Cisco ONS 15216 EDFA2. The contents include open bugs tracked in Cisco DDTS and caveats that note documentation explanations, changes, additions, and/or errors.

What's New in Release 2.1.0

The 2.1.0 product release of the Cisco ONS 15216 EDFA2 differs from the 2.0.1 product release mainly in the inclusion of Transaction Language 1 (TL1). The following changes were made to the ONS 15216 EDFA2:

New firmware, version 2.3.14, is required for the 2.1.0 software.

A new CERENT-15216-EDFA-MIB.mib file, dated 2002/Jul/11, goes with release 2.1.0.

There are now two shells for command line access: ASH and TL1.

The proprietary command line interface named the ASH shell is the same as the 2.0.1 standard shell, with a few exceptions to accommodate TL1.

The ASH shell command line begins with ash:hostname:productname>

The TL1 shell command line begins with sidtidname:productname>

The factory default shell is TL1.

The ASH shell type modify command changes the shell for serial connections and when no TCI/IP port is specified for LAN connections.

User access formats were changed to accommodate TL1 standards.

There are now three permissions access levels: read (R), read_write (RW), and read_write_admin (RWA).

Each access level has an associated timeout, which logs users out after a period of inactivity.

Passwords now require non-alphabetic special characters.

The ASH user commands were modified to accommodate the new access level format.

The default user was changed from user name "root" with password "root" to user name "CISCO15" with a blank password.

The SNMP cerent15216EdfaOverallStatusGroup table has two new variables:

cerent15216EdfaConstGainOverallGainMeasured

cerent15216EdfaVariableGainPreAttenuationMeasured

The following commands were moved to be available only in manufacturer mode:

snmp session community get/set

snmp session transmission get/set

snmp pdu monitor enable/disable

snmp agent configure/display/list/save

snmp trap monitor display/enable

The SNMP power bus alarm variables cerent15216EdfaPowerBusDCVoltageMin and cerent15216EdfaPowerBusDCVoltageMax now have three digits with an allowable range of 350 to 700 (-35 to -70 VDC).

The electrical specification for minimum and maximum supply voltage is -40 to -57 VDC.

Connections (Telnet, FTP, TFTP) now have a keep-alive function where a lost connection is polled after one minute, with nine retries every 75 seconds. If the connection is not recovered, the ONS 15216 EDFA2.

A number of miscellaneous minor bugs were fixed, as described in the "Closed Caveats" section of this document closes the connection.

Closed Caveats—ONS 15216 EDFA2 Release 2.1.0

CSCdw60723

Issue: User login does not automatically time out.

Description: User sessions do not time out after a period of inactivity.

Resolution: A timeout is settable using the ASH user inactivity modify command or the TL1 SET-ATTR-SECUDFLT command.

CSCdx35184

Issue: Power bus A and B alarms in the cerent15216EdfaAlarmEnableStatus cannot be disabled.

Resolution: The attribute can now be disabled.

CSCdx35196

Issue: SromRingMemberId attribute cannot be set.

Description: The attribute cerent15216EdfaSromRingMemberId should be read-write for the MIB. This attribute is not used and cannot be set.

Resolution: This attribute has been removed from the MIB. It was not required.

CSCdx36228

Issue: The user entry delete and user entry create commands are not accepted.

Description: The user entry delete and user entry create commands should be available to users with administrative privileges.

Resolution: The CISCO15 user and other users with the read_write_admin access level have been given a greater subset of permissions. These commands are now available.

CSCdx37206

Issue: OpStatus is not set to "pending" when OpReset is performed.

Description: MIB description for cerent15216EdfaOpReset errantly reports that there will be a short delay (about 2 seconds) before reset is performed during which OpStatus will be set to "pending."

Resolution: The comment has been changed in the MIB. The "pending" state has been removed.

CSCdx41609

Issue: Diagnostic threshold values are displayed.

Description: The ASH pdm cfg threshold display command should not display the diagnostic reading for "faulty diode threshold."

Resolution: The "faulty diode threshold" reading has been removed.

CSCdx41637

Issue: Gain alarm is triggered when the output power exceeds 17 dBm instead of 17.6 dBm.

Description: When the input power is set to the maximum value for the gain setting range, a gain alarm is triggered if the output power exceeds 17 dBm instead of 17.6 dBm.

Resolution: A tolerance of 0.6 dB has been added to the maximum output power for compliance to the specifications of the unit.

CSCdx41659

Issue: An error is generated when the loss of signal (input power) threshold is set to its minimum value.

Description: The cerent15216EdfaLOSThreshold cannot be set to -3100.

Resolution: The value of -3100 is now accepted.

Open Caveats—ONS 15216 EDFA2 Release 2.1.0

General

The following open caveats relate to the ONS 15216 EDFA2 in general.

CSCdx41604

Issue: Ethernet activity LED initialization.

Description: When powered up without an Ethernet cable, the activity light remains on.

CSCdy50894

Issue: No output power after adjusting gain setting.

Description: The VOA pre-attenuator is stuck at maximum attenuation if the gain setting is modified when the input power is below the minimum signal level.

Workaround: Use the following series of sample commands to recover from the VOA being stuck at high attenuation:

For ASH:

ash:hostname:ONS15216 EDFA2> snmp attribute set local cerent15216EdfaPumpCfgConstPumpPower 1 50 
ash:hostname:ONS15216 EDFA2> snmp attribute set local cerent15216EdfaPumpCfgControlMode 1 constPower 
ash:hostname:ONS15216 EDFA2> snmp attribute set local cerent15216EdfaVariableGainPreAttenuation 10
ash:hostname:ONS15216 EDFA2> snmp attribute set local cerent15216EdfaConstGainOverallGain 160

For TL1:

name:ONS15216 EDFA2> ED-DWDM:name:all:100:::PUMP1CTRLMODE=PWR,PUMP1CTRLVALUE=50;
name:ONS15216 EDFA2> ED-DWDM:name:all:101:::PREATT=10;
name:ONS15216 EDFA2> ED-DWDM:name:all:102:::PUMP1CTRLMODE=GAINTEMP;
name:ONS15216 EDFA2> ED-DWDM:name:all:103:::OVERALLGAIN=160;

SNMP

The following open caveats relate to SNMP.

CSCdw47424

Issue: ifInOctets always returns a zero.

Description: Instead of counting the number of octets coming in to its Ethernet interface, ifInOctets always returns a zero.

CSCdw47428

Issue: ipDefaultTTL always returns a zero.

Description: ipDefaultTTL is read-only and returns a zero instead of 64.

CSCdw50831

Issue: ifOutOctets always returns a zero.

Description: Instead of counting the number of octets transmitted out of the interface, the attribute ifOutOctets always returns a zero for the Ethernet interface.

CSCdw51339

Issue: snmpInTraps does not increase.

Description: When a trap is received, the counter SnmpInTraps does not increment.

CSCdx41575

Issue: OpFinished trap notification is sent before OpReset is completed.

Description: The cerent15216EdfaOpFinished notification trap, in the case of cerent15216EdfaOpReset, indicates that the operation is about to be performed. Instead, this notification should indicate that the operation has successfully completed.

CSCdy19014

Issue: Handling of GET-BULK requests.

Description: For GET-BULK requests with particular values of "Non-repeaters" and "Max repetitions" fields, the operation does not return exactly the expected outcome (zero variables). E.g., if non-repeaters = 0 and max-repetitions < 0, the GET-BULK returns all of them.

CSCdy20159

Issue: Incorrect error-status for some read-write variables.

Description: The implementation of the Ethernet and RS-232 interfaces for the EDFA2 does not allow the admin status ifAdminStatus, which indicates the desired status of an interface (up, down, or testing), to be changed.

CSCdy21361

Issue: snmpInASNParseErrs does not get incremented.

Description: The counter snmpInASNParseErrs, which indicates the total number of ASN.1 or BER errors encountered when decoding received SNMP Messages, does not increment if an invalid message is sent to the agent.

CSCdy21381

Issue: ipInReceives returns an inconsistent value.

Description: The counter ipInReceives, which indicates the total number of input packets received from interfaces, including those received in error, is not equal to the sum of the counters ipInAddrErrors, ipForwDatagrams, ipInUnknownProtos, ipInDiscards, and ipInDelivers.

CSCdy21386

Issue: ipFragCreates does not increment as expected.

Description: The counter ipFragCreates, which indicates the number of IP packet fragments generated when a packet fragmentation has happened, does not increment.

CSCdy22384

Issue: tcpOutRsts counter does not increment.

Description: When a connection is attempted to any port not represented in the tcpConnTable as available for connection, the expected outcome is for all the attempts to be denied, and for tcpOutRsts to increment. The connections are correctly denied but the counter tcpOutRsts, which keep track of the number of resets generated by a TCP, does not increment as it should.

CSCdy22389

Issue: snmpInTotalReqVars counter increments during GET.

Description: The counter snmpInTotalReqVars represents the total number of objects successfully retrieved as the result of receiving valid Get- and Get-Next requests. The agent does not increment this counter in the middle of a GET request. E.g., if is issued a GET containing two instances of snmpInTotalReqVars separated by an instance of sysDescr.0., the expected outcome is for both values in the response to be equal but actually they are different.

CSCdy26021

Issue: tcpPassiveOpens counter does not increment.

Description: The counter tcpPassiveOpens does not increment when a TCP connection is formed with the agent.

CSCdy26028

Issue: snmpOutTooBigs counter does not increment.

Description: The counter snmpOutTooBigs, which indicates the total number of SNMP messages generated by the SNMP protocol entity and for which the value of the error-status field is "tooBig," does not increment.

CSCdy34034

Issue: tcpActiveOpens does not increment.

Description: The counter tcpActiveOpens should increment if an outbound TCP connection is created. Instead it remains constant.

CSCdy34039

Issue: tcpAttemptFails does not increment.

Description: tcpAttempFails counts the failed TCP connection attempts (e.g., a Telnet or FTP to an unreachable IP address either through or from the device). The counter tcpAttemptFails does not increment after the attempt.

TL1

The following open caveats relate to TL1.

CSCdx62043 and CSCdy11908

Issue: Space, Tab, and Enter keys are not ignored within input messages.

Description: Spaces should be ignored, but TL1 commands can be rejected if extraneous spaces are included. Also, instead of being ignored, the Tab key accesses TL1 help and the Enter key terminates a command.

CSCdx78978 and CSCdy29420

Issue: Some commands complete in 3-4 seconds instead of maximum of 2 seconds.

Description: ED-DWDM, ED-USER-SECU, RTRV-DWDM, RTRV-TH-DWDM, and SET-TH-DWDM commands get completed slowly. Telcordia GR-831 specifies a 2-second rule, but these commands usually complete in 3 or 4 seconds.

CSCdy06088

Issue: Incorrect error message for input commands with wrong target identifier (TID).

Description: If an incorrect TID is used, the command is denied with a "Gateway forwarding failed" message. However, per GR-831, the command should be denied with an IITA "Invalid Target Identifier" error code and message instead. Note that the EDFA2 does not operate as a gateway network element (GNE).

CSCdy06097, CSCdy07176, and CSCdy09548

Issue: General Block should not be supported for certain commands.

Description: The General Block mostly has not been implemented in the EDFA2 commands. Therefore unless expressly specified in the command syntax, it should not be supported, e.g., for the following commands: ACT-USER, DLT-RFILE, ED-DWDM, ED-ENV, RTRV-ALM-ALL, RTRV-ALM-DWDM, RTRV-ALM-ENV, RTRV-AO, RTRV-COND-ALL, RTRV-COND-DWDM, RTRV-COND-ENV, RTRV-DWDM, RTRV-ENV, RTRV-HDR, RTRV-NE-GEN, RTRV-RFILE, RTRV-TH-ENV, SET-TH-ENV.

CSCdy06100

Issue: Subsequent logins with same user name get completed.

Description: Multiple logins with the same user name are accepted.

CSCdy06120 and CSCdy15422

Issue: Password format not conformant to TL1 requirements.

Description: According to Telcordia TR-835, a password can be up to 10 characters with at least 2 alphanumeric and 1 special character ( plus (+), pound (#), or percent-sign (%) ), and optionally any digits. For instance, #7SWS, 1A0, 10%, and abc are all valid passwords. The EDFA2 does not fully conform to these rules (e.g., it also accepts special characters such as ~, @, and $).

CSCdy07244

Issue: No check is performed on BootRecordType field with ED-NE-GEN.

Description: There is no validity check performed on the NAME and BOOTIPADDR1 fields when the ED-NE-GEN command is entered.

CSCdy10646

Issue: Incorrect behavior of RTRV-AO command.

Description: RTRV-AO returns AO log even if ATAGSEQ, MSGTYPE, and DBCHGSEQ are not specified.

CSCdy12948

Issue: Incorrect automatic message implemented for timeout of session.

Description: The correct message should be CANC, but the EDFA2 gives CANC-USER.

CSCdy12968

Issue: Incorrect error code for DLT-USER-SECU if user does not exist.

Description: If the DLT-USER-SECU command is executed for a non-existing user, then the EDFA2 should return a PICC (Privilege, Illegal Command Code) error code, as per Telcordia TR-835. Instead the EDFA2 returns an FCEX error code.

CSCdy12978

Issue: DLT-USER-SECU does not terminate the active session.

Description: The DLT-USER-SECU command does not terminate the active session of a user ID that is deleted.

CSCdy14134

Issue: REPT EVT DWDM for "LOS Threshold Changed" is not always dispatched.

Description: Further to a LOS Threshold Change done through ASH CLI, the TL1 does not return the related REPT EVT DWDM autonomous message unless the threshold changes very much (e.g., 150, which would be 150*100 dBm). Note that if the threshold change is done through TL1, it gets immediately notified with the REPT EVT DWDM message.

CSCdy15392

Issue: Users defined in ASH CLI do not comply with TL1 rules.

Description: User names, that are not valid TL1 user names, can be entered using the ASH CLI.

CSCdy38826

Issue: Incorrect correlation tag syntax is accepted.

Description: CTAG numbers with multiple decimal points or trailing alphabetical characters are accepted. These should be rejected per the CTAG syntax specified in Telcordia GR-831.

CSCdy48336

Issue: Minor case temperature alarm is listed as Major in RTRV-ALM-EQPT.

Description: When the case temperature alarm is raised, it is Minor, but when RTRV-ALM-EQPT is used to get the active alarm list, the case temperature alarm is listed as a Major alarm severity.

Special Instructions

This section provides the software and firmware upgrade procedures for upgrading an ONS 15216 EDFA2 Release 2.0.1 to Release 2.1.0. It also includes a software uninstall procedure to return to Release 2.0.1.

ONS 15216 EDFA2 Software Upgrade

The following procedure is used to upgrade the software image from Release 2.0.1 to Release 2.1.0. A firmware image upgrade is required after the software has been upgraded. This procedure is not service affecting, but it deletes all custom user names and passwords.


Step 1 If the ONS 15216 EDFA2 already has been assigned and IP address, subnet mask, gateway address, and host name, skip to Step 8.

Step 2 Log into the ONS 15216 EDFA2 using HyperTerminal as a user with administrative privileges.

Step 3 Enter the correct user name and password (default is root, root).

Step 4 Verify that the following login response is displayed:

Welcome to ONS15216 EDFA2 Console (v2.0.1)
hostname:ONS15216 EDFA2> 

Step 5 At the command prompt, enter the following command, entering the response information line by line:

hostname:ONS15216 EDFA2> snmp row set local cerent15216EdfaSromIpMgmtGroup

cerent15216EdfaSromIpMgmtEnetAddress 0.0.0.0
cerent15216EdfaSromIpMgmtEnetSubNetMask 0.0.0.0
cerent15216EdfaSromIpMgmtDefaultRouterAddress 0.0.0.0
cerent15216EdfaSromIpMgmtHostName ""

Step 6 To save the changes, enter the following command:

hostname:ONS15216 EDFA2> snmp attribute set local cerent15216EdfaOpSaveConfig perform

Step 7 If any changes have been made, the system must be rebooted to make the IP address active. Enter the following command:

hostname:ONS15216 EDFA2> processor reset


Step 8 Verify that the ONS 15216 EDFA2 is connected to the LAN via the module's LAN port.

If not, use a straight-through Cat5 Ethernet cable with RJ-45 connectors to connect from the LAN port to a LAN switch or hub.

Step 9 Put the Release 2.1.0 software image on a PC or server that has an FTP server and is on the same LAN as the ONS 15216 EDFA2.

Step 10 Log into the ONS 15216 EDFA2 as a user with administrative privileges.

Step 11 Enter the correct user name and password (default is root, root).

Step 12 Verify that the following login response is displayed:

Welcome to ONS15216 EDFA2 Console (v2.0.1)
hostname:ONS15216 EDFA2> 



Step 13 At the hostname prompt, enter the following command to log in to the FTP site.

hostname:ONS15216 EDFA2> network host ftp FTP_server_IP_address 

The ONS 15216 EDFA2 should respond as follows:

connecting to FTP_server_IP_address 
connected to FTP_server_IP_address 

Once the login process is completed, the ftp prompt should be available.

Step 14 At the ftp prompt, enter the command as shown below to complete the ftp logon.

ftp> login FTP_username

Step 15 When prompted, enter the FTP user password as shown.

Password: ***** 

The ONS 15216 EDFA2 should respond as follows:

230 User FTP_username logged in.

Step 16 At the ftp prompt, enter the following command:

ftp> cd /Directory_of_FTP_site

Step 17 At the ftp prompt, enter the following command:

ftp> type i 

The ONS 15216 EDFA2 should respond as follows:

type set to BINARY

Step 18 At the FTP prompt, enter the following command:

ftp> get 15216EdfaSw_2.1.0 

When the command is entered, the file transfer begins. When the file transfer is completed, the following information should be displayed:

Bytes received: xxxxx 
Transfer complete. 

Step 19 At the FTP prompt, enter the following command:

ftp> quit 

The FTP session is terminated and the following response should be displayed:

Ftp session terminated.

The ONS 15216 EDFA2 then returns to the hostname prompt.

Step 20 At the hostname prompt enter the following command:

hostname:ONS15216 EDFA2> srom cfg boot modify 

Step 21 After the response message, enter the following:

Boot Count = 4 
2

After the response message, enter the following:

Boot Record 0 type 2 Flash 
2

Step 22 After the response message, enter the following:

Filename = 15216EdfaSw_2.0.1 
15216EdfaSw_2.1.0

After the response message, enter the following:

Boot Record 1 type 2 Flash 
2

Step 23 After the response message, enter the following:

Filename = 15216EdfaSw_x.x.x 
15216EdfaSw_2.0.1

Step 24 At the hostname prompt, enter the following command:

hostname:ONS15216 EDFA2> processor reset 

Step 25 Log into the ASH shell as a user with administrative privileges.

The ONS 15216 EDFA2 now has TL1 as the default shell. Specify port 8023 in a Telnet session to specifically log into the ASH shell. In Microsoft Windows, click Start > Run, and enter the following:

telnet <ONS 15216 EDFA2 IP address> 8023

The ONS 15216 EDFA2 should respond as follows:

-- LOGIN ---------------------------------------------------- sysname
ONS15216 EDFA2 Optical Amplifier 
-------------------------------- 
Software Version 2.1.0 
Copyright (c) 2000-2001 Cisco Systems, Inc. 
Username: { } 
Password: { } 
[Login] 

Step 26 Enter the correct user name and password (default is root, root).

Step 27 Verify that the following login response is displayed:

Welcome to ONS15216 EDFA2 Console (v2.1.0) 
ash:hostname:ONS15216 EDFA2> 

Step 28 At the hostname prompt, enter the following command:

ash:hostname:ONS15216 EDFA2> manufacturer mode enable

Step 29 At the hostname prompt, enter the following command:

ash:hostname:ONS15216 EDFA2> manufacturer restore defaults srom -usr

This does not reset the other configuration parameters like IP address, optical module settings, etc.

Step 30 At the hostname prompt, enter the following command:

ash:hostname:ONS15216 EDFA2> manufacturer restore defaults srom -ka

Step 31 At the hostname prompt, enter the following command:

ash:hostname:ONS15216 EDFA2> manufacturer restore defaults quasar

Step 32 At the hostname prompt, enter the following command:

ash:hostname:ONS15216 EDFA2> manufacturer restore defaults passwords


Note The default user name CISCO15 with no password is now enabled. All custom user names and passwords get deleted in this step and need to be recreated with the new access level format and password requirements.


Step 33 At the hostname prompt, enter the following command:

ash:hostname:ONS15216 EDFA2> processor reset

The software upgrade procedure is complete. Proceed to the firmware upgrade procedure below.


ONS 15216 EDFA2 Firmware Upgrade

The following procedure is used to upgrade the firmware image from version 1.3.1 to version 2.3.14. The software upgrade to Release 2.1.0 is required before performing this procedure, but the software can be changed back to Release 2.0.1 if desired after the firmware is upgraded. This procedure is not service affecting.


Note This firmware upgrade ensures that in the event that administrative access to the ONS 15216 EDFA2 is lost and the recover default password procedure is performed, the CISCO15 default password can be recovered with CISCO15 retaining full administrative privileges.



Step 1 Put the 2.3.14 firmware image on a PC or server that has a TFTP server and is on the same LAN as the ONS 15216 EDFA2.

Step 2 Log into the ASH shell as a user with administrative privileges.

Step 3 Enter the correct user name and password (default is CISCO15 with no password).

Step 4 Verify that the following login response is displayed:

Welcome to ONS15216 EDFA2 Console (v2.1.0)
ash:hostname:ONS15216 EDFA2> 

Step 5 At the hostname prompt, enter the following command:

ash:hostname:ONS15216 EDFA2> flash boot erase

Step 6 At the hostname prompt, enter the following command:

ash:hostname:ONS15216 EDFA2> flash boot program tftp TFTP_server_IP_address 
Directory_of_TFTP_site/15216EdfaFw_2.3.14

After the series of dots on the screen, the hostname prompt returns.

Step 7 At the hostname prompt, enter the following command:

ash:hostname:ONS15216 EDFA2> processor reset

The firmware upgrade procedure is complete.


ONS 15216 EDFA2 Software Uninstall

The following procedure is used to change the software image from Release 2.1.0 back to Release 2.0.1. The firmware version in use does not affect this procedure; either firmware version 1.3.1 or version 2.3.14 is acceptable. This procedure is not service affecting.


Step 1 Log into the ASH shell as a user with administrative privileges. ( If using a Telnet session, specify port 8023 to be sure to log into the ASH shell.)

Step 2 At the hostname prompt, enter the following command:

ash:hostname:ONS15216 EDFA2> srom cfg boot modify 

Step 3 After the response message, press Enter:

Boot Count = 2 


After the response message, enter the following:

Boot Record 0 type 2 Flash 
2 

Step 4 After the response message, enter the following:

Filename = 15216EdfaSw_2.1.0 
15216EdfaSw_2.0.1

After the response message, press Enter:

Boot Record 1 type 2 Flash 


Step 5 At the hostname prompt, enter the following command:

ash:hostname:ONS15216 EDFA2> processor reset

The software uninstall procedure is complete.


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:

http://www.cisco.com

Translated documentation is available at the following URL:

http://www.cisco.com/public/countries_languages.shtml

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-9883

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

Streamline business processes and improve productivity

Resolve technical issues with online support

Download and test software packages

Order Cisco learning materials and merchandise

Register for online skill assessment, training, and certification programs

You can self-register on Cisco.com to obtain customized information and service. To access Cisco.com, go to the following URL:

http://www.cisco.com

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:

Priority level 4 (P4)—You need information or assistance concerning Cisco product capabilities, product installation, or basic product configuration.

Priority level 3 (P3)—Your network performance is degraded. Network functionality is noticeably impaired, but most business operations continue.

Priority level 2 (P2)—Your production network is severely degraded, affecting significant aspects of business operations. No workaround is available.

Priority level 1 (P1)—Your production network is down, and a critical impact to business operations will occur if service is not restored quickly. No workaround is available.

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:

http://www.cisco.com/tac

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.