[ Contents] [ Prev] [ Next] [ Index] [ Report an Error]

show services rpm probe-results

Syntax

show services rpm probe-results
<owner owner>
<test name>

Release Information

Command introduced before JUNOS Release 7.4.

Description

Display the results of the most recent real-time performance monitoring (RPM) probes.

Options

none — Display all results of the most recent RPM probes.

owner owner(Optional) Display information for the specified probe owner.

test name(Optional) Display information for the specified test.

Required Privilege Level

view

List of Sample Output

show services rpm probe-results
show services rpm probe-results (BGP Neighbor Discovery)

Output Fields

Table 10 lists the output fields for the show services rpm probe-results command. Output fields are listed in the approximate order in which they appear.

Table 10: show services rpm probe-results Output Fields

Field Name

Field Description

Owner

Owner name. When you configure the probe owner statement at the [edit services rpm] hierarchy level, this field displays the configured owner name. When you configure BGP neighbor discovery through RPM, the output for this field is Rpm-Bgp-Owner.

Test

Name of a test representing a collection of probes. When you configure the test test-name statement at the [edit services rpm probe owner] hierarchy level, the field displays the configured test name. When you configure BGP neighbor discovery through RPM, the output for this field is Rpm-BGP-Test- n, where n is a cumulative number.

Target address

Destination address used for the probes.

Source address

Source address used for the probes.

Probe type

Reflects the protocol configured on the receiving probe server. The following protocol types can be configured: http-get, http-metadata-get, icmp-ping, icmp-ping-timestamp, tcp-ping, udp-ping, and udp-ping-timestamp.

Test size

Number of probes within a test.

Routing Instance Name

(BGP neighbor discovery) Name of the configured (if any) routing instance, logical router name, or both, in which the probe is configured:

  • When a routing instance is defined within a logical router, the logical router name is followed by the routing instance name. A slash ( / ) is used to separate the two entities. For example, if the routing instance called R1 is configured within the logical router called LR, the name in the output field is LR/R1.
  • When a routing instance is configured but the default logical router is used, the name in the output field is the name of the routing instance.
  • When a logical router is configured but the default routing instance is used, the name in the output field is the name of the logical router followed by default. A slash (/) is used to separate the two entities. For example, LR/default.

Probe results

Result of a particular probe done by a remote host. The following information is contained in the results:

  • Response received—Timestamp when the probe result was determined.
  • Rtt—Average ping round-trip time (RTT), in microseconds.

Results over current test

Probes are grouped into tests, and the statistics are calculated for each test. If a test contains 10 probes, the average, minimum, and maximum results are calculated from the results of those 10 probes. If the command is issued while the test is in progress, the statistics use information from the completed probes.

  • Probes sent—Number of probes sent within the current test.
  • Probes received—Number of probe responses received within the current test.
  • Loss percentage—Percentage of lost probes for the current test.
  • Measurement—Increment of measurement. Possible values are round-trip time delay and, for the probe typeicmp-ping-timestamp, the egress delay and ingress delay.
    • Minimum—Minimum RTT, ingress delay, or egress delay measured over the course of the current test.
    • Maximum—Maximum RTT, ingress delay, or egress delay measured over the course of the current test.
    • Average—Average RTT, ingress delay, or egress delay measured over the course of the current test.
    • Jitter—Jitter, in microseconds.
    • Stddev—Standard deviation, in microseconds.

Results over last test

Results for the most recently completed test. If the command is issued while the first test is in progress, this information is not displayed

  • Probes sent—Number of probes sent for the most recently completed test.
  • Probes received—Number of probe responses received for the most recently completed test.
  • Loss percentage—Percentage of lost probes for the most recently completed test.
  • Test completed—Time the most recent test was completed.
  • Measurement—Increment of measurement. Possible values are round-trip time delay and, for the probe type icmp-ping-timestamp, the egress delay and ingress delay.
    • Minimum—Minimum RTT, ingress delay, or egress delay measured for the most recently completed test.
    • Maximum—Maximum RTT, ingress delay, or egress delay measured for the most recently completed test.
    • Average—Average RTT, ingress delay, or egress delay measured for the most recently completed test.
    • Jitter—Jitter, in microseconds.
    • Stddev—Standard deviation, in microseconds.

Results over all tests

Displays statistics made for all the probes, independently of the grouping into tests, as well as statistics for the current test.

  • Probes sent—Number of probes sent in all tests.
  • Probes received—Number of probe responses received in all tests.
  • Loss percentage—Percentage of lost probes in all tests.
  • Measurement—Increment of measurement. Possible values are round-trip time delay and, for the probe types icmp-ping-timestamp and udp-ping-timestamp, the egress delay and ingress delay.
    • Minimum—Minimum RTT, ingress delay, or egress delay measured over the course of the current test.
    • Maximum—Maximum RTT, ingress delay, or egress delay measured over the course of the current test.
    • Average—Average RTT, ingress delay, or egress delay measured over the course of the current test.
    • Jitter—Jitter, in microseconds.
    • Stddev—Standard deviation, in microseconds.

show services rpm probe-results

user@host> show services rpm probe-results
Owner: p1, Test: t1
    Target address: 10.8.4.1, Source address: 10.8.4.2, Probe type: http-get
    Test size: 10 probes
    Probe results:
      Response received, Sun Dec 18 21:05:19 2005
      Rtt: 665826 usec
    Results over current test:
      Probes sent: 7, Probes received: 7, Loss percentage: 0
      Measurement: Round trip time
        Minimum: 663857 usec, Maximum: 703188 usec, Average: 674434 usec,
        Jitter: 39331 usec, Stddev: 12666 usec
    Results over last test:
      Probes sent: 10, Probes received: 10, Loss percentage: 0
      Test Completed on Sun Dec 18 21:05:02 2005
      Measurement: Round trip time
        Minimum: 658846 usec, Maximum: 723366 usec, Average: 676462 usec,
        Jitter: 64520 usec, Stddev: 21260 usec
    Results over all tests:
      Probes sent: 112347, Probes received: 109550, Loss percentage: 2
      Measurement: Round trip time
        Minimum: 641772 usec, Maximum: 999742 usec, Average: 668326 usec,
        Jitter: 357970 usec, Stddev: 37523 usec

show services rpm probe-results (BGP Neighbor Discovery)

user@host> show services rpm probe-results
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

[ Contents] [ Prev] [ Next] [ Index] [ Report an Error]