06-13-2017 01:45 AM - edited 03-01-2019 05:53 PM
Hi,
I'm trying to create a DualStack Environment over our existing IPv4 DMVPN multipoint GRE Tunnel. The Spoke Router can ping both HUB Routers wihtin the same tunnel. So i think the tunnel is working. But i'm not able to exchange the routes via EIGRP through the tunnel...
This is the Log off the Spoke Router, it seems that the IPv6 packets can not be encaspulated into the tunnel...
Jun 7 08:15:37.650 MEST: IPv6-Fwd: Encapsulation failed, could not queue for resolution
Jun 7 08:15:39.014 MEST: IPv6-Fwd: Destination lookup for FE80::8A43:E1FF:FE7E:98A0 : Local, i/f=Tunnel50, nexthop=FE80::8A43:E1FF:FE7E:98A0
Jun 7 08:15:39.014 MEST: IPV6: source FE80::8A43:E1FF:FE18:9200 (Tunnel50)
Jun 7 08:15:39.014 MEST: dest FE80::8A43:E1FF:FE7E:98A0 (Tunnel50)
Jun 7 08:15:39.014 MEST: traffic class 224, flow 0x0, len 60+0, prot 88, hops 1, forward to ulp
Jun 7 08:15:42.482 MEST: IPv6-Fwd: SAS on intf Tunnel50 picked source FE80::8A43:E1FF:FE7E:98A0 for FF02::A
Jun 7 08:15:42.482 MEST: IPV6: source FE80::8A43:E1FF:FE7E:98A0 (local)
Jun 7 08:15:42.482 MEST: dest FF02::A (Tunnel50)
Jun 7 08:15:42.482 MEST: traffic class 224, flow 0x0, len 80+0, prot 88, hops 1, originating
Jun 7 08:15:42.482 MEST: IPv6-Fwd: Encapsulation failed, could not queue for resolution
Jun 7 08:15:47.038 MEST: IPv6-Fwd: SAS on intf Tunnel50 picked source FE80::8A43:E1FF:FE7E:98A0 for FF02::A
Jun 7 08:15:47.038 MEST: IPV6: source FE80::8A43:E1FF:FE7E:98A0 (local)
Jun 7 08:15:47.038 MEST: dest FF02::A (Tunnel50)
Jun 7 08:15:47.038 MEST: traffic class 224, flow 0x0, len 80+0, prot 88, hops 1, originating
Jun 7 08:15:47.038 MEST: IPv6-Fwd: Encapsulation failed, could not queue for resolution
When i'm looking to the Log on the HUB Router, i'm able to see that he's trying to reach the Spoke Router, but there is established connection.
Jun 13 10:30:07.794 MEST: %DUAL-5-NBRCHANGE: EIGRP-IPv6 427: Neighbor FE80::8A43:E1FF:FE7E:98A0 (Tunnel50) is down: retry limit exceeded
Jun 13 10:30:09.942 MEST: %DUAL-5-NBRCHANGE: EIGRP-IPv6 427: Neighbor FE80::8A43:E1FF:FE7E:98A0 (Tunnel50) is up: new adjacency
Maybe someone have the same issue or can help me with this issue? :)
Thanks for your help!
Regards
Kevin
HUB Tunnel config:
interface Tunnel50
vrf forwarding Wild
ip address 192.168.5.1 255.255.255.128
no ip redirects
ip accounting precedence input
ip accounting precedence output
ip nbar protocol-discovery
ip flow ingress
ip flow egress
ip nhrp authentication spe
ip nhrp map multicast dynamic
ip nhrp network-id 50
ip nhrp holdtime 10
ip tcp adjust-mss 1432
load-interval 30
delay 1000
ipv6 address 2001:db8:2085:510::1/64
ipv6 mtu 1400
ipv6 nhrp authentication spe
ipv6 nhrp network-id 50
tunnel source GigabitEthernet0/0
tunnel mode gre multipoint
tunnel key 505050
end
Spoke Tunnel config:
interface Tunnel50
vrf forwarding Wild
ip address 192.168.5.7 255.255.255.128
no ip redirects
ip accounting precedence input
ip accounting precedence output
ip nbar protocol-discovery
ip hold-time eigrp 1 35
ip flow ingress
ip flow egress
ip nhrp authentication spe
ip nhrp map multicast 10.52.192.82
ip nhrp map 192.168.5.2 10.52.192.82
ip nhrp map 192.168.5.1 10.52.192.2
ip nhrp map multicast 10.52.192.2
ip nhrp network-id 50
ip nhrp nhs 192.168.5.2
ip nhrp nhs 192.168.5.1
ip nhrp registration timeout 120
ip tcp adjust-mss 1432
load-interval 30
ipv6 address 2001:db8:2085:510::15/64
ipv6 enable
ipv6 mtu 1400
no ipv6 redirects
ipv6 nhrp authentication spe
ipv6 nhrp map 2001:db8:2085:510::2/64 10.52.192.82
ipv6 nhrp map 2001:db8:2085:510::1/64 10.52.192.2
ipv6 nhrp network-id 50
ipv6 nhrp nhs 2001:db8:2085:510::1 nbma 10.52.192.2 multicast
ipv6 nhrp nhs 2001:db8:2085:510::2 nbma 10.52.192.82 multicast
tunnel source GigabitEthernet0/0
tunnel mode gre multipoint
tunnel key 505050
end
06-13-2017 05:24 AM
Hi Kevin
As i know I can make tunnel IPv4 over IPv4 or IPv6 over IPv4 or IPv6 over IPv6
Here all three configured together. I would prefer to choose only one, at least, for troubleshooting.
But at first glance I did not see here the multicast map command on spokes.
if IPv6 over IPv4:
ipv6 nhrp map multicast 10.52.192.82
if IPv6 over IPv6
ipv6 nhrp map multicast 2001:db8:2085:510::2
Also you MUST configure link-local addresses.
Try this and message the results
06-13-2017 05:41 AM
Hi deshtikypshaq
First thanks for your reply!
We just try to do a DualStack Configuration over an IPv4 tunnel do you think this is possible?
We tried your configuration hint but with no better result than before, the LOG continous to tell the encapsulation problem...
Now the configuration looks as follow:
interface Tunnel50
vrf forwarding Wild
ip address 192.168.5.7 255.255.255.128
no ip redirects
ip accounting precedence input
ip accounting precedence output
ip nbar protocol-discovery
ip hold-time eigrp 1 35
ip flow ingress
ip flow egress
ip nhrp authentication spe
ip nhrp map multicast 10.52.192.82
ip nhrp map 192.168.5.2 10.52.192.82
ip nhrp map 192.168.5.1 10.52.192.2
ip nhrp map multicast 10.52.192.2
ip nhrp network-id 50
ip nhrp nhs 192.168.5.2
ip nhrp nhs 192.168.5.1
ip nhrp registration timeout 120
ip tcp adjust-mss 1432
load-interval 30
ipv6 address 2001:db8:2085:510::15/64
ipv6 enable
ipv6 mtu 1400
no ipv6 redirects
ipv6 nhrp authentication spe
ipv6 nhrp map 2001:db8:2085:510::2/64 10.52.192.82
ipv6 nhrp map 2001:db8:2085:510::1/64 10.52.192.2
ipv6 nhrp map multicast 10.52.192.2
ipv6 nhrp map multicast 10.52.192.82
ipv6 nhrp network-id 50
ipv6 nhrp nhs 2001:db8:2085:510::1
ipv6 nhrp nhs 2001:db8:2085:510::2
tunnel source GigabitEthernet0/0
tunnel mode gre multipoint
tunnel key 505050
end
We first had to remove the command:
ipv6 nhrp nhs 2001:db8:2085:510::1 nbma 10.52.192.2 multicast
Until we're able to config your suggestion... Do you know the meaning of the other command from above?
Regards
Kevin
06-14-2017 12:24 AM
Here my config for: IPv6 multipoint GRE Tunnel over IPv4 DMVPN (as you pointed on topic).
I tested it and it working. I remove vrf it is not needed for DMVPN tunnel. And I also changed IPv6 addresses of tunnels and remove unnecessary commands, to be more convenient.
First be sure you can ping spokes and hubs each other: ping 10.52.192.XX (must ping ok).
So the config for tunnel is:
hub1:
!
interface Tunnel0
ip address 192.168.5.1 255.255.255.0
no ip redirects
ip nhrp map multicast dynamic
ip nhrp network-id 1
ipv6 address FE80:1::1 link-local
ipv6 address 2001:1::1/64
ipv6 nhrp map multicast dynamic
ipv6 nhrp network-id 50
tunnel source GigabitEthernet1/0
tunnel mode gre multipoint
tunnel key 505050
end
hub2:
!
interface Tunnel0
ip address 192.168.5.2 255.255.255.0
no ip redirects
ip nhrp map multicast dynamic
ip nhrp network-id 1
ipv6 address FE80:1::2 link-local
ipv6 address 2001:1::2/64
ipv6 nhrp map multicast dynamic
ipv6 nhrp network-id 50
tunnel source GigabitEthernet1/0
tunnel mode gre multipoint
tunnel key 505050
end
spoke1
!
interface Tunnel0
ip address 192.168.5.3 255.255.255.0
no ip redirects
ip nhrp map multicast 10.52.192.2
ip nhrp map multicast 10.52.192.82
ip nhrp network-id 1
ipv6 address FE80:1::3 link-local
ipv6 address 2001:1::3/64
ipv6 nhrp map multicast 10.52.192.2
ipv6 nhrp map multicast 10.52.192.82
ipv6 nhrp map 2001:1::1/128 10.52.192.2
ipv6 nhrp map 2001:1::2/128 10.52.192.82
ipv6 nhrp network-id 50
ipv6 nhrp nhs 2001:1::1
ipv6 nhrp nhs 2001:1::2
tunnel source GigabitEthernet1/0
tunnel mode gre multipoint
tunnel key 505050
end
spoke2
!
interface Tunnel0
ip address 192.168.5.4 255.255.255.0
no ip redirects
ip nhrp map multicast 10.52.192.2
ip nhrp map multicast 10.52.192.82
ip nhrp network-id 1
ipv6 address FE80:1::4 link-local
ipv6 address 2001:1::4/64
ipv6 nhrp map multicast 10.52.192.2
ipv6 nhrp map multicast 10.52.192.82
ipv6 nhrp map 2001:1::1/128 10.52.192.2
ipv6 nhrp map 2001:1::2/128 10.52.192.82
ipv6 nhrp network-id 50
ipv6 nhrp nhs 2001:1::1
ipv6 nhrp nhs 2001:1::2
tunnel source GigabitEthernet1/0
tunnel mode gre multipoint
tunnel key 505050
end
Here only tunnel config. And IPv6 addresses must ping OK each other: 2001:1::1, -::2, -::3, -::4. If ping not OK stop here and analyze and message here. if not OK try to shut tunnel interfaces on all, on the hubs clear DMVPN session and unshut interfaces again. It helps really.
Next add IPv6 EIGRP.
router eigrp EI
address-f ipv6 unicast au 1
shut all unused interfaces in eigrp mode.
Now everthing is OK. ipv6 eigrp neighbors see each other and routes advertised. if not try again to shut tunnel interfaces on all, on the hubs clear DMVPN session and unshut interfaces again.
06-14-2017 06:12 AM
Many thanks to your detailed explanations!
I will try it tomorrow when i'm back in the office :)
06-14-2017 12:24 AM
Just make as in previous my post
06-23-2017 01:49 AM
Ok now i tried your configuration recommendations :)
After i gave the link-local address i was able to exchange the eigrp route to HUB02 but not with HUB01.
And i'm not able to ping HUB01 over the link-local or the real address... but the configuration from HUB01 and HUB02 looks similar and also the configuration from SPOKE01 should be ok... maybe you can see a mistake in the config?
HUB01: show dmvpn
Interface: Tunnel50, IPv6 NHRP Details
Type:Unknown, Total NBMA Peers (v4/v6): 1
1.Peer NBMA Address: UNKNOWN
Tunnel IPv6 Address: FE80:1::5
IPv6 Target Network: FE80:1::5/128 (Wild)
# Ent: 1, Status: NHRP, UpDn Time: never, Cache Attrib: IX
HUB02: show dmvpn
Interface: Tunnel50, IPv6 NHRP Details
Type:Hub, Total NBMA Peers (v4/v6): 1
1.Peer NBMA Address: 10.52.192.50
Tunnel IPv6 Address: 2001:1:2085:510::15
IPv6 Target Network: 2001:1:2085:510::15/128 (Wild)
# Ent: 1, Status: UP, UpDn Time: 6d18h, Cache Attrib: D
HUB01
interface Tunnel50
vrf forwarding Wild
ip address 192.168.5.1 255.255.255.128
no ip redirects
ip accounting precedence input
ip accounting precedence output
ip nbar protocol-discovery
ip flow ingress
ip flow egress
ip nhrp authentication spe
ip nhrp map multicast dynamic
ip nhrp network-id 50
ip nhrp holdtime 10
ip tcp adjust-mss 1432
load-interval 30
delay 1000
ipv6 address FE80:1::1 link-local
ipv6 address 2001:1:510::1/64
ipv6 nhrp authentication spe
ipv6 nhrp map multicast dynamic
ipv6 nhrp network-id 50
tunnel source GigabitEthernet0/0
tunnel mode gre multipoint
tunnel key 505050
end
HUB02
interface Tunnel50
vrf forwarding Wild
ip address 192.168.5.2 255.255.255.128
no ip redirects
ip accounting precedence input
ip accounting precedence output
ip nbar protocol-discovery
ip flow ingress
ip flow egress
ip nhrp authentication spe
ip nhrp map multicast dynamic
ip nhrp map multicast 10.52.192.2
ip nhrp map 192.168.5.1 10.52.192.2
ip nhrp network-id 50
ip nhrp holdtime 10
ip nhrp nhs 192.168.5.1
ip tcp adjust-mss 1432
load-interval 30
delay 1050
ipv6 address FE80:1::2 link-local
ipv6 address 2001:1:510::2/64
ipv6 nhrp authentication spe
ipv6 nhrp map multicast dynamic
ipv6 nhrp network-id 50
tunnel source GigabitEthernet0/0
tunnel mode gre multipoint
tunnel key 505050
end
SPOKE01
interface Tunnel50
vrf forwarding Wild
ip address 192.168.5.7 255.255.255.128
no ip redirects
ip accounting precedence input
ip accounting precedence output
ip nbar protocol-discovery
ip hold-time eigrp 1 35
ip flow ingress
ip flow egress
ip nhrp authentication spe
ip nhrp map multicast 10.52.192.82
ip nhrp map 192.168.5.2 10.52.192.82
ip nhrp map 192.168.5.1 10.52.192.2
ip nhrp map multicast 10.52.192.2
ip nhrp network-id 50
ip nhrp nhs 192.168.5.2
ip nhrp nhs 192.168.5.1
ip nhrp registration timeout 120
ip tcp adjust-mss 1432
load-interval 30
ipv6 address FE80:1::5 link-local
ipv6 address 2001:1:510::15/64
ipv6 enable
no ipv6 redirects
ipv6 nhrp authentication spe
ipv6 nhrp map 2001:1:510::2/64 10.52.192.82
ipv6 nhrp map 2001:1:510::1/64 10.52.192.2
ipv6 nhrp map multicast 10.52.192.2
ipv6 nhrp map multicast 10.52.192.82
ipv6 nhrp network-id 50
ipv6 nhrp nhs 2001:1:510::1
ipv6 nhrp nhs 2001:1:510::2
tunnel source GigabitEthernet0/0
tunnel mode gre multipoint
tunnel key 505050
end
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide