Re: [bess] EVPN MH: Backup node behavior in Primary Path Failure

"Mrinmoy Ghosh (mrghosh)" <mrghosh@cisco.com> Thu, 04 October 2018 18:09 UTC

Return-Path: <mrghosh@cisco.com>
X-Original-To: bess@ietfa.amsl.com
Delivered-To: bess@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5C7E7130DDE for <bess@ietfa.amsl.com>; Thu, 4 Oct 2018 11:09:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.501
X-Spam-Level:
X-Spam-Status: No, score=-14.501 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_MED=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Y6VfuijDbzV2 for <bess@ietfa.amsl.com>; Thu, 4 Oct 2018 11:09:45 -0700 (PDT)
Received: from alln-iport-3.cisco.com (alln-iport-3.cisco.com [173.37.142.90]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 10BA7130D7A for <bess@ietf.org>; Thu, 4 Oct 2018 11:09:44 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=40380; q=dns/txt; s=iport; t=1538676585; x=1539886185; h=from:to:cc:subject:date:message-id:references: in-reply-to:mime-version; bh=qHXNgn0QL/0S7/6/3ksZ1GSBymiaMGeOnRlnu/dQQwM=; b=EdvavPYha8skKwOmPtLTZrwNu+iVZ/Q4tS28Kp2rZFNrk9+u2RnTm70/ sIOa0uoaMFKNQO5o5/Z0m1mMY1tdMUKTYGMf786JYT0EKgt/w2Ij8H0dw zbeuOxgMxuX+zi3uvWy+A1Nd+xOAaHNi+fXUx5CEm1yz6zCnhOlw55pOK Q=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0AGAAC4VrZb/4UNJK1bGQEBAQEBAQEBAQEBAQcBAQEBAQGBUQQBAQEBAQsBgQ5NKmZ/KAqDaogVjCCCDZZdgXoLAQGEbAIXhA4hNA0NAQMBAQIBAQJtKIU5AQEBAQMjCkwQAgEIEQMBAQEhAQYDAgICMBQJCAIEAQ0FCIMagR1kpFSBLooSiywXgUE/gREBgmQuhDokAQE+BhCCS4JXAohShTWGA4lNCQKQNh+BTIRiiT2VOAIRFIElHTgngS5wFYMngiUXewECBo0UbwEBiwmBH4EfAQE
X-IronPort-AV: E=Sophos;i="5.54,341,1534809600"; d="scan'208,217";a="181344318"
Received: from alln-core-11.cisco.com ([173.36.13.133]) by alln-iport-3.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 04 Oct 2018 18:09:43 +0000
Received: from XCH-RTP-018.cisco.com (xch-rtp-018.cisco.com [64.101.220.158]) by alln-core-11.cisco.com (8.15.2/8.15.2) with ESMTPS id w94I9hAc024400 (version=TLSv1.2 cipher=AES256-SHA bits=256 verify=FAIL); Thu, 4 Oct 2018 18:09:43 GMT
Received: from xch-rtp-019.cisco.com (64.101.220.159) by XCH-RTP-018.cisco.com (64.101.220.158) with Microsoft SMTP Server (TLS) id 15.0.1395.4; Thu, 4 Oct 2018 14:09:42 -0400
Received: from xch-rtp-019.cisco.com ([64.101.220.159]) by XCH-RTP-019.cisco.com ([64.101.220.159]) with mapi id 15.00.1395.000; Thu, 4 Oct 2018 14:09:42 -0400
From: "Mrinmoy Ghosh (mrghosh)" <mrghosh@cisco.com>
To: Jaikumar Somasundaram <jaikumar.somasundaram@ericsson.com>, "Rabadan, Jorge (Nokia - US/Mountain View)" <jorge.rabadan@nokia.com>, "bess@ietf.org" <bess@ietf.org>
CC: Jiang He <jiang.he@ericsson.com>, P Muthu Arul Mozhi <p.muthu.arul.mozhi@ericsson.com>
Thread-Topic: [bess] EVPN MH: Backup node behavior in Primary Path Failure
Thread-Index: AQHUW7tP4y39mq7ZSkOVnaPFMhO3u6UO0DWQgAAs0YD//+K7sIAAaW+AgAAzNQD//+X90A==
Date: Thu, 04 Oct 2018 18:09:41 +0000
Message-ID: <bc55821dd0774af78d92ca382101257a@XCH-RTP-019.cisco.com>
References: <067ED9A1-F8D0-4C53-97A0-3E6FA7E063EC@nokia.com> <VI1PR07MB4302D68B2828F10E49C834A486EA0@VI1PR07MB4302.eurprd07.prod.outlook.com> <D4979895-D9D9-434D-A247-62682E678853@nokia.com> <VI1PR07MB430228397B3FBE63C5CE125386EA0@VI1PR07MB4302.eurprd07.prod.outlook.com> <5A914381-C0B8-47D0-B099-C57C1F2A75B5@nokia.com> <VI1PR07MB43024A4279206157CEEF955786EA0@VI1PR07MB4302.eurprd07.prod.outlook.com>
In-Reply-To: <VI1PR07MB43024A4279206157CEEF955786EA0@VI1PR07MB4302.eurprd07.prod.outlook.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [10.32.198.240]
Content-Type: multipart/alternative; boundary="_000_bc55821dd0774af78d92ca382101257aXCHRTP019ciscocom_"
MIME-Version: 1.0
X-Outbound-SMTP-Client: 64.101.220.158, xch-rtp-018.cisco.com
X-Outbound-Node: alln-core-11.cisco.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/bess/HtgSnxEQX1l6_HKVMnzTUFEpqhw>
Subject: Re: [bess] EVPN MH: Backup node behavior in Primary Path Failure
X-BeenThere: bess@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: BGP-Enabled ServiceS working group discussion list <bess.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/bess>, <mailto:bess-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/bess/>
List-Post: <mailto:bess@ietf.org>
List-Help: <mailto:bess-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/bess>, <mailto:bess-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 04 Oct 2018 18:09:48 -0000

Hi Jaikumar,

Backup failure can happen in multiple forms, Node down, Interface down etc.
There is no DF election timer on ES withdrawal, it should be carved immediately in Peering PEs.
DF election timer is manly when the ES is coming up (Node up, Interface up etc) to specify some.

Thanks,
Mrinmoy

From: BESS <bess-bounces@ietf.org> On Behalf Of Jaikumar Somasundaram
Sent: Thursday, October 4, 2018 8:39 AM
To: Rabadan, Jorge (Nokia - US/Mountain View) <jorge.rabadan@nokia.com>; bess@ietf.org
Cc: Jiang He <jiang.he@ericsson.com>; P Muthu Arul Mozhi <p.muthu.arul.mozhi@ericsson.com>
Subject: Re: [bess] EVPN MH: Backup node behavior in Primary Path Failure

Hi Jorge,

Yes, new DF will be identified after the new election.
Election process will need to wait for DF election timer period, say 3s or the configured timer period.
Until this DF election timer expiry and new DF is identified, the traffic towards CE coming to the node this PE
will get dropped. Please let me know if my understanding is right?

Thanks & Regards
Jaikumar S
From: Rabadan, Jorge (Nokia - US/Mountain View) <jorge.rabadan@nokia.com<mailto:jorge.rabadan@nokia.com>>
Sent: Thursday, October 4, 2018 8:06 PM
To: Jaikumar Somasundaram <jaikumar.somasundaram@ericsson.com<mailto:jaikumar.somasundaram@ericsson.com>>; bess@ietf.org<mailto:bess@ietf.org>
Cc: Jiang He <jiang.he@ericsson.com<mailto:jiang.he@ericsson.com>>; P Muthu Arul Mozhi <p.muthu.arul.mozhi@ericsson.com<mailto:p.muthu.arul.mozhi@ericsson.com>>
Subject: Re: [bess] EVPN MH: Backup node behavior in Primary Path Failure

Jai,

The new DF becomes DF because it re-runs DF election.
Thx
Jorge

From: Jaikumar Somasundaram <jaikumar.somasundaram@ericsson.com<mailto:jaikumar.somasundaram@ericsson.com>>
Date: Thursday, October 4, 2018 at 12:23 PM
To: "Rabadan, Jorge (Nokia - US/Mountain View)" <jorge.rabadan@nokia.com<mailto:jorge.rabadan@nokia.com>>, "bess@ietf.org<mailto:bess@ietf.org>" <bess@ietf.org<mailto:bess@ietf.org>>
Cc: Jiang He <jiang.he@ericsson.com<mailto:jiang.he@ericsson.com>>, P Muthu Arul Mozhi <p.muthu.arul.mozhi@ericsson.com<mailto:p.muthu.arul.mozhi@ericsson.com>>
Subject: RE: [bess] EVPN MH: Backup node behavior in Primary Path Failure

In-line.

From: Rabadan, Jorge (Nokia - US/Mountain View) <jorge.rabadan@nokia.com<mailto:jorge.rabadan@nokia.com>>
Sent: Thursday, October 4, 2018 3:33 PM
To: Jaikumar Somasundaram <jaikumar.somasundaram@ericsson.com<mailto:jaikumar.somasundaram@ericsson.com>>; bess@ietf.org<mailto:bess@ietf.org>
Cc: Jiang He <jiang.he@ericsson.com<mailto:jiang.he@ericsson.com>>; P Muthu Arul Mozhi <p.muthu.arul.mozhi@ericsson.com<mailto:p.muthu.arul.mozhi@ericsson.com>>
Subject: Re: [bess] EVPN MH: Backup node behavior in Primary Path Failure

In-line.

Thx
Jorge

From: Jaikumar Somasundaram <jaikumar.somasundaram@ericsson.com<mailto:jaikumar.somasundaram@ericsson.com>>
Date: Thursday, October 4, 2018 at 11:28 AM
To: "Rabadan, Jorge (Nokia - US/Mountain View)" <jorge.rabadan@nokia.com<mailto:jorge.rabadan@nokia.com>>, "bess@ietf.org<mailto:bess@ietf.org>" <bess@ietf.org<mailto:bess@ietf.org>>
Cc: Jiang He <jiang.he@ericsson.com<mailto:jiang.he@ericsson.com>>, P Muthu Arul Mozhi <p.muthu.arul.mozhi@ericsson.com<mailto:p.muthu.arul.mozhi@ericsson.com>>
Subject: RE: [bess] EVPN MH: Backup node behavior in Primary Path Failure

Thanks Jorge for the quick reply.
Please find further question below.

From: Rabadan, Jorge (Nokia - US/Mountain View) <jorge.rabadan@nokia.com<mailto:jorge.rabadan@nokia.com>>
Sent: Thursday, October 4, 2018 1:52 PM
To: Jaikumar Somasundaram <jaikumar.somasundaram@ericsson.com<mailto:jaikumar.somasundaram@ericsson.com>>; bess@ietf.org<mailto:bess@ietf.org>
Cc: Jiang He <jiang.he@ericsson.com<mailto:jiang.he@ericsson.com>>; P Muthu Arul Mozhi <p.muthu.arul.mozhi@ericsson.com<mailto:p.muthu.arul.mozhi@ericsson.com>>
Subject: Re: [bess] EVPN MH: Backup node behavior in Primary Path Failure

Hi,


Questions:
1.       Will the node in backup mode forward the packet to CE?

[JORGE] as soon as it becomes DF it can forward packets to the CE. The backup node will have to run DF election upon the ES route withdrawal from the primary. If AC-DF is enabled, it can also react to the withdrawal of AD routes from the primary PE.

[Jai] Does that mean if any packet comes to a node that is still in the backup mode will get dropped, before the new DF election is complete? Why cant this be used as FRR? Or what is the use case of having backup node(s)?

[JORGE2] when the primary node fails, ES and AD routes are withdrawn. The AD route withdrawal is an indication for remote nodes that they have to send traffic to the backup (for a given MAC) or to flush the MACs if there are more than 2 PEs in the ES. Around the same time or maybe earlier, the ES route withdrawal will make the backup PE take over as DF

[Jai] will it become DF without DF election? What if there is more than one PE in backup mode?

. So the overall convergence time will depend on how/when those two things happen in time. Only the DF PE can forward traffic. A non-DF can never forward traffic or there will be risk of duplicate packets.




2.       Will all the nodes in backup mode forward the packet before DF election?

[JORGE] Only the new DF can forward.



3. If they forward, how is duplicate packets handled, in this case?
[JORGE] see above.

My two cents..

Thanks.
Jorge



From: BESS <bess-bounces@ietf.org<mailto:bess-bounces@ietf.org>> on behalf of Jaikumar Somasundaram <jaikumar.somasundaram@ericsson.com<mailto:jaikumar.somasundaram@ericsson.com>>
Date: Thursday, October 4, 2018 at 10:03 AM
To: "bess@ietf.org<mailto:bess@ietf.org>" <bess@ietf.org<mailto:bess@ietf.org>>
Cc: Jiang He <jiang.he@ericsson.com<mailto:jiang.he@ericsson.com>>, P Muthu Arul Mozhi <p.muthu.arul.mozhi@ericsson.com<mailto:p.muthu.arul.mozhi@ericsson.com>>
Subject: [bess] EVPN MH: Backup node behavior in Primary Path Failure


Hello Everyone,

Sorry if it is a duplicate. I repost this query as I did not receive any response yet.
(I was wondering if this mail already reached the group or not)


I have a question on Primary PE encountering a failure in EVPN multihoming

in single active mode.



RFC7432, section 14.1.1:

<snip>

   If there is more than one backup PE for a given ES, the remote PE

   MUST use the primary PE's withdrawal of its set of Ethernet A-D per

   ES routes as a trigger to start flooding traffic for the associated

   MAC addresses (as long as flooding of unknown unicast packets is

   administratively allowed), as it is not possible to select a single

   backup PE.

</snip>



Questions:

1. Will the node in backup mode forward the packet to CE?

2. Will all the nodes in backup mode forward the packet before DF election?

3. If they forward, how is duplicate packets handled, in this case?



Please help me anwere these questions.



Thanks & Regards

Jaikumar S