Application Delivery Controller (ADC) Implementation Load Balancing Microsoft SharePoint Servers Solution Guide

Transcription

1 Application Delivery Controller (ADC) Implementation Load Balancing Microsoft SharePoint Servers Solution Guide January, 2009 North America Radware Inc. 575 Corporate Dr., Lobby 1 Mahwah, NJ Tel: (888) International Radware Ltd. 22 Raoul Wallenberg St. Tel Aviv 69710, Israel Tel:

2 Table of Contents Introduction... 3 AppDirector... 3 Microsoft SharePoint Tested Example Configurations... 3 Example Configuration... 4 AppDirector Active... 5 Network Configuration... 5 Farm Configuration... 5 Servers Configuration... 5 Compression Configuration... 6 Cache Configuration... 6 SSL Policy Configuration... 6 Layer 4 Configuration... 6 AppDirector Health Monitoring... 7 VRRP Configuration... 7 Mirroring Configuration... 8 AppDirector Backup... 8 Network Configuration... 8 VRRP Configuration... 8 Mirroring Configuration... 9 Note... 9 Microsoft SharePoint Front-End Servers Server 1 Network Configuration Server 2 Network Configuration Technical Support Page 2

3 Introduction Organizations looking to improve and enhance the collaboration between work teams often use Microsoft SharePoint to deliver these capabilities. As opposed to enhancing collaboration, to avoid negatively impacting productivity this type of solution requires a high level of availability and performance. Radware, which specializes in fast, reliable and secure delivery of applications to users, integrates with Microsoft SharePoint to deliver a robust and scalable solution. This guide presents a basic integration solution in which Radware s load balancing and acceleration product, AppDirector, is set up in front of a SharePoint environment to ensure its availability and performance. AppDirector AppDirector delivers performance improvement, availability assurance and acceleration of content delivery to clients using Microsoft SharePoint by utilizing load-balancing, health checks and Web acceleration capabilities, while ensuring session persistency between clients and servers. Microsoft SharePoint 2007 Microsoft Office SharePoint Server 2007 provides a single, integrated location where employees can efficiently collaborate with team members, find organizational resources, search for experts and corporate information, manage content and workflow, and leverage business insight to make better-informed decisions. Collaboration - Allow teams to work together effectively, collaborate on and publish documents, maintain task lists, implement workflows, and share information through the use of wikis and blogs. Portals - Create a personal MySite portal to share information with others and personalize the user experience and content of an enterprise Web site based on the user s profile. Enterprise Search - Quickly and easily find people, expertise, and content in business applications. Enterprise Content Management - Create and manage documents, records, and Web content. Business Process and Forms - Create workflows and electronic forms to automate and streamline your business processes. Business Intelligence - Allow information workers to easily access critical business information, analyze and view data, and publish reports to make more informed decisions. Tested Example Configurations This solution guide includes an example configuration that was tested by Radware. When implementing this example configuration, note the following: - Health Monitoring uses HTTP and HTTPS protocol checks. - Throughout this guide, reference is made to the Radware pre-configured certificate, but you can import a certificate or create a self-signed certificate in AppDirector. For more information on exporting, importing, or creating a certificate, see the AppDirector User Guide. - Persistency is performed by AppDirector inserting a cookie into the HTTP traffic. Page 3

4 Example Configuration In this scenario, two Microsoft SharePoint 2007 servers were used as front-end servers and one SharePoint back-end server was used to hold all SharePoint data. AppDirector performed load balancing on the two SharePoint front-end servers using SSL offloading, traffic compression and caching. The following is a list of software and hardware used in testing this configuration: - AppDirector version 2.0 running on OnDemand Switch 2 - SharePoint Microsoft SharePoint Clients - IE 7.0, Firefox LDAP server Windows 2003 Active Directory The following figure illustrates the configuration that was tested: FIGURE 1 CONFIGURATION 1 Page 4

5 The following are the settings for each of the listed devices in this configuration: AppDirector Active AppDirector Backup Microsoft SharePoint Front End Servers AppDirector Active The following are the settings for the Active AppDirector: Network Configuration Farm Configuration Servers Configuration Compression Configuration Cache Configuration SSL Policy Configuration Layer 4 Configuration AppDirector Health Monitoring VRRP Configuration Mirroring Configuration Network Configuration 1. Create IP /16 on port 1 2. Create /24 on port 2 3. Create default route to Farm Configuration 1. Create a farm named sharepoint.farm in AppDirector -> Farms -> Farm Table with these parameters: - Farm Name sharepoint.farm - Aging Time Session mode ServerPerSession - Dispatch Method - Cyclic - Connectivity checks No Checks 2. Enable Insert Cookie for HTTP Persistency in AppDirector -> Farms -> Extended Parameters. Servers Configuration 1. Create a server named sharepoint.server.1 and attach it to the farm sharepoint.farm in AppDirector -> Servers -> Application Servers -> Table with these parameters: - Farm Name sharepoint.farm - Server Address Server Name - sharepoint.server.1 Page 5

6 2. Create a server named sharepoint.server.2 and attach it to the farm sharepoint.farm in AppDirector -> Servers -> Application Servers -> Table with these parameters: - Farm Name sharepoint.farm - Server Address Server Name - sharepoint.server.2 Compression Configuration Create a compression policy named HTTP.compression.policy in AppDirector -> Servers -> Layer4 Traffic configuration -> Compression Policy with these parameters: - Policy Name HTTP.compression.policy - Algorithm GZIP - Compression lever - 1 Cache Configuration Create a compression policy named Cache.policy in AppDirector -> Servers -> Layer4 Traffic configuration -> Caching Policy with these parameters: - Admin Status Enable SSL Policy Configuration Create an SSL policy in AppDirector -> L4 Traffic Redirection -> SSL Policy with these parameters: - Policy name HTTPS.policy - Certificate radware - Listening Server Port 80 (AppDirector listens to HTTP port clear traffic) Note: Throughout this guide, reference is made to the radware pre-configured certificate, but you can import a certificate or create a new certificate in AppDirector. For more information on exporting, importing, or creating a certificate, see the AppDirector User Guide. Layer 4 Configuration Create a Layer 4 policy for HTTPS Traffic named Sharepoint.HTTPS in AppDirector -> Layer 4 Traffic Redirection -> Layer 4 Policies with these parameters: - Virtual IP L4 Protocol TCP - L4 Port L4 Policy Name Sharepoint.HTTPS - Application - HTTPS - Farm Name sharepoint.farm - SSL Policy HTTPS.policy - Caching Policy - Cache.policy - Compression Policy - HTTP.compression.policy Page 6

7 Create a Layer 4 Policy for HTTP Traffic named Sharepoint.HTTP in AppDirector AppDirector -> Layer 4 Traffic Redirection -> Layer 4 Policies with these parameters: - Virtual IP L4 Protocol TCP - L4 Port 80 - L4 Policy Name Sharepoint.HTTP - Application - HTTP - Farm Name sharepoint.farm - Caching Policy - Cache.policy - Compression Policy - HTTP.compression.policy AppDirector Health Monitoring 1. Enable Health Monitoring in Health Monitoring -> Global Parameters. 2. Create a check for HTTP on server in Health Monitoring -> Check Table: - Check name sharepoint.server.1 - Method HTTP - Dest IP Dest Port Create a check for HTTP on server in Health Monitoring -> Check Table with these parameters: - Check name sharepoint.server.2 - Method HTTP - Dest IP Dest Port Bind the check sharepoint.server.1 to Server sharepoint.farm in Health Monitoring -> Binding Table. 5. Bind the check sharepoint.server.2 to Server sharepoint.farm in Health Monitoring -> Binding Table. VRRP Configuration 1. Enable VRRP in AppDirector -> Redundancy -> Global Configuration with these parameters: - IP Redundancy Admin Status VRRP - Interface Grouping Enable - ARP with interface grouping Send - Backup Fake ARP Enable - Backup Interface Grouping Enable 2. Create Virtual Router interfaces in AppDirector -> Redundancy -> VRRP -> Virtual Router Table with these parameters: - IF Index 1 - VR ID 1 - Priority 255 (Highest number is Active device) - Primary IP Leave all other options as default Page 7

8 3. Create Virtual Router interfaces in AppDirector -> Redundancy -> VRRP -> Virtual Router Table with these parameters: - IF Index 2 - VR ID 2 - Priority 255 (Highest number is Active device) - Primary IP Leave all other options as default 4. Create Associated IP Addresses in AppDirector -> Redundancy -> VRRP -> Associated IP Addresses with these parameters: - IF Index 1, VR ID 1, Associated IP IF Index 1, VR ID 1, Associated IP IF Index 2, VR ID 2, Associated IP Mirroring Configuration 1. Enable Mirroring in AppDirector -> Redundancy -> Mirroring -> Active Device Parameters with these parameters: - Client Table Mirroring Enable - Session Id Table Mirroring Enable 2. Add Mirror device in AppDirector -> Redundancy -> Mirroring -> Mirror Device Parameters with the following parameter: - Mirror Device IP AppDirector Backup The following are the settings for the Backup AppDirector: Network Configuration Redundancy VRRP Configuration Mirroring Configuration Network Configuration 1. Create IP /16 on port 1 2. Create /24 on port 2 3. Create default route to Copy all configuration from the Active AppDirector device VRRP Configuration 1. Enable VRRP in AppDirector -> Redundancy -> Global Configuration with these parameters: - IP Redundancy Admin Status VRRP - Interface Grouping Enable - ARP with interface grouping Send - Backup Fake ARP Enable - Backup Interface Grouping Enable Page 8

9 2. Create Virtual Router interfaces in AppDirector -> Redundancy -> VRRP -> Virtual Router Table with these parameters: - IF Index 1 - VR ID 1 - Priority 100 (Highest number is Active device) - Primary IP Leave all other options as default 3. Create Virtual Router interfaces in AppDirector -> Redundancy -> VRRP -> Virtual Router Table with these parameters: - IF Index 2 - VR ID 2 - Priority 100 (Highest number is Active device) - Primary IP Leave all other options as default 4. Create Associated IP Addresses in AppDirector -> Redundancy -> VRRP -> Associated IP Addresses with these parameters: - IF Index 1, VR ID 1, Associated IP IF Index 1, VR ID 1, Associated IP IF Index 2, VR ID 2, Associated IP Mirroring Configuration 1. Enable Mirroring in AppDirector -> Redundancy -> Mirroring -> Backup Device Parameters with the following parameter: - Mirroring Status Enable Note 2. Add Mirror device in AppDirector -> Redundancy -> Mirroring -> Mirror Device Parameters with the following parameter: - Mirror Device IP If you have APSolute Insite installed, use the Insite wizard to copy and convert the Active AppDirector configuration choosing the redundancy mode VRRP or Proprietary. For more information on this wizard, see the AppDirector User Guide. Page 9

10 Microsoft SharePoint Front-End Servers Server 1 Network Configuration 1. Create IP /24 2. Create default route to Add the VIP IP to the alternate access mapping on the SharePoint server using the Central Administration interface under Operations -> Alternate Access Mapping. This is done only once, so there is no need to add it in the second front-end server. Server 2 Network Configuration 1. Create IP /24 2. Create default route to Technical Support Radware offers technical support for all of its products through the Radware Certainty Support Program. Please refer to your Certainty Support contract, or the Radware Certainty Support Guide available at: For more information, please contact your Radware Sales representative or: U.S. and Americas: (866) International: +972(3) Radware, Ltd. All Rights Reserved. Radware and all other Radware product and service names are registered trademarks of Radware in the U.S. and other countries. All other trademarks and names are the property of their respective owners. Printed in the U.S.A. Page 10