[SOLVED] iSCSI multipath only sees single path

eroji

Active Member
Mar 26, 2017
7
0
41
41
I am completely new to Proxmox and I tried my best to configure my server on the latest 4.4. My ultimate goal is to configure the host server to use FreeNAS iSCSI zvol targets for storage. I'm using a dual port Intel 10Gb NIC and directly attaching the host server to FreeNAS. However, I am having some problems getting it to work seamlessly.

There are some discrepancies between the howto's I was able to find, as they were meant to be for different (older) versions of Proxmox, so it seems like some of the steps I took were not needed.

What I have done so far:
  • Created bridge adapters for each NIC port 1.1.1.2/1.1.2.2 (FreeNAS side are 1.1.1.1/1.1.2.1)
  • Install open-iscsi, multipath-tools
  • Modified /etc/iscsi/nodes/targets/<ip,port> configs to startup "automatic", but this reverted itself back to "manual"
  • Created /etc/multipath.conf with wwid respective to the volumes
  • Restarted both open-iscsi and multipath-tools services
  • Formatted each volume with ext4
  • Added entries for each volume in /etc/fstab with _netdev option
For some reason, it's not seeing the path on the 1.1.1.1 IP and I can't figure out why. Restarting both services does not help, nor does restarting Proxmox. Plus, it also hangs for 90s as it's starting up on attempting to mount iSCSI device...

multipath.conf
Code:
        polling_interval        2
        path_selector           "round-robin 0"
        path_grouping_policy    multibus
        uid_attribute           ID_SERIAL
        rr_min_io               100
        failback                immediate
        no_path_retry           queue
        user_friendly_names     yes
}
blacklist {
        wwid .*
}
blacklist_exceptions {
        wwid "36589cfc000000f23f05461aad123676c"
        wwid "36589cfc000000792b4741f24309eb62c"
}
multipaths {
  multipath {
        wwid "36589cfc000000f23f05461aad123676c"
        alias data01
  }
  multipath {
        wwid "36589cfc000000792b4741f24309eb62c"
        alias data02
  }
}

multipath -ll
Code:
data01 (36589cfc000000f23f05461aad123676c) dm-6 FreeNAS,SCSI Disk
size=2.0T features='1 queue_if_no_path' hwhandler='0' wp=rw
`-+- policy='round-robin 0' prio=1 status=active
  `- 7:0:0:0 sdc 8:32 active ready running
data02 (36589cfc000000792b4741f24309eb62c) dm-5 FreeNAS,SCSI Disk
size=2.0T features='1 queue_if_no_path' hwhandler='0' wp=rw
`-+- policy='round-robin 0' prio=1 status=active
  `- 6:0:0:0 sdb 8:16 active ready running

iscsiadm -m session -P1
Code:
Target: iqn.2005-10.org.freenas.ctl.data02 (non-flash)
        Current Portal: 1.1.2.1:3260,256
        Persistent Portal: 1.1.2.1:3260,256
                **********
                Interface:
                **********
                Iface Name: default
                Iface Transport: tcp
                Iface Initiatorname: iqn.1993-08.org.debian:01:eee79f92192b
                Iface IPaddress: 1.1.2.2
                Iface HWaddress: <empty>
                Iface Netdev: <empty>
                SID: 1
                iSCSI Connection State: LOGGED IN
                iSCSI Session State: LOGGED_IN
                Internal iscsid Session State: NO CHANGE
Target: iqn.2005-10.org.freenas.ctl.data01 (non-flash)
        Current Portal: 1.1.2.1:3260,256
        Persistent Portal: 1.1.2.1:3260,256
                **********
                Interface:
                **********
                Iface Name: default
                Iface Transport: tcp
                Iface Initiatorname: iqn.1993-08.org.debian:01:eee79f92192b
                Iface IPaddress: 1.1.2.2
                Iface HWaddress: <empty>
                Iface Netdev: <empty>
                SID: 2
                iSCSI Connection State: LOGGED IN
                iSCSI Session State: LOGGED_IN
                Internal iscsid Session State: NO CHANGE
 
Figured out the issue. The open-iscsi path configs needs to be set as "automatic". I recall setting them before, not exactly sure how half of them reverted to manual but stopping the open-iscsi service and setting them again, then starting the service back up made all paths comes up correctly.
 

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!