Saturday, August 10, 2019

DMVPN - first config, hub doesn't learn EIGRP routes

Hi.

I'm making DMVPN config for customer for the first time and have some issues with EIGRP. Spoke (for now there's only one) learns EIGRP routes advertised by Hub, but not the other way around.

DMVPN is formed correctly (Hub sits in DMZ, hence "DN" status in "show dmvpn - not sure if that's important), same for EIGRP neighborship.

Hub (3945): Gi0/0 (LAN), Gi0/3 (WAN)

Spoke (3925): Gi0/0 (LAN), Gi0/2 (WAN)

Configs below:

***HUB*** interface Tunnel1 description DMVPN-HUB ip address 10.255.141.254 255.255.255.0 no ip redirects ip mtu 1400 ip authentication mode eigrp 1 md5 ip authentication key-chain eigrp 1 EIGRP-KEY no ip split-horizon eigrp 1 ip nhrp authentication NHRP_PASSWORD ip nhrp network-id 100 ip nhrp redirect ip tcp adjust-mss 1360 qos pre-classify keepalive 10 3 tunnel source GigabitEthernet0/3 tunnel mode gre multipoint tunnel key 111111111111111 tunnel protection ipsec profile DMVPN_IPSEC_PROFILE shared router eigrp 1 network 10.255.141.0 0.0.0.255 network 192.168.0.0 passive-interface default no passive-interface Tunnel1 eigrp router-id 10.255.141.254 ***SPOKE*** interface Tunnel1 ip address 10.255.141.77 255.255.255.0 no ip redirects ip mtu 1400 ip authentication mode eigrp 1 md5 ip authentication key-chain eigrp 1 EIGRP-KEY ip nhrp authentication NHRP_PASSWORD ip nhrp map multicast PUBLIC_IP_REDACTED ip nhrp map 10.255.141.254 PUBLIC_IP_REDACTED ip nhrp network-id 100 ip nhrp holdtime 600 ip nhrp nhs 10.255.141.254 ip nhrp shortcut ip tcp adjust-mss 1360 if-state nhrp qos pre-classify keepalive 10 3 tunnel source GigabitEthernet0/2 tunnel mode gre multipoint tunnel key 111111111111111 tunnel protection ipsec profile DMVPN_IPSEC_PROFILE shared router eigrp 1 network 10.255.141.0 0.0.0.255 network 192.168.77.0 passive-interface default no passive-interface Tunnel1 eigrp router-id 192.168.254.77 eigrp stub connected summary 

Any ideas what's happening?

EDIT: IOS versions (I'm hesitant to update it because I had sooo many problems with AnyConnect on hub killing it...):

  • HUB: 15.7(3)M2

  • Spoke: 15.1(4)M4



No comments:

Post a Comment