Reference Architecture Microsoft Lync Server 2013 on Dell PowerEdge R630

Reference Architecture Microsoft Lync Server 2013 on Dell PowerEdge R630 A Dell reference architecture for Lync Server 2013 solution on a central site and branch office with 5000 users Dell Global Solutions Engineering June 2015 A Dell Reference Architecture

TIS WITE PAPER IS FOR INFORMATIONAL PURPOSES ONLY, AND MAY CONTAIN TYPOGRAPICAL ERRORS AND TECNICAL INACCURACIES. TE CONTENT IS PROVIDED AS IS, WITOUT EXPRESS OR IMPLIED WARRANTIES OF ANY KIND. Copyright 2015 Dell Inc. All rights reserved. This product is protected by U.S. and international copyright and intellectual property laws. Dell and the Dell logo are trademarks of Dell Inc. in the United States and/or other jurisdictions. All other marks and names mentioned herein may be trademarks of their respective companies. 2 Reference Architecture Microsoft Lync Server 2013 on Dell PowerEdge R630

Table of contents Executive summary... 5 1 Scope... 6 1.1 Audience... 6 2 Introduction... 7 2.1 Solution components... 7 2.1.1 Dell PowerEdge R630... 7 2.1.2 Dell Networking... 8 2.1.3 Dell Networking wireless devices... 8 2.1.4 Client devices... 9 2.1.5 Microsoft Lync Server 2013... 9 2.1.6 Lync 2013 Enterprise Edition Pool... 11 2.2 Design considerations... 11 2.2.1 igh Availability... 11 2.2.2 Application performance... 11 2.2.3 Resource consolidation... 12 3 Solution reference architecture... 13 3.1 Lync Server core architecture... 14 3.1.1 Network architecture... 16 3.1.2 Storage for Lync, SQL, and ypervisor... 17 3.1.3 Storage for yper-v osts... 17 3.2 Lync Server Edge architecture... 18 3.2.1 Edge Network architecture... 20 3.2.2 Reverse Proxy... 21 3.2.3 Best Practices for Edge and Reverse Proxy ost... 21 3.3 Enterprise Voice Connectivity... 22 3.4 Branch Office Connectivity... 23 3.5 End-user connectivity... 24 4 Technical specifications... 25 4.1 Virtual Machine specifications... 25 4.2 ardware specifications... 27 5 Verification... 30 3 Reference Architecture Microsoft Lync Server 2013 on Dell PowerEdge R630

6 Conclusion... 32 A Additional resources... 33 4 Reference Architecture Microsoft Lync Server 2013 on Dell PowerEdge R630

Executive summary Unified communications (UC) provides an efficient, flexible and effective working experience while helping organizations reduce operational and capital costs. UC delivers real-time communication between peers local, remote or geographically dispersed and enables instant and direct communication with partners, suppliers, and customers. Furthermore, all of these capabilities are provided while reducing administrative, telephony, travel, and IT cost compared to traditional communications solutions. The Dell TM UC solutions provide instant messaging, presence, audio/video conferencing, web conferencing, and telephony integration (enterprise voice). This fully featured solution integrates Dell products with Microsoft Lync Server 2013 software. The ecosystem consists of Dell PowerEdge servers, Dell Networking switches and wireless, third-party voice gateways, and client devices such as Dell Latitude TM laptops, Dell Venue Pro TM tablets and Dell XPS TM tablets and Ultrabooks TM. The UC solution leverages server virtualization offered by Microsoft Windows Server 2012 R2 with yper-v to effectively consolidate and utilize resources. Furthermore, the architecture is designed for high availability (A) and functionality based upon the failure of a server, network or voice gateway. This design enables IT administrators to perform maintenance tasks without incurring Lync application downtime. Lync Server implementations can integrate with existing PBX systems or replace aging PBX systems to offer a complete UC experience, including telephony integration through the Lync clients. This type of implementation may also lead to an enhanced video conferencing experience as well given the integration of the Lync stack and all of the capabilities. Lync also complies with legal requirements of specific countries by enabling Location-Based Routing. To assist with design and implementation of a complete UC solution, the following reference architecture describes the resilient Lync Server infrastructure topology with a variety of the available modalities. The architecture is sized according to Microsoft s best practices. The Microsoft Lync Stress and Performance tool was used to generate real-time workloads on Lync servers to validate the design. This reference architecture is divided into multiple sections: Section 2 provides a quick introduction to the solution components that include Lync Server 2013, PowerEdge servers, and Dell Networking and client devices. This section briefly describes the major changes in the Lync Server 2013 architecture and discusses the design principles that dictated the architecture. Section 3 details the end-to-end design and implementation of the UC solution. For simplicity, this section divides the solution into five portions and describes each of them in detail. Section 4 provides the technical specifications, including all the virtual and physical components that make up the complete solution. Section 5 an overview of the verification process that was performed to ensure that the solution met the design principles. 5 Reference Architecture Microsoft Lync Server 2013 on Dell PowerEdge R630

1 Scope This reference architecture describes the implementation of Lync Server 2013 on PowerEdge R630 servers. The design is based on infrastructure design principles, which include A, application best practices, hardware abstraction and resource consolidation. A sample implementation for 5,000 users is given for reference. 1.1 Audience This reference architecture is intended for IT professionals and administrators interested in designing and deploying end-to-end, real-time collaboration solutions using Lync Server 2013 on Dell servers and switches, third-party gateways/session Border Controllers (SBCs), and associated client devices. This reference architecture provides an overview of the important solution components. owever, the reader is expected to have an understanding of Lync Server 2013 and voice gateways. Familiarity with Windows Server 2012 R2 and yper-v virtualization will also aid the reader s comprehension of the content in this document. 6 Reference Architecture Microsoft Lync Server 2013 on Dell PowerEdge R630

2 Introduction Dell provides a validated end-to-end UC solution, which consists of a Lync Server, PowerEdge servers, storage, networking, client devices, monitoring/reporting tools and partner devices such as Public Switched Telephone Network (PSTN) gateway, SBC, load balancer and Lync phones. PowerEdge R630 servers minimize the overall hardware cost and datacenter footprint by enabling more virtual machines to meet application requirements. Dell Unified Communications and Collaboration Consulting Services customize the UC solution for each customer as per their business and technical requirements, which provides better return on investment. Dell ardware and services for UC solution enable the organizations to have instant communication from any device which is optimized for Lync. This reference architecture is built on PowerEdge R630 servers and incorporates Windows Server 2012 R2 with yper-v and Lync Server 2013. 2.1 Solution components The reference architecture described in this paper employs PowerEdge R630 servers for virtualizing Lync server roles and other solution components such as SBC and load balancer. Dell Networking N4000 series switches are used to connect physical servers and other devices including Local Area Network (LAN). 2.1.1 Dell PowerEdge R630 PowerEdge R630 server is a 1U rack server supporting up to 36 processing cores and up to 768 GB of physical memory. The compute capacity makes PowerEdge R630 server a highly suitable platform for virtualizing enterprise applications such as Lync, which perform compute-intensive tasks. Supported network controllers provide the LAN and SAN connectivity required for the virtualized infrastructure and applications. The enhanced systems management capabilities make it easier to deploy, manage, and monitor the server infrastructure. Table 1 describes the components supported in a PowerEdge R630 server: Table 1 PowerEdge R630 server high-level technical specifications Components CPU Memory Networking Form Factor PCIe slots Specifications Up to 2 Intel E5-2600v3 family processors 24 DIMMs; up to 768GB QLogic or Intel 1GigE or 10GbE NDC Optional QLogic or Intel 1GigE or 10GbE PCIe Add-on NICs 1U rack 3 slots: Two x16 slots with x16 bandwidth, half-height, half-length One x16 slot with x8 bandwidth, half-height, half-length OR 7 Reference Architecture Microsoft Lync Server 2013 on Dell PowerEdge R630

2 slots: One x16 slot with x16 bandwidth, full-height, 3/4 length One x16 slot with x16 bandwidth (or x8 with one processor only), half-height, half-length Internal Storage Up to 28 TB; 10 x 2.5-inch SAS or SATA drives (with no CD/DVD drive) Up to 9.6 TB; 8 x 2.5-inch SAS or SATA drives (with CD/DVD drive) Up to 22.5 TB; 24 x 1.8-inch SAS or SATA drives (with no CD/DVD drive) Storage RAID Systems Management PowerEdge RAID Controller 330 PowerEdge RAID Controller 730 PowerEdge RAID Controller 730P PowerEdge RAID Controller 830 PowerEdge S110 On-board Controller idrac8 Express or idrac8 Enterprise 2.1.2 Dell Networking This reference architecture uses Dell Networking N2024 1 GbE top-of-rack (ToR) switch purpose-built for applications in high-performance data center and computing environments. Leveraging a non-blocking, cut-through switching architecture, the N2000 series delivers line-rate L2 and L3 forwarding capacity with ultra-low latency to maximize network performance. The N2024 switch provides 24 RJ45 10/100/1000Mb auto-sensing ports, as well as two 10GbE SFP+ uplinks, to conserve valuable rack space and simplify the migration to 10 Gbps in the data center core. In this solution architecture, two N2024 switches are deployed as LAN switches. For client devices (access switches), Dell Networking 7048P Power over Ethernet (PoE) switches can be used. These switches provide 30.8 W per port for Lync clients, including the Polycom CX600 IP phones, and do not require an external power source. With regard to this particular reference architecture, it should be noted that we have assumed that the necessary networking best practices have been used to support the protocols required to meet Quality of Experience (QoE) expectations. Also, the necessary Quality of Service (QoS) policy was implemented to support both the networking traffic and the connectivity required for this workload based on Dell networking best practices in conjunction with Microsoft s recommended best practices for the networking components. 2.1.3 Dell Networking wireless devices For Lync 2013 real-time workloads, Dell recommends Dell Networking W Series wireless controllers and access points (PowerConnect W). The W-Series 3200 controller can support up to 2,048 users and can manage 32 LAN access points (APs) and 128 remote APs. The AP chosen for this configuration is W-AP135, 8 Reference Architecture Microsoft Lync Server 2013 on Dell PowerEdge R630

which can deliver wireline-like data rates of up to 450 Mbps. W-AP135 can handle numerous audio-video sessions simultaneously, assuming each audio stream is 65 Kbps and each video stream is 500 Kbps. owever, the performance and quality of experience (QoE) of Lync Server must be monitored, and these throughput values should not be used as the only metric to determine quality. 2.1.4 Client devices This enterprise VoIP implementation is an end-to-end UC solution that includes client hardware components and data center hardware. Dell has a rich product portfolio of client devices that can be used to run the Lync end user client. The Latitude, XPS, Dell Inspiron, Dell Precision and Venue Pro product lines are suited to run the Lync client software/app. Visit the Dell Laptops, Tablets and Workstations site to browse Dell client products suited for the workplace. The Polycom CX300, CX500 and CX600 phones are third-party clients that can be used as Lync end points. For a complete list of client devices available for Lync, contact your Dell sales representative. 2.1.5 Microsoft Lync Server 2013 Lync Server enables instant messaging, presence, audio and video conferencing, web conferencing and voice interoperability. Lync Server provides different modalities to users, including: IM and Presence: Enables users to view the status of other Lync users and update current status (Available, Busy, Away, etc.). Conferencing with multiple users is also supported. Audio Conferencing: Enables users to communicate with other Lync users using SIP and Real-time Transport Protocol (RTP). Audio conferencing using Lync is cost-effective for enterprises with employees spread across geographical locations as users can communicate using the enterprise data network instead of expensive long-distance telephony. Video and Web Conferencing: Enables users to run meetings using 1:1 and group video conferences, including optional recording and desktop and application sharing. These workloads are available with Lync Server and can be leveraged for day-to-day tasks in the enterprise. Voice Interoperability with PSTN: Enables users to communicate with telephone users within and outside the enterprise using Lync Mediation Server, which can be collocated on the Front End Server. Lync Mediation Server works with a SIP trunk or telephony device (IP-PBX/gateway). The following are the new and existing server roles of Lync Server 2013: Front End Server: The Front End Server role manages Lync client authentication, instant messaging, web conferencing, audio/video conferencing and user presence updates. It is the central component of the Lync Server topology. The Front End Server has a local database that stores user data and topology information. This role can be deployed in an Enterprise Edition pool. In Lync Server 2013, the Archiving and Monitoring role is combined with the Front End Server role. The Archiving and Monitoring role can be used to monitor user statistics and QoE within the Lync environment and archive conference content and instant messages for future audits. The Archiving and Monitoring role also allows IT administrators to access call detail records and QoE statistics for Lync communication. 9 Reference Architecture Microsoft Lync Server 2013 on Dell PowerEdge R630

Back End Server: Microsoft SQL Server serves as the backend for Enterprise Edition servers and is also responsible for Archiving and Monitoring and Persistent Chat roles. SQL Server maintains a copy of the topology information, user contact lists, archiving and monitoring databases and logs, and other data. Lync Server supports SQL mirroring with primary and secondary copies. SQL mirroring or SQL clustering can be used to provide high availability for the SQL databases. Mediation Server: The Mediation Server role provides Enterprise Voice capabilities and manages the communication between the Front End Server roles and media gateways or SBCs. This role can be collocated with the Front End Server role. The Mediation Server role facilitates traffic encryption/decryption and transcoding by using Transport Layer Security (TLS) instead of traditional TCP. TLS is more secure than transmitting clear traffic over the wire. Transcoding refers to the process of converting media streams between different audio codecs. Transcoding is necessary if the telephony codec used is not G711, that is, the codec used by Lync. Director Server: This is an optional role in Lync Server 2013. The Director Server role redirects user requests to their home pool which can be either a Standard Edition server or an Enterprise Edition Front End pool. The Director Server protects the Front End Server roles from denial-of-service attacks and cannot be collocated with any other server role. Persistent Chat Server: This is a new and separate role in Lync Server 2013 that provides features similar to group chat in earlier versions of Lync. Persistent chat allows users to participate in multiparty and topic-based chat. Chats can be categorized by topic in a chat room and are not transient like unarchived instant message conversations or audio/video/web conferences. Edge Server: This role in Lync Server manages all communications to external and federated users except anything related to TTP/TTPS. All other traffic, such as SIP or RTP, is routed to the external users by using the Edge Server. Standard Edition Server: The Standard Edition Server delivers the features of Lync Server 2013 by using integrated databases on a single server. This configuration enables an organization to have Lync Server 2013 infrastructure at a low cost that can be deployed with a backup registrar to provide limited A features. This manages all Lync workloads, including client authentication, instant messaging, user presence updates, web conferencing, audio/video conferencing and Enterprise Voice, all running on one server. This reference architecture uses the Lync Enterprise Edition Pool. Refer to the Dell Unified Communication Solution with Lync for Single Site Implementation for a reference architecture using the Lync Standard Edition Server. The following are the other server applications that can be part of Lync Server 2013 deployment: Office Web Apps Server: This role provides enhanced web conferencing with PowerPoint presentations. Office Web Apps Server enables custom fonts, animated slides and higher-resolution content sharing in presentations. Reverse Proxy Servers: This role is an external component that complements the Edge Server role by handling web services traffic. With the Reverse Proxy Servers, external users can access web services available through simple URLs. Some of these features include meeting content downloads, address book downloads, location information, and Lync Web App. The TTP and TTPS traffic is routed to the Reverse Proxy Server which then forwards these requests to the Front End Server. 10 Reference Architecture Microsoft Lync Server 2013 on Dell PowerEdge R630

2.1.6 Lync 2013 Enterprise Edition Pool Lync Server 2013 Enterprise Edition follows Microsoft s brick model or brick architecture. In this architecture, the SQL Back End Servers and the Lync Front End Servers are loosely coupled than in Lync Server 2010. Users are now distributed among up to three different user groups. Each user group is assigned to three Front End Servers within the Enterprise Edition pool a primary, a secondary and a tertiary server. All user data is replicated across these three Front End Servers by using Windows Fabric, a management utility to handle replication. It is recommended to install a minimum of three Front End Servers when deploying an Enterprise Edition pool. Due to these changes in the Lync architecture, the Front End Servers are now primarily responsible for managing user state or presence. The presence information on the Front End Servers is synchronized and written back to the SQL database by using lazy writes. 2.2 Design considerations The key design considerations for this reference architecture include: igh Availability Application Performance Resource Consolidation 2.2.1 igh Availability A must be considered at every layer to ensure minimal application downtime. The following two layers of A are considered in this reference architecture: Application-level high availability utilizes multiple instances of server roles to provide services in the event of a failure. This A layer ensures that there is no single point of failure at the application level, thus minimizing service downtime to the end user. Infrastructure high availability is provided when a hardware resource fails; there is another preconfigured resource that takes over. During scheduled downtime, infrastructure availability ensures that there is additional hardware resource, and the application-level availability keeps the application services running for the end users. This is important for IT administrators who wish to apply patches or upgrades to their data center equipment. 2.2.2 Application performance While maintaining A is critical, applications must perform well to ensure a reliable end-user experience. The Dell Global Solutions Engineering group used Lync 2013 Stress and Performance Tool to ensure that the reference architecture is appropriately sized to meet the needs of a 5,000-user Lync deployment. Some of the workloads sized in this reference architecture included audio conferencing, video conferencing using multi-view, application sharing, distribution list expansion, address book downloads and instant messaging. The following application best practices prevent performance bottlenecks: 11 Reference Architecture Microsoft Lync Server 2013 on Dell PowerEdge R630

Using static memory allocation instead of dynamic memory allocation for virtual machines (VMs) Maintaining virtual CPU to physical core ratio at 1:1 Disabling hyperthreading Disabling non-uniform memory access (NUMA) spanning on the hypervisor Ensuring that similar roles do not coexist on the same host Using fixed or pass-through disks rather than dynamic disks Using dedicated hard drive spindles for hypervisor, VM and SQL data stores 2.2.3 Resource consolidation In a solution that uses Lync Server, voice gateways/session border controllers, and PSTN or PBX systems, it is important to consolidate multiple components to reduce data center footprint and cost. This reference architecture uses server virtualization to consolidate the different Lync Server roles. A is provided natively by Lync or by using SQL mirroring/clustering. 12 Reference Architecture Microsoft Lync Server 2013 on Dell PowerEdge R630

3 Solution reference architecture A high-level diagram of the reference architecture is illustrated in Figure 1. It shows a customer scenario that consists of one main central site and one or more branch offices with WAN links between them. This design includes both voice connectivity methods ISDN (T1/E1) and SIP trunk connections provided by Internet Telephony Service Provider (ITSP)/ PSTN providers. owever, the customer may have either ISDN (T1/E1) or SIP trunk for the central site and branch offices. SIP Trunk SBA ITSP/PSTN T1/E1 Branch Office Branch Office Users T1/E1 WAN Link SIP Trunk Enterprise Voice Connectivity Central Site Users External Users Lync Server Edge Architecture Lync Server Core Architecture Central Site Session Border Controller Lync Edge Server Reverse Proxy Lync Front SQL Server Persistent Office Web End Server Chat Server Apps Dell Quest Messagestats Virtual Load Balancer Figure 1 Dell UC Solution Logical Architecture There are five major portions of the reference architecture: Lync Server Core Architecture: This area located at the central site hosts the server roles that provide the main features of Lync Server 2013. To support these crucial Lync Server components, sufficient computing and storage resource should be allocated to meet the requirements from the targeted number of users. The design should incorporate A to ensure minimal service downtime. 13 Reference Architecture Microsoft Lync Server 2013 on Dell PowerEdge R630

Therefore, multiple instances of those important server roles are utilized to avoid a single point of failure. The design also employs load balancers to distribute workload among these server roles. Lync Server Edge Architecture: Edge Servers and the optional Reverse Proxy Servers are located in the perimeter network of the central site. They support communications across the organization s firewall between internal and external users. Enterprise Voice Connectivity: This portion includes additional PSTN connectivity components required to implement the Enterprise Voice features, such as PSTN gateways, PBX and SBC, and shows how they connect to the Lync Server core architecture. Branch Office Connectivity: The branch office supports a smaller number of users. The design has to ensure that branch office users can continue to make and receive calls through the local ISDN or SIP trunk in case of a WAN failure, which disrupts the connection between branch offices and the central site. The branch office can be equipped with a Survivable Branch Appliance (SBA), which runs a Lync Server registrar and a Mediation Server component. End User Connectivity: End users connect with Lync services through different types of end-point devices. This reference architecture describes their connectivity options and highlights how Dell Networking W-series wireless controllers and APs enhance the user experience of wirelessconnected Lync clients. Note: Step-by-step instructions for installing and configuring a complete Lync solution and any service applications used in this performance study are outside the scope of this paper. For more information and resource, refer to the Additional Resources section of this paper. 3.1 Lync Server core architecture When deploying a Lync solution, the first step is to articulate a design that will address the communication requirements across the enterprise. The following section provides the design framework adequate for 5,000 Lync users with instant messaging, audio/video, web conferencing and Enterprise Voice communication modalities. The primary component of this architecture is a Lync Server 2013 Enterprise Edition Front End pool, which serves these different modalities. The Front End pool consists of three Front End servers that are identical and provide communication services for a group of users. This pool of identically configured servers provides scalability and availability in the event of server maintenance or failure. With Lync 2013, the Front End pool is also the primary store for the user and conference data, where each user s data is replicated to up to three Front End Servers with an additional copy being backed up to the Back End Server. Each Lync Front End Server deploys a SQL Express instance to store the RTC Local and Lync Local database instances. RTC Local databases synchronize with the RTC databases on the SQL Back End Servers for Lync. The RTC local databases are required because they contain user presence information. The Lync Local database instance contains a database named lyss, which specifically works for paired pool configuration. The Back End Server hosts databases running SQL Server and does not run any Lync Server software. These databases serve as the backup store for user and conference data. The same SQL Back End Server can also be used as the primary store for other roles, such as Archiving, Monitoring and Persistent Chat. It is recommended that the Back End Server be mirrored or clustered for failover. 14 Reference Architecture Microsoft Lync Server 2013 on Dell PowerEdge R630

Figure 2provides a high-level schematic of a Lync Server 2013 core architecture that has been sized for 5,000 users. The architecture has been built on the design principles discussed in Section 2.2. The Lync Server 2013 core architecture consists of three PowerEdge R630 servers. Each of these servers is running Windows Server 2012 R2 with yper-v. The detailed hardware specifications for these servers are provided in Section 4. SIP Trunk SBA ITSP/PSTN T1/E1 Branch Office Branch Office Users T1/E1 WAN Link VM SQL PowerEdge R630 SIP Trunk Enterprise Voice Connectivity Central Site Users VM SQL PowerEdge R630 External Users Lync Server Edge Architecture VM SQL PowerEdge R630 Lync Server Core Architecture Central Site Figure 2 Lync Server 2013 Core Architecture For providing A at the application level, three Front End VMs, each collocated with Mediation and Archiving+Monitoring roles, are configured in a single Front End pool. These VMs are placed on separate physical yper-v hosts to ensure that a single physical server failure does not impact more than one Front End VM. For Lync Back End A, a SQL mirroring pair is used. Similar to the Front End VMs, SQL mirrored pairs must be placed on separate physical yper-v hosts. Because the design utilizes SQL mirroring to provide A, an additional SQL witness server instance is needed to support automatic failover. Lync 2013 requires Office Web Apps servers (OWS) to provide enhanced web conferencing experience. In this reference architecture, two OWS servers are deployed to enable A of these services. In addition, two Persistent Chat Server VMs are deployed to ensure availability. 15 Reference Architecture Microsoft Lync Server 2013 on Dell PowerEdge R630

In addition to the above mentioned Lync-specific components, Dell MessageStats TM for Lync and two virtual load balancer appliances in the active/standby mode are also optionally considered as a part of this design. MessageStats for Lync provides comprehensive usage reporting and analysis. It allows organizations to monitor usage trends and adoption of the Lync services. It can also be used as a billing and chargeback solution for Lync services. MessageStats stores application data in SQL server database. In this reference architecture, the MessageStats SQL database is deployed on the witness server used by SQL Mirror. Table 2 presents a VM resource summary for the Lync Server core architecture. Table 2 Lync Server Core Architecture VM Resource Summary Purpose VMs Total Virtual CPU (vcpus) Total Memory (GB) Lync Server 2013 Enterprise Edition Front End (with Mediation and Archiving + Monitoring roles) Lync Server 2013 Back End (SQL Server 2012 SP1 Standard Edition) Lync Server 2013 Persistent Chat Server 3 30 (10 per VM) 2 20 (10 per VM) 2 12 (6 per VM) 96 (32 GB per VM) 64 (32 GB per VM) 32 (16 GB per VM) Office Web Apps Server(OWS) 2 8 (4 per VM) 16 (8 GB per VM) SQL Mirror Witness and MessageStats Database Server (SQL Server 2012 SP1 Standard Edition) 1 2 8 Virtual Load Balancer Appliance 2 Third-party vendor recommended Third-party vendor recommended Dell MessageStats Server 1 2 8 3.1.1 Network architecture The networking configuration required on the Front End hosts is summarized in Figure 3. Each PowerEdge R630 server provides four 1 GbE network connections on the motherboard (a configuration known as LOM, for LAN on motherboard ). On the Microsoft yper-v host, a converged network design using Microsoft NIC teaming is used to provide networking connectivity to the virtual machines. This section describes the host networking used in the reference architecture. Figure 3 shows the connectivity of the Lync Front End VMs to the Converged Virtual switch, which connects to the Converged Network team. The teamed NICs from the hosts connect over 1GbE to the Dell Networking switches, which are in turn fed into a pair of redundant layer 3 switches for Lync clients and the media gateways/sbcs for VOIP connectivity. 16 Reference Architecture Microsoft Lync Server 2013 on Dell PowerEdge R630

Management yper-v Virtual Switch VMs yper-v ost OS Converged Net Team (Switch Independent yper-v Port Load Balancing) 1Gb Ethernet NDC 0 1 2 3 Dell Networking 1GbE Switch Dell Networking 1GbE Switch Wireless Clients Perimeter Network Corporate Network Load Balancer Enterprise PBX Load Balancer Internal Lync Clients E1/T1 External Lync Clients Key: Enterprise Voice Behind the PBX Internal Extensions Sonus SBC / Media Gateway E1/T1 Enterprise PBX ITSP/PSTN Enterprise Voice in front of the PBX SIP Trunking using SBC ITSP/PSTN E1/T1 Internal Extensions Figure 3 Network Architecture of Lync Core Server osts 3.1.2 Storage for Lync, SQL, and ypervisor All physical servers hosting the entire Lync core infrastructure use internal server storage, a cost-effective alternative to storage area networks or direct-attached storage for a Lync deployment of this size. The internal server storage in this design has been logically partitioned into three separate storage blocks with multiple RAID sets. The RAID sets are made up of separate disks. Each storage block supports the host operating system, guest virtual machine storage and Lync SQL database storage. Use of different storage blocks with isolated disks guarantees that there is no contention for disk access among the three different stores. 3.1.3 Storage for yper-v osts The functional separation of disk drives enables simplified storage management. This storage design of the physical hosts follows the yper-v best practice by not placing system files, application data and logs on shared physical storage drives. The detailed hardware specifications for the server hosts are provided in Section 4. Table 3 details the storage requirements for the physical hosts. 17 Reference Architecture Microsoft Lync Server 2013 on Dell PowerEdge R630

Table 3 Lync Server Core Architecture Storage Requirements Storage Building Blocks Disks Allocated RAID Configuration ypervisor 2 x 600-GB 10K RPM SAS RAID 1 Virtual Machines Store 2 x 1.2-TB 10K RPM SAS RAID 1 SQL databases 6 x 1.2-TB 10K RPM SAS RAID 10 As shown in Table 3, 10,000 RPM SAS drives were leveraged for their throughput rather than higher capacity NL-SAS or SATA drives. By using standardized 1.2-TB drives, sufficient capacity is provided for the VM store and the SQL databases. Note that these volumes are mirrored, and therefore the effective capacity is only half the total. For the VM store, a single VDX volume was created for all VMs. The Front End VMs need to be allocated some extra local hard disk space to account for the RTC local database. Because Microsoft recommends VDX format from yper-v 2012 onward, this solution leverages fixed VDX volumes to ensure performance from all virtual machines. VDX format has several-fold improved performance over VD format and can store custom metadata about operating system version, patches applied and so on. 3.2 Lync Server Edge architecture The highlighted section of Figure 4 shows the Lync components that need to reside in the perimeter network with internal and external firewalls. This reference architecture assumes that an existing perimeter network already exists and does not explicitly provide details for firewalls. Dell SonicWall has a wide range of products to fulfill any needs for security or firewall devices. To follow the A design principle, the proposed Edge architecture consists of an Edge pool with two Edge Server VMs and uses ardware load balancing on both the internal and external Edge interfaces. A Reverse Proxy Server can also be optionally configured to support the sharing of web content and web services to federated and external users and to enable certain features as detailed on the Microsoft Setting up reverse proxy servers for Lync Server 2013 site. Because the Reverse Proxy Server cannot be collocated with the Edge Server, two additional VMs are needed. The customer can deploy two Edge VMs in their existing environment if load balancer and Reverse Proxy Servers are already in place for other running applications. For the verification, both the Edge and Reverse Proxy Servers were consolidated with a Virtual Load Balancer and Virtual SBC as VMs on two PowerEdge R430 1U servers in lab environment, each with dual-socket Intel Xeon E5-2600 v3 series processors, 32 GB of DDR3 RAM and support for up to eight 2.5-inch internal DDs. Each server is running Windows Server 2012 R2 with yper-v. The detailed hardware specifications for these servers are provided in Section 4. 18 Reference Architecture Microsoft Lync Server 2013 on Dell PowerEdge R630

SIP Trunk SBA ITSP/PSTN T1/E1 Branch Office Branch Office Users T1/E1 WAN Link VM SQL PowerEdge R630 SIP Trunk Enterprise Voice Connectivity Central Site Users VM VM SQL PowerEdge R630 External Users Lync Server Edge Architecture VM VM SQL PowerEdge R630 Lync Server Core Architecture Central Site Figure 4 Lync Server Edge Architecture The recommended configuration details of the VMs are provided in Table 4. Table 4 Lync Server Edge Architecture Storage Requirements Purpose VMs Total Virtual CPU (vcpus) Total Memory (GB) Lync Server 2013 Edge Pool 2 16 (8 per VM) 32 (16 GB per VM) Reverse Proxy 2 4 (2 per VM) 16 (8 GB per VM) Virtual Load Balancer 2 4 (2 per VM) 4 (2 GB per VM) Virtual SBC 2 4 (2 per VM) 4 (2 GB per VM) 19 Reference Architecture Microsoft Lync Server 2013 on Dell PowerEdge R630

3.2.1 Edge Network architecture Figure 5 details the network connectivity for each of the PowerEdge R430 servers hosting the Edge and Reverse Proxy Server VMs. The PowerEdge R430 server uses the QLogic 5720 quad-port 1Gb LAN on Motherboard (LOM) and has an optional QLogic 5720 dual port 1Gb add-on Network Interface Card (NIC) configured. Two of the ports from the LOM are teamed together and provide the connectivity to the internal networking, and two of the ports from the add-on NIC are teamed to provide external network connectivity. Separate virtual switches are created on each of the teamed NICs, and each VM has a separate virtual NIC connecting to the internal and external networks, as shown in Figure 5. ost LAN Lync Edge + Reverse Proxy VM VM Internal VLAN VM Switch VM Switch Wireless Clients NIC TEAM NIC TEAM VM External VLAN LAN Redundant Layer 3 LAN Switches LOM NIC 1 LOM NIC 3 LOM NIC 2 LOM NIC 4 ISL Lync Front End, Back End, etc. External Clients External Network Figure 5 Network Architecture for Edge/Reverse Proxy osts 20 Reference Architecture Microsoft Lync Server 2013 on Dell PowerEdge R630

The internal network connects to the Lync core architecture and Lync clients on the LAN. The external network allows access for authenticated Lync clients from the Internet. 3.2.2 Reverse Proxy The Reverse Proxy Server is an optional, external component that is not defined as part of the Lync topology. The Reverse Proxy Server is considered optional because external users can log in and use critical Lync features, such as calls, desktop sharing, and federated communications, without the deployment of this role. With a Reverse Proxy Server, external users can use the functionalities that are available through web services, including: Downloading meeting content Expanding distribution groups Downloading files from the address book service Accessing the Lync Web App client Enabling the Lync 2013 client, Lync Windows Store app and Lync 2013 Mobile client to locate the Lync Discover (autodiscover) URLs and use Unified Communications Web API (UCWA), etc. Per Microsoft s recommendation, these web services are made available to external users by publishing them through external, simple URLs. TTP and TTPS requests from external users are handled by a Reverse Proxy Server, which forwards them internally to the Lync Front End pool. If the Reverse Proxy Server is not present, these external users will not have access to the functionalities. Furthermore, the Lync mobile client for phones and tablets will not be functional for external users as they are web-based and require the Reverse Proxy Server to communicate with the Lync Front End pool s IIS mobility website. 3.2.3 Best Practices for Edge and Reverse Proxy ost The following best practices should be considered when deploying the Edge and Reverse Proxy Servers: Two separate network interfaces should be used for internal and external networks at minimum. These should use separate subnets that are not routable across each other. Only the external interface should include the default gateway and not the internal interface. Static routes must be defined on the Edge Server for connectivity to internal subnets. A standard SSL certificate, with common name field set to the Edge Server s FQDN, should be used for the Internal Edge certificate; this certificate cannot contain a subject alternative name (SAN) field. Whenever possible, internally facing certificates should be obtained from an internal Windows Enterprise CA. The external edge certificate should be a UCC or SAN certificate issued by a public trusted certificate authority. It should include a common name field set to the access edge FQDN and subject alternative name field that contains both the access edge FQDN and the web conferencing FQDN. Additionally, external facing certificates should not include any of the internal hostnames. It is not recommended to use the same external certificate for both the external Edge Server interface and the Reverse Proxy Server interface. owever, if this is done for cost savings, the access edge FQDN must be specified in the common name field and the Reverse Proxy FQDN in the SAN (subject alternative name) field. 21 Reference Architecture Microsoft Lync Server 2013 on Dell PowerEdge R630

3.3 Enterprise Voice Connectivity In Lync Server 2013, the functionality of the Mediation Server is part of the Front End Server by default. Therefore, a separate Mediation Server is no longer required. The Front End pool can directly connect to a PSTN gateway, an IP-PBX or to a SIP trunk through a SBC. This reference architecture assumes connectivity to an ITSP through an intermediary on-premise SBC or to a PSTN through a media gateway, as shown in Figure 6. SIP Trunk SBA ITSP/PSTN T1/E1 Branch Office Branch Office Users T1/E1 WAN Link IP-PBX Gateway SBC VM SQL PowerEdge R630 SIP Trunk Enterprise Voice Connectivity Central Site Users VM VM SQL PowerEdge R630 External Users Lync Server Edge Architecture VM VM SQL PowerEdge R630 Lync Server Core Architecture Central Site Figure 6 Enterprise Voice Connectivity for Central Site The enterprise connectivity options, as shown in Figure 6, are: T1/E1 connectivity from PSTN to a Media Gateway, which in turn connects to the Lync infrastructure through SIP connectivity SIP trunk from an ITSP to an SBC, which then connects to Lync infrastructure through SIP PBX connecting to a media gateway through a T1/E1 connectivity, which in turn connects to the Lync infrastructure through SIP If SIP trunk is connected through an on-premise SBC, consider placing the SBC in the perimeter network to provide the appropriate level of security. If connecting directly to a SIP trunk provider without an 22 Reference Architecture Microsoft Lync Server 2013 on Dell PowerEdge R630

intermediary SBC, a separate Mediation Server may be required. The selected third-party gateway validated in this reference architecture is the AudioCodes Mediant TM SBC Virtual Edition. Note: This reference architecture collocates the mediation server with the Front End Server. It is recommended that you contact Dell Services or a Dell partner to scope out the optimal solution to fit your needs. 3.4 Branch Office Connectivity In this reference architecture, there is one central site and one or more branch sites. The Lync core infrastructure resides at the central site. The branch sites are connected to the central site through a WAN, and they get most of their functionality from the Lync infrastructure pool at the central site. A SBA can be deployed at the branch site to provide voice resiliency at the branch site. Figure 7 shows the logical connectivity of the branch office to the central site through a WAN. The SBA on the branch office is connected to the central site through a WAN and to a PSTN or an ITSP to provide voice resiliency. SIP Trunk SBA ITSP/PSTN T1/E1 Branch Office Branch Office Users T1/E1 WAN Link IP-PBX Gateway SBC VM SQL PowerEdge R630 SIP Trunk Enterprise Voice Connectivity Central Site Users VM VM SQL PowerEdge R630 External Users Lync Server Edge Architecture VM VM SQL PowerEdge R630 Lync Server Core Architecture Central Site Figure 7 Branch Office Connectivity to Central Site through SBA 23 Reference Architecture Microsoft Lync Server 2013 on Dell PowerEdge R630

An SBA is a purpose-built hardware appliance that has a subset of Lync features and enables voice resiliency in branch office scenarios. The SBA consists of an image running Windows Server and essential Lync components, such as mediation and registration, and has PSTN gateway functionality to connect to a PSTN or an ITSP. The SBA depends on the Front End pool on the central site to provide Lync services. owever, in the event of a WAN or Front End pool failure on the central site, the SBA enables the local users to continue receiving and placing voice calls. 3.5 End-user connectivity End-user connectivity is achieved through the Lync 2013 desktop or mobile clients, Lync Web App, Lync Windows Store App, and Lync Phone Edition or through specialized Lync devices. The Lync 2013 desktop clients can be installed on Windows-based desktops, laptops or hybrids, such as the Dell XPS 12 Ultrabook. The Lync 2013 mobile clients are available for Windows Phone devices, Apple ios devices (including the iphone and ipad) and Android devices. Specialized Lync devices, such as the Polycom CX series of phones, are designed to integrate with Lync, and some of these devices run the Lync Phone Edition natively on them. These clients can be connected through a wired connection or wirelessly. 24 Reference Architecture Microsoft Lync Server 2013 on Dell PowerEdge R630

4 Technical specifications This section details the technical specifications for all of the physical and virtual components that make up this reference architecture and are part of the UC solution. Figure 8 shows the complete logical view of the UC solution for 5,000 users with central site and branch office connectivity. SIP Trunk SBA Wireless Endpoints ITSP/PSTN Wired Endpoints Branch Office Branch Office Users WAN Link Wireless Endpoints VM SQL PowerEdge R630 SIP Trunk Wired Endpoints VM Central Site Users VM SQL PowerEdge R630 Firewall Lync Server Edge Architecture VM Firewall External Users VM SQL PowerEdge R630 Lync Server Core Architecture Central Site Figure 8 Dell UC Solution 4.1 Virtual Machine specifications Many Lync Server 2013 server roles are deployed in separate virtual machines, as detailed in Section 3. Each virtual machine has specific resource requirements in terms of compute and memory. The allocation of virtual CPU, memory and networking has been validated by using the Microsoft Lync Stress and Performance Tool and per Microsoft best practices. Table 5 Virtual Machine Configuration Details 3 x Lync Front End VMs (includes Archiving-Monitoring & Mediation Roles) Operating System Windows Server 2012 R2 Virtual Machine Configuration 10 x vcpu 32 GB RAM 25 Reference Architecture Microsoft Lync Server 2013 on Dell PowerEdge R630

Networks 1 x Synthetic Network Adapter per VM Software Lync Server 2013 Operating System Virtual Machine Configuration Networks Software Operating System Virtual Machine Configuration Networks Software 2 x Back End SQL Server VMs Windows Server 2012 R2 10 x vcpu 32 GB RAM 1 x Synthetic Network Adapter per VM SQL Server 2012 Standard Edition 1 x Witness & MessageStats SQL Server VM Windows Server 2012 R2 2 x vcpu 8 GB RAM 1 x Synthetic Network Adapter per VM SQL Server 2012 Standard Edition 2 x Office Web Apps Server (OWS) VMs Operating System Windows Server 2012 Virtual Machine Configuration Networks Software Operating System 4 x vcpu 8 GB RAM 1 x Synthetic Network Adapter per VM Office Web Apps Server 2 x Persistent Chat Server VMs Windows Server 2012 R2 Virtual Machine Configuration 6 x vcpu 16 GB RAM Networks 1 x Synthetic Network Adapter per VM Software Lync Server 2013 1 x MessageStats VM Operating System Windows Server 2012 Virtual Machine Configuration 2 x vcpu 8 GB RAM Networks 1 x Synthetic Network Adapter per VM Software Dell MessageStats for Lync 2 x Edge Server VMs Operating System Windows Server 2012 R2 Virtual Machine Configuration 8 x vcpu 16 GB RAM Networks 2 x Synthetic Network Adapter (1 internal, 1 external) Software Lync Server 2013 Operating System Virtual Machine Configuration Networks 2 x Reverse Proxy VMs Windows Server 2012 R2 2 x vcpu 8 GB RAM 2 x Synthetic Network Adapter (1 internal, 1 external) 26 Reference Architecture Microsoft Lync Server 2013 on Dell PowerEdge R630

Software Operating System Virtual Machine Configuration Networks Software Operating System Virtual Machine Configuration Networks Software IIS ARR Win 2012 R2 4 x Virtual Load Balancer VMs Third-party provider defined Third-party provider defined 1 x Synthetic Network Adapter Third-party Virtual Load Balancer (Recommended: KEMP Virtual LoadMaster VLM) 2 x SBC Virtual Edition VMs Third-party provider defined Third-party provider defined 2 x Synthetic Network Adapter Third-party Virtual Session Border Controller (Recommended: AudioCodes Mediant SBC Virtual Edition) Table 5 has the details of the recommended configuration for the virtual machines that make up this solution. Based on the role performed by each virtual machine, optimum amounts of compute, memory, network and storage resources have been allocated. CPU resources are allocated to ensure that the core:vcpu ratio is not oversubscribed for delay-sensitive real-time traffic. Memory is allocated statically to each VM, ensuring that resources are guaranteed during peak usage hours. For service availability in the event of failure at application level, more than one instance of virtual machine has been provisioned for all critical Lync server roles. Because the Lync Server external website listens on port 4443, instead of on the standard port 443, a Reverse Proxy Server is necessary for port translation between the two. The Reverse Proxy Server can use Microsoft IIS Application Request Routing (ARR) 2012 R2 to provide access to non-ttp/ttps content for the Lync user requests originating from outside of the external firewall. The IIS ARR component enables IIS to handle Reverse Proxy requests, URL rewrites and load balancing. It also enables increased web application scalability and reliability through rule-based routing, client and host name affinity, load balancing of TTP server requests, distributed disk caching and optimized resource utilization for application/web servers, among other benefits. 4.2 ardware specifications The hardware components of the reference architecture are detailed in the following tables: Table 6 Server ost Configuration Details osts for Lync Core Architecture ardware CPU RAM Dell PowerEdge R630 rack server with 10 x 2.5-inch drive chassis 2 x Intel Xeon processor E5-2695 CPUs with 14 cores per CPU 128 GB (16 x 8 GB recommended to populate 1 DIMM per Channel) 27 Reference Architecture Microsoft Lync Server 2013 on Dell PowerEdge R630