IETF Logo Mail Archive

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

"Luc Andre Burdet (lburdet)" <lburdet@cisco.com> Wed, 06 March 2019 14:21 UTC

Return-Path: <lburdet@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 7051A126C87 for <bess@ietfa.amsl.com>; Wed, 6 Mar 2019 06:21:16 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -12.601
X-Spam-Level:
X-Spam-Status: No, score=-12.601 tagged_above=-999 required=5 tests=[DKIMWL_WL_HIGH=-0.001, DKIMWL_WL_MED=-0.001, 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, URIBL_BLOCKED=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=LpAhkmfp; dkim=pass (1024-bit key) header.d=cisco.onmicrosoft.com header.b=kJygPHaR
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 UIjJugBORL2E for <bess@ietfa.amsl.com>; Wed, 6 Mar 2019 06:21:15 -0800 (PST)
Received: from rcdn-iport-3.cisco.com (rcdn-iport-3.cisco.com [173.37.86.74]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A1878124B19 for <bess@ietf.org>; Wed, 6 Mar 2019 06:21:14 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=50852; q=dns/txt; s=iport; t=1551882074; x=1553091674; h=from:to:cc:subject:date:message-id:references: in-reply-to:mime-version; bh=SmJPNZ79f/1MxlcpwanClvjJUKdAJ0MMjT7yo6g0KSY=; b=LpAhkmfpapE/sNFra2GdqPLjrDGYjrhxNek+s5zpQVLjYQa54+NUkSXv caiQmT3G5pV1mpOzW5lKxOlN+o25OwFMfrtdUiXFdmF+jcVesxEYWfYxY U8ijN6VqISC0qMOvMGaEZvyfnit/UznMUeShfSR9l/eup1FTzSjaGBIJh g=;
X-Files: image001.png, image002.jpg : 11763, 10171
IronPort-PHdr: 9a23:r42WZxcV3/h9tptPnp9MOEWOlGMj4e+mNxMJ6pchl7NFe7ii+JKnJkHE+PFxlwGRD57D5adCjOzb++D7VGoM7IzJkUhKcYcEFnpnwd4TgxRmBceEDUPhK/u/ayYnBshPSHdu/mqwNg5eH8OtL1A=
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0ADAAAV1n9c/5ldJa1hAxkBAQEBAQEBAQEBAQEHAQEBAQEBgVEEAQEBAQELAYENL1ADaHQECyeECINHA4RQiwCCMiWJLokChXOBJANUCAECAQElB4N6RgIXhBoiNAkNAQEDAQEDAQMCbRwMhUoBAQEEBR4CCAESAQEkEwEPAgEIEQMBAgYBAQEKFQMCAgIFEAoFDBQJCAIEAQ0EAQ6DFAGBXQMVAQ6fdQKKFHGBL4J4AQEFgS9Ugn0NC4IEBwiBLwGFNoVyF4FAP4ERJwwTgh4ugldHAQEBgRxbCQEVCAmCQzGCJoxHhAaGcjOEOIFcA0KFEzMJAoZYAW6HeYM+GYF2WIUOE4M1iAuJZoEJgRKFfYsiAgQCBAUCDQEBBYEhJjiBVnAVZQGCQQmCAQwXg0uKU3IBgSeMbQEB
X-IronPort-AV: E=Sophos;i="5.58,448,1544486400"; d="jpg'145?png'145,150?scan'145,150,208,217,150,145";a="519946177"
Received: from rcdn-core-2.cisco.com ([173.37.93.153]) by rcdn-iport-3.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 06 Mar 2019 14:21:12 +0000
Received: from XCH-ALN-016.cisco.com (xch-aln-016.cisco.com [173.36.7.26]) by rcdn-core-2.cisco.com (8.15.2/8.15.2) with ESMTPS id x26ELCm4031864 (version=TLSv1.2 cipher=AES256-SHA bits=256 verify=FAIL); Wed, 6 Mar 2019 14:21:12 GMT
Received: from xhs-rtp-002.cisco.com (64.101.210.229) by XCH-ALN-016.cisco.com (173.36.7.26) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Wed, 6 Mar 2019 08:21:12 -0600
Received: from xhs-rcd-003.cisco.com (173.37.227.248) by xhs-rtp-002.cisco.com (64.101.210.229) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Wed, 6 Mar 2019 09:21:10 -0500
Received: from NAM03-CO1-obe.outbound.protection.outlook.com (72.163.14.9) by xhs-rcd-003.cisco.com (173.37.227.248) with Microsoft SMTP Server (TLS) id 15.0.1473.3 via Frontend Transport; Wed, 6 Mar 2019 08:21:10 -0600
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cisco.onmicrosoft.com; s=selector1-cisco-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=Hg929EastQyvMF1R41SjqktHicgrq0/t/oKGMazIeG0=; b=kJygPHaReMC+YL1KzyDKJ4qQogxl+/gexpNA7InX/h4vwqwo1Mks10RLcpSFn3zOv9vXrOte974PwuoylvYxJlBXMp7zjBLHdrEa444d0/14Upwcl8sG8ioC40mTEOeTTutw46U/VTwzFoOa9o51vFaCdMac+ZDVw6+HeEVGNPc=
Received: from DM5PR11MB1387.namprd11.prod.outlook.com (10.168.104.13) by DM5PR11MB1339.namprd11.prod.outlook.com (10.168.108.143) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.1686.17; Wed, 6 Mar 2019 14:21:09 +0000
Received: from DM5PR11MB1387.namprd11.prod.outlook.com ([fe80::f026:e8e1:2e0c:7171]) by DM5PR11MB1387.namprd11.prod.outlook.com ([fe80::f026:e8e1:2e0c:7171%4]) with mapi id 15.20.1665.020; Wed, 6 Mar 2019 14:21:09 +0000
From: "Luc Andre Burdet (lburdet)" <lburdet@cisco.com>
To: chalapathi andhe <chalu.ietf@gmail.com>, "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>
Thread-Topic: [bess] FW: Regarding the Alias label usage in EVPN Multihoming
Thread-Index: AQHU0/0mr4+JC2oWaUyio1TmbRtcVaX+U+GA
Date: Wed, 06 Mar 2019 14:21:09 +0000
Message-ID: <478004F5-9B6E-49F0-9203-57F4953520DB@cisco.com>
References: <VI1PR07MB4462872475A375E50C33F4C8E2730@VI1PR07MB4462.eurprd07.prod.outlook.com> <VI1PR07MB44620DB939F1ABE51DDED5B6E2730@VI1PR07MB4462.eurprd07.prod.outlook.com> <CAP3Cv1beDHnU0oBheDiG4863QC8vcgMpNkOy9JjkfiFgAWuFkw@mail.gmail.com>
In-Reply-To: <CAP3Cv1beDHnU0oBheDiG4863QC8vcgMpNkOy9JjkfiFgAWuFkw@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator:
user-agent: Microsoft-MacOutlook/10.10.7.190210
authentication-results: spf=none (sender IP is ) smtp.mailfrom=lburdet@cisco.com;
x-originating-ip: [2001:420:2840:1250:59e4:cf1b:8f20:b9fd]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: 82f4544d-2321-4ec6-eb02-08d6a23efa8b
x-microsoft-antispam: BCL:0; PCL:0; RULEID:(2390118)(7020095)(4652040)(8989299)(5600127)(711020)(4605104)(4534185)(4627221)(201703031133081)(201702281549075)(8990200)(2017052603328)(7153060)(49563074)(7193020); SRVR:DM5PR11MB1339;
x-ms-traffictypediagnostic: DM5PR11MB1339:
x-ms-exchange-purlcount: 1
x-microsoft-exchange-diagnostics: 1;DM5PR11MB1339;23:pWZmKj27zmtWqKbVo4yh5syNcdDLfFFHV8kLIdJWxtv/dkTrkLqNQ5n2Fcz3D/UY/TNKF5oHuc+L+czZ8Hc8OAbFkeXY+Ppf9kq/3XDE2oUDMnqf0ay57dnVUefGZPN64kU+p/0I9ijvgVJTx6MKQRjEWYPjcTHJqL1HP3Y1SAT9xvrjYeOn2HF/c7X/349IRBvaJNTngj6M7zqEfRRQfWjnPzOXHiz/FVsy4KbTgwHoCswpB/4qSIJJiXCMiw/N1CmqiS2EK+hvETAYAqnVQ5ssoo2zX6oUABmOZMwTMrdoKLjx0DQhjhoLIA/L8YYbAZNvh85FEv+tu9eipQ+rR6mqc/g8mBvTolUEHtznji/s47uzeosSZX/eloS6oXKXauxpBLI1KdgNbqxVQBXbRcDfGFSK5sSZIAWW9tkqNf5bhVcxV38bFamU6STCp+++yw7fOcVIyFTqd0EHqZvDc+Nja4Kd71oT17umEvDiux0LOsvDI2263Gg3SrYjLtTuf/2Mk9X8OoOq3VRZQ0XoIPMeYX8pQcQRlehK1L0CAehiZ243qIprXyF8h6xzcSk/3HPlH+bdExQhfEjQtfqaAQATR/0s2wNyEMgjBDqnVkqOPyj7fqhVntogHxukjTJwExJ5ndK5iBWGYCn9Ph/OZp7injCyj9nbvznxXAk1lxrf3EkGKhzzi9aLF8akP+R4laeDZWnbDJNwnWcjHhJ4NfDYv99v+a/dqqenZzAoNpnJwbhFJCPmR2VO09djNQPVIWzVAYrMCFc9ONb42usKSlOgftguwu8khutcoNTEN4R4Y8Cly8BBPZL7YhbGS3WFwgheInjaO9HTZbVDAy+LVPyogqAkcNllM9RufuvL6dILVnYmVgCY/MHnlUsqo4ezil78hmg6yRkgLpUqrBo5AkHGh8Ra6xIC6oR2yH0ihq9d00i3PJW7Lbp8RrhprSJatnzXHm3x9+QllhmAZ4fphs/mq6tBBlf2aU/ga8o1+CNI3dro81xEuMteO5bE68zwcwNwTBEHG7iVU2UjnWAOCnKoPSfFwm0DBNAWUi6WnUazKBdYb6piSUFCD6L7PmmivcFzMrtZ7hXHfL8n5M8yALfLf3QFfTsIyCuX6r7NFT186W/YKvOwuoxNNXx6b84qnQzGqyAEgk+4c+p6mARi42zilMbONWftbH5w9DbKXndyOrTKPaox3l0d9ThjYuMqiQnoLAEKb4p5EJQrTQobMHQjtZc/Fy23kK1Bd9kR+ZGapiVaEVluGl3TOoS8Uaqm4G1EObo0U082qE7x5uTZiwLKiIS1Su5FIZCUb6pWBo2I/bvFOcC/IEjvZdV7I41d29UiTCc46RF5jCEN7CZaxBoIeWtvxRFAxj7N0VOUuo2EzkurrPmf0H0mo2sPHKfzbMF4vxZXO1bCrqpMOFvyAgtnOOg6WT0+ke1SnFbJycUBwgNpdrX7v8vGPB4cdz/PlLeXI4wOQuo1eRmVhJPPEw==
x-microsoft-antispam-prvs: <DM5PR11MB1339E24783131764F9D31023BC730@DM5PR11MB1339.namprd11.prod.outlook.com>
x-forefront-prvs: 0968D37274
x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(39860400002)(136003)(376002)(366004)(396003)(346002)(199004)(189003)(53754006)(316002)(2906002)(2501003)(6506007)(53546011)(76176011)(46003)(36756003)(486006)(5070765005)(102836004)(11346002)(2616005)(476003)(106356001)(733005)(14444005)(186003)(82746002)(6436002)(83716004)(6512007)(6306002)(54556002)(54896002)(71200400001)(71190400001)(229853002)(86362001)(5660300002)(99286004)(446003)(6486002)(236005)(99936001)(256004)(97736004)(790700001)(6116002)(53936002)(105586002)(14454004)(33656002)(8676002)(81166006)(25786009)(68736007)(81156014)(4326008)(58126008)(110136005)(54906003)(9326002)(8936002)(6246003)(606006)(7736002)(478600001); DIR:OUT; SFP:1101; SCL:1; SRVR:DM5PR11MB1339; H:DM5PR11MB1387.namprd11.prod.outlook.com; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; A:1; MX: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: I8cxuyO6QvEEgTOU1o5GoGg/0p3Rbqq4FZHzhCQUAew6j6Cmjs58spEs6tNMoh6v4LfXe8RuaAy3FMy7CZukoj5kgI0tLfkX3eDxBsQCu+9Sicp9nWStlrAnXtLPYztbLXjge1v03361qgNeBimjmYUQfhwH3ZKpc62xAe4K5+/G1BaxYaDsOC1gUpf8vPUr1iIivNpdxwGxZN83v1VStgDYl7TtCvaOL6fzV9up3cHCG3NWHQ+VKKOL7fG2aOvE9wxYEYOVNfl6QnaO88UiXUGI97oGCZDuzMQuJvOzoiDEmfqcIUky1oxG5k5PpSBTTL1N1S3FrwENOudqr6m9pGfwX5imuSZFdQv0iR7G5osMpE/E4F+iMndM01Cj1JFpDniDFs++6Qa4gLsXFgxd1fSWvN+OuHc+KHkaZghDimI=
Content-Type: multipart/related; boundary="_005_478004F59B6E49F0920357F4953520DBciscocom_"; type="multipart/alternative"
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-Network-Message-Id: 82f4544d-2321-4ec6-eb02-08d6a23efa8b
X-MS-Exchange-CrossTenant-originalarrivaltime: 06 Mar 2019 14:21:09.3628 (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-Transport-CrossTenantHeadersStamped: DM5PR11MB1339
X-OriginatorOrg: cisco.com
X-Outbound-SMTP-Client: 173.36.7.26, xch-aln-016.cisco.com
X-Outbound-Node: rcdn-core-2.cisco.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/bess/jswrE4noye79o6wo5TS2YU992Ko>
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 14:21:16 -0000

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.


[http://www.cisco.com/c/dam/m/en_us/signaturetool/images/banners/standard/09_standard_graphic.png]




Luc André Burdet
lburdet@cisco.com<mailto: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 ?


[cid:1695247dcc04ce8e91]


Thanks,
Chalapathi.

v2.23.0 | Report a Bug | By Email