I got to-break the brand new screenshots into five quadrants so I could let you know all of the content of your yields. Right here, I’ve made an effort to trim they off and you can listing only the traces I must let you know. To do so, We made use of the following the order:
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_towards.
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_with 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_into.
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_to 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 http://www.datingmentor.org/bbw-dating/. 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.
Determining Devices’ ALUA Settings
ALUA configurations are from the LUNs in conjunction with TPGs. So you’re able to checklist this type of options, you could potentially focus on the next demand:
An illustration out-of an enthusiastic EMC VNX or CLARiiON CX Assortment
This output shows the Shops Selection Style 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 Selection Types of Equipment Config line, wrapped for readability, which includes a number of parts:The first set of curly brackets, , comes with initiator registration–particular setting. This is specific so you can EMC VNX while the CLARiiON family of arrays. In this put, a couple of choices are listed:
navireg=with 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 7.)
The latest ALUA AAS government form choices are sealed when you look at the the next number of curly mounts, contained in this that is another nested set of curly supports into TPG’s AAS configuration. They are ALUA AAS management function options:
Explicit_allow=into 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).