Thanks everyone for the help.
Issue was that there was already a NAT rule for 4500 for other internal Ip address.
After I removed this rule and pointed it to the correct IP of the virtual gateway it worked like a charm.
Now the tunnels are up. :)
Thanks for the confirmation that it was a NAT issue and it should work.
I know not ideal, but it's a lab setup.
Original Message:
Sent: Jul 08, 2024 03:21 AM
From: OK96
Subject: Tunnel between VPNC & branch gateway
When udp 4500 is checked,
Did you add routing of traffic into the tunnel?
Also check Alerts and Events on the gateways from the left menu.
Check individual gateway vpn logs in Global>Network Services.
Check fw logs on the gateways, Device>Overview>Sessions tab.
Branch Gateway Group > Config > Routing > Overlay routing.
Normally redistribute connected vlans.
Similar on the VPNC group
Config > Routing > Overlay routing.
------------------------------
Ole Morten Kårbø
ACP - Campus Access Professional
ACEA | ACSP | APS CX10000 | APS Central | APS SD-Branch
Netnordic Norway
Original Message:
Sent: Jun 26, 2024 08:47 AM
From: EnzoJ
Subject: Tunnel between VPNC & branch gateway
Hi,
For my test-lab I want to create a tunnel between the Virtual Gateway (VPNC) in a datacenter and a physical gateway in my home setup.
I got experience in the Silverpeak/edgeconnect setup, so SD-wan at his own isn't new for me.
I want to have more expierence in the SD-branch portofolio.
But the VPNC concentrator is behind a router/modem of the ISP so NAT is being performed.
I'm aware that's not ideal, but want to know if that is the issue.
The Branch gateway at home has a public IP via PPPoE authentication, so no natting.
What I see in the aruba central is that he discovered the public IP of both nodes.
And want to setup the tunnel, but never comes up.
I see both the correct uplinks on both devices in central.
I enabled overlay mode Orchestrated & peering enabled but the correct hub selected.
What I'm doing wrong and how can I troubleshoot this?