Configure SNMP Trap Handling

NetLD can send traps on certain events (e.g. when device configuration changes are detected) and execute actions when it receives traps (e.g. run discovery). This section describes how to configure NetLD to send and receive traps successfully.

Send traps on events

To send traps on events, select the events that you wish to subscribe to and specify where you want NetLD to send the traps to (trap destinations).

  1. Click [Settings] on the Global Menu.

  2. Click [SNMP Traps] and select the events.

Event Trigger SNMP Trap Action
Device configuration changes are detected Sends an SNMP trap when it detects that the device configuration has changed since the last backup.
Devices are added and deleted Sends SNMP traps when devices are added/removed.
A backup failure Sends an SNMP trap if configuration backup fails.
A job completes with errors Sends an SNMP trap if job execution fails.
The compliance status of a device changes Sends SNMP traps when compliance status changes.
The status of bridge changes Sends an SNMP trap when the connection status between the smart bridge and core server changes.
(*Displayed only when the optional license is valid)
An audit event occurs Sends an SNMP trap when a user logs in/logs out.
A change approval action occurs Sends an SNMP trap when a job approval event occurs.
An email failure If email sending fails, an SNMP trap will be sent.
  1. To add a trap destination, click the button.

Enable/disable trap-triggered discovery

The trap-triggered discovery feature allows NetLD to automatically discover and add previously unknown devices that send SNMP traps to the server. If there are multiple networks configured in the product, the server will employ heuristics to determine which network the device belongs to based on the source IP address of the trap. SNMP credentials for the network must be configured in advance for successful discovery. There are also delays of up to several minutes introduced to prevent excessive discovery attempts and to allow batch discovery of multiple traps from devices in the same network. Devices that fail discovery will have subsequent traps ignored for a period of five minutes before discovery can again be triggered. Devices that are discovered but subsequently deleted cannot trigger a discovery until the next time the server is restarted.

Enable or disable trap triggered discovery by using the checkbox “Attempt discovery upon trap from unknown device.”

Receive traps by SNMP v1/v2c

If there are no configured SNMP v1/v2 community strings, all SNMP v1/v2 traps will be accepted. However, if you wish to enforce that SNMP v1/v2 traps present only verified community strings, they must be specified in [Settings]. Once defined, only traps that present a matching community string will be accepted.

To add SNMP v1/v2c trap community strings:

  1. Click [Settings] to open the [Server Settings] window and click the [SNMP Trap Users] item from the list on the left.

  2. Click the button at the bottom right, below the SNMP v1/v2 table, to begin.

  3. Fill in the community string that will be used for authenticating incoming SNMP Traps.

  4. Click the [OK] button at the bottom right.

  5. To save changes, click the [OK] button at the bottom right of the [Server Settings] window.

Receive traps by SNMPv3

To receive SNMP Traps by SNMPv3, it is required to set up credentials in advance so that NetLD can authenticate and/or decrypt incoming SNMP Traps.

  1. Click [Settings] to open the [Server Settings] window and click the [SNMP Trap Users] item from the list on the left.

  2. Click the button at the bottom right, below the SNMP v3 table, to begin.

  3. Fill in the SNMPv3 user information that will be used for authenticating and/or decrypting incoming SNMP Traps.

  4. Click the [OK] button at the bottom right.

  5. To save changes, click the [OK] button at the bottom right of the [Server Settings] window.