> Are you still using vconfig to configure the vlans or are you only using OVS > to handle all of the vlan functionality?
I am testing both of them. My server has 5 ethernet port, and I use vconfig to configure vlans in some port, and also using OVS to handle vlan functions in other port and eth0 for connection SSH. > If you are using OVS to do the vlans, you should set the tag field on the > internal port and leave the other ports alone to trunk. Yes, for eth1 and eth2, I set tag field only. And empty trunks field in Port table. > If this still doesn't work, you can use tcpdump to see what is going out on > the wire and ovs-dpctl dump-flows to see if packets are being dropped. I already did tcpdump but, it doesn’t show any packets through those vlans. And ovs-dpctl dump flows shows only 1 drop,(ip0.0.0.0->0.0.0.0 port 0->0) Belows are the brief dump-flows. [r...@vlan stg]# ovs-dpctl dump-flows dp0 tunnel00000000:in_port0001:vlan65535:pcp0 mac00:19:30:98:e2:8c->01:80:c2:00:00:00 type05ff proto0 tos0 ip0.0.0.0->0.0.0.0 port0->0, packets:2255, bytes:135300, used:0.029s, actions:drop tunnel00000000:in_port0001:vlan65535:pcp0 mac00:26:9e:b5:d0:b3->ff:ff:ff:ff:ff:ff type0806 proto1 tos0 ip10.0.3.17->10.0.3.1 port0->0, packets:2, bytes:120, used:1.981s, actions:0,set_vlan(200),9,3,5,4 tunnel00000000:in_port0001:vlan65535:pcp0 mac00:19:30:98:e2:8c->00:19:30:98:e2:8c type9000 proto0 tos0 ip0.0.0.0->0.0.0.0 port0->0, packets:0, bytes:0, used:never, actions:drop tunnel00000000:in_port0001:vlan65535:pcp0 mac00:1a:a0:38:0d:05->ff:ff:ff:ff:ff:ff type0806 proto1 tos0 ip192.168.10.1->192.168.10.13 port0->0, packets:2, bytes:120, used:0.740s, actions:0,set_vlan(200),9,3,5,4 tunnel00000000:in_port0001:vlan65535:pcp0 mac00:1a:a0:38:0d:05->ff:ff:ff:ff:ff:ff type0806 proto1 tos0 ip192.168.10.1->192.168.10.12 port0->0, packets:0, bytes:0, used:never, actions:0,set_vlan(200),9,3,5,4 tunnel00000000:in_port0004:vlan65535:pcp0 mac00:16:3e:1a:69:3b->00:16:3e:1b:c4:1e type0800 proto1 tos0 ip10.0.3.124->10.0.3.123 port0->0, packets:208, bytes:15392, used:0.293s, actions:3 tunnel00000000:in_port0001:vlan65535:pcp0 mac00:1a:a0:38:0d:05->ff:ff:ff:ff:ff:ff type0806 proto1 tos0 ip192.168.10.1->192.168.10.11 port0->0, packets:2, bytes:120, used:3.548s, actions:0,set_vlan(200),9,3,5,4 tunnel00000000:in_port0001:vlan65535:pcp0 mac00:16:3e:e1:1e:bc->ff:ff:ff:ff:ff:ff type0800 proto17 tos0 ip169.254.28.134->169.254.255.255 port138->138, packets:0, bytes:0, used:never, actions:0,set_vlan(200),9,3,5,4 tunnel00000000:in_port0003:vlan65535:pcp0 mac00:16:3e:1b:c4:1e->00:16:3e:1a:69:3b type0800 proto1 tos0 ip10.0.3.123->10.0.3.124 port8->0, packets:208, bytes:15392, used:0.308s, actions:4 [r...@vlan stg]# ovs-dpctl dump-flows dp1 tunnel00000000:in_port0002:vlan65535:pcp0 mac00:16:3e:2a:12:8c->00:15:17:b8:37:76 type0800 proto1 tos0 ip10.0.5.201->10.0.5.101 port8->0, packets:1, bytes:74, used:2.042s, actions:3 [r...@vlan stg]# ovs-dpctl dump-flows dp0 tunnel00000000:in_port0001:vlan65535:pcp0 mac00:19:30:98:e2:8c->01:80:c2:00:00:00 type05ff proto0 tos0 ip0.0.0.0->0.0.0.0 port0->0, packets:2259, bytes:135540, used:0.044s, actions:drop tunnel00000000:in_port0001:vlan65535:pcp0 mac00:16:3e:e1:1e:bc->ff:ff:ff:ff:ff:ff type0800 proto17 tos0 ip0.0.0.0->255.255.255.255 port68->67, packets:0, bytes:0, used:never, actions:0,set_vlan(200),9,3,5,4 tunnel00000000:in_port0001:vlan65535:pcp0 mac00:26:9e:82:31:b9->ff:ff:ff:ff:ff:ff type0800 proto17 tos16 ip10.0.3.16->255.255.255.255 port68->67, packets:0, bytes:0, used:never, actions:0,set_vlan(200),9,3,5,4 tunnel00000000:in_port0004:vlan65535:pcp0 mac00:16:3e:1a:69:3b->00:16:3e:1b:c4:1e type0800 proto1 tos0 ip10.0.3.124->10.0.3.123 port0->0, packets:216, bytes:15984, used:0.217s, actions:3 tunnel00000000:in_port0001:vlan65535:pcp0 mac00:26:9e:b5:ce:d3->ff:ff:ff:ff:ff:ff type0806 proto1 tos0 ip10.0.3.21->10.0.3.1 port0->0, packets:2, bytes:120, used:4.176s, actions:0,set_vlan(200),9,3,5,4 tunnel00000000:in_port0003:vlan65535:pcp0 mac00:16:3e:1b:c4:1e->00:16:3e:1a:69:3b type0800 proto1 tos0 ip10.0.3.123->10.0.3.124 port8->0, packets:216, bytes:15984, used:0.232s, actions:4 From: Jesse Gross [mailto:je...@nicira.com] Sent: Thursday, May 27, 2010 11:12 AM To: 신용진 Cc: Ben Pfaff; discuss@openvswitch.org Subject: Re: [ovs-discuss] How to set trunk on open vswitch? On Wed, May 26, 2010 at 6:58 PM, 신용진 <akay...@gmail.com> wrote: Hmm, At first, I do not set any values both of "tag", and "trunks" But servers and VMs cannot communicate each other. So, I searched about "trunk" on openvswitch, and I set the value on them. Let's suppose that I put an IP on VLAN as 10.10.10.101 at SV1(Server1). When I ping to 10.10.10.101 from other server(SV2) (those two servers(SV1, SV2) are connected to same physical server) Then, the SV1 replies for pinging 10.10.10.101. However, the VLAN(10.10.10.101) can not going out anywhere. When I ping, or traceroute through that VLAN, it doesn't works. I can see the RX bytes and TX bytes with "ifconfig". TX bytes seems OK, but RX bytes is always 0. Are you still using vconfig to configure the vlans or are you only using OVS to handle all of the vlan functionality? If you are using OVS to do the vlans, you should set the tag field on the internal port and leave the other ports alone to trunk. If this still doesn't work, you can use tcpdump to see what is going out on the wire and ovs-dpctl dump-flows to see if packets are being dropped.
_______________________________________________ discuss mailing list discuss@openvswitch.org http://openvswitch.org/mailman/listinfo/discuss_openvswitch.org
