Unlike virtual IPs on FortiGate or virtual servers on FortiWeb, virtual servers on FortiADC are activated as soon as you configure them. You do not apply them by selecting them in a policy. |
Settings | Guidelines |
Name | Unique name. No spaces or special characters. After you initially save the configuration, you cannot edit the name. |
Status | • Enable—The server can receive new sessions. • Disable—The server does not receive new sessions and closes any current sessions as soon as possible. • Maintain—The server does not receive new sessions but maintains any current connections. |
Type | • Layer 7—Persistence, load balancing, and routing are based on Layer 7 objects, such as HTTP headers, cookies, and so on. • Layer 4—Persistence, load balancing, and network address translation are based on Layer 4 objects, such as source and destination IP address. • Layer 2—This feature is useful when the request’s destination IP is unknown and you need to load balance connections between multiple next-hop gateways. |
Interface | Network interface that receives client traffic for this virtual server. |
Address Type | • IPv4 • IPv6 Note: IPv6 is not supported for FTP or HTTP Turbo profiles. |
Address | IP address provisioned for the virtual server. Note: You do not specify an IP address for a Layer 2 virtual server. A Layer 2 virtual server is not aware of IP addresses. Instead of routing data for a specific destination, this type of server simply forwards data from the specified network interface and port. |
Port | Port number to listen for client requests. Note: If a Layer 2 virtual server is assigned a network interface that uses port 80 or 443, ensure that the HTTPS and HTTP administrative access options are not enabled for the interface. |
Connection Limit | Limit the number of concurrent connections. The default is 0 (disabled). The valid range is 1 to 1,048,576 concurrent connections. You can apply a connection limit per real server and per virtual server. Both limits are enforced. Attempted connections that are dropped by security rules are not counted. Note: Connection Limit is not supported for FTP profiles. |
Connection Rate Limit | With all Layer 4 profiles, and with the Layer 2 TCP profile, you can limit the number of new connections per second. The default is 0 (disabled). The valid range is 1 to 86,400 connections per second. You can apply a connection rate limit per real server and per virtual server. Both limits are enforced. Attempted connections that are dropped by security rules are not counted. Note: Connection Rate Limit is not supported for FTP profiles. |
Transaction Rate Limit | Limit the number of HTTP requests per second. The default is 0 (disabled). The valid range is 1 to 1,048,567 transactions per second. The system counts each client HTTP request against the limit. When the HTTP request rate exceeds the limit, the virtual server sends an HTTP 503 error response to the client. Note: Transaction Rate Limit is not supported for HTTP Turbo profiles. |
Content Routing | Enable to route packets to backend servers based on IP address (Layer 4) or HTTP headers (Layer 7 content); select a content route configuration object. Overrides static or policy routes. |
Content Rewriting | Enable to rewrite HTTP headers; select a content rewriting configuration object. See “Configuring content rewriting”. |
Layer 4 only | |
Packet Forwarding Method | In Layer 4 virtual server deployments, select one of the following packet forwarding methods: • Direct Routing — Forwards the source and destination IP addresses with no changes. Note: For FTP profiles, when Direct Routing is selected, you must also configure a persistence method. • DNAT — Replaces the destination IP address with the IP address of the backend server selected by the load balancer. The destination IP address of the initial request is the IP address of the virtual server. Be sure to configure FortiADC as the default gateway on the backend server so that the reply goes through FortiADC and can also be translated. • Full NAT —Replaces both the destination and source IP addresses. The source IP address is replaced by an IP address from the pool you define using Server Load Balance > Resources > Source Pool. The destination IP address is replaced with the IP address of the backend server selected by the load balancer. |
Source Pool | If you are configuring a Layer 4 virtual server and enable Full NAT, select a source pool configuration object. See “Configuring source pool”. |
Resources | |
Profile | Select a predefined or user-defined profile configuration object. See “Configuring profiles”. |
Persistence | Select a predefined or user-defined persistence configuration object. See “Configuring persistence rules”. |
Method | Select a predefined or user-defined method configuration object. See “Configuring methods”. |
Real Server | Select a real server pool configuration object. See “Configuring pools of real servers”. |
Error Page | |
Error Page | Select an error page configuration object. See “Configuring error pages”. |
Error Message | If you do not use an error page, you can enter an error message to be returned to clients in the event no server is available. |
Traffic Log | |
Log | Enable to record traffic logs for this virtual server. Note: Local logging is constrained by available disk space. We recommend that if you enable traffic logs, you monitor your disk space closely. We also recommend that you use local logging during evaluation and verification of your initial deployment, and then configure remote logging to send logs to a log management repository. |