Inside the Chapter 5, I demonstrated you the way so you’re able to identify all the fresh new SATP legislation

I got to break this new screenshots on the four quadrants to ensure that I will reveal the stuff of one’s efficiency. Right here, I’ve attempted to trim it down and number only the lines I want to inform you. To accomplish this, I made use of the following command:

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 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_for 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_to 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_for 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_for 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.

Identifying Devices’ ALUA Setup

ALUA configurations are from the LUNs in conjunction with TPGs. So you can listing such options, you might manage the second demand:

An example off an EMC VNX or CLARiiON CX Variety

This output shows the Shop Range Sorts 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 Storage Number Variety of Tool Config line, wrapped for readability, which includes a number of parts:The first set of curly brackets, , includes initiator registration–specific configuration. This might be certain to EMC VNX while the CLARiiON group of arrays. Contained in this put, several 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 Sugar Daddy dating only Failover Function 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.)

New ALUA AAS government form options are closed from inside the the next set of curly supports, within that is some other nested group of curly mounts on TPG’s AAS arrangement. These are the ALUA AAS government mode possibilities:

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