Discovery/Monitoring Issue

To answer your questions first:

 

 

- In the Health Explorer of the F5 device you should see the monitors that are enabled by default (i.e. by design), and some of them should actually signal a valid state (as you pointed out with the "Control Device Connection" monitor). You should also see at least another state (green) for the "Global Memory Used" performance counter monitor, which is controlled by the related threshold rule (which is again, enabled by default in the F5 Management Pack). For all the other performance counter monitors, you would override / enable the related Collection / Threshold Rules, to actually 'arm' the related monitor (as you correctly assumed in your post).

 

 

- Not seeing any alerts and performance data coming in, would probably be a fall-out from you network / connectivity issue with the F5 device, which we will troubleshoot together.

 

 

- Viewing the performance counters collected by the F5 Management Pack would be simply by invoking either the Open > Performance View in the context menu related to an F5 Device / Object (in the diagram view / hierarchy), or by selecting the "Performance View" in the Actions pane (on the right hand side of the SCOM Operations Console). But you have to make sure the related performance counters are enabled / collected, by setting the appropriate collection rules.

 

 

- The F5 Management Pack doesn't feature a dedicated Alert View. Invoking the Alert View for the F5 Management Pack should be a matter of preference, being opened either from the diagram or state view. There's no recommended or intended way of using it, from our end.

 

 

* * *

 

 

For troubleshooting the network connectivity issues with the F5 Device, we will need a detailed trace log, which you will have to enable for the F5 Management Pack. See the "Verbose Logging Support" section in the Troubleshooting page (Click here). With the verbose logging enabled, attempt to discover a new device and wait for a drop in the device connection (as you mentioned, in about 5..10 minutes), than zip the trace.log file located at %Program Files%/F5 Networks/Management Pack/log and post it here, or you can email it directly to ManagementPack(at)f5.com. We can also provide FTP access for uploading it. Once we get the trace, we'll take a look and will get back to you.

 

 

Thank you,

 

Julian