Ask Your Question
0

ovs (with --dpdk) doesn't forward packets to vxlan tunnels in an openstack environment

asked 2016-03-02 12:41:47 -0500

yby-developer gravatar image

updated 2016-03-02 13:09:06 -0500

I have a compute host with Debian 8, OVS 2.4.90, compiled for dpdk 2.0.0 and running with dpdk support (--dpdk), in an openstack environment with ODL on the controller as the OVS manager (so no neutron agent). A VM is created on the same compute I mentioned. The VM tries to obtain an IP from dhcp. It sends BOOTP packets.

Those packets are matched against:

cookie=0x0, duration=575.331s, table=110, n_packets=84, n_bytes=16056, priority=16383,reg0=0x1,tun_id=0xc9,dl_dst=01:00:00:00:00:00/01:00:00:00:00:00 actions=output:8,output:4,output:1,output:5,output:6,output:7

This is how the bridge looks like:

OFPT_FEATURES_REPLY (OF1.3) (xid=0x2): dpid:000072b0e2b1ed4c
n_tables:254, n_buffers:256
capabilities: FLOW_STATS TABLE_STATS PORT_STATS GROUP_STATS QUEUE_STATS
OFPST_PORT_DESC reply (OF1.3) (xid=0x3):
 1(vxlan-10.53.6.1): addr:7e:f9:5f:c9:86:6a
     config:     0
     state:      0
     speed: 0 Mbps now, 0 Mbps max
 3(patch-ext): addr:96:ee:48:d0:58:23
     config:     0
     state:      0
     speed: 0 Mbps now, 0 Mbps max
 4(vxlan-10.53.6.1): addr:e2:f9:b2:7b:47:9f
     config:     0
     state:      0
     speed: 0 Mbps now, 0 Mbps max
 5(vxlan-10.53.6.1): addr:8e:26:fc:b8:b9:cb
     config:     0
     state:      0
     speed: 0 Mbps now, 0 Mbps max
 6(vxlan-10.53.6.1): addr:6a:69:b6:9a:47:56
     config:     0
     state:      0
     speed: 0 Mbps now, 0 Mbps max
 7(vxlan-10.53.6.1): addr:de:ed:fc:3f:7c:c3
     config:     0
     state:      0
     speed: 0 Mbps now, 0 Mbps max
 8(tap79cdb725-73): addr:fe:16:3e:b0:bc:10
     config:     0
     state:      0
     current:    10MB-FD COPPER
     speed: 10 Mbps now, 0 Mbps max
 LOCAL(br-int): addr:72:b0:e2:b1:ed:4c
     config:     PORT_DOWN
     state:      LINK_DOWN
     current:    10MB-FD COPPER
     speed: 10 Mbps now, 0 Mbps max
OFPT_GET_CONFIG_REPLY (OF1.3) (xid=0x5): frags=normal miss_send_len=0

The local_ip configured on the bridge:

root@BASE-CCP-CPN-N0003-NETCLM:~# ovs-vsctl get Open_vSwitch . other_config:local_ip
"10.53.6.16"

The interface:

root@BASE-CCP-CPN-N0003-NETCLM:~# ifconfig eth1
eth1      Link encap:Ethernet  HWaddr b0:5a:da:02:10:20
          inet addr:10.53.6.16  Bcast:10.53.6.255  Mask:255.255.255.0
          inet6 addr: fe80::b25a:daff:fe02:1020/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:5037083366 errors:0 dropped:100 overruns:0 frame:0
          TX packets:5068594045 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:835697551734 (778.3 GiB)  TX bytes:886055918384 (825.2 GiB)

So I expect the packet to be flooded to all vxlan tunnels, ports 1 and 4-7 (and seems like it's also supposed to output it back to port 8 for some reason). However, when I tcpdump -i eth1, I don't see the BOOTP packets vxlan-encapsulated (or even not encapsulated for that matter).

A similar second compute, running OVS 2.3 ... (more)

edit retag flag offensive close merge delete

1 answer

Sort by ยป oldest newest most voted
0

answered 2016-03-02 13:10:54 -0500

yby-developer gravatar image

problem solved: had to set datapath_type from netdev to system, since eth1 wasn't actually a dpdk interface:

ovs-vsctl set Bridge br-int datapath_type=system
edit flag offensive delete link more

Your Answer

Please start posting anonymously - your entry will be published after you log in or create a new account.

Add Answer

Get to know Ask OpenStack

Resources for moderators

Question Tools

1 follower

Stats

Asked: 2016-03-02 12:41:47 -0500

Seen: 785 times

Last updated: Mar 02 '16