2V0-621 · Question #154
An administrator has migrated a vCenter Server Appliance from version 5.5 to version 6.x. During the migration, the administrator selected DHCP for the appliance and obtained a hostname from the…
The correct answer is A. Regenerate the SSL certificates. Changing the hostname on a vCSA invalidates its SSL certificates because the Common Name no longer matches, requiring immediate regeneration to prevent service failures.
Question
An administrator has migrated a vCenter Server Appliance from version 5.5 to version 6.x. During the migration, the administrator selected DHCP for the appliance and obtained a hostname from the DHCP server. The administrator adjusts the hostname after the migration and uses a static IP and hostname. What should the administrator do immediately after this change to prevent service failures?
Options
- ARegenerate the SSL certificates.
- BRe-register components to Single Sign-On.
- CUpdate the /etc/hosts file.
- DExecute the command services.restart vmware-vpxd.
How the community answered
(36 responses)- A72% (26)
- B14% (5)
- C6% (2)
- D8% (3)
Why each option
Changing the hostname on a vCSA invalidates its SSL certificates because the Common Name no longer matches, requiring immediate regeneration to prevent service failures.
SSL certificates in vCSA embed the hostname or FQDN in the Common Name (CN) and Subject Alternative Name fields at the time of issuance. When the hostname is changed from the DHCP-assigned value to a static one, the existing certificates no longer match, causing SSL handshake failures across all vCenter services. Regenerating SSL certificates immediately after the hostname change ensures all services - including vCenter, SSO, and the inventory service - present valid, matching certificates.
Re-registering SSO components addresses service registration issues, not the SSL certificate CN mismatch introduced by a hostname change.
Updating /etc/hosts improves local name resolution but does not resolve the mismatch between the certificate's embedded hostname and the new static hostname.
Restarting the vpxd service alone restarts the vCenter daemon but does not fix the underlying invalid SSL certificate that still references the old hostname.
Concept tested: vCSA SSL certificate regeneration after hostname change
Source: https://kb.vmware.com/s/article/2097936
Topics
Community Discussion
No community discussion yet for this question.