Hello Rob,
I am trying to configure the queues to send QUEUE actions, but I am
facing a problem that I would like to share with the list.
I am acessing the switch S1 and running the command:
dpctl add-queue tcp:localhost:6633
But NOX is returning the error:
Passive tcp interface receive connection
stream: negotiated OpenFlow version 0x001..
Sucess sending in 'sending switch config'
Sucess sending in 'receiving features reply'
Sucess receiving in 'receiving features reply'
Warn:stream: receive error: Connection reset by peer
Warn: Error receiving features reply: recv: Connection reset by peer.
And the queue isn´t created.
Can someone help me?
My best regards.
Luciano Ignaczak
Citando Rob Sherwood <[email protected]>:
On Fri, May 27, 2011 at 5:16 AM, <[email protected]> wrote:
[Unfortunately someone else will have to answer the mininet question]
2 - A few days ago Rob answered that the last version of FlowVisor doesn´t
support Bandwidth yet. I´d like your opinion about the best way to implement
some kind of QoS. I divided my mininet´s network in two slices (voice and
data) and I have one NOX controller for each slice.
So, first, I'm hoping to have a chance to add this QoS feature soon,
but, that said:
Your nox controllers could just send QUEUE actions (which take a port
and a queue index as parameter) instead of output actions. You still
have to configure the switches manually to make the queue indexes to a
specific queuing discipline.
HTH,
- Rob
.
----------------------------------------------------------------
This message was sent using IMP, the Internet Messaging Program.
_______________________________________________
openflow-discuss mailing list
[email protected]
https://mailman.stanford.edu/mailman/listinfo/openflow-discuss
