You can start a Traceflow session in NSX Manager to trace the path of packet in an Antrea container cluster. Antrea Traceflow currently supports tracing the path of only Unicast traffic. Broadcast and Multicast traffic are not supported.
The source of a
Traceflow session must be a Pod, whereas the destination can be a Pod or a Service in the same container cluster. You can trace the path of a packet for the following types of traffic in an
Antrea container cluster:
- Pod to Pod traffic on the same node (intra-node traffic)
- Pod to Pod traffic between nodes (inter-node traffic)
- Pod to Service traffic on the same node
- Pod to Service traffic between nodes
- Pod to an arbitrary IP address
Traceflow injects a test packet into the Antrea container cluster network and monitors the flow of the packet. As the packet flows from the source to destination, observations are collected from various components along the path of the packet. These observations are displayed in the Traceflow output, which shows the various components in the path of the packet.
Prerequisites
Antrea container cluster is registered to NSX.
Procedure
Results
The
Traceflow observations are displayed in a tabular format. For each observation, the table shows the following information.
- Observation Type
-
This column takes the following values.
Observation Type Description Delivered The packet is delivered to destination Pod or Service properly. Dropped The packed is dropped by a network policy. Received The packet is received from another node in the container cluster. Forwarded The packet is forwarded to the next logical node or a container cluster object. - Component
-
This column shows the components that the test packet had encountered on its path from the source to the destination. Sample component values are: IngressRule, EgressRule, SpoofGuard, Classification, Output, and so on.
Click the component name to view more information in a pop-up window.
- Timestamp
- The date and time for each observation.