Re: Proposal for Maintenance Event for VRRP [RFC-5798]

sreenatha <[email protected]> Fri, 22 Feb 2013 09:55:35 +0530
Newsgroups gmane.ietf.vrrp
Message-ID <[email protected]>
This is a multi-part message in MIME format.
--===============1189675959037250802==
Content-Type: multipart/alternative;
 boundary="------------080809040106050203080509"

This is a multi-part message in MIME format.
--------------080809040106050203080509
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"; format="flowed"
Content-Transfer-Encoding: quoted-printable

Hi Anurag,
    Your proposal is:

- If a Maintenance event is received, then:

+ Cancel the Adver_Timer

+ Send an ADVERTISEMENT with Priority =3D 0

-endif // maintenance recv


     And you mentioned that router need to send regular ADVERTISEMENT messa=
ge till it receives the ADVERTISEMENT message from the backup router.

"2. How much time Master router should wait to receive ADVERTISEMENT messag=
e from any backup router?

[Anurag] Master doesn't have to wait. After receiving the maintenance event=
 it will send regular ADVERTISEMENT with Priority =3D 0 till some other rou=
ter 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 =3D 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 t=
he 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: [email protected] [mailto:[email protected]] On Behalf Of s=
reenatha
> Sent: Thursday, February 21, 2013 11:03 AM
> To: [email protected]
> 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 chan=
ged, 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 VR=
ID) will change to 0.
>
> 2. How much time Master router should wait to receive ADVERTISEMENT messa=
ge from any backup router?
>
> [Anurag] Master doesn't have to wait. After receiving the maintenance eve=
nt it will send regular ADVERTISEMENT with Priority =3D 0 till some other r=
outer 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 V=
RRP Priority. So you are proposing to change this value also?
>
> [Anurag] Yes. Priority 0 will have to be made a user configurable value t=
o indicate the intention of a router to relinquish Master Status.
>
> Thanks,
> Sreenatha Setty
>
> On 02/21/2013 01:30 AM, [email protected] 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
>> 	[email protected]
>>
>> 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
>> 	[email protected]
>>
>> You can reach the person managing the list at
>> 	[email protected]
>>
>> 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)"<[email protected]>
>> To:"[email protected]"  <[email protected]>
>> Subject: [VRRP] Proposal for Maintenance Event for VRRP [RFC-5798]
>> Message-ID:
>> 	<[email protected]>
>> Content-Type: text/plain; charset=3D"us-ascii"
>>
>> Hi
>>
>> I want to propose a new Maintenance Event (modification of Shutdown Even=
t) for VRRP (RFC-5798] which would allow to gracefully failover the VRRP Ma=
ster 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 =3D 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 rou=
ter sends an ADVERTISEMENT (triggered by receiving an ADVERTISEMENT with Pr=
iority =3D 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 configu=
ration.
>>
>> 2)      By setting the priority =3D 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
>> [email protected]
>> https://www.ietf.org/mailman/listinfo/vrrp
>>
>>
>> End of vrrp Digest, Vol 81, Issue 1
>> ***********************************
>>
> Disclaimer :
> This email communication may contain privileged and confidential informat=
ion and is intended for the use of the addressee only.If you are not an int=
ended recipient you are requested not to reproduce, copy disseminate or in =
any manner distribute this email communication as the same is strictly proh=
ibited. If you have received this email in error, please notify the sender =
immediately by return e-mail and delete the communication sent in error. Em=
ail communications cannot be guaranteed to be secure & error free and IB Te=
chnology is not liable for any errors in the email communication or for the=
 proper, timely and complete transmission thereof.
>
> _______________________________________________
> vrrp mailing list
> [email protected]
> https://www.ietf.org/mailman/listinfo/vrrp
>

Disclaimer : =

This email communication may contain privileged and confidential informatio=
n and is intended for the use of the addressee only.If you are not an inten=
ded recipient you are requested not to reproduce, copy disseminate or in an=
y manner distribute this email communication as the same is strictly prohib=
ited. If you have received this email in error, please notify the sender im=
mediately by return e-mail and delete the communication sent in error. Emai=
l communications cannot be guaranteed to be secure & error free and IB Tech=
nology is not liable for any errors in the email communication or for the p=
roper, timely and complete transmission thereof.

--------------080809040106050203080509
MIME-Version: 1.0
Content-Type: text/html; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<html>
  <head>
    <meta content=3D"text/html; charset=3DISO-8859-1"
      http-equiv=3D"Content-Type">
  </head>
  <body text=3D"#000000" bgcolor=3D"#FFFFFF">
    <div class=3D"moz-cite-prefix">Hi Anurag,<br>
      &nbsp;&nbsp; Your proposal is:<br>
      <br>
      <pre wrap=3D"">- If a Maintenance event is received, then:

+ Cancel the Adver_Timer

+ Send an ADVERTISEMENT with Priority =3D 0

-endif // maintenance recv


    <font face=3D"sans-serif">And you mentioned that router need to send re=
gular ADVERTISEMENT message till it receives the ADVERTISEMENT message from=
 the backup router.</font>

"2. How much time Master router should wait to receive ADVERTISEMENT messag=
e from any backup router?

[Anurag] Master doesn't have to wait. After receiving the maintenance event=
 it will send regular ADVERTISEMENT with Priority =3D 0 till some other rou=
ter send back an ADVERTISEMENT message at which point it will transition to=
 Backup."
<font face=3D"sans-serif">
If Advert_Timer is cancelled, how regular ADVERTISEMENT messages are sent?
</font>
<font face=3D"sans-serif">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 =3D 0

+ Reset the Adver_Timer

&nbsp;-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 t=
he ADVERTISEMENT message from any backup routers.

Thanks,
Sreenatha Setty

</font>
</pre>
      <br>
      <br>
      On 02/21/2013 10:12 PM, Anurag Kothari (ankothar) wrote:<br>
    </div>
    <blockquote
cite=3D"mid:[email protected]"
      type=3D"cite">
      <pre wrap=3D"">Hi Sreenatha

This ideas is based on the way the priority is defined in Section 5.2.4. an=
d 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              &lt;snip&gt;  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. &lt;snip&gt;
"

Please see my responses inline [Anurag]:

Thanks
-Anurag

-----Original Message-----
From: <a class=3D"moz-txt-link-abbreviated" href=3D"mailto:vrrp-bounces@iet=
f.org">[email protected]</a> [<a class=3D"moz-txt-link-freetext" href=
=3D"mailto:[email protected]">mailto:[email protected]</a>] On Beha=
lf Of sreenatha
Sent: Thursday, February 21, 2013 11:03 AM
To: <a class=3D"moz-txt-link-abbreviated" href=3D"mailto:[email protected]">vrr=
[email protected]</a>
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 change=
d, right? So if back-up router has less priority, even if Master receives t=
he 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 =3D 0 till some other rou=
ter 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 VRR=
P 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, <a class=3D"moz-txt-link-abbreviated" href=3D"mailt=
o:[email protected]">[email protected]</a> wrote:
</pre>
      <blockquote type=3D"cite">
        <pre wrap=3D"">If you have received this digest without all the ind=
ividual message =

attachments you will need to update your digest options in your list =

subscription.  To do so, go to

<a class=3D"moz-txt-link-freetext" href=3D"https://www.ietf.org/mailman/lis=
tinfo/vrrp">https://www.ietf.org/mailman/listinfo/vrrp</a>

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
	<a class=3D"moz-txt-link-abbreviated" href=3D"mailto:[email protected]">vrrp@i=
etf.org</a>

To subscribe or unsubscribe via the World Wide Web, visit
	<a class=3D"moz-txt-link-freetext" href=3D"https://www.ietf.org/mailman/li=
stinfo/vrrp">https://www.ietf.org/mailman/listinfo/vrrp</a>
or, via email, send a message with subject or body 'help' to
	<a class=3D"moz-txt-link-abbreviated" href=3D"mailto:[email protected]=
">[email protected]</a>

You can reach the person managing the list at
	<a class=3D"moz-txt-link-abbreviated" href=3D"mailto:[email protected]">=
[email protected]</a>

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)"<a class=3D"moz-txt-link-rfc2396E" href=3D=
"mailto:[email protected]">&lt;[email protected]&gt;</a> =

To:<a class=3D"moz-txt-link-rfc2396E" href=3D"mailto:[email protected]">"vrrp@i=
etf.org"</a>  <a class=3D"moz-txt-link-rfc2396E" href=3D"mailto:[email protected]=
rg">&lt;[email protected]&gt;</a>
Subject: [VRRP] Proposal for Maintenance Event for VRRP [RFC-5798]
Message-ID:
	<a class=3D"moz-txt-link-rfc2396E" href=3D"mailto:A2BB90B33FFDF740876C5AAE=
[email protected]">&lt;A2BB90B33FFDF740876C5AAE307D83D=
[email protected]&gt;</a>
Content-Type: text/plain; charset=3D"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 Maste=
r 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 =3D 0

-endif // maintenance recv

Unlike Shutdown event the router will not "Transition to the {Initialize} s=
tate" and continue to be Master and forward traffic  till the backup router=
 sends an ADVERTISEMENT (triggered by receiving an ADVERTISEMENT with Prior=
ity =3D 0) and becomes master.
</pre>
      </blockquote>
      <pre wrap=3D"">
</pre>
      <blockquote type=3D"cite">
        <pre wrap=3D"">
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 configurat=
ion.

2)      By setting the priority =3D 0 for a particular VRID.

Thanks
-Anurag

-------------- next part -------------- An HTML attachment was =

scrubbed...
URL:<a class=3D"moz-txt-link-rfc2396E" href=3D"http://www.ietf.org/mail-arc=
hive/web/vrrp/attachments/20130219/36a6571f/attachment.htm">&lt;http://www.=
ietf.org/mail-archive/web/vrrp/attachments/20130219/36
a6571f/attachment.htm&gt;</a>

------------------------------

_______________________________________________
vrrp mailing list
<a class=3D"moz-txt-link-abbreviated" href=3D"mailto:[email protected]">vrrp@ie=
tf.org</a>
<a class=3D"moz-txt-link-freetext" href=3D"https://www.ietf.org/mailman/lis=
tinfo/vrrp">https://www.ietf.org/mailman/listinfo/vrrp</a>


End of vrrp Digest, Vol 81, Issue 1
***********************************

</pre>
      </blockquote>
      <pre wrap=3D"">
Disclaimer : =

This email communication may contain privileged and confidential informatio=
n and is intended for the use of the addressee only.If you are not an inten=
ded recipient you are requested not to reproduce, copy disseminate or in an=
y manner distribute this email communication as the same is strictly prohib=
ited. If you have received this email in error, please notify the sender im=
mediately by return e-mail and delete the communication sent in error. Emai=
l communications cannot be guaranteed to be secure &amp; error free and IB =
Technology is not liable for any errors in the email communication or for t=
he proper, timely and complete transmission thereof.

_______________________________________________
vrrp mailing list
<a class=3D"moz-txt-link-abbreviated" href=3D"mailto:[email protected]">vrrp@ie=
tf.org</a>
<a class=3D"moz-txt-link-freetext" href=3D"https://www.ietf.org/mailman/lis=
tinfo/vrrp">https://www.ietf.org/mailman/listinfo/vrrp</a>

</pre>
    </blockquote>
    <br>
  <P><font style=3D"FONT-SIZE: 11px; FONT-FAMILY: ">Disclaimer : <br>This e=
mail communication may contain privileged and confidential information and =
is intended for the use of the addressee only.If you are not an intended re=
cipient you are requested not to reproduce, copy disseminate or in any mann=
er distribute this email communication as the same is strictly prohibited. =
If you have received this email in error, please notify the sender immediat=
ely by return e-mail and delete the communication sent in error. Email comm=
unications cannot be guaranteed to be secure &amp; error free and IB Techno=
logy is not liable for any errors in the email communication or for the pro=
per, timely and complete transmission thereof.</font></P></body>
</html>

--------------080809040106050203080509--


--===============1189675959037250802==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
vrrp mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/vrrp

--===============1189675959037250802==--