For more information regarding the security incident at F5, the actions we are taking to address it, and our ongoing efforts to protect our customers, click here.

Forum Discussion

Vratix_97086's avatar
Vratix_97086
Icon for Nimbostratus rankNimbostratus
Aug 20, 2009

Discovery/Monitoring Issue

We are seeing a discovery error in the F5 eventlog and Trace.log. The error from the eventlog is shown below. We see the F5 device inthe SCOM console, but it is showing as not monitored and has been ...
management
microsoft
scom
Vratix_97086's avatar
Vratix_97086
Icon for Nimbostratus rankNimbostratus
Aug 20, 2009
**Update**

 

 

Literally 1 min after I posted this the device went healthy. I should clarify that only one monitor went healthy and the other 100 still have no state.

 

 

Also I still see the below error with a current timestamp in the Trace.log

 

 

 

Global Error: 0 : [08/20/2009 11:56:43]Failed to discover device at address: Network-related failure has occurred: [Category]SecureSocketLayer:[Type]Connect