The customer reported observing DEPENDENCY_UNRESOLVED logs related to net::juniper::alarmd::activeAlarmObj. There was no service impact associated with the issue; however, the customer proactively shifted traffic away as a precaution.
labuser@labhost> show version invoke-on all-routing-engines
Feb 27 02:40:24
re0:
--------------------------------------------------------------------------
Hostname: labhost
Model: ptx10003-160c
Junos: 20.4R3-S4.2-EVO
Yocto: 2.2.1
Linux Kernel: 4.8.28-WR2.2.1_standard-g5382e48
JUNOS-EVO OS 64-bit [junos-evo-install-ptx-fixed-x86-64-20.4R3-S4.2-EVO]
labuser@labhost> show log messages | match DEPENDENCY
Feb 27 02:48:44
Feb 26 23:30:43 2026 labhost picd[11739]: DEPENDENCY_UNRESOLVED [op:Update][Object:0x7fcd45418540][G:846108677298][net::juniper::alarmd::activeAlarmObj]
Feb 26 23:31:43 2026 labhost picd[11739]: DEPENDENCY_UNRESOLVED [op:Update][Object:0x7fcd45418540][G:846108677298][net::juniper::alarmd::activeAlarmObj]
Feb 26 23:32:43 2026 labhost picd[11739]: DEPENDENCY_UNRESOLVED [op:Update][Object:0x7fcd45418540][G:846108677298][net::juniper::alarmd::activeAlarmObj]
Feb 26 23:33:43 2026 labhost picd[11739]: DEPENDENCY_UNRESOLVED [op:Update][Object:0x7fcd45418540][G:846108677298][net::juniper::alarmd::activeAlarmObj]
Feb 26 23:34:43 2026 labhost picd[11739]: DEPENDENCY_UNRESOLVED [op:Update][Object:0x7fcd45418540][G:846108677298][net::juniper::alarmd::activeAlarmObj]
Feb 26 23:35:43 2026 labhost picd[11739]: DEPENDENCY_UNRESOLVED [op:Update][Object:0x7fcd45418540][G:846108677298][net::juniper::alarmd::activeAlarmObj]
Feb 26 23:36:43 2026 labhost picd[11739]: DEPENDENCY_UNRESOLVED [op:Update][Object:0x7fcd45418540][G:846108677298][net::juniper::alarmd::activeAlarmObj]
Feb 26 23:37:43 2026 labhost picd[11739]: DEPENDENCY_UNRESOLVED [op:Update][Object:0x7fcd45418540][G:846108677298][net::juniper::alarmd::activeAlarmObj]
Feb 26 23:38:43 2026 labhost picd[11739]: DEPENDENCY_UNRESOLVED [op:Update][Object:0x7fcd45418540][G:846108677298][net::juniper::alarmd::activeAlarmObj]
...
labuser@labhost> show system alarms
Feb 27 02:37:35
1 alarms currently active
Alarm time Class Description
2026-02-26 23:25:40 UTC Major FPC 2 Major Errors
labuser@labhost> show system errors active detail
Feb 27 02:38:17
System Active Errors Detail Information
FPC 2
----------------------------------------------------------------
Error Name : hbm_io_pio_err
Identifier : /fpc/2/evo-cda-zx/0/cm/0/zxchip/6/hbm_io_pio_err
Description : hbm_io_pio_err
State : enabled
Scope : board
Category : internal
Level : major
Threshold : 1
Error limit : 0
Occur count : 1
Clear count : 0
Last occurred(ms ago) : 11557149
Error Name : hbm_io_timeout_err
Identifier : /fpc/2/evo-cda-zx/0/cm/0/zxchip/6/hbm_io_timeout_err
Description : hbm_io_timeout_err
Last occurred(ms ago) : 11557150
labuser@labhost> show platform dependency-state summary |except ok
Feb 27 02:41:07
Dependency state summary :
Application Node Context Status
picd re0 all ERROR
labuser@labhost> show platform dependency-state detail
Feb 27 02:50:12
picd.all (re0) Root Cause Incomplete Object Info :
GUID : 846108677298
OLC : 343597384469
Producer ID : re0::resiliencyd::50332327
Class : first class object
Type : net::juniper::alarmd::activeAlarmObj
Is del : false
Contents :
almclass : CHASSIS
almcolor : red
almobject : FPC
almreason : Major errors
almtype : System
eventId : 16759
id : 386007070
longReason : FPC 2 Major Errors
moduleId : zxchip
objectName : Fpc2
shortReason : FPC 2 Major Errors
silent : 0
slot : 2
startTime : 1772148340
AMM details :
Ref Counts
Publish : 0
BQ : 1
App-Controller : 2
Evl Tables : 0
Total : 4
Is Facade live : true
Relation count : 0
In-use in Publish : false
In-use in BQ : false
Potential Reason : This object is colliding with a newer object [Guid: 846108677300]
Potential Remedy : request system application restart app resiliencyd node re0
labuser@labhost> show platform binding-queue incomplete
Feb 27 02:41:33
picd.default (re0) Binding-Queue Object Info :
GUID : 846108677300
OLC : 343597384470
State : incomplete (--I)
eventId : 16757
App-Controller : 1
Total : 3
Is Facade live : false
Wait Guid : 0
Type : 00000000000000000000000000000000
Type Name : (null)
Root Cause Guid : 0
Waiting usr upd : false
Waiting usr inc : true
Wait for recycle : false
Is bundled : false
Potential Reason : Update is gated because the current update was gated via an explicit request by a higher layer
Potential Remedy : request system application restart app picd node re0
labuser@labhost> show platform app-controller incomplete
Feb 27 02:43:41
alarmd (re0) App controller Object Info :
Producer : re0::resiliencyd::50332327
Ref count : 0
Default stage Info
NKDB name : Controller Default
State : StateCompressed
Potential Reason : State compressed and colliding with existing live object [:Type:activeAlarmObj activeAlarmObj:2.29.23.30.2.386007070.Fpc2, guid:846108677298]
Parent : 0
license-check (re0) App controller Object Info :
picd (re0) App controller Object Info :
Ref count : 1
State : CollidingIncompleteInBQ
Potential Reason : Colliding with existing live object [:Fpc2, guid:846108677298]
There was an error on FPC2 that did not clear by itself, which eventually caused PICD to report a dependency unresolved alarm. We executed the following command to clear the errors on FPC2:
clear chassis fpc errors all fpc-slot 2
This successfully cleared the FPC2 errors, and the dependency unresolved alarm was resolved.
root@labhost> clear chassis fpc errors all fpc-slot 2
root@labhost>
Feb 27 03:26:05 2026 labhost picd[8820]: DEPENDENCY_UNRESOLVED [op:Update][Object:0x7f8ad9f919c0][G:846108677298][net::juniper::alarmd::activeAlarmObj]
Feb 27 03:27:05 2026 labhost picd[8820]: DEPENDENCY_UNRESOLVED [op:Update][Object:0x7f8ad9f919c0][G:846108677298][net::juniper::alarmd::activeAlarmObj]
Feb 27 03:28:05 2026 labhost picd[8820]: DEPENDENCY_UNRESOLVED [op:Update][Object:0x7f8ad9f919c0][G:846108677298][net::juniper::alarmd::activeAlarmObj]
Feb 27 03:29:05 2026 labhost picd[8820]: DEPENDENCY_RESOLVED [op:Update][Object:0x7f8ad9f919c0][G:846108677298][net::juniper::alarmd::activeAlarmObj]
root@labhost> show system alarms
Feb 27 03:40:28
0 alarms currently active
root@labhost> show system errors active detail
Feb 27 03:40:34
root@labhost> show platform dependency-state summary |except ok
Feb 27 03:40:50
root@labhost> show platform binding-queue incomplete
Feb 27 03:40:57
root@labhost> show platform app-controller incomplete
Feb 27 03:41:03