The Node-to-Node Test enables you to set up a mesh of tests among multiple nodes to monitor network performance characteristics such as packet loss, latency, and jitter. This is typically used with Enterprise and Cloud nodes to help identify any issues with communication among your internal and cloud-based data centers. Enterprise and Cloud nodes can also perform bi-directional mesh tests against the public node types. (See the Supported Node Types section for more information.)
Node-to-Node Test Properties | |
|---|---|
| Name | A name used to identify this test. |
| Description | Optional additional information about the test |
| Monitor | The specific type of test that the nodes will run. Options include:
|
| Test Location | Not configurable - determined by the Nodes you target. |
| Location | The Product/Folder location of this test (read only) |
| Status | Determines whether this test is currently Active or Inactive |
Supported Node Types
Mesh-testing means that each targeted node performs connection tests (Ping or Traceroute) to multiple other nodes in the mesh. Enterprise and Cloud nodes will run tests on all other nodes in the mesh, regardless of type. Public nodes (Backbone, Last Mile, and Wireless) will run tests on Enterprise and Cloud nodes, but they do not perform tests on other public nodes, because tests between public nodes would not be relevant to your applications and infrastructure at all.
For example, if you set up mesh testing with a combination of Enterprise Nodes and Backbone nodes, then the Enterprise nodes will run tests against all other nodes in the mesh, however each Backbone node will only run tests against the Enterprise nodes, and not against the other Backbone nodes.
The table below depicts a Node-to-Node test configuration in which two of each node type has been selected. A cell with a checkmark indicates that the corresponding nodes will run tests to each other, and a blank cell indicates that the corresponding nodes will not.
| Node | Enterprise1 | Enterprise2 | Cloud1 | Cloud2 | Backbone1 | Backbone2 | LastMile1 | LastMile2 | Wireless1 | Wireless2 |
|---|---|---|---|---|---|---|---|---|---|---|
| Enterprise1 | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | |
| Enterprise2 | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | |
| Cloud1 | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | |
| Cloud2 | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | |
| Backbone1 | ✔ | ✔ | ✔ | ✔ | ||||||
| Backbone2 | ✔ | ✔ | ✔ | ✔ | ||||||
| LastMile1 | ✔ | ✔ | ✔ | ✔ | ||||||
| LastMile2 | ✔ | ✔ | ✔ | ✔ | ||||||
| Wireless1 | ✔ | ✔ | ✔ | ✔ | ||||||
| Wireless2 | ✔ | ✔ | ✔ | ✔ |
Supported Metrics
The Node-to-Node test implements Catchpoint's Ping and Traceroute monitors, so the metrics captured will be the same as those standard test types.
Scheduling Frequency Options
The Node-to-Node Ping test supports extra test-run frequency settings when targeting Enterprise Nodes. In addition to the standard options available with all tests (5min - 24hr), you can also select 1 minute or Continuous (200ms, 500ms, or 1000ms).
Your Node-to-Node test must be configured as follows to enable these higher frequencies:
- Select a Ping monitor (Ping ICMP, Ping UDP, or Ping TCP)
- Override the Targeting and Scheduling section (higher frequency settings cannot be configured in a parent container and inherited)
- Target only nodes of type Enterprise or Enterprise (pt)
For tests configured as specified above, you will see 1 minute and Continuous options in the Frequency dropdown. If you select Continuous, you will then see a Trigger Interval dropdown where you can specify 200ms, 500ms, or 1000ms frequency.
Node Distribution Options
When using a non-continuous Frequency option (1min - 24hr), you can also specify the Node Distribution. This determines whether the Nodes will all run their tests at the same time, or at random times during the testing interval.
- Random - the nodes run their tests at random times during the interval.
- Concurrent - the nodes all run their tests at roughly the same time.