Compatibility Matrix
Important notes
This section provides important information that you must consider when you are working on OpenManage Integration for VMware
vCenter.
• OMIVV supports BIOS mode to deploy hypervisor on the target server. Ensure that you have BIOS mode selected in the reference
hardware prole before applying the hypervisor prole. If there is no hardware prole selected, ensure that you manually congure the
Boot mode as BIOS and reboot the server before applying the hypervisor prole.
• OMIVV currently supports only the community named "Public" or "public". The SNMP community name is not congurable. If another
community name is used, the events are not received by OMIVV and the events are not displayed in the VMware vCenter.
• A hardware prole created using a reference server with a certain BIOS version can cause deployment to fail. Some BIOS versions do
not provide accurate information for certain BIOS settings, such as the Embedded NIC1 and NIC2 settings. When a server with the
minimum BIOS version is used as a reference server in a hardware prole, the elds are ignored by both the UI and deployment. An
issue may occur, however, if the settings in question are required to have a certain value for deployment to complete successfully. The
solution to this issue is to use a server with up-to-date BIOS as a reference server for a hardware prole.
NOTE: Servers being used for deployment should also have updated BIOS. If deployment tries to apply settings to a
server with issues in BIOS, deployment fails. Currently the BIOS version is not checked for compliance, but it is displayed
on the server compliance page. Warnings are displayed on the hardware prole reference server and BIOS settings pages
and when you select a deployment template with an aected hardware prole during deployment.
• OMIVV registered with the VMware vCenter by using Fully Qualied Domain Name (FQDN) is highly recommended. For FQDN-based
registrations, the host name of the vCenter should be properly resolvable by the DNS server.
NOTE
: For more information about the DNS requirements for vSphere, see the following links:
– DNS requirements for vSphere 5.5
– DNS requirements for vSphere 6.0
– DNS requirements for vSphere 6.5 and Platform Services Controller appliance
• For cloud server, iDRAC Enterprise license is required.
• Default SNMP Community string is Public. SNMP community string can be congured from Manage > Settings > Appliance Settings
> OMSA SNMP Trap Community String.
• OMIVV supports only Server Message Block(SMB) version 1.0 and SMB version 2.0 based CIFS shares.
• vSAN rmware update is not supported on 11th generation PowerEdge servers.
3
16 Important notes