Discovery/Monitoring Issue

Thanks Marc.

 

 

Here are my findings, after thoroughly analyzing the trace logs you've sent us:

 

 

- the intermittent connection errors are happening while the F5 Monitoring Service attempts to initiate an SSL connection with the F5 device, during the periodical heartbeat / update / refresh cycle.

 

- the actual SSL error (SSL_ERROR_SYSCALL / OpenSSL) reported by the F5 Monitoring Service (as a client) points to a 'premature' ending of the connection on the server side (big3d / F5 device).

 

- the F5 Monitoring service attempts to reconnect repeatedly until the connection to the F5 device will be available again.

 

 

This being said, I believe the problem is somewhere between the box running the F5 Monitoring service and the F5 device and it may involve:

 

 

- network / routers,

 

- proxies (if any, between the monitoring box and the F5 device),

 

- big3d daemon crashing (on the F5 device)

 

 

My feeling is that the problem is related to the network, or anything on it between the monitoring box and the F5 device. Here's what I would suggest:

 

 

- run a traceroute from the monitoring box to the F5 device (and you can send it to us: ManagementPack(at)f5.com) and we can analyze it together;

 

- are there any proxies (HTTP, etc., including other Big-IP device(s)) between the monitoring box and the F5 device?

 

- try to ping / telnet the F5 device from a different box / network and see if the intermittent connection failures still happen;

 

 

Ultimately, just to be sure all is well on the F5 device / server side, we could also analyze the big3d logs (found in /var/log and /var/core on the BigIP). Just check if the /var/core has any core files (listing would suffice) during the time when the connection drops, and if there's any we'll take it from here.

 

 

Let us know, and we'll investigate further.

 

 

Thanks,

 

Julian