"Dumb" Terminal.

[Jim Gaspers]

We have a console on our rp5405 which is a 700/96 terminal. While trying to break out of a "top" command on the console, I apparently hit some combination of keys which has hung the terminal. We have tried everything we can think of short of rebooting the server, but the terminal just sits there. We don't have a manual, and I can't find anything on the HP web site about this terminal. Anyone know anything which might cause this behavior.

[Uday_S_Ankolekar]

Try killing console session by establishing a telnet session from some other place.



-USA..

[DCE]

You can try turning the terminal off and holding down the "D" key when powering back up.

This will reset the terminal to default settings.

[A. Clay Stephenson]

There are many ways to disable your terminal. It could be waiting for an XON; so the first thing to try is a Ctrl-Q. That probably won't work so power-cycle the terminal. That probably won't fix you either.

Next, System -> Modes

Check that Block Mode does not have an asterisk ('*') and that Remote Mode does have a '*'. Using 'The Force', I think that your Remote Mode is missing its star. If either of these values needs setting, change and save.

[Jim Gaspers]

have already killed the process
have already tried resetting the terminal
also tried respawning the terminal device
tried the recommended Q, didn't work.
checked Block mode has no "*"
Remote mode has a "*"
Still no work. The force is weak.

[G. Vrijhoeven]

Jim,

A rp5470 also has a GSP. You could try connecting a network cable to this device and take over the dumb terminal.

HTH,

Gideon

[G. Vrijhoeven]

Hi,

check this URL for more info.

http://docs.hp.com/en/A5191-96022/index.html


Check the GSP part.


HTH,

Gideon

[Torsten.]

The console is connected to the GSP, right?
Telnet to the box (not to the GSP) and test if the GSP is alive:

#stty +queryGSP
If there is no "functional" message, try to reset the GSP:

#stty +resetGSP

[rick jones]

Rather mundane, but you are sure that the serial cable is still properly connected?

Also, in the terminal config that the proper port on the back of the terminal is selected?

[Jim Gaspers]

Thanks to everyone for their thoughts. We finally gave up and rebooted the machine, and the problem immediately went away.