No relevant resource is found in the selected language.

This site uses cookies. By continuing to browse the site you are agreeing to our use of cookies. Read our privacy policy>Search


To have a better experience, please upgrade your IE browser.


The replication of Watchman dual system can not be built due to the incorrect rlk name

Publication Date:  2012-07-24 Views:  67 Downloads:  0

Issue Description

The replication of Watchman dual system can not be built.

Alarm Information

"Replication status is abnormal!"

Handling Process

1. Check the alarm and log info, find "rlk_10.0.0.20_wm_rvg", it is not created by Watchman. The rlk created by Watchman should be a_to_b_rlk or b_to_a_rlk.
2. Check the vea, find the rlk name is  "rlk_10.0.0.20_wm_rvg". This should be the root reason. Confirmed with on site engineer that they tried to buid replication via vea directly.
3. Change back the rlk name to a_to_b_rlk or b_to_a_rlk in vea.
4. Stop the replication via the follow command
#sh /etc/wmscript/stoprep
5. Build replication by "force active" or "force standby" in Watchman client, it succeed.

Root Cause

On site engineer tried to build replication via vea, and this led to the incorrect rlk name. vea set the rlk name as "rlk_serverIP_wm_rvg" in default, it's inconsistent with that Whatman named. This is the root reason of building replication failed.


Normally, using Watchman client to maintain the Watchman dual system is suggested. Not to operate directly vea for comman maintenance.