C.1) Observations and commentaries of the results and the redundancy scenarios.
As a reminder, in the previous chapter, we tried to build the following configuration(click on links below), in order to respect the following traffic engineering requirement:
Regarding the egress/outbound traffic for each zone, results are in accordance with the paragraph B.1.b).
Now that the configuration has been defined and implemented, it is interesting to make some tests by cutting some Ebgp speakers voluntarily, and observe if the ingress/inbound traffic for the customers is flowing accordingly to our redundancy scenarios that we defined previously.
In this chapter, we will emphasis on Zone-D_E download/ingress traffic. For easiness and visibility, the following figures will highlight only the prefix-C of Zone-D-E: 22.214.171.124/24.
- C.1) Observations /commentaries of the results and the redundancy scenarios
- C.1.a) Traffic Analysis 1: Scenario A: Zone-D_E ingress/download traffic, all Ebgp links are up.
- C.1.b) Traffic Analysis 2: Scenario B: Zone-D-E ingress/download traffic, primary link ISP-D is cut
- C.1.c) Traffic Analysis 3: Scenario C: Zone-D-E ingress/download traffic: primary link ISP-D is cut, secondary backup link ISP-B is cut too.
- C.1.d) Traffic Analysis 4: Scenario D: Zone-D-E ingress/download traffic, primary link ISP-D is restored however secondary backup link ISP-B is still down
- C.1.e) Traffic Analysis 5: Scenario E: Zone-D-E ingress/download traffic, primary link is still cut however secondary link ISP-B is restored