
901
Cross-Platform Release Notes for Cisco IOS Release 12.0S
OL-1617-14 Rev. Q0
Caveats
Resolved Caveats—Cisco IOS Release 12.0(30)S4
• CSCei25454
Symptoms: Connectivity loss may occur for MVPNs.
Conditions: This symptom is observed on a Cisco router that runs Cisco IOS Release 12.0(30)S or
a later release when the MVPNs function in a mixed network that has both VPNv4 RD2 prefixes for
MDT updates and IPv4 MDT subaddress family identifier (SAFI) prefixes.
Workaround: There is no workaround.
• CSCei26899
Symptoms: When you reset a BGP peer, some prefixes are missing.
Conditions: This symptom is observed on a Cisco MGX8850 RPM-XF that runs Cisco IOS
Release 12.3(11)T. However, the symptom is platform-independent and may also occur in other
releases.
Workaround: There is no workaround.
• CSCsa98059
Symptoms: Suboptimal routing occurs in an OSPF configuration or a routing loop occurs between
two border routers that redistribute BGP into OSPF.
Conditions: These symptoms are observed when at least two border routers are connected via eBGP
to another autonomous system, receive the same prefix over these connections, and redistribute the
prefix into OSPF. Under certain conditions, for example when the eBGP session from the preferred
BGP exit point to the eBGP peer flaps, the second router in the local autonomous system becomes
the preferred path and redistributes the eBGP route into OSPF. When the eBGP session with the first
router comes back up, the LSA should be flushed but this does not occur. This situation may create
routing problems on other OSPF routers or, when BGP has a higher administrative distance than
OSPF, routing loops between both border routers.
Workaround: There is no workaround.
• CSCsb54823
Symptoms: One router (R2) may begin sending updates to another router (R1) before R2 has
received the BGP prefix list from R1.
R1 does apply its inbound BGP prefix list so routes are denied if they need to be. However, R2 sends
routes to R1 which are denied by R1.
Conditions: This symptom is observed when both routers have negotiated a BGP outbound route
filter (ORF) and when R1 sends its BGP prefix list to R2.
Workaround: There is no workaround.
ISO CLNS
• CSCei58655
Symptoms: A route that fails remains in the routing table with its old metric, preventing an alternate
route from being used and causing a routing loop.
Conditions: This symptom is observed in a network that is configured for IS-IS and iSPF when the
IP routes that are advertised in an LSP (irrespective of whether or not the LSP is fragmented) do not
age-out during a rerouting failure.
Workaround: Remove iSPF from the IS-IS process by entering the router isis command followed
by the no ispf command.
Kommentare zu diesen Handbüchern