nanog mailing list archives

Re: BGP - Traffic Management


From: Ross Tajvar <ross () tajvar io>
Date: Thu, 19 Aug 2021 23:58:34 -0400

Atlantic Metro (now 365 Datacenters) AS29838 allows more specifics on our
backbone. We filter outbound to transit and peering obviously, but we allow
e.g. granular steering if you have more than one port with us.

On Thu, Aug 19, 2021, 1:23 PM Ryan Hamel <administrator () rkhtech org> wrote:

Hello,



Does anyone know of any US carriers that will accept more specific routes
other than what’s required for the DFZ, like “le 31” or “upto /31” (junos
speak) ? I know Zayo supports this internally but would like to know of
other carriers for redundancy.



I am currently dealing with a network that has per region assigned public
IP blocks. I would like to see about moving to announcing aggregates to the
carriers across the MPLS network and redistributing more specifics from
iBGP to the carriers to get the traffic where it needs to be. In a failover
situation these more specifics are also visible on an MPLS backbone where
other transit routers will prepend the AS path upstream based on specific
communities to prevent anycast routing.



Thanks,



Ryan


Current thread: