
764
Caveats for Cisco IOS Release 12.2(33)SRD through 12.2(33)SRD8
OL-10394-05 Rev. R0
Conditions: This symptom is seen on a VPLS setup with IGMP snooping enabled on the vlan
interface hosting the VFI VCs. If a very quick shut followed by a no-shut is performed, this
condition occurs.
Workaround: A shut followed by a no- shut on the VLAN interface is required to resume traffic.
Further Problem Description: IGMP snooping is broken with no joints received.
• CSCsm61105
Symptoms: The router can crash due to bus error. The crash is seen after repeatedly after removing
virtual-template interfaces under ATM.
Conditions: The crash is seen under the following conditions:
1) Bring up nearly 3000 PPPoE and PPPoEoA sessions. 2) Configure no interface virtual-template
number under ATM interfaces
Repeating Step 2 continuously will cause a crash.
Workaround: There is no workaround.
• CSCsm61571
Symptoms: When the optical RX level changes such that is out of the supported threshold or a
mismatched combination of XFPs used at ends (eg: ZR to LR, SR to LR etc), then the line card CPU
utilization becomes very high at the interrupt level. This greatly contributes to exhaustion of line
card CPU resources and results in failure to process heartbeat keeaplives. As a result, line card is
eventually reset by the SP to attempt recovery. Cause of the CPU being so frequently interrupted are
the continuous interface state transitions which are triggered by the line card.
Passing CLIs to the line card fail:
7600#remote command module 2 sh proc cpu sort No response from remote host 7600#
SP fails to receive heartbeat checks from the ES20 LC and eventually crashes
%CPU_MONITOR-SP-6-NOT_HEARD: CPU_MONITOR messages have not been heard for 30 seconds
[2/0] %CPU_MONITOR-SP-6-NOT_HEARD: CPU_MONITOR messages have not been heard for 60
seconds [2/0] %CPU_MONITOR-SP-6-NOT_HEARD: CPU_MONITOR messages have not been heard
for 90 seconds [2/0] %CPU_MONITOR-SP-6-NOT_HEARD: CPU_MONITOR messages have not been
heard for 120 seconds [2/0] %CPU_MONITOR-SP-6-NOT_HEARD: CPU_MONITOR messages have not
been heard for 150 seconds [2/0] %OIR-3-CRASH: The module in slot 2 has crashed
When unplugging the fibers, LC becomes responsive, but shows high CPU in interrupt:
7600#remote command module 2 sh proc cpu sort | e 0.00% 0.00% 0.00%
CPU utilization for five seconds: 99%/96%; one minute: 36%; five minutes: 23% PID
Runtime(ms) Invoked uSecs 5Sec 1Min 5Min TTY Process 124 59128 542 109092 2.19% 2.17%
2.30% 0 Vlan Statistics 134 221872 1057 209907 0.42% 8.74% 10.38% 0 CFIB LC STATS Ta
127 24072 3340 7207 0.18% 0.20% 0.17% 0 BW Stats Poll 213 1628 177 9197 0.12% 0.07%
0.05% 0 sip10g Stats Bac 173 7208 634 11369 0.12% 0.01% 0.00% 0 TCAM Manager pro 193
1240 177 7005 0.12% 0.05% 0.05% 0 MFI LFD Stats Pr 172 2488 373 6670 0.12% 0.08% 0.09%
0 QoS SP Process 104 440 87 5057 0.12% 0.04% 0.01% 0 xcvr RPC process
Conditions: Occurs on a Cisco 7600 router with a XFP-10GZR-OC192 housed in a ES20, where the
optical fiber has its RX level out of the specified range for the given XFP being used.
Workaround: Verify the optical properties of the fiber using the sh hw-module subslot X/Y
transceiver Z stat command. If out of range, replace with optical fibers for which the optical
transmission properties are within the specified range for the given XFP being used.
• CSCsm61726
Symptoms: Adaptive clock stays in HOLDOVER state and does not get to an ACQUIRED state.
Komentáře k této Příručce