Release Notes
Table Of Contents
- OpenManage Integration for VMware vCenter Version 4.3.1 Release Notes
- Release Type and Definition
- Importance
- Platforms Affected
- What is supported
- What’s New
- Important Notes
- Fixes
- Known Issues and Resolutions
- Limitations
- Installation Prerequisites
- Installation Procedure
- Installation and Configuration Notes
- Accessing documents from the Dell EMC support site
- Contacting Dell
Version Affected: 4.3
● Issue 42: Configuring the System Lockdown mode at a cluster level sometimes displays a message "No hosts under the
cluster has successful inventory".
Description: Configuring the System Lockdown mode at a cluster level sometimes displays a message "No hosts under the
cluster has successful inventory". This message is displayed even when the cluster has successfully inventoried the 14G
hosts that are managed by OMIVV.
Resolution: Reboot the vCenter.
To reboot the vCenter, do the following:
1. Log in to the vSphere Web Client with a vCenter Single Sign-on Administrator account.
2. Go to Administration > Deployment > Deployment > System Configuration.
3. Click Nodes, select the vCenter Server Appliance node and click the Related Objects tab.
4. Reboot the vCenter node.
Version Affected: 4.3
● Issue 43: Sometimes post RPM upgrade of OMIVV appliance, multiple entries in the logs are seen in vCenter Recent Tasks.
Description: Sometimes, after RPM upgrade, multiple entries are displayed in logs when viewed on vCenter Recent Tasks.
Resolution: Restart the vCenter services.
Version Affected: 4.3
●
Issue 44: Sometimes, the storage inventory data is not displayed for the host managed using chassis profile and present in
member chassis.
Description: For an MX chassis in an MCM configuration, the storage data may not be displayed for an MX host managed
using the chassis profile and for a host present in the member chassis. Though the inventory data of other components is
displayed, only the storage related data is not displayed
Resolution: Do one of the following:
1. Update the MX7000 chassis firmware version to 1.00.10.
2. Manage the host using iDRAC.
3. Reinstall the host in another slot of the same MX7000 chassis and retry the operation.
● Issue 45: The deployment job times out when OMIVV's network interface card (NIC) is not connected to the ESXi host
network.
Description: OS deployment has dependency on the selection of NIC. If the correct NIC is not selected, then OSD job will
time out.
Resolution: Select appropriate 'Appliance NIC connected to Host ' from Configure Host Settings page of Deployment
wizard . This is needed by OMIVV to reach ESXi network during hypervisor installation process
● Issue 46: Drift detection job name format is displayed incorrectly in VMware Tasks pane.
Resolution: None
Version Affected: 4.3 and later.
● Issue 46: Failed to set the password for iDRAC users and few attributes are missing in the Hardware Profile created in 4.3
for iDRAC 3.30.30.30 and later versions.
Description: While creating a Hardware Profile in 4.3 for iDRAC 3.30.30.30 and later versions, if you save the Hardware
Profile without selecting the iDRAC Settings, and try to use the same profile in 4.3.1 by selecting the iDRAC Settings, you
cannot set the password and few attributes are not captured.
Resolution: It is recommended to create a new Hardware Profile.
Version Affected: 4.3.1
Limitations
The following are the limitations for this release of OMIVV:
● If the Dell Cloud server model C6320 contains H730 controller and micro SD card in the riser, the micro SD card might not
be detected in some situations. This limits the OS deployment on the SD card.
● In the Dell Cloud server model C6320, deployment through LSI 2008 is not supported.
9