Local ID configurations for Non Meraki VPN peers

Here to help

Local ID configurations for Non Meraki VPN peers



As also mentioned in another discussion thread, V1 Dashboard API does not support a payload that provides local id information (which is ignored). So when configuring a VPN peer with IKEv2, will the MX device use the IPv4 address associated with the local end point in establishing the connection? 




3 Replies 3
Kind of a big deal
Kind of a big deal

@ksridhar : 



Cisco IT Blogs awarded in 2020 & 2021

The documentation does not mention anything about the local ID and how that is handled if it is not provided in the configuration. Hence wanted to know what the behaviour would be or specifically if there is any implicit use of IPv4 address by MX devices when establishing VPN connectivity to third party peers. 

Here to help

I'm not sure what the MX would use but previously we have just manually entered the Local ID after creating the VPN via the API. I would also be interested if there is a standard value that Meraki uses or if the VPN tunnel just wouldn't be established until the Local ID is entered manually.

Get notified when there are additional replies to this discussion.
Welcome to the Meraki Community!
To start contributing, simply sign in with your Cisco account. If you don't yet have a Cisco account, you can sign up.