Performed heat threshold testing on MX we checked to see if Syslog and traps related to alarm generation when temperature is abnormal are being output.

Syslog was output, but Trap was not output.

In this scenario customer was performing heat testing on MX304, the alarm is correctly reported but there is no corresponding SNMP trap.

> show chassis alarms | no-more

Feb 27 17:48:45

6 alarms currently active

Alarm time Class Description

2024-02-27 17:41:56 JST Minor PEM 1 Temperature Fault

2024-02-27 17:38:16 JST Minor PEM 0 Temperature Fault

2024-02-27 17:22:09 JST Minor RE 1 Inlet_Right Temp Sensor Warm

2024-02-27 17:21:09 JST Minor RE 1 Inlet_Left Temp Sensor Warm

2024-02-27 17:21:00 JST Minor RE 0 Inlet_Left Temp Sensor Warm

2024-02-27 17:20:51 JST Minor RE 0 Inlet_Right Temp Sensor Warm

Feb 27 17:20:51.761 MX304_5 alarmd[15430]: Alarm set: CB id=1996488847, color=YELLOW, class=CHASSIS, reason=RE 0 Inlet_Right Temp Sensor Warm

Feb 27 17:21:00.767 MX304_5 alarmd[15430]: Alarm set: CB id=1895825551, color=YELLOW, class=CHASSIS, reason=RE 0 Inlet_Left Temp Sensor Warm

Feb 27 17:21:09.772 MX304_5 alarmd[15430]: Alarm set: CB id=2097152143, color=YELLOW, class=CHASSIS, reason=RE 1 Inlet_Left Temp Sensor Warm

Feb 27 17:22:09.809 MX304_5 alarmd[15430]: Alarm set: CB id=-2097151857, color=YELLOW, class=CHASSIS, reason=RE 1 Inlet_Right Temp Sensor Warm

This will require a new Feature Enhancement Request.

Please contact your Juniper Networks Account Team and have them submit new Feature Enhancement Request with PLM (Product Line Management) Group.

The PLM Group would then determine if feature is feasible and discuss with engineering.

Recommended following KB to generate SNMP trap.

https://supportportal.juniper.net/s/article/EX-How-to-generate-a-SNMP-trap-for-any-syslog-message ?

Basically JUNOS uses event-options to “raise-trap” which will be sent to their NMS in the same way as other traps.