Seven years ago (On a night much like tonight)   In -someone's- first year managing Cisco routers, after only having a few months of Brocade exposure, -someone- learned how not to remove an interface from an OSPF area...  -someone- also learned that commit confirm exists in IOS-XR !   router ospf 100  area 0   no interface tengige0/0/0/1    passive enable end y   The look of fear swept across their face (A face much like my own)   15 minutes later without remote management access -someone- realized that -someone- didn't delete "passive enable" from the syntax before -someone- pasted it in...well, time to go console in for management now!  Hopefully the network will survive until -someone- gets there.   ... View more

If it were failover were to occur when 1 VLAN goes down, I would be ok with this "all-or-nothing" scenario.  But if it is -all- VLANs have to stop responding before a failover, I may have to reassess.   What is concerning to me is the following quote from documentation.  Do I read this as "any VLAN" meaning any one or as all?  Immediately my brain reads it as all VLANs have to fail before a failover even occurs.  But I can also convince myself that a failover will occur if any one fails.   (https://documentation.meraki.com/MX/Deployment_Guides/MX_Warm_Spare_-_High_Availability_Pair).  I know I could also manually force failover if needed.   "LAN failover:  The two appliances share health information over the network via the VRRP protocol. These VRRP heartbeats occur at layer two and are performed on all configured VLANs. If no advertisements reach the spare on any VLAN, it will trigger a failover. When the warm spare begins receiving VRRP heartbeats again, it will relinquish the active role back to the primary appliance." ... View more