You can configure the path detection function on the device that functions as the ingress or egress node on a VXLAN network through the CLI or NMS and enable the inbound interface of the device to construct and forward a 5-tuple packet based on packet sending parameters. Each path detection-capable device along the path is configured with a specific DSCP value so that it can obtain the packet information and send the packet information as well as the inbound and outbound interface information to the controller. The controller then displays the path information of the specified 5-tuple flow based on the information sent by the devices.
IPv4 Path Detection
An IPv4 path detection packet is a common IPv4 TCP/UDP/ICMP/SCTP packet, as shown in Figure 1. The device identifies a path detection packet based on the detection flag (DSCP) and detection data (OAM PDU).
IPv6 Path Detection
An IPv6 path detection packet is a common IPv6 TCP/UDP/ICMP/SCTP packet, as shown in Figure 2. The device identifies a path detection packet based on the detection flag (DSCP value) and detection data (OAM PDU).
In Figure 3, the controller has established NETCONF connections with devices at the DC-GW, spine, and leaf layers. Devices at the DG-GW layer are VXLAN Layer 3 gateways, devices at the spine layer are transparent transmission devices on the VXLAN network, and devices at the leaf layer are VXLAN Layer 2 gateways. The path from Device1 to VM1 needs to be detected. Assuming the detected path is Device1->Device2->Device3->VM1, the path detection process is as follows:
On the live network, the NetEngine 8000 F is generally deployed at the DG-GW layer.