Microsoft SharePoint 2010 Deployment with Coyote Point Equalizer

Transcription

1 The recognized leader in proven and affordable load balancing and application delivery solutions Deployment Guide Microsoft SharePoint 2010 Deployment with Coyote Point Equalizer Coyote Point Systems, Inc. Visit coyotepoint.com for more information.

2 Copyright 2012 Coyote Point Systems. All rights reserved. Coyote Point TM, Equalizer TM, Equalizer OnDemand TM, Equalizer VLB TM, Envoy TM, E205GX TM, E350GX TM, E450GX TM, E650GX TM and Smart Control TM are trademarks of Coyote Point Systems, Inc. in the U.S. and other countries. Windows TM and SharePoint TM are trademarks of Microsoft Corporation. All other brand or product names referenced in this document are the respective trademarks of their respective owners. The specifications and information contained in this document are subject to change without notice. All statements, information and recommendations are believed to be accurate but are presented without warranty of any kind, express or implied. Users must take full responsibly for their application thereof. Document version: 1.0 July 2012

3 Table of Contents Introduction... 1 About this Guide... 1 Prerequisites... 2 Deploying Equalizer with SharePoint Server Health Checks... 3 Affinity/Persistence... 3 Load Balancing Policy... 4 Network Topology Considerations... 4 SSL Offload & Acceleration... 4 Data Compression... 5 Configuring Equalizer for SharePoint... 5 Configuration Using the eqcli Interface... 5 Configure Servers... 5 Configure a Server Pool... 5 Add Server Instances to the Server Pool... 5 Configure Clusters... 6 Add a Certificate to Equalizer... 6 Add Certificate to HTTPS Cluster... 6 Configuration using the Administrative Interface (GUI)... 7 Configure Servers... 7 Configure Server Pools... 8 Add Server Instances to Server Pools... 9 Configure Clusters... 9 Add a Certificate to the HTTPS Cluster Configuring SharePoint Alternate Access Mappings to enable SSL offload Summary About Coyote Point Contact Us!... 13

4 This Page has been intentionally left blank.

5 Introduction SharePoint 2010 is a web-enabled Microsoft Office collaboration application that allows organizations to share information using a web browser. It provides centralized access to enterprise information on a corporate network and can help companies manage data and information easily. One of the most common applications of load balancing is to provide a single internet service from multiple servers. The SharePoint application uses a single server farm that is comprised of multiple servers. Software load balancers and reverse proxy solutions can be adequate for smaller deployments. Larger deployments benefit from the features and capacity provided by a hardware load balancer such as a Coyote Point Equalizer. Equalizer provides application-aware features that monitor server load and improve server response times by as much as 25%. In addition to basic load balancing, Equalizer provides: Automatic server and application health monitoring. Intelligent, application-aware load balancing policies (least connections, fastest response time, static weight, server agent, custom, and round-robin) including our adaptive policy that dynamically adjusts connection distribution based on load or response time. Content switching the ability to change load balancing behavior based on the content of a client request. Smart Events the ability to specify administrative actions based on observed behavior and conditions. SSL offloading and acceleration. Real time graphical performance monitoring and reporting. Redundant High Availability (HA) configurations. Tight integration with VMware Infrastructure to provide higher application performance in a virtualized or hybrid server environment. HTTP Compression to accelerate rendering and reduce bandwidth requirements (E650GX only). About this Guide This Deployment Guide describes the procedures and configuration used in the configuration of a single Coyote Point Equalizer into a typical SharePoint environment using EQ/OS 10 firmware - the latest firmware for the Equalizer GX series appliances. The eqcli command line interface provides complete administrative control over Equalizer. The webbased Administrative Interface (GUI) offers drag and drop functionality to modify your configuration. This guide provides instructions for performing Equalizer configuration using both the eqcli interface and the GUI. The Equalizer Administration Guide, which can be downloaded from the Coyote Point web site provides additional information about the eqcli and GUI as well as other Equalizer configuration details. 1 Deployment Guide: Microsoft SharePoint 2010 Deployment with Coyote Point Equalizer

6 Prerequisites Prior to installation, it is recommended that you review Microsoft s overview of load balancing recommendations in SharePoint Refer to the hyperlink below: A fundamental understanding of the following key structural elements in a SharePoint environment is required in order to correctly deploy and support SharePoint 2010: Server farms - The top-level element of a logical architecture design for SharePoint Server. Web applications - An IIS Web site that is created and used by SharePoint Server Content databases - Provides storage Web application content. Content can be separated into multiple content databases at the site collection level. Site collection - A set of web sites that have the same owner and share administration settings. In addition, it is recommended that you use a Coyote Point Equalizer with the latest EQ/OS 10 firmware in the configuration. Refer to the Equalizer Administration Guide for upgrade procedures. Deploying Equalizer with SharePoint 2010 If you are setting up a new SharePoint deployment, we recommend that you first set up your configuration without Equalizer. You should then verify each of your intended client access methods, and then follow this document to deploy Equalizer into that configuration. Logically, Equalizer resides between clients accessing SharePoint and the SharePoint servers, as shown below in the sample shown in Figure 1. In this sample: Two Web/IIS SharePoint Frond-End servers are used. Two server instances are part of a server pool. A Layer 7 HTTPS cluster communicates with the two SharePoint servers via SSL. A Layer 7 HTTP cluster redirects client requests to a secure HTTPS cluster. 2 Deployment Guide: Microsoft SharePoint 2010 Deployment with Coyote Point Equalizer

7 Figure 1. Deployment of Coyote Point Equalizer with SharePoint (Logical Topology view) Server Health Checks By default, Equalizer probes server health using ICMP and TCP probes. You can also enable Active Content Verification (verifies server availability via specific content) or server agents (user-supplied programs running on the server), if more specific probing is desired. For more information on Health Check refer to Server Health Check Probes in the Equalizer Administration Guide. Affinity/Persistence Microsoft recommends that you enable affinity. In the sample deployment presented, Equalizer uses persistence. If you have a custom topology requirement, you may want to configure the affinity differently. Refer to the hyperlink below to view Microsoft recommendations. 3 Deployment Guide: Microsoft SharePoint 2010 Deployment with Coyote Point Equalizer

8 Load Balancing Policy Microsoft recommends using Round-robin load balancing policy for each of the clusters used in this deployment. Round-robin load balancing distributes requests equally among all the servers in the cluster. Equalizer dispatches the first incoming request to the first server, the second to the second server, and so on. When Equalizer reaches the last server, it repeats the cycle. If a server in the cluster is down, Equalizer does not send requests to that server. This is the default method. Network Topology Considerations Equalizer enables the spoof option by default on all clusters all servers will see the client s IP address as the source IP in all packets received from Equalizer. This is the recommended setting and means that servers in the cluster use Equalizer as the default gateway for routing responses back to clients. This is accomplished by either making Equalizer the default gateway on the servers or by configuring static routes on the servers. This also avoids a situation where the server sends response packets directly back to the client and not through Equalizer. In that case a client will reject reply packets because they do not belong to an established connection. From the client side, it would appear as if the server is not responding. (Note that clients connect to an Equalizer cluster IP address, not a server IP address, so the clients are expecting a packet to come back to them via the Equalizer cluster IP.) Disabling the spoof option activates Source Network Address Translation (SNAT) Equalizer translates the client IP address to Equalizer s IP address on the VLAN/subnet. In that case, the server receiving the request will see Equalizer s IP address as the source IP address. SSL Offload & Acceleration Equalizer performs SSL offload for Layer 7 HTTPS clusters. Instructions in this guide show you how to upload a server certificate to an HTTPS cluster on Equalizer as well as the other necessary steps to ensure that page content and search information is delivered properly while offloading SSL. Equalizer can be configured using a Layer 4 cluster, however doing so has several consequences and is not recommended: If using a Layer 4 cluster, all SSL processing will be performed on the server since SSL offload is not available. Persistence would be provided by the IP address instead of cookies, and you may need a separate SSL certificate for any services provided via separate clusters. We do not recommend using Layer 4 clusters unless you need to support clients that are not able to use cookie persistence. The procedures in this guide assume that a single Layer 7 HTTPS cluster provides client access to the SharePoint environment, and that a second Layer 7 HTTP cluster redirects back to the more secure HTTPS cluster. E450GX and E650GX model Equalizers provide SSL Acceleration via special hardware available only on those models. 4 Deployment Guide: Microsoft SharePoint 2010 Deployment with Coyote Point Equalizer

9 Data Compression Data compression can be a useful feature in SharePoint deployments. To use SharePoint more efficiently and increase performance Coyote Point can provide dynamic data compression. This is available on the Equalizer E650GX model and enabled on a cluster-by-cluster basis by turning on the compress check box in a cluster s Networking configuration. Dynamic data compression performed by the E650GX provides increased throughput in most configurations that is 3 to 5 times the throughput observed when compression is not used. Configuring Equalizer for SharePoint Configuration Using the eqcli Interface This guide assumes that you have already set up Equalizer within your organization s network. This includes registration, licensing, and initial network configuration. In addition: All SharePoint services are delivered via HTTPS whether clients are located on a private LAN or connecting via internet. An HTTP redirect cluster is configured on the Equalizer ensures all users are redirected to a secure page to login and access information. Since Equalizer is performing SSL offload and the SharePoint IIS configuration occurs over port 80 it is possible to deliver SharePoint services without encryption. The redirect cluster helps to ensure security. Prior to beginning these procedures we recommend that you review Using the CLI in the EQ/OS 10 Administration Guide. It provides additional information for using the EQ/OS 10 eqcli interface. 1. Log in to eqcli. 2. Set up VLANs in accordance with the procedures in the EQ/OS 10 Administration Guide. Proceed with the following to configure Equalizer for SharePoint using eqcli command line syntax using Figure 1 for reference. Configure Servers 3. Create two servers on Equalizer by entering the following: eqcli > server moss-fe1 proto tcp ip port 80 eqcli > server moss-fe2 proto tcp ip port 80 Configure a Server Pool 4. Create a server pool by entering: eqcli > srvpool moss-fe-pool_80 policy round-robin respv 3 Add Server Instances to the Server Pool In server pool moss-fe-pool_80, create two server instances for the servers created in Step 3 by entering: eqcli > srvpool moss-fe-pool_80 si moss-fe1 weight 100 eqcli > srvpool moss-fe-pool_80 si moss-fe2 weight Deployment Guide: Microsoft SharePoint 2010 Deployment with Coyote Point Equalizer

10 Configure Clusters 5. Create a Layer 7 HTTPS cluster by entering: eqcli > cluster SP_fe_https proto https ip port 443 srvpool moss-fe-pool_80 6. Create the redirect, Layer 7 HTTP cluster by entering: eqcli > cluster SP_fe_http proto http ip port 80 srvpool mossfe-pool_80 Add a Certificate to Equalizer 7. Add an SSL certificate store for the HTTPS cluster SP_fe_https by entering: eqcli > certificate name Add Certificate to HTTPS Cluster If desired, refer to Certificate Commands in the EQ/OS 10 Administration Guide for more information. 8. Import the certificate and its associated private key using either of the following methods: a. If the certificate resides on an FTP site, enter commands similar to the following, substituting the IP address and path on your FTP or HTTP site from which the certificate and private key can be downloaded: eqcli > certificate name eqcli-name> certfile ftp://[username]:[password]@ftp_svr_ip _or_hostname/path/filename eqcli-name> keyfile ftp://[username]:[password]@ftp_svr_ip _or_hostname/path/filename b. If you want to cut and paste the certificate and key using an editor, use commands similar to the following: eqcli-name> certfile edit eqcli-name> keyfile edit Certificates and keys must be in PEM or PKCS12 format. If a chain of certificates and keys must be uploaded, ensure that all the certificates are in one file and all the private keys are in another. 6 Deployment Guide: Microsoft SharePoint 2010 Deployment with Coyote Point Equalizer

11 Configuration using the Administrative Interface (GUI) Configure Equalizer using the Administrative Interface (GUI) as follows: 1. Log in to the GUI. Once logged into the GUI and you add objects (clusters, servers and server pools) they are displayed in the left navigational pane (frame), while configuration details are displayed and modified in the right frame: Click an object in the left frame to display the configuration details for that object. Right-click an object in the left frame to display commands for that object. Click Equalizer to display global configuration parameters. Click Help > Context Help at any time to display documentation for the currently displayed configuration details. Refer to Using the GUI in the EQ/OS 10 Administration Guide for additional information. Configure Servers 2. Create the servers by right-clicking on the Servers icon on the left navigation pane of the GUI and selecting Add Server. 7 Deployment Guide: Microsoft SharePoint 2010 Deployment with Coyote Point Equalizer

12 3. Enter the server details for each in the Add Server form displayed. Click on Commit after each entry. An example of a completed form is as follows: 4. Repeat this procedure for each of the SharePoint servers using the following details: Protocol: TCP Server name: moss-fe1 IP: Port: 80 Protocol: TCP Server name: moss-fe2 IP: Port: 80 After you have clicked on Commit, the new server will appear on the navigation pane on the left. Configure Server Pools 5. Right-click on Server Pools on the navigation pane and select Add Server Pool. The server pool entry form will be displayed. 6. Create the Server Pool. (moss-fe-pool_80) Make sure that the Policy is round-robin. Click on Commit after entering a new Server Pool. The new Server Pool will appear on the navigation pane on the GUI. 8 Deployment Guide: Microsoft SharePoint 2010 Deployment with Coyote Point Equalizer

13 Add Server Instances to Server Pools 7. Add server instances to the servers created in steps 2, 3 and 4 into a server pool. As discussed previously, drag and drop functionality is available on the GUI so that when a server is instance is dropped into a server pool, a Specify Server Instance Weight form will appear as shown below. Add the two server instances (moss-fe1 and moss-fe2) to the Server Pool moss-fe-pool_ By default, the Server Instance Weight of 100 is for each server instance. If you need the server instance to take traffic after creating the cluster in the next step, unselect the Quiesce checkbox. Click on Commit when finished. When you have finished the Server Pool branches on the left navigational pane will appear on the left navigation pane of the GUI. Configure Clusters 9. Create a Layer 7 HTTPS cluster by right-clicking on Clusters on the navigation pane and selecting Add Cluster. The Add Cluster form will be displayed. 10. Enter cluster details for the HTTPS cluster using the following details: Cluster: SP_fe_https (Layer 7) IP Address: Port: 443 Type: https Server Pool: moss-fe-pool_ Repeat steps 9 and 10 however this time for the redirect HTTP cluster. Use the following details. Cluster: SP_fe_http (Layer 7) IP Address: Port: 80 Type: http Server Pool: moss-fe-pool_80 9 Deployment Guide: Microsoft SharePoint 2010 Deployment with Coyote Point Equalizer

14 12. Associate the Server Pools specified in steps 10 and 11 with the Clusters by selecting the desired Server Pool from the navigation pane, dragging it and then dropping it onto the Cluster. 13. After clusters are added they appear on the navigation pane. Click on each cluster to activate a cluster configuration form. A sample of the cluster configuration screen is shown below. Refer to the EQ/OS 10 Administration Guide and Microsoft for additional information for configuring clusters for your specific configuration. When you have completed creating the HTTPS and HTTP redirect cluster and associated server pools with the clusters the associated Server Pools should appear as branches on the Cluster tree on the navigation pane. Add a Certificate to the HTTPS Cluster 14. Add an SSL certificate store for the HTTPS cluster SP_fe_https by either: Right-clicking on Equalizer in the navigation pane and selecting Add Certificate. or Clicking on Equalizer in the navigation pane and then clicking on the Global > Add Certificate. Either method will display the Add Certificate form. 15. Click on Choose File and navigate to the location of the stored certificate and associated key file. Certificates and keys must be in PEM or PKCS12 format. If a chain of certificates and keys must be uploaded, ensure that all of the certificates are in the certificate file and all the private keys are in the private key file. 16. Select the files to upload to Equalizer and enter a name for the certificate in the Name field. 17. Click on Commit to upload the files. 10 Deployment Guide: Microsoft SharePoint 2010 Deployment with Coyote Point Equalizer

15 Configuring SharePoint Alternate Access Mappings to enable SSL offload For configuration with Equalizer, you will need to modify SharePoint Alternate Access Mappings to enable SSL Offload. In addition, after modification of the mappings it might be necessary to reset your current crawled content database and perform a new full crawl. Disclaimer: The following procedure provides SharePoint 2010 procedures and screen captures using the SharePoint Central Administration Screen. The procedures and screen captures are the property of Microsoft and may change without notice. For more information go to: For each public URL to be deployed you must first modify the URL protocol of the internal URL associated with that URL and zone from to and then recreate the If you attempt to simply add a new URL for HTTPS, SSL offload will not function properly. To configure SharePoint Alternate Access Mappings: 1. Click on Application Management from SharePoint Central Administration navigation pane. 2. Click on Configure Alternate Access Mappings in the main window, under Web Applications. 3. From the Internal URL list, click on the Internal URL corresponding with the Public URL you want to be accessible through Equalizer. The Edit Internal URLs page will be displayed. 4. In the URL protocol, host and port field, change the protocol from to Take note of the URL for use in step 7. Figure 2. Editing Internal URL 5. Click on OK. The Alternate Access Mappings page will be redisplayed. 6. Click on Add Internal URLs on the menu bar. Type the same internal URL used in step 4 in the URL protocol, host and port box, but use the protocol. This allows access to the non-ssl site from behind Equalizer. Click Save. Figure 3. Adding the HTTP Internal URL 7. Add the new internal URL(s) to the list of content sources of Search Administration. 11 Deployment Guide: Microsoft SharePoint 2010 Deployment with Coyote Point Equalizer

16 8. Click on Application Management from the navigation pane and then click Manage service applications from Service Applications. 9. Click on the name of your Search Service application. In the example, SharePoint Enterprise Search Service is used. 10. Click on Content Sources in the navigation pane and then click New Content Source on the Menu bar. 11. Type a name in the Name box. In the example above, is used. 12. Type the appropriate HTTPS URL in the Start Addresses section. In the example, is used. All other settings are optional. Click on OK (see Figure 4). 13. Repeat this entire procedure for each public URL deployed behind Equalizer. Figure 4 Adding Content Source Summary Equalizer provides the load balancing, application acceleration, and high availability features demanded by medium to large SharePoint 2010 configurations. This document has presented a systematic guide to configuring Equalizer s features for a SharePoint 2010 environment. About Coyote Point Coyote Point has been an application delivery innovator for over 13 years. In 1999 we introduced our first server load balancer and we ve shipped thousands of units since then. Our company is singularly focused on providing application aware server load balancing and application acceleration solutions that are deployed by small, medium and large enterprises, including some of the busiest sites on the web. At Coyote Point, we pride ourselves on delivering value to our customers. Our products perform as advertised and are easy and enjoyable to use and deploy. With a versatile and powerful architecture, we provide the highest value while enabling customers to optimize businesses that rely on Internetbased infrastructure. 12 Deployment Guide: Microsoft SharePoint 2010 Deployment with Coyote Point Equalizer

17 Contact Us! Discuss with us your application delivery challenges and the world-class benefits that Coyote Point s affordable, non-stop, application acceleration and load balancing ADC technology can bring to your business. Please see our Contact Page on the web at 13 Deployment Guide: Microsoft SharePoint 2010 Deployment with Coyote Point Equalizer