Specifications

1170
Cross-Platform Release Notes for Cisco IOS Release 12.0S
OL-1617-14 Rev. Q0
Resolved Caveats—Cisco IOS Release 12.0(28)S1
Conditions: This symptom is observed when the active RP is reloaded by entering the microcode
reload command.
Workaround: There is no workaround.
• CSCee34076
Symptoms: Routes that are removed soon after an SSO switchover occurs may remain in the CEF
table.
Conditions: This symptom is observed when VRFs are configured.
Workaround: There is no workaround.
• CSCee34094
Symptoms: A standby RP keeps crashing.
Conditions: This symptom is observed when both the snmp-server community string rw command
and the snmp-server enable traps snmp authentication linkdown linkup coldstart warmstart
command are configured.
Workaround: Remove the snmp-server community string rw command from the startup
configuration before rebooting the router. When the router has booted, reenter the snmp-server
community string rw command.
• CSCee34133
Symptoms: If CEF fails, you cannot enable CEF IPv6 by entering the ipv6 cef distributed
command.
Conditions: This symptom is observed on a Cisco 12000 series that runs the gsr-p-mz image of
Cisco IOS Release 12.0(28)S.
Workaround: There is no workaround.
• CSCee34474
Symptoms: The Open Shortest Path First (OSPF) peers were mapped to the wrong subinterfaces.
Conditions: A High Availability (HA) switch over the ATM interfaces was up and appeared to be
operational with OSPF adjacencies formed.
Workaround: There is no workaround.
• CSCee35185
Symptoms: After reloading a Cisco platform, one of the RPs may reload, or the following error
message may be displayed:
%PARSER-4-BADCFG: Unexpected end of configuration file.
Conditions: This symptom may be observed on any Cisco platform that is configured with dual RPs
and that supports RPR+.
Workaround: There is no workaround.
• CSCee35331
Symptoms: A router may reload if removing the L2TP class is followed by removing the pseudowire
class.
Conditions: This symptom is observed on a router that runs Cisco IOS Release 12.0(28)S when both
removals are done in a very short time via an auto test script and when the L2TP sessions are already
established. This is a timing related issue. The symptom could also occur in other releases.
Workaround: Wait at least 1 second before you remove the pseudowire class.