Example: Configuring RPM Using TCP and UDP Probes

This example shows how to configure RPM using TCP and UDP probes.

Requirements

Before you begin:

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.

{device A}set services rpm probe customerC test tcp-test probe-interval 5set services rpm probe customerC test tcp-test probe-type tcp-ping set services rpm probe customerC test tcp-test target address 192.162.45.6 set services rpm probe customerC test tcp-test destination-interface lt-0/0/0 set services rpm probe customerC test tcp-test destination-port 50000
{device B}set services rpm probe-server tcp port 50000 set services rpm probe-server udp port 50037

Step-by-Step Procedure

The following example requires you to navigate various levels in the configuration hierarchy. For instructions on how to do that, see Using the CLI Editor in Configuration Mode in the Junos OS CLI User Guide PDF Document.

To configure RPM using TCP and UDP probes:

  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.

[edit]user@host# show services rpmprobe customerC {test tcp-test {probe-type tcp-ping;target address 192.162.45.6;probe-interval 5;destination-port 50000;destination-interface lt-0/0/0.0;}}probe-server {tcp {port 50000;}udp {port 50037;}}

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

Verification

Confirm that the configuration is working properly.

Verifying RPM Probe Servers

Purpose

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.

user@host> show services rpm active-servers
    Protocol: TCP, Port: 50000

    Protocol: UDP, Port: 50037

Related Documentation