Re: Proposal for Maintenance Event for VRRP [RFC-5798]
"Anurag Kothari (ankothar)" <[email protected]> Fri, 22 Feb 2013 11:41:47 +0000
| Newsgroups | gmane.ietf.vrrp |
|---|---|
| Message-ID | <[email protected]> |
--===============4506615844456890903== Content-Language: en-US Content-Type: multipart/alternative; boundary="_000_A2BB90B33FFDF740876C5AAE307D83DB1C292974xmbrcdx05ciscoc_" --_000_A2BB90B33FFDF740876C5AAE307D83DB1C292974xmbrcdx05ciscoc_ Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable 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 propos= al 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:[email protected]] Sent: Thursday, February 21, 2013 11:26 PM To: Anurag Kothari (ankothar) Cc: [email protected] 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 =3D 0 -endif // maintenance recv And you mentioned that router need to send regular ADVERTISEMENT messag= e 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. 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 <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]> [mailto:vrrp-boun= [email protected]] On Behalf Of sreenatha Sent: Thursday, February 21, 2013 11:03 AM To: [email protected]<mailto:[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 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, [email protected]<mailto:[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]<mailto:[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]<mailto:[email protected]> You can reach the person managing the list at [email protected]<mailto:[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]><mailto:ankothar@cisco= .com> To:"[email protected]"<mailto:[email protected]> <[email protected]><mailto:vrrp@ietf.= org> Subject: [VRRP] Proposal for Maintenance Event for VRRP [RFC-5798] Message-ID: <[email protected]><mailto:= [email protected]> 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. 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:<http://www.ietf.org/mail-archive/web/vrrp/attachments/20130219/36<http= ://www.ietf.org/mail-archive/web/vrrp/attachments/20130219/36a6571f/attachm= ent.htm> a6571f/attachment.htm><http://www.ietf.org/mail-archive/web/vrrp/attachment= s/20130219/36a6571f/attachment.htm> ------------------------------ _______________________________________________ vrrp mailing list [email protected]<mailto:[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 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. _______________________________________________ vrrp mailing list [email protected]<mailto:[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. --_000_A2BB90B33FFDF740876C5AAE307D83DB1C292974xmbrcdx05ciscoc_ Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable <html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr= osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" = xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:= //www.w3.org/TR/REC-html40"> <head> <meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"= > <meta name=3D"Generator" content=3D"Microsoft Word 14 (filtered medium)"> <style><!-- /* Font Definitions */ @font-face {font-family:Calibri; panose-1:2 15 5 2 2 2 4 3 2 4;} @font-face {font-family:Tahoma; panose-1:2 11 6 4 3 5 4 4 2 4;} @font-face {font-family:Consolas; panose-1:2 11 6 9 2 2 4 3 2 4;} /* Style Definitions */ p.MsoNormal, li.MsoNormal, div.MsoNormal {margin:0in; margin-bottom:.0001pt; font-size:12.0pt; font-family:"Times New Roman","serif"; color:black;} a:link, span.MsoHyperlink {mso-style-priority:99; color:blue; text-decoration:underline;} a:visited, span.MsoHyperlinkFollowed {mso-style-priority:99; color:purple; text-decoration:underline;} p {mso-style-priority:99; mso-margin-top-alt:auto; margin-right:0in; mso-margin-bottom-alt:auto; margin-left:0in; font-size:12.0pt; font-family:"Times New Roman","serif"; color:black;} pre {mso-style-priority:99; mso-style-link:"HTML Preformatted Char"; margin:0in; margin-bottom:.0001pt; font-size:10.0pt; font-family:"Courier New"; color:black;} p.MsoAcetate, li.MsoAcetate, div.MsoAcetate {mso-style-priority:99; mso-style-link:"Balloon Text Char"; margin:0in; margin-bottom:.0001pt; font-size:8.0pt; font-family:"Tahoma","sans-serif"; color:black;} span.HTMLPreformattedChar {mso-style-name:"HTML Preformatted Char"; mso-style-priority:99; mso-style-link:"HTML Preformatted"; font-family:"Consolas","serif"; color:black;} span.BalloonTextChar {mso-style-name:"Balloon Text Char"; mso-style-priority:99; mso-style-link:"Balloon Text"; font-family:"Tahoma","sans-serif"; color:black;} span.EmailStyle22 {mso-style-type:personal-reply; font-family:"Calibri","sans-serif"; color:#1F497D;} .MsoChpDefault {mso-style-type:export-only; font-size:10.0pt;} @page WordSection1 {size:8.5in 11.0in; margin:1.0in 1.0in 1.0in 1.0in;} div.WordSection1 {page:WordSection1;} --></style><!--[if gte mso 9]><xml> <o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" /> </xml><![endif]--><!--[if gte mso 9]><xml> <o:shapelayout v:ext=3D"edit"> <o:idmap v:ext=3D"edit" data=3D"1" /> </o:shapelayout></xml><![endif]--> </head> <body bgcolor=3D"white" lang=3D"EN-US" link=3D"blue" vlink=3D"purple"> <div class=3D"WordSection1"> <p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:"Ca= libri","sans-serif";color:#1F497D">Hi Sreenatha<o:p></o:p></= span></p> <p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:"Ca= libri","sans-serif";color:#1F497D"><o:p> </o:p></span><= /p> <p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:"Ca= libri","sans-serif";color:#1F497D">My bad, by cancel I meant= reset the timer.<o:p></o:p></span></p> <p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:"Ca= libri","sans-serif";color:#1F497D"><o:p> </o:p></span><= /p> <p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:"Ca= libri","sans-serif";color:#1F497D">I would prefer defining m= aintenance event itself as (or being triggered by) priority being set to 0 = for a VRID. So probably we can rephrase the proposal as:<o:p></o:p></span><= /p> <p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:"Ca= libri","sans-serif";color:#1F497D"><o:p> </o:p></span><= /p> <pre>- If a Maintenance event is received, then:<o:p></o:p></pre> <pre><o:p> </o:p></pre> <pre>+ Send an ADVERTISEMENT<o:p></o:p></pre> <pre><o:p> </o:p></pre> <pre>+ Reset the Adver_Timer to Advertisement_Interval<o:p></o:p></pre> <pre><o:p> </o:p></pre> <pre>-endif // maintenance recv<o:p></o:p></pre> <p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:"Ca= libri","sans-serif";color:#1F497D"><o:p> </o:p></span><= /p> <p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:"Ca= libri","sans-serif";color:#1F497D">Thanks<o:p></o:p></span><= /p> <p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:"Ca= libri","sans-serif";color:#1F497D">-Anurag<o:p></o:p></span>= </p> <p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:"Ca= libri","sans-serif";color:#1F497D"><o:p> </o:p></span><= /p> <div> <div style=3D"border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in = 0in 0in"> <p class=3D"MsoNormal"><b><span style=3D"font-size:10.0pt;font-family:"= ;Tahoma","sans-serif";color:windowtext">From:</span></b><spa= n style=3D"font-size:10.0pt;font-family:"Tahoma","sans-serif= ";color:windowtext"> sreenatha [mailto:[email protected]= m] <br> <b>Sent:</b> Thursday, February 21, 2013 11:26 PM<br> <b>To:</b> Anurag Kothari (ankothar)<br> <b>Cc:</b> [email protected]<br> <b>Subject:</b> Re: [VRRP] Proposal for Maintenance Event for VRRP [RFC-579= 8]<o:p></o:p></span></p> </div> </div> <p class=3D"MsoNormal"><o:p> </o:p></p> <div> <p class=3D"MsoNormal">Hi Anurag,<br> Your proposal is:<br> <br> <br> <o:p></o:p></p> <pre>- If a Maintenance event is received, then:<o:p></o:p></pre> <pre><o:p> </o:p></pre> <pre>+ Cancel the Adver_Timer<o:p></o:p></pre> <pre><o:p> </o:p></pre> <pre>+ Send an ADVERTISEMENT with Priority =3D 0<o:p></o:p></pre> <pre><o:p> </o:p></pre> <pre>-endif // maintenance recv<o:p></o:p></pre> <pre><o:p> </o:p></pre> <pre><o:p> </o:p></pre> <pre> <span style=3D"font-family:"Arial","= sans-serif"">And you mentioned that router need to send regular ADVERT= ISEMENT message till it receives the ADVERTISEMENT message from the backup = router.</span><o:p></o:p></pre> <pre><o:p> </o:p></pre> <pre>"2. How much time Master router should wait to receive ADVERTISEM= ENT message from any backup router?<o:p></o:p></pre> <pre><o:p> </o:p></pre> <pre>[Anurag] Master doesn't have to wait. After receiving the maintenance = event it will send regular ADVERTISEMENT with Priority =3D 0 till some othe= r router send back an ADVERTISEMENT message at which point it will transiti= on to Backup."<o:p></o:p></pre> <pre><span style=3D"font-family:"Arial","sans-serif""><= o:p> </o:p></span></pre> <pre><span style=3D"font-family:"Arial","sans-serif"">I= f Advert_Timer is cancelled, how regular ADVERTISEMENT messages are sent?<o= :p></o:p></span></pre> <pre><o:p> </o:p></pre> <pre><span style=3D"font-family:"Arial","sans-serif"">S= o i am suggesting slight changes in the Proposal:<o:p></o:p></span></pre> <pre><span style=3D"font-family:"Arial","sans-serif""><= o:p> </o:p></span></pre> <pre><span style=3D"font-family:"Arial","sans-serif"">-= If a Maintenance event is received, then:<o:p></o:p></span></pre> <pre><span style=3D"font-family:"Arial","sans-serif""><= o:p> </o:p></span></pre> <pre><span style=3D"font-family:"Arial","sans-serif"">&= #43; Change the router priority to 0<o:p></o:p></span></pre> <pre><span style=3D"font-family:"Arial","sans-serif""><= o:p> </o:p></span></pre> <pre><span style=3D"font-family:"Arial","sans-serif"">&= #43; Send an ADVERTISEMENT with Priority =3D 0<o:p></o:p></span></pre> <pre><span style=3D"font-family:"Arial","sans-serif""><= o:p> </o:p></span></pre> <pre><span style=3D"font-family:"Arial","sans-serif"">&= #43; Reset the Adver_Timer<o:p></o:p></span></pre> <pre><span style=3D"font-family:"Arial","sans-serif""><= o:p> </o:p></span></pre> <pre><span style=3D"font-family:"Arial","sans-serif"">&= nbsp;-endif // maintenance recv<o:p></o:p></span></pre> <pre><span style=3D"font-family:"Arial","sans-serif""><= o:p> </o:p></span></pre> <pre><span style=3D"font-family:"Arial","sans-serif"">T= his will ensure that:<o:p></o:p></span></pre> <pre><span style=3D"font-family:"Arial","sans-serif"">1= . ADVERTISEMENT message with priority 0 is sent immediately on receiv= ing Maintenance event.<o:p></o:p></span></pre> <pre><span style=3D"font-family:"Arial","sans-serif"">2= . Master router will send regular Advertisement message till it receives th= e ADVERTISEMENT message from any backup routers.<o:p></o:p></span></pre> <pre><span style=3D"font-family:"Arial","sans-serif""><= o:p> </o:p></span></pre> <pre><span style=3D"font-family:"Arial","sans-serif"">T= hanks,<o:p></o:p></span></pre> <pre><span style=3D"font-family:"Arial","sans-serif"">S= reenatha Setty<o:p></o:p></span></pre> <pre><span style=3D"font-family:"Arial","sans-serif""><= o:p> </o:p></span></pre> <pre><o:p> </o:p></pre> <p class=3D"MsoNormal"><br> <br> On 02/21/2013 10:12 PM, Anurag Kothari (ankothar) wrote:<o:p></o:p></p> </div> <blockquote style=3D"margin-top:5.0pt;margin-bottom:5.0pt"> <pre>Hi Sreenatha<o:p></o:p></pre> <pre><o:p> </o:p></pre> <pre>This ideas is based on the way the priority is defined in Section 5.2.= 4. and 6.1. of RFC-5798.<o:p></o:p></pre> <pre><o:p> </o:p></pre> <pre>"<o:p></o:p></pre> <pre> The priority value zero (0) has special meaning, indicati= ng that the<o:p></o:p></pre> <pre> current Master has stopped participating in VRRP. T= his is used to<o:p></o:p></pre> <pre> trigger Backup routers to quickly transition to Master wi= thout having<o:p></o:p></pre> <pre> to wait for the current Master to time out.<o:p></o:p></p= re> <pre>"<o:p></o:p></pre> <pre><o:p> </o:p></pre> <pre>"<o:p></o:p></pre> <pre> Priority &= nbsp; <snip> The value of 0 (zero) is<o= :p></o:p></pre> <pre> &nbs= p; &= nbsp; reserved for the Master router to<o:p><= /o:p></pre> <pre> &nbs= p; &= nbsp; indicate it is releasing responsibility= <o:p></o:p></pre> <pre> &nbs= p; &= nbsp; for the virtual router. The range= 1-254<o:p></o:p></pre> <pre> &nbs= p; &= nbsp; (decimal) is available for VRRP routers= <o:p></o:p></pre> <pre> &nbs= p; &= nbsp; backing up the virtual router. <snip= ><o:p></o:p></pre> <pre>"<o:p></o:p></pre> <pre><o:p> </o:p></pre> <pre>Please see my responses inline [Anurag]:<o:p></o:p></pre> <pre><o:p> </o:p></pre> <pre>Thanks<o:p></o:p></pre> <pre>-Anurag<o:p></o:p></pre> <pre><o:p> </o:p></pre> <pre>-----Original Message-----<o:p></o:p></pre> <pre>From: <a href=3D"mailto:[email protected]">[email protected]</= a> [<a href=3D"mailto:[email protected]">mailto:[email protected]</= a>] On Behalf Of sreenatha<o:p></o:p></pre> <pre>Sent: Thursday, February 21, 2013 11:03 AM<o:p></o:p></pre> <pre>To: <a href=3D"mailto:[email protected]">[email protected]</a><o:p></o:p></pre= > <pre>Subject: Re: [VRRP] Proposal for Maintenance Event for VRRP [RFC-5798]= <o:p></o:p></pre> <pre><o:p> </o:p></pre> <pre>Hi Anurag,<o:p></o:p></pre> <pre> Proposed idea is good. I have some queries on= this proposal:<o:p></o:p></pre> <pre><o:p> </o:p></pre> <pre>1. On receiving new maintenance_event, priority of the router is not c= hanged, right? So if back-up router has less priority, even if Master recei= ves the ADVERTISEMENT from the backup router, Master will discard. <o:p></o= :p></pre> <pre>So how the Master router state is going to change?<o:p></o:p></pre> <pre><o:p> </o:p></pre> <pre>[Anurag] On receiving the maintenance event the priority of router (or= VRID) will change to 0.<o:p></o:p></pre> <pre><o:p> </o:p></pre> <pre>2. How much time Master router should wait to receive ADVERTISEMENT me= ssage from any backup router?<o:p></o:p></pre> <pre><o:p> </o:p></pre> <pre>[Anurag] Master doesn't have to wait. After receiving the maintenance = event it will send regular ADVERTISEMENT with Priority =3D 0 till some othe= r router send back an ADVERTISEMENT message at which point it will transiti= on to Backup.<o:p></o:p></pre> <pre><o:p> </o:p></pre> <pre>3. Standard VRRP MIB(RFC-2787) does not allow user to configure '0' fo= r VRRP Priority. So you are proposing to change this value also?<o:p></o:p>= </pre> <pre><o:p> </o:p></pre> <pre>[Anurag] Yes. Priority 0 will have to be made a user configurable valu= e to indicate the intention of a router to relinquish Master Status.<o:p></= o:p></pre> <pre><o:p> </o:p></pre> <pre>Thanks,<o:p></o:p></pre> <pre>Sreenatha Setty<o:p></o:p></pre> <pre><o:p> </o:p></pre> <pre>On 02/21/2013 01:30 AM, <a href=3D"mailto:[email protected]">vrrp-= [email protected]</a> wrote:<o:p></o:p></pre> <blockquote style=3D"margin-top:5.0pt;margin-bottom:5.0pt"> <pre>If you have received this digest without all the individual message <o= :p></o:p></pre> <pre>attachments you will need to update your digest options in your list <= o:p></o:p></pre> <pre>subscription. To do so, go to<o:p></o:p></pre> <pre><o:p> </o:p></pre> <pre><a href=3D"https://www.ietf.org/mailman/listinfo/vrrp">https://www.iet= f.org/mailman/listinfo/vrrp</a><o:p></o:p></pre> <pre><o:p> </o:p></pre> <pre>Click the 'Unsubscribe or edit options' button, log in, and set "= Get <o:p></o:p></pre> <pre>MIME or Plain Text Digests?" to MIME. You can set this opti= on <o:p></o:p></pre> <pre>globally for all the list digests you receive at this point.<o:p></o:p= ></pre> <pre><o:p> </o:p></pre> <pre><o:p> </o:p></pre> <pre><o:p> </o:p></pre> <pre>Send vrrp mailing list submissions to<o:p></o:p></pre> <pre> <a href=3D"mailto:[email protected]">[email protected]</a><o:p></= o:p></pre> <pre><o:p> </o:p></pre> <pre>To subscribe or unsubscribe via the World Wide Web, visit<o:p></o:p></= pre> <pre> <a href=3D"https://www.ietf.org/mailman/listinfo/vrrp">ht= tps://www.ietf.org/mailman/listinfo/vrrp</a><o:p></o:p></pre> <pre>or, via email, send a message with subject or body 'help' to<o:p></o:p= ></pre> <pre> <a href=3D"mailto:[email protected]">vrrp-request@iet= f.org</a><o:p></o:p></pre> <pre><o:p> </o:p></pre> <pre>You can reach the person managing the list at<o:p></o:p></pre> <pre> <a href=3D"mailto:[email protected]">[email protected]= g</a><o:p></o:p></pre> <pre><o:p> </o:p></pre> <pre>When replying, please edit your Subject line so it is more specific <o= :p></o:p></pre> <pre>than "Re: Contents of vrrp digest..."<o:p></o:p></pre> <pre><o:p> </o:p></pre> <pre><o:p> </o:p></pre> <pre>Today's Topics:<o:p></o:p></pre> <pre><o:p> </o:p></pre> <pre> 1. Proposal for Maintenance Event for VRRP [RFC-579= 8]<o:p></o:p></pre> <pre> (Anurag Kothari (ankothar))<o:p><= /o:p></pre> <pre><o:p> </o:p></pre> <pre><o:p> </o:p></pre> <pre>----------------------------------------------------------------------= <o:p></o:p></pre> <pre><o:p> </o:p></pre> <pre>Message: 1<o:p></o:p></pre> <pre>Date: Tue, 19 Feb 2013 22:08:41 +0000<o:p></o:p></pre> <pre>From: "Anurag Kothari (ankothar)"<a href=3D"mailto:ankothar@= cisco.com"><[email protected]></a> <o:p></o:p></pre> <pre>To:<a href=3D"mailto:[email protected]">"[email protected]"</a> = ; <a href=3D"mailto:[email protected]"><[email protected]></a><o:p></o:p></pr= e> <pre>Subject: [VRRP] Proposal for Maintenance Event for VRRP [RFC-5798]<o:p= ></o:p></pre> <pre>Message-ID:<o:p></o:p></pre> <pre> <a href=3D"mailto:A2BB90B33FFDF740876C5AAE307D83DB1C29032= [email protected]"><A2BB90B33FFDF740876C5AAE307D83DB1C290327@xmb-r= cd-x05.cisco.com></a><o:p></o:p></pre> <pre>Content-Type: text/plain; charset=3D"us-ascii"<o:p></o:p></p= re> <pre><o:p> </o:p></pre> <pre>Hi<o:p></o:p></pre> <pre><o:p> </o:p></pre> <pre>I want to propose a new Maintenance Event (modification of Shutdown Ev= ent) for VRRP (RFC-5798] which would allow to gracefully failover the VRRP = Master to Redundant (Backup Router).<o:p></o:p></pre> <pre><o:p> </o:p></pre> <pre>Problem Statement:<o:p></o:p></pre> <pre>VRRP preemption is not configured on the redundant / backup router. <o= :p></o:p></pre> <pre>How to initiate VRRP Traffic to failover to the redundant / backup <o:= p></o:p></pre> <pre>router gracefully without modifying the configuration on the redundant= <o:p></o:p></pre> <pre>/ backup router (i.e. adding preemption)<o:p></o:p></pre> <pre><o:p> </o:p></pre> <pre>Proposed Solution:<o:p></o:p></pre> <pre>Addition to Section 6.4.3 of RFC-5798:<o:p></o:p></pre> <pre><o:p> </o:p></pre> <pre>- If a Maintenance event is received, then:<o:p></o:p></pre> <pre><o:p> </o:p></pre> <pre>+ Cancel the Adver_Timer<o:p></o:p></pre> <pre><o:p> </o:p></pre> <pre>+ Send an ADVERTISEMENT with Priority =3D 0<o:p></o:p></pre> <pre><o:p> </o:p></pre> <pre>-endif // maintenance recv<o:p></o:p></pre> <pre><o:p> </o:p></pre> <pre>Unlike Shutdown event the router will not "Transition to the {Ini= tialize} state" and continue to be Master and forward traffic ti= ll the backup router sends an ADVERTISEMENT (triggered by receiving an ADVE= RTISEMENT with Priority =3D 0) and becomes master.<o:p></o:p></pre> </blockquote> <pre><o:p> </o:p></pre> <blockquote style=3D"margin-top:5.0pt;margin-bottom:5.0pt"> <pre><o:p> </o:p></pre> <pre>Here are couple of examples of how a maintenance event may be <o:p></o= :p></pre> <pre>triggered<o:p></o:p></pre> <pre><o:p> </o:p></pre> <pre><o:p> </o:p></pre> <pre>1) By some user command e.g. "maint= enance-mode" in the vrrp configuration.<o:p></o:p></pre> <pre><o:p> </o:p></pre> <pre>2) By setting the priority =3D 0 for a p= articular VRID.<o:p></o:p></pre> <pre><o:p> </o:p></pre> <pre>Thanks<o:p></o:p></pre> <pre>-Anurag<o:p></o:p></pre> <pre><o:p> </o:p></pre> <pre>-------------- next part -------------- An HTML attachment was <o:p></= o:p></pre> <pre>scrubbed...<o:p></o:p></pre> <pre>URL:<a href=3D"http://www.ietf.org/mail-archive/web/vrrp/attachments/2= 0130219/36a6571f/attachment.htm"><http://www.ietf.org/mail-archive/web/v= rrp/attachments/20130219/36<o:p></o:p></a></pre> <pre><span class=3D"MsoHyperlink"><a href=3D"http://www.ietf.org/mail-archi= ve/web/vrrp/attachments/20130219/36a6571f/attachment.htm">a6571f/attachment= .htm></a></span><o:p></o:p></pre> <pre><o:p> </o:p></pre> <pre>------------------------------<o:p></o:p></pre> <pre><o:p> </o:p></pre> <pre>_______________________________________________<o:p></o:p></pre> <pre>vrrp mailing list<o:p></o:p></pre> <pre><a href=3D"mailto:[email protected]">[email protected]</a><o:p></o:p></pre> <pre><a href=3D"https://www.ietf.org/mailman/listinfo/vrrp">https://www.iet= f.org/mailman/listinfo/vrrp</a><o:p></o:p></pre> <pre><o:p> </o:p></pre> <pre><o:p> </o:p></pre> <pre>End of vrrp Digest, Vol 81, Issue 1<o:p></o:p></pre> <pre>***********************************<o:p></o:p></pre> <pre><o:p> </o:p></pre> </blockquote> <pre><o:p> </o:p></pre> <pre>Disclaimer : <o:p></o:p></pre> <pre>This email communication may contain privileged and confidential infor= mation 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 p= rohibited. If you have received this email in error, please notify the send= er immediately by return e-mail and delete the communication sent in error.= Email communications cannot be guaranteed to be secure & error free an= d IB Technology is not liable for any errors in the email communication or = for the proper, timely and complete transmission thereof.<o:p></o:p></pre> <pre><o:p> </o:p></pre> <pre>_______________________________________________<o:p></o:p></pre> <pre>vrrp mailing list<o:p></o:p></pre> <pre><a href=3D"mailto:[email protected]">[email protected]</a><o:p></o:p></pre> <pre><a href=3D"https://www.ietf.org/mailman/listinfo/vrrp">https://www.iet= f.org/mailman/listinfo/vrrp</a><o:p></o:p></pre> <pre><o:p> </o:p></pre> </blockquote> <p class=3D"MsoNormal"><o:p> </o:p></p> <p>Disclaimer : <br> 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 prohibited. If you have received this email in err= or, please notify the sender immediately by return e-mail and delete the co= mmunication 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.<o:p></o:p></p> </div> </body> </html> --_000_A2BB90B33FFDF740876C5AAE307D83DB1C292974xmbrcdx05ciscoc_-- --===============4506615844456890903== 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 --===============4506615844456890903==--