Barracuda Load Balancer Administrator’s Guide Version 2.3 Barracuda Networks Inc. 3175 S. Winchester Blvd. Campbell, CA 95008 http://www.barracuda.
Copyright Notice Copyright 2004-2008, Barracuda Networks www.barracuda.com v2.3-081015 All rights reserved. Use of this product and this manual is subject to license. Information in this document is subject to change without notice. Trademarks Barracuda Load Balancer is a trademark of Barracuda Networks. All other brand and product names mentioned in this document are registered trademarks or trademarks of their respective holders.
Contents Chapter 1 – Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . 7 Overview . . . . . . . . . . . . . . . . . . . . Powerful Enterprise-Class Solution . . . . . Features of the Barracuda Load Balancer . . . Load balancing for all IP-based applications Easy Setup and Maintenance . . . . . . . . Intrusion Prevention System . . . . . . . . Auto-Discover . . . . . . . . . . . . . . . . Layer 4 IP Persistence . . . . . . . . . . . Layer 7 Cookie Persistence . . . . . . . . .
Creating Services . . . . . . . . . . . . . . . . . . . . . . . . . Administrative Settings . . . . . . . . . . . . . . . . . . . . . . . . Controlling Access to the Administration Interface . . . . . . . . Customizing the Appearance of the Web Interface . . . . . . . . Setting the Time Zone of the System . . . . . . . . . . . . . . . Enabling SSL for Administration . . . . . . . . . . . . . . . . . Maintaining the Barracuda Load Balancer . . . . . . . . . . . . . .
Barracuda Load Balancer 640 . . . . . . Back Panel of the Barracuda Load Balancer . Barracuda Load Balancer, all models . . . Hardware Compliance . . . . . . . . . . . . Notice for the USA . . . . . . . . . . . . Notice for Canada . . . . . . . . . . . . . Notice for Europe (CE Mark) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
vi Barracuda Load Balancer Administrator’s Guide
Chapter 1 Introduction This chapter provides an overview of the Barracuda Load Balancer and includes the following topics: • • Overview on page 8 Features of the Barracuda Load Balancer on page 9 Introduction 7
Overview Organizations use load balancers to distribute traffic across a set of servers in their network. In the event a server goes down, the load balancer automatically detects this failure and begins forwarding traffic to the remaining functioning servers, maintaining high availability of the services provided by the servers.
Features of the Barracuda Load Balancer The Barracuda Load Balancer is designed with the following features: Load balancing for all IP-based applications ..................................... 9 Easy Setup and Maintenance............................................................... 9 Intrusion Prevention System .............................................................. 10 Auto-Discover .................................................................................... 11 Layer 4 IP Persistence........
Intrusion Prevention System Many security technologies are integrated into the Barracuda Load Balancer. The set-and-forget Intrusion Prevention System (IPS) helps secure your network, even if you may have missed a patch or if an exploit manages to get past your existing security. The Barracuda Load Balancer will automatically block any exploits that are detected across any protocol; no configuration is required. The built-in IPS also provides Denial of Service (DoS) protection for all load-balanced servers.
Figure 1.1: Barracuda Energize Updates Auto-Discover All models of the Barracuda Load Balancer support Auto-Discovery of Real Servers and Services, to ensure quick and easy deployment of new servers. For common services, there's no need to manually configure each port. The Barracuda Load Balancer can automatically detect which services are running on a specified server and save deployment and configuration time.
Cookie persistence is not available if using the Direct Server Return (DSR) mode of deployment unless the application manages the cookies. This is because the cookie is inserted into the data stream by the Barracuda Load Balancer when the traffic is outbound. In DSR the traffic goes directly to the client, bypassing the Barracuda Load Balancer, so there is no opportunity to insert a cookie.
High Availability With simple setup through the Web administrative interface, the Barracuda Load Balancer supports High Availability configurations. Just point the backup Barracuda Load Balancer to the primary Barracuda Load Balancer's management IP address to synchronize configurations and establish a highly available network that brings your server farm to enterprise grade availability.
Barracuda Load Balancer Administrator’s Guide
Chapter 2 Load Balancing Concepts This chapter provides an overview of the Barracuda Load Balancer and includes the following topics: • • Barracuda Load Balancer Terminology on page 16 Load Balancer Deployment Options on page 19 Load Balancing Concepts 15
Barracuda Load Balancer Terminology The following is a list of some of the terms used by the Barracuda Load Balancer. Table 2.1: Barracuda Load Balancer terminology Term Description Service A combination of a Virtual IP (VIP) and one or more TCP/UDP ports that the Service is to listen on. Traffic arriving over the designated port(s) to the specified Virtual IP is directed to one of the Real Servers that are associated with a particular Service.
Term Description Physical Network A group of systems that are physically connected to each other, usually over a switch or VLAN. See Figure 2.2: A physical network layout using Route-Path on page 18 for an example. WAN IP Address or Management IP Address The IP address assigned to the Barracuda Load Balancer, which is also the IP address used to access the Web interface. This address must be different than the Virtual IP addresses assigned to the Services.
Figure 2.
Load Balancer Deployment Options Services on the Barracuda Load Balancer can be deployed in the following three modes: Route-Path (Recommended)............................................................... 19 Bridge-Path........................................................................................ 21 Direct Server Return ..........................................................................
Figure 2.3: Sample Route-Path network layout Deploying Route-Path In the Route-Path method of deployment, the Virtual IP addresses must be on the same subnet as the Barracuda Load Balancer. The Real Servers must be on a subnet separate from the VIPs and the Barracuda Load Balancer. This may require changing the IP addresses of your Real Servers. Normally the Real Servers are on an isolated IP network behind the Barracuda Load Balancer.
If you need to remotely administer your Real Servers individually then you should create new Services, each of which only load balances a single Real Server. Each Real Server must list the LAN IP address of the Barracuda Load Balancer as its gateway IP address. Note that Real Servers in the Route-Path deployment cannot access their own VIPs, or any other VIPs on their own Barracuda Load Balancer.
Figure 2.4: Sample Bridge-Path network layout Deploying Bridge-Path In Bridge-Path mode, the Real Servers must be physically isolated behind the Barracuda Load Balancer. This means that each Real Server is no longer visible on the network if the Barracuda Load Balancer becomes unavailable (a separate switch is absolutely required for models 440 and below). Each Real Server must be one hop away from the LAN port on the Barracuda Load Balancer.
through their own interfaces. This implementation requires enabling a non-ARPing loopback adapter, a feature that can be found on most server operating systems. Your applications may need to be explicitly bound to the loopback adapter. The Barracuda Load Balancer does not alter packets when it delivers them to the Real Servers. Instead, only the destination MAC address is changed to match the Real Server that is to handle the request, as shown in Figure 2.5. Figure 2.
flat network and have to access databases on other subnets, or if the Real Servers are on the same subnet as the Barracuda Load Balancer and the configuration cannot be changed, then DSR is recommended. • DSR can assist in optimizing Windows to Windows communication between Real Servers. If you have Real Servers on active Windows domains where the domain controllers are not on the same subnet, and Layer 7 features are not required, use DSR. See Figure 2.6 for an example of this type of layout.
DSR with Route-Path or Bridge-Path The Barracuda Load Balancer supports deployment of multiple Services simultaneously, but all Services must be configured as either Route-Path (recommended) or Bridge-Path. If Direct Server Return is desired for at least one of the load-balanced Services, then it can be configured in conjuction with the chosen deployment mode. Direct Server Return in conjunction with Bridge-Path is not recommended.
to a series of switches that eventually reach the WAN port of the Load Balancer without going through any other machines. If you specify Route-Path deployment for the Barracuda Load Balancer, but only use Real Servers with Direct Server Return enabled, the physical LAN port is not used by the Barracuda Load Balancer, and the LAN adapter may remain undefined in the Web administration interface.
listen :80 listen :80 where: is the Virtual IP Address for the Service is the actual IP Address for the Real Server 4. To check if the loopback adapter is working, make sure the Real Server is bound to the loopback adapter’s IP address. Output from the ifconfig command should show the presence of the loopback adapter.
Barracuda Load Balancer Administrator’s Guide
Chapter 3 Getting Started This chapter provides general instructions for installing, configuring and maintaining the Barracuda Load Balancer. It includes the following topics: Initial Setup ....................................................................................... 30 Administrative Settings ...................................................................... 36 Maintaining the Barracuda Load Balancer.......................................
Initial Setup These are the general steps to set up your Barracuda Load Balancer. For more detailed instructions for each step, see the following reference pages. Preparing for Installation .................................................................. 30 Connecting the Barracuda Load Balancer to the Network ............... 31 Configuring WAN IP Address and Network Settings ......................... 31 Configuring Your Corporate Firewall ...............................................
Connecting the Barracuda Load Balancer to the Network 1. Fasten the Barracuda Load Balancer to a standard 19-inch rack or other stable location. Caution Do not block the cooling vents located on the front and rear of the unit. 2. If using Route-Path, then the network switch referenced in the following steps may be the same physical switch. If using Bridge-Path, however, then separate switches on different Layer 2 networks must be used. 2a.
The User Confirmation Requested window displays the current IP configuration of the Barracuda Load Balancer. 3. Using your Tab key, click Change and click Enter to change the WAN IP configuration. 4. Enter the new WAN IP address, netmask, and default gateway for your Barracuda Load Balancer. Click Save to enter your changes. (The Primary and Secondary DNS fields are optional at this time, but if not entered at this step then they must be entered in Step 3c.
To configure the Barracuda Load Balancer: 1. From a Web browser, enter the IP address of the Barracuda Load Balancer followed by a colon and port 8000. For example: http://192.168.200.200:8000. 2. To log into the administration interface, enter admin for the username and admin for the password. 3. Select Basic > IP Configuration, and perform the following steps: 3a. Enter the following information in the WAN IP Configuration section: 3b. 3c. 3d. 3e. Note • IP Address.
4c. 4d. 4e. 4f. Time on the Barracuda Load Balancer is automatically updated via NTP (Network Time Protocol). It requires that port 123 is opened for outbound UDP (User Datagram Protocol) traffic on your firewall (if the Barracuda Load Balancer is located behind one). It is important that the time zone is set correctly because this information is used to coordinate traffic distribution and in all logs and reports.
3. The Barracuda Load Balancer should arrive with the Energize Updates (and Instant Replacement where applicable) subscription already enabled. If it is, then this step can be skipped. Otherwise, to enable your subscription: 3a. Click the Activate link as shown in Figure 3.1. The product activation displays in a new browser window. Figure 3.1: Location of the Activate Link Click to activate your subscription 3b. On the Product Activation page, fill in the required fields and click Activate.
Administrative Settings This section covers the basic administrative settings for your Barracuda Load Balancer. Controlling Access to the Administration Interface..............................36 Customizing the Appearance of the Web Interface............................ 36 Setting the Time Zone of the System .................................................. 36 Enabling SSL for Administration.......................................................
Note The SSL configuration referred to here is only related to the Web administrative interface. To enable SSL offloading for a Service, refer to SSL Offloading on page 47. In order to only allow secured connections when accessing the Web administration interface, you need to supply a digital SSL certificate which will be stored on the Barracuda Load Balancer.
Maintaining the Barracuda Load Balancer This section describes how to manage and maintain your Barracuda Load Balancer using the Web administration interface. This section covers the following topics: Backing up and Restoring Your System Configuration ..................... 38 Updating the Firmware of Your Barracuda Load Balancer.............. 38 Updating the Intrusion Prevention Rules Using Energize Updates .. 39 Replacing a Failed System ................................................................
If your Barracuda Load Balancers are not in High Availability mode, applying a new firmware version results in a temporary loss of service. For this reason, you should apply new firmware versions during non-busy hours. Updating the Intrusion Prevention Rules Using Energize Updates The Advanced > Energize Updates page allows you to manually update the Intrusion Prevention System rules, as well as change the interval at which the Barracuda Load Balancer checks for updates.
Using the Built-in Troubleshooting Tools The Advanced > Troubleshooting page provides various tools that help troubleshoot network connectivity issues that may be impacting the performance of your Barracuda Load Balancer. For example, you can test your Barracuda system’s connection to Barracuda Central to make sure it can successfully download the latest IPS definitions.
Reboot Options Table 3.2 describes the options available at the reboot menu. Table 3.2: Reboot Options Reboot Options Description Barracuda Starts the Barracuda Load Balancer in the normal (default) mode. This option is automatically selected if no other option is specified within the first three (3) seconds of the splash screen appearing.
Barracuda Load Balancer Administrator’s Guide
Chapter 4 Managing the Barracuda Load Balancer This chapter describes the configuration, monitoring, and management tasks you can perform from the Web interface. For more detailed information about a specific page in the Web interface, view the online help by clicking the question mark icon on the right side of the page. The following topics are covered: Configuring the Barracuda Load Balancer....................................... 44 Monitoring the Barracuda Load Balancer ..................................
Configuring the Barracuda Load Balancer This section describes the configuration tasks you can perform from the Web administration interface. The following topics are covered: Configuring System IP Information ................................................... 44 Creating Load-Balanced Services...................................................... 44 Enabling Persistence ......................................................................... 46 Selecting a Scheduling Policy...............................
application that uses a wide range of ports. Otherwise, you would have to configure a Service for each port. Note: When ALL is selected, the Service Monitor Default Test uses Ping instead of a TCP port check to determine if a Real Server is up or down. • Real Servers. The IP address(es) of the Real Servers that host the load-balanced application or Service. Each IP address needs to be entered on a separate line. 2. Click Add.
Enabling Persistence The Barracuda Load Balancer supports session persistence using one of the following methods: • • • Layer 4 - Client IP. All traffic from a particular IP address after the initial incoming connection will be directed to the same Real Server. Layer 7 - HTTP Cookie. A cookie placed on the connecting system identifies returning connections so that all subsequent traffic from that system will go to the same Real Server.
SSL Offloading The Barracuda Load Balancer is able to perform decryption and encryption of SSL traffic to reduce the load on the Real Servers. It also keeps the SSL certificates associated with that traffic in one location for easier management. SSL offloading is not compatible with Direct Server Return. To set up SSL offloading, complete the following two tasks: 1. Upload one SSL certificate for each Service to the Barracuda Load Balancer. 2. Identify the Services that are using SSL offloading.
• • Number of Windows Terminal Server sessions, determined by an SNMP query. In order to use this option, Real Servers must allow SNMP access to the public community by the Barracuda Load Balancer. A URL provided by each Real Server which specifies a load value. If this option is selected, the Barracuda Load Balancer will poll the URL http://[Real Server IP Address]/barracuda_load/ and expect the output to look like LOAD=23 (showing the load as an integer between 0 and 100).
In Weighted Least Connections, the Barracuda Load Balancer considers the number of live connections that each Real Server has, as well as the weight values. The Real Servers with higher weight values will receive a larger percentage of live connections at any one time. The Barracuda Load Balancer dynamically checks the number of live connections for each Real Server. Weighted Least Connections is the recommended choice. To configure the Default Scheduling Policy for a Service: 1.
Before joining two systems together, each Barracuda Load Balancer must meet the following requirements: • • • • • • Barracuda Load Balancer models 340 or higher. Be the same model as the other Barracuda Load Balancer and on the same version of firmware. Be able to access all Real Servers. Be installed on a unique management IP address. The Barracuda Load Balancers use the management IP address (over SNMP ports) to communicate for high availability. Be able to ping each other on the WAN interface (i.e.
Leave the LAN IP Address and LAN Netmask blank. If the backup unit has to take over, it will use the LAN IP Address and Netmask from the primary system. 2. On the Advanced > Task Manager page on the primary Barracuda Load Balancer, verify that no processes are running. Complete this step on the backup Barracuda Load Balancer as well. No processes should be running when you add systems to the cluster. 3.
Data Propagated to Clustered Systems Clustering systems provides redundant coverage of the propagated data. Table 4.1 identifies the data that is propagated when the cluster is created. Table 4.1: Data Propagated Between Clustered Systems Propagated Data Data Not Propagated • Global system settings configured through the Administration interface. • System IP configuration (IP address, netmask, gateway, and DNS server) configured on the Basic > IP Configuration page.
Monitoring the Barracuda Load Balancer This section describes the monitoring tasks you can perform from the Web administration interface of the Barracuda Load Balancer. This section covers the following topics: Monitoring the Health of Services..................................................... 53 Viewing Performance Statistics ......................................................... 54 Viewing the Event Log .......................................................................
The following table describes the various health indicators displayed for Real Servers. Real Server Health Indicator Description Green dot Real Server is up and responding to requests. Orange dot Real Server has been intentionally deactivated. Red dot Real Server is down unexpectedly.
Appendix A SNMP MIB The Barracuda Load Balancer supports SNMP version 1. Barracuda-REF DEFINITIONS ::= BEGIN IMPORTS MODULE-IDENTITY, enterprises FROM SNMPv2-SMI; barracuda MODULE-IDENTITY LAST-UPDATED "200705080000Z" -- August 24, 1999 ORGANIZATION "Barracuda Networks, Inc." CONTACT-INFO " Barracuda Networks Inc. 3175 S. Winchester Blvd.
3175 S. Winchester Blvd. Campbell, CA 95008 " DESCRIPTION " Barracuda Load Balancer MIB. Provides: * 1.3.6.1.4.1.20632.5.2 -* 1.3.6.1.4.1.20632.5.3 -* 1.3.6.1.4.1.20632.5.4 -* 1.3.6.1.4.1.20632.5.5 -" ::= { barracuda 5 } systemActiveServices systemOperatingServers systemConnections systemConnectionRate systemActiveServices OBJECT-TYPE SYNTAX INTEGER MAX-ACCESS read-only STATUS current DESCRIPTION "The Barracuda Load Balancer's active services.
Appendix B Barracuda Load Balancer Hardware This appendix provides hardware information for the Barracuda Load Balancer. The following topics are covered: Front Panel of the Barracuda Load Balancer................................... 58 Back Panel of the Barracuda Load Balancer.................................... 60 Hardware Compliance .......................................................................
Front Panel of the Barracuda Load Balancer Figure B.1 and Figure B.2 illustrate the front panels for each model. Barracuda Load Balancer 240, 340, and 440 Figure B.1 shows the front components as described in Table B.1. Figure B.1: Barracuda Load Balancer Front Panel for models 240, 340, and 440 1 2 3 4 567 8 9 Table B.1 describes the front components on the Barracuda Load Balancer 240, 340, and 440. Table B.
Barracuda Load Balancer 640 Figure B.2 shows the front components as described in Table B.2. Figure B.2: Barracuda Load Balancer Front Panel for model 640 345678 9 ] 10 1 2 Table B.2 describes the front components on the Barracuda Load Balancer 640. Table B.
Back Panel of the Barracuda Load Balancer Figure B.3 illustrates the back panel for all models. Barracuda Load Balancer, all models Figure B.3 shows the back components as described in Table B.3. Figure B.3: Barracuda Load Balancer Back Panel 1 2 34 5 6 7 8 9 Table B.3 describes the back components on all models of the Barracuda Load Balancer. Table B.
Hardware Compliance This section contains compliance information for the Barracuda Load Balancer hardware. Notice for the USA Compliance Information Statement (Declaration of Conformity Procedure) DoC FCC Part 15: This device complies with part 15 of the FCC Rules. Operation is subject to the following conditions: 1. This device may not cause harmful interference, and 2. This device must accept any interference received including interference that may cause undesired operation.
Barracuda Load Balancer Administrator’s Guide
Appendix C Limited Warranty and License Limited Warranty Barracuda Networks, Inc., or the Barracuda Networks, Inc. subsidiary or authorized Distributor selling the Barracuda Networks product, if sale is not directly by Barracuda Networks, Inc., ("Barracuda Networks") warrants that commencing from the date of delivery to Customer (but in case of resale by a Barracuda Networks reseller, commencing not more than sixty (60) days after original shipment by Barracuda Networks, Inc.
Exclusions and Restrictions This limited warranty does not apply to Barracuda Networks products that are or have been (a) marked or identified as "sample" or "beta," (b) loaned or provided to you at no cost, (c) sold "as is," (d) repaired, altered or modified except by Barracuda Networks, (e) not installed, operated or maintained in accordance with instructions supplied by Barracuda Networks, or (f) subjected to abnormal physical or electrical stress, misuse, negligence or to an accident.
3. You may not transfer, rent, lease, lend, or sublicense the Barracuda Software. 4. This License is effective until terminated. This License is automatically terminated without notice if you fail to comply with any term of the License. Upon termination you must destroy or return all copies of the Barracuda Software. 5. YOU EXPRESSLY ACKNOWLEDGE AND AGREE THAT THE USE OF THE BARRACUDA SOFTWARE IS AT YOUR OWN RISK AND THAT THE ENTIRE RISK AS TO SATISFACTION, QUALITY, PERFORMANCE, AND ACCURACY IS WITH YOU.
YOU MAY RETURN THE SOFTWARE FOR A FULL REFUND, OR, IF THE SOFTWARE IS SUPPLIED AS PART OF ANOTHER PRODUCT, YOU MAY RETURN THE ENTIRE PRODUCT FOR A FULL REFUND. YOUR RIGHT TO RETURN AND REFUND EXPIRES 30 DAYS AFTER PURCHASE FROM BARRACUDA NETWORKS OR AN AUTHORIZED BARRACUDA NETWORKS RESELLER, AND APPLIES ONLY IF YOU ARE THE ORIGINAL PURCHASER.
AT THE TIME OF ACQUIRING SUCH COPY OR UPGRADE, ALREADY HOLDS A VALID LICENSE TO THE ORIGINAL ENERGIZE UPDATE SOFTWARE AND HAS PAID THE APPLICABLE FEE FOR THE UPGRADE; (2) USE OF UPGRADES IS LIMITED TO BARRACUDA NETWORKS EQUIPMENT FOR WHICH CUSTOMER IS THE ORIGINAL END USER PURCHASER OR LESSEE OR WHO OTHERWISE HOLDS A VALID LICENSE TO USE THE ENERGIZE UPDATE SOFTWARE WHICH IS BEING UPGRADED; AND (3) USE OF ADDITIONAL COPIES IS LIMITED TO BACKUP PURPOSES ONLY. Energize Update Changes.
Restricted Rights. Barracuda Networks' commercial software and commercial computer software documentation is provided to United States Government agencies in accordance with the terms of this Agreement, and per subparagraph "(c)" of the "Commercial Computer Software - Restricted Rights" clause at FAR 52.227-19 (June 1987). For DOD agencies, the restrictions set forth in the "Technical Data-Commercial Items" clause at DFARS 252.227-7015 (Nov 1995) shall also apply. No Warranty.
Open Source Licensing Barracuda products may include programs that are covered by the GNU General Public License (GPL) or other "open source" license agreements. The GNU license is re-printed below for you reference. These programs are copyrighted by their authors or other parties, and the authors and copyright holders disclaim any warranty for such programs. Other programs are copyright by Barracuda Networks.
c) If the modified program normally reads commands interactively when run, you must cause it, when started running for such interactive use in the most ordinary way, to print or display an announcement including an appropriate copyright notice and a notice that there is no warranty (or else, saying that you provide a warranty) and that users may redistribute the program under these conditions, and telling the user how to view a copy of this License.
if he or she is willing to distribute software through any other system and a licensee cannot impose that choice. This section is intended to make thoroughly clear what is believed to be a consequence of the rest of this License. 8.
Barracuda Products may contain programs that are copyright (c)1995-2005 International Business Machines Corporation and others. All rights reserved.
means any form of electronic, verbal, or written communication sent to the Licensor or its representatives, including but not limited to communication on electronic mailing lists, source code control systems, and issue tracking systems that are managed by, or on behalf of, the Licensor for the purpose of discussing and improving the Work, but excluding communication that is conspicuously marked or otherwise designated in writing by the copyright owner as "Not a Contribution.
that a file or class name and description of purpose be included on the same "printed page" as the copyright notice for easier identification within third-party archives. Copyright [yyyy] [name of copyright owner] Licensed under the Apache License, Version 2.0 (the "License"); you may not use this file except in compliance with the License. You may obtain a copy of the License at http://www.apache.org/licenses/LICENSE-2.
Index A H Adaptive Scheduling 47, 48 administration interface logging in 33 Administration page 36, 39, 54 alerts 54 hardware compliance information 61 hardware test 41 Health page 53 High Availability 17 updating firmware 38 B I back panel details 60 backing up configuration 38 Backup page 38 Barracuda Load Balancer configuring 32, 44 managing 38 monitoring 53 Barracuda Load Balancer Terminology 16 Bridge-Path 16, 22 IP address setting 31 IP Configuration page 44 C Management IP Address 17 monito
replacing failed system 39 RESET button, using 39 restarting the system 39 restoring configuration 38 Route-Path 16 S Scheduling policy 16 Server Farm 16 Service 16 Service Monitor 16, 45 Services, monitoring 53 Session 12 shutting down the system 39 SSL Certificates 47 SSL Offloading 47 SSL Offloading, configuring 47 Status page 54 subscription activating 35 status 34 T Task Manager page 54 TCP ports 32 testing memory 41 time zone, setting 36 Troubleshooting page 40 U UDP ports 32 updating definitions 3
