Initiator (iSCSI, FCoE, AoE, iSER and NVMe over Fabrics), iSCSI accelerator and RAM disk
Moderators: anton (staff), art (staff), Max (staff), Anatoly (staff)
-
someuser
- Posts: 2
- Joined: Thu Jan 30, 2025 7:56 pm
Thu Jan 30, 2025 8:04 pm
Hello. We are testing NVMe-OF Initiator for suitability for our tasks, and a few issues have arisen:
1) Multipath does not work - multiple connections to one LUN give multiple devices.
2) Connecting via iSCSI Initiator interface according to your manual is not working - Login Error. Can only connect via CLI.
Setup: OceanStor Dorado 5000 V6, Windows 2019, Mellanox ConnectX 4-lx.
-
yaroslav (staff)
- Staff
- Posts: 3242
- Joined: Mon Nov 18, 2019 11:11 am
Fri Jan 31, 2025 3:18 am
Multipath for SAS devices is to be enabled in Windows separately.
CLI connectivity issue is known and relates to the good old iSCSI initiator operation. Our own UI TBA.
-
Bartek02
- Posts: 1
- Joined: Mon Feb 03, 2025 11:21 pm
Mon Feb 03, 2025 11:23 pm
someuser wrote: ↑Thu Jan 30, 2025 8:04 pm
Hello. We are testing NVMe-OF Initiator for suitability for our tasks, and a few issues have arisen:
1) Multipath does not work - multiple connections to one LUN give multiple devices.
2) Connecting via iSCSI Initiator interface according to your manual is not working - Login Error. Can only connect via CLI.
Setup: OceanStor Dorado 5000 V6, Windows 2019, Mellanox ConnectX 4-lx.
For issue 1, have you verified if multipath is correctly configured on both the initiator and target sides, including the necessary drivers for NVMe-OF support? For issue 2, are you using the correct authentication and network settings in the iSCSI Initiator, or could there be a firewall or port issue blocking the login attempt?
-
melmedarda
- Posts: 1
- Joined: Thu Feb 13, 2025 3:23 am
Thu Feb 13, 2025 3:26 am
On your Windows Server 2019 system, verify that the MPIO feature is installed. You can do this via Server Manager or by running the following PowerShell command:
Code: Select all
Install-WindowsFeature -Name Multipath-IO