Traps

StarlingX supports SNMP traps. Traps send unsolicited information to monitoring software when significant events occur.

The following traps are defined.

• wrsAlarmCritical

• wrsAlarmMajor

• wrsAlarmMinor

• wrsAlarmWarning

• wrsAlarmMessage

• wrsAlarmClear

• wrsAlarmHierarchicalClear

StarlingX alarms are mapped into one of the above traps based on severity, and customer logs are mapped into the ‘Message’ trap.

Note

StarlingX uses Wind River Systems (wrs) Enterprise Registration and Alarm MIBs. See SNMP Overview for details.

For Critical, Major, Minor, Warning, and Message traps, all variables in the active alarm table are included as varbinds (variable bindings), where each varbind is a pair of fields consisting of an object identifier and a value for the object.

For the Clear trap, varbinds include only the following variables:

• wrsAlarmActiveAlarmID

• wrsAlarmActiveEntityInstanceID

• wrsAlarmActiveDateAndTime

• wrsAlarmActiveReasonText

For the HierarchicalClear trap, varbinds include only the following variables:

• wrsAlarmActiveEntityInstanceID

• wrsAlarmActiveDateAndTime

• wrsAlarmActiveReasonText

For all alarms, the Notification Type is based on the severity of the trap or alarm. This is done to facilitate the interaction with most SNMP trap viewers which use the Notification Type to drive the coloring of traps, that is, red for critical, yellow for minor, and so on.

See https://opendev.org/starlingx/snmp-armada-app/src/branch/master/stx-snmp-helm/centos/docker/stx-snmp/mibs/wrsAlarmMib.mib.txt for alarm details.