
724
Caveats for Cisco IOS Release 12.2(33)SRD through 12.2(33)SRD8
OL-10394-05 Rev. R0
Symptoms: When the sum of EIRs of all BW queues under an ESM20 linecard exceeds 549Gbps,
the following message may be produced: "EXCEEDEXCESSQRATE".
Conditions: The symptom is observed in an environment which has a large configuration with 1000
EVCs with WRED-configured policy maps under a PC interface. When the WRED is removed from
a class which has a shape rate, a number of exceed excess error messages are seen. When the
shutdown command is executed followed by the no shutdown command on the PC interface, most
of the queues go to pending state with the exceed excess error message flooding the screen.
Workaround: Changing either the shape rate or adding the WRED back to the class-map will resolve
the problem. Reloading the linecard will also recover this problem.
• CSCsl62076
Symptoms: Configuring IPv6 RIP on a router may cause the router to crash.
Conditions: The symptom is observed on a Cisco 10000 series router when configuring IPv6 RIP.
Workaround: There is no workaround.
• CSCsl62341
Symptoms: The configuration command ip summary-address rip is not applied by radius
configuration as part of the lcp:interface-configuration.
Conditions: This symptom is observed only when the lcp:interface- configuration is used in
combination with other AVPairs that perform an interface-specific configuration. For example, the
last four AVPairs shown below use a mix of lcp:interface-configuration and interface-specific
AVPairs: xxxxx@xxxx2001 Password = "xxxx" Service-Type = Framed-User, Framed-Protocol =
PPP, Framed-IP-Address = 10.17.1.1, Framed-Routing = listen, av-pair = "ip:description=sub-VAI
ppp1", av-pair = "ip:vrf-id=X2001", av-pair = "ip-unnumbered=Loopback2001", av-pair =
"lcp:interface-config=ip summary-address rip 10.17.1.0 255.255.255.0"
Workaround: If you require a summarized address to be advertised via RIP to CPEs, ensure that the
lcp:interface-configuration command/attribute is used for all interface specific configurations, as
this issue occurs when the interface specific commands/attributes are mixed between the AVPairs
and the lcp:interface-configuration commands. The interface profile should be applied before
applying any IP configuration profiles.
• CSCsl62344
Symptoms: If a contact phone number is configured to be 12 digits long, the configuration will fail.
If the configuration is already in the running- configuration, the call-home configuration will lost
after reload.
Conditions: The symptom is observed when the call-home contact phone number is configured to
be 12 digits long.
Workaround: Add a white space in the contact phone number to make it at least 13 digits long.
• CSCsl62626
Symptoms: A Cisco 7304 router may experience high CPU utilization (90-99%) when a large
number (such as 2000) FR-L2TPv3 circuits are configured on a POS interface facing the CE router.
Conditions: A Cisco 7304 router that is configured with an NSE-100 and that is running Cisco IOS
Release 12.2(33)SB.
Workaround: No other workaround than to reduce the scale of the circuits configured.
Further Problem Description: CPU utilization is proportional to number of FR- L2TPv3 circuits. So
the issue occurs for any number of FR-L2TPv3 circuits, but rises gradually as the number of circuits
increase.
• CSCsl62963
Comentarios a estos manuales