Troubleshooting the SWAN Concentrator and WAN Subsystem

Verifying the WAN Subsystem Processes and Objects
This procedure describes how to verify that the required WAN subsystem processes and objects are
started. It also describes how to verify that the processes and objects that support a ServerNet wide
area network (SWAN) concentrator (for example, Ethernet 4 ServerNet adapters (E4SAs), Fast
Ethernet ServerNet adapters (FESAs), TCP/IP processes, and so forth) are started. If you don't know
the names of the WAN subsystem processes and objects, see Identifying the WAN Subsystem
Processes and Objects.
Note: Angle brackets (for example, <line-name>) are used in command syntax to indicate values
that you must provide.
1 Verify that the WAN manager process is in the STARTED state.
Use the SCF STATUS PROCESS command:
STATUS PROCESS $ZZKRN.#ZZWAN
The example shows the output of this command.
2 Verify that the LAN manager process is in the STARTED state.
Use the SCF STATUS PROCESS command:
STATUS PROCESS $ZZKRN.#ZZLAN
The example shows the output of this command.
3 Verify that the preferred and alternate TCP/IP processes used by SWAN concentrator are
operational.
Use the SCF STATUS PROCESS command to verify that the preferred and alternate
TCP/IP processes are in the STARTED state:
a.
STATUS PROCESS $<tcpip-process>
The example shows the output of the SCF STATUS PROCESS command.
Use the SCF STATUS SUBNET command to verify that the subnets associated with
the LIFs used by the SWAN concentrator are in the STARTED state:
b.
STATUS SUBNET $<tcpip-process>.#<subnet>
The example shows the output of the SCF STATUS SUBNET command.
Use the SCF STATUS ROUTE command to verify that the routes on the preferred and
alternate TCP/IP processes are in the STARTED state:
c.
STATUS ROUTE $<tcpip-process>.*
The example shows the output of the SCF STATUS ROUTE command.