Common ESXi & vCenter Issues with Solutions

VMware is a popular virtualization platform, but system administrators face problems related to VM power management, network, storage, and performance. This blog post will discuss practical VMware troubleshooting techniques.

🛠️ VMware Troubleshooting Guide

🔴 Issue 1: Virtual Machine Not Powering On

Symptoms

• VM stuck at Powering On

• Error: Failed to lock the file

• VM shows Invalid State

Possible Causes

• VM files locked

• Insufficient host resources

• Management service issue

Solution

1. Check host CPU and RAM usage

2. Restart ESXi management agents:

services.sh restart

3. Verify no .lck files exist in datastore

4. Try registering the VM again

---

🌐 Issue 2: VM Network Not Working

Symptoms

• VM has no internet

• Cannot ping gateway

• Network disconnected inside VM

Possible Causes

• Wrong port group

• VLAN mismatch

• Network adapter disconnected

Solution

• Verify correct vSwitch & Port Group

• Check VLAN ID (should match physical switch)

• Ensure Network Adapter → Connected

• Restart network service if required

---

💾 Issue 3: Datastore Inaccessible or Full

Symptoms

• Datastore shows inaccessible

• VM snapshot fails

• VM cannot start due to disk error

Solution

• Rescan storage adapters

• Free up datastore space

• Delete or consolidate snapshots

• Check storage connectivity (iSCSI / NFS)

---

📉 Issue 4: VM Performance Very Slow

Symptoms

• VM lagging

• High CPU Ready time

• Disk latency alerts

Possible Causes

• Overcommitment of CPU/RAM

• Storage I/O bottleneck

• Memory ballooning or swapping

Solution

• Reduce resource overcommitment

• Check CPU Ready (%RDY < 5% ideal)

• Monitor datastore latency

• Add RAM or CPU if required

---

🔍 Issue 5: vCenter Service Down

Symptoms

• Cannot log in to vCenter

• vSphere Client not loading

Solution

Restart vCenter services:

service-control --status
service-control --start --all

Check disk space on vCenter appliance — /storage/log full is a common cause.

---

📁 Important VMware Logs for Troubleshooting

Component	Log Location
ESXi Host	/var/log/vmkernel.log
VM Issues	vmware.log
vCenter	/var/log/vmware/

Always check logs before taking action.

---

✅ Best Practices

• Monitor datastore space regularly

• Avoid excessive snapshots

• Keep VMware tools updated

• Take backups before major changes

---

🔚 Conclusion

Most VMware issues are related to resources, configuration, or storage. A systematic troubleshooting approach — logs → resources → configuration — resolves issues faster and prevents downtime.

---

🔧 About This Blog

This blog is part of VMware Troubleshooting Series by TelekaTechXYZ
Follow for more real-world IT & virtualization solutions.

---

🔁 How to Replace a Failed ESXi Host in VMware VCF 9 (Step-by-Step)

In VMware Cloud Foundation (VCF) 9, replacing a failed ESXi host is a two-step automated process handled by SDDC Manager.

❌ Never replace hosts manually in vCenter
✅ Always use SDDC Manager

---

🧠 Simple Explanation (For Freshers)

• Failed Host → Hardware crash, disk failure, motherboard issue

• Replacement → Remove failed host + add a new host

• VCF ensures:

  • vSAN data protection

  • NSX cleanup

  • Cluster compliance

This process is VMware-supported and safe.

---

📋 Prerequisites Before Replacement

✅ Cluster Must Be

• Healthy (or degraded but accessible)

• Enough capacity to rebuild vSAN

• Minimum required host count maintained

🖥️ New ESXi Host Must Be

• Fresh ESXi installation

• Same ESXi version

• Same hardware model (recommended)

• DNS & NTP configured

• No VMs, no cluster membership

---

🚀 Steps to Replace Failed ESXi Host in VCF 9

---

🟢 Step 1: Identify Failed Host in SDDC Manager

1. Login to SDDC Manager

2. Go to Inventory → Workload Domains

3. Select the Cluster

4. Identify the host with Disconnected / Failed status

📌 Do NOT remove it from vCenter manually.

---

🟢 Step 2: Decommission Failed Host

1. Select the failed host

2. Click Decommission Host

3. Choose Ensure Accessibility (if host already down)

👉 Since the host is failed, Full Migration is not possible.

VCF will:

• Clean NSX references

• Remove host from inventory

• Update cluster state

---

🟢 Step 3: Prepare the New Replacement Host

On the new server:

• Install ESXi

• Configure Management IP

• Configure DNS & NTP

• Enable SSH (temporary)

📌 Keep the host standalone.

---

🟢 Step 4: Add New ESXi Host to VCF Inventory

1. In SDDC Manager

2. Go to Inventory → Hosts

3. Click Add Host

4. Enter hostname, IP, root password

5. Complete validation

---

🟢 Step 5: Add Host to Existing Cluster

1. Navigate to Workload Domain → Cluster

2. Click Add Host to Cluster

3. Select the new host

4. Run validation

5. Start deployment

VCF automatically:

• Adds host to vCenter

• Claims vSAN disks

• Configures NSX TEP

• Applies host profiles

⏱️ Time: 30–60 minutes

---

🟢 Step 6: Verify Replacement

After completion, verify:

• Host status = Connected

• vSAN health = Green

• NSX = Healthy

• Cluster capacity restored

🎉 Failed host successfully replaced.

---

🔧 Post-Replacement Best Practices

• Disable SSH on new host

• Monitor vSAN resync

• Verify alarms cleared

• Update hardware inventory

---

⚠️ Common Issues & Fixes

Issue	Cause	Fix
Cannot decommission	Host still reachable	Retry / power off
vSAN resync slow	Heavy data	Wait / add capacity
New host validation fails	DNS mismatch	Fix DNS
NSX error	MTU mismatch	Verify MTU

---

❌ What NOT To Do

• ❌ Do not remove failed host from vCenter

• ❌ Do not reuse old disks without cleaning

• ❌ Do not skip validation

• ❌ Do not change networking manually

---

🎯 Why VCF Host Replacement Is Safe

Using VMware VCF 9 ensures:

• Data integrity (vSAN)

• Clean NSX state

• Lifecycle compliance

• Full VMware support

---

🏁 Conclusion

Replacing a failed ESXi host in VCF 9 is straightforward and reliable when done through SDDC Manager.

For freshers:

Remove failed → Add new → Let VCF automate

---

📌 Blog Series

VMware Cloud Foundation 9 – Install | Expand | Remove | Replace | Upgrade

---

System Center Virtual Machine Manager 2016 installation – Overview

System Center Virtual Machine Manager 2016 installation – Overview

• 
  
• VMM is part of the System Center Suite which is used to configure, manage and transform traditional datacenters, and which helps in providing a unified management experience across on-premises, service provider, and the Azure cloud.

Prerequisites for SCVMM 2016 are two virtual machines – one is for the AD and another one is for VMM.

Capacity limits

The following table provides the scale limits that were tested for System Center 2016 Virtual Machine Manager. There are various factors that impact the scale limits, such as hardware configuration, network, topology and others.

Entity	Recommended maximum count
Physical hosts	1000
Virtual Machines	25000
Services	1000
User roles	1000
Clouds	20
Virtual networks	2000
logical networks	20
Library resources	1000
Library Objects (templates, profiles)	100

Hardware

Hardware	VMM server	VMM database	VMM library	VMM console
Processor (minimum)	8 core Pentium 4, 2GHx (x64)	8 core Pentium 4, 2.8GHx	4 core Pentium 4, 2.8GHz	2 core Pentium 4, 1 GHz CPU
Processor (recommended)	16-core, 2.66 GHz CPU	16 core 2.6 GHz CPU	4 core 2.66 GHz CPU	2 core 2 GHz CPU
RAM (minimum)	4 GB	8 GB	2 GB	4 GB
RAM (recommended)	16 GB	16 GB	4 GB	4 GB
Hard drive (minimum)	4 GB	50 GB	Based on size/amount of stored files	10 GB
Hard drive (recommended)	10 GB	200 GB	Based on size/amount of stored files	10 GB

Server operating system

Operating system	VMM serve	Remote VMM library	Remote VMM database
Windows Server 2012 Standard/Datacenter	N	N	If supported by SQL Server version
Windows Server 2012 R2 Standard/Datacenter	N	Y	If supported by SQL Server version
Windows Server 2016	Y	N	If supported by SQL Server version
Windows Server 2016 (with desktop experience)	Y	Y	If supported by SQL Server version
Windows Server 2016 Nano	N	N	If supported by SQL Server version

Client console operating system

Operating system	Supported
Windows 7	N
Windows 8	N
Windows 8.1	Y
Windows 10 Enterprise	Y
Windows Server 2008 R2 with SP1 onwards	N
Windows Server 2012	Y
Windows Server 2012 R2 Standard, Datacenter	Y
Window Server 2016 Standard, Datacenter	Y

SQL Server

Operating system	Supported
SQL Server 2008 R2 (SP1, SP2)	N
SQL Server 2012 (Enterprise, Standard, 64-bit)	N
SQL Server 2012 SP1 onwards	Y
SQL Server 2014 and all service packs	Y
SQL Server 2016 and all service packs	Y

Virtualization

VM	Supported
VMM management server	The VMM management server can be installed on a VM. If you use dynamic memory, set the start RAM of the VM to at least 2048 MB. You can deploy the VMM management server (physical or VM) in a highly available cluster.
VMM console	You can install the VMM console on a VM.

Installation components

These components should be installed on the server, before you install VMM.

Component	VMM server	VMM console
Active Directory	The VMM management server must be a domain member. The computer name shouldn’t exceed 15 characters.	A computer with the VMM console installed should be a domain member.
Windows ADK	Available in the Download Center	Not applicable

Installation:

Step – 1 Installing and configuring SQL server.

1. Install and configure an ADDS server and join the VMM machine to the domain as an administrator account
2. Now install MSSQL in VMM machine, Select “SQL Server Feature Installation” and give next
3. In next tab we have to select Instance Features, we need Database Engine Services, Management Tools – Basic, Management Tools – Complete, and SQL Client Connectivity SDK


4. That’s it now you can click next and continue with default settings
5. Once the installation finished successfully open SQL Server Management Studio
6. In left side pane, you can see Logins expand it and navigate to your user and right click and go to properties
7. In properties, you can find Server Roles, click on that and select server roles db creator, process admin, and security admin and click OK button

Step – 2 Installing Windows ADK.

Now we are going to install Windows ADK 10.

1. Double click on the setup file of Windows ADK 10 file and select Features. We need only Deployment Tools, Windows Preinstallation Environment (Windows PE), Windows Performance Toolkit, and Windows Assessment Services.

2. Now click install and the process will take some time

Step – 3 Creating Container and assigning permission

1. In this step, we are going to create a VMM Container in AD server
2. Login to the AD server and open Server Manager and click on tools and select ADSI Edit.
   In ADSI console right click on ADSI Edit and click connect to, now the default connection settings will appear to click OK and continue.

3. Click on the DC and right click and select New and select Object
4. Here you can create Container and name it

5. Now the Container has been created, now right click on the created Container and go to
6. properties and move to security tab
In security, tab verify your user account has FULL access. If not add your domain user and give Full access
7. Now click on an advance in the same security tab and select your user and click edit
8. Now change This Object to This Object and all descendant objects
9. That’s all now we are good to install VMM

Step – 4 Installing VMM

1. Double click on the SC2016_SCVMM and extract it, and navigate to the folder and run the setup.
2. There will be two options VMM Management server and VMM Console, if you select VMM Management server automatically the second option will be added.

3. In next page need to fill product registration details, fill your details and give next.
4. Next, you need to accept the license agreement and give next
5. Apply the default settings and continue.
6. In Database Configuration page, make sure server is correct and check the “Use the following credentials” option and fill the username and password of the machine and select the instance then give a database name or leave as it is and give next.
7. In next page select domain account and fill the details, and check the option “Store the keys in Active Directory” and provide the location.
8. For this location move on to the AD machine and navigate to the container which we have created in step – 3, right click and select and properties and double click distinguishedName and copy the value and paste it in the “Store the keys in Active Directory”

9. Now review the port configuration and give next.

10. In next tab you need to specify the library, here select “Create a new library and share” and give next.
11. Verify the installation summary and click install.
12. After successful installation, your result will look like this.

Step – 5 Adding Hyper – V host in VMM

1. Open the VMM console and right-click on All Host’s and select Add Hyper-V Hosts and Cluster.

2. We are going to add the host in “Windows Server computers in a trusted Active Directory domain” select this option and give next.
   Note: Create two-way trust relationship between domains.
3. Now select the option “Use an existing run as account” and click browse and create a run as account.
Note: Provide the domain administrator account credentials.
4. In next tab select “Specify Windows Server computers by names” and give FQDN or IP and proceed to the next step.
5. After successful validation, you select the host and proceed further.

6. Select default settings and proceed further and finish.
7. Now in All Hosts tab you can find the Hyper-V host and manage it.

Conclusion:

System Center Virtual Machine Manager is very easy to deploy and manage the Hosts, Admins can have control of all the Virtual Machines through Virtual Machine Manager. There are more to explore in System Center Virtual Machine Manager i.e we can add vCenter servers and ESXi hosts as well.

How to Remove an ESXi Host from a Workload Cluster in VMware VCF 9

In VMware Cloud Foundation (VCF) 9, removing an ESXi host is called Host Decommissioning and must be done only through SDDC Manager.

❌ Do NOT remove hosts from vCenter
✅ Always use SDDC Manager

---

🧠 Simple Explanation (For Freshers)

• Remove Host = Safely take an ESXi server out of the cluster

• Common reasons:

  • Hardware replacement

  • Cluster downsizing

  • Host failure

  • Maintenance

VCF ensures:

• VMs are migrated

• vSAN data is evacuated

• NSX configuration is cleaned

---

📋 Prerequisites Before Removing Host

✅ Cluster Requirements

• Cluster must have minimum required hosts after removal

  • vSAN cluster → minimum 3 hosts

• Cluster health = Green

• No active alarms

✅ Host Requirements

• Host reachable

• No critical hardware errors

• Enough cluster capacity to evacuate data

---

🚀 Steps to Remove ESXi Host in VCF 9

---

🟢 Step 1: Login to SDDC Manager

1. Open SDDC Manager UI

2. Login as admin

3. Go to Inventory → Workload Domains

4. Select the Workload Domain

5. Click the Cluster

---

🟢 Step 2: Select Host to Remove

1. Go to Hosts tab

2. Select the ESXi host

3. Click Decommission Host

📌 Freshers Tip:
VCF checks if the cluster can survive without this host.

---

🟢 Step 3: Choose vSAN Data Evacuation Mode

VCF will ask for evacuation option:

• Ensure Accessibility (faster, less safe)

• Full Data Migration ✅ (recommended)

👉 Always choose Full Data Migration in production.

---

🟢 Step 4: Run Pre-Check Validation

VCF validates:

• vSAN capacity

• VM placement

• Network health

• NSX status

⚠️ Fix all errors before proceeding.

---

🟢 Step 5: Automated Host Removal

VCF automatically:

• Migrates VMs (vMotion)

• Evacuates vSAN data

• Removes host from cluster

• Cleans NSX configuration

• Removes host from inventory

⏱️ Time: 30–90 minutes (depends on data size)

---

🟢 Step 6: Verify Removal

After completion:

• Host no longer in cluster

• vSAN health = Green

• No NSX errors

• Cluster capacity updated

🎉 Host removal completed safely.

---

🔧 Post-Removal Actions (Recommended)

• Power off or repurpose the host

• Update capacity planning

• Check alarms

• Document change

---

⚠️ Common Errors & Fixes

Error	Cause	Fix
Cannot remove host	Minimum host count	Add host first
vSAN evacuation stuck	Low free space	Add capacity
VM migration fails	VM pinned	Manually vMotion
Validation fails	Health issues	Fix alarms

---

❌ What NOT To Do

• ❌ Do not remove host in vCenter

• ❌ Do not force maintenance mode

• ❌ Do not skip vSAN evacuation

• ❌ Do not power off host early

---

🎯 Why Use SDDC Manager?

• Keeps lifecycle management intact

• Prevents data loss

• VMware-supported workflow

• Ensures NSX & vSAN cleanup

---

🏁 Conclusion

Removing an ESXi host in VCF 9 is safe and fully automated when done via SDDC Manager.

For freshers:

Validate → Evacuate → Decommission

---

📌 Blog Series

VMware Cloud Foundation 9 – Install | Expand | Remove | Upgrade

---

 How to Expand a Workload Cluster in VMware VCF 9 (Add Hosts)

In VMware Cloud Foundation (VCF) 9, expanding a workload cluster means adding new ESXi hosts to an existing cluster using SDDC Manager.

❌ Never add hosts directly in vCenter
✅ Always expand clusters via SDDC Manager

---

🧠 Simple Explanation (For Freshers)

• Expand Cluster = Add more ESXi hosts

• Purpose:

  • More compute (CPU/RAM)

  • More storage (vSAN)

  • Better performance & scalability

---

📋 Prerequisites Before Expanding Cluster

✅ ESXi Host Must Be

• Fresh installed (no VMs)

• Same ESXi version as cluster

• Same hardware model (recommended)

• Root password known

• DNS & NTP configured

🌐 Network Ready

• Management network reachable

• vMotion configured

• vSAN network ready

• NSX TEP VLAN available

• MTU ≥ 1600 (important)

---

🚀 Steps to Expand Workload Cluster in VCF 9

---

🟢 Step 1: Add ESXi Host to VCF Inventory (If Not Added)

1. Login to SDDC Manager

2. Go to Inventory → Hosts

3. Click Add Host

4. Enter ESXi details

5. Complete validation

📌 Host must be visible in inventory before cluster expansion.

---

🟢 Step 2: Navigate to Workload Cluster

1. Go to Inventory → Workload Domains

2. Select the domain

3. Click the Cluster to expand

---

🟢 Step 3: Start Expand Cluster Workflow

1. Click Add Host to Cluster

2. Select available ESXi host(s)

3. Assign host to the cluster

👉 You can add one or multiple hosts at a time.

---

🟢 Step 4: Validation & Configuration

VCF automatically checks:

• ESXi compatibility

• Disk eligibility for vSAN

• Network & MTU

• NSX readiness

⚠️ Fix all validation errors before proceeding.

---

🟢 Step 5: Automated Expansion

VCF will automatically:

• Add host to vCenter cluster

• Configure vSAN disks

• Create NSX TEP

• Apply host profiles

⏱️ Time: 20–40 minutes per host

---

🟢 Step 6: Verify Expansion

After completion, verify:

• Host status = Connected

• vSAN health = Green

• NSX = Up

• Cluster capacity increased

🎉 Cluster expansion completed successfully.

---

🔧 Post-Expansion Best Practices

• Disable SSH on ESXi host

• Check compliance status

• Rebalance workloads (optional)

• Monitor performance

---

⚠️ Common Errors & Fixes

Error	Cause	Fix
Validation failed	DNS issue	Fix forward/reverse DNS
vSAN error	Dirty disks	Clear partitions
NSX TEP error	MTU mismatch	Verify end-to-end MTU
Host not listed	Not in inventory	Add host first

---

❌ What NOT To Do

• ❌ Do not add host directly in vCenter

• ❌ Do not manually claim disks

• ❌ Do not change host networking

• ❌ Do not skip validation

---

🎯 Why Expand via SDDC Manager?

• Keeps cluster compliant

• Enables lifecycle management

• VMware-supported method

• Prevents configuration drift

---

🏁 Conclusion

Expanding a Workload Cluster in VCF 9 is a safe and fully automated process when done through SDDC Manager.

For freshers:

Add host → Validate → Let VCF automate

---

📌 Blog Series

VMware Cloud Foundation 9 – Beginner to Advanced

---

 How to Add a Workload Cluster in VMware VCF 9 (Step-by-Step)

In VMware Cloud Foundation (VCF) 9, a Workload Cluster is created inside a Workload Domain using SDDC Manager only.

❌ Do NOT create clusters directly in vCenter
✅ Always use SDDC Manager

---

🧠 Simple Understanding (For Freshers)

• Workload Domain → Logical boundary for applications

• Workload Cluster → Where your VMs actually run

• SDDC Manager → Controls and automates everything

---

📋 Prerequisites Before Adding Workload Cluster

✅ Environment Must Be Healthy

• SDDC Manager → Healthy

• Workload Domain → Healthy

• No active alarms

🖥️ ESXi Hosts Required

• Minimum 3 ESXi hosts (vSAN cluster)

• Hosts already added to VCF inventory

• Same ESXi version & hardware type

🌐 Network Ready

• Management network

• vMotion network

• vSAN network

• NSX overlay (TEP)

• MTU configured (1600+)

---

🚀 Steps to Add Workload Cluster in VCF 9

---

🟢 Step 1: Login to SDDC Manager

1. Open SDDC Manager UI

2. Login with admin user

3. Go to Inventory → Workload Domains

4. Select your Workload Domain

---

🟢 Step 2: Start Create Cluster Workflow

1. Click Add Cluster

2. Select Cluster Type

   • vSAN (most common)

   • VMFS (optional)

📌 Freshers Tip:
👉 Choose vSAN unless storage is external.

---

🟢 Step 3: Select ESXi Hosts

1. Select available ESXi hosts

2. Assign hosts to the cluster

3. Validate host compatibility

⚠️ Hosts must not be part of another cluster.

---

🟢 Step 4: Configure Cluster Settings

Provide:

• Cluster name

• vSAN configuration

• Fault domain (optional)

• NSX configuration (auto)

VCF will:

• Configure vSAN

• Create NSX TEPs

• Apply host profiles

---

🟢 Step 5: Run Validation & Deploy

1. Run pre-check

2. Fix any errors

3. Click Finish / Deploy

⏱️ Time: 30–60 minutes

---

🟢 Step 6: Verify Cluster Creation

After completion:

• Cluster visible in vCenter

• vSAN health = Green

• NSX status = Up

• Hosts = Connected

🎉 Workload cluster is ready for VMs.

---

🔧 Post-Creation Best Practices

• Create resource pools (optional)

• Verify storage policies

• Test VM deployment

• Monitor cluster health

---

⚠️ Common Errors & Fixes

Issue	Cause	Fix
Validation fails	MTU mismatch	Verify MTU
vSAN error	Disk issue	Clean disks
NSX error	VLAN missing	Check network
Host unavailable	Already used	Remove & retry

---

❌ What NOT To Do

• ❌ Do not create cluster in vCenter

• ❌ Do not modify host settings manually

• ❌ Do not skip validation

---

🎯 Why Use SDDC Manager?

• Keeps environment compliant

• Enables lifecycle management

• VMware-supported approach

• Prevents configuration drift

---

🏁 Conclusion

Adding a Workload Cluster in VCF 9 is simple and safe when done through SDDC Manager.
For freshers, follow the workflow exactly and avoid manual changes.

SDDC Manager = Automation + Support + Stability

---

📌 Blog Series

VMware Cloud Foundation 9 – Installation | Upgrade | Expansion

---

🔄VMware Cloud Foundation Upgrade from 8 to 9 (Step-by-Step Guide)

Upgrading from VCF 8 to VCF 9 is a controlled, SDDC-Manager-driven lifecycle process.
You must not upgrade components manually.

✅ Supported Method → SDDC Manager only
❌ Unsupported → Direct vCenter / ESXi upgrades

---

🧠 What Does VCF 8 → 9 Upgrade Mean?

When you upgrade VCF:

• SDDC Manager is upgraded

• vCenter Server is upgraded

• ESXi hosts are upgraded

• NSX is upgraded

• vSAN components are aligned

All upgrades are orchestrated by SDDC Manager.

---

📋 Pre-Upgrade Checklist (VERY IMPORTANT)

✅ Infrastructure Readiness

• All domains Healthy

• No alarms in vCenter / NSX

• vSAN health = Green

• Enough free datastore space (minimum 30%)

✅ Backup (Mandatory)

• SDDC Manager backup

• vCenter backup

• NSX Manager backup

⚠️ Never start upgrade without backups.

---

🧩 Upgrade Flow Overview

VCF follows this fixed order:

1. SDDC Manager

2. Management Domain

3. Workload Domains

4. ESXi Hosts

You cannot change the order.

---

🚀 Step-by-Step VCF Upgrade 8 → 9

---

🟢 STEP 1: Upgrade SDDC Manager

1. Login to SDDC Manager UI

2. Go to Lifecycle Management

3. Download VCF 9 bundles

4. Run pre-check

5. Start upgrade

⏱️ Time: ~45–60 minutes

📌 After this step, system understands VCF 9 workflows.

---

🟢 STEP 2: Upgrade Management Domain

This includes:

• vCenter

• NSX Managers

• ESXi hosts (management cluster)

Actions

1. Select Management Domain

2. Run pre-check

3. Resolve warnings

4. Start upgrade

⏱️ Time: 2–3 hours

⚠️ Do NOT interrupt.

---

🟢 STEP 3: Upgrade Workload Domains

Repeat for each domain:

1. Select workload domain

2. Upgrade vCenter

3. Upgrade NSX

4. Upgrade ESXi hosts

⏱️ Depends on host count

👉 Domains are upgraded one by one.

---

🟢 STEP 4: ESXi Host Upgrade (Automated)

VCF automatically:

• Puts host in maintenance mode

• Migrates VMs

• Upgrades ESXi

• Reboots host

• Brings host back

📌 Zero manual intervention.

---

🔍 Post-Upgrade Validation (Must Do)

After upgrade:

• Check domain status = Healthy

• Verify ESXi versions

• Check NSX segments

• Validate VM connectivity

• Review alarms

---

⚠️ Common Upgrade Issues & Fix

Issue	Cause	Fix
Pre-check fails	Snapshot exists	Remove snapshots
NSX upgrade stuck	MTU mismatch	Verify MTU
Host upgrade fails	VM pinned	vMotion manually
Bundle error	Repo issue	Re-sync bundles

---

❌ What NOT To Do During Upgrade

• ❌ Do not reboot hosts manually

• ❌ Do not login to ESXi UI

• ❌ Do not upgrade vCenter separately

• ❌ Do not stop SDDC Manager services

---

🎯 Why Upgrade to VCF 9?

VCF 9 brings:

• Faster lifecycle management

• Better security hardening

• Improved NSX performance

• Enhanced automation

• Long-term VMware support

---

🏁 Conclusion

Upgrading VCF 8 to 9 is safe and predictable when:

• Pre-checks are clean

• Backups are taken

• Upgrade is done only via SDDC Manager

Plan → Validate → Upgrade → Verify

---

📌 Blog Series

VMware Cloud Foundation 9 – Install | Upgrade | Troubleshoot

---