NSX Edge logs flooded 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 flooded 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

  • A Tier-1 was created with uplinks, but no segments were attached.
  • The following log line is repeated and appears in /var/log/syslog on an NSX Edge node:
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

This issue occurs when a Tier-1 gateway configured in Active-Standby mode lacks a configured downlink segment. Without a downlink segment to route traffic through the Tier-1 gateway to the Edge node, the Distributed Router (DR) component is not instantiated on the Edge.

When the GetTier1ForwardingTable function is subsequently invoked, the agg-service attempts to query both the Service Router (SR) and the DR components to retrieve the forwarding table. Because the DR component does not exist on the Edge node, the query fails and generates an error in the Edge logs.

There is no functional impact

Resolution

This issue is resolved in VMware NSX 4.2.4 available at Broadcom downloads.
If you are having difficulty finding and downloading software, review the Download Broadcom products and software KB.

Workaround:
Create a segment and attach it to the Tier-1.
This will lead to a Tier-1 DR creation on edge node and the error log will stop appearing.

For defects and enhancements, subscribe to this article to be updated on the fix status. See How to subscribe to Knowledge Base Articles.

Additional Information

For instructions on how to retrieve NSX Edge logs, see KB 201010.