EVPN - How Route Types 1 & 4 Help Build The ESI

Рет қаралды 1,359

4 ай бұрын

EVPN which stands for Ethernet Virtual Private Network. This is an absolutely mammoth routing protocol! Not only that but it is very agile in its approach and the way it helps advertise to all remote devices that an ESI (Ethernet Segment Identifier) exists, how they can reach it and where they can reach it through depending on the type of traffic. Trust me,,, the type 1 (Auto Discovery) and type 4 (Ethernet Segment Route) work hand-in-hand and provide some really great functionality with one another.
In this video, part of this series, we will start learning about 2 of the 5 EVPN packet types. Specifically we'll go through Route Type 4 which is absolutely crucial whenever you have a multihomed (ESI) device. It is crucial when it comes to BUM (Broadcast, Unknown Unicast, Multicast) traffic entering the ESI from the EVPN-VXLAN network. Additionally we will cover the EVPN Route Type 1. Essentially this advertises the ESI to all other VTEP's in the network but it does a lot more than just that.
👇👇 You can find me on 👇👇
/ davidtownsend1983
=====================================================
💯 Subscribe to keep up with the best Juniper & Junos content 💯:
/ @netcademy
=====================================================
#junipernetworks #juniper #routing #evpn #network #networksolutions #telecommunications #networkengineer #technology #tech #techtalk. #datacenters #cisco #routingandswitching #junos

Пікірлер: 5

@AAA-zg7yw 3 ай бұрын

Addition of Apstra will be helpful.

@Netcademy 3 ай бұрын

This is already one of my areas to cover. I plan to go through more of the UI than underlying technology. Thoughts? Thanks for the comment 👍

@amvk99 3 ай бұрын

Good explanation 🙏

@Netcademy 3 ай бұрын

Thanks very much 😁👍

@rmeissne 25 күн бұрын

Where is the loop? This is a LACP bundle. Yes, it gets the BUM twice (if the DF concept would not be there). One copy for each LACP member port. But the server will not send out the broadcast out of the bond on which it has received two copies. From the server perspective, this is one logical interface. There is no other interface to send/loop broadcast further. Would as well be true if this would not be LACP. It is always some bond interface on the server, one logical interface. There is no bridging between the member ports. Yeah, unless you put the ports in a bridge in e.g. Linux - but that is not how the servers are configured.