Welcome to Pandora FMS Community › Forums › Community support › Pandora Agents from Dynamic IP, Multiple Agents from same IP
-
Pandora Agents from Dynamic IP, Multiple Agents from same IP
Posted by RPICARD on June 9, 2008 at 02:23I have setup Pandora FMS and got the Windows agents to work correctly.
I would like to comment, the documentation for the Windows Agent configuration ins the 1.2 version of documentation was more helpfull than that listed in the 1.3x documentation.
What I would like to know, need to know is can I have
Multiple Agents comming from the Same IP address?IE Rotuer w/ NAT
– Server 1
– Server 2Since both Servers are behind a router using NAT, they would appear to have the same IP address, will this present a issue for Pandora?
Second question I have, how can I setup a agent on a dynamic IP? Since some servers I wish to monitor are on Dynamic IP’s and change frequently, can I use a DynDNS entry instead of a IP for clients who may have IP’s that change, sometime as often as once an hour. How often would Pandora update its DNS entry?
RPICARD replied 16 years, 8 months ago 2 Members · 2 Replies -
2 Replies
-
::
I have setup Pandora FMS and got the Windows agents to work correctly.
I would like to comment, the documentation for the Windows Agent configuration ins the 1.2 version of documentation was more helpfull than that listed in the 1.3x documentation.
What I would like to know, need to know is can I have
Multiple Agents comming from the Same IP address?IE Rotuer w/ NAT
– Server 1
– Server 2Since both Servers are behind a router using NAT, they would appear to have the same IP address, will this present a issue for Pandora?
Second question I have, how can I setup a agent on a dynamic IP? Since some servers I wish to monitor are on Dynamic IP’s and change frequently, can I use a DynDNS entry instead of a IP for clients who may have IP’s that change, sometime as often as once an hour. How often would Pandora update its DNS entry?
This is not a problem for Pandora FMS if you’re using software agents. It uses “agent name” as “ID”, IP address could be duplicated, IP address are only used for remote network checks and to detect if a system is already monitored when detecting new systems with Recon Server.
About differences between docs in 1.2 and 1.3, could you be more specific on that issues are better documented in 1.2?.
-
::
Great news, I have to say I am extremly impressed with your application.
In less than 1 day, I had your system setup and able to monitor hosts on remote and seperate networks.
I’ve spent the past 4 weeks trying to get nagios to do the same thing without sucess.
In regards to my comment about documentation, the main thing is in the old 1.2 documentation, section 2.4.7.x (Windows Agent) verses the new 4.5.x section. It mainly had to do with the section on enverypted traffic, mixing the old documentation with the readme helped me get it up and running.
I will post a report about the Dynamic IP question once I’ve tested it.
One suggestion I have for the next version if no one had made it, allow agents to have a ‘location’ attached. This way you could filter agents by location or by group.
Great product!