as long as there is routing between 172.20.0.x and 10.1.3.x then of course. If you can ping 172.20.0.50 from 10.1.3.x subnet that should give you a clue. Another way to test is from the datamover itself try to ping 10.1.3.x subnet gateway (10.1.3.1 ..or whatever your company uses). Also make sure you have a default gateway defined on your datamover

server_route server_2 -list

Of course going through a router might be slower than creating an additional interface on the data mover for this VLAN

Depends on your network

thanks for the reply.  im able to ping from datamover  using interface 172.20.0.50 to any host in the same VLAN but im not able to ping from datamover using interface 172.20.0.50 to different Vlan(10.1.3.X) .

from client side(10.1.3.X) i can ping to interface successfully  .

is this normal behavior ???

got (correct) default route configured on the datamover ?

Probably yes

Access depends on your existing export options – please see the “Managing NFS on VNX” manual to lean how NFS export options work

just to be more clear to me once the host be able to ping the interface the nfs share will be able mount in the host? is it correct?

and i have to export the nfs and add the host in the host access ?