<div dir="ltr"><div class="gmail_extra"><div class="gmail_quote">On Thu, Aug 4, 2016 at 7:27 PM, Chris Adams <span dir="ltr"><<a href="mailto:cma@cmadams.net" target="_blank">cma@cmadams.net</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class="">Once upon a time, James Michels <<a href="mailto:karma.sometimes.hurts@gmail.com">karma.sometimes.hurts@gmail.<wbr>com</a>> said:<br>
> Correct me if I'm wrong but I think Dan meant target's IPs. So if you have<br>
> a SAN backend with two IP addresses, you first discover LUNs from first IP<br>
> address, then discover LUNs from the second IP address, and so on... once<br>
> you have them all, you just check them and click on "OK" so the same target<br>
> is added with several IP addresses. You don't need to have one IP address<br>
> per oVirt server.<br>
<br>
</span>Well, to do iSCSI multipath right, you should also have multiple<br>
interfaces on each client server, each with its own IP. I'm not sure<br>
how you do that with oVirt.<br></blockquote><div><br></div><div>We support it as well - it's poorly called 'iSCSI bonding'.</div><div><br></div><div>BTW, having two IPs on a single subnet is not a great idea - it usually mean you have a SPOF somewhere (the switch perhaps?).</div><div>Y.</div><div><br></div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div class="HOEnZb"><div class="h5"><br>
--<br>
Chris Adams <<a href="mailto:cma@cmadams.net">cma@cmadams.net</a>><br>
______________________________<wbr>_________________<br>
Users mailing list<br>
<a href="mailto:Users@ovirt.org">Users@ovirt.org</a><br>
<a href="http://lists.ovirt.org/mailman/listinfo/users" rel="noreferrer" target="_blank">http://lists.ovirt.org/<wbr>mailman/listinfo/users</a><br>
</div></div></blockquote></div><br></div></div>