Cisco IOS Release 12.0(25)SX9

These release notes provide information about Cisco IOS software Release 12.0(25)SX9 for the Cisco 10000 series router. 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(25)SX9 is based on Cisco IOS Release 12.0(25)S. The Cisco 10000 series router supports a subset of the new features in Cisco IOS Release 12.0(25)S. For more information, see the "New Features—Cisco IOS Release 12.0(25)S" section. This section lists the features supported on the Cisco 10000 series router.

To view the release notes for the following Cisco IOS software releases, go to the following URLs:

System Requirements

This release requires that you have the performance routing engine (PRE), part number ESR-PRE1 installed in the Cisco 10000 router chassis. To verify which PRE is installed in the router, use the show version command.

Memory Requirements

The following table lists memory requirements for the Cisco 10000 series router:


Feature Set by Router	Image Name	Flash Memory	DRAM Memory	Runs From
Router	c10k-p10-mz	40 MB	512 MB	RAM
Service Provider/ Secured Shell 3DES	c10k-k4p10-mz	40 MB	512 MB	RAM

Upgrading to a New Software Release

Upgrading from Earlier Cisco IOS Releases

Upgrading from Cisco IOS Release 12.0(14)SL or from Earlier Releases Based on Cisco IOS Release 12.0(x)SL

If you are upgrading your software from Cisco IOS Release 12.0(14)SL or from earlier releases based on Cisco IOS Release 12.0(x)SL to Cisco IOS Release 12.0(25)SX9, save your current configuration file. If you decide to reinstall Cisco IOS Release 12.0(14)SL or an earlier release, you must also reinstall the configuration file associated with that release because some Border Gateway Protocol (BGP) configuration file entries in Cisco IOS Release 12.0(25)SX9 are not compatible with Cisco IOS Release 12.0(14)SL or earlier releases.

Upgrading Software on Redundant PREs

The procedure included in the "Upgrading Software on Redundant PREs" section instructs you to tell the Cisco 10000 series router the location in which the new boot image resides. Be sure to specify c10k-p10-mz instead of the c10k-p6-mz image name indicated in the documentation.

New Features—Cisco IOS Release 12.0(25)SX9

Cisco IOS Release 12.0(25)SX9 contains no new features, but includes all of the new features and performance enhancements introduced in Cisco IOS Release 12.0(25)SX1 and Cisco IOS Release 12.0(25)SX, which is based on Cisco IOS Release 12.0(25)S.

New Features—Cisco IOS Release 12.0(25)SX1

Cisco IOS Release 12.0(25)SX1 provides the following performance enhancements, but contains no new features.

This release improves the performance of the VTMS Link Utilization feature. The default queue size is based on link bandwidth instead of queue bandwidth as in previous releases.

The QA Error Recovery feature enables the router to recover quickly from problems known as QAERRORs, which can be caused by hardware or software issues. When a QAERROR occurs, the router might stop responding while it tries to recover from the problem. QA error recovery reduces the router down time to as little as one second. Previously, a fully loaded router might be down for up to five minutes (300 seconds).

The QA error recovery feature is enabled by default. To disable the feature, issue the following command:

When QA error recovery is successful, the router displays a console message indicating success. In addition, the show controllers cbus command indicates the number of QAERROR recoveries.

The following sample console messages show an occurrence of a QAERROR and the router's recovery from the error. The router might display additional messages during error recovery (which can help service technicians diagnose the cause of the problem).

The following example shows QA error recovery information in show controllers cbus command output:

New Features—Cisco IOS Release 12.0(25)SX

Cisco IOS Release 12.0(25)SX introduces support on the Cisco 10000 series router for the following features:

The Policy-Map Scaling feature increases the system-wide number of quality of service (QoS) policy maps that you can configure. In Cisco IOS Release 12.0(25)SX, the Cisco 10000 series router supports up to 4,096 policy maps. Each policy-map command counts as one policy map. The policy-map command syntax is unchanged. The maximum number of classes that you can configure in a policy is 32 classes.

The Percent-Based Policing feature enables you to specify the police rate as a percentage of the bandwidth of the network interface on which policing is applied. To specify the police rate as a percentage, use the percent percent option of the police command:

The percent argument is a value from 1 to 100 and is required when you use the percent keyword.

When you use a percent-based police command within a nested policy, the police percent is based on the policy's topmost, class-default, shape rate. Otherwise, the police percent is based on the bandwidth of the network interface on which the police command is applied.

The Random Early Detection (RED) with Queue-Limit feature expands your ability to customize the size of a RED queue. In Cisco IOS Release 12.0(25)SX, you can simultaneously use the queue-limit and random-detect commands in the same class of a policy.

The Enhanced RED Statistics feature maintains RED drop statistics for each IP precedence or differentiated services code point (DSCP) value.

Note In releases earlier than Cisco 12.0(25)SX, RED drop counts were maintained only for each class.

The 3-Level Policies feature increases the hierarchical levels of a nested QoS policy from two to three levels. A 3-level policy is typically used to define the transmission capacity of a virtual circuit in the top level, class-based queuing at the middle level, and marking or metering in the bottom level.

The service-policy command configured inside a policy map is used to define a hierarchical policy. The syntax of the command is unchanged. You can use the service-policy command in the top and middle levels of a 3-level policy.

The Virtual Circuit (VC) Oversubscription feature enables service providers to improve network utilization of otherwise underutilized shared networks by leveraging statistical multiplexing on ATM, Frame Relay, and IEEE 802.1Q networks. Instead of supporting only unconditional reservation of network bandwidth to VCs, the Cisco 10000 Cisco 10000 series router offers VC oversubscription to statistically guarantee bandwidth to VCs.

To configure VC oversubscription for Frame Relay and IEEE 802.1Q, use the service-policy command. You can optionally use the service-policy class configuration command, creating a nested policy to manage traffic within a virtual circuit. For this reason, the term Nested Policy-Map Oversubscription is sometimes used to refer to VC Oversubscription.

To enable oversubscription of ATM VCs, you must configure the following interface configuration command in service-internal mode:

Note You do not need to use the service-policy command to specify the ATM VC oversubscription, because a variable bit rate (VBR) ATM VC uses sustained cell rate (SCR) to define the VC's average transmission rate.

The External Border Gateway Protocol (EBGP) Label Distribution feature enables you to configure a carrier supporting carrier network that uses BGP to distribute routes and MPLS labels between the provider edge (PE) and customer edge (CE) routers of a backbone carrier and a customer carrier. The backbone carrier offers BGP and MPLS VPN services. The customer carrier can be one of the following:

For information on how to use BGP to distribute MPLS labels and routes for both types of customer carrier, refer to the MPLS VPN Carrier Supporting Carrier—IPv4 BGP Label Distribution, Release 12.0(21)ST feature module and the Inter-Autonomous Systems for MPLS VPNs, Release 12.1(5)T feature module.

New Features—Cisco IOS Release 12.0(25)S

The following is a brief list of the new features in Cisco IOS Release 12.0(25)S on which Cisco IOS Release 12.0(25)SX is based. Only new features that are supported by the Cisco 10000 Cisco 10000 series router are listed here. New features for other platforms (such as the Cisco 12000 series router) are not listed.

Introduced on the Cisco 10000 Cisco 10000 series router in Cisco IOS Release 12.0(23)SX, the Link Fragmentation and Interleaving (LFI) feature reduces delay and jitter on slower-speed links by breaking up large datagrams and interleaving low-delay traffic packets (such as voice) with the smaller packets resulting from the fragmented datagram. The feature supports Frame Relay (FRF.12) end-to-end and Multilink PPP (MLPPP).

Introduced on the Cisco 10000 Cisco 10000 series router in Cisco IOS Release 12.0(23)SX, the single rate 3-Color Marker feature meters an IP packet stream and marks its packets different colors, based on the Committed Information Rate (CIR) and two associated burst sizes: Committed Burst Size (CBS) and Excess Burst Size (EBS). This feature is useful, for example, for ingress policing of a service, where service eligibility is determined only by the burst's length, and not its peak rate.

The Multicast for Multiprotocol Label-Switching (MPLS)/Virtual Private Network (VPN) feature enables service providers to offer multicast services over their MPLS core network. This feature was introduced on the Cisco 10000 Cisco 10000 series router in Cisco IOS Release 12.0(23)SX.

This feature enables you to limit the number of routes that can be redistributed into the Open Shortest Path First (OSPF) protocol. The feature helps to eliminate the potential for flooding that might occur when a large number of routes are accidentally redistributed into OSPF.

This feature enables you to limit the number of routes that can be redistributed into the Intermediate System-to-Intermediate System (IS-IS) protocol. This feature helps to eliminate the potential for flooding that might occur when a large number of routes are accidentally redistributed into IS-IS.

This feature enables you to slow down the rate at which the Open Shortest Path First (OSPF) protocol sends Link State Advertisement (LSA) updates during periods of network instability. This feature uses a back-off algorithm to perform the LSA throttling.

Limitations and Restrictions

The following limitations and restrictions apply to the Cisco 10000 series router 3-Level Policies feature:

•

A top-level policy must specify only the class named class-default with only the shape command specified before the service-policy command attaches an inner policy.

•

In an inner policy, to attach a service-policy command to a class's bottommost policy, do not configure the police and set commands for the class. Classes without a service-policy command configured are not restricted from using the police and set commands.

•

In a bottommost policy, configure only the police and set commands for a class.

•

Define each bottommost class map to match only those packets that also match its parent class map. For example, the union of the set of packets of a bottommost class and that of its parent class must be equal to the set of packets that match the parent class.

•

The nested-policy shape rate is reserved for nested-policy traffic only. Excess bandwidth is not used for other traffic.

Note

The actual shape rate applied to nested-policy traffic might differ from that specified in the policy. For example, a specified shape rate of 10.5 Mbps might be mapped to 11 Mbps. Use the command show policy-map interface to determine the actual shape rate.

Open Caveats—Cisco IOS Release 12.0(25)SX9

Table 1 Open Caveats in Cisco IOS Release 12.0(25)SX9
Caveat	Description
CSCea42432	(Duplicate of CSCea52307) If you delete a service policy from an ATM interface, a traceback message or error message may appear. Workaround: None.
CSCea74742	Policing conformed packets might be less than expected when the normal burst size is set to less than two times the packet size. Workaround: Change the normal burst size to a value larger than 2 times the police frame size.
CSCea93642	When a large number of policy maps are configured on the Cisco 10000 Cisco 10000 series router, it could take more time than expected before all the policy maps activate. Before an interface's policy map activates, the traffic on the interface receives default treatment. The router compiles a super access control list (ACL) for each policy map configured. On an average, the compilation of one super ACL takes approximately one-half second. When a large number of policy maps are configured, the router requires more time to compile all of the super ACLs. Workaround: Wait approximately 0.65 seconds for each policy-map to become operational. For more than one policy map, wait (N * 0.65) seconds for all the policy maps to become operational (where N is the number of policy maps).
CSCeb02953	When traffic is sent through an ATM subinterface to which a QoS service policy is attached, the packet count of the output queue obtained by using the show policy-map interface command does not match the packet output count obtained by using the show interface atm-subinterface command. Workaround: To obtain the correct packet output count, use the show policy-map interface command. Do not use the show interface atm-subinterface command to obtain packet output counts for ATM subinterfaces.
CSCeb27728	When microcode is reloading and traffic is running over the interface, the interface output packet and byte counters display incorrect values. Workaround: Clear the counters.
CSCeb38728	Under extremely rare circumstances, when you remove a 3-level policy map attached to 4,000 VLAN interfaces, the Cisco 10000 series router stops responding. Workaround: None.

Resolved Caveats—Cisco IOS Release 12.0(25)SX9

This section describes caveats that were fixed in Cisco IOS Release 12.0(25)SX9. These caveats also include all resolved caveats in Cisco IOS Release 12.0(25)S3 and Cisco IOS Release 12.0(25)S4.

For information about caveats fixed in other Cisco IOS releases, refer to the appropriate Release Note document at the following URL:

Previously, when a Multiprotocol Label Switching (MPLS) edge router performed hardware-assisted forwarding, the hardware and software MPLS forwarding tables might be inconsistent. An example of an MPLS edge router is a provider edge (PE) router in an MPLS virtual private network (VPN).

This problem occurred when you executed either of the following command sequences on the MPLS edge router:

•

The shutdown command followed by the no shutdown command on one of the outgoing interfaces enabled for MPLS.

•

The no mpls ldp command followed by the mpls ldp command on one of the outgoing interfaces enabled for MPLS.

Previously, the trace route did not display MPLS tag switching. When you did a trace route from CE to CE in an MPLS environment, the trace route did not display tag switching. The output of trace route looked like, Tracing the route to 173.0.12.2 1 172.0.12.2 [AS 100] 0 msec 0msec 0 msec 2 * * * 3 173.0.12.1 [AS 100] 0 msec 0 msec 0 msec 4 173.0.12.2 [AS 100] 0 msec 0 msec *.

Previously, the BGP cache entry leaked when you removed the BGP configuration in the router.

Previously, under certain circumstances, SAA reported an incorrect number of out-of-sequence packets.

Previously, there was a PXF crash in column 3, which caused forwarding to stop for 10-50 seconds. This problem occurred rarely, when a policy map or class map within a policy was changed, that policy was immediately applied to an interface, and traffic was already flowing on that interface.

Previously, the following error message appears in the log of a Cisco 10000 series router: "%TCP-6-TOOBIG: Tty0, too many bytes of options (44)"

Previously, the object rttMonEchoAdminNumPackets could be set to values beyond the valid range, which is 1 - 60000.

Previously, a Flash memory card became corrupted. The output of the show flash-filesystem EXEC command displayed the following information: "Open device slot0 failed (Bad device info block)". This problem occurred on a Cisco platform when you performed an online insertion and removal (OIR) of the Flash memory card.

Previously, the no service-policy command resulted in traceback messages. Other than the traceback messages, the router continued to work normally. This problem occurred only when the service policy contained the queue-limit command.

Previously, executing a show facility-alarm status command while an ATM interface was shut lead to inaccurate output from this command. This occurred if an ATM interface was shutdown.

Previously, when you changed the type of service (TOS) on packets encapsulated in a Multiprotocol Label Switching (MPLS) virtual private network (VPN) tunnel, the TOS of the interior (encapsulated) packet did not change appropriately and was classified incorrectly at the de-encapsulating router.

This problem occurred when you applied input policing to an interface, associated a virtual routing and forwarding (VRF) instance with the interface, the interface was receiving multicast traffic from the customer edge (CE) router, and the router was configured for MPLS VPN.

Previously, Random Early Detection maintained an average length of the outbound queue of a class of traffic, and randomly discarded newly arriving packets when the average fell within the configured range. A Cisco 10000 series router contained an error in the average queue length computation which made Random Early Detection too sensitive to the instantaneous queue length. This problem was seen on a Cisco 10000 series routers that ran Cisco IOS Release 12.0(27)S but may also have occurred in earlier releases.

Previously, under a specific configuration using multiple E1 (framed or unframed) interfaces and 1500-byte IP packets, the maximum priority queue (PQ) latency was greater than 2 times the specified maximum transmission unit (MTU) plus 6 milliseconds. The following describes the conditions under which this problem occurred.

Seven queues were configured on each (1984k) E1 interface with the following bandwidths: PQ - 98k, C1 - 256k, C2 - 256k, C3 - 256k, C4 - 256k, CD - 98k, and MGMT - 20k.

The high latency was observed with 20 interfaces configured and bidirectional traffic was being sent at the following (per interface) pps rates to each queue, respectively:

Previously, when you configured class-based weighted fair queuing (CBWFQ) on a Frame Relay permanent virtual circuit (PVC), queues could drop packets even if there was no traffic on other queues on the same link and the input traffic was less than the link bandwidth. This occurred when queue bandwidth was configured as a small percentage of link bandwidth.

Previously, the receive traffic rate on the priority queue was reduced if a policy map, with RED enabled on some of the queues, was removed and then re-applied to an interface while traffic was running. If the user removed and re-applied a policy map on an interface while traffic was running, the receive traffic rate on the priority queue may have been reduced and did not return to the level when the same policy map was originally applied to the interface. The issue only happened if the queues in the policy map had RED enabled and were in congestion (having RED drops) when the policy map was removed.

Previously, on a Cisco 10000 series router the PXF information was not correctly updated from the RP after a route change, causing packets to be sent untagged even though the RP showed that the packets should be sent as tagged. This problem occurred on a Cisco 10000 series router running Cisco IOS Release 12.0(26)S.

Previously, exp 0 dropped less than exp 1 in the MPLS_exp_other queue in a default configuration when a trunk service policy was applied on an OC12ATM tag interface. This problem occurred in the Cisco IOS release 12.0(25)SX3 image.

Previously, an ACL applied to an ATM subinterface might not function correctly after a PRE switchover. This problem occurred in a Cisco 10008 router that was configured with a PRE2.

Previously, when you configured Multiprotocol Label Switching (MPLS) over Multilink PPP (MLPPP), the parallel express forwarding (PXF) microcode reloaded. After the PXF microcode reloaded, packet forwarding resumed.

Previously, for MVPN traffic, multicast traffic streams were being punted from the PXF to the route processor. Normally PXF does this when a new stream needs to be created. However in this case, PXF behaved as if the streams were not present, even if the required (S,G)/(*,G) states existed. This symptom was observed on a Cisco 10000 series when the VRF index of the VPN was higher than 255. This occurred when 255 or more VRFs were configured or when some VRFs were created and deleted many times.

Previously, when a POS line card was shut down, the show facility-alarm status command still indicated alarms. When a line card was shut, there should have been no alarms for that line card. This symptom was observed on a Cisco 10000 series router with.a POS line card.

Previously, the parallel express forwarding (PXF) processor could drop ATM adaptation layer 5 (AAL5) Connectionless Network Service (CLNS) Intermediate System-to-Intermediate System (IS-IS) packets when the path from the PXF processor to the route processor (RP) was congested. This could occur when the RP was very busy.

Previously, when the working (odd) slot was OIR'd, it took about .5 seconds for traffic to resume. This symptom was observed on a Cisco 10000 series router with an OC3ATM line card.

Previously, when using a 1oc12atm-1 card in the Cisco 10000 series router, 2 ATM interfaces came up even if the framing configuration was mismatched.

Previously, when you deleted an access control list (ACL) used in many route maps, SuperACL process memory usage increased significantly.

Previously, when redundant Performance Routing Engines (PREs) were configured, the write memory command was in progress on the active PRE, an application on the standby PRE accessed standby NVRAM, and then there was a switchover to the standby PRE, an error message appeared similar to:

Previously, when you attached a policy map to a Multilink PPP (MLPPP) interface or when links were added to an MLPPP interface and then the Cisco 10000 series router reloaded, the packet queue size on an MLPPP bundle could be larger than necessary. This could reduce scalability during the configuration of multiple MLPPP interfaces, because the system could run out of resources to allocate the packet queues. There could be substantial traffic congestion, because traffic that should have been dropped due to queue overflow was not dropped.

Previously, when new links were added to a Multilink PPP (MLPPP) interface that already had a policy map with priority class attached, the priority traffic on the MLPPP interface could exceed the configured bandwidth limits. Links could be added as result of a system reload or bootup, the link going up or down, or the user configuring more links on the bundle.

Previously, when network interfaces were operating at or above OC-3 speeds and a policy map class containing the priority percent percentage command was loaded at or greater than the specified rate, other classes were left with less than their fair share of the bandwidth and their bandwidth ratio was adversely affected.

Previously, upon configuring or modifying the configuration for a frame-relay subinterface with a policy map applied to the interface a user may have received a traceback message: Mar 10 14:41:14.460: %C10K_QOS_GENERAL-3-EREVENT: Error @..//c10k_rp/c10k_qos.c:4024 Traceback= 6010B5E4 60111CD0 608387F0 60838DE8 60840448 60837AE4 6036FAD8 60194738 60381E84 603D8264 603D8250.

Previously, the router reloaded unexpectedly as ATM VCs came up. This problem occurred when ACLs were applied on ATM interfaces, and only rarely then, on images that contain the fix for CSCed72686.

Previously, the queue size may not have been set up correctly for a Cisco 10000 series router. This symptom was observed when an MLP bundle had an output policy attached to an interface and the service policy contained WRED parameters.

Previously, when a multilink bundle was congested, a traffic class with Random Early Detection (RED) failed to achieve its share of the bandwidth due to excessive RED drops. The symptom occurred on multilink bundles under certain RED configurations and heavy traffic load.

Previously, when applied to a multilink PPP (bundle) interface, the service-policy command resulted in the following error message on the standby PRE: CEF switching is required for the set command. In addition, the multilink PPP interface configuration on the standby PRE indicated that there was no service policy on the interface. This symptom occurred only on multilink PPP (bundle) interfaces and only if the policy map referenced in the service-policy command contained a set command.

Previously, WRED may have dropped 99 percent of the packets while there was no congestion on the link. This symptom was observed on a Cisco 10000 series with an OC-12 POS line card under the following conditions: - There was a high context utilization. - There was a high feedback rate. - A high percentage of the packet output on the OC-12 POS line card were priority packets and most packets on the priority queue of the OC-12 POS line card were smaller than 100 bytes.

Previously, a class-default shape command stopped working when the child service-policy command was removed. The symptom occurred only on physical network interfaces with hierarchical policies such as, policy-map p class-default shape 1024 service-policy c An interface with a service policy p shapes its outbound traffic at 1024Kbps. When the child service policy, c, was removed, however, the interface stopped shaping.

Previously, unexpected drops may have occurred before exceeding the configured class bandwidth. This symptom was observed on Cisco 10008 ESR with ESR-24CT1/E1 running IOS 12.0 (27)S1. It was not observed with IOS 12.0(23)S3b.

Previously, a subinterface on a Cisco 10000 series may have dropped packets because of unicast RPF check failures, even though the interface was not configured with uRPF. This symptom was observed on an ATM interface with several subinterfaces when there was at least one subinterface that had uRPF configured. Disabling uRPF on the subinterface left uRPF enabled, even though the CLI indicates it was not enabled. This may also have occurred with Frame Relay subinterfaces.

Previously, after an HA switchover the ATM interfaces were up and appeared to be operational with OSPF adjacencies formed, however, the OSPF peers were mapped to the wrong subinterfaces.

Previously, the router dropped packets when Unicast Reverse Path Forwarding (URPF) was configured on an interface. This problem occurred when the router had 2 paths (outgoing interfaces) to a destination in the FIB table and URPF was enabled on one of the outgoing interfaces.

Previously, the router stopped forwarding traffic for some load balanced recursive prefixes, such as a BGP route with equal cost IGP paths to the BGP next hop. If any Multiprotocol Label Switching (MPLS) Label Distribution Protocol (LDP) adjacency on the router flapped or the router itself flapped, the hardware loadshare pointers for the recursive prefixes could point to old information because Cisco Express Forwarding (CEF) did not send updates to the Parallel Express Forwarding (PXF) processor with new label information.

Previously, on a Cisco 10000 series router running Cisco IOS Release 12.0.25SX5, the snmp-server enable traps alarm command was in the configuration by default as soon as any other SNMP server command was entered. This behavior was not the same as the 7500 with version 12.2.(6f)M1.

Previously, a Cisco router that was running Cisco IOS Release 12.0(25)SX1 may have experienced CEF disabling on the standby PRE. This symptom was observed on a Cisco router that is running Cisco IOS Release 12.0(25)SX1. The symptom may also have occurred in Cisco IOS Release 12.0 S.

Previously, when running on Cisco IOS release 12.0(25)SX1, the Cisco 10000 series router could experience spurious memory access.

Previously, if the standby PRE went down just as the chstm1 driver was trying to sync a linestate message, the active PRE may have crashed.

Previously, the PXF processor may have dropped CLNS/ISIS packets when the PXF-to-RP path was congested. This can have occurred when the RP processor was heavily loaded. It affected CLNS/ISIS packets received from interfaces that were configured with HDLC encapsulation.

Previously, on a Cisco 10000 series router, if the PXF performed PBR on a packet and there were no output features to do (e.g. output ACL, output QoS), then the PXF netflow feature did not see the packet.

Previously, on a Cisco 10000 series router, the PXF processor punted packets that had IP options to the RP for processing. The PXF processor put these packets on the pak_priority queue, but they should have been put on the default queue. This occurred with a Cisco 10000 series router with a PRE-1 routing engine.

Previously, a half-height GE interface stopped forwarding traffic while reporting that the line protocol was up. This problem occurred during a router upgrade or reload with the traffic flowing through the interface.

Previously, a Cisco 10000 series router running Cisco IOS Release 12.0(25)SX6 noticed a large increase of at least 15% in the CPU usage in the "BGP Router" process when upgraded from Cisco IOS 12.0(23)SX5. Under certain condition where there were a very large number of BGP neighbors in a PE-CE scenario, and the during steady state after BGP router convergence, there needed to be a constant churn in the updates with the addition/withdrawal of the routes from the neighbor BGP peers.

Previously, the CPU utilization of the c10k_periodic_stats_coll process increased ten-fold after migrating from a pre-12.0(25)SX release to Cisco IOS 12.0(25)SX. The symptom was seen with a large number of QoS class-based packet queues.

Previously, on a Cisco 10000 series router, if you tried to delete shaping using the no shape xxxx command, it appeared to be disabled on all interfaces (sh policy int serialx/x/x.x). However, the shape value still appeared in the policy map configuration (sh policy-map xyz).

Previously, an ATM line crashed when there was access to the uninitialized memory. The following was displayed on the line card console:

Previously, the show policy-map interface command and its corresponding MIB, CISCO-CBQOS-MIB, reported no Random Drops or fewer than the actual number of drops. The problem occurred only on interfaces at 500 Mbps or faster.

Previously, removing a policy map from a subinterface on a Cisco 10000 series router running 12.0(25)SX7 caused this subinterface to be stuck. Traffic could not cross it. This problem occurred if there was a nested policy map applied to the main/physical interface in addition to the one applied on the subinterface.

Previously, load-balancing did not work over a BGP multipath. Some of the traffic was forwarded correctly while other traffic was forwarded unlabeled into the MPLS core. This problem occurred on a Cisco router that functioned as a PE router when the following conditions were present: the affected route was in a VRF, -one of the paths was learned from a CE router via an eBGP multihop session, the eBGP multihop peer (that is, the CE router) was reachable through the MPLS core, and the BGP session did not involve a label exchange.

Previously, a Cisco 10000 series router suffered PXF crashes if it received malformed Ethernet MPLS packets. This problem occurred with Cisco IOS Release 12.0(26)S2 on a Cisco 10000 series router with an ESR-PRE1.

Previously, the cbQosPolicyMapName object stopped functioning. This problem occurred when an active view included the ciscoPingMib.

Previously, when you changed the Cisco IOS software image on a Cisco 10000 series router, HA functioned differently, causing strange behavior, a standby crash, or both. This problem affected Cisco IOS Release 12.0S, 12.2S, releases that have been derived from 12.2 releases, and releases that have been derived from Cisco IOS Release 12.3.

Previously, a Cisco 10000 series router configured with MLPPP and fragmentation enabled crashed randomly. This problem occurred on Cisco IOS Release 12.0(25)SX6a.

Previously, a multilink bundle queue did not drain immediately when it went down. This problem occurred when a multilink bundle went down while there were still packets in the bundle queue.

Previously, priority queue maximum latency for a 1ch/oc12 port was too high. Priority queue maximum latency was higher than the expected priority queue latency. This problem occurred in Cisco IOS Release 12.0(25)SX6a.

Previously, outbound security ACLs were not applied properly on the Cisco 10000 series router. This problem occurred on all 12.0S images that contain the fix for CSCed72686.

Previously, when you configured redundant Performance Routing Engines (PREs) and saved the configuration first to the standby PRE and then to the active PRE, the configuration might not be saved. Additionally, an error message appeared similar to the following:

Obtaining Documentation

Cisco documentation and additional literature are available on Cisco.com. Cisco also provides several ways to obtain technical assistance and other technical resources. These sections explain how to obtain technical information from Cisco Systems.

Cisco.com

Ordering Documentation

•

Registered Cisco.com users (Cisco direct customers) can order Cisco product documentation from the Ordering tool:

•

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

Documentation Feedback

You can submit comments by using the response card (if present) behind the front cover of your document or by writing to the following address:

Cisco Systems
Attn: Customer Document Ordering
170 West Tasman Drive
San Jose, CA 95134-9883

Obtaining Technical Assistance

For all customers, partners, resellers, and distributors who hold valid Cisco service contracts, Cisco Technical Support provides 24-hour-a-day, award-winning technical assistance. The Cisco Technical Support Website on Cisco.com features extensive online support resources. In addition, Cisco Technical Assistance Center (TAC) engineers provide telephone support. If you do not hold a valid Cisco service contract, contact your reseller.

Cisco Technical Support Website

The Cisco Technical Support Website provides online documents and tools for troubleshooting and resolving technical issues with Cisco products and technologies. The website is available 24 hours a day, 365 days a year at this URL:

Access to all tools on the Cisco Technical Support Website requires a Cisco.com user ID and password. If you have a valid service contract but do not have a user ID or password, you can register at this URL:

Submitting a Service Request

Using the online TAC Service Request Tool is the fastest way to open S3 and S4 service requests. (S3 and S4 service requests are those in which your network is minimally impaired or for which you require product information.) After you describe your situation, the TAC Service Request Tool automatically provides recommended solutions. If your issue is not resolved using the recommended resources, your service request will be assigned to a Cisco TAC engineer. The TAC Service Request Tool is located at this URL:

For S1 or S2 service requests or if you do not have Internet access, contact the Cisco TAC by telephone. (S1 or S2 service requests are those in which your production network is down or severely degraded.) Cisco TAC engineers are assigned immediately to S1 and S2 service requests to help keep your business operations running smoothly.

Asia-Pacific: +61 2 8446 7411 (Australia: 1 800 805 227)
EMEA: +32 2 704 55 55
USA: 1 800 553 2447

Definitions of Service Request Severity

To ensure that all service requests are reported in a standard format, Cisco has established severity definitions.

Severity 1 (S1)—Your network is "down," or there is a critical impact to your business operations. You and Cisco will commit all necessary resources around the clock to resolve the situation.

Severity 2 (S2)—Operation of an existing network is severely degraded, or significant aspects of your business operation are negatively affected by inadequate performance of Cisco products. You and Cisco will commit full-time resources during normal business hours to resolve the situation.

Severity 3 (S3)—Operational performance of your network is impaired, but most business operations remain functional. You and Cisco will commit resources during normal business hours to restore service to satisfactory levels.

Severity 4 (S4)—You require information or assistance with Cisco product capabilities, installation, or configuration. There is little or no effect on your business operations.

Obtaining Additional Publications and Information

Information about Cisco products, technologies, and network solutions is available from various online and printed sources.

•

Cisco Marketplace provides a variety of Cisco books, reference guides, and logo merchandise. Visit Cisco Marketplace, the company store, at this URL:

•

The Cisco Product Catalog describes the networking products offered by Cisco Systems, as well as ordering and customer support services. Access the Cisco Product Catalog at this URL:

•

Cisco Press publishes a wide range of general networking, training and certification titles. Both new and experienced users will benefit from these publications. For current Cisco Press titles and other information, go to Cisco Press at this URL:

•

Packet magazine is the Cisco Systems technical user magazine for maximizing Internet and networking investments. Each quarter, Packet delivers coverage of the latest industry trends, technology breakthroughs, and Cisco products and solutions, as well as network deployment and troubleshooting tips, configuration examples, customer case studies, certification and training information, and links to scores of in-depth online resources. You can access Packet magazine at this URL:

•

iQ Magazine is the quarterly publication from Cisco Systems designed to help growing companies learn how they can use technology to increase revenue, streamline their business, and expand services. The publication identifies the challenges facing these companies and the technologies to help solve them, using real-world case studies and business strategies to help readers make sound technology investment decisions. You can access iQ Magazine at this URL:

•

Internet Protocol Journal is a quarterly journal published by Cisco Systems for engineering professionals involved in designing, developing, and operating public and private internets and intranets. You can access the Internet Protocol Journal at this URL:

•

World-class networking training is available from Cisco. You can view current offerings at this URL:

Table Of Contents

Release Notes for the Cisco 10000 Series Router for Cisco IOS Release 12.0(25)SX9

Contents