The picture shows configurable multicast generation by a server Test Agent, joined by two client Test Agents.
Multicast is commonly used as a transport mechanism for services like IPTV, and for updating many PCs at the same time. By running a Multicast UDP test, you will learn how well your network handles multicast traffic in terms of end-to-end delay, jitter, and packet loss.
When you start a Multicast UDP test, the Netrounds server Test Agent will start generating traffic towards the destination multicast address you have specified. Then the clients will try to join that multicast address, and if successful, calculate one-way delay, jitter, packet loss, and packet misorderings for the received stream.
Client Test Agents can be placed behind NAT, since traffic will be initiated from the clients to the server.
To run Multicast UDP measurements you need to have at least two Netrounds Test Agents installed. If you haven't already done the installation, consult our quick start guides for various types of Test Agents in the section Netrounds Test Agents.
Then create a new Multicast UDP test or monitoring and fill in the mandatory parameters below:
- Duration (seconds): The duration of this test step in seconds. Min: 30 s. Max: 604800 s. Default: 60 s.
- Fail threshold (seconds): The maximum number of errored seconds (ES) that may occur without triggering a fail for this test step. Default: 0.
- Wait for ready: Time to wait before starting the test. The purpose of inserting a wait is to allow all Test Agents time to come online and acquire good time sync. Min: 1 min. Max: 24 hours. Default: "Don't wait", i.e. zero wait time.
- Server: A Netrounds Test Agent that should generate multicast traffic.
- Clients: Netrounds Test Agents that should join the multicast traffic sent by the server.
- Rate (Mbit/s): Bit rate of the multicast stream in Mbit/s.
- Multicast address: The multicast address to use.
- Port: UDP destination port of the multicast stream.
Thresholds for errored seconds (ES)
- Loss (%): Packet loss threshold for triggering an errored second. If the loss exceeds this value during one second, an ES will be indicated by Netrounds. Default: 0%.
- Delay (ms): One-way delay threshold for triggering an errored second. If the delay from server to clients exceeds this value during one second, an ES will be indicated by Netrounds. No default.
- Jitter (ms): Jitter (delay variation) threshold for triggering an errored second. If the jitter from server to clients exceeds this value during one second, an ES will be indicated by Netrounds. No default.
Thresholds for severely errored seconds (SES)
- Loss (%): Packet loss threshold for triggering a severely errored second. No default.
- Delay (ms): One-way delay threshold for triggering a severely errored second. No default.
- Jitter (ms): Jitter (delay variation) threshold for triggering a severely errored second. No default.
- Ethernet frame size (bytes): Packet size for the stream in bytes. Min: 64 bytes for IPv4. (IPv6 is not supported.) Max: The maximum packet size depends on the interface MTU (Maximum Transmission Unit); the default MTU value is 1500 bytes.
- DSCP/IPP: The Differentiated Services Code Point or IP Precedence to be used in IP packet headers. The available choices are listed in the drop-down box. Default: "0 / IPP 0". Note: Test Agents Lite currently do not support DSCP settings in outgoing IP packets.
- VLAN priority (PCP): The Priority Code Point to be used in the VLAN header. Range: 0 ... 7. Default: 0. Note: Test Agents Lite currently do not support PCP settings in outgoing IP packets.
- Delayed start (s): (Tests only) Time by which to delay the start of the test within a test step. Default: 0 s.
SLA thresholds (monitorings only)
- SLA Good: Threshold for good service level agreement. Default 99.95.
- SLA Acceptable: Threshold for acceptable service level agreement. Default 99.5.
- Bandwidth, loss, one-way delay, jitter, ES total, ES loss, ES delay