> For the complete documentation index, see [llms.txt](https://docs.thousandeyes.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.thousandeyes.com/product-documentation/tests/network-tests.md).

# Network Tests

This category of tests measures the network performance and path between an agent and a target device.

## Related Video

### Configuring Network Tests

Watch this video for a walkthrough of configuring network tests.

{% embed url="<https://thousandeyes.wistia.com/medias/bx7mqy0xyg>" %}

Network test types include

* Agent-to-server tests
* Agent-to-agent tests

Select any combination of Cloud and Enterprise Agents and a target URL or IP address. ThousandEyes sends lightweight bursts of TCP or ICMP traffic from agents to the target to measure loss, latency, and jitter. When you have agents on both ends, you can also run network tests between them that use UDP.

Both agent-to-server and agent-to-agent test types contain two views. The Overview view shows data on packet loss, latency, jitter (the mean deviation of the latency), path MTU, and, when enabled, transfer-rate metrics. Agent-to-server tests from Enterprise Agents can show **Available Bandwidth** and **Capacity**. Agent-to-agent tests can show **Throughput**. The Path Visualization view is a traceroute-like map of each router in the path from agent to target. For more information about views, see [Views](https://docs.thousandeyes.com/product-documentation/internet-and-wan-monitoring/viewing-data). For more information about path visualization, see [Path Visualization](https://docs.thousandeyes.com/product-documentation/internet-and-wan-monitoring/path-visualization).

## Agent-to-Server Tests

An agent-to-server test measures network performance as seen from ThousandEyes agent(s) towards a remote server. The target could either be an IP address or a hostname. Measurements in an agent-to-server test combine parameters of both, forward and reverse paths. To measure direction-specific parameters an agent-to-agent test can be utilized.

### Use Cases for Agent-to-Server Tests

* Measuring network performance when accessing the target remote server from agents assigned to test.
* Understand network path changes between source to destination.
* Verification of target availability.
* Identify network degradation along the network path.
* Verify network management of DSCP, MTU, and optimization.
* Monitor ingress traffic load distribution across ISPs.

#### Agent-to-Server Metrics

Agent-to-server tests collect **network-layer** end-to-end metrics (loss, latency, jitter, and optional Available Bandwidth, Capacity, MTU, and BGP as configured). They do **not** use web-layer definitions such as HTTP **Availability** or **Response time**; those belong to [HTTP Server](https://docs.thousandeyes.com/product-documentation/tests/http-server-tests) and related web tests. For precise metric definitions, see [ThousandEyes Metrics: What Do Your Results Mean?](https://docs.thousandeyes.com/product-documentation/tests/thousandeyes-metrics-what-do-your-results-mean) under **Network Layer**.

* **Loss (%)**: Percentage of packets lost during transmission.
* **Latency (ms)**: Round-trip time for packets to reach the target and return.
* **Jitter (ms)**: Variation in latency between packets.
* **Available Bandwidth (Mbps)**: Estimate of how much of the path's traffic capacity is usable right now, when bandwidth measurement is enabled for tests from Enterprise Agents.
* **Capacity (Mbps)**: Estimated upper limit of the path's transfer rate, when bandwidth measurement is enabled for tests from Enterprise Agents.
* **Error Details**: Specific errors encountered (for example, timeout, connection refused).
* **Path Trace**: Hops, IP addresses, and latency per hop in the network path.

#### Agent-to-Server Views

* Timeline (Agent-to-Server Layer): provides data on packet loss, latency, jitter (the mean deviation of the latency), path MTU and (Enterprise Agents only) bandwidth.
* Map
* Path Visualization: displays a router-by-router view of the nodes in the path from the agents to the target, along with IP, MPLS and routing information about each node and link between nodes.

Below is the *Path Visualization* for a test targeting google.com. Restricted access to Google results in 100% packet loss from Cloud Agent Beijing, China (China Unicom). The red circles signify nodes with forwarding loss. Hovering over a specific node will provide a dialog with detailed information.

![Agent-to-server Path Visualization showing packet loss from Cloud Agent Beijing, China](https://1112912342-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-M4QARF6s57qxMrOHDTZ%2Fuploads%2Fgit-blob-4990a01867237b03ea876d0d281558c778641f2a%2Fproduct-documentation_tests_guide-to-thousandeyes-test-types-3.png?alt=media\&token=8611e764-b170-4b34-9086-7fd6c989e9f7)

For more information about the *Agent-to-Server* layer, see [Using the Network View](https://docs.thousandeyes.com/product-documentation/internet-and-wan-monitoring/viewing-data/using-the-network-overview).

### Other Included Tests

* BGP test

### Manually Configuring Agent-to-Server Tests

To configure an Agent-to-Server test:

1. In the ThousandEyes platform, navigate to **Network & App Synthetics > Test Settings**.
2. Click the **Add New Test** button in the upper right corner of the screen.
3. From the menu that appears, select the card titled **Agent to Server**, located on the bottom right.
4. The configuration page is divided into the following sections: Basic Settings, Network Settings, and Additional Settings.

### Agent-to-Server Test Basic Settings

| Setting                      | Description                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          |
| ---------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Target**                   | The destination domain name or IP address for the test.                                                                                                                                                                                                                                                                                                                                                                                                                                              |
| **How often the test runs**  | The frequency at which the test runs. Options are 1, 2, 5, 10, 15, 30, or 60 minutes. More frequent intervals are recommended for business-critical services.                                                                                                                                                                                                                                                                                                                                        |
| **Where the test runs from** | Select one or more ThousandEyes Cloud and Enterprise Agents to run the test from. For help, see [Using the Agent Selector](#using-the-agent-selector).                                                                                                                                                                                                                                                                                                                                               |
| **Protocol**                 | The transport layer protocol (TCP or ICMP) used to send packets to the target.                                                                                                                                                                                                                                                                                                                                                                                                                       |
| **Port**                     | <p>The destination TCP port on the target. This setting is available only when the <strong>Protocol</strong> is set to TCP. Use this to:</p><ul><li>Test specific application ports (for example, 443 for HTTPS).</li><li>Validate firewall rules and security policies.</li><li>Analyze network paths for different traffic types.</li></ul>                                                                                                                                                        |
| **Path trace mode**          | <p>When <strong>In Session</strong> is selected, the path trace is performed within an established TCP session.<br><br>> <strong>Note:</strong> This mode is designed for environments where stateful firewalls (for example, Palo Alto Networks and Juniper SRX) might otherwise block standard path trace packets by misinterpreting them as malicious probes.</p>                                                                                                                                 |
| **Probing mode**             | <p>Defines the TCP probing method used for measurements. This setting is available only when the <strong>Protocol</strong> is set to TCP.</p><ul><li><strong>Prefer SACK:</strong> (Default) Uses a single TCP connection with Selective Acknowledgement (SACK) for efficient, low-overhead measurements.</li><li><strong>Force SYN:</strong> Sends a stream of up to 50 SYN packets from unique source ports. Use this method if SACK is not supported or is blocked in the network path.</li></ul> |
| **Alerts**                   | Enable or disable alerts for this test and assign one or more alert rules. The dropdown shows the number of selected rules out of the total available.                                                                                                                                                                                                                                                                                                                                               |
| **Labels**                   | Assign agent labels to this test for filtering and organization. The dropdown shows the number of selected labels out of the total available.                                                                                                                                                                                                                                                                                                                                                        |
| **Test name**                | (Optional) A name for the test. The name auto-populates with the target's domain or IP address but can be manually edited. The maximum length is 255 characters.                                                                                                                                                                                                                                                                                                                                     |

### Agent-to-Server Test Network Settings

| Setting                          | Description                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               |
| -------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Test execution schedule**      | <p>Determines the timing of test rounds for all assigned agents.</p><ul><li><strong>Default:</strong> All agents start the test simultaneously at each interval. Use for synchronized data collection and baseline comparisons.</li><li><strong>Randomized:</strong> Staggers agent start times randomly within the test interval. Use to prevent traffic bursts and simulate more realistic user behavior.</li></ul>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     |
| **Define which data to collect** | <p>Select the types of network data to collect during the test.</p><ul><li><strong>Perform network measurements:</strong> Enables the collection of core network metrics like loss, latency, and jitter. This option is enabled by default.</li><li><strong>Perform bandwidth measurements:</strong> Measures <strong>Capacity</strong> and <strong>Available Bandwidth</strong> for tests from Enterprise Agents. <strong>Capacity</strong> estimates the path's upper traffic limit, and <strong>Available Bandwidth</strong> estimates how much of that capacity is usable right now.<br><br>> Note: This option does not increase test unit consumption but does generate additional traffic, which might impact performance on resource-constrained networks. It is recommended to keep this option disabled for tests using agents on routers or switches.</li><li><strong>Perform MTU measurements:</strong> Determines the Maximum Transmission Unit (MTU) size along the network path to identify issues related to packet fragmentation.</li><li><strong>Collect BGP data:</strong> Correlates network data with BGP routing data from public and private monitors. Tests with IPv4 targets use IPv4 BGP monitors, and tests with IPv6 targets use IPv6 BGP monitors.</li></ul> |
| **Ping payload size**            | Defines the data portion of end-to-end ICMP or TCP probes, excluding headers. **Auto** uses a 0-byte payload for ICMP and a 1-byte payload for TCP. **Manual** accepts 1–9,188 bytes. Jumbo-frame values above 1,400 bytes are supported only when every assigned agent is an Enterprise Agent. Keep the value at 1,400 bytes or less for Cloud-only or mixed-agent assignments. Use a manual value to validate how the path handles a specific packet size.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              |
| **Transmission rate**            | Controls the rate at which test packets are sent. Use this to simulate network load, validate QoS policies, and analyze how different traffic levels impact performance.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  |
| **Number of path traces**        | The number of path traces (3 to 10) performed in each test round. Increasing the number of traces helps discover and visualize multiple or asymmetric network paths.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      |
| **DSCP**                         | Sets the Differentiated Services Code Point (DSCP) value in the IP header of test packets to simulate a specific Quality of Service (QoS) policy. Select a predefined option (for example, Best Effort or Expedited Forwarding) or a custom value.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        |
| **IPv6 Policy**                  | <p>Determines how the agent resolves the target's domain name in dual-stack (IPv4/IPv6) environments.</p><ul><li><strong>Agent's Policy:</strong> Uses the agent's local DNS resolution policy.</li><li><strong>IPv4 only:</strong> Forces DNS resolution to IPv4 addresses.</li><li><strong>Prefer IPv6:</strong> Attempts to resolve to an IPv6 address first, with a fallback to IPv4.</li><li><strong>Force IPv6:</strong> Resolves only to IPv6 addresses.</li></ul>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 |

### Agent-to-Server Test Additional Settings

| Setting                      | Description                                                                                                                                            |
| ---------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------ |
| **Description**              | An optional, user-defined description for the test. Use this field to add context, change history, or other notes for fellow users.                    |
| **Alert suppression window** | Temporarily disables all alerts for this test for a defined period. Use this feature for planned maintenance windows to prevent false-positive alerts. |

## Agent-to-Agent Tests

An agent-to-agent test evaluates the performance of the underlying network between two physical sites. The source and target for performing measurements here are ThousandEyes agents and can be both a Cloud Agent, an Enterprise Agent or a combination of both. For more information, see the [agent-to-agent test overview](https://docs.thousandeyes.com/product-documentation/tests/network-tests/agent-to-agent-test-overview).

### Use Cases for Agent-to-Agent Tests

* Measure bidirectional network throughput.
* Measuring network connectivity characteristics between:
  * Multiple data centers.
  * Regional branch offices connecting to data centers.
  * Regional branch offices connecting to IAAS cloud environments.
  * Data centers connecting to IAAS environments.
* Branch office to HQ network quality via VPN and so on.
* Detect packet dropping network nodes on the path between source to destination.
* Evaluate the return path with bidirectional testing. Measure network performance and throughput between locations.
* Compare end-to-end network performance and characteristics between the forwarding and return paths.
* Measuring network characteristics between data centers, offices, and cloud environments.
* Evaluate network connections for specific applications.
* Detect latency and loss along the network path.

#### Agent-to-Agent Metrics

* **Loss (%)**: Packet loss percentage in each direction.
* **Latency (ms)**: Round-trip time or one-way latency (if agents are clock-synced).
* **Jitter (ms)**: Variation in latency.
* **Throughput (bps, Kbps, Mbps)**: Data transfer rate between agents.
* **Path MTU (bytes)**: Maximum Transmission Unit size along the path.
* **Path Trace**: Hops, IP addresses, and latency per hop.
* **Error Details**: Specific errors (for example, packet drops or routing issues).

**Agent-to-Agent Views**

* Timeline (Agent-to-Agent layer): provides data on packet loss, latency, jitter (the mean deviation of the latency), and throughput.
* Map
* Path Visualization: displays router-by-router view of the nodes in the path from the agents to the target, along with IP, MPLS and routing information about each node and link between nodes. Arrows indicated direction of packet through the intermediate nodes.

The agent-to-agent test below depicts a connection error between Cloud Agent Wellington, New Zealand and Cloud Agent Johannesburg, South Africa.

![Agent-to-agent test showing a connection error between Cloud Agent Wellington, New Zealand, and Cloud Agent Johannesburg, South Africa](https://1112912342-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-M4QARF6s57qxMrOHDTZ%2Fuploads%2Fgit-blob-da1895cd05ace0271b0dc953f480cb00c471f9c8%2Fproduct-documentation_tests_guide-to-thousandeyes-test-types-4.png?alt=media\&token=c470224a-a67a-4a0b-bcf8-b4e31228037c)

For more information about Agent-to-Agent views, see [Using the Network View](https://docs.thousandeyes.com/product-documentation/internet-and-wan-monitoring/viewing-data/using-the-network-overview).

### Other Included Tests

* BGP test

### Manually Configuring Agent-to-Agent Tests

{% hint style="warning" %}
Note: The user interface for Test Settings is being updated. The information on this page may not reflect the new experience. The documentation will be updated shortly to align with these improvements.
{% endhint %}

* **Test Type**: agent-to-server or agent-to-agent.
* **Test Name**: This optional parameter gives the test a label. When no label is provided, then the values in the **Target** and (if the **Protocol** is TCP) the **Port** fields will be combined to comprise the **Test Name.** A test name cannot exceed 255 characters.
* **Interval**: How frequently the test will be run.
* **Alerts**: When the **Enable** box is checked, the Alert Rules and Alert Suppression Windows selected in their respective dropdown list will be active for the test. You can create, modify and delete Alert Rules with the **Edit Alert Rules** link.

#### Agent-to-Agent Test Basic Configuration

* **Target Agent**: Select a ThousandEyes Enterprise Agent available to your account.
* **Agents**: ThousandEyes Enterprise Agents agents that are available to your account. Select one or more Agents to assign them to this test.
* **Direction**: Select the direction of network and (optionally) throughput measurements between Agents as follows:
  * **Source to Target**: All selected agents will perform network measurements to Target Agent.
  * **Target to Source**: Target Agent will perform network measurements to each agent selected under the **Agents** tab.
  * **Both Directions**: Network measurements are performed from each selected Agent to Target Agent and from Target Agent to each selected Agent.
* **Protocol**: The protocol used when sending packets to the target.
* **Enable Throughput**: Check this box to perform throughput measurements in selected direction.

  * **Duration**: Use the slider to set time period for throughput measurements.
  * **Simultaneous Connections** (TCP only): Number of connections for each Source Agent to make to the Target Agent.
  * **Maximum Rate** (UDP only): Agents send packet for set duration as fast as possible.
  * **Specified Rate** (UDP only): Input sending rate of throughput packets.

  **NOTE**: It's not recommended to run tests on any agent installed on a routing or switching device due to common load, resource limitations, and the resource requirements of ThousandEyes bandwidth and throughput tests.
* **Path Trace Mode**: When the **In Session** checkbox is selected, perform a path trace "in session" within an agent to agent test, by initiating a TCP session with the target server, and sending path trace packets within that session. **NOTE:** This option is available to accommodate customer environments where middleboxes like Palo Alto and Juniper firewalls interfere with the way the ThousandEyes platform collects path trace metrics. These products misinterpret the path tracing as malicious probes, so by first establishing the TCP session the firewall doesn't reject path trace packets.
* **Alerts**: Check the **Enable** box to assign Alert Rules and create suppression windows.

#### Agent-to-Agent Test Network Settings

* **Server Port**: The port number on the Target Agent to which agents send packets.
* **Maximum segment size (MSS)**: For TCP tests, set the MSS to **Auto** or **Manual**. **Auto** uses path MTU discovery to select an MSS that avoids fragmentation. **Manual** accepts 30–9,176 bytes and sends the value you specify. Values above 1,400 bytes require Enterprise Agents for both ends of the test.
* **Collect BGP data**: Check this box to enable the **BGP Path Visualization** view\.The **BGP Public Monitors** option button allows you to choose whether ThousandEyes' public BGP Monitors should be used for monitoring target prefixes. The **Private BGP Monitors** dropdown box allows you to select which private BGP Monitors should be used for monitoring target prefixes. By default, all public and private monitors are selected.

  Note that some monitors are IPv4 monitors and some are IPv6 monitors. Tests with IPv4 targets will display only IPv4 monitors in the BGP Path Visualization; similarly, tests with IPv6 targets display only IPv6 monitors in the BGP Path Visualization.
* **Transmission Rate**: Select the checkbox to “Enforce fixed packet rate”. This will reveal a slider bar that offers the option to reduce rate packets are sent to measure the network in packets per second.
* **No. of Path Traces**: Three path trace packets are used by each agent by default to discover each hop in the Path Visualization to the target. Uncheck the box to display a slider which allows selection of 1 - 10 packets. To learn more about path trace, see [Getting Started with Path Visualization](https://docs.thousandeyes.com/product-documentation/internet-and-wan-monitoring/path-visualization/).
* **Ping payload size**: For UDP tests, set the payload to **Auto** or **Manual**. **Auto** uses path MTU discovery to select a payload that fits the path. **Manual** accepts 30–9,188 bytes and sends the value you specify. Values above 1,420 bytes require Enterprise Agents for both ends of the test. The total packet size also includes the IP and UDP headers.
* **DSCP selector**: Set the Differentiated Services Code Point (DSCP) field of the IP header for probe packets, in order for the packets to be handled by quality-of-service (QoS) devices. The default value is DSCP=0 (best effort).

## Using the Agent Selector

Use the agent selector to choose the Cloud Agents or Enterprise Agents that will run your test. In the Cloud Agents tab, recommendations can help you choose Cloud Agents based on geographic coverage, agents you have already selected, or your team's use of similar tests. When recommendations are available for your account, choose a method and review the suggested agents before applying them.

### Recommendation Methods

| Method                    | How it chooses Cloud Agents                                      |
| ------------------------- | ---------------------------------------------------------------- |
| **Global coverage**       | Suggests agents in locations around the world.                   |
| **Local coverage**        | Suggests agents near the Cloud Agents you have already selected. |
| **Based on test history** | Suggests agents your team uses most for similar tests.           |
| **None**                  | Hides recommendations.                                           |

![Cloud Agent selector showing the available recommendation methods](https://1112912342-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-M4QARF6s57qxMrOHDTZ%2Fuploads%2Fgit-blob-df0a940269759b582f9a8d2991ab7aa48d7454d2%2Fcloud-agent-recommendation-methods.png?alt=media)

### Using Recommendations

1. In the agent selector, select **Basic**, then select the **Cloud Agents** tab.
2. Open the recommendation method menu and select a method.
3. Review the recommended agents. Select **Apply** to add them to the test. The selector then shows only selected agents.
4. To remove the recommended set, select the recommendation button again after all recommended agents are selected. You can also select or clear individual agents.

If the chosen method has no eligible agents, the selector shows **No recommendations**. For Page Load and Transaction tests, and API tests that use BrowserBot, recommendations include only Cloud Agents with BrowserBot support.

### Other Agent Selector Options

Use the agent selector to:

* Select the **Enterprise Agents** or **Cloud Agents** tab.
* Group agents by label or provider.
* Filter agents by IP support or country.

![Network Test Settings Agent Selector](https://1112912342-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-M4QARF6s57qxMrOHDTZ%2Fuploads%2Fgit-blob-7052cdcdae0d679865f89284be224d6d4223ed1a%2Fagent-selector.png?alt=media)

For a table view with customizable columns and custom filters, select the **Advanced** toggle at the upper right of the screen.

![Network Test Settings Advanced Agent Selector](https://1112912342-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-M4QARF6s57qxMrOHDTZ%2Fuploads%2Fgit-blob-c2ed055870c3495dc59c123f4646cecd383b1be5%2Fagent-selector-advanced.png?alt=media)

## Testing Jumbo Frames with Enterprise Agents

Use a fixed-size jumbo probe to validate that a path carries the larger packets your applications need. A standard-size probe can succeed while a jumbo packet is fragmented or dropped because an interface has a smaller maximum transmission unit (MTU). Enterprise Agent network tests support constructed IP packets up to 9,216 bytes.

{% hint style="warning" %}
CAF Agents and ThousandEyes Virtual Appliances (TEVAs) do not support jumbo-frame probing. Support is planned for a future Enterprise Agent release.
{% endhint %}

The value you enter is the data payload or TCP maximum segment size (MSS), not the total packet size. The agent adds the IP and transport headers. Choose a value that keeps the constructed packet within both the source interface MTU and the 9,216-byte product limit.

| Test            | Protocol | Setting                        | Manual range   |
| --------------- | -------- | ------------------------------ | -------------- |
| Agent-to-server | ICMP     | **Ping payload size**          | 1–9,188 bytes  |
| Agent-to-server | TCP      | **Ping payload size**          | 1–9,188 bytes  |
| Agent-to-agent  | UDP      | **Ping payload size**          | 30–9,188 bytes |
| Agent-to-agent  | TCP      | **Maximum segment size (MSS)** | 30–9,176 bytes |

The upper input limits are fixed and do not change with the protocol or IP version. For example, the agent-to-server control accepts a TCP payload of 9,188 bytes, but that value is too large for a 9,216-byte packet after the agent adds TCP and IP headers. The platform uses the manual value you enter; it does not lower that value to fit the packet limit. Account for the complete header size before you enter a value. These examples assume no IPv4 options, IPv6 extension headers, or TCP options:

| Protocol    | IP version | Calculation for a 9,216-byte packet                   | Maximum data size  |
| ----------- | ---------- | ----------------------------------------------------- | ------------------ |
| TCP         | IPv4       | 9,216 - 20-byte IP header - 20-byte TCP header        | 9,176-byte MSS     |
| TCP         | IPv6       | 9,216 - 40-byte IP header - 20-byte TCP header        | 9,156-byte MSS     |
| ICMP or UDP | IPv4       | 9,216 - 20-byte IP header - 8-byte ICMP or UDP header | 9,188-byte payload |
| ICMP or UDP | IPv6       | 9,216 - 40-byte IP header - 8-byte ICMP or UDP header | 9,168-byte payload |

**Auto** does not guarantee a jumbo-sized probe. For agent-to-server tests, **Auto** uses a 0-byte ICMP payload or a 1-byte TCP payload. For agent-to-agent tests, **Auto** uses path MTU discovery to select a UDP payload or TCP MSS that fits the path. Use **Manual** when you need to test a specific jumbo size.

### Configuring a Test with Jumbo Frames

1. Confirm that the Enterprise Agent host interface, operating system, network interface card, and connected switch port support the intended MTU. For an agent-to-agent test, verify both agents and the intervening path.
2. Create an agent-to-server or agent-to-agent test that uses a supported Enterprise Agent deployment on the path you want to validate. Do not use a CAF Agent or TEVA for jumbo-frame probing.
3. Expand **Network Settings (Optional)**. Set **Ping payload size** for an agent-to-server test or an agent-to-agent UDP test. Set **Maximum segment size (MSS)** for an agent-to-agent TCP test.
4. Select **Manual**, and enter a value that keeps the complete packet within the source interface MTU and 9,216-byte product limit.
5. Enable **Maximum Transmission Unit (MTU)** to measure the path MTU independently from the fixed-size probe.
6. Compare loss and path MTU in the **Overview** and **Path Visualization** views. In Path Visualization, hover over the source agent to check its interface **MTU**. A lower **MTU** on a downstream link identifies a smaller limit reported along the path. For more information, see [Investigating MTU Constraints in Path Visualization](https://docs.thousandeyes.com/product-documentation/internet-and-wan-monitoring/path-visualization#investigating-mtu-constraints).

Path MTU discovery depends on ICMP feedback. When a device drops an oversized packet without returning the required feedback, the test can show loss without identifying the limiting hop. Use the fixed-size probe as evidence that the path did not carry the packet, and use reported MTU values only where the path returned enough information. Together, these results give you a clear path to isolate the constraint and move remediation forward.
