From f971f0d512a2e202731733e4034cfb4d938ee9cd Mon Sep 17 00:00:00 2001 From: Markus Vahlenkamp Date: Thu, 1 Aug 2024 10:18:08 +0200 Subject: [PATCH] fix typo (#160) --- docs/tutorials/l3evpn/rt5-only/index.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/tutorials/l3evpn/rt5-only/index.md b/docs/tutorials/l3evpn/rt5-only/index.md index 8aafe2c2..0dd6a0f9 100644 --- a/docs/tutorials/l3evpn/rt5-only/index.md +++ b/docs/tutorials/l3evpn/rt5-only/index.md @@ -33,14 +33,14 @@ As part of this tutorial we will go over two L3 EVPN scenarios. First, we will d
Directly attached L3 clients
-The second scenario will demonstrate how to connect CE devices of Tenant 2 that establish a BGP session with the leaf devices to exchange IP prefixes. The BGP EVPN will make sure that the client prefixes are distributed to the to the participants of the same L3 EVPN service of this tenant. +The second scenario will demonstrate how to connect CE devices of Tenant 2 that establish a BGP session with the leaf devices to exchange IP prefixes. The BGP EVPN will make sure that the client prefixes are distributed to the participants of the same L3 EVPN service of this tenant.
BGP-enabled CE clients
-From the data plane perspective we will be using VXLAN tunnels to transport the encapsulated tenant' packets through the IP fabric. +From the data plane perspective we will be using VXLAN tunnels to transport the encapsulated tenant packets through the IP fabric. As part of this tutorial we will configure the SR Linux-based DC fabric underlay with BGP Unnumbered. Then we will setup the overlay routing using iBGP with EVPN address family and proceed with the creation of an L3 EVPN service for the two tenants of our fabric.