Routed iSCSI and NVMe/TCP: Linux Routes and VRFs

Linux Storage Networking, Part 3 of 4.Part 1: Linux iSCSI Multipath: Fix ARP Flux and NIC BindingPart 2: LACP vs Multipath: Linux iSCSI and NVMe/TCP So the network team says the storage has to be routed. Fine. iSCSI and NVMe/TCP run over IP. We can work with that. What I don’t want is storage following the managementContinue reading “Routed iSCSI and NVMe/TCP: Linux Routes and VRFs”

LACP vs Multipath: Linux iSCSI and NVMe/TCP

Linux Storage Networking, Part 2 of 4.Part 1: ARP Flux and NIC BindingPart 3: Routed iSCSI and NVMe/TCP: Linux Routes and VRFs Two NICs, one bond, one IP. That sounds easier than dealing with two interfaces on the same subnet. And for some things it is. For iSCSI and NVMe/TCP, I would rather let multipath useContinue reading “LACP vs Multipath: Linux iSCSI and NVMe/TCP”

Linux iSCSI Multipath: Fix ARP Flux and NIC Binding

Linux Storage Networking, Part 1 of 4.Part 2: LACP vs Multipath: Linux iSCSI and NVMe/TCPPart 3: Routed iSCSI and NVMe/TCP: Linux Routes and VRFs So you’ve got two NICs in a Linux host, four iSCSI ports on the array, and eight paths to your storage. multipath -ll says everything is happy. You should be able to pullContinue reading “Linux iSCSI Multipath: Fix ARP Flux and NIC Binding”

Linux NVME-TCP shared targets with LVM

I’ve been working on Proxmox the last few months and ran into an issue when using nvme-tcp volumes. I connected multiple hosts to a number of shared volumes. I’ve done this before using a number of different methods such as iscsi or shared managed disks on Azure. All of these just worked. When connecting toContinue reading “Linux NVME-TCP shared targets with LVM”