Configuring and Managing Host-Based X.25 Links - Edition 6 (36939-90057)

Introduction
Configuring PAD Support and PAD Security
Chapter 1
27
Configuring PAD Support and PAD Security
This section contains the principles of configuring a DTC for PAD connections, and gives
examples of how to configure certain connections. X.25 levels 1, 2, and 3 must be
configured for PAD Support to function.
DTC PAD support allows terminals connected to remote PADS to access LAN-based
systems via the DTC, and LAN-based systems to access printers connected via DTC to
remote PADs. Security lists can be implemented to prevent access by unauthorized PAD
devices.
Three tables are used to control access to and from PAD devices.
Configuring DTC PAD Access Information
The PAD Access screen lists device names or numbers of remote PAD devices with X.25
addresses, closed user group (CUG) numbers and device profiles. The list enables an
incoming call to be tied to a nailed ldev on an MPE/iX system or PAD device access via
the HP DTC Device File Access (DDFA) software on the HP-UX system.
Refer to the network subscription form for the CUG number. If the CUG number entered
here does not correspond to your network subscription, calls will be cleared by the
network with the message CLR DTE 70. Note that CUG is a PSN service, and is not
configurable from the DTC Manager.
Example of PAD Access
In this example:
•The DTC is a managed DTC on System MPE_A
•The DTC is a non-managed DTC or System MPE_B
• LDEV 109 is a nailed terminal, and the PAD Device Name P1A1 has been associated
with it in NMMGR on the HP 3000 Series 900
• LDEV 110 is a nailed printer, and the PAD Device Name P1A2 has been associated
with it in NMMGR on the HP 3000 Series 900
• The address of the remote PAD Terminal 1234501 is mapped to the PAD Device
Name P1A1 in the PAD Access List