Announcement

Collapse
No announcement yet.

monitoring remote servers via the internet

Collapse
X
  • Filter
  • Time
  • Show
Clear All
new posts

    monitoring remote servers via the internet

    I have a remote windows agent in active mode reporting to my server through the Internet via the default agent port. The CPU trigger / item is working but the free swap space and free disk space isn't not reporting any data. Also, the free memory items are reading information but it is not correct. The total and free memory amount is incorrect? I tried setting the agent port to 0 on the host config on the server. I also tried 10051. It seems to only receive any data when set to 10050 but Im missing the data mentioned above and most of the data I receive is incorrect. What could be wrong? I also deployed to another monitored server with the same config and received the same results.
    Last edited by gopher_49; 07-05-2012, 18:01. Reason: Issues changed

    #2
    I had to open the SuSE firewall via the below commands?! Why in the world a firewall is enabled on these needed ports by default I don't know.. But.. I got it working now.

    6.4 Firewall
    By default, only two ports are open - 22 (SSH) and 80 (HTTP). To open additional ports - for example, Zabbix server and agent ports - modify iptables rules with SuSEfirewall2 utility:

    SuSEfirewall2 open EXT TCP zabbix-trapper zabbix-agentThen reload the firewall rules:

    SuSEfirewall2 stop
    SuSEfirewall2 start

    Comment


      #3
      agents not reporting after changing public NAT translation...

      I changed the public to private NAT translation and now my active/remote agents are not reporting back to me... I ran the firewall config syntax posted earlier in this post which fixed it before but now it seems to still have the ports close. Keep in mind that my private IP did not change. Only the public IP that I'm NAT'ing from did.. What can I try? I turned off the firewall and that didn't help... Port 80 is open but 10050-10051 is still closed... I tripled checked my NAT rules and still no luck. Any suggestions?

      Comment


        #4
        oops... It ended up being my ISP filtering ports... They filter ports when handing off even public IP's.. We requested this some time ago and I forgot.. Anyway.. Everything works just fine.. The firewall syntax below allows active agents to send data to the Zabbix server..

        6.4 Firewall

        By default, only two ports are open - 22 (SSH) and 80 (HTTP). To open additional ports - for example, Zabbix server and agent ports - modify iptables rules with SuSEfirewall2 utility:

        SuSEfirewall2 open EXT TCP zabbix-trapper zabbix-agent
        Then reload the firewall rules:

        SuSEfirewall2 stop
        SuSEfirewall2 start

        Comment

        Working...
        X