delegate-probes
Syntax
delegate-probes;
Hierarchy Level
[edit services rpm probe owner]
Description
Generate real-time performance monitoring (RPM) probes on an MS-MPC or MS-MIC card, which increases the number of RPM probes that can run at the same time.
To use the delegate-probes
statement, you must first
configure the destination-interface
statement at the [edit services rpm probe owner test test-name]
hierarchy level to point to a valid logical
unit number of a multiservices interface. Then configure the same
unit and multiservice interface with the rpm client-delegate-probes
statement at the [edit interfaces interface-name unit logical-unit-number]
hierarchy level.
The probe-type type
at the [edit services rpm probe owner test test-name]
hierarchy level can be icmp-ping
or icmp-ping-timestamp
starting in Junos OS Release 17.3R1,
and icmp6-ping
starting in Junos OS Release 18.1R1.
To avoid packet bursts in the network due to RPM, probes will be distributed in a better way.
The chances of multiple tests starting and ending at the same
time are smaller. This way RPM syslog bursts and a potential performance
bottleneck in event-processing
are avoided.. This does
not exclude potential syslog drops on the RE if more than 12000 RPM
tests are running simultaneously. For scaled configurations (with
more than 12000 RPM tests) we recommend you to configure syslogs to
sent to an external hosts for offloaded processing.
You cannot configure the routing-instance
statement
at the [edit services rpm probe owner test test-name]
hierarchy level for RMP probes that are
generated on an MS-MPC or MS-MIC card.
Required Privilege Level
interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration.
Release Information
Statement introduced in Junos OS Release 17.3R1.