-
Bug
-
Resolution: Duplicate
-
None
-
unspecified
-
None
-
Operating System: All
Platform: All
-
2628
Start mininet and connect to controller running Helium SR1. Then from Yang UI create the following flow and send to switch:
/config /nodes /node /<nodeid>/table /0
flow id = 12
ethernet-source = 00:00:1c:ed:0f:9f
instruction order = 0
instruction = apply-actions-case
action order = 0
action = output-action-case
action order = 0
output-node-connector = openflow:19705861207:12
barrier = True
priority = 11
table_id = 0
Please note that the Barrier flag is set to true so the controller should send a BARRIER_REQUEST message and process the response from the switch. In the attached pcap, packet 79 sends the flow mod, packet 81 sends the barrier_request and packet 82 is the barrier_response.
If you look at the karaf log, you will see the following error message:
2015-01-22 14:40:56,269 | WARN | entLoopGroup-9-2 | ResponseExpectedRpcListener | 218 - org.opendaylight.openflowjava.openflow-protocol-impl - 0.5.1.Helium-SR1 | Request for RpcResultKey [xid=39538, outputClazz=org.opendaylight.yang.gen.v1.urn.opendaylight.openflow.protocol.rev130731.BarrierOutput] did not receive a response
I am not sure if the error message is getting printed in error or if the controller is not able to process the barrier response message sent from the switch.
This is against Helium-SR1. The version field in bugzilla seems to be on the fritz and is not showing option other than "unspecified".
- duplicates
-
OPNFLWJAVA-42 Confusing WARN log even when rpc is handled correctly
- Resolved