Snapmirror replication problem after move (10Mbps WAN)... Status: Transfering but Progress: 0KB...

[neves_jacques]

Good Morning,

I had a fully running SnapMirror configuration on my Gigabit LAN last week.

We've just moved the target filer (fas02) to the DR site.

We have now a 10Mbps WAN connection between the two sites.

I've run a "snapmirror update volcifs" the status is "Transferring" but Progress stay forever "0KB".

Here is the output and the /etc/snapmirror.conf

slpfas02> snapmirror status -l volcifs

Snapmirror is on.

Source:                 connection:volcifs

Destination:            slpfas02:volcifs

Status:                 Transferring

Progress:               0 KB

State:                  Snapmirrored

Lag:                    99:20:08

Mirror Timestamp:       Fri Dec 23 08:32:02 CET 2011

Base Snapshot:          slpfas02(0101177175)_volcifs.118

Current Transfer Type:  Update

Current Transfer Error: -

Contents:               Replica

Last Transfer Type:     Update

Last Transfer Size:     278036 KB

Last Transfer Duration: 00:00:16

Last Transfer From:     connection:volcifs

Here is below my configuration:

Source: fas01 (FAS3020)

Target: fas02 (FAS3020)

/etc/snapmirror.conf

-------------------------------------------------

slpfas02> rdfile /etc/snapmirror.conf

connection=multi(192.168.150.41,192.168.150.42)(192.168.156.41,192.168.156.42)

connection:volcifs slpfas02:volcifs wsize=202375 - - - -

connection:volnfs slpfas02:volnfs wsize=202375 - - - -

connection:volnfslab slpfas02:volnfslab wsize=202375 - - - -

-------------------------------------------------

Thanks for the support.

Regards,

JNV

[SNEWNAMBBT]

Just to start - you've checked all the simple things right? You can ping between the filers, you've made sure DNS resolves the names correctly and/or the host file was updated with the correct IP addresses for each filer?

[neves_jacques]

Hi Sam,

Thanks for your reply. Yes, DNS is correctly defined.

I've just solved the problem.

I've modified the MTU size from 1500 to 1400 bytes on the interface now it's working fine again.

Best regards,

Jacques Neves