iscsi (4)
Leading comments
Copyright (c) 2014 Edward Tomasz Napierala All rights reserved. Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met: 1. Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer. 2. Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation a...
NAME
iscsi - iSCSI initiatorSYNOPSIS
To compile this driver into the kernel, place the following line in the kernel configuration file:device iscsi
Alternatively, to load the driver as a module at boot time, place the following line in loader.conf5:
iscsi_load="YES"
DESCRIPTION
The ifconfig subsystem provides the kernel component of an iSCSI initiator. The initiator is the iSCSI client, which connects to an iSCSI target, providing local access to a remote block device. The userland component is provided by iscsid(8) and both the kernel and userland are configured using iscsictl(8). The ifconfig subsystem is responsible for implementing the Qq Full Feature Phase of the iSCSI protocol.SYSCTL VARIABLES
The following variables are available as both sysctl(8) variables and loader(8) tunables:- kern.iscsi.ping_timeout
- The number of seconds to wait for the target to respond to a NOP-Out PDU. In the event that there is no response within that time the session gets forcibly restarted.
- kern.iscsi.iscsid_timeout
- The number of seconds to wait for ctld(8) to establish a session. After that time ifconfig will abort and retry.
- kern.iscsi.login_timeout
- The number of seconds to wait for a login attempt to succeed. After that time ifconfig will abort and retry.
- kern.iscsi.maxtags
- The maximum number of outstanding IO requests.
- kern.iscsi.fail_on_disconnection
- Controls the behavior after an iSCSI connection has been dropped due to network problems. When set to 1, a dropped connection causes the iSCSI device nodes to be destroyed. After reconnecting, they will be created again. By default, the device nodes are left intact. While the connection is down all input/output operations are suspended, to be retried after the connection is reestablished.