Troubleshooting the SLSA Subsystem

Finding SLSA Subsystem Event Messages in the
Event Log
When you view events using the OSM or TSM Event Viewer, the subsystem name (or, in
rare cases, the subsystem number) is shown in the SSID column. The subsystem name for
events generated by the ServerNet LAN Systems Access (SLSA) subsystem is SLSA and
the subsystem number is 193.
The OSM and TSM Event Viewers allow you to specify the date and time ranges of the
events you want displayed, the logs (such as $0 and $ZLOG) from which you want events
displayed, and the subsystems from which you want events displayed.
Common SLSA Problems and Events
The following table lists the event messages that are generated for some common SLSA
problems.
Problem Description
Event Number(s) Generated
Loss of a ServerNet fabric 3044 (Path switched to X-fabric)
3045 (Path switched to Y-fabric)
Loss of access of one
processor to a SAC
4001 (SAC transient fault with fault number 2011 to 2014,
2018, 2033, 2036, 2040, 2044, 2045, 3011 to 3018, 3025
to 3027, 3036, 3038, 3043, 3046,or 3047)
4007 (SAC ownership change)
4009 (SAC state after ownership change)
4102 (PIF available)
Loss of a processor 4603 (LANMON unavailable)
4007 (SAC ownership change)
4009 (SAC state after ownership change)
4102 (PIF available)
Loss of access of all processors
to a SAC
Same as loss of a processor
Loss of an adapter 4003 (SAC unavailable)
4004 (SAC state change)
4011 (SAC dump file created)