<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Vmware on Explosive Cloud</title>
    <link>https://explosive.cloud/tags/vmware/</link>
    <description>Recent content in Vmware on Explosive Cloud</description>
    <generator>Hugo</generator>
    <language>en-US</language>
    <lastBuildDate>Wed, 08 May 2024 19:05:39 +0000</lastBuildDate>
    <atom:link href="https://explosive.cloud/tags/vmware/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>NSX Upgrade Failure</title>
      <link>https://explosive.cloud/nsx-upgrade-failure/</link>
      <pubDate>Wed, 08 May 2024 19:05:39 +0000</pubDate>
      <guid>https://explosive.cloud/nsx-upgrade-failure/</guid>
      <description>&lt;h2 id=&#34;issue&#34;&gt;Issue&lt;/h2&gt;&#xA;&lt;p&gt;When upgrading our one production NSX 4.1.2.1 environment I ran into an interesting error trying to upgrade our Bare Metal Tier 0 nodes.&lt;/p&gt;&#xA;&lt;pre tabindex=&#34;0&#34;&gt;&lt;code&gt;Prepare edge upgrade bundle https://10.10.0.1/repository/4.1.2.3.0.23382408/Edge/nub/VMware-NSX-edge-4.1.2.3.0.23382424.nub failed on edge TransportNode UUID: clientType EDGE , target edge fabric node id UUID, return status Download and verify bundle failed with msg: Checking upgrade bundle /var/vmware/nsx/file-store/VMware-NSX-edge-4.1.2.3.0.23382424.nub contents Verifying bundle VMware-NSX-edge-4.1.2.3.0.23382424.bundle with signature VMware-NSX-edge-4.1.2.3.0.23382424.bundle.sig Failed to verify bundle: [&amp;#39;gpg&amp;#39;, &amp;#39;--homedir&amp;#39;, &amp;#39;/root/.gnupg&amp;#39;, &amp;#39;--verify&amp;#39;, &amp;#39;/tmp/tmpc75b6zcx/VMware-NSX-edge-4.1.2.3.0.23382424.bundle.sig&amp;#39;, &amp;#39;/tmp/tmpc75b6zcx/VMware-NSX-edge-4.1.2.3.0.23382424.bundle&amp;#39;] returned 2: b&amp;#34;gpg: Signature made Mon 26 Feb 2024 10:40:20 PM MST\ngpg: using RSA key E51BDAAAFDF4DC95\ngpg: Can&amp;#39;t check signature: No public key\n&amp;#34; .&#xA;&lt;/code&gt;&lt;/pre&gt;&lt;p&gt;However, my T1 edge nodes (which were set to upgrade first) had no problem with the same upgrade package. What a mystery!&lt;/p&gt;</description>
    </item>
    <item>
      <title>VMware Cloud Director - VAMI Backup Failure</title>
      <link>https://explosive.cloud/vmware-cloud-director-vami-backup/</link>
      <pubDate>Fri, 26 Jan 2024 16:26:20 +0000</pubDate>
      <guid>https://explosive.cloud/vmware-cloud-director-vami-backup/</guid>
      <description>&lt;h2 id=&#34;vmware-cloud-director-vami-backup&#34;&gt;VMware Cloud Director VAMI Backup&lt;/h2&gt;&#xA;&lt;p&gt;You may find yourself in a situation where you want to take a VMware Cloud Director VAMI Backup, but run into the error: Unable to create backup: A failure occured while creating the backup on the primary.&lt;/p&gt;</description>
    </item>
    <item>
      <title>NSX - Node with the same IP already exists</title>
      <link>https://explosive.cloud/nsx-same-ip-already-exists/</link>
      <pubDate>Fri, 29 Sep 2023 14:29:07 +0000</pubDate>
      <guid>https://explosive.cloud/nsx-same-ip-already-exists/</guid>
      <description>&lt;h2 id=&#34;versions-for-posterity&#34;&gt;Versions, for posterity&lt;/h2&gt;&#xA;&lt;p&gt;vCenter 8.0.1 - build 22088981&lt;br&gt;&#xA;ESXi - 22088125&lt;br&gt;&#xA;NSX - 4.1.0.2&lt;/p&gt;&#xA;&lt;h2 id=&#34;backstory&#34;&gt;Backstory&lt;/h2&gt;&#xA;&lt;p&gt;I recently came across a rather interesting issue. Long story short, I needed to rebuild one of my NSX-prepared hosts. I put the host in maintenance mode, pulled it out of my NSX cluster, disconnected the host, and removed it from vCenter.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Configuring VMware NSX Backups Using SSH Keys</title>
      <link>https://explosive.cloud/configuring-vmware-nsx-backups-using-ssh-keys/</link>
      <pubDate>Thu, 03 Aug 2023 22:30:35 +0000</pubDate>
      <guid>https://explosive.cloud/configuring-vmware-nsx-backups-using-ssh-keys/</guid>
      <description>&lt;h2 id=&#34;introduction&#34;&gt;Introduction&lt;/h2&gt;&#xA;&lt;p&gt;&lt;strong&gt;Important:&lt;/strong&gt; Starting with version 4.0, VMware NSX-T Data Center is known as VMware NSX.&lt;/p&gt;&#xA;&lt;p&gt;That&amp;rsquo;s important to note because when you google anything with NSX these days, you either get NSX-T documentation or NSX-v documentation. This post is about VMware NSX (Specifically NSX 4.1.0.2, but this should work on any NSX 4+ installation).&lt;/p&gt;</description>
    </item>
    <item>
      <title>There and Back Again (a Veeam Tale)</title>
      <link>https://explosive.cloud/there-and-back-again-a-veeam-tale/</link>
      <pubDate>Wed, 07 Jun 2023 17:48:56 +0000</pubDate>
      <guid>https://explosive.cloud/there-and-back-again-a-veeam-tale/</guid>
      <description>&lt;h2 id=&#34;introduction&#34;&gt;Introduction&lt;/h2&gt;&#xA;&lt;p&gt;Today we are backing up on-premises vSphere VMs with Veeam direct to a Minio S3 bucket, then restoring that VM to a VMware Cloud Director ORG in the cloud. Once complete, we will then back that VM up direct to a Minio S3 bucket and recover it back to the on-premises vSphere deployment.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
