Service Processor Troubleshooting

ManualsBrandsHP ManualsServerHP Integrity NonStop Troubleshooting Tips

Troubleshooting Multiple SP Firmware Updates
The following symptoms can occur when updating firmware for multiple SPs:
TSM reports Error -483 (G03.nn RVUs).● 
TSM reports Error -734 or the update hangs (G03.nn RVUs).● 
TSM, CPU RELOAD or SETTIME hangs when attempting to communicate with the
service processor. Performing a system load does not clear the problem (G04.nn
RVUs).
● 
The message box asking if you want to reset all SPs does not appear after you have
done a multiple SP firmware update (all RVUs).
● 
The firmware updates or the resets that follow never finish. (The completion dialog
box is never received.) You wish to retry the firmware update action. On the Firmware
Update dialog box, the X-side or Y-side selection option is dimmed (not available) (all
RVUs).
● 
You do not seem to be receiving status updates from the OSM Service Connection or
the TSM Service Application (all RVUs).
● 
Symptom
TSM reports Error -483.
Version
G03.nn.
Problem
Indicates an MIOP or XIO connection problem.
Fix or Workaround
Retry the firmware update. If the update fails again, contact the
Global Customer Support Center (GCSC).
Top
Symptom
TSM reports Error -734 or the update hangs.
Version
G03.nn.
Problem
Error -734 can be caused by the following:
The SP firmware in the enclosure is G03.nn. The enclosure
contains both a down-rev G02.nn PMF or IOMF CRU and a
G03.nn PMF or IOMF CRU.
● 
There might be a problem with the PMF or IOMF CRU.● 
There might be a problem with the ServerNet cable.● 
Fix or Workaround
Install the MIOP T8171AAB RVU or a superceding RVU on the
G03.nn SPR before upgrading the SP firmware to G05.00 or any
subsequent G-series RVU.
Top

Summary of content (3 pages)

PAGE 1
Troubleshooting Multiple SP Firmware Updates The following symptoms can occur when updating firmware for multiple SPs: ● TSM reports Error -483 (G03.nn RVUs). ● TSM reports Error -734 or the update hangs (G03.nn RVUs). ● TSM, CPU RELOAD or SETTIME hangs when attempting to communicate with the service processor. Performing a system load does not clear the problem (G04.nn RVUs).
PAGE 2
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.
PAGE 3
Top Symptom The firmware updates or the resets that follow never finish. (The completion dialog box is never received.) You wish to retry the firmware update action. On the Firmware Update dialog box, the X-side or Y-side selection option is dimmed (not available). Version All. Problem Once the firmware update or reset action has started, the X-side or Y-side selection option is disabled until the action has successfully finished for all SPs on the selected side.