SUMMARY: dialback problems with Sol2.5.1/flow control

From: John Dyson (
Date: Thu Jul 23 1998 - 10:25:53 CDT

Here is a short summary of my question:
> 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
> 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 (Mark Cunningham) that was
right on the money with the problem. Below is a cut-and-paste of several
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
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
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)
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
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
00:ldterm,ttcompat:login\: :::n:#Modem - Bidirectional
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
B1 E1 M1 Q0 R0 V1 X4 &E1 &E4 &E7 &E8 &E11 &E13 &E15 %C0 #C1 *C0 &C1
$MB9600 $SB9600 $BA0 &W0

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

$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


>From - Wed Apr 15 13:47:43 1998 Received: from cobra.sun.decisionone.COM ([]) by (Intermail v3.1 117 241) with SMTP id <19980415184017.BLBP7425@cobra.sun.decisionone.COM> for ; Wed, 15 Apr 1998 18:40:17 +0000 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: 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 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, ______ /_____/\ /_____\\ \ Walter J. Luzak /_____\ \\ / Technical Support Engineer /_____/ \/ / / Sun Microsystems - Warranty Support Center /_____/ / \//\ \_____\//\ / / Phone: 610-296-6067 \_____/ / /\ / Fax : 610-993-6688 \_____/ \\ \ E-mail: \_____\ \\ ========================================== \_____\/ > From Wed Apr 15 14:25:19 1998 > From: > Date: Wed, 15 Apr 1998 13:31:40 -0500 > Mime-Version: 1.0 > To: > Subject: email adx > Content-Transfer-Encoding: 7bit > > > ---------- X-Sun-Data-Type: default X-Sun-Data-Name: 6428+89266048128876 X-Sun-Charset: us-ascii X-Sun-Content-Lines: 57 Info Docs article 6428 [ Notify of patch changes ] [ Edit/Retrieve Marked Documents ] [ Mark Document ] ---------------------------------------------------------------------------- INFODOC ID: 6428 SYNOPSIS: Manually adding a bidirectional modem on Solaris 2.x DETAIL DESCRIPTION: Tip still uses the /etc/remote file format. Steps used to get a modem connected are as follows: redsands# sacadm -a -p zsmon -t ttymon -c /usr/lib/saf/ttymon -v `ttyadm -V` -y "Modem Port" redsands# pmadm -a -p zsmon -s b -i root -fu -v `ttyadm-V` -m "`ttyadm -b -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 to put the -b option in for bi-directional communications. Also, remember the deviceslive in the /dev/cua directory. redsands# more /etc/remote 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: tip1200:tc=UNIX-1200: tip0|tip2400:tc=UNIX-2400: tip9600:tc=UNIX-9600: tip19200:tc=UNIX-19200: UNIX-1200: :el=^D^U^C^S^Q^O@:du:at=hayes:ie=#$%:oe=^D:br#1200:tc=dialers: 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: PATCH ID: n/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 Questions or comments regarding this service? webmaster 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 Info Docs article 14672 [ Notify of patch changes ] [ Edit/Retrieve Marked Documents ] [ Mark Document ] ---------------------------------------------------------------------------- INFODOC ID: 14672 SYNOPSIS: Solaris 2.4/2.5 Modem configuration DETAIL DESCRIPTION: Solaris 2.4/2.5 Modem configuration and Bi-direction Port Configuration (Version 2.0 9/19/96 Kovacs,Edwards) I. Introduction. The following information provides very basic and minimal modem 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. Here are the basic steps: 1- Delete or disable port monitor services for the port to be used. 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. II. Initial Sun setup. 1. Attach the modem on the Sun system. Use either ttya or ttyb and 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.) Do not use a null modem (cross over) cable or a null modem gender adapter cable. If you are using a system that shares ports a and b, such as the 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: X985A or 530-1869/C9 2. Add the following entries to the file /etc/ttydefs. These are the serial port characteristics presented by the answering side. 38400m:38400 hupcl:38400 hupcl crtscts::38400m 19200m:19200 hupcl:19200 hupcl crtscts::19200m 9600m:9600 hupcl:9600 hupcl crtscts::9600m The above definitions turn on hardware flow control (crtscts). Your 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. 3. Verify that there are no port monitor services on the port that is being configured, by typing the command: pmadm -p zsmon -l PMTAG PMTYPE SVCTAG FLGS ID 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 If the services are present, as indicated in the above output, then remove the services by typing: pmadm -p zsmon -r -s or by using the Admintool and selecting Delete or Disable for the port. The login services need to be removed or disabled before a new ttydefs entry can be used. III. Modem Setup. Modem setup is the responsibility of the customer. This is because 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: and So check the Internet for the latest on your modem. To set the modem registers up correctly, you must be able to access the modem and its port. 1. Make sure the port monitor services are disabled or deleted. The basic tip command is: tip -38400 /dev/cua/a Use appropriate speed depending on modem and serial device. 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. 2. Verify that the modem is responding to commands. After the Connect message type: at You should see an OK displayed. If not try: ate1q0 (Execute tip in a shell tool without scrolling enabled, otherwise a carriage return (cr) is not sent) If you do not get an OK try a different port and/or cable. The modem must respond to AT commands before proceeding to the following steps. 2. Modem register/initialization a. Refer to Appendix B, Common Modem Initialization Strings, 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: 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 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. c. After setting up the modem, exit the "tip" utility by typing the following sequence: ~. The above sequence is a "carriage return" followed by a "~" character and a "." character. 3. Using 'cu' command You need 2 lines in the /etc/uucp/Devices file, for example: Direct cua/a - 9600 direct ACU cua/a - 38400 hayes "hayes" refers to an entry in /etc/uucp/Dialers. The generic hayes entry was written for old 2400 baud modems. Change the generic entry to: 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 (for hardware flow control) or hayes =,-, "" P_ZERO "" \dAT\r\c OK\r \EATDT\T\r\c CONNECT (to insure 8 data bit transfers) Basic cu syntax --------------- #cu -d -s -l /dev/cua/a To connect to the port in order to change modem registers with AT commands, disable the login services when connecting to the port. The speed above overrides the speed specified in the Devices file entry. -d option gives full debug output. #cu -b8 Use for 8 data bits. Otherwise, cu defaults to 7 even parity. 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. #cu -d or Use for creating UUCP chat scripts and seeing keystrokes necessary for successful login. is first entry on line in /etc/uucp/Systems #cu -d -L Use -L for an automated login session. When logging in 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. IV. Starting the Login Process. The following will create a port monitor service to allow login from a modem: 1. Using the Administration Tool program (admintool), add a bidirectional modem service. If you can not use the admintool, refer to appendix A. 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 with the right mouse button, press the "Modify Service" field. This will bring up a new popup menu. d. Press the "Use Template" menu button with the right mouse button and select the "Modem - Bidirectional" menu item. e. Press the "Baud Rate: " menu button and select "Other". f. A new popup window will appear. Enter either 38400m, 19200m, or 9600m according to the desired baud rate of the modem. Then press the "Apply" button. Note- Use the 38400m entry for 28800 baud modems, the 19200m entry for 14400 baud modems, and 9600m entry for 9600 baud modems. g. Enter the type of terminal that is going to be logging into the system, e.g. vt100. h. Verify all fields that data was entered in, then press the "OK" button. i. Quit the Admintool and its windows. 2. Verify that a port monitor was configured by typing the following command: pmadm -p zsmon -l PMTAG PMTYPE SVCTAG FLGS ID zsmon ttymon ttyb u root /dev/term/b b - /usr/bin/login - 9600m ldterm,ttcompat login: - dialup n #Modem - Bidirectional If a port monitor is not listed for that port, go back to setup 3 and 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. V. Modem Guidelines. Sun's policy about support of modems is strictly to give guidelines and not to set up individual modems and modem registers. The guidelines are given below. o Make sure the modem uses data terminal ready (DTR). When the system drops DTR, the modem should hang up. If the DTR signal is not asserted, the modem should not answer. o Use hardware carrier detect (CD). The modem raises the CD 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. o Modems should send result codes only in answer mode. o The modem serial port speed must be at a fixed baud rate. If the modem does not support this feature, do not use it on a Sun/unix system. o Hardware flow control must be used between the Sun system and the modem. Turn off the modem's software flow control if available. How to resolve the error "All ports busy" when accessing a modem port? 1) Disable or Delete the port monitor using admintool for that port. Then try the following using the appropriate device: tip -9600 /dev/cua/a 2) Make sure you are not trying to access a device incorrectly specified in /etc/remote when using the tip command. Use the device /dev/cua/a, for example, and not /dev/term/a. 3) There could be a permissions problem on the device. Change the permissions and owner of the modem port: #chmod 666 /dev/cua/a #chown uucp /dev/cua/a To verify the permission bits and owner use the following options to ls to follow the link to the actual device. #ls -Ll /dev/cua/a Note: If cu is abruptly killed the device will be left with an owner of the last user using cu. 3) Check for a lock file in /var/spool/locks. If there is 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. 4) Another process has the port open. This might be another tip session or another program like lp. It could also be a port monitor. #ps -ef |grep tip Do the following as root: (use appropriate device) #fuser /dev/cua/a /dev/cua/a: 652o 651o #ps -ef | grep 652 #ps -ef | grep 651 The process id's, PID's, are 652 & 651 ( drop the o ) If the process using the port is /usr/bin/login or ttymon, 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. 5) If the process is "ttymon" there are 2 ways to kill the 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) 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 up to multiuser mode. exit Windows init S type control-d 7) The following removes the devices and recreates them without rebooting. (Do not perform a boot -r if a SparcStorage Array exists) a) To determine the physical device name: ls -al /dev/term/a lrwxrwxrwx 1 root root 32 Jul 27 1995 /dev/term/a -> ../../devices/obio/zs@0,100000:a cd /devices/obio ls zs*:a* zs@0,100000:a zs@0,100000:a,cu ls -al zs*:a* 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 There are 2 physical devices for a serial port. Each has a different 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. b) Remove the devices: rm zs*:a* c) Remove the links cd /dev/term rm a cd /dev/cua rm a d) Recreate the devices in /devices and then use ports to recreate the links. /usr/sbin/drvconfig /usr/sbin/ports 8) Sometimes a complete reboot is necessary to achieve 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. A P P E N D I X A The following procedure is provided for users that do not have access to the Openwindows interface and cannot use the Admintool. 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 following command: # sacadm -l PMTAG PMTYPE FLGS RCNT STATUS COMMAND tcp listen - 0 ENABLED /usr/lib/saf/listen tcp # zsmon ttymon - 0 ENABLED /usr/lib/saf/ttymon # 2. If you do not see a zsmon entry under PMTAG, execute the following command: 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 STARTING, this is normal). 3. Check to see if a zsmon port monitor is present by executing the following command: pmadm -p zsmon -l PMTAG PMTYPE SVCTAG FLGS ID zsmon ttymon ttyb u root /dev/term/b b - /usr/bin/login - 9600m ldterm,ttcompat login: - - n #Modem - Bidirectional 4. If a port monitor for zsmon is present, remove it by executing the following command: pmadm -r -p zsmon -s Note - the value is found by using the output of the previous command. In the above example, this value will be "ttyb". 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 of the script to match or installation environment. ---- begin script ------- #!/bin/sh # script to add a port monitor PATH=PATH$:/usr/sbin: export PATH # Below is the ttydefs entry for baudrate usage. Use one of the # following, 38400m, 19200m, or 9600m ttydefs=9600m # Below specifies the port to use. Use either "/dev/term/a" or "/dev/term/b" mport=/dev/term/b # Below specifies the service name. Use either "ttya" or "ttyb" depending # on the port being used. service=ttyb # Note that the single quote characters in the command line below are a # "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. pmadm -a -p zsmon -s $service -i root -fu -v `ttyadm -V` -m "`ttyadm -Sn \ -d $mport -b -m ldterm,ttcompat -l $ttydefs -s /usr/bin/login`" \ -y "Modem - Bidirectional" ------- end script ----------- 6. Change the permissions of the file for execution and execute the script (chmod 755 pm_script). 7. Verify that the port monitor is present: Note - The entry should look like the output below but the baudrate and service tag may be different. # pmadm -p zsmon -l PMTAG PMTYPE SVCTAG FLGS ID zsmon ttymon ttyb u root /dev/term/b b - /usr/bin/login - 9600m ldterm,ttcompat login: - - n #Modem - Bidirectional A P P E N D I X B Common Modem Initialization Strings The following contains modem initialization strings to ititialize modems for use as dialin and dialout on Sun Solaris systems. --------------------------------------------------------------- Hayes Optima/Acura Modems: AT&FN0Q2X0&C1&D2S0=1&W --------------------------------------------------------------- US Robotics Courier Modems: AT&F1&B1&C1&D2X0S0=1&W 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: AT&F1&B1&C1&D2X0S0=1&W --------------------------------------------------------------- Telebit T2500 modems in Conventional mode: AT&FQ2X0N0S0=1S37=0&C1&D2&K3&W1&W2 --------------------------------------------------------------- Telebit T2500 modems in Enhanced mode: AT&FS52=4Q9S131=1S58=2S68=255S95=0S150=2S50=0S51=5 S51=5 (19200 bps) S51=4 (9600 bps) --------------------------------------------------------------- GVC 288 V.34 Modem: AT&F2E0Q1S0=1&C1&D2&W&W1 --------------------------------------------------------------- Black Box Corporation, Modem 144FX: 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 on a Sun Solaris system. Most of all problems are the result of having the modem incorrectly configured. "Garbage from Sun system with remote system logging in" This usually is an indication that the modem speed and the 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. --------------------------------------------- "When I make a call, the remote modem answers, I can hear the modems negotiating, then the modem hangs up CALL FAILED." This is probably down to a setting on one or both modems forcing it to 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. --------------------------------------------- "What does 'permission denied or link down' message fro tip utility mean?" Make sure you have "dv=/dev/cua/a" or "dv=/dev/cua/b" in 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. --------------------------------------------- "Modems do not disconnect properly or a user stays logged in even after disconnecting." The modem is not configured correctly. The modem must be configured so that the Data Carrier Detect is asserted only when a carrier is detected from the remote modem. Refer to the modem documentation. --------------------------------------------- "Nothing happens when trying to tip to the modem" Check cabling to the modem. Check if the proper port is being used. Also, make certain that "tip" is being used in a shell tool NOT a command tool. "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 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. --------------------------------------------- "Parity problems" I get a login but its corrupted, (Logn: or Logi ) if I press nothing happens but it does if I press or "control-J". Re-configure the remote computers serial port setup for 8 data bits, 1 stop bit, and no parity. --------------------------------------------- "I can't login, password fails." This is a parity problem - The originating terminal / tip session is using a parity that is different from that used by the ttymon. --------------------------------------------- "When do you modify the eeprom settings?" Don't change the eeproms unless you are trying to get a terminal working at boot prom level. --------------------------------------------- "No login prompt" Check to see if a ttymon process is started, type the command below: ps -ef | grep ttymon 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 pid of 208 is the parent ttymon process and the pid of 17258 is the child process for term/b. Call into the system and see if the ttymon process TTY has changed from "?" to "term/b". See below: ps -ef | grep ttymon 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 If this does not occur, check to see of the serial port has been configured properly and the port monitor service is present by typing: pmadm -p zsmon -l 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 Also check and verify that the port monitor service baudrate matches the modem baudrate. Use the tip utility and connect back into the modem. 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 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. For ttya port: hardwire: :dv=/dev/term/b:br#9600:el=^C^S^Q^U^D:ie=%$:oe=^D: modem1:\ <--- add this and next line :dv=/dev/cua/a:br#9600: after above entry ^ |_ appropriate baudrate* must match the login speed For ttyb port: hardwire:\ :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 * When using a 28.8k modem, use 38400; for a 14.4 modem, use 19200; and for a 9600 modem use 9600. 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 permission of the port(s), start up a shell tool (if using openwindows) and issue the following command: tip modem1 You should get a "connected" message. If you get anything else, for example, "all ports busy", check the "/etc/remote" device entry. PRODUCT AREA: Gen. Network 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 Questions or comments regarding this service? webmaster Copyright 1994-1997 Sun Microsystems, Inc., 901 San Antonio Road, Palo Alto, CA 94303 USA. All rights reserved.

This archive was generated by hypermail 2.1.2 : Fri Sep 28 2001 - 23:12:44 CDT