Automation

last person joined: 4 days ago 

Ask questions and share experiences about Apstra, Paragon, and all things network automation.
  • 1.  RPM and Event Policy Config Change!

    Posted 10-09-2016 14:51

    Hello Guys, 

     

    I am new at Juniper and I am setting up some RPM Probes which will monitored some connections. In case any of these Probes fail. The router will have some Event Policies set that will change certains config from the Router. 

     

    I've set the RPM and the event manager. Everything is working perfectly. Except 1 thing. 

     

     

    RPM Config

     

    username@host# show services rpm
    probe TEST {
    test TEST {
    probe-type icmp-ping;
    target address (IP X.X.X.X);
    probe-count 10;
    test-interval 15;
    source-address (IP X.X.X.X);

     

     and this is my event Policy:

     

     

    set event-options policy UPDATE_ON_LINK_DOWN events ping_probe_failed
    set event-options policy UPDATE_ON_LINK_DOWN attributes-match ping_probe_failed.test-name matches TEST
    set event-options policy UPDATE_ON_LINK_DOWN then change-configuration commands "set interfaces xe-1/0/0 unit 1 description TEST"
    set event-options policy UPDATE_ON_LINK_DOWN then change-configuration user-name (USERNAME)
    set event-options policy UPDATE_ON_LINK_DOWN then change-configuration commit-options log "updating configuration from event policy"

     

     

    As previously stated, Everything works as expected. However. I noticed that the CPU on the router increased around 11% and also that the Router kept commiting the Event Policy

     

    I am running 2 routing engines so I assume that only 2 commits should appear. 

     

    Commit Logs:

     

    0 2016-10-09 21:43:00 UTC by username via junoscript commit synchronize
    updating configuration from event policy
    1 2016-10-09 21:42:55 UTC byusername via junoscript commit synchronize
    updating configuration from event policy
    2 2016-10-09 21:42:46 UTC byusername via junoscript commit synchronize
    updating configuration from event policy
    3 2016-10-09 21:42:40 UTC byusername via junoscript commit synchronize
    updating configuration from event policy
    4 2016-10-09 21:42:34 UTC byusername via junoscript commit synchronize
    updating configuration from event policy
    5 2016-10-09 21:42:28 UTC byusername via junoscript commit synchronize
    updating configuration from event policy
    6 2016-10-09 21:42:22 UTC byusername via junoscript commit synchronize
    updating configuration from event policy
    7 2016-10-09 21:42:01 UTC byusername via junoscript commit synchronize
    updating configuration from event policy
    8 2016-10-09 21:41:55 UTC byusername via junoscript commit synchronize
    updating configuration from event policy
    9 2016-10-09 21:41:50 UTC byusername via junoscript commit synchronize

     

     

     

    The system keeps commiting until I bring the Interface XE 0/0/1.2 Up. Then it stops. 

     

    I assume that the Event Policy keeps detecting the Failed Probe and keeps performing the changes. 

     

    Any idea about how to make it run only 1 time and then stops?

     

     

    Any help will be highly appreciated, 



  • 2.  RE: RPM and Event Policy Config Change!
    Best Answer

    Posted 10-09-2016 22:44

    Hi,

    basic idea to get rid of this is to have two RPM probes and two event policies - one for the link up and one for the link down event - where the event polices activate and de-activate each other in turns.

     

    See my replay in http://forums.juniper.net/t5/Routing/IP-SLA-equilvilent-for-Junos/td-p/297703

     

    Cheers,

    Carsten



  • 3.  RE: RPM and Event Policy Config Change!

    Posted 10-10-2016 08:39

    Thanks camtable. I will give it a try and let you know how it goes. 



  • 4.  RE: RPM and Event Policy Config Change!

    Posted 10-10-2016 09:17

    Thanks camtable. It worked perfectly.