IPspace name
The unique identifier of the IPspace.

Yes

SVM name
The fully qualified domain name (FQDN) of the SVM.

This name must be unique across cluster leagues.

Yes

Root volume name
The name of the SVM root volume.

Yes

Aggregate name
The name of the aggregate that holds the SVM root volume.

This aggregate must exist.

Yes

Security style
The security style for the SVM root volume.

Possible values are ntfs, unix, and mixed.

Yes

IPspace name
The IPspace to which the SVM is assigned.

This IPspace must exist.

No

SVM language setting
The default language to use for the SVM and its volumes.

If you do not specify a default language, the default SVM language is set to C.UTF-8.

The SVM language setting determines the character set used to display file names and data for all NAS volumes in the SVM.

You can modify The language after the SVM is created.

No

SVM name
The name of the SVM for the LIF.

Yes

LIF name
The name of the LIF.

You can assign multiple data LIFs per node, and you can assign LIFs to any node in the cluster, provided that the node has available data ports.

To provide redundancy, you should create at least two data LIFs for each data subnet, and the LIFs assigned to a particular subnet should be assigned home ports on different nodes.

Important: If you are configuring a SMB server to host Hyper-V or SQL Server over SMB for nondisruptive operation solutions, the SVM must have at least one data LIF on every node in the cluster.

Yes

Service policy
Service policy for the LIF.

The service policy defines which network services can use the LIF. Built-in services and service policies are available for managing data and management traffic on both data and system SVMs.

Yes

Allowed protocols
IP-based LIFs do not require allowed protocols, use the service policy row instead.

Specify allowed protocols for SAN LIFs on FibreChannel ports. These are the protocols that can use that LIF. The protocols that use the LIF cannot be modified after the LIF is created. You should specify all protocols when you configure the LIF.

No

Home node
The node to which the LIF returns when the LIF is reverted to its home port.

You should record a home node for each data LIF.

Yes

Home port or broadcast domain
Chose one of the following:

Port: Specify the port to which the logical interface returns when the LIF is reverted to its home port. This is only done for the first LIF in the subnet of an IPspace, otherwise it is not required.

Broadcast Domain: Specify the broadcast domain, and the system will select the appropriate port to which the logical interface returns when the LIF is reverted to its home port.

Yes

Subnet name
The subnet to assign to the SVM.

All data LIFs used to create continuously available SMB connections to application servers must be on the same subnet.

Yes (if using a subnet)

SVM name
The name of the SVM on which you want to create an NFS or SMB server.

Yes

DNS domain name
A list of domain names to append to a host name when performing host- to-IP name resolution.

List the local domain first, followed by the domain names for which DNS queries are most often made.

Yes

IP addresses of the DNS servers
List of IP addresses for the DNS servers that will provide name resolution for the NFS or SMB server.

The listed DNS servers must contain the service location records (SRV) needed to locate the Active Directory LDAP servers and domain controllers for the domain that the SMB server will join.

The SRV record is used to map the name of a service to the DNS computer name of a server that offers that service. SMB server creation fails if ONTAP cannot obtain the service location records through local DNS queries.

The simplest way to ensure that ONTAP can locate the Active Directory SRV records is to configure Active Directory-integrated DNS servers as the SVM DNS servers.

You can use non-Active Directory-integrated DNS servers provided that the DNS administrator has manually added the SRV records to the DNS zone that contains information about the Active Directory domain controllers.

For information about the Active Directory-integrated SRV records, see the topic How DNS Support for Active Directory Works on Microsoft TechNet.

Yes

SVM name
The SVM on which you want to create an NFS or SMB server.

Yes

Whether to use DDNS
Specifies whether to use DDNS.

The DNS servers configured on the SVM must support DDNS. By default, DDNS is disabled.

Yes

Whether to use secure DDNS
Secure DDNS is supported only with Active Directory-integrated DNS.

If your Active Directory-integrated DNS allows only secure DDNS updates, the value for this parameter must be true.

By default, secure DDNS is disabled.

Secure DDNS can be enabled only after a SMB server or an Active Directory account has been created for the SVM.

No

FQDN of the DNS domain
The FQDN of the DNS domain.

You must use the same domain name configured for DNS name services on the SVM.

No