Users Guide

4. Click APPLY.
Configure deployment credentials
OMIVV acts as a provisioning server. The deployment credentials enable you to communicate with iDRAC that uses the OMIVV plugin as a
provisioning server in the auto discovery process. The deployment credentials enable you to set up iDRAC credentials to communicate
securely with a bare-metal server that is discovered using auto discovery until the operating system deployment is complete.
After the operating system deployment process is successfully complete, OMIVV changes the iDRAC credentials as provided in the host
credential profile. If you change the deployment credentials, all newly discovered systems using auto discovery are provisioned with the
new iDRAC credentials from that point onwards. However, the credentials on servers that are discovered before the change of
deployment credentials are not affected by this change.
1. On the OMIVV home page, click Settings > Appliance Settings > Deployment Credentials.
2. Enter the username and password. The default username is root and password is calvin.
Ensure that you provide only the iDRAC supported characters and iDRAC local credentials.
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 change
to the vCenter server. The available states of redundancy health status for the supported components (power supply, fans, and IDSDM)
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.
NOTE:
An Unknown health status 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.
• Proactive HA is available only on the platforms that support redundancy on power, fan, and IDSDM.
• Proactive HA feature is not supported for PSUs for which redundancy cannot be configured (for example, cabled
PSUs).
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:
Manage OMIVV appliance settings
73