10 More Discussions You Might Find Interesting
1. HP-UX
Is there one? If so where can it be found? I have the 10.20 CD set but I don't think that there's an iSCSI initiator on there.
Thank you
Dave (0 Replies)
Discussion started by: perdrix
0 Replies
2. Red Hat
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)
Discussion started by: Jeevanm
2 Replies
3. Linux
I am using Windows Server 2008R2 as a domain controller to 2 other servers and would like to use my Dell Powervault 770N as my NAS for data storage. I have FC that I would like to implement between the servers and the NAS (as an iSCSI target). I am brand new to this world; is this possible? I am... (2 Replies)
Discussion started by: NoviceAdmin
2 Replies
4. UNIX for Dummies Questions & Answers
Hi,
I want to set up a iscsi high availability with sheepdog distributed storage.
Here is my system set up. Four nodes with sheepdog distributed storage and i am sharing this storage through iscsi using two nodes as well as using a virtual ip set up using ucarp.Two nodes using same iqn. And... (0 Replies)
Discussion started by: jobycxa
0 Replies
5. Solaris
I have a Sun Blade 2500 with SUN 5.9 OS installed.
I have configured ISCSI SAN and one of my Red Hat OS can accessed/mount the ISCSI SAN disk
Now i want to access/mount another ISCSI SAN disk on SUN solaris. Is that possible ?
Thanks (1 Reply)
Discussion started by: z_haseeb
1 Replies
6. AIX
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)
Discussion started by: oldmanjoe
2 Replies
7. Solaris
Hi all
iscsiadm / iscsitadm.
Ive created two devices on a host.
# iscsitadm list target
Target: 1-disk0
iSCSI Name: iqn.1986-03.com.sun:02:f105ddf3-52a4-ed7a-9590-c3d354b8fc32.1-disk0
Connections: 1
Target: 1-disk1
iSCSI Name:... (0 Replies)
Discussion started by: sbk1972
0 Replies
8. Filesystems, Disks and Memory
I am trying to set up iscsi linux clients and am having some problems. iscsid is running, I can do discovery fine, but adding the iscsi lun I get the following error: iscsiadm -m node -T iqn.xxxxxxxxxxxxxx -p y.y.y.y:3260 -l Logging in to iscsid: session already running. iscsiadm: Could not... (0 Replies)
Discussion started by: humbletech99
0 Replies
9. OS X (Apple)
I have configured iSCSI on server with linux running on it .
On APPLE I have downloaded gloablSAN. When globalSAN is started ,it asks for target IP . I have given target IP . It has detected the disks .
But when i use "disk utilities " , here the ISCSI disk are not displayed. except the... (0 Replies)
Discussion started by: pradeepreddy
0 Replies
10. AIX
I just reloaded an IBM P-Series with AIX 5.3 and would like to configure iscsi, can someone point me in the right direction to obtaining the initiator node name?
I ran lsattr -El iscsi0 - but the name that is displayed is not the correct name. I read somewhere the default node name is not... (2 Replies)
Discussion started by: bbbngowc
2 Replies
ISCONTROL(8) BSD System Manager's Manual ISCONTROL(8)
NAME
iscontrol -- login/negotiator/control for an iSCSI initiator session
SYNOPSIS
iscontrol [-dv] [-c file [-n nickname]] [-p pidfile] [-t target] [variable=value]
DESCRIPTION
This command, along with its kernel counterpart iscsi_initiator(4), is obsolete. Users are advised to use iscsictl(8) instead.
Internet SCSI (iSCSI) is a network protocol standard, that allows the use of the SCSI protocol over TCP/IP networks, the iscontrol program is
the userland side of an iSCSI session, see iscsi_initiator(4). It has 2 modes of operation, if -d (discovery session) is specified, it will
print out the target names returned by the target and exit. In the second mode, it will, after a successful login/negotiation, run in daemon
mode, monitoring the connection, and will try to reconnect in case of a network/target failure. It will terminate/logout the session when a
SIGHUP signal is received. The flags are as follows:
-c file a file containing configuration key-options, see iscsi.conf(5).
-d do a discovery session and exit.
-n nickname if -c file is specified, then search for the block named nickname in that file, see iscsi.conf(5).
-p pidfile will write the process ID of the session to the specified pidfile
-t target the target's IP address or name.
-v verbose mode.
variable=value see iscsi.conf(5) for the complete list of variables/options and their possible values.
EXAMPLES
iscontrol -dt myiscsitarget
will start a discovery session with the target and print to stdout the list of available targetnames/targetadresses. Note: this listing does
not necessarily mean availability, since depending on the target configuration, a discovery session might not need login/access permission,
but a full session certainly does.
iscontrol -c /etc/iscsi.conf -n myiscsi
will read options from /etc/iscsi.conf, use the targetaddress found in the block nicknamed myiscsi, login and negotiate whatever options are
specified, and start an iscsi-session.
SEE ALSO
da(4), iscsi_initiator(4), sa(4), iscsi.conf(5), camcontrol(8), iscsictl(8)
STANDARDS
RFC 3720
BUGS
iscontrol should probably load the iscsi_initiator module if needed.
Not all functions/specifications have been implemented yet, noticeably missing are the Task Management Functions. The error recovery, though
not fully compliant does a brave effort to recover from network disconnects.
BSD
October 9, 2014 BSD