1 .TH ovs\-vlan\-test 1 "December 2010" "Open vSwitch" "Open vSwitch Manual"
4 \fBovs\-vlan\-test\fR \- check Linux drivers for problems with vlan traffic
7 \fBovs\-vlan\-test\fR [\fB\-s\fR | \fB\-\-server\fR] \fIcontrol_ip\fR \fIvlan_ip\fR
11 The \fBovs\-vlan\-test\fR utility has some limitations, for example, it does
12 not use TCP in its tests. Also it does not take into account MTU to detect
13 potential edge cases. To overcome those limitations a new tool was
14 developed \- \fBovs\-test\fR. \fBovs\-test\fR is currently supported only
15 on Debian so, if possible try to use that on instead of \fBovs\-vlan\-test\fR.
17 The \fBovs\-vlan\-test\fR program may be used to check for problems sending
18 802.1Q traffic which may occur when running Open vSwitch. These problems can
19 occur when Open vSwitch is used to send 802.1Q traffic through physical
20 interfaces running certain drivers of certain Linux kernel versions. To run a
21 test, configure Open vSwitch to tag traffic originating from \fIvlan_ip\fR and
22 forward it out the target interface. Then run the \fBovs\-vlan\-test\fR in
23 client mode connecting to an \fBovs\-vlan\-test\fR server.
24 \fBovs\-vlan\-test\fR will display "OK" if it did not detect problems.
26 Some examples of the types of problems that may be encountered are:
27 .so utilities/ovs-vlan-bugs.man
30 An \fBovs\-vlan\-test\fR client may be run on a host to check for VLAN
31 connectivity problems. The client must be able to establish HTTP connections
32 with an \fBovs\-vlan\-test\fR server located at the specified \fIcontrol_ip\fR
33 address. UDP traffic sourced at \fIvlan_ip\fR should be tagged and directed out
34 the interface whose connectivity is being tested.
37 To conduct tests, an \fBovs\-vlan\-test\fR server must be running on a host
38 known not to have VLAN connectivity problems. The server must have a
39 \fIcontrol_ip\fR on a non\-VLAN network which clients can establish
40 connectivity with. It must also have a \fIvlan_ip\fR address on a VLAN network
41 which clients will use to test their VLAN connectivity. Multiple clients may
42 test against a single \fBovs\-vlan\-test\fR server concurrently.
47 \fB\-s\fR, \fB\-\-server\fR
52 Display the Linux kernel version and driver of \fBeth1\fR.
59 Set up a bridge which forwards traffic originating from \fB1.2.3.4\fR out
60 \fBeth1\fR with VLAN tag 10.
62 .B ovs\-vsctl \-\- add\-br vlan\-br \(rs
64 .B \-\- add\-port vlan\-br eth1 \(rs
66 .B \-\- add\-port vlan\-br vlan\-br\-tag tag=10 \(rs
68 .B \-\- set Interface vlan\-br\-tag type=internal
70 .B ifconfig vlan\-br\-tag up 1.2.3.4
73 Run an \fBovs\-vlan\-test\fR server listening for client control traffic on
74 172.16.0.142 port 8080 and VLAN traffic on the default port of 1.2.3.3.
76 .B ovs\-vlan\-test \-s 172.16.0.142:8080 1.2.3.3
79 Run an \fBovs\-vlan\-test\fR client with a control server located at
80 172.16.0.142 port 8080 and a local VLAN ip of 1.2.3.4.
82 .B ovs\-vlan\-test 172.16.0.142:8080 1.2.3.4
88 .BR ovs\-vswitchd (8),