Guest

Cisco MDS 9000 NX-OS and SAN-OS Software

Cisco MDS 9000 Family Release Notes for Cisco MDS SAN-OS Release 1.0(3a)

 Feedback

Table Of Contents

Cisco MDS 9000 Family Release Notes
for Cisco MDS SAN-OS Release 1.0(3a)

Contents

Introduction

System Requirements

Hardware Supported

Determining the Software Version

Feature Set

New Features in Release 1.0(3a)

Upgrading from Prior Releases to Release 1.0(3a)

Replaced Commands

New Command

Fabric Manager

Limitations and Restrictions

Static Domains and Persistency

The install all Command

VSANs in a Switch

Console Severity Level

Initial Setup

Caveats

Resolved Caveats

Open Caveats

Related Documentation

Obtaining Documentation

Cisco.com

Documentation CD-ROM

Ordering Documentation

Documentation Feedback

Obtaining Technical Assistance

Technical Assistance Center

Cisco TAC Web Site

Cisco TAC Escalation Center


Cisco MDS 9000 Family Release Notes
for Cisco MDS SAN-OS Release 1.0(3a)


CCO Date: February 5, 2005

Text Part Number: OL-3899-01 A0

This document describes the caveats and limitations for switches in the Cisco MDS 9000 Family. Use this document in conjunction with documents listed in the "Related Documentation" section.


Note Release notes are sometimes updated with new information on restrictions and caveats. Refer to the following website for the most recent version of the Cisco MDS 9000 Family Release Notes: http://www.cisco.com/en/US/products/hw/ps4159/ps4358/prod_release_notes_list.html


Table 1 shows the on-line change history for this document.

Table 1 On-Line History Change

Revision
Date
Description

A0

06/23/2005

Added DDTS CSCei25319


Contents

This document includes the following section:

Introduction

System Requirements

Limitations and Restrictions

Caveats

Related Documentation

Obtaining Documentation

Obtaining Technical Assistance

Introduction

The Cisco MDS 9000 Family of multilayer directors and fabric switches offer intelligent fabric-switching services that realize maximum performance while ensuring high reliability levels. They combine robust and flexible hardware architecture with multiple layers of network and storage management intelligence. This powerful combination enables highly available, scalable storage networks that provide advanced security and unified management features.

The Cisco MDS 9000 Family provides intelligent networking features such as multiprotocol and multitransport integration, virtual SANs (VSANs), advanced security, sophisticated debug analysis tools, and unified SAN management.

System Requirements

This section describes the system requirements for Cisco MDS SAN-OS Release 1.0(3a) and includes the following topics:

Hardware Supported

Determining the Software Version

Feature Set

Hardware Supported

Table 2 lists the hardware components supported on the Cisco MDS 9000 Family and the minimum software version required. See the "Determining the Software Version" section.

Table 2 Cisco MDS 9000 Family Supported Hardware Modules and Minimum Software Requirements

Component
Part Number
Description
Applicable Products

Software

M9500-SF1EK9-1.0.3

MDS 9500 supervisor/fabric-I, enterprise software

MDS 9509 only

M9200-EK9-1.0.3

MDS9216 enterprise software

MDS 9216 only

Chassis

DS-C9509

MDS 9509 director, base configuration (9-slot chassis, dual 2500W AC power supplies, and dual supervisors — SFPs sold separately)

MDS 9509 only

DS-C9216-K9

MDS 9216 16-port modular fabric switch (includes sixteen 1 / 2-Gbps Fibre Channel ports, power supply, and expansion slot — SFPs sold separately)

MDS 9216 only

Supervisor modules

DS-X9530-SF1-K9

MDS 9500 supervisor/fabric-I, module

MDS 9509 only

Switching modules

DS-X9016

MDS 9000 16-port 1/2-Gbps Fibre Channel module (SFPs sold separately)

MDS 9509 and 9216

DS-X9032

MDS 9000 32-port 1/2-Gbps Fibre Channel module (SFPs sold separately)

LC-type fiber-optic SFP1

DS-SFP-FC-2G-SW

1/2-Gbps Fibre Channel — short wave SFP

MDS 9509 and 9216

DS-SFP-FC-2G-LW

1/2-Gbps Fibre Channel — long wave SFP

Power supplies

DS-CAC-845W

AC Power supply for MDS 9216

MDS 9216 only

DS-CAC-2500W

2500W AC power supply

MDS 9509 only

DS-CAC-4000W-US

4000W2 AC power supply for US (cable attached)

DS-CAC-4000W-INT

4000W AC power supply international (cable attached)

DS-CDC-2500W

2500W DC power supply

CompactFlash

MEM-MDS-FLD512M

MDS 9500 supervisor CompactFlash disk, 512MB

MDS 9509 only

1 SFP = small form factor pluggable

2 W = Watt


Determining the Software Version


Note We strongly recommend that you use the latest available software release for all Cisco MDS 9000 Family products.


To determine the version of the Cisco SAN-OS software currently running on a Cisco MDS 9000 Family switch, log in to the switch and enter the show version EXEC command.

Feature Set

This Cisco MDS SAN-OS Release 1.0(3a) software is packaged in feature sets (also called software images) depending on the platform. The Cisco MDS SAN-OS software feature sets available for the Cisco MDS 9000 Family include Ethernet, Fibre Channel (1 Gbps and 2 Gbps), SNMP, and IP packets.

New Features in Release 1.0(3a)

SAN-OS Release 1.0(3a) is a maintenance release for switches in the Cisco MDS 9000 Family. See the "Caveats" section for details on closed and outstanding caveats and limitations.

Upgrading from Prior Releases to Release 1.0(3a)

To perform a quick, one-step upgrade on a Cisco MDS 9000 Family switch, follow these steps:


Step 1 Copy the kickstart and system image files to the required location (see Chapter 3, "Initial Configuration" in the Cisco MDS 9000 Family Configuration Guide).

Step 2 Set the boot variables (see Chapter 5, "Software Images" in the Cisco MDS 9000 Family Configuration Guide).

Step 3 Issue the reload command. The reload command reboots the system. This upgrade is disruptive.


Replaced Commands

The install module slot# bios command replaces the following commands:

bios verify

bios program

bios validate

The install module slot# of the supervisor module loader command replaces the init bootloader command

New Command

The install all command upgrades all modules in any Cisco MDS 9000 Family switch. The install all command is only effective on switches running Cisco MDS SAN-OS Release 1.0(3a) and above.

See the Cisco MDS 9000 Family Configuration Guide.

Fabric Manager

You can monitor domain area ports and configure persistent FCIDs from the Fabric Manager and the Device Manager.

See the Cisco MDS 9000 Fabric Manager User Guide for further information.

Before you can create persistent FCIDs, you must:

Configure a static domain ID in that VSAN

Ascertain that the static configured domain and the runtime domain are the same. You can verify this using the show fcdomain command. For information about using the command line interface (CLI). See the Cisco 9000 Family Configuration Guide.

Limitations and Restrictions

The following limitations and restrictions apply to all switches in the Cisco MDS 9000 Family.

Static Domains and Persistency

When configuring FC domains, follow these guidelines:

The fcdomain restart command applies your changes to the runtime settings. You can apply most of the configurations to their corresponding runtime values by using the restart disruptive option.

You must issue the fcdomain restart command if you want to apply the configured domain changes to the runtime domain.

The configured domain ID can be preferred or static. By default, the configured domain is 0 and the configured option is preferred. If you do not configure a domain ID, the local switch sends a random ID in its request.

A static domain is specifically configured by the user and may be different from the runtime domain. If the domain IDs are different, the runtime domain ID will change to take on the static domain ID after the next restart.

By default, the persistent FC ID feature is disabled. The assigned FC IDs in a fcdomain can be activated to remain persistent even after a reboot. This ensures that an attached N Port receives the same FC ID after a switch reboot.

If you connect to the switch from an AIX or HP-UX host, be sure to enable the persistent FC ID feature in the VSAN that connects these hosts.

When enabling persistent domain IDs, once the VSAN is restarted, if the requested domain ID is not granted by the principal switch, all local interfaces in VSAN 55 are moved to an isolated state.

See the Cisco MDS 9000 Family Configuration Guide.

The install all Command

The install all command is only effective on switches running Cisco MDS SAN-OS Release 1.0(3a) and above.

See the Cisco MDS 9000 Family Configuration Guide.

VSANs in a Switch

Up to 256 VSANs can be configured in a switch. Of these, one is a default VSAN (VSAN 1), and another is an isolated VSAN (VSAN 4094). User-specified VSAN IDs range from 2 to 4093.

Console Severity Level

When logging is enabled for a console session (default), you can configure the severity levels of messages that appear on the console. The default severity for console logging is 2 (critical).

The current critical (default) logging level is maintained, if the console baud speed is 9600 baud (default). All attempts to change the console logging level generates an error message. T o increase the logging level (above critical), you must change the console baud speed to 38400 baud.

See the Cisco MDS 9000 Family Configuration Guide.

Initial Setup

The first time that you access a switch in the Cisco MDS 9000 Family, it runs a setup program that prompts you for the IP address and other configuration information necessary for the switch to communicate over the supervisor module Ethernet interface. Additionally, you can access the switch setup using the setup command in EXEC mode.

When accessing the switch setup you have the following additional capabilities:

Type Ctrl-c at any prompt to skip the remaining configuration options and proceed with what is configured until that point.

If you do not wish to answer a previously-configured question, or if you wish to skip answers to any questions press Enter. If a default answer is not available (for example switch name), the switch uses what is previously configured and skips to the next question.

Caveats

This section lists the caveats and corrected caveats for this release. Use Table 3 to determine the status of a particular caveat. In the table, "R" indicates a resolved caveat, and "O" indicates an open caveat.

Table 3 Release Caveats and Caveats Corrected Reference

DDTS Number
Software Release (Resolved or Open)
1.0(2a)
1.0(3a)

Severity 2

CSCdz49739

R

R

CSCea11544

R

R

CSCdz47813

R

R

CSCdz40286

O

R

CSCdz41824

O

R

CSCdz62706

O

R

CSCdz49589

O

R

CSCdz31332

O

O

CSCei25319

O

O

Severity 3

CSCdz40837

R

R

CSCdz39137

R

R

CSCdz38419

R

R

CSCdz25873

R

R

CSCdz42206

R

R

CSCdz39924

R

R

CSCdz40770

R

R

CSCdz34906

R

R

CSCdz16649

R

R

CSCdz80310

R

R

CSCdz30806

O

R

CSCdz36297

O

R

CSCdz41227

O

R

CSCdz73481

O

R

CSCdz73186

O

R

CSCdz62711

O

R

CSCdz81955

O

R

CSCdz76025

O

R

CSCdz38248

O

R

CSCdy77777

O

R

CSCdz40221

O

R

CSCdz29899

O

R

CSCdz80007

O

R

CSCdy71186

O

O

CSCdz41155

O

O

CSCdz42325

O

O

CSCdz12179

O

O

CSCea04957

R

CSCea43130

R

CSCdz67484

O

CSCea40555

O

CSCdz43707

O

CSCdz43106

O

CSCea47778

O


Resolved Caveats

CSCdz40286

Symptom: When VSAN interfaces (VNI) are present in a system, you may receive some extra RSCNs when a system switchover is performed.

Please use the following URL for further information: http://www.cisco.com/pcgi-bin/bugtool/onebug.pl?bugid=CSCdz40286

CSCdz41824

Symptom: If the timeout values and/or the retry count of the RADIUS server is too large, you may not be able to login into the system if the RADIUS servers are down.

Please use the following URL for further information: http://www.cisco.com/pcgi-bin/bugtool/onebug.pl?bugid=CSCdz41824

CSCdz62706

Symptom: When a zoning configuration change is made while a switch is powering-up, some entries may be rejected and a lock busy error message is generated.

Please use the following URL for further information: http://www.cisco.com/pcgi-bin/bugtool/onebug.pl?bugid=CSCdz62706

CSCdz49589

Symptom: In the Cisco Fabric Manager, when you right click on a standby supervisor module and select Reset, the standby supervisor module powers-down instead of power-cycling.

Please use the following URL for further information: http://www.cisco.com/pcgi-bin/bugtool/onebug.pl?bugid=CSCdz49589

CSCdz30806

Symptom: When you copy a file from active bootflash: to standby bootflash: and if the space available on standby bootflash: is insufficient to store the copied file, the copy command may report a success even though the file has not been copied to standby bootflash:.

Please use the following URL for further information: http://www.cisco.com/pcgi-bin/bugtool/onebug.pl?bugid=CSCdz30806

Workaround: None.

CSCdz36297

Symptom: If the standby supervisor bootflash does not have sufficient space for a new image, auto synchronization fails. This failure leaves a partial image file on the standby bootflash.

Please use the following URL for further information: http://www.cisco.com/pcgi-bin/bugtool/onebug.pl?bugid=CSCdz36297

CSCdz41227

Symptom: When you enter the IP address for the FC analyzer, save the configuration, and reboot the switch you will loose the remote capture configuration.

Please use the following URL for further information: http://www.cisco.com/pcgi-bin/bugtool/onebug.pl?bugid=CSCdz41227

CSCdz73481

Symptom: Cisco MDS 9000 Family switches support multi-pid RSCN from 1.0(2a). In some cases, it may send out more than one SW-RSCN, when the option is turned on for the same event (port_online).

Please use the following URL for further information: http://www.cisco.com/pcgi-bin/bugtool/onebug.pl?bugid=CSCdz73481

CSCdz73186

Symptom: When interoperating using a Cisco MDS 9000 Family switch and a Brocade 3900 switch, the zonesets on the MDS switch and Brocade 3900 switch may be out-of-sync due to a non-standard timeout used by the 3900 device.

Please use the following URL for further information: http://www.cisco.com/pcgi-bin/bugtool/onebug.pl?bugid=CSCdz73186

CSCdz62711

Symptom: The boot variable image does not check platform compatibility. This is an enhancement request. When enhanced, the image specified in the boot command will be checked against the platform to verify that an MDS 9500 image runs on the MDS 9500 switch and an MDS 9200 image runs on the MDS 9200 switch.

Please use the following URL for further information: http://www.cisco.com/pcgi-bin/bugtool/onebug.pl?bugid=CSCdz62711

CSCdz81955

Symptom: CLI command output attachment in XML Call Home messages are not XML encoded. In most cases it does not cause problems, as the special characters (which should be used with appropriate encoding, for example: > or <) do not appear in CLI command output. In some cases where stack traces are attached (as a result of a process crash), the CLI command output may contain these characters. These characters break the XML parsing in the back end.

Please use the following URL for further information: http://www.cisco.com/pcgi-bin/bugtool/onebug.pl?bugid=CSCdz81955

CSCdz76025

Symptom: SW-RSCN frames sent by the switch may contain non-zero values in the reserved field. While this field is ignored by the receiving Cisco MDS 9000 Family switches, other vendor switches may respond otherwise.

Please use the following URL for further information: http://www.cisco.com/pcgi-bin/bugtool/onebug.pl?bugid=CSCdz76025

CSCdz38248

Symptom: SyslogServerAddressType setting is not preserved across switch resets, when configured using the Cisco Device Manager.

Please use the following URL for further information: http://www.cisco.com/pcgi-bin/bugtool/onebug.pl?bugid=CSCdz38248

CSCdy77777

Symptom: When a fcsDiscoveryCompleteNotify trap is received through the nlmLog table, the fcsVsanDiscoverName is missing.

Please use the following URL for further information: http://www.cisco.com/pcgi-bin/bugtool/onebug.pl?bugid=CSCdy77777

CSCdz40221

Symptom: Using the Device Manager or the Fabric manager, administrators can download an image to slot0 even though there is no flash in slot0.

Please use the following URL for further information: http://www.cisco.com/pcgi-bin/bugtool/onebug.pl?bugid=CSCdz40221

CSCdz29899

Symptom: FLOGI ACC(s) sent out on FL ports are not spanned.

If an FL port is configured as a SPAN source, the FLOGI accepts that leave this FL port are not spanned to the SPAN destination.

Please use the following URL for further information: http://www.cisco.com/pcgi-bin/bugtool/onebug.pl?bugid=CSCdz29899

CSCdz80007

Symptom: After rebooting and performing a switchover on a dual supervisor switch, it is possible that a VSAN may display an up operational state even if that VSAN may not contain any ports or if none of the ports in that VSAN are up.

This can cause the Fabric Manager to continuously try fabric discovery on this VSAN and to ultimately timeout with an error.

Please use the following URL for further information: http://www.cisco.com/pcgi-bin/bugtool/onebug.pl?bugid=CSCdz80007

CSCea04957

Symptom: When you issue a show running-config, the following message may be displayed: snmp-server host 10.144.132.174 traps version 2c public udp-port 2162 snmp-server host 10.144.132.174 traps version 2c public udp-port 2162 snmp-server host 10.144.132.174 traps version 2c public udp-port 2162 snmp-server host 10.144.132.174 traps version 2c public udp-port 2162

Enter Ctrl-C to exit this message.

Please use the following URL for further information: http://www.cisco.com/pcgi-bin/bugtool/onebug.pl?bugid=CSCea04957

CSCea43130

Symptom: An excessively busy boot flash on a standby supervisor could trigger the active supervisor to shut the standby supervisor down. This is because the standby supervisor cannot respond in time to the periodic health monitoring messages sent by active supervisor.

Please use the following URL for further information: http://www.cisco.com/pcgi-bin/bugtool/onebug.pl?bugid=CSCea43130

Open Caveats

CSCdz31332

Symptom: If automatic image synchronization is enabled, and the standby supervisor module is synchronizing the image from the active supervisor, the switch won't stop the user from issuing the reload command on the active or standby supervisor modules. This may result in a failure to synchronize the images.

Workaround: Be sure to allow sufficient time for the images to be synchronized before reloading a supervisor module.

CSCei25319

Sympton: An error message in the log file occurs because the platform manager component passes the wrong parameter while responding to a SNMP query. In some cases, this results in the query not being responded to.

Workaround: Perform a refresh on Device Manager to clear the problem.

CSCdy71186

Symptom: When you bring down a range of FL ports, there is a delay of four (4) seconds. This problem does not affect switch operation.

Workaround: None.

CSCdz41155

Symptom: The show logging level command does not display the configured levels for some MDS services like system manager, RDL, and FLOGI.

Workaround: None.

CSCdz42325

Symptom: When the switch boots for the first time and you configure the initial setup dialogue, or if you issue the write erase command and then reboot the switch, the setup process creates the configuration based on the input that you provide for the configuration. If a command execution goes wrong at this stage, it displays the following error:

Error: There was an error executing at least one command
Please verify the running configuration of the switch.

In some cases, this error is not reported. For example, if an IP address is configured on the network, the error may not be reported.

Workaround: Verify that the applied config is accurate by issuing a show running-config command.

CSCdz12179

Symptom: When the Fabric Manager or Device Manager is run through VPN or any NAT scheme, a generic error occurs while adding duplicate zone members from a VPN connection.

Workaround: None. If an error occurs while running through VPN/NAT, all errors will show up as generic errors without a detailed message describing the error.

CSCdz67484

Symptom: The Ethereal decoder incorrectly decodes the A bit in the Common Service Parameters set as Normal, instead of Alternate BB_Credit Management.

Workaround: None. The trace must be interpreted correctly.

CSCea40555

Symptom: During an install procedure, entering Ctrl-c returns a message saying that the install procedure cannot be interrupted, while Ctrl-z returns the prompt without any message. In either case, the install procedure continues.

Workaround: None.

CSCdz43707

Symptom: The Fabric Manager or Device Manager reports an error for all operations if the switch is multihomed (both IPFC based in-band management and the out-of-band management interface are up) and the Fabric or Device Manager was started using the IP-FC address. Typically, you will see a notInTime window error in the Device Manager and all sets fail.

Workaround: If the switch is multihomed, then start the Fabric or Device Manager on the switch using the out-of-band address.

CSCdz43106

Symptom: The counter values freeze if the Device Manager port monitor window has been up and running for a long time (overnight or a few days).

Workaround: Close the frozen Device Manager window and open a new session.

CSCea47778

Symptom: If the switch time zone is not UTC (default), the expire option for the username command returns an error. If the expire option is not specified, the username command does not have this issue.

switch# show clock 
Mon Mar 17 18:20:28 JST 2003 
switch(config)# username user1 password cisco expire 
expiry date wrong

Workaround: While creating a user-account, temporarily change the time zone to UTC.

Related Documentation

Regulatory Compliance and Safety Information for the Cisco MDS 9000 Family

Quick Start Guide for the Cisco MDS 9000 Family

Cisco MDS 9200 Series Hardware Installation Guide

Cisco MDS 9500 Series Hardware Installation Guide

Cisco MDS 9000 Family Command Reference

Cisco MDS 9000 Family Fabric Manager User Guide

Cisco MDS 9000 Family Troubleshooting Guide

Cisco MDS 9000 Family System Messages Guide

Cisco MDS 9000 Family MIB Reference Guide

Obtaining Documentation

The following sections explain how to obtain documentation from Cisco Systems.

Cisco.com

Cisco.com is the foundation of a suite of interactive, network 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

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:

Registered Cisco.com users (Cisco direct customers) can order Cisco product documentation from the Networking Products MarketPlace:

http://www.cisco.com/en/US/partner/ordering

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, elsewhere in North America, by calling 800 553-NETS (6387).

Documentation Feedback

If you are reading Cisco product documentation on Cisco.com, you can submit technical comments electronically. Click the Fax or E-mail option under the "Leave Feedback" at the bottom of the Cisco Documentation home page.

You can e-mail your comments to mdsfeedback-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.

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://tools.cisco.com/RPF/register/register.do

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 case is automatically opened.

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.