Re: [bess] Regarding the PE-Ce link failure

chalapathi andhe <chalu.ietf@gmail.com> Thu, 21 March 2019 17:10 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 EE7E1131422 for <bess@ietfa.amsl.com>; Thu, 21 Mar 2019 10:10:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.595
X-Spam-Level:
X-Spam-Status: No, score=-0.595 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_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 HAV95Eow4zL9 for <bess@ietfa.amsl.com>; Thu, 21 Mar 2019 10:10:36 -0700 (PDT)
Received: from mail-oi1-x233.google.com (mail-oi1-x233.google.com [IPv6:2607:f8b0:4864:20::233]) (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 ABCE713141E for <bess@ietf.org>; Thu, 21 Mar 2019 10:10:36 -0700 (PDT)
Received: by mail-oi1-x233.google.com with SMTP id u12so5224721oiv.1 for <bess@ietf.org>; Thu, 21 Mar 2019 10:10:36 -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 :cc; bh=CPepdzn4btaNqnkp9bth60mtBrGUHfUcvvJmicejN+w=; b=NG1aFNo3bzCu4RbnrArWO6uXmHMzqMAUHycHCNuPO2jjqLkkGNMu1G0LJyXoEFJ7nL GwyAwhiUzVRq8evw2muVe5hW/MGx28ziBFcsjGwsTQmPSmrGoxnDzTpGt/jb8I+io2To L8JQFAL0eRJPiMoBTwsPbDRhXJkoD8KulEOzj0MLAvxmIbAXigdJ2+Sk3KyAlb3QO1Ov Sj8nYY6WVvsoRSRmePYDqZ/RgWKcOYpsseELMKs1JIM8wjqfgEnjbHoNG+lmXjkwijGs scgmndk/rIjmVJNnfoLp9Shn6VRmepZWI3/5N3s0xGppyTN4JtFRkplyExxxEk6UPvU8 8ISQ==
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=CPepdzn4btaNqnkp9bth60mtBrGUHfUcvvJmicejN+w=; b=kxu+IjKK3f2JMYJt5huQxiSQvFSCtOpDYIobfhFM0uBliPWDvlXqrrTG9/SYUC20gX Kgy7VjgG80ZolZ/kcN/xbXXNPMsGINmowhXMozfXlNzsFAplPO/Liqftkk2MKPGdQ9Io N4pw5Ey10X8BnuJEasZT6b72J6q32uYyOd33JR4fk/0mhIsYTFhrNUN/sUC+v09Fi4fh FlGPXsz/33CGDlGbW1Alcrc7uaVG/0c8dDkFQuI1ua53pGDOYZgIZcjXJ1jhM/6a7EQ5 G+kIYCNUbyXyoOEpErsxHiFEMvcI0hvu65bC0GxMLFEa8qyAHXneDHEmPpGjt/8rtAit 5XTQ==
X-Gm-Message-State: APjAAAWlOUVGIX6MfNSjscGVdeVcC+6o8IAr+i+DDh0ps3fSSiLamv+a VUFwFExE3OkNREvnxvoAr3Zm+lq2SBP2VsWjOA==
X-Google-Smtp-Source: APXvYqxvG3WYGXEliOkpVSSyyZs/7SrO8gCzKAuPhI2Tl5W3rOI3IqBjoCGAS/RuWXTxWKheXMXD3MDQch1iX1AcXgE=
X-Received: by 2002:aca:40d5:: with SMTP id n204mr230847oia.59.1553188235820; Thu, 21 Mar 2019 10:10:35 -0700 (PDT)
MIME-Version: 1.0
References: <VI1PR07MB4462FAA7B3971B3D25513AA9E2420@VI1PR07MB4462.eurprd07.prod.outlook.com>
In-Reply-To: <VI1PR07MB4462FAA7B3971B3D25513AA9E2420@VI1PR07MB4462.eurprd07.prod.outlook.com>
From: chalapathi andhe <chalu.ietf@gmail.com>
Date: Thu, 21 Mar 2019 22:40:24 +0530
Message-ID: <CAP3Cv1ZQhK1p7WJO1qgW+0jU82yR-qA8xUOb=9jh_QHe90ad=w@mail.gmail.com>
To: Chalapathi Andhe <chalapathi.andhe@ericsson.com>
Cc: "bess@ietf.org" <bess@ietf.org>
Content-Type: multipart/related; boundary="000000000000114be905849dd1ff"
Archived-At: <https://mailarchive.ietf.org/arch/msg/bess/3tIc4jchAGb9kSc5ZtLGhiLkjFs>
Subject: Re: [bess] Regarding the PE-Ce link failure
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, 21 Mar 2019 17:10:38 -0000

>
>
> Hi All,
>
>
>
> Can you please help to understand the following behavior ? The following
> topology is for a Single Active Multi-homing scenario where PE1 is the DF.
>
> In this topology, when PE1-CE1 link is failed, PE1 sends the EAD/ES route
> withdraw and PE3 updates its forwarding state to point towards PE2,
>
> which means at PE3 any packet destined to the MAC [learnt from PE1] will
> go through PE2 [will not be flooded].
>
> And later it is expected that the PE1 will start sending the MAC withdraw
> to PE3, and in the meantime PE2 might start sending the MAC add to PE3.
>
>
>
> However in case of a quick link flap between PE1-CE1, what is the expected
> behavior from PE1 ?
>
> 1). First it sends the EAD/ES withdraw, and then before it start sending
> the EAD/ES add, does it required to send the MAC delete for all the MAC’s ?
> and send the MAC add again for all the MAC’s Or
>
> 2). First sends the EAD/ES withdraw, and few MAC deletes, and again send
> all the MAC’s add
>
>
>
> In quick flap scenario’s, when should PE3’s MAC entries should point back
> to PE1 ?, should it be after the EAD/ES add or only after the MAC add is
> received again from PE1 ?
>
> Is it mandatory for PE1 to send the MAC add again in this scenario ?
>
>
>
>
>
>
>
>
>
>
>
> Thanks,
>
> Chalapathi.
>