After replacing a failed Compute Module, you notice the server profile Is not automatically assigned to the replaced server hardware. What can cause this issue?

Question

Options

• AiLO firmware of the replacement server is different than firmware in broken server.
• BServer profile affinity is configured to Device Day + server hardware.
• CThe enclosure group has to be updated to match the original enclosure group.
• DThe replacement server has more memory or CPUs than broken machine.

• A
  83% (40)
• B
  10% (5)
• C
  4% (2)
• D
  2% (1)

Explanation

Option A is correct because HPE OneView relies on iLO (Integrated Lights Out) firmware to discover and manage server hardware. If the replacement Compute Module has a different iLO firmware version than OneView expects, it may fail to properly identify or communicate with the new hardware, blocking automatic server profile assignment - OneView needs firmware compatibility to validate and bind a profile to a server.

Option B is a plausible-sounding distractor, but "Device Bay + Server Hardware" affinity is what causes a profile to follow a specific physical device, not the bay; the correct affinity setting to enable auto-assignment to a replacement in the same bay is "Device Bay" only - so B describes a valid affinity configuration, not an error that explains the failure. Option C is wrong because the enclosure group already covers the enclosure where the replacement is installed; it doesn't need to be updated for a like-for-like module swap. Option D is wrong because OneView server profiles are designed to be hardware-agnostic within compatible server families - having more CPU or RAM than the original does not block profile assignment.

Memory tip: Think of iLO firmware as the "handshake language" between OneView and the server - if the replacement speaks a different dialect, OneView won't recognize it well enough to hand it a profile.

No community discussion yet for this question.