Cisco 10000 Series Routers

Cisco IOS Release 12.0(9)SL

  • Viewing Options

  • PDF (207.2 KB)
  • Feedback
Release Notes for the Cisco 10000 ESR for Cisco IOS Release 12.0(9)SL

Table Of Contents

Release Notes for the Cisco 10000 ESR for Cisco IOS Release 12.0(9)SL


Upgrading to a New Software Release

System Requirements

Cisco 10000 ESR Software Features

Limitations and Restrictions

Important Notes


Obtaining Documentation

World Wide Web

Documentation CD-ROM

Ordering Documentation

Obtaining Technical Assistance

Cisco Connection Online

Technical Assistance Center

Documentation Feedback

Release Notes for the Cisco 10000 ESR for Cisco IOS Release 12.0(9)SL

May 9, 2000

These release notes provide information about Cisco IOS Release 12.0(9)SL, which runs on the Cisco 10000 ESR. The release notes specifically refer to the image named: c10k-p6-mz.

These release notes are updated as needed to describe new features, memory requirements, hardware support, software platform deferrals, and changes to the microcode and related documents.

Cisco IOS Release 12.0(9)SL is based on Cisco IOS Release 12.0(9)S. For a list of the software caveats that apply to Cisco IOS Release 12.0(9)SL, see the "Caveats" section and the release notes for Cisco IOS Release 12.0S.

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


Obtaining Documentation

Obtaining Technical Assistance

Upgrading to a New Software Release

For specific information on 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

You must have a minimum of 128 MB of memory on the Performance Routing Engine (PRE).

If your configuration file describes more than 500 complex interfaces, your Cisco 10000 ESR may require additional memory.

Cisco 10000 ESR Software Features

The following features are supported on the Cisco 10000 ESR.

Table 1 Principal Software Features


Cisco Discovery Protocol (CDP)

Simple Network Management Protocol (SNMP)





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 (URDL)

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

Internet Key Exchange (IKE)

Terminal Access Controller Access Control System Plus (TACACS+)

Message Digest 5 (MD5) for use with SNMPv2 and SNMPv3

Limitations and Restrictions

The Channelized OC-12 (ChOC-12) line card, which is described in the Cisco 10000 ESR documentation, is not currently supported.

Important Notes

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) sessions.

Note Each T1 interface in an MLP bundle represents a single PPP session. Thus, configuring 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).


This section lists caveats for the Cisco 10000 ESR running under IOS Release 12.0(9)SL.


BGP session fails to establish after matching BGP neighbor passwords.

Workaround: When you use passwords on BGP links, do not change the passwords when a BGP session is established. If you need to modify a BGP link password, first close the applicable BGP session (no neighbor w.x.y.z), then reconfigure the BGP session with the new password.


After you execute the neighbor default originate command, the default route may not be listed in BGP table of peered routers.

Workaround: There is currently no workaround.


A service policy that contains a set action might get removed from the interface upon router reload. This problem is seen on gigabit Ethernet interfaces.

Workaround: After reload, reapply the service policy again.


Traffic does not pass on PVCs statically configured on that interface. This happens if keepalives are disabled before an interface encapsulation is changed to Frame Relay, and not subsequently re-enabled.

Workaround: Configure keepalives after specifying Frame Relay encapsulation.


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. Use the no card command to remove references to cards that are not in the chassis.


Spurious FBB Line Card Events message may appear on the console after a reset or reload of the line card, microcode, or after a PRE cutover. Data flow is not affected.

Workaround: There is currently no workaround.


Data flow from the gigabit Ethernet line card stops. No error messages are reported.

Workaround: If this event occurs, reset the line card. In addition, you may need to reduce the amount of traffic that goes through the card.


Heavy, nonfast-switched traffic may cause line cards to reset. If a line card stops responding, all configured interfaces on that card are marked as nonfunctional and data flow ceases until communication with the PRE is reestablished. In addition, the log buffer shows OIR and channel events.

Workaround: Avoid using nonfast-switched traffic.


Netboot may fail if a large number of channels is configured. When tested with 1000 channels configured, the system displayed the error message: "No usable interfaces."

Workaround: Boot from disk.


On some occasions, virtual links that are created on OC-12 POS interfaces report that they are running, but no routing information traverses them. Vlinks are typically used where it is not possible to physically connect all areas in an OSPF autonomous system to the backbone area (area 0).

Workaround: Rearrange your network to eliminate the need for the virtual link, or create static routes instead of virtual links.


"MAJOR_FAULT:PXF DMA TBB Length Error" is posted to SysLog and the pxf microcode reloads with heavy traffic loads and with CAR enabled.

Workaround: The microcode reloads and the system recovers.


In some cases, redundancy events are not logged with buffered logging turned on.

Workaround: There is currently no workaround.


Frame Relay PVC statistics do not account for Frame Relay encapsulation bytes.

Workaround: Multiply the inbound or outbound per-PVC packets by four. Add this number to the octets transmitted/received to produce the total number.


The following message may appear on the console output or the console log:

%CI-3-PSFAIL: Power entry module 0 failure.

Workaround: Ignore the message.


When you display interface statistics, the output queue drops counter is always 0, even if packet drops should be displayed.

Workaround: There is currently no workaround.


When you display interface statistics using the show interface command, the packets input and byte fields may display numbers greater than expected.

Workaround: There is currently no workaround.


When you use the Frame Relay autosense feature, the Cisco 10000 ESR sends out all three LMI status message types immediately after the interface starts responding. However, sometimes the switch at other end is not ready to receive the messages and, as a result, misses one or two messages. LMI autosense waits until the next scheduled interval to send out the messages again. This problem primarily affects clear channel CT3 interfaces.

Workaround: There is currently no workaround.


If you copy the configuration file from PRE-A to NVRAM in a system with redundant PREs, the secondary PRE may crash.

Workaround: There is currently no workaround.


When you create clear-channel interfaces on a CT3 line card, the interfaces are listed out of order in the startup and running configurations. They are listed at the bottom of the list of interfaces.

Workaround: No workaround is required.

CSCdr38199, CSCdr38123, CSCdr35776

If you send packets with an MTU size of more than 4470 bytes, ping failure messages may appear. In addition, assertion failures may be listed in the log file.

Workaround: Send packets that contain an MTU size that is under 4470 bytes.


In some cases, the show interface command reports that hardware was removed even if the interfaces continue to pass traffic. For example:

Router#show interface serial 2/0/1/1:0
 Serial2/0/1/1:0 is up, line protocol is up
   Hardware has been removed

Workaround: No workaround is required. If the interfaces are up, the card must be in its slot.


POS and GE line cards cannot pass data even though the system indicates the line is running. This problem rarely occurs.

Workaround: Reset the line cards using shutdown command and no shutdown command.


If you execute the T3 mdl command on the CT3 line card, this causes the PRE to reboot.

Workaround: Do not configure MDL.


When you change a clear channel interface that is running to channelized on a CT3 card, an "Assertion Failure" message may appear.

Workaround: Either ignore the message or bring down the clear channel interface before you channelize it.


Regardless of whether or not interfaces are configured on a CT3 line card, the system displays a message similar to the following:

00:15:41:%LINK-3-UPDOWN:Interface Serial1/0/5, changed state to up

Workaround: Disregard the message.


In some cases, both the multilink interfaces and T1 member links are responding, but the IPCP state on the multilink interface stays in a down or listen state. This condition may occur randomly on multilink interfaces, when the Cisco 10000 ESR is reloaded. As a result, data does not pass through the multilink interfaces.

Workaround: Enter the shutdown and no shutdown commands on the multilink interface to bring the multilink interface and IPCP state to up.


OC-12 POS interface status incorrect after IP configuration.

Workaround: There is currently no workaround.


When the CT3 line card pings a series of 100 byte packets followed by a series of 1000 bytes packets, the CT3 line card may experience a ping failure. The error was only seen after you reload the line card.

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


The current eboot image, if booted by itself from rommon, reverts back to rommon. However, if the current eboot image is used to boot a run-time image from a device other than bootflash, as in a reload of a run-time image, the boot of the run-time image is successful. The problem is only seen if the eboot image is booted directly.

Workaround: Boot only a full-function runtime image.


If you remove an interface without first removing a service map and then reconfiguring the interface with a service map, this results in multiple status entries for that service map. The multiple status entries appear if you enter the show policy-map interface command.

Workaround: Remove the service map from the interface before you remove the interface.


After you issue multiple card/no card command sequences for the same card type in the same slot, the interface configuration for that card no longer appears in the display output of a show running-config command.

Workaround: Do not issue multiple card/no card command sequences.


On occasion, an interface that was responding before a PRE cutover is no longer responding after the cutover. Look at the display from the show interface command to view the interface status.

Workaround: Execute the shutdown command, followed by the no shutdown command on the failing interface.


The number of gigabit Ethernet interfaces may be incorrectly reported by the show version and show hardware commands. The reported number should match the number of gigabit Ethernet line cards that are inserted and have booted successfully in the chassis.

Workaround: There is currently no workaround.


If you enable HSRP on a gigabit Ethernet interface, the standby state remains at Init and does not change to Standby or Active. In addition, the timer values remain at 0. For example:

Router> show standby GigabitEthernet3/0/0
 GigabitEthernet3/0/0 - Group 0
   Local state is Init, priority 100, may preempt
   Hellotime 0 holdtime 0
   Hot standby IP address is configured
   Active router is unknown expired
   Standby router is unknown expired
   Standby virtual mac address is 0000.0c07.ac00

Workaround: Execute the shutdown command, followed by the no shutdown command on the failing interface.


FastEthernet 0/0/0 is configured with static IP address, but still sends out DHCP packets. The router appears to be sending out DHCP packets with the backplane Ethernet MAC address and an IP address of

Workaround: There is currently no workaround.


When the router is booted with no startup configuration file, the Setup facility runs to allow the user to create a simple startup configuration. As the dialog runs, a character entered by the user does not echo for ¼ to ½ a second and, if the user types quickly, the characters are displayed at a rate of about one every ¼ to ½ second.

Workaround: No workaround required.


If you issue the ip host-routing command, this resets the FastEthernet interface.

Workaround: The console connection is restored after a few moments.


QPPB may overwrite the qos-group value settings that are input using QoS configuration mode (also called modular CLI) commands. A simple configuration that could cause this problem:

The input interface is configured with both a QPPB qos-map and an input policy map that sets the qos-group value to a value other than zero.

The output interface is configured with an output policy map, which operates on the assigned qos group value.

Workaround: There is no simple workaround. You may be able to use different QPPB and policy map settings to achieve your goals.


Under some traffic conditions, no traffic is passed through the gigabit Ethernet interface. Although the input errors and ignored counters in the show interface command display increment, the packets input counter does not.

Workaround: Reset GE line card using the hw-module slot slot/subslot/port reset command.


Reload causes "logging console debugging" to change to '"logging console critical." On reload, user may not see system/controller/interface status messages, despite having saved logging console debugging configuration before the reload.

Workaround: Configure logging console debugging on reload.


The first autoboot fails if no boot image is specified in the configuration, or if all autoboots to the images specified in the configuration fail.

Workaround: No workaround is required and the user can ignore the error message. After the first autoboot failure, the system automatically boots the first image in bootflash again. The second boot is always successful and the system comes up properly.

Obtaining Documentation

World Wide Web

You can access the most current Cisco documentation on the World Wide Web at,, or

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. Therefore, it is probably more current than printed documentation. The CD-ROM package is available as a single unit or as an annual subscription.

Ordering Documentation

Registered CCO users can order the Documentation CD-ROM and other Cisco Product documentation through our online Subscription Services at

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

Obtaining Technical Assistance

Cisco provides Cisco Connection Online (CCO) as a starting point for all technical assistance. Warranty or maintenance contract customers can use the Technical Assistance Center. All customers can submit technical feedback on Cisco documentation using the web, e-mail, a self-addressed stamped response card included in many printed docs, or by sending mail to Cisco.

Cisco Connection Online

Cisco continues to revolutionize how business is done on the Internet. Cisco Connection Online 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.

CCO's broad range of features and services helps customers and partners to streamline business processes and improve productivity. Through CCO, you will find information about Cisco and our networking solutions, services, and programs. In addition, you can resolve technical issues with online support services, 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 CCO to obtain additional personalized information and services. Registered users may order products, check on the status of an order and view benefits specific to their relationships with Cisco.

You can access CCO in the following ways:



Modem using standard connection rates and the following terminal settings: VT100 emulation; 8 data bits; no parity; and 1 stop bit.

From North America, call 408 526-8070

From Europe, call 33 1 64 46 40 82

You can e-mail questions about using CCO to

Technical Assistance Center

The Cisco Technical Assistance Center (TAC) is available to warranty or maintenance contract customers who need technical assistance with a Cisco product that is under warranty or covered by a maintenance contract.

To display the TAC web site that includes links to technical support information and software upgrades and for requesting TAC support, use

To contact by e-mail, use one of the following:

E-mail Address


Hanzi (Chinese)

Kanji (Japanese)

Hangul (Korean)



In North America, TAC can be reached at 800 553-2447 or 408 526-7209. For other telephone numbers and TAC e-mail addresses worldwide, consult the following web site:

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, for your convenience many documents contain a response card behind the front cover. Otherwise, you can mail your comments to the following address:

Cisco Systems, Inc.
Document Resource Connection
170 West Tasman Drive
San Jose, CA 95134-9883

We appreciate and value your comments.