Line for downstream connection, Link profile for downstream connection, Local sap – Visara LINCS Configuration User Manual

Page 125: Pu address, Puid override, Data link id

Advertising
background image

107

Chapter 5. Gateway Circuits

707023-003

Line for Downstream Connection

Toggle to the desired Downstream Node line that will carry the data for this circuit.

Link Profile for Downstream Connection

Toggle to the desired Link Profile number to indicate the link type of the downstream connection
of this circuit.

Local SAP

Enter a 2-digit hex SAP address. This is the SAP address of LINCS node for this gateway
circuit. Valid SAP addresses are multiples of 4, ranging from 4 to EC (hex). If Incoming
LANSYS Connections are enabled on this line, SAP 98 (hex) is reserved. SAP E0 (hex) is
reserved for IPX.

PU Address

Enter a 2-digit hex number that matches the downstream node’s PU address. Make sure that
the address you enter is unique for this line.

PUID Override

PUID Override is used if the downstream (DAP) PU does not support the XID command.
LINCS will use the number you put here for XID exchanges with the SNA host.

If the downstream PU does support XIDs, then this field should be left blank.

Data Link ID

The Data Link ID fields are used in conjunction with the IP Address field to uniquely identify
this gateway circuit. These fields uniquely identify incoming TCP/IP frames from other host
or gateway circuits. This address combination must be unique throughout the network.

The data link ID fields require data to be entered in the canonical format for Token Ring, and
non-canonical format for Ethernet, of a LAN Address and a SAP.

The Data Link ID will be taken from the upstream’s Remote LAN Address and Remote
SAP fields if the upstream connection is configured for LLC. If the upstream connection is
configured for TCP/IP, the Data Link ID will be taken from the upstream’s Remote Data
Link ID field. In these cases, the remote addresses used to define the upstream gateway
connection must match the Remote Data Link ID of the corresponding host circuit defined
on the downstream node. Otherwise, the Data Link ID field defined on the downstream
connection of this gateway circuit must match the Remote Data Link ID of the corresponding
downstream node’s host circuit.

The Remote IP address indicates the remote device, and the Remote Data Link ID identifies
the specific circuit on the remote device. The Remote Data Link ID defined in this downstream
connection of the gateway circuit must match the Data Link ID field of the corresponding
downstream node’s host circuit.

Advertising