NSX Traceflow fails in Policy mode with error: "No Segment Port found for this VIF"

Products

• VMware NSX

Issue/Introduction

When running a Traceflow in Policy mode within VMware NSX, the results may fail to display specific port and interface identifiers for certain Virtual Machines (VMs). 

Symptoms include:

• The same Traceflow often works as expected when run in Manager mode.
• This issue typically impacts a specific subset of VMs while others on the same host or segment remain unaffected.
• The following error is displayed on the NSX UI: "No Segment Port found for this VIF"


Environment

VMware NSX

Resolution

If you believe you have encountered this issue, open a support case with Broadcom Support and refer to this KB article.

For more information, see Creating and managing Broadcom support cases.

Workaround:

For each affected VM, perform the following steps to trigger a port refresh:

1. Log in to the vSphere Client.
2. Locate the affected Virtual Machine and select Edit Settings.
3. Identify the Network Adapter connected to the NSX segment.
4. Change the network assignment to a different segment or portgroup and click OK.
5. Immediately edit the settings again and move the network adapter back to the original NSX segment.
6. Verify the fix by re-running the Traceflow in Policy mode.

Note: Although this process is typically non-disruptive to the guest OS, changing network segments may cause a momentary loss of connectivity. This action should be performed during a maintenance window.