One of the DL380 Gen10 servers in your infrastructure has failed to boot after a 3rd party PCle NIC was installed. What is the most likely cause of this issue?

Question

Options

• AHPE does not allow 3rd party PCle cards.
• BThe latest Support pack for ProLiant must be used before accessing any additional 3rd party
• CThe manufacturer did not digitally sign the correct firmware and HPE Secure Boot halted the
• DThe iLO interface did not have a correct IP address provided from DHCP.

• A
  8% (3)
• B
  16% (6)
• C
  71% (27)
• D
  5% (2)

Explanation

HPE Secure Boot is a UEFI security feature that validates firmware and option ROM signatures before allowing hardware to initialize - if a 3rd party NIC's firmware lacks a valid digital signature recognized by HPE's Secure Boot chain, the server will halt at boot, which is exactly what's described here. Option A is wrong because HPE servers do support 3rd party PCIe cards; they just must meet Secure Boot requirements. Option B is a red herring - while keeping SPP (Support Pack for ProLiant) current is good practice, it doesn't resolve a Secure Boot signature validation failure caused by unsigned 3rd party firmware. Option D is irrelevant because iLO's DHCP address affects out-of-band management access, not the server's ability to POST and boot.

Memory tip: Think "Secure Boot = bouncer at the door checking IDs." Unsigned firmware = no ID = no entry. If a new card kills your boot, suspect the signature before anything else.

No community discussion yet for this question.