|
|
1 |
(% class="row" %) |
|
|
2 |
((( |
|
|
3 |
(% class="col-xs-12 col-sm-7 test-report-content" %) |
|
|
4 |
((( |
|
|
5 |
---- |
|
|
6 |
|
|
|
7 |
RFC 7432 outlines six methods for generating an Ethernet Segment Identifier (ESI). We tested type 1 as specified in the RFC, which utilizes the LACP system MAC address and Port Key. This method allows us to automatically generate a unique ESI without the need for human configuration. |
|
|
8 |
In our testing, we confirmed that the ESI for the entire group remained consistent and that RT-4 was successfully propagated throughout the entire ES. No traffic is sent during the test. |
|
|
9 |
|
|
|
10 |
[[Figure 47: EVPN VXLAN ESI auto-config>>image:434504516545544193_1.65-vxlan.png||alt="Figure 47" width="550"]] |
|
|
11 |
|
|
|
12 |
(% id="prev-next-links" %) |
|
|
13 |
|[[< Previous>>doc:Label Switched Path (LSP) Ping Mechanisms for EVPN]]|[[Next ~>>>doc:Main.Multi-Vendor MPLS & SDN Interoperability Test Report 2025.Orchestration and Automation.WebHome]] |
|
|
14 |
))) |
|
|
15 |
|
|
|
16 |
(% class="col-xs-12 col-sm-5 test-report-sidebar" %) |
|
|
17 |
((( |
|
|
18 |
{{box}} |
|
|
19 |
{{include reference="Main.Multi-Vendor MPLS & SDN Interoperability Test Report 2025.Sidebar Nav"/}} |
|
|
20 |
{{/box}} |
|
|
21 |
))) |
|
|
22 |
))) |
