Example: Configuring Basic RPM Probes
This example shows how to configure basic RPM probes to measure performance between two network endpoints.
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.
Overview
In this example, you configure basic probes for two RPM owners, customerA and customerB. You configure the RPM test as icmp-test for customerA with a test interval of 15 seconds and specify a probe type as icmp-ping-timestamp, a probe timestamp, and a target address as 192.178.16.5. You then configure the RPM thresholds and corresponding SNMP traps to catch ingress (inbound) times greater than 3000 microseconds.
Then you configure the RPM test as http-test for customerB with a test interval of 30 seconds and specify a probe type as http-get and a target URL as http://customerB.net. Finally, you configure RPM thresholds and corresponding SNMP traps as probe-failure and test-failure to catch three or more successive lost probes and total lost probes of 10.
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
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.
To configure basic RPM probes:
- Configure the RPM.[edit]user@host# edit services rpm
- Configure the RPM owners.[edit services rpm]user@host# set probe customerAuser@host# set probe customerB
- Configure the RPM test for customerA.[edit services rpm]user@host# edit probe customerAuser@host# set test icmp-test probe-interval 15user@host# set test icmp-test probe-type icmp-ping-timestamp
- Specify a probe timestamp and a target address.[edit services rpm probe customerA]user@host# set test icmp-test hardware-timestampuser@host# set test icmp-test target address 192.178.16.5
- Configure RPM thresholds and corresponding SNMP traps.[edit services rpm probe customerA]user@host# set test icmp-test thresholds ingress-time 3000 user@host# set test icmp-test traps ingress-time-exceeded
- Configure the RPM test for customerB.[edit]user@host# edit services rpm probe customerBuser@host# set test http-test probe-interval 30
- Specify a probe type and a target URL.[edit services rpm probe customerB]user@host# set test http-test probe-type http-getuser@host# set test http-test target url http://customerB.net
- Configure RPM thresholds and corresponding SNMP traps.[edit services rpm probe customerB]user@host# set test http-test thresholds successive-loss 3user@host# set test http-test thresholds total-loss 10user@host# set test http-test traps probe-failureuser@host# set test http-test traps test-failure
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
Confirm that the configuration is working properly.
Verifying RPM Services
Purpose
Verify that the RPM configuration is within the expected values.
Action
From configuration mode, enter the show services rpm command. The output shows the values that are configured for RPM on the device.
Verifying RPM Statistics
Purpose
Verify that the RPM probes are functioning and that the RPM statistics are within expected values.
Action
From configuration mode, enter the show services rpm probe-results command.
Owner: customerD, Test: icmp-test
Probe type: icmp-ping-timestamp
Minimum Rtt: 312 usec, Maximum Rtt: 385 usec, Average Rtt: 331 usec,
Jitter Rtt: 73 usec, Stddev Rtt: 27 usec
Minimum egress time: 0 usec, Maximum egress time: 0 usec,
Average egress time: 0 usec, Jitter egress time: 0 usec,
Stddev egress time: 0 usec
Minimum ingress time: 0 usec, Maximum ingress time: 0 usec,
Average ingress time: 0 usec, Jitter ingress time: 0 usec,
Stddev ingress time: 0 usec
Probes sent: 5, Probes received: 5, Loss percentage: 0
Owner: customerE, Test: http-test
Target address: 192.176.17.4, Target URL: http://customerB.net,
Probe type: http-get
Minimum Rtt: 1093 usec, Maximum Rtt: 1372 usec, Average Rtt: 1231 usec,
Jitter Rtt: 279 usec, Stddev Rtt: 114 usec
Probes sent: 3, Probes received: 3, Loss percentage: 0
Owner: Rpm-Bgp-Owner, Test: Rpm-Bgp-Test-1
Target address: 10.209.152.37, Probe type: icmp-ping, Test size: 5 probes
Routing Instance Name: LR1/RI1
Probe results:
Response received, Fri Oct 28 05:20:23 2005
Rtt: 662 usec
Results over current test:
Probes sent: 5, Probes received: 5, Loss percentage: 0
Measurement: Round trip time
Minimum: 529 usec, Maximum: 662 usec, Average: 585 usec,
Jitter: 133 usec, Stddev: 53 usec
Results over all tests:
Probes sent: 5, Probes received: 5, Loss percentage: 0
Measurement: Round trip time
Minimum: 529 usec, Maximum: 662 usec, Average: 585 usec,
Jitter: 133 usec, Stddev: 53 usec
