Administrator's Guide

Configuring HyperFabric
Configuring HyperFabric with ServiceGuard
Chapter 4 93
Example 3:
This final example, illustrated by Figure 4-5 below, shows a situation in
which all of the HyperFabric adapters on node A fail. The HyperFabric
Resource Monitor reports to the Event Monitoring Service (EMS). The
EMS then notifies the ServiceGuard cmcld daemon that the HyperFabric
resource on node A is unavailable. Because HyperFabric is configured as
a package dependency for Packages A and B, ServiceGuard causes the
packages to failover to node B. In a four-node configuration (note that
only two nodes are shown in Figure 4-5 below), Packages A and B can
continue to communicate through the HyperFabric network with the
other active nodes in the ServiceGuard cluster.
Figure 4-5 When All HyperFabric Adapters Fail
HF
adapter 1
HF
adapter 0
HF
adapter 0
switch 0
HF
switch 1
HF
Ethernet Port
HF
adapter 1
Ethernet Port
S
S
S
S
Ethernet Heartbeat LAN 1
Ethernet Heartbeat LAN 0
node A
node B
Package
B
A
HyperFabric
Resource
HyperFabric
Resource
Failed
Packages
failover to
Node B
Active
Package