Start a Conversation

This post is more than 5 years old

Solved!

Go to Solution

542

November 23rd, 2013 10:00

Discovering which interface a host is using

Hey guys - Just started a new position at a large enterprise. They immediately hit me with decomming an NS-960 (2 DM's 1 standby) Unified frame. So I'm doing host based NFS migrations via management AIX server to a VNX7500 with 6DM's and 1 standby. I do not have access to the actual Unix/Linux servers that use the NFS exports. The network has been setup on the VNX with interfaces on the same subnets as the interfaces on the 960.

The issue I'm facing is: the interfaces are now spread out through more data movers and I need to put the new (target) VNX filesystems on the data movers who's interfaces match that of the 960's.

My question is: how do I tell which interface a host is using when multiple are configured for 1 data mover? Emails are often not replied to when trying to find out from the Unix admins.

1.2K Posts

November 26th, 2013 08:00

One way is use the "server_netstat" command.  This will show you the IP address of the source server and which interface on the NS960 it's connected to:

[nasadmin@vnxtest-cs0 ~]$ server_netstat server_2

Proto Local Address                  Foreign Address      (state)

******************************************************************

tcp  10.212.88.6.portmapper         10.211.111.145.53156  ESTABLISHED

tcp  10.212.88.6.portmapper         10.211.111.148.59169  ESTABLISHED

tcp  10.212.88.6.mount              10.211.111.145.608    ESTABLISHED

tcp  10.212.88.6.mount              10.211.111.148.974    ESTABLISHED

tcp  10.212.88.6.nfs                10.200.80.7.909       ESTABLISHED

tcp  10.212.88.6.nfs                10.211.111.145.38264  ESTABLISHED

tcp  10.212.88.6.lockd              10.211.111.145.37312  ESTABLISHED

tcp  10.212.88.6.lockd              10.211.111.148.41216  ESTABLISHED

tcp  10.211.111.126.portmapper      10.211.111.145.34360  ESTABLISHED

tcp  10.211.111.126.portmapper      10.211.111.148.34550  ESTABLISHED

tcp  10.211.111.126.NETBIOS-Session 10.200.35.211.1044    ESTABLISHED

tcp  10.211.111.126.NETBIOS-Session 10.211.111.145.34154  ESTABLISHED

tcp  10.211.111.126.NETBIOS-Session 10.211.111.148.38655  ESTABLISHED

tcp  10.211.111.126.NETBIOS-Session 10.211.111.213.2093   ESTABLISHED

tcp  10.211.111.126.CIFS            10.128.10.99.4893     ESTABLISHED

tcp  10.211.111.126.nfs             10.211.111.145.609    ESTABLISHED

tcp  10.211.111.126.nfs             10.211.111.148.975    ESTABLISHED

tcp  10.211.111.126.nfs             10.211.111.145.55453  ESTABLISHED


If you look at the *.nfs entries above, these correspond to the network interfaces on my VNX.  On the right hand side, those IP addresses are the IPs of the Linux and Solaris servers accessing my resources.  Note that I have multiple IPs configured on my VNX, but each server is currently accessing only one IP address.


Let us know if this helps!


Karl

No Events found!

Top