SSL errno 104 through F5 (vip), directly with curl ok
Hello community,
I've the following configuration design within a virtual server configuration:
- A virtual server will route the traffic based on the hostname within the request to different pools.
- Client- and server SSL are enabled
- The routing will been done with LTM policys instead of iRules.
- There are five backend systems which should be accessible over the vs
- SNAT is enabled
Now, the problem is that from the five backends are only three backend systems are accessible. The other two systems don't work. Within the LTM policy I've additional enabled the "log" option to make sure that the routing will work.
To find out what is going wrong, I've executed a curl and openssl query direct to the backend system from the F5 console. Connection can be established and I receive the 200 status code. If I do the same over the VIP of the configuration I receive the following error code:
read:errno=104
These are my teststrings:
openssl s_client -connect vip:443
GET /dialin/ HTTP/1.1
Host: lyncpool1 or 2 or 3 ...
With lyncpool1 as the value for the host it will work and with lyncpool2 I receive the error code from above. The client SSL settings from the vip will been displayed. It seams that there is an issue/problem while talking SSL with the backend system which will not work. If I do the same with the original IP of the system instead of the VIP, each system are working fine.
Have anybody an idea? I've just readed some threads within devcentral to similar problems but nothing helped my until now.
Regards seilemor