MS Lync Deployment Guide

Transcription

1 Deployment Guide UPDATED: 11 January 2018

2 Copyright Notices Copyright KEMP Technologies, Inc. All rights reserved. KEMP Technologies and the KEMP Technologies logo are registered trademarks of KEMP Technologies, Inc. KEMP Technologies, Inc. reserves all ownership rights for the LoadMaster and KEMP 360 product line including software and documentation. Used, under license, U.S. Patent Nos. 6,473,802, 6,374,300, 8,392,563, 8,103,770, 7,831,712, 7,606,912, 7,346,695, 7,287,084 and 6,970,933 Copyright KEMP Technologies, Inc. All Rights Reserved. 2

3 Table of Contents 1 Introduction Microsoft Lync Document Purpose Prerequisites 5 2 Load Balancing Microsoft Lync General Configuration Disable SNAT Globally Subnet Originating Requests Change Drop Connections Settings Increase the Connection Timeout Connection Scaling For Large Scale Deployments 12 4 Template DNS Only Configuration Lync Internal WebSvc HTTPS Virtual Service Lync Director 2013 DNS Virtual Service Lync Internal WebSvc HTTP Virtual Service HLB Only Configuration Lync Director 2013 HLB Virtual Service Lync Internal Director SIP Virtual Service Lync Mediation Virtual Service Lync Edge Internal AV Media TCP Virtual Service Lync Edge Internal AV Media UDP Virtual Service Lync Edge Internal SIP Virtual Service Lync Internal WebSvc HTTP Virtual Service 23 Copyright KEMP Technologies, Inc. All Rights Reserved. 3

4 5.2.8 Lync Internal Front-End DCOM Virtual Service Lync Internal WebSvc HTTPS Virtual Service Lync Internal Front-End SIP Virtual Service Configure Edge Virtual Services Lync Edge External AV Media UDP Virtual Service Lync Edge External SIP Virtual Service Lync Edge External SIP Federation Virtual Service Lync Edge External XMPP Virtual Service Lync Edge External Conferencing Virtual Service Lync Edge External AV Media TCP Virtual Service Common to Both Lync Office Web App Servers Virtual Service Lync Director Reverse Proxy HTTP Virtual Service Lync Director Reverse Proxy HTTPS Virtual Service Lync Front End Reverse Proxy HTTP Virtual Service Lync Front End Reverse Proxy HTTPS Virtual Service 35 6 Additional Information Server Maintenance Loss of Failover while using DNS Hardware Load Balancing 37 7 References 38 Last Updated Date 39 Copyright KEMP Technologies, Inc. All Rights Reserved. 4

5 1 Introduction 1 Introduction KEMP s LoadMaster family of purpose-built hardware and Virtual Appliances (VLM) offer advanced Layer 4 and Layer 7 server load balancing, content switching, SSL Acceleration and a multitude of other advanced Application Delivery and Optimization (ADC) features. KEMP s LoadMaster fully supports Microsoft s key solutions and are approved by Microsoft (KEMP is a Microsoft Gold partner). The LoadMaster efficiently distributes user traffic for Microsoft Lync 2013 so that users get the best experience possible. The entire KEMP LoadMaster product family, including the Virtual LoadMaster (VLM) supports Microsoft Lync For more information about KEMP Technologies, visit us online at Microsoft Lync 2013 Microsoft Lync is a communications tool which provides services such as audio/video conferencing, Instant Messaging (IM) and Voice over Internet Protocol (VoIP). These services can all be accessible from the Internet, or from an internal network. Microsoft Lync allows companies to enhance collaboration amongst employees. A number of enhancements have been made in Microsoft Lync The network topology setup is quite similar to the previous version but with a number of small differences. Changes include the consolidation of the archiving and monitoring features towards the front-end servers (optional feature). The Lync 2010 Director role is now optional and is not recommended anymore. Less servers are needed because front-end servers can now take the role of Director. 1.2 Document Purpose This documentation is intended to provide guidance on how to configure KEMP LoadMaster products to provide high availability for a Microsoft Lync Server 2013 environment. This documentation is created using a representative sample environment described later in the document. As this documentation is not intended to cover every possible deployment scenario it may not address unique setup or requirements. The KEMP Support Team is available to provide solutions for scenarios not explicitly defined. 1.3 Prerequisites It is assumed that the reader is a network administrator or a person otherwise familiar with networking and general computer terminology. It is further assumed that the Microsoft Lync Server 2013 environment has been set up and the KEMP LoadMaster has been installed. Copyright KEMP Technologies, Inc. All Rights Reserved. 5

6 1 Introduction Other LoadMaster documentation can be referred to as needed from The minimum requirements that should be met before proceeding are as follows: LoadMaster firmware version or above should be installed Configured and published Microsoft Lync Server architecture with Lync Topology builder Installed the Microsoft Servers, Active Directories and followed other Microsoft requirements Configured internal and external DNS entries for Front-End, Director and Edge pools Established access to the LoadMaster Web User Interface (WUI) Copyright KEMP Technologies, Inc. All Rights Reserved. 6

7 2 Load Balancing Microsoft Lync Load Balancing Microsoft Lync 2013 Deploying a Microsoft Lync environment can require multiple servers in Front-End pools and Edge server pools. Load balancing is necessary in this situation to distribute the traffic amongst these servers. Copyright KEMP Technologies, Inc. All Rights Reserved. 7

8 2 Load Balancing Microsoft Lync 2013 Microsoft Lync Server 2013 supports two load balancing solutions: DNS load balancing and Hardware Load Balancing (HLB). Hardware load balancers are also required to provide load balancing for the internal and external web services when DNS load balancing is used. Different load balancing methods cannot be used on the Edge internal and Edge external interfaces, for example, DNS load balancing cannot be used on the Edge internal interface when hardware load balancing is being used on the Edge external interface. Health checking at the LoadMaster ensures that, if one of the servers becomes inaccessible, the load balancer will take the sever offline and automatically re-route and reconnect users to other functioning servers. KEMP Technology recommend the configuration as depicted in the above diagram. If your configuration differs from the recommended configuration and there are issues deploying the LoadMaster, please contact the local KEMP Support Team for assistance. Copyright KEMP Technologies, Inc. All Rights Reserved. 8

9 3 General Configuration 3 General Configuration Some recommended general LoadMaster configuration settings are outlined below. These options can be set within the LoadMaster WUI. 3.1 Disable SNAT Globally By default, global Server Network Address Translation (SNAT) is enabled in the LoadMaster settings. KEMP recommends disabling SNAT globally when using the LoadMaster with a Lync 2013 environment. To disable SNAT globally, follow the steps below: 1. In the main menu, select System Configuration. 2. Select Miscellaneous Options. 3. Select Network Options. 4. Remove the check from the Enable Server NAT check box. 3.2 Subnet Originating Requests When the LoadMaster is deployed in a two-armed configuration, KEMP recommends enabling Subnet Originating Requests. When this option is enabled, the LoadMaster will use its local IP address, instead of the IP address of the Virtual Service, when communicating to the Real Servers. Subnet Originating Requests can be enabled on a per-virtual Service or a global basis. Copyright KEMP Technologies, Inc. All Rights Reserved. 9

10 3 General Configuration It is recommended that the Subnet Originating Requests option is enabled on a per-virtual Service basis. To enable Subnet Originating Requests globally, follow the steps below: 1. In the main menu of the LoadMaster WUI, select System Configuration > Miscellaneous Options > Network Options. 2. Select the Subnet Originating Requests check box. 3.3 Change Drop Connections Settings The LoadMaster must be configured to drop connections on Real Server Failure to have fast failover for clients to another Real Server. 1. To configure dropping connections, click System Configuration. 2. Click Miscellaneous Options. 3. Click L7 Configuration. Copyright KEMP Technologies, Inc. All Rights Reserved. 10

11 3 General Configuration 4. Select the Drop Connections on RS failure checkbox. 3.4 Increase the Connection Timeout The Loadmaster Connection Timeout must be set to one day. The reason why this value can be set so high is because the LoadMaster monitors client connection to Real Servers and if a server fails then the LoadMaster can drop the associated client connections to that real server. Clients are disconnected from the LoadMaster and then reconnected to the LoadMaster to connect to another Real Server. One day is the maximum value for this setting and it must be used in conjunction with the Drop Connections on RS failure option. 1. To configure the Connection Timeout, click System Configuration. 2. Click Miscellaneous Options. 3. Click L7 Configuration. Copyright KEMP Technologies, Inc. All Rights Reserved. 11

12 3 General Configuration 4. Enter (1 day) in the L7 Connection Drain Time (secs) field and click Set Time. 3.5 Connection Scaling For Large Scale Deployments Execution of this procedure is optional and should be used only in cases where network traffic is expected to be greater than 64,000 server connections at any one particular time. L7 Transparency must be disabled in order to use connection scaling. 1. To use connection scaling, click System Configuration. 2. Click Miscellaneous Options. 3. Click L7 Configuration. Copyright KEMP Technologies, Inc. All Rights Reserved. 12

13 3 General Configuration 4. Select the Allow connection scaling over 64K Connections checkbox. 5. Click Virtual Services. 6. Click View/Modify Services. 7. Click the Modify button of the appropriate Virtual IP Address. 8. Expand the Advanced Properties section. Copyright KEMP Technologies, Inc. All Rights Reserved. 13

14 3 General Configuration 9. In the Advanced Properties panel, input a list of Alternate Source Addresses. Multiple IPV4 addresses must be separated with a space; each must be unallocated and allow 64K connections. 10. Click the Set Alternate Source Addresses button. Copyright KEMP Technologies, Inc. All Rights Reserved. 14

15 4 Template 4 Template KEMP has developed a template containing our recommended settings for this workload. You can install this template to help when creating Virtual Services, as it automatically populates the settings. This is quicker and easier than manually configuring each Virtual Service. If needed, changes can be made to any of the Virtual Service settings after using the template. Download released templates from the Templates section on the KEMP documentation page: For more information and steps on how to import and use templates, refer to the Virtual Services and Templates, Feature Description on the KEMP Documentation Page. For steps on how to manually add and configure each of the Virtual Services using the recommended settings, refer to the steps in this document. Copyright KEMP Technologies, Inc. All Rights Reserved. 15

16 This deployment guide covers three types of Virtual Service; DNS Only, HLB only and those that are common to both types of environment. The below sections provide instructions and recommended configuration options for setting up a KEMP LoadMaster to work with Lync 2013 using these configuration options. For an explanation of each of the fields mentioned, refer to the Web User Interface (WUI), Configuration Guide. 5.1 DNS Only Configuration Refer to the sections below for instructions on how to set up the LoadMaster using a DNS only configuration. Microsoft recommends that DNS load balancing is used for Session Initiation Protocol (SIP) traffic. Microsoft also recommend that web services are configured to override FQDN for internal web services. Source-IP Persistence Source IP persistence can be used but take care before enabling it because: Clients from behind an NAT device show up as a single IP It can result in uneven connection distribution Cookies If cookies are used, there is no negative impact. However, there are some requirements: The cookie must be named MS-WSMAN It must not expire It must not be marked httponly Cookie optimization should be turned off To configure the various Front-End Virtual Services, refer to the sections below Lync Internal WebSvc HTTPS Virtual Service To configure a Virtual Service for Lync Internal WebSvc HTTP, follow the steps below: 3. Enter 443 in the Port field. 4. Enter a recognisable Service Name, for example Lync Internal WebSvc HTTPS. Copyright KEMP Technologies, Inc. All Rights Reserved. 16

17 5. Ensure that TCP is set as the Protocol. Standard Options Force L4 Disabled Extra Ports 4443 Click Set Extra Ports. Transparency Disabled Source IP Address Checked Port 5061 Click Set Check Port Lync Director 2013 DNS Virtual Service To configure a Virtual Service for Lync Director, follow the steps below: 3. Enter 443 in the Port field. 4. Enter a recognisable Service Name, for example Lync Director. 5. Ensure that TCP is set as the Protocol. Standard Options Extra Ports 444,4443 Click Set Extra Ports. Transparency Disabled Copyright KEMP Technologies, Inc. All Rights Reserved. 17

18 Source IP Address Checked Port 5061 Click Set Check Port Lync Internal WebSvc HTTP Virtual Service To configure a Virtual Service for Lync Internal WebSvc HTTP, follow the steps below: 3. Enter 80 in the Port field. 4. Enter a recognisable Service Name, for example Lync Internal WebSvc HTTP. 5. Ensure that tcp is set as the Protocol. Standard Options Extra Ports 8080 Click Set Extra Ports. Source IP Address Checked Port 5061 Click Set Check Port. Copyright KEMP Technologies, Inc. All Rights Reserved. 18

19 5.2 HLB Only Configuration The HLB only configuration instructions are below Lync Director 2013 HLB Virtual Service To configure a Virtual Service for Lync Director, follow the steps below: 3. Enter 443 in the Port field. 4. Enter a recognisable Service Name, for example Lync Director. 5. Ensure that TCP is set as the Protocol. Standard Options Extra Ports 444,4443 Click Set Extra Ports. Transparency Disabled Source IP Address Checked Port 5061 Click Set Check Port Lync Internal Director SIP Virtual Service To configure a Virtual Service for Lync Internal Director SIP, follow the steps below: 3. Enter 5061 in the Port field. Copyright KEMP Technologies, Inc. All Rights Reserved. 19

20 4. Enter a recognisable Service Name, for example Lync Internal Director SIP. 5. Ensure that tcp is set as the Protocol. Basic Properties Service Type Generic Standard Options Force L4 Disabled Transparency Server Initiating Protocols Disabled Normal Protocols Source IP Address Checked Port 5061 Click Set Check Port Lync Mediation Virtual Service DNS-only load balancing is sufficient for Mediation pools. If using the LoadMaster instead of DNS, load balance only TCP port To configure a Virtual Service for Lync Mediation, follow the steps below: 3. Enter 5070 in the Port field. 4. Enter a recognisable Service Name, for example Lync Mediation. 5. Ensure that TCP is set as the Protocol. Copyright KEMP Technologies, Inc. All Rights Reserved. 20

21 Basic Properties Service Type Generic Standard Options Force L4 Disabled Transparency Server Initiating Protocols Disabled Normal Protocols Source IP Address Checked Port 5070 Click Set Check Port Lync Edge Internal AV Media TCP Virtual Service This is the failback path for A/V media transfer. It is used for file transfer and desktop sharing. To configure a Virtual Service for Lync Edge Internal AV Media TCP, follow the steps below: 3. Enter 443 in the Port field. 4. Enter a recognisable Service Name, for example Lync Edge Internal AV Media TCP. 5. Ensure that TCP is set as the Protocol. Copyright KEMP Technologies, Inc. All Rights Reserved. 21

22 Basic Properties Service Type Generic Standard Options Force L4 Disabled Transparency Server Initiating Protocols Disabled Normal Protocols Source IP Address Checked Port 5061 Click Set Check Port Lync Edge Internal AV Media UDP Virtual Service This is the preferred path for A/V media transfer. To configure a Virtual Service for Lync Edge Internal AV Media UDP, follow the steps below: 3. Enter 3478 in the Port field. 4. Enter a recognisable Service Name, for example Lync Edge Internal AV Media UDP. 5. Select udp as the Protocol. Section Option Value Real Servers Real Server Check Parameters ICMP Ping Copyright KEMP Technologies, Inc. All Rights Reserved. 22

23 5.2.6 Lync Edge Internal SIP Virtual Service This is used by Directors and FE Pools. To configure a Virtual Service for Lync Edge Internal SIP, follow the steps below: 3. Enter 5061 in the Port field. 4. Enter a recognisable Service Name, for example Lync Edge Internal SIP. 5. Ensure that tcp is set as the Protocol. Basic Properties Service Type Generic Standard Options Extra Ports 5062 Click Set Extra Ports. Port 5062 is used by any FE pool and SBA. Server Initiating Protocols Normal Protocols Source IP Address Checked Port 5061 Click Set Check Port Lync Internal WebSvc HTTP Virtual Service To configure a Virtual Service for Lync Internal WebSvc HTTP, follow the steps below: Copyright KEMP Technologies, Inc. All Rights Reserved. 23

24 3. Enter 80 in the Port field. 4. Enter a recognisable Service Name, for example Lync Internal WebSvc HTTP. 5. Ensure that tcp is set as the Protocol. Standard Options Extra Ports 8080 Click Set Extra Ports. Source IP Address Checked Port 5061 Click Set Check Port Lync Internal Front-End DCOM Virtual Service To configure a Virtual Service for Lync Internal WebSvc HTTP, follow the steps below: 3. Enter 135 in the Port field. 4. Enter a recognisable Service Name, for example Lync Internal Front-End DCOM. 5. Ensure that tcp is set as the Protocol. Copyright KEMP Technologies, Inc. All Rights Reserved. 24

25 Standard Options Transparency Disabled Server Initiating Protocols Normal Protocols Source IP Address Checked Port 5061 Click Set Check Port Lync Internal WebSvc HTTPS Virtual Service To configure a Virtual Service for Lync Internal WebSvc HTTPS HLB Only, follow the steps below: 3. Enter 443 in the Port field. 4. Enter a recognisable Service Name, for example Lync Internal WebSvc HTTPS HLB Only. 5. Ensure that tcp is set as the Protocol. Standard Options Force L4 Enabled Extra Ports 4443 Click Set Extra Ports. Transparency Disabled Source IP Address Copyright KEMP Technologies, Inc. All Rights Reserved. 25

26 Checked Port 5061 Click Set Check Port Lync Internal Front-End SIP Virtual Service To configure a Virtual Service for Lync Internal Front-End SIP, follow the steps below: 3. Enter 5061 in the Port field. 4. Enter a recognisable Service Name, for example Lync Internal Front-End SIP. 5. Ensure that tcp is set as the Protocol. Basic Properties Service Type Generic Standard Options Force L4 Disabled Extra Ports Transparency Server Initiating Protocols 448, ,5075,5076,5080 Disabled Normal Protocols Source IP Address Click Set Extra Ports. Copyright KEMP Technologies, Inc. All Rights Reserved. 26

27 Configure Edge Virtual Services Checked Port 5061 Click Set Check Port. To configure the various Edge Virtual Services, refer to the sections below. When load balancing external interfaces of Edge pools, the shared interface IP should be used as the default gateway on all Edge interfaces. Also, a publicly routable IP with no NAT or port translation must be used Lync Edge External AV Media UDP Virtual Service To configure a Virtual Service for Lync Edge External AV Media UDP, follow the steps below: 3. Enter 3478 in the Port field. 4. Enter a recognisable Service Name, for example Lync Edge External AV Media UDP. 5. Select udp as the Protocol. Section Option Value Standard Options Source IP Address Real Servers Real Server Check Parameters ICMP Ping Lync Edge External SIP Virtual Service To configure a Virtual Service for Lync Edge External SIP, follow the steps below: Copyright KEMP Technologies, Inc. All Rights Reserved. 27

28 3. Enter 443 in the Port field. 4. Enter a recognisable Service Name, for example Lync Edge External SIP. 5. Ensure that tcp is set as the Protocol. Standard Options Force L4 Disabled Transparency Disabled Source IP Address Checked Port 5061 Click Set Check Port Lync Edge External SIP Federation Virtual Service To configure a Virtual Service for Lync Edge External SIP Federation, follow the steps below: 3. Enter 5061 in the Port field. 4. Enter a recognisable Service Name, for example Lync Edge External SIP Federation. 5. Ensure that tcp is set as the Protocol. Copyright KEMP Technologies, Inc. All Rights Reserved. 28

29 Standard Options Force L4 Disabled Transparency Disabled Source IP Address Checked Port 5061 Click Set Check Port Lync Edge External XMPP Virtual Service To configure a Virtual Service for Lync Edge External XMPP, follow the steps below: 3. Enter 5269 in the Port field. 4. Enter a recognisable Service Name, for example Lync Edge External XMPP. 5. Ensure that tcp is set as the Protocol. Standard Options Force L4 Disabled Transparency Disabled Source IP Address Copyright KEMP Technologies, Inc. All Rights Reserved. 29

30 Checked Port 5061 Click Set Check Port Lync Edge External Conferencing Virtual Service To configure a Virtual Service for Lync Edge External Conferencing, follow the steps below: 3. Enter 443 in the Port field. 4. Enter a recognisable Service Name, for example Lync Edge External Conferencing. 5. Ensure that tcp is set as the Protocol. Standard Options Force L4 Disabled Transparency Disabled Source IP Address Advanced Properties Redirection URL Click Add HTTP Redirector. Checked Port 443 Click Set Check Port. Copyright KEMP Technologies, Inc. All Rights Reserved. 30

31 Lync Edge External AV Media TCP Virtual Service To configure a Virtual Service for Lync Edge External AV, follow the steps below: 3. Enter 443 in the Port field. 4. Enter a recognizable Service Name, for example Lync Edge External AV Media TCP. 5. Ensure that tcp is set as the Protocol. Standard Options Force L4 Disabled Transparency Enabled Source IP Address Checked Port 443 Click Set Check Port. 5.3 Common to Both The Virtual Services listed below are common to both DNS and HLB configurations Lync Office Web App Servers Virtual Service To configure a Virtual Service for Office Web App Servers, follow the steps below: Copyright KEMP Technologies, Inc. All Rights Reserved. 31

32 3. Enter 443 in the Port field. 4. Enter a recognisable Service Name, for example Office Web App Servers. 5. Ensure that TCP is set as the Protocol. SSL Properties SSL Acceleration Enabled Standard Options Reencrypt Enabled Super HTTP and Source IP 30 Minutes Advanced Properties Redirection URL Click Add HTTP Redirector. Real Servers Real Server Check Parameters HTTPS Protocol URL /hosting/discovery Click Set URL. Use HTTP/1.1 HTTP Method Enabled GET Lync Director Reverse Proxy HTTP Virtual Service To configure a Virtual Service for Lync Reverse Proxy HTTP, follow the steps below: 3. Enter 80 in the Port field. 4. Enter a recognisable Service Name, for example Lync Director Reverse Proxy HTTP. 5. Ensure that TCP is set as the Protocol. Copyright KEMP Technologies, Inc. All Rights Reserved. 32

33 Standard Options Force L4 Disabled Transparency Disabled Source IP Address 8. Add the Real Servers: 9. Checked Port 5061 Click Set Check Port. a) Expand the Real Servers section. b) Click Add New. c) Type the address of the Real Server. d) Type 8080 as the Port. Ensure to not use 80 as the Real Server Port. e) Click Add This Real Server. f) Repeat the steps above to add more Real Servers as needed, based on the environment Lync Director Reverse Proxy HTTPS Virtual Service To configure a Virtual Service for Lync Reverse Proxy HTTPS, follow the steps below: 3. Enter 443 in the Port field. 4. Enter a recognisable Service Name, for example Lync Director Reverse Proxy HTTPS. Copyright KEMP Technologies, Inc. All Rights Reserved. 33

34 5. Ensure that TCP is set as the Protocol. SSL Properties SSL Acceleration Enabled Reencrypt Enabled Standard Options Source IP Address 8. Add the Real Servers: Checked Port 5061 Click Set Check Port. a) Expand the Real Servers section. b) Click Add New. c) Type the address of the Real Server for the Director(s). d) Type 4443 as the Port. Ensure to not use 443 as the Real Server Port. e) Click Add This Real Server. f) Repeat the steps above to add more Real Servers as needed, based on the environment Lync Front End Reverse Proxy HTTP Virtual Service To configure a Virtual Service for Lync Reverse Proxy HTTP, follow the steps below: 3. Enter 80 in the Port field. Copyright KEMP Technologies, Inc. All Rights Reserved. 34

35 4. Enter a recognisable Service Name, for example Lync Front End Reverse Proxy HTTP. 5. Ensure that TCP is set as the Protocol. Standard Options Force L4 Disabled Transparency Disabled Source IP Address 8. Add the Real Servers: Checked Port 5061 Click Set Check Port. a) Expand the Real Servers section. b) Click Add New. c) Type the address of the Real Server. d) Type 8080 as the Port. Please do not use 80 as the Real Server Port. e) Click Add This Real Server. f) Repeat the steps above to add more Real Servers as needed, based on the environment Lync Front End Reverse Proxy HTTPS Virtual Service To configure a Virtual Service for Lync Reverse Proxy HTTPS, follow the steps below: 3. Enter 443 in the Port field. Copyright KEMP Technologies, Inc. All Rights Reserved. 35

36 4. Enter a recognisable Service Name, for example Lync Front End Reverse Proxy HTTPS. 5. Ensure that TCP is set as the Protocol. SSL Properties SSL Acceleration Enabled Reencrypt Enabled Standard Options Source IP Address 8. Add the Real Servers: Checked Port 5061 Click Set Check Port. a) Expand the Real Servers section. b) Click Add New. c) Type the address of the Real Server. d) Type 4443 as the Port. Do not use 443 as the Real Server Port. e) Click Add This Real Server. f) Repeat the steps above to add more Real Servers as needed, based on the environment. Copyright KEMP Technologies, Inc. All Rights Reserved. 36

37 6 Additional Information 6 Additional Information Some additional information that may be of use is contained within the sections below. 6.1 Server Maintenance When blocking traffic to a server during maintenance, removing the server IP entry from the pool Fully Qualified Domain Name (FQDN) is not sufficient. The server entry must be removed from the DNS. As the server to server traffic is topology-aware, in order to block server to server traffic the server must be removed from the DNS topology. 6.2 Loss of Failover while using DNS Loss of failover when load balancing Edge pools using DNS is possible in the following scenarios: Federation with organizations running OCS versions older than Lync 2010 PIM connectivity with Skype, Windows Live, AOL, Yahoo! and XMPP partners UM Play on Phone functionality Transferring calls from UM Auto Attendant 6.3 Hardware Load Balancing If hardware load balancing is being used, a list of the ports that must be open can be found here: Hardware load balancing Edge servers requires N+1 Public IP addresses. Refer to the two links below for further information on hardware load balancing: Copyright KEMP Technologies, Inc. All Rights Reserved. 37

38 7 References 7 References The following sources are referred to in this document: KEMP Technologies website KEMP Technologies Documentation page MS Lync 2013 Single Pair Addendum, Deployment Guidehttp:// Web User Interface (WUI), Configuration Guide Virtual Services and Templates, Feature Description Ports and Protocols for Internal Servers 1. Port Summary - Scaled Consolidated Edge with Hardware Load Balancers 2. Scaled Consolidated Edge with Hardware Load Balancers 3. Copyright KEMP Technologies, Inc. All Rights Reserved. 38

39 Last Updated Date Last Updated Date This document was last updated on 11 January Copyright KEMP Technologies, Inc. All Rights Reserved. 39