Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

 

Understanding Using Probes for Real-Time Performance Monitoring on M, T, PTX, and MX Series Routers

 

Real-time performance monitoring (RPM) enables you to configure active probes to track and monitor traffic. 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. RPM provides Management Information Base (MIB) support with extensions for RFC 2925, Definitions of Managed Objects for Remote Ping, Traceroute, and Lookup Operations.

Starting in Junos OS Release 17.3R1, you can apply RPM to IPsec tunnels and GRE tunnels for PIC-based and Routing Engine-based RPM clients and servers if you are using MS-MPCs or MS-MICs. Packet Forwarding Engine-based RPM is not supported for IPsec tunnels. Support of RPM on IPSec tunnels enables service level agreement (SLA) monitoring for traffic transported in IPSec tunnels.

Starting in Junos OS Release 19.1R1, PTX Series routers support timestamping of RPM probe messages on the Packet Forwarding Engine.

Starting in Junos OS Release 19.2R1, you can enable timestamps on RPM probe messages in the Packet Forwarding Engine host processor for the MPC10E-15C-MRATE line card on MX240, MX480, and MX960 routers, and on the MPC11E line card on the MX2008, MX2010, and MX2020 routers.

Note

RPM is not supported on logical systems.

Note

RPM is not supported when you enable Next Gen Services on an MX Series router.

Starting in Junos OS Evolved Release 20.1R1, you can configure RPM probes. For Junos OS Evolved, RPM is configured at the [edit services monitoring rpm] hierarchy level. The scope of support is limited to:

  • Probe generation and reception (client) as well as reflection (server) for the following RPM probe types:

    • icmp-ping

    • icmp-timestamp

    • udp-ping

    • udp-timestamp

  • Probe history management

  • Reporting through syslog only

In Junos OS, you can also configure RPM services to determine automatically whether a path exists between a host router and its configured BGP neighbors. You can view the results of the discovery using an SNMP client. Results are stored in pingResultsTable, jnxPingResultsTable, jnxPingProbeHistoryTable, and pingProbeHistoryTable.

In Junos OS, probe configuration and probe results are supported by both the command-line interface (CLI) and SNMP.

The following probe types are supported with DSCP marking:

  • HTTP get (not available for BGP RPM services)

  • ICMP echo

  • ICMP timestamp

  • TCP connection

  • UDP echo

  • UDP timestamp

With probes, you can monitor:

  • Average round-trip time

  • Jitter of the round-trip time—The difference between the minimum and maximum round-trip time

  • Maximum round-trip time

  • Minimum round-trip time

  • Standard deviation of the round-trip time (Junos OS only)

One-way measurements for ICMP timestamp probes include:

  • Minimum, maximum, standard deviation, and jitter measurements for egress and ingress times

  • Number of probe responses received

  • Number of probes sent

  • Percentage of lost probes

You can configure the following RPM thresholds:

  • Ingress/egress delay

  • Jitter

  • Round-trip time

  • Standard deviation (Junos OS only)

  • Successive lost probes

  • Total lost probes (per test)

You can also configure CoS classifiers and prioritization of RPM packets over regular data packets received on an input interface with the dscp-code-points configuration statement.

Table 1 provides information about RPM and related timestamp support on MPC, MS-MIC/MPC, and Routing Engine:

Table 1: RPM and related timestamp support

Feature

Role

IP Version

Support (Y/N)

Timestamp on Routing Engine

Timestamp on MPC (hardware-timestamp)

Timestamp on MPC (si-interface)

Timestamp on MS-MIC/MPC (delegate-probes)

RPM

Client

IPv4

Y

Y (µsec)

2000 maximum probes

Y (µsec)

2000 maximum probes

N

Y (msec)

1 million maximum probes

IPv6

Y

Y (µsec)

2000 maximum probes

N

N

Y (msec)

1 million maximum probes

Server

IPv4

Y

Y (µsec)

2000 maximum probes

Y (µsec)

2000 maximum probes

N

Y (msec)

1 million maximum probes

IPv6

Y

Y (µsec)

2000 maximum probes

N

N

Y (msec)

1 million maximum probes

Release History Table
Release
Description
Starting in Junos OS Evolved Release 20.1R1, you can configure RPM probes. For Junos OS Evolved, RPM is configured at the [edit services monitoring rpm] hierarchy level.
RPM is not supported when you enable Next Gen Services on an MX Series router.
Starting in Junos OS Release 19.2R1, you can enable timestamps on RPM probe messages in the Packet Forwarding Engine host processor for the MPC10E-15C-MRATE line card on MX240, MX480, and MX960 routers, and on the MPC11E line card on the MX2008, MX2010, and MX2020 routers.
Starting in Junos OS Release 19.1R1, PTX Series routers support timestamping of RPM probe messages on the Packet Forwarding Engine.
Starting in Junos OS Release 17.3R1, you can apply RPM to IPsec tunnels and GRE tunnels for PIC-based and Routing Engine-based RPM clients and servers if you are using MS-MPCs or MS-MICs.