Start a Conversation

This post is more than 5 years old

Solved!

Go to Solution

1546

August 17th, 2017 03:00

The refresh time of vstatus for new created LUN

Hi,

    We use snmp collector to polling LUN MIB table, while we create some new LUNs, we found it will cost hours to set "vstatus=active", so we can only see the new LUN hours later, is it normal, any way to make it faster?

141 Posts

August 17th, 2017 06:00

Hi warmghost,

The vstatus property is set by the import_variable_status.task which runs every 6 hours. However don't need the vstatus to be set for the new lun to be displayed in the reports, instead of the having vstatus=='active' in the filter, you should use !vstatus=='inactive', this will exclude everything that has been marked as inactive instead of displaying only components that are marked as active.

Note that for a new component to be displayed in the report, it must be in the property-store (in order to speed up report generation SRM uses a property-store which basically acts as a local cache for properties). When a report runs, the properties are actually queried from the property-store and not directly from the mysql database.


The import-properties.task runs on a variable schedule which depends on the last execution time.

  • If the average of the last 5 executions takes < 10 seconds, schedule every 5 minutes
  • If the average of the last 5 executions takes < 1 minute, schedule every 20 minute
  • If the average of the last 5 executions takes < 5 minutes, schedule every hour
  • If the average of the last 5 executions takes < 10 minutes, schedule every 4 hours
  • If the average of the last 5 executions takes < 1 hour, schedule at 5:00AM and 12:00PM

In order for new properties to be added faster, you can run the task manually by going to Centralized-Management -> Scheduled Tasks -> Database -> import.properties.task

Regards,

Isaka

19 Posts

August 25th, 2017 01:00

Hi Isaka,

     We tested this for days, found that on SRM 4.1, new created LUN or Host will not be synchronized to report for even 1~2 days. But when we restart all the services or restart whole SRM server, this problem resolved, is it a bug?

     BTW, as a workaround, could you please let us know which service could help to synchronize LUN or Host when be restarted?


19 Posts

August 25th, 2017 23:00

Hi Isaka,

     As test, run task "mysql-maintenance-tool/Default/optimize-tables.task" from "centralized-management" console could trigger data refresh, and this task only run once a week by default. Is it normal? Any better way to resolve this problem?

141 Posts

August 29th, 2017 05:00

Hi warmghost,

it should not take that long for a new lun to show up in the report, since restarting fixed it i suspect that a service or task may have been stuck.

The optimize-tables.task is a db maintenance task, it has no impact on component visibility in the reports.


You should open a service request with support so that we can go trough logs and see what happened.



regards,

Isaka

19 Posts

August 29th, 2017 18:00

Hi Isaka,

     Thank you, as investigation it may caused by high load of server, we are checking this, will open service request if needed.

No Events found!

Top