
829
Cross-Platform Release Notes for Cisco IOS Release 12.0S
OL-1617-14 Rev. Q0
Caveats
Resolved Caveats—Cisco IOS Release 12.0(31)S
Workaround: Do not enter the ip routing command followed by the configure memory command
and the no ip routing command multiple times.
• CSCeg49796
Symptoms: Commands on a router may be unexpectedly removed from the running configuration.
Conditions: This symptom is observed on a router that is assigned as a neighbor to a BGP peer
group. For example, when the shutdown command was previously configured on the router, the
command is removed from the running configuration after the router is assigned as a neighbor to a
BGP peer group.
Workaround: Re-enter the commands on the router.
• CSCeg52889
Symptoms: TE tunnels do not come up.
Conditions: This symptom is observed when a new loopback interface is created with an IP address
on an MPLE TE head router that is configured with MPLS TE tunnels and when you reload the
router. The symptom occurs because of a change in router ID.
Workaround: Shut down the newly created loopback interface, save the configuration, and reload the
router.
• CSCeg54375
Symptoms: Routing inconsistencies may occur in the RIB: routes may be missing from the RIB but
may be present in the BGP table.
Conditions: This symptom is observed on a Cisco RPM-XF when the toaster processor crashes.
However, the symptom may occur on any platform that has a toaster processor.
Workaround: Enter the clear ip route vrf vrf-name * command.
• CSCeg70726
Symptoms: A router may crash when you enable MVPN by entering the mdt default group-address
command under a VRF.
Conditions: This symptom is observed on a Cisco router that is configured for BGP VPNv4.
Workaround: There is no workaround.
• CSCeg85215
Symptoms: BGP may crash when a withdraw message is formatted.
Conditions: This symptom is observed on a Cisco router during the converge of peers.
Workaround: There is no workaround.
• CSCeg89700
Symptoms: A Cisco router does not recognize an end-of-RIB message from a third-party vendor
router and continues to show the “Neighbor is currently in NSF mode” message although the restart
procedure of the third-party vendor router is complete.
Conditions: This symptom is observed on a Cisco router that is configured for IPv6 BGP peering
and NSF. Note that the symptom does not occur when IPv4 BGP peering is configured.
Workaround: There is no workaround.
• CSCeh07510
Symptoms: A traceback occurs on a router when you terminate an OSPF routing process by entering
the no router ospf command.
Kommentare zu diesen Handbüchern