-vserver

A name you supply for the new SVM that is either a fully qualified domain name (FQDN) or follows another convention that enforces unique SVM names across a cluster.

-aggregate

The name of an aggregate in the cluster with sufficient space for new NFS storage capacity.

-rootvolume

A unique name you supply for the SVM root volume.

-rootvolume-security-style

Use the UNIX security style for the SVM.

unix

-language

Use the default language setting in this workflow.

C.UTF-8

ipspace

IPspaces are distinct IP address spaces in which (storage virtual machines (SVMs)) reside.

-v3, -v4.0, -v4.1, -v4.1-pnfs

Enable NFS versions as needed.

-v4-id-domain

ID mapping domain name.

-v4-numeric-ids

Support for numeric owner IDs (enabled or disabled).

-vserver

The vserver in which the logical interface exists.

-lif

The name of the logical interface on which you want to enable encryption in transit using NFS over TLS.

-certificate-name

The name of the X.509 certificate configured within the storage VM.

-lif

A name you supply for the new LIF.

-role

Use the data LIF role in this workflow.

data

-data-protocol

Use only the NFS protocol in this workflow.

nfs

-home-node

The node to which the LIF returns when the network interface revert command is run on the LIF.

-home-port

The port or interface group to which the LIF returns when the network interface revert command is run on the LIF.

-address

The IPv4 or IPv6 address on the cluster that will be used for data access by the new LIF.

-netmask

The network mask and gateway for the LIF.

-subnet

A pool of IP addresses. Used instead of -address and -netmask to assign addresses and netmasks automatically.

-firewall-policy

Use the default data firewall policy in this workflow.

data

-domains

Up to five DNS domain names.

-name-servers

Up to three IP addresses for each DNS name server.

Example

johnm

123

100

John Miller

1

2

3

…​

n

Example

Engineering

100

1

2

3

…​

n

-domain

The NIS domain that the SVM will use for name lookups.

-active

The active NIS domain server.

true or false

-nis-servers

A comma-separated list of IP addresses and hostnames for the NIS servers used by the domain configuration.

-vserver

The name of the SVM for which you want to create an LDAP client configuration.

-client-config

The name you assign for the new LDAP client configuration.

-query-timeout

Use the default 3 seconds for this workflow.

3

-min-bind-level

The minimum bind authentication level. The default is anonymous. Must be set to sasl if signing and sealing is configured.

-preferred-ad-servers

One or more preferred Active Directory servers by IP address in a comma-delimited list.

-ad-domain

The Active Directory domain.

-schema

The schema template to use. You can use a default or custom schema.

-port

Use the default LDAP server port 389 for this workflow.

389

-bind-dn

The Bind user distinguished name.

-base-dn

The base distinguished name. The default is "" (root).

-base-scope

Use the default base search scope subnet for this workflow.

subnet

-session-security

Enables LDAP signing or signing and sealing. The default is none.

-use-start-tls

Enables LDAP over TLS. The default is false.

-vserver

The SVM that will communicate with the KDC.

-realm

The Kerberos realm.

-clock-skew

Permitted clock skew between clients and servers.

-kdc-ip

KDC IP address.

-kdc-port

KDC port number.

-adserver-name

Microsoft KDC only: AD server name.

-adserver-ip

Microsoft KDC only: AD server IP address.

-adminserver-ip

UNIX KDC only: Admin server IP address.

-adminserver-port

UNIX KDC only: Admin server port number.

-passwordserver-ip

UNIX KDC only: Password server IP address.

-passwordserver-port

UNIX KDC only: Password server port.

-kdc-vendor

KDC vendor.

{ Microsoft | Other }

-comment

Any desired comments.

-vserver

The name of the SVM for which you want to create a Kerberos configuration.

-lif

The data LIF on which you will enable Kerberos. You can enable Kerberos on multiple LIFs.

-spn

The Service Principle Name (SPN)

-permitted-enc-types

The permitted encryption types for Kerberos over NFS; aes-256 is recommended, depending on client capabilities.

-admin-username

The KDC administrator credentials to retrieve the SPN secret key directly from the KDC. A password is required

-keytab-uri

The keytab file from the KDC containing the SPN key if you do not have KDC administrator credentials.

-ou

The organizational unit (OU) under which the Microsoft Active Directory server account will be created when you enable Kerberos using a realm for Microsoft KDC.

-vserver

The name of the SVM that will host the new volume.

-policyname

A name you supply for a new export policy.

-clientmatch

Client match specification.

-ruleindex

Position of export rule in the list of rules.

-protocol

Use NFS in this workflow.

nfs

-rorule

Authentication method for read-only access.

-rwrule

Authentication method for read-write access.

-superuser

Authentication method for superuser access.

-anon

User ID to which anonymous users are mapped.

Examples

0.0.0.0/0,@rootaccess_netgroup

any

krb5

sys

65534

1

2

3

…​

n

-vserver

The name of a new or existing SVM that will host the new volume.

-volume

A unique descriptive name you supply for the new volume.

-aggregate

The name of an aggregate in the cluster with sufficient space for the new NFS volume.

-size

An integer you supply for the size of the new volume.

-user

Name or ID of the user that is set as the owner of the volume’s root.

-group

Name or ID of the group that is set as the owner of the volume’s root.

--security-style

Use the UNIX security style for this workflow.

unix

-junction-path

Location under root (/) where the new volume is to be mounted.

-export-policy

If you are planning to use an existing export policy, you can enter its name when you create the volume.