All of lore.kernel.org
 help / color / mirror / Atom feed
From: Talker Alex <alextalker@yandex.ru>
To: linux-nvme@lists.infradead.org
Subject: NVMe/FC compatible hardware
Date: Thu, 06 Feb 2020 21:28:27 +0300	[thread overview]
Message-ID: <5657351581013707@iva7-8a189d9308a6.qloud-c.yandex.net> (raw)

Hi,

Could anyone kindly clarify if NVMe/FC Linux drivers would work with any FibreChannel HBA?

I've connected ATTO Celerity FC-162E and ATTO Celerity FC-82EN cards(on subsystem & host respectively) and successfully managed to setup a port
but I struggle to connect to it, issuing the following command:

> nvme discover -t fc -a nn-0x20000010860370a4:pn-0x10000010860370a4  -w nn-0x2000001086036870:pn-0x2100001086036870

I get this error:

> [4164487.114514] (NULL device *): queue 0 connect admin queue failed (-111).
> [4164487.114519] nvme nvme0: NVME-FC{0}: reset: Reconnect attempt failed (-111)                                                                                           
> [4164487.114522] nvme nvme0: NVME-FC{0}: Reconnect attempt in 10 seconds
> [4164487.114535] nvme nvme0: NVME-FC{0}: new ctrl: NQN "nqn.2014-08.org.nvmexpress.discovery"
> [4164487.114672] nvme nvme0: Removing ctrl: NQN "nqn.2014-08.org.nvmexpress.discovery"

and nothing on subsystem(controller?) side.

I expect that if addr_tractive attribute of the port in ConfigFS equals 1, it means that selected port/HBA capable in utilization for NVMe-oF.
Am I wrong in that too?

Would anyone kindly provide hardware list where the FC driver works properly?

------------------
Best regards,
Alex

_______________________________________________
linux-nvme mailing list
linux-nvme@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-nvme

             reply	other threads:[~2020-02-06 18:28 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-06 18:28 Talker Alex [this message]
2020-02-06 20:28 ` NVMe/FC compatible hardware James Smart

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=5657351581013707@iva7-8a189d9308a6.qloud-c.yandex.net \
    --to=alextalker@yandex.ru \
    --cc=linux-nvme@lists.infradead.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.