Slide List
0: High Availability
1: Introduction
2: Scope
3: Concepts
4: SPOFs
5: Resource Groups
6: Resource Group Failover
7: Disk Access
8: Hot-standby configuration
9: Mutual takeover
10: Third party takeover
11: Third party takeover
12: Dual Networks
13: Network Adapter Labels
14: Synchronization
15: Cluster Topology
16: Configured Clusters
17: NFS
18: Cascading
19: Cascading
20: Cascading
21: Rotating
22: Concurrent
23: Concurrent
24: Concurrent
25: HACMP Policies
26: HACMP Guidelines
27: HACMP Standards
28: HACMP Procedures
|
HACMP - Third party takeover
The goal of IP Address Takeover is to make the server's service
address highly available and to give the clients the possibility of
always connecting to the same IP address.
Design the network topology.
Define a network mask.
Define IP addresses (adapter identifiers) for each node's service and standby adapters.
Define a boot address for each service adapter that can be taken over, if you are using IP address takeover or rotating resources.
Define an alternate hardware address for each service adapter that can have its IP address taken over, if you are using hardware address swapping.
For assistance with designing, implementing, supporting, and
automating your High Availability (HACMP)
environments, please contact Mt
Xia.
Slide ID:MXHA-11
|
|
|
