Alex,
Thank you so much again for guiding me through this process. what you advised seems to work just fine. However I was not able to get the commands (Request interface ge-0/0/3.1020 down) executed on any of the following devices/junos:
vSRX (12.1X47-D15.4)
SRX320 (junos-srxsme-17.3R1.10)
vMX (JUNOS 14.1R1.10)
MX480 (JUNOS 15.1F2.8 - AND- JUNOS 14.2R7.5)
MX960(JUNOS 10.4R8.5 - AND -JUNOS 11.4R7.5)
Therefore I had to make a minor modification to your config. I hope you dont mind.
This is my RPM config:
probe TM-Maintenance {
test TM-SouthRing-SW10 {
probe-type icmp-ping;
target address 20.20.20.4;
probe-count 10;
probe-interval 4;
test-interval 2;
routing-instance Maint;
thresholds {
successive-loss 15;
}
destination-interface ge-0/0/3.1020;
}
}
This is my event-options config:
generate-event {
1hr time-interval 240;
}
policy rpmdown-ifddown {
events PING_TEST_FAILED;
attributes-match {
PING_TEST_FAILED.test-owner matches TM-Maintenance;
PING_TEST_FAILED.test-name matches TM-SouthRing-SW10;
}
then {
change-configuration {
commands {
"set interfaces ge-0/0/3.1020 disable";
}
user-name ataheri;
commit-options {
log "Disabling ge-0/0/3.1020 to SouthRing SW10";
}
}
}
}
policy ifdup {
events 1hr;
then {
change-configuration {
commands {
"delete interfaces ge-0/0/3.1020 disable";
}
user-name ataheri;
commit-options {
log "Enabling ge-0/0/3.1020 to SouthRing SW10";
}
}
}
}
**Please note I am only using 240 Seconds instead of 3600 for testing purposes (So I dont have to wait an hour to see the results).
upto this point, everything seems to be stable and working according to the flow but I am still seeing that interface going up and down when I dont expect it to do so. I guess I dont understand the tuning part of the probes well. This is what I think the probe should do with my current config:
1- send out 1 probe every 4 seconds - total of 10 probes which should take about total of 40 seconds.
2- after 10 probes, wait 2 seconds and start from step 1 again
3-in order for this test to be "Failed" I have to see total of 15 continuous probes fail, which with my config should take about 60 seconds.
4- once 15 probes fail, disable the port, and bring the port back up after 240 seconds. (I understand this might be as short as 1 second or as long as 479 seconds depending on when the timer on the probe actually kicks in)
5- once the port is back up, start the icmp-ping probe, Basically back to step 1
Did I understand this wrong ? if yes, can you please provide some examples revolving around these timers ?
I also have two follow up questions:
1- Is there a way to have both probes and Periodic "ticking" event timers aggree/coordinate only on one timer so we dont see such variation as you explained and also seen in my step4 ?
2- I am not able to see the logs in my "Show log messages" section. what am I missing and where should I be looking for these log messages coming from my event-option policy when commiting ?
As always, thank you for your help and I hope you dont mind me taking so much of your time.