Customer may receive alarm on MX10003 after downgrading or rebooting the box.
labroot@milky-re0> show chassis alarms
Jan 16 02:59:29
1 alarms currently active
Alarm time Class Description
2024-01-16 01:41:22 UTC Minor VMHost RE 0 host lclksyncd Application failed
customer observes the alarm as below
When checking from the virtual host shell you would see that the application is not running.
labroot@milky-re0> start shell user root
root@milky-re0:/var/crash # vhclient -s
Last login: Tue Jan 16 07:11:09 PST 2024 from milky-re0 on pts/1
root@milky-re0-node:~# ps -aux | grep lclksyncd
root 25850 0.0 0.0 6720 828 pts/1 S+ 07:42 0:00 grep lclksyncd
On all Junos VMhost based platforms, the lclksyncd process alarms are seen when downgrade from LTS19/ LTS22 image to WRL6 due to change in rpm versions. There is no service impact due to this issue.
We can use the below temp workaround to clear the alarm.
root@milky-re0:~ # vhclient -s
Last login: Thu Oct 19 15:28:40 PDT 2023 from milky-re0 on pts/1
root@milky-re0-node:~# lclksyncd
PCI device with id: 155 found! bus17 dev0
Spawning [ LCLKSYNCD ]
root 4590 0.1 0.0 271852 4776 ? Ss 2023 293:04 lclksyncd
PS: This workaround is temporary and a reboot will trigger the alarm again.