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?
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
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.
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)
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.