Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Mute
- Printer Friendly Page
Connect to vfiler with ONTAPI via HTTP/HTTPS, err=10061
2012-03-06
01:16 PM
8,988 Views
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi all,
WARNING: I'm not a programmer.
I'm using zexplorer to try and troubleshoot a problem with a program I'd like to use, but I'm seeing something odd when trying to connect to vfilers.
I have an active/active pair running ONTAP 8.0.2P3.
I have several vfilers running on each controller.
On controller 1, I can use an HTTP connection to any and all of the vfilers and get an appropriate response.
On controller 2, If I use an HTTP connection, I can connect with vfiler0 (the base unit), but not if I try to connect to any of the vfilers on that controller. I get the following error message.
<results reason="Can't connect to host (err=10061)." status="failed" errno="10061"/>
This is really odd because the physical filers are a cluster pair, built at the same time, running the same version of the OS, configured identically as far as I can tell, and the vfilers were built at the same time.
Any recommendations for figuring this one out?
Thanks in advance,
Brian
Solved! See The Solution
1 ACCEPTED SOLUTION
migration has accepted the solution
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi Brian -
Compare the HTTP options between the working vfilers and the non-working vfilers. Here is an example below.
toaster> vfiler run vfiler1 options http
===== vfiler1
httpd.access legacy
httpd.admin.access legacy
httpd.admin.enable on
httpd.admin.hostsequiv.enable off
httpd.admin.max_connections 512
httpd.admin.top-page.authentication on
httpd.autoindex.enable off
httpd.bypass_traverse_checking off
httpd.enable off
httpd.ipv6.enable off
httpd.log.format common
httpd.method.trace.enable off
httpd.rootdir XXX
I assume you have verified that the IP address are valid for the non-work vfilers by ping or rsh.
Regards,
- Rick -
3 REPLIES 3
migration has accepted the solution
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi Brian -
Compare the HTTP options between the working vfilers and the non-working vfilers. Here is an example below.
toaster> vfiler run vfiler1 options http
===== vfiler1
httpd.access legacy
httpd.admin.access legacy
httpd.admin.enable on
httpd.admin.hostsequiv.enable off
httpd.admin.max_connections 512
httpd.admin.top-page.authentication on
httpd.autoindex.enable off
httpd.bypass_traverse_checking off
httpd.enable off
httpd.ipv6.enable off
httpd.log.format common
httpd.method.trace.enable off
httpd.rootdir XXX
I assume you have verified that the IP address are valid for the non-work vfilers by ping or rsh.
Regards,
- Rick -
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Where's my soft rubber bat? I need to beat myself for not thinking of that!
Thanks Rick!!!!
Note: This is why I LOVE communities.netapp.com.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
great!!! you saved my day of getting really long :-). (SnapProtect with vFilers) I didn't know that it is not possible to change the httpd.admin.enable option from within the vfiler! man I feel stupid 🙂 regards Michel
