Known Issues

This page describes issues with the NetApp Manageability SDK that are known at the time of publishing this page.

 

Problem: Bad host name error when IPv6 address is entered in Ruby 2.0.

Cause:  The built-in libraries in Ruby 2.0 do not support IPv6.

Workaround: Enter the IPv6 address within square brackets ([]).

 

Problem: IPv6 is not supported on some versions of Perl.

Cause: IPv6 is not supported by default (in Socket module).

Workaround: Use the in-built Socket module routines. If the Socket module routines are not available, install Socket6 module.

 

Problem: If the debug style is set to NA_PRINT_DONT_PARSE or NA_DONT_PRINT_DONT_PARSE by using the API na_server_set_debugstyle, an error message is added to the API response. The error message is "debugging bypassed xml parsing", and the error number is 13001.

 

Problem: Sample codes and utilities in C fail in Windows Debug mode with the following error message: "The system cannot execute the specified program."

Cause: The debug runtime libraries of Microsoft Visual Studio 2005 SP1 8.0.50727.762 are not installed in the system.

Workaround: You must install the debug runtime libraries of Microsoft Visual Studio 2005 SP1 8.0.50727.762.

 

Problem: On Data ONTAP, when SSLv2 is disabled, and either SSLv3 or TLSv1 is enabled, API communication fails. This is a known issue in Data ONTAP in C, Perl, Python (except 3.2.x), Ruby (except 1.9.2), and Java.

Workaround: Enable both SSLv3 and TLSv1 in Data ONTAP.

Note: This workaround does not apply to Data ONTAP 8.0.x because TLSv1 is not supported in this version.

 

Problem: Certificate-based authentication is supported only on the following Python versions:

·         Python 2.6.6 and later

·         Python 2.7.3 and later

·         Python 3.1.3 and later

·         Python 3.2 and later

·         Python 3.3.0 and later

  

Problem: In the Mozilla and Firefox browsers, the first click on a search keyword takes you to a topic that is listed above the destination topic.

Cause: This is a browser-specific issue.

Workaround: Keep clicking the search keyword till you reach the destination topic, where the search keywords are highlighted.

 

Problem: Microsoft .NET core API documentation does not open.

Cause: This occurs because of the security settings of the browser.

Workaround: Open the DotNet.chm file or open the Properties tab of the browser, and select the unblock option.

 

Problem: Compilation of DataFabric Manager DotNet Web Services sample codes fail in Microsoft Visual Studio 2010.

Cause: This issue occurs because Microsoft Visual Studio 2010 adds the tag <TargetFrameworkVersion>v2.0</TargetFrameworkVersion> in the .csproj file. However, Microsoft Visual Studio 2010 supports only .NET Framework v4.0. Therefore, the compilation fails.

Workaround:

  1. Load the sample code solution (.sln) or project (.csproj) in Microsoft Visual Studio 2010.
  2. Perform one of the following steps:

 

Problem: After disabling bindings validation, some of the Perl API bindings invocation return outputs that violate the type definitions specified in API Bindings Documentation by containing some fields as hash references instead of predefined array references. This is applicable only if the array field contains only one child element in the output.

For example:

When NaServer::vserver_get_iter() is invoked on a clustered Data ONTAP system and the output contains only one vserver, the 'vserver-info' field (child of 'attributes-list' field in the output) is displayed as a hash reference instead of an array reference.

Cause: When API bindings validation is disabled, the output hash is formed directly from the XML response of the server without referring to the API Bindings definitions. Thus, when an output field contains only one child element field, the output field is considered as hash reference because it cannot be differentiated from an array of single element without referring to the API Bindings Documentation.

Workaround: Perform one of the following steps:

For example:

 


Related Information