dp(4)dp(4)NAMEdp - dedicated ports file used by DDFA software and Telnet port identi‐
The file has two uses:
The file is used by the Datacommunications and Terminal Con‐
troller Device File Access (DDFA) software to allow ter‐
minal server ports to be programmatically accessed from
HP-UX applications in the same way as devices connected
directly to the HP-UX system. It contains a one-line
entry for each configured terminal server port.
The file contains the information the DDFA software needs
to set up and manage an outbound connection to a speci‐
fied terminal server port. The file is parsed by the
Dedicated Port Parser which spawns an Outbound Connection
Daemon for each outbound connection specified in the
The file is used by the HP-UX telnet daemon to identify the
calling port and board of a telnet connection from an HP
Datacommunications and Terminal Controller (DTC).
At connection time, the host negotiates the telnet envi‐
ronment option and the DTC replies with the port and
board number of the connecting device. maps the port and
board numbers to the well-known name for the device,
which has previously been configured in the file.
Datacommunications and Terminal Controller Device File Access
For outbound connections, an entry should have the following format:
The exact details of each field are given below.
Telnet Port Identification
To configure the file for using the Telnet port identification feature,
the default file should be copied to a new file and the copy configured
with the appropriate values for the incoming connections. The recom‐
mended procedure is to create a directory to hold the file and the mod‐
ified port configuration files.
An entry for this purpose should have the following format:
The exact details of each field are given below.
There are three ways to specify a terminal server port:
· Explicitly specify its IP address.
· Specify the node name or the IP address of the DTC then spec‐
ify the board and port.
· Specify the node name or the IP address of the terminal
server and the TCP port service address of the port.
Comments in the file can be appended by starting them with a character.
Everything after the is ignored by the parser. Fields in the file are
separated by space characters.
See ddfa(7) for more information on how to configure the DDFA software.
The fields of an entry of the file are as follows:
dtc_name This field is the node name or the IP address of the
terminal server being accessed or the IP address of
the port on the terminal server. A node name must be
defined in a name database.
This field contains the terminal server port address with the parts
separated by the character. It is not necessary to
pad the values with leading zeros. The port address
is not checked by but is checked by Valid values are
0 through 7 for board, and 0 through 31 for port
(these restrictions do not apply if the TCP port ser‐
vice address is specified instead).
If the dtc_name field explicitly defines the node
name or the IP address of the terminal server port,
the value in the field must be (use or
If the field is of the form where n is a decimal num‐
ber, n is assumed to be the TCP port service address
and it is used when the connection is established.
pseudonym This field is the absolute path of the device file
known to the system and the end-user application.
The device file name portion of the path name is lim‐
ited to 14 characters.
pc_file_path This field is the path to a port configuration file
which contains the configuration information for the
terminal server port. This field is mandatory for
outbound connections as uses the presence of this
field as its flag to spawn a daemon for the entry.
log_level This field is the logging level for the particular
and it determines the severity of messages sent to
The logging levels (and how they relate to system
logging levels) are as follows:
Log only LOG_CRIT messages.
Log only LOG_CRIT and LOG_ERR messages.
Log only LOG_CRIT, LOG_ERR, and LOG_WARNING mes‐
Log all messages.
It is optional and may only be specified for outbound
connections. If it is omitted, the logging level is
set to 1.
The following examples illustrate file entry syntax.
A printer is connected to port 1 of board 3 of a DTC with the IP
address 188.8.131.52. The device attached to the port can be accessed
with the HP-UX spooler by using the device file
A printer is connected to a terminal server port with IP address
184.108.40.206. The field contains The device attached to the port can
be accessed with the HP-UX spooler by using the device file
A printer is connected to a port accessed with TCP port service address
5001 of a terminal server with the IP address 220.127.116.11. The
device attached to the port can be accessed with the HP-UX spooler by
using the device file
A terminal is connected to port 1 of board 2 of a DTC with the IP
address 18.104.22.168 and wishes to use Telnet port identification.
In order to ensure that commands (such as ps) display the correct
device file name (that is, the pseudonym), all pseudonyms should be
placed into the directory If pseudonyms are not specified for placement
in this directory, the correct display of device file names with many
commands is not guaranteed.
In addition, in order to ensure that commands (such as and work cor‐
rectly, each pseudonym must be unique in its first 17 characters
(including the directory prefix If pseudonyms are not unique in their
first 17 characters, the correct functioning of many commands is not
FILESSEE ALSOdpp(1M), ocd(1M), ocdebug(1M), syslog(3C), pcf(4), ddfa(7).