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 inbuilt 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, then 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: When SSLv2 is disabled and either SSLv3 or TLSv1 is enabled on ONTAP, the API communication fails. This is a known issue in ONTAP in C, Perl, Python (except 3.2.x), Ruby (except 1.9.2), and Java.
Workaround: Enable both SSLv3 and TLSv1 in 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:
Problem: In the Mozilla Firefox browser, 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 until you reach the destination topic, where the search keywords are highlighted.
Problem: Microsoft .NET core API documentation does not open.
Cause: This issue occurs because of the security settings in 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 fails in Microsoft Visual Studio 2010.
Cause: This issue occurs because Microsoft Visual Studio 2010 adds the tag
<TargetFrameworkVersion>v2.0
</TargetFrameworkVersion> to the
.csproj file. However, Microsoft Visual Studio 2010 supports only .NET Framework v4.0. Therefore, the compilation fails.
|
•
|
Change the value of the <TargetFrameworkVersion> field from v2.0 to v4.0 in the *.csproj file and compile the DataFabric Manager DotNet Web Services sample codes.
|
|
•
|
Remove the <TargetFrameworkVersion>v2.0 </TargetFrameworkVersion> field from the *.csproj file and compile the DataFabric Manager DotNet Web Services sample codes.
|
Problem: After disabling bindings validation, some of the Perl API bindings invocation return outputs that violate the type of 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.
When NaServer::vserver_get_iter() is invoked on an ONTAP system and the output contains only one
Storage Virtual Machine (SVM), the
vserver-info field (child of the
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 from 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 a 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:
|
1.
|
Enable API bindings validation using NaServer::set_bindings_validation(1). Set the correct server family using NaServer::set_bindings_family($family) before invoking such API bindings.
|
