|
|
|
|
|
|
|
|
|
|
|
|
| home | help | back | first | fref | pref | prev | next | nref | lref | last | post |
Date: Thu, 17 Sep 2009 20:02:34 -0700 From: "Carlos Alcantar" <carlos@race.com> To: "nanog" <nanog@nanog.org> Errors-To: nanog-bounces+nanog.discuss=bloom-picayune.mit.edu@nanog.org We seem to have the highest failure rate on cross connects from ds3's and t1's. -carlos -----Original Message----- From: Brandon Palmer [mailto:bpalmer@fxcm.com]=20 Sent: Thursday, September 17, 2009 5:59 PM To: Michael J McCafferty; nanog Subject: Re: cross connect reliability We've never had a fiber CC fail. =20 =20 We HAVE had DS3 and T1s fail. Those were due to other customer circuits being installed near ours and bumping them. >>> Michael J McCafferty <mike@m5computersecurity.com> 9/17/2009 5:45 PM >>> All, Today I had yet another cross-connect fail at our colo provider. From memory, this is the 6th cross-connect to fail while in service, in 4yrs and recently there was a bad SFP on their end as well. This seemes like a high failure rate to me. When I asked about the high failure rate, they said that they run a lot of cables and there is a lot of jiggling and wiggling... lots of chances to get bent out of whack from activity near my patches and cables. Until a few years ago my time was spent mostly in single tenant data centers, and it may be true that we made fewer cabling changes and made less of a ruckus when cabling... but this still seems like a pretty high failure rate at the colo. I am curious; what do you expect the average reliability of your FastE or GigE copper cross-connects at a colo? Thanks, Mike --=20 ************************************************************ Michael J. McCafferty Principal, Security Engineer M5 Hosting http://www.m5hosting.com=20 You can have your own custom Dedicated Server up and running today ! RedHat Enterprise, CentOS, Ubuntu, Debian, OpenBSD, FreeBSD, and more ************************************************************
|
|
|
|
|
|
|
|
|
|
|
|
| home | help | back | first | fref | pref | prev | next | nref | lref | last | post |