How to Reboot the Service Processor (SP) on x86 Platforms.

Asset ID:	1-71-1448038.1
Update Date:	2017-06-19
Keywords:

Solution Type Technical Instruction Sure

Solution 1448038.1 : How to Reboot the Service Processor (SP) on x86 Platforms.

Related Items


Sun Fire X4470 Server
 Sun Blade X6275 M2 Server Module
 Sun Fire X4200 M2 Server
 Sun Fire X4600 M2 Server
 Sun Fire X4100 M2 Server
 Sun Fire X4800 Server
 Sun Fire X4640 Server
 Sun Netra X4450 Server
 Sun Fire X4140 Server
 Sun Server X2-4
 Sun Blade X6220 Server Module
 Sun Fire X4270 Server
 Sun Blade X6270 M2 Server Module
 Sun Blade X6420 Server Module
 Sun Blade X6440 Server Module
 Sun Fire X4100 Server
 Sun Blade X6275 Server Module
 Sun Fire X4270 M2 Server
 Sun Fire X4150 Server
 Sun Fire X2270 M2 Server
 Sun Fire X4600 Server
 Sun Fire X4170 Server
 Sun Fire X4240 Server
 Sun Fire X4200 Server
 Sun Netra X4270 Server
 Sun Fire X2270 Server
 Sun Fire X4170 M2 Server
 Sun Netra X4200 M2 Server
 Sun Fire X4450 Server
 Sun Fire X4275 Server
 Sun Netra X4250 Server
 Sun Server X2-8
 Sun Fire X4500 Server
 Sun Blade X6250 Server Module
 Sun Fire X4540 Server
 Sun Blade X6270 Server Module
 Sun Fire X4250 Server
 Sun Fire X4440 Server
 Sun Netra X6270 M2 Server Module
 Sun Fire X2250 Server
 Sun Blade X6240 Server Module
 Sun Blade X6450 Server Module

Related Categories


PLA-Support>Sun Systems>x86>Server>SN-x64: MISC-SERVER
 _Old GCS Categories>Sun Microsystems>Servers>x64 Servers

In this Document

Goal

Solution

References

Applies to:

Sun Fire X4275 Server - Version Not Applicable to Not Applicable [Release N/A]
Sun Blade X6420 Server Module - Version Not Applicable to Not Applicable [Release N/A]
Sun Fire X4800 Server - Version Not Applicable to Not Applicable [Release N/A]
Sun Blade X6450 Server Module - Version Not Applicable to Not Applicable [Release N/A]
Sun Blade X6250 Server Module - Version Not Applicable to Not Applicable [Release N/A]
Information in this document applies to any platform.

Goal

To discuss this information further with Oracle experts and industry peers, we encourage you to review, join or start a discussion in the My Oracle Support Community - Sun x86 Systems

This document will describe when it might be necessary to reboot the service processor.
For symptoms, such as but not limited to:

Service Processor (SP) on an x86 platform appears hung
SP is 100% non-responsive
SP is partially responsive, such as you can ping it, but can no longer log in like you have done so in the past
'BMC not responding' shown during power on self test (POST) of the host
SP is giving unexpected results and/or seems no longer functioning properly over time
ILOM inaccessible
ILOM snapshot is missing data or contains multiple *.err files with text such as "Unable to establish LAN session"
Starting or stopping the host from CLI or GUI do not function as expected.
Events in the System Event Log (SEL) are no longer being logged.

Solution

The Service Processor (SP) runs it's own dedicated operating system.
Rebooting the SP should clear the issue.

You can safely reboot the SP while the host operating system is running.

Perform one of the following steps:

#1 From the Service Processor WebGUI:

   Go to the 'Maintenance' tab
   Go to the 'Reset SP' tab
   Click on the "Reset SP" button

Shown here is ILOM 3.0

GUI Interface

Shown here is ILOM 3.1

#2 SP CLI via "root" account:

-> reset /SP
Are you sure you want to reset /SP (y/n)?

#3 ipmitool from remote host:

% ipmitool -U root -H xxx.xxx.xxx.xxx bmc reset cold
Sent cold reset command to MC

#4 ipmitool from the root account on the local host:

   % ipmitool bmc reset cold
   bmc_send_cmd: Permission denied <-- Must be root or you will get this error.
   % su root
   Password:
   # ipmitool bmc reset cold
   Sent cold reset command to MC

#5 Use the service processor serial management port connection. Defaults should be 9600 baud with no flow control but check your product documentation to be certain.

-> reset /SP
Are you sure you want to reset /SP (y/n)?

#6 Press the SP reset button.

   Some platforms have the SP reset button labeled on the rear chassis. Some older platform may show it marked only with two double slash marks: //
   The service manual for the platform may or may not show the location. The System Handbook should show the location of the SP reset button on the systemboard schematics.
   Use caution if you attempt this method. The SP reset button is usually within close proximity to "MNI" and "Host Reset" buttons. Either one of those can cause the host OS to stop running when pressed.

   Also make certain to use a non-conduction material, such as a wooden toothpick, when attempting to press the button.

   It is beyond the scope of this document to show the location of the SP reset buttons for all platforms, however there are a few images in Doc ID 1455473.1

#7 Forced cold boot:

Stop the operating system.
Power system off and remove all power cords for ~10 seconds.
In the case of blades, stop the operating system and remove the blade from the chassis.

If an FE is already onsite, they will have these additional options.

#8a SP CLI via the "sunservice" account on ILOM 2.x:

[(flash)root@SP_hostname:~]# reboot

#8b SP CLI via the "sunservice" account on ILOM 3.x:

[(flash)root@SP_hostname:~]# reboot

For #8b, an escalation mode password will be required.

If the SP is completely hung, the only option may be #7 'Forced cold boot' which will required the operating system on the host to be shut down.

You should also check to see that your SP has the latest firmware.
See "Firmware Downloads and Release History for Sun/Oracle Systems"

To check the SP uptime, see
How to Determine the 'uptime' on an x86 Platform Service Processor (SP or ILOM) (Doc ID 1448364.1)

Attachments

This solution has no attachment