We have noticed that Juniper configurations are missing from the ncm_config table in SRM and it is because Spectrum is not always generating event 0x82105a when a config change trap comes in. How come?
Release : 20.2
Component : Spectrum Core / SpectroSERVER
Check the device configuration. If the system hostname is set to lowercase - this may be a problem. Change this to uppercase:
set groups re0 system host-name re0.<hostname-value-lowercase>
set groups re0 system host-name re0.<hostname-value-uppercase>