[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

cross connect reliability

Subject: cross connect reliability
From: cmadams at hiwaay.net (Chris Adams)
Date: Fri, 18 Sep 2009 13:15:37 -0500
In-reply-to: <[email protected]>
References: <1253223936.6803.391.camel@mike-desktop> <[email protected]> <[email protected]> <[email protected]> <[email protected]> <[email protected]>

Once upon a time, Warren Kumari <warren at kumari.net> said:
> xxx.yyy.zzz.1
> xxx.yyy.zzz.2
> xxx.yyy.zzz.3
> xxx.yyy.zzz.5
> xxx.yyy.zzz.7
> xxx.yyy.zzz.11
> xxx.yyy.zzz.13
> xxx.yyy.zzz.17
> ...
> xxx.yyy.zzz.197
> xxx.yyy.zzz.199

Oh, come on; everybody knows 1 doesn't belong in that list! :-)

-- 
Chris Adams <cmadams at hiwaay.net>
Systems and Network Administrator - HiWAAY Internet Services
I don't speak for anybody but myself - that's enough trouble.

Follow-Ups:
- cross connect reliability
  - From: Valdis.Kletnieks at vt.edu (Valdis.Kletnieks at vt.edu)

References:
- cross connect reliability
  - From: mike at m5computersecurity.com (Michael J McCafferty)
- cross connect reliability
  - From: sethm at rollernet.us (Seth Mattinen)
- cross connect reliability
  - From: tme at americafree.tv (Marshall Eubanks)
- cross connect reliability
  - From: charles at thewybles.com (Charles Wyble)
- cross connect reliability
  - From: ras at e-gerbil.net (Richard A Steenbergen)
- cross connect reliability
  - From: warren at kumari.net (Warren Kumari)

Prev by Date: Weekly Routing Table Report
Next by Date: cross connect reliability
Previous by thread: cross connect reliability
Next by thread: cross connect reliability
Index(es):
- Date
- Thread