<html><body><p>Refreshing this post in case anyone might have missed it... still trying to figure out some way to have multiple iscsi paths managed <br>by a single ocf_heartbeat_iscsi resource. Any ideas? <br><br>Thanks!<br><br>Scott Greenlese ... KVM on System Z - Solutions Test, IBM Poughkeepsie, N.Y.<br> INTERNET: swgreenl@us.ibm.com <br><br><br><img width="16" height="16" src="cid:1__=8FBB0A43DFF910C38f9e8a93df938690918c8FB@" border="0" alt="Inactive hide details for Scott Greenlese---02/15/2017 12:18:57 PM---Hi folks, I'm running some test scenarios with an ocf_hear"><font color="#424282">Scott Greenlese---02/15/2017 12:18:57 PM---Hi folks, I'm running some test scenarios with an ocf_heartbeat_iscsi pacemaker</font><br><br><font size="2" color="#5F5F5F">From: </font><font size="2">Scott Greenlese/Poughkeepsie/IBM@IBMUS</font><br><font size="2" color="#5F5F5F">To: </font><font size="2">users@clusterlabs.org</font><br><font size="2" color="#5F5F5F">Cc: </font><font size="2">Si Bo Niu <niusibo@cn.ibm.com>, Michael Tebolt/Poughkeepsie/IBM@IBMUS</font><br><font size="2" color="#5F5F5F">Date: </font><font size="2">02/15/2017 12:18 PM</font><br><font size="2" color="#5F5F5F">Subject: </font><font size="2">[ClusterLabs] How to configure my ocf_heartbeat_iscsi resource(s) such that I have both paths to the LUN?</font><br><hr width="100%" size="2" align="left" noshade style="color:#8091A5; "><br><br><br><font size="5">Hi folks, </font><font size="4"><br></font><font size="5"><br>I'm running some test scenarios with an ocf_heartbeat_iscsi pacemaker resource, <br>using the following XIV multipath'ed configuration: </font><font size="4"><br></font><font size="5"><br>I created a single XIV iscsi host definition containing all the pacemaker host (cluster node) 'Initiator's:</font><font size="4"><br></font><font size="5"><br>XIV 7812475>>host_list_ports host=pacemaker_iscsi<br>Host Type Port Name <br>pacemaker_iscsi iSCSI iqn.2005-03.org.open-iscsi:6539c3daf095 <br>pacemaker_iscsi iSCSI iqn.2005-03.org.open-iscsi:11d639c0976c <br>pacemaker_iscsi iSCSI iqn.1994-05.com.redhat:74ca24d6476 <br>pacemaker_iscsi iSCSI iqn.1994-05.com.redhat:ea17bebd09a <br>pacemaker_iscsi iSCSI iqn.1994-05.com.redhat:b852a67852c </font><font size="4"><br></font><font size="5"><br>Here is the XIV Target IP:port / IQN info:</font><font size="4"><br></font><font size="5"><br>10.20.92.108:3260 <br>Target: iqn.2005-10.com.xivstorage:012475 </font><font size="4"><br></font><font size="5"><br>10.20.92.109:3260<br>Target: iqn.2005-10.com.xivstorage:012475 </font><font size="4"><br></font><font size="5"><br>I mapped a single 17Gb Lun to the XIV host: 20017380030BB110F</font><font size="4"><br><br></font><font size="5"><br>From ocf_heartbeat_iscsi man page, it didn't seem obvious to me how I might specify multiple<br>IP Portals (i.e. both the .108 and .109 IPs) to a single ocf_heartbeat_iscsi resource. So, <br>I went ahead and configured my resource using just the .108 IP path, as follows:</font><font size="4"><br></font><font size="5"><br>Using the above XIV definitions, I created a single iscsi pacemaker resource using only one of the two IP<br>paths to the XIV LUN: </font><font size="4"><br></font><font size="5"><br>[root@zs95kj VD]# pcs resource show iscsi_r4</font><font size="4"><br></font><font size="5"><br>Resource: iscsi_r4 (class=ocf provider=heartbeat type=iscsi)<br>Attributes: portal=10.20.92.108:3260 target=iqn.2005-10.com.xivstorage:012475<br>Operations: start interval=0s timeout=120 (iscsi_r4-start-interval-0s)<br>stop interval=0s timeout=120 (iscsi_r4-stop-interval-0s)<br>monitor interval=120 timeout=30 (iscsi_r4-monitor-interval-120)</font><font size="4"><br></font><font size="5"><br>I'm looking for suggestions as to how I should configure my iscsi resource(s) such that I have both paths (.108 and .109)<br>to the LUN available to my application? Do I need to create a second iscsi resource for the .109 path, and colocate<br>them so that they move about the cluster together? </font><font size="4"><br></font><font size="5"><br>As an aside, I have run into situations where the second IP (.109) comes online to where my iscsi_r4 resource is running (how or why,<br>I'm not sure), which introduces problems because iscsi_r4 only manages the .108 connection. </font><font size="4"><br></font><font size="5"><br>Thanks in advance... </font><font size="4"><br><br>Scott Greenlese ... KVM on System Z - Solutions Test, IBM Poughkeepsie, N.Y.<br>INTERNET: swgreenl@us.ibm.com <br><br></font><tt>_______________________________________________<br>Users mailing list: Users@clusterlabs.org<br></tt><tt><a href="http://lists.clusterlabs.org/mailman/listinfo/users">http://lists.clusterlabs.org/mailman/listinfo/users</a></tt><tt><br><br>Project Home: </tt><tt><a href="http://www.clusterlabs.org">http://www.clusterlabs.org</a></tt><tt><br>Getting started: </tt><tt><a href="http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf">http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf</a></tt><tt><br>Bugs: </tt><tt><a href="http://bugs.clusterlabs.org">http://bugs.clusterlabs.org</a></tt><tt><br></tt><br><br><BR>
</body></html>