Hi Fabrizio,
To first answer your questions:
1. The current release of the F5 Management Pack (v2.1.5.440) does support LTM platform versions 9.4 and higher, up to the latest.
2. Most importantly, the account running the F5 Monitoring Service should be part of the SCOM Administrators group/role. Also, see issue 5 in the following article, explaining some other SCOM related security permissions required: http://devcentral.f5.com/wiki/default.aspx/MgmtPack/InstallationTroubleshooting.html
Now coming back to your discovery problem, which we try to track on this forum post (apart from the one tracking the Active Directory integration for the F5 Device discovery account, for which I opened up a new post, mentioned in my previous reply), make sure you comply with the requirements suggested in the following articles:
F5 Device User Role Security Requirements:
http://devcentral.f5.com/wiki/default.aspx/MgmtPack/F5DeviceUserRoleSecurity.html
Discovering F5 Networks Devices:
http://devcentral.f5.com/wiki/default.aspx/MgmtPack/DiscoveringF5NetworksDevices.html
Troubleshooting Discovery:
http://devcentral.f5.com/wiki/default.aspx/MgmtPack/TroubleShootingDiscovery.html
* * *
Next I'd suggest attempting a new discovery (for the same F5 device), just to make sure the device configuration is properly discovered/cached/updated. In anticipation of possible discovery errors, I'd recommend enabling the verbose trace logs (see the "Verbose Logging Support" section in http://devcentral.f5.com/wiki/default.aspx/MgmtPack/GeneralTroubleshooting.html) and then proceed with the F5 device discovery.
Let us know if you see any errors or if the F5 device health is still not showing up in SCOM. In this case please archive and email the following to managementpack(at)f5(dot)com:
- trace.log file in \Program Files\F5 Networks\Management Pack\log folder.
- F5 Monitoring Log and Operations Manager log (in the Event Viewer).
Thank you!
Julian