Known issues
Issue 1
Description
Unable to retrieve the health and hardware inventory from the target iDRAC.
Workaround
Ensure that the following are enabled or available on the target node:
- The Redfish service is enabled.
- An iDRAC user slot is available.
- The SMB port 445 is open.
- For management of PowerEdge servers, ensure that OMIMSWAC uses an internal OS to iDRAC Pass-through interface. By default, iDRAC will be 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 like VMFleet is installed), OMIMSWAC might not be able to communicate to the iDRAC from the host OS.
To resolve the conflict, log in to iDRAC and change the USB NIC IP address under the OS to iDRAC passthrough section. For more information about assigning this IP address, see the iDRAC documentation on the Dell EMC support site.
- Ensure that the target node is not booted to Lifecycle Controller.
- Target node is not in the reboot state, or is powered-off.
- The USB NIC adapter is not disabled on the target node operating system.
Issue 2
Description
For YX3X and YX2X models of PowerEdge servers with firmware versions lesser than 2.60.60.60, and YX4X model of PowerEdge Servers with firmware versions lesser than 3.30.30.30, information of the following components are not displayed:
- Health status: memory, storage controllers, storage enclosures, and physical disks.
- Hardware inventory: memory, storage controllers, storage enclosures, physical disks, network devices, and firmware.
Workaround
- Ensure that the YX3X and YX2X models of PowerEdge servers are updated with latest iDRAC version of 2.60.60.60 or later.
- Ensure that the YX4X model of PowerEdge Servers are updated with latest iDRAC version of 3.30.30.30 or later.
Issue 3
Description
The overall health status of the PowerEdge servers, failover cluster and HCI cluster might be displayed as critical or warning even if the components of the nodes displayed on the Windows Admin Center are healthy.The health status of physical disks attached to embedded SATA controller may be displayed as Unknown because iDRAC is unable to get the health information for these disks.
Workaround
For more details on the components in critical health state, go to the respective iDRAC console.
Issue 4
Description
While installing OMIMSWAC by using local path or network path, multiple instances of OMIMSWAC extension may be listed under Available and Installed Extensions when more than one .nupkg package is available in the specified folder path, or the .nupkg packages are available in root or subfolders in addition to the folder path provided under
.
Workaround
Ensure that a single .nupkg package is available in the root or subfolders under
.
Issue 5
Description
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.”
Workaround
Disable the lockdown mode on the target node managed by Dell EMC OpenManage Integration.
Issue 6
Description
The update compliance report might not be generated for the cluster nodes.
Workaround
- Ensure that the cluster service is running on the cluster node by using the
Get -ClusterService PowerShell command.
- Ensure that the cluster node is not rebooting or powered-off.
Issue 7
Description
The hardware inventory attribute values of storage enclosure components might be empty because the information is not available on the target iDRAC.
Issue 8
Description
Retrieving inventory from servers and cluster nodes fails with the error: Unable to initialize the OMIMSWAC extension.
Workaround
Ensure IPMI driver is installed and IPMI service is running on the target node. For more information on the requirement and solution, see https://kb.dell.com/infocenter/index?page=content&id=SLN318718
Issue 9
Description
If NICs are disabled in BIOS settings, there will be a delay in displaying the health and hardware inventory information for certain iDRAC firmware versions.
Workaround
Ensure all the NICs are enabled in BIOS settings.