OnCommand Storage Management Software Discussions

Missing data from harvest after Data ONTAP upgrade

Hi,

 

after upgrading Data ONTAP from version 8.2.3 to 8.3.2, the Protocol Backend IOPs and the Disk MB/s charts in Grafana stopped showing the nfs_ops and the disk_data* metrics previously available. Looking at the harvest logs, the following messages started appearing right after the upgrade:

 

[2016-04-29 00:12:06] [WARNING] [wafl_hya_sizer] update of instance_list cache failed with reason: Object "wafl_hya_sizer" was not found.
[2016-04-29 00:12:06] [WARNING] [wafl_hya_sizer] instance-list update failed.
[2016-04-29 00:12:07] [WARNING] [disk] update of instance_list cache failed with reason: Object "disk" was not found.
[2016-04-29 00:12:07] [WARNING] [disk] instance-list update failed.
[2016-04-29 00:14:12] [WARNING] [system] update of data cache failed with reason: Object "system" was not found.
[2016-04-29 00:14:12] [WARNING] [system] data-list update failed.

 

and they are still logged. It looks like some relevant harvest objects changed name. How can we fix this? Thanks.

 

Best

Federico

3 REPLIES

Re: Missing data from harvest after Data ONTAP upgrade

Hi @fede_melaccio

 

When Harvest starts it determines the best collection template to use.  So if you update Data ONTAP between major releases [when there are likely template changes] you should restart Harvest so it will start using the new best template.

 

Cheers,

Chris

 

Cheers,
Chris Madden

Storage Architect, NetApp EMEA (and author of Harvest)

Blog: It all begins with data

 

If this post resolved your issue, please help others by selecting ACCEPT AS SOLUTION or adding a KUDO

Re: Missing data from harvest after Data ONTAP upgrade

Hi Chris,

 

thanks for your prompt reply. By "harvest" do you mean the pollers?

 

Cheers

Federico

Re: Missing data from harvest after Data ONTAP upgrade

Hi @fede_melaccio

 

Yes, Harvest is the project name for the poller software.

 

You can restart all pollers using:

 

/opt/netapp-harvest/netapp-manager -restart

Or, just the one cluster that you upgraded if you know the poller name like this:

[root@sdt-poller netapp-harvest]# ./netapp-manager -status
STATUS          POLLER               SITE
############### #################### ##################
[RUNNING]       blob1                nl
[RUNNING]       blob2                nl

[root@sdt-poller netapp-harvest]# ./netapp-manager -restart -poller blob1
STATUS          POLLER               SITE
############### #################### ##################
[STOPPED]       blob1                nl
[STARTED]       blob1                nl

Cheers,
Chris Madden

Storage Architect, NetApp EMEA (and author of Harvest)

Blog: It all begins with data

 

If this post resolved your issue, please help others by selecting ACCEPT AS SOLUTION or adding a KUDO

Forums