Drag and Drop Question Your customer wants to update the firmware for 36 HPE Synergy 480 Gen 10 compute modules with a server profile assigned from a server profile template. Put the steps required…

Question

Exhibit

Answer Area

Explanation

HPE Synergy Firmware Update via OneView - Step-by-Step Explanation

The Correct Order

1. Upload SPP to HPE OneView repository 2. Select Firmware baseline within server profile template 3. Select installation method (online or offline) 4. Update all server profiles from the template

Why This Order?

Step 1 - Upload SPP to HPE OneView repository

The Service Pack for ProLiant (SPP) is the firmware bundle containing all component updates. It must exist in OneView's repository before any profile can reference it - you cannot select a baseline that hasn't been uploaded yet. This is always the prerequisite. Nothing else can proceed without it.

Note: The question's "Available Items" list says "SPF" but the correct answer says "SPP" - this is almost certainly a typo in the question. SPP (Service Pack for ProLiant) is the correct term.

Step 2 - Select Firmware baseline within server profile template

Once the SPP is available in the repository, you edit the server profile template and point it to that SPP as the firmware baseline. Since 36 compute modules all share this one template, changing the baseline here will propagate to all derived profiles - this is the efficiency benefit of using templates.

Common mistake: Trying to set the baseline in individual server profiles rather than the template. With 36 nodes, that would require 36 separate edits and defeats the purpose of the template model.

Step 3 - Select installation method (online or offline)

With the baseline selected, you then choose how the firmware will be deployed:

• Online - update while the OS is running (no downtime, but some components may require reboot)
• Offline - server is powered down for the update (required for some firmware components, more disruptive)

This choice is made inside the template configuration before pushing the update out, because the method is part of what gets propagated to the profiles.

Common mistake: Treating online vs. offline as an afterthought. The installation method must be committed before triggering the update, not chosen mid-process.

Step 4 - Update all server profiles from the template

Finally, you trigger "Update all server profiles from template" in OneView. This pushes the new baseline and installation method to all 36 derived server profiles simultaneously and initiates the firmware update across all nodes. This is the action that actually applies the changes.

Common mistake: Skipping the template update step and trying to update profiles individually, or assuming the profiles auto-update the moment the template is changed (they don't - you must explicitly trigger the propagation).

Summary Mental Model

Have it → Point to it → Configure how → Deploy

You can't reference what doesn't exist, you can't deploy before configuring, and the template-first approach is what makes managing 36 nodes practical in OneView.

No community discussion yet for this question.