My Qemu Microcore image with Openvswitch and Quaggae is preconfigured for such things so feel free to use it.ġ. First you need to create database, configuration files, start services etc. Openvswitch is not a Cisco switch running Cisco IOS which you can configure right after device is booted. Picture 2 - QEMU Host Configuration Part1 - Basic Microcore, Openvswitch and Quagga Configurationīefore we start to configure Openvswitch we should be aware of initial configuration requirement for Openvswitch and Quagga. Below is a snapshot of Qemu host setting. You can download my Openvswitch Microcore Qemu image here.Īs for Ethernet card I suggest you to use i82557b Ethernet card type and assign at least 128 MB RAM for Microcore appliance. Picture 1 - Testing Bonding on Openvswitch As usual, our topology is created using GNS3 and Qemu images of Microcore with installed Openvswitch 1.2.2 and Quagga 0.99.20 on the top of Microcore. Let's say we have two Microcore Linux boxes connected with two links. This is the second option how to configure bonding without loading bonding module to Linux kernel. If you want to play with bonding configuration, check this lab for reference.Īs the tutorial is dedicated to configuring bonding with Openvswitch I am going to focus on this topic.

Configuration steps for Microcore are described here. The first option is to load bonding module to kernel and use ifenslave utility for its configuration. From what I know about bonding, they are two possibilities to configure it. This can crush intra-VLAN performance depending on a few factors such as CPU speed and the link speed between the switch chip and the CPU.Bonding is aggregation multiple links to single link in order to increase throughput and achieve redundancy in case one of links fails. If you use the bridge VLAN filtering method (the last one below) on the wrong type of device, you will force all intra-VLAN traffic to go to the CPU and back, even between ports on a switch. The following examples show a mix of tagged (ether1) and untagged (ether2,ether3) ports and three VLANs - 20,30, and 99. There's basically three different methods depending on the hardware you have. Otherwise you define them only in the bridge. VLANs are only configured in the switch menu if the switch chip is the best/correct place to perform all the VLAN tagging and translation.

Bonding with diffirence switch mikrotik