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

Article:TECH87318  |  Created: 2009-01-06  |  Updated: 2009-01-03  |  Article URL http://www.symantec.com/docs/TECH87318
Article Type
Technical Solution


Environment

Issue



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

Error



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

Solution



Symptoms:
The most common reason is caused by vradmind or vxconfigd process inexistence on primary. So it needs to run vradmin command on primary for double confirm. But other situations, such as, vradmind or vxconfigd restarted on one node, or system rebooted, and system gets panic, the error message can also be seen even if the process vradmind or vxconfigd existence. This is due to timestamp issue of process. It does not imply replication function as well. The Secondary data is consistent and is current or up-to-date with the Primary data. The Primary role can be migrated to this Secondary.  
Below is a sample.
# vradmin -g gxerp_misp4_dg01 -l repstatus gxerp_misp4_rvg01
VxVM VVR vradmin INFO V-5-52-1205 Primary is unreachable or RDS has configuration error. Displayed status information is from Secondary and can be out-of-date.
Replicated Data Set: gxerp_misp4_rvg01 Primary:
Host name:                  misdb2.gx.cmcc    <unreachable>
RVG name:                   gxerp_misp4_rvg01
DG name:                    gxerp_misp4_dg01
RVG state:                  enabled for I/O
Data volumes:               1
SRL name:                   dg01_srl
SRL size:                   21.00 G
Total secondaries:          1
Secondary:
Host name:                  SOL-REP2-1.hq.cmcc
RVG name:                   gxerp_misp4_rvg01
DG name:                    gxerp_misp4_dg01
Rlink from Primary:         rlk_dr_gxerp_misp4_rvg01
Rlink to Primary:           rlk_gx_gxerp_misp4_rvg01
Configured mode:            asynchronous
Latency protection:         off
SRL protection:             autodcm
Data status:                consistent, up-to-date
Replication status:         replicating (connected)
Current mode:               N/A
Logging to:                 SRL (0 updates behind, last update ID 52194.350770)
Timestamp Information:      behind by 00:00:00 hours
Last Update on Primary:     Dec  8 14:34:41
Secondary up-to-date as of: Dec  8 14:34:41
Bandwidth Limit:            3.00 Mbps  
Config Errors:
misdb2.gx.cmcc:             Pri or Sec IP not available or vradmind not running, stale information

Check the value of data status, if it is in consistent, up-to-date status. The Secondary data is consistent and is current or up-to-date with the Primary data. The Primary role can be migrated to this Secondary.
Value
Meaning
consistent, behind  
Secondary data is consistent but not up-to-date with the Primary data.  
consistent, stale  
The data on this Secondary is consistent. Replication to this Secondary has been stopped; the Primary RLINK is detached.  
consistent, up-to-date  
The Secondary data is consistent and is current or  up-to-date with the Primary data. The Primary role can be migrated to this Secondary.  
inconsistent  
The data on the Secondary volumes is not consistent and the Secondary cannot take over.  
needs recovery  
State after an import or reboot. The vxrlink recover command clears this state.  
N/A  
Current state of the Secondary data cannot be determined. This may occur because of a configuration error on this Secondary. For information about the state, use the vxprint -l rlink_name command on the Primary and Secondary.  

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


Legacy ID



319124


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


Terms of use for this information are found in Legal Notices