All of lore.kernel.org
 help / color / mirror / Atom feed
From: pawelx.cybulski@intel.com (Cybulski, PawelX)
Subject: Support needed with setting up multipath on NVMeoF
Date: Thu, 18 Jan 2018 14:24:12 +0000	[thread overview]
Message-ID: <CDAF3D5FC44D984DBB5AC42F738B4BA2589895F5@IRSMSX107.ger.corp.intel.com> (raw)

Hi,

What I want to achieve is:
-	Two NVMe targets pointing to the same NVMe 
-	Targets mounted twice on initiator via different paths (different ports in RDMA NIC)
-	Setup nvmeof multipath on initiator side
-	Run fio tests, bring down one interface and check if it will go through another
-	Run fio tests, via both interfaces at the same time

So far I have:
-	Two machines with kernel 4.15.0-rc8 compiled with CONFIG_NVME_MULTIPATH=y
-	Two targets started on server each pointing to the same NVMe (each using different network port and different ip)
-	Targets mounted on initiator side

Nvme list-subsys is displaying
nvme-subsys0 - NQN=nvme-subsystem-TEST
\
+- nvme0 rdma traddr=100.0.0.90 trsvcid=1055
nvme-subsys1 - NQN=nvme-subsystem-TEST2
\
+- nvme1 rdma traddr=100.0.50.90 trsvcid=1055

I am using latest nvme-cli:
v0.2-612-g8466996

Tried to look through documentation in nvme-cli, and I found only:
"       -m, --nmic
           Namespace multipath and sharing capabilities.

EXAMPLES
       No examples provided yet."

In ./nvme-create-ns.1

Could you point me to documentation where I could find setup steps for nvme multipath (different options, fail over, round robin), or if there isn't any could you provide me with some steps to follow.



Best Regards,
Pawe? Cybulski?


--------------------------------------------------------------------

Intel Technology Poland sp. z o.o.
ul. Slowackiego 173 | 80-298 Gdansk | Sad Rejonowy Gdansk Polnoc | VII Wydzial Gospodarczy Krajowego Rejestru Sadowego - KRS 101882 | NIP 957-07-52-316 | Kapital zakladowy 200.000 PLN.

Ta wiadomosc wraz z zalacznikami jest przeznaczona dla okreslonego adresata i moze zawierac informacje poufne. W razie przypadkowego otrzymania tej wiadomosci, prosimy o powiadomienie nadawcy oraz trwale jej usuniecie; jakiekolwiek
przegladanie lub rozpowszechnianie jest zabronione.
This e-mail and any attachments may contain confidential material for the sole use of the intended recipient(s). If you are not the intended recipient, please contact the sender and delete all copies; any review or distribution by
others is strictly prohibited.

             reply	other threads:[~2018-01-18 14:24 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-18 14:24 Cybulski, PawelX [this message]
2018-01-18 14:32 ` Support needed with setting up multipath on NVMeoF Johannes Thumshirn

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=CDAF3D5FC44D984DBB5AC42F738B4BA2589895F5@IRSMSX107.ger.corp.intel.com \
    --to=pawelx.cybulski@intel.com \
    /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.