Observation:
The alarms are cleared with a glitch (Clear, set, clear)
eg
250.001 clear (2020-09-28 08:54:23.200403)
250.001 set (2020-09-28 08:54:26.254063)
250.001 clear (2020-09-28 08:54:31.006866)
By looking at var/log/bash.log
the history of config update and and config apply (lock/unlock)
Observation:
There is a continuously appearing error in sm.log from 2020-09-28T08:46:09 to 2020-09-28T16:18:06 (tens of times each second)
controller-0 sm: debug time[3290.984] log<75888> ERROR: sm[93126]: sm_msg.c(880): Failed to send message on socket for interface (vlan49), error=Network is unreachable.
controller-0 sm: debug time[3290.984] log<75890> ERROR: sm[93126]: sm_msg.c(880): Failed to send message on socket for interface (vlan48), error=Network is unreachable.
From networking.info
---
48: vlan48@oam0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc htb state UP mode DEFAULT group default qlen 1000
link/ether 3c:fd:fe:b5:7e:ec brd ff:ff:ff:ff:ff:ff
RX: bytes packets errors dropped overrun mcast
3546091 37207 0 0 0 61
TX: bytes packets errors dropped carrier collsns
13365456 66206 0 0 0 0
49: vlan49@oam0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP mode DEFAULT group default qlen 1000
link/ether 3c:fd:fe:b5:7e:ec brd ff:ff:ff:ff:ff:ff
RX: bytes packets errors dropped overrun mcast
0 0 0 0 0 0
TX: bytes packets errors dropped carrier collsns
3822854 27905 0 0 0 0
---
fd01:13::4 dev vlan48 used 3/2987/0 probes 6 FAILED
By looking at var/extra/ database/ fm.db.sql. txt
the history of alarms set and cleared is like this:
Alarms Set Alarm cleared
2020-09-28 08:46:31.456314 --- 2020-09-28 08:54:31.006866
2020-09-28 09:44:32.492961 --- 2020-09-28 10:40:30.987332
2020-09-28 11:37:33.310559 --- 2020-09-28 12:17:32.351701
2020-09-28 12:46:59.391213 --- 2020-09-28 16:01:19.306163T
Observation:
The alarms are cleared with a glitch (Clear, set, clear)
eg
250.001 clear (2020-09-28 08:54:23.200403)
250.001 set (2020-09-28 08:54:26.254063)
250.001 clear (2020-09-28 08:54:31.006866)
By looking at var/log/bash.log
the history of config update and and config apply (lock/unlock)
2020-09- 28T12:46: 58.000 clock_synchroni zation= ptp 28T13:38: 54.000 clock_synchroni zation= ntp
2020-09-
2020-09- 28T13:39: 10.000 host-lock controller-0 28T13:39: 56.00 host-unlock controller-0
2020-09-
2020-09- 28T14:53: 59.000 clock_synchroni zation= ptp 28T14:55: 10.000 clock_synchroni zation= ntp
2020-09-
2020-09- 28T15:00: 46.000 clock_synchroni zation= ptp 28T15:01: 46.000 clock_synchroni zation= ntp
2020-09-
2020-09- 28T15:07: 54.000 clock_synchroni zation= ptp 28T15:08: 54.000 clock_synchroni zation= ntp
2020-09-
2020-09- 28T15:09: 10.000 host-lock controller-0 28T15:09: 56.000 host-unlock controller-0
2020-09-
2020-09- 28T15:18: 52.000 host-lock controller-0 28T15:20: 43.000 host-unlock controller-0
2020-09-
Observation:
There is a continuously appearing error in sm.log from 2020-09-28T08:46:09 to 2020-09-28T16:18:06 (tens of times each second)
controller-0 sm: debug time[3290.984] log<75888> ERROR: sm[93126]: sm_msg.c(880): Failed to send message on socket for interface (vlan49), error=Network is unreachable.
controller-0 sm: debug time[3290.984] log<75890> ERROR: sm[93126]: sm_msg.c(880): Failed to send message on socket for interface (vlan48), error=Network is unreachable.
From networking.info MULTICAST, UP,LOWER_ UP> mtu 1500 qdisc htb state UP mode DEFAULT group default qlen 1000 MULTICAST, UP,LOWER_ UP> mtu 1500 qdisc noqueue state UP mode DEFAULT group default qlen 1000
---
48: vlan48@oam0: <BROADCAST,
link/ether 3c:fd:fe:b5:7e:ec brd ff:ff:ff:ff:ff:ff
RX: bytes packets errors dropped overrun mcast
3546091 37207 0 0 0 61
TX: bytes packets errors dropped carrier collsns
13365456 66206 0 0 0 0
49: vlan49@oam0: <BROADCAST,
link/ether 3c:fd:fe:b5:7e:ec brd ff:ff:ff:ff:ff:ff
RX: bytes packets errors dropped overrun mcast
0 0 0 0 0 0
TX: bytes packets errors dropped carrier collsns
3822854 27905 0 0 0 0
---
fd01:13::4 dev vlan48 used 3/2987/0 probes 6 FAILED