Health, hardware, and iDRAC inventory
Unable to copy the required files to the target node to fetch inventory information.
Ensure that:
- Target node is not in the reboot state and is powered on.
- Firewall is not blocking communication through SMB port 445. For more information, see
prepare your environment for Windows Admin Center.
- The USB NIC adapter is not disabled on the target node operating system.
Unable to fetch the health and hardware inventory from iDRAC
To fetch the health and hardware inventory information from iDRAC, ensure that:
- YX3X and YX2X models of PowerEdge servers are updated with latest iDRAC version of 2.60.60.60 or later.
- YX4X models of PowerEdge Servers are updated with latest iDRAC version of 3.30.30.30 or later.
- For management of PowerEdge servers, OMIMSWAC uses an internal operating system to iDRAC Pass-through interface. By default, iDRAC is reachable using the IP address 169.254.0.1/<Subnet> or 169.254.1.1/<Subnet>. However, if the host has another network interface in the same subnet (for example, when tool such as VMFleet is installed), OMIMSWAC might not be able to communicate to the iDRAC from the host operating system.
To resolve the conflict, log in to iDRAC and change the USB NIC IP address under the operating system to iDRAC passthrough section. For more information about assigning this IP address, see the iDRAC documentation on the support site.
- For management of Clusters, all the cluster nodes are reachable using IP address, Hostname, and Fully Qualified Domain Name (FQDN) before managing the cluster with OMIMSWAC.
- If the Redfish service is disabled, enable the Redfish service by using iDRAC UI. For more information, see the iDRAC documentation on Dell EMC support site.
- User slots are available on iDRAC to create new users.
Health and hardware inventory of YX2X, YX3X, and YX4X models of PowerEdge servers not displayed
- Ensure that YX3X and YX2X models of PowerEdge servers are updated with latest iDRAC version of 2.60.60.60 or later.
- Ensure that YX4X models of PowerEdge Servers are updated with latest iDRAC version of 3.30.30.30 or later.
Overall health status shows warning or critical while health status of node components shows healthy
The overall health status of PowerEdge servers, failover clusters, and HCI clusters might be displayed as critical or warning even if the components of the nodes displayed on the Windows Admin Center are healthy. Because the health status of physical disks that are attached to embedded SATA controller may be displayed as Unknown as iDRAC is unable to get the health information for these disks.
For more details on the components in critical health state, go to the respective iDRAC console.
Unable to create users on target iDRAC device
If the lockdown mode is enabled on YX4X model of PowerEdge Servers and above, inventory of health, hardware, and iDRAC fails with the error: “Unable to create users on target iDRAC device.”
Resolution: Disable the lockdown mode on the target node managed by Dell EMC OpenManage Integration.
Unable to initialize the OMIMSWAC extension.
Retrieving inventory from servers and cluster nodes may fail with the error: Unable to initialize the OMIMSWAC extension.
Resolution: Ensure the IPMI driver is installed, and the IPMI service is running on the target node. For more information on the requirement and solution, see
Dell information center.
Cluster-Aware Updating
Job failed while downloading the required components for the update compliance operation
While downloading the DSU and IC tools, the update jobs may fail due to various reasons. Probable causes and solutions are given below:
- Cause: While exporting the repository by using Dell EMC Repository Manager (DRM), the export job may complete with status as "Partially succeeded." In this case, one or more DUPs may be missing from the repository.
Resolution: Retry exporting the repository in DRM and ensure that the job is successfully completed.
- Cause: One or more components may not be downloaded when the 'update source' is selected as an online source.
Resolution: Ensure that there is Internet connectivity and retry downloading the catalog from the online source. For more information, see Dell EMC Repository Manager user guide.
Unable to download the DUP(s)
-
Ensure to access the Windows Admin Center remotely using domain user credentials. Otherwise, use local administrator credentials to access the WAC locally. For more information, see
Microsoft documents.
- Check your Internet connection or proxy configuration.
Unable to generate compliance report
- Cause: When you connect to a target node or cluster using Single-Sign-on rather than 'Manage as' and generate compliance report using OMIMSWAC, the compliance generation may fail.
Resolution: Before connecting to the target node or cluster, ensure that you select "Manage as" and provide appropriate Server Administrator or Cluster Administrator accounts.
- Cause: When generating a compliance report, the compliance report generation may fail with the following error in the log:
Starting a command on the remote server failed with the following error message : The WinRM client sent a request to the remote WS-Management service and was notified that the request size exceeded the configured MaxEnvelopeSize quota. For more information, see the about_Remote_Troubleshooting Help topic.
Resolution: Ensure that:
- Network connectivity between the gateway system and the target node is intact.
- File copying works between the gateway system and the target node. To check this:
- Create a session based on target node credential by executing the following PowerShell command:
$SecurePassword = convertto-securestring <password> -asplaintext -force
$credential = New-Object System.Management.Automation.PSCredential -ArgumentList <userid>, $SecurePassword
$session = New-PSSession -ComputerName <MN FQDN> -Credential $credential -ErrorAction SilentlyContinue
- Copy a test file to the failed target node assuming "Test.txt" is in C:\ drive
Copy-Item -Path "C:\Test.txt" -Destination "C:\" -Recurse -Force -ToSession $session
- If the problem persists after performing the above actions, try restarting the Windows Remote Management (WS-Management) service in the target node (file copy is failing) then re-run the compliance.
- Cause: When generating a compliance report for a cluster, the compliance report generation may fail for cluster nodes.
Resolution: Ensure that:
- The cluster service is running on the cluster node by using the
Get-ClusterService PowerShell command.
- The cluster node is not rebooting or in the powered-off state.
- When adding a cluster to the Windows Admin Center, ensure to use the cluster name in FQDN format.
- Cause: When generating a compliance report using Windows 10 Microsoft Edge browser, the compliance report generation may fail with the following error:
Unable to generate compliance report. The Manage As credentials have not been set or are not in domain\user format.
Resolution: Do any of the followings:
- Connect the target node with credentials using Fully Qualified Domain Name (For example,
domain.lab\username) or Top Level Domain (For example,
domain\username).
- Clear the cache memory of the browser and rerun the compliance.
- Ensure that the DNS is configured properly in the WAC installed system to connect to the target node with right credentials.
- Cause: Compliance report generation may fail with the following error
Unable to install Dell System Update(DSU) package for the server/cluster because DSU installation operation is already in progress for another server/cluster. This occurs because, a user may be trying to run compliance concurrently from two different instances/sessions. For example, one instance by clicking the pop-out button and another instance by using the browser from the same gateway at the same time. One of the instance/sessions that was triggered first proceeds for compliance/update; while another results in an error.
Resolution: Run only one compliance/update for a target node/cluster at a time using one gateway instance.
Compliance report page on loading state for a long time
While generating a compliance report, the compliance report page may show up in the loading state even after the notification of successfully generated update compliance report.
In this case, go to any of the other tabs such as "Settngs", "Inventory", and so forth,, and then go back to the Update tab, where you will see the generated compliance report.
Job failed while updating the selected components
Sometimes, CAU or target node updates may fail due to various reasons. The causes and resolutions are given below:
- Causes: If target nodes are not validated before triggering CAU, the CAU may fail.
Resolution: For Cluster-Aware Updating, ensure to validate the cluster before triggering CAU. For more information about validating a cluster, see Microsoft document
Validate Hardware for a cluster.
- Causes: If Failover Clustering feature and Failover Clustering Tools are not installed on target nodes, the CAU may fail.
Resolution: As OMIMSWAC uses the Microsoft Cluster-Aware Updating feature framework to perform cluster updates, before updating a cluster using OMIMSWAC, ensure that the Failover Clustering feature and Failover Clustering Tools are installed on all the target nodes. For more information, see
CAU requirements and best practices in Microsoft documents.
To check whether failover clustering tools are running on all the target nodes, from the PowerShell window on the target node, run the
Get-CauClusterRole PowerShell command.
- Cause: Compliance Inventory file is not available for some nodes or file copying from node to gateway is failed after compliance generation.
Resolution: Rerun the compliance.
- Cause: Due to Internet connectivity issue, the followings may fail:
- Signature verification of DSU or IC
- Downloading of online catalog
- Downloading of DUP
If any of the above fails, CAU or server update also fails.
Resolution: Ensure that there is Internet connectivity and rerun compliance and update.
- Cause: DSU installer is not cleared from a node because the installer file sometimes gets locked by the Windows Admin Center process (sme.exe).
Resolution: Restart the Windows Admin Center service from Windows Services consoles.
- Cause: CAU fails if any of the disks is not in healthy state.
Resolution: Ensure both physical and virtual disks are in healthy state before triggering CAU. If any disk is in an unhealthy healthy state, see the
Microsoft document to get it to a healthy state.
- Cause: CAU fails if any of the cluster nodes is paused.
Resolution: Resume cluster nodes (Failover roles) before triggering CAU.
- Cause: CAU fails when Failover Clustering feature and Failover Clustering Tools are not installed on all the target nodes.
Resolution: Ensure Failover Clustering feature and Failover Clustering Tools are installed on all the target nodes before performing CAU. For more information, see
https://docs.microsoft.com/en-us/windows-server/failover-clustering/cluster-aware-updating-requirements.
CredSSP Failure
Check the event viewer logs in the gateway system to ensure that CredSSP has not failed during Cluster-Aware Updating. If the CredSSP fails, following are the probable causes and solutions:
- Cause: While updating a cluster, credential delegation using CredSSP may fail.
Resolution: Reconnect the cluster using fully qualified domain name, and click
Use this credential for all servers check box.
For example, if the domain name is test.dev.com, use
test.dev.com\administrator as the domain name, and then click
Use this credential for all servers check box.
- Cause: When using CredSSP authentication to run scripts on a remote machine, the update job may fail with an error.
The issue is because CredSSP has been disabled in the gateway machine.
Resolution: To resolve the issue, follow the steps below:
- From PowerShell window, run
gpedit
- In the Group Policy Editor window,
- Select
Allow delegating fresh credentials with NTLM-only server authentication and enable it.
- Run
gpupdate /force in the PowerShell.
The Dell EMC Update Package (DUP) may fail to update components after you trigger an update. There are various reasons for the DUP to fail during the update. Look at the following possible solutions to resolve the issue:
- In Windows Admin Center (WAC) installed machine, check the log files to get more information regarding DUP download failure and component mapping. The component mapping is provided to identify the component (selected for update) in the DUP catalog. The log files are at the following path.
Gateway system:
- Server update:
<Windows Directory>\ServiceProfiles\NetworkService\AppData\Local\Temp\generated\logs\<PrepareUpdate XXXX>
- CAU:
<Windows Directory>\ServiceProfiles\NetworkService\AppData\Local\Temp\generated\logs\Update XXXX
Windows 10 gateway system:
- Server update:
<Windows installed drive>\Users\<user_name>\AppData\Local\Temp\generated\logs\<PrepareUpdate XXXX>
- CAU:
<Windows installed drive>\Users\<user_name>\AppData\Local\Temp\generated\logs\Update XXXX
- Sample log messages are given below:
- DUP download failure error log
28-Apr-2020 12:19:18 AM::: Error >>> Message : DUPs for some of the selected components are not present in DRM repository.
- Component mapping log file
## Format: :>> Component Name -> Package Name
:>> [0001] Broadcom NetXtreme Gigabit Ethernet -> Network_Firmware_RG25N_WN64_21.60.2_01.EXE
- In the target node, refer component mapping and find the component related DUP log file and check the return code that is specified in
<Windows Directory>\Dell\UpdatePackage\log\<Package Name>. See Dell EMC Update Package user guide for cause and possible resolution.
A return code sample of a DUP failure scenario is given below:
Exit code = 1 (Failure)
2020-04-21 23:48:27
Update Package finished. Exit code = 1
- The DUP may fail when attempting to downgrade a driver component to a lower version. In this case, uninstall the driver from the operating system then rerun the component update from OMIMSWAC. For more information about how to uninstall drivers, see Microsoft document.
- After cluster update, you may see components showing as non-compliant. This happens because of DUP failure.
Resolution: In this case, check the cleanup logs having the DSU logs to see if there is any ERROR for those components. If there is any prerequisite that is required for the component before update, follow the prerequisite and then rerun the update.
Alternatively, you can also try the followings:
- Reset and update the iDRAC to version 4.20.20.20 or higher and then rerun the update. For more information about how to Reset or update iDRAC, see iDRAC documentation.
- Run the update manually in the target node by downloading from the path specified in
<Windows Directory>\Dell\UpdatePackage\log\<Package Name> in the DUP log. Example for a network firmware is
https://downloads.dell.com/FOLDER06091050M/1/Network_Firmware_TWFF6_WN64_16.26.60.00.EXE.
- Ensure that the selected DUP is supported on the selected operating system and platform by searching the component name in the Dell Support site. Dell support site URL:
https://www.dell.com/support/home/in/en/inbsd1/?app=products.
Full Stack Cluster-Aware Updating
Couldn't configure cluster aware updates
Cause: To perform full stack updates, in Windows Admin Center, when you select
Updates from the
Tools menu, an error might occur:
Couldn't configure cluster aware updates. This error occurs because CAU clustered role could not be added to the cluster for update.
Resolution: As a workaround, you can add the cluster role manually using the following PowerShell command before triggering the full stack update:
Add-CauClusterRole -StartDate "02-03-2021 3:00:00 AM" -DaysOfWeek Tuesday -WeeksOfMonth 3 -EnableFirewallRules -RequireAllNodesOnline -Force
For more information, see
Configure the nodes for remote management in Microsoft documents.
Couldn't query readiness for cluster aware updates
Cause: To perform full stack updates, in Windows Admin Center, when you select
Updates from the
Tools menu, an error might occur:
Couldn't query readiness for cluster aware updates. This error occurs because of CredSSP failure.
Resolution: As a workaround, see
CredSSP failure to find the cause and solution.
For more information, see the
Microsoft document.
Tests Summary page appears
While triggering full stack updates, Tests Summary page may appear.
Resolution: As a workaround, verify if pre-update or post-update script are part of the cluster role. If 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 prerequisites required for cluster update, see the
Microsoft document.
Update status takes longer to refresh
During full stack cluster updates, the update status that is shown in the
Updates page may take longer to refresh. In this case, it is recommended to stay on the Updates page and wait for the update to complete. The update status will automatically be displayed once the update is complete. For more information about Microsoft recommendations, see the
Microsoft document.
Full stack update may fail with failover cluster tool extension 1.271.0 nupkg
During full stack cluster updates in Azure Stack HCI clusters, the update may fail with an exception Error: RemoteException: Exception calling "Add" with "2" argument(s): "Item has already been added. Key in dictionary: 'PreUpdateScript' Key being added: 'PreUpdateScript'". This issue occurs when Microsoft Failover Cluster Tool Extension 1.271.0 is installed. Due to this issue, both hardware and OS cluster-aware updates (Full stack update) cannot be performed together.
Resolution: Upgrade to the latest Microsoft Failover Cluster Tool Extension 1.280.0.nupkg available in the Microsoft feed to perform full stack cluster update.
Others
OpenManage Integration access denied
Cause: When you log in to Windows Admin Center (WAC) using gateway user credentials without admin privileges and try to launch OpenManage Integration from the WAC console, access denied error may appear.
Resolution: Before you launch Dell EMC OpenManage Integration extension in Windows Admin Center, ensure to log in to WAC as a gateway administrator.
Test-Cluster fails with network communication errors
Cause: With USB NIC enabled in iDRAC, if you run Test-Cluster command to verify the cluster creation readiness or cluster health, you may see an error in the validation report. The error states 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.
Resolution: Disable the USB NIC (labeled as Ethernet by default) temporarily before running the Test-Cluster command.
USB NIC network shows as partitioned cluster network
Cause: When the USB NIC is enabled in iDRAC, cluster networks in the failover cluster manager show the networks that are associated with the USB NIC as partitioned. This issue occurs as cluster communications are enabled by default on all network adapters and USB NIC IPv4 addresses cannot be used to communicate externally, thus disrupting cluster communication on those NICs. This error can be safely ignored.
Resolution: Disable cluster communication with the networks associated with the USB NICs from the cluster manager.
Acceptance Failed to save: Dell EMC Software License Agreement and Customer Notice
Cause: Dell EMC Software License Agreement and Customer Notice acceptance may fail to save. This may happen when you launch multiple instances of the Dell EMC OpenManage Integration extension from the same gateway, and accept terms and conditions in one instance. In the remaining instances, if you attempt to accept the terms and conditions, you will encounter this error.
Resolution: Navigate away from the Dell EMC OpenManage Integration extension where this issue occurs, and then back in to resolve this issue.
