After redeploying VCFA to correct an incorrect DNS entry, one of the NSX Managers stopped appearing under:
Provider Portal > Administration > Connections > vCenter
Provider Portal > Administration > Connections > NSX Manager
Despite this, the VCFA component was already managed under Fleet Management > Lifecycle, and data collection for both vCenter and NSX was functioning correctly from VCF Operations.
Manually attempting to sync NSX-T Edge information through:
Inventory > VCF Instance > Actions > Sync Inventory (with Enable Edge cluster sync selected) Fails with error 'Import operation for sync with id <request_id> failed internally" pointing towards SDDC
VCF Automation 9.0.1
VCF Operations 9.0.1
The NSX Manager was incorrectly marked in an ERROR state by SDDC, preventing it from being listed under VCFA connections.
The NSX Manager status was updated to ACTIVE directly in the SDDC Manager database, restoring visibility under VCFA Connections.
Steps:
psql --host=localhost -U postgres -d platform
update nsxt set status = 'ACTIVE' where cluster_fqdn = '<VCFA_FQDN';