
Configuring HyperFabric
Configuring HyperFabric with MC/ServiceGuard
Figure 4-2 An MC/ServiceGuard Configuration (with Two HyperFabric Switches)
Ethernet Heartbeat LAN 1
| Ethernet Heartbeat LAN 0 | ||
node A |
|
| node B |
HF |
|
| HF |
adapter 1 |
|
| adapter 0 |
HF |
|
| HF |
adapter 0 |
|
| adapter 1 |
Ethernet Port | HF | HF | Ethernet Port |
switch 0 | switch 1 | ||
node C |
|
| node D |
HF |
|
| HF |
adapter 0 |
|
| adapter 1 |
HF |
|
| HF |
adapter 1 |
| adapter 0 | |
S |
|
| S |
S |
|
| S |
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 MC/ServiceGuard environment. In the
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
100 | Chapter 4 |