Multi-homing / Multiple NICs configuration of VC is not supported in VCF
search cancel

Multi-homing / Multiple NICs configuration of VC is not supported in VCF

book

Article ID: 367841

calendar_today

Updated On:

Products

VMware SDDC Manager

Issue/Introduction

Upgrading a vCenter Server with multi-homing from an SDDC Manager is failed. For example:

Error Message: Reason is: com.vmware.vcf.error.update.vc.runtime.vcsa.install.failed

YYYY-MM-DD HH:mm:ss,SSS [loggable.py:102]: Querying REST endpoint '/rest/vcenter/deployment' on appliance '192.168.XXX.XXX' for deployment status
YYYY-MM-DD HH:mm:ss,SSS [loggable.py:102]: Failed to query REST endpoint '/rest/vcenter/deployment' on appliance IP '192.168.XXX.XXX' for deployment status because: Failed while trying the connection with certificate validation. Exception: HTTPSConnectionPool(host='192.168.XXX.XXX', port=5480): Max retries exceeded with url: /rest/vcenter/deployment (Caused by NewConnectionError('<urllib3.connection.HTTPSConnection object at 0x7f88a847e530>: Failed to establish a new connection: [Errno 113] No route to host')). If the error message contains references about messages being expired, a login problem, or its context indicates a timing issue, a possible reason could be system clock skew. Refer to error messages in 'taskflow.log' for more details.
YYYY-MM-DD HH:mm:ss,SSS [retry.py:62]: Operation 'Checking target VCSA has appliance REST API ready' is going to retry because 'The appliance REST API was not yet available from the target VCSA 'vcenter-upgrade-target-appliance_9812a854-9f72-4568-8103-74782ec56ff4'because 'Failed while trying the connection with certificate validation. Exception: HTTPSConnectionPool(host='192.168.XXX.XXX', port=5480): Max retries exceeded with url: /rest/vcenter/deployment (Caused by NewConnectionError('<urllib3.connection.HTTPSConnection object at 0x7f88a847e530>: Failed to establish a new connection: [Errno 113] No route to host')). If the error message contains references about messages being expired, a login problem, or its context indicates a timing issue, a possible reason could be system clock skew. Refer to error messages in 'taskflow.log' for more details. '. The VCSA might still be starting up.'. Will retry in 30 seconds, timeout in 30 seconds

Environment

All VCF versions starting from inception of VCF.

Cause

This feature is not supported in VCF.

Resolution

VCF does not support multi-homing / multiple NICs configuration of VC. Try having only one NIC configured for VC.