You have to start with the dhcp problem first in your case. “ip netns” on your 
controller node should list a dhcp name space,

ip netns
qdhcp-3fc234e5-335f-463d-ba1d-bcf1bdd8f479
qrouter-6df76d30-17fc-4024-8d01-4cfe007ab531

then session into that dhcp name space,

sudo ip netns exec qdhcp-3fc234e5-335f-463d-ba1d-bcf1bdd8f479 ifconfig

it should list a tap interface,

tapef85f5c3-c5 Link encap:Ethernet  HWaddr fa:16:3e:53:ad:f2

then check the dnsmasq is launched against that interface,

dnsmasq --no-hosts --no-resolv --strict-order --bind-interfaces 
--interface=tapef85f5c3-c5 -

Also I don’t see ovs physical bridge is been created in your show table.

HTH

Dennis Qin

From: discuss [mailto:discuss-boun...@openvswitch.org] On Behalf Of t22330033
Sent: Monday, May 19, 2014 1:54 AM
To: discuss@openvswitch.org
Subject: [ovs-discuss] network problem with vxlan

I set up openstack with one control node and one compute node with vxlan. my 
problem is that the instance in compute node always failed to get IP address by 
DHCP. I checked ovs flows and cannot figure out what the problem is. here is 
what I saw

$ovs-vsctl show
    Manager "tcp:172.22.11.43:6640<http://172.22.11.43:6640/>"
        is_connected: true
    Bridge br-int
        Controller "tcp:172.22.11.43:6633<http://172.22.11.43:6633/>"
            is_connected: true
        fail_mode: secure
        Port "tap766671cd-d8"
            tag: 1
            Interface "tap766671cd-d8"
        Port br-int
            Interface br-int
                type: internal
        Port patch-tun
            Interface patch-tun
                type: patch
                options: {peer=patch-int}
        Port "vxlan-172.31.0.125"
            Interface "vxlan-172.31.0.125"
                type: vxlan
                options: {key=flow, local_ip="172.22.11.43", 
remote_ip="172.31.0.125"}
    Bridge br-tun
        Port patch-int
            Interface patch-int
                type: patch
                options: {peer=patch-tun}
        Port "vxlan-ac1f007d"
            Interface "vxlan-ac1f007d"
                type: vxlan
                options: {in_key=flow, local_ip="172.22.11.43", out_key=flow, 
remote_ip="172.31.0.125"}
        Port br-tun
            Interface br-tun
                type: internal
    ovs_version: "2.1.90"

$ ovs-ofctl dump-flows br-int -O OpenFlow13
OFPST_FLOW reply (OF1.3) (xid=0x2):
 cookie=0x0, duration=2294.917s, table=0, n_packets=9, n_bytes=1434, 
send_flow_rem in_port=2,dl_src=fa:16:3e:d6:ee:31 
actions=set_field:0x3e9->tun_id,goto_table:10
 cookie=0x0, duration=2285.698s, table=0, n_packets=0, n_bytes=0, send_flow_rem 
priority=8192,in_port=2 actions=drop
 cookie=0x0, duration=2264.881s, table=0, n_packets=0, n_bytes=0, send_flow_rem 
tun_id=0x3e9,in_port=3 actions=goto_table:20
 cookie=0x0, duration=3133.421s, table=0, n_packets=0, n_bytes=0, send_flow_rem 
dl_type=0x88cc actions=CONTROLLER:56
 cookie=0x0, duration=2272.421s, table=10, n_packets=5, n_bytes=650, 
send_flow_rem priority=8192,tun_id=0x3e9 actions=goto_table:20
 cookie=0x0, duration=2262.715s, table=10, n_packets=4, n_bytes=784, 
send_flow_rem 
priority=16384,tun_id=0x3e9,dl_dst=01:00:00:00:00:00/01:00:00:00:00:00 
actions=output:3,goto_table:20
 cookie=0x0, duration=2267.424s, table=20, n_packets=0, n_bytes=0, 
send_flow_rem priority=8192,tun_id=0x3e9 actions=drop
 cookie=0x0, duration=2281.314s, table=20, n_packets=0, n_bytes=0, 
send_flow_rem tun_id=0x3e9,dl_dst=fa:16:3e:d6:ee:31 actions=output:2
 cookie=0x0, duration=2275.604s, table=20, n_packets=9, n_bytes=1434, 
send_flow_rem 
priority=16384,tun_id=0x3e9,dl_dst=01:00:00:00:00:00/01:00:00:00:00:00 
actions=output:2

I think in table 10, the DHCP request is output to port 3 which is of type 
vxlan and the host will send out an UDP packet to remote host. I tried to use 
tcpdump to capture the vxlan packet but saw nothing. Could anybody advise 
what's wrong here and how I should proceed to fix the problem? Thanks.
_______________________________________________
discuss mailing list
discuss@openvswitch.org
http://openvswitch.org/mailman/listinfo/discuss

Reply via email to