Before you migrate VVR from IPv4 to IPv6, review your current configuration. The sample configuration is as follows:
There are two nodes each on the Primary and the Secondary site of replication.
RVG objects are created on both the sites. Replication between the sites uses the IPv4 address.
A failover service of the Virtual IPv4 address is created for high availability.
The failover service group consists of one IP resource and one NIC resource for the virtual IPv4 address.
On every system, the state of the resources in the failover service group is similar to the following:
# hares -state | grep -i res #Resource Attribute System Value ipres State swsx25 ONLINE ipres State swsx27 OFFLINE nicres State swsx25 ONLINE nicres State swsx27 ONLINE
On both the systems, the state of the failover service group is similar to the following:
# hastatus -summ | grep -i VVRGRP B VVRGRP swsx25 Y N ONLINE B VVRGRP swsx27 Y N OFFLINE
The contents of the main.cf
file in the failover service group are displayed as follows:
group VVRGRP ( SystemList = { swsx25 = 0, swsx27 = 1 } AutoStartList = { swsx25 } ) IP ipres ( Device = bge0 Address = "10.209.87.186" NetMask = "255.255.252.0" ) NIC nicres ( Enabled = 1 Device = bge0 ) ipres requires nicres // resource dependency tree // // group VVRGRP // { // IP ipres // { // NIC nicres // } // }
After you create the service group VVRGRP, the output of the ifconfig command is as follows:
# ifconfig -a lo0: flags=2001000849<UP,LOOPBACK,RUNNING,MULTICAST,IPv4,VIRTUAL> mtu 8232 index 1 inet 127.0.0.1 netmask ff000000 bge0: flags=1000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4> mtu 1500 index 2 inet 10.209.85.35 netmask fffff800 broadcast 10.209.87.255 ether 0:14:4f:1f:bd:f1 lo0: flags=2002000849<UP,LOOPBACK,RUNNING,MULTICAST,IPv6,VIRTUAL> mtu 8252 index 1 inet6 ::1/128