Re: [VRRP] vrrp Digest, Vol 81, Issue 3

Thirumavalavan Periyannan <tperiyannan@extremenetworks.com> Fri, 22 February 2013 17:41 UTC

Return-Path: <tperiyannan@extremenetworks.com>
X-Original-To: vrrp@ietfa.amsl.com
Delivered-To: vrrp@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4707921F8E4A for <vrrp@ietfa.amsl.com>; Fri, 22 Feb 2013 09:41:06 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level:
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id M1Uly7csMT8z for <vrrp@ietfa.amsl.com>; Fri, 22 Feb 2013 09:41:04 -0800 (PST)
Received: from ussc-casht-p1.extremenetworks.com (ussc-casht-p1.extremenetworks.com [207.179.9.62]) by ietfa.amsl.com (Postfix) with ESMTP id 6F91A21F8E3A for <vrrp@ietf.org>; Fri, 22 Feb 2013 09:41:04 -0800 (PST)
Received: from inch-casht-p1.corp.extremenetworks.com (10.120.89.28) by ussc-casht-p1.corp.extremenetworks.com (10.0.4.73) with Microsoft SMTP Server (TLS) id 8.3.297.1; Fri, 22 Feb 2013 09:41:04 -0800
Received: from INEXCHANGE.corp.extremenetworks.com ([192.168.131.111]) by inch-casht-p1.corp.extremenetworks.com ([10.120.89.28]) with mapi; Fri, 22 Feb 2013 23:11:00 +0530
From: Thirumavalavan Periyannan <tperiyannan@extremenetworks.com>
To: "Anurag Kothari (ankothar)" <ankothar@cisco.com>
Date: Fri, 22 Feb 2013 23:10:54 +0530
Thread-Topic: [VRRP] vrrp Digest, Vol 81, Issue 3
Thread-Index: Ac4RI8Z8FN8e4KHYQ92R/65MDP3rdQ==
Message-ID: <91BD27DC-D555-49C7-8B40-F74F4D8B596F@extremenetworks.com>
References: <mailman.7259.1361533310.3383.vrrp@ietf.org> <14CA6619-DB7C-40ED-85E4-535CB689AC86@extremenetworks.com> <A2BB90B33FFDF740876C5AAE307D83DB1C292B8C@xmb-rcd-x05.cisco.com> <F547EC1D-C8F0-4468-AFB9-CC1115833704@gmail.com> <A2BB90B33FFDF740876C5AAE307D83DB1C292D70@xmb-rcd-x05.cisco.com>
In-Reply-To: <A2BB90B33FFDF740876C5AAE307D83DB1C292D70@xmb-rcd-x05.cisco.com>
Accept-Language: en-US
Content-Language: en-GB
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "vrrp@ietf.org" <vrrp@ietf.org>
Subject: Re: [VRRP] vrrp Digest, Vol 81, Issue 3
X-BeenThere: vrrp@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Virtual Router Redundancy Protocol <vrrp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/vrrp>, <mailto:vrrp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/vrrp>
List-Post: <mailto:vrrp@ietf.org>
List-Help: <mailto:vrrp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/vrrp>, <mailto:vrrp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 22 Feb 2013 17:41:06 -0000

Hi Anurag,

If customer wants to do any maintenance work then they can do "disable vrrp" on MASTER Router which will generate VRRP Advertisement with "priority 0" and one among the backup router will become master based on the priority or higher interface IP addres.


Sent from my iPhone

On 22-Feb-2013, at 10:59 PM, "Anurag Kothari (ankothar)" <ankothar@cisco.com>; wrote:

> Hi Peter
>
> Please See my responses inline [Anurag]
>
> Thanks
> -Anurag
>
> -----Original Message-----
> From: Peter Hunt [mailto:pfhunt@gmail.com]
> Sent: Friday, February 22, 2013 11:59 AM
> To: Anurag Kothari (ankothar)
> Cc: Thirumavalavan Periyannan; vrrp@ietf.org
> Subject: Re: [VRRP] vrrp Digest, Vol 81, Issue 3
>
> Sorry to jump in here, but I'm having trouble understanding the motivation for the maintenance event.
>
> It seems like its behaviour is to relinquish mastership immediately to a backup if it exists, but remain master silently otherwise. Is that correct?
>
> [Anurag] The master will not remain silent it will keep sending Advertisements with Priority = 0 until some backup router takes over as Master.
>
> If so, why is that desirable behaviour? It seems to me that you would either want to take the node out of the vrrp cluster completely, or have it participate at a reduced priority. What situation makes a silent-but-active master preferable?
>
> [Anurag] Many mobile service providers disable preemption for VRRP as they do not like the idea of unplanned traffic switch when a router with higher priority comes up. They only want traffic to switch in the event of a failure or as part of a planned activity in a maintenance window.
> Now here is an example: A site has PE1 and PE2 configured to backup each other. Now if I want to perform any maintenance work on the say PE1 (Code upgrade / HW upgrade etc.) I want to take it out of the traffic path gracefully. Now the only way to Gracefully failover the traffic to PE2 is to configure preemption on it and reduce the priority on PE1 (or increase it on PE2) and remove it at the end of the maintenance work. But most service providers do not like the idea of touching (making changes to configuration) on both the boxes within the same maintenance window. So the idea here is to be able to failover the traffic to the backup router without enabling preemption on the Backup router.  If the backup router exists it will take over immediately if it doesn't exist the existing Master will continue to provide service. A lack of failover will indicate to the operator that backup is missing / not working and he will have to troubleshoot the situation.
>
> Peter
>
>
> On Feb 22, 2013, at 7:55 AM, "Anurag Kothari (ankothar)" <ankothar@cisco.com>; wrote:
>
>> Yes that is correct.
>>
>> The intention is to be able to switch the traffic to the backup router (with minimal traffic interruption) when preemption is not configured on the backup router without shutting down the interface or VRRP on Master.
>>
>> Thanks
>> ~Anurag
>>
>> -----Original Message-----
>> From: vrrp-bounces@ietf.org [mailto:vrrp-bounces@ietf.org] On Behalf
>> Of Thirumavalavan Periyannan
>> Sent: Friday, February 22, 2013 8:56 AM
>> To: vrrp@ietf.org
>> Cc: vrrp@ietf.org
>> Subject: Re: [VRRP] vrrp Digest, Vol 81, Issue 3
>>
>> Hi Anurag,
>>
>> You meant to say that when we do graceful failover on VRRP Master then traffic needs switch to VRRP backup router without waiting for Master_Down_Interval time.
>>
>> Please correct me if I am wrong.
>>
>> Sent from my iPhone
>>
>> On 22-Feb-2013, at 5:11 PM, "vrrp-request@ietf.org"; <vrrp-request@ietf.org>; wrote:
>>
>>> If you have received this digest without all the individual message
>>> attachments you will need to update your digest options in your list
>>> subscription.  To do so, go to
>>>
>>> https://www.ietf.org/mailman/listinfo/vrrp
>>>
>>> Click the 'Unsubscribe or edit options' button, log in, and set "Get
>>> MIME or Plain Text Digests?" to MIME.  You can set this option
>>> globally for all the list digests you receive at this point.
>>>
>>>
>>>
>>> Send vrrp mailing list submissions to
>>>      vrrp@ietf.org
>>>
>>> To subscribe or unsubscribe via the World Wide Web, visit
>>>      https://www.ietf.org/mailman/listinfo/vrrp
>>> or, via email, send a message with subject or body 'help' to
>>>      vrrp-request@ietf.org
>>>
>>> You can reach the person managing the list at
>>>      vrrp-owner@ietf.org
>>>
>>> When replying, please edit your Subject line so it is more specific
>>> than "Re: Contents of vrrp digest..."
>>>
>>>
>>> Today's Topics:
>>>
>>> 1. Re: Proposal for Maintenance Event for VRRP [RFC-5798]
>>> (sreenatha)  2. Re: Proposal for Maintenance Event for VRRP [RFC-5798]
>>>    (Anurag Kothari (ankothar))
>>>
>>>
>>> ---------------------------------------------------------------------
>>> -
>>>
>>> Message: 1
>>> Date: Fri, 22 Feb 2013 09:55:35 +0530
>>> From: sreenatha <sreenatha.setty@ibtechnology.com>;
>>> To: "Anurag Kothari (ankothar)" <ankothar@cisco.com>;
>>> Cc: "vrrp@ietf.org"; <vrrp@ietf.org>;
>>> Subject: Re: [VRRP] Proposal for Maintenance Event for VRRP
>>> [RFC-5798]
>>> Message-ID: <5126F33F.1080005@ibtechnology.com>;
>>> Content-Type: text/plain; charset="iso-8859-1"; Format="flowed"
>>>
>>> Hi Anurag,
>>>  Your proposal is:
>>>
>>> - If a Maintenance event is received, then:
>>>
>>> + Cancel the Adver_Timer
>>>
>>> + Send an ADVERTISEMENT with Priority = 0
>>>
>>> -endif // maintenance recv
>>>
>>>
>>>   And you mentioned that router need to send regular ADVERTISEMENT message till it receives the ADVERTISEMENT message from the backup router.
>>>
>>> "2. How much time Master router should wait to receive ADVERTISEMENT message from any backup router?
>>>
>>> [Anurag] Master doesn't have to wait. After receiving the maintenance event it will send regular ADVERTISEMENT with Priority = 0 till some other router send back an ADVERTISEMENT message at which point it will transition to Backup."
>>>
>>> If Advert_Timer is cancelled, how regular ADVERTISEMENT messages are sent?
>>>
>>> So i am suggesting slight changes in the Proposal:
>>>
>>> - If a Maintenance event is received, then:
>>>
>>> + Change the router priority to 0
>>>
>>> + Send an ADVERTISEMENT with Priority = 0
>>>
>>> + Reset the Adver_Timer
>>>
>>> -endif // maintenance recv
>>>
>>> This will ensure that:
>>> 1. ADVERTISEMENT message with priority 0 is sent  immediately on receiving Maintenance event.
>>> 2. Master router will send regular Advertisement message till it receives the ADVERTISEMENT message from any backup routers.
>>>
>>> Thanks,
>>> Sreenatha Setty
>>>
>>>
>>>
>>>
>>> On 02/21/2013 10:12 PM, Anurag Kothari (ankothar) wrote:
>>>> Hi Sreenatha
>>>>
>>>> This ideas is based on the way the priority is defined in Section 5.2.4. and 6.1. of RFC-5798.
>>>>
>>>> "
>>>>  The priority value zero (0) has special meaning, indicating that the
>>>>  current Master has stopped participating in VRRP.  This is used to
>>>>  trigger Backup routers to quickly transition to Master without having
>>>>  to wait for the current Master to time out.
>>>> "
>>>>
>>>> "
>>>>  Priority              <snip>  The value of 0 (zero) is
>>>>                              reserved for the Master router to
>>>>                              indicate it is releasing responsibility
>>>>                              for the virtual router.  The range 1-254
>>>>                              (decimal) is available for VRRP routers
>>>>                              backing up the virtual router. <snip>
>>>> "
>>>>
>>>> Please see my responses inline [Anurag]:
>>>>
>>>> Thanks
>>>> -Anurag
>>>>
>>>> -----Original Message-----
>>>> From: vrrp-bounces@ietf.org [mailto:vrrp-bounces@ietf.org] On Behalf
>>>> Of sreenatha
>>>> Sent: Thursday, February 21, 2013 11:03 AM
>>>> To: vrrp@ietf.org
>>>> Subject: Re: [VRRP] Proposal for Maintenance Event for VRRP
>>>> [RFC-5798]
>>>>
>>>> Hi Anurag,
>>>>    Proposed idea is good. I have some queries on this proposal:
>>>>
>>>> 1. On receiving new maintenance_event, priority of the router is not changed, right? So if back-up router has less priority, even if Master receives the ADVERTISEMENT from the backup router, Master will discard.
>>>> So how the Master router state is going to change?
>>>>
>>>> [Anurag] On receiving the maintenance event the priority of router (or VRID) will change to 0.
>>>>
>>>> 2. How much time Master router should wait to receive ADVERTISEMENT message from any backup router?
>>>>
>>>> [Anurag] Master doesn't have to wait. After receiving the maintenance event it will send regular ADVERTISEMENT with Priority = 0 till some other router send back an ADVERTISEMENT message at which point it will transition to Backup.
>>>>
>>>> 3. Standard VRRP MIB(RFC-2787) does not allow user to configure '0' for VRRP Priority. So you are proposing to change this value also?
>>>>
>>>> [Anurag] Yes. Priority 0 will have to be made a user configurable value to indicate the intention of a router to relinquish Master Status.
>>>>
>>>> Thanks,
>>>> Sreenatha Setty
>>>>
>>>> On 02/21/2013 01:30 AM, vrrp-request@ietf.org wrote:
>>>>> If you have received this digest without all the individual message
>>>>> attachments you will need to update your digest options in your
>>>>> list subscription.  To do so, go to
>>>>>
>>>>> https://www.ietf.org/mailman/listinfo/vrrp
>>>>>
>>>>> Click the 'Unsubscribe or edit options' button, log in, and set
>>>>> "Get MIME or Plain Text Digests?" to MIME.  You can set this option
>>>>> globally for all the list digests you receive at this point.
>>>>>
>>>>>
>>>>>
>>>>> Send vrrp mailing list submissions to
>>>>>   vrrp@ietf.org
>>>>>
>>>>> To subscribe or unsubscribe via the World Wide Web, visit
>>>>>   https://www.ietf.org/mailman/listinfo/vrrp
>>>>> or, via email, send a message with subject or body 'help' to
>>>>>   vrrp-request@ietf.org
>>>>>
>>>>> You can reach the person managing the list at
>>>>>   vrrp-owner@ietf.org
>>>>>
>>>>> When replying, please edit your Subject line so it is more specific
>>>>> than "Re: Contents of vrrp digest..."
>>>>>
>>>>>
>>>>> Today's Topics:
>>>>>
>>>>>   1. Proposal for Maintenance Event for VRRP [RFC-5798]
>>>>>      (Anurag Kothari (ankothar))
>>>>>
>>>>>
>>>>> -------------------------------------------------------------------
>>>>> -
>>>>> --
>>>>>
>>>>> Message: 1
>>>>> Date: Tue, 19 Feb 2013 22:08:41 +0000
>>>>> From: "Anurag Kothari (ankothar)"<ankothar@cisco.com>;
>>>>> To:"vrrp@ietf.org"  <vrrp@ietf.org>;
>>>>> Subject: [VRRP] Proposal for Maintenance Event for VRRP [RFC-5798]
>>>>> Message-ID:
>>>>>   <A2BB90B33FFDF740876C5AAE307D83DB1C290327@xmb-rcd-x05.cisco.com>;
>>>>> Content-Type: text/plain; charset="us-ascii"
>>>>>
>>>>> Hi
>>>>>
>>>>> I want to propose a new Maintenance Event (modification of Shutdown Event) for VRRP (RFC-5798] which would allow to gracefully failover the VRRP Master to Redundant (Backup Router).
>>>>>
>>>>> Problem Statement:
>>>>> VRRP preemption is not configured on the redundant / backup router.
>>>>> How to initiate VRRP Traffic to failover to the redundant / backup
>>>>> router gracefully without modifying the configuration on the
>>>>> redundant / backup router (i.e. adding preemption)
>>>>>
>>>>> Proposed Solution:
>>>>> Addition to Section 6.4.3 of RFC-5798:
>>>>>
>>>>> - If a Maintenance event is received, then:
>>>>>
>>>>> + Cancel the Adver_Timer
>>>>>
>>>>> + Send an ADVERTISEMENT with Priority = 0
>>>>>
>>>>> -endif // maintenance recv
>>>>>
>>>>> Unlike Shutdown event the router will not "Transition to the {Initialize} state" and continue to be Master and forward traffic  till the backup router sends an ADVERTISEMENT (triggered by receiving an ADVERTISEMENT with Priority = 0) and becomes master.
>>>>> Here are couple of examples of how a maintenance event may be
>>>>> triggered
>>>>>
>>>>>
>>>>> 1)      By some user command e.g. "maintenance-mode" in the vrrp configuration.
>>>>>
>>>>> 2)      By setting the priority = 0 for a particular VRID.
>>>>>
>>>>> Thanks
>>>>> -Anurag
>>>>>
>>>>> -------------- next part -------------- An HTML attachment was
>>>>> scrubbed...
>>>>> URL:<http://www.ietf.org/mail-archive/web/vrrp/attachments/20130219
>>>>> /
>>>>> 36
>>>>> a6571f/attachment.htm>
>>>>>
>>>>> ------------------------------
>>>>>
>>>>> _______________________________________________
>>>>> vrrp mailing list
>>>>> vrrp@ietf.org
>>>>> https://www.ietf.org/mailman/listinfo/vrrp
>>>>>
>>>>>
>>>>> End of vrrp Digest, Vol 81, Issue 1
>>>>> ***********************************
>>>> Disclaimer :
>>>> This email communication may contain privileged and confidential information and is intended for the use of the addressee only.If you are not an intended recipient you are requested not to reproduce, copy disseminate or in any manner distribute this email communication as the same is strictly prohibited. If you have received this email in error, please notify the sender immediately by return e-mail and delete the communication sent in error. Email communications cannot be guaranteed to be secure & error free and IB Technology is not liable for any errors in the email communication or for the proper, timely and complete transmission thereof.
>>>>
>>>> _______________________________________________
>>>> vrrp mailing list
>>>> vrrp@ietf.org
>>>> https://www.ietf.org/mailman/listinfo/vrrp
>>>
>>> Disclaimer :
>>> This email communication may contain privileged and confidential information and is intended for the use of the addressee only.If you are not an intended recipient you are requested not to reproduce, copy disseminate or in any manner distribute this email communication as the same is strictly prohibited. If you have received this email in error, please notify the sender immediately by return e-mail and delete the communication sent in error. Email communications cannot be guaranteed to be secure & error free and IB Technology is not liable for any errors in the email communication or for the proper, timely and complete transmission thereof.
>>> -------------- next part -------------- An HTML attachment was
>>> scrubbed...
>>> URL:
>>> <http://www.ietf.org/mail-archive/web/vrrp/attachments/20130222/a56c0
>>> 7
>>> 14/attachment.htm>
>>>
>>> ------------------------------
>>>
>>> Message: 2
>>> Date: Fri, 22 Feb 2013 11:41:47 +0000
>>> From: "Anurag Kothari (ankothar)" <ankothar@cisco.com>;
>>> To: sreenatha <sreenatha.setty@ibtechnology.com>;
>>> Cc: "vrrp@ietf.org"; <vrrp@ietf.org>;
>>> Subject: Re: [VRRP] Proposal for Maintenance Event for VRRP
>>> [RFC-5798]
>>> Message-ID:
>>>
>>> <A2BB90B33FFDF740876C5AAE307D83DB1C292974@xmb-rcd-x05.cisco.com>;
>>> Content-Type: text/plain; charset="us-ascii"
>>>
>>> Hi Sreenatha
>>>
>>> My bad, by cancel I meant reset the timer.
>>>
>>> I would prefer defining maintenance event itself as (or being triggered by) priority being set to 0 for a VRID. So probably we can rephrase the proposal as:
>>>
>>>
>>> - If a Maintenance event is received, then:
>>>
>>>
>>>
>>> + Send an ADVERTISEMENT
>>>
>>>
>>>
>>> + Reset the Adver_Timer to Advertisement_Interval
>>>
>>>
>>>
>>> -endif // maintenance recv
>>>
>>> Thanks
>>> -Anurag
>>>
>>> From: sreenatha [mailto:sreenatha.setty@ibtechnology.com]
>>> Sent: Thursday, February 21, 2013 11:26 PM
>>> To: Anurag Kothari (ankothar)
>>> Cc: vrrp@ietf.org
>>> Subject: Re: [VRRP] Proposal for Maintenance Event for VRRP
>>> [RFC-5798]
>>>
>>> Hi Anurag,
>>> Your proposal is:
>>>
>>>
>>>
>>> - If a Maintenance event is received, then:
>>>
>>>
>>>
>>> + Cancel the Adver_Timer
>>>
>>>
>>>
>>> + Send an ADVERTISEMENT with Priority = 0
>>>
>>>
>>>
>>> -endif // maintenance recv
>>>
>>>
>>>
>>>
>>>
>>>  And you mentioned that router need to send regular ADVERTISEMENT message till it receives the ADVERTISEMENT message from the backup router.
>>>
>>>
>>>
>>> "2. How much time Master router should wait to receive ADVERTISEMENT message from any backup router?
>>>
>>>
>>>
>>> [Anurag] Master doesn't have to wait. After receiving the maintenance event it will send regular ADVERTISEMENT with Priority = 0 till some other router send back an ADVERTISEMENT message at which point it will transition to Backup."
>>>
>>>
>>>
>>> If Advert_Timer is cancelled, how regular ADVERTISEMENT messages are sent?
>>>
>>>
>>>
>>> So i am suggesting slight changes in the Proposal:
>>>
>>>
>>>
>>> - If a Maintenance event is received, then:
>>>
>>>
>>>
>>> + Change the router priority to 0
>>>
>>>
>>>
>>> + Send an ADVERTISEMENT with Priority = 0
>>>
>>>
>>>
>>> + Reset the Adver_Timer
>>>
>>>
>>>
>>> -endif // maintenance recv
>>>
>>>
>>>
>>> This will ensure that:
>>>
>>> 1. ADVERTISEMENT message with priority 0 is sent  immediately on receiving Maintenance event.
>>>
>>> 2. Master router will send regular Advertisement message till it receives the ADVERTISEMENT message from any backup routers.
>>>
>>>
>>>
>>> Thanks,
>>>
>>> Sreenatha Setty
>>>
>>>
>>>
>>>
>>>
>>>
>>> On 02/21/2013 10:12 PM, Anurag Kothari (ankothar) wrote:
>>>
>>> Hi Sreenatha
>>>
>>>
>>>
>>> This ideas is based on the way the priority is defined in Section 5.2.4. and 6.1. of RFC-5798.
>>>
>>>
>>>
>>> "
>>>
>>> The priority value zero (0) has special meaning, indicating that the
>>>
>>> current Master has stopped participating in VRRP.  This is used to
>>>
>>> trigger Backup routers to quickly transition to Master without
>>> having
>>>
>>> to wait for the current Master to time out.
>>>
>>> "
>>>
>>>
>>>
>>> "
>>>
>>> Priority              <snip>  The value of 0 (zero) is
>>>
>>>                             reserved for the Master router to
>>>
>>>                             indicate it is releasing responsibility
>>>
>>>                             for the virtual router.  The range 1-254
>>>
>>>                             (decimal) is available for VRRP routers
>>>
>>>                             backing up the virtual router. <snip>
>>>
>>> "
>>>
>>>
>>>
>>> Please see my responses inline [Anurag]:
>>>
>>>
>>>
>>> Thanks
>>>
>>> -Anurag
>>>
>>>
>>>
>>> -----Original Message-----
>>>
>>> From: vrrp-bounces@ietf.org<mailto:vrrp-bounces@ietf.org>
>>> [mailto:vrrp-bounces@ietf.org] On Behalf Of sreenatha
>>>
>>> Sent: Thursday, February 21, 2013 11:03 AM
>>>
>>> To: vrrp@ietf.org<mailto:vrrp@ietf.org>
>>>
>>> Subject: Re: [VRRP] Proposal for Maintenance Event for VRRP
>>> [RFC-5798]
>>>
>>>
>>>
>>> Hi Anurag,
>>>
>>>   Proposed idea is good. I have some queries on this proposal:
>>>
>>>
>>>
>>> 1. On receiving new maintenance_event, priority of the router is not changed, right? So if back-up router has less priority, even if Master receives the ADVERTISEMENT from the backup router, Master will discard.
>>>
>>> So how the Master router state is going to change?
>>>
>>>
>>>
>>> [Anurag] On receiving the maintenance event the priority of router (or VRID) will change to 0.
>>>
>>>
>>>
>>> 2. How much time Master router should wait to receive ADVERTISEMENT message from any backup router?
>>>
>>>
>>>
>>> [Anurag] Master doesn't have to wait. After receiving the maintenance event it will send regular ADVERTISEMENT with Priority = 0 till some other router send back an ADVERTISEMENT message at which point it will transition to Backup.
>>>
>>>
>>>
>>> 3. Standard VRRP MIB(RFC-2787) does not allow user to configure '0' for VRRP Priority. So you are proposing to change this value also?
>>>
>>>
>>>
>>> [Anurag] Yes. Priority 0 will have to be made a user configurable value to indicate the intention of a router to relinquish Master Status.
>>>
>>>
>>>
>>> Thanks,
>>>
>>> Sreenatha Setty
>>>
>>>
>>>
>>> On 02/21/2013 01:30 AM, vrrp-request@ietf.org<mailto:vrrp-request@ietf.org> wrote:
>>>
>>> If you have received this digest without all the individual message
>>>
>>> attachments you will need to update your digest options in your list
>>>
>>> subscription.  To do so, go to
>>>
>>>
>>>
>>> https://www.ietf.org/mailman/listinfo/vrrp
>>>
>>>
>>>
>>> Click the 'Unsubscribe or edit options' button, log in, and set "Get
>>>
>>> MIME or Plain Text Digests?" to MIME.  You can set this option
>>>
>>> globally for all the list digests you receive at this point.
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>> Send vrrp mailing list submissions to
>>>
>>> vrrp@ietf.org<mailto:vrrp@ietf.org>
>>>
>>>
>>>
>>> To subscribe or unsubscribe via the World Wide Web, visit
>>>
>>> https://www.ietf.org/mailman/listinfo/vrrp
>>>
>>> or, via email, send a message with subject or body 'help' to
>>>
>>> vrrp-request@ietf.org<mailto:vrrp-request@ietf.org>
>>>
>>>
>>>
>>> You can reach the person managing the list at
>>>
>>> vrrp-owner@ietf.org<mailto:vrrp-owner@ietf.org>
>>>
>>>
>>>
>>> When replying, please edit your Subject line so it is more specific
>>>
>>> than "Re: Contents of vrrp digest..."
>>>
>>>
>>>
>>>
>>>
>>> Today's Topics:
>>>
>>>
>>>
>>>  1. Proposal for Maintenance Event for VRRP [RFC-5798]
>>>
>>>     (Anurag Kothari (ankothar))
>>>
>>>
>>>
>>>
>>>
>>> ---------------------------------------------------------------------
>>> -
>>>
>>>
>>>
>>> Message: 1
>>>
>>> Date: Tue, 19 Feb 2013 22:08:41 +0000
>>>
>>> From: "Anurag Kothari
>>> (ankothar)"<ankothar@cisco.com><mailto:ankothar@cisco.com>
>>>
>>> To:"vrrp@ietf.org"<mailto:vrrp@ietf.org>
>>> <vrrp@ietf.org><mailto:vrrp@ietf.org>
>>>
>>> Subject: [VRRP] Proposal for Maintenance Event for VRRP [RFC-5798]
>>>
>>> Message-ID:
>>>
>>>
>>> <A2BB90B33FFDF740876C5AAE307D83DB1C290327@xmb-rcd-x05.cisco.com><mail
>>> t o:A2BB90B33FFDF740876C5AAE307D83DB1C290327@xmb-rcd-x05.cisco.com>
>>>
>>> Content-Type: text/plain; charset="us-ascii"
>>>
>>>
>>>
>>> Hi
>>>
>>>
>>>
>>> I want to propose a new Maintenance Event (modification of Shutdown Event) for VRRP (RFC-5798] which would allow to gracefully failover the VRRP Master to Redundant (Backup Router).
>>>
>>>
>>>
>>> Problem Statement:
>>>
>>> VRRP preemption is not configured on the redundant / backup router.
>>>
>>> How to initiate VRRP Traffic to failover to the redundant / backup
>>>
>>> router gracefully without modifying the configuration on the
>>> redundant
>>>
>>> / backup router (i.e. adding preemption)
>>>
>>>
>>>
>>> Proposed Solution:
>>>
>>> Addition to Section 6.4.3 of RFC-5798:
>>>
>>>
>>>
>>> - If a Maintenance event is received, then:
>>>
>>>
>>>
>>> + Cancel the Adver_Timer
>>>
>>>
>>>
>>> + Send an ADVERTISEMENT with Priority = 0
>>>
>>>
>>>
>>> -endif // maintenance recv
>>>
>>>
>>>
>>> Unlike Shutdown event the router will not "Transition to the {Initialize} state" and continue to be Master and forward traffic  till the backup router sends an ADVERTISEMENT (triggered by receiving an ADVERTISEMENT with Priority = 0) and becomes master.
>>
>>>
>>>
>>>
>>>
>>>
>>> Here are couple of examples of how a maintenance event may be
>>>
>>> triggered
>>>
>>>
>>>
>>>
>>>
>>> 1)      By some user command e.g. "maintenance-mode" in the vrrp configuration.
>>>
>>>
>>>
>>> 2)      By setting the priority = 0 for a particular VRID.
>>>
>>>
>>>
>>> Thanks
>>>
>>> -Anurag
>>>
>>>
>>>
>>> -------------- next part -------------- An HTML attachment was
>>>
>>> scrubbed...
>>>
>>> URL:<http://www.ietf.org/mail-archive/web/vrrp/attachments/20130219/3
>>> 6
>>> <http://www.ietf.org/mail-archive/web/vrrp/attachments/20130219/36a65
>>> 7
>>> 1f/attachment.htm>
>>>
>>> a6571f/attachment.htm><http://www.ietf.org/mail-archive/web/vrrp/atta
>>> c hments/20130219/36a6571f/attachment.htm>
>>>
>>>
>>>
>>> ------------------------------
>>>
>>>
>>>
>>> _______________________________________________
>>>
>>> vrrp mailing list
>>>
>>> vrrp@ietf.org<mailto:vrrp@ietf.org>
>>>
>>> https://www.ietf.org/mailman/listinfo/vrrp
>>>
>>>
>>>
>>>
>>>
>>> End of vrrp Digest, Vol 81, Issue 1
>>>
>>> ***********************************
>>>
>>>
>>>
>>>
>>>
>>> Disclaimer :
>>>
>>> This email communication may contain privileged and confidential information and is intended for the use of the addressee only.If you are not an intended recipient you are requested not to reproduce, copy disseminate or in any manner distribute this email communication as the same is strictly prohibited. If you have received this email in error, please notify the sender immediately by return e-mail and delete the communication sent in error. Email communications cannot be guaranteed to be secure & error free and IB Technology is not liable for any errors in the email communication or for the proper, timely and complete transmission thereof.
>>>
>>>
>>>
>>> _______________________________________________
>>>
>>> vrrp mailing list
>>>
>>> vrrp@ietf.org<mailto:vrrp@ietf.org>
>>>
>>> https://www.ietf.org/mailman/listinfo/vrrp
>>>
>>>
>>>
>>>
>>> Disclaimer :
>>> This email communication may contain privileged and confidential information and is intended for the use of the addressee only.If you are not an intended recipient you are requested not to reproduce, copy disseminate or in any manner distribute this email communication as the same is strictly prohibited. If you have received this email in error, please notify the sender immediately by return e-mail and delete the communication sent in error. Email communications cannot be guaranteed to be secure & error free and IB Technology is not liable for any errors in the email communication or for the proper, timely and complete transmission thereof.
>>> -------------- next part -------------- An HTML attachment was
>>> scrubbed...
>>> URL:
>>> <http://www.ietf.org/mail-archive/web/vrrp/attachments/20130222/cdd2c
>>> 4
>>> c7/attachment.htm>
>>>
>>> ------------------------------
>>>
>>> _______________________________________________
>>> vrrp mailing list
>>> vrrp@ietf.org
>>> https://www.ietf.org/mailman/listinfo/vrrp
>>>
>>>
>>> End of vrrp Digest, Vol 81, Issue 3
>>> ***********************************
>>
>> DISCLAIMER:
>> This e-mail and any attachments to it may contain confidential and proprietary material and is solely for the use of the intended recipient. Any review, use, disclosure, distribution or copying of this transmittal is prohibited except by or on behalf of the intended recipient.  If you have received this transmittal in error, please notify the sender and destroy this e-mail and any attachments and all copies, whether electronic or printed.
>> _______________________________________________
>> vrrp mailing list
>> vrrp@ietf.org
>> https://www.ietf.org/mailman/listinfo/vrrp
>> _______________________________________________
>> vrrp mailing list
>> vrrp@ietf.org
>> https://www.ietf.org/mailman/listinfo/vrrp

DISCLAIMER:
This e-mail and any attachments to it may contain confidential and proprietary material and is solely for the use of the intended recipient. Any review, use, disclosure, distribution or copying of this transmittal is prohibited except by or on behalf of the intended recipient.  If you have received this transmittal in error, please notify the sender and destroy this e-mail and any attachments and all copies, whether electronic or printed.