
730
Caveats for Cisco IOS Release 12.2(33)SRD through 12.2(33)SRD8
OL-10394-05 Rev. R0
Workaround: Disable the CEF consistency checkers by using the following commands:
no cef table consistency-check ipv4 no cef table consistency-check ipv6
• CSCsl72789
Symptoms: SW_INIT_TIMEOUT message for ES20 line cards, line card may or may not recover.
Conditions: Generally this error is seen with large routing tables, large configurations with many
subinterfaces, or in the case of hardware failure.
Workaround: Depending on the source of the error, the workaround may be to reload the line card
or reload the chassis. Some problems may have no workaround.
Further Problem Description: This fix will effectively remove the possibility of a
SW_INIT_TIMEOUT.
• CSCsl72826
Symptoms: Router crashes at ipfib_policy_forward.
Conditions: The issue seems to occur when a script is removing route map configurations and
reconfiguring them at very short intervals. This occurred during internal testing and is not likely to
occur in a production environment.
Workaround: There is no workaround.
• CSCsl72831
Symptoms: Cisco 7600 displays the following error:
CWAN_CHOC_DSX-3-VC_CONFIG_ERR
Conditions: Occurred while configuring channelized OC3 SPA on c7600-SIP-200.
Workaround: There is no workaround.
• CSCsl74120
Symptoms: Classification is broken after online insertion and removal (OIR) in Optical Services
Module (OSM), as the OSM queues are not created.
Conditions: Occurs after an online insertion and removal (OIR) event.
Workaround: Remove and attach the policy again on the interface to solve the issue.
• CSCsl74441
Symptoms: "%INTERFACE_API-3-NODESTROYSUBBLOCK: The SWIDB subblock named SW
FIB PENDING EVENT was not removed" error messages are observed on the router. This symptom
does not affect traffic but may be the cause of a memory leak.
Conditions: This symptom is observed when PPPoE/L2TP sessions are established on Cisco 7300
routers. CSCsk38385 addresses this issue on Cisco 7200 routers.
Workaround: There is no workaround.
• CSCsl74712
Symptoms: When an existing Virtual Router Redundancy Protocol (VRRP) tracking entry is
re-entered into the configuration of the active RP, the standby RP automatically resets.
Conditions: This problem only occurs after the following sequence of configuration events:
–
VRRP is configured to track an existing tracking object.
–
The existing tracking object is removed from the global tracking configuration.
–
The standby is initiated and establishes the full STANDBY state.
Comentarios a estos manuales