vFilers should be discovered as of VSC 2.0 and Ontap 126.96.36.199 - so I'll need to troubleshoot why they are not in my case
MultiStore vFiler unit support
Does VSC support MultiStore vFiler units?
Yes, vFilers are now supported as of VSC 2.0.
vFilers are discovered in the same manner as physical controllers.
vFilers have the same ONTAP version restrictions as physical controllers.
All vFiler hostnames will be pre-pended with "MultiStore:" in the hostname of the Overview panel.
VSC only communicates with the vFiler. VSC cannot determine the physical controller (aka vFiler0).
vFiler storage totals will be calculated by adding up all the available storage owned by the vFiler. vFilers don't have a concept of disks like physical controllers do. The Total Capacity and Total Allocated columns will be the same.
What version of Data ONTAP is required for vFiler support?
Data ONTAP 188.8.131.52+ is required for VSC to discover vFilers. Please see the NetApp Interoperability matrix for specific support configurations.
What VSC features are not available on a MultiStore vFiler unit?
vFilers do not support SSL.
Supported protocols column – The column displays the license protocols allowed by the controller. As mentioned above, VSC only talks to the actual vFiler. When a controller is a vFiler unit, the "supported protocols" column will be presented as the protocols "in-use". For instance, if an NFS export is found by VSC, NFS will be listed. If an iSCSI LUN is discovered as well, both NFS and iSCSI will be listed.
Overall Status column – This column displays the operational state of the controller. If VSC is communicating with the vFiler, it's in the "running" state. To be consistent with physical controllers, a state of "running" will be presented as "Normal". vFilers in any of the other 4 states (these are non-operational states) will not be discoverable by VSC.
Overall Status Reason – This column displays the details status returned by the controller. vFilers do not return a status reason, so the following string will be printed for the status reason: "This controller is a MultiStore vFiler unit."
The following columns are not applicable for vFilers. These will be left blank.
Yes, httpd must be enabled. I was just responding to the question about ssl. Some of the limitations make sense since the vfiler can't do things like resize a volume. I run central vfilers dedicated to vmdk exports and separate vfilers for each customer's data access (luns and shares.) The esxi hosts and vcenter can't reach the customer vfilers so they can't and shouldn't manage that storage.