[ovs-discuss] Bonded interface on ovs bridge configuration

[Orabuntu-LXC]

Hi, this is some code I used quite awhile back to create bonded switch
ports in case this helps...

ovs-vsctl add-bond sw4 bond0 sw4p2 sw4p1 trunks=10,322
ovs-vsctl add-bond sw3 bond1 sw3p2 sw3p1 trunks=10,322
ovs-vsctl set interface sw3p1 type=patch options:peer=sw4p1
ovs-vsctl set interface sw4p1 type=patch options:peer=sw3p1
ovs-vsctl set interface sw3p2 type=patch options:peer=sw4p2
ovs-vsctl set interface sw4p2 type=patch options:peer=sw3p2


On Wed, Jun 13, 2018 at 9:34 AM, Chris Boley <ilgtech75 at gmail.com> wrote:

> Hi, depending on your switch: for example a C!$C0 3560 or 3750 will often
> can only use slow LACP negotiation and not fast negotiation. I’m not sure
> if this might make any difference to your scenario.
>
> On Tue, Jun 12, 2018 at 8:13 AM Tejali Bhujbal <tejalibhujbal at gmail.com>
> wrote:
>
>> Hi Guys ,
>> I am trying to configure bonded interface on ovs bridge but somehow
>> bonding doesn't up.
>> can you see any mistake in my configuration?
>>
>>
>> auto lo
>> iface lo inet loopback
>> dns-nameservers 129.241.0.200
>> dns-search dev.iaas.ntnu.no mass
>>
>> # Bond enp7s0f0 and enp7s0f1 together
>> allow-vmbr0 bond0
>> iface bond0 inet static
>>   ovs_bridge vmbr0
>>   ovs_type OVSBond
>>   ovs_bonds enp7s0f0 enp7s0f1
>>   address 10.212.28.11/22
>>   # Force the MTU of the physical interfaces to be jumbo-frame capable.
>>   # This doesn't mean that any OVSIntPorts must be jumbo-capable.
>>   # We cannot, however set up definitions for eth0 and eth1 directly due
>>   # to what appear to be bugs in the initialization process.
>>   pre-up ( ifconfig enp7s0f0 mtu 9000 && ifconfig enp7s0f1 mtu 9000 )
>>   ovs_options bond_mode=balance-slb lacp=active
>> other_config:lacp-time=fast
>>   mtu 9000
>>
>> # Bridge for our bond and vlan virtual interfaces (our VMs will
>> # also attach to this bridge)
>> auto vmbr0
>> allow-ovs vmbr0
>> iface vmbr0 inet manual
>>   ovs_type OVSBridge
>>   # NOTE: we MUST mention bond0, vlan50, and vlan55 even though each
>>   #       of them lists ovs_bridge vmbr0!  Not sure why it needs this
>>   #       kind of cross-referencing but it won't work without it!
>>   ovs_ports bond0 vlan1529 vlan1530
>>   mtu 9000
>>
>> # Proxmox cluster communication vlan
>> allow-vmbr0 vlan1529
>> iface vlan1529 inet static
>>   ovs_type OVSIntPort
>>   ovs_bridge vmbr0
>>   ovs_options tag=1529
>>   ovs_extra set interface ${IFACE} external-ids:iface-id=$(hostname
>> -s)-${IFACE}-vif
>>   address 10.212.36.11
>>   netmask 255.255.252.0
>>   gateway 10.212.36.1
>>   mtu 1500
>>
>> # Ceph cluster communication vlan (jumbo frames)
>> allow-vmbr0 vlan1530
>> iface vlan1530 inet static
>>   ovs_type OVSIntPort
>>   ovs_bridge vmbr0
>>   ovs_options tag=1530
>>   ovs_extra set interface ${IFACE} external-ids:iface-id=$(hostname
>> -s)-${IFACE}-vif
>>   address 10.212.40.11
>>   netmask 255.255.252.0
>>   mtu 9000
>>
>> auto eno1
>> iface eno1 inet static
>>     address 10.212.48.11/22
>>     mtu 1500
>>
>> auto eno2
>> iface eno2 inet manual
>>     mtu 1500
>>
>> auto eno3
>> iface eno3 inet manual
>>     mtu 1500
>>
>> auto eno4
>> iface eno4 inet manual
>>     mtu 1500
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>> Kind regards
>>
>> Tejali Sonawane-Bhujbal
>> Department Engineer - NTNU IT
>> Byggteknisk, s-226, Gløshaugen
>> Contact- +47-96708171
>> _______________________________________________
>> discuss mailing list
>> discuss at openvswitch.org
>> https://mail.openvswitch.org/mailman/listinfo/ovs-discuss
>>
>
> _______________________________________________
> discuss mailing list
> discuss at openvswitch.org
> https://mail.openvswitch.org/mailman/listinfo/ovs-discuss
>
>


-- 
Gilbert Standen
Creator Orabuntu-LXC
914-261-4594
gilbert at orabuntu-lxc.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.openvswitch.org/pipermail/ovs-discuss/attachments/20180613/e988a7d0/attachment-0001.html>