Snapvault (transfer aborted because of network error) after changing to vif

[AGREGERSEN]

I've changed our FAS2240 (destination for Snapvault) configuration from a single nic to a lacp based vif and rebooted (rc and hosts updated), but now Snapvault are failing and the FAS still has the same hostname and ip address. Eacho source can ping the destination by ip and hostname. /etc/messages doesn't reveal any more details.

Any ideas on how to solve this?

rc

hostname fas2240-1
ifgrp create lacp vif0 -b mac e0a e0b e0c e0d
vlan create vif0 2020
ifconfig vif0-2020 `hostname`-vif0 netmask 255.255.0.0 mtusize 9000
ifconfig e0a flowcontrol full
ifconfig e0b flowcontrol full
ifconfig e0c flowcontrol full
ifconfig e0d flowcontrol full
route add default 172.20.1.1 1
routed on
options dns.domainname int.ida.dk
options dns.enable on
options nis.enable off
savecore

hosts

#changed by agr Sun May 25 8:00:00 GMT+1 2014
127.0.0.1 localhost localhost-stack
127.0.10.1 localhost-10 localhost-bsd
127.0.20.1 localhost-20 localhost-sk
# 0.0.0.0       fas2240-1-e0M
# 0.0.0.0       fas2240-1-e0P
# 172.20.2.113    fas2240-1 fas2240-1-e0a
# 0.0.0.0       fas2240-1-e0b
# 0.0.0.0       fas2240-1-e0c
# 0.0.0.0       fas2240-1-e0d
172.20.2.113    fas2240-1 fas2240-1-vif0

[neto]

Hi my friend

This is neto from Brazil

How are you?

Could you please share the error message?

Thank you,

neto

[AGREGERSEN]

Hi neto

The error message is in the subject

"Transfer aborted because of network error"

I wish there was more information, but sadly that is what it says in messages for each qtree and nfs I have protected with snapvault. If there are other logfiles that could contain more detailed information I'll gladly go through them.

Cheers,

 Anders

[rwelshman]

You can look in the snapmirror log file on both the source and the destination filers, that may give you some more details as to the cause.

[AGREGERSEN]

Snapmirror log

src Wed May 20 06:08:12 CES fas3240-1:/vol/fas3240_1_aggr0_nfs1/- fas2240-1:/vol/sv_fas3240_1_aggr0_nfs1/vmwarexdataset_fas3240-1_fas32 Request (172.20.2.113)
slk Wed May 20 06:08:12 CES state.qtree_softlock.fas3240_1_aggr0_nfs1.008883d6.004.-.src-qt.fas2240-1:/vol/sv_fas3240_1_aggr0_nfs1/vmwarexdataset_fas3240-1_fas3
2.00000000.-01.1 Softlock_add (Transfer)
src Wed May 20 06:08:12 CES fas3240-1:/vol/fas3240_1_aggr0_nfs1/- fas2240-1:/vol/sv_fas3240_1_aggr0_nfs1/vmwarexdataset_fas3240-1_fas32 Start
slk Wed May 20 08:24:36 CES state.qtree_softlock.fas3240_1_aggr0_nfs1.00886130.003.-.src-qt.fas2240-1:/vol/sv_fas3240_1_aggr0_nfs1/vmwarexdataset_fas3240-1_fas3
2.00000000.-01.1 Softlock_delete (Transfer)
src Wed May 20 08:24:36 CES fas3240-1:/vol/fas3240_1_aggr0_nfs1/- fas2240-1:/vol/sv_fas3240_1_aggr0_nfs1/vmwarexdataset_fas3240-1_fas32 End (279337776 KB)
src Thu May 21 22:27:54 CES - - Request (172.20.2.113)
src Thu May 21 22:27:54 CES - - Abort (transfer aborted because of network error)

[AGREGERSEN · Accepted solution]

Hi

It seems that I have a breakthrough. Two items was different from before. The old host name FAS2240-1-e0a was commented out in the hosts file and the mtu was changed from 1500 to 9000 to increase some local copy jobs on the same LAN as our 2240.

After adding the FAS2240-1-e0a to the hosts file and changing the new vif0-2020 mtu from 9000 to 1500 the snapvault seems to be working again - currently it's copying data and if and when it succeeds I'll update that as well.

[AGREGERSEN]

It worked. I'm not sure which of the two changes that solved the problem.