Using the vmkernel interface
Once the LUN is ready, the ESXi host needs to be configured to communicate with the iSCSI target. In ESXi, this is done on the vmkernel interface. A vmkernel interface is installed by default, but for storage it should be separated as much as possible. In this image, an additional vmkernel interface is being added.
Even though this configuration is a lab environment, I’m still separating the storage traffic to new interfaces.
Note that the default gateway cannot be changed AND is on a separate subnet. This is by design, as that is the first vmkernel interface and is a visual reminder that the storage traffic is separated from the other vmkernel traffic on vmnic0.
Rick Vanover is a software strategy specialist for Veeam Software, based in Columbus, Ohio. Rick has years of IT experience and focuses on virtualization, Windows-based server administration, and system hardware.
I'd recommand to start configure SAN after iSCSI's configure on VM host Allocated volume and etc. Then add VM host(s) on SAN to see if SAN can see it. Only after this done, return to VM host and add preconfigred SAN volumes Rerun and allocate space and etc.
i need the pdf or ppt of this presentation. If any on have plz send it to me on my email address firstname.lastname@example.org
As a pre-sales technical person, this write up was extremely helpful in aiding me in setting up a virtual Data Center. Thank you for taking the time to put this together!
May i ask how valuable and how easy to adapt this connection an ESXi host to an iSCSI storage target. And whats the risk..? As a newbie Novice i want to learn momre of this.. Is there a step by step and definition about this thanks... Sorry if i ask cause i'm just a fresh graduate in I.T major in networking and trouble shooting thank you kindly.. ^_^