[145953] in North American Network Operators' Group
BGP AS question
daemon@ATHENA.MIT.EDU (Cliff Bowles)
Thu Oct 27 14:53:31 2011
From: Cliff Bowles <cliff.bowles@apollogrp.edu>
To: "nanog@nanog.org" <nanog@nanog.org>
Date: Thu, 27 Oct 2011 11:51:55 -0700
Errors-To: nanog-bounces+nanog.discuss=bloom-picayune.mit.edu@nanog.org
Greetings. We have a few facilities within a 30 mile radius, and each has a=
n ISP link. We use P2P links at the edge to make certain traffic sourcing f=
rom one facility, and destined to the Public IPs at another, stay on the "d=
irty" links rather than punting out to the ISP. All sites use the same BGP =
AS.
Recently, we were required to turn up an additional facility in a short tim=
e frame. It also uses the same BGP AS. However, it does not have a dirty cr=
oss-connect link. So, even though this facility has unique /24 public IP bl=
ocks, it still has the same AS.
One thing we are noticing is that some ISPs don't seem to have a problem al=
lowing this traffic, and some do. I suspect some don't like traffic with th=
e same source and destination BGP AS, even though the prefixes are differen=
t at each location. But other ISPs seem to permit this with no problem.
My question is: is normal BGP default behavior to permit or to allow this t=
ype of traffic? Also, would it be easier to ask the ISP to make an exceptio=
n, or to buy another AS for the rogue facility?
Thanks.
Clifford W Bowles, Technical Director
Apollo Group | IT Services | Network Engineering
4025 S. Riverpoint Parkway | CF-C201 | Phoenix, AZ 85040
phone: 602-557-6762 | fax: 602-557-6607 | email: cliff.bowles@apollogrp.edu=
<mailto:cliff.bowles@apollogrp.edu>
________________________________
This message is private and confidential. If you have received it in error,=
please notify the sender and remove it from your system.
