HP-UX SNAplus2 R7 Administration Guide

Defining Connectivity Components
Defining Link Stations
The DTE address of the remote DTE as a series of hexadecimal digits (only applicable if the circuit is a
switched virtual circuit).
Adapter/Port Number
The card number (if your card has only one port). If you have only a single card, use a value of 0.
If your card has more than one port, use the value npx, where n is the card number and x is the port number.
Cards are numbered starting at 0; ports are numbered starting at 1. For example, the first port on the first
card should be specified as 0p1.
To determine the card and port number to use, use a string that matches the end of the device name of the
X.25 driver. For example, use an adapter/port number of 0p1 for an X.25 driver named /dev/x25_0p1.
Additional Link Station Parameters for Enterprise Extender (HPR/IP)
Remote IP host name
Remote host name of the destination node for this link. This can be specified as a dotted-decimal IP address
(such as 193.1.11.100), as a name (such as newbox.this.co.uk), or as an alias (such as newbox).
If you specify a name or alias, the HP-UX system must be able to resolve this to a fully quali
fied name (either
using the local TCP/IP configuration or using a Domain Name server).
Parameters for Independent LU Traffic
You need the following information to configure this link station for use by independent LUs (LUs of type 6.2 for
use by APPC, 5250, or CPI-C applications):
Remote node name
The fully qualified CP name of the remote node.
If the remote system is a VTAM host, you can find the network name (the first eight characters of the
fully qualified name) in the NETID parameter of the VTAM start list. The last eight characters are in the
SSCPNAME parameter of the VTAM start list.
Note
If you enter the name of a new remote node, you can add a definition for the remote
node to enable you to define partner LUs on the new remote node. If the local node
is a LEN node, you do not need to specify the remote node type, and the Remote
node type field does not apply.)
To define a new remote node in this way, specify the remote node type as a value
other than Discover, as well as specifying the remote node name.
Alternatively, you can specify Discover and leave the remote node name empty.
This means that any adjacent node can use the link station. The Discover option
is not available if the local node is a LEN node.
Remote node type
The level of APPN support on the remote node that is accessed through this link station (only applicable if
the local node is an end node or network node).
If you do not know whether the remote node is a LEN node or end node or whether it is a network node, you
can choose Discover. Discovering the level of APPN support on the remote node can delay link activation
slightly, so if you do know the type it is better to specify it. This also helps to ensure network configuration
consistency.
You cannot choose Discover if the link station is activated on demand.
If the local node is a LEN node, this field does not apply.
Branch link type
95