
476
Caveats for Cisco IOS Release 12.2(33)SRD through 12.2(33)SRD8
OL-10394-05 Rev. R0
The running Cisco IOS image uses IPSERVICE, which is unable to configure no mls flow ipv6. But
this command can be detected as mismatch command, and it fails to start with SSO mode.
Conditions: This issue can occur after conducting “write memory” and reloading the part.
This issue is confirmed by using Cisco IOS Release 12.2(33)SRC4. A similar issue has been seen
on Cisco IOS Release 12.2(33)SRC5 and Cisco IOS Release 12.2(33)SRD4, but not on Cisco IOS
Release 12.2(33)SRE.
Workaround: Conduct reload when startup-config is saved in NVRAM.
• CSCtf96659
Symptoms: Broadcast/multicast storm across L2 switchport trunked etherchannel on ES+ links.
Conditions: The symptom is observed with an L2 trunked port-channel interface with ES+ member
links. There is “ip pim” configured on VLAN SVI where that VLAN is allowed across the trunked
port-channel.
Workaround: Use a single link configured as switchport trunk.
• CSCtg01296
Symptoms: Enhanced FlexWAN with scaled DLFI setup resets on doing a shut/no shut on the ATM
interface.
Conditions: The symptom is observed with the following steps:
1. 256 dLFIoATM interface on a single PA. 2. Traffic of around 44 Mbps Imix types is flowing
through the all bundles. This is equally divided between all the bundles. 3. Do a continuous shut/no
shut. 4. Enhanced FlexWAN might reset. It does not generate a crashinfo.
Workaround: There is no workaround.
• CSCtg11217
Symptoms: Standby crashes when doing an SSO.
Conditions: The symptom is observed when one of the slots in the chassis has a fabric connection
issue.
Workaround: Power down the module in the slot that is having the fabric connection issue.
• CSCtg11421
Symptoms: The following issues are observed:
–
All egress traffic by SIP-400 is dropped.
–
Consecutive BusConnectivityTest failure for SIP-400.
–
When SIP-400 is hosting intelligent SPAs such as SPA-8XCHT1/E1, then this SPA gets into
OutSrvc state.
Conditions: The symptom is observed with a SIP-400 with egress LLQ shaping and with a high
volume of traffic to low speed stream.
Workaround 1: SIP-400 reload using the hw-module module X reset command (where X is the
module/SIP-400 number).
Workaround 2: Remove LLQ configuration.
Workaround 3: SIP-400 microcode reload (where X is the module/SIP-400 number):
attach X
enable
microcode reload np
Komentáře k této Příručce