Configuring HyperFabric

Configuring HyperFabric with ServiceGuard

How HyperFabric Handles Adapter Failures

HyperFabric adapters are handled differently than other types of networking adapters (such as Ethernet, FDDI, and Fibre Channel) in the ServiceGuard environment. In the non-HyperFabric cases, two network links are in a node, and one will be active and one will be idle or in standby. In the case of an active link failure, ServiceGuard is notified and the network traffic is switched to the standby adapter (which then becomes active).

However, in the case of HyperFabric, if two adapters are in a node, both will be active. If one active HyperFabric adapter fails, its network traffic is switched to the other active HyperFabric adapter in the node.

(Throughput might be slower because only one active adapter is now handling the network traffic.) This rearrangement is handled by the HyperFabric software, and ServiceGuard is not notified. However, note that if all of the HyperFabric adapters fail, HyperFabric does notify ServiceGuard. In both cases, though, the events are logged to /var/adm/clic_log and /var/adm/syslog.log.

90

Chapter 4

Page 104
Image 104
HP manual How HyperFabric Handles Adapter Failures