<!-- 
RSS generated by JIRA (8.20.10#820010-sha1:ace47f9899e9ee25d7157d59aa17ab06aee30d3d) at Wed Feb 07 20:33:04 UTC 2024

It is possible to restrict the fields that are returned in this document by specifying the 'field' parameter in your request.
For example, to request only the issue key and summary append 'field=key&field=summary' to the URL of your request.
-->
<rss version="0.92" >
<channel>
    <title>OpenDaylight JIRA</title>
    <link>https://jira.opendaylight.org</link>
    <description>This file is an XML representation of an issue</description>
    <language>en-us</language>    <build-info>
        <version>8.20.10</version>
        <build-number>820010</build-number>
        <build-date>22-06-2022</build-date>
    </build-info>


<item>
            <title>[OPNFLWPLUG-664] Failed to add flows with actions ICMP code and type in OF1.3</title>
                <link>https://jira.opendaylight.org/browse/OPNFLWPLUG-664</link>
                <project id="10155" key="OPNFLWPLUG">OpenFlowPlugin</project>
                    <description>&lt;p&gt;I have been testing with Beryllium SR1 distribution for VTN project, and faced issue while adding flows with action ICMP code and type for OF1.3. &lt;/p&gt;

&lt;p&gt;  That is after adding flows when i verify using dump-flows in mininet actions mod_tp_src and mod_tp_dst are not displayed in OF1.3. But for OF1.0 mod_tp_src and mod_tp_dst are shown in dump-flows. &lt;/p&gt;

&lt;p&gt;  To cross verify, i have tested the above scenario with Openflowplugin Restconf command and faced same issue. Below are the steps i have followed,&lt;/p&gt;

&lt;p&gt;1) Configured mininet with sudo mn --topo tree,2  --controller remote,ip=10.106.138.117  --switch ovsk,protocols=OpenFlow10&lt;/p&gt;


&lt;p&gt;2) Add flows with action set-tp-dst-action and set-tp-src-action using below command, and response code is success&lt;/p&gt;

&lt;p&gt;curl -v --user &quot;admin&quot;:&quot;admin&quot; -H &quot;Content-type: application/xml&quot; -X PUT &lt;a href=&quot;http://localhost:8181/restconf/config/opendaylight-inventory:nodes/node/openflow:1/table/2/flow/134&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;http://localhost:8181/restconf/config/opendaylight-inventory:nodes/node/openflow:1/table/2/flow/134&lt;/a&gt; -d &apos;&amp;lt;?xml version=&quot;1.0&quot; encoding=&quot;UTF-8&quot; standalone=&quot;no&quot;?&amp;gt; &amp;lt;flow xmlns=&quot;urn:opendaylight:flow:inventory&quot;&amp;gt; &amp;lt;strict&amp;gt;false&amp;lt;/strict&amp;gt; &amp;lt;instructions&amp;gt; &amp;lt;instruction&amp;gt; &amp;lt;order&amp;gt;0&amp;lt;/order&amp;gt; &amp;lt;apply-actions&amp;gt; &amp;lt;action&amp;gt; &amp;lt;order&amp;gt;0&amp;lt;/order&amp;gt; &amp;lt;set-tp-dst-action&amp;gt; &amp;lt;port&amp;gt;109&amp;lt;/port&amp;gt; &amp;lt;/set-tp-dst-action&amp;gt; &amp;lt;/action&amp;gt; &amp;lt;action&amp;gt; &amp;lt;order&amp;gt;1&amp;lt;/order&amp;gt; &amp;lt;set-tp-src-action&amp;gt; &amp;lt;port&amp;gt;108&amp;lt;/port&amp;gt; &amp;lt;/set-tp-src-action&amp;gt; &amp;lt;/action&amp;gt; &amp;lt;action&amp;gt; &amp;lt;output-action&amp;gt; &amp;lt;output-node-connector&amp;gt;3&amp;lt;/output-node-connector&amp;gt; &amp;lt;/output-action&amp;gt; &amp;lt;order&amp;gt;2&amp;lt;/order&amp;gt; &amp;lt;/action&amp;gt; &amp;lt;/apply-actions&amp;gt; &amp;lt;/instruction&amp;gt; &amp;lt;/instructions&amp;gt; &amp;lt;table_id&amp;gt;2&amp;lt;/table_id&amp;gt; &amp;lt;id&amp;gt;134&amp;lt;/id&amp;gt; &amp;lt;cookie_mask&amp;gt;255&amp;lt;/cookie_mask&amp;gt; &amp;lt;match&amp;gt; &amp;lt;ethernet-match&amp;gt; &amp;lt;ethernet-type&amp;gt; &amp;lt;type&amp;gt;0x800&amp;lt;/type&amp;gt; &amp;lt;/ethernet-type&amp;gt; &amp;lt;ethernet-destination&amp;gt; &amp;lt;address&amp;gt;ff:ff:29:01:19:61&amp;lt;/address&amp;gt; &amp;lt;/ethernet-destination&amp;gt; &amp;lt;ethernet-source&amp;gt; &amp;lt;address&amp;gt;00:00:00:11:23:ae&amp;lt;/address&amp;gt; &amp;lt;/ethernet-source&amp;gt; &amp;lt;/ethernet-match&amp;gt; &amp;lt;ipv4-source&amp;gt;17.0.0.0/8&amp;lt;/ipv4-source&amp;gt; &amp;lt;ipv4-destination&amp;gt;172.168.0.0/16&amp;lt;/ipv4-destination&amp;gt; &amp;lt;ip-match&amp;gt; &amp;lt;ip-protocol&amp;gt;1&amp;lt;/ip-protocol&amp;gt; &amp;lt;/ip-match&amp;gt;  &amp;lt;in-port&amp;gt;0&amp;lt;/in-port&amp;gt; &amp;lt;/match&amp;gt; &amp;lt;cookie&amp;gt;11&amp;lt;/cookie&amp;gt; &amp;lt;flow-name&amp;gt;FooXf11&amp;lt;/flow-name&amp;gt; &amp;lt;priority&amp;gt;11&amp;lt;/priority&amp;gt; &amp;lt;/flow&amp;gt;&apos; &lt;/p&gt;

&lt;p&gt;&amp;lt; HTTP/1.1 200 OK&lt;br/&gt;
&amp;lt; Set-Cookie: JSESSIONID=lw27td6lxerhh9af3fnhneta;Path=/restconf&lt;br/&gt;
&amp;lt; Expires: Thu, 01 Jan 1970 00:00:00 GMT&lt;br/&gt;
&amp;lt; Set-Cookie: rememberMe=deleteMe; Path=/restconf; Max-Age=0; Expires=Tue, 29-Mar-2016 04:32:56 GMT&lt;br/&gt;
&amp;lt; Content-Length: 0&lt;/p&gt;

&lt;p&gt;3) Checked flowentries in mininet for OF1.0 and actions mod_tp_src and mod_tp_dst are applied in node.&lt;br/&gt;
mininet&amp;gt; dpctl dump-flows -OOpenFlow10&lt;/p&gt;
&lt;ul&gt;
	&lt;li&gt;
	&lt;ul&gt;
		&lt;li&gt;
		&lt;ul&gt;
			&lt;li&gt;s1 ------------------------------------------------------------------------&lt;br/&gt;
NXST_FLOW reply (xid=0x4):&lt;br/&gt;
 cookie=0xb, duration=26.914s, table=0, n_packets=0, n_bytes=0, idle_age=26, priority=11,icmp,in_port=0,dl_src=00:00:00:11:23:ae,dl_dst=ff:ff:29:01:19:61,nw_src=17.0.0.0/8,nw_dst=172.168.0.0/16,nw_tos=108,icmp_type=6,icmp_code=3 actions=mod_tp_dst:109,mod_tp_src:108,output:3&lt;/li&gt;
			&lt;li&gt;s2 ------------------------------------------------------------------------&lt;br/&gt;
NXST_FLOW reply (xid=0x4):&lt;/li&gt;
			&lt;li&gt;s3 ------------------------------------------------------------------------&lt;br/&gt;
NXST_FLOW reply (xid=0x4):&lt;/li&gt;
		&lt;/ul&gt;
		&lt;/li&gt;
	&lt;/ul&gt;
	&lt;/li&gt;
&lt;/ul&gt;




&lt;p&gt;I have followed the same above scenario in OF1.3, failed to display flows in mininet. &lt;/p&gt;

&lt;p&gt;1)1) Configured mininet with sudo mn --topo tree,2  --controller remote,ip=10.106.138.117  --switch ovsk,protocols=OpenFlow13&lt;/p&gt;


&lt;p&gt;2) Add flows with action set-tp-dst-action and set-tp-src-action using below command, and response code is success. Used the same command which i tried for OF1.0, which is above.&lt;/p&gt;

&lt;p&gt;3) Checked flowentries in mininet for OF1.3 and but flow is not created. Output is as below,&lt;br/&gt;
mininet&amp;gt; dpctl dump-flows -OOpenFlow10&lt;/p&gt;
&lt;ul&gt;
	&lt;li&gt;
	&lt;ul&gt;
		&lt;li&gt;
		&lt;ul&gt;
			&lt;li&gt;s1 ------------------------------------------------------------------------&lt;br/&gt;
NXST_FLOW reply (xid=0x4):&lt;/li&gt;
			&lt;li&gt;s2 ------------------------------------------------------------------------&lt;br/&gt;
NXST_FLOW reply (xid=0x4):&lt;/li&gt;
			&lt;li&gt;s3 ------------------------------------------------------------------------&lt;br/&gt;
NXST_FLOW reply (xid=0x4):&lt;br/&gt;
mininet&amp;gt;&lt;/li&gt;
		&lt;/ul&gt;
		&lt;/li&gt;
	&lt;/ul&gt;
	&lt;/li&gt;
&lt;/ul&gt;



&lt;p&gt;I would like to know is there any issues in adding flows with actions ICMP code and type. Since the scenario which is working for OF1.0.&lt;/p&gt;


&lt;p&gt;For your information i have attached karaf.log with TRACE enabled for Openflowplugin.&lt;/p&gt;

&lt;p&gt;Attached with of_karaf_log.zip file.&lt;/p&gt;</description>
                <environment>&lt;p&gt;Operating System: All&lt;br/&gt;
Platform: All&lt;/p&gt;</environment>
        <key id="27932">OPNFLWPLUG-664</key>
            <summary>Failed to add flows with actions ICMP code and type in OF1.3</summary>
                <type id="10104" iconUrl="https://jira.opendaylight.org/secure/viewavatar?size=xsmall&amp;avatarId=10303&amp;avatarType=issuetype">Bug</type>
                                                <status id="5" iconUrl="https://jira.opendaylight.org/images/icons/statuses/resolved.png" description="A resolution has been taken, and it is awaiting verification by reporter. From here issues are either reopened, or are closed.">Resolved</status>
                    <statusCategory id="3" key="done" colorName="green"/>
                                    <resolution id="10003">Cannot Reproduce</resolution>
                                        <assignee username="-1">Unassigned</assignee>
                                    <reporter username="siva-karthik@hcl.com">Karthik Sivasamy</reporter>
                        <labels>
                    </labels>
                <created>Tue, 29 Mar 2016 15:58:43 +0000</created>
                <updated>Mon, 27 Sep 2021 09:01:47 +0000</updated>
                            <resolved>Mon, 18 Jul 2016 05:38:29 +0000</resolved>
                                                                    <component>General</component>
                        <due></due>
                            <votes>0</votes>
                                    <watches>3</watches>
                                                                                                                <comments>
                            <comment id="57774" author="siva-karthik@hcl.com" created="Tue, 29 Mar 2016 15:58:43 +0000"  >&lt;p&gt;Attachment of_karaf_logs.zip has been added with description: Trace Enabled logs for Openflowplugin&lt;/p&gt;</comment>
                            <comment id="57769" author="vishnoianil@gmail.com" created="Wed, 30 Mar 2016 03:38:13 +0000"  >&lt;p&gt;set-tp-src and set-tp-dst fields are specific to openflow 1.0 switches, these actions were removed from openflow 1.3 spec. For openflow 1.3, please use set-field actions to set any packet header value.&lt;/p&gt;</comment>
                            <comment id="57770" author="siva-karthik@hcl.com" created="Wed, 30 Mar 2016 13:41:10 +0000"  >&lt;p&gt;Hi Anil,&lt;/p&gt;

&lt;p&gt;As you said i have used set-field for icmpv4 actions. Below is the command which i  have tried,&lt;/p&gt;

&lt;p&gt;curl -v --user &quot;admin&quot;:&quot;admin&quot; -H &quot;Content-type: application/xml&quot; -X PUT &lt;a href=&quot;http://localhost:8181/restconf/config/opendaylight-inventory:nodes/node/openflow:3/table/2/flow/256&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;http://localhost:8181/restconf/config/opendaylight-inventory:nodes/node/openflow:3/table/2/flow/256&lt;/a&gt; -d &apos;&amp;lt;?xml version=&quot;1.0&quot; encoding=&quot;UTF-8&quot; standalone=&quot;no&quot;?&amp;gt; &amp;lt;flow xmlns=&quot;urn:opendaylight:flow:inventory&quot;&amp;gt; &amp;lt;strict&amp;gt;false&amp;lt;/strict&amp;gt; &amp;lt;flow-name&amp;gt;set-field-tcp-src&amp;lt;/flow-name&amp;gt; &amp;lt;id&amp;gt;256&amp;lt;/id&amp;gt; &amp;lt;cookie_mask&amp;gt;255&amp;lt;/cookie_mask&amp;gt; &amp;lt;cookie&amp;gt;101&amp;lt;/cookie&amp;gt; &amp;lt;table_id&amp;gt;2&amp;lt;/table_id&amp;gt; &amp;lt;priority&amp;gt;2&amp;lt;/priority&amp;gt; &amp;lt;instructions&amp;gt; &amp;lt;instruction&amp;gt; &amp;lt;order&amp;gt;0&amp;lt;/order&amp;gt; &amp;lt;apply-actions&amp;gt; &amp;lt;action&amp;gt; &amp;lt;order&amp;gt;0&amp;lt;/order&amp;gt; &amp;lt;set-field&amp;gt; &amp;lt;icmpv4-match&amp;gt; &amp;lt;icmpv4-type&amp;gt;3&amp;lt;/icmpv4-type&amp;gt; &amp;lt;icmpv4-code&amp;gt;1&amp;lt;/icmpv4-code&amp;gt; &amp;lt;/icmpv4-match&amp;gt; &amp;lt;/set-field&amp;gt; &amp;lt;/action&amp;gt; &amp;lt;/apply-actions&amp;gt; &amp;lt;/instruction&amp;gt; &amp;lt;/instructions&amp;gt; &amp;lt;match&amp;gt; &amp;lt;ethernet-match&amp;gt; &amp;lt;ethernet-type&amp;gt; &amp;lt;type&amp;gt;2048&amp;lt;/type&amp;gt; &amp;lt;/ethernet-type&amp;gt; &amp;lt;/ethernet-match&amp;gt; &amp;lt;ipv4-source&amp;gt;10.0.0.1/32&amp;lt;/ipv4-source&amp;gt; &amp;lt;ipv4-destination&amp;gt;10.0.0.3/32&amp;lt;/ipv4-destination&amp;gt;  &amp;lt;ip-match&amp;gt; &amp;lt;ip-protocol&amp;gt;1&amp;lt;/ip-protocol&amp;gt; &amp;lt;/ip-match&amp;gt; &amp;lt;/match&amp;gt; &amp;lt;/flow&amp;gt;&apos;&lt;/p&gt;

&lt;p&gt;The above command to add flows executed successfully with return code 200.&lt;/p&gt;

&lt;p&gt;In Dumpflow i have checked flows which are not displayed&lt;br/&gt;
mininet&amp;gt; dpctl dump-flows -OOpenFlow13&lt;/p&gt;
&lt;ul&gt;
	&lt;li&gt;
	&lt;ul&gt;
		&lt;li&gt;
		&lt;ul&gt;
			&lt;li&gt;s1 ------------------------------------------------------------------------&lt;br/&gt;
OFPST_FLOW reply (OF1.3) (xid=0x2):&lt;/li&gt;
			&lt;li&gt;s2 ------------------------------------------------------------------------&lt;br/&gt;
OFPST_FLOW reply (OF1.3) (xid=0x2):&lt;/li&gt;
			&lt;li&gt;s3 ------------------------------------------------------------------------&lt;br/&gt;
OFPST_FLOW reply (OF1.3) (xid=0x2):&lt;br/&gt;
mininet&amp;gt;&lt;/li&gt;
		&lt;/ul&gt;
		&lt;/li&gt;
	&lt;/ul&gt;
	&lt;/li&gt;
&lt;/ul&gt;



&lt;p&gt;Note: Using OVS version 2.3.1&lt;/p&gt;

&lt;p&gt;I have captured packets for port 6633 in controller side, and analysed in pcap file in wireshark tool. &lt;/p&gt;

&lt;p&gt;Here i have Attahced pcap file --&amp;gt; icmp_of13.pcap&lt;/p&gt;

&lt;p&gt;In attached icmp_of13.pcap file Line 401 which is OFPT_FLOW_MOD ,&lt;br/&gt;
In OFPT_FLOW_MOD -&amp;gt; openflow 1.3 -&amp;gt; Insructions -&amp;gt; Action -&amp;gt; 0xM field, in which i can see only ICMP Type field but ICMP code is not present.&lt;/p&gt;

&lt;p&gt;In attahced icmp_of13.pcap file Line 402 OFPT_ERROR,&lt;br/&gt;
In openflow 1.3 below are displayed.&lt;br/&gt;
TYPE: OFPET_BAD_ACTION (2)&lt;br/&gt;
CODE: OFPBAC_BAD_SET_ARGUMENT(15)&lt;/p&gt;

&lt;p&gt;The same above error which i observed in pcap file when i installed flows with ICMP actions using VTN Manager RESTCONF.&lt;/p&gt;

&lt;p&gt;So, please clarify my query below.&lt;br/&gt;
a)  The command which i configured with set-field for ICMP code and type formation are correct or not ?  If it is wrong please provide me a correct steps to add flows with ICMP code and type.&lt;/p&gt;

&lt;p&gt;b) If the command is correct, is it OFplugin BUG ?&lt;/p&gt;

&lt;p&gt;Kindly correct me if i missed anything in testing.&lt;/p&gt;

&lt;p&gt;In Karaf log i have observed below error messages,&lt;/p&gt;

&lt;p&gt;2016-03-30 15:59:01,728 | TRACE | OFmsgHarvester-0 | QueueKeeperHarvester             | 261 - org.opendaylight.openflowplugin - 0.2.1.Beryllium-SR1 | messageHarvester is about to make a starve sleep&lt;br/&gt;
2016-03-30 15:59:01,728 | DEBUG | OFmsgProcessor-1 | TicketProcessorFactoryImpl       | 261 - org.opendaylight.openflowplugin - 0.2.1.Beryllium-SR1 | message received, type: ErrorMessage&lt;br/&gt;
2016-03-30 15:59:01,728 | TRACE | OFmsgProcessor-1 | TicketProcessorFactoryImpl       | 261 - org.opendaylight.openflowplugin - 0.2.1.Beryllium-SR1 | translating ticket: ErrorMessage, ticket: 959291382&lt;br/&gt;
2016-03-30 15:59:01,728 | DEBUG | OFmsgProcessor-1 | TicketProcessorFactoryImpl       | 261 - org.opendaylight.openflowplugin - 0.2.1.Beryllium-SR1 | translatorKey: 4 + org.opendaylight.yang.gen.v1.urn.opendaylight.openflow.protocol.rev130731.ErrorMessage&lt;br/&gt;
2016-03-30 15:59:01,729 | DEBUG | OFmsgProcessor-1 | AbstractErrorTranslator          | 261 - org.opendaylight.openflowplugin - 0.2.1.Beryllium-SR1 |  Error Message received: type=2&lt;span class=&quot;error&quot;&gt;&amp;#91;BADACTION&amp;#93;&lt;/span&gt;, code=15&lt;span class=&quot;error&quot;&gt;&amp;#91;BADSETARGUMENT&amp;#93;&lt;/span&gt;, data=&lt;span class=&quot;error&quot;&gt;&amp;#91;04 0e 00 a0 00 00 02 6f 00 00 00 00 00 00 00 0b 00 00 00 00 00 00 00 ff 02 00 00 00 00 00 00 0b ff ff ff ff ff ff ff ff ff ff ff ff 00 00 00 00 00 01 00 43 80 00 00 04 00 00 00 00 80 00 06 06&amp;#93;&lt;/span&gt; &lt;br/&gt;
2016-03-30 15:59:01,729 | TRACE | OFmsgProcessor-1 | TicketProcessorFactoryImpl       | 261 - org.opendaylight.openflowplugin - 0.2.1.Beryllium-SR1 | translator: org.opendaylight.openflowplugin.openflow.md.core.translator.ErrorTranslator@4784b4bd elapsed time 561063 ns&lt;br/&gt;
2016-03-30 15:59:01,729 | DEBUG | OFmsgProcessor-1 | TicketProcessorFactoryImpl       | 261 - org.opendaylight.openflowplugin - 0.2.1.Beryllium-SR1 | message processing done (type: ErrorMessage, ticket: 959291382)&lt;/p&gt;</comment>
                            <comment id="57771" author="siva-karthik@hcl.com" created="Thu, 31 Mar 2016 09:29:44 +0000"  >&lt;p&gt;Anil,&lt;/p&gt;

&lt;p&gt;I have modified the OFPlugin resctconf command by having two different action filed for ICMP code and type. Now i can see in pcap file two actions which contains action Field:  &lt;br/&gt;
OFPXMT_OFB_ICMPV4_TYPE (19) &lt;br/&gt;
OFPXMT_OFB_ICMPV4_CODE (20). &lt;br/&gt;
But still same OFTP_ERROR for the flows created i.e.,(Type: OFPET_BAD_ACTION (2) and Code: OFPBAC_BAD_SET_ARGUMENT (15))&lt;/p&gt;

&lt;p&gt;Below are the command which i tried to have two different action field for ICMP type and code.&lt;/p&gt;

&lt;p&gt;curl -v --user &quot;admin&quot;:&quot;admin&quot; -H &quot;Content-type: application/xml&quot; -X PUT &lt;a href=&quot;http://localhost:8181/restconf/config/opendaylight-inventory:nodes/node/openflow:3/table/2/flow/256&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;http://localhost:8181/restconf/config/opendaylight-inventory:nodes/node/openflow:3/table/2/flow/256&lt;/a&gt; -d &apos;&amp;lt;?xml version=&quot;1.0&quot; encoding=&quot;UTF-8&quot; standalone=&quot;no&quot;?&amp;gt; &amp;lt;flow xmlns=&quot;urn:opendaylight:flow:inventory&quot;&amp;gt; &amp;lt;strict&amp;gt;false&amp;lt;/strict&amp;gt; &amp;lt;flow-name&amp;gt;set-field-tcp-src&amp;lt;/flow-name&amp;gt; &amp;lt;id&amp;gt;256&amp;lt;/id&amp;gt; &amp;lt;cookie_mask&amp;gt;255&amp;lt;/cookie_mask&amp;gt; &amp;lt;cookie&amp;gt;101&amp;lt;/cookie&amp;gt; &amp;lt;table_id&amp;gt;2&amp;lt;/table_id&amp;gt; &amp;lt;priority&amp;gt;2&amp;lt;/priority&amp;gt; &amp;lt;instructions&amp;gt; &amp;lt;instruction&amp;gt; &amp;lt;order&amp;gt;0&amp;lt;/order&amp;gt; &amp;lt;apply-actions&amp;gt; &amp;lt;action&amp;gt; &amp;lt;order&amp;gt;0&amp;lt;/order&amp;gt; &amp;lt;set-field&amp;gt; &amp;lt;icmpv4-match&amp;gt; &amp;lt;icmpv4-type&amp;gt;3&amp;lt;/icmpv4-type&amp;gt; &amp;lt;/icmpv4-match&amp;gt; &amp;lt;/set-field&amp;gt; &amp;lt;/action&amp;gt; &amp;lt;action&amp;gt; &amp;lt;order&amp;gt;1&amp;lt;/order&amp;gt; &amp;lt;set-field&amp;gt; &amp;lt;icmpv4-match&amp;gt; &amp;lt;icmpv4-code&amp;gt;1&amp;lt;/icmpv4-code&amp;gt; &amp;lt;/icmpv4-match&amp;gt; &amp;lt;/set-field&amp;gt; &amp;lt;/action&amp;gt; &amp;lt;/apply-actions&amp;gt; &amp;lt;/instruction&amp;gt; &amp;lt;/instructions&amp;gt; &amp;lt;match&amp;gt; &amp;lt;ethernet-match&amp;gt; &amp;lt;ethernet-type&amp;gt; &amp;lt;type&amp;gt;2048&amp;lt;/type&amp;gt; &amp;lt;/ethernet-type&amp;gt; &amp;lt;/ethernet-match&amp;gt; &amp;lt;ipv4-source&amp;gt;10.0.0.1/32&amp;lt;/ipv4-source&amp;gt; &amp;lt;ipv4-destination&amp;gt;10.0.0.3/32&amp;lt;/ipv4-destination&amp;gt;  &amp;lt;ip-match&amp;gt; &amp;lt;ip-protocol&amp;gt;1&amp;lt;/ip-protocol&amp;gt; &amp;lt;/ip-match&amp;gt; &amp;lt;/match&amp;gt; &amp;lt;/flow&amp;gt;&apos;&lt;/p&gt;


&lt;p&gt;The same BAD_ACTION and BAD_SET_ARGUMENT error we had seen in pcap file while testing using VTN Manger restconf to add ICMP codee and type. But in VTN manager karaf log we didnt see any issue regarding adding flows. So to cross check we tested using OFPlugin to know the issues.&lt;/p&gt;

&lt;p&gt;I would like to know the issue is in &quot;OVS&quot; or openflowplugin. please let me know what is the actual reason for the failure.&lt;/p&gt;

&lt;p&gt;Attached karaf logs and pcap file in OF13_FLOW_ICMP.zip&lt;/p&gt;</comment>
                            <comment id="57772" author="siva-karthik@hcl.com" created="Thu, 31 Mar 2016 09:45:11 +0000"  >&lt;p&gt;Attached zip file OF13_FLOW_ICMP.zip which has,&lt;/p&gt;

&lt;p&gt;OF_ICMP.pcap  --&amp;gt; pcap file which i have captured while using OpenFlowPlugin restconf command to test with ICMP code and type.&lt;/p&gt;

&lt;p&gt;VTN_ICMP.pcap --&amp;gt; pcap file which i have captured while using VTN Manager restconf command to test with ICMP code and type.&lt;/p&gt;

&lt;p&gt;Trace enabled karaf logs. In which i have observed error message in karaf.log.3.&lt;/p&gt;</comment>
                            <comment id="57775" author="siva-karthik@hcl.com" created="Thu, 31 Mar 2016 09:45:11 +0000"  >&lt;p&gt;Attachment OF13_FLOW_ICMP.zip has been added with description: OFPlugin and VTN pcap file and Karaf logs&lt;/p&gt;</comment>
                            <comment id="57773" author="siva-karthik@hcl.com" created="Thu, 14 Jul 2016 10:41:32 +0000"  >&lt;p&gt;Bug Verification :&lt;br/&gt;
==================&lt;/p&gt;

&lt;p&gt;Tested with Beryllium SR2 dsitro to check/verify ICMP code and type are added in flowentries with OFplugin.&lt;/p&gt;

&lt;p&gt;Since ICMP code and type are not supported in ovs2.3.0 for OF1.3&lt;br/&gt;
I have updated mininet with latest OVS 2.5.0.&lt;/p&gt;

&lt;p&gt;Issue is not reproduced. Now i can see in flowentries created with ICMP code and type actions successfully.&lt;/p&gt;

&lt;p&gt;Below are the command which i tried to have two different action field for ICMP type and code.&lt;/p&gt;

&lt;p&gt;And i followed the same steps which i tested earlier when i got issue.&lt;/p&gt;

&lt;p&gt;1) Configured mininet with sudo mn --topo tree,2  --controller remote,ip=10.106.138.117  --switch ovsk,protocols=OpenFlow13&lt;/p&gt;


&lt;p&gt;2) Add flows with action set-tp-dst-action and set-tp-src-action using below command, and response code is success.&lt;/p&gt;

&lt;p&gt; curl -v --user &quot;admin&quot;:&quot;admin&quot; -H &quot;Content-type: application/xml&quot; -X PUT &lt;a href=&quot;http://localhost:8181/restconf/config/opendaylight-inventory:nodes/node/openflow:3/table/2/flow/256&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;http://localhost:8181/restconf/config/opendaylight-inventory:nodes/node/openflow:3/table/2/flow/256&lt;/a&gt; -d &apos;&amp;lt;?xml version=&quot;1.0&quot; encoding=&quot;UTF-8&quot; standalone=&quot;no&quot;?&amp;gt; &amp;lt;flow xmlns=&quot;urn:opendaylight:flow:inventory&quot;&amp;gt; &amp;lt;strict&amp;gt;false&amp;lt;/strict&amp;gt; &amp;lt;flow-name&amp;gt;set-field-tcp-src&amp;lt;/flow-name&amp;gt; &amp;lt;id&amp;gt;256&amp;lt;/id&amp;gt; &amp;lt;cookie_mask&amp;gt;255&amp;lt;/cookie_mask&amp;gt; &amp;lt;cookie&amp;gt;101&amp;lt;/cookie&amp;gt; &amp;lt;table_id&amp;gt;2&amp;lt;/table_id&amp;gt; &amp;lt;priority&amp;gt;2&amp;lt;/priority&amp;gt; &amp;lt;instructions&amp;gt; &amp;lt;instruction&amp;gt; &amp;lt;order&amp;gt;0&amp;lt;/order&amp;gt; &amp;lt;apply-actions&amp;gt; &amp;lt;action&amp;gt; &amp;lt;order&amp;gt;0&amp;lt;/order&amp;gt; &amp;lt;set-field&amp;gt; &amp;lt;icmpv4-match&amp;gt; &amp;lt;icmpv4-type&amp;gt;3&amp;lt;/icmpv4-type&amp;gt; &amp;lt;/icmpv4-match&amp;gt; &amp;lt;/set-field&amp;gt; &amp;lt;/action&amp;gt; &amp;lt;action&amp;gt; &amp;lt;order&amp;gt;1&amp;lt;/order&amp;gt; &amp;lt;set-field&amp;gt; &amp;lt;icmpv4-match&amp;gt; &amp;lt;icmpv4-code&amp;gt;1&amp;lt;/icmpv4-code&amp;gt; &amp;lt;/icmpv4-match&amp;gt; &amp;lt;/set-field&amp;gt; &amp;lt;/action&amp;gt; &amp;lt;/apply-actions&amp;gt; &amp;lt;/instruction&amp;gt; &amp;lt;/instructions&amp;gt; &amp;lt;match&amp;gt; &amp;lt;ethernet-match&amp;gt; &amp;lt;ethernet-type&amp;gt; &amp;lt;type&amp;gt;2048&amp;lt;/type&amp;gt; &amp;lt;/ethernet-type&amp;gt; &amp;lt;/ethernet-match&amp;gt; &amp;lt;ipv4-source&amp;gt;10.0.0.1/32&amp;lt;/ipv4-source&amp;gt; &amp;lt;ipv4-destination&amp;gt;10.0.0.3/32&amp;lt;/ipv4-destination&amp;gt;  &amp;lt;ip-match&amp;gt; &amp;lt;ip-protocol&amp;gt;1&amp;lt;/ip-protocol&amp;gt; &amp;lt;/ip-match&amp;gt; &amp;lt;/match&amp;gt; &amp;lt;/flow&amp;gt;&apos;&lt;/p&gt;

&lt;p&gt;In Mininet i can see actions &quot;ICMP code and type&quot; changes:&lt;/p&gt;

&lt;p&gt;Mininet Flowentries Output:&lt;br/&gt;
===========================&lt;/p&gt;

&lt;p&gt;Here in below output in switch s3 you can see ICMP type and code entries.&lt;/p&gt;

&lt;p&gt;mininet&amp;gt; dpctl dump-flows&lt;/p&gt;
&lt;ul&gt;
	&lt;li&gt;
	&lt;ul&gt;
		&lt;li&gt;
		&lt;ul&gt;
			&lt;li&gt;s1 ------------------------------------------------------------------------&lt;br/&gt;
NXST_FLOW reply (xid=0x4):&lt;br/&gt;
 cookie=0x7f57ffffffffffff, duration=70.147s, table=0, n_packets=28, n_bytes=2380, idle_age=4, priority=0 actions=CONTROLLER:65535&lt;/li&gt;
			&lt;li&gt;s2 ------------------------------------------------------------------------&lt;br/&gt;
NXST_FLOW reply (xid=0x4):&lt;br/&gt;
 cookie=0x7f57ffffffffffff, duration=72.755s, table=0, n_packets=15, n_bytes=1275, idle_age=4, priority=0 actions=CONTROLLER:65535&lt;/li&gt;
			&lt;li&gt;s3 ------------------------------------------------------------------------&lt;br/&gt;
NXST_FLOW reply (xid=0x4):&lt;br/&gt;
 cookie=0x7f57ffffffffffff, duration=70.629s, table=0, n_packets=15, n_bytes=1275, idle_age=4, priority=0 actions=CONTROLLER:65535&lt;br/&gt;
 cookie=0x65, duration=86.111s, table=2, n_packets=0, n_bytes=0, idle_age=86, hard_age=3, priority=2,icmp,nw_src=10.0.0.1,nw_dst=10.0.0.3 &lt;br/&gt;
=====================================================================&lt;br/&gt;
actions=load:0x6-&amp;gt;NXM_OF_ICMP_TYPE[],load:0x3-&amp;gt;NXM_OF_ICMP_CODE[]&lt;/li&gt;
		&lt;/ul&gt;
		&lt;/li&gt;
	&lt;/ul&gt;
	&lt;/li&gt;
&lt;/ul&gt;


&lt;p&gt;======================================================================&lt;/p&gt;</comment>
                    </comments>
                    <attachments>
                            <attachment id="14049" name="OF13_FLOW_ICMP.zip" size="193978" author="siva-karthik@hcl.com" created="Thu, 31 Mar 2016 09:45:11 +0000"/>
                            <attachment id="14048" name="of_karaf_logs.zip" size="532578" author="siva-karthik@hcl.com" created="Tue, 29 Mar 2016 15:58:43 +0000"/>
                    </attachments>
                <subtasks>
                    </subtasks>
                <customfields>
                                                                            <customfield id="customfield_11400" key="com.atlassian.jira.plugins.jira-development-integration-plugin:devsummary">
                        <customfieldname>Development</customfieldname>
                        <customfieldvalues>
                            
                        </customfieldvalues>
                    </customfield>
                                                                                                                        <customfield id="customfield_10208" key="com.atlassian.jira.plugin.system.customfieldtypes:textfield">
                        <customfieldname>External issue ID</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>5618</customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                <customfield id="customfield_10201" key="com.atlassian.jira.plugin.system.customfieldtypes:url">
                        <customfieldname>External issue URL</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue><![CDATA[https://bugs.opendaylight.org/show_bug.cgi?id=5618]]></customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                <customfield id="customfield_10000" key="com.pyxis.greenhopper.jira:gh-lexo-rank">
                        <customfieldname>Rank</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>0|i032jr:</customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                </customfields>
    </item>
</channel>
</rss>