Important note about SSL VPN compatibility for 20.0 MR1 with EoL SFOS versions and UTM9 OS. Learn more in the release notes.

Thread Info
  • State Verified Answer
  • Locked Locked
  • Replies 7 replies
  • Subscribers 39 subscribers
  • Views 14708 views
  • Users 0 members are here
Options
Suggested
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Load Balancing - First Alive TCP Port

ChrisDrescher

Hello Community

I am trying to create a first alive - fail over rule, which is checking TCP port 1935.

So I changed the port from 80 to 1935 and saved the rule. When I now review the rule again, there is still port 80 used for the health check.

Is that a bug??

Thank you for your help.

Regards,

Chris



This thread was automatically locked due to age.
Parents
  • 0

    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.

  • 0 in reply to lferrara

    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

Reply
  • 0 in reply to lferrara

    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

Children
Unfiltered HTML