After SEGV2 upgrade, F5 no longer detecting

[tsmithcoc]

Hi,

We have 2x SEG servers. After upgrading to V2 on 1 of the SEGs and modifying the URI endpoints, that SEG was detected and is receiving traffic.

The same steps were performed on our secondary server, however the F5 detects it as down.

Anyone run into the issue with F5 detecting SEGs after upgrading to SEG V2?

Thanks!

[UiliamFoschiera]

Hi tsmithcoc,

Here, our F5 monitors port TCP 443 of both Seg V2 servers, in round-robin load balancing mode. It works fine, and we no had issues when we migrated SEG from classic to V2.

How your F5 is set to detect servers?

Regards

Uiliam Mello

[ogushia]

Hi tsmithcoc

In my test environment, when I used health monitoring method [HTTPS HEAD Request] response of each versions was following.

-SEG Classic : HTTP/1.1 200 OK

-SEG V2 : HTTP/1.1 404 Not Found

In above case, after migrated to SEG V2 the SEG server was detected down, so I changed monitoring method [HTTPS GET Request] to resolve issue.

Regards