Audit check failed for NSX-T. Check if the SDDC Manager is able to communicate with NSX-T Manager.
search cancel

Audit check failed for NSX-T. Check if the SDDC Manager is able to communicate with NSX-T Manager.

book

Article ID: 316102

calendar_today

Updated On:

Products

VMware Cloud Foundation

Issue/Introduction

To let the user know that the audit check failed for NSX-T, They will be unable to upgrade NSX-T.

Symptoms:


Description Checks for NSX-T audit failures.

Error Description: NSX-T Manager Audit for FQDN failed with unknown exception

/var/log/vmware/vcf/lcm/lcm-debug.log indicates


2022-09-14T01:23:16.386+0000 ERROR [vcf_lcm,4f54415159a57605,21a5,auditId=45659dfc-acc7-4a1c-8073-80fba9d39aed,resourceType=NSX_T_MANAGER,resourceId=nsxt.domain.local,name=nsxt.domain.local] [c.v.e.s.l.p.impl.nsxt.NsxtAuditImpl,Scheduled-6] Error auditing NSX-T Cluster nsxt.domain.local with exception {}
com.vmware.evo.sddc.lcm.model.error.LcmException: Failed to load NSX-T Cluster from the Inventory
  at com.vmware.evo.sddc.lcm.primitive.impl.nsxt.NsxtInventoryLoader.loadNsxtInventory(NsxtInventoryLoader.java:85)
  at com.vmware.evo.sddc.lcm.primitive.impl.nsxt.NsxtAuditImpl.doAudit(NsxtAuditImpl.java:68)
  at com.vmware.evo.sddc.lcm.audit.NsxtAuditService.doAudit(NsxtAuditService.java:121)
  at com.vmware.evo.sddc.lcm.audit.NsxtInventoryAuditScheduler.auditNsxtInventory(NsxtInventoryAuditScheduler.java:84)


Logs also will contain :

XXXX-XX-XX:01:31.231+0000 ERROR [vcf_lcm,623c47be30e82659,3333,auditId=aa6b062f-9bc7-4cd6-9d8d-8a1909cb8852,resourceType=NSX_T_MANAGER,resourceId=NSXFQDN,name=NSXFQDN] [c.v.e.s.l.p.i.n.NsxtInventoryLoader,pool-7-thread-1] Corresponding vCenter Mapping for Compute Manager VCIP NOT FOUND in the VCF inventory
XXXX-XX-XX:01:31.914+0000 INFO  [vcf_lcm,623c47be30e82659,3333,auditId=aa6b062f-9bc7-4cd6-9d8d-8a1909cb8852,resourceType=NSX_T_MANAGER,resourceId=NSXFQDN,name=NSXFQDN] [c.v.e.s.l.a.i.i.InventoryClientImpl,pool-7-thread-1] Fetching NSX-T Upgrade Coordinator Connection for b1db118e-4242-43bd-85b8-de3b6efb433b
XXXX-XX-XX:01:32.370+0000 INFO  [vcf_lcm,f0ec742a97785228,4196] [c.v.e.s.l.s.UpgradeServiceHelper,pool-7-thread-3] create Upgrade item  for bundle 393fb05f-23ff-47d1-8b84-db39647677ce and bundle element type SDDC_MANAGER_VCF is true
XXXX-XX-XX:01:32.370+0000 INFO  [vcf_lcm,f0ec742a97785228,4196] [c.v.e.s.l.s.UpgradeServiceHelper,pool-7-thread-3] Found successful EVORACK upgrade 3462faaf-1270-4dd7-8c4c-dfb11b68caac with bundle 8f26c34a-7488-4960-aaf7-276ba313846b
XXXX-XX-XX:01:32.370+0000 INFO  [vcf_lcm,f0ec742a97785228,4196] [c.v.e.s.l.s.UpgradeServiceHelper,pool-7-thread-3] returning 1 number of upgradableResources
XXXX-XX-XX:01:32.370+0000 WARN  [vcf_lcm,f0ec742a97785228,4196] [c.v.e.s.l.s.i.InventoryUpgradeServiceImpl,pool-7-thread-3] EVORACK bundle 393fb05f-23ff-47d1-8b84-db39647677ce is pending on Vmware Software bundle 00a3b5c2-dbfb-498f-bdc1-1d47010e0fcb
XXXX-XX-XX:01:32.611+0000 INFO  [vcf_lcm,623c47be30e82659,3333,auditId=aa6b062f-9bc7-4cd6-9d8d-8a1909cb8852,resourceType=NSX_T_MANAGER,resourceId=NSXFQDN,name=NSXFQDN] [c.v.e.s.l.a.i.i.InventoryClientImpl,pool-7-thread-1] Fetching NSX-T Upgrade Coordinator Connection for b1db118e-4242-43bd-85b8-de3b6efb433b
XXXX-XX-XX:01:32.640+0000 ERROR [vcf_lcm,623c47be30e82659,3333,auditId=aa6b062f-9bc7-4cd6-9d8d-8a1909cb8852,resourceType=NSX_T_MANAGER,resourceId=NSXFQDN,name=NSXFQDN] [c.v.e.s.l.p.impl.nsxt.NsxtAuditImpl,pool-7-thread-1] Error auditing NSX-T Cluster NSXFQDN with exception {}
com.vmware.evo.sddc.lcm.model.error.LcmException: Failed to load NSX-T Cluster from the Inventory
        at java.lang.Thread.run(Thread.java:748)
Caused by: java.util.NoSuchElementException: No value present
        at java.util.Optional.get(Optional.java:135)
        at com.vmware.evo.sddc.lcm.primitive.impl.nsxt.NsxtInventoryLoader.markUpgradeAvailability(NsxtInventoryLoader.java:529)
        at com.vmware.evo.sddc.lcm.primitive.impl.nsxt.NsxtInventoryLoader.loadNsxtInventory(NsxtInventoryLoader.java:85)
        ... 35 common frames omitted

Environment

VMware Cloud Foundation 4.4.1
VMware Cloud Foundation 5.0
VMware Cloud Foundation 3.0.x
VMware Cloud Foundation 4.x

Cause

The SDDC manager code uses a hostname to compare the presence of a specific Compute Manager in sddc inventory.
Since NSX-T allows setting either a fqdn or IP Address, if an IP address is set through NSX-T , it trips SDDC manager audit check.

Resolution

The issue has been fixed in VMware Cloud Foundation 5.1 release.

Workaround:
Follow the below steps:
  1. Go to NSX-T manager UI.
  2. Go to System > Configuration > Fabric > Compute Managers.
  3. Edit the compute manager.
  4. Change IP of VCenter to FQDN of VCenter.