Configuring RPM with a Configuration Editor

To configure the device to perform real-time performance tests, you perform the following tasks. For information about using the J-Web and CLI configuration editors, see User Interface Overview.

Configuring Basic RPM Probes

To configure basic RPM probes, you must configure the probe owner, the test, and the specific parameters of the RPM probe.

For ICMP ping, ICMP ping timestamp, UDP ping, and UDP ping timestamp probes, you can also set a timestamp to improve the measurement of latency or jitter. The probe is timestamped by the device originating the probe (the RPM client).

In this sample use of RPM, basic probes are configured for two customers: Customer A and Customer B. The probe for Customer A uses ICMP timestamp packets and sets RPM thresholds and corresponding SNMP traps to catch lengthy inbound times. The probe for Customer B uses HTTP packets and sets thresholds and corresponding SNMP traps to catch excessive lost probes. To configure these RPM probes:

  1. Navigate to the top of the configuration hierarchy in either the J-Web or CLI configuration editor.
  2. Perform the configuration tasks described in Table 181.
  3. If you are finished configuring the network, commit the configuration.
  4. Go on to one of the following procedures:

Table 181: Configuring Basic RPM Probes

Task

J-Web Configuration Editor

CLI Configuration Editor

Navigate to the Services>RPM level in the configuration hierarchy.

  1. In the J-Web interface, select CLI Tools>Point and Click CLI.
  2. Next to Services, click Configure or Edit.
  3. Next to Rpm, select the Yes check box.
  4. Click Configure.

From the [edit] hierarchy level, enter

edit services rpm

Configure the RPM owners customerA and customerB.

  1. In the Probe box, click Add new entry.
  2. In the Owner box, type customerA.
  3. Click OK.
  4. Repeat the previous steps and add an RPM probe owner for customerB.
  1. Enter

    set probe customerA

  2. Enter

    set probe customerB

Configure the RPM test icmp-test for the RPM owner customerA.

The sample RPM test is an ICMP probe with a test interval (probe frequency) of 15 seconds, a probe type of icmp-ping-timestamp, a probe timestamp, and a target address of 192.178.16.5.

  1. On the Rpm page, select customerA.
  2. In the Test box, click Add new entry
  3. In the Name box, type icmp-test.
  4. In the Test interval box, type 15.
  5. In the Probe type box, select icmp-ping-timestamp.
  6. Select the Hardware timestamp check box.
  7. In the Target box, select the Yes check box, and click Configure.
  8. In the Target type box, select Address.
  9. In the Address box, type 192.178.16.5.
  10. Click OK.
  1. From the [edit] hierarchy level, enter

    edit services rpm probe customerA

  2. Enter

    set test icmp-test probe-frequency 15

  3. Enter

    set test icmp-test probe-type icmp-ping-timestamp

  4. Enter

    set test icmp-test hardware-timestamp

  5. Enter

    set test icmp-test target address 192.178.16.5

Configure RPM thresholds and corresponding SNMP traps to catch ingress (inbound) times greater than 3000 microseconds.

  1. On the Probe page, select icmp-test.
  2. In the Thresholds box, select the Yes check box, and click Configure.
  3. In the Ingress time box, type 3000.
  4. Click OK.
  5. In the Traps box, click Add new entry.
  6. In the Value box, select ingress-time-exceeded.
  7. Click OK.
  1. Enter

    set probe customerA test icmp-test thresholds ingress-time 3000

  2. Enter

    set probe customerA test icmp-test traps ingress-time-exceeded

Configure the RPM test http-test for the RPM owner customerB.

The sample RPM test is an HTTP probe with a test interval (probe frequency) of 30 seconds, a probe type of http-get, and a target URL of http://customerB.net.

  1. On the Rpm page, select customerB.
  2. In the Test box, click Add new entry.
  3. In the Name box, type http-test.
  4. In the Test interval box, type 30.
  5. In the Probe type box, select http-get.
  6. In the Target box, select the Yes check box, and click Configure.
  7. In the Target type box, select Url.
  8. In the Url box, type http://customerB.net.
  9. Click OK.
  1. From the [edit] hierarchy level, enter

    edit services rpm probe customerB

  2. Enter

    set test http-test probe-frequency 30

  3. Enter

    set test http-test probe-type http-get

  4. Enter

    set test http-test target url http://customerB.net

Configure RPM thresholds and corresponding SNMP traps to catch 3 or more successive lost probes and total lost probes of 10 or more.

  1. On the Probe page, select http-test.
  2. In the Thresholds box, select the Yes check box, and click Configure.
  3. In the Successive loss box, type 3.
  4. In the Total loss box, type 10.
  5. Click OK.
  6. In the Traps box, click Add new entry.
  7. In the Value box, select probe-failure.
  8. Click OK.
  9. In the Traps box, click Add new entry.
  10. In the Value box, select test-failure.
  11. Click OK.
  1. Enter

    set probe customerB test icmp-test thresholds successive-loss 3

  2. Enter

    set probe customerB test icmp-test thresholds total-loss 10

  3. Enter

    set probe customerB test icmp-test traps probe-failure

  4. Enter

    set probe customerB test icmp-test traps test-failure

Configuring TCP and UDP Probes

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 OS Class of Service Configuration Guide for Security Devices.

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:

  1. Navigate to the top of the configuration hierarchy in either the J-Web or CLI configuration editor.
  2. Perform the configuration tasks described in Table 182.
  3. If you are finished configuring the network, commit the configuration.
  4. Go on to one of the following procedures:

Table 182: Configuring TCP and UDP Probes

Task

J-Web Configuration Editor

CLI Configuration Editor

Router A Configuration 

Navigate to the Services>RPM level in the configuration hierarchy.

  1. In the J-Web interface, select CLI Tools>Point and Click CLI.
  2. Next to Services, click Configure or Edit.
  3. Next to Rpm, select the Yes check box.
  4. Click Configure.

From the [edit] hierarchy level, enter

edit services rpm

Configure the RPM owner customerC.

  1. In the Probe box, click Add new entry.
  2. In the Owner box, type customerC.
  3. Click OK.

Enter

set probe customerC

Configure the RPM test tcp-test for the RPM owner customerC.

The sample RPM test is a TCP probe with a test interval (probe frequency) of 5, a probe type of tcp-ping, and a target address of 192.162.45.6.

  1. On the Rpm page, select customerC.
  2. In the Test box, click Add new entry.
  3. In the Name box, type tcp-test.
  4. In the Test interval box, type 5.
  5. In the Probe type box, select tcp-ping.
  6. In the Target box, select the Yes check box, and click Configure.
  7. In the Target type box, select Address.
  8. In the Address box, type 192.162.45.6.
  9. Click OK.
  1. From the [edit] hierarchy level, enter

    edit services rpm probe customerC

  2. Enter

    set test tcp-test probe-frequency 5

  3. Enter

    set test tcp-test probe-type tcp-ping

  4. Enter

    set test tcp-test target address 192.162.45.6

Configure the destination interface.

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

In the Destination interface box, type lt-0/0/0

Enter

set test tcp-test destination-interface lt-0/0/0

Configure port 50000 as the TCP port to which the RPM probes are sent.

In the Destination port box, type 50000.

Enter

set test tcp-test destination-port 50000

Router B Configuration 

Navigate to the Services>RPM level in the configuration hierarchy.

  1. In the J-Web interface, select CLI Tools>Point and Click CLI.
  2. Next to Services, click Configure or Edit.
  3. Next to Rpm, select the Yes check box.
  4. Click Configure.

From the [edit] hierarchy level, enter

edit services rpm

Configure Router B to act as a TCP server, using port 50000 to send and receive TCP probes.

  1. Next to Probe server, click Configure.
  2. In the Tcp box, click Configure.
  3. In the Port box, type 50000.
  4. Click OK.

Enter

set probe-server tcp port 50000

Configure Router B to act as a UDP server, using port 50037 to send and receive UDP probes.

  1. Next to Probe server, click Edit.
  2. In the Udp box, click Configure.
  3. In the Port box, type 50037.
  4. Click OK.

Enter

set probe-server udp port 50037

Tuning RPM Probes

After configuring an RPM probe, you can set parameters to control probe functions, such as the interval between probes, the total number of concurrent probes that a system can handle, and the source address used for each probe packet. This example tunes the ICMP probe set for customer A in Configuring Basic RPM Probes.

To configure tune RPM probes:

  1. Perform the configuration tasks described in Table 181.
  2. Navigate to the top of the configuration hierarchy in either the J-Web or CLI configuration editor.
  3. Perform the configuration tasks described in Table 183.
  4. If you are finished configuring the network, commit the configuration.
  5. To check the configuration, see Verifying an RPM Configuration.

Table 183: Tuning RPM Probes

Task

J-Web Configuration Editor

CLI Configuration Editor

Navigate to the Services>RPM level in the configuration hierarchy.

  1. In the J-Web interface, select CLI Tools>Point and Click CLI.
  2. Next to Services, click Configure or Edit.
  3. Next to Rpm, select the Yes check box.
  4. Click Edit.

From the [edit] hierarchy level, enter

edit services rpm

Set the maximum number of concurrent probes allowed on the system to 10.

  1. In the Probe limit box, type 10.
  2. Click OK.

Enter

set probe-limit 10

Access the ICMP probe of customer A.

  1. In the Owner box, click CustomerA.
  2. In the Name box, click icmp-test.

From the [edit] hierarchy level, enter

edit services rpm probe customerA test icmp-test

Set the time between probe transmissions to 15 seconds.

In the Probe interval box, type 15.

Enter

set probe-interval 15

Set the number of probes within a test to 10.

In the Probe count box, type 10.

Enter

set probe-count 10

Set the source address for each probe packet to 192.168.2.9.

If you do not explicitly configure a source address, the address on the outgoing interface through which the probe is sent is used as the source address.

  1. In the Source address box, type 192.168.2.9.
  2. Click OK.

Enter

set source-address 192.168.2.9

Configuring RPM Probes to Monitor BGP Neighbors

By default, the device is not configured to send RPM probes to its BGP neighbors. You must configure the BGP parameters under RPM configuration to send RPM probes to BGP neighbors.

You can also direct the probes to a particular group of BGP neighbors.

This section contains the following topics:

Configuring RPM Probes for BGP Monitoring

This sample use of RPM for BGP monitoring uses a TCP probe. To use TCP or UDP probes, you must configure both the probe server (J Series or SRX Series device) and the probe receiver (the remote device) to transmit and receive RPM probes on the same TCP or UDP port. The sample probe uses TCP port 50000.

To configure RPM probes on a device to monitor BGP neighbors with a configuration editor:

  1. Navigate to the top of the configuration hierarchy in either the J-Web or CLI configuration editor.
  2. Perform the configuration tasks described in Table 184.
  3. If you are finished configuring the device, commit the configuration.
  4. Go on to one of the following tasks:

Table 184: Configuring RPM Probes to Monitor BGP Neighbors

Task

J-Web Configuration Editor

CLI Configuration Editor

Navigate to the Services>RPM>BGP level in the configuration hierarchy.

  1. In the J-Web interface, select CLI Tools>Point and Click CLI.
  2. Next to Services, click Configure or Edit.
  3. Next to Rpm, select the Yes check box and click Configure or Edit.
  4. Next to Bgp, click Configure.

From the [edit] hierarchy level, enter

edit services rpm bgp

Specify a hexadecimal value (the range is between 1 and 2048 characters) that you want to use for the data portion of the RPM probe—for example, ABCD123.

In the Data fill box, type ABCD123.

Enter

set data-fill ABCD123

Specify the data size of the RPM probe in bytes, a value from 0 through 65507—for example, 1024.

In the Data size box, type 1024.

Enter

set data-size 1024

Configure port 50000 as the TCP port to which the RPM probes are sent.

In the Destination port box, type 50000.

Enter

set destination-port 50000

Specify the number of probe results to be saved in the probe history—for example, 25. The range is between 0 and 255, and the default is 50.

In the History size box, type 25.

Enter

set history-size 25

Configure the probe count—for example, 5—and probe interval—for example, 1.

  • Probe count—Total number of RPM probes to be sent for each test. The range is between 1 and 15 and the default is 1.
  • Probe interval—Wait time (in seconds) between RPM probes. The range is between 1 and 255, and the default is 3.
  1. In the Probe count box, type 5.
  2. In the Probe interval box, type 1.

Enter

set probe-count 5 probe-interval 1

Specify the type of probe to be sent as part of the test—tcp-ping.

Note: If you do not specify the probe type the default ICMP probes are sent.

In the Probe type box, select tcp-ping.

Enter

set probe-type tcp-ping

Configure a value between 0 and 86400 seconds for the interval between tests—for example, 60.

  1. In the Test interval box, type 60.
  2. Click OK.

Enter

set test-interval 60

Directing RPM Probes to Select BGP Routers

If a device has a large number of BGP neighbors configured, you can direct (filter) the RPM probes to a selected group of BGP neighbors rather than to all the neighbors. To identify the BGP routers to receive RPM probes, you can configure routing instances.

The sample RPM configuration in Table 185 sends RPM probes to the BGP neighbors in routing instance R1.

To direct RPM probes to select BGP neighbors:

  1. Navigate to the top of the configuration hierarchy in either the J-Web or CLI configuration editor.
  2. Perform the configuration tasks described in Table 185.
  3. If you are finished configuring the device, commit the configuration.
  4. To verify the configuration, see Verifying an RPM Configuration.

Table 185: Directing RPM Probes to Select BGP Routers

Task

J-Web Configuration Editor

CLI Configuration Editor

Navigate to the Services>RPM>BGP level in the configuration hierarchy.

  1. In the J-Web interface, select CLI Tools>Point and Click CLI.
  2. Next to Services, click Configure or Edit.
  3. Next to Rpm, select the Yes check box and click Configure or Edit.
  4. Next to Bgp, click Configure or Edit.

From the [edit] hierarchy level, enter

edit services rpm bgp

Configure routing instance RI1 to send RPM probes to BGP neighbors within the routing instance.

  1. Next to Routing instances, click Add new entry.
  2. In the Routing instance name box, type RI1.
  3. Click OK.

Enter

set routing-instances RI1

Configuring RPM Timestamping

To account for latency in the communication of probe messages, you can enable timestamping of the probe packets. You can timestamp the following RPM probe types: icmp-ping, icmp-ping-timestamp, udp-ping, and udp-ping-timestamp.

The following example shows how to enable timestamping for customerA. The test for customerA is identified as customerA-test.

To configure timestamping:

  1. Specify the RPM probe owner for which you want to enable timestamping:
    [edit services rpm]user@host#edit probe customerA
  2. Specify a name for the test:
    [edit services rpm probe customerA]user@host#edit test customerA-test
  3. Enable timestamping:
    [edit services rpm probe customerA test customerA-test]user@host#edit hardware-timestamp
  4. (Optional) If preferred, indicate that you want the timestamping to be only one-way:
    [edit services rpm probe customerA test customerA-test]user@host#edit one-way-hardware-timestamp

Note: You cannot include both the source-address and hardware-timestamp or one-way-hardware-timestamp statements at the [edit services rpm probe probe-name test test-name] hierarchy level simultaneously.

Copyright© 1999-2010 Juniper Networks, Inc. All rights reserved.