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

What we are going to deploy today is NLB. What is NLB? To put it bluntly, it is the high availability of the client access role. Load balancing is a way to manage which servers receive traffic. Load balancing helps distribute incoming client connections through endpoints, such as client access servers, to ensure that no endpoint bears a disproportionate share. Load balancing can also provide failover redundancy when one or more endpoints fail. By using load balancing in Exchange Server 2013, you can ensure that users can continue to receive Exchange services in the event of computer failure. Load balancing also enables your deployment to handle more traffic than a single server can handle, while providing a single hostname for the client.

Please refer to the following link for details:

Https://technet.microsoft.com/ZH-CN/library/jj898588(v=exchg.150).aspx

All right, needless to say, let's start today's deployment trip.

Before installing and deploying the network load balancer, we first add an A record to the DNS server, which is mainly used for the NLB configured by the CAS server. Its name and IP are unique. Open the DNS server, click manage in the server manager interface, and select DNS

Expand the forward search area, navigate to the domain name, and right-click to create a new A record

Enter the name and IP, and click add Host

Add completed

Open the client access role and install the network load balancer role (here is an example of ExchCas01). Open Server Manager, click manage, and select add roles or functions

Next step

Keep the default, next step

Select the target server

By default, click next.

Select the network load balancing function, next step

Click install

Installation is complete, click close

Open the network load balancing manager in the tool

Right-click to select New Cluster

Enter the local IP address in the host, and then click Connect, interface IP. We choose to manage the network card.

Keep the default, click next

Click add, then enter the IP we created in DNS, and click OK

Enter the Internet name, FQDN, and click next

Click finish

Then we add another CAS server to the cluster

Connect to the host, select the management network card, and click next

Keep the default, next step

Click finish

Configuration completed successfully

Open the web page and try to enter https://exchnlb.windows.com/ecp to access it

Enter the account number to test the login. Login is successful.

Then we use the FQDN of the CAS server to open ECP, which can also be opened.

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.