
386
Cross-Platform Release Notes for Cisco IOS Release 12.0S
OL-1617-14 Rev. Q0
Caveats
Resolved Caveats—Cisco IOS Release 12.0(33)S6
Conditions: It is necessary that “mpls traffic-eng tunnel automesh” is running in the OSPF area of
the router, although automesh need not be configured on the affected router.
Workaround: There is no workaround.
• CSCsy74390
Symptoms: ISIS adjacency is not established with an E4 SRP linecard.
Conditions: This symptom is observed when ISIS is configured between SRP interfaces with at least
one end having an E4 SRP linecard.
Workaround: There is no workaround.
• CSCsy82104
Symptoms: I/O memory leaks after several days. The output of the E1 serial interface may be
blocked as well.
Conditions: The symptoms are observed on a Cisco 7200 series router that is running Cisco IOS
Release 12.0(33)S and when an E1 interface serial flaps. The QoS outgoing service-policy needs to
be provisioned on this serial interface.
Workaround: Remove the outgoing QoS service-policy from the flapped/blocked serial interface.
• CSCsy92142
Symptoms: The serial interface on a channelized OC48 linecard stays in the UP/DOWN state after
encountering Layer 1 alarms (PRID or PAIS). The interface continues to be in the UP/DOWN state
even after the Layer 1 alarms are cleared.
The interface is configured for PPP encapsulation, and path level delay triggers are enabled on this
interface. The link shows UP, but the PPP negotiation will be stuck in Echo Request Sent.
Conditions: This symptom is observed with a 12.0(32)S11o-based image for channelized DS3
Engine 3 linecards with alarm delay triggers configured. The problem will be seen only with
momentary path level alarms.
Workaround:
1. Perform a shut/no shut on the serial interface that is in the UP/DOWN state. However, this needs
manual intervention every time.
2. Remove the alarm-delay triggers path 2500 command from the serial interface configuration.
However, the side effect of this would cause the serial interface to flap.
• CSCsy94776
Symptoms: A Cisco 12000 series Internet router may have missing lfib entries on linecards.
Conditions: This symptom is observed in Cisco IOS Release 12.0(32)s11o.
Workaround: Reload the linecard.
• CSCsy96287
Symptoms: A customer experienced a single T1 flapping on controller 0/3/0. It would take between
2,500 and 3,000 path code violations and then drop and come back. It would do this about once every
15 minutes. Problems with our phones losing connectivity to a central call manager when a WAN
circuit experiences a problem.
We use Multilink PPP to bundle three T1s for a 4.5-Mb circuit. If any one of the three T1s
experiences even a minor issue, phones are resetting. However, we never lose Layer 3 connectivity.
The edge router maintains its BGP peering across the Multilink PPP bundle, and none of our
management applications ever sees a loss in connectivity.
Comentarios a estos manuales