Modifying the failover service group used for replication to IPv6


Modifying the failover service group used for replication to IPv6
Prev	Migrating from IPv4 to IPv6	Next

On the Primary site, in the existing failover service group created for the IPv4 virtual IP, create an IP resource and/or NIC resource for the virtual IPv6 address. In the following example, the service group is VVRGRP.

To modify the failover service group used for replication to IPv6

Enable write operations on the VCS configuration. Enter the following:
```
# haconf -makerw
```

Add the NIC resource for the IPv6 address and configure the related attributes:

# hares -add  nicres_v6  NIC  VVRGRP
# hares -modify nicres_v6 Device  bge1
# hares -modify nicres_v6 Enabled 1
# hares -modify nicres_v6 Protocol IPv6
# hares -probe nicres_v6 -sys node1
# hares -probe nicres_v6 -sys node2

Add the IP resource for the IPv6 address and configure the necessary attributes.

hares -add  ipres_v6  IP  VVRGRP
# hares -modify ipres_v6 Device  bge1 
# hares -modify ipres_v6 \
  Address fd4b:454e:205a:111:211:43ff:feaa:af71
# hares -modify ipres_v6 Enabled 1
# hares -modify ipres_v6 PrefixLen 64
# hares -probe ipres_v6 -sys node1
# hares -probe ipres_v6 -sys node2
# hares -online ipres_v6 -sys node1

In the example above, the new IP resource ipres_v6 is configured for the virtual IPv6 address.

Note:

If you configure the IPv6 address on the same NIC that is used for IPv4, you do not need to create a new NIC resource. Instead, use the existing NIC resource and link the new IP resource to it. If you configure the IPv6 address on a separate interface, create a new NIC resource (nicres_v6) for the IPv6 interface.

Link the IP resource to the NIC resource, Enter the following:
```
# hares -link ipres_v6 nicres_v6
```
Save your configuration changes. Enter the following:
```
# haconf -dump -makero
```
Repeat step 1 to 5 on the Secondary site.

The virtual IP will be different on each site.

Note:

Do not stop VCS; do not modify the existing service group in the main.cf file. These changes affect replication between the sites because the service group will go offline.

After you save the configuration, the service group (VVRGRP) has the following settings:

The state of resources after configuring the virtual IPv6 address:

# hares -state | grep -i res
Resource     Attribute        System     Value
ipres        State            swsx25     ONLINE
ipres        State            swsx27     OFFLINE
ipres_v6     State            swsx25     ONLINE
ipres_v6     State            swsx27     OFFLINE
nicres       State            swsx25     ONLINE
nicres       State            swsx27     ONLINE
nicres_v6    State            swsx25     ONLINE
nicres_v6    State            swsx27     ONLINE

The state of the failover service group (VVRGRP):

# hastatus -summ | grep -i vvr
B  VVRGRP          swsx25               Y          N      ONLINE
B  VVRGRP          swsx27               Y          N      OFFLINE

The updated contents of main.cf file after adding new resources:

group VVRGRP (
        SystemList = { swsx25 = 0, swsx27 = 1 }
        AutoStartList = { swsx25 }
        )

        IP ipres (
                Device = bge0
                Address = "10.209.87.186"
                NetMask = "255.255.252.0"
                )

        IP ipres_v6 (
                Device = bge1
                Address = "fd4b:454e:205a:111:211:43ff:feaa:af71"
                PrefixLen = 64
                )

        NIC nicres (
                Enabled = 1
                Device = bge0
                )

        NIC nicres_v6 (
                Enabled = 1
                Device = bge1
                )

        ipres requires nicres
        ipres_v6 requires nicres_v6

        // resource dependency tree
        //
        //      group VVRGRP
        //      {
        //      IP ipres
        //          {
        //          NIC nicres
        //          }
        //      IP ipres_v6
        //          {
        //          NIC nicres_v6
        //          }
        //      }

After you modify 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
bge0:0: flags=1000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4> mtu 1500 index 2
        inet 10.209.87.186 netmask fffff800 broadcast 10.255.255.255
        ether 0:14:4f:1f:bd:f1
lo0: flags=2002000849<UP,LOOPBACK,RUNNING,MULTICAST,IPv6,VIRTUAL> mtu 8252 index 1
        inet6 ::1/128
bge1: flags=2000841<UP,RUNNING,MULTICAST,IPv6> mtu 1500 index 2
        inet6 fd4b:454e:205a:111:211:43ff:feaa:af71
        ether 0:14:4f:1f:bd:f1

In this example, the virtual IPv4 address is bge0: 10.209.87.186 and the virtual IPv6 address is bge1: fd4b:454e:205a:111:211:43ff:feaa:af71.

Note:

Replication continues to use the virtual IPv4 address. The virtual IPv6 address is successfully configured without affecting the existing VVR replication.

Because both the virtual IPv4 and IPv6 addresses are online, you can migrate the Primary and Secondary VVR sites from the IPv4 network to the IPv6 network without disrupting the replication between the sites.