add r4, eigrp 1, the two loopbacks...
router eigrp 1
passive-interface Serial0
network 192.168.1.0
network 192.168.100.0
!
router bgp 200
redistribute eigrp 1
neighbor 192.168.1.226 remote-as 100
this is using redistribution which is not recommended for igp to bgp...
r1#sh ip bgp
BGP table version is 9, local router ID is 1.1.1.1
Network Next Hop Metric LocPrf Weight Path
*> 192.168.1.216/30 192.168.1.225 0 0 200 ?
r> 192.168.1.224/30 192.168.1.225 0 0 200 ?
*> 192.168.100.0 192.168.1.225 0 0 200 ?
*> 192.168.200.0 192.168.1.225 156160 0 200 ?
r1#
great... i always lke to study what is not recommended so i know to avoid it for the future... this practice of misconfiguring to prove a point i find is often confusing... this happens all the time...
so instead simply add the networks to bgp...
router bgp 200
network 192.168.1.216 mask 255.255.255.252
network 192.168.100.0
network 192.168.200.0
neighbor 192.168.1.226 remote-as 100
which means you are doing the work of the protocol... basically statically assigning the networks to bgp from eigrp... i guess my former colleague was right about bgp being static on steroids...
r1#sh ip bgp
BGP table version is 16, local router ID is 1.1.1.1
Network Next Hop Metric LocPrf Weight Path
*> 192.168.1.216/30 192.168.1.225 0 0 200 i
*> 192.168.100.0 192.168.1.225 0 0 200 i
*> 192.168.200.0 192.168.1.225 156160 0 200 i
note the use of the mask command for the eigrp link... the explanation is that it is a subnet, not a major network... this makes sense...
another big point is the lack of ? marks in the path output... this is the origin indicator, whereas with redistribution it was incomplete, the i means that it originated from an igp...
so don't redistribute from igp to bgp, nor from bgp to igp... that's nice...
No comments:
Post a Comment