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

Jaikumar Somasundaram <jaikumar.somasundaram@ericsson.com> Thu, 04 October 2018 15:39 UTC

Return-Path: <jaikumar.somasundaram@ericsson.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 B3F05130E65 for <bess@ietfa.amsl.com>; Thu, 4 Oct 2018 08:39:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.3
X-Spam-Level:
X-Spam-Status: No, score=-4.3 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=ericsson.com header.b=GEbCmRbF; dkim=pass (1024-bit key) header.d=ericsson.com header.b=VzSTJ0fE
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 Pak3OD6iDCFC for <bess@ietfa.amsl.com>; Thu, 4 Oct 2018 08:39:19 -0700 (PDT)
Received: from sesbmg23.ericsson.net (sesbmg23.ericsson.net [193.180.251.37]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2D31812008A for <bess@ietf.org>; Thu, 4 Oct 2018 08:39:19 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; d=ericsson.com; s=mailgw201801; c=relaxed/simple; q=dns/txt; i=@ericsson.com; t=1538667557; h=From:Sender:Reply-To:Subject:Date:Message-ID:To:CC:MIME-Version:Content-Type: Content-Transfer-Encoding:Content-ID:Content-Description:Resent-Date:Resent-From: Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID:In-Reply-To:References:List-Id: List-Help:List-Unsubscribe:List-Subscribe:List-Post:List-Owner:List-Archive; bh=8KtDMk3M8d3O6AYz1Y0iGnqfjwZ8UUjsyVjSlKOXVHA=; b=GEbCmRbFGyebXJJA9t6BDd1zlTorUJCnV7tckcWL4rMG9cYiAwAMsllldkGPutST a4+qHBVhJJfTRHsvpYnZ17AX6FO7dZOlK8j8pz3b/PBFoMNVHiUnhtnhCUI3CSN4 zWJvUNlba6WsBfjwMZZoe0c+RUeXdFKABaQio96I9+c=;
X-AuditID: c1b4fb25-8e7ff700000013ad-fb-5bb6342588ba
Received: from ESESSMB501.ericsson.se (Unknown_Domain [153.88.183.119]) by sesbmg23.ericsson.net (Symantec Mail Security) with SMTP id 8C.88.05037.52436BB5; Thu, 4 Oct 2018 17:39:17 +0200 (CEST)
Received: from ESESSMB503.ericsson.se (153.88.183.164) by ESESSMB501.ericsson.se (153.88.183.162) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.1466.3; Thu, 4 Oct 2018 17:39:17 +0200
Received: from EUR04-HE1-obe.outbound.protection.outlook.com (153.88.183.157) by ESESSMB503.ericsson.se (153.88.183.164) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.1466.3 via Frontend Transport; Thu, 4 Oct 2018 17:39:17 +0200
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ericsson.com; s=selector1; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=8KtDMk3M8d3O6AYz1Y0iGnqfjwZ8UUjsyVjSlKOXVHA=; b=VzSTJ0fEoSa5PRXarffDrGdVXrgOhIJRfEK/m+EhoNKe0M+qODWHAb+RtEFNUsQowdUVIlUIj61DrJ+XXmZhaPLVGFiOaFfxkBCWMvGcPp2yuwDPn4SwOD+lFvPs/NZEM7VH6E0qvxtvUhh/y/2YRkEXjWFCK061Mg+dhUdN05o=
Received: from VI1PR07MB4302.eurprd07.prod.outlook.com (20.176.6.159) by VI1PR07MB3968.eurprd07.prod.outlook.com (52.134.28.140) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.1207.11; Thu, 4 Oct 2018 15:39:15 +0000
Received: from VI1PR07MB4302.eurprd07.prod.outlook.com ([fe80::9090:f202:f51d:5519]) by VI1PR07MB4302.eurprd07.prod.outlook.com ([fe80::9090:f202:f51d:5519%3]) with mapi id 15.20.1207.022; Thu, 4 Oct 2018 15:39:14 +0000
From: Jaikumar Somasundaram <jaikumar.somasundaram@ericsson.com>
To: "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: AQHUW7tPwY67GDKFZkSdu6BevJADsqUO0DWQgAAs0YD//+K7sIAAaW+A///uRKA=
Date: Thu, 04 Oct 2018 15:39:14 +0000
Message-ID: <VI1PR07MB43024A4279206157CEEF955786EA0@VI1PR07MB4302.eurprd07.prod.outlook.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>
In-Reply-To: <5A914381-C0B8-47D0-B099-C57C1F2A75B5@nokia.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
authentication-results: spf=none (sender IP is ) smtp.mailfrom=jaikumar.somasundaram@ericsson.com;
x-originating-ip: [122.179.55.136]
x-ms-publictraffictype: Email
x-microsoft-exchange-diagnostics: 1; VI1PR07MB3968; 6:P+4PIHDoi9xdkWjWFH3URGtwiTmvhxxDQcWJ7QOWMm9rQTsEgasmbuC3QGJL+v8SXQbF3Zr9jraUabbTC3okarhhZ0sIMDYO4g3v+nG00PrMoYdDTjZa3OU6pCvSx2LOLnvw+UI9r658vn9rRQLozZkcZZcTF84wEBN/gQF08zK6hzEBN59Ar7IvWD3MHZ4aSUzHaHHR2FE319n8A4k1iF1U/+8MA6v/u70j3WqpA5zJoIwCJcX9Ul9YL9UC+w0/QbX4AKgWbUpvBCDUbUJcPKY8ziTdUn7cE4iKANCNtb5QW+CZqEcbLy/yV8LigQWYCIM0CPSnliHUx6FL4njgmji93kxTlNx2ohPL1YnjFqJZfMYCZwEIaRIdB+uecFGcecpWVZCb5ZQNGrVKAA904LVuGFh1mBLa26vda5sDu7eN0ZcFWX04RVHi7NDiMBBTt55eAoNbWv0HXNj1BHphcQ==; 5:pN6D5Pw1puuasY7C1FELdolA24tbj5bUGySRT5ABaDbTK3r190nU0FWInBnuEyUG4woUwNbCtxkwDOTIy38AjePFKyjN0oIwjG9twHVKl7P0OPiJDTk6L1rFPf0r2s7zSKAUkM1v2vLhlMx6pHYBvWyAMdLGC2U4/rCJWaQndU0=; 7:NtwFLbAkUS3pabKUrqNSujNFb2A7ca2USIcqRkN/3PU8TaUnOTY95QCahW+bWagbhnmKSGYX2qqRVZDR5iDqp1xt0uhKZkFE4kPnHLw/IFNO6+JkpFAfkmRgykqJ8ia6BER2Pr7SxJaqcfpG30onVvT+qIxpnhC1LYJt0Dsbc7LDJg1AiaNbQZn8uZC6NE4dFYPebcG3Mh5/DukVBMa0/VOSii5uVD2gVbl1d6h+IWVH65kmoHg7B9wZrqxpC3hS
x-ms-exchange-antispam-srfa-diagnostics: SOS;SOR;
x-forefront-antispam-report: SFV:SKI; SCL:-1; SFV:NSPM; SFS:(10009020)(39860400002)(396003)(376002)(366004)(346002)(136003)(53754006)(199004)(189003)(53474002)(9326002)(81156014)(74316002)(102836004)(11346002)(6306002)(53936002)(236005)(86362001)(8676002)(81166006)(476003)(26005)(97736004)(53546011)(25786009)(55016002)(107886003)(8936002)(71190400001)(2501003)(7736002)(256004)(6436002)(446003)(2906002)(76176011)(14444005)(54896002)(6246003)(71200400001)(44832011)(186003)(9686003)(5660300001)(4326008)(6506007)(486006)(68736007)(7696005)(229853002)(478600001)(14454004)(6116002)(19609705001)(316002)(99286004)(110136005)(93886005)(106356001)(66066001)(2900100001)(790700001)(5250100002)(296002)(33656002)(3846002)(54906003)(105586002); DIR:OUT; SFP:1101; SCL:1; SRVR:VI1PR07MB3968; H:VI1PR07MB4302.eurprd07.prod.outlook.com; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; A:1; MX:1;
x-ms-office365-filtering-correlation-id: 47df4597-c5de-4bd5-d9d1-08d62a0f8a02
x-microsoft-antispam: BCL:0; PCL:0; RULEID:(7020095)(4652040)(8989299)(4534185)(4627221)(201703031133081)(201702281549075)(8990200)(5600074)(711020)(2017052603328)(7153060)(7193020); SRVR:VI1PR07MB3968;
x-ms-traffictypediagnostic: VI1PR07MB3968:
x-microsoft-antispam-prvs: <VI1PR07MB3968A6B295F3B3DE93CED04A86EA0@VI1PR07MB3968.eurprd07.prod.outlook.com>
x-exchange-antispam-report-test: UriScan:(109105607167333)(195916259791689)(82608151540597)(37575265505322)(248295561703944)(21748063052155)(28532068793085)(190501279198761)(227612066756510);
x-ms-exchange-senderadcheck: 1
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(8211001083)(6040522)(2401047)(5005006)(8121501046)(93006095)(93001095)(10201501046)(3231355)(944501410)(52105095)(3002001)(149066)(150057)(6041310)(20161123564045)(20161123562045)(20161123558120)(201703131423095)(201703031522075)(201702281528075)(20161123555045)(201703061421075)(201703061406153)(20161123560045)(201708071742011)(7699051); SRVR:VI1PR07MB3968; BCL:0; PCL:0; RULEID:; SRVR:VI1PR07MB3968;
x-forefront-prvs: 0815F8251E
received-spf: None (protection.outlook.com: ericsson.com does not designate permitted sender hosts)
x-microsoft-antispam-message-info: qgJv90QzPtmSecqjnG/M6SrAPvKweKnNiUoqIyaHY1rhywRwbBeadodkWynqeGPXSDGmlRbzhP9Ho2JdZ2QTFSdDw1ilwJfwZ+ZCCW5QGyaUG4DOJtf7242kNDAxuQrbEw4SL4g2rxUsxaqB732EANfIDkFOUtifcT3ryACMDLXYkk5uKlVTXmINCz52J7xJj7fhwRXhbaulPOBpE7T/4y8lYr1P9MTDwdoSMmf2T2hS5UdRD0wNzzPBhxo7oSj7Y7A76X6N5A+Qodv8CW9lHicaKh1bega8LAOZxpEdaQNDN4sASKWIE1eueSHOwNxC12ROX2XqiOFO4eXqF1oCrFYkOQeIXz7QMz4EHoDurSY=
spamdiagnosticoutput: 1:99
spamdiagnosticmetadata: NSPM
Content-Type: multipart/alternative; boundary="_000_VI1PR07MB43024A4279206157CEEF955786EA0VI1PR07MB4302eurp_"
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-Network-Message-Id: 47df4597-c5de-4bd5-d9d1-08d62a0f8a02
X-MS-Exchange-CrossTenant-originalarrivaltime: 04 Oct 2018 15:39:14.7041 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 92e84ceb-fbfd-47ab-be52-080c6b87953f
X-MS-Exchange-Transport-CrossTenantHeadersStamped: VI1PR07MB3968
X-OriginatorOrg: ericsson.com
X-Brightmail-Tracker: H4sIAAAAAAAAA02Sa0hTYRjHec85247m4HVqPiqFLgUd5KWs/JCxyA8qTMIITANbeVBxXtiZ mkKxIsFcXhLTZg0VpUyjQsu8pObSZpoWMwiMCSMttAvGmvdLutfAb7/n//8/F15elpa0CrzZ 9CwNp85SqqRCZ0af8DL/YEB4R1Lo6IJvRLNJT0dYltaFciq6qWmZirZMmqnTVKLz8RROlZ7H qUNOXHBO+7gSlWM2UJfbNhO1qKqaKkEsCzgcrv0+WoKcWQkeQmDp1IpIYUdw06xlSNFIwXXD mGC7YHAFDbaaEZo4tylYWdPt9FgRvH/Q6hgsxHIY6AooQU6sO1aB7d6EaJtpfB5eF31D2+yG Y8Dc3EuTTCx03bIJCMdBS9mGQ2ewPyw/rHD0ird6qxd0FNk1TMFgTbcj5IQjYWh12TEU4b2w OPKYIss8YXK6zsGAMTS9+kAT9oDZrxsCkudgaeSJgOhSKG7W7WT2gblOh7aXAe4TwXRPE0OM MDA96qeJMSOEGWv7jqGA7sFyihgmBIvPbIgYMmgo7t05IwPmN18wJNSPwDy1Tleg0Npd5xLO hs6+FQeLsSu8008ztVvPSuMgeNodQiJ+UKWziggHQtF9g2i3Xo9ELciD5/iLmamHDgdz6vRL PJ+dFZzFadrQ1hcaeL4a0Ikmfp40IswiqYtY6NuRJBEo8/iCTCMClpa6i78EbkniFGVBIafO TlbnqjjeiHxYRuopth5rT5TgVKWGy+C4HE7936VYJ28tSsGjldZFWalvQpDbkU+hta6FXgr/ 3Dda2aQ+9peX4nsnLFjudszy2XfWhj0j5ePlV+QGhTxqbM5+rsxlcL/s6oxpXDNkXPTL38P6 lDbY7etdfi1TpfPJB2w5ktDGmLcG77nxU1Vu5o04VOn+1xR/40/8VP1ZzY8zReufZ9p6pAyf pgyT0Wpe+Q9tWvskPgMAAA==
Archived-At: <https://mailarchive.ietf.org/arch/msg/bess/Fw3QBDPDGBDsicxpvV6B32KZ7Wo>
X-Mailman-Approved-At: Thu, 04 Oct 2018 09:01:32 -0700
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 15:39:23 -0000

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>
Sent: Thursday, October 4, 2018 8:06 PM
To: Jaikumar Somasundaram <jaikumar.somasundaram@ericsson.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

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