Uninstall of OvS

Use Apt-get installed Openvswitch, and then uninstall good trouble Isaac, and there is no relevant information about how to delete, hereby record, I hope there is a reference

First remove all new virtual bridges on the server using OvS

Then remove the original kernel from sudo rmmod openvswitch

And then stop the service.

sudo killall ovsdb-server

sudo killall ovs-vswitchd

Finally follow the documentation (many commands require sudo, please note that the red is the command used)

Once you has installed all the prerequisites listed above in the Base
Prerequisites section, follow the procedure below to build.

1. If you pulled the sources directly from an Open vSwitch Git tree,
Run boot.sh in the top source directory:

%./boot.sh

2. In the top source directory, configure the running the
Configure script. Can usually invoke configure without any
Arguments

%./configure

By default all files is installed under/usr/local. If you want
To install into, e.g,/usr And/var instead of/usr/local and
/usr/local/var, add options as shown here:

%./configure--PREFIX=/USR--localstatedir=/var

To use a specific C compiler for compiling Open vSwitch user
Programs, also specify it on the Configure command line, like so:

%./configure cc=gcc-4.2

To build the Linux kernel module, so that can run the
kernel-based switch, pass the location of the kernel build
directory on--with-linux. For example, to-build for a running
Instance of Linux:

%./configure--with-linux=/lib/modules/' uname-r '/build

If you wish to build the kernel module for a architecture other
than the architecture of the machine used for the build, your may
Specify the kernel architecture string using the Karch variable
When invoking the Configure script. For example, to-build for MIPS
With Linux:

%./configure--with-linux=/path/to/linux karch=mips

The Configure script accepts a number of other options and honors
Additional environment variables. For a full list, invoke
Configure with the--HELP option.

3. Run make in the top source directory:

% make

4. Become root by running ' su ' or another program.

5. Run "Makeinstall" To install the executables and manpages into the
Running system, by default under/usr/local.

6. If you built kernel modules, your may load them with "insmod", e.g.:

% Insmod Datapath/linux/openvswitch_mod.ko

Need to specify a full path to insmod, e.g./sbin/insmod.
To verify the modules has been loaded, run "/sbin/lsmod" and
Check that Openvswitch_mod is listed.

If the "Insmod" operation fails, look at the last few kernel log
Messages (e.g. with "DMESG | Tail "):

-The message "Openvswitch_mod:exports duplicate symbol
Br_should_route_hook (owned by bridge) "means the bridge
Module is loaded. Run "/sbin/rmmod Bridge" to remove it.

If "/sbin/rmmod Bridge" fails with "Error:module Bridge does
Not exist In/proc/modules "and then the bridge was compiled into
The kernel, rather than as a module. Open VSwitch does not
Support the This configuration (see "Build Requirements", above).

-The message "Openvswitch_mod:exports duplicate symbol
Dp_ioctl_hook (owned by Ofdatapath) "means that the Ofdatapath
Module from the OpenFlow reference implementation is loaded.
Run "/sbin/rmmod Ofdatapath" to remove it. (You might has to
Delete any existing datapaths beforehand, using the "Dpctl"
Program included with the OpenFlow reference implementation.
"Ovs-dpctl" won't work.)

-Otherwise, the most likely problem are that Open VSwitch was
Built for a kernel different from the one to which you are
Trying to load it. Run "Modinfo" on Openvswitch_mod.ko and on
A module built for the running kernel, e.g.:

%/sbin/modinfo Openvswitch_mod.ko
%/sbin/modinfo/lib/modules/' uname-r '/kernel/net/bridge/bridge.ko

Compare the "vermagic" lines output by the commands. If
They differ, then Open VSwitch is built for the wrong kernel.

-If You decide to report a bug or ask a question related to
Module loading, please include the output from the "DMESG" and
"Modinfo" commands mentioned above.

There is a optional module parameter to Openvswitch_mod.ko called
Vlan_tso that enables TCP segmentation offload over VLANs on NICs
That's support it. Many drivers do not expose support for TSO on VLANs
In a-on-the-Open VSwitch can use and there is no-to-detect
Whether the case. If you know that your particular driver can
Handle it (for example by testing sending large TCP packets over VLANs)
Then passing in a value of 1 may improve performance. Modules built for
Linux Kernels 2.6.37 and later, as well as specially patched versions
Of earlier kernels, do not need this and does not have the this parameter. If
You don't understand what this means or does not know if your driver
Would work, does not set this.

7. Initialize the configuration database using Ovsdb-tool, e.g.:

% mkdir-p/usr/local/etc/openvswitch
% Ovsdb-tool create/usr/local/etc/openvswitch/conf.db vswitchd/vswitch.ovsschema (possible file directory already available, change create to convert)

Startup
=======

Before starting OVS-VSWITCHD itself, you need-start its
Configuration database, Ovsdb-server. Each machine on which Open
VSwitch is installed should run its own copy of Ovsdb-server.
Configure it to use the database created during step 7 of
installation, above, to listen in a Unix domain socket, to connect to
Any managers specified in the database itself, and to use the SSL
Configuration in the database:

% Ovsdb-server--remote=punix:/usr/local/var/run/openvswitch/db.sock \
--remote=db:open_vswitch,manager_options \
--private-key=db:ssl,private_key \
--certificate=db:ssl,certificate \
--bootstrap-ca-cert=db:ssl,ca_cert \
--pidfile--detach

(If you built Open VSwitch without SSL support and then omit
--private-key,--certificate, and--bootstrap-ca-cert.)

Then initialize the database using Ovs-vsctl. This was only
Necessary the first time after you create the database with
Ovsdb-tool (but running it was harmless):

% Ovs-vsctl--no-wait Init

Then start the main Open vSwitch Daemon, telling it to connect to the
Same Unix domain socket:

% Ovs-vswitchd--pidfile--detach

Uninstall of OvS