Stephen Satchell wrote on 9/24/2015 11:00 AM:
On 09/24/2015 07:05 AM, Blake Hudson wrote:
However, the ultimate way to control routing would be to advertise more
specific prefixes via the path that you want traffic to flow.
Tried that, no joy.
I could only assume then that your peers were
On 09/24/2015 07:05 AM, Blake Hudson wrote:
However, the ultimate way to control routing would be to advertise more
specific prefixes via the path that you want traffic to flow.
Tried that, no joy.
What Blake just said below works best - I do this MED together with
small-ers all the way to india for video conferencing customers sitting in
silicon valley.
Thank You
Bob Evans
CTO
>
>
> Stephen Satchell wrote on 9/24/2015 8:39 AM:
>> On 09/23/2015 02:38 PM, Jason Bullen wrote:
>>> I've alwa
Thank you all for answering. I was disregarding Local Pref because the
route server I was on was showing 100. That was an error on my part though
as it clearly states in the login banner that it is eBGP peering with the
AT&T routers hence the local Pref would go back to 100 from its
perspective.
Stephen Satchell wrote on 9/24/2015 8:39 AM:
On 09/23/2015 02:38 PM, Jason Bullen wrote:
I've always worked in enterprise only so I thought you guys might be
able
to help me with this one.
We are dual homed to Verizon and AT&T. We prepend all our prefixes out
AT&T to make them least preferre
On 24/Sep/15 15:21, William Herrin wrote:
> Hi Jason,
>
> That's normal. Verizon does it too. Both have "community" tags which
> you can attach to your route advertisement. Each will have one that
> indicates they should give external routes the same "local pref" as
> the route you announce to th
On 09/23/2015 02:38 PM, Jason Bullen wrote:
I've always worked in enterprise only so I thought you guys might be able
to help me with this one.
We are dual homed to Verizon and AT&T. We prepend all our prefixes out
AT&T to make them least preferred. During a recent issue we found some
users wer
On Wed, Sep 23, 2015 at 5:38 PM, Jason Bullen wrote:
> So if my research is correct, the internet prefers Verizon UNLESS they are
> a direct AT&T customer then they would use the AT&T circuit.
> Is this a standard practice that I should assume to encounter?
Hi Jason,
That's normal. Verizon does
On 23/Sep/15 23:38, Jason Bullen wrote:
> I've always worked in enterprise only so I thought you guys might be able
> to help me with this one.
> We are dual homed to Verizon and AT&T. We prepend all our prefixes out
> AT&T to make them least preferred. During a recent issue we found some
> us
Many transit providers support BGP communities to modify how your
announced routes are treated within their network. A quick search shows
that AT&T supports BGP community 7018:70 to lower the default local-pref
100 down to 70 (below peer routes). If you tag your AT&T announced
routes with BGP comm
> On Sep 23, 2015, at 5:38 PM, Jason Bullen wrote:
>
> I've always worked in enterprise only so I thought you guys might be able
> to help me with this one.
> We are dual homed to Verizon and AT&T. We prepend all our prefixes out
> AT&T to make them least preferred. During a recent issue we fo
I've always worked in enterprise only so I thought you guys might be able
to help me with this one.
We are dual homed to Verizon and AT&T. We prepend all our prefixes out
AT&T to make them least preferred. During a recent issue we found some
users were coming in via AT&T. Using various looking g
12 matches
Mail list logo
