Specifications

1404
Cross-Platform Release Notes for Cisco IOS Release 12.0S
OL-1617-14 Rev. Q0
Resolved Caveats—Cisco IOS Release 12.0(27)S
– The remote PE router can ping the local CE router with ToS equal to 0xe0.
– A ping with the route record option does not work in either direction.
– A ping with the trace route option does work.
Conditions: These symptoms are observed on the LSC of a Cisco MGX Route Processor Module
(MGX-PRM-PR-512) that is running Cisco IOS Release 12.2(15) T4a.
Workaround: From the node of the local LSC that is observing the symptoms, enter the clear ip
route network EXEC command.
• CSCec65940
Symptoms: Packets that go to destinations learned by Border Gateway Protocol (BGP) may be
dropped for up to 60 seconds or so as soon as the routes are installed. The packet loss occurs only
for the first minute or so after the BGP session comes up. After that time period, packet forwarding
functions correctly.
Conditions: This symptom is observed when all of the following conditions occur:
– The BGP session involves a Multiprotocol Label Switching (MPLS) label exchange (external
BGP [eBGP] single-hop sessions are most likely to be affected).
– The BGP peer is reachable via a link with PPP encapsulation.
– The router in question is running Cisco IOS Release 12.0(22)S or a later release.
Workaround: Since the symptom is specific to PPP encapsulation, one way to avoid the symptom is
to use another form of encapsulation (for example, High-Level Data Link Control [HDLC]).
• CSCec66970
Symptoms: A Section Data Communications Channel (SDCC) interface on a channelized IP
Services Engine (ISE) OC48 line card no longer functions.
Conditions: This symptom is observed in Cisco IOS software releases that are after
Release 12.0(26)S.
Workaround: There is no workaround.
• CSCec67272
Symptoms: When you reload a Multiprotocol Label Switching (MPLS) provider edge (PE) router
that has 20 PA-MC-2T3+ controllers and 780 channelized interfaces, the first PA-MC-2T3+
controller may have many channelized interfaces in the down/down state.
Conditions: This symptom is observed on an MPLS PE router that has the channelized interfaces
that are in the down/down state directly connected to a customer edge (CE) router. If the connection
is a T1 interface, then the interfaces on the CE router are in an up/down state. If the connection is
sub-T1 (fractional T1), then the interfaces on the CE router are in an up/up state.
Workaround: Reload only the CE router and all the interfaces will go to the up/up state on both the
CE router and the PE router.
• CSCec67980
Symptoms: The standby Route Processor may reload shortly after if boots up if the snmp-server
packetsize byte-count global configuration command is included in the configuration.
Conditions: This symptom is observed on a standby RP if the packet size of the Simple Network
Management Protocol (SNMP) server is included in the configuration of the router.
Workaround: Do not specify the packet size of the SNMP server in the configuration of the router.