Bug 1389086

Summary:	[Docs] iscsi multipathing docs are unclear
Product:	Red Hat Enterprise Virtualization Manager	Reporter:	marc skinner <mskinner>
Component:	Documentation	Assignee:	rhev-docs <rhev-docs>
Status:	CLOSED WONTFIX	QA Contact:	rhev-docs <rhev-docs>
Severity:	medium	Docs Contact:
Priority:	low
Version:	4.3.0	CC:	apinnick, ctomasko, danken, lsurette, mburman, mskinner, pkovar, sgoodman, srevivo, thildred
Target Milestone:	---	Keywords:	Documentation, Task, ZStream
Target Release:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2022-02-16 16:04:39 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	Storage	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description marc skinner 2016-10-26 20:03:26 UTC

The docs at:

https://access.redhat.com/documentation/en/red-hat-virtualization/4.0/single/administration-guide/#Configuring_iSCSI_Multipathing

are not as clear as they should be.

I found this access document that explains how to set it up - and it gave examples.

https://access.redhat.com/articles/1750313

Please update the documentation to have an example and to better explain the multipath configuration process in the UI.

Comment 2 Emma Heftman 2018-11-08 15:20:54 UTC

Hi Marc
I reviewed the KB article with Maor Lipchuk and he feels that the following suggestion is incorrect:

iSCSI Bond Storage50Multipath mates logical network Storage50 with targets 192.168.50.1 and .50.2
iSCSI Bond Storage51Multipath mates logical network Storage51 with targets 192.168.51.1 and .51.2

This suggests that you need to create two iSCSI bonds, where each is connected to one network and two targets.

Instead he suggests creating one iSCSI bond, connect it to two logical networks and connect them with two targets. This is how redundancy is created.

I will be happy to reflect this in the documentation and to receive any further feedback that you have. The remaining information that appeared in the article was not directly connected with iSCSI multipath.

Comment 3 marc skinner 2018-11-08 22:37:28 UTC

Thanks - I just thought it makes sense to have more information in the docs.

Comment 4 Sandro Bonazzola 2019-01-28 09:41:23 UTC

This bug has not been marked as blocker for oVirt 4.3.0.
Since we are releasing it tomorrow, January 29th, this bug has been re-targeted to 4.3.1.