IPV6 Addresses Support

NCache supports IPV6 addresses, for both, cluster wide and client-server communication. All that the user needs to do is assign IPV6 addresses to tags BindToClusterIP and BindToClientServerIP in the cache server configuration file found in the NCache installation as follows:

How to Configure IPV6 Addresses Support in NCache

  • .NET: Alachisoft.NCache.Service.exe.config located in %NCHOME%\bin\service
  • .NET Core Windows: Alachisoft.NCache.Service.dll.config located in %NCHOME%\bin\service
  • .NET Core Linux: Alachisoft.NCache.Daemon.dll.config located in /opt/ncache/bin/service
  • Java Windows: Alachisoft.NCache.Service.dll.config located in %NCHOME%\bin\service
  • Java Linux: Alachisoft.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"/>

IPV6 Addresses Support Limitations in NCache

However, the only limitation at present is that cache statistics in the NCache Management Center cannot be fetched using IPV6. This is because the NCache Management Center 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 the hostname (server name) instead for fetching cache statistics if the NCache cluster is on IPV6.

Warning

In NCache Command Line tools where the server name or IPV6 address is required as an argument, it is recommended to use the IPV6 address instead of the server name. This is because using the server name might run the tool on such an IP address on the server where NCache Service is not running. This will result in an exception.

See Also

Monitor Caches using the NCache Monitor
Monitor Bridge
Monitor Caches using the NCache Management Center
Troubleshooting the NCache Monitoring