
879
Cross-Platform Release Notes for Cisco IOS Release 12.0S
OL-1617-14 Rev. Q0
Caveats
Resolved Caveats—Cisco IOS Release 12.0(30)S5
Workaround: To enable the members of the BGP update group to synchronize with each other, enter
the clear ip /jointfilesconvert/415844/bgp * soft out command. Doing so does not bounce the sessions but forces BGP to
re-advertise all prefixes to each member.
• CSCsb36755
Symptoms: When BGP receives an update that has a worse metric route than the previously received
route for equal-cost multipath, the BGP table is updated correctly but the routing table is not,
preventing the old path from being deleted from the routing table.
Conditions: This symptom is observed on a Cisco router that is configured for BGP multipath.
Workaround: Enter the clear ip route network command.
• CSCsb74708
Symptoms: An OSPF sham link may not form an adjacency.
Conditions: This symptom is observed when there is an interface in the global route table that has
an IP address that matches the IP address of the OSPF sham link neighbor.
Workaround: Reconfigure the routers so that the IP address of the OSPF sham link neighbor does
not match any IP addresses of interfaces in the global route table.
Alternate Workaround: Shut down the interface or change the IP address of the interface in the
global route table.
• CSCsb79749
Symptoms: The output of the show memory summary command may contain garbled characters in
the “What” column.
Conditions: This symptom is observed when you configure OSPF with at least one network, and then
unconfigure it.
Workaround: There is no workaround.
• CSCsc59089
Symptoms: BGP does not advertise all routes to a peer that sends a route-refresh request.
Conditions: This symptom is observed under the following conditions:
–
The router is in the process of converging all of its peers and has updates ready in the output
queue for the peer.
–
The peer sends a route-refresh request to the router. This may occur when the clear ip /jointfilesconvert/415844/bgp *
soft in command is entered on the peer or when a VRF is added to the peer.
–
The router processes the route-refresh request from the peer while the router still has updates in
the output queue for the peer.
In this situation, all of prefixes that are advertised by the unsent updates in the output queue for the
peer are lost.
Workaround: There is no workaround. When the symptom has occurred, enter the clear ip /jointfilesconvert/415844/bgp *
soft out command on the router to force the router to send all updates to its peers.
• CSCsc75426
Symptoms: A router that is configured for BGP and that has the ip policy-list command enabled
may unexpectedly reload because of a bus error or SegV exception.
Conditions: This symptom is observed when BGP attempts to send an update with a “bad” attribute.
Workaround: There is no workaround.
Comentarios a estos manuales