Skip to main content
titanium98118
New Member
January 26, 2025
Solved

Automation Stitch with link monitor cannot be trigged properly

  • January 26, 2025
  • 3 replies
  • 2073 views

Hi,

 

EDIT:

I alreay find the solution, just set the set name using "msg", and it is working as expected.

---------------------------------------------------------------------------------------------------------------------------------

I am new to fortigate, I just got a fortigate 60e(192.168.98.99) with os version 7.4.7, and a debian device(192.168.98.178) directly conneted 60e.

I setup a link monitor on 60e in order to monitor if the debian device is online or not.

Till now, link monitor is working as expected:

 

# diagnose sys link-monitor status   Link Monitor: n1, Status: alive, Server num(1), cfg_version=0 HA state: local(alive), shared(alive) Flags=0x1 init, Create time: Sun Jan 26 16:39:12 2025 Source interface: internal5 (12) VRF: 0 Interval: 2000 ms Service-detect: disable Diffservcode: 000000 Class-ID: 0 Transport-Group: 0 Class-ID: 0   Peer: 192.168.98.178(192.168.98.178)          Source IP(192.168.98.99)         Route: 192.168.98.99->192.168.98.178/32, gwy(192.168.98.99)         protocol: ping(54321), state: alive                 Latency(Min/Max/Avg): 0.513/0.779/0.632 ms                 Jitter(Min/Max/Avg): 0.000/0.196/0.091 ms                 Packet lost: 27.000%                 MOS: 4.390                 Number of out-of-sequence packets: 0                 Fail Times(0/5)                 Packet sent: 751, received: 205, Sequence(sent/rcvd/exp): 752/752/753

 

 

I create two Stitches, the first one is when debian is offline and change fortigate's system dns to isp's one, second one is when debian is back online and change fortigate's system dns to debian's ip. I search on internet, and finding one post here https://community.fortinet.com/t5/Support-Forum/How-to-get-email-alerts-of-for-lost-internet-connectivity/td-p/268373

Using this configuration, none Automation stitch is trigged.

 

FGT60E (global) # show system automation-trigger n1\ from\ alive\ to\ dead  config system automation-trigger     edit "n1 from alive to dead"         set event-type event-log         set logid 22932         config fields             edit 1                 set name "ping"                 set value "Link Monitor changed state from alive to dead, protocol: ping."             next         end     next end  FGT60E (global) # show system automation-trigger n1\ from\ dead\ to\ alive  config system automation-trigger     edit "n1 from dead to alive"         set event-type event-log         set logid 22922         config fields             edit 1                 set name "ping"                 set value "Link Monitor changed state from dead to alive, protocol: ping."             next         end     next end

 

 

But when I delete the "set name" and "set value", it can be trigged successfully. Then the problem is link monitor will generate two logs when the debian device becomming offine, first one is  "Link monitor status warning", second one is "Link monitor status", two Stitches are being trigged at time same time.

 

My question is, how can I set the "set name" and "set value" correctly?

Thanks in advance.

Best answer by titanium98118

Thanks Anthony_E,

 

I alreay find the solution, just set the "set name" using "msg", and it is working as expected.

3 replies

Anthony_E
Staff
Staff
January 29, 2025

Hello,


Thank you for using the Community Forum. I will seek to get you an answer or help. We will reply to this thread with an update as soon as possible.


Thanks,

Best Regards
Anthony_E
Staff
Staff
February 3, 2025

Hello,

 

We are still looking for someone to help you.

We will come back to you ASAP.


Regards,

Best Regards
titanium98118
titanium98118AuthorAnswer
New Member
February 5, 2025

Thanks Anthony_E,

 

I alreay find the solution, just set the "set name" using "msg", and it is working as expected.

Anthony_E
Staff
Staff
February 6, 2025

Thank you for sharing this solution!

Best Regards