HP ML350 HP ProLiant Servers Troubleshooting Guide - Page 47

Server is o, Memory count error exists, Server fails to recognize existing memory, Server fails

Page 47 highlights

Server is out of memory Action: 1. Be sure the memory is configured properly. Refer to the application documentation to determine the memory configuration requirements. 2. Be sure no operating system errors are indicated. 3. Be sure a memory count error ("Memory count error exists" on page 47) did not occur. Refer to the message displaying memory count during POST. Memory count error exists Possible Cause: The memory modules are not installed correctly. Action: 1. Be sure the memory modules are supported by the server. See the server documentation. 2. Be sure the memory modules have been installed correctly in a supported configuration. See the server documentation. 3. Be sure the memory modules are seated properly ("DIMM handling guidelines" on page 18). 4. Be sure no operating system errors are indicated. 5. Restart the server and check to see if the error message is still displayed. 6. Run HP Insight Diagnostics (on page 74). Then, replace failed components as indicated. Server fails to recognize existing memory Action: 1. Reseat the memory. Use care when handling DIMMs ("DIMM handling guidelines" on page 18). 2. Be sure the memory is configured properly. See the server documentation. 3. Be sure a memory count error did not occur ("Memory count error exists" on page 47). 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. See 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. See the server documentation. 3. Be sure no Event List error messages are displayed in the IML ("Integrated Management Log" on page 75). 4. Be sure the memory is seated properly ("DIMM handling guidelines" on page 18). 5. Be sure no conflicts are occurring with existing memory. Run the server setup utility. 6. 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. 7. Replace the memory. See the server documentation. Hardware problems 47

  • 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
  • 113
  • 114
  • 115
  • 116
  • 117
  • 118
  • 119
  • 120
  • 121
  • 122
  • 123
  • 124
  • 125
  • 126
  • 127
  • 128
  • 129
  • 130
  • 131
  • 132
  • 133
  • 134
  • 135
  • 136
  • 137
  • 138
  • 139
  • 140
  • 141
  • 142
  • 143
  • 144
  • 145
  • 146
  • 147
  • 148
  • 149
  • 150
  • 151
  • 152
  • 153
  • 154
  • 155
  • 156
  • 157
  • 158
  • 159
  • 160
  • 161
  • 162
  • 163
  • 164
  • 165
  • 166
  • 167
  • 168
  • 169
  • 170
  • 171
  • 172
  • 173
  • 174
  • 175
  • 176
  • 177
  • 178
  • 179
  • 180
  • 181
  • 182
  • 183
  • 184
  • 185
  • 186
  • 187
  • 188

Server is o
o
Action
1.
efer to the application documentation to determine the
2.
3.
Memory count error exists
tly.
r documentation.
d configuration. See the
ver documentation.
4.
6.
Server fails to recognize existing memory
Action
:
guidelines
" on page
18
).
sure a memory count error did not occur ("
Memory count error exists
" on page
47
). See the
ess
Server fails to recognize new memory
1.
pe for the server and is installed according to the server
on or HP website (
ut f memory
:
memory configuration requirements.
Be sure the memory is configured properly. R
Be sure no operating system errors are indicated.
Be sure a memory count error ("
Memory count error exists
" on page
47
) did not occur. Refer to the
message displaying memory count during POST.
Possible Cause
: The memory modules are not installed correc
Action
:
1.
Be sure the memory modules are supported by the server. See the serve
2.
Be sure the memory modules have been installed correctly in a supporte
ser
3.
Be sure the memory modules are seated properly ("
DIMM handling guidelines
" on page
18
).
Be sure no operating system errors are indicated.
5.
Restart the server and check to see if the error message is still displayed.
Run HP Insight Diagnostics (on page
74
). Then, replace failed components as indicated.
1.
Reseat the memory. Use care when handling DIMMs ("
DIMM handling
2.
Be sure the memory is configured properly. See the server documentation.
3.
Be
m
age displaying memory count during POST.
Action
:
Be sure the memory is the correct ty
requirements. See the server documentati
).
r or operating system. See the server
3.
no Event List error messages are displayed in the IML ("
Integrated Management Log
" on
page
18
).
ith existing memory. Run the server setup utility.
on which you are testing the memory.
2.
Be sure you have not exceeded the memory limits of the serve
documentation.
Be sure
page
75
).
4.
Be sure the memory is seated properly ("
DIMM handling guidelines
" on
5.
Be sure no conflicts are occurring w
6.
Test the memory by installing the memory into a known working server. Be sure the memory meets
the requirements of the new server
7.
Replace the memory. See the server documentation.
Hardware problems 47