Owner's Manual

72 Workflow

• Due to the

hostname

dependency the SCOM objects in the workflow may

not work after importing. You may need to reselect the connection for all

the SCOM Objects based on your configuration.

• Ensure that the Opalis server has a DNS server and hostname comes from

the SCOM alerts are resolvable.

Workflow – Proactive Failover

When a critical failure occurs on a physical server, the Proactive Failover

workflow retargets the server's workload.

Proactive Failover

Figure 4-1 depicts

the proactive failover workflow.

Proactive Failover

Figure 4-1. Proactive Failover

When the critical alert is received from the physical machine:

Using the WMI query, the service tag (if it is a Dell system) or serial

number of the server is retrieved.

NOTE: This serial number/service tag acts as the unique identifier to get the

server details from Dell AIM controller.

The

IsVMRack

object determines if the physical server hosts

VMRack

Physical Persona

NOTE: In AIM environment a server is hosting a physical persona or hosting a

VMRack (example HyperV). This workflow takes different actions based on

the image hosted on the physical server.

The workflow takes different actions based on the

IsVMRack

's outcome.

IsVMRack

object determines the physical server has a

Physical Persona:

AIMOpalis_bk0.book Page 72 Monday, October 24, 2011 10:16 AM