HP ML350 HP ProLiant Servers Troubleshooting Guide - Page 57

Expansion board problems

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

Page 57 highlights

2. Be sure the correct network driver is installed for the controller and that the driver file is not corrupted. Reinstall the driver. 3. Be sure no loose connections (on page 17) exist. 4. Be sure the network cable is working by replacing it with a known functional cable. 5. Check the PCI Hot Plug power LED to be sure the PCI slot is receiving power, if applicable. 6. Be sure the network controller is not damaged. 7. Run Insight Diagnostics ("HP Insight Diagnostics" on page 74) and replace failed components as indicated. Network controller stopped working when an expansion board was added Action: 1. Be sure no loose connections (on page 17) exist. 2. Be sure the server and operating system support the controller. Refer to the server and operating system documentation. 3. Be sure the new expansion board has not changed the server configuration, requiring reinstallation of the network driver. a. Uninstall the network controller driver for the malfunctioning controller in the operating system. b. Restart the server and run RBSU. Be sure the server recognizes the controller and that resources are available for the controller. c. Restart the server, and then reinstall the network driver. 4. Refer to the operating system documentation to be sure the correct drivers are installed. 5. Refer to the operating system documentation to be sure that the driver parameters match the configuration of the network controller. Problems are occurring with the network interconnect blades Action: Be sure the network interconnect blades are properly seated and connected. Expansion board problems System requests recovery method during expansion board replacement When replacing an expansion board on a BitLocker™-encrypted server, always disable BitLocker™ before replacing the expansion board. If BitLocker™ is not disabled, the system requests the recovery method selected when BitLocker™ was configured. Failure to provide the correct recovery password or passwords results in loss of access to all encrypted data. Be sure to enable BitLocker™ after the installation is complete. For information on BitLocker™, see BitLocker™ for Servers on the Microsoft website (http://www.microsoft.com). Hardware problems 57

  • 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
2.
cor
3.
Be
4.
Be sure the n
cable.
5.
e
6.
7.
Run
("
HP Insight Diagnostics
" on page
74
) and replace failed components as
Network controller stopped working wh
d
Action
:
(on page
17
) exist.
3.
Be sure the new expansion board has not changed the server configuration, requiring reinstallation
nctioning controller in the operating system.
Restart the server and run RBSU. Be sure the server recognizes the controller and that resources
or the controller.
Restart the server, and then reinstall the network driver.
Problem a
and connected.
System
method during expansion board replacement
disable BitLocker™
requests the recovery
Be sure to enable BitLocker™ after the installation is complete.
osoft website
Be sure the correct network driver is installed for the controller and that the driver file is not
rupted. Reinstall the driver.
sure no loose connections (on page
17
) exist.
etwork cable is working by replacing it with a known functional
Ch
ck the PCI Hot Plug power LED to be sure the PCI slot is receiving power, if applicable.
Be sure the network controller is not damaged.
Insight Diagnostics
indicated.
en an expansion board was adde
1.
Be sure no loose connections
2.
Be sure the server and operating system support the controller. Refer to the server and operating
system documentation.
of the network driver.
a.
Uninstall the network controller driver for the malfu
b.
are available f
c.
4.
Refer to the operating system documentation to be sure the correct drivers are installed.
match the
5.
Refer to the operating system documentation to be sure that the driver parameters
configuration of the network controller.
s
re occurring with the network interconnect blades
Action
: Be sure the network interconnect blades are properly seated
Expansion board problems
requests recovery
When replacing an expansion board on a BitLocker™-encrypted server, always
before replacing the expansion board. If BitLocker™ is not disabled, the system
method selected when BitLocker™ was configured. Failure to provide the correct recovery password or
passwords results in loss of access to all encrypted data.
For information on BitLocker™, see BitLocker™ for Servers on the Micr
(
).
Hardware problems 57