
541
Caveats for Cisco IOS Release 12.2(33)SRD through 12.2(33)SRD8
OL-10394-05 Rev. R0
Conditions: A Cisco 7600 running Cisco IOS Release 12.2(33)SRB2 and 12.2(33)SRB3 with
Multilink interface configured for CBWFQ QOS policy will suspend policy and display error
message similar to the above if service-policy is applied to Multilink interface at time of route
loading.
Workaround: Load router with no service-policies applied and apply them after router is up.
• CSCsx03301
Symptoms: Crash in TCP.
Conditions: Happens when clearing a BGP neighbor. The trigger is uncertain and hard to reproduce.
Workaround: There is no workaround.
• CSCsx07159
Symptoms: A policy-map is applied to an interface on ESM20G card and has a random-detect
aggregate action configured in a class. If another class is added to the policy-map which has match
statement as "match cos <cos-value>", this class gets added. Now if random-detect aggregate is
removed from the previous class, an error message is dumped on screen :
’match cos’ combined with other match statements at the same class level is not supported for this
interface.
If random-detect action is added to this class, router crashes.
Conditions: Occurs with the following configuration:
policy-map PMAP_UPLINKS
class CMAP-RT-COS (match cos <vaue>)
class CMAP-BC-EXP
no random-detect aggregate
random-detect -----> (CRASH)
Workaround: Do not add a class-map with "match cos" filter to a policy-map which conflicts with
other class-map filters.
• CSCsx07537
Symptoms: Delay in bootup time of the line cards occurs during reload with diags enabled. Issue not
seen when diags are disabled.
Conditions: There is no specific configuration or traffic combination that will trigger this issue.
Issue seen with or without any Ethernet Virtual Circuit (EVC) configs or traffic conditions.
Workaround: Disable bootup diags or power down the 6748-GE-TX card
• CSCsx08861
Symptoms: ATOM VC status is seen as down in standby RP and traffic loss is seen after switchover
for 44 seconds.
Conditions:
1. Bring 6RU up (SSO) with 1 AToM VC, 1 AToM VP (Initial VC state: active:UP;
standby:HOTSTANDBY)
2. Delete the AToM VC sub-int (’no int a2/2/0.122’) and delete the AToM VP sub-int (’no int
a2/2/0.1001’)
3. Re-configure back the same AToM VC and VP configuration (VC state: Active:UP;
Standby:DOWN for AToM VC)
Comentarios a estos manuales