Cohosting around Lebanon - suggestions?

[Dave Johnson]

Christopher Schmidt writes:
> On Fri, Jan 27, 2006 at 01:05:22AM -0500, Ken D'Ambrosio wrote:
> > On Thu, January 26, 2006 11:54 pm, Bill McGonigle wrote:
> > 
> > > We'd probably want to fund a terminal server/remote power unit to share
> > > for decent non-driving management.  I have a Zyplex with lots of serial
> > > ports but it only speaks telnet, so there would be need for a pokey ssh
> > > box in front of it, which might not be worth another U.
> > 
> > Somewhere, I've got a power strip that allows remote access.  Not sure
> > what protocols it speaks.  I think it's an APC, so that probably says
> > something to someone.  I'd be glad to contribute it for this project; I
> > imagine poking around with the docs could get it up and running fairly
> > quickly.  [I, too, have an older-than-death Ethernet-to-RS-232 gizmo. 
> > Since it actually has an AUI port, in addition to the 10-Base-T port, I
> > imagine it only supports telnet.]
> 
> Presumably this is an "APC Masterswitch." I actually wrote a perl script
> to talk to one of those things at Wedu. They're typically pretty simple:
> You telnet in, you can get a status of plugs, you can turn them off or
> on or cycle.
> 
> We used it to do our heartbeat STONITH (Shoot the Other Node In the
> Head) step. Worked pretty well when we wanted to kill a machine and
> din't want to drive to the colo (even though it was only a mile away).
> 
> It does only support telnet, and only 8 char passwords at that. (At
> least, ours does.) Note that this was determined by trial and error, and
> was not documented anywhere obvious.

APC materswitches can also be controlled via snmp which is how I
control mine.  See http://centerclick.org/temp/ms-reboot

Also,  I have a spare 24port 10/100 managed rackmount ethernet switch
that I can bring along.  It supports dot1q so we could use a seperate
vlan for local equipment such as materswitch/console server/etc..


-- 
Dave