Troubleshooting the SLSA Subsystem

4 Verify that the ServerNet addressable controllers (SACs) are in the STARTED
state.
Use the SCF STATUS SAC command:
STATUS SAC $ZZLAN.<adapter>.*
The example shows the output of the SCF STATUS SAC command.
You can use the DETAIL option with the SCF STATUS SAC command to obtain
additional information. The example shows the output of the SCF STATUS SAC
command with the DETAIL option and explains how to interpret it.
Tip: If the SAC associated with MIOE0 or MIOE1 remains in the
STARTING state, you might need to reset the service processor (SP) associated
with the SAC using the OSM or TSM Low-Level Link.
5 Verify that the physical interfaces (PIFs) are in the STARTED state.
Use the SCF STATUS PIF command :
STATUS PIF $ZZLAN.<adapter>.*
The example shows the output of the SCF STATUS PIF command.
You can use the DETAIL option with the SCF STATUS PIF command to obtain
additional information. The example shows the output of the SCF STATUS PIF
command with the DETAIL option and explains how to interpret it.
Tip: The following are reasons why a PIF might not start:
The parent SAC must be in the STARTED or STARTING state for the SCF
START PIF command to be accepted. The PIF goes into the STARTED
state only when the parent SAC is in the STARTED state.
●
The PIF cannot go into the STARTED state until the adapter is successfully
downloaded with the DLFILENAME. The SCF START SAC command
causes the download of the SAC. If the SAC status is STARTED, then the
SAC has been successfully downloaded.
●
The PIF on a Token-Ring ServerNet adapter (TRSA) cannot go to the
STARTED state until successful ring insertion occurs. When not connected
to a token-ring LAN, the PIF remains in the STARTING state and the SLSA
event message 4101 is generated. A PIF status of STARTED for a TRSA
indicates a successful download to the adapter and ring insertion.
●
After starting the PIF, check the configuration of the SAC using the SCF●