Ad Widget

Collapse

Is there a simple trigger that actually work for IP availability?

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • xcalibur
    Member
    • Apr 2011
    • 40

    #1

    Is there a simple trigger that actually work for IP availability?

    Hi,

    I simply would like to know wether or not my servers are online.
    Ping Check\unreachable for 3 minutes and what not keep spamming my mail with false results.

    Is there a simple syntax that work properly?

    Thanks
  • mazate
    Junior Member
    • Oct 2011
    • 20

    #2
    I'm having exactly the same problem...

    Comment

    • xcalibur
      Member
      • Apr 2011
      • 40

      #3
      Anyone?

      Comment

      • Colttt
        Senior Member
        Zabbix Certified Specialist
        • Mar 2009
        • 878

        #4
        yes you can use simplechecks.. icmpping
        Debian-User

        Sorry for my bad english

        Comment

        • mazate
          Junior Member
          • Oct 2011
          • 20

          #5
          Thanks, I'll try that...

          Comment

          • HullZabbix
            Senior Member
            • Feb 2011
            • 104

            #6
            We had problems when sometimes a machine wouldn't reply back to a ping ocassionally, but was actually online. So now for a trigger we use this:

            {Template1:icmpping[].last(0)}#1 | {Template1:icmpping[].nodata(120)}=1

            Admittedly last(0)#1 is probably a bit pointless as if the host is offline then it's not going to reply with anything. So if we get no reply for 120 seconds (the ping item is every 60 seconds)

            For remote servers where pings are even more unreliable we use the trigger with a ping item every 30 seconds:

            {Template2:icmpping[].avg(210)}<0.5 | {Template2:icmpping[].nodata(210)}=1

            Comment

            • mazate
              Junior Member
              • Oct 2011
              • 20

              #7
              Now I'm using icmpping with this expression,
              {Template_Windows:icmpping.count(300,0,"eq")}>3
              and it's working fine.

              Comment

              • vrolok
                Junior Member
                • Jan 2011
                • 22

                #8
                Originally posted by mazate
                Now I'm using icmpping with this expression,
                {Template_Windows:icmpping.count(300,0,"eq")}>3
                and it's working fine.
                I'm trying to understand your trigger, can you tell how to "read" it. Thanks!

                Comment

                • mazate
                  Junior Member
                  • Oct 2011
                  • 20

                  #9
                  This is my understanding...

                  I set one simple check item, icmpping, to ping every minute (fping is required).

                  This expression counts the number of failed pings (status equals to "0") in the period of 5 minutes (300 seconds).
                  If it is grater than 3 (out of 5) then there is a problem.

                  Hope this helps.

                  Comment

                  • Davidus
                    Senior Member
                    • Dec 2010
                    • 281

                    #10
                    Hello everyone,
                    Would like to share with you guys my solution for this particular issue. Because of the different circumstances I`m doing following (might be useful for someone, cause using this method we don’t need zabbix agent at all)

                    ITEM
                    Description: Exchange servers connectivity
                    Type: Zabbix trapper
                    Key: eserv.connect
                    Type of information: character

                    TRIGGER
                    Name: No connectivity to Exchange server
                    Expression: {EXSERV:eserv.connect.strlen(0)}#1


                    I have perl script, which is located at the same server where zabbix server is.


                    Code:
                    #!/usr/bin/perl
                    #following scripts monitors Exchange servers connectivity status;
                    
                    	if( system(" ping -c 2 192.168.25.142 > /dev/null ") )
                    	{
                    		system(' /usr/local/bin/zabbix_sender -z localhost -s " EXSERV " -k eserv.connect -o "Cannot PING Exchange server" > /dev/null ');
                    	}
                    	else
                    	{
                    		system(' /usr/local/bin/zabbix_sender -z localhost -s " EXSERV " -k eserv.connect -o "0" > /dev/null ');
                    	}
                    exit;

                    This is it!! Link to this script I placed in cron and cron is running it once every 15 minutes

                    Regards

                    Comment

                    • mazate
                      Junior Member
                      • Oct 2011
                      • 20

                      #11
                      Thanks for sharing...

                      Comment

                      • HullZabbix
                        Senior Member
                        • Feb 2011
                        • 104

                        #12
                        Just incase you weren't aware, icmpping[] doesn't require a zabbix agent. So the script method above seems rather long winded.

                        Comment

                        Working...