 |
Finally, lets look at path restoration when OVS2 recovers. The recovery process follows five steps: First, the Topology Monitor detects OVS2 restoration. Second, theres a WAIT delay for the stabilization period. Third, IS_NODE_HEALTHY verifies OVS2s status. Fourth, REMOVE_FLOWS removes the backup path flows. Fifth, INSTALL_FLOWS reinstalls the original path flows. On the left panel, you can see the Slice Manager terminal log detecting OVS2 restoration and initiating path recovery. On the right panel, the Wireshark capture shows VLAN 200 traffic transitioning from the backup path back to the restored primary path. This demonstrates that our system not only handles failures but also automatically restores optimal paths when nodes recover. |
IEEE/ICACT20260257 Slide.19
[Big Slide]
[YouTube]