Search Mailing List Archives
[mininet-discuss] [ovs-discuss] Queue added to ports but not being used
blp at nicira.com
Fri Mar 6 14:24:59 PST 2015
What configuration does "tc" report for queues? What is in your OVS
On Fri, Mar 06, 2015 at 10:19:58PM +0000, Rui Braz wrote:
> You're right, i forgot to add it, sorry.
> Logs: http://pastebin.com/Sk2EQSNy
> Nuno B.
> De: Ben Pfaff <blp at nicira.com>
> Enviado: 6 de mar?o de 2015 22:15
> Para: Rui Braz
> Cc: mininet-discuss at lists.stanford.edu; discuss at openvswitch.org
> Assunto: Re: [ovs-discuss] Queue added to ports but not being used
> We're having a communication problem. I keep asking for logs and you
> keep not giving me logs. When you give me logs, I can start helping
> On Fri, Mar 06, 2015 at 10:11:39PM +0000, Rui Braz wrote:
> > I've restarted the daemon. I saw the logs being stored elsewhere, with the correct version. The queue is inserted and how many packets passed through it.
> > However the command 'sudo ovs-ofctl queue-get-config s1 s1-eth2
> > ' gives me the output
> > 'queue 0:
> > However as you may see the actions I did in mininet since i started the topology: http://pastebin.com/RwvV3K10
> > After I've defined the rates I created an enqueue action when flows went from s1->s2 and s2->s1. After that I did iperf and bandwidth was too low (around 500kb) and iperf took like 1 minute. After that I just used the action output:<port> in order to have connectivity and then I had around 10mb. Note that when link is not specified in mininet links are around 10Gpbs.
> > FYI I added the queues in another tab, but essencially the command was this one: "sudo ovs-vsctl -- set port s1-eth2 qos=@newqos -- --id=@newqos create qos type=linux-htb other-config:max-rate=10000000 queues:0=@newQ -- --id=@newQ create queue other-config:min-rate=150000 other-config:max-rate=250000". I added the same configuration to s1 and s2 switches on port the ports that connect those switches.
> > Is that normal behaviour ?
> > Regards,
> > Nuno B.
> > ________________________________________
> > De: Ben Pfaff <blp at nicira.com>
> > Enviado: 6 de mar?o de 2015 21:05
> > Para: Rui Braz
> > Cc: mininet-discuss at lists.stanford.edu; discuss at openvswitch.org
> > Assunto: Re: [ovs-discuss] Queue added but not shown using ovs-ofctl
> > OK.
> > I don't know how to help without the log. I guess you'll have to
> > figure out what's going on there first.
> > On Fri, Mar 06, 2015 at 08:47:02PM +0000, Rui Braz wrote:
> > > I don't need to start it, I just launch the topology. I think mininet vm already has scripts to launch it at boot. However after I start the VM i checked the processes that are running and i got this: http://pastebin.com/13bYMN3K
> > >
> > > Logs seem to be being saved in the same place according to this excert of the process ovs-vswitchd '--log-file=/usr/var/log/openvswitch/ovs-vswitchd.log'.
> > >
> > > However as i mentioned in previous emails, the last info I have on that is about openvswitch 2.0.2 and I have no problem in running mininet with openvswitch 2.3.
> > >
> > > Regards,
> > > Nuno B.
> > > ________________________________________
> > > De: Ben Pfaff <blp at nicira.com>
> > > Enviado: 5 de mar?o de 2015 19:15
> > > Para: Rui Braz
> > > Cc: mininet-discuss at lists.stanford.edu
> > > Assunto: Re: [ovs-discuss] Queue added but not shown using ovs-ofctl
> > >
> > > On Thu, Mar 05, 2015 at 05:20:51PM +0000, Rui Braz wrote:
> > > > I've upgraded the OVS from 2.0.2 to 2.3 using this script: http://pastebin.com/3ViQxg7D. Script was on github from mininet if I'm not mistaken.
> > > >
> > > > After doing that the logs generated from OVS are not sent to /var/log/openvswitch because when I go there and print the log only appears to me the log from last version which is 2.0.2 as you may see here: http://pastebin.com/Tf4VtAtz
> > > >
> > > > Are the logs being generated elsewhere ?
> > >
> > > When you start ovs-vswitchd, where you do tell it to put the log?
> > >
> > > > Also I'm able to see the queues I've created if I do "sudo ovs-vsctl list queue".
> > >
> > > Not relevant.
More information about the mininet-discuss