Multi-NIC vMotion in vDS

Similar Questions

• Multi-NIC vMotion with ESXi/vCenter 4.1

  We take running ESXi and vCenter 4.1 and after the secure Channel secure Channel 5.5 class and sitting for my exam in a few weeks, I have actively tried to improve our environment. Previously, to the study and trying to learn more about VMware, we were in pretty bad condition. Relevant material (AMD, Intel CPU, generations of Intel CPU, amount of RAM and CPU), versions hyperviosr Mismatched ESXi and ESX and no redundancy, vmotion and TONS of snapshots as backups.

  In the two weeks since my course, I have eliminated all snapshots (performance daily vCheck to check on the health of the venvironment), emigrated to 5 similar hosts (and memory/cpu configurations) that we had to drag do not, connected to all ports card NETWORK 6 to 2 x 3560g cisco switches and connected the second switch updated ESX to ESXi 4.1 and patched all hosts with Update Manager (nobody used), created the host profiles and compliance on the cluster and hosts, activated DRS and HA, set up a couple of VAPP for STM systems... the list is long

  I still have a lot to learn, but now I'm a bit confused about one thing...

  We use Fibre Channel SAN, one side get our second Fibre Channel switch hooked up for redundancy and I guess that Multi - pathing (?) I have a couple questions question...

  1. set up the second fiber switch would give me several warehouses of data, correct paths?

  2 can I create and separate vMotion in our configuration, using the CF WITHOUT? Any flow of traffic (for vmotion) through the vswitches or he remains behind the FC switch?

  -I know with iSCSI, you want to create a vSwitche separated and installation multi-nic vmotion

  3. in the configuration of the redundant management interfaces do I need to create two vSwitches with vmkernel with separate IP addresses management ports or just create on vSwitch with a vmkernel port and two network cards is assigned to the (two different connected to 2 physical switches physical cards)?

  -We will most likely use VST if we can get the trunk ports to pass traffic defaullt VLAN, so I think it is still acceptable to create separate vSwitches for management, vMotion (if necessary because of the CF) and port VM group? The designs I see online usually use only a vSwitch for VST and multiple is.

  That's all I can think of for now... Just some things that need to be clarified on... I guess I still need a vSwitch vMotion (allocate 2 of 6 network adapters in it) because some type of traffic would pass over him, but I think that most of the vMotion and all the SvMotion would remain behind the FC switch.

  Thanks for any help!

  With regard to the topic of discussion: Multi-NIC vMotion introduced with vSphere 5.x and is not available in earlier versions.

  1.) Multipathing is not related the number of FC switches, but only for the number of initiator and target. However, using several CF toggle availability increases due to redundancy.

  2.) you must differentiate here. vMotion is a live VM migration process to other hosts, i.e. only the workload of the migration. vMotion only uses the network. Storage vMotion on the other side generally used storage connections - i.e. the CF in your case - to migrate files/folders to the virtual machine.

  3.) redundancy for management traffic can be reached in several ways. The easiest is to simply assign multiple uplinks (vmnic) to vSwitch network management. So, a simple 'Netowrk management' will do, and redundancy is made based on recovery of the vSwitch.

  From a design point of view you can use multiple vSwitches for different traffic types, or combine them on a vSwitch by configuring the failover policies for groups (Active/Standby/Unused) port for example.

  André

• Multi-NIC vMotion question

  BACKGROUND

  I'll put up a new environment vSphere 5 with a couple of hosts ESXi 5 to test how things work in this latest version.

  I use HP DL385 G7 servers that have 4 integrated network cards and I have a quad-port NIC card server that I will implement etherchannel to serve my VM networks. I intend to use the 4 port NIC integrated for vMotion and my Console of service (management).

  CONFIGURATION

  For the vMotion and the Console, I built a unique standard vSwitch on each host and created 4 physical Ports VMKernel linked to my 4 network interface cards. 3 network cards are configured for vMotion with StandBy is defined as the vMotion other network cards. The 4th NIC is configured for management ensures only being 3 NICS of vMotion.  I use VLAN separate NIC of the Console and the vMotion NIC.

  My hosts are in an active cluster with DRS.

  All this seems to work well.

  TEST

  I have a couple of VM located on this cluster (2 hosts), so I use Putty SSH in one of my hosts. I run ESXTOP and press N to view the network settings. Here, things seem normal.

  I take a VM and vMotion he host that I followed. I was all traffic met on a single vMotion NIC instead of my 3 cards of vMotion.  This was not planned.  NOTE that this is the VM being vMotioned to my monitored host.

  When I vMotion a VM on the host that I followed, all 3 cards network vMotion ignite and is used. This was as expected.

  SUMMARY

  Several cards using vMotion network seems to work only when you migrate a computer that host virtual. The host on which the virtual computer is being migrated, yet receives just the virtual machine on the one primary NIC.

  I have a call in VMware and they are studying if this is normal or if there is a problem.

  URDaddy wrote:

  Rickard,

  Mine looks the same, but note that the receipt settings (right) only receive on vmnic2

  Pictured to the right, I don't see MbTX (sent), can you expand it too also see MbRX (receiving information)? It could actually be used...

• Single network or Multi vMotion Nic card

  Here are our current design for our soon vSphere 5.1 deployment

  There has a been a good bit of internal discussions on whether to use a single 10 GB for vMotion network adapter or use two NICs 10 GB for vMotion

  Most of the debate has been around "isolate" the vMotion traffic and makes it as localized as possible

  We all have the vMotion traffic is a vlan separate, vlan127 you can see in our design

  The big question becomes exactly where will the vMotion traffic? What switches/links it really go?

  Is this correct?

  1. If we start with a vMotion nic, then once that Vmotion begins traffic will be generated from the host lose the virtual machine and the host wins the virtual machine. In this scenario, traffic will cross a BNT switch. This leads to two conclusions
     
     
     1. Traffic is never as far away as the nucleus of Juniper
        
     2. vlan127 (vMotion) didn't need to be part of the trunk, go to the heart of Juniper to the TNB
        
  2. If we go with two NICs of vMotion, then the two 10GB network adapters might be involved in vMotion. This means that vMotion traffic between two hosts ESXi could hit a switch BNT, browse the battery connections (two 10 GB between the BNTs connections) and go to another host via a network card. GB 10 it has also led to two conclusions:
     
     1. Traffic is never as far away as the nucleus of Juniper. He remains isolated on a single switch BNT or moves between BNT switches through the two stack 10 GB connections
        
     2. vlan127 (vMotion) didn't need to be part of the trunk, go to the heart of Juniper to the TNB
        

  

  vMotion traffic is just unicast IP traffic (well good, except for some bug) between ESXi configured for vMotion, vmkernel ports if all goes well insulated in a non-routed layer 2 broadcast domain (VLAN). Simple as that. Considering that the traffic will cross physically regardless of the physical NIC is configured for the respective vmkernel ports. The path between the two is obviously depends on the layer 2 switching/STP infrastructure, which in your case would be just the blade chassis switches.

  Multi-NIC vMotion essentially implements several independent streams between different IP addresses and MAC, belonging to the same host. Consider the following:

  Host A and B with vmk1, using physical vmnic1, connected to physical pSwitch1 and vmk2, using vmnic2, connected to pSwitch2. The two pSwitches directly the trunk the VLAN vMotion between them.

  If the two hosts have only vmk1 is enabled for vMotion, traffic will never pass by pSwitch1. If host B has only vmk2 enabled for vMotion or you switch uplink, it'll pass the two pSwitches.

  Now, if you enable the two interfaces for vMotion vmkernel, it is difficult to say how the hosts decide what vmk connects to that. You may find yourself going through the two pSwitches for the two water courses, or you're lucky and you end up with source and destination interfaces that reside on the same pSwitch. I don't know how ESXi decides the pairings, this article seems to suggest it's done deterministically for that in a similar configuration, the same key vmk would connect between them:

  http://www.yellow-bricks.com/2011/12/14/multi-NIC-VMotion-how-does-it-work/

  Whatever the case, unless you need to other hosts on different switches, connected through your hearts only, to be able to vMotion between hosts, there no need at all to mark the vMotion VLANS on your links between chassis and Core switches.

  You see, your question of vMotion Multi-NIC is completely unrelated to this.

  If we start with a vMotion nic, then once that Vmotion begins traffic will be generated from the host lose the virtual machine and the host wins the virtual machine. In this scenario, traffic will cross a BNT switch. This leads to two conclusions

  1. Traffic is never as far away as the nucleus of Juniper
  2. vlan127 (vMotion) didn't need to be part of the trunk, go to the heart of Juniper to the TNB

  1. Yes.

  2. Yes.

  Circulation * could * crosses both switches BNT, according to what I explained above.

  If we go with two NICs of vMotion, then the two 10GB network adapters might be involved in vMotion. This means that vMotion traffic between two hosts ESXi could hit a switch BNT, browse the battery connections (two 10 GB between the BNTs connections) and go to another host via a network card. GB 10 it has also led to two conclusions:

  1. Traffic is never as far away as the nucleus of Juniper. He remains isolated on a single switch BNT or moves between BNT switches through the two stack 10 GB connections
  2. vlan127 (vMotion) didn't need to be part of the trunk, go to the heart of Juniper to the TNB

  1.Yes.

  2.Yes.

  Personally, I'd go with Multi-NIC vMotion use NIOC with soft actions in your config file.

• Mulitple-NIC vs. CASL for VMotion

  Hello

  TNX for reading

  I use Vsphere 6

  My Switch have Nexus (2Port 10Gbs for Vmotion)! and I don't know which one is better!

  Mulitple-NIC or CASL (LAG and Active Mode) for VMotion?

  and another Q is for an optimal speed to migrate Vmition. better MTU (Jumbo frames).

  tnxxxxxxxxxxxx

  It's actually the answer to your question "Mulitple-NIC or CASL (LAG and Active Mode) for VMotion?", i.e. to use Multi-NIC vMotion rather than LACP.

  André

• HP Flex10 and config recommended vDS for HA and failover?

  In the last two days I have experienced connectivity issues with my VM and I think I reduced it to beacon probing when is used as a failover mechanism in my groups of port / VLAN. I guess that the broader question "is what the settings recommended for failover based on my hardware configuration"...

  My ESXi hosts run 5.0.0U1 or 5.1.0 I just walking to vCenter 5.1.0a. Hosts are BL460c G7 servers in a c7000 with ICs Flex10 chassis. Each ESXi has a profile of server blade with 4 FlexNICs: a pair for the movement of data all VM (several Tagged VLAN) that belong to a vDS. The second pair is used for all traffic management and (at the moment I have reset) is on a stand-alone vSwitch with untagged traffic.

  Uplinks for each IC go with the Avaya VSP9000 switch. The two VSP9ks are connected by a STI trunk with all the VLAN tagged.

  Initially, I discovered the source of my traffic has dropped with the ARP table of a computer virtual pretend flip flop between the local binding of 10 GB on an Avaya and the link of the IST for the other Avaya (i.e. the uplink of the other IC module was used), which can cause a small temporary loop.

  No matter what method of load balancing I configure in the PG (stick to those supported by VC) and regarless if I have the two dvUplinks marked as Active or a marked as Active and the other as the day before, I see occasional about-face when beacon probing is used.

  I've set up virtual networks in Virtual Connect to use Smart Link, so I hope that Link Status should only be enough.

  Now while I still don't entirely understand beacon probe (I read about it on a few posts), I was hoping that it could provide a little more resilience despite having Smart Link set up on the side of VC.

  So for those of you who have the same hardware configuration, how you have configured your?

  Long term, I would like to bring to the management of virtual machines inside the vDS, mainly to have more flexibility in the management of bandwidth to have a slice of the 10 GB uplink established Virtual Connect level. I tried to put the management in the vDS but failed miserably and I think it's down to a scenario of chickens and eggs and I get the order to execute orders wrong... I'll look in that, once my configuration problem above fundamental network has been sorted.

  Thank you

  regarding overhead... NIOC is... good... but the general rule is that we release the core esx... so if we use more features... it will finally be an overhead projector... and if physical hardware does the same... thing... so it's better... This is why vmware has now VAAI... SRIOV... CPU/Memory unloading... If someone does not have the blades... and then if they have 10gig NIOC is only option...

  http://pibytes.WordPress.com/2013/01/12/multi-NIC-VMotion-speed-and-performance-in-vSphere-5-x/

  Management and vMotion are on the same VLAN (but different IP addresses) - it is recommended to use a VLAN from a safety perspective... and in production, this is how we do it. they can share the same NIC... no problem... but it should be labeled. 2 natachasery with 2gbe is good - I have recently done a comparative analysis of the speed of vmotion in the blade, you can see more info in my blog - http://pibytes.wordpress.com/2013/01/12/multi-nic-vmotion-speed-and-performance-in-vsphere-5-x/

  So a few questions:

  • I understand that you recommend keeping management / management of vMotion in a pair separated from flexNICs way to not give an additional charge within VMware.

  It is not mandatory... we have to use separate NICs... its all based on the customer's environment. But in separate VLANS... of couse VST marking consumes cycles CPU... we can ignore... the world... This is ignored. in case, you can use 2 natachasery with 2gbe to combine the mgmt/vmotion.

  • Y at - it an advantage of splitting management and vMotion in different VLAN but keep in the same uplink (so the VLAN tagging)

  security wise and best practices in production, we use separate VLANS, and we can share the same NIC...... There are some use cases as... that if you have 100 guests... and there may be several vmotions happening at the same time... in this case, we use dedicated pSwitch so that VMOtion traffic will not FLOOD the main switch. so here we use natachasery dedicated... in a small environment and a well balanced and if not on subscription of cluster CPU/RAM, then there is very little happening VMotion... If we can share the same natachasery and same pswitch.

  • Would we be better to use two different pairs of FlexNICs, one for management and one for vMotion using 3 pairs of FlexNICs in total (1 for all data VLAN, one not marked for management and a third no marked for vMotion). If so, I guess you'd give different bandwidths in VC to keep vMotion, nice and fast?

  According to my bench marking... what I did... If we give... 2GbE for vmotion, going too fast... and once again, as I said above... We can combine... or just give 2 natachasery with a bandwidth of 500 MB for mgmt and 2 gig for vmotion for VM traffic rest... * it is a good design... Here, we have isolated physically and VLAN wise as we need to isolate.

  for the low response fo the console... check the DNS resolution... and nothing to do with... the bandwidth. Check the CPU/RAM vcenter and the Vcenter CPU/RAM database...

• Question about the collection of NETWORK adapters for vMotion / VM vSwitch

  Hello

  We use vSphere Enterprise Edition 5.1.

  We also create separate vSwitch for management / vMotion and VM.

  Each vSwitch receives 2 network cards connected to the different switch for redundancy.

  We would like to know is necessary to provide the collection of NETWORK adapters for these vSwitches?  Currently, only enable us NIC Teaming for VM vSwitch only.

  Thank you

  VSwitch vMotion, we have 2 assigned NIC (nic2 and nic6) with 10 VLANS.  NIC2 and nic6 are connected to 2 different physical switches.

  Should I choose

  (1) both are active

  (2) both are assets + grouping of NETWORK cards?

  Question - if there is only 1 VLAN, it seems that NIC Teaming is also not very useful unless we use 2 VLAN (Multi-NIC vMotion).  Is this right?

  If you use Multi-NIC vMotion, there is no need to have two different VLANS, all you need is depending on configuration

  on your vMotion switch, please create two vmkernel port for vMotion with the same VLAN ID, but the grouping of NETWORK cards as below

  vMotion_1 - VLAN ID: 10

  Grouping of NETWORK cards

  vmnic2 - active

  vmnic6 - watch

  vMotion_2 - VLAN ID: 10

  vmnic6 - active

  vmnic2 - watch

• VMotion recommended Teaming

  Dear team,

  I created a new vSwitch1 and added two physical network adapter on vSwitch1.

  Then, I created two vmknic1 and vmknic2 and activated on the vSwitch1 vMotion.

  I just want to confirm, nic teaming this is just or not, need your help on the same.

  vSwitch1 (VMnic1 & VMNic2 set as active)

  vmknic1 (vmnic1 = > active, vmnic2 = > Eve)

  vmnic2 (vmnic2 = > Active, vmnic1 = > standby)

  concerning

  Mr. VMware

  Fix. I also highlight the process here: http://wahlnetwork.com/2013/03/18/blazing-fast-workload-migrations-with-multi-nic-vmotion-video/

  

• Tolerance of failure with multiple NICs

  Apologize if this has been asked before.

  I'll put up a vSphere 5.5 environment and I have NIC 1 GB for each host to devote two NICs per host for tolerance to failures.  I was wondering the best way to set this up to their maximum output.  I have implemented as a Multi - NIC Vmotion?  As noted here: VMware KB: Multiple-NIC in vSphere vMotion 5. Essentially using two groups of ports as FT-1 and FT-2.  Or what I need to do as a Multi-NIC iSCSI with separate vswitches and each vswitch with a Port Group.

  Thanks in advance.

  You run into a problem of flow when you use 1 NIC for FT?

  Currently FT only supports using a single network adapter (1 G or 10 G)

• vMotion network clarification

  Say, I activated vMotion on the management network and a more vMotion (dedicated) as well. What NETWORK card will be used for vMotion if MultiNIC is not configured? As management network must handle the rest of the network traffic, it is the only reason the management network is not recommended for vMotion?

  Hello

  Take a look at article francs on this piece

  http://frankdenneman.nl/2013/02/07/why-is-VMotion-using-the-management-network-instead-of-the-VMotion-network/

  in particular:

  "If the host is configured with a Multi-NIC vMotion configuration using the same subnet as the management network / 1 VMkernel NIC, then vMotion respects the vMotion configuration and only sends traffic through active vMotion VMkernel network adapters."

• Network [vSphere 4.1] load balancing and failover vMotion

  GoodMorning everyone.

  I have some doubts about the configuration of the network for vMotion in vSphere 4.1

  I know that I can activate a single portgroup VMkernel for vMotion on the single host, but can I have this portgroup in a vSwitch with two or more physical NIC attached.

  Currently, I managed to have a vSwtich with vMotion and management of trade wth two NICs (see attachment).

  Both NICs works very well with the recovery for both exchanges.

  I would switch to a vSwitch with multiple network cards and I have some doubts.

  It seems that I could configure it... but the load balancer for vMotion supported on vSphere 4.1?

  And also, have the protgroup of vMotion in a switch with several network cards, is there a way to check what physical nic is currently used by vMotion?

  I am currently under a license from the company.

  Thank you all for your help.

  vMotion for vSphere pre 5 does not support Multi-NIC, in vSphere 5, you can configure several VMKernel enable vMotion and select different Nic Active and load balance between the two vmnic, but unfortunately not in vSphere 4.x

  For the management of ESXi, if you set active on both network adapters, you not to cross any active advantage / standby because it will only use on vmNIC, unless there is still a failure... but 1 vmNIC just because bandwidth is usually not a problem for the ESXi management only.

  So the answer: upgrade to vSphere 5 for multi-nic vMotion and don't worry ESXi management as an active NETWORK card is more than enough bandwidth,.

  Here's a YouTube on the Multi-NIC vMotion http://www.youtube.com/watch?v=7njBRF2N0Z8 configuration

• Creation of vMotion, management and iSCSI

  Hi all

  I have doubts that I'd like to have some clarification.

  First vMotion and traffic management.

  I have two network cards. My question is, should I create IDE oucederomsurlesecondport VMkernel for each one (and adding the vMotion Option and management traffic) adding a different IP address for each and put the two in a vSwtich but the example; an active nic1 for vMotion and nic2 Eve and the management of the same traffic, nic2 active and standby nic1. With this, I have two different networks, but by using two NICs in case of failure.

  Or create a VMkernel and activate them both on the same VMkernel and put the two active network cards.

  What is the best choice, or the best performance?

  I have 6 guests on this cluster, so I need to do this in on the hosts.

  First I use QLOGIC

  The iSCSI side, should I use VMkernel Port binding? Or just use a normal VMkernel with my wihout VLAN iSCSI definition of any Biding VMkernel Port on iSCSI Software adapter?

  I have both running, but do not know which is the best way to get the best performance.

  Thank you

  JL

  Nice day!

  In summary, you should do something like that.

  vSwitch0 - Mgmt & vMotion

  ====================

  vmk0

  --------

  Management

  Uplink 1: assets

  Uplink 2: Passive

  vmk1

  --------

  vMotion

  Uplink 1: Passive

  Uplink 2: Active

  vSwitch1 - iSCSI

  ====================

  vmk2

  --------

  iSCSI traffic

  Uplink 3: assets

  If you only have an uplink for iSCSI traffic, you don't have to set up the binding of ports.  iSCSI ports is for the multipath.  If you only have one NIC for iSCSI, you cannot have MPIO.  You need two or multiple NICs or uplinks to the multipath.

  Now, for the management and the links of vMotion, I suggest using only an asset and a liability for each type of traffic.  Although vSphere 5 has the multi-NIC vMotion functionality, the idea of separating vMotion and traffic management is to separate vMotion and its important traffic in your management traffic bursts, which happens to include your traffic HA (also important).  You have certainly not * have * to set it up like that, but maintaining vMotion on his own physical link will keep walking on your management traffic.  In the case of a defective cable, I'm sure you would rather a cluttered link as no management or vMotion traffic.

  All the best,

  Mike

  http://VirtuallyMikeBrown.com

  https://Twitter.com/#! / VirtuallyMikeB

  http://LinkedIn.com/in/michaelbbrown

• Clarification on dvSwitch

  Hello

  I'm pretty new to dvSwitch administration.

  Can someone help me with the sub queries.

  1 a portgroup how if the traffic passing by its dvswitch vMotion or Mgmt or VMtraffic. There is a separate option in vSS to choose whether the traffic is vMotion management/traffic/FT etc... Or dvSwitch treats all traffic as the same thing... Except the id VLAN, I couldn't see any difference between the port groups vMotion/Mgmt/VM traffic...

  2. in my current infrastructure all exchanges load balancing strategies are defined on the method of ip originating virtual port. Should I use LBT on this config for best performance.

  3. is it recommended to use the LBT for vMotion (Heard is not recommended)?
  

  4 uplinks has one role other that simply forward the traffic.

  5. can you a virtual machine in an ESXi host using the uplink from another esxi host in the dvSwitch because all uplinks seem to be a pool of uplink for dvswitch (logically impossible)?
  

  
  

  Thanks in advance.
  

  1 a portgroup how if the traffic passing by its dvswitch vMotion or Mgmt or VMtraffic. There is a separate option in vSS to choose whether the traffic is vMotion management/traffic/FT etc... Or dvSwitch treats all traffic as the same thing... Except the id VLAN I couldn't see any difference between the port groups vMotion/Mgmt/VM traffic...

  There is no difference in standard switch, on the ability to select the type of traffic, this selection is done on VMkernel level and there is no difference in standard distributed. Have a look here for some vDS basics: Back To Basics: manage a distributed vSwitch (part 1 of 9) | Mike Landry...

  2. in my current infrastructure all exchanges load balancing strategies are defined on the method of ip originating virtual port. Should I use LBT on this config for best performance.

  LBT is my recommendation.

  3. is it recommended to use the LBT for vMotion (Heard is not recommended)?

  For vMotion traffic, I would recommend the vMotion NIC multi: http://www.settlersoman.com/how-to-configure-multi-nic-vmotion-on-vss-or-vds/

  4 uplinks has one role other that simply forward the traffic.

  The role of uplinks to connect your host and the virtual machines on the physical network.

  5. can you a virtual machine in an ESXi host using the uplink from another esxi host in the dvSwitch because all uplinks seem to be a pool of uplink for dvswitch (logically impossible)?

  Not sure if I understand your request, but in any case a virtual machine can use the uplink of the host where the virtual machine is running.

• With the help of site with iscsi

  You will need to validate whether you site for a config where vmotion and iscsi share the same vmnic.

  MY idea is to set up a single vDS with 2 vmk for iscsi connections, 1 with vmnic2 active and vmnic3 not used, the other vmk would be configured inversely with active vmnic3 and vmnic2 as unused.

  Now now for vmotion I would create a configuration multi-NIC where vmnic2 is active and vmnic 3 is not used and once again the 2nd vmk vmotion would be configured conversely where vmnic3 is active and vmnic2 is not used.

  VMotion networks would be configured w lower priority than iscsi networks to allow storage traffic

  Concerns:

  in iscsi multi pathing others vmnic in the vDS other than the active vmnic must be unused when the use binding, it is also the case for several microphones vmotion or is having other vmnic in the ok mode standby?  Which is the preferred method?

  the above configuration is officially suppotted?

  site slow performance of iscsi network will somehow?

  Thanks in advance

  in iscsi multi pathing others vmnic in the vDS other than the active vmnic must be unused when the use binding, it is also the case for several microphones vmotion or is having other vmnic in the ok mode standby?  Which is the preferred method?

  Unlike iSCSI use cases for Multi-NIC vMotion inactive NICS must be configured as standby and not as unused.

  See VMware KB: Multiple-NIC in vSphere vMotion 5

  the above configuration is officially suppotted?

  Yes.

  site slow performance of iscsi network will somehow?

  It obviously depends on how to actually configure NIOC and how the consumption of bandwidth real iSCSI and available bandwidth. Usually you would not define the limits of the NIOC on iSCSI traffic bandwidth and assign a higher priority as well.

  You can also consider to use the traffic on the port vMotion group shaping, see the following articles:

  Test vSphere NIOC host limits on Multi-NIC vMotion traffic | Network of Wahl

  Based on the Multi-NIC vMotion bandwidth control traffic shaping | Network of Wahl

• Failed to create FT logging with grouping of NETWORK cards

  I use vSphere vCenter 5.1 and 5.1.

  I create a port group of kernel VM on a new vSwitch, assign two NICs used on my ESX Server and logging FT. I have then add a second port VM kernel group to the two network cards and also assign FT logging. When I do this FT Logging the first port of kernel VM group is disabled. If I then manually enable FT gones then a second by logging on the first group of ports of kernel VM mode off.

  The same thing happens when I create 2 vSwitches, assign 1 NIC to each of them and assign the FT logging.

  I wanted to create my FT Logging predisposees in this way to match what I've done with vMotion and VM Network.

  I do something wrong or you can have a group of ports per server for recording of FT? Please notify.

  Thank you

  Multi-NIC VMotion is a new feature in vSphere 5.0. Multi-NIC FT has not yet been introduced. You mentioned trade Multi-NIC VM, but it is not possible either. While you can have two interchanges to connect to the same VLAN they must have unique names and a VM NIC may connect only to a unique name.

  What advantage do you hope to achieve with Multi - NIC FT? If the goal is more throughput 10G is the only option currently. If the lens is better traffic load balancing so that you could watch LACP on the vDS.