<?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>quicknote on Why did IT fail</title><link>https://www.why-did-it.fail/categories/quicknote/</link><description>Recent content in quicknote 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/categories/quicknote/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>TKGS failing to authenticate with the NSX ALB (AVI)</title><link>https://www.why-did-it.fail/blog/2022-01-tkgs-avi-basicauth/</link><pubDate>Wed, 02 Feb 2022 00:00:00 +0000</pubDate><guid>https://www.why-did-it.fail/blog/2022-01-tkgs-avi-basicauth/</guid><description><![CDATA[While rebuilding my lab from scratch with
vSphere 7.0 U3c NSX Advanced (AVI) Load Balancer 21.1.3 I hit a situation where my TKGS installation would not continue with an error, it was stuck for hours:
The control plane VM &lt;ID&gt; was unable to authenticate to the load balancer (Avi - https://&lt;NSX ALB Controler IP&gt;:443/api/cluster) with the username &#39;&lt;user&gt;&#39; and the supplied password. Validate the Supervisor cluster load balancer&#39;s authentication configuration. To make a long story short, while user, password and connectivity check out it looks like the AVI defaults changed along the way.]]></description></item><item><title>VMware Workstation - vctl unable to start</title><link>https://www.why-did-it.fail/blog/2021-06-conflicting-vmrun-versions/</link><pubDate>Sat, 20 Nov 2021 00:00:00 +0000</pubDate><guid>https://www.why-did-it.fail/blog/2021-06-conflicting-vmrun-versions/</guid><description>Many thanks to Darius Davis from our engineering team who set me up on the solution.
This morning I &amp;ldquo;just wanted to spin up a container quickly&amp;rdquo;. Having a recent version of VMware workstation already on my computer, using vctl was my preferred choice (In case you missed the blog).
Problem My initial plans came to a halt as very attempt of a vctl system config or vctl system start threw an error:</description></item><item><title>LogInsight not receiving host data via cfapi</title><link>https://www.why-did-it.fail/blog/2021-05-loginsight-default-cfapi/</link><pubDate>Wed, 21 Jul 2021 00:00:00 +0000</pubDate><guid>https://www.why-did-it.fail/blog/2021-05-loginsight-default-cfapi/</guid><description><![CDATA[On a recent, fresh installation of LogInsight I observed that no data from a set of hosts was coming into the LogInsight server.
Debugging showed not issues related to the usual suspects of DNS, NTP, firewall or network which left me a bit puzzled.
I found the answer by going through the logs of the loginsight agent (usually in /var/log/loginsight-agent/liagent_&lt;date&gt;):
2021-07-20 07:08:22.319018 0x00007ff1c1a74700 &lt;trace&gt; DataController:167 | Creating cfapi transport 2021-07-20 07:08:22.]]></description></item><item><title>Tagging the vCenter (object)</title><link>https://www.why-did-it.fail/blog/2021-03-tag-vcenter-object/</link><pubDate>Tue, 16 Mar 2021 00:00:00 +0000</pubDate><guid>https://www.why-did-it.fail/blog/2021-03-tag-vcenter-object/</guid><description>I am working on enhancing my vSphere release tagging script with the ability to tag the vCenter with a human-readable release name. As shown in the screenshot, it&amp;rsquo;s easy enough in the UI.
Tags applied to the vCenter in the UI However, in PowerCLI there is no commandlet like get-vcenter. After many tries I gave up trying to force the object returned from
$global:DefaultVIServers[0] to accept any tag-related operations. Today, I had the idea of working backwards from the assigned tags with Get-TagAssignment</description></item><item><title>VMware Workstation - Updates to v15 and later breaks Minikube</title><link>https://www.why-did-it.fail/blog/2019-07-workstation-minikube/</link><pubDate>Sat, 21 Dec 2019 00:00:00 +0000</pubDate><guid>https://www.why-did-it.fail/blog/2019-07-workstation-minikube/</guid><description><![CDATA[Update from 2020-01-11 below
Life was good when I was playing around with Minikube on my private Windows Notebook until I had the (stupid) idea to use choco to update everything to the latest version. Now, Minikube would not start and notably these two packages were updated:
VMware Workstation 15 Pro: 15.5.1 build-15018445 minikube version: v1.6.1 The docker driver for VMware (docker-machine-vmware) hadn&rsquo;t changed. Problem The error suggested that &ldquo;vmrun&rdquo; isn&rsquo;t installed:]]></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>