SNAX/XF and SNAX/APN Configuration and Management Manual
Configuring for Ethernet Support
SNAX/XF and SNAX/APN Configuration and Management Manual—425836-006
10-16
Configuration Example
example, PU2, that has an address of 04400011110001 must be connected to PU4 
through SAP %H08, the unique address being 04400011110001,08400011110002.
Note that these restrictions apply only to PU-to-PU connections. There may be many 
LU-LU sessions channelled through a single PU, and LU6.2 further allows multiple 
parallel sessions between two LUs.
Configuration Example
SNAX does not directly control the Ethernet ServerNet adapter. SNAX communicates 
with the QIO process and QIO communicates with the Ethernet adapter. The QIO 
subsystem is preconfigured and it should require no configuration for SNAX. QIO is a 
system process and it should always be running. For information about QIO 
configuration and management, see the QIO Configuration and Management Manual.
The Ethernet adapter is configured when the hardware is installed and it should require 
no configuration for SNAX. You need to know the name of the Ethernet adapter’s line 
interface (LIF) that SNAX will use.
There are only two steps required:
Verify that the Ethernet adapter is ready for communication over the LAN.
Configure the SNAX/XF or SNAX/APN LINE, PUs, and LUs and then start them.
Step One: Verify the Ethernet Adapter’s LIF 
Status
Issue the following SCF commands using the name of the LIF that SNAX will use:
->ASSUME PROCESS $ZZLAN
->STATUS ADAPTER <LIF name>
Verify that the LIF’s State is Started its Access State is Up. If not, correct the problem 
and reissue the STATUS command. For more information, see the Ethernet Adapter 
Installation and Support Guide for the E4SA adapter, the Fast Ethernet Adapter 
Installation and Support Guide for the FESA adapter, the Gigabit Ethernet Adapter 
Installation and Support Guide for the GESA adapter, or the Gigabit 4-Port ServerNet 
Adapter Installation and Support Guide for the G4SA adapter.
Step Two: Configure SNAX 
At the SNAX level you choose SNAX/XF for legacy-style, sub-area communications or 
SNAX/APN for peer-to-peer communication.
This example uses SNAX/APN. This product allows parallel sessions within a single 
LU-LU connection and dynamic configuration of the remote LU.










