Submit a ticketCall us

AnnouncementsTHWACKcamp 2018 is here

2018 is the seventh year for THWACKcamp™, and once again we’ll be live October 17 – 18 with packed session tracks covering everything from network monitoring and management, to change control, application management, storage, cloud and DevOps, security, automation, virtualization, mapping, logging, and more.

Register for online sessions.

Home > Success Center > Network Performance Monitor (NPM) > NPM - Knowledgebase Articles > How to forward incoming SNMP trap messages to another server

How to forward incoming SNMP trap messages to another server

Table of contents

Updated: October 9, 2017

Overview

This article describes how to forward incoming SNMP trap messages received by a SolarWinds server to a secondary management server (such as Kiwi Syslog). 

Environment

  • NPM 11.0 and later

Steps

TCP port 162 is reserved to listen for incoming trap messages from monitored devices within a SolarWinds deployment. After the messages are processed by the SolarWinds server, you can forward the messages to a secondary server.

If you are unable to receive trap messages from your targeted devices, see How to verify if SNMP traps are received by your Orion server

  1. Log in to the targeted SolarWinds server.
  2. Open the Trap Viewer.
  3. Click the yellow warning icon in the menu bar and select Add Rule. image.png
  4. In the Rule Name field, enter a name for the new rule. Capture1.JPG
  5. Enter the IP addresses that will be forwarded to the secondary server.
    Enter [ * ] to apply this rule to all trap messages.
  6. Click the Alert Actions tab.
  7. Click Add Action and select Forward the Trap.Capture2.JPG
  8. Enter the hostname or IP Address of the secondary server that receives the incoming trap message. 3Capture.JPG
  9. Select any additional options, and then click OK. 

 

 

Last modified

Tags

Classifications

Public