vsphere-esxi-vcenter-server-55-storage-guide

vSphere Storage2 Assign the MASK_PATH plug-in to a path by creating a new claim rule for the plug-in.esxcli --server=server_name storage core claimrule add -P MASK_PATH3 Load the MASK_PATH claim rule into your system.esxcli --server=server_name storage core claimrule load4 Verify that the MASK_PATH claim rule was added correctly.esxcli --server=server_name storage core claimrule list5 If a claim rule for the masked path exists, remove the rule.esxcli --server=server_name storage core claiming unclaim6 Run the path claiming rules.esxcli --server=server_name storage core claimrule runAfter you assign the MASK_PATH plug-in to a path, the path state becomes irrelevant and is no longermaintained by the host. As a result, commands that display the masked path's information might show thepath state as dead.Example: Masking a LUNIn this example, you mask the LUN 20 on targets T1 and T2 accessed through storage adapters vmhba2 andvmhba3.1 #esxcli --server=server_name storage core claimrule list2 #esxcli --server=server_name storage core claimrule add -P MASK_PATH -r 109 -t location -Avmhba2 -C 0 -T 1 -L 20#esxcli --server=server_name storage core claimrule add -P MASK_PATH -r 110 -t location -Avmhba3 -C 0 -T 1 -L 20#esxcli --server=server_name storage core claimrule add -P MASK_PATH -r 111 -t location -Avmhba2 -C 0 -T 2 -L 20#esxcli --server=server_name storage core claimrule add -P MASK_PATH -r 112 -t location -Avmhba3 -C 0 -T 2 -L 203 #esxcli --server=server_name storage core claimrule load4 #esxcli --server=server_name storage core claimrule list5 #esxcli --server=server_name storage core claiming unclaim -t location -A vmhba2#esxcli --server=server_name storage core claiming unclaim -t location -A vmhba36 #esxcli --server=server_name storage core claimrule runUnmask PathsWhen you need the host to access the masked storage device, unmask the paths to the device.In the procedure, --server=server_name specifies the target server. The specified target server prompts youfor a user name and password. Other connection options, such as a configuration file or session file, aresupported. For a list of connection options, see Getting Started with vSphere Command-Line Interfaces.PrerequisitesInstall vCLI or deploy the vSphere Management Assistant (vMA) virtual machine. See Getting Started withvSphere Command-Line Interfaces. For troubleshooting, run esxcli commands in the ESXi Shell.232 VMware, Inc.