Failover within an Azure subnet using private IP - Linux
InfoScale clusters let you fail over IPs - and thereby, the application configured for HA - within the same subnet in the same VNet.
The following information is required:
-
A private IP (secondary private IP) address to be failed over
-
The device to which the IP should be plumbed
Sample configuration with private IP
The following graphic depicts a sample failover configuration within the same subnet using a private IP:
The sample configuration includes the following elements:
-
A Azure virtual network (VNet) is configured in Region A of the Azure cloud
-
An application is configured for HA using a cluster that comprises two nodes, Node1 and Node2, which are Azure virtual machines
-
Both the cluster nodes exist in the same subnet
-
A private IP is configured, which is failed over from one node to the other as part of the failover or the failback operations
Sample service group configuration with private IP
The following snippet is a service group configuration from a sample configuration file (main.cf):
group AzureAuthGrp (
SystemList = { azureVM1 = 0, azureVM2 = 1 }
Parallel = 1
)
AzureAuth azurauth (
SubscriptionId = 6940a326-abg6-40dd-b628-c1e9bbdf1d63
ClientId = 8c891a8c-xyz2-473b-bigc-035bd50fb896
SecretKey = gsiOssRooSnoJuiOhmOumShuNoiQioNsjQlqHovUosQsrMt
TenantId = 96dcasae-0448-4308-b503-6667d61dd0e3
)
Phantom phres (
)
group AzurePrivateIP (
SystemList = { azureVM1 = 0, azureVM2 = 1 }
AutoStartList = { azureVM1, azureVM2 }
)
AzureIP azureipres (
PrivateIP = "10.3.3.100"
NICDevice = eth0
VMResourceGroup = ShilRG
AzureAuthResName = azurauth
)
IP ipres (
Device = eth0
Address = "10.3.3.100"
NetMask = "255.255.255.0"
)
NIC nicres (
Device = eth0
)
ipres requires azureipres
ipres requires nicres
Related information