Re: Force NFS mount to a specific TCP/IP interface

Right now things are not working the way we think ("I do not think that word means what you think it means"). Setting the preferred interface for a .0 subnet seems to be doing exactly the opposite of what we expect, at least when we run TRCTCPRTE. I'm on another topic right now, but I'll get back after I read the Schowler info and get some more testing time.

Joe

Joe

Look up "Schowler route" and see if that can help you. It's and
i-specific thing, however. They do let you specify an interface to talk
to a specific IP address.

A presentation on Virtual IP -
http://www.ibm.com/developerworks/wikis/download/attachments/16253354/VirtualIP.pdf?version=1

General KB on them -
http://www-01.ibm.com/support/docview.wss?uid=nas1eb95209430bbcb7486256d170047484a

Looks as if there is a redbook, too, SG24-6718, that might help -
iSeries IP networks: Dynamic!

HTH
Vern

On 5/9/2011 11:01 AM, Joe Pluta wrote:

We've got multiple IP addresses configured on our IBM i. With SMTP,
it's relatively easy to configure which address to bind to. iSeries
Navigator lets you select which IP addresses to bind to right in the
SMTP server configuration page. Is there something similar to force an
NFS mount to a specific interface? This is when we're trying to use the
MOUNT command to access an external device's file system as an IBM i
folder, so I don't think the NFS server configuration is going to help
(and there's nothing there about binding anyway).

MOUNT seems to want to use the numerically lowest IP interface (SMTP did
the same thing until we reconfigured it). We can probably configure the
external device to accept requests from this address, but it would be
good to know if there's a better control mechanism.

Joe