[OVSDB-91] VM ingress rule is not installed for vlan networking Created: 15/Sep/14  Updated: 19/Oct/17  Resolved: 25/Sep/14

Status: Resolved
Project: ovsdb
Component/s: openstack.net-virt-providers
Affects Version/s: unspecified
Fix Version/s: None

Type: Bug
Reporter: Sam Hague Assignee: Unassigned
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Operating System: Linux
Platform: PC


External issue ID: 1885

 Description   

When using vlan network the vm ingress rule is not installed. The flow should look like:

[odl@fedora41 devstack]$ sudo ovs-ofctl --protocol=OpenFlow13 dump-flows br-int
OFPST_FLOW reply (OF1.3) (xid=0x2):
cookie=0x0, duration=4.381s, table=0, n_packets=9, n_bytes=634, send_flow_rem in_port=1,vlan_tci=0x0000/0x1fff,dl_src=fa:16:3e:96:59:14 actions=push_vlan:0x8100,set_field:6097->vlan_vid,goto_table:20



 Comments   
Comment by Vishal Patil [ 16/Sep/14 ]

The openflow rules for vlan seem to be completely broken. I do not see a "strip_vlan" flow for egress traffic as well.

Comment by Vishal Patil [ 16/Sep/14 ]

I am marking this blocking since vlans + Openstack is completely broken without the fix for this problem.

Comment by Ed Warnicke [ 23/Sep/14 ]

Vishal Patil, Sam Hague... are you not programming flows, or are you not seeing them come through?

Comment by Vishal Patil [ 23/Sep/14 ]

I am not programming any flows. I am driving ODL using OpenStack (Neutron). I am basically creating Openstack tenant networks of type vlan.

Comment by Dave Tucker [ 23/Sep/14 ]

https://git.opendaylight.org/gerrit/11198

Comment by Sam Hague [ 23/Sep/14 ]

This bug is closely related to OVSDB-109. OVSDB-109 implements the rest of the vlan fixes.

Comment by Vishal Patil [ 24/Sep/14 ]

Folks,

I just checkout the latest OVSDB and tried testing this fix. I think the problem is still not fixed.

Check the openflow rules on the compute node

odl@cmp11 devstack]$ sudo ovs-ofctl -O Openflow13 dump-flows br-int
OFPST_FLOW reply (OF1.3) (xid=0x2):
cookie=0x0, duration=47.778s, table=0, n_packets=2, n_bytes=128, send_flow_rem in_port=1,dl_vlan=101 actions=goto_table:20
cookie=0x0, duration=49.301s, table=0, n_packets=0, n_bytes=0, send_flow_rem priority=8192,in_port=2 actions=drop
cookie=0x0, duration=212.682s, table=0, n_packets=7, n_bytes=938, send_flow_rem dl_type=0x88cc actions=CONTROLLER:65535
cookie=0x0, duration=49.784s, table=0, n_packets=7, n_bytes=790, send_flow_rem in_port=2,vlan_tci=0x0000/0x1fff,dl_src=fa:16:3e:7a:9d:01 actions=push_vlan:0x8100,set_field:101->vlan_vid,goto_table:20
cookie=0x0, duration=48.286s, table=110, n_packets=0, n_bytes=0, send_flow_rem priority=8192,dl_vlan=101 actions=output:1
cookie=0x0, duration=47.224s, table=110, n_packets=0, n_bytes=0, send_flow_rem priority=16384,dl_vlan=101,dl_dst=01:00:00:00:00:00/01:00:00:00:00:00 actions=output:1,strip_vlan,output:2
cookie=0x0, duration=48.796s, table=110, n_packets=0, n_bytes=0, send_flow_rem dl_vlan=101,dl_dst=fa:16:3e:7a:9d:01 actions=strip_vlan,output:2

The first rule says "goto_table:20" but there are no rules for table 20. As a result the packets are getting dropped.

Comment by Sam Hague [ 24/Sep/14 ]

Vishal,

do you have the latest code? The table 20 (and other table) flows are programmed via the pipeline code outside of the vlan code.

The rest of the flows look good for the vlan's. But you need to have the pipeline flows in place also.

The pipeline flows would be installed when the switch first connects to ODL. Is it possible that connection went down or something and the pipeline flows were not installed or removed? The pipeline flows look like the below and should be there as soon as the switch connects to ODL.

Thanks, Sam

cookie=0x0, duration=1763.032s, table=0, n_packets=881, n_bytes=45681, send_flow_rem priority=0 actions=goto_table:20
cookie=0x0, duration=1763.868s, table=0, n_packets=0, n_bytes=0, send_flow_rem dl_type=0x88cc actions=CONTROLLER:65535
cookie=0x0, duration=1762.531s, table=20, n_packets=1065, n_bytes=63425, send_flow_rem priority=0 actions=goto_table:30
cookie=0x0, duration=1762.026s, table=30, n_packets=1065, n_bytes=63425, send_flow_rem priority=0 actions=goto_table:40
cookie=0x0, duration=1761.523s, table=40, n_packets=1065, n_bytes=63425, send_flow_rem priority=0 actions=goto_table:50
cookie=0x0, duration=1761.019s, table=50, n_packets=1065, n_bytes=63425, send_flow_rem priority=0 actions=goto_table:60
cookie=0x0, duration=1760.515s, table=60, n_packets=1065, n_bytes=63425, send_flow_rem priority=0 actions=goto_table:70
cookie=0x0, duration=1760.011s, table=70, n_packets=1065, n_bytes=63425, send_flow_rem priority=0 actions=goto_table:80
cookie=0x0, duration=1759.507s, table=80, n_packets=1065, n_bytes=63425, send_flow_rem priority=0 actions=goto_table:90
cookie=0x0, duration=1759.003s, table=90, n_packets=1065, n_bytes=63425, send_flow_rem priority=0 actions=goto_table:100
cookie=0x0, duration=1758.496s, table=100, n_packets=1065, n_bytes=63425, send_flow_rem priority=0 actions=goto_table:110
cookie=0x0, duration=1757.988s, table=110, n_packets=889, n_bytes=46261, send_flow_rem priority=0 actions=drop

Comment by Vishal Patil [ 24/Sep/14 ]

Sam

I am seeing the pipeline flows being installed correctly on the controller node but not on the compute nodes.

Following are the flows on the controller node

  • Vishal

[odl@ctrl devstack]$ sudo ovs-ofctl -O Openflow13 dump-flows br-int
OFPST_FLOW reply (OF1.3) (xid=0x2):
cookie=0x0, duration=8069.175s, table=0, n_packets=89, n_bytes=5684, send_flow_rem in_port=1,dl_vlan=101 actions=goto_table:20
cookie=0x0, duration=8070.759s, table=0, n_packets=0, n_bytes=0, send_flow_rem priority=8192,in_port=2 actions=drop
cookie=0x0, duration=8198.377s, table=0, n_packets=273, n_bytes=36582, send_flow_rem dl_type=0x88cc actions=CONTROLLER:65535
cookie=0x0, duration=8197.406s, table=0, n_packets=317, n_bytes=58240, send_flow_rem priority=0 actions=goto_table:20
cookie=0x0, duration=8072.111s, table=0, n_packets=114, n_bytes=5224, send_flow_rem in_port=2,vlan_tci=0x0000/0x1fff,dl_src=fa:16:3e:66:cd:d2 actions=push_vlan:0x8100,set_field:101->vlan_vid,goto_table:20
cookie=0x0, duration=8196.904s, table=20, n_packets=520, n_bytes=69148, send_flow_rem priority=0 actions=goto_table:30
cookie=0x0, duration=8196.4s, table=30, n_packets=520, n_bytes=69148, send_flow_rem priority=0 actions=goto_table:40
cookie=0x0, duration=8195.896s, table=40, n_packets=520, n_bytes=69148, send_flow_rem priority=0 actions=goto_table:50
cookie=0x0, duration=8195.386s, table=50, n_packets=520, n_bytes=69148, send_flow_rem priority=0 actions=goto_table:60
cookie=0x0, duration=8194.88s, table=60, n_packets=520, n_bytes=69148, send_flow_rem priority=0 actions=goto_table:70
cookie=0x0, duration=8194.378s, table=70, n_packets=520, n_bytes=69148, send_flow_rem priority=0 actions=goto_table:80
cookie=0x0, duration=8193.881s, table=80, n_packets=520, n_bytes=69148, send_flow_rem priority=0 actions=goto_table:90
cookie=0x0, duration=8193.378s, table=90, n_packets=520, n_bytes=69148, send_flow_rem priority=0 actions=goto_table:100
cookie=0x0, duration=8192.873s, table=100, n_packets=520, n_bytes=69148, send_flow_rem priority=0 actions=goto_table:110
cookie=0x0, duration=8069.715s, table=110, n_packets=85, n_bytes=3676, send_flow_rem priority=8192,dl_vlan=101 actions=output:1
cookie=0x0, duration=8068.677s, table=110, n_packets=34, n_bytes=1798, send_flow_rem priority=16384,dl_vlan=101,dl_dst=01:00:00:00:00:00/01:00:00:00:00:00 actions=output:1,strip_vlan,output:2
cookie=0x0, duration=8192.367s, table=110, n_packets=319, n_bytes=58426, send_flow_rem priority=0 actions=drop
cookie=0x0, duration=8070.16s, table=110, n_packets=82, n_bytes=5248, send_flow_rem dl_vlan=101,dl_dst=fa:16:3e:66:cd:d2 actions=strip_vlan,output:2

Comment by Sam Hague [ 24/Sep/14 ]

Vishal,

that is a different issue then. Nothing to do with the vlan flows as they are being installed. It might be related to https://bugs.opendaylight.org/show_bug.cgi?id=2024.

Sam

Comment by Vishal Patil [ 24/Sep/14 ]

Sam, I am not seeing that exception in my ODL logs.

I will re-run the test tomorrow after checking out ovsdb again.

Comment by Vishal Patil [ 25/Sep/14 ]

I have verified that the fix works with latest OVSDB. Sorry for the confusion Sam.

Comment by Sam Hague [ 25/Sep/14 ]

(In reply to Vishal Patil from comment #12)
> I have verified that the fix works with latest OVSDB. Sorry for the
> confusion Sam.

Great! Thanks Vishal.

Generated at Wed Feb 07 20:35:29 UTC 2024 using Jira 8.20.10#820010-sha1:ace47f9899e9ee25d7157d59aa17ab06aee30d3d.