Hi,   When configuring Non-Meraki VPN peers it is mandated to provide the private subnets which are essentially the subnets behind the third party VPN device. There is this option to provide a default route too using 0.0.0.0/0. However when this is configured, I see this message -    "The local subnet x.x.x.x/x overlaps with a remote VPN subnet on the non-Meraki peer <peer name> (0.0.0.0/0). IP traffic will be routed to the smallest subnet that contains the IP address."    As I understand this, the smallest prefix will always be used over the default route when traffic is designated to an IP address in the "local subnet". All other traffic will still be routed via this VPN tunnel including any internet bound traffic. Is my understanding correct?    Also, if the tunnel goes down, does it mean that all other MX devices other than the Z series devices will automatically fail over to the underlay connection or the direct WAN connectivity?    Thanks, Krishna ... View more

Hi,   Can anyone help me find the API that I could use to list the available subnets in a given network that have the VPN mode enabled?    Thanks!  ... View more

Hi,   Can someone help me understand what would the default/implicit behaviour be when Local ID is not specified when configuring a Non Meraki VPN peer? As I understand when using the V1 APIs there is currently no support to provide the Local ID configuration. So in this case how is the identification of individual VPN links be done? I did read in some online resources that other Cisco appliances were capable of using local IPv4 addresses of the interface if Local IDs are not specified. Is this true with the Meraki SD-WAN appliance too? If so is the IP address used the public IP or the private IP address of the WAN port?    Thanks! ... View more

Hi,   It seems that the only way to run any CRUD operations via APIs on Non-Meraki VPN peer resources, is to first retrieve the existing list of peers and then update the list with the needed updates and push the entire list back. I was wanting to know if such operations would cause existing VPN connections to be torn down and brought up once again even if those specific configurations were not changed in any way.    Thanks! ... View more

Hi,   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?    Thanks, Krishna ... View more

Hi,   I would like to know if the Meraki SD-WAN solution provided with MX appliances support integration with 3rd party firewall services hosted in cloud environments.    Thanks, Krishna ... View more