To configure RPM using TCP and UDP probes, in addition to the basic RPM properties, you must configure both the host device and the remote device to act as TCP and UDP servers.
If you are using class of service (CoS) and want to classify probes, you must also set a destination interface. The destination interface is the output interface for sending packets to the forwarding plane. Classified packets are sent to the output queue on the output interface specified by the CoS scheduler map configured on the interface.
For information about CoS, see the JUNOS Software Interfaces and Routing Configuration Guide.
![]() |
Caution: Use probe classification with caution, because improper configuration can cause packets to be dropped. |
The destination interface must support looping of probe packets to an input interface without adding any encapsulation. The device's destination interface must be an lt services interface.
In this sample use of RPM, a probe is configured for one customer: Customer C. The probe for Customer C uses TCP packets. The remote device is configured as an RPM server for both TCP and UDP packets, using an lt services interface as the destination interface, and ports 50000 and 50037, respectively. Router A is the host device in this example, and Router B is the remote device. To configure this RPM probe:
Table 229: Configuring TCP and UDP Probes