SCST ALUA configuration

[David Hunter]

Hi!

I'm building a test system similar to the one detailed in:

http://marcitland.blogspot.com/2014/07/open-storage-dual-controller-oss-disk.html

except that I'm using QLogic HBAs for the targets.  I've followed the configuration closely, but host initiators are still seeing luns from the nonoptimized/slave node.  corosync/pacemaker seem to be configured correctly:

[root@esos-n2 ~]# crm configure show
node $id="1" esos-n1.example.com
node $id="2" esos-n2.example.com
primitive p_scst ocf:esos:scst \
params alua="true" device_group="esos" local_tgt_grp="local" remote_tgt_grp="remote" m_alua_state="active" s_alua_state="nonoptimized" \
op monitor interval="10" role="Master" \
op monitor interval="20" role="Slave" \
op start interval="0" timeout="120" \
op stop interval="0" timeout="60"
ms ms_scst p_scst \
meta master-max="1" master-node-max="1" clone-max="2" clone-node-max="1" notify="true" interleave="true"
property $id="cib-bootstrap-options" \
dc-version="1.1.10-9d39a6b" \
cluster-infrastructure="corosync" \
stonith-enabled="false"

[root@esos-n2 ~]# crm status
Last updated: Sun Dec 14 05:28:16 2014
Last change: Sun Dec 14 03:55:04 2014 via crm_shadow on esos-n1.example.com
Stack: corosync
Current DC: esos-n1 (1) - partition with quorum
Version: 1.1.10-9d39a6b
2 Nodes configured
2 Resources configured

Online: [ esos-n1.example.com esos-n2.example.com ]
 Master/Slave Set: ms_scst [p_scst]
     Masters: [ esos-n1.example.com ]
     Slaves: [ esos-n2.example.com ]
[root@esos-n2 ~]# 

Any help is much appreciated!

Dave

 

[Marc Smith]

Hi Dave,

The initiators will always "see" all of the targets (the paths). Its up to the initiator to use the implicit ALUA information to determine which path(s) IO should take. The target interface(s) from the "master" node will appear as "active" to the initiators and the ones on the "slave" interface will appear "nonoptimized" (at least those are the states I used in that article with the SCST RA).

What type are the initiators (Windows, Linux, ESXi hosts, etc.)? The initiators should use the ALUA information to determine the path, its expected for all of the targets to be visible on the initiators.

--Marc

--
You received this message because you are subscribed to the Google Groups "esos-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to esos-users+...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.