Support Forum
The Forums are a place to find answers on a range of Fortinet products from peers and product experts.
ys1
New Contributor

FortiManager - VPN Manager Tunnel ID

Hi ,

 

We are setting up a Hub and Spoke architecture, and Spoke to Spoke through the ADVPN (we have almost 100 remote sites), with 3 links for the SD WAN.

 

We used the FortiManager, and we created 3 community in dial up for the three links, on the other hand we just have a difficulty to put a name to the tunnel which is created with a random ID, suddenly we cannot associate them with SD-WAN interfaces.

 

How can we proceed please.

 

Thank you community.

3 REPLIES 3
scan888
Contributor

Hi @ys1 

Use normalized Interfaces in the VPN configuration.

You find this option in "VPN Manager->Edit VPN Community"

scan888_0-1673904942183.png

 

Afterwards you can use this normalized interface in the SD-WAN configuration.

- Have you found a solution? Then give your helper a "Like" and mark the solution.
- Have you found a solution? Then give your helper a "Like" and mark the solution.
ys1
New Contributor

Hi @scan888 ;

 

Thank you for your response,

 

we have already try this, but, when we use normalized "VPNZone" he create a zone interface, and note an SD WAN , our need is when the tunnel is created, he automatically associated to the SD WAN zone, and not an interface Zone.

 

Thank you for your support,

Faiza_Emam_Delhi
Contributor

you are encountering an issue with naming VPN tunnels in FortiManager when using ADVPN for Hub and Spoke architecture with SD-WAN. Specifically, you are having difficulty assigning a name to the VPN tunnel created with a random ID.

Here are some steps you can take to resolve this issue:

1. Verify that the VPN configuration on the FortiManager and FortiGate devices is correct. Make sure that the community settings, SD-WAN interface settings, and VPN settings are all configured correctly.

2. Check that the tunnel ID is unique and not shared with any other VPN tunnels. If there are multiple VPN tunnels with the same ID, it can cause issues with naming and associating the tunnels with SD-WAN interfaces.

3. Consider using a naming convention for the VPN tunnels that includes the community name, SD-WAN interface, and tunnel ID. This can help ensure that the VPN tunnels are named consistently and can be associated with the correct SD-WAN interfaces.

4. If you are still having difficulty assigning a name to the VPN tunnel, consider reaching out to Fortinet support for further assistance. They may be able to provide more specific guidance based on your specific situation.

By following these steps, you can resolve the issue with naming VPN tunnels in FortiManager when using ADVPN for Hub and Spoke architecture with SD-WAN.

Thanks & Regards,
Faizal Emam
Thanks & Regards,Faizal Emam
Top Kudoed Authors