接續上個章節，此章節進行 LAB 實作，下圖為本實驗的架構
Spine 在 EVPN 實驗架構中扮演負責讓所有 Leaf 之間能夠交換路由資訊。核心配置
ASN：設定為 65199。在 eBGP 架構中，Spine 擁有獨立的 ASN，與 Leaf 區隔。
BGP Unnumbered
...
vrf:
default:
router:
bgp:
peer-group:
underlay:
remote-as: external # 代表使用 eBGP
EVPN 啟用：除了交換普通路由，還要幫忙傳遞 EVPN 的二層訊息
...
vrf:
default:
...
address-family:
...
l2vpn-evpn:
state: enabled
開啟與鄰居的 EVPN 對話。針對加入 underlay 這個群組的所有鄰居（即 swp1 到 swp4 這些 Leaf），跟他們討論 EVPN 的內容
vrf:
default:
router:
bgp:
peer-group:
underlay:
...
address-family:
l2vpn-evpn:
state: enabled
在 NVIDIA Cumulus Linux 的 NVUE 配置中，需要兩步驟來完成 EVPN 的部署。首先，我們在全域 BGP 下開啟 l2vpn-evpn，這相當於為交換器載入了 EVPN 的大腦；接著，我們在負責底層連線的 peer-group 中再次啟用它。這是一個關鍵動作，因為它正式授權交換器將複雜的 Type-1 到 Type-5 EVPN 路由，透過實體介面（swp1-swp4）傳遞給下游的 Leaf 交換器。
- set:
system:
hostname: spine01
interface:
lo:
ipv4:
address:
10.10.10.101/32: {}
swp1:
type: swp
swp2:
type: swp
swp3:
type: swp
swp4:
type: swp
router:
bgp:
autonomous-system: 65199
router-id: 10.10.10.101
vrf:
default:
router:
bgp:
peer-group:
underlay:
remote-as: external
address-family:
l2vpn-evpn:
state: enabled
neighbor:
swp1:
peer-group: underlay
swp2:
peer-group: underlay
swp3:
peer-group: underlay
swp4:
peer-group: underlay
address-family:
ipv4-unicast:
redistribute:
connected:
state: enabled
l2vpn-evpn:
state: enabled
- set:
system:
hostname: spine02
interface:
lo:
ipv4:
address:
10.10.10.102/32: {}
swp1:
type: swp
swp2:
type: swp
swp3:
type: swp
swp4:
type: swp
router:
bgp:
autonomous-system: 65199
router-id: 10.10.10.102
vrf:
default:
router:
bgp:
peer-group:
underlay:
remote-as: external
address-family:
l2vpn-evpn:
state: enabled
neighbor:
swp1:
peer-group: underlay
swp2:
peer-group: underlay
swp3:
peer-group: underlay
swp4:
peer-group: underlay
address-family:
ipv4-unicast:
redistribute:
connected:
state: enabled
l2vpn-evpn:
state: enabled
Leaf 是業務接入點，負責將物理 VLAN 映射到虛擬隧道 (VXLAN)，並處理伺服器的雙掛備援 (Multihoming)。
基礎建設層 (Underlay & BGP)
虛擬隧道層 (VXLAN & VNI)
L2 VNI (Layer 2): 10, 20, 30。
L3 VNI (Layer 3): 4001。
BLUE:
evpn:
vni:
'4002': {}
EVPN Multihoming
負責伺服器的雙掛備援與負載平衡。
ESI (Ethernet Segment Identifier): 03:44:38:39:ff:00:aa:00:00:01。
bond1:
bond:
member:
swp1: {}
lacp-bypass: enabled
evpn:
multihoming:
segment:
local-id: 1
mac-address: 44:38:39:FF:00:AA
df-preference: 50000
Redundancy Mode: all-active
服務與控制層 (BGP EVPN Address-Family)
路由重分佈 (Redistribute Connected)
...
address-family:
ipv4-unicast:
redistribute:
connected:
state: enabled
路由導出至 EVPN
BLUE:
...
router:
bgp:
...
route-export:
to-evpn: {}
- set:
system:
hostname: leaf01
bridge:
domain:
br_default:
vlan:
'10':
vni:
'10': {}
'20':
vni:
'20': {}
'30':
vni:
'30': {}
interface:
lo:
ipv4:
address:
10.10.10.1/32: {}
swp1:
type: swp
swp2:
type: swp
swp3:
type: swp
swp13:
type: swp
evpn:
multihoming:
uplink: enabled
swp14:
type: swp
evpn:
multihoming:
uplink: enabled
bond1:
bond:
member:
swp1: {}
lacp-bypass: enabled
evpn:
multihoming:
segment:
local-id: 1
mac-address: 44:38:39:FF:00:AA
df-preference: 50000
link:
mtu: 9000
bridge:
domain:
br_default:
access: 10
bond2:
bond:
member:
swp2: {}
lacp-bypass: enabled
evpn:
multihoming:
segment:
local-id: 2
mac-address: 44:38:39:FF:00:AA
df-preference: 50000
link:
mtu: 9000
bridge:
domain:
br_default:
access: 20
bond3:
bond:
member:
swp3: {}
lacp-bypass: enabled
evpn:
multihoming:
segment:
local-id: 3
mac-address: 44:38:39:FF:00:AA
df-preference: 50000
link:
mtu: 9000
bridge:
domain:
br_default:
access: 30
vlan10:
type: svi
vlan: 10
vrf: RED
ipv4:
address:
10.1.10.2/24: {}
vrr:
state: enabled
address:
10.1.10.1/24: {}
vlan20:
type: svi
vlan: 20
vrf: RED
ipv4:
address:
10.1.20.2/24: {}
vrr:
state: enabled
address:
10.1.20.1/24: {}
vlan30:
type: svi
vlan: 30
vrf: BLUE
ipv4:
address:
10.1.30.2/24: {}
vrr:
state: enabled
address:
10.1.30.1/24: {}
nve:
vxlan:
state: enabled
source:
address: 10.10.10.1
arp-nd-suppress: enabled
evpn:
state: enabled
multihoming:
state: enabled
router:
bgp:
autonomous-system: 65101
router-id: 10.10.10.1
vrf:
default:
router:
bgp:
peer-group:
underlay:
remote-as: external
address-family:
l2vpn-evpn:
state: enabled
neighbor:
swp13:
peer-group: underlay
swp14:
peer-group: underlay
address-family:
ipv4-unicast:
redistribute:
connected:
state: enabled
RED:
evpn:
vni:
'4001': {}
router:
bgp:
autonomous-system: 65101
router-id: 10.10.10.1
address-family:
ipv4-unicast:
redistribute:
connected:
state: enabled
route-export:
to-evpn: {}
BLUE:
evpn:
vni:
'4002': {}
router:
bgp:
autonomous-system: 65101
router-id: 10.10.10.1
address-family:
ipv4-unicast:
redistribute:
connected:
state: enabled
route-export:
to-evpn: {}
- set:
system:
hostname: leaf02
bridge:
domain:
br_default:
vlan:
'10':
vni:
'10': {}
'20':
vni:
'20': {}
'30':
vni:
'30': {}
interface:
lo:
ipv4:
address:
10.10.10.2/32: {}
swp1:
type: swp
swp2:
type: swp
swp3:
type: swp
swp13:
type: swp
evpn:
multihoming:
uplink: enabled
swp14:
type: swp
evpn:
multihoming:
uplink: enabled
bond1:
bond:
member:
swp1: {}
lacp-bypass: enabled
evpn:
multihoming:
segment:
local-id: 1
mac-address: 44:38:39:FF:00:AA
df-preference: 50000
link:
mtu: 9000
bridge:
domain:
br_default:
access: 10
bond2:
bond:
member:
swp2: {}
lacp-bypass: enabled
evpn:
multihoming:
segment:
local-id: 2
mac-address: 44:38:39:FF:00:AA
df-preference: 50000
link:
mtu: 9000
bridge:
domain:
br_default:
access: 20
bond3:
bond:
member:
swp3: {}
lacp-bypass: enabled
evpn:
multihoming:
segment:
local-id: 3
mac-address: 44:38:39:FF:00:AA
df-preference: 50000
link:
mtu: 9000
bridge:
domain:
br_default:
access: 30
vlan10:
type: svi
vlan: 10
vrf: RED
ipv4:
address:
10.1.10.3/24: {}
vrr:
state: enabled
address:
10.1.10.1/24: {}
vlan20:
type: svi
vlan: 20
vrf: RED
ipv4:
address:
10.1.20.3/24: {}
vrr:
state: enabled
address:
10.1.20.1/24: {}
vlan30:
type: svi
vlan: 30
vrf: BLUE
ipv4:
address:
10.1.30.3/24: {}
vrr:
state: enabled
address:
10.1.30.1/24: {}
nve:
vxlan:
state: enabled
source:
address: 10.10.10.2
arp-nd-suppress: enabled
evpn:
state: enabled
multihoming:
state: enabled
router:
bgp:
autonomous-system: 65102
router-id: 10.10.10.2
vrf:
default:
router:
bgp:
peer-group:
underlay:
remote-as: external
address-family:
l2vpn-evpn:
state: enabled
neighbor:
swp13:
peer-group: underlay
swp14:
peer-group: underlay
address-family:
ipv4-unicast:
redistribute:
connected:
state: enabled
RED:
evpn:
vni:
'4001': {}
router:
bgp:
autonomous-system: 65102
router-id: 10.10.10.2
address-family:
ipv4-unicast:
redistribute:
connected:
state: enabled
route-export:
to-evpn: {}
BLUE:
evpn:
vni:
'4002': {}
router:
bgp:
autonomous-system: 65102
router-id: 10.10.10.2
address-family:
ipv4-unicast:
redistribute:
connected:
state: enabled
route-export:
to-evpn: {}
- set:
system:
hostname: leaf03
bridge:
domain:
br_default:
vlan:
'10':
vni:
'10': {}
'20':
vni:
'20': {}
'30':
vni:
'30': {}
interface:
lo:
ipv4:
address:
10.10.10.3/32: {}
swp1:
type: swp
swp2:
type: swp
swp3:
type: swp
swp13:
type: swp
evpn:
multihoming:
uplink: enabled
swp14:
type: swp
evpn:
multihoming:
uplink: enabled
bond1:
bond:
member:
swp1: {}
lacp-bypass: enabled
evpn:
multihoming:
segment:
local-id: 1
mac-address: 44:38:39:FF:00:BB
df-preference: 50000
link:
mtu: 9000
bridge:
domain:
br_default:
access: 10
bond2:
bond:
member:
swp2: {}
lacp-bypass: enabled
evpn:
multihoming:
segment:
local-id: 2
mac-address: 44:38:39:FF:00:BB
df-preference: 50000
link:
mtu: 9000
bridge:
domain:
br_default:
access: 20
bond3:
bond:
member:
swp3: {}
lacp-bypass: enabled
evpn:
multihoming:
segment:
local-id: 3
mac-address: 44:38:39:FF:00:BB
df-preference: 50000
link:
mtu: 9000
bridge:
domain:
br_default:
access: 30
vlan10:
type: svi
vlan: 10
vrf: RED
ipv4:
address:
10.1.10.4/24: {}
vrr:
state: enabled
address:
10.1.10.1/24: {}
vlan20:
type: svi
vlan: 20
vrf: RED
ipv4:
address:
10.1.20.4/24: {}
vrr:
state: enabled
address:
10.1.20.1/24: {}
vlan30:
type: svi
vlan: 30
vrf: BLUE
ipv4:
address:
10.1.30.4/24: {}
vrr:
state: enabled
address:
10.1.30.1/24: {}
nve:
vxlan:
state: enabled
source:
address: 10.10.10.3
arp-nd-suppress: enabled
evpn:
state: enabled
multihoming:
state: enabled
router:
bgp:
autonomous-system: 65103
router-id: 10.10.10.3
vrf:
default:
router:
bgp:
peer-group:
underlay:
remote-as: external
address-family:
l2vpn-evpn:
state: enabled
neighbor:
swp13:
peer-group: underlay
swp14:
peer-group: underlay
address-family:
ipv4-unicast:
redistribute:
connected:
state: enabled
RED:
evpn:
vni:
'4001': {}
router:
bgp:
autonomous-system: 65103
router-id: 10.10.10.3
address-family:
ipv4-unicast:
redistribute:
connected:
state: enabled
route-export:
to-evpn: {}
BLUE:
evpn:
vni:
'4002': {}
router:
bgp:
autonomous-system: 65103
router-id: 10.10.10.3
address-family:
ipv4-unicast:
redistribute:
connected:
state: enabled
route-export:
to-evpn: {}
- set:
system:
hostname: leaf04
bridge:
domain:
br_default:
vlan:
'10':
vni:
'10': {}
'20':
vni:
'20': {}
'30':
vni:
'30': {}
interface:
lo:
ipv4:
address:
10.10.10.4/32: {}
swp1:
type: swp
swp2:
type: swp
swp3:
type: swp
swp13:
type: swp
evpn:
multihoming:
uplink: enabled
swp14:
type: swp
evpn:
multihoming:
uplink: enabled
bond1:
bond:
member:
swp1: {}
lacp-bypass: enabled
evpn:
multihoming:
segment:
local-id: 1
mac-address: 44:38:39:FF:00:BB
df-preference: 50000
link:
mtu: 9000
bridge:
domain:
br_default:
access: 10
bond2:
bond:
member:
swp2: {}
lacp-bypass: enabled
evpn:
multihoming:
segment:
local-id: 2
mac-address: 44:38:39:FF:00:BB
df-preference: 50000
link:
mtu: 9000
bridge:
domain:
br_default:
access: 20
bond3:
bond:
member:
swp3: {}
lacp-bypass: enabled
evpn:
multihoming:
segment:
local-id: 3
mac-address: 44:38:39:FF:00:BB
df-preference: 50000
link:
mtu: 9000
bridge:
domain:
br_default:
access: 30
vlan10:
type: svi
vlan: 10
vrf: RED
ipv4:
address:
10.1.10.5/24: {}
vrr:
state: enabled
address:
10.1.10.1/24: {}
vlan20:
type: svi
vlan: 20
vrf: RED
ipv4:
address:
10.1.20.5/24: {}
vrr:
state: enabled
address:
10.1.20.1/24: {}
vlan30:
type: svi
vlan: 30
vrf: BLUE
ipv4:
address:
10.1.30.5/24: {}
vrr:
state: enabled
address:
10.1.30.1/24: {}
nve:
vxlan:
state: enabled
source:
address: 10.10.10.4
arp-nd-suppress: enabled
evpn:
state: enabled
multihoming:
state: enabled
router:
bgp:
autonomous-system: 65104
router-id: 10.10.10.4
vrf:
default:
router:
bgp:
peer-group:
underlay:
remote-as: external
address-family:
l2vpn-evpn:
state: enabled
neighbor:
swp13:
peer-group: underlay
swp14:
peer-group: underlay
address-family:
ipv4-unicast:
redistribute:
connected:
state: enabled
RED:
evpn:
vni:
'4001': {}
router:
bgp:
autonomous-system: 65104
router-id: 10.10.10.4
address-family:
ipv4-unicast:
redistribute:
connected:
state: enabled
route-export:
to-evpn: {}
BLUE:
evpn:
vni:
'4002': {}
router:
bgp:
autonomous-system: 65104
router-id: 10.10.10.4
address-family:
ipv4-unicast:
redistribute:
connected:
state: enabled
route-export:
to-evpn: {}
network:
version: 2
ethernets:
enp2s0: {}
enp2s1: {}
bonds:
bond0:
interfaces:
- enp2s0
- enp2s1
addresses:
- 10.1.10.101/24
parameters:
mode: 802.3ad
mii-monitor-interval: 100
lacp-rate: fast
transmit-hash-policy: layer3+4
routes:
- to: default
via: 10.1.10.1
network:
version: 2
ethernets:
enp2s0: {}
enp2s1: {}
bonds:
bond0:
interfaces:
- enp2s0
- enp2s1
addresses:
- 10.1.20.102/24
parameters:
mode: 802.3ad
mii-monitor-interval: 100
lacp-rate: fast
transmit-hash-policy: layer3+4
routes:
- to: default
via: 10.1.20.1
network:
version: 2
ethernets:
enp2s0: {}
enp2s1: {}
bonds:
bond0:
interfaces:
- enp2s0
- enp2s1
addresses:
- 10.1.30.103/24
parameters:
mode: 802.3ad
mii-monitor-interval: 100
lacp-rate: fast
transmit-hash-policy: layer3+4
routes:
- to: default
via: 10.1.30.1
network:
version: 2
ethernets:
enp2s0: {}
enp2s1: {}
bonds:
bond0:
interfaces:
- enp2s0
- enp2s1
addresses:
- 10.1.10.104/24
parameters:
mode: 802.3ad
mii-monitor-interval: 100
lacp-rate: fast
transmit-hash-policy: layer3+4
routes:
- to: default
via: 10.1.10.1
network:
version: 2
ethernets:
enp2s0: {}
enp2s1: {}
bonds:
bond0:
interfaces:
- enp2s0
- enp2s1
addresses:
- 10.1.20.105/24
parameters:
mode: 802.3ad
mii-monitor-interval: 100
lacp-rate: fast
transmit-hash-policy: layer3+4
routes:
- to: default
via: 10.1.20.1
network:
version: 2
ethernets:
enp2s0: {}
enp2s1: {}
bonds:
bond0:
interfaces:
- enp2s0
- enp2s1
addresses:
- 10.1.30.106/24
parameters:
mode: 802.3ad
mii-monitor-interval: 100
lacp-rate: fast
transmit-hash-policy: layer3+4
routes:
- to: default
via: 10.1.30.1
驗證全域 EVPN-MH 狀態與 Uplink 追蹤 (Global State & Uplink Tracking)
必須確認交換器已正確啟用 EVPN-MH，並且系統有正確監控到 Uplink 介面。在 EVPN-MH 架構中，當所有 Uplink 斷線時，交換器會自動將連接伺服器的 Ethernet Segment (ES) Bond 介面設為 protodown 或 error-disabled 狀態，以防止流量黑洞。
cumulus@leaf01:mgmt:~$ nv show evpn multihoming
operational applied
------------------- ----------- -------
state enabled
mac-holdtime 1080 1080
neighbor-holdtime 1080 1080
startup-delay 180 180
ead-evi-route
rx enabled
tx enabled
segment
df-preference 32767
startup-delay-timer --:--:--
uplink-count 2
uplink-active 2
此指令會顯示全域的 EVPN-MH 狀態，包含 mac-holdtime、neighbor-holdtime、startup-delay 等計時器，以及當前活躍的 Uplink 數量 (uplink-active) 與總數 (uplink-count)。確認 state 為 enabled，且 uplink-active 數量符合實體接線預期，在拓撲中應顯示為 2（代表去往 Spine01/02 的路徑正常）。
檢查乙太網路網段 (Ethernet Segment) 狀態
確認各個連接伺服器的 Bond 介面是否已經成功生成 Ethernet Segment ID (ESI)，以及其 Designated Forwarder (DF) 優先級是否正確。
cumulus@leaf01:mgmt:~$ nv show evpn multihoming esi
ESInterface - Local interface, NHG - Nexthop group ID, DFPref - Designated
forwarder preference, VNICnt - ESI EVPN instances, MacCnt - Mac entries using
this ES as destination, RemoteVTEPs - Remote tunnel Endpoint, Flags - * - ready-
for_bgp, s - oper-up, x - non-designated-forward, r - remote, l - local, f -
designated-forward, b - bridge-port, A - active
ESI ESInterface NHG DFPref VNICnt MacCnt RemoteVTEPs Flags
----------------------------- ----------- --------- ------ ------ ------ ----------- -------
03:44:38:39:ff:00:aa:00:00:01 bond1 536870913 50000 1 1 10.10.10.2 lrf*bsA
03:44:38:39:ff:00:aa:00:00:02 bond2 536870914 50000 1 1 10.10.10.2 lrf*bsA
03:44:38:39:ff:00:aa:00:00:03 bond3 536870915 50000 1 1 10.10.10.2 lrf*bsA
03:44:38:39:ff:00:bb:00:00:01 536870917 0 0 1 10.10.10.3 rA
10.10.10.4
03:44:38:39:ff:00:bb:00:00:02 536870920 0 0 1 10.10.10.3 rA
10.10.10.4
03:44:38:39:ff:00:bb:00:00:03 536870921 0 0 1 10.10.10.3 rA
10.10.10.4
這個指令極為重要，它會列出所有的 ESI 以及其關聯的本地介面 (Local interface)、DF 優先級 (DFPref)、MAC 數量 (MacCnt)，以及遠端 VTEP 的 IP 位址。其 Flags 中帶有 local (代表本地直連) 與 remote (代表成功從對等交換器學習到)等值。
詳細來看:
核心欄位解析
| 參數名稱 | 解析與說明 |
|---|
| ESI | 乙太網路網段識別碼。由您配置的 mac-address (44:38:39:FF:00:AA/BB) 與 local-id (1, 2, 3) 自動生成。 |
| ESInterface | 本地綁定介面。顯示該 ESI 在本地對應的 bond 介面。若為空值，代表該 ESI 是從遠端（其他 Rack）學習過來的。 |
| NHG | 下跳群組識別碼 (Nexthop Group ID)。系統內部用於硬體轉發流量的唯一編號。 |
| DFPref | DF 選舉權重 (Preference)。配置的數值為 50000。數值越高，越優先成為該網段的指定轉發者 (DF)。 |
| VNICnt | VNI 數量。該 ESI 目前關聯的 EVPN 實例數量（例如 VLAN 10 在此顯示為 1）。 |
| MacCnt | MAC 位址數量。目前在該 ESI 後端學習到的終端設備 MAC 數量。 |
| RemoteVTEPs | 遠端對等節點。共享同一個 ESI 的鄰居交換器 Loopback IP。 |
| Flags | 狀態標籤。反映該網段的運行協議狀態。 |
狀態標籤 (Flags) 深度解析
輸出中出現了兩組主要的 Flags，分別代表「本地網段」與「遠端網段」：
A. 本地網段狀態：lrf*bsA (以 ESI ...aa...01 為例)
這代表 leaf01 物理連接了此設備，且目前正負責轉發。
bond1）。10.10.10.2 (leaf02) 也宣告了同一個 ESI。leaf01 目前在該網段被選為 DF (主)，負責轉發 BUM 流量。B. 遠端網段狀態：rA (以 ESI ...bb...01 為例)
這代表該設備連接在 leaf03 與 leaf04 的機櫃下。
leaf01 知道該網段由 10.10.10.3 與 10.10.10.4 共同服務。拓撲運行現狀總結
根據輸出結果，目前的運行邏輯如下：
leaf01 與 leaf02 成功形成了 ES 群組。bond1, bond2, bond3，leaf01 目前都擔任 DF (f 標籤)，代表它在這些網段是主導地位。leaf01 已經正確看見了位於另一端機櫃的 Server4, Server5, Server6 所屬的 ESI (...bb...)。10.10.10.3 與 10.10.10.4 這兩個 VTEP，這意味著當 leaf01 往這些伺服器傳送流量時，可以實現 ECMP (等價多路徑) 負載平衡。若發現特定 ES 異常，可針對單一 ESI 進行深入檢視其旗標 (如 bridge-port on, designated-forward on) 以及遠端 VTEP 的狀態。
$ nv show evpn multihoming esi 03:44:38:39:ff:00:aa:00:00:02
operational
---------------------- -----------
local-interface bond2
df-preference 50000
mac-count 1
vni-count 1
nexthop-group-id 536870914
flags-string lrf*bsA
flags
local on
remote on
ready-for-bgp on
bridge-port on
oper-up on
nexthop-group-active on
designated-forward on
remote-vtep
==============
DFAlgo - Designated forwarder election algorithm, DFPref - Designated forwarder
preference, NHG - Remote VTEP Nexthop group ID
VTEP DFAlgo DFPref NHG
---------- ---------- ------ ---------
10.10.10.2 preference 50000 268435460
透過 BGP 控制平面驗證 Type-1 與 Type-4 路由 (BGP Control Plane)
EVPN-MH 的核心是透過 BGP 交換路由資訊。Type-4 (Ethernet Segment Route) 用於自動發現共享同一個 ES 的 VTEP 並進行 DF 選舉；Type-1 (Ethernet Auto-Discovery, EAD) 則用於流量的快速容錯移轉 (Fast Failover) 與別名 (Aliasing)。
驗證 Type-4 (ES 發現與 DF 選舉)
cumulus@leaf01:mgmt:~$ sudo vtysh -c "show bgp l2vpn evpn es"
ES Flags: B - bypass, L local, R remote, I inconsistent
VTEP Flags: E ESR/Type-4, A active nexthop
ESI Flags RD #VNIs VTEPs
03:44:38:39:ff:00:aa:00:00:01 LR 10.10.10.1:5 1 10.10.10.2(EA)
03:44:38:39:ff:00:aa:00:00:02 LR 10.10.10.1:6 1 10.10.10.2(EA)
03:44:38:39:ff:00:aa:00:00:03 LR 10.10.10.1:7 1 10.10.10.2(EA)
03:44:38:39:ff:00:bb:00:00:01 R (null) 1 10.10.10.3(A),10.10.10.4(A)
03:44:38:39:ff:00:bb:00:00:02 R (null) 1 10.10.10.3(A),10.10.10.4(A)
03:44:38:39:ff:00:bb:00:00:03 R (null) 1 10.10.10.3(A),10.10.10.4(A)
cumulus@leaf01:mgmt:~$ nv show evpn multihoming bgp-info esi
SrcIP - Originator IP, VNICnt - VNI Count, VRFCnt - VRF Count, MACIPCnt - MAC IP
path count, MacGlblCnt - Mac global count, VTEP - Remote VTEP ID, FragID -
Fragments ID, Flags - u - up, a - advertise-evi, VtepFlags - e - esr, A - active
ESI RD SrcIP VNICnt VRFCnt MACIPCnt MacGlblCnt Local Remote VTEP FragID Flags VtepFlags
----------------------------- ------------ ---------- ------ ------ -------- ---------- ----- ------ ---------- ------------ ----- ---------
03:44:38:39:ff:00:aa:00:00:01 10.10.10.1:5 10.10.10.1 1 1 2 4 yes yes 10.10.10.2 10.10.10.1:5 ua eA
03:44:38:39:ff:00:aa:00:00:02 10.10.10.1:6 10.10.10.1 1 1 2 4 yes yes 10.10.10.2 10.10.10.1:6 ua eA
03:44:38:39:ff:00:aa:00:00:03 10.10.10.1:7 10.10.10.1 1 1 2 4 yes yes 10.10.10.2 10.10.10.1:7 ua eA
03:44:38:39:ff:00:bb:00:00:01 (null) 1 1 0 8 yes 10.10.10.3 A
10.10.10.4 A
03:44:38:39:ff:00:bb:00:00:02 (null) 1 1 0 8 yes 10.10.10.3 A
10.10.10.4 A
03:44:38:39:ff:00:bb:00:00:03 (null) 1 1 0 8 yes 10.10.10.3 A
10.10.10.4 A
此輸出會顯示從 BGP Type-1 與 Type-4 路由中學習到的 ES 資訊。必須確認本地與遠端 VTEP 皆正確顯示於該 ESI 的路由表內。
驗證 Type-1 (EAD 路由，用於多重路徑 (multihomed) 端點的資料中心)
此指令會列出所有 BGP 表內的 Type-1 路由。若伺服器端的 Bond 發生故障，VTEP 會發送單一的 EAD-ES withdrawal 訊息來通知所有其他 VTEP，從而觸發快速容錯移轉。
cumulus@leaf01:mgmt:~$ sudo vtysh -c "show bgp l2vpn evpn route type ead"
BGP table version is 14, local router ID is 10.10.10.1
Status codes: s suppressed, d damped, h history, * valid, > best, i - internal
Origin codes: i - IGP, e - EGP, ? - incomplete
EVPN type-1 prefix: [1]:[EthTag]:[ESI]:[IPlen]:[VTEP-IP]:[Frag-id]
EVPN type-2 prefix: [2]:[EthTag]:[MAClen]:[MAC]:[IPlen]:[IP]
EVPN type-3 prefix: [3]:[EthTag]:[IPlen]:[OrigIP]
EVPN type-4 prefix: [4]:[ESI]:[IPlen]:[OrigIP]
EVPN type-5 prefix: [5]:[EthTag]:[IPlen]:[IP]
Network Next Hop Metric LocPrf Weight Path
Extended Community
Route Distinguisher: 10.10.10.1:4
*> [1]:[0]:[03:44:38:39:ff:00:aa:00:00:02]:[128]:[::]:[0] RD 10.10.10.1:4
10.10.10.1 (leaf01)
32768 i
ET:8 RT:65101:20
Route Distinguisher: 10.10.10.1:5
*> [1]:[4294967295]:[03:44:38:39:ff:00:aa:00:00:01]:[128]:[::]:[0] RD 10.10.10.1:5
10.10.10.1 (leaf01)
32768 i
ET:8 ESI-label-Rt:AA RT:65101:10
Route Distinguisher: 10.10.10.1:6
*> [1]:[4294967295]:[03:44:38:39:ff:00:aa:00:00:02]:[128]:[::]:[0] RD 10.10.10.1:6
10.10.10.1 (leaf01)
32768 i
ET:8 ESI-label-Rt:AA RT:65101:20
Route Distinguisher: 10.10.10.1:7
*> [1]:[4294967295]:[03:44:38:39:ff:00:aa:00:00:03]:[128]:[::]:[0] RD 10.10.10.1:7
10.10.10.1 (leaf01)
32768 i
ET:8 ESI-label-Rt:AA RT:65101:30
Route Distinguisher: 10.10.10.1:8
*> [1]:[0]:[03:44:38:39:ff:00:aa:00:00:03]:[128]:[::]:[0] RD 10.10.10.1:8
10.10.10.1 (leaf01)
32768 i
ET:8 RT:65101:30
Route Distinguisher: 10.10.10.1:9
*> [1]:[0]:[03:44:38:39:ff:00:aa:00:00:01]:[128]:[::]:[0] RD 10.10.10.1:9
10.10.10.1 (leaf01)
32768 i
ET:8 RT:65101:10
Route Distinguisher: 10.10.10.2:2
*> [1]:[0]:[03:44:38:39:ff:00:aa:00:00:02]:[32]:[0.0.0.0]:[0] RD 10.10.10.2:2
10.10.10.2 (spine02)
0 65199 65102 i
RT:65102:20 ET:8
* [1]:[0]:[03:44:38:39:ff:00:aa:00:00:02]:[32]:[0.0.0.0]:[0] RD 10.10.10.2:2
10.10.10.2 (spine01)
0 65199 65102 i
RT:65102:20 ET:8
Route Distinguisher: 10.10.10.2:3
*> [1]:[4294967295]:[03:44:38:39:ff:00:aa:00:00:01]:[32]:[0.0.0.0]:[0] RD 10.10.10.2:3
10.10.10.2 (spine01)
0 65199 65102 i
RT:65102:10 ET:8 ESI-label-Rt:AA
* [1]:[4294967295]:[03:44:38:39:ff:00:aa:00:00:01]:[32]:[0.0.0.0]:[0] RD 10.10.10.2:3
10.10.10.2 (spine02)
0 65199 65102 i
RT:65102:10 ET:8 ESI-label-Rt:AA
Route Distinguisher: 10.10.10.2:4
*> [1]:[4294967295]:[03:44:38:39:ff:00:aa:00:00:02]:[32]:[0.0.0.0]:[0] RD 10.10.10.2:4
10.10.10.2 (spine01)
0 65199 65102 i
RT:65102:20 ET:8 ESI-label-Rt:AA
* [1]:[4294967295]:[03:44:38:39:ff:00:aa:00:00:02]:[32]:[0.0.0.0]:[0] RD 10.10.10.2:4
10.10.10.2 (spine02)
0 65199 65102 i
RT:65102:20 ET:8 ESI-label-Rt:AA
Route Distinguisher: 10.10.10.2:5
*> [1]:[4294967295]:[03:44:38:39:ff:00:aa:00:00:03]:[32]:[0.0.0.0]:[0] RD 10.10.10.2:5
10.10.10.2 (spine01)
0 65199 65102 i
RT:65102:30 ET:8 ESI-label-Rt:AA
* [1]:[4294967295]:[03:44:38:39:ff:00:aa:00:00:03]:[32]:[0.0.0.0]:[0] RD 10.10.10.2:5
10.10.10.2 (spine02)
0 65199 65102 i
RT:65102:30 ET:8 ESI-label-Rt:AA
Route Distinguisher: 10.10.10.2:8
*> [1]:[0]:[03:44:38:39:ff:00:aa:00:00:03]:[32]:[0.0.0.0]:[0] RD 10.10.10.2:8
10.10.10.2 (spine02)
0 65199 65102 i
RT:65102:30 ET:8
* [1]:[0]:[03:44:38:39:ff:00:aa:00:00:03]:[32]:[0.0.0.0]:[0] RD 10.10.10.2:8
10.10.10.2 (spine01)
0 65199 65102 i
RT:65102:30 ET:8
Route Distinguisher: 10.10.10.2:9
*> [1]:[0]:[03:44:38:39:ff:00:aa:00:00:01]:[32]:[0.0.0.0]:[0] RD 10.10.10.2:9
10.10.10.2 (spine02)
0 65199 65102 i
RT:65102:10 ET:8
* [1]:[0]:[03:44:38:39:ff:00:aa:00:00:01]:[32]:[0.0.0.0]:[0] RD 10.10.10.2:9
10.10.10.2 (spine01)
0 65199 65102 i
RT:65102:10 ET:8
Route Distinguisher: 10.10.10.3:2
*> [1]:[0]:[03:44:38:39:ff:00:bb:00:00:02]:[32]:[0.0.0.0]:[0] RD 10.10.10.3:2
10.10.10.3 (spine02)
0 65199 65103 i
RT:65103:20 ET:8
* [1]:[0]:[03:44:38:39:ff:00:bb:00:00:02]:[32]:[0.0.0.0]:[0] RD 10.10.10.3:2
10.10.10.3 (spine01)
0 65199 65103 i
RT:65103:20 ET:8
Route Distinguisher: 10.10.10.3:3
*> [1]:[4294967295]:[03:44:38:39:ff:00:bb:00:00:01]:[32]:[0.0.0.0]:[0] RD 10.10.10.3:3
10.10.10.3 (spine01)
0 65199 65103 i
RT:65103:10 ET:8 ESI-label-Rt:AA
* [1]:[4294967295]:[03:44:38:39:ff:00:bb:00:00:01]:[32]:[0.0.0.0]:[0] RD 10.10.10.3:3
10.10.10.3 (spine02)
0 65199 65103 i
RT:65103:10 ET:8 ESI-label-Rt:AA
Route Distinguisher: 10.10.10.3:4
*> [1]:[4294967295]:[03:44:38:39:ff:00:bb:00:00:02]:[32]:[0.0.0.0]:[0] RD 10.10.10.3:4
10.10.10.3 (spine01)
0 65199 65103 i
RT:65103:20 ET:8 ESI-label-Rt:AA
* [1]:[4294967295]:[03:44:38:39:ff:00:bb:00:00:02]:[32]:[0.0.0.0]:[0] RD 10.10.10.3:4
10.10.10.3 (spine02)
0 65199 65103 i
RT:65103:20 ET:8 ESI-label-Rt:AA
Route Distinguisher: 10.10.10.3:5
*> [1]:[4294967295]:[03:44:38:39:ff:00:bb:00:00:03]:[32]:[0.0.0.0]:[0] RD 10.10.10.3:5
10.10.10.3 (spine01)
0 65199 65103 i
RT:65103:30 ET:8 ESI-label-Rt:AA
* [1]:[4294967295]:[03:44:38:39:ff:00:bb:00:00:03]:[32]:[0.0.0.0]:[0] RD 10.10.10.3:5
10.10.10.3 (spine02)
0 65199 65103 i
RT:65103:30 ET:8 ESI-label-Rt:AA
Route Distinguisher: 10.10.10.3:8
*> [1]:[0]:[03:44:38:39:ff:00:bb:00:00:03]:[32]:[0.0.0.0]:[0] RD 10.10.10.3:8
10.10.10.3 (spine02)
0 65199 65103 i
RT:65103:30 ET:8
* [1]:[0]:[03:44:38:39:ff:00:bb:00:00:03]:[32]:[0.0.0.0]:[0] RD 10.10.10.3:8
10.10.10.3 (spine01)
0 65199 65103 i
RT:65103:30 ET:8
Route Distinguisher: 10.10.10.3:9
*> [1]:[0]:[03:44:38:39:ff:00:bb:00:00:01]:[32]:[0.0.0.0]:[0] RD 10.10.10.3:9
10.10.10.3 (spine02)
0 65199 65103 i
RT:65103:10 ET:8
* [1]:[0]:[03:44:38:39:ff:00:bb:00:00:01]:[32]:[0.0.0.0]:[0] RD 10.10.10.3:9
10.10.10.3 (spine01)
0 65199 65103 i
RT:65103:10 ET:8
Route Distinguisher: 10.10.10.4:2
*> [1]:[0]:[03:44:38:39:ff:00:bb:00:00:02]:[32]:[0.0.0.0]:[0] RD 10.10.10.4:2
10.10.10.4 (spine02)
0 65199 65104 i
RT:65104:20 ET:8
* [1]:[0]:[03:44:38:39:ff:00:bb:00:00:02]:[32]:[0.0.0.0]:[0] RD 10.10.10.4:2
10.10.10.4 (spine01)
0 65199 65104 i
RT:65104:20 ET:8
Route Distinguisher: 10.10.10.4:3
*> [1]:[0]:[03:44:38:39:ff:00:bb:00:00:03]:[32]:[0.0.0.0]:[0] RD 10.10.10.4:3
10.10.10.4 (spine02)
0 65199 65104 i
RT:65104:30 ET:8
* [1]:[0]:[03:44:38:39:ff:00:bb:00:00:03]:[32]:[0.0.0.0]:[0] RD 10.10.10.4:3
10.10.10.4 (spine01)
0 65199 65104 i
RT:65104:30 ET:8
Route Distinguisher: 10.10.10.4:4
*> [1]:[0]:[03:44:38:39:ff:00:bb:00:00:01]:[32]:[0.0.0.0]:[0] RD 10.10.10.4:4
10.10.10.4 (spine02)
0 65199 65104 i
RT:65104:10 ET:8
* [1]:[0]:[03:44:38:39:ff:00:bb:00:00:01]:[32]:[0.0.0.0]:[0] RD 10.10.10.4:4
10.10.10.4 (spine01)
0 65199 65104 i
RT:65104:10 ET:8
Route Distinguisher: 10.10.10.4:9
*> [1]:[4294967295]:[03:44:38:39:ff:00:bb:00:00:01]:[32]:[0.0.0.0]:[0] RD 10.10.10.4:9
10.10.10.4 (spine01)
0 65199 65104 i
RT:65104:10 ET:8 ESI-label-Rt:AA
* [1]:[4294967295]:[03:44:38:39:ff:00:bb:00:00:01]:[32]:[0.0.0.0]:[0] RD 10.10.10.4:9
10.10.10.4 (spine02)
0 65199 65104 i
RT:65104:10 ET:8 ESI-label-Rt:AA
Route Distinguisher: 10.10.10.4:10
*> [1]:[4294967295]:[03:44:38:39:ff:00:bb:00:00:02]:[32]:[0.0.0.0]:[0] RD 10.10.10.4:10
10.10.10.4 (spine01)
0 65199 65104 i
RT:65104:20 ET:8 ESI-label-Rt:AA
* [1]:[4294967295]:[03:44:38:39:ff:00:bb:00:00:02]:[32]:[0.0.0.0]:[0] RD 10.10.10.4:10
10.10.10.4 (spine02)
0 65199 65104 i
RT:65104:20 ET:8 ESI-label-Rt:AA
Route Distinguisher: 10.10.10.4:11
*> [1]:[4294967295]:[03:44:38:39:ff:00:bb:00:00:03]:[32]:[0.0.0.0]:[0] RD 10.10.10.4:11
10.10.10.4 (spine01)
0 65199 65104 i
RT:65104:30 ET:8 ESI-label-Rt:AA
* [1]:[4294967295]:[03:44:38:39:ff:00:bb:00:00:03]:[32]:[0.0.0.0]:[0] RD 10.10.10.4:11
10.10.10.4 (spine02)
0 65199 65104 i
RT:65104:30 ET:8 ESI-label-Rt:AA
Displayed 24 prefixes (42 paths) (of requested type)
我們可以用以下方式拆解並理解上述輸出：
什麼是 Type-1 (EAD) 路由？
在 EVPN Multihoming 架構中，Type-1 路由不負責告訴別人主機在哪裡（那是 Type-2 的工作），它負責的是：
欄位 [1]:[EthTag]:[ESI] 解析
4294967295 (即 0xFFFFFFFF)：這叫 EAD-per-ES 路由。它不針對特定 VLAN，而是針對整個物理網段發布的。它的目的是「快速收斂」。0：這叫 EAD-per-EVI 路由。它是針對特定 VNI 發布的，目的是實現負載平衡 (Aliasing)。[ESI]：這是配置的乙太網路網段識別碼。
驗證 VNI 層級的 ES 映射與連線 (Per-VNI ES Mapping)
我們必須確保這些 Ethernet Segments 有正確對應到覆疊網路 (Overlay) 中的 L2 VNI 上。
檢視各 VNI 的 ES 映射
這會顯示特定的 VNI 下綁定了哪些 ESI，以及它們是本地 (Local, L) 還是遠端 (Remote, R) 學習到的。
cumulus@leaf01:mgmt:~$ nv show evpn vni 10 multihoming esi
Local - ESI type configured as local, Remote - ESI type configured as remote
ESI Local Remote
----------------------------- ----- ------
03:44:38:39:ff:00:aa:00:00:01 yes
cumulus@leaf01:mgmt:~$ nv show evpn vni 20 multihoming esi
Local - ESI type configured as local, Remote - ESI type configured as remote
ESI Local Remote
----------------------------- ----- ------
03:44:38:39:ff:00:aa:00:00:02 yes
cumulus@leaf01:mgmt:~$ nv show evpn vni 30 multihoming esi
Local - ESI type configured as local, Remote - ESI type configured as remote
ESI Local Remote
----------------------------- ----- ------
03:44:38:39:ff:00:aa:00:00:03 yes
檢視 BGP 層級的 VNI 映射
此指令能進一步確認 BGP 針對每個 VNI 所宣告的 ES 狀態，包含是否具備 EAD-per-ES (E) 或 EAD-per-EVI (V) 的能力旗標。
cumulus@leaf01:mgmt:~$ sudo vtysh -c "show bgp l2vpn evpn es-evi"
Flags: L local, R remote, I inconsistent
VTEP-Flags: E EAD-per-ES, V EAD-per-EVI
VNI ESI Flags VTEPs
20 03:44:38:39:ff:00:aa:00:00:02 LR 10.10.10.2(EV)
20 03:44:38:39:ff:00:bb:00:00:02 R 10.10.10.3(EV),10.10.10.4(EV)
30 03:44:38:39:ff:00:aa:00:00:03 LR 10.10.10.2(EV)
30 03:44:38:39:ff:00:bb:00:00:03 R 10.10.10.3(EV),10.10.10.4(EV)
10 03:44:38:39:ff:00:aa:00:00:01 LR 10.10.10.2(EV)
10 03:44:38:39:ff:00:bb:00:00:01 R 10.10.10.3(EV),10.10.10.4(EV)
解讀資料內容:
本地機櫃狀態 (ESI 末兩碼為 aa) 10 03:44:38:39:ff:00:aa:00:00:01 LR 10.10.10.2(EV)
遠端機櫃狀態 (ESI 末兩碼為 bb) 10 03:44:38:39:ff:00:bb:00:00:01 R 10.10.10.3(EV),10.10.10.4(EV)
另外 EAD-per-ES 與 VAD-per-EVI 分別代表什麼意思 ?
在 EVPN Multihoming (EVPN-MH) 的標準中，這兩者都屬於 BGP EVPN Route Type-1 (Ethernet Auto-Discovery Route)，但它們負責解決的問題完全不同。簡單來說，EAD-per-ES負責速度（故障收斂），而EAD-per-EVI負責效率（負載平衡）。
EAD-per-ES (Ethernet Auto-Discovery per Ethernet Segment)
這是針對整個乙太網路網段發佈的路由。當交換器（Leaf）偵測到本地的 ESI（如 bond1）處於 Up 狀態時，它會發送一條針對該 ESI 的路由，其 Ethernet Tag ID 設為一個特殊值（通常是 MAX-ET）。
EAD-per-EVI (Ethernet Auto-Discovery per EVPN Instance)
這是針對特定*EVPN 實例（即 VNI/VLAN）*發佈的路由。交換器會為該 ESI 所屬的每一個 VNI 分別發送路由。例如 ESI-aa-01 同時屬於 VNI 10, 20, 30，就會有三條對應的 EAD-per-EVI 路由。
接入層 LACP 與 ESI 驗證
目標: 確認伺服器是否將兩台 Leaf 視為同一個邏輯設備
抓包位置: Server1 與 leaf01 或 leaf02 之間的連線（如 swp1）。
驗證目標(第一個封包):
Partner MAC 地址： 在 LACP PDU 封包中，檢查 Partner System ID。它必須是配置的 Anycast MAC：44:38:39:FF:00:AA。Collecting 與 Distributing 狀態。...
Link Aggregation Control Protocol
LACP Version: 0x01
TLV Type: Actor Information (0x01)
TLV Length: 0x14
Actor System Priority: 65535
Actor System ID: 4e:d4:fb:d8:48:6a (4e:d4:fb:d8:48:6a)
Actor Key: 15
Actor Port Priority: 255
Actor Port: 1
Actor State: 0x3f, LACP Activity, LACP Timeout, Aggregation, Synchronization, Collecting, Distributing
[Actor State Flags: **DCSGSA]
Reserved: 000000
TLV Type: Partner Information (0x02)
TLV Length: 0x14
Partner System Priority: 65535
Partner System: CumulusNetwo_ff:00:aa (44:38:39:ff:00:aa)
Partner Key: 15
Partner Port Priority: 255
Partner Port: 1
Partner State: 0x3f, LACP Activity, LACP Timeout, Aggregation, Synchronization, Collecting, Distributing
.... ...1 = LACP Activity: Active
.... ..1. = LACP Timeout: Short Timeout
.... .1.. = Aggregation: Aggregatable
.... 1... = Synchronization: In Sync
...1 .... = Collecting: Enabled
..1. .... = Distributing: Enabled
.0.. .... = Defaulted: No
0... .... = Expired: No
[Partner State Flags: **DCSGSA]
Reserved: 000000
TLV Type: Collector Information (0x03)
TLV Length: 0x10
Collector Max Delay: 0
Reserved: 000000000000000000000000
TLV Type: Terminator (0x00)
TLV Length: 0x00
Pad: 0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
控制平面 BGP EVPN 路由驗證
在 wireshark 中可以用
bgp.evpn.nlri.rt == 1進行過濾
我們觀察第 80 個封包，結論如下:
在 EVPN 運行前，Leaf 與 Spine 必須先交換 Loopback 地址以建立 VXLAN 隧道。第 80 個封包顯示 leaf01 (AS 65101) 正在向 spine01 宣告其 Loopback 地址 10.10.10.1/32。該底層路由採用的 BGP Unnumbered (IPv6 Link-local) 方式已成功運作 。
ESI 發現與鄰居關係 (EVPN Type-4)，是驗證 EVPN-MH 的核心目標，確認兩台 Leaf 是否知道彼此共享同一個網段。這是 leaf01 在告訴 spine01（以及最終告訴 leaf02）: 我有這三個 Bond 網段，準備好進行多歸屬備援了
....
Path attributes
Path Attribute - MP_REACH_NLRI
Flags: 0x90, Optional, Extended-Length, Non-transitive, Complete
1... .... = Optional: Set
.0.. .... = Transitive: Not set
..0. .... = Partial: Not set
...1 .... = Extended-Length: Set
.... 0000 = Unused: 0x0
Type Code: MP_REACH_NLRI (14)
Length: 84
Address family identifier (AFI): Layer-2 VPN (25)
Subsequent address family identifier (SAFI): EVPN (70)
Next hop: 10.10.10.4
IPv4 Address: 10.10.10.4
Number of Subnetwork points of attachment (SNPA): 0
Network Layer Reachability Information (NLRI)
EVPN NLRI: Ethernet Segment Route
Route Type: Ethernet Segment Route (4) # Type4
Length: 23
Route Distinguisher: 00010a0a0a040009 (10.10.10.4:9)
ESI: 03:44:38:39:ff:00:bb:00:00:01
ESI Type: ESI MAC address defined (3)
ESI Value: 44 38 39 ff 00 bb 00 00 01
ESI system MAC: CumulusNetwo_ff:00:bb (44:38:39:ff:00:bb)
ESI system mac discriminator: 00 00
Remaining bytes: 01
IP Address Length: 32
IPv4 address: 10.10.10.4
EVPN NLRI: Ethernet Segment Route
Route Type: Ethernet Segment Route (4)
Length: 23
Route Distinguisher: 00010a0a0a04000a (10.10.10.4:10)
ESI: 03:44:38:39:ff:00:bb:00:00:02
ESI Type: ESI MAC address defined (3)
ESI Value: 44 38 39 ff 00 bb 00 00 02
ESI system MAC: CumulusNetwo_ff:00:bb (44:38:39:ff:00:bb)
ESI system mac discriminator: 00 00
Remaining bytes: 02
IP Address Length: 32
IPv4 address: 10.10.10.4
EVPN NLRI: Ethernet Segment Route
Route Type: Ethernet Segment Route (4)
Length: 23
Route Distinguisher: 00010a0a0a04000b (10.10.10.4:11)
ESI: 03:44:38:39:ff:00:bb:00:00:03
ESI Type: ESI MAC address defined (3)
ESI Value: 44 38 39 ff 00 bb 00 00 03
ESI system MAC: CumulusNetwo_ff:00:bb (44:38:39:ff:00:bb)
ESI system mac discriminator: 00 00
Remaining bytes: 03
IP Address Length: 32
IPv4 address: 10.10.10.4
Path Attribute - ORIGIN: IGP
Flags: 0x40, Transitive, Well-known, Complete
0... .... = Optional: Not set
.1.. .... = Transitive: Set
..0. .... = Partial: Not set
...0 .... = Extended-Length: Not set
.... 0000 = Unused: 0x0
Type Code: ORIGIN (1)
Length: 1
Origin: IGP (0)
Path Attribute - AS_PATH: 65199 65104
Flags: 0x50, Transitive, Extended-Length, Well-known, Complete
0... .... = Optional: Not set
.1.. .... = Transitive: Set
..0. .... = Partial: Not set
...1 .... = Extended-Length: Set
.... 0000 = Unused: 0x0
Type Code: AS_PATH (2)
Length: 10
AS Path segment: 65199 65104
Segment type: AS_SEQUENCE (2)
Segment length (number of ASN): 2
AS4: 65199
AS4: 65104
Path Attribute - EXTENDED_COMMUNITIES
Flags: 0xc0, Optional, Transitive, Complete
1... .... = Optional: Set
.1.. .... = Transitive: Set
..0. .... = Partial: Not set
...0 .... = Extended-Length: Not set
.... 0000 = Unused: 0x0
Type Code: EXTENDED_COMMUNITIES (16)
Length: 24
Carried extended communities: (3 communities)
Encapsulation: VXLAN Encapsulation [Transitive Opaque]
ES-Import Route Target: RT: 44:38:39:ff:00:bb [Transitive EVPN]
DF Election: 0x0200 0x0000 0xc350 [Transitive EVPN]
**全主動負載平衡與 Aliasing (
iThome鐵人賽
看影片追技術