When you recently configured SharePoint 2013 WFE, the customer mentioned that to allow multiple WFE to load balance, the next Network Load Balancing was studied.
When a server (including Web servers, FTP servers, or streaming media servers, etc.) is put into the network, as the number of clients increases, people often need more powerful and faster servers. To solve this problem, it is clearly not a laudable way to replace an existing server with a server that is more powerful and faster. But if the new server can be added to the processing power of the original server rather than replace it, this scenario is undoubtedly more acceptable to users. This is achieved by the advent of Network Load Balancing (Network load BALANCING,NLB) clusters.
Working principle:
Both Node A and Node B have an externally used static IP address. Creating an NLB cluster produces a virtual IP that is in the same network segment as the IP of the node, and the externally advertised IP as a virtual cluster IP, while the client accesses the actual node A or node B.
Configuration steps:
1. Set up static IP in Node A and Node B respectively:
2. Install NLB in Node A and Node B, respectively: