redistribute EIGRP into BGP on N9ks

[SandevChopra07800]

Hi folks,

I have a use case to redistribute EIGRP learnt external routes into eBGP on N9k running ver 9.3.x

I used a route-map for this, but nothing was learnt on the eBGP neighbor. When advertising the same eigrp learnt subnet via the Network command under the address-family ipv4 unincast, it worked.

Wondering, how EIGRP redistribution works in BGP on N9ks. Is the redistribution really needed OR just the network command does the trick? Any relevant documents would be helpful. 

Thx

[Georg Pauwen]

Hello,

what does the route map you use look like ?

The redistribution should look like below:

router bgp 65535
address-family ipv4 unicast
redistribute eigrp 1 route-map EIGRP_RM

[SandevChopra07800]

That is correct.

the routemap refers a prefix list which permits the subnet.

[Georg Pauwen]

And the prefix list matches the D-EX route exactly ?

I am not sure prefix lists work well with EIGRP (they do with BGP), but what if the route map matches an access list instead ?

[SandevChopra07800]

---------------------------------------------------------------

ip prefix-list EIGRP-TO-EBGP permit 10.199.0.0/16

Route-map EIGRP-TO-EBGP permit 10

Match IP address prefix-list EIGRP-TO-EBGP

Exit

router bgp 65519

  address-family ipv4 unicast

    redistribute eigrp eigrp-LAN-EIGRP route-map EIGRP-TO-EBGP

------------------------------------------------------------------

The ACL method in NXOS will need source and destination, unlike a standard ACL in IOS which can just match a subnet/wildcard bits. 

[Georg Pauwen]

Hello,

just to be sure, check if the redistributed route shows up in the BGP topology table...

What if you match on a 'permit any' prefix list, or if you redistribute connected routes as well (redistribute direct), or if you use the EIGRP number instead of the name during redistribution ?

[SandevChopra07800]

Redistribute direct works with a routemap.

the eigrp redistributed route does not show up in the bgp topology table.

Nxos needs the eigrp-process name tag, not the number while redistributing. 

[Georg Pauwen]

Hello,

listen, I am just trying to help. I have seen it countless, and I mean countless, times, that the documentation tells you to configure something in a specific way, but the documentation is just plain wrong. So in order to get this resolved, I am trying to think out-of-the-box.

What I meant was to replace the EIGRP instance tag with the AS number. You probably have configured something like below:

ip prefix-list EIGRP-TO-EBGP permit 10.199.0.0/16
!
route-map EIGRP-TO-EBGP permit 10
match IP address prefix-list EIGRP-TO-EBGP
!
router bgp 65519
address-family ipv4 unicast
redistribute eigrp eigrp-LAN-EIGRP route-map EIGRP-TO-EBGP

!

router eigrp eigrp-LAN-EIGRP
autonomous-system 1

So just replace 'eigrp-LAN-EIGRP' with '1" (or whatever AS number you are using).

In order to verify if the redistribution works at ll, I would like to see what happens if you redistribute everything including connected routes:

ip prefix-list EIGRP-TO-EBGP permit  0.0.0.0/0 le 32
!
route-map EIGRP-TO-EBGP permit 10
match IP address prefix-list EIGRP-TO-EBGP
!
router bgp 65519
address-family ipv4 unicast
redistribute direct eigrp eigrp-LAN-EIGRP route-map EIGRP-TO-EBGP

or use the AS number:

ip prefix-list EIGRP-TO-EBGP permit  0.0.0.0/0 le 32
!
route-map EIGRP-TO-EBGP permit 10
match IP address prefix-list EIGRP-TO-EBGP
!
router bgp 65519
address-family ipv4 unicast
redistribute direct eigrp 1 route-map EIGRP-TO-EBGP

What device to you expect to see the redistributed routes on, is that a Nexus as well ?