From: Sebastian Riemer <sebastian.riemer-EIkl63zCoXaH+58JC4qpiA@public.gmane.org>
To: Gandalf Corvotempesta
<gandalf.corvotempesta-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Cc: linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: Infiniband HA
Date: Wed, 08 May 2013 12:24:28 +0200 [thread overview]
Message-ID: <518A27DC.5070303@profitbricks.com> (raw)
In-Reply-To: <CAJH6TXgC8jGHiRxL5gRnYud8V6fSrDRvEd+w8nazCcmt92-bCA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
Hi Gandalf,
just build up two separate fabrics. This means that you don't
interconnect both switches.
Otherwise, issues on one port also affect the other port.
What do you use for storage? SRP?
This requires dm-multipath and fast IO failing + automatic reconnect
patches from Bart or from me.
All other traffic like IPoIB for example also has to be able to switch
the port.
Cheers,
Sebastian
On 08.05.2013 12:06, Gandalf Corvotempesta wrote:
> Hi to all
> I'm new to Infiniband/RMDA and probabily this is not the right place to ask.
> I'm planning a new infiniband infrastructure with dual port HBA and I
> have a question:
>
> How can I archieve fault tollerance with multiple switches? Should I
> connect all like a standard ethernet infrastructure ? (port1 to
> switch1, port2 to switch2, and both switches interconnected with a
> cable?)
>
> Thank you.
--
To unsubscribe from this list: send the line "unsubscribe linux-rdma" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
prev parent reply other threads:[~2013-05-08 10:24 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-08 10:06 Infiniband HA Gandalf Corvotempesta
[not found] ` <CAJH6TXgC8jGHiRxL5gRnYud8V6fSrDRvEd+w8nazCcmt92-bCA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2013-05-08 10:24 ` Sebastian Riemer [this message]
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=518A27DC.5070303@profitbricks.com \
--to=sebastian.riemer-eikl63zcoxah+58jc4qpia@public.gmane.org \
--cc=gandalf.corvotempesta-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
--cc=linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.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