Unsolved
This post is more than 5 years old
1 Rookie
•
47 Posts
0
62520
January 17th, 2014 07:00
Connecting Server 2012 VM to EQL PS6100
Hello. I am trying to connect a windows server 2012 vmware machine directly to my eql 6100 san. Currently I have the EQL attached to 2 Dell R620's which is hosting my virtual machines. I have 2 force10 switches that serves as my iSCSI network and I have 4 ports on each R620 connected to the force 10 iSCSI switches. Inside of vmware I have 4 ISCSI vmkernel ports setup in round robin. I don't have the enterprise version of ESXI so I cannot use the MEM plugin. My question is this:
If I want to create a volume inside of server 2012 using the windows iSCSI initiator that will be used for file shares, what is the best practice on doing this?
I have additional ports available on the R620's that I can use to connect directly to the force 10 iSCSI network. In vmware do I need to create vswitches that will be only used for the windows network shares connected to the EQL? I plan on creating a volume on the EQL side that will only be used for the windows file shares.
Hopefully the above makes sense:). Thanks



Origin3k
4 Operator
•
2.3K Posts
1
January 17th, 2014 08:00
1. Always install MeM. there is no paper which say it isnt allowed
As Don suggest,
if you have pNICs around on your R620 create a new vSwitch with 2 "Virtual Machine Network" Portgroups is a good solution. In this way there would no interference with your existing ISCSI VMKs. (iSCSI for ESXi Host is completly different compared to iSCSI into GuestOS.) Different PG, different Failover Settings ....)
You have to add 2 more vNICs (vmxnet3) to your VM and install the MPIO feature together with Dell HIT Kit. If you would like to use JumboFrames dont forget to configure the vSwitch as well and than set it on the virtual NIC within the OS.
Regards,
Joerg
Origin3k
4 Operator
•
2.3K Posts
0
January 17th, 2014 09:00
Don, yes its VMware but it doesnt act as you think for now :)
Regards,
Joerg
phil435
1 Rookie
•
47 Posts
0
January 17th, 2014 09:00
Joerg,
I tried installing the MEM module in VCLI but it kept giving me errors. I traced the errors down to certain activeperl modules not supported in windows 7 64 bit. I will try this again in XP mode and see what happens.
I was told by my EQL remote install guy that the way he set the iSCSI up in vmware was what the MEM script did as well. However, after discussion with my Dell rep he stated that the MEM module improved performance when multiple members where setup in a group. Right now I only have a PS 6100X that will be used for production and a 4100 that will hold the replicated data (no VM's using this unless disaster).
Origin3k
4 Operator
•
2.3K Posts
0
January 17th, 2014 09:00
We see much better performance with Mem aka "EQL Routed" than "RoundRobin" also with a single EQL Array. We always install it.
I havent touch the setup.pl for ages so i can say if the vSphere Perl SDK produces error when try to execute the script. I use the SDK for normal scripting and it works but using Powershell is 10 times easier for me ;) In the early days the perl code wraps around esxcli.exe and various vi..bla.cfg. commands.
Normaly i copy the *.zip to the esxi and use "esxcli software ...." from the local command line to install it. Its in the same step as we install OMSA for ESXi. Later it becomes part of the VUM (for updates).
As for today VMware have forget to enable the restrictions of using 3rd party MPIO within vSphere ESX when having not Enterprise(+).
Regards,
Joerg
phil435
1 Rookie
•
47 Posts
0
January 17th, 2014 09:00
Thanks Don. This is exactly the information that I needed. I will connect up two additional nics and test the above scenario.
phil435
1 Rookie
•
47 Posts
0
January 17th, 2014 09:00
I am using jumbo frames, so I will set the guests up to support this as well. I only have vsphere essentials plus, which I think does not allow me to enable MEM. I assume the big advantage of MEM will be when I add additional members to my group and span volumes across members?
Understood Joerg, MEM may install.
Origin3k
4 Operator
•
2.3K Posts
0
January 17th, 2014 10:00
See it working on Essentials (the smallest ) and up and this on vSphere 4/5. Its not the first time VMware have forget to enable a restriction.
The reason maybe why they never locked it maybe is that there are only 2? vendors which offer such a kind of SATP.
Just to say it clearly.. on paper you need E/E+ but in real world its different. So in the meantime use it and be happy.
Regards,
Joerg
phil435
1 Rookie
•
47 Posts
0
January 18th, 2014 18:00
I did get the MEM module installed on one of my hosts. I notice even though I have 4 vmk adapters on each host, it is only using 2 paths per volume. If I understand the user guide then this is the default behavior. I do notice that the paths are different for each host, so overall it is using all 4 paths. Is there any reason to change the default behavior to 4? My 6100x has 4 1gb ports on each controller.
phil435
1 Rookie
•
47 Posts
0
January 21st, 2014 12:00
I just found out that if you reboot the esxi host the MEM module goes inactive. Apparently they are checking on boot for proper licensing. We have the essentials plus license which has storage API's but not storage api's for multipathing.
phil435
1 Rookie
•
47 Posts
0
January 21st, 2014 16:00
Thanks Don for the info. I do have RR set back as the default policy.
Back to the orginial topic :) Is there a real advantage to connecting guest to the storage direct for file shares and is this the same as raw device mapping? I can create another volume just for the file share and present this to the VM using vmfs. I have read were direct access is beneficial for exchange servers and databases by bypassing the vmware layer though.