Functional area | Limitation | Affected Platforms/Models |
---|---|---|
Health and Hardware inventory | Information of the following components are not displayed:
Workaround:
|
|
Installation | 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
Workaround: Ensure that a single .nupkg package is available in the root or subfolders under . |
.
Not applicable |
Health, Hardware, and iDRAC inventory | If the lockdown mode is enabled on YX4X models of
Dell PowerEdge servers, inventory of health, hardware, and iDRAC fails with error: “Unable to create users on target iDRAC device.
Workaround: Disable the lockdown mode on the target node managed by Dell OpenManage Integration extension. |
YX4X models of Dell PowerEdge servers |
Hardware inventory | The attribute values of hardware inventory information for storage enclosure components might be empty because the information is not available on the target iDRAC. | Not applicable |
Health and Hardware inventory | 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. |
Not applicable |
Hardware inventory | For PCIe SSD Backplane of storage enclosures, few attribute values might not be available. | Not applicable |
Hardware inventory | For embedded network adapters, few properties or FRU objects are not available through Redfish. For more information about the fixes, see iDRAC9 with Lifecycle Controller Release Notes on the support site. | Not applicable |
Update | During the update compliance operation, to select or clear the noncompliant components, you can navigate back to the Complaince Details tab from the Summary tab. However, you cannot re-run the compliance report during the update compliance operation and report can only be generated once the update compliance operation is completed. | Not applicable |