
843
Cross-Platform Release Notes for Cisco IOS Release 12.0S
OL-1617-14 Rev. Q0
Caveats
Resolved Caveats—Cisco IOS Release 12.0(31)S
• CSCef85916
Symptoms: In a scaled L2VPN configuration, CPUHOG-related tracebacks may be generated on a
CE router.
Conditions: This symptom is observed on a Cisco 12000 series that runs the c12kprp-p-mz image of
Cisco IOS Release 12.0(30)S and that functions as a CE router.
Workaround: There is no workaround.
• CSCef87309
Symptoms: A basic back-to-back ping fails on an Engine 4+ line card.
Conditions: This symptom is observed on a Cisco 12000 series that runs the c12kprp-p-mz image of
a Cisco IOS interim release for Release 12.0(30)S. However, this caveat is resolved in
Release 12.0(30)S.
Workaround: There is no workaround.
• CSCef89192
Symptoms: A self-ping may not function on a Cisco 12000 series and traffic may stop.
Conditions: This symptom is observed on a Cisco 12000 series after you remove and reconfigure a
port-channel subinterface.
Workaround: Remove the member interfaces from the channel group and add them again. Doing so
enables traffic to resume.
• CSCef89562
Symptoms: An Engine 4+ EPA-GE/FE-BBRD line card reports “%TX192-3-PAM_MODULE” and
“%TX192-3-PAM_PIM” errors, and the interfaces continue to flap with the following error
message:
%GRPGE-6-INVALID_WORD: Interface GigabitEthernet15/1/0: Detected RX Invalid Word
When there is heavy traffic, the line card may crash without generating any crashinfo.
Conditions: These symptoms are observed on a Cisco 12000 series that runs Cisco IOS
Release 12.0(26)S3 or Release 12.0(27)S3.
Workaround: There is no workaround.
• CSCef89925
Symptoms: IPv4 multicast traffic may be punted to the CPU of the RP, causing a throughput of only
700 pps.
Conditions: This symptom is observed on a Cisco 12000 series that runs the gsr-p-mz image of Cisco
IOS Release 12.0(30)S.
Workaround: There is no workaround.
• CSCef90783
Symptoms: The output counter on the interface of a PE router that faces a P router generates almost
twice the value that is should provide.
Conditions: This symptom is observed in the following MPLS topology in which Cisco 12000 series
routers are connected via interfaces of Engine 3 line cards:
A CE router (CE1) connects to a PE router (PE1) that connects, in turn, to a P router. This P router
connects to another PE router (PE2) that, in turn, connects to another CE (CE2) router.
The symptom occurs when a VRF ping is generated from PE1 to the VRF interface of PE2, that is,
the interface that is connected to CE2. The output counter on PE2 generates incorrect values.
Comentarios a estos manuales