-
Feature Request
Pardon me if this is already available, but I don’t think it is, so I am gonna request it.
I think this is a very important feature to make this application really enterprise ready.
A Relay Server.
Example.
I run and IT Company that services clients.
Client A has private network, Client B has it’s own private network, Client C has it’s out Private Network.I would setup and FMS system at each Client site. Now the issue is, I have to have a webconsole at each Client site for the clients and for me to use to monitor the systems.
Here is where a relay server would come in handy.
Have a web console for each client at their site. Have the relay server, relay all the alerts and information to a Central Relay server on my network, then the FMS system at my network collects my network data plus the Central Relay data and displays it via a web console connection, and sorts it via client, so I can see my site, and each clients site.Now the 2nd reason for the relay server is that, if their internet link goes down, it still collects the data and when their internet link comes back up, it then pushes it to the central relay server, updating my central db.
3rd reason/scenario.
Client D has 100 Satelite sites connected via VPN, put a relay server at each site in case vpn goes down it still collects data and pushes it out when it comes up, and an alert server at each site as well.
This would ensure that you always have all the data eventually, so if the VPN link goes down, or the network link goes down, you still have local monitoring.
I know of one product that has this capability, it’s called Performance IT, but it costs a hell of a lot.
How is that for a wish?!
-
5 Replies
-
Very GOOD idea. Please, post it at our Sourceforge’s Wish list. I’ll keep in mind for 1.3 version and SURE for upgoing 2.0 version, this is the ideas we want to add to our project because Pandora FMS wants to have features that people needs in real enterprise environments.
Post this idea in:
http://sourceforge.net/tracker/?group_id=155200&atid=794855
Currently we are coding other things, but we want to have all “good ideas” and bugreports in the same public place, to review, recheck and work on that when time will be availble for us.
Thank you for your time and your interesting ideas 🙂
-
Here is one for the Agents.
From a post I read earlier, it seems they have an issue with NAT, Fixing this should be a priority as well, if it’s not already.
Just have the agent grab it’s IP and use a unidue Identifier, and put it in the data packet along with the monitoring data, so you will know it came from client a, site b, and so forth, so it can be tracked and used behind nat. Pardon me if it already has this functionality.
-
Here is one for the Agents.
From a post I read earlier, it seems they have an issue with NAT, Fixing this should be a priority as well, if it’s not already.
Just have the agent grab it’s IP and use a unidue Identifier, and put it in the data packet along with the monitoring data, so you will know it came from client a, site b, and so forth, so it can be tracked and used behind nat. Pardon me if it already has this functionality.
Agent IP it’s only a descriptive Field. All IP’s used for network monitoring are defined in modules, not in agent.
-
Here is one for the Agents.
From a post I read earlier, it seems they have an issue with NAT, Fixing this should be a priority as well, if it’s not already.
Just have the agent grab it’s IP and use a unidue Identifier, and put it in the data packet along with the monitoring data, so you will know it came from client a, site b, and so forth, so it can be tracked and used behind nat. Pardon me if it already has this functionality.
Agent IP it’s only a descriptive Field. All IP’s used for network monitoring are defined in modules, not in agent.
Ok, so then the Agent is not compatible with NAT at this time because if 2 devices with the same IP are behing nat, the module only sees it as one.
My request is for the Module to be able to differentiate between the 2 devices behind NAT.
-
A Firewall or a Router does the Nat. When the packet goes in Pandora Server the IP that appears in the packet is the original one, not the traslated IP.
The NAT is transparent for Pandora Server.
It is different if you use the Network server, you need to define a unique IP.
Regards.
