Forum Discussion
mbayer_59439
Nimbostratus
NimbostratusF5 Discovery Error
Hi,
After the install of the mgt pack and license install I try to discover all my F5 10.2 devices (all same level) and get this weird error -- I tried the admin, root, and my account (admin priv) all with same result:
Execute device discovery:Failure
Failure Message: F5Networks.Protocols.iControl.iControlException: The request failed with HTTP status 401: F5 Authorization Required.
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) in c:\home\f5cm\sandbox\cc\builds\ballantine\104734\Branches\Trunk\Platform\Discovery\Networking\iControlDiscovery.cs:line 88
at F5Networks.ManagementPack.Discovery.Networking.iControlDiscovery.CoreGetSystemLocalTime() in c:\home\f5cm\sandbox\cc\builds\ballantine\104734\Branches\Trunk\Platform\Discovery\Networking\iControlDiscovery.cs:line 99
at F5Networks.ManagementPack.Discovery.Networking.iControlDiscoveryBase.<>c__DisplayClass1.b__0() in c:\home\f5cm\sandbox\cc\builds\ballantine\104734\Branches\Trunk\Platform\Discovery\Networking\iControlDiscoveryBase.cs:line 59
at F5Networks.ProgressTracking.Tracer.<>c__DisplayClass1.b__0()
at F5Networks.ProgressTracking.Tracer.DoActionWithTryFinally[TReturnResult](GenericVoidHandler`1 activeCode, VoidVoidDelegate preCode, VoidGenericHandler`1 postCode, VoidVoidDelegate postCodeSuccess, VoidGenericHandler`1 postCodeFailure)
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() in c:\home\f5cm\sandbox\cc\builds\ballantine\104734\Branches\Trunk\Platform\Discovery\Networking\iControlDiscoveryBase.cs:line 57
at F5Networks.ManagementPack.Discovery.DiscoveryManager.DiscoverDevice._ConnectToDeviceAndPushCertificate(Credentials deviceCredentials, ManagementPackIQueryConnection deviceConnection) in c:\home\f5cm\sandbox\cc\builds\ballantine\104734\Branches\Trunk\Platform\Discovery\DiscoverDevice.cs:line 697
at F5Networks.ManagementPack.Discovery.DiscoveryManager.DiscoverDevice._ConnectToDevice(Credentials deviceCredentials) in c:\home\f5cm\sandbox\cc\builds\ballantine\104734\Branches\Trunk\Platform\Discovery\DiscoverDevice.cs:line 562
at F5Networks.ManagementPack.Discovery.DiscoveryManager.DiscoverDevice._Execute(DiscoveryInfo discoveryInfo) in c:\home\f5cm\sandbox\cc\builds\ballantine\104734\Branches\Trunk\Platform\Discovery\DiscoverDevice.cs:line 196
at F5Networks.ManagementPack.Discovery.DiscoveryManager.DiscoverDevice.<>c__DisplayClassc.b__a() in c:\home\f5cm\sandbox\cc\builds\ballantine\104734\Branches\Trunk\Platform\Discovery\DiscoverDevice.cs:line 156
at F5Networks.ProgressTracking.ProgressEventSourceBase`1.<>c__DisplayClass6.b__5()
at F5Networks.ProgressTracking.ProgressEventSourceBase`1.<>c__DisplayClassb`1.b__8()
at F5Networks.ProgressTracking.Tracer.DoActionWithTryFinally[TReturnResult](GenericVoidHandler`1 activeCode, VoidVoidDelegate preCode, VoidGenericHandler`1 postCode, VoidVoidDelegate postCodeSuccess, VoidGenericHandler`1 postCodeFailure)
at F5Networks.ProgressTracking.Tracer.DoActionWithTryFinally[TReturnResult](GenericVoidHandler`1 activeCode, VoidVoidDelegate preCode, VoidGenericHandler`1 postCode)
at F5Networks.ProgressTracking.ProgressEventSourceBase`1.DoActionWithProgressNotification[TReturnResult](GenericVoidHandler`1 activeCode, String action)
at F5Networks.ProgressTracking.ProgressEventSourceBase`1.DoActionWithProgressNotification(VoidVoidDelegate activeCode, String action)
at F5Networks.ManagementPack.Discovery.DiscoveryManager.DiscoverDevice.Execute(DiscoveryInfo discoveryInfo) in c:\home\f5cm\sandbox\cc\builds\ballantine\104734\Branches\Trunk\Platform\Discovery\DiscoverDevice.cs:line 155
at F5Networks.ManagementPack.Discovery.DiscoveryManager._SyncFinishDiscovery(DiscoverDeviceHandler discoveryHandler, DiscoveryInfo info) in c:\home\f5cm\sandbox\cc\builds\ballantine\104734\Branches\Trunk\Platform\Discovery\DiscoveryManagerAsyncWork.cs:line 240
at F5Networks.ManagementPack.Discovery.DiscoveryManager._AsyncFinishDiscovery(AsyncDiscoveryInfo asyncInfo) in c:\home\f5cm\sandbox\cc\builds\ballantine\104734\Branches\Trunk\Platform\Discovery\DiscoveryManagerAsyncWork.cs:line 274 Attempt to connect to the iControl device socket:Success
Attempt to connect to the iControl device socket:Success
Any help would be appreciated.
Thanks,
Mike
4 Replies
- Hi Mike,
The error you get (HTTP 401: F5 Authorization Required), shows that you may not be able to access the iControl web service interface on the F5 device. Before performing more involved iControl calls into the device, the F5 Management Pack 'pings' the iControl web-service interface availability by placing a simple call for retrieving the local system time on the F5 device. This iControl call apparently fails in your environment. Such a call would normally go through the device's authZ security layer even with guest credentials. Can you access the iControl web-service interface at all on the device? From any browser, try:
https://[user]:[password]@device_ip:443/iControl/iControlPortal.cgi (where [user] and [password] are the device credentials that you're using for discovering the F5 device)
or
https://device_ip/iControl/iControlPortal.cgi
Let me know if you get any errors, in both cases, and we'll take it from here.
Julian 
mbayer_59439Julian,
Thank you -- I am past that and on to a new error -- bad IP?? Let me know if you want more -- the stack trace is huge. Thanks
Execute device discovery:Failure
Failure Message: F5Networks.ManagementPack.DataAccess.DataFormatException: Invalid IP address: 10.0.216.1%2
at F5Networks.ManagementPack.DataAccess.Configuration.Entity.EntityData.InstanceParentEntityNameToNameAddressPort(EntityType entityType, String instanceParentName, String entityName, String& name, IPAddress& ipAddress, String& port, String& slotId)
at F5Networks.ManagementPack.DataAccess.Configuration.Entity.EntityInfo..ctor(IPAddress deviceIP, EntityData entityData)
at F5Networks.ManagementPack.DataAccess.OperationsManager.OpsMgrMonitoringAdapter.ConfigObject..ctor(IPAddress deviceIP, EntityData entity, CustomMonitoringObject customMonitoringObject)
at F5Networks.ManagementPack.DataAccess.OperationsManager.OpsMgrMonitoringAdapter._CreateChildEntity(SdkConnector connector, IPAddress deviceIP, EntityData entity, MonitoringObject hostingParentObj, DeviceConfigStats configStats)
at- mbayer_59439Julian,
Could a route domain canuse a problem here???
Thanks,
Mike - Yes Mike. The route domain IP address(es) would cause this type of issue when discovering an F5 device that has route domains defined in the configuration. We know about this problem and have a case filed in our bug tracking system. We'll let you know when we have a fix for it.
Julian
