I experienced to-break new screenshots to your four quadrants to make sure that I can let you know all stuff of your returns. Right here, We have attempted to trim it off and you can listing just the contours I must show. To achieve this, I made use of 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_to 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 the 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_on 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_on. 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.
ALUA setup was regarding the LUNs in combination with TPGs. To record these types of configurations, you could potentially focus on next order:
This output shows the Sites Variety Sort 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 Stores Range Kind of Unit Config line, wrapped for readability, which includes a number of parts:The first set of curly brackets, , includes initiator membership–specific arrangement. This might be particular to EMC VNX in addition to CLARiiON family of arrays. Within lay, a few choices are noted:
navireg=into 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=to your-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.)
New ALUA AAS government form options are closed during the the second band of curly brackets, inside that’s some other nested collection of curly supports on TPG’s AAS arrangement. These represent the ALUA AAS management means choice:
Explicit_allow=towards 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 sugarbook reviews controller).