<?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>NSX-T on Why did IT fail</title><link>https://www.why-did-it.fail/tags/nsx-t/</link><description>Recent content in NSX-T 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, 18 Sep 2023 00:00:00 +0000</lastBuildDate><atom:link href="https://www.why-did-it.fail/tags/nsx-t/index.xml" rel="self" type="application/rss+xml"/><item><title>Quicknote - Finding state information in the NSX-T Policy API</title><link>https://www.why-did-it.fail/blog/2023-02-nsxt-api-lrp-quicknote/</link><pubDate>Mon, 18 Sep 2023 00:00:00 +0000</pubDate><guid>https://www.why-did-it.fail/blog/2023-02-nsxt-api-lrp-quicknote/</guid><description>A collegue approached me with a customer request that concerned the NSX-T APIs. More specifically the customer is already using the NSX-T API in management mode but didn&amp;rsquo;t find the equivalent in the policy API.
Doing my own research, I also failed to find the API right away. This post is basicially a reminder to check on the &amp;ldquo;realized&amp;rdquo; state and get the head around the desired state of the NSX-T policy API.</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></channel></rss>