Service Processor Troubleshooting

Symptom
TSM, CPU RELOAD or SETTIME hangs when attempting to
communicate with the service processor. Performing a system load
does not clear the problem.
Version
G04.nn
Problem
The service processor is in a state where all SPIOLIB calls from the
NonStop Kernel hang. Reference TPR S970812 1109 2212.
Workaround
For TSM versions earlier than 4.0, use the following workaround: Use
the TSM Low-Level Link Application to reset the MSP currently
connected to $YMIOP. Determine which SP is supporting the CLCI
window. After the MSP has been reset, close the CLCI window and
open a new CLCI window against the other MSP.
Fix
The fix is available on G05.00. All I/Os initiated by the NonStop
Kernel SPIOLIB are now initiated as no-waited I/Os using the built in
command timeout values plus ten seconds as the timeout value. This
will cause SPIOLIB to time out any requests that are hung. This does
not fix the actual hang condition, but will return a timeout error to the
client.
Top
Symptom
The message box asking if you want to reset all SPs does not appear
after you have done a multiple SP firmware update.
Version
All.
Problem
Some SPs are not reporting firmware update status. These SPs
probably have not been updated.
Fix
Leave the Firmware Update dialog box open.
Using OSM: Select each SP whose firmware updates status is
missing from the Action Summary list. Open the Actions dialog box.
From the Available Actions drop-down list, choose SP Firmware
Update.
Using TSM: Open the Single SP Firmware Update dialog box and
update the firmware for each SP whose firmware update status is
missing from the Firmware Update Action Summary list.
After the firmware for each of these SPs has been successfully
updated, the multiple firmware update operation continues and
displays the message box. Click Yes in the message box to reset all
SPs and complete the update operation.
If any SP still fails to update, follow the recommended action
associated with the error message.