NSX Federation Environment: vRNI Groups Enter Failed State After Brownfield Configuration Import
search cancel

NSX Federation Environment: vRNI Groups Enter Failed State After Brownfield Configuration Import

book

Article ID: 384349

calendar_today

Updated On:

Products

VMware NSX

Issue/Introduction

In a federation environment, vRNI groups may encounter realization errors and enter a failed state in both the Local Manager and Global Manager following a brownfield configuration import.

  • The issue occurs specifically after importing brownfield configurations.
  • Despite the realization errors, there is no impact on the datapath or overall network functionality.
  • The following log entry is commonly observed in the user interface:

Entity /global-infra/sites/###_default/enforcement-points/default/host-transport-nodes/###-#####-####-a15e-####-####-####23e02aa0host-#### was deleted. Group /global-infra/domains/###/groups/vRNI-Node_Group_Profile_TN_####-#####-#### must be updated to remove the invalid reference.



This behavior is attributed to invalid references created during the configuration import process, which require updates to resolve.

Environment

VMware NSX

Cause

The HostTransportNode entity is not supported on the Global Manager, and unlike other fabric entities, these objects are not discovered on the Global Manager. During the vRNI workflow, a group was created with HostTransportNode as a member. When the configuration was onboarded, this group was imported to the Global Manager, resulting in the observed issue.

Resolution

In the event of this issue, a support case should be opened with Broadcom for assistance.