
396
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
Workaround: Create a dummy Fast Ethernet subinterface and force it to allocate the tx-port being
back-pressured.
Further Problem Description: Removing the policy and re-applying it or performing a shut/no shut
solves the issue temporally, but the issue will move to another subinterface in the same main
interface.
• CSCtb49864
Symptoms: An HP ingress policy is applied on the Gigabit Ethernet main interface (E5). After an
RP switchover, the counter for the “show policy-map int gig 0/0/0” command stays at 0 even though
the police function appears to be working okay. The policer also disappears from the “show
policy-map int” command output.
Conditions: RP switchover.
Workaround:
1. Perform a shut/no shut on the interface.
2. Delete/re-apply the service policy on the interface.
• CSCtb51864
Symptoms: An IPv6 ACL is not working on the ingress of an E3 engine.
Conditions: Apply the IPv6 ACL on the ingress of the E3 engine, remove the ACL, and then reapply
the same ACL on the same interface.
Workaround: Reload the linecard.
• CSCtb52229
Symptoms: When a class map is added to an existing service policy (with a huge number of class
maps), high CPU utilization occurs and CPU hog messages are seen, which causes OSPF flapping,
and, in turn, a network outage.
Conditions: This symptom is observed when a class map is bonded/unbonded from a service policy
that has a huge number of class maps.
Workaround: There is no workaround.
• CSCtc36576
Symptoms: In a FR-Ethernet IP interworking scenario, a Cisco 12000 series PE (with an E5 linecard
being used as CE facing) corrupts CE-to-CE packets that are less than 58 bytes.
Conditions: One Cisco 12000 series is running Cisco IOS Release 12.0(32) SY8, 12.0(32)SY9, or
12.0(32)SY10. The linecard that is facing the CE must be E5.
Workaround: There is no workaround.
• CSCtc55200
Symptoms: An E5 linecard crashes while the “show ip hardware-cef x.x.x.x detail” command is
executed during CEF troubleshooting.
Conditions: This symptom is observed under the following conditions:
–
Core-facing interfaces using Eng3 with two Port-Channel and load-balance.
–
Customer-facing interfaces using Eng5 with exhausted FSRAM memory because of a high
number of hosts or load-balance routes from Eng3.
When FSRAM memory becomes exhausted, if you try to add one more host on the port-channel, the
following error message will appear:
Comentarios a estos manuales