ctl.conf5

Create an auth-group configuration context, defining a new auth-group, which can then be assigned to any number of targets.

The debug verbosity level. The default is 0.

The limit for concurrently running child processes handling incoming connections. The default is 30. A setting of 0 disables the limit.

The path to the pidfile. The default is /var/run/ctld.pid.

Create a portal-group configuration context, defining a new portal-group, which can then be assigned to any number of targets.

Create a transport-group configuration context, defining a new transport-group, which can then be assigned to any number of NVMeoF controllers.

Create a lun configuration context, defining a LUN to be exported by any number of targets or controllers.

Create a target configuration context, which can optionally contain one or more lun contexts.

Create a controller configuration context, which can optionally contain one or more namespace contexts.

The timeout for login sessions, after which the connection will be forcibly terminated. The default is 60. A setting of 0 disables the timeout.

An IPv4 or IPv6 address and optionally port of iSNS server to register on.

iSNS registration period. Registered Network Entity not updated during this period will be unregistered. The default is 900.

Timeout for iSNS requests. The default is 5.

Sets the authentication type. Type can be either "none", "deny", "chap", or "chap-mutual". In most cases it is not necessary to set the type using this clause; it is usually used to disable authentication for a given auth-group.

A set of CHAP authentication credentials. Note that for any auth-group, the configuration may only contain either chap or chap-mutual entries; it is an error to mix them.

A set of mutual CHAP authentication credentials. Note that for any auth-group, the configuration may only contain either chap or chap-mutual entries; it is an error to mix them.

An NVMeoF host address: an IPv4 or IPv6 address, optionally followed by a literal slash and a prefix length. Only NVMeoF hosts with an address matching one of the defined addresses will be allowed to connect. If not defined, there will be no restrictions based on host address.

An NVMeoF host name. Only NVMeoF hosts with a name matching one of the defined names will be allowed to connect. If not defined, there will be no restrictions based on NVMe host name.

An iSCSI initiator name. Only initiators with a name matching one of the defined names will be allowed to connect. If not defined, there will be no restrictions based on initiator name.

An iSCSI initiator portal: an IPv4 or IPv6 address, optionally followed by a literal slash and a prefix length. Only initiators with an address matching one of the defined addresses will be allowed to connect. If not defined, there will be no restrictions based on initiator address.

Assign a previously defined authentication group to the portal group, to be used for target discovery. By default, portal groups are assigned predefined auth-group "default", which denies discovery. Another predefined auth-group, "no-authentication", may be used to permit discovery without authentication.

Determines which targets are returned during discovery. Filter can be either "none", "portal", "portal-name", or "portal-name-auth". When set to "none", discovery will return all targets assigned to that portal group. When set to "portal", discovery will not return targets that cannot be accessed by the initiator because of their initiator-portal. When set to "portal-name", the check will include both initiator-portal and initiator-name. When set to "portal-name-auth", the check will include initiator-portal, initiator-name, and authentication credentials. The target is returned if it does not require CHAP authentication, or if the CHAP user and secret used during discovery match those used by the target. Note that when using "portal-name-auth", targets that require CHAP authentication will only be returned if discovery-auth-group requires CHAP. The default is "none".

An IPv4 or IPv6 address and port to listen on for incoming connections.

Define iSCSI hardware offload driver to use for this portal-group. The default is "none".

The CTL-specific port options passed to the kernel.

IPv4 or IPv6 address to redirect initiators to. When configured, all initiators attempting to connect to portal belonging to this portal-group will get redirected using "Target moved temporarily" login response. Redirection happens before authentication and any initiator-name or initiator-portal checks are skipped.

Unique 16-bit tag value of this portal-group. If not specified, the value is generated automatically.

Specifies that this portal-group is listened by some other host. This host will announce it on discovery stage, but won't listen.

The DiffServ Codepoint used for sending data. The DSCP can be set to numeric, or hexadecimal values directly, as well as the well-defined "CSx" and "AFxx" codepoints.

The 802.1Q Priority CodePoint used for sending packets. The PCP can be set to a value in the range between "0" to "7". When omitted, the default for the outgoing interface is used.

See the description for this option for portal-group contexts.

Filter can be either "none", "address", or "address-name". When set to "none", discovery will return all controllers assigned to that transport group. When set to "address", discovery will not return controllers that cannot be accessed by the host because of their host-address. When set to "address-name", the check will include both host-address and host-nqn. The default is "none".

An IPv4 or IPv6 address and port to listen on for incoming connections using the specified NVMeoF transport. Supported transports are "tcp" (for NVMe/TCP I/O controllers) and "discovery-tcp" (for NVMe/TCP discovery controllers).

One of the following options:

Unique 16-bit port ID for this transport-group. If not specified, the value is generated automatically.

See the description for this option for portal-group contexts.

See the description for this option for portal-group contexts.

Assign a human-readable description to the target. There is no default.

Assign a previously defined authentication group to the target. By default, targets that do not specify their own auth settings, using clauses such as chap or initiator-name, are assigned predefined auth-group "default", which denies all access. Another predefined auth-group, "no-authentication", may be used to permit access without authentication. Note that this clause can be overridden using the second argument to a portal-group clause.

Sets the authentication type. Type can be either "none", "deny", "chap", or "chap-mutual". In most cases it is not necessary to set the type using this clause; it is usually used to disable authentication for a given target. This clause is mutually exclusive with auth-group; one cannot use both in a single target.

A set of CHAP authentication credentials. Note that targets must only use one of auth-group, chap, or chap-mutual; it is a configuration error to mix multiple types in one target.

A set of mutual CHAP authentication credentials. Note that targets must only use one of auth-group, chap, or chap-mutual; it is a configuration error to mix multiple types in one target.

An iSCSI initiator name. Only initiators with a name matching one of the defined names will be allowed to connect. If not defined, there will be no restrictions based on initiator name. This clause is mutually exclusive with auth-group; one cannot use both in a single target.

An iSCSI initiator portal: an IPv4 or IPv6 address, optionally followed by a literal slash and a prefix length. Only initiators with an address matching one of the defined addresses will be allowed to connect. If not defined, there will be no restrictions based on initiator address. This clause is mutually exclusive with auth-group; one cannot use both in a single target.

The auth-type, chap, chap-mutual, initiator-name, and initiator-portal clauses in the target context provide an alternative to assigning an auth-group defined separately, useful in the common case of authentication settings specific to a single target.

Assign a previously defined portal group to the target. The default portal group is "default", which makes the target available on TCP port 3260 on all configured IPv4 and IPv6 addresses. Optional second argument specifies auth-group for connections to this specific portal group. If second argument is not specified, target auth-group is used.

Assign specified CTL port (such as "isp0" or "isp2/1") to the target. This is used to export the target through a specific physical - eg Fibre Channel - port, in addition to portal-groups configured for the target. Use ctladm portlist command to retrieve the list of available ports. On startup ctld(8) configures LUN mapping and enables all assigned ports. Each port can be assigned to only one target.

IPv4 or IPv6 address to redirect initiators to. When configured, all initiators attempting to connect to this target will get redirected using "Target moved temporarily" login response. Redirection happens after successful authentication.

Export previously defined lun by the parent target.

Create a lun configuration context, defining a LUN exported by the parent target.

This is an alternative to defining the LUN separately, useful in the common case of a LUN being exported by a single target.

Assign a previously defined authentication group to the controller. By default, controllers that do not specify their own auth settings, using clauses such as host-address or host-nqn, are assigned to the predefined auth-group "default", which denies all access. Another predefined auth-group, "no-authentication", may be used to permit access without authentication. Note that this clause can be overridden using the second argument to a transport-group clause.

Sets the authentication type. Type can be either "none" or "deny". In most cases it is not necessary to set the type using this clause; it is usually used to disable authentication for a given controller. This clause is mutually exclusive with auth-group; one cannot use both in a single controller.

An NVMeoF host address: an IPv4 or IPv6 address, optionally followed by a literal slash and a prefix length. Only NVMeoF hosts with an address matching one of the defined addresses will be allowed to connect. If not defined, there will be no restrictions based on host address. This clause is mutually exclusive with auth-group; one cannot use both in a single controller.

An NVMeoF host name. Only NVMeoF hosts with a name matching one of the defined names will be allowed to connect. If not defined, there will be no restrictions based on NVMe host name. This clause is mutually exclusive with auth-group; one cannot use both in a single target.

The auth-type, host-address, and host-nqn clauses in the controller context provide an alternative to assigning an auth-group defined separately, useful in the common case of authentication settings specific to a single controller.

Assign a previously defined transport group to the controller. The default transport group is "default", which makes the controller available on TCP port 4420 on all configured IPv4 and IPv6 addresses. The optional second argument specifies the auth-group for connections to this specific transport group group. If the second argument is not specified, the controller auth-group is used.

Export previously defined lun as an NVMe namespace from the parent controller.

Create a namespace configuration context, defining an NVMe namespace exported by the parent target.

This is an alternative to defining the namespace separately, useful in the common case of a namespace being exported by a single controller. namespace configuration contexts accept the the same properties as lun contexts.

The CTL backend to use for a given LUN. Valid choices are "block" and "ramdisk"; block is used for LUNs backed by files or disk device nodes; ramdisk is a bitsink device, used mostly for testing. The default backend is block.

The blocksize visible to the initiator. The default blocksize is 512 for disks, and 2048 for CD/DVDs.

Global numeric identifier to use for a given LUN inside CTL. By default CTL allocates those IDs dynamically, but explicit specification may be needed for consistency in HA configurations.

The SCSI Device Identification string presented to iSCSI initiators.

Specify the SCSI device type to use when creating the LUN. Currently CTL supports Direct Access (type 0), Processor (type 3) and CD/DVD (type 5) LUNs.

The CTL-specific options passed to the kernel. All CTL-specific options are documented in the OPTIONS section of ctladm(8).

The path to the file, device node, or zfs(8) volume used to back the LUN. For optimal performance, create ZFS volumes with the "volmode=dev" property set.

The SCSI serial number presented to iSCSI initiators.

The LUN size, in bytes or by number with a suffix of K, M, G, T (for kilobytes, megabytes, gigabytes, or terabytes). When the configuration is in UCL format, use the suffix format kKmMgG|bB, (i.e., 4GB, 4gb, and 4Gb are all equivalent).