Traceflow will convert the source IP to network IP when the source port is Edge uplink or Edge CSP
Article ID: 345806
Updated On:
Products
VMware NSX
Issue/Introduction
N/A
Symptoms:
When doing a traceflow from an uplink interface the wrong source IP is used with the injected packet.
User could notice this through pktcap-uw, the crafted traceflow packet is different what they specific one.
E.g., customer specific the source ip is "192.168.1.100/24", the source port is an Edge uplink. But the actual source IP of packet is "192.168.1.0/24".
Symptoms:
When doing a traceflow from an uplink interface the wrong source IP is used with the injected packet.
User could notice this through pktcap-uw, the crafted traceflow packet is different what they specific one.
E.g., customer specific the source ip is "192.168.1.100/24", the source port is an Edge uplink. But the actual source IP of packet is "192.168.1.0/24".
Environment
VMware NSX-T Data Center
Cause
Traceflow crafted packet will be dropped by RPF(reverse path forwarding) checking of Edge if the source IP is not converted to network IP.
Resolution
This is by design.
Workaround:
N/A
Workaround:
N/A
Additional Information
Product Versions:
NSX 2.3.0 to the latest NSX version
Impact/Risks:
N/A
NSX 2.3.0 to the latest NSX version
Impact/Risks:
N/A
Feedback
Yes
No
Powered by
