Re: [VRRP] RFC5798

"Danny J. Mitzel" <mitzel@acm.org> Thu, 14 October 2010 16:52 UTC

Return-Path: <mitzel@acm.org>
X-Original-To: vrrp@core3.amsl.com
Delivered-To: vrrp@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id A3B003A6B08 for <vrrp@core3.amsl.com>; Thu, 14 Oct 2010 09:52:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.598
X-Spam-Level:
X-Spam-Status: No, score=-102.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id K7hRmSjcUPu6 for <vrrp@core3.amsl.com>; Thu, 14 Oct 2010 09:52:06 -0700 (PDT)
Received: from web33208.mail.mud.yahoo.com (web33208.mail.mud.yahoo.com [209.191.69.156]) by core3.amsl.com (Postfix) with SMTP id A40AB3A6AB7 for <vrrp@ietf.org>; Thu, 14 Oct 2010 09:52:06 -0700 (PDT)
Received: (qmail 90261 invoked by uid 60001); 14 Oct 2010 16:53:23 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s1024; t=1287075203; bh=NZ3YVPzkJeDy6fg8SUVhYCvV77rhZpPSd6ruFJLTCKs=; h=Message-ID:X-YMail-OSG:Received:X-RocketYMMF:X-Mailer:Date:From:Reply-To:Subject:To:Cc:In-Reply-To:MIME-Version:Content-Type; b=195pD0tB4icBoACcw+zpZr0TAj2/eXh+9WSdRmJgM6nAcIc/ZmNB5ekXJn1gw7BzKdTlqJyCfTA99WbtCzztjnEtrMm1YkqkdzSneReFpn2cLJ8PjBEfPsrxZu+k2D2Xrc/cHfEnNil6vKlaqKTn0Q5SeGVYu+7yx9whb+/31uY=
Message-ID: <139969.89447.qm@web33208.mail.mud.yahoo.com>
X-YMail-OSG: sOJLl4sVM1mDyiZw1Xdtr2_brpDa6yXFBhQ6ldYQ5z2WsVk 2m5WqmJWpB_oXgl_USA73Gw0bkceZJxkwPYwgvfcS5BFWMmtFosEIl4MXB5M jdCjTN_lRipvMlxFhJMAh7c1kuZDWI6dXNJvYMNeKMkMSd1FoOQYAOC8FW3b fYXmoczEH7Ii6YzuiOwDoE7T4oXW3UyxaaLyUlBSpGzy5Ug9O1LDwvMptd_J 14thkWQqmr3xv1v9IYJxy7w9oTJEz3YuEok2vAfw6ri_gjv6SIc.5NVmE5w9 GS.BotkixhnpYjBIwpCxsoP64HldwDoL_YE1N9.hhW_qe3WmJIYx3iP2l9.y W4pQ7
Received: from [216.239.45.4] by web33208.mail.mud.yahoo.com via HTTP; Thu, 14 Oct 2010 09:53:22 PDT
X-RocketYMMF: danny_j_mitzel
X-Mailer: YahooMailClassic/11.4.9 YahooMailWebService/0.8.106.282862
Date: Thu, 14 Oct 2010 09:53:22 -0700 (PDT)
From: "Danny J. Mitzel" <mitzel@acm.org>
To: Carl Petersen <CPetersen@broadsoft.com>, Stephen Nadas <stephen.nadas@ericsson.com>
In-Reply-To: <450AE4BEC513614F96969DDA34F35934149DC427BD@EUSAACMS0701.eamcs.ericsson.se>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="0-985233537-1287075202=:89447"
Cc: "vrrp@ietf.org" <vrrp@ietf.org>
Subject: Re: [VRRP] RFC5798
X-BeenThere: vrrp@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: mitzel@acm.org
List-Id: Virtual Router Redundancy Protocol <vrrp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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, 14 Oct 2010 16:52:08 -0000

When VRRP is enabled then the associated MAC address is alwaysfixed 00-00-5E-00-01-{VRID}.  Whether there's a Master failover, ornetwork partition and heal, etc. there's no change to the mapping andall client hosts should be consistent.  No action is required.
The sole reason for the gratuitous ARP is to increase robustnessthe very first time VRRP is enabled in the network.  Prior to VRRPenable some client hosts may have cached the router physicalMAC address.  When VRRP is then enabled the first Mastertransition triggers gratuitous ARP to encourage client hosts toflush the router physical MAC address if it's in their cache.

--- On Thu, 10/14/10, Stephen Nadas <stephen.nadas@ericsson.com> wrote:

From: Stephen Nadas <stephen.nadas@ericsson.com>
Subject: Re: [VRRP] RFC5798
To: "Carl Petersen" <CPetersen@broadsoft.com>
Cc: "vrrp@ietf.org" <vrrp@ietf.org>
Date: Thursday, October 14, 2010, 9:10 AM



 
 
 _filtered #yiv163395626 {
font-family:Cambria Math;}
 _filtered #yiv163395626 {
font-family:Calibri;}
 _filtered #yiv163395626 {margin:1.0in 1.0in 1.0in 1.0in;}
#yiv163395626 P.yiv163395626MsoNormal {
FONT-SIZE:11pt;MARGIN:0in 0in 0pt;FONT-FAMILY:"sans-serif";}
#yiv163395626 LI.yiv163395626MsoNormal {
FONT-SIZE:11pt;MARGIN:0in 0in 0pt;FONT-FAMILY:"sans-serif";}
#yiv163395626 DIV.yiv163395626MsoNormal {
FONT-SIZE:11pt;MARGIN:0in 0in 0pt;FONT-FAMILY:"sans-serif";}
#yiv163395626 A:link {
COLOR:blue;TEXT-DECORATION:underline;}
#yiv163395626 SPAN.yiv163395626MsoHyperlink {
COLOR:blue;TEXT-DECORATION:underline;}
#yiv163395626 A:visited {
COLOR:purple;TEXT-DECORATION:underline;}
#yiv163395626 SPAN.yiv163395626MsoHyperlinkFollowed {
COLOR:purple;TEXT-DECORATION:underline;}
#yiv163395626 SPAN.yiv163395626EmailStyle17 {
COLOR:windowtext;FONT-FAMILY:"sans-serif";}
#yiv163395626 .yiv163395626MsoChpDefault {
}
#yiv163395626 DIV.yiv163395626WordSection1 {
}


 
IMO 
better to ask VRRP list than me, individually, 
Regards,
Steve 




From: Carl Petersen 
[mailto:CPetersen@broadsoft.com] 
Sent: Thursday, October 14, 2010 
11:13 AM
To: Stephen Nadas
Subject: 
RFC5798




Stephen, I want to ask you a question about this RFC and the 
VRRP protocol. Regarding section 6.4.3, bullet points (735) to 
(765). 
   
If 2 vrrp routers became isolated for whatever reason, one 
router would remain as master, the other would transition from backup to master 
and send a gratuitous arp (ipv4 only) to notify remote arp caches. My question 
is about when the fault is corrected. One router transitions from master to 
backup; the other router still remains as master. The backup router follows 
(735) to (765), but the master seemingly does nothing at all. In particular the 
now-for-real master does not send a gratuitous arp. This leaves remote arp 
caches with the wrong ip/mac value. 
   
I’m sure this has been considered. What is typically done to 
prevent this scenario or to recover from it? 
   
Thanks 
   
Carl Petersen 
  

-----Inline Attachment Follows-----

_______________________________________________
vrrp mailing list
vrrp@ietf.org
https://www.ietf.org/mailman/listinfo/vrrp