Devin Reade |
GNO Consortium | Home | GNO/ME |
Are you thinking about purchasing a second-hand Xyplex 1600? Are you thinking about introducing these devices that you've had collecting dust on your shelf into your production environment? Before you do, you should read my observations on the matter.
In general, no. I've tried to collect what Xyplex information that I have on this site, so if it isn't here I probably don't know it. I've also retired almost all of my Xyplexes from service at this point.
I'm sorry, but I don't really have enough hours in the day to volunteer one-on-one assistance. I potentially could be paid to go splunking for a solution, but to be honest if you can't afford a more modern console server, then you can't afford my consulting rate.
Note that the Xyplex 1600 cannot handle SSH or other secure protocols, and therefore be placed on a secure administrative network when using it as a console server.
The configuration for your Xyplex terminal server will obviously be very dependent on how you're using it. Sometimes you have to experiment with the configuration to solve things like echo problems, double line feeds, et cetera. With that in mind, here is a sample configuration that assumes that you will be using port 1 for configuring the console itself, and the rest of the ports are being used to access other servers' consoles.
Manufacturer's Documentation | Other Documentation | |||||||||
|
|
The Xyplex 1600 came in two configurations; one with 1 MB RAM minimum and one with 3 MB RAM minimum. Some or all models may have memory expansion slots. Good luck finding memory ...
I suspect that at least some of the following files will also work for an MX1500 and maybe other models, but I don't know and the risk is all yours. Enjoy.
Common Files |
|
|||||
Files for 1MB (min) Xyplex |
|
|||||
Files for 3MB (min) Xyplex |
|
Contact me @ gdr at gno.org |
Last Updated: 13 Mar 2006 |
|