Originally posted by: SystemAdmin

I followed the pattern of exports file in the IBM lib doc. However, it seems that I can not combine multiple options as option http://, optins... I have tried followoing patterns, one entry in each attemp:
/filesystem/subdir -rw, access=client1, sec=dh
/filesystem/subdir -access=client1, rw
/filesystem/subdir -sec=dh, rw
and run the exportfs -av, but all return with "1831-190 unknown option:". I trid
/filesystem/subdir -rw, sec=dh
and I got :security flavor must be specified before option: rw
The only thing worked was to enter one option. So what is the correct way?
#AIX-Forum

Originally posted by: orphy

If you are messing with /etc/exports manually, I suggest using
"smitty mknfsexp" instead. It should be easier for you. I vi the file
myself sometimes but a lot of times, it's better to use smit to
do the job.
Orphy
#AIX-Forum

Originally posted by: SystemAdmin

OK, I found the trick of it. the option list will not allow to have space between options. Ex. "-sec=dh,access=client1,rw" works, but if -sec=dh, access=client1, rw", the OS said "unknow option".

I went to smitty mknfsexp, but I still do not quite understand how to use those security levels and about the NSF 2,3 or 4.

At this moment, I may stay with scripting level. Maybe later, I will use the smitty.
#AIX-Forum

Originally posted by: SystemAdmin

I also found out that when creating the exports file, do not include the sec=dh; otherwise, the client side will not allow to mknfsmnt with error of "vmount: There is an input or output error.
NFS fsinfo failed for server baanbk: error 7 (RPC: 1832-010 Authentication error)", unless there are some extra option which I have not figure yet.
#AIX-Forum

Originally posted by: orphy

I know you mention about using smitty later but the good thing about smitty
is that it will not allow you to mess up /etc/exports. Also, unless you
really care about all those NFS security features, you might want to just
consider setting up a simple NFS server-client relationship and go from there.
Then again, I don't know your business requirements and I hope that you are
heading the right direction.
Orphy
#AIX-Forum

Originally posted by: SystemAdmin

Well. Apparently, that´s a good recommendation. I just run into a problem. Currently I am testing the NFS between a RHEL3 (server) and a Dev AIX (client). When I tried to reboot the RHEL and checked whether the reboot would affect the server´s (RHEL) exports file in its kernel, and subsequently affected the mounting of the NFS on the client. Guess what, there was a problem of the RH when it rebooted, the exports was not there, and so when I rebooted the AIX, it could not find the server, so it was stucked in the booting process, and trying to mount that remote drive on RH. Even I rebooted the RH second time and the original exports file appeared again ( I did not do "exportfs -a"), my AIX client box is still trying to mount NFS and hung.. So how can I resolve the problem of the reboot of AIX? (more urgent)
should I take out the -A in my mknfsmnt command in the future?
#AIX-Forum

Originally posted by: orphy

-A is not the problem though not using it will fix your problem here.
The really problem is that you have the default "hard" mount in place and
thus AIX will keep trying to mount until Linux responses. You can try using
"soft" mount (-S).
Orphy
#AIX-Forum

Originally posted by: SystemAdmin

My urgent problem is the reboot process hung at trying to mount that NFS. Even i have corrected exports on the server side and exportfs correctly, the reboot of the AIX was still hung (after few power-off/on). How can I go in AIX system and correct the mounting fs problem?
#AIX-Forum

Originally posted by: orphy

http://www-1.ibm.com/support/docview.wss?rs=0&q1=AIX+recovery+from+LED&uid=isg3T1000131&loc=en_US&cs=utf-8&cc=us&lang=en

You need to go to Maintenance Mode, mount /dev/hd4, and edit/comment out the NFS
stanza in /etc/filesystems (or specify a soft mount instead).

Not every step in the above URL is needed for your case so go through the
URL carefully.
Orphy
#AIX-Forum

Originally posted by: SystemAdmin

I have solved the problem. It turn out that I did not start the NFS service from the server side (RH) after reboot that machine. As long as I did "service nfs start", even the clinet, AIX, still gave up on the NFS, at least it finished the NFS and continued the reboot. So after the reboot, I did "rmnfsmnt" to remove the nfs entry in filesystems.

But your information is so valuable. Actually it revealed another problem on this AIX box, which my DVD won´t read the CD. I need to find out why.
#AIX-Forum

Originally posted by: orphy

Let's hope that you have a bad CD for that would make it a lot easier for you.
Try reading the CD on your PC or something to make sure it's ok. I take that
you actually created a cdrfs on AIX and mounted it properly?
Orphy
#AIX-Forum

Originally posted by: SystemAdmin

Thanks so much and patiently to guide me through. Because I was not a SA and it just happened that the Oracle is sitted on this box, and No one in this office understand about the AIX either. So for my Oracle works, I have to learn all necessary things.
Certainly I will check the CD.
Just tried the mknfsmnt with -S option. However, the NFS will not be mounted after reboot. so I have to figure out something later. Hope next week, I will learn something new. (I am in Mexico as a volunteer and the Mexican do not work on weekend except emergency).
#AIX-Forum

Originally posted by: orphy

I know you mention about using smitty later but the good thing about smitty
is that it will not allow you to mess up /etc/exports. Also, unless you
really care about all those NFS security features, you might want to just
consider setting up a simple NFS server-client relationship and go from there.
Then again, I don't know your business requirement and I hope that you are
heading the right direction.
Orphy
#AIX-Forum