From: Ayson, Alison {Info~Palo Alto} (ALISON.AYSON@ROCHE.COM)
Date: Tue Apr 15 2003 - 17:49:36 EDT
My original post:
-------------------------------
I have an L3000 which has ... apparently ... only one serial port. It's the octopus looking thing (with 3 ports) that connects to the L class. It has a "console", "ups" and "remote" port. According to HP the "console" port is the only port that allows for a modem.
I normally have a console hooked up to this port. However we have an application that requires a modem. It needs to be able to receive and dial-out.
I called HP Response center and they told me that I could use the "console" port for the modem. I figured I'd just have to set up the Lan console port for my console.
I sent into SAM-->peripherals-->terminals and modems. SAM came up with /dev/ttyd0p2 which is using the GPS serial console port. I chose this and configured the modem. However, no matter what I do I can't talk to the modem through the port (I can call the modem from my phone and it picks up fine).
I've tried:
kermit
C-kermit> set line /dev/ttyd0p2
C-kermit> set baud 19200
C-kermit> connect
Then everything hangs....I can't get the modems attention.
I don't really like the idea of using the console port for the modem..and it confuses me. How can a port be configured for both? I guess if you reference /dev/console you are getting a different setting (because of /etc/ttytype?). Who knows...I sure don't
At this point I've given up and reconnected the console to the console port (oh yeah..and it hung. I had to reboot the server to get console response back). I think the only solution is to buy a PCI MUX card and install it on the L class and then use that for the modem.
I don't even know what to ask here...the last time I had to install a modem on an HP Unix server was over 6 years ago.
If anyone has a cheat-sheet or suggestions for documentation I can read..I'd appreciate it.
Alison Ayson
Roche Bioscience
Palo Alto, CA
----------------------------------------
I received many replies (thanks) which told me that you CAN use the remote port for a modem. However after following the suggestions I still couldn't get the modem to work. I logged another call with the HP Response Center and they responded with a document (KBRC00011494) which gives step-by-step instructions for configuring an external modem on both an N class and an L class server. I was able to get the modem working (FINALLY!!!). The key was creating an entry in /etc/uucp/Devices. I've pasted in the article from the Reponse Center in case some don't have access to the ITRC website. (NOTE: I had to create an entry in /etc/uucp/Devices for /dev/ttyd0p2 although the document only says to create one for /dev/cul0p2).
Thanks to everyone who responded..
-- Alison Ayson
DocId: KBRC00011494 Updated: 2/3/03 10:57:00 AM
PROBLEM
The HP Support Link Modem MT5634ZBA is attached to the GSP (guardian
service processor) modem port on either a N-Class or L-Class system.
Which steps are necessary to configure the modem for HP-UX dialout
and dialin (session mode) ?
CONFIGURATION
Support Modem MT5634ZBA
N-Class
L-Class
HP-UX 10.X & 11.X
RESOLUTION
To configure the HP Support Link Remote Modem in session mode, follow
the steps below.
Note: If you have an older support modem type MT1432BA, please follow
the procedure in document 1100413790
Modem: installing a MT5634ZBA Modem on the N/L-Class System
Connect the modem to the system
The MT5634ZBA Support Link Modem Kit part number is 0960-1074.
The above kits consist of the MT5634ZBA modem, universal power supply,
power cable, modem cable, MultiModem Quick Start Guide, feet for modem,
and RJ11 cable.
Use either the cable supplied with the modem kit or a 24542M cable.
On the N-Class, attach the modem to the 9-pin connector labeled
"Remote Console Serial Port (Modem)".
On the L-Class, attached the modem to the W-cable connector labeled
"REMOTE".
Connect the telephone line.
Configure the modem port
On the console, type "CTRL-B" to access the GSP. At the GSP prompt,
type the "CA" command (Configure asynch/serial ports) to configure
the port.
GSP> ca
CA
This command allows you to modify the local and remote modem serial port
configurations. Current configuration settings:
Local Console Serial Port bit rate: 9600 bits/s
Local Console Serial Port Flow Control: Software
Local Console Serial Port Terminal Type: hpterm
Remote Console Serial Port Modem Protocol: CCITT
Remote Console Serial Port Modem bit rate: 19200 bits/s
Remote Console Serial Port Modem Flow Control: Software
Remote Console Serial Port Modem Transmit Configuration Strings: Enabled
Remote Console Serial Port Modem Presence: always connected
If the settings differ, change them. The modem will be set up for 19200
baud and software flow control. The modem reset command will be able
to transmit modem configuration strings to configure the modem.
Enable HP-UX dialout and dialin (Session mode)
At the GSP prompt, type the "ER" command (Enable/disable Remote/modem).
GSP> er
ER
Current remote/modem port access: Session
If the setting differs, change it to Session mode. The choices are:
Do you want to modify this configuration? (Y/[N]) y
y
Remote/modem serial port access options:
[L]ocked-out: Lock out all dial-in access.
[G]SP : Dial-in results in a GSP login.
[S]ession : O/S controls modem for dial-in and dial-out
GSP may page in any mode if modem is not in use.
O/S may use modem in Session mode only.
Please indicate the new mode for the remote/modem console serial port,
or to retain current value. Choose one of (L, G, S):
Reset the modem to default values
At the GSP prompt, type the "MR" command (Modem Reset).
This will automatically configure the modem with the correct
default configuration settings.
Create the modem device files
Login to the HP-UX system. Type "CO" at the GSP prompt to get a regular
login prompt.
Verify the device files for the hardware path, example:
# ioscan -funC tty
Class I H/W Path Driver S/W State H/W Type Description
==================================================================
tty 0 0/0/4/0 asio0 CLAIMED INTERFACE PCI Serial (103c1048)
/dev/GSPdiag1 /dev/diag/mux0 /dev/tty0p1
/dev/cua0p2 /dev/mux0 /dev/tty0p2
/dev/cul0p2 /dev/tty0p0 /dev/ttyd0p2
tty 1 0/0/5/0 asio0 CLAIMED INTERFACE PCI Serial (103c1048)
/dev/GSPdiag2 /dev/mux1
/dev/diag/mux1 /dev/tty1p1
Note: The instance number (I) and device file names may differ.
Create the callin and callout device files if they are missing:
# mknod /dev/cul0p2 c 1 0x000201
# mknod /dev/ttyd0p2 c 1 0x000202
Verify the device files:
# ll /dev/*0p2
crw-r--r-- 1 bin bin 1 0x000201 Jan 8 10:44 /dev/cua0p2
crw-r--r-- 1 bin bin 1 0x000201 Jan 8 12:01 /dev/cul0p2
crw--w--w- 1 bin bin 1 0x000200 Apr 28 2000 /dev/tty0p2
crw--w---- 1 uucp tty 1 0x000202 Jan 8 11:52 /dev/ttyd0p2
# lssf /dev/*0p2
asio0 card instance 0 port 2 callout at address 0/0/4/0 /dev/cua0p2
asio0 card instance 0 port 2 callout at address 0/0/4/0 /dev/cul0p2
asio0 card instance 0 port 2 hardwired at address 0/0/4/0 /dev/tty0p2
asio0 card instance 0 port 2 callin at address 0/0/4/0 /dev/ttyd0p2
Edit /etc/inittab
Add an uugetty entry for the modem:
# vi /etc/inittab
...
a0:3:respawn:/usr/lbin/uucp/uugetty -r -t 60 -h ttyd0p2 19200
Note: The "a0" in the above line is a label, which must be unique
in the /etc/inittab file.
Start the uugetty:
# init q
# ps -ef | grep uugetty
root 14521 1 0 11:53:53 ? 0:00 /usr/lbin/uucp/uugetty -r -t 60
-h ttyd0p2 19200
Verify /etc/gettydefs
An entry for 19200 should already exist in /etc/gettydefs:
# vi /etc/gettydefs
...
19200 # B19200 HUPCL IGNPAR PARENB ICRNL IXON OPOST ONLCR CS7 CREAD
ISIG ICANON ECHO ECHOK PARENB ISTRIP IXANY TAB3
# B19200 SANE CS7 PARENB ISTRIP IXANY TAB3 HUPCL
#login: #19200
Edit /etc/uucp/Devices
Add the following line to the end of the file:
# vi /etc/uucp/Devices
...
Direct cul0p2 - 19200 direct
You should now be able to dialout and dialin to the modem. If this fails,
verify the modem configuration:
Check the modem status
At the GSP prompt, type the "MS" command (Modem Status).
GSP> ms
MS
Type to update modem status, or Q/q to quit
-Modem state- ------------ Remote Console Modem Signals -----------
RTS/105 DTR/108 CTS/106 DSR/107 DCD/109 RI/125
Console 0 1 1 0 0 0
Check the configuration
At the HP-UX login prompt, use the "cu" command to connect to the modem
and list the current configuration. The GSP "MR" command should have
configured the modem with these parameters:
# cu -l cul0p2 -s 19200 dir
Connected
at
OK
at&v
Note: If you receive an error from cu "Connect failed: line problem",
reset the modem again using the GSP MR command.
Note: There is a known issue with modem dialin in Session mode with
GSP firmware revisions B.02.08 or later.
Login to the remote modem port fails after the first successful
login and logout. The solution is to update the firmware to
revision B.02.17.
Update to B.02.15 prior to updating to B.02.17. Firmware
revisions B.02.14 or later require the following patches:
HP-UX 11.00
PHNE_27393 s700_800 11.00 Cumulative Mux and Pty Patch
PHCO_27370 s700_800 11.00 mksf(1M) cumulative patch
HP-UX 11.11
PHNE_26326 s700_800 11.11 Cumulative Mux and Pty Patch
PHCO_27243 s700_800 11.11 mksf(1M) cumulative patch
As with all patches, please refer to the Patch Database for the
most recent version of this patch. Patches can be obtained from
the HP IT Resource Center web site at http://itrc.hp.com.
ALT KEYWORDS
N4000 rp7400 rp74xx
L1000 L1500 L2000 L3000 rp5400 rp54xx rp5430 rp5450 rp5470
support modem GSP remote Multitech
--------------------------------------------------------------------------------
--
---> Please post QUESTIONS and SUMMARIES only!! <---
To subscribe/unsubscribe to this list, contact majordomo@dutchworks.nl
Name: hpux-admin@dutchworks.nl Owner: owner-hpux-admin@dutchworks.nl
Archives: ftp.dutchworks.nl:/pub/digests/hpux-admin (FTP, browse only)
http://www.dutchworks.nl/htbin/hpsysadmin (Web, browse & search)
This archive was generated by hypermail 2.1.7 : Sat Apr 12 2008 - 11:02:28 EDT