The system was generating approx four SNMP_TRAPS per minute for 1.3.6.1.4.1.2636.3.63.1 (jnxLicenseAboutToExpire), which corresponds to the notification for license expiration, three months prior to the license expiry date. This notification window is too long for the customer’s environment, as their renewal preparation typically begins around that time.

System configuration for SNMP trap.

set snmp community public authorization read-only

set snmp trap-options source-address 10.X.X.X

set snmp trap-group TRAP-GROUP version all

set snmp trap-group TRAP-GROUP destination-port 1620

set snmp trap-group TRAP-GROUP categories chassis

set snmp trap-group TRAP-GROUP categories link

set snmp trap-group TRAP-GROUP categories startup

set snmp trap-group TRAP-GROUP targets 10.X.X.X

System's version:

Model: vSRX

Junos: 23.2R1-S1.6

There is a known issue where the no. of SNMP traps specific to license expiration is not in sync with the standard time slab for alarms frequency. It should have been only once a week when there are 3 months left. This has been fixed starting 24.2R2 junos:24.3R1 junos:24.4R1.

Please check PR details: PR1777649