Re: Affordable IP KVMs?

From: Bob Martin (bob_at_buckhorn.net)
Date: 07/12/04

  • Next message: Gabriel Ambuehl: "Re[2]: Affordable IP KVMs?" 
    Date: Mon, 12 Jul 2004 11:10:01 -0500
To: Gabriel Ambuehl <gabriel_ambuehl@buz.ch>

    We came up with an alternative solution to the IP KVM. Good, old
    fashioned, terminal servers.

    We have an old Livingston PM2E, and our servers are set up to use the
    serial console instead of a console. The whole setup was less than $100.
    And as an added bonus, we now have remote access to our TC 1000 and
    switch consoles. (This would work well for a Cisco too, but we use FBSD
    routers instead)

    There are 2 "gotcha's". This won't work for NT servers, and unless your
    MB supports truly headless operations, you can't access the machine's
    boot. (Most SuperMicro Server MB's will support headless operation, as
    will a lot of the newer 1U servers)

    When combined with a remote power switch, and NIC's with boot ROM's,
    this does create a really cost effective remote solution. I have even
    re-formated and reloaded OS's this way.

    As far as IP KVM's go, you're much better off getting a good one. I
    managed some servers for some folks that tried using cheap IP KVM's.
    Lost time, production and trips to the co-lo quickly made a $1200 IP KVM
    more expensive than the $5100 Cyclades that eventually replaced it.

    If you're only working with one remote server, a modem and a headless MB
    is the only way to go. If you're box doesn't do headless, Cyclades makes
    a remote management card for about $700 (retail) that will solve the
    problem, and give you remote power cycling as well.

    Bob Martin

    Gabriel Ambuehl wrote:
    > Slightly off topic but I assume some people here would know one thing
    > or two about it...
    >
    > I'm in the market for some bullet proof remote administration product
    > (most likely IP KVM but I'm open to other solutions). 99% of all work
    > I can obviously do with ssh but the remaining ones when the server is
    > actually DOWN is were fast fixing is required the most. So what do you
    > people use for remote access to boxes who don't repond anymore? Any
    > pointers to "cheap" IP KVMs (somewhere in the 1000$ range as opposed
    > to the 5000$ one at which point it's probably cheaper to get redundant
    > servers in first place...)?
    >
    > (I know about the serial console and while it certainly has its uses,
    > I'm looking for something *really* bullet proof, enabling me to mess
    > with BIOS etc as well).
    >
    > _______________________________________________
    > freebsd-isp@freebsd.org mailing list
    > http://lists.freebsd.org/mailman/listinfo/freebsd-isp
    > To unsubscribe, send any mail to "freebsd-isp-unsubscribe@freebsd.org"
    _______________________________________________
    freebsd-isp@freebsd.org mailing list
    http://lists.freebsd.org/mailman/listinfo/freebsd-isp
    To unsubscribe, send any mail to "freebsd-isp-unsubscribe@freebsd.org"

  • Next message: Gabriel Ambuehl: "Re[2]: Affordable IP KVMs?"

    Relevant Pages

    • Re: configuration of 2 remote sites
      ... The users at the remote siites will need to access ... You should configure the sites and assign the proper subnets ... to these sites and then use IFM to promote the new additional servers, ... you're using different subnets you may want to setup WINS at these remote ...
      (microsoft.public.windows.server.active_directory)
    • Re: What happens to my W2K domain controllers
      ... Make sure you make the remote dc's gc's as well ... >> offices (running AD-integrated DNS) ... > 2003 member servers. ... >> 8) Run dcpromo on all four old W2k DCs to demote them to member servers. ...
      (microsoft.public.windows.server.active_directory)
    • Re: Restricting access to a web server by IP
      ... > remote control clients, etc - we remotely ... > The agrument against is that mpst vulnerabilities seem to come through ... > servers, and blocking access to all IPs accept those on the allowed list - ...
      (comp.security.firewalls)
    • Re: Restricting access to a web server by IP
      ... > remote control clients, etc - we remotely ... > The agrument against is that mpst vulnerabilities seem to come through ... > servers, and blocking access to all IPs accept those on the allowed list - ...
      (alt.computer.security)
    • Re: MSAccess to Web App
      ... and almost by defintion remote. ... there are any applications running on a web. ... send information back and forth between clients and servers. ... what the client wanted but it's still a joke!). ...
      (comp.databases.ms-access)