Redistribution throughout IGP and BGP is a typical situation particularly when we now have WAN and LAN communication occurring. One instance consists of Service supplier offering WAN hyperlink on BGP and buyer utilizing IGP like EIGRP in LAN setting.
Nevertheless, let’s perceive what occurs when EIGRP redistributes default route into BGP. In case default route not being marketed into BGP, how can the requirement situation for BGP to study default route be met.
Situation: EIGRP Learnt Default Route not being marketed into BGP
A lab situation has been created under –
Under is the essential configuration of R1, R2 and R3 –
R1#
interface Loopback0
ip handle 1.1.1.1 255.255.255.0
!
interface FastEthernet0/0
ip handle 192.168.12.1 255.255.255.0
!
router eigrp 1
redistribute static metric 1000 100 255 1 1500 >>>>>> Configured to redistribute default route into EIGRP
community 1.1.1.0 0.0.0.255
community 192.168.12.0
no auto-summary
!
ip route 0.0.0.0 0.0.0.0 Null0 >>>>>> A Default Route is injected in the direction of NULL0 for testing objective
R2
interface Loopback0
ip handle 2.2.2.2 255.255.255.0
!
interface FastEthernet0/0
ip handle 192.168.12.2 255.255.255.0
!
interface FastEthernet0/1
ip handle 192.168.23.2 255.255.255.0
!
router eigrp 1
community 192.168.12.0
no auto-summary
!
router bgp 1
no synchronization
bgp log-neighbor-changes
community 2.2.2.0 masks 255.255.255.0
community 192.168.23.0
neighbor 192.168.23.3 remote-as 2
neighbor 192.168.23.3 soft-reconfiguration inbound
R3
interface FastEthernet0/1
ip handle 192.168.23.3 255.255.255.0
!
router bgp 2
no synchronization
bgp log-neighbor-changes
community 192.168.23.0
neighbor 192.168.23.2 remote-as 1
neighbor 192.168.23.2 soft-reconfiguration inbound
no auto-summary
Subsequent we configure redistribution of EIGRP Routes into BGP on R2 –
R2(config)#router bgp 1
R2(config-router)#redistribute eigrp 1
Now lets view the output on R3
R3#present ip bgp
BGP desk model is 10, native router ID is 192.168.23.3
Standing codes: s suppressed, d damped, h historical past, * legitimate, > finest, i – inside,
r RIB-failure, S Stale
Origin codes: i – IGP, e – EGP, ? – incomplete
Community Subsequent Hop Metric LocPrf Weight Path
*> 1.1.1.0/24 192.168.23.2 409600 0 1 ?
*> 2.2.2.0/24 192.168.23.2 0 0 1 i
*> 192.168.12.0 192.168.23.2 0 0 1 ?
* 192.168.23.0 192.168.23.2 0 0 1 i
As seen from above configuration , R3 is just not receving the default Route redistributed from EIGRP into BGP .
Subsequent , we’ll embrace “Default-originate” key phrase on R2 and examine the output on R3 –
R2(config)#router bgp 1
R2(config-router)#neighb 192.168.23.3 default-originate
R3#sh ip bgp
BGP desk model is 11, native router ID is 192.168.23.3
Standing codes: s suppressed, d damped, h historical past, * legitimate, > finest, i – inside,
r RIB-failure, S Stale
Origin codes: i – IGP, e – EGP, ? – incomplete
Community Subsequent Hop Metric LocPrf Weight Path
*> 0.0.0.0 192.168.23.2 0 0 1 i
*> 1.1.1.0/24 192.168.23.2 409600 0 1 ?
*> 2.2.2.0/24 192.168.23.2 0 0 1 i
*> 192.168.12.0 192.168.23.2 0 0 1 ?
* 192.168.23.0 192.168.23.2 0 0 1 i
*> 0.0.0.0 0 32768 i
As seen from the output , as soon as “Default-Originate” key phrase is issued on R2 for neighbour R3 , the Default Route is being marketed into BGP which was not the case initially.
Proceed Studying:
Redistributed EIGRP Routes not learnt attributable to identical Router ID
EIGRP vs OSPF : Know the distinction
