Shulou(Shulou.com)06/03 Report--

Today's deployment of the Exchange 2013 front-end NLB is highly available, and load balancing is a way to manage which servers receive traffic.

Load balancing can provide failover balance in the event of a failure of one or more servers, ensuring that users are on the computer.

You can continue to receive Exchange services in the event of a failure, and load balancing also enables your deployment to handle more than a server.

Handle more traffic while providing a single hostname for the client.

Server inventory

DC01 (abcd.com)

192.168.131.133 main domain control, DNS server Exchange-01 (Cas client, Mbx server) 192.168.131.137 first exchange-01Exchange-02 (Cas client, Mbx server) 192.168.131.138 second exchange-01

NLB (no server) 192.168.131.150DNS domain name resolution can now add an A record to the DNS server, which is mainly used for NLB configured by the CAS service, whose name and ip are unique. First open the domain control DC01 to set dns

Open the exchange01 server, the cas client, to install the nlb service

After the installation is complete, open the network load balancing manager in the tool

Start to establish NLB network load balancing

Now the first Exchange01 server-side NLB has been built, and the second Exchange02 has also installed the network load balancing tool.

The operation steps can be followed by step 5.

Now go back to Exchange01's server and add the second Exchange02 CAS to the cluster

Now you can try to open the web page https://exchangenlb.abcd.com/ecp to access it.

At this point, the Exchange 2013 NLB is deployed successfully.

Note: I use multicast in cluster mode here. To use unicast, you need to turn on MAC address spoofing. The following are the differences between the three modes of operation of the NLB cluster:

Unicast

On each cluster member, NLB overrides the MAC address provided by the manufacturer on the network adapter. NLB uses the same unicast MAC address for all members. The advantage of this mode is that it works seamlessly with most routers and switches. The disadvantage is that traffic to the cluster spreads to all ports on the switch virtual LAN (VLAN), and communication between hosts cannot be bound through the adapter to which the NLB is bound.

Multicasting

NLB leaves the original MAC address unchanged, but adds a layer 2 multicast MAC address to the network adapter. All inbound traffic will reach this multicast MAC address. The advantage is that this approach allows inbound traffic to reach only hosts in the cluster by creating static entries in the content addressable memory (CAM) table of the switch. Of course, this approach also has drawbacks because the CAM entry must be statically associated with a set of switch ports. Without these CAM entries, inbound traffic will still spread to all ports on switch VLAN. Another disadvantage is that many routers do not automatically associate a unicast IP address (the virtual IP address of the cluster) with a multicast MAC address. If configured statically, some routers can have this association.

IGMP Multicast

Just like the multicast mode, NLB leaves the original MAC address unchanged, but adds an IGMP multicast address to the network adapter. In addition, the NLB host sends out an IGMP join message for this group. If the switch detects these messages, it can populate its CAM table with the required multicast addresses so that inbound traffic does not spread to all ports on the VLAN. This is the main advantage of this clustering model. The disadvantage is that some switches do not support IGMP probe. In addition, routers still support the translation of unicast IP addresses to multicast MAC addresses.

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.