NetXMS Support Forum

English Support => General Support => Topic started by: jdowney on October 22, 2010, 05:32:05 PM

Title: NetXMS server not talking to other Netxms server...
Post by: jdowney on October 22, 2010, 05:32:05 PM
I have two Netxms Servers one In our main office monitoring severs in this location running on Windows 2003 server and sql 2000 . In our remote office we have another Netxms Server setup to monitor servers in this location. Windows XP pro / Sql Express 2005.

The remote server is set to forward on alerts to the server in the main office. This function seem to work. I have run wireshark on the main sever it is receiving the data on port 4702.

But I'm not seeing these alerts come though on the main server.

I've set the following settings - EnableISCListener and ReceiveForwardedEvents to 1 and restarted the core

Any ideas is there something I've missed?
Cheers
Title: Re: NetXMS server not talking to other Netxms server...
Post by: Victor Kirhenshtein on October 22, 2010, 05:54:59 PM
Hi!

Currently event forwarding has a lot of limitations. In order for incoming event to be processed on recipient server, two conditions must be met:

1. Event template with same event code or event name must exist on recipient server
2. Node object with same IP address as event's source node's address must exist on recipient server

Events not met these conditions are discarded.

You can try to turn on debug with level 5 or more - than you will be able to see if and why incoming events are discarded.

Best regards,
Victor
Title: Re: NetXMS server not talking to other Netxms server...
Post by: jdowney on October 22, 2010, 06:45:49 PM
How should I set these nodes up then? Unmanaged or not to poll on the main server?

I don't want the main server to poll these nodes as well?

Are there plans to improve the forwarding of alerts?

Cheers
Title: Re: NetXMS server not talking to other Netxms server...
Post by: Victor Kirhenshtein on October 25, 2010, 11:01:00 AM
You can create either unmanaged node or disable all polling protocols - it depends on how you wish to see node's status. For unmanaged node, it always be "unmanaged", regardless of active alarms. If you disable polling, node's status will be "unknown" unless there will be active alarms for that node - in that case node's status will change to severity of most critical alarm.

Best regards,
Victor