Differences

This shows you the differences between two versions of the page.

--- virtualization:evpnvxlan [2023/10/15 08:43] – jotasandoku
+++ virtualization:evpnvxlan [2025/07/17 18:06] (current) – jotasandoku
@@ Line 45: / Line 45: @@
 === Design Goals ===
-TODO
+Aggregate on the ToRs only. Use single, not dual tor.
 {{:virtualization:evpnv-goals1.png?400|}}
+If we want to grow further (ie: we run out of ports), we use multi-planar clos topologies. Full meshed 'pods' connect to planes
+Use BFD and be sure is lag and lacp aware
 ----
 === LEAF AND SPINE WITH ARISTA SWITCHES ===
 Arista Validated Designs
+  * [[https://www.itential.com/network-automation-use-cases/vxlan-bgp-evpn-deployments/|Itential]] is vendor agnostic
+  * CLOUDVISION (is ~Arista's aci)
   * [[https://www.inetsix.net/posts/avd-with-containerlab/]]
   * [[https://avd.sh/en/stable/]] and [[https://avd.arista.com/4.4/roles/eos_designs/index.html]]
@@ Line 62: / Line 69: @@
   show bgp evpn detail    # to see the evpn routes
   show bgp evpn route-type mac-ip/imet/ip-prefix    # to see the evpn rtypes 2,3,5
+Note that, in evpn-vxlan, 85% of the configuration is community settings and its route maps. Automation helps a lot here.
+Also [[https://lostintransit.se/2016/02/25/ccde-bgp-convergence/|MRAI]] is covenient to be 0. Some implementation are still 30 seconds (specially for Internet) but we don't want that in the DC
@@ Line 69: / Line 80: @@
 ----
-=== LEAF AND SPINE WITH NEXUS SWITCHES ===
+=== LEAF AND SPINE WITH CISCO ===
+  * [[https://www.itential.com/network-automation-use-cases/vxlan-bgp-evpn-deployments/|Itential]] is vendor agnostic
   * This is a guide for ACI but we don't want aci[[https://unofficialaciguide.com/2023/02/16/cisco-nexus-9364c-gx-convertible-aci-leaf-or-spine-and-discovery-tips/|External Link]]
   * But we should be able to use some aternative designs TODO
     * Automation needs to be tough in advance, [[https://netcraftsmen.com/ways-to-automate-vxlan/|External Link]]
-      * [[https://netcraftsmen.com/ways-to-automate-vxlan/|Apstra]],
       * [[https://blogs.cisco.com/developer/automatingciscoevpnfabric01|Cisco-DCNM]]
         * Allows interacting with the fabric with **ansible and terraform**
       * [[https://packetpushers.net/podcast/heavy-networking-580-multivendor-evpn-nope/|other_options]]
+  show interface nve                     ! displays NVE (VXLAN tunnel) interface status
+  show interface nve detail              ! shows detailed info: packet counters, drops, state
+  show nve vni                           ! shows configured VNIs, their state, and bindings
+  show nve peers                         ! displays remote VTEPs (VXLAN Tunnel Endpoints)
+  show mac address-table dynamic         ! lists learned MACs, including VXLAN-related ones
+  show ip route vrf <VRF>                ! checks reachability within a VXLAN-associated VRF
+  show arp vrf <VRF>                     ! shows ARP table entries for a specific VRF
+  show l2route evpn mac all              ! shows learned MACs via EVPN control plane
+  show l2route evpn mac-ip all           ! includes MAC and IP bindings (Type 2 routes)
+  show bgp l2vpn evpn                    ! general overview of BGP EVPN routes
+  show bgp l2vpn evpn route-type mac-ip  ! EVPN Type 2: MAC + IP advertisement
+  show bgp l2vpn evpn route-type imet    ! EVPN Type 3: multicast replication group
+  show bgp l2vpn evpn route-type prefix  ! EVPN Type 5: IP prefix route info
 == Models ==
@@ Line 83: / Line 113: @@
+----
+Juniper:
+      * Mist for evpn TODO
+      * [[https://netcraftsmen.com/ways-to-automate-vxlan/|Apstra]]
+----
+Cumulus:
+  * Find their automation platform and mix it with best ansible Jinja templates

dokucama

User Tools

Site Tools

Differences

Page Tools