|
|
1 |
(% class="row" %) |
|
|
2 |
((( |
|
|
3 |
(% class="col-xs-12 col-sm-8 test-report-content" %) |
|
|
4 |
((( |
|
|
5 |
---- |
|
|
6 |
|
|
|
7 |
The SRv6 policy with Seamless BFD (S-BFD) was used to provide fast and deterministic failure detection for an explicitly defined SRv6 path. The main objective was to detect data-plane failures that are not visible to the control plane and to trigger immediate traffic protection without waiting for IGP or BGP convergence. |
|
|
8 |
|
|
|
9 |
Two SRv6 policies were configured toward the same endpoint: a primary path and a secondary path. Depending on vendor capabilities, S-BFD was either enabled only on the primary path or enabled on both primary and standby paths. |
|
|
10 |
|
|
|
11 |
To simulate failure of the active SRv6 path, S-BFD continuity was intentionally disrupted. When only the primary path was monitored with S-BFD, this was achieved by shutting down the S-BFD reflector on the peer device, which caused the head-end to stop receiving S-BFD replies. As a result, the S-BFD session expired and the primary segment list was declared invalid, triggering traffic switchover to the secondary SRv6 policy. |
|
|
12 |
|
|
|
13 |
When S-BFD was configured on both primary and standby paths, shutting down the reflector would have impacted both paths simultaneously. Therefore, a traffic filter was applied specifically on the primary path to block S-BFD control packets. This caused loss of continuity only on the active segment list, while the standby path remained operational. Upon S-BFD failure detection on the primary path, traffic was automatically redirected to the standby SRv6 policy. |
|
|
14 |
|
|
|
15 |
In both scenarios, S-BFD successfully detected data-plane failure and triggered correct and deterministic switchover behavior. |
|
|
16 |
|
|
|
17 |
[[~[~[Figure 86:SRv6 Policy with S-BFD~>~>image:486179564671533057_SRv6 Policy with S-BFD.png~|~|alt="Figure 86" width="550"~]~]>>attach:486179564671533057_SRv6 Policy with S-BFD.png||target="_blank"]] |
|
|
18 |
|
|
|
19 |
{{container cssClass="tc-role-table"}} |
|
|
20 |
(% class="table-bordered" %) |
|
|
21 |
|=Policy Headend and S-BFD Initiator|=Policy Tailend and S-BFD reflector|=Traffic Generator |
|
|
22 |
|Nokia 7750 SR-1|ZTE ZXR10 M6000-2S16|Keysight IxNetwork |
|
|
23 |
|((( |
|
|
24 |
ZTE ZXR10 M6000-2S16, |
|
|
25 |
ZTE ZXR10 M6000-3S Plus |
|
|
26 |
)))|((( |
|
|
27 |
HPE ACX7024, |
|
|
28 |
HPE MX204, |
|
|
29 |
Nokia 7750 SR-1 |
|
|
30 |
)))|Keysight IxNetwork |
|
|
31 |
|
|
|
32 |
Table 61: Static SRv6 policy with S-BFD - µSID |
|
|
33 |
{{/container}} |
|
|
34 |
|
|
|
35 |
(% id="prev-next-links" %) |
|
|
36 |
|[[< Previous>>doc:SRv6 Policies with Explicit Paths]]|[[Next ~>>>doc:Main.EANTC Transport & Cloud Networks Interop Test Report 2026.Time Synchronization.WebHome]] |
|
|
37 |
))) |
|
|
38 |
|
|
|
39 |
(% class="col-xs-12 col-sm-4 test-report-sidebar" %) |
|
|
40 |
((( |
|
|
41 |
{{box}} |
|
|
42 |
{{include reference="Main.EANTC Transport & Cloud Networks Interop Test Report 2026.Sidebar Nav"/}} |
|
|
43 |
{{/box}} |
|
|
44 |
))) |
|
|
45 |
))) |
