initial

presentation/presentation.md

@@ -0,0 +1,78 @@
+---
+theme: jobs
+_class: lead
+size: 16:9
+paginate: true
+#footer: "Felix EVPN Demo"
+marp: true
+backgroundColor: #fff
+backgroundImage: url('https://marp.app/assets/hero-background.svg')
+---
+<!-- _backgroundImage: url('https://marp.app/assets/hero-background.svg') -->
+# **EVPN Demo**
+
+2024-07-17 Munich
+Felix Schüren
+
+---
+![bg left:66% contain](./img/felix_evpn_design_2.drawio.png)
+## lab diagram reference
+<span style="color: darkgrey; font-size: 0.4em">Lo0 numbering from left to right, starting at ```.1```</span>
+<span style="color: darkgrey; font-size: 0.4em">management via hostname, prefix is ```clab-f3-```</span>
+<style scoped>
+ul {
+  font-size: smaller;
+}
+</style>
+- Spines
+  - 10.0.255/24
+- Leaves
+  - 10.0.254/24
+
+---
+<!-- _backgroundColor: white -->
+<!-- _backgroundImage: "" -->
+<style scoped>
+ul {
+  font-size: smaller;
+}
+</style>
+![bg left:33% contain](./img/felix_evpn_design_2.drawio.png)
+- basic Spine/Leaf architecture
+- border/service leaf
+  - keep spine config as simple as possible
+  - help humans
+- eBGP underlay
+  - I come from a service provider background, BGP is second nature
+- bgp unnumbered instead of /31
+  - easier debugging of BGP sessions etc as you can see the Interface name in BGP :)
+  - no IPAM for underlay transfer links
+<!-- Only scenario where it might make sense to use IS-IS or OSPF in the underlay is if there are different teams responsible to run underlay/core transport vs overlay/services/end customer needs-->
+--- 
+![bg](./img/bgp-unnumbered-playbook-excerpt.png)
+![bg](./img/bgp-unnumbered-example-eos-cfg.png)
+
+---
+![bg contain](./img/bgp-unnumbered-show-interface-mapping.png)
+![bg contain](./img/bgp-unnumbered-leaf3-ping.png)
+
+---
+MLAG: querlink noetig, aber weniger EVPN-Routen, vendor-spezifisch
+EVPN-Multihoming: kein querlink, aber mehr Routen, ...
+
+underlay/overlay via AVD fertigmachen
+
+service deployment via ansible oder so (VLANs, VNIs, ...)
+
+v4-less underlay? 5549 nexthop rewriting mit interface-peering, damit baut sich ein neues leaf quasi umsonst
+
+weitere leaf(s) dazubauen im Betrieb
+
+eAPI, eAPI-Docs raussuchen
+
+show commands rund um evpn (welche mac wo, aktueller Zustand, etc)
+
+
+tmux auf einem arista-switch installieren und casual anmoderieren
+
+habe mir ueberlegt, mal eben prometheus/loki etc drumrumzubauen, aber Zeit, ...