Re: [bess] EVPN VPWS BDF forwarding behavior at MH site

"Thirumavalavan Periyannan (thiperiy)" <thiperiy@cisco.com> Fri, 09 August 2019 21:20 UTC

Return-Path: <thiperiy@cisco.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 2D0C3120077 for <bess@ietfa.amsl.com>; Fri, 9 Aug 2019 14:20:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.5
X-Spam-Level:
X-Spam-Status: No, score=-14.5 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_HI=-5, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.com header.b=bZJwTIEe; dkim=pass (1024-bit key) header.d=cisco.onmicrosoft.com header.b=NWnvOq8D
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 vuIX6ygg7iXF for <bess@ietfa.amsl.com>; Fri, 9 Aug 2019 14:20:41 -0700 (PDT)
Received: from alln-iport-2.cisco.com (alln-iport-2.cisco.com [173.37.142.89]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7FAE312006B for <bess@ietf.org>; Fri, 9 Aug 2019 14:20:41 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=54186; q=dns/txt; s=iport; t=1565385641; x=1566595241; h=from:to:cc:subject:date:message-id:references: in-reply-to:mime-version; bh=1BUjOWwMwyd7COKPqyeR9VQH69odOuli2EhZx7D01FU=; b=bZJwTIEeXN0y1rRhKdMksCD4IYKSVyxepXpQMi+l/MclRxHTXi4lycxU gI9vqCYdN7URIK1prY0toj0JTLiBf5a+MdHI/3B3ZVZx+xauOixO7mtpd Ib/0vFLvS0XtCcJw4u2weEnqe7XLDar2wR68i+2BkONeMpcw0rnriXn9k 0=;
X-Files: image.png : 32966
IronPort-PHdr: =?us-ascii?q?9a23=3AKL2QfxaDAKiEGDsgPD4bnkv/LSx94ef9IxIV55?= =?us-ascii?q?w7irlHbqWk+dH4MVfC4el20gabRp3VvvRDjeee87vtX2AN+96giDgDa9QNMn?= =?us-ascii?q?1NksAKh0olCc+BB1f8Kav2by0iEd5DRXdu/mqwNg5eH8OtL1A=3D?=
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0AUAABp401d/4UNJK1mGgEBAQEBAgE?= =?us-ascii?q?BAQEHAgEBAQGBVAQBAQEBCwGBRCQFJwNtVSAECyoKhBSDRwOLD4JbiVuJLIR?= =?us-ascii?q?agS6BJANQBAIHAQEBCQECAQEYAQoKAgEBVYNqAheCSiM1CA4BBAEBBAEBBAE?= =?us-ascii?q?KbYUnDIVLAgEDAQEDDRECCRIBASwLAQ8CAQgdAQEgAwICAgUQAQkGCxQRAgQ?= =?us-ascii?q?OBQYIFIMAAYFqAxwBAQIMoGcCgTiIYHKBMoJ6AQEFgkiCUw0Lgg0HAwaBNAG?= =?us-ascii?q?EcoZxF4FAP4ERJx+CTD6CGkcBAYIOgl4ygiaPEIUMgQ2MdogBaUAJAoIdhVM?= =?us-ascii?q?BimKDeRuCMIcvjlmXJ44pAgQCBAUCDgEBBYFRATaBWHAVOyoBgkGCQoEnAQm?= =?us-ascii?q?CQYUUhT9ygSmMRQGBIAEB?=
X-IronPort-AV: E=Sophos;i="5.64,366,1559520000"; d="png'150?scan'150,208,217,150";a="307896771"
Received: from alln-core-11.cisco.com ([173.36.13.133]) by alln-iport-2.cisco.com with ESMTP/TLS/DHE-RSA-SEED-SHA; 09 Aug 2019 21:20:37 +0000
Received: from XCH-ALN-006.cisco.com (xch-aln-006.cisco.com [173.36.7.16]) by alln-core-11.cisco.com (8.15.2/8.15.2) with ESMTPS id x79LKbrV015893 (version=TLSv1.2 cipher=AES256-SHA bits=256 verify=FAIL); Fri, 9 Aug 2019 21:20:37 GMT
Received: from xhs-aln-003.cisco.com (173.37.135.120) by XCH-ALN-006.cisco.com (173.36.7.16) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Fri, 9 Aug 2019 16:20:36 -0500
Received: from xhs-rcd-002.cisco.com (173.37.227.247) by xhs-aln-003.cisco.com (173.37.135.120) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Fri, 9 Aug 2019 16:20:35 -0500
Received: from NAM04-SN1-obe.outbound.protection.outlook.com (72.163.14.9) by xhs-rcd-002.cisco.com (173.37.227.247) with Microsoft SMTP Server (TLS) id 15.0.1473.3 via Frontend Transport; Fri, 9 Aug 2019 16:20:35 -0500
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=O/8ZOrQuIWrwI+Qn7Lc6m+jKvZAgJZ94cv9hOf6ih4dLUL/5Xd+8JI0ld8v+WdQ57eIu+cupUoc5YxcAmXBuO5cER/PzCdIDuC9n1EdP3v1g7r+m0FiN5NN1wfVTujU708vqVJNDz3U+pL4alaFKdYl6VT2W8FC9kFt1p55qnkbRgmir1g3FUyBu8n4IHqDSmakncNBVIdORU3x2Xk2bAxrca5xUMtq1hnml0OddzNLtdnhO8hSO9L+BHPbhIS4G5N7HtszvmDhM3bUzCTHJWvjp3s2jF6l1+eDNlcg4WTOz/Rk/rPqzxYeWVWKVT5x4nF89Cido0I3yOCiGLav/Vg==
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=NXFyRWTjCoR5l1KLxT09Y4SqjQnU3fSPmXVq9cDf59o=; b=Gxjk0VtCmT/ZISDPYtQTTmi/Qv7JM5hg/Fhesp1EqcSV2tcnYYOGLUvXRZtIyRdC8KyZe8KzRl1JiscHWu6y9gKmi+r7sgSm7jE64O21ipiaBjnNgE6hRjlW67cRInId8AhumvXlX1BCONLUTDDXh6oSangvC/RS93rMu95gGzIEF8C4M0NZpQlDbsiWMZJQVOTLlAhKBTAqweOcDR6KOac+jwbO1AZMJEEXhc2y7SopfvNmoj95AlpmW8pZsCcDr80VeOJleggI5mIfiUgmu6NPXD49ETzA9qb91H7bHU9vV0XW130LMNVHeC2MfiZzHPrEHm8gIwcny6AoZVlwyw==
ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=cisco.com; dmarc=pass action=none header.from=cisco.com; dkim=pass header.d=cisco.com; arc=none
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cisco.onmicrosoft.com; s=selector2-cisco-onmicrosoft-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=NXFyRWTjCoR5l1KLxT09Y4SqjQnU3fSPmXVq9cDf59o=; b=NWnvOq8DdJObRDJoLsQD6yYSqwYD5j2NrqeeO/SyWqtYRWtpiip8EYH+TjFcakxXJUNEQk0aX6LZa+sJJE0n186QWnLADlOblYJRuzSaamNrul8m7AW8sbsxVWPSz6IEWfXV5ReNCAhsSce/LJyHR7COa0J1E3RckrxdcHO3egA=
Received: from DM6PR11MB4060.namprd11.prod.outlook.com (20.176.125.221) by DM6SPR01MB0017.namprd11.prod.outlook.com (20.176.113.94) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.2157.14; Fri, 9 Aug 2019 21:20:35 +0000
Received: from DM6PR11MB4060.namprd11.prod.outlook.com ([fe80::f1b7:a1cc:266d:f29d]) by DM6PR11MB4060.namprd11.prod.outlook.com ([fe80::f1b7:a1cc:266d:f29d%6]) with mapi id 15.20.2157.015; Fri, 9 Aug 2019 21:20:34 +0000
From: "Thirumavalavan Periyannan (thiperiy)" <thiperiy@cisco.com>
To: gangadhara reddy chavva <meetgangadhara@gmail.com>
CC: "bess@ietf.org" <bess@ietf.org>
Thread-Topic: [bess] EVPN VPWS BDF forwarding behavior at MH site
Thread-Index: AQHVTrbZpoJlJbwDnkyQH27ddz9oh6bzUyJa
Date: Fri, 9 Aug 2019 21:20:34 +0000
Message-ID: <3A8DD12F-E9CF-4B91-8B28-05344A82E752@cisco.com>
References: <CAAG_SC_gizf5nRVGOL1XJ4nSHg_7RwP92wcgjqi9MCTMMiUA7A@mail.gmail.com>
In-Reply-To: <CAAG_SC_gizf5nRVGOL1XJ4nSHg_7RwP92wcgjqi9MCTMMiUA7A@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator:
authentication-results: spf=none (sender IP is ) smtp.mailfrom=thiperiy@cisco.com;
x-originating-ip: [106.197.204.0]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: d8d9d5da-bef7-4cbd-c579-08d71d0f6acf
x-microsoft-antispam: BCL:0; PCL:0; RULEID:(2390118)(7020095)(4652040)(8989299)(4534185)(4627221)(201703031133081)(201702281549075)(8990200)(5600148)(711020)(4605104)(1401327)(2017052603328)(49563074)(7193020); SRVR:DM6SPR01MB0017;
x-ms-traffictypediagnostic: DM6SPR01MB0017:
x-ms-exchange-purlcount: 1
x-microsoft-antispam-prvs: <DM6SPR01MB00172DE5334BB0C9E22C2F64C2D60@DM6SPR01MB0017.namprd11.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:10000;
x-forefront-prvs: 01244308DF
x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(4636009)(346002)(366004)(136003)(396003)(39860400002)(376002)(189003)(199004)(53754006)(229853002)(14454004)(4326008)(606006)(99936001)(316002)(86362001)(256004)(14444005)(25786009)(33656002)(71190400001)(7736002)(6916009)(2906002)(6486002)(6436002)(66066001)(71200400001)(5660300002)(66446008)(66616009)(66476007)(66556008)(64756008)(3846002)(66946007)(76116006)(6116002)(91956017)(36756003)(1411001)(6506007)(486006)(11346002)(102836004)(53546011)(6246003)(446003)(53936002)(81166006)(81156014)(186003)(2616005)(476003)(478600001)(76176011)(26005)(54896002)(6306002)(8936002)(8676002)(236005)(966005)(6512007)(99286004); DIR:OUT; SFP:1101; SCL:1; SRVR:DM6SPR01MB0017; H:DM6PR11MB4060.namprd11.prod.outlook.com; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; MX:1; A:1;
received-spf: None (protection.outlook.com: cisco.com does not designate permitted sender hosts)
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam-message-info: z+LQM0tU+VzsGToccnteb9OwNn1thx+SRV/3HKDua9rOxE5Y2lZy/8nqYiO15dcHc6rcVltHURxHMkPzDlRYaAJnMpomcnYC9tNd7/u8xwf/M5zU8sYlFBl7xuWtQDVr3stuYrtQQTzJPpJmTC1KMeor1MiCiFDh3GRXODCYS+Jhwsy4veWt9dGg5M2z51qEPuqoMr4lCEaWHV8hclUp8ytW10ATOnvAMY2aCUEIfsfQwRIXn8ZAjSx92LJKnRMSv8xeKL24a53VFx5zM3FIjSDlum0wYqsy7fo+qOvsn1slAIeOEn2cM3i5uaIqiu9IIT3V0qtsGP901stEPZurW3Unc7HPI78CBb89FtGjrtr27Ag4SLQPkfmwvfiKDGNOq3dCQ4X8eJ4F/J3rrml1fJ2s89lJMVC1PCOmDu9M6ag=
x-ms-exchange-transport-forked: True
Content-Type: multipart/related; boundary="_004_3A8DD12FE9CF4B918B2805344A82E752ciscocom_"; type="multipart/alternative"
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-Network-Message-Id: d8d9d5da-bef7-4cbd-c579-08d71d0f6acf
X-MS-Exchange-CrossTenant-originalarrivaltime: 09 Aug 2019 21:20:34.8011 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 5ae1af62-9505-4097-a69a-c1553ef7840e
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-CrossTenant-userprincipalname: TKtTbrhobtHLcFuC+vBDLXqK586ZjIs8mok2Ntn/dE4jIcgbS3wcVq5lH+PevXepUkHnujkzWpjUmHqBc+M6lw==
X-MS-Exchange-Transport-CrossTenantHeadersStamped: DM6SPR01MB0017
X-OriginatorOrg: cisco.com
X-Outbound-SMTP-Client: 173.36.7.16, xch-aln-006.cisco.com
X-Outbound-Node: alln-core-11.cisco.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/bess/p-LP1T1a2XqiWJfCTCrLOynb_6o>
Subject: Re: [bess] EVPN VPWS BDF forwarding behavior at MH site
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, 09 Aug 2019 21:20:44 -0000

Hello Gangadhara,

How remote PE detect the DF failure? It’s based on EVI/AD Withdraw message from DF PE if so then NDF PE also received this route and changed its DF status at the same time Remote PE changed its nexthop to NEW DF PE.

The below info is not clear, could you please help me to understand.

for faster convergence if we can install the route such that BDF can allow the traffic from remote PE towards to multi homed segment, we can forward the traffic received from the remote PE.

at the same time we shouldn't allow the traffic from multi homed site this leads to duplicate traffic on the remote PE. to achieve this we should not program the path from multi home site towards remote PE until this PE elected as DF for that VPWS instance.

Thanks,
Thiru

On 09-Aug-2019, at 19:02, gangadhara reddy chavva <meetgangadhara@gmail.com<mailto:meetgangadhara@gmail.com>> wrote:

HI All,

i have one question on EVPN VPWS BDF forwarding behavior at MH site.
when PE is selected as BDF, it will communicate the EAD EVI route with B bit set to remote PE. so remote PE will install the FRR route with primary path towards DF PE and secondary path towards BDF.
when ever primary path get disconnected it will switch the path to secondary path quickly at remote PE. because of this data from the remote PE will reach to BDF very quickly, but if BDF is not programmed its path towards multi homed segment then traffic will be get dropped until control plane convergence and it will be elected as DF.

for faster convergence if we can install the route such that BDF can allow the traffic from remote PE towards to multi homed segment, we can forward the traffic received from the remote PE.

at the same time we shouldn't allow the traffic from multi homed site this leads to duplicate traffic on the remote PE. to achieve this we should not program the path from multi home site towards remote PE until this PE elected as DF for that VPWS instance.

can you please let me know if there are any problems with this kind of approach..

<image.png>

Regards,
Gangadhar






_______________________________________________
BESS mailing list
BESS@ietf.org<mailto:BESS@ietf.org>
https://www.ietf.org/mailman/listinfo/bess