Mvendor-VXLAN-lab - Revision history

PierreLancastre at 13:38, 29 October 2021

2021-10-29T13:38:22Z

PierreLancastre at 13:38, 29 October 2021

2021-10-29T13:38:05Z

PierreLancastre at 13:35, 29 October 2021

2021-10-29T13:35:59Z

PierreLancastre at 13:26, 29 October 2021

2021-10-29T13:26:26Z

PierreLancastre at 13:21, 29 October 2021

2021-10-29T13:21:49Z

Show changes

PierreLancastre: Created page with "
= Useful Infos = == Lab Target == The target of the lab is to build a multivendor lab, with an architecture reflecting those deployed in customers' environ..."

2021-10-29T13:07:44Z

Created page with "<div> = Useful Infos = == <span>Lab Target</span> == The target of the lab is to build a multivendor lab, with an architecture reflecting those deployed in customers' environ..."

New page

<div>
= Useful Infos =

== <span>Lab Target</span> ==
The target of the lab is to build a multivendor lab, with an architecture reflecting those deployed in customers' environment?.

This lab will be constructed in several steps, starting in a virtual version, followed by a physical one.

For the moment, we are working on typical "modern" datacenters implementations :<div></div>

* EVPN/VXLAN layer 2 only
* EVPN/VXLAN layer 2 + layer 3 per rack (ou layer 3 anycast gw)
* EVPN en MPLS en L2/L3
* "standard" IP Fabric

but there are also labs for SP customers running LDP/OSPF or SR/ISIS for EVPN/L3VPN services.

One goal is to spot/identify the (in)compatibilities between the different vendors, and build the different configurations to be able to provide "ready-to-deploy" setup. In add, working permits to securize the project of vendors migration / NOS migration (ex : EOS to Sonic for Arista).

Once the different setup consolidated, we can begin an automation work, within tools like ansible/saltstack/other, in parallel with the implementation of propietary vendor tools (like Arista Cloudvision).

The idea behing of all of that is to gain a good knwoledge of the products, wihtou necessarily being expert, but ideally with front-desk-setup, reflecting "the real life". In add, for me a work has to be led to implement a ZTP/ material validation setup, in order to improve/securize at most the deployment/assets management.

Now, the more vendors we have the best it is. We have to sollicitate the different vendors and communicate about the different setup in a "high level manner", without taking publicly position. The idea is to stay neutral whatever happens.

== <span>Host specifications</span> ==
For the moment, I'm working on an OVH dedicated server.

<span>Commercial reference :</span> RISE-LE-1 - Intel Xeon E5-1660v3 - 64GB DDR4 ECC 2133MHz - 2x HDD SATA 4TB Datacenter Class Soft RA

Système (OS) VMware ESXi 6.7 U3

<span>Software versions :</span>

All network devices instances run within EVE-NG software , here EVE-NG 2.0.3-110 The software has been installed with an OVF available on the website https://www.eve-ng.net/

Regarding the vendors images, they have been downloaded on the vendors portals (or provided by them directly). For Juniper you need a "special" account to be allowed to download the images, on Arista it's free even you are a simple user. For Nokia I don't know, but I suppose it's just in deal contexts since the licences are mandatory and need to be generated by Nokia guys.<div></div>

* Arista : veos-4.24.1F
* Juniper MX : 20.1R1.11-limited-VCP
* Juniper QFX : 18.4R1.8
* Juniper SRX : next-gen 20.1R1.11
* Nokia : 7750 VSR-I timos-20.7R1

<span>Password used :</span><div></div>

* Nokia : admin:nokia2020
* Arista : admin: <-- no password
* Juniper : root:Juniper
* Cumulus : cumulus:CumulusLinux!
</div>

← Older revision		Revision as of 13:38, 29 October 2021
Line 7:		Line 7:

	Analyzes and conclusions are not an absolute truth. So if you have remarks/advices, please share :)		Analyzes and conclusions are not an absolute truth. So if you have remarks/advices, please share :)
−

	== <span>Lab Target</span> ==		== <span>Lab Target</span> ==

@@ Line 61: / Line 61: @@
 * Overlay is managed by eBGP multihop sessions between loopback IPs. Well think to only activate EVPN family for those sessions + define the upsate-source IP (loopback IP)
-= Configurations + diagrams =
+== Configurations + diagrams ==
 [[File:Lab-mvendor-vxlan-l2-nok-ars-jun-cum.jpeg]]
@@ Line 71: / Line 71: @@
-== Note ==
+== Observations ==
 Juniper vQFX supports only vlan-aware-bundle service in VXLAN (one EVPN instance for N VLAN)
@@ Line 254: / Line 254: @@
 So, since no type 2 routes is received, the packets from Arista to Nokia are processed as BUM (so sent to all VTEP from the VXLAN instance).
-Below the sources of different versions of the lab :
+Some tests wee done with L3 routing, details coming

@@ Line 3: / Line 3: @@
 These labs were realized end of 2020. So different behaviors could be observed today with last releases, in a good or a bad way.
 == <span>Lab Target</span> ==
@@ Line 57: / Line 62: @@
 = Configurations + diagrams =

@@ Line 2: / Line 2: @@
 = Introduction =
-This lab was realized early 2021. So different behaviors could be observed today with last releases, in a good or a bad way.
+These labs were realized end of 2020. So different behaviors could be observed today with last releases, in a good or a bad way.
 == <span>Lab Target</span> ==
@@ Line 22: / Line 22: @@
 System : VMware ESXi 6.7 U3
-Software versions :<
+Software versions :
 All network devices instances run within EVE-NG software , here EVE-NG 2.0.3-110 The software has been installed with an OVF available on the website https://www.eve-ng.net/
@@ Line 56: / Line 56: @@
 * Overlay is managed by eBGP multihop sessions between loopback IPs. Well think to only activate EVPN family for those sessions + define the upsate-source IP (loopback IP)
-= LAB DIAGRAM =
+= Configurations + diagrams =
 == Note ==

Mvendor-VXLAN-lab - Revision history

PierreLancastre at 13:38, 29 October 2021

PierreLancastre at 13:38, 29 October 2021

PierreLancastre at 13:35, 29 October 2021

PierreLancastre at 13:26, 29 October 2021

PierreLancastre at 13:21, 29 October 2021

PierreLancastre: Created page with " = Useful Infos = == Lab Target == The target of the lab is to build a multivendor lab, with an architecture reflecting those deployed in customers' environ..."

PierreLancastre: Created page with "
= Useful Infos = == Lab Target == The target of the lab is to build a multivendor lab, with an architecture reflecting those deployed in customers' environ..."