Home > Switches > Layer 3 Switching > MS Warm Spare (VRRP) Overview

MS Warm Spare (VRRP) Overview

MS Series switches configured for layer 3 routing can also be configured with a warm spare for gateway redundancy. This allows two identical switches to be configured as redundant gateways for a given subnet, thus increasing network reliability for users.  Warm spare is currently available on the MS250, MS320, MS42, and MS400 series family of switches.

Enabling Warm Spare

Warm Spare and OSPF cannot operate simultaneously.

  1. Layer 3 switching must be initialized before configuring warm spare.  To enable L3 switching, follow the instructions in the Layer 3 Switching Overview.
  2. To enable warm spare, navigate to Configure > Routing and DHCP in the Meraki Dashboard.
  3. Scroll to the "Warm Spares" section of the page and select "Add a new warm spare".
  4. You will be prompted to choose both a "Primary" and "Spare" switch.

    All active L3 interfaces and routing functions on the "Spare" switch will be over-written with the L3 configuration of the selected primary switch.

  1. Once you have selected the desired pair, choose "Save".

How Warm Spare Works

Warm Spare is built on VRRP to provide clients with a consistent gateway. The switch pair will share a virtual MAC address and IP address for each layer 3 interface. The MAC address will always begin with 00-00-5E-00-01, and the IP address will always be the configured interface IP address on the primary. Clients will always use this virtual IP and MAC address to communicate with their gateway.

 

 

When configured, the primary switch will send out VRRP advertisements on each layer 3 (L3) interface every 0.3 seconds. These advertisements will include the L3 switch's priority, configured addresses, and are used to ensure the spare/backup remains aware that the primary is online. When operating normally, the spare will act only as a layer 2 switch, and not perform any routing. All routing functionality will be performed by the primary.

 

In the event of a failure, such as the primary losing power, the spare will wait for 3 missed advertisements before it assumes the role of primary. When this occurs, the spare will assume ownership of the virtual IP/MAC addresses and begin performing routing functions. Thus there may about 1 second of downtime before the spare is able to take over for a failed primary. Clients will continue to send traffic to the same IP address, and virtual MAC address, as both of these will be shifted from the primary to the spare.

 

Once the primary comes back online, it will assume control again, and the spare will return to its previous state.

Important Notes

While the setup and operation of Warm Spare is generally simple and seamless, there are some pieces of information that become important when troubleshooting or planning. 

Timers

On Cisco Meraki MS Series switches, the following VRRP timers apply:

  • Advertisement/hello timer - 0.3 seconds
  • Hold timer - 0.9 seconds (3 missed advertisements)
  • Preempt delay - Preempt will occur once the configured primary is fully initialized

Priority

The primary will use a priority of 255, and the spare/backup will use a priority of 100.

Interoperability

At this time Cisco Meraki MS Series switches can only be configured in pairs from the same family when using VRRP/Warm Spare. Integration with other vendors or platforms is currently not supported.

Ex. An MS250 can only be paired with another MS250.

Exception: MS320 and MS42 can be in a VRRP/Warm Spare pair.

Settings When Adding a Spare

When adding a warm spare, any previously configured layer 3 settings for the spare will be lost, and the configuration from the primary will be assumed. If this switch is later removed from the pair, it will not regain its original settings.

Management IP

When configuring VRRP/warm spare, the management IP address on the primary cannot also be assigned to a layer 3 interface. This is due to the interface IP address being shifted to the spare in the event of a failover. Thus both the primary and spare must have unique management IP addresses for communication with Dashboard, that do not conflict with the layer 3 interface IP addresses.

 

You must to post a comment.
Last modified
12:51, 27 Feb 2017

Tags

Classifications

This page has no classifications.

Article ID

ID: 1128

Contact Support

Most questions can be answered by reviewing our documentation, but if you need more help, Cisco Meraki Support is ready to work with you.

Open a Case