
Configuring HyperFabric
Configuring HyperFabric with ServiceGuard
Figure 4-5 When All HyperFabric Adapters Fail
node A
| HyperFabric |
| |
| Resource |
| |
| Failed |
| |
|
|
|
|
|
| HF |
|
Packages |
| adapter 1 |
|
failover to |
|
|
|
|
|
| |
Node B |
|
|
|
|
|
|
|
|
| HF |
|
|
| adapter 0 |
|
|
|
|
|
|
|
|
|
HF switch 0
Ethernet Port
node B |
|
HyperFabric |
|
Resource |
|
Active |
|
| Package |
HF | A |
adapter 0 |
|
HF | Package |
B | |
adapter 1 |
|
HF switch 1
Ethernet Port
Ethernet Heartbeat LAN 0
Ethernet Heartbeat LAN 1
Configuring HyperFabric with the ServiceGuard Resource Monitor
You can configure the HyperFabric Resource Monitor with ServiceGuard in either of these ways:
•Editing an ASCII file.
•Using the SMH GUI.
For more details, please see the manual Using EMS HA Monitors.
NOTE | You should configure HyperFabric with ServiceGuard before running the clic_start |
| command or using SMH to start HyperFabric. |
|
|
Configuring ServiceGuard with HyperFabric Using the ASCII File
When using the ServiceGuard commands (for example, cmapplyconf) to specify the use of the HyperFabric Resource Monitor, the section of the package ASCII configuration file that has the keyword RESOURCE_NAME must be uncommented and set to the following values:
RESOURCE_NAME /net/interfaces/clic/status
RESOURCE_POLLING_INTERVAL 10
80 | Chapter 4 |