Got it

DSVPN Spoke connected to two hubs with two tunnel interfaces not working

Latest reply: May 17, 2020 01:10:31 2360 8 0 0 0
Hi dear,

Im working to setup new DSVPN topology to connect many spokes to dual hubs in datacenter by using two tunnel interfaces from spokes to each hub.
Physical peering is done by using OSPF on a 1 process and second peering via nhrp tunnels by using a second OSPF process and different area.

I can successfully register to spoke with the first hub and build the OSPF adjency but the second tunnels still protocol down from the same spoke to the second Hub.

I use for each tunnel P2p ip subnet and it is advertised via OSPF. Network reachability was verified between spoke and two hub using the physical ip addresses using for NHRP peering.

OSPF and MGRE using P2Mp between spokes and Hubs.

I don't found any documentation for this scenario using two tunnel interfaces from Spoke to Hub.
I have experience the Actif/standby tunnel registration from Spoke to Hub by using a using tunnel interfaces to connect to the two hubs and its working well.

Please check advise and help to use two tunnel interfaces from Spoke to Hub.

Thanks.

sindiba
sindiba Created Aug 10, 2017 19:27:08 (0) (0)
Any news please 
@kmyd @撒么 please help ,thanks.
View more
  • x
  • convention:

Posted by 网络管理员木头 at 2017-08-09 02:48 @kmyd @撒么 please help ,thanks.
Nobody can help on this case?!
View more
  • x
  • convention:

can we see the config ? I do the similar setup, 2 hubs but using one tunnel interface. see below, I've xx the internet IP's but you get the idea...

interface Tunnel0/0/129
description ***DMVPN/DSVPN_CLOUD_129***
tcp adjust-mss 1360
ip address 192.168.159.143 255.255.255.128
tunnel-protocol gre p2mp
source Dialer1
gre key cipher thekey
qos pre-classify
ospf cost 50
ospf authentication-mode md5 1 cipher thekey
ospf network-type p2mp
ospf dr-priority 0
ospf timer hello 1
ospf timer dead 3
ipsec profile ENCR-T129
statistic enable inbound
statistic enable outbound
undo ip fast-forwarding enable
nhrp shortcut
nhrp registration no-unique
nhrp registration interval 120
nhrp network-id 129
nhrp entry holdtime seconds 3600
nhrp entry 192.168.159.130 xx.xx.xx.218 register
nhrp entry 192.168.159.132 xx.xx.xx.217 register
View more
  • x
  • convention:

hi, I have already implement this scenario. but we can't provide load balancing between the two hubs. at all time trafic is forwarded to on hub and need to be done to failover to standby hub.

our objectif is to provide link balancing accross the two hubs.
View more
  • x
  • convention:

sks29
sks29 Created Feb 19, 2018 11:51:58 (0) (0)
In one project at customer site same solution was suggested but load balancing couldn't be achieved
@sindiba please confirm if you found the solution for the load balancing issue?
waiting for your reply. 
I think is great
View more
  • x
  • convention:

well explained
View more
  • x
  • convention:

Comment

You need to log in to comment to the post Login | Register
Comment

Notice: To protect the legitimate rights and interests of you, the community, and third parties, do not release content that may bring legal risks to all parties, including but are not limited to the following:
  • Politically sensitive content
  • Content concerning pornography, gambling, and drug abuse
  • Content that may disclose or infringe upon others ' commercial secrets, intellectual properties, including trade marks, copyrights, and patents, and personal privacy
Do not share your account and password with others. All operations performed using your account will be regarded as your own actions and all consequences arising therefrom will be borne by you. For details, see " User Agreement."

My Followers

Login and enjoy all the member benefits

Login

Block
Are you sure to block this user?
Users on your blacklist cannot comment on your post,cannot mention you, cannot send you private messages.
Reminder
Please bind your phone number to obtain invitation bonus.