Assessments - 0, GPA: 0
(
)
)
|
por este dispositivo também tem outras instruções :
Facilidade de uso
The blade has been forced to power-on, either via the MP user interface or the power
button. The blade did not negotiate with the enclosure to insure that there was
sufficient power for this action. Probable Cause: A forced power on occurred. Usually
this is performed when a normal power on request is denied. The Onboard
Administrator may now be running in a non-redundant or over-budget power
configuration. Recommended Action: Make sure Onboard Administator has the
appropriate number and configuration of power supplies. Reduce power required
by the blade (for instance, remove some memory or a CPU.) Or, if there are
powered-on blades that are not in use, power them off. WBEM EventID: 6582. WBEM
12165
Warning
ProviderName: FPL_IndicationProvider.
The MP has repeatedly tried to communicate with the enclosure manager and has
not received any response. Probable Cause: The MP has repeatedly requested
communication with the Onboard Administrator and has not received a response.
This may be because the EM has a fault condition, or is busy, being reset, or removed.
Recommended Action: The communication loss may have been temporary and
nothing needs to be done if the communication is now working. Check the Fault LED
on the enclosure manager. Reset the enclosure manager. Reset the management
processor. Replace the enclosure manager. WBEM EventID: 6583. WBEM
12168
Warning
ProviderName: FPL_IndicationProvider.
This is an internal SW error. See Cause/Action . Probable Cause: A CPU has tried to
acquired the same semaphore twice which resulted in a deadlock. This is an internal
SFW error and is not recoverable. Recommended Action: Collect the entire FPL, SEL,
console logs and forward them to the SFW team. Also note all activities around the
time of this event. The entire logs must analyzed by the SFW team before further
actions can be taken. The system must be cold reset to resume normal operation.
12193
Error
WBEM EventID: 6693. WBEM ProviderName: FPL_IndicationProvider.
This is an internal SW error. See Cause/Action. Probable Cause: A CPU has tried to
acquired the same semaphore twice which resulted in a deadlock. This is an internal
SFW error and is not recoverable. Recommended Action: Collect the entire FPL, SEL,
console logs and forward them to the SFW team. Also note all activities around the
time of this event. The entire logs must analyzed by the SFW team before further
actions can be taken. The system must be cold reset to resume normal operation.
12194
Error
WBEM EventID: 6694. WBEM ProviderName: FPL_IndicationProvider.
This is an internal SW error. See Cause/Action. Probable Cause: A CPU has tried to
acquired the same semaphore twice which resulted in a deadlock. This is an internal
SFW error and is not recoverable. Recommended Action: Collect the entire FPL, SEL,
console logs and forward them to the SFW team. Also note all activities around the
time of this event. The entire logs must analyzed by the SFW team before further
actions can be taken. The system must be cold reset to resume normal operation.
12195
Error
WBEM EventID: 6695. WBEM ProviderName: FPL_IndicationProvider.
This is an internal SW error. See Cause/Action. Probable Cause: A CPU has tried to
acquired the same semaphore twice which resulted in a deadlock. This is an internal
SFW error and is not recoverable. Recommended Action: Collect the entire FPL, SEL,
console logs and forward them to the SFW team. Also note all activities around the
time of this event. The entire logs must analyzed by the SFW team before further
actions can be taken. The system must be cold reset to resume normal operation.
12196
Error
WBEM EventID: 6696. WBEM ProviderName: FPL_IndicationProvider.
The complex profiles between cells in a partition do not match. Data field is unused,
earlier events will give more detail. Probable Cause: The Group A or Group C complex
profiles didn't match on all cells in the partition. Recommended Action: Push out
new complex profiles and reset. WBEM EventID: 6698. WBEM ProviderName:
12199
Error
FPL_IndicationProvider.
An I/O device is missing from the Core I/O. Probable Cause: Either an I/O device on
the Core I/O has failed or the wrong card is plugged into the location of the expected
Core I/O. Recommended Action: Replace the specified location with the supported
12204
Warning
Core I/O card. WBEM EventID: 6699. WBEM ProviderName: FPL_IndicationProvider.
fPars PMI handler was unable to Notify a CPU's new owner after a migrate. Probable
Cause: OS has not fully set up GPE enable bits with the FSHWA interface.
Recommended Action: Contact HP support. WBEM EventID: 6701. WBEM
12207
Warning
ProviderName: FPL_IndicationProvider.
Platform Events
83
... Este manual também é adequado para os modelos :
Computadores - HP BL860c Single Processor Server Blade (1 mb)
Computadores - HP Integrity BL860c Carrier-grade Server Blade (1 mb)
Computadores - HP Integrity BL860c i2 Server Blade (1 mb)
Computadores - HP Integrity BL860c Server Blade (1 mb)