The name of the IPspace.

The name must be unique in the cluster.

The IPspace to which the broadcast domain is assigned.

The IPspace must exist.

The name of the broadcast domain.

This name must be unique in the IPspace.

The MTU of the broadcast domain.

Commonly set to either 1500 or 9000.

The MTU value is applied to all ports in the broadcast domain and to any ports that are later added to the broadcast domain.

The network ports to add to the broadcast domain.

The ports assigned to the broadcast domain can be physical ports, VLANs, or interface groups (ifgroups).

If a port is in another broadcast domain, it must be removed before it can be added to the broadcast domain.

Ports are assigned by specifying both the node name and port: for example, node1:e0d.

The IPspace to which the subnet will be assigned.

The IPspace must exist.

The name of the subnet.

The name must be unique in the IPspace.

The broadcast domain to which the subnet will be assigned.

The broadcast domain must reside in the specified IPspace.

The subnet and mask in which the IP addresses reside.

You can specify a default gateway for the subnet.

If you do not assign a gateway when you create the subnet, you can assign one to the subnet at any time.

You can specify a range of IP addresses or specific IP addresses.
For example, you can specify a range such as:
192.168.1.1-192.168.1.100, 192.168.1.112, 192.168.1.145

If you do not specify an IP address range, the entire range of IP addresses in the specified subnet are available to assign to LIFs.

Specifies whether to force the update of existing LIF associations.

By default, subnet creation fails if any service processor interfaces or network interfaces are using the IP addresses in the ranges provided.

Using this parameter associates any manually addressed interfaces with the subnet and allows the command to succeed.

The name of the SVM.

You should use a fully qualified domain name (FQDN) to ensure unique SVM names across cluster leagues.

The name of the SVM root volume.

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

This aggregate must exist.

The security style for the SVM root volume.

Possible values are ntfs, unix, and mixed.

The IPspace to which the SVM is assigned.

This IPspace must exist.

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.

The name of the SVM for the LIF.

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.

The role of the LIF.

Data LIFs are assigned the data role.

The protocols that can use the LIF.

By default, SMB, NFS, and FlexCache are allowed.

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.

The port to which the logical interface returns when the LIF is reverted to its home port.

You should record a home port for each data LIF.

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.

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

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.

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.

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

Specifies whether to use DDNS.

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

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.

The FQDN of the DNS domain.

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