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.

Note

RPM is not supported on logical systems.

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.

Probe configuration and probe results are supported by 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

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

Note

Timestamping is not supported on PTX Series Packet Transport routers.

You can configure the following RPM thresholds:

  • Ingress/egress delay

  • Jitter

  • Round-trip time

  • Standard deviation

  • Successive lost probes

  • Total lost probes (per test)

Support is also implemented for user-configured CoS classifiers and for prioritization of RPM packets over regular data packets received on an input interface.

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 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.