We have a VIP of 184.108.40.206:443 and Pool having 2 pool members(220.127.116.11:443 and 18.104.22.168:443) and currently running fine on array load balancer.
Having encrypted session on both client side and server side.
Android mobile Application server is configured to allow only TLS1.2 traffic.
As soon as traffic was shifted to our F5 device(LTM & ASM) we are facing below issue as viewed in wireshark after tcpdump.
F5 VIP 22.214.171.124:443 >TLS1.1>ClientHello> 126.96.36.199:443
188.8.131.52:443 >TCP_RST> 184.108.40.206:443
Application server is sending RST back to F5 due to TLS 1.1 not allowed.
F5 VIP 220.127.116.11:443 >TLS1.2>ClientHello> 18.104.22.168:443
Application server is accepting and traffic is processed successfully.
Due to above issue, all user traffic is handled by only one server and hence we are facing issues.
LB Method=Least Connection, Persistence=SourcePersistence,SSL Client & Server Profile,SNAT=Yes, map to VIP
Wanted to understand why F5 is sending Client Hello of TLS 1.1 to 1st pool member and TLS 1.2 to 2nd pool member, during initial stage in same Pool ?
Can anybody help me to understand the exact issue faced here and provide solution ?
What is ssl profile configuration at F5 end?
SSL Client & Server Profile is configured in VS. In SSL Profile configuration .pfx certificate and key is mapped(nothing else) and as I said the SSL Profiles are working fine for 1 pool member. Most importantly both 2 pool members are working fine on Array device currently.
I would verify the SSL profile on the F5 end and the cipher restrictions on the server itself. I would compare the cipher suite on both pool members to see if there is a difference, it may be that the server that is working is allowing TLS1.1, which you don't actually want according to your post.
You made 2 statements above and my reply is
1) I verified configuration on both F5 and Array(SSL Profile configuration .pfx certificate and key is mapped(nothing else)). On Array it is working fine.
2) I verified both application server are only processing TLS 1.2 negotiations only and working fine when traffic is passing through Array.
You can restrict SSL/TLS version to TLS1.2 only and blocking rest on F5 server SSL profile then check. Setting is available as shown below under server ssl profile.
Making changes in these setting should resolve your issue.
I tried your above solution when we faced the issue. In option list i selected "No TLS 1.1", still issue was persistent. Since customer had moved/routed production traffic on F5 without any pre-planned/emergency downtime, they did not give me enough time to troubleshoot the issue and routed traffic back on Array, also gave me NO troubleshooting captures and images of this technical issue they previously had.
Ok Rahul but i think only disabling TLS1.1 will not resolve your issue. If you get chance to work on same again in future, then keep TLS1.2 enabled only and rest should be disable and then try.
I hope it will work for you!
Ok Mayur Thanks, can try your suggestion, next time if I hit the same issue again.