You can run "exportfs" without any options to verify that your export is loaded correctly. If it's in the /etc/exports file but not loaded, you might need to "exportfs -a" or "exportfs -r" to reexport it. From there you can check the access cache with "exportfs -c" or flush it with "exportfs -f".
The next thing to check on the controller is that your client is reachable & resolvable. Assuming you have pings enabled on your network you can "ping -s hostname" from the NetApp controller. I'd check both the hostname and ip address.
Past that, you'll probably need to look at your client.
Here's a link to the ifconfig man page for ontap: http://ecserv1.uwaterloo.ca/netapp/man/man1/na_ifconfig.1.html
Here's one for the cifs commands: http://ecserv1.uwaterloo.ca/netapp/man/man1/na_cifs.1.html
changing your IP would be something like this (you would want to do this when logged in from the console in case it's not obvious):
# Get the name of the interface your current IP is assigned to, as well as
# netmask, etc
ifconfig -a
# down the interface (i'm not actually sure if this is needed)
ifconfig INTERFACE down
# bring the interface back up with the new network info (substituting the
# correct values for INTERFACE, NETMASK, and ADDRESS)
ifconfig INTERFACE ADDRESS netmask NETMASK ip
You might also have to edit some files in the filer's etc/ dir to make the change persist across a reboot, as I said it's been a long time. cd to the filer's etc and grep for the current IP to get an idea.
as for renaming the share... Looks like you can't do a straight rename, you're in for deleting the old one and recreating it with the new name. How about something like this:
# show the info about the current shares:
cifs shares
# change the share name
cifs shares -delete OLDSHARE
# add the new name with the same settings as the old
cifs shares -add NEWNAME [options]
See the na_cifs_shares man page for more infor on the options when you recreate the share (http://ecserv1.uwaterloo.ca/netapp/man/man1/na_cifs_shares.1.html)
Hope that helps somewhat...
Best Answer
Assuming I'm understanding what you're asking correctly:
The short answer is "No". The longer answer is "You don't need it".
NetApp filers cache NFS writes to NVRAM and acknowledge them to the host immediately, using that NVRAM to assemble full stripe writes and make good use of the Write Anywhere File Layout (WAFL).
What this means though, is that you're effectively doing
asyncalready - a write is deemed 'complete' as soon as it's committed in NVRAM, and the filer will handle destaging behind the scenes. (The NVRAM is battery backed in order to avoid potential data loss in a power outage).