Skip to content

Commit b59a057

Browse files
Update Blog “configure-isut-and-ams-for-vlcm-based-firmware-updates-on-gen-12-servers”
1 parent 1bbc38f commit b59a057

File tree

1 file changed

+12
-16
lines changed

1 file changed

+12
-16
lines changed

content/blog/configure-isut-and-ams-for-vlcm-based-firmware-updates-on-gen-12-servers.md

Lines changed: 12 additions & 16 deletions
Original file line numberDiff line numberDiff line change
@@ -14,24 +14,20 @@ tags:
1414
---
1515
<style> li { font-size: 27px; line-height: 33px; max-width: none; } </style>
1616

17+
HPE Gen12 servers introduce enhanced security by supporting only High Security modes (SecureStandard, CNSA, FIPS). This impacts how you configure Intelligent System Update Tool **(iSUT)** and Agentless Management Service **(AMS)** for vSphere Lifecycle Manager **(vLCM)** based firmware updates.
1718

19+
Unlike previous generations, configuration through the HPE OneView for VMware vCenter **(OV4VC)** and HPE Compute Ops Management plug-in for VMware vCenter **(COM4VC)** vLCM Pre-Check page is not available in these modes, as iLO credentials are now required. Instead, you must manually configure AMS and iSUT by creating an application account and providing valid HPE iLO credentials.
1820

1921
In this blog post, I’ll show you how to configure iSUT and AMS to enable vLCM-based firmware updates on HPE Gen12 servers.
2022

21-
22-
23-
HPE Gen12 servers introduce enhanced security by supporting only High Security modes (SecureStandard, CNSA, FIPS). This impacts how you configure Intelligent System Update Tool (**iSUT**) and Agentless Management Service (**AMS**) for vSphere Lifecycle Manager **(vLCM)** based firmware updates.
24-
25-
Unlike previous generations, configuration through the HPE OneView for VMware vCenter (**OV4VC**) and HPE Compute Ops Management plug-in for VMware vCenter (**COM4VC**) vLCM Pre-Check page is not available in these modes, as iLO credentials are now required. Instead, you must manually configure AMS and iSUT by creating an application account and providing valid HPE iLO credentials.
26-
2723
- - -
2824

2925
## **Prerequisites**
3026

31-
* HPE Gen12 server with iLO 7.
32-
* vSphere environment with vLCM enabled.
33-
* iLO credentials with sufficient privileges.
34-
* Access to server CLI (SSH or local console).
27+
* HPE Gen12 server with iLO 7
28+
* vSphere environment with vLCM enabled
29+
* iLO credentials with sufficient privileges
30+
* Access to server CLI (SSH or local console)
3531

3632
- - -
3733

@@ -75,20 +71,20 @@ For VMware environments, create the AMS application account:
7571

7672
## **Step 4: Verify Application Account in iLO**
7773

78-
1. Open the **iLO GUI**.
79-
2. Navigate to **iLO Settings** > **User Management** > **Users**.
80-
3. Select **Application Account**.
81-
4. Confirm the application account details are present.
74+
1. Open the **iLO GUI**
75+
2. Navigate to **iLO Settings** > **User Management** > **Users**
76+
3. Select **Application Account**
77+
4. Confirm the application account details are present
8278

8379
- - -
8480

85-
## **Step 5: Check AMS Status in iLO GUI**
81+
## **Step 5: Check AMS status in iLO GUI**
8682

8783
* Ensure AMS status is reported as **Available** in the iLO GUI.
8884

8985
- - -
9086

91-
## **Step 6: Verify iSUT and AMS Status in vSphere**
87+
## **Step 6: Verify iSUT and AMS status in vSphere**
9288

9389
1. Log in to **VMware vSphere**.
9490
2. Select the required **cluster** and click the **Configure** tab.

0 commit comments

Comments
 (0)