When and How to Reboot the Service Processor (SP) on x86 Platforms.
(Doc ID 1448038.1)
Last updated on MAY 13, 2022
Applies to: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]
Oracle Database Appliance - Version All Versions to All Versions [Release All Releases]
Sun Fire X4640 Server - Version Not Applicable to Not Applicable [Release N/A]
Sun Fire X4150 Server - Version Not Applicable to Not Applicable [Release N/A]
Information in this document applies to any platform.
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.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document