Due to a ransomware attack, the wiki was reverted to a July 2022 version. . We apologize for the lack of a more recent valid backup.
...
- 3.1 Check routes installed - FAIL
- Routes are wrong!
- 3.2 Check M2S intents installed - FAIL
- MultiPointToSinglePoint Intent Num is wrong!
- 3.3 Check whether all flow status are ADDED - PASS FAIL
- Flow status is wrong!
Case 4: Ping test for each route, all hosts behind BGP peers - FAIL
...
- 5.1 Bring down the link between sw32 and p64514 - PASS
- 5.2 Check routes installed - FAIL
- Route number is wrong!
- 5.3 Check M2S intents installed - FAIL
- M2S intent number is wrong!
- 5.4 Bring down the link between sw8 and p64515 - PASS
- 5.5 Check routes installed - FAIL
- Route number is wrong!
- 5.6 Check M2S intents installed - FAIL
- M2S intent number is wrong!
- 5.7 Bring down the link between sw28 and p64516 - PASS
- 5.8 Check routes installed - FAIL
- Route number is wrong!
- 5.9 Check M2S intents installed - FAIL
- M2S intent number is wrong!
- 5.10 Check whether all flow status are ADDED - PASS FAIL
- Flow status is wrong!
- 5.11 BGP speakers ping peers, expect all tests to fail - PASS
- 5.12 Check ping between each host pair, expect all to succede=False - PASS
...
- 6.1 Bring up the link between sw32 and p64514 - PASS
- 6.2 Check routes installed - FAIL
- Route number is wrong!
- 6.3 Check M2S intents installed - FAIL
- M2S intent number is wrong!
- 6.4 Bring up the link between sw8 and p64515 - PASS
- 6.5 Check routes installed - FAIL
- Route number is wrong!
- 6.6 Check M2S intents installed - FAIL
- M2S intent number is wrong!
- 6.7 Bring up the link between sw28 and p64516 - PASS
- 6.8 Check routes installed - FAIL
- Route number is wrong!
- 6.9 Check M2S intents installed - FAIL
- M2S intent number is wrong!
- 6.10 Check whether all flow status are ADDED - PASS FAIL
- Flow status is wrong!
- 6.11 BGP speakers ping peers, expect all tests to fail - PASS
- 6.12 Check ping between each host pair, expect all to succede=False - PASS
...