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/SFC-86 sfc <p>OVS/Controller fails to create flow to next hop in chain, if SF in next hop does not have "ip-mgmt-address" set. Tested on path:<br/> 1. SFF-1 (OVS)<br/> 2. SF-1 (python agent)<br/> 3. SFF-1 (OVS)<br/> 4. SFF-2 (python agent)<br/> 5. SF-2 (python agent)<br/> 6. SFF-2 (python agent)</p> <p>If "ip-mgmt-address" == null =&gt; packet is droped on step "3. SFF-1 (OVS)".</p> <p>Operating System: All<br/> Platform: All</p> SFC-86

OVS flow to next hop is not created if "ip-mgmt-address" of SF on next SFF is not set

Bug Verified Cannot Reproduce Ricardo Noriega Peter Žeby Tue, 21 Jul 2015 14:50:57 +0000 Tue, 29 May 2018 18:13:41 +0000 Tue, 29 May 2018 18:13:35 +0000 unspecified Carbon General 0 2 <p>Which flow are you referring to that dont get created? Are you referring to the OpenFlow flows? If so, the OpenFlow flows have nothing to do with "ip-mgmt-address" being set.</p> <p>To be able to debug this problem, I need the following pieces of information:</p> <ul class="alternate" type="square"> <li>The complete SFC configuration, including: SFs, SFFs, SFCs, SFPs, and RSPs.</li> <li>a dump of the OpenFlow flows from each SFF using the command: "sudo ovs-ofctl -O OpenFlow13 dump-flows &lt;SFF switch name&gt;"</li> </ul> <p>Brady</p> <p>Attachment chain_setup.txt has been added with description: sfc configuration</p> <p>I am referring to OF flow on OVS, when packet is returned from SF.</p> <p>My basic topology/chain setup:<br/> Client <del>&gt; classifier (python) -&gt; SFF (OVS &lt;</del>&gt; SF python) <del>&gt; SFF (python &lt;</del>&gt; SF python) -&gt; Server</p> <p>Created flows on OVS:<br/> root@OVS1:~# ovs-ofctl -O OpenFlow13 dump-flows sw1<br/> OFPST_FLOW reply (OF1.3) (xid=0x2):<br/> cookie=0x14, duration=4.070s, table=0, n_packets=0, n_bytes=0, priority=250,ip actions=goto_table:3<br/> cookie=0x14, duration=4.056s, table=3, n_packets=0, n_bytes=0, priority=540,nsp=2,nsi=255 actions=load:0xc0a82133-&gt;NXM_NX_TUN_IPV4_DST[],goto_table:10<br/> cookie=0xba5eba11ba5eba11, duration=4.049s, table=10, n_packets=0, n_bytes=0, priority=640,nsp=2,nsi=255 actions=move:NXM_NX_NSH_C1[]<del>&gt;NXM_NX_NSH_C1[],move:NXM_NX_NSH_C2[]</del>&gt;NXM_NX_NSH_C2[],move:NXM_NX_TUN_ID<span class="error">&#91;0..31&#93;</span>-&gt;NXM_NX_TUN_ID<span class="error">&#91;0..31&#93;</span>,IN_PORT</p> <p>Created flows on OVS (new chain), when second hop SF has "ip-mgmt-address" set:<br/> OFPST_FLOW reply (OF1.3) (xid=0x2):<br/> cookie=0x14, duration=4.740s, table=0, n_packets=0, n_bytes=0, priority=250,ip actions=goto_table:3<br/> cookie=0x14, duration=878.708s, table=3, n_packets=0, n_bytes=0, priority=540,nsp=2,nsi=255 actions=load:0xc0a82133-&gt;NXM_NX_TUN_IPV4_DST[],goto_table:10<br/> cookie=0x14, duration=4.729s, table=3, n_packets=0, n_bytes=0, priority=540,nsp=3,nsi=255 actions=load:0xc0a82133-&gt;NXM_NX_TUN_IPV4_DST[],goto_table:10<br/> cookie=0x14, duration=4.674s, table=3, n_packets=0, n_bytes=0, priority=540,nsp=3,nsi=254 actions=load:0xc0a82135-&gt;NXM_NX_TUN_IPV4_DST[],goto_table:10<br/> cookie=0xba5eba11ba5eba11, duration=878.701s, table=10, n_packets=0, n_bytes=0, priority=640,nsp=2,nsi=255 actions=move:NXM_NX_NSH_C1[]<del>&gt;NXM_NX_NSH_C1[],move:NXM_NX_NSH_C2[]</del>&gt;NXM_NX_NSH_C2[],move:NXM_NX_TUN_ID<span class="error">&#91;0..31&#93;</span>-&gt;NXM_NX_TUN_ID<span class="error">&#91;0..31&#93;</span>,IN_PORT<br/> cookie=0xba5eba11ba5eba11, duration=4.722s, table=10, n_packets=0, n_bytes=0, priority=640,nsp=3,nsi=255 actions=move:NXM_NX_NSH_C1[]<del>&gt;NXM_NX_NSH_C1[],move:NXM_NX_NSH_C2[]</del>&gt;NXM_NX_NSH_C2[],move:NXM_NX_TUN_ID<span class="error">&#91;0..31&#93;</span>-&gt;NXM_NX_TUN_ID<span class="error">&#91;0..31&#93;</span>,IN_PORT<br/> cookie=0xba5eba11ba5eba11, duration=4.668s, table=10, n_packets=0, n_bytes=0, priority=640,nsp=3,nsi=254 actions=move:NXM_NX_NSH_C1[]<del>&gt;NXM_NX_NSH_C1[],move:NXM_NX_NSH_C2[]</del>&gt;NXM_NX_NSH_C2[],move:NXM_NX_TUN_ID<span class="error">&#91;0..31&#93;</span>-&gt;NXM_NX_TUN_ID<span class="error">&#91;0..31&#93;</span>,IN_PORT</p> <p>Configuration is in att.</p> <p>Controller branch used - master</p> <p>This is a little bit old, but so far, I haven't been able to reproduce the failure.</p> <p>In my testing environment, using the same type of configuration and removing the ip-mgmt-address from one of the SFs, flows are properly created.</p> <p>Could you reproduce the bug or should we close it?</p> <p>I tested this on Fluorine, and all flows are created as expected when the ip-mgmt-address is not specified on the SFs. Considering the sfc-agent is no longer supported, Im closing this bug.</p> Development External issue ID 4028 External issue URL Rank 0|i02eyv: