Abstract: In one implementation, a method herein comprises: determining a given time during which a computer network is unstable in response to a topology event within the computer network; causing, in response to the computer network being unstable, a measurement analysis process to perform network performance analysis on the computer network based on the computer network being unstable during the given time; and causing, in response to determining that the computer network is otherwise in a stable state, the measurement analysis process to perform network performance analysis on the computer network based on the computer network being stable.

Abstract: Techniques for processing path tracing probe packets using hardware (e.g., hardware memory of a node) and without the involvement of a path tracing collector component of a network controller. A source node may be configured to generate and assign random flow labels to a large number of probe packets and send them through the network to a sink node. The sink node may determine whether a flow indicated by the probe packet has previously been traversed. Additionally, the sink node may determine latency values associated with the flows, and store probe packets in corresponding latency bins. The latency bins may be stored in hardware memory of the sink node. Telemetry data representing the probe packets stored in the latency bins may be sent to a network controller for further network analysis.

Abstract: Techniques for processing path tracing probe packets using hardware (e.g., hardware memory of a node) and without the involvement of a path tracing collector component of a network controller. A source node may be configured to generate and assign random flow labels to a large number of probe packets and send them through the network to a sink node. The sink node may determine whether a flow indicated by the probe packet has previously been traversed. Additionally, the sink node may determine latency values associated with the flows, and store probe packets in corresponding latency bins. The latency bins may be stored in hardware memory of the sink node. Telemetry data representing the probe packets stored in the latency bins may be sent to a network controller for further network analysis.

Abstract: Techniques for providing an optimized behavior to source node(s) of a path tracing sequence allowing for implementation of path tracing source node behavior on an ASIC with edit-depth limitations and/or on an ASIC that does not have access to the full 64-bit timestamp. A source node having optimized behavior may be configured to record a first full 64-bit timestamp in an SRH PT-TLV header of a probe packet using the CPU of the source node. A source node having the optimized behavior may also be configured to compute a midpoint compressed data (MCD) entry and record the entry into an MCD stack of a probe packet using the NPU of the source node. A sink node and/or network controller may be configured to determine a final timestamp for the probe packet through the network by leveraging the SRH PT-TLV header and the MCD entry.

Abstract: Systems, methods, and computer-readable media are provided for path tracing proxy behavior using an external probing appliance. An example method can include generating, at an external probing appliance of a network, a probe packet, the probe packet including a source address, a destination address, and a packet tracing indication in a next header field of the probe packet, the packet tracing indication triggering a proxy source behavior at a source node having the source address and a proxy sink behavior at a sink node having the destination address; sending the probe packet to the source node to trigger a packet tracing mechanism; and receive an updated probe packet from the sink node, the updated probe packet including probe data associated with one or more data flows in the network as the one or more data flows traverse the network from the source node to the sink node.

Abstract: Techniques for monitoring data transport in a network virtualization function (NVF) chain. A path tracing packet is generated having a Midpoint Compressed Data (MCD) to collect path tracing information of the NVF chain. The NVF node is configured to record an MCD containing Wide Local Path Tracing Identification (WL PT ID). The WL PT ID includes a first field having a value that indicates that a non-standard path tracing format is to be used and has a second field that indicates a particular path tracing format to be used. The path tracing packet is passed through the NVF chain and is then received back again after passing through the NVF chain. Data collected by the path tracing packet is analyzed to determine which NVF nodes the path tracing packet passed through, and the amount of time taken for the path tracing packet to pass through, the NVF chain.

Abstract: Techniques for monitoring data transport in a network virtualization function (NVF) chain. A path tracing packet is generated having a Midpoint Compressed Data (MCD) to collect path tracing information of the NVF chain. The NVF node is configured to record an MCD containing Wide Local Path Tracing Identification (WL PT ID). The WL PT ID includes a first field having a value that indicates that a non-standard path tracing format is to be used and has a second field that indicates a particular path tracing format to be used. The path tracing packet is passed through the NVF chain and is then received back again after passing through the NVF chain. Data collected by the path tracing packet is analyzed to determine which NVF nodes the path tracing packet passed through, and the amount of time taken for the path tracing packet to pass through, the NVF chain.

Abstract: In one implementation, a method is disclosed comprising: identifying, based on path tracing probes sent through a network, data plane forwarding paths between nodes in the network; determining, based on topology data for the network, expected protocol-based paths between the nodes; detecting, based on a comparison of the data plane forwarding paths and the expected protocol-based paths between the nodes, a routing anomaly in the network when the data plane forwarding paths and the expected protocol-based paths differ; and causing performance of a mitigation action in the network with respect to the routing anomaly.

Abstract: Systems and techniques are provided for path tracing. For example, a process can include establishing a path tracing session associated with path tracing (PT) probe packets from a PT source node of an IPv6 network fabric. A PT probe packet can be received with a first IPv6 Destination Options Header with Path Tracing Option (DOH-PT) header that encodes path tracing information of the PT source node and indicates respective path tracing information for each PT midpoint node along a path from the PT source node to a PT sink node of the IPv6 network fabric. The received PT probe packet can be updated to include a second DOH-PT header that encodes path tracing information of the PT sink node. An updated PT probe packet includes the first and second DOH-PT headers and can be encapsulated with an additional IPv6 header corresponding to forwarding information of a collector node.

Abstract: In one implementation, a method herein comprises: determining a given time during which a computer network is unstable in response to a topology event within the computer network; causing, in response to the computer network being unstable, a measurement analysis process to perform network performance analysis on the computer network based on the computer network being unstable during the given time; and causing, in response to determining that the computer network is otherwise in a stable state, the measurement analysis process to perform network performance analysis on the computer network based on the computer network being stable.

Abstract: This disclosure describes techniques and mechanisms for performing passive measurement for combined one-way latency, packet loss metrics along with liveness detection using customer data packets ingested at a sink node in hardware for Level 2 and Level 3 VPN services. The customer data packets are sampled and copied for measurement either at source node or sink node. The duplicated measurement packet headers are punted based on the IPV6 destination option type to hardware analytics engine at sink node for analytics that populates histogram bins using the timestamps from the packets. Using the transmitted packets during a period, and received packets in all the bins, packet loss is measured. Based on the packets received status, liveness state is detected by the sink node and notified to the source node.

Abstract: Techniques for determine latency, loss, and liveness performance metrics associated with ECMP routes. The techniques may include determining that a TWAMP probe is to be sent from a first node to a second node along an equal-cost multipath ECMP route. In some examples, the first node may generate a packet for sending the TWAMP probe to the second node. The packet may include information specifying a forward path and reverse path to be traversed by the packet. In examples, the first node may send the packet to the second node along the ECMP route and subsequently receive the packet including telemetry data associated with the second node and a midpoint node of the ECMP route. Based at least in part on the telemetry data, the first node may determine a metric indicative of a performance measurement associated with the ECMP route.

Abstract: Techniques for providing an optimized behavior to source node(s) of a path tracing sequence allowing for implementation of path tracing source node behavior on an ASIC with edit-depth limitations and/or on an ASIC that does not have access to the full 64-bit timestamp. A source node having optimized behavior may be configured to record a first full 64-bit timestamp in an SRH PT-TLV header of a probe packet using the CPU of the source node. A source node having the optimized behavior may also be configured to compute a midpoint compressed data (MCD) entry and record the entry into an MCD stack of a probe packet using the NPU of the source node. A sink node and/or network controller may be configured to determine a final timestamp for the probe packet through the network by leveraging the SRH PT-TLV header and the MCD entry.

Abstract: Techniques for processing path tracing probe packets using hardware (e.g., hardware memory of a node) and without the involvement of a path tracing collector component of a network controller. A source node may be configured to generate and assign random flow labels to a large number of probe packets and send them through the network to a sink node. The sink node may determine whether a flow indicated by the probe packet has previously been traversed. Additionally, the sink node may determine latency values associated with the flows, and store probe packets in corresponding latency bins. The latency bins may be stored in hardware memory of the sink node. Telemetry data representing the probe packets stored in the latency bins may be sent to a network controller for further network analysis.

Abstract: Techniques for monitoring data transport in a network virtualization function chain (chain). A path tracing packet is generated having a Midpoint Compressed Data (MCD) to collect path tracing information of the chain. The network virtualization function node is configured to record an MCD containing Wide Local Path Tracing Identification (WL PT ID). The WL PT ID includes a first field having a value that indicates that a non-standard path tracing format is to be used and a second field that indicates a particular path tracing format to be used. The path tracing packet is passed through the chain and is received back after passing through the chain. Data collected by the path tracing packet is then analyzed to determine which network virtualization function nodes and chains the path tracing packet passed through and the amount of time taken for the path tracing packet to pass through the chain.

Abstract: Techniques for monitoring data transport in a network virtualization function (NVF) chain. A path tracing packet is generated having a Midpoint Compressed Data (MCD) to collect path tracing information of the NVF chain. The NVF node is configured to record an MCD containing Wide Local Path Tracing Identification (WL PT ID). The WL PT ID includes a first field having a value that indicates that a non-standard path tracing format is to be used and has a second field that indicates a particular path tracing format to be used. The path tracing packet is passed through the NVF chain and is then received back again after passing through the NVF chain. Data collected by the path tracing packet is analyzed to determine which NVF nodes the path tracing packet passed through, and the amount of time taken for the path tracing packet to pass through, the NVF chain.

Abstract: Techniques for monitoring data transport in a network virtualization function chain (chain). A path tracing packet is generated having a Midpoint Compressed Data (MCD) to collect path tracing information of the chain. The network virtualization function node is configured to record an MCD containing Wide Local Path Tracing Identification (WL PT ID). The WL PT ID includes a first field having a value that indicates that a non-standard path tracing format is to be used and a second field that indicates a particular path tracing format to be used. The path tracing packet is passed through the chain and is received back after passing through the chain. Data collected by the path tracing packet is then analyzed to determine which network virtualization function nodes and chains the path tracing packet passed through and the amount of time taken for the path tracing packet to pass through the chain.

Abstract: Techniques for monitoring data transport in a network virtualization function chain (chain). A path tracing packet is generated having a Midpoint Compressed Data (MCD) to collect path tracing information of the chain. The network virtualization function node is configured to record an MCD containing Wide Local Path Tracing Identification (WL PT ID). The WL PT ID includes a first field having a value that indicates that a non-standard path tracing format is to be used and a second field that indicates a particular path tracing format to be used. The path tracing packet is passed through the chain and is received back after passing through the chain. Data collected by the path tracing packet is then analyzed to determine which network virtualization function nodes and chains the path tracing packet passed through and the amount of time taken for the path tracing packet to pass through the chain.