Tag:

VMware Cloud Foundation

Cloud

Upgrading VMware Cloud Director to 10.x Versions

by Tommy Grot
written by Tommy Grot 4 minutes read

This walkthrough is valid for VMware Cloud Director 10.6.x Upgrade!

What’s New

VMware Cloud Director version 10.4.1.1 release provides bug fixes, updates the VMware Cloud Director appliance base OS and the VMware Cloud Director open-source components.

Resolved Issues

  • VMware Cloud Director operations, such as powering a VM on and off takes longer time to complete after upgrading to VMware Cloud Director 10.4.1After upgrading to VMware Cloud Director 10.4.1, VMware Cloud Director operations, such as powering a VM on or off takes longer time to complete. The task displays a Starting virtual machine status and nothing happens.The jms-expired-messages.logs log file displays an error.RELIABLE:LargeServerMessage & expiration=
  • During an upgrade from VMware Cloud Director 10.4 to version 10.4.1, upgrading the standby cell fails with a Failure: Error while running post-install scripts error messageWhen upgrading the VMware Cloud Director appliance by using an update package from version 10.4 to version 10.4.1, the upgrade of the standby cell fails with an error message.Failure: Error while running post-install scriptsThe update-postgres-db.log log file displays an error.> INFO: connecting to source node> DETAIL: connection string is: host=primary node ip user=repmgr> ERROR: connection to database failed> DETAIL:> connection to server at “primary node ip”, port 5432 failed: could not initiate GSSAPI security context: Unspecified GSS failure. Minor >> code may provide more information: No Kerberos credentials available (default cache: FILE:/tmp/krb5cc_1002)> connection to server at “primary node ip”, port 5432 failed: timeout expired
More Fixes and Known Issues here

More Information about VMware Cloud Director 10.4.1

VMware Cloud Director 10.4.1 introduces several new concepts that facilitate creating, deploying, running, and managing extensions. Solution Add-Ons are an evolution of VMware Cloud Director extensions that are built, implemented, packaged, deployed, instantiated, and managed following a new extensibility framework. Solution Add-Ons contain custom functionality or services and can be built and packaged by a cloud provider or by an independent software vendor. VMware also develops and publishes its own VMware Cloud Director Solution Add-Ons.

My Versions

  • VMware NSX 4.1.0.0.0.21332672
  • VMware vCSA 8.0.0 21216066
  • VMware Cloud Director 10.4.1

First. properly shutdown your VCD Cells if you have multiple cells. Once they are turned off take a snapshot of all of the appliances

Next we will want to upload the tar.gz file via WINSCP to the primary VCD Cell if you have a multi cell deployment you will need to upgrade the first cell, then second and third.

I have logged into the VCD appliance with root account

Then open up a Putty session to the VCD appliance login as root,

Then change directory to /tmp/ Once in the directory:

cd /tmp

Create a Directory within /tmp directory, with the command below:

mkdir local-update-package

Start to upload the VMware_Cloud_Director_10.4.1.9360-21373231_update.tar.gz file for the upgrade into /tmp/local-update-package via winscp

File has been successfully uploaded to the VCD appliance.

Next steps we will need to prepare the appliance for the upgrade:

We will need to move the VMware_Cloud_Director_10.4.1.9360-21373231_update.tar.gz from the /tmp directory to /tmp/local-update-package/

mv VMware_Cloud_Director_10.4.1.9360-21373231_update.tar.gz /tmp/local-update-package

Once in the local-update-package director, and you have your VMware_Cloud_Director_10.4.1.9360-21373231_update.tar.gz run the command below to extract the update package in the new directory we created in /tmp/local-update-package

tar -zxf VMware_Cloud_Director_10.4.1.9360-21373231_update.tar.gz

You can run the “ls” command and you shall see the VMware_Cloud_Director_10.4.1.9360-21373231_update.tar.gz file along with manifest and package-pool

After you have verified the local update directory then we will need to set the update repository.

vamicli update --repo file:///tmp/local-update-package

Check for update with this command after you have set the update package into the repository address

vamicli update --check

Now, we see that we have a upgrade that is staged and almost ready to be ran! But, we will need to shutdown the cell(s) with this command

/opt/vmware/vcloud-director/bin/cell-management-tool -u administrator cell --shutdown

Next is to take a backup of the database, log into VMware Cloud Director Appliance, https://<your-ip>:5480 , same port as vCSA VAMI.

Backup was successful! Now, time for the install

Apply the upgrade for VCD, the command below will run will install the update

vamicli update --install latest

Now, the next step is important, if you have any more VCD Cell appliances you will want to repeat first few steps and then just run the command below to upgrade the other appliances:

/opt/vmware/vcloud-director/bin/upgrade

Select Y to Proceed with the upgrade

After successful upgrade, you may reboot VCD appliance and test, and after successful tests remove your snapshot.

0 comments 3.4K views
3 FacebookTwitterLinkedinEmail
VMware NSX

Upgrading VMware NSX 4.0.1.1 to 4.1.0

by Tommy Grot
written by Tommy Grot 4 minutes read

Topic of the day – How to upgrade VMware NSX 4.0.1.1 to 4.1.0, during this walkthrough, I will go through all the steps that are required, along with how the upgrade process is and any issues I encounter.

Lets Begin!

What Will You Need:

Version I am Running:

  • VMware ESXi 8.0 Build 21203435
  • VMware vCenter Server – 8.0.0.10200

The supported upgrade paths for the NSX product versions. (More Info Here)

Adhere to the following upgrade paths for each NSX release version.

  • NSX 3.2.x > NSX 4.1.x.
  • NSX 4.0.x > NSX 4.1.x.

What’s New

Information below is from VMware’s NSX Release Notes – More Info Check out here!

NSX 4.1.0 provides a variety of new features to offer new functionalities for virtualized networking and security for private, public, and multi-clouds. Highlights include new features and enhancements in the following focus areas:

  • IPv6 support for NSX internal control and management planes communication – This release introduces support for Control-plane and Management-plane communication between Transport Nodes and NSX Managers over IPv6. In this release, the NSX manager cluster must still be deployed in dual-stack mode (IPv4 and IPv6) and will be able to communicate to Transport Nodes (ESXi hosts and Edge Nodes) either over IPv4 or IPv6. When the Transport Node is configured with dual-stack (IPv4 and IPv6), IPv6 communication will be always preferred.
  • Multi-tenancy available in UI, API and alarm framework – With this release we are extending the consumption  model of NSX by introducing multi-tenancy, hence allowing multiple users in NSX to consume their own objects, see their own alarms and monitor their VMs with traceflow.  This is made possible by the ability for the Enterprise Admin to segment the platform into Projects, giving different spaces to different users while keeping visibility and control.
  • Antrea to NSX Integration improvements – With NSX 4.1, you can create firewall rules with both K8s and NSX objects. Dynamic groups can also be created based on NSX tags and K8s labels. This improves usability and functionality of using NSX to manage Antrea clusters.
  • Online Diagnostic System provides predefined runbooks that contain debugging steps to troubleshoot a specific issue. These runbooks can be invoked by API and will trigger debugging steps using the CLI, API and Scripts. Recommended actions will be provided post debugging to fix the issue and the artifacts generated related to the debugging can be downloaded for further analysis. Online Diagnostic System helps to automate debugging and simplifies troubleshooting

Interoperability Check for VMware vSphere 8 and NSX 4.1

Before we start the upgrade, make sure that you have successfully backups of your current NSX Environment! For my implementation I used a SFTP Server running on Ubuntu Linux VM which is hosted on a secondary tier storage SAN,

Now, that we verified our backups are good. Lets begin uploading the MUB file.

Go To Upgrade ->

Click on UPGRADE

Find via Browse the VMware-NSX-upgrade-bundle-4.1.0.0.0.21332672.mub and upload it

Wait few min for the MUB to upload

Now, the MUB has been successfully uploaded to NSX Manager appliance, now we wait and let it extract all the files.

Verifying Stage

Now, we are ready to prepare for the Upgrade! (Accept the EULA at the pop up)

This portion of the upgrade will go through many stages within this little window, you will see once as an example: Restarting Upgrade Coordinator

Click – Run Pre-Check Before upgrading!

Now Let the NSX Edge Nodes upgrade, this is a pretty quick automated process!

NSX Edge Nodes successfully upgraded!

Now time to upgrade the Transport Nodes (also known as ESXi Hosts)

You will see the upgrade process going in vCenter Tasks. (Make sure that all VMs that are not on any kind of shared storage such as vSAN or a iSCSI LUN which is shared within the cluster, off.)

In Process upgrade for Hosts.

Successful Upgrade

The final part, we will upgrade the NSX Managers

Confirm to start the upgrade

Upgrade in process for NSX Managers, it does them 1 at a time.

Data Migration upgrade process

Unpin API

Unpin UI

There it is! Fully upgrade to NSX 4.1.0 – Now, next blog post we will get into the new features. But Check out that new Project Tab drop down for multi-tenancy!

0 comments 4.5K views
0 FacebookTwitterLinkedinEmail
Hardware Tips & Tricks

Palo Alto PPPoE VLAN Tagging w/ Century Link Gigabit Fiber

by Tommy Grot
written by Tommy Grot 1 minutes read

Today’s topic is about Palo Alto and PPPoE interface and VLAN tagging. Currently Palo Alto does not support VLAN Tagging on an Interface with PPPoE authentication for your ISP. So, our workaround that works well but definitely need to have a Managed switch so you can Trunk and Tag an interface to make the Century Link FTTH ADTRAN know that VLAN 201 is Tagged.

Info –

Century Link Fiber Internet – Utilizes VLAN tagging to segregate out their Internet traffic, and their TV service.

What You Need:

  • PPPoE Username & Password
  • VLAN ID = 201
  • Managed Switch / Router that supports VLAN Tagging

First we will setup two ports on a managed switch, for my implementation I am using a Cisco Catalyst WS-C3750X-24P-S.

Interface Gi1/0/23 – Syntax below to copy (Just FYI, this is for Cisco)

description Trunk to CenturyLink
switchport trunk allowed vlan 201
switchport trunk encapsulation dot1q
switchport mode trunk
switchport nonegotiate
spanning-tree portfast edge

Interface Gi1/0/24 – Syntax below to copy (Just FYI, this is for Cisco)

description WAN-PAFW
switchport access vlan 201
switchport mode access

Go to Network -> Click on Ethernet1/1

Once Interface is opened up, make sure your Virtual Router and all configured, but then Go to IPv4

Click on General -> Select PPPoE -> Fill in your Username and Password for Century Link PPPoE Authentication -> Click OK

Now that your Century Link PPPoE user name and info is filled out, under advanced, you may set your Static IP address here for your WAN Interface.

Red Ethernet cable Et1/1 going to Gi1/0/24 which is the one that is Tagged as an access port on vlan 201

0 comments 998 views
0 FacebookTwitterLinkedinEmail
Education

I passed my VCAP-DCV Deploy 2023!

by Tommy Grot
written by Tommy Grot 1 minutes read

On Wednesday 11th, 2023, I took the VCAP-DCV Deploy 2023 and passed it! It was my first lab/exam of 2023. After completing this exam, I earned the VCIX – VMware Certified Implementation Expert milestone, this unlocks the next level for me to pursue my VMware Certified Data Center Expert (VCDX).

Information on Data Center Virtualization track from VMware

Information About the Exam –

After getting logged in the first thing I did was fire up Notepad++ I created a task list of all 17 questions, this way any step I did during the exam I would document what I did and what I configured so I can trace back what I did. Overall, I enjoyed the exam/lab. It was fun to do the tasks, I recommend getting all the easy ones first that way you can concentrate on the longer duration tasks that.

0 comments 1.5K views
2 FacebookTwitterLinkedinEmail
CloudNetworking

Reverse Proxy & Load Balancing a Web Server with VMware NSX Advanced Load Balancer

by Tommy Grot
written by Tommy Grot 3 minutes read

Want to setup a load balancer and reverse proxy with VMware NSX Advanced Load Balancer, and you want to replace your Nginx Reverse Proxy, well let’s get started!

First, we will make sure that you already have NSX ALB setup and configured within your environment, this walkthrough will only step you through on building a Virtual Service and Pools and VIPs for your multiple web servers. During this deployment you can set up many different FQDNs.

Requirements

  • Public FQDN
  • Lets Encrypt SSL Certificate (Wild Card or SAN or Single Cert)
  • NAT – Service Engine
  • Virtual IP
  • Service Pool
  • Web Server(s)

Product Versions:

  • VMware NSX ALB: 22.1.2
  • VMware NSX: 4.0.1.1.0.20598726

Steps

Login as an administrator account to NSX ALB ->

Go to Virtual Services -> Create Virtual Service

Select -> Advanced Setup

Next prompt -> Select your Cloud (For my setup I am doing everything NSX Overlay Backed)

Click Next -> Select your VRF Context (I am using a Tier 1 Gateway)

So now at this point – you should see this screen below, we will create a New Virtual Service, this will be the main ingress and egress point of your network and the external world. I have a NAT from my firewall going to this Virtual Service (VIP) Virtual IP.

  • Name: External-ParentSNI-VS (This is my naming convention, but you can choose your own)
  • Select: Enable Virtual Hosting VS
  • Virtual Hosting Type: SNI
  • VS VIP – (Create the main VIP for Ingress/Egress NAT, that is routable)
  • Application Profile: System-Secure-HTTP
  • WAF ( You can enable if you would like too, this is optional)
  • Service Port ( 80,443 – For 443 you will want to select SSL)
  • Pool – (Create a Pool, I used one of my very first web servers to start the pool)
  • SSL Certificate – Select your Cert – by default ALB will put System-Default-Cert

Click Save / Next – For this portion of the Virtual Service with Parent SNI we are done, next we will deploy the Child SNI which will be a parent to the main Ingress/Egress SNI Virtual Service.

As an example – I will use my Virtual Bytes SNI Child Virtual hosting.

Click on drop down for Pool, if you have not created a pool we will do so now.

  • Name: External-Parent-SNI-VS-Pool
  • VRF Context – Your Tier 1 Gateway
  • Default Server Port: 443

Select your first webserver, this will let you start the Virtual Service. You can do it via a IP Group or IP Address or DNS Name as well as have the capability to use a security group from NSX.

After you have created all the required services you should be able to access your web server from an internal or external (Internet) if you have NAT’d. But for the next steps we will repeat the steps for a Child SNI.

Child SNI Setup

  • Go to Virtual Services – > Click on Create Virtual Service (Advanced)
  • Name: You Web Server
  • Check – Virtual Hosting VS
  • Virtual Hosting Type: SNI
  • Virtual Hosting Parent: External-ParentSNI-VS (or your own naming)
  • Domain Name: www.yourdomain.com
  • Application Mode: System Secure-HTTP
  • Pool: Create a pool for the Virtual Machine or service you want to load balance
  • SSL Certificate: Select your Certificate

Click Next all the way till the end, and now you have successfully setup a Child SNI which now you can replicate the same steps for multiple web servers, and you no longer need to NAT anymore IPs, since your main ingress/egress is already NAT’d and everything will flow through the main Parent service.

0 comments 3.1K views
1 FacebookTwitterLinkedinEmail
Cloud

“The Next Chapter of Cloud Management” VMware’s LAST multi-cloud briefing of 2022

by Tommy Grot
written by Tommy Grot 2 minutes read

With all these organizations trying to be multi-cloud centric it is hard to set up and control all those environments. Organizations that have Amazon Web Services or Azure and they run VMware Clouds on top of those environments, well that’s a tedious job to keep control and tabs on everything. Creating dashboards and information from a high level for leadership will let them know what kind of costs and consumption they are utilizing for their workloads. Well, with VMware Aria Hub – it is now possible to keep track of everything, from cost to capacity and consumption and how they can scale back workloads without compromising the business aspect and goals!

*** Disclaimer *** – Preview information and functionality will not be available till early 2023!

Links:

Check out the Video below for more details –

VMware Aria Graph is a highly scalable system but also federated which you can federate from any other third party with their solutions. You can gather data from many third-party sources and create rich data and analytics to help your business needs. With VMware Aria Graph if you already own VMware vRealize Suite then this will be even better for your organization this will allow you to gather data and create more richer business models and practices with the data you will gather about your environment.

Main Dashboard – Shows overall cost, infrastructure and security compliance, and many more features.

Application View – This lets you see the aggregate information of your application, along with resources, and cost and what relationships the application has for what kind of image was used to build this and what kind of security settings have been applied like firewall rules..

Aria Guard Rails – Policy as code, continuous police enforcement engine. This will let you know what kind of security violations that are not controlled and with guard rails there is a library with pre-built templates for bootstrapping environments, cost, security. This will let you ensure that you set the proper security policies.

Deployment Information – Resources this draws out in detail how your workloads a connected and consumed and you can click on each individual icon and get into the depth information of each workload or VM

Migrating Workloads to VMC – you can select what kind of workloads you want to move to AWS VMC; you can get very granular on what kind of VM you want to move, you can move based on VLANs or prevent moving some workloads to save cost or keep on premise.

Cost of Ownership, this allows you to preview what your workload would cost on VMC on AWS.

Migration Planning – Gives you an awesome road map to plan out your workloads and how they will migrate and what business practices you want to implement and execute before running the migration.

Step 2 of Migration

Step 4 – Scheduling your migration

0 comments 479 views
0 FacebookTwitterLinkedinEmail
Cloud

VMware Aria – VMware Multi-Cloud Briefing December 5th, 2022

by Tommy Grot
written by Tommy Grot 1 minutes read

The new and exciting annoucment that occured at VMware Explore 2022 about VMware Aria! I personally got to meet the team behind the VMware Aria and vRealize Buisness Unit team thank to our awesome VMware Senior Techinical Account Manager!

My first day at VMware Explore 2022, I got to see all the new release and information before it hit emargo, with Purnima’s Session with the Multi Cloud Journy. Overall, it was a great time to see how the product would help organizations and developers and engineers with creating new solutiuons that are multi-cloud. Many oragnizations today, are going versatile with many different clouds where many of the organizations are in a cloud chaos point in their life of their organization and they do not know or how to take control over and get their cloud infrastructures and development in line.

With that said! I am linking here some news that will be released on December 5th, 2022. So stay tuned and check this page below!

0 comments 438 views
0 FacebookTwitterLinkedinEmail
VMware ESXiVMware vCenter

vSphere 8 vMotion Unified Data Transport

by Tommy Grot
written by Tommy Grot 2 minutes read

Tonight’s topic is about vMotion! But not just any kind of vMotion, we are going to enable blazing fast speeds to migrate your workloads. Before we get into the topic, I want to bring up information on VMware vSphere 8! I have been using the GA version of vSphere 8 on my new home lab (datacenter) and it’s been great so far!

vSphere vMotion migrates a(n) running state of a virtual machine from one ESXI host to another ESXI host in minutes or now even seconds! This allows you to vMotion workloads much faster now with vMotion protocol in vSphere 8 and all its huge performance improvements cause before standard vMotion utilized Network File Copy (NFC) which this was much slower and took longer but now with Unified Data Transport we will now enable Provisioning on the same vMotion VMkernel to speed up migration of workloads!

Here is more information from VMware:

To solve this problem, we introduce a new protocol called Unified Data Transport (UDT). In a nutshell, UDT combines the best of the NFC and vSphere vMotion protocols. Unified Data Transport (UDT) uses NFC as a control channel but offloads the data transfer to the vSphere vMotion protocol to benefit from the substantially greater performance and throughput.

How to Configure? Well Lets start!

Login into your vCSA

Go to your first ESXi hosts -> VMkernel Adapters

Click Edit on vMotion VMkernel, for mine it is vmk2

Select Provisioning along make sure your vMotion Enabled Service stays selected.

Click OK -> You will see a +1 Under Enabled Services and now I have vMotion and Provisioning Enabled on my single vmk2.

Repeat the steps on your next following ESXi Hosts.

That is it! Start enjoying the blazing speeds of migrating your workloads from ESXi host to another ESXi host!

0 comments 1.7K views
0 FacebookTwitterLinkedinEmail
VMware vCenter

Upgrading vSphere 7.0.3 to vSphere 8.0

by Tommy Grot
written by Tommy Grot 6 minutes read

vSphere 8 Update 1 – Released!! If you want to see how to upgrade go here to new blog post!

I will be going over on how to upgrade your vSphere 7 to vSphere 8! I will be doing step by step screenshots to walk anyone through, keep in mind that this is upgrading from vSphere 7.0.3 going to vSphere 8.0.

Exciting news! vSphere 8 is (IA) Yes, there is a new release model. Below I have some information below from VMware’s website but if you want to get more in-depth information go to the link below!

New IA/GA model (Information from VMware)

Our intent going forward is that all major and update vSphere releases will be delivered first with an IA designation. An IA release is a production-quality release that meets all GA quality gates and is fully partner certified. IA releases will be available during the IA phase to all customers for production deployments.

Changing to this IA/GA model is motivated by several factors. Most importantly, feedback from customers who want us to be more explicit when a release has achieved strong traction and usage without having to wait for the next update release, which they sometimes use as a proxy. By switching the designation from IA to GA, we’ll be making it clear when the release has gained wide adoption. We think this is a better model than waiting for a 6-month update, particularly as these updates now include feature enhancements as well as net new features.

DISCLAIMER:

– Everything I document here is on my lab, do not try this on a production system if you do not have backups or a way to restore if something goes wrong.

– This Walkthrough is only for a vSphere Cluster upgrade

Before you start the upgrde ensure you have a backup of your vCenter Server Appliance.

We will be upgrading a vSphere 7.0.3 Cluster to vSphere 8.0! Below is the vSphere 7 snippet

Download you ISO from VMware’s website and copy the iso to your local workstation

Once you get your ISO ready mount it to your local computer and drill down into the

vcsa-ui-installer -> win32 -> then execute installer.exe

Go to Upgrade ->

Once you are ready to upgrade your environment you will go Next

Once you get to this window, you will want to fill in your Source Appliance which is the vSphere 7 Cluster you want to upgrade. For Example: lab-vcsa-m01.virtualbytes.io

Then -> Click Connect to Source

Once it connects to the source server, you will get this detail specific page during the deployment asking to fill in the vCenter Server Appliance SSO Username and Password along with the Appliance (OS) root password along with the ESXi Host or vCenter Server that manages the source appliance

Accept the Certificate Warning which you will have your Source and Destination servers where the appliance will get deployed

Input your vCenter Server deployment target, where the new vCenter Server Appliance will get deployed

If you are installing this select your current datacenter object where the vCSA appliance will be stored in

This is creating the new vCSA on the target server, you will want to make sure that the two vCenter Server Appliances do not collide with the same naming convention or you will get any error saying this name for the VM exists.

Fill in your network information for the upgraded preparation

After ~15 minutes, you will get to the Phase 2 of the Upgrade Process, Click -> Next

I purposly did not enable SSH on my source vCenter Server, this way if anyone encounters the same issue, this will guide you to make sure you have SSH enabled on the Source vCenter Server Applaince or you will get this error below 🙂

After you enabled SSH and re-try the task you will go into the Pre-Upgrade Checks state

Below is a Pre-Upgrade check result which has some Warnings to let you know

Here at this step we are about to upgrade the data for our vCSA! Select your requirment, i only did the Configuration and Inventory.

Select – > I have backed up the source vCenter Server and all the required data from the database.

WARNING!! – Make sure you have your source vCenter backed up and/or snapshot to revert too if something does not upgrade properly.

This process will take ~ 15 – 20 minutes max, but this also depends on how large your environment is, the more objects in the data base the longer it will take.

Next snippet, will show you that we have copied the data from the source vCenter Server to the Targer vCenter Server

Now, that we have finalized the migration and the import to the target vCenter Server is done, we will log into the new vCSA appliance.

Login with your ” [email protected]”

Now, you shall see that our vCenter Server is at vSphere 8. Next we will be creating a Baseline within vSphere Life Cycle Manager to upgrade our Hosts.

Click on the top right hamburger menu -> Life Cycle Manager

Go to Imported ISOs ->

Now we will upload our vSphere 8 ISO – > VMware-VMvisor-Installer-8.0-20513097.x86_64.iso

Once it is uploaded, we will go and create a Baseline for our new Image to upgrade the ESXi hosts from ESXi 7 to 8

Then go “Baselines” -> New -> Baseline

Now we will create a name for our baseline -> vSphere 8 Upgrade

Attach the vSphere 8.0 iso we just uploaded earlier to this baseline.

Finalize the Creation of the vSphere 8 Upgrade baseline

Then go back to the ESXi host object, and go to Updates tab

Here we will attach the vSphere 8 Upgrade Baseline we created

Once the ESXi host has the new vSphere 8 baseline attached, you can now Remediate the host, and then repeat the vLCM (vSphere Life Cycle Manager) Baseline attach to the rest of your hosts and then follow the traditional Remediation process that way your ESXi hosts properly migrate workloads off to other ESXi hosts during this process to ensure that you won’t have any downtime.

Web console view of our ESXi host that just got upgraded!!

Our first ESXi host has been upgraded to vSphere 8!

Next, after all our ESXi hosts are on vSphere 8, we will want to make sure that our vSAN version is upgraded so you will want to upgrade it.

Go to your vSAN Cluster -> Configure -> Services

Once you get to vSAN Services, you will see Pre-Check vSAN upgrade and Upgrade vSAN. A proper best practice is to do a pre-check of your vSAN cluster to ensure that all the objects are healthy and synchronized and there are not disk issues before doing a vSAN upgrade.

After vSAN upgrade – Your vSphere Cluster is now officially upgraded to vSphere 8! with vSAN 8! This walkthrough was able to walk you through any issues that you may encounter. Next blog post will be on how to convert a vSAN (OSA) Datastore to vSAN (ESA) – Express Storage Architecture

0 comments 28.8K views
6 FacebookTwitterLinkedinEmail
VMware Troubleshooting

Unregister vCSA Plugin or Extension via vCenter MOB

by Tommy Grot
written by Tommy Grot 1 minutes read

Have you had an issue with vCenter Server Appliance? Well there is a way to fix and remove a plugin or extension. Open up your browser to https://<your-vcenter-ip>/mob and login with your credentials, if you do not have any other identity source you will need to login with your [email protected] SSO account.

Go to Content ->

Go to Exetension Manager ->

Go to More -> look for your extension that has been registered.

Copy the file name from “com.xxx.xxxx.xxxxxx.xxxx”

Go to Unregister -> and paste in the value and execute Invoke Method

0 comments 1.6K views
1 FacebookTwitterLinkedinEmail
Newer Posts
Older Posts