NFS Protocol Flashcards
NFS protocol
Shares are exported.
Clients must use the mount command to access.
Used for UNIX/LINUX
NFS file access
Enable NFS access for the storage SM
- Verify that NFS protocol is licensed
- Enable the NFS protocol
- Enter the network interface details.
- Create a volume in the storage vm.
Export policy rules - these determine access (either denied or acessible).
File Access Protocol =- any, nfs, nfs3, nfs4
Client identifier = name,location or address by with the client is identified .e.g host name, ip addresss, net group name,
domain
Security type = the authentication type - e.g. krb5, krb5i, krb5p, says and none
Client Identifiers
Host name = e.g. host 1
IP address v4 = 10.1.12.24
IP v4 and subnet = 10.1.12.10/4
IP v4 with subnet mask = 10.1.16.0/255.255.255.0
IP6 address in dotted format = ::1.2.3.4
IP6 with subnet mask as number of bits = ff:00/32
Domain name proceed by the “.” Character = .example.com
A single net group = @netgroup1
Security types
Any = enable access to the volume regardless of the security type
None = enable access to the volume as an anonymous user
Never = do not enable any access
Krb5. = enable Kerberos v5
Krb5i. = enable Kerberos v5 with integrity service
Krb5p = enable Kerberos v5 with integrity service and privacy protection (encryption)
Says = enable AUTH_SYS
Access levels = Read-only, Read/write, superuser
Examples of an export policy rule
-protocol nfs
-client match 10.1.16.0/255.255.255.0
-rorule any
-row rule any
-sueperuser any
Client Identifiers
Type. Defines name services source for this task. Valid source
Host converting host name to IP addresses. Files, dns
Group. Finding user-group information. Files, nis, ldap
Passwd. Finding user information. Files, nis, ldap
Netgroup Finding netgroup information. Files, nis, ldap
Namemap. Mapping user names. Files, ldap
Accessing files from an NFS client
The client will use the mount command.
Show mount -e <ip> to see the available NFS shares on a server</ip>
By default Netapp doesn’t allow for showing.
SMB PROTOCOL
Used by the Microsoft OS
1. Verify that SMB/CIFS is licensed
2. On the storage VM, enable SMB/CIFS functionality
3. Configure the storage VM to enable data access and create a CIFS server
4. Create a volume
5. Map the shared resources from the client.
SMB file access.
- Verify that the SMB/CIFS is licensed; 2. Enable SMB/CIFS; 3 Enter the CIFS server details; Enter the network details.
- Create a volume in the storage VM.
Network File Access (client access)
A client can access a storage VM resource by specifying one of two values: the IP of the LIF or host name
The DNS manages host-to-ip name resolution
If a client access a data LIF on the same node as the volume they have direct access. If the volume is on another node to the data LIF they have indirect access to the volume and the cluster interconnect is used. There should be no impact on performance.
Consider; 1. Number of clients; 2 workload bandwidth requirements; 3. port usage; 4. Port speed
DNS load balancing
Spread Data LIFs across the cluster.
Use DNS load balancing. There are two types
- onbox (zone based) built into ONTAP. ONTAP decides to use the least used data LIF.
- off box (which supports round robin). Based upon the DNS server. The DNS server provides the required paths.