{"id":548,"date":"2023-05-16T20:10:47","date_gmt":"2023-05-16T19:10:47","guid":{"rendered":"https:\/\/www.shakral.de\/blog\/?p=548"},"modified":"2023-06-06T08:27:34","modified_gmt":"2023-06-06T07:27:34","slug":"satp-regel-fuer-vsphere-esxi-erstellen","status":"publish","type":"post","link":"https:\/\/www.shakral.de\/blog\/2023\/05\/16\/satp-regel-fuer-vsphere-esxi-erstellen\/","title":{"rendered":"SATP Regel f\u00fcr vSphere ESXi erstellen"},"content":{"rendered":"<p class=\"wp-block-paragraph\">HPE hat f\u00fcr alle Storage-System der 3PAR Familie einen Befehl im Handbuch, dass die richtigen Round-Robin Einstellungen automatisch anwenden, sobald sich ein Datastore \u00fcber SCSI-Informationen als 3PAR-VV zu erkennen gibt. <\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Hier der Befehl f\u00fcr bis ESXi 7.0 U1 und \u00e4lter<\/p>\n\n\n<div class=\"wp-block-syntaxhighlighter-code \"><pre class=\"brush: plain; title: ; notranslate\" title=\"\">\nesxcli storage nmp satp rule add \u2013o &quot;throttle_sll&quot; -s &quot;VMW_SATP_ALUA&quot; -P &quot;VMW_PSP_RR&quot; -O &quot;policy=latency&quot; -c &quot;tpgs_on&quot; -V &quot;3PARdata&quot; -M &quot;VV&quot; -e &quot;HPE Custom iSCSI\/FC\/FCoE ALUA Rule&quot;\n<\/pre><\/div>\n\n\n<p class=\"wp-block-paragraph\">Beispiel f\u00fcr ESXi 6.5 &#8211; 6.7U1<\/p>\n\n\n<div class=\"wp-block-syntaxhighlighter-code \"><pre class=\"brush: plain; title: ; notranslate\" title=\"\">\nesxcli storage nmp satp rule add -s &quot;VMW_SATP_ALUA&quot; -P &quot;VMW_PSP_RR&quot; -O iops=1 -c &quot;tpgs_on&quot; -V &quot;3pardata&quot; -M &quot;VV&quot; -e &quot;HP Custom SCSI\/FC\/FCoE ALUA Rule\u201d\n<\/pre><\/div>\n\n\n<p class=\"wp-block-paragraph\">Da dies nicht alle Hersteller so angeben, hier ein kleiner Guide, wie dieser Befehl selbst zu bauen ist und woher man die notwendigen Informationen erh\u00e4lt. Die am Beispiel einer HPE MSA 2060.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Aufbau der Regel<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">esxcli storage nmp satp rule add<\/p>\n\n\n\n<figure class=\"wp-block-table\"><table><thead><tr><th>CLI-Abk\u00fcrzung<\/th><th>Beschreibung<\/th><th>Parameter<\/th><th>Kommentar<\/th><\/tr><\/thead><tbody><tr><td>-S<\/td><td>welche SATP dient als Basis<\/td><td>VMW_SATP_ALUA<\/td><td>Info aus dem Array Handbuch<\/td><\/tr><tr><td>-P<\/td><td>welche Load-Balancing PSP wird verwendet<\/td><td>VMW_PSP_RR<\/td><td>Info aus dem Array Handbuch<\/td><\/tr><tr><td>-O<\/td><td>Optionen f\u00fcr das Load-Balancing<\/td><td>iops=1<\/td><td>optionale Info aus dem Array Handbuch<\/td><\/tr><tr><td>-c<\/td><td>claim-option<\/td><td>tpgs_on<\/td><td><br>optionale Info aus dem Array Handbuch<\/td><\/tr><tr><td>-V<\/td><td>Array Hersteller<\/td><td>3pardata<\/td><td>aus den ausgelesenen SCSI-Informationen<\/td><\/tr><tr><td>-M<\/td><td>Model-Informationen<\/td><td>VV<\/td><td>aus den ausgelesenen SCSI-Informationen<\/td><\/tr><tr><td>-e<\/td><td>Beschreibung der Regel<\/td><td>HP Custom SCSI\/FC\/FCoE ALUA Rule<\/td><td>Beschreibung der Regel<\/td><\/tr><\/tbody><\/table><figcaption class=\"wp-element-caption\">Link zu ESXCLI Reference <a rel=\"noreferrer noopener\" href=\"https:\/\/developer.vmware.com\/docs\/11743\/esxi-7-0-esxcli-command-reference\" target=\"_blank\">Guide<\/a> &#8211; <a rel=\"noreferrer noopener\" href=\"https:\/\/developer.vmware.com\/docs\/11743\/esxi-7-0-esxcli-command-reference\/namespace\/esxcli_storage.html\" target=\"_blank\">SATP Rule Kapitel<\/a> &#8211; <a href=\"https:\/\/vdc-download.vmware.com\/vmwb-repository\/dcr-public\/24be7af7-d9cd-48d9-bab8-8c91614be19d\/0ca33108-8017-4b40-86b9-f066456894ea\/doc\/GUID-0DE75E3B-29B7-41C1-93A0-D5B1373470E3.html\" target=\"_blank\" rel=\"noreferrer noopener\">old<\/a><\/figcaption><\/figure>\n\n\n\n<h2 class=\"wp-block-heading\">SCSI-Informationen auslesen<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">\u00fcber die ESXCLI k\u00f6nnen wir die SCSI-Informationen aller Storage-Devices anzeigen lassen, wenn wir davor schon eine Device-Namen haben, k\u00f6nnen wir auch diesen gezielt anzeigen lassen<\/p>\n\n\n<div class=\"wp-block-syntaxhighlighter-code \"><pre class=\"brush: plain; title: ; notranslate\" title=\"\">\nesxcli storage core device list\n<\/pre><\/div>\n\n\n<p class=\"wp-block-paragraph\">F\u00fcr eine bestimmtes Device<\/p>\n\n\n<div class=\"wp-block-syntaxhighlighter-code \"><pre class=\"brush: plain; highlight: [1,9,10]; title: ; notranslate\" title=\"\">\nesxcli storage core device list -d naa.600c0ff00053171a492541600100xxxx\nnaa.600c0ff00053171a492541600100xxxx\n   Display Name: HPE Fibre Channel Disk (naa.600c0ff00053171a492541600100xxxx)\n   Has Settable Display Name: true\n   Size: 19072\n   Device Type: Direct-Access\n   Multipath Plugin: NMP\n   Devfs Path: \/vmfs\/devices\/disks\/naa.600c0ff00053171a492541600100xxxx\n   Vendor: HPE\n   Model: MSA 2060 FC\n   Revision: I110\n   SCSI Level: 6\n   Is Pseudo: false\n   Status: on\n   Is RDM Capable: true\n   Is Local: false\n   Is Removable: false\n   Is SSD: false\n   Is VVOL PE: false\n   Is Offline: false\n   Is Perennially Reserved: false\n   Queue Full Sample Size: 0\n   Queue Full Threshold: 0\n   Thin Provisioning Status: yes\n   Attached Filters:\n   VAAI Status: supported\n   Other UIDs: vml.0200020000600c0ff00053171a49254160010000004d5341203230\n   Is Shared Clusterwide: true\n   Is SAS: false\n   Is USB: false\n   Is Boot Device: false\n   Device Max Queue Depth: 64\n   No of outstanding IOs with competing worlds: 32\n   Drive Type: unknown\n   RAID Level: unknown\n   Number of Physical Drives: unknown\n   Protection Enabled: false\n   PI Activated: false\n   PI Type: 0\n   PI Protection Mask: NO PROTECTION\n   Supported Guard Types: NO GUARD SUPPORT\n   DIX Enabled: false\n   DIX Guard Type: NO GUARD SUPPORT\n   Emulated DIX\/DIF Enabled: false\n\n<\/pre><\/div>\n\n\n<h2 class=\"wp-block-heading\">Zusammensetzung der MSA-Regel <\/h2>\n\n\n\n<h3 class=\"wp-block-heading\">Informationen aus dem MSA-Handbuch<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Screenshot aus dem Dokument &#8222;HPE MSA Storage Configuration and Best Practices for VMware vSphere&#8220;<\/p>\n\n\n\n<h5 class=\"wp-block-heading\">Seite 30<\/h5>\n\n\n\n<figure class=\"wp-block-image size-full\"><img loading=\"lazy\" decoding=\"async\" width=\"893\" height=\"325\" src=\"https:\/\/www.shakral.de\/blog\/wp-content\/uploads\/2023\/05\/image-1.png\" alt=\"\" class=\"wp-image-552\" srcset=\"https:\/\/www.shakral.de\/blog\/wp-content\/uploads\/2023\/05\/image-1.png 893w, https:\/\/www.shakral.de\/blog\/wp-content\/uploads\/2023\/05\/image-1-300x109.png 300w, https:\/\/www.shakral.de\/blog\/wp-content\/uploads\/2023\/05\/image-1-768x280.png 768w\" sizes=\"auto, (max-width: 893px) 100vw, 893px\" \/><\/figure>\n\n\n\n<h5 class=\"wp-block-heading\">Seite 50<\/h5>\n\n\n\n<figure class=\"wp-block-image size-full\"><img loading=\"lazy\" decoding=\"async\" width=\"848\" height=\"324\" src=\"https:\/\/www.shakral.de\/blog\/wp-content\/uploads\/2023\/05\/image.png\" alt=\"\" class=\"wp-image-551\" srcset=\"https:\/\/www.shakral.de\/blog\/wp-content\/uploads\/2023\/05\/image.png 848w, https:\/\/www.shakral.de\/blog\/wp-content\/uploads\/2023\/05\/image-300x115.png 300w, https:\/\/www.shakral.de\/blog\/wp-content\/uploads\/2023\/05\/image-768x293.png 768w\" sizes=\"auto, (max-width: 848px) 100vw, 848px\" \/><\/figure>\n\n\n\n<p class=\"wp-block-paragraph\"><\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Informationssammlung<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Aus den Informationen aus dem Handbuch und der SCSI Inquiry setzt sich der Befehl aus folgenden Informationen zusammen.<\/p>\n\n\n\n<figure class=\"wp-block-table\"><table><thead><tr><th>CLI-Abk\u00fcrzung<\/th><th><strong>Beschreibung<\/strong><\/th><th>Paramter<\/th><th>Kommentar<\/th><\/tr><\/thead><tbody><tr><td>-S<\/td><td>welche SATP dient als Basis<\/td><td>VMW_SATP_ALUA<\/td><td>Info aus dem Array Handbuch, Seite 30<\/td><\/tr><tr><td>-P<\/td><td>welche Load-Balancing PSP wird verwendet<\/td><td>VMW_PSP_RR<\/td><td>Info aus dem Array Handbuch, Seite 50<\/td><\/tr><tr><td>-O<\/td><td>Optionen f\u00fcr das Load-Balancing<\/td><td>iops=1<\/td><td>Info aus dem Array Handbuch, Roundrobin wechselt den Pfad nach jedem einzelnen IO, siehe Seite 50<\/td><\/tr><tr><td>-V<\/td><td>Array Hersteller<\/td><td>HPE<\/td><td>aus den ausgelesenen SCSI-Informationen, Zeile 8<\/td><\/tr><tr><td>-M<\/td><td>Model-Informationen<\/td><td>MSA 2060 FC<\/td><td>aus den ausgelesenen SCSI-Informationen, Zeile 9<\/td><\/tr><tr><td>-e<\/td><td>Beschreibung der Regel<\/td><td>HPE MSA Claim<\/td><td>Beschreibung der Regel<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n<h3 class=\"wp-block-heading\">Fertiger Befehl<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">so sieht der zusammengesetzte Befehl aus<\/p>\n\n\n\n<pre class=\"EnlighterJSRAW\" data-enlighter-language=\"generic\" data-enlighter-theme=\"\" data-enlighter-highlight=\"\" data-enlighter-linenumbers=\"\" data-enlighter-lineoffset=\"\" data-enlighter-title=\"\" data-enlighter-group=\"\">esxcli storage nmp satp rule add --satp=VMW_SATP_ALUA --psp=VMW_PSP_RR -O=\"iops=1\" --vendor=\"HPE\" --model=\"MSA 2060 FC\" --description=\"HPE MSA Claim\"<\/pre>\n\n\n\n<h2 class=\"wp-block-heading\">Ergebnis<\/h2>\n\n\n<div class=\"wp-block-syntaxhighlighter-code \"><pre class=\"brush: plain; highlight: [1,6,11,12,18,19]; title: ; notranslate\" title=\"\">\n&#x5B;root@demohost:~] esxcli storage nmp device list\nnaa.600c0ff00053171a82445a6401000000\n   Device Display Name: HPE Fibre Channel Disk (naa.600c0ff00053171a82445a6401000000)\n   Storage Array Type: VMW_SATP_ALUA\n   Storage Array Type Device Config: {implicit_support=on; explicit_support=off; explicit_allow=on; alua_followover=on; action_OnRetryErrors=off; {TPG_id=1,TPG_state=ANO}{TPG_id=0,TPG_state=AO}}\n   Path Selection Policy: VMW_PSP_MRU\n   Path Selection Policy Device Config: Current Path=vmhba1:C0:T1:L6\n   Path Selection Policy Device Custom Config:\n   Working Paths: vmhba1:C0:T1:L6\n   Is USB: false\n&#x5B;root@demohost:~] esxcli storage nmp satp rule add --satp=VMW_SATP_ALUA --psp=VMW_PSP_RR -O=&quot;iops=1&quot; --vendor=&quot;HPE&quot; --model=&quot;MSA 2060 FC&quot; --description=&quot;HPE MSA Claim&quot;\n&#x5B;root@demohost:~] esxcli storage nmp device list\nnaa.600c0ff00053171a82445a6401000000\n   Device Display Name: HPE Fibre Channel Disk (naa.600c0ff00053171a82445a6401000000)\n   Storage Array Type: VMW_SATP_ALUA\n   Storage Array Type: VMW_SATP_ALUA\n   Storage Array Type Device Config: {implicit_support=on; explicit_support=off; explicit_allow=on; alua_followover=on; action_OnRetryErrors=off; {TPG_id=1,TPG_state=ANO}{TPG_id=0,TPG_state=AO}}\n   Path Selection Policy: VMW_PSP_RR\n   Path Selection Policy Device Config: {policy=rr,iops=1,bytes=10485760,useANO=0; lastPathIndex=0: NumIOsPending=0,numBytesPending=0}\n   Path Selection Policy Device Custom Config:\n   Working Paths: vmhba1:C0:T1:L9, vmhba2:C0:T1:L9\n   Is USB: false\n&#x5B;root@demohost:~]\n<\/pre><\/div>\n\n\n<h2 class=\"wp-block-heading\">ACHTUNG<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Der Befehl wirkt nur f\u00fcr neu hinzugef\u00fcgte Datastores, bestehende Datastores werden nicht angepasst. Dies kann h\u00e4ndisch angepasst werden oder durch einen Host-Neustart realisiert werden<\/p>","protected":false},"excerpt":{"rendered":"<p>HPE hat f\u00fcr alle Storage-System der 3PAR Familie einen Befehl im Handbuch, dass die richtigen Round-Robin Einstellungen automatisch anwenden, sobald sich ein Datastore \u00fcber SCSI-Informationen als 3PAR-VV zu erkennen gibt. Hier der Befehl f\u00fcr&#46;&#46;&#46;<\/p>\n","protected":false},"author":2,"featured_media":0,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_uag_custom_page_level_css":"","footnotes":""},"categories":[1,102,45,46,52],"tags":[109,56,53,104,110,105,106,107,108,103,76,111],"class_list":["post-548","post","type-post","status-publish","format-standard","hentry","category-allgemein","category-hpe","category-storage","category-virtualisierung","category-vmware","tag-claim","tag-esxcli","tag-esxi","tag-hpe","tag-iops","tag-msa","tag-multipathing","tag-psp","tag-satp","tag-storage","tag-vmware","tag-vsphere"],"uagb_featured_image_src":{"full":false,"thumbnail":false,"medium":false,"medium_large":false,"large":false,"1536x1536":false,"2048x2048":false,"thumb-small":false,"thumb-standard":false,"thumb-medium":false,"thumb-large":false,"thumb-xlarge":false,"thumb-xxlarge":false},"uagb_author_info":{"display_name":"Shakral","author_link":"https:\/\/www.shakral.de\/blog\/author\/shakral\/"},"uagb_comment_info":0,"uagb_excerpt":"HPE hat f\u00fcr alle Storage-System der 3PAR Familie einen Befehl im Handbuch, dass die richtigen Round-Robin Einstellungen automatisch anwenden, sobald sich ein Datastore \u00fcber SCSI-Informationen als 3PAR-VV zu erkennen gibt. Hier der Befehl f\u00fcr&#46;&#46;&#46;","_links":{"self":[{"href":"https:\/\/www.shakral.de\/blog\/wp-json\/wp\/v2\/posts\/548","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.shakral.de\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.shakral.de\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.shakral.de\/blog\/wp-json\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/www.shakral.de\/blog\/wp-json\/wp\/v2\/comments?post=548"}],"version-history":[{"count":10,"href":"https:\/\/www.shakral.de\/blog\/wp-json\/wp\/v2\/posts\/548\/revisions"}],"predecessor-version":[{"id":600,"href":"https:\/\/www.shakral.de\/blog\/wp-json\/wp\/v2\/posts\/548\/revisions\/600"}],"wp:attachment":[{"href":"https:\/\/www.shakral.de\/blog\/wp-json\/wp\/v2\/media?parent=548"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.shakral.de\/blog\/wp-json\/wp\/v2\/categories?post=548"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.shakral.de\/blog\/wp-json\/wp\/v2\/tags?post=548"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}