LAN Configuration and Management Manual

SCF Commands for the SLSA Subsystem
LAN Configuration and Management Manual—520469-012
4-12
ABORT PIF Command
Examples
The following example aborts the LANMON in processor 01:
ABORT MON $ZZLAN.#ZLM01
The following example aborts the LANMONs in processors 01, 02, and 03:
ABORT MON ($ZZLAN.#ZLM01, $ZZLAN.#ZLM02, $ZZLAN.#ZLM03)
ABORT PIF Command
The ABORT PIF command stops the operation of the specified PIF as quickly as
possible and places the PIF in the STOPPED state. Only enough processing is done to
ensure that the PIF can run again when the PIF is restarted.
This command takes effect immediately.
Command Syntax
OUT file-spec
causes any SCF output generated for this command to be directed to the specified
file.
Other Clients When a LANMON is aborted, other SLSA clients should handle
the situation like NonStop TCP/IP.
Other clients that may be affected include PAM, SS7/SHTI, and
IPX/SPX. TSM/OSM and SNMP clients should not be affected.
SS7/SHTI For SHTI clients running in the same CPU in which a LANMON
has been aborted, the calls to slsa_connect_nw and
slsa_lif_get_info fail with error
slsa_err_invalid_device_name (110). Like other clients,
the SHTI client gets an indication that LIF access has been lost
whenever a LANMON is aborted
NonStop
TCP/IP
When a LANMON is ABORTED, NonStop TCP/IP
(NonStop TCP/IP, Parallel Library TCP/IP, and
NonStop TCP/IPv6) gets an indication that the PIF/LIF has lost
access from its primary CPU and that SM_LIF_GET_INFO_
has been called. TCP/IP switches and keeps the SUBNET
started. LANMON cleans up and stops. TCP/IP fault-tolerant
capability is restored once the aborted LANMON is re-started.
ABORT [ /OUT file-spec/ ] PIF pif-name
[ , SUB { ONLY |ALL | NONE } ]
Effects of the ABORT MON command on Clients/NonStop TCP/IP (page2of2)