Lab: VCSA Troubleshooting & Certificate Renewal
Objectives
- Check vCenter service health with service-control
- Read the Machine SSL certificate expiry from VECS and renew it after a file-based backup
- Check /storage free space and the vmware-vpostgres service
Prerequisites
Holodeck VVF 9.0 instance; SSH to the vCenter appliance enabled; a current file-based backup of vCenter
Lab Environment
Holodeck vSphere Foundation 9.0 instance (New-HoloDeckInstance -VVF; -vSANMode OSA by default, ESA where the physical layer supports it): vCenter managing one vSAN cluster of nested ESX hosts, plus VCF Operations. VVF has no SDDC Manager and no NSX.
Credentials
| System | Username | Password |
|---|---|---|
| vCenter | administrator@vsphere.local | Holodeck documented default (Post Deployment table) |
| VCF Operations | admin | Holodeck documented default (Post Deployment table) |
| Nested ESX hosts | root | Holodeck documented default (Post Deployment table) |
Tasks
Task 1 vCenter health checks and Machine SSL renewal
SSH to VCSA: ssh root@vcsa_hostname
Check services: service-control --status --all | grep -i "vpxd\|ui\|vpostgres"
View the Machine SSL certificate expiry — it lives in VECS, not in a legacy file: /usr/lib/vmware-vmafd/bin/vecs-cli entry getcert --store MACHINE_SSL_CERT --alias __MACHINE_CERT | openssl x509 -noout -enddate. Cross-check in the vSphere Client under Administration > Certificates > Certificate Management.
Check disk space: df -h /storage (should show >20% free)
Verify the database service: service-control --status vmware-vpostgres (should be running — the service name is vmware-vpostgres).
Restart the vSphere Client service: service-control --restart vsphere-ui. The vSphere Client is unavailable for a few minutes; hosts and VMs are unaffected (hosts only show disconnected after a vpxd restart).
After the restart, log in to the vSphere Client again. Then, after a file-based backup, renew the Machine SSL certificate from Administration > Certificates > Certificate Management (or with /usr/lib/vmware-vmca/bin/certificate-manager option 3 in the lab) and confirm the new 'Not After' date with the vecs-cli command from step 3.
Validation Gate
Check: Verify VCSA health: all services running, certificates not expiring within 30 days, disk partitions below 80%, and PostgreSQL database accessible
Expected: service-control --status shows all services green. Certificate Manager shows certificates valid for >30 days. df -h shows all partitions below 80%. psql can connect to VCDB.
Common Errors
Final Validation
Gate: every check below passes with the evidence recorded in the lab log.
✓ service-control --status --all → All required services running
✓ Machine SSL certificate → New expiry date shown in VECS and in Administration > Certificates
✓ df -h /storage → Partitions below 80% used
✓ vmware-vpostgres → Running
Cleanup / Restore
• Disable SSH on the vCenter appliance again
Design Reflection (VCDX)
vCenter availability is critical — a VCSA failure impacts management of the entire domain. VCDX designs should include VCSA monitoring, certificate lifecycle management, and backup/recovery procedures.
Requirements
- Monitor VCSA service health and disk space
- Manage certificate lifecycle proactively
- Maintain VCSA backup for recovery
Constraints
- Certificate renewal must follow dependency order
- Log partition can fill rapidly during service issues
- VCSA backup must be current before certificate operations
Assumptions
- VCSA backup runs daily via file-based backup
- Certificate expiry monitoring is configured in VCF Operations
Risks
- Certificate expiry cascade across VCF components
- VCSA instability from log partition exhaustion