Zabbix agent configuration

[sutech88]

Hi everybody
First of all I must say that I'm somehow new to zabbix, though I have installed a zabbix server and an agentd on windows successfully.

Now I want to setup another windows zabbix agentd but I'm confused with the IP/PORT addressing.
I know the IP/PORT of the machine that my zabbix server is installed- I have access to the front-end using this address, lets say: 1.1.1.146/1234 .
and I also know the IP/PORT of the machine that I want to monitor its resource in both active and passive modes, lets say: 1.1.1.146/10000 .

But now I'm not sure about the configuration file and also the hosts address in the front-end!
So far I have configured as follow:
serverActive = 1.1.1.146
ListenPort = 1234
server = 127.0.0.1
and in host configuration in the front-end I've written:
IP= 127.0.0.1 and PORT 10050
I also have test these front-end configurations:
IP= 1.1.1.146 and PORT 10000

I have some data on two configured graphs, but they are not much rational.
also the active mode is unreachable(which maybe because of firewall issue).
To make the long story short I want to monitore a few linux and windows machine through a linux server via Zabbix, and I'm not sure about the addressing

[rthonpm]

The IP's in your configuration file on the machine you want to monitor should be for the Zabbix server, not the machine itself.

A basic configuration file for the agent would be something like:

Hostname=A case sensitive name for the system you're monitoring. This needs to be the same as the name you give the host in the server front end.
Server=The IP address of the Zabbix Server (used for passive monitoring items)
ServerActive=The IP address of the Zabbix Server (used for active items)
ListenPort=10050 (This is the default port, if you've changed your server to use a different port to talk to the agent, use that instead)
LogFile=Directory path to where you want the Zabbix Agent to create its log file

Any mention of 'Server' in the agent configuration file always refers to the Zabbix server itself.
There are a lot more things you could configure for the agent, but using these values will give you a fairly clean configuration file to start seeing how the agent works.

You may also need to make sure that the port used by the agent and server to communicate isn't being blocked by any firewalls.

[sutech88]

Thank you
I found my missconfiguration, as you mentioned + I found out that I can make the connection using just a same hostname on the front-end and Agent.

Also I have want to advise newbies like myself that

If you are installing Agent on CentOS remember to customize SELinux and Firewall; otherwise everything would get messed up.