I just loaded NetApp System Manager 1.0 and received the following when logging on to my active/active fas2020:
"API invoked failed. The underlying connection was closed. An unexpected error occurred on a send. Received an unexpected EOF or 0 bytes from the transport stream. No corrective action was found in Error Details".
I believe you are using print_volume.pl sample code provided in SDK. To use this sample code you need not enable httpd.enable.
Since incorrect arguments have been passed to print_volume.pl mentioned failure is seen. I observed that you are using non-default ports for HTTP and HTTPS. Hence print_volume.pl sample code cannot be used directly. It requires small customization.
Please use apitest.pl. This can be used to invoke requests on customised ports.
Doesn't look like anyone has responded yet to this,,,,but I, too, am getting the same exact error when using the NetApp CIFS Analyzer software.
We have installed the software and discovered the filers just fine using our SNMP community string. But as soon as we attempt to click on any of the filers, it throws the error u detail exactly as you have experienced it. The CIFS Analyzer software doesn't appear to be very forthcoming in the way of any kind of troubleshooting in this area. There are no apparent errors in the Windows host event log that we are running from and the filer throws no errors either.....google is peculiar in its silence on the topic as well,,,,, not sure where to go on it at this point......