Skip to content

Commit 536f7cc

Browse files
Update Blog “configure-isut-and-ams-for-vlcm-based-firmware-updates-on-gen-12-servers”
1 parent 4359aeb commit 536f7cc

File tree

1 file changed

+90
-3
lines changed

1 file changed

+90
-3
lines changed

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

Lines changed: 90 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -5,8 +5,95 @@ author: Vijayakannan M
55
authorimage: /img/Avatar1.svg
66
disable: false
77
---
8-
<!--StartFragment-->
8+
# How to Configure iSUT and AMS for vLCM-Based Firmware Updates on HPE Gen12 Servers (High Security Mode)
99

10-
Provide step-by-step instructions to configure iSUT (Intelligent System Update Tool) and AMS (Agentless Management Service) to enable vSphere Lifecycle Manager (vLCM) based firmware updates on HPE Gen 12 servers. Include prerequisites, configuration commands, and any best practices for ensuring successful integration and updates.
10+
HPE Gen12 servers introduce enhanced security by supporting only High Security modes (SecureStandard, CNSA, FIPS). This impacts how you configure **iSUT** (Intelligent System Update Tool) and **AMS** (Agentless Management Service) for **vSphere Lifecycle Manager (vLCM)** based firmware updates. Unlike previous generations, configuration via the vLCM Pre-Check page is not available in these modes due to credential requirements. Instead, you must manually configure AMS and iSUT by creating an application account and providing valid HPE iLO credentials.
1111

12-
<!--EndFragment-->
12+
- - -
13+
14+
## **Prerequisites**
15+
16+
* HPE Gen12 server with iLO 7
17+
* vSphere environment with vLCM enabled
18+
* iLO credentials with sufficient privileges
19+
* Access to server CLI (SSH or local console)
20+
21+
- - -
22+
23+
## **Step 1: Create an Application Account on iLO 7**
24+
25+
Application accounts are service accounts in iLO 7, used by host applications (like iSUT and AMS) to securely authenticate and communicate with iLO.
26+
27+
**To create an application account using CLI:**
28+
29+
```shell
30+
sut appaccount create -u <ilo_username> -p <ilo_password>
31+
```
32+
33+
**Alternatively, to provide iLO credentials directly (not recommended for production):**
34+
35+
```shell
36+
sut -set ilousername=<ilo_username> ilopassword=<ilo_password>
37+
```
38+
39+
- - -
40+
41+
## **Step 2: Set iSUT Mode to AutoDeploy**
42+
43+
Set the iSUT mode to `AutoDeploy` to enable automated firmware updates:
44+
45+
```shell
46+
sut -set mode=AutoDeploy
47+
```
48+
49+
- - -
50+
51+
## **Step 3: Configure AMS Application Account (for VMware)**
52+
53+
For VMware environments, create the AMS application account:
54+
55+
```shell
56+
amsdCli appaccount create -u <ilo_username> -p <ilo_password>
57+
```
58+
59+
- - -
60+
61+
## **Step 4: Verify Application Account in iLO**
62+
63+
1. Open the **iLO GUI**.
64+
2. Navigate to **iLO Settings** > **User Management** > **Users**.
65+
3. Select **Application Account**.
66+
4. Confirm the application account details are present.
67+
68+
- - -
69+
70+
## **Step 5: Check AMS Status in iLO GUI**
71+
72+
* Ensure AMS status is reported as **Available** in the iLO GUI.
73+
74+
- - -
75+
76+
## **Step 6: Verify iSUT and AMS Status in vSphere**
77+
78+
1. Log in to **VMware vSphere**.
79+
2. Select the required **cluster** and click the **Configure** tab.
80+
3. In the left panel, go to **Cluster > Configure > HPE Server Hardware**.
81+
4. On the **vLCM Pre-Check** panel, check the **iSUT mode** and **AMS state**.
82+
5. Refresh the page and confirm both statuses are **green**.
83+
84+
- - -
85+
86+
## **Best Practices**
87+
88+
* **Use application accounts** instead of direct credentials for better security.
89+
* **Regularly verify** AMS and iSUT status before updates.
90+
91+
- - -
92+
93+
## **Conclusion**
94+
95+
With AMS and iSUT properly configured, you are ready to proceed with vLCM-based firmware updates on HPE Gen12 servers, including both **ProLiant** and **Synergy** models. This ensures secure, automated, and compliant lifecycle management in high-security environments.
96+
97+
- - -
98+
99+
**Tip:** Always refer to the latest HPE and VMware documentation for updates on security practices and supported configurations.

0 commit comments

Comments
 (0)