SNMP Trap Condition

Description

Monitors for a specific SNMP trap related action and evaluates as TRUE when the condition is met. An SNMP trap is a message sent by an agent to a management system indicating that an event has occurred on the host running the agent. This condition can be set as one of the following workflow elements:

  • Trigger element - When positioned in the beginning of a workflow, triggers its execution when the monitored condition (that is, an enterprise specific trap is received from a specified device) evaluates to TRUE.

  • Wait element - Suspends execution of a running workflow until the monitored condition (that is, any trap is received from any device) valuates to TRUE.

  • Conditional element - Determines the course of a workflow depending on whether or not a specific condition (that is, when a specific trap code is received) evaluates to TRUE.

Practical usage

Used to integrate tasks with other network systems management software.

Related Topics  

Parameters

General

Property Type Description
Agent IP Address Options Specifies whether the condition will start the task when a trap is received from any device or only devices within a specific IP range. The available options are:
  • Any - The task will run when a trap is received from any host with no IP address restrictions.
  • Specific - The task will only run when a trap is received from a host within the specified IP Address Range.
  • IP range start - Specifies the starting IP address of the range of acceptable IP addresses. This parameter is available only if the Agent IP address parameter is set to Specific.
  • IP Range Ends: Specifies the ending IP address of the range of acceptable IP addresses. This parameter is available only if the Agent IP address parameter is set to Specific.
Community Options Specifies whether the condition will start the task when a trap is received from a device from any community or only devices within a specific community. The available options are:
  • Any - The task will run when a trap is received from any host with no community restrictions.
  • Specific - The task will only run when a trap is received from a host within the specified community.
  • Community - Specifies the community that the monitored trap must originate from. This parameter is available only if the Community parameter is set to Specific.
Enterprise OID Options Specifies whether the condition will start the task when a trap is received from any Enterprise OID device or only devices within a specific Enterprise OID. The available options are:
  • Any - The task will run when a trap is received from any enterprise OID with no enterprise OID restrictions.
  • Specific - The task will only run when a trap is received from a host within the specified enterprise OID.
  • Specific enterprise OID - Specifies the enterprise OID that the monitored trap must originate from. This parameter is available only if the Enterprise OID parameter is set to Specific.
Trap generic type Options Specifies that the condition will filter out traps that are not intended for a specific generic type and act on traps received only from a specific generic type. The available options are:
  • Any  
  • Enterprise Specific - Signifies that the sending protocol entity recognizes that some enterprise-specific event has occurred. The Trap type code field identifies the particular trap that occurred.
  • Cold Start - Signifies that the sending protocol entity is reinitializing itself so that the agent's configuration or the protocol entity implementation can be altered.
  • Warm Start - Signifies that the sending protocol entity is reinitializing itself so that neither the agent configuration nor the protocol entity implementation can be altered.
  • Link Down - Signifies that the sending protocol entity recognizes a failure in one of the communication links represented in the agent's configuration.
  • Link Up - Signifies that the sending protocol entity recognizes that one of the communication links represented in the agent's configuration has come up.
  • Authentication Failure - Signifies that the sending protocol entity is the addressee of a protocol message that is not properly authenticated.
  • EGP Neighbor Loss - Signifies that an EGP neighbor for whom the sending protocol entity was an EGP peer has been marked down and the peer relationship no longer exists.
Trap specific type  Options Indicates whether the condition will act on any enterprise specific trap type or monitor for the occurrence of a specific trap type code. This parameter is active only if the Trap generic type parameter is set to Enterprise Specific. The available options are:
  • Any - The condition will listen to traps sent with any Code.
  • Specific - The condition will only listen for traps sent with the code specified in the specific code parameter.
    • Trap specific code type: Specifies the trap specific code type.
Use String notation for OIDs Yes/No If enabled, IODs will be entered as string notations (disabled by default).
Use String notation for timetick values Yes/No If enabled, timetick values will be entered as string notations (disabled by default).

Authentication

Property Type Description
Accept authenticated traps from these users Options Specifies the users in which to accept authenticated traps. Click the Click here to add new item link to add a new item. The available values are:
  • User - Enter the username
  • Auth. Type - Enter the authentication type. The available options are:
    • Any (default)
    • MD5
    • SHA
    • SHA2
  • Auth. Password - Enter the password
  • Encryption - Enter the encryption type. The available options are:
    • No encryption (default)
    • DES
    • AES
    • 3DES
    • AES192
    • AES256
  • Private Password - Enter the private password related to the encryption type.
Accept authenticated Version 3 traps Yes/No If enabled, Version 3 traps will be accepted (disabled by default).

Behavior

The Behavior properties dictate how the system should react upon the occurrence of a condition. These properties are significant in determining whether the Automate condition should act as a trigger object (used to fire off workflow execution), wait object (used to suspend workflow execution) or conditional (decision making) object.

More on Condition Behavior

Additional notes

AMTrigger

When the Key event is used to trigger workflow execution, it automatically creates an AMTrigger dataset which can be used much like the datasets created by the Database - SQL query activity and Email action. The fields that AMTrigger generates can be used to determine properties of the object that caused the workflow to launch, such as the type of trigger, when the trigger was activated and what system event or condition took place to activate the trigger. Along with a collection of global AMTrigger fields that are created and populated by every instance of AMTrigger, a unique set of AMTrigger fields exclusive to each Automate trigger are created as well.

To view AMTrigger values exclusive to the SNMP Trap condition, see AMTrigger - SNMP Trap.

AMCondition

When the SNMP Trap condition is used in the middle of a workflow as wait or conditional object, it automatically creates an AMCondition dataset. Similar to AMTrigger, the fields that AMCondition generates can be used to determine properties of the object that caused the condition to activate. Along with a collection of global AMCondition fields that are created and populated by every instance of AMCondition, a unique set of AMCondition fields exclusive to each Automate condition are created as well.

To view AMCondition values exclusive to the SNMP Trap condition, see AMCondition - SNMP Trap.

NOTE: A full list of AMTrigger and AMCondition fields exclusive to each trigger/condition can be viewed from Expression Builder by expanding the Objects folder and selecting the desired object from either the Triggers or Conditions folder.