IP Binding Client/Server

A specific client or server can employ dedicated IP binding using the NCache Management Center as detailed below.

IP Binding: Using the NCache Management Center

  • Launch the NCache Management Center by browsing to http://localhost:8251 or <server-ip>:8251 on Windows and 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 the detailed configuration page for the cache.

  • Under the 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 choose to change the 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 the 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 Dedicated Client/Server IP Binding

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

The 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.

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

Situations can arise where the cluster nodes are unable to join with each other and no cluster forms. This could stem from one node listening to join requests from other nodes on one network interface, while the other nodes send these join requests on the other network interface.

Workaround

To avoid such problems, you can bind th NCache Service to a 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