I am currently in the process of deploying meraki devices in my network, but I am just trying to wrap my head around some concepts with the meraki MX devices.
2. With the MX Warm Spare configuration, i can't seem to understand how the VRRP worked on the LAN side, as i can't see a place to have the VIP configured, but from my research it says the secondary MX device would assume the IP of the primary MX, do i need to configure the secondary MX with a Physical IP?
3. Does the MX support Dynamic routing(OSPF) with the LAN device, so that I can have the connection between the Core switch and the MX device to be doing dynamic routing.
Solved! Go to Solution.
in simple terms it means the WAN port needs to be in thesame VLAN, so you need to find a way to split the interface, either with a dedicated breakout switch or using one of your network switch, in other to split the interface you have to have three interfaces in same broadcast domain(VLAN) and in thesame subnet " the internet circuit, WAN port on both the Active and Spare MX".
Got it, Thanks. This will make it a bit complex and if i do not want to do it this way i can just skip the VIP ? and configure warm spare without VIP if its possible ? Will get redundancy on WAN via meraki's WAN monitoring and on LAN through VRRP ? just wanting to confirm i have understood it correct.
You don't have to use a VIP on the WAN-side. Consequences of not using one are described here:
Use MX uplink IPs: When using this option, the current Active MX will use its distinct uplink IP or IPs when sending traffic out to the Internet. This option does not require additional public IPs for Internet-facing MXs, but also results in more disruptive failover because the source IP of outbound flows will change.
Use virtual uplink IPs: When using this option, both MXs will use a shared virtual IP (VIP) when sending traffic out to the Internet. This option requires an additional public IP per uplink but allows for seamless failover because the IP address the network is using to communicate with the Internet will be consistent. The VIP for each uplink must be in the same subnet as the IPs of the MXs themselves for that uplink, and the VIP must be different from both MX uplink IPs.
To configure a new network with warm spare failover, create the network as you would normally and add the Primary MX. Then add the Secondary MX using the process described above.
Regardless of which option is selected, both MX devices will need their own uplink IP addresses for Dashboard connectivity.
Dashboard configuration should always be performed before the Secondary MX is physically connected to the network.
On the LAN side no VIPs are needed either. The process is described more in detail here:
will this suggestion also work without problems - when I´ve 2 ISPs?
ISP 1 ISP 2
if yes, is there anything to keep in mind according the physical cabling?
Yes, as long as you are only using the stack for internet connection splitting and they are not in the same 'network' as the MXs.
I use basic 5 port layer2 switches to split the ISP connections and keep the MSs for the internal network.
Also remember that you need 2-3 IP addresses for each ISP
""Yes, as long as you are only using the stack for internet connection splitting and they are not in the same 'network' as the MXs. ""
If you have the switches split to both be external and internal then you have two issues