topic Re: what is the command to ping a NFS client via a Vlan port? in Network and Storage Protocols

what is the command to ping a NFS client via a Vlan port?

netappmagic — Thu, 05 Jun 2025 04:51:06 GMT

For instance, I have a backup Vlan and need to verify the connection to a backup nic on the host. CDOT

Thank you for sharing!

JSHACHER11 — Tue, 17 Mar 2015 12:59:42 GMT

you can ping from a lif, not a VLAN:

net ping -lif lif_nfs2 -destination IP

netappmagic — Wed, 18 Mar 2015 02:18:25 GMT

::>net ping -lif-owner cluster1-nfs-2 -lif cluster1-nfs-2-02 -destination x.x.x.x

(network ping)
no answer from x.x.x.x

I could not get the response back when I run the above command on the filer.

Both are on the same subnet, a private network for backup. I got the lif name "cluster1-nfs-2-01" from "net int show" command.

Can anything block the ping between host and the filer? there is no firewall here.

Should I try something else, or is there something else I need to do before the following command could work out?

It seems that I could not use IP address to replace lif name

Tiedan — Wed, 18 Mar 2015 05:43:52 GMT

Its probable worth confirming that your routing is configured correctly. You can obtain the routing information by running:

network routing-groups route show

netappmagic — Wed, 18 Mar 2015 18:36:41 GMT

Well, I tried the routing group command.

However, the lif and the nic on the client host are located on the same subnet, both are x.x.30.x, so, routing group should not be invovoled.

Correct?

Furhter, the client (linux) host CAN ping the lif through the specific nic, but not the other around, if I use "net ping..." command

Whe

vlan that is associating with lif has the following settings:
Auto-Negot Duplex Speed (Mbps)
Node Port Role Link MTU Admin/Oper Admin/Oper Admin/Oper

data up 9000 true/- auto/full auto/10000

The lif connection looks healthy. Could something blocked ping on the filer?

Tiedan — Thu, 19 Mar 2015 05:09:36 GMT

Can you perform a traceroute from the netapp to the client?

network traceroute -node <node name> -destination <destination ip>

If its setup correctly the client should be the first hop.

netappmagic — Thu, 19 Mar 2015 10:41:54 GMT

Yes, the client IP is indeed the first hop.

> net traceroute -node node02 -destination x.x.30.109
(network traceroute)

traceroute to x.x.30.109 (x.x.30.109), 64 hops max, 52 byte packets
1 linx_host (x.x.30.109) 0.490 ms !Z 0.208 ms !Z 0.177 ms !Z

right, this comand showed there is no switch involved.

Looking forward to hear the next step. Thank you!