![build iscsi device fromscratch build iscsi device fromscratch](https://i.pinimg.com/originals/a3/62/1a/a3621af5e226151ce427a266e6bf1079.png)
We need the target name(s) for the next part. For example, if my iSCSI target had an address of 192.168.10.10, I would add the following:Ĥ. The defaults should be good for most, if not you can edit them according to your environment.Īdd a line at the bottom with your iSCSI Target device's IP Address. Unload iSCSI, if running (rciscsi stop).ģ. Manually dismount any mounted iscsi targetsĢ. This information is pieced together from the following sources:ġ. ISCSI devices change each time iscsi reconnects Get iSCSI devices to mount at persistent mountpoints on Linux
#Build iscsi device fromscratch install
This is the piece that permits IO through multiple paths over the multiple sessions.ġ) Install dm-multipath tools # apt-get install multipath-toolsĢ) Configure dm-multipath by creating and populating /etc/multipath.This document ( 10097545) is provided subject to the disclaimer at the end of this document. The system is still operable as normal, but you won't yet be taking advantage of the parallel sessions.ĭm-multipath is a utility that can find matching disk UUIDs, build a converged block device that will allow you to take advantage of the multiple sessions. So if you have 2x LUNs on the VPSA, and establish 8x sessions, you will end up with 16 block devices. The additional sessions will generate additional block devices on your system. Unfortunately, in most cases this is not enough by itself.
#Build iscsi device fromscratch update
In this case there are two VPSAs connected, each with 1 session.Ģ) To immediately add an additional session (Does not persist reboot) # iscsiadm -mode session -r -op newģ) To configure the total number of sessions to initiate on reboot # iscsiadm -m node -T -p -op update -n _sessions -v The part of the results is the session ID number.
![build iscsi device fromscratch build iscsi device fromscratch](https://cdn.arstechnica.net/wp-content/uploads/2014/06/freenas_owncloud_stop_and_restart_jail.png)
You should now be able to access the LUN via your favorite partitioning or filesystem formatting utility.ġ) Obtain the current iSCSI sessions # iscsiadm -m session If you stop here, you have successfully configured a single session iSCSI connection to your VPSA. # iscsiadm -m node -T -p -op update -n node.startup -v automaticĩ) If the LUN configuration has been changed in the VPSA GUI after the host has been configured, you may need to "Rescan your LUNs". # iscsiadm -m node -T -p -op update -n -v :3260,1 :vsa-00009628:1Ĩ) Login to the discovered iSCSI target using CHAP # iscsiadm -m node -T -p -op update -n -v CHAP # iscsiadm -m discovery -t sendtargets -p :3260 -I zadara_ InitiatorName=:4aa7d2f25ea5ģ) VPSA GUI: Create the appropriate server record within the VPSA, acquire CHAP credentialsĤ) VPSA GUI: "Attach" the server record to an iSCSI Volumeĥ) Create an iscsiadm "iface" for the VPSA # iscsiadm -m iface -I zadara_ -op newĦ) Map the iSCSI "iface" to the network interface that can reach the VPSA # iscsiadm -m iface -I zadara_ -op update -n _ifacename -v eth0ħ) Discover the VPSA via iSCSI, this will return the VPSA IQN, which is also available in the VPSA GUI. You would still need to perform step 4 and 9.ġ) Install iscsi utilities for iscsiadm # apt-get install open-iscsiĢ) Obtain the host's IQN # cat /etc/iscsi/initiatorname.iscsi ISCSI Install and Configuration from ScratchĪlternatively, the VPSA does offer an automatic configuration script for download.