VMware ESXi and vSphere Cluster Management
Basic VMware ESXi Host Configuration Using the DCUI
Learn how to configure an ESXi management network and static IP address with the Direct Console User Interface (DCUI), then verify remote access and troubleshoot connectivity.
A newly installed VMware ESXi host is a bare-metal hypervisor installed directly on server hardware. The physical server running ESXi is called an ESXi host, and it provides computing resources for virtual machines.
Before you can administer the host remotely, it needs reachable management networking. This lesson explains how to configure that network and assign a static IP address using the Direct Console User Interface (DCUI).
What Initial ESXi Configuration Accomplishes
Initial configuration gives administrators a reliable way to reach the ESXi host after installation. The management connection is used for tasks such as opening the ESXi Host Client, connecting with the vSphere Client, monitoring the host, and adding the host to vCenter Server.
The management network is the network interface and IP configuration used to administer ESXi. It is separate conceptually from virtual machine networking:
- Host management networking carries administration traffic to and from ESXi itself.
- Virtual machine networking connects guest operating systems to other systems through virtual switches, port groups, physical uplinks, and VMkernel networking.
These networks can use different VLANs, adapters, or security policies. Configuring the management IP does not automatically configure the network connectivity of virtual machines.
When remote access is not yet available, configuration is performed locally from the server console. The console may be the physical keyboard and display attached to the server or a remote console supplied by the server's hardware management system.
Prerequisites
- A completed ESXi installation.
- Access to the physical server console or a hardware remote-management console.
- An ESXi administrative account and password created or assigned during installation.
- Basic knowledge of IP addresses, subnet masks, and default gateways.
- An approved management network plan containing the address, subnet, gateway, and any required DNS or hostname information.
Understanding the DCUI
The Direct Console User Interface (DCUI) is ESXi's local, text-based administration interface. It appears on the physical server console or through a compatible remote server console.
The DCUI supports initial configuration and basic network troubleshooting without requiring the browser-based ESXi Host Client or the vSphere Client. It is especially useful when the host has no working management address or when a remote configuration change has interrupted access.
The interface is keyboard-driven. Function keys, arrow keys, Enter, and other keyboard controls are used to select menus and confirm settings.
Open System Customization
- Open the ESXi console on the physical server or through the server's hardware remote console.
- From the ESXi console screen, press F2 to open System Customization.
- Authenticate with an ESXi administrative account. The credentials created or assigned during installation are required.
- From the System Customization menu, select Configure Management Network.
System Customization is the DCUI menu used after authentication to change host-level settings, including management networking and other essential configuration.
Configure the Management Network IP Address
Open IP Configuration
- In Configure Management Network, select IP Configuration.
- Review the available addressing choices.
- Choose DHCP or static addressing according to the approved network design.
DHCP is a service that automatically assigns network settings to a host. DHCP can be appropriate when the organization reserves the address or reliably tracks the lease and the resulting management address.
A static IP address is manually assigned and intended to remain stable. Static addressing is commonly preferred when administrators need a predictable endpoint for direct management, monitoring, documentation, and infrastructure tools.
Enter static values
When static addressing is required, select the static IP configuration option and enter:
- IP address: The approved address for the ESXi management interface.
- Subnet mask: The value that defines the boundary of the local IP network.
- Default gateway: The router used to reach systems outside the local management subnet.
Use values that belong to the host's management network. For example, an organization might assign an address such as 192.0.2.25, a subnet mask of 255.255.255.0, and a gateway of 192.0.2.1 in a documentation or lab network. Do not copy example values into production unless they are part of your approved network plan.
Optional DNS and hostname settings
Depending on the environment, configure DNS and hostname settings under the appropriate management network or DNS configuration menus. DNS server values allow ESXi to resolve names, while a hostname gives the host a recognizable identity. Obtain these values from the network plan or the administrator responsible for DNS.
Apply the configuration
- Review every field for typing errors.
- Accept or apply the changes before leaving the menu.
- If ESXi asks whether to apply the changes or restart management networking, confirm the operation.
- Note the resulting management IP address shown by the console.
Changes must be accepted before they become active. Leaving the menu without applying them can leave the previous DHCP or static settings in place.
Static Management Network Values
| Setting | Purpose | Example format | Where to obtain it |
|---|---|---|---|
| IP address | Stable address used to reach the ESXi host | 192.0.2.25 | Approved management IP allocation or IP address database |
| Subnet mask | Defines the local IP network boundary | 255.255.255.0 | Management subnet design |
| Default gateway | Router used to reach destinations outside the local subnet | 192.0.2.1 | Network administrator or routing plan |
| DNS server | Resolves host and service names | 192.0.2.53 | Organizational DNS design |
| Hostname | Human-readable identity for the ESXi host | esxi01.example.test | Naming standard and DNS administrator |
DCUI Configuration Workflow
| Step | DCUI location | Administrator action | Expected result |
|---|---|---|---|
| Open customization | ESXi console | Press F2 | System Customization authentication prompt appears |
| Authenticate | Authentication prompt | Enter an ESXi administrative account and password | System Customization menu opens |
| Open management network settings | System Customization | Select Configure Management Network | Management network options are displayed |
| Configure IP settings | Configure Management Network > IP Configuration | Choose DHCP or static addressing and enter the required values | New management network values are ready to be applied |
| Apply changes | IP Configuration and confirmation prompt | Accept the changes and confirm any restart of management networking | ESXi activates the new settings |
| Connect remotely | Administrator workstation | Browse to the management IP or use the vSphere Client | The ESXi host's remote management interface responds |
Verify Remote Host Access
After applying the configuration, use the configured management IP address from an administrator workstation. The ESXi Host Client is the browser-based management interface available directly from an ESXi host. Open a browser to the host's HTTPS address using the management IP, or use the vSphere Client to connect to the host or to a vCenter Server environment.
For example, if the management address is 192.0.2.25, use the corresponding secure browser address for that host. The workstation must be connected to a network that can reach the ESXi management subnet.
Confirm that:
- The host responds from the administrator workstation.
- The expected ESXi Host Client sign-in page appears in a browser.
- The management IP shown in the console matches the address being used.
- The workstation has suitable routing or local network access to the management subnet.
An initial browser-based connection may display a certificate warning because a newly installed host can use a certificate that is not trusted by the workstation. Evaluate the warning and proceed only according to your organization's security policy. Do not treat an untrusted certificate warning as proof that the connection is safe.
Choosing DHCP or Static Addressing
| Choice | Use when | Important consideration |
|---|---|---|
| DHCP | The organization reserves or reliably tracks the assigned management address | The address can change unless reservation and lease management are controlled |
| Static IP | Administrators need a predictable endpoint for management, monitoring, and documentation | The address must be selected carefully and kept unique on the network |
For a standalone host that must be reachable consistently, a static address is often the simplest operational choice. The correct choice depends on the organization's address management and security practices.
Basic Management Network Troubleshooting
If the browser or vSphere Client cannot connect after configuration, the problem may be at several layers. A valid value entered in the DCUI is not enough if the physical link, switch port, VLAN, or routing is incorrect.
Check the host and switch connection
- Confirm the network cable is connected to the intended physical NIC.
- Check link lights or the hardware management console for physical link status.
- Verify that the switch port is enabled and connected to the expected switch.
- Confirm the switch port's VLAN configuration matches the ESXi management network design.
- Verify that the configured management interface has an active uplink.
Check IP addressing
- Confirm the IP address was typed correctly.
- Confirm the subnet mask matches the management subnet.
- Confirm the default gateway is on the same local subnet as the management IP.
- Check that another device is not already using the selected address.
- Verify that DHCP was not left selected when static addressing was intended.
- Confirm that the changes were accepted and applied.
Check workstation reachability
- Verify that the administrator workstation is connected to the correct network or management VLAN.
- Check routing and firewall rules between the workstation and the management subnet.
- Confirm that the workstation is using the correct host address rather than an old DHCP address.
- Check whether network access controls or security policies block ESXi management traffic.
When remote access fails, the DCUI remains available at the server console. Return to Configure Management Network, reopen IP Configuration, correct the address, mask, or gateway, and apply the changes again.
Common Failure Scenarios
The client cannot connect after configuration
Likely causes include an incorrect IP address, subnet mask, or gateway; an unreachable administrator workstation; a physical link problem; or assignment to the wrong VLAN. Use the DCUI to review the settings, confirm that the address is valid and unused, verify the switch port and uplink, and confirm routing to the management subnet.
The expected static address is not active
DHCP may still be selected, the changes may not have been accepted, or a field may contain a typing error. Reenter IP Configuration, confirm that static addressing is selected, review each field, and apply the corrected configuration.
System Customization does not open
Check the administrative credentials first. If the password is correct, confirm that keyboard focus is on the ESXi console. A remote console interface may not pass function keys correctly, so use the server's local console or adjust the remote console settings to ensure that F2 reaches ESXi.
Exam-Relevant Notes
- The DCUI is a local, keyboard-driven interface for essential ESXi configuration and troubleshooting.
- F2 opens System Customization from the ESXi console.
- Administrative credentials are required to enter System Customization.
- The management IP is used to access the ESXi Host Client or connect with the vSphere Client.
- A management network configuration is distinct from virtual machine networking.
- A static configuration requires an IP address, subnet mask, and default gateway.
- Incorrect VLAN, uplink, switch, routing, or physical link settings can prevent remote access even when the IP fields are correct.
- The DCUI is the recovery path for correcting management settings when remote access is unavailable.
Next Steps
Once the host is reachable, you can continue with adding the ESXi host to vCenter Server inventory or study the broader VMware ESXi online course. Further host administration may include configuring DNS and hostname settings, management VLANs, virtual switches, VMkernel adapters, and secure administrative access.