Troubleshooting the SWAN Concentrator and WAN Subsystem

3 Verify that the NonStop TCP/IP processes that support the SWAN concentrator are
operational.
Use the SCF STATUS PROCESS command to verify that the preferred and
alternate NonStop TCP/IP processes are in the STARTED state:
a.
STATUS PROCESS $<pref-tcpip-process>
STATUS PROCESS $<alt-tcpip-process>
The example shows the output of the SCF STATUS PROCESS
command.
Use the SCF STATUS SUBNET command to verify that the subnets on the
preferred and alternate NonStop TCP/IP processes that are associated with the
LIFs are in the STARTED state:
b.
STATUS SUBNET
$<pref-tcpip-process>.#<subnet-name>
STATUS SUBNET
$<alt-tcpip-process>.#<subnet-name>
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 NonStop TCP/IP processes are in the STARTED state:
c.
STATUS ROUTE
$<pref-tcpip-process>.#<route-name>
STATUS ROUTE
$<alt-tcpip-process>.#<route-name>
The example shows the output of the SCF STATUS ROUTE command.
4 Restart any NonStop TCP/IP processes or objects that are not in the STARTED
state.
If a TCP/IP process no longer exists, you must recreate it using the following
TACL commmand:
a.
TCPIP / NAME $<tcpip-process>, NOWAIT,
CPU <primary-cpu-num>, PRI <priority-num>,
TERM $ZHOME / <backup-cpu-num>
Note: Always run NonStop TCP/IP as a process pair. Otherwise, the
NonStop TCP/IP process loses all LAN access if the data path to the LIF
changes.
If a subnet is not in the started state, use the SCF START SUBNET command:b.
START SUBNET $<tcpip-process>.#<subnet-name>
If a route is not in the started state, use the SCF START ROUTE command:c.
START ROUTE $<tcpip-process>.#<route-name>