The reverse is true for TPG with That is, really AO for LUN 2 and ANO for LUN 1.

On some active/passive ALUA-capable arrays, you might read slot groups with a€?Standbya€? AAS instead of a€?ANOa€? from the non-owner SP.

Asymmetric Accessibility Condition

Ports in an ALUA TPG tends to be in the same AAS always pertaining to a given LUN. The TPG’s AAS include reported into initiators as a result into the REPORT TPGS demand. The TPG descriptor is reported in byte 1 of the impulse.

Transitioning-The TPG AAS is in the process of changing in one county to some other. For instance, if the SP of an AO TPG has been rebooted or is taken traditional, or if the SAN (storage space community) admin by hand moves LUN control (on EMC CLARiiON, that is known as trespass), the AAS with the TPG regarding the different SP modifications to AO. Although this procedure is actually continuous, the TPG AAS are transitioning.

As the TPG is during this county, getting demands through the initiators return ACTIVE or a CHECK CONDITION with awareness crucial NOT SET and ASC (additional sense code) PRACTICAL PRODUCT NOT OBTAINABLE or ASYMMETRIC ACCESSIBILITY CONDITION TRANSITION.

Standby-This county is much like a passive SP in a non-ALUA setup as well as on some ALUA-capable arrays. It returns a CHECK SITUATION with awareness crucial NOT SET.

As soon as the TPG is within this AAS, it helps a subset of instructions that it accepts when it’s in AO AAS:

Unavailable-This AAS is generally observed whenever the TPG’s the means to access the LUN is restricted read review through hardware mistakes or any other SCSI product limitations. A TPG within this county is unable to transition to AO or ANO up until the error subsides.

ESXi 6 sends the I/O to TPGs which can be in AO AAS, however if they may not be available, I/O is distributed to TPGs being in ANO AAS. If the storage array gets continual I/O on TPGs being in ANO AAS, the range changes the TPG’s county to AO AAS. Which makes that change is dependent upon the ALUA management means associated with storing collection (understand then section).

ALUA Administration Settings

This is done via a couple of instructions and feedback back and forth from the space arrays. These instructions are as follows:

INQUIRY-According to SPC-3, section 6.4.2, in reaction for this demand, a wide range returns some content regarding the VPD (vital goods data) or EVPD (expanded essential product facts). The query facts returned in response to the order contains the TPGS field. If came back benefits in this industry try nonzero, that product (LUN) helps ALUA. (See Table 6.3, later on contained in this part, for all the relationship between your value of the TPGS area and AAS management modes.)

ready TARGET SLOT COMMUNITIES (ready TPGs)-This command desires that storage array ready the AAS of most slots in given TPGs. For instance, a TPG’s AAS can move from ANO to AO through the ready TPGs demand.

Table 6.1 ALUA AAS management methods

Maybe not Supported-The response to the REPORT TPGs and ready TPGs instructions is invalid. This means that the storage collection does not supporting ALUA or, in the case of EMC CLARiiON, the initiator documents commonly set up in a mode that supports ALUA.

Implicit-The variety reacts to DOCUMENT TPGs however ready TPGs instructions. In cases like this, establishing the TPG’s AAS is accomplished just by space selection.

Explicit-The selection responds to both REPORT TPGs and SET TPGs directions. In cases like this, establishing the TPG’s AAS can be done best by initiator.