Traceflow diagram includes hops not traversed by the actual traffic
Article ID: 322534
Updated On:
Products
VMware NSX
Issue/Introduction
Symptoms:
When running a traceflow between 2 VMs, the diagram displays hops which are not traversed.
The data path section shows the correct hops taken.
The traceflow source and destination VMs are on two separate segments and are connected to a Tier-1 Logical router.
The Tier-1 Logical router is connected to a Tier-0 Logical router.
One of the two segments is also connected to a second Tier-1 via a service interface.
When running a traceflow between 2 VMs, the diagram displays hops which are not traversed.
The data path section shows the correct hops taken.
The traceflow source and destination VMs are on two separate segments and are connected to a Tier-1 Logical router.
The Tier-1 Logical router is connected to a Tier-0 Logical router.
One of the two segments is also connected to a second Tier-1 via a service interface.
Environment
VMware NSX-T Data Center
Cause
If a segment is connected to two Tier-1 routers and one of the those Tier-1 routers is connected to a
parent Tier-0, the logic to find the correct hierarchy for the same segment fails.
parent Tier-0, the logic to find the correct hierarchy for the same segment fails.
Resolution
Feedback
Yes
No
Powered by
