ISCSID(8) BSD System Manager's Manual ISCSID(8)NAME
iscsid -- interface to kernel iSCSI driver
SYNOPSIS
iscsid [-n] [-d lvl]
DESCRIPTION
The iSCSI initiator runs as a kernel driver, and provides access to iSCSI targets running across a network using the iSCSI protocol, RFC
3720. The iscsid utility itself interfaces to the kernel iSCSI driver, and also communicates, using isns(3), with the iSCSI name service
running on other hosts to locate services and iSCSI instances. In normal operation, iscsid is a standard daemon, and will detach from the
controlling terminal using daemon(3) and then loops, reading requests, processing them, and sending responses. Communication takes place
over a Unix domain socket. iscsid exits on receiving a terminate message, (no response to one that is sent to the kernel), or when an error
occurs reading from or writing to the socket.
The -d flag increases the debug level to lvl. Any level above 0 causes iscsid to remain in the foreground, and increases the amount of debug
output. The -n flag makes the daemon single-threaded.
It is envisaged that user-level communication take place with iscsid using the iscsictl(8) utility, rather than directly over its communica-
tion socket. An example of setting up the in-kernel iSCSI initiator is shown in iscsictl(8).
SEE ALSO daemon(3), isns(3), iscsictl(8)HISTORY
The iscsid utility appeared in NetBSD 6.0.
AUTHORS
Alistair Crooks <agc@NetBSD.org> wrote this manual page. The iscsid utility was contributed by Wasabi Systems, Inc.
BSD May 27, 2012 BSD
Check Out this Related Man Page
ISCSID(8) Linux Administrator's Manual ISCSID(8)NAME
iscsid - Open-iSCSI daemon
SYNOPSIS
iscsid [OPTION]
DESCRIPTION
The iscsid implements the control path of iSCSI protocol, plus some management facilities. For example, the daemon could be configured to
automatically re-start discovery at startup, based on the contents of persistent iSCSI database.
OPTIONS
[-c|--config=]config-file
Read configuration from config-file rather than the default /etc/iscsi/iscsid.conf file.
[-i|--initiatorname=]iname-file
Read initiator name from iname-file rather than the default /etc/iscsi/initiatorname.iscsi file.
[-f|--foreground]
run iscsid in the foreground.
[-d|--debug=]debug_level
print debugging information. Valid values for debug_level are 0 to 8.
[-u|--uid=]uid
run under user ID uid (default is the current user ID)
[-g|--gid=]gid
run under user group ID gid (default is the current user group ID).
[-n|--no-pid-file]
do not write a process ID file.
[-p|--pid=]pid-file
write process ID to pid-file rather than the default /var/run/iscsid.pid
[-h|--help]
display this help and exit
[-v|--version]
display version and exit.
FILES
/etc/iscsi/iscsid.conf
The configuration file read by iscsid and iscsiadm on startup.
/etc/iscsi/initiatorname.iscsi
The file containing the iSCSI initiatorname and initiatoralias read by iscsid and iscsiadm on startup.
/etc/iscsi/nodes
Open-iSCSI persistent configuration database
SEE ALSO iscsiadm(8)AUTHORS
Open-iSCSI project <http://www.open-iscsi.org/>
Alex Aizman <itn780@yahoo.com>
Dmitry Yusupov <dmitry_yus@yahoo.com>
July 2005 ISCSID(8)
hi,
I have installed Solaris 10 10/08 on sparc machine. I would like to configure iSCSI on that to mount SAN Volumes. Is there any need to install any additional patches for iSCSI to work.
Thanks,
Prashant. (4 Replies)
System: Sun M3000 and M4000
OS: Solaris 10 (fully up to date with latest patches)
iSCSI HBA: 2x QLE4060C (QLogic)
In each system are 2 QLE4060C iSCSI adapters.
I manage to set up both HBA's to connect to the LUNs on the SAN
However I don't manage to enable multi-pathing.
Made the... (4 Replies)
I am running Solaris 10 on a V490. I have Dell EqualLogic SAN attached.
I would like to take full advantage of the iSCSI initiator.
I have a primary network interface and IP addresses for all four SAN ports. Since the four ports are SUN GigaSwift (legacy), I cannot utilize dladm, so I downloaded... (2 Replies)
I have an Equallogic SAN that I connect to from AIX (as well as Windows)
I had configured the connection and created the volumes and filesystems and all was working great.
Then one day, no communication between the SAN and the AIX (I can ping though) Anything I do on the AIX box at this time... (2 Replies)
Hi,
I have an iSCSI LUN attached to an AIX 5.3 box. It's initial size is 250GB, I just grew it on the SAN to 300GB, but AIX is not seeing the change. Right now I have some processes going and it's eating up the disk space. I need to grow this lun by atleast 30GB otherwise the process with bomb... (5 Replies)
Previous forum threads have noted that AIX cannot use iSCSI disks because it fails when trying to add them to a volume group using mkvg. The failure is caused by AIX's use of the SCSI "WRITE AND VERIFY"(0x2e) command which some iSCSI targets do not support.
We experienced the same problem using... (1 Reply)
Hello Friends,
I am facing issue with the iSCSI configuration on some of our RHEL 5 servers,
When I restart the iSCSI service, it triggers the RHEL server reboot.
Could you please help me with this issue.
Below are the system details :
uname -a :
Linux za-rac-prd-01.abc.local... (2 Replies)
Sorry guys but let me start off by saying I am an AIX noob! I am running AIX 6.1 and recently purchased two iSCSI TOE cards. The plan is to connect these two cards to a Dell EqualLogic SAN and that has two volumes configured for logs and data.
The point of the two cards is to do load balancing... (21 Replies)
I need boot any images from iSCSI and I'd like to boot from linux console of a previous LiveCD booted. Is possible, without gpxe, ipxe firmware or similar? With a simple iSCSI initiator for example? (1 Reply)