Re: [Idr] draft-walton-bgp-hostname-capability-00
Dinesh Dutt <ddutt@cumulusnetworks.com> Sat, 16 May 2015 07:00 UTC
Return-Path: <ddutt@cumulusnetworks.com>
X-Original-To: idr@ietfa.amsl.com
Delivered-To: idr@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D03931A9139 for <idr@ietfa.amsl.com>; Sat, 16 May 2015 00:00:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.378
X-Spam-Level:
X-Spam-Status: No, score=-1.378 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=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 NCU9JS56o2TJ for <idr@ietfa.amsl.com>; Sat, 16 May 2015 00:00:49 -0700 (PDT)
Received: from mail-yk0-x232.google.com (mail-yk0-x232.google.com [IPv6:2607:f8b0:4002:c07::232]) (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 D465C1AC3F7 for <idr@ietf.org>; Sat, 16 May 2015 00:00:48 -0700 (PDT)
Received: by ykec202 with SMTP id c202so40340435yke.2 for <idr@ietf.org>; Sat, 16 May 2015 00:00:48 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cumulusnetworks.com; s=google; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=0xwpMdg8VJl1yeQl3QI1pYvI1FjWK8UK1bzyESJgB6U=; b=h2D2BAKUp1ziUh+aMY49Ty4/N0sO+YiRj7iZD3cvTmhbraJx5ScsaqReXIjdfvfhxX ed/qoT2AuH//UQbDO1pTgxkX6Qpy8FgiQnNhzTOaS5IJJYwWJ4K6r0hAtf/Li93lvJFS 0+NVFuhdr/c0aNJra4JQ0c7EupSP8qvFxoGQI=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc:content-type; bh=0xwpMdg8VJl1yeQl3QI1pYvI1FjWK8UK1bzyESJgB6U=; b=SE/MkRtrRHndEkxx+pvjIv62IRPXyrPm5QgPM2AODBPioRdex4+MUxKh89eZ65WsUG wr7UA3AUrZ0lR2+0T5RbzQWe9rkNW37gZu6bPb9Z1dlD2j3Q76QZcy4VxkYy7YZdfNh8 BiOvIeIWaeMtcaFGabx2C4HUWfThflmdViSOSUlwJqS8nRedDi9FeIyuf14tVQL7V+Cv wkh8hHTc+OHEfnEGXmbERJ/2Wmzz2gxUY9h48ztqenzF7/0c0RZ/MKGRxo9kxoqGk3jP c5nNPN4bHICmEJ3nHgTfae3XjFURgW8eBrXvfTpt1qKxnxuzJbG8ePouxN2ftbA0hojd TEUQ==
X-Gm-Message-State: ALoCoQlUIJglZYwdMf7hN0u75SFDM9CEX+kMpU9vyfYoq9do8ESQp1XZ1otC4dafNmw0+dXEOLmR
X-Received: by 10.236.210.69 with SMTP id t45mr13190375yho.75.1431759648119; Sat, 16 May 2015 00:00:48 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.129.103.8 with HTTP; Sat, 16 May 2015 00:00:27 -0700 (PDT)
In-Reply-To: <CA+b+ERmCpjbBmNAeFyNm6_KTWtOB41Zge559O4jbtEjwKG+yXg@mail.gmail.com>
References: <CANL=f0h9ZV+SPr+2vcx2dEk4O9MxBAZJEU7xgHZDC=ep2g2r-g@mail.gmail.com> <m2bnhlwaov.wl%randy@psg.com> <20150516015819.5849234.74476.67011@gmail.com> <CANL=f0gAfs9f-Jt7r3bxMfB7f3Ta+funv8nvmkiCmFsQfGHTcg@mail.gmail.com> <CA+b+ERmY46GHLJUhi5PzwyVJ4Wcns_R11QXC=oLMzAXrYi-v2g@mail.gmail.com> <CABg5FUV5Z+S_m6V7=dB_cuOZpDV-MS_cV+mhwERtjaNCiNfT2w@mail.gmail.com> <CA+b+ERmCpjbBmNAeFyNm6_KTWtOB41Zge559O4jbtEjwKG+yXg@mail.gmail.com>
From: Dinesh Dutt <ddutt@cumulusnetworks.com>
Date: Sat, 16 May 2015 00:00:27 -0700
Message-ID: <CABg5FUVSq4Xunivo3tBNh0=x+W=ZOD9pUYGWs18EcuXiFG-4MQ@mail.gmail.com>
To: Robert Raszuk <robert@raszuk.net>
Content-Type: multipart/alternative; boundary="047d7bfea3f23af3b705162d85b9"
Archived-At: <http://mailarchive.ietf.org/arch/msg/idr/-EYnxj_DTVqt7uJst6a0QlIRUKg>
Cc: idr wg <idr@ietf.org>
Subject: Re: [Idr] draft-walton-bgp-hostname-capability-00
X-BeenThere: idr@ietf.org
X-Mailman-Version: 2.1.15
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: <http://www.ietf.org/mail-archive/web/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: Sat, 16 May 2015 07:00:52 -0000
Hi Robert, On Fri, May 15, 2015 at 11:27 PM, Robert Raszuk <robert@raszuk.net> wrote: > Hi Dinesh, > > Q1 - how do you ping physical interface not a loopback In the DC, common practice I've seen is pinging node, not physical interface. The physical interface addresses aren't even advertised to be able to be reachable more than one hop away. > > Q2 - how about lookup on bgp rtr id instead LL address to get the name ? > I don't lookup LL address. Router ID is typically the loopback IP address in DC, Dinesh > > Cheers, > R. > > > On Saturday, May 16, 2015, Dinesh Dutt <ddutt@cumulusnetworks.com> wrote: > >> Hi Robert, >> >> On Fri, May 15, 2015 at 11:01 PM, Robert Raszuk <robert@raszuk.net> >> wrote: >> >>> Hi Daniel & Dinesh, >>> >>> I very much like the intention, but have a concern how it would simplify >>> troubleshooting in practice ... >>> >>> Imagine we exchange the names in new capability when session comes up so >>> we list it in summary output instead of link local address. But when you >>> try to trace or ping that name (from pc or router) your local or global DNS >>> will return not the LL address but most likely loopback so the results will >>> be rather of questionable value. >>> >> >> I'm confused. Why would we send a hostname in this capability that is >> different from the one assigned to loopback ? Within the DC at least, >> people don't advertise link addresses at all, only the loopback. So, the >> hostname exchanged in the capability would be the same as the one returned >> by traceroute/ping. >> >> Dinesh >> >> >>> Would you not see this as a problem ? I hope you did not intended to >>> just cover the cosmetic nature of few show commands which I must agree with >>> others is rather a legacy way to operate the network these days anyway ;)). >>> >> >> >> >>> >>> Cheers, >>> R. >>> >>> >>> On Saturday, May 16, 2015, Daniel Walton <dwalton@cumulusnetworks.com> >>> wrote: >>> >>>> Many of our customers use a Clos architecture and bgp peer to the IPv6 >>>> LL address of every directly connected router. To avoid configuring >>>> neighbor statements with LL addresses we support a "neighbor swpX >>>> interface" command ("swpX" is the default notation for an interface name in >>>> cumulus linux). We then peer to the LL address on the other end of the >>>> swpX link (we only support this for point-to-point links). >>>> >>>> When you run commands like "show ip bgp summary" you see a list of >>>> interface names instead of IP addresses. Typically if you are loopback >>>> peering you either become familiar with "10.0.0.1 is Chicago" because you >>>> see 10.0.0.1 in the 'show ip bgp summ' output of several different routers >>>> or you could use DNS to do a lookup on 10.0.0.1 and put the hostname in the >>>> output. When every box is peering to LL addresses though ("swpX" for short >>>> for us) you can't easily tell who that peer is and you can't use DNS >>>> because they LL addresses >>>> >>>> *Before* >>>> >>>> leaf-11# show ip bgp summ >>>> BGP router identifier 6.0.0.5, local AS number 65101 >>>> BGP table version 25 >>>> RIB entries 33, using 3960 bytes of memory >>>> Peers 6, using 100 KiB of memory >>>> Peer groups 1, using 56 bytes of memory >>>> >>>> Neighbor V AS MsgRcvd MsgSent TblVer InQ OutQ Up/Down >>>> State/PfxRcd >>>> swp1 4 65000 196 198 0 0 0 00:02:51 >>>> 9 >>>> swp2 4 65000 195 200 0 0 0 00:02:51 >>>> 9 >>>> swp3 4 65000 197 200 0 0 0 00:02:51 >>>> 9 >>>> swp4 4 65000 198 200 0 0 0 00:02:51 >>>> 9 >>>> swp5 4 65201 207 200 0 0 0 00:02:51 >>>> 2 >>>> swp6 4 65202 210 201 0 0 0 00:02:52 >>>> 2 >>>> >>>> Total number of neighbors 6 >>>> leaf-11# >>>> >>>> spine-3# show ip bgp summ >>>> BGP router identifier 6.0.0.15, local AS number 65000 >>>> BGP table version 19 >>>> RIB entries 33, using 3960 bytes of memory >>>> Peers 8, using 134 KiB of memory >>>> Peer groups 1, using 56 bytes of memory >>>> >>>> Neighbor V AS MsgRcvd MsgSent TblVer InQ OutQ Up/Down >>>> State/PfxRcd >>>> swp5 4 65101 675 675 0 0 0 00:10:49 >>>> 5 >>>> swp6 4 65101 678 676 0 0 0 00:10:50 >>>> 5 >>>> swp7 4 65101 667 668 0 0 0 00:10:48 >>>> 5 >>>> swp8 4 65101 676 676 0 0 0 00:10:49 >>>> 5 >>>> swp9 4 65102 701 692 0 0 0 00:11:04 >>>> 5 >>>> swp10 4 65102 701 692 0 0 0 00:11:04 >>>> 5 >>>> swp11 4 65102 701 691 0 0 0 00:11:04 >>>> 5 >>>> swp12 4 65102 701 692 0 0 0 00:11:04 >>>> 5 >>>> >>>> Total number of neighbors 8 >>>> spine-3# >>>> spine-3# >>>> >>>> >>>> *After* >>>> >>>> leaf-11# show ip bgp summ >>>> BGP router identifier 6.0.0.5, local AS number 65101 >>>> BGP table version 25 >>>> RIB entries 33, using 3960 bytes of memory >>>> Peers 6, using 100 KiB of memory >>>> Peer groups 1, using 56 bytes of memory >>>> >>>> Neighbor V AS MsgRcvd MsgSent TblVer InQ OutQ Up/Down >>>> State/PfxRcd >>>> spine-1(swp1) 4 65000 211 213 0 0 0 00:03:07 >>>> 9 >>>> spine-2(swp2) 4 65000 210 215 0 0 0 00:03:07 >>>> 9 >>>> spine-3(swp3) 4 65000 212 215 0 0 0 00:03:07 >>>> 9 >>>> spine-4(swp4) 4 65000 213 215 0 0 0 00:03:07 >>>> 9 >>>> tor-11(swp5) 4 65201 222 215 0 0 0 00:03:07 >>>> 2 >>>> tor-12(swp6) 4 65202 225 216 0 0 0 00:03:08 >>>> 2 >>>> >>>> Total number of neighbors 6 >>>> leaf-11# >>>> >>>> spine-3# show ip bgp summ >>>> BGP router identifier 6.0.0.15, local AS number 65000 >>>> BGP table version 19 >>>> RIB entries 33, using 3960 bytes of memory >>>> Peers 8, using 134 KiB of memory >>>> Peer groups 1, using 56 bytes of memory >>>> >>>> Neighbor V AS MsgRcvd MsgSent TblVer InQ OutQ Up/Down >>>> State/PfxRcd >>>> leaf-11(swp5) 4 65101 1119 1119 0 0 0 00:18:13 >>>> 5 >>>> leaf-12(swp6) 4 65101 1122 1120 0 0 0 00:18:14 >>>> 5 >>>> leaf-13(swp7) 4 65101 1110 1111 0 0 0 00:18:12 >>>> 5 >>>> leaf-14(swp8) 4 65101 1119 1119 0 0 0 00:18:13 >>>> 5 >>>> leaf-21(swp9) 4 65102 1144 1135 0 0 0 00:18:28 >>>> 5 >>>> leaf-22(swp10) 4 65102 1144 1135 0 0 0 00:18:28 >>>> 5 >>>> leaf-23(swp11) 4 65102 1144 1134 0 0 0 00:18:28 >>>> 5 >>>> leaf-24(swp12) 4 65102 1144 1135 0 0 0 00:18:28 >>>> 5 >>>> >>>> Total number of neighbors 8 >>>> spine-3# >>>> >>>> It makes troubleshooting much easier. >>>> >>>> Daniel >>>> >>>> >>>> On Fri, May 15, 2015 at 9:58 PM, <deleskie@gmail.com> wrote: >>>> >>>>> Agree.. adding code for no real operational benefit >>>>> >>>>> Sent from my BlackBerry 10 smartphone on the Rogers network. >>>>> Original Message >>>>> From: Randy Bush >>>>> Sent: Friday, May 15, 2015 10:52 PM >>>>> To: Daniel Walton >>>>> Cc: idr wg; Dinesh Dutt >>>>> Subject: Re: [Idr] draft-walton-bgp-hostname-capability-00 >>>>> >>>>> one more unneeded place for things to go wrong >>>>> >>>>> randy >>>>> >>>>> _______________________________________________ >>>>> Idr mailing list >>>>> Idr@ietf.org >>>>> https://www.ietf.org/mailman/listinfo/idr >>>>> >>>> >>>> >>
- [Idr] draft-walton-bgp-hostname-capability-00 Daniel Walton
- Re: [Idr] draft-walton-bgp-hostname-capability-00 Randy Bush
- Re: [Idr] draft-walton-bgp-hostname-capability-00 deleskie
- Re: [Idr] draft-walton-bgp-hostname-capability-00 Jeff Haas
- Re: [Idr] draft-walton-bgp-hostname-capability-00 Randy Bush
- Re: [Idr] draft-walton-bgp-hostname-capability-00 Daniel Walton
- Re: [Idr] draft-walton-bgp-hostname-capability-00 Robert Raszuk
- Re: [Idr] draft-walton-bgp-hostname-capability-00 Dinesh Dutt
- Re: [Idr] draft-walton-bgp-hostname-capability-00 Robert Raszuk
- Re: [Idr] draft-walton-bgp-hostname-capability-00 Dinesh Dutt
- Re: [Idr] draft-walton-bgp-hostname-capability-00 Thomas Mangin
- Re: [Idr] draft-walton-bgp-hostname-capability-00 Robert Raszuk
- Re: [Idr] draft-walton-bgp-hostname-capability-00 Rajiv Asati (rajiva)
- Re: [Idr] draft-walton-bgp-hostname-capability-00 Rajiv Asati (rajiva)
- Re: [Idr] draft-walton-bgp-hostname-capability-00 Daniel Walton
- Re: [Idr] draft-walton-bgp-hostname-capability-00 Robert Raszuk
- Re: [Idr] draft-walton-bgp-hostname-capability-00 Thomas Mangin
- Re: [Idr] draft-walton-bgp-hostname-capability-00 John Heasley
- Re: [Idr] draft-walton-bgp-hostname-capability-00 Nick Hilliard
- Re: [Idr] draft-walton-bgp-hostname-capability-00 Daniel Walton
- Re: [Idr] draft-walton-bgp-hostname-capability-00 Thomas Mangin
- Re: [Idr] draft-walton-bgp-hostname-capability-00 Dinesh Dutt
- Re: [Idr] draft-walton-bgp-hostname-capability-00 Dinesh Dutt
- Re: [Idr] draft-walton-bgp-hostname-capability-00 Dinesh Dutt
- Re: [Idr] draft-walton-bgp-hostname-capability-00 Job Snijders
- Re: [Idr] draft-walton-bgp-hostname-capability-00 Randy Bush
- Re: [Idr] draft-walton-bgp-hostname-capability-00 Dinesh Dutt
- Re: [Idr] draft-walton-bgp-hostname-capability-00 Randy Bush
- Re: [Idr] draft-walton-bgp-hostname-capability-00 Curtis Villamizar
- Re: [Idr] draft-walton-bgp-hostname-capability-00 jim deleskie
- Re: [Idr] draft-walton-bgp-hostname-capability-00 Randy Bush
- Re: [Idr] draft-walton-bgp-hostname-capability-00 Christopher Morrow
- Re: [Idr] draft-walton-bgp-hostname-capability-00 John Heasley
- Re: [Idr] draft-walton-bgp-hostname-capability-00 Thomas Mangin
- Re: [Idr] draft-walton-bgp-hostname-capability-00 Randy Bush
- Re: [Idr] draft-walton-bgp-hostname-capability-00 Thomas Mangin
- Re: [Idr] draft-walton-bgp-hostname-capability-00 Robert Raszuk
- Re: [Idr] draft-walton-bgp-hostname-capability-00 heasley
- Re: [Idr] draft-walton-bgp-hostname-capability-00 Dinesh Dutt
- Re: [Idr] draft-walton-bgp-hostname-capability-00 Dinesh Dutt
- Re: [Idr] draft-walton-bgp-hostname-capability-00 Thomas Mangin
- Re: [Idr] draft-walton-bgp-hostname-capability-00 Thomas Mangin
- Re: [Idr] draft-walton-bgp-hostname-capability-00 Robert Raszuk
- Re: [Idr] draft-walton-bgp-hostname-capability-00 Thomas Mangin
- Re: [Idr] draft-walton-bgp-hostname-capability-00 Ćukasz Bromirski
- Re: [Idr] draft-walton-bgp-hostname-capability-00 Daniel Walton
- Re: [Idr] draft-walton-bgp-hostname-capability-00 Daniel Walton
- Re: [Idr] draft-walton-bgp-hostname-capability-00 Daniel Walton
- Re: [Idr] draft-walton-bgp-hostname-capability-00 Daniel Walton
- Re: [Idr] draft-walton-bgp-hostname-capability-00 Acee Lindem (acee)
- Re: [Idr] draft-walton-bgp-hostname-capability-00 Thomas Mangin
- Re: [Idr] draft-walton-bgp-hostname-capability-00 Curtis Villamizar
- Re: [Idr] draft-walton-bgp-hostname-capability-00 Randy Bush
- Re: [Idr] draft-walton-bgp-hostname-capability-00 Curtis Villamizar
- Re: [Idr] draft-walton-bgp-hostname-capability-00 Christopher Morrow
- Re: [Idr] draft-walton-bgp-hostname-capability-00 Dongjie (Jimmy)
- Re: [Idr] draft-walton-bgp-hostname-capability-00 Hannes Gredler
- Re: [Idr] draft-walton-bgp-hostname-capability-00 bruno.decraene
- Re: [Idr] draft-walton-bgp-hostname-capability-00 Nick Hilliard
- Re: [Idr] draft-walton-bgp-hostname-capability-00 Neil J. McRae
- Re: [Idr] draft-walton-bgp-hostname-capability-00 Jeffrey Haas
- Re: [Idr] draft-walton-bgp-hostname-capability-00 Daniel Walton
- Re: [Idr] draft-walton-bgp-hostname-capability-00 Dongjie (Jimmy)
- Re: [Idr] draft-walton-bgp-hostname-capability-00 Jon Mitchell