Submit a ticketCall us

WebinarUpcoming Webinar: Should I Move My Database to the Cloud?

So you’ve been running an on-premises SQL Server® for a while now. Maybe you’ve moved it from bare metal to a VM, and have seen some positive benefits. But, do you want to see more? If you said “YES!”, then this session is for you, as James Serra will review the many benefits that can be gained by moving your on-prem SQL Server to an Azure® VM (IaaS). He’ll also talk about the many hybrid approaches, so you can gradually move to the cloud. If you are interested in cost savings, additional features, ease of use, quick scaling, improved reliability, and ending the days of upgrading hardware, this is the session for you.

Register now.

Home > Success Center > Network Performance Monitor (NPM) > Change the polling engine configuration to ignore traps from an un-monitored device

Change the polling engine configuration to ignore traps from an un-monitored device

Table of contents
No headers

A new feature in NPM 10.7 and latter allows users to ignore traps from a device, that is not monitored by current polling engine. When the device is assigned to a polling engine, this polling engine accepts traps from that device. If you re-assign the device to a different poller, that poller will start receiving the traps from the device and the old poller will no longer receive the traps from this device.

 

Please follow these steps to ignore duplicate traps from different polling engines:

  1. Stop the Orion Services - How to Start/Stop Orion Services.
  2. Go to the installation folder C:\Program Files (x86)\SolarWinds\Orion.
  3. Edit SWTrapService.exe.config and set the following settings:
  4. Click Save, and then click Close.
  5. Start the Orion Services - How to Start/Stop Orion Services.

 

Applies to: NPM v10.7 and later.

Last modified

Tags

Classifications

Public