Bind Client/Server with a Dedicated IP

Note

This feature is only available in NCache Enterprise Edition.

A specific client/server can be bound with a dedicated IP address in the following way:

Using NCache Web Manager

  • Launch NCache Web Manager by browsing to http://localhost:8251 (Windows) or <server-ip>:8251 (Windows + Linux).

  • In the left navigation bar, click on Clustered Caches or Local Caches, based on the cache to configure. Against the cache name, click on View Details.

View Details Web

  • This opens up the detailed configuration page for the cache.

  • Under Server Nodes tab, check the box against the server node IP to change NIC.

    • Method 1: Click on the Change NIC Button Web button on the toolbar to change NIC.

      Server Node Toolbar

    • Method 2: Click on "..." against the server IP and select Change NIC.

      Server node started web

  • Configure NIC dialog will open. It will list all network cards available on that node with their assigned IP addresses.

  • Select the Client/Server option from drop down in front of the IP with which you want to bind the client and server.

Bind Client Server NIC Web

  • Click OK.

Troubleshooting

If you have dedicated network cards configured for public and private communication, then you might not be able to create new clusters or possibly existing NCache cluster could not communicate with others. Please note, the following problems will occur if nodes are unable to communicate with each other on specific interface(s).

NCache Service starts at one interface whereas other nodes try to communicate with it on the other interface. Therefore the two nodes are always unable to communicate with each other even when apparently both nodes are fully functional.

NCache Clients connect to NCache Server to get OutProc cache instances. So, it is possible that NCache Server starts at one interface whereas the client tries to connect to it on the other interface. This way, though NCache Server is ready to accept the client requests, client applications will always be unable to connect to the OutProc caches.

Situations can arise where cluster nodes are unable to join with each other and no cluster is forming. The reason could be that one node is listening join requests from other nodes on one network interface whereas other nodes send join requests on other network interface.

Workaround

To avoid such problems, you can bind NCache service to specific IP that is publicly available to other nodes in the cluster.

<add key = "NCacheServer.BindToClientServerIP" value = "<your-ip>" />

See Also

Bind Cluster with a Dedicated IP
Email Notifications
Heartbeat
Communication Reliability