Ad Widget

Collapse

Local and Remote Networks

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • rlangle
    Junior Member
    • May 2013
    • 10

    #1

    Local and Remote Networks

    Hi

    Could some one tell me if what I'm trying to do is at least possible, as I have spent most the day on this...

    Were trying to reference our Zabbix server using 2 different DNS names, one for internal and on for external agents

    We have been using Zabbix for about 2 years and monitor a combination of active / passive clients. These all have had external IP addresses and the agent config references the DNS name monitor.company.com (74.x.x.x) however we have a number of servers on our local network that I'm trying to configure to use the internal network by using the agent settings monitor.company.com (10.x.x.x)

    Everything resolves correctly and using telnet I can connect to Zabbix server / agent on ports 10050 /10051

    I see no obvious errors in the agent logs yet I'm getting no data?

    I'm thinking perhaps the server is only happy if I uses the server name monitor.company.com. Can I reference the same server with 2 different names?

    Thanks

    Rob
  • aib
    Senior Member
    • Jan 2014
    • 1615

    #2
    Did you try to use just an IP address for internal agents?
    Sincerely yours,
    Aleksey

    Comment

    • rlangle
      Junior Member
      • May 2013
      • 10

      #3
      Originally posted by aib
      Did you try to use just an IP address for internal agents?
      Hi
      Yes I have substituted the dns name for IP in the config file without success.

      However I have noticed if I reboot the client I get a few values record before it stops. However stopping / starting the service does not have the same affect ??

      Looking in the server logs I can see the following

      Code:
         964:20140527:194553.457 Zabbix agent item [agent.ping] on host [SERVER01] failed: another network error, wait for 15 seconds
         964:20140527:194611.482 Zabbix agent item [system.swap.size[,free]] on host [SERVER01] failed: another network error, wait for 15 seconds
         964:20140527:194629.557 temporarily disabling Zabbix agent checks on host [SERVER01]: host unavailable

      Comment

      • aib
        Senior Member
        • Jan 2014
        • 1615

        #4
        Could you describe your network diagram a little bit more precise?

        When you are saying
        Zabbix server using 2 different DNS names, one for internal and on for external agents
        - Did you mean that your server has two network card?

        Or the second, external IP coming from something like router/firewall/etc. ?

        I'm asking because when you have only one network card it made the life painful. Zabbix Server can be easily messed up because of different network path to internal or to external devices.
        Sincerely yours,
        Aleksey

        Comment

        • rlangle
          Junior Member
          • May 2013
          • 10

          #5
          Hi

          We have fixed the issue, so thought I would update this so it may help others.

          The server we were monitoring is at Amazon (AWS) and we have a cloud based Anti Virus solution BitDefender. As soon as I removed this software all monitoring resumed. This is strange since as far as I know this is only Anti Virus and not a firewall. Several reboots later I re installed the software and rebooted again several times. In all cases Zabbix returns to service as expected.

          We have BitDefender on many of our servers both internal and external and not had an issue before.


          In answer to your question we have a Zabbix server on our network (AWS) monitoring mainly external client servers using external IP addresses. Some clients use the active and some the passive agent. These all reference our external DNS monitor.company.com. As I mention earlier many of these servers have been monitored for close to 2 years.

          We decided to monitor some of our own servers on the same internal network as our Zabbix Server using the internal DNS name of monitor.company.local and this is when the issues started.

          Anyway thanks for your help

          Rob

          Comment

          • aib
            Senior Member
            • Jan 2014
            • 1615

            #6
            Wow!
            One more Zabbix killer (in the company to SELinux) - BitDefender.

            Thank you for your information!
            Sincerely yours,
            Aleksey

            Comment

            • nazz
              Junior Member
              • Jun 2014
              • 12

              #7
              Can you please tell me how did you do to monitor host on remote subnet?

              I Installed Active agent checks ans specify DNS of the zabbix server, but it's not working...

              Comment

              Working...