<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: VAN 2.2 flow issue with Mininet ping - output actions show incorrect port_id in Software Defined Networking</title>
    <link>https://community.hpe.com/t5/software-defined-networking/van-2-2-flow-issue-with-mininet-ping-output-actions-show/m-p/6473414#M280</link>
    <description>&lt;P&gt;Hello Stace,&lt;BR /&gt;&lt;BR /&gt;We are glad that your problem is solved.&lt;BR /&gt;Please do let us know if you need further assistance.&lt;BR /&gt;&lt;BR /&gt;Please feel free to reply incase you have more questions around the same topic or open a new thread if new topic.&lt;BR /&gt;&lt;BR /&gt;Thanks&lt;BR /&gt;HP SDN Team&lt;BR /&gt;&lt;BR /&gt;&lt;/P&gt;</description>
    <pubDate>Tue, 13 May 2014 07:44:01 GMT</pubDate>
    <dc:creator>sdnindia</dc:creator>
    <dc:date>2014-05-13T07:44:01Z</dc:date>
    <item>
      <title>VAN 2.2 flow issue with Mininet ping - output actions show incorrect port_id</title>
      <link>https://community.hpe.com/t5/software-defined-networking/van-2-2-flow-issue-with-mininet-ping-output-actions-show/m-p/6470378#M274</link>
      <description>&lt;P&gt;I have just installed 2.2 and am seeing a difference from 2.0 with regards to REST call&amp;nbsp;of/datapaths/&lt;EM&gt;DPID&lt;/EM&gt;/ports. I am using mininet to create the topolgy and am pinging between two nodes.&lt;SPAN&gt;&lt;BR /&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;In 2.0 I see the the output of a correct port_id but in 2.2 i see stuff like&amp;nbsp;"output": 4294967290. There is no port_id of&amp;nbsp;4294967290.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Has 2.2 changed how to shows ICMP flows or is this a bug?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Stace&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Fri, 09 May 2014 09:37:41 GMT</pubDate>
      <guid>https://community.hpe.com/t5/software-defined-networking/van-2-2-flow-issue-with-mininet-ping-output-actions-show/m-p/6470378#M274</guid>
      <dc:creator>stacehip</dc:creator>
      <dc:date>2014-05-09T09:37:41Z</dc:date>
    </item>
    <item>
      <title>Re: VAN 2.2 flow issue with Mininet ping - output actions show incorrect port_id</title>
      <link>https://community.hpe.com/t5/software-defined-networking/van-2-2-flow-issue-with-mininet-ping-output-actions-show/m-p/6472440#M277</link>
      <description>&lt;P&gt;Fixed - controller was on Hybrid mode. I changed it to OpenFlow only and it worked as expected.&lt;/P&gt;</description>
      <pubDate>Mon, 12 May 2014 12:37:19 GMT</pubDate>
      <guid>https://community.hpe.com/t5/software-defined-networking/van-2-2-flow-issue-with-mininet-ping-output-actions-show/m-p/6472440#M277</guid>
      <dc:creator>stacehip</dc:creator>
      <dc:date>2014-05-12T12:37:19Z</dc:date>
    </item>
    <item>
      <title>Re: VAN 2.2 flow issue with Mininet ping - output actions show incorrect port_id</title>
      <link>https://community.hpe.com/t5/software-defined-networking/van-2-2-flow-issue-with-mininet-ping-output-actions-show/m-p/6473414#M280</link>
      <description>&lt;P&gt;Hello Stace,&lt;BR /&gt;&lt;BR /&gt;We are glad that your problem is solved.&lt;BR /&gt;Please do let us know if you need further assistance.&lt;BR /&gt;&lt;BR /&gt;Please feel free to reply incase you have more questions around the same topic or open a new thread if new topic.&lt;BR /&gt;&lt;BR /&gt;Thanks&lt;BR /&gt;HP SDN Team&lt;BR /&gt;&lt;BR /&gt;&lt;/P&gt;</description>
      <pubDate>Tue, 13 May 2014 07:44:01 GMT</pubDate>
      <guid>https://community.hpe.com/t5/software-defined-networking/van-2-2-flow-issue-with-mininet-ping-output-actions-show/m-p/6473414#M280</guid>
      <dc:creator>sdnindia</dc:creator>
      <dc:date>2014-05-13T07:44:01Z</dc:date>
    </item>
  </channel>
</rss>

