Hi Ravi,
I went through the logs you've sent me and apparently the two key modules for collecting and interpreting the rules within the F5 Management Pack (F5 MP) - Rules Override Manager and Condition Detection - are not initialized correctly, in your environment. Here's what I would like you to do, to gather more specific information about the errors related to these two modules:
- stop the F5 MP monitoring service,
- add the following sections to the F5 MP service configuration file (f5mpsvc.exe.config), under the section (within :
switchName="sourceSwitch"
switchType="System.Diagnostics.SourceSwitch">
switchName="sourceSwitch"
switchType="System.Diagnostics.SourceSwitch">
- save the service configuration file (f5mpsvc.exe.config);
- delete the trace.log file (in the %Program Files%\F5 Networks\F5 Management Pack\Log folder)
- restart the F5 MP monitoring service and wait at least 5 minutes (to get a couple of refresh cycles for collecting rules); you can also run the tasks associated with refreshing the rules inside the SCOM Management Console).
- save the trace.log file and send it to us: managementpack(at)f5.com
Also, check and make sure the service account running the F5 MP monitoring service has the Operations Manager Administrator user role associated with it. And on the a last note, please run the SQL query I sent you in a previous post (about the similar topic):
Click here
and let me know if there's any raw data retrieved from the Operations Manager live and data warehouse databases. This would also help diagnosing the reporting problems that you may have. I'll post the SQL queries again, here:
/**************************************************
* Get the stats from the live database
***************************************************/
select
BME.FullName,
PCV.ManagedEntityId,
PCV.CounterName,
PDAV.SampleValue,
PDAV.TimeSampled
from [OperationsManager].[dbo].[BaseManagedEntity] BME with (nolock)
join [OperationsManager].[dbo].[PerformanceCounterView] PCV with (nolock) on BME.BaseManagedEntityID = PCV.ManagedEntityId
join [OperationsManager].[dbo].[PerformanceDataAllView] PDAV with (nolock) on PDAV.PerformanceSourceInternalId = PCV.PerformanceSourceInternalId
where BME.FullName like 'F5.%'
Data warehouse query (~OperationsManagerDW):
/**************************************************
* Get the stats from the data warehouse
***************************************************/
select
PR.ManagedEntityRowId,
ME.ManagedEntityGuid,
PR.SampleValue,
PR.DateTime,
ME.FullName,
R.ObjectName,
R.CounterName
from [OperationsManagerDW].[Perf].[vPerfRaw] PR with (nolock)
join [OperationsManagerDW].[dbo].[PerformanceRuleInstance] PRI with (nolock) on PR.PerformanceRuleInstanceRowId = PRI.PerformanceRuleInstanceRowId
join [OperationsManagerDW].[dbo].[PerformanceRule] R with (nolock) on PRI.RuleRowId = R.RuleRowId
join [OperationsManagerDW].[dbo].[ManagedEntity] ME with (nolock) on PR.ManagedEntityRowId = ME.ManagedEntityRowId
where ME.FullName like 'F5.%'
These issues may all be related (the rule collection and processing failure and reports data not showing), and again, make sure the account running the F5 MP service is an Ops Manager Admin.
Thanks,
Julian
Nimbostratus
