Storage Performance Development Kit (SPDK)
 help / color / mirror / Atom feed
From: Kirubakaran Kaliannan <kirubak at zadarastorage.com>
To: spdk@lists.01.org
Subject: Re: [SPDK] NVMf target configuration issue
Date: Tue, 05 Sep 2017 16:08:37 +0530	[thread overview]
Message-ID: <8628fc0b70a92168c4bc1cb2e2bc96e3@mail.gmail.com> (raw)
In-Reply-To: FA6C2217B01E9D48A581BB486602101439937F79@shsmsx102.ccr.corp.intel.com

[-- Attachment #1: Type: text/plain, Size: 4132 bytes --]

Thanks Yang, adding the host line helped.



Regards

-kiru



*From:* SPDK [mailto:spdk-bounces(a)lists.01.org] *On Behalf Of *Yang, Ziye
*Sent:* Tuesday, September 05, 2017 10:41 AM
*To:* Storage Performance Development Kit
*Subject:* Re: [SPDK] NVMf target configuration issue



And the other choice is to remove the Host related line, which means any
host can connect.



*From:* SPDK [mailto:spdk-bounces(a)lists.01.org <spdk-bounces(a)lists.01.org>] *On
Behalf Of *Yang, Ziye
*Sent:* Tuesday, September 5, 2017 1:04 PM
*To:* Storage Performance Development Kit <spdk(a)lists.01.org>
*Subject:* Re: [SPDK] NVMf target configuration issue



Hi Kiru,



According to the error message, I suggest that you add the Host info in the
following section.





[Subsystem1]

  NQN nqn.2016-06.io.spdk:cnode1

  Core 0

  Listen RDMA 10.3.7.2:4420

  Host nqn.2016-06.io.spdk:init

*                 Host
nqn.2014-08.org.nvmexpress:NVMf:uuid:5e5e0064-2ad6-4a43-9c26-063e3ef6cf14*

  SN SPDK00000000000001

  Namespace AIO0





Thanks.



*From:* SPDK [mailto:spdk-bounces(a)lists.01.org <spdk-bounces(a)lists.01.org>] *On
Behalf Of *Kirubakaran Kaliannan
*Sent:* Tuesday, September 5, 2017 12:52 PM
*To:* Storage Performance Development Kit <spdk(a)lists.01.org>
*Subject:* [SPDK] NVMf target configuration issue







Hi All,



I am trying to get the nvmf configuration going with SPDK.



I have the following configuration,



*# ofed 2.4 on both target and initiator*

*# SPDK + 3.18 kernel on target *

*# 4.9 kernel on initiator*

*# mellanox connect3X-Pro*



*/etc/spdk/nvmf.conf*



[Global]

[Rpc]

  Enable No

  Listen 127.0.0.1

[AIO]

  AIO /dev/sdd AIO0



[Nvmf]

  MaxQueuesPerSession 4

  AcceptorPollRate 10000



[Subsystem1]

  NQN nqn.2016-06.io.spdk:cnode1

  Core 0

  Listen RDMA 10.3.7.2:4420

  Host nqn.2016-06.io.spdk:init

  SN SPDK00000000000001

  Namespace AIO0





*From initiator I tried discover and connect*



*# nvme discover -t rdma -a 10.3.7.2 -s 4420*



Discovery Log Number of Records 1, Generation counter 4

=====Discovery Log Entry 0======

trtype:  rdma

adrfam:  ipv4

subtype: nvme subsystem

treq:    not specified

portid:  0

trsvcid: 4420

subnqn:  nqn.2016-06.io.spdk:cnode1

traddr:  10.3.7.2

rdma_prtype: not specified

rdma_qptype: connected

rdma_cms:    rdma-cm

rdma_pkey: 0x0000



*# nvme connect -t rdma -n "nqn.2016-06.io.spdk:cnode1" -a 10.3.7.2 -s 4420*

Failed to write to /dev/nvme-fabrics: Input/output error



[dmesg]

[59909.541392] nvme nvme0: new ctrl: NQN
"nqn.2014-08.org.nvmexpress.discovery", addr 10.3.7.2:4420

[59940.389952] nvme nvme0: Connect command failed, error wo/DNR bit: 388



*On target I get the following error*



# app/nvmf_tgt/nvmf_tgt -c /etc/spdk/nvmf.conf  > /tmp/1

EAL: Detected 20 lcore(s)

reactor.c: 314:_spdk_reactor_run: *NOTICE*: Reactor started on core 0 on
socket 0

copy_engine_ioat.c: 306:copy_engine_ioat_init: *NOTICE*: Ioat Copy Engine
Offload Enabled

nvmf_tgt.c: 215:nvmf_tgt_create_subsystem: *NOTICE*: allocated subsystem
nqn.2014-08.org.nvmexpress.discovery on lcore 0 on socket 0

nvmf_tgt.c: 215:nvmf_tgt_create_subsystem: *NOTICE*: allocated subsystem
nqn.2016-06.io.spdk:cnode1 on lcore 0 on socket 0

rdma.c: 955:spdk_nvmf_rdma_create: *NOTICE*: *** RDMA Transport Init ***

rdma.c:1120:spdk_nvmf_rdma_listen: *NOTICE*: *** NVMf Target Listening on
10.3.7.2 port 4420 ***

conf.c: 500:spdk_nvmf_construct_subsystem: *NOTICE*: Attaching block device
AIO0 to subsystem nqn.2016-06.io.spdk:cnode1

nvmf_tgt.c: 290:spdk_nvmf_startup: *NOTICE*: Acceptor running on core 0 on
socket 0

*request.c: 171:nvmf_process_connect: *ERROR*: Subsystem
'nqn.2016-06.io.spdk:cnode1' does not allow host
'nqn.2014-08.org.nvmexpress:NVMf:uuid:5e5e0064-2ad6-4a43-9c26-063e3ef6cf14'*





can you please help on why I am not able to connect in this configuration.



Regards,

-kiru

[-- Attachment #2: attachment.html --]
[-- Type: text/html, Size: 10999 bytes --]

             reply	other threads:[~2017-09-05 10:38 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-09-05 10:38 Kirubakaran Kaliannan [this message]
  -- strict thread matches above, loose matches on Subject: below --
2017-10-18  6:17 [SPDK] NVMf Target configuration issue Gyan Prakash
2017-10-18  1:17 Gyan Prakash
2017-10-18  1:06 Gyan Prakash
2017-10-18  0:54 Gyan Prakash
2017-10-18  0:51 Gyan Prakash
2017-10-18  0:51 Liu, Changpeng
2017-10-18  0:41 Harris, James R
2017-10-18  0:36 Gyan Prakash
2017-10-17 20:03 Gyan Prakash
2017-10-17 19:54 Verkamp, Daniel
2017-10-17 19:04 Gyan Prakash
2017-09-07  8:29 [SPDK] NVMf target " Kirubakaran Kaliannan
2017-09-06 15:28 Harris, James R
2017-09-06  7:28 Kirubakaran Kaliannan
2017-09-05  5:10 Yang, Ziye
2017-09-05  5:03 Yang, Ziye
2017-09-05  4:51 Kirubakaran Kaliannan

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=8628fc0b70a92168c4bc1cb2e2bc96e3@mail.gmail.com \
    --to=spdk@lists.01.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox