There's been plenty of change in the 3000 manager's life over the last 10 years. Some of it might involve changing the location of HP 3000s from one part of the IT shop to another. Users and support experts have discussed the many ways to adjust a 3000 console's location. The method you choose depends on budget, experience and technical skills depth.
Kent Wallace, a 3000 manager for Idaho-Oregon healthcare delivery system Primary Health, needed to move his 3000 console:
I was asked to move the console another 10 feet (more) from the rack (it's an N-Class HP 3000/N4000-100-22). What are the 3 pin positions on the wire that I need to extend this RS-232 cable?
Reid Baxter of JP Chase offered the most direct answer, for those willing to modify cables. "Pins 2, 3 and 7."
Tracy Johnson of Measurement Specialties added:
In addition to what Reid said, you can also get a 3-pin mini-din extension cord and extend the other end.
Our blog contributing editor Gilles Schipper chipped in with a solution offering even farther movement:
If you want to extend the range of the console to anywhere on the planet (at least where there’s Internet access) you could consider the HP Secure Web Console to replace the physical console.
Depending upon the condition of your physical console, this solution may also save a bit of wear and tear on your eyeballs.
(Schipper wrote us a great article on setting up such a web console.)
Former HP support engineer Lars Appel offered another take on Schipper's strategy:
While Gilles is right about the possibility of using the web console, it would probably be easier to use the already built-in dedicated LAN port of the N-Class systems that gives access to the GSP by telnet.
I prefer the “telnet console” over the “web console” because it gives more freedom in the choice of terminal emulator — whereas the web console typically lacks features like “easy cut and paste” or special key mappings (e.g. German language ;-) or something similar.
This prompted Schipper to clarify his suggestion:
Lars is absolutely right about the built-in “secure-web-console” that comes with all N-Class and all but the earliest A-Class e3000s.
And, yes, the built-in is definitely more functional, allowing cut-and-paste as well as telnet access, whereas the external variety has only Java access to it via a web browser and no cut-and-paste.
So, if one has a choice, the built-in is definitely superior and available with only proper configuration.
However, the external secure web console is available for all HP 3000s, and would still be most useful where is internal secure web console is not an option.
Jeff Kell, curator of the 3000 newsgroup where the advice appeared, added the last word and a little joke:
The internal one isn't really "secure" — it's plaintext telnet. The GSP "documents" some secure access mode (ssh? https?) but I could never get it to work on our A-Class. Maybe it's an HP-UX thing.
The external web console was the really insecure "secure" web console. It used a secret decoder ring :-)