FAS3140 CIFS/NFS/ISCSI connection issue

abknoc · ‎2013-08-21

Hey guys,

We have a problem with our NFS mounts on VMWare. Our environment now:

2 x FAS3140 HA cluster with 10gig NIC cards, ONTap version 8.1.2

5 x ESX hosts all running 1 gig NICs

Intermittently the NFS storage on the ESX hosts will go out. This will only happen on random ESX hosts. The outage that occurs is not consistent with ESX host and time. We had just upgraded from a 4 port 1 gig NIC to a 2 port 10 gig port NIC. When we had the 1 gig NIC, there were no problems but with the 10gig, we are having all sorts of little problems.

Our RC file on Netapp looks like this:

ifgrp create single vif e4a e4b

vlan create vif 67 80

ifconfig vif 172.67.1.35 netmask 255.255.0.0 partner vif

ifconfig vif-67 172.67.1.37 netmask 255.255.0.0 partner vif-67

ifconfig vif-80 172.80.1.21 netmask 255.255.0.0 partner vif-80

route add default 172.67.1.222 1

routed on

options dns.domainname our.domain.net

options dns.enable on

options nis.enable off

savecore

Currently:

Vif is serving CIFS

Vif-67 is serving NFS

Vif-80 is serving ISCSI

e4a and e4b are our 10gig cards

e0a and e0b are our 1 gig cards and are not being used right now.

We are not using e0a and e0b because we can not figure out how the RC file configuration has to be to serve the CIFS over that and have NFS/ISCSI over the e4a and e4b. Any config we do, the Netapp will not respond over the ports e0a and e0b.

Can anyone shed some light or tell me what I am missing? Any help would be greatly appreciated.

resqme914 · ‎2013-08-21

I don't profess to be a networking expert, but I would've thought that the vlan create command would turn the vif interface into a vlan-only interface and that you wouldn't be able to use "vif" with an ip address, and that you should've created another vlan for the CIFS traffic. Did this rc file actually work on a reboot?

Also, have you ruled out a hardware problem on your new nic or on the network/switch side?

How are you restricting the protocols to specific interfaces? options interface.blocked?

aborzenkov · ‎2013-08-21

Starting with 8.0 (I think) it is possible to use VLAN base interface as well.

Отправлено с iPhone

22.08.2013, в 0:05, "resqme914" <xdl-communities@communities.netapp.com<mailto:xdl-communities@communities.netapp.com>> написал(а):

<https://communities.netapp.com/index.jspa>

Re: FAS3140 CIFS/NFS/ISCSI connection issue

created by resqme914<https://communities.netapp.com/people/resqme914> in Storage Systems - View the full discussion<https://communities.netapp.com/message/115470#115470>

I don't profess to be a networking expert, but I would've thought that the vlan create command would turn the vif interface into a vlan-only interface and that you wouldn't be able to use "vif" with an ip address, and that you should've created another vlan for the CIFS traffic. Did this rc file actually work on a reboot?

Also, have you ruled out a hardware problem on your new nic or on the network/switch side?

How are you restricting the protocols to specific interfaces? options interface.blocked?

Reply to this message by replying to this email -or- go to the message on NetApp Community<https://communities.netapp.com/message/115470#115470>

Start a new discussion in Storage Systems by email<mailto:discussions-community-products_and_solutions-storage_systems@communities.netapp.com> or at NetApp Community<https://communities.netapp.com/choose-container.jspa?contentType=1&containerType=14&container=2878>

resqme914 · ‎2013-08-22

Thanks for the correction. I was going to try this on the 8.2 simulator yesterday but ran out of time.

abknoc · ‎2013-08-22

We have ruled out hardware problem on the NIC cards. We switched to two different NIC cards and the results are the same.

We are not restricting the protocols via the interface. The reason why we have it setup like the above is because we have another two filers that are setup the exact same way in another location and those are working fine.

And yes, the RC file will boot up correctly and no errors show. The NFS mounts for VMWare go out intermittently without any errors logged on either environment.