五阶段 IP 交换矩阵设计和实施
为了使您能够扩展数据中心中的现有 EVPN-VXLAN 网络,瞻博网络支持 5 级 IP 交换矩阵。尽管 5 级 IP 交换矩阵实际上由 3 层网络设备组成,但术语 5 阶段 是指从一个主机发送到另一个主机的流量必须遍历才能到达其目标的网络设备数。
瞻博网络在数据中心内的交付点间 (POD) 连接用例中支持 5 级 IP 交换矩阵。此用例假设您的 EVPN-VXLAN 网络已将主干和叶设备层包括在两个 POD 中。要启用两个 POD 之间的连接,请添加一层超级主干设备。要确定哪些瞻博网络设备可用作超级主干设备,请参阅 数据中心 EVPN-VXLAN 交换矩阵参考设计 - 支持的硬件摘要 表。
图 1 显示了在此参考设计中使用的 5 级 IP 交换矩阵。
如图 1 所示,每个超级主干设备都连接到了每个 POD 中的每个主干设备。
我们在每个 POD 中支持以下网络叠加类型组合:
两个 POD 中的 EVPN-VXLAN 交换矩阵都有一个集中路由的桥接叠加。
两个 POD 中的 EVPN-VXLAN 交换矩阵具有边缘路由桥接叠加。
一个 POD 中的 EVPN-VXLAN 交换矩阵具有集中路由桥接叠加,另一个 POD 中的交换矩阵则具有边缘路由桥接叠加。
瞻博网络的 5 级 IP 交换矩阵支持 RFC 7938( 在大规模数据中心中使用 BGP 进行路由)。但是,在适当情况下,我们使用术语来更有效地描述我们的用例。
请注意以下 5 级 IP 交换矩阵参考设计:
此参考设计假定两个 POD 中的主干和叶设备层已存在,并已开始运行。因此,本主题除了介绍如何配置 EVPN 5 类路由的播发外,本主题仅提供超级主干设备的配置。有关在两个 POD 中配置主干和叶设备的信息,请参阅以下内容:
参考设计将超级主干 1 和 2 集成到现有 IP 交换矩阵底层和 EVPN 叠加网络中。
超级主干设备具有以下功能:
它们仅充当 IP 传输设备。
它们用作主干 1 到 4 的路由反射器。
在 EVPN 叠加网络中配置路由协议时,您可以使用 IBGP 或 EBGP。通常,如果数据中心在整个过程中使用相同的自治系统 (AS) 编号,则使用 IBGP;如果数据中心始终使用不同的 AS 编号,则使用 EBGP。此参考设计使用 IBGP 配置选项。有关 EBGP 配置选项的信息,请参阅 EVPN 网络中通过顶置式数据中心互连。
将超级主干 1 和 2 集成到现有 IP 交换矩阵底层和 EVPN 叠加网络中并验证配置后,超级主干设备将通过传播 EVPN type-2 路由来处理 POD 1 和 2 之间的通信。如果您的 POD 使用相同的 IP 地址子网方案,此方法将起作用。但是,如果连接到每个 POD 中叶设备的服务器位于不同的子网中,则必须配置在 POD 中处理子网间路由的设备,以便播发 EVPN 5 类路由。有关更多信息,请参阅本主题后面的 如何启用 POD 中的路由设备上的 EVPN Type-5 路由通告 。
如何将超级主干设备集成到 IP 交换矩阵底层网络中
本部分介绍如何配置超级主干设备,以便这些超级主干设备能够与已配置为现有 IP 交换矩阵底层网络的一部分主干设备进行通信。
有关 IP 交换矩阵底层网络中接口和自治系统 (AS) 的详细信息,请参阅 图 2。
- 配置将超级主干设备连接到主干 1 到 4 的接口。
对于与每个主干设备的连接,我们创建一个聚合以太网接口,该接口当前包含一个链路。如果以后需要增加每个主干设备的吞吐量,我们可以使用此方法。
有关超级主干设备的接口详细信息,请参阅 图 2。
Super Spine 1
set interfaces et-0/0/1 ether-options 802.3ad ae1 set interfaces ae1 unit 0 family inet address 172.16.101.0/31 set interfaces et-0/0/2 ether-options 802.3ad ae2 set interfaces ae2 unit 0 family inet address 172.16.102.0/31 set interfaces et-0/0/3 ether-options 802.3ad ae3 set interfaces ae3 unit 0 family inet address 172.16.103.0/31 set interfaces et-0/0/4 ether-options 802.3ad ae4 set interfaces ae4 unit 0 family inet address 172.16.104.0/31
Super Spine 2
set interfaces et-0/0/1 ether-options 802.3ad ae1 set interfaces ae1 unit 0 family inet address 172.16.101.2/31 set interfaces et-0/0/2 ether-options 802.3ad ae2 set interfaces ae2 unit 0 family inet address 172.16.102.2/31 set interfaces et-0/0/3 ether-options 802.3ad ae3 set interfaces ae3 unit 0 family inet address 172.16.103.2/31 set interfaces et-0/0/4 ether-options 802.3ad ae4 set interfaces ae4 unit 0 family inet address 172.16.104.2/31
- 为环路接口 lo0.0 指定 IP 地址。
此过程稍后在设置导出路由策略时,我们会为每个超级主干设备使用环路地址。
Super Spine 1
set interfaces lo0 unit 0 family inet address 192.168.2.1/32
Super Spine 2
set interfaces lo0 unit 0 family inet address 192.168.2.2/32
- 配置路由器 ID。
在 EVPN 叠加网络中设置路由反射器群集时,我们使用每个超级主干设备的路由器 ID。
Super Spine 1
set routing-options router-id 192.168.2.1
Super Spine 2
set routing-options router-id 192.168.2.2
- 创建名为
underlay-bgp
的 BGP 对等组,并在底层网络中启用 EBGP 作为路由协议。Super Spines 1 and 2
set protocols bgp group underlay-bgp type external
- 配置 AS 编号。
在此参考设计中,在底层网络中,为每台设备分配一个唯一的 AS 编号。有关超级主干设备的 AS 编号,请参阅 图 2。
底层网络中 EBGP 的 AS 编号使用
local-as
语句在 BGP 对等组级别配置,因为系统 AS 编号设置用于 EVPN 叠加网络中的 MP-IBGP 信令。Super Spine 1
set protocols bgp group underlay-bgp local-as 4200000021
Super Spine 2
set protocols bgp group underlay-bgp local-as 4200000022
- 设置与主干 1 到 4 的 BGP 对等关系。
要建立对等关系,请在每个超级主干设备上指定主干设备的 IP 地址和 AS 编号,将每个主干设备配置为邻接方。有关主干设备的 IP 地址和 AS 编号,请参阅 图 2。
Super Spine 1
set protocols bgp group underlay-bgp neighbor 172.16.101.1 peer-as 4200000001 set protocols bgp group underlay-bgp neighbor 172.16.102.1 peer-as 4200000002 set protocols bgp group underlay-bgp neighbor 172.16.103.1 peer-as 4200000003 set protocols bgp group underlay-bgp neighbor 172.16.104.1 peer-as 4200000004
Super Spine 2
set protocols bgp group underlay-bgp neighbor 172.16.101.3 peer-as 4200000001 set protocols bgp group underlay-bgp neighbor 172.16.102.3 peer-as 4200000002 set protocols bgp group underlay-bgp neighbor 172.16.103.3 peer-as 4200000003 set protocols bgp group underlay-bgp neighbor 172.16.104.3 peer-as 4200000004
- 配置导出路由策略,用于将超级主干设备上的环路接口 lo0.0 的 IP 地址播发至 EBGP 对等设备(主干 1 到 4)。此策略会拒绝所有其他播发。
Super Spines 1 and 2
set policy-options policy-statement underlay-clos-export term loopback from interface lo0.0 set policy-options policy-statement underlay-clos-export term loopback then accept set policy-options policy-statement underlay-clos-export term def then reject set protocols bgp group underlay-bgp export underlay-clos-export
- 使用
multiple-as
选项启用多路径,从而在不同 AS 中的 EBGP 对等方之间实现负载平衡。默认情况下,EBGP 会为每个前缀选择一个最佳路径,并将该路由安装在转发表表中。启用 BGP 多路径后,指向给定目标的所有等价路径都会安装到转发表表中。
Super Spines 1 and 2
set protocols bgp group underlay-bgp multipath multiple-as
- 对所有 BGP 会话启用双向转发检测 (BFD),以便快速检测故障和重新融合。
Super Spines 1 and 2
set protocols bgp group underlay-bgp bfd-liveness-detection minimum-interval 1000 set protocols bgp group underlay-bgp bfd-liveness-detection multiplier 3 set protocols bgp group underlay-bgp bfd-liveness-detection session-mode automatic
如何将超级主干设备集成到 EVPN 叠加网络中
本节介绍如何将超级主干设备集成到 EVPN 叠加网络中。在此控制平面驱动叠加中,我们使用 IBGP 与多协议 BGP (MP-IBGP) 在单个 AS 中的所有设备之间建立一个信令路径。
在此 IBGP 叠加中,超级主干设备充当路由反射器群集,而主干设备是路由反射器客户端。有关 EVPN 叠加网络中路由反射器群集 ID 和 BGP 邻接方 IP 地址的详细信息,请参阅 图 3。
- 为 IBGP 叠加配置 AS 编号。
参与此叠加的所有设备(超级主干 1 和 2、主干 1 到 4、叶 1 到 4)都必须使用相同的 AS 编号。在此示例中,AS 编号为专用 AS 4210000001。
Super Spines 1 and 2
set routing-options autonomous-system 4210000001
- 使用 EVPN 信令配置 IBGP,以便与主干 1 到 4 对等。此外,形成路由反射器群集(群集 ID 192.168.2.10),并为 BGP 配置等价多路径 (ECMP)。启用路径最大传输单元 (MTU) 发现,以动态确定源和目标之间的网络路径上的 MTU 大小,以避免 IP 分片。
有关超级主干和主干设备的路由反射器群集 ID 和 BGP 邻接方 IP 地址的详细信息,请参阅 图 3。
Super Spine 1
set protocols bgp group overlay-bgp type internal set protocols bgp group overlay-bgp local-address 192.168.2.1 set protocols bgp group overlay-bgp mtu-discovery set protocols bgp group overlay-bgp family evpn signaling set protocols bgp group overlay-bgp cluster 192.168.2.10 set protocols bgp group overlay-bgp multipath set protocols bgp group overlay-bgp neighbor 192.168.0.1 set protocols bgp group overlay-bgp neighbor 192.168.0.2 set protocols bgp group overlay-bgp neighbor 192.168.0.3 set protocols bgp group overlay-bgp neighbor 192.168.0.4
Super Spine 2
set protocols bgp group overlay-bgp type internal set protocols bgp group overlay-bgp local-address 192.168.2.2 set protocols bgp group overlay-bgp mtu-discovery set protocols bgp group overlay-bgp family evpn signaling set protocols bgp group overlay-bgp cluster 192.168.2.10 set protocols bgp group overlay-bgp multipath set protocols bgp group overlay-bgp neighbor 192.168.0.1 set protocols bgp group overlay-bgp neighbor 192.168.0.2 set protocols bgp group overlay-bgp neighbor 192.168.0.3 set protocols bgp group overlay-bgp neighbor 192.168.0.4
注意:此参考设计不包括超级主干 1 和 2 之间的 BGP 对等配置。但是,如果要设置此对等互连以完成全网状对等拓扑,则可以选择通过创建另一个 BGP 组并指定该组中的配置来实现。例如:
Super Spine 1
set protocols bgp group overlay-bgp2 type internal set protocols bgp group overlay-bgp2 local-address 192.168.2.1 set protocols bgp group overlay-bgp2 family evpn signaling set protocols bgp group overlay-bgp2 neighbor 192.168.2.2
Super Spine 2
set protocols bgp group overlay-bgp2 type internal set protocols bgp group overlay-bgp2 local-address 192.168.2.2 set protocols bgp group overlay-bgp2 family evpn signaling set protocols bgp group overlay-bgp2 neighbor 192.168.2.1
- 为所有 BGP 会话启用 BFD,以快速检测故障和重新融合。
Super Spines 1 and 2
set protocols bgp group overlay-bgp bfd-liveness-detection minimum-interval 1000 set protocols bgp group overlay-bgp bfd-liveness-detection multiplier 3 set protocols bgp group overlay-bgp bfd-liveness-detection session-mode automatic
如何验证超级主干设备是否已集成到底层和叠加网络中
本节介绍如何验证超级主干设备是否已正确集成到 IP 交换矩阵底层和 EVPN 叠加网络中。
成功完成此验证后,超级主干设备将通过广告 EVPN type-2 路由来处理 POD 1 和 2 之间的通信。如果您的 POD 使用相同的 IP 地址子网方案,此方法将起作用。但是,如果每个 POD 使用不同的 IP 地址子网方案,则必须额外配置在 POD 中处理子网间路由的设备,以便播发 EVPN 5 类路由。有关更多信息,请参阅本主题后面的 如何启用 POD 中的路由设备上的 EVPN Type-5 路由通告 。
- 验证聚合以太网接口是否已启用、物理链路是否已启动以及数据包(如果发送了流量)。
以下输出提供了超级主干 1 上的聚合以太网接口 ae1 的验证。
user@super-spine-1> show interfaces ae1 Physical interface: ae1, Enabled, Physical link is Up Interface index: 129, SNMP ifIndex: 544 Link-level type: Ethernet, MTU: 9192, Speed: 80Gbps, BPDU Error: None, Ethernet-Switching Error: None, MAC-REWRITE Error: None, Loopback: Disabled, Source filtering: Disabled, Flow control: Disabled, Minimum links needed: 1, Minimum bandwidth needed: 1bps Device flags : Present Running Interface flags: SNMP-Traps Internal: 0x4000 Current address: 80:ac:ac:24:21:98, Hardware address: 80:ac:ac:24:21:98 Last flapped : 2020-07-30 13:09:31 PDT (3d 05:01 ago) Input rate : 42963216 bps (30206 pps) Output rate : 107152 bps (76 pps) Logical interface ae1.0 (Index 544) (SNMP ifIndex 564) Flags: Up SNMP-Traps 0x4004000 Encapsulation: ENET2 Statistics Packets pps Bytes bps Bundle: Input : 7423834047 30126 1155962320326 37535088 Output: 149534343 82 17315939427 83824 Adaptive Statistics: Adaptive Adjusts: 0 Adaptive Scans : 0 Adaptive Updates: 0 Protocol inet, MTU: 9000 Max nh cache: 75000, New hold nh limit: 75000, Curr nh cnt: 1, Curr new hold cnt: 0, NH drop cnt: 0 Flags: Sendbcast-pkt-to-re, Is-Primary, User-MTU Addresses, Flags: Is-Preferred Is-Primary Destination: 172.16.101.0/31, Local: 172.16.101.0
- 验证 BGP 是否已启动并运行。
下面的输出可以验证是否与主干 1 到 4 建立了 EBGP 和 IBGP 对等关系,以及流量路径是否处于活动状态。
user@super-spine-1> show bgp summary Threading mode: BGP I/O Groups: 2 Peers: 8 Down peers: 0 Table Tot Paths Act Paths Suppressed History Damp State Pending bgp.evpn.0 219394 210148 0 0 0 0 inet.0 55 27 0 0 0 0 Peer AS InPkt OutPkt OutQ Flaps Last Up/Dwn State|#Active/Received/Accepted/Damped... 172.16.101.1 4200000001 9452 10053 0 2 3d 5:01:58 Establ inet.0: 6/14/14/0 172.16.102.1 4200000002 9462 10061 0 3 3d 4:58:50 Establ inet.0: 7/14/14/0 172.16.103.1 4200000003 9244 9828 0 5 3d 3:14:54 Establ inet.0: 7/14/14/0 172.16.104.1 4200000004 9457 10057 0 1 3d 4:58:35 Establ inet.0: 7/13/13/0 192.168.0.1 4210000001 29707 436404 0 2 3d 5:01:49 Establ bgp.evpn.0: 16897/16897/16897/0 192.168.0.2 4210000001 946949 237127 0 3 3d 4:58:51 Establ bgp.evpn.0: 50844/55440/55440/0 192.168.0.3 4210000001 40107 350304 0 7 3d 3:13:54 Establ bgp.evpn.0: 50723/55373/55373/0 192.168.0.4 4210000001 50670 274946 0 1 3d 4:58:32 Establ bgp.evpn.0: 91684/91684/91684/0
- 验证 BFD 是否工作。
下面的输出可以验证超级主干 1 与主干 1 到 4 之间的 BGP 会话是否已建立并处于 Up 状态。
user@super-spine-1> show bfd session Detect Transmit Address State Interface Time Interval Multiplier 172.16.101.1 Up ae1.0 3.000 1.000 3 172.16.102.1 Up ae2.0 3.000 1.000 3 172.16.103.1 Up ae3.0 3.000 1.000 3 172.16.104.1 Up ae4.0 3.000 1.000 3 192.168.0.1 Up 3.000 1.000 3 192.168.0.2 Up 3.000 1.000 3 192.168.0.3 Up 3.000 1.000 3 192.168.0.4 Up 3.000 1.000 3
如何在 POD 中的路由设备上启用 EVPN 5 类路由的播发
完成以下部分中的任务后,超级主干设备将通过广告 EVPN type-2 路由来处理 POD 1 和 2 之间的通信。
如果连接到两个 POD 中叶设备的服务器位于同一子网中,则可以跳过此部分的任务。但是,如果每个 POD 中的服务器位于不同的子网中,则必须进一步配置在 POD 中处理子网间路由的设备,以便按照本节所述播发 EVPN 5 类路由。此类型的路由也称为 IP 前缀路由。
在此 EVPN 5 类参考设计中,两个 POD 中的 EVPN-VXLAN 交换矩阵都有一个集中路由的桥接叠加。在这种叠加中,主干设备会处理子网间路由。因此,本节介绍如何在 POD 1 和 2 中的主干设备上启用 EVPN 5 类路由的播发。
要启用 EVPN 5 类路由的播发,您可以在每个主干设备上设置名为 VRF-1 的租户路由实例。在路由实例中,您可以指定希望主干设备将哪些主机 IP 地址和前缀播发为 EVPN 5 类路由,并且 VXLAN 网络标识符 (VNI) 为 500001。主干设备会将 EVPN type-5 路由播发至同一 POD 内的其他主干和叶设备。主干设备还将将 EVPN type-5 路由播发至超级主干设备,而超级主干设备又会将路由播发至其他 POD 中的主干设备。配置 VRF-1 的所有主干设备都将将 EVPN type-5 路由导入其 VRF-1 路由表中。
启用 EVPN 5 类路由的播发后,超级主干设备将通过播发 EVPN type-5 路由来处理 POD 1 和 2 之间的通信。
图 4 显示了 POD 间用例的 EVPN Type-5 配置详细信息。
表 1 概述了此参考设计的 VLAN ID 到 IRB 接口的映射。
VLAN 名称 |
VLAN ID |
IRB 接口 |
---|---|---|
Spines 1 and 2 in POD 1 |
||
VLAN BD-1 |
1 |
irb.1 |
VLAN BD-2 |
2 |
irb.2 |
Spines 3 and 4 in POD 2 |
||
VLAN BD-3 |
3 |
irb.3 |
VLAN BD-4 |
4 |
irb.4 |
要设置 EVPN 5 类路由的播发:
- 创建环路接口 lo0.1,并指定其位于 IPv4 地址系列中。
例如:
Spine 1
set interfaces lo0 unit 1 family inet
- 配置名为 VRF-1 的路由
vrf
实例。在此路由实例中,包括环路接口 lo0.1,以便作为 VXLAN 网关的主干设备可以解析与每个主干设备对应的 ARP 请求和 IRB 接口(见 表 1)。为路由实例设置路由识别工具和 VRF 目标。使用多路径 ECMP 选项为 EVPN 5 类路由配置负载平衡。例如:
Spine 1
set routing-instances VRF-1 instance-type vrf set routing-instances VRF-1 interface lo0.1 set routing-instances VRF-1 interface irb.1 set routing-instances VRF-1 interface irb.2 set routing-instances VRF-1 route-distinguisher 192.168.0.1:1 set routing-instances VRF-1 vrf-target import target:200:1 set routing-instances VRF-1 vrf-target export target:100:1 set routing-instances VRF-1 routing-options rib VRF-1.inet6.0 multipath set routing-instances VRF-1 routing-options multipath
Spine 2
set routing-instances VRF-1 instance-type vrf set routing-instances VRF-1 interface lo0.1 set routing-instances VRF-1 interface irb.1 set routing-instances VRF-1 interface irb.2 set routing-instances VRF-1 route-distinguisher 192.168.0.2:1 set routing-instances VRF-1 vrf-target import target:200:1 set routing-instances VRF-1 vrf-target export target:100:1 set routing-instances VRF-1 routing-options rib VRF-1.inet6.0 multipath set routing-instances VRF-1 routing-options multipath
Spine 3
set routing-instances VRF-1 instance-type vrf set routing-instances VRF-1 interface lo0.1 set routing-instances VRF-1 interface irb.3 set routing-instances VRF-1 interface irb.4 set routing-instances VRF-1 route-distinguisher 192.168.0.3:1 set routing-instances VRF-1 vrf-target import target:100:1 set routing-instances VRF-1 vrf-target export target:200:1 set routing-instances VRF-1 routing-options rib VRF-1.inet6.0 multipath set routing-instances VRF-1 routing-options multipath
Spine 4
set routing-instances VRF-1 instance-type vrf set routing-instances VRF-1 interface lo0.1 set routing-instances VRF-1 interface irb.3 set routing-instances VRF-1 interface irb.4 set routing-instances VRF-1 route-distinguisher 192.168.0.4:1 set routing-instances VRF-1 vrf-target import target:100:1 set routing-instances VRF-1 vrf-target export target:200:1 set routing-instances VRF-1 routing-options rib VRF-1.inet6.0 multipath set routing-instances VRF-1 routing-options multipath
- 启用 EVPN 以播发直接下一跃点,指定 VXLAN 封装,并将 VNI 500001分配给 EVPN 5 类路由。
对于主干 1 到 4 的配置,在此配置中使用 VNI 500001。
例如:
Spine 1
set routing-instances VRF-1 protocols evpn ip-prefix-routes advertise direct-nexthop set routing-instances VRF-1 protocols evpn ip-prefix-routes encapsulation vxlan set routing-instances VRF-1 protocols evpn ip-prefix-routes vni 500001
- 为租户路由实例 VRF-1 定义名为 ExportHostRoutes 的 EVPN type-5 导出策略。
例如,以下配置确定 VRF-1 播发 EVPN 从直接连接到主干 1 的网络获得的所有主机 IPv4 和 IPv6 地址和前缀。
Spine 1
set policy-options policy-statement ExportHostRoutes term 1 from protocol evpn set policy-options policy-statement ExportHostRoutes term 1 from route-filter 0.0.0.0/0 prefix-length-range /32-/32 set policy-options policy-statement ExportHostRoutes term 1 then accept set policy-options policy-statement ExportHostRoutes term 2 from family inet6 set policy-options policy-statement ExportHostRoutes term 2 from protocol evpn set policy-options policy-statement ExportHostRoutes term 2 from route-filter 0::0/0 prefix-length-range /128-/128 set policy-options policy-statement ExportHostRoutes term 2 then accept set policy-options policy-statement ExportHostRoutes term 3 from protocol direct set policy-options policy-statement ExportHostRoutes term 3 then accept
- 将名为 ExportHostRoutes 的导出策略应用于 VRF-1。
例如:
Spine 1
set routing-instances VRF-1 protocols evpn ip-prefix-routes export ExportHostRoutes
- 在此参考设计中,QFX5120-32C 交换机用作主干设备。对于这些交换机以及作为集中路由桥接叠加中主干设备的所有其他 QFX5XXX 交换机,必须执行以下附加配置,以正确实施 EVPN 纯 5 类路由。
Spines 1 through 4
set routing-options forwarding-table chained-composite-next-hop ingress evpn set forwarding-options vxlan-routing next-hop 32768 set forwarding-options vxlan-routing interface-num 8192 set forwarding-options vxlan-routing overlay-ecmp
如何验证 POD 中路由设备上的 EVPN 5 类路由的播发
要验证此参考设计中的主干设备是否正确宣传 EVPN type-5 路由,
- 查看 VRF 路由表,以验证终端系统路由和主干设备路由是否正在交换。
以下输出片段仅显示 IPv4 路由。
主干 1
user@Spine-1> show route table VRF-1 VRF-1.inet.0: 53 destinations, 93 routes (53 active, 0 holddown, 0 hidden) @ = Routing Use Only, # = Forwarding Use Only + = Active Route, - = Last Active, * = Both 10.0.1.0/24 *[Direct/0] 1d 00:19:49 > via irb.1 10.0.1.1/32 *[EVPN/7] 00:00:56 > via irb.1 10.0.1.241/32 *[Local/0] 1d 00:19:49 Local via irb.1 10.0.1.254/32 *[Local/0] 1d 00:19:49 Local via irb.1 10.0.2.0/24 *[Direct/0] 1d 00:19:49 > via irb.2 10.0.2.1/32 *[EVPN/7] 00:00:56 > via irb.2 10.0.2.241/32 *[Local/0] 1d 00:19:49 Local via irb.2 10.0.2.254/32 *[Local/0] 1d 00:19:49 Local via irb.2 10.0.3.0/24 @[EVPN/170] 1d 00:17:54 to 172.16.101.0 via ae3.0 > to 172.16.101.2 via ae4.0 [EVPN/170] 20:53:20 to 172.16.101.0 via ae3.0 > to 172.16.101.2 via ae4.0 #[Multipath/255] 20:53:20, metric2 0 to 172.16.101.0 via ae3.0 > to 172.16.101.2 via ae4.0 to 172.16.101.0 via ae3.0 > to 172.16.101.2 via ae4.0 10.0.3.1/32 @[EVPN/170] 00:00:26 to 172.16.101.0 via ae3.0 > to 172.16.101.2 via ae4.0 [EVPN/170] 00:00:26 to 172.16.101.0 via ae3.0 > to 172.16.101.2 via ae4.0 #[Multipath/255] 00:00:26, metric2 0 to 172.16.101.0 via ae3.0 > to 172.16.101.2 via ae4.0 to 172.16.101.0 via ae3.0 > to 172.16.101.2 via ae4.0 10.0.4.0/24 @[EVPN/170] 1d 00:17:54 to 172.16.101.0 via ae3.0 > to 172.16.101.2 via ae4.0 [EVPN/170] 20:53:20 to 172.16.101.0 via ae3.0 > to 172.16.101.2 via ae4.0 #[Multipath/255] 20:53:20, metric2 0 to 172.16.101.0 via ae3.0 > to 172.16.101.2 via ae4.0 to 172.16.101.0 via ae3.0 > to 172.16.101.2 via ae4.0 10.0.4.1/32 @[EVPN/170] 00:00:26 to 172.16.101.0 via ae3.0 > to 172.16.101.2 via ae4.0 [EVPN/170] 00:00:26 to 172.16.101.0 via ae3.0 > to 172.16.101.2 via ae4.0 #[Multipath/255] 00:00:26, metric2 0 to 172.16.101.0 via ae3.0 > to 172.16.101.2 via ae4.0 to 172.16.101.0 via ae3.0 > to 172.16.101.2 via ae4.0 ...
主干 3
user@Spine-3> show route table VRF-1 10.0.1.0/24 @[EVPN/170] 1d 00:17:54 to 172.16.103.0 via ae3.0 > to 172.16.103.2 via ae4.0 [EVPN/170] 20:53:20 to 172.16.103.0 via ae3.0 > to 172.16.103.2 via ae4.0 #[Multipath/255] 20:53:20, metric2 0 to 172.16.103.0 via ae3.0 > to 172.16.103.2 via ae4.0 to 172.16.103.0 via ae3.0 > to 172.16.103.2 via ae4.0 10.0.1.1/32 @[EVPN/170] 00:00:26 to 172.16.103.0 via ae3.0 > to 172.16.103.2 via ae4.0 [EVPN/170] 00:00:26 to 172.16.103.0 via ae3.0 > to 172.16.103.2 via ae4.0 #[Multipath/255] 00:00:26, metric2 0 to 172.16.103.0 via ae3.0 > to 172.16.103.2 via ae4.0 to 172.16.103.0 via ae3.0 > to 172.16.103.2 via ae4.0 10.0.2.0/24 @[EVPN/170] 1d 00:17:54 to 172.16.103.0 via ae3.0 > to 172.16.103.2 via ae4.0 [EVPN/170] 20:53:20 to 172.16.103.0 via ae3.0 > to 172.16.103.2 via ae4.0 #[Multipath/255] 20:53:20, metric2 0 to 172.16.103.0 via ae3.0 > to 172.16.103.2 via ae4.0 to 172.16.103.0 via ae3.0 > to 172.16.103.2 via ae4.0 10.0.2.1/32 @[EVPN/170] 00:00:26 to 172.16.103.0 via ae3.0 > to 172.16.103.2 via ae4.0 [EVPN/170] 00:00:26 to 172.16.103.0 via ae3.0 > to 172.16.103.2 via ae4.0 #[Multipath/255] 00:00:26, metric2 0 to 172.16.103.0 via ae3.0 > to 172.16.103.2 via ae4.0 to 172.16.103.0 via ae3.0 > to 172.16.103.2 via ae4.0 10.0.3.0/24 *[Direct/0] 1d 00:19:49 > via irb.3 10.0.3.1/32 *[EVPN/7] 00:00:56 > via irb.3 10.0.3.241/32 *[Local/0] 1d 00:19:49 Local via irb.3 10.0.3.254/32 *[Local/0] 1d 00:19:49 Local via irb.3 10.0.4.0/24 *[Direct/0] 1d 00:19:49 > via irb.4 10.0.4.1/32 *[EVPN/7] 00:00:56 > via irb.4 10.0.4.241/32 *[Local/0] 1d 00:19:49 Local via irb.4 10.0.4.254/32 *[Local/0] 1d 00:19:49 Local via irb.4 ...
- 验证 EVPN Type-5 IPv4 和 IPv6 路由是否已导出并导入到 VRF-1 路由实例中。
主干 1
user@Spine-1> show evpn ip-prefix-database l3-context VRF-1 L3 context: VRF-1 IPv4->EVPN Exported Prefixes Prefix EVPN route status 10.0.1.0/24 Created 10.0.1.1/32 Created 10.0.2.0/24 Created 10.0.2.1/32 Created IPv6->EVPN Exported Prefixes Prefix EVPN route status 2001:db8::10.0.1:0/112 Created 2001:db8::10.0.1:1/128 Created 2001:db8::10.0.2:0/112 Created 2001:db8::10.0.2:1/128 Created EVPN->IPv4 Imported Prefixes Prefix Etag 10.0.3.0/24 0 Route distinguisher VNI/Label Router MAC Nexthop/Overlay GW/ESI 192.168.0.3:1 500001 00:00:5e:00:53:f2 192.168.0.3 192.168.0.4:1 500001 00:00:5e:00:53:d0 192.168.0.4 10.0.3.1/32 0 Route distinguisher VNI/Label Router MAC Nexthop/Overlay GW/ESI 192.168.0.3:1 500001 00:00:5e:00:53:f2 192.168.0.3 192.168.0.4:1 500001 00:00:5e:00:53:d0 192.168.0.4 10.0.4.0/24 0 Route distinguisher VNI/Label Router MAC Nexthop/Overlay GW/ESI 192.168.0.3:1 500001 00:00:5e:00:53:f2 192.168.0.3 192.168.0.4:1 500001 00:00:5e:00:53:d0 192.168.0.4 10.0.4.1/32 0 Route distinguisher VNI/Label Router MAC Nexthop/Overlay GW/ESI 192.168.0.3:1 500001 00:00:5e:00:53:f2 192.168.0.3 192.168.0.4:1 500001 00:00:5e:00:53:d0 192.168.0.4 EVPN->IPv6 Imported Prefixes Prefix Etag 2001:db8::10:0:3:0/112 0 Route distinguisher VNI/Label Router MAC Nexthop/Overlay GW/ESI 192.168.0.3:1 500001 00:00:5e:00:53:f2 192.168.0.3 192.168.0.4:1 500001 00:00:5e:00:53:d0 192.168.0.4 2001:db8::10:0:3:1/128 0 Route distinguisher VNI/Label Router MAC Nexthop/Overlay GW/ESI 192.168.0.3:1 500001 00:00:5e:00:53:f2 192.168.0.3 192.168.0.4:1 500001 00:00:5e:00:53:d0 192.168.0.4 2001:db8::10:0:4:0/112 0 Route distinguisher VNI/Label Router MAC Nexthop/Overlay GW/ESI 192.168.0.3:1 500001 00:00:5e:00:53:f2 192.168.0.3 192.168.0.4:1 500001 00:00:5e:00:53:d0 192.168.0.4 2001:db8::10:0:4:1/128 0 Route distinguisher VNI/Label Router MAC Nexthop/Overlay GW/ESI 192.168.0.3:1 500001 00:00:5e:00:53:f2 192.168.0.3 192.168.0.4:1 500001 00:00:5e:00:53:d0 192.168.0.4
主干 3
user@Spine-3> show evpn ip-prefix-database l3-context VRF-1 L3 context: VRF-1 IPv4->EVPN Exported Prefixes Prefix EVPN route status 10.0.3.0/24 Created 10.0.3.1/32 Created 10.0.4.0/24 Created 10.0.4.1/32 Created IPv6->EVPN Exported Prefixes Prefix EVPN route status 2001:db8::10.0.3:0/112 Created 2001:db8::10.0.3:1/128 Created 2001:db8::10.0.4:0/112 Created 2001:db8::10.0.4:1/128 Created EVPN->IPv4 Imported Prefixes Prefix Etag 10.0.1.0/24 0 Route distinguisher VNI/Label Router MAC Nexthop/Overlay GW/ESI 192.168.0.1:1 500001 00:00:5e:00:53:38 192.168.0.1 192.168.0.2:1 500001 00:00:5e:00:53:29 192.168.0.2 10.0.1.1/32 0 Route distinguisher VNI/Label Router MAC Nexthop/Overlay GW/ESI 192.168.0.1:1 500001 00:00:5e:00:53:38 192.168.0.1 192.168.0.2:1 500001 00:00:5e:00:53:29 192.168.0.2 10.0.2.0/24 0 Route distinguisher VNI/Label Router MAC Nexthop/Overlay GW/ESI 192.168.0.1:1 500001 00:00:5e:00:53:38 192.168.0.1 192.168.0.2:1 500001 00:00:5e:00:53:29 192.168.0.2 10.0.2.1/32 0 Route distinguisher VNI/Label Router MAC Nexthop/Overlay GW/ESI 192.168.0.1:1 500001 00:00:5e:00:53:38 192.168.0.1 192.168.0.2:1 500001 00:00:5e:00:53:29 192.168.0.2 EVPN->IPv6 Imported Prefixes Prefix Etag 2001:db8::10:0:1:0/112 0 Route distinguisher VNI/Label Router MAC Nexthop/Overlay GW/ESI 192.168.0.1:1 500001 00:00:5e:00:53:38 192.168.0.1 192.168.0.2:1 500001 00:00:5e:00:53:29 192.168.0.2 2001:db8::10:0:1:1/128 0 Route distinguisher VNI/Label Router MAC Nexthop/Overlay GW/ESI 192.168.0.1:1 500001 00:00:5e:00:53:38 192.168.0.1 192.168.0.2:1 500001 00:00:5e:00:53:29 192.168.0.2 2001:db8::10:0:2:0/112 0 Route distinguisher VNI/Label Router MAC Nexthop/Overlay GW/ESI 192.168.0.1:1 500001 00:00:5e:00:53:38 192.168.0.1 192.168.0.2:1 500001 00:00:5e:00:53:29 192.168.0.2 2001:db8::10:0:2:1/128 0 Route distinguisher VNI/Label Router MAC Nexthop/Overlay GW/ESI 192.168.0.1:1 500001 00:00:5e:00:53:38 192.168.0.1 192.168.0.2:1 500001 00:00:5e:00:53:29 192.168.0.2
- 验证 EVPN type-5 路由封装详细信息。以下输出显示指定前缀的详细信息。
主干 1
user@Spine-1> show route table VRF-1 10.0.4.1 extensive VRF-1.inet.0: 53 destinations, 93 routes (53 active, 0 holddown, 0 hidden) 10.0.4.1/32 (3 entries, 1 announced) State: CalcForwarding TSI: KRT in-kernel 10.0.4.1/32 -> {list:composite(99398), composite(129244)} @EVPN Preference: 170/-101 Next hop type: Indirect, Next hop index: 0 Address: 0x16197b18 Next-hop reference count: 31 Next hop type: Router, Next hop index: 0 Next hop: 172.16.101.0 via ae3.0 Session Id: 0x0 Next hop: 172.16.101.2 via ae4.0, selected Session Id: 0x0 Protocol next hop: 192.168.0.4 Composite next hop: 0x1b8ed840 99398 INH Session ID: 0x349 VXLAN tunnel rewrite: MTU: 0, Flags: 0x0 Encap table ID: 0, Decap table ID: 1508 Encap VNI: 500001, Decap VNI: 500001 Source VTEP: 192.168.0.1, Destination VTEP: 192.168.0.4 SMAC: 00:00:5e:00:53:38, DMAC: 00:00:5e:00:53:f2 Indirect next hop: 0x15bc4284 2101077 INH Session ID: 0x349 State: Active Int Ext Age: 6:49 Metric2: 0 Validation State: unverified Task: VRF-1-EVPN-L3-context AS path: I (Originator) Cluster list: 192.168.2.10 Originator ID: 192.168.0.4 Communities: target:200:1 encapsulation:vxlan(0x8) router-mac:00:00:5e:00:53:f2 Composite next hops: 1 Protocol next hop: 192.168.0.4 Composite next hop: 0x1b8ed840 99398 INH Session ID: 0x349 VXLAN tunnel rewrite: MTU: 0, Flags: 0x0 Encap table ID: 0, Decap table ID: 1508 Encap VNI: 500001, Decap VNI: 500001 Source VTEP: 192.168.0.1, Destination VTEP: 192.168.0.4 SMAC: 00:00:5e:00:53:38, DMAC: 00:00:5e:00:53:f2 Indirect next hop: 0x15bc4284 2101077 INH Session ID: 0x349 Indirect path forwarding next hops: 2 Next hop type: Router Next hop: 172.16.101.0 via ae3.0 Session Id: 0x0 Next hop: 172.16.101.2 via ae4.0 Session Id: 0x0 192.168.0.4/32 Originating RIB: inet.0 Node path count: 1 Forwarding nexthops: 2 Next hop type: Router Next hop: 172.16.101.0 via ae3.0 Session Id: 0x0 Next hop: 172.16.101.2 via ae4.0 Session Id: 0x0 EVPN Preference: 170/-101 Next hop type: Indirect, Next hop index: 0 Address: 0x2755af1c Next-hop reference count: 31 Next hop type: Router, Next hop index: 0 Next hop: 172.16.101.0 via ae3.0 Session Id: 0x0 Next hop: 172.16.101.2 via ae4.0, selected Session Id: 0x0 Protocol next hop: 192.168.0.3 Composite next hop: 0x2a627e20 129244 INH Session ID: 0x84e VXLAN tunnel rewrite: MTU: 0, Flags: 0x0 Encap table ID: 0, Decap table ID: 1508 Encap VNI: 500001, Decap VNI: 500001 Source VTEP: 192.168.0.2, Destination VTEP: 192.168.0.3 SMAC: 00:00:5e:00:53:38, DMAC: 00:00:5e:00:53:d0 Indirect next hop: 0x15bb6c04 2105498 INH Session ID: 0x84e State: Int Ext Inactive reason: Nexthop address Age: 6:49 Metric2: 0 Validation State: unverified Task: VRF-1-EVPN-L3-context AS path: I (Originator) Cluster list: 192.168.2.10 Originator ID: 192.168.0.3 Communities: target:200:1 encapsulation:vxlan(0x8) router-mac:00:00:5e:00:53:d0 Composite next hops: 1 Protocol next hop: 192.168.0.3 Composite next hop: 0x2a627e20 129244 INH Session ID: 0x84e VXLAN tunnel rewrite: MTU: 0, Flags: 0x0 Encap table ID: 0, Decap table ID: 1508 Encap VNI: 500001, Decap VNI: 500001 Source VTEP: 192.168.0.2, Destination VTEP: 192.168.0.3 SMAC: 00:00:5e:00:53:38, DMAC: 00:00:5e:00:53:d0 Indirect next hop: 0x15bb6c04 2105498 INH Session ID: 0x84e Indirect path forwarding next hops: 2 Next hop type: Router Next hop: 172.16.101.0 via ae3.0 Session Id: 0x0 Next hop: 172.16.101.2 via ae4.0 Session Id: 0x0 192.168.0.3/32 Originating RIB: inet.0 Node path count: 1 Forwarding nexthops: 2 Next hop type: Router Next hop: 172.16.101.0 via ae3.0 Session Id: 0x0 Next hop: 172.16.101.2 via ae4.0 Session Id: 0x0 #Multipath Preference: 255 Next hop type: Indirect, Next hop index: 0 Address: 0xe3aa170 Next-hop reference count: 19 Next hop type: Router, Next hop index: 0 Next hop: 172.16.101.0 via ae3.0 Session Id: 0x0 Next hop: 172.16.101.2 via ae4.0 Session Id: 0x0 Next hop type: Router, Next hop index: 0 Next hop: 172.16.101.0 via ae3.0 Session Id: 0x0 Next hop: 172.16.101.2 via ae4.0, selected Session Id: 0x0 Protocol next hop: 192.168.0.4 Composite next hop: 0x1b8ed840 99398 INH Session ID: 0x349 VXLAN tunnel rewrite: MTU: 0, Flags: 0x0 Encap table ID: 0, Decap table ID: 1508 Encap VNI: 500001, Decap VNI: 500001 Source VTEP: 192.168.0.2, Destination VTEP: 192.168.0.4 SMAC: 00:00:5e:00:53:38, DMAC: 00:00:5e:00:53:f2 Indirect next hop: 0x15bc4284 2101077 INH Session ID: 0x349 Protocol next hop: 192.168.0.3 Composite next hop: 0x2a627e20 129244 INH Session ID: 0x84e VXLAN tunnel rewrite: MTU: 0, Flags: 0x0 Encap table ID: 0, Decap table ID: 1508 Encap VNI: 500001, Decap VNI: 500001 Source VTEP: 192.168.0.2, Destination VTEP: 192.168.0.3 SMAC: 00:00:5e:00:53:38, DMAC: 00:00:5e:00:53:d0 Indirect next hop: 0x15bb6c04 2105498 INH Session ID: 0x84e State: ForwardingOnly Int Ext Inactive reason: Forwarding use only Age: 6:49 Metric2: 0 Validation State: unverified Task: RT Announcement bits (1): 2-KRT AS path: I (Originator) Cluster list: 192.168.2.10 Originator ID: 192.168.0.4 Communities: target:200:1 encapsulation:vxlan(0x8) router-mac:00:00:5e:00:53:f2
主干 2
user@Spine-3> show route table VRF-1 10.0.1.1 extensive VRF-1.inet.0: 53 destinations, 93 routes (53 active, 0 holddown, 0 hidden) 10.0.1.1/32 (3 entries, 1 announced) State: CalcForwarding TSI: KRT in-kernel 10.0.1.1/32 -> {list:composite(99398), composite(129244)} @EVPN Preference: 170/-101 Next hop type: Indirect, Next hop index: 0 Address: 0x16197b18 Next-hop reference count: 31 Next hop type: Router, Next hop index: 0 Next hop: 172.16.103.0 via ae3.0 Session Id: 0x0 Next hop: 172.16.103.2 via ae4.0, selected Session Id: 0x0 Protocol next hop: 192.168.0.1 Composite next hop: 0x1b8ed840 99398 INH Session ID: 0x349 VXLAN tunnel rewrite: MTU: 0, Flags: 0x0 Encap table ID: 0, Decap table ID: 1508 Encap VNI: 500001, Decap VNI: 500001 Source VTEP: 192.168.0.3, Destination VTEP: 192.168.0.1 SMAC: 00:00:5e:00:53:f2, DMAC: 00:00:5e:00:53:38 Indirect next hop: 0x15bc4284 2101077 INH Session ID: 0x349 State: Active Int Ext Age: 6:49 Metric2: 0 Validation State: unverified Task: VRF-1-EVPN-L3-context AS path: I (Originator) Cluster list: 192.168.2.10 Originator ID: 192.168.0.1 Communities: target:100:1 encapsulation:vxlan(0x8) router-mac:00:00:5e:00:53:38 Composite next hops: 1 Protocol next hop: 192.168.0.1 Composite next hop: 0x1b8ed840 99398 INH Session ID: 0x349 VXLAN tunnel rewrite: MTU: 0, Flags: 0x0 Encap table ID: 0, Decap table ID: 1508 Encap VNI: 500001, Decap VNI: 500001 Source VTEP: 192.168.0.3, Destination VTEP: 192.168.0.1 SMAC: 00:00:5e:00:53:f2, DMAC: 00:00:5e:00:53:38 Indirect next hop: 0x15bc4284 2101077 INH Session ID: 0x349 Indirect path forwarding next hops: 2 Next hop type: Router Next hop: 172.16.103.0 via ae3.0 Session Id: 0x0 Next hop: 172.16.103.2 via ae4.0 Session Id: 0x0 192.168.0.1/32 Originating RIB: inet.0 Node path count: 1 Forwarding nexthops: 2 Next hop type: Router Next hop: 172.16.103.0 via ae3.0 Session Id: 0x0 Next hop: 172.16.103.2 via ae4.0 Session Id: 0x0 EVPN Preference: 170/-101 Next hop type: Indirect, Next hop index: 0 Address: 0x2755af1c Next-hop reference count: 31 Next hop type: Router, Next hop index: 0 Next hop: 172.16.103.0 via ae3.0 Session Id: 0x0 Next hop: 172.16.103.2 via ae4.0, selected Session Id: 0x0 Protocol next hop: 192.168.0.2 Composite next hop: 0x2a627e20 129244 INH Session ID: 0x84e VXLAN tunnel rewrite: MTU: 0, Flags: 0x0 Encap table ID: 0, Decap table ID: 1508 Encap VNI: 500001, Decap VNI: 500001 Source VTEP: 192.168.0.3, Destination VTEP: 192.168.0.2 SMAC: 00:00:5e:00:53:f2, DMAC: 00:00:5e:00:53:29 Indirect next hop: 0x15bb6c04 2105498 INH Session ID: 0x84e State: Int Ext Inactive reason: Nexthop address Age: 6:49 Metric2: 0 Validation State: unverified Task: VRF-1-EVPN-L3-context AS path: I (Originator) Cluster list: 192.168.2.10 Originator ID: 192.168.0.2 Communities: target:100:1 encapsulation:vxlan(0x8) router-mac:00:00:5e:00:53:29 Composite next hops: 1 Protocol next hop: 192.168.0.2 Composite next hop: 0x2a627e20 129244 INH Session ID: 0x84e VXLAN tunnel rewrite: MTU: 0, Flags: 0x0 Encap table ID: 0, Decap table ID: 1508 Encap VNI: 500001, Decap VNI: 500001 Source VTEP: 192.168.0.3, Destination VTEP: 192.168.0.2 SMAC: 00:00:5e:00:53:f2, DMAC: 00:00:5e:00:53:29 Indirect next hop: 0x15bb6c04 2105498 INH Session ID: 0x84e Indirect path forwarding next hops: 2 Next hop type: Router Next hop: 172.16.103.0 via ae3.0 Session Id: 0x0 Next hop: 172.16.103.2 via ae4.0 Session Id: 0x0 192.168.0.3/32 Originating RIB: inet.0 Node path count: 1 Forwarding nexthops: 2 Next hop type: Router Next hop: 172.16.103.0 via ae3.0 Session Id: 0x0 Next hop: 172.16.103.2 via ae4.0 Session Id: 0x0 #Multipath Preference: 255 Next hop type: Indirect, Next hop index: 0 Address: 0xe3aa170 Next-hop reference count: 19 Next hop type: Router, Next hop index: 0 Next hop: 172.16.103.0 via ae3.0 Session Id: 0x0 Next hop: 172.16.103.2 via ae4.0 Session Id: 0x0 Next hop type: Router, Next hop index: 0 Next hop: 172.16.103.0 via ae3.0 Session Id: 0x0 Next hop: 172.16.103.2 via ae4.0, selected Session Id: 0x0 Protocol next hop: 192.168.0.1 Composite next hop: 0x1b8ed840 99398 INH Session ID: 0x349 VXLAN tunnel rewrite: MTU: 0, Flags: 0x0 Encap table ID: 0, Decap table ID: 1508 Encap VNI: 500001, Decap VNI: 500001 Source VTEP: 192.168.0.3, Destination VTEP: 192.168.0.1 SMAC: 00:00:5e:00:53:f2, DMAC: 00:00:5e:00:53:38 Indirect next hop: 0x15bc4284 2101077 INH Session ID: 0x349 Protocol next hop: 192.168.0.2 Composite next hop: 0x2a627e20 129244 INH Session ID: 0x84e VXLAN tunnel rewrite: MTU: 0, Flags: 0x0 Encap table ID: 0, Decap table ID: 1508 Encap VNI: 500001, Decap VNI: 500001 Source VTEP: 192.168.0.3, Destination VTEP: 192.168.0.2 SMAC: 00:00:5e:00:53:f2, DMAC: 00:00:5e:00:53:29 Indirect next hop: 0x15bb6c04 2105498 INH Session ID: 0x84e State: ForwardingOnly Int Ext Inactive reason: Forwarding use only Age: 6:49 Metric2: 0 Validation State: unverified Task: RT Announcement bits (1): 2-KRT AS path: I (Originator) Cluster list: 192.168.2.10 Originator ID: 192.168.0.2 Communities: target:100:1 encapsulation:vxlan(0x8) router-mac:00:00:5e:00:53:29