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
Store

Free Trial NTM

Downloaded the App this morning and began to work with it. Using SNMPv3 with MD5 and DES. No polling is attempted. RED error message beside MD5 "MD5 method is not FII". Cannot proceed any further. What am I missing?

Also, is this a more in depth product than the mapper included in the Engineering Toolset? Will this one transfer into Visio correctly? The one included in the Eng Toolset will not transfer Interface descriptions in to Visio.....just lines and switch names.

Thanks for any replies!

Find more posts tagged with

Accepted answers

All comments

bkyle

Please try the following:

1. In NTM, click Help\Support Tools\Grab SNMPWALK

2. Enter the IP address of one of your nodes with the correct SNMP v3 information, and click Scan

Do you get back information?

alabama

I have Paessler SNMP tool and it does work fine with it. Tried it this AM right after NTM failed just to be sure. Also I am running SW UDT via SNMPv3 queries and they work just fine.

alabama

BTW, I had a sniffer running and never seen NTM attempt to make the query. It just refuses my SNMPv3 parameters I enter to set up a New SNMP credential. Errors out at stated above.

alabama

The SNMP Walk tool perform the scan just fine. I had to re-install NTM. But as you can see above, I never get any further on setting up credentials for NTM to do the 1st scan.

sean.martinez

To loop in the thread for closure, what the error was stating was that FIPS encryption was enabled in the OS registry. FIPS requires SHA Authentication for SNMPv3 devices. FIPS enabled systems will have issues connecting to SNMPv2 and SNMPv3 MD5 systems due to the increased security on the OS.

alabama

Thanks Sean, turning off FIPS did the job!