Unsolved
This post is more than 5 years old
19 Posts
0
630
August 29th, 2017 04:00
New metrics are collected but not refreshed in report timely
Dear,
We found that on SRM 4.1, with SNMP collector, new created LUN or Host will not be synchronized to report for even 1~2 days. As test, run task "mysql-maintenance-tool/Default/optimize-tables.task" from "centralized-management" console could trigger data refresh, after refresh we could see all the data before refresh. This means the data was collected but not synchronized to report.
This task only run once a week by default, so we guess there must be a better way to resolve refresh problem, could it be fixed by configuration change, or by patch?
No Events found!
isakats
141 Posts
1
August 30th, 2017 05:00
Hi warmghost,
The optimize-table.task should not prevent the new lun's from being displayed in the reports.
The successful completion of the import-properties.task is key for the new lun's to show up in the reports; several things could be preventing this task from completing correctly like high cpu load / lack of free memory, locked or crashed database tables, network connectivity issues, database metric count being above 1.5 million, etc...
There is also the possibility of a backlog in the data processing between the snmp collector and database, you can validate this by looking in the failover filters, load-balancer and the backend's tmp directory
My colleague John wrote a document on managing SRM health here; it's a bit old but the general concept still applies
We also have a youtube video that's more recent
Also, if you open a service request with support we can validate these points and do a quick sanity check of the environment and setup.
regards,
Isaka