For those of us who have been around long enough multipathing in VMware environments has just been a thing that has worked. FC or iSCSI you knew what you had to do. iSCSI needs port binding and multiple initiator IPs. FC needs multiple HBAs and paths. It just became a way of life to configure things correctly. I noticed when I was adding some iSCSI storage to Proxmox even with dm-multipath installed there was only one path. What gives? Well the default iSCSI storage configuration in Proxmox is just like ESXi is without port binding. It uses whatever interface is either on the subnet with your target or uses the interface with a route to the target. But there is no way to configure multiple sources or physical interface binding. I showed the NVMe configuration in one of my previous posts. Go check it out and see all the things you need to do. I didn’t write the same guide for iSCSI yet but you get the idea.
So what? Well I don’t like doing things manually. So I wrote a couple of storage plugins to handle this for you. Either from the CLI or if you are brave a hacky GUI.
iSCSI: https://github.com/PureStorage-OpenConnect/proxmox-iscsi-multipath-plugin
NVMe-tcp: https://github.com/PureStorage-OpenConnect/proxmox-nvme-tcp-multipath-plugin
The readme explains them both but the main point is you configure your IP interfaces on the hosts using the same names on each host. Then add the storage using the interface names and the plugins will detect the IPs on the interfaces and connect to the storage via those interfaces. There is a GUI install and it add the options to the add storage menu. The GUI will likely not persist through a host upgrade as it’s a completely unsupported hacky integration. The CLI should be fine. Give them a shot and let me know what you think. The usual use at your own risk applies.
Pairing these with the multipath display plugin (https://github.com/PureStorage-OpenConnect/proxmox-multipath-display) gets you a much more vSphere like experience.
vSkeeBall 