[41196] in North American Network Operators' Group

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

RE: FIBER CUT: Dallas to West Coast

daemon@ATHENA.MIT.EDU (E.B. Dreger)
Thu Aug 30 23:08:01 2001

Date: Fri, 31 Aug 2001 03:07:25 +0000 (GMT)
From: "E.B. Dreger" <eddy+public+spam@noc.everquick.net>
To: Chris Boyd <CBoyd@apogeetelecom.com>
Cc: nanog@merit.edu
In-Reply-To: <5A1E91591378D243B6B6C5425F2B2B3E07C14E@apexch.apogeetelecom.com>
Message-ID: <Pine.LNX.4.20.0108310257020.20164-100000@www.everquick.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Errors-To: owner-nanog-outgoing@merit.edu


> Date: Thu, 30 Aug 2001 14:34:03 -0500
> From: Chris Boyd <CBoyd@apogeetelecom.com>
> 
> If you really need diversity, talk to _one_ carrier that can
> go everywhere you need.  It's much easier for one proviioning
> group to make sure that your circuits don't go through the
> same fiber, ring, cross-connect, mux, or office if they have
> complete visibility to both circuits.  Nigh impossible if you
> try to get two different carriers to cooperate like that, I
> would think.

This assumes that said carrier can truly provide that redundancy.
Too often, "separate" paths aren't.  And, after being told things
like "I can't loop your smart jack, so your CSU/DSU is configured
incorrectly", this basement dual-homer questions the local ILEC's
ability to provision over totally separate loops.

Speaking for myself, basement dual-homers want:

* Physically separate paths
* Politically disparate networks
* Complementary IP routes.

in no particular order.

Perhaps the answer is to request two totally different paths from
a provider, then rinse and repeat with a second upstream?


Eddy

---------------------------------------------------------------------------
Brotsman & Dreger, Inc. - EverQuick Internet Division
Phone: +1 (316) 794-8922 Wichita/(Inter)national
Phone: +1 (785) 865-5885 Lawrence
---------------------------------------------------------------------------

Date: Mon, 21 May 2001 11:23:58 +0000 (GMT)
From: A Trap <blacklist@brics.com>
To: blacklist@brics.com
Subject: Please ignore this portion of my mail signature.

These last few lines are a trap for address-harvesting spambots.  Do NOT
send mail to <blacklist@brics.com>, or you are likely to be blocked.


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