<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Gal Uzan on Medium]]></title>
        <description><![CDATA[Stories by Gal Uzan on Medium]]></description>
        <link>https://medium.com/@galuzan8?source=rss-359053f212af------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*7a79M6Vpa6xem3Cc2as8wA.jpeg</url>
            <title>Stories by Gal Uzan on Medium</title>
            <link>https://medium.com/@galuzan8?source=rss-359053f212af------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Fri, 20 Nov 2026 12:13:20 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@galuzan8/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[How to configure ISCSI on VMware ESXi with multiple interfaces]]></title>
            <link>https://medium.com/@galuzan8/how-to-configure-iscsi-on-vmware-esxi-with-multiple-interfaces-72c7d503c283?source=rss-359053f212af------2</link>
            <guid isPermaLink="false">https://medium.com/p/72c7d503c283</guid>
            <category><![CDATA[performance]]></category>
            <category><![CDATA[ethernet]]></category>
            <category><![CDATA[storage]]></category>
            <category><![CDATA[vmware]]></category>
            <category><![CDATA[networking]]></category>
            <dc:creator><![CDATA[Gal Uzan]]></dc:creator>
            <pubDate>Sun, 18 Dec 2022 13:23:16 GMT</pubDate>
            <atom:updated>2022-12-20T11:36:30.332Z</atom:updated>
            <content:encoded><![CDATA[<p>This article is a step by step guide on how to configure an ESXi using VMware best practice for ISCSI, as per this offical document: <a href="https://core.vmware.com/resource/best-practices-running-vmware-vsphere-iscsi">https://core.vmware.com/resource/best-practices-running-vmware-vsphere-iscsi</a></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*crmBmr5sXOkj44ZNzZY2fw.jpeg" /></figure><p>This article will include:</p><ol><li>How to configure the vSwitch and VMKernel</li><li>How to configure the ethernet switch</li><li>How to configure the ISCSI software Adapter, initiator and connect to the ISCSI targets</li><li>How to check the load is balanced</li></ol><p>For the sake of this article, I am using:</p><ul><li>vSphere 7.0.3 build 19234570</li><li>Dell PowerEdge R640 with ESXi running 7.0.3, 19193900</li><li>Dell PowerSwitch S5248F-ON running 10.4.3.1.154</li><li>PowerStoreT 5000</li></ul><p>Assuming you have a running vcenter, a clean ESXi host, your starting position should appear like so:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Zg4WQ5SRGxye5pXnUSIe7g.png" /></figure><p><strong>Step 1 — configure the vSwitch and VMKernel</strong></p><p>Create a new VMkernel adapter for each of your physical adapters you want to run ISCSI, in my case 2:</p><p>For the first VMkernel you create, you want to also create a new standard switch and configure the MTU to 9000.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/843/1*TVgjdqs_ixkmSflUx-rzbQ.png" /></figure><p>Add all the interfaces into Active adapters</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/868/1*ZxqZlgo8GyPHwtJdJnQosA.png" /></figure><p>You want to name this VMKernel as ISCSI-1, the second NIC will be ISCSI-2. you Also want to configure correct vlan as per the network you want ISCSI traffic to use.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/860/1*6fRpfLkDxdA-oYvwxoRLGQ.png" /></figure><p>Next, we configure an IP address for the VMkernel. The ISCSI traffic will later travel back and forth from theses adresses to your ISCSI targets. You also want to configure the gateway for each VMkernel, this is very important.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/861/1*_DT8xV6cq6nwDQkn1eO6cg.png" /></figure><p>Next step is to do the same for a second VMkernel adapter, this time we will use the existing vSwitch1</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/878/1*__jDUr2p76pZdrL0gFo1IQ.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/865/1*l4VRIz7czZdY9-IlS88FPQ.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/868/1*DcxNz06uxoGmGJ2UAdCjmg.png" /></figure><p>Overall, our network should now look like this:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*-OxEStu3TjE_yoPdbvTg3g.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/999/1*E0MS1LJCPaZKg8es45WDvA.png" /></figure><p>Next step is to assign each NIC to each VMkernel:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/698/1*Erb1hTjtsxN1Nb-5_IjopA.png" /></figure><p>Configure the teaming same as below:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/998/1*qJSKLQT0I968ezXE29JVXA.png" /></figure><p>And the same for the second VMkernel:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/999/1*pk9w0sv2QJIQ0kzYmk1HCg.png" /></figure><p><strong>Step 2 — configure the ethernet switch</strong></p><p>Now, what we want to do is get the switch configuration properly.</p><pre>SW16# show running-configuration interface ethernet 1/1/17<br>!<br>interface ethernet1/1/17<br> description 1-17_XXXXX_S1-P0<br> no shutdown<br> switchport mode trunk<br> switchport access vlan 1<br> switchport trunk allowed vlan XXXX<br> mtu 9214<br> flowcontrol receive on<br>SW16# show running-configuration interface ethernet 1/1/18<br>!<br>interface ethernet1/1/18<br> description 1-18_XXXXX_S1-P1<br> no shutdown<br> switchport mode trunk<br> switchport access vlan 1<br> switchport trunk allowed vlan XXXX<br> mtu 9214<br> flowcontrol receive on</pre><p>After we do that, our VMkernel should be pingable, assuming those IPs are routable:</p><pre>uzang@vd-XXXXXXXXXXX~ $ ping 10.XXXXX<br>PING 10.XXXXX (10.XXXXX) 56(84) bytes of data.<br>64 bytes from 10.XXXXX: icmp_seq=1 ttl=54 time=138 ms<br>^C<br>--- 10.XXXXX ping statistics ---<br>1 packets transmitted, 1 received, 0% packet loss, time 0ms<br>rtt min/avg/max/mdev = 137.522/137.522/137.522/0.000 ms<br>uzang@vd-XXXXXXXXXXX~ $ ping 10.XXXXX<br>PING 10.XXXXX (10.XXXXX) 56(84) bytes of data.<br>64 bytes from 10.XXXXX: icmp_seq=1 ttl=54 time=139 ms<br>64 bytes from 10.XXXXX: icmp_seq=2 ttl=54 time=138 ms<br>^C<br>--- 10.XXXXX ping statistics ---<br>2 packets transmitted, 2 received, 0% packet loss, time 1002ms<br>rtt min/avg/max/mdev = 137.760/138.336/138.913/0.686 ms</pre><p>To be more careful, we want to ping our gateway using these IPs new vmk. ssh into your ESXi and follow:</p><pre>[root@nc5211175:~] esxcli network ip interface ipv4 get<br>Name  IPv4 Address    IPv4 Netmask   IPv4 Broadcast  Address Type  Gateway       DHCP DNS<br>----  --------------  -------------  --------------  ------------  ------------  --------<br>vmk0  10.XXXXXXXXXXX  255.255.252.0  10.XXXXXXXXXXX  DHCP          10.XXXXXXXXXXX      true<br>vmk1  10.XXXXXXXXXXX  255.255.240.0  10.XXXXXXXXXXX  STATIC        10.XXXXXXXXXXX     false<br>vmk2  10.XXXXXXXXXXX  255.255.240.0  10.XXXXXXXXXXX  STATIC        10.XXXXXXXXXXX     false<br>[root@XXXXXXXXXXX:~] vmkping -I vmk1 10.XXXXXXXXXXX<br>PING 10.XXXXXXXXXXX (10.XXXXXXXXXXX): 56 data bytes<br>64 bytes from 10.XXXXXXXXXXX: icmp_seq=0 ttl=64 time=0.164 ms<br>64 bytes from 10.XXXXXXXXXXX: icmp_seq=1 ttl=64 time=0.296 ms<br>--- 10.XXXXXXXXXXX ping statistics ---<br>2 packets transmitted, 2 packets received, 0% packet loss<br>round-trip min/avg/max = 0.164/0.230/0.296 ms<br>[root@XXXXXXXXXXX:~] vmkping -I vmk2 10.XXXXXXXXXXX<br>PING 10.XXXXXXXXXXX (10.XXXXXXXXXXX): 56 data bytes<br>64 bytes from 10.XXXXXXXXXXX: icmp_seq=0 ttl=64 time=0.130 ms<br>64 bytes from 10.XXXXXXXXXXX: icmp_seq=1 ttl=64 time=0.121 ms<br>--- 10.XXXXXXXXXXX ping statistics ---<br>2 packets transmitted, 2 packets received, 0% packet loss<br>round-trip min/avg/max = 0.121/0.126/0.130 ms</pre><p><strong>Step 3 — configure the ISCSI software Adapter, initiator and connect to the ISCSI targets</strong></p><p>Now, create a Software ISCSI Adapter:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*VEOO9m_94M_Zjg2w17lgEA.png" /></figure><p>First thing with this adapter, we want to bind it specifically to the VMkernel we created earlier.</p><p>Before:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/853/1*u3O0uYgyk-KclmdHojNViw.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*WL9LqOeeT-KbnQKyhcvZzg.png" /></figure><p>After (rescan the adapter after bind):</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*43NZARV7xRWYnuIXGck03g.png" /></figure><p>Next, we want to add our discoverable ISCSI target. In Dell PowerStore you can find this IP here:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*AOYh7n8Trn2jFyDy0Dyfow.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/900/1*9XuVKtPvfej4jfQMFwPLGA.png" /></figure><p>It will automatically discover the Static addresses:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/953/1*WfM88GAMNSgZzOIL_SDLHQ.png" /></figure><p>Thats it, you now have a working ISCSI with 2 NICs.</p><p><strong>Step 4 — How to check the load is balanced</strong></p><p>In my case, I created a virtual machine running Linux and mapped a 2TB drive <strong>thin drive</strong> from my VMFS datastore. I then run a vdbench of 1mb pure reads.</p><pre>root@linuxvm ~]# cat parmfile_c<br><br>* Contents of parameter file: /tmp/vdbench-2902e042-9358-435b-83ea-b8a80b821398-1669672550<br><br>monitor=/tmp/vb_monitor<br>dedupratio=2.0<br>dedupunit=4k<br>dedupsets=5%<br>compratio=2.0<br>hd=localhost,jvms=24,shell=ssh,vdbench=/usr/bin/,system=localhost,user=root<br>sd=sd_09448,openflags=o_direct,align=1mb,hd=localhost,lun=/dev/sdc<br>wd=1mb_r,rdpct=100,xfersize=1mb,seekpct=random,sd=sd*<br>rd=rd0,wd=(1mb_r),warmup=20,interval=1,elapsed=280,threads=7,iorate=max<br>[root@linuxvm ~]# vdbench -f parmfile_c<br><br><br><br>Dec 18, 2022  interval        i/o   MB/sec   bytes   read     resp     read    write     resp     resp queue  cpu%  cpu%<br>                             rate  1024**2     i/o    pct     time     resp     resp      max   stddev depth sys+u   sys<br>08:04:23.071         1    2144.00  2144.00 1048576 100.00    2.035    2.035    0.000    5.340    0.609   4.4  71.3   1.6<br>08:04:24.048         2    3526.00  3526.00 1048576 100.00    1.957    1.957    0.000   34.513    1.233   6.8  13.5   6.8<br>08:04:25.047         3    3735.00  3735.00 1048576 100.00    1.862    1.862    0.000    5.418    0.543   7.0   6.3   3.8<br>08:04:26.045         4    3184.00  3184.00 1048576 100.00    2.184    2.184    0.000   23.317    1.700   7.0   7.6   3.2<br>08:04:27.047         5    3251.00  3251.00 1048576 100.00    2.140    2.140    0.000    5.572    0.629   7.0   5.8   3.6<br>08:04:28.044         6    3006.00  3006.00 1048576 100.00    2.318    2.318    0.000   12.891    0.891   7.0   5.7   3.5<br>08:04:29.044         7    3257.00  3257.00 1048576 100.00    2.142    2.142    0.000    5.434    0.622   7.0   5.1   3.4<br>08:04:30.046         8    3151.00  3151.00 1048576 100.00    2.208    2.208    0.000    8.650    0.613   7.0   6.4   3.7<br>08:04:31.044         9    2944.00  2944.00 1048576 100.00    2.367    2.367    0.000    6.453    0.672   7.0   6.7   3.4<br>08:04:32.052        10    3076.00  3076.00 1048576 100.00    2.280    2.280    0.000    5.758    0.636   7.0   5.5   4.0</pre><p>I then go to the ethernet switch, and look at the same ports as before, now greping for ‘rate’, we can see the Output load is 72% of line rate for each port.</p><pre>SW16# show interface ethernet 1/1/18 | grep rate<br>Queuing strategy: fifo<br>     Input 80 Mbits/sec, 97948 packets/sec, 0% of line rate<br>     Output 18243 Mbits/sec, 1485437 packets/sec, 72% of line rate<br>SW16# show interface ethernet 1/1/17 | grep rate<br>Queuing strategy: fifo<br>     Input 85 Mbits/sec, 104260 packets/sec, 0% of line rate<br>     Output 18242 Mbits/sec, 1484832 packets/sec, 72% of line rate<br>DUR-L1D5K-32BE-SW16#</pre><p>Hope anyone finds this useful, I could not find a proper guide for this hence decided to write this one.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=72c7d503c283" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>