NSX Global manager objects are in unknown state.
search cancel

NSX Global manager objects are in unknown state.

book

Article ID: 423559

calendar_today

Updated On:

Products

VMware NSX

Issue/Introduction

  • GM objects like Tier-1 and Tier-0 gateways were in unknown state.
  • We found following symptoms, that a LM (Local manager) was showing in unknown state on the GM.

  • Further checks confirmed issue with Global manager unable to lookup the impacted Local Manager's FQDN.

    /var/log/syslog
    -------------------
    <Timestamp><GM> NSX 5554 - [nsx@6876 comp="global-manager" level="WARNING" subcomp="site-manager"] Unable to resolve ip <Local_Manager_IP_address> to fqdn.
    <Timestamp><GM> NSX 3211 - [nsx@6876 comp="global-manager" subcomp="node-mgmt" username="root" level="WARNING"] Unable to resolve ip <Local_Manager_IP_address> to fqdn.
    

Environment

VMware NSX

Cause

Missing DNS entries for Local managers, as Global manager was not able to resolve the FQDN of Local manager, due to which GM(Global Manager) to LM(Local Manager) nslookup was failing. 

Resolution

Kindly ensure, DNS nslookup is working from GM(Global manager) to LM (Local manager).