vol show -field policy -vserver ocna06c-nfs
(volume show)
vserver volume policy
----------- ----------------- ----------
test-nfs test1 testvm
.....
(network interface show)
Logical Status Network Current Current Is
Vserver Interface Admin/Oper Address/Mask Node Port Home
----------- ---------- ---------- ------------------ ------------- ------- ----
test-nfs
test-nfs_nfs_lif1
up/up 10.9.9.9/24 testA a0a-670 true
Vserver Name: test-nfs
Logical Interface Name: test-nfs_nfs_lif1
Role: data
Data Protocol: nfs
Home Node: testA
Home Port: a0a-670
Current Node: testA
Current Port: a0a-670
Operational Status: up
Extended Status: -
Numeric ID: 1039
Is Home: true
Network Address: 10.9.9.9
Netmask: 255.255.255.0
Bits in the Netmask: 24
IPv4 Link Local: -
Routing Group Name: d10.9.9.0/24
Administrative Status: up
Failover Policy: nextavail
Firewall Policy: mgmt
Auto Revert: false
Sticky Flag: false
Fully Qualified DNS Zone Name: none
DNS Query Listen Enable: false
Load Balancing Migrate Allowed: false
Load Balanced Weight: load
Failover Group Name: system-defined
FCP WWPN: -
Address family: ipv4
Comment: -
eth0 Link encap:Ethernet HWaddr 00:50:56:B4:7D:A9
inet addr:10.9.9.3 Bcast:10.9.9.255 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:1871372 errors:0 dropped:0 overruns:0 frame:0
TX packets:2047231 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:605262141 (577.2 MiB) TX bytes:286957218 (273.6 MiB)
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
UP LOOPBACK RUNNING MTU:65536 Metric:1
RX packets:47212 errors:0 dropped:0 overruns:0 frame:0
TX packets:47212 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:10208922 (9.7 MiB) TX bytes:10208922 (9.7 MiB)
[root@/]# netstat -rn
Kernel IP routing table
Destination Gateway Genmask Flags MSS Window irtt Iface
10.9.9.0 0.0.0.0 255.255.255.0 U 0 0 0 eth0
169.254.0.0 0.0.0.0 255.255.0.0 U 0 0 0 eth0
0.0.0.0 10.9.9.1 0.0.0.0 UG 0 0 0 eth0
The NFS vserver only has visiabilty to DATA interface...how can route would go somewhere else?
On Monday, December 22, 2014 3:10 PM, tmac <tmacmd@gmail.com> wrote:
So, got this data so far:
appears to be using a0a (single mode e0b/e0d, e0b active, e0d not so much with IP distribution)
10.9.9.9:/test1 on /mnt1 type nfs (rw,bg,hard,intr,rsize=32768,wsize=32768,vers=3,tcp,timeo=600,addr=10.9.9.9)
--> tried both intr and nointr
Confirmed v3 is ENABLED and all v4+ are disabled on the NFS vserver
TCP & UDP are both enabled on vserver
No Jumbo frames
No blatant errors showing via netstat -i on the client or netapp side
Flow control appears off from cdot point of view.
have the export-policy rule data
Waiting for this data:
vol show -field policy
Wondering if it might be related.
--> Iluhes
Please send:
vol show -field policy
net int show -vserver test-nfs -instance
(would like to see all the network interface details)
Also send the client-side "ifconfig -a" for all interfaces, including netstat -rn
maybe there is a bad route someplace.