Users Guide

Resolution: System profile that is taken from an FC640 server in slot 1 of a FX2s chassis can only be applied on another FC640
server residing in the slot 1 of another FX2s chassis.
Drift Detection shows noncompliant for Modular servers that has
PCIe card in the FX chassis
The System profiles searches for exact instance(FQDD) while comparing with the baseline, which works successfully on Rack
servers (identical), but may have few restrictions in Modular servers. For example, in FC640, the System profile (Baseline)
created from one modular server shows drift for other modular servers in the same FX chassis because of FQDD mismatches.
Version Affected: 4.1 and later.
Resolution: While creating System profile, clear the FQDDs that are not common with other servers.
Unable to deploy an OS on PowerEdge serves when the iDRAC does
not populate the MAC address of the selected NIC
The OS deployment fails on PowerEdge Servers when the iDRAC does not populate the MAC address for the selected NIC port.
Resolution: Update the respective NIC firmware and iDRAC firmware to the latest version and ensure that the MAC address is
populated on the NIC port.
Version Affected: 4.3 and later
When creating a host credential profile for the host having ESXi
6.5U1, the Service Tag of the host is not displayed on the Select
Hosts page
When the OMIVV queries vCenter for the Service Tag of ESXi, vCenter cannot return the Service Tag because the Service Tag
value is null.
Resolution: Update the ESXi version to ESXi 6.5U2 or ESXi 6.7 U1.
Version Affected: 4.3 and later
Dell EMC icon is not displayed after backup and restore from an
earlier OMIVV version to a later OMIVV version
After backup and restore from an earlier OMIVV version to a later OMIVV version, the following issues are observed:
● The Dell EMC logo is not displayed at vCenter.
● The 2000000 error
● The 3001 error
Resolution:
○ Restart vSphere Client on the vCenter server.
○ If the issue persists:
￭ For VMware vCenter Server Appliance, go to /etc/vmware/vsphere-ui/vc-packages/vsphere-client-
serenity and for Windows vCenter, go to C:\ProgramData\VMware\vCenterServer\cfg\vsphere-ui
\vc-packages\vsphere-client-serenity folder in the vCenter appliance and see if the old data exists, such
as: com.dell.plugin.OpenManage_Integration_for_VMware_vCenter_WebClient-X.0.0.XXX.
￭ Manually delete the folder corresponding to the earlier OMIVV version.
Frequently Asked Questions-FAQ
157