summaryrefslogtreecommitdiff
path: root/docs/configexamples/autotest/L3VPN_EVPN/L3VPN_EVPN.rst
diff options
context:
space:
mode:
Diffstat (limited to 'docs/configexamples/autotest/L3VPN_EVPN/L3VPN_EVPN.rst')
-rw-r--r--docs/configexamples/autotest/L3VPN_EVPN/L3VPN_EVPN.rst28
1 files changed, 14 insertions, 14 deletions
diff --git a/docs/configexamples/autotest/L3VPN_EVPN/L3VPN_EVPN.rst b/docs/configexamples/autotest/L3VPN_EVPN/L3VPN_EVPN.rst
index 0abe7a5b..2a528852 100644
--- a/docs/configexamples/autotest/L3VPN_EVPN/L3VPN_EVPN.rst
+++ b/docs/configexamples/autotest/L3VPN_EVPN/L3VPN_EVPN.rst
@@ -3,8 +3,8 @@
L3VPN EVPN with VyOS
####################
-| Testdate: 2023-02-24
-| Version: vyos-1.4-rolling-202302150317
+| Testdate: 2023-05-11
+| Version: 1.4-rolling-202305100734
I spun up a new lab in EVE-NG, which represents this as the
"Foo Bar - Service Provider Inc." that has 3 points of presence (PoP) in random
@@ -160,7 +160,7 @@ Show routes for all VRFs
VRF blue:
C>* 10.1.1.0/24 is directly connected, br2000, 00:01:13
- B>* 10.1.2.0/24 [200/0] via 172.29.255.2, br2000 onlink, weight 1, 00:00:54
+ B>* 10.1.2.0/24 [200/0] via 172.29.255.2, br2000 onlink, weight 1, 00:00:49
B>* 10.1.3.0/24 [200/0] via 172.29.255.3, br2000 onlink, weight 1, 00:00:49
VRF default:
@@ -171,7 +171,7 @@ Show routes for all VRFs
O 172.29.0.6/31 [110/1] is directly connected, eth3, weight 1, 00:01:09
C>* 172.29.0.6/31 is directly connected, eth3, 00:01:12
C>* 172.29.255.1/32 is directly connected, dum0, 00:01:14
- O>* 172.29.255.2/32 [110/20] via 172.29.0.3, eth1, weight 1, 00:00:55
+ O>* 172.29.255.2/32 [110/20] via 172.29.0.3, eth1, weight 1, 00:00:50
O>* 172.29.255.3/32 [110/20] via 172.29.0.7, eth3, weight 1, 00:00:45
VRF green:
@@ -179,12 +179,12 @@ Show routes for all VRFs
B>* 10.3.3.0/24 [200/0] via 172.29.255.3, br4000 onlink, weight 1, 00:00:49
VRF mgmt:
- S>* 0.0.0.0/0 [210/0] via 10.100.0.1, eth0, weight 1, 00:01:43
- C>* 10.100.0.0/24 is directly connected, eth0, 00:01:44
+ S>* 0.0.0.0/0 [210/0] via 10.100.0.1, eth0, weight 1, 00:01:45
+ C>* 10.100.0.0/24 is directly connected, eth0, 00:01:45
VRF red:
- C>* 10.2.1.0/24 is directly connected, br3000, 00:01:12
- B>* 10.2.2.0/24 [200/0] via 172.29.255.2, br3000 onlink, weight 1, 00:00:54
+ C>* 10.2.1.0/24 is directly connected, br3000, 00:01:13
+ B>* 10.2.2.0/24 [200/0] via 172.29.255.2, br3000 onlink, weight 1, 00:00:49
Information about Ethernet Virtual Private Networks
@@ -205,19 +205,19 @@ Information about Ethernet Virtual Private Networks
Route Distinguisher: 10.1.1.1:5
*> [5]:[0]:[24]:[10.1.1.0]
172.29.255.1 0 32768 ?
- ET:8 RT:100:2000 Rmac:16:b7:8d:21:46:fb
+ ET:8 RT:100:2000 Rmac:4e:bb:3c:ba:bd:a6
Route Distinguisher: 10.1.2.1:4
*>i[5]:[0]:[24]:[10.1.2.0]
172.29.255.2 0 100 0 ?
- RT:100:2000 ET:8 Rmac:50:00:00:02:00:04
+ RT:100:2000 ET:8 Rmac:26:07:da:eb:fc:ea
Route Distinguisher: 10.1.3.1:4
*>i[5]:[0]:[24]:[10.1.3.0]
172.29.255.3 0 100 0 ?
- RT:100:2000 ET:8 Rmac:50:00:00:03:00:04
+ RT:100:2000 ET:8 Rmac:26:98:28:24:6e:54
Route Distinguisher: 10.2.1.1:6
*> [5]:[0]:[24]:[10.2.1.0]
172.29.255.1 0 32768 ?
- ET:8 RT:100:3000 Rmac:42:02:20:9d:0b:a8
+ ET:8 RT:100:3000 Rmac:50:00:00:01:00:05
Route Distinguisher: 10.2.2.1:5
*>i[5]:[0]:[24]:[10.2.2.0]
172.29.255.2 0 100 0 ?
@@ -229,7 +229,7 @@ Information about Ethernet Virtual Private Networks
Route Distinguisher: 10.3.3.1:6
*>i[5]:[0]:[24]:[10.3.3.0]
172.29.255.3 0 100 0 ?
- RT:100:4000 ET:8 Rmac:50:00:00:03:00:06
+ RT:100:4000 ET:8 Rmac:06:32:9d:22:55:8a
Displayed 7 out of 7 total prefixes
@@ -248,4 +248,4 @@ the EVPN network we need to run
172.29.255.1 (metric 20) from 172.29.255.1 (172.29.255.1)
Origin incomplete, metric 0, localpref 100, valid, internal, best (First path received)
Extended Community: RT:100:4000 ET:8 Rmac:50:00:00:01:00:06
- Last update: Fri Feb 24 12:00:32 2023
+ Last update: Thu May 11 13:31:13 2023