I'm glad to hear that you figured it out. I really didn't have an idea what the problem was.
On Mon, Jul 30, 2012 at 03:36:19AM -0300, daniel marques wrote: > Don't worry anymore, I've solved it! When I used the tc, I ended up messing > up with the interface and the OVS ended not working properly... This is how > I managed to do it: > > ip link add type veth > ip link set veth0 up > ip link set veth1 up > ovs-vsctl add-port br0 veth0 > ovs-vsctl add-port br1 veth1 > ovs-vsctl set port veth0 qos=@newqos -- --id=@newqos create qos > type=linux-htb other-config:max-rate=5000000 queues:0=@newqueue -- > --id=@newqueue create queue other-config:min-rate=3000000 > other-config:max-rate=3000000 > > Regards, > Daniel > > 2012/7/30 daniel marques <[email protected]> > > > Sorry to keep annoying you but I've already made this question at Mininet > > list some days before asking here and I didn't receive any kind of answer, > > but as you said it seems Mininet is making a confusion with OVS, so as a > > result of this, I decide to migrate to an OVS(1.6.1)+LXC testbed, but I am > > still with the queue/QoS problem. > > In this new testbed I decided to connect two switches together and I am > > trying to add queue/QoS in the port that connects to the other switch, at > > first I made this connection using patch ports but this was no use for me > > since this kind of interface is unable to work with Queues/QoS, so for the > > next step I have tried to work with veth, and working externally with tc > > I've managed to do the limit rate in this interface, but following the > > ovs-vsctl QoS example, I was unable to add any kind of QoS/queue services > > (ovs-ofctl and tc don't show any kind of queues in the port). Do you have > > any guess for this problem? > > Regards, > > Daniel > > > > 2012/7/26 Ben Pfaff <[email protected]> > > > >> This is another sign that you are not working with OVS 1.2.2, because > >> OVS 1.2.2 did not have a program named ovs-openflowd either. > >> > >> I think you should ask the mininet folks for help. > >> > >> On Thu, Jul 26, 2012 at 02:56:04AM -0300, daniel marques wrote: > >> > I am pretty sure that I am using OVS. Also I noted that ovs-ofctl and > >> > ovs-dpctl don't have any kind of parameter to add queues. For some odd > >> > reason seems that my email was cut, but I'll (try to) add the rest here. > >> > > >> > sudo ovs-ofctl queue-stats tcp:127.0.0.1:6634 > >> > OFPST_QUEUE reply (xid=0x1): 0 queues > >> > > >> > And this is how Mininet creates OpenFlow switches: > >> > ovs-openflowd dp0 tcp:192.168.1.139:6633 --fail=secure > >> --listen=ptcp:6634 > >> > --datapath-id=0000000000000001 > >> > ovs-openflowd dp1 tcp:192.168.1.139:6633 --fail=secure > >> --listen=ptcp:6635 > >> > --datapath-id=0000000000000002 > >> > > >> > Also it's important to note the version of the Open vSwitch is 1.2.2. > >> > > >> > Regards, > >> > Daniel > >> > > >> > 2012/7/26 Ben Pfaff <[email protected]> > >> > > >> > > On Thu, Jul 26, 2012 at 02:02:10AM -0300, daniel marques wrote: > >> > > > I am using Mininet to do my testbed setup and I am using Open > >> vSwitch in > >> > > my > >> > > > topology, so far I've managed to create a topology and I've already > >> put > >> > > my > >> > > > NOX plugin to work, now I'm willing to do some QoS tests but I am > >> having > >> > > > some problems to add queues to my OVS switches. > >> > > > I've tried to use the dpctl command as it follows: dpctl add-queue > >> tcp: > >> > > > 127.0.0.1:6634 3 1 2 > >> > > > >> > > Are you sure you're using OVS? OVS's program is called ovs-dpctl, not > >> > > dpctl, and ovs-dpctl doesn't have an add-queue command. > >> > > > >> > > > > _______________________________________________ discuss mailing list [email protected] http://openvswitch.org/mailman/listinfo/discuss
