IETF Logo Mail Archive

Re: [GROW] Handling of LAGs in Mitigating Negative Impact of Maintenance through BGP Session Culling

Job Snijders <job@instituut.net> Tue, 09 January 2018 11:35 UTC

Return-Path: <job@instituut.net>
X-Original-To: grow@ietfa.amsl.com
Delivered-To: grow@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 18AF7127369 for <grow@ietfa.amsl.com>; Tue, 9 Jan 2018 03:35:13 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level:
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_LOW=-0.7, UNPARSEABLE_RELAY=0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=instituut-net.20150623.gappssmtp.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 SiSqt6WQNpzK for <grow@ietfa.amsl.com>; Tue, 9 Jan 2018 03:35:10 -0800 (PST)
Received: from mail-wm0-x233.google.com (mail-wm0-x233.google.com [IPv6:2a00:1450:400c:c09::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 71400126DEE for <grow@ietf.org>; Tue, 9 Jan 2018 03:35:10 -0800 (PST)
Received: by mail-wm0-x233.google.com with SMTP id r78so19879643wme.5 for <grow@ietf.org>; Tue, 09 Jan 2018 03:35:10 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=instituut-net.20150623.gappssmtp.com; s=20150623; h=date:from:to:cc:subject:message-id:references:mime-version :content-disposition:in-reply-to:user-agent; bh=Fq+2OG0xs3SGh1bqSJrZKXcj2SpO8sOWQOUcJEyz0Zg=; b=Ek2vXHWTyKC/xvI3iU73vEPyHXViD+7u72wqpNNS5NxTAmVpVGDNximnYJO84DPE4W rd+eIUciJj0pPRQvAMHVACY7QJnCLpm02Lqs797Agrdjqb/WMZOecypH9FVPevemPPvn TMCXAnKfzoZcWtD62BGyGuAmPh5mJ34Nt3oF9y8i4oCxTO9sPkKpTnAU4Cp+6cCqCKUt LmbMJQqtVUvzUKD9gSUCNRKGMyDApTCztzH4weBLC1ixFwStXfgzR+s4HvO9I+OSgj1v syL5yCR/Au3QZMnVj4vHuOGHr0kh1BY/UC68EZnmkiKG5W5WmeF0QrltjxgNBTd116oU BBqg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:cc:subject:message-id:references :mime-version:content-disposition:in-reply-to:user-agent; bh=Fq+2OG0xs3SGh1bqSJrZKXcj2SpO8sOWQOUcJEyz0Zg=; b=M1bYSJxgqk0iskM02ewtIp3vJRRDT/6EQoCjHLDO1nRBtDgxKehgdWJOF0MXlTGI5P d/IgMXtbyRMziqgfhkILRt4VhBt+eDLhsXFOlCAMEcAaILS+Usf/HGrz2c49muUskBIi NHEGt4/WeHgpHrw7qFvrW34iflzplFx3NYbTNvQzEhDInter679SSA/+c7JO6hLtopE6 eP88Wl2bCp404jH/Ftxo+3L+P+VMW0/ygn0ASDpuqprgEVdLO7e1TQpCPX++Cl/njFG6 q4GVtuVV/InJZyS2ZguUFVlEpov/2KlCyVlj66O0ssc4SahTCVGXuMjH8xYcBBDfTRln HFKw==
X-Gm-Message-State: AKGB3mIgCUUAS+D5T4/S0ra6hv01PDeWL8mwi0dmlPhMOS2hX7sNSR/B oTAIC0B3q33erLulU7uNJv11/g==
X-Google-Smtp-Source: ACJfBosBOpe4aFAGOu8ErQH+QKZqn7DwroqscXV9pnBKZFPVKpSDG8mDHl8MunItsJ84u95k86oUfQ==
X-Received: by 10.80.195.193 with SMTP id i1mr20815620edf.139.1515497708779; Tue, 09 Jan 2018 03:35:08 -0800 (PST)
Received: from vurt.meerval.net (vurt.meerval.net. [192.147.168.22]) by smtp.gmail.com with ESMTPSA id v20sm8051790edm.10.2018.01.09.03.35.07 (version=TLS1_2 cipher=ECDHE-RSA-CHACHA20-POLY1305 bits=256/256); Tue, 09 Jan 2018 03:35:08 -0800 (PST)
Received: from localhost (vurt.meerval.net [local]) by vurt.meerval.net (OpenSMTPD) with ESMTPA id 34b672f2; Tue, 9 Jan 2018 11:35:07 +0000 (UTC)
Date: Tue, 09 Jan 2018 11:35:07 +0000
From: Job Snijders <job@instituut.net>
To: Thomas King <thomas.king@de-cix.net>
Cc: "grow@ietf.org" <grow@ietf.org>, "draft-ietf-grow-bgp-session-culling@ietf.org" <draft-ietf-grow-bgp-session-culling@ietf.org>
Message-ID: <20180109113506.GA99435@vurt.meerval.net>
References: <8BB20DB3-61E9-4CAC-B33B-B18CA12C2591@de-cix.net>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <8BB20DB3-61E9-4CAC-B33B-B18CA12C2591@de-cix.net>
X-Clacks-Overhead: GNU Terry Pratchett
User-Agent: Mutt/1.9.2 (2017-12-15)
Archived-At: <https://mailarchive.ietf.org/arch/msg/grow/cifX0R0EgMxUAfrTn1nJ2E6oxOc>
Subject: Re: [GROW] Handling of LAGs in Mitigating Negative Impact of Maintenance through BGP Session Culling
X-BeenThere: grow@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Grow Working Group Mailing List <grow.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/grow>, <mailto:grow-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/grow/>
List-Post: <mailto:grow@ietf.org>
List-Help: <mailto:grow-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/grow>, <mailto:grow-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 09 Jan 2018 11:35:13 -0000

Dear Thomas,

On Tue, Jan 09, 2018 at 11:30:35AM +0000, Thomas King wrote:
> we at DE-CIX are currently implementing BGP Session Culling and we hit
> the question how to handle LAGs (e.g. LACP, Static configured). The
> Internet Draft is not covering this question yet, however, from our
> point of view it is worth discussing it.
> 
> Our suggestion for handling LAGs looks like this: Typically, a minimum
> number of port members can be defined for a LAG being up. The LAG is
> not touched by BGP Session Culling during a maintenance unless this
> number is undercut. If the number if undercut the LAG is handled by
> BGP Session Culling as defined in the Internet Draft.
> 
> If no value for the minimum number of active port members is defined
> for a LAG, the value 1 should be used as this is the behaviour of LAGs
> today already.

Is this in context of multi-chassis LAG?

Kind regards,

Job

v2.23.0 | Report a Bug | By Email