Hi Everyone,   I hope this message finds you well. This is my inaugural post, and I am seeking guidance on implementing a resilient network for a mini data center. Currently, we have one MX at the location connected to satellite sites via auto site-to-site VPN. Below is the network diagram I've planned to implement, and I would appreciate feedback on its suitability for our requirements and any potential challenges.   HW/ISP Resiliency To ensure hardware and ISP resiliency, two MX devices will be deployed, each connecting to a different ISP. Can both MX units function together to balance the load and provide High Availability (HA)? If so, how will the licensing work? Site-to-Site VPN How would site-to-site VPN function when we have two MX devices? DHCP Service With two MX units, how will the DHCP service work? What happens if the MX responsible for DHCP fails? VLAN Configuration Do I need to create the same VLANs on both MX units and Layer 3 switches? Understanding and Confirmation If we have Layer 3 switches capable of inter-VLAN routing and the same VLANs configured on both the L3 switches and the Meraki MXs, is it accurate to state that traffic between different VLANs on the same switch generally doesn't need to traverse the Meraki MX devices? Local VLAN Communication on L3 Switch - Traffic within the same VLAN on the L3 switch remains local, utilizing the Layer 3 functionality of the switch for routing between devices in different subnets/VLANs on the switch itself. Inter-VLAN Routing on L3 Switch - If devices in different VLANs on the L3 switch need to communicate, the Layer 3 switch can internally route the traffic between VLANs without involving the Meraki MXs. Internet-bound Traffic - When a device in one of the VLANs needs internet access, the Layer 3 switch routes the traffic to the Meraki MX, serving as the gateway. The MX handles NAT and forwards the traffic to the ISP. I would greatly appreciate any insights, recommendations, or corrections you can provide.               ... View more