
615
Cross-Platform Release Notes for Cisco IOS Release 12.0S
OL-1617-14 Rev. Q0
Caveats
Resolved Caveats—Cisco IOS Release 12.0(32)S4
access-list 60 permit 10.0.1.5
access-list 60 permit 10.0.2.6
access-list 60 permit 10.0.3.7
access-list 60 permit 10.0.5.1
access-list 60 permit 10.0.6.2
access-list 60 permit 10.0.8.12
• CSCse12983
Symptoms: If following steps are performed on 2xCT3 SPA and 10x1GE SPA located in E5
12000-SIP-601
–
Enter the hw-module slot shelf-id/slot-number shutdown command on 2xCT3 SPA.
–
Enter the no hw-module slot shelf-id/slot-number shutdown command on 2xCT3 SPA.
–
Enter the hw-module slot shelf-id/slot-number shutdown command on 10x1GE SPA. Before
CT3 SPA comes up, the CT3 SPA may get in an out-of-service state.
Conditions: This symptom is observed on a Cisco 12000 series that runs Cisco IOS interim
Release 12.0(32.1)S9
Workaround: Performing the no hw-module slot shelf-id/slot-number shutdown command on
10x1GE SPA, or the microcode reload command on the SIP-601 may fix the problem.
• CSCse23872
Symptoms: A Cisco 12000 Engine 3 card is used as an IP ingress to classify traffic to different
classes using a set of IP standard and extended ACLs. After reaching a stable state, when the ACLs
take a substantial part of the TCAM, adding a single line to an ACL used in the class-map may result
in the TCAM Mngr merge process on the line card to take 99% CPU for a long time (over 60
seconds), and then crash the card with the following errors:
00:14:59: %QM-4-TCAM_ENTRY: Hardware TCAM entry capacity exceeded
00:14:59: %QM-4-SW_SWITCH: Interface GigabitEthernet2/2 routed traffic will be
software switched in ingress direction(s)
SLOT 2:00:14:06: %EE48-5-TM_PROC: TCAM handling fail for features config for
interface: 13
-Traceback= 40030CAC 404B7604 404B76B4 404BA7D4 404BC61C 404BC7C4 404BC8D8
404C7C00 404D197C 404D3684 404C7BB4 404C8800 404C8BA4
00:15:00: %QM-2-TCAM_ERROR: TCAM pgm error(36): Invalid Parameters
Conditions: This issue is observed with multiple interfaces on the same line card using service
policies with long (over 1000 entries) ACLs.
Workaround: When restarting the line card with the policy-map configured, it boots correctly. Also,
removing the QoS policy from all the interfaces, waiting for the TCAM to clear up, then changing
the ACL and reapplying the QoS policy on the interface is a valid workaround.
• CSCse29480
Symptoms: Locally originated traffic is not prioritized correctly in specific MQC configuration for
MPLS and Engine 4 plus used as the egress LC. Control plane protocols might flap as a result of
oversubscription of the default class.
Conditions: This occurs if the policy-map includes a priority class, e.g. to carry voice traffic, and
that there is no class mapping precedence 6 or 7 (i.e. the policy map defines mappings only for EXP
6 and 7).
Kommentare zu diesen Handbüchern