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

"Anurag Kothari (ankothar)" <ankothar@cisco.com> Tue, 19 February 2013 22:08 UTC

Return-Path: <ankothar@cisco.com>
X-Original-To: vrrp@ietfa.amsl.com
Delivered-To: vrrp@ietfa.amsl.com
Received: from localhost (localhost []) by ietfa.amsl.com (Postfix) with ESMTP id 92C4121F85F5 for <vrrp@ietfa.amsl.com>; Tue, 19 Feb 2013 14:08:48 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.598
X-Spam-Status: No, score=-10.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([]) by localhost (ietfa.amsl.com []) (amavisd-new, port 10024) with ESMTP id ghhhtgKQlF55 for <vrrp@ietfa.amsl.com>; Tue, 19 Feb 2013 14:08:43 -0800 (PST)
Received: from rcdn-iport-1.cisco.com (rcdn-iport-1.cisco.com []) by ietfa.amsl.com (Postfix) with ESMTP id 510EE21F85E7 for <vrrp@ietf.org>; Tue, 19 Feb 2013 14:08:43 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=8330; q=dns/txt; s=iport; t=1361311723; x=1362521323; h=from:to:subject:date:message-id:mime-version; bh=g2v9W6OYxA0zgvX3n19IVu+kOPkqlJfarJKa5Z37CHE=; b=HMG6LriY0v1psUPdz2Gv2S14NIg/JVgXwt1g5uKk5vgwpH2lVjwYX7ar nF8/OJuTcscQaWEjGQJ9lA1G9WwCv5Yw5eOJYbQL4XDhPsgeofiRbZY+O WEzO5H4VuEZyRZNEX1L+WEBNEBmYSIlojKRKhzzOKmW5L667x4yEoLGZD 0=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AgAFAJX2I1GtJXG+/2dsb2JhbABFgkO9f4ENFnOCIQEELV4BKlYmAQQbE4d3nxyRE5AojTSBKYMXYQOnA4MHgic
X-IronPort-AV: E=Sophos; i="4.84,697,1355097600"; d="scan'208,217"; a="178690665"
Received: from rcdn-core2-3.cisco.com ([]) by rcdn-iport-1.cisco.com with ESMTP; 19 Feb 2013 22:08:42 +0000
Received: from xhc-rcd-x15.cisco.com (xhc-rcd-x15.cisco.com []) by rcdn-core2-3.cisco.com (8.14.5/8.14.5) with ESMTP id r1JM8gYh029199 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL) for <vrrp@ietf.org>; Tue, 19 Feb 2013 22:08:42 GMT
Received: from xmb-rcd-x05.cisco.com ([]) by xhc-rcd-x15.cisco.com ([]) with mapi id 14.02.0318.004; Tue, 19 Feb 2013 16:08:42 -0600
From: "Anurag Kothari (ankothar)" <ankothar@cisco.com>
To: "vrrp@ietf.org" <vrrp@ietf.org>
Thread-Topic: Proposal for Maintenance Event for VRRP [RFC-5798]
Thread-Index: Ac4O7aThy0QLWPNySdyGWhregnot6w==
Date: Tue, 19 Feb 2013 22:08:41 +0000
Message-ID: <A2BB90B33FFDF740876C5AAE307D83DB1C290327@xmb-rcd-x05.cisco.com>
Accept-Language: en-US
Content-Language: en-US
x-originating-ip: []
Content-Type: multipart/alternative; boundary="_000_A2BB90B33FFDF740876C5AAE307D83DB1C290327xmbrcdx05ciscoc_"
MIME-Version: 1.0
Subject: [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: Tue, 19 Feb 2013 22:22:32 -0000


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.