[Date Prev] [Date Index] [Date Next] [Thread Prev] [Thread Index] [Thread Next]
Bryan Stansell bryan@conserver.com
Tue, 8 Nov 2005 22:11:18 -0800 (PST)
and here's my 2 cents... after following some links on their support site, i found the docs here: http://www.raritan.com/_downloads/pdfs/products/user_man_dom_sx.pdf after a quick scan through it, it doesn't look like they offer plain old telnet-style access to the ports. they do allow you to ssh into the box and then connect to a console via their cli. they even show: $ SSH -l dominion -t 192.168.51.225 "sconsole -u admin -a pass123 -p 2" as an example of how to connect to port #2 with a username of admin and password of pass123. that's workable (from a conserver perspective), but not ideal. why? because when you do that you are going through what looks like their own console management system. you can be connected read-write or read-only, you have an escape key that takes you to a cli for doing things with the port (like sending a break), etc. just an alternate take on the conserver experience, really. so, you have two layers of console management going on - one on the box, another by conserver. will the two play well together? what's the definition of "well"? ;-) will it be easy to configure the box and have conserver talk to it? perhaps. take out "easy", and yeah, it could work. assuming it can handle 48 full-time ssh connections. could it start getting complicated if someone uses their web interface or another ssh connection to bump you to read-only on the box but conserver still thinks it's read-write? i'd think so. impossible to work with? nah. those are just a few of my random thoughts. can it be made to work? i think so. would other things integrate "easier", yep. remember, the flexibility of conserver makes it able to talk to many things...you'll have to judge for yourself whether or not it *should* talk to a particular thing. (btw, in general the box does seem to have a lot of cool features) Bryan