RealPort Setup: HP-UXdocs/external/realport/rp-hpux.pdfThe HP-UX RealPort driver supports versions 10.10 or later of the operating system. It will not work with earlier versions. Once

RealPort Setup: HP-UX

Introduction

Introduction to RealPort●

Planning and Preparation

Requirements and Considerations●

Information to Gather●

Configuring a PortServer for RealPort●

PortServer Cable Guide●

Setup

Master Setup Process●

Driver Installation - CD●

Driver Installation - Downloaded●

Creating Diskettes●

Adding a PortServer with drpadmin●

Deleting a PortServer with drpadmin●

Uninstalling RealPort●

RealPort Devices●

Setting TTY Options●

Configuring a Device for a Terminal●

Configuring a Device for a Printer●

Configuring a Device for a Modem●

About Transparent Printing●

Transparent Printer Configuration●

Setup Examples for Transparent Printing●

Troubleshooting

Symptoms●

Diagnostics and Resolutions●

Copyright © 2000, Digi International. All rights reserved.

An Introduction to RealPort

RealPort software can be installed on one or more host servers to provide local serial port functionality.RealPort can be used to provide standard system COM, AIO or TTY interfaces to control baud rate, parity, stopbits, and flow control of local serial ports. Any system utility or user application that works with a locallyattached serial port should work with a Digi PortServer port.

Digi's RealPort software works with both the PortServer and PortServer II products. In RealPort documentation,the term PortServer refers to either the PortServer or PortServer II.

Requirements and Considerations

Read this section before beginning the RealPort driver installation.

The HP-UX RealPort driver supports versions 10.10 or later of the operating system. It will not workwith earlier versions.

●

Once the RealPort driver is installed, HP-UX manual pages are available for:

Item Functionditty Sets and displays RealPort device TTY optionsdrpadmin The Digi RealPort configuration utilitydrpd The Digi RealPort network daemondrp The Digi RealPort driver

●

Information to Gather

Before you install RealPort, you need to determine:

The hostname or IP address to assign each unconfigured PortServer.●

The number of ports each PortServer has. Include any Xem PORTS Module ports that are attached toPortServer II units.

●

Determine the link speed between the host machine and the PortServer devices if a slow WAN link (forexample, a 56K leased line) connects them.

●

Configuring a PortServer for RealPort

Use this procedure to configure a PortServer to use RealPort.

Access a root prompt on the PortServer using one of the two following methods:

Method 1 - Unconfigured PortServer:

Use these steps to access a root prompt on an unconfigured PortServer.

Attach a terminal to port 1 of the PortServer and configure the terminal for VT-100 emulation,9600 baud, 8 data bits, 1 stop bit, and no parity.

1.

Turn on the PortServer and press Return or Enter.2.

At the login prompt, enter:

root

3.

At the passwd prompt, enter:

dbps

4.

Note: dbps is the default PortServer root password. Enter your specific PortServer root password if it isdifferent.

Method 2 - Previously-Configured PortServer:

Use this method to access a root prompt on a previously-configured PortServer.

Login to the PortServer as root directly from an attached terminal or by using telnet.

Note: If a port is configured to bypass the PortServer login, you cannot directly log into the PortServerfrom that port. Use another port that does not bypass the PortServer login or use telnet to login to thePortServer.

1.

Set the PortServer's IP address with this command:

set config ip=[ipaddress]

where [ipaddress] is the IP address the PortServer will use.

2.

Set any other relevant PortServer set config parameters such as name server, gateway, etc. See thePortServer II Configuration and Administration Guide or the PortServer User's Guide and ReferenceManual for details on initial PortServer configuration.

3.

Check the RealPort TCP port value with this command:

set config realport

The default value is 771. If it is some other number, change it to 771 with this command:

set config realport=771

4.

Configure the PortServer ports using RealPort to prn by using the set ports command. The followingexample configures ports 2 through 16 of a PortServer for RealPort:

set ports range=2-16 dev=prn

5.

If 8-pin RJ-45 cables are used on the PortServer, the altpin option should be enabled. The followingexample enables altpin on ports 2 through 16 of a PortServer:

set flow range=2-16 altpin=on

6.

Make sure that all other set flow options are "off". Enter this command to view all the set flow options:

set flow range=2-16

Use your own range of ports in the previous command. If other set flow options are "on", use a set flowcommand to change them to "off".

7.

Verify the PortServer configuration with these commands:

set config

set ports range=2-16

set flow range=2-16

8.

Master Setup Process

These are the steps necessary for the installation and configuration of RealPort.

Read any release notes that may be included with the installation media.1.

Gather information necessary for installation. See Information to Gather.2.

Configure the PortServer for RealPort. See Configuring a PortServer for RealPort.3.

Install the RealPort driver. See Driver Installation - CD or Driver Installation -Downloaded.4.

Follow the procedure Adding a PortServer with drpadmin.5.

Configure the TTY Devices as necessary. 6.

Installing the Driver: CD

Use this procedure to install a Digi driver from the Digi CD front end menu.

Note: This procedure assumes that you have accessed the Digi RealPort CD and that the front end menuappears on your screen. See the Digi RealPort CD Access Resource document for information on properlyaccessing the front end menu.

Procedure

Select an operating system.1.

Choose Install Drivers.2.

Follow the prompts.3.

Installing a Driver from a Download

This procedure describes how to install the HP-UX RealPort device driver after downloading it.

Note: This is an example of an installation of RealPort on HP-UX. Your installation steps may vary dependingon your version of HP-UX. Consult your HP-UX documentation for information on installing drivers.

Procedure

Log onto the console as root.1.

Copy the driver file to /tmp either from a diskette, or by using ftp.2.

Extract the files from the compressed tar file with this command:

tar xvf filename.tar

where filename.tar is the name of the downloaded tar file.

3.

Now register the installation package with the system by entering the following command:

swreg -l depot /tmp/drp.pkg

4.

Once the component files have been copied, use the swinstall program to copy the component files tothe system.

/usr/sbin/swinstall -s /tmp/drp.pkg

5.

Choose the DRP line item.6.

Choose Actions > Mark for Install.7.

Choose Actions > Install (analysis)...

The Install Analysis window appears.

8.

Choose [OK] to proceed.9.

Confirm the prompts that follow.

Upon successful completion, swinstall will reboot your system.

10.

Continue with the procedure Adding a PortServer with drpadmin.11.

Creating Diskettes: CD

Use this procedure to create driver installation diskettes from the CD menu program.

Procedure

Access the Digi CD program. See the Access Resource card for operating system-specific information.1.

From the CD menu program, choose an operating system and Create Diskettes.2.

Follow the prompts to complete the procedure.3.

Adding a PortServer with drpadmin

Use this procedure to create RealPort devices and start the RealPort daemons.

Procedure

Enter this command at a root prompt:

/usr/sbin/drpadmin

1.

Answer the prompts as appropriate.

When Prompted to: Action:

Select an option Choose add.

Enter the node name or IP address forthis PortServer

If an IP address is used, make sure it is unique and doesnot conflict with any other network device.

If a name is entered, the name must be registered in/etc/hosts or with an accessible nameserver.

Enter the number of ports on thePortServer

Enter the number of ports for this PortServer. Theinstallation will prompt to confirm this number.

Note: If PORTS/Xem (EBI) modules will be attached to aPortServer II module, include these ports.

Enter TTY device ID letter(s) Enter one or two letters. These letters will be used tocreate the RealPort device names.

Enter WAN speed if the connectionbetween the PortServer and HP-UXsystem includes a WAN link slowerthan 1 MB

Enter the WAN speed if this is the case. Otherwise,choose Enter to continue.

Confirm the configuration Enter y to proceed or n to reenter the information.

Select an option Enter a to add another PortServer. Enter s to showconfigured PortServer(s). Enter q to exit drpadmin.

2.

Deleting a PortServer with drpadmin

Use this procedure to delete a PortServer from HP-UX.

Procedure

Enter this command at a root prompt:

/usr/sbin/drpadmin

1.

Enter s to show all installed PortServers.2.

Note the number of the PortServer to delete.3.

Choose Enter to make the options prompt reappear.4.

Enter d (delete).5.

Enter the PortServer number to delete.6.

Enter y to confirm the deletion.7.

Uninstalling RealPort

Use this procedure to remove a PortServer from HP-UX.

Procedure

Delete any configured PortServers on the HP-UX system. See Deleting a PortServer.1.

Enter this command at a Unix root prompt:

swremove

The SD - Remove Software Selection window appears.

2.

Choose DRP (Digi HP-UX RealPort Driver).3.

Choose Actions > Remove (Analysis)...4.

Choose OK to continue at the Remove Analysis window.5.

Choose Yes at the Confirmation windows that appear.6.

Choose Done at the Remove window.7.

Confirm the prompt to reboot the system when it appears. If it does not appear, the system should berebooted manually.

8.

RealPort Devices

The RealPort installation creates three different devices for each port in the /dev directory.

Standard device●

Modem device●

Transparent print device●

Device Name Format

The devices are named according to the following conventions:

aa-zz The PortServer letter ID.01-64 The port number on the individual PortServer.

Following are examples of the devices for the first port of a PortServer with the identification letters "aa":

Device Path Name ExampleStandard Device /dev/cuaa01

Modem Device /dev/ttyaa01

Standard Transparent Print Device /dev/praa01

Standard Device

Example: /dev/cuaa01

A standard PortServer device begins with the prefix "cua". The default handshake method is XON/XOFF. Data CarrierDetect (DCD) need not be present to open the device.

Once a connection is established and DCD becomes active, standard devices behave in the same way as modemdevices. Subsequent loss of the Data Carrier Detect signal will cause active processes on the port to be killed and theuser will be automatically logged off.

Modem Device

Example: /dev/ttyaa01

PortServer modem devices begin with the prefix "tty". They are sometimes referred to as "dial-in" devices.

Modem devices are traditional UNIX ports with modem control. They require Data Carrier Detect to be high beforethey will operate. RTS/CTS handshaking is enabled by default. When used with a modem, the ports will wait for DCDbefore sending out the login prompt

When used with a terminal or other device, it is usually wise to wire the Digi DCD signal to the terminal's DataTerminal Ready (DTR) line. When the terminal is turned on, the system outputs a login prompt. When the terminal isturned off, any associated jobs are killed, and the user is logged out.

Transparent Print Device

Example: /dev/praa01

The transparent print device can be used with auxiliary printer ports on terminals. Output directed to a "pr" devicegoes out the auxiliary port of a terminal while you continue to use the terminal normally.

Setting TTY Options

AccelePort and RealPort UNIX device driver packages include a command, ditty, which is a superset of stty,and may be used to set and display the device options for Digi AccelePort devices.

The general command format is:

ditty [-a] [-n ttyname] [option(s)] [ttyname]

In AIX, substitute the command, stty-digi, for ditty:

/usr/Lbin/tty/stty-digi [-a] [-n ttyname] [option(s)] [ttyname]

When using RealPort for Linux, substitute the command, ditty-rp, for ditty:

ditty-rp [-a] [-n ttyname] [option(s)] [ttyname]

With no options, ditty displays all Digi special driver settings, modem signals, and all standard parametersdisplayed by stty(1) for the TTY device referenced by standard input.

Command options are provided to change flow control settings, set transparent print options, force modemcontrol lines, and display all TTY settings. Any unrecognized options are passed to stty(1) for interpretation.

ditty commands may be executed from the command line, or placed in a startup script to be run whenever thesystem is booted.

The options are:

-a Display all of the unique Digi option settings, as well as all of the standard TTYsettings reported by stty -a.

-n ttyname Set and display options for the given TTY device, instead of standard input. This optionmay be specified multiple times to perform the same operation on multiple TTYs.

ttyname Set and display options for the specified TTY device. Replace ttyname with the TTYpathname (such as /dev/ttya01s, /dev/term/a01 or /dev/dty/a001s, depending on youroperating system). This option may be used on a modem control line when no carrier ispresent.

The following options specify transient actions to be performed immediately:

break Send a 250 MS break signal out on the TTY line.

clear Clear the tbusy flag in the channel structure to free the port.

NOTE: This option is supported only in UnixWare, OpenServer and Solaris operatingsystems.

cspeed n Set the port speed to n bps, where n is an integer value. Available only on Xr, Xem andXp adapters.

NOTE: This option is supported only in UnixWare, OpenServer and Solaris operatingsystems.

flush Immediately flush (discard) TTY input and output.

flushin Flush TTY input only.

flushout Flush TTY output only.

The following options specify actions which are not sticky, meaning that the changes are cancelled when thedevice is closed, and that the device will use the default values the next time it is opened.

stopout Stop output exactly as if an XOFF character were received.

startout Restart stopped output exactly as if an XON character were received.

stopin Activate flow control to stop input.

startin Release flow control to resume stopped input.

[-]dtr Raise [drop] the DTR modem control line, unless DTR hardware flow control isselected.

[-]rts Raise [drop] the RTS modem control line, unless RTS hardware flow control isselected.

The following options are sticky—the effects continue until the system is rebooted or until the options arechanged.

[-]printer Forces the port to stay open so that non-sticky parameters such as baud rate and flowcontrol are not reset to default values.

NOTES:

This option is supported only in UnixWare, OpenServer and Solaris operatingsystems.

●

This option is not supported by RealPort.●

[-]fastcook Perform cooked output processing on the adapter itself to minimize use of hostresources.

NOTES:

This option is supported only in OpenServer and AIX operating systems.●


[-]fastbaud Alter the baud rate tables to permit the use of data rates that are beyond the rangesupported by the operating system. See fastbaud Data Rate Mapping, at the end of thispage.

[-]rtspace Enable [disable] RTS hardware input flow control, so RTS drops to pause remotetransmission.

[-]ctspace Enable [disable] CTS hardware output flow control, so local transmission pauses whenCTS drops.

[-]dsrpace Enable [disable] DSR hardware output flow control, so local transmission pauses whenDSR drops.

[-]dcdpace Enable [disable] DCD hardware output flow control, so local transmission pauses whenDCD drops.

[-]dtrpace Enable [disable] DTR hardware input flow control, so DTR drops to pause remotetransmission.

[-]forcedcd Disable [re-enable] carrier sense, so the TTY may be opened and used even whencarrier is not present.

edelay n edelay is a tunable parameter used to set the number of milliseconds of delay betweenthe time the first character arrives after a period of no characters and notification of itsarrival to the host. This is also referred to as the wakeup rate between the host adaptersoftware (FEP/OS) and the host device driver. This has the advantage of reducing hostoverhead by allowing the host to process larger blocks of incoming data.

Larger edelay values result in more characters being sent in a given time period. Thiswill reduce host processor overhead and increase overall system throughput.

Smaller edelay values result in fewer characters being sent in a given time period. Thiswill increase character response time and increase host processor overhead.

The default value for edelay is 100. This is a good value for normal TTY activity liketyping. For some applications like uucp, decreasing the edelay value may increasecharacter throughput, but will result in increased host (system) overhead. Forapplications receiving continuous input at high speeds, increasing edelay will result inlowering host overhead and increasing overall system throughput. A value of 250 isreasonable.

NOTES:

This option is supported only in UnixWare, OpenServer and AIX operatingsystems.

●


startc c Sets the XON flow control character. The character may be given as a decimal, octal orhexadecimal number. Octal numbers are recognized by the presence of a leading zero,and hexadecimal numbers are denoted by a leading "0x". For example, the standardXON character, <CTRL-Q>, can be entered as "17" (decimal), "021" (octal) or "0x11"(hexadecimal).

stopc c Sets the XOFF flow control character. The character may be given as a decimal, octal,or hexadecimal number (see startc, above, for format of octal and hexadecimalnumbers).

astartc c Sets auxiliary XON flow control character. The character may be given as a decimal,octal, or hexadecimal number (see startc, above, for format of octal and hexadecimalnumbers).

Note: This option is not supported in Solaris.

astopc c Sets auxiliary XOFF flow control character. The character may be given as a decimal,octal, or hexadecimal number (see startc, above, for format of octal and hexadecimalnumbers).

Note: This option is not supported in Solaris.

[-]aixon Enables auxiliary flow control, so that two unique characters are used for XON andXOFF. If both XOFF characters are received, transmission will not resume until bothXON characters are received.

maxcps n Sets the maximum Characters Per Second (CPS) rate at which characters are output tothe transparent print device. The rate chosen should be just below the average printspeed. If the number is too low, printer speed will be reduced. If the number is too high,the printer will resort to flow control, and user entry on the terminal will becorrespondingly impaired. Default is 100 CPS.

maxchar n Sets the maximum number of transparent print characters the driver will place in theoutput queue. Reducing this number increases system overhead; increasing this numberdelays operator keystroke echo times when the transparent printer is in use. Default is50 characters.

bufsize n Sets the driver’s estimate of the size of the transparent printer’s input buffer. After aperiod of inactivity, the driver bursts this many characters to the transparent printerbefore reducing to the maxcps rate selected above. Default is 100 characters.

onstr "s" Defines the terminal escape sequence to direct subsequent data to the transparentprinter.

s is a string of ASCII characters, enclosed in quotes, that command the terminal to entertransparent printing mode. An arbitrary octal character xxx may be given as \xxx.

For example, the sequence <Esc>[5i would be entered as: "\033[5i".

offstr "s" Defines the terminal escape sequence to stop directing data to the printer.

s is a string of ASCII characters, enclosed in quotes, that command the terminal to entertransparent printing mode. An arbitrary octal character xxx may be given as \xxx.

For example, the sequence <Esc>[5i would be entered as: "\033[5i".

term t Sets the transparent printer on/off strings to values found in the internal default table.Internal defaults are used for the following terminals: adm31, ansi, dg200, dg210,hz1500, mc5, microterm, multiterm, pcterm, tvi, vp-a2, vp-60, vt52, vt100, vt220,wyse30, wyse50, wyse60, or wyse75. If the terminal type is not found in the internaldefault table, then ditty reads the terminfo entry for the terminal type and setstransparent print on/off strings to values given by the mc5/mc4 attributes found there.

fastbaud Data Rate Mapping

Use the table below to see how setting fastbaud affects data rates for standard AccelePort and RealPortproducts. Select one of the links to view a table of fastbaud data rates for:

AccelePort fastbaud Data Rates ●

RealPort fastbaud Data Rates●

AccelePort fastbaud Data Rates

Xp Xe Xr, Xem,EPC/X Xr 920 C/X

Specified DataRate:

Data RateMapped to:

Data RateMapped to:

Data RateMapped to:

Data RateMapped to:

Data RateMapped to:

50 57600 57600 57600 57600 57600

75 76800 76800 76800 76800 75

110 115200 115200 115200 115200 115200

134 131657 14400 14400 14400 14400

150 153600 28800 57600 57600 57600

200 230400 200 230400 230400 200

300 460800 300 76800 76800 300

600 921600 600 115200 115200 115200

1200 1200 1200 230400 230400 1200

1800 1800 1800 28800 28800 28800

2400 2400 2400 2400 460800 2400

4800 4800 4800 4800 921600 4800

9600 9600 9600 9600 9600 9600

19200 19200 19200 19200 19200 19200

38400 38400 38400 38400 38400 38400

RealPort fastbaud Data Rates

The table below contains the fastbaud data rates available for RealPort. All other fastbaud data rates forRealPort are unmapped.

Specified Data Rate:Data

Rate Mapped to:

50 57600

75 76800

110 115200

Configuring a Device for a Terminal

Use this procedure to configure a RealPort device for a terminal. See your operating system documentation formore information on configuring a serial device for a terminal.

Procedure

In HP-UX, TTY devices require the carrier detect high. This must either be tied high within the cable orit can be forced high in the driver by entering a ditty command, like the following example, for the portin a startup file:

ditty forcedcd ttya12

1.

Connect a proper cable between the port and terminal. See the PortServer Cable Guide.2.

Set the port to dev=rp on the PortServer by entering this command at a PortServer root prompt:

set port dev=rp ra=12

This example sets PortServer port 12 to be a RealPort device.

Note: If your PortServer firmware does not support the dev=rp option, use dev=prn instead.

3.

If you are using 8-pin RJ-45 cabling from the PortServer to the terminal, set the port to altpin=on byentering this command at a PortServer root prompt:

set port altpin=on ra=12

This example sets altpin=on for port 12 of a PortServer.

4.

Enable the port by editing the /etc/inittab file. Locate the proper RealPort device to enable and changethe word off to respawn. This line shows an example of a inittab entry for the first port of a PortServerwith a designation letter of "a".

Xx01:23:off:/etc/getty ttya12 H

5.

Change the letter or number at the end of the entry as needed. The last number or letter (H in theprevious example) is an entry in the /etc/gettydefs file. This sets the speed, data bits, stop bit(s) andparity for the port. Consult your operating system documentation for more information on /etc/gettydefs.

6.

Enter the following command at a root prompt:

init q

7.

Configuring a Device for a Printer

Use this procedure to configure a RealPort device for a printer. See your operating system documentation formore information on configuring a serial device for a printer.

Procedure

In HP-UX, TTY devices require Data Carrier Detect to be high. This must either be tied high within thecable, or it can be forced high in the driver by entering this ditty command for the port in a startup file:

ditty forcedcd ttya12

The device, ttya01, is used as an example in this command.

1.

Connect a proper cable between the port and printer. See the PortServer Cable Guide.2.





3.

If you are using 8-pin RJ-45 cabling from the PortServer to the terminal, set the port to altpin=on byentering this command at a PortServer root prompt:

set port altpin=on ra=12

This example sets altpin=on for port 12 of a PortServer.

4.

Configuring a Device for a Modem

Use this procedure to configure a RealPort device for a Dial-in/Dial-out modem connection. Configuring adevice for a modem requires familiarity with both the operating system and the modem being used. While thefollowing procedure is sufficient for most cases, it may be necessary to take additional steps to properlyconfigure your modem or to set up the operating system for a specific application.

Procedure

Connect a proper cable between the port and modem. See the PortServer Cable Guide.1.

Log into the PortServer as root and enter this command:

set port ra=## dev=prn

where ## is the port (number) to which the modem is attached.

2.





3.

On the HP-UX server, use vi to enable the new modem entries in the /etc/inittab file for dial-in. Here areexamples of two entries for Digi RealPort ports:

Xx01:23:off:/etc/getty ttya12 HXx02:23:off:/etc/getty ttyb02 H

4.

Change the word off to respawn for each port you want enabled. For example:

Xx01:23:respawn:/etc/getty ttya12 HXx02:23:respawn:/etc/getty ttyb02 H

Note: The numbers associated with each "tty" represent port number (ttya01 is Port 1, ttya08 is Port 8).

5.

The last number or letter (H in the previous example) is an index into the /etc/gettydefs file, which maybe set to any of the allowable baud rates (check your operating system's manual.). In this case, Hspecifies 9600 baud, 8 data bits, 1 stop bit, and no parity.

6.

Enter this command at a root prompt: init q7.

Modify the file /usr/lib/uucp/Devices. Add an entry for the device at the end of the file like this:

Direct cua12 - 38400 direct

8.

Comment out any ACU lines relating to this device until dialin is working properly.

Note: An ACU line is necessary for correct operation of the modem in dialout applications. Refer toyour modem manual or to the modem manufacturer for the correct initialization string to use for yourmodem. Refer to your operating system documentation for guidance on setting up an appropriate ACUentry that uses this initialization string.

9.

Connect to the modem by entering this command at a root prompt:10.

cu -l /dev/cua12 -s 38400at&w [train modem to port speed]

Note: In HP-UX, the TTY device name is for dial-in, the cu name is for dial-out.

To exit cu, enter:11.

~. (a tilde followed by a period)

About Transparent Printing

Most terminals have an auxiliary port that can be connected to a serial printer. When this port is configured as atransparent printer port, print jobs may be run simultaneously with normal terminal operation.

Data bound for the printer is preceded by a terminal escape sequence which turns on transparent printing, andfollowed by a sequence which turns transparent printing off.

Transparent printer devices are accessed in the same manner as a printer on a regular serial port. Data sent to atransparent printer device is automatically "wrapped" in the transparent print on/off command strings for thespecified printer.

Configuring Transparent Printers

Use this procedure to configure transparent printers on terminals.

Procedure

At the command prompt, enter:

ditty -n ttyname [options]

where ttyname is the name of the terminal device and options are selected from the list below.

maxcps n Limits the maximum printer port character-per-second data rate. n should be set tothe minimum character rate the printer can sustain in typical use.

maxchar n Limits the number of characters queued to the printer ahead of terminal output.Lower numbers increase system overhead, higher numbers result in keystrokeecho delays. A value of 50 is generally a good compromise at 9600 baud.

bufsize n This parameter should be set to a value just below the printer's buffer size. After aperiod of inactivity, the driver will burst up to this many characters to the printerto fill the print buffer before slowing to the maxcps rate.

onstr "s" Defines the terminal escape sequence to direct subsequent data to the transparentprinter.

s is a string of ASCII characters, enclosed in quotes, that command the terminal toenter transparent printing mode. An arbitrary octal character xxx may be given as\xxx.

For example, the sequence "<Esc>[5i" would be entered as:"\033[5i".

offstr "s" Defines the terminal escape sequence to stop directing data to the printer.

s is a string of ASCII characters, enclosed in quotes, that command the terminal toenter transparent printing mode. An arbitrary octal character xxx may be given as\xxx.

For example, the sequence "<Esc>[4i" would be entered as:"\033[4i".

term t Sets the transparent printer on/off strings to values found in the internal defaulttable. Internal defaults are used for the following terminal types: adm31, ansi,dg200, dg210, hz1500, mc5, vt100, vt220, vt320, vt420, wang2x36, wyse30,wyse50, wyse60 or wyse75.

If the terminal type is not found in the internal default table, then ditty reads theterminfo entry for the terminal type and sets the transparent print on/off strings tothe values given by the mc5/mc4 attributes found there.

Setup Examples for Transparent Printing

Use the ditty program to set up your terminal for transparent printing.

Example 1:

The following command configures the transparent print options for a DEC VT100 terminal connected to/dev/ttyaa01 (note that the printer will be called /dev/praa01). maxcps, maxchar and bufsize are left to defaults.Enter:

ditty term vt100 /dev/ttyaa01

Example 2:

The following example uses onstr and offstr arguments (this sets the terminal to use ANSI Standard). Againmaxcps, maxchar, and bufsize are defaults. Enter (on a single command line):

ditty onstr \033[5i offstr \033[4i /dev/ttyaa01

Example 3:

This example command sets the transparent print option for a WYSE30 terminal, with maxcps of 75, a maxcharof 100, and a printer buffer size, bufsize, of 1000. Enter (on a single command line):

ditty term wyse30 maxcps 75 maxchar 100 bufsize 1000 /dev/ttyaa01

Symptoms: HP-UX

Use this recommended troubleshooting procedure if you have any problem with RealPort. This procedure takesyou from one of the two main symptoms to a Master Troubleshooting Process. From the MasterTroubleshooting Process, you might be directed to use some of the troubleshooting tools, which are shortprocedures. If you have already been through this procedure already or are knowledgeable enough to take ashortcut without needing to go through the Master Troubleshooting Process, go to Diagnostics and Resolutions:HP-UX.

Before you begin this procedure, keep in mind the following:

Some of this troubleshooting involves the PortServer, the operating system you are working with, andother hardware and software.

●

At some point in this procedure, you might need to call Digi Technical Support. You should record howfar you have progressed through the procedure with what results to help describe your problem.

●

At the beginning of this process and before you call Digi Technical Support, reboot your devices andcheck your cables. You might need to refer to the PortServer Cable Guide.

●

Identify a symptom and a starting point. You will be directed to the first step in a Master TroubleshootingProcess. Choose which of these two general symptoms most closely resembles your symptom.

All devices do not function One or several devices function incorrectly or notat all

Go to Master Troubleshooting Process: HP-UX (AllDevices Fail).

Go to Master Troubleshooting Process: HP-UX(Some Devices Fail).

Diagnostics and Resolutions: HP-UX

Use this information if you are knowledgeable enough to take a shortcut when you have any problem withRealPort. Use this information also when you are talking with Digi Technical Support and they ask you to do aprocedure.

Note: If this is the first time you are going through the troubleshooting process, it is recommended you gothrough the Main Troubleshooting Process. To get to this process, go to Symptoms: HP-UX.

Before you begin any of the procedures, keep in mind the following:

Some of this troubleshooting involves the PortServer, the operating system you are working with andother hardware and software.

●

At some point in this procedure, you might need to call Digi Technical Support. Writing down what youhave done with what results would be helpful in describing what your problem is.

●

At the beginning of this process and before you call Digi Technical Support, reboot your devices andcheck your cables. You might need to refer to the PortServer Cable Guide.

●

Following are possible procedures you might need to perform:

Running PortServer Diagnostics●

Running PortServer II Diagnostics●

Troubleshooting TFTP●

Resetting PortServer●

Testing the Port Connections●

Performing a Telnet●

Disconnecting Telnet●

Telnet: Receiving a Login Prompt●

Telnet: Receiving No Login Prompt●

Checking LED Indicators: OFC On?●

Testing the Terminal Connection●

Testing the Terminal Connection: No Data ●

Testing the Terminal Connection: Scrambled Data●

Master Troubleshooting Process: HP-UX (All Devices Fail)

Use this Master Troubleshooting Process if none of the devices are functioning.

In many of the steps, you will be sent to another shorter procedure that you need to complete. Once you havecompleted the procedure, you most often will be sent back to the Master Troubleshooting Process to continuewith where you left off. Otherwise, you might be directed to call Digi Technical Support.

Process

Step 1. Check the status of the PortServer. Is AC displayed on the PortServer?

Continue with the next step. Do the following steps:

Reboot the Port Server. 1.

If AC now is displayed, go toStep 2 to verify your networkconnection.

Go to Running PortServer Diagnosticsor Running PortServer II Diagnostics.

2.

If the PortServer is TFTP-bootingfirmware, go to Troubleshooting TFTP.

3.

If the PortServer is booting frominternal firmware, continue withthe next step.

Note: TFTP booting may bebypassed by simultaneouslypressing and releasing the twoarrows on the front of thePortServer during a TFTP boot.

Go to Resetting PortServer.4.

Step 2. To verify the network connection, telnet to the PortServer.

From the UNIX RealPort host root prompt, enter:

telnet ipaddress

where ipaddress is the IP address of the PortServer.

Did you receive a PortServer login prompt?

Go to Telnet: Receiving a Login Prompt.

You might have a network, cable or hubproblem. You need to check this. Go to Telnet:Receiving No Login Prompt.

Step 3. Test the port connection from the operating system. Go to Testing the Port Connection.

Do the DTR and RTS indicator lights on the PortServer flash briefly and do you get data resultsand port status information on your terminal screen?

Your connection was successful. Your deviceshould work.

If the device doesn't work, call Digi TechnicalSupport.

Make note of the results and continue to thenext step.

Step 4. Check the LED indicators on the PortServer. Is OFC on?

Go to Checking the LED Indicators: OFC On? If OFC is not on, continue to the next step.

Step 5. Telnet directly to the port. Go to Performing a Telnet to the Port.

When you entered the command on the keyboard, did the word, "Connected," appear on thescreen?

Also, anything you entered should appear onthe attached terminal and anything entered onthe dumb terminal should appear on your telnetscreen. This verifies that the port is functional,along with the attached cable and terminalwhile bypassing RealPort.

Disconnect from the telnet session. Go toDisconnecting Telnet.

If the host cannot telnet to the port, thenRealPort won't connect to it.

Check the previous set commands on thePortServer and try the command again.

If you still do not get any results, call DigiTechnical Support.

Step 6. Test the connections from each terminal. Go to Testing the Terminal Connection.

Does the date appear on the terminal?

The device is properly connected. Continuewith the next step.

If nothing appears on the terminal, the device isnot receiving data. Go to Testing the TerminalConnection: No Data.

If scrambled characters appear on the screen,the device is receiving data but there is stillsomething wrong. Go to Testing the TerminalConnection: Scrambled Data.

Step 7. Verify that RealPort is running on the HP-UX operating system by entering:

ps ef| grep drp

Do you see an entry for each PortServer similar to the following?

root 2254 1 0 Dec 13 ? 0:03/sbin/drpd 1 199.86.0.1


Your devices should now be working properly.If they still do not work correctly, call DigiTechnical support.

Do one of the following:

Reboot the UNIX server●

Add the PortServer device again indrpadmin.

●

Your devices should now be in an availablestate and working properly. If they are not, goto Step 8.

Your devices should now be in an availablestate and working properly. If they are not,continue to the next step to force a carrierdetect.

Step 8. Force carrier detect on the port by entering one of the following commands:

ditty forcedcd /dev/ttyx#

tty is entered if you have a terminal connected. If you have a device that doesnot require a login, use tty for a terminal device.

Do your devices work correctly now?

You have completed the MasterTroubleshooting Process.

Call Digi Technical Support.

Master Troubleshooting Process: HP-UX (Some Devices Fail)

Use this troubleshooting process if one or several devices function incorrectly or not at all. This process focuseson your operating system, which is where the problem probably might be.

Process

Step 1. Test the port connection from the operating system. Go to Testing the port connection.

Do the DTR and RTS indicator lights on the PortServer flash briefly and do you get data resultsand port status information on your terminal screen?

Your connection was successful. Your devicesshould work.

If the device doesn't work, call Digi TechnicalSupport.

Make note of the results and continue to thenext step.

Step 2. Check the LED indicators on the PortServer. Is OFC on?

Go to Checking the LED Indicators: OFC On?

If OFC is not on, continue to the next step.

Step 3. Telnet directly to the port. Go to Performing a Telnet to the Port.

When you entered the command on the keyboard, did the word "Connected" appear on thescreen?

Also, anything you entered should appear onthe attached terminal and anything entered onthe dumb terminal should appear on your telnetscreen. This verifies that the port is functional,along with the attached cable and terminalwhile bypassing RealPort.

Disconnect from the telnet session. Go toDisconnecting Telnet.

If the host cannot telnet to the port, thenRealPort won't connect to it.

Check the previous set commands on thePortServer and try the command again.

If you still do not get any results, call DigiTechnical Support.

Step 4. Test the connection from each terminal. Go to Testing the Terminal Connection.

Does the date appear on the terminal?

The device is properly connected. Continuewith the next step.

If nothing appears on the terminal, the device isnot receiving data. Go to Testing the TerminalConnection: No Data.

If scrambled characters appear on the screen,the device is receiving data but there is stillsomething wrong. Go to Testing the TerminalConnection: Scrambled Data.

Step 5. Verify that RealPort is running on the HP-UX operating system by entering:

ps ef| grep drp

Do you see an entry for each PortServer similar to the following?



Your devices should now be working properly.If they still do not work correctly, call DigiTechnical support.

Do one of the following:

Reboot the UNIX server●

Add the PortServer device again indrpadmin.

●

Your devices should now be in an availablestate and working properly. If they are not, goto Step 6.

Your devices should now be in an availablestate and working properly. If they are not,continue to the next step to force a carrierdetect.

Step 6. Force a carrier detect on the port by entering one of the following commands:

ditty forcedcd /dev/ttyx#

tty is entered if you have a terminal connected. If you have a device that doesnot require a login, use tty for a terminal device.

Do your devices work correctly now?

You have completed the MasterTroubleshooting Process.

Call Digi Technical Support.

Running PortServer Diagnostics

Use one of these procedures to perform hardware diagnostic tests on a PortServer. In the event of a diagnostictest failure, first verify that you are running the test correctly, then contact Digi Technical Support.

For a description of each individual diagnostic test in the following procedures, see PortServer Diagnostic TestDescriptions.

There are two modes of user diagnostics available for troubleshooting the PortServer; video display mode andfront panel mode.

Video Display Diagnostics Procedure

Connect a terminal (or PC with terminal emulation software) to port 1 of the PortServer.

Note: Ensure that your terminal will send the v character when the DTR (Data Terminal Ready) andRTS (Request To Send) signals on the serial port are low (inactive). If you encounter a problem, use a3-wire connection to the terminal.

1.

Configure the terminal for 9600 baud, 8 data bits, 1 stop bit, and no parity.2.

Turn the power switch on the PortServer off and then back on.3.

Before the POST diagnostic tests finish, enter a "v" from the terminal attached to port 1.

A startup screen should appear. The screen displays test information, and waits for user input. There areeight tests that can be selected.

4.

Follow the screen menu and prompts to start and stop each test5. Choose Back to return to and continue with the Master Troubleshooting Process.6.

Front Panel Display Diagnostics Procedure


Before the POST diagnostic tests finish, press either arrow pushbutton on the front panel of thePortServer.

At this time, all of the lights (LEDs) go OFF, the left 7-segment display is blank, and the right7-segment display reads "1." The right decimal point blinks at a 1 second rate. At this point, Test 1 -Panel Light Test is selected.

2.

To select a test, press the right pushbutton.

The right LED will cycle through the possible test numbers.

3.

Once the desired test has been selected, press the left pushbutton to start the test.

The left decimal point will light to indicate the test has started and the appropriate test information willbegin updating via the front panel indicators.

The selected test will continue to cycle until an error is detected or until you stop the test by pressing thepushbutton. Failures accumulate and count up in the 10 digit LED display.

4.

To stop a test, press and hold the left arrow button and wait for the left decimal point to go OFF. At thispoint, release the pushbutton.

The test should stop. At this point, the left alphanumeric display will display either a "P" or an "F" forpass or fail respectively. The right display will show the test number that was just executed. "P3"indicates that test 3 has passed, while "F3" indicates that the test failed.

5.

Choose Back to return to and continue with the Master Troubleshooting Process.

Running PortServer II Diagnostics

Use one of the following procedures to perform hardware diagnostic tests on a PortServer. In the event of adiagnostic test failure, first verify that you are running the test correctly, then contact Digi Technical Support.

There are two modes of user diagnostics available for troubleshooting the PortServer; video display mode andfront panel mode.

Video Display Diagnostics Procedure

Connected a terminal to port 1 and configured the terminal for VT100 emulation, 9600 baud, 8 data bits,1 stop bit, and no parity.

Note: Ensure that your terminal will send the v character when the DTR (Data Terminal Ready) andRTS (Request To Send) signals on the serial port are low (inactive). If you encounter a problem, use a3-wire connection to the terminal.

1.


When PO appears on the PortServer front panel LED display, press V on the terminal keyboard to enterdiagnostic mode.

A display similar to the following should appear.

Digi International Inc. PortServer IIEthernet address....12:34:56:78:9A:BCROM revision: 91-398 Rev DROM startup (cold boot)Instruction cache size: 0x00001000Data cache size: 0x00000800RAM size: 0x00200000CPU test............passedWatchdog test.......passedROM checksum test...passedFlash RAM test......passedSimple RAM test............0xA00010000xA01F0010 passedComplex RAM test............0xA00010000xA0002000 passedTimer test..........passedRT clock+RAM test...passedEthernet internal...passedEthernet external...passedTest EBI 0 UART08..15 devices passedEBI 1...............noneEBI 2...............noneEBI 3...............none

Press "?" for diagnostics menu or carriage return to continue booting

3.

Press ? to display the Diagnostics Menu.

The Diagnostic Menu should appear:

DIAGNOSTICS MENU---A = All tests (except 9)1 = Front panel light test2 = RAM test3 = Timer and real-time clock test4 = EBI internal loopback test

4.

5 = EBI external loopback test6 = Ethernet internal loopback test7 = Ethernet external loopback test8 = Flash RAM test9 = Watchdog testC = Configure bootT = Set date & timeEthernet address: 12:34:56:78:9A:BCB = Reboot

To start a test, press the appropriate test number. See PortServer II Diagnostic Tests Descriptions fordetails on each test.

5.

In the event of a diagnostic test failure, first verify that you are running the test correctly, then contactDigi Technical Support.

6.

Choose Back to return to and continue with the Master Troubleshooting Process.7.

Front Panel Display Diagnostics Procedure


When PO appears in the alphanumeric display, press either the left (<) or right (>) pushbutton on thefront panel to enter diagnostic mode.

2.

Use the right pushbutton (>) to cycle through the tests until the desired test number is displayed in thePortServer front panel LED display.

These are the tests:

A = All tests (except 9)1 = Front panel light test2 = RAM test3 = Timer and real-time clock test4 = EBI internal loopback test5 = EBI external loopback test6 = Ethernet internal loopback test7 = Ethernet external loopback test8 = Flash RAM test9 = Watchdog testC = Configure bootT = Set date & time

3.

Press the left pushbutton (<) to start the test. See PortServer II Diagnostic Tests Descriptions forinformation on individual tests.

The test will continue until an error is detected or until you stop it.

4.

To stop a test, press the left pushbutton (<). If a test passes, a P plus the test number will be displayed inthe front panel LED display (example: P3). If it fails, F plus the test number will be displayed (example:F3).

5.

In the event of a diagnostic test failure, first verify that you are running the test correctly, then contactDigi Technical Support.

6.


Troubleshooting TFTP

Use this procedure to verify that TFTP is working correctly on your UNIX host. This procedure is only valid ona UNIX system.

Procedure

Access a root prompt on the UNIX host.1.

Make sure that you are not in the /tftpboot directory.2.

Enter this command:

tftp ipaddress

where ipaddress is the IP address of the UNIX host. A TFTP prompt should appear.

3.

Enter this command at the TFTP prompt:

tftp > get tftp_file_name

where tftp_file_name is the name of the PortServer boot image in the /tftpboot directory.

Result Action

This message appears:

received [number] bytes in [number] seconds

Continue to step 6 of this procedure.

An error message appears Skip to step 7 of this procedure.

4.

Enter this command at the TFTP prompt to exit TFTP:

tftp> quit

5.

Compare the size of the original file against the transferred file using this command:

ls -l tftp_file_name /tftpboot/tftp_file_name

Result Action

The file sizes match. TFTP is working correctly. Exit this procedure and continuetroubleshooting.

The file sizes do not match. Continue to the next step in this procedure.

6.

Verify that the /tftpboot directory exists and has read, write and execute (777) permissions with thiscommand:

ls -l /tftpboot

If necessary, use this command to create the directory:

mkdir /tftpboot

If necessary, use this command to change permissions of the directory to read, write and execute:

chmod 777 /tftpboot

7.

Verify that the file /tftpboot/ftp_file_name exists and has read and execute permissions with thiscommand:

8.

ls -l /tftpboot/ftp_file_name

where ftp_file_name is the name of the firmware boot image specified by the PortServer.

If necessary, use this command to change permissions of the file to read and execute:

chmod 666 /tftpboot/ftp_file_name

Verify that the inetd.conf file is properly configured for tftp by displaying the file /etc/inetd.conf.

An entry similar to this should be uncommented:

tftp dgram udp something

where something will vary with each operating system.

For controlled TFTP access, make sure that the file /etc/tftpaccess.ctl exists and verify that it only allowsaccess to public directories. If this file is not present, tftp will allow full access. A sample file is locatedin the directory /usr/lpp/tcpip/samples.

9.

Restart the inetd process with these two commands:

ps -ef | grep inetd

This will report back the inetd process number.

Kill -1 inetd_PID

Where inetd_PID is the process number for the inetd process reported by the previous command.

10.

Test TFTP by repeating steps 1-7.11.

If successful, reboot the PortServer.12.


Resetting PortServer

Use this troubleshooting procedure when AC does not display on PortServer and you need to reset PortServer tothe factory defaults.

Important: You will lose all PortServer settings when you reset PortServer to factory defaults. If you have acomplex configuration, call Digi Technical Support for assistance.

Procedure

Power on while simultaneously pressing both arrow buttons on the front of PortServer.1.

Hold these buttons down until EP is displayed on PortServer I or CL is displayed on PortServer II.2.

Reboot PortServer.3.

If AC appears, reconfigure PortServer. 4.

If AC still appears, choose Back to return and continue with the Master Troubleshooting Process.

If AC doesn't appear, make note of the status of the LED display on the front of the PortServer.

5.

Contact Digi Technical Support.6.

Testing the Port Connection

Use this troubleshooting procedure to test the port connection from the operating system.

Procedure

Before disconnecting any cabling, ensure you have disabled the services (if you have already enabledthem) on that port.

1.

Disconnect the cabling to the port on which you are testing.2.

On the PortServer, press the right arrow until the LED indicator displays the port you are testing.3.

None of the indicator lights should be lit at this point. Continue with this procedure. If theindicator lights are lit, go to PortServer Front Panel.

Enter on the command line:4.

ditty -a portname

where portname is the name of the port you are testing.


Performing a Telnet to the Port

Use this troubleshooting procedure when you are checking the connection to your operating system.

Procedure

Attach a dumb terminal to the PortServer port you are testing.1.

From the root prompt, enter:2.

telnet ipaddress [2000+port number]

where ipaddress is the IP address of the PortServer and an example of[2000+port number] would be 2001 for port number 1, 2016 for portnumber 16, and so on.

Choose Back to return to the Master Troubleshooting Process for your operating system.3.

Disconnecting Telnet

Use this troubleshooting procedure once you have performed a telnet session, observed the results, and nowneed to disconnect the telnet session.

Procedure

Press Ctrl-] (hold down the Ctrl key and press the ] key).1.

At the telnet prompt, enter: 2.

quit

Choose Back to return to the next step in the Master Troubleshooting Process.3.

Telnet: Receiving a Login Prompt

Use this procedure during the Master Troubleshooting Process when you performed a telnet to the PortServerand did receive a PortServer login prompt.

Procedure

Log in as root. The default password is dbps.1.

Check to see that the required information appears in your port settings by using the followingcommands:

2.

Command Requirement

set port range=range

where range is two numbers separated by ahyphen. The first number is the beginningrange and must be less than the secondnumber. Often the number is 1. The secondnumber is the end range and is between 8 and64.

prn or rp must be in the dev column.

IMPORTANT! All set port parameters mustbe factory default.

Go to Example: set port Command for anexample of the result of choosing a set portrange that equals 1-16.

set flow range=range

where range is two numbers separated by ahyphen. The first number is the beginningrange and must be less than the secondnumber. Often the number is 1. The secondnumber is the end range and is between 8 and64.

If you are using an 8-wire modem cable or ifyour operating system is AIX, HP-UX,Solaris, or SCO UnixWare/SVR4, the altpincolumn must display on.

Note: If you are using an RJ-45 10-pinmodem cable, the Flow Range setting musthave off in the altpin column.

Go to Example: set flow Command for anexample of the result of choosing a set flowrange that equals 1-16.

set auth

In the RealPort column, the set auth valueshould be set to o for each RealPort port.

Go to Example: set auth Command for anexample of the result of using the set authcommand.

If your port settings match the above requirements, choose Back to return and continue with the MasterTroubleshooting Process.

3.

If your port settings do not match the above requirements, you need to change the port or a groupof ports to be available for RealPort. See the PortServer II Command Reference Guide for moreinformation. Once you've changed the port settings and the devices still don't work, go throughthe Master Troubleshooting Process again.

Telnet: Receiving No Login Prompt

Use this troubleshooting procedure to verify the connection when you performed a telnet to the PortServer anddid NOT receive a PortServer login prompt.

If you can find no problem at the end of each step in this procedure, continue with the next step. If there is aproblem, fix it and check to see of the RealPort devices are working. If they are, you should have resolved theproblem. If they are not, go back to the Master Troubleshooting Process.

Procedure

Turn off the PortServer and issue the ping command,1.

ping ipaddress

If it fails (you do not receive a response), continue with this procedure.

If it succeeds (you received a response), this indicates there is another system using the same IPaddress. In this case, you need to assign another IP address to the PortServer.

From a terminal directly attached to the PortServer, check the configuration by entering the command:2.

set config

Verify the IP address, the mask settings, the gateway and that the RealPort setting is 771.

Check the Ethernet cable. Verify the following: 3.

The Ethernet cable is connected securely at both ends.●

The Ethernet cable is pinned correctly.●

The quality of the cable is sufficient for the cable length and the cable environment.●

Note: Common Category 5 Unshielded Twisted Pair cabling can generally be run 300 meters ata speed of 10 Mbps and 150 meters at higher speeds. Consult an Ethernet cable manufacturer fora recommended cable for your configuration.

IMPORTANT! If you are using a 10/100 hub, PortServer only supports a 10 megabit Ethernetnetwork.

If you are using a Thinnet (10Base2) cable, make sure the cable selector switch on the PortServer is inthe left-handed position.

4.

If you are using a Twisted Pair (10Base2) cable, make sure the cable selector switch on thePortServer is in the right-handed position.

Verify your Ethernet hub. See your Ethernet hub manual.5.

If there is still a problem, choose Back to return to and continue with the Master TroubleshootingProcess.

6.

Checking LED Indicators: OFC On?

Use this procedure when an OFC indicator light is on on the PortServer.

Note: This Procedure only works with a PortServer and not a PortServer II. PortServer II users should chooseBack to return and continue with the Master Troubleshooting Process.

Procedure

From a terminal attached to the port, enter:

Ctrl-Q

1.

From the PortServer, enter:

kill tty=port number

where port number is the number assigned to the PortServer.

2.

If OFC is still on, enter the following at the PortServer command line prompt:3.

who

If the Connected from column shows other items such as IP address, make sure that theoriginating system process is disabled.

If in either case, the lights are still on, choose Back to return and continue with the MasterTroubleshooting Process.

Testing the Terminal Connection

Use this troubleshooting procedure when you need to test the connection at each terminal.

Procedure

Connect terminals to the ports (using a null modem cable, if necessary).1.

Enter the following at the UNIX command prompt for each port:2.

date >/dev/tty01

where date is merely a command used for a this simple test to provide textoutput (there is no other significance) and tty01 is the port to which the terminalis connected.


Testing the Terminal Connection: No Data

Use this troubleshooting procedure if the device is not receiving data and you need to test the terminalconnection.

Procedure

Disconnect the dumb terminal and install a loopback plug.1.

From the UNIX root prompt for each port, enter:2.

date >/dev/tty01

where date is merely a command used for a this simple test to provide textoutput (there is no other significance) and tty01 is the port to which the terminalis connected.

If the date appears, choose Back to return to the Master Troubleshooting Process.3.

If the date does not appear on your screen, check the power, cables, connections and so on. Ifyou still cannot get the date to appear, contact Digi Technical Support.

Testing the Terminal Connection: Scrambled Data

Use this troubleshooting procedure to try to make the data on your screen appear normally.

Procedure

Verify that your terminal and operating system settings for the port are the same. Specifically, but notexclusively, look at flow control, baud rate, data bits, stop bits and parity.

1.

If the settings don't match, change them. If the scrambled data is no longer there, choose Back toreturn to and continue with the Master Troubleshooting Process.

Check your cable to see that it is pinned correctly and that it is of sufficient quality. See the PortServerCabling Guide.

2.

If you still cannot get the data to appear normally, contact Digi Technical Support.

PortServer Diagnostics Test Descriptions

The following descriptions explain the test philosophy for each functional PortServer diagnostic test. The basictest is the same whether it is run from the video display or the front panel display.

Test 1 - Panel Light Test

This test cycles the 10 LEDs ON and OFF and both seven-segment displays in one second intervals. Since theLEDs and seven-segment displays are all write only, the operator must make a visual check of the indicators toensure that they all cycle correctly. The pushbuttons are read by the test and checked for the non-depressed state(0).

Test 2 - Memory Test

Each pass of this test performs a pattern test and an address tag test to DRAM memory.

The byte pattern is incremented for each pass and is displayed on the front panel LEDs 0-7 (TD-RI). The patternis written to 32K bytes beginning at address 08000h. The pattern is written again to 32K bytes beginning ataddress 30000h. The two 32K blocks are compared to determine pass or fail status.

The address tag test writes 32K bytes beginning at address 08000H. Address 08000h equals a 0h, 08001h equalsa 1h, etc. This same tag pattern is written 32K times beginning at address 30000h. The two 32K blocks arecompared to determine pass or fail status.

The word pattern is incremented for each pass and is displayed on the front panel LEDs 0-7 (TD-RI). Thepattern is written to 32K words beginning at address 10000h. The pattern is written again to 32K wordsbeginning at address 20000h. The two 64K blocks are compared to determine pass or fail status.

The address tag test writes 32K words beginning at address 10000h. Address 10000h equals a 0h, 10002hequals a 2h, etc. This same tag pattern is written 32K times beginning at address 20000h. The two 64K blocksare compared to determine pass or fail status.

Test 3 - Memory/DMA Test

This test uses DMA0 to move data from one memory location to another. The byte pattern is incremented foreach pass and is displayed on the front panel LEDs 0-7 (TD-RI). The pattern is written to 32K bytes beginningat address 08000h. DMA0 is used to move 32K of data from 08000h to 10000h. When the move is complete,DMA0 interrupts and the two 32K blocks are compared to determine pass or fail status. If the DMA transfer isnot completed within two seconds, a timeout error causes the test to fail.

Test 4 - Async Internal Test

This test is used to check out the 16550 async ports. The test puts the UART in loopback mode. The four outputsignals, DTR, RTS, OUT1, and OUT2 are looped back to the four input signal lines, CTS, DSR, RI and DCD.These signals are checked for high and low conditions. The UARTs are initialized to 9600 baud, 8 data bits, 1stop bit, and no parity. Data is transmitted and received by the same UART.

Received data is compared to the transmitted data. As each port is being tested, port test results ("Pass/FAIL")are displayed. A failure on one or more ports is considered a test "FAIL."

Test 5 - Built-In UART External Loopback Test

Same as Test 4, but uses external loopback. From the front panel, press the right pushbutton to select the port totest. The display will cycle from "01" to "16" or highest UART plus "All". With the port selected, press the leftpushbutton to start the test.

In Test 5 (Async External Test), each port loops back on itself instead of looping back between ports. Thisrequires a test plug made from an RJ-45 connector at one end, with the pins wired as follows:

Output Pins Connected To Input PinsPin 3 (RTS) connected to Pin 1 (RI) and Pin 8 (CTS)Pin 5 (SOUT) connected to Pin 6 (SIN)Pin 9 (DTR) connected to Pin 10 (DCD)

Test 6 - NIC/DMA Test

This tests the 8390 NIC's ability to transmit, receive, and verify data in three diagnostic modes. To ensure thatall test display information and test results are correct, the PortServer unit must be disconnected from theEthernet network, and the PortServer’s Ethernet connector properly terminated.

Test 7 - Watchdog Timer Test

This test checks out the watchdog timer, a hardware feature used to ensure system reliability. The firmwaremust access PCS 5 within 1.6 seconds or the CPU will reset and jump to the reset vector (0FFFF0h).

It is up to the system to keep accessing PCS 5 to prevent it from resetting. This will force the POST diagnosticsequence to begin. This test allows the timer to expire. Normal test execution causes the user diagnostics tojump to the reset vector and begin the POST diagnostic sequence. The test will fail after three seconds if thetimer has not expired.

PortServer II Diagnostics Test Descriptions

The following descriptions explain the test philosophy for each functional PortServer diagnostic test. The basic test is the same whether it is runfrom the video display or the front panel display.

Test # Test Test Description1 Front Panel Light Test This cycles the PortServer front panel LEDs on and off. It also cycles both

alphanumeric displays.2 Memory Test This is a memory test. It takes about two minutes for each pass.3 Timer Test This ensures that the timer counts and interrupts. It tests the real-time clock, checking

the set time for legal values and tests the battery-backed RAM in real-time clock.4 Built-in UART and External EBI Internal

Loopback TestThis test ensures that the UARTs interrupt and that data loops back.

5 Built-In UART and External EBIExternal Loopback Test

This test is the same as Test 4, but uses an external loopback (required for the test topass). From the front panel, press the right pushbutton (>) to select the port to test. Thedisplay will cycle from 01 to 16 (or higher, if you have expansion modules connected)plus All. With the number of the port to test displayed, press the left pushbutton (<) tostart the test.

6 Ethernet Internal Loopback Test This tests the 10BaseT and 10Base2 circuits within PortServer II.7 Ethernet External Loopback Test This verifies correct operation of the Ethernet interfaces to the external network. You

must have a dummy network (for example, a "T" connector with termination resistors)attached to each Ethernet connector for this test to pass.

8 Flash ROM Test (Read Only) This verifies that the Flash ROM can be read.9 Watchdog Timer Test This checks out the watchdog timer used to check system reliability.

PortServer Front Panel

The front panel of the PortServer terminal server has ten LEDs, two seven-segment alphanumeric displays, and two pushbuttons with a left and rightarrow.

The pushbuttons can be used to:

Select diagnostic tests. See Running PortServer Diagnostics and Running PortServer II Diagnostics.●

Reset the PortServer to the factory defaults. See Resetting a PortServer to Factory Defaults.●

Select a port to monitor for EIA-232 serial activity.●

The two-digit alphanumeric display is used to list error messages and inform the user of test or activity status.

The ten LEDs have different meanings, according to the testing or display mode that the PortServer operating system is in.

SEND (Serial Activity)

You can monitor a port’s activity by pressing either pushbutton when AC is shown on the alphanumeric display. The display will then show the portnumber being monitored; depress the same pushbutton repeatedly until the port you wish to monitor is displayed.

The LED indicators provide EIA-232 line status information (similar to a breakout box) and EIA-232 flow control information. The ten LEDs thengive information related to the labels on the top ("SEND"): TD, RD, RTS, CTS, DSR, DCD, DTR, RI, OFC and IFC. The first eight correspond toactivity of that EIA-232 signal on the port being monitored. OFC stands for Output is Flow Controlled; IFC stands for Input is Flow Controlled.

ETHERNET (Ethernet Activity)

When EA is shown by the alphanumeric display, the row of ten LEDs gives Ethernet information as follows:

Signal Category LED Active or "Lit" Signal Means

SerialTD Data has been transmitted on any of the serial lines.RD Data has been received on any of the serial lines.

Twisted PairLG A good physical connection to the PortServer exists. LG stands for "Line Good."

POL Polarity is backwards. While the PortServer hardware fixes this, it indicates that the twisted pair wiringhas been installed with the wires transposed.

Receive

CS Carrier Sense. This LED blinks when the PortServer hardware senses the Ethernet carrier.RX A packet has been received by the PortServer.ERR A network error on a packet has been received (CRC, Frame, FIFO overrun, etc.).

OVF An overflow condition has occurred. This occurs when packets come faster than the PortServer hardwarecan process them.

TransmitTX The PortServer hardware is transmitting a packet.

COL A collision has occurred on the network (any collision—not necessarily on packets destined to ororiginated by the PortServer devices).

Example: set port Command

Use this example of the set port command to check your port settings. Once you have completed this, choose Back to return and continuewith the previous procedure.

Following is an example of the result of choosing a port range that equals 1-16.

Example: set flow Command

Use this example of the set flow command to check your port settings. Once you have completed this, choose Back to return and continuewith the previous procedure.

Following is an example of the result of choosing a flow range that equals 1- 16.

Example: set auth Command

Use this example of the set auth command to check your port settings. Once you have completed this, choose Back to return and continuewith the previous procedure.

Following is an example when you use the set auth command:

PortServer Cable Guide

EIA-232 Asynchronous Interface

General EIA-232 Cable Information●

EIA-232: DB-25 - to - DB-25

Digi DB-25 Pinouts●

Software Handshake Cable●

Hardware Handshake Cable●

Fully-Wired Terminal/Printer Cable●

Modem Cable●

EIA-232: RJ - to - DB-25

Digi RJ-45 Pinouts●

RJ Connector Types●

Digi RJ-45 to DB-25 Adapters●



8-Wire ALTPIN Cable●

10-Wire Terminal/Printer Cable●

8-Wire ALTPIN Modem Cable●

10-Wire Modem Cable●

EIA-422 Asynchronous Interface

General EIA-422 Cable Information●

Digi EIA-422 Pinouts●



Modem Cable●

Copyright © 2000, Digi International. All rights reserved.

General EIA-232 Cable Information

Use this information to determine the proper EIA-232 cable requirements for your application.

Physical Cable Characteristics

EIA-232 serial interface cables should be shielded, low capacitance cables, designed specifically for serial datatransmission.

Grounding Requirements

EIA-232 interface cables should have the shield grounded at both ends of the cable. Digi recommends ChassisGround, available on the shell of Digi's DB-25 connectors, and pin 4 of a 10-pin RJ-45 connector.

Environmental Requirements

While good shielding provides reasonable protection against "noise" (electromagnetic interference, or EMI),cables should still be routed away from noise sources wherever possible. Avoid laying cables in close proximityto transformers, generators, motors, fluorescent lights, etc.

Data Rate Information

The maximum date rate that can be used for EIA-232 connections is primarily determined by the quality andlength of the interconnecting cable. The quality of the cable (for transmission purposes) is generally determinedby the capacitance per foot rating of the cable.

The following table gives the recommended maximum cable length for a given data rate. Longer cables may beimplemented at your discretion.

Data Rate vs. Cable Length

Data Rate (bps) Maximum Cable Length

57,600 or less 100 feet

115,200 80 feet

230,400 40 feet

460,800 20 feet

921,600 10 feet

Notes:

The maximum length is the amount of cable that is connected to a Digi supplied interconnect device,such as Quad or Octa cables and boxes.

●

The maximum length is based on a cable rated at:

12.3 pF/foot, conductor to conductor22.4 pF/foot conductor to shield

●

In situations where low-capacitance cable is unavailable, or very long cable runs are required, "short-haul"

modems can be used to increase the effective range of the EIA-232 interface. Short-haul modems are similar tostandard modems, except that they are connected directly to each other via a cable instead of going through atelephone circuit.

Note: Use only externally-powered short-haul modems with Digi products.

Transmission Errors

If transmission errors occur, follow this procedure to determine the cause of the problem:

Reduce the baud rate.1.

Reduce the cable length.2.

Use a cable with a lower capacitance per foot rating.3.

Digi DB-25 Connector Pin Assignments

Signal Description DTE Use Pin #

GND Chassis Ground N/A Shell

TxD Transmitted Data Output 2

RxD Received Data Input 3

RTS Request to Send Output 4

CTS Clear to Send Input 5

DSR Data Set Ready Input 6

SG Signal Ground reference 7

DCD Data Carrier Detect Input 8

DTR Data Terminal Ready Output 20

RI Ring Indicator Input 22

DB-25 Software Handshaking (XON/XOFF) Cable

The following three-wire cable is often sufficient for a terminal, printer, or other DTE device configured forsoftware flow control.

Simple Terminal/Printer Cable

DB-25 Female(Digi End)

DB-25 Male(Peripheral)

Signal Pin Pin Signal

TxD 2 connected to 3 RxD

RxD 3 connected to 2 TxD

SG 7 connected to 7 SG

GND Shell connected (via shield) to Shell GND

This cable is a three-wire null modem cable. Transmitted Data on one end of the cable is connected to ReceivedData at the other end, and vice versa. The male DB-25 end can be plugged directly into most serial terminalsand printers without any adapters. The female DB-25 end plugs directly into any Digi DB-25 serial port.

DB-25 4-Wire Hardware Handshaking (Ready/Busy) Cable

The following four-wire cable is often sufficient for a terminal, printer, or other DTE device configured forDTR (hardware) flow control. However, some terminals and printers may use a signal other than DTR for flowcontrol. In addition, some terminals and printers may have other cable requirements. Consult your terminal orprinter manual for this information. For more universal compatibility, use a fully-wired DB-25 terminal/printercable.

Terminal/Printer Cable with DTR Handshaking

DB-25 Female(Digi End)

DB-25 Male(Peripheral)




CTS 5 connected to 20 DTR


GND Shell connected (via shield) to Shell GND

jumpered 4 & 5 RTS & CTS

Note: Some Okidata printers use a control signal on pin 11, called Supervisory Send Data (SSD) instead ofDTR. In this case, simply connect CTS on the female DB-25 side to pin 11 of the male DB-25, instead of pin20.

Fully-Wired DB-25 Terminal/Printer Cable

The following cable wiring supports most serial terminals or printers with either software or hardwarehandshaking. This cable is valid with any Digi DB-25 serial port.

Most terminals and printers use Data Terminal Ready (DTR) for Ready/Busy hardware handshaking. Thefollowing cable wiring supports this method.

Terminal/Printer Cable for Software (XON/XOFF) or Hardware (DTR) Handshaking

DB-25(Digi End)

DB-25 Male(Terminal/Printer)


RTS 4 connected to 5 CTS

GND Shell connected to Shell GND




CTS 5 connected to 20 DTR*

DTR 20 connected to 8 and 6 DCD and DSR**

DCD and DSR 8 and 6 connected to 4 RTS

* Okidata Printers may use SSD (pin 11) instead.**Some printers require DSR. If DSR is required, it should be either wired or the printer set to ignore DSR(DSR Invalid).

Important: Other printer manufacturers may use different methods of flow control. Consult your printer'sdocumentation for specific wiring requirements.

DB-25 Modem Cable

To connect a DB-25 equipped asynchronous adapter to a modem, use a standard "straight-through" cable. Astraight-through cable has a DB-25 female connector at the Digi end, and a DB-25 male connector at themodem end. All 25 pins are connected, 1 to 1, 2 to 2, 3 to 3, etc. Use shielded cable, and connect pin 1 of eachconnector to the cable shield.

Digi RJ-45 Connector Pin Assignments

10-pin RJ-45 plugs may be difficult to obtain in the retail market; therefore, most Digi device driver softwareincorporates an optional feature called ALTPIN, which swaps the logical functions of DSR (Data Set Ready)with DCD (Data Carrier Detect).

When ALTPIN is enabled, DCD becomes available on pin 1 of an 8-pin RJ-45 connector (equivalent to pin 2 ofa 10-pin connector).

Signal Description DTE Use Pin #

RI Ring Indicator Input 1

DSR (DCD*) Data Set Ready (Data Carrier Detect*) Input 2

RTS Request to Send Output 3

GND Chassis Ground N/A 4

TxD Transmitted Data Output 5

RxD Received Data Input 6

SG Signal Ground reference 7

CTS Clear to Send Input 8

DTR Data Terminal Ready Output 9

DCD (DSR*) Data Carrier Detect (Data Set Ready*) Input 10

*When ALTPIN is in effect.

RJ Connector Types

The following table shows the relationship of various RJ plugs to the Digi RJ-45 10-pin jack. The Digi 10-pinjack can accept any of the listed plug types. The wiring of each plug type corresponds to support of specificcapabilities such as software handshaking, hardware handshaking, and the Digi ALTPIN feature.

Digi10-PinJack

Signal Name RJ-4510-PinPlug

RJ-458-PinPlug

RJ-116-PinPlug

RJ-114-PinPlug

1 RI 1

2 DSR (DCD*) 2 1

3 RTS 3 2 1

4 GND 4 3 2 1

5 TxD 5 4 3 2

6 RxD 6 5 4 3

7 SG 7 6 5 4

8 CTS 8 7 6

9 DTR 9 8

10 DCD (DSR*) 10

*When ALTPIN is in effect.

Digi RJ-45 to DB-25 Cable Adapters

RJ-45 to DB-25 cable adapters can be purchased from Digi. These adapters consist of a Digi 10-pin RJ-45 plugconnected through a two- or four-foot cable to a DTE-configured DB-25 male connector. You can use DB-25modem cables with the adapters for longer cable runs.

Because these adapters use the standard Digi 10-pin RJ-45 plug and DB-25 connector configurations, theyprovide full modem support (Ring Indicator and Data Carrier Detect are available only on 10-pin RJ-45connectors).

Part numbers for RJ-45 to DB-25 Cable Adapters

Cable RJ45 to DB25 Male 24" 76000129Cable RJ45 to DB25 Male 48" 76000195

RJ-11 Software Handshaking (XON/XOFF) Cable

The following 3-wire cable is often sufficient for a terminal, printer or other DTE device configured forsoftware flow control.

Simple Software Handshaking Terminal/Printer Cable (RJ-11)

RJ-11 (Digi End)

DB-25 Male (Peripheral)





GND 1 connected (via shield) to 1 (or shell) GND

This cable is a 3-wire null modem cable. Transmitted Data on one end of the cable is connected to ReceivedData at the other end, and vice versa.

The RJ-11 plug fits into the center of the RJ-45 jack. The male DB-25 end can be plugged directly into mostserial terminals and printers without any adapters.

An RJ-45 8-pin connector uses the same wiring with the center pins only--pins 3, 4, 5, and 6. See RJ ConnectorTypes for a comparison of various RJ connector types that work with the Digi 10-pin RJ-45 jack.

RJ-45 8-Pin Plug Hardware Handshaking (Ready/Busy) Cable

Using an 8-pin plug, the following cable wiring is often sufficient for a terminal, printer, or other DTE deviceconfigured for DTR (hardware) flow control. However, some terminals and printers may use a signal other thanDTR for flow control. In addition, some terminals and printers may have other cable requirements. Consult yourterminal or printer manual for this information. For more universal compatibility, use the RJ-45 10-wireterminal/printer cable or a Digi RJ-45 to DB-25 adapter.

Terminal/Printer Cable with DTR Handshaking

RJ-45 (Digi End)

DB-25 Male (Peripheral)




CTS* 7 connected to 20 DTR



jumpered 4 & 5 RTS & CTS

* Some Okidata printers use a control signal on pin 11, called Supervisory Send Data (SSD) instead of DTR. Inthis case, simply connect CTS on the RJ-45 side to pin 11 of the DB-25, instead of pin 20.

RJ-45 8-Wire ALTPIN Terminal/Printer Cable

Using an 8-pin RJ-45 plug, the following cable wiring supports most serial terminals or printers with eithersoftware or hardware handshaking using the Digi ALTPIN option. This cable is valid with any Digi RJ-45 serialport.

Most terminals and printers use Data Terminal Ready (DTR) for Ready/Busy hardware handshaking. The cableshown supports this method.

ALTPIN Terminal/Printer Cable for Software (XON/XOFF) or Hardware (DTR) Handshaking

RJ-45 8-pin(Digi End)



DCD* 1 connected to 4 RTS


GND 3 connected (via shield) to Shell GND




CTS 7 connected to 20 DTR**

DTR 8 connected to 6 and 8 DCD and DSR***

* ALTPIN must be turned on for pin 1 to be DCD. When ALTPIN is enabled, DCD becomes available on pin 1of an 8-pin RJ-45 connector (equivalent to pin 2 of a 10-pin connector).** Okidata Printers may use SSD (pin 11) instead.***Some printers require DSR. If DSR is required, it should be either wired or the printer set to ignore DSR(DSR Invalid).

Important: Other terminal or printer manufacturers may use different methods of flow control. Consult yourprinter documentation for specific wiring requirements.

RJ-45 10-Wire Terminal/Printer Cable

Using a 10-pin RJ-45 plug, the following cable wiring supports most serial terminals or printers with eithersoftware or hardware handshaking. This cable is valid with any Digi RJ-45 serial port.

Most terminals and printers use Data Terminal Ready (DTR) for Ready/Busy hardware handshaking. The cableshown supports this method.

Terminal/Printer Cable for Software (XON/XOFF) or Hardware (DTR) Handshaking

RJ-45 10-pin(Digi End)




GND 4 connected (via shield) to Shell GND




CTS 8 connected to 20 DTR**

DTR 9 connected to 8 and 6 DCD and DSR***

DCD* and DSR 10 and 2 connected to 4 RTS

* ALTPIN must be turned off for DCD to be on pin 10.** Okidata Printers may use SSD (pin 11) instead.***Some printers require DSR. If DSR is required, it should be either wired or the printer set to ignore DSR(DSR Invalid).

Important: Other terminal or printer manufacturers may use different methods of flow control. Consult yourprinter documentation for specific wiring requirements.

RJ-45 8-Pin to Modem (ALTPIN option)

The following table shows how to build an 8-wire modem cable using an 8-pin RJ-45 plug. This cable supportsthe Digi ALTPIN option when plugged into a Digi RJ-45 serial port.

8-Wire Modem Cable Supporting ALTPIN Option

RJ-45(Digi End)

DB-25 Male(Modem End)


DCD 1 connected to 6 DCD

RTS 2 connected to 4 RTS





CTS 7 connected to 5 CTS

DTR 8 connected to 20 DTR

When ALTPIN is enabled, DCD becomes available on pin 1 of an 8-pin RJ-45 connector (equivalent to pin 2 ofa 10-pin connector).

Note: ALTPIN is not supported for the PortServer product under Windows NT. Use a full 10-wire modemcable in this case.

RJ-45 10-Pin Plug to DB-25 Modem Cable

The simplest way to connect a modem to a Digi RJ-45 jack is to use a Digi RJ-45 to DB-25 cable adapter. Thefollowing table shows how to apply the adapter wiring scheme to custom modem cables.

RJ-45 to DB-25 Modem Cable (10 Wire)

RJ-45(Digi End)

DB-25 Male(Modem End)


RI 1 connected to 22 RI

DSR 2 connected to 8 DSR

RTS 3 connected to 4 RTS





CTS 8 connected to 5 CTS

DTR 9 connected to 20 DTR

DCD 10 connected to 6 DCD

General EIA-422 Cable Information

This section applies to Digi products equipped with EIA-422 asynchronous interfaces.

Physical Cable Characteristics

EIA-422 interface cables should be shielded twisted-pair cables. Each signal requires two leads (one twistedpair of wires) to complete a balanced voltage digital circuit. The shield should be connected to the ChassisGround of the devices at both ends of the interface cable.

EIA-422 Interface Signaling

The EIA-422 interface provides four signals: Transmitted Data (TxD), Received Data (RxD), Request To Send(RTS) and Clear To Send (CTS). The functions of these signals are identical to their EIA-232 counterparts.

EIA-422 Grounding Requirements

EIA-422 interface cables must provide a ground path between the devices to be connected. This ensures theintegrity of data transfers and control signals. This should be connected to the Chassis Ground of each device.Digi recommends using the cable shield for this purpose.

DB-9 and DB-25 Connector Wiring for Digi EIA-422 Adapters

A terminal, a serial printer, or a serial port for another computer usually functions as a DTE device. The Digiadapter is also a DTE device. To connect a DTE device to another DTE device a null modem cable or adaptermust be used.

Two wires (one twisted pair) are required for each signal, a positive lead ("+"), and a negative lead ("-"). The"+" leads at one end of the cable must be connected to the "+" leads at the other end, and the "-" leads at oneend must be connected to the "-" leads at the other end.

Incorrect wiring could result in damage to the connected devices. The following table shows the pinconfigurations for the EIA-422 versions of Digi DB-9 and DB-25 connectors.

Signal Description DB-9 Pin DB-25 Pin

TxD+ Transmitted Data (+) 8 2

TxD- Transmitted Data (-) 9 14

RxD+ Received Data (+) 6 3

RxD- Received Data (-) 7 16

RTS+ Request To Send (+) 2 4

RTS- Request To Send (-) 3 19

CTS+ Clear To Send (+) 4 5

CTS- Clear To Send (-) 5 13

GND Chassis Ground Shell Shell

EIA-422 Software Handshaking (XON/XOFF) Cable

Use the chart below as a guide for EIA-422 wiring. Pin numbers have been omitted because they vary fromproduct to product. For Digi pin numbers, see Digi EIA-422 Pinouts. For peripheral device pin numbers, see thedocumentation for your peripheral device.

DTE (Digi End)

DTE (Peripheral)

Signal Lead Lead Signal

TxD+ Connected to +

RxD- Connected to -

RxD+ Connected to +

TxD- Connected to -

GND Connected to GND

RTS Jumpered, connect:RTS(+) to CTS(+);RTS(-) to CTS(-)

Jumpered, connect:RTS(+) to CTS(+);RTS(-) to CTS(-)

RTS

CTS CTS

EIA-422 Hardware Handshaking (Ready/Busy) Cable

Use the following table as a guide for EIA-422 wiring. Pin numbers have been omitted because they vary fromproduct to product. For Digi pin numbers, see Digi EIA-422 Pinouts. For peripheral device pin numbers, see thedocumentation for your peripheral device.

DTE (Digi End)

DTE (Peripheral)


TxD + Connected to + RxD

- Connected to -

RxD + Connected to + TxD

- Connected to -

RTS + Connected to + CTS

- Connected to -

CTS + Connected to + RTS

- Connected to -


EIA-422 DTE to DCE (Modem) Cable

Use the chart below as a guide for EIA-422 modem wiring. Pin numbers have been omitted because they varyfrom product to product. For Digi pin numbers, see Digi EIA-422 Pinouts. For modem pin numbers, see yourmodem's documentation.

DTE (Digi End)

DCE (Modem)


TxD + Connected to + TxD

- Connected to -

RxD + Connected to + RxD

- Connected to -

RTS + Connected to + RTS

- Connected to -

CTS + Connected to + CTS

- Connected to -


Resetting a PortServer

Use this troubleshooting procedure when AC does not display on your PortServer and you need to reset thePortServer to the factory defaults.

Important: You will lose all PortServer settings when you reset your PortServer to factory defaults. If you havea complex configuration, call Digi Technical Support for assistance.

Procedure

Power on while simultaneously pressing both arrow buttons on the front of the PortServer.1.

Hold these buttons down until EP is displayed on a PortServer I or CL is displayed on a PortServer II.2.

Reboot the PortServer.3.

If AC appears, reconfigure the PortServer. 4.

If AC still appears, choose Back to return and continue with the Master Troubleshooting Process.

If AC doesn't appear, make note of the status of the LED display on the front of the PortServer andcontact Digi Technical Support.

5.

Documents

RealPort Setup: HP-UXdocs/external/realport/rp-hpux.pdfThe HP-UX RealPort driver supports versions 10.10 or later of the operating system. It will not work with earlier versions. Once