Hello All,
Is there any reason why this would not satisfy the requirements for the
Loopback advertisements for this task? This approach seems to be a little
more specific without needing to redistribute connected routes in BGP. It
appears that I achieve the same result, but I'd prefer another set of eyes
and opinions.
R2
----------------------------------------------------------
access-list 1 permit 200.0.0.0 0.0.255.255
route-map bgploop
set origin incomplete
match ip address 1
router bgp 256
network 200.0.0.2 mask 255.255.255.255 route-map bgploop
network 200.0.1.2 mask 255.255.255.255 route-map bgploop
network 200.0.2.2 mask 255.255.255.255 route-map bgploop
network 200.0.3.2 mask 255.255.255.255 route-map bgploop
R5
----------------------------------------------------------
access-list 1 permit 200.0.0.0 0.0.255.255
route-map bgploop
set origin incomplete
match ip address 1
router bgp 256
network 200.0.0.5 mask 255.255.255.255 route-map bgploop
network 200.0.1.5 mask 255.255.255.255 route-map bgploop
network 200.0.2.5 mask 255.255.255.255 route-map bgploop
network 200.0.3.5 mask 255.255.255.255 route-map bgploop
R6
----------------------------------------------------------
access-list 1 permit 200.0.0.0 0.0.255.255
route-map bgploop
set origin incomplete
match ip address 1
router bgp 256
network 200.0.0.6 mask 255.255.255.255 route-map bgploop
network 200.0.1.6 mask 255.255.255.255 route-map bgploop
network 200.0.2.6 mask 255.255.255.255 route-map bgploop
network 200.0.3.6 mask 255.255.255.255 route-map bgploop
The sh ip bgp output from R2 is below:
R2(config-router)#do sh ip bgp
BGP table version is 23, local router ID is 200.0.3.2
Status codes: s suppressed, d damped, h history, * valid, > best, i -
internal,
r RIB-failure, S Stale
Origin codes: i - IGP, e - EGP, ? - incomplete
Network Next Hop Metric LocPrf Weight Path
*> 150.100.25.0/24 0.0.0.0 0 32768 i
*>i150.100.69.0/24 150.100.100.6 0 100 0 i
*>i150.100.96.0/24 150.100.100.6 0 100 0 i
*> 150.100.100.0/24 0.0.0.0 0 32768 i
*> 200.0.0.2/32 0.0.0.0 0 32768 ?
*>i200.0.0.5/32 150.100.100.5 0 100 0 ?
*>i200.0.0.6/32 150.100.100.6 0 100 0 ?
*> 200.0.1.2/32 0.0.0.0 0 32768 ?
*>i200.0.1.5/32 150.100.100.5 0 100 0 ?
*>i200.0.1.6/32 150.100.100.6 0 100 0 ?
*> 200.0.2.2/32 0.0.0.0 0 32768 ?
*>i200.0.2.5/32 150.100.100.5 0 100 0 ?
*>i200.0.2.6/32 150.100.100.6 0 100 0 ?
*> 200.0.3.2/32 0.0.0.0 0 32768 ?
*>i200.0.3.5/32 150.100.100.5 0 100 0 ?
*>i200.0.3.6/32 150.100.100.6 0 100 0 ?
R2(config-router)#
R2(config-router)#do sh ip bgp 200.0.0.6
BGP routing table entry for 200.0.0.6/32, version 15
Paths: (1 available, best #1, table Default-IP-Routing-Table)
Advertised to update-groups:
2
Local, (Received from a RR-client)
150.100.100.6 from 150.100.100.6 (200.0.3.6)
Origin incomplete, metric 0, localpref 100, valid, internal, best
R2(config-router)#
Regards,
--
Darrell Arbaugh
_______________________________________________
For more information regarding industry leading CCIE Lab training, please visit
www.ipexpert.com
