NetXMS Support Forum

Wow, thank you very much for the quick fix. I just tested and I can confirm it's fixed.

Thanks
Dani

ok, thanks Victor, so for the moment I leave the BeaconHost IP in reverse order till V2.0-M5.

Thanks Tomas. Ok let's have a look what Victor says.

Dani

Yes, Beacon Probing is enabled:
BeaconHosts: 172.16.100.8
BeaconPollingInterval: 1000
BeaconTimeout: 1000
It's configured like this for a few months. The Beacon Host ist the core switch.

I tested, I can ping the core switch ip from the command line on the NetXMS server.

Now I changed the IP address to reversed order: "8.100.16.172". And now I get the alarms of SYS_NODE_DOWN events again! When I switch back to normal IP address, I get a "SYS_NETWORK_CONN_LOST event".
Is this a similar bug as in the PING subagent of V2.0-M3?
And why are only the "SYS_NODE_DOWN" events correlated with this and not all other events too? I get alarms from the same nodes when a DCI threshold is active but not when node down, strange for me.

Thanks Victor. I see in all test cases the same root event ID. In the DB I saw it is a "SYS_NETWORK_CONN_LOST" event (Event Code 50) several days ago.
I don't understand why this very old event is relevant in the event correlation. Of course the NetXMS server has network connection.

where can I see the root cause event ID exactly? Or should I send you the log (but not in the public forum)?

[24-Apr-2015 16:26:31.220] [DEBUG] EVENT 28 (ID:1852235 F:0x0001 S:4 TAG:"" CORRELATED) FROM node.domain.com: Node down
[24-Apr-2015 16:26:31.220] [DEBUG] Event::expandText(event=0x2a57620 sourceObject=392 template='Interface "%2" changed state to DOWN (IP Addr: %3/%4, IfIndex: %5)' alarmMsg='(null)' alarmKey='(null)')
[24-Apr-2015 16:26:31.220] [DEBUG] CorrelateEvent: event SYS_IF_DOWN id 1852234 source node.domain.com [392]
[24-Apr-2015 16:26:31.220] [DEBUG] CorrelateEvent: finished, rootId=1852235

Yes the line in the log is like this:
[25-Apr-2015 17:50:04.531] [DEBUG] EVENT 28 (ID:1857867 F:0x0001 S:4 TAG:"" CORRELATED) FROM mb460.domain.com: Node down

VPN-connector Subnets tab:
Since V2.0-M3 I can't open the Subnets tab of an existing VPN-connector anymore, I get the following error:
"The currently displayed page contains invalid values." in the Windows x64 Java Console.
Now in V2.0-M4 when you try a second time to open this tab it's opening but looks like in the attached printscreen.

and  it's only possible to add or remove from 'Local networks'.

It's a little bit hard going, each problem with the vpn connectors is followed by the next problem... ;-)

I just updated to V2.0-M4. But the problem still exists.

Ok, I will try V2.0-M4 first. When will it be available?

Hi Victor.
Have you found anything in my config and the registry?

thanks
Dani

Hi Victor

I definitely get the "SYS_NODE_DOWN" event (double checked).
When I shut down a test printer for example, first I get the events "SYS_IF_DOWN" and "SYS_NODE_CRITICAL" (in the same second), than 7seconds later "SYS_NODE_DOWN".

thanks
Dani

We use NetXMS V2.0-M3 and see a very strange but critical problem.

All "SYS_NODE_DOWN" events are not processed anymore in Event Process Policies. I checked the EPPs double and triple. Everything still like it worked before (same config). I also tested with the EPP-policy for "SYS_NODE_DOWN" as first rule. "SYS_NODE_UP" and all other events are processed fine. The events "SYS_NODE_DOWN" are generated, that part is ok. It occures on all tested nodes.
I turned on server debug logging (level=9). There I see for every generated event a line like this:
[25-Apr-2015 17:50:04.531] [DEBUG] EPP: processing event 1857868
But no such line for the "SYS_NODE_DOWN" events. I have the debug log but would not like attach to forum posts.

It could be since upgrade to V2.0-M3, but not for sure.
At the moment I don't know where the problem can be. Any help is appreciated.

Have you found anything in my config and the registry?

Thanks Victor. I didn't saw anything in 'show queues. At the moment I have no more such events. But I don't know why ;-) I will come back to this if it re-occures.