nanog mailing list archives
Equinix routeservers (MLPE) behavior c/f no_export
From: "Elmar K. Bins" <elmi () 4ever de>
Date: Fri, 28 Oct 2022 14:21:56 +0200
Hi guys (and others), I couldn't find an official description/explanation of this (EQX docs only mention that this should behave the same as their "set the no_export" TE community. We are using Equinix' IXP platform's routeserver service (MLPE) in a few locations on the planet, and due to the nature of our anycast structure, we are sending our prefixes with the well-known NO_EXPORT community attached. It seems to me that, at least in some places (i.e. Warsaw, ex-PLIX), the routeservers will not forward the routes further, being intransparent to the NO_EXPORT setting. My assumption was transparency, so the prefixes would be forwarded unchanged, including the NO_EXPORT community attached. It would be nice to hear directly from Equinix, of course, but if anybody on this list has hard knowledge of this, please share, so that I can take the appropriate measures... Thanks in advance, Elmar.
Current thread:
- Equinix routeservers (MLPE) behavior c/f no_export Elmar K. Bins (Oct 28)
- Re: Equinix routeservers (MLPE) behavior c/f no_export Frank Habicht (Oct 28)
- Re: Equinix routeservers (MLPE) behavior c/f no_export Elmar K. Bins (Oct 28)
- Re: Equinix routeservers (MLPE) behavior c/f no_export Frank Habicht (Oct 28)