[149214] in North American Network Operators' Group
Re: Console Server Recommendation
daemon@ATHENA.MIT.EDU (Nick Hilliard)
Tue Jan 31 05:01:57 2012
X-Envelope-To: <nanog@nanog.org>
Date: Tue, 31 Jan 2012 10:01:32 +0000
From: Nick Hilliard <nick@foobar.org>
To: nanog@nanog.org
In-Reply-To: <20120131091136.GA22047@pob.ytti.fi>
Errors-To: nanog-bounces+nanog.discuss=bloom-picayune.mit.edu@nanog.org
On 31/01/2012 09:11, Saku Ytti wrote:
> For me, required features are
This is part of the problem here. You want a terminal server which was
designed for console access. Most of the terminal servers on the market
are by-products of the modem dialin era and their development function was
aimed at a different market. Consequently, they are better at stuff like
modem dialin and stuff like that rather than console management.
The problem is that there isn't a large market for console servers designed
specifically for management console access, and there are a pile of
incumbents in the existing market place.
I like feature list you posted, btw. If there were any console servers out
there with these features, I would buy a bunch of them.
> RS232 console on control-plane is ridiculously useless, you cannot copy
> images over it (even if supported, images are several hundreds megabytes).
> It is completely dependant on control-plane working which is very poor
> requirement for OOB.
Yeah, indeed. And most of us have been stuck in the "omfg, the router is
crashing and I'm in a hotel 2000km away, with crap OOB access, FML"
situation more than once.
Nick
