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

sreenatha <sreenatha.setty@ibtechnology.com> Thu, 21 February 2013 16:03 UTC

Return-Path: <sreenatha.setty@ibtechnology.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 B676921F8EBB for <vrrp@ietfa.amsl.com>; Thu, 21 Feb 2013 08:03:58 -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 8LJdqSoF5XF1 for <vrrp@ietfa.amsl.com>; Thu, 21 Feb 2013 08:03:56 -0800 (PST)
Received: from ipinternal.indiabulls.com (ipinternal.indiabulls.com [202.54.119.192]) by ietfa.amsl.com (Postfix) with ESMTP id 8B8A021F8950 for <vrrp@ietf.org>; Thu, 21 Feb 2013 08:03:53 -0800 (PST)
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AqIEAB1FJlGsEQGd/2dsb2JhbABFwHuBG3OCHwEBAQEDAQEBNRYgChELDQQDAQIBCQMBEg8JAwIBAgEVCh4IEQIGAgEBBRICBId9vw6NNAkQgTYSBoM6A4hnhUOOI41WgWo
X-IronPort-AV: E=Sophos;i="4.84,710,1355077800"; d="scan'208";a="7554844"
X-IronPort-AV: E=Sophos;i="4.84,710,1355077800"; d="scan'208";a="102937383"
Received: from unknown (HELO [192.168.0.102]) ([27.124.57.10]) by ipgate.indiabulls.com with ESMTP; 21 Feb 2013 21:29:25 +0530
Message-ID: <51264544.7070300@ibtechnology.com>
Date: Thu, 21 Feb 2013 21:33:16 +0530
From: sreenatha <sreenatha.setty@ibtechnology.com>
User-Agent: Mozilla/5.0 (X11; Linux i686; rv:17.0) Gecko/17.0 Thunderbird/17.0
MIME-Version: 1.0
To: vrrp@ietf.org
References: <mailman.53.1361390408.7703.vrrp@ietf.org>
In-Reply-To: <mailman.53.1361390408.7703.vrrp@ietf.org>
Content-Type: text/plain; charset="iso-8859-1"; format="flowed"
Content-Transfer-Encoding: quoted-printable
Subject: Re: [VRRP] Proposal for Maintenance Event for VRRP [RFC-5798]
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: Thu, 21 Feb 2013 16:04:00 -0000

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?

2. How much time Master router should wait to receive ADVERTISEMENT 
message from any backup router?

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?

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/36a6571f/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.