Currently, replication between the Primary and Secondary sites uses an IPv4 network. Before you can migrate the network to IPv6, you must add the IP and NIC resources to VCS control. You can do this in one of the following ways:
The first method, adding new IP and NIC resources for IPv6, ensures high availability. For example, suppose you add resources for IP and NIC resources for IPv6 addresses in the
main.cf on the node in the Primary site from where replication is active. If the Primary site crashes before VVR migration to IPv6 from IPv4, the application service group fails over to the other node in the Primary site and replication continues using the IPv4 address. The existing IP and NIC resources are still in the
The second method, modifying the current IP and NIC resources, hampers replication. If a node in the Primary site crashes as you modify the existing IP resource, the original IPv4 virtual IP is lost. The application service group fails over to the other node, but the IPv4 IP address does not come online on the other node because you changed the IP resource from an IPv4 address to an IPv6 address. Instead, the IPv6 IP comes online. However, VVR is not configured use the IPv6 IP for replication, and replication pauses or stops. The IPv4 IP is not available on the other node.
To add the IP and NIC resources on the Primary and Secondary sites
# haconf -makerw
# haconf -makerw # hares -modify logowner_ip Device eth1 # hares -modify logowner_ip \ Address fd4b:454e:205a:111:213:72ff:fe59:4a23 # hares -modify logowner_ip Enabled 1 # hares -modify nic Device eth1 # hares -modify nic Enabled 1 # hares -modify logowner_ip PrefixLen 64 # haconf -dump -makero
Repeat step 2 on the Secondary site, using the appropriate system names and IP addresses.
# haconf -dump -makero