Cisco 10000 Series Routers

Cisco IOS Release 12.0(14)SL1

  • Viewing Options

  • PDF (220.5 KB)
  • Feedback
Release Notes for the Cisco 10000 ESR for Cisco IOS Release 12.0(14)SL1

Table Of Contents

Release Notes for the Cisco 10000 ESR for Cisco IOS Release 12.0(14)SL1


Upgrading to a New Software Release

System Requirements

Cisco 10000 ESR Software Features

Limitations and Restrictions

Automatic Protection Switching Support

Important Notes

Frame Relay and PPP Sessions

Cisco Discovery Protocol


Resolved in Cisco IOS Release 12.0(14)SL1

Obtaining Documentation

World Wide Web

Documentation CD-ROM

Ordering Documentation

Documentation Feedback

Obtaining Technical Assistance

Technical Assistance Center

Contacting TAC by Using the Cisco TAC Website

Contacting TAC by Telephone

Release Notes for the Cisco 10000 ESR for Cisco IOS Release 12.0(14)SL1

February 20, 2001

These release notes provide information about Cisco IOS Release 12.0(14)SL1, which runs on the Cisco 10000 Edge Services Router (ESR).

These release notes have been updated to include a fix for an SNMP problem (see CSCdt34097). Beyond the fix for CSCdt34097, these release notes are identical to the release notes for Cisco IOS Release 12.0(14)SL, which are included for your convenience.

Cisco IOS Release 12.0(14)SL1 is based on Cisco IOS Release 12.0(14)SL. For a list of the software caveats that apply to Cisco IOS Release 12.0(14)SL1, see the "Caveats" section and the release notes for Cisco IOS Release 12.0(S). To review the release notes for Cisco IOS Release 12.0S, go to and click Technical Documents > Cisco Product Documentation > Cisco IOS Software Configuration > Cisco IOS Release 12.0 > Release Notes > Cisco 12000 Series Router > Cisco 7000 Family and 12000 Series - Release Notes for Release 12.0(S).

Use these release notes in conjunction with the cross-platform Release Notes for Cisco IOS Release 12.0.


Upgrading to a New Software Release

System Requirements

Cisco 10000 ESR Software Features

Limitations and Restrictions

Important Notes


Resolved in Cisco IOS Release 12.0(14)SL1

Obtaining Documentation

Obtaining Technical Assistance

Upgrading to a New Software Release

For specific information about upgrading your Cisco 10000 ESR to a new software release, see the Cisco 10000 ESR Software Configuration Guide.

For general information about upgrading to a new software release, see the product bulletin Cisco IOS Upgrade Ordering Instructions located at:

For additional information about ordering Cisco IOS software, refer to the Cisco IOS Software Releases URL:

System Requirements

We recommend that you use 512 MB of memory on the Performance Routing Engine (PRE). New PREs are shipped with 512 MB of memory. In a redundant setup, both PREs should have the same amount of memory.

Cisco 10000 ESR Software Features

Table 1 lists the features supported in the Cisco 10000 ESR.

Table 1 Principal Software Features 


Cisco Discovery Protocol (CDP)

Simple Network Management Protocol (SNMP)


SONET 1+1 Automatic Protection Switching (APS)



High-Level Data Link Control (HDLC)

Frame Relay

Point-to-Point (PPP)

Multilink Point-to-Point (MLP)

Multiprotocol Label Switching

Multiprotocol Label Switching (MPLS) edge services

Multicast Features

Multicast Static Routes

Multicast Routing Monitor (MRM)

Multicast Services

Internet Group Management Protocol (IGMP)

Protocol-Independent Multicast (PIM)

Distance Vector Multicast Routing Protocol (DVMRP)

Cisco Group Management Protocol (CGMP)

Unidirectional Link Routing (UDLR)

Session Directory Protocol (SDP)

Multicast Source Discovery Protocol (MSDP)

Border Gateway Protocol (BGP)

Quality of Service

Committed Access Rate (CAR)

Weighted Random Early Detection (WRED)

QoS Policy Propagation on BGP (QPPB)

Marking packets by using IP header precedence and differentiated service code point (DSCP)

Routing Protocols

Border Gateway Protocol (BGP)

Intermediate System-to-Intermediate System (IS-IS)

Open Shortest Path First (OSPF)

Interior Gateway Routing Protocol (IGRP)

Enhanced Interior Gateway Routing Protocol (EIGRP)

Routing Information Protocol (RIP)

Security Features

Standard and extended access lists

Authentication, Authorization, and Accounting (AAA)

Kerberos authentication and client support on Telnet

Radius authentication

Terminal Access Controller Access Control System Plus (TACACS+)

Limitations and Restrictions

This section describes ant limitations and restrictions that you should review before you use the Cisco 10000 ESR.

Automatic Protection Switching Support

Automatic protection switching is supported on the OC-12 Packet Over SONET (POS) line card, with the following limitation.

For APS to work properly, you must always have an OC-12 POS line card installed in the lower-numbered (odd) slot.

The system receives clocking information from the line card in the odd slot. If you remove the odd-numbered card (or if the clocking mechanism on that card fails), the clocking is lost and the data path is shut down. (Caveat CSCdr81416)

To manage this APS behavior, we recommend the following:

1. For the card pair, fully configure the lower-numbered card, and leave the higher-numbered card set to its default configuration.

2. Before you remove a card from the odd slot, run the no associate command and shut down the card. The following is an example of disabling APS for cards in slots 5 and 6:

Router(config)# redundancy
Router(config-r)# no associate 5 6
Router(config-r-a-sl)# exit
Router(config)# interface pos 5/0/0
Router(config-if)# shutdown

You can now remove the card in slot 5.

3. Move the card located in the even slot to the odd slot and enter the no shutdown command. Traffic flow resumes. Insert a new card into the even slot and reconfigure the pair for redundancy.

Important Notes

This section contains issues that you should be aware of with Cisco IOS Release 12.0(14)SL.

Frame Relay and PPP Sessions

You can run up to 2000 Frame Relay sessions or 1300 PPP sessions, and you can configure up to 300 BGP peers on the Cisco 10000 ESR. The router also supports up to 512 Multilink Point-to-Point (MLP) protocol sessions.

Note Each T1 interface in an MLP bundle represents a single PPP session. Thus, if you configure 130 MLP bundles of 10 T1 interfaces, each results in 1300 PPP sessions (which is the maximum number of PPP sessions that are supported on the Cisco 10000 ESR).

Cisco Discovery Protocol

Starting with this release, the Cisco Discovery Protocol (CDP) is disabled by default. You can enable CDP on an interface using the cdp enable command.


This section describes the caveats for the Cisco 10000 ESR running under Cisco IOS software Release 12.0(14)SL.


If you configure a DS3 BERT pattern 2^20-O153 on any unchannelized DS3 (by using the bert pattern 2^20-O153 interval 1-14400 command), and you then connect the line card to T-Bird 310 test set, the pattern does not synchronize with T-Berd 310.

Workaround: Use a different BERT pattern.


If you preconfigure a line card using the card command, this significantly degrades PRE performance.

Workaround: Do not use the card command to preconfigure line cards. Instead, use the no card command to remove references to cards that are not in the chassis.


The router sends out DHCP INFORM and DISCOVER messages containing an incorrect Ethernet address.

Workaround: No workaround is necessary. This caveat is harmless because these DHCP messages are not used to acquire IP addresses. They are used to gather environmental data such as the domain name server address.


When you enter the hw-module slot_number reset command, the event sequence appears in a different order than that shown by the reload command if the logging console is configured to informational.

Workaround: There is currently no workaround. You only encounter this problem if you change the default logging (critical) to informational.


When you use the Frame Relay autosense feature, the Cisco 10000 ESR sends all three LMI status message types immediately after the interface starts responding. However, sometimes the switch at the other end is not ready to receive messages and as a result, misses one or two messages that were sent. LMI autosense waits until the next scheduled interval (default is 1 minute) to send the messages again.

This problem primarily affects clear channel CT3 interfaces.

Workaround: There is currently no workaround.


If you configure an STS-1 on a ChOC-12 line card as unchannelized and then configure the remote side to send idle-character marks (namely, 0xFF), the T3 line stops responding and transmits a Remote Alarm Indication (RAI).

Workaround: When you use unchannelized T3 mode, configure the remote side to send idle-character flags (0x7E). To set this value, use the interface configuration mode idle-character command.


When you send large numbers of packets from the Gigabit Ethernet line card to the PRE in the Cisco 10000 ESR, you may lose a small number of packets. This only occurs for some packet sizes at very high bandwidths, with loss rates of a few parts per million.

Workaround: There is currently no workaround.


During periods of heavy traffic (approaching interface line rate), some interfaces may experience inconsistent performance between interfaces of the same type.

Workaround: There is currently no workaround.

CSCdr52081 and CSCdj94209

The PRE may crash if you repeatedly change a port back and forth from channelized to unchannelized.

Repeated conversions of a T3 port from channelized mode to unchannelized mode and back, with intervening assignments of IP addresses to the interfaces and ping testing, may cause the PRE crash.

Workaround: Reload the chassis.


If large MLP configurations are in use, and you attempt to copy the configuration from a TFTP server directly into the running config, the copy may fail. Failures may include interfaces not appearing or IPCP or LCP states not opening correctly.

Workaround: These failures are far less likely to occur if the configuration is copied to bootflash, and then from bootflash to the running config. Copy the configuration file to the startup config and then reload the router.


Limited support for APS. For detailed information, refer to the "Automatic Protection Switching Support" section.


On rare occasions, the system may not be able to retrieve remote performance data if you are using a ChOC-12 line card that has its T1s configured with ANSI FDL enabled.

Workaround: There is currently no workaround.


When the encapsulation mode is changed from PPP to HDLC or vice-versa, the system drops about 3 of the next 10 packets transmitted. After that, the packets are transmitted normally.

Workaround: There is currently no workaround.


When a ChOC-12 line card is reconfigured from a channelized T3 configuration to an unchannelized T3 configuration or vice-versa, the initial packets are not forwarded.

Workaround: Save the configuration and then remove and reinsert the ChOC-12 line card. When the card restarts, it does not drop the initial packets.


Under normal (IMIX) traffic loads, the OC-12 ATM line card segmenter may not keep up with line rate. This is indicated by an increase in "output queue drops" or "output buffer failure" counts as displayed by the show interface command.

Workaround: There is currently no workaround.


Large multicast groups may cause CPU hog issues with PIM.

Workaround: There is currently no workaround.


The Flash disk can fall into the chassis when you insert the disk into the empty space to the right of the slot B in the PRE flash assembly.

Workaround: Pay extra attention when inserting a flash disk into the PRE flash assembly. Do not insert the disk in the empty space to the right of the slot B—if you insert a card in that space, it will fall into the chassis.


If you send a large number of small packets in large multicast groups, this may cause the following debug messages to appear on the console:

../src-4k-c10k/c10k_isr_ct3.c, line 548
 <idb invalid on vc 0x624FA974, slot 12 port 0 chan 104
 dh 05E0001F 680100FF>
 60044EB4 60016E48 60017238 601F2C9C 601D0404

../src-4k-c10k/c10k_isr_ct3.c, line 535
 <port 7 invalid>
 60044CEC 60016E48 60017238 601F2C9C 601D0404

Workaround: Decrease the number of small packets.


When older CT3 line cards are powered on with live DS3 signals present at the receive BNC connector, the receive line interface device on the board may lock up, preventing the controller from running. You can verify this symptom by using the show controller t3 command, which shows that the controller is down, the Receiver has Loss of Frame, and the Line Code Violations counter is counting errors at a rapid rate.

Workaround: Replace the CT3 line card with an upgraded line card. CT3 line cards with Version 800-05547-04 Revision A0 or later have a hardware design change to avoid this problem. On older cards, you can work around the problem by removing the receive signal momentarily after the line card is powered on. For example, remove and reinsert the coaxial cable on the associated RX BNC connector on the rear of the chassis.


Under rare circumstances, closure of VBR-nrt VCs fail, leaving the associated VPI/VCI value unavailable for future use. This can occur for VCs with relatively small rates (such as PCR and SCR values under 1500 kbps) that are actively passing traffic at the time the VC is being closed. The symptoms are an IOS error message alerting the user to an Open_Channel failure with a status of 4 and an associated PVC that transitions to the inactive state.

Workaround: Ensure that all traffic is stopped on a PVC before modification or deletion. If this situation is encountered, use the hw-module slot slot_number reset command to reload the line card.


Under conditions in which the OC-12 ATM line card is reloaded while traffic is actively passing over multiple VCs, some or all of the VCs may not successfully reopen after the line card is reloaded.

This is indicated by one or more of the following error messages:

%C10K-4-LC_WARN:Slot[2/0] 1oc12atm-1 SAR:0/100 no Open_Channel ack
      returned for reassembly device (handle 0x0001)

%C10K-4-LC_WARN:Slot[2/0] 1oc12atm-1 SAR:0/100 Open_Channel failure for
      reassembly device (handle 0x0001), status 2

Workaround: Reload the line card firmware by using the hw-module slot slot_number reset command. If the problem persists, stop the traffic and reload the line card firmware.


The default logging parameter (logging rate-limit console all 10 except critical) sets console logging to disabled.

Workaround: Enter the logging console critical command to view the most important events such as card up/down and toaster failure events.


For VBR-nrt VCs with low SCR values (400 kbps and below), a steady stream of small packets (for example, 64 byte packets) only achieves roughly 85% of the requested SCR.

Workaround: There is currently no workaround.


If you enter the clear ip mroute command on a system with large multicast groups, CPU hog issues may arise that cause problems of moderate severity (such as losing keepalives).

Workaround: Do not use the clear ip mroute command in large multicast groups.


Mass configuration (which occurs during boot/reload and can occur during link state changes) takes a long period of time (for example, over 40 minutes for 2000 VCs associated with a main interface) with large numbers of PVCs (100s to 1000s). This problem occurs when attempting to configure large numbers of PVCs on the main interface (or multipoint subinterfaces) with static maps on each PVC.

Workaround: Do not configure more than 500 PVCs on a single OC-12 ATM line card or more than 900 PVCs on a Cisco 10000 ESR.


Occasionally, an alarm LED appears as active even though no alarms are indicated after you enter the show controller command.

Workaround: Perform shut/no shut commands on the SONET controller. For example:

conf t
controller sonet 7/0/0
no shut


If you reload a Cisco 10000, some initialization messages are logged to the console before the startup-config is loaded. These initialization messages are transitional and may report an incorrect state, especially for the FastEthernet interface.

00:00:15: Downloading Microcode: file=system:pxf/ucode_file, 
version=2.0(21.4), description=Nightly Build Software created Wed 
13-Sep-00 00:38
00:00:21: %LINK-3-UPDOWN: Interface Ethernet0/0/0, changed state to up
00:00:21: %LINK-5-CHANGED: Interface FastEthernet0/0/0, changed state to 
00:00:23: %LINEPROTO-5-UPDOWN: Line protocol on Interface Ethernet0/0/0, 
changed state to up
 0:00:23: %LINEPROTO-5-UPDOWN: Line protocol on Interface 
FastEthernet0/0/0, changed state to down

These messages are not displayed in the buffered log.

Workaround: Ignore these messages.


The show atm pvc command displays 'Unexpected QoS type' for its traffic parameters. This occurs when a PVC was previously configured with only an ATM vc-class, and then the vc-class was subsequently deleted.

For example:

 sw-apollo-3(config)#vc-class atm test
 sw-apollo-3(config-vc-class)#vbr-nrt 1000 1000 10
 sw-apollo-3(config)#int atm 3/0/0
 sw-apollo-3(config-if)#pvc 200
 sw-apollo-3(config-if-atm-vc)#class-vc test
 sw-apollo-3#sh atm vc
                VCD /                                     Peak Avg/Min 
Interface     Name   VPI   VCI  Type   Encaps     Kbps   Kbps  Cells Sts
 3/0/0         1       0   200   PVC    SNAP       1000   1000   10   UP
 Now delete the vc-class :
 sw-apollo-3#conf t
 sw-apollo-3(config)#no vc-class atm test
 sw-apollo-3#sh atm vc
                VCD /                                     Peak Avg/Min 
Interface     Name   VPI   VCI  Type   Encaps     Kbps   Kbps  Cells Sts
3/0/0          1      0    200   PVC    SNAP    %Unexpected qos type UP

Workaround: Configure the vc directly using conventional means (non ATM vc-classes), or remove the vc and recreate it with a new ATM vc-class.


The show interface command output occasionally displays an extremely large number of configured VCs which do not truly exist.

Workaround: There is currently no workaround.


Under normal (IMIX) traffic loads, the OC-12 ATM line card reassembler may inappropriately drop packets, yielding less than line rate.

This is indicated by an increase in "input error" and "abort" counts in the show interface display for the line card in question.

Workaround: There is currently no workaround.


With multiple PVP tunnels, if the aggregate traffic received by one or more of the PVPs is heavily oversubscribed (starting at about 110% of the tunnel's PCR rate), the traffic on companion PVP tunnels on that interface may experience throughput that is lower than expected.

Workaround: There is currently no workaround.


When you boot the Cisco 10000, the system may display the following messages:

*Oct 17 12:32:48.287: %SNMP-3-TRAPBLOCK: Attempt to generate SNMP trap 
from a process with blocking disabled
 -Traceback= 60565064 606A6B34 60678238 60678438 6067AD88 6067AF30 
602FCBDC 6024817C 60248168

Workaround: Ignore the messages.


If incoming multicast packets match an input access list that has the log option enabled, the output of the show log command and show access-list commands display double the number of matches.

Workaround: There is currently no workaround.


If you perform an SNMP walk or view entries in the if table, cef-layer internal interfaces appear in the interface table.

Workaround: Ignore interfaces whose descriptor contains the string .0-cef layer.


Kentrox DS3 subrate mode does not work when you set it to full bandwidth (45.2 Mbps on Kentrox CSU, 44210 kbps on a Cisco10000 ESR).

Workaround: Set the subrate mode on the ChOC-12 board to Digital Link mode, bandwidth = 44210. This fix works with and without scrambling.


Line Protocol on one or two T1s may not come up when you perform a reload with a large configuration (for example, 1008 T1s with PPP encap or 504 MLPPPs).

Workaround: Reload the linecard using the command hw slot slot_number reset.


If a redundant power supply is removed or a line card is OIRed, the SNMP traps are generated by the syslog mib. There is a request to generate these traps using the env, mon, and entity mibs respectively.

Workaround: Filter the SNMP traps using the syslog mib.


If multiple VBR and UBR VCs are configured together and traffic is flowing over both types of VCs, throughput on the VBR VCs may suffer (may fall noticeably below the associated Sustainable Cell Rate [SCR]) while UBR traffic appears unaffected.

Workaround: There is currently no workaround.


Occasionally, after you reload routers (with background traffic load equal to no_drop rate), the throughput is some 3 to 400 pps below the expected rate.

Workaround: The rate does not recover until the traffic is stopped and restarted.


On rare occasions, the OC-12 ATM line card segmenter fails to respond to requests for statistics. This is indicated by one or more of the following error messages:

%C10K-4-LC_WARN:Slot[2/0] 1oc12atm-1 SAR:no Get_Channel_Stats ack
      returned for segmentation device, continuing

%C10K-4-LC_WARN:Slot[2/0] 1oc12atm-1 SAR:segmentation device
      Get_Channel_Stats failure, status is 0x02, continuing

Workaround: Reload the line card firmware by using the hw-module slot slot_number reset command.


On rare occasion, after a single reload while under load, the Gigabit Ethernet line card is up but drops nearly all packets on the output queue.

Workaround: Reset the linecard from the console with the hw-module slot n reset command.


Under some conditions, the OC-12 ATM line card reassembler may be unable to process all incoming packets and the reassembler may inaccurately count these erroneous packets as aborts. This may be indicated by an increase in the input "abort" counter in the show interface command display.

Workaround: There is currently no workaround.


In the unlikely event of a total failure of the cooling fan tray, or any other scenario resulting in high-temperature operation, the Cisco 10000 continues running, and does not power off.

Workaround: If you observe fan failure or over-temperature alarms or log messages are observed, you should immediately power down the chassis until the problem is corrected.


You may get a redundancy error message on cards that are not redundant.

Workaround: There is no workaround for this message, but it does not affect service. The message may be ignored.


If you execute more than 126 PVP creation commands, this leads to Open Tunnel failures on the line card.

%ATM: PVP, interface specific setupvp failure
%C10K-3-LC_ERR: Slot[3/0] 1oc12atm-1 SAR: Open_Tunnel failure for 
segmentation device (vpi 2), status 1
02:46:12: config_vp event failure vpi=2, reason code=3

Workaround: Reload the line card firmware using the hw-module slot n reset command, where n is the number of the slot where the line card resides.


When the dir or show slot0: or show slot1: command is issued, the router reports "Open device slot0 failed (Device not ready)."

Workaround: Use the dir disk0: and dir disk1: commands.


ISIS adjacencies recalculated with 65-85MB of tcp traffic to rtr.

Workaround: Because this problem is caused by hackers we recommend that you use access lists to block out hackers. Access lists prevent packets from punting to the RP and take down the router.


A Cisco 10000 router running Release 12.0(10)SL may experience a buffer leak when interfaces are down but not administratively down.

Workaround: Administratively shut down the interfaces.


If large OIDs (1024 .1 fields) are sent to the router, the Cisco 10000 stops responding.

Workaround: There is currently no workaround.


When a t1/e1 is deleted, ip routes associated with subinterfaces are not removed.

Workaround: Manually issue a no ip route ip_address.


The flash file delete function may choose the wrong default device when you request deletion of a file from flash storage. The incorrect default used is slot0:.

Workaround: Prefix the filename with disk0: when specifying the filename.


The no pos report all command does not work. The pos report all configuration line remains in the configuration file.

Workaround: There is currently no workaround.


PVCs in the down state can still pass traffic. When a PVP is created with associated F4 OAM VCs and those F4 OAM VCs do not come up (for instance, because there is no VP at the far end or the VP at the far end did not create F4 OAM VCs), traffic can still be passed on the PVCs associated with the PVP in question. When the F4 OAM loopback cells are not returned, IOS declares all PVP associated PVCs to be down. It does not, however, notify the forwarding engine or the line card. This allows traffic routed over the PVCs in question to pass.

Workaround: There is currently no workaround.


When configuring CAR on the Cisco 10000, CAR does not differentiate between user traffic and control traffic. Because of this, if a user sets up CAR on an interface to restrict the amount of bits per second allowed on the interface, CAR may drop control packets. This may cause line flaps or lost routing updates on the interface.

Workaround: Use access lists to help tag which traffic to drop.


On a Cisco 10000 system with channelized OC-12 line cards, the output of the show controllers command is incomplete and incorrect:

The output does not show any information about SONET controllers.

The output shows information on data structures which are not relevant to the C10000 system.

The output mixes the information between paths configured in T3 mode and those configured in VT mode (which has not yet been released).

Workaround: Issue show controller commands for each controller individually. The aggregated command does not work.


If in a Frame-Relay environment a handful of interfaces are flapping continuously, the interface statistics report input errors (overruns) on the flapping interfaces.

Workaround: There is currently no workaround.


Exit is displayed two times in config mode under the policy-map class section of IOS. If you are in config mode and are configuring policy-map statements, you cannot use the exit statement to get back to global config mode.

Workaround: Use Ctrl-Z to exit config mode, or enter a global config mode command that accesses config mode.


Following a reload of the Cisco IOS software, the Gigabit Ethernet interface does not always come back up. The interface remains in the "GigabitEthernet1/0/0 is down, line protocol is down" state.

Workaround: Perform a shut/no shut to the interface to restore communications.


During a reload, if the router is continuously receiving IP packets, you may see CPUHOG messages in the log, and the router may take longer to come up. The problem only occurs during initialization.

Workaround: There is currently no workaround. After the interfaces and PVCs are all up and functional, you do not see the CPUHOG messages in the log.

Resolved in Cisco IOS Release 12.0(14)SL1

This section lists problems that are resolved in Cisco IOS Release 12.0(14)SL1. For a list of problems that were resolved in previous Cisco IOS Releases, refer to the release notes for those particular versions.


Snmpwalk skips OIDs, so some interfaces are missed in the walk.

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 users can order the Documentation CD-ROM through the online Subscription Store:

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

Documentation Feedback

If you are reading Cisco 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 e-mail 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 95134-9883

We appreciate your comments.

Obtaining Technical Assistance

Cisco provides as a starting point for all technical assistance. Customers and partners can obtain documentation, troubleshooting tips, and sample configurations from online tools. For registered users, additional troubleshooting tools are available from the TAC website. 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. provides a broad range of features and services to help customers and partners streamline business processes and improve productivity. Through, 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 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, 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.

Contacting TAC by Using the Cisco TAC Website

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

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, go to the following website:

If you cannot resolve your technical issue by using the TAC online resources, registered users can open a case online by using the TAC Case Open tool at the following website:

Contacting TAC by Telephone

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

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.