<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/"><channel><title>network on Why did IT fail</title><link>https://www.why-did-it.fail/tags/network/</link><description>Recent content in network on Why did IT fail</description><generator>Hugo -- gohugo.io</generator><language>en</language><copyright>Copyright © 2026 Dominik Textoris (formerly Zorgnotti). All Rights Reserved.</copyright><lastBuildDate>Mon, 07 Oct 2019 00:00:00 +0000</lastBuildDate><atom:link href="https://www.why-did-it.fail/tags/network/index.xml" rel="self" type="application/rss+xml"/><item><title>An overview of the vSphere MAC address space</title><link>https://www.why-did-it.fail/blog/2019-05-vsphere-mac-address-space/</link><pubDate>Mon, 07 Oct 2019 00:00:00 +0000</pubDate><guid>https://www.why-did-it.fail/blog/2019-05-vsphere-mac-address-space/</guid><description>Recently another TAM requested some infos on this topic in VMware’s slack, finally giving me the push to publish as I had this post for ages in my drafts. Given, it is somewhat of an edge case for only a hand full of customers and the problem itself is not new but here is my take. As always please do your own research before you put this untested into production.</description></item><item><title>The edge in NSX-v versus NSX-T</title><link>https://www.why-did-it.fail/blog/2019-04-nsx-edge-in-nsx-v-vs-nsx-t/</link><pubDate>Fri, 06 Sep 2019 00:00:00 +0000</pubDate><guid>https://www.why-did-it.fail/blog/2019-04-nsx-edge-in-nsx-v-vs-nsx-t/</guid><description>While bringing myself up-to-date with NSX-T I struggled with the terminology in relation to my existing NSX-v knowledge. There are quite a few awesome blog posts around -v or -T and I am trying to compare the &amp;ldquo;edge&amp;rdquo; at a high level.
I hesitated to make a public post out of it since I am myself quite new to NSX-T and my post may not be 100% correct, but then figured that I can just learn from the feedback.</description></item><item><title>Route-based IKEv2 site-to-site VPN between Azure and an NSX-v ESG</title><link>https://www.why-did-it.fail/blog/2018-01-nsxv-azure-vpn/</link><pubDate>Wed, 21 Mar 2018 00:00:00 +0000</pubDate><guid>https://www.why-did-it.fail/blog/2018-01-nsxv-azure-vpn/</guid><description>Just a quick drop of notes on how to configure this if anyone else needs it.
You probably searched the net and found tons of howtos on policy-based VPNs. However, I needed to do a route-based VPN my Azure resources with multi-devices and you can have only a single VPN-policy on a Gateway. Infos on IPSEC settings where taken from the Azure documentation - please make sure you read the fields marked important.</description><enclosure url="https://www.why-did-it.fail/blog/2018-01-nsxv-azure-vpn/feature.png" length="24449" type="image/png"/></item></channel></rss>