Specifications

1192
Cross-Platform Release Notes for Cisco IOS Release 12.0S
OL-1617-14 Rev. Q0
Resolved Caveats—Cisco IOS Release 12.0(28)S1
Wide-Area Networking
• CSCdx84284
Symptoms: A router may not recognize some inbound Multiprotocol Label Switching
(MPLS)-tagged packets that are sent via Frame Relay. Because the router cannot recognize the
inbound MPLS-tagged packets, MPLS cannot switch those packets to the outgoing interface. The
MPLS-tagged packets are dropped by the router, and the router does not increment the input-packet
counter in the output of the show frame pvc output EXEC command.
Conditions: This symptom is observed on a Cisco router that has Cisco Express Forwarding (CEF)
enabled and that is running Cisco IOS Release 12.2(7b). The symptom may also occur in other
releases.
Workaround: Enable the debug mpls packets EXEC command.
• CSCee62222
Symptoms: The frame-relay interface-dlci command is removed unexpectedly from a
point-to-point subinterface.
Conditions: This symptom is observed when you enter the clear frame-relay-inarp command.
Workaround: Do not use the clear frame-relay-inarp command.
• CSCee75882
Symptoms: A GEIP+ that is installed in VIP may crash.
Conditions: This symptom is observed on a Cisco 7500 series when the routing protocol adjacency
of a neighbor is reset because an interface flaps.
Workaround: Stabilize the routing protocol adjacency of the neighbor.
• CSCee85213
Symptoms: A spurious memory access may occur and the following error message is generated:
%ALIGN-3-SPURIOUS: Spurious memory access made at 0x60C19208 reading 0x1C
Under high-traffic conditions, the console freezes because of an alignment error.
Conditions: These symptoms are observed on a Cisco 7200 series when a FR-FR local switched
connection is configured by entering the connect command, when a queuing service policy is
enabled on the main interface, and when the DLCI on the outgoing interface does not exist on the
incoming interface.
Workaround: Enter the frame-relay route command instead of the connect command. If the
connect command is needed for access to features like policing, the errors do stop if the DLCI on
the outgoing interface also exists on the incoming interface that has the service policy. The DLCI
can be created under a subinterface that is shut down and that has no IP address configured if it is
not used to handle traffic.
• CSCin74785
Symptoms: A VIP crashes with the following error message:
VIP-3-SYSTEM_EXCEPTION: VIP System Exception occurred sig=10, code=0x8
Conditions: This symptom is observed when you remove a Frame Relay local switching connection
from an MFR interface while traffic is running.
Workaround: Shut down the connection or interface and ensure incoming traffic has stopped before
you remove the connection.