ON THIS PAGE
Supported Plug-ins
This topic lists all the Plug-ins, both Native and RPM, supported by Test Agents.
Overview
A Plug-in is a software extension that enables Test Agents to run Measurements. Plug-ins are packaged as .nap files, which contain necessary Plug-in executables and dependencies. Each Plug-in supports a specific type of Measurements such as DNS, HTTP, TWAMP, IPTV, RPM, and so on. Each Plug-in corresponds to a Task in Routing Director, for example, the HTTP Plug-in is used for HTTP tasks and run HTTP measurements. When a Measurement starts, Test Agents downloads the packages of Plug-ins that you have specified on the Test or Monitor Tasks and use these Plug-ins to run Measurements. Measurements then report the metrics in the form of streams, which you can view in the Routing Director GUI. For more information, see Tests and Monitors Overview.
Navigation
To access and configure the supported Plug-ins:
-
For Test-related Plug-ins—Click Observability > Active Assurance > Measurement Designer > + Create blank Test.
-
For Monitor-related Plug-ins—Click Observability > Active Assurance > Measurement Designer > + Create blank Monitor.
-
For Packet Capture Plug-in—Click Observability > Active Assurance > Measurement Designer > + Create Packet Capture.
Client parameter configuration
When configuring a Measurement, you must specify a Client. A client refers to a Test Agent Interface, which is the endpoint used by the plug-in to initiate and perform active testing.
To configure clients:
Select Observability > Active Assurance > Measurement Designer > + Create blank Test/Monitor/Packet Capture > Task > Plug-in.
Click the Clients text box.
The Select interfaces page appears.
Select one or more Test Agents. You can filter Test Agent interfaces based on various criteria. For more information, see Filter Test Agent Interfaces.
Click OK.
A Test Agent client runs the Measurements using a Plug-in. Without a client you cannot run a Measurement.
Filter Test Agent Interfaces
On the Select Test Agent/Interfaces page (Observability > Active Assurance > Measurement Designer > + Create blank Test/Monitor/Packet Capture > Task > Plug-in > Clients), you can filter the Test Agent interfaces based on the following criteria:
-
Interface name or the Test Agent name, or both. Select or deselect specific Test Agents or interfaces based on your requirements.
IP address of a Test Agent. Select one of the following:
IPv4- Has IPv4: Displays interfaces associated with the IPv4 family.
- No IPv4: Displays interfaces not associated with the IPv4 family.
- Has IPv6: Displays interfaces associated with the IPv6 family.
- No IPv6: Displays interfaces not associated with the IPv6 family.
-
Deployment type of Test Agent. Select one of the following:
-
Application—Filter out the Test Agents deployed in a device as an application.
-
Device—Filter out the Test Agents associated with a device.
-
-
Connection types of Test Agent. Select one of the following:
-
Link—Indicates that the status is Up and there is an active connection for the interface.
-
No Link—Indicates that the status is Down and there is no active connection for the interface.
-
-
Connection statuses of Test Agent. Select one of the following:
-
Online—The Test Agent is connected to Routing Director.
-
Offline—The Test Agent is not connected to Routing Director.
Note:Interfaces supporting RPM plug-ins display (On device) at the end of their name, indicating Device Online status.
Interfaces supporting only native plug-ins do not display (On device), and their status reflects the Online/Offline state.
-
-
Interface types of the Test Agent. Select one of the following:
-
Normal—Network interfaces that are used for testing traffic.
-
Management—Network interfaces used by the Test Agents to connect to Routing Director.
-
Unknown—Network interfaces that the Test Agent is unable to identify or that have been removed.
-
In addition to filtering, you can do the following:
-
Enable the Display Device Names toggle button to display the hostnames of the routers that are associated with the Test Agents.
-
Enable the Hide unsupported toggle button to hide devices that are not supported by the plug-in you have selected.
-
Search for a specific interface or a Test Agent, enter one or more keywords in the search text box. You can search based on the name, description, IP and MAC address of the interfaces or the Test Agents. You can also search based on the device name, device model, and device MAC addresses if searching for a Test Agent associated with the device.
-
Remove the interface filters you have selected and reset the filters to the default mode by using the Reset filters button.
-
Hover over an interface name to view the details such as the Test Agent name, bind interface, bind family, and to check if the Test Agent is run on a device or not.
Plug-ins in Routing Director
Routing Director supports a variety of Plug-ins, each designed to perform specific tasks. You can view the list of available Plug-ins along with their details from Table 1.
| Tasks | Description |
|---|---|
|
DNS |
For information on the configuration parameters and metrics that you can configure for DNS, see DNS. |
|
HTTP |
For information on the configuration parameters and metrics that you can configure for HTTP, see HTTP. |
|
IPTV MPEG |
For information on the configuration parameters and metrics that you can configure for IPTV MPEG, see IPTV MPEG. |
|
Netflix Speedtest |
For information on the configuration parameters and metrics that you can configure for Netflix Speedtest, see Netflix Speedtest. |
|
OTT - HLS |
For information on the configuration parameters and metrics that you can configure for OTT-HLS, see OTT-HLS. |
|
Pathtrace |
For information on the configuration parameters and metrics that you can configure for Pathtrace, see Path Trace. |
|
Ping |
For information on the configuration parameters and metrics that you can configure for ping, see Ping. |
|
RPM CISCO TWAMP |
For information on the configuration parameters and metrics that you can configure for RPM CISCO TWAMP, see RPM Cisco TWAMP Reflector. |
|
RPM HTTP |
For information on the configuration parameters and metrics that you can configure for RPM HTTP, see RPM HTTP. |
|
RPM PING |
For information on the configuration parameters and metrics that you can configure for RPM PING, see RPM Ping. |
|
RPM RFC2544 CCC |
For information on the configuration parameters and metrics that you can configure for RPM RFC2544 CCC, see RPM RFC2544 CCC. |
|
RPM RFC2544 ETH |
For information on the configuration parameters and metrics that you can configure for RPM RFC2544 ETH, see RPM RFC2544 ETH. |
|
RPM RFC2544 INET |
For information on the configuration parameters and metrics that you can configure for RPM RFC2544 INET, see RPM RFC2544 INET. |
|
RPM RFC2544 REF CCC |
For information on the configuration parameters and metrics that you can configure for RPM RFC2544 REF CCC, see RPM RFC2544 REFCCC. |
|
RPM RFC2544 REF ETH |
For information on the configuration parameters and metrics that you can configure for RPM RFC2544 REF ETH, see RPM RFC2544 REF ETH. |
|
RPM RFC2544 REF INET |
For information on the parameters that you can configure for RPM RFC2544 CCC, see RPM RFC2544 REF INET. |
|
RPM TCP |
For information on the configuration parameters and metrics that you can configure for RPM TCP, see RPM TCP. |
|
RPM TWAMP |
For information on the configuration parameters and metrics that you can configure for RPM TWAMP, see RPM TWAMP. |
|
RPM UDP |
For information on the configuration parameters and metrics that you can configure for RPM UDP, see RPM UDP. |
|
RPM Y.1731 DM |
For information on the configuration parameters and metrics that you can configure for Y.1731 DM, see RPM Y.1731 DM. |
|
RPM Y.1731 SLM |
For information on the configuration parameters and metrics that you can configure for Y.1731 SLM, see RPM Y.1731 SLM. |
|
TCP |
For information on the configuration parameters and metrics that you can configure for TCP, see Path Trace. |
|
TWAMP Reflector |
For information on the configuration parameters and metrics that you can configure for TWAMP Reflector, see TWAMP Reflector. |
|
TWAMP/TWAMP Light |
For information on the configuration parameters and metrics that you can configure for TWAMP/TWAMP Light, see TWAMP/TWAMP Light. |
|
UDP |
For information on the configuration parameters and metrics that you can configure for UDP, see UDP. |
|
Packet Capture |
For information on the configuration parameters and metrics that you can configure for Packet Capture, see Packet Capture. |
DNS
The DNS measurement is used to test and monitor DNS servers. When the measurement starts, Test Agents send a request to resolve a lookup address and collect statistics on response times. DNS primarily uses User Datagram Protocol (UDP) on port number 53 to serve requests. DNS queries consist of a single UDP request from the client followed by a single UDP reply from the server. Running a DNS measurement provides insight into DNS response times from different locations. Since high DNS latency directly impacts services that rely on DNS resolution, such as web browsing, this Plug-in helps in diagnosing performance issues. The Plug-in supports both IPv4 and IPv6.
| Parameter | Description |
|---|---|
| GENERAL | |
| Clients* |
Select one or more Test Agent interfaces on which you want to run Measurements by using this Plug-in. A separate Measurement will be run on each interface you select. For more information, see Client Configuration for plug-ins. |
|
Lookup names* |
Specify the domain name to lookup. For example, example.net Lookup is the process of querying the server to translate a domain name into IP address. When you click the Lookup names text box, a Select Lookup name page appears. You can add a name in the Lookup text box. To add more than one Lookup names, click + Add Lookup. |
| Time between requests |
Specify the time that Test Agent should wait between successive DNS queries. Unit—seconds (s) Default value—10.00 s Range—0.01 s through 3600 s |
| DNS server |
Specify the IP address of the DNS server to query. If left empty, Test Agents use the default DNS server. Maximum—200 characters |
| DNS record type |
Select the DNS record type. A DNS record is a set of unstructured data stored in a DNS database. The database consists of information on a domain and its services. DNS has different resource records. Each record type has different functions in the resolution process.
By default, the record type is A. |
| THRESHOLDS FOR ERRORED SECONDS (ES) | |
| Timeout |
Specify the timeout value. If no response is received for the DNS request within the defined timeout period, an errored-second is raised unless the request lifetime expires. Unit—Milliseconds (ms) Default value—1000 ms Range—1ms through 30000 ms |
| ADVANCED | |
| Request lifetime |
Specify the timeout value. If no response is received for the DNS request within the defined timeout period, an errored-second is raised unless the request lifetime expires. Request lifetime value is the duration for which a DNS request is alive. It determines how long a request persists without getting terminated. Unit—Milliseconds (ms) Default value—5000 ms Range—1 ms through 30000 ms |
| Recursive requests |
Enable or disable the Recursive Requests toggle button. Recursive Request is the process where a DNS server queries other DNS servers until it resolves the lookup address. If you enable the Recursive Requests toggle button, the Recursion Desired flag is set on the DNS queries. By default, the toggle button is enabled. |
| Response code |
Select the DNS response code. You can select one of the following response codes:
The DNS response code can be any value from 0 to 9. The value indicates the outcome of a DNS query. For more information on DNS response codes and strings with descriptions, see IANA link. |
| Expected response |
Specify an expected response from the DNS server. If the actual response does not match the expected response, an errored-second is raised. In case, the response consists of more than one codes, at least one code must match the expected response. For more information on DNS response codes and strings with descriptions, see IANA link. |
| Metric | Description |
|---|---|
| Minimum response time |
Minimum response time of all the requests in the result interval. Response time is the time elapsed from when the DNS request was sent until a response was received. The response time is calculated in milliseconds. |
| Average response time |
Average response time of all the requests in the result interval. Response time is the time elapsed from when the DNS request was sent until a response was received. The response time is calculated in milliseconds. |
| Maximum response time |
Maximum response time of all the requests in the result interval. Response time is the time elapsed from when the DNS request was sent until a response was received. The response time is calculated in milliseconds. |
| ES timeout |
ES timeout is the errored-seconds raised when Test Agent considers a DNS request to be timed-out. The ES timeout is calculated in milliseconds. |
| ES lifetime |
ES lifetime is the errored-seconds raised when Test Agent fails the DNS request as there is no response received within the specified Request lifetime. The ES lifetime is calculated in milliseconds. |
| ES response |
ES response is the errored-seconds raised when the DNS Response code differs from the expected response code or when the response differs from the expected response. |
|
ES |
ES is the number of seconds during which error second thresholds are violated. It is the total number of error-seconds raised during result interval. The ES is calculated in milliseconds. |
HTTP
The HTTP measurement is used to test or monitor HTTP servers. When an HTTP measurement starts, Test Agents send an HTTP GET request to the specified URL and retrieve the response. The measurement does not render HTML pages or request additional resources such as images, CSS files, and so on. Instead, it focuses on measuring response times and connection efficiency. The measured parameters include TCP connect time, time until first byte received, time until last byte received, and download speed.
Running an HTTP measurement helps validate the responsiveness of web servers and quality pf network path between the servers and Test Agents. This Plug-in is applicable for both IPv4 and IPv6.
| Parameter | Description |
|---|---|
| GENERAL | |
| Clients* |
Select one or more Test Agent interfaces on which you want to run measurements by using this Plug-in. A separate measurement will be run on each interface you select. For more information, see Client Configuration for plug-ins. |
| URLs* |
Specify the URL for the HTTP request. Maximum—200 characters |
| Time between requests |
Specify the time taken between successive HTTP requests initiated by Test Agent. Unit—Seconds (s) Default value—10.00 s Range—0.01 s through 3600 s |
| THRESHOLDS FOR ERRORED SECONDS (ES) | |
| Timeout |
Specify the timeout value. If no response is received to the HTTP request within the defined timeout period, an errored second for timeout is raised. Unit—Milliseconds (ms) Default value—1000 ms Range—1 ms through 30000 ms |
| Response content |
Specify the regular expression (case-insensitive) against which the HTTP response content is validated. Maximum—50 characters |
| ADVANCED | |
| Request lifetime |
Specify the maximum time to wait for a response before the HTTP request is canceled. If this time expires without a response, an errored second for lifetime expiry is raised. Unit—Milliseconds (ms) Default value—5000 ms Range—1 ms through 30000 ms |
| HTTP response code |
Specify the HTTP response code for Test Agent. If the HTTP response code does not match the specified response code, an errored-second is raised. For more information on HTTP response codes, see RFC 9110. |
| Proxy server |
Specify the IP address of the HTTP proxy server optionally. |
| Proxy port |
Specify the HTTP proxy port when using HTTP proxy server. Default value—8080 Range—1 through 65535 |
| Proxy authentication |
Select the authentication method that the Test Agent uses when connecting to a proxy server. Select one of the following authentication method:
Proxy authenticates the incoming request from a Test Agent. This ensures that only the authorized users have access to the internet. |
| Proxy username |
Specify the username for authorized access to a proxy. |
| Proxy password |
Specify the password for authorized access to a proxy server. |
| Metric | Description |
|---|---|
|
Connect time |
Connect time is the time taken to set up a TCP connection between Test Agent and the Web server by using a TCP handshake. The connect time is calculated in milliseconds. |
|
First byte received |
First byte received indicates the total time taken by Test Agent to receive the first byte of response packet from the Web server. The first byte received time is calculated in milliseconds. |
| Minimum response time |
Minimum response time is the duration when the request was sent until the full response is received. TCP connection setup time is included in the average response duration. The response time is calculated in milliseconds. |
| Average response time |
Average response time is the average duration when the request was sent until the full response is received. TCP connection setup time is included in the average response duration. The response time is calculated in milliseconds. |
| Maximum response time |
Maximum response time is the maximum duration when the request was sent until the full response is received. TCP connection setup time is included in the average response duration. The response time is calculated in milliseconds. |
|
Size |
Size indicates the total size of the data transferred from a remote endpoint to Test agent in response to an HTTP request. The size also includes the header size. The size is calculated kilobytes. |
|
Rate |
Rate is the download rate at which the response is received from first byte to last. The rate is displayed in Megabits Per Second. |
| ES timeout |
ES timeout is the number of errored-seconds raised because no HTTP response was received before the timeout period expires. The ES timeout is calculated in milliseconds. |
| ES response |
ES response is the errored-seconds raised when the response code differs from the expected response code or when the response content differs from the expected response. |
|
ES |
ES is the number of seconds during which error-second thresholds were violated. It is the total number of errored-seconds raised during the result interval. The ES is calculated in milliseconds. |
IPTV MPEG
The IPTV MPEG measurement is used to monitor the IPTV channel quality. When the measurement starts, Test Agents join the channels by sending IGMP join messages and receive the MPEG streams. Test Agents then continuously evaluate the streams to measure packet loss, MPEG loss, PCR jitter, bitrate, and continuity count errors. The results provide a clear view of IPTV quality at Test Agent endpoints and highlight potential impairments that affect user experience.
| Parameter | Description |
|---|---|
| GENERAL | |
| Clients* |
Select one or more Test Agent interfaces on which you want to run measurements by using this Plug-in. A separate measurement will be run on each interface you select. For more information, see Client Configuration for plug-ins. |
|
IPTV Channels* |
Specify one or more IPTV channels to monitor from the preset IPTV channel list. When you click IPTV Channels, the Select Channel page appears where you can enter channels. To add more than one channels, click + Add channel and specify the following:
|
|
THRESHOLDS FOR ERRORED SECONDS (ES) |
|
|
MPEG loss (CC errors/s) |
Specify the maximum allowed MPEG packet loss (Continuity Count errors) per second. An errored-second is raised if the MPEG loss exceeds this threshold. Continuity Counter (CC) error indicates an issue with the packet sequence in an MPEG transport stream. |
|
PAT/PMT delay variation (ms) |
Specify the maximum tolerated jitter (delay variation) of the received MPEG stream. An errored-second is triggered if the PCR jitter or RTP jitter exceeds this threshold. PCR provides timestamps to maintain synchronization of audio and video, RTP provides end-to-end delivery of real-time data over IP networks. |
|
PAT/PMT interval (s) |
Specify the maximum allowable time interval between Program Allocation Table (PAT)/ Program Map Table (PMT) transmissions. PAT has information on all the available programs in a transport stream. PAT maps all the programs numbers to PMT packet identifiers. PMT has information on the streams and lists the PIDs of all the streams associated with a program. |
|
PID interval (s) |
Specify the maximum allowable time interval between audio or video Packet Identifiers (PIDs) as specified by Program Map Table (PMT). PID is a 13-bit field in the header of a transport stream used to identify different data streams, such as video, audio, subtitles, within a transport stream. |
| Metrics | Description |
|---|---|
|
Rate |
Rate indicates the bit rate of the MPEG program stream. |
|
Transport rate |
Transport rate indicates the bit rate of the MPEG transport stream (MPEG-TS). It includes the overhead from the header of the Transport Stream packet. |
|
MPEG Loss |
MPEG loss indicates the MPEG packet loss during a transmission. The loss is calculated from the continuity count (CC) errors in the MPEG stream. |
|
PCR jitter |
PCR jitter (delay variation) indicates the received MPEG stream. It is calculated from the timestamps in the Program Clock Reference (PCR) field transmitted in the adaption layer of the MPEG transport stream. |
|
PAT error |
PAT error occurs if a Program Allocation Table (PAT) is not received on a multicast group within the configured PAT/PMT interval. |
|
PMT errors |
PMT error occurs if a Program Map Table (PMT) is not received on a multicast group within the configured PAT/PMT interval. |
|
PID errors |
PID error occurs if no frame is received within the specified PID interval threshold for every second that elapses. |
|
RTP errors |
RTP Errors indicates lost packets based on Real-Time protocol (RTP) header. Whether an MPEG stream contains RTP headers depends on the configuration of the encoder at the head-end. |
|
RTP misorders |
RTP misorders indicates the number of misorder packets based on Real-Time protocol (RTP) header. A packet is counted as misordered if it is delivered after a packet with a higher sequence number. Whether an MPEG stream contains RTP headers depends on the configuration of the encoder at the head-end. |
|
RTP jitter |
The jitter (delay variation) of the received MPEG stream. Calculated using the timestamps from the Real Time protocol (RTP) if the MPEG stream contains RTP headers. Whether an MPEG stream contains RTP headers depends on the configuration of the encoder at the head-end. |
|
ES |
ES is the number of seconds during which errors occurred in a specific duration of time. ES is an aggregate of all specific ES metrics. |
|
ES MPEG loss |
ES MPEG loss is the errored-seconds raised due to MPEG packet loss (CC errors). It is raised when the MPEG loss exceeds the configured MPEG loss threshold. |
|
ES Jitter |
ES jitter is the number of errored-seconds raised when the PCR jitter or RTP jitter exceeds the defined jitter threshold. |
|
ES invalid stream |
ES invalid stream is an aggregate of PAT, PMT, and PID errors. If any of these types of errors are experienced in a second, an errored-second is raised. |
Netflix Speedtest
The Netflix Speedtest measurement measures the performance of a Netflix speed test transaction. When the measurement runs, the Routing Director instructs Test Agents to download Netflix test segments over HTTPS. The test results provide information on available bandwidth, latency, and any threshold violations. This Plug-in helps determine whether the network can optimally support Netflix streaming traffic.
| Parameter | Description |
|---|---|
| GENERAL | |
| Clients* |
Select one or more Test Agent interfaces on which you want to run measurements by using this Plug-in. A separate measurement will be run on each interface you select. For more information, see Client Configuration for plug-ins. |
|
Measurement Cycle period |
Specify the time interval between successive measurement cycles. On each measurement cycle, the Test Agent downloads Netflix test segments over HTTPS from one or several OCAs (Open Connect Appliances) operated by Netflix. OCA is a server appliance to cache and deliver content locally to subscribers, reducing the load on Netflix's central servers. Unit—Minutes (min) Default value—15 min Range—1 min through 60 min |
|
Upload or Download |
Select the type of bandwidth to measure the rate of the data transfer. Upload data transfer is calculated from the Test Agent to OCAs, while download is calculated from the OCAs to the Test Agent. |
| ADVANCED | |
|
Minimum Duration (s) |
Specify the minimum duration of speedtest that must be run before checking for throughput stabilization. Unit—Seconds (s) Default value—2 s Range—1 s through 3600 s |
|
Maximum Duration (s) |
Specify the maximum duration of speedtest that must be run to check for throughput stabilization. Unit—Seconds (s) Default value—30 s Range—5 s through 3600 s |
|
Minimum Concurrent OCA connections |
Specify the minimum number of concurrent Open Connect Appliance (OCA) connections used for bandwidth testing. Default value—3. Range—1 through 5. |
|
Maximum Concurrent OCA connections |
Specify the maximum number of concurrent Open Connect Appliance (OCA) connections used for bandwidth testing. Default value—5 Range—1 through 5 |
|
THRESHOLDS FOR ERRORED SECONDS (ES) |
|
|
Minimum bandwidth (Mbit/s) |
Specify the minimum expected bandwidth during the speedtest. An errored-second is raised if the bandwidth drops below the defined value. |
|
Maximum latency (ms) |
Specify the minimum expected bandwidth during the speedtest. An errored-second is raised if the bandwidth drops below the defined value. |
| Metrics | Description |
|---|---|
|
Bandwidth speed |
Bandwidth speed is the speed of data transmission to the Netflix servers or from the Netflix servers. The Bandwidth speed is displayed in Megabits Per Second. |
| End to End Latency |
End-to-end latency indicates the latency occurred during the transfer of data from the Test Agent to the Netflix server or vice versa. The End to End Latency is displayed in milliseconds. |
| ES bandwidth |
ES bandwidth indicates the number of errored-seconds raised if the bandwidth drops below the defined value. |
| ES latency |
ES latency indicates the number of errored-seconds raised if the latency exceeds the defined value. |
| ES |
ES is the number of seconds during which errors occurred in a specific duration of time. ES is an aggregate of all specific ES metrics. The ES is displayed in seconds. |
| ES rate |
ES Rate is the number of errored-seconds occurred when the rate at which the UDP packet reception drops below the defined value. |
OTT-HLS
The OTT-HLS measurement is used to monitor Over-the-Top (OTT) streaming services. When the measurement runs, Test Agent parses the manifest file of the media stream and begins downloading video segments. The adaptive algorithm selects the highest possible bitrate based on the current network conditions, minimizing buffering and allowing smooth playback. This Plug-in helps in validating video quality across distributed locations.
| Parameter | Description |
|---|---|
| GENERAL | |
| Clients* |
Select one or more Test Agent interfaces on which you want to run measurements by using this Plug-in. A separate measurement will be run on each interface you select. A separate measurement will be run on each interface you select. For more information, see Client Configuration for plug-ins. |
|
URLs* |
Specify the URL of the video stream to which you send the connection requests. The URL can either be a playlist linking to other playlists for the different variants, or a playlist containing the segments. The file extension is .m3u or .m3u8. When you click URLs, the Select URL page appears where you can enter URLs. To add more than one URLs, click + Add URL and specify the following:
|
|
Buffer size (s) |
Specify the target duration of the buffered data. If the duration of the buffer data drops below the defined value, new segments are downloaded. Unit—Seconds (ms) Default value—60 s Minimum—1 s |
|
Initial Buffering (s) |
Specify the duration of the initial buffered data required before the playback begins. Unit—Seconds (ms) Default value—10 s Minimum—1 s |
|
Loop |
Enable or disable the Loop button. If enabled, the playback loops when the stream reaches the end of the playlist. If disabled, the playback stops, and errored-seconds are raised. By default, the toggle button is enabled. |
|
THRESHOLDS FOR ERRORED SECONDS (ES) |
|
|
Minimum playback rate (Mbit/s) |
Specify the minimum expected playback rate of the video stream. An errored second is triggered if its value drops below this threshold. Unit—Megabit per second (Mbit/s) Minimum value—0 Mbit/s |
|
Minimum download rate (Mbit/s) |
Specify the minimum expected playback rate of the video stream. An errored-second is raised if the download rate drops below the defined value. Unit—Megabit per second (Mbit/s) Minimum value—0 Mbit/s |
|
Minimum selected rate (Mbit/s) |
Specify the minimum expected download rate for the segments. An errored-second is raised if the selected rate drops below the defined value. Variants are the versions of media streams that is encoded at a specific rate. They enable adaptive streaming where the Test Agents can select variants to provide the best experience. Unit—Megabit per second (Mbit/s) Minimum value—0 Mbit/s |
|
Minimum buffer size (s) |
Specify the minimum expected duration of the data segment buffered in the Test Agent. An errored-second is triggered if its value drops below the defined value. Unit—Megabit per second (Mbit/s) Minimum value—0 Mbit/s |
| Metrics | Description |
|---|---|
| Playback rate |
Playback rate indicates the actual data rate of the video stream. The rate is displayed in Megabits Per Second. |
| Download rate |
Download rate indicates the download rate of the segments. When the amount of buffered data drops below the defined buffer size, the download begins. The rate is displayed in Megabits Per Second. |
| Selected rate |
Selected rate indicates the data rate of the selected variant in the manifest file. The rate is displayed in Megabits Per Second. |
| Buffer length |
Buffer length is the duration of the initial buffered data at a given time. When the duration of the buffered data drops below the defined value, new segments are downloaded. |
| ES |
ES is the number of seconds during which errors occurred in a specific duration of time. ES is an aggregate of all specific ES metrics. |
| ES playback rate |
ES playback rate is the number of errored-seconds raised when the playback rate drops below the defined playback rate value. |
| ES selected rate |
ES selected rate is the number of errored-seconds raised when selected rate drops below the defined value. |
| ES download rate |
ES download rate is the number of errored-seconds raised when the download rate drops below the defined value. |
| ES buffer |
ES buffer is the number of errored-seconds raised when buffer length of the video stream drops below the defined value. |
| ES buffering | ES buffer is the number of errored-seconds raised when buffer length of the video stream drops below the defined value. |
Packet Capture
Packet capture helps you to analyze network traffic and troubleshoot network problems. It captures real-time data packets traveling over the network for monitoring purposes. When packet capturing is enabled on a Test Agent interface, the entire packet including the Layer 2 header is captured and stored as a file in .pcap format. You can specify the maximum size (up to 65535 bytes) for the packet that can be captured.
Once you run a Packet Capture, you can access the results file from the PCAP Results tab (Observability > Active Assurance > Measurement Explorer > Packet-Capture-Name). For more information, see About the Packet Capture Page.
Packets are captured as binary data without modification. You can analyse the packet information offline with a packet analyzer such as Wireshark or tcpdump. This allows you to analyze both IPv4 and IPv6 traffic.
| Parameter | Description |
|---|---|
|
Capture interface |
Select a Test Agent interface on which to run Packet Capture measurements. For more information, see Client Configuration for Plug-ins. |
|
Capture Filter |
Specify a filter to capture only the packets that match the criteria. The filter uses the standard tcpdump or Wireshark filter syntax. The packet filter can filter out packets based on different criteria such as logical interface, protocol, source IP address prefix, source port, destination IP address prefix, and destination port. |
|
Frame Size |
Specify the maximum number of bytes to capture from each packet. Unit—Bytes Default value—1518 Range—64 through 65535 |
|
Number of frames |
Specify the number of packets to capture before stopping the capture. The total capture size is limited to 15 MB. The capture automatically stops when either the packet count limit or the size limit is reached, whichever comes first. Default value—100 Minimum value—1 |
|
Enable promiscuous mode |
Enable promiscuous mode on the interface to capture all traffic on the interface, including packets not destined for that interface. |
|
Maximum duration |
Specify the time limit for the Packet Capture. The Packet Capture stops when either the maximum duration is reached or the configured number of frames is captured, whichever comes first. Maximum value—86400s (24h) |
Path Trace
The Path Trace measurement evaluates network performance by sending ICMP/UDP echo packets with increasing Time to Live (TTL). This identifies actual routes of packets during a transmission from source to destination using the Paris Trace route algorithm. Path Trace enables you to validate traffic paths and evaluate network KPIs such as round-trip time, packet loss, hop count, and path changes. This measurement is applicable for both IPv4 and IPv6.
| Parameter | Description |
|---|---|
|
GENERAL |
|
|
Clients |
Select one or more Test Agent interfaces on which you want to run measurements by using this Plug-in. A separate measurement will be run on each interface you select. For more information, see Client Configuration for Plug-ins. |
|
Hosts |
Specify the target hostname or IP address. When you click the text box, the Select Host page appears where you can enter hostnames. To add more than one Hosts, click + Add Host and specify the following:
|
|
Frame size (Bytes) |
Specify the size of Layer 2 Ethernet frame for the data flow. Default—82 Range—64 bytes through 9018 bytes |
|
Rate (Mbit/s) |
Specify the number of packets per hop that Test Agent will send each second. Default—0.1 Mbit/s Unit—Megabit per second (Mbit/s) Range—0.01 Mbit/s through 50.0 Mbit/s |
|
Apply thresholds for all hops |
Enable this toggle button to apply Errored Second (ES) thresholds for all intermediate hops. By default, it is disabled, and the thresholds are only applied to the destination hop. |
|
Lifetime |
Specify the maximum lifetime of a test packet before it is considered lost. Default—1000 ms Unit—Milliseconds (ms) Range—1000 ms through 3000 ms |
|
THRESHOLDS FOR ERRORED SECONDS (ES) |
|
|
Expected DSCP |
Specify the expected Differentiated Services Code Point (DSCP) that must be in the frame when received by Test Agent. If the received DSCP value does not match the configured value, an errored-second is raised. DSCP is a six-bit binary value in the DS field of the IP header. DSCP value facilitates QoS for traffic management through the Best Effort, Assured Forwarding, Class Selector, and the Expedited Forwarding categories. See RFC 2474 for more information. Range—0 through 63 |
|
Loss (%) |
Specify the threshold for loss. If the loss percentage exceeds the configured value, an errored-second is raised. Default—0 Unit—Percentage (%) Range—0.0% through 100.0% |
| Delay |
Specify the threshold value for the maximum delay measured between Test Agent and a reflecting hop. If maximum delay exceeds the defined value, an errored-second is raised. Unit—Milliseconds (ms) Default—1000 ms Range—0.001 ms through 1000 ms |
| DV (Delay variance) |
Specify the threshold value for the maximum delay variance (jitter) measured between Test Agent and the reflecting hop. If delay variance exceeds the defined value, an errored-second is raised. Unit—Milliseconds (ms) Range—0.01 ms through 1000ms |
|
THRESHOLDS FOR SEVERELY ERRORED SECONDS (ES) |
|
|
Loss (%) |
Specify the threshold for loss. If the loss percentage exceeds the configured value, an errored-second is raised. Default—0 Unit—Percentage (%) Range—0.0% through 100.0% |
| Delay |
Specify the threshold value for the maximum delay measured between Test Agent and a reflecting hop. If maximum delay exceeds the defined value, an errored-second is raised. Unit—Milliseconds (ms) Default—1000 ms Range—0.001 ms through 1000 ms |
| DV (Delay variance) |
Specify the threshold value for the maximum delay variance (jitter) measured between Test Agent and the reflecting hop. If delay variance exceeds the defined value, an errored-second is raised. Unit—Milliseconds (ms) Range—0.01 ms through 1000ms |
|
ADVANCED |
|
|
Protocol |
Select one of the following network protocols to be used for test traffic. The available options are: ICMP—Suitable for connectivity checks and round-trip time measurement. UDP—Suitable for testing real-time traffic. Default—ICMP |
|
UDP port |
Specify the destination UDP port. Only applicable when UDP is selected under Protocol. Default—7 Range—0 through 65535 |
|
DSCP/IPP |
Specify the Differentiated Services Code Point (DSCP) or the IP Precedence (IPP) value that is used in the sent IP packet headers. DSCP is a six-bit binary value in the DS field of the IP header. DSCP value facilitates QoS for traffic management through the Best Effort, Assured Forwarding, Class Selector, and the Expedited Forwarding categories. See RFC 2474 for more information. Range—0 through 63 |
|
Stable period (s) |
Specify the number of seconds packet trains must follow the same
route before assuming a stable state. You must consider the Rate
value when configuring this. Use a period long enough to send two
packets per TTL plus the packet lifetime. Unit—Seconds (s) Default—60s Range—3 s through 60 s |
|
Maximum ttl |
Specify the maximum value of the Time-To-Live parameter. The value will also limit the maximum number of hops detected. Default—30 Range—2 through 64 |
|
Sending socket buffer (Bytes) |
Specify the value for the send socket buffer size. Range—1000 through 1000000 |
|
Receive socket buffer (Bytes) |
Specify the value for the receive socket buffer size. Range—1000 through 1000000 |
| Metrics | Description |
|---|---|
| Packets received |
Total number of packets received by Test Agent from the reflecting hop. |
| Lost packets |
Total number of lost packets for which Test Agent did not get a response from the reflecting hop. |
| Minimum RTT |
Minimum round-trip time in the result interval. Round-trip time indicates the duration from when the test packet is sent from Test Agent until the packet is reflected and received again on the Test Agent |
| Average RTT |
Average round-trip time in the result interval. Round-trip time indicates the duration from when the test packet is sent from Test Agent until the packet is reflected and received again on Test Agent. |
| Maximum RTT |
Maximum round-trip time in the result interval. Round-trip time indicates the duration from when the test packet is sent from Test Agent until the packet is reflected and received again on Test Agent. |
| RTT DV | Average round-trip delay variance in the result interval. Round-trip delay variance is the difference in round-trip time between the packets with the longest and the shortest round-trip time. |
| Loss |
Loss percentage indicates the percentage of packets sent by Test Agent that did not receive a response from the reflecting hop. |
| ES |
ES is the number of seconds during which error-second thresholds were violated. It is the total number of errored-seconds raised. |
| ES loss |
ES loss is the number of errored-seconds raised when the measured loss is greater than the configured loss threshold. |
| ES delay |
ES delay is the number of errored-seconds raised when Test Agent measures a delay greater than the configured delay threshold. |
| ES DV |
ES delay variance is the number of errored-seconds raised when the measured delay variance is greater than the configured DV threshold. |
| ES DSCP |
ES DSCP indicates number of errored-seconds raised when the received DSCP value does not match the expected value. |
| ES SES |
Severely errored second (SES) indicates the number of seconds that a SES threshold has been violated. |
| UAS |
Unavailable Seconds (UAS) indicates the total number of seconds during which the monitored service is considered unavailable. The service refers to the connectivity check performed by Path Trace to evaluate traffic paths and network KPIs. UAS is recorded when the device does not respond to the configured probe type (for example, ICMP or UDP echo) for an entire second. |
Ping
The Ping measurement checks connectivity to a remote host. When the measurement starts, Test Agent sends a single ICMP or UDP request to the host and waits for a reply. Based on this exchange, the measurement reports delay, jitter, and packet loss of the connection. The Plug-in is useful to validate basic connectivity and network stability. The Plug-in supports both IPv4 and IPv6.
| Parameter | Description |
|---|---|
| GENERAL | |
| Clients* |
Select one or more Test Agent interfaces on which you want to run measurements by using this Plug-in. A separate measurement will be run on each interface you select. For more information, see Client Configuration for Plug-ins. |
| Hosts* |
Specify the hostname or the destination IP. A host is the remote endpoint to which the Test Agent sends the request. When you click the Host text box, the Select Host page appears where you can enter hostnames. To add more than one hosts, click + Add Host and specify the following:
|
| Time between requests |
Specify the time taken between successive ping requests initiated by Test Agent. Unit—Seconds (s) Default value—10.00 s Range—0.01 s to 3600 s |
| THRESHOLDS FOR ERRORED SECONDS (ES) | |
| Delay |
Specify the maximum threshold for the delay. If the round-trip time for a Ping response exceeds this value, an errored-second is raised. Unit—Milliseconds (ms) Default value—1000 ms Range—1 ms through 30000 ms |
| DV (Delay variance) |
Specify the maximum threshold value for jitter or delay variance (DV). DV is the difference between the maximum and minimum delay experienced in a one second metrics interval. If the DV exceeds the defined value, an errored-second is raised. Delay variation (DV) occurs when different packets take different amount of time to travel from a Test Agent to a remote endpoint. Packets are sent at regular interval of time and if variation is experienced in consecutive packets, the Test Agent generates an errored-second event. Unit—Milliseconds (ms) Default value—500 ms Range—0 ms through 10000 ms |
| ADVANCED | |
| UDP echo |
Enable UDP Echo protocol instead of ICMP Ping. By default, the toggle button is disabled. |
| Payload |
Specify the size of the ping payload. Payload is the actual data in a request packet. Unit—Bytes Default value—56 bytes Range—0 byte through 65000 bytes |
| TTL (Time to Live) |
Specify the number of times the packets hop before a device discards the packet. Time to live (TTL) value indicates lifespan of a request packet. TTL prevents infinite loop in a network when the packet fails to reach the destination. For example, if you have entered the TTL value as 64, every time the packet passes a device, the value is reduced by one until the packet reaches the remote server. If the entered value reaches zero before reaching the remote endpoint, the packet is discarded. Default value—64 Range—1 through 255 |
| Request Lifetime |
Specify the request lifetime value. Request lifetime value is the maximum duration for which a ping request is alive. It determines how long a request persists before it is counted as lost. Unit—Milliseconds (ms) Default value—2000 ms Range—1 ms through 30000 ms |
| DSCP/IPP |
Specify the Differentiated Services Code Point (DSCP) or the IP Precedence (IPP) value that is used in the IP packet headers. The IPP is the three-bit binary values (Precedence) in the ToS field of the IP header. An IPP value can be in the 0-7 range. IPP value informs the router about the priority of the packet. The higher the IPP value, the more the priority of the packet. See RFC 791 for more information. DSCP is a six-bit binary value in the DS field of the IP header. DSCP value facilitates QoS for traffic management through the Best Effort, Assured Forwarding, Class Selector, and the Expedited Forwarding categories. See RFC 2474 for more information. Default value—0 Range—0 through 255 |
| Metrics | Description |
|---|---|
|
Successful ping counts |
Number of ICMP or UDP echo request which has received a response during the result interval. The higher ping counts denote to a more reliable the network connection. |
|
Minimum round-trip delay |
Minimum round-trip delay of all the requests in the result interval. Round-trip measures the duration from the time Test Agent sends a request until it receives a response from the device. The delay is calculated in milliseconds. |
|
Maximum round-trip delay |
Maximum round-trip delay of all the requests in the result interval. Round-trip measures the duration from the time Test Agent sends a request until it receives a response from the remote endpoint. The delay is calculated in milliseconds. |
|
Average round-trip delay |
Average round-trip delay of all the requests in the result interval. Round-trip measures the duration from the time Test Agent sends a request until it receives a response from the remote endpoint. The delay is calculated in milliseconds. |
|
Average round-trip DV |
Average round-trip delay variance in the result interval. Round-trip delay variance is the difference in time between the request with longest round-trip time and the shortest round-trip time. The delay variance is calculated in milliseconds. |
|
Lost |
Indicates the number of ping request packets sent by Test Agent that did not receive a response before the configured lifetime. |
|
Loss |
Indicates the number of ping request packets sent by Test Agent that did not receive a response before the configured lifetime. |
|
ES |
ES is the number of seconds during which error-second thresholds were violated. It is the total number of errored-seconds raised during the result interval. The ES is calculated in milliseconds. |
|
ES loss |
ES loss is the number of errored-seconds during the result interval where a request or more did not receive a response. The ES loss is calculated in milliseconds. |
|
ES delay |
ES delay is the number of errored-seconds raised when Test Agents experience round-trip delay greater than the configured timeout. The ES delay is calculated in milliseconds. |
| ES response |
ES response is the number errored-seconds raised because Test Agent failed to resolve the destination hostname or because the response payload does not match what was sent. |
| ES delay variance (DV) |
ES delay variance is the number of errored-seconds raised because Test Agent measures a variance in delay greater than the configured delay variation threshold. The ES delay variance is calculated in milliseconds. |
RPM Cisco TWAMP Reflector
The RPM Cisco TWAMP Reflector measurement measures network performance specifically for Cisco devices. It uses the Two-Way Active Measurement Protocol (TWAMP) to collect metrics such as round-trip delay, jitter, and packet loss between Test Agents acting as senders and Cisco devices acting as responders.
It is recommended to configure this measurement using the API because configuration through the Routing Director GUI is currently available only as a Beta feature.
| Parameter | Description |
|---|---|
| GENERAL | |
|
Reflectors* |
Select one or more Test Agent interfaces on which you want to run measurements by using this Plug-in. A separate measurement will be run on each interface you select. For more information, see Client Configuration for Plug-ins. |
|
Ports* |
Specify the Test session port value. When you click the text box, the Select Test Session Port Value page appears where you can add port values. On this page:
|
|
ADVANCED |
|
|
Collection interval* |
Specify the collection interval. Collection interval is the frequency at which the results are collected from the device. Collection interval must be larger than the value specified in the Timeout period field. Unit—Seconds (s) Default value—30s Range—30s through 300s |
|
Session Timeout |
Specify the duration of time after which an idle session is automatically ended. Unit—Seconds (s) Default value—35s Range— 10s through 300s |
|
Timeout period |
Specify the inactivity timeout period for the test session. The session terminates if no activity happens within the specified time. Unit—Seconds (s) Range—1s through 604800s |
|
Inactivity-timer value |
Specify the inactivity timeout period for the TWAMP server. The session terminates if no activity happens within the specified time. Unit—Seconds (s) Range—1s through 6000s |
|
Server Test Session Port IP |
Specify the IPv4 or IPv6 address of the TWAMP reflector used for test sessions. Maximum—255 characters |
|
Control Session Port |
Specify the port used for the control session. Specify 0 for TWAMP Light and specify any value starting from 862 through 65535 for managed TWAMP. Default value—0 Range—0 through 65535 |
|
Session Duration |
Specify the total duration the test session runs. Unit—Seconds (s) Default value—Unlimited (the session continues until the session is manually stopped.) Range— 60s through 86400s |
|
VRF |
Specify the VRF (Virtual Routing and Forwarding) instance to use for the test session. Default value—Any Maximum—255 characters |
|
Session ID |
Specify the session ID used for the TWAMP light test session. Default value—1 Range—1 through 65535 |
| Stream Metric | Description |
|---|---|
|
Keep alive count |
Keep alive count indicates the number of active Cisco TWAMP Plug-in measurement updates in real time. |
RPM HTTP
The RPM HTTP measurement checks connectivity and verifies the availability of a the remote device. It sends HTTP request to cofirm that the devices respond as expected. Use this measurement if you are using ACX, PTX, or MX devices to verify HTTP-based connectivity.
| Parameter | Description |
|---|---|
| GENERAL | |
| Clients* |
Select one or more Test Agent interfaces on which you want to run measurements by using this Plug-in. A separate measurement will be run on each interface you select. For more information, see Client Configuration for Plug-ins. |
| URLs* |
Specify the URL or host towards which the router sends HTTP Get requests. Maximum—255 characters |
| Time between requests |
Specify the time taken between successive HTTP requests initiated by the router. Unit—Seconds (s) Default value—10 s Range—1 s to 255 s |
|
ADVANCED |
|
| Collection Interval |
Specify the collection interval. Collection interval is the frequency at which the results are collected from the device. Collection interval must be larger than the specified Time between requests. Unit—Seconds (s) Default value—15 s Range—5 s through 300 s |
| Device response timeout |
Specify the device response timeout value. Device response timeout determines the time to wait for a response from the router. If the specified time exceeds, the connection to the device is considered to be failed. Device response timeout must be larger than the specified Collection Interval. Unit—Seconds (s) Default value—200 s Range—30 s through 300 s |
| Routing instance |
Specify the name of routing instance on the router used by the probes. |
|
TTL |
Specify the number of times the packets hop before a device discards the packet. Time to live (TTL) value indicates lifespan of a request packet. TTL prevents infinite loop in a network when the packet fails to reach the destination. Default value—64. Range—1 through 254. |
|
Metadata get |
Enable Metadata get for the Test to perform HTTP Get requests for metadata to a target URL. By default, the toggle button is disabled. |
|
IPv6 local link |
Specify the router link-local logical interface name for the egress interface to be used. This applies only for Test sessions with IPv6 address as the target address. Maximum—64 characters |
| Hardware timestamp |
Specify the router link-local logical interface name for the egress interface to be used. This applies only for Test sessions with IPv6 address as the target address. By default, the toggle button is disabled. |
| Metric | Description |
|---|---|
|
Round trip time |
Round-trip time (RTT) measures the amount of time taken by the request packet to travel from Test Agent Devices to the remote endpoint and the response packet to travel from the remote endpoint to Test Agent Devices. RTT indicates the time delay between sending a request and receiving a response. RTT indicates the time delay between sending a request and receiving a response. |
|
Round trip jitter |
Jitter occurs when the packets experience a delay during a round trip, from the Test Agent to the remote endpoint. The delay is calculated in milliseconds. |
|
Round trip inter-arrival |
The Round-trip interarrival jitter indicates an estimate of the total statistical variance of a packet’s interarrival time as defined in IETF RFC 1889. The interarrival jitter is calculated in milliseconds |
|
Loss |
Loss indicates the percentage of request packets sent for which responses were not received. |
RPM Ping
The RPM Ping measurement measures one-way ICMP timestamps to evaluate connectivity and latency. Use this Plug-in to understand the minimum, maximum, standard deviation, and jitter. In addition, you can also view the number of responses received, the percentage of lost packets, and the total number of packets sent. If you are using ACX, PTX or MX devices, use this Plug-in to evaluate connectivity and latency.
| Parameter | Description |
|---|---|
| GENERAL | |
| Clients* |
Select one or more Test Agent interfaces on which you want to run measurements by using this Plug-in. A separate measurement will be run on each interface you select. For more information, see Client Configuration for Plug-ins. |
|
Hosts* |
Specify the target hostname or IP address. When you click the text box, the Select Host page appears where you can enter hostnames. To add more than one Hosts, click + Add Host and specify the following:
|
| Time between requests |
Specify the time taken between successive ping requests initiated by the router. Unit—Seconds (s) Default value—10 s Range—1 s through 255 s |
|
ADVANCED |
|
| Collection interval |
Specify the collection interval. Collection interval is the frequency at which the results are collected from the device. Collection interval must be larger than the specified Time between requests. Unit—Seconds (s) Default value—15 s Range—5 s through 300 s |
| Device response timeout |
Specify the device response timeout value. Device response timeout determines the time to wait for a response from the router. If the specified time is exceeded, the connection to the device is considered failed. Device response timeout must be larger than the specified Collection Interval. Unit—Seconds (s) Default value—200 s Range—30 s through 300 s |
| Routing instance |
Specify the name of routing instance on the router used by the probes. |
| Data size |
Specify the size of the data portion of the request packet sent from the router. Default value—0 Range—0 through 65400 |
| Data fill |
Specify the contents of the data portion of the request packets sent from the router. The value should be in hexadecimal format. |
| TTL |
Specify the number of times the packets hop before a device discards the packet. Time to live (TTL) value indicates lifespan of a request packet. TTL prevents infinite loop in a network when the packet fails to reach the destination. For example, if you have entered the TTL value as 64, every time the packet passes a device, the value is reduced by one until the packet reaches the remote server. If the entered value reaches zero before reaching the remote endpoint, the packet is discarded. Default value—64 Range—1 through 254 |
| DSCP code points |
Specify the Differentiated Services Code Point (DSCP) value that is used in the IP packet headers. Maximum—64 characters |
| Hardware timestamp |
Enable hardware timestamping of RPM probe messages in the Packet Forwarding Engine host processor on the router. In case of ping Plug-in, you can enable timestamping of RPM messages in the Packet Forwarding Engine host processor. By default, the toggle button is disabled. |
| Ping timestamp |
Enable ping timestamp to perform ICMP timestamp requests instead of ICMP echo requests. By default, the toggle button is disabled. |
| One way hardware timestamp |
Enable the one-way hardware timestamping for one-way measurements (delay and jitter) By default, the toggle button is disabled. |
| IPv6 local link |
Specify the router link-local logical interface name for the egress interface to be used. This applies only for Test sessions with IPv6 address as the target address. Maximum—64 characters |
| Metric | Description |
|---|---|
|
Round trip time |
Round-trip time (RTT) measures the amount of time taken by the request packet to travel from Test Agent Devices to the remote endpoint and the response packet to travel from the remote endpoint to Test Agent Devices. RTT indicates the time delay between sending a request and receiving a response. RTT indicates the time delay between sending a request and receiving a response. |
|
Round trip jitter |
Jitter occurs when the packets experience a delay during a round trip, from the Test Agent to the remote endpoint. The delay is calculated in milliseconds. |
|
Round trip inter-arrival |
The Round-trip interarrival jitter indicates an estimate of the total statistical variance of a packet’s interarrival time as defined in IETF RFC 1889. The interarrival jitter is calculated in milliseconds |
|
Loss |
Loss indicates the percentage of request packets sent for which responses were not received. |
RPM RFC2544 CCC
RFC2544 tests are standardized benchmarks used to measure network performance metrics like throughput, latency, and frame loss. RFC 2544 tests are performed by transmitting test packets from a device that functions as the generator or the initiator. These packets are sent to a device that functions as the reflector, which receives and returns the packets back to the initiator. This Measurement configures and collects results from the probe service for RPM RFC2544 CCC generator/initiator. For more information, see RFC 2544-Based Benchmarking Tests.
| Parameter | Description |
|---|---|
| GENERAL | |
| Senders* |
Select one or more Test Agent interfaces on which you want to run measurements by using this Plug-in. A separate measurement will be run on each interface you select. For more information, see Client Configuration for Plug-ins. |
|
Test type* |
Select the type of RFC2544 test to be performed. The available test types are:
Default—Throughput |
|
Packet size |
Specify the size of the test packets in bytes. Unit—Bytes Default value—64 Range—64 through 9216 |
|
Rate (kbps) |
Specify the maximum rate limit Unit—Kilobytes per second Default value—64 Range—64 through 1000 |
|
Step percentage [Frame-Loss] (%) |
Specify the step percentage. This is only applicable for frame-loss test type. Unit—Percentage (%) Range—10 through 100 |
| Test iteration duration |
Specify the duration for a single iteration of test. Unit—Second (s) Default value—20 Range—10 through 300 |
|
CCC FAMILY PARAMETERS |
|
| Destination MAC address |
Specify the reflector's MAC address. You must follow the aa:bb:cc:dd:ee:ff format. |
| Source MAC address |
Specify the sender's MAC address. You must follow the aa:bb:cc:dd:ee:ff format. |
|
ADVANCED |
|
| DSCP code points |
Select the Differentiated Services Code Point (DSCP) value that is used in the IP test packet headers. The available values are none, af11, af12, af13, af21, af22, af23, af31, af32, af33, af41, af42, af43, be, cs1, cs2, cs3, cs4, cs5, cs6, cs7, ef, nc1, nc2. Default: none |
| Collection interval |
Specify the collection interval. Collection interval is the frequency at which the results are collected from the device. Unit—Seconds (s) Default value—30 s Range—30 s through 300 s |
| Device response timeout |
Specify the device response timeout value. Device response timeout determines the time to wait for a response from the router. If the specified time is exceeded, the connection to the router is considered failed. Device response timeout must be larger than the specified Collection Interval. Unit—Seconds (s) Default value—120 s Range—120 s through 300 s |
| Metric | Description |
|---|---|
| Tx packets (packets) |
The total number of packets that are sent to the reflector. This metric is available only for measurements with throughput or frame-loss test types. |
| Rx packets (packets) |
The total number of packets received from the reflector. This metric is available only for measurements with throughput or frame-loss test types. |
| Rate |
The rate at which the test packets are transmitted. For measurements with test type frame-loss, rate corresponds with the rate percent at Tx (sender). For any other test type, rate is measured in kilobytes per second. |
| Throughput | The maximum rate at which the packets are successfully sent and received by the sender without any frame loss. This metric is available only for measurements with test type throughput. |
| Frameloss (%) |
The percentage of test packets lost during transmission. This metric is available only for measurements with test type frame-loss. |
| Burst length (packets) |
The number of packets transmitted in a single burst. This metric is available only for measurements with test type back-to-back. |
| Theoretical bandwidth (Kpbs) |
The maximum bandwidth that the network can support, which is measured kilobytes per second. This metric is available only for measurements with test type back-to-back. |
| Latency (s) | The time taken by a test packet to travel from the sender to the reflector and back, which is measured in microseconds. This metric is available only for measurements with test type latency. |
RPM RFC2544 ETH
RFC2544 tests are standardized benchmarks used to measure network performance metrics like throughput, latency, and frame loss. RFC 2544 tests are performed by transmitting test packets from a device that functions as the generator or the initiator. These packets are sent to a device that functions as the reflector, which receives and returns the packets back to the initiator. This Measurement configures and collects results from the probe service for RPM RFC2544 ETH generator/initiator. For more information, see RFC 2544-Based Benchmarking Tests.
| Parameter | Description |
|---|---|
| GENERAL | |
| Senders |
Select one or more Test Agent interfaces on which you want to run measurements by using this Plug-in. A separate measurement will be run on each interface you select. For more information, see Client Configuration for Plug-ins. |
|
Test type |
Select the type of RFC2544 test to be performed. The available test types are:
Default—Throughput |
|
Packet size |
Specify the size of the test packets in bytes. Unit—Bytes Default value—64 Range—64 through 9216 |
|
Rate (kbps) |
Specify the maximum rate limit. Unit—Kilobytes per second Default value—64 Range—64 through 1000 |
|
Step percentage [Frame-Loss] (%) |
Specify the step percentage. This is only applicable for frame-loss test type. Unit—Percentage (%) Range—10 through 100 |
| Test iteration duration |
Specify the duration for a single iteration of test. Unit—Second (s) Default value—20 Range—10 through 300 |
| Destination MAC address |
Specify the reflector's MAC address. You must follow the aa:bb:cc:dd:ee:ff format. |
| Source MAC address |
Specify the sender's MAC address. You must follow the aa:bb:cc:dd:ee:ff format. |
|
In Service |
Enable the toggle button to use In-Service to test without interrupting regular data traffic and disable the toggle button to use Out-of-Service to test in isolated environment. By default, the toggle button is disabled. |
|
Service type |
Select the service type from the drop-down list. Choose ELAN to swap the source and destination MAC addresses and ELINE to keep the MAC address the same. |
|
DSCP code points |
Select the Differentiated Services Code Point (DSCP) value that is used in the IP test packet headers. The available values are none, af11, af12, af13, af21, af22, af23, af31, af32, af33, af41, af42, af43, be, cs1, cs2, cs3, cs4, cs5, cs6, cs7, ef, nc1, nc2. Default: none |
| Collection interval |
Specify the collection interval. Collection interval is the frequency at which the results are collected from the device. Unit—Seconds (s) Default value—30 s Range—30 s through 300 s |
| Device response timeout |
Specify the device response timeout value. Device response timeout determines the time to wait for a response from the router. If the specified time is exceeded, the connection to the router is considered failed. Device response timeout must be larger than the specified Collection Interval. Unit—Seconds (s) Default value—120 s Range—120 s through 300 s |
| Metric | Description |
|---|---|
| Tx packets (packets) |
The total number of packets (Tx) that are sent from the sender to the reflector during the RFC2544 test. A higher count for Tx packets indicate flooding or misconfiguration. |
| Rx packets (packets) |
The total number of packets (Rx) that are received from the reflector during the RFC2544 test. A lower count of Rx packets indicate packet drops. |
| Rate |
The rate at which the test packets are transmitted, which is measured in kilobytes per second. The rate is calculated as the size of the response received divided by the total response time. The rate is displayed in kilobytes per second. |
| Throughput |
The maximum rate at which the test packets are successfully sent and received by the sender without any frame loss. |
| Frameloss (%) |
The percentage of test packets lost during transmission. If the value is lower, it has better overall stability. |
| Burst length (packets) |
The number of packets transmitted in a single burst. |
| Theoretical bandwidth (Kpbs) |
The maximum bandwidth the network can support, which is measured in kilobytes per second. The value will be higher than the actual usable bandwidth due to overhead. |
| Latency (s) | The time taken by a test packet to travel from the sender to the reflector and back, which is measured in seconds |
RPM RFC2544 INET
RFC2544 tests are standardized benchmarks used to measure network performance metrics like throughput, latency, and frame loss. RFC 2544 tests are performed by transmitting test packets from a device that functions as the generator or the initiator. These packets are sent to a device that functions as the reflector, which receives and returns the packets back to the initiator. This Measurement configures and collects results from the probe service for RPM RFC2544 INET generator/initiator. For more information, see RFC 2544-Based Benchmarking Tests.
| Parameter | Description |
|---|---|
| GENERAL | |
| Senders |
Select one or more Test Agent interfaces on which you want to run measurements by using this Plug-in. A separate measurement will be run on each interface you select. For more information, see Client Configuration for Plug-ins. |
|
Test type |
Select the type of RFC2544 test to be performed. The available test types are:
Default—Throughput |
|
Packet size |
Specify the size of the test packets in bytes. Unit—Bytes Default value—64 Range—64 through 9216 |
|
Rate (kbps) |
Specify the maximum rate limit Unit—Kilobytes per second Default value—64 Range—64 through 1000 |
|
Step percentage [Frame-Loss] (%) |
Specify the step percentage. This is only applicable for frame-loss test type. Unit—Percentage (%) Range—10 through 100 |
| Test iteration duration |
Specify the duration for a single iteration of test. Unit—Second (s) Default value—20 Range—10 through 300 |
|
INET FAMILY PARAMETERS |
|
| Destination IP address |
Specify the IPv4 address of reflector. |
| Destination UDP Port |
Specify the UDP port the reflector is listening on for incoming traffic. |
| Source UDP port |
Specify the UDP port used by the sender. |
| Halt on IP prefix down |
Use the Halt on IP prefix down to stop the test if the previously advertised IP prefix is unavailable. By default, the toggle option is disabled. |
|
ADVANCED |
|
| DSCP code points |
Select the Differentiated Services Code Point (DSCP) value that is used in the IP test packet headers. The available values are none, af11, af12, af13, af21, af22, af23, af31, af32, af33, af41, af42, af43, be, cs1, cs2, cs3, cs4, cs5, cs6, cs7, ef, nc1, nc2. Default: none |
| Collection interval |
Specify the collection interval. Collection interval is the frequency at which the results are collected from the device. Unit—Seconds (s) Default value—30 s Range—30 s through 300 s |
| Device response timeout |
Specify the device response timeout value. Device response timeout determines the time to wait for a response from the router. If the specified time is exceeded, the connection to the router is considered failed. Device response timeout must be larger than the specified Collection Interval. Unit—Seconds (s) Default value—120 s Range—120 s through 300 s |
| Metric | Description |
|---|---|
| Tx packets (packets) |
The total number of test packets that are sent from the sender to the reflector during the RFC2544 test. A higher count for Tx packets indicate flooding or misconfiguration. |
| Rx packets (packets) |
The total number of packets that are received from the reflector during the RFC2544 test. A lower count of Rx packets indicate packet drops. |
| Rate |
The rate at which the test packets are transmitted, which is measured in kilobytes per second. The rate is calculated as the size of the response received divided by the total response time. The rate is displayed in Kilobytes Per Second. |
| Throughput |
The maximum rate at which the test packets are successfully sent and received by the sender without any frame loss. |
| Frameloss (%) |
The percentage of test packets lost during transmission. If the value is lower, it has better overall stability. |
| Burst length (packets) |
The number of packets transmitted in a single burst. |
| Theoretical bandwidth (Kpbs) |
The maximum bandwidth the network can support, which is measured kilobytes per second. The value will be higher than the actual usable bandwidth due to overhead. |
| Latency (s) | The time taken by a test packet to travel from the sender to the reflector and back, which is measured in seconds. |
RPM RFC2544 REFCCC
RFC2544 tests are standardized benchmarks used to measure network performance metrics like throughput, latency, and frame loss. RFC 2544 tests are performed by transmitting test packets from a device that functions as the generator or the initiator. These packets are sent to a device that functions as the reflector, which receives and returns the packets back to the initiator. This Measurement configures and collects results from the probe service for RPM RFC2544 CCC reflector. For more information, see RFC 2544-Based Benchmarking Tests.
| Parameter | Description |
|---|---|
| GENERAL | |
| Reflectors* |
Select one or more Test Agent interfaces on which you want to run measurements by using this Plug-in. A separate measurement will be run on each interface you select. For more information, see Client Configuration for Plug-ins. |
|
CCC FAMILY PARAMETERS |
|
|
Destination MAC address |
Specify the reflector's MAC address. You must follow the aa:bb:cc:dd:ee:ff format. |
|
Source MAC address |
Specify the sender's MAC address. You must follow the aa:bb:cc:dd:ee:ff format. |
|
Reflect Etype |
Specify the ethernet type to match the selected reflect mode. Range: 1 through 65535 |
|
Reflect mode |
Select the reflect mode for swapping the MAC addresses in test packets. The available values are none, mac-swap, no-mac-swap. |
|
ADVANCED |
|
| Signature check disable |
Enable the toggle button to disable the signature check on the reflected packets. Disabling the signature check is only applicable for Junos OS Evolved devices. |
| DSCP code points |
Select the Differentiated Services Code Point (DSCP) value that is used in the IP test packet headers. The available values are none, af11, af12, af13, af21, af22, af23, af31, af32, af33, af41, af42, af43, be, cs1, cs2, cs3, cs4, cs5, cs6, cs7, ef, nc1, nc2. Default: none |
| Collection interval |
Specify the collection interval. Collection interval is the frequency at which the results are collected from the device. Unit—Seconds (s) Default value—30 s Range—30 s through 300 s |
| Device response timeout |
Specify the device response timeout value. Device response timeout determines the time to wait for a response from the router. If the specified time is exceeded, the connection to the router is considered failed. Device response timeout must be larger than the specified Collection Interval. Unit—Seconds (s) Default value—120 s Range—120 s through 300 s |
| Metric | Description |
|---|---|
| Reflected packet counts | The total number of packets received by the sender from the reflector. If the count is lower than the sent Tx packets, it can cause packet loss or network interruption. |
| Reflected bytes count |
The total number of bytes received by the sender from the reflector. |
RPM RFC2544 REF ETH
RFC2544 tests are standardized benchmarks used to measure network performance metrics like throughput, latency, and frame loss. RFC 2544 tests are performed by transmitting test packets from a device that functions as the generator or the initiator. These packets are sent to a device that functions as the reflector, which receives and returns the packets back to the initiator. This Measurement configures and collects results from the probe service for RPM RFC2544 ETH reflector. For more information, see RFC 2544-Based Benchmarking Tests.
| Parameter | Description |
|---|---|
| GENERAL | |
| Reflectors* |
Select one or more Test Agent interfaces on which you want to run measurements by using this Plug-in. A separate measurement will be run on each interface you select. For more information, see Client Configuration for Plug-ins. |
|
ETHERNET-SWITCHING FAMILY PARAMETERS |
|
|
Destination MAC address |
Specify the reflector's MAC address. You must follow the aa:bb:cc:dd:ee:ff format. |
|
In-Service |
Enable the toggle button to use in-Service to test without interrupting regular data traffic and disable the toggle button to use Out-of-Service to test in isolated environment. By default, the toggle button is disabled. |
|
Reflect Etype |
Specify the Ethernet Ethertype value used to identify frames for reflection. Range: 1 through 65535 |
|
IP Swap |
Enable IP swap to swap the source and destination IP addresses in the reflected packet and disable IP swap to not swap the source and destination IP addresses in the reflected packet. By default, the toggle button is disabled. |
|
UDP Port Swap |
Enable UDP port swap to swap the source and destination UDP port in the reflected packet and disable UDP port swap to not swap the source and destination UDP port in the reflected packet. By default, the toggle button is disabled. |
|
ADVANCED |
|
| Signature check disable |
Enable the toggle button to disable the signature check on the reflected packets. Disabling the signature check is only applicable for Junos OS Evolved devices. |
| DSCP code points |
Select the Differentiated Services Code Point (DSCP) value that is used in the IP test packet headers. The available values are none, af11, af12, af13, af21, af22, af23, af31, af32, af33, af41, af42, af43, be, cs1, cs2, cs3, cs4, cs5, cs6, cs7, ef, nc1, nc2. Default: none |
| Collection interval |
Specify the collection interval. Collection interval is the frequency at which the results are collected from the device. Unit—Seconds (s) Default value—30 s Range—30 s through 300 s |
| Device response timeout |
Specify the device response timeout value. Device response timeout determines the time to wait for a response from the router. If the specified time is exceeded, the connection to the router is considered failed. Device response timeout must be larger than the specified Collection Interval. Unit—Seconds (s) Default value—120 s Range—120 s through 300 s |
| Metric | Description |
|---|---|
| Reflected packet counts | The total number of packets received by the sender from the reflector. If the count is lower than the sent Tx packets, it can cause packet loss or network interruption. |
| Reflected bytes count |
The total number of bytes received by the sender from the reflector. |
RPM RFC2544 REF INET
RFC2544 tests are standardized benchmarks used to measure network performance metrics like throughput, latency, and frame loss. RFC 2544 tests are performed by transmitting test packets from a device that functions as the generator or the initiator. These packets are sent to a device that functions as the reflector, which receives and returns the packets back to the initiator. This Measurement configures and collects results from the probe service for RPM RFC2544 INET reflector. For more information, see RFC 2544-Based Benchmarking Tests.
| Parameter | Description |
|---|---|
| GENERAL | |
| Reflectors* |
Select one or more Test Agent interfaces on which you want to run measurements by using this Plug-in. A separate measurement will be run on each interface you select. For more information, see Client Configuration for Plug-ins. |
|
INET FAMILY PARAMETERS |
|
| Destination IP address |
Specify the IPv4 address of reflector. |
| Destination UDP Port |
Specify the UDP port the reflector is listening on for incoming traffic. |
| Source UDP port |
Specify the UDP port used by the sender. |
| Halt on IP prefix down |
Use the Halt on IP prefix down to stop the test if the previously advertised IP prefix is unavailable. By default, the toggle option is disabled. |
|
ADVANCED |
|
| Signature check disable |
Enable the toggle button to disable the signature check on the reflected packets. Disabling the signature check is only applicable for Junos OS Evolved devices. |
| DSCP code points |
Select the Differentiated Services Code Point (DSCP) value that is used in the IP test packet headers. Available values are none, af11, af12, af13, af21, af22, af23, af31, af32, af33, af41, af42, af43, be, cs1, cs2, cs3, cs4, cs5, cs6, cs7, ef, nc1, nc2. Default: none |
| Collection interval |
Specify the collection interval. Collection interval is the frequency at which the results are collected from the device. Unit—Seconds (s) Default value—30 s Range—30 s through 300 s |
| Device response timeout |
Specify the device response timeout value. Device response timeout determines the time to wait for a response from the router. If the specified time is exceeded, the connection to the router is considered failed. Device response timeout must be larger than the specified Collection Interval. Unit—Seconds (s) Default value—120 Range—120 through 300 |
| Metric | Description |
|---|---|
| Reflected packet counts | The total number of packets (Tx) received by the sender from the reflector. If the count is lower than the sent Tx packets, it can cause packet loss or network interruption. |
| Reflected bytes count |
The total number of bytes received by the sender from the reflector. |
RPM TCP
The RPM TCP measurement checks how well devices connect and perform using TCP connections. It checks if a remote device can be reached using TCP. It also gives information on reachability, packet loss, and how reliable the connection is. The ACX, PTX, and MX devices supports this measurement.
| Parameter | Description |
|---|---|
| GENERAL | |
| Clients* |
Select one or more Test Agent interfaces on which you want to run measurements by using this Plug-in. A separate measurement will be run on each interface you select. For more information, see Client Configuration for Plug-ins. |
|
Servers* |
Specify the hostname or the IP address of the remote endpoint. When you click the text box, the Select server page appears where you can enter details. To add more than one servers, click + Add Server and specify the following:
|
|
Time between requests |
Specify the time taken between successive TCP requests initiated by the router. Unit—Seconds (s) Default value—10 s Range—1 s through 255 s |
|
ADVANCED |
|
| Collection interval |
Specify the collection interval. Collection interval is the frequency at which the results are collected from the device. Collection interval must be larger than the specified Time between requests. Unit—Seconds (s) Default value—15 s Range—5 s through 300 s |
| Device response timeout |
Specify the device response timeout value. Device response timeout determines the time to wait for a response from the router. If the specified time is exceeded, the connection to the device is considered failed. Device response timeout must be larger than the specified Collection Interval. Unit—Seconds (s) Default value—200 s Range—30 s through 300 s |
| Routing instance |
Specify the name of routing instance on the router used by the request packets. Maximum value—64 |
| Data size |
Specify the size of the data portion of the request packets sent from the router. Default value—0 Range—0 through 65400 |
| Data fill |
Specify the contents of the data portion of the request packets sent from the router. The value should be in hexadecimal format. |
| TTL |
Specify the number of times the packets hop before a device discards the packet. Time to live (TTL) value indicates lifespan of a request packet. TTL prevents infinite loop in a network when the packet fails to reach the destination. For example, if you have entered the TTL value as 64, every time the packet passes a device, the value is reduced by one until the packet reaches the remote server. If the entered value reaches zero before reaching the remote endpoint, the packet is discarded. Default value—64 Range—1 through 254 |
| DSCP code points |
Specify the Differentiated Services Code Point (DSCP) value that is used in the IP packet headers. Maximum—64 characters |
| IPv6 Local Link |
Specify the router link-local logical interface name for the egress interface to be used. This applies only for Test sessions with IPv6 address as the target address. Maximum—64 characters |
| Metric | Description |
|---|---|
|
Round trip time |
Round-trip time (RTT) measures the amount of time taken by the request packet to travel from Test Agent Devices to the remote endpoint and the response packet to travel from the remote endpoint to Test Agent Devices. RTT indicates the time delay between sending a request and receiving a response. RTT indicates the time delay between sending a request and receiving a response. |
|
Round trip jitter |
Jitter occurs when the packets experience a delay during a round trip, from the Test Agent to the remote endpoint. The delay is calculated in milliseconds. |
|
Round trip inter-arrival |
The Round-trip interarrival jitter indicates an estimate of the total statistical variance of a packet’s interarrival time as defined in IETF RFC 1889. The interarrival jitter is calculated in milliseconds |
|
Loss |
Loss indicates the percentage of request packets sent for which responses were not received. |
RPM TWAMP
The two way active measurement protocol (TWAMP) facilitates the measurement of two-way or round-trip network performance metrics. Running a TWAMP measurement provides information about the round-trip delay, delay variance (jitter), and packet loss. The Session-Initiator creates TWAMP test packets and sends to the Session-Reflector in the TWAMP server, and the Session-Reflector sends back a measurement packet when a test packet is received. TWAMP uses TWAMP-Control protocol to perform a handshake between initiator and reflector.
| Parameter | Description |
|---|---|
| GENERAL | |
| Clients* |
Select one or more Test Agent interfaces on which you want to run measurements by using this Plug-in. A separate measurement will be run on each interface you select. For more information, see Client Configuration for Plug-ins. |
|
Hosts* |
Specify IPv4 or IPv6 Address of TWAMP reflector. When you click the text box, the Select reflectors page appears where you can add reflectors. On this page:
|
| Time between requests* |
Specify the time taken between successive TWAMP requests initiated by the router. Unit—Seconds (s) Default value—10 s Range—1 s through 255 s |
|
ADVANCED |
|
| Collection interval* |
Specify the collection interval. Collection interval is the frequency at which the results are collected from the device. Collection interval must be larger than the specified Time between requests. Unit—Seconds (s) Default value—15 s Range—5 s through 300 s |
| Device response timeout |
Specify the device response timeout value. Device response timeout determines the time to wait for a response from the router. If the specified time is exceeded, the connection to the device is considered failed. Device response timeout must be larger than the specified Collection Interval. Unit—Seconds (s) Default value—200 s Range—30 s through 300 s |
| Routing instance |
Specify the name of routing instance on the router used by the request packets. Maximum value—64 |
|
Zero fill |
Enable Zero Fill to populate the content for the request packet with zeros. |
|
Data size |
Specify the size of the data portion of the request packets sent from the router. Default value—60. Range—60 to 1400. |
|
TTL |
Specify the number of times the packets hop before a device discards the packet. Time to live (TTL) value indicates lifespan of a request packet. TTL prevents infinite loop in a network when the packet fails to reach the destination. For example, if you have entered the TTL value as 64, every time the packet passes a device, the value is reduced by one until the packet reaches the remote server. If the entered value reaches zero before reaching the remote endpoint, the packet is discarded. Default value—64 Range—1 to 254 |
| DSCP Code Points |
Specify the Differentiated Services Code Point (DSCP) value that is used in the IP packet headers. Maximum—64 characters |
| IPv6 Local Link |
Specify the router link-local logical interface name for the egress interface to be used. This applies only for Test sessions with IPv6 address as the target address. Maximum—64 characters |
|
PFE timestamping |
Enable PFE timestamping to perform timestamping on Packet Forward Engine host. By default, the toggle button is disabled. |
| Metric | Description |
|---|---|
|
Round trip time |
Round-trip time (RTT) measures the amount of time taken by the request packet to travel from a router to the remote endpoint and the response packet to travel from the remote endpoint to a router. RTT indicates the time delay between sending a request and receiving a response. RTT indicates the time delay between sending a request and receiving a response. |
|
Round trip jitter |
Jitter occurs when the packets experience a delay during a round trip, from the Test Agent to the remote endpoint. The delay is calculated in milliseconds. |
|
Round trip inter-arrival |
The Round-trip interarrival jitter indicates an estimate of the total statistical variance of a packet’s interarrival time as defined in IETF RFC 1889. The interarrival jitter is calculated in milliseconds. |
|
Egress time |
Egress time indicates the time at which the test packet leave the router. |
|
Ingress time |
Ingress time indicates the time at which the test packet reaches the router. |
|
Egress jitter |
Egress jitter indicates the variation in the time between test packets sent from the router. The egress jitter is calculated in milliseconds. |
|
Ingress jitter |
Ingress jitter indicates the variation in the time between test packets received by the router. The ingress jitter is calculated in milliseconds. |
|
Loss |
Loss indicates the percentage of request packets sent for which responses were not received. |
RPM UDP
When a UDP measurement starts, the Test Agents will generate traffic at the rate you specify. The rate is the Layer 2 Ethernet rate, also known as the Committed Information Rate (CIR). It includes the Ethernet headers with the CRC checksum but not the Frame Gap, Preamble, or Start of Frame Delimiter. The UDP flow sent by the sender Test Agent includes timestamps and sequence numbers, so that the receiving Test Agent can calculate one-way delay, jitter, and packet loss. This Test checks if your network is good enough for quality-demanding services such as client–server applications and video conferencing.
| Parameter | Description |
|---|---|
| GENERAL | |
| Clients* |
Select one or more Test Agent interfaces on which you want to run measurements by using this Plug-in. A separate measurement will be run on each interface you select. For more information, see Client Configuration for Plug-ins. |
|
Servers* |
Specify the remote IP address or hostname of the server to which Test Agents send the requests. When you click the text box, the Select server page appears where you can enter details. To add more than one servers, click + Add Server and specify the following:
|
| Time Between Requests |
Specify the time taken between successive UDP requests initiated by the routers. Unit—Seconds (s). Default value—10 s. Range—1 s through 255 s. |
|
Remote port |
Configure the remote port number for the Test sessions. Default value—7. Range—7 through 65535. |
|
ADVANCED |
|
| Collection Interval |
Specify the collection interval. Collection interval is the frequency at which the results are collected from the remote endpoint or the device. Collection interval must be larger than the specified Time between requests. Unit—Seconds (s). Default value—15 s. Range—5 s through 300 s. |
| Device Response Timeout |
Specify the device response timeout value. Device response timeout determines the time to wait for a response from the router. If the specified time is exceeded, the connection to the device is considered failed. Device response timeout must be larger than the specified Collection Interval. Unit—Seconds (s). Default value—200 s. Range—30 s through 300 s. |
| Routing instance |
Specify the name of routing instance on the router used by the probes. Maximum value—64. |
| Data Size |
Specify the size of the data portion of the request packets sent from the router. Default value—0. Range—0 through 65400. |
| Data fill |
Specify the contents of the data portion of the request packets sent from the router. The value should be in hexadecimal format. The value should be in hexadecimal format. |
| TTL |
Specify the number of times the packets hop before a device discards the packet. Time to live (TTL) value indicates lifespan of a request packet. TTL prevents infinite loop in a network when the packet fails to reach the destination. For example, if you have entered the TTL value as 64, every time the packet passes a device, the value is reduced by one until the packet reaches the remote server. If the entered value reaches zero before reaching the remote endpoint, the packet is discarded. Default value—64. Range—1 through 254. |
| DSCP Code Points |
Specify the Differentiated Services Code Point (DSCP) value that is used in the IP packet headers. Maximum—64 characters. |
| Hardware Timestamp |
Enable hardware timestamping of RPM probe messages in the Packet Forwarding Engine host processor on the router. By default, the toggle button is disabled. |
| Ping Timestamp |
Enable ping timestamping to send UDP timestamp requests. By default, the toggle button is disabled. |
| One Way Hardware Timestamp |
Enable the one-way hardware timestamping for one-way delay and jitter measurements. By default, the toggle button is disabled. |
| IPv6 Local Link |
Specify the router link-local logical interface name for the egress interface to be used. This applies only for Test sessions with IPv6 address as the target address. Maximum—64 characters. |
| Metric | Description |
|---|---|
|
Round trip time |
Round-trip time (RTT) measures the amount of time taken by the request packet to travel from Test Agent Devices to the remote endpoint and the response packet to travel from the remote endpoint to Test Agent Devices. RTT indicates the time delay between sending a request and receiving a response. RTT indicates the time delay between sending a request and receiving a response. |
|
Round trip jitter |
Jitter occurs when the packets experience a delay during a round trip, from the Test Agent to the remote endpoint. The delay is calculated in milliseconds. |
|
Round trip inter-arrival |
The Round-trip interarrival jitter indicates an estimate of the total statistical variance of a packet’s interarrival time as defined in IETF RFC 1889. The interarrival jitter is calculated in milliseconds |
|
Loss |
Loss indicates the percentage of request packets sent for which responses were not received. |
RPM Y.1731 DM
RPM Y.1731 Delay Measurement (DM) measurement is used to evaluate the network performance with respect to time. It is a service OAM (Operations, Administration, and Maintenance) mechanism defined by the ITU-T to monitor network performance.
Running an RPM Y.1731 DM measurement measures delay and delay variance of packets. The local maintenance end point (MEP) sends packets that has timestamps to the remote maintenance end point (MEP) and vice-versa. The Test Agents then calculate one-way delay as well as two-way delay measurements. For more information on Y.1731 Ethernet Service OAM, see ITU-T Y.1731 Ethernet Service OAM Overview.
| Parameter | Description |
|---|---|
| GENERAL | |
| Senders* |
Select one or more Test Agent interfaces on which you want to run measurements by using this Plug-in. A separate measurement will be run on each interface you select. For more information, see Client Configuration for Plug-ins. |
|
SLA Iterators |
Specify one or more performance monitoring iterator profile names. When you click the text box, the Select iterator page appears where you can enter details. To add more than one iterator, click + Add iterator and specify the following:
|
| Collection interval (s) |
Specify the collection interval. Collection interval is the frequency at which the results related to delay and jitter are collected from the router. Unit—Seconds (s). Default value—15 s. Range—5 s through 300 s. |
|
Device response timeout |
Specify the device response timeout value. Device response timeout determines the time to wait for a response from the router. If the specified time exceeds then the connection to the router is considered to be failed. Device response timeout must be larger than the specified Collection Interval. Unit—Seconds (s). Default value—200 s. Range—30 s through 300 s. |
| Metric | Description |
|---|---|
| Minimum two-way frame delay |
Minimum two-way frame delay indicates the minimum delay for each frame to travel from local maintenance end point (MEP) to the remote maintenance end point (MEP) and back to the local MEP. |
| Maximum two-way frame delay |
Maximum two-way frame delay indicates the maximum delay for each frame to travel from local MEP to the remote MEP and back to local MEP. |
| Average two-way frame delay |
Average two-way frame delay indicates the average delay for each frame to travel from local MEP to the remote MEP and back to the local MEP. |
| Minimum one-way frame delay at far end |
Minimum one-way frame delay at far end indicates the minimum delay for each frame to travel from local MEP to the remote MEP. |
| Maximum one-way frame delay at far end |
Maximum one-way frame delay at far end indicates the maximum delay for each frame to travel from local MEP to the remote MEP. |
| Average one-way frame delay at far end |
Average one-way frame delay at far end indicates the average delay for each frame to travel from local MEP to the remote MEP. |
| Minimum one-way frame delay at near end | Indicates the minimum delay for each frame to travel back from the remote MEP to local MEP. |
| Maximum one-way frame delay at near end |
Minimum one-way frame delay at near end indicates the maximum delay for each frame to travel back from the remote MEP to local MEP. |
| Average one-way frame delay at near end |
Average one-way frame delay at near end indicates the average delay for each frame to travel back from the remote MEP to local MEP. |
| Minimum two-way inter frame delay variance |
Minimum two-way inter frame delay variance indicates the minimum delay variance experienced to travel from local MEP to the remote MEP and back to the local MEP. |
| Maximum two-way inter frame delay variance |
Maximum two-way inter frame delay variance indicates the maximum delay variance experienced to travel from local MEP to the remote MEP and back to the local MEP. |
| Average two-way inter frame delay variance |
Average two-way inter frame delay variance indicates the average delay variance experienced to travel from local MEP to the remote MEP and back to the local MEP. |
| Minimum delay variance at far end |
Minimum delay variance at far end indicates the minimum delay variance experienced by each frame to travel from local MEP to the remote MEP. |
| Maximum frame delay variance at far end |
Maximum inter frame delay variance at far end indicates the minimum delay variance experienced by each frame to travel from local MEP to the remote MEP. |
| Average frame delay variance at far end |
Average frame delay variance at far end indicates the average delay variance experienced by each frame to travel from local MEP to the remote MEP. |
| Minimum frame delay variance at near end |
Minimum frame delay variance at near end indicates the minimum delay variance experienced by each frame to travel back from the remote MEP to local MEP. |
| Maximum frame delay variance at near end |
Maximum frame delay variance at near end indicates the maximum delay variance experienced by each frame to travel back from the remote MEP to local MEP. |
| Average frame delay variance at near end |
Average frame delay variance at near end indicates the average delay variance experienced by each frame to travel back from the remote MEP to local MEP. |
| SOAM frames transmitted |
SOAM frames received indicates the SOAM delay measurement messages transmitted by local MEP to the remote MEP to measure network performance. |
| SOAM frames received |
SOAM frames received indicates the SOAM delay measurement messages received by the remote MEP from the local MEP to measure network performance. |
RPM Y.1731 SLM
RPM Y.1731 Synthetic Loss measurement (SLM) measurement is used to measure the frame loss across the network. It is a service OAM (Operations, Administration, and Maintenance) mechanism defined by the ITU-T to monitor network performance.
Running an RPMY.1731 Synthetic Loss Measurement (SLM) measurement measures the number of frames lost during transmission. The local MEP sends synthetic frames to the remote MEP and compares the number of frames transmitted with the number received. The ratio of lost frames to the total number of frames that are sent is calculated to measure the frame loss on the network. For more information on Y.1731 Ethernet Service OAM, see ITU-T Y.1731 Ethernet Service OAM Overview.
| Parameter | Description |
|---|---|
| GENERAL | |
| Senders* |
Select one or more Test Agent interfaces on which you want to run measurements by using this Plug-in. A separate measurement will be run on each interface you select. For more information, see Client Configuration for Plug-ins. |
|
SLA Iterators* |
Specify one or more performance monitoring iterator profile names. When you click the text box, the Select iterator page appears where you can enter details. To add more than one iterator, click + Add iterator and specify the following:
|
| Collection interval (s) |
Specify the collection interval. Collection interval is the frequency at which the results related to delay and jitter are collected from the router. Unit—Seconds (s). Default value—15 s. Range—5 s through 300 s. |
|
Device response timeout |
Specify the device response timeout value. Device response timeout determines the time to wait for a response from the router. If the specified time exceeds then the connection to the router is considered to be failed. Device response timeout must be larger than the specified Collection Interval. Unit—Seconds (s). Default value—200 s. Range—30 s through 300 s. |
| Metric | Description |
|---|---|
| SOAM frames transmitted |
SOAM frames transmitted indicates the SOAM synthetic loss measurement frames transmitted by local MEP to the remote MEP to monitor network performance. |
| SOAM frames received |
SOAM frames received indicates the SOAM synthetic loss measurement frames received by the remote MEP from local MEP to monitor network performance. |
|
Frames transmitted at far end |
Frames transmitted at far end indicates the frames transmitted by local MEP to the remote MEP to monitor network performance. |
|
Frames received at far end |
Frames received at far end indicates the frames received by local MEP to the remote MEP to monitor network performance. |
|
Frames transmitted at near end |
Frames transmitted at far end indicates the frames transmitted back by the remote MEP to local MEP to monitor network performance. |
|
Frames received at near end |
Frames received at far end indicates the frames transmitted back by the remote MEP to local MEP to monitor network performance. |
|
Frame loss at far end |
Frame loss at far end indicates the number of frames that were sent by local MEP but failed to receive at the remote MEP. |
|
Frame loss at near end |
Frame loss at near end indicates the number of frames that were sent back by the remote MEP but failed to receive at the local MEP. |
| Min frame loss ratio at far end |
Minimum frame loss ratio indicates the minimum ratio of frames lost during transmission of frames from local MEP to the remote MEP. |
| Max frame loss ratio at far end |
Maximum frame loss ratio indicates the maximum ratio of frames lost during transmission of frames from local MEP to the remote MEP. |
| Avg frame loss ratio at far end |
Average frame loss ratio indicates the average ratio of frames lost during transmission of frames from local MEP to the remote MEP. |
| Min frame loss ratio at near end |
Minimum frame loss ratio at near end indicates the minimum ratio of frames lost during transmission of frames back to local MEP from the remote MEP. |
| Max frame loss ratio at near end |
Maximum frame loss ratio at near end indicates the maximum ratio of frames lost during transmission of frames back to local MEP from the remote MEP. |
| Avg frame loss ratio at near end |
Average frame loss ratio at near end indicates the average ratio of frames lost during transmission of frames back to local MEP from the remote MEP. |
| High loss intervals at far end |
High loss intervals at far end indicates the intervals when the number of lost frames traveling from the local MEP to the remote MEP exceeds the configured threshold. |
| High loss intervals at near end |
High loss intervals at near end indicates the intervals when the number of frames lost while traveling from the remote MEP to local MEP exceeds the configured threshold. |
|
Consecutive high loss intervals at far end |
Consecutive high loss intervals at far end indicates the consecutive intervals when the number of lost frames traveling from the local MEP to the remote MEP exceeds the configured threshold. |
|
Consecutive high loss intervals at near end |
Consecutive high loss intervals at near end indicates the consecutive intervals when the number of lost frames traveling from the remote MEP to local MEP exceeds the configured threshold. |
|
Availability indicator at far end |
Availability indicator at far end indicates the number of shorter intervals (deltas) within the measurement period that were lost when traveling from the local MEP to the remote MEP is below the configured threshold. |
| Availability indicator at near end |
Availability indicator at near end indicates the number of shorter intervals (deltas) within the measurement period that were lost when traveling from the remote MEP to local MEP is below the configured threshold. |
| Unavailability indicator at far end |
Unavailability indicator at far end indicates the number of shorter intervals (deltas) within the measurement period that were lost when traveling from local MEP to the remote MEP exceeds the configured threshold. |
| Unavailability indicator at near end |
Unavailability indicator at near end indicates the number of shorter intervals (deltas) within the measurement period that were lost when traveling from the remote MEP to local MEP exceeds the configured threshold. |
| Availability Frame Loss Ratio min at far end |
Availability Frame Loss Ratio min at far end indicates the minimum ratio of frames lost to the total transmitted frames within the measurement period while traveling from local MEP to the remote MEP is below the configured threshold. |
| Availability Frame Loss Ratio max at far end |
Availability Frame Loss Ratio max at far end indicates the maximum ratio of frames lost to the total transmitted frames within the measurement period while traveling from local MEP to the remote MEP is below the configured threshold. |
| Availability Frame Loss Ratio avg at far end |
Availability Frame Loss Ratio avg at far end indicates the average ratio of frames lost to the total transmitted frames within the measurement period while traveling from local MEP to the remote MEP is below the configured threshold. |
TCP
The TCP measurement is used to assess the network performance for client-server applications by sending TCP sessions between Test Agents. Running a TCP measurement provides information about the latency, jitter, throughput bandwidth, and monitor network congestion. When a TCP measurement starts, the client Test Agents send TCP packets to server Test Agents, and receives measurement information from server Test Agents. This gives an overall view of the network.
| Parameter | Description |
|---|---|
| GENERAL | |
| Clients* |
Select one or more Test Agent interfaces on which you want to run measurements by using this Plug-in. A separate measurement will be run on each interface you select. For more information, see Client Configuration for Plug-ins. |
|
Server* |
Select one or more Test Agent interfaces that you want you want to use as UDP servers. For more information, see Client Configuration for Plug-ins. |
|
Direction |
Choose the direction of the test traffic. The data is sent from 'Server to Client' or 'Client to Server'. Client to server—Evaluates the data upload capabilities. Server to client—Evaluates the data download capabilities. |
|
Rate (Mbit/s) |
Rate indicates the target data rate between the server and the client Test Agents. ES Rate is the number of errored-seconds occurred when the rate at which the TCP packet reception drops below the defined value. Unit—Megabit per second (Mbit/s) Range—0.01 Mbit/s through 1000000.0 Mbit/s |
|
ADVANCED |
|
|
Server TCP port |
Specify the port number used by the server Test Agent. Default value—5000 Range—1 through 65535 |
|
Client TCP port |
Specify the port number used by the client Test Agent. Range—1 through 65535 |
|
Number of flows |
Specify the number of TCP flows. If more than one flows are specified, you should not set the Client port. If set, the Plug-in activates an invalid configuration error, and if not set, the Client port gets a randomly assigned port number. Default value—1 Range—1 through 64 |
|
DSCP/IPP |
Specify the Differentiated Services Code Point (DSCP) or the IP Precedence (IPP) value that is used in the IP packet headers. DSCP is a six-bit binary value in the DS field of the IP header. DSCP value facilitates QoS for traffic management through the Best Effort, Assured Forwarding, Class Selector, and the Expedited Forwarding categories. See RFC 2474 for more information. Default value—0 Range—0 through 63 |
|
VLAN priority (PCP) |
Specify the value for the VLAN priority code point to be used in VLAN header. Range—0 through 7 |
|
Client connect delay (s) |
Specify the allowable delay until the client initiates TCP connection towards the server. Unit— Seconds (s) Default value—0 Range—0 through 10 |
|
Proxy address |
Specify the IP address of the TCP proxy server. |
|
Proxy port |
Specify the port number that the Test Agent uses for TCP proxy server. Range—1 through 65535 |
|
THRESHOLDS FOR ERRORED SECONDS (ES) |
|
|
Min rate (Mbit/s) |
Specify the minimum expected rate. An errored-second is raised if the TCP data rate drops below the defined value. Unit—Megabit per second (Mbit/s) Minimum—0.001 Mbit/s |
|
Max rate (Mbit/s) |
Specify the minimum expected rate. An errored-second is raised if the TCP data rate drops below the defined value. Unit—Megabit per second (Mbit/s) Minimum—0.001 Mbit/s |
| Metric | Description |
|---|---|
| Rate |
Rate indicates the speed or throughput (goodput) at which the Test Agent receives the TCP packets in a selected interval of time. The rate is displayed in Megabits Per Second. |
| ES |
ES is the number of seconds during which errors occurred in a specific duration of time. ES is an aggregate of all specific ES metrics. The ES is displayed in seconds. |
| ES rate |
ES Rate is the number of errored-seconds occurred when the data rate drops below the defined value. The ES rate is displayed in seconds. |
TWAMP Reflector
The TWAMP Reflector is a component of TWAMP. It receives test packets from the Session-Initiator and reflects them back. Running a TWAMP Reflector helps in evaluation of the quality of the network and provides information on how data is transmitted in two-directions; between Session-Initiator and Session-Reflector. This bidirectional communication enables the measurement of performance metrics such as round-trip delay, delay variance (jitter), and packet loss. This measurement is applicable for both IPv4 and IPv6.
| Parameter | Description |
|---|---|
|
GENERAL |
|
|
Clients* |
Select one or more Test Agent interfaces on which you want to run measurements by using this Plug-in. A separate measurement will be run on each interface you select. For more information, see Client Configuration for Plug-ins. |
|
Test session port |
Specify the destination port on which the TWAMP reflector listens. Default value—7000 Range—1 through 65535 |
|
Rate threshold for ES |
Specify the rate threshold for the combined rate for all sessions. If rate is below the threshold value, an errored-second is raised. Unit—Megabits per seconds (Mbit/s) Range—0.001 (Mbit/s) through 10000 (Mbit/s) |
|
Standalone mode |
Enable Standalone mode to push the metrics data to Routing Director. By default, the toggle button is disabled. |
| Metric | Description |
|---|---|
|
Received packets |
Received packets indicates the number of packets received by the Test Agent from the reflector. |
|
Rate |
Rate indicates the rate at which Test Agent received TWAMP traffic. It is the aggregate of all the concurrent sessions. The rate is calculated as the size of the response received divided by the total response time. The rate is displayed in Megabits Per Second. |
|
Active sessions |
Active sessions indicate the number of currently active sessions on the specified reflector. |
|
Bytes received |
Bytes received indicates the total size of TWAMP traffic received during the report interval. The size also includes the header size. |
|
ES |
ES is the number of seconds during which errors occurred in a specific duration of time. It is the total number of error-seconds that any threshold was violated. The ES is calculated in milliseconds. |
|
ES rate |
ES Rate is the number of errored-seconds raised because the rate threshold was violated. The ES rate is calculated in milliseconds. |
TWAMP/TWAMP Light
-
TWAMP—The two way Active measurement protocol facilitates the measurement of two-way or round-trip network performance metrics. Running a TWAMP measurement provides information about the round-trip delay, delay variance (jitter), and packet loss. The Session-Initiator creates TWAMP test packets and sends to the Session-Reflector in the TWAMP server, and the Session-Reflector sends back a measurement packet when a test packet is received. TWAMP uses TWAMP-Control protocol over TCP to perform a handshake between initiator and reflector.
-
TWAMP Light—The two way Active measurement protocol light is a simplified version of TWAMP. It is a stateless version of TWAMP where test parameters are predefined instead of negotiated. All test packets received by the server on a test port are reflected back and forgotten right away.
Running a TWAMP Light measurement provides information about the round-trip delay, delay variance (jitter), and packet loss. Unlike TWAMP, TWAMP Light does not use TWAMP-Control protocol.
| Parameter | Description |
|---|---|
| GENERAL | |
|
Senders* |
Select one or more Test Agent interfaces on which you want to run measurements by using this Plug-in. A separate measurement will be run on each interface you select. For more information, see Client Configuration for Plug-ins. |
|
Reflectors* |
Specify the reflector address. A Test Agent application can run a Reflector Plug-in whereas a Test Agent that is associated with a device needs to be configured to run Reflector Plug-in. When you click the text box, the Select reflectors page appears where you can add reflectors. On this page:
|
|
Rate |
Specify the rate at which the TWAMP sender will send test traffic. The rate is calculated as the size of the request packet sent divided by the total request time. Each Ethernet packet contains one frame. Unit—Megabits per seconds (Mbit/s) Range—0.0 Mbit/s through 10000.0 Mbit/s |
|
Time sync |
Select the time synchronization option. Select Yes, if the clocks of Test Agent and the reflector are synchronized via Network Time Protocol (NTP) using external NTP servers. Select No to disable the time synchronization option. Select Inband to use the in-band synchronization algorithm. |
|
Use hardware timestamping |
Enable hardware timestamping, SO_TIMESTAMPING parameter, on TWAMP socket), if you want to use the network interface card (NIC) of Test Agents for delay and jitter measurements. If Test Agent NIC does not support it, an error message is displayed, and the measurement does not produce any delay metrics. By default, the toggle button is disabled. |
|
THRESHOLDS FOR ERRORED SECONDS (ES) |
|
|
Loss% |
Specify the loss percentage value. If the loss percentage exceeds the configured value, an errored-second is raised. The Loss percentage is calculated by comparing the total number of packets that were lost with the total number of packets that were sent from the Test Agent. Unit—Percentage (%) Default value—0.0 % Range—0.0 % through 100.00 % |
|
Delay |
Specify the maximum tolerated value for delay. If there is time synchronization, the threshold value applies only to one-way delay. If there is no time synchronization, the threshold applies to round-trip delay. If delay exceeds the defined value, an errored-second is raised. Unit—Milliseconds (ms) Range—0.001 ms through 1000.0 ms |
|
Delay Variation |
Specify the maximum tolerated value for delay variance. If there is time synchronization, it applies to one-way delay. If there is no time synchronization, it applies to round-trip delay. If delay exceeds the defined value, an errored-second is raised. Unit—Milliseconds (ms) Range—0.001 ms through 1000.0 ms |
|
Expected DSCP Value |
Specify the expected DSCP or IP Precedence value on the IP packets received from the reflector device. If the received DSCP value does not match the configured value, an errored-second will be raised. Range—0 through 63 |
|
THRESHOLDS FOR SEVERELY ERRORED SECONDS (ES) |
|
|
Loss |
Specify the loss percentage value. If the loss percentage exceeds the configured value during a one-second interval, a severely errored-second is raised. The Loss percentage is calculated by comparing the total number of packets that were lost with the total number of packets that were sent from the Test Agent. Unit—Percentage (%) Minimum value—0.0 % |
|
Delay |
Specify the maximum acceptable delay. If there is time synchronization, it applies to one-way delay. If there is no time synchronization, it applies to round-trip delay. If delay exceeds the defined value, a severely errored-second is raised. Unit—Milliseconds (ms) Minimum value—0.001 ms |
|
Delay variation |
Specify the maximum tolerated value for delay variance (jitter). If there is time synchronization, it applies to one-way delay. If there is no time synchronization, it applies to round-trip delay. If delay exceeds the defined value, a severely errored-second is raised. Unit—Milliseconds (ms) Minimum value—0.001 ms |
|
ADVANCED |
|
| Frame Size |
Specify the size of Layer 2 Ethernet frame size for the TWAMP test traffic. Frame Size indicates the total size of the data frame sent from the Test Agent to the remote endpoint. The size also includes the header size. Unit—Bytes Default value—1518 Range—87 through 9018 |
| DSCP |
Specify the Differentiated Services Code Point (DSCP) or IP Precedence value that is used in the IP packet headers. Default value—0 Range—0 through 63 |
| Use random padding |
Enable this to use random numbers or zeroes as padding in a TWAMP packet. By default, the toggle button is enabled. |
|
Socket priority |
Specify the value of SO_PRIORITY parameter of the TWAMP socket. Default value—0 Range—0 through 7 |
|
Socket send buffer size |
Specify the value of SO_PRIORITY parameter of the TWAMP socket. Unit—Bytes Range—2048 through 10000000 bytes |
|
Socket receive buffer size |
Specify the value of SO_PRIORITY parameter of the TWAMP socket. Unit—Bytes Range—2048 through 10000000 bytes |
|
Don't fragment flag |
Enable the Don’t Fragment Flag (DF Flag) to restrict the fragmentation of the packets that exceed the MTU. DF Flag is configured in an IP header. Router drops the packet if fragmentation is needed. Enabling this option may cause performance degradation both in the network and in the sending or receiving Test Agents. By default, the toggle button is enabled. |
|
UAS period length |
Specify the minimum value for the consecutive severely errored-seconds (SES) that causes a period of unavailability. The Unavailable Seconds (UAS) metric determines the number of seconds at which the service can be considered to be unavailable. Unit—Seconds (s) Default value—10 s Range—0 s through 300 s |
| Accept UDP checksum zero for IPv6 |
Enable Accept UDP Checksum Zero for IPv6 to accept the UDP Checksum as Zero for IPv6 in TWAMP Reflector packets. By default, the toggle button is enabled. |
|
PERCENTILES |
|
|
First delay percentile |
Specify the first delay percentile of the value of the TWAMP request packet. If the delay exceeds the configured value, the packet is included in the defined first delay percentile slot. Unit—Percentage (%) Range—0 % through 1 % |
|
Second delay percentile |
Specify the second delay percentile of the value of the TWAMP request packet. If the delay exceeds the configured value, the packet is included in the defined second delay percentile slot. Unit—Percentage (%) Range—0 % through 1 % |
|
Threshold for first delay percentile |
Specify the threshold for triggering an errored second based on the first delay percentile. Unit—Milliseconds (ms). Range—0.001 ms through 1000.00 ms |
|
Threshold for second delay percentile |
Specify the threshold for triggering an errored second based on the second delay percentile. Unit—Milliseconds (ms). Range—0.001 ms through 1000.00 ms |
|
SES threshold for first delay percentile |
Specify the threshold for triggering a severely errored second based on the first delay percentile. Unit—Milliseconds (ms). Range—0.001 ms through 1000.00 ms |
|
SES threshold for second delay percentile |
Specify the threshold for triggering a severely errored second based on the second delay percentile. Unit—Milliseconds (ms). Range—0.001 ms through 1000.00 ms |
|
PERIODIC STREAMS |
|
|
Active period duration |
Specify the time duration of each cycle during which ethernet frames are sent. Active period is followed by a silent period during which no ethernet frames are sent. Unit—Milliseconds (ms) Range—1 ms to 3600000 ms |
|
Active cycle |
Specify the time duration of the cycle starting with an active period and ending with a silent period. The Active cycle duration must be at least equal to the active period duration. Unit—Milliseconds (ms) Range—1 ms to 604800 ms |
|
Report metrics during inactive period |
Enable the toggle button to report metrics related to inactive periods of a periodic Test. By default, the toggle button is enabled. |
| Metric | Description |
|---|---|
|
Rate |
Rate indicates the rate at which sender Test Agent receives response packets from the TWAMP reflector in a selected interval of time. The rate is calculated as the size of the response received divided by the total response time. The rate is calculated in Megabits Per Second. |
|
Minimum round trip time |
Minimum round-trip delay of all the requests in the result interval. Round-trip time indicates the duration from when a test packet is sent from a Test Agent until the packet is reflected back and received again on the Test Agent. Time spent in the reflector is not included. The time is calculated in milliseconds. |
|
Average round trip time |
Average round-trip delay of all the requests in the result interval. Round-trip time indicates the duration from when a test packet is sent from a Test Agent until the packet is reflected and received again on the Test Agent. Time spent in the reflector is not included. The time is calculated in milliseconds. |
|
Maximum round trip time |
Maximum round-trip delay of all the requests in the result interval. Round-trip time indicates the duration from when the test packet is sent from a Test Agent until the packet is reflected and received again on the Test Agent. Time spent in the reflector is not included. The time is calculated in milliseconds. |
|
Round trip time DV |
Average round-trip delay variance in result interval. Round-trip delay variance is the difference in round-trip time between the packets with the longest and the shortest round-trip time. The Round trip time DV is calculated in milliseconds. |
|
Received Packets |
Received packets indicates the total number of packets received by Test Agent from the reflector. |
|
Far-end loss |
Far-end loss indicates the percentage of packets lost between Test Agent and the Reflector. It is the percentage of packets that were lost before reaching the reflector. |
|
Far-end lost |
Far-end lost indicates the number of packets lost before reaching the reflector. |
|
Far-end misorders |
Far-end misorders indicate the number of packets sent by Test Agent that reached the reflector out of sequence compared to their original order of transmission. |
|
Minimum far-end delay |
Minimum one-way far-end delay indicates the minimum delay measured for a packet to travel from Test Agent to the Reflector. The delay is calculated in milliseconds. |
|
Average far-end delay |
Average one-way far-end delay indicates the average delay measured for a packet to travel from Test Agent to the Reflector. The delay is calculated in milliseconds. |
|
Maximum far-end delay |
Maximum one-way far-end delay indicates the average delay measured for a packet to travel from Test Agent to the Reflector. The delay is calculated in milliseconds. |
|
Far-end DV |
Far-end DV indicates the delay variance measured at the remote endpoint. It is the difference between the maximum and minimum one-way far-end delay. The delay is calculated in milliseconds. |
|
Near-end loss |
Near-end loss indicates the percentage of packets lost between the Reflector and Test Agent. It is the percentage of packets that were lost before reaching the Test Agent. |
|
Near-end lost |
Near-end lost indicates the number of packets lost between the Reflector and Test Agent. It is the number of packets that were lost before reaching the Test Agent. |
|
Near-end misorders |
Near-end misorders indicates the number of packets that reached Test Agent out of sequence compared to their original order of transmission. |
|
Minimum near-end delay |
Minimum one-way near-end delay indicates the minimum delay experienced by a packet to travel from the Reflector to Test Agent. The delay is calculated in milliseconds. |
|
Average near-end delay |
Average one-way near-end delay indicates the average delay experienced by a packet to travel from the Reflector to Test Agent. The delay is calculated in milliseconds. |
|
Maximum near-end delay |
Maximum one-way near-end delay indicates the maximum delay experienced by a packet to travel from the Reflector to Test Agent. The delay is calculated in milliseconds. |
|
Near-end DV |
Near-end DV indicates the delay variance measured at Test Agent endpoint. It is the difference between the maximum and minimum one-way near-end delay. The delay is calculated in milliseconds. |
|
ES |
ES is the number of seconds during which error-second thresholds were violated. It is the total number of errored-seconds raised. The ES is calculated in milliseconds. |
|
ES delay |
ES delay is the number of errored-seconds raised when Test Agent measures a delay greater than the configured delay threshold. The ES delay is calculated in milliseconds. |
| ES loss |
ES loss is the number of errored-seconds raised when the measured loss is greater than the configured loss threshold. The ES loss is calculated in milliseconds. |
| ES delay variance (DV) |
ES delay variance is the number of errored-seconds raised when the measured delay variance is greater than the configured DV threshold. The ES delay variance is calculated in milliseconds. |
|
ES DSCP |
ES DSCP is the number of errored-seconds occurred when the received DSCP value does not match the expected value. |
|
SES |
Severely errored second (SES) indicates the number of seconds that a SES threshold has been violated. |
|
First round trip delay percentile |
First round trip delay percentile. If the delay exceeds the configured value, the packet is included in the defined first delay percentile slot. |
|
Second round trip delay percentile |
Second round trip delay percentile. If the delay exceeds the configured value, the packet is included in the defined second delay percentile slot. |
|
First far end round trip delay percentile |
First far end round trip delay percentile. If the delay exceeds the configured value, the packet is included in the defined first far end round trip delay percentile slot. |
|
Second far end round trip delay percentile |
Second far end round trip delay percentile. If the delay exceeds the configured value, the packet is included in the defined second far end round trip delay percentile slot. |
|
First near end round trip delay percentile |
First near end round trip delay percentile. If the delay exceeds the configured value, the packet is included in the defined first near end round trip delay percentile slot. |
|
Second near end round trip delay percentile |
Second near end round trip delay percentile. If the delay exceeds the configured value, the packet is included in the defined second near end round trip delay percentile slot. |
|
ES for first round trip delay percentile |
ES for first round trip delay percentile. If the delay exceeds the configured value, the packet is included in the defined first round trip delay percentile slot and an errored-second is raised. |
|
ES for second round trip delay percentile |
ES for second round trip delay percentile. If the delay exceeds the configured value, the packet is included in the defined second round trip delay percentile slot and an errored-second is raised. |
|
Round trip loss |
Round-trip loss indicates the percentage of TWAMP packets sent from Test Agent that were lost either on the way to the reflector or on the way back to Test Agent. The loss percentage is calculated by comparing the total packets lost with the total number of packets sent. |
|
Round trip lost |
Round-trip lost indicates the number of TWAMP packets sent from Test Agent that were lost either on the way to the reflector or on the way back to Test Agent. |
|
Timestamp samples |
The number of valid timestamp samples used in delay measurements. |
UDP
The UDP measurement is used to evaluate the network quality for client-server applications and video conferencing. Running a UDP measurement measures one-way delay, jitter, packet loss, and misorders of packets. When a UDP measurement starts, the client Test Agents send packets that include timestamps and sequence numbers to the server Test Agents at the rate you specify. In this way, the server Test Agent can calculate one-way delay, jitter, and packet loss.
| Parameter | Description |
|---|---|
| GENERAL | |
| Clients* |
Select one or more Test Agent interfaces on which you want to run measurements by using this Plug-in. A separate measurement will be run on each interface you select. For more information, see Client Configuration for Plug-ins. |
|
Server* |
Select one or more Test Agent interfaces on which you want to run measurements by using this Plug-in. A separate measurement will be run on each interface you select. For more information, see Client Configuration for Plug-ins. |
|
Direction |
Choose the direction of the test traffic. The data is sent from 'Server to Client' or 'Client to Server'. Client to server—Evaluates the data upload capabilities. Server to client—Evaluates the data download capabilities. |
|
Rate (Mbit/s) |
Specify the target data rate at which the client or server Test Agent transmits the UDP frames. Unit—Megabit per second (Mbit/s) Range—0.01 Mbit/s through 1000000.0 Mbit/s |
|
ADVANCED |
|
|
Server UDP port |
Specify the port number of the UDP server to which the client Test Agent form a connection. Default value—5000 Range—1 through 65535 |
|
Client TCP port |
Specify the port number of the UDP server to which the client Test Agent form a connection. Range—1 through 65535 |
|
Number of flows |
Specify the total number of UDP connections established between the client and server Test Agents. If more than one flows are specified, you should not set the Client port. If set, the Plug-in activates an invalid configuration error, and if not set, the Client port gets a randomly assigned port number. Default value—1 Range—1 through 64 |
|
Don't Fragment flag |
Enable the Don’t Fragment Flag (DF Flag) to restrict the fragmentation of the packets that exceed the MTU. DF Flag is configured in an IP header. Router drops the packet if fragmentation is needed. Enabling the toggle button may cause performance degradation both in the network and in the sending or receiving Test Agents. By default, the toggle button is disabled. |
|
Ethernet frame size (Bytes) |
Specify the size of Layer 2 Ethernet frame for the data flow. Frame Size indicates the total size of the data frame sent from a remote endpoint to the Test agent as a response to a request. Default—1518 Range—64 bytes through 9018 bytes |
|
DSCP/IPP |
Specify the Differentiated Services Code Point (DSCP) or the IP Precedence (IPP) value that is used in the IP packet headers. DSCP is a six-bit binary value in the DS field of the IP header. DSCP value facilitates QoS for traffic management through the Best Effort, Assured Forwarding, Class Selector, and the Expedited Forwarding categories. See RFC 2474 for more information. Default value—0 Range—0 through 63 |
|
VLAN priority (PCP) |
Specify the value for the VLAN priority code point to be used in VLAN header. Range—0 through 7 |
|
THRESHOLDS FOR ERRORED SECONDS (ES) |
|
|
Loss (%) |
Specify the loss percentage value. If the loss percentage exceeds the configured value, an errored-second is triggered. Unit—Percentage (%) Range—0.0% through 100.0% |
|
Delay (ms) |
Specify the threshold value for the minimum delay measured between the Test Agent client and server. If delay exceeds the defined value, an errored-seconds is raised. Unit—Milliseconds (ms) Minimum—0.0 ms |
|
Jitter (ms) |
Specify the maximum threshold value for delay variance (jitter) in UDP transaction. Delay variation (DV) occurs when different packets take different amount of time to travel from a Test Agent to a remote endpoint. Unit—Milliseconds (ms) Minimum—0.0 ms |
|
Expected DSCP |
Specify the expected DSCP that must be in the frame when received by Test Agent. If the received DSCP value does not match the configured value, an errored-second is raised. Range—0 through 64 |
|
THRESHOLDS FOR SEVERELY ERRORED SECONDS (ES) |
|
|
Loss (%) |
Specify the maximum allowable loss percentage value. If the loss percentage exceeds the configured value, an errored-second is raised. Unit—Percentage (%) Range—0.0% through 100.0% |
|
Delay (ms) |
Specify the maximum allowable value for delay measurement. If the delay between server and client exceeds the configured value during a one-second interval, a severely-error seconds is indicated. Unit—Milliseconds (ms) Minimum—0.0 ms |
|
Jitter (ms) |
Specify the maximum threshold value for delay variance (jitter). Packets are sent at regular interval of time and if variation is experienced in consecutive packets, the Test Agent generates an errored-second event. Unit—Milliseconds (ms) Minimum—0.0 ms |
| Metric | Description |
|---|---|
| Misordered packets |
Misordered packets indicates the total number of packets received by the Test Agent in a different order than they were sent. |
| Rate |
Rate indicates the speed or throughput at which Test Agent receives the UDP packets in a selected interval. The rate is displayed in Megabits Per Second. |
| ES |
ES is the number of seconds during which errors occurred in a specific duration of time. ES is an aggregate of all the specific ES metrics. |
| ES Rate |
ES Rate is the number of errored-seconds occurred when the rate at which the UDP packet reception drops below the defined value. The rate is displayed in milliseconds. |
| ES Loss |
ES loss is the number of errored-seconds raised when measured packet loss exceeds the defined loss value. |
| ES Delay |
ES Delay is the number of errored-seconds raised when the measured one-way delay exceeds the defined delay value. The ES delay is displayed in milliseconds. |
| ES DSCP | ES DSCP is the number of errored-seconds occurred when the DSCP marked packets experience loss, delay, delay variance, or configuration issues. |
| SES |
Severely errored second (SES) indicates the interval of time during which any of the defined SES thresholds were violated. |
| UAS |
The Unavailable Seconds (UAS) metric indicates the number of seconds at which the service can be considered to be unavailable. |
| Average delay |
Average delay indicates the average delay experienced by data packets in the UDP measurement. The average delay is displayed in milliseconds. |
| Minimum delay |
Minimum delay indicates the minimum delay experienced by data packets in a UDP measurement. The minimum delay is displayed in milliseconds. |
| Maximum delay |
Average delay indicates the average delay experienced by data packets in the UDP measurement. The maximum delay is displayed in milliseconds. |
| Jitter |
Jitter is the difference between maximum and minimum one-way delay measured during a result interval. The jitter is displayed in milliseconds. |
| Number of packets in the interval |
Number of packets in the interval. |
| Percentage of packets lost |
Loss percentage indicates the percentage of packets sent from the Test Agent that were lost before reaching the receiving Test Agent. |
| Lost Packet count |
Lost indicates the number of packets sent from the Test Agent that were lost before reaching the receiving Test Agent. |