BGP-CCIE的学习资料.pptVIP

* * * * * * * * * * * * * Should be CIERS110S04L01.ppt slide 14 (replaced ‘R2#show run | beg router bgp’ with ‘R2#show run | sec router bgp’) * Should be CIERS110S04L01.ppt slide 15 (replaced ‘R2#show run | beg router bgp’ with ‘R2#show run | sec router bgp’) * * * * * * * * * * * * * * * * * * * * * * * * * BGP Task Analysis and Configuration Resolving Advanced BGP Tasks Review of BGP Peering BGP Peering Options Analysis Example: BGP Confederation Peering R1 and Sw2 in AS 65001 R4 and R3 in AS 65002 For each sub-AS: Use bgp confederation identifier command Use bgp confederation peers command AS 100 behaves like one AS in terms of: Local preference Next hop Administrative distance MED AS path length Where unspecified, the IP addresses are /24 subnets of 172.16.0.0. Next-Hop Reachability Issues Next-Hop Reachability Issues Symptoms: Advertised subnets are not placed in all routing tables. Next hop is shown as Inaccessible on BGP table. Options to resolve: Advertise the border networks into the IGP: Is not permitted in this lab Use neighbor next-hop-self command: Affects all routes advertised to that neighbor Use a route-map command to define the next-hop address: Demonstrates that the BGP next hop can be directly manipulated Example: Next-Hop Reachability Issue R4 has route 147.10.1.128 in the BGP table but not in the IP routing table. R1 has route 157.10.1.208 in the BGP table but not in the IP routing table. The root issue is that the border networks are not advertised into AS 100. The neighbor next-hop-self command on R4 causes a routing loop on R3. R4 needs to use a selective route map. Where unspecified, the IP addresses are /24 subnets of 172.16.0.0. BGP Synchronization Issues BGP Synchronization Issues With synchronization enabled, BGP does not use or advertise a route learned from an IBGP peer unless there is a matching route in the IP routing table from a source other than BGP. BGP synchronization is useful as a check against advertising routes that i