Beruflich Dokumente
Kultur Dokumente
(//www.facebook.com/sharer.php?u=http%3A%2F%2Fwww.gabesvirtualworld.com%2Fchanging-satp-claimrules-specific-storage-configurations%2F)
(//twitter.com/intent/tweet?text=Changing%20SATP%20Claimrules%20for%20specific%20storage%20configurations&url=http%3A%2F%2Fwww.gabesvirtualworld.com%2Fchanging-satp-claimrules-specific-storage-
(//plus.google.com/share?url=http%3A%2F%2Fwww.gabesvirtualworld.com%2Fchanging-satp-claimrules-specific-storage-configurations%2F)
(//pinterest.com
At my current customer I was upgrading their vSphere 4.1 environment to vSphere 5.5. When installing and configuring the first ESXi 5.5 host, I noticed a difference in the Path Selection Policy (PSP)
between the ESX 4.1 hosts and the ESXi 5.5 host. Each host is connected to two Hitachi storage arrays, each a different model. In the current 4.1 config a general setting is used to have both arrays use
Round Robin:
Because of the above rule in the ESX 4.1 hosts, all storage that is not captured by the existing rule sets, will be set to Round Robin (VMW_PSP_RR). Although applying this rule to my ESXi 5.5 host, would
solve the problem for me on short term, I could imagine running into an issue when the customer would attach a third storage that didn’t required Round Robin, but would then somehow still default to it,
because of this “catch-all” rule.
To write a very specific rule for this storage array I would need to find out what vendor and model this storage array is according to ESXi. This was actually the hardest part, since I was using the wrong
command at first, but with some help of the VMware Community (https://communities.vmware.com/message/2325041) and specifically Tom Verhaeg (http://www.tomverhaeg.nl), I found the right command.
Let me take you through the steps.
COMMAND:
RESULT:
naa.60060e80132892005020289200001001
Device Display Name: HITACHI Fibre Channel Disk (naa.60060e80132892005020289200001001)
Storage Array Type: VMW_SATP_DEFAULT_AA
Storage Array Type Device Config: SATP VMW_SATP_DEFAULT_AA does not support device configuration.
Path Selection Policy: VMW_PSP_FIXED
Path Selection Policy Device Config: {preferred=vmhba1:C0:T0:L37;current=vmhba1:C0:T0:L37}
Path Selection Policy Device Custom Config:
Working Paths: vmhba1:C0:T0:L37
Is Local SAS Device: false
Is Boot USB Device: false
The next step is to find out what storage array Vendor and Model type this LUN is coming from, because we need this info to create a new SATP claiming rule. Running the following command, shows that
we’re working with Vendor = Hitachi and Model = OPEN-V.
COMMAND:
RESULT:
naa.60060e80132892005020289200001001
Display Name: HITACHI Fibre Channel Disk (naa.60060e80132892005020289200001001)
Has Settable Display Name: true
Size: 1048576
Device Type: Direct-Access
Multipath Plugin: NMP
Devfs Path: /vmfs/devices/disks/naa.60060e80132892005020289200001001
Vendor: HITACHI
Model: OPEN-V
Revision: 5001
SCSI Level: 4
Is Pseudo: false
Status: on
Is RDM Capable: true
Is Local: false
Is Removable: false
Is SSD: false
Is Offline: false
Is Perennially Reserved: false
Queue Full Sample Size: 0
Queue Full Threshold: 0
Thin Provisioning Status: yes
Attached Filters: VAAI_FILTER
VAAI Status: supported
Other UIDs: vml.020025000060060e801328920050202892000010014f50454e2d56
Is Local SAS Device: false
Is Boot USB Device: false
No of outstanding IOs with competing worlds: 32
www.gabesvirtualworld.com/changing-satp-claimrules-specific-storage-configurations/ 1/4
4/12/2019 Changing SATP Claimrules for specific storage arrays GabesVirtualWorld
Before creating the new rule, I wanted to check the current SATP rule list, so I could also check after creating the rule, if there was a change. For easy of reading I only display the results here that were
important to me:
COMMAND:
RESULT:
COMMAND:
RESULT:
What the admin of this environment did in the past, was changing this “overall” default to VMW_PSP_RR, which is not the approach I want to take. The above table explains why the ESXi 5.5 host is now
working with the VMW_PSP_FIXED policy. We’re now ready to change the SATP rule using “HITACHI” as storage Vendor, “OPEN-V” as model type. We’re telling the ESXi to use VMW_SATP_DEFAULT_AA
with a PSP of “VMW_PSP_RR” when Venor and Model match our specification:
COMMANDS:
esxcli storage nmp satp rule add -V HITACHI -M "OPEN-V" -P VMW_PSP_RR -s VMW_SATP_DEFAULT_AA
esxcli storage core claimrule load
To check how this worked out, we check the satp rule list again:
COMMAND:
COMMAND:
RESULT:
naa.60060e80132892005020289200001001
Device Display Name: HITACHI Fibre Channel Disk (naa.60060e80132892005020289200001001)
Storage Array Type: VMW_SATP_DEFAULT_AA
Storage Array Type Device Config: SATP VMW_SATP_DEFAULT_AA does not support device configuration.
Path Selection Policy: VMW_PSP_RR
Path Selection Policy Device Config: {policy=rr,iops=1000,bytes=10485760,useANO=0; lastPathIndex=0: NumIOsPending=0,numBytesPending=0}
Path Selection Policy Device Custom Config:
Working Paths: vmhba1:C0:T0:L37, vmhba0:C0:T0:L37
Is Local SAS Device: false
Is Boot USB Device: false
WARNING: Changing Path Selection Policies or SATP rules, should only be done when you are 100% sure of what you’re about to do. Always check the VMware HCL to see what the prefered policy is for
your storage array in combination with firmware and ESXi version. Also check what your vendor’s documentation recommends.
www.gabesvirtualworld.com/changing-satp-claimrules-specific-storage-configurations/ 2/4
4/12/2019 Changing SATP Claimrules for specific storage arrays GabesVirtualWorld
(http://www.gabesvirtualworld.com/tag/vmw_psp_rr/), VMW_SATP_DEFAULT_AA (http://www.gabesvirtualworld.com/tag/vmw_satp_default_aa/). permalink (http://www.gabesvirtualworld.com/changing-satp-claimrules-
specific-storage-configurations/).
LOG IN WITH
OR SIGN UP WITH DISQUS ?
Name
Great article, it answered most of what I'm trying to do, though I am still looking
on how to configure the No of outstanding IOs with competing worlds using an
SATP rule with a default value of 256 for a specific storage vendor.
Any ideas?
Thanks!
△ ▽ • Reply • Share ›
Gabrie
△ ▽ • Reply • Share ›
I'm familiar with this blog post from Cormac but unfortunately it
does not answer my question. What I'm trying to do is to set a
default value of 256 to the Disk.SchedNumReqOutstanding
parameter for all LUNs from a specific vendor using SATP or any
other alternative that does not require manual interfere. Are you
familiar with a way to achieve this?
Thanks,
Matan
△ ▽ • Reply • Share ›
How to move VMware Single Sign On DELL XPS 13 – 9365 and network
(SSO) database disconnect in sleep mode
8 comments • 7 years ago 2 comments • 2 years ago
Gabrie van Zanten — My guess is that Gabrie van Zanten — Well this worked
the ssocli commands make a change for me, since when I'm at work I never
INSIDE the database. And the change want the laptop go into sleep mode.
Cannot open the disk and could not Did you know, no VMotion when HA
open change tracking file network partitioned
16 comments • 5 years ago 2 comments • 6 years ago
Richard Ryder — Ran into this issue Roy — This issue has little to do with
when upgrading the virtual hardware any restrictions imposed by VMware.
from 7 to 10. Thanks for saving me Rather, it's the fact that your partitioned
✉S d
Search my blog
Search...
My Sponsors
Advertise Here
www.gabesvirtualworld.com/changing-satp-claimrules-specific-storage-configurations/ 3/4
4/12/2019 Changing SATP Claimrules for specific storage arrays GabesVirtualWorld
Veeam
(index.php?
adclick=4)
Recent Posts
DELL XPS 13 – 9365 and network disconnect in sleep mode (http://www.gabesvirtualworld.com/dell-xps-13-9365-network-disconnect-sleep-mode/) 7 September, 2017
vCenter: How was that account locked out? (http://www.gabesvirtualworld.com/vcenter-account-locked/) 19 April, 2017
Datacenter Migration with VEEAM Backup & Replication and PowerShell (http://www.gabesvirtualworld.com/datacenter-migration-veeam-backup-replication-powershell/) 20 January, 2017
Gabes Virtual World (http://gabesvirtualworld.com.webhosting101.transurl.nl/) All rights reserved. Theme by Colorlib (http://colorlib.com/wp/) Powered by WordPress (http://wordpress.org/)
www.gabesvirtualworld.com/changing-satp-claimrules-specific-storage-configurations/ 4/4