ip-monitoring (Services)
Syntax
ip-monitoring {
policy policy-name {
match {
rpm-probe [probe-name];
}
no-preempt ;
then {
interface interface-name (disable | enable);
preferred-route {
withdraw;
route destination-address {
direct-next-hop
discard
next hop next-hop;
preferred-metric metric;
}
routing-instances name;
}
}
}
traceoptions {
file {
filename;
files number;
match regular-expression;
size maximum-file-size;
(world-readable | no-world-readable);
}
flag flag;
no-remote-trace;
}
}
Hierarchy Level
[edit services]
Description
Enabling tracing can adversely impact scale and performance and may increase security risk. We strongly recommend using the trace, tracing, or traceoptions commands only under the guidance of a JTAC support engineer. After collecting the debug information, immediately disable tracing to minimize risk and restore normal system performance.
Configure IP monitoring.
Options
withdraw—Remove the primary routes when RPM
fails to probe the destination. So, the traffic can choose other routes
in the route table. If no other route exists, then the traffic is
dropped. When you run the show services ip-monitoring status command, in the output, the status of the route WITHDRAWED indicates that this route is removed. See show services ip-monitoring status for more details.
direct-next-hop-This configuration requests the next
hop, which must be direct. This configuration ignores the other kind
of hops.
The remaining statements are explained separately. See CLI Explorer.
Required Privilege Level
services—To view this statement in the configuration.
services-control—To add this statement to the configuration.
Release Information
Statement introduced in Junos OS Release 10.4.
Support added for the discard option starting from
Junos OS Release 15.1X49-D60.
Support added for the withdraw option starting from
Junos OS Release 20.3R1.
direct-next-hop is introduced in Junos OS Release
20.4R1.