HP Integrity rx2800 HP Insight Management WBEM Provider Events Reference Guide - Page 96

The TPM DOT checksum could not be recalculated. Probable Cause: The System

Get HP Integrity rx2800 - i2 PDF manuals and user guides View all HP Integrity rx2800 manuals
Add to My Manuals
Save this manual to your list of manuals

Page 96 highlights

13721 Warning 13722 Warning 13724 Warning 13726 Warning 13727 Warning 13728 Warning 13730 Warning 13741 Error 13742 Error The TPM DOT checksum could not be recalculated. Probable Cause: The System Firmware has detected a bad checksum in the TPM shared memory table and failed to fix the checksum in Non-Volatile Memory. Manageability may not be able to update NVM. Recommended Action: Review the event log for related MFW events to determine if there is an NVM (Non-Volatile Memory) problem.Try a MFW reset via web or text interface. If this fails, verify all the firmware versions are at a supported revision level and do a full power cycle of the system. WBEM EventID: 8324. WBEM ProviderName: FPL_IndicationProvider. The TPM DOT information is not initialized. Probable Cause: The System Firmware has detected an uninitialized shared memory table for the TPM. This can be caused by manageability firmware/hardware. Recommended Action: The system will try to initialize the memory table. If the error persists, review the event log for related MFW events to determine if there is an NVM (Non-Volatile Memory) problem.Try a MFW reset via web or text interface. If this fails, verify all the firmware versions are at a supported revision level and do a full power cycle of the system.Replace the battery. WBEM EventID: 8329. WBEM ProviderName: FPL_IndicationProvider. The TPM DOT information could not be initialized successfully. Probable Cause: The System Firmware has detected an uninitialized shared memory table for the TPM and failed to initialize it. This can be caused by an error with Manageability firmware/hardware. Recommended Action: Review the event log for related MFW events to determine if there is an NVM (Non-Volatile Memory) problem.Try a MFW reset via web or text interface. If this fails, verify all the firmware versions are at a supported revision level and do a full power cycle of the system. WBEM EventID: 8327. WBEM ProviderName: FPL_IndicationProvider. The TPM DOT information could not be updated with the TPM presence indication. Probable Cause: The system could not initialize the value of the TPM presence flag in NVM (Non-Volatile Memory) possibly due to an error on manageability. Recommended Action: Review the event log for related MFW events to determine if there is an NVM (Non-Volatile Memory) problem.Try a MFW reset via web or text interface. If this fails, verify all the firmware versions are at a supported revision level and do a full power cycle of the system. WBEM EventID: 8325. WBEM ProviderName: FPL_IndicationProvider. The TPM DOT could not be updated with the TPM absent flag. Probable Cause: The system could not initialize the value of the TPM presence flag to Absent in NVM (Non-Volatile Memory) possibly due to an error on Manageability. Recommended Action: Review the event log for related MFW events to determine if there is an NVM (Non-Volatile Memory) problem.Try a MFW reset via web or text interface. If this fails, verify all the firmware versions are at a supported revision level and do a full power cycle of the system. WBEM EventID: 8326. WBEM ProviderName: FPL_IndicationProvider. The TPM mode at next boot command could not be cleared in the TPM DOT table. Probable Cause: The system could not clear the command to change the TPM state at next boot in the NVM (Non-Volatile Memory) possibly due to an error on manageability firmware/hardware. Recommended Action: Review the event log for related MFW events to determine if there is an NVM (Non-Volatile Memory) problem.Try a MFW reset via web or text interface. If this fails, verify all the firmware versions are at a supported revision level and do a full power cycle of the system. WBEM EventID: 8323. WBEM ProviderName: FPL_IndicationProvider. The command to change the TPM state has failed. Probable Cause: The request to change the TPM state has failed. An error occurred with the TPM. Recommended Action: Review the event log for TPM related messages. Reboot the system. Replace the TPM board. WBEM EventID: 8332. WBEM ProviderName: FPL_IndicationProvider. Failed to acquire platform specific data in ACPI. Probable Cause: Corrupted SFW image. Recommended Action: Ensure SFW component is at supported level. WBEM EventID: 8533. WBEM ProviderName: FPL_IndicationProvider. Failed to acquire platform specific data in ACPI. Probable Cause: Corrupted SFW image. Recommended Action: Ensure SFW component is at supported level. WBEM EventID: 8527. WBEM ProviderName: FPL_IndicationProvider. 96 WBEM Provider Event Tables

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
  • 81
  • 82
  • 83
  • 84
  • 85
  • 86
  • 87
  • 88
  • 89
  • 90
  • 91
  • 92
  • 93
  • 94
  • 95
  • 96
  • 97
  • 98
  • 99
  • 100
  • 101
  • 102
  • 103
  • 104
  • 105
  • 106
  • 107
  • 108
  • 109
  • 110
  • 111
  • 112
The TPM DOT checksum could not be recalculated. Probable Cause: The System
Firmware has detected a bad checksum in the TPM shared memory table and failed
to fix the checksum in Non-Volatile Memory. Manageability may not be able to
update NVM. Recommended Action: Review the event log for related MFW events
to determine if there is an NVM (Non-Volatile Memory) problem.Try a MFW reset
via web or text interface. If this fails, verify all the firmware versions are at a supported
revision level and do a full power cycle of the system. WBEM EventID: 8324. WBEM
ProviderName: FPL_IndicationProvider.
Warning
13721
The TPM DOT information is not initialized. Probable Cause: The System Firmware
has detected an uninitialized shared memory table for the TPM. This can be caused
by manageability firmware/hardware. Recommended Action: The system will try to
initialize the memory table. If the error persists, review the event log for related MFW
events to determine if there is an NVM (Non-Volatile Memory) problem.Try a MFW
reset via web or text interface. If this fails, verify all the firmware versions are at a
supported revision level and do a full power cycle of the system.Replace the battery.
WBEM EventID: 8329. WBEM ProviderName: FPL_IndicationProvider.
Warning
13722
The TPM DOT information could not be initialized successfully. Probable Cause:
The System Firmware has detected an uninitialized shared memory table for the
TPM and failed to initialize it. This can be caused by an error with Manageability
firmware/hardware. Recommended Action: Review the event log for related MFW
events to determine if there is an NVM (Non-Volatile Memory) problem.Try a MFW
reset via web or text interface. If this fails, verify all the firmware versions are at a
supported revision level and do a full power cycle of the system. WBEM EventID:
8327. WBEM ProviderName: FPL_IndicationProvider.
Warning
13724
The TPM DOT information could not be updated with the TPM presence indication.
Probable Cause: The system could not initialize the value of the TPM presence flag
in NVM (Non-Volatile Memory) possibly due to an error on manageability.
Recommended Action: Review the event log for related MFW events to determine
if there is an NVM (Non-Volatile Memory) problem.Try a MFW reset via web or text
interface. If this fails, verify all the firmware versions are at a supported revision
level and do a full power cycle of the system. WBEM EventID: 8325. WBEM
ProviderName: FPL_IndicationProvider.
Warning
13726
The TPM DOT could not be updated with the TPM absent flag. Probable Cause: The
system could not initialize the value of the TPM presence flag to Absent in NVM
(Non-Volatile Memory) possibly due to an error on Manageability. Recommended
Action: Review the event log for related MFW events to determine if there is an NVM
(Non-Volatile Memory) problem.Try a MFW reset via web or text interface. If this
fails, verify all the firmware versions are at a supported revision level and do a full
power cycle of the system. WBEM EventID: 8326. WBEM ProviderName:
FPL_IndicationProvider.
Warning
13727
The TPM mode at next boot command could not be cleared in the TPM DOT table.
Probable Cause: The system could not clear the command to change the TPM state
at next boot in the NVM (Non-Volatile Memory) possibly due to an error on
manageability firmware/hardware. Recommended Action: Review the event log for
related MFW events to determine if there is an NVM (Non-Volatile Memory)
problem.Try a MFW reset via web or text interface. If this fails, verify all the firmware
versions are at a supported revision level and do a full power cycle of the system.
WBEM EventID: 8323. WBEM ProviderName: FPL_IndicationProvider.
Warning
13728
The command to change the TPM state has failed. Probable Cause: The request to
change the TPM state has failed. An error occurred with the TPM. Recommended
Action: Review the event log for TPM related messages. Reboot the system. Replace
the TPM board. WBEM EventID: 8332. WBEM ProviderName:
FPL_IndicationProvider.
Warning
13730
Failed to acquire platform specific data in ACPI. Probable Cause: Corrupted SFW
image. Recommended Action: Ensure SFW component is at supported level. WBEM
EventID: 8533. WBEM ProviderName: FPL_IndicationProvider.
Error
13741
Failed to acquire platform specific data in ACPI. Probable Cause: Corrupted SFW
image. Recommended Action: Ensure SFW component is at supported level. WBEM
EventID: 8527. WBEM ProviderName: FPL_IndicationProvider.
Error
13742
96
WBEM Provider Event Tables