Listing and removing the NVMeoF target from StarWind Init

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
am2020
Posts: 6
Joined: Fri Aug 21, 2020 8:40 pm

Thu Sep 10, 2020 8:08 pm

Hi,

I am using the "StarNVMeof_ctrl" application to connect to my NVMEoF target and I can connect to target and run few test tests using FIO tool.

Is there a way, I can run the nvme-cli commands, like listing the drives and getting more information about the drives on windows platform?

I see few issues with removing the target from initiator. I removed the target as following:
C:\Users\Administrator>starNVMeof_ctrl remove disk2

StarNVMeoF Controller Application v1.6.0
Searching ScsiPorts...
OpenAdapter: Our miniport is \\.\Scsi3:.
Disconnecting ControllerId 0...
Controller disconnected: Id= [0]

C:\Users\Administrator>


Even after removing the target using above command, target IP seems to be saved somewhere on the Initiator system and initiator keeps sending the login request continuously. Is there a way to control this? I do not want StarWind Initiator to persist the target information and keep trying to login all the time. It is causing me grief. How can I control this?
yaroslav (staff)
Staff
Posts: 2341
Joined: Mon Nov 18, 2019 11:11 am

Sat Sep 12, 2020 4:21 am

Greetings,

Welcome to StarWind Forum. You should use the target number, not the disk name with the remove parameter.
After removing the target, the initiator should not keep on connecting to the disks anymore. Please make sure to install the latest Initiator version.
Please note that StarWind NVMe-oF Initiator presents disks as SAS devices to the system. Please consider using something for working with SCSI instead of nvme-cli.
Let me know if removing the target in a way I mentioned above works.
am2020
Posts: 6
Joined: Fri Aug 21, 2020 8:40 pm

Tue Sep 15, 2020 9:56 pm

Thanks for the reply.
I will use target number for removing the target and let you know how it goes.

Whether this target number is number from
"Controller connected: TargetId = [3]
numLuns = 1, numIoQs = 1, ioQDepth = 63, firstCore = 0"
I will try to use the target number there.

Is there a way to know which target number is which "PhysicalDrive<num>" in the Disk Manager?

I will use the SCSI utility to get the drive information.
yaroslav (staff)
Staff
Posts: 2341
Joined: Mon Nov 18, 2019 11:11 am

Wed Sep 16, 2020 3:47 am

Yes, please, try using TargetId=3.

Let us know if any additional assistance is required.
Post Reply