Verifying an RPM Configuration

To verify an RPM configuration, perform these tasks:

• Verifying RPM Services
• Verifying RPM Statistics
• Verifying RPM Probe Servers

Verifying RPM Services

Purpose

Verify that the RPM configuration is within the expected values.

Action

From configuration mode in the CLI, enter the show services rpm command.

Sample Output

   probe test {
    test customerA {
        probe-type icmp-ping;
        target address 192.178.16.5;
        probe-count 15;
        probe-interval 1;
        hardware-timestamp;
    }
    test customerB {
        probe-type icmp-ping-timestamp;
        target address 192.178.16.5;
        probe-count 15;
        probe-interval 1;
        hardware-timestamp;
    }
    test customerC {
        probe-type udp-ping;
        target address 192.178.16.5;
        probe-count 15;
        probe-interval 1;
        destination-port 50000;
        hardware-timestamp;
    }
   }

Meaning

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 the J-Web interface, select Troubleshoot>RPM>View RPM. From the CLI, enter the show services rpm probe-results command.

Sample Output

    Owner: customerA, 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: customerB, 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

Meaning

The output shows the probe results for the RPM tests configured on the device. Verify the following information:

• Each configured test is displayed. Results are displayed in alphabetical order, sorted first by owner name and then by test name.
• The round-trip times fall within the expected values for the particular test. The minimum round-trip time is displayed as Minimum Rtt, the maximum round-trip time is displayed as Maximum Rtt, and the average round-trip time is displayed as Average Rtt.

  A high average round-trip time might mean that performances problems exist within the network. A high maximum round-trip time might result in high jitter values.

• The egress (outbound) trip times fall within the expected values for the particular test. The minimum outbound time is displayed as Minimum egress time, the maximum outbound time is displayed as Maximum egress time, and the average outbound time is displayed as Average egress time.
• The ingress (inbound) trip times fall within the expected values for the particular test. The minimum inbound time is displayed as Minimum ingress time, the maximum inbound time is displayed as Maximum ingress time, and the average inbound time is displayed as Average ingress time.
• The number of probes sent and received is expected.

  Lost probes might indicate packet loss through the network. Packet losses can occur if the remote server is flapping. If the RPM probe type is TCP or UDP, complete probe loss might indicate a mismatch in TCP or UDP RPM port number.

• For Type, each peer is configured as the correct type (either internal or external).

Related Topics

For a complete description of show services rpm probe-results output, see the Junos System Basics and Services Command Reference.

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 the CLI, enter the show services rpm active-servers command.

Sample Output

    Protocol: TCP, Port: 50000

    Protocol: UDP, Port: 50037

Meaning

The output shows a list of the protocols and corresponding ports for which the device is configured as an RPM server.

Related Topics

For a complete description of show services rpm active-servers output, see the Junos System Basics and Services Command Reference.