OpenvSwitch installation process-in vain

OpenvSwitch installation process-Alibaba Cloud has been researching SDN for the past three months and has a better understanding of SDN. Starting from today, I also hope to share my achievements online. First, we will introduce the installation process of OpenvSwitch (OVS. OVS version 1.4.2 introduced today. We hope to help you. The runtime environment is redhat6.2 (considering that 6.2 is because the company has a red hat with genuine services, and then the red hat has a good support for KVM, so I used the Red Hat system). The server is HP (the specific model is forgotten) OVS's current functions: (1) more flexible configuration. For example, if you have a server, if the performance is good, you can configure several vswitches, and the number of ports can be flexibly selected. For a vswitch, you can imagine that a virtual machine is the same, a server, the higher the configuration, the larger the number of virtual machines, the lower the cost. (2) The performance achieved by expensive common switches can be achieved through virtual switches, for example, the online speed between virtual machines and vswitches in VMware can easily reach 10 Gbps (3) supports visual communication, and the network can be configured through vswitches, we can use popular protocols on the current network to view traffic, such as NetFlow, sFlow, SPAN, RSPAN, and GRE tunnels (4) Support the LACP protocol ), LACP Based on the IEEE 802.3ad standard is a kind of dynamic link aggregation. Protocol (5) support for Virtual LAN (VLAN), VLAN relay mode based on the IEEE 802.1Q standard (6) Support for CCM, and CCM link monitoring based on the 802.1ag standard (7) support Spanning Tree Protocol (STP) and topology (8) Support for fine-grained QoS traffic control (9) Support for HFCS queue provision (10) · Support for monitoring each virtual interface. (11) · Support NIC binding source MAC load balancing, active backup and L4 Hash (12) · Support for OpenFlow protocol, IVP6 (13) · Support for multiple Ethernet tunneling protocols, for example, GRE, CAPWAP, IPsec, and GRE over IPsec (14) · supports binding Remote Configuration Protocol to local scripts (15) · supports multi-stream table forwarding pipeline cache (16) · install Openvswitch after porting it to the hardware development platform: (1) start to install Openvswitch. Determine the packages and versions to be installed before installation: gcc version 4.1 or higher pkg-config version 0.22 or higher autoconf version 2.64 or higher automake version 1.10 or higher m4 version 1.42 or higher python2.X, x> 4 (python3.0 or later is not recommended) (2) download the OVS Software Package http://openvswitch.org/releases/openvswitch-1.4.2.tar.gz Decompress the package to the system folder (3 )#. /boot. sh #. /configure -- prefix =/usr -- localstatedir =/var #. /configure CC = gcc #. /configure -- with-linux =/lib/modules/'uname-R'/build # make install the above three steps to complete the OVS installation, next, configure, initialize, and start OVS: #/sbin/remod bridge remove the Bridge module in linux # insmod datapath/linux/openvswitch_mod.ko # insmod datapath/linux/brcompat_mod.ko # mkdir-p/user/local/etc/openvswitch create ovs small database # ovs-tool create/usr/local/etc/openv Switch/conf. dbvswitchd/vswitch. ovsschema depends on the ovsdb module vswitch. ovsschema creates a data ovs-vswitchd.conf.db to store configuration information for a vswitch # ovsdb-server -- remote = punix:/local/var/run/openvswitch/db. sock \ -- remote = db: Open_vSwitch, manager_options \ -- private-key = db: SSl, private_key \ -- pidfile -- detach start ovsdb database server, the openvswitch virtual bridge module will use ovsdb-server to obtain the vswitch configuration # ovs-vsctl -- no-wait init to initialize OVS # ovs-vswitchd -- pidfile -- detach to start the OVS Module # ovs-brco When mpatd -- pidfile -- detach starts the OVS bridge module, all OVS installation and configuration are successfully completed. Now, you can have your own OVS vswitch. The following is a simple OVS vswitch: # ovs-vsctladd-br br0 # ovs-vsctl add-port br0 vif1.0 # ovs-vsctl add-port br0 eth0 # ifconfigbr up # service network restart the network