NSX Edge logs spammed with log: Query to /var/run/vmware/edge/dpd.ctl failed with lrouter with the UUID or vrfid does not exist
search cancel

NSX Edge logs spammed with log: Query to /var/run/vmware/edge/dpd.ctl failed with lrouter with the UUID or vrfid does not exist

book

Article ID: 423650

calendar_today

Updated On:

Products

VMware NSX

Issue/Introduction

NSX Edge logs are spammed with these errors:
 FABRIC [nsx@6876 comp="nsx-edge" subcomp="nsx-edge-exporter" s2comp="nsx-app-ctl" level="ERROR" errorCode="EDG0500002"] Query to /var/run/vmware/edge/dpd.ctl failed with lrouter with the UUID or vrfid does not exist

Environment

VMware NSX
VMware NSX-T Data Center

Cause

When downlink segment of tier-1 Active-Standby does not exist, tier-1 DR is not created on edge. (Because in that case, there is no entity that can send traffic through that tier-1 to edge.)
But in GetTier1ForwardingTable (GET https://<mgr-ip>/api/v1/infra/tier-1s/<t1-id>/forwarding-table) agg-service queries both SR and DR components to fetch the forwarding table.
DR Component does not exist on edge. But querying it. So, error log in edge.

Resolution

Workaround:
Create a downlink segment for the tier-1.
It'll lead to tier-1 DR creation on edge node and the error log will stop appearing.

Resolution:
Code fix to prevent querying DR component on edge for the cases where tier-1 DR does not exist on edge node.