Monitoring Pools across Data Centers

I am trying to monitor pools across data centers. It is working in one direction only, both sides have been checked that they are set up the same in the configuration and access to the sites. Below is a curl command that I did from each data center. I can see both connect, but one side will not give back the correct answer. Any help with this would be greatly appreciated.

 

Data Center 1 curl -vk https://1.1.1.1/pool_status.html * About to connect() to 1.1.1.1 port 443 (0) * Trying 1.1.1.1... connected * Connected to 1.1.1.1 (1.1.1.1) port 443 (0) * successfully set certificate verify locations: * CAfile: /etc/pki/tls/certs/ca-bundle.crt CApath: none * SSLv3, TLS handshake, Client hello (1): * SSLv3, TLS handshake, Server hello (2): * SSLv3, TLS handshake, CERT (11): * SSLv3, TLS handshake, Server key exchange (12): * SSLv3, TLS handshake, Server finished (14): * SSLv3, TLS handshake, Client key exchange (16): * SSLv3, TLS change cipher, Client hello (1): * SSLv3, TLS handshake, Finished (20): * SSLv3, TLS change cipher, Client hello (1): * SSLv3, TLS handshake, Finished (20): * SSL connection using DHE-RSA-AES256-GCM-SHA384 * Server certificate: * subject: C=US; ST=XX; L=XX; O=XX; OU=XX; CN= * start date: 2016-08-27 00:00:00 GMT * expire date: 2017-09-01 12:00:00 GMT * common name: (does not match '1.1.1.1') * issuer: C=US; O=DigiCert Inc; CN=DigiCert SHA2 Secure Server CA * SSL certificate verify ok.

 

GET /pool_status.html HTTP/1.1 User-Agent: curl/7.19.7 (x86_64-redhat-linux-gnu) libcurl/7.19.7 OpenSSL/1.0.1l zlib/1.2.3 libidn/1.18 Host: 1.1.1.1 Accept: /

 

• SSL read: error:00000000:lib(0):func(0):reason(0), errno 104
• Closing connection 0

Data Center 2 curl -vk https://2.2.2.2/pool_status.html * About to connect() to 2.2.2.2 port 443 (0) * Trying 2.2.2.2... connected * Connected to 2.2.2.2 (2.2.2.2) port 443 (0) * successfully set certificate verify locations: * CAfile: /etc/pki/tls/certs/ca-bundle.crt CApath: none * SSLv3, TLS handshake, Client hello (1): * SSLv3, TLS handshake, Server hello (2): * SSLv3, TLS handshake, CERT (11): * SSLv3, TLS handshake, Server key exchange (12): * SSLv3, TLS handshake, Server finished (14): * SSLv3, TLS handshake, Client key exchange (16): * SSLv3, TLS change cipher, Client hello (1): * SSLv3, TLS handshake, Finished (20): * SSLv3, TLS change cipher, Client hello (1): * SSLv3, TLS handshake, Finished (20): * SSL connection using DHE-RSA-AES256-GCM-SHA384 * Server certificate: * subject: C=US; ST=XX; L=XX; O=XX; OU=XX; CN= * start date: 2016-08-27 00:00:00 GMT * expire date: 2017-09-01 12:00:00 GMT * common name: (does not match '2.2.2.2') * issuer: C=US; O=DigiCert Inc; CN=DigiCert SHA2 Secure Server CA * SSL certificate verify ok.

 

GET /pool_status.html HTTP/1.1 User-Agent: curl/7.19.7 (x86_64-redhat-linux-gnu) libcurl/7.19.7 OpenSSL/1.0.1l zlib/1.2.3 libidn/1.18 Host: 2.2.2.2 Accept: /

 

• HTTP 1.0, assume close after body < HTTP/1.0 200 OK < Server: BigIP
• HTTP/1.0 connection set to keep alive! < Connection: Keep-Alive < Content-Length: 2 <
• Connection 0 to host 2.2.2.2 left intact
• Closing connection 0
• SSLv3, TLS alert, Client hello (1):