gsalcedo
asked on
How do create a NFS volume on a NetApp and then mount it to a Solaris server?
I have a Solaris server that I would like to create an external storage because of disc space. As an external storage we have a NetApp filer. How do I create a NFS vol and then mount it to our Solaris server?
You didn't say which NetApp you were using. This is a general overview covering even the older stuff.
Log into the admin web interface <your IP>/na_admin
click on FILER VIEW (authenticate the control panel)
Go to VOLUMES > QTREES > ADD , pick a name for the share directory, follow the wizard
then go to NFS > ADD and follow the wizard to create the share for the qtree. Be sure to set the IP that can access the NFS share or everyone will have access.
If you want to run it loose you can set the anonymous ID to ' 0 ' (zero) in stead of 64500. This will make the anyone able to access the share be able to do whatever they want. Permissions will still be enforced by the mounting client machine so it's ok.
On your Solaris machines just setup your NFS mount like normal to the IP address of the NetApp filer.
Since you're asking the question here I'm guessing you either have 2nd market equipment or at the very least you don't have a N.O.W. contract with NetApp. After you get this setup you should really get someone on standby who can maintenance this stuff since you should be looking at the system weekly to ensure long life and proper operation.
Log into the admin web interface <your IP>/na_admin
click on FILER VIEW (authenticate the control panel)
Go to VOLUMES > QTREES > ADD , pick a name for the share directory, follow the wizard
then go to NFS > ADD and follow the wizard to create the share for the qtree. Be sure to set the IP that can access the NFS share or everyone will have access.
If you want to run it loose you can set the anonymous ID to ' 0 ' (zero) in stead of 64500. This will make the anyone able to access the share be able to do whatever they want. Permissions will still be enforced by the mounting client machine so it's ok.
On your Solaris machines just setup your NFS mount like normal to the IP address of the NetApp filer.
Since you're asking the question here I'm guessing you either have 2nd market equipment or at the very least you don't have a N.O.W. contract with NetApp. After you get this setup you should really get someone on standby who can maintenance this stuff since you should be looking at the system weekly to ensure long life and proper operation.
Also iSCSI and fiber doesn't have anything to do with each other. iSCSI is just the protocol, like NFS. You should always have at least a 1gig connection from the switch to the NetApp.
ASKER
Hi razorwoods,
I appreciate your help. While at "Qtrees," do you have any recommendation as to what volume (vol0, vol1, or vol2) that I should work with. I notice that vol0 is "checked" as root. Is it alright to use that volume? In the process of doing the NFS add, I noticed that there are 6 selections (Actual Path, Anonymous User ID, Read-Only Access, Read-Write Access, Root Access and Security) for the "Export Options." Do you have any recommendation for those selection(s)? Finally, the "Export Path." When I attempted to indicate the path of the Qtree that I just recently indicated, it would not proceed after clicking the "Next" button. If my Qtree is /vol/vol0/share, would the Export Path be /vol/vol0/share?
Thank you.
I appreciate your help. While at "Qtrees," do you have any recommendation as to what volume (vol0, vol1, or vol2) that I should work with. I notice that vol0 is "checked" as root. Is it alright to use that volume? In the process of doing the NFS add, I noticed that there are 6 selections (Actual Path, Anonymous User ID, Read-Only Access, Read-Write Access, Root Access and Security) for the "Export Options." Do you have any recommendation for those selection(s)? Finally, the "Export Path." When I attempted to indicate the path of the Qtree that I just recently indicated, it would not proceed after clicking the "Next" button. If my Qtree is /vol/vol0/share, would the Export Path be /vol/vol0/share?
Thank you.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Hi razorwoods,
Thank you very much for the great information. Your explanation is understandable.
Here is my update. I am able to add a Qtree and export, export the NFS and mount that remote volume to my Solaris server (mount -F filer:/vol/vol0/share /share). The only issue that I am facing now is whenever I have to reboot and power on the Solaris system, I will have to run the mount command. I have tried to edit the "vfstab" file, but for some reason, it is not mounting after it completes the boot up. Please see below of my input in the "vfstab" file.
#Device to mount Device to fsck Mount point FS type fsck pass mount at boot mount option
filer:/vol/vol0/share - /share nfs - yes rw,soft
Thank you very much for the great information. Your explanation is understandable.
Here is my update. I am able to add a Qtree and export, export the NFS and mount that remote volume to my Solaris server (mount -F filer:/vol/vol0/share /share). The only issue that I am facing now is whenever I have to reboot and power on the Solaris system, I will have to run the mount command. I have tried to edit the "vfstab" file, but for some reason, it is not mounting after it completes the boot up. Please see below of my input in the "vfstab" file.
#Device to mount Device to fsck Mount point FS type fsck pass mount at boot mount option
filer:/vol/vol0/share - /share nfs - yes rw,soft
You have the settings right. Unless NFS, portmap, etc... are starting later in the boot and it's not physically able to access NFS services prior to engaging the vfstab.
It's an old hack , but you could always stick a manual mount command in the good old rc.local file. That would do the trick.
You also may want to consider getting a maintenance contract with someone like us for older NetApp filers. They're built like tanks, but when there's a problem... it's like fixing a tank too ;)
It's an old hack , but you could always stick a manual mount command in the good old rc.local file. That would do the trick.
You also may want to consider getting a maintenance contract with someone like us for older NetApp filers. They're built like tanks, but when there's a problem... it's like fixing a tank too ;)
ASKER