vServices
vServices
This is the section where load balancing services are created and all traffic-related settings are made, except for WAF and basic configurations. It is used to manage the traffic on the device from a single point from the moment of reception until the user is answered. Basically, Backend Services (servers) which the incoming requests will be forwarded to, are defined by determining a VIP address or an Interface IP address. In the vServices, definitions can be made for all kinds of traffic such as HTTP, HTTPS (SSL), TCP, UDP, FTP. While doing this, it is an important point which protocol will be used in the vServices. Traffic can be manipulated with Conditions/Actions in vServices, different profiles can be assigned, and it can be decided how the traffic will be transmitted to the Backend Services with various distribution algorithms. There are basically 3 different types of vService on TR7 ASP devices. These are;
HTTP vServices are used for web applications serving at the L7 layer. This type of vService has profiles such as WAF, L7 DDOS, Cache, Compression, XFF, Report.
In L7 TCP vServices, TR7 ASP terminates its incoming requests and opens a TCP connection to the Backend Service. Thus, it can work as a TCP Proxy and can also terminate SSL when necessary. In this type of vService, such as FTP, SQL, FIX, MQTT, SNMP are load balanced.
Network vServices are used for load balancing at L3 and L4 levels. Incoming requests are forwarded to the defined Backend Services before they are terminated. While load balancing can be done for TCP and UDP (DNS, SYSLOG etc) protocols at L4 level, load balancing can be done for the whole protocol at L3 level.
By clicking on a vServices on TR7 ASP interface, a logical diagram of the relevant service is displayed on the right of the screen. There are many information such as IP addresses used on this diagram, certificate information, action/condition information, information of selected profiles.
