STAR_NVMEOF_IOCTL_TARGET_ADD request failed (err 55)!

[Gokul]

Hi Team,

We are getting the below error message while connecting NVMe Namespace throught TCP protocol.

StarNVMeoF_Ctrl.exe insert_tcp 192.168.10.247:4420 192.168.10.169 nqn.1992-05.com.wdc.openflex-data24-usalp03922qa0030:nvme.1 SW1 7 16StarNVMeoF Controller Application v 1.9.0.519
Our Miniport #3 (ver 1.9 build 500)
HostId 0xF4E6155881933F39-CD7F0A8F02457586 - HostName WIN-7UE6DQLR44E
NET_LUID: 0x6008007000000
Connecting to TCP target at addr 192.168.10.247:4420 from 192.168.10.169 SubNQN=nqn.1992-05.com.wdc.openflex-data24-usalp03922qa0030:nvme.1 HostNQN=SW1 nq=7 qd=16 core=0...
STAR_NVMEOF_IOCTL_TARGET_ADD request failed (err 55)!
ConnectController() failed

The same connection is working with RoCE because of the default MDTS value. In RoCE we use default MDTS as 128 but in TCP mode we set default MDTS as 32.
Looks like Starwind having a restriction on a minimum expected MDTS value of the controller which could be either 64K or 128K. The initiator/host must comply with the MDTS advertised by the target/controller.

Could you please let us know why would have such an expectation?

[yaroslav (staff)]

That's a good question!
StarWind NVMe-oF Driver parameters can be altered by editing the corresponding registry keys.
The driver must be restarted to apply new parameter values.
The MaxTransfer Length is set to 64K by default.
You can tweak it in the registry HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\StarNVMeoF\Parameters.

[Gokul]

Thank you for your response.
Please let me know the parameter which I need to add to change the maxtransfer length.
I am unable to see the parameter setting on my current machine on the following path - HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\StarNVMeoF\Parameters

[yaroslav (staff)]

Thanks for your update. Can you please try creating the registry key?

[Gokul]

I have created the following parameter "MaxTarnsferLength" on the registry editor under - HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\StarNVMeoF\Parameters with the default value as "32". After this i tried restarting the starwind service and a host reboot.
Even after rebooting the host i am unable to establish a connection with TCP protocol.
Please confirm me the register key and the value?

[yaroslav (staff)]

Can you please try 64?

[manigandanj]

I ran into a different. Can someone tell me what could the problem ? I am able to discover the controller. FWIW, I am trying to add a TCP controller.

Code: Select all

STAR_NVMEOF_IOCTL_TARGET_ADD request failed (err 0, status 0xc00000c0)!

[yaroslav (staff)]

Can you please share the command and network configuration?
I need to know what is the target, what witches and NIC you use, what is the host OS?
Make sure there are no firewalls or AW software and NVMe-oF is allowed on the target.

[manigandanj]

I am using the below command,

Code: Select all

StarNVMeoF_Ctrl.exe insert_tcp 192.168.179.120:4420 192.168.187.2 nqn.1992-08.com.netapp:sn.807196b3872211ef8793d039ea92bf56:discovery SW_1 512 32 0

This is the environment I have,

• OS : Windows Server 2022 Datacenter edition

• NIC : Chelsio 25G (T6)

• Nic driver : 6.16.1

• Target controller : NetApp with ontap version 9.12.1P5

I am certain about firewall rules. We were able to mount storage on our VMware host using NVMeoF/TCP with the same storage setup.

[yaroslav (staff)]

Many thanks. Can you please share the discovery command output with me?

[manigandanj]

Code: Select all

starNVMeoF_Ctrl.exe discovery_tcp 192.168.179.120:4420 192.168.187.2

StarNVMeoF Controller Application v 2.0.0.672
Our Miniport #4 (ver 2.0 build 672)
Discovering of TCP addr 192.168.179.120:4420 from 192.168.187.2...
        NET_LUID:       0x6008002000000
Discovery returned: gen 13, numrec 4
1) subnqn nqn.1992-08.com.netapp:sn.807196b3872211ef8793d039ea92bf56:discovery
        Discovery: port 0x0, cntlid 0xffff, trtype TCP, addr 192.168.211.121 : 8009, adrfam 1, asqsz 32
2) subnqn nqn.1992-08.com.netapp:sn.807196b3872211ef8793d039ea92bf56:discovery
        Discovery: port 0x1, cntlid 0xffff, trtype TCP, addr 192.168.179.121 : 8009, adrfam 1, asqsz 32
3) subnqn nqn.1992-08.com.netapp:sn.807196b3872211ef8793d039ea92bf56:discovery
        Discovery: port 0x2, cntlid 0xffff, trtype TCP, addr 192.168.211.120 : 8009, adrfam 1, asqsz 32
4) subnqn nqn.1992-08.com.netapp:sn.807196b3872211ef8793d039ea92bf56:discovery
        Discovery: port 0x3, cntlid 0xffff, trtype TCP, addr 192.168.179.120 : 8009, adrfam 1, asqsz 32

[yaroslav (staff)]

Try running the insert_tcp command without :discovery at the end.

[manigandanj]

Removing :discovery did not help, unfortunately.

[yaroslav (staff)]

Can I please have the command and output?
Could you please double-check the firewall rules in Windows or any antivirus installed? Also try
StarNVMeoF_Ctrl.exe insert_tcp 192.168.211.121:4420 192.168.187.2 nqn.1992-08.com.netapp:sn.807196b3872211ef8793d039ea92bf56