You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
17
18
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.
18
20
19
21
In this blog post, I’ll show you how to configure iSUT and AMS to enable vLCM-based firmware updates on HPE Gen12 servers.
20
22
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
-
27
23
- - -
28
24
29
25
## **Prerequisites**
30
26
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)
35
31
36
32
- - -
37
33
@@ -75,20 +71,20 @@ For VMware environments, create the AMS application account:
75
71
76
72
## **Step 4: Verify Application Account in iLO**
77
73
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
82
78
83
79
- - -
84
80
85
-
## **Step 5: Check AMS Status in iLO GUI**
81
+
## **Step 5: Check AMS status in iLO GUI**
86
82
87
83
* Ensure AMS status is reported as **Available** in the iLO GUI.
88
84
89
85
- - -
90
86
91
-
## **Step 6: Verify iSUT and AMS Status in vSphere**
87
+
## **Step 6: Verify iSUT and AMS status in vSphere**
92
88
93
89
1. Log in to **VMware vSphere**.
94
90
2. Select the required **cluster** and click the **Configure** tab.
0 commit comments