The ovs-vlan-test utility has some limitations, for example, it does not use TCP in its tests. Also it
does not take into account MTU to detect potential edge cases. To overcome those limitations a new tool
was developed - ovs-test. ovs-test is currently supported only on Debian so, if possible, try to use that
on instead of ovs-vlan-test.
The ovs-vlan-test program may be used to check for problems sending 802.1Q traffic which may occur when
running Open vSwitch. These problems can occur when Open vSwitch is used to send 802.1Q traffic through
physical interfaces running certain drivers of certain Linux kernel versions. To run a test, configure
Open vSwitch to tag traffic originating from vlan_ip and forward it out the target interface. Then run
the ovs-vlan-test in client mode connecting to an ovs-vlan-test server. ovs-vlan-test will display “OK”
if it did not detect problems.
Some examples of the types of problems that may be encountered are:
• When NICs use VLAN stripping on receive they must pass a pointer to a vlan_group when reporting the
stripped tag to the networking core. If no vlan_group is in use then some drivers just drop the
extracted tag. Drivers are supposed to only enable stripping if a vlan_group is registered but not all
of them do that.
• On receive, some drivers handle priority tagged packets specially and don’t pass the tag onto the
network stack at all, so Open vSwitch never has a chance to see it.
• Some drivers size their receive buffers based on whether a vlan_group is enabled, meaning that a
maximum size packet with a VLAN tag will not fit if no vlan_group is configured.
• On transmit, some drivers expect that VLAN acceleration will be used if it is available, which can only
be done if a vlan_group is configured. In these cases, the driver may fail to parse the packet and
correctly setup checksum offloading or TSO.
ClientMode
An ovs-vlan-test client may be run on a host to check for VLAN connectivity problems. The client
must be able to establish HTTP connections with an ovs-vlan-test server located at the specified
control_ip address. UDP traffic sourced at vlan_ip should be tagged and directed out the interface
whose connectivity is being tested.
ServerMode
To conduct tests, an ovs-vlan-test server must be running on a host known not to have VLAN
connectivity problems. The server must have a control_ip on a non-VLAN network which clients can
establish connectivity with. It must also have a vlan_ip address on a VLAN network which clients
will use to test their VLAN connectivity. Multiple clients may test against a single ovs-vlan-test
server concurrently.