On Fri, Feb 17, 2017 at 11:30 AM, Neelakantam Gaddam
wrote:
> This issue is not reproducible on x86, but seeing zero mac address.
Did the patch from Nic help with the zero mac address issue? There is
a related patch I will push today.
I currently don't have access to a
This issue is not reproducible on x86, but seeing zero mac address.
Steps to reproduce the issue:
1. Cross compiled for MIPS big endian platform.
2. Ran the ovs as mentioned in INSTALL file.
3. Make the link status of two slave interfaces UP and RUNNING.
4. Created the bond with above two
> On Feb 12, 2017, at 1:05 PM, nickcooper-zhangtonghao
> wrote:
>
> If you use the virtual ethernet driver, you should set the type of net
> device. If not, the “system” will be used.
>
> For example, tap device
>
> ovs-vsctl add-br br0
> ifconfig tap1 up
> ifconfig
But there were no issues observed with ovs 2.4.0 version without any
interface settings. Issue exist with ovs 2.6.1 only if both eth0 and eth1
are up (link state RUNNING).
Can you give me some pointers on what changed between 2.4 and 1.6.1
regarding this bond issue.
On Feb 12, 2017 10:35 AM,
If you use the virtual ethernet driver, you should set the type of net device.
If not, the “system” will be used.
For example, tap device
ovs-vsctl add-br br0
ifconfig tap1 up
ifconfig tap2 up
ovs-vsctl add-bond br0 bond0 tap1 tap2 bond_mode=active-backup
ovs-vsctl set interface tap1 type=tap
To: ovs-discuss@openvswitch.org
Subject: Re: [ovs-discuss] Bonding slave disabled
One more observation is that if any of the interface link status is down, then
the add-bond operation is showing the down interface as disabled and up
interface as enabled with proper mac address.
On Fri, Feb 10, 2017
One more observation is that if any of the interface link status is down,
then the add-bond operation is showing the down interface as disabled and
up interface as enabled with proper mac address.
On Fri, Feb 10, 2017 at 1:25 PM, Neelakantam Gaddam
wrote:
> Hi all,
>
> I