Turn off TCP nagling for both internal and external ports 443. Hardware Load Balancer Requirements for Edge Servers Running the A/V Edge Serviceįollowing are the hardware load balancer requirements for Edge Servers running the A/V Edge service:
To determine whether your hardware load balancer supports the necessary features required by Skype for Business Server, see Infrastructure for Skype for Business. The direct server return (DSR) NAT is not supported with Skype for Business Server. If high availability is required for any of the following scenarios, a hardware load balancer must be used on Edge Server pools for the following:įederation with organizations using Office Communications Server 2007 R2 or Office Communications Server 2007Įxchange UM for remote users using Exchange UM prior to Exchange 2010 with SP1 The Skype for Business Server scaled consolidated Edge topology is optimized for DNS load balancing for new deployments federating primarily with other organizations using Skype for Business Server or Lync Server. You must remove the DNS entry for the computer as well. If you use DNS load balancing and you need to block traffic to a specific computer, it is not sufficient to just remove the IP address entries from the Pool FQDN. Administrators do not need to set up or manage this type of load balancing.
Servers read the published topology in the Central Management store to obtain the FQDNs of servers in the topology, and automatically distribute the traffic among the servers. For details, see DNS Load Balancing.įor server-to-server traffic, Skype for Business Server uses topology-aware load balancing. For example, configuring the hardware load balancer will be simpler as it will only manage the HTTP and HTTPS traffic, while all other protocols will be managed by DNS load balancing. If you choose to use DNS load balancing for a pool but still need to implement hardware load balancers for traffic such as HTTP traffic, the administration of the hardware load balancers is greatly simplified. DNS load balancing does not work with client-to-server web traffic. For example, HTTP traffic requires a hardware load balancer instead of DNS load balancing. Some types of traffic require a hardware load balancer. You cannot use DNS load balancing on one interface and hardware load balancing on the other. The internal Edge interface and external Edge interface must use the same type of load balancing. DNS load balancing offers several advantages including simpler administration, more efficient troubleshooting, and the ability to isolate much of your Skype for Business Server traffic from any potential hardware load balancer problems.ĭecide for yourself which load balancing solution is appropriate for each pool in your deployment, but keep in mind the following restrictions: Skype for Business Server supports two types of load balancing solutions for client-to-server traffic: Domain Name System (DNS) load balancing and hardware load balancing (often abbreviated as HLB). If you have Front End pools, Mediation Server pools, or Edge Server pools, you need to deploy load balancing for these pools. Load balancing distributes traffic among the servers in a pool.
Summary: Review the load balancing considerations before implementing Skype for Business Server.
0 kommentar(er)
