 |
» |
|
|
|
If you are configuring a modem to the single
modem port on a Series 800 multi-function card, you need to ensure
that the modem port is not locked. Execute a control-B on the console to get
into command mode. This will give you a CM> prompt. Execute a ur command to unlock the remote access port. Execute a dr command to disable the remote access port. Execute a co command to return to the console mode.
Execute the ioscan -C tty
-fn command to identify again the card instance, hardware
path, and port number for the modem port. Create device special files for the modem based on the
card instance (or hardware path) and port number. You can use SAM
to create the device special files (recommended) or use mksf. Modem device files have the following format: Table 3-7 Device Special Files for Modems Access
Mode [1] | Port
Access | Device
File Format |
|---|
0 | Direct
connect | /dev/cuainstance#pport#[2] | 1 | Dial-out
port[3] | /dev/culinstance#pport# | 2 | Dial-in
modem[3] | /dev/ttydinstance#pport# |
| | | |  | NOTE: By default, mkfs creates a device special file for access mode 0 appropriate
for terminals. To create a device file with modem syntax (that is, /dev/cua#p#), you need to execute mksf with the -i option. The -i is used for only direct connect; it is not necessary
for dial-out or dial-in modem files. | | | | |
Here is an example of creating device special files with mksf for a Series 700 whose modem is connected to hardware
path 2/0/4. Note that one file each is created for direct
connect (-a0), dial-out modem (-a1) and dial-in modem (-a2). /usr/sbin/mksf -d asio0 -H 2/0/4 -a0 -i -v
making cua0p0 c 1 0x000000
/usr/sbin/mksf -d asio0 -H 2/0/4 -a1 -v
making cul0p0 c 1 0x000001
/usr/sbin/mksf -d asio0 -H 2/0/4 -a2 -v
making ttyd0p0 c 1 0x000002 |
Series 800 requires yet another additional option when creating
device special files for a modem: you must cite the port number
for the Series 800 in your mksf command. (In the following example, the card instance is
used instead of the hardware path and the port is 2.) Verify the creation of the device special files by using
the lssf command. For the Series 700 example, /usr/sbin/lssf /dev/cua0p0
asio0 card instance 0 hardwired at address 2/0/4 /dev/cua0p0
/usr/sbin/lssf /dev/cul0p0
asio0 card instance 0 callout at address 2/0/4 /dev/cul0p0
/usr/sbin/lssf /dev/ttyd0p0
asio0 card instance 0 callin at address 2/0/4 /dev/cul0p0 |
For the Series 800 example, /usr/sbin/lssf /dev/cua0p2
mux2 card instance 0 port 2 hardwired at address 56/0 /dev/cua0p2
/usr/sbin/lssf /dev/cul0p2
mux2 card instance 0 port 2 callout at address 56/0 /dev/cul0p2
/usr/sbin/lssf /dev/ttyd0p2
mux2 card instance 0 port 2 callin at address 56/0 /dev/cul0p2 |
With your modem still disconnected from
the port, edit the /etc/inittab file to add a getty entry for the modem port that will receive incoming
calls. The entries must conform to the format documented on the inittab(4) manpage
of the HP-UX Reference. For example: p5:234:respawn:/usr/sbin/getty -h -t 240 ttyd2p5 9600 |
The p5 is a label used to uniquely identify the entry. This getty is executed when the system is in both run states 1 and 2. The respawn tells init to restart the process if it dies for any reason. The /usr/sbin/getty is the process used to open the port and provide
the initial login prompt. The -h option ensures that the getty will set the port speed before resetting the port,
which is crucial for the modem to work properly. The -t 240 is a security option to require that the user
login name and password is typed within 240 seconds. The ttyd2p5 is the device for modem port through which the getty will receive incoming calls. (getty will complete the device name by prefixing /dev to the port designation.) The 9600 does not represent the baud
rate, but represents a label in the /etc/gettydefs file. See gettydefs(4).
After saving the file, invoke the following command
to activate the updated /etc/inittab file: To verify that getty is running on the port in a pending state, execute ps-ef | grep ttyd2p5 (using the device file name for which the getty was created). You should see a question mark in
the tty field. With modem still disconnected from the port, but powered
on, the DTR or TR light should be off. Connect the modem to its
port. DTR or TR light should come on. This verifies that the port
(not the modem) is setting DTR or TR. If DTR or TR light remains
on all the time, the modem has DTR strapped high and setting should
be changed. Check the modem users' manual for procedure on how to
change strapping. Execute another ps -ef
| grep ttyd2p5 command to verify that getty is still in a pending state. If getty has a port number in the tty field instead of a question mark, the modem has
carrier detect (CD) strapped high. Check the modem users' manual
for procedure on how to change strapping. At this point the modem is ready for call-in use. To set up the modem for call-out use, you must add entries
to the /etc/uucp/Devices file. (This file does not have an associated manpage; follow
the examples given in the file itself.) Edit /etc/uucp/Devices to include an entry for the /dev/culnpp file created earlier. For example, ACU cul2p5 - 2400 hayes
Direct cul2p5 - 2400 direct |
After saving the file, you can test the modem's call-out
ability executing the following cu command: /usr/bin/cu -s2400 -lcul2p5 dir |
You should get a message indicating that you are connected.
If you enter AT Return, the system will respond with OK. If it does not, the modem might have its echo
turned off. Enter ATDTtelephone_number and listen to the modem to hear if it dials. If the
modem does not dial, refer to your modem user's manual or have the
modem hardware checked out. The modem is now ready for call-out using cu -s2400 telephone_number.
Requirements for Modems to Work on
HP-UX | |
Your modem hardware documentation will be your primary resource
for setting switch positions and commands for proper functioning
of your modem. However, note the following information specific
to HP-UX: The modem should not ignore DTR, but
instead autoanswer when HP computer raises DTR. Modem should hang
up the line, disable autoanswer, and return to command state when
computer drops DTR. (This is AT&D2 on Hayes modem protocol). Do not have the modem
do power-on reset when DTR is dropped, as some modems temporarily raise
CD during reset. (On Hayes modems, do not use AT&D3.) Modem should assert carrier detect only when there
is a carrier and should drop CD when carrier is lost. (This is AT&C1 on Hayes modem). Modem should pass through BREAK, because the BREAK
key is used for the interrupt signal as well as for baud-rate switching. Modem speed between modem and terminal should be
known; however, speed can be negotiated in modem-to-modem connections (using
the modems' autobauding speed detection). Initially, features such
as hardware flow control (CTS/RTS) and error correct should be turned
off. Once you have established that the modem communicates properly,
add these features one at a time. If modems connect but no data appears, turn off
all compression, reliability, MNP, PEP, LAP, and other advanced
features. Set the modem as simply as possible. Once working, add
the advanced features. Do not use CCITT control signals
on modem or HP computer. Note that this does not affect the modem
use of CCITT modulation or compression standards such as V.22, V.32,
V.22bis, V.32bis, V34, V.42, or V.42bis. Save modem settings in non-volatile memory on modem
so modem remembers setup after power loss. (Use AT&W on Hayes modems). Record modem settings on a worksheet in Appendix D “Worksheets” for future reference.
|
Printable version
