SWAN Concentrator and WAN Subsystem Troubleshooting Guide

Verifying the WAN Subsystem
SWAN Concentrator and WAN Subsystem Troubleshooting Guide—426992-008
3-2
Verifying the WAN Subsystem Processes and
Objects
b. Verify that the SUBNETS associated with the LIFs used by the SWAN
concentrator are in the STARTED state by using the SCF STATUS SUBNET
command:
STATUS SUBNET $tcpip-process.#subnet
Verifying That a TCP/IP SUBNET is Started on page A-25 shows the output of
this command.
c. Verify that the routes on the preferred and alternate TCP/IP processes are in
the STARTED state by using the SCF STATUS ROUTE command:
STATUS ROUTE $<tcpip-process>.*
Verifying That a TCP/IP Route is Started on page A-26 shows the output of this
command.
4. Verify that the E4SAs, FESAs, GESAs, or G4SAs to which the SWAN concentrator
is connected are operational.
a. Verify that the ADAPTER object for each E4SA, FESA, GESA, or G4SA is in
the STARTED state by using the SCF STATUS ADAPTER command for the
SLSA subsystem:
STATUS ADAPTER $ZZLAN.adapter
Verifying That the ADAPTER Object for a LAN Adapter is Started on
page A-20 shows the output of this command.
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.*
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.pif-name
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-name
Verifying That a LIF is Started on page A-23 shows the output of this
command.