Migrating VVR RLINKs from IPv4 to IPv6 when VCS global clustering and VVR agents are configured in the presence of a bunker


Migrating VVR RLINKs from IPv4 to IPv6 when VCS global clustering and VVR agents are configured in the presence of a bunker
Prev	Migrating to IPv6 when VCS global clustering and VVR agents are configured in the presence of a bunker	Next

Before you perform the steps in this section, make sure all sites are in dual mode; that it, all sites have both IPv4 and IPv6 addresses defined.

To migrate VVR RLINKs from IPv4 to IPv6, do the following:

Migrate the VVR RLINKs of the Primary and Secondary sites to IPv6.
Migrate the VVR RLINKs of the Primary and bunker sites to IPv6.
Manually edit the VVR RLINKs at the bunker and Secondary sites. You must edit the RLINKs manually because they are inactive and the vradmin changeip command cannot change the IP for these rlinks

To migrate the RLINKs of the Primary and Secondary sites to IPv6

On the Primary site node, run the vradmin changeip command.

# vradmin -g hrdg changeip hr_rvg 10.209.87.171 \
  newpri=fd4b:454e:205a:111:211:43ff:feaa:af70 \
  newsec=fd4b:454e:205a:111:211:43ff:feaa:af71 
Message from Primary:
VxVM VVR vxrlink INFO V-5-1-3614 Secondary data volumes detected with rvg hr_rvg as parent:
VxVM VVR vxrlink INFO V-5-1-6183 datavol:      len=10485760          primary_datavol=datavol

Check the replication status. Enter the following:

# vradmin -g hrdg repstatus hr_rvg
Replicated Data Set: hr_rvg
Primary:
  Host name:                  10.209.87.170
  RVG name:                   hr_rvg
  DG name:                    hrdg
  RVG state:                  enabled for I/O
  Data volumes:               1
  VSets:                      0
  SRL name:                   hr_srl
  SRL size:                   1.00 G
  Total secondaries:          2

Bunker (secondary):
  Host name:                  10.209.87.202
  RVG name:                   hr_rvg
  DG name:                    hrdg
  Data status:                consistent, behind
  Replication status:         replicating (connected)
  Current mode:               synchronous
  Logging to:                 SRL (48 Kbytes behind, 0% full)
  Timestamp Information:      behind by 0h 0m 0s

Secondary:
  Host name:                  fd4b:454e:205a:111:211:43ff:feaa:af71
  RVG name:                   hr_rvg
  DG name:                    hrdg
  Data status:                consistent, behind
  Replication status:         replicating (connected)
  Current mode:               asynchronous
  Logging to:                 SRL (341972 Kbytes behind, 32% full)
  Timestamp Information:      behind by 0h 1m 10s

To migrate the RLINKs of the Primary and bunker sites to IPv6

On the Primary site node, run the vradmin changeip command.

# vradmin -g hrdg changeip hr_rvg 10.209.87.202 \
  newpri=fd4b:454e:205a:111:211:43ff:feaa:af70 \ 
  newsec=fd4b:454e:205a:111:210:20ff:fe98:af72
Message from Primary:
VxVM VVR vxrlink INFO V-5-1-12348 Secondary srl detected with rvg hr_rvg as parent:

Check the replication status. Enter the following:

# vradmin -g hrdg repstatus hr_rvg

Replicated Data Set: hr_rvg
Primary:
  Host name:                  fd4b:454e:205a:111:211:43ff:feaa:af70
  RVG name:                   hr_rvg
  DG name:                    hrdg
  RVG state:                  enabled for I/O
  Data volumes:               1
  VSets:                      0
  SRL name:                   hr_srl
  SRL size:                   1.00 G
  Total secondaries:          2

Bunker (secondary):
  Host name:                  fd4b:454e:205a:111:210:20ff:fe98:af72
  RVG name:                   hr_rvg
  DG name:                    hrdg
  Data status:                consistent, up-to-date
  Replication status:         replicating (connected)
  Current mode:               synchronous
  Logging to:                 SRL
  Timestamp Information:      behind by 0h 0m 0s

Secondary:
  Host name:                  fd4b:454e:205a:111:211:43ff:feaa:af71
  RVG name:                   hr_rvg
  DG name:                    hrdg
  Data status:                consistent, behind
  Replication status:         replicating (connected)
  Current mode:               asynchronous
  Logging to:                 SRL (752444 Kbytes behind, 71% full)
  Timestamp Information:      behind by 0h 5m 4s

After you migrate to IPv6, check the RLINKs on the Primary site. Enter the following:

# vxprint -Pl
Disk group: hrdg

Rlink:    rlk_10.209.87.202_hr_rvg
info:     timeout=500 rid=0.1077
          latency_high_mark=10000 latency_low_mark=9950
          bandwidth_limit=none
state:    state=ACTIVE
          synchronous=override latencyprot=off srlprot=off
assoc:    rvg=hr_rvg
          remote_host=fd4b:454e:205a:111:211:43ff:feaa:af72 
          IP_addr=fd4b:454e:205a:111:210:20ff:fe98:af72 port=4145
          remote_dg=hrdg
          remote_dg_dgid=1276521227.64.swsx29
          remote_rvg_version=30
          remote_rlink=rlk_10.209.87.203_hr_rvg
          remote_rlink_rid=0.1048
          local_host=fd4b:454e:205a:111:210:20ff:fe98:af70 
          IP_addr=fd4b:454e:205a:111:210:20ff:fe98:af70 port=4145
protocol: TCP/IP
flags:    write enabled attached consistent connected bunker synchronous

Rlink:    rlk_10.209.87.204_hr_rvg
info:     timeout=500 rid=0.1073
          latency_high_mark=10000 latency_low_mark=9950
          bandwidth_limit=10240kbps
state:    state=ACTIVE
          synchronous=off latencyprot=off srlprot=autodcm
assoc:    rvg=hr_rvg
          remote_host=fd4b:454e:205a:111:211:43ff:feaa:af71 
          IP_addr=fd4b:454e:205a:111:210:20ff:fe98:af71 port=4145
          remote_dg=hrdg
          remote_dg_dgid=1276621272.66.swsx27
          remote_rvg_version=30
          remote_rlink=rlk_10.209.87.203_hr_rvg
          remote_rlink_rid=0.1068
          local_host=fd4b:454e:205a:111:211:43ff:feaa:af70 
          IP_addr=fd4b:454e:205a:111:210:20ff:fe98:203 port=4145
protocol: TCP/IP
flags:    write enabled attached consistent connected asynchronous

To change the RLINKs on the bunker and Secondary sites to use IPv6 addresses

Check the RLINKs on the bunker site. Enter the following:

# vxprint -Pl
Disk group: hrdg

Rlink:    rlk_10.209.87.203_hr_rvg
info:     timeout=500 rid=0.1048
          latency_high_mark=10000 latency_low_mark=9950
          bandwidth_limit=none
state:    state=ACTIVE
          synchronous=override latencyprot=off srlprot=off
assoc:    rvg=hr_rvg
          remote_host=fd4b:454e:205a:111:211:43ff:feaa:af70 
          IP_addr=fd4b:454e:205a:111:211:43ff:feaa:af70 port=4145
          remote_dg=hrdg
          remote_dg_dgid=1276518249.76.swsx25
          remote_rvg_version=30
          remote_rlink=rlk_10.209.87.202_hr_rvg
          remote_rlink_rid=0.1077
          local_host=fd4b:454e:205a:111:210:20ff:fe98:af72 
          IP_addr=fd4b:454e:205a:111:210:20ff:fe98:af72 port=4145
protocol: TCP/IP
flags:    write enabled attached consistent connected bunker

Rlink:    rlk_10.209.87.204_hr_rvg
info:     timeout=500 rid=0.1052
          latency_high_mark=10000 latency_low_mark=9950
          bandwidth_limit=none
state:    state=STALE
          synchronous=override latencyprot=off srlprot=off
assoc:    rvg=hr_rvg
          remote_host=10.209.87.171 IP_addr=10.209.87.171 port=4145
          remote_dg=hrdg
          remote_dg_dgid=1276621272.66.swsx27
          remote_rvg_version=30
          remote_rlink=rlk_10.209.87.202_hr_rvg
          remote_rlink_rid=0.1075
          local_host=10.209.87.202 IP_addr=10.209.87.202 port=4145
protocol: TCP/IP
flags:    write enabled detached consistent disconnected bunker

Check the RLINKs on the Secondary site. Enter the following:

# vxprint -Pl
Disk group: hrdg

Rlink:    rlk_10.209.87.202_hr_rvg
info:     timeout=500 rid=0.1075
          latency_high_mark=10000 latency_low_mark=9950
          bandwidth_limit=none
state:    state=STALE
          synchronous=off latencyprot=off srlprot=autodcm
assoc:    rvg=hr_rvg
          remote_host=10.209.87.202 IP_addr=10.209.87.202 port=4145
          remote_dg=hrdg
          remote_dg_dgid=1276521227.64.swsx29
          remote_rvg_version=30
          remote_rlink=rlk_10.209.87.204_hr_rvg
          remote_rlink_rid=0.1052
          local_host=10.209.87.204 IP_addr=10.209.87.204 port=
protocol: TCP/IP
flags:    write enabled detached consistent disconnected bunker_target

Rlink:    rlk_10.209.87.203_hr_rvg
info:     timeout=500 rid=0.1068
          latency_high_mark=10000 latency_low_mark=9950
          bandwidth_limit=10240kbps
state:    state=ACTIVE
          synchronous=off latencyprot=off srlprot=autodcm
assoc:    rvg=hr_rvg
          remote_host=fd4b:454e:205a:111:210:20ff:fe98:af70 
          IP_addr=fd4b:454e:205a:111:210:20ff:fe98:af70 port=4145
          remote_dg=hrdg
          remote_dg_dgid=1276518249.76.swsx25
          remote_rvg_version=30
          remote_rlink=rlk_10.209.87.204_hr_rvg
          remote_rlink_rid=0.1073
          local_host=fd4b:454e:205a:111:210:20ff:fe98:af71 
          IP_addr=fd4b:454e:205a:111:210:20ff:fe98:af71 port=4145
protocol: TCP/IP
flags:    write enabled attached consistent connected

On the bunker and Secondary sites, set the IPv6 addresses manually.

On the bunker site, enter the following:

# vxedit -g hrdg \
  set local_host=fd4b:454e:205a:111:210:20ff:fe98:af72 \
  remote_host=fd4b:454e:205a:111:210:20ff:fe98:af71 \
  rlk_10.209.87.204_hr_rvg

On the Secondary site, enter the following:

# vxedit -g hrdg \
  set local_host=fd4b:454e:205a:111:210:20ff:fe98:af71 \
  remote_host=fd4b:454e:205a:111:210:20ff:fe98:af72 \
  rlk_10.209.87.202_hr_rvg

Check the RLINKs on the bunker site to verify your changes:

# vxprint -Pl
Disk group: hrdg

Rlink:    rlk_10.209.87.203_hr_rvg
info:     timeout=500 rid=0.1048
          latency_high_mark=10000 latency_low_mark=9950
          bandwidth_limit=none
state:    state=ACTIVE
          synchronous=override latencyprot=off srlprot=off
assoc:    rvg=hr_rvg
          remote_host=fd4b:454e:205a:111:210:20ff:fe98:af70 
          IP_addr=fd4b:454e:205a:111:210:20ff:fe98:af70 port=4145
          remote_dg=hrdg
          remote_dg_dgid=1276518249.76.swsx25
          remote_rvg_version=30
          remote_rlink=rlk_10.209.87.202_hr_rvg
          remote_rlink_rid=0.1077
          local_host=fd4b:454e:205a:111:210:20ff:fe98:af72 
          IP_addr=fd4b:454e:205a:111:210:20ff:fe98:af72 port=4145
protocol: TCP/IP
flags:    write enabled attached consistent connected bunker

Rlink:    rlk_10.209.87.204_hr_rvg
info:     timeout=500 rid=0.1052
          latency_high_mark=10000 latency_low_mark=9950
          bandwidth_limit=none
state:    state=STALE
          synchronous=override latencyprot=off srlprot=off
assoc:    rvg=hr_rvg
          remote_host=fd4b:454e:205a:111:210:20ff:fe98:af71 
          IP_addr=fd4b:454e:205a:111:210:20ff:fe98:af71 port=
          remote_dg=hrdg
          remote_dg_dgid=1276621272.66.swsx27
          remote_rvg_version=30
          remote_rlink=rlk_10.209.87.202_hr_rvg
          remote_rlink_rid=0.0
          local_host=fd4b:454e:205a:111:210:20ff:fe98:af72 
          IP_addr=fd4b:454e:205a:111:210:20ff:fe98:af72 port=4145
protocol: TCP/IP
flags:    write enabled detached consistent disconnected bunker

Check the RLINKs on the Secondary site. Enter the following:

# vxprint -Pl
Disk group: hrdg

Rlink:    rlk_10.209.87.202_hr_rvg
info:     timeout=500 rid=0.1075
          latency_high_mark=10000 latency_low_mark=9950
          bandwidth_limit=none
state:    state=STALE
          synchronous=off latencyprot=off srlprot=autodcm
assoc:    rvg=hr_rvg
          remote_host=fd4b:454e:205a:111:210:20ff:fe98:af72 
          IP_addr=fd4b:454e:205a:111:210:20ff:fe98:af72 port=
          remote_dg=hrdg
          remote_dg_dgid=1276521227.64.swsx29
          remote_rvg_version=30
          remote_rlink=rlk_10.209.87.204_hr_rvg
          remote_rlink_rid=0.0
          local_host=fd4b:454e:205a:111:210:20ff:fe98:af71 
          IP_addr=fd4b:454e:205a:111:210:20ff:fe98:af71 port=4145
protocol: TCP/IP
flags:    write enabled detached consistent disconnected bunker_target

Rlink:    rlk_10.209.87.203_hr_rvg
info:     timeout=500 rid=0.1068
          latency_high_mark=10000 latency_low_mark=9950
          bandwidth_limit=10240kbps
state:    state=ACTIVE
          synchronous=off latencyprot=off srlprot=autodcm
assoc:    rvg=hr_rvg
          remote_host=fd4b:454e:205a:111:210:20ff:fe98:af70
          IP_addr=fd4b:454e:205a:111:210:20ff:fe98:af70 port=4145
          remote_dg=hrdg
          remote_dg_dgid=1276518249.76.swsx25
          remote_rvg_version=30
          remote_rlink=rlk_10.209.87.204_hr_rvg
          remote_rlink_rid=0.1073
          local_host=fd4b:454e:205a:111:210:20ff:fe98:af71 
          IP_addr=fd4b:454e:205a:111:210:20ff:fe98:af71 port=4145
protocol: TCP/IP
flags:    write enabled attached consistent connected

The replication IPs have been changed to IPv6 on all the Sites. Now the Sites can be moved to pure IPv6 by removing the IPv4 network.

Prev	Up	Next
Adding the IP and NIC resources for IPv6 addresses in the RVG agent group when VCS global clustering and VVR agents are configured in the presence of a bunker	Home	Removing the IPv4 resources from the VCS configuration when VCS global clustering and VVR agents are configured in the presence of a bunker