Release Notes

Known issues

Issue 1

Description

Unable to fetch the health and hardware inventory from target iDRAC.

Workaround

Ensure the following are enabled or available on the target node.

• The Redfish service is enabled.

• An iDRAC user slot is available.

• SMB port 445 is open. For more information, see https://go.microsoft.com/fwlink/?linkid=2101556.

• For management of PowerEdge servers, 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 OS.

Issue 2

Description

For 12th and 13th generation of PowerEdge servers with firmware versions lesser than 2.60.60.60, and 14th generation 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 12th and 13th generation of PowerEdge servers are updated with latest iDRAC version of 2.60.60.60 or later.

• Ensure that the 14th generation 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 and HCI cluster might be displayed as critical or warning even though the components

of the nodes displayed on the Windows Admin Center are healthy.

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 might be listed under

Available and Installed Extensions when more than one .nupkg packages are available in the specified folder path, or the .nupkg packages

are available in root or subfolders in addition to the folder path provided under Feeds > Add package source.

Workaround

Known issues 7