secure web console is displaying rubbish ?

[Scott Dunkley]

When I logon onto Secure Web console it isnt displaying the right characters it just displays rubbish, is there some sort of term setting I need to set within secure web console ?

[harry d brown jr]

Scott,

(1) What kind of web console, on what kind of server, and what OS?

(2) Is the web console branded HP or is it an Arula (the manufacturer for them anyways)?

(3) If it is an external web console, connected to the serial port, then I believe that the serial port has to be set to 9600 baud.

(4) Also, when you say it is displaying garbage, do you mean the terminal display area or the entire web page? If it is just the terminal area, try "resetting" the web console.

(5) Using the same cable hooked to your web console, will a HP serial console work?

(6) Also, what terminal type are you using?

live free or die
harry

[Darrell Allen]

Hi Scott,

Here's the settings I find work best on HP's web console:

term type vt100
baud rate 9600
Parity/data bits none/8
parity checking disable
Xon/Xoff not selected

The above came from http://forums.itrc.hp.com/cm/QuestionAnswer/1,,0xb011630fe5c4d5118ff10090279cd0f9,00.html

Darrell

[Uday_S_Ankolekar]

Hi,

First check the TERM type and export it accordingly (TERM=hp;export TERM) Also check the baud rate speed , it should be 9600
and finally check the cable is right.

Good Luck,
-USA..

[Tom Geudens]

Hi,
I don't want to tell everything different from the others :-), but I solved the "garbage" by setting the Web Console terminal setting to HP2392.

Kind regards,
Tom Geudens

[Bill Hassell]

The term garbage characters needs to be quantified just a bit. If there are perfectly fine characters on the screen with a few wierd characters such as numbers and square brackets (something like: [4h [?25I and so on), these are special codes typically defined for vt100 and similar terminals. If these codes are sent to an HP terminal program, they will produce the above result.

There are two places where the terminal emulators must match: the GSP (for N, L, A class machines) and the Web Console. The default (IMHO incorrectly chosen) is vt100, not hpterm and this GSP setting is carried into HP-UX each time you login. Due to special code in ttytype and tset, the GSP overrides what the 'real' terminal (in this case, the Web Console) is using.

The other location is the Web Console itself. To see what the web console is using, open the main window and click on the left frame under Support to see: Configuration report.

Now, if the GSP is overriding the Web Console's setting, you'll see these extra characters, especially with smart terminal programs like vi, sam and swinstall...the screen will be a mess because HP-UX was told to use the wrong terminal control codes.

To synchronize the two processes, I would leave the Web Console as HP2392A and change the GSP to use hpterm as the mode for the console. You do this by using CTRL-B to get to the GSP (you can use the Web Console for this), then type: CA and follow the instructions to change the Local Console Serial Port Terminal Type to hpterm. Leave the other settings alone and exit back to HP-UX by using the CO command.

Now when you login, the terminal codes sent out by vi and sam, etc will match the Web Console's terminal type.

[Scott Dunkley]

thanks for all the ideas, so far I have tried ctrl-b to GSP prompt then typing CA and all settings are fine baude rate is 9600 and term setting is vt100. Term setting on web console is vt100, and I tried the HP one too. Plugged in a normal serial console and the same is true of that, tried EM100 and HP as the console term setting, still no joy......it is HP-UX 11.00 (64-bit), the web console is made by HP, supposedly, prbably just a badge....lol!
The garbage on the screen is unreadable, these are not codes and most not even real letters, just symbols and stuff......hmmmmm!

Any other ideas ?

Scott.

[Angus Crome]

Make sure you have Cat3 or better networking cable going to the console.

Also, if you are plugged into a HUB or switch, try bypassing it. The 3Com Hub I used to use (10BaseT) was generating all kinds of electrical noise on the wires. I replaced it with something a little more robust (an HP Procurve switch).

Finally, if you haven't already tried it. Do a reset on the Console and reconfigure it. Out of the 15 I have setup here, two of them blinked out on me immediately after the initial configuration. After reset/reconfig, everything worked fine.

[John Payne_2]

You plugged a physical console in, and it is working, but SWC is not? What kind of machine do you have? One that has those little 3-way dongles you have to attach? If so, are you sure that you are plugging into the one marked 'console'?

Justa thought.

John

[Sanjay_6]

Hi Scott,

Try this link on how to configure SWC,

http://docs.hp.com/hpux/onlinedocs/hw/swc/index.html

http://docs.hp.com/hpux/onlinedocs/hw/swc/install/NIL0002J9.html

Hope this helps.

Regds

[Bill Hassell · Accepted solution]

No, the HP terminal is not an OEM (badged) unit. HP invented their smart terminal design more than 20 years ago and have manufactured HP terminals every since then. LaserJet and DeskJet printers base their PCL codes on HP terminals.

Since the GSP works correctly but the login has nothing but garbage characters, have you checked gettydefs and inittab? inittab should use the gettydefs entry called console and it should match the default version stored in /usr/newconfig/etc/gettydefs. A bad gettydefs entry (setting the stty values incorrectly) could produce garbage for HP-UX but leave the GSP unaffected as the GSP is a separate computer.

If all that checks out, you may have a bad GSP which can fail like any other component. The GSP must control the path to/from the HP-UX console data so an electronic failure is certainly possible.