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

Article:TECH52571  |  Created: 2007-01-09  |  Updated: 2013-08-29  |  Article URL http://www.symantec.com/docs/TECH52571
Article Type
Technical Solution

Product(s)

Environment

Issue



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


Solution




Introduction

In VVR (Veritas Volume Replicator), if either replication partner contains invalid information, replication will stop. Each partner may report the other as "disconnected." Vxprint can be used to verify that the Rlinks, hostnames and IP addresses for the primary and secondary replication partners match each other.


Solution

1. Run the following command on both sites:

 
vxprint -VPl
 

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:


Figure 1 - Sample Vxprint Results from a Primary

 
Diskgroup = BasicGroup
 

 
Diskgroup = jhkexch1
 

 
Diskgroup = vvr
 

 
Rvg        : vvr_rdg
 
state      : state=ACTIVE kernel=ENABLED
 
assoc      : datavols=\Device\HarddiskDmVolumes\vvr\data1
 
            srl=\Device\HarddiskDmVolumes\vvr\srl
 
            rlinks=rlk_hroha01a_12843
 
att        : rlinks=rlk_hroha01a_12843
 
checkpoint :
 
flags      : primary enabled attached
 

 
Rlink      : rlk_hroha01a_12843
 
info       : timeout=500 packet_size=8400
 
            latency_high_mark=10000 latency_low_mark=9950
 
            bandwidth_limit=none
 
state      : state=ACTIVE
 
            synchronous=override latencyprot=off srlprot=autodcm
 
assoc      : rvg=vvr_rdg
 
            remote_host=10.65.98.61
 
            remote_dg=vvr
 
            remote_rlink=rlk_hroha01b_25239
 
            local_host=10.65.98.62
 
protocol   : UDP/IP
 
flags      : write attached consistent connected
 



Figure 2 - Sample Vxprint Results from a Secondary

 
Diskgroup = BasicGroup
 

 
Diskgroup = System
 

 
Diskgroup = vvr
 

 
Rvg        : vvr_rdg
 
state      : state=ACTIVE kernel=ENABLED
 
assoc      : datavols=\Device\HarddiskDmVolumes\vvr\data1
 
            srl=\Device\HarddiskDmVolumes\vvr\srl
 
            rlinks=rlk_hroha01b_25239
 
att        : rlinks=rlk_hroha01b_25239
 
checkpoint :
 
flags      : secondary enabled attached
 

 
Rlink      : rlk_hroha01b_25239
 
info       : timeout=500 packet_size=8400
 
            latency_high_mark=10000 latency_low_mark=9950
 
            bandwidth_limit=none
 
state      : state=ACTIVE
 
            synchronous=override latencyprot=off srlprot=autodcm
 
assoc      : rvg=vvr_rdg
 
            remote_host=10.65.98.62
 
            remote_dg=vvr
 
            remote_rlink=rlk_hroha01a_12843
 
            local_host=10.65.98.61
 
protocol   : UDP/IP
 
flags      : write attached consistent connected
 


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

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

 
Rlink
 
assoc: local_host
 

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 the following:

- An IP address mismatch can be corrected by following the procedure found in this article:  http://support.veritas.com/docs/245929
- Other mismatches should be resolved by recreating the RVG that contains the invalid information. A procedure for recreating a secondary RVG can be found in this article:  http://support.veritas.com/docs/289827


Keywords: 289868, a289868
 



Legacy ID



289868


Article URL http://www.symantec.com/docs/TECH52571


Terms of use for this information are found in Legal Notices