 | ||
| Failover within the same subnet of an AZ using virtual private IP | ||
|---|---|---|
| Prev | HA and DR configurations using in AWS | Next |
| ||
| Failover within the same subnet of an AZ using virtual private IP | ||
|---|---|---|
| Prev | HA and DR configurations using in AWS | Next |
clusters let you fail over IPs - and thereby, the application configured for HA - within the same subnet of an AZ.
The following information is required:
The virtual private IP (secondary private IP) address to be failed over
The device to which the IP should be plumbed
The directory in which the AWS CLI is installed; this input is not required if it is provided in the PATH environment variable
The following graphic depicts a sample failover configuration within the same subnet using a virtual private IP:
The sample configuration includes the following elements:
A virtual private cloud (VPC) is configured in Region A of the AWS cloud.
An application is configured for HA using an cluster that comprises two nodes, Node1 and Node2, which are EC2 instances.
Both the cluster nodes exist in the same subnet.
A virtual private IP is configured, which is failed over from one node to the other as part of the failover or the failback operations.
The following snippet is a service group configuration from a sample configuration file (main.cf):
group appnetworkSG (
SystemList = { ip-172-34-20-109 = 0, ip-172-34-30-231 = 1 }
AutoStartList = { ip-172-34-20-109, ip-172-34-30-231 }
)
AWSIP AwsIp_Res (
PrivateIP = "10.239.2.242"
Device = eth0
AWSBinDir = "/usr/local/bin"
)
IP Ip_Res (
Device = eth0
Address = "10.239.2.242"
NetMask = "255.255.252.0"
)
NIC Nic_Res (
Device = eth0
)
AwsIp_Res requires Ip_Res
Ip_Res requires Nic_Res