This follow up is for documentation purposes in the archive and to thank all
those who responded. It was a piece of each response that put the puzzle
together. Hence, all responses are important. Thanks
Success at last, a long haul on this one. Here's what I found were the
problems.
A parameter issue with the mount command, then another parameter issue.
Although I believe the main issue was with the exports file. I originally had
an ip address in the exports file then a dns name, I then realized we had
multiple paths out of the stack so I modified the exports file as below because
I did not know what path nfs was taking. Replacing the dns name and ip address
in the exports file with an * I think allowed the traffic to get to the server
which in turn led to the insecure port issue. I then added the insecure parm.
Below is the mvs mount command and the exports file that worked for initial
connectivity testing.
Exports file on Linux:
/home/matt *(ro,sync,insecure)
MVS mount command:
MOUNT FILESYSTEM('NFSTEST') TYPE(NFS) MODE(RD) +
MOUNTPOINT('/u/st1mat/test/') +
PARM('lntest1.li.pch.com:/home/matt,XLAT(Y),vers(3)')
Thanks again.
-----Original Message-----
From: Linux on 390 Port [mailto:[email protected]] On Behalf Of Mark Post
Sent: Monday, September 26, 2011 3:37 PM
To: [email protected]
Subject: Re: RH NFS Server
>>> On 9/26/2011 at 03:04 PM, "Dazzo, Matt" <[email protected]> wrote:
> I finally got some messages to the /var/log/messages file. What might these
> means? Thanks Matt
>
> Sep 26 14:54:35 lntest1 mountd[1264]: authenticated mount request from
> 27.1.39.74:1023 for /home/matt (/home/matt)
> Sep 26 14:54:35 lntest1 kernel: nfsd: request from insecure port
> (27.1.39.74:1062)!
> [root@lntest1 log]#
It means that the z/OS client initiated the mount request on outgoing port
1062. Since only root can open ports between 0-1023, those are called 'secure
ports" and anything else is referred to as "unprivileged" or "insecure" ports.
Some NFS server implementations don't like mount requests coming in on
unprivileged ports, since it means that some process that might not be running
as root has done that.
I don't recall if the z/OS NFS client can be made to only make requests on
secure ports or not. If not, then you'll have to tell your NFS server to
accept requests on unprivileged ports.
Mark Post
----------------------------------------------------------------------
For LINUX-390 subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
----------------------------------------------------------------------
For more information on Linux on System z, visit
http://wiki.linuxvm.org/
----------------------------------------------------------------------
For LINUX-390 subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
----------------------------------------------------------------------
For more information on Linux on System z, visit
http://wiki.linuxvm.org/
