F5 Discovery failure

I found this thread and am also having a similar issue. I have a clustered pair of LTM 1500s running 9.3.1 build 37.1. My SCOM server is a single server and I recently applied the CU3 hoping to get the discovery working. Since that did not work I saw there was a more recent release to the Management Pack than the 2.0.0 version I had in place, so I upgraded to the 2.1.4 in hopes my units would get discovered, but they were not.

 

 

My SCOM server sits on the same subnet as my units, 192.168.162.0/23. In the F5 Monitoring Log I get the error

 

 

Failed to discover device at address: 192.168.163.248

 

Network-related failure has occurred: [Category]SecureSocketLayer:[Type]ConnectFailure;LastError=SSL IO Error 474139472: SYSCALL: UNKNOWN

 

 

In the actual log that you see when double-clicking the failed discovery I get

 

Execute device discovery:Failure

 

Failure Message: F5Networks.Protocols.iQuery.iQueryException: [Category]SecureSocketLayer:[Type]ConnectFailure;LastError=SSL IO Error 474139472: SYSCALL: UNKNOWN

 

 

I am using an admin account for discovery so the permissions for the account should be suitable. What else should I be looking at?