Comments
-
Yes that is true for traps and we put it in there in case we needed to do that down the road.
-
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.…
-
This problem has been resolved by SonicWALL on my case. They are putting the hot fix is 6.2.6.2 release that is coming out for new TZ units and current NSA models. The trap messages have stopped being invalid to the SolarWinds server and we are back to normalcy now.
-
Update on this issue. I have been working with SonicWALL engineers and development team on this matter. I believe there is a resolution coming soon if you are running Gen6 (6.2.5) code or higher. They are to be providing me hotfix soon to correct the problem. It did not matter if it was SolarWinds or just sending the data…
-
ahutch43 & I work for the same company. I have been dealing with SolarWinds and Dell SonicWALL support on the matter over the past weeks. We have done multiple packet captures and have given the information to Dell SonicWALL Support. Dell SonicWALL engineer is working with their escalation team. The data stream being sent…
-
Disable the traps and the errors will go away at least from SonicWALL perspective. That stopped all the errors from coming in. They did fix the problem on Gen 6 appliances, but if you have old Gen 5 it will still respond this way. Just take out the server IP in Traps and you will be fine to do SNMP get to monitor the…
-
You would need to have a entry point into the location where to terminate the VPNs for management. From there at your location, your NPM server will need to be accessible to those devices via that entry point at your location.
-
Agreed. You would need to do a management VPN tunnel to be able to poll loopback IP addresses. We have done that and that configuration works fine. Just have to make the loopback accessible via routing to get it sent to peer at the host source where NPM is running at.
-
We do a lot of our monitoring via Loopback interfaces on Cisco devices and have no issues with it. We just make sure the devices are reachable on that address to out NPM system.
