SWAN Concentrator and WAN Subsystem Troubleshooting Guide

Verifying the WAN Subsystem
SWAN Concentrator and WAN Subsystem Troubleshooting Guide—426992-008
3-4
Starting the WAN Subsystem Processes and Objects
Starting the WAN Subsystem Processes and
Objects
This procedure describes how to start the required WAN subsystem processes and
objects. It also describes how to start the processes and objects that support a SWAN
concentrator (for example, E4SAs, FESAs, GESAs, G4SAs, TCP/IP processes, and so
forth).
1. Start the WAN manager process by using the SCF START PROCESS command:
START PROCESS $ZZKRN.#ZZWAN
2. Start the LAN manager process by using the SCF START PROCESS command:
START PROCESS $ZZKRN.#ZZLAN
3. Start the E4SAs, FESAs, GESAs, or G4SAs to which the SWAN concentrator is
connected by using the SCF START ADAPTER command with the SUB ALL
option:
START ADAPTER $ZZLAN.adapter-name1, SUB ALL
START ADAPTER.$ZZLAN.adapter-name2, SUB ALL
Use the SCF START LIF command to start the logical interfaces (LIFs) used by the
SWAN concentrator on each E4SA, FESA, GESA, or G4SA:
START LIF $ZZLAN.lif-name1
START LIF $ZZLAN.lif-name2
4. Start the TCP/IP stacks associated with each LIF:
a. If a preferred and/or alternate TCP/IP process no longer exists, you must
recreate it using the following Tandem Advanced Command Language (TACL)
command:
TCPIP / NAME $tcpip-process, NOWAIT,
CPU primary-cpu-num, PRI priority-num,
TERM $ZHOME / backup-cpu-num
b. If the SUBNETS associated with the LIFs are not started, use the SCF START
SUBNET command to start them:
START SUBNET $pref-tcpip-process.#subnet-name
START SUBNET $alt-tcpip-process.#subnet-name
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.
Note. Depending on which TCP/IP product you are using, for more information, see
one of these manuals:
•
TCP/IP Configuration and Management Manual
•
TCP/IP (Parallel Library) Configuration and Management Manual
•
TCP/IPv6 Configuration and Management Manual