Highlighted
Absent Member.
Absent Member.
888 views

NFS mount not visible during Filr1.1 installation

Hi,

I have a problem with the NFS mount during the configuration. I have the following servers:

1 NFS server in the LAN (172.16.0.201) with the following definition in the exports file: /vashare *(rw,no_root_squash,sync,no_subtree_check)

1 FILR appliance in the DMZ (192.168.0.51) I want to install


At the point of configuring shared storage, the appliance doesn't see any remote directory on this NFS server (172.16.0.201), but can see the directory on another NFS server (172.16.0.20)
(exports file on 172.16.0.20: /vashare *(rw,no_root_squash,sync,no_subtree_check))

I have an old 1.01 appliance (DMZ: 192.168.0.171) and this one can mount the NFS volume of the new NFS Server (172.16.0.201):

slesnfs.bbz-biel.ch:/vashare on /test type nfs4 (rw,relatime,vers=4,rsize=524288,wsize=524288,namlen=255,hard,proto=tcp,port=0,timeo=600,retrans=2,sec=sys,clientaddr=192.168.0.171,minorversion=0,local_lock=none,addr=172.16.0.201)

Both NFS Servers are on SLES11 SP3 and have NFS V4, no server firewall active.

The firewall ports are OK as I can mount the volumes on the old server.


I don't understand why the old FILR appliance can mount the volume form the new NFS server, and the new appliance not from the new one but from the old one.

Do I have to change the configuration for the volume on the new NFS?

I'm really stuck on this as I can't continue with the installation.

Bernard
0 Likes
2 Replies
Absent Member.
Absent Member.

Re: NFS mount not visible during Filr1.1 installation

I'm responding from an NFS viewpoint... I know very little about FILR appliances or the install process you're referring to. But here's various ideas:

1. NFS server code requires that before a mount request is approved, the NFS Server must be able to turn the client's IP address into a name. If the OLD nfs server does that reverse-name-resolution for a certain client IP successfully, but the NEW nfs server does not do it, that could explain the difference. You could check /etc/hosts contents and "nslookup <client-ip>" from the nfs server console, and see if it is able to do this.

2. I notice that your 2 IP addresses (for new and old NFS server) are quite similar. They are identical except for the final octet, which is 201 vs 20. This seems like a prime area for typos. Maybe an IP address is entered incorrectly somewhere. Maybe in some places you are using names, but a hosts file or dns record has been mistyped at some point? It doesn't seem likely, but there's reasonable doubt here.

3. I'm not 100% certain what is really failing here. The most precise terminology you used indicated that some things can mount and some things cannot. In other places, you merely said, 'doesn't see', which could mean other things (like mount was okay, but file access was not). Can you clarify that? And how confidently? For example, is this a situation where you can go to a shell and manually issue a mount command, and see what happens? Does it give a specific error? Does the error come immediately, or only after a delay or timeout? If we can more specifically isolate the point of failure / nature of failure, I might have additional suggestions.

Darcy
0 Likes
Highlighted
Absent Member.
Absent Member.

Re: NFS mount not visible during Filr1.1 installation

I had a workaround for the problem. I simply used the old NFS server for the installation, then copy the data to the new NFS. Changed the mount from the old to the new NFS and everything works now perfectly.

I didn't change any IP or servername. So I'm pretty sure it is a FILR bug during the initial installation.

But thanks anyway for you response.

Bernard
0 Likes
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.