Supported Platforms
Related Documentation
Configuring Real-Time Performance Monitoring (J-Web Procedure)
Real-time performance monitoring (RPM) in EX Series switches enables you to configure and send probes to a specified target and monitor the analyzed results to determine packet loss, round-trip time, and jitter. Jitter is the difference in relative transit time between two consecutive probes. You can set up probe owners and configure one or more performance probe tests under each probe owner.
The ways in which you can use RPM include:
- Monitor time delays between devices.
- Monitor time delays at the protocol level.
- Set thresholds to trigger SNMP traps when threshold values are exceeded. You can configure thresholds for round-trip time, ingress or egress delay, standard deviation, jitter, successive lost probes, and total lost probes per test.
- Determine automatically whether a path exists between a host switch and its configured Border Gateway Protocol (BGP) neighbors. You can view the results of the discovery using an SNMP client.
- Use the history of the most recent 50 probes to analyze trends in your network and predict future needs.
Probes collect packets per destination and per application, including PING Internet Control Message Protocol (ICMP) packets, User Datagram Protocol and Transmission Control Protocol (UDP/TCP) packets with user-configured ports, user-configured Differentiated Services code point (DSCP) type-of-service (ToS) packets, and Hypertext Transfer Protocol (HTTP) packets.
EX Series switches support the following tests and probe types:
- Ping tests:
- ICMP echo
- ICMP timestamp
- HTTP tests:
- HTTP get (not available for BGP RPM services)
- UDP and TCP tests with user-configured ports:
- UDP echo
- TCP connection
- UDP timestamp
To account for latency in the communication of probe messages, you can enable timestamping of the probe packets. You must configure both the requester and the responder to timestamp the RPM packets. The RPM features provides an additional configuration option to set one-way hardware timestamps. Use one-way timestamps when you want information about one-way, rather than round-trip, times for packets to traverse the network between the requester and the responder.
![]() | Note:
|
To configure RPM using the J-Web interface:
- Select Troubleshoot > RPM > Configure RPM .
- In the Configure RPM page, enter information
as specified in Table 1.
- Click Add to set up the Owner Name and Performance Probe Tests.
- Select a probe owner from Probe Owners list and click Delete to remove the selected probe owner
- Double-click one of the probe owners in Probe Owners list to display the list of performance probe tests.
- Double-click one of the performance probe tests to edit the test parameters.
- Enter the Maximum Number of Concurrent Probes and specify the Probe Servers.
- Click Apply to apply the RPM probe settings.
Table 1: RPM Probe Owner, Concurrent Probes, and Probe Servers Configuration Fields
Field | Function | Your Action |
---|---|---|
Probe Owners | Identifies a owner for whom one or more RPM tests are configured. In most implementations, the owner name identifies a network on which a set of tests is being run. |
|
Maximum Number of Concurrent Probes | Specifies the maximum number of concurrent probes allowed. | Type a number from 1 through 500. |
Probe Servers | Specifies the servers that act as receivers and transmitters for the probes. | Set up the following servers:
|
Table 2: Performance Probe Tests Configuration Fields
Field | Function | Your Action |
---|---|---|
Identification | ||
Test Name | Identifies the RPM test. | Type a test name. |
Target (Address or URL) | Specifies the IP address or the URL of the probe target. | Type the IP address in dotted decimal notation or the URL of the probe target. If the target is a URL, type a fully formed URL that includes http://. |
Source Address | Specifies the IP address to be used as the probe source address. | Type the source address to be used for the probe. If you do not supply this value, the packet uses the outgoing interface's address as the probe source address. |
Routing Instance | Specifies the routing instance over which the probe is sent. | Type the routing instance name. The routing instance applies only to icmp-ping and icmp-ping-timestamp probe types. The default routing instance is inet.0. |
History Size | Specifies the number of probe results to be saved in the probe history. | Type a number from 0 through 255. The default history size is 50. |
Request Information | ||
Probe Type | Specifies the type of probe to send as part of the test. | Select a probe type from the list:
|
Interval | Sets the wait time (in seconds) between probe transmissions. | Type a number from 1 through 255 . |
Test Interval | Sets the wait time (in seconds) between tests. | Type a number from 0 through 86400 . |
Probe Count | Sets the total number of probes to be sent for each test. | Type a number from 1 through 15. |
Moving Average Size | Specifies the number of samples to be used in the statistical calculation operations to be performed across a number of the most recent samples. | Type a number from 0 through 255. |
Destination Port | Specifies the TCP or UDP port to which probes are sent. To use TCP or UDP probes, you must configure the remote server as a probe receiver. Both the probe server and the remote server must be Juniper Networks network devices configured to receive and transmit RPM probes on the same TCP or UDP port. | Type the number 7 (a standard TCP or UDP port number) or a port number from 49160 through 65535. |
DSCP Bits | Specifies the Differentiated Services code point (DSCP) bits. This value must be a valid 6-bit pattern. | Type a valid 6-bit pattern. |
Data Size | Specifies the size (in bytes) of the data portion of the ICMP probes. | Type a number from 0 through 65507. |
Data Fill | Specifies the hexadecimal value of the data portion of the ICMP probes. | Type a hexadecimal value from 1h through 800h . |
Hardware Timestamp | ||
One Way Hardware Timestamp | Enables one-way hardware timestamp. | To enable timestamping, select the check box. |
Destination Interface | Enables hardware timestamp on the specified interface. | Select an interface from the list. |
Maximum Probe Thresholds | ||
Successive Lost Probes | Sets the number of probes that can be lost successively, if exceeded, triggers a probe failure and generates a system log message. | Type a number from 0 through 15. |
Lost Probes | Sets the number of probes that can be lost , if exceeded, triggers a probe failure and generates a system log message. | Type a number from 0 through 15. |
Round Trip Time | Sets the round-trip time (in microseconds), from the switch to the remote server, if exceeded, triggers a probe failure and generates a system log message. | Type a number from 0 through 60000000. |
Jitter | Sets the jitter (in microseconds), if exceeded, triggers a probe failure and generates a system log message. | Type a number from 0 through 60000000. |
Standard Deviation | Sets the maximum allowable standard deviation (in microseconds), if exceeded, triggers a probe failure and generates a system log message. | Type a number from 0 through 60000000. |
Egress Time | Sets the one-way time (in microseconds), from the switch to the remote server, if exceeded, triggers a probe failure and generates a system log message. | Type a number from 0 through 60000000. |
Ingress Time | Sets the one-way time (in microseconds), from the remote server to the switch, if exceeded, triggers a probe failure and generates a system log message. | Type a number from 0 through 60000000 (microseconds). |
Jitter Egress Time | Sets the outbound-time jitter (in microseconds), if exceeded triggers a probe failure and generates a system log message. | Type a number from 0 through 60000000. |
Jitter Ingress Time | Sets the inbound-time jitter (in microseconds), if exceeded, triggers a probe failure and generates a system log message. | Type a number from 0 and 60000000. |
Egress Standard Deviation | Sets the maximum allowable standard deviation of outbound times (in microseconds), if exceeded, triggers a probe failure and generates a system log message. | Type a number from 0 through 60000000. |
Ingress Standard Deviation | Sets the maximum allowable standard deviation of inbound times (in microseconds), if exceeded, triggers a probe failure and generates a system log message. | Type a number from 0 through 60000000. |
Traps | ||
Egress Jitter Exceeded | Generates SNMP traps when the threshold for jitter in outbound time is exceeded. |
|
Egress Standard Deviation Exceeded | Generates SNMP traps when the threshold for standard deviation in outbound times is exceeded. |
|
Egress Time Exceeded | Generates SNMP traps when the threshold for maximum outbound time is exceeded. |
|
Ingress Jitter Exceeded | Generates SNMP traps when the threshold for jitter in inbound time is exceeded. |
|
Ingress Standard Deviation Exceeded | Generates SNMP traps when the threshold for standard deviation in inbound times is exceeded. |
|
Ingress Time Exceeded | Generates SNMP traps when the threshold for maximum inbound time is exceeded. |
|
Jitter Exceeded | Generates SNMP traps when the threshold for jitter in round-trip time is exceeded. |
|
Probe Failure | Generates SNMP traps when the threshold for the number of successive lost probes is exceeded. |
|
RTT Exceeded | Generates SNMP traps when the threshold for maximum round-trip time is exceeded. |
|
Standard Deviation Exceeded | Generates SNMP traps when the threshold for standard deviation in round-trip times is exceeded. |
|
Test Completion | Generates SNMP traps when a test is completed. |
|
Test Failure | Generates SNMP traps when the threshold for the total number of lost probes is exceeded. |
|