Before enabling
Proactive HA on clusters, ensure that the following conditions are
met:
A cluster with DRS enabled is created and configured in the vCenter console. To enable DRS on a cluster, see the VMware documentation.
All hosts that are part of the cluster should be part of a connection profile and successfully inventoried.
Steps
In OpenManage Integration, click Clusters.
Under Clusters, click
a cluster, select Configure > vSphere Availability, and then
click Edit.
The Edit Cluster Settings wizard is displayed.
Click vSphere DRS and
select Turn on vSphere DRS, if not selected.
Click vSphere Availability and select Turn on Proactive HA , if not selected.
In the left pane, under vSphere
Availability, click Proactive HA Failures and Responses.
The Proactive HA Failures
and Responses screen is displayed.
In the Proactive HA Failure
and Responses screen, expand the Automation Level.
For the Automation Level, select Manual or Automated.
For the Remediation, select quarantine mode, maintenance mode, or a combination of both quarantine and maintenance mode based on severity status. See the VMware documentation for more information.
For the Proactive HA provider, use
the check box to select the Dell provider for the cluster.
Click edit against
the selected Dell provider.
The Edit Blocked Failure Conditions dialog box for the Proactive HA provider is displayed.
To block a failure condition from posting events,
use the check boxes to select events (generated through traps or polling)
from the failure conditions table.
You can filter the content of the failure conditions
data grid by using the Filter field, or drag
and drop columns within the failure conditions data grid. The failure
conditions can be applied at a cluster level or host level.
To apply on all current and future hosts in
the cluster, select the Cluster-level check
box.
To apply on a host, use the check boxes to
select a host from the To be applied at table
for the partial failure provider.
You can filter the content of the data grid by
using the Filter field.
To apply the changes, in the Edit
Blocked Failure Conditions, click OK, or to cancel, click Cancel.
To save the changes, click OK, or to cancel, click Cancel.
Next steps
OMIVV can now forward the health update notification of components to the vCenter server through events from the Dell server. Based on the notification, the vCenter server takes a manual or automatic action that you have selected for Remediation.
Health polling for the Dell servers
Prerequisites
Before OMIVV
polls every one hour, ensure that the following conditions are met:
A connection profile is assigned to the host.
A successful completed inventory is available for
the host system.
About this task
The following are the health polling events:
Table 1. Polling eventsThe following table lists the polling events:
Event name
Severity
Recommended action
Polling: Fan redundancy is in normal state
Info
No action
Polling: Fan redundancy is in warning state
Warning
Replace fan
Polling: Fan redundancy is in critical state
Critical
Replace fan
Polling: Power redundancy is in normal state
Info
No action
Polling: Power redundancy is in warning state
Warning
Replace power supply unit
Polling: Power redundancy is in critical state
Critical
Replace power supply unit
Polling runs every hour, and you cannot configure the polling schedule. Polling is available as a fail-safe mechanism to cover the possibility of a trap loss.
NOTE: Polling
does not provide redundancy information of the IDSDM component to the
vCenter server.
Aiheeseen liittyviä tietoja ei ole saatavilla.
Anna arvioinnit (1–5 tähteä).
Anna arvioinnit (1–5 tähteä).
Anna arvioinnit (1–5 tähteä).
Valitse, oliko artikkelista mielestäsi hyötyä vai ei.
Kommenteissa ei voi olla seuraavia erikoismerkkejä: <>()\
