IETF Logo Mail Archive

Re: [Idr] New BGP capability to advertise running daemon version

Donatas Abraitis <donatas.abraitis@gmail.com> Fri, 02 August 2019 14:57 UTC

Return-Path: <donatas.abraitis@gmail.com>
X-Original-To: idr@ietfa.amsl.com
Delivered-To: idr@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C6E20120345 for <idr@ietfa.amsl.com>; Fri, 2 Aug 2019 07:57:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level:
X-Spam-Status: No, score=-1.999 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, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham 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 UlIwQWlki55n for <idr@ietfa.amsl.com>; Fri, 2 Aug 2019 07:57:19 -0700 (PDT)
Received: from mail-qt1-x831.google.com (mail-qt1-x831.google.com [IPv6:2607:f8b0:4864:20::831]) (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 53DC8120181 for <idr@ietf.org>; Fri, 2 Aug 2019 07:57:07 -0700 (PDT)
Received: by mail-qt1-x831.google.com with SMTP id r6so69921673qtt.0 for <idr@ietf.org>; Fri, 02 Aug 2019 07:57:07 -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:content-transfer-encoding; bh=7wMmB6L4t7XM/wO6F8UNLM0ObBNED+BBPoGp4d2M/a4=; b=HHOP74xUc2sHuxIXLYSvS+szurx8/Bh7to7cHZqiMw6i9nam0nZazEw6Jd1mqM1W+7 FJS5FrEuhJodhG87QzV7jwWO4MEaxGo/r6l2cVQ9naPRBk5h5LqVrVrblDoTKOJ4FiOA MFBB/6FOMRcpFYMlyCIycYp3wPlXzPKiphr6+chYrqrL3kCin3V+REEStPW6ZKKNis6x wbZsCw03EnXF7e4gC1nykVQ8BsSuO7KFYe5F+vaFgyksN/HJJwe1A0K07CbSi2/6Bu2x eHpX2T+S8KpnKVK8nHxpLON8biSBQsw49WkJGS4RssiEVKr2e2glT1+2WoCeHVDoCf27 E0Ew==
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:content-transfer-encoding; bh=7wMmB6L4t7XM/wO6F8UNLM0ObBNED+BBPoGp4d2M/a4=; b=iT8PqG3284GsPkQcO2UVTO9/J8npl+wlr3+JodicSxwcW2APgog9BDEMlyxQGu3HQr 0pB3kMTVV7lGu2L9hjTIrJ9buY40bmvBQJ5waCzaQVVAUtdF19+MtBvjRsx7KOLADYf1 ei3I13X+q1pKnNuP4Lk7q4HFd+Qig4hY07FuB8hFnUM+MIVYQSJoAz9PXAY/gfDmv/M6 +XJEJPC1xvLJcn2yiwl41NXB7yEUb/eOIB0LeLHK7lwBWxFhhC9/IiAHRirYt6XdrTwr 0AsaMposiH2S+sy0Q4zLfsuNQloTGIaPjK9QTQQDBxVjpduXO/n+p646gESyLHbh8AWV SJuw==
X-Gm-Message-State: APjAAAUW34DHw4QN65lO4EWb3vrvoZrHM49L09bxy7nN9iNbdBSuQ7N4 7JVV0YSR76aYOilvp9o39sRweZMwWCrSXiwol4GZnV2K
X-Google-Smtp-Source: APXvYqxnkaB1ofi2nfDt2nR4sU0uL+yRKgy4HGIIpMdw4ubhKVX9b3Y5s5VddZ6j97VXFcZkGD0Qt2/iGTXG+k+iZRw=
X-Received: by 2002:ac8:3014:: with SMTP id f20mr95714085qte.69.1564757826435; Fri, 02 Aug 2019 07:57:06 -0700 (PDT)
MIME-Version: 1.0
References: <CAPF+HwV3EEUza3FyiXsd_oSkj80OwY-tE2DgFWnynq1FL2tLHg@mail.gmail.com> <CAOj+MMHB4BTZqo3YgdrBHCg88RdymS_Xs9Z=XM5pADqh6-uwzg@mail.gmail.com> <CAPF+HwXzMUOF0D-4VFuJ+vkQ+26+1UcEM=fWU=R82M30qra0SA@mail.gmail.com> <DDF61F35-1512-463F-98BC-17F5E6D49110@eu.clara.net>
In-Reply-To: <DDF61F35-1512-463F-98BC-17F5E6D49110@eu.clara.net>
From: Donatas Abraitis <donatas.abraitis@gmail.com>
Date: Fri, 02 Aug 2019 17:56:55 +0300
Message-ID: <CAPF+HwWTJDHGTV+H69ksiBAKzn5WHe7YOQ7eoW4kop=eS4YFnA@mail.gmail.com>
To: Sandy Breeze <sandy.breeze@eu.clara.net>
Cc: Robert Raszuk <robert@raszuk.net>, "idr@ietf. org" <idr@ietf.org>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/idr/MFcSvVcXUat8XXbHamZo1GDZ9q0>
Subject: Re: [Idr] New BGP capability to advertise running daemon version
X-BeenThere: idr@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Inter-Domain Routing <idr.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/idr>, <mailto:idr-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/idr/>
List-Post: <mailto:idr@ietf.org>
List-Help: <mailto:idr-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/idr>, <mailto:idr-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 02 Aug 2019 14:57:21 -0000

Hello Sandy,

>How would you identify versions on those sessions which are down?  Are you assuming the ToR might cache the information after the lifetime of the session?  That’s probably quite implementation specific assumption and I probably wouldn’t bank on it being there.

Good point. This can be reflected in logs or can be stored in peer's
cache (but I'm not sure the latter is the right solution). Another use
case would be like checking why some routes are not announced from
random hosts? Even more, bundling this information together with FQDN
capability would open a bigger picture of what's going on in your
network.



On Fri, Aug 2, 2019 at 5:44 PM Sandy Breeze <sandy.breeze@eu.clara.net> wrote:
>
> Hi Donastas,
>
> >    One simple example is a single ToR device with 300 or 400 VMs under.
> >    Each runs different versions BGP daemons. I noticed that few of 400
> >    peers are down, how would you quickly identify which version or why
> >    they are down? By having version in place it's easy to notice such
> >    things and no need to log into those all 400 hosts in advance.
>
> How would you identify versions on those sessions which are down?  Are you assuming the ToR might cache the information after the lifetime of the session?  That’s probably quite implementation specific assumption and I probably wouldn’t bank on it being there.
>
> I can see value though.
>
> Sandy
>
>


--
Donatas

v2.23.0 | Report a Bug | By Email