iscsi

By steve, 29 October, 2015

We have some iSCSI setups using a linux pacemaker cluster, and I have always had issues with adding more resources. The setup is as follows:

  • IP Primitive - One for each IP address
  • Target Primitive - One for the system
  • LUN Primitive - One per LUN
  • Device Primitive - One per device (may include a clone primitive)

These are controlled through the following mechanisms:

By steve, 21 October, 2015

Having built a number of iscsi target systems over the years, I have consistently come back to SCST as my preferred implementation. Reasons have varied from IET crashing under load (doe not handle error conditions correctly), LIO crashing in early releases or not supporting naa_id (which is needed for vmware to mount a filesystem if the LUN id changes, or is different for different clusters).

By steve, 17 September, 2015

There are 2 parts to this that I would like to note. First, in order to get drbd, iscsi and multipath to play nicely together under systemd, I had to do the following:
Create /etc/systemd/system/drbd.service.d/override-after.conf with the following contents:

[Unit]
After=systemd-modules-load.service network.target open-iscsi.service dev-mapper-bhqibm01\x2dr6\x2dsata01\x2dlun01.device
Requires=dev-mapper-bhqibm01\x2dr6\x2dsata01\x2dlun01.device

I also had to edite each of the /etc/iscsi/nodes/_iqn_/_ip_/default files and set: