HP ProLiant BL660c HP ProLiant Gen8 Troubleshooting Guide Volume I: Troublesho - Page 45

HP Trusted Platform Module problems, Memory problems

Get HP ProLiant BL660c PDF manuals and user guides View all HP ProLiant BL660c manuals
Add to My Manuals
Save this manual to your list of manuals

Page 45 highlights

zone that indicates which server is consuming a lot of FAN speed. Possible indicators could be either an outdated ROMBIOS or HP iLO firmware or a server repeatedly going through POST or reboot. For more information, review the HP BladeSystem c-Class Enclosure Troubleshooting Guide on the HP website (http://www.hp.com/go/bladesystem/documentation). HP Trusted Platform Module problems Action: If the TPM fails and is no longer detected by RBSU, request a new system board and TPM board from an HP authorized service provider ("Contacting HP technical support or an authorized reseller" on page 79). CAUTION: Any attempt to remove an installed TPM from the system board breaks or disfigures the TPM security rivet. Upon locating a broken or disfigured rivet on an installed TPM, administrators should consider the system compromised and take appropriate measures to ensure the integrity of the system data. When installing or replacing a TPM, observe the following guidelines: • Do not remove an installed TPM. Once installed, the TPM becomes a permanent part of the system board. • When installing or replacing hardware, HP service providers cannot enable the TPM or the encryption technology. For security reasons, only the customer can enable these features. • When returning a system board for service replacement, do not remove the TPM from the system board. When requested, HP Service provides a TPM with the spare system board. • Any attempt to remove an installed TPM from the system board breaks or disfigures the TPM security rivet. Upon locating a broken or disfigured rivet on an installed TPM, administrators should consider the system compromised and take appropriate measures to ensure the integrity of the system data. • When using BitLocker™, always retain the recovery key/password. The recovery key/password is required to enter Recovery Mode after BitLocker™ detects a possible compromise of system integrity. • HP is not liable for blocked data access caused by improper TPM use. For operating instructions, see the encryption technology feature documentation provided by the operating system. Memory problems General memory problems are occurring Action: • Isolate and minimize the memory configuration. Use care when handling DIMMs ("DIMM handling guidelines" on page 16). o Be sure the memory meets the server requirements and is installed as required by the server. Some servers may require that memory banks be populated fully or that all memory within a memory bank must be the same size, type, and speed. To determine if the memory is installed properly, see the server documentation. o Check any server LEDs that correspond to memory slots. o If you are unsure which DIMM has failed, test each bank of DIMMs by removing all other DIMMs. Then, isolate the failed DIMM by switching each DIMM in a bank with a known working DIMM. o Remove any third-party memory. Hardware problems 45

  • 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
Hardware problems 45
zone that indicates which server is consuming a lot of FAN speed. Possible indicators could be either an
outdated ROMBIOS or HP iLO firmware or a server repeatedly going through POST or reboot.
For more information, review the
HP BladeSystem c-Class Enclosure Troubleshooting Guide
on the HP
website (
).
HP Trusted Platform Module problems
Action
: If the TPM fails and is no longer detected by RBSU, request a new system board and TPM board from
an HP authorized service provider ("
Contacting HP technical support or an authorized reseller
" on page
79
).
CAUTION:
Any attempt to remove an installed TPM from the system board breaks or disfigures
the TPM security rivet. Upon locating a broken or disfigured rivet on an installed TPM,
administrators should consider the system compromised and take appropriate measures to ensure
the integrity of the system data.
When installing or replacing a TPM, observe the following guidelines:
•
Do not remove an installed TPM. Once installed, the TPM becomes a permanent part of the system
board.
•
When installing or replacing hardware, HP service providers cannot enable the TPM or the encryption
technology. For security reasons, only the customer can enable these features.
•
When returning a system board for service replacement, do not remove the TPM from the system board.
When requested, HP Service provides a TPM with the spare system board.
•
Any attempt to remove an installed TPM from the system board breaks or disfigures the TPM security
rivet. Upon locating a broken or disfigured rivet on an installed TPM, administrators should consider the
system compromised and take appropriate measures to ensure the integrity of the system data.
•
When using BitLocker™, always retain the recovery key/password. The recovery key/password is
required to enter Recovery Mode after BitLocker™ detects a possible compromise of system integrity.
•
HP is not liable for blocked data access caused by improper TPM use. For operating instructions, see the
encryption technology feature documentation provided by the operating system.
Memory problems
General memory problems are occurring
Action
:
•
Isolate and minimize the memory configuration. Use care when handling DIMMs ("
DIMM handling
guidelines
" on page
16
).
o
Be sure the memory meets the server requirements and is installed as required by the server. Some
servers may require that memory banks be populated fully or that all memory within a memory bank
must be the same size, type, and speed. To determine if the memory is installed properly, see the
server documentation.
o
Check any server LEDs that correspond to memory slots.
o
If you are unsure which DIMM has failed, test each bank of DIMMs by removing all other DIMMs.
Then, isolate the failed DIMM by switching each DIMM in a bank with a known working DIMM.
o
Remove any third-party memory.