VMware ESXi and vSphere Cluster Management

Configure VMware vCenter Server Appliance Network and Initial Settings

Learn how to configure VCSA networking, DNS, the appliance management interface, and the historical vSphere web client in a lab deployment.

Configuration goal and deployment state

The vCenter Server Appliance (VCSA) is a prepackaged virtual appliance that provides VMware vCenter Server services. Before administrators can use its appliance management interface or vSphere client, the appliance must have reachable network connectivity.

A newly deployed appliance can receive its initial network configuration from DHCP. DHCP automatically assigns network information to clients. In an environment without DHCP, or when a stable infrastructure address is required, configure a static IP address manually.

Method	When to Use	Advantages	Considerations
DHCP	Initial lab deployment or an environment that manages appliance reservations through DHCP	Provides an address automatically and can simplify first access	The address may change unless a reservation is used; long-term infrastructure services commonly require planned, stable addressing
Static IP configuration	Production-like labs and environments requiring a predictable appliance address	Creates a stable address for DNS records, browser URLs, certificates, and integrations	Every value must be correct, and the address must not conflict with another device

When DHCP is available, identify the assigned address from the DHCP lease table or the appliance console. When DHCP is unavailable, plan the static settings before attempting browser access.

Network information to collect

Collect the following information before configuring the appliance:

Setting	Example Value	Purpose	Validation Method
Appliance hostname	vcsa	Short host name used to identify the appliance	Confirm it follows the organization's naming standard
FQDN	vcsa.lab.example	Complete DNS name of the appliance	Plan a forward DNS record and, where required, a reverse record
IPv4 address	192.168.10.50	Address assigned to the appliance	Confirm it is unused and belongs to the intended subnet
Subnet mask	255.255.255.0	Defines the local IPv4 subnet	Compare it with the network design
Default gateway	192.168.10.1	Router used to reach networks outside the local subnet	Confirm it is reachable and belongs to the appliance subnet
Primary DNS server	192.168.10.10	Resolves hostnames and FQDNs	Confirm the appliance can reach the server
Secondary DNS server	192.168.10.11	Provides alternate name resolution when available	Confirm it is reachable and authorized for the environment

DNS maps hostnames and fully qualified domain names to IP addresses. A FQDN is the complete DNS name of a system, such as vcsa.example.com. Before production use, plan the relationship among the hostname, FQDN, IP address, forward DNS lookup, reverse DNS lookup, and browser URLs.

Access the appliance console

Open the vSphere Client and locate the deployed, powered-on appliance virtual machine.
Open the virtual machine console.
Choose the appliance login option shown by the console.
Authenticate as the appliance operating-system administrator.

For the historical release described in this lesson, a controlled lab may use the historical credentials root and vmware. Do not retain these credentials in a production or shared environment. Change the password immediately and protect the replacement credential.

Configure networking from the appliance console

After signing in, run the appliance's interactive network configuration utility:

/opt/vmware/share/vami/vami_config_net

VAMI means the virtual appliance management interface and its related configuration tooling. The menu numbering in this utility is specific to the historical appliance release, so use the displayed labels rather than assuming that a particular number is identical across versions.

Select the menu item for configuring the IP address.
Choose the static IPv4 option when manually assigning an address.
Enter an unused IPv4 address and the associated subnet mask or prefix information when prompted.
Configure the default gateway.
Enter the primary DNS server and a secondary DNS server when one is available.
Enter the appliance FQDN, for example vcsa.lab.example.
Review the resulting address, mask, gateway, DNS servers, hostname, and FQDN before committing or exiting.
Leave the configuration utility after validation, then leave the shell:

exit

Use an address that belongs to the correct subnet and is not assigned to another device. The address selected here becomes part of later browser URLs, such as https://vcsa.lab.example:5480 or the equivalent URL using the IP address.

Example: manual static configuration

Suppose the lab network is 192.168.10.0/24. A consistent configuration could be:

FQDN: vcsa.lab.example
IPv4 address: 192.168.10.50
Subnet mask: 255.255.255.0
Default gateway: 192.168.10.1
Primary DNS: 192.168.10.10
Secondary DNS: 192.168.10.11

Every value must match the network design. The FQDN should resolve to 192.168.10.50, and the address should be reserved for the appliance or otherwise confirmed unused.

Open the appliance management interface

After the appliance has a reachable address, connect to the appliance management interface over HTTPS. The TCP 5480 endpoint is the historical HTTPS management port for this appliance generation.

https://[APPLIANCE_NAME_OR_IP_ADDRESS]:5480

For the example configuration, use:

https://vcsa.lab.example:5480

If DNS is not yet available, use the configured IP address instead:

https://192.168.10.50:5480

Log in with the appliance administrator account. This account is separate from the vCenter authentication accounts used by the vSphere client. A browser may show a certificate warning during initial setup; use HTTPS and validate the warning according to the organization's certificate policy rather than ignoring certificate errors automatically.

Complete initial setup in the management interface

Accept the EULA, or End User License Agreement, when the initial setup presents it.
Choose whether to participate in telemetry or technical-data collection according to organizational policy.
Review the available setup choices.
Use the default setup path when appropriate. In this historical workflow, default setup can defer advanced network, SSO, and database-related choices until later.
Review the complete configuration summary carefully.
Start the configuration process and wait for the appliance services to initialize.

SSO, or Single Sign-On, is the authentication framework used by vCenter-related services. Do not confuse SSO credentials with the appliance operating-system administrator credential used for appliance management.

Connect to the vSphere client

After initial appliance configuration completes, open the historical vSphere web client:

https://[APPLIANCE_NAME_OR_IP_ADDRESS]:9443/vsphere-client

For the example configuration:

https://vcsa.lab.example:9443/vsphere-client

TCP 9443 is the historical HTTPS port for the vSphere web client in this appliance generation. If DNS is unavailable, substitute the configured IP address for the appliance name.

The vSphere Client is the management client used to access vCenter Server and managed virtual infrastructure. Use the appropriate vCenter or SSO credentials here, not automatically the appliance operating-system root credential.

Access endpoints

Interface	URL Format	Historical Port	Primary Use
Appliance management interface	`https://[APPLIANCE_NAME_OR_IP_ADDRESS]:5480`	TCP 5480	Appliance administration and initial setup
vSphere web client	`https://[APPLIANCE_NAME_OR_IP_ADDRESS]:9443/vsphere-client`	TCP 9443	vCenter inventory and virtual infrastructure management

Validate the completed configuration

Confirm that the configured IP address responds from the intended administrative network.
Confirm that the subnet mask or prefix is correct.
Confirm that the default gateway is on the appliance subnet and provides the expected routed access.
Confirm that the configured DNS servers are correct and reachable.
Confirm that the selected FQDN resolves to the configured address.
Confirm that the appliance management page opens over HTTPS on TCP 5480.
Confirm that the historical vSphere client opens over HTTPS on TCP 9443.
Record the address, hostname, FQDN, DNS servers, gateway, and protected credentials in deployment documentation.

Troubleshooting

The appliance cannot be reached after assigning a static address

Reopen the virtual machine console and review the address, subnet mask, gateway, DNS, and FQDN.
Confirm that the address is unused and that no IP conflict exists.
Confirm that the virtual NIC is connected to the correct port group and VLAN.
Confirm that the gateway belongs to the appliance subnet.

The management URL on port 5480 does not open

Try the configured IP address instead of the hostname.
Verify that the URL uses HTTPS and port 5480.
Confirm that firewalls permit TCP 5480 from the trusted administrative network.
Wait for startup and configuration tasks to finish before testing again.

The hostname does not resolve, but the IP address works

Verify the forward DNS record for the FQDN.
Verify reverse DNS where the environment requires it.
Confirm that the appliance is using the intended primary and secondary DNS servers.
Check the spelling of the configured FQDN.

The vSphere client on port 9443 cannot be reached

Confirm that the initial appliance setup completed successfully.
Test with the configured IP address.
Verify that network policy permits TCP 9443.
Confirm that the deployed product version uses this historical endpoint.

Login fails

Identify whether the target is the appliance management interface or the vSphere client.
Use the credential type appropriate to that interface.
Check whether the historical default password was changed.
Follow approved password recovery procedures if the required administrator credential is unavailable.

Security and operational cautions

Change historical default passwords immediately outside an isolated training lab.
Use HTTPS for both management endpoints.
Validate browser certificate warnings according to organizational policy.
Restrict TCP 5480 and TCP 9443 to trusted administrative networks.
Document addressing, DNS, gateway, hostname, FQDN, and credential ownership.
Plan identity and DNS changes carefully because later changes can affect certificates, services, and integrations.

For a focused reference, see vCenter Server Appliance Configuration.