Load balancing with Client/AnyConnect VPN

[SteveDW]

Hello all, I currently have Client VPN and AnyConnect VPN working great with two stacked MX250s with a WAN1 and WAN2 circuit. I discovered that when activating load balancing with WAN1 and WAN2, the VPN connection on the client computer has proven to be unreliable with random results. The traffic will randomly go through either WAN1 or WAN2. Thus, this changes the IP address on the client. In addition, I discovered the DDNS assigned name xxxxx.dynamic-m.com keeps changing the IP addresses between the two WAN ports.

I have researched a bit on the Meraki MX device and discovered there is a "SD-WAN policies" section that includes a "VPN traffic" option. I suspect that if I "add a preference" and choose "load balance" for a certain "performance class," this may resolve the problem. Is this correct? If not, can you please provide some insight on this?

Please let me know if I need to clarify this further. I really appreciate any input. Thanks in advance.

[RaphaelL · Accepted solution]

That's correct. This documentation covers some topics that you are searching : https://documentation.meraki.com/MX/Firewall_and_Traffic_Shaping/MX_Load_Balancing_and_Flow_Preferen...

[SteveDW]

Thank you so much. I appreciate the feedback!

[PhilipDAth]

>In addition, I discovered the DDNS assigned name xxxxx.dynamic-m.com keeps changing the IP addresses between the two WAN ports.

This should ONLY happen if the primary WAN interface goes down - and in no other case.  AnyConnect clients terminating on an MX do no load balance across the WAN ports.

I think you might have a bug in the firmware version you are using.  I would try upgrading to the latest stable release, ot the latest in the release train you are already using.