STAR_NVMEOF_IOCTL_TARGET_DISCOVERY request failed (err 121)

Initiator (iSCSI, FCoE, AoE, iSER and NVMe over Fabrics), iSCSI accelerator and RAM disk

Moderators: anton (staff), art (staff), Max (staff), Anatoly (staff)

Post Reply
Aqor-roy
Posts: 4
Joined: Thu Dec 15, 2022 10:04 am

Thu Dec 22, 2022 4:38 pm

I have tried iscsi taget by using starwind vsan such that sucessfully connected to client computer using microsoft iscsi initiators. While when using nvme target by vsan but cannot be connected to starwind nvme of initiator. It appear error 121 when using cmd mode and appear log in fail message when using microsoft iscsi initiator creat the channel of 4420 port. Both server and client nic are directly connect.
For what I can check by myself first and what is the meaning of the error code ?

My server setup:
CPU: Xeon E2387g
Motherboard: ASrock rack E3C256D4U-2L2T
RAM: 8GB (will upgrade to 128GB)
SSD:P5800X 800GB
NIC: E810-2CQDA2
OS: windows server 2022 standard evaluation

My client setup:
CPU : Ryzen 5700g
Motherboard : X570Phanton Gaming-ITX/TB3
RAM:64GB
SSD:Optane 905p 960GB
NIC: E810-XXVDA4
OS: windows server 2022 standard evaluation
yaroslav (staff)
Staff
Posts: 2315
Joined: Mon Nov 18, 2019 11:11 am

Thu Dec 22, 2022 4:50 pm

Please log a call with StarWind Support at support@starwind.com Use this thread and 836281 as your references. Having the command you use will be helpful.
Also, make sure the drivers are up to date.
Aqor-roy
Posts: 4
Joined: Thu Dec 15, 2022 10:04 am

Fri Dec 23, 2022 3:07 am

The command I use in cmd is " starwNVMeof_Ctrl.exe discovery 172.16.77.2:4420 172.16.77.1" . This is not first time appear this error message. Previously, the case is using chelois T6 in ubuntu as target and e810 in win 2022 as starwind nvme initiator, I try to install the least nic driver of intel nic then is ok. But this time fail for both win server and using intel nic.
So, I also want to what does this error mesage. (i have sent email for support)
User avatar
anton (staff)
Site Admin
Posts: 4010
Joined: Fri Jun 18, 2004 12:03 am
Location: British Virgin Islands
Contact:

Tue Feb 27, 2024 3:29 pm

We didn't test much with Chelsio TBH, just because they are rare in the field. Mellanox is what our NIC-of-choice is.

P.S. I'm pinging support guys...
Aqor-roy wrote:
Fri Dec 23, 2022 3:07 am
The command I use in cmd is " starwNVMeof_Ctrl.exe discovery 172.16.77.2:4420 172.16.77.1" . This is not first time appear this error message. Previously, the case is using chelois T6 in ubuntu as target and e810 in win 2022 as starwind nvme initiator, I try to install the least nic driver of intel nic then is ok. But this time fail for both win server and using intel nic.
So, I also want to what does this error mesage. (i have sent email for support)
Regards,
Anton Kolomyeytsev

Chief Technology Officer & Chief Architect, StarWind Software

Image
Post Reply