Log in to the F5 server's management interface. "Virtual Server" -> virtual server that you want to configure.- >"Resources" tab. ->click on the pool that the virtual server->Click on the "Members" tab-> Click on the member that you want to configure for HTTP.
Under "Node Properties," change the "Port" to 80 (for HTTP) instead of the default 443 (for HTTPS). Click "Update" to save the changes.
Once you have made this change, the F5 server will allow HTTP connections to the API on the specified port.
I saw another user (TimRiker) helping you on the other post, and I'm inclined to repeat his answer: if you're using a self-signed certificate, you have to add that very certificate to Java's trust store. If you're using a certificate signed by a private CA, you need to add the root (and possibly the rest of the chain) to the trust store.
This assumes you're connecting to the management interface, normally called "mgmt"; you can confirm that with "ifconfig". Break the tcpdump with Ctrl-C, and then download the file with SCP, open in wireshark, confirm SSL handshake includes what you expected.
No, you must never import private keys when dealing only with trust. Keys are used for encryption/decryption, not for trust. In this case it seems you're using a self-signed certificate for F5 management, so it's like a special case of a Root CA establishing the trust for itself (by definition, a Root CA is self-signed).
But... reading between the lines in your question makes me believe things are not working yet. Or are they?
If not, I would suggest the procedure in my previous post: get a traffic capture, confirm the certificate your java machine is getting from the F5 box is the one you are expecting to see there. Or in other words, if that certificate is signed by the one you have imported into java trust store.
The Device certificate has the CN as "localhost.localdomain" where the hostname is 10.10.10.10. This causing the hostname verification to fail.Can anyone please let me know is there an issue with the certificate?
Indeed, the default management certificate does not include a SAN for the management IP. In your place, I would replace the management certificate with one for which you can control the trust chain. Tipically this would be an Active Directory CA chain, or similar PKI.
If you don't have a proper PKI available you can try a "light" version, like TinyCA (which is a simple graphical interface for openssl). Or pure openssl commands if you're into that!
Either way, you must import the CA trust chain into java trust store. If you want to use the IP address to access your F5 system, don't forget to add something like "IP:10.10.10.10" to the SAN field of the certificate.