Ad Widget

Collapse

Monitoring Dell ESX Host with SNMP

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • thecapoeista
    Junior Member
    • Sep 2010
    • 10

    #16
    Originally posted by fjrial
    Can you see something in the log?
    You must set
    Code:
    my $DEBUG = 1;
    my $DEBUGFILE = "/tmp/zabbix_snmptrapdebug_new.log";
    in the snmptrap.pl script

    Then, check the log to see if there is some errors and write it down here..

    If you can't see any errors, you are missing something. Maybe the firewall is blocking tcp connections on port 10051, maybe the dell openmanage is not configured to send the traps to zabbix..

    You are correct I had to open the ports on the firewall and set TRAPDRUN=no to yes in the /etc/default/snmpd in order to start the trap. Now im getting this message in the traps.


    [2010.Sep.21 10:25:43] (blah.blah.local, x.x.x.x) SNMPv2-MIB::authenticationFailure, snmpTrapEnterprise.0: NET-SNMP-MIB::netSnmpAgentOIDs.10
    [2010.Sep.21 10:25:43] (blah.blah.local, x.x.x.x) SNMPv2-MIB::authenticationFailure, snmpTrapEnterprise.0: NET-SNMP-MIB::netSnmpAgentOIDs.10
    [2010.Sep.21 10:25:42] (blah.blah.local, x.x.x.x) SNMPv2-MIB::authenticationFailure, snmpTrapEnterprise.0: NET-SNMP-MIB::netSnmpAgentOIDs.10


    This is what shows up in the logs.


    2010-09-21 10:25:43 -- 29639 --<STDIN> blah.blah.local
    2010-09-21 10:25:43 -- 29639 --<STDIN> UDP: [x.x.x.x]:33822->[x.x.x.x]
    2010-09-21 10:25:43 -- 29639 --<STDIN> DISMAN-EVENT-MIB::sysUpTimeInstance 0:0:17:04.93
    2010-09-21 10:25:43 -- 29639 --<STDIN> SNMPv2-MIB::snmpTrapOID.0 SNMPv2-MIB::authenticationFailure
    2010-09-21 10:25:43 -- 29639 --<STDIN> SNMPv2-MIB::snmpTrapEnterprise.0 NET-SNMP-MIB::netSnmpAgentOIDs.10
    2010-09-21 10:25:43 -- 29639 --/usr/bin/zabbix_sender --zabbix-server x.x.x.x --port 10051 --host TRAP_HOST --key snmptraps --value "(blah.blah.blah, x.x.x.x) SNMPv2-MIB::authenticationFailure, snmpTrapEnterprise.0: NET-SNMP-MIB::netSnmpAgentOIDs.10"


    Thanks for your help.

    Comment

    • fjrial
      Senior Member
      • Feb 2010
      • 140

      #17
      Hi:

      Ok, this is going in a good way, you already did it!..

      First messages are traps, traps indicating that a snmp authentication has no sucess.. maybe someone doing nasty things... maybe.. you should investigate it

      Second one is the snmptrap.pl log.. it indicates that a trap was received (you won´t see all that information in the log because the script cuts some basic info in order to make the traps more readable (you can change this behaviour))

      But for the information you sended, the script is working fine, and sending the traps to zabbix, to a host name "TRAP_HOST" and to an item called "snmptraps"..

      Now.. al traps received by zabbix, will be stored in that item, and you can examine them in the lastes data section.

      Tomorrow (I´m at home now), I will send you the info to configure the triggers for the specific traps that you want.

      Then, if you have more equipment that sends traps, you will be able to configure a host and item per equipment (just if you want).

      For example, I have configured a lot of routers, each one has a host with an item for its traps.. the routers have different brands, I´ve deployed all mibs from all brands and I can see specific information about them, like power failure xx, or changes in configurations, users logged in/out, etc...

      Cheers.

      Comment

      • thecapoeista
        Junior Member
        • Sep 2010
        • 10

        #18
        Originally posted by fjrial
        Hi:

        Ok, this is going in a good way, you already did it!..

        First messages are traps, traps indicating that a snmp authentication has no sucess.. maybe someone doing nasty things... maybe.. you should investigate it

        Second one is the snmptrap.pl log.. it indicates that a trap was received (you won´t see all that information in the log because the script cuts some basic info in order to make the traps more readable (you can change this behaviour))

        But for the information you sended, the script is working fine, and sending the traps to zabbix, to a host name "TRAP_HOST" and to an item called "snmptraps"..

        Now.. al traps received by zabbix, will be stored in that item, and you can examine them in the lastes data section.

        Tomorrow (I´m at home now), I will send you the info to configure the triggers for the specific traps that you want.

        Then, if you have more equipment that sends traps, you will be able to configure a host and item per equipment (just if you want).

        For example, I have configured a lot of routers, each one has a host with an item for its traps.. the routers have different brands, I´ve deployed all mibs from all brands and I can see specific information about them, like power failure xx, or changes in configurations, users logged in/out, etc...

        Cheers.
        Thanks for all your help I will appreciate the info on the triggers. I had to get the book Essential SNMP by O'reilly to get a better understanding of snmp along with your post have been extremely helpful. Is there a way to make the traps more readable?

        Thanks Again

        Comment

        • fjrial
          Senior Member
          • Feb 2010
          • 140

          #19
          attached you will find a template with triggers for standard mibs notifications like link up/down, snmp authentication failure, etc...

          Just apply to a host. In my template, the item which receives the traps is called snmptraps... If yours is different, be sure to change it accordingly in the script snmptrap.pl.

          You can change/clone triggers and modify in order to get alerted on several others mibs..

          The strings enclosed into parenthesis in the triggers, like "str(IF-MIB::linkDown)" are like regular expression to check in the traps received.

          After this, you'll only need to configure actions in order to get traps emailed or whatever.

          about the more readable traps, as I understand, is very difficult to have more readable traps, it depends on manufacturers. If it helps, in your mibs files, you'll be able to find more information about specific traps, when they are generated, why, etc... But the amount of info sometimes is very limited..

          Hope it helps you
          Cheers,
          Attached Files
          Last edited by fjrial; 22-09-2010, 14:48.

          Comment

          • Sparky
            Member
            • Jun 2010
            • 54

            #20
            Hi Guys

            Ok, this thread actually helped me a lot. I can now see that I am receiving the SNMP trap, where before I wasn't getting anything. However, I am now getting the following error in the last line of the log file, after all the trap details

            2010-10-15 09:50:45 -- 32651 --Error sending command. Output is:

            I know it looks like I haven't copied the entire error, but that is where it ends, nothing after that.

            I am guessing it has something to do with zabbix-sender not working as expected... any ideas?

            OMW... never mind! I'm just an idiot... lol... I had the wrong path to zabbix-sender, so obviously it wouldn't work.

            Just want to say thanks for this thread. Some awesome information.
            Last edited by Sparky; 15-10-2010, 10:09.

            Comment

            • efrain02
              Banned
              • Apr 2011
              • 81

              #21
              This works great. A perfect and clean solution. Thank you so much

              Comment

              Working...