Use the esxcli commands to add a multipathing PSA claim rule to the set of claim rules on the system. For the new claim rule to be active, you first define the rule and then load it into your system.
Examples when you add a PSA claim rule include the following:
You load a new third-party MPP and must define the paths that this module claims.
You must enable the native HPP.
You cannot create rules where two different plug-ins claim paths to the same device. Your attempts to create these claim rules fail with a warning in vmkernel.log.
Install vCLI or deploy the vSphere Management Assistant (vMA) virtual machine. See Getting Started with vSphere Command-Line Interfaces. For troubleshooting, run esxcli commands in the ESXi Shell.
- To define a new claim rule, use the following command:
esxcli storage core claimrule add
The command takes the following options:
Adapter of the paths to use. Valid only if
Adds a claim rule based on its characteristics. The rule number is not required.
Channel of the paths to use. Valid only if
Claim rule class to use in this operation. You can specify
To configure hardware acceleration for a new array, add two claim rules, one for the VAAI filter and another for the VAAI plug-in. See Add Hardware Acceleration Claim Rules for detailed instructions.
UID of the device. Valid only when
Driver for the HBA of the paths to use. Valid only if
Force claim rules to ignore validity checks and install the rule anyway.
Override protection of reserved rule ID ranges.
Reserved claim rules are the rules with an ID below 100. You can use them to reassign local devices to specific plug-ins, for example, the NVMe device to HPP.
Run this command if this advanced user variable is not set to 1.
iSCSI Qualified Name for the target. Valid only when
LUN of the paths. Valid only if
LUN ID must not be higher than the value of the advanced configuration option /Disk/MaxLUN.
Model of the paths to use. Valid only if
Valid values are values of the Model string from the SCSI inquiry string. Run
vicfg-scsidevs <conn_options> -lon each device to see model string values.
PSA plug-in to use. The values are
HPP. Third parties can also provide their own PSA plug-ins. Required.
Rule ID to use. The rule ID indicates the order in which the claim rule is to be evaluated. User-defined claim rules are evaluated in numeric order starting with 101.
You can run esxcli storage core claimrule list to determine which rule IDs are available.
Target of the paths to use. Valid only if
Transport of the paths to use. Valid only if
transport. The following values are supported.
block— block storage
fc— Fibre Channel
iscsi— not currently used
ide— IDE storage
sas— SAS storage
sata— SATA storage
usb— USB storage
Type of matching to use for the operation. Valid values are the following. Required.
Vendor of the paths to use. Valid only if
Valid values are values of the vendor string from the SCSI inquiry string. Run
vicfg-scsidevs <conn_options> -lon each device to see vendor string values.
World-Wide Node Number for the target.
World-Wide Port Number for the target.
Use the array reported values to construct the XCOPY command to be sent to the storage array. This applies to VAAI claim rules only.
Use multiple segments when issuing an XCOPY request. Valid only if
Maximum data transfer size in MB when you use a transfer size different than array reported. Valid only if
Maximum transfer size in KiB for the XCOPY commands when you use a transfer size different than array reported. Valid only if
- To load the new claim rule into your system, use the following command:
esxcli storage core claimrule load
This command loads all newly created multipathing claim rules from the esx.conf configuration file into the VMkernel. The command has no options.
- To apply claim rules that are loaded, use the following command:
esxcli storage core claimrule run
The command takes the following options:
If --type is location, name of the HBA for the paths to run the claim rules on. To run claim rules on paths from all adapters, omit this option.
location, value of the SCSI channel number for the paths to run the claim rules on. To run claim rules on paths with any channel number, omit this option.
Claim rule class to use in this operation.
UID of the device.
location, value of the SCSI LUN for the paths to run claim rules on. To run claim rules on paths with any LUN, omit this option.
path, this option indicates the unique path identifier (UID) or the runtime name of a path to run claim rules on.
location, value of the SCSI target number for the paths to run claim rules on. To run claim rules on paths with any target number, omit this option.
Type of claim to perform. By default, uses
all, which means claim rules run without restriction to specific paths or SCSI addresses. Valid values are
You can use this option only if you also use
If the option is included, the claim waits for paths to settle before running the claim operation. In that case, the system does not start the claiming process until it is likely that all paths on the system have appeared before starting the claim process.
After the claiming process has started, the command does not return until device registration has completed.
If you add or remove paths during the claiming or the discovery process, this option might not work correctly.
Defining Multipathing Claim Rules
In the following example, you add and load rule # 500. The rule claims all paths with the NewMod model string and the NewVend vendor string for the NMP plug-in.
# esxcli storage core claimrule add -r 500 -t vendor -V NewVend -M NewMod -P NMP
# esxcli storage core claimrule load
After you run the esxcli storage core claimrule list command, you can see the new claim rule appearing on the list.
The following output indicates that the claim rule 500 has been loaded into the system and is active.
Rule Class Rule Class Type Plugin Matches ... ... ... ... ... ... MP 500 runtime vendor NMP vendor=NewVend model=NewMod MP 500 file vendor NMP vendor=NewVend model=NewMod