NCache supports IPV6 addresses for both cluster wide and client-server
communication. All that the user needs to do is assigning IPV6 addresses to tags
cache server configuration file found in NCache installation as follows:
- .NET: Alachsioft.NCache.Service.exe.config located in %NCHOME%/bin/service
- .NET Core Windows: Alachsioft.NCache.Service.dll.config located in %NCHOME%/bin/service
- .NET Core Linux: Alachsioft.NCache.Daemon.dll.config located in /opt/ncache/bin/service
Here's the xml code for that:
<add key="NCacheServer.BindToClusterIP" value="FE80::0202:B3FF:FE1E:8329"/> <add key="NCacheServer.BindToClientServerIP" value="FE80::0202:B3FF:FE1E:8329"/>
However, the only limitation at present is that cache statistics in NCache Manager cannot be fetched using IPV6. This is because NCache Web Manager employs a third party tool to fetch and show cache statistics using PerfMon. This tool, at the moment, does not support IPV6 addresses. Therefore, it is recommended to use host name (server name) instead for fetching cache statistics if NCache cluster is on IPV6.
In NCache Command Line tools where server name or IPV6 address is required as argument, it is recommended to use IPV6 address instead of server name. This is because using server name might run the tool on such an IP address on server where NCache service is not running. This wil result in an exception.