If you followed the previous blog NSX-T: Deploy NSX-T Manager 2.5 with OVFtool you should have NSX-T Managers deployed.

There's a few more things we have to configure within NSX-T Manager like:

• Add a compute Manager (when using vCenter)
• Create IP Pools
• Create Transport Zones
• Create Profiles - Uplink & Transport …

If you have the NSX-T Manager OVA on a fileshare or web server you can deploy it from the vCenter GUI, or use any other deployment tool like OVFtool.

Using OVFtool to deploy NSX-T Manager is a great way to deploy a quick and repeatable configuration. It also helps to document the configuration options.

After adding a compute manager, the Registration Status shows as Not Registered, and Connection Status is Down.

This is usually caused by a previously registered NSX-T Manager to vCenter, that has been deleted. If you remove the Compute Manager via the Delete option in NSX-T Manager, it also removes the registration …

Recently VMware released a Fling of the VMware Appliance for Folding@Home.

It's great to see the VMware community coming together so quickly to help out.

As part of my love/hate relationship with OVFtool, here's a few ways you can deploy the VMware Appliance for Folding@Home using OVFtool.

If you try and deploy vRA8 into VMware Cloud on AWS, you'll get this error:

User has no administrative privileges

More customers are embracing the suite of applications provided by VMware in managing their environment. I'm seeing customers with vRealize Network Insight (vRNI), but a lot still don't appreciate all the things it can do. One of those things is showing redundant NSX firewall rules. Often when customers create NSX …

For those with NSX-v 6.4, they’d know the end of general support date was 16/01/2021, (just over a year from now). If you check the product lifecycle it now shows the end of general support is 16/01/2022.

<img
  loading="lazy" …</picture></figure></p>

When using the Migration Assistant to Migrate from a Windows 5.5 vCenter to 6.5 VCSA, the migration assistant was failing to run on the Windows vCenter server.

It automatically saves the logs on the desktop. When viewing the logs, this part stood out:

12019-07-22T00:31:58.193Z ERROR upgrade.states.component_states …

Deploying vRNI 4.1 you might get an error: Insufficient capacity on each physical CPU.

<img
  loading="lazy"
  decoding="async"
  alt="Insufficient capacity on each physical CPU"
  
    class="image_figure image_internal …</picture></figure></p>