I had the same issue some time ago. Probably you cannot use Mininet tc and ovs queues together, because both are based on HTB. There is a conflict.
Giuseppe Giuseppe Cofano, PhD Dipartimento di Ing. Elettrica e dell'Informazione Politecnico di Bari, Italy Via Orabona 4, 70125 Bari Italy +39 080 596 3851 giuseppe.cof...@poliba.it <g.cof...@poliba.it>; g.cofan...@gmail.com 2016-05-02 17:33 GMT+02:00 Ben Pfaff <b...@ovn.org>: > On Sat, Apr 30, 2016 at 08:55:41PM +0200, Guillermo Chica wrote: > > Hi, > > > > I have created a topology with mininet. When I've added the links, I've > > used the delay parameter, as in self.addLink( node1, node2, delay='5ms'). > > After running the topology with sudo mn --custom topo5g.py --topo topo5g > > --switch ovsk --controller remote --mac --arp --link tc > > > > I have created a qos for a switch and I have added the flows to force > > traffic to go through these queues, like this: > > > > sudo ovs-vsctl -- set Port s1-eth1 qos=@newqos -- set Port s1-eth2 > > qos=@newqos -- --id=@newqos create QoS type=linux-htb > > other-config:max-rate=100000 queues=0=@q0,1=@q1 -- --id=@q0 create Queue > > other-config:min-rate=100000 other-config:max-rate=100000 -- --id=@q1 > > create Queue other-config:min-rate=1000 other-config:max-rate=1000 > > > > sudo ovs-ofctl add-flow s1 > > > in_port=2,dl_type=0x0800,nw_proto=6,nw_src=10.0.0.8,nw_dst=10.0.0.4,tp_src=333,priority=100,actions=enqueue:1:1 > > sudo ovs-ofctl add-flow s1 > > > in_port=1,dl_type=0x0800,nw_proto=6,nw_src=10.0.0.4,nw_dst=10.0.0.8,tp_dst=333,priority=100,actions=enqueue: > > > > However, when I use sudo ovs-ofctl queue-stats s1, I obtain this answer: > > OFPST_QUEUE reply (xid=0x2): 0 queues. > > > > And obviously the QoS does not work. > > > > This does not happen when I don't use the delay parameter in mininet. If > I > > don't define a delay in mininet, the queues exist and the QoS works fine. > > Why is that? Can't I have queues and control delay at the same time? > > I guess that mininet implements delay via some form of QoS. You might > be more likely to get a useful answer on a mininet mailing list. > _______________________________________________ > discuss mailing list > discuss@openvswitch.org > http://openvswitch.org/mailman/listinfo/discuss >
_______________________________________________ discuss mailing list discuss@openvswitch.org http://openvswitch.org/mailman/listinfo/discuss
