External bridge and NFS problems

[Sally_H_]

Hi,

I've setup an external bridge for my MICs and they can see IPs on the same subnet that they are on (off the host that they're on).  Which is great news.

However, my NFS server is on a different subnet and the MICs have no routes and no way I can see of configuring them via micctrl.

Based on the idea that they should use the routes of the host RHEL OS, I tried to add an NFS share  (as on another thread on this forum I was told that we can add external NFS mounts if using external bridges).  unfortunately, it didn't work -- it seems like it assumes that the nfs share is on my host RHEL OS as it substitutes the IP for my host :-(

I've changed IPs, but otherwise, this is the output (10.10.10.21 is my guest RHEL, and my MICs are effectively 10.10.10.22 and .23, the NFS server is 10.10.20.74) - remember, I am using genuine, routable IPs, I just don't want to post them publically :-) ;

[root@host mic0]# micctrl --addnfs=10.10.20.74:/vol/myfiler/myshare --dir=/export/myshare
[Warning] Export directory '/vol/myfiler/myshare' does not currently exist
[root@host mic0]# more /var/mpss/mic0/etc/fstab
rootfs          /               auto            defaults                1  1
proc            /proc           proc            defaults                0  0
devpts          /dev/pts        devpts          mode=0620,gid=5         0  0
10.10.10.21:/vol/myfiler/myshare /export/myshare  nfs             nolock          1 1
[root@host mic0]#
 

Any ideas?

Thanks, Sally.

[Frances_R_Intel]

The problems with NFS mounts between networks is fixed in MPSS 3.2. The file list is no longer used for Linux, so any issues with NFS mounts messing around with file list are moot.