10.20 MDP question

[VINCENT SPURGEON]

I have a customer running a 10.20 on a K570. They have recently requested that we add some serial ports and install two modems.

We have added a MDP (5062-3054) to the server and have connected the modems using HP Cable 92219Q in ports 2 and ports 3. I understand that ports 0, 1, and 7 will be used for the console, modem, etc.

When I go through SAM, I only see:
10/4/0 mux2 MUX (3 ports)

I did attempt to create the device files for a dial out modem. When I execute, `ioscan -fnC tty`, I get:

# ioscan -fnC tty
Class I H/W Path Driver S/W State H/W Type Description
============================================================
tty 0 10/4/0 mux2 CLAIMED INTERFACE MUX
/dev/cul0p2 /dev/diag/tty0p12 /dev/diag/tty0p6 /dev/tty0p11 /dev/tty0p5
/dev/cul0p3 /dev/diag/tty0p13 /dev/diag/tty0p7 /dev/tty0p12 /dev/tty0p6
/dev/cul0p4 /dev/diag/tty0p14 /dev/diag/tty0p8 /dev/tty0p13 /dev/tty0p7
/dev/diag/mux0 /dev/diag/tty0p15 /dev/diag/tty0p9 /dev/tty0p14 /dev/tty0p8
/dev/diag/tty0p0 /dev/diag/tty0p2 /dev/mux0 /dev/tty0p15 /dev/tty0p9
/dev/diag/tty0p1 /dev/diag/tty0p3 /dev/tty0p0 /dev/tty0p2
/dev/diag/tty0p10 /dev/diag/tty0p4 /dev/tty0p1 /dev/tty0p3
/dev/diag/tty0p11 /dev/diag/tty0p5 /dev/tty0p10 /dev/tty0p4

However, when I try to access the modems, I get errors like the device isn't found.

# stty < /dev/cul0p2
sh: /dev/cul0p2: Cannot find or open the file.
# stty < /dev/cul0p3
sh: /dev/cul0p3: Cannot find or open the file.
# cu -l /dev/cul0p2 -d 4
call dial(2063837464)
baud=-1, speed=300, line=(null), telno=(null)
call find_dev(17300724430)
baud=-1, speed=300, line=(null), telno=(null)
nomodem is 1
OPEN FAILED /dev/cul0p2, errno = 6
call undial(-6)
Connect failed: line problem
#

I have not rebooted the box since it has a ton of users using it in production.

Will SAM recognize the new ports after the reboot? Is there a way for SAM to recognize the new ports without a reboot?

Thanks for your comments and help.

[A. Clay Stephenson · Accepted solution]

The /dev/culNpP (dial-out), /dev/cuaNpP (ACU Dial-out), /dev/ttydNpP (Dial in) all have characteristics like Data Carrier Detect, DTR, etc. -- so that not only does the cable have to be configured exactly right but the modem must also be configured to assert and recognize the correct signals. You will find that it is much easier to start with the /dev/ttyNpP (Direct Connect) device nodes which look for none of these signals.

I never try to connect modems without a modem manual AND a break-out box so that I can determine what lines have to be jumpered or properly connected to what lines on the other end.

[VINCENT SPURGEON]

Rebooting allowed SAM to see the additional ports. I was confused as to why ioscan could see the ports and SAM couldn't.

[VINCENT SPURGEON]

I can now talk to the modem(s)...

# cu -l cul0p2
Connected
ati7
USRobotics Courier V.Everything Configuration Profile...

Product type US/Canada External
Product ID 00345302
Options HST,V32bis,Terbo,VFC,V34+,V90,V92
Fax Options Class 1,Class 2.0
Clock Freq 25 MHz
Flash ROM 1024k, C2-22D6
Ram 256k

Supervisor date 07/26/04
DSP date 12/16/03

Supervisor rev 2.2.05
DSP rev 2.0.32
DAA rev 0013

Serial Number 3MBUY5OF0983

OK
~[huxal01].

[VINCENT SPURGEON]

Everything is working now. As always thanks for your help.