Loading

×Sorry to interrupt
CSS Error

Refresh

Cookie Preference Center

General Information on cookies

When you visit our website, we use cookies to ensure that we give you the best experience. This information does not usually directly identify you, but it can give you a more personalized web experience. Because we respect your right to privacy, you can choose not to allow some types of cookies by clicking on the different category headings to find out more and change your settings. However, blocking some types of cookies may impact your experience on the site and the services we are able to offer. Further information can be found in our

Cookie Policy.

Strictly Necessary

Strictly Necessary

Always Active

Strictly Necessary

Strictly necessary cookies are always enabled since they are essential for our website to function. They enable core functionality such as security, network management, and website accessibility. You can set your browser to block or alert you about these cookies, but this may affect how the website functions. For more information please visit www.aboutcookies.org or www.allaboutcookies.org.

Cookie Details‎

Performance

Performance

Performance

Performance cookies are used to analyze the user experience to improve our website by collecting and reporting information on how you use it. They allow us to know which pages are the most and least popular, see how visitors move around the site, optimize our website and make it easier to navigate.

Cookie Details‎

Please confirm your settings by refreshing the page.

Functional

Functional

Functional

Functional cookies help us keep track of your past browsing choices so we can improve usability and customize your experience. These cookies enable the website to remember your preferred settings, language preferences, location and other customizable elements such as font or text size. If you do not allow these cookies, then some or all of these services may not function properly.

Cookie Details‎

Advertising

Advertising

Advertising

Advertising cookies are used to send you relevant advertising and promotional information. They may be set through our site by third parties to build a profile of your interests and show you relevant advertisements on other sites. These cookies do not directly store personal information, but their function is based on uniquely identifying your browser and internet device.

Cookie Details‎

Advertising Cookies

Consent Leg.Interest

Select All Vendors

Select All Vendors

Select All Hosts

Select All

Clear Filters

Information storage and access

Apply

Confirm My Choices Reject All Allow All

My Subscriptions

Loading

Knowledge Base

Changing a LUN to use a different Path Selection Policy (PSP) (1036189)

Last Updated: 2/28/2024Categories: How toTotal Views: 90854Language:
Chinese (Simplified)JapaneseEnglish

2 like this article

Subscribe to get an email
newsletter with new updates

2 people found this helpful Please provide article feedback:

Details

Based on your storage array vendor's best practices, you have configured your ESX and ESXi hosts with Round Robin Path Selection Policy (VMW_PSP_RR) for your storage array.

However, in some configurations, such as MSCS using shared storage RDMs (Raw Device Mappings), you need to change the Path Selection Policy (PSP) because Round Robin PSP is not supported for MSCS Clustering prior to vSphere 5.5. For more information see MSCS support enhancements in vSphere 5.5 (2052238)

Solution

To work around the issue, change the PSP for the LUNs used by the MSCS cluster's RDMs to a PSP other than VMW_PSP_RR. The choice of PSP must be relevant to the Storage Array Type. For example, if the array is Active/Passive, do not use FIXED PSP, use MRU PSP.

To change a LUN to use a different PSP:

Log in to the ESX host's terminal directly, or by SSH.

For ESX hosts, press Alt+F1 in the console or your remote System Management Interface and log in as root. For more information, see Connecting to an ESX host using an SSH client (1019852).

For ESXi hosts, see Using Tech Support Mode in ESXi 4.1 and ESXi 5.x (1017910).

Identify the RDM file name for each shared storage used by the virtual machines in the MSCS cluster nodes.

Note: This step requires that the virtual machine be powered off first. If you do not power off the virtual machine, you receive the error, Device or resource busy. This applies to all virtual machines accessing the LUN.

#cd /vmfs/volumes/Clusters_datastore/node1
#fgrep scsi1 *.vmx |grep fileName
scsi1:0.fileName = "/vmfs/volumes/4d8008a2-9940968c-04df-001e4f1fbf2a/node1/quorum.vmdk"
scsi1:1.fileName = "/vmfs/volumes/4d8008a2-9940968c-04df-001e4f1fbf2a/node1/data.vmdk"

The last two lines of the output show the path to the file and the file names of the shared storage for 2 RDMs.

You use the text in double quotes in some of the steps of this article.

Identify the logical device name mapped by the first RDM (the quorum disk above).

#vmkfstools -q /vmfs/volumes/4d8008a2-9940968c-04df-001e4f1fbf2a/node1/quorum.vmdk
Disk /vmfs/volumes/4d8008a2-9940968c-04df-001e4f1fbf2a/node1/quorum.vmdk is a Passthrough Raw Device Mapping
Maps to: vml. 02000100006006016055711d00cff95e65664ee011524149442035

Identify the LUN ID (NAA ID) represented by the logical device name (prefixed with vml listed in red above)

#esxcfg-scsidevs -l -d vml. 02000100006006016055711d00cff95e65664ee011524149442035 |grep Display
Display Name: DGC Fibre Channel Disk ( naa.6006016055711d00cff95e65664ee011)

Using the NAA ID identified in step 3, list the current PSP used by the LUN.

#esxcli nmp device list -d naa.6006016055711d00cff95e65664ee011 |grep PSP
Path Selection Policy: VMW_PSP_RR

For ESXi 5.x, the equivalent is:

#esxcli storage nmp device list -d naa.6006016055711d00cff95e65664ee011 |grep PSP

This output shows that the Path Selection Policy is VMW_PSP_RR

Change the policy to one relevant to the array type. This example uses MRU.

In ESXi/ESX 4.1, run this command:

# esxcli nmp device setpolicy -d naa.6006016055711d00cff95e65664ee011 --psp=VMW_PSP_MRU

In ESXi 5.x, run this command:

# esxcli storage nmp device set -d naa.6006016055711d00cff95e65664ee011 --psp=VMW_PSP_MRU

Verify that the change was successful

In ESX/ESXi 4.1, run this command:

# esxcli nmp device list -d naa.6006016055711d00cff95e65664ee011 |grep PSP
naa.6006016055711d00cff95e65664ee011
Path Selection Policy: VMW_PSP_MRU

In ESXi 5.x, run this command:

# esxcli storage nmp device list -d naa.6006016055711d00cff95e65664ee011 |grep PSP naa.6006016055711d00cff95e65664ee011

Repeat Steps 3 through 7 for each RDM identified in Step 2.

Repeat above steps for each node in the cluster on other ESXi/ESX hosts on which these nodes are running.

Additional Information

For translated versions of this article, see:

日本語: 異なるパス選択ポリシー (PSP) を使用するように LUN を変更する (2088815)

简体中文: 更改 LUN 以使用不同的路径选择策略 (PSP) (2097707)

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
Chinese (Simplified)JapaneseEnglish

Attachments

Additional Resources

KB
•
End Of General Availability of the Free vSphere Hypervisor (ESXi 7.x and 8.x) (2107518)

Result 1 of 1

Ask The Community

Get answers quickly from VMware experts in the community

Post Subject

CONTINUE IN COMMUNITIES

Related Products:

VMware vSphere ESXi

VMware vSphere ESXi

VMware ESX Server

Related Versions:

VMware vSphere ESXi 6.7

VMware vSphere ESXi 6.5

VMware vSphere ESXi 6.0

VMware vSphere ESXi 5.5

VMware vSphere ESXi 5.5

VMware vSphere ESXi 5.1

VMware vSphere ESXi 5.0

VMware ESXi 4.1.x Installable

VMware ESXi 4.1.x Embedded

VMware ESXi 4.0.x Installable

VMware ESXi 4.0.x Embedded

VMware ESX 4.1.x

VMware ESX 4.0.x

view all

Take Our Survey

Support Assistant