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
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi,
i have problems with the sdk and ipv6.
into NaServer there is a perl call gethostbyname(), this will fail because it supports only ipv4.
is there a release with ipv6 support planned? when will it released?
has someone solved it already? how?
thank you!
regards
Christian
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
As of now, it’s only the Perl language that does not have any support for IPv6 address. We plan to fix this in the upcoming release (NMSDK 5.1).
NMSDK already supports IPv6 for C/C++ language from NMSDK (previously known as Manage ONTAP) 3.5 release onwards.
For Java, Python and Ruby, NMSDK uses native socket APIs which are already IPv6 compliant and is automatic and transparent. In other words, NMSDK supports IPv6 for these languages as well.
.NET APIs are not fully IPv6 compliant. The client application that uses NMSDK must specify the literal IPv6 address enclosed in square brackets (e.g.: http://[2001:db8::a00:20ff:fea7:ccea]:8080).
In the upcoming release (NMSDK 5.1), we plan to remove this restriction of having brackets for .NET and to make the usage uniform across all the languages.
Hope that helped.
Thank you
Best Regards
Aashray Arora
Technical Marketing Engineer (TME) NetApp Manageability SDK
2 REPLIES 2
migration has accepted the solution
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
As of now, it’s only the Perl language that does not have any support for IPv6 address. We plan to fix this in the upcoming release (NMSDK 5.1).
NMSDK already supports IPv6 for C/C++ language from NMSDK (previously known as Manage ONTAP) 3.5 release onwards.
For Java, Python and Ruby, NMSDK uses native socket APIs which are already IPv6 compliant and is automatic and transparent. In other words, NMSDK supports IPv6 for these languages as well.
.NET APIs are not fully IPv6 compliant. The client application that uses NMSDK must specify the literal IPv6 address enclosed in square brackets (e.g.: http://[2001:db8::a00:20ff:fea7:ccea]:8080).
In the upcoming release (NMSDK 5.1), we plan to remove this restriction of having brackets for .NET and to make the usage uniform across all the languages.
Hope that helped.
Thank you
Best Regards
Aashray Arora
Technical Marketing Engineer (TME) NetApp Manageability SDK
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Just to add, you can expect NMSDK 5.1 release within the month of Feb. It should solve your issues.
-Kunal
