frederik.maassen
/
ComparisonOfFastRecoveryMethodsInNetworks
Archived
3
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity

some changes

Browse Source
master
Frederik Maaßen 2 years ago
parent 8014409c39
commit a707adc65d
2 changed files with 8 additions and 3 deletions
Show all changes Ignore whitespace when comparing lines Ignore changes in amount of whitespace Ignore changes in whitespace at EOL
Show Stats Download Patch File Download Diff File
  1. 6
      implementation/topologies/8r4h_topo.py
  2. 5
      thesis/content/evaluation/failure_path_networks.tex

6
implementation/topologies/8r4h_topo.py
Unescape View File

@ -552,9 +552,9 @@ class EightRoutersFourHosts(CustomTopo):
"use_pre_defined_function": True,
"separate_definitions": True,
"command_pre": ("measure_packet_flow", (
'h1', 'h8', '10.8.0.101', ["r1", "r2", "r4", "r7"], 30, 1, "udp_before_failure", [0, 20000], "UDP Packet flow on routers before failure", "udp", 100)),
'h1', 'h8', '10.8.0.101', ["r1", "r2", "r4", "r7"], 30, 1, "udp_before_failure", [0, 22000], "UDP Packet flow on routers before failure", "udp", 100)),
"command_post": ("measure_packet_flow", (
'h1', 'h8', '10.8.0.101', ["r1", "r2", "r4", "r7"], 30, 1, "udp_after_failure", [0, 20000], "UDP Packet flow on routers after failure", "udp", 100)),
'h1', 'h8', '10.8.0.101', ["r1", "r2", "r4", "r7"], 30, 1, "udp_after_failure", [0, 22000], "UDP Packet flow on routers after failure", "udp", 100)),
},
"failures": [
@ -579,7 +579,7 @@ class EightRoutersFourHosts(CustomTopo):
"execute": {
"use_pre_defined_function": True,
"command": ("measure_packet_flow", (
'h1', 'h8', '10.8.0.101', ["r1", "r2", "r4", "r7"], 30, 1, "udp_concurrent_failure", [0, 20000], "UDP Packet flow on routers before failure", "udp", 100)),
'h1', 'h8', '10.8.0.101', ["r1", "r2", "r4", "r7"], 30, 1, "udp_concurrent_failure", [0, 22000], "UDP Packet flow on routers before failure", "udp", 100)),
},
"failures": [

5
thesis/content/evaluation/failure_path_networks.tex
Unescape View File

@ -203,7 +203,9 @@ We measure the amount of TCP packets forwarded in our failure path networks. For
\end{figure}
At a first glance the results from the test run on the minimal topology and our failure path networks are very similar. As in \cref{evaluation_minimal_packet_flow} we observe that TCP packets sent through the looped path only forward the TCP packets bearing data as returning ACKs from the \textit{iperf} server are not passed into the loop. Router R1 however forwards an additional 50\% of packets, forwarding packets containing data twice on their way to the \textit{iperf} server and forwarding returning ACKs once back to the host H1.
The implications for the network are however quite more severe the more routers are contained on the looped paths. Because each router that is not the start and end point of our loop path forwards each packet in the loop twice, the amount of packets forwarded relative to the total amount of packets forwarded in a healthy network will steadily increase. For our first failure path this means an additional 50\% of packets forwarded. For our second failure path network the amount of packets forwarded even increases by 60\%.
\subsubsection{With FRR and ShortCut}
ShortCut was able to cut off the loop and therefore reduce the amount of packets forwarded to the original amount. Because this is similar to the behaviour in \cref{evaluation_minimal_tcp_packet_flow} we omitted additional graphs from our results.
@ -229,5 +231,8 @@ ShortCut was able to cut off the loop and therefore reduce the amount of packets
\label{fig:evaluation_failure_path_packet_flow_udp_wo_sc}
\end{figure}
\subsubsection{With FRR and ShortCut}
Similar to the behaviour of ShortCut in our TCP packet flow measurements, it was able to restore the network to its original amount of packets forwarded on the routers. Because this behaviour does not add any room for interpretation, we omitted graphs for these measurements from our results.