Nsx on Explosive Cloud

NSX Upgrade Failure

Wed, 08 May 2024 19:05:39 +0000

Issue

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.

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: ['gpg', '--homedir', '/root/.gnupg', '--verify', '/tmp/tmpc75b6zcx/VMware-NSX-edge-4.1.2.3.0.23382424.bundle.sig', '/tmp/tmpc75b6zcx/VMware-NSX-edge-4.1.2.3.0.23382424.bundle'] returned 2: b"gpg: Signature made Mon 26 Feb 2024 10:40:20 PM MST\ngpg: using RSA key E51BDAAAFDF4DC95\ngpg: Can't check signature: No public key\n" .

However, my T1 edge nodes (which were set to upgrade first) had no problem with the same upgrade package. What a mystery!

NSX - Node with the same IP already exists

Fri, 29 Sep 2023 14:29:07 +0000

Versions, for posterity

vCenter 8.0.1 - build 22088981
ESXi - 22088125
NSX - 4.1.0.2

Backstory

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.

Configuring VMware NSX Backups Using SSH Keys

Thu, 03 Aug 2023 22:30:35 +0000

Introduction

Important: Starting with version 4.0, VMware NSX-T Data Center is known as VMware NSX.

That’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).