The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.
With Path Trace, the controller reviews and collects network topology and routing data from discovered devices. Then it uses this data to calculate a path between two hosts or Layer 3 interfaces.
Optionally, you can choose to collect interface, QoS, device, and Performance Monitor statistics for a path. You can use the information gathered through Path Trace to monitor and debug traffic paths that are distributed among the various devices throughout your network.
You perform these tasks by running a path trace between two nodes in your network. The two nodes can be a combination of wired or wireless hosts and/or Layer 3 interfaces. In addition, you can specify the protocol for the controller to use to establish the path trace connection, either TCP or UDP.
Note | Path traces from the a router's loopback interface or a wireless controler's management interface are not supported. |
Note | For devices connected to a voice or video endpoint (for example, Cisco IP phones), you need to enable IP Device Tracking (IPDT) for these devices to discover voice/data VLAN information about the endpoints. For information, see IP Device Tracking Configuration. |
At every node in the path, the controller reports information about the device and path. For example, if a Layer 2 protocol is used to discover a node, the controller reports that the path is a switched path and labels it as Switched. If the controller detects load balancing decisions being made on a discovered device, it reports the path as an ECMP path and labels it as ECMP. For a complete list of the protocols and technologies that path trace can identify, see Supported Protocols and Technologies.
For unknown devices within a path trace (usually non-Cisco devices), the controller calculates the path between the unknown devices starting from the last known Cisco device (from the Host Source IP) to the next, neighboring Cisco device (sometimes the Destination Source IP). The collected IP address data about the unknown device is then sent from this neighboring Cisco device to the controller to calculate the trace path. The unknown device is displayed in the controller's GUI as a question mark (?).
Note | In certain circumstances, a path trace may flow between one of two (or more) devices. To determine which device actually received the flow for the path trace, the controller reads the NetFlow configurations and records on the devices (if they exist). By reading this data from the devices, the controller can determine the likelihood of the actual path. |
Path Trace also supports unknown destinations, where the device is not managed by the Cisco APIC-EM but is reachable.
After the Cisco APIC-EM performs an initial scan, additional on-going network scans are performed at regular intervals every few minutes. Information captured during the on-going scans are displayed in the Devices table. Click Device Inventory in the navigation pane to view the Devices table. Each time the Cisco APIC-EM performs a scan, it also reads and records access control list, quality of service, and SPAN policy configuration information from the network.
Note | If the controller can not complete a path trace for the selected hosts or interfaces, it displays the results of a partial trace. |
The following table describes the device protocols, network connections (physical, wireless, and virtual), and features that Path Trace supports.
Note | For detailed information about protocol, wireless connection, and feature support by platform and scenario, see the Supported Platforms for the Cisco Application Policy Infrastructure Controller Enterprise Module. |
Supported Device Protocols and Network Connections |
Description |
||
---|---|---|---|
Access Control List (ACL) |
Access Control List (ACL) Trace analyzes how a flow is affected by ACLs programmed on the path. After the path is calculated between the source and the destination, the ACL Trace analyzes both ingress and egress interfaces of all devices on the path. Analysis is independent among the ACLs throughout the path. For example, if an ACL has entries that would deny the traffic on an interface along the path, the results of the analysis are reported as if the traffic had reached the destination without being denied by the ACL. However, analysis of entries within an individual ACL is cumulative. That is, if a higher priority ACE is a match, lower-priority ACEs are ignored. |
||
Border Gateway Protocol (BGP) |
When BGP is used in a network, the path trace for a given application flow can be displayed through the controller's GUI. The user is able to determine the exact path a particular application is taking. The data used for this path trace calculation is obtained during the discovery process and stored in the controller's database where it is kept up to date. |
||
Dynamic Multipoint VPN (DMVPN) |
Path Trace shows DMVPN dynamic tunnels between two spokes by identifying the link information source. For more information, see Understanding DMVPN Path Trace Results. |
||
Enhanced Interior Gateway Routing Protocol (EIGRP) |
When EIGRP is used in a network, the path trace for a given application flow can be displayed through the controller's GUI. The user is able to determine the exact path a particular application is taking. The data used for this path trace calculation is obtained during the discovery process and stored in the controller's database where it is kept up to date. |
||
Equal Cost Multipath/Trace Route (ECMP/TR) |
When ECMP/TR is used in a network, the path trace for a given application flow can be displayed through the controller's GUI. The user is able to determine the exact path a particular application is taking. The data used for this path trace calculation is obtained on demand by polling the device. When performing a path trace on ECMP, Cisco Express Forwarding (CEF) lookup is performed on the device on demand for requested tuples. When a path trace detects a number of unknown or unmanaged devices in the path, the path trace is executed on demand from the last known or managed Cisco device and the path calculation is restarted from the first known or managed Cisco device in the trace route result. The unknown or unmanaged hops discovered using path trace are added to the path as unknown devices along with their IP addresses. |
||
Equal Cost Multi Path (ECMP) |
When an ECMP routing strategy is used in a network, the path trace for a given application flow can be displayed through the controller's GUI. The user is able to determine the exact path a particular application is taking. The data used for this path trace calculation is obtained through an on-demand query made through the network device at the time the path calculation request is made.
|
||
Hot Standby Router Protocol (HSRP) |
When HSRP is used in a network, the controller automatically looks up the HSRP active router for a given segment and calculates the path appropriately for a path trace. The data used for this path trace calculation is obtained during the discovery process and stored in the controller's database where it is kept up to date. |
||
Intermediate System-to-Intermediate System (IS-IS) Protocol |
When IS-IS is used in a network, the path trace for a given application flow can be displayed through the controller's GUI. The user is able to determine the exact path a particular application is taking. The data used for this path trace calculation is obtained during the discovery process and stored in the controller's database where it is kept up to date. |
||
Layer 3 Forwarding Interface |
The controller can perform path traces between two Layer 3 forwarding interfaces or between a Layer 3 forwarding interface and a host. |
||
Layer 3 Recursive Lookup |
When Layer 3 Recursive Lookup is used in a network, the path trace for a given application flow can be displayed through the controller's GUI. The user is able to determine the exact path a particular application is taking. Up to three recursive lookups are supported. The data used for this path trace calculation is obtained during the discovery process and stored in the controller's database where it is kept up to date. |
||
MPLS-VPN (WAN) |
The controller provides path trace support for a branch-to-branch connected and provider-managed MPLS-VPN service. Supported devices for this type of path trace include:
All customer edge (CE) routers should have NetFlow enabled with traffic running between the hosts and routers.
The data used for this path trace calculation is obtained through an on-demand query made through the network device at the time the path calculation request is made. |
||
Netflow |
When Netflow is used in a network, the path trace for a given application flow can be displayed through the controller's GUI. The user is able to determine the exact path a particular application is taking. When we have multiple border routers in the destination island, the Netflow cache from the devices are used to find the actual ingress border router. The Netflow record is matched from these devices on demand for a given tuple. It is essential to configure Netflow on the border routers. If Netflow is not configured, trace route is used to find the ingress interfaces, which might not be accurate. |
||
Next Hop Resolution Protocol (NHRP) |
Path Trace shows DMVPN dynamic tunnels between two spokes by identifying the LinkInformationSource as NHRP. |
||
Open Shortest Path First Protocol (OSPF) |
When OSPF is used in a network, the path trace for a given application flow can be displayed through the controller's GUI. The user is able to determine the exact path a particular application is taking. The data used for this path trace calculation is obtained during the discovery process and stored in the controller's database where it is kept up to date. |
||
Physical connectivity (Ethernet, Serial and Packet over SONET (PoS)) |
The path trace for a given application flow can be displayed over Ethernet, Serial over SONET, and Packet over SONET. The data used for this path trace calculation is obtained during the discovery process and stored in the controller's database where it is kept up to date. |
||
Spanning Tree Protocol (STP) |
The controller provides Layer 2 support for Spanning Tree Protocol (STP). The data used for this path trace calculation is obtained during the discovery process and stored in the controller's database where it is kept up to date. |
||
Static Routing |
When static routing is used in a network, the path trace for a given application flow can be displayed through the controller's GUI. The user is able to determine the exact path a particular application is taking. The data used for this path trace calculation is obtained during the discovery process and stored in the controller's database where it is kept up to date. |
||
Sub interfaces |
When sub interfaces are used within a network, the path trace for a given application flow is displayed. The path trace between the two sub interfaces is displayed, so that the user can visualize an end-to-end path for an application. |
||
Virtual connectivity—Layer 2 Port Channel |
When virtual connectivity (Layer 2 port channel) is used within a network, the path trace for a given application flow is displayed. The path trace over virtual interfaces (port channels) is displayed, so that the user can visualize an end-to-end path for an application. |
||
Virtual connectivity—VLAN/SVI |
When virtual connectivity (VLAN/SVI) is used within a network, the path trace for a given application flow is displayed. The path trace is displayed, so that the user can visualize an end-to-end path for an application. The data used for this path calculation is obtained during the discovery process and stored in the controller's database where it is kept up to date. |
||
Virtual Routing and Forwarding (VRF) |
Path trace supports VRF Lite and VRF route leaking. For information, see Understanding VRF Path Trace Results. |
||
Wireless |
The controller provides path trace support for Control and Provisioning of Wireless Access Points (CAPWAP), 802.11, and mobility. When wireless network elements are used, the path trace for a given application flow is displayed. The user knows the exact path a particular application is taking.
The data used for this path calculation is obtained during the discovery process and stored in the controller's database where it is kept up to date. |
You can perform a path trace between two nodes in your network. The two nodes may be two hosts and/or Layer 3 interfaces.
Note | The path trace application may display accuracy notes. Accuracy notes are red boxes that appears on a node or path segment indicating the accuracy of the computed path as a percentage. Place your cursor over the note to view suggestions of corrective actions to take to improve the path trace accuracy. For example, you may be prompted to enter port values and run the path trace again. |
Make sure that you have devices in your inventory. If not, discover devices using the Discovery function.
Ensure that the controller has SSH or Telnet access to the devices.
Step 1 | In the Navigation pane, click Path Trace. | ||
Step 2 | From the path trace toolbar, click Start new Path Trace. | ||
Step 3 | In the Source field,
enter the IP address of the host or the Layer 3 forwarding interface where you
want the trace to start.
If you enter the device IP address manually, you need to select the device from the list and then the interfaces for that device. | ||
Step 4 | In the Destination field, enter the IP address of the host or Layer 3 forwarding interface where you want the trace to end. You can also enter an IP address of an unmanaged device (called an unknown destination).
If you enter the device IP address manually, you need to select the device from the list and then the interfaces for that device. | ||
Step 5 | (Optional)To configure source and destination ports or protocols, click More Options. | ||
Step 6 | (Optional)In the Source Port field, enter the port number of the host where you want the trace to end. | ||
Step 7 | (Optional)In the Destination Port field, enter the port number of the host where you want the trace to end. | ||
Step 8 | (Optional)In the Protocol field, choose tcp or udp from the drop-down menu for the Layer 4 path trace protocol. | ||
Step 9 | (Optional)To configure the path trace to refresh every 30 seconds, check the Periodic Refresh (30 sec) check box. | ||
Step 10 | (Optional)To configure the path trace
to collect additonal statistics, check the Stats check
box and any of the following check boxes, as desired:
| ||
Step 11 | (Optional)Select the ACL Trace check box to run an ACL-based path trace. | ||
Step 12 | Click Start Trace.
Review the path trace output. For more information, see Understanding Path Trace Results. | ||
Step 13 | Unless you performed a path trace to an unknown destination, you can view the path trace in the Topology window. To do so, click View in Topology. The Topology window opens in a new window with the path trace highlighted in your network. For more information about the Topology window, see the Cisco Application Policy Infrastructure Controller Enterprise Module Administrator Guide.
|
You can perform a path trace between two nodes in your network. The two nodes may be two hosts and/or Layer 3 interfaces.
Note | The path trace application may display accuracy notes. Accuracy notes are red boxes that appears on a node or path segment indicating the accuracy of the computed path as a percentage. Place your cursor over the note to view suggestions of corrective actions to take to improve the path trace accuracy. For example, you may be prompted to enter port values and run the path trace again. |
Make sure that you have devices in your inventory. If not, discover devices using the Discovery function.
Ensure that the controller has SSH or Telnet access to the devices.
Step 1 | In the Navigation pane, click Path Trace. | ||
Step 2 | From the path trace toolbar, click Start new Path Trace. | ||
Step 3 | In the Source field, enter the IP address of the host
or the Layer 3 forwarding interface where you want the trace to start.
If you enter the device IP address manually, you need to select the device from the list and then the interfaces for that device. | ||
Step 4 | In the Destination field, enter the IP address of the host or Layer 3 forwarding interface where you want the trace to end. You can also enter an IP address of an unmanaged device (called an unknown destination).
If you enter the device IP address manually, you need to select the device from the list and then the interfaces for that device. | ||
Step 5 | (Optional)To configure source and destination ports or protocols, click More Options. | ||
Step 6 | (Optional)In the Source Port field, enter the port number of the host where you want the trace to end. | ||
Step 7 | (Optional)In the Destination Port field, enter the port number of the host where you want the trace to end. | ||
Step 8 | (Optional)In the Protocol field, choose tcp or udp from the drop-down menu for the Layer 4 path trace protocol. | ||
Step 9 | (Optional)To configure the path trace to refresh every 30 seconds, check the Periodic Refresh (30 sec) check box. | ||
Step 10 | (Optional)To configure the path trace to collect additonal statistics, check the
Stats check box and any of the following check boxes,
as desired:
| ||
Step 11 | Select the ACL Trace check box to run an ACL-based path trace. | ||
Step 12 | Click Start Trace.
Review the path trace output. For more information, see Understanding ACL Path Trace Results. | ||
Step 13 | Unless you performed a path trace to an unknown destination, you can view the path trace in the Topology window. To do so, click View in Topology. The Topology window opens with the path trace highlighted in your network. For more information about the Topology window, see the Cisco Application Policy Infrastructure Controller Enterprise Module Administrator Guide.
|
After you run a path trace, the results are displayed in the Path Trace window.
The Path Trace Toolbar provides the following options and information:
Filters—Allows you to search for path traces by source or destination IP address, source or destination ports, protocol, creation date, or statistics gathered (QoS, Device, Interface, Perf Mon, and ACL trace)
Start new Path Trace—Displays a dialog box where you can define the parameters for your path trace.
Copy icon—Allows you to create a new path trace using the parameters that are defined in the selected (source) path trace. You can keep any of the values from the source path trace and change, add, or deselect any parameters for the new path trace.
The Path Traces pane lists the path traces in one of three categories:
IN PROGRESS— Path is currently being calculated. No results to show yet.
ACTIVE—A path has been calculated and will be refreshed every 30 seconds. Statistics may also be collected periodically.
COMPLETED—The path has been calculated one time and is not being refreshed. However, statistics may still be collected periodically.
At the top of the Trace Results Graphical Display pane, the toolbar provides buttons for adjusting the path trace display.
Name 1 |
Description |
||
---|---|---|---|
View Small |
Minimizes the trace results to view the details better. |
||
Reverse |
Displays the trace results from the host destination IP to the host source IP. The reverse path trace graphic is displayed directly below the original path trace. The reverse path trace details are displayed to the right of the original path trace details.
|
||
Scroll Lock |
Locks the scrolling of the path trace and reverse path trace details windows. (Available when Show Reverse is enabled.) |
||
Show Duplicate Devices |
Displays or hides duplicate devices within a path trace. |
||
ACL Trace checkbox 2 |
Displays an icon at each device or interface that indicates whether any ACLs are blocking traffic on the path. |
||
Stats |
If statistics were collected for the trace, you can select one or more of the interface, QoS, device, and performance monitor check boxes to display the corresponding information in the graphical display. |
||
View in Topology |
Opens the Topology window and highlights the path trace results in your network topology. If you performed a path trace to an unknown destination, this option is not available. For more information about using the Topology window, see the Cisco Application Policy Infrastructure Controller Enterprise Module Administrator Guide. |
The controller graphically displays the path direction and the hosts and devices (including their IP addresses) along the path between the source (host A) and destination (host B). Clicking an individual device in the path trace highlights the device in the Trace Results Device Details area. The display also shows the protocol of the path source between devices along the path: Switched, STP, ECMP, Routed, Trace Route, or other source type.
If you performed an ACL trace, the devices show whether the traffic matching your criteria would be permitted or denied based on the ACLs configured on the interfaces. For more information, see Performing an ACL-Based Path Trace.
You can review the detailed information displayed for each device in the path trace.
Name |
Description |
---|---|
IP |
IP address of the device. |
Type |
Wired or wireless device (access point, switch, or router). |
Link Source |
Information about the link between two devices (source and destination). Link information is based on the configuration of the source device.
|
Tunnels |
Path trace provides a graphical view of these types of tunnels:
|
Ingress interface |
Ingress interface of the device for the path trace (physical or virtual). For example, a physical ingress interface is GigabitEthernet1/0/1 and a virtual ingress interface is GigabitEthernet1/3 [Vlan1]. If statistics were gathered for this path trace, clicking the View Stats button displays the interface or QoS statistics. For information, see Interface Statistics or QoS Statistics. |
Egress interface |
Egress interface of the device for the path trace (physical or virtual). For example, a physical interface is GigabitEthernet1/0/2 and a virtual ingress interface is GigabitEthernet1/4 [Vlan2]. If statistics were gathered for this path trace, clicking the View Stats button displays the interface or QoS statistics. For information, see Interface Statistics or QoS Statistics. |
Accuracy note |
If there is uncertainty about the path trace on a segment between devices, path trace displays a note that indicates the accuracy of the computed path as a percentage. For example, 10 percent would indicate lower accuracy than 90 percent. Place your cursor over the note to view suggestions of corrective actions to take to improve the path trace accuracy. For example, you may be prompted to enter port values and run the path trace again. |
VRF |
If Path Trace detects a VRF on a router, it displays the VRF in the graphical display and provides the interface name and VRF name. For more information, see Understanding VRF Path Trace Results. |
If you specified that device statistics be included in the path trace, statistical information about the device is gathered and displayed. You can select or deselect one or more of the options from the Stats drop-down list so that you can isolate different information.
For information about the statistics, see the following sections:
An ACL path trace shows whether the traffic matching your criteria would be permitted or denied based on the ACLs configured on the path.
The following rules effect the ACL path trace results:
Only matching ACEs are reported.
If you leave out the protocol, source port, or destination port when defining a path trace, the results include ACE matches for all possible values for these fields.
If no matching ACEs exists in the ACL, the flow is reported to be implicitly denied.
When you perform a path trace on a spoke-to-spoke connection, Path Trace determines (in real time) whether there is a dynamic NHRP entry due to traffic occurring between the two spokes. If there is, Path Trace shows the LinkInformationSource as NHRP.
If the there is no traffic between the two spokes, Path Trace uses the inventory data collected during device discovery to determine the next hop server (NHS), which is the hub for the two spokes. Path trace identifies and highlights the routing protocol advertised by hub, for example EIGRP or OSPF. In addition, path trace shows any intermediate hops, including service providers (shown as a cloud icon).
Path Trace identifies all tunnel source interface types and highlights them as egress or ingress interfaces and indicates the tunnel transport types, such as Front Door VRF (FVRF) and Inside VRF (IVRF).
PathTrace shows the mGRE tunnel interface as a virtual interface and the underlay interface as physical interface on a DMVPN endpoint.
Path trace supports VRF Lite and VRF route leaking. If Path Trace detects a VRF on a router, it displays the VRF in the graphical display and provides the interface name and VRF name. VRFs are shown as a colored circle, making it easy to see where they are along the path. VRFs with the same name have the same color.
You can perform a path trace between two nodes in your network and collect the following types of statistics about the path:
Quality of Service (QoS)
Interface
Device
Performance Monitor (If you choose to run a path trace to collect Perf Mon statistics, the Cisco APIC-EM configures all of the devices in the requested path with the necessary flow monitor configuration. For information about this configuration, see Performance Monitor Configuration.)
Note | The path trace application may display accuracy notes. Accuracy notes are red boxes that appears on a node or path segment indicating the accuracy of the computed path as a percentage. Place your cursor over the note to view suggestions of corrective actions to take to improve the path trace accuracy. For example, you may be prompted to enter port values and run the path trace again. |
Make sure that you have devices in your inventory. If not, discover devices using the Discovery function.
Step 1 | In the Navigation pane, click Path Trace. | ||
Step 2 | From the path trace toolbar, click Start new Path Trace. | ||
Step 3 | In the Source field, enter the IP address of the host or the Layer 3 forwarding interface where you want the trace to start. | ||
Step 4 | In the Destination field, enter the IP address of the host or Layer 3 forwarding interface where you want the trace to end. | ||
Step 5 | (Optional)To configure source and destination ports or protocols, click More Options. | ||
Step 6 | (Optional)In the Source Port field, enter the port number of the host where you want the trace to start. | ||
Step 7 | (Optional)In the Destination Port field, enter the port number of the host where you want the trace to end. | ||
Step 8 | (Optional)In the Protocol field, choose either tcp or udp from the drop-down menu for the Layer 4 path trace protocol. | ||
Step 9 | (Optional)To configure the path trace to refresh every 30 seconds, check the Periodic Refresh (30 sec) check box. | ||
Step 10 | Check the Stats check box. | ||
Step 11 | Check any of the following check boxes corresponding to the type of statistics that will be collected:
| ||
Step 12 | Click Start Trace.
The results are displayed in the Trace Results Device Details pane. For information, see the following topics: | ||
Step 13 | (Optional)To view the path trace in the
Topology window. Click View in
Topology.
The Topology window opens with the path trace highlighted in your network.
For more information about the Topology window, see the Cisco Application Policy Infrastructure Controller Enterprise Module Administrator Guide. |
Understanding the Statistics Retrieved During a Path Trace
If you specified that device statistics be included in the path trace, Path Trace gathers and displays statistical information about the device. Not all device types support all of the parameters (5 minutes, 5 seconds, and 1 minute). If a device does not support a particular parameter, Path Trace displays N/A (not supported).
Parameter |
Description |
---|---|
CPU Usage |
|
5 Mins Usage(%) |
Percentage of the device's CPU usage for the last 5 minutes. |
5 Secs Usage(%) |
Percentage of the device's CPU usage for the last 5 seconds. |
1 Min Usage(%) |
Percentage of the device's CPU usage for the last minute. |
Refreshed At |
Date and time when the information was gathered. |
Memory Usage |
|
Refreshed At |
Date and time when the information was gathered. |
Memory Usage(bytes) |
The sum of the physical memory usage and I/O memory usage (in bytes) that the device is using. |
Total Memory (bytes) |
Total memory (in bytes) of the device. |
When you perform a path trace, you can collect interface statistics that show how the interfaces are performing. In this way, you can monitor the effect of the QoS policies on the network and make any changes, if necessary. The following table lists the interface statistics that are retrieved.
When you perform a path trace, you can collect QoS statistics that show how the QoS policies are performing. The only interface statistics included in the QoS statistics are those for the border router egress interface. Collecting QoS statistics helps you to monitor the effect of the QoS policies on your network devices and make any changes, if necessary.
The following table lists the QoS Statistics that are retrieved.
Parameter |
Description |
---|---|
Policy Name |
Drop-down list of policy names that QoS statistics have been collected about. |
Class Map Name |
Name of the class map. |
Num of Bytes |
Average number of bytes forwarded by the queue. |
Offered Rate |
Traffic rate offered for that particular traffic. |
Queue Bandwidth (bps) |
Rate (bps) at which the queue can process packets. |
Queue Total Drops |
Number of packets dropped from the queue due to the queue reaching its maximum threshold. |
Drop Rate |
Number of bits per second at which packets are being dropped from the queue. |
Num of Packets |
Number of packets that the queue can hold. |
Queue Depth |
Maximum number of packets that the queue can hold before it must start dropping packets. |
Queue No Buffer Drops |
Number of times that packets were dropped due to not enough buffer allocated. |
Refreshed At |
Date and time that the current statistics were gathered. |
When you run a path trace to collect Perf Mon statistics, the Cisco APIC-EM automatically configures all of the devices in the requested path with the necessary flow monitor configuration, and then removes the configuration when it is no longer needed (no pending performance monitor path trace for the path or 24 hours, whichever is first). For information about this configuration, see Performance Monitor Configuration.
The following table lists the performance monitor statistics that are retrieved.
Parameter |
Description |
---|---|
Packet Count |
Total number of IP packets sent. |
Byte Rate |
Average number of packets or bytes (as configured) that were processed by the monitoring system per second during the monitoring interval. |
Packet Loss |
Total number of IP packets lost by any intermediate system in the monitored flow. |
Packet Loss (%) |
Percentage of IP packets lost by any intermediate system in the monitored flow. |
RTP Jitter Mean |
Mean deviation (in microseconds) of the difference in packet spacing at the receiver compared to the sender for a pair of packets. |
RTP Jitter Min |
Minimum value of the Real-time Transport Protocol (RTP) jitter in microseconds. |
RTP Jitter Max |
Maximum value of the Real-time Transport Protocol (RTP) jitter in microseconds. |
IPv4 DSCP (Hexadecimal) |
Hexadecimal value of the IPv4 differentiated services code point (DSCP) type of service (ToS). |
IPv4 TTL |
Value of the IPv4 time-to-live (TTL). |
Input Interface |
Name of the input interface that was used as match criteria. |
Output Interface |
Name of the output interface that was used as match criteria. |
Refreshed At |
Date and time that the performance monitor statistics were gathered. |
Source IP |
IP address of the source interface for all of the packets sent by a flow exporter. |
Destination IP |
IP address of the destination interface for all of the packets sent by a flow exporter. |