By using the HCP Compliance feature, you can see the cluster compliance using HCI Configuration Profile (HCP) checks, see the recommendations, and remediate noncompliant components.
Before you begin, the cluster:
- Must be Dell Integrated System for Microsoft Azure Stack HCI, version 22H2.
- Nodes must have a valid OMIWAC premium license installed.
- Mode models are listed as supported in the support matrix.
To run HCP Compliance check in OpenManage Integration extension, perform the following steps by selecting the single node cluster in the Cluster Manager.
- Select View > Compliance. From the drop-down menu, select HCP. The Compliance Summary page appears. If the Check Compliance button is enabled, go to step 3.
- If the Check Compliance button is disabled, ensure:
- Requirements that are mentioned in the prerequisites are met.
- Required inputs are provided in the Configure Cluster Settings tab. If not, choose the network topology and the deployment model, and click Save to save the settings for future use. These settings are required to generate compliance for Dell OS Configuration policies.
- Network topology
- Fully-converged: All storage ports from the server are connected to the same network fabric. Within the host operating system, the NIC ports are used for both storage and management/VM traffic.
- Non-converged-Physical: Storage traffic is on the physical storage network adapter ports and management/VM traffic goes through a SET that is created using network ports of the server rNDC.
- Non-Converged-Set: Storage traffic uses virtual adapters in the host operating system that is connected to a SET.
- Deployment model
- Scalable model supports from 2 to 16 nodes in a cluster and uses top-of-rack switches for management and storage traffic networking.
- Switchless model uses full mesh connections between the cluster nodes for storage traffic and supports from 2 to 4 nodes in a cluster.
- Stretch cluster with Azure Stack HCI consists of servers residing at two different locations or sites, with each site having two or more servers, replicating volumes either in synchronous or asynchronous mode.
- Network topology
- Click Check Compliance to View HCP Compliance Summary.
- Optional: If Internet connection is not available, perform the following steps to run HCP check in offline mode:
- Download the HCPMetaData.json and HCPMetaData.json.sign files from Dell Technologies Downloads > OMIMSWAC > ASE.
- Place these files in C:\Users\Dell\HCPMetaData folder in the gateway system where Windows Admin Center is installed.
- Run the HCP compliance check.
OpenManage Integration extension fetches the applicable policies, validates the cluster node(s) attributes with the policy attributes, and displays the compliance summary.
- Optional: If Internet connection is not available, perform the following steps to run HCP check in offline mode:
- Click Fix Compliance to fix noncompliant policies. CAUTION: Fix Compliance is disabled if Dell Hardware Symmetry Policy is noncompliant with a critical error. In this case, you are not allowed to remediate other policies. Review the recommendations and show details, and contact Dell.com/support to resolve the issue before proceeding to the next step. The critical error states that this aspect of nodes configuration is not supported. You must correct the issue before you can deploy a symmetric HCI cluster.
- Manual Fixes include policies that require physical interventions and recommendations that can be remediated manually. Note: Ensure that your cluster is compliant with Dell Hardware Symmetry Policy and Dell OS Configuration Policies otherwise the cluster performance is not guaranteed.
- Automatic Fixes include policies that can be remediated using OpenManage Integration extension.
- Manual Fixes include policies that require physical interventions and recommendations that can be remediated manually.
- If any of the policy fixes require a cluster reboot, choose the reboot option to apply the configurations by restarting your cluster in a cluster-aware updating format.
- Apply and Reboot Now: Applies BIOS, NIC, and iDRAC attributes concurrently to all the cluster nodes now and restart the cluster in cluster-aware update manner.
- Apply at Next Reboot: Applies BIOS, NIC, and iDRAC attributes concurrently to all the cluster nodes when cluster nodes are restarted at the next maintenance window.
- Click the Schedule Reboot checkbox to schedule the date and time when BIOS, NIC, and iDRAC attributes are applied concurrently to all the cluster nodes and restart the cluster in cluster-aware update manner. Note: If you select to apply the changes at the next reboot, ensure to disable the infrastructure lock before the next reboot starts to successfully apply the changes.
- Click the Schedule Reboot checkbox to schedule the date and time when BIOS, NIC, and iDRAC attributes are applied concurrently to all the cluster nodes and restart the cluster in cluster-aware update manner.
- If the infrastructure lock is enabled, a window appears to disable the lock and then proceed. To allow the OpenManage Integration extension automatically to lock the infrastructure after the operation is complete, select Allow OMIMSWAC to re-enable the infrastructure lock after the operation is complete.
- When finished, click Apply to trigger the update.
- If Kernel Soft Reboot is enabled for the cluster, the OpenManage Integration extension ignores this setting and performs a full reboot to apply all the BIOS-related settings. See When to use Kernel Soft Reboot.
- The operation enables the CredSSP. To improve the security, disable the CredSSP after the operation is complete.
- Click View Details to see the update status and progress at node level.
After the status is succeeded, OpenManage Integration extension rechecks the compliance and displays the updated compliance summary.
- Click Export compliance summary to export the HCP compliance report in an Excel file which can be useful while contacting the Dell Technologies support team.