Hello. I use Xen 6.5 in my network. We want to configure active-passive
bond to different switch for redundancy. If we use Vlan network for VM over
bond (for example Vlan20) we have bug(v.2.1.3). I repeat lab on clean
debian(2.3.0) and have bug too:
*Description:*
ovs-vsctl show
7d896967-0afc-4680-8b9a-0e6aa4ed9ac8
Bridge "br0"
Port "br0"
Interface "br0"
type: internal
Port "bond0"
Interface "eth0"
Interface "eth1"
Port "svi20"
tag: 20
Interface "svi20"
type: internal
ovs_version: "2.3.0"
svi20 has address 192.168.0.1/24 - neighbor device has 192.168.0.2/24 in
Vlan20
*Work status:*
ovs-appctl bond/show
---- bond0 ----
bond_mode: active-backup
bond may use recirculation: no, Recirc-ID : -1
bond-hash-basis: 0
updelay: 0 ms
downdelay: 0 ms
lacp_status: off
slave eth0: enabled
active slave
may_enable: true
slave eth1: enabled
may_enable: true
If i down eth0 my lab continue work(active move to eth1)
If i up eth0 and set eth0 active(ovs-appctl bond/set-active-slave bond0
eth0) - my ping to 192.168.0.2 is missing.
If we tcpdump our link we look, that device not learning arp-record for
neighbor.
If we add static arp record ping absent too.
2016-03-02 15:23 GMT+08:00 Андрей Зайцев <andrezay...@gmail.com>:
> Hello. I use Xen 6.5 in my network. We want to configure active-passive
> bond to different switch for redundancy. If we use Vlan network for VM over
> bond (for example Vlan20) we have bug(v.2.1.3). I repeat lab on clean
> debian(2.3.0) and have bug too:
>
> *Description:*
>
> ovs-vsctl show
> 7d896967-0afc-4680-8b9a-0e6aa4ed9ac8
> Bridge "br0"
> Port "br0"
> Interface "br0"
> type: internal
> Port "bond0"
> Interface "eth0"
> Interface "eth1"
> Port "svi20"
> tag: 20
> Interface "svi20"
> type: internal
> ovs_version: "2.3.0"
>
>
> svi20 has address 192.168.0.1/24 - neighbor device has 192.168.0.2/24 in
> Vlan20
>
> *Work status:*
> ovs-appctl bond/show
> ---- bond0 ----
> bond_mode: active-backup
> bond may use recirculation: no, Recirc-ID : -1
> bond-hash-basis: 0
> updelay: 0 ms
> downdelay: 0 ms
> lacp_status: off
>
> slave eth0: enabled
> active slave
> may_enable: true
>
> slave eth1: enabled
> may_enable: true
>
>
> If i down eth0 my lab continue work(active move to eth1)
> If i up eth0 and set eth0 active(ovs-appctl bond/set-active-slave bond0
> eth0) - my ping to 192.168.0.2 is missing.
> If we tcpdump our link we look, that device not learning arp-record for
> neighbor.
> If we add static arp record ping absent too.
>
>
>
>
>
>
>
_______________________________________________
discuss mailing list
discuss@openvswitch.org
http://openvswitch.org/mailman/listinfo/discuss
