How to use Monitor End Point

Relevancy: EdgeADC v5.x

Example 1

Let’s take an example of an infrastructure comprising two load balanced web servers that deliver a web application to the end user. The web application is connected to a database server in the back end. The access to the database server goes down, but the web application servers remain in operation. The users will be trying to use the web application and will be receiving errors.

The solution is to use Monitor End Point.

• The example shows two web servers, 10.0.0.20 and 10.0.0.21, together with a third web server 10.0.0.22. The 10.0.0.22 server has been placed in a Standby mode.
• The two active web servers have been configured with a Monitoring End Point value of 10.0.0.111:4033 which is the database server connection IP Address and Port.
• In the event that the database server connection was to drop, the two active servers will be placed into an Offline mode, and the Standby server will go online, serving a web page that may inform the customer that the systems are under maintenance.

Example 2

Another example of Monitor End Point usage is when you are load balancing UDP protocol servers, such as Always-On-VPN. As you may know, UDP ports are not reliably monitored, and so there arises a need to monitor a TCP port.

Using Monitor End Point allows us to do just that. The main port being used by the Always-on-VPN servers will be 53/UDP, but you will monitor, say, 8433/TCP. In such a case, you just need to enter the port value in the Monitor End Point field.