Setup and Install

Configuring HyperFabric
Configuring HyperFabric with MC/ServiceGuard
Chapter 4
103
Example 2:
This example, illustrated by Figure 4-4 below, shows the same node after the failure of
one of the HyperFabric adapters. The remaining adapter in node A is now handling all
HyperFabric network traffic for the node. Because the HyperFabric resource is still
available, MC/ServiceGuard has not been notified; 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
HF
adapter 0
HF
adapter 1
node A
Failed
172.16.10.11
Adapter IP addresses:
Active
172.16.20.21
Adapter
Adapter
Package
A
Package
B
HyperFabric
Resource Active