I have a Cyclades acs-48 console server. Direct power and Ethernet drop from the ceiling with a public ip. In my subnet, but not through my routers/switches or pdus. Completely out of band, except for relying on colo power/net, which if that's not up then oob is worthless to me anyway.
I have every device hooked to this. Pdus, routers, switches, vm, storage servers. That allows me to get console and power cycle every device. What more would I want? Dialup means I need to be in a place I can hook up a modem. Not too many of those. If I make a configuration mistake, need to reboot a box etc, I want to be able to access my kit from anywhere with ip connectivity. If power or network in the colo is down, then oob does me no good, and I have a dr site for that scenario. That dr site also monitors production and emails my sms address. Michael Thomas <m...@mtcc.com> wrote: >On 01/10/2013 07:02 AM, Jared Mauch wrote: >> On Jan 10, 2013, at 9:51 AM, Mikael Abrahamsson <swm...@swm.pp.se> >wrote: >> >> I certainly want to use something more modern, having run Xmodem to >load images into devices or net-booted systems with very large images >in the past… >> >> I've seen all sorts of creative ways to do this (e.g.: DSL for OOB, >3G, private VPLS network via outside carrier). It is a challenge in >the modern network space. Plus I have to figure that 9600 modems are >going to be harder to find as time goes by.. at some point folks will >stop making them. >> >> > >Isn't the biggest issue here resilience? If you have ethernet/IP as >your >OOB mechanism, how sure can you be that it's really "OOB"? This is, >I'm assuming the fallback for when things are really, really hosed. >What would happen if you needed to physically get hands into many, >many pops? > >Mike -- Sent from my Android phone with K-9 Mail. Please excuse my brevity.
