SWAN Concentrator and WAN Subsystem Troubleshooting Guide

Verifying the SWAN Hardware
SWAN Concentrator and WAN Subsystem Troubleshooting Guide—426992-008
4-5
Error IDs related to OSM or TSM Test Action Failure
b. Verify that the ServerNet addressable controllers (SACs) for each E4SA,
FESA, GESA, or G4SA are in the STARTED state by using the SCF STATUS
SAC command:
STATUS SAC $ZZLAN.adapter-name1.*
STATUS SAC $ZZLAN.adapter-name2.*
Verifying That the SACs for a LAN Adapter Are Started on page A-21 shows
the output of this command.
c. Verify that the physical interfaces (PIFs) used by the SWAN concentrator on
each E4SA, FESA, GESA, or G4SA are in the STARTED state by using the
SCF STATUS PIF command:
STATUS PIF $ZZLAN.adapter-name1.pif-name1
STATUS PIF $ZZLAN.adapter-name2.pif-name2
Verifying That a PIF is Started on page A-22 shows the output of this
command.
d. Verify that the logical interfaces (LIFs) used by the SWAN concentrator on
each E4SA, FESA, GESA, or G4SA are in the STARTED state and that the
access state is UP by using the SCF STATUS LIF command:
STATUS LIF $ZZLAN.lif-name1
STATUS LIF $ZZLAN.lif-name2
Verifying That a LIF is Started on page A-23 shows the output of this
command.
2. Restart any E4SA, FESA, GESA, or G4SA objects that are not in the STARTED
state.
a. If an ADAPTER object is not in the STARTED state, use the SCF START
ADAPTER command with the SUB ALL option. This command starts the
subordinate SAC and PIF objects.
START ADAPTER $ZZLAN.adapter-name, SUB ALL
b. If one or more of the LIF objects are not in the STARTED state, use the SCF
START LIF command:
START LIF $ZZLAN.lif-name
3. Verify that the TCP/IP stacks that support the SWAN concentrator are operational.
a. Verify that the preferred and alternate TCP/IP processes are in the STARTED
state by using the SCF STATUS PROCESS command:
STATUS PROCESS $pref-tcpip-process
STATUS PROCESS $alt-tcpip-process
Verifying That a TCP/IP Process is Started on page A-24 shows the output of
this command.