Specifications

1299
Cross-Platform Release Notes for Cisco IOS Release 12.0S
OL-1617-14 Rev. Q0
Resolved Caveats—Cisco IOS Release 12.0(27)S3
BGP routing table entry for 200:2:192.168.0.0/32, version 54
Paths: (2 available, best #1, table vpn2)
Flag: 0x820
Advertised to non peer-group peers:
10.10.10.10 10.20.20.20
2
10.4.1.2 from 10.4.1.2 (10.4.1.2)
Origin IGP, localpref 100, valid, external, best
Extended Community: RT:1:2
2 100, imported path from 200:2:172.16.0.0/24
10.1.1.2 from 10.1.1.2 (10.1.1.2)
Origin IGP, localpref 100, valid, external
Extended Community: RT:1:3
This BGP VPNv4 table entry is for prefix 192.168.0.0/32 but it shows that a path is imported from
172.16.0.0/24. This situation occurs when a path has a link to a deleted BGP table entry, and then
the memory for the deleted entry is reused for a new table entry of which the prefix may not match
with the importing entry.
Conditions: These symptoms are observed when you enter the maximum-paths import number
command in router BGP address-family IPv4 VRF mode. The number argument indicates the
number of paths to import from one VRF to another.
Workaround: Remove the maximum-paths import number command from the router BGP
address-family IPv4 VRF mode.
• CSCee69396
Symptoms: A Cisco 10000 series router that is running Cisco IOS Release 12.0(25)SX6 notices a
large increase of at least 15% in the CPU usage in the “BGP Router” process when upgraded from
Cisco IOS Release 12.0(23)SX5. This occurs under certain conditions where there are a very large
number of BGP neighbors in a PE-CE scenario. During the steady state after BGP router
convergence, there needs to be a constant churn in the updates with addition/withdrawal of the routes
from the neighbor BGP peers.
Conditions: This symptom is observed on a Cisco 10000 series router that is running Cisco IOS
Release 12.0(25)SX6. All versions starting from Cisco IOS Release 12.0(25)SX to
Release 12.0(25)SX6 are affected by this problem.
Workaround: Configure the neighbors by grouping into sets or peer-groups, in which a few of the
neighbors in each set share similar outbound policy. Each set will fall into a separate update group
or peergroup.
• CSCee83549
Symptoms: When multipath is configured, one of the paths may have an inconsistent (old) label,
causing only one path to be operational.
Conditions: This symptom is observed when BGP does not update the outlabel information in the
TFIB and for CEF.
Workaround: Clear or readvertise the route that is inoperational.
• CSCee89438
Symptoms: An MSDP enabled RP does not build an (S,G) state from its SA cache when it should
do so. Depending on the topology and if an SPT threshold is configured as infinite, this situation
may result in a multicast forwarding interruption of up to 2 minutes.