HP ML150 HP ProLiant ML100 Series Server User Guide - Page 74

Server fails to recognize new memory, PPM problems, Processor problems

Get HP ML150 - ProLiant - G6 PDF manuals and user guides
UPC - 884420743644
View all HP ML150 manuals
Add to My Manuals
Save this manual to your list of manuals

Page 74 highlights

3. Be sure a memory count error did not occur ("Memory count error exists" on page 73). See the message displaying memory count during POST. Server fails to recognize new memory Action: 1. Be sure the memory is the correct type for the server and is installed according to the server requirements. Refer to the server documentation or HP website (http://www.hp.com). 2. Be sure you have not exceeded the memory limits of the server or operating system. Refer to the server documentation. 3. Be sure the memory is properly seated. 4. Be sure no conflicts are occurring with existing memory. Run the server setup utility. 5. Test the memory by installing the memory into a known working server. Be sure the memory meets the requirements of the new server on which you are testing the memory. 6. Replace the memory. Refer to the server documentation. PPM problems Action: If the PPMs are not integrated on the system board: CAUTION: Do not operate the server for long periods with the access panel open or removed. Operating the server in this manner results in improper airflow and improper cooling that can lead to thermal damage. 1. If applicable, check the PPM LEDs to identify if a PPM failure occurred. For information on LEDs, refer to the server documentation. 2. Reseat each PPM, and then restart the server. 3. If reseating the PPMs is not effective, remove all but one PPM, restart the server to see if the PPM is working, and then install each PPM individually, cycling power each time. Follow the warnings and cautionary information in the server documentation. Processor problems Action: 1. If applicable, check the processor LEDs to identify if a PPM failure occurred. For information on LEDs, refer to the server documentation. 2. Be sure each processor is supported by the server and is installed properly. Refer to the server documentation for processor requirements. 3. Be sure the server ROM is up to date. 4. Be sure you are not mixing processor stepping, core speeds, or cache sizes if this is not supported on the server. Refer to the server documentation for more information. CAUTION: Removal of some processors and heatsinks require special considerations for replacement, while other processors and heatsinks are integrated and cannot be reused once separated. For specific instructions for the server you are troubleshooting, refer to processor information in the server user guide. 5. If the server has only one processor installed, replace it with a known functional processor. If the problem is resolved after you restart the server, the original processor failed. Troubleshooting 74

  • 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
Troubleshooting 74
3.
Be sure a memory count error did not occur ("
Memory count error exists
" on page
73
). See the
message displaying memory count during POST.
Server fails to recognize new memory
Action
:
1.
Be sure the memory is the correct type for the server and is installed according to the server
requirements. Refer to the server documentation or HP website (
).
2.
Be sure you have not exceeded the memory limits of the server or operating system. Refer to the
server documentation.
3.
Be sure the memory is properly seated.
4.
Be sure no conflicts are occurring with existing memory. Run the server setup utility.
5.
Test the memory by installing the memory into a known working server. Be sure the memory meets
the requirements of the new server on which you are testing the memory.
6.
Replace the memory. Refer to the server documentation.
PPM problems
Action
: If the PPMs are not integrated on the system board:
CAUTION:
Do not operate the server for long periods with the access panel open or
removed. Operating the server in this manner results in improper airflow and improper
cooling that can lead to thermal damage.
1.
If applicable, check the PPM LEDs to identify if a PPM failure occurred. For information on LEDs, refer
to the server documentation.
2.
Reseat each PPM, and then restart the server.
3.
If reseating the PPMs is not effective, remove all but one PPM, restart the server to see if the PPM is
working, and then install each PPM individually, cycling power each time. Follow the warnings and
cautionary information in the server documentation.
Processor problems
Action
:
1.
If applicable, check the processor LEDs to identify if a PPM failure occurred. For information on LEDs,
refer to the server documentation.
2.
Be sure each processor is supported by the server and is installed properly. Refer to the server
documentation for processor requirements.
3.
Be sure the server ROM is up to date.
4.
Be sure you are not mixing processor stepping, core speeds, or cache sizes if this is not supported
on the server. Refer to the server documentation for more information.
CAUTION:
Removal of some processors and heatsinks require special considerations for
replacement, while other processors and heatsinks are integrated and cannot be reused once
separated. For specific instructions for the server you are troubleshooting, refer to processor
information in the server user guide.
5.
If the server has only one processor installed, replace it with a known functional processor. If the
problem is resolved after you restart the server, the original processor failed.