Load Balancing - First Alive TCP Port

Chris,

the port used for monitoring if a server is alive and the service you want to publish must be the same.
So if you are publishing 1935, health check port must be 1935.

Chris,

the port used for monitoring if a server is alive and the service you want to publish must be the same.
So if you are publishing 1935, health check port must be 1935.

Hi Luk

Thank you for you reply.

The Problem was, that i am publishing multiple ports and port 80 was at first.

No I changed the order, so that port 1935 is the first in the row.

Thank you again.

Regards,

Chris

Hi Luk

I have another question.

We have a webcam at an external location, which is streaming (on port 1935 UDP) to our firewall via public ip.

On our firewall, I created a rule, which is forwarding that port to an internal streaming server. Additionally that rule should do a fail over via "first alive" to a backup server. That means, if port 1935 TCP is not responding on primary server, all the traffic should be forwarded on port 1935 UDP to the backup server. But if I stop the service on primary server, which is listening on port 1935, the fail over mechanism does not work and the firewall is still sending the traffic to the primary.

Here is a screenshot of the rule:

I hope you can help.

Thank you in advance.

Regards,

Chris

TCP and UDP are different protocols. Probe method and port forwarding should be the same (i think if is not working!). Using icmp instead?

Hallo Luk

Thank you for your reply.

Now I am using the ICMP mode and forward all ports.

But if I completely shut down the first server, the stream is still be sending to the first server, which is configured in the range.

Am I doing something wrong?

Regards,

Chris

Chris,

it is strange! Can you open another thread? This is marked as resolved.

Thanks.

Hello Luk

I just created a new thread right now.

Thanks.

Regards,

Chris