vCenter Server 8.0.2 Initial Configuration Guide

Overview

This guide covers the initial configuration of vCenter Server 8.0.2 for a mixed ESXi environment with Intel NUCs (ESXi 8.0.3) and Mac Pro (ESXi 7.0.3).

Environment Details

VCSA Information

  • FQDN: vcsa.markalston.net
  • IP: 192.168.10.11
  • Version: vCenter Server 8.0.2-22617221
  • Login: administrator@vsphere.local / Cl0udFoundry!

ESXi Hosts

Host IP Hardware ESXi Version Role
esxi-nuc-01.markalston.net 192.168.10.8 Intel NUC6i7KYK 8.0.3 Workload
esxi-nuc-02.markalston.net 192.168.10.9 Intel NUC6i7KYK 8.0.3 Workload
esxi-nuc-03.markalston.net 192.168.10.10 Intel NUC6i7KYK 8.0.3 Workload
macpro.markalston.net 192.168.10.7 Mac Pro Late 2013 7.0.3 Management/vCenter

Step 1: Initial vCenter Access

1.1 Access vSphere Client 

URL: https://vcsa.markalston.net
Username: administrator@vsphere.local  
Password: Cl0udFoundry!

1.2 Accept Certificates

  • Accept any SSL certificate warnings
  • Consider configuring proper certificates later

Step 2: Create Datacenter Structure

2.1 Create Datacenter

  1. Right-click on vCenter server in inventory
  2. Select: New Datacenter
  3. Name: Homelab-DC
  4. Click: OK

Under Homelab-DC, create folders for organization:

  1. Right-click on Homelab-DC
  2. New Folder → New VM and Template Folder
    • Name: Management-VMs
    • Name: Workload-VMs
  3. New Folder → New Host and Cluster Folder
    • Name: Compute-Hosts
    • Name: Management-Hosts

Step 3: Add ESXi Hosts

3.1 Add Intel NUC Hosts (ESXi 8.0.3)

For each Intel NUC:

  1. Right-click on Homelab-DC (or Compute-Hosts folder)
  2. Select: Add Host
  3. Host Configuration:
    • Host name: esxi-nuc-01.markalston.net (etc.)
    • User name: root
    • Password: Cl0udFoundry!
  4. Click: Next through security certificate warning
  5. Host Summary: Review and click Next
  6. Assign License: Use evaluation license for now
  7. Lockdown Mode: Disabled (recommended for homelab)
  8. VM Location: Select appropriate folder (Workload-VMs)
  9. Ready to Complete: Click Finish

Repeat for:

  • esxi-nuc-02.markalston.net
  • esxi-nuc-03.markalston.net

3.2 Add Mac Pro Host (ESXi 7.0.3)

  1. Right-click on Management-Hosts folder (or Homelab-DC)
  2. Select: Add Host
  3. Host Configuration:
    • Host name: macpro.markalston.net
    • User name: root
    • Password: Cl0udFoundry!
  4. Follow same process as Intel NUCs

Step 4: Create Clusters

4.1 Create Compute Cluster (Intel NUCs Only)

  1. Right-click on Homelab-DC
  2. Select: New Cluster
  3. Basic Configuration:
    • Name: NUC-Cluster
    • DRS: Enabled (Fully Automated)
    • HA: Enabled
    • vSphere Lifecycle Manager: Select “Manage all hosts in the cluster with a single image”
  4. Image Setup Options (appears when single image selected):
    • For existing hosts: Choose “Import image from an existing host in the vCenter inventory”
    • Select host: Choose one of your Intel NUCs (e.g., esxi-nuc-01) as the reference
    • Configuration Management: ✅ Check “Manage configuration at the cluster level”
  5. Click: Next through remaining options
  6. Click: Finish

Image Import Options Explained:

  • Compose a New Image: Start from scratch (not needed - your hosts are already configured)
  • Import from existing host: Best option - uses your current NUC configuration as template
  • Import from new host: For hosts not yet added to vCenter

Note: The “Manage configuration at the cluster level” option ensures consistent host settings across all cluster members.

4.2 Move Intel NUCs to Cluster

  1. Select all three Intel NUC hosts
  2. Drag and drop into NUC-Cluster
  3. Confirm the move

4.3 Configure EVC Mode (Enhanced vMotion Compatibility)

Since you have mixed CPU generations:

  1. Right-click on NUC-Cluster
  2. Settings → EVC
  3. Enable EVC
  4. Select: Intel “Haswell” Generation or appropriate baseline
  5. Apply

Note: Keep Mac Pro separate due to different ESXi version

Step 5: Configure Networking

  1. Navigate: Networking tab
  2. Right-click on Homelab-DC
  3. Select: Distributed Switch → New Distributed Switch
  4. Configuration:
    • Name: Homelab-DvS
    • Version: 7.0.0 (compatible with ESXi 7.0.3)
    • Number of uplinks: 2 per host

5.2 Add Hosts to Distributed Switch

  1. Right-click on Homelab-DvS
  2. Add and Manage Hosts
  3. Select: Add hosts
  4. Select all ESXi hosts
  5. Configure uplinks:
    • Map physical NICs to uplink ports
      • Map vmnic0 → Uplink 1
      • Map vusb0 → Uplink 2
    • For Intel NUCs: vmnic0 (built-in) and vusb0 (USB adapter)
    • For Mac Pro: Both built-in NICs
    • Note: USB NICs appear as vusb0, not vmnic1

5.3 Create Port Groups

Create port groups for different VLANs based on VCF requirements:

  1. Management Network:
    • Name: Management-PG
    • Port Binding: Static
    • Port Allocation: Elastic
    • Number of Ports: 8
    • Network Resource Pool: Default
    • VLAN Type: VLAN
    • VLAN ID: 10
    • Description: ESXi management, vCenter Server, and infrastructure management traffic
    • Usage: VMkernel adapters for management (vmk0)
    • Advanced Policies: Default security policy (Promiscuous mode: Reject, MAC changes: Reject, Forged transmits: Reject)
  2. vMotion Network:
    • Name: vMotion-PG
    • Port Binding: Static
    • Port Allocation: Elastic
    • Number of Ports: 8
    • Network Resource Pool: Default
    • VLAN Type: VLAN
    • VLAN ID: 20
    • Description: Live migration of VMs between hosts, requires low latency and high bandwidth
    • Usage: VMkernel adapters for vMotion (vmk1)
    • Advanced Policies: MTU 9000 (jumbo frames), Load balancing: Route based on physical NIC load, Network failure detection: Beacon probing
  3. vSAN Network:
    • Name: vSAN-PG
    • Port Binding: Static
    • Port Allocation: Elastic
    • Number of Ports: 8
    • Network Resource Pool: Default
    • VLAN Type: VLAN
    • VLAN ID: 30
    • Description: Storage traffic for vSAN cluster communication and data replication
    • Usage: VMkernel adapters for vSAN (vmk2)
    • Advanced Policies: MTU 9000 (jumbo frames), Traffic shaping enabled for guaranteed bandwidth
    • Note: Only needed if using vSAN storage
  4. NSX TEP Network:
    • Name: NSX-TEP-PG
    • Port Binding: Static
    • Port Allocation: Elastic
    • Number of Ports: 8
    • Network Resource Pool: Default
    • VLAN Type: VLAN
    • VLAN ID: 40
    • Description: NSX Tunnel Endpoints for overlay network encapsulation (GENEVE/VXLAN)
    • Usage: VMkernel adapters for NSX TEPs
    • Advanced Policies: MTU 1600+ (increased for encapsulation overhead)
    • Note: Required for NSX-T deployment
  5. NSX Edge Uplink Network:
    • Name: NSX-Edge-Uplink-PG
    • Port Binding: Ephemeral
    • Port Allocation: Elastic
    • Number of Ports: 16
    • Network Resource Pool: Default
    • VLAN Type: VLAN
    • VLAN ID: 50
    • Description: NSX Edge north-south connectivity to physical network/router
    • Usage: NSX Edge VM uplink interfaces for external connectivity
    • Advanced Policies: Security policy (Promiscuous mode: Accept, MAC changes: Accept, Forged transmits: Accept)
    • Note: This is where Edge nodes connect to physical network for routing
  6. TKG Management Network:
    • Name: TKG-Management-PG
    • Port Binding: Static
    • Port Allocation: Elastic
    • Number of Ports: 16
    • Network Resource Pool: Default
    • VLAN Type: VLAN
    • VLAN ID: 100
    • Description: Tanzu Kubernetes Grid management cluster and control plane components
    • Usage: VMs for TKG management cluster
    • Advanced Policies: Default security policy
  7. TKG Workload Network:
    • Name: TKG-Workload-PG
    • Port Binding: Static
    • Port Allocation: Elastic
    • Number of Ports: 32
    • Network Resource Pool: Default
    • VLAN Type: VLAN
    • VLAN ID: 110
    • Description: Tanzu Kubernetes Grid workload clusters and application deployments
    • Usage: VMs for TKG workload clusters
    • Advanced Policies: Default security policy
  8. NUC Management Network (Optional - Not Recommended for Production):
    • Name: NUC-Management-PG
    • Port Binding: Static
    • Port Allocation: Elastic
    • Number of Ports: 8
    • Network Resource Pool: Default
    • VLAN Type: VLAN
    • VLAN ID: 200
    • Description: Alternative management network for testing/troubleshooting only
    • Usage: Temporary management access during network reconfiguration
    • Advanced Policies: Default security policy
    • Note: Keep NUCs on main management network (VLAN 10) for normal operation

Step 6: Configure Storage

6.1 Review Existing Datastores

Each host should show its local datastore:

  • Intel NUCs: datastore names like esxi-nuc-01-ssd-local
  • Mac Pro: MAC_LOCAL

6.2 Create Datastore Clusters (Optional)

For Intel NUCs with similar storage:

  1. Navigate: Storage tab
  2. Right-click on Homelab-DC
  3. Storage → New Datastore Cluster
  4. Name: NUC-Storage-Cluster
  5. Enable Storage DRS
  6. Add datastores from Intel NUCs

6.3 Configure Storage Policies

  1. Navigate: Policies and Profiles
  2. VM Storage Policies → Create
  3. Create policies for:
    • High-performance workloads (NUC local storage)
    • Management VMs (Mac Pro storage)

Step 7: Configure Advanced Settings

7.1 Configure vMotion Networks

For each Intel NUC host:

  1. Select host → Configure → VMkernel adapters
  2. Add Networking
  3. VMkernel Network Adapter
  4. Select vMotion port group
  5. Enable vMotion service

7.2 Set Up HA/DRS

  1. Select Compute-Cluster
  2. Configure → Configuration
  3. DRS Settings:
    • Automation Level: Fully Automated
    • Migration Threshold: Apply Priority 1, Priority 2, and Priority 3 recommendations
  4. HA Settings:
    • Host failures cluster tolerates: 1
    • Admission Control: Enabled

7.3 Configure Alarms and Monitoring

  1. Monitor → Alarms
  2. Review default alarms
  3. Create custom alarms for:
    • Host disconnection
    • Datastore usage
    • VM resource usage

Step 8: Post-Configuration Tasks

8.1 Update Host Profiles (Optional)

  1. Extract host profile from a reference host
  2. Apply to similar hosts for consistency

8.2 Configure Backup

  1. Menu → Administration → Configuration → Backup
  2. Configure backup schedule
  3. Set backup location (to Mac Pro datastore)

8.3 Install vCenter Plugins

Consider installing:

  • Update Manager (WSUS integration)
  • Log Insight (if available)

Mixed Environment Best Practices

EVC Considerations

  • Intel NUCs: Can use newer EVC modes
  • Mac Pro: Limited by Ivy Bridge architecture
  • Recommendation: Keep clusters separate or use conservative EVC

vMotion Limitations

  • Between versions: Use EVC mode
  • Cross-version: May have limitations
  • Storage vMotion: Works across versions

Resource Management

  • Mac Pro: Ideal for management VMs and VCSA
  • Intel NUCs: Workload VMs with HA/DRS
  • Mixed workloads: Distribute based on requirements

Verification Checklist

  • All hosts added and connected
  • Clusters created and configured
  • Networking configured (standard or distributed switches)
  • Storage visible and accessible
  • HA/DRS functional
  • vMotion working within cluster
  • Alarms and monitoring configured
  • Backup schedule configured

Troubleshooting

Host Connection Issues 

# Test connectivity
ping esxi-nuc-01.markalston.net

# Check ESXi service status
ssh root@esxi-nuc-01.markalston.net "service.sh status"

vMotion Issues

  • Check VMkernel networking
  • Verify shared storage access
  • Review EVC settings

HA/DRS Issues

  • Check cluster configuration
  • Verify resource pools
  • Review constraints and rules

Useful PowerCLI Commands 

# Connect to vCenter
Connect-VIServer -Server vcsa.markalston.net

# Get all hosts
Get-VMHost

# Get cluster information
Get-Cluster

# Check vMotion configuration
Get-VMHost | Get-VMHostNetworkAdapter -VMKernel | Where-Object {$_.VMotionEnabled}

Next Steps

Once basic configuration is complete:

  1. Deploy test VMs on each host
  2. Test vMotion within cluster
  3. Configure monitoring and alerting
  4. Set up automated backup for VMs
  5. Configure SSL certificates for production use

Configuration URLs:

This project is for educational and home lab purposes.