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
ISCSI-INITIATOR(8) BSD System Manager's Manual ISCSI-INITIATOR(8)
NAME
iscsi-initiator -- refuse-based iSCSI initiator
SYNOPSIS
iscsi-initiator [-46bcDfVv] [-a authentication-type] [-d digest-type] [-h target-hostname] [-p target-port-number] [-t target-number]
[-u username] mount_point
DESCRIPTION
The iscsi-initiator utility can be used to access an iSCSI target, such as iscsi-target(8), to access block storage which has been exported.
Information pertaining to the target is displayed underneath the mount point, along with the device corresponding to the storage which the
target exports.
The various arguments are as follows:
-4 Use an IPv4 connection to the target.
-6 Use an IPv6 connection to the target.
-a authentication-type
Use the specified authentication type when communicating with the target. The possible values are chap, kerberos, srp or none. The
default value is none.
-b Show the storage as a block device.
-c Show the storage as a character device.
-d digest-type
Use the specified digest type when communicating with the target. The possible values are header, data, both, all or none. The
default value is none.
-D List the LUNs on the specified target and exit (i.e. do discovery only)
-f Show the storage as a regular file.
-h hostname
Connect to the iSCSI target running on the host specified as the argument.
-p port-number
Connect to the iSCSI target running on the port specified as the argument. The default value is 3260.
-t target
Connect to the number of the iSCSI target running as the argument.
-u username
Use the specified user's credentials when logging in to the iSCSI target. There is no default.
-V Print out the version number and then exit.
-v Be verbose in operation.
The refuse(3) library is used to provide the file system features.
The mandatory parameter is the local mount point.
This iSCSI initiator presents a view of the targets underneath the mount point. Firstly, it creates a directory tree with the hostname of
the target, and, in that directory, a virtual directory is created for each target name exported by the iSCSI target program. Within that
virtual target directory, symbolic links exist for the hostname (for convenience), a textual representation of the IP address, the iSCSI tar-
get product name, the iSCSI target IQN, the iSCSI target vendor and version number. One other directory entry is presented in the virtual
target directory, relating to the storage presented by the iSCSI target. This can be in the form of a regular file, which is also the
default, a block device or a character device.
Please note that the iscsi-initiator utility needs the ``puffs'' kernel module loaded via modload(8) to operate.
EXAMPLES
# ./iscsi-initiator -u agc -h iscsi-target0.alistaircrooks.co.uk /mnt
# ls -al /mnt/target0
total 576
drwxr-xr-x 2 agc agc 512 May 11 22:24 .
drwxr-xr-x 2 agc agc 512 May 11 22:24 ..
lrw-r--r-- 1 agc agc 39 May 11 22:24 hostname -> iscsi-target0.alistaircrooks.co.uk
lrw-r--r-- 1 agc agc 14 May 11 22:24 ip -> 172.16.135.130
lrw-r--r-- 1 agc agc 16 May 11 22:24 product -> NetBSD iSCSI
-rw-r--r-- 1 agc agc 104857600 May 11 22:24 storage
lrw-r--r-- 1 agc agc 43 May 11 22:24 targetname -> iqn.1994-04.org.netbsd.iscsi-target:target0
lrw-r--r-- 1 agc agc 8 May 11 22:24 vendor -> NetBSD
lrw-r--r-- 1 agc agc 4 May 11 22:24 version -> 0
#
SEE ALSO
puffs(3), refuse(3), iscsi-target(8)
HISTORY
The iscsi-initiator utility first appeared in NetBSD 6.0. An earlier version called iscsifs was available in NetBSD 5.0 in source format
only.
AUTHORS
The iscsi-initiator utility was written by Alistair Crooks <agc@NetBSD.org>.
BUGS
iscsi-initiator currently only supports a CHAP challenge length of 16 octets. Other initiators support up to 1024 and thus it is expected
that most targets will also support such lengths. This means that CHAP compatibility with other targets apart from iscsi-target(8) is likely
to be poor. To workaround this, please use authentication type none by not specifying a username with the -u option.
BSD
February 22, 2011 BSD