Rate and give feedback:  Feedback Received. Thank You!

Rate and give feedback: 

X

This document helped resolve my issue

Yes No

Additional Comments

800 characters remaining

May we contact you if necessary?

Name:  

E-mail: 

Enter a valid Email ID

Need product assistance? Contact Juniper Support

Submit

This site is protected by hCaptcha and its Privacy Policy and Terms of Service apply.

English  

English

Example: Configuring RPM Using TCP and UDP Probes

Requirements

Before you begin:

• Establish basic connectivity. See the Getting Started Guide for your device.
• Configure network interfaces. See Junos OS Interfaces Library for Security Devices.
• Configure the probe owner, the test, and the specific parameters of the RPM probe. See Example: Configuring Basic RPM Probes.

Overview

In this example, you configure both the host (device A) and the remote device (device B) to act as TCP and UDP servers. You configure a probe for customerC, which uses TCP packets. Device B 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.

Caution: Use probe classification with caution, because improper configuration can cause packets to be dropped.

Note: On J Series devices, the destination interface must be an lt services interface.

Configuration

CLI Quick Configuration

To quickly configure this example, copy the following commands, paste them into a text file, remove any line breaks, change any details necessary to match your network configuration, and then copy and paste the commands into the CLI at the [edit] hierarchy level.

Step-by-Step Procedure

1. Configure the RPM owner on device A.
   {device A}[edit]user@host# edit services rpmuser@host# set probe customerC
2. Configure the RPM test.
   {device A}[edit services rpm]user@host# edit services rpm probe customerCuser@host# set test tcp-test probe-interval 5
3. Set the probe type.
   {device A}[edit services rpm probe customerC]user@host# set test tcp-test probe-type tcp-ping
4. Specify the target address.
   {device A}[edit services rpm probe customerC]user@host# set test tcp-test target address 192.162.45.6
5. Configure the destination interface.
   {device A}[edit services rpm probe customerC]user@host# set test tcp-test destination-interface It-0/0/0
6. Configure port 50000 as the TCP port to which the RPM probes are sent.
   {device A}[edit services rpm probe customerC]user@host# set test tcp-test destination-port 50000
7. Configure device B to act as a TCP server using port 50000.
   {device B}[edit]user@host# edit services rpmuser@host# set probe-server tcp port 50000
8. Configure device B to act as a UDP server using port 50037.
   {device B}[edit services rpm]user@host# set probe-server udp port 50037

Results

From configuration mode, confirm your configuration by entering the show services rpm command. If the output does not display the intended configuration, repeat the configuration instructions in this example to correct it.

If you are done configuring the device, enter commit from configuration mode.

Verification

Verifying RPM Probe Servers

Purpose

Confirm that the configuration is working properly.

Verify that the device is configured to receive and transmit TCP and UDP RPM probes on the correct ports.

Action

From configuration mode, enter the show services rpm active-servers command. The output shows a list of the protocols and corresponding ports for which the device is configured as an RPM server.

    Protocol: TCP, Port: 50000

    Protocol: UDP, Port: 50037