Resonate Central Dispatch

Resonate Central Dispatch Microsoft Exchange 2010 Resonate, Inc. Tel. + 1.408.545.5535 Fax + 1.408.545.5502 www.resonate.com

Copyright 2013 Resonate, Inc. All rights reserved. Resonate Incorporated and its licensors retain all ownership rights to the Central Dispatch, CDConsole and Global Dispatch computer programs (hereinafter collectively called Resonate Software) and their documentation. Use of Resonate Software is governed by the license agreement accompanying your original media. Resonate is a registered trademark of Resonate, Inc. The Resonate logo, Resonate Global Dispatch, Resonate CDConsole, the Resonate CDConsole logo, Resonate Central Dispatch, and Resource-based Scheduling are trademarks of Resonate, Inc. Microsoft, Windows, Windows Server, Exchange 2010 and Outlook are either registered trademarks or trademarks of Microsoft Corporation in the United States and/or other countries. All other brand or product names used in this document are trademarks or registered trademarks of their respective companies or organizations. All other brand product names mentioned herein may be the trademarks or registered trademarks of their respective companies. Resource-based Scheduling technology is protected under U.S. Patent 5,774,660. THE INSTRUCTION AND INFORMATION REGARDING THE PRODUCTS IN THIS GUIDIE ARE SUBJECT TO CHANGE WITHOUT NOTICE. COMPANIES, NAMES, AND DATA USED IN ANY EXAMPLES HEREIN ARE FICTITIOUS UNLESS OTHERWISE NOTED. ALL STATEMENTS, INFORMATION, DECLARATIONS AND RECOMMENDATIONS IN THIS MANUAL ARE BELIEVED TO BE ACCURATE BUT ARE PRESENTED WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED. USERS MUST TAKE FULL RESPONSIBILITY FOR THEIR APPLICATION OF ANY PRODUCTS.

Contents Contents Contents... 1 Preface... 2 1.1. Purpose... 2 1.2. Intended Audience... 2 1.3. Related documents... 2 1.4. Availability... 2 Chapter 2. Introduction... 3 Chapter 3. Requirements... 4 3.1. Hardware... 4 3.2. Software... 4 3.3. Operating system... 4 Chapter 4. Architecture... 5 4.1. Exchange roles... 5 4.2. Load balancing Microsoft Exchange 2010... 5 4.3. Components to be load balanced... 6 4.4. Network diagram... 7 Chapter 5. Configuring Central Dispatch... 8 5.1. Overview... 8 5.2. Logging to Central Dispatch... 9 5.3. Creating a new site... 10 5.4. Adding nodes to a site... 12 5.5. Adding virtual IP addresses to a site... 14 5.6. Configuring scheduling rules... 16 5.7. Starting the site... 24 Technical support... 28 Glossary... 29 Index... 30 Deploying Central Dispatch 1

Preface Preface This section contains the following topics: Purpose Intended Audience Related documents Availability 1.1. Purpose The purpose of this deployment guide is to provide detailed information about how you can effectively use Central Dispatch for load balancing Microsoft Exchange 2010. 1.2. Intended Audience This deployment guide is intended for the administrators who are authorized to configure Central Dispatch for the purpose of load balancing Microsoft Exchange 2010. 1.3. Related documents In support of this deployment guide, you can also refer the following additional guides: Central Dispatch Release 6 Quick Start guide Central Dispatch Release 6 Evaluation guide 1.4. Availability A soft copy of this deployment guide is available on the Resonate support web site at: www.resonate.com. 2 Deploying Central Dispatch

Introduction Availability Chapter 2. Introduction Resonate Central Dispatch is a software or a virtual load balancing solution, which is free from the constraints that are usually associated with hardware based load balancing systems and ADCs. This enables you to use Resonate Central Dispatch in any physical, virtual, or cloud environment, with the ability to scale and migrate your systems on-demand. Using Resonate Central Dispatch software you can: Automatically detect and resolve server capacity issues by efficiently load balancing users among server resources. Optimize the traffic flow and resource utilization by monitoring network performance and server availability and then intelligently routing traffic to maximize application availability and performance. In traditional load balancing systems, server and application availability is determined by writing physical interactions between the load balancing system and the applications. This approach not only limits the number of applications that can be managed, but ignores the health of the server and network infrastructure. While Central Dispatch can use this traditional approach, Resonate s patented Resource-Based Scheduling technology allows routing decisions based on actual statistics and heuristics obtained from the server and network infrastructure. This inherent support for all applications provides higher application availability, lower costs, and an improved end-user experience. Central to the Resonate Active Intelligence are lightweight distributed software agents that collect detailed information, such as CPU load and memory utilization. This information, together with network latency and other metrics obtained by the CD Schedulers and Central Dispatch Console, determine the most ideal path for data flow. Deploying Central Dispatch 3

Requirements Hardware Chapter 3. Requirements To use Central Dispatch for load balancing Exchange 2010, ensure that the system meets the following requirements: Hardware Software Operating system 3.1. Hardware No additional hardware is required as you can directly install Central Dispatch on the Client Access Servers (CAS). 3.2. Software No any additional software required, other than Microsoft Windows server Microsoft Exchange 2010. 3.3. Operating system For Microsoft Exchange 2010 load balancing, Central Dispatch supports the following operating systems: Windows Server 2008 Windows Server 2008 R2 4 Deploying Central Dispatch

Architecture Exchange roles Chapter 4. Architecture This chapter provides the information about the functions of Exchange server 2010, the components that you can load balance in Exchange server 2010, and how you can use the Resonate Central Dispatch application to perform the load balancing of Microsoft Exchange server 2010. This chapter also provides a network diagram that shows the deployment of Central Dispatch in a lab for load balancing Exchange 2010. This chapter contains the following topics: Exchange roles Load balancing Microsoft Exchange 2010 Components to be load balanced Network diagram 4.1. Exchange roles The primary functionality of Exchange 2010 is split into the following component roles. Component Edge Transport Unified Messaging Mailbox Client Access Hub Transport Function Responsible for routing mail in and out of Exchange. Often this role is integrated with the Hub Transport, especially in smaller installations. Connects exchange to other messaging systems. Usually this role is used with PBX (phone system). Stores client mailboxes and public folders. Access/Entry point for all clients. Responsible for routing mail within the various components. Out of these five roles, Edge Transport and Unified Messaging roles are optional and not found in the installations. However, Mailbox, Client Access Server, and Hub Transport roles are part of every Exchange 2010 installation. 4.2. Load balancing Microsoft Exchange 2010 Load Balancing is the process of managing and distributing client traffic among all the available components of Exchange 2010. Central Dispatch, if you properly Deploying Central Dispatch 5

Architecture Components to be load balanced deploy, can provide redundancy with scalability and can ensure that users continue to receive access to Exchange services despite the component or server failure. Using Resonate Central Dispatch, you can leverage the following benefits: Performance: Clients are directed to the least loaded server thereby ensuring a more satisfactory response. Scalability: You can realize a higher number of users than would be otherwise not possible. Flexibility: You can make components online and offline without service disruption. You can access component services through same or different IP addresses. Redundancy: Your Exchange services remain available and viable despite server failure. Security: DDOS protection as well as security by obscurity is implemented by default. The following are primary purposes of load balancing Exchange 2010: Mitigate the impact of a failure of any Client Access server. Ensure that client traffic/load is evenly distributed across all Client Access and Hub Transport servers. For more information, see Understanding Load Balancing in Exchange 2010 and Load Balancing Requirements of Exchange Protocols. 4.3. Components to be load balanced This deployment guide provides the load balancing information about the Client Access server, CAS, Hub Transport, and HT components. TCP Port Role Uses 25 HT SMTP 80 CAS HTTP various services 110 CAS POP3 clients 135 CAS RPC end point mapper 143 CAS IMAP4 clients 443 CAS HTTPS various services 993 CAS Secure IMAP4 clients 995 CAS Secure POP3 clients 59532* CAS Static port for RPC client access service 59533* CAS Static port for Exchange address book service 6 Deploying Central Dispatch

Architecture Network diagram TCP Port Role Uses * This guide assumes that the CAS servers to be load balanced have been modified to use ports 59532 and 59533 for the RPC ports for client access and address book service, respectively. For more information, see Configure Static RPC Ports on an Exchange 2010 CAS. 4.4. Network diagram Hostname IP Address Hub Transport Server 1 ozone-1 192.168.76.152 Hub Transport Server 2 ozone-2 192.168.76.153 Client Access Server 1 ozone-1 192.168.76.152 Client Access Server 2 ozone-2 192.168.76.153 Virtual IP Address (VIP) ozone-3 192.168.76.154 Resonate GUI ozone-2 192.168.76.153 Deploying Central Dispatch 7

Overview Chapter 5. Configuring Central Dispatch Configuration of Central Dispatch consists of the following procedures: Logging to Central Dispatch Creating a new site Adding nodes to a site Adding virtual IP addresses to a site Configuring scheduling rules Starting the site 5.1. Overview The Central Dispatch configuration is fairly straightforward. Load Balancing the Exchange CAS services involves creating three load balancing policies with an additional two where POP3 and IMAP4 happen to be required. Once you successfully install Central Dispatch, the configuration of Central Dispatch for Exchange only takes few minutes. All HTTPS services will be load balances using a catch-all scheduling rule that provides application access for OWA, OA, EAS, ECP, EWS and AD. Additional policies will be created for RPC, SMTP, and the optional IMAP4 and POP3. The following table summarizes the possible Central Dispatch configuration for each Exchange Client Access role: Exchange Role Scheduling Rule Type Cluster Port Server Port Affinity Type Outlook Web Access SSL3 443 443 Session ID Outlook Anywhere SSL3 443 443 Session ID ActiveSync SSL3 443 443 Session ID RPC (Portmapper) IP Persist 135 135 Client IP RPC CA (MAPI) IP Persist 59532 59532 Client IP RPC CA (Address Book) IP Persist 59533 59533 Client IP POP3 Generic TCP 110 110 None POP3 (secure) Generic TCP 995 995 None IMAP4 Generic TCP 143 995 None 8 Deploying Central Dispatch

Logging to Central Dispatch Exchange Role Scheduling Rule Type Cluster Port Server Port Affinity Type IMAP4 (secure) Generic TCP 993 993 None SMTP Generic TCP 25 25 None The following table summarizes the Central Dispatch configuration that will be employed in this guide: Rule Label Exchange Role Scheduling Rule Type Cluster Port(s) Server Port(s) HTTPS_ OWA, OA, EWS EAS,AD, ECP SSL3 443 443 RPC RPC Services IP Persist 135, 59532, 59533 135, 59532, 59533 POP3 POP3 Generic TCP 110, 995 110, 995 IMAP4 IMAP4 Generic TCP 143, 993 995, 993 SMTP SMTP Generic TCP 25 25 For more information about Central Dispatch installation, see CD6_Quick_Start.pdf and CD6_EvalGuide_10.pdf. 5.2. Logging to Central Dispatch To log in to Central Dispatch: 1. Access the URL http://ozone-2:8080/cd60 in the address bar of a browser. Note: Replace ozone-2 with the hostname or IP address of the node where you installed Central Dispatch application. The browser displays the Login page. Deploying Central Dispatch 9

Creating a new site 2. In the Login Name field, enter the login. Default login for Central Dispatch is admin. 3. In the Password field, enter the password configured for the login name. Default password for Central Dispatch is password. 4. Click the Login button. The browser displays the Central Dispatch dashboard. 5.3. Creating a new site To create a new site: 1. On the Central dispatch dashboard, click the Create new site link in the Commands section. 10 Deploying Central Dispatch

Creating a new site The browser displays the Create New Site page. 2. Enter the values in the fields as described in the following table: Field Label Site ID Node IP address or Hostname Admin Password Description A label for the Central Dispatch site. An internal ID that Central Dispatch uses to refer the site in the scripts. An IP address or a host name of the system at the site. The administrator password to access the Central Dispatch site. 3. Click the Create button. The browser displays the All Sites Dashboard page with a list of all the configured sites. Deploying Central Dispatch 11

Adding nodes to a site 5.4. Adding nodes to a site To add nodes to a site: 1. On the All Sites Dashboard page, click the site name in the Site Name column that you want to configure. The browser displays the Site Dashboard page. 2. Click the Nodes tab. The browser displays the Detail of Nodes page with the details of the site that you created. 12 Deploying Central Dispatch

Adding nodes to a site 3. Click the Add button. The browser displays the Add Node page. 4. Enter the appropriate information in the fields. 5. Click the OK button. The Nodes tab displays the information about two nodes. Deploying Central Dispatch 13

Adding virtual IP addresses to a site 5.5. Adding virtual IP addresses to a site After you add nodes to a site, you need to add virtual IP addresses. Virtual IP addresses must be in the same subnet as the Primary and Backup scheduler, which ensures high availability of the scheduler. To add a virtual IP addresses to a site: 1. On the All Sites Dashboard page, click the site name in the Site Name column that you want to configure. The browser displays the Site Dashboard page. 14 Deploying Central Dispatch

Adding virtual IP addresses to a site 2. Click the VIPs node. The browser displays the VIPs page. 3. Click the Add button. The browser displays the Add VIPs page. Deploying Central Dispatch 15

Configuring scheduling rules 4. In the Name field, enter the name of the virtual IP address. 5. In the Primary Scheduler field, select the IP address of the primary scheduler. 6. In the Backup Scheduler field, select the IP address of the backup scheduler. 7. Click the OK button. 5.6. Configuring scheduling rules This topic provide steps for creating the scheduling rules that decides what traffic is load balanced by Central Dispatch. To configure scheduling rules: 1. On the Central dispatch dashboard, click the Rules tab. The browser displays scheduling rules subtabs that you can use for configuration. 2. Click the SSL tab. 16 Deploying Central Dispatch

Configuring scheduling rules The browser displays the SSL page. 3. Click the Add button. The browser displays the Add SSL Rule page. 4. In the Timeout field, enter the timeout value in seconds for your SSL scheduling rule. You can enter the 3600 seconds (1 hour) as the timeout value for your SSL scheduling rule. 5. Click the Server tab at the left side. The browser displays a list of exchange servers. Deploying Central Dispatch 17

Configuring scheduling rules 6. From the list of servers, select the servers that you want to use for SSL scheduling rule. 7. Click the OK button. 8. Click the IP Persistence tab. The browser displays the IP Persistence Rules page. On this page, you can configure an IP Persistence scheduling rule. 9. Click the Add button. The browser displays the Add IP Persistence Rule page. 18 Deploying Central Dispatch

Configuring scheduling rules 10. In the Timeout field, enter the value in seconds for your IP persistence scheduling rule. You can enter the 3600 seconds (1 hour) as the timeout value for your IP persistence scheduling rule. 11. Click the Server tab at the left side. The browser displays a list of exchange servers. 12. From the list of servers, select the servers that you want to use for IP persistence scheduling rule. 13. Click the OK button. 14. Click the Generic TCP tab. The browser displays the Details of Generic TCP Rules page. Deploying Central Dispatch 19

Configuring scheduling rules On this page, you need to separately configure the Generic TCP scheduling rules for POP3, IMAP4, and SMTP. 15. Click the Add button. The browser displays the Add Generic TCP Rule page. 16. Add the values in the fields for configuring the POP3 scheduling rule. 17. Click the Server tab at the left side. 20 Deploying Central Dispatch

Configuring scheduling rules 18. From the list of servers, select the servers that you want to use for Generic TCP scheduling rule. 19. Click the OK button. 20. Click the Generic TCP tab again. The browser displays the Details of Generic TCP Rules page. 21. Click the Add button. The browser displays the Add Generic TCP Rule page. Deploying Central Dispatch 21

Configuring scheduling rules 22. Add the values in the fields for configuring the IMAP4 scheduling rule. 23. Click the Server tab at the left side. 24. From the list of servers, select the servers that you want to use for Generic TCP scheduling rule. 25. Click the OK button. 26. Click the Generic TCP tab again. The browser displays the Details of Generic TCP Rules page. 22 Deploying Central Dispatch

Configuring scheduling rules 27. Click the Add button. The browser displays the Add Generic TCP Rule page. 28. Add the values in the fields for configuring the SMTP scheduling rule. 29. Click the Server tab at the left side. Deploying Central Dispatch 23

Starting the site 30. From the list of servers, select the servers that you want to use for Generic TCP scheduling rule. 31. Click the OK button. The Generic TCP tab displays all the configured Generic TCP scheduling rules. 5.7. Starting the site To start the site: 1. On the Central dispatch dashboard, click the Site tab. The browser displays the All Sites Dashboard page. 24 Deploying Central Dispatch

Starting the site 2. In the Site Name column, click the site name link for the site that you want to start. The browser displays the Site Dashboard page. 3. From the navigation tabs, click the Settings tab. Deploying Central Dispatch 25

Starting the site The browser displays the General Settings page. 4. Click the License tab at the left side. The browser displays the License Settings page. 5. Click the New License Key button. The browser displays the New License Key dialog box. 6. In the License Key field, enter the license key. 7. Click the OK button. 26 Deploying Central Dispatch

Starting the site 8. Click the Dashboard tab. The browser displays the Site Dashboard page. 9. In the Commands section, click the Start Site link. The browser displays a dialog box for successfully starting the site. 10. Click the Close button to close the dialog box. Deploying Central Dispatch 27

Technical support Technical support If you have any trouble with Resonate Central Dispatch configuration for load balancing, you should: 1. Retry the action. Carefully follow the instructions written in the guide. 2. Check the documentation that came with your hardware for maintenance or hardware-related problems. 3. Note the sequence of events that led to the problem and the exact messages displayed. Have the documentation available. 4. If you continue to have a problem, contact Resonate Technical Support by sending an email message to the following email address: support@resonate.com. Deploying Central Dispatch 28

Glossary Glossary The following table provides the description of various important terms and acronyms used in this guide. Term CD CAS DNS EAC ECP OWA IMAP POP3 OA OAB RPC SMTP TCP VIP AD Description Resonate Central Dispatch Client Access Server Domain Name System Exchange Active Sync Exchange Control Panel Outlook Web Access Internet Message Access Protocol Post Office Protocol Outlook Anywhere (RPC over http) Offline Address Book RPC CAS Simple Mail Transfer Protocol Transmission Control Protocol Virtual Internet Protocol Address Autodiscover Service Deploying Central Dispatch 29

Index Index A adding nodes to a site... 12 adding virtual IP addresses to a site... 14 architecture... 5 exchange roles... 5 architecture diagram... 7 C Central Dispatch logging... 9 components to be load balanced... 6 configuring... 16 creating a new site... 10 E exchange roles... 5 G glossary... 29 H hardware requirements... 4 I introduction... 3 introduction to Central Dispatch load balancing 8 L load balancing... 8 load balancing MS Exchange... 5 logging to Central Dispatch... 9 N network diagram... 7 new site... 10 new site creation... 10 R requirements... 4 hardware... 4 operating system... 4 software... 4 S site adding nodes to a site... 12 adding virtual IP addresses to a site... 14 configuring scheduling rules... 16 starting... 24 software requirements... 4 starting a site... 24 T technical support... 28 30 Deploying Central Dispatch