Re: vfiler dr resync failing - Page 2

PKKASTURI · ‎2012-08-30

Hi,

I'm trying to perform vfiler dr resync from one filer to other filer. But didn't success, getting below error. I initially did vfiler dr configure on destination filer (netapp-02) and it got successfull. i've added some data and now i'm trying to syncing the data from destination (netapp-02) filer to source (netapp-01) filer.

netapp-01> vfiler status

vfiler0 running

vf-test stopped

netapp-01> vfiler dr resync vf-test@netapp-02

netapp-02's Administrative login: root

netapp-02's Administrative password:

cannot resync path /vol/src_vol: transfer aborted because of network error

Mon Aug 27 19:55:54 GMT [replication.dst.resync.failed:error]: SnapMirror resync of src_vol to netapp-02:src_vol : transfer aborted because of network error.

netapp-01> df -h test_vol

Filesystem total used avail capacity Mounted on

/vol/test_vol/ 240MB 66MB 173MB 28% /vol/test_vol/

netapp-01> snapmirror status

Snapmirror is on.

Source Destination State Lag Status

netapp-01:test_vol netapp-02:sm_vol Source - Idle

netapp-01:src_vol netapp-02:src_vol Source 161:51:16 Idle

netapp-01:test_vol netapp-02:test_vol Source 161:51:14 Idle

netapp-01>

netapp-02> df -h test_vol

Filesystem total used avail capacity Mounted on

/vol/test_vol/ 240MB 73MB 166MB 31% /vol/test_vol/

netapp-02> snapmirror status

Snapmirror is on.

Source Destination State Lag Status

netapp-01:src_vol netapp-02:src_vol Broken-off 06:25:12 Idle

netapp-01:test_vol netapp-02:test_vol Broken-off 06:25:10 Idle

netapp-02:src_vol netapp-01:src_vol Source - Idle

netapp-02:test_vol netapp-01:test_vol Source - Idle

netapp-02>

can anyone tell me what i'm missing?

Thanks,

Phani

scottgelb · ‎2014-03-28

It looks like it thinks the mirror is the same volume source and target. Have not seen dr resync do this. Anything weird or different in snapmirror.conf or dns or hosts files pointing to the same controller?

Sent from my iPhone 5

Eric_Johnson · ‎2015-04-03

I was having EXACTLY the same problem but was able to resolve it. It had to do with the fact that the simulators all share a common sys_serial_num and sysid which was causing the resync to throw an error about syncing to itself.

I followed the procedure to change the System ID and ran through the setup again and it worked.

This is on Netapp's site but here's a c&p

*****************************************************

Setting the System ID
---------------------

IMPORTANT: You must enter the two following commands BEFORE the Simulate ONTAP node boots up for the first time.

Follow the steps below to change the System ID and System Serial Number for the second node:

1. Once you start the Simulate ONTAP node, the system will begin the boot up process in 10 seconds unless you interrupt it. You will see the following information on the console:

Hit [Enter] to boot immediately, or any other key for command prompt.
Booting in 10 seconds...

2. Press any key other than the Enter key to interrupt the boot process. You will see the following information:

Type '?' for a list of commands, 'help' for more detailed help.
SIMLOADER>

3. Enter the following commands to set the Serial Number and System ID for this node:

SIMLOADER> setenv SYS_SERIAL_NUM 4034389-06-2
SIMLOADER> setenv bootarg.nvram.sysid 4034389062

4. Enter the following commands to verify that the information was saved correctly:

SIMLOADER> printenv SYS_SERIAL_NUM
4034389-06-2
SIMLOADER> printenv bootarg.nvram.sysid
4034389062

5. Now enter the "boot" command to boot up the node:

SIMLOADER> boot

*****************************************************

netappz · ‎2017-08-30

Thanks you Eric - that information was great and would have sorted the issue I came across, except it broke my SIM as it had already been booted 🙂

Not to worry though, as least I now know why it was failing (the duplicate sysids - never would have figured that otherwise).

Thanks again.