Microsoft Skype for Business

1 Introduction

 KEMP’s LoadMaster family of purpose-built hardware and Virtual LoadMasters (VLMs) 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. The LoadMaster efficiently distributes user traffic for Microsoft Skype for Business 2015 so that users get the best experience possible.

The entire KEMP LoadMaster product family, including the Virtual LoadMaster (VLM) supports Microsoft Skype for Business 2015.

For more information about KEMP Technologies, visit us online at www.kemptechnologies.com.

1.1 Microsoft Skype for Business 2015

Microsoft Skype for Business 2015 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 Skype for Business 2015 allows companies to enhance collaboration amongst employees.

A number of enhancements have been made in Microsoft Skype for Business 2015. The network topology setup is quite similar to the previous version (Lync 2013) but with a number of small differences. The Director role is still optional and is not recommended. Less servers are needed because front-end servers can now take the role of Director. A new role has been added called the Video Interoperability Server (VIS) which acts as an intermediary between third party teleconference systems and the Skype for Business 2015 deployment.

1.2 Document Purpose

This documentation is intended to provide guidance on how to configure KEMP LoadMaster products to provide High Availability (HA) for a Microsoft Skype for Business 2015 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 Skype for Business 2015 environment has been set up and the KEMP LoadMaster has been installed.

Other LoadMaster documentation can be referred to as needed from http://kemptechnologies.com/documentation.

The minimum requirements that should be met before proceeding are as follows:

LoadMaster firmware version 7.1 or above should be installed

Configured and published Microsoft Skype for Business 2015 architecture with Skype for Business 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)

2 Load Balancing Microsoft Skype for Business 2015

Load Balancing Microsoft Skype.png

Deploying a Microsoft Skype for Business 2015 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.

Microsoft Skype for Business 2015 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, that is, 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.

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 Skype for Business 2015 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.

Disable SNAT Globally.png

4. Remove the check from the Enable Server NAT check box.

3.2 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.

Change Drop Connections Settings.png

4. Select the Drop Connections on RS failure checkbox.

3.3 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.

Increase the Connection Timeout.png

4. Enter 86400 (1 day) in the L7 Connection Drain Time (secs) field and click Set Time.

3.4 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.

Connection Scaling For Large.png

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.

VSVSAP023.png

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.

3.5 Enable Subnet Originating Requests Globally

It is best practice to enable the Subnet Originating Requests option globally.

In a one-armed setup (where the Virtual Service and Real Servers are on the same network/subnet) Subnet Originating Requests is usually not needed. However, enabling Subnet Originating Requests should not affect the routing in a one-armed setup.

In a two-armed setup where the Virtual Service is on network/subnet A, for example, and the Real Servers are on network B - Subnet Originating Requests should be enabled on LoadMasters with firmware version 7.1-16 and above.

When Subnet Originating Requests is enabled, the LoadMaster will route traffic so that the Real Server will see traffic arriving from the LoadMaster interface that is in that network/subnet not the Virtual Service address.

When Subnet Originating Requests is enabled globally, it is automatically enabled on all Virtual Services. If the Subnet Originating Requests option is disabled globally, you can choose whether or not to enable Subnet Originating Requests on a per-Virtual Service basis.

To enable Subnet Originating Requests globally, follow the steps below:

1. In the main menu of the LoadMaster Web User Interface (WUI), go to System Configuration > Miscellaneous Options > Network Options.

SCMONO002.png

2. Tick the Subnet Originating Requests check box.

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: http://kemptechnologies.com/documentation.

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.

5 Configuring Skype for Business 2015 VSs without Templates

This deployment guide covers three types of Virtual Service (VS); 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 Skype for Business 2015 without the use of Virtual Service Templates. 

For an explanation of each of the fields mentioned, refer to the http://kemptechnologies.com/documentation.

5.1 DNS Only Configuration without Templates

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 a 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 Virtual Services, refer to the sections below.

5.1.1 Director Internal WebSvc HTTPS Virtual Service

To configure a Virtual Service for Skype for Business Director, follow the steps below:

1. Click the Add New button.

Director Internal WebSvc HTTPS.png

2. Enter a Virtual Address.

3. Enter 443 in the Port field.

4. Enter a recognisable Service Name, for example SfB 2015 Director Internal WebSvc HTTPS.

5. Ensure that TCP is set as the Protocol.

6. Click Add This Virtual Service.

Director Internal WebSvc HTTPS_1.png

7. Expand the Standard Options section and select the following options:

a) Ensure the Force L4 checkbox (if visible) is clear.

b) Ensure the Transparency checkbox is clear.

c) Enter 444 in the Extra Ports field and click the Set Extra Ports button.

d) Select Source IP Address as the Persistence Mode.

e) Select 20 Minutes as the Persistence Timeout.

f) Select least connection as the Scheduling Method.

g) Enter 1800 in the Idle Connection Timeout field and click Set Idle Timeout.

Director Internal WebSvc HTTPS_2.png

8. Expand the Real Servers section.

9. Select TCP Connection Only from the drop-down list.

10. Enter 5061 in the Checked Port field and click Set Check Port.

5.1.2 Director Internal WebSvc HTTP Virtual Service

To configure a Virtual Service for Skype for Business Director, follow the steps below:

1. Click the Add New button.

Director Internal WebSvc HTTP.png

2. Enter a Virtual Address.

3. Enter 80 in the Port field.

4. Enter a recognisable Service Name, for example SfB 2015 Director Internal WebSvc HTTP.

5. Ensure that TCP is set as the Protocol.

6. Click Add This Virtual Service.

Director Internal WebSvc HTTP_1.png

7. Expand the Standard Options section and select the following options:

a) Ensure the Force L4 checkbox is clear.

b) Ensure the Transparency checkbox is clear.

c) Select Source IP Address as the Persistence Mode.

d) Select 20 Minutes as the Persistence Timeout.

e) Select least connection as the Scheduling Method.

f) Enter 1800 in the Idle Connection Timeout field and click Set Idle Timeout.

8. Expand the Real Servers section.

Director Internal WebSvc HTTPS_2.png

9. Select TCP Connection Only from the drop-down list.

10. Enter 5061 in the Checked Port field and click Set Check Port.

5.1.3 Front End Internal WebSvc HTTPS Virtual Service

To configure a HTTPS Virtual Service for Skype for Business Front End Internal WebSvc, follow the steps below:

1. Click the Add New button.

Front End Internal WebSvc.png

2. Enter a Virtual Address.

3. Enter 443 in the Port field.

4. Enter a recognisable Service Name, for example SfB 2015 FE Internal WebSvc HTTPS.

5. Ensure that TCP is set as the Protocol.

6. Click Add This Virtual Service.

Front End Internal WebSvc_1.png

7. Expand the Standard Options section and select the following options:

a) Ensure the Force L4 checkbox is clear.

b) Ensure the Transparency checkbox is clear.

c) Enter 444 in the Extra Ports field and click the Set Extra Ports button.

d) Select Source IP Address as the Persistence Mode.

e) Select 20 Minutes as the Persistence Timeout.

f) Select least connection as the Scheduling Method.

g) Enter 1800 in the Idle Connection Timeout field and click Set Idle Timeout.

Director Internal WebSvc HTTPS_2.png

8. Expand the Real Servers section and select the following options:

a) Select TCP Connection Only in the drop-down menu.

b) Enter 5061 in the Checked Port field and click Set Check Port.

5.1.4 Front End Internal WebSvc HTTP Virtual Service

To configure a Virtual Service for Skype for Business Front End Internal WebSvc HTTP, follow the steps below:

1. Click the Add New button.

Front End Internal WebSvc_1_1.png

2. Enter a Virtual Address.

3. Enter 80 in the Port field.

4. Enter a recognisable Service Name, for example SfB 2015 FE Internal WebSvc HTTP.

5. Ensure that tcp is set as the Protocol.

6. Click Add This Virtual Service.

Front End Internal WebSvc_1_2.png

7. Expand the Standard Options section and select the following options:

a) Ensure the Force L4 checkbox is clear.

b) Ensure the Transparency checkbox is clear.

c) Select Source IP Address as the Persistence Mode.

d) Select 20 Minutes as the Persistence Timeout.

e) Select least connection as the Scheduling Method.

f) Enter 1800 in the Idle Connection Timeout field and click Set Idle Timeout.

Director Internal WebSvc HTTPS_2.png

8. Expand the Real Servers section and select the following options:

a) Select TCP Connection Only in the drop-down menu.

b) Enter 5061 in the Checked Port field and click Set Check Port.

5.2 HLB Only Configuration without Templates

The HLB only configuration instructions are below.

5.2.1 Director Internal WebSvc HTTPS Virtual Service

To configure a Virtual Service for Skype for Business Director, follow the steps below:

1. Click the Add New button.

Director Internal WebSvc HTTPS_1_1.png

2. Enter a Virtual Address.

3. Enter 443 in the Port field.

4. Enter a recognisable Service Name, for example SfB 2015 Director Internal WebSvc HTTPS.

5. Ensure that TCP is set as the Protocol.

6. Click Add This Virtual Service.

Director Internal WebSvc HTTPS_1_2.png

7. Expand the Standard Options section and select the following options:

a) Ensure the Force L4 checkbox is clear.

b) Ensure the Transparency checkbox is clear.

c) Enter 444 in the Extra Ports field and click the Set Extra Ports button.

d) Select Source IP Address as the Persistence Mode.

e) Select 20 Minutes as the Persistence Timeout.

f) Select least connection as the Scheduling Method.

g) Enter 1800 in the Idle Connection Timeout field and click Set Idle Timeout.

Director Internal WebSvc HTTPS_2.png

8. Expand the Real Servers section.

9. Select TCP Connection Only as the Real Server Check Parameters.

10. Enter 5061 in the Checked Port field and click Set Check Port.

5.2.2 Director Internal WebSvc HTTP Virtual Service

To configure a Virtual Service for Skype for Business Director, follow the steps below:

1. Click the Add New button.

Director Internal WebSvc HTTP_1_1.png

2. Enter a Virtual Address.

3. Enter 80 in the Port field.

4. Enter a recognisable Service Name, for example SfB 2015 Director Internal WebSvc HTTP.

5. Ensure that TCP is set as the Protocol.

6. Click Add This Virtual Service.

Director Internal WebSvc HTTP_1_2.png

7. Expand the Standard Options section and select the following options:

a) Ensure the Force L4 check box is clear.

b) Ensure the Transparency check box is clear.

c) Select Source IP Address as the Persistence Mode.

d) Select 20 Minutes as the Persistence Timeout.

e) Select least connection as the Scheduling Method.

f) Enter 1800 in the Idle Connection Timeout field and click Set Idle Timeout.

Director Internal WebSvc HTTPS_2.png

8. Expand the Real Servers section.

9. Select TCP Connection Only as the Real Server Check Parameters.

10. Enter 5061 in the Checked Port field and click Set Check Port.

5.2.3 Front End Internal WebSvc HTTPS Virtual Service

To configure a Virtual Service for Skype for Business Front End Internal WebSvc HTTP, follow the steps below:

1. Click the Add New button.

Front End Internal WebSvc_2.png

2. Enter a Virtual Address.

3. Enter 443 in the Port field.

4. Enter a recognisable Service Name, for example SfB 2015 FE Internal WebSvc HTTPS.

5. Ensure that TCP is set as the Protocol.

6. Click Add This Virtual Service.

Front End Internal WebSvc_2_1.png

7. Expand the Standard Options section and select the following options:

a) Ensure the Force L4 check box is clear.

b) Ensure the Transparency check box is clear.

c) Enter 444 in the Extra Ports field and click the Set Extra Ports button.

d) Select Source IP Address as the Persistence Mode.

e) Select 20 Minutes as the Persistence Timeout.

f) Select least connection as the Scheduling Method.

g) Enter 1800 in the Idle Connection Timeout field and click Set Idle Timeout.

Director Internal WebSvc HTTPS_2.png

8. Expand the Real Servers section and select the following options:

a) Select TCP Connection Only in the drop-down menu.

b) Enter 5061 in the Checked Port field and click Set Check Port.

5.2.4 Front End Internal WebSvc HTTP Virtual Service

To configure a Virtual Service for Skype for Business Front End Internal WebSvc HTTP, follow the steps below:

1. Click the Add New button.

Front End Internal WebSvc_3.png

2. Enter a Virtual Address.

3. Enter 80 in the Port field.

4. Enter a recognisable Service Name, for example SfB 2015 FE Internal WebSvc HTTP.

5. Ensure that tcp is set as the Protocol.

6. Click Add This Virtual Service.

Front End Internal WebSvc_3_1.png

7. Expand the Standard Options section and select the following options:

a) Ensure the Force L4 checkbox is clear.

b) Ensure the Transparency checkbox is clear.

c) Select Source IP Address as the Persistence Mode.

d) Select 20 Minutes as the Persistence Timeout.

e) Select least connection as the Scheduling Method.

f) Enter 1800 in the Idle Connection Timeout field and click Set Idle Timeout.

Director Internal WebSvc HTTPS_2.png

8. Expand the Real Servers section and select the following options:

a) Select TCP Connection Only in the drop-down menu.

b) Enter 5061 in the Checked Port field and click Set Check Port.

5.2.5 Internal Front-End SIP Virtual Service

To configure a Virtual Service for Skype for Business Internal Front-End SIP, follow the steps below:

1. Click the Add New button.

Internal Front End SIP Virtual.png

2. Enter a Virtual Address.

3. Enter 5061 in the Port field.

4. Enter a recognisable Service Name, for example SfB 2015 Internal Front-End SIP.

5. Ensure that tcp is set as the Protocol.

6. Click Add This Virtual Service.

Internal Front End SIP Virtual_1.png

7. Within the Basic Properties section, select Generic as the Service Type.

Internal Front End SIP Virtual_2.png

8. Expand the Standard Options section and select the following options:

a) Enter 448,5070-5073,5075,5076,5080 in the Extra Ports field and click the Set Extra Ports button.

b) Select Normal Protocols in the Server Initiating Protocols drop-down menu.

c) Select Source IP Address as the Persistence Mode.

d) Select 20 Minutes as the Persistence Timeout.

e) Select least connection as the Scheduling Method.

f) Enter 1800 in the Idle Connection Timeout field and click Set Idle Timeout.

Director Internal WebSvc HTTPS_2.png

9. Expand the Real Servers section and select the following options:

a) Select TCP Connection Only in the drop-down menu.

b) Enter 5061 in the Checked Port field and click Set Check Port.

5.2.6 Internal Front-End DCOM Virtual Service

To configure a Virtual Service for Skype for Business Internal WebSvc HTTP, follow the steps below:

1. Click the Add New button.

Internal Front End DCOM Virtual.png

2. Enter a Virtual Address.

3. Enter 135 in the Port field.

4. Enter a recognisable Service Name, for example SfB 2015 Internal Front-End DCOM.

5. Ensure that tcp is set as the Protocol.

6. Click Add This Virtual Service.

Internal Front End DCOM Virtual_1.png

7. Expand the Standard Options section and select the following options:

a) Deselect the Transparency checkbox.

b) Select Normal Protocols in the Server Initiating Protocols drop-down menu.

c) Select Source IP Address as the Persistence Mode.

d) Select 20 Minutes as the Persistence Timeout.

e) Select least connection as the Scheduling Method.

f) Enter 1800 in the Idle Connection Timeout field and click Set Idle Timeout.

Director Internal WebSvc HTTPS_2.png

8. Expand the Real Servers section and select the following options:

a) Select TCP Connection Only in the drop-down menu.

b) Enter 5061 in the Checked Port field and click Set Check Port.

5.2.7 Director SIP Virtual Service

To configure a Virtual Service for Skype for Business Internal Director SIP, follow the steps below:

1. Click the Add New button.

Director SIP Virtual Service.png

2. Enter a Virtual Address.

3. Enter 5061 in the Port field.

4. Enter a recognisable Service Name, for example SfB 2015 Internal Director SIP.

5. Ensure that tcp is set as the Protocol.

6. Click Add This Virtual Service.

Director SIP Virtual Service_1.png

7. Within the Basic Properties section, select Generic as the Service Type.

Director SIP Virtual Service_2.png

8. Expand the Standard Options section and select the following options:

a) Ensure the Force L4 checkbox is clear.

b) Ensure the Transparency checkbox is clear.

c) Select Normal Protocols in the Server Initiating Protocols drop-down menu.

d) Select Source IP Address as the Persistence Mode.

e) Select 20 Minutes as the Persistence Timeout.

f) Select least connection as the Scheduling Method.

g) Enter 1800 in the Idle Connection Timeout field and click Set Idle Timeout.

h) Select the Use Address for Server NAT checkbox.

Director Internal WebSvc HTTPS_2.png

9. Expand the Real Servers section and select the following options:

a) Select TCP Connection Only in the drop-down menu.

b) Enter 5061 in the Checked Port field and click Set Check Port.

5.2.8 Mediation Virtual Service

DNS-only load balancing is sufficient for Mediation pools. If using the LoadMaster instead of DNS, load balance only TCP port 5070.

To configure a Virtual Service for Skype for Business Mediation, follow the steps below:

1. Click the Add New button.

Mediation Virtual Service.png

2. Enter a Virtual Address.

3. Enter 5070 in the Port field.

4. Enter a recognisable Service Name, for example SfB 2015 Mediation.

5. Ensure that TCP is set as the Protocol.

6. Click Add This Virtual Service.

Mediation Virtual Service_1.png

7. Within the Basic Properties section, select Generic as the Service Type.

Mediation Virtual Service_2.png

8. Expand the Standard Options section and select the following options:

a) Ensure the Force L4 checkbox is clear.

b) Ensure the Transparency checkbox is clear.

c) Select Normal Protocols in the Server Initiating Protocols drop-down menu.

d) Select Source IP Address as the Persistence Mode.

e) Select 20 Minutes as the Persistence Timeout.

f) Select least connection as the Scheduling Method.

g) Enter 1800 in the Idle Connection Timeout field and click Set Idle Timeout.

Mediation Virtual Service_3.png

9. Expand the Real Servers section and select the following options:

a) Select TCP Connection Only in the drop-down menu.

b) Enter 5070 in the Checked Port field and click Set Check Port.

5.2.9 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 Skype for Business Edge Internal AV Media TCP, follow the steps below:

1. Click the Add New button.

Edge Internal AV Media TCP.png

2. Enter a Virtual Address.

3. Enter 443 in the Port field.

4. Enter a recognisable Service Name, for example SfB 2015 Edge Internal AV Media TCP.

5. Ensure that TCP is set as the Protocol.

6. Click Add This Virtual Service.

Edge Internal AV Media TCP_1.png

7. Within the Basic Properties section, select Generic as the Service Type.

Edge Internal AV Media TCP_2.png

8. Expand the Standard Options section and select the following options:

a) Ensure the Force L4 check box is clear.

b) Ensure the Transparency check box is clear.

c) Select Normal Protocols in the Server Initiating Protocols drop-down menu.

d) Select Source IP Address as the Persistence Mode.

e) Select 20 Minutes as the Persistence Timeout.

f) Select least connection as the Scheduling Method.

g) Enter 1800 in the Idle Connection Timeout field and click Set Idle Timeout.

Edge Internal AV Media TCP_3.png

9. Expand the Real Servers section and select the following options:

a) Select TCP Connection Only in the drop-down menu.

b) Enter 5061 in the Checked Port field and click Set Check Port.

5.2.10 Edge Internal AV Media UDP Virtual Service

This is the preferred path for A/V media transfer.

To configure a Virtual Service for Skype for Business Edge Internal AV Media UDP, follow the steps below:

1. Click the Add New button.

Edge Internal AV Media UDP.png

2. Enter a Virtual Address.

3. Enter 3478 in the Port field.

4. Enter a recognisable Service Name, for example SfB 2015 Edge Internal AV Media UDP.

5. Select udp as the Protocol.

6. Click Add This Virtual Service.

7. Expand the Standard Options section.

Edge Internal AV Media UDP_1.png

8. Select Source IP Address as the Persistence Mode.

9. Select 20 Minutes as the Persistence Timeout.

10. Select least connection as the Scheduling Method.

Edge Internal AV Media UDP_2.png

11. Expand the Real Servers section.

12. Select ICMP Ping in the Real Server Check Parameters drop-down menu.

5.2.11 Edge Internal SIP Virtual Service

This is used by Directors and FE Pools.

To configure a Virtual Service for Skype for Business Edge Internal SIP, follow the steps below:

1. Click the Add New button.

Edge Internal SIP Virtual.png

2. Enter a Virtual Address.

3. Enter 5061 in the Port field.

4. Enter a recognisable Service Name, for example SfB 2015 Edge Internal SIP.

5. Ensure that tcp is set as the Protocol.

6. Click Add This Virtual Service.

Edge Internal SIP Virtual_1.png

7. Within the Basic Properties section, select Generic as the Service Type.

Edge Internal SIP Virtual_2.png

8. Expand the Standard Options section and select the following options:

a) Enter 5062 in the Extra Ports field and click Set Extra Ports.

Port 5062 is used by any FE pool and SBA

b) Ensure the Transparency checkbox is clear.

c) Select Normal Protocols in the Server Initiating Protocols drop-down menu.

d) Select Source IP Address as the Persistence Mode.

e) Select 20 Minutes as the Persistence Timeout.

f) Select least connection as the Scheduling Method.

g) Enter 1800 in the Idle Connection Timeout and click Set Idle Timeout.

h) Select the Use Address for Server NAT checkbox.

Edge Internal SIP Virtual_3.png

9. Expand the Real Servers section and select the following options:

a) Select TCP Connection Only in the Real Server Check Parameters drop-down menu.

b) Enter 5061 in the Checked Port field and click Set Check Port.

5.3 Configure External Edge Virtual Services without Templates

To configure the various Edge Virtual Services, refer to the sections below.

Load Balancing External Interfaces of Edge Pools using LoadMaster

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.

5.3.1 Edge External SIP Virtual Service

To configure a Virtual Service for Skype for Business Edge External SIP, follow the steps below:

1. Click the Add New button.

Edge External SIP Virtual.png

2. Enter a Virtual Address.

3. Enter 443 in the Port field.

4. Enter a recognisable Service Name, for example SfB 2015 Edge External SIP.

5. Ensure that tcp is set as the Protocol.

6. Click Add This Virtual Service.

Edge External SIP Virtual_1.png

7. Expand the Standard Options section and select the following options:

a) Ensure the Force L4 checkbox is clear.

b) Ensure the Transparency checkbox is clear.

c) Select Source IP Address as the Persistence Mode.

d) Select 20 Minutes as the Persistence Timeout.

e) Select least connection as the Scheduling Method.

f) Enter 1800 in the Idle Connection Timeout and click Set Idle Timeout.

Edge Internal SIP Virtual_3.png

8. Expand the Real Servers section and select the following options:

a) Select TCP Connection Only in the Real Server Check Parameters drop-down menu.

b) Enter 5061 in the Checked Port field and click Set Check Port.

5.3.2 Edge External SIP Federation Virtual Service

To configure a Virtual Service for Skype for Business Edge External SIP Federation, follow the steps below:

1. Click the Add New button.

Edge External SIP Federation.png

2. Enter a Virtual Address.

3. Enter 5061 in the Port field.

4. Enter a recognisable Service Name, for example SfB 2015 Edge External SIP Federation.

5. Ensure that tcp is set as the Protocol.

6. Click Add This Virtual Service.

Edge External SIP Federation_1.png

7. Expand the Standard Options section and select the following options:

a) Ensure the Force L4 checkbox is clear.

b) Ensure the Transparency checkbox is clear.

c) Select Source IP Address as the Persistence Mode.

d) Select 20 Minutes as the Persistence Timeout.

e) Select least connection as the Scheduling Method.

f) Enter 1800 in the Idle Connection Timeout and click Set Idle Timeout.

Edge Internal SIP Virtual_3.png

8. Expand the Real Servers section and select the following options:

a) Select TCP Connection Only in the Real Server Check Parameters drop-down menu.

b) Enter 5061 in the Checked Port field and click Set Check Port.

5.3.3 Edge External XMPP Virtual Service

To configure a Virtual Service for Skype for Business Edge External XMPP, follow the steps below:

1. Click the Add New button.

Edge External XMPP Virtual.png

2. Enter a Virtual Address.

3. Enter 5269 in the Port field.

4. Enter a recognisable Service Name, for example SfB 2015 Edge External XMPP.

5. Ensure that tcp is set as the Protocol.

6. Click Add This Virtual Service.

Edge External XMPP Virtual_1.png

7. Expand the Standard Options section and select the following options:

a) Ensure the Force L4 checkbox is clear.

b) Ensure the Transparency checkbox is clear.

c) Select Source IP Address as the Persistence Mode.

d) Select 20 Minutes as the Persistence Timeout.

e) Select least connection as the Scheduling Method.

f) Enter 1800 in the Idle Connection Timeout and click Set Idle Timeout.

Edge Internal SIP Virtual_3.png

8. Expand the Real Servers section and select the following options:

a) Select TCP Connection Only in the Real Server Check Parameters drop-down menu.

b) Enter 5061 in the Checked Port field and click Set Check Port.

5.3.4 Edge External Conferencing Virtual Service

To configure a Virtual Service for Skype for Business Edge External Conferencing, follow the steps below:

1. Click the Add New button.

Edge External Conferencing.png

2. Enter a Virtual Address.

3. Enter 443 in the Port field.

4. Enter a recognisable Service Name, for example SfB 2015 Edge External Conferencing.

5. Ensure that tcp is set as the Protocol.

6. Click Add This Virtual Service.

Edge External Conferencing_1.png

7. Expand the Standard Options section and select the following options:

a) Ensure the Force L4 checkbox is clear.

b) Ensure the Transparency checkbox is clear.

c) Select Source IP Address as the Persistence Mode.

d) Select 20 Minutes as the Persistence Timeout.

e) Select least connection as the Scheduling Method.

f) Enter 1800 in the Idle Connection Timeout and click Set Idle Timeout.

Edge External Conferencing_2.png

8. Expand the Real Servers section and select the following options:

a) Select TCP Connection Only in the Real Server Check Parameters drop-down menu.

b) Enter 443 in the Checked Port field and click Set Check Port.

5.3.5 Edge External AV Media TCP Virtual Service

To configure a Virtual Service for Skype for Business Edge External AV, follow the steps below:

1. Click the Add New button.

Edge External AV Media TCP.png

2. Enter a Virtual Address.

3. Enter 443 in the Port field.

4. Enter a recognisable Service Name, for example SfB 2015 Edge External AV Media TCP.

5. Ensure that tcp is set as the Protocol.

6. Click Add This Virtual Service.

Edge External AV Media TCP_1.png

7. Expand the Standard Options section and select the following options:

a) Ensure the Force L4 check box is clear.

b) Select Transparency check box.

c) Select Source IP Address as the Persistence Mode.

d) Select 20 Minutes as the Persistence Timeout.

e) Select least connection as the Scheduling Method.

f) Enter 1800 in the Idle Connection Timeout and click Set Idle Timeout.

Edge External Conferencing_2.png

8. Expand the Real Servers section and select the following options:

a) Select TCP Connection Only in the Real Server Check Parameters drop-down menu.

b) Enter 443 in the Checked Port field and click Set Check Port.

5.3.6 Edge External AV Media UDP Virtual Service

To configure a Virtual Service for Skype for Business Edge External AV Media UDP, follow the steps below:

1. Click the Add New button.

Edge External AV Media UDP.png

2. Enter a Virtual Address.

3. Enter 3478 in the Port field.

4. Enter a recognisable Service Name, for example SfB 2015 Edge External AV Media UDP.

5. Select udp as the Protocol.

6. Click Add This Virtual Service.

Edge External AV Media UDP_1.png

7. Expand the Standard Options section and select the following options:

a) Select Source IP Address as the Persistence Mode.

b) Set the Timeout to 20 Minutes.

c) Select least connection as the Scheduling Method.

Edge External AV Media UDP_2.png

8. Expand the Real Servers section.

9. Select ICMP Ping in the Real Server Check Parameters drop-down menu.

Ensure the Forwarding Method is set to Direct Return when adding Real Servers.

5.4 Common to Both without Templates

The Virtual Services listed below are common to both DNS and HLB configurations.

5.4.1 Office Web App Servers Virtual Service

To configure a Virtual Service for Office Web App Servers, follow the steps below:

1. Click the Add New button.

Office Web App Servers Virtual.png

2. Enter a Virtual Address.

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.

6. Click Add This Virtual Service.

Office Web App Servers Virtual_1.png

7. Expand the SSL Properties section and select the following options:

a) Select the Enabled check box.

b) Select the Reencrypt check box.

Office Web App Servers Virtual_2.png

8. Expand the Standard Options section and select the following options:

a) Select Super HTTP and Source IP as the Persistence Mode.

b) Select 30 Minutes as the Persistence Timeout.

c) Select least connection as the Scheduling Method.

d) Enter 1800 in the Idle Connection Timeout field and click Set Idle Timeout.

Office Web App Servers Virtual_3.png

9. Expand the Real Servers section and select the following options:

a) Select HTTPS Protocol in the drop-down menu.

b) Enter /hosting/discovery in the URL field and click Set URL.

c) Select the Use HTTP/1.1 checkbox.

d) Select GET as the HTTP Method.

5.4.2 Director Reverse Proxy HTTP Virtual Service

To configure a Virtual Service for Skype for Business Reverse Proxy HTTP, follow the steps below:

1. Click the Add New button.

Director Reverse Proxy HTTP.png

2. Enter a Virtual Address.

3. Enter 80 in the Port field.

4. Enter a recognisable Service Name, for example SfB 2015 Director Reverse Proxy HTTP.

5. Ensure that TCP is set as the Protocol.

6. Click Add This Virtual Service.

Director Reverse Proxy HTTP_1.png

7. Expand the Standard Options section and select the following options:

a) Ensure the Force L4 checkbox is clear.

b) Ensure the Transparency checkbox is clear.

c) Select None as the Persistence Mode.

d) Select least connection as the Scheduling Method.

e) Enter 1800 in the Idle Connection Timeout field and click Set Idle Timeout.

Director Reverse Proxy HTTP_2.png

8. Expand the Real Servers section and select the following options:

a) Select TCP Connection Only in the drop-down menu.

b) Enter 5061 in the Checked Port field and click Set Check Port.

9. Click the Add New … button to add a Real Server.

Director Reverse Proxy HTTP_3.png

10. Enter the Real Server Address for Director(s).

11. Enter 8080 as the port.

Ensure to not use 80 as the Real Server Port.

12. Click the Add This Real Server button.

5.4.3 Director Reverse Proxy HTTPS Virtual Service

To configure a Virtual Service for Skype for Business Reverse Proxy HTTPS, follow the steps below:

1. Click the Add New button.

Director Reverse Proxy HTTPS.png

2. Enter a Virtual Address.

3. Enter 443 in the Port field.

4. Enter a recognisable Service Name, for example SfB 2015 Director Reverse Proxy HTTPS.

5. Ensure that TCP is set as the Protocol.

6. Click Add This Virtual Service.

7. Expand the SSL Properties section.

Director Reverse Proxy HTTPS_1.png

8. Select the Enabled check box.

9. Select the Reencrypt checkbox.

Director Reverse Proxy HTTPS_2.png

10. Expand the Standard Options section and select the following options:

a) Select None as the Persistence Mode.

b) Select least connection as the Scheduling Method.

c) Enter 1800 as the Idle Connection Timeout value and click Set Idle Timeout.

Director Reverse Proxy HTTP_2.png

11. Expand the Real Servers section and select the following options:

a) Select TCP Connection Only in the drop-down menu.

b) Enter 5061 in the Checked Port field and click Set Check Port.

12. Click the Add New … button to add a Real Server.

Director Reverse Proxy HTTPS_3.png

13. Enter the Real Server Address for Director(s).

14. Enter 4443 as the Port.

Ensure to not use 443 as the Real Server Port.

15. Click the Add This Real Server button.

5.4.4 Front End Reverse Proxy HTTP Virtual Service

To configure a Virtual Service for Skype for Business Reverse Proxy HTTP, follow the steps below:

1. Click the Add New button.

Front End Reverse Proxy HTTP.png

2. Enter a Virtual Address.

3. Enter 80 in the Port field.

4. Enter a recognisable Service Name, for example SfB 2015 Front End Reverse Proxy HTTP.

5. Ensure that TCP is set as the Protocol.

6. Click Add This Virtual Service.

Front End Reverse Proxy HTTP_1.png

7. Expand the Standard Options section and select the following options:

a) Ensure the Force L4 checkbox is clear.

b) Ensure the Transparency checkbox is clear.

c) Select None as the Persistence Mode.

d) Select least connection as the Scheduling Method.

e) Enter 1800 in the Idle Connection Timeout field and click Set Idle Timeout.

Director Reverse Proxy HTTP_2.png

8. Expand the Real Servers section and select the following options:

a) Select TCP Connection Only in the drop-down menu.

b) Enter 5061 in the Checked Port field and click Set Check Port.

9. Click the Add New button to add a Real Server.

Front End Reverse Proxy HTTP_2.png

10. Enter the Real Server Address for the Front End Server(s).

11. Enter 8080 as the port.

Ensure to not use 80 as the Real Server Port.

12. Click the Add This Real Server button.

5.4.5 Front-End Reverse Proxy HTTPS Virtual Service

To configure a Virtual Service for Skype for Business Reverse Proxy HTTPS, follow the steps below:

1. Click the Add New button.

Front End Reverse Proxy HTTPS.png

2. Enter a Virtual Address.

3. Enter 443 in the Port field.

4. Enter a recognisable Service Name, for example SfB 2015 Front-End Reverse Proxy HTTPS.

5. Ensure that TCP is set as the Protocol.

6. Click Add This Virtual Service.

7. Expand the SSL Properties section.

Front End Reverse Proxy HTTPS_1.png

8. Select the Enabled check box.

9. Select the Reencrypt checkbox.

Front End Reverse Proxy HTTPS_2.png

10. Expand the Standard Options section and select the following options:

a) Select None as the Persistence Mode.

b) Select least connection as the Scheduling Method.

c) Enter 1800 as the Idle Connection Timeout and click Set Idle Timeout.

Director Reverse Proxy HTTP_2.png

11. Expand the Real Servers section and select the following options:

a) Select TCP Connection Only in the drop-down menu.

b) Enter 5061 in the Checked Port field and click Set Check Port.

12. Click the Add New button to add a Real Server.

Front End Reverse Proxy HTTPS_3.png

13. Enter the Real Server Address for the Front End Server(s).

14. Enter 4443 as the Port.

Ensure to not use 443 as the Real Server Port.

15. Click the Add This Real Server button.

6 Configuring Skype for Business 2015 VSs with Templates

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 Skype for Business 2015 with the use of Virtual Service templates. 

For an explanation of each of the fields mentioned, refer to the http://kemptechnologies.com/documentation.

6.1 DNS Configuration with Templates

Refer to the sections below for instructions on how to set up the LoadMaster using a DNS only configuration using the KEMP templates.

Microsoft recommends that DNS load balancing is used for Session Initiation Protocol (SIP) traffic. Microsoft also recommends 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 a 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 Virtual Services, refer to the sections below.

6.1.1 Director DNS

The Skype Director DNS template contains two Virtual Services.

Skype Director DNS - WebSvc HTTP

Skype Director DNS - WebSvc HTTPS

6.1.1.1 Deploy the Director DNS template

To add the Virtual Services for Skype Director DNS with the template, follow the steps below:

1. Click the Add New button.

Director DNS.png

2. Enter a Virtual Address.

3. Select the Skype Director DNS template from the Use Template drop-down list.

4. Click Add This Virtual Service

6.1.1.2 Configure Director WebSvc HTTP Virtual Service

To configure the SfB Director WebSvc HTTP Virtual Service, follow the steps below:

1. Select View/Modify Services under Virtual Services in the left-hand navigation.

Director DNS_1.png

2. Click Modify on the Skype Director DNS - WebSvc HTTP Virtual Service.

3. Expand the Real Servers section.

4. Click Add New.

Director DNS_2.png

5. Enter the Real Server Address.

6. Confirm that Port 80 is entered.

7. Click Add This Real Server.

6.1.1.3 Configure Director WebSvc HTTPS Virtual Service

To configure the Skype Director DNS - WebSvc HTTPS Virtual Service, follow the steps below:

1. Select View/Modify Services under Virtual Services in the left-hand navigation.

Director DNS_1.png

2. Click Modify on the Skype Director DNS - WebSvc HTTPS Virtual Service.

3. Expand the Real Servers section.

4. Click Add New.

Director DNS_3.png

5. Enter the Real Server Address.

6. Confirm that Port 443 is entered.

7. Click Add This Real Server.

6.1.2 Front End DNS

The Skype Front End DNS template contains two Virtual Services.

Skype Front End DNS - WebSVC HTTP

Skype Front End DNS - WebSVC HTTPS

6.1.2.1 Deploy Front End DNS template

To add the Virtual Services for Skype for Business Front End with the template, follow the steps below:

1. Click the Add New button.

Front End DNS.png

2. Enter a Virtual Address.

3. Select the Skype Front End DNS template under Use Template.

4. Click Add This Virtual Service

6.1.2.2 Configure Front End WebSvc HTTP Virtual Service

To configure the Skype Front End DNS - WebSVC HTTP Virtual Service, follow the steps below:

1. Select View/Modify Services under Virtual Services in the left-hand navigation.

Front End DNS_1.png

2. Click Modify on the Skype Front End DNS - WebSVC HTTP Virtual Service.

3. Expand the Real Servers section.

4. Click Add New.

Director DNS_2.png

5. Enter the Real Server Address.

6. Confirm that Port 80 is entered.

7. Click Add This Real Server.

6.1.2.3 Configure Front End WebSvc HTTPS Virtual Service

To configure the Skype Front End DNS - WebSVC HTTPS Virtual Service, follow the steps below:

1. Select View/Modify Services under Virtual Services in the left-hand navigation.

Front End DNS_2.png

2. Click Modify on the Skype Front End DNS - WebSVC HTTPS Virtual Service.

3. Expand the Real Servers section.

4. Click Add New

Director DNS_3.png

5. Enter the Real Server Address.

6. Confirm that Port 443 is entered.

7. Click Add This Real Server.

6.2 HLB Only Configuration with Templates

The HLB only configuration instructions using the KEMP Templates are below.

6.2.1 Director HLB Only

The Skype Director HLB Only template contains three Virtual Services:

Skype Director HLB Only - WebSvc HTTP

Skype Director HLB Only - WebSvc HTTPS

Skype Director HLB Only - SIP

6.2.1.1 Deploy Director HLB Only template

To add the Virtual Services for Skype Director with the template, follow the steps below:

1. Click the Add New button.

Director HLB Only.png

2. Enter a Virtual Address.

3. Select the Skype Director HLB Only template in the Use Template drop-down list.

4. Click Add This Virtual Service

6.2.1.2 Configure Director WebSvc HTTP Virtual Service

To configure the Skype Director HLB Only - WebSvc HTTP Virtual Service, follow the steps below:

1. Select View/Modify Services under Virtual Services in the left-hand navigation.

Director HLB Only_1.png

2. Click Modify on the Skype Director HLB Only - WebSvc HTTP Virtual Service.

3. Expand the Real Servers section.

4. Click Add New

Director DNS_2.png

5. Enter the Real Server Address.

6. Confirm that Port 80 is entered.

7. Click Add This Real Server.

6.2.1.3 Configure Director WebSvc HTTPS Virtual Service

To configure the Skype Director HLB Only - WebSvc HTTPS Virtual Service, follow the steps below:

1. Select View/Modify Services under Virtual Services in the left-hand navigation.

Director HLB Only_1.png

2. Click Modify on the Skype Director HLB Only - WebSvc HTTPS Virtual Service.

3. Expand the Real Servers section.

4. Click Add New.

Director HLB Only_2.png

5. Enter the Real Server Address.

6. Confirm that Port 443 is entered.

7. Click Add This Real Server.

6.2.1.4 Configure Director SIP Virtual Service

To configure the Skype Director HLB Only - SIP Virtual Service, follow the steps below:

1. Select View/Modify Services under Virtual Services in the left-hand navigation.

Director HLB Only_1.png

2. Click Modify on the Skype Director HLB Only - SIP Virtual Service.

3. Expand Real Servers section.

4. Click Add New.

Director HLB Only_3.png

5. Enter the Real Server Address.

6. Confirm that Port 5061 is entered.

7. Click Add This Real Server.

6.2.2 Front End HLB Only

The Skype Front End HLB Only template contains four Virtual Services:

Skype Front End HLB Only - WebSvc HTTP

Skype Front End HLB Only - WebSvc HTTPS

Skype Front End HLB Only - SIP

Skype Front End HLB Only - DCOM

6.2.2.1 Deploy Front End HLB Only template

To add the Virtual Services for Skype Front End with the template, follow the steps below:

1. Click the Add New button.

Front End HLB Only.png

2. Enter a Virtual Address.

3. Select Skype Front End HLB Only in the Use Template drop-down list.

4. Click Add This Virtual Service. 

6.2.2.2 Configure Front End WebSvc HTTP Virtual Service

To configure the Skype Director HLB Only - WebSvc HTTP Virtual Service, follow the steps below:

1. Select View/Modify Services under Virtual Services in the left-hand navigation.

Front End HLB Only_1.png

2. Click Modify on the Skype Director HLB Only - WebSvc HTTP Virtual Service.

3. Expand the Real Servers section.

4. Click Add New.

Director DNS_2.png

5. Enter the Real Server Address.

6. Confirm that Port 80 is entered.

7. Click Add This Real Server.

6.2.2.3 Configure the Front End WebSvc HTTPS Virtual Service

To configure the Skype Front End HLB Only - WebSvc HTTPS Virtual Service, follow the steps below:

1. Select View/Modify Services under Virtual Services in the left-hand navigation.

Front End HLB Only_1.png

2. Click Modify on the Skype Front End HLB Only - WebSvc HTTPS Virtual Service.

Front End HLB Only_2.png

3. Expand the Real Servers section.

4. Click Add New.

5. Enter the Real Server Address.

6. Confirm that Port 443 is entered.

7. Click Add This Real Server.

6.2.2.4 Configure the Front End DCOM Virtual Service

To configure the Skype Front End HLB Only - DCOM Virtual Service, follow the steps below:

1. Select View/Modify Services under Virtual Services in the left-hand navigation.

Front End HLB Only_1.png

2. Click Modify on the Skype Front End HLB Only - DCOM Virtual Service.

3. Expand the Real Servers section.

4. Click Add New.

Front End HLB Only_3.png

5. Enter the Real Server Address.

6. Confirm that Port 135 is entered.

7. Click Add This Real Server.

6.2.2.5 Configure the Front End SIP Virtual Service

To configure the Skype Front End HLB Only - SIP Virtual Service, follow the steps below:

1. Select View/Modify Services under Virtual Services in the left-hand navigation.

Front End HLB Only_1.png

2. Click Modify on the Skype Front End HLB Only - SIP Virtual Service.

Front End HLB Only_4.png

3. Expand the Real Servers section.

4. Click Add New.

5. Enter the Real Server Address.

6. Confirm that Port 5061 is entered.

7. Click Add This Real Server.

6.2.3 Mediation Virtual Service

DNS-only load balancing is sufficient for Mediation pools. If using the LoadMaster instead of DNS, load balance only TCP port 5070.

To configure a Virtual Service for Skype Mediation with the template, follow the steps below:

1. Click the Add New button.

Mediation Virtual Service_1_1.png

2. Enter a Virtual Address.

3. Select Skype Mediation HLB Only in the Use Template drop-down list.

4. Click Add This Virtual Service.

Mediation Virtual Service_1_2.png

5. Expand the Real Servers section.

6. Click Add New.

7. Enter the Real Server Address.

8. Confirm that Port 5070 is entered.

9. Click Add This Real Server.

6.2.4 Internal Edge HLB Only

The Skype Edge Internal HLB Only template contains three Virtual Services:

Skype Edge Internal HLB Only - AV Media TCP

Skype Edge Internal HLB Only - AV Media UDP

Skype Edge Internal HLB Only - SIP

6.2.4.1 Deploy Internal Edge HLB template

To add the Virtual Services for Skype for Business Director with Template, follow the steps below:

1. Click the Add New button.

Internal Edge HLB Only.png

2. Enter a Virtual Address.

3. Select the Skype Edge Internal HLB Only template in the Use Template drop-down list.

4. Click Add This Virtual Service

6.2.4.2 Configure Internal Edge AV Media TCP Virtual Service

To configure the Skype Edge Internal HLB Only - AV Media TCP Virtual Service, follow the steps below:

1. Select View/Modify Services under Virtual Services in the left.e -hand navigation.

Internal Edge HLB Only_1.png

2. Click Modify on the Skype Edge Internal HLB Only - AV Media TCP Virtual Service.

Internal Edge HLB Only_2.png

3. Expand the Real Servers section.

4. Click Add New.

5. Enter the Real Server Address.

6. Confirm that Port 443 is entered.

7. Click Add This Real Server.

6.2.4.3 Configure the Internal Edge AV Media UDP Virtual Service

To configure the Skype Edge Internal HLB Only - AV Media UDP Virtual Service, follow the steps below:

1. Select View/Modify Services under Virtual Services in the left-hand navigation.

Internal Edge HLB Only_1.png

2. Click Modify on the Skype Edge Internal HLB Only - AV Media UDP Virtual Service.

Internal Edge HLB Only_3.png

3. Expand Real Servers section.

4. Click Add New.

5. Enter the Real Server Address.

6. Confirm that Port 3478 is entered.

7. Click Add This Real Server.

6.2.4.4 Configure Internal Edge SIP Virtual Service

To configure the Skype Edge Internal HLB Only - SIP Virtual Service, follow the steps below:

1. Select View/Modify Services under Virtual Services in the left-hand navigation.

Internal Edge HLB Only_1.png

2. Click Modify on the Skype Edge Internal HLB Only - SIP Virtual Service.

3. Expand the Real Servers section.

4. Click Add New

Internal Edge HLB Only_4.png

5. Enter the Real Server Address.

6. Confirm that Port 5061 is entered.

7. Click Add This Real Server.

6.3 Configure External Edge Virtual Services with Templates

To configure the various Edge Virtual Services with Templates, 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.

6.3.1 Edge External HLB Only

The Skype Edge External HLB Only template contains three Virtual Services:

Skype Edge External HLB Only - SIP

Skype Edge External HLB Only - SIP Federation

Skype Edge External HLB Only - XMPP

6.3.1.1 Deploy the External Edge HLB Template

To add the Virtual Services for Skype Edge External HLB Only with the template, follow the steps below:

1. Click the Add New button.

Edge External HLB Only.png

2. Enter a Virtual Address.

3. Select the Skype Edge External HLB Only template in the Use Template drop-down list.

4. Click Add This Virtual Service

6.3.1.2 Configure the External SIP Virtual Service

To configure the SfB Edge External SIP Virtual Service, follow the steps below:

1. Select View/Modify Services under Virtual Services in the left-hand navigation.

Edge External HLB Only_1.png

2. Click Modify on the SfB Edge External SIP Virtual Service.

Edge External HLB Only_2.png

3. Expand the Real Servers section.

4. Click Add New.

5. Enter the Real Server Address.

6. Confirm that Port 443 is entered.

7. Click Add This Real Server.

6.3.1.3 Configure the External SIP Federation Virtual Service

To configure the Skype Edge External HLB Only - SIP Federation Virtual Service, follow the steps below:

1. Select View/Modify Services under Virtual Services in the left-hand navigation.

Edge External HLB Only_1.png

2. Click Modify on the Skype Edge External HLB Only - SIP Federation Virtual Service.

Edge External HLB Only_3.png

3. Expand the Real Servers section.

4. Click Add New.

5. Enter the Real Server Address.

6. Confirm that Port 5061 is entered.

7. Click Add This Real Server.

6.3.1.4 Configure the External XMPP Virtual Service

To configure the Skype Edge External HLB Only - XMPP Virtual Service, follow the steps below:

1. Select View/Modify Services under Virtual Services in the left hand navigation.

Edge External HLB Only_1.png

2. Click Modify on the Skype Edge External HLB Only - XMPP Virtual Service.

Edge External HLB Only_4.png

3. Expand Real Servers section.

4. Click Add New.

5. Enter the Real Server Address.

6. Confirm that Port 5269 is entered.

7. Click Add This Real Server.

6.3.2 Edge External Conferencing

To configure a Virtual Service for Skype Edge External Conferencing with the template, follow the steps below:

1. Click the Add New button.

Edge External Conferencing_1_1.png

2. Enter a Virtual Address.

3. Select the Skype Edge External Conferencing template in the Use Template drop-down list.

4. Click Add This Virtual Service.

5. Expand the Real Servers section.

6. Click Add New.

Edge External Conferencing_1_2.png

7. Enter the Real Server Address.

8. Confirm that Port 443 is entered.

9. Click Add This Real Server.

6.3.3 Edge External AV HLB Only

The Skype Edge External AV HLB Only template contains two Virtual Services:

Skype Edge External AV HLB Only - Media TCP

Skype Edge External AV HLB Only - Media UDP

6.3.3.1 Deploy the Edge External AV HLB Template

To add the Virtual Services for Skype Edge External AV with the template, follow the steps below:

1. Click the Add New button.

Edge External AV HLB Only.png

2. Enter a Virtual Address.

3. Select the Skype Edge External AV HLB Only template in the Use Template drop-down list.

4. Click Add This Virtual Service

6.3.3.2 Configure the Edge External AV Media TCP Virtual Service

To configure the Skype Edge External AV HLB Only - Media TCP Virtual Service, follow the steps below:

1. Select View/Modify Services under Virtual Services in the left hand navigation.

Edge External AV HLB Only_1.png

2. Click Modify on the Skype Edge External AV HLB Only - Media TCP Virtual Service.

Edge External AV HLB Only_2.png

3. Expand the Real Servers section.

4. Click Add New.

5. Enter the Real Server Address.

6. Confirm that Port 443 is entered.

7. Click Add This Real Server.

6.3.3.3 Configure the Edge External AV Media UDP Virtual Service

To configure the Skype Edge Internal HLB Only - AV Media UDP Virtual Service, follow the steps below:

1. Select View/Modify Services under Virtual Services in the left-hand navigation.

Edge External AV HLB Only_1.png

2. Click Modify on the Skype Edge Internal HLB Only - AV Media UDP Virtual Service.

3. Expand the Real Servers section.

4. Click Add New.

Edge External AV HLB Only_3.png

5. Enter the Real Server Address.

6. Confirm that Port 3478 is entered.

7. Set the Forwarding Method to Direct Return.

8. Click Add This Real Server.

Ensure the Forwarding Method is set to Direct Return when adding the Real Servers.

6.4 Common to Both with Templates

The Virtual Services listed below are common to both DNS and HLB configurations.

6.4.1 Office Web App Servers Virtual Service

To configure a Virtual Service for Office Web App Servers with the template, follow the steps below:

1. Click the Add New button.

Office Web App Servers Virtual_1_1.png

2. Enter a Virtual Address.

3. Select Skype Office Web App Servers in.e the Use Template drop-down list.

4. Click Add This Virtual Service.

Office Web App Servers Virtual_1_2.png

5. Select a valid certificate which was previously imported and click the > button to assign the certificate.

6. Click Set Certificates.

7. Expand the Real Servers section.

8. Click Add New.

Office Web App Servers Virtual_1_3.png

9. Enter the Real Server Address.

10. Confirm that Port 443 is entered.

11. Click Add This Real Server.

6.4.2 Director Reverse Proxy

The Skype Director Reverse Proxy template contains two Virtual Services:

Skype Director Reverse Proxy - HTTP

Skype Director Reverse Proxy - HTTPS

6.4.2.1 Deploy the Director Reverse Proxy Template

To add the Virtual Services for Skype for Business Director with the template, follow the steps below:

1. Click the Add New button.

Director Reverse Proxy.png

2. Enter a Virtual Address.

3. Select the Skype Director Reverse Proxy template in the Use Template drop-down list.

4. Click Add This Virtual Service

6.4.2.2 Configure Director Reverse Proxy HTTP Virtual Service

To configure the Skype Director Reverse Proxy - HTTP Virtual Service, follow the steps below:

1. Select View/Modify Services under Virtual Services in the left-hand navigation.

Director Reverse Proxy_1.png

2. Click Modify on the Skype Director Reverse Proxy - HTTP Virtual Service.

Director Reverse Proxy_2.png

3. Expand the Real Servers section.

4. Click Add New.

5. Enter the Real Server Address.

6. Confirm that Port 8080 is entered.

7. Click Add This Real Server.

Ensure to not use 80 as the Real Server Port.

6.4.2.3 Configure the Director Reverse Proxy HTTPS Virtual Service

To configure the Skype Director Reverse Proxy - HTTPS Virtual Service, follow the steps below:

1. Select View/Modify Services under Virtual Services in the left-hand navigation.

Director Reverse Proxy_1.png

2. Click Modify on the Skype Director Reverse Proxy - HTTPS Virtual Service.

3. Expand the SSL Properties section.

Director Reverse Proxy_3.png

4. Select a valid certificate which was previously imported and click the > button to assign the certificate.

5. Click Set Certificates.

6. Expand the Real Servers section.

7. Click Add New.

Director Reverse Proxy_4.png

8. Enter the Real Server Address.

9. Confirm that Port 4443 is entered.

10. Click Add This Real Server.

Ensure to not use 443 as the Real Server Port.

6.4.3 Front End Reverse Proxy

The Skype for Business 2015 Front End Reverse Proxy template contains two Virtual Services:

Skype Front End Reverse Proxy - HTTP

Skype Front End Reverse Proxy - HTTPS

6.4.3.1 Deploy the Front End Reverse Proxy Template

To add the Virtual Services for Skype Front End Reverse Proxy with the template, follow the steps below:

1. Click the Add New button.

Front End Reverse Proxy.png

2. Enter a Virtual Address.

3. Select the Skype For Business 2015 Front End Reverse Proxy template in the Use Template drop-down list.

4. Click Add This Virtual Service

6.4.3.2 Configure the Front End Reverse Proxy HTTP Virtual Service

To configure the Skype Front End Reverse Proxy - HTTP Virtual Service, follow the steps below:

1. Select View/Modify Services under Virtual Services in the left-hand navigation.

Front End Reverse Proxy_1.png

2. Click Modify on the Skype Front End Reverse Proxy - HTTP Virtual Service.

Front End Reverse Proxy_2.png

3. Expand the Real Servers section.

4. Click Add New.

5. Enter the Real Server Address.

6. Confirm that Port 8080 is entered.

7. Click Add This Real Server.

Ensure to not use 80 as the Real Server Port.

6.4.3.3 Configure the Front End Reverse Proxy HTTPS Virtual Service

To configure the Skype Front End Reverse Proxy - HTTPS Virtual Service, follow the steps below:

1. Select View/Modify Services under Virtual Services in the left-hand navigation.

Front End Reverse Proxy_1.png

2. Click Modify on the Skype Front End Reverse Proxy - HTTPS Virtual Service.

Front End Reverse Proxy_3.png

3. Select a valid certificate which was previously imported and click the > button to assign the certificate.

4. Click Set Certificates.

5. Expand the Real Servers section.

6. Click Add New.

Front End Reverse Proxy_4.png

7. Enter the Real Server Address.

8. Confirm that Port 4443 is entered.

9. Click Add This Real Server.

Ensure to not use 443 as the Real Server Port.

7 Additional Information

Some additional information that may be of use is contained within the sections below.

7.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.

7.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

7.3 Hardware Load Balancing

If hardware load balancing is being used, a list of the ports that must be open can be found here: http://technet.microsoft.com/en-us/library/gg398833.aspx

Hardware load balancing Edge servers requires N+1 Public IP addresses.

Refer to the link below for further information on hardware load balancing:

https://technet.microsoft.com/en-us/library/gg615011.aspx

References

The following sources are referred to in this document:

KEMP Technologies website

www.kemptechnologies.com

KEMP Technologies Documentation page

http://kemptechnologies.com/documentation

Web User Interface (WUI), Configuration Guide

http://kemptechnologies.com/documentation

Virtual Services and Templates, Feature Description

http://kemptechnologies.com/documentation

Ports and Protocols for Internal Servers

1. http://technet.microsoft.com/en-us/library/gg398833.aspx

Port Summary - Scaled Consolidated Edge with Hardware Load Balancers

2. http://technet.microsoft.com/en-us/library/gg398739.aspx

Scaled Consolidated Edge with Hardware Load Balancers

3. http://technet.microsoft.com/en-us/library/gg398478.aspx

Document History

Date Change Reason for Change Version Resp.

Mar 2016

Minor updates

Enhancements made

7.0

LB

Oct 2016

Release updates

Updates for 7.2.36

8.0

POC

Jan 2017

Minor updates

Enhancements made

9.0

LB

July 2017 Release updates Updates for 7.2.39 10.0 CMC

 

Was this article helpful?

0 out of 0 found this helpful

Comments