Your Browser is Out of Date

Nytro.ai uses technology that works best in other browsers.
For a full experience use one of the browsers below
E2E Deployment and Operations Guide with Scalable Networking: Microsoft HCI Solutions from Dell Technologies
About using this guide Deployment Introduction Solution Overview Solution Deployment Scalable Architecture with Network ATC GPU Integration Day 1 operations Managing and monitoring clusters with Windows Admin Center Dell OpenManage Integration with Windows Admin Center
Dell OpenManage Integration with Windows Admin Center
Overview
Prerequisites for managing AX nodes
Installing the OMIMSWAC license
Managing Microsoft HCI-based clusters
Overview Prerequisite checks Health status Inventory Locating physical disks and viewing their status Viewing update compliance and updating the cluster
Full Stack Cluster-Aware Offline Updating
Full Stack Cluster-Aware Updating for Azure Stack HCI clusters
Updating a standalone node before adding it to the cluster
Enabling hardware alerts for HCI cluster
Secure cluster with Secured-core
Enabling operating system features
Protect your infrastructure with infrastructure lock
Enable or disable infrastructure lock
Manage CPU cores in Azure Stack HCI clusters
Expanding cluster from two nodes to three-node+ cluster
Validate and remediate Azure Stack HCI clusters
View HCP compliance summary
Onboard Dell policies to Azure Arc from Windows Admin Center
View recommendations for storage expansion
View node level storage configuration details
Known issues
Updates and maintenance Secure connect gateway References

Known issues

Home > Integrated Products > Microsoft HCI Solutions from Dell Technologies > Guides 22H2 and earlier > E2E Deployment and Operations Guide with Scalable Networking: Microsoft HCI Solutions from Dell Technologies > Known issues

Known issues

  • The following table lists known issues and workarounds related to OpenManage Integration with Microsoft Windows Admin Center with Microsoft HCI Solutions from Dell Technologies clusters.

    Note: For details about troubleshooting steps and known issues, see the Dell OpenManage Integration Version 3.0 with Microsoft Windows Admin Center User’s Guide at Dell Support | Documentation | OpenManage Integration with Microsoft Windows Admin Center.

    Table 9. Known issues
    Issue Resolution or workaround
    Running Test-Cluster fails with network communication errors.

    With USB NIC enabled in iDRAC, if you run the Test-Cluster command to verify the cluster creation readiness or cluster health, the validation report includes an error indicating that the IPv4 addresses assigned to the host operating system USB NIC cannot be used to communicate with the other cluster networks.     		This error can be safely ignored. To avoid the error, temporarily disable the USB NIC (labeled as Ethernet, by default) before running the Test-Cluster command.
    The USB NIC network appears as a partitioned cluster network.

    When the USB NIC is enabled in iDRAC, cluster networks in the failover cluster manager show the networks associated with the USB NIC as partitioned. This issue occurs because the cluster communication is enabled by default on all network adapters, and USB NIC IPv4 addresses cannot be used to communicate externally, which, therefore, breaks cluster communication on those NICs.     		Remove the USB NIC from any cluster communication by using the following script: 
    $rndisAdapter = Get-NetAdapter -InterfaceDescription 'Remote NDIS Compatible Device' -ErrorAction SilentlyContinue

        if ($rndisAdapter)
        
    {
            Write-Log -Message 'Remote NDIS found on the system. Cluster communication will be disabled on this adapter.'
            
            # Get the network adapter and associated cluster network
            $adapterId = [Regex]::Matches($rndisAdapter.InstanceID, '(?<={)(.*?)(?=})').Value
            $usbNICInterface = (Get-ClusterNetworkInterface).Where({$_.adapterId -eq $adapterId})
            $usbNICClusterNetwork = $usbNICInterface.Network

            # Disable Cluster communication on the identified cluster network
            (Get-ClusterNetwork -Name $usbNICClusterNetwork.ToString()).Role = 0
        }
    While triggering full stack updates, the Tests Summary page might appear. As a workaround, verify whether the pre-update or post-update scripts are part of the cluster role. If they are present, remove the scripts from the cluster node by running the following command in PowerShell: 
    Set-CauClusterRole -PreUpdateScript $null -PostUpdateScript $null
    For more information about the prerequisites required for a cluster update, see Update Azure Stack HCI clusters.
    The update status takes a long time to refresh. During full stack cluster updates, the update status shown in the Updates page might take a long time to refresh. If this issue occurs, it is recommended that you stay on the Updates page and wait for the update to complete. The update status will automatically be displayed once the update is complete.
    When using CredSSP authentication to run scripts on a remote machine, the update job might fail with an error. This failure occurs because CredSSP has been disabled in the gateway machine. To resolve the issue, follow these steps:
    1. From the PowerShell window, run gpedit.
    2. In the Group Policy Editor window, browse to Computer Configurations > Administrative Templates > System > Credentials Delegation.
    3. Select Allow delegating fresh credentials with NTLM-only server authentication and enable it.
    4. Run gpupdate /force in PowerShell.