readthefuckingmanual.net

Step 1

Check whether the system controller(SC), otherwise known as the Advanced Lights-Out Management interface(ALOM), is accessible using an external connection, rather than from within the operating system. This is to test whether the SC is still alive, regardless of whether there is Solaris access to SC.

To conduct this verification, you must connect to the SC via the serial management port, to confirm whether the SC is responsive. Take note that
connecting to the SC via the Ethernet port (network management port) will depend
on whether the SC\'s Ethernet port has been previously configured to accept
incoming connections. If the SC\'s Ethernet port is not configured, access to the
SC will not be available via the Ethernet.

When a connection has been gained to the SC, there might not be any output. This
is normal because the SC default behavior(setting), is to time-out console
redirection within 60 seconds of being booted or reset. 

Enter the escape sequence \"#.\" to gain access to the SC prompt \"sc> \" or a ?login:? request by
the SC.

Step 2

If no response is seen from the SC after keying in the escape sequence \"#.\"
or even after a power cycle, consider replacing the SC.

However, if you are able to access the system controller externally, then you might be experiencing Bug, ID 5017681 

Permalink

-----------------------------------------
Bug ID: 5017681
\"su driver unloading causes loss of connection from Solaris to ALOM\"

Work Around: 
You can manually load the driver again using the \"modload su\"command from Solaris. This is only temporary as Solaris may unload su again later.

Add the line following line to /etc/system and reboot:
forceload: drv/su

This should assist in preventing \"su\" from unloading.
------------------------------------------

Permalink