The error message is seen while run vradmin -g <diskgroup> -l repstatus <rvg name> on secondary of Veritas Volume Replicator(VVR).

Article: 100023065
Last Published: 2021-07-16
Ratings: 1 0
Product(s): InfoScale & Storage Foundation

Problem

The error message is seen while run vradmin -g -l repstatus on secondary of Veritas Volume Replicator(VVR).

Error Message

VxVM VVR vradmin INFO V-5-52-1205 Primary is unreachable or RDS has configuration error.

Solution

Symptoms:
Themost common reason is caused by vradmind or vxconfigd process inexistence onprimary. So it needs to run vradmin command on primary for double confirm. Butother situations, such as, vradmind or vxconfigd restarted on one node, orsystem rebooted, and system gets panic, the error message can also be seen evenif the process vradmind or vxconfigd existence. This is due to timestamp issueof process. It does not imply replication function as well. The Secondary datais consistent and is current or up-to-date with the Primary data. The Primaryrole can be migrated to thisSecondary.  
Below is asample.
# vradmin -g gxerp_misp4_dg01-l repstatus gxerp_misp4_rvg01
VxVMVVR vradmin INFO V-5-52-1205 Primary is unreachable or RDS has configurationerror. Displayed status information is from Secondary and can be out-of-date.
Replicated Data Set:gxerp_misp4_rvg01 Primary:
Hostname:                  misdb2.gx.cmcc    <unreachable>
RVGname:                  gxerp_misp4_rvg01
DGname:                    gxerp_misp4_dg01
RVGstate:                  enabled forI/O
Datavolumes:               1
SRLname:                   dg01_srl
SRLsize:                   21.00 G
Totalsecondaries:          1
Secondary:
Hostname:                  SOL-REP2-1.hq.cmcc
RVGname:                  gxerp_misp4_rvg01
DGname:                    gxerp_misp4_dg01
Rlink fromPrimary:         rlk_dr_gxerp_misp4_rvg01
Rlink toPrimary:           rlk_gx_gxerp_misp4_rvg01
Configuredmode:            asynchronous
Latencyprotection:         off
SRLprotection:             autodcm
Datastatus:                consistent,up-to-date
Replicationstatus:         replicating(connected)
Currentmode:               N/A
Loggingto:                 SRL (0 updatesbehind, last update ID 52194.350770)
TimestampInformation:      behind by 00:00:00 hours
Last Update onPrimary:     Dec  8 14:34:41
Secondary up-to-date as of:Dec  8 14:34:41
BandwidthLimit:            3.00Mbps  
Config Errors:
misdb2.gx.cmcc:            Pri or Sec IP not available or vradmind not running, staleinformation

Check the value ofdata status, if it is in consistent, up-to-date status. The Secondary data isconsistent and is current or up-to-date with the Primary data. The Primary rolecan be migrated to this Secondary.
Value
Meaning
consistent,behind  
Secondary data is consistentbut not up-to-date with the Primary data.  
consistent,stale  
The data on this Secondary isconsistent. Replication to this Secondary has been stopped; the Primary RLINK isdetached.  
consistent,up-to-date  
The Secondary data isconsistent and is current or  up-to-date with the Primary data. The Primaryrole can be migrated to this Secondary.  
inconsistent  
The data on the Secondaryvolumes is not consistent and the Secondary cannot takeover.  
needs recovery  
State after an import orreboot. The vxrlink recover command clears thisstate.  
N/A  
Current state of the Secondarydata cannot be determined. This may occur because of a configuration error onthis Secondary. For information about the state, use the vxprint -lrlink_name command on the Primary andSecondary.  

Workaround:
1.Runthe following commands in turn, first on secondary thenprimary.
# /etc/init.d/vxrsyncd.sh stop
# /etc/init.d/vras-vradmind.sh stop
# /etc/init.d/vxnm-vxnetd stop
2.Run the following commands inturn, first on primary thensecondary.
# /etc/init.d/vxrsyncd.sh start
# /etc/init.d/vras-vradmind.sh start
# /etc/init.d/vxnm-vxnetdstart
The workaround sometimes cannot be guaranteed to solve the problem completely.
 

 

Was this content helpful?