f5 load balancer certification

 

equals the IP address of the physical server and, without

load balancer, it would be the IP address and the name of the server (for example,

solution www.example.com) to. For the rest of this article, we will

comment on this idea as a guest.

The second concept is a member (sometimes, unfortunately, also called from a node

some manufacturers). A member is usually a little more defined than the server / node

because it includes the TCP port of the actual application that receives the traffic.

For example, a server named www.example.com could resolve to an address

172.16.1.10, which represents the server / node, and which may be in an application (web

server) running on TCP port 80, making member address 172.16.1.10:80. Quite simply

push, the member includes an explanation of the application port and IP

physical server address. For the rest of this article, we will discuss this

as the service.

f5 load balancer certification

Why all the trouble? Because the difference between a physical server and the

the running application services allow the balance of interactions on their own

with applications rather than basic hardware. May guest (172.16.1.10)

more than one service available (HTTP, FTP, DNS, and so on). Explain each one

unique application (172.16.1.10:80, 172.16.1.10:21 and 172.16.1.10:53), the load

the balancer can apply a special load balance and health check (discussed later)

based on services rather than hospitality. However, there are still times

able to interact with the guest (such as low-level health checks or while taking a file)

offline server for maintenance) extremely convenient.