SWAN Concentrator and WAN Subsystem Troubleshooting Guide

Verifying the SWAN Hardware
SWAN Concentrator and WAN Subsystem Troubleshooting Guide—426992-008
4-6
Error IDs related to OSM or TSM Test Action Failure
b. Verify that the SUBNETS on the preferred and alternate TCP/IP processes that
are associated with the LIFs are in the STARTED state by using the SCF
STATUS SUBNET command:
STATUS SUBNET $pref-tcpip-process.#subnet-name
STATUS SUBNET $alt-tcpip-process.#subnet-name
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 $pref-tcpip-process.#route-name
STATUS ROUTE $alt-tcpip-process.#route-name
Verifying That a TCP/IP Route is Started on page A-26 shows the output of this
command.
4. Restart any TCP/IP processes or objects that are not in the STARTED state.
a. If a TCP/IP process no longer exists, you must recreate it by using this TACL
command:
TCPIP / NAME $tcpip-process, NOWAIT,
CPU primary-cpu-num, PRI priority-num,
TERM $ZHOME / backup-cpu-num
b. If a SUBNET is not in the started state, use the SCF START SUBNET
command:
START SUBNET $tcpip-process.#subnet-name
c. If a route is not in the started state, use the SCF START ROUTE command:
START ROUTE $tcpip-process.#route-name
Error ID 1000022
This error is returned when you run the OSM or TSM Test Verify action and the CLIP is
not in a STOPPED state. To recover from this error, stop the CLIP then retry the test
action. For more information, see Preparing a SWAN CLIP for the OSM or TSM Test
Verify Test Action or Firmware Update on page 4-19.
Note. Always run TCP/IP as a process pair. Otherwise, the TCP/IP process loses all
LAN access if the data path to the LIF changes.