HPE 9000 and HPE e3000 Servers
cancel
Showing results for 
Search instead for 
Did you mean: 

GSP Settings

 
SOLVED
Go to solution
Sreejith Kaliyam
Regular Advisor

GSP Settings

Hi
How do I change bits and parity of remote console port of L3000
I could change only baud rate from GSP prompt.
Is it something default which you cant change ?? If so what is those values ??

Thanks in advance
Anoop
7 REPLIES 7
aparna challagulla
Valued Contributor

Re: GSP Settings

hi Anoop,

yes u can only change the baud rate of the remote console port. The other settings cannot be changed. i am sorry i dont have any idea about the default values for the bits and parity.

HTH
aparna
If you don't have time to do it right you must have time to do it over
Zeev Schultz
Honored Contributor

Re: GSP Settings

Use GSP ca command. Default emulation is vt100.
The following baud rates are recommended for the revision A GSP:
· Console: 19200

· Remote: 19200

· UPS: 1200
The following baud rates are recommended for the revision B GSP:
· Console: 38400

· Remote: 38400

·
So computers don't think yet. At least not chess computers. - Seymour Cray
Sreejith Kaliyam
Regular Advisor

Re: GSP Settings

Hi zeev,

What is parity and bits?? How will I change ?? Is there any default values
anoop
aparna challagulla
Valued Contributor

Re: GSP Settings

hi Anoop,

the answer is here
http://forums1.itrc.hp.com/service/forums/questionanswer.do?threadId=240132

Have fun
aparna
If you don't have time to do it right you must have time to do it over
Ryan_4
Advisor
Solution

Re: GSP Settings

The Remote Console only works at 8bit no parity -- however, if you use it for session login under hpux, then you can do one of two things:

1. login with the normal user login/password to the port and ignore what the "login" and "password" prompts look like (the parity will make it look scrambled). Hit enter several times until you see a repeatable pattern (this will be the hpux prompt). Then, type:
stty -parity -- then press enter.

This will make the session appear as normal -- but, it is only good for that login session. Once you exit the session, you lose the parity.

2. To make it a permanent situation you will need to modify the /etc/gettydefs file.

You should us 'vi' to edit the /etc/gettydefs file. All instructions included
here expect that you are using this editor to add to the file.

The steps required to set up the gettydefs file for proper 8n1 editing are
a simple A-B-C process. Because the gettydefs follows a specific field
format, we recommend that you DO NOT "hand-type" in the settings. The vi
functions required to copy & paste the necessary settings into place
are as follows:

A. Jump down to the line below the "9600" section (use "j" key). Go to
the insert mode ("i") and hit return to add additional lines. Now hit
escape ("ESC") to return to the editing mode.

B. Go up to the beginning of the "9600" entry (use "k") and "yank"
the four lines containing the indicated port signals (example follows):

--> 9600 # B9600 HUPCL IGNPAR PARENB ICRNL IXON OPOST ONLCR CS8 CREAD
| ISIG ICANON ECHO ECHOK PARENB IXANY TAB3
| # B9600 SANE CS8 PARENB IXANY TAB3 HUPCL
| #login: #300
|
|__(cursor here) =====> Type "4yy" (This will copy 4 lines from the cursor
position on down.)

C. Now, move the cursor down to a BLANK line after the original "9600"
entry and type in "p" ("put") to place the copied lines into position.
If placed correctly, you should have 1 BLANK line between the two "9600"
gettydefs entries and 1 BLANK line below the last "9600" entry. THERE
MUST BE A BLANK LINE BETWEEN EACH GETTYDEFS ENTRY FOR THE SYSTEM TO
PROPERLY FIND AND START A GETTY.

**** YOU ARE NOW READY TO CUSTOMIZE YOUR NEW GETTYDEFS ENTRY ****

**** THIS IS A FOUR STEP PROCESS ****

STEP #1
Add a custom identifier to the addiional 9600 entry to distinguish it
from the one already there (9600M for 9600MODEM).

STEP #2
Delete the "PARENB" in all three lines & change "CS7" to "CS8" in the
first & third lines.

9600M # B9600 HUPCL IGNPAR ICRNL IXON OPOST ONLCR CS8 CREAD
ISIG ICANON ECHO ECHOK IXANY TAB3
# B9600 SANE CS8 IXANY TAB3 HUPCL
#login: #9600M

STEP #3
Change the "#login: #300" (which tells the gettydefs file where to look
for the next entry) to loop back onto itself:

#login: #9600M

***NOTE: If you plan to add custom "19200" entry, set this value
as "19200M" so it can cycle to the "19200M" entry.
AND
If entering a custom "19200M" entry, make sure to change
the "#login: " entry to loop back onto itself (eg. "19200M").

STEP #4
Finally, edit the /etc/inittab entry to reflect the correct gettydefs pointer
to "9600M" (our inittab example shows modem on port 5):

a0:234:respawn:/usr/lbin/uucp/uugetty -r -t 60 -h ttyd0p5 9600M <====

YOU ARE NOW READY TO ADD A CUSTOM ENTRY FOR 19200 (HIGH-SPEED MODEM) IN
THE GETTYDEFS FILE. IF YOU WISH TO DO THIS, RETURN TO STEP "A" AND
SUBSTITUTE "19200" FOR ALL "9600" ENTRIES.

To allow the correct getty to take effect, do a "ps -ef|grep {your ttydXpY}"
to get the PID & then "kill -9" on that PID. The inittab causes the
corrected getty to respawn at the new speed.

Repeat "ps -ef|grep {your ttydXpY} ==> should show pending getty for your
ttydXpY pointing to the "9600M" or "19200M" entry in the gettydefs file.
(example below:)

root 0 1236 1 0 Apr 15 ? 0:00 /usr/lbin/uucp/uugetty -r
-t 60 -h ttyd0p5 9600M

- or -

root 0 1236 1 0 Apr 15 ? 0:00 /usr/lbin/uucp/uugetty -r
-t 60 -h ttyd0p5 19200M
Efim Kushnir
Frequent Advisor
Sreejith Kaliyam
Regular Advisor

Re: GSP Settings

Thank you very much to all of you