Hi Samy, Are you going against a linux server? I don't think linux server has the functionality you are looking for. What you are really looking for I believe is session trunking and neither the linux client nor server fully support that (though we plan to add that functionality in the near future). Bruce, correct me if I'm wrong but linux server doesn't support multi-home (multi-node?) therefore, it has no ability to distinguish requests coming from different network interfaces and then present different server major/minor/scope values and also return different clientids in that case as well. So what happens now even though the client is establishing a new TCP connection via the 2nd network, the server returns back to the client same clientid and server identity as the 1st mount thus client will use an existing connection it already has. On Fri, Nov 8, 2019 at 3:48 AM Samy Ascha <samy@xxxxxxxxx> wrote: > > Hi! > > I have an NFS server with 2 NICs, configured on different subnets. These subnets are on different network segments (2 dedicated switches). > > I have clients that mount 2 distinct shares from this server. Expecting to spread the network load, I specified the mounts like so, in fstab: > > 10.110.1.235:/srv/nfs/www /var/www nfs defaults,rw,intr,nosuid,noatime,vers=4.1 0 0 > 10.110.0.235:/srv/nfs/backup /backup nfs defaults,rw,intr,nosuid,noatime,vers=4.1 0 0 > > However, as you may find totally expected, I see both mounts connected to the same IP on the server. Specificly, the one specified for the first mount: > > 10.110.1.235:/srv/nfs/www on /var/www type nfs4 (rw,...) > 10.110.1.235:/srv/nfs/backup on /backup type nfs4 (rw,...) > > Is this expected? Am I wrong to assume that this is a possible setup? If possible/forcible, what am I missing / doing wrong? :) > > Thanks much, > Samy
