Generating SNMP traps

You can generate and send Niagara alarms (in the form of SNMPv1 traps) to a defined SNMP manager whenever a new Niagara alarm record is routed to the SnmpRecipient. In order to generate SNMP traps you must setup and configure the SnmpRecipient on a station running an SnmpNetwork. This includes placing an SnmpRecipient component under the AlarmService component, configuring it to enable trap generation and designating a valid SNMP network manager. Refer to SnmpRecipient configuration for details.

Once the proper IP address and port are assigned for the SNMP network manager, the SnmpRecipient component must have a link to an appropriate Alarm Class under the Alarming Service in order to provide the Niagara Alarm source for the generation and routing of SNMP trap messages to the network manager. You add SnmpRecipient components under the AlarmService by copy-and-paste from the SNMP module palette. You can add as many SnmpRecipients as you need to configure your SNMP integration. Figure 14 shows an SnmpRecipient component linked to the Default Alarm Class. In this example, any Niagara alarms routed to the Default Alarm Class are also routed to the SnmpRecipient. The SnmpRecipient then packages the alarms into SNMP trap messages and sends them to the specified SNMP network manager.

Figure 14. SnmpRecipient linked to default alarm class

All SNMP traps generated and sent by the SnmpRecipient are SNMPv1 messages. The SNMP driver currently does not support generating and sending SNMPv2 trap messages.

To configure a station for SNMP trap generation

To configure a station for SNMP trap generation, you must first have an SNMP network established and running in your station. (See Adding an SnmpNetwork).

Open the SNMP palette in the Workbench palette side bar.
Under the Trap Generation folder, drag and drop an SnmpRecipient component onto the AlarmService property sheet or onto the AlarmService component in the nav tree.
Select the property sheet view of the SnmpRecipient and set the Time Range, Days of Week, and Transitions properties as desired. See SnmpRecipient properties for details.
On the SnmpRecipient property sheet, set the Route Acks property to True and choose the following options:
- Route Alarms To Network Manager As Traps
  
  If this option is not selected, traps are not routed.
- Use SnmpNetwork’s Default Network Manager
  
  If this option is selected, traps report using the network manager that is defined in the Default Network Manager properties. If this property option is not selected, then the alarms are reported as traps using the network manager that is defined in the Network Manager Config properties.
Set the following Network Manager Config properties if you choose to use an SnmpNetwork Manager other than the SnmpNetwork’s Default Network Manager.
These properties are read-only unless you clear (do not select) the SnmpNetwork’s Default Network Manager option field under the Rout Acks property.
- Network Manager IP Address
  
  Type in the address of the SnmpNetwork manager that you want to use.
- Use SnmpNetwork’s Default Network Manager
  
  If this option is selected, traps report using the network manager that is defined in the Default Network Manager properties. If this property option is not selected, then the alarms are reported as traps using the network manager that is defined in the Network Manager Config properties.
- Network Manager Traps Community
  
  This property provides a field for you to specify a string value to use for outgoing SNMP version 1 trap messages (sent to the network manager). The default value is “public”.
On the SnmpRecipient property sheet, choose one of the following options for the Snmp Alarm Table property.
- Store Received Alarms
  
  This option specifies that alarms that are routed to this recipient are also cached in the Snmp Alarm Table. This is the default option.
- Do Not Store Received Alarms
  
  This option disables the caching of alarms for the recipient.
On the SnmpRecipient property sheet, click the Save button. SNMP trap generation is configured and enabled.