Robert Wood <rwood <at> iss-integration.com> writes: > > One node sets ALUA state to s (Standby), while the other to o > (Active/Optimized). However,when both nodes are presenting the same > LUN to Vmware, the TPG is only set to one of the nodes' ID for all > paths to storage. ALUA state is Standby for all LUNs and there are > many errors in Vmware host's vmkernel.log, such as: So far we found that TPG groups of the same name must be present on both hosts, even if they have no members. Suspecting that LIO generates some TPG ID behind the scenes, but this is not documented. As long as all groups with the same names are present on all hosts, initiator sees correct ALUA states. Working to test failover and wondering if there are any controls over the described behavior. RW -- To unsubscribe from this list: send the line "unsubscribe target-devel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
