10 likes | 147 Views
L3 VPN. EIGRP routes should be advertised via eBGP. EIGRP routes should be advertised via eBGP. eBGP. eBGP. EIGRP 10. BB1 AS 10. BB2 AS 10. No need to adv. redistributed EIGRP via IBGP. Currently, EIGRP is redistributed into BGP. Currently, EIGRP is redistributed into BGP. i BGP.
E N D
L3 VPN EIGRP routes should be advertised via eBGP EIGRP routes should be advertised via eBGP eBGP eBGP EIGRP 10 BB1 AS 10 BB2 AS 10 No need to adv. redistributed EIGRP via IBGP Currently, EIGRP is redistributed into BGP Currently, EIGRP is redistributed into BGP iBGP EIGRP AD is allotted as 210, and iBGP AD is 200 as not altered. Due to the complexity of various routing protocol in Backbone area, Specific subnets are not correctly learned from proper routing protocol at sometime. These specific subnet should be learned by EIGRP instead of iBGP routes. Redistributed EIGRP routes should be advertised via L3 VPN, but, we have to filter send these routes to nearby BB device. Because, EIGRP is already covering I tried to add ‘set tag’ when EIGRP redistribute into BGP. But, I could see following error that ‘set tag’ doesn’t support along with BGP process. % "rdeigrp2bgp" used as redistribute eigrp into bgp route-map, set tag not supported I strived to use ‘community string’ when redistributed, so that I can use that community-string to filter via iBGP session when retrieving the routes. But, it works What is the another best and simple way to archive like above environment? Redistributed EIGRP should be advertised via eBGP, but, no need to advertise via IBGP session.