Stackvora.tech

ESXi 8: install and join to vCenter

Deploying new ESXi hosts and integrating them into an existing vCenter Server environment is a fundamental task for any VMware administrator. This guide…

Deploying new ESXi hosts and integrating them into an existing vCenter Server environment is a fundamental task for any VMware administrator. This guide covers the end-to-end process for installing ESXi 8.0 Update 2 and adding it to a vCenter Server 8.0 Update 2 instance, focusing on practical steps and configuration details required for a successful setup in a production-ready state.

Preparation and Prerequisites

Before initiating the ESXi installation, several prerequisites must be met to ensure a smooth deployment and integration process. Neglecting these steps often leads to network connectivity issues or failed vCenter registration.

  • Hardware Compatibility: Verify that your server hardware (CPU, RAM, NICs, storage controllers) is listed on the VMware Compatibility Guide (VCG) for ESXi 8.0. Incompatible hardware, especially NICs, can prevent installation or lead to unstable operation.
  • Networking:
    • Dedicated management network VLAN (e.g., VLAN 100).
    • Static IP address for the ESXi host management interface (e.g., 192.168.100.10/24).
    • Default Gateway (e.g., 192.168.100.1).
    • DNS Server (e.g., 192.168.10.5).
    • Hostname for the ESXi host (e.g., esxi-01.stackvora.tech). Ensure both A and PTR records are created in DNS.
  • ESXi 8.0 ISO: Download the ESXi 8.0 Update 2 installer ISO from the VMware Customer Connect portal. Alternatively, use a vendor-customized ISO if available (e.g., HPE, Dell) which often includes updated drivers for specific hardware. The filename typically resembles VMware-VMvisor-Installer-8.0.2-22380479.x86_64.iso.
  • vCenter Server: Ensure your vCenter Server instance is running and accessible (e.g., vCenter 8.0 Update 2). The vCenter Appliance management interface is usually on port 5480 (https://vcenter.stackvora.tech:5480) and the vSphere Client on port 443 (https://vcenter.stackvora.tech/ui).
  • NTP Server: Identify an authoritative NTP server for time synchronization (e.g., pool.ntp.org or an internal NTP server).

ESXi 8.0 Installation

The installation process for ESXi 8.0 is largely consistent with previous versions, primarily a text-based, interactive wizard. The key is to select the correct installation target and set a strong root password.

Booting the Installer

Boot the server from the prepared ESXi 8.0 ISO. This can be done via a physical DVD drive, USB stick, or remotely using IPMI/iLO/DRAC virtual media. The server will load the ESXi installer kernel and initial ramdisk. After a few minutes, you will be presented with the welcome screen.

  1. On the welcome screen, press Enter to continue.
  2. Read and accept the End User License Agreement (EULA) by pressing F11.

Disk Selection and Password

The installer will scan for available storage devices. If multiple disks are present, especially if using a RAID controller, ensure you select the correct disk for ESXi installation. It is generally recommended to install ESXi on a dedicated boot device (e.g., a small SSD, M.2 drive, or even a USB drive, though USB is less common for critical systems now) separate from your VM datastores.

  1. Select the target disk for installation. For this example, we assume a single 120GB SSD: Use arrow keys to highlight the correct disk and press Enter.
  2. Choose the keyboard layout (default US is usually fine) and press Enter.
  3. Enter and confirm a strong root password. This password will be used for direct console access and SSH. VMware recommends a password of at least 7 characters with a mix of uppercase, lowercase, numbers, and special characters. Press Enter.
  4. The installer will present a confirmation screen. Verify the selected disk and confirm the installation by pressing F11.

The installation process will begin, typically taking 5-10 minutes. Once complete, you will be prompted to remove the installation media and reboot the host. Press Enter to reboot.

Initial Post-Installation Configuration (DCUI)

After the first boot, ESXi will load the Direct Console User Interface (DCUI). This text-based interface is crucial for initial network configuration before the host can be managed by vCenter or accessed via the vSphere Client.

Configuring Management Network

Access the DCUI by pressing F2. You will be prompted for the root password set during installation.


ESXi 8.0.2 build-22380479
(C) Copyright 2023 VMware, Inc.

VMware ESXi DCUI
Welcome to the VMware ESXi management interface.

Customize System/View Logs                 (F2)
Troubleshooting Options                    (F11)
Exit to continue Boot                     (ESC)
  1. Log in with the root user and its password.
  2. From the System Customization menu, select "Configure Management Network" and press Enter.
  3. Select "Network Adapters" and press Enter. Verify that the correct physical NIC is selected for management (e.g., vmnic0). If you have multiple NICs, ensure the appropriate one connected to your management network VLAN is chosen. Press Enter to accept.
  4. Select "VLAN (optional)" and press Enter. Enter your management VLAN ID (e.g., 100) and press Enter.
  5. Select "IPv4 Configuration" and press Enter.
    • Choose "Set static IPv4 address and network configuration".
    • Enter the IP Address (e.g., 192.168.100.10).
    • Enter the Subnet Mask (e.g., 255.255.255.0).
    • Enter the Default Gateway (e.g., 192.168.100.1).
    • Press Enter to accept these settings.
  6. Select "DNS Configuration" and press Enter.
    • Enter the Primary DNS Server (e.g., 192.168.10.5).
    • (Optional) Enter a Secondary DNS Server.
    • Enter the Hostname (e.g., esxi-01.stackvora.tech).
    • Press Enter to accept these settings.
  7. Press Esc to exit the "Configure Management Network" menu. You will be prompted to apply the changes and restart the management network. Press Y to confirm.

Testing Network Connectivity and Time Sync

After applying network changes, it's crucial to verify connectivity:

  1. From the System Customization menu, select "Test Management Network" and press Enter.
  2. Enter the default gateway IP, a DNS server IP, and the vCenter Server IP (if known). The test should succeed for all targets. If not, troubleshoot your cabling, switch port configuration, or VLAN tagging.
  3. (Optional but Recommended) Configure NTP for time synchronization. Select "Configure Management Network" again, then "IPv6 Configuration" (even if not using IPv6) to access the NTP settings.
    • Select "NTP Configuration".
    • Choose "Enable NTP Client".
    • Enter your NTP server IP or hostname (e.g., pool.ntp.org).
    • Press Enter to accept, then Esc and Y to apply.

Once network configuration is complete and tested, exit the DCUI by pressing Esc.

Adding the ESXi Host to vCenter Server

With the ESXi host now network-accessible, the final step is to add it to your vCenter Server environment using the vSphere Client.

Logging into vCenter and Creating a Datacenter

  1. Open a web browser and navigate to the vSphere Client URL (e.g., https://vcenter.stackvora.tech/ui).
  2. Log in with an administrative account (e.g., administrator@vsphere.local).
  3. In the Hosts and Clusters view, right-click on your vCenter Server instance and select "New Datacenter...".
  4. Provide a meaningful name for the Datacenter (e.g., Main_DC) and click "OK".

Adding the ESXi Host

  1. Right-click on the newly created Datacenter (e.g., Main_DC) and select "Add Host...".
  2. In the "Add Host" wizard:
    • Connect to Host: Enter the IP address or fully qualified domain name (FQDN) of the ESXi host (e.g., 192.168.100.10 or esxi-01.stackvora.tech). Click "Next".
    • User name and password: Enter root for the User name and the root password you set during installation. Click "Next".
    • Host Summary: Review the host's summary information. You may see a host certificate warning; click "OK" to accept it for now. Click "Next".
    • Assign license: Select an appropriate ESXi license. If you have an evaluation license or want to assign a permanent license later, you can choose "Assign a new license" or "Manage licenses later". Click "Next".
    • Lockdown mode: Decide whether to enable lockdown mode. For initial setup, it's often best to leave it "Disabled". You can enable it later after verifying full functionality. Click "Next".
    • VM location: Choose the datacenter folder where the host will reside (e.g., Main_DC). Click "Next".
    • Ready to complete: Review all settings. Click "Finish" to add the host.

vCenter Server will now connect to the ESXi host, import its configuration, and bring it under management. This process can take a few minutes. Once complete, the host will appear in the Hosts and Clusters inventory and its status should show as "Connected".

Common Pitfalls and Troubleshooting

  • DNS Resolution: Ensure forward (A record) and reverse (PTR record) DNS entries are correctly configured for the ESXi host. If DNS is not working, vCenter may struggle to communicate with the host, often reporting "Cannot contact the specified host (host is null)" or similar errors. Try to ping the ESXi host by hostname from the vCenter appliance and vice-versa.
  • Firewall: ESXi's default firewall configuration is usually sufficient for vCenter communication. However, if custom firewall rules are applied, ensure ports 902 (control/data) and 443 (HTTP/SOAP) are open inbound to the ESXi host from vCenter.
  • Incorrect IP/VLAN: Double-check the management IP, subnet mask, gateway, and VLAN ID configured via DCUI. A mismatch here is the most frequent cause of "Cannot connect to host" errors.
  • Duplicate IP Address: Verify that the static IP assigned to the ESXi host is not already in use on the network. Use ping -c 1 before assigning it.
  • Out-of-Date Drivers: If the ESXi installation fails or network adapters aren't detected, it's often due to missing or outdated drivers. Try a vendor-customized ESXi ISO or inject drivers using the VMware PowerCLI Image Builder.
  • Time Skew: Significant time differences between the ESXi host and vCenter Server can cause authentication failures (e.g., "A general system error occurred: Internal error"). Ensure NTP is correctly configured on both and clocks are synchronized.
  • Root Password Expiry: By default, the root password on ESXi does not expire. However, if configured through a host profile or security policy, an expired password can prevent vCenter from connecting.

Back to the knowledge base · Ask the AI assistant