HP Rp3440-4 - 9000 - 0 MB RAM User manual

HP 9000 Computers
DTC Device File Access
Utilities and Telnet P
ort
Identification
ABCDE
HP Part No. B1030-90002
Printed in U.S.A. 01/95
Edition 2
E0195

Legal Notices
The information in this document is sub ject to c
hange
without notice.
Hew lett-Packar
dmakes no warr
anty of any kind with
r
e
gar
dto this material, including, but not limite
dto, the
implie
dwarr
anties of mer
chantability and tness for a
p
articular purp
ose.
Hewlett-P
ac
k
ard shall not beliable
for errors con
tained herein or direct, indirect, special,
inciden
tal, or consequen
tial damages in connection with
the furnishing, performance, or use of this material.
W
arran
t
y
.
Acop
yof the specic w
arran
t
yterms
applicable to y
our Hewlett-P
ac
k
ard pro duct and
replacemen
tparts can beobtained from your local Sales
and Service oce.
Restricted Rights Legend.
Use, duplication or disclosure
b
ythe U.S. Go
v
ernmen
tis sub ject to restrictions as
set forth in subparagraph (c) (1) (ii) of the Righ
ts in
T
ec
hnical Data and Computer Soft
w
are clause at DFARS
252.227.7013 for DOD agencies, and subparagraphs (c)
(1) and (c) (2) of the Commercial Computer Soft
w
are
Restricted Righ
ts clause at F
AR 52.227-19 for other
agencies.
HEWLETT-P
A
CKARD COMP
ANY
3000 Hano
v
er Street
Palo Alto, California 94304 U.S.A.
Use of this man
ual and exible disk(s) or tap e
cartridge(s) supplied for this pac
k is restricted to this
pro duct only
. Additional copies of the programs ma
ybe
made for securit
y and bac
k-up purposes only
. Resale of
the programs in their presen
t form or with alterations, is
expressly prohibited.

Copyrigh
t Notices.
(c)cop
yrigh
t1979, 1980, 1983,
1985-93 Regen
ts of the Univ
ersit
yof California
This soft
w
are is based in part on the F
ourth Berk
eley
Soft
w
are Distribution under license from the Regents of
the Univ
ersit
yof California.
(c)cop
yrigh
t1980, 1984, 1986 No
v
ell, Inc.
(c)cop
yrigh
t 1986-1992 Sun Microsystems, Inc.
(c)cop
yrigh
t1985-86, 1988 Massac
h
usetts Institute of
T
ec
hnology
(c)cop
yrigh
t1989-93 The Open Soft
ware F
oundation,
Inc.
(c)cop
yrigh
t1986 Digital Equipmen
tCorp oration
(c)cop
yrigh
t1990 Motorola, Inc.
(c)copyrigh
t1990, 1991, 1992 Cornell Univ
ersit
y
(c)cop
yrigh
t1989-1991 The Universit
yofMaryland
(c)cop
yrigh
t1988 Carnegie Mellon Univ
ersit
y
T
rademark Notices
UNIX is aregistered trademark
in the United States and other coun
tries, licensed
exclusiv
ely through X/Open Compan
yLimited.
XWindo
wSystem is atrademark of the Massac
h
usetts
Institute of Tec
hnology
.
MS-DOS and Microsoft are U.S. registered trademarks of
Microsoft Corp oration.
OSF/Motif is ais a trademark of the Op en Soft
w
are
F
oundation, Inc. in the United States and other
countries.
c
 Copyright 1995, Hewlett-Packard Company.

Printing History
The man
ual prin
ting date and part n
um
ber indicate its
curren
tedition. The prin
ting date will c
hange when a
new edition is prin
ted. Minor c
hanges ma
ybemade at
reprin
twithout c
hanging the prin
ting date. The manual
part n
um
ber will c
hange when extensiv
ec
hanges are
made.
Man
ual updates ma
ybeissued bet
w
een editions to
correct errors or documen
tpro duct c
hanges. T
o ensure
that y
ou receiv
ethe updated or new editions, y
ou should
subscribeto the appropriate pro duct supp ort service.
See y
our HP sales respresen
tativ
e for details.
Edition 2
Jan
uary 1995 (HP-UX Release 10.0)
iv

Contents
1. In
tro duction
In
tended Audience ..........1-2
Prerequisites .............1-2
Supported Congurations .......1-3
Related HP Do cumen
tation ......1-5
2. Ov
erview of DDF
AAnd T
elnet P
ort Iden
tication
How DDF
AUtilities W
ork .......2-2
Ho
wT
elnet P
ort Iden
tication W
orks ..2-5
Ho
wDevice Files Are Handled By MUXes
and DTC T
erminal Serv
ers .....2-5
Setting Up Outgoing and Incoming
Connections ...........2-6
DDF
AFile Directories and Setup ....2-9
3. Conguring DDF
AConnections
DDFAMaster Files . . ........3-1
Related Conguration T
asks .... . . 3-3
DDF
AConguration T
asks ......3-4
Conguring Outgoing Connections
(Prin
ters) . . . . . . . . . . . . 3-5
Conguring Incoming Connections
(Terminals) . .. . . . . . . . . 3-8
Starting Up the o cd Daemons . . . . 3-9
Contents-1

4. Dening and Executing DDF
AP
arameters
Using Dedicated P
orts .........4-1
The Dedicated P
ort File, dp . . . . . .4-2
The P
ort Conguration File, pcf ....4-4
Managing Outgoing Dedicated P
orts With
dpp and ocd .. . . . ......4-9
Preparing to Use dpp ........4-11
Using dpp to Kill and Restart ocds ..4-12
Using dpp to Start Up New o cds . ..4-12
Using dpp to Remo
v
eExisting ocds ..4-12
Managing Incoming Connections b
ytelnetd 4-13
Using dpp to Update T
elnet P
ort
Identication Info . . . .....4-13
5. Application Examples
Setting Up Prin
ters with the HP-UX
Spooler ............. . 5-1
HP-UX Spooler Example ......5-2
Accessing DTC or non-DTC P
orts
Programmatically .........5-3
Conguring Incoming Connections for
CSLIP/SLIP .. . . . ......5-5
6. Simple DDF
AT
roubleshooting
Troublesho oting Chec
klist . ......6-2
T
roublesho oting Outgoing Connections .6-3
Chec
kfor Syn
tax Errors .......6-3
Check for Incorrect Addresses ....6-3
Chec
kT
elnet Operation . . . . . ..6-3
V
erify ocd .... . ........6-4
Checkthe pty . . . . . . . . . . . 6-4
Check System Lev
el Data P
ath . . . . 6-4
Troublesho oting Incoming Connections .6-5
If You Ha
ve to Call Hewlett-P
ackard . 6-6
Contents-2

A. Appendix A: dpp Error Messages
B. Appendix B: ocd Logging Messages
Critical Messages . . . . . ......B-2
Serious Messages ...........B-7
W
arning Messages ...... . . . .B-19
Informational Messages . . . .....B-26
Index
Contents-3

Figures
2-1. HP 9000 and DTC In
teraction With
DDF
A.............2-4
2-2. Incoming Connection Using T
elnet P
ort
Iden
tication ......... . 2-8
Contents-4

1
Introduction
This man
ual explains ho
wto use the DTC Device
File Access Utilities (DDF
A) and the T
elnet P
ort
Iden
tication feature to comm
unicate with HP 9000
serial devices connected to net
w
ork terminal serv
ers suc
h
as the HP Datacommunications and T
erminal Con
troller
(DTC). DDF
Afacilitates the use of pseudoterminal
(pt
y) device les to open outgoing T
elnet connections
to the DTC or other terminal serv
er, while T
elnet P
ort
Iden
tication uses them to establish incoming T
elnet
connections from kno
wn devices on the serv
er. T
elnet
is one of the HP 9000 In
ternet Services (HP B1030B),
formerly kno
wn as the HP 9000 ARP
AServices.
DDF
Aw
as originally designed for use with DTCs, but as
of HP-UX 10.0, it can no
wbeused with other terminal
serv
ers whic
huse addressing schemes similar to the
DTC. There will besome guidelines on ho
wto congure
DDF
Afor use with non-DTC terminal serv
ers, but the
DTC will be used as the primary example throughout
this man
ual.
In addition, there is general discussion on the topic of
pt
yuse with HP DTC terminal serv
ers v
ersus the HP
MUX, and ho
w to troublesho ot incoming and outgoing
DDF
A connections.
Introduction 1-1

Intended Audience
This man
ual is in
tended for at least three t
ypes of users:
The HP 9000 system administrator or net
work
administrator who denes and congures the device
les asso ciated with DTC and other terminal serv
er
devices on the system.
The HP 9000 system operator or net
w
ork operator
who ma
yimplemen
tthe actual tasks set up by the
system or net
w
ork administrator.
The applications programmer who needs programmatic
con
trol of devices on the DTC or other terminal serv
er
using standard HP-UX input/output calls suc
has
open
,
close
,
io ctl
,
read
,and
write
.This programmer
ma
y also ha
v
eapplications using devices connected to
MUX ports and wishes to extend the application to
use DTC devices.
Prerequisites
Before reading this man
ual and using this soft
w
are, y
ou
should befamiliar with ho
wto:
Handle HP-UX operating system and system
administration, especially with devices and device les.
Congure aDTC
with either the DTC Manager/UX
pro duct (HP J2120A) or the OpenView DTC Manager
pro duct on the PC (HP D2355A).
Congure and administer other terminal serv
ers.
Program devices and use device les for
pseudoterminals (pt
ys) or MUXes.
Access on-line DDF
Aman pages on y
our system like
ddfa(7), dp(4), dpp(1M), ocd(1M), o cdebug(1M), as
well as io ctl(2), io ctl(5), p cf(4), and termio(7).
1-2 Introduction

Supported
Configurations
There are sev
eral t
ypes of soft
w
are and hardware
pro ducts and services used in conjunction with DTC
Device File Access Utilities. Refer to the \Related HP
Do cumen
tation" section for more information.
HP-UX operating system v
ersion .The DTC Device
File Access Utilities are included with HP-UX
v
ersion 9.0 and later. The DDF
AUtilities consists of
executable les, default conguration les and man
ual
reference pages.
In
ternet Services.
DDFA is an extension of the T
elnet
service. Because T
elnet is one of the Internet Services
(HP B1030B), DDF
Ais automatically installed and
requires Internet Services and the LAN Link to be
congured and operating prop erly
.
HP 9000 Series 700 and 800 systems.
The DDF
A
Utilities are supported only on HP 9000 Series 700
and 800 systems. Because these systems ha
v
eIn
ternet
Services as part of their HP-UX system, these systems
also ha
v
eDDF
Ainstalled.
DTC Manager/UX or OpenView DTC Manager.
The
HP DTCs whic
haccess an HP 9000 Series 800 are
congured and managed b
yeither the host-based
HP
DTC Manager/UX
(HP J2120A) or the PC-based
Op
enView DTC Manager
(HP D2355A). The
PC-based OpenView DTC Manager also congures
and manages DTCs whic
haccess HP 9000 Series 700
systems and HP 3000 systems. The v
ersion for DTC
Manager/UX should b e A.04.00 or later. The v
ersion
of the OpenView DTC Manager should be A.14.10 or
later. The v
ersion for DTC 16RX Manager/UX should
be A.04.00 or later.
Printers and plotters.
DDFA Utilities can be used
with the HP-UX sp o oler for prin
ters and plotters for
which a mo del script exists., and are supported for use
with HP DTCs.
Introduction 1-3

T
erminals.
An
yterminal supported for use with HP
DTCs is also supported.
Mo dems.
An
ymo dem supported for use with HP
DTCs is also supported.
HP DTCs.
The following DTCs are supported on HP
9000 systems:
HP 2340A -DTC 16 with 16 ports.
HP 2360A -DTC 16TN with 16 ports.
HP 2363A - DTC 16MX with 16 ports.
HP 2364A -DTC 16RX with 16 ports.
HP 2345A -DTC 48 with 48 p orts.
HP 2370A -DTC 72MX with 72 ports.
Other T
erminal Serv
ers.
DDF
AUtilities can beused
with non-HP terminal serv
ers whichuse addressing
sc
hemes similar to the DTC. Ho
w
ev
er, in order to
w
ork, the individual user m
ust perform three tasks:
(a) Congure the non-DTC terminal serv
er ports for
use with the DDF
Apro duct. (b) Congure DDFAfor
use with non-DTC ports, and (c) T
est whether this
particular terminal server conguration w
orks correctly
with DDF
Abefore calling HP
.
The user m
ust follo
wtheconguration guidelines
discussed in this man
ual, as w
ell as those given by
the specic terminal serv
er v
endor in order for HP to
support the DDF
Ain
terface.
1-4 Introduction

Related HP
Documentation
HP-UX System man
uals:
HP-UX System A
dministration Tasks
(the HP part
num
ber is dieren
tfor eac
hof the HP 9000 systems)
Instal ling HP-UX 10.0
(the HP part n
um
ber is
dieren
tfor eachof the HP 9000 systems)
LAN and Internet Services man
uals:
Instal ling and A
dministering Internet Servic
es
(B1030-90000)
Instal ling and A
dministering LAN/9000
(98194-90050)
Using Serial Line IP Pr
oto
c
ols
(98194-90051)
DTC Manager man
uals:
Using HP Op
enView DTC Manager
(D2355-90001) for
the PC-based DTC manager.
Using HP Op
enView DTC Manager/UX
(J2120-62000) for the host-based DTC manager for HP
9000s.
Using DTC 16RX Manager
(J2496-90000) for the
DTC 16RX manager.
Introduction 1-5

2
Ov
erview of DDF
AAnd T
elnet P
ort Identification
This c
hapter giv
es abrief o
v
erview of DTC Device File
Access (DDF
A) Utilities and T
elnet P
ort Iden
tication.
Read this c
hapter to learn ho
wDDF
Aand T
elnet
P
ort Iden
tication w
ork, and ho
wdevice les are
used to comm
unicate with devices attac
hed to DTCs
and other terminal serv
ers. Chapters 3, 4, and 6
pro
vide information on conguring, executing and
troublesho oting DDF
Aconnections to DTCs and other
terminal serv
ers.
This pro duct enhances and supplemen
ts the T
elnet
proto col by pro
viding the following benets:
DDF
Amak
es accessing devices attac
hed to DTCs or
other terminal serv
ers lik
eaccessing MUX devices.
DDF
A Utilities allo
wthe system administrator to
set up acorresp ondence b etw
een these DTC p orts
and HP-UX device les. With this corresp ondence
dened, the system spooler or auser application can
manipulate w
ell-known device les to read and write
to specic serv
er ports.
DDF
A allows the HP-UX Spooler for prin
ters
attac
hed to DTCs or other serv
ers to becongured
in SAM.
After the corresp ondence bet
ween prin
ters
on a DTC and HP-UX device les has been set-up,
SAM (System Administration Managemen
t to ol) can
be used to congure the spo oler for DTC-connected
printers as w
ell as for MUX-connected prin
ters. The
only dierence is that the pt
y device le name of the
DTC prin
ter m
ust b e used instead of a tt
y name for
Overview of DDFAAnd Telnet Port Identification 2-1

a MUX printer. In fact, the standard spooler mo del
scripts can beused with serv
er prin
ter(s).
DDF
Aallows user applications to access devices
attached to DTC and other terminal serv
ers
using standard HP-UX system calls.
After the
corresp ondence betw
een DTC devices and HP-UX
device les has been set up, user applications can use
the standard HP-UX
read
,
write
,
open
,
close ,and
io ctl
calls. These calls access the devices b
ymanipulating
their corresp onding device les.
T
elnet P
ort Iden
tication lets the system
administrator ensure that incoming T
elnet connections
from sp ecic DTC ports will beassigned to specic,
rather than random pt
ydevice les.
DDF
AUtilities and T
elnet P
ort Iden
tication c
annot
be
used sim
ultaneously on the same device le, since they
pro
vide separate functionalit
y
.Ho
w
ev
er, they ma
ybe
used on the system at the same time.
HowDDF
AUtilities
W
ork
The DTC Device File Access Utilities are a group of
conguration les, executable les and one or more
daemons. Together these utilities allowthe HP 9000
system administrator to set up logical pairs of pty
device les and ph
ysical ports on the DTC or other
serv
er. Once this is done, the serv
er's pt
ydevices can be
accessed in the same w
a
yas MUX-connected tt
y devices
can.
These pt
ys can b e assigned to \incoming" connections
or to \outgoing" connections. Incoming connections to
the system are initiated b
y input devices attached to the
server (suc
h as terminals), while outgoing connections
are initiated b
y the system to output devices attached
to the serv
er (usually prin
ters). When an application on
2-2 Overview of DDFA And Telnet Port Identification

the system op ens one of these device les, the DDF
A
Utilities transparen
tly manage the creation of aT
elnet
connection to the asso ciated server port and its device.
Congure and execute the DDFAUtilities in tw
osimple
steps:
1. Edit the Dedicated P
ort conguration le (
dp
)to
add an entry for eac
hph
ysical terminal serv
er port
whic
hdescribes the asso ciation to aunique pt
ydevice
lename.
2. Run the Dedicated P
ort P
arser program (
dpp
)to
parse the dp le and to execute an
ocd
pro cess for
eac
houtgoing connection dened in the dp le.
Eac
htime the HP-UX system initiates an outgoing
connection to apre-dened terminal serv
er port, its
unique Outgoing Connection Daemon (
ocd
)becomes
activ
e. It then establishes the T
elnet connection and
manages it un
til the connection is closed.
Figure 2-1 sho
ws howthe system, the DTC terminal
serv
er, and the DDF
AUtilities in
teract with one
another.
Overview of DDFAAnd Telnet Port Identification 2-3

Figure 2-1. HP 9000 and DTC Interaction With DDF
A
2-4 Overview of DDFA And Telnet Port Identification

Ho
wT
elnet P
ort
Identification
W
orks
T
elnet P
ort Iden
tication is made possible b
yasetof
enhancemen
ts to the T
elnet daemon (
telnetd
), whic
his
part of In
ternet Services. In earlier v
ersions of T
elnet,
incoming connections, including those coming from a
DTC serv
er, were alwa
ys assigned pt
ydevice les on a
random basis.
In
ternet Services T
elnet allo
ws the system administrator
to set up pre-dened pt
ynames dened in the DDF
A
dedicated port le,
dp
.In addition, the DTC do
wnload
co de w
as enhanced so that it will deliv
er board and
port information to the host (via Telnet) at connection
establishmen
ttime. The host will map the incoming
connection to its pre-dened pt
ydevice le, thereb
y
pro
viding a\dedicated port" b
ywhic
hthe iden
tityof the
caller can bedetermined. The Telnet P
ort Iden
tication
feature is a
v
ailable with HP-UX and DTCs, but ma
ynot
becompatible on other serv
ers.
Ho
wDevice Files
Are Handled By
MUXes and DTC
T
erminal Serv
ers
Recall that adevice le is an HP-UX le that \poin
ts"
to asystem device. The system administrator often uses
the name of the device le when conguring soft
w
are to
access that device. When devices are connected to an
HP-UX MUX (m
ultiplexer), they are assigned to tt
y
device le names. When devices are connected to a
DTC serv
er, they are assigned to
r
andom
pt
ydevice
le names. T
othe user logging on at his terminal from
either a MUX or a DTC, the terminal functions the
same w
ay. The user do es not see ho
w the device le is
assigned to the connection, and whether the MUX driv
er
or the terminal serv
er driver is used.
The HP-UX System Administrator creates a device le
for eac
h MUX p ort, using the HP-UX
insf or mkno d
command. Each device le maps to a sp ecic physical
Overview of DDFA And Telnet Port Identification 2-5

MUX p ort, and device les are named b
ycon
v
en
tion, so
that eac
hiden
ties aunique MUX port. F
or example,
/dev/tt
y2p3
means port 3on
MUX card 2.
Adevice connected to a DTC or other terminal serv
er
comm
unicates with the system via T
elnet. Therefore, it
is considered to bealogical device, and it is serviced b
y
a
pseudoterminal device driv
er (pt
y). It is referenced
using its pt
ydevice le name.
Usually
,this pt
yis assigned to the T
elnet connection
randomly from apool of free pt
ys in the
/dev
directory
or subdirectories at connection setup time. In man
y
cases, the randomness of pty assignmen
ts for T
elnet
users is acceptable, because the ph
ysical lo cation
of the T
elnet user is unimportan
t. In fact, users of
system-to-system T
elnet ha
v
ealw
a
ys been sub ject to
this situation. Ho
w
ev
er, when aspecic DTC device
m
ust alw
a
ys beasso ciated with the same pty
,then the
randomness of pt
yassignmen
ts m
ust beremo
v
ed through
autilit
ysuchas DDF
A.
Starting with HP-UX 10.0, pt
ydevice les for incoming
connections should beassigned to the directory
/dev/telnet
so that they can bemore easily trac
k
ed and
becorrectly displa
y
ed b
ycommands suc
has
ps -ef
.
Setting Up
Outgoing and
Incoming
Connections
Aprin
t job sent from the system to aprin
ter creates an
outgoing connection. When auser logs in at aterminal
on a DTC and receiv
es a system prompt from the host
to complete the login, an incoming connection is created.
Both op erations require the use of a device le name.
Whenever an application on the host needs to access
a MUX device, the application can read and write to
the tt
y device le that b elongs to the MUX device.
However, if an application wants to op en a DTC device,
2-6 Overview of DDFA And Telnet Port Identification