- Native Multipathing
- Storage Array Type Plug-in (SATP)
- Path Selection Plugin (PSP)
- Third-Party Plug-ins
- Multipathing Plugins (MPPs)
- Anatomy of PSA Components
- I/O Flow Through PSA and NMP
- Listing Multipath Details
- Claim Rules
- MP Claim Rules
- Plug-in Registration
- SATP Claim Rules
- Modifying PSA Plug-in Configurations Using the UI
- Modifying PSA Plug-ins Using the CLI
- Summary
This chapter is from the book
This chapter is from the book
This chapter is from the book
MP Claim Rules
The first set of claim rules defines which MPP claims which devices. Figure 5.25 shows the default MP claim rules.
)
Figure 5.25. Listing MP Claim Rules
The command to list these rules is
esxcli storage core claimrule list
The namespace here is for the Core Storage because the MPP definition is done on the PSA level. The output shows that this rule class is MP, which indicates that these rules define the devices’ association to a specific multipathing plug-in.
There are two plugins specified here: NMP and MASK_PATH. I have already discussed NMP in the previous sections. The MASK_PATH plug-in is used for masking paths to specific devices and is a replacement for the deprecated Legacy Multipathing LUN Masking vmkernel parameter. I provide some examples in the “Modifying PSA Plug-in Configurations Using the UI” section.
Table 5.9 lists each column name in the ouput along with an explanation of each column.
Table 5.9. Explanation of Claim Rules Fields
|
Column Name |
Explanation |
|
Rule Class |
The plugin class for which this claim rule set is defined. This can be MP, Filter, or VAAI. |
|
Rule |
The rule number. This defines the order the rules are loaded. Similar to firewall rules, the first match is used and supersedes rules with larger numbers. |
|
Class |
The value can be runtime or file. A value of file means that the rule definitions were stored to the configuration files (more on this later in this section). A value of Runtime means that the rule was read from the configuration files and loaded into memory. In other words, it means that the rule is active. If a rule is listed as file only and no runtime, the rule was just created but has not been loaded yet. Find out more about loading rules in the next section. |
|
Type |
The type can be vendor, model, transport, or driver. See the explanation in the “Claim Rules” section. |
|
Plugin |
The name of the plug-in for which this rule was defined. |
|
Matches |
This is the most important field in the rule definition. This column shows the “Type” specified for the rule and its value. When the specified type is vendor, an additional parameter, model, must be used. The model string must be an exact string match or include an * as a wild card. You may use a ^ as “begins with” and then the string followed by an *—for example, ^OPEN-*. |
The highest rule number in any claim rules set is 65535. It is assigned here to a Catch-All rule that claims devices from “any” vendor with “any” model string. It is placed as the last rule in the set to allow for lower numbered rules to claim their specified devices. If the attached devices have no specific rules defined, they get claimed by NMP.
Figure 5.26 is an example of third-party MP plug-in claim rules.
)
Figure 5.26. Listing EMC PowerPath/VE claim rules.
Here you see that rules number 250 through 320 were added by PowerPath/VE, which allows PowerPath plug-in to claim all the devices listed in Table 5.10.
Table 5.10. Arrays Claimed by PowerPath
|
Storage Array |
Vendor |
Model |
|
EMC CLARiiON Family |
DGC |
Any (* is a wild card) |
|
EMC Symmetrix Family |
EMC |
SYMMETRIX |
|
EMC Invista |
EMC |
Invista |
|
HITACHI |
HITACHI |
Any |
|
HP |
HP |
Any |
|
HP EVA HSV111 family (Compaq Branded) |
HP |
HSV111 (C) COMPAQ |
|
EMC Celerra |
EMC |
Celerra |
|
IBM DS8000 family |
IBM |
2107900 |