Re: [bess] VXLAN BGP EVPN Question
Gyan Mishra <hayabusagsm@gmail.com> Wed, 22 April 2020 22:48 UTC
Return-Path: <hayabusagsm@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 0F0803A0C70 for <bess@ietfa.amsl.com>; Wed, 22 Apr 2020 15:48:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.097
X-Spam-Level:
X-Spam-Status: No, score=-2.097 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, 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 m6NGKGO9co6D for <bess@ietfa.amsl.com>; Wed, 22 Apr 2020 15:48:09 -0700 (PDT)
Received: from mail-il1-x134.google.com (mail-il1-x134.google.com [IPv6:2607:f8b0:4864:20::134]) (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 1B7A03A0B3D for <bess@ietf.org>; Wed, 22 Apr 2020 15:48:09 -0700 (PDT)
Received: by mail-il1-x134.google.com with SMTP id e8so3681977ilm.7 for <bess@ietf.org>; Wed, 22 Apr 2020 15:48:09 -0700 (PDT)
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; bh=IseA2Y5tpkWuS/DtoASO7Pn9q4rx3IzIj31wHPwtANU=; b=dPFPisuHDbOq+Jx0k+m0lESsZQ94zeUR0IR4TModLPoaQ4Wm/tyz8D6yGm8UFAg24D IpFQqpZB5jKXwRwjZBjkHu7YPZhmLAsjV0MnFrIxmHRYOzEzKNu/rWqF1L77+oDKazuH QtZ5wPReszbOxWsYMjcEjE4pPeRt9NubH1U2hBf1JoH0qeUiLXHFUP/D4p/TgfVApbVI +r+bg7EuMWsslXr8MeyuQ/BcJm0jtux8fYQT3m/QTPOqsKOtFTOg9PFVOMDQDuoDO6yD kV69GVQiVliXQp3D7SLKHNQLJsDwHYdpS9RK2lk8JhlNQLTwlsJrNPdcMmEkHb5VLsib adQQ==
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; bh=IseA2Y5tpkWuS/DtoASO7Pn9q4rx3IzIj31wHPwtANU=; b=m9aY/3rWWy2RtubDFxG1jmx3NhVOwOsYIAONZqwWjnXmhSfc2S4I32jkE1auAQKcHM HteMlDKOPWugKjNrjq8oPVjiFn3Y+VPa7y5/8fA0+l/H/mClk2FVbejLVcTn+E2x2S1V I5B6oXPrS41GspAxjsEwy+JeXWYQaH7C/5rIxn+7BAU1voGyCNclGBcIx34sR6rd9eHJ pnMKWiGpFA4pr17ozLB4hiDVNrHD7lFduOL5+zBLhtzigGXbZMcJgiT5NTHmv7mm9B5R QkLelhXY54wqzgJOWjscWMBncPQ7JTdMUfuUBt9FfuyHDs/0LEZl13LpsGVD73zGGm5i 581g==
X-Gm-Message-State: AGi0PuamastR0jNCMIC2nMJrk7z7DF33i8qHALzpnWhlsdK4ZQVEv3nT xWBh4o5F28mxSHMdd6tImWyF5s8SFraBDAHkPg+e2abxMgo=
X-Google-Smtp-Source: APiQypIZnVN2I93QNpUNms5UPkt6v5/iGE2PSaV9ilhgSZGvpaPDrIjgCLyZXb/Yy04QcUeSDYiM3nNBofwFtMaztL8=
X-Received: by 2002:a92:8350:: with SMTP id f77mr684907ild.257.1587595688140; Wed, 22 Apr 2020 15:48:08 -0700 (PDT)
MIME-Version: 1.0
References: <CABNhwV1kPDhRcuqS8GOpTiKoyk_QHKVXa582JUznLvKfXQe54w@mail.gmail.com>
In-Reply-To: <CABNhwV1kPDhRcuqS8GOpTiKoyk_QHKVXa582JUznLvKfXQe54w@mail.gmail.com>
From: Gyan Mishra <hayabusagsm@gmail.com>
Date: Wed, 22 Apr 2020 18:47:37 -0400
Message-ID: <CABNhwV352jKVSu2Jwf9dRgzmjc05gvmLo_CL5EGuR12en-7Z_A@mail.gmail.com>
To: BESS <bess@ietf.org>
Content-Type: multipart/alternative; boundary="00000000000009f43805a3e8ed18"
Archived-At: <https://mailarchive.ietf.org/arch/msg/bess/KbImsBhvTSOMR_eaJdjr86A9SF4>
Subject: Re: [bess] VXLAN BGP EVPN Question
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, 22 Apr 2020 22:48:12 -0000
In the description of the vxlan BGP evpn scenario has a typo on the multisite feature segmented LSP inter pod with the RT auto rewrite which is similar to MPLS inter-as option b not a. Kind regards Gyan On Wed, Apr 22, 2020 at 5:57 PM Gyan Mishra <hayabusagsm@gmail.com> wrote: > > All > > Had a question related to vxlan BGP EVPN architecture specifications > defined in BGP EVPN NVO3 overlay RFC 8365 and VXLAN data plane RFC 7348. > > In a Data Center environment where you have a multiple PODs individual > fabrics per POD connected via a super spine extension using a Multi site > feature doing auto rewrite of RTs to stitch the NVE tunnel between pods > similar to inter-as option A. > > So in this scenario where you have vlan sprawl everywhere with L2 and L3 > VNIs everywhere as if it were a a single L2 domain. The topology is a > typical vxlan spine leaf topology where the L3 leafs are the TOR switch so > very small physical L2 fault domain. So I was wondering if with the vxlan > architecture if this feature below is possible or if their is a way to do > so in the current specification. > > Cisco use to have a DC product called “fabric path” which was based on > conversation learning. > > Is there any way with existing vxlan BGP evpn specification or maybe > future enhancement to have a Mac conversation learning capability so that > only the active mac’s that are part of a conversations flow are the mac > that are flooded throughout the vxlan fabric. That would really help > tremendously with arp storms so if new arp entries are generated locally on > a leaf they are not flooded through the fabric unless their are active > flows between leafs. > > Also is there a way to filter type 2 Mac mobility routes between leaf > switches at the control plane level based on remote vtep or maybe other > parameters. That would also reduce arp storms BUM traffic. > > Kind regards > > Gyan > -- > > Gyan Mishra > > Network Engineering & Technology > > Verizon > > Silver Spring, MD 20904 > > Phone: 301 502-1347 > > Email: gyan.s.mishra@verizon.com > > > > -- Gyan Mishra Network Engineering & Technology Verizon Silver Spring, MD 20904 Phone: 301 502-1347 Email: gyan.s.mishra@verizon.com
- [bess] VXLAN BGP EVPN Question Gyan Mishra
- Re: [bess] VXLAN BGP EVPN Question Gyan Mishra
- Re: [bess] VXLAN BGP EVPN Question Gyan Mishra
- Re: [bess] VXLAN BGP EVPN Question Jeff Tantsura
- Re: [bess] VXLAN BGP EVPN Question Gyan Mishra
- Re: [bess] VXLAN BGP EVPN Question Rabadan, Jorge (Nokia - US/Mountain View)
- Re: [bess] VXLAN BGP EVPN Question Krzysztof Grzegorz Szarkowicz
- Re: [bess] VXLAN BGP EVPN Question Gyan Mishra
- Re: [bess] VXLAN BGP EVPN Question Rabadan, Jorge (Nokia - US/Mountain View)
- Re: [bess] VXLAN BGP EVPN Question Lukas Krattiger (lkrattig)
- Re: [bess] VXLAN BGP EVPN Question Gyan Mishra
- Re: [bess] VXLAN BGP EVPN Question Rabadan, Jorge (Nokia - US/Mountain View)
- Re: [bess] VXLAN BGP EVPN Question Gyan Mishra
- Re: [bess] VXLAN BGP EVPN Question Gyan Mishra
- Re: [bess] VXLAN BGP EVPN Question Rabadan, Jorge (Nokia - US/Mountain View)
- Re: [bess] VXLAN BGP EVPN Question Gyan Mishra
- [bess] Fwd: VXLAN BGP EVPN Question Gyan Mishra
- Re: [bess] VXLAN BGP EVPN Question John E Drake
- Re: [bess] VXLAN BGP EVPN Question Gyan Mishra
- Re: [bess] VXLAN BGP EVPN Question Acee Lindem (acee)
- Re: [bess] VXLAN BGP EVPN Question Gyan Mishra
- Re: [bess] VXLAN BGP EVPN Question Jeff Tantsura
- Re: [bess] VXLAN BGP EVPN Question Gyan Mishra
- Re: [bess] VXLAN BGP EVPN Question Gyan Mishra