Deploying the BIG-IP System with Microsoft Lync Server 2010 and 2013 for Site Resiliency.pdf
免费下载
Deploying the BIG-IP System with Microsoft
Lync Server 2010 and 2013 for Site Resiliency
Welcome to the F5 and Microsoft
®
Lync Server
®
Deployment Guide for site resiliency. This guide
contains instructions on configuring F5 Global Traffic Manager (GTM) and BIG-IP Local Traffic
Manager (LTM) modules to support site resiliency for Microsoft Lync Server 2010 and 2013.
For more information on the F5 devices in this guide, see http://www.f5.com/products/big-ip/.
You can also visit the Microsoft page of F5’s online developer community, DevCentral, for
Microsoft forums, solutions, blogs and more: http://devcentral.f5.com/Microsoft/.
Why F5
Microsoft Lync Server supports DNS Load Balancing for distributing non-HTTP based connections
to Lync Front End, Edge, and Mediation Servers. However, there are advantages to using the BIG-
IP system to load balance these connections in certain scenarios:
•
You are using legacy clients or servers (Office Communication Server (OCS), pre-2010 SP1
Exchange Unified Messaging).
• You are federated with an organization using legacy clients or servers (see examples in the
previous bullet) or public IM services/XMPP.
• You want to use intelligent logic (such as pool member status, least connection load
balancing, and more) to make the initial client connection to the Front End, Edge, or
Mediation pool.
• You want to use the F5 iApp template to deploy Lync Server rapidly.
• You use F5 GTM in your environment and would like to take advantage of F5’s Lync Site
Resiliency solution.
Advantages
•
The BIG-IP system does not interfere with Lync client registration/deregistration.
• Disabling BIG-IP system pool members is effectively the same as (and can be used in
conjunction with) Lync Server Draining.
•
The BIG-IP is a certified ICSA firewall, providing security over deploying your Lync Servers
directly on the Internet.
•
Even if you are using DNS Load Balancing, Microsoft requires hardware load balancing for
Lync Web Services.
What’s inside:
2 Configuration example
5 Configuring the BIG-IP
LTM using the Lync
2010 iApp
6 Configuring the BIG-IP
GTM
11 Creating a Distributed
Application for Lync
12 Document Revision
History
IMPORTANT: This guide has been archived. While the content in this guide is still valid for the
products and version listed in the document, it is no longer being updated and may
refer to F5 or 3rd party products or versions that have reached end-of-life or
end-of-support. See https://support.f5.com/csp/article/K11163 for more information.
Archived
DEPLOYMENT GUIDE
Microsoft Lync Server
2
Products and versions tested
Product Versions
BIG-IP system 11.0, 11.0.1, 11.1, 11. 2, 11. 3, 11.4
Microsoft Lync Server 2010 and 2013
Important: Make sure you are using the most recent version of this deployment guide, available at http://www.f5.com/pdf/deployment-
guides/lync-2010-site-resiliency-dg.pdf.
To provide feedback on this deployment guide or other F5 solution documents, contact us at solutionsfeedback@f5.com.
Prerequisites and configuration notes
The following are general prerequisites and configuration notes for this guide:
h For this deployment guide, the BIG-IP system must be running version 11.0 or later. The configuration described in this guide does
not apply to previous versions.
h This document is written with the assumption that you are familiar with both F5 devices and Microsoft Lync Server. For more
information on configuring these devices, consult the appropriate documentation.
h This guide assumes that you have configured the Lync Server Simple URLs in the following format:
» http://meet.mydomain.com
» http://dialin.mydomain.com
h We strongly recommend performing the BIG-IP LTM portion of this configuration using the downloadable iApp template, as
described in Downloading, importing, and running the Lync Server iApp on page 5.
h You must have your internal name resolution configured properly. For example, every Lync Edge server needs to be able to resolve
every Front End and Director server, and vice versa. Additionally, the FQDNs of all Lync Server pools (Edge, Front End, and Director)
must resolve to the IP addresses of the corresponding BIG-IP LTM virtual servers.
h You must have a minimum of two BIG-IP GTM devices to perform the configuration in this guide.
Configuration example
In this guide, we configure the BIG-IP GTM with two data centers. Lync Server 2010 is configured with a “stretched” VLAN where all Lync
Front End and Director Servers reside on the same layer 2 network, while Lync Server 2013 is configured with paired Front End pools for
each data center (for more information on pairing pools, see http://technet.microsoft.com/en-us/library/jj205293.aspx).
BIG-IP GTM uses topology load balancing to direct internal clients to Lync Front End Server resources, and external clients to Edge Server
and Reverse Proxy resources. The BIG-IP system monitors the availability of the internal Lync services, and marks the external services down
should the health check fail. Resiliency for file shares and Microsoft SQL Server instances are beyond the scope of this document.
Logical configuration examples with traffic flow callouts for internal and external clients are on the following pages.
Archived
of 12
免费下载
【版权声明】本文为墨天轮用户原创内容，转载时必须标注文档的来源（墨天轮），文档链接，文档作者等基本信息，否则作者和墨天轮有权追究责任。如果您发现墨天轮中有涉嫌抄袭或者侵权的内容，欢迎发送邮件至：contact@modb.pro进行举报，并提供相关证据，一经查实，墨天轮将立刻删除相关内容。
下载排行榜
评论