Re: XenServer bond question

2016-08-30 Thread Daniel Mezentsev
LACP provide load-balancing based on hash of source+destination MAC addresses. Also on the linux end (not sure about XS) you can configure hash based on tcp port. Hash will be the same for one stream, it will be the same for any pair of src+dst MAC addresses, so you'll never get balanced

Re: XenServer bond question

2016-08-24 Thread Stavros Konstantaras
Hi Allessandro, In our environment with servers of 4 NICs, we configured it as following: - 1 bond for management traffic (NICs of 1Gbps) - 1 bond for storage,public & guest traffic by using VLAN separation of course (NICs of 10Gbps) In your case I would configure it as following - 1 bond for

Re: XenServer bond question

2016-08-23 Thread Gabriel Beims Bräscher
Looking at the section 4.3.5.1. Active-Active Bonding from documentation of the XenServer 6.5: "Management or storage traffic. Only one of the links (NICs) in the bond is active and the other NICs remain unused unless traffic fails over to them. Configuring a management interface or

RE: XenServer bond question

2016-08-22 Thread Marty Godsey
LACP does not provide more throughput but does provide more bandwidth. Basically if you have two 1G NICs in an LACP bond, you will not get a stream faster than 1G.. However, since you are not load balancing, you can have MORE 1Gb streams. So what your seeing is normal. Also do a ovs-vsctl