Filter
Top Products
Post only Virtualization-Related Critical and Warning
Events
Post Virtualization related events received from hosts into
related vCenters. Virtualization related events are those
that Dell has selected to be most critical to hosts running
virtual machines.
When you configure your events and alarms, you can enable them. When enabled, critical hardware alarms can trigger
the OpenManage Integration for VMware vCenter to put the host system into a maintenance mode, and in certain cases,
migrate the virtual machines to another host system. The OpenManage Integration for VMware vCenter forwards events
received from managed Dell hosts, and creates alarms for those events. Use these alarms to trigger actions from
vCenter, like a reboot, maintenance mode, or migrate. For example, when a dual power supply fails and an alarm is
created, the resulting action is to migrate the virtual machine on that machine to a new one.
A host enters or leaves maintenance mode only as when you request it. If the host is in a cluster when it enters
maintenance mode, you are given the option to evacuate powered-off virtual machines. If this option is selected, each
powered-off virtual machine is migrated to another host, unless there is no compatible host available for the virtual
machine in the cluster. While in maintenance mode, the host does not allow deployment or
power-on
of a virtual
machine. Virtual machines that are running on a host entering maintenance mode need to be either migrated to another
host or shut down, either manually or automatically by VMware Distributed Resource Scheduling (DRS).
Any hosts outside of clusters, or in clusters without VMware Distributed Resource Scheduling (DRS) enabled, could see
virtual machines being shut down due to a critical event. DRS continuously monitors usage across a resource pool and
intelligently allocates available resources among virtual machines according to business needs. Use clusters with DRS
configured in conjunction with Dell Alarms to make sure that virtual machines are automatically migrated on critical
hardware events. Listed in the details of the on screen message are any clusters on this vCenter instance that may be
impacted. Confirm that the clusters are impacted before enabling Events and Alarms.
If you ever need to restore the default alarm settings, you can do so with the Reset Default Alarm button. This button is a
convenience to restore the default alarm configuration without uninstalling and reinstalling the product. If any Dell alarm
configurations have been changed since install, those changes are reverted using this button.
NOTE: To receive Dell events, you must enable the events.
NOTE: The OpenManage Integration for VMware vCenter pre-selects the virtualization-related events that are the
essential to hosts successfully running virtual machines. Dell host alarms are disabled by default. If Dell alarms
are enabled, the clusters should use the VMware Distributed Resource Scheduler to make sure that the virtual
machines that send critical events are automatically migrated.
Understanding OMSA For 11th Generation Dell PowerEdge Hosts
On PowerEdge servers earlier than 12th generation, it is mandatory to install OMSA to work with the OpenManage
Integration for VMware vCenter. OMSA is installed automatically on 11th generation Dell PowerEdge hosts during
deployment, or if you want to install it manually, you may still do so.
NOTE: When deploying the OMSA agent using the OpenManage Integration for VMware vCenter starts the
httpClient service and enables port 8080 on and releases after ESXi 5.0 to download OMSA VIB and install it. Once
the OMSA installation is completed, the service automatically stops and the port is closed.
To configure OMSA on 11th generation Dell PowerEdge servers, choose from the following:
• Deploying an OMSA Agent Onto ESXi System
• Deploying an OMSA Agent Onto ESX System
• Setting Up An OMSA Trap Destination
Deploying the OMSA Agent onto an ESX System
Install the OMSA tar.gz on an ESX system to gather inventory and alert information from the systems.
35