How to have a main netXMS server that is been fed by slave netXMS server's

[edwin]

For sure a newbie on netXMS AND Linux so have to do some ketch-up.
Perhaps subject is not clear enough but did not know how to explain properly so here is the situation.

One headquarter with a few sub divisions in different location's
Each location should get his own netXMS server so your are able to see the network status in each location on a local dashboard..
On top of that in the headquarters we would like to see each sub divisions as if we would look on their dashboard.

So far i understand that zones would be the answer to this. Being each zone a sub division.

So now the question's 

1. Is it possible to poll all sub division netXMS servers to collect all accumulated data from each sub?
2. Is it possible to let the agent send data to multiple netXMS server's
3. Is it possible to change agent configuration from within the netxms server (say you have to change the IP adres from the netXMS server)

Any help would be appreciated even if it is just a pointer in the right direction.

Thanks,
edwin

[victor]

Hi,

it is not possible to transfer collected data from one server to another. However, agent can work simultaneously with multiple servers - you just have to list them in agent's config file. It is possible to change agent configuration from NetXMS server if this server address listed in MasterServers parameter on agent. You can edit agent config from management console by right-clicking on the node and selecting "Edit agent configuration".

Best regards,
Victor

[edwin]

Missed the reply, sorry.
So the only solution would be a kind of master netxms server. Is it then possible to work with sites?
This means that each server location has to have a vpn connection to the master server location OR there has to be a open port on which the master sever is listening to the agents. Which port would that be and is it configurable?

regards,
edwin
Still trying to get the first netxms server installed 

[victor]

Hi,

server connects to agents (on port 4700 by default, but it can be changed). You can also have one agent on remote site working as a proxy for other agents - in that case you only need to open port 4700 to one machine on remote site from management server. Agent can also be used as proxy for SNMP, so you can monitor network devices via agent without direct SNMP requests from management server.

Best regards,
Victor

[edwin]

thanks.
Does this mean that every agent uses his own port?
Unable to open port on remote location's so only option seems to be to let agent agent send data to master server and local server. Right?