Junos OS

IMPORTANT MODERATION NOTICE

This community is currently under full moderation, meaning  all posts will be reviewed before appearing in the community. Please expect a brief delay—there is no need to post multiple times. If your post is rejected, you'll receive an email outlining the reason(s). We've implemented full moderation to control spam. Thank you for your patience and participation.



realtime performance monitoring (RPM) vs two-way active measurement protocol (TWAMP)

  • 1.  realtime performance monitoring (RPM) vs two-way active measurement protocol (TWAMP)

    Posted 05-27-2021 04:00
    Hi all,
    I've already read about RPM and TWAMP. I recognize a couple of things between them. By my understanding, they're almost the same.
    But while I setting up two of them on my device (two acx2200 series), I see the RPM results, and the TWAMP results are different. As you can see below:

    show services rpm twamp client probe-results | match rtt
    May 27 14:53:00
          Rtt: 40 usec, Round trip jitter: 0 usec, Round trip interarrival jitter: 0 usec​

    show services rpm probe-results owner SLA test Ping-from-R150-to-R151 | match rtt
    May 27 14:53:27
          Rtt: 888 usec, Round trip jitter: 14 usec, Round trip interarrival jitter: 453 usec​


    →  The round trip time (Rtt) value has a big difference. Why is that? Please kindly explain for me. Tks

    My configuration about RPM and TWAMP:
         - RMP:

    @AGG1> show configuration services rpm probe SLA
    May 27 14:59:29
    test Ping-from-R150-to-R151 {
        probe-type icmp-ping;
        target address 172.16.2.2;
        probe-count 3;
        probe-interval 10;
        test-interval 10;
        source-address 172.16.2.1;
        thresholds {
            successive-loss 1;
            total-loss 3;
        }
        traps [ test-failure probe-failure ];
    }


         - TWAMP:

    AGG1> show configuration services rpm twamp
    May 27 15:00:17
    client {
        control-connection c1 {
            authentication-mode none;
            destination-interface si-1/1/0.10;
            history-size 500;
            target-address 70.70.70.1;
            test-count 1;
            test-session t1 {
                target-address 70.70.70.1;
                data-fill-with-zeros;
                data-size 1400;
                probe-count 6;
                probe-interval 10;
            }
        }
    }