dialback problems with Sol2.5.1/flow control
2007-12-25 10:53:00
> I am working on an Sun Ultra 2 running Solaris 2.5.1 (with the latest
> patchs) and trying to get dialback running. I have a LASAT Safire modem
> (although i have tried several modems, including a courier) connected via
> serial cable to ttyb. I am at the point that i can call the modem from
my
> pc (via hyperterm), get the password prompt, and get the modem to call me
> back. Then, after connection from the dialback, i get a continuous
> scrolling of 'login' prompts on the screen until i get overflows and am
> forced a disconnect. I have been thinking it was flow control (crtscts),
> but i can't seem to find the problem. If i don't do dialback (just direct
> dialin), all works well. So the problem seems to be when the modem dials
> the pc back and then connects it to the login program running on ttyb.
>
I got a response from ds2sw@worldnet.att.net (Mark Cunningham) that was
right on the money with the problem. Below is a cut-and-paste of several
emails
that we exchanged. I am currently working to get the T-patch for
Solaris2.5.1 to.
get this working. Thanks for all your help everyone!
------------------
I just went thru this problem trying to use zmodem protocol.
I read the pages from celeste. they suggested i set hardware modem flow
control in the /etc/ttydefs (crtscts). caused my modem/os to go into an
echo - login endless loop. Same problem ?
my modems are set for 9600 bi-directional in admintool.
That means that Carrier detect (pin 8 - &c) must be allowed to act
normally.
It is what determines when ttymon spawns a login process on the port. If
you tie
CD high the os will always spawn a login process, and will lock the port.
If you
tie it low the os will never spawn a login.
The login loop comes from cd being high when a modem with echo on enable
attaches.
the os spawns login, the modem echo's login, the os interpets the modem
echo as
a failed login attempt, and respawns login. and around and around she goes.
Sun's official answer was to tie cd low (oops never get a login BAD THING)
or
disable echo (get a login but cant see it REALLY BAD THING)
I have attached the html document where i found this at (included at the
end of this email)
As I said my solution was to
1.)disable hardware flow control in the /etc/ttydefs.
2.) Apply the above Tpatch to get a stable serial buffer.
3.) Set my multitech to factory defaults at&f
4.) Set normal cd operation AT&C1&D2
5.) Set the modem serial port speed to match the ttydefs entry used
when you define the port in admintool. On a multitech the command
is AT$SB9600 or AT$SB19200.
6.) I set my modems up using admintool -> select the port in question
(for me ttyb). Pick the bi-directional modem template. Pick the speed
(for me 9600). Apply and okay.
The Temp Patch number is T105924-04.tar.Z
TALK TO SUN FIRST. This number is for a 2.6 patch.
Pmadm -l output
#
PMTAG PMTYPE SVCTAG FLGS ID <PMSPECIFIC>
tcp listen lp - root - - p -
/var/spool/lp/fifos/listenS5 #
tcp listen lpd - root
\x00020203000000000000000000000000 - p - /var/spool/lp/fifos/listenBSD
#
tcp listen 0 - root
\x00020ACE000000000000000000000000 - c - /usr/lib/saf/nlps_server #
zsmon ttymon ttya u root /dev/term/a b -
/usr/bin/login - 9600 ldterm,ttcompat login: - - n #Modem - Bidirectional
zsmon ttymon ttyb u root /dev/term/b b -
/usr/bin/login - 9600 ldterm,ttcompat login: - - n #Modem - Bidirectional
cat /etc/saf/zsmon/_pmtab output
#
# VERSION=1
ttya:u:root:reserved:reserved:reserved:/dev/term/a:b::/usr/bin/login::96
00:ldterm,ttcompat:login\: :::n:#Modem - Bidirectional
ttyb:u:root:reserved:reserved:reserved:/dev/term/b:b::/usr/bin/login::96
00:ldterm,ttcompat:login\: :::n:#Modem - Bidirectional
grep 9600 /etc/ttydefs
#
9600:9600 -crtscts hupcl:9600 -crtscts hupcl::4800
My modem is a multitech mt 2834
here is the register set
#
# cu -l cua/b
Connected
atl5
B1 E1 M1 Q0 R0 V1 X4 &E1 &E4 &E7 &E8 &E11 &E13 &E15 %C0 #C1 *C0 &C1
$MB9600 $SB9600 $BA0 &W0
OK
atl6
S0 S2 S3 S4 S5 S6 S7 S8 S9 S10 S11 S13 S24 S25 S30
002 043 013 010 008 002 036 002 006 007 070 037 020 000 000
OK
atl7
$A0 &A0 #A0 &B0 &BS1 $D0 &D2 #DB0 %DL0 $EB0 %E1 %E4 #F2 $F0 &G0 #L0 $MI0
&M0 &P0 #P0 &Q0 $R0 &R1 &RF1 &S1 $SP0 &SF0 &T5 #T1 $T1 $V0 $V6 $VD0 &X1 Y0
$MB9600 $SB9600 $BA0 &W0
OK
>From - Wed Apr 15 13:47:43 1998 ---------- Mark, Attached are the modem configuration guides. This service order will be closed upon receipt of this email. Please open a new service order for additional questions or issues. Thank You, ______ > From ds2sw@worldnet.att.net Wed Apr 15 14:25:19 1998 Info Docs article 6428 ---------------------------------------------------------------------------- INFODOC ID: 6428 SYNOPSIS: Manually adding a bidirectional modem on Solaris 2.x Tip still uses the /etc/remote file format. Steps used to get a modem redsands# sacadm -a -p zsmon -t ttymon -c /usr/lib/saf/ttymon -v `ttyadm -V` redsands# pmadm -a -p zsmon -s b -i root -fu -v `ttyadm-V` -m "`ttyadm -b Remember to put the -b option in for bi-directional communications. Also, redsands# more /etc/remote tip1200:tc=UNIX-1200: UNIX-1200: :el=^D^U^C^S^Q^O@:du:at=hayes:ie=#$%:oe=^D:br#1200:tc=dialers: PATCH ID: n/a ---------------------------------------------------------------------------- Questions or comments regarding this service? webmaster Info Docs article 14672 ---------------------------------------------------------------------------- INFODOC ID: 14672 SYNOPSIS: Solaris 2.4/2.5 Modem configuration Solaris 2.4/2.5 Modem configuration and Bi-direction Port Configuration I. Introduction. The following information provides very basic and minimal modem Here are the basic steps: 1- Delete or disable port monitor services for the port to be used. II. Initial Sun setup. 1. Attach the modem on the Sun system. Use either ttya or ttyb and Do not use a null modem (cross over) cable or a null modem gender adapter If you are using a system that shares ports a and b, such as the X985A or 530-1869/C9 2. Add the following entries to the file /etc/ttydefs. These are the 38400m:38400 hupcl:38400 hupcl crtscts::38400m The above definitions turn on hardware flow control (crtscts). Your 3. Verify that there are no port monitor services on the port that is being pmadm -p zsmon -l PMTAG PMTYPE SVCTAG FLGS ID If the services are present, as indicated in the above output, pmadm -p zsmon -r -s or by using the Admintool and selecting Delete or Disable for the port. III. Modem Setup. Modem setup is the responsibility of the customer. This is because www.telebit.com and www.hayes.com. So check the Internet for the latest on your modem. To set the modem registers up correctly, you must be able 1. Make sure the port monitor services are disabled or deleted. tip -38400 /dev/cua/a Use appropriate speed depending on modem and serial device. 2. Verify that the modem is responding to commands. After the Connect at You should see an OK displayed. If not try: ate1q0 (Execute tip in a shell tool without scrolling enabled, otherwise a If you do not get an OK try a different port and/or cable. The modem must 2. Modem register/initialization a. Refer to Appendix B, Common Modem Initialization Strings, AT&F1&B1&C1&D2X0S0=1&W or a simple: at&f1&w should work. Please check your modem manual. b. If you do not have the initialization string, refer to c. After setting up the modem, exit the "tip" utility by The above sequence is a "carriage return" followed by a 3. Using 'cu' command You need 2 lines in the /etc/uucp/Devices file, for example: Direct cua/a - 9600 direct "hayes" refers to an entry in /etc/uucp/Dialers. The generic hayes =,-, "" \dAT\r\c OK\r \EATDT\T\r\c CONNECT or hayes =,-, "" \dAT\r\c OK\r \EATDT\T\r\c CONNECT STTY=crtscts or hayes =,-, "" P_ZERO "" \dAT\r\c OK\r \EATDT\T\r\c Basic cu syntax #cu -d -s To connect to the port in order to change modem registers -d option gives full debug output. #cu -b8 Use for 8 data bits. Otherwise, cu defaults to 7 even parity. #cu -d Use for creating UUCP chat scripts and seeing keystrokes #cu -d -L Use -L for an automated login session. When logging in IV. Starting the Login Process. The following will create a port monitor service to allow login 1. Using the Administration Tool program (admintool), add a bidirectional a. Click on the "Serial Port Manager" icon. b. Highlight the desired port with left mouse button. c. With the right mouse button, press the edit button once. Then d. Press the "Use Template" menu button with the right mouse button e. Press the "Baud Rate: " menu button and select "Other". f. A new popup window will appear. Enter either 38400m, 19200m, or Note- Use the 38400m entry for 28800 baud modems, g. Enter the type of terminal that is going to be logging into h. Verify all fields that data was entered in, then press the i. Quit the Admintool and its windows. 2. Verify that a port monitor was configured by typing the following pmadm -p zsmon -l PMTAG PMTYPE SVCTAG FLGS ID zsmon ttymon ttyb u root /dev/term/b b - If a port monitor is not listed for that port, go back to setup 3 and V. Modem Guidelines. Sun's policy about support of modems is strictly to give guidelines o Make sure the modem uses data terminal ready (DTR). When o Use hardware carrier detect (CD). The modem raises the CD o Modems should send result codes only in answer mode. o The modem serial port speed must be at a fixed baud o Hardware flow control must be used between the Sun system How to resolve the error "All ports busy" when accessing a modem 1) Disable or Delete the port monitor using admintool for that tip -9600 /dev/cua/a 2) Make sure you are not trying to access a device incorrectly 3) There could be a permissions problem on the device. #chmod 666 /dev/cua/a To verify the permission bits and owner use the following #ls -Ll /dev/cua/a Note: If cu is abruptly killed the device will be left 3) Check for a lock file in /var/spool/locks. If there is 4) Another process has the port open. This might be another tip #ps -ef |grep tip Do the following as root: (use appropriate device) #fuser /dev/cua/a #ps -ef | grep 652 The process id's, PID's, are 652 & 651 ( drop the o ) If the process using the port is /usr/bin/login or ttymon, 5) If the process is "ttymon" there are 2 ways to kill the The command to remove the service is as follows: #pmadm -r -p zsmon -s (use pmadm -l to determine SVCTAG) 6) Try bringing system down to single user mode and then back exit Windows 7) The following removes the devices and recreates them without a) To determine the physical device name: ls -al /dev/term/a cd /devices/obio ls -al zs*:a* There are 2 physical devices for a serial port. Each has a different b) Remove the devices: rm zs*:a* c) Remove the links cd /dev/term d) Recreate the devices in /devices and then use ports to /usr/sbin/drvconfig 8) Sometimes a complete reboot is necessary to achieve A P P E N D I X A The following procedure is provided for users that do not have access Setting up Bi-directional modem service from the command line. 1. Check to see if a zsmon process is running under SAC by typing the # sacadm -l 2. If you do not see a zsmon entry under PMTAG, execute the following sacadm -a -p zsmon -t ttymon -c /usr/lib/saf/ttymon -v `ttyadm -V` Check again to see if the zsmon entry is present (STATUS will be 3. Check to see if a zsmon port monitor is present by executing the pmadm -p zsmon -l 4. If a port monitor for zsmon is present, remove it by executing the pmadm -r -p zsmon -s Note - the 5. Configure your port monitor: a. Create or edit a file called pm_script. See below: Note- remember to change the service name, port, and baud rate ---- begin script ------- PATH=PATH$:/usr/sbin: # Below is the ttydefs entry for baudrate usage. Use one of the # Below specifies the port to use. Use either "/dev/term/a" or # Below specifies the service name. Use either "ttya" or "ttyb" # Note that the single quote characters in the command line below are a pmadm -a -p zsmon -s $service -i root -fu -v `ttyadm -V` -m "`ttyadm -Sn ------- end script ----------- 6. Change the permissions of the file for execution and execute the 7. Verify that the port monitor is present: Note - The entry should look like the output below but the # pmadm -p zsmon -l A P P E N D I X B Common Modem Initialization Strings The following contains modem initialization strings to ititialize modems --------------------------------------------------------------- AT&FN0Q2X0&C1&D2S0=1&W --------------------------------------------------------------- AT&F1&B1&C1&D2X0S0=1&W --------------------------------------------------------------- AT&F1&B1&C1&D2X0S0=1&W --------------------------------------------------------------- AT&FQ2X0N0S0=1S37=0&C1&D2&K3&W1&W2 --------------------------------------------------------------- AT&FS52=4Q9S131=1S58=2S68=255S95=0S150=2S50=0S51=5 S51=5 (19200 bps) --------------------------------------------------------------- AT&F2E0Q1S0=1&C1&D2&W&W1 --------------------------------------------------------------- ATN0S37=0S0=1Q1&C1&D2&K3&W A P P E N D I X C Troubleshooting Advice This section contains the most common problems of installing a modem "Garbage from Sun system with remote system logging in" This usually is an indication that the modem speed and the configured --------------------------------------------- "When I make a call, the remote modem answers, I can hear the modems This is probably down to a setting on one or both modems forcing it to --------------------------------------------- "What does 'permission denied or link down' message fro tip utility Make sure you have "dv=/dev/cua/a" or "dv=/dev/cua/b" in --------------------------------------------- "Modems do not disconnect properly or a user stays logged in even after The modem is not configured correctly. The modem must be configured --------------------------------------------- "Nothing happens when trying to tip to the modem" Check cabling to the modem. Check if the proper port is being used. "When dialing into the sun, the modems never pick up the phone." The modem is not configured properly. Check to see if the modem is --------------------------------------------- "Parity problems" I get a login but its corrupted, (Logn: or Logi ) if I press Re-configure the remote computers serial port setup for 8 data bits, --------------------------------------------- "I can't login, password fails." This is a parity problem - The originating terminal / tip session is --------------------------------------------- "When do you modify the eeprom settings?" Don't change the eeproms unless you are trying to get a terminal --------------------------------------------- "No login prompt" Check to see if a ttymon process is started, type the command below: ps -ef | grep ttymon The pid of 208 is the parent ttymon process and the pid of 17258 is Call into the system and see if the ttymon process TTY has changed ps -ef | grep ttymon If this does not occur, check to see of the serial port has been pmadm -p zsmon -l Also check and verify that the port monitor service baudrate matches A P P E N D I X D 1. Prepare to communicate with the modem using the tip utility program. a. Modify the "/etc/remote" file and add the following For ttya port: hardwire: :dv=/dev/term/b:br#9600:el=^C^S^Q^U^D:ie=%$:oe=^D: For ttyb port: hardwire:\ * When using a 28.8k modem, use 38400; for a 14.4 modem, b. Change the permissions and owner of the modem port: chmod 666 /dev/cua/a ; chown uucp /dev/cua/a -- or this for port b -- chmod 666 /dev/cua/b ; chown uucp /dev/cua/b c. After modifying the "/etc/remote" file and changing the tip modem1 You should get a "connected" message. If you get PRODUCT AREA: Gen. Network ---------------------------------------------------------------------------- Questions or comments regarding this service? webmaster Got something to say? You must be logged in to post a comment.
Received: from cobra.sun.decisionone.COM ([192.204.128.125])
by mtiwgwc03.worldnet.att.net (Intermail v3.1 117 241) with SMTP
id <19980415184017.BLBP7425@cobra.sun.decisionone.COM>
for
Received: by cobra.sun.decisionone.COM (SMI-8.6/SMI-SVR4)
id OAA00745; Wed, 15 Apr 1998 14:36:44 -0400
Date: Wed, 15 Apr 1998 14:36:44 -0400
From:
Message-Id: <199804151836.OAA00745@cobra.sun.decisionone.COM>
To: ds2sw@worldnet.att.net
Subject: Re: email adx
Cc:
Content-Type: X-sun-attachment
X-Mozilla-Status: 0011
Content-Length: 31600
X-Sun-Data-Type: text
X-Sun-Data-Description: text
X-Sun-Data-Name: text
X-Sun-Charset: us-ascii
X-Sun-Content-Lines: 34
/_____/\
/_____\\ \ Walter J. Luzak
/_____\ \\ / Technical Support Engineer
/_____/ \/ / / Sun Microsystems - Warranty Support Center
/_____/ / \//\
\_____\//\ / / Phone: 610-296-6067
\_____/ / /\ / Fax : 610-993-6688
\_____/ \\ \ E-mail: wluzak@sun.decisionone.com
\_____\ \\ ==========================================
\_____\/
> From: ds2sw@worldnet.att.net
> Date: Wed, 15 Apr 1998 13:31:40 -0500
> Mime-Version: 1.0
> To: walt.luzak@sun.decisionone.com
> Subject: email adx
> Content-Transfer-Encoding: 7bit
>
> ds2sw@worldnet.att.net
>
----------
X-Sun-Data-Type: default
X-Sun-Data-Name: 6428+89266048128876
X-Sun-Charset: us-ascii
X-Sun-Content-Lines: 57
[ Notify of patch changes ]
[ Edit/Retrieve Marked Documents ] [ Mark Document ]
DETAIL DESCRIPTION:
connected are as follows:
-y "Modem Port"
-i
'Modem Disabled' -l contty5H -m ldterm,ttcompat -r 999 -p 'Good Day Mate :
' -t 300 -T dialup -d /dev/cua/b -s /usr/bin/login`"
remember the deviceslive in the /dev/cua directory.
cuaa:dv=/dev/cua/a:br#19200
dialup1|Dial-up system: :pn=2015551212:tc=UNIX-2400:
hardwire: :dv=/dev/cua/a:br#9600:el=^C^S^Q^U^D:ie=%$:oe=^D:
tip0|tip2400:tc=UNIX-2400:
tip9600:tc=UNIX-9600:
tip19200:tc=UNIX-19200:
UNIX-2400: :el=^D^U^C^S^Q^O@:du:at=hayes:ie=#$%:oe=^D:br#2400:tc=dialers:
UNIX-9600: :el=^D^U^C^S^Q^O@:du:at=hayes:ie=#$%:oe=^D:br#9600:tc=dialers:
UNIX-19200: :el=^D^U^C^S^Q^O@:du:at=hayes:ie=#$%:oe=^D:br#19200:tc=dialers:
dialers: :dv=/dev/cua/a:
PRODUCT AREA: Gen. Network
PRODUCT: Asynch Modem
SUNOS RELEASE: Solaris 2.x
UNBUNDLED RELEASE: n/a
HARDWARE: All
Home | Free Services | Contract Services | Account Services
Table of Contents | Comments about SunSolve | Help | SunSolve FAQ's
Copyright 1994-1997 Sun Microsystems, Inc., 901 San Antonio Road, Palo
Alto, CA 94303 USA.
All rights reserved.
----------
X-Sun-Data-Type: default
X-Sun-Data-Name: 14672+89266029828457
X-Sun-Charset: us-ascii
X-Sun-Content-Lines: 768
[ Notify of patch changes ]
[ Edit/Retrieve Marked Documents ] [ Mark Document ]
DETAIL DESCRIPTION:
(Version 2.0 9/19/96 Kovacs,Edwards)
installation instructions. These instructions give details about
installing a modem on a Solaris 2.4/2.5 Sun system using the standard
ttya or ttyb port. They describe a common method and should prevent any
issues or problems that might arise.
2- tip to port and get an OK back from modem. Set modem registers.
3- Verify the /etc/ttydefs entry for the answering side, and
verify the /etc/uucp/Dialers and /etc/uucp/Devices entries for the
calling side.
If the modem is bidirectional, then all 3 files need editing.
4- Enable the port monitor (login services)and specify a new ttydefs
entry (aka Baud Rate in admintool) if the modem is for dialin.
5- Test dialing out with the 'cu' command.
make sure that the RS-232 cable is a "straight through" cable with
pins 1-8 and pin 20 provided. (Any 25 to 25 pin cable is ok to use.)
cable.
Sparc 10, Classic/LX, or Sparc 20, and you are using port b for
the modem port, you must use a splitter cable. This splitter
cable is available from SunExpress at 1-800-873-7869.
The part number is:
serial port characteristics presented by the answering side.
19200m:19200 hupcl:19200 hupcl crtscts::19200m
9600m:9600 hupcl:9600 hupcl crtscts::9600m
modem needs to have hardware flow control register set for this to
be compatible. Also, the above definition uses 8 data bits, no
parity transfers. Using 'sane' turns ON even parity 7 data bits.
Remember, 14000 and 28800 baud rates are the modem to modem speeds
and 19200 & 38400 are the speeds the modem uses to communicate with
the serial port. Modem to serial port speeds should be faster than
modem to modem speeds, if possible, to prevent bottlenecks.
configured, by typing the command:
zsmon ttymon ttya u root /dev/term/a - -
/usr/bin/login - 9600 ldterm,ttcompat login: - vt100 y #Terminal
zsmon ttymon ttyb u root /dev/term/b - -
/usr/bin/login - 9600 ldterm,ttcompat login: - vt100 y #Terminal
then remove the services by typing:
The login services need to be removed or disabled before a new ttydefs
entry can be used.
there are a variety of types of modems and modem manufactures. If
there are questions regarding modem setup, refer to the modem
manufacturer's documentation and their support. Appendix B contains
examples of modem initialization and register setups. This information
has been gathered and might change because of changes in modem firmware
levels, modem models, and added features. Use this only as a guide.
Most modem manufacturers have Web sites, for example:
to access the modem and its port.
The basic tip command is:
2.5 termio supports higher speeds than 38400. See man termio
and Sunsolve infodoc #12597. This command assumes a modem is
attached to serial port A.
It does NOT require editing of /etc/remote. See last Appendix
for specific information on /etc/remote.
message type:
carriage return (cr) is not sent)
respond to AT commands before proceeding to the following steps.
and see if the modem type is referenced. If so,
set the dip switches and then use that string to initialize
them modem. For example, the US Robotic Courier Modem:
the modem manuals. The following lists the guidelines
to set the modem registers. If you still can not figure
out the initialization string, refer to the modem manufacturer's
technical support.
typing the following sequence:
"~" character and a "." character.
ACU cua/a - 38400 hayes
hayes
entry was written for old 2400 baud modems. Change the generic entry
to:
(for hardware flow control)
CONNECT
(to insure 8 data bit transfers)
---------------
with AT commands, disable the login services
when connecting to the port. The speed above overrides
the speed specified in the Devices file entry.
If the login hangs at the login prompt or the password
prompt, then cu is not able to communicate with the
ttydefs serial port settings on the answering machine.
necessary for successful login.
as a UUCP account you should see "SHERE=
This indicates that uucico is the active process. It will not
timeout and the process will need to be killed. If you are
setting up PPP, use this command to see if login is successful
and PPP packets are sent. A series of { curly braces and other
characters indicate a successful PPP link.
from a modem:
modem service. If you can not use the admintool, refer to appendix A.
with the right mouse button, press the "Modify Service" field.
This will bring up a new popup menu.
and
select the "Modem - Bidirectional" menu item.
9600m according to the desired baud rate of the modem. Then press
the "Apply" button.
the 19200m entry for 14400 baud modems, and 9600m entry
for 9600 baud modems.
the system, e.g. vt100.
"OK" button.
command:
/usr/bin/login - 9600m ldterm,ttcompat login: - dialup n #Modem -
Bidirectional
try again, and make sure that when completing the fields, press the
"OK"
button. If the port monitor still is not listed, call Sun support
for further help.
and not to set up individual modems and modem registers. The
guidelines are given below.
the system drops DTR, the modem should hang up. If the DTR
signal is not asserted, the modem should not answer.
line only when there is an active carrier signal on the phone
connection. When the carrier drops, either because the other
end is alternated or the phone connection is broken, the system
is notified and acts appropriately.
rate. If the modem does not support this feature, do not
use it on a Sun/unix system.
and the modem. Turn off the modem's software flow control
if available.
port?
port. Then try the following using the appropriate device:
specified in /etc/remote when using the tip command.
Use the device /dev/cua/a, for example, and not /dev/term/a.
Change the permissions and owner of the modem port:
#chown uucp /dev/cua/a
options to ls to follow the link to the actual device.
with an owner of the last user using cu.
a lock file, for example LK.032.028.001, then cat the
file. The number displayed is the PID of a process.
Use the ps command above to determine if the process
is still active. Try removing the lock file. If you
still get "All ports busy" then the process will need
to be killed. If the process is defunct it can not be
killed and rebooting will be necessary. This happens
because the driver is waiting at an unkillable level
for a device to respond.
session or another program like lp. It could also be a port monitor.
/dev/cua/a: 652o 651o
#ps -ef | grep 651
either somebody has dialed into your machine hence the modem
will be active or the modem might be asserting DCD all the time,
in which case check the jumpers and modem settings.
process. The easiest is to use the Admintool and select
the port -> Edit -> Delete Service. You should now
be able to tip or cu to the port. (The modem is no longer
configured for dial-in)
up to multiuser mode.
init S
type control-d
rebooting. (Do not perform a boot -r if a SparcStorage Array exists)
lrwxrwxrwx 1 root root 32 Jul 27 1995 /dev/term/a ->
..http://devices/obio/zs@0,100000:a
ls zs*:a*
zs@0,100000:a zs@0,100000:a,cu
crw------- 1 lp tty 29, 0 Feb 19 14:01 zs@0,100000:a
crw-rw-rw- 1 uucp uucp 29,131072 Dec 26 14:08 zs@0,100000:a,cu
minor number which allows the operating system to identify which
driver to use. The a,cu (/dev/cua/a) device is typically used for
modem control and outgoing transactions.
rm a
cd /dev/cua
rm a
recreate the links.
/usr/sbin/ports
a hardware reset on the port. But before rebooting, REMOVE the device
(don't leave a dangling cable - remove the device at the workstation)
and DELETE the port monitor. If after rebooting, the first tip -9600
/dev/cua/a gives an "all ports busy," that means that there is
non-sun
software opening the port.
to the Openwindows interface and cannot use the Admintool.
following command:
PMTAG PMTYPE FLGS RCNT STATUS COMMAND
tcp listen - 0 ENABLED /usr/lib/saf/listen tcp #
zsmon ttymon - 0 ENABLED /usr/lib/saf/ttymon #
command:
STARTING, this is normal).
following command:
PMTAG PMTYPE SVCTAG FLGS ID
zsmon ttymon ttyb u root /dev/term/b b -
/usr/bin/login - 9600m ldterm,ttcompat login: - - n #Modem - Bidirectional
following command:
previous
command. In the above example, this value will be "ttyb".
of the script to match or installation environment.
#!/bin/sh
# script to add a port monitor
export PATH
# following, 38400m, 19200m, or 9600m
ttydefs=9600m
"/dev/term/b"
mport=/dev/term/b
depending
# on the port being used.
service=ttyb
# "back quote" or "back tick". This is normally found below
the double
# quote key ("). This is noted for clarity since some printers do not
# print this character correctly and is printed as a "forward quote" or
# "forward tick" character.
\
-d $mport -b -m ldterm,ttcompat -l $ttydefs -s /usr/bin/login`" \
-y "Modem - Bidirectional"
script (chmod 755 pm_script).
baudrate and service tag may be different.
PMTAG PMTYPE SVCTAG FLGS ID
zsmon ttymon ttyb u root /dev/term/b b -
/usr/bin/login - 9600m ldterm,ttcompat login: - - n #Modem - Bidirectional
for use as dialin and dialout on Sun Solaris systems.
Hayes Optima/Acura Modems:
US Robotics Courier Modems:
dip switch settings:
Switch Setting
1 OFF
2 OFF
3 ON
4 OFF
5 OFF*
6 OFF
7 ON*
8 ON
9 OFF
10 OFF
US Robotics Modems:
Telebit T2500 modems in Conventional mode:
Telebit T2500 modems in Enhanced mode:
S51=4 (9600 bps)
GVC 288 V.34 Modem:
Black Box Corporation, Modem 144FX:
---------------------------------------------------------------
on a Sun Solaris system. Most of all problems are the result of having
the modem incorrectly configured.
port monitor speed is not matched. Check the modem speed and make
certain that it matches the speed of the Sun system. Connect back to
the modem, using tip, and verify modem configuration. Remember, the
modem must be able to lock the modem speed and match the port monitor
speed (speed configured using the admintool.
negotiating, then the modem hangs up CALL FAILED."
use a particular connect speed or compression protocol - if one modem
can't manage to connect up to the other modem, the modem will hang up.
Check the settings of BOTH modems.
mean?"
the
hardwire entry of the "/etc/remote" file. Check also in
"/var/spool/locks" for a lock file LCK.* and remove that file.
Check the permissions on the serial device (/dev/cua/a or
/dev/cua/b) and ownership.
disconnecting."
so that the Data Carrier Detect is asserted only when a carrier is
detected from the remote modem. Refer to the modem documentation.
Also, make certain that "tip" is being used in a shell tool NOT a
command
tool.
setup For auto answer modem (usually S0=1). Make sure that the DTR
or TR light is lit on the modem indicating that the Data Terminal
Ready is asserted from the sun. If it is not, the ttymon process is
either hung or is not running. Try re-initialing the port for
bi-directional modem use.
nothing happens but it does if I press
1 stop bit, and no parity.
using a parity that is different from that used by the ttymon.
working at boot prom level.
root 208 204 80 Sep 21 ? 0:01 /usr/lib/saf/ttymon
root 17258 208 2 10:42:43 ? 0:00 /usr/lib/saf/ttymon
the child process for term/b.
from "?" to "term/b". See below:
root 208 204 80 Sep 21 ? 0:01 /usr/lib/saf/ttymon
root 17258 208 6 10:42:43 term/b 0:00 /usr/lib/saf/ttymon
configured properly and the port monitor service is present by
typing:
PMTAG PMTYPE SVCTAG FLGS ID
zsmon ttymon ttyb u root /dev/term/b b -
/usr/bin/login - 9600m ldterm,ttcompat login: - tvi925 n #Modem -
Bidirectional
the modem baudrate. Use the tip utility and connect back into the
modem.
entry to the file after the "hardwire:\" entry:
Always use the same speed to tip to the modem as
the login process is set to use.
modem1:\ <--- add this and next line
:dv=/dev/cua/a:br#9600: after above entry
^
|_ appropriate baudrate*
must match the login speed
:dv=/dev/term/b:br#9600:el=^C^S^Q^U^D:ie=%$:oe=^D:
modem1:\ <--- add this and next line
:dv=/dev/cua/b:br#9600: after above entry
^
|_ appropriate baudrate*
must match the login speed
use 19200; and for a 9600 modem use 9600.
permission of the port(s), start up a shell tool (if using
openwindows) and issue the following command:
anything else, for example, "all ports busy",
check the "/etc/remote" device entry.
PRODUCT: Serial Comms
SUNOS RELEASE: Solaris 2.5
HARDWARE: n/a
Home | Free Services | Contract Services | Account Services
Table of Contents | Comments about SunSolve | Help | SunSolve FAQ's
Copyright 1994-1997 Sun Microsystems, Inc., 901 San Antonio Road, Palo
Alto, CA 94303 USA.
All rights reserved.
Comments
