The SNMP plug-in can receive SNMP traps by running a workflow, which waits for a single trap message, or with a policy, which can handle traps continuously. The plug-in supports SNMPv1 and SNMPv2c traps.

Wait for a Trap on an SNMP Device

You can run a workflow that waits to receive an SNMP trap from a specified device.

This workflow features a trigger, which stops the run of the workflow and waits for an SNMP trap before continuing. When a trap is received, the workflow run resumes. You can use the workflow as part of more complex workflows, or as a sample that you can customize or extend for a specific need.

Prerequisites

  • Verify that you are logged in to the Automation Orchestrator Client as an administrator.
  • Verify that you have a connection to an SNMP device from the Inventory view.

Procedure

  1. Navigate to Library > Workflows and enter the snmp tag in the workflow search box.
  2. Locate the Wait for a trap on an SNMP device workflow and click Run.
  3. Select the device on which you want to wait for an SNMP trap.
  4. (Optional) In the OID text box, enter the object identifier of a specific trap.
    Note: If you leave the text box empty, the workflow run resumes after receiving any trap from the specified SNMP device.
  5. Click Run.

Set an SNMP Trap Policy

You can set a policy to continuously listen for traps from an SNMP device that is already registered in the plug-in inventory.

Prerequisites

  • Verify that you are logged in to the Automation Orchestrator Client as an administrator.
  • Verify that you have a connection to an SNMP device from the Inventory view.

Procedure

  1. In the Automation Orchestrator Client, navigate to Library > Policies.
  2. Open the SNMP Trap policy template and click Run.
  3. Enter a name for the policy that you want to create.
  4. (Optional) Enter a description for the policy.
  5. Select an SNMP device for which to set the policy.
  6. Click Run to create the policy.
    The Automation Orchestrator Client switches to Run perspective.
  7. On the Policies view, right-click the policy that you created and select Start policy.

Results

The trap policy starts to listen for SNMP traps.

What to do next

You can edit the SNMP Trap policy.

Configure an SNMP Trap Host Policy

With the SNMP Trap Host policy listens for SNMP traps from hosts that might not be added as registered SNMP devices.

Prerequisites

  • Verify that you are logged in to the Automation Orchestrator Client as an administrator.
  • Verify that you have a connection to an SNMP device from the Inventory view.

Procedure

  1. In the Automation Orchestrator Client, navigate to Library > Policies.
  2. Open the SNMP Trap Host policy template and click Run.
  3. Enter a name for the policy that you want to create.
  4. (Optional) Enter a description for the policy.
  5. Select Trap Host (Online) from the inventory tree.
  6. Click Run to create the policy.
    The Orchestrator client switches to Run perspective.
  7. Right-click the policy and select Edit.
  8. In the Scripting tab, expand host > OnTrapAll.
    1. Select a workflow or a script to associate with the policy.
  9. Click Save and close to apply the edited settings.
  10. On the Policies view, right-click the policy that you edited and select Start policy.

What to do next

You can edit the SNMP Trap Host policy.

Edit a Trap Policy

You can edit a trap policy to customize it for a specific use case. When you edit a trap policy, you can change its priority and startup settings, and customize the scripting and permissions associated with the policy.

Prerequisites

  • Verify that you are logged in to the Automation Orchestrator Client as an administrator.
  • Verify that you have a connection to an SNMP device from the Inventory view.

Procedure

  1. In the Automation Orchestrator Client, navigate to Library > Policies.
  2. If the policy that you want to edit is running, right-click the policy and select Stop policy.
  3. Right-click the policy and select Edit.
  4. From the General tab, edit the startup settings, priority, and description of the policy.
  5. (Optional) From the Scripting tab, you can associate a specific workflow or scripting code with the policy, for integration in a more complex scenario.
    You can set the policy to trigger a custom workflow when a trap is received.
  6. (Optional) From the Permissions tab, you can modify the access rights.
    You can give permissions to a user or to a group to start the policy, without giving permissions to edit the policy.
  7. Click Save and close to apply the edited settings.
  8. On the Policies view, right-click the policy that you edited and select Start policy.