Have you checked the full post below ?
When you say "That server is not being monitored specifically by NPM " do you mean the server is not been added as node in the Orion and you are still sending the Traps ?
You will noticed that the IP address in the error message was actually assigned to an interfaces on the routers and that the traps were being sent from this interfaces.
Since the SNMPv3 credentials are used by the router and not the interfaces you then needed to find a way to source all traps from the router's Loopback address themselves.
The easiest way to do this was to enter the following line within the SNMP portion of the router configuration.
"snmp-server trap-source Loopbackxxxx" Where xxxx is the loopback # that the router's IP address is assigned to.
I recieved a hotfix but have not seen any update in release notes that it has been posted. I will check with our SonicWALL account team to see if can get answer. The problem is traps but still want to get snmp status, remove the SolarWinds server from the host field. That will stop the messages from spawning off.
SonicWALLs do not support Loopback addreses. That is for Cisco devices. What is stated is not what the SonicWALLs were doing. The engine ID and user information was being sent accordingly.
Have you received any resolutions to this hotfix from the SonicWall support? We are also having this issue with our NSA2600 and TZ400s
SolarWinds solutions are rooted in our deep connection to our user base in the THWACK® online community. More than 150,000 members are here to solve problems, share technology and best practices, and directly contribute to our product development process. Learn more today by joining now.