Re: Shared cabinet "security"

2016-02-13 Thread Bevan Slattery
Sorry. I'm not sure I get from which angle you are coming at this from. Happy to clarify for you and anyone interested if you can help me out here. Cheers [b] > On 13 Feb 2016, at 12:58 PM, Mike Hammett wrote: > > There are more options when you're not just using someone else's datacenter.

Xfinity stale DNS

2016-02-13 Thread Chris Garrett
An inadvertent DNS change was made on one of our domains yesterday. While the rest of the ISP world seems to be working correctly after propagation for the fix, I can not get Comcast / Xfinity to clear the stale records. Anyone have suggestions or experience in moving them along?

Re: Shared cabinet "security"

2016-02-13 Thread Joe Hamelin
On Fri, Feb 12, 2016 at 6:58 PM, Mike Hammett wrote: > There are more options when you're not just using someone else's > datacenter. Indeed, paying for and maintaining your own generator and UPS system, digging up streets for diverse network paths if you can get a CLEC to play with you, twenty

Re: Shared cabinet "security"

2016-02-13 Thread Mike Hammett
Getting a cabinet in someone else's datacenter (Equinix, Coresite, Telx, etc.) and having sub-tenants. Most networks aren't going to need more than a handful of U in a datacenter, but the more significant the datacenter, the less likely they are to provide partial cabinets... which makes no sens

Re: Xfinity stale DNS

2016-02-13 Thread Chris Garrett
This was sorted in record time. Thank you both very much! > On Feb 13, 2016, at 7:26 AM, Chris Garrett wrote: > > An inadvertent DNS change was made on one of our domains yesterday. While the > rest of the ISP world seems to be working correctly after propagation for the > fix, I can not get C

Re: Shared cabinet "security"

2016-02-13 Thread Mike Hammett
Right, but that doesn't limit one's ability (intentional or not) to pull out the wrong power cord or smack someone's loosely ran cables, etc. We're sorting out some standards now and I think it'll largely involve color coding, wire looms, horizontal cable management and a "cabinet practices" doc

Re: Shared cabinet "security"

2016-02-13 Thread Jason Canady
Mike, Are you leasing a full cabinet and sub-leasing out portions of it? Not sure how you can define what other customers do, unless they're your customers. Split cabinets are ideal, as you the sections are compartmentalized. -- Jason Canady Unlimited Net, LLC Responsive, Reliable, Secure

Re: Shared cabinet "security"

2016-02-13 Thread Mike Hammett
AFAIK, there's no way to securely compartmentalize someone else's rack, which is why I've been going down this road. - Mike Hammett Intelligent Computing Solutions http://www.ics-il.com Midwest-IX http://www.midwest-ix.com - Original Message - From: "Jason Canady" To: n

RE: Automated alarm notification

2016-02-13 Thread frnkblk
Thanks, but I don’t see that datadog can ingests SNMP traps – can you point me in the right direction? Frank From: John Adams [mailto:j...@retina.net] Sent: Thursday, February 11, 2016 5:24 PM To: Frank Bulk Cc: nanog@nanog.org list Subject: Re: Automated alarm notification datadog

Re: Shared cabinet "security"

2016-02-13 Thread Greg Sowell
Mike, I've seen people use shelves to segregate cabinets. I've seen some that screw from both sides and eat very little space. Greg On Feb 13, 2016 8:07 AM, "Mike Hammett" wrote: > Getting a cabinet in someone else's datacenter (Equinix, Coresite, Telx, > etc.) and having sub-tenants. Most net

NTT Charles

2016-02-13 Thread Jared Geiger
So who is this Charles fellow in the NTT reverse DNS? ge-102-0-0-0.happy-trails-Charles.r05.asbnva02.us.bb.gin.ntt.net ae-10.happy-trails-Charles.r22.asbnva02.us.bb.gin.ntt.net ae-5.happy-trails-Charles.r25.nycmny01.us.bb.gin.ntt.net ae-2.happy-trails-Charles.r08.nycmny01.us.bb.gin.ntt.net ae-

Re: Shared cabinet "security"

2016-02-13 Thread Chris Woodfield
I've seen colos sell half-racks where both the top and bottoms of the racks have their own cabinet doors. It's not a common thing though. -C > On Feb 12, 2016, at 18:58, Mike Hammett wrote: > > There are more options when you're not just using someone else's datacenter. > > > > > - >