Support Support Downloads Knowledge Base Case Manager My Juniper Community

Knowledge Base

Search our Knowledge Base sites to find answers to your questions.

Ask All Knowledge Base Sites All Knowledge Base Sites JunosE Defect (KA)Knowledge BaseSecurity AdvisoriesTechnical BulletinsTechnotes Sign in to display secure content and recently viewed articles

Configuring Real-Time Performance Monitoring on EX Switches

0

0

Article ID: KB15648 KB Last Updated: 03 Mar 2017Version: 2.0
Summary:
Real-time performance monitoring (RPM) enables you to configure active probes to track and monitor traffic across the network and investigate network problems. You can use RPM with EX Switches and this KB provides sample configurations.
Symptoms:

Solution:
To configure RPM services, include the rpm statement at the [edit services] hierarchy level.

Topology for the following sample configurations:
 
Probe                                      Target
  EX1 ------------------------------  EX2 (loopback0:37.1.1.1)


Configuring the Probe

The probe statement defines the owner name and test name used as identifiers for the probe. Together, they represent a single RPM configuration instance. When you specify the test name, you also can configure the test parameters. To configure the probe owner, test name, and test parameters, include the probe statement at the [edit services rpm] hierarchy level.

Here is an example using probe types, udp-ping and icmp-ping:
root@EX1# show services rpm
probe probe1 {                    # probe owner #
    test probe_test1 {            # test name #
        probe-type udp-ping;      # test parameters #
        target address 37.1.1.1;
        test-interval 10;
        destination-port 49160;
    }
}
probe probe2 {                    # probe owner #
    test probe_test2 {            # test name #
        probe-type icmp-ping;     # test parameters #
        target address 37.1.1.1;
        test-interval 10;
    }
}

Configuring the Server

The TCP and UDP probes are proprietary to Juniper Networks and require a receiver to receive the probes. To configure the server to receive the probes, include the probe-server statement at the 'edit services rpm' hierarchy level.

Here is an example.
root@EX2# show services rpm
probe-server {
     udp {
         port 49160;
     }
}
NOTE: This port number should be same as the value of 'destination-port' from the Probe configuration.

Here are sample outputs:
root@EX1# run show services rpm probe-results
    Owner: probe1, Test: probe_test1
    Target address: 37.1.1.1, Probe type: udp-ping, Test size: 1 probes
    Probe results:
      Response received, Mon Oct 5 01:49:37 2009, No hardware timestamps
      Rtt: 1999 usec
    Results over current test:
      Probes sent: 1, Probes received: 1, Loss percentage: 0
      Measurement: Round trip time
        Samples: 1, Minimum: 1999 usec, Maximum: 1999 usec, Average: 1999 usec, Peak to peak: 0 usec,
        Stddev: 0 usec, Sum: 1999 usec
    Results over last test:
      Probes sent: 1, Probes received: 1, Loss percentage: 0
      Test completed on Mon Oct 5 01:49:40 2009
      Measurement: Round trip time
        Samples: 1, Minimum: 1999 usec, Maximum: 1999 usec, Average: 1999 usec, Peak to peak: 0 usec,
        Stddev: 0 usec, Sum: 1999 usec
    Results over all tests:
      Probes sent: 152, Probes received: 140, Loss percentage: 7
      Measurement: Round trip time
        Samples: 140, Minimum: 1762 usec, Maximum: 9799 usec, Average: 2252 usec, Peak to peak: 8037 usec,
        Stddev: 800 usec, Sum: 315335 usec

    Owner: probe2, Test: probe_test2
    Target address: 37.1.1.1, Probe type: icmp-ping, Test size: 1 probes
    Probe results:
      Response received, Mon Oct 5 01:49:36 2009, No hardware timestamps
      Rtt: 1598 usec
    Results over current test:
      Probes sent: 1, Probes received: 1, Loss percentage: 0
      Measurement: Round trip time
        Samples: 1, Minimum: 1598 usec, Maximum: 1598 usec, Average: 1598 usec, Peak to peak: 0 usec,
        Stddev: 0 usec, Sum: 1598 usec
    Results over last test:
      Probes sent: 1, Probes received: 1, Loss percentage: 0
      Test completed on Mon Oct 5 01:49:36 2009
      Measurement: Round trip time
        Samples: 1, Minimum: 1598 usec, Maximum: 1598 usec, Average: 1598 usec, Peak to peak: 0 usec,
        Stddev: 0 usec, Sum: 1598 usec
    Results over all tests:
      Probes sent: 699, Probes received: 699, Loss percentage: 0
      Measurement: Round trip time
        Samples: 699, Minimum: 1334 usec, Maximum: 13510 usec, Average: 1898 usec, Peak to peak: 12176 usec,
        Stddev: 1156 usec, Sum: 1326634 usec


root@EX1# run show services rpm history-results
    Owner, Test Probe received Round trip time
    probe1, probe_test1 Mon Oct 5 01:39:00 2009 2048 usec
    probe1, probe_test1 Mon Oct 5 01:39:13 2009 3484 usec
    probe1, probe_test1 Mon Oct 5 01:39:26 2009 2210 usec
    probe1, probe_test1 Mon Oct 5 01:39:39 2009 2022 usec
    probe1, probe_test1 Mon Oct 5 01:39:52 2009 2379 usec
    probe1, probe_test1 Mon Oct 5 01:40:05 2009 1930 usec
    ----snip
    probe2, probe_test2 Mon Oct 5 01:41:26 2009 1473 usec
    probe2, probe_test2 Mon Oct 5 01:41:36 2009 1528 usec
    probe2, probe_test2 Mon Oct 5 01:41:46 2009 1512 usec
    probe2, probe_test2 Mon Oct 5 01:41:56 2009 1470 usec
    probe2, probe_test2 Mon Oct 5 01:42:06 2009 1537 usec
    probe2, probe_test2 Mon Oct 5 01:42:16 2009 1614 usec
    ----snip


root@EX2# run show services rpm active-servers
Protocol: UDP, Port: 49160

Related Links

Comment on this article > Affected Products Browse the Knowledge Base for more articles related to these product categories. Select a category to begin.

Getting Up and Running with Junos

Getting Up and Running with Junos Security Alerts and Vulnerabilities Product Alerts and Software Release Notices Problem Report (PR) Search Tool EOL Notices and Bulletins JTAC User Guide Customer Care User Guide Pathfinder SRX High Availability Configurator SRX VPN Configurator Training Courses and Videos End User Licence Agreement Global Search