Community
- Command Central
- MVP Program
- Monthly Mission
- Blogs
- Groups
- Events
- Media Vault
Products
- Observability
- Network Management
- Application Management
- IT Security
- IT Service Management
- System Management
- Database Management
Content Exchange
- SolarWinds Platform
- Server & Application Monitor
- Database Performance Analyzer
- Server Configuration Monitor
- Network Performance Monitor
- Network Configuration Manager
- SQL Sentry
- Web Help Desk
Free Tools & Trials

How do traps from unmanaged devices get handled ?

Hi, new to solar winds and have spent a week with a consultant watching it get setup. Interested in catching device up traps from a unmanaged node to enable us to keep track of new devices added to the network. But after a lot of reading and head scratching it looks like snmp traps from unmanaged objects are just discarded with no processing.

Hoping an expert will tell me that's not the case

Find more posts tagged with

snmp traps from unmanaged nodes

Accepted answers

RichardLetts

This post was impetus to knock up a couple of reports

See:

Traps from unknown devices report

Syslog from unknown devices report

Hope this is helpful for tracking down people who add random assets to the network.

All comments

RichardLetts

for SNMPv1/v2 They get stored in the database (as do syslogs); unfortunately the NODEID will be zero.

(I don't have any SNMPv3 devices sending traps)

You can search for them by IP address (if you know it).

fellowsm

Richard

So unsolicited traps are stored – can I write some SWQL to report on NODEID = 0 ?

Mike

Mike Fellows | Senior OSS Specialist

Direct: 07701319753 | Mobile: 07701319753

E-mail: Mike.Fellows@telent.com | Web: www.telent.com<http://www.telent.com>

telent Technology Services Ltd. Registered in England. No 703317.

Registered Office: Point 3, Haywood Road, Warwick, CV34 5AH, England

telent Technology Services Limited is authorised and regulated by the Financial Conduct Authority for credit-related regulated activities

telent_new_logo1.png

RichardLetts

This post was impetus to knock up a couple of reports

See:

Traps from unknown devices report

Syslog from unknown devices report

Hope this is helpful for tracking down people who add random assets to the network.

RichardLetts

yes, see my next reply that links to such reports.

RichardLetts

... and once you've got the missong nodes added you might want to link the historical data, so here the the queries for the database manager

CAUTION DRAGONS AHEAD, proceed with caution beyond this point

fix trap data

update tset t.nodeid = n.nodeidfrom traps tinner join nodes n on n.ip_address=t.ipaddresswhere t.nodeid=0

fix syslog data

update sset s.nodeid = n.nodeidfrom syslog sinner join nodes n on n.ip_address=s.ipwhere s.nodeid=0

fellowsm

Richard

Thanks for the update will have a play and see what I can get

Mike

Mike Fellows | Senior OSS Specialist

Direct: 07701319753 | Mobile: 07701319753

E-mail: Mike.Fellows@telent.com | Web: www.telent.com<http://www.telent.com>

telent Technology Services Ltd. Registered in England. No 703317.

Registered Office: Point 3, Haywood Road, Warwick, CV34 5AH, England

telent Technology Services Limited is authorised and regulated by the Financial Conduct Authority for credit-related regulated activities

telent_new_logo1.png

sja

Try kiwisyslog as a filter to your traps before forwarding them to NPM...

You can just make a "display" or log to that source traps that you don't expect.

It will keep your NPM setup much healthier...

fellowsm

Sja

Cheers

Mike

Mike Fellows | Senior OSS Specialist

Direct: 07701319753 | Mobile: 07701319753

E-mail: Mike.Fellows@telent.com | Web: www.telent.com<http://www.telent.com>

telent Technology Services Ltd. Registered in England. No 703317.

Registered Office: Point 3, Haywood Road, Warwick, CV34 5AH, England

telent Technology Services Limited is authorised and regulated by the Financial Conduct Authority for credit-related regulated activities

telent_new_logo1.png