ALOHA Load-Balancer. API objects. Document version: v2.0. API version concerned: v2.0. Aloha version concerned: Last update date: 24 th November, 2011



Similar documents
FortiOS Handbook - Load Balancing VERSION 5.2.2

HAProxy. Ryan O'Hara Principal Software Engineer, Red Hat September 17, HAProxy

Load Balancing. FortiOS Handbook v3 for FortiOS 4.0 MR3

TESTING & INTEGRATION GROUP SOLUTION GUIDE

FortiOS Handbook Load Balancing for FortiOS 5.0

Snapt Balancer Manual

How to Make the Client IP Address Available to the Back-end Server

Configuring Network Address Translation

Configuring Stickiness

Understanding Slow Start

Introduction. Linux Virtual Server for Scalable Network Services. Linux Virtual Server. 3-tier architecture of LVS. Virtual Server via NAT

21.4 Network Address Translation (NAT) NAT concept

Firewall Load Balancing

ALOHA LOAD BALANCER MANAGING SSL ON THE BACKEND & FRONTEND

Firewall Load Balancing

DEPLOYMENT GUIDE Version 2.1. Deploying F5 with Microsoft SharePoint 2010

DEPLOYMENT GUIDE. Deploying the BIG-IP LTM v9.x with Microsoft Windows Server 2008 Terminal Services

Chapter 7. Address Translation

Introduction to ServerIron ADX Application Switching and Load Balancing. Module 6: Content Switching (CSW) Revision 0310

DEPLOYMENT GUIDE DEPLOYING THE BIG-IP LTM SYSTEM WITH MICROSOFT WINDOWS SERVER 2008 TERMINAL SERVICES

Network Address Translation (NAT)

Load Balancing and Sessions. C. Kopparapu, Load Balancing Servers, Firewalls and Caches. Wiley, 2002.

Configuring Health Monitoring

DEPLOYMENT GUIDE Version 1.2. Deploying the BIG-IP system v10 with Microsoft Exchange Outlook Web Access 2007

Deploying F5 with Microsoft Remote Desktop Session Host Servers

Exam : EE : F5 BIG-IP V9 Local traffic Management. Title. Ver :

DEPLOYMENT GUIDE Version 1.2. Deploying the BIG-IP System v10 with Microsoft IIS 7.0 and 7.5

Configuring Health Monitoring

Deploying the BIG-IP System v10 with SAP NetWeaver and Enterprise SOA: ERP Central Component (ECC)

Migrating the SSL Offloading Configuration of the Alteon Application Switch 2424-SSL to AlteonOS version

Load Balancing Clearswift Secure Web Gateway

Application Note. Lync 2010 deployment guide. Document version: v1.2 Last update: 12th December 2013 Lync server: 2010 ALOHA version: 5.

NETASQ MIGRATING FROM V8 TO V9

Deploying F5 with Microsoft Active Directory Federation Services

DEPLOYMENT GUIDE Version 1.0. Deploying the BIG-IP LTM with Microsoft Windows Server 2008 R2 Remote Desktop Services

Load Balancing Bloxx Web Filter. Deployment Guide

Chapter 51 Server Load Balancing

Deploying F5 with Microsoft Remote Desktop Session Host Servers

ATS Test Documentation

Managing Virtual Servers

Deploying the BIG-IP System v10 with VMware Virtual Desktop Infrastructure (VDI)

Configuring SSL Termination

Availability Digest. Redundant Load Balancing for High Availability July 2013

Chapter 37 Server Load Balancing

MULTI WAN TECHNICAL OVERVIEW

UNIVERSITY OF OSLO Department of Informatics. Performance Measurement of Web Services Linux Virtual Server. Muhammad Ashfaq Oslo University College

Deploying F5 with Microsoft Remote Desktop Services

Web Load Balancing on a Budget

LinkProof And VPN Load Balancing

Load Balancing Trend Micro InterScan Web Gateway

HAProxy. Free, Fast High Availability and Load Balancing. Adam Thornton 10 September 2014

IP Filter/Firewall Setup

Outline VLAN. Inter-VLAN communication. Layer-3 Switches. Spanning Tree Protocol Recap

Deploying the BIG-IP System with Microsoft IIS

Virtual private network. Network security protocols VPN VPN. Instead of a dedicated data link Packets securely sent over a shared network Internet VPN

CS 457 Lecture 19 Global Internet - BGP. Fall 2011

Firewall Defaults, Public Server Rule, and Secondary WAN IP Address

Single Pass Load Balancing with Session Persistence in IPv6 Network. C. J. (Charlie) Liu Network Operations Charter Communications

Load Balancing Sophos Web Gateway. Deployment Guide

DEPLOYMENT GUIDE Version 1.2. Deploying the BIG-IP System v9.x with Microsoft IIS 7.0 and 7.5

Introducing the Microsoft IIS deployment guide

Load Balancing McAfee Web Gateway. Deployment Guide

Load Balancing Microsoft Terminal Services. Deployment Guide

Deploying the BIG-IP LTM v10 with Microsoft Lync Server 2010 and 2013

NAT & IP Masquerade. Internet NETWORK ADDRESS TRANSLATION INTRODUCTION. NAT & IP Masquerade Page 1 of 5. Internal PC

ENTERPRISE DATA CENTER CSS HARDWARE LOAD BALANCING POLICY

DEPLOYMENT GUIDE Version 1.0. Deploying the BIG-IP LTM with Apache Tomcat and Apache HTTP Server

How To Understand The Role Of The Lib8000 On A Network (Networking) On A Server Cluster (Netware) On An Ipnet (Netrope) On Ubuntu) On Pcode (Netnet)

DEPLOYMENT GUIDE DEPLOYING F5 WITH SAP NETWEAVER AND ENTERPRISE SOA

DEPLOYMENT GUIDE Version 1.1. Deploying the BIG-IP LTM v10 with Citrix Presentation Server 4.5

Deploying F5 with Microsoft Forefront Threat Management Gateway 2010

Scalable Linux Clusters with LVS

IOS Server Load Balancing

Load Balancing Web Proxies Load Balancing Web Filters Load Balancing Web Gateways. Deployment Guide

Layer 4-7 Server Load Balancing. Security, High-Availability and Scalability of Web and Application Servers

DEPLOYMENT GUIDE Version 1.2. Deploying F5 with Microsoft Exchange Server 2007

Chapter 1 Load Balancing 99

DEPLOYMENT GUIDE Version 1.0. Deploying the BIG-IP LTM System with VMware View

How To Balance A Load Balancer On A Server On A Linux (Or Ipa) (Or Ahem) (For Ahem/Netnet) (On A Linux) (Permanent) (Netnet/Netlan) (Un

DEPLOYMENT GUIDE DEPLOYING F5 WITH VMWARE VIRTUAL DESKTOP INFRASTRUCTURE (VDI)

WAN Optimization, Web Cache, Explicit Proxy, and WCCP. FortiOS Handbook v3 for FortiOS 4.0 MR3

Link Load Balancing :50:44 UTC Citrix Systems, Inc. All rights reserved. Terms of Use Trademarks Privacy Statement

ZEN LOAD BALANCER EE v3.04 DATASHEET The Load Balancing made easy

Deploying F5 with Microsoft Remote Desktop Gateway Servers

Veriton. Getting the Best out of Hardware Load Balancers in an Oracle Environment. What is a Load Balancer? Agenda. What s out there?

Troubleshooting Tools

Load Balancing Barracuda Web Filter. Deployment Guide

Configuring Load Balancing

DMZ Network Visibility with Wireshark June 15, 2010

Deploying F5 for Microsoft Office Web Apps Server 2013

Deployment Guide. AX Series with Microsoft Exchange Server

Deploying the Barracuda Load Balancer with Office Communications Server 2007 R2. Office Communications Server Overview.

About Firewall Protection

Smoothwall Web Filter Deployment Guide

DEPLOYMENT GUIDE DEPLOYING F5 WITH MICROSOFT WINDOWS SERVER 2008

Configuring Traffic Policies for Server Load Balancing

DEPLOYMENT GUIDE Version 1.2. Deploying the BIG-IP LTM for SIP Traffic Management

DEPLOYMENT GUIDE Version 1.1. Deploying F5 with IBM WebSphere 7

Transcription:

ALOHA Load-Balancer API objects Document version: v2.0 API version concerned: v2.0 Aloha version concerned: v4.2.3 Last update date: 24 th November, 2011 [Sélectionnez la date]

Sommaire L7 module objects... 5 Farm object... 5 balance... 5 protocol... 5 log... 6 log_format... 6 http_connection_mode... 6 http_pretend_keepalive... 6 http_xff_header_insert... 7 http_cookie... 7 http_cookie_name... 7 http_cookie_mode... 7 http_cookie_nocache... 8 check-interval... 8 check_rise... 9 check_fall... 9 check_port... 9 check_timeout... 9 adv_check... 9 adv_check_http_uri... 10 adv_check_http_method... 10 queued_timeout... 10 connect_timeout... 10 connect_retries... 10 connect_failure_redispatch... 11 connect_source... 11 connect_transparent... 11 server_inactivity_timeout... 11 Server object... 12 Page 2

address... 12 port... 12 max_connections... 12 weight... 12 http_cookie_id... 13 sorry... 13 check... 13 maintenance... 13 Service object... 14 protocol... 14 log... 14 log_format... 14 log_ignore_null... 15 http_connection_mode... 15 http_pretend_keepalive... 15 client_inactivity_timeout... 16 http_request_timeout... 16 http_keepalive_timeout... 16 max_connections... 16 default_farm... 16 Listener object... 17 port... 17 address... 17 ssl... 17 ssl_certificate... 17 transparent... 18 L4 module objects... 18 Farm object... 18 balance... 18 mode... 19 Page 3

persistence... 19 persistance_timeout... 19 persistance_netmask... 19 service_address... 20 service_port... 20 service_protocol... 20 check-interval... 20 check_port... 20 check_timeout... 21 check_source... 21 adv_check... 21 adv_check_http_uri... 21 adv_check_http_status_code... 21 Server object.... 22 address... 22 port... 22 weight... 22 sorry... 22 check... 23 Page 4

L7 module objects Farm object A farm is a real server container. Contained servers are supposed to have the same role and to deliver the same service. Farm attributes and options define session behavior on the real servers side of the load balancer: how to check, dispatch connections, connect, forward data and maintain sessions to real servers. Farms are identified by a name, allowed chars are alpha numerics dot, dash and underscore. The available attributes for a farm are listed below. balance Defines the load balancing algorithm to dispatch new connections on real servers roundrobin: Each server is used in turn, according to their weights least-connections: The new connection is affected to the server with the lowest number of connections hash-uri: The left part of the URI (before the question mark) is hashed and divided by the total weight of the running servers. The result designates which server will receive the request hash-source: The source IP address is hashed and divided by the total weight of the running servers to designate which server will receive the request. This ensures that the same client IP address will always reach the same server as long as no server goes down or up Default: roundrobin is used. protocol Defines the protocol analyser used by load balander. Some features on HTTP protocol require to set analyser on http. tcp: Layer4 protocol TCP analyser. http: Layer7 protocol HTTP analyser. Default: Layer4 protocol TCP analyser. Page 5

log Enable logging on farm events. enabled: logs are enabled. Default: log are disabled. log_format Defines the log format used if logs are enabled. tcp: Advanced tcp log format http: Advanced http log format (fall back on tcp mode if protocol not set to http) clf: Use common log format defined by apache (fall back on tcp mode if protocol not set to http) Default: basic log format. http_connection_mode Defines http keepalive behavior (ignored if protocol is not set to http). tunnel: Connection header is left untouched and body is ignored. passive-close: Connection header is changed and body is ignored server-close: Connection header set, body scanned, client-side keep-alive is made possible regardless of server-side capabilities forced-close: Connection header set, body scanned, connection closed Default: Connection header is left untouched and body is ignored. http_pretend_keepalive Page 6

Enable load balancer keepalive announce to the server regardless keepalive status (ignored if protocol is not set on http). enabled: keepalive announces are enabled. disabled: keepalive announces are disabled. Default: keepalive announce are disabled. http_xff_header_insert Enable the X-Forwarded-For header insertion to requests filled using client source ip (ignored if protocol not set to http). enabled: X-Forwarded-For header insertion is enabled. Default: X-Forwarded-For header insertion is disabled. http_cookie Enable session affinity using cookie analyse (ignored if protocol is not set to http). enabled: cookie analyse is enable (require http_cookie_name, http_cookie_mode and http_cookie_nocache configured) Default: no cookie affinity. http_cookie_name Type: string Defines the name of the cookie used for server affinity. On incoming connections, request is forwarded to the server whose the http_cookie_id server attribut match current cookie value. Settable if http_cookie is set. Settable and mandatory if http_cookie is set. Default: no cookie affinity. http_cookie_mode Page 7

Defines affinity cookie analyse/insertion behavior. Settable if http_cookie is set. Settable and mandatory if http_cookie is set. passive: cookie is analysed on incoming request to choose server but load balancer does not perform any insertion update or deletion on the cookie or set-cookie passive-silent: cookie is analysed on incoming request to choose server and set-cookie is removed from response if not needed. reset: cookie is analysed on incoming request to choose server and set-cookie value is rewrited in response if present. set: cookie is analysed on incoming request to choose server and set-cookie value is rewrited if present or inserted in response if needed. set-silent: cookie is analysed on incoming request to choose server and set-cookie value is rewrited if present, inserted in response if needed or removed if not needed. session-prefix: cookie is analysed on incoming request to choose server whose http_cookie_id prefix match. set-cookie value is prefixed using http_cookie_id server attribute value in response. insert-only-silent: cookie is analysed on incoming request to choose server and set-cookie value is leaved untouched if present, inserted in response if needed or removed if not needed. passive-session-prefix: cookie is analysed on incoming request to choose server whose http_cookie_id prefix match. Default: no cookie affinity. http_cookie_nocache Enable nocache flag on inserted cookie to prevent proxy caching of the cookie. Settable if http_cookie is set. Settable and mandatory if http_cookie is set. enabled: nocache flag insertion on cookie is enabled. disabled: nocache flag insertion on cookie is disabled. Default: no cookie affinity. check-interval Defines interval in seconds between two consecutive server health checks. Default: 2. Page 8

check_rise Defines count of consecutive successful health checks to consider server operational. Default: 2. check_fall Defines count of consecutive unsuccessful health checks to consider server not operational. Default: 3. check_port Defines destination TCP port used to perform health check. Set to 0 to use server port. Default: server port is used. check_timeout Defines additional health check timeout in seconds, but only after a connection has been already established. Set to 0 for set timeout to check-interval. Default: timeout is set to check-interval. adv_check Defines advanced check method. http: Use an http request health check for server testing, If http status code 2xx or 3xx is returned, check is successful (require adv_check_http_method and adv_check_http_uri configured). Page 9

ssl: Use SSLv3 client hello health checks for server testing, If a SSLv3 server hello is retured, check is successful. Default: no advanced check a tcp connect is preformed. adv_check_http_uri Type: string Defines requested URI on health check. Settable and mandatory if adv_check is set to http. Default: advanced check not set to http. adv_check_http_method Type: string Defines HTTP request method used on health check. Default is HEAD. Settable and mandatory if adv_check is set to http. Default: advanced check not set to http. queued_timeout Defines the maximum time to wait in the queue for a connection slot to be free. Set to 0 for no timeout. Default: no timeout. connect_timeout Defines the maximum time to wait for a connection attempt to a server to succeed. Set to 0 for no timeout. Default: no timeout. connect_retries Defines the number of retries to perform on a server after a connection failure. Set to 0 for no retries. Default: no retries. Page 10

connect_failure_redispatch Enabled session redispatch to an other server in case of connection failure. enabled: session redipatch is enabled. disabled: session redipatch is disabled. Default: no redispatch. connect_source Type: ip Force source address to use to connect to servers (require connect_transparent configured). Set to 0.0.0.0 to use first address on load balancer outgoing interface. Default: first address on load balancer outgoing interface is used. connect_transparent Enable transparent proxy mode: client source address is re-used as source address to connect to server. Settable and mandatory if connect_source is set. enabled: transparend proxy mode is enabled. disabled: transparend proxy mode is disabled. Default: first address on load balancer outgoing interface is used. server_inactivity_timeout Defines the maximum inactivity time on the server side. Set to 0 for no timeout. Default: no timeout. Page 11

Server object This is the real server, it delivers the same service than other real servers of the same farm. Server attributs and options define the way and the conditions to forward requests to this real server and the capacity of the server to process requests comparativly to other server. Servers are identified by a name and the name of the containing farm, allowed chars are alpha numerics dot, dash and underscore. address Type: ip Defines the ip address to forward requests to this server. Mandatory, no default available. port Type: port Defines the port to forward requests to this server Set to 0: incoming connection destination port is reused. Default: incoming connection destination port is reused. max_connections Specifies the maximal number of concurrent connections that will be sent to this server. If the number of incoming concurrent requests goes higher than this value, they will be queued, waiting for a connection to be released. This parameter is very important as it can save fragile servers from going down under extreme loads. Default: unlimited. weight Used to adjust the server's weight relative to other servers of the farm. All servers will receive a load proportional to their weight relative to the sum of all weights, so the higher the weight, the higher the load. The default weight is 1, and the maximal value is 256. A value of 0 means the server will not participate in load-balancing but will still accept persistent connections. If this parameter is used to distribute the load according to server's capacity, it is Page 12

recommended to start with values which can both grow and shrink, for instance between 10 and 100 to leave enough room above and below for later adjustments. Default: 1. http_cookie_id string Defines the identifier used as cookie value to identify this server. sorry A sorry server is only used when all none sorry servers are not operational ( health checks ). enabled: current server is a sorry server. Default: server is not a sorry server. check Enable health checks on current server to determine if this server is operational. enabled: current server is checked. Default: server is not checked. maintenance This server is disabled for maintenance purpose. enabled: current server is disabled. Page 13

Default: server is not disabled. Service object A Layer 7 service is a set of listener. Service attributs and options define session behavior on the client side and into the the load balancer: max accepted simultaneous sessions, choice of server farm, timeouts on the client side. Service are identified by a name, allowed chars are alpha numerics dot, dash and underscore. protocol enum Defines the protocol analyser used by load balander. Some features on HTTP protocol require to set analyser on http. tcp: Layer4 protocol TCP http: Layer7 protocol HTTP Default: Layer4 protocol TCP. log Enable logging on farm events. enabled: log are enabled. Default: logs are disabled. log_format Defines the log format used if logs are enabled. tcp: Advanced tcp log format Page 14

http: Advanced http log format (fall back on tcp mode if protocol not set to http) clf: Use common log format defined by apache (fall back on tcp mode if protocol not set to http) Default: basic log format. log_ignore_null enum Enabled: no log for open/closed empty connections. enabled: no log for connections are ignored disabled: no log for connections are not ignored Default: log empty connections. http_connection_mode Defines http keepalive behavior (ignored if protocol is not set to http). tunnel: Connection header is left untouched and body is ignored. passive-close: Connection header is changed and body is ignored server-close: Connection header set, body scanned, client-side keep-alive is made possible regardless of server-side capabilities forced-close: Connection header set, body scanned, connection closed Default: Connection header is left untouched and body is ignored. http_pretend_keepalive Enable load balancer keepalive announce to the server regardless keepalive status (ignored if protocol is not set on http). enabled: keepalive announces are enabled. disabled: keepalive announces are disabled. Page 15

Default: keepalive announce are disabled. client_inactivity_timeout integer Defines the maximum inactivity time on the client side. Set to 0 for no timeout. Default: no timeout. http_request_timeout integer Defines the maximum time to wait an entire valid HTTP request (no effect if protocol is not set to http). Set to 0 for no timeout.. Default: no timeout. http_keepalive_timeout integer Defines the maximum time to wait for a new HTTP request to appear in the same session (no effect if protocol is not set to http). Set to 0 for no timeout. Default: no timeout. max_connections integer Defines the maximum of simultaneous sessions accepted on this service. Default: no limit. default_farm integer Defines the default farm used to process requests Default: if no rules match connections are closed. Page 16

Listener object A listener is part of a service. it defines a port or a couple ip port to listen for incoming tcp connections. Listener are identified by a name and the name of the containing service, allowed chars are alpha numerics dot, dash and underscore. port type: integer Defines the port to listen. Mandatory, No default available. address Type: ip Defines the address to listen. Use 0.0.0.0 for all ipv4 adresses present on load balancer network configuration. Mandatory, No default available. ssl enum Enable ssl offloading. enabled: ssl offloading is enabled. Default: ssl offloading is disabled. ssl_certificate string Defines the certificate used for ssl offloading. Settable and mandatory if ssl is enabled. Default: ssl offloading is disabled. Page 17

transparent enum Enabled: incoming connections to listener ip and port are intercept even if ip is not present in load balancer network configuration of the load balancer (ie a router forward connections to the load balancer). enabled: transparent accept is enabled. Default: intercept only connections to listener ip and port present in load balancer network configuration. L4 module objects Farm object A farm is a real server containers. Contained servers are supposed to have the same role and to deliver the same service. Farm attributs and options defines session behavior on the real servers side of the load balancer: how to check real servers, dispatch connections on real servers, forward packets to real servers, maintain session to real servers. Farms are identified by a name, allowed chars are alpha numerics dot, dash and underscore. balance Defines the load balancing algorithm to dispatch new connections on real servers roundrobin: distributes jobs equally amongst the available real servers, jobs are assigned to real servers proportionally to there real servers' weight. least-connections: assigns more jobs to servers with fewer jobs and relative to the real servers' weight. This is the default. hash-source: assigns jobs to servers through looking up a statically assigned hash table by their source IP addresses. hash-destination: assigns jobs to servers through looking up a statically assigned hash table by their destination IP addresses shortest-expected-delay: assigns an incoming job to the server with the shortest expected delay. never-queue: assigns an incoming job to an idle server if there is, instead of waiting for a fast one; if all the servers are busy, it adopts the Shortest Expected Delay policy to assign the job. Page 18

Default: roundrobin mode Default: nat gateway: Use direct routing. nat: Use destination masquerading (network access translation, or NAT). tunnel: Use ipip encapsulation (tunneling). persistence If this option is enabled, multiple requests from a client (same source ip) are redirected to the same real server selected for the first request. This option may be used in conjunction with protocols such as SSL or FTP where it is important that clients consistently connect with the same real server. enabled: persistence is enabled. Default: persistence is disabled. persistance_timeout Value in seconds specify how long sessions are kept persistence load balance table. persistence <timeout> Default: 300 seconds. persistance_netmask Type: ip Specify the granularity of persistance Default: 255.255.255.255 Page 19

service_address Type: ip Defines the service address to intercept to be served by current farm. Default: no interception. service_port Type: port Defines the service port to intercept to be served by current farm. Settable if service_address is configured. Set to 0 for intercept all ports. Default: if service_address is set all ports are intercepted. service_protocol Defines the service protocol (udp or tcp) to intercept to be served by current farm. * tcp: intercept tcp. * udp: intercept udp. Default: if service_address is set tcp is intercept. check-interval Defines interval between two consecutive server health checks in seconds. Default: 10. check_port Defines destination TCP port used to perform health check. Default: server port is used. Page 20

check_timeout optional Defines additional health check timeout, but only after a connection has been already established. If not set default is check interval. check_timeout <seconds> Default: checkinterval/2 check_source Defines source address used to perform health check. Default: first load balancer interface address is used. adv_check Defines advanced check method. Default: icmp http: Use an http request health checks for server testing, If http status code 200 is returned, check is successful. tcp: Perform a tcp connect. if connect accepted, check is successful. icmp: process an icmp echo to server, if echo reply received, check is successful. adv_check_http_uri Type: string Defines requested URI on health check. Default is / (ignored if adv_check not set to http). Default: / adv_check_http_status_code Type: intger (ignored if adv_check is not set to http) Page 21

Defines the HTTP status code value to consider check successful (ignored if adv_check not set to http). Default: 200. Server object. This is the real server, it deliver the same service than other real servers of the same farm. Server attributs and options define the way and the conditions to forward packets to this real server and the capacity of the server to process requests comparativly to other server. Servers are identified by a name and the name of the containing farm, allowed chars are alpha numerics dot, dash and underscore. address Type: ip Defines the ip address to forward requests to this server. Mandatory, no default. port Type: port Defines the port to forward requests to this server in mode nat. or/and port to perform tcp checks if checkport not configured. Set to 0 and incoming packets destination port is used. Default: incoming packets destination port is used. weight jobs are assigned to real servers proportionally to their real servers' weight. Servers with higher weight receive new jobs first and get more jobs than servers with lower weights. Servers with same weight get an equal distribution of new jobs. Default: 1 sorry Type enum If enabled, server is only used when all none sorry servers are not operational ( health checks ). Only one sorry server is available per L4 farm. A sorry server could not be checked (heath check). Page 22

enabled: server is a sorry server. Default: server is not a sorry server. check Type enum If enabled, health checks are processed to determine if this server is operational. enabled: server is checked. Default: server is not checked. Page 23