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

Jaikumar Somasundaram <jaikumar.somasundaram@ericsson.com> Fri, 05 October 2018 05:07 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 623CD130DDA for <bess@ietfa.amsl.com>; Thu, 4 Oct 2018 22:07:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.755
X-Spam-Level:
X-Spam-Status: No, score=-4.755 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.456, 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, URIBL_BLOCKED=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=PFyC/Mou; dkim=pass (1024-bit key) header.d=ericsson.com header.b=ly0uug7j
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 Y0_UoI7jGIqt for <bess@ietfa.amsl.com>; Thu, 4 Oct 2018 22:07:02 -0700 (PDT)
Received: from sessmg23.ericsson.net (sessmg23.ericsson.net [193.180.251.45]) (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 D409C130DD2 for <bess@ietf.org>; Thu, 4 Oct 2018 22:07:01 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; d=ericsson.com; s=mailgw201801; c=relaxed/simple; q=dns/txt; i=@ericsson.com; t=1538716019; 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=5APXu9wMXjDBcPHeB1GuebET+BI4MIMLoqbP7D2ntj4=; b=PFyC/MouhtYAHVOzqdSH+fvgpMwYGLtbwGaoXOpCIc+ZnnWwm3Q5iaQUdbR4GR4o jy07+La59FDT5ae/IVzaxvtaxXc+JUnDhs1wD79FqwSkvrH3XvIEu9//stD3jVpc 16bD/dsx7Gvo2MOtKMijmzxh8TOXu92x8rRXNYsDQxE=;
X-AuditID: c1b4fb2d-5ecb19c0000055ff-cc-5bb6f1730db0
Received: from ESESSMB502.ericsson.se (Unknown_Domain [153.88.183.120]) by sessmg23.ericsson.net (Symantec Mail Security) with SMTP id A3.6F.22015.371F6BB5; Fri, 5 Oct 2018 07:06:59 +0200 (CEST)
Received: from ESESBMR505.ericsson.se (153.88.183.201) by ESESSMB502.ericsson.se (153.88.183.163) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.1466.3; Fri, 5 Oct 2018 07:06:57 +0200
Received: from ESESBMB504.ericsson.se (153.88.183.171) by ESESBMR505.ericsson.se (153.88.183.201) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.1466.3; Fri, 5 Oct 2018 07:06:57 +0200
Received: from EUR03-AM5-obe.outbound.protection.outlook.com (153.88.183.157) by ESESBMB504.ericsson.se (153.88.183.171) 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; Fri, 5 Oct 2018 07:06:57 +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=5APXu9wMXjDBcPHeB1GuebET+BI4MIMLoqbP7D2ntj4=; b=ly0uug7j9PYXA5sDBpdvvM4Qz0NRgB6REjBW2LBMxWNn9GivOCjuL+PVEjmUW9Mr7evRul73ElrKmu1mNaWvZbo+RuFlQbbAUsEt9/J8nlZY2n/LmU+wU6Uzbo5iXal2Z/tdDkEued58wwKq1pld65w1G4ZpmLaSPujMZ1CYl/c=
Received: from VI1PR07MB4302.eurprd07.prod.outlook.com (20.176.6.159) by VI1PR07MB4591.eurprd07.prod.outlook.com (20.177.56.212) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.1143.10; Fri, 5 Oct 2018 05:06:56 +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.024; Fri, 5 Oct 2018 05:06:55 +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///uRKCAADSgAIAArQxw
Date: Fri, 05 Oct 2018 05:06:55 +0000
Message-ID: <VI1PR07MB430267AB4A374A27E6AAE68386EB0@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> <VI1PR07MB43024A4279206157CEEF955786EA0@VI1PR07MB4302.eurprd07.prod.outlook.com> <EF297F98-D1AC-4D66-8F73-B440789AAB93@nokia.com>
In-Reply-To: <EF297F98-D1AC-4D66-8F73-B440789AAB93@nokia.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [125.16.128.122]
x-ms-publictraffictype: Email
x-microsoft-exchange-diagnostics: 1; VI1PR07MB4591; 6:luS8r2wiTNRkynshew3KJDnymnB6JGuEo16rRIN6Pzj9i/G6s6nG/Nr2OvO5Vs+RTcc9u6sSWmctg18mqoLVwQ6mD0AvJ3cGAQfotc1iA9oeEe5kFvnh/M6AS233J62Q/eOGAsi9OjUVLbAsysdPk6AO0Dmbq0Vx3M080QxLdk9Jp1M4ahCTi/W8slxE8HZLxWYIjvqO95GJ3vkuUSHoYZzTaglGbejCNOnx7Jo+zx1F+RcJyKFzQPSL97E+JLEYhCkjnZptNRngk8rnz4/B2POKCBLnWaU8eHhWN2iWyWRhYVipTbVK61STHaDr8F9jaufidY9oTLgrjYRgrcDeyItjiZdqU4UAsV1iOLWlmqULMDd+7b3ts7Wr/vJKHMaAwmRpQ31XCtFXVNeJyYL5JjicMCoETy5vy/Jw/QTvsKLjLolYUgSG6vfD2ODl8/LuyXSDzPY2F8RfrXBwSdwpXA==; 5:QMNuDSnMnxRop2nV0oHtlKjeLFtgn18XFUnYORoPH2NYuOilFuNumgIjEazii8l+HEX5ygdoaTRrgR5tgvRxasKlxBWQuY1cV9npq7gh5gIQvkcCLidvKuwGxSQ/VEb5T7nMJqB0LQccDnt4YCi4+pR2fcLUy+wJCzRG2VPq0Xg=; 7:V3O2QYZXOdNWrB51QbkZPhrW3tIYjvPouubCGj75Va5EP0TbfUW31zG3bZRgnx/+JL6KrvknqVvrwjpy1RIhtzIbbUO0MlLwvZu0LijUQ5uFLYQ+q/xgIV+InxCCWJt9zQqrd58hMwcQGEdOOT8i424tQUmvKt9+SaG3DsOGrEywnFExKJomZHgxH+xT+Kur3hUqakZWNQx0DvpxM+3mV+SDEPXsfB42Z+Wi1JdAVxtkK/8dg22g3w6PDZAOMMz8
x-ms-exchange-antispam-srfa-diagnostics: SOS;SOR;
x-forefront-antispam-report: SFV:SKI; SCL:-1; SFV:NSPM; SFS:(10009020)(396003)(136003)(346002)(366004)(39860400002)(376002)(53754006)(51444003)(189003)(199004)(53474002)(68736007)(105586002)(236005)(14454004)(9686003)(6306002)(19609705001)(6116002)(229853002)(5250100002)(790700001)(53546011)(66066001)(25786009)(14444005)(2501003)(2900100001)(55016002)(44832011)(8676002)(256004)(2906002)(8936002)(26005)(54906003)(86362001)(186003)(3846002)(296002)(476003)(6506007)(107886003)(7736002)(7696005)(33656002)(478600001)(316002)(99286004)(6436002)(97736004)(93886005)(53936002)(74316002)(71190400001)(106356001)(71200400001)(4326008)(76176011)(5660300001)(81166006)(102836004)(6246003)(54896002)(486006)(81156014)(11346002)(446003)(110136005); DIR:OUT; SFP:1101; SCL:1; SRVR:VI1PR07MB4591; H:VI1PR07MB4302.eurprd07.prod.outlook.com; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; MX:1; A:1;
x-ms-office365-filtering-correlation-id: 608e1113-93d5-4edb-9e1e-08d62a805f00
x-microsoft-antispam: BCL:0; PCL:0; RULEID:(7020095)(4652040)(8989299)(4534185)(4627221)(201703031133081)(201702281549075)(8990200)(5600074)(711020)(2017052603328)(7153060)(7193020); SRVR:VI1PR07MB4591;
x-ms-traffictypediagnostic: VI1PR07MB4591:
authentication-results: spf=none (sender IP is ) smtp.mailfrom=jaikumar.somasundaram@ericsson.com;
x-microsoft-antispam-prvs: <VI1PR07MB4591AFCB87508A77578A1A0586EB0@VI1PR07MB4591.eurprd07.prod.outlook.com>
x-exchange-antispam-report-test: UriScan:(82608151540597)(109105607167333)(195916259791689)(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)(8121501046)(5005006)(93006095)(93001095)(10201501046)(3231355)(944501410)(52105095)(3002001)(149066)(150057)(6041310)(20161123562045)(20161123558120)(201703131423095)(201703031522075)(201702281528075)(20161123555045)(201703061421075)(201703061406153)(20161123564045)(20161123560045)(201708071742011)(7699051)(76991048); SRVR:VI1PR07MB4591; BCL:0; PCL:0; RULEID:; SRVR:VI1PR07MB4591;
x-forefront-prvs: 0816F1D86E
received-spf: None (protection.outlook.com: ericsson.com does not designate permitted sender hosts)
x-microsoft-antispam-message-info: CUvd3Eoss4LBdsZyFwn5TvU71I4a46v30vRNm5J1fuutAVPAwGB1fOjlnoygvMbCPdZfHA53aPWvMhw0u6WeW+b4sU2QZzJJuoW3NipMncLlVKR5Q5J9F1LPsd0GaJNJIYlDnYw6GohmvBZvtQJiRnAaCohXRykL5iDL/sG24DgeMwutzLHDXE4EnwhIzVK6Tig7fxJJ2hcZgYlhw2gIgp6ZPRerSw+AwFh9F5oXiDtqefZjZgWKasgXlwD9W3bT5wp+9P0989Ku07MPD85zQQQ01C6ExFB2WnkRG4Ay7IXRrkiXCa9ib6nObRK/J5RTa9PcODk1i2sjtXNOSMaeuNDA+mfWsDPxLn8Qi5oMm8c=
spamdiagnosticoutput: 1:99
spamdiagnosticmetadata: NSPM
Content-Type: multipart/alternative; boundary="_000_VI1PR07MB430267AB4A374A27E6AAE68386EB0VI1PR07MB4302eurp_"
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-Network-Message-Id: 608e1113-93d5-4edb-9e1e-08d62a805f00
X-MS-Exchange-CrossTenant-originalarrivaltime: 05 Oct 2018 05:06:55.6935 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 92e84ceb-fbfd-47ab-be52-080c6b87953f
X-MS-Exchange-Transport-CrossTenantHeadersStamped: VI1PR07MB4591
X-OriginatorOrg: ericsson.com
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFlrLKsWRmVeSWpSXmKPExsUyM2J7hW7xx23RBpdX6lqsOD6T2eLuj79s DkweS5b8ZPK4e+sSUwBTFJdNSmpOZllqkb5dAlfGqo/tLAWn/jBVbH7czdTAeOUTUxcjJ4eE gIlE+7srQDYXh5DAUUaJ3S8+s0E4XxklVn1oZ4dzTl/ZDlW2mEnizI1+ZhCHRWACs8S/5XcZ ITITmSTWfWxjhXAeMkpcnHQFqIyDg03AQeLgTlWQjSICORKfZ19mB7GZBWIkDrQ+YwSxhQU8 JS6t2MsMUeMlsbPnMyuEHSWxedp1MJtFQEVi7qt1YDYvUO/+yQ1QJ51jlvh/9AQryC5OAVuJ K4dDQGoYBcQkvp9awwSxS1zi1pP5UF8LSCzZc54ZwhaVePn4HyuErSSxeeYLqBpZiUvzu8Ee kxDYxy7xraeXBSJhKHF85X5miMQzNolFHU1QHb4S/at2QHUcZ5RoaJwP1aElMfP2ciaIk1Il fpxaB7UuW2Lmrk0sExgNZyG5EMLOl3jffpFlFtinghInZz4BsjmA4poS63fpQ5QoSkzpfsgO YWtItM6Zy44svoCRfRWjaHFqcXFuupGxXmpRZnJxcX6eXl5qySZGYCI6uOW37g7G1a8dDzEK cDAq8fA6P90WLcSaWFZcmXuIUYKDWUmEN7wEKMSbklhZlVqUH19UmpNafIhRmoNFSZxXb9We KCGB9MSS1OzU1ILUIpgsEwenVAOj6uZpwm+Dzi/wexpq6fXLLe/hvez06zNUmryOzXUx57I9 Gc+exCXo7GR3573qnhcfoov0l8imRDdpcP86M6dtq+X0mG/v9jI2xx8zDVberLv8t+iFr8cF VizpnPGmcq3YqsZ31x36HhqnlukfT+LlU/0mcd9/ndC+/Q/1J3FELe49o+gkemKFEktxRqKh FnNRcSIAyrJbFUADAAA=
Archived-At: <https://mailarchive.ietf.org/arch/msg/bess/2aUYbulZqOmQXlTlmshVtNINZ6Y>
X-Mailman-Approved-At: Tue, 09 Oct 2018 07:17:13 -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: Fri, 05 Oct 2018 05:07:09 -0000

Thanks Jorge.

I think that this optimization is not mentioned in the RFC 7432.

Section 8.5 of RFC 7432:

      In the case of link or port failure, the affected PE withdraws its
      Ethernet Segment route.  This will re-trigger the service carving
      procedures on all the PEs in the redundancy group.  For PE node
      failure, or upon PE commissioning or decommissioning, the PEs
      re-trigger the service carving.

Section 13.2.1 of RFC 7432:


  - If the PE is not the designated forwarder on any of the ESIs for

     the Ethernet tag, the default behavior is for it to drop the

     packet.

Section 14.1.1 of RFC 7432:


   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.

Thanks & Regards
Jaikumar S
From: Rabadan, Jorge (Nokia - US/Mountain View) <jorge.rabadan@nokia.com>
Sent: Thursday, October 4, 2018 10:11 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

Hi Jai,

Yes, but see my other email.. if you only have two PEs in the ES, you may optimize things.
Thanks.
Jorge

From: Jaikumar Somasundaram <jaikumar.somasundaram@ericsson.com<mailto:jaikumar.somasundaram@ericsson.com>>
Date: Thursday, October 4, 2018 at 5:39 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

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