2015-03-17 05:29 AM - last edited on 2015-04-08 07:37 PM by alissa
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!
Solved! SEE THE SOLUTION
2015-03-17 12:21 PM - edited 2015-03-17 07:18 PM
::>net ping -lif-owner cluster1-nfs-2 -lif cluster1-nfs-2-02 -destination x.x.x.x
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
2015-03-17 10:43 PM
Its probable worth confirming that your routing is configured correctly. You can obtain the routing information by running:
network routing-groups route show
2015-03-18 02:29 AM - edited 2015-03-18 11:36 AM
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.
Furhter, the client (linux) host CAN ping the lif through the specific nic, but not the other around, if I use "net ping..." command
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?
2015-03-18 10:09 PM
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.
2015-03-19 03:41 AM
Yes, the client IP is indeed the first hop.
> net traceroute -node node02 -destination x.x.30.109
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!