Re: NFS Mount over a Specific Interface

[Matthew J. Roth]

Apologies for the repost, but I flubbed the subject the first time...

Thank you for the response.

I should have been more specific in my original post.  The multiple NICs 
are on the NFS client.

One NIC on the NFS client will be receiving HEAVY VoIP traffic and I 
want any NFS traffic to be offloaded to a separate NIC on the client, as 
shown:
           ________           ________
         _|        |_        |        |
        |e|        |e|       |        |
  VoIP  |t|   NFS  |t|  NFS  |  NFS   |
--------|h| Client |h|-------| Server |
        |0|        |1|       |        |
         -|________|-        |________|

I'm looking for a way to tell the mount command on the NFS client which 
interface to use.  It defaults to the first active interface.  I can 
easily swap interfaces and IPs around in the box to meet my goal, but I 
was looking for a more flexible solution.

I've read the pertinent man pages and the NFS section in my network 
administration guide but they make no mention of this.  We are currently 
using NFS version 3.

Thank you,

Matthew Roth
InterMedia Marketing Solutions
Software Engineer and Systems Developer
> > I have a NIC that I would like to dedicate to an NFS mount.  After much 
> > reading, I can't find any mount options that let me specify the 
> > interface.  Mount seems to only want to use the first active NIC on the 
> > system.
> >
> > If anyone knows how to do this, I'd greatly appreciate your help.
> >
> > Thank you,
> >
> > Matthew Roth
> > InterMedia Marketing Solutions
> > Software Engineer and Systems Developer
>
> From what I can tell is you want an nfs client to attach to a certain
> nfs server interfaces. If you have the appropriate dns/host record's you
> should be able to make this happen.
>
> server01.domain.com 1.1.1.1/24
> server01-eth1.domaincom 1.1.2.1/24
>
> client.domain.com 1.1.1.2/24
> client-eth1.domain.com 1.1.1.2/24
>
> On client.domain.com
> mount server01-eth1.domain.com/exports /imports
>
> Common mistake most people tend to do is over look impact of the routing
> involved. If the client does not share a broadcast domain with the
> server, you are just going to create a heap of ____.
>
> Provide some details about your network topology with client and server
> shown for a better response.
>
> Regards,
> Ted

NFS Mount over a Specific Interface

[Les Mikesell]

On Tue, 2005-09-27 at 10:30, Matt Roth wrote:
> I should have been more specific in my original post.  The multiple NICs 
> are on the NFS client.
>
> One NIC on the NFS client will be receiving HEAVY VoIP traffic and I 
> want any NFS traffic to be offloaded to a separate NIC on the client, as 
> shown:
>            ________           ________
>          _|        |_        |        |
>         |e|        |e|       |        |
>   VoIP  |t|   NFS  |t|  NFS  |  NFS   |
> --------|h| Client |h|-------| Server |
>         |0|        |1|       |        |
>          -|________|-        |________|
>
> I'm looking for a way to tell the mount command on the NFS client which 
> interface to use.  It defaults to the first active interface.  I can 
> easily swap interfaces and IPs around in the box to meet my goal, but I 
> was looking for a more flexible solution.

The sure way to do it is to put it on a different subnet with an
address on the NFS server also on that subnet.  You could either
add a physical interface to the NFS server to match or just overlay
another address on the existing interface if you don't care about
isolating the traffic on that side or the backbone path.

AW: NFS Mount over a Specific Interface

[Cetin Haftaoglu]

Dear Matt,

I think the solution for You is not to look for the nfs command, You 
must create a route (see man route) to link the traffic to an IP-adress 
or subnet to a special nic.

Regards,
Cetin

-----Ursprungliche Nachricht-----
Von: [e-mail]
[mailto:[e-mail]]Im Auftrag von Matt Roth
Gesendet: Dienstag, 27. September 2005 17:31
An: [e-mail]
Betreff: Re: NFS Mount over a Specific Interface

Apologies for the repost, but I flubbed the subject the first time...

Thank you for the response.

I should have been more specific in my original post.  The multiple NICs 
are on the NFS client.

One NIC on the NFS client will be receiving HEAVY VoIP traffic and I 
want any NFS traffic to be offloaded to a separate NIC on the client, as 
shown:
           ________           ________
         _|        |_        |        |
        |e|        |e|       |        |
  VoIP  |t|   NFS  |t|  NFS  |  NFS   |
--------|h| Client |h|-------| Server |
        |0|        |1|       |        |
         -|________|-        |________|

I'm looking for a way to tell the mount command on the NFS client which 
interface to use.  It defaults to the first active interface.  I can 
easily swap interfaces and IPs around in the box to meet my goal, but I 
was looking for a more flexible solution.

I've read the pertinent man pages and the NFS section in my network 
administration guide but they make no mention of this.  We are currently 
using NFS version 3.

Thank you,

Matthew Roth
InterMedia Marketing Solutions
Software Engineer and Systems Developer
> > I have a NIC that I would like to dedicate to an NFS mount.  After much 
> > reading, I can't find any mount options that let me specify the 
> > interface.  Mount seems to only want to use the first active NIC on the 
> > system.
> >
> > If anyone knows how to do this, I'd greatly appreciate your help.
> >
> > Thank you,
> >
> > Matthew Roth
> > InterMedia Marketing Solutions
> > Software Engineer and Systems Developer
>
> From what I can tell is you want an nfs client to attach to a certain
> nfs server interfaces. If you have the appropriate dns/host record's you
> should be able to make this happen.
>
> server01.domain.com 1.1.1.1/24
> server01-eth1.domaincom 1.1.2.1/24
>
> client.domain.com 1.1.1.2/24
> client-eth1.domain.com 1.1.1.2/24
>
> On client.domain.com
> mount server01-eth1.domain.com/exports /imports
>
> Common mistake most people tend to do is over look impact of the routing
> involved. If the client does not share a broadcast domain with the
> server, you are just going to create a heap of ____.
>
> Provide some details about your network topology with client and server
> shown for a better response.
>
> Regards,
> Ted

NFS Mount over a Specific Interface

[Nigel Wade]

Matt Roth wrote:
> Apologies for the repost, but I flubbed the subject the first time...
>
> Thank you for the response.
>
> I should have been more specific in my original post.  The multiple NICs 
> are on the NFS client.
>
> One NIC on the NFS client will be receiving HEAVY VoIP traffic and I 
> want any NFS traffic to be offloaded to a separate NIC on the client, as 
> shown:
>           ________           ________
>         _|        |_        |        |
>        |e|        |e|       |        |
>  VoIP  |t|   NFS  |t|  NFS  |  NFS   |
> --------|h| Client |h|-------| Server |
>        |0|        |1|       |        |
>         -|________|-        |________|
>
> I'm looking for a way to tell the mount command on the NFS client which 
> interface to use.  It defaults to the first active interface.  I can 
> easily swap interfaces and IPs around in the box to meet my goal, but I 
> was looking for a more flexible solution.

You can't tell mount anything about interfaces. NFS uses IP to transmit 
data, it's up to the OS to determine how that data gets routed via network 
interfaces.

eth0 and eth1 need to be on different networks. The NFS server needs to be 
on the same network as eth1. All you need to do then is setup appropriate 
routing information for the two networks so traffic for each goes via the 
appropriate interface, and that will take care of it.