Error adding rules to collection: Can't find rule for MCP tag

A possible reason for the errors that you see in the gtm log is that some of the rules enabled by default in the F5 Management Pack could not be resolved by the MCP module (on the F5 device). This could happen in either of the following cases:

 

 

1. the F5 device being discovered is a virtual appliance.

 

2. the platform version on the F5 device is older than 10.x (possibly at v9.3.x)

 

 

Can you confirm if either of these two assumptions are true? Can you also check the F5 Monitoring Log on your SCOM Management Server where you discovered the F5 device from. You may as well see some warnings there pointing to the MCP tags that could not be queried. Ultimately, you could disable these stats being queried altogether. Another option for you, if 2 above is true, would be to wait for our upcoming F5 MP release (scheduled for this month) where we have a few hotfixes included, some of them addressing issues 1 and 2 mentioned here.

 

 

Can you also send us the verbose service log to managementpack(at)f5(dot)com? Instructions on how to enable these trace logs are found in the "Verbose Logging Support" section of the following article/wiki: http://devcentral.f5.com/wiki/default.aspx/MgmtPack/GeneralTroubleshooting.html

 

 

Once you enable verbose logging and restart the F5 Monitoring Service, go to the SCOM Operations Console > Monitoring > F5 Device > Actions > Refresh Collection Rules and run this action. After done, archive the trace.log file (as described in the wiki) and send it to us.

 

 

Let us know. Thanks!

 

Julian