L3/HE/Inbound Pathing Question
brandon at bitradius.com
Tue Jun 10 05:35:24 UTC 2014
If you're not familiar with how you can engineer traffic on L3's network
take a peek at
3.pdf (slightly outdated but still useful)
As far as HE is concerned, when I asked them about communities a few weeks
ago all they could offer was a blackhole community.
However, as Jay said, you're likely at the mercy of the blended provider and
what they support.
> -----Original Message-----
> From: NANOG [mailto:nanog-bounces at nanog.org] On Behalf Of Jay Hennigan
> Sent: Monday, June 09, 2014 3:10 PM
> To: nanog at nanog.org
> Subject: Re: L3/HE/Inbound Pathing Question
> On 6/9/14 9:38 AM, Dennis Burgess wrote:
> > I have ran into this a few times, and have not found a solution:
> > L3 à
> > HEà --- blended Provider A --- > Customer
> > Cogent -- > Customer
> > Cogent of course is cheaper, and customer wishes to use the blended
> provder more as backup and/or have most of the inbound traffic coming
> in the cheaper path (cogent). The issue appears to be L3 and HE
> specifically (of course they make up a good chunk of inbound traffic)
> always prefers their customer peers, so even if we advertise any prefix
> to the blended, those companies (l3/he) always choose to come in though
> the customer peer and then to my customer.
> > Any thoughts on how to get around this, and still have some kind of
> route in the blended provider for failover? Off list is fine..
> Thanks in advance.
> Advertise a community to the other providers to localpref your prefixes
> down to the point of being a backup.
> 3356:70 should work for Level 3, you will need to talk to HE and/or
> your blended provider for what to use (and whether they support it).
> Jay Hennigan - CCIE #7880 - Network Engineering - jay at impulse.net
> Impulse Internet Service - http://www.impulse.net/ Your local
> telephone and internet company - 805 884-6323 - WB6RDV
-------------- next part --------------
A non-text attachment was scrubbed...
Size: 6328 bytes
Desc: not available
More information about the NANOG