Distributed Monitoring available?
-
I've read some posts about this, but they are almost 3 years old. We have 3 locations that I want to monitor. Do I put a server at each location and then have them report back to the "master" server? If so, what is the configuration to accomplish this? Is ther something in the docs that show how to configure a multi-site monitoring system?
-
You can install one agent at the remote location and use it as a proxy agent to get information from other devices using that agent, snmp and so on.
https://www.netxms.org/documentation/adminguide/agent-management.html -
So basically, I can set up an additional server at one other location, install the agent and point it's config back to the main server, correct? Then details from that server are then forwarded back to the master? Making sure I understand how this works. Does the remote server then show up in the object panel?
-
You install a NetXMS agent at the other sites and configure it as a proxy node. If required, setup a port forward for port 4700 to that proxy agent, so the server can communicate with it.
Install additional agents, setup SNMP, etc. as required at each site, ensuring that the proxy agent has access to those additional agents (i.e. the proxy agent is the "master server" for those additional agents).Your NetXMS server will communicate to all other devices/nodes on those networks via those proxy agents. You configure that part either via zone defaults or directly on the nodes.
There is no need for multiple NetXMS servers.We are monitoring dozens of different sites like this.
-
-
Under the Entire Network tree, nodes will show in the zone that they belong to.
Assigning a node to a zone will assign the default proxy agent for that zone to it.
On the other hand, manually assigning a proxy agent to a node does not make that node part of the proxy agent's zone.Are you having any specific issues with your proxy/zone setup which you are trying to resolve?
-
Right now I am trying to determine the parameters with which I can operate NetXMS, or rather it's limitations. We monitor several hundred subnets, and most of them have the same internal IP scheme. There is a firewall which has different public IP's. What I need to be able to do is to separate each location into it's own zone with it's subnet underneath it. I need to be able to have alerts set for each zone so I know when there are issues from each location. I hope that makes sense. Here is a sample layout:
Zone 1
192.168.1.0/24
Zone 2
192.168.1.0/24
Zone 3
192.168.1.0/24And so on. Not all have the same subnet, but a good portion of them do.
-
Yes, this is what zones are for. You can have overlapping IP addresses as long as they are in different zones.
Best regards,
Victor -
Good. One last question. Our networks consist of devices that do not have the ability of installing an agent on them. We currently use SNMP to monitor them. If I set a proxy on that network, will it poll SNMP and use that data or does the agent have to be installed in order for the proxy to work?
-
You need one agent in the network to act as proxy.
Other than that, you can monitor everything else in that network using SNMP only via the above agent/proxy.
Just set that agent as your default proxy for the zone in question and ensure you add the other SNMP devices to that zone.
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