[134908] in North American Network Operators' Group

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

Re: co-location and access to your server

daemon@ATHENA.MIT.EDU (Kevin Stange)
Wed Jan 12 17:01:04 2011

Date: Wed, 12 Jan 2011 16:00:58 -0600
From: Kevin Stange <kevin@steadfast.net>
To: nanog@nanog.org
In-Reply-To: <alpine.BSF.2.00.1101121642210.10560@murf.icantclick.org>
Errors-To: nanog-bounces+nanog.discuss=bloom-picayune.mit.edu@nanog.org

This is an OpenPGP/MIME signed message (RFC 2440 and 3156)
--------------enigA777BD2CED3A3C61D967C2A1
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

On 01/12/2011 03:44 PM, david raistrick wrote:
> On Wed, 12 Jan 2011, Jeroen van Aart wrote:
>=20
>> I guess knowing who entered the building by means of a keycard and
>> having cameras isn't considered enough to deter potential "evil
>> doers". I know it's not enough for places like equinix, but that's of
>> a different caliber.
>=20
> Paying for 1u of colo justifys a keycard for you, cameras and keycard
> hardware for the facility?   you're paying what, 50-100$ a month, maybe=

> less?   you realize that low prices comes at the cost of reduced servic=
es?

Having the infrastructure in place to support full cab customers already
and 24/7 remote hands, the cost of providing 24/7 access to smaller colo
customers is negligible.

We could issue a card to every single server one of our colo customers
for only the one-time cost of the card.  It doesn't make sense for most
single-server customers because a tech still has to go into the data
center, unlock the cabinet, fetch a crash cart, etc, so he might as well
let them in the front door.

I guess what you're saying holds true if the facility doesn't already
offer /anyone/ this access regardless of how much equipment and space
they have.

--=20
Kevin Stange
Chief Technology Officer
Steadfast Networks
http://steadfast.net
Phone: 312-602-2689 ext. 203 | Fax: 312-602-2688 | Cell: 312-320-5867


--------------enigA777BD2CED3A3C61D967C2A1
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org/

iEYEARECAAYFAk0uJJoACgkQkd/BoeKjg0gNVgCeJX5m0gk9ZuVowM46k+V+J5ww
9sAAoINc2XFE3Qmxc2ACwYj054nj/O3P
=Z6T0
-----END PGP SIGNATURE-----

--------------enigA777BD2CED3A3C61D967C2A1--


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