I experienced to-break the latest screenshots on five quadrants so I will show all the articles of your own returns. Right here, I’ve tried to thin they down and you will listing only the outlines I need to let you know. To accomplish this, We used the pursuing the demand:

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 -we 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 your.

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_on 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_into 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 2145) 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_with the. 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 Options

ALUA configurations is actually from the LUNs in combination with TPGs. So you’re able to checklist these types of setup, you might run the next demand:

An illustration off a keen EMC VNX otherwise CLARiiON CX Assortment

This output shows the Shop Assortment 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 Array Style of Equipment Config line, wrapped for readability, which includes a number of parts:The first set of curly brackets, , includes initiator membership–particular setting. This will be particular to help you EMC VNX together with CLARiiON family of arrays. Within place, several options are detailed:

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 Form is set to 4, which enables ALUA for this initiator. (You can find more details on this in Chapter 7.)

ipfilter=for 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 check out the post right here 7.)

The new ALUA AAS administration mode choices are enclosed when you look at the the next set of curly supports, inside that’s another nested group of curly mounts on the TPG’s AAS arrangement. They are ALUA AAS administration setting possibilities:

Explicit_allow=to 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).