SCOM F5 Objects Not Consistent with Objects on F5

I have also seen several SQL connection failures in previous logs you've sent. For some reason the SQL server is occasionally rejecting connections or the network route to the SQL server gets broken. While certainly not a good thing, we do have recovery logic which keeps trying to recreate the connection and generally succeeds from the logs I've seen. If there is a problem with SQL server that could affect OpsMgr as well though.

 

 

The error at 5:30 pm means we tried to do a basic TCP connect to port 443 (iControl) during a discovery on the BIG-IP and it timed out without a response. The next error is another discovery that had a certificate problem. Do you still have the connection analyzer tool that I sent about 3 months ago? There seems to be some connectivity/certificate problems with discovery. I believe last time it was due to the clock getting off on the BIG-IP. These discovery issues should not affect pool member state however.

 

 

The "Service Logging" message just means the the "f5mpsvc.exe.config" file got updated (probably you turning on verbose logging?). Should not affect pool member health either.

 

 

Finally, the last error is due to a discovery where the "Update Big3D" checkbox was not checked on the discovery dialog box, or if using command line, the "/d:UpdateBig3d" switch was not specified. We require the user to authorize this explicitly since it's changing that binary on the BIG-IP. Again, no effect on pool members.