VMware ESXi and vSphere Cluster Management

Basic VMware ESXi Host Configuration Using the DCUI

Learn how to configure a static ESXi management IP address through the DCUI, validate connectivity, and connect to the ESXi Host Client or vSphere Client.

After installing VMware ESXi, the physical server becomes an ESXi host: a server running VMware’s bare-metal hypervisor for virtual machines. Before you can administer that host remotely, it needs a working management network.

This lesson shows how to configure the management network locally through the Direct Console User Interface (DCUI), assign a static IPv4 address, apply the settings, and connect through a browser-based management interface.

Why Initial ESXi Configuration Matters

The management network is the network path used to administer the ESXi host. It carries administrative traffic such as connections to the ESXi Host Client, vSphere Client, monitoring systems, and management services.

The management IP address identifies the host on that network. Administrators use this address, or a DNS name that resolves to it, to open the host management interface.

Management access is different from virtual machine networking. The management network allows administrators to control the host. Virtual machine networks allow guest operating systems to communicate with other systems. They may use different virtual switches, physical uplinks, VLANs, and IP subnets.

A host can sometimes run virtual machines while remote management is unavailable, but that is not a usable or safe operating state. Configure and test management access before relying on the host for normal administration.

What Is the DCUI?

The Direct Console User Interface (DCUI) is the local, text-based ESXi console displayed directly on the server. It provides basic host setup and recovery functions without requiring network access.

DCUI is especially useful when:

• ESXi has just been installed and remote management has not yet been configured.
• The current management address is unknown or incorrect.
• A network change has made the host unreachable.
• You need to inspect or repair basic management settings from the physical or out-of-band console.

Administrative credentials are required to enter System Customization, the DCUI area containing host-level configuration options.

Prepare the Management Network Values

Collect the network information before changing the host. The values must match the intended management subnet, switch configuration, and VLAN design.

Choose an address approved for the deployment. It should not be assigned to another device and should normally be outside the active DHCP pool unless your organization uses a documented DHCP reservation.

Access System Customization in the DCUI

1. Boot the ESXi host and wait for the main ESXi console screen to appear.
2. Use the system customization function-key shortcut shown on the console. On standard ESXi DCUI screens, this is commonly F2.
3. Enter the administrative credentials configured during ESXi installation.
4. Open the Configure Management Network area.
5. Locate the IPv4 Configuration option.

The exact wording or function-key behavior can vary with the ESXi release, console type, and remote-console software. If the shortcut does not work, use the physical keyboard or the server’s out-of-band console and verify that function keys are being passed through.

Choose DHCP or Static IPv4 Configuration

DHCP, or Dynamic Host Configuration Protocol, automatically supplies network settings to a device. Static configuration requires an administrator to enter the values manually.

Management interfaces commonly use static addresses because administrators, monitoring systems, DNS records, and automation need a dependable destination. A DHCP reservation can provide similar stability, but it must be documented and maintained by the network team.

Configure a Static Management Address

1. In IPv4 Configuration, select the option to use a static IPv4 address and network configuration.
2. Enter the approved management IPv4 address.
3. Enter the subnet mask, such as 255.255.255.0.
4. Enter the default gateway, such as 192.168.50.1.
5. Return to the management network settings and review the values before applying them.

For a lab example, the configuration could be:

IPv4 address:  192.168.50.10
Subnet mask:   255.255.255.0
Default gateway: 192.168.50.1
DNS server:    192.168.50.5
Host name:     esxi-lab01.example.local
Management VLAN: 50

These are example values only. Replace them with addresses appropriate for your network. The address, mask, gateway, VLAN, and physical switch configuration must agree. For example, placing the host on a switch port that delivers VLAN 20 while configuring management for VLAN 50 can make the host unreachable.

DNS server, host name, and domain settings are separate from the IPv4 address configuration, although they are commonly completed during the same initial setup. Configure them according to your organization’s naming and DNS design.

Apply and Validate the Changes

1. Confirm the new management network settings in the DCUI.
2. Accept the prompt to apply the changes.
3. Allow the management network to restart if ESXi displays a restart warning.
4. Return to the main console screen and verify that the displayed management address is the new address.
5. From an administrator workstation on a permitted, reachable network, test connectivity to the new address.

Where network policy permits, test basic reachability with ICMP. Also test the management service itself by opening the HTTPS address in a browser. A successful ping does not by itself prove that HTTPS management access is allowed, and a blocked ping does not always prove that HTTPS is unavailable.

https://<esxi-management-ip-or-hostname>/ui/

For the example host, the destination would be:

https://192.168.50.10/ui/

Connect with the ESXi Host Client or vSphere Client

The ESXi Host Client is the web interface served directly by a standalone ESXi host. Open the HTTPS URL using the configured management IP address or a resolvable host name.

The vSphere Client is VMware’s management interface for ESXi hosts and vCenter Server environments. In a vCenter-managed environment, administrators commonly connect to vCenter Server and manage hosts through it. For a standalone host, connect directly to the ESXi Host Client.

1. From the administrator workstation, browse to the host’s HTTPS management URL.
2. Inspect the certificate warning and handle it according to organizational policy. A newly installed host may use a certificate that is not trusted by the workstation.
3. Sign in with an ESXi account authorized to administer the standalone host.
4. Confirm that host status, storage, networking, and virtual machine management views are available.

Example: Move from Temporary DHCP to a Permanent Address

1. Use the DCUI to identify the temporary address currently assigned by DHCP.
2. Plan an approved static address outside the DHCP pool, or create a documented DHCP reservation.
3. Replace the DHCP selection with the approved static address, subnet mask, and gateway in the DCUI.
4. Apply the change and wait for the management network to restart.
5. Update bookmarks, inventory records, monitoring configuration, and DNS records if applicable.

Initial Configuration Checklist

• Record the ESXi host name and domain.
• Record the management IP address and subnet mask or prefix length.
• Record the default gateway and DNS server addresses.
• Document the management VLAN ID, physical switch port, and uplink.
• Confirm that the address is not duplicated or unintentionally inside an active DHCP pool.
• Verify access from an authorized management workstation.
• Change temporary or shared credentials according to security policy.
• Configure time synchronization, such as approved NTP sources.
• Limit management access to authorized networks and administrators.

Troubleshooting Management Connectivity

The Host Cannot Be Opened in a Browser

Likely causes include an incorrect IP address, subnet mask, or gateway; an unreachable administrator workstation; a management VLAN mismatch; a physical uplink problem; or a firewall and routing policy that blocks HTTPS management traffic.

1. Review the address displayed in the DCUI.
2. Confirm that the physical network link is active and that the correct uplink is connected.
3. Verify the switch port’s access or trunk configuration and its management VLAN behavior.
4. Test ICMP reachability where permitted.
5. Confirm that the administrator workstation has a route to the management subnet.
6. Check whether security policy permits HTTPS management traffic.

The Address Conflicts with Another Device

A conflict can occur when a static address is inside an active DHCP pool, already belongs to another infrastructure device, or was assigned without updating address inventory.

• Disconnect or isolate the host if duplicate-address behavior is suspected.
• Check DHCP leases, IP address management records, and network monitoring.
• Assign an approved unused address and document the change.

The Host Is Reachable by IP but Not by Name

Verify the DNS server settings, host name, and domain configured on the host. Confirm that a forward DNS record exists and resolves correctly from the administrator workstation. Use the IP address temporarily while correcting DNS.

You Cannot Enter System Customization

Confirm the administrative credentials established during installation. If the function key does not work, use the physical console or the server’s out-of-band management console. Check keyboard mapping and whether the remote console passes function keys correctly.

Exam-Relevant Notes

• DCUI is local to the ESXi host and is useful before remote management is available.
• The management IP address is used to reach host administration tools; it is not automatically the address used by virtual machines.
• A default gateway is needed when management traffic must reach networks outside the local subnet.
• DNS name resolution and host naming are separate from basic IP address assignment.
• A management VLAN must match the physical switch and network design.
• Changing management network settings can restart the management network and temporarily interrupt remote access.
• A static address must be unique and documented.

Once the host is reachable, continue with host name and DNS configuration, management VLAN validation, time synchronization, security hardening, physical uplink and vSwitch configuration, and—where applicable—adding the host to vCenter Server.

Return to the Basic ESXi Configuration guide for the related setup sequence.