Re: cdot NFS exports

Is there a way to avoid 0.0.0.0 ro is defult policy rule

On Nov 11, 2014, at 10:12 PM, "Parisi, Justin" Justin.Parisi@netapp.com wrote:

TR-4067 covers all of these questions.

http://www.netapp.com/us/media/tr-4067.pdf

Exports are covered starting on page 21.

From: Iluhes iluhes@yahoo.com Reply-To: Iluhes iluhes@yahoo.com Date: Tuesday, November 11, 2014 at 9:51 PM To: "Toasters@teaparty.net" Toasters@teaparty.net Subject: cdot NFS exports

Hi toasters, NFS export in CDOT (ouch) I understand I have to have a default policy and a rule..

1. Must it have 0.0.0.0/0 read only? What if I dont want to give read-only to entire name space to all clients?
2. Qtrree exports: can I restrict qtree A to host A, and qtree B to host B, but then what about volume and it is policy? Can qtree be more restrictive than volume (and why dont qtree show up in GUI?)
3. Does showmount -e LIF of NFS filer still produce good information. It does not look like, so how do I check what my exports are?
4. What does it buy me with qtree exports, what? If I have to give access to server A and B to volume that has qtree A and B