Network Topology Mapper SNMPv3 Test Credential Failed

That's an interesting situation.  If your node is configured to allow the right pollers to talk to it, and if the node and the pollers have the correct snmp-v3 strings, and if there are no routing or firewall issues present, you've got a bit of a perfect storm.

I'll mention one thing that's easy to miss--Windows Server local firewall.  I can't count the number of times a "network problem" has been put on my table that turned out to be caused by the SysAdmin forgetting that the server firewall is enabled by default in our environment.  

It sounds like you've proven the L2 and L3 paths are valid (if your new test APE can ping the node, that part's good).

I'd spend a tiny bit of time focusing on the snmp-v3 string on the node and the new Solarwinds environment.  A single character (especially an unintentionally pasted-in space at the end of a Ctrl-C to a Ctrl-V) is far to easy to accidentally put in place, thanks to Microsoft's functionality.  Sometimes this is so pervasive that we open a Notepad++ window and test-paste the snmp-v3 string into it and look closely to confirm whether a space is being pasted in.

If that isn't the case in your situation, does it work with snmp-v2 (just as a temporary test for confirmation)?

Another surprise I've run into is certain combinations of devices and their versions (especially APC UPS's and other APC networked devices like ATS's) have a set maximum snmp string limit that's far too short.  In other cases, some systems just won't play well with special characters in the snmp strings.

At the least, open a support ticket with Solarwinds and detail the complete setup, including device models & brands & their software versions.

I'm confident you'll get it figured out, and it should (hopefully) be something simple like an easily overlooked operator error or typo.  If it turns out to be something weird, right out of left field (like your Node can't report to two different Solarwinds environments using the same snmp-v3 string), I'll be watching to see what you and Solarwinds Support come up with.  Please post what you learn here!

Swift Packets!

Rick Schroeder

That's an interesting situation.  If your node is configured to allow the right pollers to talk to it, and if the node and the pollers have the correct snmp-v3 strings, and if there are no routing or firewall issues present, you've got a bit of a perfect storm.

I'll mention one thing that's easy to miss--Windows Server local firewall.  I can't count the number of times a "network problem" has been put on my table that turned out to be caused by the SysAdmin forgetting that the server firewall is enabled by default in our environment.  

It sounds like you've proven the L2 and L3 paths are valid (if your new test APE can ping the node, that part's good).

I'd spend a tiny bit of time focusing on the snmp-v3 string on the node and the new Solarwinds environment.  A single character (especially an unintentionally pasted-in space at the end of a Ctrl-C to a Ctrl-V) is far to easy to accidentally put in place, thanks to Microsoft's functionality.  Sometimes this is so pervasive that we open a Notepad++ window and test-paste the snmp-v3 string into it and look closely to confirm whether a space is being pasted in.

If that isn't the case in your situation, does it work with snmp-v2 (just as a temporary test for confirmation)?

Another surprise I've run into is certain combinations of devices and their versions (especially APC UPS's and other APC networked devices like ATS's) have a set maximum snmp string limit that's far too short.  In other cases, some systems just won't play well with special characters in the snmp strings.

At the least, open a support ticket with Solarwinds and detail the complete setup, including device models & brands & their software versions.

I'm confident you'll get it figured out, and it should (hopefully) be something simple like an easily overlooked operator error or typo.  If it turns out to be something weird, right out of left field (like your Node can't report to two different Solarwinds environments using the same snmp-v3 string), I'll be watching to see what you and Solarwinds Support come up with.  Please post what you learn here!

Swift Packets!

Rick Schroeder