Users Guide
Table Of Contents
- OpenManage Integration for VMware vCenter Version 5.3 User's Guide
- Contents
- Introduction
- Log in to Dell EMC OMIVV administration console
- Register new vCenter server
- Register vCenter server using a non-administrative account
- Required privileges for non-administrator users
- Assign Dell privileges to existing role
- Update certificates for registered vCenter servers
- Modify vCenter login credentials
- Unregister OpenManage Integration for VMware vCenter
- Upload license to OMIVV Administration Console
- Manage the OMIVV appliance
- Access the appliance management
- Restart OMIVV appliance
- Upgrade OMIVV appliance and repository location
- OMIVV upgrade options
- Upgrade OMIVV appliance using RPM (using Internet)
- Upgrade OMIVV appliance using RPM (using Intranet)
- Upgrade OMIVV appliance using backup and restore
- Manage backup and restore
- Generate and download the troubleshooting bundle
- Set up HTTP proxy
- Set up Network Time Protocol (NTP) servers
- Configure deployment mode
- Extended monitoring
- Generate a Certificate Signing Request (CSR)
- Upload HTTPS certificate
- Restore default HTTPS certificate
- Set up global alerts
- About OMIVV VM console
- Open OMIVV VM console
- Configure OMIVV appliance
- Configure OMIVV appliance with two Network Interface Controllers (NICs)
- Change OMIVV appliance password
- Configure Network Time Protocol (NTP) and set local time zone
- Change hostname of OMIVV appliance
- Reboot OMIVV appliance
- Reset OMIVV appliance to factory settings
- Read-only user role
- Register new vCenter server
- Monitor hosts and chassis using dashboard
- Manage hosts using host credential profile
- Manage chassis using chassis credential profile
- Manage firmware and driver repositories using repository profile
- Capture baseline configuration using cluster profile
- Manage bare-metal servers
- Manage deployment profiles
- System profile and ISO profile deployment
- Compliance
- Manage OMIVV jobs
- Manage logs
- Manage OMIVV appliance settings
- Manage vCenter settings
- Chassis Management
- View Dell EMC chassis information
- View chassis inventory information
- Viewing hardware inventory information for chassis
- View firmware inventory information
- View management controller information
- View storage inventory information
- View warranty information
- View related host for chassis
- View related chassis information
- Manage PowerEdge MX chassis
- Update MX chassis firmware
- Host Management
- View OMIVV hosts
- Monitor single host
- Firmware update
- vSphere Lifecycle Manager overview
- Using OMIVV as a firmware add-on provider in vSphere Lifecycle Manager—User Interface
- Using OMIVV as a firmware add-on provider in vSphere Lifecycle Manager—vSphere Automation APIs
- Set up blink indicator light
- Configure System Lockdown Mode
- Security roles and permissions
- Frequently Asked Questions-FAQ
- Compliance
- iDRAC license type and description are displayed incorrectly for non-compliant vSphere hosts
- On running fix noncompliant vSphere hosts wizard, the status of a specific host is displayed as Unknown
- A server may show as non-compliant with CSIOR status, "Unknown"
- iDRAC license status is displayed as compliant on the management compliance page when the iDRAC IP is not reachable
- Drift Detection shows noncompliant for Modular servers that has PCIe card in the FX chassis
- Unable to view new iDRAC version details listed on vCenter hosts and clusters page
- Deployment
- Attempting to deploy ESXi on server fails
- OS deployment fails when NPAR is enabled on a target node and disabled in System Profile
- Auto discovered systems are displayed without model information in Deployment wizard
- During deployment, system profile apply fails due to iDRAC error
- Unable to deploy an OS on PowerEdge serves when the iDRAC does not populate the MAC address of the selected NIC
- After OS deployment, OMIVV failed to add ESXi host to vCenter or failed to add Host Profile or Enter Maintenance Mode is failed for host
- ESXi host is either disconnected or not responding state after successful OS deployment using OMIVV.
- Deployment job times out when network interface card (NIC) of OMIVV is not connected to the ESXi host network
- Deployment job fails in OMIVV
- Unable to apply System Profile that has PCIe card in the FX chassis
- NFS share is set up with ESXi ISO, but deployment fails with errors mounting share location
- Bare-metal deployment issues
- Firmware update
- Running firmware update may display an error message, The firmware repository file does not exist or is invalid.
- Why did system not enter maintenance mode when I performed one-to-many firmware update
- What should I do as firmware update failed
- Firmware level not updated when I have performed firmware update with Apply on Next reboot option and system was rebooted
- Chassis Management Controller (CMC) firmware update fails in FX2 chassis
- When upgrading or downgrading some iDRAC firmware versions using OMIVV, even when the firmware update is successful, OMIVV may indicate that the job is failed.
- Using OMIVV to update the Intel network card with firmware version of 13.5.2 is not supported
- Sometimes, inventory fails after firmware update
- Installation
- Upgrade
- The 2000002 error is displayed in all the pages of OMIVV after performing RPM upgrade or backup and restore from an earlier OMIVV version to a later OMIVV version
- Proactive HA initialization is not happening after performing backup and restore
- A server with Unknown status in the earlier version is not listed on the Bare-metal Servers page after backing up and restoring to a latest OMIVV version
- Non-compliant 11G PowerEdge servers are retained in OMIVV inventory after backup and restore
- Sometimes post RPM upgrade of OMIVV appliance, multiple entries in the logs are seen in vCenter Recent Tasks
- Dell EMC icon is not displayed after backup and restore from an earlier OMIVV version to a later OMIVV version
- OMIVV RPM upgrade fails when proxy is configured with domain user authentication
- After backup and restore of OMIVV, alarm settings are not restored
- Entering a Password in the Backup Now Screen Receives an Error Message
- Unable to launch vCenter from flex client after upgrading the OMIVV appliance
- Bare-metal discovery
- Certificate
- Registration
- Sometimes, OMIVV takes long time to complete vCenter un-registration
- After registration of vCenter, the Dell EMC logo of OMIVV is not displayed on the home page of VMware
- What should I do as vCenter registration failed
- I am not seeing OpenManage Integration icon in HTML-5 Client even if registration of plug-in to vCenter was successful
- Dell privileges that are assigned while registering the OMIVV appliance are not removed after unregistering OMIVV
- Proactive HA
- DNS
- Host credential profile
- 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
- Performance during host credential profile test credentials is slow or unresponsive
- Host inventory or test connection fails due to invalid or unknown iDRAC IP.
- When I tried to use lockdown mode, it fails
- Network configuration
- System profile
- vCenter
- Others
- OMIVV instance is not removed from vCenter after resetting OMIVV appliance to factory settings
- Test connection and inventory fails in OMIVV after changing vCenter password
- OMIVV page displays invalid session, or time out exception, or two million errors in Firefox browser
- Warranty job is not running for certain hosts
- Configuring the System Lockdown mode at a cluster level sometimes displays a message "No hosts under the cluster has successful inventory"
- Available OMIVV appliance version displays wrong information when the available version is lesser than the current version
- Host still displayed under chassis even after removing host from vCenter tree
- Does OMIVV support VMware vCenter server appliance
- How do I force remove OMIVV appliance from vCenter
- In Administration Console, Update Repository Path is not set to default path after I reset appliance to factory settings
- Why does Administration Portal display unreachable update repository location
- Chassis global health still healthy when some of power supply status has changed to critical
- Processor version is displayed as “Not Applicable” in processor view in system overview page
- Does OMIVV support vCenter in linked mode
- What are required port settings for OMIVV
- Can OMIVV support ESXi with lockdown mode enabled
- Sometimes, test connection fails when using NFS share
- Compliance
- System specific attributes
- Additional information
- Customization attributes
- Component vs. baseline version comparison matrix
- Response codes
3. Click APPLY.
Hardware component redundancy health—Proactive
HA
Proactive HA is a vCenter feature that works with OMIVV. When you enable Proactive HA, the feature safeguards your
workloads by proactively taking measures based on degradation of redundancy health of supported components in a host.
After assessing the redundancy health status of the supported host components, the OMIVV appliance updates the health
status in the vCenter server. Proactive HA is available only on the platforms that support redundancy on PSU, fan, IDSDM,
and memory. Proactive HA feature is not supported for PSUs for which redundancy cannot be configured (for example, cabled
PSUs).
Memory component is applicable only for iDRAC9-based servers with the Memory Operating Mode BIOS configurations of
Advanced ECC Mode, Mirror Mode, Spare Mode, Spare with Advanced ECC Mode, and Dell Fault Resilient Mode. It is
recommended to have homogeneous cluster and iDRAC9-based hosts in the cluster. OMIVV cannot manage iDRAC8 and earlier
hosts because memory redundancy is not supported.
If memory redundancy is disabled on host, the hosts are moved to memory filter and the memory component is not applicable
for those hosts present in the memory filter. There will not be any action on those hosts present in the memory filter even if the
memory goes bad. However, OMIVV continue to monitor the remaining components.
For the PowerEdge MX chassis hosts, memory component is applicable only if the host is managed through Host Credential
profile in OMIVV.
For memory components, the redundancy health status check happens during initialization, polling, and SNMP events. If the
component redundancy status is disabled on host, the host is moved to memory filter during the next polling cycle or when any
event occurs. The host is moved out of memory filter during the next polling cycle once the component redundancy status is
enabled. After the host is moved out of memory filter or when any event occurs, OMIVV manages the memory components
present in the host. For more information about memory operating modes, see the Mode-specific guidelines topic in the Dell
EMC PowerEdge server Installation and Service Manual.
You can view the events on the Events page in vSphere Client and OMIVV logs page.
The available states of redundancy health status for the supported components (power supply, fans, IDSD, and memory) are:
● Healthy (Information)—component operating normally
● Warning (Moderately degraded)—component has a noncritical error. The moderately degraded states are represented as
Warning in the Type column on the Events page.
● Critical (Severely degraded)—component has a critical failure.
● Unknown—denotes the unavailability of any Proactive HA health update from the Dell Inc provider. An unknown health
status might occur when:
○ All hosts that are added to a Proactive HA cluster may remain in the unknown state for a few minutes until OMIVV
initializes them with their appropriate states.
○ A vCenter server restart may put the hosts in a Proactive HA cluster into an unknown state until OMIVV initializes them
with their appropriate states again.
When OMIVV detects a change in the redundancy health status of supported components (either through Traps or polling),
the health update notification for the component is sent to the vCenter server. Polling runs every hour, and it is available as a
fail-safe mechanism to cover the possibility of a Trap loss.
NOTE:
When configuring events, it is recommended that you select Post all Events option as event posting level. For more
information about configuring events, see Configure events and alarms on page 103.
Proactive HA events
Based on the components supported by VMware for Proactive HA, the following events are registered by the Dell Inc provider
during its registration with vCenter:
Table 5. Dell Proactive HA events
Dell Inc provider event Component type Description
DellFanRedundancy Fan Fan redundancy event
92 Manage OMIVV appliance settings