Similarly, on the NESiGate ESCON board, a "Device Index" is defined as a Unit Address on a Logical
Control Unit (up to 16 may exist). The Physical Control Unit may be connected to a Port on an ESCON
Director, which may provide connectivity to multiple LPARs across multiple hosts.
Since both the Device Number and Device Index represent the same unique device (from different per-
spectives), the same addressing components must be specified
exactly the same
in both definitions.
Failure to do so will prevent the NESiGate devices from functioning properly.
When defining devices on the ESCON channel board, the following items are specified: Device Unit
Address, Logical Control Unit, the Director port to which the host channel is connected, and Partition-id
(LPAR). The Device Index values are not specified by the user. They are automatically generated
when the channel configuration is defined.
A maximum of 64 devices are supported on each ESCON interface.
Refer to the “Channel Define Interface” button on page 15 for a description of defining the channel de-
vices.
Conflicts and illogical configurations may be accepted as input (to the web or CLI), however that does
NOT mean they will work (i.e. overlapping subchannel addresses, incorrect CUs, etc.). The channel
configuration in the NESiGate must match the (gen'ed) configuration in the host.
GNA Address
The GNA address represents a NetEx/IP network address that is associated with a given device. It is
specified in the NetEx/IP Network Configuration Table (NCT). It is also specified during the customi-
zation of the NESiGate Channel Driver. At that time, an association is established between a particular
GNA address and a Device Index.
IP Address
The IP address represents a NetEx/IP network node address. There is no channel device awareness in-
herent in an IP address. However, during the NESiGate configuration, IP host names are defined, each
having a format based on its GNA address. This enables NESiGate to perform a direct mapping be-
tween GNA and IP addresses. This mapping is transparent to the NetEx/IP running on the host, as well
as to all NetEx/IP applications.
Page
4
Customization
MAN-REF-COSW 2.10-19
