For more information regarding the security incident at F5, the actions we are taking to address it, and our ongoing efforts to protect our customers, click here.

Forum Discussion

LA_Medina_32319's avatar
LA_Medina_32319
Icon for Nimbostratus rankNimbostratus
Apr 12, 2018

SSL Handshake Failure

Hi, We are having trouble with one of our newly created VS. It cant seem to be able to 'communicate' to the backend server (NODEs). We have reachability to the Node IP. We also have an existing V...
application delivery
BIG-IP
devops
LTM
jaikumar_f5's avatar
jaikumar_f5
Icon for Noctilucent rankNoctilucent
Apr 12, 2018

Are you nodes ssl or non-ssl.

If they are non ssl nodes, there's no point of putting https monitor, it will fail. You gotta try putting http monitor.

Having node ip from the same subnet does not mean it is ssl server. Maybe the one working is having ssl enabled and thats why https monitor is put and like wise a serverssl profile.

But if your current non-working is non ssl, put http monitor and remove serverssl profile. Try http instead of https.

curl -vk http://[Node IP]

If your http/https monitor is marking it as up and still VS is inaccessible, we can troubleshoot further.