Forum Discussion
Samir
Sep 05, 2020MVP
Which BIGIP version you are running? As such not observed such behaviour in BIG-IP.
Gone through both wireshark image and found that one of the connection is going on x.x.x.12 and other is x.x.x.11. To narrow done issue, keep one member in pool and isolate the issue.
Try below options?
- Remove the https monitor from pool , save the config and add back same monitor in pool
- openssl s_client -connect x.x.x.x:443 -tls1_2
- openssl s_client -connect x.x.x.x:443 -tls1
Hope this will help you.