I experienced to split brand new screenshots on the four quadrants with the intention that I am able to inform you the articles of efficiency. Right here, I’ve made an effort to thin it down and you will listing only the contours I have to let you know. To do so, I utilized the following the command:
This command lists all SATP rules and then uses grep for the string’s model, 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_for 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_with 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_with the.
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_towards. 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.
Identifying Devices’ ALUA Setup
ALUA configurations is for the LUNs in combination with TPGs. So you can listing this type of options, you could potentially work at the next command:
An illustration regarding a keen EMC VNX otherwise CLARiiON CX Variety
This output shows the Stores Number Kind 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 Shops Variety Variety of Device Config line, wrapped for readability, which includes a number of parts:The first set of curly brackets, , boasts initiator registration–certain setting. It is specific to EMC VNX and the CLARiiON family of arrays. Contained in this place, a couple choices are indexed:
navireg=on the-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 Mode is set to 4, which enables ALUA for this initiator. (You can find more details on this in Chapter 7.)
ipfilter=on 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 new ALUA AAS management means options are closed into the an extra number of curly brackets, within that is some other nested collection of curly supports to the TPG’s AAS free herpes dating Australia setup. These are the ALUA AAS government function alternatives:
Explicit_allow=for the-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).