- Community Home
- >
- Servers and Operating Systems
- >
- Legacy
- >
- HPE 9000 and HPE e3000 Servers
- >
- Re: GSP port settings
Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Forums
Discussions
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Community
Resources
Forums
Blogs
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО10-26-2003 07:01 PM
тАО10-26-2003 07:01 PM
GSP port settings
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО10-26-2003 10:13 PM
тАО10-26-2003 10:13 PM
Re: GSP port settings
9600baud , 8 bit , no parity, 1 stop bit
TT
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО10-28-2003 06:51 AM
тАО10-28-2003 06:51 AM
Re: GSP port settings
I suspect that you want to change from 9600 to a higher speed for performance. Never do anything on the console that requires speed! In fact, never login to the console except during emergencies such as root's login has been disabled, or you need single user mode. The console should be left at a the default value to prevent major difficulties in the future.
Bill Hassell, sysadmin
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО10-28-2003 11:05 PM
тАО10-28-2003 11:05 PM
Re: GSP port settings
I remember that in a previous thread somewhere you said that these values cannot be changed( bit parity ). after reading your answer i feel that maybe u meant that these values should not be changed. i tried serching the forums to find that thread but the forums is experiencing all the service unavailable and page is not available problems again so i could not find it.
Pl forgive me if i am breaking any rules by asking u like this.
Just wanted to know the correct answer and i know you can guide me in the right direction.
regards,
aparna
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО10-29-2003 12:44 AM
тАО10-29-2003 12:44 AM
Re: GSP port settings
Bill Hassell, sysadmin
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО10-29-2003 04:00 AM
тАО10-29-2003 04:00 AM
Re: GSP port settings
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