[44908] in North American Network Operators' Group
Re: Automated DLR conflict detection
daemon@ATHENA.MIT.EDU (Valdis.Kletnieks@vt.edu)
Sat Dec 29 06:17:21 2001
Message-Id: <200112291116.fBTBGXW5009633@foo-bar-baz.cc.vt.edu>
To: Sean Donelan <sean@donelan.com>
Cc: nanog@merit.edu
In-Reply-To: Your message of "Sat, 29 Dec 2001 04:32:08 EST."
<Pine.GSO.4.40.0112290239530.29284-100000@clifden.donelan.com>
From: Valdis.Kletnieks@vt.edu
Mime-Version: 1.0
Content-Type: multipart/signed; boundary="==_Exmh_164454912P";
micalg=pgp-sha1; protocol="application/pgp-signature"
Content-Transfer-Encoding: 7bit
Date: Sat, 29 Dec 2001 06:16:33 -0500
Errors-To: owner-nanog-outgoing@merit.edu
--==_Exmh_164454912P
Content-Type: text/plain; charset=us-ascii
On Sat, 29 Dec 2001 04:32:08 EST, Sean Donelan said:
> How can you perform due dilegence on a carrier? With a car, you
> can open the trunk and check the spare tire. What is the best way
> to check a spare circuit?
How do you know it's a <insert vendor> field engineer trying to fix a
flat tire? He keeps swapping tires till he finds the flat one...
Make sure your testing procedure *really* tests the actual spare circuit,
not something else's representation of one. I know one poor soul who
wrote software to monitor-via-ping the other end of a point-to-point,
then watched in horror as a co-worker accidentally removed the entire
DSU from the rack, unwilling to say "Wait, that's the wrong one" because
the monitor hadn't burped an error.
Guess who's network was basically a triangle? ;)
--
Valdis Kletnieks
Operating Systems Analyst
Virginia Tech
--==_Exmh_164454912P
Content-Type: application/pgp-signature
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: Exmh version 2.5 07/13/2001
iD8DBQE8LaYQcC3lWbTT17ARAuqeAJ0QagFhJkKHtf4Qow/F4L/12IpyEwCgkDnM
Ka/i4ww2kvzPMzSJGP/L6nQ=
=I5J7
-----END PGP SIGNATURE-----
--==_Exmh_164454912P--
