I'm curious if there's an intentional difference in behavior between the NDK (say as used via ZExplore) and the Web Services (SOAP-base) API with respect to the service-status element/object returned from the host-list-into-iter-* calls to the DFM?
When using the NDK-based calls I get a list of service-statuses that contain both the service and it's status:
<service-statuses>
<service-status>
<service>nfs</service>
<status>up</status>
</service-status>
<service-status>
<service>cifs</service>
<status>up</status>
</service-status>
<service-status>
<service>iscsi</service>
<status>up</status>
</service-status>
</service-statuses>
However when using the Web Services calls I get back what is equivalent to:
<service-statuses>
<service-status>
<service>nfs</service>
</service-status>
<service-status>
<service>cifs</service>
</service-status>
<service-status>
<service>iscsi</service>
</service-status>
</service-statuses>
Note there is no indication of status. This is despite the documentation implying otherwise:
It looks like one needs to to use the vfiler-allowed-protocols array to know what the service status is for vFiler at least. It appears to match what is "up" for a vFiler using the NDK-based data.
Any thoughts or clarification would be appreciated.
Thanks.
