SUT for ESXi 6.7 on ProLiant Gen10

[cprinz]

Hello,

is SUT for ESXi 6.7 on ProLiant Gen10 needed and where to get it?

I was not able to find a download.

Regards,

cprinz

[ronissac · Accepted solution]

Hi Cprinz, 

You may download the iSUT utility for esxi 6.7 from the 2018.11.0 Service pack for proliant .

The component name is cp035501.zip.

1. Extract the offline bundle from the iSUT component(cpxxxxxx.zip).

2. Copy the iSUT offline bundle (sut-esxi-bundle-.zip) to the VMware ESXi system.

3. Install the iSUT offline bundle on the VMware ESXi host—esxcli software vib install –d

4. Reboot the VMware ESXi host.

5. If there was no other OS installed (Windows or Linux) on the system before installing ESXi, proceed to step 6.

Alternatively, execute the sut -deregister command to clear the iLO settings used by the earlier iSUT installation.

6. Set the iSUT mode using the OnDemand command, sut –set mode=<OnDemand/AutoDeploy/ AutodeployReboot>

Ref: https://support.hpe.com/hpsc/doc/public/display?docId=a00059716en_us  , Page 11

If you feel this was helpful please click the KUDOS! Thumbs below!

Regards

Ronny

[cprinz]

Hi Ronny,

so SUT is useful on Gen10?

Is it also useful for Synergy? I think so but just to be sure :)

Regards,

cprinz

[ronissac]

Yes it can be very useful to stage, install and Activate Driver and firmware updates across the hosts

Ronny

[MCSAP]

Has anyone had luck updating firmware on a Gen10 using OneView and the embedded iSUT agent in ESXi 6.7?

Error I'm getting in OneView when changing the Server Profile FW baseline:

Issue 

Firmware update using Smart Update Tools is not currently supported for this server hardware, when the OS deployed is ESXi.

Resolution 

Retry the operation by selecting the "Firmware only" option in the server profile.

[MCSAP]

Ronny,

Have you had success updating firmware with OneView for Gen10 ESXi 6.7 hosts?  If so, please share detail steps you followed along with configuration parameters of SUT, OneView Profile Settings, and any other items not clear from the HPE documenetation. :-)