Troubleshooting the SLSA Subsystem

INFO SAC command with the DETAIL option. For example:
INFO SAC $ZZLAN.<adapter>.<sac>, DETAIL
If there is a dump file in the current SYSnn, check its creation date.
Provide the dump file to the GCSC if the cause of the failure is
unknown. Also provide any related event messages for the SLSA
subsystem and the VPROC of the dump file. The dump file names for
the different types of adapters are as follows:
For the ATM3SA, the dump file name is C0440D00●
For the CCSA, the dump file name is C0303D00●
For the E4SA, the dump file name is C7957D00●
For the FESA, the dump file name is C0301D00●
For the GESA, the dump file name is C0507D00●
For the MFIOB, the default file names are null●
For the TRSA, the dump file name is C0084D00●
If one or more of the PIFs for a Common Communication ServerNet
adapter (CCSA) fail to start but the SAC is in the STARTED state, there
might be a problem with the cable. Remove the cable and inspect the cable
connector for damage. For more information, see Support Note S99018.
●
6 Verify that the logical interfaces (LIFs) are in the STARTED state and that the
access state is UP:
Use the SCF STATUS LIF command:
STATUS LIF $ZZLAN.*
The example shows the output of the SCF STATUS LIF command.
You can use the DETAIL option with the SCF STATUS LIF command to obtain
additional information. The example shows the output of the SCF STATUS LIF
command with the DETAIL option and explains how to interpret it.
Tip: If a LIF is in the STARTED state but its access state is DOWN, this
indicates that the associated PIF does not have data access. For MIOE0 or
MIOE1, this can occur if ServerNet access is down or if the service processor
(SP) is hung. Reset the SP using the OSM or TSM Low-Level Link. You might
also do the following:
Make sure that the processor that owns the SAC associated with the LIF is
the same as the primary processor of the NonStop TCP/IP process
associated with the LIF.
●
Check the state of the PIF associated with the LIF. If the PIF is not started,●