You may find that when using event-options to change a configuration, that the event triggers, and the event-options says that the configuration change is triggered, but then the commit does not actually happen.
services {
rpm {
probe PRIMARY {
test ICMP {
probe-type icmp-ping;
target address 8.8.8.8;
probe-count 10;
test-interval 5;
thresholds {
successive-loss 10;
total-loss 10;
}
event-options {
policy vrrp-failover {
events ping_test_failed;
attributes-match {
ping_test_failed.test-owner matches PRIMARY;
ping_test_failed.test-name matches ICMP;
then {
change-configuration {
retry count 5 interval 4;
commands {
"deactivate services rpm probe PRIMARY";
"activate services rpm probe SECONDARY";
"set interfaces irb unit 100 family inet address 172.22.64.2/18 vrrp-group 1 priority 10";
interfaces {
irb {
unit 100 {
family inet {
address 172.10.0.2/24 {
vrrp-group 1 {
virtual-address 172.10.0.1;
priority 80;
accept-data;
track {
interface ge-0/0/0 {
priority-cost 20;
The event-options traceoptions indicate that the event triggered and that it invoked the configuration change.
Mar 22 18:44:41 Processing event <PING_TEST_FAILED>
Mar 22 18:44:41 policy <vrrp-failover> should now be executed
Mar 22 18:44:41 changing configuration for policy 'vrrp-failover' triggered on receipt of event 'PING_TEST_FAILED', with '/tmp/evt_cmd_QZL62U' as the temporary command file
Mar 22 18:44:41 Initialize eventd with newset of arguments to change configuration
However, we see there is no new change in "show system commit" and the priority configuration that we expected to be changed by the event options still looks the same:
priority 80; <<<<<<<<< Did not change to 10 as per the event-options
Any time new event-options configurations are being used to make configuration changes, those changes should be tested first with a "commit check".
[edit]
root@srx345# set interfaces irb unit 100 family inet address 172.22.64.2/18 vrrp-group 1 priority 10
root@srx345# commit check
[edit interfaces irb unit 100 family inet address 172.10.0.2/24]
'vrrp-group 1'
'priority-cost' for worst case must not exceed configured 'priority' for 'vrrp-group'
error: configuration check-out failed
root@srx345#
In this case, the priority cannot be set to 10, because the effect of the event options would allow a scenario where the priority-cost could lower the priority to below 0. The solution is to change the event-options to change the priority to something greater than 20.
set interfaces irb unit 100 family inet address 172.10.0.2/24 vrrp-group 1 priority 30
2024-03-23 : Article Created