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 event ID is 301. We have not changed the password for the account that is used to communicate with the F5. We have tried several restarts of the F5 service and a reboot of the SCOM machine to no avail. We have even reset the big3d service on the F5 since then. That has not worked either. What could have caused this and how do we fix it?
Failed to discover device at address: 10.41.52.27
Network-related failure has occurred: The request failed with HTTP status 401: F5 Authorization Required, Invalid Token.
F5Networks.Protocols.iControl.iControlException: The request failed with HTTP status 401: F5 Authorization Required, Invalid Token.
at F5Networks.Protocols.iControl.Utilities._HandleWebException(WebException webException)
at F5Networks.Protocols.iControl.Utilities.WrapNetworkErrors[ReturnType](GenericVoidHandler`1 soapCall)
at F5Networks.ManagementPack.Discovery.Networking.iControlDiscovery._MakeSoapCall[ReturnType](GenericVoidHandler`1 soapAsyncBegin, GenericTypeHandler`2 soapAsyncComplete)
at F5Networks.ManagementPack.Discovery.Networking.iControlDiscovery.CoreGetSystemLocalTime()
at F5Networks.ManagementPack.Discovery.Networking.iControlDiscoveryBase.<>c__DisplayClass1.b__0()
at F5Networks.ProgressTracking.Tracer.DoActionWithTryFinally(VoidVoidDelegate activeCode, VoidVoidDelegate preCode, VoidGenericHandler`1 postCode, VoidVoidDelegate postCodeSuccess, VoidGenericHandler`1 postCodeFailure)
at F5Networks.ProgressTracking.Tracer.DoActionWithTryFinally(VoidVoidDelegate activeCode, VoidVoidDelegate preCode, VoidVoidDelegate postCodeSuccess, VoidGenericHandler`1 postCodeFailure)
at F5Networks.ProgressTracking.Tracer.TraceCall(VoidVoidDelegate activeCode, String action, String area, String category, Int32 id)
at F5Networks.ManagementPack.Discovery.Networking.iControlDiscoveryBase.get_SystemLocalTime()
at F5Networks.ManagementPack.Discovery.DiscoveryManager.DiscoverDevice._TryToConnectToDeviceWithToken(ManagementPackIQueryConnection deviceConnection)
at F5Networks.ManagementPack.Discovery.DiscoveryManager.DiscoverDevice._ConnectToDevice(Credentials deviceCredentials)
at F5Networks.ManagementPack.Discovery.DiscoveryManager.DiscoverDevice._Execute(DiscoveryInfo discoveryInfo)
at F5Networks.ManagementPack.Discovery.DiscoveryManager.DiscoverDevice.<>c__DisplayClassc.b__a()
at F5Networks.ProgressTracking.ProgressEventSourceBase`1.<>c__DisplayClass8.b__5()
at F5Networks.ProgressTracking.Tracer.DoActionWithTryFinally(VoidVoidDelegate activeCode, VoidVoidDelegate preCode, VoidGenericHandler`1 postCode, VoidVoidDelegate postCodeSuccess, VoidGenericHandler`1 postCodeFailure)
at F5Networks.ProgressTracking.Tracer.DoActionWithTryFinally(VoidVoidDelegate activeCode, VoidVoidDelegate preCode, VoidGenericHandler`1 postCode)
at F5Networks.ProgressTracking.ProgressEventSourceBase`1.DoActionWithProgressNotification(VoidVoidDelegate activeCode, String action)
at F5Networks.ManagementPack.Discovery.DiscoveryManager.DiscoverDevice.Execute(DiscoveryInfo discoveryInfo)
at F5Networks.ManagementPack.Discovery.DiscoveryManager._SyncFinishDiscovery(DiscoverDeviceHandler discoveryHandler, DiscoveryInfo info)
at F5Networks.ManagementPack.Discovery.DiscoveryManager._AsyncFinishDiscovery(AsyncDiscoveryInfo asyncInfo)
- 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.
