### Configuring Modems

Use this topic for information on configuring modems on Digi EtherLite and SCSI Terminal Server ports. This topic discusses the following:

- Information on the tools used to configure port monitors
- Information on setup preparation
- An example of ports configured for modems

#### About the Port Configuration Tools on Solaris Systems

Use the sacadm and pmadm tools to configure port monitors on Solaris systems.

#### Setup Preparation

Keep the following information in mind when setting up terminal connections on SCSI and EtherLite ports:

- Make sure to define a dial-in (/dev/sts/ttyc) type node for logins and a dial-out (/dev/sts/ttyc) node for dial-out devices, such as tip and cu.
- Make sure to use a straight-through, one-to-one cable.
- If you want to dial out on a modem between user logins, use the bi-directional flag (-b) in your ttymon setup.

#### Example

This is two examples in one. It provides information on configuring both SCSI Terminal Server and EtherLite ports for the following:

- Two 38400 baud modem logins using hardware flow control on ports 5 and 6
- Two 2400 baud modem logins using software flow control on ports 7 and 8

Here is how the example is organized:

- The first row of the table below provides an example of SAC creation that works for both SCSI Terminal Server and EtherLite ports.
- The second row is for SCSI Terminal Server ports only.
- The third row is for EtherLite Terminal Server ports only.

The only difference between the two configurations is the method of identifying nodes. For more information see Device Names.

Example | Notes
`fas384:38400 hupcl crtscts -ixon -ixoff:38400 hupcl crtscts -ixon -ixoff::fas384` | This command, which works for both SCSI Terminal Server and EtherLite ports, does the following: Adds a hardware flow control entry for the 38400 modems in the /etc/ttydefs file. It is required because there is no default hardware flow control entry. Sets the baud rate at 38400. The defaults for character size (8 bits) and parity (no parity) are used. The /etc/ttydefs file already has an appropriate default entry for the 2400 baud modem, called 2400. You can add this command by directly editing the file or with the sttydefs command. See the sttydefs man page for more information.
`pmadm -a -p ttymon5 -s ttyc54 -i root -fu -v 1 -m "`ttyadm \ -S n -d /dev/sts/ttyc54 -l fas384 -b -s /usr/bin/login`"` `pmadm -a -p ttymon5 -s ttyc55 -i root -fu -v 1 -m "`ttyadm \ -S n -d /dev/sts/ttyc55 -l fas384 -b -s /usr/bin/login`"` `pmadm -a -p ttymon5 -s ttyc56 -i root -fu -v 1 -m "`ttyadm \ -S n -d /dev/sts/ttyc56 -l 2400 -b -s /usr/bin/login`"` `pmadm -a -p ttymon5 -s ttyc57 -i root -fu -v 1 -m "`ttyadm \ -S n -d /dev/sts/ttyc57 -l 2400 -b -s /usr/bin/login`"` | These four commands, which work for SCSI Terminal Server ports, do the following: Start the port monitors that will run under the SAC on ports 5 through 8. Specify the use SCSI ID 5, which is the default.
`pmadm -a -p ttymon5 -s ttyn04 -i root -fu -v 1 -m "`ttyadm -S n -d /dev/sts/ttyn04 -l fas384 -b -s /usr/bin/login`"` `pmadm -a -p ttymon5 -s ttyn05 -i root -fu -v 1 -m "`ttyadm -S n -d /dev/sts/ttyn05 -l fas384 -b -s /usr/bin/login`"` `pmadm -a -p ttymon5 -s ttyn06 -i root -fu -v 1 -m "`ttyadm -S n -d /dev/sts/ttyn06 -l 2400 -b -s /usr/bin/login`"` `pmadm -a -p ttymon5 -s ttyn07 -i root -fu -v 1 -m "`ttyadm -S n -d /dev/sts/ttyn07 -l 2400 -b -s /usr/bin/login`"` | These four commands, which work for EtherLite Terminal Server ports, do the following: Start the port monitors that will run under the SAC on ports 5 through 8. Specify the ports 5 through 8 on the first EtherLite unit.