Information Technology Reference
In-Depth Information
Example 8-88 BGP Configurations on R6
R6#show ip bgp
BGP table version is 9, local router ID is 192.168.100.6
Status codes: s suppressed, d damped, h history, * valid, > best, i - internal,
r RIB-failure
Origin codes: i - IGP, e - EGP, ? - incomplete
Network Next Hop Metric LocPrf Weight Path
*>i172.16.0.0 192.168.15.1 0 100 0 (65000) 200 i
*>i192.168.200.0 192.168.100.3 0 100 0 (65000) i
*> 192.168.201.0 0.0.0.0 0 32768 i
*>i192.168.202.0 192.168.100.7 0 100 0 I
Step 3: On R1 and R2, Add Member AS 100 to the Peers and Update the Peerings
with R4
On R1 and R2, update the peerings with R4. Example 8-89 shows the new BGP configura-
tions on R1. Note that you must add member AS 100 to the confederation peer list. Without
it, the session cannot be established. If R1 thinks R4 is attempting an eBGP session rather
than a confederation eBGP session, the session is rejected because it conflicts with confed-
eration 100. Similar changes are made to R2.
Example 8-89 BGP Configurations on R1
router bgp 65000
no synchronization
bgp router-id 192.168.100.1
bgp log-neighbor-changes
bgp confederation identifier 100
bgp confederation peers 100 65001
neighbor Internal peer-group
neighbor Internal remote-as 65000
neighbor Internal update-source Loopback0
neighbor Internal next-hop-self
neighbor 192.168.14.4 remote-as 100
neighbor 192.168.14.4 route-map set-NH out
neighbor 192.168.15.5 remote-as 65001
neighbor 192.168.15.5 route-map set-NH out
neighbor 192.168.18.8 remote-as 200
neighbor 192.168.100.2 peer-group Internal
neighbor 192.168.100.3 peer-group Internal
no auto-summary
Figure 8-16 shows the updated topology.
Search WWH ::




Custom Search