05-08-2022 11:38 PM - edited 05-08-2022 11:39 PM
Hello Team.
Through the logs below we found a path monitoring failure and have a question to discuss.
#show_log_system.log
2022/05/05 11:03:36 critical routing defaul path-mo 1 Path monitoring for static route destination 0.0.0.0/0 with next hop 221.165.217.2 recovered. Route restored.
2022/05/05 11:02:50 info dhcp lease-s 0 DHCP lease started ip 192.168.4.172 --> mac 04:b4:29:fb:3c:25 - hostname Galaxy-A30, interface ethernet1/11
2022/05/05 11:02:34 critical routing defaul path-mo 1 Path monitoring failed for static route destination 0.0.0.0/0 with next hop 221.165.217.2. Route removed.
#routed.log
2022-05-05 11:02:34.528 +0900 MON: status update md(64: 221.165.217.7 => 221.165.217.2 => 221.165.217.2) Failed
2022-05-05 11:02:34.528 +0900 MON: status update monitor(vr default: 0.0.0.0 > 221.165.217.2) Down
2022-05-05 11:02:36.524 +0900 MON: status update md(64: 221.165.217.7 => 221.165.217.2 => 221.165.217.2) Success
2022-05-05 11:02:36.524 +0900 MON: status update monitor(vr default: 0.0.0.0 > 221.165.217.2) Up
2022-05-05 11:02:36.524 +0900 MON: hold timer schedule for 60 sec.
2022-05-05 11:02:36.524 +0900 MON: status update schedule hold!
2022-05-05 11:02:47.062 +0900 IFMon: refresh ifstates, server path sw.dev.runtime.
Our customer has configured an route path-monitoring but it was downed by an unknowed issue.
We have checked the dp-monitor log, syslog and HA-agent log but we couldn't find any issue.
Thanks.
