InfoScale™ 9.0 Replication Administrator's Guide - AIX
- Section I. Getting started with Volume Replicator
- Introducing Volume Replicator
- Understanding how Volume Replicator works
- How VVR processes application writes
- How VVR uses kernel buffers for replication
- How data flows in VVR asynchronous mode
- About secondary logging enabled asynchronous mode
- About bulk transfer with secondary logging
- How data flows in VVR asynchronous mode with secondary logging
- How data flows in VVR synchronous mode
- How data flows in an RDS containing multiple Secondary hosts
- Replication in a shared disk group environment
- Assigning a slave node as a logowner
- Understanding how VVR logs writes to the SRL
- Understanding Storage Checkpoints
- Volume sets in VVR
- Changing membership of an RVG and a volume set
- Using SmartTier with VVR
- Cross-platform Data Sharing in VVR
- Understanding the VVR snapshot feature
- About VVR compression
- Planning and configuring replication
- Introduction to planning and configuring replication
- Before you begin configuring
- Choosing the mode of volume replication
- Choosing latency and SRL protection
- Planning the network
- Sizing the SRL
- Choosing the type of DCM logging
- Best practices for setting up replication
- How the agents for hybrid applications work
- Pre-requisites to enable data over wire encryption
- Enabling Data Change Object (DCO) for SRL Volumes
- Understanding replication settings for a Secondary
- Configuring VVR in a VCS environment
- Overview of how to configure VVR in a VCS environment
- Using the primary-elect feature to choose the primary site after a site disaster or network disruption
- Requirements for configuring VVR in a VCS environment
- Generic VVR setup in a VCS environment
- Example VVR configuration in a VCS environment
- Example RVG configuration for a failover application
- Example RVG configuration for a parallel application
- Example setting up VVR in a VCS environment
- Configuring the agents for a bunker replication configuration
- Administering VCS service groups
- Section II. Setting up and administering VVR
- Setting up replication
- About configuring VVR replication
- Enabling security certificate
- Setting up the certificate authority (CA) certificates in /etc/vx/vvr/cacert.pem
- Creating a Replicated Data Set
- Creating a Primary RVG of an RDS
- Adding a Secondary to an RDS
- Changing the replication settings for a Secondary
- Synchronizing the Secondary and starting replication
- Starting replication when the data volumes are zero initialized
- Starting replication over the wire when data volumes are encrypted
- Setting up replication with different sector-sized disks
- Displaying configuration information
- Displaying RVG and RDS information
- Displaying information about data volumes and volume sets
- Displaying information about Secondaries
- Displaying a list of Storage Checkpoints
- Displaying statistics with the vrstat display commands
- Displaying the consolidated statistics
- Displaying the RLINK information for all the hosts in the RDS
- Displaying information about all the data volumes for all the hosts in the RDS
- Displaying information about the SRL volumes for all the hosts in the RDS
- Displaying information about the memory tunable parameters for all the hosts in the RDS
- Determining VVR network bandwidth usage and compression ratio
- Collecting consolidated statistics of the VVR components
- Displaying network performance data
- VVR event notification
- Administering Volume Replicator
- Administering data volumes
- Associating a volume to a Replicated Data Set
- Associating a volume set to an RDS
- Associating a Data Change Map to a data volume in DCO
- Associating a Data Change Map to a data volume as a log plex
- Resizing a data volume in a Replicated Data Set
- Renaming a data volume in a Replicated Data Set
- Dissociating a data volume from its Replicated Data Set
- Mapping the name of a Secondary data volume to a differently named Primary data volume
- Mapping disk groups
- Administering the SRL
- Protecting from SRL overflow
- Incrementally synchronizing the Secondary after SRL overflow
- SRL overflow protection with DCM - flags and definitions
- Prerequisite for incrementally synchronizing the Secondary
- Breaking off mirrors before incremental synchronization
- Example - Resynchronizing the Secondary using break off mirrors
- Example - Recreating volumes if a disaster occurs during resynchronization
- Notes on using incremental synchronization on SRL overflow
- Changing the size of the SRL on the Primary and the Secondary
- Decreasing the size of the SRL on the Primary
- Administering replication
- Administering the Replicated Data Set
- Administering Storage Checkpoints
- Creating RVG snapshots
- Using the instant snapshot feature
- About instant full snapshots
- Prerequisites for creating instant full snapshots
- Creating snapshot volumes for data volumes in an RVG
- Preparing the volumes prior to using the instant snapshot feature
- Freezing or pausing replication prior to taking a snapshot
- Creating instant full snapshots
- Unfreezing or resuming replication after taking a snapshot
- About instant space-optimized snapshots
- Preparing the RVG volumes for snapshot operation
- Creating the cache object for instant space-optimized snapshots
- Freezing or pausing replication prior to creating an instant space-optimized snapshot
- Creating instant space-optimized snapshots
- Unfreezing or resuming replication after taking an instant space-optimized snapshot
- About instant plex-breakoff snapshots
- Administering snapshots
- Using the traditional snapshot feature
- Using Veritas Volume Manager FastResync
- Verifying the DR readiness of a VVR setup
- Backing up the Secondary
- Administering data volumes
- Using VVR for off-host processing
- Transferring the Primary role
- About transferring the Primary role
- Migrating the Primary
- About taking over from an original Primary
- Failing back to the original Primary
- About choosing the Primary site after a site disaster or network disruption
- Application availability in the case of a network disruption
- Configuring VCS global clustering so you can choose the Primary site
- Choosing the Primary site after a site disaster or network disruption
- Troubleshooting the primary-elect feature
- Primary-elect configuration limitations
- Replication using a bunker site
- Introduction to replication using a bunker site
- Sample bunker configuration
- Setting up replication using a bunker site
- Administering replication using a bunker site
- Using a bunker for disaster recovery
- Replication using a bunker site in a VCS environment
- Removing a bunker
- About bunker commands
- Configuring and administering VVR using System Management Interface Tool
- About SMIT for VVR
- Accessing Volume Replicator interface in SMIT
- Setting up a simple Volume Replicator configuration using SMIT
- Displaying configuration information using SMIT
- Administering Volume Replicator using SMIT
- Pausing replication to a Secondary using SMIT
- Resuming replication to a Secondary using SMIT
- Resynchronizing a Secondary using SMIT
- Taking traditional snapshot of data volumes of an RVG using SMIT
- Taking instant snapshot of data volumes of an RVG using SMIT
- Snapback of data volumes of an RVG using SMIT
- Associating a volume to a Replicated Data Set using SMIT
- Dissociating a data volume from a Replicated Data Set using SMIT
- Removing a Secondary from a Replicated Data Set using SMIT
- Removing a Primary from an RDS using SMIT
- Stopping replication to a Secondary using SMIT
- Transferring the Primary role using SMIT
- Troubleshooting VVR
- Recovery from RLINK connect problems
- Recovery from configuration errors
- Errors during an RLINK attach
- Errors during modification of an RVG
- Recovery on the Primary or Secondary
- About recovery from a Primary-host crash
- Recovering from Primary data volume error
- Primary SRL volume error cleanup and restart
- Primary SRL volume error at reboot
- Primary SRL volume overflow recovery
- Primary SRL header error cleanup and recovery
- Secondary data volume error cleanup and recovery
- Secondary SRL volume error cleanup and recovery
- Secondary SRL header error cleanup and recovery
- Secondary SRL header error at reboot
- Tuning replication performance
- Overview of replication tuning
- SRL layout
- Tuning Volume Replicator
- VVR buffer space
- Write buffer space on the Primary
- Readback buffer space on the Primary
- Buffer space on the Secondary
- Tunable parameters for the VVR buffer spaces
- Tunable parameters for the write buffer space on the Primary in a private disk group
- Tunable parameter for the readback buffer space
- Tunable parameters for the buffer space on the Primary in a shared disk group
- Tunable parameters for the buffer space on the Secondary
- DCM replay block size
- Heartbeat timeout
- Memory chunk size
- UDP replication tuning
- Tuning the number of TCP connections
- Message slots on the Secondary
- VVR and network address translation firewall
- Tuning VVR compression
- VVR buffer space
- Setting up replication
- Section III. Analyzing your environment with Volume Replicator Advisor
- Introducing Volume Replicator Advisor (VRAdvisor)
- Collecting the sample of data
- About collecting the sample of data
- Collecting the sample of data on UNIX
- Collecting the sample of data on Windows
- Analyzing the sample of data
- About analyzing the sample of data
- Launching the VRAdvisor wizard
- Analyzing the collected data
- Understanding the results of the analysis
- Viewing the analysis results
- Recalculating the analysis results
- Applying different parameters to the existing sample of data
- Performing What-if analysis
- Calculating the SRL Size for a specified Network Bandwidth and Outage
- Calculating the Network Bandwidth for data loss specified in bytes
- Calculating the Network Bandwidth for data loss specified in time duration
- Calculating the Network Bandwidth for Bunker and RTO
- Changing the value ranges on the slider bar
- Recording and viewing the results
- Installing Volume Replicator Advisor (VRAdvisor)
- Section IV. VVR reference
- Appendix A. VVR command reference
- Appendix B. Using the In-band Control Messaging utility vxibc and the IBC programming API
- About the IBC messaging utility vxibc
- In-band Control Messaging overview
- Using the IBC messaging command-line utility
- Registering an application name
- Displaying the registered application name for an RVG
- Receiving an IBC message
- Sending an IBC message
- Unfreezing the Secondary RVG
- Unregistering an application name
- Receiving and processing an IBC message using a single command
- Sending and processing an IBC message using a single command
- Examples - Off-host processing
- Example 1 - Decision support using the traditional snapshot feature and the vxibc utility
- Example 2 - Backing up using the snapshot feature and the vxibc utility
- Example 3 - Trial failover using the snapshot feature
- Example 4 - Decision support using the instant full snapshot feature and the vxibc utility
- In-band Control Messaging API
- Appendix C. Volume Replicator object states
- Appendix D. Alternate methods for synchronizing the Secondary
- Using the full synchronization feature
- Using block-level backup and Storage Checkpoint
- Using the Disk Group Split and Join feature
- Using difference-based synchronization
- Examples for setting up a simple Volume Replicator configuration
- Creating a Replicated Data Set for the examples
- Example for setting up replication using full synchronization
- Example for setting up replication using block-level backup and checkpointing
- Example for setting up replication using Disk Group Split and Join
- Example for setting up replication using differences-based synchronization
- Example for setting up replication when data volumes are initialized with zeroes
- Appendix E. Migrating VVR from IPv4 to IPv6
- Migrating VVR to support IPv6 or dual stack
- Overview of VVR migration from IPv4 to IPv6
- About migrating to IPv6 when VCS global clustering and VVR agents are not configured
- About migrating to IPv6 when VCS global clustering and VVR agents are configured
- Understanding the current IPv4 configuration when VCS global clustering and VVR agents are configured
- Migration prerequisites when VCS global clustering and VVR agents are configured
- Migrating to IPv6 when VCS global clustering and VVR agents are configured
- Migrating the VCS global clustering service group to IPv6 when VCS global clustering and VVR agents are configured
- Adding IP and NIC resources for IPv6 addresses in the RVG agent group when VCS global clustering and VVR agents are configured
- Migrating VVR RLINKs from IPv4 to IPv6 when VCS global clustering and VVR agents are configured
- Removing the IPv4 resources from the VCS configuration when VCS global clustering and VVR agents are configured
- About migrating to IPv6 when VCS global clustering and VVR agents are configured in the presence of a bunker
- Understanding the current IPv4 configuration when VCS global clustering and VVR agents are configured in the presence of a bunker
- Migration prerequisites when VCS global clustering and VVR agents are configured in the presence of a bunker
- Migrating to IPv6 when VCS global clustering and VVR agents are configured in the presence of a bunker
- Migrating the VCS global clustering service group to IPv6 when VCS global clustering and VVR agents are configured in the presence of a bunker
- 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
- Migrating VVR RLINKs from IPv4 to IPv6 when VCS global clustering and VVR agents are configured in the presence of a bunker
- Removing the IPv4 resources from the VCS configuration when VCS global clustering and VVR agents are configured in the presence of a bunker
- Appendix F. Sample main.cf files
Migrating VVR RLINKs from IPv4 to IPv6 when VCS global clustering and VVR agents are configured in the presence of a bunker
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.swax29 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.swax27 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.swax25 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.swax27 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.swax29 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.swax25 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.swax25 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.swax27 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.swax29 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.swax25 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.