rutgerblom.com

geneve

  • BGP EVPN Between NSX And VyOS – Part 2

    Welcome back! In Part 1 we configured and prepared NSX to participate in a BGP EVPN control and data plane. In this part we continue with configuration of the VyOS router. Once both NSX and VyOS are configured we’ll verify… Continue reading

    BGP EVPN Between NSX And VyOS – Part 2

  • BGP EVPN Between NSX And VyOS – Part 1

    Recently I’ve been looking into setting up BGP EVPN between VMware NSX and VyOS router. I’m using VyOS quite a lot in labs and demos, often as the counterpart to a Tier-0 gateway, and wanted to find out if it… Continue reading

    BGP EVPN Between NSX And VyOS – Part 1

  • HCX Your Way To NSX-T Overlay

    Happy New Year! 🙂 In the last two posts we had a look at two different methods for extending VLANs to NSX-T overlay. In the first post we configured a bridge which works well in scenarios where we the source… Continue reading

  • VPN Your Way To NSX-T Overlay

    In the previous article we had a look at how VLAN-connected workloads were migrated to NSX-T overlay by setting up a bridge between VLANs and NSX-T overlay segments. This works well in scenarios where layer 2 adjacency between source and… Continue reading

  • Bridge Your Way To NSX-T Overlay

    Organizations implementing NSX-T overlay have several options when it comes to migrating existing VLAN-connected workloads to NSX-T overlay segments. Common methods include re-IP’ing or re-deploying workloads to a new IP space allocated to NSX-T logical networking. It gives the workload… Continue reading

  • NSX-T Data Path Visibility – Part 3

    Hi and welcome back. We’re looking into the NSX-T data path and investigating different points at which we can capture network traffic. You may remember from part one that virtual machine “app01” (172.16.2.50) is trying to ping another virtual machine called “web01”… Continue reading

  • NSX-T Data Path Visibility – Part 2

    Welcome back! We’re looking at how to gain visibility at different points in the NSX-T data path. You may remember from part one that virtual machine “app01” (172.16.2.50) is trying to ping another virtual machine called “web01” (172.16.1.53), but it’s… Continue reading