Midplane assembly replacement 66
Midplane assembly replacement
Midplane assembly troubleshooting
Historic service data collected on the c-Class Enclosures suggests that midplane hardware failures are very
rare. Therefore, midplane replacements must only be made as a last resort.
Midplane connections are 100% copper to copper connections for the data-ports. These connections hardly
brake during a normal day to day operation.
Before requesting midplane assembly replacement, always complete the enclosure troubleshooting (on page
) procedures in this guide. The procedures in this section should be completed by an HP authorized service
provider.
CAUTION:
To replace the midplane assembly, contact an HP authorized service provider.
CAUTION:
Before continuing with this procedure, be sure to record or save all data stored on all
enclosure components. Failure to save the information, could result in data loss.
Midplane assembly troubleshooting guidelines:
1.
Remove and reinsert the blades or use the OA CLI command:
reset server x
(where
x
represents
the server bay slot) to simulate a removal and reinsertion of a blade server.
2.
If a server is not booting up at all, then review the EBIPA settings for this blade to make sure that the iLO
IP is only used once and not a duplicate.
3.
If there are two devices on the network with the same iLO IP for a single blade, then a blade server does
not boot up.
4.
If a blade server is not booting up, then review the SHOW ENCLOSURE POWER summary section at
OA SHOW ALL to see if enough power is available to boot up all server blades.
5.
Review if all optional mezzanine cards are installed properly and are aligned with the right
interconnect bay.
6.
Remove and reinsert the OA tray firmly.
7.
If a blade server does not gain network or SAN connectivity on a single port (no Virtual Connect
installed), review the OA SHOW ALL section for the SHOW SERVER PORT MAP {bay}.
To see how and if the network or SAN port is connected properly from a OA perspective:
—
Observe the port statistics from the interconnect device to verify that specific port is not working.
—
Observe the server OS to verify that the network or SAN port is enabled properly.
—
Reboot or factory reset this interconnect device first, where needed.
8.
If a blade server does not gain network or SAN connectivity on a single port (Virtual connect installed):
o
Backup the VC domain configuration by using VCSU or VC GUI.
o
Remove the VC server profile from that specific bay and retry to power on that blade.
