VPN connection failed.

[DavidCameron]

Hey,

I made an adjustment to a firewall that I had setup as a HUB in my S2S environment.
The firewall, initially unused, had its hostname changed, leading to widespread VPN issues. Despite verifying DNS and RADIUS settings, problems persisted. Transitioning it from HUB to SPOKE resolved one HUB's issue, but not the other. Removing the non-functioning HUB from the SPOKE list fixed the problem. Currently configured as SPOKE, seeking guidance on reverting to HUB status or using the old hostname.

I would also like to know how this could have happened where changing the hostname of this firewall would drop all other HUBS and deny VPN connections

Thanks.

paybyplatema

[alemabrahao]

Look, I think it's a little difficult that simply changing the name would make the environment inoperative.

I suggest you open a support case for them to investigate.

[PhilipDAth]

Is this using AutoVPN or non-Meraki VPN?

If this is AutoVPN - the most common issue for this occurs when the Hub MX does not have a public IP address directly on its WAN interface and sites behind something doing NAT.  Is this your case?
If it is sitting behind something doing NAT, then enable manual NAT traversal and it will become 100% rock solid reliable.