Information Technology Reference
In-Depth Information
next hop inside the confederation, the BGP next hop on R1 is reset using a route map set-
NH for sessions with the other member AS. For sessions within the same member AS, the
BGP next hop is still reset using the
next-hop-self
method. (See Example 8-78.)
Example 8-78
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 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 65001
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
!
access-list 1 permit 192.168.18.8
!
route-map set-NH permit 10
match ip route-source 1
set ip next-hop 192.168.100.1
!
route-map set-NH permit 20
!
Within the route map set-NH, only routes from R8 (192.168.18.8) are reset with a next hop
to R1 (192.168.100.1). As discussed in Case Studies 2 and 3, this is one of the methods to
avoid forwarding loops during migration.
Example 8-79 shows the BGP configurations of R2.
Example 8-79
BGP Configurations on R2
router bgp 65000
no synchronization
bgp router-id 192.168.100.2
bgp log-neighbor-changes
bgp confederation identifier 100
bgp confederation peers 65001
neighbor Internal peer-group
continues
