[111859] in North American Network Operators' Group

home help back first fref pref prev next nref lref last post

Re: One /22 Two ISP no BGP

daemon@ATHENA.MIT.EDU (Francois Menard)
Sat Feb 14 09:47:43 2009

From: Francois Menard <francois@menards.ca>
To: Charles Regan <charles.regan@gmail.com>
In-Reply-To: <e353d880902131548m3bda32adi2fab8bee75133190@mail.gmail.com>
Date: Sat, 14 Feb 2009 09:44:44 -0500
Cc: nanog@nanog.org
Errors-To: nanog-bounces@nanog.org

The rule with ARIN is that you only need to demonstrate that you WANT =20=

do do multihoming, not that you WILL do multihoming.

That question would be better asked on the ARIN policy mailing list.  =20=

I'm also on that list.

That was cleared with ARIN as part of the process to get that /22

I guess ARIN rightly assumes that most ISPs do want to do BGP with =20
their customers...

F.
--
Fran=E7ois D. M=E9nard
francois@menards.ca



On 13-Feb-09, at 6:48 PM, Charles Regan wrote:

> The problem we have now is that we got our /22 from arin to do =20
> multihoming.
> If we dump tlb, no more multihoming? No /22. Is that correct?
>
> We also have a contract with tlb.
> $$$ 1.5yrs left...
>
>
>
>
>
>
> 2009/2/13, Seth Mattinen <sethm@rollernet.us>:
>> Charles Regan wrote:
>>> Isp2 is vtl not bell
>>>
>>> 2009/2/13, Seth Mattinen <sethm@rollernet.us>:
>>>> Charles Regan wrote:
>>>>> Just got final confirmation from ISP1 that they will not do BGP =20=

>>>>> with us.
>>>>>
>>>>> ISP1 is Telebec.
>>>>> =
http://www.iptools.com/dnstools.php?tool=3Dipwhois&user_data=3D142.217.0.0=
&submit=3DGo
>>>>>
>>>>> My subnet
>>>>> =
http://www.iptools.com/dnstools.php?tool=3Dipwhois&user_data=3D204.144.60.=
0&submit=3DGo
>>>>>
>>>>> What can we do now ? Any suggestions ?
>>>>>
>>>> Do you know who is upstream of ISP2? We've established that =20
>>>> Telebec is
>>>> only connected to Bell Canada. If ISP2 also has a connection to =20
>>>> Bell
>>>> then you don't gain anything with Telebec except this huge mess and
>>>> horrible hacks to work around their lack of BGP.
>>>>
>>>> ~Seth
>>>>
>>>
>>
>>
>> Also, VTL peers with Sprint and SAVVIS. Based on this information I'd
>> just drop Telebec completely. They only have one upstream. You =20
>> won't get
>> any redundancy with them since they're just giving you a connection =20=

>> to
>> Bell, which VTL already gives you. Here's the view from my SAVVIS =20
>> router
>> with Sprint as the preferred path:
>>
>> routy-border0>show ip bgp 216.113.0.0/17
>> BGP routing table entry for 216.113.0.0/17, version 78286019
>> Paths: (3 available, best #1, table Default-IP-Routing-Table)
>>  Not advertised to any peer
>>  1239 5769, (received & used)
>>    208.79.242.129 (metric 3) from 208.79.242.129 (208.79.242.129)
>>      Origin IGP, metric 439, localpref 100, valid, internal, best
>>      Community: 11170:1239
>>  3561 5769
>>    216.88.158.93 from 216.88.158.93 (206.24.210.102)
>>      Origin IGP, localpref 90, valid, external
>>      Community: 3561:11840 11170:3561
>>  3561 5769, (received-only)
>>    216.88.158.93 from 216.88.158.93 (206.24.210.102)
>>      Origin IGP, localpref 90, valid, external
>>      Community: 3561:11840
>>
>>
>> --
>> Seth Mattinen		sethm@rollernet.us
>> Roller Network LLC
>>
>
> --=20
> Envoy=E9 avec mon mobile
>



home help back first fref pref prev next nref lref last post