Howdy all,
I have the following issue:
I've two filers "stuck" at ONTAP 7.0.4P9. Don't ask... they were put there before my time here, and now support 50,000 mailboxes that *never* go down....
I've inherited the following in my exports file which I cannot experiment with without risking downtime to our pool of mailhosts:
/vol/vol0 -sec=sys,rw=XXX.XX.XXX.XXX/25:admin-host.domain.edu,root=XXX.XX.XXX.XXX/25:admin-host.domain.edu,nosuid /vol/vol1 -sec=sys,rw=XXX.XX.XXX.XXX/25:admin-host.domain.edu,root=XXX.XX.XXX.XXX/25:admin-host.domain.edu,nosuid
Mount access is NOT granted to the admin-host in this configuration and I cannot find a reference to this issue on the NOW site. Was there issues similar to this in the exports file back in ONTAP 7.0.4 ? There seems to only be a reference to ONTAP 7.0.6 on the NOW site and at that a fair amount of "exports" issues but none specific to this issue that I found. Anybody seen this ?
Any help is much appreciated.
-Robert
On Tue, Feb 26, 2008 at 02:21:11PM -0600, Robert K. Borowicz wrote:
I've inherited the following in my exports file which I cannot experiment with without risking downtime to our pool of mailhosts:
No room to create another small volume and export that?
/vol/vol0 -sec=sys,rw=XXX.XX.XXX.XXX/25:admin-host.domain.edu,root=XXX.XX.XXX.XXX/25:admin-host.domain.edu,nosuid /vol/vol1 -sec=sys,rw=XXX.XX.XXX.XXX/25:admin-host.domain.edu,root=XXX.XX.XXX.XXX/25:admin-host.domain.edu,nosuid
Mount access is NOT granted to the admin-host in this configuration
Are you sure that the admin host's IP address reverse resolves to 'admin-host.domain.edu'? If it resolves to the short name 'admin-host', then it won't match.
Is admin-host in /vol/vol0/etc/hosts, or is it only resolved via DNS?
You can also use getXXbyYY with the IP of the admin-host to see how the filer will resolve it. That command lives in priv set advanced but is quite safe (I've never had a problem with it).
getXXbyYY gethostbyaddr_r ip_of_host
Just an extra trick..
-- Adam Fox adamfox@netapp.com
-----Original Message----- From: A Darren Dunham [mailto:ddunham@taos.com] Sent: Tuesday, February 26, 2008 4:04 PM To: toasters@mathworks.com Subject: Re: exports issue with 7.0.4P9
On Tue, Feb 26, 2008 at 02:21:11PM -0600, Robert K. Borowicz wrote:
I've inherited the following in my exports file which I cannot experiment with without risking downtime to our pool of mailhosts:
No room to create another small volume and export that?
/vol/vol0
-sec=sys,rw=XXX.XX.XXX.XXX/25:admin-host.domain.edu,root=XXX.XX.XXX.XXX/ 25:admin-host.domain.edu,nosuid
/vol/vol1 -sec=sys,rw=XXX.XX.XXX.XXX/25:admin-host.domain.edu,root=XXX.XX.XXX.XX X/25:admin-host.domain.edu,nosuid
Mount access is NOT granted to the admin-host in this configuration
Are you sure that the admin host's IP address reverse resolves to 'admin-host.domain.edu'? If it resolves to the short name 'admin-host', then it won't match.
Is admin-host in /vol/vol0/etc/hosts, or is it only resolved via DNS?
Darren,
Yeah there's a couple hundred gig free to create a test vol... Thanks.... I'll go there....
dns info is fine...
Pinging the admin host (elvis) yields this:
elvis ~ $ sudo rsh filer.domain.edu priv set advanced;ping elvis Warning: These advanced commands are potentially dangerous; use them only when directed to do so by Network Appliance personnel. elvis is alive
;-)
-Rob
A Darren Dunham wrote:
On Tue, Feb 26, 2008 at 02:21:11PM -0600, Robert K. Borowicz wrote:
I've inherited the following in my exports file which I cannot experiment with without risking downtime to our pool of mailhosts:
No room to create another small volume and export that?
/vol/vol0 -sec=sys,rw=XXX.XX.XXX.XXX/25:admin-host.domain.edu,root=XXX.XX.XXX.XXX/25:admin-host.domain.edu,nosuid /vol/vol1 -sec=sys,rw=XXX.XX.XXX.XXX/25:admin-host.domain.edu,root=XXX.XX.XXX.XXX/25:admin-host.domain.edu,nosuid
Mount access is NOT granted to the admin-host in this configuration
Are you sure that the admin host's IP address reverse resolves to 'admin-host.domain.edu'? If it resolves to the short name 'admin-host', then it won't match.
Is admin-host in /vol/vol0/etc/hosts, or is it only resolved via DNS?
On Tue, Feb 26, 2008 at 04:31:38PM -0600, Robert K. Borowicz wrote:
elvis ~ $ sudo rsh filer.domain.edu priv set advanced;ping elvis Warning: These advanced commands are potentially dangerous; use them only when directed to do so by Network Appliance personnel. elvis is alive
-sec=sys,rw=XXX.XX.XXX.XXX/25:admin-host.domain.edu,root=XXX.XX.XXX.XXX/25:admin-host.domain.edu,nosuid
"elvis" != "elvis.domain.edu".
Darren,
There's Joy in Mudville....
And thanks for the reminder, understood loud and clear that:
"elvis" != "elvis.domain.edu".
I was testing non-FQDN lookup/search order etc etc... Interestingly I found that:
filer FQDN = filer.domain-a.edu admin-host FQDN = admin-host.domain-b.edu
And:
domain-b.edu
Was not in the search list on the filer,
But DNS resolution worked, (imagine that) since the /etc/hosts file on the filer did NOT contain admin-host.domain-b.edu.
Cool.
I fixed this export issue with the command:
exportfs -r
And verified with the command:
exportfs -c <admin-host-IP> /vol/vol0
Which previously yielded:
exportfs: <admin-host-IP> does not have mount access to /vol/vol0
And of course now yields:
exportfs: <admin-host-IP> has mount access to /vol/vol0
Joy,
Thanks to all!
-Rob
A Darren Dunham wrote:
On Tue, Feb 26, 2008 at 04:31:38PM -0600, Robert K. Borowicz wrote:
elvis ~ $ sudo rsh filer.domain.edu priv set advanced;ping elvis
elvis is alive
-sec=sys,rw=XXX.XX.XXX.XXX/25:admin-host.domain.edu,root=XXX.XX.XXX.XXX/25:admin-host.domain.edu,nosuid
"elvis" != "elvis.domain.edu".
-
A Darren Dunham -
Fox, Adam -
Robert K. Borowicz