6.7

Table Of Contents
Table 192. Management Node Log Directories (Continued)
Log Directory Description
vsphere-client VMware vSphere Web Client
vcha VMware High Availability Service (Linux only)
Platform Services Controller Logs
You can examine the following logs if a Platform Services Controller node deployment is chosen.
Table 193. Platform Services Controller Node Log Directories
Log Directory Description
cis-license VMware Licensing Service
sso VMware Secure Token Service
vmcad VMware Certificate Authority daemon
vmdird VMware Directory Service
For Platform Services Controller node deployments, additional runtime logs are located at
C:\ProgramData\VMware\CIS\runtime\VMwareSTSService\logs.
Troubleshooting MAC Address Allocation
In vSphere, certain restrictions on the range of MAC addresses that can be assigned to virtual machines
might cause lost of connectivity or inability to power on workloads.
Duplicate MAC Addresses of Virtual Machines on the Same
Network
You encounter loss of packets and connectivity because virtual machines have duplicate MAC addresses
generated by vCenter Server.
Problem
The MAC addresses of virtual machines on the same broadcast domain or IP subnet are in conflict, or
vCenter Server generates a duplicate MAC address for a newly created virtual machine.
A virtual machine powers on and functions properly, but shares a MAC address with another virtual
machine. This situation might cause packet loss and other problems.
Cause
Virtual machines might have duplicate MAC addresses due to several reasons.
n
Two vCenter Server instances with identical IDs generate overlapping MAC addresses for virtual
machine network adapters.
Each vCenter Server instance has an ID between 0 and 63 that is randomly generated at installation
time, but can be reconfigured after installation. vCenter Server uses the instance ID to generate MAC
addresses for the network adapters of the machine.
vSphere Networking
VMware, Inc. 253