The opposite is true for TPG thereupon are, truly AO for LUN 2 and ANO for LUN 1.
On some active/passive ALUA-capable arrays, you are likely to discover slot groups with a€?Standbya€? AAS instead of a€?ANOa€? in the non-owner SP.
Asymmetric Accessibility Condition
Slots in an ALUA TPG are in identical AAS all the time with respect to confirmed LUN. The TPG’s AAS become reported for the initiators as a result towards the REPORT TPGS command. The TPG descriptor are reported in byte 1 of this response.
Transitioning-The TPG AAS is in the procedure for switching from just one state to a different. Assuming the SP of an AO TPG is being rebooted or perhaps is taken offline, or if the SAN (storage space network) administrator manually moves LUN possession (on EMC CLARiiON, it is titled trespass), the AAS associated with TPG on alternative SP modifications to AO. While this procedure is continuous, the TPG AAS try transitioning.
While the TPG is during this state, getting demands through the initiators come back HECTIC or a CHECK SITUATION with feeling important NOT EAGER and ASC (additional good sense signal) LOGICAL UNIT NOT ACCESSIBLE or ASYMMETRIC ACCESS COUNTY CHANGE.
Standby-This condition is similar to a passive SP in a non-ALUA setup as well as on some ALUA-capable arrays. They returns a CHECK STATE with good sense important NOT EAGER.
Whenever TPG is during this AAS, they supports a subset of commands which accepts when it’s in AO AAS:
Unavailable-This AAS is usually viewed once the TPG’s usage of the LUN is fixed resulting from hardware mistakes or other SCSI equipment limitations. A TPG in this county cannot change to AO or ANO until the error subsides.
ESXi 6 delivers the I/O to TPGs being in AO AAS, however if they are certainly not offered, I/O is sent to TPGs which happen to be in ANO AAS. In the event that storage space array receives continual I/O on TPGs which are in ANO AAS, the array transitions the TPG’s condition to AO AAS. Who makes that change is determined by the ALUA control mode on the storage range (see the next part).
ALUA Administration Settings
This is accomplished via a set of instructions and feedback to and from the storage space arrays. These directions are as follows:
INQUIRY-According to SPC-3, point 6.4.2, in response to this demand, an array return specific content on the VPD (vital product data) or EVPD (longer important goods information). The query data came back as a result for this demand contains the TPGS area. If the came back benefits in that area is nonzero, that tool (LUN) aids ALUA. (discover desk 6.3, later in this chapter, the relationship within value of the TPGS industry and AAS administration settings.)
SET TARGET INTERFACE TEAMS (ready TPGs)-This command desires your storing array put the AAS of slots in given TPGs. As an example, a TPG’s AAS can transition from ANO escort in Lansing to AO through the SET TPGs demand.
Dining table 6.1 ALUA AAS administration modes
Not Supported-The reaction to the REPORT TPGs and ready TPGs instructions is actually invalid. Therefore the storage collection does not help ALUA or, in the case of EMC CLARiiON, the initiator reports aren’t set up in a mode that aids ALUA.
Implicit-The collection responds to REPORT TPGs not arranged TPGs commands. In this situation, placing the TPG’s AAS is completed just by the storing variety.
Explicit-The variety reacts to both DOCUMENT TPGs and SET TPGs directions. In this situation, placing the TPG’s AAS is possible best from the initiator.
Leave A Comment