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

Certain imported nodes show wrong SNMP version

Hi,

I'm running a nightly DB import from Orion NPM to NCM. Almost everything on it works like clockwork; it never fails to miss newly added devices from NPM, in imports all my synced custom properties and tied in with a nightly config download job it takes a lot of hassle out of node management between the 2 systems. Everything an administrator could ever want ay? Well no quite.

For some reason I have noticed that certain devices are being imported from NPM and added to NCM with SNMP v1 as their version. None of our devices are running SNMP v1 and I can see in the NPM database that the devices in question are stored as SNMPv2 as they should be.

Any idea why it's importing certain nodes in and assigning the SNMP version as version 1?

Thanks

Find more posts tagged with

Accepted answers

All comments

chris.lapoint

Can you check your mapping for the NCM attribute SNMPLevel to ensure it is matched with the appropriate NPM database field? It could be that nothing is mapped so it just defaults to SNMP v1.