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

Jaikumar Somasundaram <jaikumar.somasundaram@ericsson.com> Fri, 05 October 2018 04:59 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 649D7130DCD for <bess@ietfa.amsl.com>; Thu, 4 Oct 2018 21:59:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.299
X-Spam-Level:
X-Spam-Status: No, score=-4.299 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, 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=FvCmE3Oc; dkim=pass (1024-bit key) header.d=ericsson.com header.b=AAJeBTcM
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 qwbemKdjr6m6 for <bess@ietfa.amsl.com>; Thu, 4 Oct 2018 21:59:22 -0700 (PDT)
Received: from sessmg22.ericsson.net (sessmg22.ericsson.net [193.180.251.58]) (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 CD817130DD4 for <bess@ietf.org>; Thu, 4 Oct 2018 21:59:21 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; d=ericsson.com; s=mailgw201801; c=relaxed/simple; q=dns/txt; i=@ericsson.com; t=1538715559; 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=lFbMJ+R0us5nlHBBZujH+9F87FR/6E+y5eUu8YffTAU=; b=FvCmE3OcypsFwuBGjYTcXQPZ0OjqXGY1KXrfRzzUQF0atH7C3w+MMv1Lyn1/YxMO 4w+cF2ZGUoeynNxARmJFJivI1SKTSUOxoUgXYrPhi/MmG6uN4k8IGS+w8hnkWn5J aFUMLZ/f7+GvlxoI2PlnIKg1fSvs4k6bvhTkABhIZoI=;
X-AuditID: c1b4fb3a-9b7ff70000002fc1-8a-5bb6efa76ee1
Received: from ESESSMB501.ericsson.se (Unknown_Domain [153.88.183.119]) by sessmg22.ericsson.net (Symantec Mail Security) with SMTP id D2.88.12225.7AFE6BB5; Fri, 5 Oct 2018 06:59:19 +0200 (CEST)
Received: from ESESBMB502.ericsson.se (153.88.183.169) 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; Fri, 5 Oct 2018 06:59:18 +0200
Received: from EUR04-HE1-obe.outbound.protection.outlook.com (153.88.183.157) by ESESBMB502.ericsson.se (153.88.183.169) 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 06:59:18 +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=lFbMJ+R0us5nlHBBZujH+9F87FR/6E+y5eUu8YffTAU=; b=AAJeBTcMoH78PdMuJhicacEm7cw5jEMMOama6nKDCd5l8iKCanjMmVwdqdZgjSa4RhrQqRjuHcbwlEoP1aDowSb3Z4gmLX20JkqKjjwG+hYU08x0qrpmpW0j8k+wHZOovr9qrqoR4dpZZb3M1lMpK7XrMZcU5obb2xTgO/EIQzk=
Received: from VI1PR07MB4302.eurprd07.prod.outlook.com (20.176.6.159) by VI1PR07MB4608.eurprd07.prod.outlook.com (20.177.56.217) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.1207.17; Fri, 5 Oct 2018 04:59:16 +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 04:59:15 +0000
From: Jaikumar Somasundaram <jaikumar.somasundaram@ericsson.com>
To: "Mrinmoy Ghosh (mrghosh)" <mrghosh@cisco.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: AQHUW7tPwY67GDKFZkSdu6BevJADsqUO0DWQgAAs0YD//+K7sIAAaW+A///uRKCAACvsgIAAsK0w
Date: Fri, 05 Oct 2018 04:59:15 +0000
Message-ID: <VI1PR07MB4302903A1D91E7876F59202B86EB0@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> <bc55821dd0774af78d92ca382101257a@XCH-RTP-019.cisco.com>
In-Reply-To: <bc55821dd0774af78d92ca382101257a@XCH-RTP-019.cisco.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; VI1PR07MB4608; 6:9Wd/lqhzVZNxc/QQe0HgbfhF9qDiJKo/ZERin58oAr5GbWZDTIB2octQpjq2DBKVS8tWgqS4hxWpKLDFBR9Qw+1GUtFvgWT5LPrXwsFzF5FL3yiwITvF1DQcn1/BgIC6Fm5DDSgzmd6UPu6vDlDBjMewSsXMv0Uzzbx7yowRsBpX+AiKZF+Z976pFCa7PqJrsbQSvgrj/XR6zzhWDE/q28tfLguTt/2Q8AlnbsAzrKFaKGH2/sZt7IeJ5RCmx3FcK2g9hqpTznxETn4LiFNawlk7SYBhcCWtwJ5BXYemHtFOs7SORzg1LJCf9lx4OgngGSadglwT8ScC/BmJJ5kmdZBaLazdtcArh7LV2sL2xREkQ+/YpwXMiJh2GUmMW+bw/5PeWBNIjC7HI9aQbYtn7Rg0WYnWK1lDznmwBjAWW/St8yzAKUjxyutY/gzzI36EEUVKy4ZskBQM5YQWCGbRZA==; 5:PFYE1dgkVEHLiEkOdEziESLhnRD8bGN6LVybHr1XolQjAn0TzBiCO8wgZzU4U7oHakUy3IyVWiywXlFWq5OlVOnBothflKtZ7S3y3krO7CS9Y7ZD5zJEN8DRJ4JN31gRvuROYgy8YA6JW+Qlk/Jj3V8LkM9ebmfMzdbW1TNLB5s=; 7:fDaPE3L2iDzbpy1tnfzUK2tW0jhnAq1G5hH37rCBWRpmNVN0d/BB2VqI/mR2koRPNbsrJ/7e7Pwz1edgm+K+GJXvZfdkHb/g2B49+q4qbUzyFqckHfuZXBPXuqETP1mtShA4oc3qZQLXIpeJgN9GYfcjYf88Gdkp77xj1GeEEeljMPBKthqavRyzWE5dr0EdN8ZCFWy6kXnGNr/nPK7mPxYYv/AVqNgjq0ikD7iL7pzMH4WrGg27yhSgHDyE/xB6
x-ms-exchange-antispam-srfa-diagnostics: SOS;SOR;
x-forefront-antispam-report: SFV:SKI; SCL:-1; SFV:NSPM; SFS:(10009020)(346002)(136003)(396003)(376002)(39860400002)(366004)(53754006)(53474002)(189003)(199004)(53936002)(33656002)(6346003)(9686003)(236005)(54896002)(6306002)(102836004)(2501003)(54906003)(110136005)(5250100002)(19609705001)(2906002)(486006)(8676002)(53546011)(6506007)(6436002)(446003)(11346002)(8936002)(55236004)(476003)(81166006)(81156014)(186003)(7696005)(229853002)(26005)(99286004)(68736007)(76176011)(7736002)(74316002)(44832011)(2900100001)(71190400001)(71200400001)(93886005)(316002)(3846002)(97736004)(256004)(14454004)(86362001)(14444005)(5660300001)(4326008)(478600001)(790700001)(6116002)(6246003)(106356001)(25786009)(107886003)(66066001)(105586002)(55016002); DIR:OUT; SFP:1101; SCL:1; SRVR:VI1PR07MB4608; H:VI1PR07MB4302.eurprd07.prod.outlook.com; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; MX:1; A:1;
x-ms-office365-filtering-correlation-id: 62cf4a92-169d-4b59-b454-08d62a7f4c82
x-microsoft-antispam: BCL:0; PCL:0; RULEID:(7020095)(4652040)(8989299)(4534185)(7168020)(4627221)(201703031133081)(201702281549075)(8990200)(5600074)(711020)(2017052603328)(7153060)(7193020); SRVR:VI1PR07MB4608;
x-ms-traffictypediagnostic: VI1PR07MB4608:
x-microsoft-antispam-prvs: <VI1PR07MB46080EE44634E5F50B3486B686EB0@VI1PR07MB4608.eurprd07.prod.outlook.com>
x-exchange-antispam-report-test: UriScan:(95692535739014)(37575265505322)(248295561703944)(195916259791689)(82608151540597)(109105607167333)(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)(3231355)(944501410)(52105095)(10201501046)(3002001)(149066)(150057)(6041310)(20161123562045)(201703131423095)(201702281528075)(20161123555045)(201703061421075)(201703061406153)(20161123558120)(20161123560045)(20161123564045)(201708071742011)(7699051)(76991048); SRVR:VI1PR07MB4608; BCL:0; PCL:0; RULEID:; SRVR:VI1PR07MB4608;
x-forefront-prvs: 0816F1D86E
received-spf: None (protection.outlook.com: ericsson.com does not designate permitted sender hosts)
authentication-results: spf=none (sender IP is ) smtp.mailfrom=jaikumar.somasundaram@ericsson.com;
x-microsoft-antispam-message-info: Y0lZgFpp7j4AXt00I2R7iozyqRe0xC65+8uD5qZFlmYasJiYZ1/pFAOTK8ZeZYYckDrgaBUEUr08Te01oFVJBpoDN87Eg+kT1bug5ilSeGg02uvmb5nQC7gIfUeyqOUJ7i1SfSXKd5tVkc2H/WWZHhCZ5jEZ8NM9jyuDwA9SxYrBkQDNNJoCjuThV9bt72kElVmybfV0Vl5U7NNnzwZXnAsBEkhO0TpYOJD4rSJr+nOcWcLWM3lL4IMEYHJCV7rtKQU+FxeFmvjv+R06JnAXkvJgq0dgiy1hhXhE3FQeIUTrc/CuKUKm8zQ3x8RdiJGCPmnd0ndPbe7JHaMHsv0m6ID86sLn6+M+rYpGCVlN6ug=
spamdiagnosticoutput: 1:99
spamdiagnosticmetadata: NSPM
Content-Type: multipart/alternative; boundary="_000_VI1PR07MB4302903A1D91E7876F59202B86EB0VI1PR07MB4302eurp_"
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-Network-Message-Id: 62cf4a92-169d-4b59-b454-08d62a7f4c82
X-MS-Exchange-CrossTenant-originalarrivaltime: 05 Oct 2018 04:59:15.1882 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 92e84ceb-fbfd-47ab-be52-080c6b87953f
X-MS-Exchange-Transport-CrossTenantHeadersStamped: VI1PR07MB4608
X-OriginatorOrg: ericsson.com
X-Brightmail-Tracker: H4sIAAAAAAAAA02Sa0iTYRTHed7LfB3NnubtYCg17SbeKxghpoJhZiF+SbSwkW8qzs32Lksh 2Qet0DJDg7a8ZAotEeZtXipLl2HaRfMSZvlhqFmWWV4yMSVf3wV++z3nnP855394GFLaSLsx qSotq1EplDKRmNLHtVz0fTDbnBBwe3G/3NitJ+Vjf1ZF8rWhQjKUjCxZqacjq6uXicix0QEi howXByexytRMVuMfckacMtZmITJ0k8QlS919pEMjH4l8ZM8APgDmsm5RPhIzUvwCQf+HDppP SPEigmKDm8BVBPQ0qHmmcBEJC9+UguAWAdcW3iDhYUXw462BykcMI8Kh0Nm2i4874bsIpsxX KV5N4lPQkfcZ8eyIj8KAsZ3k2QlHQdv1eVrgePj0u0skTPOCwplcgu8pWdeOPY4SFnpPwvAc w7M9jgDrbN6GG4RdYKm3lhBGucLoRIXNJYbqJ32kwM7wdXyNFlgGjfovthp3GKgo2PAC+Kkd mOZabIJA6H74zMZTIqh7flDg42B9PUcLgn4EBrPR1tUbuq4M2QRpYBp/RwpFfQj0zTqRkPCA mhtWqggFGDZtK7AaykoWaZ4leBv06Ccow/oBSLwPTI/8hZKdUFJgtRN4L+SVltltjt9DdjXI mWM5Lj05KMiP1aSe5Ti1yk/FahvQ+lfqbFo51Io6p8IsCDNItkUinmxOkNKKTC4r3YKAIWVO kpPa9ZAkSZGVzWrUiZoLSpazoO0MJXOVhJ+Tx0txskLLprFsBqv5nyUYezcdCnf0jXOxRlSe qBy+vJoTO9NV73BssK8+xuw37WnunU/61aTcvSchxGN6yZUKdr8ZlV3YOBP/0uirW5aXxNYO 7zA5to9UDI4Ma1XNf++gI5NR6sJXpVU/y32VxbSPQ8332NwIU4sH0Tp4OGdrYpiPp9G74nT1 +WivaMYjtLyzI11GcSmKQG9Swyn+AdLkUzhGAwAA
Archived-At: <https://mailarchive.ietf.org/arch/msg/bess/bQxaljDeEvcj46x-2h19UvBguec>
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 04:59:27 -0000

Thanks Mrinmoy.
Response in-lined.

From: Mrinmoy Ghosh (mrghosh) <mrghosh@cisco.com>
Sent: Thursday, October 4, 2018 11:40 PM
To: Jaikumar Somasundaram <jaikumar.somasundaram@ericsson.com>; 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 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.
[Jai] RFC 7432 does not mention anything about this.
<snip of 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.
<snip end>
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<mailto: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<mailto:jorge.rabadan@nokia.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 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