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

chalapathi andhe <chalu.ietf@gmail.com> Wed, 06 March 2019 09:15 UTC

Return-Path: <chalu.ietf@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 B8DBF130ED1 for <bess@ietfa.amsl.com>; Wed, 6 Mar 2019 01:15:14 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.594
X-Spam-Level:
X-Spam-Status: No, score=-0.594 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_IMAGE_ONLY_28=1.404, HTML_IMAGE_RATIO_08=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=no 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 2OMDIwevuMIa for <bess@ietfa.amsl.com>; Wed, 6 Mar 2019 01:15:12 -0800 (PST)
Received: from mail-ot1-x32f.google.com (mail-ot1-x32f.google.com [IPv6:2607:f8b0:4864:20::32f]) (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 AB510130DF1 for <bess@ietf.org>; Wed, 6 Mar 2019 01:15:12 -0800 (PST)
Received: by mail-ot1-x32f.google.com with SMTP id v20so10121877otk.7 for <bess@ietf.org>; Wed, 06 Mar 2019 01:15:12 -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=jp9MF5yMAomE11lSJ3f6LaQfFZGmKSfqXYoZBEQLA6E=; b=qEpA5hpbqyFgkBmLEf6Jxx0Pkt2JTuyJ/CPUTDQw9COoLwgQ8sRcdYh+fjYOsQeNJL OSxKo+u0sJkVDkxHQ77PY7caMUwVVKKWShY36rVCjPiPt+RC8jDWthQrWBZp0xJEsPl9 OUE82qM6lMXFweogxnsc1haaHad4PBnqeiuKOeNWXqAlY2q3DKK/dsNwJmQ58/DCxwBC OsF7q2cI1w4/Sz5EgaD/nUFS0ihbhZ1QOMs8gqaBtYYpxrZ0SCh2K578lpuLhJ6vycNu p38+eUBdwYIR1Nmdow4X/cjk0umRzBxCB4U8iYVCr9S8RUDE45DLbRe9zcWbPSYlW2UM Bm2g==
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=jp9MF5yMAomE11lSJ3f6LaQfFZGmKSfqXYoZBEQLA6E=; b=mxrU5r/j3lyLZF+NW0hqZSl9ade66k8mXI6hcxZKc2WHmQzg0O8WpYi9Zg0SdI4utG ipd1rYcQZSaCahFzOThYRGWTtouXz/xE7L3kgEf400FM6MYfBFZgoedvL1ZthjRvvPm0 YQcdDQK5pzT5miNDJJzxF+E+JnS+D/oqIpGOsXK/YbIOODkfY29ITJMooU7W4/iY0nPE ZOTcvzOuc/bflxeRjz9JHzGzoGZCt3umqkt6TDR88Pgjv8IA3O8TYA6aaxs1tz1Q7VnG xyu53RRgH/7N6cNSKOSYRoBmWTdTM8y55xVJSBnPG2gmfSsSyC7UEJkpbf+52QOGm1So Gy9A==
X-Gm-Message-State: APjAAAVxDYLSAT38UMvADusKT17+cm2qCvNt9auVXcgiZP0CPsBY1vmd rV9rWluqR1G+EO9SPQCtl+lRxV7wBd9FQhuvhrnU1TUwGQ==
X-Google-Smtp-Source: APXvYqxljoJ/zr9N8v7sttf2trhwiszM8+xKDKkKQ57gXSd1dWh9HM0ZvPfYJnycYnmLy6NlsgvHjbMBrFZN9FtDkvw=
X-Received: by 2002:a9d:5e83:: with SMTP id f3mr3809996otl.181.1551863710831; Wed, 06 Mar 2019 01:15:10 -0800 (PST)
MIME-Version: 1.0
References: <VI1PR07MB4462872475A375E50C33F4C8E2730@VI1PR07MB4462.eurprd07.prod.outlook.com> <VI1PR07MB44620DB939F1ABE51DDED5B6E2730@VI1PR07MB4462.eurprd07.prod.outlook.com>
In-Reply-To: <VI1PR07MB44620DB939F1ABE51DDED5B6E2730@VI1PR07MB4462.eurprd07.prod.outlook.com>
From: chalapathi andhe <chalu.ietf@gmail.com>
Date: Wed, 06 Mar 2019 14:44:59 +0530
Message-ID: <CAP3Cv1beDHnU0oBheDiG4863QC8vcgMpNkOy9JjkfiFgAWuFkw@mail.gmail.com>
To: bess@ietf.org
Cc: Jaikumar Somasundaram <jaikumar.somasundaram@ericsson.com>, Sean Wu <sean.wu@ericsson.com>, chalapathi.andhe@ericsson.com
Content-Type: multipart/related; boundary="000000000000397f280583696d83"
Archived-At: <https://mailarchive.ietf.org/arch/msg/bess/29KWktTfmRwHO93UjIdK3db4vMQ>
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: Wed, 06 Mar 2019 09:15:15 -0000

>
> 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 ?
>
>
>
>
>
>
>
>
>
> Thanks,
>
> Chalapathi.
>