Users Guide

OS deployment fails when NPAR is enabled on a target node and
disabled in System Profile
OS deployment fails when a System Profile with a disabled NIC Partitioning (NPAR) is applied on a target machine. Here, NPAR
is enabled on the target node and only one of the partitioned NIC, except partition 1 is selected as the NIC for the Management
Tasks during the deployment process through the deployment wizard.
Resolution: If you are changing the NPAR status using System Profile during deployment, ensure that you select only the first
partition for management network in the deployment wizard.
Version Affected: 4.1 and later
Available OMIVV appliance version displays wrong information
when the available version is lesser than the current version
In the OMIVV Admin console, under Appliance Management, Available Virtual Appliance Version displays the modes RPM
and OVF as available.
NOTE: It is recommended that update repository path is set to the latest version and downgrading the virtual appliance
version is not supported.
The 267027 exception is thrown while adding a 12G and later bare-
metal server
During bare-metal discovery, if an incorrect credential is entered, the user account is automatically locked for few minutes.
During this period, iDRAC becomes unresponsive and takes a few minutes before restoring normalcy.
Resolution: Wait for few minutes and retype the user credentials.
During deployment, system profile apply fails due to iDRAC error
During deployment, OMIVV attempts to create configuration update job in iDRAC. However, the job creation may fail sometimes
and displays a message indicating that a Configuration job is already created.
Resolution: Clear the stale entries and retry the deployment. Log in to iDRAC to clear the jobs.
OMIVV RPM upgrade fails when proxy is configured with domain
user authentication
If OMIVV appliance is configured with proxy to reach the Internet and proxy is authenticated using NTLM authentication, then
the RPM update fails due to the issues in the underlying yum tool.
Version Affected: OMIVV 4.0 and above
Resolution / Work around: Do Back up and Restore to update the OMIVV appliance.
Unable to apply System Profile that has PCIe card in the FX chassis
The OS deployment fails on a target server if the source server has PCIe card information when using an FX chassis. The
System profiles on the source server have different fc.chassislot ID than the one on the target server. OMIVV tries to
deploy the same fc.chassislot ID on the target server but fails. The System profiles searches for exact instance( FQDD)
while applying the profile, which works successfully on rack servers (identical), but may have few restrictions in modular
servers. For example, in FC640, the System profiles that are created from one modular server cannot be applied on other
modular servers in the same FX chassis because of NIC level restrictions.
Version Affected: 4.1 and later.
156
Frequently Asked Questions-FAQ