Wireless Access

Reply
Frequent Contributor I
Posts: 82
Registered: ‎05-28-2010

VRRP best practices

When configuring VRRP parameters between an active and stand-by controller, should Enable Router Pre-emption be checked on on both controllers or just the one that that will have the higher priority value (i.e. the controller that we would want to be the active one at all time)? Should the Delay field be left blank or is there a best practice parameter for that as well?

 

Regards,

Tony Marques

Aruba
Posts: 1,368
Registered: ‎12-12-2011

Re: VRRP best practices

If you are running 6.3.1 or above, please consider our AP fast faliover OVER VRRP for AP redundancy.  

 

For the preemption question, it should be checked on both to prevent a "flappoing" issue on either end.

Seth R. Fiermonti
Consulting Systems Engineer - ACCX, ACDX, ACMX
Email: seth@hpe.com
-----
If you found my post helpful, please give kudos
Contributor II
Posts: 48
Registered: ‎05-14-2012

Re: VRRP best practices

[ Edited ]

Did you want to mean "unchecked"? VRD guide says for master/standby, it should be unchecked.

Guru Elite
Posts: 20,822
Registered: ‎03-29-2007

Re: VRRP best practices


tmarques wrote:

When configuring VRRP parameters between an active and stand-by controller, should Enable Router Pre-emption be checked on on both controllers or just the one that that will have the higher priority value (i.e. the controller that we would want to be the active one at all time)? Should the Delay field be left blank or is there a best practice parameter for that as well?

 

Regards,

Tony Marques


tmarques,

 

Please see the Wikipedia entry for VRRP here for answers to all of your questions about VRRP:  http://en.wikipedia.org/wiki/Virtual_Router_Redundancy_Protocol

 

To directly answer your question, you would Enable Router pre-emption on one side of a VRRP if you want a controller that has a higher VRRP priority when it comes up to always take control of a VRRP from a controller with lesser priority.  If it is NOT enabled, when a controller  is coming up, it will NOT take control of a VRRP when it sees another controller advertising that it is master for that VRRP, even if it has priority.

 

There is no best design practice for the delay parameter:  Accept the default.   "This feature prevents unnecessary transitions of VRRP State to MASTER.  By adding a delay to the master transition, we prevent a router from becoming the master during network flapping. For a short interval, there may be congestion in the network, or links may be flapping. This should not cause VRRP MASTER to be altered. "  It works just fine with the default.  A number of administrators have their reasons for editing this parameter, but for most, the default works just fine



Colin Joseph
Aruba Customer Engineering

Looking for an Answer? Search the Community Knowledge Base Here: Community Knowledge Base

Guru Elite
Posts: 20,822
Registered: ‎03-29-2007

Re: VRRP best practices

[ Edited ]

ado75 wrote:

Did you want to mean "unchecked"? VRD guide says for master/standby, it should be unchecked.


Ado,

 

It is a design choice by the administrator whether it should be unchecked or not.  There really is no right or wrong answer.



Colin Joseph
Aruba Customer Engineering

Looking for an Answer? Search the Community Knowledge Base Here: Community Knowledge Base

Search Airheads
Showing results for 
Search instead for 
Did you mean: