Problem

How to use Vxprint to verify that the Rlinks, hostnames and IP addresses for the primary and secondary replication partners match each other in Veritas Storage Foundation for Windows - Volume Replicator Option.

In VVR (Veritas Volume Replicator),

Error Message

When running the command vxprint -VPl will report the flags below:

write attached consistent disconnected

Cause

If either replication partner contains invalid information, replication will stop. each partner may report the other as "disconnected."

Solution

Vxprint can be used to verify that the Rlinks, hostnames and IP addresses for the primary and secondary replication partners match each other.

Run vxprint -VPl on both sites:

Note: That is an upper-case V, an upper-case P and a lower-case L.
This will return results that are similar to the following:

Sample Vxprint Results from a Primary

Disk group: vvrdg
Rlink:    rlk_192.168.20.51_vvrrvg
info:      timeout=500 rid=0.1080
             latency_high_mark=10000 latency_low_mark=9950
             bandwidth_limit=none
state:    state=ACTIVE
             synchronous=off latencyprot=off srlprot=autodcm
assoc:    rvg=vvrrvg
              remote_host=192.168.20.51 IP_addr=192.168.20.51 port=4145
              remote_dg=vvrdg
              remote_dg_dgid=1490633094.42.DRServer201
              remote_rvg_version=45
              remote_rlink=rlk_192.168.20.50_vvrrvg
              remote_rlink_rid=0.1115
              local_host=192.168.20.50 IP_addr=192.168.20.50 port=4145
protocol: TCP/IP
flags:    write enabled attached consistent connected asynchronous

                 Rvg:       vvrrvg
                 info:        rid=0.1076 version=0 rvg_version=45 last_tag=1
                 state:      state=ACTIVE kernel=ENABLED
                 assoc:    datavols=vvrdatavol
                                srl=vvrsrlvol
                                rlinks=rlk_192.168.20.51_vvrrvg
                                exports=(none)
                                vsets=(none)
                att:           rlinks=rlk_192.168.20.51_vvrrvg
                flags:        closed primary enabled attached logging bulktransfer
                device:     minor=4002 bdev=199/4002 cdev=199/4002 path=/dev/vx/dsk/vvrdg/vvrrvg
                perms:      user=root group=root mode=0600
 

Sample Vxprint Results from a Secondary

  Disk group: vvrdg

 Rlink:      rlk_192.168.20.50_vvrrvg
                info:        timeout=500 rid=0.1115
                               latency_high_mark=10000 latency_low_mark=9950
                               bandwidth_limit=none
                state:      state=ACTIVE
                               synchronous=off latencyprot=off srlprot=autodcm
                assoc:     rvg=vvrrvg
                               remote_host=192.168.20.50 IP_addr=192.168.20.50 port=4145
                               remote_dg=vvrdg
                               remote_dg_dgid=1490648820.33.Server101
                               remote_rvg_version=45
                               remote_rlink=rlk_192.168.20.51_vvrrvg
                               remote_rlink_rid=0.1080
                               local_host=192.168.20.51 IP_addr=192.168.20.51 port=4145
                protocol: TCP/IP
                flags:       write enabled attached consistent connected

                Rvg:       vvrrvg
                info:        rid=0.1073 version=0 rvg_version=45 last_tag=1
                state:      state=ACTIVE kernel=ENABLED
                assoc:    datavols=vvrdatavol
                               srl=vvrsrlvol
                               rlinks=rlk_192.168.20.50_vvrrvg
                               exports=(none)
                               vsets=(none)
                att:          rlinks=rlk_192.168.20.50_vvrrvg
                flags:      closed secondary enabled attached logging
                device:   minor=23002 bdev=199/23002 cdev=199/23002 path=/dev/vx/dsk/vvrdg/vvrrvg
                perms:    user=root group=root mode=0600
 

To confirm that the Rlink names, hostnames or IP addresses match both sites, follow these steps:

1. From the primary vxprint results, locate the following attributes:

Rlink:      rlk_192.168.20.50_vvrrvg
assoc: 
               local_host=192.168.20.50 IP_addr=192.168.20.50 port=4145
NOTE: There are two instances of assoc found in the vxprint results. These steps refer to the second instance.

2. Ensure that the values of the attributes that were found in the primary vxprint results match the following attributes on the secondary vxprint results:

assoc: remote_rlink
assoc: remote_host

The value of Rlink should match assoc: remote_rlink on the opposite partner.
The value of assoc: local_host should match the value of assoc: remote_host. on the opposite partner.

These values should match in both directions. If there is mismatch, review How to change IP address used by VVR in Veritas Storage Foundation for Windows. Volume