Cisco Cisco IOS Software Release 12.2(33)SRE
169
Caveats for Cisco IOS Release 12.2(33)SRE through 12.2(33)SRE13
OL-10394-05 Rev. S1
Conditions: This symptom is observed when static route statements present on the active and is
missing on the stand-by. Perform these steps to recreate the issue:
missing on the stand-by. Perform these steps to recreate the issue:
1.
Configure a static route with an interface dependency (eg: ip static route 1.1.1.0 255.255.255.0
eth 0/0).
eth 0/0).
2.
Shutdown the Hardware Module/SPA corresponding to that interface. When the hardware
module/SPA corresponding to that interface is shutdown, the static route entry is hidden from
the configuration.
module/SPA corresponding to that interface is shutdown, the static route entry is hidden from
the configuration.
3.
Reload the stand-by. When stand-by comes up, it performs a bulk sync to the running
configuration of master. However the static routes which are HIDDEN, won't be present in the
running configuration of master and hence will not be created in stand-by.
configuration of master. However the static routes which are HIDDEN, won't be present in the
running configuration of master and hence will not be created in stand-by.
4.
Bring up the hardware module/SPA. As this is still treated as OIR, the HIDDEN flag will be
removed from the static routes and other related configurations will now be part of running
configurations in the master. However these static routes are not present in stand-by as these
information is lost due to reload and there will not be a disclosure of routes in standby and
standby will be missing these static routes.
removed from the static routes and other related configurations will now be part of running
configurations in the master. However these static routes are not present in stand-by as these
information is lost due to reload and there will not be a disclosure of routes in standby and
standby will be missing these static routes.
5.
User executes no ip route. The route will be removed from master but as standby doesn't have
these routes, it will result in a PRC failure leading to a standby reload.
these routes, it will result in a PRC failure leading to a standby reload.
6.
Stand-by comes up after the reload. Now, it will have the entire configuration along with static
routes in sync as the unhidden static routes are now part of the running configurations that are
synced to standby
routes in sync as the unhidden static routes are now part of the running configurations that are
synced to standby
Workaround: Reloading the standby (most likely in a maintenance window) is the only way to sync
missing ip route statements.
missing ip route statements.
Resolved Caveats—Cisco IOS Release 12.2(33)SRE9
Cisco IOS Release 12.2(33)SRE9 is a rebuild release for Cisco IOS Release 12.2(33)SRE. The caveats
in this section are resolved in Cisco IOS Release 12.2(33)SRE9 but may be open in previous Cisco IOS
releases.
in this section are resolved in Cisco IOS Release 12.2(33)SRE9 but may be open in previous Cisco IOS
releases.
•
CSCsl38246
Symptom: When console logging is turned on, a flood of the messages shown below can potentially
lead to watchdog invocation and a subsequent crash:
lead to watchdog invocation and a subsequent crash:
%MWAM-DFC3-0-CORRECTABLE_ECC_ERR: A correctable ECC error has occurred,
A_BUS_L2_ERRORS: 0x0, A_BUS_MEMIO_ERRORS: 0xFF, A_SCD_BUS_ERR_STATUS: 0x80DC0000
Conditions: A single-bit correctable error is detected on a CPU read from DRAM. As long as the
errors remain correctable, and the performance of the processor does not deteriorate, the module is
usable.
errors remain correctable, and the performance of the processor does not deteriorate, the module is
usable.
Workaround: Since this is a parity error you can prevent the issue from happening in the future by
reseating the module. If the issue still persists after reseating the module then we may be facing a
hardware issue.
reseating the module. If the issue still persists after reseating the module then we may be facing a
hardware issue.
•
CSCsv74508
Symptom: If a linecard is reset (either due to an error or a command such as hw-module slot reload)
at the precise time an SNMP query is trying to communicate with that linecard, the RP could reset
due to a CPU vector 400 error.
at the precise time an SNMP query is trying to communicate with that linecard, the RP could reset
due to a CPU vector 400 error.
Conditions: This symptom occurs when the linecard is reset(either due to error or a command such
as hw-module slot reload) at the precise time an SNMP query is received.
as hw-module slot reload) at the precise time an SNMP query is received.