The snmpgtw subscribes directly to the alarm subject on the message bus. This gives snmpgtw an unfiltered view of all alarms before alarm-enrichment or nas processing. To setup snmpgtw to be more specific as to what traps get set out we can setup a new "outbound" queue and forward alarms to it via nas Auto-Operator (AO) profiles.
Environment
Release: Any Component: nas 4.73+
Resolution
Create a NEW ATTACH queue called snmpgtw with the subject of 'outbound,' or for example 'SPECTRUM_alarms,' within the hub queues configuration.
In the snmpgtw probe raw configuration, change the key "subject" with the existing value of "alarm" to "outbound" or for example, 'SPECTRUM_alarms.'
Open the nas probe and create a new Auto-Operator profile
Set the Action type to "repost"
Use Action mode of "On Message Arrival"
Change the Subject to "outbound" or "SPECTRUM_alarms"
Set the appropriate matching criteria for the alarms you want to repost.
In the case of Spectrum alarms, when the steps above are followed, then the nas will process the alarms first before sending them to Spectrum. (instead of the snmpgtw).
For testing this configuration it is best to have 2 alarms being frequently generated, e.g., by ntevl, one which is being excluded by the preprocessing rule and another which is not being excluded which should make it to Spectrum.
Additional Information
The snmpgtw probe sits on the bus and by design it will forward alarms directly to the profile destination without interacting with the nas probe. For this reason if you want to exclude alarms from being sent to the profile destination, or process them via AO, etc. you will want to process them with the above configuration change.