Routing strategy in symptomatic EIGRP topology. Please assist?

[jmaxwellUSAF]

Hello.

GIVEN:
Server1 <==> Nexus9300 <==> DMVPN-Router1 <==L2L-tunnel1==> DMVPN-Router2 <===> Cat2960 <==> ASA1120 <==L2L-tunnel2==> Server2

Existing static routes redistributed to EIGRP in ASA1120 are NOT present in DMVPN-Router2

GOAL:
Implement a route from Server1 to Server2.

QUESTIONS:

1. What is the best routing strategy to accomplish the GOAL?

2. In what box(es) is the new route(s) inserted?

Thank you!

[MHM Cisco World]

draw topology please.

[jmaxwellUSAF]

Server1 <==> Nexus9300 <==> DMVPN-Router1 <==L2L-tunnel1==> DMVPN-Router2 <===> Cat2960 <==> ASA1120 <==L2L-tunnel2==> Server2

[MHM Cisco World]

L2L tunnel between ASA and DMVPN router ??

[jmaxwellUSAF]

L2L tunnel between ASA and vendor (Server2). 

Server1 <==> Nexus9300 <==> DMVPN-Router1 <==L2L-tunnel1==> DMVPN-Router2 <===> Cat2960 <==> ASA1120 <==L2L-tunnel2==> Server2

[paul driver]

Hello

---

@jmaxwellUSAF wrote:

Hello.

GIVEN:
Server1 <==> Nexus9300 <==> DMVPN-Router1 <==L2L-tunnel1==> DMVPN-Router2 <===> Cat2960 <==> ASA1120 <==L2L-tunnel2==> Server2

Existing static routes redistributed to EIGRP in ASA1120 are NOT present in DMVPN-Router2

---

So your OP suggests you are running EIGRP over the DMVPN tunnel correct and that redistributed routes are not being advertised between spokes or at least between spoke and hub?

So If you as running eigrp over the DMVPN and routes are not being advertised then its probably to do with default split horizon being active on the DMVPN hub, which will need to be turned off

Example:
Int tun xx
description DMVPN hub
no ip split-horizon eigrp xxx

[Kanan Huseynli]

Hi,

you have problem in this segment "DMVPN-Router2 <===> Cat2960 <==> ASA1120" since ASA1120 redistributes routes but DMVPN-RTR2 does not receive. Here, nothing is related to tunnel and split-horizon issue.

This issue (redistribute into eigrp) "sounds" well-known seed metric issue. Do you type parameters for metric calculation? EIGRP (as RIP) uses infinity metric values for calculation, thus route can not be selected as best and advertised.

Add metric values (for example based on incoming interface parameters - bandwidth/ delay etc.) then you should have route on RTR2.

HTH,

Please rate and mark as an accepted solution if you have found any of the information provided useful.

[paul driver]

Hello @Kanan Huseynli 

---

@Kanan Huseynli wrote: nothing is related to tunnel and split-horizon issue.

This issue (redistribute into eigrp) "sounds" well-known seed metric issue. Do you type parameters for metric calculation? EIGRP (as RIP) uses infinity metric values for calculation, thus route can not be selected as best and advertised.

Add metric values (for example based on incoming interface parameters - bandwidth/ delay etc.) then you should have route on RTR2.

---

Curious, why do you need to set seed metric when redistributing static routes into EIGRP, As no metric conversion is required when doing this?

[Kanan Huseynli]

Hello Paul,

that's right. Normally, it is not needed (at least on IOS/IOS XE), but I don't quite sure about ASA implementation.

Regards,