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/VTN-78 vtn <p>Tried the Service Function HowTo page<br/> <a href="https://wiki.opendaylight.org/view/VTN_How_to_Configure_Service_Function_Chaining" class="external-link" target="_blank" rel="nofollow noopener">https://wiki.opendaylight.org/view/VTN_How_to_Configure_Service_Function_Chaining</a></p> <p>When attempting h12 ping h22, the ping was never responding. The same page works well with Helium distribution.</p> <p>Some of the errors that were observed in the karaf.log were</p> <p>************<b>start of karaf.log error part</b>****************<br/> v201506150016 | default:vTerminal:Tenant2.vt_srvc1_1: vTerminal added: VTerminal<span class="error">&#91;name=vt_srvc1_1,desc=vterminal for service1,faults=0,state=UNKNOWN&#93;</span><br/> 2015-06-18 23:58:43,373 | INFO | Thread: default | VTNManagerImpl | 345 - org.opendaylight.vtn.manager.implementation - 0.3.0.Lithium-RC1-v201506150016 | default:vTerminal-IF:Tenant2.vt_srvc1_1.IF: Virtual interface added: VInterface<span class="error">&#91;name=IF,desc=Description about IF-1,enabled,state=UNKNOWN,entityState=UNKNOWN&#93;</span><br/> 2015-06-18 23:58:48,669 | INFO | Thread: default | VTNManagerImpl | 345 - org.opendaylight.vtn.manager.implementation - 0.3.0.Lithium-RC1-v201506150016 | default:vTerminal-IF:Tenant2.vt_srvc1_1.IF: Port mapping added: PortMap[config=PortMapConfig[node=OF|00:00:00:00:00:00:00:03,port=SwitchPort<span class="error">&#91;name=s3-eth3,type=OF,id=3&#93;</span>,vlan=0],connector=OF|3@OF|00:00:00:00:00:00:00:03]<br/> 2015-06-18 23:58:48,669 | INFO | Thread: default | VTNManagerImpl | 345 - org.opendaylight.vtn.manager.implementation - 0.3.0.Lithium-RC1-v201506150016 | default:vTerminal-IF:Tenant2.vt_srvc1_1.IF: Virtual interface changed: VInterface<span class="error">&#91;name=IF,desc=Description about IF-1,enabled,state=DOWN,entityState=UP&#93;</span><br/> 2015-06-18 23:58:48,669 | INFO | Thread: default | VTNManagerImpl | 345 - org.opendaylight.vtn.manager.implementation - 0.3.0.Lithium-RC1-v201506150016 | default:vTerminal:Tenant2.vt_srvc1_1: vTerminal changed: VTerminal<span class="error">&#91;name=vt_srvc1_1,desc=vterminal for service1,faults=0,state=DOWN&#93;</span><br/> 2015-06-18 23:58:54,493 | INFO | Thread: default | VTNManagerImpl | 345 - org.opendaylight.vtn.manager.implementation - 0.3.0.Lithium</p> <ul> <li> <ul> <li> <ul> <li> <ul> <li> <ul> <li> <ul> <li> <ul> <li> <ul> <li>end of karaf.log error part ***************************</li> </ul> </li> </ul> </li> </ul> </li> </ul> </li> </ul> </li> </ul> </li> </ul> </li> </ul> <p>When setting log level as TRACE, other logs like "Ignore the Packet from Internal Port OpenFlow:4-s4-eth3" was observed. When checking the flow entries in mininet using sudo ovs-ofctl dump-flows, Flows were seen in s1, s2 and s3. s4 had no flows installed. We will provide those logs also.</p> <p>Operating System: All<br/> Platform: All</p> VTN-78

redirect Operation fails to forward packets

Bug Resolved Done Unassigned Venkatrangan Govindarajan Fri, 19 Jun 2015 04:22:08 +0000 Thu, 19 Oct 2017 21:25:15 +0000 Thu, 1 Oct 2015 11:42:08 +0000 unspecified VTN Manager 0 3 <p>This issue seems to be caused by difference of behavior in Lithium topology manager.</p> <p>This example of service function maps openflow:3:3 to vt_srvc1_1 and openflow:4:3 to vt_srvc1_2 respectively. But the topology manager detects inter-swtich link between openflow:3:3 and openflow:4:3.</p> <p>GET /restconf/operational/network-topology:network-topology/topology/flow:1/link/openflow:3:3<br/> -&gt; {<br/> "link": [<br/> {<br/> "destination": </p> { "dest-node": "openflow:4", "dest-tp": "openflow:4:3" } <p>,<br/> "link-id": "openflow:3:3",<br/> "source": </p> { "source-node": "openflow:3", "source-tp": "openflow:3:3" } <p> }<br/> ]<br/> }</p> <p>So VTerminal interfaces are treated as DOWN because ISL port cannot be mapped to virtual interface.</p> <p>All the operations in that wiki page seems to work fine if we add the following flow entries:</p> <ul> <li>Drop LLDP received from openflow:3:3<br/> PUT /restconf/config/opendaylight-inventory:nodes/opendaylight-inventory:node/openflow:3/flow-node-inventory:table/0/flow-node-inventory:flow/drop_lldp_3<br/> {<br/> "flow-node-inventory:flow": [<br/> {<br/> "hard-timeout": 0,<br/> "id": "drop_lldp_3",<br/> "idle-timeout": 0,<br/> "match": {<br/> "ethernet-match": <div class="error"><span class="error">Unknown macro: { &quot;ethernet-type&quot;}</span> </div> <p>,<br/> "in-port": "openflow:3:3"<br/> },<br/> "priority": 10,<br/> "table_id": 0<br/> }<br/> ]<br/> }</p></li> </ul> <ul> <li>Drop LLDP received from openflow:3:4<br/> PUT /restconf/config/opendaylight-inventory:nodes/opendaylight-inventory:node/openflow:3/flow-node-inventory:table/0/flow-node-inventory:flow/drop_lldp_4<br/> {<br/> "flow-node-inventory:flow": [<br/> {<br/> "hard-timeout": 0,<br/> "id": "drop_lldp_4",<br/> "idle-timeout": 0,<br/> "match": {<br/> "ethernet-match": <div class="error"><span class="error">Unknown macro: { &quot;ethernet-type&quot;}</span> </div> <p>,<br/> "in-port": "openflow:3:4"<br/> },<br/> "priority": 10,<br/> "table_id": 0<br/> }<br/> ]<br/> }</p></li> </ul> <ul> <li>Drop LLDP received from openflow:4:3<br/> PUT /restconf/config/opendaylight-inventory:nodes/opendaylight-inventory:node/openflow:4/flow-node-inventory:table/0/flow-node-inventory:flow/drop_lldp_3<br/> {<br/> "flow-node-inventory:flow": [<br/> {<br/> "hard-timeout": 0,<br/> "id": "drop_lldp_3",<br/> "idle-timeout": 0,<br/> "match": {<br/> "ethernet-match": <div class="error"><span class="error">Unknown macro: { &quot;ethernet-type&quot;}</span> </div> <p>,<br/> "in-port": "openflow:4:3"<br/> },<br/> "priority": 10,<br/> "table_id": 0<br/> }<br/> ]<br/> }</p></li> </ul> <ul> <li>Drop LLDP received from openflow:4:4<br/> PUT /restconf/config/opendaylight-inventory:nodes/opendaylight-inventory:node/openflow:4/flow-node-inventory:table/0/flow-node-inventory:flow/drop_lldp_4<br/> {<br/> "flow-node-inventory:flow": [<br/> {<br/> "hard-timeout": 0,<br/> "id": "drop_lldp_4",<br/> "idle-timeout": 0,<br/> "match": {<br/> "ethernet-match": <div class="error"><span class="error">Unknown macro: { &quot;ethernet-type&quot;}</span> </div> <p>,<br/> "in-port": "openflow:4:4"<br/> },<br/> "priority": 10,<br/> "table_id": 0<br/> }<br/> ]<br/> }</p></li> </ul> <p>I am planning to add new feature which manages static network topology configuration to VTN Manager by Lithium SR2, and it will solve this issue.</p> <p><a href="https://git.opendaylight.org/gerrit/26177" class="external-link" target="_blank" rel="nofollow noopener">https://git.opendaylight.org/gerrit/26177</a> (stable/lithium)</p> <p>SFC example described in the wiki page will work fine if the following configuration is applied.</p> <p>PUT /restconf/config/vtn-static-topology:vtn-static-topology/static-edge-ports</p> <p>{<br/> "static-edge-ports": {<br/> "static-edge-port": [<br/> </p> { "port": "openflow:3:3" } <p>,<br/> </p> { "port": "openflow:3:4" } <p>,<br/> </p> { "port": "openflow:4:3" } <p>,</p> { "port": "openflow:4:4" } <p> ]<br/> }<br/> }</p> <p><a href="https://git.opendaylight.org/gerrit/26424" class="external-link" target="_blank" rel="nofollow noopener">https://git.opendaylight.org/gerrit/26424</a> (master)</p> <p>Patch was merged.<br/> Please retest and close this bug if this issue is fixed.</p> <p>I updated the patch. Please retest with new patch.</p> <p> <a href="https://git.opendaylight.org/gerrit/26540" class="external-link" target="_blank" rel="nofollow noopener">https://git.opendaylight.org/gerrit/26540</a> (master)<br/> <a href="https://git.opendaylight.org/gerrit/26541" class="external-link" target="_blank" rel="nofollow noopener">https://git.opendaylight.org/gerrit/26541</a> (stable/lithium)</p> <p>Tested the updated patch successfully, and modified the wiki page accordingly:</p> <p><a href="https://wiki.opendaylight.org/view/Release/Lithium/VTN/HowTos/VTN_How_to_Configure_Service_Function_Chaining" class="external-link" target="_blank" rel="nofollow noopener">https://wiki.opendaylight.org/view/Release/Lithium/VTN/HowTos/VTN_How_to_Configure_Service_Function_Chaining</a></p> <p>The patch works fine. It has been tested in stable/lithium karaf distribution.</p> <p>As suggested by Yesuda San, used the below rest api before configuring :</p> <p>curl -v --user admin:admin -H 'Accept: application/json' -H 'content-type: application/json' -H 'ipaddr:127.0.0.1' -X PUT <a href="http://localhost:8181/restconf/config/vtn-static-topology:vtn-static-topology/static-edge-ports" class="external-link" target="_blank" rel="nofollow noopener">http://localhost:8181/restconf/config/vtn-static-topology:vtn-static-topology/static-edge-ports</a> -d '{"static-edge-ports": {"static-edge-port": [ </p> {"port": "openflow:3:3"} <p>, </p> {"port": "openflow:3:4"} <p>, </p> {"port": "openflow:4:3"} <p>, </p> {"port": "openflow:4:4"} <p>]}}'</p> <p>Update the Service function chaining wiki page with the above comamnd: PFB the link for the same:</p> <p><a href="https://wiki.opendaylight.org/view/Release/Lithium/VTN/HowTos/VTN_How_to_Configure_Service_Function_Chaining" class="external-link" target="_blank" rel="nofollow noopener">https://wiki.opendaylight.org/view/Release/Lithium/VTN/HowTos/VTN_How_to_Configure_Service_Function_Chaining</a></p> Development External issue ID 3818 External issue URL ODL SR Target Milestone Rank 0|i02tg7: