Specifications

1321
Cross-Platform Release Notes for Cisco IOS Release 12.0S
OL-1617-14 Rev. Q0
Resolved Caveats—Cisco IOS Release 12.0(27)S3
FAIL REASON = retry queue flush
%LCINFO-3-CRASH: Line card in slot 4 crashed
Conditions: The symptom is seen when the ciscoOpticalMonitoringMIB is polled on a router
running Cisco IOS Release 12.0(27)S1. The card that crashes does not have to be the card that is
being polled. For example, an OC192E/POS-VSR in slot 0 may be polled with
1.3.6.1.4.1.9.10.83.1.1.1.1.8.2 and the OC192E/POS-IR-SC in slot 4 may crash.
Workaround: Stop the crashes by configuring an SNMP view that prevents the
ciscoOpticalMonitoringMIB from being polled.
• CSCef29224
Symptoms: When removing or modifying a service-policy from a MFR or MLPPP bundle CFI, there
is an RP crash.
Conditions: This symptom is observed on a Cisco router in which a police-policy is applied on the
bundle CFI over an ISE 1xOC12 Channelized to DS1 Line Card.
Workaround: There is no workaround.
• CSCef31934
Symptoms: In a scaled configuration with hundreds of eBGP peers with very low BGP timers,
issuing clear ip bgp * may increase HW forwarding memory utilization.
Conditions: This problem is seen with 500 eBGP sessions with BGP keepalive timer of 3 seconds
and hold timer of 9 seconds. The router has 200K MPLS VPN routes. This problem is not seen if
the BGP timers are set to the default value.
Workaround: There is no workaround.
• CSCef37186
Symptoms: The Simple Network Management Protocol (SNMP) agent may use 99 percent of the
CPU bandwidth of a Route Processor (RP) for an arbitrarily long time, possibly generating
CPUHOG errors and causing a watchdog crash. Other processes on the router may fail because these
processes do not receive the CPU bandwidth that they require. Consequently, the following
difficulties may occur:
– Routes may time out.
– Tunnels may go down.
– Accessing the router via a Telnet connection to a network port may become impossible.
– The command-line interface (CLI) via the console line may become quite slow to respond.
The output of the show snmp summary EXEC command may indicate that the number of requests
is “N” while the number of replies that were sent is “N-1.” The output of the show processes cpu |
include SN EXEC command may indicate that the SNMP process uses 99 percent of the CPU
bandwidth of the RP.
Conditions: These symptoms are observed on a Cisco 7300 series when the MPLS-LSR-MIB MIB
is enabled, when you query the object mplsXCIndexNext, and when there are more than 1,000
Multiprotocol Label Switching (MPLS) labels active. However, the symptoms are
platform-independent.
Workaround: Perform the following steps:
1. Shut down interfaces to bring the total count of active MPLS labels down to far below 1,000.
2. Disable the MPLS-LSR-MIB MIB by entering the following sequence of commands:
snmp-server view nolsrmib mplsLsrMIB exclude
snmp-server view nolsrmib iso include