ESX/ESXi 4.x/5.

x Multipathing SATP ALUA settings

Tegile ZebiTM storage arrays support storage multipathing for SAN protocols (FC and iSCSI) when used with
storage consumers such as VMware ESX/ESXi and/or Windows servers.
iSCSI multipathing support in ZebiTM is transparent, and implemented through transparent takeover of virtual IP
addresses (service IP) between the two nodes of the HA2x00 appliances. Although storage initiators cannot see
active/standby paths during regular usage, upon failover, the virtual service IP is taken over by the peer node, thus
allowing the initiator to reestablish a connection and proceed with I/O.
FC multipathing support in ZebiTM utilizes Aymmetric Logical Unit Access (ALUA) support in initiators. FC--ALUA
support has been tested and is supported with VMware ESX 4.1, 5.0, 5.1, and Windows server 2003 (R2), and 2008
(R2).
To enable ALUA support, the initiator host has to be configured to use ALUA for the LUNs provided by Zebi. This
document identifies and details the configuration necessary on VMware ESX, XenServer, and Windows. In addition,
where necessary, any configuration necessary for iSCSI is also identified.

To check settings of a lun from the Vsphere Client GUI:

1) Right click on the tegile lun in ESX (Confuguration>Storage)
2) Click properties
3) Click 'manage paths'
4) You will see a string which says SATP Alua or SATP Default AA for the storage plugin loaded.
For ISCSI: This should have Satp Default AA
For FC: This should have SATP ALUA

ESX/ESXi 4.X
- SSH to the ESX server as root

Steps to Check existing rules for Zebi FC and iSCSI arrays and Remove existing rules
Verify the rules were added in 4.X:
# esxcli nmp satp listrules | grep -i TEGILE
Removing the rules for FC and ISCSI
# esxcli nmp satp deleterule -s VMW_SATP_ALUA -V TEGILE -M "ZEBI-FC" c "tpgs_on" -e
"Tegile Zebi FC"
# esxcli nmp satp deleterule -s VMW_SATP_DEFAULT_AA -V TEGILE -M "ZEBI-ISCSI" -c
"tpgs_on"-e "Tegile Zebi iSCSI"
Add New Rules
FC:
# esxcli nmp satp addrule --force -s VMW_SATP_ALUA -e "Tegile Zebi FC" -V "TEGILE"
-M "ZEBI-FC" -c "tpgs_on" --psp="VMW_PSP_MRU"
iSCSI:
# esxcli nmp satp addrule --force -s VMW_SATP_DEFAULT_AA -e "Tegile Zebi iSCSI" -V
"TEGILE" -M "ZEBI-ISCSI" --psp="VMW_PSP_MRU"
Steps to Un-claim existing Zebi Luns and reload/re-run claims rules
#esxcli corestorage claiming unclaim -t vendor -v TEGILE-m "ZEBI-FC"
#esxcli corestorage claiming unclaim -t vendor -v TEGILE-m "ZEBI-ISCSI"
Note: If existing Zebi LUNS are in use, they may not be unclaimed. In that case the
rules will not take effective on those existing LUNS until next host reboot.
Reload and re-run claim rules for the newly added rules to take effective
#esxcli corestorage claimrule load
#esxcli core storage core claimrule run

ESXi 5.X
- SSH to the ESX server as root.

Steps to Check existing rules for Zebi FC and iSCSI arrays and Remove existing rules
Verify the rules were added in 5.X:
# esxcli storage nmp satp rule list | grep -i TEGILE
Removing the rules for FC and ISCSI
# esxcli storage nmp satp rule remove -s VMW_SATP_ALUA -V "TEGILE" -M "ZEBI-FC" -P
VMW_PSP_FIXEDc "tpgs_on" -e "Tegile Zebi FC"
# esxcli storage nmp satp rule remove -s VMW_SATP_DEFAULT_AA -V "TEGILE" -M
"ZEBI-ISCSI" -P VMW_PSP_FIXEDc "tpgs_on"-e "Tegile Zebi iSCSI"
Add New Rules
FC:
# esxcli storage nmp satp rule add -s VMW_SATP_ALUA -V "TEGILE" -M "ZEBI-FC" -c
"tpgs_on" -P VMW_PSP_FIXED -e "Tegile Zebi FC"
iSCSI:
# esxcli storage nmp satp rule add -s VMW_SATP_DEFAULT_AA -V "TEGILE" -M
"ZEBI-ISCSI" -P VMW_PSP_FIXED -e "Tegile Zebi iSCSI"
Steps to Un-claim existing Zebi Luns and reload/re-run claims rules
Un-claim existing Zebi Luns
# esxcli storage core claiming unclaim -t vendor -v TEGILE-m "ZEBI-FC"
#esxcli storage core claiming unclaim -t vendor -v TEGILE-m "ZEBI-ISCSI"
Note: If existing Zebi LUNS are in use, they may not be unclaimed. In that case the
rules will not take effective on those existing LUNS until next host reboot.
Reload and re-run claim rules for the newly added rules to take effective
#esxcli storage core claimrule load
#esxcli storage core claimrule run

If running ESXi 5 also see:

http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=2007
427
# esxcli system settings advanced set --int-value 0 --option /VMFS3/EnableBlockDelete
Note: This is a per-host setting and must be issued on each ESXi 5.0 host in your cluster. It will work for
both VMFS3 and VMFS5 datastores.
Note: If running ESX 5.0, Update 1, or ESX 5.1, then running the above EnableBlockDelete command is not
required.