IETF Logo Mail Archive

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

Randy Bush <randy@psg.com> Thu, 18 January 2018 18:45 UTC

Return-Path: <randy@psg.com>
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 97B9F129C56; Thu, 18 Jan 2018 10:45:32 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.911
X-Spam-Level:
X-Spam-Status: No, score=-6.911 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=ham autolearn_force=no
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 IjouTYFMxYmq; Thu, 18 Jan 2018 10:45:31 -0800 (PST)
Received: from ran.psg.com (ran.psg.com [IPv6:2001:418:8006::18]) (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 A7C6012895E; Thu, 18 Jan 2018 10:45:31 -0800 (PST)
Received: from localhost ([127.0.0.1] helo=ryuu.rg.net) by ran.psg.com with esmtp (Exim 4.86_2) (envelope-from <randy@psg.com>) id 1ecFBn-0001rg-JR; Thu, 18 Jan 2018 18:45:27 +0000
Date: Thu, 18 Jan 2018 10:45:27 -0800
Message-ID: <m2fu73t394.wl-randy@psg.com>
From: Randy Bush <randy@psg.com>
To: joel jaeggli <joelja@bogus.com>
Cc: Nick Hilliard <nick@foobar.org>, "grow@ietf.org" <grow@ietf.org>, "draft-ietf-grow-bgp-session-culling@ietf.org" <draft-ietf-grow-bgp-session-culling@ietf.org>
In-Reply-To: <3412ecb1-c8f1-0228-5e3b-d90c131c1f98@bogus.com>
References: <8BB20DB3-61E9-4CAC-B33B-B18CA12C2591@de-cix.net> <20180109113506.GA99435@vurt.meerval.net> <53E19D26-D4C0-4722-8CFE-FDC5BF5C3FBC@harg.net> <20180109155039.GD59807@vurt.meerval.net> <DF40EDF7-DFF4-44EA-AF7E-A41552E5400A@de-cix.net> <2EE7BDAB-095C-4D09-B51C-44CFBA48B6FF@de-cix.net> <20180115183409.GL33439@vurt.meerval.net> <F5BCB532-0D06-480B-B95B-30AA92062A77@de-cix.net> <5A5E1CE0.7080505@foobar.org> <m2o9lrub79.wl-randy@psg.com> <3412ecb1-c8f1-0228-5e3b-d90c131c1f98@bogus.com>
User-Agent: Wanderlust/2.15.9 (Almost Unreal) Emacs/25.3 Mule/6.0 (HANACHIRUSATO)
MIME-Version: 1.0 (generated by SEMI-EPG 1.14.7 - "Harue")
Content-Type: text/plain; charset="US-ASCII"
Archived-At: <https://mailarchive.ietf.org/arch/msg/grow/fu2WHWMdrAYjMeBNWtsWd9oRA6U>
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: Thu, 18 Jan 2018 18:45:33 -0000

>> really do not want to get drawn into this.  but while looking into lags
>> a few years back, we found a lot of them split across line cards, with
>> resilience to line card failure being the stated reason.
> 
> even in fixed configuration 1 and 2ru switches you may split them across
> asics for survivability and fabric / forwarding capacity reasons.

we think we saw more results of hashing spread in those splits

v2.23.0 | Report a Bug | By Email