|
|
1 |
(% class="row" %) |
|
|
2 |
((( |
|
|
3 |
(% class="col-xs-12 col-sm-7 test-report-content" %) |
|
|
4 |
((( |
|
|
5 |
---- |
|
|
6 |
|
|
|
7 |
Performing liveness checks, such as enhanced fault detection, has several benefits. Once a failing path in a network is detected, operators can implement immediate corrective measures to avoid any traffic disruption. |
|
|
8 |
This year's testing also covered Seamless Bidirectional Forwarding Detection (S-BFD), among other focus areas. The given topology comprised two PE routers, each attached to a pair of dual spines. The configurations established S-BFD sessions from an initiator node to a reflector node, transmitting continuous probes along the primary path. |
|
|
9 |
To artificially induce failure without physically breaking the links, we applied an ACL on one of the spine links that dropped any MPLS packets (including S‑BFD) but not IGP packets, thus allowing IGP to continue attracting traffic to the failed link. Because routers encapsulated S‑BFD in MPLS (the same as the protected SR-TE), the packets got dropped, too. We didn't bring down the link; thus, we could see how fast the network could detect partial failure by the S‐BFD probes that were not arriving. |
|
|
10 |
|
|
|
11 |
[[Figure 83: Liveness of SR Policy using Seamless BFD>>image:433705802541826049_SRMPLS-11-SBFD-Generic-6-v1.png||alt="Figure 83" width="550"]] |
|
|
12 |
|
|
|
13 |
Once the S‐BFD detected the absence of returning probes from any instance on the primary path, it triggered the SR‐TE policy to seamlessly switch traffic over to the backup path within the configured failure threshold and delay. Therefore, network operations were not interrupted, which was helpful in the effective functioning of S‐BFD, as it enabled preventive measures in mitigating path failures in an SR‐MPLS environment. |
|
|
14 |
|
|
|
15 |
{{container cssClass="tc-role-table"}} |
|
|
16 |
(% class="table-bordered" %) |
|
|
17 |
|=Initiator \ Reflector|=Arista 7280R3|=Juniper PTX10002-36QDD|=Juniper ACX7100-48L|=Nokia 7750 SR-1|=Nokia 7730 SXR-1x-44s|=Ciena 5134|=Ribbon NPT-2100|=Huawei NetEngine A816|=Huawei NetEngine 8000 M14|=H3C CR16000-M1A |
|
|
18 |
|=Arista 7280R3| |✔|✔|✔|✔|✔|✔|✔|✔|✔ |
|
|
19 |
|=Juniper PTX10002-36QDD|✔| | |✔|✔|✔|✔|✔|✔|✔ |
|
|
20 |
|=Juniper ACX7100-48L|✔| | |✔|✔|✔|✔|✔|✔|✔ |
|
|
21 |
|=Nokia 7750 SR-1|✔|✔|✔| | | |✔|✔|✔|✔ |
|
|
22 |
|=Nokia 7730 SXR-1x-44s|✔|✔|✔| | | | | | | |
|
|
23 |
|=Ciena 5134| | | | | | | | | | |
|
|
24 |
|=Ribbon NPT-2100|✔|✔|✔| |✔| | |✔|✔|✔ |
|
|
25 |
|=Huawei NetEngine A816|✔|✔|✔|✔|✔| |✔| | |✔ |
|
|
26 |
|=Huawei NetEngine 8000 M14|✔|✔|✔|✔|✔| |✔| | |✔ |
|
|
27 |
|=H3C CR16000-M1A|✔|✔|✔|✔|✔| |✔|✔| | |
|
|
28 |
|
|
|
29 |
Table 26: Liveness of SR Policy using Seamless BFD |
|
|
30 |
{{/container}} |
|
|
31 |
|
|
|
32 |
{{container cssClass="tc-role-table"}} |
|
|
33 |
(% class="table-bordered" %) |
|
|
34 |
|=PE|=Spine|=Traffic Generator |
|
|
35 |
|((( |
|
|
36 |
Arista 7280R3, |
|
|
37 |
Ciena 5134, |
|
|
38 |
H3C CR16000-M1A, |
|
|
39 |
Huawei NetEngine 8000 M14, |
|
|
40 |
Huawei NetEngine A816, |
|
|
41 |
Juniper ACX7100-48L, |
|
|
42 |
Juniper PTX10002-36QDD, |
|
|
43 |
Nokia 7730 SXR-1x-44s, |
|
|
44 |
Nokia 7750 SR-1, |
|
|
45 |
Ribbon NPT-2100 |
|
|
46 |
)))|((( |
|
|
47 |
Arista 7280R3, |
|
|
48 |
Juniper ACX7100-48L |
|
|
49 |
)))|Keysight IxNetwork |
|
|
50 |
|
|
|
51 |
Table 27: Liveness of SR Policy using Seamless BFD - S-BFD |
|
|
52 |
{{/container}} |
|
|
53 |
(% id="prev-next-links" %) |
|
|
54 |
|[[< Previous>>doc:SR-MPLS - SRTE Traffic Steering (per destination)]]|[[Next ~>>>doc:Optical Networks Using 400ZRZR+ -800ZRZR+ Optical Plugs]] |
|
|
55 |
))) |
|
|
56 |
|
|
|
57 |
(% class="col-xs-12 col-sm-5 test-report-sidebar" %) |
|
|
58 |
((( |
|
|
59 |
{{box}} |
|
|
60 |
{{include reference="Main.Multi-Vendor MPLS & SDN Interoperability Test Report 2025.Sidebar Nav"/}} |
|
|
61 |
{{/box}} |
|
|
62 |
))) |
|
|
63 |
))) |