HTTP (L7) vServices
How to Add?
To add a new HTTP (L7) vService, follow the steps vServices > Add through TR7 ASP web interface.
Interface
vServices List Screen
By "vServices" tab, the list of all vServices added on the TR7 ASP device is reached. On this screen, operations such as adding, editing and deleting the vService are performed.
- 1 (Information to be Displayed in the Table)
It is selected which information will be shown or not in the table where the vServices are located.
Information that can be selected and selected by default;
- Preferences
- Status
- Name
- vDevice
- TR7 ASP Device Hostname > For more details click here.
- Type
- WAF
- Algorithm
- 2 (Add)
Clicking on the Add
button opens a new vService creation form.
- 3 (Edit)
By clicking on the Edit
button, the editing screen of the relevant vService is opened.
- 4 (Delete)
After selecting one or more vServices, click the Delete
button to delete the relevant vServices on the TR7 ASP device.
- 5 (Enable)
When a Disabled vService is selected and the Enable
service button is clicked, the vService is activated.
- 6 (Disable)
The vService is disabled by selecting an Enable
vService and clicking the Disable
button.
- 7 (Search)
It is used to search for all expressions in the table.
- 8 (RegExp Search)
Used to regexp search for all expressions in the table.
- 9 (Column Based Search)
Used to column based search for all expressions in the table.
- 10 (Status)
This is the section where the status of the vServices are displayed.
Blue > vService is starting.
Green > vService is active.
Red > vService is in an error state. Configurations should be checked.
Gray > vService is disabled.
Yellow > vService gives warning. For example, when 1 of 2 Backend Services fails to perform health check, the status of the vService changes to Warning. The traffic coming to the vService continues to be transmitted to the Backend Service standing on.
- 11 (WAF Status)
This is the section where the WAF status (Enabled/Disabled) of the vServices is displayed.
- Right Click Window
The following operations can be performed from the window opened by right-clicking on any vService.
- 12 (Page Information)
In the drop-down list, there is information about how many vServices there are and how many vServices are listed. When the vServices is selected from the left to delete, the information of the selected vServices is also displayed here.
- 13 (Page Size)
In the drop-down list, the maximum number of vServices to be listed is selected. You can switch between pages with arrow icons.
- Preview of Selected vService
By "vServices" tab, when any vService is clicked on, the window with the diagram of the relevant vService opens on the right side of the screen.
The preview can be closed by clicking the (x)
button at the top right of the window that opens or clicking on the vService again.
Interface
HTTP (L7) vService Adding Screen
By following "vServices > Add" buttons, a new vService is added on the TR7 ASP device. This section describes the HTTP (L7) vService creation form.
- Status
In which case vService will be opened is selected.
Enabled > vService is opened actively.
Disabled > vService is opened as disabled.
Debug Mode > vService is opened in Debug Mode. Thus, Debug Mode Logs is displayed for the requests arrived to the vService.
- Name
Name of the vService is entered.
- vDevice
On which vDevice the vService to be created will be opened is selected. For details about vDevices click here.
- Frontend IP - Port - SSL
The IP, Port and SSL statuses of the vService created here are set. By clicking on the +
icon, tabs are added to select the Fronted IP addresses. SSL status is selected by typing the desired port number. Under the SSL tab, None, HTTP/2.0, Terminate or Redirect can be selected.
None > No action is taken regarding SSL.
HTTP/2.0 > HTTP/2.0 protocol is used.
Terminate > It is used for SSL Offloading by terminating SSL on TR7 ASP.
Redirect > It is used to automatically redirect requests from HTTP to HTTPS.
Warning
Certificate selection is required when HTTP/2.0 or Terminate is selected.
- Conditional Backend Services
By clicking the Conditional Backend Services button, the incoming request is forwarded to the desired Backend Services (Content Switching) if it complies with the selected condition. In conditional distributions, all Conditions that can be defined on TR7 ASP can be used.
In the example, for the 1st conditional distribution, HTTP Header condition is used in the incoming request. If the header information matches www.tr7.com exactly, www.tr7.com will be transferred to the Backend Service. For the second conditional distribution, the Host header information will be sent to support.tr7.com. If it matches exactly, it is forwarded to support.tr7.com Backend Service. Requests that do not match the host header information will be forwarded to the servers selected in the Default Backend Services tab. If no selection is made in the Default Backend Service, clients display the TR7 ASP 503 status code.
Warning
Conditional Distributions run in the order created in the configuration. The icon marked in the 2nd image below can be easily changed by dragging it.
- Default Backend Services
Backend Services to which the requests coming to the Frontend IP:Port will be forwarded are selected. In addition, a new Backend Service can be added on the vService screen by clicking the Add
button in the drop-down list.
- Save
By clicking the Save
button, vService is created.
Interface
Details
When the Details button is clicked on the HTTP (L7) vService adding screen, the list of profiles and configurations that can be added to the vService is reached.
- Debug
Puts the vService into debug mode. Thus, Debug Mode Logs are displayed for the requests coming to the vService. By clicking on Select Conditions, the debug logs are displayed under the desired conditions. If nothing is selected, Always debug mode is active.
- WAF
WAF is activated in the vService.
- L7 DDOS
L7 DDOS protection is activated in the vService. Profiles that have been added before, except the default profile, can be selected. Adding a new L7 DDOS profile can also be done on this screen. For more information click here.
- Cache
Cache is enabled on the vService. Profiles that have been added before, except the default profile, can be selected. Adding a new Cache profile can also be done on this screen. For more information click here.
- Compression
Compression is enabled in the vService. Profiles that have been added before, except the default profile, can be selected. Adding a new Compression profile can also be done on this screen. For more information click here.
- Actions
Actions are activated in vService. Adding a new Action can also be done on this screen. For more information click here.
- X-Forwarded-For
It is ensured that the user's IP address is forwarded to the Backend Services with the help of the "X-Forwarded-For" header information.
- LOG
LOG is activated in vService. Profiles that have been added before, except the default profile, can be selected. Adding a new Log profile can also be done on this screen. For more information click here.
- SSL Security
SSL Security is activated in the vService. Profiles that have been added before, except the default profile, can be selected. Adding a new SSL Security profile can also be done on this screen. For more information click here.
- Notification
Notification is enabled in vService. Profiles that have been added before, except the default profile, can be selected. Adding a new Notification profile can also be done on this screen. For more information click here.
- Report
Report is activated in the vService. Profiles that have been added before, except the default profile, can be selected. By selecting more than one report profile at the same time, e-mails can be sent to different people at different periods. Adding a new Report profile can also be done on this screen. For more information click here.
- QOS
QOS is the feature that ensures maximum efficiency in the vService by optimizing resources. By assigning certain resources such as CPU and RAM to the relevant vService, it can be ensured that that service operates independently of the situation of other services, even under heavy load.
Inline Mode
Inline Mode is activated in the vService. For more information click here.
Route Table
It is selected on which Route Table the log will be sent to the IP:Port specified in the Log profile of the vService.
Memory Limit
Memory Limit is determined in the vService.
Cores
The CPU that the vService will use is selected manually.
Processor Priority is selected in the vService. (Low-Normal-High)
Processor Usage Limit (%) is determined in the vService.
Core Engine
Core Version to be used in the vService is determined.
- vService Limits
vService Limits are activated in vService. Profiles that have been added before, except the default profile, can be selected. Adding a new vService Limit profile can also be done on this screen.For more information click here.
- Timeout
Timeout is activated in vService. Profiles that have been added before, except the default profile, can be selected. Adding a new Timeout profile can also be done on this screen. For more information click here.
- LB Algorithm
When distributing the requests coming from the vService to the Backend Service, the algorithm that will be used for this operation is selected. By default, Weighted Round Robin is selected.
Algorithm
The algorithm that will be distributed to Backend Services is selected.
- Round Robin > The load balancing is done independent from the dynamic loads (weights) of the vServices.
- Least Connection > The servers that currently have less connections get the priority. Recommended for servers with long session times such as LDAP and SQL.
- Random > Used for random server selection. The weight and server response time are taken into account.
- URI (Self-Persistent) > URI text with specified length (until ? character if any) is hashed and used for load balancing based on the weights of the servers. Same URIs always go to the same server.
- HDR (Self-Persistent) > In each HTTP request, the specified HTTP header is checked. Same header contents are sent to the same server.
- Weighted Round Robin > The load balancing is done based on the dynamic loads (weights) of the vServices.
- First > The first server on the vService gets the load until it reaches maximum connections.
- Source (Self-Persistent) > The hash value of source IP is used for load balancing based on the weights of the servers. Same clients always go to the same server.
- URL Param (Self-Persistent) > The value of specified URL param is and used to track user ID. This value is used for load balancing based on the weights of the servers. Same user ID always goes to the same server.
-
Fastest > Fastest algorithm based on selected option.
-
Least Response Time
- Least Connection Time
- Least Queue Time
- Least Connection
- Least Queues
- Least Connection Error
- Least Aborted Connections
- Least Used Connections
- Fastest+ > Fastest algorithm based on selected options (if first results in a tie, the second is used).
Fastest Opt-1
- Least Response Time
- Least Connection Time
- Least Queue Time
- Least Connection
- Least Queues
- Least Connection Error
- Least Aborted Connections
- Least Used Connections
Fastest Opt-2
- Least Response Time
- Least Connection Time
- Least Queue Time
- Least Connection
- Least Queues
- Least Connection Error
- Least Aborted Connections
- Least Used Connections
Persistence
After selecting the Algorithm, the following options can be used if persistence is desired.
It is chosen in cases where persistent operation is not desired. Requests are distributed to Backend Services with the algorithm selected in Algorithm.
Through the selected cookie, other connections are directed to the same Backend Service according to the cookie information of the Backend Service to which the client first connected. Values such as cookie name, max-idle, max-life can be set.
The cookie name specified in each HTTP request is searched. The same cookie contents are sent to the same Backend Service.