Networking and Client Access (NFS, SMB, SAN)
This domain tests LIF design, physical port configuration, and client protocol access for NFS, SMB, and SAN.
LIFs and physical networking
Data LIFs serve client traffic; management LIFs serve administration; cluster LIFs carry intra-cluster traffic; intercluster LIFs carry SnapMirror traffic. Broadcast domains group ports and VLANs. Interface groups provide link aggregation, and failover groups define which ports a LIF can move to. LIFs fail over within their assigned policies, so a data LIF should not be restricted to a single port unless intended.
Protocol access
NFS access is controlled by export policies with rules matching clients and access levels. NFSv4 uses a pseudo-filesystem rooted at the SVM namespace. SMB requires a CIFS server joined to Active Directory, shares, and share or NTFS permissions. SAN access depends on correct zoning, initiator grouping, and LUN mapping. NVMe/TCP and iSCSI use similar host-side access control but different initiator configuration.
Worked example
An NFS client on 10.0.0.50 cannot mount /vol1. Check that the volume is junctioned, that a data LIF is reachable, and that the export policy has a rule allowing 10.0.0.50/32 or its subnet with rw. A missing export rule or an unjunctioned volume produces the same mount failure, so verify both.
Traps
Putting data LIFs in a management-only broadcast domain; forgetting that export policy rules are evaluated by client match; mixing SAN and NAS LIF roles; and changing failover groups without checking LIF mobility.