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.   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
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?
The refresh time of vstatus for new created LUN