flowvisor
flowvisor copied to clipboard
opennetworkinglab
Missing error message after unsuccessful OFPPC_PORT_DOWN
(I understand that this bug report is not precise at all, but I couldn't even figure out version number of Flowvisor being used in the testbed.)
My controller sent OFPPC_PORT_DOWN port configuration messages to a switch, but most probably it was not authorized to bring the port down. It seemed that the flowvisor filtered out the port configuration messages. I think it is OK if the Flowvisor doesn't let a controller disabling a (shared) port. The problem is that the controller is not notified about the rejection.
It would be good if the flowvisor could a OFPET_PORT_MOD_FAILED error message back to the controller. In this case, the ideal error code is OFPPMFC_EPERM, but that appeared in version 1.2 of the OpenFlow specification.
In the newer version of FlowVisor, to know its version number you just have to type ./fvctl.py list-version
Could you please tell more about your test script like what exactly are you running your controller with? Is it possible to attach that script along with this report? Also would it be possible to take a flowvisor log in DEBUG mode and attach that as well with this report. To run flowvisor in debug mode, you have to execute the foll. command - ./flowvisor.sh -d DEBUG Then go to /var/log/syslog and collect the log info.
Would it be possible to do this?
Thanks & Best Regards Sumanth
On Mon, Jun 3, 2013 at 12:26 AM, Felicián Németh [email protected]:
(I understand that this bug report is not precise at all, but I couldn't even figure out version number of Flowvisor being used in the testbed.)
My controller sent OFPPC_PORT_DOWN port configuration messages to a switch, but most probably it was not authorized to bring the port down. It seemed that the flowvisor filtered out the port configuration messages. I think it is OK if the Flowvisor doesn't let a controller disabling a (shared) port. The problem is that the controller is not notified about the rejection.
It would be good if the flowvisor could a OFPET_PORT_MOD_FAILED error message back to the controller. In this case, the ideal error code is OFPPMFC_EPERM, but that appeared in version 1.2 of the OpenFlow specification.
— Reply to this email directly or view it on GitHubhttps://github.com/OPENNETWORKINGLAB/flowvisor/issues/242 .
Unfortunately, I was just an unprivileged user of this testbed. But I'll ask the operators for details and whether they allow me to collect the log info. Alternatively, I can try to replicate the experiment in our lab and create a precise test scenario, but that would take time.