[137668] in North American Network Operators' Group
Re: Internet Exchange Point(IXP) questions
daemon@ATHENA.MIT.EDU (Leo Bicknell)
Thu Feb 17 21:31:36 2011
Date: Thu, 17 Feb 2011 18:31:22 -0800
From: Leo Bicknell <bicknell@ufp.org>
To: "Michael K. Smith - Adhost" <mksmith@adhost.com>
Mail-Followup-To: "Michael K. Smith - Adhost" <mksmith@adhost.com>,
"Yaoqing(Joey) Liu" <joey.liuyq@gmail.com>,
"nanog@nanog.org" <nanog@nanog.org>
In-Reply-To: <D8CD26287252844898B508C40824D8F424F3D4@AD-EXH02.adhost.lan>
Cc: "nanog@nanog.org" <nanog@nanog.org>,
"Yaoqing\(Joey\) Liu" <joey.liuyq@gmail.com>
Errors-To: nanog-bounces+nanog.discuss=bloom-picayune.mit.edu@nanog.org
--3MwIy2ne0vdjdPXF
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
In a message written on Fri, Feb 18, 2011 at 02:17:48AM +0000, Michael K. S=
mith - Adhost wrote:
> On the Seattle Internet Exchange (SIX) we have ARIN-assigned addresses th=
at we use on the Layer 2 fabric (your type 2 above). Hopefully the address=
es aren't being announced at all, although we sometimes have to chase down =
people that announce it. Those addresses aren't the destination for any tr=
affic, they are merely part of the transport to a destination, so there is =
no need for them to be in the DFZ.
I've had to deal with exchanges like this in the past, and frankly
they have always been a pain for the support organization.
You see, customers use tools like mtr or Visual Traceroute that do
a traceroute and then continuously ping each hop. Many of these
customers don't have a default route, or default to their _other_
provider. These tools end up showing 100% loss at the exchange,
as they get the traceroute response and then can't ping it.
They then open a ticket, and your support organization has to explain
to them how all of this works and why it isn't the real cause of
their problem.
My preference is that the exchange get an ASN, peer with everyone
(e.g. from the route server) and announce the exchange prefix.
That way it's consistently announced. For exchange that don't do
this, I've always put the prefix into BGP in such a way that I will
announce it but only to my customers to work around this problem.
Please get your own ASN and announce the route, for the sake of all of
your members.
--=20
Leo Bicknell - bicknell@ufp.org - CCIE 3440
PGP keys at http://www.ufp.org/~bicknell/
--3MwIy2ne0vdjdPXF
Content-Type: application/pgp-signature
Content-Disposition: inline
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.13 (FreeBSD)
iQIVAwUBTV3Z+rN3O8aJIdTMAQI/eg/+L8xOzR3Rchg8r9HSGMZpNUfpSvfqGvSe
OgcbX1zAevGkrFG2409b37tzVr7vqod2Ydk39EaLG/FVx1RDZfOwyfpwGWg6+lWG
OCZBH1yJcuJeLoruh6AyQs5cRmkcKkIHtZgiGAKHKEEIYtkGkCxOVXAK1FzsWgN4
tCwDlFrXvNn9LOb0KS/dHclWvErw+pOEKE7ZO99HyjLdv1BcXBQ75vy2lOGDqexF
raIgtEErympmPGeZFWBF5bb+4+DzO0+Rnvoh5Zch8rRHWABNIDx6+cgo8slgbgaL
+fDDO8oUCmIlbUPoWKTzwzNYsn8EZsARqJmwRjrqgm5fLSBSpbBSbYQ7eaagKEXi
y8sX9QqbzFpxO20P0O2sMWMskiR4pPxYTrzvyraga4W6tF3cs+lPKZ04ijYQCfco
bWgKbTvAhbLt9uovIACi5QL/FYvDBwcLU5vRbBZDEkiOQQ3Rfe6aYdyspK/MZoCc
yLmAw4FtNsmDSILq2g2936iYZA/40jY7bHzHJbyDzbcXFwBwKN9HLtie4tiXBWiY
PAOQnK4I2B3vuEF5wnSkvBpH2fdJeZlBPYDlwptt8f2v2279eVCOXNud2TcXwf8d
XP7MzvmVyZ5Mj+X7PBFgxLsGRzalvqAitio+zsvataTKK26oEHXlugV9e6sI68rv
o3fIq1+ry7s=
=6hOv
-----END PGP SIGNATURE-----
--3MwIy2ne0vdjdPXF--
