RPMs (Realtime Performance Monitoring) are like Cisco’s SLA’s. They are probes that check the availability of an endpoint or its services, or link performance.
There can be simple or complicated probes, based on:
Performance monitoring can track metrics such as:
- packet loss
- response time
- round trip time
A simple ICMP probe does not require any special configuration on the target endpoint. Other types of monitoring will require the endpoint to be configured accordingly.
A ‘test’ is a collection of probes. Probes are sent out at regular intervals. When all the probes in a test are complete, the test is finished, and it will repeat.
Route tracking based on RPMs is available on the MX series platform, if its running 18.4 or later. This enables static routes to rely on the successful result of an RPM.
|set services rpm probe OWNER test NAME||Configuration||Create a new RPM test|
|set services rpm probe OWNER test NAME probe-type icmp-ping||Configuration||Create an ICMP probe|
|set services rpm probe OWNER test NAME probe-count||Configuration||Set the number of times a probe will repeat|
|set services rpm probe OWNER test NAME target-address||Configuration||Set the IP of the target|
|show services rpm probe-results||Operational||Verify the results of a probe|
Configuring Basic RPM Probes
Static route tracking with Juniper MX ( rpm-tracking )