Commit 1a48941e authored by adietmue's avatar adietmue
Browse files

Small clarifications to README.

parent bf006c66
......@@ -234,7 +234,9 @@ The controller is started with the selected traffic scenario and automatically p
The controller variable `traffic` contains a list of dictionaries.
Each dict contains the information of one flow, such as `src`, `dst`, etc.
:no_entry: The controller has not accessed to the failure scenario. You are not allowed to read the failure scenario files from the controller, and you can't use Open vSwitch commands to detect a failure (we use Open vSwitches to simulate silent failures, instead of bringing the interface down). As in a real network, to detect failures you have to rely on the protocols provided by the routers and/or you can implement your own failure detection mechanism in P4 and use it in the switches.
:no_entry: The controller cannot access the failure scenario.
You are not allowed to read the failure scenario files from the controller, and you must not use Open vSwitch commands (`ovs-ofctl`) to check whether we have failed a link (we use Open vSwitches to simulate silent failures, instead of bringing the interface down).
As in a real network, to detect failures you have to rely on the protocols provided by the routers and/or you can implement your own failure detection mechanism in P4 and use it in the switches.
The provided controller already installs the required rules for L2 forwarding onto the switches.
......
Supports Markdown
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment