SNMPV3
-
-
-
ok after doing some packet captures there does seem to be a slight difference in response from netxms .. after the initial report from the switch which includes the engineid nextxms fails to include the engineid in following get request messages. I have verified that both snmpb and using net-snmp command line from my laptop both work and all but netxms includes the engineid. Not sure if this is still a vendor issues or not but the specific switch i am testing is a Ruggedcom RS900
-
-
-
-
Here you go.. Its seems worse with 2.0-RC2 I had to reboot my switch several times because it was continually trying several times per second and by default the ruggedcoms will quit responding after so many failed attempts. I also attached the switch debug screen. I have also tried 1.2.17 linux version running on ubuntu thinking maybe it was a windows thing
-
Hi,
it could be a bug in NetXMS SNMP library. Is it possibe to get access over SNMP to your switch so we can test and fix it? Please send me private message if that's possible.
Best regards,
Victor -
Hi,
I've fixed bug in SNMP library, thanks for the access to the switch! Fix will be included in 2.0 release. If you built NetXMS from sources I can provide you a patch.
Best regards,
Victor -
-
-
And by the way thank you for the quick fix ....you mentioned the fix will be released in 2.0 ... ive been wanting to move to 2.0 rc but wasnt sure how stable things are and didnt want to have to migrate everything from 1.2 .. how far along would you guess 2.0 is from being stable release
-
Hi,
patch for src/snmp/libnxsnmp/transport.cpp attached.
We plan to make 2.0 release before December 10th.
Best regards,
Victor
-
-
We have a new problem with SNMP, maybe something similar as the points above.
We use NetXMS V2.0-RC2 compiled with patched transport.cpp (I attached the patched one).
After Software Update on some ZyXEL Access-Points these devices stop responding to SNMPv3 (SHA1, AES) after a while. I also checked by snmpwalk on command line. I have to reboot the affected Access-Points, but after a short while the same. When I disable all SNMP on these nodes in NetXMS, SNMP on these APs are stable (checked by snmpwalk on command line).
Which information do you need for further troubleshooting?thanks
Dani
-
Hi,
how fast device stops responding to SNMP? If you disable SNMP in NetXMS and run snmpwalk or snmpget from command line in a loop, will it have the same effect?
Best regards,
Victor -
Hi Victor
First I thought it's only by configuration polls. But some APs 'crash' quite fast, after a few minutes. But I also saw APs where it lasts longer. I can start about 50 snmpwalks from command line in short time without any problems (about 20 OIDs each). Only disabling configuration polls on these nodes is not enough. I have to disable SNMP completely for these nodes. If SNMP is completely disabled the SNMP service on these APs are stable permanent.
thanks
Dani -
Try to disable routing table and topology polls.
Best regards,
Victor -
-
Hello! It looks like you're interested in this conversation, but you don't have an account yet.
Getting fed up of having to scroll through the same posts each visit? When you register for an account, you'll always come back to exactly where you were before, and choose to be notified of new replies (either via email, or push notification). You'll also be able to save bookmarks and upvote posts to show your appreciation to other community members.
With your input, this post could be even better 💗
Register Login