https://jira.opendaylight.org This file is an XML representation of an issue en-us 8.20.10 820010 22-06-2022 https://jira.opendaylight.org/browse/OVSDB-91 ovsdb <p>When using vlan network the vm ingress rule is not installed. The flow should look like:</p> <p><span class="error">&#91;odl@fedora41 devstack&#93;</span>$ sudo ovs-ofctl --protocol=OpenFlow13 dump-flows br-int<br/> OFPST_FLOW reply (OF1.3) (xid=0x2):<br/> 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-&gt;vlan_vid,goto_table:20</p> <p>Operating System: Linux<br/> Platform: PC</p> OVSDB-91

VM ingress rule is not installed for vlan networking

Bug Resolved Done Unassigned Sam Hague Mon, 15 Sep 2014 17:21:48 +0000 Thu, 19 Oct 2017 21:29:09 +0000 Thu, 25 Sep 2014 14:27:50 +0000 unspecified openstack.net-virt-providers 0 4 <p>The openflow rules for vlan seem to be completely broken. I do not see a "strip_vlan" flow for egress traffic as well.</p> <p>I am marking this blocking since vlans + Openstack is completely broken without the fix for this problem.</p> <p>Vishal Patil, Sam Hague... are you not programming flows, or are you not seeing them come through?</p> <p>I am not programming any flows. I am driving ODL using OpenStack (Neutron). I am basically creating Openstack tenant networks of type vlan.</p> <p><a href="https://git.opendaylight.org/gerrit/11198" class="external-link" target="_blank" rel="nofollow noopener">https://git.opendaylight.org/gerrit/11198</a></p> <p>This bug is closely related to <a href="https://jira.opendaylight.org/browse/OVSDB-109" title="Vlan flows needs merging from traditional rules to a single L2Fwding Service. Similar to OVSDB-107" class="issue-link" data-issue-key="OVSDB-109"><del>OVSDB-109</del></a>. <a href="https://jira.opendaylight.org/browse/OVSDB-109" title="Vlan flows needs merging from traditional rules to a single L2Fwding Service. Similar to OVSDB-107" class="issue-link" data-issue-key="OVSDB-109"><del>OVSDB-109</del></a> implements the rest of the vlan fixes.</p> <p>Folks,</p> <p>I just checkout the latest OVSDB and tried testing this fix. I think the problem is still not fixed.</p> <p>Check the openflow rules on the compute node</p> <p>odl@cmp11 devstack]$ sudo ovs-ofctl -O Openflow13 dump-flows br-int <br/> OFPST_FLOW reply (OF1.3) (xid=0x2):<br/> 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<br/> cookie=0x0, duration=49.301s, table=0, n_packets=0, n_bytes=0, send_flow_rem priority=8192,in_port=2 actions=drop<br/> cookie=0x0, duration=212.682s, table=0, n_packets=7, n_bytes=938, send_flow_rem dl_type=0x88cc actions=CONTROLLER:65535<br/> 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-&gt;vlan_vid,goto_table:20<br/> cookie=0x0, duration=48.286s, table=110, n_packets=0, n_bytes=0, send_flow_rem priority=8192,dl_vlan=101 actions=output:1<br/> 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<br/> 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</p> <p>The first rule says "goto_table:20" but there are no rules for table 20. As a result the packets are getting dropped.</p> <p>Vishal,</p> <p>do you have the latest code? The table 20 (and other table) flows are programmed via the pipeline code outside of the vlan code.</p> <p>The rest of the flows look good for the vlan's. But you need to have the pipeline flows in place also.</p> <p>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.</p> <p>Thanks, Sam</p> <p>cookie=0x0, duration=1763.032s, table=0, n_packets=881, n_bytes=45681, send_flow_rem priority=0 actions=goto_table:20<br/> cookie=0x0, duration=1763.868s, table=0, n_packets=0, n_bytes=0, send_flow_rem dl_type=0x88cc actions=CONTROLLER:65535<br/> cookie=0x0, duration=1762.531s, table=20, n_packets=1065, n_bytes=63425, send_flow_rem priority=0 actions=goto_table:30<br/> cookie=0x0, duration=1762.026s, table=30, n_packets=1065, n_bytes=63425, send_flow_rem priority=0 actions=goto_table:40<br/> cookie=0x0, duration=1761.523s, table=40, n_packets=1065, n_bytes=63425, send_flow_rem priority=0 actions=goto_table:50<br/> cookie=0x0, duration=1761.019s, table=50, n_packets=1065, n_bytes=63425, send_flow_rem priority=0 actions=goto_table:60<br/> cookie=0x0, duration=1760.515s, table=60, n_packets=1065, n_bytes=63425, send_flow_rem priority=0 actions=goto_table:70<br/> cookie=0x0, duration=1760.011s, table=70, n_packets=1065, n_bytes=63425, send_flow_rem priority=0 actions=goto_table:80<br/> cookie=0x0, duration=1759.507s, table=80, n_packets=1065, n_bytes=63425, send_flow_rem priority=0 actions=goto_table:90<br/> cookie=0x0, duration=1759.003s, table=90, n_packets=1065, n_bytes=63425, send_flow_rem priority=0 actions=goto_table:100<br/> cookie=0x0, duration=1758.496s, table=100, n_packets=1065, n_bytes=63425, send_flow_rem priority=0 actions=goto_table:110<br/> cookie=0x0, duration=1757.988s, table=110, n_packets=889, n_bytes=46261, send_flow_rem priority=0 actions=drop</p> <p>Sam</p> <p>I am seeing the pipeline flows being installed correctly on the controller node but not on the compute nodes. </p> <p>Following are the flows on the controller node</p> <ul class="alternate" type="square"> <li>Vishal</li> </ul> <p><span class="error">&#91;odl@ctrl devstack&#93;</span>$ sudo ovs-ofctl -O Openflow13 dump-flows br-int <br/> OFPST_FLOW reply (OF1.3) (xid=0x2):<br/> 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<br/> cookie=0x0, duration=8070.759s, table=0, n_packets=0, n_bytes=0, send_flow_rem priority=8192,in_port=2 actions=drop<br/> cookie=0x0, duration=8198.377s, table=0, n_packets=273, n_bytes=36582, send_flow_rem dl_type=0x88cc actions=CONTROLLER:65535<br/> cookie=0x0, duration=8197.406s, table=0, n_packets=317, n_bytes=58240, send_flow_rem priority=0 actions=goto_table:20<br/> 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-&gt;vlan_vid,goto_table:20<br/> cookie=0x0, duration=8196.904s, table=20, n_packets=520, n_bytes=69148, send_flow_rem priority=0 actions=goto_table:30<br/> cookie=0x0, duration=8196.4s, table=30, n_packets=520, n_bytes=69148, send_flow_rem priority=0 actions=goto_table:40<br/> cookie=0x0, duration=8195.896s, table=40, n_packets=520, n_bytes=69148, send_flow_rem priority=0 actions=goto_table:50<br/> cookie=0x0, duration=8195.386s, table=50, n_packets=520, n_bytes=69148, send_flow_rem priority=0 actions=goto_table:60<br/> cookie=0x0, duration=8194.88s, table=60, n_packets=520, n_bytes=69148, send_flow_rem priority=0 actions=goto_table:70<br/> cookie=0x0, duration=8194.378s, table=70, n_packets=520, n_bytes=69148, send_flow_rem priority=0 actions=goto_table:80<br/> cookie=0x0, duration=8193.881s, table=80, n_packets=520, n_bytes=69148, send_flow_rem priority=0 actions=goto_table:90<br/> cookie=0x0, duration=8193.378s, table=90, n_packets=520, n_bytes=69148, send_flow_rem priority=0 actions=goto_table:100<br/> cookie=0x0, duration=8192.873s, table=100, n_packets=520, n_bytes=69148, send_flow_rem priority=0 actions=goto_table:110<br/> cookie=0x0, duration=8069.715s, table=110, n_packets=85, n_bytes=3676, send_flow_rem priority=8192,dl_vlan=101 actions=output:1<br/> 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<br/> cookie=0x0, duration=8192.367s, table=110, n_packets=319, n_bytes=58426, send_flow_rem priority=0 actions=drop<br/> 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</p> <p>Vishal,</p> <p>that is a different issue then. Nothing to do with the vlan flows as they are being installed. It might be related to <a href="https://bugs.opendaylight.org/show_bug.cgi?id=2024" class="external-link" target="_blank" rel="nofollow noopener">https://bugs.opendaylight.org/show_bug.cgi?id=2024</a>.</p> <p>Sam</p> <p>Sam, I am not seeing that exception in my ODL logs.</p> <p>I will re-run the test tomorrow after checking out ovsdb again.</p> <p>I have verified that the fix works with latest OVSDB. Sorry for the confusion Sam.</p> <p>(In reply to Vishal Patil from comment #12)<br/> &gt; I have verified that the fix works with latest OVSDB. Sorry for the<br/> &gt; confusion Sam.</p> <p>Great! Thanks Vishal.</p> Development External issue ID 1885 External issue URL Rank 0|i020lb: