LAN Configuration and Management Manual

Managing the SLSA Subsystem
LAN Configuration and Management Manual—520469-012
5-14
Replacing a LANMON Without a Cold Load
8. Verify that the primary LANMAN has switched CPUs by issuing the SCF STATUS
PROCESS command:
9. Use the SCF ABORT MON command to ABORT the LANMON in CPU 0 (if your
backup LANMAN is in CPU 0). If your backup LANMAN is in CPU 01, abort the
LANMON in CPU 01.
10. Use the SCF START MON command to start the LANMON in CPU 0 (if your
backup LANMAN is in CPU 0). If your backup LANMAN is in CPU 01, start the
LANMON in CPU 01.
Considerations

Starting $ZZKRN.#ZZLAN causes all LANMONs to be created and started
automatically. The fact that a LANMON was previously aborted is lost when
$ZZLAN is aborted.

The system will need to be cold loaded the first time the new software is installed.

The amount of time a LANMON is aborted should be kept to a minimum.

A client may be prevented from switching if the LANMON in which the client’s
backup is running has been aborted.
STATUS PROCESS $ZZKRN.#ZZLAN
NONSTOP KERNEL - Status PROCESS \HELLO.$ZZKRN.#ZZLAN
Symbolic Name Name State Sub Primary Backup Owner
PID PID ID
$ZZLAN $ZZLAN STARTED 1 ,15 0 ,16 255,255
ABORT MON $ZZLAN.#ZLM00
START MON $ZZLAN.#ZLM00