Skip to content

Commit 9985026

Browse files
jagratacRam-srini
andauthored
Update the ACM mode doc (#422)
* Update the ACM mode doc * Updated indentation of deactivation * Updated indentation for code-block --------- Co-authored-by: Ramakrishna Srinivasamurthy <ramakrishna.srinivasamurthy@intel.com>
1 parent f30cd3d commit 9985026

File tree

2 files changed

+67
-0
lines changed

2 files changed

+67
-0
lines changed
563 KB
Loading

docs/user_guide/advanced_functionality/vpro_power_mgt.rst

Lines changed: 67 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -40,6 +40,73 @@ Assumptions & Recommendations
4040
- **Port Enablement:** Ensure that the 4433 network ports for Intel® AMT communication are open
4141
and not blocked by firewalls.
4242

43+
Activate vPro In ACM mode
44+
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
45+
46+
- `ACM mode certificate creation <https://device-management-toolkit.github.io/docs/2.32/GetStarted/Cloud/createProfileACM/#provisioning-certificate>`_
47+
48+
ACM (Admin Control Mode) activation requires a provisioning certificate issued by a trusted Certificate Authority (CA).
49+
This certificate must be rooted in one of the trusted CAs embedded in the Intel AMT firmware (e.g., Comodo, DigiCert, GoDaddy, or VeriSign).
50+
51+
To obtain and prepare the certificate:
52+
53+
**Purchase a provisioning certificate** from a CA whose root certificate hash is listed in Intel AMT's trusted root store.
54+
The certificate must match the domain suffix configured in the AMT BIOS (MEBx) settings.
55+
56+
**Export the certificate** in PFX/PKCS#12 format, including the full certificate chain and private key.
57+
58+
**Note the certificate password** — it will be required when creating the AMT domain profile via ``orch-cli``.
59+
60+
.. note::
61+
62+
The domain suffix in the certificate's Common Name (CN) or Subject Alternative Name (SAN) must match the
63+
PKI DNS suffix configured in the edge node's MEBx settings.
64+
65+
- BIOS configuration for ACM mode
66+
67+
Ensure the edge node's BIOS is configured for ACM mode with Domain suffix in Remote configuration settings.
68+
69+
Advanced > MEBx > {Enter MEBx Password- default is "admin"} > Intel AMT Configuration > Network Access State > Full Unprovision
70+
Advanced > MEBx > {Enter MEBx Password- default is "admin"} > Intel AMT Configuration > Remote Setup and Configuration > PKI DNS Suffix > Set to your domain suffix (e.g., "example.com")
71+
72+
.. figure:: images/Vpro-BIOS-settings.png
73+
:alt: BIOS ACM configuration settings
74+
75+
- Domain creation
76+
77+
.. code-block:: bash
78+
79+
orch-cli create amtprofile <domain_name> \
80+
--project ${PROJECT_NAME} \
81+
--cert 'Domain-certificate.pfx' \
82+
--cert-pass cert-password \
83+
--cert-format string \
84+
--domain-suffix <Domain-suffix> \
85+
--api-endpoint https://api.${CLUSTER_FQDN}
86+
87+
- ACM Activation command
88+
89+
.. code-block:: bash
90+
91+
orch-cli set host ${HOST_ID} \
92+
--project ${PROJECT_NAME} \
93+
--api-endpoint https://api.${CLUSTER_FQDN} \
94+
--amt-state provisioned \
95+
--control-mode admin
96+
97+
- ACM mode Deactivation - Once the operation is complete, you can deactivate ACM mode using the following command
98+
99+
.. code-block:: bash
100+
101+
orch-cli set host ${HOST_ID} \
102+
--project ${PROJECT_NAME} \
103+
--api-endpoint https://api.${CLUSTER_FQDN} \
104+
--amt-state unprovisioned
105+
106+
.. note::
107+
Ensure that deactivation completes successfully. If it does not, the host may enter a limbo state and cannot be reactivated.
108+
In that case, you must clear the system CMOS to reset the Intel® vPro® state before activating again.
109+
43110
Power Operations
44111
----------------------------
45112

0 commit comments

Comments
 (0)