iSCSI and LACP

Similar Questions

• How to compare premises, iSCSI and storage NFS for VMware ESXi 5 with IO Analyzer?

  Hello

  I have 2 hosts ESXi 5.0 with a few virtual machines running. I would compare the IO throughput for my local storage, iSCSI and NFS vmware storage store. Can someone point me to the right direction? I read the documents and tutorials, but I'm not sure how to compare tests from these 3 options.

  I have a need to compare the following storage options.

  Local disk on the ESX host

  iSCSI on QNAP NAS device

  iSCSI on EMC e 3100

  NFS on QNAP NAS device

  NFS on EMC e 3100

  IOmeter seems to be good tool based on reading, but still not clear where to make changes to pass tests of storage to another.

  Thanks in advance,

  Sam

  If you use IO monitor, then you must simply vmotion the VMS to the data store for the device you want to test, and then run the test (and Records results).  Can vmotion for the following data store and repeat.

• Questions about iSCSI and subnets

  IM planning on a deployment of 8 ESX servers connected to an array of iSCSI on double dedicated switches.

  1. 2 cards on each ESX host network is dedicated to iSCSI and VMware dependent ontraffic.
  2. SAN iSCSI target consists of two controllers with 2 uplinks of iscsi on each controller (4 total)
  3. The manufacturer of SAN is suggesting setting up of their SAN ports in separate subnets for higher throughput
  • For the sake of simplicity lets say assign 10.10.100.1 24 ports SAN 1 & 3 and 10.10.200.1 24-port SAN 2 & 4
  • On the side of ESX, a single iSCSI VMKernel address will be 10.10.100.2 and the other will be 10.10.200.2.

  My questions:

  1. do I have to enable trunking VLAN on the side of the switch so that the initiator 10.10.100.2 ESX failover to the port of SAN 10.10.200.1 and vice versa, because they are not in the same subnet and therefore not in the same VLAN?
  2. If this is the case, will trunking VLAN also solve the problem if we were to buy an identical iSCSI SAN on the road and 2 subnets more setup for controllers, but still only have two cards on the ESX Server.
  3. I would assign the 2nd ESX Server in this config with the same IP addresses as the first, or I re them with differnet IPs (but obviously still in the same subnet as the storage arrays), for example ESX 1 is 10.10.100.2 and ESX 2 would be 10.10.100.3

  Any other associated iSCSI I get with VMware, simply not able to think through this particular obsticle and I don't have the equipment to test it yet. Doesn't help that it's late in my part of the world and my brain power is depleting fast!

  Thank you!

  I mean really isolated network. No routing between them.

  Is the software of multiple paths that can pass a path to another, and if you need one network to another.

  Note that the PowerVault will have an interface of a mosquito net and to one another for each processor.

  André

• sVMotion between iscsi and fc?

  I would like to know if sVMotion worked between iscsi and fc storage.  Just by looking at the possibility of moving from FC to iscsi on the road and wanted to check, it is that we give a host at the same time we can use svmotion to get the virtual machine out of a store on a datastore iscsi and FC database.

  Ideally the VM perform during this process. Any witch hunt, it's if it was running?

  Storage VMotion does not care SAN type, I carried out all types of migration between FC, iSCSI and NFS myself.

  So don't worry about it. But beware this SVMotion create large extra i/o load, so run when it will not affect the services running.

  ---

  MCSA, MCTS, VCP, VMware vExpert 2009

  http://blog.vadmin.ru

• ISCSI and FC SAN VI 3.5

  Hello gurus!

  I have a VI 3.5 with FC SAN environment, but now we need more hard drive space. I think the use of ISCSI SAN, but some people says that it is not correct (unstable) to use ISCSI and FC SAN in the same environment.

  What do you think of this?

  Thank you!

  You can always have FC, ISCSI and NFS presented to the same ESX Server, it will not come into conflict each other as long as you do not present the same logic of FC and ISCSI each unit number.

  Craig

  vExpert 2009

  Malaysia, VMware communities - http://www.malaysiavm.com

• NFS and LACP

  I have a 5.0 vSphere deployment where I take advantage of NFS.  I forced sub and I wanted to share my approach to see if someone has a strong feedback or could play the Devil's advocate.

  Constraints:

  (1) protocol choice NFS

  (2) a single switch cisco 3750 for small sites and (2) 3750 MLACP for large sites.

  (3) all the only 4 cards available for storing copper.

  (4) provider Netapp

  For sites with a single physical switch, I create two separate vmkernels on the same subnet (VLAN) on a standard switch and each vmkernel will all have two cards.  VMkernel port groups will hash IP, as load balancing strategies and physical switch will need ports configured with LACP (802.3ad).

  For sites with two physical switches I have each spread vmkernel on physical switches.  I'll also have two vmkernels on the same subnet on a standard switch and each vmkernel will have two active network cards.  VMkernel will hash IP balancing political and physical switches port groups is configured to support MLACP (802.3ad).

  NetApp will be alive to NFS in Multimode support to allow multiple IP addresses.  Each data store will have a different IP address.

  I was planning to use several subnets for the VMkernels, but still have not completely made my mind yet.

  Thank you

  Hello

  Yes, if you mount two data warehouses using two different IP addresses, you will use only two links of the ESXi hosts to the switch.  If you use only two links from a controller, you will use so the two links on the way back.  Remember that each device in the path (the host ESXi, the switch and controller) using its own hashing algorithm to determine what port or uplink to send traffic.

  It is a fine design, even if you use only two data stores at first.  If you are planning on using all four links at the beginning, then look at how you use your data warehouses.  You're breaking up to .vmdks by the operating system and data? VM and ESXi host .vswp page files burst you? Maybe you should.  You replicate between sites? If so, you can separate data storage for these types of transient data.  In this way, you can create several data stores more and spread over the bandwidth.

  All the best,

  Mike

  http://VirtuallyMikeBrown.com

  https://Twitter.com/VirtuallyMikeB

  http://LinkedIn.com/in/michaelbbrown

  Post edited by: Mike Brown for grammar

• iSCSI and LAN traffic even vSwitch?

  Hello

  It is a question for laboratory and not the production. I have a server with two network adapters.

  Is it possible to use these network adapters with two vswitch for LAN and iSCSI. Will it work?

  I know that it is not recommended.

  Thank you

  Edy

  You could also put them on a single switch with the consolidation of NETWORK cards. For iSCSi, you can have active NIC1 and NIC two mode standby. For data traffic, you can have active NIC2 and NIC1 mode standby.

• Cannot add to the inventory if virtual machine running on the other guests - iSCSI and VMFS5

  5.5 ESXi hosts free standalone version

  iSCSI mounts with multiple paths - relatively new unit with more modern hardware

  CHAP not used

  I'm running a few hosts in order to climb the same iSCSI data stores. The iSCSI LUN is visible and editable by all hosts. If Host1 is to map the iSCSI LUN (VMFS5) and a VM is powered, Host2 can add that VM to the inventory. It's possible with NFS iSCSI for a reason any. This is for a specific reason? Only when I turned off the virtual computer can I add it to both hosts. Other that just lock files are placed in the directory, I missed something related to the lock?

  From now on, adding new esxi hosts does not allow me to add existing virtual machine, less than the voltage first. Once again, NFS does, iSCSI, this isn't. Any ideas?

  It is not specific to ISCSI but rather to the use of VMFS. NFS has no awareness VM VMFS is and why it is not possible to do that with iSCSI / VMFS. There is a lock on the disk for each virtual machine of (race), and that's why the second host is not able to add this host to its inventory. With vSphere HA, this lock is released when a failover should occur.

• question of vMotion iSCSI and jumbo frames

  Hello

  I have a cluster ESXi 4.1 using vCenter and a SAN MD3200i.  I'll do an upgrade to optimize the installation, which includes the installation of four NIC ports in hosts that will be used for iSCSI.  I struggle to enable frames or not, but if I do, I just want to do for the iSCSI, at least for now.  Currently, the maps iSCSI network on the hosts and the MD3200 iSCSI connections are connected to two switches separated, although I have seven other switches in the building connected to the PC, printers, etc.  What I only turn frames on two switches that iSCSI is connected, or do I have to enable frames on all my switches?  There is a Dell 2724 and eight 6224Ps of Dell.  ISCSI is connected to the 2724 and one from the 6224Ps.

  The two switches that are connected to the iSCSI ports are not dedicated iSCSI switches; they have other devices on them, but I can only enable the frames extended globally on the switch.  Would there be any problem allowing the frames extended on the switches, otherwise all connected devices are configured for them?

  Another question about vMotion: I will create four ports on each host for iSCSI vmkernel.  Currently, there is also a port configuration vmkernel for traffic management and vMotion.  Is it possible to set up each of the four iSCSI for vMotion vmkernel channels, or should I leave it configured on the port of vmkernel management?

  Thank you!

  Sure. If you're going to enable Jumbo frames, you need to have dedicated switches for that, or a switch that may have different units MTU on their ports.

• iSCSI and distributed switches

  This could be a long post, but I did not ' have much time so will now start on it and Add.

  I am trying to install two vswitches distributed with ports vmkernel on each and link them to two physical cards on their own subnets connected to an iSCSI device that has two interfaces.

  I do all this in my lab ESXi nested under fusion using OpenFiler as the iSCSI device.

  I currently have two hosts, I have a cluster with vcenter server and openfiler iSCSI shared storage that works perfectly.  All comms management are on the subnet of the network management including iSCSI.

  I then created two networks more molten vmnet4 and vmnet 5, added 2 network I / f on each host and openfiler.

  Then created two dvswitches and vmkernel ports added to each and vmnic connected to iSCSI networks.

  What are hosts autodeply btw, so I then updated my host from my hosts of reference profiles and applied to the other host (I have a couple more autodeploy of hosts also although I use for practice in collaboration with autodeplay and everything works well) rebooted everything and the dvswitches are soft, pings all good work.

  Now comes the problem.  I can add these vmk/portgroup/vmnic for vmhba33 iSCSI software initiattor...  I can't enable iSCSI on the vmkernels in the vds or as it is grayed out.  When I try and add them to the adapter vmhba33 I get the message:

  The selected physical network adapter is not associated with VMkernel consistent teaming and political failver. VMkernel NIC must have exactly a link active and no rising shall be eligible to bind to the iSCSI HBA.

  so, I have attached a picture of this.  When I watch the vmkernel ports, iSCSI is greyed out.

  Basically, I'm trying this for is better acquainted with dvs and thought to deploy dvs and assign to the many guests would be the fastest way to implement an iSCSI for many guests esxi autodeployed network.

  The curious bit is that the görüş and vmkernel port adapter not listed FRO the dvs on vmnic 2 and 3 networks that are my iSCSI.  There are ports of the vmk in a portgroup with the name and the port group.

  I stuffed the properties I can find, and each button and the disturbingling, a lot of things is grayed out.

  I am stop for tonight and hope that someone can tell me first if what I'm doing is really possible and I do not do something stupid... and on the other hand, if someone can tell me the correct downwards path as I seem to have gone astray.

  Thank you

  Bill

  You can retrace your steps using this procedure to see if you have missed the steps;

  http://thefoglite.com/2012/06/14/configure-software-iSCSI-port-binding-on-a-VDS-with-dvPorts/

• Why vmkernel port for iscsi and vmotion services?

  Hello

  Just a quick question.

  I was trying to understand - why we need to have a vmkernel port when we want to use features such as vmotion or iscsi.

  Why not use them with a console port service or a port of vm management traffic.

  No particular reason.

  Thank you

  Yes. You're not really all that traffic produced by DRS and vMotion actions in your production (maybe time critical).

  Concerning

• iSCSI and adapter NC550SFP

  Hi all

  I have adapters HP NC550SFP with ESXi 4.1 for an iscsi (10 G, control flow and frames configured) network.

  My configuration is up to now using the "iscsi software map" in vmware... because I see no support for adapter hardware iscsi for these cards. My questions are:

  1 the NC550SFP is supported by a hardware iscsi adapter?

  2 should I worry used with 10Gig iscsi software adapter?

  Thanks for your time... I'm a newbie to iscsi here... so I would like to do things properly before putting them on the prod!

  Glenn

  1 the NC550SFP is supported by a hardware iscsi adapter?
  2 should I worry used with 10Gig iscsi software adapter?

  1. I see iSCSI on the plug on HP, but no confirmation that it is a hardware iSCSI HBA.  It should be appear under storage adapters if she supports the iSCSI hardware.

  2. I don't think you should be concerned.  ISCSI HBA hardware will take off the part of the processing load and overhead of off the VMkernel (CPU and memory).  But you can see the small difference with the new processors and memory that we have in the servers today.

• Gross storage iSCSI and VMDK questions

  I don't know if this is the best place for this question, so let me know if it is better to have another forum.

  I have ESX4 Setup on a server with a box of Equalogic serving 500g on iSCSI disks. For now, I have a 500 GB slice that I use only for the OS data and store all on OS VM.

  One of these virtual machines is a replacement for our mail server on Ubuntu 10.04 server that I want to run Zimbra. In our current setup, we have a physical 400 GB RAID 1 implemented as the/opt directory to store the install zimbra and the data store, this config partition makes I/O and backup issues a wink. I want to replicate this model, but I'm having problems.

  As I understand it, I have two options on the new VM server.  I can attach a raw disk via iSCSI via the menu vCenter as a connected virtual drive, or I can config the iSCSI connector in Ubuntu to access the drive directly.  I prefer the former because it makes things simple, but what I will meet an error when I try to connect the drive.

  Basically, it forces me to choose the location of the data store virtual and I have only two options, the 147 GB SAS on the physical ESX Server or the iSCSI drive 500 GB that I have attached to vCenter for the OS data. In both cases the error that I get States that there is not enough space on the data store for the extra 500 GB added to the virtual machine by attaching it.

  Yes, is there a way to add this iSCSI disk to the virtual machine without being part of the VMDK files? Or what I need to reach via iSCSI inside the Ubuntu VM? It would be nice to take advantage of snapshots and others, but I don't see how to do this job unless I have duplicate all storage making it OSdata drive big enough to accomidate the attachment of additional 500 GB to this virtual machine and even all my other virtual machines that have similar needs. This seems impractical because it would literally data duplicated without the benefit of the RAID or parallel I/O.

  Thanks in advance for any help/advice.

  We've covered this before, but you're absolutely sure that "OSDATA EQ iSCSI" is formatted with a block size of 4MB?

• Network configuration for ISCSI and VMotion

  Hello

  I have an ESX host configured with the iSCSI storage and am currently working on the best way to affect my NIC I a four VMK vSwitch and two nic

  http://communities.VMware.com/message/1428385#1428385

  I also have an additional switch for VMotion.

  vSwitch3

  -

  ---

  -VMkernel

  -Service 2 console

  -

  ---

  vmnic6

  -

  ---

  vmnic7

  -

  ---

  vmnic6 and vmnic7 are both on the San.

  After adding the new VMkernel and activation of vmotion, I was wondering why this has not shown as an additional path to the storage (I want to know if this is another question). Then I ran "esxcli swiscsi nic list d vmhba33" and of course, only the first four VMK was listed.

  Why the new VMKernel is not automatically linked to vmhba33?

  It would be a bad idea?

  See you soon

  Just to play devil's advocate, why shouldn't be VMotion and SAN traffic on the same link though?

  the iSCSI traffic MUST have a low latency and no mistake.

  VMotion can create advanced that could generate problems in iSCSI traffic.

  No idea why it does not automatically bind well?

  Can you vmkping each IPs Eql?

  You have to add each interface vmkernel of initiator iSCSI, with a command like this?

  esxcli swiscsi nic add - n vmk0 d vmhba34

  André

• iSCSI and cable

  Hi all

  I have 3 physical server each with esxi4 and storage shared (win2008-storage box) with 4 gib nic

  I think to connect to each server with a crossover cable for storage and the use of iSCSI Protocol to map drives.

  I read somewhere that crossover is not supported and it slows down the performance.

  Does anyone have more information or experience about it please?

  Thanks in advance

  CAIRP

  Hi Cariparo,

  Of course, you can do, see following diagram is what I use now.

  a direct connection to the SAN in the ESXi servers with nothing in the Middle, it can eliminate the single point of failure caused by the switch and also to provide redundancy.

  each color in the iSCSI network is another IP subnet by itself. the ESXi in the production network, I put two cable connected to two different ports and then add the bears in same vSwitch for failover

  hope this helps,

  all comemnts and input would be greatly appreciated.

  Kind regards

  AWT