Unable to view traps through snmptrad?











up vote
1
down vote

favorite












I've been unable to view traps through snmptrapd. I generated a SNMP trap manually using the below provided snmptrap command:



snmptrap -c public -v 2c -n "" localhost 0 uptime


But I'm unable to capture the trap using the below provided snmptrapd command:



snmptrapd -f -M /usr/share/snmp/mibs -m inUnixPlatformApp-MIB -Os


Question: How can I capture the snmptrap in snmptrapd?



Installed software



I have the following RPM packages installed on the RHEL 6.3 server:



# rpm -qa|grep -i snmp
net-snmp-libs-5.5-41.el6.x86_64,
net-snmp-libs-5.5-41.el6.i686,
net-snmp-devel-5.5-41.el6.x86_64,
net-snmp-5.5-41.el6.x86_64,
net-snmp-perl-5.5-41.el6.x86_64,
net-snmp-utils-5.5-41.el6.x86_64,
perl-SNMP_Session-1.12-4.el6.noarch


System info




  • Linux Rhel: 6.3

  • SNMP Master Agent version: 5.5

  • SNMP Protocol version: v2C










share|improve this question
















bumped to the homepage by Community 2 days ago


This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.















  • Do you get any error messages when you try the snmptrapd command?
    – slm
    Jan 25 '14 at 23:38










  • Where's the output?
    – slm
    Jan 26 '14 at 3:16










  • No, i do not have any error messages while i run snmp trapd command..please find the start & end of the dump snmptrapd here:- # snmptrapd -M /usr/share/snmp/mibs -m inUnixPlatformApp-MIB -f -n -Ddump No log handling enabled - turning on stderr logging registered debug token dump, 1 NET-SNMP version 5.5 dumpx_recv:02 01 01 ....... 2014-01-25 22:33:55 UDP: [127.0.0.1]:40313->[127.0.0.1] [UDP: [127.0.0.1]:40313->[127.0.0.1]]: SNMPv2-SMI::mib-2.1.3.0 = Timeticks: (0) 0:00:00.00 SNMPv2-SMI::snmpModules.1.1.4.1.0 = OID: SNMPv2-SMI::mib-2.1.3
    – user57619
    Jan 26 '14 at 3:57










  • In continuation to my previous comment, in dump mode of snmptrapd i am able to see the lines of trap but that seems to be in improper format or not the actual trap, because the snmptrapd when run in normal mode(without dump) i do not get any traps, it just goes blank after the following 3lines: [root@eirsnmp ~]# snmptrapd -M /usr/share/snmp/mibs -m airwide-solutions-inUnixPlatformApp-MIB -f -n -Ddump No log handling enabled - turning on stderr logging registered debug token dump, 1 NET-SNMP version 5.5 The trapd terminal will now be blank forever even after generating snmptraps !!
    – user57619
    Jan 26 '14 at 4:07

















up vote
1
down vote

favorite












I've been unable to view traps through snmptrapd. I generated a SNMP trap manually using the below provided snmptrap command:



snmptrap -c public -v 2c -n "" localhost 0 uptime


But I'm unable to capture the trap using the below provided snmptrapd command:



snmptrapd -f -M /usr/share/snmp/mibs -m inUnixPlatformApp-MIB -Os


Question: How can I capture the snmptrap in snmptrapd?



Installed software



I have the following RPM packages installed on the RHEL 6.3 server:



# rpm -qa|grep -i snmp
net-snmp-libs-5.5-41.el6.x86_64,
net-snmp-libs-5.5-41.el6.i686,
net-snmp-devel-5.5-41.el6.x86_64,
net-snmp-5.5-41.el6.x86_64,
net-snmp-perl-5.5-41.el6.x86_64,
net-snmp-utils-5.5-41.el6.x86_64,
perl-SNMP_Session-1.12-4.el6.noarch


System info




  • Linux Rhel: 6.3

  • SNMP Master Agent version: 5.5

  • SNMP Protocol version: v2C










share|improve this question
















bumped to the homepage by Community 2 days ago


This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.















  • Do you get any error messages when you try the snmptrapd command?
    – slm
    Jan 25 '14 at 23:38










  • Where's the output?
    – slm
    Jan 26 '14 at 3:16










  • No, i do not have any error messages while i run snmp trapd command..please find the start & end of the dump snmptrapd here:- # snmptrapd -M /usr/share/snmp/mibs -m inUnixPlatformApp-MIB -f -n -Ddump No log handling enabled - turning on stderr logging registered debug token dump, 1 NET-SNMP version 5.5 dumpx_recv:02 01 01 ....... 2014-01-25 22:33:55 UDP: [127.0.0.1]:40313->[127.0.0.1] [UDP: [127.0.0.1]:40313->[127.0.0.1]]: SNMPv2-SMI::mib-2.1.3.0 = Timeticks: (0) 0:00:00.00 SNMPv2-SMI::snmpModules.1.1.4.1.0 = OID: SNMPv2-SMI::mib-2.1.3
    – user57619
    Jan 26 '14 at 3:57










  • In continuation to my previous comment, in dump mode of snmptrapd i am able to see the lines of trap but that seems to be in improper format or not the actual trap, because the snmptrapd when run in normal mode(without dump) i do not get any traps, it just goes blank after the following 3lines: [root@eirsnmp ~]# snmptrapd -M /usr/share/snmp/mibs -m airwide-solutions-inUnixPlatformApp-MIB -f -n -Ddump No log handling enabled - turning on stderr logging registered debug token dump, 1 NET-SNMP version 5.5 The trapd terminal will now be blank forever even after generating snmptraps !!
    – user57619
    Jan 26 '14 at 4:07















up vote
1
down vote

favorite









up vote
1
down vote

favorite











I've been unable to view traps through snmptrapd. I generated a SNMP trap manually using the below provided snmptrap command:



snmptrap -c public -v 2c -n "" localhost 0 uptime


But I'm unable to capture the trap using the below provided snmptrapd command:



snmptrapd -f -M /usr/share/snmp/mibs -m inUnixPlatformApp-MIB -Os


Question: How can I capture the snmptrap in snmptrapd?



Installed software



I have the following RPM packages installed on the RHEL 6.3 server:



# rpm -qa|grep -i snmp
net-snmp-libs-5.5-41.el6.x86_64,
net-snmp-libs-5.5-41.el6.i686,
net-snmp-devel-5.5-41.el6.x86_64,
net-snmp-5.5-41.el6.x86_64,
net-snmp-perl-5.5-41.el6.x86_64,
net-snmp-utils-5.5-41.el6.x86_64,
perl-SNMP_Session-1.12-4.el6.noarch


System info




  • Linux Rhel: 6.3

  • SNMP Master Agent version: 5.5

  • SNMP Protocol version: v2C










share|improve this question















I've been unable to view traps through snmptrapd. I generated a SNMP trap manually using the below provided snmptrap command:



snmptrap -c public -v 2c -n "" localhost 0 uptime


But I'm unable to capture the trap using the below provided snmptrapd command:



snmptrapd -f -M /usr/share/snmp/mibs -m inUnixPlatformApp-MIB -Os


Question: How can I capture the snmptrap in snmptrapd?



Installed software



I have the following RPM packages installed on the RHEL 6.3 server:



# rpm -qa|grep -i snmp
net-snmp-libs-5.5-41.el6.x86_64,
net-snmp-libs-5.5-41.el6.i686,
net-snmp-devel-5.5-41.el6.x86_64,
net-snmp-5.5-41.el6.x86_64,
net-snmp-perl-5.5-41.el6.x86_64,
net-snmp-utils-5.5-41.el6.x86_64,
perl-SNMP_Session-1.12-4.el6.noarch


System info




  • Linux Rhel: 6.3

  • SNMP Master Agent version: 5.5

  • SNMP Protocol version: v2C







snmp centos






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited Jan 25 '14 at 23:35









slm

246k66506672




246k66506672










asked Jan 25 '14 at 18:29









user57619

612




612





bumped to the homepage by Community 2 days ago


This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.







bumped to the homepage by Community 2 days ago


This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.














  • Do you get any error messages when you try the snmptrapd command?
    – slm
    Jan 25 '14 at 23:38










  • Where's the output?
    – slm
    Jan 26 '14 at 3:16










  • No, i do not have any error messages while i run snmp trapd command..please find the start & end of the dump snmptrapd here:- # snmptrapd -M /usr/share/snmp/mibs -m inUnixPlatformApp-MIB -f -n -Ddump No log handling enabled - turning on stderr logging registered debug token dump, 1 NET-SNMP version 5.5 dumpx_recv:02 01 01 ....... 2014-01-25 22:33:55 UDP: [127.0.0.1]:40313->[127.0.0.1] [UDP: [127.0.0.1]:40313->[127.0.0.1]]: SNMPv2-SMI::mib-2.1.3.0 = Timeticks: (0) 0:00:00.00 SNMPv2-SMI::snmpModules.1.1.4.1.0 = OID: SNMPv2-SMI::mib-2.1.3
    – user57619
    Jan 26 '14 at 3:57










  • In continuation to my previous comment, in dump mode of snmptrapd i am able to see the lines of trap but that seems to be in improper format or not the actual trap, because the snmptrapd when run in normal mode(without dump) i do not get any traps, it just goes blank after the following 3lines: [root@eirsnmp ~]# snmptrapd -M /usr/share/snmp/mibs -m airwide-solutions-inUnixPlatformApp-MIB -f -n -Ddump No log handling enabled - turning on stderr logging registered debug token dump, 1 NET-SNMP version 5.5 The trapd terminal will now be blank forever even after generating snmptraps !!
    – user57619
    Jan 26 '14 at 4:07




















  • Do you get any error messages when you try the snmptrapd command?
    – slm
    Jan 25 '14 at 23:38










  • Where's the output?
    – slm
    Jan 26 '14 at 3:16










  • No, i do not have any error messages while i run snmp trapd command..please find the start & end of the dump snmptrapd here:- # snmptrapd -M /usr/share/snmp/mibs -m inUnixPlatformApp-MIB -f -n -Ddump No log handling enabled - turning on stderr logging registered debug token dump, 1 NET-SNMP version 5.5 dumpx_recv:02 01 01 ....... 2014-01-25 22:33:55 UDP: [127.0.0.1]:40313->[127.0.0.1] [UDP: [127.0.0.1]:40313->[127.0.0.1]]: SNMPv2-SMI::mib-2.1.3.0 = Timeticks: (0) 0:00:00.00 SNMPv2-SMI::snmpModules.1.1.4.1.0 = OID: SNMPv2-SMI::mib-2.1.3
    – user57619
    Jan 26 '14 at 3:57










  • In continuation to my previous comment, in dump mode of snmptrapd i am able to see the lines of trap but that seems to be in improper format or not the actual trap, because the snmptrapd when run in normal mode(without dump) i do not get any traps, it just goes blank after the following 3lines: [root@eirsnmp ~]# snmptrapd -M /usr/share/snmp/mibs -m airwide-solutions-inUnixPlatformApp-MIB -f -n -Ddump No log handling enabled - turning on stderr logging registered debug token dump, 1 NET-SNMP version 5.5 The trapd terminal will now be blank forever even after generating snmptraps !!
    – user57619
    Jan 26 '14 at 4:07


















Do you get any error messages when you try the snmptrapd command?
– slm
Jan 25 '14 at 23:38




Do you get any error messages when you try the snmptrapd command?
– slm
Jan 25 '14 at 23:38












Where's the output?
– slm
Jan 26 '14 at 3:16




Where's the output?
– slm
Jan 26 '14 at 3:16












No, i do not have any error messages while i run snmp trapd command..please find the start & end of the dump snmptrapd here:- # snmptrapd -M /usr/share/snmp/mibs -m inUnixPlatformApp-MIB -f -n -Ddump No log handling enabled - turning on stderr logging registered debug token dump, 1 NET-SNMP version 5.5 dumpx_recv:02 01 01 ....... 2014-01-25 22:33:55 UDP: [127.0.0.1]:40313->[127.0.0.1] [UDP: [127.0.0.1]:40313->[127.0.0.1]]: SNMPv2-SMI::mib-2.1.3.0 = Timeticks: (0) 0:00:00.00 SNMPv2-SMI::snmpModules.1.1.4.1.0 = OID: SNMPv2-SMI::mib-2.1.3
– user57619
Jan 26 '14 at 3:57




No, i do not have any error messages while i run snmp trapd command..please find the start & end of the dump snmptrapd here:- # snmptrapd -M /usr/share/snmp/mibs -m inUnixPlatformApp-MIB -f -n -Ddump No log handling enabled - turning on stderr logging registered debug token dump, 1 NET-SNMP version 5.5 dumpx_recv:02 01 01 ....... 2014-01-25 22:33:55 UDP: [127.0.0.1]:40313->[127.0.0.1] [UDP: [127.0.0.1]:40313->[127.0.0.1]]: SNMPv2-SMI::mib-2.1.3.0 = Timeticks: (0) 0:00:00.00 SNMPv2-SMI::snmpModules.1.1.4.1.0 = OID: SNMPv2-SMI::mib-2.1.3
– user57619
Jan 26 '14 at 3:57












In continuation to my previous comment, in dump mode of snmptrapd i am able to see the lines of trap but that seems to be in improper format or not the actual trap, because the snmptrapd when run in normal mode(without dump) i do not get any traps, it just goes blank after the following 3lines: [root@eirsnmp ~]# snmptrapd -M /usr/share/snmp/mibs -m airwide-solutions-inUnixPlatformApp-MIB -f -n -Ddump No log handling enabled - turning on stderr logging registered debug token dump, 1 NET-SNMP version 5.5 The trapd terminal will now be blank forever even after generating snmptraps !!
– user57619
Jan 26 '14 at 4:07






In continuation to my previous comment, in dump mode of snmptrapd i am able to see the lines of trap but that seems to be in improper format or not the actual trap, because the snmptrapd when run in normal mode(without dump) i do not get any traps, it just goes blank after the following 3lines: [root@eirsnmp ~]# snmptrapd -M /usr/share/snmp/mibs -m airwide-solutions-inUnixPlatformApp-MIB -f -n -Ddump No log handling enabled - turning on stderr logging registered debug token dump, 1 NET-SNMP version 5.5 The trapd terminal will now be blank forever even after generating snmptraps !!
– user57619
Jan 26 '14 at 4:07












2 Answers
2






active

oldest

votes

















up vote
0
down vote













I would start by turning up the debugging output from snmptrapd. You can do so like this:



$ snmptrapd -D all -f -M /usr/share/snmp/mibs -m inUnixPlatformApp-MIB -Os


You can see the full list of "all" the valid tokens you can provide for debugging if you want to target things more explicitly here, Debug tokens 5.4.2.1.






share|improve this answer





















  • Hi, i tried the -D mode of snmptrapd and found an error in the last line stating: getaddrinfo("all", NULL, ...): Temporary failure in name resolution couldn't open all -- errno 3 ("No such process") Is this a reason for my trap not being captrued on snmptrapd? If yes, how to overcome the err, because i see i am able to ping the server through hostname but still getting the above err !! Please help..
    – user57619
    Jan 26 '14 at 4:01












  • @user57619 - I would try changing it to the IP addr. to see if that's the real issue or a false positive.
    – slm
    Jan 26 '14 at 4:06










  • Hi, I do not have an option to change the IP, as is my office server and i should stick on to the same ip.. But the issue does not seem to be with IP or hostname because i am able to ping the servers from other servers through both hostname and IP..
    – user57619
    Jan 26 '14 at 4:10










  • @user57619 - I wasn't suggesting to change your IPs, but to use the IP instead of the hostname. The resolving of a hostname to an IP can happen in a variety of ways on Linux, so this was meant to eliminate this as a possible issue.
    – slm
    Jan 26 '14 at 4:19








  • 1




    @user57619 - use the -n switch.
    – slm
    Jan 26 '14 at 5:12


















up vote
0
down vote













SNMP traps arrive as UDP packets to port 162. Is your iptables configured to allow incoming SNMP traps?






share|improve this answer





















    Your Answer








    StackExchange.ready(function() {
    var channelOptions = {
    tags: "".split(" "),
    id: "106"
    };
    initTagRenderer("".split(" "), "".split(" "), channelOptions);

    StackExchange.using("externalEditor", function() {
    // Have to fire editor after snippets, if snippets enabled
    if (StackExchange.settings.snippets.snippetsEnabled) {
    StackExchange.using("snippets", function() {
    createEditor();
    });
    }
    else {
    createEditor();
    }
    });

    function createEditor() {
    StackExchange.prepareEditor({
    heartbeatType: 'answer',
    convertImagesToLinks: false,
    noModals: true,
    showLowRepImageUploadWarning: true,
    reputationToPostImages: null,
    bindNavPrevention: true,
    postfix: "",
    imageUploader: {
    brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
    contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
    allowUrls: true
    },
    onDemand: true,
    discardSelector: ".discard-answer"
    ,immediatelyShowMarkdownHelp:true
    });


    }
    });














    draft saved

    draft discarded


















    StackExchange.ready(
    function () {
    StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f110908%2funable-to-view-traps-through-snmptrad%23new-answer', 'question_page');
    }
    );

    Post as a guest















    Required, but never shown

























    2 Answers
    2






    active

    oldest

    votes








    2 Answers
    2






    active

    oldest

    votes









    active

    oldest

    votes






    active

    oldest

    votes








    up vote
    0
    down vote













    I would start by turning up the debugging output from snmptrapd. You can do so like this:



    $ snmptrapd -D all -f -M /usr/share/snmp/mibs -m inUnixPlatformApp-MIB -Os


    You can see the full list of "all" the valid tokens you can provide for debugging if you want to target things more explicitly here, Debug tokens 5.4.2.1.






    share|improve this answer





















    • Hi, i tried the -D mode of snmptrapd and found an error in the last line stating: getaddrinfo("all", NULL, ...): Temporary failure in name resolution couldn't open all -- errno 3 ("No such process") Is this a reason for my trap not being captrued on snmptrapd? If yes, how to overcome the err, because i see i am able to ping the server through hostname but still getting the above err !! Please help..
      – user57619
      Jan 26 '14 at 4:01












    • @user57619 - I would try changing it to the IP addr. to see if that's the real issue or a false positive.
      – slm
      Jan 26 '14 at 4:06










    • Hi, I do not have an option to change the IP, as is my office server and i should stick on to the same ip.. But the issue does not seem to be with IP or hostname because i am able to ping the servers from other servers through both hostname and IP..
      – user57619
      Jan 26 '14 at 4:10










    • @user57619 - I wasn't suggesting to change your IPs, but to use the IP instead of the hostname. The resolving of a hostname to an IP can happen in a variety of ways on Linux, so this was meant to eliminate this as a possible issue.
      – slm
      Jan 26 '14 at 4:19








    • 1




      @user57619 - use the -n switch.
      – slm
      Jan 26 '14 at 5:12















    up vote
    0
    down vote













    I would start by turning up the debugging output from snmptrapd. You can do so like this:



    $ snmptrapd -D all -f -M /usr/share/snmp/mibs -m inUnixPlatformApp-MIB -Os


    You can see the full list of "all" the valid tokens you can provide for debugging if you want to target things more explicitly here, Debug tokens 5.4.2.1.






    share|improve this answer





















    • Hi, i tried the -D mode of snmptrapd and found an error in the last line stating: getaddrinfo("all", NULL, ...): Temporary failure in name resolution couldn't open all -- errno 3 ("No such process") Is this a reason for my trap not being captrued on snmptrapd? If yes, how to overcome the err, because i see i am able to ping the server through hostname but still getting the above err !! Please help..
      – user57619
      Jan 26 '14 at 4:01












    • @user57619 - I would try changing it to the IP addr. to see if that's the real issue or a false positive.
      – slm
      Jan 26 '14 at 4:06










    • Hi, I do not have an option to change the IP, as is my office server and i should stick on to the same ip.. But the issue does not seem to be with IP or hostname because i am able to ping the servers from other servers through both hostname and IP..
      – user57619
      Jan 26 '14 at 4:10










    • @user57619 - I wasn't suggesting to change your IPs, but to use the IP instead of the hostname. The resolving of a hostname to an IP can happen in a variety of ways on Linux, so this was meant to eliminate this as a possible issue.
      – slm
      Jan 26 '14 at 4:19








    • 1




      @user57619 - use the -n switch.
      – slm
      Jan 26 '14 at 5:12













    up vote
    0
    down vote










    up vote
    0
    down vote









    I would start by turning up the debugging output from snmptrapd. You can do so like this:



    $ snmptrapd -D all -f -M /usr/share/snmp/mibs -m inUnixPlatformApp-MIB -Os


    You can see the full list of "all" the valid tokens you can provide for debugging if you want to target things more explicitly here, Debug tokens 5.4.2.1.






    share|improve this answer












    I would start by turning up the debugging output from snmptrapd. You can do so like this:



    $ snmptrapd -D all -f -M /usr/share/snmp/mibs -m inUnixPlatformApp-MIB -Os


    You can see the full list of "all" the valid tokens you can provide for debugging if you want to target things more explicitly here, Debug tokens 5.4.2.1.







    share|improve this answer












    share|improve this answer



    share|improve this answer










    answered Jan 25 '14 at 23:42









    slm

    246k66506672




    246k66506672












    • Hi, i tried the -D mode of snmptrapd and found an error in the last line stating: getaddrinfo("all", NULL, ...): Temporary failure in name resolution couldn't open all -- errno 3 ("No such process") Is this a reason for my trap not being captrued on snmptrapd? If yes, how to overcome the err, because i see i am able to ping the server through hostname but still getting the above err !! Please help..
      – user57619
      Jan 26 '14 at 4:01












    • @user57619 - I would try changing it to the IP addr. to see if that's the real issue or a false positive.
      – slm
      Jan 26 '14 at 4:06










    • Hi, I do not have an option to change the IP, as is my office server and i should stick on to the same ip.. But the issue does not seem to be with IP or hostname because i am able to ping the servers from other servers through both hostname and IP..
      – user57619
      Jan 26 '14 at 4:10










    • @user57619 - I wasn't suggesting to change your IPs, but to use the IP instead of the hostname. The resolving of a hostname to an IP can happen in a variety of ways on Linux, so this was meant to eliminate this as a possible issue.
      – slm
      Jan 26 '14 at 4:19








    • 1




      @user57619 - use the -n switch.
      – slm
      Jan 26 '14 at 5:12


















    • Hi, i tried the -D mode of snmptrapd and found an error in the last line stating: getaddrinfo("all", NULL, ...): Temporary failure in name resolution couldn't open all -- errno 3 ("No such process") Is this a reason for my trap not being captrued on snmptrapd? If yes, how to overcome the err, because i see i am able to ping the server through hostname but still getting the above err !! Please help..
      – user57619
      Jan 26 '14 at 4:01












    • @user57619 - I would try changing it to the IP addr. to see if that's the real issue or a false positive.
      – slm
      Jan 26 '14 at 4:06










    • Hi, I do not have an option to change the IP, as is my office server and i should stick on to the same ip.. But the issue does not seem to be with IP or hostname because i am able to ping the servers from other servers through both hostname and IP..
      – user57619
      Jan 26 '14 at 4:10










    • @user57619 - I wasn't suggesting to change your IPs, but to use the IP instead of the hostname. The resolving of a hostname to an IP can happen in a variety of ways on Linux, so this was meant to eliminate this as a possible issue.
      – slm
      Jan 26 '14 at 4:19








    • 1




      @user57619 - use the -n switch.
      – slm
      Jan 26 '14 at 5:12
















    Hi, i tried the -D mode of snmptrapd and found an error in the last line stating: getaddrinfo("all", NULL, ...): Temporary failure in name resolution couldn't open all -- errno 3 ("No such process") Is this a reason for my trap not being captrued on snmptrapd? If yes, how to overcome the err, because i see i am able to ping the server through hostname but still getting the above err !! Please help..
    – user57619
    Jan 26 '14 at 4:01






    Hi, i tried the -D mode of snmptrapd and found an error in the last line stating: getaddrinfo("all", NULL, ...): Temporary failure in name resolution couldn't open all -- errno 3 ("No such process") Is this a reason for my trap not being captrued on snmptrapd? If yes, how to overcome the err, because i see i am able to ping the server through hostname but still getting the above err !! Please help..
    – user57619
    Jan 26 '14 at 4:01














    @user57619 - I would try changing it to the IP addr. to see if that's the real issue or a false positive.
    – slm
    Jan 26 '14 at 4:06




    @user57619 - I would try changing it to the IP addr. to see if that's the real issue or a false positive.
    – slm
    Jan 26 '14 at 4:06












    Hi, I do not have an option to change the IP, as is my office server and i should stick on to the same ip.. But the issue does not seem to be with IP or hostname because i am able to ping the servers from other servers through both hostname and IP..
    – user57619
    Jan 26 '14 at 4:10




    Hi, I do not have an option to change the IP, as is my office server and i should stick on to the same ip.. But the issue does not seem to be with IP or hostname because i am able to ping the servers from other servers through both hostname and IP..
    – user57619
    Jan 26 '14 at 4:10












    @user57619 - I wasn't suggesting to change your IPs, but to use the IP instead of the hostname. The resolving of a hostname to an IP can happen in a variety of ways on Linux, so this was meant to eliminate this as a possible issue.
    – slm
    Jan 26 '14 at 4:19






    @user57619 - I wasn't suggesting to change your IPs, but to use the IP instead of the hostname. The resolving of a hostname to an IP can happen in a variety of ways on Linux, so this was meant to eliminate this as a possible issue.
    – slm
    Jan 26 '14 at 4:19






    1




    1




    @user57619 - use the -n switch.
    – slm
    Jan 26 '14 at 5:12




    @user57619 - use the -n switch.
    – slm
    Jan 26 '14 at 5:12












    up vote
    0
    down vote













    SNMP traps arrive as UDP packets to port 162. Is your iptables configured to allow incoming SNMP traps?






    share|improve this answer

























      up vote
      0
      down vote













      SNMP traps arrive as UDP packets to port 162. Is your iptables configured to allow incoming SNMP traps?






      share|improve this answer























        up vote
        0
        down vote










        up vote
        0
        down vote









        SNMP traps arrive as UDP packets to port 162. Is your iptables configured to allow incoming SNMP traps?






        share|improve this answer












        SNMP traps arrive as UDP packets to port 162. Is your iptables configured to allow incoming SNMP traps?







        share|improve this answer












        share|improve this answer



        share|improve this answer










        answered Dec 2 '17 at 18:06









        telcoM

        15.5k12143




        15.5k12143






























            draft saved

            draft discarded




















































            Thanks for contributing an answer to Unix & Linux Stack Exchange!


            • Please be sure to answer the question. Provide details and share your research!

            But avoid



            • Asking for help, clarification, or responding to other answers.

            • Making statements based on opinion; back them up with references or personal experience.


            To learn more, see our tips on writing great answers.





            Some of your past answers have not been well-received, and you're in danger of being blocked from answering.


            Please pay close attention to the following guidance:


            • Please be sure to answer the question. Provide details and share your research!

            But avoid



            • Asking for help, clarification, or responding to other answers.

            • Making statements based on opinion; back them up with references or personal experience.


            To learn more, see our tips on writing great answers.




            draft saved


            draft discarded














            StackExchange.ready(
            function () {
            StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f110908%2funable-to-view-traps-through-snmptrad%23new-answer', 'question_page');
            }
            );

            Post as a guest















            Required, but never shown





















































            Required, but never shown














            Required, but never shown












            Required, but never shown







            Required, but never shown

































            Required, but never shown














            Required, but never shown












            Required, but never shown







            Required, but never shown







            Popular posts from this blog

            Accessing regular linux commands in Huawei's Dopra Linux

            Can't connect RFCOMM socket: Host is down

            Kernel panic - not syncing: Fatal Exception in Interrupt