User's Guide

Conﬁguring HyperFabric

Conﬁguring HyperFabric with ServiceGuard

Chapter 4

available, ServiceGuard has not been notiﬁed; HyperFabric handles the local

HyperFabric adapter failover. However, the failure of adapter 1 has been logged to

/var/adm/clic_log.

Figure 4-4 Node with One Failed HyperFabric Adapter

After the failover, if you issue a netstat -in command, you will see that an IP address is

still assigned to each adapter. For example:

Name MTU network Address Ipkts Opkts

clic1 31744 172.16.10.0 172.16.10.11 711 12

clic0 31744 172.16.20.0 172.16.20.21 1222 333

Example 3:

This ﬁnal 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 notiﬁes the ServiceGuard cmcld daemon

that the HyperFabric resource on node A is unavailable. Because HyperFabric is

conﬁgured as a package dependency for Packages A and B, ServiceGuard causes the

packages to failover to node B. In a four-node conﬁguration (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.

adapter 0

adapter 1

node A

Failed

172.16.10.11

Adapter IP addresses:

Active

172.16.20.21

Adapter

Package

HyperFabric

Resource Active