How do you setup an active active HA configuration at the branch with two internet access circuits?
Solved! Go to solution.
If you mean load balancing between the two internet circuits check the link:
If you mean active-active HA configuration using two MX's, you can't Meraki doesn't support active-active HA, only warm spare. Recommended topologies can be seen here:
https://documentation.meraki.com/MX/Deployment_Guides/MX_Warm_Spare_-_High_Availability_Pair
If you mean load balancing between the two internet circuits check the link:
If you mean active-active HA configuration using two MX's, you can't Meraki doesn't support active-active HA, only warm spare. Recommended topologies can be seen here:
https://documentation.meraki.com/MX/Deployment_Guides/MX_Warm_Spare_-_High_Availability_Pair
does meraki MX support routing protocol on the LAN side, BGP, OSPF?
does meraki mx supports routing protocol on the LAN side (BGP, OSPF)?
@Cminott wrote:does meraki mx supports routing protocol on the LAN side (BGP, OSPF)?
It supports OSPF on the LAN-side, it only advertises the subnets available through AutoVPN. So it's not full blown OSPF support. It can't learn routes, and I don't think it advertises anything towards the WAN side either:
https://documentation.meraki.com/MX/Site-to-site_VPN/Using_OSPF_to_Advertise_Remote_VPN_Subnets
Pretty sure the same is true for it's BGP support that is in beta at the moment (so you need to contact helpdesk to have it activated). More info here:
https://documentation.meraki.com/MX/Networks_and_Routing/BGP
For BGP, you can advertise your LAN subnet, such as a connected network through EBGP between peers.
For example;
<Your L3 Core switch>
router bgp 64555 <--Your DC AS number
bgp log-neighbor-changes
neighbor 192.168.19.52 remote-as 64512 <--Meraki iBGP
neighbor 192.168.19.52 timers 60 180
!
address-family ipv4
redistribute connected route-map SERVER_CONNECTED
neighbor 192.168.19.52 activate
neighbor 192.168.19.52 soft-reconfiguration inbound
exit-address-family
route-map SERVER_CONNECTED permit 10
match ip address prefix-list SERVER_SUBNET
ip prefix-list SERVER_SUBNET seq 5 permit 192.168.132.0/24
DC2-SW1#show ip route conn
Gateway of last resort is 192.168.19.41 to network 0.0.0.0
C 192.168.132.0/24 is directly connected, Vlan503
L 192.168.132.1/32 is directly connected, Vlan503