Skip to content

Commit 4eb84c9

Browse files
hellthellt
authored
update for sr linux 25.10.1 (#199)
1 parent 8b657a6 commit 4eb84c9

File tree

2 files changed

+7
-7
lines changed

2 files changed

+7
-7
lines changed

‎docs/tutorials/l3evpn/rt5-only/index.md‎

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -8,12 +8,12 @@ tags:
88
| | |
99
| --------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
1010
| **Tutorial name** | RT5-only (aka Interface-less) L3 EVPN-VXLAN with SR Linux |
11-
| **Lab components** | 3 SR Linux nodes, 2 [FRR](https://frrouting.org), 2 Alpine nodes |
11+
| **Lab components** | 3x [SR Linux](https://github.com/nokia/srlinux-container-image) nodes, 2x [FRR](https://frrouting.org) nodes, 2 Alpine nodes |
1212
| **Resource requirements** | :fontawesome-solid-microchip: 2vCPU <br/>:fontawesome-solid-memory: 8 GB |
1313
| **Lab Repo** | [srl-rt5-l3evpn-basics-lab][lab-repo] |
1414
| **Packet captures** | [EVPN IP Prefix routes exchange][capture-evpn-rt5] |
1515
| **Main ref documents** | [RFC 7432 - BGP MPLS-Based Ethernet VPN](https://datatracker.ietf.org/doc/html/rfc7432)<br/>[RFC 8365 - A Network Virtualization Overlay Solution Using Ethernet VPN (EVPN)](https://datatracker.ietf.org/doc/html/rfc8365)<br/>[RFC 9136 - IP Prefix Advertisement in Ethernet VPN (EVPN)](https://datatracker.ietf.org/doc/html/rfc9136)<br/>[Nokia 7220 SR Linux Advanced Solutions Guide][adv-sol-guide-evpn-l3]<br/>[Nokia 7220 SR Linux EVPN-VXLAN Guide][evpn-vxlan-guide] |
16-
| **Version information**[^1] | [`containerlab:v0.56.0`][clab-install], [`srlinux:24.3.3`][srlinux-container], [`frr:9.0.2`][frr-container] [`docker-ce:26.1.4`][docker-install] |
16+
| **Version information**[^1] | [`containerlab:v0.71.1`][clab-install], [`srlinux:25.10.1`][srlinux-container], [`frr:9.0.2`][frr-container] [`docker-ce:26.1.4`][docker-install] |
1717
| **Authors** | Korhan Kayhan [:material-linkedin:][kkayhan-linkedin]<br>Roman Dodin [:material-linkedin:][rd-linkedin] [:material-twitter:][rd-twitter]<br/>and reviewers[^3] |
1818

1919
While EVPN originally emerged as a Layer 2 VPN technology to overcome VPLS limitations, it has since evolved to become a unified control plane for many services, Layer 3 VPN included. Founded upon the BGP protocol, EVPN has [lots of flexibility and features](https://www.nokia.com/networks/ethernet-vpn/) to become a one-stop-shop for all VPN services in various network deployments, but especially fit for the IP fabrics.
@@ -51,7 +51,7 @@ To let you follow along the configuration steps of this tutorial we created [a l
5151
/// tab | Locally
5252

5353
```
54-
sudo containerlab deploy -c -t srl-labs/srl-l3evpn-basics-lab
54+
containerlab deploy -c -t srl-labs/srl-l3evpn-basics-lab
5555
```
5656

5757
Containerlab will pull the git repo to your current working directory and start deploying the lab.

‎docs/tutorials/l3evpn/rt5-only/underlay.md‎

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -309,7 +309,7 @@ commit now
309309

310310
## eBGP Unnumbered for Underlay Routing
311311

312-
Now we will set up the eBGP routing protocol that will be used for exchang loopback addresses throughout the fabric. These loopbacks will be used to set up iBGP EVPN peerings, which we will cover in the following chapter.
312+
Now we will set up the eBGP routing protocol that will be used for exchange loopback addresses throughout the fabric. These loopbacks will be used to set up iBGP EVPN peerings, which we will cover in the following chapter.
313313

314314
The eBGP setup is done according to the following diagram:
315315

@@ -357,7 +357,7 @@ Here is a breakdown of the configuration steps done on `leaf1` and you will find
357357
Next, we will create a routing policy that matches on the prefix set we just created and accepts them.
358358
359359
```{.srl .no-select}
360-
set / routing-policy policy system-loopbacks-policy statement 1 match prefix-set system-loopbacks
360+
set / routing-policy policy system-loopbacks-policy statement 1 match prefix prefix-set system-loopbacks
361361
set / routing-policy policy system-loopbacks-policy statement 1 action policy-result accept
362362
```
363363
@@ -366,8 +366,8 @@ Here is a breakdown of the configuration steps done on `leaf1` and you will find
366366
367367
```{.srl .no-select}
368368
set / network-instance default protocols bgp group underlay
369-
set / network-instance default protocols bgp group underlay export-policy system-loopbacks-policy
370-
set / network-instance default protocols bgp group underlay import-policy system-loopbacks-policy
369+
set / network-instance default protocols bgp group underlay export-policy [ system-loopbacks-policy ]
370+
set / network-instance default protocols bgp group underlay import-policy [ system-loopbacks-policy ]
371371
```
372372
373373
5. **Enable `ipv4-unicast` Address Family**

0 commit comments

Comments
 (0)