Learn EVPN Route Type 2 and Type 3

Sdílet
Vložit
  • čas přidán 6. 09. 2024
  • EVPN & VXLAN which stands for Ethernet Virtual Private Network and Virtual Extensible Local Are Network. These are two independent protocols which, when working together, offer a great deal of routing capabilities to service provider, data center and enterprise networks.
    In this video, part 3 of this series, we will start learning about 2 of the 5 EVPN packet types. Specifically we'll go through Route Type 2 which is used for unicast MAC/ IP advertisement as well Route Type 3 Inclusive Multicast. As the name implies this is for 'handling' multicast traffic within an EVPN network, and a bit more.
    👇👇 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

Komentáře • 15

  • @kris___5655
    @kris___5655 Před měsícem +1

    Thank you for explaining in detail

    • @Netcademy
      @Netcademy  Před měsícem

      @@kris___5655 you’re welcome and thank you for your support

  • @jonallan121
    @jonallan121 Před 20 dny +2

    Just recently came across your material when looking for some videos to help some colleagues. This is a Great series !
    Just one observation… ingress replication is unicast so we wouldn’t expect it to be sending to both spines? It would still send the same amount of bytes as multicast?
    The efficiency with multicast is that only those leaf switches with that vlan/Vxlan would require a copy.
    Correct me if I assume wrong though, please?
    Keep up the amazing content!

    • @Netcademy
      @Netcademy  Před 16 dny +1

      Ooh good question! Ingress replication is making a copy of the multicast traffic and then, as you said, sending it to only interested VTEPs which have advertised their interest via the RT3. I do believe it would send this copy via both spine 1 and spine 2 though as if you look at the IGMP route types (6-8) which I haven't covered; then a receiving leaf device would receive copies of the unicast (copy of multicast traffic) from both spines. So whilst it is more efficient in my opinion it's not 100% efficient. Thanks for the kind words and support

  • @dineshstill7573
    @dineshstill7573 Před 4 dny +1

    Hi David. Type 3 is used for update BUM traffic. While explaining EVPN benefits in previous video, we understand that leafs will be configured as DF to better handle BUM traffic in order to avoid potential loop. But in EVPN RT3 there is nothing about DF. How is DF configured? Does it have anything to do with RT3 or it has got nothing to do with it? Or both are different? TIA

    • @Netcademy
      @Netcademy  Před 4 dny +1

      @@dineshstill7573 Hi, so the RT3 is essentially advertising “interested” & connected hosts/ tenants for BUM traffic. The RT4 is for the election of a DF and it does so in a round-robin fashion per vlan. So if you have leaf 1 & leaf 2 connected to server A for vlans 1-10; it could look like:
      Leaf 1 as DF for vlans 1,3,5,7,9
      Leaf 2 as DF for vlans 2,4,6,8,10
      The actual election mechanism I’ve not researched but I trust it works 😂👍
      Please note RT6,7 & 8 are also available but specifically for multicast traffic although I’ve not covered these yet.
      Thanks for the support

    • @dineshstill7573
      @dineshstill7573 Před 3 dny

      @@Netcademy Thank you for the explanation. I have posted this question quite early without completing your video on RT4 which is all about DF. I quite sometimes post my questions without completing whole things. Silly me but thanks for the reply. Thanks.

  • @cankaranisoner9208
    @cankaranisoner9208 Před 3 měsíci +1

    This is best series for EVPN-VXLAN bro. Like bread and butter :D

    • @Netcademy
      @Netcademy  Před 3 měsíci

      Thanks very much for the positive feedback

  • @mahikris9625
    @mahikris9625 Před 5 měsíci +2

    Excellent explanation .. better if you can show some packet capture added with this .. but great work thank you so much ...

    • @Netcademy
      @Netcademy  Před 5 měsíci

      Thanks so much for the positive feedback. My approach is to do the theory first and then in the labs, in verification phase, to do packet captures 👍 So stay tuned as videos on deployment, configuration and verification are coming soon….

  • @coriolanus14
    @coriolanus14 Před 3 měsíci +1

    HI, thanks for sharing this. Btw, are you using a L3 etherchannel to connect the host to Leaf2 and Leaf3? If not it shouldn't work, unless you connect Leaf2 and 3 with a mlag,vss,vpc...

    • @Netcademy
      @Netcademy  Před 3 měsíci

      Hi, you are absolutely correct! It would not work but I have seen cumulus being used to connect a host/ server to different leafs but honestly I don't know the configuration. In this video the video wasn't about the hosts/ servers. The connection is there just for illustrative purposes, nothing more. Thanks

  • @faridyc344
    @faridyc344 Před 3 měsíci +1

    Thanks for this great video , just perhaps a correction concerning mp-bgp evpn safi value (70)