NetXMS Support Forum

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

Maybe look at this thread: https://www.netxms.org/forum/announcements/netxms-1-2-16-released/msg15422/#msg15422

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

Thanks Victor for the patch and your work in general!!
Now I'm only waiting for a patch for the snmp authentication failures (other thread). Then I hope our SNMP problems are gone in NetXMS.

Dani

Hi Victor

I would be interested in the source code patch. Is the problem with the SNMP auth. failures a separate thing?

Thanks
Dani

Victor

Do you already have a fix for the SNMP problems? Maybe a fixed source code file?

Thanks
Dani

Hi Victor

Very strange. I have tested with a Win7, a Win8.1 and a Win2012R2 node. All with the same negative result.
How did you tested?

My test was like this:

Logwatch section of the agent config:
[logwatch]
ProcessOfflineEvents = yes
Parser = ${ProgramFiles}\NetXMS\var\eventlog-system-parser.xml
Parser = ${ProgramFiles}\NetXMS\var\eventlog-application-parser.xml

Parser (file: eventlog-system-parser.xml):
<parser name="SystemLog">
  <file>*System</file>
  <rules>
    <rule>
      <match>(.*)</match>
      <level>1</level>
      <event params="1">100845</event>
    </rule>
  </rules>
</parser>

Than I hard-switched of the node. After that I checked the NetXMS events of this node. But I can't find any event for the expected Windows Event (Eventlog: System, Event-ID: 6008, Source: Eventlog, Text: Last shutdown was unexpected).
While normal operation I get a NetXMS event for every error in Windows Eventlog. I only have problems with offline events.

thanks
Dani

Are there any news about the offline processing feature? In V2.0-RC2 it's still not working for us.

Thanks Victor. I really hope you can make a fix before V2.0.

We are using NetXMS V2.0-RC2. We configured the NetXMS agents by policies (Windows and Linux). I just wanted to change something in an existing policy. Now all but one node assignments are disappeared in the console!

Is something in the agent configuration policy feature broken in V2.0-RC2?

edit:
I can reinstall the policies on the nodes, then they appear again in the console under the policy. Maybe an upgrade or database problem?

Thanks
Dani

I have registered this as a feature in the issue tracker:
https://dev.raden.solutions/issues/976

If you register a feature request for that. We also have problems like that:

We use instance discovery on VPN-appliances for site-2-site tunnels.
If one tunnel goes down for a short time and in this moment instance discovery runs, all DCIs for this tunnel are deleted. Then the tunnel goes up again. On the next instance discovery run new DCIs will be created for the same tunnel. Now there are different DCIs for the same tunnel, now without history.

At the moment I don't know what would be the best solution for that. Otherwise I would already register the feature request. The best behavior for us would be to have the same DCIs (same number) after that. But I don't know how you could do that.

thanks
Dani

We also see a big number of "SNMP_AUTH_FAILURE" events since update to V2.0-RC2 and have problems on some network devices with SNMP. They do not respond to SNMP requests anymore.

edit:
But only some of the SNMP nodes are affected, others not.
We use SNMPv3.

https://dev.raden.solutions/projects/netxms

I can confirm, problem is fixed with the patched 'node.cpp'.

thanks!
Dani