Re: [bess] FW: Regarding the Alias label usage in EVPN Multihoming

Muthu Arul Mozhi Perumal <muthu.arul@gmail.com> Thu, 07 March 2019 06:58 UTC

Return-Path: <muthu.arul@gmail.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 9A3FE130E64 for <bess@ietfa.amsl.com>; Wed, 6 Mar 2019 22:58:59 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.998
X-Spam-Level:
X-Spam-Status: No, score=-1.998 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.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 bTp2BlbpsmEc for <bess@ietfa.amsl.com>; Wed, 6 Mar 2019 22:58:53 -0800 (PST)
Received: from mail-lj1-x235.google.com (mail-lj1-x235.google.com [IPv6:2a00:1450:4864:20::235]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0519B129C6A for <bess@ietf.org>; Wed, 6 Mar 2019 22:58:53 -0800 (PST)
Received: by mail-lj1-x235.google.com with SMTP id q128so13199890ljb.11 for <bess@ietf.org>; Wed, 06 Mar 2019 22:58:52 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=hYFImAXN77PWkaY84RkMLHQ1c5jJ42HZJsEb+R0sY+w=; b=U9DG+zWy9WHZW7ChSXS4KPUQby14BTHX57O1vhFDI0LSSPZK2p7CZrTEjhpRz/0xmm AKkyjKTHVjYfbW60uI+aK1aHe0REHJx2bk2tSCIqV13vdBT4/RCo9BSfgnEyU/A3xO8X gVEwFLuqYgBL6KOmw3/OnJBiFOQn/vY1b4A5Qy20qHJpdxse4SdmCh5qhESybCZjkF5o 46NT2jpHKn5UXO5xqn81LQ9M1dK/qgCbuxoOiVPurkA99xCAfYxhhkoBtYuRy2/HyMkc 5dWN2YpyYvZQDJfvx6zHMD7FGMw2N5E1zDu0R0kmGEL900hqcnSgy74pi6iI42zQHsi0 o9ZA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=hYFImAXN77PWkaY84RkMLHQ1c5jJ42HZJsEb+R0sY+w=; b=jcoyUIJ1bpREeyk9iTeLFqtko81tKdxhjQ7iyLCTzYkWwIgKa6AyF5bL+bI1NW9twF 8aZqUx3HGPkkxhCU3B9RZR9/RDR0RJwja47i+RklQhxtplTQjrXktA2DdqMpkkBmwYdD /bB5969bM890DYjbFjnDXA/3nfMWUo+SP20meZA4agQE2F6p3z5zAcAtfAFvjxiDgHIs 3ZrX78pzhqTZCayHI4VjoFnJRh8f1d0hloe6v4WoIkig/a5BcGitDiSE1tJj9A4xY9Gi dxEBl0CcBOKgYKEaKtlJoc+KuFsXeVk4dJQfYljfZeoX48BcEwsUO0Gf8Zxm9cYrtIxt wKSw==
X-Gm-Message-State: APjAAAVkJv2TzAefU5dxvK/ttq0liIOpGq18ywXp/Fvm8lu1ynXWvKAm 8UzM9kep0O9TV5AakndL0OcOyE7qRXJcEK4j46o=
X-Google-Smtp-Source: APXvYqzFSo54L+SiTIcSg6sOAn9Qu4KRyz3aoZ6UXrZpOsoXFk33Sp9zkqAs8P2EDMLGD6Nbtl5pJl/zZyJebzlAF5k=
X-Received: by 2002:a2e:6505:: with SMTP id z5mr4885696ljb.180.1551941930804; Wed, 06 Mar 2019 22:58:50 -0800 (PST)
MIME-Version: 1.0
References: <VI1PR07MB4462872475A375E50C33F4C8E2730@VI1PR07MB4462.eurprd07.prod.outlook.com> <VI1PR07MB44620DB939F1ABE51DDED5B6E2730@VI1PR07MB4462.eurprd07.prod.outlook.com> <CAP3Cv1beDHnU0oBheDiG4863QC8vcgMpNkOy9JjkfiFgAWuFkw@mail.gmail.com> <478004F5-9B6E-49F0-9203-57F4953520DB@cisco.com>
In-Reply-To: <478004F5-9B6E-49F0-9203-57F4953520DB@cisco.com>
From: Muthu Arul Mozhi Perumal <muthu.arul@gmail.com>
Date: Thu, 07 Mar 2019 12:22:41 +0530
Message-ID: <CAKz0y8xbMQgWqYk18+zG4_NBF2O+iFGE_+aOzd1LKkMgdNc-1Q@mail.gmail.com>
To: "Luc Andre Burdet (lburdet)" <lburdet@cisco.com>
Cc: chalapathi andhe <chalu.ietf@gmail.com>, "bess@ietf.org" <bess@ietf.org>, Jaikumar Somasundaram <jaikumar.somasundaram@ericsson.com>, Sean Wu <sean.wu@ericsson.com>, "chalapathi.andhe@ericsson.com" <chalapathi.andhe@ericsson.com>
Content-Type: multipart/related; boundary="0000000000007fb4a205837ba342"
Archived-At: <https://mailarchive.ietf.org/arch/msg/bess/uK59ryS0pVxDyRApZrixNSqZaMs>
Subject: Re: [bess] FW: Regarding the Alias label usage in EVPN Multihoming
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, 07 Mar 2019 06:59:00 -0000

My understanding:

For the single-active case in the diagram below, when PE4 receives the A-D
per ES route withdraw it won't know whether PE2 or PE3 will become the new
primary/DF for the <ES, VLAN>, so it will start flooding the traffic
destined to MAC1. Then either PE2 or PE3 will become the new primary/DF for
the <ES, VLAN> and advertise the MAC/IP route for MAC1. PE4 will then start
sending the traffic destined to MAC1 to the new primary.

For the all-active case, when PE4 receives the A-D per ES route withdraw it
will update the nexthop list for MAC1 by removing PE1 from that list. PE4
will then load balance the traffic destined to MAC1 by send it to PE2 and
PE3 using alias label.

Regards,
Muthu

On Wed, Mar 6, 2019 at 7:51 PM Luc Andre Burdet (lburdet) <lburdet@cisco.com>
wrote:

> Hi Chalu,
>
>
>
> Please read 7432 s.8.4: in single-active it is not an aliasing
> label/procedure but a backup-path procedure.
>
> It will answer your questions (both, actually).
>
>
>
> There is no flooding once the MAC is learnt & distributed: cf. that’s the
> point.
>
>
>
>
>
> [image:
> http://www.cisco.com/c/dam/m/en_us/signaturetool/images/banners/standard/09_standard_graphic.png]
>
> *Luc André Burdet*
>
> lburdet@cisco.com
>
> Tel: *+1 613 254 4814*
>
> Cisco Systems Canada Co. / Les Systemes Cisco Canada CIE
>
> Cisco.com <http://www.cisco.com/web/CA/>
>
>
>
>
>
> *From: *BESS <bess-bounces@ietf.org> on behalf of chalapathi andhe <
> chalu.ietf@gmail.com>
> *Date: *Wednesday, March 6, 2019 at 04:15
> *To: *"bess@ietf.org" <bess@ietf.org>
> *Cc: *Sean Wu <sean.wu@ericsson.com>, Jaikumar Somasundaram <
> jaikumar.somasundaram@ericsson.com>, "chalapathi.andhe@ericsson.com" <
> chalapathi.andhe@ericsson.com>
> *Subject: *Re: [bess] FW: Regarding the Alias label usage in EVPN
> Multihoming
>
>
>
>
>
>
>
> Hi All,
>
>
>
> Can you please help us on the following issue.
>
> In the following diagram, PE1, PE2, PE3 are connected to the same ES [ES1]
> in Single active mode, and PE4 is a remote PE.
>
> Let’s say PE1 is advertising the MAC1 route, PE4 will install the MAC1
> with the PE1 as primary path with MAC Label,
>
> and PE2, PE3 as backup with the Alias Label. Now if the PE1 to CE1 link
> goes down, then PE1 withdraw the EAD/ES route
>
> which will be processed by PE4.
>
> Now what should the forwarding state at PE4 ?, PE4 should update the
> forwarding state of MAC1 with the PE2, PE3 Alias label
>
> and any traffic destined to MAC1 should be flooded to PE2, PE3 with the
> Alias labels ?
>
> Or packet should be flooded to PE2, PE3 with the Flood labels ? Or should
> it be some other method ?
>
>
>
> In similar if the ES is operating in all active mode, what should be the
> forwarding state at PE4 ?
>
> PE4 should update the forwarding state of MAC1 with the PE2, PE3 Alias
> label
>
> and any traffic destined to MAC1 should be sent to either PE2 or PE3 with
> the Alias labels [ not flood to both] ?
>
> Or packet should be flooded to PE2, PE3 with the Flood labels  or Alias
> Label ?
>
> Or should it be some other method ?
>
>
>
>
>
> [image: cid:1695247dcc04ce8e91]
>
>
>
>
>
> Thanks,
>
> Chalapathi.
>
> _______________________________________________
> BESS mailing list
> BESS@ietf.org
> https://www.ietf.org/mailman/listinfo/bess
>