I’d to-break the brand new screenshots towards the five quadrants so I’m able to reveal the articles of the yields. Here, I have attempted to trim it down and you may number just the contours I want to reveal. To do so, I used the following the order:
This command lists all SATP rules and then uses grep for the string’s design, satp_alua, and ---. This causes the output to have column headers and separator lines, which are the first two lines in the output. The rest of the output shows only the lines with satp_alua in them. Notice that the -i argument causes grep to ignore the case.
In this output, notice that the EMC CLARiiON CX family is claimed by the VMW_SATP_ALUA_CX plug-in, based on matches on the Model column setting being DGC and the Claim Options setting being tpgs_to the.
On the other hand, both LSI and IBM 2810-XIV are claimed by the VMW_SATP_ALUA plug-in, based on matches on the Vendor column, the Model column, and the value of tpgs_towards the in the Claim Options column.
NetApp is also claimed by the VMW_SATP_ALUA plug-in, based on matches on the Vendor column and the value of tpgs_towards in the Claim Options column only. In this case, the Model column was not used.
IBM DS8000, which is model 2107-900 (listed in the output without the dash), and IBM SVC (listed here as model 21cuatro5) are claimed by the VMW_SATP_ALUA plug-in, based on the Vendor and Model columns only, even though the Claim Options column setting is not tpgs_towards.
The remaining rule allows VMW_SATP_ALUA to claim devices with any Vendor or Model column value, as long as the Claim Options column value is tpgs_into. This means that any array not listed in the preceding rules that returns a nonzero value for the TPGS field in the inquiry response string gets claimed by VMW_SATP_ALUA. You might think of this as a catch-all ALUA claim rule that claims devices on all ALUA arrays that are not explicitly listed by vendor or model in the SATP claim rules.
Distinguishing Devices’ ALUA Settings
ALUA setup was associated with LUNs in combination with TPGs. So you can list these types of settings, you might manage another demand:
A good example away from an EMC VNX or CLARiiON CX Array
This output shows the Stores Array Variety of field set to VMW_SATP_ALUA_CX, which is the same as the VMW_SATP_ALUA plug-in with additional code to handle certain commands specific to CLARiiON CX ALUA arrays.
The output also shows the Sites Assortment Type Product Config line, wrapped for readability, which arablounge Zoeken includes a number of parts:The first set of curly brackets, , includes initiator registration–particular arrangement. This will be certain so you can EMC VNX and the CLARiiON category of arrays. Inside set, one or two options are indexed:
navireg=toward-This means that NaviAgent Registration option is enabled on this host. It registers the initiator with the VNX or CX array if it is not already registered. Note that you need to check the initiator record on the array to make sure that Failover Form is set to 4, which enables ALUA for this initiator. (You can find more details on this in Chapter 7.)
ipfilter=with the-This option filters the host’s IP address so that it is not visible to the storage array. (You’ll learn more about this in Chapter 7.)
The brand new ALUA AAS management function options are shut in the the next set of curly mounts, inside that is another nested pair of curly mounts with the TPG’s AAS setting. They are the ALUA AAS government function solutions:
Explicit_allow=toward-This means that the host is configured to allow the SATP to exercise its explicit ALUA capability if the need arises (for example, in the event of a failed controller).