Hi, corey
Please keep mailing list :)

Sorry, I don't know whether the cause is in Ryu app or Mininet.
The software you seem to use (https://github.com/muzixing/ryu/tree/master/ryu/app/network_awareness) was forked more than 3 years ago,
and committed more than 100 times from this point.
I don't know this so much, so I think you should ask the support team of this software.


Thanks,
Fujimoto

On 2017年10月21日 18:15, corey ross wrote:
Hello Fujimoto,

Sorry for the delay. I have installed OVS 2.7.2 and it seems the problem was not due to OVS, I realized if I run my Mininet topology and wait for few seconds before starting the Ryu app then there wont be any switch reconnection in  the app. This behavior happens in looped networks. Would you tell me if this is due to the Ryu app or the Mininet?


BTW I have attached the app I am using in this mail ( just in case you require it). I am usingthis <https://github.com/muzixing/ryu/tree/master/ryu/app/network_awareness> app and modified the network-aware module to send and receive flow-table features.

Thank You very much for your time.

Regards,
Corey


On Sun, Oct 1, 2017 at 5:02 PM, corey ross <coreyvr...@gmail.com <mailto:coreyvr...@gmail.com>> wrote:

    Hi, Fujimoto

    Yes, I installed OVS 2,.8 but It was talking long time for the
    controller to get the switches, then I saw this bug.
    Sure I will install OVS 2.7.2 and then I will email you my
    finding. However at the moment I don't have access to my system so
    it might take some times....

    Thank You for your reply :)


    On Thu, Sep 28, 2017 at 6:39 AM, Fujimoto Satoshi
    <satoshi.fujimo...@gmail.com <mailto:satoshi.fujimo...@gmail.com>>
    wrote:

        Hi, corey

        Sorry, OVS 2.8.0 has a problem so it may be difficult to run it...

        OVS 2.8.0 can not work with passive controller connection, it
        will crash.
        The fix has been merged to master, but it is not released yet:
        
https://github.com/openvswitch/ovs/commit/1ea2184501d43352ec40764f5eaa3cbd07e3fee3
        
<https://github.com/openvswitch/ovs/commit/1ea2184501d43352ec40764f5eaa3cbd07e3fee3>

        I think it is better to try with OVS 2.7.2. It is stable .
        Could you try with it?


        Thanks,
        Fujimoto


        On 2017年09月27日 20:00, corey ross wrote:
        Mr Fujimoto I am using Ryu 4.17 and OVS 2.6. I have some
        difficulties in installing OVS 2.8 as soon as I fix this
        problem I will share the results with you.

        On Tue, Sep 26, 2017 at 7:12 AM, Fujimoto Satoshi
        <satoshi.fujimo...@gmail.com
        <mailto:satoshi.fujimo...@gmail.com>> wrote:

            Hi, corey

            Sorry, I couldn't see the reconnection with your code, it
            seems to work.

            Please confirm the followings:
            * Using the latest version of Ryu(4.17)
            * (If you use OVS,) Using the latest version of OVS(2.8.0)

            If confirmed, would you send me the whole of your code?

            Thanks,
            Fujimoto


            On 2017年09月25日 20:24, corey ross wrote:
            Hello,
            I am trying to send and parse table feature message.
            This is my code:

                @set_ev_cls(ofp_event.EventOFPSwitchFeatures,
                CONFIG_DISPATCHER)
                  def switch_features_handler(self, ev):
                      """
                         Send miss-table flow entry to datapaths and
                send the table feature request.
                      """
                      datapath = ev.msg.datapath
                      ofproto = datapath.ofproto
                      parser = datapath.ofproto_parser
                      msg = ev.msg
                self.logger.info
                <http://self.logger.info>("switch:%s connected",
                datapath.id <http://datapath.id>)

                      # install table-miss flow entry
                      match = parser.OFPMatch()
                      actions =
                [parser.OFPActionOutput(ofproto.OFPP_CONTROLLER,
                ofproto.OFPCML_NO_BUFFER)]
                self.add_flow(datapath, 0, match, actions)

                      # send_table feature request
                      stats =
                parser.OFPTableFeaturesStatsRequest(datapath, 0, [])
                datapath.send_msg(stats)

                @set_ev_cls(ofp_event.EventOFPTableFeaturesStatsReply,
                MAIN_DISPATCHER)
                  def _table_features_handler(self, ev):
                      """
                          It get the max entries for a table and
                store it in max_table_capacity.
                      """
                      msg = ev.msg
                      datapath = msg.datapath
                      # print(msg.body)
                      for stat in msg.body:
                          if stat.table_id == 0:
                self.table_body[datapath.id
                <http://datapath.id>]['body'] = stat
                self.logger.debug('table_body: %s',
                self.table_body[datapath.id <http://datapath.id>])

            but as you can see when I run the program it causes the
            switches to reconnect:

                switch:2 connected
                switch:6 connected
                switch:7 connected
                switch:4 connected
                switch:1 connected
                switch:3 connected
                switch:5 connected

                switch:7 connected
                switch:6 connected
                switch:1 connected
                switch:4 connected
                switch:5 connected
                switch:3 connected
                switch:2 connected

            What could be wrong? What is the correct way to request
            for table features (during) handshake?

            Thank you


            
------------------------------------------------------------------------------
            Check out the vibrant tech community on one of the world's most
            engaging tech sites, Slashdot.org!http://sdm.link/slashdot


            _______________________________________________
            Ryu-devel mailing list
            Ryu-devel@lists.sourceforge.net
            <mailto:Ryu-devel@lists.sourceforge.net>
            https://lists.sourceforge.net/lists/listinfo/ryu-devel
            <https://lists.sourceforge.net/lists/listinfo/ryu-devel>




        
------------------------------------------------------------------------------
        Check out the vibrant tech community on one of the world's most
        engaging tech sites, Slashdot.org!http://sdm.link/slashdot


        _______________________________________________
        Ryu-devel mailing list
        Ryu-devel@lists.sourceforge.net
        <mailto:Ryu-devel@lists.sourceforge.net>
        https://lists.sourceforge.net/lists/listinfo/ryu-devel
        <https://lists.sourceforge.net/lists/listinfo/ryu-devel>




------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Ryu-devel mailing list
Ryu-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ryu-devel

Reply via email to