Hi Fabrizio,
Thank you for the detailed error report. For some reason the error log(s) that you were referring to have not been attached to your post. From what you are describing, I would assume your discovery fails because of device related connectivity, authorization, etc, issues. Please enable verbose logging support (see http://devcentral.f5.com/wiki/default.aspx/MgmtPack/GeneralTroubleshooting.html) and try discovery again. Gather the following logs (to have as much information as we can possibly have) to expedite troubleshooting:
- trace.log file (in \Program Files\F5 Networks\Management Pack\log folder)
- F5 Monitoring Log (in Event Viewer)
- OperationsManager log (in Event Viewer)
Zip the logs to managementpack(at)f5(dot)com.
Also, please consider the following important prerequisites for a successful F5 device discovery:
- admin credentials for the F5 device account specified in discovery.
- enable TCP port 4353 through the firewall for bi-directional [iQuery] communication with the F5 device.
- enable the 'Authorize big3d agent update' [checkbox] in the F5 Discovery wizard.
Here are some relevant links detailing these prerequisites for F5 Management Pack discovery:
- http://devcentral.f5.com/wiki/default.aspx/MgmtPack/F5DeviceUserRoleSecurity.html
- http://devcentral.f5.com/wiki/default.aspx/MgmtPack/TroubleShootingDiscovery.html
Let us know.
Thank you!
Julian