# vradmin -g nbu_dg -l repstatus nbu_rvg
data status consistent, behind replication status: paused due to network disconnection timestamp behind 18h 12m 49s asynchronous
# vxprint -PVl flags
write enabled attached consistent disconnected asynchronous
One of the VVR daemons had stopped communicating between the VVR primary and secondary. There are three VVR daemons that are started by the system at runtime. They are vradmind, in.vxrsynchd, and vxnetd.
In this issue, it was the vxnetd daemon that was not communicating, as this is the daemon that provides communication between the rlinks of the VVR primary and secondary.
The customer called in, and I had him do a # /usr/sbin/vxstart_vvr stop and start on each node, and this resolved the issue.
# vxprint -PVl shows the rlink is attached, but not connected.