Rate and give feedback:  Feedback Received. Thank You!

Rate and give feedback: 

X

This document helped resolve my issue

Yes No

Additional Comments

800 characters remaining

May we contact you if necessary?

Name:  

E-mail: 

Enter a valid Email ID

Need product assistance? Contact Juniper Support

Submit

This site is protected by hCaptcha and its Privacy Policy and Terms of Service apply.

English  

English

Configuring the Interface for RPM Timestamping for Client/Server on an EX Series Switch (CLI Procedure)

Use real-time performance monitoring (RPM) to configure active probes to track and monitor traffic across the network and to investigate network problems. To configure basic RPM probes on the EX Series switch, you must configure the probe owner, the test, and the specific parameters of the RPM probe.

You can also set a timestamp to improve the measurement of latency or jitter. The probe is timestamped by the device originating the probe (the RPM client). If you do not enable hardware timestamps, the timer values are set. You should configure both the RPM client (the requester) and the RPM server (the responder) to timestamp the RPM packets. However, if the RPM server does not support hardware timestamps, RPM can only report the round-trip measurements.

Timestamps apply only to IPv4 traffic.

You can enable hardware timestamps for the following RPM probe types:

• icmp-ping
• icmp-ping-timestamp
• udp-ping
• udp-ping-timestamp

1. Specify the probe owner:
   [edit services rpm]
user@switch# set probe owner
2. Specify a test name. A test represents the range of probes over which the standard deviation, average, and jitter are calculated.
   [edit services rpm probe owner]
user@switch# set test test-name
3. Specify the packet and protocol contents of the probe:
   [edit services rpm probe owner test test-name]
user@switch# set probe-type type
4. Specify the destination IPv4 address to be used for the probes:
   [edit services rpm probe owner test test-name]
user@switch# set target address
5. Specify the number of probes within a test:
   [edit services rpm probe owner test test-name]
user@switch# set probe-count count
6. Specify the time, in seconds, to wait between sending packets:
   [edit services rpm probe owner test test-name]
user@switch# set probe-interval interval
7. Specify the time, in seconds, to wait between tests:
   [edit services rpm probe owner test test-name]
user@switch# set test-interval interval
8. Specify the source IP address to be used for probes. If the source IP address is not one of the switch’s assigned addresses, the packet uses the outgoing interface’s address as its source.
   [edit services rpm probe owner test test-name]
user@switch# set source-address address
9. Specify the value of the Differentiated Services (DiffServ) field within the IP header. The DiffServ code point (DSCP) bits value must be set to a valid 6-bit pattern.
   [edit services rpm probe owner test test-name]
user@switch# set dscp-code-point dscp-bits
10. If you are using ICMP probes, specify the size of the data portion of ICMP probes:
    [edit services rpm probe owner test test-name]
user@switch# set data-size size
11. Enable hardware timestamping of RPM probe messages:
    [edit services rpm probe owner test test-name]
user@switch# set hardware-timestamp