HP manual When All HyperFabric Adapters Fail, Node a Node B

Configuring HyperFabric

Configuring HyperFabric with ServiceGuard

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
	node A
						node B
		HyperFabric			HyperFabric
		Resource			Resource
		Failed			Active
							Package
			HF	HF			A
	Packages		adapter 1	adapter 0
	failover to
	Node B
							Package
			HF	HF
							B
			adapter 0	adapter 1

		HF	HF
		switch 0	switch 1
	Ethernet Port			Ethernet Port
S					S
		Ethernet Heartbeat LAN 0
S		Ethernet Heartbeat LAN 1			S

Chapter 4 93