Automation

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.



question about event trigger timing for event policy

  • 1.  question about event trigger timing for event policy

    Posted 04-24-2021 20:48
    I have the following:
    set services rpm probe demo-probe test demo-ping probe-type icmp-ping
    set services rpm probe demo-probe test demo-ping target address 10.146.40.242
    set services rpm probe demo-probe test demo-ping probe-count 2
    set services rpm probe demo-probe test demo-ping probe-interval 2
    set services rpm probe demo-probe test demo-ping test-interval 2
    set services rpm probe demo-probe test demo-ping source-address 10.146.40.39
    set services rpm probe demo-probe test demo-ping routing-instance NSX-QFX-B-MGMT
    deactivate services rpm probe demo-probe test demo-ping routing-instance
    set services rpm probe demo-probe test demo-ping thresholds successive-loss 2
    
    set event-options policy demo-ep events ping_test_failed
    set event-options policy demo-ep within 14 trigger on
    set event-options policy demo-ep within 14 trigger 4
    set event-options policy demo-ep within 17 trigger until
    set event-options policy demo-ep within 17 trigger 5
    set event-options policy demo-ep attributes-match ping_test_failed.test-owner matches demo-probe
    set event-options policy demo-ep attributes-match ping_test_failed.test-name matches demo-ping
    deactivate event-options policy demo-ep attributes-match
    set event-options policy demo-ep then change-configuration commands "set system ntp server 1.1.1.1"
    set event-options policy demo-ep then change-configuration commit-options log "event trigged"
    set event-options traceoptions file event-log
    set event-options traceoptions flag all
    
    root@QGX-39# run show log rpm | last 10 | match PING_TEST_FAILED 
    Apr 24 09:10:13.278 2021  QGX-39 rmopd[6830]: PING_TEST_FAILED: pingCtlOwnerIndex = demo-probe, pingCtlTestName = demo-ping
    Apr 24 09:10:17.540 2021  QGX-39 rmopd[6830]: PING_TEST_FAILED: pingCtlOwnerIndex = demo-probe, pingCtlTestName = demo-ping
    Apr 24 09:10:21.808 2021  QGX-39 rmopd[6830]: PING_TEST_FAILED: pingCtlOwnerIndex = demo-probe, pingCtlTestName = demo-ping
    Apr 24 09:10:26.067 2021  QGX-39 rmopd[6830]: PING_TEST_FAILED: pingCtlOwnerIndex = demo-probe, pingCtlTestName = demo-ping
    Apr 24 09:10:30.328 2021  QGX-39 rmopd[6830]: PING_TEST_FAILED: pingCtlOwnerIndex = demo-probe, pingCtlTestName = demo-ping
    Apr 24 09:10:34.594 2021  QGX-39 rmopd[6830]: PING_TEST_FAILED: pingCtlOwnerIndex = demo-probe, pingCtlTestName = demo-ping
    Apr 24 09:10:38.858 2021  QGX-39 rmopd[6830]: PING_TEST_FAILED: pingCtlOwnerIndex = demo-probe, pingCtlTestName = demo-ping
    Apr 24 09:10:43.120 2021  QGX-39 rmopd[6830]: PING_TEST_FAILED: pingCtlOwnerIndex = demo-probe, pingCtlTestName = demo-ping
    Apr 24 09:10:47.379 2021  QGX-39 rmopd[6830]: PING_TEST_FAILED: pingCtlOwnerIndex = demo-probe, pingCtlTestName = demo-ping
    Apr 24 09:10:51.636 2021  QGX-39 rmopd[6830]: PING_TEST_FAILED: pingCtlOwnerIndex = demo-probe, pingCtlTestName = demo-ping​

    Event trace log complains
    Apr 24 09:04:40 Policy <demo-ep>'s conditions dont match for event <PING_TEST_FAILED>

    How to specify the trigger time  based on rpm log ?  4 events should 16s or 12s ?

    thanks a lot in advance !!