VMware Networking Community
rajeevmenon
Contributor
Contributor
‎02-02-2022 05:25 PM

Missing nsx-opsagent vim connection

Hi,

I have a deployment with ESXi(6.7.0), vCenter(7.0.3.00100) and NSX-T(3.1.3.5.0.19068435). I have the host added in Vcenter and NSX is configured in the host. LLDP information is not available via the UI at NSX-T manager. As per the nsx-syslog logs, the host is failing to communicate with lldp Vim.

2022-02-02T23:56:32Z nsx-opsagent[5120570]: NSX 5120570 - [nsx@6876 comp="nsx-esx" subcomp="opsagent" s2comp="lldp" tid="5120593" level="ERROR" errorCode="OPS00005"] Query failed: error: Failed to call QueryLldpInfo
2022-02-02T23:56:32Z nsx-opsagent[5120570]: NSX 5120570 - [nsx@6876 comp="nsx-esx" subcomp="opsagent" s2comp="lldp" tid="5120593" level="ERROR" errorCode="OPS00202"] Failed to communicate With lldp Vim

 

The opslldpvim.log specifies failure to report LLDP information.

2022-02-03T01:23:03Z opslldpvim: [ 5120570 ] INFO call ProcessRequest failed^@
2022-02-03T01:23:03Z opslldpvim: [ 5120570 ] DEBUG response: b'error: Failed to call QueryLldpInfo'^@

 

The vim connection based on nsxcli seems to be missing

server-1.dc1.com> get service nsx-opsagent vim connection
Thu Feb 03 2022 UTC 01:10:56.172
              CHANNEL                STATUS

 

There shouldn't be a IP connectivity issue between the NSX-T manager and the host as the manager is pingable from the host. How do I debug vim connection issue here?

Labels (4)
Labels
Reply
0 Kudos
1 Reply
rajeevmenon
Contributor
Contributor
‎02-10-2022 01:42 PM

I could get to the resolution of errors in opslldpvim.log. The error seems to be because the LLDP information available at the ESXi host contains "Management Address" entry as seen below

server-1> get lldp neighbors
Tue Feb 08 2022 UTC 00:53:46.230
============================================================
Device                          : vmnic2
Neighbor Count                  : 1
Neighbors
  Chassis Id                    : 50:54:00:19:b5:bc
  Port Id                       : Ethernet3
  TTL                           : 93
  Port Description              : to.rack1-001-sys001:eth0
  System Name                   : leaf-1-5054007D810C
  Enabled Capabilities          : TransparentBridge, Router
  Management Address            : 172.16.0.0
  Organizationally Specific TLVs:
    Aggregation Status          : 1
    Aggregated Port ID          : 0
    Vlan ID                     : 0
    Maximum Frame Size          : 9236

 

I worked around the issue by updating the LLDP neighbor to not send the Management Address.

 

Reply
0 Kudos