On 10/21/2014 05:59 PM, nu li wrote:
> Thanks for the reply, all the hosts are bonded with LACP mode.it
> <http://mode.it> should be load balancing.
> Now, our environment need this kind of configuration.
>
>
> eth2 eth5 ---VF----> assign one of the VF to a VM, this VF NIC can
> not ping another VM with same configuration (VF, host NIC bond).
> | |
> | |
> -------------
> |
> bond (lacp)
>
>
When you say another VM are you referring to another VF on eth5 or
something that has to go through the bond? The problem is anything that
has to go through the bond could end up at either eth2 or eth5. If it
ends up at eth2 and was meant for the VF on eth5 then the packet is dropped.
You either need to not use SR-IOV on eth5 with the lacp bond, or you
need to enable SR-IOV on eth2 as well and then give your VM a VF from
both so that it can set up a bond of its own. In order for your current
configuration to work the link partner needs to be able to route traffic
to a given interface based on the MAC address and lacp is load-balancing
the MAC address across eth2 and eth5 and this is the most likely reason
why the bond and SR-IOV will not work together.
Thanks,
Alex
------------------------------------------------------------------------------
Comprehensive Server Monitoring with Site24x7.
Monitor 10 servers for $9/Month.
Get alerted through email, SMS, voice calls or mobile push notifications.
Take corrective actions from your mobile device.
http://p.sf.net/sfu/Zoho
_______________________________________________
E1000-devel mailing list
E1000-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/e1000-devel
To learn more about Intel® Ethernet, visit
http://communities.intel.com/community/wired
