[ovs-discuss] VLAN setting problems with Openflow controller
blp at nicira.com
Tue May 1 09:11:56 PDT 2012
On Tue, May 01, 2012 at 05:19:47PM +0800, 楊雅倫 wrote:
> We are working with Open vSwitch testing above XenServer6.0. The version of Open vSwitch is 1.0.99.
> Now we meet a serious problem when setting VLAN.
> We have two virtual machines on two different physical hypervisors, VM_A and VM_B.
> We separately use ovs-vsctl add-br xxx xxx tag=x to set VLAN tag on two VMs, VM_A for VLAN 10, and VM_B for VLAN 20, and it works well (VM_A could not ping VM_B).
> However, when Open vSwitch connected to the NOX controller and the controller also enables pyswitch, the functionality of VLAN setting is missing.
> That is, the two VMs can ping each other.
When you connect an OpenFlow controller, the controller becomes
responsible for implementing whatever behavior you want, including
VLAN behavior. The controller can, if it is convenient, send packets
to the OpenFlow OFPP_NORMAL port, in which case Open vSwitch will
implement the behavior configured in its database.
> We also observe the packet formats with Wireshark, and the packet headers do not contain VLAN tag.
This should not be a surprise. These ports are access ports. Packets
sent or received on access ports do not contain VLAN tags.
More information about the discuss