
466
Cross-Platform Release Notes for Cisco IOS Release 12.0S
OL-1617-14 Rev. Q0
Caveats
Resolved Caveats—Cisco IOS Release 12.0(33)S1
Further Problem Description: This issue is not seen with an E3/E5 combination or an E2/E6
combination.
• CSCso30471
Symptoms: Engine 5 SIP-600 crashes and tracebacks seen for Flexible NetFlow (FNF)
configuration.
Conditions: Line card crash is hard to reproduce, and it is seen when show flow monitor is used.
Tracebacks are easily re-producible while unconfiguring FNF output mode.
Workaround: There is no workaround.
• CSCso31508
Symptoms: CEF and hardware CEF for global default route are inconsistent. This may cause the
default traffic to be sent through the wrong interface.
Conditions: This issue occurs under the following conditions:
1. Global default should point toward the core. 2. VRF default should be learned from the remote PE.
Workaround: Enter the following command:
clear ip route 0.0.0.0 0.0.0.0
• CSCso33290
Symptoms: L2VPN traffic on an MFR interface is unable to pass through FR/IETF encapsulation
MPLS trunk. Furthermore, if this MFR interface is deleted and re-added, the following error
messages are received.
SLOT 4:Mar 20 11:51:05.459 UTC: %SPA_CHOC_DSX-3-ERROR: Serial4/0/0/1:0: response
parsing failed for DLCI (601) provisioning SLOT 4:Mar 20 11:51:05.471 UTC:
%SPA_CHOC_DSX-3-ERROR: Serial4/0/0/1:0: response parsing failed for DLCI (602)
provisioning
Conditions: This symptom is observed after an MFR interface is deleted and re-added.
Workaround: There is no workaround.
• CSCso46965
Symptoms: Ping fails
Conditions: Occurs when 2x1GE V2 shared port adapter (SPA) is in BN jacket.
Workaround: There is no workaround.
• CSCso47485
Symptoms: The E4+ line card crashes continuously with the following output:
SLOT 1:Jan 19 02:06:09.559 UTC: %TX192-3-CPUIF: Error=0x40
rd 0x15 base 0x12 hdr 0x14 last 0x14 wr 0x14 insert 0x0 back 0x1 len 0x2474 cnt 0x0
Conditions: There is no exact trigger. But this symptom is observed when there are corrupt packets
being sent from the ingress card under unknown circumstances.
Workaround: There is no workaround.
• CSCso53048
Symptoms: A router acting as an OSPF ABR for an NSSA area, when announcing a default route
into the NSSA area, sets the LSA forwarding address to one of its interfaces instead of to 0.0.0.0.
When there is more than one interface from that router into the NSSA area (load balancing), only
Kommentare zu diesen Handbüchern