Forum Discussion
Jeremy_Bridges_
Nimbostratus
NimbostratusF5 Authorization Error from SCOM F5 Monitoring Service
Sometime on 9-26 our DEV F5 device stopped communicating well with the F5 monitoring service on our DEV SCOM machine. We are getting the error below in the F5 Monitoring Log every 4-5 minutes. The e...
This issue has been resolved.
When Big-IPs are discovered, the clock times of both the OpsMgr server and the Big-IP are recorded and used when generating tokens to communicate via iControl. If those clock times diverge later by more than 10 minutes, the F5 Management Pack will not be able to communicate any more with the Big-IP.
The solution is to keep the clocks in sync either with time servers or with manual intervention.
A fix for this issue is currently scheduled to be included in the next release of the pack.
