Just wondering what’s the criteria for dfm to determine the value of <host-perf-status> :
Also want to know the criteria about <host-communication-status>.
If the host-perf-status is 'Unknown', object must have been recently added and hence performance data has not been collected yet.
The OnCommand Unified Manager API Documentation gives the following information:
host-perf-status : Current status of the host based on performance events
Possible status values:
Whether we are able to establish a connection to validate the host credentials. Valid only for storage systems and Host Agents. Possible values: "unknown", "up", or "down".
Thanks for your reply.
As for <host-perf-status>, actually I found a page on NetApp internal site, giving same explanation as what you refer here. However, only "Current status of the host based on performance events" is really too abstract to understand.
Could you please detail that, or with an example ?
As for <host-communication-status>, you say "only for storage systems and Host Agents", can I understand vFiler is not included ? Or, <host-communication-status> for a vFiler would be shown as "unknown" ?
DFM host can be a storage system, a vFiler unit, a switch, or an agent. Hence, <host-communication-status> can include any of these.
Since the API is based on NDMP communication I feel <host-perf-status> indicates whether DFM is able to collect performance data from the host or not.
As I said earlier, if the <host-perf-status> is 'Unknown', the host must have been recently added and hence performance data has not been collected from the host yet.
Hope this helps.
As for <host-communication-status>, in one of our customers' environment, all vFilers show as unknown, compared with normal for physical Filers. So it's not a coincidence, right ?
From the image I can see the communication status is unknown for vfilers because DFM is unable to contact the vfiler.
It might be because NDMP/ vfiler monitoring is not configured, although I am not too sure.
> It might be because NDMP/ vfiler monitoring is not configured,
I think we have different tag ndmp-communication-status to define status of ndmp communication status, different than ost-communication-status