Thanks Syed. It was a snippet that I showed. There are flows with n_packets
> 0.

cookie=0, duration_sec=382s, duration_nsec=535000000s, table_id=0,
priority=32768, n_packets=757, n_bytes=58265,
idle_timeout=0,hard_timeout=0,tcp,nw_dst=10.0.0.2,tp_dst=34092,actions=mod_dl_dst:00:00:00:00:00:02,mod_nw_src:10.0.0.253,mod_tp_src:6002,output:2
  cookie=0, duration_sec=410s, duration_nsec=118000000s, table_id=0,
priority=32768, n_packets=0, n_bytes=0,
idle_timeout=0,hard_timeout=0,tcp,nw_dst=10.0.0.253,tp_dst=6008,actions=CONTROLLER:65535,mod_dl_dst:00:00:00:00:00:02,mod_nw_dst:10.0.0.2,mod_tp_dst:5000,output:2
  cookie=0, duration_sec=410s, duration_nsec=120000000s, table_id=0,
priority=32768, n_packets=382, n_bytes=33158,
idle_timeout=0,hard_timeout=0,tcp,nw_dst=10.0.0.253,tp_dst=6002,actions=CONTROLLER:65535,mod_dl_dst:00:00:00:00:00:04,mod_nw_dst:10.0.0.4,mod_tp_dst:5000,output:4

I check the flow-tables every 1 sec. Flow-table entries dont grow with time.

Thanks,
Rohan

On Tue, Apr 17, 2012 at 3:39 PM, Syed Muhammad Mohsin Kazmi <
[email protected]> wrote:

> If you see at flow table,there is no packet hits the flow at field
> n_packets=0. In my opinion, every packet sent to controller where your
> app. write down the flow for it to the swtich each time, so that is
> why your flow-table entries are flushed after some time. You should
> check your code again, i think so, there is a problem.
>
> Regards,
> Syed M. Mohsin Kazmi
>
> On Wed, Apr 18, 2012 at 12:13 AM, Rohan Gandhi <[email protected]>
> wrote:
> > Hello All,
> >
> > I am sorry to bother you again. I got most of my questions sorted out.
> But
> > my flow-table entries are getting flushed after some time. All the flows
> > that I add have idle and hard timeout set to permanent. The switch has 6
> > ports with 3 TCP connections (1 TCP connection for 2 hosts with no host
> > having more than 1 connection). I continuously send the packets over
> these 3
> > flows. Any idea on why this is happening? These does not happen if I
> limit
> > the traffic (by adding a delay at the hosts). I could not quantify how
> much
> > traffic I reduced though.
> >
> > The following is the snippet of the flow-table.
> >
> > Thanks!
> > Rohan
> >
> > openflow@openflowtutorial:~$ dpctl dump-flows tcp:127.0.0.1:6634
> > stats_reply (xid=0x2e34f6b7): flags=none type=1(flow)
> >   cookie=0, duration_sec=12s, duration_nsec=558000000s, table_id=0,
> > priority=32768, n_packets=0, n_bytes=0,
> >
> idle_timeout=0,hard_timeout=0,tcp,nw_dst=10.0.0.253,tp_dst=6008,actions=CONTROLLER:65535,mod_dl_dst:00:00:00:00:00:02,mod_nw_dst:10.0.0.2,mod_tp_dst:5000,output:2
> > ...
> > ..
> >
> >
> >
> > openflow@openflowtutorial:~$ dpctl dump-flows tcp:127.0.0.1:6634
> > stats_reply (xid=0xc01ad743): flags=none type=1(flow)
> >
>

Reply via email to